Database Develop

OTA 139.15.1 keep root

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

[Q] Can I update? Confused by so many unclear posts.

Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks

Icon000 said:
Background information:
Bought the AT&T version when it came out right away
Got root the first time it was released
Updated root when next update came out ( Didn't know if I need to )
OTA has been Frozen since I got the phone
Is it safe for me? Should I go back to the first version and then update?
Trust me I've read the posts and since I know there have been some issues on the Verizon side I wasn't sure if that was something that was effecting AT&T too. If some one could please give me an explain of that to it would be extremely helpful as I like to know my **** so I can help others.
Thanks
Click to expand...
Click to collapse
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(

I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
matt99017d said:
Flash back to stock via RSDLite. Let it boot up. Get your gmail setup.
When the prompt comes up, DL the .54 update. Install.
Root with jcase's new root method.
Or you could just install safestrap. Install a ROM with the camera update and not worry about it until kitkat comes around.
Sent from non rooted motoX :'(
Click to expand...
Click to collapse

Icon000 said:
I'm not really interested in updating to another Rom unless it has the touchless controls or something really interesting. Touchless Controls is one of the main reasons I got this phone next to battery life.
Is Safestrap finally settled down? I feel like last time I check there were still messages about bugs and other issues?
Click to expand...
Click to collapse
the only rom out for SS that i am aware of is just a ported tmobile rom for vzw phones that has the update built in. Basically it is just the OTA stock rom running on SS. This is what I am using currently. Not sure if it flashable for ATT phones, but I'm sure there is some workaround there. Or maybe the OP on that thread can make a ATT one if you asked him. SS is stable as of now. Haven't had any new updates to it because no one is having any problems currently (at least with moto x devices).
For your question pertaining to options for taking the OTA. There are 4 methods now.
1. SS method described above
2. use the thread called something like "keep root through the OTA." It basically takes the ota without updating the BL so you can still downgrade to your stock original FW that you are on now. It's the same thing as the SS method because SS also does not udpate the BL, but you won't be using SS for this method obviously.
3. you can flash recovery.img (and system.img if you need to) or just RSD, then install pwnmymoto without running it, then take the ota and pwnmymoto will root the phone automatically after the ota is taken. you won't be able to downgrade your FW anymore with this method.
4. you can just take the ota (also must flash or use rsd to take it obviously) and then use jcase's rockmymoto root exploit. This uses adb commands and telnet stuff. Not too difficult but if you are unfamiliar with all of that then it will take at least some reading. There is also a thread out there for windows users that simplifies it pretty well.
For future Kit kat root. it is still up in the air what will happen with that. I chose to use SS because it was easy. quick. and allows me to make nandroids. I also like knowing that I can still flash to original stock FW in case that might be necessarry for getting root on kit kat. This seems less likely now that jcase created a root method for the OTA that is out, but I'm still just playing it safe personally, even if it might be pointless now.

[Q]I'm not a noob, not yet a woman..i mean, expert.

Hello!
Recently jumped shipped to AT&T moto x and am absolutely loving it. I was perusing around the forum, and really wanted to ask some questions on a specific thread but due to the fear and anxiety of sounding dumb and wasting everyone else's time, I'm just posting a question here hoping that even stupid questions are answered with lots of love. I'm pretty comfortable with rooting, flashing.....aka I'm really good at following instructions, but would really like to expand my knowledge further and am having difficult time getting the explanations I need. SO, hoping some kind soul on here with AT&T Moto X will answer my questions in one shot.
Since my Moto X automatically updated with the new camera update via OTA when I got it four days ago, I was able to successfully root it using JCase's new RockMyMoto method. So, now I'm rooted - great. Everything is set up perfectly the way I want. Then now I find out that AT&T 4.4 is leaked, meaning it's probably going to be ready for an OTA update in the near future (I'm not planning on using the leaked one). So my questions are as follows...
1. I'm going to keep mine rooted until AT&T has 4.4 available for OTA update. Can I simply just run that update when it's available (which will break the root), then just re-root it when that's also available (which it seems like will be rather soon according to Jcase's tweet...)? Or will running the OTA update on my rooted moto x cause more issues other than simply breaking the root? Should I be going back to stock, get the OTA update, THEN re-root it?
2. My understanding is that AT&T boot loader is still locked down...so to my limited knowledge, this means I'm not able to make a NANDROID back up using CWM...am I wrong here in any way? Is there a way to make a NANDROID-like back up (which I used to back in S3 days) without having my bootloader unlocked?
3. Tethering...I was able to use FoxFi fine on my S3 (I got that good old granfathered unlimited data plan....), but it does not seem to work on my new Moto X. Is there any known work around for this? I have Titanium Backup Pro as well, so thought I could maybe just freeze the tether provision or w/e by AT&T but seems like I'm also somehow misunderstanding that there as no such thing seems to exist.
Thanks,
Yoondroid

