Database Users

Android N Preview 2 npc91k (flashable & image with no encryption and dm verification)

Android N Preview 2 npc91k (flashable & image with no encryption and dm verification)
This thread is for the second Android N Preview.
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **​** The following are instruction for installing Android N Preview 2 image released by Google on 4/13/2016. After the installation you will have TWRP recovery 3.0.2-0 with the data partition erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **​Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP installed on your phone.
2- Download this flashable zip..
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N Preview 2. If your internal storage is unencrypted before flashing it remains unencrypted.
For some people this didn't work. It seems to be the case when you have been encrypted by your previous Android N installation, in which case TWRP seems to have difficulty reading the file, and that seemingly Preview 2 doesn't play nice with TWRP. It works best when you are unencrypted and your recovery is 3.0.2-0. Thanks to @gammaxgoblin, @blitzerking1, @Michael in ATL, @HueyT, and @PhillyFlyer for debugging and hints.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and upgrades TWRP)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.71 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133. Despite the fact that SuperSU 2.71 is supposedly re-written for Android N, there are still some apps that seem to have a problem obtaining root. The commonest complaint on this thread so far has been about Adaway. If you want to block Ads just manually do what Adaway does. Download a hosts file from any ad block list server such as http://winhelp2002.mvps.org/hosts.htm, copy the files on your sdcard, boot the phone into recovery, and using the TWRP file manager replace the file /system/etc/hosts with this file and set its permissions to 644 (rw-r--r--).

wouldnt flash first go. redl now
no flash again

gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Same happened to me. It would not flash, same error

gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?

najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
Same error for me as well. I can extract the zip and view the file it is talking about. I also tried on TWRP 3.0.1-0 and TWRP 3.0.2-0
Everything is working perfect for me with the new zip. I have a unencrypted phone and used 3.0.2 TWRP.

najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
i tried 3.0.1 and 3.0.2 and i can also see the file

Method 2 works great

Method two works I used it myself

Shall I flash preview 2 directly from marshmallow?

Seems like TWRP is having a lot of troubles with each version of N Preview's encryption. I have same problem with both N6 and N6P, as do others in that forum too....:/

i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.

marius987 said:
i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.
Click to expand...
Click to collapse
Sorry for the stupid question. What do you mean for TB?

cerico76 said:
Sorry for the stupid question. What do you mean for TB?
Click to expand...
Click to collapse
I'm going to assume it stands for Titanium Backup.

Waiting for fixed method #1

outkastz said:
I'm going to assume it stands for Titanium Backup.
Click to expand...
Click to collapse
Ah,yes! Thanx!

Can someone please provide a link to the desktop website for the flashable zip?

Just to help with the installation of method 2, holding shift and right clicking a blank space in your unzipped folder, you can click open command window here. That will save you having to CD all the way to it.
Sent from my Nexus 6 using XDA-Developers mobile app

I did method 1. It upgraded fine. All my data remained. It killed root (expected this) and my TWRP. I was unencrypted before attempting.
I went and downloaded the latest TWRP and flashed via fastboot. Then downloaded latest SuperSU from http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 and flashed it via my newly installed TWRP. Root confirmed and all is well.
Good to go Thanks!

I've got an "Invalid boot image" issue :
Any tought ?

outpox said:
I've got an "Invalid boot image" issue :
Any tought ?
Click to expand...
Click to collapse
You may have to flash a previous stable release of marshmallow or lollipop from Google first and then try this because something seems to be corrupted in your system.

Bricked System - Need Image for fastboot or ideas

