Database Users

[GUIDE] All-in-One Moto E Beginner's Guide

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About the guide
This guide is to provide information about the phone and directions about modding your phone. Most of the stuff is already posted in the forums while some of it is not. I'll try my best to explain how the stuff works for Moto E. How to Root, recover, troubleshoot so you don't screw up your phone by flashing something you're not supposed to.
Standard Disclaimer:** I'm NOT responsible for any damage you do to your phone trying to mod it. Understand how to recover from issues carefully. **
Index
I just bought a Moto E, now what?
Starting Up -Drivers, ADB and Fastboot.
Facts - Bootloader & Recovery.
Beginning the workout
Unlocking Bootloader
Flashing Custom Recovery
Rooting.​
I just bought a Moto E, now what?
Congratulations on your phone. Now you should understand the device you have.
Moto E has three variants,
XT1021 - Single SIM
XT1022 - Dual SIM
XT1025 - Dual SIM with TV
Determine what variant you have. Its important as some mods maybe specific to one device and might not work with other.
To get more info about your device, I'd recommend giving this FAQ thread some time.
[FAQ] Frequently Asked Questions For Moto E​
Starting Up - Drivers, ADB & Fastboot
So let us begin. You need to setup your system first.
Drivers, Get your drivers from Motorola Motorola Device Manager. Install it.
ADB & Fastboot.
[Option 1]
(Android SDK), Android SDK is the Android Software Development Kit. It includes the tools to develop apps and debug your device.You need it in order to mod your device and recover sometimes.Get it from Android SDK Its a big package in terms of size.
[Option 2]
If you don't plan to develop anytime soon and concerned with the size, you can get the Minimal ADB & fastboot from [TOOL]Minimal ADB and Fastboot
Setting UP ADB & Fastboot:
You need to set you path variables so you can run ADB & Fastboot commands without worrying about your present directory.
Extract your SDK package to a directory. (or installation path in case of minimal)
Run SDK Manager.exe. It might show few packages available to download. Tick everything under tools.Click Install packages. Accept license. Install
Naviagte to platform-tools (it should have files adb.exe & fastboot.exe)
Copy the path
Now goto Control Panel > System
Click Advanced system settings
Click environment variables
In the box, find 'Path' under system variables. Select it and click Edit
Now, Paste your SDK path in the Variable Value after a ; (It should be something like this C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;I:\Android SDK\platform-tools Click OK
Done, close the boxes and windows.
Now time for validation. To verify if you've setup the system correctly.
Get your phone and goto Settings>About Phone.
Tap on Build Number 7-10 times (until it says 'You are a developer'), You've enabled developer options.
Goto Settings> Developer options.
Under Debugging, tick USB DebuggingClick OK.
Connect your phone to your PC (on a USB 2.0 port). It might install some drivers, let it finish.
Now open the command prompt on your PC.
Type
Code:
adb devices
.
You will get a prompt on your phone to authorize. Tick 'Always Allow from this computer' And click OK.
It will show the device ID followed by 'device'.
Done, your system is ready.​
IMP: If you encounter some errors. Check Troubleshooting.​
Facts - Bootloader & Recovery & Rooting.
Bootloader
Bootoader is a small code that reside in your device. When your phone is turned ON, it loads all the hardware and the software of your device and make your phone come alive.
Locked BL & UNLocked BL: Locked BL is a little insurance (for most users)for your device. It checks everything your system can flash(install) thus helps to keep it safe from unwanted or corrupted files. This sounds cool at beginning but is a nightmare for developers. This means there is no way to rewrite the stock recovery of your phone and limiting the things you can do with it(bye bye custom ROMs).
Unlocked BL on the other hand allows to rewrite the recovery (almost everything) on your phone with a custom one, but it also include the risks(everything good, comes with a price). You Lose your warranty (permanently) and your phone is vulnerable to bricking.
Its totally your choice if you want to unlock your BL or wish to remain on stock.​Recovery
Then we have the Stock Recovery, this little part of your phone is also locked and cannot be removed or changed from your phone, it will allow you to make Recovery stuff like Full Wipe (Data and Cache) and install Update.zip(specific only) files.
A custom recovery is a special recovery. This allows Android Phones to do recovery tasks, like deleting data, installing recovery Zips and so on; The tasks you are allowed to do with Stock Recovery are pretty basic. Here is where TWRP comes into play.
TWRP is a Recovery that allows you to not only do basic tasks but also create Backups, Restore Them, Fix Permissions and quite a lot of other useful stuff like flashing Custom ROMs.
A Custom Recovery is installed by flashing the Recovery Partition in your Android Phone with a Custom Image.
Most importantly and commonly, Recovery is used to flash update.zip files. These files could be anything from ROM zip to apps,or certain modified system files. Whenever you see the term, "Recovery flashable", this is what meant by it. They are always in *.zip format.​Rooting.
So, what’s rooting and why everyone talks about it.
Phones come “locked” , this means users can only do basic usage of their phones, installing/uninstalling apps, wallpapers and basic stuff. You can see but not touch any System file, or change the actual behavior of Android. Rooting just means you have access to your phone like an Administrator(in windows) or SuperUser(in linux), meaning you can access and change system files, delete/create files and folders and so on.
Rooting simply involves giving user rights to modify system, this is done by pushing (installing) 'su' binary into system. This can only be done by a Custom recovery and needs unlocked Bootloader. There are other methods to push 'su' binary to android system but none of those work as of now for Moto E. Unlocking BL and flashing through TWRP is the only method available. ​Beginning the workout
So now that you know your phone and the terms, you can begin modding it. The process followed is simple:
Unlock your Bootloader
Flash a custom Recovery
Flash Root binary
Flash the custom ROM (Optional)
Unlocking your Bootloader:
This is the first step for modding.
IMPORTANT: Unlocking your Bootloader will void your warranty permanently(Not applicable to EU users.). You cannot claim your warranty once you request the unlock key. No matter if you don't unlock, relock it or the issue is unrelated to Bootloader. That is Motorola Policy.
Also, all your apps, data, photos,music on your internal memory will be wiped make sure to back it up before proceeding.
You can follow the Guide to unlock BL by @Falcon G
[GUIDE]Unlock Bootloader - Moto E
It is well detailed.​Flash Custom Recovey
After you have unlocked your Bootloader, you can flash a Custom recovery.As of now, TWRP & CWM are available for Moto E
You can easily flash it using the TWRP manager app from play store (not tested) Play Store Link
Or you can flash the recovery manually:
Manual Flash:
Download TWRP from TWRP.. Or ClockworkMod from this thread.
If its an *.img file then rename it to recovery.img . If its compressed archive (*.zip or *.tar) then extract and rename it.
Boot you phone into fastboot mode. (See tips)
Connect you phone to PC
Goto the folder where you extracted your recovery. Shift+Right Click, select 'Open Command Prompt Here'.
Type in command prompt
Code:
fastboot flash recovery recovery.img
(it should give a partition size mismatch error, don't worry about it)
Reboot.
Done.
Root
You have a custom recovery, now you can flash the root package.
You can check this thread for root, or follow the procedure below.
Download the SuperSU from this thread. DO NOT Extract it.
Copy the .Zip file to your phone. (Internal sdcard recommended)
Boot into recovery(See Tips)
Chose, flash Zip from sdcard
Chose the zip file you copied and confirm
Reboot
Done. You are now rooted. Check the phone it should have the SuperSU app.
[Optional] Flashing a custom ROM
Finally, you can flash your desired Custom ROM.
IMP: Please DON NOT ask for recommended/best/stable ROM in this thread or anywhere in the Forum. It is against forum rules
Make a complete Backup, Most important, in case you get into some error, you'll need it to recover.
You will lose your apps in the process when you wipe /data. So backup your apps too.You can use Titanium Backup or any other app from Play Store.
Download the required ROM from Dev section.(Make sure you have the correct ones depending your variant)It should be a *.zip file. DO NOT extract.
[Optional] Download Gapps. Make sure you have the ones for KK.It should be a *.zip fil as well. Again, DO NOT extract.
Download any add-ons required (like the dual-sim fix for CM)
Copy the files to your sdcard root directory, or any folder just remember it(internal recommended, however external will also work fine)
Boot into recovery.
Make a backup. Chose backup & restore amd create a complete backup.
Wipe /data /cache /dalvik cache.In case you are updating the same ROM, like flashing a nightly, you can skip wiping /data and only wipe /cache and /dalvik cache.(just for reference it is called dirty flashing).
Select 'Install zip from sdcard', navigate to the ROM .zip and select it. Let it finish.
Similarly, flash any Add-ons you have like gapps.
Reboot. First boot will take some time, be patient.

Tips and Troubleshooting
Commands can be entered via command prompt after you've setup the ADB. However, if you don't want to connect to your PC for a simpe command, download Terminal Emulator from Play Store.
Boot into Bootloader
ADB
type into cmd
Code:
adb reboot bootloader
Terminal
Code:
reboot bootloader
Manually
Power off,
Hold Power+VolUp+VolDown​
In Bootloader, VolDown is used to scroll, VolUp is used to select​
Boot into Recovery
ADB
Code:
adb reboot recovery
Terminal
Code:
reboot recovery
Manual
Power Off.
Hold Power+VolUp+VolDown
Scroll to recovery by using VolDown
Select Recovery by pressing VolDown​
Move your App Data to sdcard using Link2SD (Coming Soon)
Flashing back your stock ROM.
Follow this guide.
[GUIDE] Restore Moto E Stock Firmware.

Manualy updating official 4.4.4 with TWRP.XT1022
Requirements: Unmodified Stock 4.4.2. Your system shouldn't be modified. All your system apps should be present & unmodified. Doesn't matter if you're rooted or have TWRP. If you have some stock files missing, either restore a nandroid if you have or flash stock ROM. Just follow troubleshooting steps.
Troubleshooting:Fixing fie verification error due to modified system files.
Extract your stock ROM
Boot to fastboot mode (bootloader)
Flash these files ONLY
Code:
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
This will restore your system to stock without afecting Recovery or user apps.
Reboot
Now continue with flashing the update
Thanks to @Deadly for verifying this method.​
Flashing the Update .zip
Method 1: A little difficult,involves manually replacing the updater script, apt for advanced users
If you already have the original OTA file (Either extracted or downloaded)
Download the updater script from here. updater script
Either extract the .Zip file or use a file manager to navigate to META-INF>com>google>android
replace the updater script by the modifed one. Rezip if you've extracted (7-Zip recommended with 'store' compression)
Copy the zip to your sdcard or external card.
Boot into Recovery(TWRP)
Wipe Cache & Dalvik
Select Install
Select your Zip file and confirm.
Reboot
Done.
Method 2:.Easier method and ready to flash zip
If you haven't downloaded the OTA or don't mind downloading an additional file (~60 MB)
Download file .Blur.Zip
Copy the zip to sdcard (internal or external)
Boot to recovery
Wipe cache and Dalvik
Select Install.
Select the Blur.zip
Reboot
Done.
​
IMP:
Flashing will take a few minutes so be patient.
Some users have reported that after OTA custom recovery doesn't stick(unconfirmed as of now).
If you flash it using TWRP, your custom recovery will be intact and you can re-root.
Thanks to @Gogeta for providing the OTA Zip file.

Nice Guide I'll reserve one here for future

Nice job man.

Falcon G said:
Nice Guide I'll reserve one here for future
Click to expand...
Click to collapse
Hetalk said:
Nice job man.
Click to expand...
Click to collapse
Thanks guys. Remind me if I've missed something.

Any tips on SIM Unlock method
neo.ank said:
Thanks guys. Remind me if I've missed something.
Click to expand...
Click to collapse
I have rooted Moto E but with SIM Lock. Any custom ROM can remove this?

orionmb said:
I have rooted Moto E but with SIM Lock. Any custom ROM can remove this?
Click to expand...
Click to collapse
Not likely. Though it depends on the type of lock it has.
BTW, whats your variant and your carrier.?

neo.ank said:
Not likely. Though it depends on the type of lock it has.
BTW, whats your variant and your carrier.?
Click to expand...
Click to collapse
I have XT1021 and locked to O2 UK. Cannot find anyone from the paid services who can provide the unlock code so decided to root and investigate if its possible this way. Running CM11 (4.4.4).

A much appreciated thread. Good work buddy! :good::highfive:
But a clarification is regarding warranty:
neo.ank said:
Unlocking your Bootloader:
This is the first step for modding.
IMPORTANT: Unlocking your Bootloader will void your warranty permanently. You cannot claim your warranty once you request the unlock key. No matter if you don't unlock, relock it or the issue is unrelated to Bootloader. That is Motorola Policy.
Also, all your apps, data, photos,music on your internal memory will be wiped make sure to back it up before proceeding.
​
Click to expand...
Click to collapse
While Indian customers will deinitely loose warranty if they've rooted or unlocked the boot-loader, I don't think it's applicable to EU customers. Please look here for more information.
Please make the appropriate changes if I'm right. Cheers!

orionmb said:
I have XT1021 and locked to O2 UK. Cannot find anyone from the paid services who can provide the unlock code so decided to root and investigate if its possible this way. Running CM11 (4.4.4).
Click to expand...
Click to collapse
You will need the unlock code. Flashing a ROM wouldn't unlock it.
Perhaps the paid unlock services haven't listed it yet.It might be available in near future. Can't say anything for sure.
Ex-Hunter said:
A much appreciated thread. Good work buddy! :good::highfive:
But a clarification is regarding warranty:
While Indian customers will deinitely loose warranty if they've rooted or unlocked the boot-loader, I don't think it's applicable to EU customers. Please look here for more information.
Please make the appropriate changes if I'm right. Cheers!
Click to expand...
Click to collapse
Added to the guide. :good:

Added manually flashing OTA for XT1022 using TWRP

neo.ank said:
Added manually flashing OTA for XT1022 using TWRP
Click to expand...
Click to collapse
Thank you for the extensive guide and update instructions.
So I should flash stock ROM, then flash TWRP
then the update.
Is it correct process.?

coefficientoffriction said:
Thank you for the extensive guide and update instructions.
So I should flash stock ROM, then flash TWRP
then the update.
Is it correct process.?
Click to expand...
Click to collapse
Yes you are absolutely right.

neo.ank said:
Yes you are absolutely right.
Click to expand...
Click to collapse
I'm flashing stock ROM now. I will post the result after trying your file.

Its not working....It shows failed using step 2... !!

dubai1991 said:
Its not working....It shows failed using step 2... !!
Click to expand...
Click to collapse
Which method did you use.?
And can you post the exact error you got.? at which step.?

it fails while verifying the zip file. tried with unticking the zip file verification and error is binary error... !!!
---------- Post added at 08:04 PM ---------- Previous post was at 07:58 PM ----------
Method 2.. Zip file verification failed.

dubai1991 said:
it fails while verifying the zip file. tried with unticking the zip file verification and error is binary error... !!!
---------- Post added at 08:04 PM ---------- Previous post was at 07:58 PM ----------
Method 2.. Zip file verification failed.
Click to expand...
Click to collapse
Is your system unmodified.?
Have you modified or removed any system app?

Where is the Ota update zip....
Sent from my XT1022 using XDA Premium 4 mobile app

[TUT] Install [FireOS 5.4.0.1], ROOT & GAPPS

Update13, Oct 23, 2017: Everything still works with the latest 5.4.0.1, just grab the correct ROM file
Update12, Jul 23, 2016: Upgraded to FireOS 5.3.1, everything went smooth. It's not clear yet if 5.3.1 can be safely downgraded to 5.1.2 in order to get root. Stay put until we get some confirmation! It has been reported that the downgrade from 5.3.1 to 5.1.2 bricks the Fire HD!!! So downgrade to FireOS 4.5.3 instead, root, quickly turn off the WiFi, and then use this guide to go back to 5.3.1 (and do use 5.3.1 bootloaders!):
http://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
Update11, Apr 29, 2016: I installed the new 5.1.2 build from Mar 30, 2016 via the instructions below (using TWRP), and everything worked fine. This version is not rootable by Kingroot (yet). One good option (if you have this version now) is to sideload via the stock recovery the rootable 5.1.2 from Feb 26 https://kindle-fire-updates.s3.amaz...HBV/update-kindle-20.5.4.2_user_542168620.bin , and then run Kingroot. See Update10 for other tips on what to do.
Update10, Apr 8, 2016: According to the reports, the stock 5.1.2 (Feb 26, 2016 build) is rootable via Kingroot (update to 5.1.2 via the standard Amazon procedures, try Kingroot several times). Block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_ . Then you can install GAPPS as per these instructions : http://forum.xda-developers.com/showpost.php?p=65405511&postcount=268 Note that you will still benefit if you follow this guide: install TWRP, and reinstall 5.1.2 via the steps below and get all the Android goodies loaded at once (including Xposed) on an entirely clean /system partition with no Kingroot files.
Update9, Mar 21, 2016: The instructions below are updated for 5.1.2 . Kingroot does not work under 5.1.2, use adb sideload to 4.5.3 to get root! It seems that 5.1.2 has a bug where /sdcard is not visible for root (the issue seems to be this newer SuperSu version, not FireOS 5.1.2 ... I went back to SuperSu 2.46, and now it works as before). To be on the safe side, I modified scripts in post #2 to work with the newer SuperSu as well (but I don't recommend this newer SuperSu version ...) . According to a report, 5.1.1 bootloaders can be run after 5.1.2 without bricking. Regardless, here, all the bootloaders will be kept as 5.1.1 just to be sure
Update7, Feb 13, 2016: Instructions for the latest 5.4.1 update file (FireOS 5.1.1 -Bellini - with "blue shade") - Note that the instructions can be confusing, don't rush if you are not sure what you are doing (and especially if your Amazon warranty already expired) !!!
Update6: Since early Oct, there is a new evil (!!!) update named here as 5.2.2u2 (which bricked a few Fires), but thankfully the update glitches has been worked out!!! Back to business !!! Observe that once you booted 5.2.2u2 bootloaders (either through the Amazon update or the procedure below), there is no going back !!! The only other bootloaders you can run at this point are 4.5.3 as per post #2
Update4: Please do not deviate from the instructions, and do flash GAPPS during Step 1), together with Xposed. JMZ tool for installing GAPPS is not recommended!
For lazy ones I recommend skipping factory reset in Step 1) below if you already have Lollipop.
Install instructions.
Unless you have 4.5.3 bootloaders and TWRP at the moment, your path into TWRP goes via post #2 (and you do need TWRP to proceed!!!). No need to fear, I have made a simple script to flash 4.5.3 bootloaders and TWRP in just one click, see section "101" in post #2 !!!
Before proceeding, please write down your current FireOS version, and its date. To install the latest Lollipop you can pretty much start anywhere, these are rough suggestions how to get TWRP running in the quickest way possible :
unrooted Lollipop, pre-5.1.2 or 5.1.2, root via KingRoot (try several times), use post #2 for TWRP, re-load 5.1.2 from TWRP by following this post
unrooted Lollipop, alternative option, (note the version you have!!!), downgrade to 4.5.3 via stock recovery ADB sideload option (block updates immediately!!!), root 4.5.3, use post #2 to install TWRP
already rooted Lollipop, use post #2 to boot into TWRP, the bat script in section "101" is recommended (and can do a clean re-install of your current Lollipop version with the same procedure if you care)
rooted FireOS 4.5.x (latest Kingroot is known to root either 4.5.3 or 4.5.5.1, perhaps 4.5.4 & 4.5.5 as well) -then post #2 (if the bootloaders are not 4.5.3)
unrooted 4.5.x (>4.5.3 such as 4.5.4 or 4.5.5 but pre-4.5.5.1): disable OTA, run latest Kingroot, report back if failure, use post #2 for TWRP
unrooted whatever - write directly into memory 4.5.3 bootloaders & TWRP (somewhat slow, but can be an attractive option if you cannot root your version of Lollipop directly, and don't want to factory reset the device memore during the downgrade to 4.5.3 in order to root) :
http://forum.xda-developers.com/fire-hd/development/unbrick-fire-hd-6-7-flashing-lollipop-t3405797
0) Before proceeding, ensure that you have a functional non-system launcher (install any as user app), or enable the stock Amazon launcher via adb if it's blocked (pm enable com.amazon.firelauncher) !!! Make sure it works. This will ensure that you can avoid problems later on when the /system partition is overwritten, and your non-Amazon launcher that was installed as a system app is gone. I had Nova as the system app (overwritten by the upgrade!), and Amazon launcher blocked, so after the upgrade to 5.1.2 there was no working launcher. Not good ... Had to do a couple of system resets and TWRP restores until I figured out what was happening ...
1) boot into TWRP, and, in a single session (!!!!!)
(Optional) clear cache/dalvik (to shrink the backup size), run TWRP backup to a USB drive via USBOTG cable for your /data partition
(Optional) do factory reset (can skip if you already have Lollipop),
flash the latest FireOS from this official Amazon link (rename *bin to *zip such that TWRP can recognize it):
https://www.amazon.com/gp/help/customer/display.html?nodeId=201596850
If for some reason you need a different FireOS version, grab the file you need from the links in this post.
flash 5.2.0_stock_recovery_only.zip below. If you kept track of your prior FireOS versions and know what you are doing, you can flash
5.4.1_1133_stock_recovery_uboot.zip from post #2 (this will flash 5.2.0 stock recovery & 5.4.1 bootloaders). Note that if you downgraded from FireOS 5.3.1 to 4.5.3 to root, you must flash 5.5.2_1534_stock_recovery_uboot.zip instead, this will put the required 5.3.1 bootloaders back.
flash the attached make_space_v02.zip (this will remove moffice and weather to make room in /system for GAPPS , can always install this stuff from Play Store)
flash Supersu.zip https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
flash Xposed for Lollipop 5.1 (if you want it for misc modules, highly recommended to do this just in case)
http://forum.xda-developers.com/showthread.php?t=3034811
(version xposed-vXX-sdk22-arm.zip )
flash Pico (Uni) GAPPS for 5.1 :
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
clear cache/dalvik in TWRP
Another reminder: If you are absolutely sure that you have never run FireOS 4.5.5.1 bootloaders or Lollipop with anything but 5.2.0 bootloaders, you can flash 5.2.0_stock_recovery_uboot.zip from post #2 here, this way you preserve the well behaved 5.2.0 bootloaders. If you are not sure about any of this, don't do it !!!
2) reboot to recovery, you should see stock 5.2.0 recovery (this is just to see if it works, for troubleshooting, but otherwise a meaningless step from the update perspective ...). Notice that at this point you no longer have TWRP. Since it does not boot with the 5.x bootloaders anyway, TWRP was replaced with the stock recovery that has some useful features, such as adb sideload. Later on it's possible to get back into TWRP from within the rooted Lollipop by following post #2.
3) reboot to Lollipop (takes ~15 minutes), and hopefully, it works.
Bricking warning !!! If you flashed the wrong bootloaders, and you get a black screen upon reboot, there is good news - you can UNBRICK !!! The bad news is that the procedure is quite involved, and may take quite a bit of effort. So measure twice, cut once !!! If unsure about bootloaders, ask here first before flashing, instead of coming back to complain about the brick later.
4) if step 3) fails, you get into working 5.2.0 recovery by pressing "Pwr & Vol+". At this point you sideload 4.5.3 stock, and go back to step 0). Come back here and ask questions (and thank me again for being able to recover so easily !!! )
5) make_space_v02.zip already disabled OTA updates , but please verify that you now have DeviceSoftwareOTA.apk_ block OTA updates (to prevent surprises): In Explorer go to /system/priv-app/DeviceSoftwareOTA and rename DeviceSoftwareOTA.apk to .apk_
6) Consider adding an option to switch from pure Amazon interface to almost pure Android and back on the fly:
http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
Note: Using JMZ tool for installing GAPPS is not recommended, please flash GAPPS as per Step 1)
The next post discusses how to get into TWRP temporarily with Lollipop installed, and come back to Lollipop
Want to say thanks by clicking the "Thanks" button ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Higher skill level operation - proceed with care !!!
Update3.5 : Updates for 5.3.1 !!! Please use 5.5.2_1534_stock_recovery_uboot.zip if you downgraded from stock FireOS 5.3.1 to 4.5.3 for rooting, meaning that you now have 5.3.1 bootloaders
Update3.4 : Updates for 5.1.2 !!! Please use the new WindowsAutoTWRP_v03.zip with 5.1.2 (backward compatible to 5.1.1 and before). There are tons of verification messages in the new script, please read carefully !!! It appears that in 5.1.2 there is a bug such that root cannot see /sdcard/gscript properly (this was the issue caused by the latest SuperSu I tried). To handle this, I redirected the path to /data/media/0/gscript . If you are using Gscript, delete the flash_453(_stay) scripts in Gscript, and open them again after you run WindowsAutoTWRP_v03 once. This way Gscript will pick up the corrected scripts with the updated path. Pay attention to the checksums !!!
Update3.3 : And now "Newbie Friendly" !!! Just one simple *.bat script under Windows !!! See section "101"
Update3.2 : If you are unsure what bootloader file to use, go with 5.4.1_1133_stock_recovery_uboot.zip
Update2: If you ever booted the Sept 2015 Lollipop (FireOS 5.0.1, called here 5.2.2u2), DO NOT use 5.2.0_stock_recovery_uboot.zip , it will brick!!!
Update1: Instructions are clarified with more detail on how to use "dd" correctly.
Important : do not try to use Flashify!!! Flashify cannot access all partitions that you need to flash !!! Flashify will brick your Fire !!!
Here you get to run TWRP again, and then return to Lollipop.
The steps must be executed with precision (all 3 files must be dd'ed successfully). Keep the 5.4.1_1133_stock_recovery_uboot.zip file from below on the device, in its /images directory you have 3 images for 5.4.1 which you can flash back right away if you need to abort. If something is wrong, DO NOT reboot for as long as it takes. Keep the device without reboots, and come back here for guidance.
To understand a bit what we are doing in this post, read this :
A bit of background. Fire HD boots TEE1 -> UBOOT -> recovery. With 4.5.3, we lucked out that TEE1 & UBOOT accepted unsigned recovery (aka TWRP). No such luck with 5.2.x - TEE1 & UBOOT expect signed recovery (for example, stock one). That's why I had everybody overwrite TWRP with stock recovery in post #1 as the last step in the upgrade. Otherwise after the upgrade to 5.2.x, TWRP would still be sitting in recovery, and being unsigned, it cannot boot !!! A few bricks were created because of this last point. But with the stock 5.2.0 recovery (which it will boot), at least there is an option to sideload another update file.
So, the key to running TWRP while in 5.2.x is to overwrite the 3 key components together (TEE1, UBOOT, recovery), and then return things to 5.2.x once TWRP is no longer needed.
For convenience, before proceeding save all the attached files on your Fire in "/sdcard/gscript"
101 - Automatic installation under Windows !!!
I managed to debug it and not to brick !!! Tested personally (gotta eat your dog food !!!) Heavily inspired by glitch3yf0x in http://forum.xda-developers.com/amazon-fire/general/root-playstore-busybox-optimize-flash-t3281804
Save the necessary Lollipop bootloaders zip into /sdcard/gscript on Fire HD, this will get you back into Lollipop
Download WindowsAutoTWRP_v03.zip to your PC with some Windows on it, unpack anywhere
Run the commands below, and make sure you authorize root access for adb when the question pops up on your Fire:
Code:
adb shell
su
exit
exit
Enable apps from unknown sources
Run 1_FIRE_HD_4TH_GEN_TWRP.bat
At the bottom you should see these checksums :
Code:
3a1f3cd1ef405eaeec719eaeb41ab791 /dev/block/mmcblk0p3
d605e31a180652c65d6957b58d2d8501 /dev/block/mmcblk0p5
305a5546ff8960b51cd573b59a05cde6 /dev/block/mmcblk0p7
Make sure the checksums are correct before rebooting !!! Do not reboot if checksums are wrong, keep the Fire running, and come back here to ask questions !!! I almost bricked under 5.1.2 due to the newer SuperSu version, but managed to catch the wrong checksums, and updated the scripts to have additional verifications.
A possible issue here is that you did not have root access, so the "dd" commands could not succeed. At this point you can go to method A since the script left all the necessary ingredients on the device, so all you need to do is to run the script from Gscript (installed for you!), make sure you click "needs SU". Delete the old flash_453 and flash_453_stay scripts from Gscript, and re-open them again after you run WindowsAutoTWRP_v03 at least once.
Verify again that you have 5.x.x bootloaders zip file on Fire HD which you will access from TWRP (it can also be on a USB drive if you got USB OTG cable) - Out of kindness I've provided the most popular bootloaders zip at the moment - 5.4.1 version, you can find it in /sdcard/gscript, it's TWRP ready, just flash it if 5.4.1 is OK for you (5.4.1 bootloaders will also work with FireOS 5.1.2 )
Type "adb reboot recovery"
In TWRP, after you are done with everything, don't forget to flash the 5.x.x bootloaders zip file in order to boot back into Lollipop!
After the batch file runs, you will have Gscript installed, together with the required script & image files in /sdcard/gscript, so you can head over to the next section (section A), and set up TWRP access without using a PC! You will also have scripts in there to enable/disable Amazon's stuff on the fly, as described in here :
http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
A - Instructions with Gscript.
Due to popular demand (looking at DoLooper here ), the approach is simplified and all the bootloaders are flashed via a script, and this assumes that you have Gscript installed (here : https://bitbucket.org/Equidamoid/gscript/downloads )
Download the attached "453_key_images.zip" to your Fire, create a folder (if does not exist) "/sdcard/gscript", and unpack this zip file in "/sdcard/gscript" (so all *bins sit in this directory)
[*]Download the attached "flash453.zip", copy to "/sdcard/gscript", unpack
Run the bat from WindowsAutoTWRP_v03 in section "101" at least once
Go to Gscript/Add script/Need Su (yes, check)/Load file "flash_453_stay.sh"
From Gscript run this "flash_453_stay.sh", and verify the checksums
If you are using versions prior to FireOS 5.1.2, you can use "flash_453.sh" and you should end up in TWRP (it will reboot automatically)
If unhappy about auto-reboot, use "flash_453_stay.sh" script, it will only do "dd" and exit back to the current OS (no auto-reboot to recovery)
B - Alternative (old) instructions via ADB
Download the attached "453_key_images.zip" to your Fire, create a folder "/sdcard/gscript", and unpack this zip file in "/sdcard/gscript". From the PC side, open ADB and start typing :
adb shell
su
cd /sdcard/gscript
ls
dd if=453_tee1.img of=/dev/block/mmcblk0p3
dd if=453_uboot.img of=/dev/block/mmcblk0p5
dd if=453_twrp.img of=/dev/block/mmcblk0p7
exit
exit
adb reboot recovery
These are 4.5.3 bootloaders, and TWRP. Just like in the good old days under FireOS 4.5.x
This is a sample log, your output should look similar (typed commands are colored in red) :
C:\Program Files\Minimal ADB and Fastboot>adb devices
List of devices attached
0000000000000XXX device
C:\Program Files\Minimal ADB and Fastboot>adb shell
[email protected]:/ $ su
su
[email protected]:/ # cd /sdcard/gscript
cd /sdcard/gscript
[email protected]:/sdcard/gscript # ls
ls
453_key_images.zip
453_tee1.img
453_twrp.img
453_uboot.img
[email protected]:/sdcard/gscript # dd if=453_tee1.img of=/dev/block/mmcblk0p3
dd if=453_tee1.img of=/dev/block/mmcblk0p3
6364+1 records in
6364+1 records out
3258876 bytes transferred in 0.543 secs (6001613 bytes/sec)
[email protected]:/sdcard/gscript # dd if=453_uboot.img of=/dev/block/mmcblk0p5
dd if=453_uboot.img of=/dev/block/mmcblk0p5
414+1 records in
414+1 records out
212116 bytes transferred in 0.041 secs (5173560 bytes/sec)
[email protected]:/sdcard/gscript # dd if=453_twrp.img of=/dev/block/mmcblk0p7
dd if=453_twrp.img of=/dev/block/mmcblk0p7
14004+0 records in
14004+0 records out
7170048 bytes transferred in 1.103 secs (6500496 bytes/sec)
[email protected]:/sdcard/gscript # exit
exit
[email protected]:/ $ exit
exit
C:\Program Files\Minimal ADB and Fastboot>adb reboot recovery
Click to expand...
Click to collapse
Reboot into recovery, and you should be in TWRP.
C - What am I doing in TWRP ???
-- Well, you tell me
Generally, you want to flash something (Xposed, GAPPS?). Keep flashing whatever else you need! Note that at this point you won't be able to boot into 5.2.x, siegesoldier has established this fact with his early upgrade attempts. 4.5.3 bootloaders will not boot 5.2.x kernel due to some missing parameters !
When you want to go back to Lollipop, in TWRP flash the attached 5.4.1_1133_stock_recovery_uboot.zip (or 5.5.2_1534_stock_recovery_uboot.zip). This will put 5.4.1 (or 5.5.2) bootloaders back, as well as 5.2.0 stock recovery. Note if you are sure that you never had 5.4.1, 5.2.2u3 or 5.2.2u2 bootloaders running (or stock FireOS 4.5.5.1), use 5.2.0_stock_recovery_uboot.zip (this is rare now, be very sure !!!) If you forget to flash the 5.x.x bootloaders, the device will cycle upon reboot with the Amazon logo continuously. This is not a big issue ! Just hold the power button until the Fire shuts off. Then from the turned off state turn it on by pressing power and Vol+ buttons together, and this will get you back into TWRP where you can flash the 5.x.x bootloaders and reboot to Lollipop.
Now reboot to system, and you should have your Lollipop
Want to say thanks by clicking the "Thanks" button ?

bibikalka said:
. . . and finally, when TWRP asks you to install root, say "yes" . . .
2) reboot to recovery, you should see stock 5.2.0 recovery.
Click to expand...
Click to collapse
Yahoo! I'm either almost there or am no longer rooted. adb shell, su doesn't return #-sign, but I can "cd" and "ls" all around /system. SuperSU installer says I'm "not fully rooted," but if you press Play (store) Amazon wants to open appstore of course, and no TWRP. Tried adb install, which failed:
Desktop>adb install eu.chainfire.supersu.apk
3017 KB/s (5904943 bytes in 1.911s)
pkg: /data/local/tmp/eu.chainfire.supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]​Guess I'm partially rooted? Need some reassurance because had a little trouble flashing (which I won't explain unless I must) . Anyway, I have 5.2.0 recovery and if superuser is as expected, I'll go for post 2 (i think)! Thanks!