I can only respond to your first question. You can not take an ota while rooted. The exploit breaks the stock recovery. In order to take the update, you'll have to fastboot the factory images to revert to an in rooted state and then accept the ota. It's really easy and only takes a few minutes... Assuming you have adb set up and know how to use it, if not, an hour or so if searching and reading will get you up to speed.
Sent from my XT1058 using XDA Premium 4 mobile app

theraffman said:
I can only respond to your first question. You can not take an ota while rooted. The exploit breaks the stock recovery. In order to take the update, you'll have to fastboot the factory images to revert to an in rooted state and then accept the ota. It's really easy and only takes a few minutes... Assuming you have adb set up and know how to use it, if not, an hour or so if searching and reading will get you up to speed.
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can also just flash the recovery.img back and take the OTA update while rooted.

You can install safestrap to make a backup and WiFi tether root works with some minor changes there's a thread somewhere.

Hmm, thanks guys I'll be checking out/learning more about the fastboot option
As for tethering, I've found some good information though for the first option, I haven't figured out a way to patch the at&t apk OP posted in his thread. Seems like quite the ingenious work around though, so hopefully I'll be able to figure it out soon! The second option seems to be a quick work around to get tethering to work, but seems way less secure...and I'll be using tethering to do work which I prefer to be on a much secure network, so we'll see.
First (tricking the phone to think it's not an at&t phone when turning on tethering in native app): http://forum.xda-developers.com/showthread.php?t=2443562
Second: http://forum.xda-developers.com/showthread.php?t=2449534&page=3

mandrsn1 said:
You can also just flash the recovery.img back and take the OTA update while rooted.
Click to expand...
Click to collapse
just so the OP is led astray, if you only flash the recovery.img and you have made changes to your system apps or anything in the /system then you won't be able to take the ota and it will likely through you into a BL. If you don't know what you have changed, then go ahead and flash the system.img as well as recovery and you will be good to go. If you know what you changed then uninstall all of your root apps and change everything you change in the /system back to how it was and take the ota (after flashing recovery.img of coarse).
here is a great guide to adb stuff for you as well that got me started. still go back to it for reference occasionally. its a little old but it is still good.
http://forum.xda-developers.com/showthread.php?t=872128

Brand new, 4.2.2, Any reason not to update to latest firmware?

Hi folks,
Just got my TF701T from Amazon on the $279 deal. I've connected it to my wifi but have not even set up a google account for it yet. It's doing an initial charge.
Is there any compelling reason not to let the update happen? The main short term use for the tablet will be that my 7 year old son will play games on it. Eventually, I'd still like to unlock it and maybe to a custom OS, but for now it's plain Jane use.
The only special thing I might want to do is get Helium/Carbon going so I can backup / restore game positions for him... I've got his status on several games saved from another tablet that had root and I backed them up. Would like to restore if possible. Does this require root?
Thanks. Looking forward to advice.
Marc

Hi, before giving my opinion, I would suggest you to look through the forum while you are here. That said, I have some opinions against updating to 4.4.2. The main reason is that there are some battery issues on that boot loader for some unknown reason. Also, there is no root exploit available for the 4.4.2 version without having to unlock the boot loader. I was told that 4.3 was the best to stay on right now if you can.I just recently got my tablet too from that same deal. On 4.3 there is a easy root exploit called towelroot available, so you can root without unlocking.
---------- Post added at 01:48 AM ---------- Previous post was at 01:48 AM ----------
I also believe that carbon needs root for using it. If you have any questions, feel free to ask!!

royredman said:
Hi, before giving my opinion, I would suggest you to look through the forum while you are here. That said, I have some opinions against updating to 4.4.2. The main reason is that there are some battery issues on that boot loader for some unknown reason. Also, there is no root exploit available for the 4.4.2 version without having to unlock the boot loader. I was told that 4.3 was the best to stay on right now if you can.I just recently got my tablet too from that same deal. On 4.3 there is a easy root exploit called towelroot available, so you can root without unlocking.
---------- Post added at 01:48 AM ---------- Previous post was at 01:48 AM ----------
I also believe that carbon needs root for using it. If you have any questions, feel free to ask!!
Click to expand...
Click to collapse
Thanks. I've used Carbon and believed it requires root, too. I'm a bit surprised that Towelroot wouldn't work on 4.4.2, as it was originally designed for 4.4.2 on Samsung and similar related kernel units. I've used it on my Samsung S4, and it required being on a pretty up to date 4.4.2 build. Wouldn't work on 4.3. But it may be different on the Asus.
I saw a mention off battery drain on 4.4.2 but without details. I'll continue looking. For now I've charged then powered off the tablet. No time to set it up tonight anyway. Seems like a very nice unit though.
Thanks for your reply!
Marc

Frankenscript said:
Thanks. I've used Carbon and believed it requires root, too. I'm a bit surprised that Towelroot wouldn't work on 4.4.2, as it was originally designed for 4.4.2 on Samsung and similar related kernel units. I've used it on my Samsung S4, and it required being on a pretty up to date 4.4.2 build. Wouldn't work on 4.3. But it may be different on the Asus.
I saw a mention off battery drain on 4.4.2 but without details. I'll continue looking. For now I've charged then powered off the tablet. No time to set it up tonight anyway. Seems like a very nice unit though.
Thanks for your reply!
Marc
Click to expand...
Click to collapse
Yeah, from what I understand, towelroot worked on the galaxy s4 (my current awesome phone) because the exploit wasn't patched at that time for the phone, but sadly Asus patched it as for the 4.4.2 drain, Netflix seems to be one of the couple of apps that is really draining power. Not really sure about it, but I'm probably not going to update until the next update is released.

royredman said:
Yeah, from what I understand, towelroot worked on the galaxy s4 (my current awesome phone) because the exploit wasn't patched at that time for the phone, but sadly Asus patched it as for the 4.4.2 drain, Netflix seems to be one of the couple of apps that is really draining power. Not really sure about it, but I'm probably not going to update until the next update is released.
Click to expand...
Click to collapse
Thanks. I read up a bit and indeed see how they patched the exploit before the 4.4.2 build, so sadly no Towelroot in Kitkat for us, without unlocking the bootloader and voiding warranty.
Since I will be using the tablet just for kid use, 4.3 will be just fine for now. Which of the (US) firmwares is the best to flash? I'm having some trouble relating the build numbers listed to the "4.2.2 / 4.3 / 4.4.2 etc" nomenclature. I've been reviewing the Device Essential Material thread but I'm still learning the ropes on the Asus.
So as I understand it, I get the right one downloaded, unzip it (one level), put it in sdcard root directory, reboot, and it auto-applies. Is that correct? Then Towelroot,, presumably SuperSU, then I can freeze the update processes with TiBU or somesuch. IS there a good description of what to freeze to prevent further update notices?
Anything else I should know? I'm still catching up.
Marc
PS. Based on THIS POST it sounds like I want 10.26.1.18 . Do you agree?

Frankenscript said:
Thanks. I read up a bit and indeed see how they patched the exploit before the 4.4.2 build, so sadly no Towelroot in Kitkat for us, without unlocking the bootloader and voiding warranty.
Since I will be using the tablet just for kid use, 4.3 will be just fine for now. Which of the (US) firmwares is the best to flash? I'm having some trouble relating the build numbers listed to the "4.2.2 / 4.3 / 4.4.2 etc" nomenclature. I've been reviewing the Device Essential Material thread but I'm still learning the ropes on the Asus.
So as I understand it, I get the right one downloaded, unzip it (one level), put it in sdcard root directory, reboot, and it auto-applies. Is that correct? Then Towelroot,, presumably SuperSU, then I can freeze the update processes with TiBU or somesuch. IS there a good description of what to freeze to prevent further update notices?
Anything else I should know? I'm still catching up.
Marc
PS. Based on THIS POST it sounds like I want 10.26.1.18 . Do you agree?
Click to expand...
Click to collapse
You can use any on. I just used the one that was on my tablets before (which was US). 10.26.1.18 is the 4.3 file to grab. Yup, unzip once and put it on the sd root file. For me, when I rebooted it, it let me know that there was a downloaded update detected (NOT the normal "click this button to download the system update")(be really careful about that one). Once I tapped the detected update file, it showed me it was the 10.26.1.18 file and I told it to install it.
If you want to see what to freeze, go into the towelroot thread in the Q&A section and look for my posts on the last page or so. I was asking exactly the same thing and they answered it all for me. Good luck and let me know if it goes well!!

Frankenscript said:
Thanks. I read up a bit and indeed see how they patched the exploit before the 4.4.2 build, so sadly no Towelroot in Kitkat for us, without unlocking the bootloader and voiding warranty.
Since I will be using the tablet just for kid use, 4.3 will be just fine for now. Which of the (US) firmwares is the best to flash? I'm having some trouble relating the build numbers listed to the "4.2.2 / 4.3 / 4.4.2 etc" nomenclature. I've been reviewing the Device Essential Material thread but I'm still learning the ropes on the Asus.
So as I understand it, I get the right one downloaded, unzip it (one level), put it in sdcard root directory, reboot, and it auto-applies. Is that correct? Then Towelroot,, presumably SuperSU, then I can freeze the update processes with TiBU or somesuch. IS there a good description of what to freeze to prevent further update notices?
Anything else I should know? I'm still catching up.
Marc
PS. Based on THIS POST it sounds like I want 10.26.1.18 . Do you agree?
Click to expand...
Click to collapse
You got it.
The .18 firmware is the JB 4.3. But stick to your SKU (US, WW - whatever it is now).
Once rooted freeze DMClient and CMClient and you won't be bothered with OTA updates.

Thanks! It's all done.
For anyone who reads this and needs to do the same thing, it was super easy. Just plugged the new Tab into the PC via USB, opened up to "Internal Storage", copied the UL-K00C-US-10.26.1.18-user.zip file over there, and rebooted. It auto-applied, rebooted again. Eventually I had to delete the .zip file from the internal storage, because on each reboot it would notice it and spend time figuring out if it had new updates or not.
Then Towelroot, SuperSU, and used App Quarantine-Root to freeze DMClient and CMClient. Rebooted again and no more update waiting for download messages.
I'm good to go!

royredman said:
Hi, before giving my opinion, I would suggest you to look through the forum while you are here. That said, I have some opinions against updating to 4.4.2. The main reason is that there are some battery issues on that boot loader for some unknown reason. Also, there is no root exploit available for the 4.4.2 version without having to unlock the boot loader. I was told that 4.3 was the best to stay on right now if you can.I just recently got my tablet too from that same deal. On 4.3 there is a easy root exploit called towelroot available, so you can root without unlocking.
---------- Post added at 01:48 AM ---------- Previous post was at 01:48 AM ----------
I also believe that carbon needs root for using it. If you have any questions, feel free to ask!!
Click to expand...
Click to collapse
First, i can confirm battery issues with 4.4.2. Android sometimes does not go to deepsleep (even if there are no addition apps installed, it seems a general problem). If i charge the tablet to 100% and go to bed, on the next morning i can be glad, if i have 30% battery left. Not always, but every 2.nd or 3rd night.
Second, a little question. Becauce of this "bug" i'd like to root my tablet and use a custom rom. I would like to use this method "http://forum.xda-developers.com/showthread.php?t=2604462 <- [MOD] JB 4.3+ | TF701T | Flashable Root Method v2 | Asus Stock 10.26.1.7/18
My first problem is the unlock app from asus. On the support site a text says: "1. Only suitable for Android4.2 Jelly Bean OS version" . But, according to most of the threads here, i should also work with 4.4.2??
The second question is, if the root method i just linked, works without any problems with the last asus update 4.4.2?
Using the tablet with this battery issue is horrible.
Thanks!

Hypothetix said:
First, i can confirm battery issues with 4.4.2. Android sometimes does not go to deepsleep (even if there are no addition apps installed, it seems a general problem). If i charge the tablet to 100% and go to bed, on the next morning i can be glad, if i have 30% battery left. Not always, but every 2.nd or 3rd night.
Second, a little question. Becauce of this "bug" i'd like to root my tablet and use a custom rom. I would like to use this method "http://forum.xda-developers.com/showthread.php?t=2604462 <- [MOD] JB 4.3+ | TF701T | Flashable Root Method v2 | Asus Stock 10.26.1.7/18
My first problem is the unlock app from asus. On the support site a text says: "1. Only suitable for Android4.2 Jelly Bean OS version" . But, according to most of the threads here, i should also work with 4.4.2??
The second question is, if the root method i just linked, works without any problems with the last asus update 4.4.2?
Using the tablet with this battery issue is horrible.
Thanks!
Click to expand...
Click to collapse
Reg. Battery drain: Did you run Netflix on those nights you had that severe battery drain?
Reg. Unlock: The tool should work on any fimware version. Just run it. Worst case scenario: It won't work.
Reg. Root: Why would you root the stock rom if you want to replace it with a custom rom anyway?
To install a custom rom you need to:
A) unlock the bootloader
B) flash a custom recovery in fastboot
C) create a nandroid of your stock rom in recovery
D) wipe cache, Dalvik and data using your custom recovery
E) flash the custom rom (which is rooted anyway).
For general reference on flashing custom roms to the Transformer, check out my guide here:
http://forum.xda-developers.com/showthread.php?t=2688891
NOTE: This is a guide for the TF700!! The general instructions on flashing, fastboot commands etc still apply. The specifics like recovery and version, bootloader and version etc DO NOT.
For TF701 specific instructions check out the OP of the CROMi-X thread in the Development section for the TF701 here on XDA.

