Related
How many of you have tried updating to a new firmware and you got the yellow exclamation mark?
Well, you probably have a combination of these modifications:
Custom Kernel
ClockworkMod Recovery
Rooted
If you have any of these, this is what you should do.
First, download and run this ONLY FOR INSTALLING/UNINSTALLING STOCK/CLOCKWORKMOD RECOVERY. - Thread
Read the instructions on how to boot into APX Mode.
Backup your /data with CWM.
After you have backed up your data, you should restore the STOCK ROM of your device.
When you get an update, it /should/ complete without any errors.
DO NOT DO ANYTHING TO THE ROM AT THIS POINT.
Alright. So at this point, you should have a completely stock, updated ROM.
Here are the next steps.
DO NOT ROOT YOUR ROM. DO NOT CHANGE A KERNEL.
Boot into APX Mode.
Make a backup of the STOCK Recovery. (Download From Linked Thread If You Haven't.)
Reboot into APX Mode.
Install ClockworkMod Recovery. (Using Brk's RootKit Script.) Once again. Without Rooting. Without changing the kernel.
Update ClockworkMod Recovery to 3.2.0.1. - Thread
Make a backup of EVERYTHING. (boot, system, data, cache, sd-ext).
After the backup is complete, you can ROOT and install a custom Kernel.
When You Get A New Update: DO NOT INSTALL. DO NOT POSTPONE.
Boot into ClockworkMod Recovery.
Restore the stock Boot.
Restore the stock System.
Boot into APX.
Restore stock recovery. (Using Brk's RootKit Script.)
Now everything should be back to stock.
Your data should still be intact.
When you apply the update, it should complete without a hitch.
Complete these steps again to be ready for the next update.
Cheers.
Thanks !! This did the trick for me. Had previously un-rooted and lost the update. Couldnt get it back until I did this !
I have a question.
I used the root method mentioned above a few weeks ago and everything went perfectly. I did not install CWM, only root.
I used the Netflix hack but managed to erase the original lib file.
I received the update and got the yellow exclamation point.
Last night I used BRK's pure root method and attempted to restore boot image and recovery image hoping it would return my lost lib file. I did not attempt to unroot.
When you mention "stock rom", where do I find the stock US rom?
I have an Epic 4G and run custom roms but I think the Transformer is fine and honestly don't care about root now that Netflix and ad-hoc appear to be working. I would like to end up with a stock Transformer that receives regular updates.
Is this the method for me, or something else?
Thanks
bmcgarry67 said:
I have a question.
I used the root method mentioned above a few weeks ago and everything went perfectly. I did not install CWM, only root.
I used the Netflix hack but managed to erase the original lib file.
I received the update and got the yellow exclamation point.
Last night I used BRK's pure root method and attempted to restore boot image and recovery image hoping it would return my lost lib file. I did not attempt to unroot.
When you mention "stock rom", where do I find the stock US rom?
I have an Epic 4G and run custom roms but I think the Transformer is fine and honestly don't care about root now that Netflix and ad-hoc appear to be working. I would like to end up with a stock Transformer that receives regular updates.
Is this the method for me, or something else?
Thanks
Click to expand...
Click to collapse
You should go here: http://tabletroms.com/forums/transf...stock-3-2-recovery-roms-unbricking-tools.html
Make sure you backup your data for your applications and the internal sdcard. They will be erased.
Install the 8.4.4.5.
Then you should go here and update to the latest version they have available.
Follow the instructions for this.
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
Select Android and download your firmware.
Then you should get your update working after that.
Use this guide, then restore your data using clockworkmod.
Thanks and follow up
The Dark Lestat said:
You should go here:
Make sure you backup your data for your applications and the internal sdcard. They will be erased.
Install the 8.4.4.5.
Then you should go here and update to the latest version they have available.
Follow the instructions for this.
Select Android and download your firmware.
Then you should get your update working after that.
Use this guide, then restore your data using clockworkmod.
Click to expand...
Click to collapse
I just had a couple of questions?
You mentioned updating to 8.4.4.5, them updating to 8.6.5.6.
They have the NVFlash with 8.6.5.6. Has that changed since you advised me or should I do it in 2 steps?
Do I download the Asus Rom to the transformer or download to computer, then copy to SD card to install?
Now, I just noticed that 8.6.5.9US is available from Asus. Does this change my procedure?
Thanks again
bmcgarry67 said:
I just had a couple of questions?
You mentioned updating to 8.4.4.5, them updating to 8.6.5.6.
They have the NVFlash with 8.6.5.6. Has that changed since you advised me or should I do it in 2 steps?
Do I download the Asus Rom to the transformer or download to computer, then copy to SD card to install?
Now, I just noticed that 8.6.5.9US is available from Asus. Does this change my procedure?
Thanks again
Click to expand...
Click to collapse
When I NVFlashed to 8.6.5.6, I could not receive the update.
Since I used the file from Asus to update, it enabled FOTA somehow.
Anyways, the guide is the same.
If 8.6.5.6 is available, then you can NVFlash 8.6.5.6, then download and update to 8.6.5.9
Thank you.
I NVFlashed to 8.6.5.6 and wiped everything.
The FOTA arrived immediately and updated flawlessly.
Thanks again
Is this update even worth unrooting then root again?
it does fix the issue with browser shortcuts. You no longer have to rotate the screen.
I have not played with it. But it is said to allow Netflix and adhoc without root and patches. Those were the 2 reasons that I rooted.
Why jump through all these hoops?
Step 1: Download the clockworkmod update posted.
Step 2: Flash it.
daoist said:
Why jump through all these hoops?
Step 1: Download the clockworkmod update posted.
Step 2: Flash it.
Click to expand...
Click to collapse
Because if you do that, for some reason, FOTA doesn't enable.
AND you will have to wait for a flashible zip to become available.
Not hoops.
I've already tested that route. It didn't work for me.
bmcgarry67 said:
I have not played with it. But it is said to allow Netflix and adhoc without root and patches. Those were the 2 reasons that I rooted.
Click to expand...
Click to collapse
Has this been verified?
pigskins said:
Has this been verified?
Click to expand...
Click to collapse
Verified.
Netflix and Adhoc work WITHOUT root.
No need to root for those two options.
I personally root because of Titanium Backup.
Even if I have CWM installed.
The Dark Lestat said:
Verified.
Netflix and Adhoc work WITHOUT root.
No need to root for those two options.
I personally root because of Titanium Backup.
Even if I have CWM installed.
Click to expand...
Click to collapse
TY!
Did you root after getting the update and if so, how? Did you follow the steps in this thread?
pigskins said:
TY!
Did you root after getting the update and if so, how? Did you follow the steps in this thread?
Click to expand...
Click to collapse
Yes. The thread that I posted has all the updated CWM and Root methods. You can use those to root.
The Dark Lestat said:
Because if you do that, for some reason, FOTA doesn't enable.
AND you will have to wait for a flashible zip to become available.
Not hoops.
I've already tested that route. It didn't work for me.
Click to expand...
Click to collapse
Why do you want FOTA enabled?
Why be bothered when a release that won't work (without jumping through hoops) is available?
The whole point of installing CWM is that you're going to be managing your tablet rather than letting ASUS do it. If you're going to unroot, FOTA, and reroot every time, just leave it unrooted.
I had successfully update my transformer through OTA without doing all those steps. I just had to root it again after update is done.
daoist said:
Why do you want FOTA enabled?
Why be bothered when a release that won't work (without jumping through hoops) is available?
The whole point of installing CWM is that you're going to be managing your tablet rather than letting ASUS do it. If you're going to unroot, FOTA, and reroot every time, just leave it unrooted.
Click to expand...
Click to collapse
You don't have to root to use CWM. FOTA won't work with CWM.
I use Root only for setCPU and Titanium.
I like getting the update as soon as possible. Not waiting a couple days for it.
Sei911 said:
I had successfully update my transformer through OTA without doing all those steps. I just had to root it again after update is done.
Click to expand...
Click to collapse
If you just rooted and did not make any changes to the system, then in theory, it should work. Depending on the root method.
[TIPS AND DISCUSS] ICS update DOES NOT *ALWAYS* BREAK ROOT (& other tips and reviews)
This is not intended to be a bug-sharing thread, report them if you wish, but I'm sure there will be entire threads devoted to this, so keep this in mind when posting.
Yep, that's all I had to say, but if I posted in any of the ICS threads it would be buried. Dlpkgfile available HERE NOW!
luna_c666 said:
Yep, that's all I had to say, but if I posted in any of the ICS threads it would be buried. Dlpkgfile available HERE NOW!
Click to expand...
Click to collapse
Cheers luna ... just need a WW version
Noob question though ..... I am on a custom ROM. I have CWM recovery.
I thought I couldnt update OTA if my TF was rooted ? or is it that I have the custom recovery that prevents this ?
I can flash back to stock easily - its removing CWM and unrooting that looked to be the more techie issue.
With what you are saying is there an easy way, once I have reverted to stock ROM, to revert to stock recovery without losing root ? Or do i even need to revert to stock ROM ??
Can update if rooted, but need to be on a stock ROM and stock Recovery image in order to successfully install. Download the 8.2.3.5 US recovery file located here :http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/, flash it through CWM and you have now overwritten your CWM and gone back to stock. Ready to update from there. Cheers!
so what is the procedure to update? Rename it, put it in microsd root and reboot into recovery?
another question, i cannot root with nachoroot, so is it possible to root with 1-click root?
asder00 said:
so what is the procedure to update? Rename it, put it in microsd root and reboot into recovery?
Click to expand...
Click to collapse
That might work, I don't know exactly because I got the FOTA pushed to my device and updated through the 'official' update process. I honestly have no idea how the dlpkgfile is even packaged, if it is CWM flashable or requires stock recovery etc., honestly my first time fooling with capturing the OTA files.
Ok I'm trying and I will tell u....
I don't care about root right now...
luna_c666 said:
Can update if rooted, but need to be on a stock ROM and stock Recovery image in order to successfully install. Download the 8.2.3.5 US recovery file located here :http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/, flash it through CWM and you have now overwritten your CWM and gone back to stock. Ready to update from there. Cheers!
Click to expand...
Click to collapse
Do I understand correctly that I only have to do Step 7 of the tutorial? and then install ICS (regular update process)?
I am rooted and I have CWM (no custom ROM)
So first impressions luna? Might as well start a discussion to keep the post on top and visible.
Did you run Spark? If so how does it compare?
Positives negatvies
Yes I do realise that you have had it for like 12 seconds but first impressions are nice.
Sent from my Sparkified TF101
Dreamboxuser said:
So first impressions luna? Might as well start a discussion to keep the post on top and visible.
Did you run Spark? If so how does it compare?
Positives negatvies
Yes I do realise that you have had it for like 12 seconds but first impressions are nice.
Sent from my Sparkified TF101
Click to expand...
Click to collapse
Unfortunately I never did get around to trying the latest Spark, I saw the complaints about touchscreen issues and decided it might be best to wait for Paul to work it out, but Asus finally got the upper hand on him!
Seems a treat, but I expected as you can see I've been running CM9 on my epic for about 3 weeks now. Much snappier, generic comments that have already been posted- but not explored completely yet, too busy helping others get their own ICS since the update came in to be selfish and sign off yet
Steven, I'm not sure which step 7 you are referring to but you will need a stock recovery in order to flash the file. CWM will flash files that have been repacked for CWM usually, and OTA updates install from the cache partition so CWM will not be able to install the OTA. CWM can flash it manually, I THINK (not sure if it needs to be repackaged for that to occur or not), but CWM will not install the OTA through the normal OTA process.
luna_c666 said:
Steven, I'm not sure which step 7 you are referring to but you will need a stock recovery in order to flash the file. CWM will flash files that have been repacked for CWM usually, and OTA updates install from the cache partition so CWM will not be able to install the OTA. CWM can flash it manually, I THINK (not sure if it needs to be repackaged for that to occur or not), but CWM will not install the OTA through the normal OTA process.
Click to expand...
Click to collapse
I was refering to step 7 on the Unlocker page you pointed to:
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
So in short only replace the recovery as explained in pojnt 7 (and 8) of that page and then do a regular system update to ICS.
No need to unroot??
Will this keep my apps and settings? I do have Titanium so I can do a backup and restore that way.
Thanks a lot for helping!!
Steven_nl said:
I was refering to step 7 on the Unlocker page you pointed to:
http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
So in short only replace the recovery as explained in pojnt 7 (and 8) of that page and then do a regular system update to ICS.
No need to unroot??
Will this keep my apps and settings? I do have Titanium so I can do a backup and restore that way.
Thanks a lot for helping!!
Click to expand...
Click to collapse
Yes, your apps and data should remain intact, and that is correct, you only need to flash the recovery back to stock if you are already on a stock ROM. As of right now, only US and TW firmware versions are getting the OTA pushed to their device, but if you are not one of these you can manually flash to these stock ROMs via CWM if need be. But yes, if you are stock + root + CWM, you only need to flash over CWM back to stock. Root is fine to keep and all data will be saved (it is an official update, people would be irate if it wiped their data you know!)
Great stuff thanks again. I'n in Europe so I might need to wait for a bit but that is fine.
No problem. Ok guys, I've done a bunch of talking and answered quite a few PMs, and posted all my methods/experience with ICS so far, now, I'm going to go play for a while (it's 7am, and I've not been to bed, and I have to work at 4pm and my son will likely be up in an hour, so no sleep for me today, should have a well-rounded review by the time you see me again)
If you guys want to keep this thread alive, have at it! Turn it into a discussion.. See you guys in a while, can't wait to see what I miss while I'm gone
Well I did the update with root disabled with rootkeeper but now rootkeeper will not restore Root.
I guess I should of read thi before updating
Anyone in the same state?
dmazyn said:
Well I did the update with root disabled with rootkeeper but now rootkeeper will not restore Root.
I guess I should of read thi before updating
Anyone in the same state?
Click to expand...
Click to collapse
If you are SBK1 device you can flash CWM via NVFlash, use CWM to flash SU binary from ChainsDD (located HERE ) and then flash the stock recovery if you so choose to return to stock recovery (in case any patches or incremental updates come out you may need this if you want to stay stock ICS).
ONE MORE THING BEFORE I GO GUYS;
I just noticed that ICS brings a new recovery as well, so the update will overwrite your recovery, I assume it will do this if you figure out how to flash via CWM so be prepared for that. Any devs will want to work on removing the recovery blob from the patch file before releasing as a CWM flashable zip. My 2 cents. See you guys in a few hours/days, depending on how addicted I get to ICS.
Your dlpkgfile didn't work.. i need the WW version
Anyway I've rooted with nachoroot with stock asus recovery, waiting for ics update via FOTA
asder00 said:
Your dlpkgfile didn't work.. i need the WW version
Anyway I've rooted with nachoroot with stock asus recovery, waiting for ics update via FOTA
Click to expand...
Click to collapse
You need to reflash with a US version not WW.
Sent from my Sparkified TF101
Confirmed working! thanks. too bad i have to go straight to work
Dreamboxuser said:
You need to reflash with a US version not WW.
Sent from my Sparkified TF101
Click to expand...
Click to collapse
Ur right but i prefer to wait for ww
luna_c666 said:
Yep, that's all I had to say, but if I posted in any of the ICS threads it would be buried.
Click to expand...
Click to collapse
After I updated to ICS, OTA Rootkeeper gave me the option to Restore root. Under the status section, Device rooted and Root permission granted were both unchecked until I used the Restore root option.
I just pushed the new 4.2 update via adb,
I then tried re-rooting as I lost root in the project.
I used WugFreshs at first, which said successful. I tried root check and titanium backup which both said no root access.
I then tried mikes toolkit and chose root and install busybox, all that wen through great and said successful, so I retried Tibackup and rootchecker again, both were denied root access.
This time round, rootcheck said "System Running Slow" whilst checking for root access.
What should I do?
Re-boot into recovery and clear cache etc?
Factory reset?
Both?
For some reason superuser is installed not supersu if that makes a difference?
Any help appreciated.
Wilks3y said:
I just pushed the new 4.2 update via adb,
I then tried re-rooting as I lost root in the project.
I used WugFreshs at first, which said successful. I tried root check and titanium backup which both said no root access.
I then tried mikes toolkit and chose root and install busybox, all that wen through great and said successful, so I retried Tibackup and rootchecker again, both were denied root access.
This time round, rootcheck said "System Running Slow" whilst checking for root access.
What should I do?
Re-boot into recovery and clear cache etc?
Factory reset?
Both?
For some reason superuser is installed not supersu if that makes a difference?
Any help appreciated.
Click to expand...
Click to collapse
I apply the update by doing fresh install:
-always backup your data
Then I use wug's nexus root toolkit:
-flash stock + unroot 4.1.2 jzo54k
-flash zip stock + unroot 4.2 jop40c
-change the model type to "NAKASI: Android *.*.* Any build"
-apply root
gesitkumara said:
I apply the update by doing fresh install:
-always backup your data
Then I use wug's nexus root toolkit:
-flash stock + unroot 4.1.2 jzo54k
-flash zip stock + unroot 4.2 jop40c
-change the model type to "NAKASI: Android *.*.* Any build"
-apply root
Click to expand...
Click to collapse
I applied the update over the top of 4.1.2, wiped cache and then restarted.
I then used Wug's toolkit to root, which didn't work.
So I tried Mikes, which also didnt work.
Both report the Root as being succesful, but they arent.
If I change the model to all types on Wug's, would that make a difference?
Is it worth trying a manual root?
I use the Google Nexus 7 Toolkit which was great in fixing the problems after upgrade. Flashing the previous version bootloader (I think that is what it was) solved the root problem. The hints and guidance in this application are great and have always solved my problems. No offence meant to Wug here, I just find the other application suits me better.
Sent using Tapatalk 2
Waxwrong said:
I use the Google Nexus 7 Toolkit which was great in fixing the problems after upgrade. Flashing the previous version bootloader (I think that is what it was) solved the root problem. The hints and guidance in this application are great and have always solved my problems. No offence meant to Wug here, I just find the other application suits me better.
Sent using Tapatalk 2
Click to expand...
Click to collapse
As already said, both Toolkits have been attempted and both report that its rooted, but my device tells me otherwize, as do Titanium Backup.
Can someone just give me a step by step for what I should do to gain Root again?!
Wilks3y said:
As already said, both Toolkits have been attempted and both report that its rooted, but my device tells me otherwize, as do Titanium Backup.
Can someone just give me a step by step for what I should do to gain Root again?!
Click to expand...
Click to collapse
Hi, are you using the fully updated version of Toolkit (updated to include the 4.2 stuff. When I did mine I was told to go ahead but if it didn't work the next step was to flash the 4.1 bootloader? as it was compatible with 4.2
The root with the 4.2 bootloader didn't give me root so I flashed the 4.1 bootloader and rooted again. This was successful for me. The Toolkit application gives you step by step instructions as you request as long as it is updated to do 4.2 and follow the advice you should have no problem.
I don't think you can do the full updates in the application unless you are a donater. If I remember correctly you cannot update the application unless you use the donater version. The update for 4.2 came out at almost the same time as 4.2 was being pushed to devices.
You sound cluey enough to know you must use USB debugging but many users don't realise this or the tapping on the build trick to get the developer options available so you can select USB debugging.
Sent using Tapatalk 2
Waxwrong said:
Hi, are you using the fully updated version of Toolkit (updated to include the 4.2 stuff. When I did mine I was told to go ahead but if it didn't work the next step was to flash the 4.1 bootloader? as it was compatible with 4.2
The root with the 4.2 bootloader didn't give me root so I flashed the 4.1 bootloader and rooted again. This was successful for me. The Toolkit application gives you step by step instructions as you request as long as it is updated to do 4.2 and follow the advice you should have no problem.
I don't think you can do the full updates in the application unless you are a donater. If I remember correctly you cannot update the application donate version. The update for 4.2 came out at almost the same time as 4.2 was being pushed to devices.
You sound cluey enough to know you must use USB debugging but many users don't realise this or the tapping on the build trick to get the developer options available so you can select USB debugging.
Sent using Tapatalk 2
Click to expand...
Click to collapse
Hey mate, thanks for your reply !
I downloaded both ToolKits yesterday, so I'm guessing they are the newly updated ones?
Yes my tablet has usb debugging enabled, and is put into the Camera Mode.
I will have another go tonight, and try a different way, including using the "All Models" choice you mentioned.
If this doens't work, whereabouts in the ToolKit(Wug's) if the option to downgrade HBOOT in order to try the Root method you attempted which was successful.
Again, thanks mate !
Wilks3y said:
Hey mate, thanks for your reply !
I downloaded both ToolKits yesterday, so I'm guessing they are the newly updated ones?
Yes my tablet has usb debugging enabled, and is put into the Camera Mode.
I will have another go tonight, and try a different way, including using the "All Models" choice you mentioned.
If this doens't work, whereabouts in the ToolKit(Wug's) if the option to downgrade HBOOT in order to try the Root method you attempted which was successful.
Again, thanks mate !
Click to expand...
Click to collapse
I don't use Rug's Toolkit but Mike's Toolkit (only because it is easier to follow and use because it tells you what to do at all stages). You can see if it is updated by checking whether it has functions for 4.2 - I always use it for flashing the latest roms as well as the unlocking, root, recovery, etc, all of which the Toolkit guides you through. It even downloads the roms for you.
My only question is why did you put it in camera mode, change it back.
Sent using Tapatalk 2
Just install the 4.2 that is already Stock rooted, de-odexed apps.
Install the ROM as already Stock rooted, de-odexed apps.
Here is the link for the download: http://www.scottsroms.com/downloads.php?do=file&id=288
Thanks to Scott's post http://forum.xda-developers.com/showthread.php?t=1991157
My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
rsipson said:
My 7 is unlocked and rooted, using Nexus Root Toolkit. I did an OTA to get to 4.2.1 some time ago and that went well. Root and unlock persisted. I am now getting OTA options for 4.2.2 from the System menu. First time I got and error in Android's belly. I restarted and was still in 4.2.1. System then said that I was up to date. A week or so later System told me again that OTA was available and I got the same result.
Any suggestions as to how I can do the update?
Click to expand...
Click to collapse
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
You have to restore everything except relocking bootloader ... To be able to update ...when u finish ..just re-root
Sent from my Nexus 7 using xda premium
Same thing happened to me, I had to unroot and then root again after update.
Sent from my HTC Desire S using xda app-developers app
heat361 said:
You have two choices
1. Flash the stock 4.2.2 image using fastboot from here https://developers.google.com/android/nexus/images
Or
2. Flash this in CWM recovery (note this link is for the wifi model) http://android.clients.google.com/p....signed-nakasi-JDQ39-from-JOP40D.6ece895e.zip
Click to expand...
Click to collapse
Thanks for your post. I tried this using Clockwork and got a very long error message. I will quote part of it.
assert failed_apply_patch_check("/system/bin/debuggerd", "a2323a0c8 and a lot more
This is followed by error in file
I saw something about busybox changing some system files.
Any ideas??
How do I unroot without whipping all data?
Sent from my Nexus 7 using xda app-developers app
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
bftb0 said:
Search this forum for "OTA debugged"
There are only a few threads - read them all before you take any action.
This particular problem appears to be caused by StickMount.
You don't need to delete everything, nor do you need to flash the ENTIRE stock image - only the boot.img and system.img (via fastboot) without doing a factory reset or any other wiping.
This will unroot the ROM, and (of course) prevent StickMount from working. So you should over flash a SuperSU root kit afterwards (via custom recovery).
This very same problem may recur on the next OTA - so for goodness sake's, make a nandroid backup before you re-install StickMount and give it root privileges.
Click to expand...
Click to collapse
Sorry for being a numpty... can someone put the above into a mini step by step guide for me.. I'm stuggling with the terminology.
I rooted my Nexus and have since forgotten anything techie regarding it. I have StickMount and cannot update to 4.2.2..
How do i flash boot.img and system.img via fastboot, where do i get these files from, what versions etc do i need? And over flash SuperSU root kit?
What is OTA?
Basically, I think i need a newbie guide. I am techie enough to achieve most things normally.. i just don't know the android system at all, and what i did know to be able to root it i have completely forgotten!
Any guidance would be very much appreciated. Cheers.
Hello everyone,
I noticed that this is a common problem and I realize just not that I shouldn't have just updated without informing myself.
Anyway, I checked and the root seems to be gone (checked with Root Checker, although the SU app is still there [but not working]).
I checked the fastbook and it says 'unlocked', which is good, I don't have to lose data.
How do I re-root properly?
I am using OS X at the moment and I have access to adb but, if needed, I can access a Windows computer again and use Nexus Root Toolkit again (that's what I used the first time I rooted).
I have CWM-SuperSU-v0.98.zip and recovery-clockwork-6.0.1.9-manta.img.
I checked the bootloader and it says 'no command' but it still has:
- reboot system now
- apply update from ADB
- wipe data...
- wipe cache...
Thanks in advance for any help
First thing - Nearly always you will lose root after applying an OTA - at least lately so that's not really a big deal.
Second - Get and always use the Latest version of root zip from chainfire: http://download.chainfire.eu/370/SuperSU/UPDATE-SuperSU-v1.80.zip
Or you can also just apply SuperSU from google play and you will prompted to reboot to update binaries etc. after you apply the OTA.
His blog on latest version: https://plus.google.com/+Chainfire/posts/QhrEdeJ3nqQ
I got the same problem.
I solved it by just by downgrading and upgrading back to the latest version of Cyanogenmod.
lg Darcade
I have the same problem...
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Easily got my root back using Wugfresh toolkit.
Only the paid for version of SuperSU - "Pro" will attempt to keep root after an OTA update. It worked perfectly for me on a 5, 7 and 10.
[Lemmy] said:
I have the same problem, I have installed the 4.4.3 OTA and now SuperSU stopped working.
Any advice?
Click to expand...
Click to collapse
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
gee2012 said:
Don`t use toolkits, just boot into TWRP in fastboot and reflash the latest superSU.zip and you`re rooted.
Click to expand...
Click to collapse
thats what I did by now, just with CWM instead of TWRP.
[Lemmy] said:
thats what I did by now, just with CWM instead of TWRP.
Click to expand...
Click to collapse
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
gee2012 said:
Well done mate , toolkits suck and you have no control over them. Flashing with adb gives you full control and you learn something
Click to expand...
Click to collapse
...after having to go through this over and over again with every single update I'm starting to think that having root is definitely not worth the pain.
If you switch to TWRP using its built in SuperSU install makes re-rooting a breeze.
Sent from my SM-T800 using XDA Premium HD app