root the phone will block future OTA update? even factory image installed?
I donwload rom manager from market, it says your 'rom does not support OTA update, please contact your developer', but I have pure factory image from google installed.
is it showing worong thing? or did it mess up my system? or I should never had clicked there?
ROM manager is talking about an ota update for a custom rom, which you aren't running. And if you want to know whether rooting will prevent a future official ota, a search will tell you the answer.
Sent from my Galaxy Nexus using XDA App
this article says yes. but other places say it might not, but ota update will remove the root.
citrix80 said:
it might not, but ota update will remove the root.
Click to expand...
Click to collapse
This.
Twice so far for me.
Rooting the stock ROM will not prevent OTA updates. I've had the Nexus One and now the Galaxy Nexus, and I can tell you that rooting will not prevent OTA updates, as long as you have stock recovery.
What will prevent OTA updates from installing is custom recovery. If you're using ClockwordMod recovery, you will get the OTA update notifications, but the actual update will fail to install. You can still install them manually by flashing the update yourself in recovery. It's easy.
In either case, you'll almost certainly need to re-root afterwards.
stock recovery? you mean stock image from google.
logically it make sense custom roms don't get update because they are modified from orginal copy, updates are for original condtion copy so may not fit into them correcty. but what exactly is preventing the update there?
I dont have custom rom or recovery and my ota failed.
Sent from my Galaxy Nexus using xda premium
@rbiter said:
I dont have custom rom or recovery and my ota failed.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
after root?
OTA updates install via recovery, so they fail with custom recovery (ClockworkMod). They should install with stock recovery. This is assuming the stock ROM (even rooted), not a custom ROM since as you said that definitely won't work at all, since the update is meant for the stock ROM.
If an OTA update fails on the stock ROM (even rooted) with stock recovery, something else is usually wrong. It's definitely possible, but not the normal situation. In two years with my Nexus One and now Galaxy Nexus, I've never had an OTA update fail on a rooted stock ROM (both automatically with stock recovery and re-rooting afterwards, or manually applying the update with custom recovery).
I know with the Nexus One, some OTA updates failed if people had rooted and removed some of the built-in apps or otherwise messed around with /system. If things like that get modified, there's a good chance the update will fail.
Just my experience... hopefully someone else can give some further input.
does rooting make any change to system?
citrix80 said:
does rooting make any change to system?
Click to expand...
Click to collapse
Getting root access only involves two files being placed in the /system partition:
1) the su binary is placed in the /system/bin directory; and,
2) the Superuser.apk file is placed in the /system/app directory.
Other than that, there are no other changes.
As phazerorg said, rooting will not affect getting the OTA.
There are two separate issues here:
1) Receiving the OTA update; and,
2) Having the OTA update install.
Everyone on a stock ROM (and even some custom ROMs) will receive the OTA update (eventually).
As for installing the OTA update, there are again two issues here:
1) Having the OTA update install automatically; or,
2) Installing the OTA update manually.
To have the OTA update install automatically, you need the following:
1) A stock recovery;
2) A stock ROM (and it CANNOT be de-odexed);
3) All the original applications need to be present (like Goggles, Google+, etc.)
4) Root or no root makes no difference; and
5) A stock boot image.
If you have a custom recovery flashed, then you can manually apply the update through the recovery. However, all the other items from the list above still apply.
If you flashed a stock de-odexed ROM, or a boot image (i.e., kernel) that was modified somehow, you need to flash back to the stock version of each or else you cannot apply the update.
Hope this clears up some things.
what is stock recovery? is it same as stock image?
what is de-odexd ?
efrant said:
Getting root access only involves two files being placed in the /system partition:
1) the su binary is placed in the /system/bin directory; and,
2) the Superuser.apk file is placed in the /system/app directory.
Other than that, there are no other changes.
As phazerorg said, rooting will not affect getting the OTA.
There are two separate issues here:
1) Receiving the OTA update; and,
2) Having the OTA update install.
Everyone on a stock ROM (and even some custom ROMs) will receive the OTA update (eventually).
As for installing the OTA update, there are again two issues here:
1) Having the OTA update install automatically; or,
2) Installing the OTA update manually.
To have the OTA update install automatically, you need the following:
1) A stock recovery;
2) A stock ROM (and it CANNOT be de-odexed);
3) All the original applications need to be present (like Goggles, Google+, etc.)
4) Root or no root makes no difference; and
5) A stock boot image.
If you have a custom recovery flashed, then you can manually apply the update through the recovery. However, all the other items from the list above still apply.
If you flashed a stock de-odexed ROM, or a boot image (i.e., kernel) that was modified somehow, you need to flash back to the stock version of each or else you cannot apply the update.
Hope this clears up some things.
Click to expand...
Click to collapse
Thank you for taking the time to clear this up.
I unlocked the bootloader, rooted, and then installed CWM to make a back-up. I am still, and plan on always, running the stock Rom (4.0.2 right now). I was worried about the OTA's but based on what you said, I can still download the update, but I would need to use CWM to actually install the update? Or would I just need to flash the new update via an updated-stock-rom?
citrix80 said:
what is stock recovery? is it same as stock image?
Click to expand...
Click to collapse
Your phone has several different firmwares on it. Radio, bootloader, recovery and the actual OS. Recovery is what lets you "recover" the OS when things are screwed, and also perform other maintenance operations... such as installing OS updates. You can boot your phone into the bootloader or recovery, in addition to the OS.
Custom recoveries such as ClockworkMod let you do even more things, such as flashing updates or custom ROMs of your choice, or taking nandroid backups (which are basically "images" of your current ROM. Restoring a nandroid backup brings your phone back to exactly how it was at the time the backup was taken... very useful when trying new ROMs or messing around! This is reason enough to use a custom recovery in my opinion).
The stock OS only knows how to install OTA updates using the stock recovery. Stock recovery is what comes on your phone (or from Google via an update). Custom recoveries like ClockworkMod are generally based on the stock recovery, but are different and the OTA updates don't work with them automatically. You can definitely install OTA updates using custom recovery, but you have to do it manually. After you get an update notification from the stock ROM, the update zip file should be downloaded and located in /cache and you can use ClockworkMod to flash it. I also keep the Superuser zip on my phone at all times, so I can flash it immediately after flashing an OTA update, which lets me retain root.
To answer your actual question, I would say that stock recovery is one part of the stock image. But most people probably think of the "stock image" as being the OS side of things. You could have the stock image OS, but still use custom recovery. I hope that makes sense.
what is de-odexd ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/Glossary#De-Odex
Although I understand what odex/deodex is, I'm not sure I can give a very good explanation. Someone else can comment, or you can do a search as it's been covered a number of times in various forums on xda, and other sites.
where is the recovery/stock recovery and how to access?
when I boot into fastboot, there is up/down arrow, when I click on revoery, i see an android robot with x mark on it.
I used cwm did a full system wipe, the phone went dead, stuck on bootloader screen, then I flashed stock image from beginning.
how to take nandroind back up? i only see backup/restore in cwm.
citrix80 said:
where is the recovery/stock recovery and how to access?
when I boot into fastboot, there is up/down arrow, when I click on revoery, i see an android robot with x mark on it.
I used cwm did a full system wipe, the phone went dead, stuck on bootloader screen, then I flashed stock image from beginning.
how to take nandroind back up? i only see backup/restore in cwm.
Click to expand...
Click to collapse
In CWM go to Recovery (Hit the "power" button to select), then go to "Back Up and Restore" (use the "power" button to select), then go to "Back Up". Make sure you have at least 50% battery when you do this.
After it finishes copy the contents it should be in /sdcard/clockworkmod/backup I back it up to Dropbox, so I can have the files where ever. (PM me if you'd like an invite so we can both get more space on Dropbox. If you do use Dropbox, I'd encrypt the data with something like TrueCrpyt.)
citrix80 said:
where is the recovery/stock recovery and how to access?
when I boot into fastboot, there is up/down arrow, when I click on revoery, i see an android robot with x mark on it.
I used cwm did a full system wipe, the phone went dead, stuck on bootloader screen, then I flashed stock image from beginning.
how to take nandroind back up? i only see backup/restore in cwm.
Click to expand...
Click to collapse
With the phone completely off, holding down both volume up and volume down and then holding the power button will get you into the bootloader. From there you can use volume up/down to scroll through options to boot into recovery. Alternatively, if you're already rooted, you can use apps like Quickboot to just reboot directly into recovery.
I never actually tried the stock recovery on my phone... I unlocked the bootloader and flashed ClockworkMod and rooted as soon as I got the phone home from the store. Normally, selecting "Recovery" from the bootloader menu would get you into recovery. The only time when I saw the android with the X was after trying to apply the first OTA update (just for fun even though I knew it wouldn't work without stock recovery).
If you have ClockworkMod (CWM)... the backup/restore is nandroid. It's called nandroid because it's NAND flash, and the OS is Android... NAND... Android... Nandroid.
But... make sure you backup /sdcard to another place, because if you do a full factory wipe, you'll also lose all that since they're stored on the "sd card", which is really the data partition. Doing wipes in CWM doesn't wipe /sdcard, but factory resets do. I reguarly rsync my /sdcard to another computer over wifi so I'm sure to always have a completely external backup. That's never a bad idea when you're messing around with this stuff. Too many backups never hurt anyone. Too few backups, on the other hand...
citrix80 said:
what is stock recovery? is it same as stock image?
what is de-odexd ?
Click to expand...
Click to collapse
http://lmgtfy.com/?q=what+is+stock+recovery
http://lmgtfy.com/?q=what+is+deodexed
JayBeezy802 said:
Thank you for taking the time to clear this up.
I unlocked the bootloader, rooted, and then installed CWM to make a back-up. I am still, and plan on always, running the stock Rom (4.0.2 right now). I was worried about the OTA's but based on what you said, I can still download the update, but I would need to use CWM to actually install the update? Or would I just need to flash the new update via an updated-stock-rom?
Click to expand...
Click to collapse
Yes, if you have CWM installed, you can use that to install the update. No need to flash an updated stock ROM.
---------- Post added at 08:52 AM ---------- Previous post was at 08:49 AM ----------
citrix80 said:
where is the recovery/stock recovery and how to access?
when I boot into fastboot, there is up/down arrow, when I click on revoery, i see an android robot with x mark on it.
[snip]
Click to expand...
Click to collapse
The Android robot with the X on it is the stock recovery. When you are there, hold the power button and press the volume up key to access the menu.
efrant said:
The Android robot with the X on it is the stock recovery. When you are there, hold the power button and press the volume up key to access the menu.
Click to expand...
Click to collapse
I just tried to access my stock recovery. But I see the Android robot with a triangle with ! inside. Then I can't do anything with it - power button and volume keys have no effect. What does this mean? I'm running stock rom with stock recovery but with bootloader unlocked.
Related
I got an OTA notification. I'm currently running the stock GB rom,
with s-off, rooted (unrevoked 3.21) and CWM 5.0.2.0. I have ADB
installed and working.
What do I need to do to apply update without messing up
existing root setup?
Anyone know what is being updated? Does it replace radio,
boot or recovery?
fuzzynco said:
I got an OTA notification. I'm currently running the stock GB rom,
with s-off, rooted (unrevoked 3.21) and CWM 5.0.2.0. I have ADB
installed and working.
What do I need to do to apply update without messing up
existing root setup?
Anyone know what is being updated? Does it replace radio,
boot or recovery?
Click to expand...
Click to collapse
Applying the ota will make you loose root, but as long as your s-off you can root again easily.
Not sure exactly whats updated. If your rooted the update will not go thru anyways. It checks to make sure you have the stock recovery, and that all of your original stock apps and system files are there and unchanged. To install you would have to go complete stock other than still being s-off.
it does nothing if you have a custom recovery file.
if you click install, it'll do the count down, but won't reboot.
when you manually reboot, it'll still be what you had.
my setup is:
S-ON
HBOOT: 0.92.0000
CWM: 5.0.2.0
Baseband: 2.15.10.07.07
GingerTiny v2
GingerSense 3.5
So, I need to replace CWR with stock recovery?
All the bloatware is still there I just froze it in Ti.
I guess I need to remove superuser.apk & su?
then update, fastboot flash cwr back,
(is the last recovery.img file from nandroid
backup suitable for restoring cwr via fastboot?),
then reroot?
Think someone will package the update
for cwr flashing?
So, I need to replace CWR with stock recovery?
All the bloatware is still there I just froze it in Ti.
I guess I need to remove superuser.apk & su?
then update, fastboot flash cwr back,
(is the last recovery.img file from nandroid
backup suitable for restoring cwr via fastboot?),
then reroot?
Think someone will package the update
for cwr flashing?
PS:
Is there a way to stop the prompting for
OTA installing?
thanks
yes, anyone know how to get it to stop prompting? should i just let it try to upate and fail (i have root/custom recovery)? i froze updater using TI and i tried editing build.prop but neither worked.
orphicone said:
yes, anyone know how to get it to stop prompting? should i just let it try to upate and fail (i have root/custom recovery)? i froze updater using TI and i tried editing build.prop but neither worked.
Click to expand...
Click to collapse
What line did you edit in the build.prop? What number did you replace and what did you use to replace it? I've been trying to narrow this down also since it's worked in the past. So far I see one user that claims the build is 210690.
So in the build.prop I'd be looking for the line that included "/XXXXXX:user..." and replace the old 6 digit number with the new.
iowabowtech said:
What line did you edit in the build.prop? What number did you replace and what did you use to replace it? .
Click to expand...
Click to collapse
I used root explorer but my editing wasn't very sophisticated. Hopefully someone can shed some light? Post the updated build.prop values for this build and which ones we have to change?
orphicone said:
I used root explorer but my editing wasn't very sophisticated. Hopefully someone can shed some light? Post the updated build.prop values for this build and which ones we have to change?
Click to expand...
Click to collapse
Check this out, hopefully I explained it a little better here. Maybe you could give it a shot or confirm if this is how you did it and if that's the number you edited?
http://forum.xda-developers.com/showpost.php?p=19371024&postcount=58
Open build.prop with the text editor and look for:
Code:
ro.htc.checkin.url =http://andchin.htc.com/android/checkin
Change the url to something else but dont leave it blank. This will prevent the phone from contacting thr update server.
fuzzynco said:
All the bloatware is still there I just froze it in Ti.
I guess I need to remove superuser.apk & su?
then update, fastboot flash cwr back,
(is the last recovery.img file from nandroid
backup suitable for restoring cwr via fastboot?),
then reroot?
Think someone will package the update
for cwr flashing?
Click to expand...
Click to collapse
I hope someone posts a flashable version of this update for us on cwm. I'm in the same boat as you.
yeah me too
Chernyi said:
I hope someone posts a flashable version of this update for us on cwm. I'm in the same boat as you.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1347044
The above linked thread is to an entire ROM and requires wiping. Is it possible to create an update.zip to bump me up (and keep me rooted) if I am rooted and have CWM? I know this has been done for previous updates.
This method helped me turn off the annoying install reminders. I used it with Nils' Business Gingersense.
http://forum.xda-developers.com/showpost.php?p=19370543&postcount=993
I just went ahead and updated since mine is S-OFF.
The steps I used to update and re-root:
Make sure you have S-OFF.
Boot into Clockworkmod and Backup your phone just in case.
Download the following:
Stock Recovery: http://www.multiupload.com/86N0CZ8NO0
Clockworkmod Recovery: http://www.multiupload.com/UQ3Q5ZI0HO
SuperUser: http://androidsu.com/superuser/ (use binary only if you already had SuperUser app installed)
Copy OTA update in /cache to SD card and name it update.zip.
Copy recovery zip files and SuperUser zip (su-bin-3.0.3-efgh-signed.zip) to SD card.
Rename stock_recovery_PB31IMG.zip to just PB31IMG.zip.
Hold VOL-, press POWER to boot into bootloader.
Press VOL- to update recovery to stock. At this point, it may automatically install the update. If not (red exclamation), press VOL+ and POWER to get to the stock recovery menu and select "Apply update.zip from SD" to update manually.
When update completes and you're booted into Android, go to Settings, Applications, and turn off Quick Boot.
Rename or delete existing stock recovery .zip on SD card.
Rename Clockworkmod recovery, cwm_PB31IMG.zip, to PB31IMG.zip.
Shutdown or reboot phone and get into bootloader again, and this time flash Clockworkmod recovery.
Get into Clockworkmod and use it to flash su-bin-3.0.3-efgh-signed.zip.
Once it reboots, you will be updated and rooted.
GnatGoSplat said:
I just went ahead and updated since mine is S-OFF.
The steps I used to update and re-root:
1. Make sure you have S-OFF.
2. Copy OTA update in /cache to SD card and name it update.zip.
3. Copy stock recovery to SD card and make sure it's named PB31IMG.zip.
4. Hold VOL-, press POWER to boot into bootloader.
...
Where is the stock recovery file? There is nothing in /cache or /cache/recovery. For a brief time, the OTA update file for Gingerbread 4.08 was in /cache, but nothing in recovery. the update file has since disappeared, but not before I copied it to my sdcard, so I have that.
Also, I noticed after installing that version of Gingerbread on another phone that was not rooted, that once I did that the hboot menu did not appear when holding down the vol key while powering on. Maybe that is an S-off thing only.
Thanks.
Click to expand...
Click to collapse
I had to search Google for quite some time before finding the stock recovery and when i searched just now, all I found were broken links.
I won't be home for awhile, but let me know if you can't find the stock recovery and I'll upload it somewhere.
Oh yeah, you have to go into Settings, Applications, and turn off Fast Boot or Quick Boot in order to be able to get into bootloader when rebooting.
shoot
I wish I had read this thread before i messed up my phone. I was running fine rooted with unrevoked and I thought I'd be smart and get the OTA to install and worry about re-rooting later. It would never reboot so I did a factory reset. That only stuck mine in a Sense crash loop. I'm on PrimeXL's r40 ROM now for 24hours and I'm looking into what else might be available. It runs ok but I can't get Exchange mail for work because something about "device encryption enabled" policy, pic gallery won't show emmc folders, and keyboard auto-correct goes nuts in portrait mode on internet.
jonduncan99 said:
I wish I had read this thread before i messed up my phone. I was running fine rooted with unrevoked and I thought I'd be smart and get the OTA to install and worry about re-rooting later. It would never reboot so I did a factory reset. That only stuck mine in a Sense crash loop. I'm on PrimeXL's r40 ROM now for 24hours and I'm looking into what else might be available. It runs ok but I can't get Exchange mail for work because something about "device encryption enabled" policy, pic gallery won't show emmc folders, and keyboard auto-correct goes nuts in portrait mode on internet.
Click to expand...
Click to collapse
Are you wanting to go back to stock?
If so, are you S-OFF? If yes, it's pretty easy, you can just install the full Gingerbread RUU (the .exe file that installs from PC) to go back completely to stock and it'll boot for sure.
What I would do is do a backup with clockworkmod to SD.
Then install the RUU.
Flash clockworkmod back into it (this is why you need to be S-OFF).
Use clockworkmod to restore only your /data partition from SD.
Re-root by installing su.zip.
You should now be rooted, stock, and all your apps and settings should still be intact.
I don't know for sure the backup and restore will work from one ROM to the next, but it did work when I bricked my wife's Incredible and had to restore from RUU (though it was on stock ROM before and after).
HI all:
Actually its my friends problem, since he got GN, I was helping him to unlock bootloader, root and flash CWM recovery.
After few weeks, he got an OTA to 4.0.4, of course he cant, because he's using CWM.
So I help him to re-flash stock recovery, and apply an OTA update, but I got an red mark again.
I tried to find where the problem is, and I asked here, I got an answer, I do re-flash stock recovery, I only need to press vol+, vol- and power when I saw red mark to start it.
OK, then I tried again, I enter recovery and I press the button, I success start stock recovery.
I think there would be no problem to me to apply an OTA to 4.0.4 again, but damn I still got an red mark, so I press 3 button, and it shows me to recovery page, I choose "apply update from /cache", next, I see the file of OTA update.
Unfortunately, it cant update again because of signature fail.
how should I do if I don't want to use CWM to update?
Harry1021 said:
HI all:
Actually its my friends problem, since he got GN, I was helping him to unlock bootloader, root and flash CWM recovery.
After few weeks, he got an OTA to 4.0.4, of course he cant, because he's using CWM.
So I help him to re-flash stock recovery, and apply an OTA update, but I got an red mark again.
I tried to find where the problem is, and I asked here, I got an answer, I do re-flash stock recovery, I only need to press vol+, vol- and power when I saw red mark to start it.
OK, then I tried again, I enter recovery and I press the button, I success start stock recovery.
I think there would be no problem to me to apply an OTA to 4.0.4 again, but damn I still got an red mark, so I press 3 button, and it shows me to recovery page, I choose "apply update from /cache", next, I see the file of OTA update.
Unfortunately, it cant update again because of signature fail.
how should I do if I don't want to use CWM to update?
Click to expand...
Click to collapse
Your friend has one or more of the following:
1) a radio that is different from XXKK6;
2) a boot image that is either not stock or (if it is stock), a different version from the one included in the factory image of the ROM you are using;
3) a stock recovery that is a different version from the one included in the factory image of the ROM you are using;
4) files in /system that were modified or deleted, either by him, or one of his root apps.
Those issues need to be rectified before the update will install.
And by the way, if you download the update, it will install in CWM -- it just won't install over-the-air in CWM.
Have a read of this thread for additional info.
efrant said:
Your friend has one or more of the following:
1) a radio that is different from XXKK6;
2) a boot image that is either not stock or (if it is stock), a different version from the one included in the factory image of the ROM you are using;
3) a stock recovery that is a different version from the one included in the factory image of the ROM you are using;
4) files in /system that were modified or deleted, either by him, or one of his root apps.
Those issues need to be rectified before the update will install.
And by the way, if you download the update, it will install in CWM -- it just won't install over-the-air in CWM.
Have a read of this thread for additional info.
Click to expand...
Click to collapse
I do think the problem is version in recoovery, where can I get the stock recovery img of 4.0.1?
Harry1021 said:
I do think the problem is version in recoovery, where can I get the stock recovery img of 4.0.1?
Click to expand...
Click to collapse
Sorry, I made a mistake in the first point above. I believe that XXKK1 was the radio that came with 4.0.1, not XXKK6.
You can get the images from here, thanks to oldblue910.
efrant said:
Sorry, I made a mistake in the first point above. I believe that XXKK1 was the radio that came with 4.0.1, not XXKK6.
You can get the images from here, thanks to oldblue910.
Click to expand...
Click to collapse
THZ I will try
Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA
KrizTM said:
Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA
Click to expand...
Click to collapse
Yes that means its rooted, you should have a custom Recovery. If you power off and hold the volume keys and the power button then a green android will pop up use the volume keys and hit up twice to the "recovery mode" then hit the power button... then if you could tell me what you see? At the bottom it should say Clockworkmod 5.x.x.x or it will have TWRP which it will show TeamWin at first and a curtain will pull up. If you do have custom recovery you could just simply flash a custom ROM like AOKP for you device .
KrizTM said:
Hi guys, blackberry convert here.
So I just bought a "docomo" carrier nexus and it's been working good so far.
It's running 4.01 and recently got an update notification but when i tried to update it rebooted to a green android with its chest opened up and a red exclamation mark. I did some searching and noticed that happens when you try to OTA upgrade a rooted phone am I correct?
So my question is what are my options? Can I flash 4.04 ? Do i need to lock my bootloader and wipe back to stock? If I do.. Will i get the unpleasant surprise of everything being in japanese?
What about flashing a custom rom such as aokp? Will that upgrade me to 4.04 or not?
TIA
Click to expand...
Click to collapse
No, that doesn't happen because of root. Root has NO IMPACT WHATSOEVER on your ability to install updates OTA. It will happen if your recovery does not match your ROM.
You have a few options:
1) you can go to the "update" link in my signature, find the update for your build, and install it manually as per the instructions in that thread.
2) you can go to the "flash" link in my signature and flash stock (yakju) 4.0.4 as per the instructions.
3) you can flash a 4.0.4-based custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
No, that doesn't happen because of root. Root has NO IMPACT WHATSOEVER or your ability to install updates OTA.
Click to expand...
Click to collapse
UH YES it does... why do you think we get so many "broken android red exclamation mark!" threads started... because people who root tried to accept the OTA. OTA's require the stock Recovery to install... when it sees that thats been changed or something has been modified.. then it errors. Get it straight.
ÜBER™ said:
UH YES it does... why do you think we get so many "broken android red exclamation mark!" threads started... because people who root tried to accept the OTA. OTA's require the stock Recovery to install... when it sees that thats been changed or something has been modified.. then it errors. Get it straight.
Click to expand...
Click to collapse
Uh, excuse me... having root makes no difference. You get it straight. But you are right, having the wrong recovery (custom recovery or incorrect stock version) will give you that screen.
I've applied every single update on a rooted phone. Details in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Uh, excuse me... having root makes no difference. You get it straight. But you are right, having the wrong recovery (custom recovery or incorrect stock version) will give you that screen.
I've applied every single update on a rooted phone. Details in the update link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Heh... i dont see people with just superuser and no custom recovery the two go hand in hand... which is why i say Root does to play a part. At least on certain devices.
ÜBER™ said:
Heh... i dont see people with just superuser and no custom recovery the two go hand in hand... which is why i say Root does to play a part. At least on certain devices.
Click to expand...
Click to collapse
Well, lots of users in the forums root and keep the stock recovery, but yeah, not as many as those who use a custom recovery along with root. That is why I make the distinction. Adding files to /system (which is what rooting does ) doesn't affect anything. Deleting or replacing system files does however.
Additionally, you can still update even with a custom recovery. Just put the update file in /sdcard, reboot into recovery and flash it. No difference than having it flashed by a stock recovery.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Well, lots of users in the forums root and keep the stock recovery, but yeah, not as many as those who use a custom recovery along with root. That is why I make the distinction. Adding files to /system (which is what rooting does ) doesn't affect anything. Deleting or replacing system files does however.
Additionally, you can still update even with a custom recovery. Just put the update file in /sdcard, reboot into recovery and flash it. No difference than having it flashed by a stock recovery.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Gotcha now that we are done bickering.. i hope the OP can find his way.
ycholish siempre
3) you can flash a 4.0.4-based custom ROM.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Is aokp a 4.04 based ROM? I keep refering to aokp because from what ive read its the best rom out there.
then if you could tell me what you see?
Click to expand...
Click to collapse
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Thanks for the help guys .
KrizTM said:
Is aokp a 4.04 based ROM? I keep refering to aokp because from what ive read its the best rom out there.
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Thanks for the help guys .
Click to expand...
Click to collapse
Aokp just has a bunch more options which is quite overwhelming especially for a new user such as yourself. I would suggest using CM9 first. Okay that means your boot loader is unlocked... I said you have to go into recovery mode... which when at the boot loader screen you use the volume keys and hit up twice it change from start to recovery mode in red. Press the power button and tell me if you see a cyan blue recovery or team win on a blue curtain that pulls up.
Sent from my Galaxy Nexus using xda premium
ÜBER™ said:
Aokp just has a bunch more options which is quite overwhelming especially for a new user such as yourself. I would suggest using CM9 first. Okay that means your boot loader is unlocked... I said you have to go into recovery mode... which when at the boot loader screen you use the volume keys and hit up twice it change from start to recovery mode in red. Press the power button and tell me if you see a cyan blue recovery or team win on a blue curtain that pulls up.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Ok. i did the recovery mode thing and it gave me the android with its chest open and a red exclamation mark thing again
What's going on?
Check my sig to get yourself on AOKP.
KrizTM said:
[snip]
Well it tells me im on prime and that my lock mode is : unlocked. So i suppose i'm rooted.
Click to expand...
Click to collapse
Ok, I think you are confusing things here:
(1) An unlocked bootloader
(2) Root
(3) A custom recovery
The three items above are completely separate. Having one does not mean the others, nor does one require any of the others. Just because your bootloader is unlocked does not mean your OS is rooted, nor does it mean you have a custom recovery.
KrizTM said:
So if i flash a custom 4.04 rom i'm all set for future upgrades? Or should I flash androids stock 4.04 and then flash a custom rom?
Click to expand...
Click to collapse
ONLY stock ROMs can receive OTA updates. If you want updates, you need to be running a stock ROM. Period.
If you want to run a custom ROM, you will either get updates from the developer, or you will need to flash an updated version of that custom ROM.
Again, don't confuse flashing an updated version of ROM (i.e., a complete ROM), vs updating a ROM (i.e., an incremental update).
KrizTM said:
Ok. i did the recovery mode thing and it gave me the android with its chest open and a red exclamation mark thing again
What's going on?
Click to expand...
Click to collapse
That screen IS the stock recovery. (FYI, to access the menu, you need to press vol up and power simultaneously and repeatedly).
I would suggest you follow the instructions here to flash the yakju 4.0.4 build (do all the optional steps in part D) and then you will be set for all future OTA updates. (And besides, it is always wiser to run stock for a while, so that when you switch to a custom ROM, you have a basis for comparison.)
If you want to run a custom ROM, download whichever ROM it is to your /sdcard.
No you must first flash a custom recovery. Do this:
Assuming you already have the drivers set up and you have fastboot.exe on you computer (instructions found in the link above), do the following:
1) Download CWM from here;
2) Rename the file to cwm.img, and make sure it is in the same directory as your fastboot.exe file;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot flash recovery cwm.img
6) Now you have a custom recovery. Use the volume buttons on your device to navigate to "recovery", and use the power button to select;
7) Wipe your device using the CWM menus;
8) Flash the ROM by using the CWM menus (something like flash zip or something).
efrant said:
Ok, I think you are confusing things here:
(1) An unlocked bootloader
(2) Root
(3) A custom recovery
The three items above are completely separate. Having one does not mean the others, nor does one require any of the others. Just because your bootloader is unlocked does not mean your OS is rooted, nor does it mean you have a custom recovery.
ONLY stock ROMs can receive OTA updates. If you want updates, you need to be running a stock ROM. Period.
If you want to run a custom ROM, you will either get updates from the developer, or you will need to flash an updated version of that custom ROM.
Again, don't confuse flashing an updated version of ROM (i.e., a complete ROM), vs updating a ROM (i.e., an incremental update).
That screen IS the stock recovery. (FYI, to access the menu, you need to press vol up and power simultaneously and repeatedly).
I would suggest you follow the instructions here to flash the yakju 4.0.4 build (do all the optional steps in part D) and then you will be set for all future OTA updates. (And besides, it is always wiser to run stock for a while, so that when you switch to a custom ROM, you have a basis for comparison.)
If you want to run a custom ROM, download whichever ROM it is to your /sdcard.
No you must first flash a custom recovery. Do this:
Assuming you already have the drivers set up and you have fastboot.exe on you computer (instructions found in the link above), do the following:
1) Download CWM from here;
2) Rename the file to cwm.img, and make sure it is in the same directory as your fastboot.exe file;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot flash recovery cwm.img
6) Now you have a custom recovery. Use the volume buttons on your device to navigate to "recovery", and use the power button to select;
7) Wipe your device using the CWM menus;
8) Flash the ROM by using the CWM menus (something like flash zip or something).
Click to expand...
Click to collapse
Awesome. That clears up a lot of things. Thanks a lot You're right. Gonna stick to stock 4.04 till I get better at this hehe.
Thanks
Hello all, I was wondering if anyone can point me in the right direction. I have a acer iconia a100 rooted and currently running the carbon rom (4.2.2) and twrp recovery (2.6.3.0). I would like to go back to stock rom (ICS). I have not changed any kernals or anything like that. Can I just restore my nandroid backup of my stock rom or is there something specific I have to do? Also, I just looked and I dont have a stock backup with twrp, only with cwm. When I unlocked bootloader, I installed cwm, then must have done a backup of stock rom, then flashed carbon rom, then switched to twrp and made another backup so I would have to go back to cwm to restore nandroid. How do I go back to cwm from twrp?? Thanks for the feedback.
I looked in my internal storage and it looks like I have 2 zips, fastbootrecovery.zip and xsposeddisabler-cwm.zip, do I flash one of these?? and if I do, can I do it with es explorer?? Thanks
jreink01 said:
Hello all, I was wondering if anyone can point me in the right direction. I have a acer iconia a100 rooted and currently running the carbon rom (4.2.2) and twrp recovery (2.6.3.0). I would like to go back to stock rom (ICS). I have not changed any kernals or anything like that. Can I just restore my nandroid backup of my stock rom or is there something specific I have to do? Also, I just looked and I dont have a stock backup with twrp, only with cwm. When I unlocked bootloader, I installed cwm, then must have done a backup of stock rom, then flashed carbon rom, then switched to twrp and made another backup so I would have to go back to cwm to restore nandroid. How do I go back to cwm from twrp?? Thanks for the feedback.
I looked in my internal storage and it looks like I have 2 zips, fastbootrecovery.zip and xsposeddisabler-cwm.zip, do I flash one of these?? and if I do, can I do it with es explorer?? Thanks
Click to expand...
Click to collapse
Just the stock ROM or completely back to stock, 100%?
If you don't know what those zips are, or how to use them, then don't use them, period.
To get back cwm you can use fastboot to flash it back on or use one of the cwm installers in development, if any are still there, if you want to do it with fastboot you'll need some stuff to get ready, most of it should be there from when you rooted the first time, then a couple lines in a command prompt and you'll have it back. There's also stock rooted ICS ROMs available, so depending on what you want we can go from there.
Tapatalked from my HTC DNA - Akakaze
pio_masaki said:
Just the stock ROM or completely back to stock, 100%?
If you don't know what those zips are, or how to use them, then don't use them, period.
To get back cwm you can use fastboot to flash it back on or use one of the cwm installers in development, if any are still there, if you want to do it with fastboot you'll need some stuff to get ready, most of it should be there from when you rooted the first time, then a couple lines in a command prompt and you'll have it back. There's also stock rooted ICS ROMs available, so depending on what you want we can go from
I am going to sell my tablet so I would like to go to my backup of my stock rom. When I restore my stock backup, I can just do a full wipe, that will get me back to the starting point of just the basic rom, right?? That will wipe all my data from the backup rom, or will a full wipe erase the rom too?? I want to get back to the basic rom (just like if I install a new rom) have to set up accounts, wifi, etc).
Also, is there a tutorial or a step by step guide to reinstall cwm back on my tablet, since my stock rom was backed up with cwm? And where do I have the files to reflash cwm. Thanks for your assistance in helping me return my tablet to the state I want.
Click to expand...
Click to collapse
I found a site that has it step by step, installing cwm. Here it is.
Here it is guys, Stock CWM Recovery for the ACER A100.
Before anything make sure you have the latest ICS leak C/O Vache, Root, and Unlocked Bootloader.
Official ICS Leak c/o Vache:
http://forum.xda-developers.com/show....php?t=1510706
Root Instructions here:
http://forum.xda-developers.com/show....php?t=1531646
Unlock your bootloader for fastboot, follow here:
http://forum.xda-developers.com/show....php?t=1557445
once you have done all of the above, you should be ready to flash this recovery. Make sure you have ADB up and working properly. And place the recovery.img in your working folder (see below)
1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
But it says make sure you have the latest ics leak?? Are they refferring to the rom?? If so, I currently have carbon rom istalled which is jellybean. This will not work then?? I am a little confused and any feedback would be greatly appreciated.
jreink01 said:
I found a site that has it step by step, installing cwm. Here it is.
Here it is guys, Stock CWM Recovery for the ACER A100.
Before anything make sure you have the latest ICS leak C/O Vache, Root, and Unlocked Bootloader.
Official ICS Leak c/o Vache:
http://forum.xda-developers.com/show....php?t=1510706
Root Instructions here:
http://forum.xda-developers.com/show....php?t=1531646
Unlock your bootloader for fastboot, follow here:
http://forum.xda-developers.com/show....php?t=1557445
once you have done all of the above, you should be ready to flash this recovery. Make sure you have ADB up and working properly. And place the recovery.img in your working folder (see below)
1- Open a command prompt in your working folder (usually in your platform tools, mine is C:\android-sdk-windows\platform-tools) make sure you are administrator.
2- Connect Tablet to pc and get excited.
3- Type: adb devices (verify your Tab is connected and listed)
4- Type: adb reboot bootloader
5- Once bootloader is in fastboot type: fastboot flash recovery recovery.img
You will see writing recovery, flashing recovery, etc.
6- Once flashed Type: fastboot reboot
7- Profit
But it says make sure you have the latest ics leak?? Are they refferring to the rom?? If so, I currently have carbon rom istalled which is jellybean. This will not work then?? I am a little confused and any feedback would be greatly appreciated.
Click to expand...
Click to collapse
Does anyone have any suggestions?? Thanks
Well, before the tab got official ICS, we had a leak. If you had read down the topics some you would've found it. You do not want cwm, you want twrp.
Sent from my SPH-L710 using xda app-developers app
das_webos_transformer said:
Well, before the tab got official ICS, we had a leak. If you had read down the topics some you would've found it. You do not want cwm, you want twrp.
Does anyone have any suggestions on whether it is ok to do this? Thanks
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I need cwm to restore my stock rom. If I use the steps quoted below to reinstall cwm, will I run into any problems since I'm coing from carbon rom (jellybean) to stock rom which is (ICS)?
jreink01 said:
I need cwm to restore my stock rom. If I use the steps quoted below to reinstall cwm, will I run into any problems since I'm coing from carbon rom (jellybean) to stock rom which is (ICS)?
Click to expand...
Click to collapse
Does anyone know if this how to guide is good to use when coming from carbon rom (jellybean) to stock rom (ics))? Thanks
jreink01 said:
Does anyone know if this how to guide is good to use when coming from carbon rom (jellybean) to stock rom (ics))? Thanks
Click to expand...
Click to collapse
To just go back to stock to sell it you'll run into a couple issues coming from 4.2+, namely the storage path changes, you'll retain the /0 folders, however many were made. Otherwise following the guide that roman made will work to go back to 100% stock, I'll see if I can get a link, I'm in a waiting room with crappy data lol
Edit:
That guide will work for installing cwm, basically get your cwm image then get fastboot going, fastboot flash recovery cwmimageyougot.IMG
http://forum.xda-developers.com/showthread.php?p=33574648
Best way to return to 100% stock. No need to fuss with recoveries just install what he says then the ROM does the rest. While in twrp remember to go delete /0 directories or they'll remain there forever. Or until its deleted at a later date, but if you have stuff in there you should do it prior to going fully stock again.
Tapatalked from my HTC DNA - Akakaze
pio_masaki said:
To just go back to stock to sell it you'll run into a couple issues coming from 4.2+, namely the storage path changes, you'll retain the /0 folders, however many were made. Otherwise following the guide that roman made will work to go back to 100% stock, I'll see if I can get a link, I'm in a waiting room with crappy data lol
Edit:
That guide will work for installing cwm, basically get your cwm image then get fastboot going, fastboot flash recovery cwmimageyougot.IMG
http://forum.xda-developers.com/showthread.php?p=33574648
Best way to return to 100% stock. No need to fuss with recoveries just install what he says then the ROM does the rest. While in twrp remember to go delete /0 directories or they'll remain there forever. Or until its deleted at a later date, but if you have stuff in there you should do it prior to going fully stock again.
Tapatalked from my HTC DNA - Akakaze
Click to expand...
Click to collapse
Thanks for the response, youve fully confused me with the /0 folders?? What exactly is that?? When I go to es file explorer, I see sdcard0 (which looks like the internal storage) and sd01 which looks like my ext sd card. Is it one of those your are talking about??
Also, you said something about go delete in twrp, I went into twrp and did not find anything with that name?? am I deleteing something in twrp. Could you spell it out for me since I am a noob when it comes to reverting a device to stock. Thanks for taking the time to explain this.
jreink01 said:
Thanks for the response, youve fully confused me with the /0 folders?? What exactly is that?? When I go to es file explorer, I see sdcard0 (which looks like the internal storage) and sd01 which looks like my ext sd card. Is it one of those your are talking about??
Also, you said something about go delete in twrp, I went into twrp and did not find anything with that name?? am I deleteing something in twrp. Could you spell it out for me since I am a noob when it comes to reverting a device to stock. Thanks for taking the time to explain this.
Click to expand...
Click to collapse
that is something happening with cwm. i had this problem. it keeps creating a folder names 0 and keep moving old files into that whenever you install a new rom.
Hello guys. I need your feedback. I have a A100 that is rooted and is currently running carbon rom 4.2. I am going to be selling this in the next couple weeks because I just don't use it anymore now that I have a second pc.Do you think it would be more advantagious to sell this just the way it is (rooted and custom rom) or should I take it back to completely stock? Or if it is more advantagious to sell it with a custom rom, which rom would you guys suggest?? Thanks again for any and all suggestions.
Please Help!! I was trying to go to stock ics and these are the steps I used.The simple method to revert back to stock ICS from a custom ROM on an A100.
+++Locked bootloader, no custom recovery, no root. Full stock .014 rom. It will recieve OTA updates to latest Acer version.+++
Get Ready
1) Download this flashable Stock recovery zip, and place in your normal flashing location, - Thx 4 help pio
http://db.tt/VLmnMCzq
Also uploaded below
2) Download the Official .014 Stock ICS rom
The stock ICS zip from zeronull. http://forum.xda-developers.com/show....php?t=1611696
Here is a second link to it. http://ubuntuone.com/7DZtbNqZzOk7qsaQxNk99a - thx zleto
3) Rename the Stock ICS rom to "update.zip", no quotes (make sure you have "hide known file extensions" UNCHECKED, in the folder options). And place it on the root of your microSD card. This will allow you to see the file extension to verify that it is named properly.
Get it Done
1) Flash the Stock recovery zip with your custom recovery. Then wipe cache, davlik cache, and wipe data/factory reset.
2) Reboot to system.
3) Allow it to sit for 5 minutes or so.
4) Then Power off.
5) Update from the microSD card by holding down the power and volume rocker closest to the corner at the same time, until you see "erasing cache .".. ect, ect. The stock rom install should start by itself, dont touch anything, wait for it to reboot.
****** If it won't boot do a factory reset (with the hardware buttons, see below) and/or try to reflash the ics rom one more time. ******
Quote:
To perform a Factory Data Reset use the following steps:
1.Place the rotation lock switch in the up position (tablet held in portrait). Or to the left if held in landscape.
2.Press and hold the Volume down button, which is located farthest from the corner (it is volume up, if held in landscape).
3.With the Volume down button held, press and hold the Power button for 3 seconds then release it. Continue holding the Volume down button.
4.Once the tablet vibrates, switch the rotation lock on and off repeatedly while still holding the Volume down button.
5.Release the Volume down button and stop switching the rotation lock once the "Erasing Userdata..." message appears in the upper left corner of the screen
Now I get the android symbol with the red triangle, that stays for about a minute, then it reboots and stays on thye acer screen. When I did the steps and was going to reboot, I received a waring while in recovery sayiny that I dont have a op installed. I did it anyway, as posted and now I'm stuck, can anyone PLEASE help me.I tried doing a reset with steps 2 though 4 but while pressing the vol up and letting go of the power button, it does not vibrate.
I try to boot into recovery with vol up + power, it boots than says erasing cache, then booting into recovery, the the android synbol comes up with the red triangle.
I can't even get into recovery. It says bootloader (unlock mode) when I pwer it on. If I press power + vol up, it says erasing cache, then booting into recovery kernal, then the android symbol comes up with the red triangle.Thanks for responding and since this is the wrong thread, can we discuss this in the other thread?? While I was typing this, the android symbol with the triangle was on the screen for about 2 minutes, then it just rebooted and now its saying acer acer acer acer acer on the bottom of the screen.
Can anyone help me out with this please?
I'm trying to take the OTA update using the steps provided here: https://forum.xda-developers.com/htc-10/help/updating-via-ota-modified-t3440340
I restored my system image and then flashed my stock recovery: fastboot flash recovery 1.53.617.5_rec.img. Both from my computer and my phone it appears to succeed. However when I reboot and download the OTA, it enters a boot loop. I can break out of the boot loop (not sure if it is giving up eventually on it's own or if it's from me holding the power button) and get back into android fine. However if I try to enter recovery, I get the htc logo for 1/2 second, then I get it again along with a boot vibrate, and android loads.
I've tried flashing the stock recovery twice with the same results.
I used this same stock recovery the last time I took an OTA. I'm not positive I'm taking the exact same steps so I've probably missed something.
What have I done wrong and how do I fix it so I can take the OTA?
Root checker does say it's still rooted. Would being rooted prevent the stock recovery from loading? I thought restoring the system image unrooted the phone. Maybe I missed a step? I previously rooted by sideloading the supersu zip for the htc 10.
TheShanMan said:
I'm trying to take the OTA update using the steps provided here: https://forum.xda-developers.com/htc-10/help/updating-via-ota-modified-t3440340
I used this same stock recovery the last time I took an OTA. I'm not positive I'm taking the exact same steps so I've probably missed something.
What have I done wrong and how do I fix it so I can take the OTA?
Click to expand...
Click to collapse
That recovery won't work then. You should be on 2.xx.617.x firmware now and will need the recovery that matches it. Also the proper system.img to match it.
Do you know what your current firmware version is? I can upload the stock system.img and recovery.img for you if you let me know.
---------- Post added at 09:33 AM ---------- Previous post was at 09:18 AM ----------
Try using this recovery instead.
fastboot flash recovery 2.38.617.6_recovery_signed.img
Thanks! I'm on 2.41.617.3.
delete. will update soon
Undelete: I thought I uploaded the wrong file
Here is the recovery.img for that.
Do you need the system.img for that as well? Because if so you should just backup what you have now and run the RUU to 2.46.617.2 It'll be quicker and easier
I don't think that worked. It appeared to succeed but when I took the OTA I got the red exclamation on boot. I rebooted and root checker says I still have root.
I previously restored the system_image. So I have to restore system too? I did a full backup after my last OTA so I think I've got everything I need, but from the linked thread I thought I only had to do system_image.
To be clear, I'm looking for clarity on what to restore. I just tried doing boot plus system_image (plus the stock recovery you provided) and I get the red exclamation mark at 25% of OTA application. So what of the following needs restoring?
*boot
*system
*system image
OTA worked for me last time so I'm not sure what I'm doing differently this time. I'd rather not go the RUU route because I want to develop muscle memory (not to mention keeping my own notes!) for doing OTA's in general so I don't have to deal with restoring my apps and data every time.
No ideas? Do I need to resort to an RUU update? Like I said, I'd rather not but it wouldn't be the end of the world.
TheShanMan said:
I don't think that worked. It appeared to succeed but when I took the OTA I got the red exclamation on boot. I rebooted and root checker says I still have root.
I previously restored the system_image. So I have to restore system too? I did a full backup after my last OTA so I think I've got everything I need, but from the linked thread I thought I only had to do system_image.
Click to expand...
Click to collapse
If you have the full stock backup, then restore that, reflash the stock recovery, and try again.
An RUU really isn't a bad way to go either, especially in the future. If you did one before you tried updating now, then there's no reason not to. When you restore it, the system and boot partitions will be re-written, but the firmware won't be. You could also flash the signed firmware, but that will wipe your phone as well so there's really not much of an advantage there.
You should think about going S-Off. For the $25 price it REALLY makes updating easier. All you need to do is flash a no-wipe firmware.zip and be done.
Will either of those methods, RUU or "full stock backup", allow me not to have to reinstall apps and data? Because I thought they both would. And when you say "full stock backup" what partitions exactly do you mean? I took a full backup after my last OTA but I don't want to wipe out apps and data ideally. Appreciate the help!