Is downgrade to GB possible? is 4.0.3 stock rootable? - Nexus S Q&A, Help & Troubleshooting

I just bought an unlocked 9023 nexus s for my sister in India. I am a flash-junkie on my verizon droid inc, but she is not tech savvy. I wanted to load up a good stable system for her before handing over the phone so she could use it as a daily machine. I was thinking about applying the stock 4.0.3 full update but then i saw some issues about wifi and signal and google halting it, so now im having second thoughts. if i do the 4.0.3 full update from recovery, can i go back to gb if i have problems?
will the phone keep getting all future ics upgrades through google?
is 4.0.3 stock rootable? and will root stay in upgrades? (so if i root and give her, Id like her to use titanium and stuff and not have to worry about losing root in future OTA.)
Thanks.

How about reading the stickies.

k.electron said:
I just bought an unlocked 9023 nexus s for my sister in India. I am a flash-junkie on my verizon droid inc, but she is not tech savvy. I wanted to load up a good stable system for her before handing over the phone so she could use it as a daily machine. I was thinking about applying the stock 4.0.3 full update but then i saw some issues about wifi and signal and google halting it, so now im having second thoughts. if i do the 4.0.3 full update from recovery, can i go back to gb if i have problems?
will the phone keep getting all future ics upgrades through google?
is 4.0.3 stock rootable? and will root stay in upgrades? (so if i root and give her, Id like her to use titanium and stuff and not have to worry about losing root in future OTA.)
Thanks.
Click to expand...
Click to collapse
Nexus devices can always have their bootloaders unlocked and then install superuser afterward. When unlocking the bootloader all of her data will be lost.
Root is disable on OTA updates because permissions get adjusted. You can run a fix permissions in CWM or reflash a superuser zip file after the OTA to get root again.
You can go back to GB by flashing an old system image using fastboot if you don't like ICS.

superm1 said:
Nexus devices can always have their bootloaders unlocked and then install superuser afterward. When unlocking the bootloader all of her data will be lost.
Root is disable on OTA updates because permissions get adjusted. You can run a fix permissions in CWM or reflash a superuser zip file after the OTA to get root again.
You can go back to GB by flashing an old system image using fastboot if you don't like ICS.
Click to expand...
Click to collapse
thanks.
exactly what i needed to know. i might just put ics and give it to her without root so she can keep getting OTAs because i dont think she really needs root.

Related

Searching and searching, looking for eoot access

what is the sure way to root thunderbolt on the latest OTA, i was rooted before but lost root on the update i waited a few weeks before rooting again and now im searching if there is a way to root the device atm?
http://forum.xda-developers.com/showthread.php?t=1401959 you need to go here you have to downgrade. Then you can use revolutionary
thank you for your support, after i downgrade how do i update and keep root?
You dont. Just run the downgraded. Or flash a custom rom if u want root. The radios from the upgrade are available in the dev section as well. If u want them. Supposidly better handoff betweeen 4g and 3g with the new radio
Andlamv said:
thank you for your support, after i downgrade how do i update and keep root?
Click to expand...
Click to collapse
I know a little late on the scene and don't know if you figured this out but..
If you mean by "update", running the stock 605.9 then..
-after downgrading to 605.5 using the provided link
-root with revolutionary
-at that point you can flash the "rooted" version of 605.9 or any other ROM as mentioned before, this will allow you to keep root and prevent Big Red from trying to push the OTA

[Q] root & unlock