Hello,
somehow I had a problem that many apps force closed after doing something, so I tried flashing opengapps - worst idea. I started the phone and nothing worked because I always get force close on Setup Assistent.
I were on Cydras Rom (https://forum.xda-developers.com/le-pro3/development/rom-google-edition-cydras-t3514742). So now I tried overflashing it again but somehow it says successfully installed and also "cant unmount system: volume not found". The system image is now about 900mb big, the zip 1.3gb - can't be possible. It doesn't but and stuck on the first Leeco screen. Now I tried sideload: failed - invalid command..
Well, I tried getting another rom and put it on phone by MTP in TWRP.. Same problem - TARS causes boot into Recovery and CM13 by Superluminal doesn't even flash: stuck on "patching system image unconditonally".
Has someone a solution or more like is there any system image I can flash through fastboot?
Or could someone make one? PLEASE!
I think somehow the system can't be mounted...

Probably flashing stock ROM jacked your phone into locked system.
Are you able to fastboot flash/boot TWRP?
If yes, try to copy the official firmware zip by renaming it to update.zip and putting it into internal storage.
Next you have to flash stock recovery from fastboot, reboot into recovery right away and then apply update. If you succeed you should have a working back-to-stock.
You didn't mention if u have x727 or x720? And you didn't mention what possible "something" u did which jacked up your apps to FCs. Looks like a kernel level modification to me...
Have u tried the bootloader unlock checking command?

Somehow I tried this twrp backup: https://forum.xda-developers.com/le-pro3/how-to/le-pro-3-lex727-twrp-backup-eui-5-8-019s-t3504761
Now I can't mount storage, because it's encrypted... -.-
I have x720 and I don't really know what caused the FCs, the last I remember was uninstalling Android WebView.
Now I have to try to get access to storage again..
## bootloader is unlocked

dark_prince said:
Probably flashing stock ROM jacked your phone into locked system.
Are you able to fastboot flash/boot TWRP?
If yes, try to copy the official firmware zip by renaming it to update.zip and putting it into internal storage.
Next you have to flash stock recovery from fastboot, reboot into recovery right away and then apply update. If you succeed you should have a working back-to-stock.
You didn't mention if u have x727 or x720? And you didn't mention what possible "something" u did which jacked up your apps to FCs. Looks like a kernel level modification to me...
Have u tried the bootloader unlock checking command?
Click to expand...
Click to collapse
Okay, my internal storage is now lost.. but idc.
I tried getting 20s stock zip and it says "apk not found" in stock recovery..?

Grossoshop ROM is fastboot installable.

Presterin said:
Grossoshop ROM is fastboot installable.
Click to expand...
Click to collapse
Link?

idragonx said:
Link?
Click to expand...
Click to collapse
Sure, here you go: http://blog.grossoshop.net/leeco-x720-grossoshop-rom-italiano-ota/

idragonx said:
Okay, my internal storage is now lost.. but idc.
I tried getting 20s stock zip and it says "apk not found" in stock recovery..?
Click to expand...
Click to collapse
Unlocked bootloader so far so good.
Flash TWRP and try to reformat partitions.
ADB side-load your favorite ROM (make sure to verify MD5 first before side-loading)...

dark_prince said:
Unlocked bootloader so far so good.
Flash TWRP and try to reformat partitions.
ADB side-load your favorite ROM (make sure to verify MD5 first before side-loading)...
Click to expand...
Click to collapse
How to reformat? I tried wiping all & make it ext4 in TWRP.
Sideload doesn't work: * failed to read command: Invalid argument

Advanced wipe > modify or repair file system?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
What appears if u use the 2nd wipe option instead of advanced wipe (the option other than slide to factory reset & Advanced wipe, I forgot it's name but it reformats internal storage as well)

dark_prince said:
Advanced wipe > modify or repair file system?
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
What appears if u use the 2nd wipe option instead of advanced wipe (the option other than slide to factory reset & Advanced wipe, I forgot it's name but it reformats internal storage as well)
Click to expand...
Click to collapse
All wipes work, but sideload still doesn't work.
I tried now downloading the grossoshop zip and there is no batch like in the screenshots, so I tried flashing system.img manually out of the zip and I get:
fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi

Elaborate side load doesn't work.... Is it an error on TWRP? Or you just can't find device while doing "ADB devices"?
Is ADB correctly installed? Is ur device correctly recognized drivers-wise ? Check device manager after enabling side load while ur device is connected via USB....
Which device is it? 720 or 727?
Drivers? Check in device manager after "Swipe to enable side load"

idragonx said:
All wipes work, but sideload still doesn't work.
I tried now downloading the grossoshop zip and there is no batch like in the screenshots, so I tried flashing system.img manually out of the zip and I get:
fastboot flash system system.img
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
Click to expand...
Click to collapse
That's weird, I downloaded it couple of days ago, and it has batch file. Corrupted download?

Presterin said:
That's weird, I downloaded it couple of days ago, and it has batch file. Corrupted download?
Click to expand...
Click to collapse
I used this from the post: https://mega.nz/#!tUkUQJwZ!h3tniWVWlSiYJICadW7MuEdYLDFKfNmNcEOBQ-eL1JM

dark_prince said:
Elaborate side load doesn't work.... Is it an error on TWRP? Or you just can't find device while doing "ADB devices"?
Is ADB correctly installed? Is ur device correctly recognized drivers-wise ? Check device manager after enabling side load while ur device is connected via USB....
Which device is it? 720 or 727?
Drivers? Check in device manager after "Swipe to enable side load"
Click to expand...
Click to collapse
It's x720.
Drivers seems to work in device manager, I can use adb, but on sideload it goes to ~3% and the the error I mentioned comes with invalid argument.
Can I change somehow the maximum system.img size for device? Somehow I need to flash it with fastboot
#####
I GOT IT.
Finally - https://mega.nz/#!VEM1QIYL!HwT9hk7-GA6KZBTRMv0IQ9kleYaG-el63UF21S6P0us
It could do it using fastboot - oh god thanks. Now I try to flash my custom rom.

idragonx said:
It's x720.
Drivers seems to work in device manager, I can use adb, but on sideload it goes to ~3% and the the error I mentioned comes with invalid argument.
Can I change somehow the maximum system.img size for device? Somehow I need to flash it with fastboot.
Click to expand...
Click to collapse
mD5 verified?
Alright try this. Get latest CM13 build from teamsuperluminal website and also get the x720 patch from there too. Then in TWRP (while connected to USB) go to advanced wipe > cache + system + dalvik + data.
Open downloaded CM13 zip in 7-zip file manager, go to META-INF > Android folder and extract only the updater_script file. (Should be in that or in a subwoofer). Keep the 7-zip opened and dont close it.
Open the updater_script file in notepad++ and remove first line which starts with "assert". Save
Then drag drop it back into 7-zip( in the same folder structure.) Close 7-zip after
Enable side load in TWRP
Now side load x720 patch first
Then side load CM13 ROM file u just modified into your phone.

dark_prince said:
Enable side load in TWRP
Now side load x720 patch first
Then side load CM13 ROM file u just modified into your phone.
Click to expand...
Click to collapse
Thank you very much for your help, but finally I found the 18s from grossoshop with the BATCH - it could fastboot load the system.img partially and now it boots <3

Ah sweet. Lol
I couldn't flash CM13 until I tried 5 different methods to get Round patching system lockout...

dark_prince said:
Ah sweet. Lol
I couldn't flash CM13 until I tried 5 different methods to get Round patching system lockout...
Click to expand...
Click to collapse
Well, but I can't flash back my cydras ROM

Imho it should work now to go back to stock. Download official Chinese firmware zip file (not OTA) and rename it to update.zip
Put it in internal storage (not into any folder)
Go to fastboot and flash stock recovery.
Then boot into stock recovery and apply update.zip
Result should be profiting.
idragonx said:
Well, but I can't flash back my cydras ROM
Click to expand...
Click to collapse

[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

[HELP]xXx No Limits to Android Pie

Hello everyone, could anyone help me to migrate from ROM xXx to Android 9?
I am currently using the ROM xXx but when trying to switch to another ROM I have problems with bootloop.
I tried following the procedures outlined in the last comments of the original thread but did not succeed, could anyone help me with a step by step to get out of the ROM and go to version 9 of android?
Here is some information that may be helpful in finding a possible solution:
Actually ROM: xXx No Limits 4.3 (https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121)
New ROM:OxygenOS 9.0.1 (https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003)
Device is decrypted
Bootloader Unlocked
TRWP 3.2.1-X blu_spark v8.61
In some attempts to install ROM the TWRP returned me error regarding vendor partition.
Thanks to anyone who can help me.

josebeserra said:
Hello everyone, could anyone help me to migrate from ROM xXx to Android 9?
I am currently using the ROM xXx but when trying to switch to another ROM I have problems with bootloop.
I tried following the procedures outlined in the last comments of the original thread but did not succeed, could anyone help me with a step by step to get out of the ROM and go to version 9 of android?
Here is some information that may be helpful in finding a possible solution:
Actually ROM: xXx No Limits 4.3 (https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121)
New ROM:OxygenOS 9.0.1 (https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003)
Device is decrypted
Bootloader Unlocked
TRWP 3.2.1-X blu_spark v8.61
In some attempts to install ROM the TWRP returned me error regarding vendor partition.
Thanks to anyone who can help me.
Click to expand...
Click to collapse
You'll need to be on your PC for this. Make sure you backup anything you want to keep from Internal Storage:
OOS:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
1) Wipe and Format everything in TWRP.
2) Move OOS 5.1.3 (Full Zip) to Internal Storage
3) Install 5.1.3 and nothing else (You will lose TWRP, but don't worry abut that now)
4) OTA up to 5.1.7
5) If you don't get offered OTA to 9.0.1 use full zip from here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
6) Once on OOS 9.0.1 you can use Fastboot to flash latest Codeworkx TWRP: https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
If you want to install a custom ROM after that:
7) Wipe and Format
8) Install Pie ROM/Gapps etc