berndblb said:
Reg. Battery drain: Did you run Netflix on those nights you had that severe battery drain?
Reg. Unlock: The tool should work on any fimware version. Just run it. Worst case scenario: It won't work.
Reg. Root: Why would you root the stock rom if you want to replace it with a custom rom anyway?
Click to expand...
Click to collapse
Thanks. Yes i know. I like the look the stock rom has. Therefore i first wanted to test, if i can stop the battery drain, if i use apps like greenify to send a few apps to deepsleep.
I rooted yesterday and tested it. Unfortunately, even with greenify i have the same problem. Every time i use the keydock, the tablet does not go into deepsleep mode. I checked with wakeup detector if i can find out which app is bad, but there are no apps which wake up the tablet more that 5 or 6 times.... If i use the tablet without the dock i dont have this problem (or just when i use netflix and dont reboot after usage)
Now i will try a custom rom....maybe it helps.
Thanks !

[Q] Should I try Stock Andoroid before CM12?

My Nexus 6 has finally shipped! It should be here Friday!
This is my first Nexus and I have never rooted, unlocked, flashed, etc. any of my previous phones.
I have been doing a lot of research and have been considering running CM12.
My question is, should I run my Nexus 6 with stock android for a few weeks and then try CM12? Or should I just root, unlock, and flash CM12 as soon as I get it?
I know that if I wait then I will need to back up all my data because it will factory data reset but I am not worried about that... I understand it is easier to do it right out of the box because you don't have to worry about loosing anything but I can just back my info/apps up so that isn't a big deal.
Also, would you guys suggest something over CM12? Right now I am planning on using CM12 and just getting it setup how I like it then leaving it. I don't plan on always flashing and making changes but I might get sucked into it lol
Thanks everyone!

