Database Users

[REF][How To] Return to STOCK Recovery (IF rooted) and sideload OTA

By now, with all the OTA's, unless you are brand new to the 2013 X, you know you have to have stock recovery on your phone for an OTA Update or Soak Test to install, and your system can't be modified too much or it will fail the pre-flash validation checks built into the OTA.zip. (i.e. there is a manifest file that checks for specific files and their check sums before it will flash the ota).
If you have an unlocked bootloader, and rooted by flashing a 3rd party recovery (like TWRP, CWM, Philz, etc) and installing SuperSU, you likely didn't put stock recovery back on your phone.
IF you are close enough to stock (like I am... stock, unlocked, rooted, with adfree, wifi tether for root, greenify, Quick boot, and a few other apps that require root), you can just flash stock recovery and take the OTA.
The steps in this post help you do that, or get ready to do that, in case you are not near your PC when an OTA comes, of if you just don't want to use your PC.
NOTE: If you have changed too much of stock that the OTA fails, please see -> [FAQ] How to prepare for and take an OTA update (All Carriers)
NOTE: the following worked when updating 4.4 to 4.4.2, and 4.4.2 to 4.4.4 on my VZW Dev Edition X. Since Lollipop has not yet been released for my phone, I can't test this yet.
Note: If you have flashed your phone with another carrier's ROM, or have only flashed "parts" of your phone, these steps may not work!! Or they may cause you to brick!
NOTE: If your Bootloader version does NOT match the one for your phone's software version, taking an OTA could brick your phone!
You must have an Unlocked Bootloader and be rooted for these steps to work:
Obtain the STOCK Moto Recovery image, and TWRP image, for your phone:
On you phone, go App Drawer -> Settings... Make note of what is listed under System Version, and Android Version.
Visit one of the sites listed in -> http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347 and obtain the EXACT same ROM/SBF file that is currently on your phone. Download the ZIP to your PC.
Unzip or extract the RECOVERY.IMG file from the SBF ZIP file.
Download the latest TWRP Recovery from -> http://teamw.in/project/twrp2/234 (under the Download-Fastboot heading)
the latest SuperSU from -> http://download.chainfire.eu/supersu or the latest CWM / TWRP / MobileODIN installable ZIP from http://forum.xda-developers.com/showthread.php?t=1538053
Flashing Recovery
Place your stock recovery.img, the latest TWRP img, and the latest SuperSU.zip in your phone's DOWNLOAD folder.
Install Rashr.
On your phone, launch Rashr.
Scroll down and select other from storage
Browse and select your stock recovery
When it completes, pick the option to reboot to stock recovery.
Your device should reboot and display the Motorola logo and then the Android in distress (logo with Exclamation mark)
Press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key. You should be in Stock recovery now.
Reboot your phone as normal.
To reflash TWRP or other custom recovery, as long as you are still rooted, you can repeat the same steps, selecting your custom recovery in step 5.
How to SIDE LOAD an OTA.ZIP via this process
If your carrier has started the push of the OTA ZIP for your phone, but you haven't received it, and you've found the correct OTA ZIP posted online and would like to flash it, the following steps can be used...
Download the OTA ZIP file (usually named as BLUR_XXX.XXX.XXX.zip, where XXX.XXX.XXX is the build number the ZIP will update) to your phone's /SDCard
Perform steps 1-7 under Flashing Recovery above to flash STOCK recovery onto your phone, and reboot into Stock Recovery.
Use the Vol Down key to scroll to Apply Update From SDCard, and press the Power key to select.
Use Vol Down key to scroll to your OTA zip file, and press Power to select.
The install will begin by verifying the update package, then verifying files on your phone match.
If the install fails, it will be reported on the screen, along with why. (usually because you have modified system files, or are not on the correct ROM version). You need to fix these errors and try again.
If verifications are successful, the patching process steps will begin. This may take several minutes.
Your phone should report Script Succeeded and Install from sdcard Complete.
Ensure Reboot System Now is highlighted, and press the Power key to reboot the phone.
The initial reboot may take longer than a regular reboot.
Note: You will see Android Is Upgrading or Optimizing screen during the boot process, that is normal.
After the update install process is complete, use Rashr to flash TWRP (again, other from storage and pick your TWRP). When prompted, reboot into recovery (so twrp sticks). When in TWRP, select reboot to system.
If you lost root, reboot into TWRP recovery and install SuperSU.zip
How to Root with unlocked bootloader...
If you unlocked your bootload by getting the code from Moto, after taking the OTA you may root by following ->http://forum.xda-developers.com/moto-x/general/how-to-how-to-root-5-1-unlocked-t3140217 NOTE: while the thread is titled for 5.1, it works on older Android versions as well.

Good work KidJoe :laugh::good:

I guess this will be more relevant as Soaks start heading out for the 2013 X...

Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )

