Related
Since I was an android virgin until just before Christmas, I'm still trying to get to grips with all the cool stuff that can be done.
I've rooted the phone and unlocked the bootloader. Everything else is currently stock.
I don't want to go to Clockwork recovery, or Cyanogen/MoDaCo ROMs. Not yet. I'm still savouring the "Google Experience".
However, I have three questions (which may turn into many more ) about flashing new kernels, and I don't want to clog up any specific kernal thread with noob questions.
1) Does flashing a kernel wipe the whole phone the way unlocking the bootloader did?
2) If you're running stock ROM with new kernel, will you still pick up OTA updates as before?
3) How do you get the original kernal back if you don't like the new one (or if it just goes totally tits up)?
Thanks guys
EDIT: Yes, I realise there is a search and this may well have been asked before. But before someone points this out, I'd like to mention that if you do a search for "android kernel", you get approximately 1 bajillion hits...
Mr.Clark said:
Since I was an android virgin until just before Christmas, I'm still trying to get to grips with all the cool stuff that can be done.
I've rooted the phone and unlocked the bootloader. Everything else is currently stock.
I don't want to go to Clockwork recovery, or Cyanogen/MoDaCo ROMs. Not yet. I'm still savouring the "Google Experience".
However, I have three questions (which may turn into many more ) about flashing new kernels, and I don't want to clog up any specific kernal thread with noob questions.
1) Does flashing a kernel wipe the whole phone the way unlocking the bootloader did?
2) If you're running stock ROM with new kernel, will you still pick up OTA updates as before?
3) How do you get the original kernal back if you don't like the new one (or if it just goes totally tits up)?
Thanks guys
EDIT: Yes, I realise there is a search and this may well have been asked before. But before someone points this out, I'd like to mention that if you do a search for "android kernel", you get approximately 1 bajillion hits...
Click to expand...
Click to collapse
1) No, you should not wipe anything before flashing a kernel. You should however do a NANDroid backup.
2) You should be able to but it will wipe your kernel.
3) Restore your backup from #1
Mr.Clark said:
Since I was an android virgin until just before Christmas, I'm still trying to get to grips with all the cool stuff that can be done.
I've rooted the phone and unlocked the bootloader. Everything else is currently stock.
I don't want to go to Clockwork recovery, or Cyanogen/MoDaCo ROMs. Not yet. I'm still savouring the "Google Experience".
However, I have three questions (which may turn into many more ) about flashing new kernels, and I don't want to clog up any specific kernal thread with noob questions.
1) Does flashing a kernel wipe the whole phone the way unlocking the bootloader did?
2) If you're running stock ROM with new kernel, will you still pick up OTA updates as before?
3) How do you get the original kernal back if you don't like the new one (or if it just goes totally tits up)?
Thanks guys
EDIT: Yes, I realise there is a search and this may well have been asked before. But before someone points this out, I'd like to mention that if you do a search for "android kernel", you get approximately 1 bajillion hits...
Click to expand...
Click to collapse
flashing a kernel doesnt wipe your phone, it simply replaces whatever kernel is in your phone at the moment.
kenvan19 said:
1) No, you should not wipe anything before flashing a kernel. You should however do a NANDroid backup.
Click to expand...
Click to collapse
Right. Guess what my next question will be
kenvan19 said:
2) You should be able to but it will wipe your kernel.
3) Restore your backup from #1
Click to expand...
Click to collapse
2) Is fine, as once I've figured out how to NANDroid backup, re-flashing it should be easy enough. 3) Is fine, once I've taken the backup in the first place.
simms22 said:
flashing a kernel doesnt wipe your phone, it simply replaces whatever kernel is in your phone at the moment.
Click to expand...
Click to collapse
Excellent, thanks!
Ok. So all the NANDroid guides I've seen here start with ADB and Fastboot (which I remember doing when I rooted the phone), but then they say about flashing alternative recovery images... is that necessary? Or is that what the fastboot thing was?
I've just checked and ADB still works, so if fastboot is an alternative recovery image, am I good to take a NANDroid backup, and if so, how do I do that?
If Fastboot is not an appropriate recovery image, do I need Clockwork Recovery (is that different to the "CWM" I see mentioned around here?)?
The Nexus S guide I read said that there was a NANDroid option in the Clockwork Recovery. Now this isn't in my recovery options, obviously, but I assume with ADB, a command prompt and a few instructions, I can do it manually. Maybe.
Bear with me guys, I'll get there eventually...
Ok, scratch the NANDroid questions. NANDroid is a backup tool contained in the Clockwork Mod recovery image.
Using Fastboot, you can boot from the recovery image without flashing it (using this guide here), so I've still got whatever recovery image I got when I did Paul's rooting technique, but have booted into CWM once to do the NANDroid backup.
I may flash CWM later, that's a task for another day.
So. Now I've got the backup (and thus, booting from that image again later, the ability to restore from it), I can try flashing the kernel. Which I can do from the regular recovery image.
Mr.Clark said:
Ok, scratch the NANDroid questions. NANDroid is a backup tool contained in the Clockwork Mod recovery image.
Using Fastboot, you can boot from the recovery image without flashing it (using this guide here), so I've still got whatever recovery image I got when I did Paul's rooting technique, but have booted into CWM once to do the NANDroid backup.
I may flash CWM later, that's a task for another day.
So. Now I've got the backup (and thus, booting from that image again later, the ability to restore from it), I can try flashing the kernel. Which I can do from the regular recovery image.
Click to expand...
Click to collapse
To flash from the stock recovery you must rename files update.zip just FYI. I've said it before and I'll say it again; there are no possible negative repercussions from flashing a non-stock recovery image.
Apparently it was unsigned, so the stock recovery wouldn't do anything with it.
Back in CWM and it worked fine. I may have to flash that, it's damned useful...
So now I have a new kernel!
Thanks for all your help
Mr.Clark said:
Apparently it was unsigned, so the stock recovery wouldn't do anything with it.
Back in CWM and it worked fine. I may have to flash that, it's damned useful...
So now I have a new kernel!
Thanks for all your help
Click to expand...
Click to collapse
It is very useful indeed! Enjoy your kernel
Ah, am I right in thinking that if I flash CWM, I can't revert back to stock if I want to?
I'm hoping to do nothing permanent at this point...
Mr.Clark said:
Ah, am I right in thinking that if I flash CWM, I can't revert back to stock if I want to?
I'm hoping to do nothing permanent at this point...
Click to expand...
Click to collapse
Yes, you can flash back. Not only can you but depending on how you did flash the recovery the phone may revert it on your behalf. I know mine has several times, like any time I reboot. There's ways to stop it from doing that but I don't mind.
To get the stock recovery back if it isn't automatically restoring means flashing an NAND from the Dev section here.
I didn't want to open a new thread just to ask this so I hope it's OK to post it here.
I'm very interested in getting supercurio's voodoo sound and ext4 mod on my Nexus S but I don't need/want the overclocked frequencies and other stuff included on most of the kernels out there. You guys know any kernel that I could flash to get those and keep my stock fequencies?
Thanks
Sent from my Nexus S using XDA App
nicholasbgr said:
I didn't want to open a new thread just to ask this so I hope it's OK to post it here.
I'm very interested in getting supercurio's voodoo sound and ext4 mod on my Nexus S but I don't need/want the overclocked frequencies and other stuff included on most of the kernels out there. You guys know any kernel that I could flash to get those and keep my stock fequencies?
Thanks
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I use overclocked with voodoo and setcpu...you can keep it set to 1000 and not over the stock limit.
Bionix 1.3 is solid and no OC
Sent from my Nexus S using XDA App
nicholasbgr said:
I didn't want to open a new thread just to ask this so I hope it's OK to post it here.
I'm very interested in getting supercurio's voodoo sound and ext4 mod on my Nexus S but I don't need/want the overclocked frequencies and other stuff included on most of the kernels out there. You guys know any kernel that I could flash to get those and keep my stock fequencies?
Thanks
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
If you flash the Trinity max kernel and do not adjust the clock you will have everything your asking for. This kernel boots at stock and has Voodoo and ext4 built in.
icandy75 said:
If you flash the Trinity max kernel and do not adjust the clock you will have everything your asking for. This kernel boots at stock and has Voodoo and ext4 built in.
Click to expand...
Click to collapse
So your saying the trinity max kernel has voodoo built in?
Sent from my bionix nexus s
mrnexus said:
So your saying the trinity max kernel has voodoo built in?
Sent from my bionix nexus s
Click to expand...
Click to collapse
That is exactly what he is saying, yes =)
Thanks guys, I'm gonna take a look at your recommendations as soon as I get some spare time.
Do all the trinitys have voodoo
Sent from my bionix nexus s
mrnexus said:
Do all the trinitys have voodoo
Sent from my bionix nexus s
Click to expand...
Click to collapse
No, only the most recent ones.
kenvan19 said:
No, only the most recent ones.
Click to expand...
Click to collapse
Such as:
Sent from my bionix nexus s
Ok, so i have had a samsung captivate since last summer. I just did the official froyo update the other day and it was successful with kies mini. I then decided to root it using super1click which also worked successfully. I have superuser, titanium backup with busybox installed, and super manager and terminal emulator. I also successfully got clockworkmod flashed and working.
My problem is that ive got the new cognition rom on my internal sd card, but when i try to flash it with cwm, i get the 3e recovery failure message. Ive been reading various sites today on how to fix this problem, but every site seems to tell me something different. I ask this question here, because it seems to be the most knowledgeable site to go to.
How do i get my rooted captivate, with all the above installed and running, to allow me to flash a new rom and possible a new kernal down the road? Im about to go insane trying to decipher through all the info all the different sites have said. Sorry to write such a novel on a tired subject, but im going crazy. Any help will be GREATLY appreciated. Thanks.
trontheman said:
Ok, so i have had a samsung captivate since last summer. I just did the official froyo update the other day and it was successful with kies mini. I then decided to root it using super1click which also worked successfully. I have superuser, titanium backup with busybox installed, and super manager and terminal emulator. I also successfully got clockworkmod flashed and working.
My problem is that ive got the new cognition rom on my internal sd card, but when i try to flash it with cwm, i get the 3e recovery failure message. Ive been reading various sites today on how to fix this problem, but every site seems to tell me something different. I ask this question here, because it seems to be the most knowledgeable site to go to.
How do i get my rooted captivate, with all the above installed and running, to allow me to flash a new rom and possible a new kernal down the road? Im about to go insane trying to decipher through all the info all the different sites have said. Sorry to write such a novel on a tired subject, but im going crazy. Any help will be GREATLY appreciated. Thanks.
Click to expand...
Click to collapse
If you would have done a search here then you would have found that you need to do one of 2 things.
1. Flash back to 2.1
2. Replace the 3e recovery with one that doesnt check for the sig.
I dont know how to replace the 3e recovery. I think ill go with flashing back to 2.1. Once i dl Odin and flash back to 2.1, then i can flash a new rom or a new kernel? Will it undo everything i've done so far? Thanks for the help.
trontheman said:
I dont know how to replace the 3e recovery. I think ill go with flashing back to 2.1. Once i dl Odin and flash back to 2.1, then i can flash a new rom or a new kernel? Will it undo everything i've done so far? Thanks for the help.
Click to expand...
Click to collapse
Here is a link to the replacement recovery.
Make sure you have the right odin and that your 3 button works right.
Yesh doing this will wipe out everything. Make sure to back up. Do not back up system data at all as when you restore it, it can lead to major issues. Once done with a custom rom it will be wiped clean. You will have to redo contacts, email, and all other settings
Thanks. Would it be okay to just flash a new kernel like speedmod kernal and just use the stock rom? Is that possible to do while im on rooted 2.2? I like the rom just fine, i just want it faster mainly. Thanks again.
trontheman said:
Thanks. Would it be okay to just flash a new kernel like speedmod kernal and just use the stock rom? Is that possible to do while im on rooted 2.2? I like the rom just fine, i just want it faster mainly. Thanks again.
Click to expand...
Click to collapse
To be honest I am not sure. I only had the stock on for a few hours as it was just not that great compared to the 2.2.1 rom that I have been used to running. I need BT voice dial and the added exchange options so 2.2 was not really for me. If you want a stock feel but faster then I would go with COG or one of the other roms based on the kb1 rom.
So I've come to the conclusion that I should just flash back to 2.1 and go from there. I have odin downloaded, but I'm not certain how to use it. Do you guys think I should flash a custom rom from stock, or just flash a kernel with lag fix and delete the bloatware? Thanks.
first flash 2.1 stock to get rid of the damn 3e. custom roms dont replace that always. also most custom roms dont flash with odin.
get a stock rom. read the instructions, flash
trontheman said:
So I've come to the conclusion that I should just flash back to 2.1 and go from there. I have odin downloaded, but I'm not certain how to use it. Do you guys think I should flash a custom rom from stock, or just flash a kernel with lag fix and delete the bloatware? Thanks.
Click to expand...
Click to collapse
If you are getting .zip signature errors when trying to flash a rom (because you are using 3e recovery) you will not be able to flash a kernel.
Supercurio did make a KB1 kernel that is installable via Odin. If you install that, you will also get CWM recovery. Then you can flash anything you want.
Either way you will need an Odin program. Either Odin One Click to flash back to stock 2.1 or Odin v1.7 to flash the Supercurio KB1 Kernel .tar file.
trontheman said:
Thanks. Would it be okay to just flash a new kernel like speedmod kernal and just use the stock rom? Is that possible to do while im on rooted 2.2? I like the rom just fine, i just want it faster mainly. Thanks again.
Click to expand...
Click to collapse
Correct me if i'm wrong but I think the speedmod kernal is i9000 based which would cause a major headache/bootloop on the stock rom.
Sent from my SAMSUNG-SGH-I897 using XDA App
Johnnie5000 said:
Correct me if i'm wrong but I think the speedmod kernal is i9000 based which would cause a major headache/bootloop on the stock rom.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
....it works fine on stock 2.2, as does any other 2.2/2.2.1 kernel
Pirateghost said:
....it works fine on stock 2.2, as does any other 2.2/2.2.1 kernel
Click to expand...
Click to collapse
The problem is, the OP has no idea what he's doing. It sounds like he's wanting to flash to 2.1, then add a I9000 kernel. Since he's all over the place, it's hard to decipher what he's thinking.
To the OP. I'd HIGHLY suggest you look for the stickied "how to" video's by Connexxion. They will tell you what you need to do and show you EXACTLY how to do it. Invaluable info for the noobs.
Here is the link your looking for, download the installer zip file at the bottom of the first post. Extract to your fancy, use the install.bat file once extracted. Be sure to have the phone connect to the pc (DO NOT MOUNT) and have USB Debugging on.
Modded 3e recovery that works like 2e
trontheman said:
Ok, so i have had a samsung captivate since last summer. I just did the official froyo update the other day and it was successful with kies mini. I then decided to root it using super1click which also worked successfully. I have superuser, titanium backup with busybox installed, and super manager and terminal emulator. I also successfully got clockworkmod flashed and working.
My problem is that ive got the new cognition rom on my internal sd card, but when i try to flash it with cwm, i get the 3e recovery failure message. Ive been reading various sites today on how to fix this problem, but every site seems to tell me something different. I ask this question here, because it seems to be the most knowledgeable site to go to.
How do i get my rooted captivate, with all the above installed and running, to allow me to flash a new rom and possible a new kernal down the road? Im about to go insane trying to decipher through all the info all the different sites have said. Sorry to write such a novel on a tired subject, but im going crazy. Any help will be GREATLY appreciated. Thanks.
Click to expand...
Click to collapse
I am wanting to flash back to 2.1 and go from there. I have the drivers installed and I have odin downloaded. I tried it last night, but I couldn't get it to work. I got it to download mode, but still nothing. What could the problem be? Thanks.
I tried odin one click again today, but still nothing. All i want to do is flash back to 2.1, root, then flash a rom or custom kernel. Im losing my mind, any more help is greatly appreciated. Thanks.
Bump. Thanks.
trontheman said:
I tried odin one click again today, but still nothing. All i want to do is flash back to 2.1, root, then flash a rom or custom kernel. Im losing my mind, any more help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
ok no need to flash 2.1
get neldars kernel flashing app from the market
get a kernel for froyo without 3e recovery in the dev section. this one is great
http://forum.xda-developers.com/attachment.php?attachmentid=547852&d=1300708475
use neldars app (edit) "sgs kernel flasher" or something to that effect. to flash this kernel
then flash cognition
you can also use odin3 but not the oneclick downloader without the .pit file and flash the same kernel placed in the pda slot.
when you installed keis mini, it installed new WRONG drivers (for odin)
reinstall the original other drivers.
BUT. in your OP all you wanted was to be able to flash COG or something.
ALL you have to do is fix your 3e recovery, SEVERAL people including myself have told you how to fix it. then CWM will work! you dont need a computer to fix 3e if you have root explorer (google it $) .
if you are going to flash a custom rom anyway dont bother going back to 2.1.
if you are going to stay stock, 2.2 is better anyway. (aside from 3e but staying stock dont matter)
you can also use odin3 but not the oneclick downloader without the .pit file and the same kernel placed in the pda slot.
Click to expand...
Click to collapse
@ dani - dude read the thread. odin doesn't recognize his phone.!! try to catch up before butting in...
well that doesn't make my whole post irrelivent. if he is rooted and has busy box he can use neldars kernel flasher. sorry if i over looked something.
Ok, well i got the aio toolbox, and i flashed back to stock. Now im running 2.1-update1. How do i go about rooting now? I cant seem to find a root file. Thanks.
I rooted according the directions found here: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/ after getting a new Nexus S 4G.
Even after locking the bootloader. It goes to the Android-with-box then to the Exclaimation-point-inside triangle. When I volume-up and power-button from that screen, an "Android Recovery <3e>" comes up...
Does anyone know what might be going on? And how do I get my custom recovery to stick?
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
mikeyinid said:
Well, that's my post, so ill try to help. First, and don't take this the wrong way, but did you follow those instructions to a T? When you boot into bootloader, your pushing CWM to you phone with the fastboot command?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Apparently alot of people have this issue, me included. I seen some posts about using root explorer to change the name of the recovery image if it shows up in system /ext. Sounds crazy but I hear it doesn't show up on all phone's. IV come to terms with having to fastboot every time I flash but I'd love to see a fix. Have you tried Amons recovery?
TonyArmstrong said:
No offense taken...it's a valid questions since humans have trouble following directions.
To answer your Q, yes, I followed it to a tee. I'm going to retry now...from scratch. Gonna load the stock imgs and go from the beginning...
Click to expand...
Click to collapse
Have you flashed recovery through Rommanager when your phone boots up?
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
mbh87 said:
You have to flash a non-stock kernel, the recovery gets overwritten on reboot. So if you flash CWM and reboot without flashing a custom kernel you will be back to stock recovery.
Edit: oops maybe I was wrong lol, maybe it isnt the kernel. im assuming you flashed the recovery in fastboot?
Click to expand...
Click to collapse
No, I dont think your wrong bro. It makes sense. Ill test your theory soon.
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
david1171 said:
I've read on some methods for rooting that there is a file /system/etc/install-recovery.sh (or something like that, should be able to find it by mounting system in recovery and adb shell ls /system/etc then using adb shell rm -r /system/etc/install-recovery.sh).
Though after I fastboot flashed the recovery, booted into recovery, did a nandroid, I formatted /system before I flashed CM7, so that would've killed the file anyways.
Click to expand...
Click to collapse
I just had CWM, never had any issues. Im not sure what dictates whether that file is there or not. Im guessing that since tony is so quiet though he got it figured out..
whats amazing is i dont have this script and its one of the things holding the one click up :x
also its part of init.rc so technically a new kernel would.. in theory wipe that out...
mikeyinid said:
Have you flashed recovery through Rommanager when your phone boots up?
Click to expand...
Click to collapse
I did flash CWM through Rom Manager. That didn't work the first few times. It stalled...
mikeyinid said:
Tony, when you push CWM, are you able to boot into recovery by hitting volume down twice to recovery and hitting power? If so, I suggest you flash this ROM. Its stock rooted and you will not have problems with CWM sticking. You dont even have to wipe to flash it...
Click to expand...
Click to collapse
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
TonyArmstrong said:
I got it to stick -- or at least i thought I had it. I followed the initial instructions provided in a previous thread. And per the instructions, I download Rom Manager and I installed CWM through it (again).
I'm going to wipe my phone fully -- reinstall the base 2.3.4 with the the stock recovery, via the IMG files for GRJ22 and start over...See what happens then.
Click to expand...
Click to collapse
Sent from my Nexus S 4G using XDA App
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
mikeyinid said:
Wait, I'm confused. Why would you flash stock images when your already stock? If you follow the instructions in the link you posted in the op there is no reason you shouldn't be rooted. Have you actually even booted into recovery?
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
TonyArmstrong said:
I'm rooted successfully. I feel more comfortable (with recovery acting flaky) with unrooting and starting over from scratch...
Call me kooky, but a bone-stock unrooted phone with no user data, no nothing, is how I got it, so why not return it to that state and start over. That's the only way I know to insure that whatever I do is not influenced by any data, bad file permissions, etc. that could hose rooting and installing recovery.
Click to expand...
Click to collapse
OCD, I know the feeling lol. What got it to stick?
derekwilkinson said:
I realllyyy don't suggest flashing a recovery with rom manager. I'm not bashing ROM Manager, I'm a paid user, but the way that it flashes recoveries is unsafe. I've had it almost brick my Evo and I've seen it brick other phones.
Just use fastboot... if you can't get that working, you probably shouldn't be messing with the phone.
Click to expand...
Click to collapse
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
TonyArmstrong said:
I used fastboot to install CWM initially (fastboot flash recovery recovery-xxxxx.zip -- can't remember the filename right now). The directions for rooting the NS4G state explicitly to use ROM Manager to flash the recovery to "make sure it sticks" after initially pushing it to the phone via fastboot.
It's obviously a hack, but apparently it works more often than it fails.
I'm a paid user of ROM Manager as well. I have to admit, it was fine to flash Amon Ra to my Evo. Since I'm new(er) to the NS4G, I'm going to defer to those with more expertise and follow the directions given.
Click to expand...
Click to collapse
well the "make sure it sticks" flashing with rom manager doesn't make any sense. the only way the recovery would be overwritten is if the ROM you flash over writes it or in fastboot
mikeyinid said:
OCD, I know the feeling lol. What got it to stick?
Click to expand...
Click to collapse
Yeah, I'm very anal when it comes to this kind of stuff...I was a developer for a little bit (Java middleware, then on to the front-end stuff) where regression testing was important. Sometimes, it's best to reload things piece by piece to see what breaks what. Then go from there.
I haven't gotten it to stick yet; gonna get some sleep and start over tomorrow. I used fastboot to push the stock boot, bootloader, system, recovery, and userdata IMGs a moment ago, and the phone is back to bone stock.
Hi, new Android user here.
I was trying to root my Nexus S phone yesterday and I'm having problems. There is a lot of rooting guides out there and I used one from xda and also one from unlockr.com. Managed to root the phone ok (I think), but everytime I flash a custom ROM, the phone won't start at all, it just sits at the boot up screen and repeats itself.
So I'm thinking, I should just start over again. So I flash the stock ROM from xda back to 2.3.1. Everything seems ok, the phone starts up... but it's always stuck on airplane mode and the phone itself doesn't even show stuff like IMEI, mac address anymore.
So now I figure I've probably messed the phone up enough and need help lol. How do I go about reflashing the stock ROM and getting my Nexus back to out of the box condition (Stock ROM and no custom bootloader)?? Any guides or step by step instructions would be very helpful.
Thanks
Did you wipe before flashing roms?
Sent from my Nexus S c",)
Maybe flashing the KB2 modem would help that but the 9020a came stock with 2.3.3 and not 2.3.1 so that could be it...I'm not sure but that software wasn't meant at all for ours so it could be part of the problem. But if I was you I'd take a look at this thread wich has all the stock software for your phone. Make sure you wipe everything in clockework and then flash the stock rom. http://forum.xda-developers.com/showpost.php?p=13123996&postcount=39
dsixda uploaded the stock backup and the stock recovery, you can read more at that link, good luck hope it helps
You can download the full stock ROM from the link below:
http://goo.gl/8P8vl
Move the zip file to sdcard. Boot into recovery and flash the ROM. It should get you back to stock 2.3.4 ROM, all locked.
jungbum said:
You can download the full stock ROM from the link below:
Move the zip file to sdcard. Boot into recovery and flash the ROM. It should get you back to stock 2.3.4 ROM, all locked.
Click to expand...
Click to collapse
that did the trick. thanks everyone, now time to try rooting and flashing ROM again!
hrm lol now trying to update it to 2.3.4, it downloaded the update, but on reboot i get the white triangle with ! in it :\
this phone is so messed now
edit: well now everything is ok again, wiped data, flashed with CM7 and now it says 2.3.4, go figure.
Ok guys so I have managed to root my i9023 and flash clockwork recovery which was all good, I set about flashing some new roms via rom manager, again, all good.
So now I settle on this cm7 based rom which I love, used anim mod to get some nice transitions, then I used font changer.
All was good, then I decided that the font I was using was a bit ott so I decided to change it again, upon reboot it starts boot looping, bollocks !!!
So I try to get into clockwork recovery, and it seems to have gone back to the stock bootloader, grrrrr
I re flash clockwork, wipe / clear etc... then flash the rom again, but it would not flash, so I went to my backup of stock n flashed that, all good.
I then install rom manager again and flash the rom I liked again, this time no problem, but when it loads up the home button and search button are not working
So i decide on a factory reset, I select wipe everything including sd just to be sure but it comes up "error null"???
So now I wipe the sd manually and then do the reset and it works, ok, I re load everything on from scratch and all is good, but when I installed rom manager it says that clockwork recovery IS NOT installed again
Can anyone here work out from my ramblings WTF is going on???
I dont get why the font changer all of a sudden caused a boot loop, as I had changed font about 15 times with it without issue, also why clockwork recovery will not stick anymore after a reboot, when before it did and I have not changed a thing!
Cheers!!!
Rename install-recovery.sh in system/etc to something else, flash cwm recovery again, this time it'll stick until you install a stock rom again.
Rom manager is causing more problems than it's saving time, hence I don't use it.
Sent from my Nexus S using XDA App
Thanks for the reply, can you go into detail on what exactly I need to do to get clockwork to stick? I still hold noob status!
Thanks!
Also rom manager seems fine, I flashed loads of roms with it with no issue, I also rebooted a few time at least between flashes so I dont get why clockwork suddenly decided to jump ship.
It was the font changer that f&%ked it all up for me, or anim mod (which I wont touch now even tho I miss the wicked transitions).
When using Font Changer, it's better to do a reboot manually instead of selecting Reboot from within the program. That sometimes cause me a boot loop too. But after turning the phone off / on a.k.a. "reboot manually", the phone boots fine.
To elaborate what rentaric said, use Root Explorer and go to /system/etc/, there should be a file named install-recovery.sh. This file is responsible for flashing the stock recovery every time the phone boots. If you rename it to something else e.g. install-recovery.sh.bak then CWM will stick on reboot.
Thanks, but when I get into the /system/etc/ there is not file called install-recovery.sh.
The only .sh in there is init.goldfish.sh
Any ideas???
bump...............
Flash cwm rec and either stock or custom rom.
Stock rom incl the .sh you want.
Sent from my Nexus S using XDA App
I've read on these forums that using Clockwork on the I9023 is a no-go. Serves up incompatible ROMs, etc.
BTW, I'm looking to root my I9023. Can the OP please point me to the method he used.
athani said:
I've read on these forums that using Clockwork on the I9023 is a no-go. Serves up incompatible ROMs, etc.
BTW, I'm looking to root my I9023. Can the OP please point me to the method he used.
Click to expand...
Click to collapse
LINK: http://forum.xda-developers.com/showthread.php?t=1007782
Please read the whole thread, if I had it would have saved me half a night scratching my head...lol
rentaric said:
Flash cwm rec and either stock or custom rom.
Stock rom incl the .sh you want.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yeah I have a custom rom installed, supercm7, but the install-recovery.sh. that I have been told is causing the problem of clockwork disappearing is not in the /system/etc/ folder, so I am asking if there is anything else that could be causing me to have to re flash clockwork via my pc every time I want to change rom?
I will tell you exactly what happens.
1. I go into rom manager
2. download a rom and choose flash rom from sd card
3. it asked if I want to wipe etc, i select yes
4. phone re boots and I get ! with an android
5. I pull the battery, hold volume up n power and boot / connect to my pc
6. re flash clockwork via SDK
7.the phone then load the new rom on its own
Before it would just flash the rom without me having to install clockwork again.
install-recovery.sh is only there if you're using a stock android rom.
"so I am asking if there is anything else that could be causing me to have to re flash clockwork via my pc every time I want to change rom?"
ROM Manager.
It's not a reliable working tool for ME as I'm changing ROMs/kernels on a regular basis and it might not work reliable the one time you need it.
Thanks for that, I may just sack rom manager then.
Its a shame as I flashed several roms with it without issue.
Oh well, loving this supercm7 so gonna stick with it untill an update comes out.
Many thanks to all who have replied, clicking the thanks buttons now!
I had the same problem but i installed a previus recovery and works fine formeforme
Sent from my Nexus S 4G using XDA Premium App