Develop Bugs

How to apply OTA upgrade Nexus 5X android keep data, keep un-encrypted [SOLVED]

I've got an unlocked rooted Nexus 5x, encryption off, build MMB29K. I got a notification of OTA update. Looks like it's to upgrade to MMB29P. I'd like to do this without losing 'encryption off' and having to redo all data and apps.
Here's what worked:
cd </path/to/hammerhead-lrx22c>
fastboot flash bootloader bootloader-hammerhead-hhz12d.img
Reboot the bootloader.
fastboot flash radio radio-hammerhead-m8974a-*.img
cd <image-hammerhead-lrx22c>
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
If you DO NOT use a custom recovery (like TWRP or CWM), then also: fastboot flash recovery recovery.img
Don't worry if you see messages like "target reported max download size of 1073741824 bytes". Just wait and let it finish.
Reboot your phone and enjoy. It's normal for the first boot to take a while. Going from Kitkat to Lollipop took about 20 minutes. Going from 5.0 to 5.0.1 took 5-10, I think. YMMV.
Click to expand...
Click to collapse
flash:
radio-bullhead-xxxxxxx.img
bootloader-bullhead-xxxxx.img
boot.img (might be unnecessary, since we will flash a modified version later on.)
cache.img
system.img
vendor.img
While ignoring these:
recovery.img (would overwrite TWRP)
userdata.img (would erase your data)
Click to expand...
Click to collapse
from here
Any other ideas?

replace anything in the <>. From here
cd </path/to/hammerhead-lrx22c>
fastboot flash bootloader bootloader-<hammerhead-hhz12d>.img
Reboot the bootloader.
fastboot flash radio radio-<hammerhead-m8974a>-*.img
cd <image-hammerhead-lrx22c>
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img

It worked. I opted to stick closer to the second set of instructions. I am on build MMB29P, still un-encrypted, and kept all data.

dkerlee said:
I've got an unlocked rooted Nexus 5x, encryption off, build MMB29K. I got a notification of OTA update. Looks like it's to upgrade to MMB29P. I'd like to do this without losing 'encryption off' and having to redo all data and apps.
from here
Any other ideas?
Click to expand...
Click to collapse
Flashing the bootloader is unnecessary. After following your steps, boot into TWRP and install SuperSU 2.6x (this is systemless root). This will auto patch the boot.img and keep encryption off.
If you boot into the rom before installing SuperSU, you will be encrypted.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
Flashing the bootloader is unnecessary. After following your steps, boot into TWRP and install SuperSU 2.6x (this is systemless root). This will auto patch the boot.img and keep encryption off.
If you boot into the rom before installing SuperSU, you will be encrypted.
Click to expand...
Click to collapse
Thank you. I mis-read my settings, my phone is now encrypted BOOO. That means I'll have to wipe it to un-encrypt the thing.
When I go through "my steps" up there, boot into TWRP to install SuperSU 2.6x, do I need to download that and copy it over beforehand from https://plus.google.com/+Chainfire > latest Beta SuperSU? 2.66 beta at xda

dkerlee said:
Thank you. I mis-read my settings, my phone is now encrypted BOOO. That means I'll have to wipe it to un-encrypt the thing.
When I go through "my steps" up there, boot into TWRP to install SuperSU 2.6x, do I need to download that and copy it over beforehand from https://plus.google.com/+Chainfire > latest Beta SuperSU? 2.66 beta at xda
Click to expand...
Click to collapse
Since you installed the bullhead factory images, format data and decrypt is next. Yes, you'll want to have SuperSU downloaded on your computer. I have a Mac, so I used "ADB Push filename.zip /sdcard/filename.zip" to move it onto my phone after a data format. You must format data then move SuperSU onto your phone and install in TWRP before booting up.
Sent from my Nexus 5X using Tapatalk

Anyone has modified boot.img for MMB29P?

Encryption issues on Nougat firmware

Hi guys,
just nowadays I installed OxygenOS Open Beta 10.
I was upgrading from Open Beta 7, but since I unlocked bootloader after doing that, we can say that I did a clean install (everyone should know that fastboot oem unlock erase all data).
However, I'm having troubles both with stock recovery and TWRP v3.0.2-1.28: pattern won't to be recognized.
If I disable pattern requiring at bootup, in recovery I need to type "a password" (that obviously is wrong in any case).
I tried to reinstall more times the firmware, also did factory reset both via stock/TWRP recovery and fastboot commands.
But nothing has changed.
System is working, but I can't access to recovery anyway.