Managed to get the upgrade from reading the last thread, but no TWRP. Thanks!!
DoLooper said:
Yahoo! I'm either almost there or am no longer rooted. adb shell, su doesn't return #-sign, but I can "cd" and "ls" all around /system. SuperSU installer says I'm "not fully rooted," but if you press Play (store) Amazon wants to open appstore of course, and no TWRP. Tried adb install, which failed:
Desktop>adb install eu.chainfire.supersu.apk
3017 KB/s (5904943 bytes in 1.911s)
pkg: /data/local/tmp/eu.chainfire.supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]​Guess I'm partially rooted? Need some reassurance because had a little trouble flashing (which I won't explain unless I must) . Anyway, I have 5.2.0 recovery and if superuser is as expected, I'll go for post 2 (i think)! Thanks!
Click to expand...
Click to collapse
This happened to me as well... the su binary was in /system/xbin but wasn't working, and the app said I had to flash or install from the Play Store. I copied the Superuser.apk to /sdcard and installed it device side, worked fine.

Yes! thx! (Can easily get es file explorer from appstore for this.)

Thanks for this bro! I can confirm this process works, and I will show the steps I took here (clarification for people who want to do this).
1. I started on 4.5.4 + Root + TWRP with adb installed on my Mac
2. I connected fire to computer, and did (in terminal window)
adb backup -apk -shared -all ~/Downloads
to save my data before factory reset (this should work on Mac + Linux).
3. Rebooted to TWRP
4. Performed a Factory Reset (the default one under Wipe on TWRP)
5. Installed the 5.2.0 bin file with adb sideload
6. Installed 5.20 stock recovery with adb sideload
7. Went to Reboot page and chose reboot recovery
8. TWRP will prompt you to install root, do it
9. It will then reboot into stock Amazon recovery, choose to reboot your system
10. Mine took forever, but it finally booted into 5.2.0
11. If you're plugged into the computer, it gives you the option to enable usb debugging, do this
12. I completed the setup process
13. Downloaded SupersSU from here on computer
14. Used
adb install -r supersu.apk
(or whatever your's is named)
15. Check you have root by running
adb shell
su
16. You should have root installed!
17. Now run
adb restore backup.ab
which will restore your data (apps)
18. SKIP UNLESS YOU HAD XPOSED INSTALLED If you had Xposed installed, it is not compatible now, so uninstall all of your modules (if you want to save space). I believe the problem with Xposed is that we need to change a build.prop sdk/api value, but that's something for us to figure out later.
19. Install jmz fire tools from here
20. Run it and choose install Gapps, your device will reboot
21. Sucess!!! Lollipop + Root + Gapps
Anyways, good luck to everyone I hope this helps someone in the future!
---------- Post added at 10:33 AM ---------- Previous post was at 10:32 AM ----------
DoLooper said:
Yahoo! I'm either almost there or am no longer rooted. adb shell, su doesn't return #-sign, but I can "cd" and "ls" all around /system. SuperSU installer says I'm "not fully rooted," but if you press Play (store) Amazon wants to open appstore of course, and no TWRP. Tried adb install, which failed:
Desktop>adb install eu.chainfire.supersu.apk
3017 KB/s (5904943 bytes in 1.911s)
pkg: /data/local/tmp/eu.chainfire.supersu.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]​Guess I'm partially rooted? Need some reassurance because had a little trouble flashing (which I won't explain unless I must) . Anyway, I have 5.2.0 recovery and if superuser is as expected, I'll go for post 2 (i think)! Thanks!
Click to expand...
Click to collapse
pcrhckyman said:
Managed to get the upgrade from reading the last thread, but no TWRP. Thanks!!
This happened to me as well... the su binary was in /system/xbin but wasn't working, and the app said I had to flash or install from the Play Store. I copied the Superuser.apk to /sdcard and installed it device side, worked fine.
Click to expand...
Click to collapse
I fixed this by running
adb install -r eu.chainfire.supersu.apk
or whatever your supersu file is named.

