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
Related
Never had this problem on any other phone...
I have my 4G rooted and have adb'ed Clockwork onto it, flashed a new kernal, etc...
the problem i am having is that Clockwork seems to vanish when I try to boot into recovery. If i use ADB and reflash i get it to work, but on the next reboot, I am back to stock android recovery...
Am I doing something wrong that my phone will only run a custom recovery when "tethered"?
My root access is still active...just i have to reflash Clockwork every time i want to flash something or backup.
I am completely confused...
this hasnt happened on any of my nexus s 4g's but it does. there is a way to fix it, im looking for the link now as Ive read it a million times.
if someone doesnt post by the time i find it, ill link it.
Quote: obsanity says:: One other important addition to this, if you wish to run stock ROM rooted, is that you must rename this file after flashing recovery:
/system/etc/install-recovery.sh
Stock ROM flashes the stock recovery back to original during bootup if that script runs and detects that recovery has changed.
Thanks to Netarchy over @ XDA for this important tip.
pulled the above post from here: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/
good luck
edit: I used this post: http://forum.xda-developers.com/showthread.php?t=1071500
and this guide: http://forum.xda-developers.com/showthread.php?t=935819
tailsthecat3 said:
Quote: obsanity says:: One other important addition to this, if you wish to run stock ROM rooted, is that you must rename this file after flashing recovery:
/system/etc/install-recovery.sh
Stock ROM flashes the stock recovery back to original during bootup if that script runs and detects that recovery has changed.
Thanks to Netarchy over @ XDA for this important tip.
pulled this post from here: http://www.droidfiles.us/nexus-s-4g/root-nexus-s-4g/
good luck
Click to expand...
Click to collapse
Duh...thanks! I would never have thought of that! Thanks for your help! Just noticed a lack of "Thanks" buttons on this board...Used to the Epic board and always clicking a thumbs up.
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.
If I am using this forum improperly or asking too many questions on one thread that don't fit together, please inform me kindly.
Stock on 2.3.4 hboot 1.18 I rooted with revolutionary, and installed teamwin recovery. I am using the newest CM7 from the rootzwiki I believe. This is what I flashed anyway - update-cm-7.1.0-SelfKANG10-Sensation-signed.zip. Now I am 2.3.7 kernel ver 2.6.35.13_CyanogenMod+ [email protected] #1
ROM Manager app is now on my phone, but it says I need Clockwork recovery to use it. I also read through google and forums that just flashing between ROMs you have to have like same kernels and stuff like that, which I am very noob too.
I'm having Google framework FC issues and no GPS on CM7.
I think I want to switch from CM7 to this MIUI zip I got at MIUI.us - MIUI.us_pyramid_1.12.9.01_Eng_Deo_ZipA_Signed.zip
Which recovery SHOULD I be using? If clockwork is way to go, can I just go to my ROM manager app where it says, "flash Clockwork to this phone"?
If I want to change ROMs, what do I need and NOT need to backup? What exactly is "nandroid" back up, is it better than backup apps? Do I need to backup ROMs, and what exactly is that and what is proper way?
Do I have to wipe then restore everytime? Had some issues with this first time from stock sense to CM7, couldn't get Titanium or mybackup pro to restore my apps, and my contacts are quadrupled in size and organized oddly.
What is the best way to switch ROMs, flashing, ROM Manager, something else?
IF I wanted to run only one ROM for lets say 6 months, after I flash it, can I delete that zip from sd card, and phone will still work?
Suggest a ROM for me if you like also
_DavidWebb said:
If I am using this forum improperly or asking too many questions on one thread that don't fit together, please inform me kindly.
Stock on 2.3.4 hboot 1.18 I rooted with revolutionary, and installed teamwin recovery. I am using the newest CM7 from the rootzwiki I believe. This is what I flashed anyway - update-cm-7.1.0-SelfKANG10-Sensation-signed.zip. Now I am 2.3.7 kernel ver 2.6.35.13_CyanogenMod+ [email protected] #1
Click to expand...
Click to collapse
So standard CM7, use the CM7 thread here on XDA as the reference.
ROM Manager app is now on my phone, but it says I need Clockwork recovery to use it. I also read through google and forums that just flashing between ROMs you have to have like same kernels and stuff like that, which I am very noob too.
Click to expand...
Click to collapse
I personally don't use ROM Manager but use ClockworkMod alot. There is a thread here on CWM 5.0.2.0 somewhere, if I remember I'll add it.
Kernels need to be Compatible with the ROM. This compatibility requitement is in terms of Kernel revision (i.e. old Kernel might not work with a newer ROM). More importantly though there are two basic typed of ROM on the Sensation, namely Sense and AOSP based ones. These two varieties have completely different Kernels so you will need one from that branch. For example Faux makes two Kernel types AOSP (e.g. for CM7 and MIUI) and all the Sense derivatives.
I'm having Google framework FC issues and no GPS on CM7.
I think I want to switch from CM7 to this MIUI zip I got at MIUI.us - MIUI.us_pyramid_1.12.9.01_Eng_Deo_ZipA_Signed.zip
Which recovery SHOULD I be using? If clockwork is way to go, can I just go to my ROM manager app where it says, "flash Clockwork to this phone"?
Click to expand...
Click to collapse
I'd just install CWM directly from the PG58IMG.zip file, but as I said I don't use ROM Manager.
If I want to change ROMs, what do I need and NOT need to backup? What exactly is "nandroid" back up, is it better than backup apps? Do I need to backup ROMs, and what exactly is that and what is proper way?
Click to expand...
Click to collapse
The Nandroid backup performs a backup of the various phone partitions onto the SD-Card. This allows for a point in time backup and recovery of the phone.
ALWAYS do a Nandroid backup before playing with a new ROM or Kernel, JUST IN CASE **** happens.
Do I have to wipe then restore everytime? Had some issues with this first time from stock sense to CM7, couldn't get Titanium or mybackup pro to restore my apps, and my contacts are quadrupled in size and organized oddly.
Click to expand...
Click to collapse
Never had this issue with contacts, I keep all mine synced with gmail. New ROM and they automatically update. I don't often use TB, others can probaby advise.
What is the best way to switch ROMs, flashing, ROM Manager, something else?
Click to expand...
Click to collapse
I manually install the ROM Zip from CWM then wipe cache, Dalvik Cache and Fix permissions, YMMV.
IF I wanted to run only one ROM for lets say 6 months, after I flash it, can I delete that zip from sd card, and phone will still work?
Click to expand...
Click to collapse
Yes
Suggest a ROM for me if you like also
Click to expand...
Click to collapse
Depends if you want a Sense or ASOP based phone.
Ok ill try to hit all the points for you. First you can use any recovery you like (cwm, twrp, 4ext) but Rom manager will only work with cwm. You can get to your recovery 2 ways, either hold the power button and select reboot then recovery (note some roms don't have this) second power off your phone completely and hold vol down and power until you get to hboot and select recovery (note fastboot must be turned off in settings). Personally I don't recommend using Rom manager to flash your roms go to the recovery itself.
Flashing roms: it is recommended to wipe data wipe cache and wipe dalvik cache (its sometimes found under advanced like in cwm) and when you get that part down it isn't always neccesary but wipe system partition... Never ever wipe anything else... Unless your cleaning your battery stats but let's stick to the basics.
If you are just flashing an update to a Rom sometimes you don't have to wipe anything (i.e. cm7 v9 flashing to cm7 v10) but anytime you change Rom bases always wipe. Especially if you are going from cm7 to a sense 3 Rom and also sense 3.5 and vice versa. Also there are several superwipe files from several devs. I suggest using one of these. All you do is flash it like a Rom in recovery. They automatically wipe for you.
Kernels are labeled with the base you need I.e cm7 or sense review the kernels threads for more info.
Next, if you haven't wiped and tried a couple Roms that explains the contact problems and GPS issues.
A nandroid put simply is just a backup of your current Rom. Go to backup in your recovery and backup your current Rom. Is saves every little bit of your current Rom. You need to do this in case something goes wrong or if you don't like the new one. Then you can simply restore it if you need to.
After you flash a Rom it is in your phones memory. You can delete it off your sdcard no problems, unless you want to flash it again at another time. You can also delete old nandroids if you need to just keep at least the last one you made. They are large sometimes.
I have used about every Rom here I suggest mikes hdrevolution or cdtdroids Roms if you don't want cm7 (which is often referred to as aosp) if you want to try another aosp Rom try hypersensation it works good too.
And you used this forum perfectly asking questions in the q&a good job some people don't get that.
Edit: he beat me to the answers while I was typing lol. Also I hate autocorrect had to clean up my post hope it didn't confuse you.
Sent from my HTC Sensation XE with Beats Audio using xda premium
gol_n_dal;20335770
The Nandroid backup performs a backup of the various phone partitions onto the SD-Card. This allows for a point in time backup and recovery of the phone.
ALWAYS do a Nandroid backup before playing with a new ROM or Kernel said:
I also can't get the multi quote to work like you did, how does that work lol?
Click to expand...
Click to collapse
Ok, this forum is awesome, and I will defintely check out the other forums for kernels and other topics. I am understanding most of your replies, but as you see I get other questions from some answers lol. I did just wipe everything(data factory reset) again, and installed the MIUI and when I signed in my google on setup, all my apps started downloading from market and my contacts were all there in a little bit better fashion than before. Also, when I put CM7 that was my FIRST ROM and immediately after my FIRST time attempting and successfully doing a root s-off. Now MIUI makes my 2nd ROM. I'm sure if I hang around here enough I'll get the hang of it all and start to figure it all out better. I vultured around these forums for 4 months with a stock phone before I did anything, and my phone isn't bricked so I'm happy about that.
For some more detail try checking out the stickies in the development section there are some awesome guides and answers there too.
Sent from my HTC Sensation XE with Beats Audio using xda premium
Hi xda. I just installed (flashed) cyanogenmod 9 on my nexus s, after getting bored with the stock kernel so I flashed trinity ics kernel. Now when I try and flash a new kernel nothing changes, cwm recovery said it flashed successfully. The procedure I did when I installed it was:
1) install zip from SD card
2) choose zip
3) yes
4) reboot system
Is there anything I did wrong? Do i need to clean the cache and dalvik cache?
Sent from my Nexus S using xda premium
How are confirming that it did not flash?
Clockwork recovery said it was successfully installed. Also the version of the kernels are right for my rom (ics)
Sent from my Nexus S using xda premium
You missed understood me.
How are you checking/confirming that the kernels you flashed after trinity are not actually flashing/ booting/being used or how ever you want to phrase it?
cm changed their ramdisk(again). so now custom kernels without cm ramdisk wont boot cm. as always, cm likes to "break" things. complain to cm. i recommend other non cm based roms, like rasbean jelly. it doesnt have as much junk included and is a faster/smoother experience than cm. many kernel developers arent willing to cater to cm anymore because of these changes they constantly make. enough is enough.
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
maybe so, bit i dont see a mention of a boot animation
---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------
albundy2010 said:
Im with you Simms but I think this one is a case of him seeing the boot animation of Trinity and thinking it is still the kernel.
Click to expand...
Click to collapse
ah, ok. i reread the op very slowly.
op, did you check the kernel version in your about phone? other kernels wont get rid of the boot animation unless they offer a boot animation or include a script to delete it.
Yeah. But he is saying he doesn't see a change. Implying the phone boots up as it did prior.
He is also on cm9 , not the new cm10 that botched things up again.
That is why I am trying to get him to confirm how he is checking if the kernel changed. Almost certain its the op just seeing the boot animation and thinking that it didn't change due to that.
Op. Go to settings /about phone and look at kernel version. Flash a different kernel again. Check again.
I am confirming that it did not flash by going to settings and then about phone. In kernel it still says Trinity kernel rather that matrix kernel or air kernel (2 roms I've tried flashing).
Sent from my Nexus S using xda premium
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
[/QUOTE]
albundy2010 said:
Strange. What recovery and version of it are you using? If its a older cwm with a updated version or a different recovery altogether.
You can boot the different recovery with fastboot boot recovery name of.img and flash without loosing your current one
Click to expand...
Click to collapse
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
I am using Clockworkmod Recovery version 6.0.1.0. Would you suggest flashing a new rom, I am considering that as a last resort. Also I am fairly new to rooting and things like that so I do not know a great deal about ramdisks etc.[/QUOTE]
albundy2010 said:
I would try to flash a kernel with twrp first. I am not a fan of cwm recovery myself and don't trust it.
If that's a no go. Try a different ICS ROM if that's what you want. Or jb etc.
Still find it odd that recovery says it flashes but it doesn't. Usually as Simms was saying the phone doesn't boot with strange kernel behavior/ incompatibility. Honestly not sure what exactly what is causing it. So just use process of elimination to try and sort it out.
Maybe Simms knows of or heard of this type of behavior before and can provide some info.
Click to expand...
Click to collapse
Ok ll try that
You can flash my cm compatible kernel.
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
p1gp3n said:
Make a backup of your current setup in cwm recovery. Then format /boot under mounts and storage to wipe your current kernel. Then flash new kernel and reboot. Even if this gives you an issue, you have a current backup that can be restored.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I gave up and flash a new rom and kernel thanks for the help.
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
t1op said:
I brought my phone to stock. Installed a rom. Fine. Went back into CWM recovery. Every time I reboot the phone (power button or in recovery) it returns to recovery.
I brought my phone back to stock again. Installed another rom. Went back to TWRP. Again, I can't reboot the system, only return to recovery.
Is there a way to fix this, or can I never use recovery after installing a rom?
{I'm sure this question has probably been asked before, but I've been searching for hours and can't find a fix.)
Click to expand...
Click to collapse
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
WayTooGosu said:
This would occur for me when I had installed an incompatiable kernel with the ROM I am trying to install. I would fix this problem by either looking at the thread for a compatiable kernel if it does not come with one, or if it is an ICS ROM, Team Acid's ICS Kernel works fine. I think Team Acid's ICS kernel is included in their unofficial AOKP release if you have that downloaded. I hoped this help!
Click to expand...
Click to collapse
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
lumin30 said:
All of our ROM's have kernels. It is the kernel you flash from that makes a difference. And once you flash the ROM, the kernel that is packaged with the ROM replaces the kernel you previously had/flashed from. However, the OP of the ROM's usually specify what you need to do to flash the ROM.
Click to expand...
Click to collapse
Ah I see. But my point was that some ROMs state that the user must be on an ICS ROM/Kernel to flash this. I guess I wasn't very clear as I am new here and lack understanding.
champ1919 said:
Did you wipe data & caches? What did you flash and how? Cwm, heimdall or Odin? Sgh-t959v under battery?
Find lumin30's guides. They/he will steer you straight.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
I used Odin to return to stock. I used Super One Click to root. I used root explorer modify the recovery to allow me to boot into "CWM final for Froyo". That much each and every time.
The first time I installed
[TFQ - 30/12/2012]X.A.O.K[Kanged - Xperia Style]
That is an ICS rom. Installed fine with a new CWM.
The second time I installed the same.
The third time I installed
ROM-MTD-TWRP-ICS-4.x-Audiophile
That is another ICS rom. Installed fine with TWRP.
Each and every time, when returning to recovery to flash more, I got stuck. I can't boot to anything except recovery.
My brother suggested that the problem is using the Volume up and down and power button ("three finger salute") to return to recovery instead of from OS power down menu.
For a fourth time I started over again. Now, using the reboot>recovery, everything works fine.
One thing, you need to have ginger bread bootloaders. So, when you say Odin back to stock, are you referring to kj6?
You could cut down some of the work by using Odin to flash a kernel with recovery & root in it. Antonx & drhonk both have kernels that will do that with odin.
I flash bhundven's cm9 Rom before jumping to any of the others(and wipe between). I believe some of the Rom authors have that in their instructions.
Sent from my SGH-T959V using xda app-developers app
Yeah... GB bootloaders, not Froyo. Your return to stock should be a return to GB stock, not Froyo... and your return to stock can be a return to a rooted stock. If you want to make your life less painful.
It's about MTD to BML, not really about the base version. You just don't want to wipe out what allows later stuff to actually work properly...
Thanks for the advice. I haven't used custom roms very much. Trying to figure out which ones to choose was difficult. I started on stock Gingerbread, but everything I encountered in searching indicated that I needed to go back to Froyo to get CWM then go from there. ...Perhaps I kept running into very old instructions? In any case, should I need to go back to stock again some day, I'll try to figure out which GB roms I could use, including root and custom recovery.
I guess the solution to my problem is: 1) flash back to Froyo or Gingerbread; 2) after flashing an ICS+ rom, only go to recovery from OS reboot menu (never "three finger salute").
I'm actually surprised that people don't run into this problem more often, enough to create a sticky about it. I'm sure I'd still be pulling my hair out if my brother hadn't run into the problem on his Fascinate a year ago.
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Theraze said:
On mine, the 3 finger boot to recovery works fine. Then again, I haven't been on Froyo since Samsung and TMo said to stop using Froyo back in November (October?) 2011 with the official 2.3.6 update. And the only boot-loops I have, whether recovery is booted through the menu or salute, are when I flash something invalid.
Click to expand...
Click to collapse
Interesting... Perhaps if I went back to a gingerbread stock then upgraded to ICS the problem wouldn't occur?
I'll have to try that the next time I might need to return to stock.
Hello,
First I just want to say thank you to the mods for running a great forum and to the devs for keeping this device current.
I just struggled over a period of days with this issue.
The end result being, that you need to go to CM9 BEFORE you try JellyBean or later!
Just hope this helps someone else who missed that instruction.
Thanks devs/mods/everyone for keeping this device alive!!!! :good::good::good:
*EDIT* correction... i THINK you need to go CM9 Before trying something else
Not all ICS ROMs require CM9, but you must have at least CWM5 recovery to be able to flash CM9 or these ROMs. Follow ROMs' OP instructions.
I personally tested HebMIUI flash over Stock GB with CWM5 (Basic with a twist kernel) without going through CM9.