Related
Will (auto) root & unroot. Work for the new ota 605.7 update for the HTC thunderbolt
My friend wants to root the easy way ....NEED HELP will auto root work or not ...
sent from my rooted tbolt using XDA app
Yes but he should use the manual as most soft bricks occur with auto root.
Sent from my ADR6400L using XDA App
miketoasty said:
Yes but he should use the manual as most soft bricks occur with auto root.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
This. I don't trust "auto" roots.
The manual, ADB method is proven and not NEARLY as difficult as it may seem up front. You just have to follow the steps in jcase's thread, and you'll be done in half an hour. It's at least worth reading through.
TheStick13 said:
This. I don't trust "auto" roots.
The manual, ADB method is proven and not NEARLY as difficult as it may seem up front. You just have to follow the steps in jcase's thread, and you'll be done in half an hour. It's at least worth reading through.
Click to expand...
Click to collapse
Completely agree. You don't even need to learn adb to use it it's all just copy and paste.
Sent from my ADR6400L using XDA App
i was trying to root my friends phone with captains script which holds your hand...
I came across a problem... when trying to flash the downgrade pcimgfile... kept saying "Main version older, update failed"
As per him, he has not flashed anything on his phone, everything is stock andhe got his phone about a month after i did (for it launch day). The script was able to push the files and all seems good, but i have not been able to pin point whats causing the error. (i didnt get to take a screen shot with the firmware and stuff) Ive rooted 2 phones without issues with the script and on this particular phone, it seems to be working fine until i try to flash the update.
will using adb manually help in this case? I am thinking no.... but if anyone encountered this, mind sharing what you did?
I have not had any issue with the script. Its similar to the JCase's method it just issues the commands for you. Capt includes a copy of the commands the scrips runs in his thread so I found it helpful to look at it while I ran the scrip so I knew what it was doing and when. Like any set of instructions its always good to read through it all once before you preform it so you know what to expect. If you just download everything, click start, and expect it all to run smoothly then you are likely to run into problems.
JCase's method is good to learn off of tho and might be easier for people to pin point where errors occur.
The error i am seeing is with the phone itself. I think something may have gotten updated?
the script its doing its job. I also reboot my pc and did a factory restore.
Well Capt's script says it only works with software version 605.6 or 605.9 which I assume from when it was written means 1.12.605.6 or 1.12.605.9. If the phone your using is using software version 1.13.605.7 then you should use JCase's method here
The software is 1.12.605.6
Could it be Jcase maybe also updated the downgrade img file?
That first step is causijg the problem when i try to downgrade (the first time you flash the img file)
*looked at the thread and also went to the original thread, file md info is the same for the ruu on both posts **
I also have all the original exploit files on my pc from when i rooted MY phone... since he had a software version that was on the original root threads, i didnt have to change anything
This may be an issue you would want to ask in the chat room that there is a link to in the Development section. If you look at the scripts contents as well as the manual instructions from JCase they are exactly the same up the the point you are getting stuck at. The MD5's even match. So I wouldnt expect doing one method over the other would solve your problem. Maybe someone on the chat could help you out tho.
yeah... im gonna have to go in there....
Its the same software as mines. I didnt modify any files on my pc.... it should have just worked. thanks for the feed back. Guess i will try when i get home later and have more time to mess with it.
So I had an issue in hboot, i am not sure if something was unconnected or what but i think i am in a bootloop.
It happened during the first round where you unplug you phone, I did and it started to check the sd image and had the expected no image error message.
after it checked them all the phone displayed a error message the the "main version is older" that "update failed" and to press power to reboot.
when i do that it takes me to another screen. I think its the fastboot screen and my only options are bootloader, reboot, reboot bootloader, power down. All of which lead me to the same problem and no way that i can figure out.
I found this while searching for a fix, would i be able to pull the sd card, flash the update, and start over again? (albe it with a different root program)
Thank you before hand for your help.
I have done a lot of reading her about rooting and updating my TF300. After getting a headspinning amount of information, I'd like someone to verify what I think I know.
I have a TF300, stock ROM, no root, running US .17. I have not received any updates after going to Settings/about tab/update and pressing the update button (I get "no updates found') I have cleared DM and CM client and rebooted several times, but no updates are found. I have tried on several WiFI networks I have access to.
1. I should be able to root using one of several one click methods I have found here, correct?
2. Once rooted and root keeper is installed, I should be able to update to .29 and keep root, correct?
3. A manual update to US .29, once rooted, will cause me to lose root, correct?
4. Will I receive Over The Air update once rooted? If not, how can I update to US .29 without losing root?
5. Is this the best path to take, or is there another path that would be easier for a newb like me (I know just enough about Android to be dangerous)? What I mean by another path is, should I manually update to US .29 and wait for a one click solution to come out later, all the while enjoying the new update.
6. All this is to fix some lag issues I have with all browsers....Tried Stock, Dolphin, Firefox, Opera...all the same. Some FC and others just hang for up to 30 seconds, even in Performance mode (With only one tab open!) So this will "FIX" those lag issues, correct?
Thank you for your time
If you're still on .17, root with sparkyroot, save it with ota rootkeeper, update to .29 (if it isn't there, they've been posted in many places on the forums), and restore root. As for fixing lag issues, it depends on what you do, rooting alone won't change anything, but you can try out the different tweaks available.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Missed a couple of your questions, yes, you will still receive ota updates if you're rooted, as long as you don't unlock the bootloader. This is the easiest way to root too, all you need to do is follow sparkyroot's instructions and back up your root.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
One question always leads to another
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Throb1231 said:
Thank you! But of course, I now have just a few more questions.
I do understand rooting alone will not help me with my lag issues. I'm hoping the update to .29 will. I am not a power user, but I would like the option open to me later to install ROMs, hence why I want to root now.
1. I thought I had to unlock bootloader to root. With sparkyroot I do not?
2. Since I have not unlocked bootloader, will rooting alone void my warranty? I thinking not since I should be able to unroot with no trace, correct?
3. I thought, (or read somewhere here, I think) that if I do a MANUAL install, I would lose root and be unable to regain it. If I get an update PUSHED to me by ASUS, Ill be able to regain root with rootkeeper. Is that correct?
I'd like to thank everyone here, by the way, for all the information I have gotten in my 30 days of owning this tablet and lurking here.
Click to expand...
Click to collapse
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Oh, and after you've updated to .29 and rooted; don't forget to use OTA rootkeeper to backup root.
If Asus releases a new update it may save your root.
EndlessDissent said:
No need to unlock for root. They are completely unrelated. Just update manually and use THIS THREAD to root .29. There's even a one-click tool like you wanted. Don't forget to press Thanks for miloj.
Click to expand...
Click to collapse
He's still on the .17 software, so no need to do that. Just use the sparkyroot method, backup with rootkeeper and then update.
Edit to add that no, rooting will not void the warranty, just unroot before you need to send it back.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Throb1231 said:
Thank you both! Rooted with Sparky root and backed up with OTA rootsaver. Now I have downloaded the .29 update from ASUS webpage and installed. It says I have lost root.
I tried to restore root with OTA and it says SU restored, however it does not show that I have root access. Tring to use Titanium BU also shows I do not have root.
Tried then to go back to Sparkyroot and try again, but to no avail. Do I now have to downgrade back to .17 to gain root because I messed it up, or is there a solution? I was rooted for several hours before the upgrade to .29.
Click to expand...
Click to collapse
No, you need to go to:
h tt p://forum.xda-developers.c om/showthread.php?t=1704209 (sorry for the chopped up link. I can't post links yet)
and root again.
EndlessDissent said:
Yeah, he's still on .17, but he's not getting the OTA prompt. He wants to manually upgrade, and you can't restore root after a manual upgrade, so my advice still stands.
Click to expand...
Click to collapse
Ah, ok. Didn't realize you couldn't restore if you updated manually.
Yes, it is as I thought. Tried Sparkys and miloj's root program and I can not get root. I ran the program twice from my lap top. Driver's for TF300 show installed in Device manager (Windows 7). ASUS sync was installed in laptop and recognized TF300 but the program was not running during root attempt.
When I run Superuser and attempt to update SU binaries, I get "Failed" when it attempts pathway to write update.
Attempted to restore using OTA rootkeeper but all I get is "SU Restored". Check boxes indicate no root.
Any other ideas?
Confirmed I am on .29 from a MANUAL update.
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Throb1231 said:
Tried again from home computer. Ran Sparky and miloj program. I get error stating
"failed to copy 'Superuser.apk' to '/data/local/tmp/Superuser.apk' : not a directory"
Tablet reboots and says I should be rooted but obviously not. Superuser not written to tablet
Click to expand...
Click to collapse
Can you just install Superuser from the market? The su binaries might be there and the app just isn't installing. I may be wrong, not sure how the automated program works, but it can't hurt.
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Try manually doing the code from miloj's thread?
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Throb1231 said:
While the instructions in his thread are clear, they are way past my level of expertise. I would not attempt it without someone standing next to me. I have not entered code since the 1980's Compute! magazine days.
Click to expand...
Click to collapse
Well, I can't think of anything else, you could just use the downgrade method, that's easy enough. The code really is just copy/paste though.
Throb1231 said:
Just tried that. Installs fine but when I try to update binaries, I get error writing to filepath, telling me there is no root. I'm hoping this makes 10 posts for me so I can actually go to Sparky's thread in Dev. forum and ask directly. Thanks for your help tho. Ill still be monitoring here if anyone has a solution
Click to expand...
Click to collapse
Your problem is not with the superuser apk.
The actual root is when you write an "su" binary to system and makes it executable (there is some access control stuff in between, but it's what's happening in essence).
So - your trouble is not with the installation nor the messages from superuser.apk - it's with the actual rooting method.
Make absolutely sure your adb drivers are working and that you've got the files "debugfs", "su" and the other debugfs file on top of the .bat file, which is the installation script, in the same directory whilst running the .bat file.
Agreed. I posted this in development.
It was surprisingly more difficult to install the drivers correctly than anticipated.
For those noobs like me, here's a step-by-step for installing the drivers before running the root method.
http://transformerprimeroot.com/tra...all-transformer-prime-usb-drivers-on-windows/
Please note that before using the step-by-step guide above, I also had to put the tf300 in Camera Mount to even get the "“ASUS Android Composite ADB Interface" option to show up in Device Manager.
Once you get this far, you can manually update the driver (found in the sparkym3 "Drivers" folder from the download) via the step-by-step.
Sent from my ASUS Transformer Pad TF300T using XDA
For the past two days, I've been constantly struggling to find a way to update my phone to android 5.0. When trying to download the OTA update, it will download fine, but once it goes to install and reboot, it will stop halfway through and the same screen you see when you enter what i believe is called bootloader mode. On this screen i see clockworkmod and other words such as error which really confuses me because i do not believe I ever worked with that. Ill then be met by a message asking if i want to trust the untrusted zip to install. Upon clicking no, the phone will either reboot normally or go to another screen, where the android icon is now on his back with a red triangle above him and ill be asked if i would like to keep root access. Choosing either yes or no will result in the phone booting normally. If i click yes when asked if i want to download the untrusted zip, the result will be the same except the android will not get the red triangle. After being asked if i would like to keep root access, choosing either option will just reboot the phone.
Ive spent countless hours searching the web for solutions, and on the phone with google. I tried to flash a new image but I lack the skill and knowledge, to do this. My method of root was towerroot which i realize now was a mistake, because here i am with no knowledge on what ive actually done and no knowledge on how to fix it. I did not install a custom rom. So far, ive tried a factory reset, flashing a factory image (unsuccessful), using supersu to unroot my device, and deleting all root files in ex file explorer. I'm using windows if that helps.
The biggest kicker here now is that my phone tells me that i do not have root access any longer if i download a root checker, but when trying to install the update it asks me if i would like to keep root access. I also still have custom navigation keys stuck on my phone from the "softkeyz" app. As far as i know, there are no other traces of root on my device. I have almost no knowledge on how android os functions and am unfamiliar with terms I've been met with recently such as "custom image" "bootloader" "apk" "sdk" etc.
I completely understand that being this uninformed and rooting was a mistake, but what is done is done. If anybody has any idea at all on what i need to do to be able to update to lollipop please let me know. Any suggestions would be greatly appreciated as well. I may have left out key imformation but i've included all i can think of. If any other information is needed i can likely provide it.
1) you must be fully stock to accept OTA
2) various methods to update to and root lollipop are in my signature
3) this is the problem with one-click root methods. People don't get to learn what they need to know.
Please read my adb and fastboot thread. Again, you can get to it via my signature. Its in sticky roll-up
By the way, lack of paragraphs made your post a nightmare to read
Upgrading to 5.0
Though you don't know it, you most likely just dodged a bullet. 5.0 is not yet ready for prime time, or visa versa. Puzzle and Dragons can't launch under it (and probably won't for months.) My bank's app likewise won't launch under 5.0, and there are other impositions and quirks and annoyances. So maybe better that you couldn't do so.
I just put mine back to 4.4 and am very glad to have my old friend back. Installing 5.0 reminded me of installing Windows 8, and then wondering why the F*** I did so.
Good luck... enjoy 4.4 as long as possible. If you're not up for fixing the root issue you just described, you're also not ready for putting the phone back to 4.4 if, like me, you find 5.0 intolerable.
tthomas12 said:
For the past two days, I've been constantly struggling to find a way to update my phone to android 5.0. When trying to download the OTA update, it will download fine, but once it goes to install and reboot, it will stop halfway through and the same screen you see when you enter what i believe is called bootloader mode. On this screen i see clockworkmod and other words such as error which really confuses me because i do not believe I ever worked with that. Ill then be met by a message asking if i want to trust the untrusted zip to install. Upon clicking no, the phone will either reboot normally or go to another screen, where the android icon is now on his back with a red triangle above him and ill be asked if i would like to keep root access. Choosing either yes or no will result in the phone booting normally. If i click yes when asked if i want to download the untrusted zip, the result will be the same except the android will not get the red triangle. After being asked if i would like to keep root access, choosing either option will just reboot the phone. . Ive spent countless hours searching the web for solutions, and on the phone with google. I tried to flash a new image but I lack the skill and knowledge, to do this. My method of root was towerroot which i realize now was a mistake, because here i am with no knowledge on what ive actually done and no knowledge on how to fix it. I did not install a custom rom. So far, ive tried a factory reset, flashing a factory image (unsuccessful), using supersu to unroot my device, and deleting all root files in ex file explorer. I'm using windows if that helps. The biggest kicker here now is that my phone tells me that i do not have root access any longer if i download a root checker, but when trying to install the update it asks me if i would like to keep root access. I also still have custom navigation keys stuck on my phone from the "softkeyz" app. As far as i know, there are no other traces of root on my device. I have almost no knowledge on how android os functions and am unfamiliar with terms I've been met with recently such as "custom image" "bootloader" "apk" "sdk" etc.. I completely understand that being this uninformed and rooting was a mistake, but what is done is done. If anybody has any idea at all on what i need to do to be able to update to lollipop please let me know. Any suggestions would be greatly appreciated as well. I may have left out key imformation but i've included all i can think of. If any other information is needed i can likely provide it.
Click to expand...
Click to collapse
I have the EXACT same problem as you. I rooted my phone with towel root, then i flashed a custom recovery with an app called flashify. after that i flashed the proper supersu.zip file with the custom recovery. Next i rebooted my phone. I used an app called root checker to see if my root was working, and it was. Then i flashed my custom recovery back on. I tried updating my phone with the OTA Android 5, it was updating until around 25% once it hit that stage it just said error. Then i un rooted my phone and tried it again i got the same error. I did a factory reset and tried it again but i got the same result? i dont know why this is happening i need help!
---------- Post added at 07:27 PM ---------- Previous post was at 07:13 PM ----------
rootSU said:
1) you must be fully stock to accept OTA
2) various methods to update to and root lollipop are in my signature
3) this is the problem with one-click root methods. People don't get to learn what they need to know.
Please read my adb and fastboot thread. Again, you can get to it via my signature. Its in sticky roll-up
By the way, lack of paragraphs made your post a nightmare to read
Click to expand...
Click to collapse
Hello rootSU, you seem pretty experienced when it comes to stuff like flashing custom roms and rooting... My nexus 5 is on stock android 4.4.4, i have the stock recovery,i never flashed a rom....
When i try to use the OTA update and update to android 5.0 it always says error when its flashing. When the notification pops up i click it, then i click the button to start the download. once its downloaded and verified i click install. It takes me to my recovery and shows the android flashing logo thing and it says updating, when the progress bar reaches to 25% give or take a few percent an android logo pops up with a warning sign and it says error. I've tried multiple times and i got the same result. I even factory reseted my nexus and it still didn't work. Help ASAP please.
Regards,
cyberusman
Can't help with OTA. I refuse to use them. You can follow other advice from me in my thread in my signature
cyberusman said:
I have the EXACT same problem as you. I rooted my phone with towel root, then i flashed a custom recovery with an app called flashify. after that i flashed the proper supersu.zip file with the custom recovery. Next i rebooted my phone. I used an app called root checker to see if my root was working, and it was. Then i flashed my custom recovery back on. I tried updating my phone with the OTA Android 5, it was updating until around 25% once it hit that stage it just said error. Then i un rooted my phone and tried it again i got the same error. I did a factory reset and tried it again but i got the same result? i dont know why this is happening i need help!
---------- Post added at 07:27 PM ---------- Previous post was at 07:13 PM ----------
Hello rootSU, you seem pretty experienced when it comes to stuff like flashing custom roms and rooting... My nexus 5 is on stock android 4.4.4, i have the stock recovery,i never flashed a rom....
When i try to use the OTA update and update to android 5.0 it always says error when its flashing. When the notification pops up i click it, then i click the button to start the download. once its downloaded and verified i click install. It takes me to my recovery and shows the android flashing logo thing and it says updating, when the progress bar reaches to 25% give or take a few percent an android logo pops up with a warning sign and it says error. I've tried multiple times and i got the same result. I even factory reseted my nexus and it still didn't work. Help ASAP please.
Regards,
cyberusman
Click to expand...
Click to collapse
Did you ever remove any of the system apps? If you did, you will need to put them back or you will get an error with the OTA.
rootSU said:
1) you must be fully stock to accept OTA
2) various methods to update to and root lollipop are in my signature
3) this is the problem with one-click root methods. People don't get to learn what they need to know.
Please read my adb and fastboot thread. Again, you can get to it via my signature. Its in sticky roll-up
By the way, lack of paragraphs made your post a nightmare to read
Click to expand...
Click to collapse
xda6969 said:
Did you ever remove any of the system apps? If you did, you will need to put them back or you will get an error with the OTA.
Click to expand...
Click to collapse
Thanks for taking the time out of your busy life to help me, i already found a solution but thanks.
---------- Post added at 01:56 AM ---------- Previous post was at 01:49 AM ----------
tthomas12 said:
For the past two days, I've been constantly struggling to find a way to update my phone to android 5.0. When trying to download the OTA update, it will download fine, but once it goes to install and reboot, it will stop halfway through and the same screen you see when you enter what i believe is called bootloader mode. On this screen i see clockworkmod and other words such as error which really confuses me because i do not believe I ever worked with that. Ill then be met by a message asking if i want to trust the untrusted zip to install. Upon clicking no, the phone will either reboot normally or go to another screen, where the android icon is now on his back with a red triangle above him and ill be asked if i would like to keep root access. Choosing either yes or no will result in the phone booting normally. If i click yes when asked if i want to download the untrusted zip, the result will be the same except the android will not get the red triangle. After being asked if i would like to keep root access, choosing either option will just reboot the phone.
Ive spent countless hours searching the web for solutions, and on the phone with google. I tried to flash a new image but I lack the skill and knowledge, to do this. My method of root was towerroot which i realize now was a mistake, because here i am with no knowledge on what ive actually done and no knowledge on how to fix it. I did not install a custom rom. So far, ive tried a factory reset, flashing a factory image (unsuccessful), using supersu to unroot my device, and deleting all root files in ex file explorer. I'm using windows if that helps.
The biggest kicker here now is that my phone tells me that i do not have root access any longer if i download a root checker, but when trying to install the update it asks me if i would like to keep root access. I also still have custom navigation keys stuck on my phone from the "softkeyz" app. As far as i know, there are no other traces of root on my device. I have almost no knowledge on how android os functions and am unfamiliar with terms I've been met with recently such as "custom image" "bootloader" "apk" "sdk" etc.
I completely understand that being this uninformed and rooting was a mistake, but what is done is done. If anybody has any idea at all on what i need to do to be able to update to lollipop please let me know. Any suggestions would be greatly appreciated as well. I may have left out key imformation but i've included all i can think of. If any other information is needed i can likely provide it.
Click to expand...
Click to collapse
Okay, like i said in one of my previous posts i had the same problem as you. But i looked around and found out how to fix it. The new android OTA update checks if every single file and system app is there, if u make any changes you cant use the OTA lolipop update.To fix this you have to flash a factory image. Flashing the factory image maks your nexus have a stock android rom on it. The instructions are really easy...
https://developers.google.com/android/nexus/images
^^go on this website^^ and look for the android 4.4.4 or 5.0 factory image. There are instructions on how to flash it.
Hello Cyberusman. This isn't new in Android. Even in past versions of Android, if you removed or renamed apps or if you changed app permissions, the OTA would fail. Flashing the factory image is one way of fixing it but you could also put any removed apps back with correct permissions and that would work as well.
The goal: Get my sluggish phone (Razr Maxx HD, JB 4.1.2, currently 9.16.6.XT926.Verizon.en.US, rooted, bootloader locked) to be less sluggish.
The proposed method: Wipe phone and start over.
The "problem": Because I am rooted and want to stay that way, I am aware that I can't just do a factory reset. I believe that I need to unroot first, then wipe, then reroot. But there are many more possible methods to do this than there were before and I'm having trouble figuring out which might be the best method for me (or which will even work, at all).
Background: If I had just blindly done what I did the last time I wiped (I think I was starting from ICS 0.7.2 last time, not JB), I would have backed up everything, used DROID_RAZR_HD_Utility1.10 which I have from before (dates appear to be 1/28/2013) to go back to 0.6.25.X926., and, using the zip files I have from before, go from 0.6.25 to 0.7.2 to 9.1.41 to 9.16.6. (I was never able to successfully take OTA updates). Like this: http://forum.xda-developers.com/showthread.php?t=2024423 BUT, now that I'm on JB, it's not clear to me that I can even do this. One post is telling me that if I'm on 9.16.6, I should NOT use Droid Razr HD Utility 1.10. http://forum.xda-developers.com/showthread.php?p=33610625#post33610625 and when I found the thread for the 1.21 utility, it also says no 9.16.6.
I've been wandering around the relevant posts that are linked from here: http://forum.xda-developers.com/showthread.php?t=2247250
but for whatever reason, this is just making my head spin. I'm more confused about what I can and cannot do, than I was before I started. I think too many OTA versions have passed me by... I was happy with the way things were working so I just didn't care about updates, KitKat, etc. I don't have a good feel for how many versions there are between 9.16.6 and current.
My actual question: I think I could really use some help narrowing down my options. Do I have any options at all? If so, can anyone suggest what my realistic options actually are? I don't care if I end up in JB or KitKat at the end; I do want to be able to restore some of the data from some of my apps using Titanium Backup and/or MyBackup Pro; and I want to be rooted when I am done. Any suggestions would be greatly appreciated.
Thank you, dlc
dlc2001 said:
The goal: Get my sluggish phone (Razr Maxx HD, JB 4.1.2, currently 9.16.6.XT926.Verizon.en.US, rooted, bootloader locked) to be less sluggish.
The proposed method: Wipe phone and start over.
The "problem": Because I am rooted and want to stay that way, I am aware that I can't just do a factory reset. I believe that I need to unroot first, then wipe, then reroot. But there are many more possible methods to do this than there were before and I'm having trouble figuring out which might be the best method for me (or which will even work, at all).
Background: If I had just blindly done what I did the last time I wiped (I think I was starting from ICS 0.7.2 last time, not JB), I would have backed up everything, used DROID_RAZR_HD_Utility1.10 which I have from before (dates appear to be 1/28/2013) to go back to 0.6.25.X926., and, using the zip files I have from before, go from 0.6.25 to 0.7.2 to 9.1.41 to 9.16.6. (I was never able to successfully take OTA updates). Like this: http://forum.xda-developers.com/showthread.php?t=2024423 BUT, now that I'm on JB, it's not clear to me that I can even do this. One post is telling me that if I'm on 9.16.6, I should NOT use Droid Razr HD Utility 1.10. http://forum.xda-developers.com/showthread.php?p=33610625#post33610625 and when I found the thread for the 1.21 utility, it also says no 9.16.6.
I've been wandering around the relevant posts that are linked from here: http://forum.xda-developers.com/showthread.php?t=2247250
but for whatever reason, this is just making my head spin. I'm more confused about what I can and cannot do, than I was before I started. I think too many OTA versions have passed me by... I was happy with the way things were working so I just didn't care about updates, KitKat, etc. I don't have a good feel for how many versions there are between 9.16.6 and current.
My actual question: I think I could really use some help narrowing down my options. Do I have any options at all? If so, can anyone suggest what my realistic options actually are? I don't care if I end up in JB or KitKat at the end; I do want to be able to restore some of the data from some of my apps using Titanium Backup and/or MyBackup Pro; and I want to be rooted when I am done. Any suggestions would be greatly appreciated.
Thank you, dlc
Click to expand...
Click to collapse
to get rid of the slowness of the phone i recommend going to a lolipop rom , LP has to be the quickest my phone has ran... ever.
-step 1 use rsd lite to flash [4.4.2] 183.46.10 fxz (make sure it ends with a 10 not a 14 or 15 or you wont be able to unlock bootloader)
http://www.droidrzr.com/index.php/topic/45494-fxz-442-1834610/
-step 2 root and unlock use TR.apk (root)and motopocalypse.apk (bootloader unlock)
http://forum.xda-developers.com/showthread.php?t=2783912
-step 3 use ADB fastboot to Flash custom recovery, i personally use twrp there are others you can use if you decide to do the research
http://www.droidrzr.com/index.php/topic/51883-recoverytwrp-2810-11-01-14/
-step 4 flash LP custom rom, i use blisspop, it seems to have the most updates at the moment . it has really impressed me
http://www.droidrzr.com/index.php/topic/60153-rom502lollipopmsm8960-kkbl-blisspop-official/
that rom comes with supersu built in so you will have root. if your reason for having root is to have exposed, it doesnt work on lolipop so stop at sstep 3 and either flash a KK custom rom or just flash supersu which will give you root on stock kitkat
OK, I will spend a little more time absorbing/reading and then I'll give it a shot, thanks muchly. I want to do some backups just in case, so it'll take a while...
Couple of followup questions based on the reading I've done so far from the links you provided, just so I know what I'm doing before I do it:
1. I think I get Steps 1 and 2. After Step 2 I am rooted and on stock KK, correct? So if I stop there do I still need to "flash supersu" per your comment at the end? Does the root in step 2 put supersu in my apps, and if not can I not just install it from google play?
2. Seems like I can use the Step 1 method to flash back to JB (or any other FXZ I can find) if I want. If I do that, is there any way to root JB, or is this trip I'm about to take, a one-way trip? Just to clarify, JB hasn't always been slow for me... it's just slowed down recently. Not saying I want to go back to JB for sure, but I like to know what options I am closing off when I move forward, and reviews of KitKat are not universally splendid.... I hear you about the custom ROM but for various work-related reasons I may be better off staying stock (well, stock + root) for a while at least.
Again, thank you for your help.
dlc2001 said:
OK, I will spend a little more time absorbing/reading and then I'll give it a shot, thanks muchly. I want to do some backups just in case, so it'll take a while...
Couple of followup questions based on the reading I've done so far from the links you provided, just so I know what I'm doing before I do it:
1. I think I get Steps 1 and 2. After Step 2 I am rooted and on stock KK, correct? So if I stop there do I still need to "flash supersu" per your comment at the end? Does the root in step 2 put supersu in my apps, and if not can I not just install it from google play?
2. Seems like I can use the Step 1 method to flash back to JB (or any other FXZ I can find) if I want. If I do that, is there any way to root JB, or is this trip I'm about to take, a one-way trip? Just to clarify, JB hasn't always been slow for me... it's just slowed down recently. Not saying I want to go back to JB for sure, but I like to know what options I am closing off when I move forward, and reviews of KitKat are not universally splendid.... I hear you about the custom ROM but for various work-related reasons I may be better off staying stock (well, stock + root) for a while at least.
Again, thank you for your help.
Click to expand...
Click to collapse
yes you can install it from playstore, but once your bootloader is unlocked you can always root by flashing in custom recovery. you dont need exploits anymore
All done, worked great!
HI was downloading the new update 5.0 but it stopped and now the tablet says me "your system is updated" but with the 6.0.1.I can't restart the download now,what i have to do???
Same thing happened to me. Don't know why yet.
Same here. Where are you from?
Nvidia might have pulled it to fix something wait patiently it will come.
I had a similar problem as well. I got the notification to download the update, and when I clicked on the "Download" button in the notification, it did nothing. When I went into my settings and opened the OTA updater, it kept telling me that "Your system is up to date," even after repeatedly pressing the "Check Now" button, selecting "Clear data," rebooting, and messing with the advanced settings. I hope they fix this soon, I was really excited about this update!
Exact same issue here.
If you haven't root/twrp etc:
Download from here:
https://forum.xda-developers.com/shield-tablet/general/5-0-update-nougat-incoming-t3553612/page2 (there are two version - k1 & standard).
Paste it to internal memory, boot into recovery and apply update from zip.
Just wait a little. That's what NVIDIA calls "staggered rollout".
Just wanted to update and say that I got my OTA this morning and will apply it later this afternoon. Guess, just as suggested earlier, they staggered them. It's strange though that they actually pulled it back, but then again it might have been an issue with it.
if you have "nougat launcher apk" just delete it.
Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?
My 2 cents: if the root is confirmed to work, there is no "process" per se.
D/L the root zip to the tablet, boot into recovery, flash that zip and reboot into system.
Should be within 2-3 min the whole thing.
Wayno-san said:
Been a while since I rooted mine and I'd prefer not to lose root. Anyone know if there's going to be a pre-rooted version available that won't require going through the whole process again? Honestly I don't recall if it was difficult or not but I know for previous phones I've had there was a rooted version of the OTA that someone would post within a day or two of the release. Made the whole update process quicker and easier.
Also, for those who have updated, how is the performance compared to Marshmallow?
Click to expand...
Click to collapse
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/
pucka said:
Performance feels good so far. Don't know if there will be a pre-rooted version, but it's fairly simple and fast to root since your bootloader is unlocked and you'll get to keep all your data. If you want custom recovery I had to use the TWRP app after root to flash the recovery. Couldn't get it to stick using fastboot. There's a good rooting guide here:
http://nvidiashieldzone.com/shield-...ndroid-7-nougat/root-shield-tablet-k1-nougat/
Click to expand...
Click to collapse
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.
Wayno-san said:
Thanks for the info and the guide link. If I'm rooted can I let the update to nougat proceed and then just follow the procedure in the link? Thought I read somewhere that I need to unroot it first.
Click to expand...
Click to collapse
Yes you can just apply the update and there's no need to flash stock first. If you want to flash TWRP I would recommend getting root first by sideloading (like in the guide) and then using the TWRP app to flash TWRP.
I'm now rooted again with TWRP as custom recovery.