Has CM moved to 5. 1 yet?
What version android came your phone?
Depending on those two answers you have to ask yourself if you want to downgrade your phone. At least version wise
Sent from my Google N6 on VZ

DebianDog said:
Has CM moved to 5. 1 yet?
What version android came your phone?
Depending on those two answers you have to ask yourself if you want to downgrade your phone. At least version wise
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Good point! I don't know if CM is on 5.1 yet. I just assumed it was but I will look into it. This is all new to me so thanks for pointing that out, didn't even think about that!
I won't know what version is on the phone until Friday. But even if it is on 5.0 I am sure it will notify me that 5.1 is ready to download as soon as I boot up the phone.

On my other phones I usually got rid of the stock and was on a custom ROM a pretty quick. I have tried a few ROMs on this phone as well. in my experience if you want to be on 5 .1 currently the best way to go is stock with debloating . Or use one of the clean/vanilla ROMs. Of course I did not test them all there are so many out there. Good luck with your new toy.
I will try CM after its been out a few weeks on 5 .1
Sent from my Google N6 on VZ

I'd recommend updating to 5.1 if it doesn't ship with 5.1. Then, I'd run stock for at least a few days to get a baseline for comparison. I think this is useful especially for bugs. That way you can get an idea of the issues that exist in stock 5.1 before using a custom ROM.