Dirk said:
You'll need to be on your PC for this. Make sure you backup anything you want to keep from Internal Storage:
OOS:
https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
1) Wipe and Format everything in TWRP.
2) Move OOS 5.1.3 (Full Zip) to Internal Storage
3) Install 5.1.3 and nothing else (You will lose TWRP, but don't worry abut that now)
4) OTA up to 5.1.7
5) If you don't get offered OTA to 9.0.1 use full zip from here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
6) Once on OOS 9.0.1 you can use Fastboot to flash latest Codeworkx TWRP: https://sourceforge.net/projects/cheeseburgerdumplings/files/16.0/cheeseburger/recovery/
If you want to install a custom ROM after that:
7) Wipe and Format
8) Install Pie ROM/Gapps etc
Click to expand...
Click to collapse
Thx for Help dude, but i have a problem.
I backed up my stuff and joined TWRP, after joining TWRP I went to WIPE> Format Data.
After that I passed the file from ROM 5.1.3 to the internal memory of the device and went to install and started the procedure, but doing so returned an error and I would like you to help me if it were possible.
The following message was displayed:
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/OnePlus5Oxygen_23_OTA_036_5.1.3.zip'
Can you help me?

josebeserra said:
Thx for Help dude, but i have a problem.
I backed up my stuff and joined TWRP, after joining TWRP I went to WIPE> Format Data.
After that I passed the file from ROM 5.1.3 to the internal memory of the device and went to install and started the procedure, but doing so returned an error and I would like you to help me if it were possible.
The following message was displayed:
Updater process ended with ERROR: 7
Error installing zip file '/sdcard/OnePlus5Oxygen_23_OTA_036_5.1.3.zip'
Can you help me?
Click to expand...
Click to collapse
Error 7 leads to corrupted file. Check your downloaded file, try again.

