FORUMS
Remove All Ads from XDA

[Important and caution] Stoping further using ICS now until the kernel is rebuilt

232 posts
Thanks Meter: 396
 
By UnknownzD, Senior Member on 22nd August 2012, 08:50 PM
Post Reply Email Thread
So as I need to rebuild the kernel soon, I keep things short.

Unfortunately the kernel src code for the ICS build of our device contains the MMC_CAP_ERASE problem (as I have found it from the src code), I highly recommend everyone stop using the ICS leaked build right now since it has the potential problem to hard brick your device. You can continue to use the device / ICS after the kernel is rebuilt.

To revert back to GB, please do the following things :
1. Boot into download mode / CWM (actually CWM is pretty safe to use if it is using 2.x kernel, and if you don't reboot into the system after wiping /data or done a factory reset, read below)
2. Install any GB kernel (or even the whole package)
3. After installing GB kernel, you are safe to install any files in CWM

btw, if someone has bricked device and have recorded the emmc chip ID as well as the firmware version, please report here. It is important for us to get emmc brickbug test / GotBrickBug to support our device, so that we can blacklist those firmware version.


Until the ICS kernel src is successfully rebuilt, I recommend everyone stop using ICS or just turning off your device.

If you want to continue using ICS, please stop deleting any files from the system. Thank you.

For devs : http://forum.xda-developers.com/show....php?t=1847859 (The line to be removed from the kernel src code in order to suppress MMC_CAP_ERASE bug)


Update 1 : The reason of hard bricking in CWM

For the reason of hard bricking in CWM, there are 2 common possible reasons.

1. After you have wiped the /data partition in CWM, the android system will spawned a lot of files in /data which may trigger the MMC_CAP_ERASE problem if you have rebooted the phone in normal mode (which is using the malfunctioning 3.x kernel). This is because files may get erased (and then the firmware borked the whole partition) after the reset process.
2. The CWM is using a 3.x kernel which has MMC_CAP_ERASE enabled. But for now, all the CWM release for I9103 are based on 2.x kernel only. This is because the recovery partition has got a different kernel when compared to the normal one (which is stored in boot.img).

Those things are confirmed with one of the CWM devs, utkanos (so credit goes to him as well). And I am going to copy and paste the IRC log just to clarify things up (this is not meant to cause any privacy issue, just to clarify things up).
Code:
<utkanos> not the standard boot
<UnknownzD> weird then
<UnknownzD> then how those guys say that the EMMC_CAP_ERASE hard brick is related to CWN>
<UnknownzD> CWM?*
<utkanos> its not
<UnknownzD> ah k then
<utkanos> its after you flash the 'bad' kernel
<utkanos> and boot once
<utkanos> it derps the emmc
<utkanos> permanently
<UnknownzD> ah I totally get what you mean now
<utkanos> ok
<UnknownzD> people uses factory reset / delete data files
<UnknownzD> data files respawned after rebooting in normal situtation
<utkanos> yep
<UnknownzD> = the system hardbricked
<UnknownzD> btw utkanos, do you mind if I copy / paste the above lines to clarify the things in forum?
<UnknownzD> I want people to know that CWM is no unsafe @ all
<UnknownzD> not*
<utkanos> well
<utkanos> its a combination of things
<utkanos> but yes its the kernel bug that is the problem
<utkanos> if the recovery binary attempts to erase before formatting
<utkanos> it triggers the bug
<utkanos> and ICS/JB based recovery code does this
<utkanos> http://forum.xda-developers.com/showpost.php?p=27074278&postcount=69
<utkanos> link them to this thread^
<utkanos> instead of my words
<utkanos> :P
<utkanos> read those top 3 conditions
<utkanos> the real issue is that the emmc doesnt support the command properly
<UnknownzD> yea I know that, but it does not tells that part that
<UnknownzD> people can revert to GB
<UnknownzD> using CWM
<utkanos> recovery attempts to erase emmc
<utkanos> kernel can block it if the code for it is missing
<utkanos> but if code is in the kernel
<utkanos> and recovery requests an erase
<utkanos> and the emmc doesnt know how to handle said command
<utkanos> = bug
<UnknownzD> but as far as I know, all the current CWM release are based on 2.x kernel
<UnknownzD> for I9103
<utkanos> gotcha
<UnknownzD> so I guess it is safe?
<utkanos> then its unlikely the recovery binary will try an erase
<utkanos> but I can't say for certain at all
<utkanos> the best way to secure yourself is to make sure the kernel thats in the recovery does NOT have that erase code
The Following 18 Users Say Thank You to UnknownzD For This Useful Post: [ View ] Gift UnknownzD Ad-Free
 
 
22nd August 2012, 09:01 PM |#2  
Member
Thanks Meter: 156
 
More
How about me, can it brick my device if i flash the new kernel later on?

Sent from my GT-I9103 using xda premium
22nd August 2012, 09:06 PM |#3  
'cooleagle''s Avatar
Retired Forum Moderator
Thanks Meter: 1,145
 
More
Thanks for confirming that buddy, You're a savior !

I'll update the guide accordingly.
Cheers !
22nd August 2012, 09:09 PM |#4  
Indha Lezzio's Avatar
Senior Member
Flag Barcelona
Thanks Meter: 204
 
More
I'm the first one that hates ETA's... but could i kindly ask if we are taking about hours or days for all of our respected devs to rebuild the kernel.
I'm a little scared about the information in the post (thanks for the information and how kindly you share it, for sure), and maybe me and some others would only turn off device for several hours waiting for the new kernel than dw to GB.

Hope that the question is understood, i do not want neither to break the rules neither give hurry to all this lovely people that work so hard for them, and for us, and for free. But the importance of the post makes me kindly ask the question mentioned before.

Thanks to all
The Following User Says Thank You to Indha Lezzio For This Useful Post: [ View ] Gift Indha Lezzio Ad-Free
22nd August 2012, 09:11 PM |#5  
OP Senior Member
Thanks Meter: 396
 
More
Quote:
Originally Posted by Indha Lezzio

I'm the first one that hates ETA's... but could i kindly ask if we are taking about hours or days for all of our respected devs to rebuild the kernel.
I'm a little scared about the information in the post (thanks for the information and how kindly you share it, for sure), and maybe me and some others would only turn off device for several hours waiting for the new kernel that dw to GB.

Hope that the question is understood, i do not want neither to break the rules neither give hurry to all this lovely people that work so hard for them, and for us, and for free. But the importance of the post makes me kindly ask the question mentioned before.

Thanks to all

I am starting up my debian VMs already and I am not sure whether I can build it on first time or not.

Not to mention that I have lost all the otatools in late June / July (which is required to unpack kernel).
The Following 3 Users Say Thank You to UnknownzD For This Useful Post: [ View ] Gift UnknownzD Ad-Free
22nd August 2012, 09:14 PM |#6  
Indha Lezzio's Avatar
Senior Member
Flag Barcelona
Thanks Meter: 204
 
More
Thanks for your kind answer, and SUCCESS!!!
22nd August 2012, 09:20 PM |#7  
OP Senior Member
Thanks Meter: 396
 
More
Quote:
Originally Posted by Machram

How about me, can it brick my device if i flash the new kernel later on?

Sent from my GT-I9103 using xda premium

If your device is not bricked now then the device cannot not be bricked after the new kernel is released.
The Following 3 Users Say Thank You to UnknownzD For This Useful Post: [ View ] Gift UnknownzD Ad-Free
22nd August 2012, 09:58 PM |#8  
OP Senior Member
Thanks Meter: 396
 
More
Okay it is compiling right now and it would take @ least 15 mins to see if any errors occur, let hope the things go well. Will only know about half an hour later. And I still need some times to repack the initramfs.
The Following 2 Users Say Thank You to UnknownzD For This Useful Post: [ View ] Gift UnknownzD Ad-Free
23rd August 2012, 01:29 AM |#9  
Google86's Avatar
Senior Member
Flag Spain, EU.
Thanks Meter: 34
 
More
but, can I just keep ics atm?

I'm not planning doing any wipe. Can I just delete and copy new files on my external SD without taking any risks?


Correct me if I'm wrong, are you making a bug free ICS kernel flasable via CMW? ( dont wanna lose configs) just flash the bug free kernel would be posible?

thank you!
23rd August 2012, 02:28 AM |#10  
pudup's Avatar
Senior Member
Thanks Meter: 133
 
More
If I don't do any wipes or delete anything from system, will I be ok?

Sent from my GT-I9103 using XDA Premium HD app
23rd August 2012, 03:52 AM |#11  
CallMeVentus's Avatar
Senior Member
Flag Singapore
Thanks Meter: 2,876
 
Donate to Me
More
We need to look at the source code of the Notes/SIIs and see if we can adapt the patchset from there

"Friends forever." - Ventus
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes