Related
Hey guys, I have the TF700T and, unfortunately, was over-eager and rooted & unlocked it the day I bought it. Now it seems that I am not receiving OTA updates and I am quite disappointed. What are the basic steps that I can take to either un-do the lock so I can receive updates, or manually push through the update? I admit, I probably am more of a noob with Android than most of you. What should my next move be??
Bzktz said:
Hey guys, I have the TF700T and, unfortunately, was over-eager and rooted & unlocked it the day I bought it. Now it seems that I am not receiving OTA updates and I am quite disappointed. What are the basic steps that I can take to either un-do the lock so I can receive updates, or manually push through the update? I admit, I probably am more of a noob with Android than most of you. What should my next move be??
Click to expand...
Click to collapse
I'm assuming you still have stock recovery even though you unlocked the tablet. You can't re-lock the tablet so you'll eventually want to start using a custom recovery. However, don't install a custom recovery yet because the firmware upgrades are going to wipe custom recovery every time.
This should help you get started with the upgrade process using only the stock recovery:
Pre-upgrade:
0) HIGHLY RECOMMENDED -- Take the time to make nvflash accessible and make backups so that you'll be able to recover from a brick situation. This is the ONLY chance you have to do this before upgrading to .30:
http://forum.xda-developers.com/showthread.php?t=1901479
0.25) Performing the upgrades shouldn't affect your apps and data, but back them up if you want to just in case.
0.5) Make sure your tablet is charged 60% or higher or is plugged in.
Simple Upgrade Process:
1) Download "Voodoo OTA RootKeeper" from the market to back up your root.
2) Follow these instructions to update to .30:
http://forum.xda-developers.com/showthread.php?t=1755576
3) Reboot the tablet 2 times or so to make sure the .30 update finishes completely -- it updates the camera firmware and some other stuff.
4) Run RootKeeper again and verify you can still restore root. If you have to, re-root and use RootKeeper to back it up. Restoring a backed-up root is is currently the only way to root on Jelly Bean, so this is your LAST chance.
5) Download the appropriate Jelly Bean OTA update zip from here:
http://forum.xda-developers.com/showthread.php?t=1915079
6) Repeat the instructions in step 2, except you can just directly rename the file you downloaded in step 5 (there's no "zip within a zip").
7) After the upgrade is complete, run RootKeeper again and restore root.
8) Install the custom recovery of your choice (edit: when a working one becomes available).
recovery works in JB?
lafester said:
recovery works in JB?
Click to expand...
Click to collapse
sorry my mistake, there isn't one that's working yet.
i tried the manual method and it wont work
i did what the instructions said and in the end when android logo and status bar come out, shortly it display android with red triangle indicating that it failed. it says "ID verification failed." does anyone successfully update their TF700 using this method?
Bzktz said:
Hey guys, I have the TF700T and, unfortunately, was over-eager and rooted & unlocked it the day I bought it. Now it seems that I am not receiving OTA updates and I am quite disappointed. What are the basic steps that I can take to either un-do the lock so I can receive updates, or manually push through the update? I admit, I probably am more of a noob with Android than most of you. What should my next move be??
Click to expand...
Click to collapse
If you are still on 26 the first thing i recommend you is to use the NvFlash tool (from the Development forum) so you can recover your device from any soft brick, then update to 30 and JB. Unlocking avoid your warranty so NvFlash tool is a wise thing to go with.
Just went through the motions (Including accessing nvflash)
no worries, I bricked it on purpose and then unbricked it just to make sure. nvflash is rad!
the new JB update, Forget the benchmarks, I don't even care what they say at this point, this is the best user experience I've had on this thing so far and it's just going to get better. at least with nvflash I can still load unsigned bootloaders, that's all I need for native linux experimentation.
yea though I walk through the valley of the shadow of flash I will fear no bricking, for blob.bin art with me. :good:
Thank you very much for the response. I am up to #5 in the process but now I am stuck. I renamed the file and stuck it on my sd card. However I am getting nothing when I then boot in recovery. It tells me SD Installation aborted, and gives me the Red Triangle. What am I doing wrong here?
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.
I'm on a verizon SCH-I535 running android 4.1.2 (baseband I535VRBMF1, kernel 3.0.31-1152558, build jzo54k.i535vrbmf1, hardware version i535.10). I rooted the device a couple years ago, and have rejected OTA updates, ever since I received the 4.1.2 one (in fact, I used a file manager, to rename some files, so I wouldnt get the pop-up telling me there was an OTA update anymore). Everything is, as it was required to be, in order to get root access on 4.1.2, I just followed the instructions I found on xda.
Now that android 4.4.2 is available, and there is an easy root for it, what is the easiest way for me to move from where I am to 4.4.2 rooted? Am I supposed to follow the instructions in the "Reset your phone in order to return to Verizon" sticky? If so, how do I know if my bootloader is 'locked' or 'unlocked'? Alternatively to these instructions I was thinking of doing a "full unroot" with superSU then simply doing an OTA update, but wasnt sure if that would introduce issues.
Finally, in terms of doing a backup, I downloaded an app called "online nandroid" which supposedly saved a backup to my sd card. But my sd card is tiny, and the backup went really quick, so what exactly is it backing up? Is it enough of a backup that if I want to do a full restore back to exactly the state my phone is in now later, I can do that, or do I need a different tool for that?
loonytoon500 said:
I'm on a verizon SCH-I535 running android 4.1.2 (baseband I535VRBMF1, kernel 3.0.31-1152558, build jzo54k.i535vrbmf1, hardware version i535.10). I rooted the device a couple years ago, and have rejected OTA updates, ever since I received the 4.1.2 one (in fact, I used a file manager, to rename some files, so I wouldnt get the pop-up telling me there was an OTA update anymore). Everything is, as it was required to be, in order to get root access on 4.1.2, I just followed the instructions I found on xda.
Now that android 4.4.2 is available, and there is an easy root for it, what is the easiest way for me to move from where I am to 4.4.2 rooted? Am I supposed to follow the instructions in the "Reset your phone in order to return to Verizon" sticky? If so, how do I know if my bootloader is 'locked' or 'unlocked'? Alternatively to these instructions I was thinking of doing a "full unroot" with superSU then simply doing an OTA update, but wasnt sure if that would introduce issues.
Finally, in terms of doing a backup, I downloaded an app called "online nandroid" which supposedly saved a backup to my sd card. But my sd card is tiny, and the backup went really quick, so what exactly is it backing up? Is it enough of a backup that if I want to do a full restore back to exactly the state my phone is in now later, I can do that, or do I need a different tool for that?
Click to expand...
Click to collapse
In order to move to the 4.4.2 update you'll have to unroot, but keep in mind if you do your bootloader will be PERMANENTLY locked, no going back
The backup of stock is normally somewhere between 2-3gb or more, it didn't do the full backup. I highly doubt it's a full backup. Once you take the OTA to 4.4.2 your stuck and there is no going back
Your best bet is to install a custom recovery, cwm, twrp or philz or similar. If you want to take the OTA your free to but once again there's no custom roms after that. No CM or AOSP after you take the OTA
From my S3 running BlissStalk
ShapesBlue said:
In order to move to the 4.4.2 update you'll have to unroot, but keep in mind if you do your bootloader will be PERMANENTLY locked, no going back
The backup of stock is normally somewhere between 2-3gb or more, it didn't do the full backup. I highly doubt it's a full backup. Once you take the OTA to 4.4.2 your stuck and there is no going back
Your best bet is to install a custom recovery, cwm, twrp or philz or similar. If you want to take the OTA your free to but once again there's no custom roms after that. No CM or AOSP after you take the OTA
From my S3 running BlissStalk
Click to expand...
Click to collapse
Thank you for your response.
I do not care about custom ROMS, I am ok with the stock android OS, as long as I can get root. If the OTA update permanently locks my bootloader I am ok with that.
That said, I want to ensure I dont have any incidents when I do the OTA update. (that I dont brick my device. or make things more difficult for myself.) It doesnt look like I currently have a custom recovery (I tried to boot into custom recovery but the phone simply boots normally. I can however boot into stock android recovery). Also, my bootloader is currently unlocked.
Given that I dont currently have a custom recovery, and that my bootloader is currently unlocked, will that present any issue if I simply do a full unroot using superSU, and then take the OTA update? I used triangle away earlier today to reset my flash counter to 0 (it was 1 before).
loonytoon500 said:
Thank you for your response.
I do not care about custom ROMS, I am ok with the stock android OS, as long as I can get root. If the OTA update permanently locks my bootloader I am ok with that.
That said, I want to ensure I dont have any incidents when I do the OTA update. (that I dont brick my device. or make things more difficult for myself.) It doesnt look like I currently have a custom recovery (I tried to boot into custom recovery but the phone simply boots normally. I can however boot into stock android recovery). Also, my bootloader is currently unlocked.
Given that I dont currently have a custom recovery, and that my bootloader is currently unlocked, will that present any issue if I simply do a full unroot using superSU, and then take the OTA update? I used triangle away earlier today to reset my flash counter to 0 (it was 1 before).
Click to expand...
Click to collapse
It shouldn't but the OTA will lock in back up
From my S3 running BlissStalk
ShapesBlue said:
It shouldn't but the OTA will lock in back up
From my S3 running BlissStalk
Click to expand...
Click to collapse
Ok, i unrooted, and tried to take the OTA update, but a quarter of the way through the update, the update fails/stops, and it shows a lying android, with a red exclamation triangle over it; then the phone simply reboots and says "sorry, there was a problem updating your SAMSUNG SCH-I535. No changes were made." I read something about how this could be the case if I froze some stock apps, but how do I check if any stock apps are frozen? I dont remember doing so but its certainly possible.
What course of action do you recommend? It sounds like I will need to go through the process of rerooting again. I've read I can reflash the 4.1.2 stock rom and then do the OTA update, but I dont want to wipe data. The no wipe version is linked to here, but the firmware links there appears to be broken.
loonytoon500 said:
Ok, i unrooted, and tried to take the OTA update, but a quarter of the way through the update, the update fails/stops, and it shows a lying android, with a red exclamation triangle over it; then the phone simply reboots and says "sorry, there was a problem updating your SAMSUNG SCH-I535. No changes were made." I read something about how this could be the case if I froze some stock apps, but how do I check if any stock apps are frozen? I dont remember doing so but its certainly possible.
What course of action do you recommend? It sounds like I will need to go through the process of rerooting again. I've read I can reflash the 4.1.2 stock rom and then do the OTA update, but I dont want to wipe data. The no wipe version is linked to here, but the firmware links there appears to be broken.
Click to expand...
Click to collapse
After all the reading I've done in order to take the OTA you have to unroot. I don't know the complete process as I am not on any OTA
From my S3 running BlissStalk
Even if you dont care about custom ROMs right now you may in the future when there are no updates released for the phone or you want to sell it and could have gotten a higher price with the lower system version. Before you update try some of the ROMs out and see if there are some you like and if you dont like any then update.
That being said I have updated using ODIN and the firmware I got from this site. look around and you will find the stuff you need.
i ended up flashing a 4.1.1 stock no wipe rom i found and after that i could take the ota updates (had to do multiple in a row).
out of curiosity couldn't the devs find a way to unlock the bootloader via some hackery in the future?
loonytoon500 said:
i ended up flashing a 4.1.1 stock no wipe rom i found and after that i could take the ota updates (had to do multiple in a row).
out of curiosity couldn't the devs find a way to unlock the bootloader via some hackery in the future?
Click to expand...
Click to collapse
Sure it's possible, but unlikely. To put into perspective, I don't believe there has been a bootloader unlock for Verizon Notes 2-4 and Galaxy S4-5 (which would allow one to natively run AOSP without Safestrap) so the likelihood is low.
Sent from my SCH-I535 using Tapatalk
I'm asking for my girlfriend. I have the T-Mobile variant with a custom recovery and I know not to take an OTA because custom recoveries and OTAs don't mix. She, however, has an AT&T variant and she just told me she was prompted to update to Lollipop. She rooted long ago with whatever root for AT&T app was popular at the time.
Doesn't taking an OTA just make you lose root? Nothing else to worry about?
I would not recommend due to the chance it could boot loop. I would wait for a OTA zip and flash through TWRP.
If she is rooted it will break root, If she has a custom recovery (twrp) than it will cause a boot loop.
advice: if she wants lollipop she's gonna have to follow these steps.
http://www.androidrootz.com/2014/07/how-to-unroot-lg-g3-all-variants.html
Going to pass the link on to her now.
There is no custom recovery. She used Stump Root originally to get her phone route, if that makes any difference.
martinezma99 said:
I would not recommend due to the chance it could boot loop. I would wait for a OTA zip and flash through TWRP.
Click to expand...
Click to collapse
Is there an ota zip available for the D850. I froze software updates in titanium backup so I won't loose root.
SGE_DEW said:
Is there an ota zip available for the D850. I froze software updates in titanium backup so I won't loose root.
Click to expand...
Click to collapse
You would still lose root
2SHAYNEZ
Yep.. I went through the whole process of going completely back to stock and then rooted before updating to Lollipop hoping it would stay. It didn't and Stump Root says it's already rooted.
Thanks for this cool tool and method. The LGFlashtool gets up the 'Change to download mode' step adn then fails, with a '[16:10:26] can't change to download mode 00000064' error in the box. Any help would be appreciated. In the meantime I'll try another usb port. Also, when I first ran the Flashtool I had to select from three choices: the default checked off one had the word Korea in it, the second had Brazil and the third had the word Global. I left in on Korea--you think I should have gone with global?
Thanks again, Xamadiex.
Rayvin56 said:
Thanks for this cool tool and method. The LGFlashtool gets up the 'Change to download mode' step adn then fails, with a '[16:10:26] can't change to download mode 00000064' error in the box. Any help would be appreciated. In the meantime I'll try another usb port. Also, when I first ran the Flashtool I had to select from three choices: the default checked off one had the word Korea in it, the second had Brazil and the third had the word Global. I left in on Korea--you think I should have gone with global?
Thanks again, Xamadiex.
Click to expand...
Click to collapse
I read somewhere the LG Flashtool had to be modified at installation to avoid what you are going through.
You're right, it's just a matter of overwriting the megalock.dll file after you install the tool. It was a step I didn't miss. But good news for me, I used another pc and when I installed the flashtool it again gave me the three choices (not sure, but the title bar of the window was something like 'DMB').
This time I chose the 'global' selection and ran the tool as before and it completed for me. I'm currently DL'ing the lollipop update right now. Thanks for the quick reply, netomel.
partylikeaninjastar said:
I'm asking for my girlfriend. I have the T-Mobile variant with a custom recovery and I know not to take an OTA because custom recoveries and OTAs don't mix. She, however, has an AT&T variant and she just told me she was prompted to update to Lollipop. She rooted long ago with whatever root for AT&T app was popular at the time.
Doesn't taking an OTA just make you lose root? Nothing else to worry about?
Click to expand...
Click to collapse
I just received my G3 for AT&T yesterday. It had 4.4.2 firmware on it. I rooted and installed titanium backup and froze all of the AT&T bloatware. Got notification last night that I had a system update available so I went ahead and let it update thinking it would be 4.4.4 but I was wrong. End result, I wound up with a perfectly functional Lollipop with all bloatware removed, but did lose root in the process. I can live with that until someone figures root for lollipop out I think.
hitekredneck said:
I just received my G3 for AT&T yesterday. It had 4.4.2 firmware on it. I rooted and installed titanium backup and froze all of the AT&T bloatware. Got notification last night that I had a system update available so I went ahead and let it update thinking it would be 4.4.4 but I was wrong. End result, I wound up with a perfectly functional Lollipop with all bloatware removed, but did lose root in the process. I can live with that until someone figures root for lollipop out I think.
Click to expand...
Click to collapse
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update. That's just fine because i have to have root so I was planning to wait anyway...
p0k3y said:
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update.
Click to expand...
Click to collapse
+1
p0k3y said:
So it installed on your rooted G3? It wouldn't on mine - kept saying rooted device detected or something like that and then refuse to update. That's just fine because i have to have root so I was planning to wait anyway...
Click to expand...
Click to collapse
Yes, it installed with no problems at all. And I must say that I am loving it. So glad that I froze all of those at&t apps before I lost root. I am looking forward to root for lollipop so that I can freeze a few more. I must say that this is the best stock android rom that I have ever had the pleasure of using. I will probably stick with it for quite some time because of the speed and excellent battery life.
Lolipop upgrade
Hi iam very new on this forum . I got LGg3 AT&t version D85010f and i cannot upgrade to LOLIPOP always i have com that i have latest soft and need to wait 48h to next check ......plz help me
hitekredneck said:
Yes, it installed with no problems at all. And I must say that I am loving it. So glad that I froze all of those at&t apps before I lost root. I am looking forward to root for lollipop so that I can freeze a few more. I must say that this is the best stock android rom that I have ever had the pleasure of using. I will probably stick with it for quite some time because of the speed and excellent battery life.
Click to expand...
Click to collapse
I call bull****. Lolipop OTA will NOT install on a rooted device. Humor me, what root method did you use?
Vess69 said:
I call bull****. Lolipop OTA will NOT install on a rooted device. Humor me, what root method did you use?
Click to expand...
Click to collapse
Call Bull**** all you want, I don't lie. To be honest, I can't even remember what method I used to root when on KitKat. Then I used TiBu to freeze a bunch of apps that I didn't want or need. Shortly thereafter the update hit me so I went ahead and let it do its thing. As stated, I did lose root afterwards but the apps I had frozen with TiBu remained frozen and everything still worked as it should. I waited patiently for a few weeks until the one click root script became available and used it to root lollipop, then installed TWRP and flashed Cloudy G3 stock ROM which is where I am happily at at this moment.
It could possibly have successfully updated due to the fact that I had not installed a custom recovery, that's the only thing I can think of that would have allowed it to happen on mine, yet not on others that were rooted.
EDIT: After reading back through this thread it jogged my memory. I used the Stump Root method to root while on KitKat.
You'd be the first person reported to be able to do this.
It would be a boon to the AT&T G3 community if you could remember the precise details of how you pulled this off as it would save loads of time and hassle for everyone else who has to restore to KK (which means a full wipe), then take the OTA to L, then root there.
Thanks in advance.
*edit
I think you're L is version 20f, not the latest 21l, based on the date of your posts above.
Further, I'd suppose that what may have happened to you, is that the deivce had already downloaded the L update (from 10f to 20f) before you pulled off the root on KitKat. Then you simply acknowledged the install, which perhaps KK would allow to continue through.
Reports are the L will not allow this. So, going forward, someone rooted on L would not be allowed to complete the install even if the package is already downloaded on the device.
Still, it is, interesting.
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
spook2022 said:
I have a rooted, bootloader unlocked Pixel from Google Play. I am currently on 7.1 (NDE63V) November 5th security patch. I have stock recovery and would like to keep it that way if possible.
Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader? I used adb and boot-to-root for my current root method if it matters.
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
quangtran1 said:
You will lose root, but you can re-root easily enough. Bootloader doesn't relock on its own. Plus, you have the Google Store version, so it's easy to unlock BL anyway. To me, the cleanest and easiest method is to use the flash-all method, with the -w switch removed. Download the 7.1.1 image from the Google developers site and go at it. You can search for 'flash-all google pixel' here or on the web in general to get directions. It's easy as pie.
Click to expand...
Click to collapse
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
lightmastertech said:
I've got an unlocked Verizon Pixel running the non Verizon stock ROM (I know the bootloader won't relock itself with the non-Verizon ROM, right?). what if you are using a computer that can't use the ./flash-all.sh script? My only 2 computers are a Chromebook (1GB RAM) and a Raspberry Pi 3 (again, 1GB RAM). The flash-all script always gives an error saying it can't allocate enough memory, and with my old Nexus 6P, before I started using Custom ROMs, I'd just extract the image zip and manually flash the .img files inside it. With the Pixel however, there are a lot of img files (aboot.img, apdp.img, etc) and I'm not sure if I should try flashing these or not. I've read a couple less than reliable guides out there that basically said to just flash the same .img files as the Nexus 6P used, but I feel that those other ones are probably their for a reason and might need to be flashed too.
Also, should I flash both _a and _b partitions when updating, or just whichever is active? Seems that there is an _a and _b for almost every single partition on it.
Click to expand...
Click to collapse
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
quangtran1 said:
I have a ChromeBook but I've never used it to fastboot my phones. Sorry but I'll refrain from giving instructions on something with which I'm not familiar. I can say that the bootloader won't relock by itself. And the boot.img image should be all you need. Those points are universal. Also, you can just flash the 7.1.1 OTA, which is only 260mb.
Click to expand...
Click to collapse
If it rooted, and has modified system, doesn't the OTA update method fail?
And I actually use the Raspberry Pi for fastboot. Easier than trying to get my Chromebook's chroot to talk to talk to my phone's bootloader.
Hi
Whats about Flashfire? Can i download the Factory Image, deselect Boot and Recovery in Flashfire and flash it?
After this, can i flash the the SuperSU.zip with TWRP?
spook2022 said:
<snip>
Many thanks in advance for any assistance. If a thread with the requested info already exists, please feel free to just post a link to it.
Click to expand...
Click to collapse
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
https://www.google.com/search?q=root+on+unlocked+pixel+7.1.1&ie=utf-8&oe=utf-8
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
bobby janow said:
Have you any idea how many threads there are regarding this? How many duplicate posts and the same question about 2 dozen times all in separate threads? And now we have another? Even if you can't search XDA for some unknown reason, here you go.
Search terms from your OP ... root. on unlocked pixel 7.1.1
Can we please put an end to this question already?
Click to expand...
Click to collapse
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
spook2022 said:
I went back and read my post again just to make sure I wasn't crazy, and sure enough I couldn't find where I asked how to root 7.1.1...
I did however ask "Can someone please provide step-by-step instructions on how to update to 7.1.1 without losing root or the unlocked bootloader?" So, posting a Google search on how to root 7.1.1 isn't exactly the help I was after. Regardless of your disgruntled, condescending reply to the whole matter, I did manage to achieve the end result I was originally after.
Click to expand...
Click to collapse
As far as I know you can not update without losing root.. You can however update without losing data and reroot just like you did the first time.
@spook2022 It's just so frustrating to see the same question over and over. It wasn't that condescending, but yes, it was disgruntled. I just like to search for these things myself because I learn a lot along the way. Might take me an hour or so for the answer but then I learned an hours worth of stuff. I do agree though that there should be a sticky like the Heisenberg thread in the n5x forum that gives step by step for everything. One thing I will say that perhaps a few people don't know is that the Pixel and the XL are basically the same regarding root, unlocking and updating. So if you don't find the answers here you might want to head over to that forum. There seems to be a dearth of information here.
Someone suggested that the forums be combined with separate sections for things specific to each device like battery life and display as well as Verizon vs Google brand differences. I originally thought not but I'm changing my mind. Nonetheless, take the frustration from whence it came. I'm sorry I insulted you, that was not my intention. If you found a link to your solution perhaps you can post it for others. There is bound to be a similar question within a day. (oh oh there I go again..)
edit: This is what I was talking about regarding the Pixel vs the XL forums. Anything by Chainfire regarding root is a must read if you are rooted and even if you are not as I am. http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
<snip>
Click to expand...
Click to collapse
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Konfuzion said:
Download the 7.1.1 NMF260 image from Google.
Extract the zip file into the adb folder on the PC.
Edit the flash-all.bat file to remove the -w switch so user data won't be deleted. You'll find this -w switch easily enough.
Put your Pixel into fastboot mode, using either power+volume down or via adb command.
Plug phone to PC if not already done so. Execute the flash-all batch file.
When that's done, you have 7.1.1 on your phone, along with new radio and new kernel. (actually, I'm not sure if Google even put out a new kernel.)
Then you can go back to re-root with whatever method you used previously.
Click to expand...
Click to collapse
Thank you so much.
bobby janow said:
...I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
bobby janow said:
Why not the OTA coming from 7.1? Stock recovery according to the OP. Why go thru all the hassle unless you want a dirty flash? I know you say reroot after the install. I haven't been rooted in a few months now but I always used to unroot first for some reason before flashing a new image whether it be full image as you describe or an OTA. I'm sure it's not needed at this point, I was always leery of a bootloop. But with an unlocked bl it probably wouldn't matter since you could always recover if needed.
Click to expand...
Click to collapse
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
kyle4269 said:
He's on 7.1.0...63V..he can't apply the latest ota to 63V..he would have to apply each ota in order of their release.
Click to expand...
Click to collapse
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
---------- Post added at 03:50 PM ---------- Previous post was at 03:22 PM ----------
lightmastertech said:
That right there is why I always unlock my bootloader's and hack Verizon's phones to have unlocked bootloaders. Always great to have the assurance that you can easily fix it if something ever breaks.
Sorry if that's a little off topic.
Click to expand...
Click to collapse
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
bobby janow said:
I don't believe that to be correct. I think the 7.1.1 is cumulative. I'll double check though and edit later.
edit: You can go directly to the latest without incremental OTA flashes. Just sideload the OTA from recovery. Easy, peasy.
.
Click to expand...
Click to collapse
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
bobby janow said:
I always, always unlocked first thing I did. I even unlocked the unlockable S4 before the VZW firmware update. But lately I've been running locked. I have a banking app that will not run without passing SafetyNet. I know there are a couple of kernels that will bypass that check but I believe they will close that too eventually. The only thing I miss at this point is what you describe above. But the Pixel even from vzw, which I now have with the O update and therefore totally locked for now, is not full of bloat and runs rather well. So although I do root around these threads (no pun intended) it's merely for entertainment now and general knowledge.
Click to expand...
Click to collapse
Luckily I'm with USAA and they are too slow with adopting new technology, just got chip debit cards 2 months ago, and they'd till don't have Android Pay, lol. If they did start using SafetyNet, I'd use the kernel patch in a heartbeat. It'll be a long time before Google fixes that since there's still a lot of devices that can't use verified boot, and Google doesn't want to become the new Apple, abandoning old device just to suit them.
Wife got the Verizon version of the Pixel as an early Xmas present from my parents, and I wouldn't let the Verizon sales person activate it for fear of getting 7.1.1 before I could unlock bootloader. Wouldn't let wife turn it on for a couple hours till I had the bootloader unlocked and had flashed Google's version of Android to keep Verizon from screwing with it. Viper4Android and all the awesome rooted featured are too good to give up. She'll be really happy when Xposed or custom ROMs start coming out for it cuz even the little features are great, like holding power button with screen off to turn on flashlight. (She's been stuck with locked phones for a while while I've had my Nexus 6P and is glad to finally get a rootable phone).
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
Yep, that's about it. Personally I'd reboot right after the OTA flash then go back to bl and do the root process. Probably not needed though.
Sent from my Pixel using XDA-Developers mobile app
kyle4269 said:
That makes it so much easier then.. Download the latest ota zip from https://developers.google.com/android/ota then you need to flash the 63V boot. Reboot to recovery. Follow the directions on the Google ota site to sideload the ota. Reboot back to Bootloader and flash the twrp boot image to boot.. Reboot to recovery. Install the supersu zip and reboot.. All rooted and to the latest build.
Click to expand...
Click to collapse
How is that better or different than flashing the full image by using fastboot to flash bootloader and radio (if updated), then using
Code:
fastboot update <image>.zip
and leave off the -w to keep it from wiping.
Also, correct me if I'm wrong, but doesn't OTA updates fail if you've modified the system partition, like installing Viper4Android or other mods? I know that flashing the whole system image works no matter what which is why I use that method.