Have the VZW G2 rooted on the previous OTA update, now starting to see the nag screen to update again.
Last time, I reverted to stock and had to set up everything again from scratch. I needed root so did that but now at the same point again.
Is there an easier way to update, without having to wipe everything and start over again?
TIA
I was rooted and just installed the update. Went through fine and kept root. All my had to do was install/update xposed framework and reboot to get my modules working again. Aside from xposed I had no modified system files and stock recovery. I had not uninstalled any pre-installed apps, just have a few frozen with titanium.
How did you install the update? I tried the OTA path and it gave some hex error after the reboot
wujuyamakin said:
How did you install the update? I tried the OTA path and it gave some hex error after the reboot
Click to expand...
Click to collapse
If you find a solution would you kind enough to share? Ive been delaying my install and when i finally decided to do it, it errors.
wujuyamakin said:
Have the VZW G2 rooted on the previous OTA update, now starting to see the nag screen to update again.
Last time, I reverted to stock and had to set up everything again from scratch. I needed root so did that but now at the same point again.
Is there an easier way to update, without having to wipe everything and start over again?
TIA
Click to expand...
Click to collapse
Other than root, are you stock? If so, should be able to take ota with non issue. If you modded wifi hotspot, need to change it back for ota. Did you also install custom recovery?
wujuyamakin said:
How did you install the update? I tried the OTA path and it gave some hex error after the reboot
Click to expand...
Click to collapse
I didn't have any errors but I have no system files modded.
Thanks mhirsh, you nailed it. I had to restore the stock wifi hotspot app, do OTA update, then do the steps for wifi hotspot again.
It's actually the only root feature I've used for quite a while now. The root uninstallers I've tried have all failed to remove bloatware. I'll be looking at other root benefits to get more use out of it.
And to think I spent days restoring my phone from scratch last update ... lol.
wujuyamakin said:
Thanks mhirsh, you nailed it. I had to restore the stock wifi hotspot app, do OTA update, then do the steps for wifi hotspot again.
It's actually the only root feature I've used for quite a while now. The root uninstallers I've tried have all failed to remove bloatware. I'll be looking at other root benefits to get more use out of it.
And to think I spent days restoring my phone from scratch last update ... lol.
Click to expand...
Click to collapse
I tired this with no success. So i didnt delete my stock wifi hotspots (apk and odex) just renamed them. I removed my modded one and switched back to original names, rebooted, downloaded ota and it errored when it tried to install. Am i missing a step? Thanks in advance
lg g2 Verizon ota update with twrp
I have tried to do the ota Verizon update and get stuck in twrp . It won't reboot after that. I found the commands to get it to reboot on this site but it won't do the update. I'm new to all of this and still learning . please help me figure this out. Thanks
wrayzor71 said:
I have tried to do the ota Verizon update and get stuck in twrp . It won't reboot after that. I found the commands to get it to reboot on this site but it won't do the update. I'm new to all of this and still learning . please help me figure this out. Thanks
Click to expand...
Click to collapse
I couldn't get the OTA update to work until I went back to stock and unrooted. I was rooted with stock except I had performed the audio mod and the tethering mod which modified system files. Once I unrooted and factory reset to stock everything updated fine. haven't rooted again yet kind of waiting for stock lollipop OTA update to show up soon.
wrayzor71 said:
I have tried to do the ota Verizon update and get stuck in twrp . It won't reboot after that. I found the commands to get it to reboot on this site but it won't do the update. I'm new to all of this and still learning . please help me figure this out. Thanks
Click to expand...
Click to collapse
TheJuicer said:
I couldn't get the OTA update to work until I went back to stock and unrooted. I was rooted with stock except I had performed the audio mod and the tethering mod which modified system files. Once I unrooted and factory reset to stock everything updated fine. haven't rooted again yet kind of waiting for stock lollipop OTA update to show up soon.
Click to expand...
Click to collapse
You should never attempt OTA unless you are stock (having only root will be ok).
Yeah i had forgotten i had performed those mods after i rooted. Initially i thought i was just stock and rooted. Thankfully pretty easy to go back to stock.
Related
I rooted my Nexus One with the 1-click androot and today I've received the 2.2.1 update (FRG83) OTA. I don't want to install it because it'll unroot, but the notification is really persistent and irritating, and I'm afraid I'm going to accidentally hit the install button.
How can I make it go away?
Install a custom recovery, make sure it works, try to flash the rom, it will fail because it needs to stock recovery to install, delete the update from /cache/.
That will at least leave you with a little time before it tries to notify you again. Best thing to do is load a rooted custom rom with a build.prop mod to make it think it's a version better/same so it won't try and update you.
I thought I had to have an unlocked bootloader in order to install a custom recovery or flash custom roms. Is this not the case?
I also have rooted with the one click but have clockworkmod recovery with stock rom. I just received the update ota and I am confused as to what would happen if I attempt to install it. Will it just abort or will it brick the device? Would just a battery pull and reboot be all thats necessary? Has any new roots come out for this update? I really dont want to lose my root. Any and all help is appreciated.
tenbeau said:
I also have rooted with the one click but have clockworkmod recovery with stock rom. I just received the update ota and I am confused as to what would happen if I attempt to install it. Will it just abort or will it brick the device? Would just a battery pull and reboot be all thats necessary? Has any new roots come out for this update? I really dont want to lose my root. Any and all help is appreciated.
Click to expand...
Click to collapse
I was in the same boat as you yesterday. I didn't think of the recovery so I hit update because I was tired of the notification. The phone applied the update successfully and I don't have root anymore. I have no idea how that impacts the recovery since ClockworkMod says the ClockworkMod recovery is installed.
Would like to know as well. Do not want to lose one-click root and would love to get rid of that stupid notification.
check out post #102 here:
http://forum.xda-developers.com/showthread.php?t=791124&page=11
this user says he has gotten it to stop via this method. I cannot verify yet as I have not received the OTA
For me that seems to have stopped the OTA nagg screen.
Using quickboot to reboot then clearing the notification, I have not got another OTA nagg screen. I like the 1 click root, turn on when needed off when not.
tinymiata said:
For me that seems to have stopped the OTA nagg screen.
Using quickboot to reboot then clearing the notification, I have not got another OTA nagg screen. I like the 1 click root, turn on when needed off when not.
Click to expand...
Click to collapse
I'm willing to try anything after 100+ "install later" replies Quickboot here I come
Thank you! I don't know why Quick Boot worked, but it seems that it has. It's now been a couple of hours without a notification message when they were coming back every few minutes. Thanks!
wouldn't it be cool if we got around Google's grand plan to force us to update by driving us crazy!?
Accidentally rooted my new RMA phone before I installed the 5.0 update that needed to be installed. How do I temp unroot so that I can install the update. I tried disabling Superuser to no avail. Every time I try installing the OTA I get an error saying system must be remounted or something.
mdandashly said:
Accidentally rooted my new RMA phone before I installed the 5.0 update that needed to be installed. How do I temp unroot so that I can install the update. I tried disabling Superuser to no avail. Every time I try installing the OTA I get an error saying system must be remounted or something.
Click to expand...
Click to collapse
no such thing as temp unroot.
1. you can flash the factory img, which is already the latest, then reroot.
2. you can flash any of the aosp roms, which are all the latest, in the android and original development sections, and not worry about an ota, ever.
simms22 said:
no such thing as temp unroot.
1. you can flash the factory img, which is already the latest, then reroot.
2. you can flash any of the aosp roms, which are all the latest, in the android and original development sections, and not worry about an ota, ever.
Click to expand...
Click to collapse
Gotcha, I seem to remember being able to temporarily unroot back in the day.
You have to flash the stock factory image to unroot. If you do, you might as well just flash the stock factory image with the LRX21O update included, at https://developers.google.com/android/nexus/images
Edit: Sorry I just realized someone else replied while i was typing.
mdandashly said:
Gotcha, I seem to remember being able to temporarily unroot back in the day.
Click to expand...
Click to collapse
there were methods in the past, and there might be methods in the future. it just at this point with lollipop, there isnt any methods yet.
simms22 said:
there were methods in the past, and there might be methods in the future. it just at this point with lollipop, there isnt any methods yet.
Click to expand...
Click to collapse
Got it. That must have been my confusion. Flashed the factory image.
You're right
Right within the SuperSU app, if you go into settings, and scroll all the way down you can go into the option for "Full Unroot." You can also use Wugfresh toolkit to unroot, this will be "permanent" but as soon as you flash 5.01 you can reroot using either adb/fastboot (fastboot boot root.img) or using chainfire auto root or wugfresh.
I used fastboot to flash system then the OTA worked few days later rerooted.
The full unroot method via SuperSU app did not allow the OTA to take.
Hey all,
Thought I'd let those of you that have an AT&T Tab S 8.4 know that Lollipop has been released today. Happened to be on the AT&T Software update page here: http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB425812&cv=820 and noticed it listed the update.
Manually checked for updates on my tablet, it's downloading now. My 8.4 on AT&T is totally stock.
Downloading now... 1.1GB
manually checking shows nothing for me
Mine wasn't too laggy after the upgrade. But as I know from places like XDA usually a very good idea to do a full system wipe which I did.
What I am most thankful for is there is now an option to remove that Samsung screen that has those Samsung widgets that go full page. Can't recall what it is called. Yeah I know could have got rid of that using a 3rd party launcher in 4.4 but so happy Samsung put option there to disable it finally. To get rid of it, long press blank space like you were going to add a widget, then click Home Screen Settings, then uncheck "Content Home Screen".
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
Not sure it will work.
Maybe try to adapt the method given by ashyx here: http://forum.xda-developers.com/galaxy-tab-s/general/guide-how-to-root-tripping-knox-kitkat-t3129484
It worked successfully for me on the T800
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
I'm rooted with Kingroot and it's currently downloading the update. If you load Xposed Framework and Wanam Xposed, under Security hacks there's a setting for Fake System Status that allows you to set it to Original.
I'll follow up when the download finishes.
Update: The download completed but the install failed and then got stuck in a boot loop. Ended up having to go to the Samsung place at Best Buy to have them re-flash KitKat. Now the tab is telling me I have to wait 24 hours to check for updates. I'm sure everything will be good now that I'm back on a factory image.
fleabeard said:
I'm rooted with Kingroot and it's currently downloading the update. If you load Xposed Framework and Wanam Xposed, under Security hacks there's a setting for Fake System Status that allows you to set it to Original.
I'll follow up when the download finishes.
Update: The download completed but the install failed and then got stuck in a boot loop. Ended up having to go to the Samsung place at Best Buy to have them re-flash KitKat. Now the tab is telling me I have to wait 24 hours to check for updates. I'm sure everything will be good now that I'm back on a factory image.
Click to expand...
Click to collapse
Turn off automatic date and time and manually advance it by a day, and try again.
When they re-flashed KitKat did it wipe your tablet? The OTA failed me when rooted, failed me after un-installing adaway and un-rooting and removing KingUser. I cannot do a firmware upgrade via Kies 3 as it's not available. I cannot do an emergency firmware recover via Kies 3 as it's not soft bricked. I can't find either the KitKat or the Lollipop firmwares online anywhere... Currently I have a tablet, works fine, I did a factory reset (in the back of my mind knew this wouldn't work) that has a custom status and won't take the OTA.
If anyone knows where I can find the KitKat firmware, or the OTA, please let me know.
Or maybe someone could grab the OTA off their tablet after downloading prior to updating and share the wealth with the community???
Has any kingroot user tried triangle away, unroot via kinguser, and take the OTA?
Also just realized that if I can fail the OTA, I can obviously download it... Where do I grab it from if I wanted to flash it with odin or sideload?
Russ77 said:
Has anyone who rooted with kingroot updated? I'm assuming it'll kill root, just curious if I need to unroot prior, or if the update will still install. I'll post the answer tomorrow after I update.
I've had some Samsung devices which will update while rooted, and some that will not.
Click to expand...
Click to collapse
Russ77 said:
Turn off automatic date and time and manually advance it by a day, and try again.
When they re-flashed KitKat did it wipe your tablet? The OTA failed me when rooted, failed me after un-installing adaway and un-rooting and removing KingUser. I cannot do a firmware upgrade via Kies 3 as it's not available. I cannot do an emergency firmware recover via Kies 3 as it's not soft bricked. I can't find either the KitKat or the Lollipop firmwares online anywhere... Currently I have a tablet, works fine, I did a factory reset (in the back of my mind knew this wouldn't work) that has a custom status and won't take the OTA.
If anyone knows where I can find the KitKat firmware, or the OTA, please let me know.
Or maybe someone could grab the OTA off their tablet after downloading prior to updating and share the wealth with the community???
Click to expand...
Click to collapse
OTA came down successfully while not rooted. The reflash at Best Buy didn't wipe it.
As far as I know, the factory images for the AT&T versions aren't available anywhere, or at least I've been unable to find them. They obviously exist because I'm pretty sure the guy at Best Buy used Kies to flash with an image that's available to him from Samsung.
I re-rooted last night in the attempt of using triangle away to clear customs status, then un-rooting. This was odd because device status still shows custom but download mode shows official and Knox is 0.
While I was briefly rooted again I downloaded the OTA in the hopes of copying it to my PC and updating via ADB Sideload... Couldn't find it. If anyone knows where Samsung puts these I'll grab it and post it to share.
im not rooted, performed a factory reset, and my device still doesn't see any updates. Can somebody provide a link to the ROM?
Same situation here - no root, no mods, no available update
Sent from my SM-G925V using XDA Premium HD app
Same Thing Here Also
bshaw100 said:
Same situation here - no root, no mods, no available update
Sent from my SM-G925V using XDA Premium HD app
Click to expand...
Click to collapse
I've got the same thing: no root, no mods, no update available! Darn!!!!
I've got the same thing: no root, no mods, no update available!
Russ77 said:
I re-rooted last night in the attempt of using triangle away to clear customs status, then un-rooting. This was odd because device status still shows custom but download mode shows official and Knox is 0.
While I was briefly rooted again I downloaded the OTA in the hopes of copying it to my PC and updating via ADB Sideload... Couldn't find it. If anyone knows where Samsung puts these I'll grab it and post it to share.
Click to expand...
Click to collapse
The OTA gets downloaded to /cache. If you are rooted you can see it. But the OTA is not a complete ROM, just a differential to the ROM you have.
Sent from my SM-T707V using XDA Premium HD app
still nothing
gshaw_nash said:
I've got the same thing: no root, no mods, no update available! Darn!!!!
Click to expand...
Click to collapse
gshaw1967 said:
I've got the same thing: no root, no mods, no update available!
Click to expand...
Click to collapse
I've reset several time and cannot download the update. I get "Connecting to DM Server" and then update interrupted. Has anyone gotten around this?
---------- Post added at 08:58 AM ---------- Previous post was at 08:11 AM ----------
gshaw1967 said:
I've reset several time and cannot download the update. I get "Connecting to DM Server" and then update interrupted. Has anyone gotten around this?
Click to expand...
Click to collapse
Turns out there is a imei problem with the tablet that is preventing the download. My imei number is paired with a IPhone 4. Anyway will take a few day to fix then the upgrade should work.
I get the same. I wiped my device hoping for a different outcome, and still no update.
I found this in the thread below.
It is an old tread but I'll comment anyway. SM-T807 is the 3G version while SM-T805 is the LTE version. Both Hardware (CPU/GPU) and comms modules are different. So 805 LTE (which has Lollipop) firmware won't work for 807 (no Lollipop is currently available nor Samsung plans to release soon).
Click to expand...
Click to collapse
http://forum.xda-developers.com/galaxy-tab-s/help/sm-t805-sm-t807a-t2961117
John.
After not being able to take the OTA after rooting, even after un rooting, not being able to find the OTA and sideload (not in /cache), and not able use Kies or Odin I finally took it to the Samsung kiosk at my bestbuy.
They reflashed 4.4.2, didn't wipe anything, and immediately downloaded and successfully installed the lollipop update after getting home and on WiFi.
Just don't mention that you rooted ;')
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?
I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.
Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?
If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.
Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img
You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.
I have a Droid Turbo that is currently on version 5.1 (23.21.44) and I just recently unfroze the system update notifications for my phone because of the news of MM. I am currently rooted and have an unlocked bootloader but I don't have TWRP installed and would rather not install it for now if I don't have to.
The system update that it is trying to push to my phone isn't MM, instead it is version 23.21.49.en.US. Is it safe to just take this update while being rooted and with an unlocked bootloader? I'm also not sure how many updates I'll have to make my way through before reaching the MM update, but if there are other updates, should it also be safe to go ahead with those as well? I know I could install TWRP and flash the MM ROM that way but I would prefer to do the updates officially if it is not risking a bricked phone.
Thanks for any advice.
EDIT: I forgot to finish the title of the thread...
AirJordanTS said:
I have a Droid Turbo that is currently on version 5.1 (23.21.44) and I just recently unfroze the system update notifications for my phone because of the news of MM. I am currently rooted and have an unlocked bootloader but I don't have TWRP installed and would rather not install it for now if I don't have to.
The system update that it is trying to push to my phone isn't MM, instead it is version 23.21.49.en.US. Is it safe to just take this update while being rooted and with an unlocked bootloader? I'm also not sure how many updates I'll have to make my way through before reaching the MM update, but if there are other updates, should it also be safe to go ahead with those as well? I know I could install TWRP and flash the MM ROM that way but I would prefer to do the updates officially if it is not risking a bricked phone.
Thanks for any advice.
EDIT: I forgot to finish the title of the thread...
Click to expand...
Click to collapse
It's safe, but it will be unsuccessful until you unroot your phone and undo any other system modifications that you've done (xposed, for example). There's a huge part of the update script that checks every single file in your system partition to make sure nothing has been modified.
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
AirJordanTS said:
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
Click to expand...
Click to collapse
You did that by modifying /system/build.prop. That change might be okay, but I would change it back if I were you just to be safe. The change is going to be overwritten anyway once the OTA is done.
AirJordanTS said:
Ok great, thanks.
The only other modification I can think that I've made is enabling mobile Hotspot through editing a setting somewhere. Do you know if that would be affected or would need changed back?
Click to expand...
Click to collapse
It's possible it may miss overlooking that. The worst that could happen was the update just doesn't take. It fails and nothing is changed. There is a pure MM official version that you can Flash in TWRP. It will update everything, radios and all, but will not relock the bootloader. I recommend you download Titanium Backup and backup all of your apps and their data to be restored after the update. A factory reset is recommended after the update. Also, don't forget to back up all of your photos, documents, music, etc. 24.81.5 is MM. Your update was a prep for MM.
Thanks for the advice guys.
I didn't realize it but I had TWRP installed so I decided to flash a stock ROM and proceed with the OTA updates from there. The problem currently is that I'm being locked out of my phone because of the Google "verify your account" page. I reset my account password on that page and now I'm not able to log in.