Hi, this might be stupid to ask but I really need answer for this -
1. I know that with rooted stock OS one cannot get OTA updates, but can anybody get OTA updates with unlocked bootloader - non-rooted stock OS ?
2. Also all the guides I have found to unroot a xoom is asking to flash a stock OS, which will erase all the data & all the customization which I have made. Is there is no way possible to unroot the current rooted stock OS without losing out the small customization.
I came in here looking for the same answer... want to update, I'm rooted, but can't get it OTA this way.
Go to Development and the first post by stachre is rooted stock ICS 4.0.3, cwm flashable zip.
Thats just fr wifi, while i m on 3g build
Still waiting fr an answer :-(
Sent from my MZ601 using XDA App
You DONT need to unroot for to get a ota.
The ota is NOT out for the 3g version or any other version at this point.
If EVERYTHING else is stock besides root the ota will install.
The state of the bootloader does not matter either.
I think there's a chance to brick your device if you do an OTA update after you unlock your bootloader?
So if you really want to try 4.0 then I would recommend the TeamEOS roms, they have roms for both the wifi only and the 3G versions.
No there is no chance.
albundy2010 said:
You DONT need to unroot for to get a ota.
The ota is NOT out for the 3g version or any other version at this point.
If EVERYTHING else is stock besides root the ota will install.
The state of the bootloader does not matter either.
Click to expand...
Click to collapse
thanks matey , just 1 clarify require on your statement.
my mz601 xoom's current state is unlocked bootloader, cwm recovery, rooted with stock 3.2 OS with a small change in framework-res.apk to send sms.
for this situation also your point stands right?
No.
I put the word everything in caps for a reason.... nothing that is supposed to be there can be changed or deleted. Includes apks recovery.... you know everything

Lost root after flash via RSD Lite on JB

Hi guys,
I'm moving from my hard-bricked GS2 to a Razr HD. Second hand and got the carrier unlock code yesterday, so I was all like "ooook now the fun begins... time to root ICS,, OTA keeper, OTA update, etc..."
Root went smooth. OTA rootkeeper too, then I upgraded to JB (I'm in France, phone is SFR branded so I got the OTA update), and recovered root. But then I thought "ok, I should probably do a reset to factory, just to start clean from here on". Bad idea, as I ended on a bootloop, hardly possible to access fastboot mode. But I managed to access it in the end, first tried a "Factory" from there. The phone booted correctly, but something was still wrong: battery indicator was "?", and at every reboot I ended up in bootloop again. No other choice than to flash the full rom via RSD Lite, which I did earlier today.
And now, I'm back on a fully working 4.1.1, but OTA RootKeeper says no "protected root" available, and I can't restore root at all. Tried Matt's Razr HD Utility, but it fails at downgrading to 4.0.4 since my bootloader is locked... and I'm not too found of unlocking it, since I've been VERY unlucky for the past 2 months, and voiding my warranty now would be a message to the universe like "hey dude, juste add another mess with my stuffs, now's the time!"
Am I correct in the assumption that the only way to re-root my device is to unlock bootloader/downgrade to 4.0.4 with razr hd utils/flash original SFR 4.0.4/root/rootkeeper protect/re-upgrade via OTA/rootkeeper restore ? Are there any progress in rooting directly from JB ?
Thanks for your help!
CoinCoin88 said:
Hi guys,
I'm moving from my hard-bricked GS2 to a Razr HD. Second hand and got the carrier unlock code yesterday, so I was all like "ooook now the fun begins... time to root ICS,, OTA keeper, OTA update, etc..."
Root went smooth. OTA rootkeeper too, then I upgraded to JB (I'm in France, phone is SFR branded so I got the OTA update), and recovered root. But then I thought "ok, I should probably do a reset to factory, just to start clean from here on". Bad idea, as I ended on a bootloop, hardly possible to access fastboot mode. But I managed to access it in the end, first tried a "Factory" from there. The phone booted correctly, but something was still wrong: battery indicator was "?", and at every reboot I ended up in bootloop again. No other choice than to flash the full rom via RSD Lite, which I did earlier today.
And now, I'm back on a fully working 4.1.1, but OTA RootKeeper says no "protected root" available, and I can't restore root at all. Tried Matt's Razr HD Utility, but it fails at downgrading to 4.0.4 since my bootloader is locked... and I'm not too found of unlocking it, since I've been VERY unlucky for the past 2 months, and voiding my warranty now would be a message to the universe like "hey dude, juste add another mess with my stuffs, now's the time!"
Am I correct in the assumption that the only way to re-root my device is to unlock bootloader/downgrade to 4.0.4 with razr hd utils/flash original SFR 4.0.4/root/rootkeeper protect/re-upgrade via OTA/rootkeeper restore ? Are there any progress in rooting directly from JB ?
Thanks for your help!
Click to expand...
Click to collapse
Just to make sure you do have SuperUser, SuperSU, and I generally prefer to include BusyBox all into the mix. Also, if you would download Root Checker by Joey Krim in the Play store. Just to confirm and we know you are missing root click the verify should indicate the appropriate SU's are red and not engaged, slide to the right verify BusyBox, chances are it is green, if so you are in good condition. With Busybox in green, exit go into SuperUser and update the binaries, once that is completed go into SuperSU and click the update. Go back to Root Checker and double check, click verify root on SuperUser/SuperSU and should be green = rooted. :good:
Root is red.... and so is busybox (however it is installed by default on my marketplace apps...) So if I understand correctly, I'm f***ed (at least, until a JB exploit is found, or I decide to void my warranty and unlock the bootloader, which I'm probably not going to do for now...)
CoinCoin88 said:
Root is red.... and so is busybox (however it is installed by default on my marketplace apps...) So if I understand correctly, I'm f***ed (at least, until a JB exploit is found, or I decide to void my warranty and unlock the bootloader, which I'm probably not going to do for now...)
Click to expand...
Click to collapse
If the color is Red all around then yes, there is little you can do. However, there are ways to get out of this and gain root without waiting even if they have Jelly Bean 4.1.1. For instance those on JB that own the XT926 can use the Droid Razr HD Utility 1.10 > go back to ICS 4.0.4 > apply the 1st update > Root > Voodoo OTA, SU Backup > apply the JB 4.1.1 update. I have done this twice and have been quite successful on my XT926 with Verizon.
But, in general going back to the discussion. If after the update the Supers are not showing, as long as Busy Box is Green and in place, Root can be restored by updating the binaries.
If your RSD/Flash you device root is gone.
The flashing completely formats and wipes the area for system.
Either you have to root JB, from what I understand you can.
Of back to ICS, root, Voodoo install, protect, then upgrade to JB.
tech_head said:
If your RSD/Flash you device root is gone.
The flashing completely formats and wipes the area for system.
Either you have to root JB, from what I understand you can.
Of back to ICS, root, Voodoo install, protect, then upgrade to JB.
Click to expand...
Click to collapse
I haven't found anything about that... however I might have missed something. Do you have any link to explain how ?
Regarding the flashing via RSD, that is what I thought, but was unsure. Coming from the GS2, the equivalent software is Odin, and wiping doesn't necessarily occurs (depends on build.prop content), so I had a *little* hope.
@KachowPow: indeed, Matt's Razr HD Utility for XT926 is known to work on the XT925 too... however it requires an unlocked bootloader. I *could* unlock mine since Motorola provides the code for XT925 too, however I'm not too found of voiding my warranty right now because of the whole "universe against me" thing ...
I'll probably wait for a proper JB exploit then. For now, root was important to *try* to restore contacts data from my old TB backup of my Galaxy S2 (I wanted to do a "dirty" restore of the co,tacts, hoping that even if it's not the same phone/apk/databases they would at least appear on the phone and be able to sync to Gmail from there.... And then I would have wiped to factory default and restored from Gmail). But I've managed to mess around with the contacts2.db from my GS2 and created a CSV with first name/last name/phone number(s). So for now I'm good and don't actually need root anymore. Yeah, that was a "just talking about my life" moment, so what ? )
CoinCoin88 said:
I haven't found anything about that... however I might have missed something. Do you have any link to explain how ?
Regarding the flashing via RSD, that is what I thought, but was unsure. Coming from the GS2, the equivalent software is Odin, and wiping doesn't necessarily occurs (depends on build.prop content), so I had a *little* hope.
@KachowPow: indeed, Matt's Razr HD Utility for XT926 is known to work on the XT925 too... however it requires an unlocked bootloader. I *could* unlock mine since Motorola provides the code for XT925 too, however I'm not too found of voiding my warranty right now because of the whole "universe against me" thing ...
I'll probably wait for a proper JB exploit then. For now, root was important to *try* to restore contacts data from my old TB backup of my Galaxy S2 (I wanted to do a "dirty" restore of the co,tacts, hoping that even if it's not the same phone/apk/databases they would at least appear on the phone and be able to sync to Gmail from there.... And then I would have wiped to factory default and restored from Gmail). But I've managed to mess around with the contacts2.db from my GS2 and created a CSV with first name/last name/phone number(s). So for now I'm good and don't actually need root anymore. Yeah, that was a "just talking about my life" moment, so what ? )
Click to expand...
Click to collapse
Not sure what carrier you are on but if you flashed to JB, then just find the xml and flash to ICS, then you root.
I used Voodoo to preserve root my device.
I'm pretty sure there *IS* a JB root in the last day or so.
You will need to search since I don't know for sure.
tech_head said:
Not sure what carrier you are on but if you flashed to JB, then just find the xml and flash to ICS, then you root.
I used Voodoo to preserve root my device.
I'm pretty sure there *IS* a JB root in the last day or so.
You will need to search since I don't know for sure.
Click to expand...
Click to collapse
edit the XML ?? I'm new to RSD lite, but from what I've understood so far, edit the xml is only neededn when flashing via RSDLite/fastboot so that you don't end-up with the "unknown fastboot command" or something like that (by removing 2 lines in the fw xml file, indeed).
How is this related to going back from JB to ICS ? I'm not sure that's possible with a locked bootloader (which I'm probably not going to unlock). Also, how is my carrier related to this operation ? (the phone was SFR simlocked, but I bought an unlock code online and I'm no using it on Free Mobile)
Or did I miss something ? (btw, no mention of a JB root for the Razr HD, only for the Razr M, and it is assumed it won't work on HD because for reasons I am yet to find)

[Q] OTA Lollipop update

So back in the day, I did a root and unlocked a bootloader on my Nexus 5 but didn't do any major changes, I mean I didn't install any rom or any any mods, then I did everything back - un-rooted, locked a bootloader.
What I am actually curious about is - Will I still receive ota through my settings menu or do I have to do everything back and flash an image on my phone?
Rey0 said:
So back in the day, I did a root and unlocked a bootloader on my Nexus 5 but didn't do any major changes, I mean I didn't install any rom or any any mods, then I did everything back - un-rooted, locked a bootloader.
What I am actually curious about is - Will I still receive ota through my settings menu or do I have to do everything back and flash an image on my phone?
Click to expand...
Click to collapse
You will receive the OTA fine as long as there were no modifications to your system. Rooting and un-rooting wouldn't change that, nor would un-locking and locking your bootloader.
jagreci said:
You will receive the OTA fine as long as there were no modifications to your system. Rooting and un-rooting wouldn't change that, nor would un-locking and locking your bootloader.
Click to expand...
Click to collapse
Sounds cool then. Thanks
I'm actually thinking about doing just that myself. IE doing a clean install with unlocked boot loader and rooting the device. If nothing else so I can make full Nandroid backups in the future.
I was worried however that if I rooted my n5 with Lollipop that I may not get future OTA updates. Or that an update may break root access. Sounds like however this is not the case and I have nothing to worry about?
crucialcolin said:
I'm actually thinking about doing just that myself. IE doing a clean install with unlocked boot loader and rooting the device. If nothing else so I can make full Nandroid backups in the future.
I was worried however that if I rooted my n5 with Lollipop that I may not get future OTA updates. Or that an update may break root access. Sounds like however this is not the case and I have nothing to worry about?
Click to expand...
Click to collapse
1st, just so you know, you don't need root for "nandroid" backups. Only thing you need is a custom recovery.
2nd, naturally, a OTA update may break root. Being rooted doesn't stop the OTA from being downloaded or installed.
keep this in mind:
- want to root? an update/new factory images is out? you're in control, update manually, don't update, do backups before updating, whatever: OTAs are all hype, no stability.
http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
beekay201 said:
1st, just so you know, you don't need root for "nandroid" backups. Only thing you need is a custom recovery.
2nd, naturally, a OTA update may break root. Being rooted doesn't stop the OTA from being downloaded or installed.
keep this in mind:
- want to root? an update/new factory images is out? you're in control, update manually, don't update, do backups before updating, whatever: OTAs are all hype, no stability.
Click to expand...
Click to collapse
I've actually been spoiled by nandroid on the HP TouchPad with CM. Really nice to have a complete backup image. Wish I would have thought about unlocking and rooting before I got a bunch of stuff on my Nexus setup the way I like it. Sort of stuck since you have to unlock the boot loader for a custom recovery. Thus is life though.
I haven't tried it yet but it looks like Adb can do it on a stock device.
ex: http://forum.xda-developers.com/showpost.php?p=51694433&postcount=2
I'm actually extremely torn on the OTA thing. I find it just so damn convenient with the admission I've gotten lazy of late Otherwise I have a tendency to never update.

[Q] Moving SCH-I535 Verizon S3 from 4.1.2 rooted to 4.4.2 rooted

I'm on a verizon SCH-I535 running android 4.1.2 (baseband I535VRBMF1, kernel 3.0.31-1152558, build jzo54k.i535vrbmf1, hardware version i535.10). I rooted the device a couple years ago, and have rejected OTA updates, ever since I received the 4.1.2 one (in fact, I used a file manager, to rename some files, so I wouldnt get the pop-up telling me there was an OTA update anymore). Everything is, as it was required to be, in order to get root access on 4.1.2, I just followed the instructions I found on xda.
Now that android 4.4.2 is available, and there is an easy root for it, what is the easiest way for me to move from where I am to 4.4.2 rooted? Am I supposed to follow the instructions in the "Reset your phone in order to return to Verizon" sticky? If so, how do I know if my bootloader is 'locked' or 'unlocked'? Alternatively to these instructions I was thinking of doing a "full unroot" with superSU then simply doing an OTA update, but wasnt sure if that would introduce issues.
Finally, in terms of doing a backup, I downloaded an app called "online nandroid" which supposedly saved a backup to my sd card. But my sd card is tiny, and the backup went really quick, so what exactly is it backing up? Is it enough of a backup that if I want to do a full restore back to exactly the state my phone is in now later, I can do that, or do I need a different tool for that?
loonytoon500 said:
I'm on a verizon SCH-I535 running android 4.1.2 (baseband I535VRBMF1, kernel 3.0.31-1152558, build jzo54k.i535vrbmf1, hardware version i535.10). I rooted the device a couple years ago, and have rejected OTA updates, ever since I received the 4.1.2 one (in fact, I used a file manager, to rename some files, so I wouldnt get the pop-up telling me there was an OTA update anymore). Everything is, as it was required to be, in order to get root access on 4.1.2, I just followed the instructions I found on xda.
Now that android 4.4.2 is available, and there is an easy root for it, what is the easiest way for me to move from where I am to 4.4.2 rooted? Am I supposed to follow the instructions in the "Reset your phone in order to return to Verizon" sticky? If so, how do I know if my bootloader is 'locked' or 'unlocked'? Alternatively to these instructions I was thinking of doing a "full unroot" with superSU then simply doing an OTA update, but wasnt sure if that would introduce issues.
Finally, in terms of doing a backup, I downloaded an app called "online nandroid" which supposedly saved a backup to my sd card. But my sd card is tiny, and the backup went really quick, so what exactly is it backing up? Is it enough of a backup that if I want to do a full restore back to exactly the state my phone is in now later, I can do that, or do I need a different tool for that?
Click to expand...
Click to collapse
In order to move to the 4.4.2 update you'll have to unroot, but keep in mind if you do your bootloader will be PERMANENTLY locked, no going back
The backup of stock is normally somewhere between 2-3gb or more, it didn't do the full backup. I highly doubt it's a full backup. Once you take the OTA to 4.4.2 your stuck and there is no going back
Your best bet is to install a custom recovery, cwm, twrp or philz or similar. If you want to take the OTA your free to but once again there's no custom roms after that. No CM or AOSP after you take the OTA
From my S3 running BlissStalk
ShapesBlue said:
In order to move to the 4.4.2 update you'll have to unroot, but keep in mind if you do your bootloader will be PERMANENTLY locked, no going back
The backup of stock is normally somewhere between 2-3gb or more, it didn't do the full backup. I highly doubt it's a full backup. Once you take the OTA to 4.4.2 your stuck and there is no going back
Your best bet is to install a custom recovery, cwm, twrp or philz or similar. If you want to take the OTA your free to but once again there's no custom roms after that. No CM or AOSP after you take the OTA
From my S3 running BlissStalk
Click to expand...
Click to collapse
Thank you for your response.
I do not care about custom ROMS, I am ok with the stock android OS, as long as I can get root. If the OTA update permanently locks my bootloader I am ok with that.
That said, I want to ensure I dont have any incidents when I do the OTA update. (that I dont brick my device. or make things more difficult for myself.) It doesnt look like I currently have a custom recovery (I tried to boot into custom recovery but the phone simply boots normally. I can however boot into stock android recovery). Also, my bootloader is currently unlocked.
Given that I dont currently have a custom recovery, and that my bootloader is currently unlocked, will that present any issue if I simply do a full unroot using superSU, and then take the OTA update? I used triangle away earlier today to reset my flash counter to 0 (it was 1 before).
loonytoon500 said:
Thank you for your response.
I do not care about custom ROMS, I am ok with the stock android OS, as long as I can get root. If the OTA update permanently locks my bootloader I am ok with that.
That said, I want to ensure I dont have any incidents when I do the OTA update. (that I dont brick my device. or make things more difficult for myself.) It doesnt look like I currently have a custom recovery (I tried to boot into custom recovery but the phone simply boots normally. I can however boot into stock android recovery). Also, my bootloader is currently unlocked.
Given that I dont currently have a custom recovery, and that my bootloader is currently unlocked, will that present any issue if I simply do a full unroot using superSU, and then take the OTA update? I used triangle away earlier today to reset my flash counter to 0 (it was 1 before).
Click to expand...
Click to collapse
It shouldn't but the OTA will lock in back up
From my S3 running BlissStalk
ShapesBlue said:
It shouldn't but the OTA will lock in back up
From my S3 running BlissStalk
Click to expand...
Click to collapse
Ok, i unrooted, and tried to take the OTA update, but a quarter of the way through the update, the update fails/stops, and it shows a lying android, with a red exclamation triangle over it; then the phone simply reboots and says "sorry, there was a problem updating your SAMSUNG SCH-I535. No changes were made." I read something about how this could be the case if I froze some stock apps, but how do I check if any stock apps are frozen? I dont remember doing so but its certainly possible.
What course of action do you recommend? It sounds like I will need to go through the process of rerooting again. I've read I can reflash the 4.1.2 stock rom and then do the OTA update, but I dont want to wipe data. The no wipe version is linked to here, but the firmware links there appears to be broken.
loonytoon500 said:
Ok, i unrooted, and tried to take the OTA update, but a quarter of the way through the update, the update fails/stops, and it shows a lying android, with a red exclamation triangle over it; then the phone simply reboots and says "sorry, there was a problem updating your SAMSUNG SCH-I535. No changes were made." I read something about how this could be the case if I froze some stock apps, but how do I check if any stock apps are frozen? I dont remember doing so but its certainly possible.
What course of action do you recommend? It sounds like I will need to go through the process of rerooting again. I've read I can reflash the 4.1.2 stock rom and then do the OTA update, but I dont want to wipe data. The no wipe version is linked to here, but the firmware links there appears to be broken.
Click to expand...
Click to collapse
After all the reading I've done in order to take the OTA you have to unroot. I don't know the complete process as I am not on any OTA
From my S3 running BlissStalk
Even if you dont care about custom ROMs right now you may in the future when there are no updates released for the phone or you want to sell it and could have gotten a higher price with the lower system version. Before you update try some of the ROMs out and see if there are some you like and if you dont like any then update.
That being said I have updated using ODIN and the firmware I got from this site. look around and you will find the stuff you need.
i ended up flashing a 4.1.1 stock no wipe rom i found and after that i could take the ota updates (had to do multiple in a row).
out of curiosity couldn't the devs find a way to unlock the bootloader via some hackery in the future?
loonytoon500 said:
i ended up flashing a 4.1.1 stock no wipe rom i found and after that i could take the ota updates (had to do multiple in a row).
out of curiosity couldn't the devs find a way to unlock the bootloader via some hackery in the future?
Click to expand...
Click to collapse
Sure it's possible, but unlikely. To put into perspective, I don't believe there has been a bootloader unlock for Verizon Notes 2-4 and Galaxy S4-5 (which would allow one to natively run AOSP without Safestrap) so the likelihood is low.
Sent from my SCH-I535 using Tapatalk

Categories

Resources