You could try with other TWRP versions? Say 3.0.2-22

It's a known issue

Use twrp v3.0.2-1.19
Works with no issues, except a mouse pointer in the middle of the twrp. It does not interfere with anything, it is just there (a bug).

Simone98RC said:
Hi guys,
just nowadays I installed OxygenOS Open Beta 10.
I was upgrading from Open Beta 7, but since I unlocked bootloader after doing that, we can say that I did a clean install (everyone should know that fastboot oem unlock erase all data).
However, I'm having troubles both with stock recovery and TWRP v3.0.2-1.28: pattern won't to be recognized.
If I disable pattern requiring at bootup, in recovery I need to type "a password" (that obviously is wrong in any case).
I tried to reinstall more times the firmware, also did factory reset both via stock/TWRP recovery and fastboot commands.
But nothing has changed.
System is working, but I can't access to recovery anyway.
Click to expand...
Click to collapse
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption

If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.

All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!

atulclassic said:
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
Click to expand...
Click to collapse
Cannot find Open Beta 8 Recovery on the download link mentioned above. Looked else where but cannot locate.
Also I flashed recovery_OBT7.img (presumably Open Beta 9 recovery) and followed as mentioned above but DM Verity error does not vanish and TWRP also still asks for password.
Password I hope can be managed with the new modified TWRP mentioned below by @abhibnl but I am more concerned with the dm verity message not going...
---------- Post added at 12:37 AM ---------- Previous post was at 12:30 AM ----------
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
confirmed password request gone...
dm-verity still exist...
phone does not boot past oneplus logo..can boot into recovery or fastboot but no system loading..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
confirmed password request gone...
dm-verity still exist...
phone does not boot past oneplus logo..can boot into recovery or fastboot but no system loading..
now i am sideloading os from twrp

mnishamk said:
You could try with other TWRP versions? Say 3.0.2-22
Click to expand...
Click to collapse
It's not working, because modded TWRP from .18 to .23 are designed for Marshmallow community builds.
dbabaev21 said:
Use twrp v3.0.2-1.19
Works with no issues, except a mouse pointer in the middle of the twrp. It does not interfere with anything, it is just there (a bug).
Click to expand...
Click to collapse
What I've said above (tried .19 too with same unsuccessful result).
atulclassic said:
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
Click to expand...
Click to collapse
Probably it would be risolutive, however I want to stay on latest Community Build.
I can say that sideload won't work with Open Beta 10: it can be flashed only via recovery (both TWRP and stock).
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
That would be easy! The hoped behaviour
Obviously I've just tried with unsuccessful result.
abhibnl said:
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
Click to expand...
Click to collapse
Are you referring to this recovery?
Yeah, I would be in love both with you and the developer, if it works properly
Tomorrow I should try, I'll keep you updated :good:
UPDATE: I've always loved Magisk, since v7 (when I've started using it).
Magisk is the workaround for encryption: just today I've flashed it together with Open Beta 10.
Now encryption is disabled, so goodbye to recovery troubles.
However the issue can't be considered solved because of a stupid workaround, this is not the right approach: I will try @abhibnl solution (re-enable encryption, then install latest blu_spark recovery).
Thanks all for answering.

badmaash said:
Cannot find Open Beta 8 Recovery on the download link mentioned above. Looked else where but cannot locate.
Also I flashed recovery_OBT7.img (presumably Open Beta 9 recovery) and followed as mentioned above but DM Verity error does not vanish and TWRP also still asks for password.
Click to expand...
Click to collapse
The recovery should be linked in the official OB10 download page @ oneplus.net