ks73417 said:
Good post. Can I use the same process on MotoX 2014 pure? I have turned Moto OTA to get rid of constant "update available" notification, if I turn that back on, do you know where the OTA zip file is downloaded (i'm thinking cache )
Click to expand...
Click to collapse
Yes, the OTA zip is usually stored in /cache (at least is is on the 2013 X, and my past Moto phones). it is usually named for the rom it is upgrading, not what the upgrade takes you to.
I don't see why this wont work on the 2014 X, as it did on older motos too.

Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app

ajsonofgod said:
Brother i got Motorola updates services update today. I will try your method once there will be available ota. And can you tell me how to backup my whole rom?
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
In TWRP you can make a nandroid backup. I've never done it. I haven't had need because I run stock. If I need to reflash, I just reflash the same SBF I've been running.

I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?

ejlmd said:
I followed the instructions in the OP to return to stock recovery, then applied the OTA update Blur_Version.213.44.1.ghost_row.Retail.en.US, but am failing with this message
/system/etc/install-recovery.sh has unexpected contents
I haven't knowingly modified any system files, although I am rooted. Any thoughts about what this error might mean and how to resolve it?
Click to expand...
Click to collapse
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.

KidJoe said:
What ROM is on you phone to start with? On your phone go App Drawer -> Settings -> About.. tell me the Android Version, System Version and Build Number. Also what model X do you have?
213.44.1.ghost_row.Retail.en.US is an XT1053 4.4.4 update file for the XT1053 if I'm not mistaken. It is meant to be applied to a 4.4.3 stock rom, and it might apply to a 4.4.2 stock rom..
The OTA file will fail its pre-flash validation checks if you are not on the intended stock rom.
Click to expand...
Click to collapse
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.

there any way to make a dump the stock recovery in Lollipop, without the need root?

ejlmd said:
Thank you. I'm embarrassed that I didn't perform sufficient due diligence. I am already on the same system version as the update (213.44.1.ghost_row.Retail.en.US ), which I mistakenly thought was to get to Lollipop from 4.4.4.
Click to expand...
Click to collapse
Yeah, OTA Update files are often named including the version the phone must be on, not the version it takes the phone to.

Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.

ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
It's ABSOLUTELY BEST you avoid the update............but....
If you can't, it is highly recommended that you clean flash it...kind of the only choice. Flash the 4.4.4 Brazilian stock ROM. And install the update from recovery. You can reroot after adding TWRP back.

I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app

ajsonofgod said:
I am also on stock rom 4.4.4. But i dont have this rom on my pc for reflashing. Please provide link for download or some info related to it
Sent from my XT1052 using XDA Free mobile app
Click to expand...
Click to collapse
Please see the LINK in my signature for sites to download stock SBF files

ks73417 said:
Do I need to uninstall xPosed & GravityBox before I sideload L ? I guess, Kitkat version of xposed worn't work in L anyway.
Click to expand...
Click to collapse
As explained elsewhere... Xposed makes changes to /system which cause OTA updates to fail their pre-flash validation checks.
It is recommended to boot to TWRP and install /SDcard/Android/data/de.robv.android.xposed.installer/files/Xposed-Disable-Recovery.zip then uninstall XPosed.
You will also need to undo any changes to /system or other parts the the OTA tries to validate before installing, or else it will fail.
You are correct that a newer version of Xposed is needed.
You may also want to wait on trying the 5.0.2 Leaks because if they are an early limited early test version, rather than a soak which is nearly ready to be pushed to all, you could be stuck on this version until an SBF leaks.

Update
Does anyone know how to return to stock recovery for lollipop? New update came up today but I have TWRP.

upload the stock recovery lollipop please!!!!

Good work, love your detailed explanations always .

Unable to update phone

I recently purchased the Zuk Z1 from Amazon. After I started the device there was a message that I could update my phone. After I clicked it, it said 'Update is installing' but after a short time the device turned itself off and started again in Recovery-Mode. There it said something in Chinese which I can only confirm. After that I can choose a language and then there are 4 Options:
Reboot
Install update package
Swipe data
Shut down
If I choose Install update package there is clue and if I confirm it, it says 'Install failure'
After a restart there is still that update available but if I do it again, nothing changes.
Does anyone have the same problem and could help me?
Note: My phone is not encrypted and Hard-Reset doesn't work either.

Hello, I had bought from Amazon and had the same problems with the updates. have found preinstalled supersu and then installed with flashify TWRP. then simply flashed a other rom

Your rom is ZUI ?

My rom is cyanogenOS and I have exactly the same problem. I bought my zuk z1 via Linio and i suspect that I have the chinese version with cyanogenOS installed afterwards, but I don't know because I received the update.
I hope someone has the solution for this trouble.

gmurop said:
My rom is cyanogenOS and I have exactly the same problem. I bought my zuk z1 via Linio and i suspect that I have the chinese version with cyanogenOS installed afterwards, but I don't know because I received the update.
I hope someone has the solution for this trouble.
Click to expand...
Click to collapse
If the phone has been rooted via an app like KingRoot, or has had SuperSU installed on it, then the partitions are changed. It's possible that your vendor may have messed with your phone before you purchased it. When this happens, COS recovery won't be able to install new updates.
As far as I know, the only solution is a clean flash of COS. Search for PaulOBrien's "Convert Z1 from ZukUI to Cyanogen OS" forum post on MoDaCo, download the COS zip file, and flash that in recovery (you'll lose all your data, be warned. Also, if you are using a custom recovery, you'll need to revert back to the COS recovery .img in that post before flashing the COS zip).
You should be able to install COS updates after doing so. Keep in mind you'll need to install about 8-10 of them after the initial flash to get up the most recent version of Z1 COS.
Good luck!

Frogger4600 said:
If the phone has been rooted via an app like KingRoot, or has had SuperSU installed on it, then the partitions are changed. It's possible that your vendor may have messed with your phone before you purchased it. When this happens, COS recovery won't be able to install new updates.
As far as I know, the only solution is a clean flash of COS. Search for PaulOBrien's "Convert Z1 from ZukUI to Cyanogen OS" forum post on MoDaCo, download the COS zip file, and flash that in recovery (you'll lose all your data, be warned. Also, if you are using a custom recovery, you'll need to revert back to the COS recovery .img in that post before flashing the COS zip).
You should be able to install COS updates after doing so. Keep in mind you'll need to install about 8-10 of them after the initial flash to get up the most recent version of Z1 COS.
Good luck!
Click to expand...
Click to collapse
Oh man thank you very much, but does that mean that I won't be root anymore? In that case I don't know if staying with the current version or upgrade and loss my root privilegies. What do you think?

I have info tha new apdate is ready to install. I press install and phone restarts and come back to noal system. Didnt install the update. Can anybody help?
Wysłane z mojego Z1 przy użyciu Tapatalka

[GUIDE] Install Official Marshmallow Update Oxygen OS 3.1.3

OnePlus Team has finally rolled out long-awaited Marshmallow Update. This time, it isn't community build or beta, it is a STABLE update!
This post will guide you to upgrade from 2.2.2 to 3.1.2 for both non-rooted and rooted users.
Disclaimer:
Code:
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
For non-rooted, unmodified system users (who haven't tinkered anything with the device's software):
1a. You must have received a notification to update to OOS 2.2.3
Download it, and hit reboot now! This will automatically install the update which will prepare your device to install MM update.
1b. If you haven't received the update notification for 2.2.3 then download it manually from here - https://goo.gl/NkZm2I
Place it in the root directory of Internal Storage (not inside any folder, just directly on Internal storage) and then enter recovery mode by turning off your phone and then pressing Power button + volume down button at the same time. Once you get into recovery, select Install from Internal Storage and the select your file and flash it!
Congratulations, now you are on OOS 2.2.3!
Download MM OOS 3.1.2 from here - http://s3.amazonaws.com/oxygenos.on...OTA_017_all_201609231354_e675a52db5a044e7.zip
and place it on your SD card again, like above, go to recovery and flash the file!
You are now on Official Oxygen OS 3.1.2 MM Update!
For rooted users, who have modified system:
1. Download the zip http://s3.amazonaws.com/oxygenos.on...OTA_017_all_201609231354_e675a52db5a044e7.zip and place it on your SD Card or Internal Storage
2. Go to your recovery (TWRP is preferred)
3. Wipe System, Data, Cache, and Dalvik Cache
4. Select Install and navigate to your file location, select your file and flash it!
5. Flash https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view to get root access!
6. Reboot! Enjoy your MM Update!
(Optional) These are steps I followed for a safer install:
1. Took the whole backup of 2.2.2 from official TWRP
2. Flashed Whole 2.2.2 zip from here - http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_2.2.2/ which I had already downloaded
3. Flashed Stock Lollipop recovery
4. Unrooted my phone
5. Locked and unlocked my bootloader (don't know why I was getting locked bootloader error while flashing blu-spark twrp so did it)
6. Unrooted my phone
7. Flashed 3.1.2 zip from stock lollipop recovery
8. Flashed blu-spark TWRP using fastboot
9. Flashed modified SuperSU
10. Restored just data partition from my 2.2.2 backup and wiped cached.
This way is long and tedious but ensures you get the data, which was important for me.
Edit: Above process can be applied to install Oxygen OS 3.1.3 (link below) Directly! Hope you have a pleasant experience on Marshmallow, cause I'm definitely loving it
Feel free to ask any queries!
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.2 link - http://s3.amazonaws.com/oxygenos.on...OTA_017_all_201609231354_e675a52db5a044e7.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
6. Official Oxygen OS 3.1.3 link - http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_3.1.3/
Credits: Joshwin Aranha, OnePlus Team, Google and everyone who I forgot to mention
Hit Thanks if this post helped you!

The 3.1.2 official update isn't in oneplus download center. And it seams that there is no mention in oneplus forums.
Is your info legit?
Sent from my ONE E1001

OP didn't announced officially about oxygen os 3.1.2 but sone OPX users have installed it

Strange......
This rom file can be installed as stand alone? Im currently on community 3.1.1.
Sent from my ONE E1001

sniper20 said:
Strange......
This rom file can be installed as stand alone? Im currently on community 3.1.1.
Sent from my ONE E1001
Click to expand...
Click to collapse
It can be flashed directly using TWRP (use Latest TWRP by blu spark)

sniper20 said:
The 3.1.2 official update isn't in oneplus download center. And it seams that there is no mention in oneplus forums.
Is your info legit?
Sent from my ONE E1001
Click to expand...
Click to collapse
It was announced but then again removed. I personally saw and downloaded it from there.

Mystery solved.... Hehe. I ll install it via official recovery.
Sent from my ONE E1001

sniper20 said:
Mystery solved.... Hehe. I ll install it via official recovery.
Sent from my ONE E1001
Click to expand...
Click to collapse
Let me know how that works out for you!

I'm using Sultan's CM 13. Can i flash Oxygen via Blu_spark TWRP after factory reset ?

aadnanrulz said:
I'm using Sultan's CM 13. Can i flash Oxygen via Blu_spark TWRP after factory reset ?
Click to expand...
Click to collapse
You will have to wipe system, data and both cache and then flash the zip!

Sachin7843 said:
Let me know how that works out for you!
Click to expand...
Click to collapse
I ll post today late at night.....
Sent from my ONE E1001

Thanks mate !

Do we need to upgrade to 2.2.3 first or upgrade from 2.2.2 is also fine ?

Szaby59 said:
Do we need to upgrade to 2.2.3 first or upgrade from 2.2.2 is also fine ?
Click to expand...
Click to collapse
I didn't have right resources with me for now so I just flashed 2.2.2 zip (had downloaded the whole zip from downloads.oneplus.net), unrooted and flashed stock recovery (check the main post for links) and directly flashed 3.1.2 zip! Worked flawlessly!

Sachin7843 said:
I didn't have right resources with me for now so I just flashed 2.2.2 zip (had downloaded the whole zip from downloads.oneplus.net), unrooted and flashed stock recovery (check the main post for links) and directly flashed 3.1.2 zip! Worked flawlessly!
Click to expand...
Click to collapse
i have two questions here
1. were you able to format external SD card as internal?
2.how to flash modified/original TWRP after install OOS 3.1.2?

I flashed and rooted it properly but xposed isn't active. What version do I have to flash?

Which custom recovery is supported for this ROM ? I couldn't install the package using official twrp recovery. Had to switch to official recovery to install the ROM

Darkside1984 said:
I flashed and rooted it properly but xposed isn't active. What version do I have to flash?
Click to expand...
Click to collapse
Ok, I answer myself: xposed sdk23 arv version. Everything works fine (I've installed all zips by custom recovery).

working on twrp
just dirty flashed over oos 3.1.1 with bluspark latest recovery & working well

nitheshg said:
i have two questions here
1. were you able to format external SD card as internal?
2.how to flash modified/original TWRP after install OOS 3.1.2?
Click to expand...
Click to collapse
I couldn't understand your question 1... for your second question - I flashed 3.1.2, unlocked bootloader, flashed Blu-spark's TWRP, flashed Modified Super SU and then restored just Data from my 2.2.2 backup!

[Solved] Can´t update from version 5.1.2 to version 5.1.4 OnePlus5

So i tried to install the update for my OnePlus5 but TWRP gives ERROR 7 i also tried to wipe my data (including system),
i also tried to install the update with the stock recovery (without root) and the update just fails
oxygen updater won´t work aswell
thanks in advance
i´ve trieded newer versions of oxygen os too
sry for my bad english i am german

Hi!
Are you trying to install a full OTA zip (1GB+ in file size), or a partial OTA (more around 50 MB - 200 MB) over your current 5.1.2 ROM?
At this point I would suggest you flash a full OTA zip of OOS 5.1.4, either through TWRP or OnePlus' recovery. @Titokhan provides a list of mirrors where you can download full signed flashable zips. Make sure to compare the MD5 signature of your downloaded file with the reference signature inscribed on the download page -- this makes sure your download is not corrupted.

Alexandre-P said:
Hi!
Are you trying to install a full OTA zip (1GB+ in file size), or a partial OTA (more around 50 MB - 200 MB) over your current 5.1.2 ROM?
At this point I would suggest you flash a full OTA zip of OOS 5.1.4, either through TWRP or OnePlus' recovery. @Titokhan provides a list of mirrors where you can download full signed flashable zips. Make sure to compare the MD5 signature of your downloaded file with the reference signature inscribed on the download page -- this makes sure your download is not corrupted.
Click to expand...
Click to collapse
i used the OTA before but i will try the OTA you suggested
thanks in advanced:good:
Edit: can i theoretically use a newer version than 5.1.4?

Fredwuz said:
Edit: can i theoretically use a newer version than 5.1.4?
Click to expand...
Click to collapse
OnePlus enabled Treble on the OP5 around stable release 5.1.5, and release notes for 5.1.5 stressed that the device should be on 5.1.4 before applying the 5.1.5 upgrade. The release notes for 5.1.6 also stressed that the user first upgrade to 5.1.5 before applying the 5.1.6 system upgrade. Based on that information, I would highly suggest you make sure your device works correctly on 5.1.4 first, then 5.1.5, followed by 5.1.6, and only then you upgrade to a later release.

Alexandre-P said:
OnePlus enabled Treble on the OP5 around stable release 5.1.5, and release notes for 5.1.5 stressed that the device should be on 5.1.4 before applying the 5.1.5 upgrade. The release notes for 5.1.6 also stressed that the user first upgrade to 5.1.5 before applying the 5.1.6 system upgrade. Based on that information, I would highly suggest you make sure your device works correctly on 5.1.4 first, then 5.1.5, followed by 5.1.6, and only then you upgrade to a later release.
Click to expand...
Click to collapse
so i flashed version 5.1.3 and it did work but when i tried to flash to version 5.1.4 TWRP was stuck in "Patching system image unconditionally..." did i do something wrong?
After i flashed to 5.1.3 the devices worked normal as always

Here's what I would do:
1. Flash 5.1.3 -- don't re-root, don't flash TWRP.
2. At this point, if you try to boot to recovery, you should have OnePlus' recovery. That's cool, just leave it that way.
3. Boot to system. Allow the system to find newer upgrades, and apply them using the system updater as they come.
4. When you're all updated again to latest release, follow instructions to TWRP and root the device.

Alexandre-P said:
Here's what I would do:
1. Flash 5.1.3 -- don't re-root, don't flash TWRP.
2. At this point, if you try to boot to recovery, you should have OnePlus' recovery. That's cool, just leave it that way.
3. Boot to system. Allow the system to find newer upgrades, and apply them using the system updater as they come.
4. When you're all updated again to latest release, follow instructions to TWRP and root the device.
Click to expand...
Click to collapse
now the updater says my system is up-to-date but i only have 5.1.3 installed

Fredwuz said:
now the updater says my system is up-to-date but i only have 5.1.3 installed
Click to expand...
Click to collapse
Reboot, wait some time.

What is sometime are about 5 hours enough?
Sent from my OnePlus5 using XDA Labs

Fredwuz said:
What is sometime are about 5 hours enough?
Click to expand...
Click to collapse
You can try to use a VPN(app) which connects to another country to force the update. Or flash it with the stock recovery by downloading the file, place it in .ota folder and update it.

strongst said:
You can try to use a VPN(app) which connects to another country to force the update. Or flash it with the stock recovery by downloading the file, place it in .ota folder and update it.
Click to expand...
Click to collapse
I tried to use tunnelbear and connected to USA but the updater won't find an update now I will try the other method but can't I just use the lokal Upgrade Option in the updater?
Edit: I have to use version 5.1.4 or?
Sent from my OnePlus5 using XDA Labs

Fredwuz said:
I tried to use tunnelbear and connected to USA but the updater won't find an update now I will try the other method but can't I just use the lokal Upgrade Option in the updater?
Click to expand...
Click to collapse
Yes you can, that's what I suggested already

My experience with the 5.1.4 update - ERROR 7 & Treble error fix
Hi, I have 3 OnePlus 5's in my household and I have gotten them all to update to 5.1.4, then 5.1.5, then 5.1.6+ with this method.
(5.1.4 and then 5.1.5 is needed before flashing 5.1.6 or greater).
In my experience, no matter what caches I cleared or what recoveries I had used, 5.1.4 was not flashable on all three devices with the bootloader unlocked. If you have the patience and time, this method should 99.99% work for you if done correctly (leaving a 0.01% chance of failure just in case it does fail lol but that shouldn't happen.)
1.) Firstly, back up your device. I suggest doing this by making a full titanium backup, and copying all the files on the internal storage to a folder on your computer.
This may take a while to copy. In my experience, the fastest way to copy all the data off to the computer is to boot the device into TWRP recovery, plug a good USB C cable in to the device and to the PC's USB port, unlock the device in TWRP (put in the password/pattern to decrypt and mount the data partition [Ignorable if you dont set a password on the device]), and use the adb pull command to pull the files off the device. I found that ADB pull works much faster than an mtp file transfer in windows explorer.
Steps for ADB pull:
Ensure adb is installed on the computer with adb drivers. For Windows, open command prompt or powershell as admin. Type in adb devices and hit enter. If your OnePlus device comes up, then all is good. Use the command (without the square brackets):
[ adb pull /sdcard "XXX/." ]
Replace XXX with a directory on your computer (for example, you can do [ adb pull /sdcard "C:\Users\YOURUSERNAME\Desktop\OnePlus/." ]
If anyone notices any issues with this command please let me know so I can update the post. I am writing this off memory, so there may be minor mistakes.
2.) After your device backs up and you're happy with the backup (i.e. everything you need backed-up is saved off of the phone onto the computer), It's time to relock the bootloader and restore the firmware on the phone.
I haven't tried a simple fastboot OEM relock command, so I cannot say whether that is sufficient enough.
What I did was follow this thread:
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Download the Driver and the Oxygen version.
Once downloaded, extract the driver Driver_OnePlus5.zip file to its own folder. Extract the firmware to its own folder (cheeseburger_23_O.13_170803).
3.) Using the firmware restoring tool to relock the bootloader and restore the device to factory firmware condition.
Now:
Turn off your OnePlus 5 device.
Hold volume up key.
Plug USB cable in to the PC and the Type-C side to the device. Make sure only volume up is held whilst you do this.
Open device manager and check for missing drivers/driver issues. If the driver isn't detected, use device manager to browse for the extracted Driver_OnePlus5 folder you made earlier.
The LED light on the OnePlus 5 should be yellow if I can remember correctly.
Open msm download tool as an adminstrator (right click, run as administrator)
Click the start button on the top left of the msm download tool. (If nothing happens, make sure drivers are installed properly and that the device is in download mode [Repeat the above steps])
If successful, one of the "Device Type" should show your device connected {com device} and the download process and time row will update. Wait for the download progress to finish. The device will reboot on its own when completed. The status should turn green and say done/finished (If I remember correctly).
When your device reboots, do a quick setup. Don't bother putting your google account in or restoring anything if you plan on unlocking the bootloader later for TWRP or other reasons.
Unlocking the bootloader will wipe the phone. For now, just focus on the updates.
Connect the device to Wi-Fi. I found one of the devices I used this method on wouldn't connect to Wi-Fi (modem issue or something). Luckily, I had the 5.1.4 update already downloaded on the computer so I copied the update to the root folder on the device and used the local upgrade option in the OTA update options (in the phone system update settings). Updating the firmware fixed my Wi-Fi issue.
Basically, just do the OTA updates as you would normally. Start with 5.1.4, then you can do the 5.1.5. Do not jump to 5.1.7 because OnePlus only just added treble support in 5.14/5.15 releases so it is important do do those in order first. If you can, do 5.1.4, 5.1.5, 5.1.6 and then 5.1.7 in order. Just follow the updates that the OTA screen allows you to take.
Notes for the Pie update:
I haven't had issues installing Pie with the bootloader unlocked, so if you wish to stay on oreo for now and update later with an unlocked bootloader, that should be fine.
If your bootloader is locked, and you're on at least OOS 5.1.5, you should be able to flash the Pie OTA with the stock recovery without issues.
If you encounter issues installing Pie, and your bootloader is unlocked follow this:​
Unlocked bootloader - Pie Update - Removing compatibility.zip from firmware archive:​
Method 1: Pre-Removed compatibility.zip modified firmwares:
For STABLE:​Follow this link:
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Download " OxygenOS 9.0.0 Full Zip (modified, without compatibility.zip) ".
For BETA:​Follow this link:
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
Download " OxygenOS Open Beta XX Full Zip (modified, without compatibility.zip) ".
You will need a Pie-compatible recovery. Download a compatible custom Recovery (TWRP) (Also available on https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 )
Flash a Pie-compatible TWRP and boot into it.
Copy the downloaded " OxygenOS Open Beta XX Full Zip (modified, without compatibility.zip) " to the device.
In TWRP, use: Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe.
I would recommend taking a nandroid backup before proceeding, if you have any important data on the device.
Flash the downloaded " OxygenOS Open Beta XX Full Zip (modified, without compatibility.zip) ".
Wipe dalvik-cache and cache.
Enjoy Pie.
Method 2: Manual Method to remove compatibility.zip for unlocked bootloaders:
Download the FULL firmware OTA (from device settings, or from the OnePlus website).
Copy the firmware to the computer (If downloaded on the device, it will be in the ".ota" folder. Else, it is available on the OnePlus firmware downloads page.
Open the firmware archive with 7-Zip.
Delete Compatibility.zip from the archive.
Copy the now-modified firmware back to the device.
You will need a Pie-compatible recovery. Download a compatible custom Recovery (TWRP) (Also available on https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003 )
Flash a Pie-compatible TWRP and boot into it.
In TWRP, use: Wipe > Advanced wipe > Select dalvik-cache and cache > Swipe to wipe.
I would recommend taking a nandroid backup before proceeding, if you have any important data on the device.
Flash your manually-modified OTA/firmware archive in TWRP.
Wipe dalvik-cache and cache.
Enjoy Pie.
DO NOT use winrar or any other non-recommended programs to remove compatibility.zip. I found that winrar causes treble errors or error 7.
4.) Re-unlocking the bootloader & Restoring your data.
Once you've installed 5.1.5 or greater, you can now safely go into developer settings and enable oem unlocking, and then reboot to the bootloader to unlock the bootloader (which will wipe/erase the phone data but keep the version to whatever you updated it to). You may then proceed to install TWRP, magisk if you plan on restoring with titaniumbackup, and restore all your sd card contents (or the sd card contents that you need) back from the computer backup the the device (I usually use ADB Push whilst booted in TWRP recovery because it copies quicker than MTP).
Updates should work from now on ( I was able to install android PIE Beta with the bootloader unlocked [See the Pie notes above]. Only had issues with the 5.14 / 5.15 updates with the bootloader unlocked ).
Hope this helps. If anyone has any more information, or questions about this method, do share. Like I said earlier, if done correctly, this method should definitely work for you guys.

Love you Guys:victory:
I did it and it worked first I flashed version 5.1.3 then version 5.1.4 and then I used the updater to upadate directly to version 9.0.0 and it worked :victory:
Thanks a lot and a happy new year
Sent from my OnePlus5 using XDA Labs

Fredwuz said:
Love you Guys:victory:
I did it and it worked first I flashed version 5.1.3 then version 5.1.4 and then I used the updater to upadate directly to version 9.0.0 and it worked :victory:
Thanks a lot and a happy new year
Click to expand...
Click to collapse
Sent from my OnePlus5 using XDA Labs

Fredwuz said:
Love you Guys:victory:
I did it and it worked first I flashed version 5.1.3 then version 5.1.4 and then I used the updater to upadate directly to version 9.0.0 and it worked :victory:
Thanks a lot and a happy new year
Click to expand...
Click to collapse
Glad you got it working! Happy new year to you as well

Upgrade from old 9.8.15 to the latest dev build

All right guys, I haven't been active for quite a long time in the past year or so and need some additional help like the title says.
So , what would be the most painless way to get from the old Dev 9.8.15 to the latest dev build ... probably the 20.3.26? (From Android 9 to 10).
A step by step guide would be priceless since no one wants to end getting your phone bricked, right?
So...what? Use miflash an get back to global Rom? If so, which one, and which firmware? Also, what twrp to use,magisk and so on...
Is it possible to use the twrp app for the process ?
Any kind of advice is appreciated.
Cheers!
Sent from my Redmi K20 using Tapatalk

We guess you speak about beta xiaomi.eu custom ROM and not beta China ROM?
- Download latest 20.3.26 (for Redmi K20/Mi 9T devices) => https://androidfilehost.com/?fid=4349826312261755297
- Download Magisk uninstaller (if you get issues after reinstalling Magisk in new ROM version) => https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-uninstaller-20200323.zip
- Download latest Magisk version => https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Put all these zip files in root of your phone's storage and reboot your phone in TWRP.
1) Flash new ROM version in TWRP. Reboot after finished.
2) Wait phone to boot into system (can take a few minutes).
3) Reboot again in TWRP and flash Magisk zip (NOT uninstaller zip).
4) Reboot your phone, *if your phone fail to boot to system -> do step 5.
*5) Reboot to TWRP and flash Magisk uninstaller zip, then flash Magisk zip again. Reboot your phone.
Nothing difficult... ^^