Easy TWRP and Gapps?
bibikalka said:
OK, here the risk is pretty simple - likely brick. On the upside, you get to run TWRP, and then return to 5.2.0.
Click to expand...
Click to collapse
Remolten said:
I fixed this by running adb install -r eu.chainfire.supersu.apk or whatever your supersu file is named.
Click to expand...
Click to collapse
Yep, still learning, and thanks for the detailed steps.
Why not adb install (or file explorer install) Flashify or TWRP manager, install TWRP, and then Gapps? Or for that matter, use Flashify to install Gapps? Thanks.

As far as GAPPS, go the lazy way of using JMZs app just worked for me. I'll be removing the modifications that prevent the apps from updating shortly. But the old playstore works fine on lolipop.

DoLooper said:
Yep, still learning, and thanks for the detailed steps.
Why not adb install (or file explorer install) Flashify or TWRP manager, install TWRP, and then Gapps? Or for that matter, use Flashify to install Gapps? Thanks.
Click to expand...
Click to collapse
I don't think the Flashify method works, but I will try it.
EDIT: Flashify requires custom recovery
EDIT 2: Trying siegesoldier's method
EDIT 3: We have a winner! Thanks siegesoldier and jmz!

siegesoldier said:
As far as GAPPS, go the lazy way of using JMZs app just worked for me. I'll be removing the modifications that prevent the apps from updating shortly. But the old playstore works fine on lolipop.
Click to expand...
Click to collapse
Thx for info, but JMZ's TWRP manager is crashing on me.