Simone98RC said:
Are you referring to this recovery?
Yeah, I would be in love both with you and the developer, if it works properly
Tomorrow I should try, I'll keep you updated :good:
UPDATE: I've always loved Magisk, since v7 (when I've started using it).
Magisk is the workaround for encryption: just today I've flashed it together with Open Beta 10.
Now encryption is disabled, so goodbye to recovery troubles.
However the issue can't be considered solved because of a stupid workaround, this is not the right approach: I will try @atulclassic solution (re-enable encryption, then install latest blu_spark recovery).
Thanks all for answering.
Click to expand...
Click to collapse
Yes i was referring to that recovery. 1 user has responded that it worked fine on his f2fs encrypted storage, so i believe it's worth trying. I am not on f2fs so i personally can't test it for you. But i would advise you to atleast give it a try. You never know when you by mistake boot right after a fresh stock rom install with stock kernel, and it will immediately encrypt your storage. So, you can't always just keep formatting internal memory. A proper TWRP recovery is indeed required for both ext4 and f2fs. All i am waiting for is updated kernel sources for recovery devs to work on.

For the many having issues, here's a step by step:
step by step install for OOS 4.0 and twrp-3.0.2-1.28-op3.img
Have OOS stock recovery installed on your phone. You must also have adb installed on your computer.
connect your phone to your computer via usb and open a dos command session on your computer.
On your phone, reboot into fastboot (bootloader).
From adb command on computer, type fastboot boot twrp-3.0.2-1.28-op3.img.
First make a backup and copy it to a safe location.
Now wipe everything - Internal, system, data, cache.
Reboot to Recovery. This is the stock OOS recovery!
Go to install from USB and then enter sideload mode.
On your computer dos prompt, type adb sideload (path)OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Allow the long and slow process to complete and reboot.
Upon reboot, it is encrypting the data partition as EMMC.
Upon bootup, enter setup and go through it quickly as you will have to enter it again so do not waste time configuring it.
Once setup is complete, reboot into fastboot.
From DOS command, enter adb and type command fastboot boot twrp-3.0.2-1.28-op3.img.
TWRP will boot up asking for encryption password. Hit cancel and then swipe to allow modifications.
Go into mount. Only the system and cache will appear. Back out and select WIPE.
select ADVANCED WIPE and data partition only.
Modify the data parition by selecting Repair or Change file system.
It will list the current mount point as emmc. Select Change File System.
Select F2FS and swipe.
This will wipe current data partition and reformat it.
Once you have done this, while in TWRP, select the ADVANCED button on the main menu.
Now select ADB SIDELOAD and swip to start sideload.
On your computer in ADB, type command adb sideload SR1-SuperSU-v2.79-SR1-20161221223537.zip.
Now reboot system and go through the usual setup and your done.

TWRP v11: the definitive solution
abhibnl said:
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
Click to expand...
Click to collapse
FINAL UPDATE: the specified recovery is working with Open Beta 10 decryption.
Thanks all for answering :good:

Install twrp on device without os?

So I almost ****ed up trying to flash a custom rom on my redmi note 8. I had to wipe my whole system image so I had no os installed there. I did almost accidentally wipe my whole internal storage. So twrp would've been gone aswell. So I could've thrown my phone in the trash can, right? Or is there a way to get twrp on a phone with no os and nothing on it? Or maybe even flash a rom? Idk I'm kinda new to this whole topic. What can you do if your phone is completely wiped? No os, no twrp, nothing.
Edit: I just figured out that wiping the internally storage doesn't remove twrp. But still would there still be a way to save your phone with twrp removed and no os? Basically a completely blank device?

Re: @Johnny3_3
Can you boot to twrp by long pressing POWER and VOL UP?
According to your description, your bootloader has been unlocked. But maybe you can't boot with only a boot without ramdisk. Go to fastboot and flash the right fastboot ROM for your phone. Then flash, and go to TWRP using the key combo. Don't use fastboot boot command. Then do anything you want.

Yuki1001 said:
Re: @Johnny3_3
Can you boot to twrp by long pressing POWER and VOL UP?
According to your description, your bootloader has been unlocked. But maybe you can't boot with only a boot without ramdisk. Go to fastboot and flash the right fastboot ROM for your phone. Then flash, and go to TWRP using the key combo. Don't use fastboot boot command. Then do anything you want.
Click to expand...
Click to collapse
Hey, im sorry I think I didn't explain it that well. I have havoc installed already. I just wanted to know what I could have done if I had no os and no twrp installed.

Re: @Johnny3_3
Wiping Internal storage will not wipe the recovery partition.
Once you wipe system partition, you maybe can't boot with a boot that has no ramdisk.
If you have no OS and no TWRP, you can only boot into fastboot and flash images.
If you wipe system, recovery, data, internal storage, cust, you will only be able to boot into fastboot.
If you want to flash twrp on device without OS, just flash the TWRP img file through fastboot.