DebianDog said:
On my other phones I usually got rid of the stock and was on a custom ROM a pretty quick. I have tried a few ROMs on this phone as well. in my experience if you want to be on 5 .1 currently the best way to go is stock with debloating . Or use one of the clean/vanilla ROMs. Of course I did not test them all there are so many out there. Good luck with your new toy.
I will try CM after its been out a few weeks on 5 .1
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
Okay, thanks for the info!
Since I ordered my phone directly from Google, do I need to debloat? Or is that just for carrier versions?

mlin said:
I'd recommend updating to 5.1 if it doesn't ship with 5.1. Then, I'd run stock for at least a few days to get a baseline for comparison. I think this is useful especially for bugs. That way you can get an idea of the issues that exist in stock 5.1 before using a custom ROM.
Click to expand...
Click to collapse
Another great point! I knew you guys were the people to ask! lol
What about rooting and unlocking? Would you suggest waiting on that as well? Is there really any reason to unlock and root if I won't be running CM? I was going to root so that I could decrypte but it sounds like the lag from encryption is fixed in 5.1.

Well I would guess you WILL want to unlock and root because who does want to be able to run a root level ad blocker? Who wants to wait on OTA for an update? Not me.
I got mine from Google, as well, and heres what I did:
Played with the phone in stock form for like an hour saw it was still on 5.01 even after updating
Decided this is not for me. I wanted my root apps and I wanted to copy all the stuff off my old phone with Titanium backup to the Nexus
Looked on the interwebs for the easiest way to get root
Found a tool from my old buddy WugFresh (I knew him in the Droid X days)
Prepared myself for a giant PITA night. Download, drivers, and programs, reading various sites, etc, etc, etc
Was freaking SHOCKED that the tool did ALL THIS for me. I mean I literally plugged in my phone and it collected and set up everything. (It also has a console if you feel the need to type in adb commands)
Was unlocked, upgraded, rooted with a custom recovery with all my apps copied over in less than an hour
Sent Wuggy some $$$ and a thank-you note
You only need to decrypt, IMO, if you are running high end games that demand that level of performance. I have not seen any lag myself. Again this is my own personal experience. Your results may vary. 5.1 has optimized out many of the issues I heard about in 5.01 or so I have been told.