DoLooper said:
Thx for info, but JMZ's TWRP manager is crashing on me.
Click to expand...
Click to collapse
This one silly!
http://forum.xda-developers.com/fir...ool-jmz-fire-hd-7-tool-gapps-disable-t3113655

siegesoldier said:
This one silly!
Click to expand...
Click to collapse
lol thx. (Sorry for taking up more space here, but that was funny!)

FYI. Xposed is possible if you downgrade back to 4.5.3/twrp and after flashing lolipop, but before replacing recovery, flash xposed-v67-sdk22-arm-by-romracer-20150716.zip found in http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979 and install XposedInstaller_3.0_alpha4.apk once you're back into lolipop found here http://forum.xda-developers.com/showthread.php?t=3034811.

bibikalka said:
OK, fellas, 1st attempt for a reasonably safe journey to rooted Lollipop. The key now is to flash 5.2.0 recovery right after flashing 5.2.0 stock, this way there is an option to recover if something goes wrong.
Disclaimer : most of the info is compiled from other threads. Myself, I have tested flashing the attached 5.2.0 stock recovery zip from TWRP, it works fine.
Big credit here hawkazn for blazing the trail, and getting to a working rooted Lollipop first, then dumping the stock recovery:
http://forum.xda-developers.com/showpost.php?p=62009468&postcount=75
0) I assume you have TWRP installed and working, which means you've followed the guide to step 3) only, [and skip all the steps after 3) , since nobody is going to care, no extra credit here!]:
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
1) boot into TWRP, and, in a single session (!!!!!)
do factory reset,
flash the 5.2.0 update from this post (the official 5.2.0 zip will work just fine):
http://forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810
flash the attached 5.2.0_stock_recovery_only.zip
and finally, when TWRP asks you to install root, say "yes"
Let's pause for a second and realize what we did here - we've put full stock 5.2.0, added root, and, most importantly, overwrote TWRP with 5.2.0 stock recovery.
2) reboot to recovery, you should see stock 5.2.0 recovery
3) reboot to 5.2.0 OS, and hopefully, it works. Install SuperSu to manage root requests.
4) if step 3) fails, you get into working 5.2.0 recovery by pressing "Pwr & Vol+". At this point you sideload 4.5.3 stock, and go back to step 0). Come back here and ask questions.
You may be asking about GAPPS - try to install manually, as indicated here :
http://forum.xda-developers.com/showpost.php?p=62008212&postcount=71
More experimental stuff in the next post.
Click to expand...
Click to collapse
Glad I was able to help out and get it working for everyone!

