I am on 4.1.6 and wanted to un-root my phone so I can get the OTA updates. My recovery is TWRP 3.1.1-x blu_spark v37. Can someone please link me to a thread that can help me out.
There is already a guide to unroot and revert oneplus 3t to stock by the_rooter. Go through.
https://forum.xda-developers.com/oneplus-3t/how-to/guide-return-youre-op3t-to-stock-lock-t3569383
You could use Osm0sis unSU from here https://forum.xda-developers.com/showthread.php?t=2239421&p=40409356
navpal93 said:
I am on 4.1.6 and wanted to un-root my phone so I can get the OTA updates. My recovery is TWRP 3.1.1-x blu_spark v37. Can someone please link me to a thread that can help me out.
Click to expand...
Click to collapse
If you like being rooted (and want to stay that way) you don't need to jump through the hoops of returning to stock, or hiding root.
You can simply download the "full" update zip (not the OTA patch, you're looking for the zip that is >1 GB). Then flash in TWRP. Immediately root by your method of choice (SuperSU or Magisk) before rebooting. Which will not only give you root, but doing this before rebooting (after flashing the update) will prevent TWRP from being overwritten with stock recovery.
Super easy. You can do this any time there is an update. And probably get it here on XDA before you would ever get the update notification. The only added hitch is that you will need to update to a Oreo-compatible version TWRP (if the intent is to update to Oreo). Either TWRP 3.1.1-x blu_spark v8.54 (or later) or "official" TWRP 3.2. You are currently on blu_spark, which anyway is more device specific, and recommended.
You can download the full update OOS 5.0, and more details on how to flash, from here: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Even if rooted, you should still get the update notifications. It will automatically download the full update (instead of the patch) since you are rooted/TWRP. The only difference, is if you do it that way, it will reboot right after installing the update. You won't have a chance to root, and therefore TWRP will be overwritten with stock recovery. Not a big deal, as you can just fastboot flash TWRP again. But downloading the update and flashing "manually" as posted up above, just saves some steps (in cases other than going to Oreo - since you need to update TWRP in this case).
---------- Post added at 11:12 AM ---------- Previous post was at 11:01 AM ----------
ersandeepkr said:
There is already a guide to unroot and revert oneplus 3t to stock by the_rooter. Go through.
https://forum.xda-developers.com/oneplus-3t/how-to/guide-return-youre-op3t-to-stock-lock-t3569383
Click to expand...
Click to collapse
Only need to return to "full stock" in order to lock the bootloader. And the only reason to lock the bootloader, is if the user is selling the device, or just doesn't want an unlocked bootloader (or TWRP, root, etc.) anymore.
As I outlined above,: root, custom recovery, and unlocked bootloader are all okay (updates will still install) with some minor caveats.
redpoint73 said:
If you like being rooted (and want to stay that way) you don't need to jump through the hoops of returning to stock, or hiding root.
You can simply download the "full" update zip (not the OTA patch, you're looking for the zip that is >1 GB). Then flash in TWRP. Immediately root by your method of choice (SuperSU or Magisk) before rebooting. Which will not only give you root, but doing this before rebooting (after flashing the update) will prevent TWRP from being overwritten with stock recovery.
Super easy. You can do this any time there is an update. And probably get it here on XDA before you would ever get the update notification. The only added hitch is that you will need to update to a Oreo-compatible version TWRP (if the intent is to update to Oreo). Either TWRP 3.1.1-x blu_spark v8.54 (or later) or "official" TWRP 3.2. You are currently on blu_spark, which anyway is more device specific, and recommended.
You can download the full update OOS 5.0, and more details on how to flash, from here: https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Even if rooted, you should still get the update notifications. It will automatically download the full update (instead of the patch) since you are rooted/TWRP. The only difference, is if you do it that way, it will reboot right after installing the update. You won't have a chance to root, and therefore TWRP will be overwritten with stock recovery. Not a big deal, as you can just fastboot flash TWRP again. But downloading the update and flashing "manually" as posted up above, just saves some steps (in cases other than going to Oreo - since you need to update TWRP in this case).
---------- Post added at 11:12 AM ---------- Previous post was at 11:01 AM ----------
Only need to return to "full stock" in order to lock the bootloader. And the only reason to lock the bootloader, is if the user is selling the device, or just doesn't want an unlocked bootloader (or TWRP, root, etc.) anymore.
As I outlined above,: root, custom recovery, and unlocked bootloader are all okay (updates will still install) with some minor caveats.
Click to expand...
Click to collapse
is this still possible to go from 7.1.1 to 9.0? read somewere it is not possible? other methods:
[GUIDE][MODDED FIRMWARE][9.0.6][OP3/T]The least annoying 9.0.x firmware
but i am on 7.1.1, will this work with the above mentioned guide?
or should i unroot my phone again? but what oxygen version do i flash? 4.0 as mentioned above? will my data and apps be gone? i don't want to revert the phone completely to stock a it was new. Just want the lastest official oxygen version because my android auto won't work anymore.
can't find this on the forum
thanks!
Related
I bought the T-Mobile version (on AT&T) and received it yesterday, based on the numerous threads that seemed to be the best option for me. I've been unlocking, rooting, and flashing the previous 3 Android phones and have yet to brick or "damage" any of them (knock on wood). Not too worried about voiding warranty since unfortunately they sold out of DE early on.
Originally, all I wanted to do was root. Though, I should have read more carefully before accepting the 4.4 OTA, chalk it up to "new phone" excitement. Seems like you needed to remain on 4.2.2. to root and THEN updating to 4.4. Decided to go ahead and unlock the bootloader and rooting the "traditional" method. Worked fine. Unlocked bootloader, flashed TWRP, and installed SuperSU. Profit. Thanks to the all the helpful people here.
I plan to stay on stock with the Moto X...for the first time ever with an Android device. Will I be able to accept future OTA updates? From what I've interpreted, I can't because I no longer have stock recovery, is that correct? If that is the case, what would I have to do to "keep up" with future official OTA updates?
Despite unlocking, rooting, and flashing previous phones - I've realized that this is far more complicated than I thought for a layman like myself.
It is still possible, and should remain so, that you can flash OTAs using CWM or TWRP recovery while rooted if you have not made any changes to system apps. I just updated my rooted, stock rom & kernel N7 with TWRP recovery to Kitkat 4.2.2. After updating successfully, I just restored TWRP with a fastboot flash of the twrp recovery image and used TWRP to flash SuperSU 1.8. to restore root. It all worked perfectly, but I had to unfreeze a couple of apps and uninstall the AOSP root browser app. After updating, I reinstalled the AOSP browser and all is well.
Groid said:
It is still possible, and should remain so, that you can flash OTAs using CWM or TWRP recovery while rooted if you have not made any changes to system apps. I just updated my rooted, stock rom & kernel N7 with TWRP recovery to Kitkat 4.2.2. After updating successfully, I just restored TWRP with a fastboot flash of the twrp recovery image and used TWRP to flash SuperSU 1.8. to restore root. It all worked perfectly, but I had to unfreeze a couple of apps and uninstall the AOSP root browser app. After updating, I reinstalled the AOSP browser and all is well.
Click to expand...
Click to collapse
someone will have to provide the OTA zip file for us to flash throu twrp right? we wont be able to install the OTA right on the phone like normally.
claudiuslu2011 said:
someone will have to provide the OTA zip file for us to flash throu twrp right? we wont be able to install the OTA right on the phone like normally.
Click to expand...
Click to collapse
You can't flash the ota with twrp recovery, it will bootloop, other have tried it and always goes south, unlike the previous person who had a nexus 7 , the moto x is a different beast. We do have access to the firmware which you can flash with rsdlite but it wipes the phone, wipes recovery and puts the phone back to original specs
Sent on my Moto X
I rooted my HTC One a while ago.
Recently, I got the request from my phone to preform a system update. I wasn't used to my phone being rooted and forgot it was rooted and preformed the update. When the update tried to install, it opened up my recovery (ClockworkMod Recovery) and rebooted my phone (I guess this is the normal reaction).
I really like my phone to be up-to-date. How can I get the official 4.4.2. update on my phone?
(If necessary, I wouldn't mind losing my root access in the process as long as I can root back after the update. However, I would prefer my Bootloader to remain unlocked so I won't have to format again.)
I am very interested in Android, but i know very little about things like this so please, if you know how, explain it to me step by step without leaving out little details.
Thanks in advance.
JellyFox said:
I rooted my HTC One a while ago.
Recently, I got the request from my phone to preform a system update. I wasn't used to my phone being rooted and forgot it was rooted and preformed the update. When the update tried to install, it opened up my recovery (ClockworkMod Recovery) and rebooted my phone (I guess this is the normal reaction).
I really like my phone to be up-to-date. How can I get the official 4.4.2. update on my phone?
(If necessary, I wouldn't mind losing my root access in the process as long as I can root back after the update. However, I would prefer my Bootloader to remain unlocked so I won't have to format again.)
I am very interested in Android, but i know very little about things like this so please, if you know how, explain it to me step by step without leaving out little details.
Thanks in advance.
Click to expand...
Click to collapse
Many things are required to flash ota updates. First one is the stock recovery, you can't install an ota update with a custom recovery like cwm or twrp. So flash back the stock recovery that match the version you have on your phone. If you have modified or deleted files in /system, you'll have to revert those changes. The updater script of the ota update MD5 cheksum these files. If only 1 file doesn't match the expected value, the installation will fail. Same thing apply to preloaded app that get wiped when you unlock bootloader (calculator, flashlight etc...)
So first, flash your stock recovery and try to install the ota. If it doesn't work, post the output of ''fastboot getvar all'' (except imei/sn) and we will check what you can do to updates your phone
alray said:
Many things are required to flash ota updates. First one is the stock recovery, you can't install an ota update with a custom recovery like cwm or twrp. So flash back the stock recovery that match the version you have on your phone. If you have modified or deleted files in /system, you'll have to revert those changes. The updater script of the ota update MD5 cheksum these files. If only 1 file doesn't match the expected value, the installation will fail. Same thing apply to preloaded app that get wiped when you unlock bootloader (calculator, flashlight etc...)
So first, flash your stock recovery and try to install the ota. If it doesn't work, post the output of ''fastboot getvar all'' (except imei/sn) and we will check what you can do to updates your phone
Click to expand...
Click to collapse
Thank you for the reply.
I wasn't able to try this since my phone broke down and i had to return it to the store.
(The person working there knew what he was talking about and was familiar with Bootloader.)
I will use your info if i ever need it again.
So, i have a motox (xt1058) with stock rom and twrp recovery. If i receive the lolipop via OTA, can i install it? or do i have to flash the original firmware?
Thanks in advance
You will have to flash stock recovery. Uninstall any xposed modules and unfreeze/restore any system apps.
PedroAlba said:
So, i have a motox (xt1058) with stock rom and twrp recovery. If i receive the lolipop via OTA, can i install it? or do i have to flash the original firmware?
Thanks in advance
Click to expand...
Click to collapse
This is asked every time an new OTA comes out, and we get many threads started covering it.
To date...
For the Motorola X 2013, the OTA's are incremental updates. You must be on a specific previous ROM, and "step up." To put it another way... to take the 4.4.2 OTA, your phone needs to be on 4.4. To take the 4.4 OTA, your phone needs to be on the 4.2.2 w/camera fix version. To take the 4.2.2 w/camera fix OTA, your phone needs to be on the initial shipping ROM version.
None of the OTA's will install if you have TWRP recovery on your phone. Instead you get stuck in a bootloop. (mfastboot erase cache will get you out of the bootloop). You need to have stock recovery on your phone. NOTE: I don't recall what happens when using Philz or CWM as recovery.
Each OTA so far has included a "Pre-Install Verification Check", a manifest of files and their checksum/hashes which the update compares against your phone. If expected files are missing, or the wrong hash, the OTA will fail to install. - So any removed or modified "bloat", system files, etc. need to be in place. Any apps like Xposed which change /system need to be disabled/removed. In some cases Freezing apps using Titanium Backup cause the OTA to fail, and the apps need to be unfrozen. However, some have not had to unfreeze. Using the phone's app manager to disable an app (Settings -> Apps -> open app listing -> DISABLE) does not have to be undone.
If you have version mismatch between GPT.BIN or Motoboot.img and the ROM on your phone, taking an OTA WILL brick the phone. - Grab the FULL SBF for the Stock Moto ROM which matches the bootloader version on your phone, or a newer SBF (i.e. if you have the bootloader version that corresponds to 4.4.2, grab the 4.4.2 SBF or 4.4.4 SBF), and flash it via mfastboot. You may need some extra steps to flash GPT.BIN and Motoboot.img.
If you've used hacks to root/disable write protection because you have a locked bootloader, you may lose root, and wont be able to re-root until a new exploit is found. Those hacks might also get in the way of the OTA's pre-install validation checks.
If you have unlocked your bootloader via mfastboot oem unlock UNIQUECODE or Sunshine, the bootloader will not re-lock.
There have been some posts (twitter and G+) about how Lollipop poses new security features which are a challenge to rooting, even with an unlocked bootloader. Since I don't know the technical ins and outs, all I can say is.. Even with an unlocked bootloader, I wont jump on Lollipop as soon as its available, until I know if I can still root my X.
(I have a little bit more detail posted here -> http://mark.cdmaforums.com/MotoX-OTA.html)
lowvolt1 said:
You will have to flash stock recovery. Uninstall any xposed modules and unfreeze/restore any system apps.
Click to expand...
Click to collapse
For what it's worth, you don't need to uninstall the modules. Just use the Xposed Disabler zip in your SD card, then install the framework again once you've flashed /system and taken the update.
When I did updated to 4.4.4 I disabled the modules in the Xposed UI (not sure if that was necessary or not), but did not actually uninstall any of the APKs for the modules. When I reinstalled Xposed after updating, all I just turned all my modules back on and rebooted.
Call me paranoid, but whenever there is an update, I always flash back to 100% stock and then do the OTA update. Then, I'll re-root using philz recovery and restore my desktop with a backup of Nova. I'm always worried that taking an OTA update with and previous tinkering will lead to a gummed up phone.
That is just me, though.
mtpease said:
Call me paranoid, but whenever there is an update, I always flash back to 100% stock and then do the OTA update. Then, I'll re-root using philz recovery and restore my desktop with a backup of Nova. I'm always worried that taking an OTA update with and previous tinkering will lead to a gummed up phone.
That is just me, though.
Click to expand...
Click to collapse
Not really a bad practice either way, if you clear stuff out now and again. If you try to take an OTA with a modified /system partition, it usually just fails during the hash checks and never installs/modifies anything.
You started your thread title with a [q].... Perhaps the Q&A section would be the section to ask your question? ?
Good day all,
got a new OTA rolled in for my Droid Turbo, though I already have a clean flash from MM on this device.
The following update rolled in which failed to install per TWRP recovery (ERROR 7)
What exactly is this update?
Has to be installed with stock MM recovery, OR flash the full stock firmware, twrp version, in twrp (3020) worked for me. Don't forget to wipe caches, data unnecessary.
Einsteindks said:
Has to be installed with stock MM recovery, OR flash the full stock firmware, twrp version, in twrp (3020) worked for me. Don't forget to wipe caches, data unnecessary.
Click to expand...
Click to collapse
But I do not want to re-flash my firmware. Especially since this update is only 20+ mb it is not large enough for me to re-clean everything and restart it all. Stock recovery is the only solution?
Stock recovery only for tbe OTA. The OTA will likely fail if the ROM isn't pure stock. Flash the twrp version and wipe, and you'll only need to reload any ROM extras. Root with the beta SU after a simmered restart. It seems to like a settled ROM better. Update SU via PlayStore at restart.
M_w_B said:
But I do not want to re-flash my firmware. Especially since this update is only 20+ mb it is not large enough for me to re-clean everything and restart it all. Stock recovery is the only solution?
Click to expand...
Click to collapse
If by re-clean you mean re-delete system apps that you don't want, that will be inevitable. The OTA will not install unless system is 100% stock, and the TWRP package will reflash everything to 100% stock. So either way, if you want this update, you'll be re-deleting some system apps.
However, if you're worried about losing userdata, don't. Neither the OTA nor the TWRP package will touch that.
As for your original question of "what is the update," it's just a security patch. It updates the android security patch level to January 2017, and it makes it so phones with locked bootloaders cannot be unlocked (but it will not re-lock and already unlocked bootloader).
TheSt33v said:
If by re-clean you mean re-delete system apps that you don't want, that will be inevitable. The OTA will not install unless system is 100% stock, and the TWRP package will reflash everything to 100% stock. So either way, if you want this update, you'll be re-deleting some system apps.
However, if you're worried about losing userdata, don't. Neither the OTA nor the TWRP package will touch that.
As for your original question of "what is the update," it's just a security patch. It updates the android security patch level to January 2017, and it makes it so phones with locked bootloaders cannot be unlocked (but it will not re-lock and already unlocked bootloader).
Click to expand...
Click to collapse
Thank you for the info on the update. I will not do the effort for a patch like that.
Hi,
Can someone concisely give the most up to date instructions on how to root the P20 Pro
Confused because some people talk about debranding first? Is this necessary if you, like me, just have a generic non-network branded phone?
Also.. Does rooting require twrp?
A bit unclear on if I should use the offical or unofficial twrp methods.
And if so does twrp prevent OTA updates? I was lead to believe that any OTA updates would simply wipe any root and you just have to go through the steps again, but would twrp prevent an OTA update in the first place?
What are the best instructions to root the P20 Pro to keep the OTA updates going (even if you need to reroot after each update).
Thanks heaps in getting through the confusion!
Here you have manual to root in simple 4 steps. You need adb and fastboot on your computer, bootloader unlock code and Magisk from link in post
https://forum.xda-developers.com/hu...de-how-to-root-debrand-remove-retail-t3788326
Does any of the steps,
1/ unlocking the bootloader
2/ debranding
3/ installing TWRP
3/ rooting
Wipe the device?.. I'm assuming yes?
Also. What's the point of debranding?..
I think I'm on a generic P20 Pro that wasn't bought from a carrier - so is that step necessary for me.
Thanks heaps again for the advice - coming over from the Samsung world and maybe I'm so used to the rooting methods there
Also do any of those steps prevent OTA updates?
Or is there somehow to still use OTA updates but simply need to reapply root on every occasion there is ah update?
dgoncalves81 said:
Also do any of those steps prevent OTA updates?
Or is there somehow to still use OTA updates but simply need to reapply root on every occasion there is ah update?
Click to expand...
Click to collapse
Unlocking the bootloader will wipe your device. The other steps won't.
You need to have TWRP installed in order to be able to flash Magisk (for Root), and no you don't have to rebrand if you don't want to. You'll still be able to receive and download OTAs but if TWRP remains installed on your phone it won't be able to install unless you change back to the stock recovery. However there is methods to update with TWRP and you'll be able to get and install updates quicker than waiting for them to be pushed to you phone. That's the main reason people rebrand because generic European models are getting updates the fastest.
What's your device model and current firmware version from 'About Phone' in settings?
..
danifilth4king said:
Unlocking the bootloader will wipe your device. The other steps won't.
You need to have TWRP installed in order to be able to flash Magisk (for Root), and no you don't have to rebrand if you don't want to. You'll still be able to receive and download OTAs but if TWRP remains installed on your phone it won't be able to install unless you change back to the stock recovery. However there is methods to update with TWRP and you'll be able to get and install updates quicker than waiting for them to be pushed to you phone. That's the main reason people rebrand because generic European models are getting updates the fastest.
What's your device model and current firmware version from 'About Phone' in settings?
Click to expand...
Click to collapse
Thanks heaps for the advice - makes sense now!
I'm using the model CLT-L29 on C636 which I think is the Asia Pacific model.. And incidentally just received a OTA upgrade to the 128 firmware
.. So in order to receive OTA updates you simply have to change back to the stock recovery after using TWRP to install magisk and root?
But I imagine every time the OTA update occurs it wipes root?.. Which would mean reinstalling TWRP to regain root and doing the whole process again every time?
dgoncalves81 said:
Thanks heaps for the advice - makes sense now!
I'm using the model CLT-L29 on C636 which I think is the Asia Pacific model.. And incidentally just received a OTA upgrade to the 128 firmware
.. So in order to receive OTA updates you simply have to change back to the stock recovery after using TWRP to install magisk and root?
But I imagine every time the OTA update occurs it wipes root?.. Which would mean reinstalling TWRP to regain root and doing the whole process again every time?
Click to expand...
Click to collapse
Yep you got it in one lol
The other option so that you don't have to flash TWRP then back to stock recovery each time is when you receive an OTA is download the same firmware (Full-OTA version) from Firmware Finder - you would just need the update.zip - then using Huawei update extractor you can extract the ramdisk.img Then copy the ramdisk.img to your phone, use Magisk manager to patch it then copy it back to your PC and flash it via fastboot. But I think this is more work than flashing between TWRP & stock recoveries haha