Micdu70 said:
We guess you speak about beta xiaomi.eu custom ROM and not beta China ROM?
Click to expand...
Click to collapse
Exactly.
Micdu70 said:
- Download latest 20.3.26 (for Redmi K20/Mi 9T devices) => https://androidfilehost.com/?fid=4349826312261755297
- Download Magisk uninstaller (if you get issues after reinstalling Magisk in new ROM version) => https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-uninstaller-20200323.zip
- Download latest Magisk version => https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Put all these zip files in root of your phone's storage and reboot your phone in TWRP.
1) Flash new ROM version in TWRP. Reboot after finished.
2) Wait phone to boot into system (can take a few minutes).
3) Reboot again in TWRP and flash Magisk zip (NOT uninstaller zip).
4) Reboot your phone, *if your phone fail to boot to system -> do step 5.
*5) Reboot to TWRP and flash Magisk uninstaller zip, then flash Magisk zip again. Reboot your phone.
Nothing difficult... ^^
Click to expand...
Click to collapse
Just to be clear so i do not hassle day in and day out.
- Since we are speaking about two different android builds, there is no need to revert back to global? Somewhere else "suggested" to do that because of that exact reason. (by that I mean the global fastboot ROM)
- Do i need any specific TWRP build to make it go without any troubles?
- When flashing new ROM i wipe all - anything specific so i don't miss out ? (haven't done it in a while)
for now thanks a lot mon ami.