Fantastic effort in a short period of time !!! The sales of HDs and "brick" returns will surely skyrocket
Also, noting the confusion with TWRP, I've updated my post #2 to explain exactly why all that stuff needs to be done to run TWRP :
http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
DoLooper said:
Yep, still learning, and thanks for the detailed steps.
Why not adb install (or file explorer install) Flashify or TWRP manager, install TWRP, and then Gapps? Or for that matter, use Flashify to install Gapps? Thanks.
Click to expand...
Click to collapse
TWRP is not signed, and will not run with the bootloader from 5.2.0 which expects a signed recovery. That's was the whole reason to do the "circus" with 3 dd's, basically, one needs to flash all the bootloaders in the chain from 4.5.3, together with TWRP to be able to boot into TWRP. After that, one would reflash back all the bootloaders and recovery back to 5.2.0 versions.
Remolten said:
I don't think the Flashify method works, but I will try it.
EDIT: Flashify requires custom recovery
EDIT 2: Trying siegesoldier's method
EDIT 3: We have a winner! Thanks siegesoldier and jmz!
Click to expand...
Click to collapse
See the above answer, to get into TWRP, you have to flash all 3 files together. But itself, TWRP does not boot from 5.2.0 bootloaders, that's why people had bricks before when they did not replace TWRP after flashing 5.2.0
siegesoldier said:
FYI. Xposed is possible if you downgrade back to 4.5.3/twrp and after flashing lolipop, but before replacing recovery, flash xposed-v67-sdk22-arm-by-romracer-20150716.zip found in http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979 and install XposedInstaller_3.0_alpha4.apk once you're back into lolipop found here http://forum.xda-developers.com/showthread.php?t=3034811.
Click to expand...
Click to collapse
Ha-ha, love Alex' 3rd Fire! Must have chewed through 2 previous ones Indeed, you can run TWRP, provided it's booted via 4.5.3 bootloaders. And after flashing 5.2.0 in TWRP, that's the last time you see TWRP booted up unless you then "dd" them back as in my post #2.
I will update that post to make these points more clear.