CFrance said:
Another great point! I knew you guys were the people to ask! lol
What about rooting and unlocking? Would you suggest waiting on that as well? Is there really any reason to unlock and root if I won't be running CM? I was going to root so that I could decrypte but it sounds like the lag from encryption is fixed in 5.1.
Click to expand...
Click to collapse
I unlocked and rooted right away, mainly for the ability to use Titanium Backup to setup my phone and in the event that I installed a custom ROM. Outside of TB, I haven't really needed or used root, but it sure is nice to have. I played with a few custom ROMs before 5.1 came out but mostly felt that I preferred the stock experience. I downloaded the MCR modpack found here: http://forum.xda-developers.com/showpost.php?p=58019266&postcount=1 but have yet to install it. If/when I do, root will become more of a requirement for my uses.
I came from a Verizon Note 4 which could not be rooted. I got used to not playing with my phone and just using the stock experience. Its nice that the stock experience on the N6 is so fantastic and stable. It makes it easy to just use the phone without worry of fixing, modding, and adding features, though I still enjoy those aspects too which is why I'll likely use MultiROM next time I decide to install something custom.

Dude are you somehow tied up with this Tool Kit? You`re promoting it on so many threads i`am starting to get the impression you`re not quite objective about it There is no harm in using toolkits by xperienced users and i`am sure its well build, but for newbies its very dangerous because they`re lost if something should go wrong.

gee2012 said:
Dude are you somehow tied up with this Tool Kit? You`re promoting it on so many threads i`am starting to get the impression you`re not quite objective about it There is no harm in using toolkits by xperienced users and i`am sure its well build, but for newbies its very dangerous because they`re lost if something should go wrong.
Click to expand...
Click to collapse
Which is exactly why I'm promoting it it is almost bulletproof. what's the alternative loading all the different tools and drivers they need and following some instructions found on the internet.
And as I explained in my post you can just download the tool to make sure you have all the drivers and connections. use it to get the proper files you need and then run the command line like a power user if you want to feel better about yourself.
Sent from my Google N6 on VZ

