Related
I am very sorry for what is certainly a stupid question, but if it is any consolation I DID search and read through threads until my head hurt prior to posting.
1) What is the best way to apply the new OTA 4.2 update for those with rooted Nexus 7 tablet.
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work? And if not, is there a good working alternative for streaming mkv h264 movies to MXPlayer (or other player)?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
hinsdale1 said:
I am very sorry for what is certainly a stupid question, but if it is any consolation I DID search and read through threads until my head hurt prior to posting.
1) What is the best way to apply the new 4.2 update for those with rooted Nexus 7 tablet.
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
Click to expand...
Click to collapse
1) I just downloaded the OTA 4.2 .zip, copied it to my N7, ran CWM and flashed it. When it asked about keeping recovery and keeping root, I said "yes" and it worked without a problem!
2) Works for me.
volarchico said:
1) I just downloaded the OTA 4.2 .zip, copied it to my N7, ran CWM and flashed it. When it asked about keeping recovery and keeping root, I said "yes" and it worked without a problem!
2) Works for me.
Click to expand...
Click to collapse
Sorry these answers need to be dumb'd down for me
1) If i already have the update downloaded via OTA trying to install itself, is it really easier/necessary to locate the zip you mention, copy it to the N7 (not sure where to copy) and run CWM (not sure what that is or where i get it or how to install it). Is there an easier way to accomplish the update? Perhaps setting the Voodoo Rootkeeper to preserve the root or temporarily unroot.. then just install the downloaded OTA update and then return the root? Or just installing the update and then running the re-root using the Nexus Toolkit (like I did with the 4.1.2 update)?
2) I would like to know more about how you avoided this issue described in this thread here with stickmount not functioning with v4.2 because of the new mulituser framework that causes it no longer to see files in the mounted folders.
Thanks for your help and to anyone else that chimes in... any help is appreciated. Again sorry for being stupid.
hinsdale1 said:
Sorry these answers need to be dumb'd down for me
1) If i already have the update downloaded via OTA trying to install itself, is it really easier/necessary to locate the zip you mention, copy it to the N7 (not sure where to copy) and run CWM (not sure what that is or where i get it or how to install it). Is there an easier way to accomplish the update? Perhaps setting the Voodoo Rootkeeper to preserve the root or temporarily unroot.. then just install the downloaded OTA update and then return the root? Or just installing the update and then running the re-root using the Nexus Toolkit (like I did with the 4.1.2 update)?
Click to expand...
Click to collapse
i tried with OTArootkeeper app. but it don't update.... at restart for installing, it gave a black screen with android in the middle, with a RED icon inside it...... then it restart and 4.1.2 is always there
Perhaps these questions are so rudimentary that they hardly seem worth bothering with - but for some of us, these hacks and the info being thrown around in here are pretty confusing at times. I would be very grateful to anyone with some insight willing to help out?.
i found that this could be a problem with recovery mode... infact if i tr y to restart in recovery, it gave the same error...
i rooted with toolbox, and i'm thinking that it could have removed my recovery... now i'd like to try to recover the stock recovery with the same tool... but i'm not sure about that.
We seem to have veered off topic a bit here (at least for me)... so let me re-post the questions and beg again for mercy from any kind soles who can offer some advice?
1) What is the best way to apply the new OTA 4.2 update for those with rooted Nexus 7 tablet?
With the 4.1.2 update, I blindly installed the OTA update when prompted and didnt realize there was a problem until i tried to access my stickmount USB drive. Luckily the nexus 7 was still unlocked so I didn't need to wipe everything. All i did was re-root it using Nexus Root Toolkit v. 1.5.4. and was back up and running. Is this going to be the same experience with the 4.2 update?
I have installed Voodoo OTA Root keeper v2.0.3 - is this a better route for upgrade instead of re-rooting via the Nexus Toolkit? And if so, how should I use it (do know much about the app).?
2) Is stickmount going to work? And if not, is there a good working alternative for streaming mkv h264 movies to MXPlayer (or other player)?
The main reason I rooted was to access a USB drive for playing movies, TV shows while traveling. We are heading off to Cabo for Thanksgiving and definitely want to be able to access and play movies from my stickmount'ed usb drive. Any suggestions ? Should I just wait to update - and if so is there any way to get the Nexus to stop prompting to install the update all the time?
Thanks in advance to anyone willing to have pity on me...
Bueller...... Bueller...... Bueller?
Hi! Last month I did the 4.1.2 OTA update. I was rooted but on stock. It updated with no problems. I used Voodoo OTA rootkeeper, restored the root, and either renistalled super su, or just updated the binary. Can't remember.....But I did lose my custom recovery. Didn't realize it till tonite when I went to do the 4.2 update.
So to your question. I forced the OTA 4.2 update. And it downloaded. I made sure voodoo rootkeeper was set to save the root. Then let it install. It rebooted. I opened voodoo, restored root, was asked to update super su binary, accepted. Still not rooted till I rebooted.
So far I have root, and am on 4.2 JB. So my goal was to get my custom recovery back on. Install goo manager from market. Open it, go to the settings button top right, it will give you the choice to install open recovery script. TWRP- Then it will ask you twice are you sure you want to do this and reboot? Say yes. Mine did not reboot and it looked like it did nothing. So, I flipped into recovery and Teamwinn recovery was installed. I made a backup, and rebooted.
Good luck!
Thanks for your help. Glad to hear that the OTA 4.2 update should go relatively painlessly (keeping root using voodoo rootkeeper). If you have a minute, I would be grateful if you can just briefly confirm, describe specifically what I need to be checking/configuring in Voodooo (not very familiar with the app) prior to initiating the OS update, I would feel a little more secure before pulling the trigger.
It appears that many apps are still catching up with their own updates, including apparently stickmount (the reason I rooted) to handle the new 4.2 framework so I am thinking best to hold off until after thanksgiving vacation before applying the update.
Thanks again.
hinsdale1 said:
Thanks for your help. Glad to hear that the OTA 4.2 update should go relatively painlessly (keeping root using voodoo rootkeeper). If you have a minute, I would be grateful if you can just briefly confirm, describe specifically what I need to be checking/configuring in Voodooo (not very familiar with the app) prior to initiating the OS update, I would feel a little more secure before pulling the trigger.
It appears that many apps are still catching up with their own updates, including apparently stickmount (the reason I rooted) to handle the new 4.2 framework so I am thinking best to hold off until after thanksgiving vacation before applying the update.
Thanks again.
Click to expand...
Click to collapse
Hi hinsdale,
Have you tried updating to 4.2 yet? Also i heard that if you update SuperSU to version 0.98 the latest version it could cause issues and you will have to reflash the device.
Thanks,
JBIRD
Thanks,
JBIRD
4.2 OTA already loaded, lost root
Hi, I have learned the hard way not to do the OTA upgrade. I just let the 4.2 OTA download when asked to. Now I lost my root that I had on my Nexus7 with 4.1.2. Still unlocked though. What can I do now to root it again and not lose all my apps and data?
I'm a newbie, so please remember that when responding. Thanks.
Hi hinsdale! I am not a techie- I just learn as I go and read, read, read.
So, my voodoo app has 4 checks in the boxes. I seem to remember only 3 boxes checked when I did the update, but I'm not sure. It would make sense that all are checked.
After I updated, I opened the voodoo app first, and there is a box that says restore root. Then it asked if I wanted to update the su binary. Did that, still not rooted according to Tit. BU. Rebooted, then I was rooted. Good luck with your update.
I'm sorry I can't tell you how to run the initial save root on voodoo. I did it a while ago and don't remember, but it was not hard. Very easy.. Just make sure you Read, re- read, and read again before you do any modifications to your tablet. Know the possible bad outcomes, and be prepared to trouble shoot. This site is very good about helping you out if things go wrong. That's why it's a very good idea to be aware of the possible bad outcomes. The only way to know is to READ-READ=READ!
Did I mention READ??? lol. That's how I figure stuff out. If you read about others mistakes, you can avoid them. I also wait a day or 2 to see how it goes for others before I attempt modifications. That includes new roms. You never know what goes wrong until someone is the guinea pig! I am not techie enough to be the guinea pig!
paulie7880 said:
Hi, I have learned the hard way not to do the OTA upgrade. I just let the 4.2 OTA download when asked to. Now I lost my root that I had on my Nexus7 with 4.1.2. Still unlocked though. What can I do now to root it again and not lose all my apps and data?
I'm a newbie, so please remember that when responding. Thanks.
Click to expand...
Click to collapse
same thing here...I tried to use TWRM to flash SU but it seems that after going into recovery using TWRM I can't see any any file or folder on my SD except 3 folders???? Can someone please help us....
YOu will need to search the best way to root again.
How did you root initially?? You may have to do it that way again. Just make sure the method is compatible with 4.2 JB.
sashusmom said:
YOu will need to search the best way to root again.
How did you root initially?? You may have to do it that way again. Just make sure the method is compatible with 4.2 JB.
Click to expand...
Click to collapse
Nexus Root Toolkit
The OTA update downloaded to my cache folder, I moved it to my sdcard. Wouldn't install since I had to fix a couple of files I had edited. So once those 2 files were fixed it installed just fine. Haven't had any issues yet.
The same on here...
But I guess it is better until they fix all this bugs they are reporting.
I'll wait until then.
Sent from my Nexus 7 using xda app-developers app
Updated to 4.2
Hi have updated the nexus to 4,2 and used Voodoo OTA Rootkeeper to keep my root followed the instructions as I did when updated to 4.1.2,my Nexus appears to be rooted superSu is working also stickmount sees the usb but it will not show any files on the sd card any help here please to get it to see the files on the sd card, thanks for your time
Nick
i dont post often as i am usually here looking for help. this time i get to help
i just downloaded and installed 4.2 OTA.
if your nexus was previously unlocked and rooted, it will download and install just fine. however you will lose root, but KEEP the unlocked state.
to root it again, you must goto "about tablet" and tap your build number 7 times to become a developer, this is not a troll, i got this info from another thread on xda.
then using the nexus root toolkit 1.5.4 with modeltype set to "android *.*.* any build", just do the root procedure.
reboot and ur in business, no need to update supersu, and busybox will still be installed already.
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
First item, this is a question so it should belong in the question and answer threads! Secondly look here http://forum.xda-developers.com/showthread.php?t=2466191
Sent on my Moto X
Sorry, and thanks! I'll probably give this a shot, make that camera work a little better...
You can always install the SafeStrap ROM here. That's what I did.
http://forum.xda-developers.com/showthread.php?t=2484908
[Rom] [VZW] SafeStrap 139.12.57
Sent from my Moto X
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
mercado79 said:
This method makes it so SafeStrap is no longer available though, right? If that's not the case then... Don't know what I've been waiting for!
Sent from my Moto X
Click to expand...
Click to collapse
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
dymmeh said:
I searched around and can't really find an answer to that. I don't use SafeStrap so I have no idea. I'd assume you can try the method I posted and try using SafeStrap after. If that doesn't work then just RSD back to pre-update and hang on to SafeStrap until it's figured out. No guarantees if it'd work / break stuff, though. You'd be the guinea pig for that one.
Click to expand...
Click to collapse
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
mercado79 said:
@jcase Any chance you can answer this for us? Just cause someone was able to keep root (the one shot kind you mentioned), does that mean that using RSD is still on the table?
Sent from my Moto X
Click to expand...
Click to collapse
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
juancaperez2000 said:
If you take the OTA you dont have wY to revert to old stock Motorola block the reverts already and @jcase already said that he will be back for root in this device till 4.3 is out
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
That's what I thought too. Thanks.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
will2live said:
For sure have I just updated my Moto X the other day on VZW and kept root. Here is a link to the process on how to do it
http://forum.xda-developers.com/showthread.php?t=2466191
Click to expand...
Click to collapse
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
MikeyNick said:
All,
Has anyone on Verizon done the OTA update and kept root? From what I've been reading, sounds like if you rooted with MotoRoot then you're okay, but not if you used PwnMyMoto.
As far as people getting a bootloop, that does make some sense because the recovery partition is really just the boot image... So I can flash the stock recovery to the recovery partition before running the update, and that should theoretically prevent a bootloop. However, if this is going to erase my root, then I don't want to do the update.
So, has anyone on verizon done the OTA and kept their root? How did you do it?
Click to expand...
Click to collapse
mercado79 said:
I think that's not up for debate. The issue is that even though you kept root, you're now blocked from using safestrap or ever gaining root again in the future (once another ota comes through). The update has now patched root going forward and it sounds like you won't be able to keep it after this update.
Click to expand...
Click to collapse
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
boardrx182 said:
So I installed PwnMyMoto, SuperSU and OTA Root Keeper, then decided not to root. I installed the Verizon update and boom, I'm rooted. Is that what you're saying is needed? I was surprised that root apps all work fine for me, I really didn't do anything but install those apks before I installed the camera update!
Click to expand...
Click to collapse
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
dymmeh said:
The way that everyone (including myself) have been updating and keeping root on Verizon is as followed:
1. RSD back to stock (instructions here: http://forum.xda-developers.com/showthread.php?t=2446515)
2. Install PwnMyMoto and DO NOT RUN IT
3. Download and install OTA
4. When the install completes, your phone will reboot a few times. This is just PwnMyMoto doing its magic.
5. Profit.
Click to expand...
Click to collapse
dymmeh said:
As long as you had PwnMyMoto and never ran it / not rooted you were good to go. SuperSU could be installed before or after. I dont think OTA Root Keeper was needed at all. PwnMyMoto runs after a reboot so once you installed the OTA and rebooted it did its rooting magic automatically for you. Glad it all worked out for you
Click to expand...
Click to collapse
That's awesome, didn't realize that would happen automatically. I completely expected that I'd have to complete the entire root process steps that were outlined in an earlier post if I wanted root. Thanks for the reply.
will2live said:
Safestrap i know about and dont care about as i dont use it. As for moving forward with root I'll be surprised if that is the case but I wont disagree either. It is very possible they patch something to actually block root down the road. From my understanding tho currently the patch is blocking ppl to root the update not keeping root if the process is followed correctly. My guess is odds are it will be the same on the next OTA just like we had to do on the original Razr line to keep root until the bootloader was unlocked. However if the next OTA is 4.3 tha tcould all change for sure as anything is possible. Even so when that time comes I'll just unlock mine. I do have a Dev edition i just haven't unlocked with it being brand new and not wanting to void warranty yet to make sure hardware is cool but i do want root so i went the long route for now is all.
Click to expand...
Click to collapse
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
jayboyyyy said:
people who have moto employee friends say they are moving to 4.3 next. Also, there may be a work around for you to keep root with the next release, but because people who aren't on dev phones that must be sure they can retain root would not have used this method (as it is a one chance type of method). so it is more likely that any new workarounds that people come up with will be for those that still have the ability to downgrade to original stock firmware. Also, SS is nice because it gives you the ability to run the phone just like you normally would but you can create complete backups of the device so you don't have to set everything up all over again if you screw something up with your phone. Even if you don't use SS for flashing roms it is still useful for back ups.
Click to expand...
Click to collapse
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
will2live said:
I have my Moto contacts and yes they are moving to 4.3 next last i was told when I asked. As for downgrading stock software that isn't going to happen once updated as you can't go backwards. Moto devices have been that way going back to the original Droid Razr. Its few and far between where you could actually go backwards after an OTA. So unless you mean stock of the current build installed then ppl will have issues for sure. That said if ppl OTA and have root now but for whatever reason need to use the new fastboot file that was just posted they will in fact be SOL for gaining root. This is exactly why I refuse to buy consumer units from the carrier besides a few other reason I wont go into. My theory is simple we want to mess with device buy an unlockable one or be ready to suffer/wait for an exploit after an OTA hits.
As far as root moving forward what process you talking about tho? There is 2 ways to do it. The one posted right above your post in this thread, or the link I posted above. If the info in this thread was used yes there may be an issue because of the patch. However I will be very surprised to see ppl not be able to keep root if they updated using the process in the link I posted above. Besides having to fastboot the boot.img to recovery in that process its the same way original Droid Razr owners had to update to be able to keep root if there was no root process for the OTA being pushed. Moving forward my guess is there will be an issue once 4.3 hits tho. I'm not sure you will be able to use the old kernel from 4.2.2 to overwrite recovery and boot the 4.3 /system so you can restore root and pull the actual 4.3 boot.img so that can be used for the recovery highjack. Bottom line is only time will tell at this point as you never know what Moto/Google will do with the next update.
Agreed on SS for backups even if not flashing ROMs, but personally i just dont mess with my device enough to worry about a full back i guess. For apps/settings I just use MyBackup PRO. I've also have an app a buddy made that creates a full XML if i wanted to use it. In the old days I use to make alot of backups for ROM flashing when I used SS. Guess in my old age I've just got lazy and dont worry about it that much anymore. I really hose the device I'll just swap to one of my others til i get back to fixing the messed up one.
Click to expand...
Click to collapse
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
jayboyyyy said:
3 ways to maintain root are the one in the thread, SS, and the one you posted. The one you posted actually allows you to flash the original stock firmware on the phone because the BL was never touched thus the security (keeping you from downgrading) was never installed. That was what I was referring to when I said those that must make sure they will retain root in the future would not have done the install pwnmymmoto without running then take ota then run pwnmymoto. As you said those people will be screwed if the next root requires you to flash back to original stock or use part of the pwnmymoto exploit that will only be accessible to those that got the OTA with SS or the link you posted. I don't toy with my phone as much as I used to especially this one, but bypasing exchange security is pretty essential for me. I don't want an encrypted device with mandatory pin. I never lose my phone and I would know within minutes of losing it if i ever did so I could shut it down remotely.
And I'm not sure about the new kernel situation either. This is why I wanted to make sure I could go back to original firmware as I see that being our best bet to retain root through 4.3, assuming jcase doesn't release another exploit for it to get some cash.
Click to expand...
Click to collapse
Gotchya, makes total sense now what you are saying. I think there is just confusion at times when talking about root & OTA because of different ways to do it in a case like this device. Being a Moto guy for so long tho i'm use to all the BS they throw at us.....lol. That said that is why i posted the link I did. Imho it's a bad plan to update using the other method of installing pwnmymoto and not running it first before taking the OTA. Doing the process to protect root before updating is a much safer bet atm imo. Sure its a little more work but at the end of the day you dont have to be worried as much moving forward. Only concern I have still for doing it the longer way is if that process will work when they push out 4.3. It had alot of changes in it so lord only knows what will be up for keeping root. And really in my case its no concern but for all the folks with consumer version it is still a concern i think for the time being
This is a tutorial on how to root and unlock the bootloader of the nexus 4 without wiping any data!
Note: I'm not responsible for any damage on your phone! You choose to do these modifications and you are responsible for any problems!
I tested this on Android 4.4.3, but you may try it on other android versions, too. Please report if it works
Devices you can root using this app:
- Nexus 4: 4.4.3, 4.4.4
- Nexus 5, 4.4.3
1. Install the towelroot app (xda thread) from the project site! Please thank geohot, he made this possible!
2. Open the app and click on "make it ra1n"
3. Wait 15 seconds and the phone will reboot!
Congratulations! Your phone is rooted now!
4. Install either SuperSu or Superuser
a) In the app update your binary the "normal way" (without a custom recovery)
b)
1. Install BootUnlocker for nexus devices to unlock your bootloader! In the app, click "unlock" to unlock it!
2. Now you are able to install a custom recovery like TWRP or cwm
3. Boot up your system again, open SuperSu or Superuser and update the binary (using "TWRP/CWM")
This is it! You're rooted now and you can easily unlock/relock your bootloader using the BootUnlocker app without wiping any data
Note: This was not my work! I just wrote down some steps to root and unlock
How to unroot:
1. Reflash the stock recovery image/stock kernel/etc (only necessary if you are running a custom kernel/recovery/etc)
2. Open BootUnlocker and lock the bootloader. Now you are able to uninstall the app!
3. Open SuperSu -> Settings -> Full unroot. This will unroot your phone and the app will automatically be uninstalled.
4. Reboot and done
noob clarifications
Hey, came across your post in another post where you mentioned this method would prevent the posibility of the phone being wiped when unlocked + rooted via "traditional" methods using a PC w SDK etc. Phone at present is locked, unrooted stock Nexus 4 kitkat 4.4.4 stock.
Just wanted to clarify a few points since this is the first time I've come across a method where the phone is rooted and unlocked from within itself (I've rooted and unlocked a HTC desire back in my heydays).
--- Do I need to unlock the phone if I just want to change the kernel from stock to the Matr1x kernel? (I had taken unlocking as a given as it was the first step in every guide - there is no mention of steps on how to actually install the kernel but I was going to research that process once root and unlock was done successfully)
--- Any chance you can give steps on updating the binary the 'normal' way? (never done this before)
--- How do you install CWM using your method? Again, I have only seen it being installed via command lines from the PC
Apologies in advance for the dumb questions but searched and couldn't find any clear answers for those steps that I'm not understanding
salxtai said:
Hey, came across your post in another post where you mentioned this method would prevent the posibility of the phone being wiped when unlocked + rooted via "traditional" methods using a PC w SDK etc. Phone at present is locked, unrooted stock Nexus 4 kitkat 4.4.4 stock.
Just wanted to clarify a few points since this is the first time I've come across a method where the phone is rooted and unlocked from within itself (I've rooted and unlocked a HTC desire back in my heydays).
--- Do I need to unlock the phone if I just want to change the kernel from stock to the Matr1x kernel? (I had taken unlocking as a given as it was the first step in every guide - there is no mention of steps on how to actually install the kernel but I was going to research that process once root and unlock was done successfully)
--- Any chance you can give steps on updating the binary the 'normal' way? (never done this before)
--- How do you install CWM using your method? Again, I have only seen it being installed via command lines from the PC
Apologies in advance for the dumb questions but searched and couldn't find any clear answers for those steps that I'm not understanding
Click to expand...
Click to collapse
1. To flash a kernel you have to unlock your bootloader, that's right. You just flash it using your PC and fastboot, there are many guides on how to do that
2. If your phone is rooted and you have SuperSU installed there'll be a popup and it'll tell you to update the binary before using the app. You are able to select the "normal" way then without a recovery
3. You can install CWM/TWRP using your PC in fastboot mode!
No problem, just ask :good:
Can the usual commandline methods for other things be used after this?
PGvossman said:
Can the usual commandline methods for other things be used after this?
Click to expand...
Click to collapse
If you mean fastboot commands for example to flash another kernel/recovery/etc, yes! There's no difference between unlocking using this method or another "old" one, but this one doesn't wipe data
PGvossman said:
Can the usual commandline methods for other things be used after this?
Click to expand...
Click to collapse
yes. can also be used flashify to flash recovery.img without PC
I think I'll give it a try then (assuming there's no risk of bricking my phone or doing irreversible damage). On that subject, is there an easy way to lock the bootloader and unroot?
PGvossman said:
I think I'll give it a try then (assuming there's no risk of bricking my phone or doing irreversible damage). On that subject, is there an easy way to lock the bootloader and unroot?
Click to expand...
Click to collapse
Check the OP, there are already the steps given to unroot and relock
mihahn said:
I tested this on Android 4.4.3, but you may try it on other android versions, too. Please report if it works
Click to expand...
Click to collapse
I tested this on Android 4.4.4... it works fine!
Note: with TowelRoot v3 it isn't necessary reboot, but when I've tried to update SuperSu it fails so reboot and that's all
Thanks so much!
I apologize for asking so many questions but what exactly is "updating the binaries". Is that just for the app itself or does it do something to the phone?
PGvossman said:
I apologize for asking so many questions but what exactly is "updating the binaries". Is that just for the app itself or does it do something to the phone?
Click to expand...
Click to collapse
It updates the superuser binary that got installed by Towelroot I guess
will this method work on the nexus 5?
mihahn said:
This is a tutorial on how to root and unlock the bootloader of the nexus 4 without wiping any data!
Note: I'm not responsible for any damage on your phone! You choose to do these modifications and you are responsible for any problems!
I tested this on Android 4.4.3, but you may try it on other android versions, too. Please report if it works
1. Install the towelroot app (xda thread) from the project site! Please thank geohot, he made this possible!
2. Open the app and click on "make it ra1n"
3. Wait 15 seconds and the phone will reboot!
Congratulations! Your phone is rooted now!
4. Install either SuperSu or Superuser
F
a) In the app update your binary the "normal way" (without a custom recovery)
b)
1. Install BootUnlocker for nexus devices to unlock your bootloader! In the app, click "unlock" to unlock it!
2. Now you are able to install a custom recovery like TWRP or cwm
3. Boot up your system again, open SuperSu or Superuser and update the binary (using "TWRP/CWM")
This is it! You're rooted now and you can easily unlock/relock your bootloader using the BootUnlocker app without wiping any data
Note: This was not my work! I just wrote down some steps to root and unlock
How to unroot:
1. Reflash the stock recovery image/stock kernel/etc (only necessary if you are running a custom kernel/recovery/etc)
2. Open BootUnlocker and lock the bootloader. Now you are able to uninstall the app!
3. Open SuperSu -> Settings -> Full unroot. This will unroot your phone and the app will automatically be uninstalled.
4. Reboot and done
Click to expand...
Click to collapse
Thanks, for the average user who doesn't use custom roms or anything really crazy, is super su or Superuser a better option? Or is it the same more or less? Thanks
anees167 said:
will this method work on the nexus 5?
Click to expand...
Click to collapse
Yes, it should work fine. Try it
dodgebizkit said:
Thanks, for the average user who doesn't use custom roms or anything really crazy, is super su or Superuser a better option? Or is it the same more or less? Thanks
Click to expand...
Click to collapse
These two are basically the same, as they are apps to manage the superuser permissions of other apps. You may use the one you like
That was easy
Of course I don't see this thread unitl after I spent the last hour setting everything up in Ubuntu to root the old fashioned way! Used this and was rooted in no time.
ota updates affected or not?
does using this towelroot will affect the ota updates i.e. if any ota update comes will i able to install as in the stock rom...?? please clarify this...
ashutoshchauhan211 said:
does using this towelroot will affect the ota updates i.e. if any ota update comes will i able to install as in the stock rom...?? please clarify this...
Click to expand...
Click to collapse
see towelroot only roots your device.
You can get OTA PROVIDED - You dont change any of the stock files.. Nothing should be changed.
mihahn said:
This is a tutorial on how to root and unlock the bootloader of the nexus 4 without wiping any data!
b)
1. Install BootUnlocker for nexus devices to unlock your bootloader! In the app, click "unlock" to unlock it!
2. Now you are able to install a custom recovery like TWRP or cwm
3. Boot up your system again, open SuperSu or Superuser and update the binary (using "TWRP/CWM")
Click to expand...
Click to collapse
Hi, I have rooted Nexus 4 4.4.4 with towelroot app (and I have SuperSu app).
Now, If I install custom recovery, I will lost data? With custom recovery, I will get OTA update?
Thank you
blank nexus 4 without ROM
hi
i tried to install android L, forgot to backup the old ROM , unable to flash the new android L and i cant even restore the old ROM because i forgot to backup the ROM. Tried to do ADB SIDELOAD also....it says cannot read the (file)...tried so many times
i am unable to install a ROM in my nexus 4....only thing i can see in my phone is recovery mode....
Kindly please help.........anyone please reply to this post....and help me......
nexusfans said:
hi
i tried to install android L, forgot to backup the old ROM , unable to flash the new android L and i cant even restore the old ROM because i forgot to backup the ROM. Tried to do ADB SIDELOAD also....it says cannot read the (file)...tried so many times
i am unable to install a ROM in my nexus 4....only thing i can see in my phone is recovery mode....
Kindly please help.........anyone please reply to this post....and help me......
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
GADGTGUY said:
Hi,
I have a Nexus 6 that I am going to start using for work.
My work has a policy that they do not allow rooted devices.
I rooted my Nexus 6 simply to get LED LightFlow to trigger the hidden LED.
When I rooted I used the Nexus Root Toolkit from Wugfresh. I did not use a Custom Recovery and I kept the stock OS (5.0.1 LRX22C)
I really would rather not have to do a wipe/reset if I don't have to. I just need the device unrooted to adhear to company policy.
(and ideally to be able to get the 5.1 OTA when it is released later this month)
D.
Click to expand...
Click to collapse
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
the_rooter said:
Um how will you work know? do they have software they put on the phones? also if your worried just use root cloak. It hides root from set apps.
Click to expand...
Click to collapse
They push a BES client that checks. They already told me they know the phone is rooted. (big brother)
jj14 said:
You can flash the images from the Google Stock image file, and skip userdata - that will restore your phone to stock, without wiping data. Look at the stickies in the general forum for N6
Click to expand...
Click to collapse
Thanks for this info....
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
GADGTGUY said:
I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
It may - but it still won't get you direct OTA (since OTA now checks for any change to system files)
GADGTGUY said:
[snip]I just noticed that in SuperSU there is a feature called: Full unroot
Can I simply do this and presto... the phone is unrooted?
Since I kept the stock OS and didn't put a custom recovery on the phone... do you think this might do the trick?
D.
Click to expand...
Click to collapse
Just to echo what jj14 said. The "Full unroot" option in SuperSU will remove root, but it won't (at least it hadn't on the last version of it that I tried) revert one file that root modifies, so, while you won't have root, and the BES client should work, the update checks the entire file system, so it will fail. A quick flash of only the system.img file using fastboot will remove root and leave everything else untouched.
Thanks for all the advice guys!
I appreciate the assistance... this is why this community rocks!
D.
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
GADGTGUY said:
I should have paid closer attention to the Nexus Root Toolkit from WugFresh.
There is a built in option that unroots without a refresh.
D'oh
D.
Click to expand...
Click to collapse
Many of us would recommend you learn fastboot commands manually rather than relying on toolkits. This helps you get out of trouble when things go wrong. That said, its too late now
Hello, I'm very new to rooting, but over the last few days I've spent hours and hours trying to figure out how to root my phone. Last year I used KingRoot on my Galaxy S4, but it inundated my phone with ads and malware stuff, so I've developed an untrust towards these one-click root apps. I also read how that Android 5.0+ can't be rooted with these one click programs anymore. So I searched up how to root Honor 8, with one of the coming up being on this site. I followed the steps (as confusing as they were), and ended up unlocking my bootloader, flashing TWRP and SuperSU. Now, the reason why I want to root is to use GameGuardian to mess around with some games. The title of the post on how to root the Honor 8 said, [Guide] Unlock Bootloader // Install TWRP // Root - one of these being root, but not once in the actual post do they actually specify when the root happens. I've completed the process, tried to run GameGuardian, and I still can't use it. I downloaded a root checker and it says that my phone isn't rooted. (Heres the link to the guide btw: https://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946) So now I'm very frustrated as to how to root my phone, cos ik rooting can mean many things - including unlocking bootloader and all that with the TWRP custom recoveries and SuperSU, but all I want is a permissions root to let me get run GameGuardian..... Please someone help. I've looked high and low and I'm at a loss.
yejosheph said:
Hello, I'm very new to rooting, but over the last few days I've spent hours and hours trying to figure out how to root my phone. Last year I used KingRoot on my Galaxy S4, but it inundated my phone with ads and malware stuff, so I've developed an untrust towards these one-click root apps. I also read how that Android 5.0+ can't be rooted with these one click programs anymore. So I searched up how to root Honor 8, with one of the coming up being on this site. I followed the steps (as confusing as they were), and ended up unlocking my bootloader, flashing TWRP and SuperSU. Now, the reason why I want to root is to use GameGuardian to mess around with some games. The title of the post on how to root the Honor 8 said, [Guide] Unlock Bootloader // Install TWRP // Root - one of these being root, but not once in the actual post do they actually specify when the root happens. I've completed the process, tried to run GameGuardian, and I still can't use it. I downloaded a root checker and it says that my phone isn't rooted. (Heres the link to the guide btw: https://forum.xda-developers.com/honor-8/how-to/guide-unlock-bootloader-tested-root-t3443946) So now I'm very frustrated as to how to root my phone, cos ik rooting can mean many things - including unlocking bootloader and all that with the TWRP custom recoveries and SuperSU, but all I want is a permissions root to let me get run GameGuardian..... Please someone help. I've looked high and low and I'm at a loss.
Click to expand...
Click to collapse
Flashing SuperSU on an unlocked device should yield the desired outcome if properly performed. Suggest you reflash the latest SuperSU build (at present 2.82 SR5) which can be obtained from here.
Davey126 said:
Flashing SuperSU on an unlocked device should yield the desired outcome if properly performed. Suggest you reflash the latest SuperSU build (at present 2.82 SR5) which can be obtained from here.
Click to expand...
Click to collapse
So I should've technically have already been rooted?
yejosheph said:
So I should've technically have already been rooted?
Click to expand...
Click to collapse
Didn't say that. I confirmed the procedure should work on a device with an unlocked bootloader caveated with "if properly performed". Recommend retrying with 2.82 SR5.