hawkazn said:
Glad I was able to help out and get it working for everyone!
Click to expand...
Click to collapse
Yep, thanks for making the 5.2.0 into a dull flashing experience instead of the nail biting one !!!

I am loving this good-looking and way more customizeable update! Thanks again!
bibikalka said:
That's was the whole reason to do the "circus" with 3 dd's, basically, one needs to flash all the bootloaders in the chain from 4.5.3, together with TWRP to be able to boot into TWRP. After that, one would reflash back all the bootloaders and recovery back to 5.2.0 versions.
Click to expand...
Click to collapse
If one wanted to, the 3 dds circus could still be done any time, right? So if we wanted to slap on TWRP for a quick flash we could do that?
Speaking for myself, getting Gapps turned out to be a priority once I saw lollipop on the Fire. And the "JMZ tool/allow update" method was both expedient and didn't include the phrase, "likely brick"

DoLooper said:
I am loving this good-looking and way more customizeable update! Thanks again!
If one wanted to, the 3 dds circus could still be done any time, right? So if we wanted to slap on TWRP for a quick flash we could do that?
Speaking for myself, getting Gapps turned out to be a priority once I saw lollipop on the Fire. And the "JMZ tool/allow update" method was both expedient and didn't include the phrase, "likely brick"
Click to expand...
Click to collapse
Ha-ha, true, saying "likely brick" is poor marketing. I'll rephrase it to something more benign

Disable ota on rooted 5.20
bibikalka said:
OK, fellas, 1st attempt for a reasonably safe journey to rooted Lollipop. The key now is to flash 5.2.0 recovery right after flashing 5.2.0 stock, this way there is an option to recover if something goes wrong.
Disclaimer : most of the info is compiled from other threads. Myself, I have tested flashing the attached 5.2.0 stock recovery zip from TWRP, it works fine.
Big credit here hawkazn for blazing the trail, and getting to a working rooted Lollipop first, then dumping the stock recovery:
http://forum.xda-developers.com/showpost.php?p=62009468&postcount=75
0) I assume you have TWRP installed and working, which means you've followed the guide to step 3) only, [and skip all the steps after 3) , since nobody is going to care, no extra credit here!]:
http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
1) boot into TWRP, and, in a single session (!!!!!)
do factory reset,
flash the 5.2.0 update from this post (the official 5.2.0 zip will work just fine):
http://forum.xda-developers.com/fire-hd/general/lolipop-ota-capture-t3141810
flash the attached 5.2.0_stock_recovery_only.zip
and finally, when TWRP asks you to install root, say "yes"
Thanks to Remolten, there is a very detailed write up regarding all of this:
http://forum.xda-developers.com/showpost.php?p=62018692&postcount=6
Note that this is the last time you see TWRP (unless you do what I recommend in post #2), so take an opportunity to flash other stuff such as Xposed, thanks to siegesoldier for pointing this out (not sure about GAPPS yet without at least one reboot into 5.2.0):
http://forum.xda-developers.com/showpost.php?p=62021411&postcount=13
Let's pause for a second and realize what we did here - we've put full stock 5.2.0, added root, and, most importantly, overwrote TWRP with 5.2.0 stock recovery.
2) reboot to recovery, you should see stock 5.2.0 recovery (this is just to see if it works, for troubleshooting, but otherwise a meaningless step from the update perspective ...)
3) reboot to 5.2.0 OS, and hopefully, it works. Install SuperSu to manage root requests.
4) if step 3) fails, you get into working 5.2.0 recovery by pressing "Pwr & Vol+". At this point you sideload 4.5.3 stock, and go back to step 0). Come back here and ask questions.
You may be asking about GAPPS - install them via JMZ tool, there are reports that everything works just fine:
http://forum.xda-developers.com/fir...ool-jmz-fire-hd-7-tool-gapps-disable-t3113655
More experimental stuff in the next post, this is how to get into TWRP again with 5.2.0 installed.
Click to expand...
Click to collapse
Is it necessary to disable ota after upgrading to 5.2.0 with root? If so. How?

Brofreeman said:
Is it necessary to disable ota after upgrading to 5.2.0 with root? If so. How?
Click to expand...
Click to collapse
I'm not sure if it is required, but it is a good precaution just in case. If you install the JMZ tool, the third page has a switch to disable OTA's.

Downgrade from 7.0 to 6.0.1 for the LG G5 H850

1，unlocked bootload，https://www.gizdev.com/lg-g5-h850-twrp-3-0-rooting-guide/
2，install rec for h850 ，http://thunderztech.com/root-lg-g5-on-android-7-0-nougat-with-twrp-recovery/
3，into rec and flash LG-H85010E-Flashable.Bootloader.zip from autoprime,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
4,lg up flash 6.0.1 kdz,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
5,wipe you device by keep volume- always and power,when look lg logo,press power again and keep it ,then press yes,yes
you have downgrade to 6.0.1

xjqlfq said:
1，unlocked bootload，https://www.gizdev.com/lg-g5-h850-twrp-3-0-rooting-guide/
2，install rec for h850 ，http://thunderztech.com/root-lg-g5-on-android-7-0-nougat-with-twrp-recovery/
3，into rec and flash LG-H85010E-Flashable.COMPLETE.zip from autoprime,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
4,lg up flash 6.0.1 kdz,http://forum.xda-developers.com/lg-g5/development/stock-h850-10e-eu-rom-flashable-zips-t3448273
5,wipe you device by keep volume- always and power,when look lg logo,press power again and keep it ,then press yes,yes
you have downgrade to 6.0.1
Click to expand...
Click to collapse
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!

autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
thanks，get it

autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
I had several problems with this procedure (coming from V20a):
1. After flashing 10C BOOTLOADER ZIP via TWRP, LGUP was not able to detect my device type anymore, but this worked with previous bootloader. Why?
2. Flashing the 10C COMPLETE ZIP did result in a loss of TWRP (although recovery.img is not part if complete ZIP). Why?
3. Flashing the 10E COMPLETE ZIP caused FCs and a bootloop Reset in system recovery did help to get the device up again.
After that LGUP did find again my H850 and upgrade option works now with M KDZs (which did not work under Nougat). But the refurbish option is still not working and says "not supported".

fuxi222 said:
I had several problems with this procedure (coming from V20a):
1. After flashing 10C BOOTLOADER ZIP via TWRP, LGUP was not able to detect my device type anymore, but this worked with previous bootloader. Why?
2. Flashing the 10C COMPLETE ZIP did result in a loss of TWRP (although recovery.img is not part if complete ZIP). Why?
3. Flashing the 10E COMPLETE ZIP caused FCs and a bootloop Reset in system recovery did help to get the device up again.
After that LGUP did find again my H850 and upgrade option works now with M KDZs (which did not work under Nougat). But the refurbish option is still not working and says "not supported".
Click to expand...
Click to collapse
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.
2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.
3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.

autoprime said:
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.
2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.
3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.
Click to expand...
Click to collapse
At first: Big thanks for your quick response!!!
to 1.: The reason for 10C instead of 10E is simple: you do not have a KDZ file for 10E on your codefire drive (only a ZIP), but for 10C the KDZ was available. And the links to LG server were not working yesterday for me.
I read Uppercut the first time now and will give it a try today in the evening (German time). :fingers-crossed:
to 2.: Understood. Thank you! :good:
to 3.: Then how can I get rid of the 3 error messages on start-up related to NT-code ("Can't find matched cust for NT-code" + "OP name for Buyer-code...")? I understood, that refurbish will flash new cust partition and this will solve the problem. I see cust.img also on your drive, but it is not inluded in the COMPLETE ZIPs. Would it help to flash this?
Or can LG Bridge help in this case? It does refuse to flash my phone, maybe because of the bootloader unlock?!
I read so many threads yesterday, but nothing solved this issue... :crying::crying:

fuxi222 said:
to 3.: Then how can I get rid of the 3 error messages on start-up related to NT-code ("Can't find matched cust for NT-code" + "OP name for Buyer-code...")? I understood, that refurbish will flash new cust partition and this will solve the problem. I see cust.img also on your drive, but it is not inluded in the COMPLETE ZIPs. Would it help to flash this?
Or can LG Bridge help in this case? It does refuse to flash my phone, maybe because of the bootloader unlock?!
I read so many threads yesterday, but nothing solved this issue... :crying::crying:
Click to expand...
Click to collapse
cust should be getting flashed regardless of selecting refurbish or not as far as I know.. but perhaps I'm wrong.
if you have root/twrp just zero out the cust partition or simply delete the files inside the cust folder using a file explorer app... and the error msg should go away on next reboot.
this is in the FAQ/Q&A section in the OP of all my stock threads for H850.
if you're on M and must flash a KDZ with refurb option... just use the old LGUP methods. but if you're sticking with TWRP there's not really any need to flash any KDZ.. you can flash whatever in TWRP instead.

autoprime said:
cust should be getting flashed regardless of selecting refurbish or not as far as I know.. but perhaps I'm wrong.
if you have root/twrp just zero out the cust partition or simply delete the files inside the cust folder using a file explorer app... and the error msg should go away on next reboot.
this is in the FAQ/Q&A section in the OP of all my stock threads for H850.
if you're on M and must flash a KDZ with refurb option... just use the old LGUP methods. but if you're sticking with TWRP there's not really any need to flash any KDZ.. you can flash whatever in TWRP instead.
Click to expand...
Click to collapse
"and the error msg should go away on next reboot." I get 3 error messages related to this. Will I get rid of all of them?
"old LGUP methods" means tool version 1.11 instead of 1.14? So use version 1.11 for MM and 1.14 for N?!
Unfortunately, refurbish does not work even under MM for me regardless if I use version 1.11 or 1.14.
BTW: The old version 1.11 asks my each time I trigger the refurbish process to "Input new NT code" (the new version does not behave like this). Is my problem maybe caused by this or can this be used to input a working string there?

fuxi222 said:
"and the error msg should go away on next reboot." I get 3 error messages related to this. Will I get rid of all of them?
"old LGUP methods" means tool version 1.11 instead of 1.14? So use version 1.11 for MM and 1.14 for N?!
Unfortunately, refurbish does not work even under MM for me regardless if I use version 1.11 or 1.14.
BTW: The old version 1.11 asks my each time I trigger the refurbish process to "Input new NT code" (the new version does not behave like this). Is my problem maybe caused by this or can this be used to input a working string there?
Click to expand...
Click to collapse
i dont have an H850 so idk.. but any time ive had someone zero cust theyve said errors have gone away. so if they dont for you.. you must be special. try it and find out... then report back. if it doesnt work... ¯\_(ツ)_/¯
old lgup methods = 1.11 + dll msi installer, yes. but i see no reason to use 1.11 simply for refurbish option. most people should be able to use LGUP 1.14 + UPPERCUT for most situations on G4/G5/V20.
i dont know abotu the NT code stuff with LGUP.. again.. I dont have a H850. but if you have TWRP then there's really no need to be messing with LGUP at all unless you want to be 100% stock/unrooted with no TWRP. just zero cust or try flashing the cust.img that's in the folder.
I cant help any more on this NTCode subject without a device that uses it. good luck.

autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
Only if someone is on the same point: For me, it is only working to flash the COMPLETE ZIP! When I flash bootloader only, LGUP does not detect the model type of my device anymore (detected type is "Unknown"). I have tried it now for 2 times with similar results...
BTW: I used this method to get rid of the annoying NT code issue: http://forum.xda-developers.com/showpost.php?p=66957161&postcount=4

@autoprime Can't we just flash 10E with the refubrish option? Somehow I'm unable to get into recovery with the button combination after downgrading and updating again, even though I'm doing it properly and I was able to do it before.
EDIT: So refubrish stopped working now too. Dang. I installed the recovery through Dirty Cow, flashed the bootstack and went back to 10E, but I still don't have a recovery. ;_;
Ok, I've tried everything and button combination for recovery still doesn't work, so think if you really wanna risk being unable to easily factory reset your phone.

autoprime said:
1. I suggested 10E not 10C.. not sure why LGUP 1.14 + UPPERCUT wouldn't see it. But UPPERCUT is geared towards recent devices on recent software. It's possible 10C is too old to fall under the UPPERCUT 1.0.0.0 umbrella.. and you're always welcome to use the older LGUP methods instead.
2. You will always lose TWRP if you boot into Android without patching the boot.img or flashing supersu zip first. The stock system.img has a patch in it which always tries to replace the recovery partition with stock recovery.. and zips like supersu stop such things from happening. The procedure is to flash twrp.. boot into twrp.. flash supersu. flashing twrp then booting into android = no more twrp. this is standard android stuff for awhile now.
3. The refurbish option isn't needed and I've already explained in the UPPERCUT thread that refurbish is not supported. All refurbish option does is force the phone to run a factory reset after KDZ finishes... the user can just run a factory reset manually after the flash to achieve the exact same end result.
Click to expand...
Click to collapse
Well I am trying to flash stock EE rom, which I have the KDZ for.
I am flashing via upgrade, and all that happens is when the phone boots it is unstable, phone app crashing etc.
All settings still intact, no myee app, app from open EU rom still exists, very very strange.
Is it possible to convert a KDZ to a twrp flashable zip as twrp seems far easier.
I suspect if I used refurbish it would fix this issue as upgrade seems to not be clearing everything.

chrcol said:
Well I am trying to flash stock EE rom, which I have the KDZ for.
I am flashing via upgrade, and all that happens is when the phone boots it is unstable, phone app crashing etc.
All settings still intact, no myee app, app from open EU rom still exists, very very strange.
Is it possible to convert a KDZ to a twrp flashable zip as twrp seems far easier.
I suspect if I used refurbish it would fix this issue as upgrade seems to not be clearing everything.
Click to expand...
Click to collapse
Did u try what I suggested in other thread? Wipe internal storage before first boot, reboot recovery afterwards before booting system; are u clean flashing? Are you trying to restore any data at all besides things like messages and call logs?
Going from an openEU.kdz to a branded .Kdz would definitely require a Twrp data format and a recovery reboot, perhaps do all this b4 using LGUP with kdz.
Yes it is possible to make a .zip from a kdz, but it's not a simple process and there is no EE branded 20a.zip
Autoprime already stated that refurbish option can be used if you use LGUP v1.11 instead of latest 1.14 but don't forget the .DLL file. Also all refurbish does is wipe data and internal storage; which can be done via TWRP using the method I mentioned above. Try what I mentioned and then reflash kdz;forget about any data besides text messages just take the extra 30min to resetup device from scratch.
What version of LGUP are you using? Can u give more info be more descriptive about what's happening?

