Hey guys,
I tried to update my rooted G5 via OTA firmware update, but when the device reboots (to install the update), I'm booting to TWRP automatically.
There was some setting you could set on the install of TWRP ("to make stock updates easier" or so). Do you know, what that setting was? Is there a way to install stock updates on a rooted device?
Thanks!
Twrp asks if it should put the system partition not writable. But I think you cannot install OTAs even then.
But... I had the same problem and you can just use lg up with the kdz file of the latest ROM version and select upgrade in the program. It will not delete your data but you will have to install twrp and root again.
But you can of course also do a factory reset while installing the new ROM and start from scratch.
Related
michpan said:
So, to recap, you don't need to relock the bootloader for OTA updates but you have to flash stock recovery first? And you'll lose root in the process?
Click to expand...
Click to collapse
The answer was "YES".
I wonder whether OTA updates will be possible if you have deleted system apps.
Has anyone tried this before updating to JB?
Stock ROM, stock recovery, rooted (by booting the phone into e.g. TWRP recovery without flashing it), system apps deleted -> OTA update possible?
According to these "negative effects of unlocked bootloader", every OTA update checks the MD5 checksum of every file that originally came with your device, so it should not be possible.
Can anyone confirm that no OTA updates will be possible if you have deleted system (or any preinstalled) apps?
Thanks.
mary-lou said:
The answer was "YES".
I wonder whether OTA updates will be possible if you have deleted system apps.
Has anyone tried this before updating to JB?
Stock ROM, stock recovery, rooted (by booting the phone into e.g. TWRP recovery without flashing it), system apps deleted -> OTA update possible?
According to these "negative effects of unlocked bootloader", every OTA update checks the MD5 checksum of every file that originally came with your device, so it should not be possible.
Can anyone confirm that no OTA updates will be possible if you have deleted system (or any preinstalled) apps?
Thanks.
Click to expand...
Click to collapse
Yes. If you have deleted any system app then OTA will not be possible so restore a nandroid backup to get all the files..
I updated to jb with unlocked bootloader and root.
Reported to move.
Ok. So, if I keep my original recovery and only boot into TWRP occassionally to make backups, if I keep the original ROM and only "move" a few system apps to a special folder on my SD, I will be informed when there is an OTA update available but I won't be able to install it due to the wrong MD5 checksum, right?
So, if I move the "deleted" system apps back, I should be able to install the OTA update, right?
After the update, I can "delete=move" them again.
As the bootloader remains open, there will be no factory reset, right?
Should be. Just make sure you flash stock recovery before doing the OTA.
Sent from my HTC Desire X using xda premium
So I rooted my MetroPCS Stylo, and installed TWRP.
I woke up to an OTA update this morning and looked it up, and it's a good one. Upgrades from 5.0.1 to 5.1.1 with a radio update and other goodies.
I went ahead with the update thinking TWRP would handle it and I would just need to root device again.
That didn't work of course.
I'd like help with applying this update please.
What I have:
Backup of original rooted stock system without much modification.
Backup of current rooted stock system/system data/user data.
Backup of stock recovery.
Copy of the OTA update.zip retrieved from within recovery (it's still residing within /cache )
I was thinking I could do a fresh backup of system and data images, then flash the stock recovery and go for update and re-root afterwards.
Questions:
How do I initiate recovery command for rebooting and applying recovery?
How can I avoid breaking anything?
How would you apply this update?
Thanks
Guys iam unrooted my one plus x for getting official ota updates , but after unrooting iam getting ota notification and click on install , but in process of update in recovry mode it says failed and reboot , pls pls help me how to solve this problem and get back to official opx device
1. Download OnePlusOxygen_14_OTA_008_all_201601221550.zip .
2. Just flash it.
3. You'll be on OxygenOS 2.2.0 without any other files to flash. Don't wipe data and cache to retain your apps and data.
The right answer is : you won't have Over The Air. You have to flash it manually as @StraightEdgeKid just said.
You should flash the next updates the same too.
After installing full 2.2.0 ROM, he'll be unrooted completely, and if he has stock recovery, he can install OTA's afterwards, unless he remains on stock.
Yeah but it always depends on the way he rooted the phone. The OneCmlickRoot solution have to be bannished on OPX!
Ofcourse not, if he flashes full 2.2.0 ROM, everything from system will be overwritten, leaving no place for previous stuff in system. /system will be cleaned completely.
Thanks for this. Downloaded the file, flashed through stock "recovery", and voila.
Flash the full ota and after that check you are on stock recovery or custom recovery(twrp) if its custom then flash stock recovery and you will be able to get otas
I was trying to update my phone using CM system update process and I realized that I had lost root access so I tried to root my phone agan using the latest available version of Stomp but when ran the app it reported that the software was not comparable with my phone. I have used stomp to root my G3 in the past without issue. I am using Twap 2.8.8 for my recovery. I tried to update to a newer version and that is how I food out that I had sometime in the last few month had lost root access. I then tried to go manual update and I Couldnt access the download folder in Twarp recovery, I guessing because I did not have root access. Then I think I made a big mistake by having twarp reset permissions, Thinking that might help. I rebooted the phone and now it just sits in the CM boot screen .
Please Help I am a relative noob and I am hoping that this can be fixed
"Stump" root only works on stock LG 10B. If you weren't using CM13's built-in Root capability (probably in the Developer's menu), such as if you were using SuperSU, you probably could've just flashed the latest SuperSU.zip from @Chainfire 's website.
Even on 10B, Stump reports it's not compatible but you have to choose the option to use the brute force method, which works on 10B but with a working custom recovery I wouldn't even try that on CyanogenMod.
Just wiping Cache and Dalvik/ART might solve things. If not, do those first again and dirty flash the latest CM13 ROM and SuperSU.zip if necessary, and anything else you normally flash like Xposed, then you should be fine.
If it still won't boot, you may have to flash the 10B TOT which will wipe everything including internal storage, and re-root with Stump, put TWRP on with TWRP Manager from the Play Store, and reflash CM13 and 35B Bootstack.
Hi, I saw about the quad rooter issue, and today I checked the ota update. (I never had an ota update because I always been rooted, s3, s5 and g5)
But now it purpose the 10d update. (450mo)
I'm 10c h850 rooted.
Should I make this update?
Will I lose root? (Rooted via twrp super su)
If I have to re install everything (apps, datas, root), maybe should I wait for 7 nougat don't you think?
Thanks.
trotirider said:
Hi, I saw about the quad rooter issue, and today I checked the ota update. (I never had an ota update because I always been rooted, s3, s5 and g5)
But now it purpose the 10d update. (450mo)
I'm 10c h850 rooted.
Should I make this update?
Will I lose root? (Rooted via twrp super su)
If I have to re install everything (apps, datas, root), maybe should I wait for 7 nougat don't you think?
Thanks.
Click to expand...
Click to collapse
It won't install the update anyway with twrp installed. It'll just fail and reboot. Wait until your ROM devs rebase your ROM on the new base.
Thanks, it was stock rom. But yeah I don't think it's worth if I make a fresh install with android 7.
As you said I'm affraid about the bootloop issue.
trotirider said:
Thanks, it was stock rom. But yeah I don't think it's worth if I make a fresh install with android 7.
As you said I'm affraid about the bootloop issue.
Click to expand...
Click to collapse
Not bootloop, just because you have custom recovery installed the stock update process will not complete even on stock Rom, you'd need to wait for a flashable version of the update or you'd have to flash stock recovery back to your device first.
I just used LGUP without any issues. Pretty painless.
Then flashed TWRP again, and flashed my ROM of choice.
The only tricky part was quickly getting into TWRP after you flash TWRP. It reboots and if you're not quick enough, TWRP will be overridden by the stock recovery. Then you just need to repeat (flash TWRP again, get into TWRP and flash ROM).