Database Info

returning to stock kernel

So a couple of quick questions.
One (and im asking this because including my og droid i haven't not been rooted in two years) if i return to stock (i.e verizon may replace my tbolt) will it also automatically return my kernel to stock. The only reason i ask is i just did a full data and cache wipe for a new rom and my new adrenaline kernel was still there, which is fine for now but not if i have to take it in.
Second: if it doesnt return to a stock kernel is there a boot.img or even a .zip that will work on clockwork for it.
I did try searching, and i do know how to unroot, I just dont know about the kernel issue once i do unroot.
edit: i did do my own full root, bloatware removed, stock kernel backup before i flashed the kernel, so as long as restoring that backup reverts it to the original kernel that is fine also.

if you use a RUU to return to stock....everything is back to stock including the kernel

magneticzero said:
if you use a RUU to return to stock....everything is back to stock including the kernel
Click to expand...
Click to collapse
thanks i figured that was the case just wanted to make sure.
question answered: so unless someone needs help with this have a good one.

http://forum.xda-developers.com/showthread.php?t=975888
if you use that RUU(out of the box state rom) it will remove root and return everything back to 'normal' so you could return/warranty exchange it

magneticzero said:
http://forum.xda-developers.com/showthread.php?t=975888
if you use that RUU(out of the box state rom) it will remove root and return everything back to 'normal' so you could return/warranty exchange it
Click to expand...
Click to collapse
yeah i found the unroot instructions here http://forum.xda-developers.com/showthread.php?t=1009423 if anyone else needs them and it has the link to the ruu. I just wanted to make sure it did return it. so all is good.

For what it's worth, my son returned a rooted Droid running CM7 because it had a bad camera, he did a mail exchange and never heard a word about it from Verizon. I'm sure the first thing they do with a returned phone is burn a stock image into it even before they "test" it. Think about it, they can't possibly have someone do a forensic examination of the software on returned phones. I think the main way they have of finding modded phones are due to people admitting that they modded it. Just sayin'.

If you make a backup in CWR (Rom Manager) before flashing a new kernel then you can roll back and restore the old configuration... including kernel.
You can also flash the stock kernel from Rom Manager.
No need to RUU unless it is absolutely needed. But this will cause a lot of extra work (need to re-root, etc)

bmcclure937 said:
If you make a backup in CWR (Rom Manager) before flashing a new kernel then you can roll back and restore the old configuration... including kernel.
You can also flash the stock kernel from Rom Manager.
No need to RUU unless it is absolutely needed. But this will cause a lot of extra work (need to re-root, etc)
Click to expand...
Click to collapse
Yea but the OP wanted to know in case they had to return/exchange the phone for whatever reason....

Any way to get a copy of the stock kernal only. Would just like to have it around. Im rooted and running the stock rom with the phone and Adrynalynes 1.9 kernal...
Thanks in advance

magneticzero said:
Yea but the OP wanted to know in case they had to return/exchange the phone for whatever reason....
Click to expand...
Click to collapse
Ah. My bad... then RUU would be the best method!

Jrocker23 said:
Any way to get a copy of the stock kernal only. Would just like to have it around. Im rooted and running the stock rom with the phone and Adrynalynes 1.9 kernal...
Thanks in advance
Click to expand...
Click to collapse
bump? also looking to go back to stock kernel, without unrooting...

[Q] To root or not to root..

..that is the question
I just bought a brand new Nexus S (cheaply compared to other phones of this caliber), and I'm really loving the the speed, stock Gingerbread and basically everything about it.
This is my first Android phone, but previously I used a Nook Color (rooted it myself) with CM7 so I'm also familiar with Cyanogen team's work.
I have been using it only for a few days and considering to root it, but here's what's stopping me:
- Google's ICS update (any estimates when it will hit the Nexus S?)
- warranty (any way to save to stock ROM and return it if I need to send the phone?
- bricking?
So I'm asking you guys who are using your Nexus S' for awhile:
- are there any special options in the CM7 for the Nexus S?
- what specific features are in CM7 that are missing from stock Gingerbread?
- which kernels do you guys suggest (with what major features)?
Regarding rooting and warranty:
- can I somehow unroot my Nexus S later on, when the ICS OTA update is available
- possibility of bricking? How high is it? I'm never had to do some ADB stuff so far, so as I see this won't be exactly just a walk in the park...
I know I bombed this post with questions but basically all I want to know from you guys: is it worth rooting, what are the advantages of rooting (beside the obvious one - having a root access for some apps that needs it) and most importantly what is "fixed" and tweaked in various kernels for the Nexus S?
Thanks in advance,
Atila

atirage said:
..that is the question
I just bought a new Nexus S (cheaply compared to other phones of that caliber), and I'm really loving the the speed, stock Gingerbread and basicly everything about it.
This is my first Android phone, but previously I used a Nook Color (rooted it myself) with CM7 so I'm also familiar with Cyanogen team's work.
I have been using it only for a few days and considering to root it, but here's what stopping me:
- Google's ICS update (any estimates when it will hit the Nexus S?)
- Warranty (any way to save to stock ROM and return it if I need to send the phone?
Click to expand...
Click to collapse
If you only unlock, flash CWM and flash the SU binary you will have root access and OTAs will still work fine.
Unlike the Nexus One unlocking the boot loader on the Nexus S does not automatically void the warranty. The language has changed to *may* void the warranty.
To save the stock rom, install CWM and make a nandroid backup. Flash that back, reboot and let install-recovery.sh restore the stock recovery and you're back in stock business.
atirage said:
Regarding rooting and warranty:
- can I somehow unroot my Nexus S later on, when the ICS ota update is due
- possibility of bricking? How high it is? I'm never had to do some ADB stuff so far, so as I see this wont be exactly a walk in the park..
Click to expand...
Click to collapse
- Restore nandroid to go back to stock, fastboot oem lock to relock the boot loader
- Possibility of bricking is insanely low. Essentially don't pull the battery during a radio flash (if you are updating the radio) and don't flash a CDMA radio to your GSM device. Other than that it's going to be near impossible to really brick it (in the sense that you can't recover it using recovery or fastboot).

krohnjw said:
If you only unlock, flash CWM and flash the SU binary you will have root access and OTAs will still work fine.
Unlike the Nexus One unlocking the boot loader on the Nexus S does not automatically void the warranty. The language has changed to *may* void the warranty.
To save the stock rom, install CWM and make a nandroid backup. Flash that back, reboot and let install-recovery.sh restore the stock recovery and you're back in stock business.
- Restore nandroid to go back to stock, fastboot oem lock to relock the boot loader
- Possibility of bricking is insanely low. Essentially don't pull the battery during a radio flash (if you are updating the radio) and don't flash a CDMA radio to your GSM device. Other than that it's going to be near impossible to really brick it (in the sense that you can't recover it using recovery or fastboot).
Click to expand...
Click to collapse
quick question how can you still receive OTAs after installing CWR because you essentially replaced the recovery, I was told that once you mod the recovery OTAs won't work. When 2.3.6 was launched I never received it until I went back to stock completely. Please help

anishs said:
quick question how can you still receive OTAs after installing CWR because you essentially replaced the recovery, I was told that once you mod the recovery OTAs won't work. When 2.3.6 was launched I never received it until I went back to stock completely. Please help
Click to expand...
Click to collapse
You were told incorrectly. I've flashed plenty of OTA's over CWM on both the Nexus One and the Nexus S. There is no assert done on the recovery in the OTA update script, it merely erases it and flashes a full recovery image over it.
Receiving the OTA has NOTHING to do with the status of your system (rooted, not rooted, custom recovery, locked/unlocked). Your device periodically checks to see if there are updates, if your IMEI / ESN is flagged for an update and you are running a previous build (based on build fingerprint) you'll get the notification to download the OTA.

oh wow alright thanks a lot!

@anishs: OTA update is basically downloading an update.zip which the stock recovery later flashes into the stock rom.
When rooted, you will probably have to tell CWM to flash the update.zip you just received from Google via OTA.
Please correct me if I'm wrong (@krohnjw).
@krohmjw: Thanks a lot for your answers, cleared up bunch of things for me, most of all the fear from bricking.
So could you please tell me some improvements done in CM7 compared the stock rom? (I didn't follow it's development and now I wouldn't know where/how to search for this.)
And the same question regarding the kernels available on XDA - do they improve speed or battery life or anything in particular you'd highlight as a new/better feature?
And regarding kernels: is a stock ROM + custom kernel (flashed by CWM) possible?
Thanks in advance,
Atila
PS: You said you also have a Nexus One, do you remember how long it received the Gingerbread update (and how was that done) after they started rolling out the Nexus S in December last year?
Was the community faster with the update then el Goog?

I wouldn't rely on the word "may" in regards to warranty. They'll argue and say "just unlocking won't void warranty, but further actions that require an unlocked bootloader will".

rentaric said:
I wouldn't rely on the word "may" in regards to warranty. They'll argue and say "just unlocking won't void warranty, but further actions that require an unlocked bootloader will".
Click to expand...
Click to collapse
Honestly, I wouldn't worry about it. I sent in an unlocked Nexus One that was damaged in a car accident - repaired under warranty for no charge. If it's a clear hardware defect you're fine, if you burn our your LED or toast your speaker then they may give you grief.

atirage said:
@anishs: OTA update is basically downloading an update.zip which the stock recovery later flashes into the stock rom.
When rooted, you will probably have to tell CWM to flash the update.zip you just received from Google via OTA.
Please correct me if I'm wrong (@krohnjw).
Click to expand...
Click to collapse
Correct
atirage said:
@krohmjw: Thanks a lot for your answers, cleared up bunch of things for me, most of all the fear from bricking.
Click to expand...
Click to collapse
It's really difficult to "brick" in the traditional sense.
atirage said:
So could you please tell me some improvements done in CM7 compared the stock rom? (I didn't follow it's development and now I wouldn't know where/how to search for this.)
And the same question regarding the kernels available on XDA - do they improve speed or battery life or anything in particular you'd highlight as a new/better feature?
Click to expand...
Click to collapse
I don't use CM7 or any non standard kernel any longer - too many stability issues early on and stock AOSP runs fine. Someone else will need to chime in here.
atirage said:
And regarding kernels: is a stock ROM + custom kernel (flashed by CWM) possible?
Click to expand...
Click to collapse
Yes - this will modify the boot partition though, so OTAs that assert boot to patch it will fail.
atirage said:
PS: You said you also have a Nexus One, do you remember how long it received the Gingerbread update (and how was that done) after they started rolling out the Nexus S in December last year?
Was the community faster with the update then el Goog?
Click to expand...
Click to collapse
The OTA didn't come out until last Feb if memory serves correctly. AOSP Gingerbread roms were being built for the Nexus One in December though.

Thank you again for all your answers
Can somebody explain to me what are the improvements in CM7 and a stable kernel over the stock ones?

Which rom and kernel combo is super stable for everyday use and have some major improvements/features compared to the stock rom?
Anyone can make some good points to root the phone?

atirage said:
Which rom and kernel combo is super stable for everyday use and have some major improvements/features compared to the stock rom?
Anyone can make some good points to root the phone?
Click to expand...
Click to collapse
A lot..just read at nexus S development..
If you want to safe..
flash CM 7.1/brainmaster MIUI/Formel MIUI/Pete Alfonso/Oxygen 2.3
kernel matrix V8, TEUV,TUV stable

I am personally holding out till ICS is released.

My conclusion...
borrowedchief said:
I am personally holding out till ICS is released.
Click to expand...
Click to collapse
After several days of research, that's the conclusion I got too.
It's all nice what I can do with a rooted device and an unlocked bootloader, but on the other hand the unrooted device is also very customizable and powerful.
The stock rom/kernel works fast and stable, so why risk it?
And the faster ICS official update (earlier then on any other device) is the main reason I bought this phone...
PS. Although I think we won't see an official ICS OTA update before 2-3 months after it's premier (which is next week). Most probably the XDA developers will make an ICS rom much, much sooner and we gonna end up unlocking/rooting our devices anyways.

[Q] I must be doing it wrong. Is there an easier way to get back to stock?

Hey, guys-
I'm unrooted and running stock Android. I have all of my settings and apps exactly how I like them right now.
In the past, I've flashed different ROMs and Kernels. When I get tired/frustrated with them and want to revert back to stock, I usually just do the 1 click revert back to factory settings. When you do that, it... well.. erases anything and everything in order to get back to factory settings.
Nothing is broke. I just don't want to delete my SD card contents and lose root. I just want to revert to the stock kernel and ROM from another ROM and kernel.
I was wondering if there's an easier way to get back to my current settings on the stock Android and Kernels WITHOUT using the 1 click revert back to factory method? If there is, could you PLEASE tell me how to do it EXACTLY? I say that because sometimes people on here give instructions that are clear as mud. Thanks!

Factory reset does NOT restore kernels or roms. It simply wipes user data.
You're confused. What you really want is a nandroid back up

If you have ROM Manager installed, open it up and go to "Download ROM". At the very bottom of the list, there should be a selection that says "Stock Images". I'm pretty sure you can use that to get back to stock. I'M NOT POSITIVE, I've never tried it before. It may unroot your phone/get rid of clockwork mod recovery. Just a suggestion

Remember to fastboot OEM lock
Sent from my HD2 using Tapatalk

shockem said:
Remember to fastboot OEM lock
Sent from my HD2 using Tapatalk
Click to expand...
Click to collapse
Ummm... what?

DangerZone1223 said:
Ummm... what?
Click to expand...
Click to collapse
That is to relock your bootloader. Just flash a stock rom in recovery with a full wipe, You'll be unrooted.
Stock roms can be found here.
http://forum.xda-developers.com/showthread.php?t=1063664

It's also wise to keep your content copied on a folder on your comp. 5 minutes of copying back and you got it all back. If you got all that sorted what you should always do is once you've got a stock rooted rom, run a nandroid backup/backup restore from CWM before you flash new roms / kernels.

People posting all this trash.
Nexus S 4G 1 Click : http://forum.xda-developers.com/showthread.php?t=1167819
Nexus S 1 Click : http://nexusshacks.com/nexus-s-hacks/how-to-unroot-nexus-s-i9020ti9020ai9023/
USE GOOGLE PEOPLE! If you don't know what you're talking about, keep your mouth shut!
The easiest method would've been to nandroid backup your OEM setup & restored it...

Exaxtly. GOOGLE IS YOUR TEACHER.google will teach you so much. Use it!!!!
Mish.Mash said:
People posting all this trash.
Nexus S 4G 1 Click : http://forum.xda-developers.com/showthread.php?t=1167819
Nexus S 1 Click : http://nexusshacks.com/nexus-s-hacks/how-to-unroot-nexus-s-i9020ti9020ai9023/
USE GOOGLE PEOPLE! If you don't know what you're talking about, keep your mouth shut!
The easiest method would've been to nandroid backup your OEM setup & restored it...
Click to expand...
Click to collapse
sent from my Nexus S

Question about backing up and Un-rooting.

So I am looking to root but I still a few questions.
So if I don't flash roms or anything to revert to stock could i just use the factory reset built in to phones settings app (Razr HD XT925) and would that make it back to a fresh phone with no signs of root?
Also if i am going to flash roms and kernels if take a nandroid backup then even if I switch roms or kernels I can restore using the backup to stock rom and then I can just factory reset after i restore from my backup through the factory restore in settings to make it like a brand new phone agian?
Last question, say I wanted to get warranty would they be able to tell it was rooted if I did one of the two steps above? Sorry for all the questions I just kinda want to figure this out before I root my phone.
Thanks
-Riley

1. that will not return to stock, that is not a flash. You would need to install the whole OS using once of the flash utilities.
You can remove root by getting rid of the SU application and such. They may or may not be able to tell. I've sent rooted phones back for warranty with no issues.
2. You would have to remove safestrap, etc. But yes you can go back to stock.
3. If done correctly, no they can't tell.

tech_head said:
1. that will not return to stock, that is not a flash. You would need to install the whole OS using once of the flash utilities.
You can remove root by getting rid of the SU application and such. They may or may not be able to tell. I've sent rooted phones back for warranty with no issues.
2. You would have to remove safestrap, etc. But yes you can go back to stock.
3. If done correctly, no they can't tell.
Click to expand...
Click to collapse
Number 3 is not true. There is a second method that shows rooted status that right now can't be changed. I'm sure a method to fix that can be devised now with the unlocked bootloader but that in itself is irreversible.
sent from my xt926 RAZR maxx hd

WARNING WARNING please read before rooting!!!

I know this isn't technically the right section for this but I put it here in hopes more people would see it. This is very important for anyone rooting using the dirtysanta method and perhaps other methods as well. It would be nice if this could get a sticky because people need to see this or this problem is going to keep occurring. I'm seeing it all over the threads.
DO NOT FACTORY RESET FROM INSIDE THE ROM. DO NOT USE LG's BUILT IN FACTORY RESET IN THE PHONE OR YOU WILL GET STUCK IN RECOVERY. Use the factory reset option inside of TWRP if you want to do a factory reset.
There have been many people (myself included even though I knew better and told myself not to do it before I did) who have got stuck in recovery because of this and it's not common sense to get out of it. I've been rooting and messing with this stuff for over 5 years and for 2 hours tried every trick I knew and nothing worked. What did finally end up working for me personally is this:
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power (hold them down), as soon as you see the LG logo let go of power for a brief moment and continue to press and hold both buttons until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount storage button, and reboot system.

lol this is only because it give you your stock boot.img. So if you factory reset, you have to flash SuperSU, no need to freak out.
If you format /system, you will need to flash a ROM, if the ROM does not flash SuperSU, you will h ave to flash it.
That's all folks!
That said, who wants a VZW Custom ROM and Kernel? Making the thread now. Identical to my H918 5.1 MOD ROM

Tilde88 said:
lol this is only because it give you your stock boot.img. So if you factory reset, you have to flash SuperSU, no need to freak out.
If you format /system, you will need to flash a ROM, if the ROM does not flash SuperSU, you will h ave to flash it.
That's all folks!
That said, who wants a VZW Custom ROM and Kernel? Making the thread now. Identical to my H918 5.1 MOD ROM
Click to expand...
Click to collapse
I tried flashing supersu.zip but that wouldn't work either. I challenge you to factory reset in the rom and then once stuck in recovery flash a new rom and the supersu zip and see if that works. I did this several times and it wouldn't work. I tried it with flashing a rom, and after restoring a backup. What appears to be happening is the system isn't mounting and it doesn't recognise that you have a ROM installed.
Not freaking out either, just trying to let people know not to factory reset inside the rom but use TWRP. There have been many people with this issue.

imucarmen said:
I tried flashing supersu.zip but that wouldn't work either. I challenge you to factory reset in the rom and then once stuck in recovery flash a new rom and the supersu zip and see if that works. I did this several times and it wouldn't work. I tried it with flashing a rom, and after restoring a backup. What appears to be happening is the system isn't mounting and it doesn't recognise that you have a ROM installed.
Not freaking out either, just trying to let people know not to factory reset inside the rom but use TWRP. There have been many people with this issue.
Click to expand...
Click to collapse
Oh, sorry. I overlooked something. That you had in huge bold caps the words IN THE ROM lol, my bad. I've never factory reset from within the ROM.
But my post stands when factory resetting from TWRP.

Tilde88 said:
Oh, sorry. I overlooked something. That you had in huge bold caps the words IN THE ROM lol, my bad. I've never factory reset from within the ROM.
But my post stands when factory resetting from TWRP.
Click to expand...
Click to collapse
Yea I knew better too, that's the bad part. In 5+ years I've never factory reset while in a rom when I have root and TWRP installed. Before I did it I even told myself it was probably a bad idea and I should just use TWRP. But my lazy conscience said "ahhh what the heck! just do it, it's too much trouble to boot into TWRP and besides, it might work ok" I hate my lazy consicence :'(

Exactly what I did and exactly what happened.
Gonna try this in the AM. One question...
If I'm able to flash back to "stock" using a deoxed stock rom, how can I then get rid of the boot warning so I can return this device to T-Mobile?

mrbigdrawsz said:
Exactly what I did and exactly what happened.
Gonna try this in the AM. One question...
If I'm able to flash back to "stock" using a deoxed stock rom, how can I then get rid of the boot warning so I can return this device to T-Mobile?
Click to expand...
Click to collapse
You'll need to return to full stock. I can't verify it works but this thread here claims to have a method for returning to stock.

imucarmen said:
You'll need to return to full stock. I can't verify it works but this thread here claims to have a method for returning to stock.
Click to expand...
Click to collapse
Well pray for me. Downloading now and will try first thing tomorrow.

mrbigdrawsz said:
Well pray for me. Downloading now and will try first thing tomorrow.
Click to expand...
Click to collapse
Did it work for you? Also since there is no t mobile rom there what did you use?

thegameksk said:
Did it work for you? Also since there is no t mobile rom there what did you use?
Click to expand...
Click to collapse
I used this guide https://goo.gl/ZHZPfO and it worked perfectly. Had a little stress when attempting to flash the stock recovery, but after installing two again, I was able to revert back to stock. Locked bootloader and it's as if I never did anything but boot up the stock OS.
Returning to T-Mobile today and just waiting on my Oneplus 3T to ship (granted I'm pissed off because the 128gb version is out of stock).

mrbigdrawsz said:
I used this guide https://goo.gl/ZHZPfO and it worked perfectly. Had a little stress when attempting to flash the stock recovery, but after installing two again, I was able to revert back to stock. Locked bootloader and it's as if I never did anything but boot up the stock OS.
Returning to T-Mobile today and just waiting on my Oneplus 3T to ship (granted I'm pissed off because the 128gb version is out of stock).
Click to expand...
Click to collapse
Glad you got it fixed.
Just for the record, this thread isn't for helping people get back to stock, its main focus is to warn people not to factory reset inside the rom. Then I just shared the method that worked for me to get out of being stuck in TWRP. Not saying you implied any different, I'm just clarifying for anyone that may read in the future. It's awesome return to stock methods are now popping up which are usually good for fixing all sorts of issues.
Enjoy your OnePlus 3T