it is resolved now but I was just trying to get it in a good state to return the phone to EE.
Doing a factory reset in twrp didnt work, but what did work is I did a reset from in the rom, and after the reboot it was properly reset.
What was odd is when I wiped system and data manually in twrp that also didnt work.
I think I forgot to check if I completely wiped the internal storage, photos etc. As I was rushing to get the phone to be sent back. But the description for the reset option in android says it does wipe all personal data so hopefully that did it.

How can I downgrade LS992?

İs this possible for lg g5 H860?

For H850 just download H85010i_00_OPEN_EU_OP_0923.kdz flash it with LGUP 1.4(uppercut) after it's finished reset the phone then just flash android 6 firmware that you like.

i have h850 ,
current firmware is v20a updated via fota
no root , no bootloader unlock ,,, compleatlly stock phone
i want to downgreade to any 6.0.1 firmware without losing data (if possible)
if not, what to check and what steps to do without tripping on cust ot drk or modem or .... issues ?
pleas advice me ....

LGUP corrupts whenever i hit Start, but it works just fine with N kdz (mine is 20a). I have tried to flash bootloader but still ended up with the same outcome.

Lucky patcher does not work on nougat. Application not installed. playstore error 504
autoprime said:
good info.
I can make it even easier... instead of downloading my 10E COMPLETE ZIP
Just download/flash my 10E BOOTLOADER ZIP. It'll make LGUP work again with M KDZs and the BOOTLOADER ZIP is much smaller!
Click to expand...
Click to collapse
I rooted H850 following autoprime's LG G5 H850 Bootloader Unlock instruction with autoprime's modded "Minimal ADB and Fastboot" {[ 1.) selecting port 41 in device manager (maybe was not necessary) and 2.) pushing TWRP twrp-3.1.1-0-h850.img 3.)booted into recovery (Using 2 hands.. use one hand/finger to press/hold volume down.. and use the other hand for the power button. Press n hold both buttons.) 4. flashing SuperSU (UPDATE-SuperSU-v2.82-20170528234214.zip) ]}.
Installed 20a with lgup because for a strange (windows 10 folder administrator permission) reason nether UPPERCUT_1.0.0.0.exe nether LGFlashTool.exe worked properly).
Unfortunatly I installed [ROM] [Nougat 7.0] Fulmics ROM 3.3 ◦ v20D ◦ H850 but, because the very big LACK of xposed framework on nougat, I had too much difficulties to patch correctly the core jar with lucky patcher getting a lot of error "app not installed the package appears to be corrupt" and other play store error 504 app not installed.
So I decided to downgrade and leave from any Nougat 7.0 based rom in order to move on Marshmallow 6.0. In particular I used TWRP to wipe everything and flash [STOCK][M] H850 10E OPEN EU ROM autoprime's 10E COMPLETE ZIP then Supersu then framework.
On android this time I skipped google registration and LG software updates with data and wifi OFF.
Then I activated USB debug in developer section
Then I followed these step in that really precise order:
a) installed super su again with twrp (want to be sure to have got ROOT);
b) configure Super Su setting in android to activate pseudo PRO option then uncheck the "separation mount space" in order to share .init;
c) configure Super Su setting giving permission always without asking and also during in boot (to everybody);
d) installed xposed-v87-sdk23-arm64.zip in TWRP
e) installed lucky patcher and using it to unistall every LG apps;
f) activate for the very first time wify in order to update immidiately lucky patcher (update available in lucky patcher settings) than download patch update;
g) installed xposed apk (in android obviosly because I refer to apk pattern) and run it following app procedure for a correct detection of framework then activate Lucky patcher module in xposed apk then reboot to permit lucky patcher using framework;
h) installed busybox (after the check I choose the "smart install").
i) and now I enjoy the freedom that I haven't got in Nougat to test some application before buying them, just to be sure to not waste money for fake apk like voice pro or other expensive one that fools me before so many times. :good:
Update: G5 H850 Genisys Theme 1.3 v10e MM is a great choice for stability and battery life.

Instruction for TWRP, rooting and updating T-Mobile G5 H830

Hi,
If this is the wrong place, please move it.
I'm new to LG G5. Bought from eBay with a modified ROM H83020i_un. Below are the steps I took to root this device and upgrade it to the latest stock Android 7 ROM
Notes about rebooting into recovery
1. Power off device.
2. Hold power and vol down button.
3. Wait until lg logo appears.
4. Release power button only for one second while continuing to hold vol down. After the second elapsed press and hold the power button until it boots into recovery.
Click to expand...
Click to collapse
Notes
NEVER use Settings -> factory reset. It will end up in TWRP loop
If you ended up in TWRP loop, never wipe misc partition. It will result in MAC Address changes every time you reboot . The correct method is [FIX] Stuck in Custom Recovery [TWRP/CWM] (After trying OTA)
1. Install 20a. This is the last version I can install TWRP and root. Instruction is [STOCK][N][ARB01] H830 20A ROM + Flashable ZIPs + IMGs + KDZ. I used LG UP method and this is fairly painless
2. Unlock the bootloader, install TWRP and root. Instructions are now with TWRP!. However, the adb posted in the link can't ever trigger the Allow USB Debug prompt on the phone. I wasted 2 hours on trying all kinds of combination of settings. Eventually, I download version 1.4.3 Minimal ADB and Fastboot Tool and it worked as expected. I flashed SuperSU. And formatted the data to disable encryption. Now I have 20a with TWRP and root
3. Upgrade to the latest (20m as of now). Instructions for 20k is [STOCK][N][ARB01] H830 20k ZIPs + IMGs + KDZ (2017-07-01 Security Patch), following Install via TWRP Directions -> Stock ROOTED. I had to do quite a bit reading to make sure the correct step (keep TWRP and root).
autoprime's post https://forum.xda-developers.com/showpost.php?p=72537357&postcount=21
recovery-from-boot.p is contained in the system partition and returns any time you flash a stock system.img (such as my COMPLETE zip).. so if you were on, for example, 20f and then renamed/deleted recovery-from-boot.p.. and then flash 20i COMPLETE zip.. you would have to rename/delete the file again... and when you flash the next update you'll have to do it again etc. The reason I leave this file inside the system file is because I'm providing 100% stock images so users can go back to 100% stock or mod/customize things to their liking.
Click to expand...
Click to collapse
There is also another advice from him in https://forum.xda-developers.com/showpost.php?p=73343155&postcount=40
am now suggesting people wipe cache after flashing my COMPLETE zip but before they flash a root zip. This may help with the random people who seem to lose TWRP after flashing Magisk/SuperSU.
Complete zip -> wipe cache -> flash root zip -> finished
Click to expand...
Click to collapse
So I followed the TWRP stock rooted step. Wipe cache -> flash complete zip -> wipe cache -> flash SuperSU zip -> Mount system -> File Manger rename /system/recovery-from-boot.p to /system/recovery-from-boot.p.bak. Reboot (no need to format data)
To get into TWRP, you would need to boot into recovery, and choose Yes twice (it won't reset your device)
4. Disable OTA update as it will break my phone.
The instruction is in LG G5 ALL-IN-ONE THREAD in the section of "Disable OTAs". I've also found another method which was posted for G4 but the menu is also available in G5 at https://www.androidexplained.com/lg-g4-disable-ota-updates/
Hidden Menu Method
Launch the Dialer Application
Enter the Following Code to Access the Hidden Menu. . .
277634#*#
. . .Then Scroll Down and Tap on ‘WiFi Test’
Tap on the ‘OTA Setting’ Option
Then Tap on the Big ‘Disable’ Button
Reboot the LG G4
Click to expand...
Click to collapse
It contains some other methods but none worked on non-root devices.
On rooted device, I can find LG Update Center and FOTA and disabled them.
However, Google Play Service still show the notification for Android System Update. The only option is to disable notification from it.
Hopefully, this is helpful

[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