DebianDog said:
Which is exactly why I'm promoting it it is almost bulletproof. what's the alternative loading all the different tools and drivers they need and following some instructions found on the internet.
And as I explained in my post you can just download the tool to make sure you have all the drivers and connections. use it to get the proper files you need and then run the command line like a power user if you want to feel better about yourself.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I will never use/promote a Toolkit even if it seems very good for the reason i posted earlier. Flashing manualy in fastboot doesn`t take more time and makes users more aware about their phone and knowledge of it and gives you control over whats happening Just my 2 cents.

My two cents. I don't think you've dealt with enough newbies. on another forum it was me and a group of others that would help people get their phones out of boot loops and soft bricks. I have literally helped hundreds of people get their phone back.
even if you look here on XDA you'll see people trying to flash the wrong files download files that are not even for their phone, are following a dated instruction or don't really understand how directories work.
Sent from my Google N6 on VZ

DebianDog said:
Well I would guess you WILL want to unlock and root because who does want to be able to run a root level ad blocker? Who wants to wait on OTA for an update? Not me.
I got mine from Google, as well, and heres what I did:
Played with the phone in stock form for like an hour saw it was still on 5.01 even after updating
Decided this is not for me. I wanted my root apps and I wanted to copy all the stuff off my old phone with Titanium backup to the Nexus
Looked on the interwebs for the easiest way to get root
Found a tool from my old buddy WugFresh (I knew him in the Droid X days)
Prepared myself for a giant PITA night. Download, drivers, and programs, reading various sites, etc, etc, etc
Was freaking SHOCKED that the tool did ALL THIS for me. I mean I literally plugged in my phone and it collected and set up everything. (It also has a console if you feel the need to type in adb commands)
Was unlocked, upgraded, rooted with a custom recovery with all my apps copied over in less than an hour
Sent Wuggy some $$$ and a thank-you note
You only need to decrypt, IMO, if you are running high end games that demand that level of performance. I have not seen any lag myself. Again this is my own personal experience. Your results may vary. 5.1 has optimized out many of the issues I heard about in 5.01 or so I have been told.
Click to expand...
Click to collapse
Thanks for the info! I actually had just downloaded this program over the weekend and was planning on using it once I do decide to root... which I am thinking will be as soon as I get the phone. lol other than that I think I am going to run it on stock for a while at first and wait until CM is on 5.1 for a while....

mlin said:
I unlocked and rooted right away, mainly for the ability to use Titanium Backup to setup my phone and in the event that I installed a custom ROM. Outside of TB, I haven't really needed or used root, but it sure is nice to have. I played with a few custom ROMs before 5.1 came out but mostly felt that I preferred the stock experience. I downloaded the MCR modpack found here: http://forum.xda-developers.com/showpost.php?p=58019266&postcount=1 but have yet to install it. If/when I do, root will become more of a requirement for my uses.
I came from a Verizon Note 4 which could not be rooted. I got used to not playing with my phone and just using the stock experience. Its nice that the stock experience on the N6 is so fantastic and stable. It makes it easy to just use the phone without worry of fixing, modding, and adding features, though I still enjoy those aspects too which is why I'll likely use MultiROM next time I decide to install something custom.
Click to expand...
Click to collapse
Thanks! I am planning on rooting and unlocking right away for TB and maybe a couple other little things like lightflow just for fun. Being the nerd that I am, I have a feeling that once I start playing with the whole rooting, unlocking, and flashing stuff I am going to really enjoy it.

gee2012 said:
I will never use/promote a Toolkit even if it seems very good for the reason i posted earlier. Flashing manualy in fastboot doesn`t take more time and makes users more aware about their phone and knowledge of it and gives you control over whats happening Just my 2 cents.
Click to expand...
Click to collapse
Thanks for the reply! I see what you are saying, I had already come across Wug's toolkit over the weekend and was planning on using that because it seemed so simple.
However, seeing how I still have two and a half days until my phone will be here, maybe I will look into the manual way a little more to decide which route I want to go.... Any suggestions on where to start? Threads, videos, etc?
Thanks!

Boot into download mode, Unlock bootloader, reboot, boot back into download mode, fastboot twrp recovery, boot into recovery, reboot via recovery and install su when prompted. When you boot into android you will be prompted to update su. You now are rooted. Only other thing I would think about when you first get your device is if you want forced encryption. You will be required to wipe SD data if you decide to go with non forced encryption.
I loved cm on my previous touchwiz devices because I like stock/asop style. I find cm has bugs in early os update releases. I would only install cm if i took advantage of themes which I don't.

CFrance said:
Any suggestions on where to start? Threads, videos, etc?
Thanks!
Click to expand...
Click to collapse
You can waste a lot of time while you're waiting for your phone in this thread http://forum.xda-developers.com/showthread.php?t=2992769
ROM Reviews (5.1) + Nexus 6 Hacking: NRT · Apps · Utilities [3.22.15]
Sent from my Google N6 on VZ