Pejpi said:
Exactly.
Just to be clear so i do not hassle day in and day out.
- Since we are speaking about two different android builds, there is no need to revert back to global? Somewhere else "suggested" to do that because of that exact reason. (by that I mean the global fastboot ROM)
- Do i need any specific TWRP build to make it go without any troubles?
- When flashing new ROM i wipe all - anything specific so i don't miss out ? (haven't done it in a while)
for now thanks a lot mon ami.
Click to expand...
Click to collapse
- You don't need to revert back to global when using xiaomi.eu ROM.
- Use your current TWRP, it should be fine and it will be automatically updated after flashing new xiaomi.eu ROM.
- You don't need to wipe anything. In case of issue after ROM update, you can "Format Data" in TWRP > Reboot TWRP > Put 20.3.26 zip ROM and reflash it (clean flash).

Micdu70 said:
- You don't need to revert back to global when using xiaomi.eu ROM.
- Use your current TWRP, it should be fine and it will be automatically updated after flashing new xiaomi.eu ROM.
- You don't need to wipe anything. In case of issue after ROM update, you can "Format Data" in TWRP > Reboot TWRP > Put 20.3.26 zip ROM and reflash it (clean flash).
Click to expand...
Click to collapse
Allright, quick update. Tried to flash as you said.
And almost everything went fine. Phone booted perfectly into new xiaomi.eu dev ROM - Thumbs up!
but, but...there is always a but What ever i do now i cant enter TWRP anymore, what ever i press vol up or down it goes straight into fastboot mode. I suppose i need to reinstall TWRP again? If so what would be the best build reinstall ?

