Related
ive looked at the threads to see what i can do but none of what they said worked. i want to revert to the stock recovery, if possible. any help will be appreciated. willing to donate to whoever can help me out thanks
Can't you just delete the update.zip from your sd card and then not use it?
wicked7o7 said:
ive looked at the threads to see what i can do
Click to expand...
Click to collapse
1. No you haven't.
2. This thread doesn't go here.
wicked7o7 said:
ive looked at the threads to see what i can do but none of what they said worked. i want to revert to the stock recovery, if possible. any help will be appreciated. willing to donate to whoever can help me out thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=731989
feed a homeless person
TechTony13 said:
Can't you just delete the update.zip from your sd card and then not use it?
Click to expand...
Click to collapse
+1. Ya just remove the update.zip and the next time you reboot into recovery it should be stock recovery.
i actually tried doing this step already and it didnt remove it from my phone
wicked7o7 said:
i actually tried doing this step already and it didnt remove it from my phone
Click to expand...
Click to collapse
Were you able to remove the update.zip from your home directory on your phone? If that update.zip is gone then you should not be able to get into clockwork recovery.
In fact to actually get into clockwork recovery you not only have to have a clockwork recovery update.zip on your phone, but you actually boot into stock recovery then have to select reinstall packages to get into clockwork recovery.
I'm going to assume because you haven't shared what you're running, you're running Cognition 2.1.7 which contains clockwork built in and can't be "replaced" since it is the stock. Either that, or you installed Unhelpful's 1.7 kernel manually.
Either way, you can't remove it. You'd need to switch kernels.
i deleted the update.zip but it still booted clockwordmod recovery.
how do i manually removed the kernel? ands after removing what would you suggest be the best kernel/rom to run so that i can overclock my samsung captivate to 1.2
wicked7o7 said:
i deleted the update.zip but it still booted clockwordmod recovery.
how do i manually removed the kernel? ands after removing what would you suggest be the best kernel/rom to run so that i can overclock my samsung captivate to 1.2
Click to expand...
Click to collapse
Um I don't think you want to "manually" remove the kernel. You can flash another kernel over your current one using odin or if you have another kernel that is packaged with a clockwork flashable rom you could use the clockwork recovery that you are trying to get rid of. By the way the kernel is your OS, your phone won't work to well without one.
Unhelpfuls kernel is probably your best option if you want to overclock.
i got the problem fixed, and i used unhelpfuls kernel the newest one v 1.7 and even tried the cognition v2.1.7 with unhelpfuls kernels and i was not able to overclock on setcpu.
do you think i should use an older version of unhelpfuls kernels so that i can overclock?
The info you need about how to overclock can be found in unhelpfuls thread
http://forum.xda-developers.com/showthread.php?t=762171
The first post in my kernel thread explains all features and how to use them.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi, I am a new user on the xda forums (although I have read countless threads). I am a little confused as to what I should do with my captivate. I am debating between flashing 2.3 (to which I see only one drawback: there are not many stable roms out there and flashing them can be a struggle as my recovery image is not very functional in 2.3), or sticking to 2.2 and finding a nice rom that I enjoy (only drawback: it's 2.2 and not 2.3! ) So can anyone advise what to do? Thanks in advance!
My opinion: If you're new to flashing, flash a 2.2 rom. There's less chance of things going truly wrong (less true brick chances). Then, once you feel comfortable flashing (and know a little more), make the jump to 2.3.
I'd say go with 2.2, unless you are feeling brave. CM7 and MIUI (both 2.3) have pretty short battery life. Some people talk about having good battery life, but I think those people are in the minority.
thanks for the quick responses. Well I have flashed roms before (not really new to it), it's just that I haven't done it through the clockwork mod recovery because I am not able perform functions in recovery mode when running 2.3 (which is what I am currently running). Is there a stable 2.3 recovery image for the captivate out there? (none of the options in rom manager seem to work for me...) Have others been able to successfully use rom manager on a Captivate running 2.3?? If so, could someone please provide detailed instructions on how to do so?
What are you NOT able to do in recovery mode for 2.3 that you CAN do in 2.2? I mean I have been from 2.1>2.2> 2.3.4>2.3.3>2.3.4 via clockworkmod without any issues.
What exactly are you trying/wanting to do? If you are just trying to change roms? A little more info might be helpful.
Sent from My KickAss Captivated CM7 OC'd 1.5Ghz/Undervolted
well yea basically I can't use rom manager to flash a clockwork mod recovery that is functional on my captivate. This hampers me from flashing roms through recovery. Could someone just walk me through the installation of rom manager on a 2.3 stock captivate and then the flshing of a recovery image (chosing the proper model etc.)? (I think the issue may have something to do with unsigned packages or something like that?)
sharma_akarsh said:
well yea basically I can't use rom manager to flash a clockwork mod recovery that is functional on my captivate. This hampers me from flashing roms through recovery. Could someone just walk me through the installation of rom manager on a 2.3 stock captivate and then the flshing of a recovery image (chosing the proper model etc.)? (I think the issue may have something to do with unsigned packages or something like that?)
Click to expand...
Click to collapse
pretty sure there is a ton of info on here about that exact error.......in fact there is a freakin sticky on it.
you cant use ROM manager to flash recovery on 2.2 or 2.3....without getting around that error
hint: that error makes a really good search
Pirateghost said:
pretty sure there is a ton of info on here about that exact error.......in fact there is a freakin sticky on it.
you cant use ROM manager to flash recovery on 2.2 or 2.3....without getting around that error
hint: that error makes a really good search
Click to expand...
Click to collapse
okay well I found a method a while back involving the replacement of the recovery in the system/bin folder with a moded 3e recovery.... (not to change topic) but would you recommend soing that and then using cwm, or should i try this new bootloader stuff with Odin (or whatever is needed to flash roms through odin)?
sharma_akarsh said:
okay well I found a method a while back involving the replacement of the recovery in the system/bin folder with a moded 3e recovery.... (not to change topic) but would you recommend soing that and then using cwm, or should i try this new bootloader stuff with Odin (or whatever is needed to flash roms through odin)?
Click to expand...
Click to collapse
you have some reading to do.
pick a rom that you want, flash it
2.2 and 2.3 will come with android recovery 3e. to get around signature verification error, you need to replace the recovery as you indicated
if you are flashing from 2.1/2.2 to 2.3 (excluding CM7 and MIUI) you will be required to flash bootloaders first before you can flash the 2.3 rom
aside from going from 2.1/2.2 to 2.3, there is no reason to flash bootloaders....
if you stick with 2.2 roms, as long as you take care of the 3e recovery, you use CWM....always
if you go to 2.3 roms, flash the bootloaders ONE TIME, then you can flash as often as you want,
Pirateghost said:
you have some reading to do.
pick a rom that you want, flash it
2.2 and 2.3 will come with android recovery 3e. to get around signature verification error, you need to replace the recovery as you indicated
if you are flashing from 2.1/2.2 to 2.3 (excluding CM7 and MIUI) you will be required to flash bootloaders first before you can flash the 2.3 rom
aside from going from 2.1/2.2 to 2.3, there is no reason to flash bootloaders....
if you stick with 2.2 roms, as long as you take care of the 3e recovery, you use CWM....always
if you go to 2.3 roms, flash the bootloaders ONE TIME, then you can flash as often as you want,
Click to expand...
Click to collapse
Ohhhh I see.... I don't think I clarified this, but I am currently on stock 2.3 using this method mentioined by: nakedninja42
I personally always remove my external memory and sim card before using odin. It is not needed as people will post but neither is doing master clear. I do these steps just to make sure I eliminate any possible issues that can occur during flashing.
1) Download Firmware from http://www.samfirmware.com/WEBPROTECT-samsungusa.htm
2) Flash back to stock JF6 w/ odin one-click and did a master clear.
3) Flash Gingerbread KF1 using Odin (see image in post link for reference) http://forum.xda-developers.com/show...9&postcount=75
4) Flash fugu kernel http://forum.xda-developers.com/show....php?t=1010141 Look for the step two that says download odin or heimdall, select the ODIN (well the version your going to use).
5) Flash stock kernel (see post link) credit to lownox for helping me on that http://forum.xda-developers.com/show...&postcount=116
6) Settings>Applications> enable Unknown Sources (AT&T finally got something right)
7) Install busybox from market
8) ENJOY!
Click to expand...
Click to collapse
So from here, do I need to do anything additional with bootladers in order to flash other roms - how exactly do I flash roms from this point? Thanks!
if you are already on 2.3, then you already have the bootloaders. you dont need to do anything with odin or bootloaders to get a new rom on. bypass 3e recovery and use CWM... NOT ROM MANAGER, to flash your rom
Pirateghost said:
if you are already on 2.3, then you already have the bootloaders. you dont need to do anything with odin or bootloaders to get a new rom on. bypass 3e recovery and use CWM... NOT ROM MANAGER, to flash your rom
Click to expand...
Click to collapse
Sorry to sound extremely noobish... but I thought cwm was through rom-manager?? How do I go about flashing solely through cwm?
on the samsung galaxy s line, cwm is an update.zip file. all rom manager does is put an update.zip of itself on the /sdcard/
you dont need rom manager, just that update.zip. if you have bypassed 3e recovery, it will work.
Pirateghost said:
on the samsung galaxy s line, cwm is an update.zip file. all rom manager does is put an update.zip of itself on the /sdcard/
you dont need rom manager, just that update.zip. if you have bypassed 3e recovery, it will work.
Click to expand...
Click to collapse
o okay, that makes sense. I did see that update.zip file when using rom manager. So as I think you have said I already bypassed the 3e recovery because I am now on 2.3? So just find that update.zip file and everything will work through my recovery?
sharma_akarsh said:
o okay, that makes sense. I did see that update.zip file when using rom manager. So as I think you have said I already bypassed the 3e recovery because I am now on 2.3? So just find that update.zip file and everything will work through my recovery?
Click to expand...
Click to collapse
no. any time you use 'official' firmware and not a custom rom, you will get 3e recovery back to defaults. you will need to bypass it again
Pirateghost said:
no. any time you use 'official' firmware and not a custom rom, you will get 3e recovery back to defaults. you will need to bypass it again
Click to expand...
Click to collapse
yea okay that is what i have been trying to do with the replacing of the recovery... but that method does not seem to work. Do you have any other suggestions?
Nevermind I think I got it...
sharma_akarsh said:
yea okay that is what i have been trying to do with the replacing of the recovery... but that method does not seem to work. Do you have any other suggestions?
Click to expand...
Click to collapse
Do you just want to get CWM recovery somehow? If you already have GB BL flash a custom kernel using ODIN which has CWM. For how to flash GB try to see installation instructions from Apex
got it-thanks!
i open this thread for furthur update of CWM recovery
What working :
Every things
CWM TOUCH 5.2.0.8 ext
add option to choose ext type to format your sdcard while partition
CWM TOUCH 5.2.0.8
Thanks to Napstar for Great Job
Original Thread for CWM touch
CWM 5.2.0.8 rev3
change key layout to default(tested), fix update from older CWM for some baseband
CWM 5.2.0.8 rev2Outdated
add option(tested, for fix permission work only for system app), change key layout(tested), try to make compatible with ROM manager (untested)
CWM 5.2.0.8Outdated
fix recovery backup
CWM 5.2.0.8 Outdated
please rename from update-CWM-5 .2.0.8-squadzone-signed.zip into update-CWM-5.2.0.8-squadzone-signed.zip before Flashing
CWM 5.2.0.7
How to Flash :
1. put this file into your SDCARD
2. goto CWM recovery
3. Choose this file
4. Flash it
5. goto advanced menu
6. reboot recovery
7. done
YOU CAN FLASH THIS ON RZ RECOVERY FOR CHANGE RZ RECOVERY FROM YOUR DEVICE
How to flash using RZ recovery :
1. choose install
2. choose this file
3. install this file
4. reboot recovery
5. done
I hope it fix some bug. 5.0.2.6 sometime can not install rom.
ver 4 is so good. But I like color in v5
Now we have another great work from our artist Yanuar Harry(squadzone).
I just got a new MINI and wanted to know if it is possible to flash CMW 5.0.2 .7 on stock RECOVERY????
lackhoo said:
I just got a new MINI and wanted to know if it is possible to flash CMW 5.0.2 .7 on stock RECOVERY????
Click to expand...
Click to collapse
Well if you read the second post, you'll see that CWM it's mentioned there. I think you need a custom Recovery to do that.
lackhoo said:
I just got a new MINI and wanted to know if it is possible to flash CMW 5.0.2 .7 on stock RECOVERY????
Click to expand...
Click to collapse
you need to use this first CWM via ODIN
then update with flash this file CWM
Hey, squadzone any way to integrate it with rom manager?
Not necessary, but if it is it would be better.
Sent from my GT-S5570 using xda premium
Thanks
Send From My Samsung Galaxy using XDA
Is it possible to somehow make everything smaller ?
nishanty13 said:
Hey, squadzone any way to integrate it with rom manager?
Not necessary, but if it is it would be better.
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
No, i will not touch ROM manager,
TheWhisp said:
Is it possible to somehow make everything smaller ?
Click to expand...
Click to collapse
can you explain? i dont understand what you mean bro,
squadzone said:
can you explain? i dont understand what you mean bro,
Click to expand...
Click to collapse
I guess he is referring to the font size mr. squad..
Yes, I meant the font size, some letters are cut off from the screen.
hey squadzone! what tool do you use to unpack the recovery?
TheWhisp said:
Yes, I meant the font size, some letters are cut off from the screen.
Click to expand...
Click to collapse
the font already small,
may be i will fix the layout like i did on RZ recovery
dhruvbatra205 said:
hey squadzone! what tool do you use to unpack the recovery?
Click to expand...
Click to collapse
What you mean unpack?
im build this recovery from source, not just pack or unpack for boot.img, Lol
squadzone said:
No, i will not touch ROM manager,
Click to expand...
Click to collapse
Totally your choice.
Sent from my GT-S5570 using xda premium
squadzone said:
What you mean unpack?
im build this recovery from source, not just pack or unpack for boot.img, Lol
Click to expand...
Click to collapse
you coded the whole recovery?? thats nice!
otherwise, do you know any way to unpack the recovery?
No, he didn't code it. He took the source, edited it to work with Galaxy Mini and then compiled.
TheWhisp said:
No, he didn't code it. He took the source, edited it to work with Galaxy Mini and then compiled.
Click to expand...
Click to collapse
Yes, absolutely correct... He modified the source of clock work mod recovery to make it work with our mini.
BTW, @squadzone, Can you please make this recovery flash able via Odin. It would be nice, if we can flash this directly without having to flash the original/older recovery.
Also, it would be much nice if it can be flashed directly from stock recovery. Do you think you can give it a go?
Regards!
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.
Hello,
I have the Samsung N7000, but it is stuck on Odin too.
My phone is not bricked or something like it, but I want Clockworkmod recovery 6.0.4.5 on it so I can flash Cyanogenmod 11 KitKat on it.
It is stuck on NAND WRITE too. I already have Clockworkmod recovery 6.0.2.8 on it, so I need to upgrade it.
Any suggestions??
Best regards, Joey
Moved to a new thread in Note Q&A
JoeyLohstroh said:
Hello,
I have the Samsung N7000, but it is stuck on Odin too.
My phone is not bricked or something like it, but I want Clockworkmod recovery 6.0.4.5 on it so I can flash Cyanogenmod 11 KitKat on it.
It is stuck on NAND WRITE too. I already have Clockworkmod recovery 6.0.2.8 on it, so I need to upgrade it.
Any suggestions??
Best regards, Joey
Click to expand...
Click to collapse
You have not mentioned the file you were trying to flash.. No mind readers here...
Anyways, flash raw kernel from the current recovery and reboot recovery.
nokiamodeln91 said:
You have not mentioned the file you were trying to flash.. No mind readers here...
Anyways, flash raw kernel from the current recovery and reboot recovery.
Click to expand...
Click to collapse
Sorry, I tried flashing Clockworkmod 6.0.4.5 tar.md5 file.
It ran till it said NAND WRITE START and than FAIL. The collor above turned red and instead of PASS it said FAIL!
So raw kernel should fix this?
Do you have a link maybe? I'll search for it on Google but I want to make sure I have the good file.
Edit*
I found what you told me, but it says that raw kernel is for Android 4.4?
http://forum.xda-developers.com/showthread.php?t=2397000
I have 4.1.2 so I'm not sure if this will brick my device or something like that.
My device is all working fine and it is not bricked or bootloop YET, and since it has that NAND WRITE fail I'm not sure if it will reinstall my stock rom.. if it may brick.
I will still say what I wrote above.. Flash raw r4..reboot recovery and flash kk rom.
nokiamodeln91 said:
I will still say what I wrote above.. Flash raw r4..reboot recovery and flash kk rom.
Click to expand...
Click to collapse
Allright, but I don't need to upgrade my cwm then? Because on several websites are telling me that I need at least Philz touch CWM 6.0.4.3 on it..
JoeyLohstroh said:
Allright, but I don't need to upgrade my cwm then? Because on several websites are telling me that I need at least Philz touch CWM 6.0.4.3 on it..
Click to expand...
Click to collapse
1. To flash a kitkat rom you will need a recent Cwm recovery.
2. Philz tw kernel are not updated to latest cwms.
3. If you try to flash philz_touch_xxx.zip, it won't work as you already saw.
So if you want to root the phone, use philz tw kernel that is associated with a rom build number like XXLTA.. Then you will get Cwm but not recent enough flash kk. That's why you flash raw r4.reboot into recovery takes to to recent Cwm. From there you can flash kk..
Just note that r4 is for 4.3 and will not boot a 4.1.2 so you will need to flash kk after r4.
nokiamodeln91 said:
1. To flash a kitkat rom you will need a recent Cwm recovery.
2. Philz tw kernel are not updated to latest cwms.
3. If you try to flash philz_touch_xxx.zip, it won't work as you already saw.
So if you want to root the phone, use philz tw kernel that is associated with a rom build number like XXLTA.. Then you will get Cwm but not recent enough flash kk. That's why you flash raw r4.reboot into recovery takes to to recent Cwm. From there you can flash kk..
Just note that r4 is for 4.3 and will not boot a 4.1.2 so you will need to flash kk after r4.
Click to expand...
Click to collapse
Aah like that. But I think that I need Raw kernel R5 than? Because KitKat is Android 4.4
And when I flash raw kernel, than I should be able of flashing newest Cwm?
JoeyLohstroh said:
Aah like that. But I think that I need Raw kernel R5 than? Because KitKat is Android 4.4
And when I flash raw kernel, than I should be able of flashing newest Cwm?
Click to expand...
Click to collapse
Hi,
Is not possible to flash recovery without kernel, on recent samsung phones recovery and kernel are tied. (Maybe you can change recovery editing the kernel image but that is out of subject and maybe your skills).
Follow the steps @nokiamodeln91 suggest you, there is no other way. Raw Kernel has a KK compatible recovery.
llawarta said:
Hi,
Is not possible to flash recovery without kernel, on recent samsung phones recovery and kernel are tied. (Maybe you can change recovery editing the kernel image but that is out of subject and maybe your skills).
Follow the steps @nokiamodeln91 suggest you, there is no other way. Raw Kernel has a KK compatible recovery.
Click to expand...
Click to collapse
Okay. But if KitKat doesn't work that well, do I need to downgrade my Kernel and Cwm recovery than?
And do you have a link to the stock kernel?
Then you go into recovery, wipe data, and flash anew rom using odin or use recovery to flash a custom rom.
nokiamodeln91 said:
Then you go into recovery, wipe data, and flash anew rom using odin or use recovery to flash a custom rom.
Click to expand...
Click to collapse
But do you know/have a link to the stock kernel?
Just in case..
JoeyLohstroh said:
But do you know/have a link to the stock kernel?
Just in case..
Click to expand...
Click to collapse
No, and what will you do with the stock kernel?
nokiamodeln91 said:
No, and what will you do with the stock kernel?
Click to expand...
Click to collapse
If cwm doesn't want to instal KitKat, because of some reason, or I decide to not install it, than I want to reboot 4.1.2 but because of the Raw Kernel that won't be possible.
JoeyLohstroh said:
If cwm doesn't want to instal KitKat, because of some reason, or I decide to not install it, than I want to reboot 4.1.2 but because of the Raw Kernel that won't be possible.
Click to expand...
Click to collapse
LOL that does not make any sense.. You will need to restore the backup or install a new rom. There is no need to separately install a stock kernel.. May be you need to read more how all this works.
nokiamodeln91 said:
LOL that does not make any sense.. You will need to restore the backup or install a new rom. There is no need to separately install a stock kernel.. May be you need to read more how all this works.
Click to expand...
Click to collapse
Well, I didn't know that you sometimes need another kernel before you can install cwm.
I have been installing custom roms en recoverys many times on LG's so that isn't the problem.
But the NAND WRITE and FAIL problem must be a kernel issue than?