Johnny3_3 said:
Hey, im sorry I think I didn't explain it that well. I have havoc installed already. I just wanted to know what I could have done if I had no os and no TWRP installed.
Click to expand...
Click to collapse
Get into fastboot mode and flash/boot the recovery with Fastboot - ADB Tools.
There is also an app on github called "Xiaomi ADB Fastboot Tools" I used that to do everything on my phone.

Yuki1001 said:
Re: @Johnny3_3
Wiping Internal storage will not wipe the recovery partition.
Once you wipe system partition, you maybe can't boot with a boot that has no ramdisk.
If you have no OS and no TWRP, you can only boot into fastboot and flash images.
If you wipe system, recovery, data, internal storage, cust, you will only be able to boot into fastboot.
If you want to flash twrp on device without OS, just flash the TWRP img file through fastboot.
Click to expand...
Click to collapse
OK. And what i need to do now? I have Samsung Galaxy A6 and the same problem as @Johnny3_3, but idk how i can now use the phone without enythong in there!!! Pls help me figure out what i should to do in this situation.
~GTHX

Because i dont have the twrp and os on my phone... it just looping the logo of samsung galaxy A6 blablabla....

GTHX2021 said:
OK. And what i need to do now? I have Samsung Galaxy A6 .....
Click to expand...
Click to collapse
This topic is for XRN8.
Better is to ask in the right A6 topic, because the procedure to flash twrp is not the same

Yuki1001 said:
Re: @Johnny3_3
Wiping Internal storage will not wipe the recovery partition.
Once you wipe system partition, you maybe can't boot with a boot that has no ramdisk.
If you have no OS and no TWRP, you can only boot into fastboot and flash images.
If you wipe system, recovery, data, internal storage, cust, you will only be able to boot into fastboot.
If you want to flash twrp on device without OS, just flash the TWRP img file through fastboot.
Click to expand...
Click to collapse
Hi, I have the same problem with my OnePlus 5T. I've tried many times flashing TWRP but it doesn't boot up

Custom ROMS don't work on my device, how do I restore MIUI?

Hello, unfortunately I've tried flashing Pixel Experience and LineageOS along with the vendor.img from the PE thread but they both don't boot up (infinite loading screen). Also the official TWRP doesn't work for me, but the unofficial one by wzsx150 (LR team) does work.
The problem now is that I cannot restore MIUI back. I've tried restoring all the backups I made prior flashing any vendor or custom ROM (except for the Data partition) but it does not boot, so I have downloaded the EU firmware from the official website and tried to flash it. These are the steps I follow:
-Wipe System, Vendor, Data, Internal Storage, Cache, Cache / Dalvik
-Flash MIUI zip
-Enter fastboot
-Re-apply anti-brick fix
-Flash vbmeta.img (taken from the official MIUI zip) with following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And this is what I get:
When I first turn on the device, I get the Redmi logo for about 20 seconds, then it reboots automatically. At the startup, TWRP automatically boots instead of System.
How do I fix it?
One last thing: I have the EEU version, idk if that's the root of all the problems I had.

Vexx_zerozero said:
Hello, unfortunately I've tried flashing Pixel Experience and LineageOS along with the vendor.img from the PE thread but they both don't boot up (infinite loading screen). Also the official TWRP doesn't work for me, but the unofficial one by wzsx150 (LR team) does work.
The problem now is that I cannot restore MIUI back. I've tried restoring all the backups I made prior flashing any vendor or custom ROM (except for the Data partition) but it does not boot, so I have downloaded the EU firmware from the official website and tried to flash it. These are the steps I follow:
-Wipe System, Vendor, Data, Internal Storage, Cache, Cache / Dalvik
-Flash MIUI zip
-Enter fastboot
-Re-apply anti-brick fix
-Flash vbmeta.img (taken from the official MIUI zip) with following command:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
And this is what I get:
When I first turn on the device, I get the Redmi logo for about 20 seconds, then it reboots automatically. At the startup, TWRP automatically boots instead of System.
How do I fix it?
One last thing: I have the EEU version, idk if that's the root of all the problems I had.
Click to expand...
Click to collapse
This thread may help you:-
https://forum.xda-developers.com/redmi-note-8-pro/how-to/flashing-ota-fastboot-rom-tgz-xiaomi-t3993359

