Related
I have a stupid question, since Chainfire can modify the kernal with 2e recovery, is it possible to use ClockWorkMod recovery to replace the stock recovery directly?
Koush said:
I will probably not create a permanent recovery method, because of the way Samsung handles boot and recovery partitions: they are both contained in the same kernel. So, by creating a recovery image, I would have to replace the boot kernel, and then other devs would not be able to do future kernel tweaks unless they included Clockwork in their kernel.
Furthermore, if someone is using a custom kernel, and I want to upgrade Clockwork, it would overwrite any custom changes they had in their kernel (overclocking, or whatever else). Fakeflash is perfectly acceptable and preferred for the Samsung Galaxy S.
I will of course provide new fakeflash zips for the Galaxy S as I fix bugs and add features.
Click to expand...
Click to collapse
That should suffice as to why there isnt a permanent recovery yet.
There is a way because Modaco has released a Rom with Clockworkrecovery as the default recovery.. ;D But i don`t no how it works ;D
That is possible, yes.
I can't remember the exact name, but I saw a German Guy on Twitter who replaced the stock recovery with ClockWorkMod on our Galaxy S.
Was it Aery...?
Daneshm90 said:
That should suffice as to why there isnt a permanent recovery yet.
Click to expand...
Click to collapse
It sounds reasonable, but still wanna after the official version released
Borky_16 said:
There is a way because Modaco has released a Rom with Clockworkrecovery as the default recovery.. ;D But i don`t no how it works ;D
Click to expand...
Click to collapse
Any link available? Thx.
Dont use wipe, restore,or factory reset in STOCK ICS kernel with your Recovery
Thank you for moderator make this sticky..
You know that this not new for us.. This problem exist in many samsung devices with ICS, i got this brick on my GT-N7000 and my device had a motherboard replacement because of that, and it seem our beloved tab definitely got this problem too..
im no dev..just an ordinary Windows and Unix User,not Using English as my Native
but I will update and summarize the issues in this thread until we got the fix about it..
If you already in ICS you need to read the whole thread from this to figure out what the problem is..
Emmc bugs is exist.. And if you need to know what kind of EMMC you have and the possibilty of brick, use this app from chainfire
This is suspected kernel and recovery build from ICS source with this bug if you try to wipe on this:
-any boot.img from stock ICS
-any recovery.img from stock ICS
-CWM 6.0.1.2 which is build from ICS source..
-update binary which is build from ICS source..
Click to expand...
Click to collapse
Discussion about this:
CWM 6.0.1.2-Risk of Brick start by fred_be9300 please report your issue about CWM here..
Official CM9 thread by kallt_kaffe , discussion about this start from page 107
Click to expand...
Click to collapse
After you read, this is my advice:
Dont use any wipe operation or something similar with that such as:
command "Format" in Edify script if you plan make a flashable zip
Nandroid Restore in CWM (build from ics source)
Using wipe with stock recovery in stock ICS boot.img(kernel)
Wiping in safe CWM in stock ICS boot.img
using wipe and nandroid restore with CWM from ICS source without mmc erase patch
using update-binary from ICS build..(compiled from ICS source without mmc erase patch)
Click to expand...
Click to collapse
Thanks for entropy512 who figure out this and make all samsung users more aware about flashing in ICS
And chainfire who makes the tools..
This is not about what version of cwm are used.. But what kind of kernel that recovery operates..
If the recovery execute the command in honeycomb kernel maybe its more safe then ICS kernel..
This is quote from chainfire itself
Chainfire said:
..... CWM is just a userspace program, nothing special(!) - so if the problem can happen in CWM, it can happen in Android....
Click to expand...
Click to collapse
this is possible solution if you want to flash, wipe or restore in ICS
First method: use recovery.img and boot.img with MMC_CAP_ERASE disable.. For that you must familiar with compiling kernel from the source..
Second method:Flashing recovery.img and boot.img from honeycomb, after installation done reboot to recovery and flash the ROM you desire..Remember, your ROM package must have boot.img and recovery.img too..
Click to expand...
Click to collapse
PLEASE BE CAREFULL UNTIL SOMEONE WITH MORE KNOWLEDGE SOLVE THIS FOR US..REMEMBER ITS JUST A WARNING! WHATEVER YOU DID, YOU OWN THAT RISK!!!
Some people are able to safely wipe and flash using affected kernels forever. Some people can wipe a few times before problems occur, some people have problems on their first wipe.
The number of people that broken kernels affect may only be 5-10% - but so far, there is no way to definitively determine that you are safe without putting your device at risk.
Click to expand...
Click to collapse
nandroid restore....are you serious?
orlandoxpolice said:
nandroid restore....are you serious?
Click to expand...
Click to collapse
Yep. And some zip file update-binary executables too (the edify format() function in the 'updater-script's).
Specifically those update-binary commands that were statically linked with the ICS version of the ext4 library.
Both of these operations (edify format() and nandroid partition restore) make use of the make_ext4fs() function. That function apparently changed in ICS to add a call to the eMMC erase functionality in the vigilant pursuit of security. However, that functionality is what tickles the eMMC fw bug with the 'bad' kernels (i.e. those that don't have the erase functionality disabled).
Oh what a tangled web we weave ...
Correct me if I'm wrong, but if i understand the problem and various threads correctly, the easiest and safest way to keep flashing ics based custom roms without fear of the emmc bug would be to always flash a #honeycomb kernel# in recovery each time #before# flashing any ics rom, right?
So if we have a flashable zip of galaxy tab 8.9 honeycomb kernel or even a pre-ics cm9 kernel, and keep it in our sdcard to be available to flash everytime, then we could, go into recovery, flash the bugless kernel, reboot in to recovery again, then safely flash an ics rom(even wipe data) , since it'll run according to the bugless k ernel (this is how we got the ics roms on our tabs in the first place, right)!
I'm no developer, so I don't know how to make one, but is there an existing flashable zip of the stock honeycomb kernel or a honeycomb based cm9 kernel in the existing threads(maybe motely's should be fine?) Or can a developer craft one for us?
This should work, right? Or an I mistake somewhere?
Sent from my Galaxy Nexus using xda premium
Jnn1 said:
This should work, right?
Click to expand...
Click to collapse
Unfortunately, no.
The problem isn't what you are flashing onto the device or what you are flashing over the top of. It's what you are flashing WITH. This is done with the recovery image (usually Stock or CWM).
The recovery image has its own kernel which is distinct from 'the kernel' used by the regular system. The recovery image is an entirely self-contained mini-system that is able to manipulate the contents of the device. Other than being able to read and write and format the rest of the device it shares no operational functionality with the rest of the system (well, other than the bootloader, of course ).
So if you had HC installed and wanted to flash JB you could still get bricked if your recovery image was using a 'bad' kernel.
This is why there have been recommendations to use CWM 5.x.y.z or 6.0.0.8 or lower. Someone says that 6.0.1.0 seems to work but KK and a few others have strongly recommended the lower versions.
HTH.
orlandoxpolice said:
nandroid restore....are you serious?
Click to expand...
Click to collapse
Nandroid restore is ONLY unsafe in a recovery that (itself) is built with a buggy ICS kernel. Version 6.0.0.8 and before are safe, because based on earlier GB kernel.
Also, update-binary (a copy of which exists in EVERY flashable zip) is ONLY unsafe IF built against buggy ICS kernel module... and if the updater-script in the same zip does a format()
I don't know if we've already seen dangerous update-binary in the wild... Mostly people don't recompile that, but endlessly reuse older ones. Still, you might want to check that next time you want to flash a zip. Or keep a safe update-binary available to inject into any zip you want to flash...
Disclaimer: this is my interpretation based on careful reading of many posts
This thread needs to be stickied!
I was on 6.0.1.2 but now went back to 6.0.1.0 but it looks like I'll be heading for 6.0.0.8
pseudoheld said:
This thread needs to be stickied!
I was on 6.0.1.2 but now went back to 6.0.1.0 but it looks like I'll be heading for 6.0.0.8
Click to expand...
Click to collapse
6.0.1.2 is the only one I compiled that uses the ICS kernel and I've removed the links to it some days ago. I don't remember compiling a 6.0.1.0 version but I could be wrong.
kallt_kaffe said:
6.0.1.2 is the only one I compiled that uses the ICS kernel and I've removed the links to it some days ago. I don't remember compiling a 6.0.1.0 version but I could be wrong.
Click to expand...
Click to collapse
Haha yeah you did it was in the cm9 thread as a test version. I had it running quite some time without any problems but decided to be on the safe side with 6.0.0.8
It think there was a 6.0.0.8 and a 6.0.0.8_alternate (version in file name) Then someone said one of these was saying 6.0.1.0 in the UI. AFAIR.
fred_be9300 said:
It think there was a 6.0.0.8 and a 6.0.0.8_alternate (version in file name) Then someone said one of these was saying 6.0.1.0 in the UI. AFAIR.
Click to expand...
Click to collapse
Right. The 6.0.0.8 in CM9 thread is 6.0.1.0 according to CWM recovery menu header.
tracid said:
Right. The 6.0.0.8 in CM9 thread is 6.0.1.0 according to CWM recovery menu header.
Click to expand...
Click to collapse
Oh well, then they are safe. I just didn't notice the version number had changed. Only the 6.0.1.2 version has the dangerous kernel.
So again...
1. I have the same eMMC chip revision number known to be brickable as per Chainfire's app.
2. I have been using CWM 5.5.0.4 only and never anything else.
3. I have flashed CM9 and AOSP Jelly Bean without bricking my device using CWM 5.5.0.4
Is it safe to assume that flashing the latest CM9 through CWM 5.5.0.4 will not result in a lifeless brick of a P7300?
Again, I am only asking for an assumption, not a definitive answer. Will hold nobody responsible.
de3pkeeper said:
Is it safe to assume that flashing the latest CM9 through CWM 5.5.0.4 will not result in a lifeless brick of a P7300?
Click to expand...
Click to collapse
should be safe!
it seems like only in conjunction with the newer cwm the brick can happen.
boscorama said:
Unfortunately, no.
The problem isn't what you are flashing onto the device or what you are flashing over the top of. It's what you are flashing WITH. This is done with the recovery image (usually Stock or CWM).
The recovery image has its own kernel which is distinct from 'the kernel' used by the regular system. The recovery image is an entirely self-contained mini-system that is able to manipulate the contents of the device. Other than being able to read and write and format the rest of the device it shares no operational functionality with the rest of the system (well, other than the bootloader, of course ).
So if you had HC installed and wanted to flash JB you could still get bricked if your recovery image was using a 'bad' kernel.
This is why there have been recommendations to use CWM 5.x.y.z or 6.0.0.8 or lower. Someone says that 6.0.1.0 seems to work but KK and a few others have strongly recommended the lower versions.
HTH.
Click to expand...
Click to collapse
Ah ... I see ... the recovery has it's own kernel that is a separate beast from the Rom kernel ... thanks for taking the time to kindly explain! And I'll make sure to stay on cwm 6.0.0.8 or lower!
Sent from my GT-P7310 using xda premium
Jnn1 said:
Correct me if I'm wrong, but if i understand the problem and various threads correctly, the easiest and safest way to keep flashing ics based custom roms without fear of the emmc bug would be to always flash a #honeycomb kernel# in recovery each time #before# flashing any ics rom, right?
So if we have a flashable zip of galaxy tab 8.9 honeycomb kernel or even a pre-ics cm9 kernel, and keep it in our sdcard to be available to flash everytime, then we could, go into recovery, flash the bugless kernel, reboot in to recovery again, then safely flash an ics rom(even wipe data) , since it'll run according to the bugless k ernel (this is how we got the ics roms on our tabs in the first place, right)!
I'm no developer, so I don't know how to make one, but is there an existing flashable zip of the stock honeycomb kernel or a honeycomb based cm9 kernel in the existing threads(maybe motely's should be fine?) Or can a developer craft one for us?
This should work, right? Or an I mistake somewhere?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes you can..
We dont know from what kernel the bugs appear maybe from boot.img or from recovery.img..
So the safest way is flash the safe boot.img with safe recovery.img in one flashable.zip and then reboot to recovery again and flash the ROM you desire..
It works and tested by me..
There are 2 types of CWM 6.0.0.8 to choose at KK's CM9 thread. One is original and the other is alternate. So which one should we install. I am comfuse. I am currently on CM10 review. Is KK's CM10 kernel safe to use? Thanks
nexus_g said:
There are 2 types of CWM 6.0.0.8 to choose at KK's CM9 thread. One is original and the other is alternate. So which one should we install. I am comfuse. I am currently on CM10 review. Is KK's CM10 kernel safe to use? Thanks
Click to expand...
Click to collapse
The alternate version is for those folks that experience display issues with the regular one. You can use either one.
I don't know what kernel is in the CM10 preview. But as long as you use a 'safe' recovery for your wipes and resets you should be just fine.
boscorama said:
The alternate version is for those folks that experience display issues with the regular one. You can use either one.
I don't know what kernel is in the CM10 preview. But as long as you use a 'safe' recovery for your wipes and resets you should be just fine.
Click to expand...
Click to collapse
No, mine bricked not in recovery. But on first booting of new rom (unofficial cm9) with 3.1.0 kernel.
notz76 said:
No, mine bricked not in recovery. But on first booting of new rom (unofficial cm9) with 3.1.0 kernel.
Click to expand...
Click to collapse
The important thing here is what you used to install CM9.
So I've had a nexus one for a while now, and recently I decided to root it. I managed to unlock my bootloader and flash clock work recovery. I then made a stupid mistake of trying to flash a rom before rooting my phone or backing up my rom. When I power on my phone now it just freezes on the boot animation. The only thing I can do is access recovery. What is the easiest way to root my nexus one in this condition or is there anyway of flashing a rom, hence fixing it? Preferably from a Mac but I may be able to get access to windows or linux. Thanks in advance
Sent from my U20i using xda app-developers app
moose.splash1 said:
So I've had a nexus one for a while now, and recently I decided to root it. I managed to unlock my bootloader and flash clock work recovery. I then made a stupid mistake of trying to flash a rom before rooting my phone or backing up my rom. When I power on my phone now it just freezes on the boot animation. The only thing I can do is access recovery. What is the easiest way to root my nexus one in this condition or is there anyway of flashing a rom, hence fixing it? Preferably from a Mac but I may be able to get access to windows or linux. Thanks in advance
Sent from my U20i using xda app-developers app
Click to expand...
Click to collapse
Turn off your phone, pop your SD card in your comp and copy the su.zip into it. Pop it back into your phone, boot into recovery and flash it on. Voila, root access!
Then wipe cache, dalvik-cache and all those and reflash the ROM again. You should be good to go.
BTW. I hope you are flashing a ROM which needs a stock HBOOT. Coz for JB ROMs, custom HBOOT is needed. Cheers!
sphinxcs898 said:
Turn off your phone, pop your SD card in your comp and copy the su.zip into it. Pop it back into your phone, boot into recovery and flash it on. Voila, root access!
Then wipe cache, dalvik-cache and all those and reflash the ROM again. You should be good to go.
BTW. I hope you are flashing a ROM which needs a stock HBOOT. Coz for JB ROMs, custom HBOOT is needed. Cheers!
Click to expand...
Click to collapse
Thanks a lot for the help! Do you know of any JB or ICS roms that do not require a special HBOOT? And where is the download for the su.zip you mentioned? Thanks a lot
All newer ROMs have a larger system partition requirement, why not flash an older gingerbread ROM that doesn't require black rose until you get the hang of flashing.
You don't need to flash superuser or busy box or anything first, just wipe all in recovery, flash ROM (plus anything else needed like gapps) reboot
Sent from my Nexus 4 using xda premium
moose.splash1 said:
Thanks a lot for the help! Do you know of any JB or ICS roms that do not require a special HBOOT? And where is the download for the su.zip you mentioned? Thanks a lot
Click to expand...
Click to collapse
demkantor said:
All newer ROMs have a larger system partition requirement, why not flash an older gingerbread ROM that doesn't require black rose until you get the hang of flashing.
You don't need to flash superuser or busy box or anything first, just wipe all in recovery, flash ROM (plus anything else needed like gapps) reboot
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
@demkantor is right. Basically you don't need su.zip coz most ROMs will have that flashed in already. I think the problem you were facing was because you did not wipe your cache/dalvik-cache and data before flashing on the ROM.
[PROBLEM SOLVED] I flashed the custom ROM directly and everything is up and running! Details are below Thanks everyone!
==========================================================================================================================
Experts please help!
I have been surfing my whole day trying to root my Note I (N7000) and flash a custom ROM.
My kernal is XXLSF and I flashed PhilZ-cwm6-ZCLSF-CHN-5.08.5-signed.zip.
I rebooted it after flashing. The Samsung logo appears but then, it blackens and nothing appear on screen.
Now, I can get into the recovery mode by pressing the volume up, power and home button.
I am planning on flashing a stock ROM from SamMobile. Is it okay? WIll I brick my device? What should I do?
I am so frustrated right now:crying:
Your help is much appreciated. Thank you!
"http://forum.xda-developers.com/showthread.php?t=1746794"
From this post, "None since I switched to the CWM4 and CWM6 recoveries (no more superbrick risks under 4.0.4 ICS kernels, only CWM5.x was affected)"
Should I flash a stock ROM that is under 4.0.4, but not the lastest 4.1.2?
What is the XXLSF kernel? May be you flashed an incompatible kernel. Yes you can boot into download mode and flash stock rom.. It will boot up the device again.. Before rooting next time, read instruction more carefully.
If you were intending to flash a custom rom, you can do it without flashing a stock rom as you have access to recovery. In the recovery mode, select mount USB storage>connect to PC.. drives will appear. then place the custom rom zip file on to phone. In recovery mode, choose clean before New rom install and then flash the new rom.
nokiamodeln91 said:
What is the XXLSF kernel? May be you flashed an incompatible kernel. Yes you can boot into download mode and flash stock rom.. It will boot up the device again.. Before rooting next time, read instruction more carefully.
If you were intending to flash a custom rom, you can do it without flashing a stock rom as you have access to recovery. In the recovery mode, select mount USB storage>connect to PC.. drives will appear. then place the custom rom zip file on to phone. In recovery mode, choose clean before New rom install and then flash the new rom.
Click to expand...
Click to collapse
Thank you so much for such prompt reply!!
Really? I can flash a custom ROM without root access?
THANK YOU!!!
You dont need root access to flash a custom rom.. Just CWM recovery which you should have after flashing Philz kernel,
nokiamodeln91 said:
You dont need root access to flash a custom rom.. Just CWM recovery which you should have after flashing Philz kernel,
Click to expand...
Click to collapse
Yes! I do have CWM recovery
Should I flash stock ROM and then flash the custom rom([ROM][JB 4.3][AOSPA][AOKP-MR1][CM10.2]P.A.C True All in 1 ROM[Nightlies])?
because I have never updated my Note I, the kernal version is very old.
The kernel now is not OLD as its now updated to Philz. You can directly install the PAC rom.
nokiamodeln91 said:
The kernel now is not OLD as its now updated to Philz. You can directly install the PAC rom.
Click to expand...
Click to collapse
Thank you for keeping an eye on this post!
I encounter a problem during flashing the custom rom :crying:
Besides, I can't find the option "Format system" while following the steps to flash the custom ROM
Ok.,.. then get any one of the CM kernels first from here,.,http://forum.xda-developers.com/showthread.php?t=1789397
flash the CM kernel first.. then reboot recovery and flash the rom again..
format system data cache and preload are under mounts & storage menu
nokiamodeln91 said:
Ok.,.. then get any one of the CM kernels first from here,.,http://forum.xda-developers.com/showthread.php?t=1789397
flash the CM kernel first.. then reboot recovery and flash the rom again..
format system data cache and preload are under mounts & storage menu
Click to expand...
Click to collapse
AMAZING!!!!
I have finally and successfully boot into my device after nine hours battle with my note I :silly:
But the last eight hours was nothing when comparing with your BIG HELP!
What's weird is that all my photos and data are present
I am 100% sure that I wiped all the data and cache and format data cache
Anything on the internal SD card that you stored using camera or music or videos will not be erased doing a factory reset. For that you will need to choose..format /emmc in the recovery mode. /data is one that app stores on the phone.
nokiamodeln91 said:
Anything on the internal SD card that you stored using camera or music or videos will not be erased doing a factory reset. For that you will need to choose..format /emmc in the recovery mode. /data is one that app stores on the phone.
Click to expand...
Click to collapse
"UI system is forced to stop" appear continuously after changing language from English to Chinese.
Is it true that changing system language will lead to breakdown of system?
THANKS A MILLION!!
I have not used any language other than English. So you may need to ask in the PAC ROM thread.
Sent from my GT-I9500 using xda premium
nokiamodeln91 said:
I have not used any language other than English. So you may need to ask in the PAC ROM thread.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Understood!
Thank you very much for helping me all along! :fingers-crossed:
Please accept my genuinely gratitude for helping a stranger like me!:highfive:
I LOVE YOU!
:thumbup::thumbup::thumbup:
Sent from my GT-I9500 using xda premium
I need to flash a zip file form recovery (cerberus).
I go in recovery mode but isn't present flash zip, but only update.
There is the way to solve it ?...i don't find mod recovery for S5 Mini
Thank
Hispanico
P.S.
I root S5 Mini from this post
Without custom recovery you can't flash any zip.
(CWM, Philz Touch, TWRP )
I really hope that the Devs do something soon. :good:
Without Custom Rom and Recovery it makes no fun.
DönerXXL said:
Without Custom Rom and Recovery it makes no fun.
Click to expand...
Click to collapse
+1
Hispanico