strongst said:
Error 7 leads to corrupted file. Check your downloaded file, try again.
Click to expand...
Click to collapse
ok, i will re-download the file and try the installation again.

I downloaded it again and tried the installation but again I got the same error when trying to install.
I am doing the download again but this time I will try to download without using download managers, in the previous attempts I used the Internet Download Manager (IDM) to do the downloads, do you recommend some download manager or browser?
I will also download via mobile data on the 4G network.

josebeserra said:
I downloaded it again and tried the installation but again I got the same error when trying to install.
I am doing the download again but this time I will try to download without using download managers, in the previous attempts I used the Internet Download Manager (IDM) to do the downloads, do you recommend some download manager or browser?
I will also download via mobile data on the 4G network.
Click to expand...
Click to collapse
I never use or recommend download managers cause of this
You can use Opera mobile, Firefox etc. But with download managers there are more issues(you'll find a lot on xda).

strongst said:
I never use or recommend download managers cause of this
You can use Opera mobile, Firefox etc. But with download managers there are more issues(you'll find a lot on xda).
Click to expand...
Click to collapse
Okay, thanks, I'll try to download again and I'll come back with the result soon

I downloaded the file from ROM 5.1.3 on the phone and again it returned the same error, I will try one more time.
Please give me your opinion, is there any version of TWRP that is recommended for installation? is it not the version I'm using that might not be reading the file?
Anything else, do I need to install 5.1.3 exactly or can I get a version prior to it?
There's something wrong in the middle of it, but let's keep trying.
lol

josebeserra said:
Actually ROM: xXx No Limits 4.3 (https://forum.xda-developers.com/on...xxx-nolimits-1-1-speed-ram-optimized-t3627121)
New ROM:OxygenOS 9.0.1 (https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003)
Device is decrypted
Bootloader Unlocked
TRWP 3.2.1-X blu_spark v8.61[/B]
Click to expand...
Click to collapse
Are you on xXx No Limits 4.3 (Nougat - 4.5.14) or xXx No Limits 4.3 Magisk Rom?
If you are talking about the Magisk Rom then we need to know what OOS version you are on to be able to give you the right advise.

josebeserra said:
I downloaded the file from ROM 5.1.3 on the phone and again it returned the same error, I will try one more time.
Please give me your opinion, is there any version of TWRP that is recommended for installation? is it not the version I'm using that might not be reading the file?
Anything else, do I need to install 5.1.3 exactly or can I get a version prior to it?
There's something wrong in the middle of it, but let's keep trying.
lol
Click to expand...
Click to collapse
Maybe you can try with this recovery: twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
And see if it works.
Otherwise I would recommend to download OxygenOS 5.1.4 and try to flash that.

Z-Blade said:
Are you on xXx No Limits 4.3 (Nougat - 4.5.14) or xXx No Limits 4.3 Magisk Rom?
If you are talking about the Magisk Rom then we need to know what OOS version you are on to be able to give you the right advise.
Click to expand...
Click to collapse
I'm currently in version 4.3 Magisk, I think this can make it easier to find a possible output or end up making it more difficult.
strongst said:
Maybe you can try with this recovery: twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
And see if it works.
Otherwise I would recommend to download OxygenOS 5.1.4 and try to flash that.
Click to expand...
Click to collapse
I will test with the one that recommended me and I will also download version 5.1.4

josebeserra said:
I'm currently in version 4.3 Magisk, I think this can make it easier to find a possible output or end up making it more difficult.
I will test with the one that recommended me and I will also download version 5.1.4
Click to expand...
Click to collapse
4.3 xXx magisk means you're running a stock oxygenOS where xXx 4.3 mod is running. Do you remember which oxygenOS version it was? 5.1.4 5.1.7 or whatever?

josebeserra said:
I'm currently in version 4.3 Magisk, I think this can make it easier to find a possible output or end up making it more difficult.
Click to expand...
Click to collapse
It could make things easier. If your phone still boots into OOS, go into Setting and scroll to the very bottom and select About Phone. Look at what Oxygen OS you are running. What you need to do is get that version all the way up to 5.1.7. Once you are there, you can just flash 9.0.2.

strongst said:
4.3 xXx magisk means you're running a stock oxygenOS where xXx 4.3 mod is running. Do you remember which oxygenOS version it was? 5.1.4 5.1.7 or whatever?
Click to expand...
Click to collapse
I'm using the OREO Stable version xXx_NoLimits_12.0_OP5_Oxygen_5.1.3 with the update patch xXx_NoLimits_4.3_magisk_rom
Z-Blade said:
It could make things easier. If your phone still boots into OOS, go into Setting and scroll to the very bottom and select About Phone. Look at what Oxygen OS you are running. What you need to do is get that version all the way up to 5.1.7. Once you are there, you can just flash 9.0.2.
Click to expand...
Click to collapse
This is the problem, I can not get out of the ROM No Limits to go to another ROM, I've tried some suggestions but still nothing worked, I'm counting on the patience of the members here of the forum to help me with this problem, but I believe that will soon be resolved and thank you all for the help.

josebeserra said:
I'm using the OREO Stable version xXx_NoLimits_12.0_OP5_Oxygen_5.1.3 with the update patch xXx_NoLimits_4.3_magisk_rom
Click to expand...
Click to collapse
Ok, so you're on a patched xXx rom not stock rom with xXx mod. Weird setup
Anyway, did 5.1.4 sucessfully flash without error 7?

strongst said:
Ok, so you're on a patched xXx rom not stock rom with xXx mod. Weird setup
Anyway, did 5.1.4 sucessfully flash without error 7?
Click to expand...
Click to collapse
strongst said:
Ok, so you're on a patched xXx rom not stock rom with xXx mod. Weird setup
Anyway, did 5.1.4 sucessfully flash without error 7?
Click to expand...
Click to collapse
I have not tried to install 5.1.4 yet, I was trying to 5.1.3 as it was suggested, I will download version 5.1.4 that is in this repository (https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190), and I will try to make the installation clean, ie format all the data, move the ZIP into the internal memory and try to see if it works.
I will try to clarify about the patch in case I try to reinstall ROM No Limits I need to install the full version which is 12.0 and patch 4.3 is just an update patch for the latest version and I can also go back to version 12.0.
Version 5.1.4 I have not yet tested if I can install it without errors, I will do it soon and I will come back with the result.

I think 5.1.4 should do the trick. I would highly recommend you wipe everything including systems, internal and data. This will pretty much give you a blank phone. Connect the phone to your computer and copy over 5.1.4 to the internal storage through TWRP, it should be the only file you see in your sdcard. Flash it and you should be good.

Z-Blade said:
I think 5.1.4 should do the trick. I would highly recommend you wipe everything including systems, internal and data. This will pretty much give you a blank phone. Connect the phone to your computer and copy over 5.1.4 to the internal storage through TWRP, it should be the only file you see in your sdcard. Flash it and you should be good.
Click to expand...
Click to collapse
Okay, I'll do the test and I'll come back soon with the result, I'll change the version of TWRP too, this may be the problem.

Bringing the result of a few more tests, I first changed the recovery version, I went to the twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img as suggested and after that I formatted all the data and started to appear a new one Error that was Failed to mount '/ vendor' (Invalid argument), I tried to install the 5.1.3 ROM and also to 5.1.4, which it was indicating was installing but at the end of the installation again I returned the error Failed to mount '/ vendor '(Invalid argument).
After that I reinstalled ROM No Limits 12.0 v. 5.1.3.
Does anyone know how to solve this new error?

Guide to flash realmeUI 2.0 beta builds [Global Variant Only]

DISCLAIMER: YOU ARE RESPONSIBLE FOR WHAT YOU DO​The only reason behind posting this guide is because now we have a way to fix device if any unusual things happen after flashing beta builds. Beginners & noobs who doesn't have any idea about flashing stuff should stay away.
PREREQUISITES:
1. Bootloader Unlocked Device
2. OrangeFox
3. Stable OZIP (Android 10 | realmeUI 1.0 | C35)
4. Beta ZIP (Android 11 | realmeUI 2.0 | F06)
5. Unofficial OrangeFox beta build (For realmeUI 2.0 A11 FW only)
6. realmeUI 2.0 stock recovery
7. A11 VBMETA
8. Patched VBMETA
PROCESS TO FLASH:
1. Just to be on safer side we are going to make sure everything is stock & all partitions are unmodified. So reflash latest Stable OZIP (C35) via OrangeFox.
2. Format data & reboot to System (This is optional but better to do it, we never know what might happen with realme device)
3. Reboot back to Bootloader if realmeUI 1.0 boots fine
4. Flash OrangeFox build which you used previously & also flash patched vbmeta (fastboot flash vbmeta patched_vbmeta.img)otherwise you get "Boot is destroyed........"
5. Boot into custom recovery & copy downloaded Beta ZIP
6. Flash the Beta ZIP & format data.
7. Reboot to System. realmeUI 2.0 should boot now.
COMMON ISSUES & FIXES:
1. Device stuck at white realme splash logo
Sol. Few people reported it booted when they flashed patched vbmeta so you can first try that. If doesn't work then you can flash A11 vbmeta (fastboot flash vbmeta vbmeta.img) attached here & reboot to system
2. Device stuck at Yellow realme boot animation
Sol. If it's stuck for more than 2-3mins then reboot to bootloader & format data by executing fastboot erase userdata ., never do fastboot -w it's messing up data partition in A11 due to new changes introduced by realme
3. Stuck in bootloader (fastboot)
Sol. Flash the unofficial OrangeFox rescue build & boot into it, copy C35 OZIP to internal storage. Flash it & format data. Reboot to System. Wait for public realmeUI 2.0 release.
4. Unofficial OrangeFox beta build stuck at Ofox splash & display keeps blinking
Sol. This happens because Ofox can't decrypt realmeUI 2.0 data, only way to boot this ofox build properly is by formatting data, reboot back to bootloader. fastboot erase userdata
5. Device doesn't have realmeUI 2.0 Stock Recovery
Sol. Flash the attached stock recovery

reserved

Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA

Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader

bharatgsp said:
Can i Flash on Locked Bootloader device via stock recovery or filemanager currently i am c 34 locked bootloader
Click to expand...
Click to collapse
na it doesn't work

ChromiumPD said:
Congrats! Will try now
EDIT: Works fine but just 2 hints.
1: Don't Use TWPR 3.5.0_9 or you will get Zip Treble Error
2: After you flash RUI 2.0 it's a MUST flash A11 VBMETA
Click to expand...
Click to collapse
Right will update guide, thank you

What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?

kurtextrem said:
What does the check look like that prevents the stock recovery from accepting to flash the beta build (if you try to upgrade from C.35)?
Click to expand...
Click to collapse
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.

It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""

Zippka224 said:
It can't install on TWRP 3.4.0.0 -> Error this package is for RMX1931L1, this is a ""
Click to expand...
Click to collapse
edited guide, use ofox only. TWRP doesn't seem to work for everyone.

Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance

4j17h said:
Stock recovery only accepts signed OZIP/ZIP like the ones uploaded in their website, OTA updates we receive are signed with different certificate that's why installing those custom OZIPs fail if we do it manually.
Click to expand...
Click to collapse
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?

Tierri said:
Hi, first thanks for the post.
I would like to ask you if there is a way to revert back to c35 after?
Thank you in advance
Click to expand...
Click to collapse
Well there are two ways, we can use stock recovery to downgrade from beta builds to C34
Another way would be to flash unofficial Ofox build, copy C34 OZIP to internal storage & flash it.

kurtextrem said:
Thank you. I wonder how the software update works then? How does the software update "app" manage to flash those builds then?
Click to expand...
Click to collapse
OTA updater app is verifying the update & rebooting to stock recovery, so if we can figure out the same way we can install custom ozips via stock recovery too

How would you recommend to bring over apps & their settings to A11? After formatting data they'll be lost. Which backup method is able to restore them? Have you rooted it already?

Magisk?
Cool ! It works fine thank you.
but I noticed that the "Unofficial OrangeFox beta build" cant mount internal storage issue with following error : "could not mount /data and unable to find crypto footer"
So is there another way to Root my device without wiping data?

Hi
First Thank you for this post .
I want to restore a stock recovery UI 1.0 now i am using orangefox recovery on C.34
can i restore without format data or waiting UI 2.0 stable ??
Many Thanks

Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks

tuga49 said:
Hi,
I've followed the steps and no errors. After reboot, the system stucks at Realme white logo. How it's said on common issues, i've flashed then A11 vbmeta, and the same. Ive waited about 10minutes and it keeps there. I've tried flash the Ofox recovery again to repeat the process but now I can't get Ofox working. I can access fastboot and if I try reboot to recovery, it symply reboots to bootloader... What should I do? I also tried all the options in common issues but without success...
Thanks
Click to expand...
Click to collapse
try to install patched vbmeta its work form me

So for me I dirty flashed the f06.zip beta on c.35 in official [email protected]_1 release and flashed vbmetaA11 but it failed to then i flashed patched_vbmeta.img and voila it booted just fine and optimizing apps appeared.
Thanks very much to Original Poster we can now use Realme UI 2.0 because of him.
Thanks a lot once again