Related
Update
Since this thread seems to have become quite popular, I thought I'd update it to give people all the newest information in one place.
Since I've made this post, there has been another OTA (build 12940) that improves bootloader security even further and prevents some potential root methods which were being developed for 12840. As of now, neither build 12840, build 12940, nor build 13300 has a published root method. New units have the patched bootloader preloaded from the factory and are not rootable. If you buy a unit at this point, there is a good chance that you will get one that is patched. (EDIT 2013-10-22: People are reporting that units they have purchased from Best Buy and Amazon are still running the vulnerable build. It is unclear if this is simply old stock or if there are still vulnerable units being produced.)
As for the methods described below, they cannot be performed through a shell (i.e. telnet) since the root filesystem is formatted as squashfs, which is read-only. Instead, the root images must be manually repacked for each OTA and flashed using a USB drive with an image such as FlashCast. @ddggttff3 maintains a FlashCast mod to update Chromecasts to the latest firmware without losing root, which can be found here.
For those of you who have managed to keep your vulnerable bootloaders, keep your eyes out. There should be some very cool releases in the near future.
Original post
As can be seen in this commit to Google's Chromecast source mirror, firmware version 1.1 adds a check for the result of image verification on line 755. This check will cause GTVHacker's USB image to fail to boot, and you will not be able to obtain root. Even if another root exploit is found, it seems very unlikely that it will be as clean or simple as the one which exists now, which simply uses version 0.7's unlocked bootloader to flash a new system image.
Unfortunately, I don't have a Chromecast to test on, so I cannot recommend a method of disabling OTAs. However, from looking at the system image, there are a few possibilities I see. THE FOLLOWING METHODS ARE UNTESTED AND ARE NOT GUARANTEED TO WORK OR LEAVE YOUR CHROMECAST IN A WORKING STATE. PERFORM THEM AT YOUR OWN RISK.
After telnetting into your rooted Chromecast or otherwise obtaining a root shell, you can try these two possible methods
Rename otacerts.zip to otacerts.zip.bak in /system/etc/security/. This may remove the OTA signing keys and cause the Chromecast to reject any OTAs. However, I do not know whether this file is actually used or whether is simply a remnant from Chromecast's Android base.
Replace /chrome/update_engine with an empty, executable, shell script (make sure to make a backup copy first). I am very unsure of this method, since it is simply going off the name of the update_engine binary. If update_engine happens to perform some task core to the system, doing this will leave your device in an unusable state. If this happens, simply re-rooting using GTVHacker's USB image should restore your system to how it was.
Again, I am not responsible for any bricked Chromecasts which may result from attempting this. If you do try either method, please report whether or not it appeared to work or have any ill effects.
Any idea when they'll push the update?
xuser said:
Any idea when they'll push the update?
Click to expand...
Click to collapse
According to Google, it's rolling out now.
Thanks for this, just checked my unit, which is still on the old version. Am waiting for my cable to get here so I can root it, so glad I caught it before it updated!
Looks like the update will be automatic and my Chromecast is plugged up at home (connected to wifi). Hope it doesn't get pushed today. My powered USB OTG cable hasn't arrived yet so I can't even root it ATM.
Sent from my GT-N5110 using Xparent Green Tapatalk 2
joshw0000 said:
Looks like the update will be automatic and my Chromecast is plugged up at home (connected to wifi). Hope it doesn't get pushed today. My powered USB OTG cable hasn't arrived yet so I can't even root it ATM.
Sent from my GT-N5110 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
find out the server name/ip for the OTA update, block it on your router
paperWastage said:
find out the server name/ip for the OTA update, block it on your router
Click to expand...
Click to collapse
Here are the URLs:
Stable channel updates http://goo.gl/3yy01K
Beta channel updates http://goo.gl/53l5sA
Dev channel updates http://goo.gl/JVkHhl
Weird...when I just loaded those, the stable channel has the highest build number. Stable is at 12840 (which is the update that is rolling out now), Beta is at 12726, Dev is at 12819
paperWastage said:
find out the server name/ip for the OTA update, block it on your router
Click to expand...
Click to collapse
I wont be home until later tonight.
Sent from my GT-N5110 using Xparent Green Tapatalk 2
also, i'd assume replacing /boot/recovery.img with a custom recovery or just removing it would also prevent updates. not sure though, I also don't have a chromecast.
also, if you are feeling adventurous, try this: http://db.tt/Ja1XBNgH. if it works, you'll have the latest software, root, and no updated bootloader. if it doesn't work, you might be able to recover by using gtvhacker's image. no promises though, since I don't own a chromecast, I cant test it. Don't blame me if your chromecast quits working, explodes, kills your puppy, or hands north korea some working nukes.
@xuser your signature made me think there was an actual bug on my screen. I tried to kill it, but it ignored my attempts and kept crawling around under the glass
[removed]
Wouldn't it be possible to flash build 12072 back onto the device (since it is signed by Google), and then root it using that build? That is a fairly common practice for many devices that have exploits in early releases. Is there a copy of the image for build 12072 floating around yet?
It's possible. But it seems like more and more manufacturers are preventing downgrading. Who actually manufacturers this thing?
Sent from my SCH-I545 using Xparent Green Tapatalk 2
the chromecast seems to have a recovery mode (like android) that flashes update zips (like android). so if we found a google signed update for the original firmware that includes flashing the insecure bootloader, then downgrades are possible. but the update zips posted above include a build date check,which means you have to either modify your build.prop (requires root, which is what we are trying to accomplish) or modify the update zip (which will make it no longer google signed and valid, so it would need a custom recovery. which requires root). so, unless google lets us, downgrading is not possible.
I'm still hoping that google built in a dev-mode, like their chrome os devices.
Hmm I wonder if I were to order one now would it come with the old software or the new update?
I'm guessing that it would still be on the old build (assuming you get it shipped soon, or pick it up at Best Buy). My Chromecast sticks still haven't updated to the latest build.
joshw0000 said:
Who actually manufacturers this thing?
Sent from my SCH-I545 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
Good question.
mine updated itself today and lost root
no one tried my image yet?
I'm curious if you had your Chromecast powered off during the day today. And if so, did you see it update when you turned it on?
I have been using my Chromecast to stream music all day, and so far it hasn't updated to the latest build. I would assume as long as the Chromecast is off or in use casting then the update will not be performed.
Louer Adun said:
I'm curious if you had your Chromecast powered off during the day today. And if so, did you see it update when you turned it on?
I have been using my Chromecast to stream music all day, and so far it hasn't updated to the latest build. I would assume as long as the Chromecast is off or in use casting then the update will not be performed.
Click to expand...
Click to collapse
I've turned it off a few times but it finally updated ~30 min ago.
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
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 !
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
you can downgrade and then you can root
Ubuntu_noobi said:
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
Click to expand...
Click to collapse
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Davey126 said:
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Click to expand...
Click to collapse
I've tried moving the factory update after downloading it to the DCIM, when trying to update, it states that you can't update because it's an older version of the os. Is it required to side load?
Ubuntu_noobi said:
I've tried moving the factory update after downloading it to the DCIM, when trying to update, it states that you can't update because it's an older version of the os.
Click to expand...
Click to collapse
Wrong procedure. See forum index for details, in particular the first two posts in this thread.
Ubuntu_noobi said:
Is it required to side load?
Click to expand...
Click to collapse
Yes.
So glad I found this post. Researching the same thing. Trying it out now
Sent from my iPhone using Tapatalk
yungskeeme01 said:
So glad I found this post. Researching the same thing. Trying it out now
Click to expand...
Click to collapse
Any new info to share? I still haven't been able to figure it out
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
What exactly are you trying to "figure out"? Responded a few days ago with downgrade/rollback links which includes a step-by-step video.
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
I downgraded to 5.3.1. Rooted the fire and am now running CM 12.1. Very smooth!. Took me a awhile to get since I have a Mac but got it working. Used Rootjunky's YouTube video on how to restore. That's how I downgraded. Then used his Supertool for Mac and rooted. I then installed Flashfire and put CM12 on the tablet.
Sent from my iPhone using Tapatalk
Ubuntu_noobi said:
Any new info to share? I still haven't been able to figure it out
Click to expand...
Click to collapse
Davey126 already answered it here.
Davey126 said:
Fair bit of info on 5.3.2; sorry you couldn't find it. As for rooting simply roll back to 5.3.1 and then use the SuperTool to root (do not use Kingroot directly). See forum index in General thread for additional detail.
Click to expand...
Click to collapse
I also bought the Fire a few days ago and I dealt with 5.3.2 by first using "adb sideload" to go to 5.3.1 and then rooting it.
I had problems with rooting via the SuperTool, as it used an old KingRoot version and after several rooting attempts when it finally succeeded, the SuperTool had problems removing KingRoot and replacing it with SuperSu (this error made it lose root somehow). Same problem occurred when I used the SuperTool but with the newest KingRoot, so instead of using the SuperTool I used newest KingRoot directly and decided not to replace it with SuperSu.
All is fine now, lockscreen ads are gone, AdAway is installed and OTA updates blocked.
amerkiller1995 said:
I used KingRoot directly and decided not to replace it with SuperSu.
Click to expand...
Click to collapse
FYI - recognize KingRoot is a shady tool whose authors have uncertain motivations. Even after rooting it continues to send/receive information without apparent reason. One has to question any app that is offered for free and aggressively resists being uninstalled. Given the unknowns I would reconsider the decision to retain KingRoot/KingUser.
amerkiller1995 said:
Davey126 already answered it here.
I also bought the Fire a few days ago and I dealt with 5.3.2 by first using "adb sideload" to go to 5.3.1 and then rooting it.
I had problems with rooting via the SuperTool, as it used an old KingRoot version and after several rooting attempts when it finally succeeded, the SuperTool had problems removing KingRoot and replacing it with SuperSu (this error made it lose root somehow). Same problem occurred when I used the SuperTool but with the newest KingRoot, so instead of using the SuperTool I used newest KingRoot directly and decided not to replace it with SuperSu.
All is fine now, lockscreen ads are gone, AdAway is installed and OTA updates blocked.
Click to expand...
Click to collapse
I had the issue with King Root as well. What I did was download a newer version and replaced in the SuperTool folder
Sent from my iPhone using Tapatalk
Davey126 said:
FYI - recognize KingRoot is a shady tool whose authors have uncertain motivations. Even after rooting it continues to send/receive information without apparent reason. One has to question any app that is offered for free and aggressively resists being uninstalled. Given the unknowns I would reconsider the decision to retain KingRoot/KingUser.
Click to expand...
Click to collapse
Yes, it certainly gives that vibe. However my Fire is just a portable anime player, it's offline and there's nothing on it except anime, so I'll let it be.
BTW KingRoot flagged AdAway as a "risk"
yungskeeme01 said:
I had the issue with King Root as well. What I did was download a newer version and replaced in the SuperTool folder
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
I've done that, it's in the post you quoted. Still, in the replacing step, the SuperTool deletes KingRoot, but then fails to put SuperSu in its place, it prints some errors to the console like ERR_WRITE or something.
amerkiller1995 said:
Yes, it certainly gives that vibe. However my Fire is just a portable anime player, it's offline and there's nothing on it except anime, so I'll let it be.
BTW KingRoot flagged AdAway as a "risk"
I've done that, it's in the post you quoted. Still, in the replacing step, the SuperTool deletes KingRoot, but then fails to put SuperSu in its place, it prints some errors to the console like ERR_WRITE or something.
Click to expand...
Click to collapse
Sorry if I misread it. I used the version included and KingRoot so I replaced it in Supertool and re-rooted using SuperTool and it removed it no issues. Whatever though, it got rooted one way or another!
Sent from my iPhone using Tapatalk
Awesome I will try again tonight
Solved!!! Finally!!!
Ubuntu_noobi said:
So every post seems to address only 5.3.1. I can't find a SINGLE thing about rooting the 2015 5th gen Fire that runs 5.3.2. Am I the only person not able to find answers? King Root cant unlock, I can't figure out a solution and I can't stand the interface.
Purchased this for my son and he won't even use it. And He's 5. If I can't load CM or another custom rom soon I'm gonna smash it. At least I will feel better afterwards! I HATE that companies do this. Please help!
Click to expand...
Click to collapse
TL;DR: THERE IS NO "One click" OPTION THAT WORKS. I DOWNLOADED ALL OF THEM. IVE TRIED EVERY DAMN ONE OF THEM. STOP SEARCHING. You MUST side load the system with the code necessary to make it capable to root. Downgrading to 5.3.1 was the secret, instead of trying to root on 5.3.2. I made a glossary of the confusing terminology, made a step by step walk through for noobs
SO, having felt encouraged by the response by people on this forum, last night I decided it was worth another try.
I finally figured out what I was missing. IF YOU CURRENTLY HAVE FIREOS VERSION 5.3.1, YOU MUST ROLL IT BACK THRU SIDE LOADING see here: SIDELOAD TUTORIAL
I tried to load straight onto the system disk and caused all kinds of problems. Once I followed that step by step, which TBH, was a lot of pausing and rewinding. I am not familiar with many terms so I made this...
Android Common Terms:
Boot: A sequence of commands written into the underlying software that tells the device what order to operate in
Bootloader: See Previous (this is the sequence I referenced previously)
Locked Bootloader: Think of trying to edit a PDF you did not create... Exactly.
ADB Fastboot: THIS IS A PROGRAM... NOT A FUNCTION. I still get this confused, thinking that it is a quicker version of the boot sequence... IT IS NOT. ADB Fastboot is a program that gives access to the base software code making it reachable to use certain sections of to "edit the PDF".
Custom Recovery: It is the new version of Windows 10 you were updating to when your crappy laptop you JUST bought came with Windows 8.1. Essentially.
Root: Remember the PDF? Well, if you work somewhere that has Adobe Reader, and you see the window on the right pop up with the ability to login to Adobe Online or whatever? Well, rooting is having login credentials to ACTUALLY edit that damn PDF.
Flash: Download from the internet, and install on your hard drive, or SD Card. It actually means you erase whatever is there completely first, then install. It's two steps, which is why they don't just call it installing... I think.
Partition: Have you ever worked in an office with cubicles? Exactly. A partition is a wall that you put up to segregate files, or programs, or whatever.
SuperTool: Based in your computer. RootJunky Went through and basically made one tool that has everything you need for rooting. PROBLEM IS THAT HE TELLS YOU TO DOWNLOAD ADB FASTBOOT AND DRIVERS AND A BUNCH OF STUFF, then says, or you can just download the SuperTool, which means, I now HAVE TWO OF ALL OF IT, and then I spend the next three hours trying to figure out if its the "custom rom that I sideload into the TWRP, or if the Flashed version of the bootloader gets added to the recovery image, but not before the drivers are flashed into the fastboot."
While this doesn't cover a lot, I hope that people in this community understand what it is like for someone unversed in the lingo to grasp exactly what is going on. I don't think we should speak like idiots and elementary students, but I also think we lose a ton of people that may have something to offer one day because they got frustrated with the terminology and gave up. Luckily, I stuck it out and gave it one last chance and I got it.
So, once I downgraded from 5.3.2 to 5.3.1, I went about trying to root the device, which was also a little confusing.
Step 1: Downgrade if you have 5.3.2 to 5.3.1
Step 2: Enable ADB and Debug in the Settings
Step 3: Hold down the Power and Volume Down button, release the power button once the device starts to reboot and a menu will popup
Step 4: Use the volume keys to access the first selection. This is how you access the "sideloading".
Step 5: Open the SuperTool, click on the batch file which should say Auto... because calling it SuperTool would be confusing
Step 6: follow the super easy instructions. Honestly.
It will walk you through the process and get you to the part about Kingroot and FlashFire and eventually root the device.
I honestly hope this helps someone. God knows it would have saved me from spending approximately 30 hours trying to figure this out.
I have an old NVIDIA Shield Tablet K1 that has served me very well since I bought it back in 2016.
Recently it was getting filled up and started to slow down, so I bit the bullet and restored the last factory recovery image.
That went perfectly fine except for one problem. I had zipped up my files prior to the reimage. When I unzip them back to the tablet, they wind up with current dates. This really messes things up.
After doing some searching, it seems that this is a limitation of Android 7. I've read that dates are preserved when copying to internal storage only if the device is rooted on this version of Android.
After doing some searches on rooting, I stumbled upon Magisk. Upon reading the installation instructions at https://topjohnwu.github.io/Magisk/install.html, I came away thinking that it sounds too good to be true. The instructions make it seem like rooting my device will be relatively straight forward.
Can it really be this simple to root? Is un-rooting as simple as flashing the original boot.img? I really don't need to be rooted normally. So after I restore my files with their proper dates I'd be happy to un-root. Unless there is some great things I can do with root that I've never needed to do before.
This latest version of Magisk is very new (just about a week at the time of this writing) so I imagine there hasn't been a lot of use of it on an old device like the K1. But if anyone has any experiences using this new Magisk to root older devices, I'd like to hear about it.
In case any other Shield owner stumbles upon this thread, just a quick follow up to say that it was indeed as simple and straight forward as the Magisk install instructions seemed to indicate.
I successfully rooted the Shield and was able to copy back my files with dates intact.
Now off to see if there is anything else handy that I can do with root!
Can you explain it step by step. I ttied, but nothing happened. I had to put some commands through the console, but the device was not found...I have the driver and everything...
Pudah said:
I have an old NVIDIA Shield Tablet K1 that has served me very well since I bought it back in 2016.
Recently it was getting filled up and started to slow down, so I bit the bullet and restored the last factory recovery image.
That went perfectly fine except for one problem. I had zipped up my files prior to the reimage. When I unzip them back to the tablet, they wind up with current dates. This really messes things up.
After doing some searching, it seems that this is a limitation of Android 7. I've read that dates are preserved when copying to internal storage only if the device is rooted on this version of Android.
After doing some searches on rooting, I stumbled upon Magisk. Upon reading the installation instructions at https://topjohnwu.github.io/Magisk/install.html, I came away thinking that it sounds too good to be true. The instructions make it seem like rooting my device will be relatively straight forward.
Can it really be this simple to root? Is un-rooting as simple as flashing the original boot.img? I really don't need to be rooted normally. So after I restore my files with their proper dates I'd be happy to un-root. Unless there is some great things I can do with root that I've never needed to do before.
This latest version of Magisk is very new (just about a week at the time of this writing) so I imagine there hasn't been a lot of use of it on an old device like the K1. But if anyone has any experiences using this new Magisk to root older devices, I'd like to hear about it.
Click to expand...
Click to collapse
Can you explain it step by step. I ttied, but nothing happened. I had to put some commands through the console, but the device was not found...I have the driver and everything...