Pejpi said:
Allright, quick update. Tried to flash as you said.
And almost everything went fine. Phone booted perfectly into new xiaomi.eu dev ROM - Thumbs up!
but, but...there is always a but What ever i do now i cant enter TWRP anymore, what ever i press vol up or down it goes straight into fastboot mode. I suppose i need to reinstall TWRP again? If so what would be the best build reinstall ?
Click to expand...
Click to collapse
vol up = TWRP
vol down = Fastboot
Yes, you can try to reinstall TWRP (Official) => https://dl.twrp.me/davinci/

Micdu70 said:
vol up = TWRP
vol down = Fastboot
Yes, you can try to reinstall TWRP (Official) => https://dl.twrp.me/davinci/
Click to expand...
Click to collapse
So, just a quick update.
I did all as you described, step by step and now after a few days using the phone i can say....everything well better then i expected. No problems while flashing whatsoever.
Cheers to you and your guide, i suppose the same goes when upgrading to new MIUI12?

Pejpi said:
So, just a quick update.
I did all as you described, step by step and now after a few days using the phone i can say....everything well better then i expected. No problems while flashing whatsoever.
Cheers to you and your guide, i suppose the same goes when upgrading to new MIUI12?
Click to expand...
Click to collapse
Yeap, download and install MIUI 12 Beta zip ROM in TWRP.
After updating to MIUI 12 Beta ROM, you may need to clear all app data of "Updater" app in phone's settings to fix it (if you can't open the Updater to check for OTA updates).

Micdu70 said:
We guess you speak about beta xiaomi.eu custom ROM and not beta China ROM?
- Download latest 20.3.26 (for Redmi K20/Mi 9T devices) => https://androidfilehost.com/?fid=4349826312261755297
- Download Magisk uninstaller (if you get issues after reinstalling Magisk in new ROM version) => https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-uninstaller-20200323.zip
- Download latest Magisk version => https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip
Put all these zip files in root of your phone's storage and reboot your phone in TWRP.
1) Flash new ROM version in TWRP. Reboot after finished.
2) Wait phone to boot into system (can take a few minutes).
3) Reboot again in TWRP and flash Magisk zip (NOT uninstaller zip).
4) Reboot your phone, *if your phone fail to boot to system -> do step 5.
*5) Reboot to TWRP and flash Magisk uninstaller zip, then flash Magisk zip again. Reboot your phone.
Nothing difficult... ^^
Click to expand...
Click to collapse
Is this guide works with already rooted Mi 9T with unlocked bootloader? I also have an old MIUI with TWRP Recovery and Magisk. I wondering if i could use this guide...?
Wysłane z mojego Mi 9T przy użyciu Tapatalka