Related
:beer:This is very simple.
1) Get Root first in v.19
2) Go there and read what is about it: http://forum.xda-developers.com/showthread.php?p=17117779
3) Download from market Voodo OTA RootKeeper.
4) Install Voodo OTA RootKeeper and run the application and make a backup of your root.
5) Go to settings/about tablet/system firmware update/check update
6) Follow regular update procedure
7) After reboot open Voodo OTA RootKeeper and restore root.
8) Be happy with the new updated tablet and with working root.
Thanks to supercurio for his tools and application.
This has been done on TF101 US v19 B80 series
Sent from my Transformer TF101 using Tapatalk
goodoane said:
:beer:This is very simple.
1) Get Root first in v.19
2) Go there and read what is about it: http://forum.xda-developers.com/showthread.php?p=17117779
3) Download from market Voodo OTA RootKeeper.
4) Install Voodo OTA RootKeeper and run the application and make a backup of your root.
5) Go to settings/about tablet/system firmware update/check update
6) Follow regular update procedure
7) After reboot open Voodo OTA RootKeeper and restore root.
8) Be happy with the new updated tablet and with working root.
Thanks to supercurio for his tools and application.
This has been done on TF101 US v19 B80 series
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
that is just pure craziness... whatever works though... but if you dont flash a custom rom there's always a chance u can lose root with asus's updates and such... pretty smart peeps if they wanna lock it down gonna be hard to get back in.. i dont flash **** unless it comes through a dev first just to be safe....
Sent from my Revolver Powered Asus Transformer
or just flash a rom that has been updated to the 21 base firmware.. like revolver.
KingDavid63 said:
that is just pure craziness... whatever works though... but if you dont flash a custom rom there's always a chance u can lose root with asus's updates and such... pretty smart peeps if they wanna lock it down gonna be hard to get back in.. i dont flash **** unless it comes through a dev first just to be safe....
Sent from my Revolver Powered Asus Transformer
Click to expand...
Click to collapse
OTA Rootkeeper will only not work if the complete /system partition is wiped. At the moment this is not the case with current OTA updates.
Can you apply this method and update a rom in specifc prime rom. Thanks in advance
Worked as advertised on my B70. I had frozen DMClient using Titanium Backup so it didn't keep bugging me about the update. However when I thawed it out while applying the above procedure the transfomer told me I had an update and to click the notification in the bar, but there wasn't one (notification). A reboot brought things back the way they should be and I was able to click on the notification and complete the process.
Could I request the OP keep this thread up to date as to whether it is effective on future updates where ASUS tries to take away root (thinking particularly of possible ICS).
I will keep this update if we gonna have new updates.
Sent from my GT-I9000 using Tapatalk
Has anyone been successful in update their Nexus 7 device with the following configuration:
1. Stock ROM
2. Rooted
3. SuperSU v0.98 (recently updated)
4. Voodoo RootKeeper
5. DPI set to 160, need confirmation but assuming this needs to be reverted back to 213
I have been viewing other posts of successful upgrades but with prior versions of SuperSU, so I was hoping i could find that one person who has the above configuration and was successful in updating.
Thanks,
JBIRD
Apart from 4, the Rootkeeper, that was my setup when I updated from 4.1.2 via the 4.2 OTA (adb sideload).
Worked fine.
Re-rooted using superboot and am happycat ever since.
SuperSU (updated) kills multiuser on my 4.2.
Even setting up a new user took over 15 minutes.
I kept getting SU requests from the new user for /system/bin/id. Why id was calling SU I have no idea - but it is a killer.
I was not able to recover until I used Voodoo RootKeeper to temporarily unroot. That fixed it. Multiuser performance is great now.
I will not use SuperSU again until a full fix is released. Really don't need root anyway until stickmount is fixed.
rmm200 said:
SuperSU (updated) kills multiuser on my 4.2.
Even setting up a new user took over 15 minutes.
I kept getting SU requests from the new user for /system/bin/id. Why id was calling SU I have no idea - but it is a killer.
I was not able to recover until I used Voodoo RootKeeper to temporarily unroot. That fixed it. Multiuser performance is great now.
I will not use SuperSU again until a full fix is released. Really don't need root anyway until stickmount is fixed.
Click to expand...
Click to collapse
Thanks for the information. So do you recommend removing superSU and root from the device prior to upgrading?
jbird92113 said:
Thanks for the information. So do you recommend removing superSU and root from the device prior to upgrading?
Click to expand...
Click to collapse
No - keep SuperSU and RootKeeper.
As always - use RootKeeper to temporarily unroot before the upgrade.
After the upgrade, just wait for Chainfire to release an update before restoring root.
Actually - SuperSU seemed to work fine until I tried adding a second user. Only the multi user scenario gave me trouble.
rmm200 said:
No - keep SuperSU and RootKeeper.
As always - use RootKeeper to temporarily unroot before the upgrade.
After the upgrade, just wait for Chainfire to release an update before restoring root.
Actually - SuperSU seemed to work fine until I tried adding a second user. Only the multi user scenario gave me trouble.
Click to expand...
Click to collapse
Thanks again. Sorry for the newbie questions but to confirm, I choose Temp. Un-root button in rootkeeper prior to the upgrade then run the OTA update?
jbird92113 said:
Thanks again. Sorry for the newbie questions but to confirm, I choose Temp. Un-root button in rootkeeper prior to the upgrade then run the OTA update?
Click to expand...
Click to collapse
Yes!
rmm200 said:
Yes!
Click to expand...
Click to collapse
One last thing, I changed my DPI settings to 160, do I need to revert to back to 213...
I am not the right person to answer - but if buildprops is anything other than stock the update will fail. Think install checks the checksum.
Sent from my Nexus 7 using xda app-developers app
rmm200 said:
I am not the right person to answer - but if buildprops is anything other than stock the update will fail. Think install checks the checksum.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Do you recommend to be on the safe side that I disable supersu as well prior to the upgrade?
Thanks again...
Really bad things happen if you disable Supersu and someone calls su. Leave it enabled and temporarily unroot.
Sent from my Nexus 7 using xda app-developers app
Oh, you didn't mention you were on Safestrap. That may bring up some additional issues. And you do need to revert your build.prop to the original. With any luck, you have a build.prop.bak that you can restore. SuperSU hasn't caused me any problems, but I don't use multi-user.
rmm200 said:
Really bad things happen if you disable Supersu and someone calls su. Leave it enabled and temporarily unroot.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Will follow your directions. I do have other apps that require root, once I update can I use the rootkeeper to re-enable root?
Thanks again for all your help..
jbird92113 said:
Will follow your directions. I do have other apps that require root, once I update can I use the rootkeeper to re-enable root?
Click to expand...
Click to collapse
If it was me - I would not have root enabled while on a secondary user.
I am sure SuperSU will be fixed in short order.
If you use MSkips Nexus 7 Toolkit and use option 8 it will not only unlock the boot loader, but root, install busy box, your choice of either cwm or twrp, recommends using the 3.34 bootloader, and recommends using SuperSu 0.98 due to problems with superuser not being updated yet. I can attest to the fact that the 4.13 bootloader causes root issues. At least on my 7. Apparently that isn't so on all 7s.
Sent from my Nexus 7 using xda premium
rmm200 said:
If it was me - I would not have root enabled while on a secondary user.
I am sure SuperSU will be fixed in short order.
Click to expand...
Click to collapse
I am not going to use the multiuser feature as I am the only one who uses the tablet. Will rerooting work on the primary user?
Seems to work fine.
Sent from my Nexus 7 using xda app-developers app
So if I try to update to 4.2 AFTER updating supersu to v0.98 it will fail for sure? Still waiting for stickmount *fingers crossed* and Google to fix Bluetooth before I even attempt 4.2 anyway. Would uninstalling updates for supersu through app info/settings work? Tia
Sent from my Nexus 7 using xda premium
Gigabitex2 said:
So if I try to update to 4.2 AFTER updating supersu to v0.98 it will fail for sure? Still waiting for stickmount *fingers crossed* and Google to fix Bluetooth before I even attempt 4.2 anyway. Would uninstalling updates for supersu through app info/settings work? Tia
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Only problems I have seen are trying to set up / use a second user while rooted.
Stay away from multi-user and you should be fine.
Note - problems I have reported with SuperSU may just be related to multiuser and root, no matter how you get root.
I have not tried the "superuser" app, so I have no idea if the problems will be the same.
Hi guys, I just updated my N7 to 4.2 and I lost root during the process. I made a su backup with Voodoo OTA rootkeeper before I did the install. After the install was complete, went back into voodoo to restore root, rebooted, and did a root check using 3 different apps. Voodoo shows my device rooted and root checker and titanium backup cannot find my root access. Is there something I did wrong, and is there any way to restore root access without a fresh wipe. Thanks in advanced!!!
Try uninstalling your root App and then reinstalling it. You also might want to wipe cache and data for your root App in Apps under Settings. Do this before uninstalling.
If that doesn't work push root to your device using one of the many methods available.
Sent from my Nexus 7 using xda premium
ezas said:
Try uninstalling your root App and then reinstalling it. You also might want to wipe cache and data for your root App in Apps under Settings. Do this before uninstalling.
If that doesn't work push root to your device using one of the many methods available.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I tried that with no luck. I am trying Wug's toolkit right now, but android 4.2 doesn't show up under the model list.
Need to push the superuser app via fastboot. Either adb or use wugs toolkit.
Sent from my Nexus 7 using Tapatalk 2
Testingchip said:
Need to push the superuser app via fastboot. Either adb or use wugs toolkit.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Wugs worked perfectly. THANKS!! For anyone who is having the same problem, I used wugs toolkit, and I chose Nexus 7 "any build type" under the model type.
Glad you got it. I did the update at work and had the same problem till I got home to the pc.
Sent from my Galaxy Nexus using Tapatalk 2
silentbeatz said:
Wugs worked perfectly. THANKS!! For anyone who is having the same problem, I used wugs toolkit, and I chose Nexus 7 "any build type" under the model type.
Click to expand...
Click to collapse
I hesitate asking thjis but being greener than grass I need you if you would please explain in very noob terms how to push superuser in Wugs. I use the tool kit and was sucsefully rooted in 4.1.2 but the "upgrade" to 4.2 has brought me back to square one and having spent the money on apps like titanium backup I would like to one again use them. Thanks and sorry to be so needy but I'm trying.
patience1 said:
I hesitate asking thjis but being greener than grass I need you if you would please explain in very noob terms how to push superuser in Wugs. I use the tool kit and was sucsefully rooted in 4.1.2 but the "upgrade" to 4.2 has brought me back to square one and having spent the money on apps like titanium backup I would like to one again use them. Thanks and sorry to be so needy but I'm trying.
Click to expand...
Click to collapse
I ran into same problem, if you use Wug Toolkit, make sure you set to "android Anybuild". this Toolkit is not yet updated for 4.2.
There is another Nexus Toolkit by Mark Skippen which was updated to 4.2, however you need to donate to get the latest version. It works well for me
It's woth the donation of Pounds 5 or $8++ something
Good Luck
dominicvn said:
I ran into same problem, if you use Wug Toolkit, make sure you set to "android Anybuild". this Toolkit is not yet updated for 4.2.
There is another Nexus Toolkit by Mark Skippen which was updated to 4.2, however you need to donate to get the latest version. It works well for me
It's woth the donation of Pounds 5 or $8++ something
Good Luck
Click to expand...
Click to collapse
All fine and dandy and I dont mind spending the money but if I use Wugs do i just plug in to the computer open Wugs choose any build and then hit root? TIA and thanks for responding. Like I said NOOB
silentbeatz said:
Hi guys, I just updated my N7 to 4.2 and I lost root during the process. I made a su backup with Voodoo OTA rootkeeper before I did the install. After the install was complete, went back into voodoo to restore root, rebooted, and did a root check using 3 different apps. Voodoo shows my device rooted and root checker and titanium backup cannot find my root access. Is there something I did wrong, and is there any way to restore root access without a fresh wipe. Thanks in advanced!!!
Click to expand...
Click to collapse
Hi did you by any change have SuperSU v.0.98 installed prior to the upgrade with survival mode enabled?
Thanks,
JBIRD
I apologize in advance if this has been answered or if I have inadvertently offended. I did watch the video and have developed OSes for 30 years. I also have searched all over this site and the web for resolution and am making no progress, so I'm asking the 'oracle'
Got an ATT S4 (I337) a week ago - it was running UCUAMDL. I rooted it using Motochopper and was happily using Titanium Pro etc. I get notified of OTA update. OTA update downloads (357MB) yet fails during install at 30% consistsently.
I figure it is unhappy with my root - I unrooted and cannot remember which way I did it - I seem to recall SuperSU I was using did not have the built-in 'unroot' support so I grabbed the stock image and used ODIN to flash it.I also may have manually uninstalled the 'normal' way the SU app - I suspect this may be my real problem.
After flashing stock ROM for UCUAMDL phone was no longer rooted, did not say custom etc, and took the OTA upgrade just fine. This was for UCUAMF3 which did add App 2 SD support - BTW this update used another 1G of storage compared to UCUAMDL, and I could not recover the 1G by moving apps either, making it virtually worthless as far as adding support for apps in SD, lol.
The problem is now I cannot seem to get the device rooted again. Motochopper fails when installing su.apk. I suspect I have screwed the pooch - what do I need to do to get this thing rooted again?
Is it typical for an OTA update to fail 'because' the device is rooted?
Any advice is much appreciated.
You can't root mf3. You never should have taken the update if you want to be rooted. Cross your fingers that someone finds a way to root the update but I'm not sure you should hold your breath.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
So is doing a stockrom restore back to MDL an option? Then just root that with Motochopper? And disable OTA updates till its figured out?
The real joke here is that to get their built in app-to-sd functionality they give you an update that hogs up another 1GB!
Nope. Can't go back. Just gotta wait it out. Cheers
Just curious if you don't mind - WHY can't you go back? (Ready for the explanation based on perms and su etc, lol) Or flash stock ROM and factory reset etc?
TheKog said:
Just curious if you don't mind - WHY can't you go back? (Ready for the explanation based on perms and su etc, lol) Or flash stock ROM and factory reset etc?
Click to expand...
Click to collapse
A qfuse is blown when you take the update. It won't let you odin or anything else to go back to an earlier firmware.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Just thought people might like to know if you unroot via motoroot or pwnmymoto and then install the OTA, the entitlement hack sticks through the update. I only rooted for that reason and now that it stuck I don't need to re-root!
Sent from my XT1080 using Tapatalk
ssgtob1 said:
Just thought people might like to know if you unroot via motoroot or pwnmymoto and then install the OTA, the entitlement hack sticks through the update. I only rooted for that reason and now that it stuck I don't need to re-root!
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Yes you are correct it was this way on the droid razr throughout all the updates that I did. Anyways you can still have the joy in testing and go ahead and root it you can always hide root after rooting.
ssgtob1 said:
Just thought people might like to know if you unroot via motoroot or pwnmymoto and then install the OTA, the entitlement hack sticks through the update. I only rooted for that reason and now that it stuck I don't need to re-root!
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Okay, this is exactly what I would like to do to my Maxx. Don't really use root except for the wireless tether hack. What is the entire process you did if you don't mind me asking? I am currently rooted using pwnmymoto. Does it go something like this:
1. Download update.
2. Place file in correct location.
3. Unroot using pwnmymoto
4. Install update.
5. Enjoy Droid Maxx with tether and newest OTA Update.
Sent from my XT1080 using xda app-developers app
ssgtob1 said:
Just thought people might like to know if you unroot via motoroot or pwnmymoto and then install the OTA, the entitlement hack sticks through the update. I only rooted for that reason and now that it stuck I don't need to re-root!
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
Can you tell us more about your setup? do you have a custom recovery? Are there any other system modifications? I am rooted with root my moto, & I have the entitlement hack, but I do not have a custom recovery. Were you pushed ota or did you download it from another source? the information is appreciated.
No customs recovery....I clicked unroot from the menu in motoroot and flashed the update zip from stock recovery. No other system mods.
Sent from my XT1080 using Tapatalk
---------- Post added at 07:23 PM ---------- Previous post was at 06:31 PM ----------
[/COLOR]
DroidJoe said:
Cool! Thats great news. Im going to do it and post results since i, and many otyhers are in the same boat. But, for us noobs out there, can you list the steps with a little more detail? Basically, start with pre-reqs, file download info, correct folder location, etc. I'll do it if you want?
Click to expand...
Click to collapse
I'm impatient: here we go.....this is what I did, it worked for me. As always, I'm not responsible for bricked phones...yada, yada, yada, proceeded at your own risk.
Prereqs: Maxx with original 4.2.2, MotoRoot 1.1 by Jcase, entitlement hack optional for free hotspot, no mod recovery, safestrap or non-stock bootloader installed. (If you do, follow instructions posted by AndrewC 2 posts below. Cheers!)
1. Download update. ( http://forum.xda-developers.com/showthread.php?t=2513563). Thanks Kickbut101.
2. Place file in correct location. (Copied from download file to sdcard file using esfile explorer while rooted)
3. Unroot using motoroot 1.1 (reboots phone, once powered up, you need to power down again).
4. Install update. (First, while holding *down* volume key, then press and hold power 5 seconds. Boots to recovery. Go down one to "recovery" and hit volume up to select. May be tricky. Find sdcard ota update file and hit power to select. Should install. Sit back and enjoy your fav beverage for about 2 or 3 minutes.
5. Enjoy Droid Maxx with tether and newest OTA Update.
I was told that I do not need to unroot if I am rooted via motoroot. Is that true?
If I do have to unroot before the ota, can I reroot afterwards using Motoroot?
Sent from my XT1080 using Tapatalk
Piaband said:
I was told that I do not need to unroot if I am rooted via motoroot. Is that true?
If I do have to unroot before the ota, can I reroot afterwards using Motoroot?
Sent from my XT1080 using Tapatalk
Click to expand...
Click to collapse
You have to unroot if you want your phone to not bootloop once you take the OTA. Afterwards you can use RockMyMoto to root again.
Unroot using House of Moto
Root after OTA update using RockMyMoto
Check here to download the OTA
Andrew C said:
You have to unroot if you want your phone to not bootloop once you take the OTA. Afterwards you can use RockMyMoto to root again.
Unroot using House of Moto
Root after OTA update using RockMyMoto
Check here to download the OTA
Click to expand...
Click to collapse
I'm sorry. I don't understand a few things.
Why cant I just unroot using the Motoroot app that I rooted with? Are you sure Motoroot'ed phones need to be unrooted. This was the early root provided by jCase, it doesnt have anything to do with safestrap, the bootloader, or the recovery.
I'm getting some conflicting info here and I don't want to cause myself any headaches when I accept the OTA. I really appreciate the help.
I really wish jCase or someone would go over all of the root methods and how to OTA update with each one. I just feel like there has been a lot of different root methods that have come out.
Piaband said:
I'm sorry. I don't understand a few things.
Why cant I just unroot using the Motoroot app that I rooted with? Are you sure Motoroot'ed phones need to be unrooted. This was the early root provided by jCase, it doesnt have anything to do with safestrap, the bootloader, or the recovery.
I'm getting some conflicting info here and I don't want to cause myself any headaches when I accept the OTA. I really appreciate the help.
I really wish jCase or someone would go over all of the root methods and how to OTA update with each one. I just feel like there has been a lot of different root methods that have come out.
Click to expand...
Click to collapse
If you want to be able to update to the latest OTA then you will have to follow the steps provided in the links to get back to a stock system. There are no if, and, or buts about it. When you used the MotoRoot/PwnMyMoto exploit you wiped out your stock recovery. No recovery=bootloop. The only root methods available are PwnMyMoto and RockMyMoto (will work with new OTA) both by jcase.
Again, not responsible for a bricked phone, but all I had to do was use the motoroot app by Jcase to unroot after putting the ota file on my sdcard. The unroot option reboots to non-root. I powered down and booted into recovery and applied the ota zip file. That was it. No boot loops. I had no system or framework changes, and no moded recovery. Just the entitlement hack. Worked no problem. House of moto is a safe precautionary step to take but it was unnecessary in my case. YMMV.
For some reason I am unable to unroot. I have tried multiple times. I have launched the unroot option from motoroot and rebooted over and over again. I also downloaded pwnmymoto to try there but no luck.
Any one know another way to unroot? I just want to keep the entitlement hack if possible. Worst thing about all this is my phone downloaded the update so I keep getting a message to install it.
Sent from my XT1080 using xda app-developers app
Nathanjb7 said:
For some reason I am unable to unroot. I have tried multiple times. I have launched the unroot option from motoroot and rebooted over and over again. I also downloaded pwnmymoto to try there but no luck.
Any one know another way to unroot? I just want to keep the entitlement hack if possible. Worst thing about all this is my phone downloaded the update so I keep getting a message to install it.
Sent from my XT1080 using xda app-developers app
Click to expand...
Click to collapse
That's weird. It has worked for me multiple times.
I think you're best option is probably to fxz with saved data. That takes you back to stock. So I don't think it will keep the mobile hotspot.
Sent from my XT1080 using Tapatalk
I just want to post for those of you that rooted via Motoroot v1.1. This was the original root solution provided by Jcase.
I have updated my Maxx without removing root and it worked just fine.
I was rooted via Motoroot v1.1, I have the mobile hotspot hack running, and some apps that use root. No other changes were made to my device.
The update installed perfectly, my device still has root access and the mobile hotspot hack intact.
***warning*** Motoroot is different than the root solutions jCase provided later on that changed the recovery/hboot partitions. If you don't know what you're doing, you might be better off to FXZ to unrooted device before installing the update.
Piaband said:
I just want to post for those of you that rooted via Motoroot v1.1. This was the original root solution provided by Jcase.
I have updated my Maxx without removing root and it worked just fine.
I was rooted via Motoroot v1.1, I have the mobile hotspot hack running, and some apps that use root. No other changes were made to my device.
The update installed perfectly, my device still has root access and the mobile hotspot hack intact.
***warning*** Motoroot is different than the root solutions jCase provided later on that changed the recovery/hboot partitions. If you don't know what you're doing, you might be better off to FXZ to unrooted device before installing the update.
Click to expand...
Click to collapse
i am in the same situation, rooted with just motoroot and i can confirm that i just ran the ota and it went through with no issues and was able to retain root.
Andrew C said:
If you want to be able to update to the latest OTA then you will have to follow the steps provided in the links to get back to a stock system. There are no if, and, or buts about it. When you used the MotoRoot/PwnMyMoto exploit you wiped out your stock recovery. No recovery=bootloop. The only root methods available are PwnMyMoto and RockMyMoto (will work with new OTA) both by jcase.
Click to expand...
Click to collapse
That's not correct: MotoRoot DOES NOT replace the stock recovery - PwmMyMoto DOES.
If you were rooted with MotoRoot - you dont need to do anything to take the update. You can take it even while rooted.
If you were rooted with PwnMyMoto - then yes, you need to unroot and flash the stock recovery.
Anyone have this working on Maxx with 4.4 update, I am unable to locate the entitlement check location.
SDC_Bolts said:
Anyone have this working on Maxx with 4.4 update, I am unable to locate the entitlement check location.
Click to expand...
Click to collapse
Thank baby jesus and buy me a beer.
http://forum.xda-developers.com/showthread.php?p=48680232#post48680232
CrazyRussianXDA said:
That's not correct: MotoRoot DOES NOT replace the stock recovery - PwmMyMoto DOES.
If you were rooted with MotoRoot - you dont need to do anything to take the update. You can take it even while rooted.
If you were rooted with PwnMyMoto - then yes, you need to unroot and flash the stock recovery.
Click to expand...
Click to collapse
Has anyone taken the 4.4 update with motoroot yet? results? I took the camera update with motoroot and still rooted. I like it cause my /system is still write protected and i can still 1 click unroot if need be.