doop said:
This thread may help you:-
https://forum.xda-developers.com/redmi-note-8-pro/how-to/flashing-ota-fastboot-rom-tgz-xiaomi-t3993359
Click to expand...
Click to collapse
Well, I think I'm in condition n.1 "Can'boot to home screen but you can still enter recovery mode. Then download the firmware update.zip to install it via recovery mode.". As you can see, I've already tried flashing MIUI. It doesn't boot.

Vexx_zerozero said:
Well, I think I'm in condition n.1 "Can'boot to home screen but you can still enter recovery mode. Then download the firmware update.zip to install it via recovery mode.". As you can see, I've already tried flashing MIUI. It doesn't boot.
Click to expand...
Click to collapse
Seeing as you have already tried that I would move onto the flashing via fastboot or miflash method.

Hello. I'll close the thread here for now, as an user helped me to install Pixel Experience successfully. Thanks a lot for the help!
(for those who have problems with custom roms, in short: after flashing the zip file, go to the Advanced tab in the unofficial TWRP and choose "Close AVB2.0" and then "RM Encrypt". Apply both of these fixed with ALL the boxes checked for both options. Done!).

Are these steps correct to flash custom rom in 2020?

-use miunlock to unlock bootloader
-put phone on fastboot mode
-type 'fastboot flash antirbpass dummy.img'
-type 'fastboot flash recovery twrp-3.3.1-0-whyred.img'
-type 'fastboot reboot'
-reboot to recovery using phone
-copy gapps & custom rom to phone
-wipe system, data, dalvik, cache
-flash rom
-flash gapps
-reboot
I am currently on MIUI Global 9.5.19.0 with locked bootloader.
Is this method correct? I dont know which guide is outdated right now and which is not. Sorry if this is asked too many times.

Yes this is correct but i want to make some changes in your guide
1. Use orange fox recovery as it is better than twrp and it won't give u any error which u may encounter using twrp.
2. U can use fastboot boot *recovery* to push recovery file and flash its zip after entering recovery (it doesn't need any kind of dummy file flash)
3. Wiping vendor is also there
Thank you

oh ok so basically these are the edited steps to follow now:
-use miunlock to unlock bootloader
-put phone on fastboot mode
-boot twrp using 'fastboot boot XYZ.img'
-flash orange fox zip from twrp
-reboot to orange fox recovery from twrp
-wipe system, data, dalvik, cache, vendor
-flash latest firmware
-flash custom rom
-flash gapps
-flash magisk
-reboot
correct?
thanks a lot btw!

? correct and u can use 9.4.25 firmware as it is best (atleast for me)

Should I follow the same procedure if my phone is on 11.0.3.0?

scarednewbie said:
Should I follow the same procedure if my phone is on 11.0.3.0?
Click to expand...
Click to collapse
Now most of the customs support the new pie firmware.
1. Unlock bootloader.
2. Reboot to bootloader
3. Boot to orangefox recovery using
fastboot boot recoveryname.img
4. Copy the orangefoxrecovery.img(extract the orangefox zip) to device storage using the booted orangefox in step 3.
5. Flash orangefox permanently from the copied img file using the booted recovery.
4. If you are planning to use miui don't reboot without flashing magisk. It may reset the recovery to default miui recovery.
6. Enjoy flashing custom roms after wiping(not formating) system, data, cache, vendor etc. No need to format data if you need file ssystem encryption. Formating data from recovery will remove encryption.

niyas90 said:
Now most of the customs support the new pie firmware.
1. Unlock bootloader.
2. Reboot to bootloader
3. Boot to orangefox recovery using
fastboot boot recoveryname.img
4. Copy the orangefoxrecovery.img(extract the orangefox zip) to device storage using the booted orangefox in step 3.
5. Flash orangefox permanently from the copied img file using the booted recovery.
4. If you are planning to use miui don't reboot without flashing magisk. It may reset the recovery to default miui recovery.
6. Enjoy flashing custom roms after wiping(not formating) system, data, cache, vendor etc. No need to format data if you need file ssystem encryption. Formating data from recovery will remove encryption.
Click to expand...
Click to collapse
Orange fox recovery has aggressive stock recovery deactivation so magisk is not necessary