Related
Hi
Today I get my OnePlus 3T. So I did that, what I do with any new phone = TWRP and Root. So I...
1. Boot, download and install Oxygen OS 4
2. Fastboot unlock bootloader, flash TWRP (latest official build)
3. Reboot in TWRP and TWRP ask for password (never set any password for this phone, nothing! just start without sim and set nothing, only wifi for the first step)
4. Download SuperSU .zip and try to root - 0MB when I try to install SuperSu
5. TWRP > Wipe > Format data
6. Reboot and now I see (when I click on install) internal Storage (52100 MB). After that (dont flash SuperSU) just boot in TWRP
7. With OTG and USB stick I flash Oxygen OS 4.0 (full ROM with 1,4GB) > phone just reboot in TWRP.
When I go to
Wipe > Advanced Wipe > check Internal Storage > click on Repair or Change File System I get "invalid partition selection"
This also happen, when I check Dalvik/ART Cache. With System, Data and Cache no problems.
I have no idea what I can do. Over Google I only find some thread from Huawei and Samsung device, something with PIT file. Nothing to OnePlus (not One, not Two and not Three).
Klanac89 said:
Hi
Today I get my OnePlus 3T. So I did that, what I do with any new phone = TWRP and Root. So I...
1. Boot, download and install Oxygen OS 4
2. Fastboot unlock bootloader, flash TWRP (latest official build)
3. Reboot in TWRP and TWRP ask for password (never set any password for this phone, nothing! just start without sim and set nothing, only wifi for the first step)
4. Download SuperSU .zip and try to root - 0MB when I try to install SuperSu
5. TWRP > Wipe > Format data
6. Reboot and now I see (when I click on install) internal Storage (52100 MB). After that (dont flash SuperSU) just boot in TWRP
7. With OTG and USB stick I flash Oxygen OS 4.0 (full ROM with 1,4GB) > phone just reboot in TWRP.
When I go to
Wipe > Advanced Wipe > check Internal Storage > click on Repair or Change File System I get "invalid partition selection"
This also happen, when I check Dalvik/ART Cache. With System, Data and Cache no problems.
I have no idea what I can do. Over Google I only find some thread from Huawei and Samsung device, something with PIT file. Nothing to OnePlus (not One, not Two and not Three).
Click to expand...
Click to collapse
This question seems to keep repeating itself due to missing information on TWRP post about the latest official version being incompatible with OOS 4 encryption method, but that is the explanation. There is a beta release of TWRP in post 550 in that thread that is supposed to fix this.
Here's some spoon feeding for you
https://forum.xda-developers.com/showthread.php?t=3507308
Lookup post numbered 550 and it has a link to the unofficial TWRP update
What to do? Boot in beta1 and looks like the same... can flash OOS 4 but still the same problem.
Gesendet von meinem MI 5s Plus mit Tapatalk
First there are shortcuts for this, but I wanted to be sure I covered every step and where one is at each point, since it can be helpful for recovery or simply to see where one is. There are of course other ways but I just went through on a GM1917 and verified each of these steps, so that others do not need to piece together multiple threads. I'm assuming here we want to start from scratch, never a bad idea if you are willing to lose data, or else you have no choice and need to start from scratch.
Posts used:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585
https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I'm going to disable Encryption as well, because when written TWRP was not decrypting it and also because I find it a pain and simply put I do not need it on my phone, but those steps are optionally shown below, as well as root.
Next I'm doing this using files for the GM1917 (US/Internaltional), but you can replace both the fastboot version and the OTA for your device and the current version.
Before you begin: I'm assuming an unlocked boot loader
Be warned the steps below result in total loss of all DATA on the phone
Time: This takes about 45 minutes to an hour to complete.
I'm assuming you can get to fastboot mode, beyond that your phone can be seriously messed up, but as we are starting from scratch it should be ok.
Boot into Fastboot mode: (Vol- & Vol+ & power)
Use: 9.5.3-GM21AA-OnePlus7ProOxygen_21.O.07_OTA_007_all_1905120542_aa37bad-FASTBOOT to restore a prestine copy of 9.5.3 to slot A (only writes slot A)
Force it to power off on reboot (Vol+ & Power)
Reboot to fastboot mode (vol- & vol+ & power)
Now you should check which slot are you using with this command "fastboot getvar current-slot"
Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b"
Now you should flash the twrp in the boot partion using this command "fastboot flash boot twrp.img"
Now reboot the device with in recovery mode scrolling the menu with the volume button and selecting "Recovery Mode" with the power button
Now we have TWRP on Slot B and 9.5.3 on Slot A we are on Slot B
If asked to decrypt, if not skip this step: Format Data, Then Internal Storage, Data and cache
Upload the 9.5.4 OTA Image: adb push OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip /cache
Upload the twrp image: adb.exe push test-twrp-3.3.1-2-guacamole.img /cache
Now Install 9.5.4: using TWRP to slot B
- Install -> /cache -> OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip
Go in advanced menu
Click on "Install Recovery Ramdisk"
Choose the recoveryimgfilename.img
Swipe to install
Reboot -> Select Slot A
Reboot Select Recovery
We now have TWRP on slots A and B. 9.5.3 on Slot A and 9.5.4 on Slot B
Back in TWRP we are now on Slot A:
Upload the 9.5.4 OTA Image: adb push OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip /cache
Upload the twrp image: adb.exe push test-twrp-3.3.1-2-guacamole.img /cache
Now Install 9.5.4: using TWRP to slot B
- Install -> /cache -> OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip
Go in advanced menu
Click on "Install Recovery Ramdisk"
Choose the recoveryimgfilename.img
Swipe to install
We now have TWRP on slots A and B. 9.5.4 Slots A and B
At this point you can boot up 9.5.4 Stock from Slot A by selecting Reboot System or we can root / disable encryption
To disable encryption (suggested if you do not care as it makes TWRP easier):
Optional: block the ROM from encrypting storage as we can not currently decrypt.
upload the zip: adb push Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip /cache
- Install -> /cache -> Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
Note: this only affects the current slot (A in this case) which is fine
Reboot->System
At this point you have 9.5.4 Stock without Encryption on Slot A, With Encryption (and unused) on Slot B, and TWRP on Slots A and B.
Complete inital setup (I do the minimal at this point)
- Set a password, to verify if Dm-Verity_ForceEncrypt is working or not
Enable Developers Options
Enable Advanced Reboot in Developers Options
Note: My suggestion is to now power off and restart to ensure you have Wifi, as this is picky for some reason, and it is best to be sure.
Power -> Off
Power back on and verify that Wifi is still working, it should be.
If you want root:
Power -> Recovery
Upload Magisk: adb push Magisk-v19.2.zip /cache
- Install -> /cache -> Magisk-v19.2.zip
Wipe Dalvik
Reboot System
Finally: Verify that Safenet is passing in Magisk, it should be
You have 9.5.4 Stock with Encryption and Root on Slot A, With Encryption (and unused) on Slot B, and TWRP on Slots A and B. I hope having this in one place can help others, as I've tried to lay out exactly what I did each step of the way.
Parting suggestion: Maybe a good time to create a backup, one with EFS and Modem to just to be safe!
ERIC
I would love to leave this device permanently decrypted as well for convenience, but I do want lockscreen security enabled.
On the 6T, if you flash the dm_verity disabler zip, the drawback is that you couldn't enable lockscreen security. You could set a PIN, but the system would never recognize it, even if it was entered correctly. So once your screen went off, you had to either format internal storage from recovery to boot into a no-lockscreen system, or use file manager in TWRP to manually delete the files to disable lockscreen.
I'm thinking that 7Pro is the same way. Can someone confirm?
Thanks
reaper000 said:
I would love to leave this device permanently decrypted as well for convenience, but I do want lockscreen security enabled.
On the 6T, if you flash the dm_verity disabler zip, the drawback is that you couldn't enable lockscreen security. You could set a PIN, but the system would never recognize it, even if it was entered correctly. So once your screen went off, you had to either format internal storage from recovery to boot into a no-lockscreen system, or use file manager in TWRP to manually delete the files to disable lockscreen.
I'm thinking that 7Pro is the same way. Can someone confirm?
Thanks
Click to expand...
Click to collapse
I'm using A pattern, and fingerprint without issues. on 9.5.3 and 9.5.4.
ERIC
trying to use this guide and getting fastboot: unrecognised option `--set-active=b'
reaper000 said:
I would love to leave this device permanently decrypted as well for convenience, but I do want lockscreen security enabled.
On the 6T, if you flash the dm_verity disabler zip, the drawback is that you couldn't enable lockscreen security. You could set a PIN, but the system would never recognize it, even if it was entered correctly. So once your screen went off, you had to either format internal storage from recovery to boot into a no-lockscreen system, or use file manager in TWRP to manually delete the files to disable lockscreen.
I'm thinking that 7Pro is the same way. Can someone confirm?
Thanks
Click to expand...
Click to collapse
I saw o xXx Telegram that you can decrypt 7 Pro and also have lock screen security...
I too can confirm working lockscreen while remaining decrypted. Much appreciation to the OP!
Though I took a few shortcuts and used an otg USB drive, it still worked. Here's what I did:
(keep in mind that I am on 9.5.3, already had an unlocked bootloader, and had already used a patched boot.img that I injected via fastboot to achieve root)
To decrypt:
- downloaded dm_verity disable zip, magisk 19.2, and TWRP installer zip, and copied them to USB drive. Also, backup internal storage.
- used Magisk manager app to flash TWRP installer and Magisk 19.2
- reboot to recovery
- formatted internal storage (type yes, completely formatted the data partition and lost all media, photos, downloads, etc)
- twrp factory reset
- flashed dm-verity disabler zip and magisk 19.2 from otg USB drive
- reboot to system
Complete initial setup, repopulate internal storage with mefia (mp3, downloads, etc) from backup.
To upgrade to 9.5.4 once decrypted:
- download full 9.5.4 zip
- reboot to TWRP
- flash 9.5.4 zip and TWRP installer
- reboot to TWRP
- flash dm_verity disable zip and Magisk
- wipe dalvik
- reboot to system
Life is so much better decrypted.
earthbend said:
trying to use this guide and getting fastboot: unrecognised option `--set-active=b'
Click to expand...
Click to collapse
Need a newer version of fastboot this that case.
reaper000 said:
I too can confirm working lockscreen while remaining decrypted. Much appreciation to the OP!
Though I took a few shortcuts and used an otg USB drive, it still worked. Here's what I did:
(keep in mind that I am on 9.5.3, already had an unlocked bootloader, and had already used a patched boot.img that I injected via fastboot to achieve root)
To decrypt:
- downloaded dm_verity disable zip, magisk 19.2, and TWRP installer zip, and copied them to USB drive. Also, backup internal storage.
- used Magisk manager app to flash TWRP installer and Magisk 19.2
- reboot to recovery
- formatted internal storage (type yes, completely formatted the data partition and lost all media, photos, downloads, etc)
- twrp factory reset
- flashed dm-verity disabler zip and magisk 19.2 from otg USB drive
- reboot to system
Complete initial setup, repopulate internal storage with mefia (mp3, downloads, etc) from backup.
To upgrade to 9.5.4 once decrypted:
- download full 9.5.4 zip
- reboot to TWRP
- flash 9.5.4 zip and TWRP installer
- reboot to TWRP
- flash dm_verity disable zip and Magisk
- wipe dalvik
- reboot to system
Life is so much better decrypted.
Click to expand...
Click to collapse
I have tried your steps, but failed to decrypt the data partition.
I also tried different ways to flash:
* Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip then Magisk-v19.3.zip
* Magisk-v19.3.zip then Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
* Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip then Magisk-v19.3.zip then Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
but all failed.
My 1+7 Pro is GM1910.
Decryption is quite easy on my OnePlus 5T. Could you help me with some hint?
tinyfish said:
I have tried your steps, but failed to decrypt the data partition.
I also tried different ways to flash:
* Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip then Magisk-v19.3.zip
* Magisk-v19.3.zip then Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
* Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip then Magisk-v19.3.zip then Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
but all failed.
My 1+7 Pro is GM1910.
Decryption is quite easy on my OnePlus 5T. Could you help me with some hint?
Click to expand...
Click to collapse
I suppose "decrypt" is actually a misnomer.
The more accurate description is "disable forced encryption on initial and subsequent boots".
You aren't actually decrypting your current data partition, you're preventing a BLANK data partition from being encrypted upon initial boot of a virgin operating system.
The reason I'm saying all this is the most common reason for the no_verity disable zip to fail is because users have not done a factory reset AND not formatted their internal storage (you have to type the word "yes" or you haven't done it) before flashing no_verity and magisk.
Also ensure your no_verity disabler zip wasn't a bad download (md5 checksum)
If this doesn't work, then you're left with what I've termed a "scorched earth format" (you select everything except usb drive to wipe in advanced wipe, and then format internal storage with a typed yes). You then install FROM A USB DRIVE the latest full ota zip + twrp on both slots with the appropriate twrp reboots, then magisk + no_verity, twrp reboot then magisk yet again and finally system reboot.
reaper000 said:
I suppose "decrypt" is actually a misnomer.
The more accurate description is "disable forced encryption on initial and subsequent boots".
You aren't actually decrypting your current data partition, you're preventing a BLANK data partition from being encrypted upon initial boot of a virgin operating system.
The reason I'm saying all this is the most common reason for the no_verity disable zip to fail is because users have not done a factory reset AND not formatted their internal storage (you have to type the word "yes" or you haven't done it) before flashing no_verity and magisk.
Also ensure your no_verity disabler zip wasn't a bad download (md5 checksum)
If this doesn't work, then you're left with what I've termed a "scorched earth format" (you select everything except usb drive to wipe in advanced wipe, and then format internal storage with a typed yes). You then install FROM A USB DRIVE the latest full ota zip + twrp on both slots with the appropriate twrp reboots, then magisk + no_verity, twrp reboot then magisk yet again and finally system reboot.
Click to expand...
Click to collapse
I have formatted the data partition, and the Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip is valid.
Anyway I succeeded after upgrade to latest H2OS 9.5.5, with the same steps.
Thanks for your help.
Time-Saver!
QUOTE=egandt;79606005]First there are shortcuts for this, but I wanted to be sure I covered every step and where one is at each point, since it can be helpful for recovery or simply to see where one is. There are of course other ways but I just went through on a GM1917 and verified each of these steps, so that others do not need to piece together multiple threads. I'm assuming here we want to start from scratch, never a bad idea if you are willing to lose data, or else you have no choice and need to start from scratch.
Posts used:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
https://forum.xda-developers.com/oneplus-7-pro/how-to/oneplus-7-pro-global-repo-oxygen-os-t3930585
https://forum.xda-developers.com/oneplus-7-pro/development/recovery-unofficial-twrp-recovery-t3931322
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I'm going to disable Encryption as well, because when written TWRP was not decrypting it and also because I find it a pain and simply put I do not need it on my phone, but those steps are optionally shown below, as well as root.
Next I'm doing this using files for the GM1917 (US/Internaltional), but you can replace both the fastboot version and the OTA for your device and the current version.
Before you begin: I'm assuming an unlocked boot loader
Be warned the steps below result in total loss of all DATA on the phone
Time: This takes about 45 minutes to an hour to complete.
I'm assuming you can get to fastboot mode, beyond that your phone can be seriously messed up, but as we are starting from scratch it should be ok.
Boot into Fastboot mode: (Vol- & Vol+ & power)
Use: 9.5.3-GM21AA-OnePlus7ProOxygen_21.O.07_OTA_007_all_1905120542_aa37bad-FASTBOOT to restore a prestine copy of 9.5.3 to slot A (only writes slot A)
Force it to power off on reboot (Vol+ & Power)
Reboot to fastboot mode (vol- & vol+ & power)
Now you should check which slot are you using with this command "fastboot getvar current-slot"
Now you should change the slot in use with this command "fastboot --set-active=*" you should replace with the slot is not in use, for example if you are using slot a the command will be "fastboot --set-active=b"
Now you should flash the twrp in the boot partion using this command "fastboot flash boot twrp.img"
Now reboot the device with in recovery mode scrolling the menu with the volume button and selecting "Recovery Mode" with the power button
Now we have TWRP on Slot B and 9.5.3 on Slot A we are on Slot B
If asked to decrypt, if not skip this step: Format Data, Then Internal Storage, Data and cache
Upload the 9.5.4 OTA Image: adb push OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip /cache
Upload the twrp image: adb.exe push test-twrp-3.3.1-2-guacamole.img /cache
Now Install 9.5.4: using TWRP to slot B
- Install -> /cache -> OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip
Go in advanced menu
Click on "Install Recovery Ramdisk"
Choose the recoveryimgfilename.img
Swipe to install
Reboot -> Select Slot A
Reboot Select Recovery
We now have TWRP on slots A and B. 9.5.3 on Slot A and 9.5.4 on Slot B
Back in TWRP we are now on Slot A:
Upload the 9.5.4 OTA Image: adb push OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip /cache
Upload the twrp image: adb.exe push test-twrp-3.3.1-2-guacamole.img /cache
Now Install 9.5.4: using TWRP to slot B
- Install -> /cache -> OnePlus7ProOxygen_21.O.08_OTA_008_all_1905230032_1ef7fd0dc3.zip
Go in advanced menu
Click on "Install Recovery Ramdisk"
Choose the recoveryimgfilename.img
Swipe to install
We now have TWRP on slots A and B. 9.5.4 Slots A and B
At this point you can boot up 9.5.4 Stock from Slot A by selecting Reboot System or we can root / disable encryption
To disable encryption (suggested if you do not care as it makes TWRP easier):
Optional: block the ROM from encrypting storage as we can not currently decrypt.
upload the zip: adb push Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip /cache
- Install -> /cache -> Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip
Note: this only affects the current slot (A in this case) which is fine
Reboot->System
At this point you have 9.5.4 Stock without Encryption on Slot A, With Encryption (and unused) on Slot B, and TWRP on Slots A and B.
Complete inital setup (I do the minimal at this point)
- Set a password, to verify if Dm-Verity_ForceEncrypt is working or not
Enable Developers Options
Enable Advanced Reboot in Developers Options
Note: My suggestion is to now power off and restart to ensure you have Wifi, as this is picky for some reason, and it is best to be sure.
Power -> Off
Power back on and verify that Wifi is still working, it should be.
If you want root:
Power -> Recovery
Upload Magisk: adb push Magisk-v19.2.zip /cache
- Install -> /cache -> Magisk-v19.2.zip
Wipe Dalvik
Reboot System
Finally: Verify that Safenet is passing in Magisk, it should be
You have 9.5.4 Stock with Encryption and Root on Slot A, With Encryption (and unused) on Slot B, and TWRP on Slots A and B. I hope having this in one place can help others, as I've tried to lay out exactly what I did each step of the way.
Parting suggestion: Maybe a good time to create a backup, one with EFS and Modem to just to be safe!
ERIC[/QUOTE]
Hello @tinyfish
Just dropping a note to thank you for the procedure. I wanted to achieve the same thing and I have been doing so through my own trial-and-error (and I'm actually documenting my steps as I go with the same intention of sharing to the community).
Apparently someone already beat me to it and I even used this written procedure. It worked for me. Although there are a few "differences" in the way I did it:
1. Instead of OOS version 9.5.4 I used OOS version 9.5.13 which is the latest Android Pie for the OnePlus 7 Pro as of this writing.
2. I used the latest version of the "DM-Verity and Forced Encrypt Disabler" zip which is version 10.20.2019 as of this writing. The older version didn't work and resulted to "Settings" app force-closing and thereby preventing me from booting. I didn't investigate but I assume that the reason is because the 05.21.2019 version is "older" than the OOS version 9.5.13 that I was flashing. I could be wrong. But it is important that I write it here so that it is made known and investigated by someone who has the time/knowledge/energy for it.
There are certain important apps that I use that couldn't run properly on Android 10, so I had to revert to Android 9 (Pie).
Thank you once again!
Each ROM thread has a different installation guide.
So I was confused and tried various installation methods.
"Step 1/2" and "Step 2/2" shown during installation rom, probably means installation on each partition (A, B).
If so, this is the most COMPLETE way I have tried
[Clean Install]
0. reboot to TWRP
1. Format Data, Wipe Cache
2. reboot to recovery
3. Flash latest OOS (necessary)
4. Wipe Data, Cache
5. Flash ROM, TWRP
6. reboot to recovery
7. Flash gapps, magisk (If you do not want to be encrypted, flash disable force encryption)
8. reboot to system
[Update]
0. reboot to TWRP
1. Flash ROM(+TWRP)
2. reboot to recovery
3. Flash gapps, magisk (If you do not want to be encrypted, flash disable force encryption)
4. reboot to system
This series of roms is focused tu gain more performance for this series and add some other features to the rom, all of them are based in latest firrmware for each
How To install:
1) install TWRP for your device
2) enter in advance wipe and wipe dalvik, system,data,internal storage and cache
3) format data partition
4) flash the rom
5) 4) flash DM-verity
6) enjoy!!
A70:
to boot it must format data after install the rom
Download:mediafire
ROM OS Version: 10
ROM Kernel: Stock
ROM Firmware Required: Stock Android 10
Status: Stable
Created 31-08-2020
Last Updated 11-12-2020
In orden to boot the rom you need to flash DM-Verity after install the rom
Telegram Group for support and updates
wrong instruction for a705FN or this for a70MN only
MHMD NZMY said:
wrong instruction for a705FN or this for a70MN only
Click to expand...
Click to collapse
Wdym? All variants doesn't matter lmao
I'm on A705MN running latest TWRP and your instructions are not very clear. Here is what I am doing and get a bootloop
I advanced wipe cache, dalvik, data, system, internal storage
I format data and type "yes".
install add files for zip of rom, then add second zip of DM-verity
Both flash fine; do not reboot, but go to TWRP home and format data again per your instructions, type "yes"
then reboot system...and I get boot loop.
If my order is wrong please clarify.
Any prints?
gaderderian said:
I'm on A705MN running latest TWRP and your instructions are not very clear. Here is what I am doing and get a bootloop
I advanced wipe cache, dalvik, data, system, internal storage
I format data and type "yes".
install add files for zip of rom, then add second zip of DM-verity
Both flash fine; do not reboot, but go to TWRP home and format data again per your instructions, type "yes"
then reboot system...and I get boot loop.
If my order is wrong please clarify.
Click to expand...
Click to collapse
2.1 after format data, you need to reboot recovery
Anyone with A70? I installed Android 10 Stock Rom to install this Tutibreaker rom and the phone never started, the phone was in bootlogo and I repeated the process and instructions and the phone never started so I had to go back to Stock Rom and I got frustrated
Hi. I wanted to share with you this guide so you can flash newer Retrofit Dynamic Partitions on Redmi 7A/8A/8 devices.
These kind of ROM's can be found on SDM Mi439 Telegram group as well. Here are the instructions.
You will also need to use newer recoveries. For flashing Android 12+ rom I recommend official TWRP 3.7.0 for Mi439.
Download TWRP 3.7.0 here: CLICK ME!
Download OrangeFox here: CLICK ME!
(Note for OrangeFox: Use A11 version for Android 11 Roms, and A12 version for Android 12 and 13)
Instruction to flash newer ROMs with Retrofit Dynamic Partitions:
(Please Ignore recovery errors at the first installation, because every system partitions are blank at the moment)
(If you proceed with using old unsupported recoveries, You'll surely ending up getting errors)
First time installation of Retrofit Dynamic Partitions ROMs:
1. Flash recovery with Retrofit Dynamic Partitions support (Download Here)
2. Enter the newly flashed recovery
3. Flash Retrofit Dynamic Partitions Converter (Download Here)
4. Wipe metadata partition
5. Flash the ROM
6. Factory Reset (Format data is recommended) if you're coming from a different ROM
7. Reboot and Enjoy
Update ROM from Standard Partitions to Retrofit Dynamic Partitions:
Follow without Factory Reset step
Update ROM from Retrofit Dynamic Partitions to Retrofit Dynamic Partitions:
1. Enter recovery
2. Flash the update
3. Reboot and Enjoy
Switch to another Retrofit Dynamic Partitions ROM:
1. Enter recovery
2. Flash the ROM
3. Factory Reset (Format data is recommended)
4. Reboot and Enjoy
Revert back to standard partition ROM:
1. Enter recovery
2. Untick "Settings > Unmount System before installing a ZIP"
3. Do "Advanced > Unmap Super Devices"
4. Flash the ROM
5. Factory Reset (Format data is recommended)
6. Reboot and Enjoy
Warning! You can't flash static partition ROM on dynamic partitions and vice versa!
All ROMs that I post here are RDP (Retrofit Dynamic Partitions)!
works perfekt
thank you!
I rebooted after step 3 ( Flash Retrofit Dynamic Partitions Converter )
Now i am trapped in bootloader and installing twrp in boot or recovery didn't work.
How do i get back into recovery?
I think you need to reflash your ROM and try again.
Use same rom you have and download from this site https://xiaomifirmwareupdater.com/miui/pine/
You need to use fastboot on your pc.
But... Keep in mind I can be wrong. I have same problem restoring system partition with 12.5.3 miui using pbrp on my redmi 7a.
You could probably flash only recovery partition using CMD command on pc as well.
I hope it will help you.
lee99 said:
You could probably flash only recovery partition using CMD command on pc as well.
Click to expand...
Click to collapse
I tried to flash recovery using Terminal (Linux , the same way like i flashed twrp before installing the dynamic partitions, but it didn't work.
lee99 said:
I think you need to reflash your ROM and try again.
Use same rom you have and download from this site https://xiaomifirmwareupdater.com/miui/pine/
Click to expand...
Click to collapse
Yeah that was my solution, too.^^
After that i was more carefully and made exactly what the instructions told me and after wiping and formating data lineageos started =)
Thanks for your help =)
I am glad I could help
Do you have a video on how to install it on redmi 7a since I have a problem that gives me an error in everything I try in twrp 3.7.0
certerox said:
Do you have a video on how to install it on redmi 7a since I have a problem that gives me an error in everything I try in twrp 3.7.0
Click to expand...
Click to collapse
Hey I would like some help^^ I came from the stock MIUI rom and tried to flash it with the guide, went well with the help of the video but rebooted after step 3 and now the phone is stuck into fastboot and I cannot unbrick it.. I tried to flash TWRP again but still stuck, so now I'm trying to reinstall the stock MIUI rom.
The xiaomi website offers me two files, one "fastboot" and one "recovery". I tried to use MiFlash with these files but the app run like crap and keep giving me errors..
So I have the recovery zip file, inside there is a boot.img : I tried to flash that the same way I flashed TWRP with fastboot but the phone still is stuck in fastboot.
The fastboot file is a .tgz, inside there is a .tar and inside there is .bat files with the image but I cannot run the flash_all.bat with fastboot commands. I tried various all returned errors. I think I don't know the proper command to write as I'm noobish here : first time trying to flash
Any help appreciated I can't even turn the phone off lol I fear that the battery die and loose my phone
Edit : So it manage to unbrick it with the MiFlash app, just downloaded again and it worked fine this time ^^
Had to use the fastboot file, extracted and flash_all_lock option to make it work if someone face the same problem as me.
Hello
Nem1x said:
Hi. I wanted to share with you this guide so you can flash newer Retrofit Dynamic Partitions on Redmi 7A/8A/8 devices.
These kind of ROM's can be found on SDM Mi439 Telegram group as well. Here are the instructions.
You will also need to use newer recoveries. For flashing Android 12+ rom I recommend official TWRP 3.7.0 for Mi439.
Download TWRP 3.7.0 here: CLICK ME!
Instruction to flash newer ROMs with Retrofit Dynamic Partitions:
(Please Ignore recovery errors at the first installation, because every system partitions are blank at the moment)
(If you proceed with using old unsupported recoveries, You'll surely ending up getting errors)
First time installation of Retrofit Dynamic Partitions ROMs:
1. Flash recovery with Retrofit Dynamic Partitions support (Download Here)
2. Enter the newly flashed recovery
3. Flash Retrofit Dynamic Partitions Converter (Download Here)
4. Wipe metadata partition
5. Flash the ROM
6. Factory Reset (Format data is recommended) if you're coming from a different ROM
7. Reboot and Enjoy
Update ROM from Standard Partitions to Retrofit Dynamic Partitions:
Follow without Factory Reset step
Update ROM from Retrofit Dynamic Partitions to Retrofit Dynamic Partitions:
1. Enter recovery
2. Flash the update
3. Reboot and Enjoy
Switch to another Retrofit Dynamic Partitions ROM:
1. Enter recovery
2. Flash the ROM
3. Factory Reset (Format data is recommended)
4. Reboot and Enjoy
Revert back to standard partition ROM:
1. Enter recovery
2. Untick "Settings > Unmount System before installing a ZIP"
3. Do "Advanced > Unmap Super Devices"
4. Flash the ROM
5. Factory Reset (Format data is recommended)
6. Reboot and Enjoy
Warning! You can't flash static partition ROM on dynamic partitions and vice versa!
All ROMs that I post here are RDP (Retrofit Dynamic Partitions)!
Click to expand...
Click to collapse
Hello, the (to) retrofit dynamic partitions converter ROM doesn't work with [pine] - Redmi 7A. It is signed with [olive]. So this thread should be renamed or updated. THX
olivier_b said:
Hello
Hello, the (to) retrofit dynamic partitions converter ROM doesn't work with [pine] - Redmi 7A. It is signed with [olive]. So this thread should be renamed or updated. THX
Click to expand...
Click to collapse
You clearly didn't read the whole thread and it's title.
Men i really dont understand what is retrofit dynamic partition, when i used to install roms was with xiamitool v2 or flashing wiping data and thats it but this i really dont get it can you help me?
Nem1x said:
You clearly didn't read the whole thread and it's title.
Click to expand...
Click to collapse
That's true because this time I've read the guide and it works! Thx
Nem1x said:
Hi. I wanted to share with you this guide so you can flash newer Retrofit Dynamic Partitions on Redmi 7A/8A/8 devices.
These kind of ROM's can be found on SDM Mi439 Telegram group as well. Here are the instructions.
You will also need to use newer recoveries. For flashing Android 12+ rom I recommend official TWRP 3.7.0 for Mi439.
Download TWRP 3.7.0 here: CLICK ME!
Download OrangeFox here: CLICK ME!
(Note for OrangeFox: Use A11 version for Android 11 Roms, and A12 version for Android 12 and 13)
Instruction to flash newer ROMs with Retrofit Dynamic Partitions:
(Please Ignore recovery errors at the first installation, because every system partitions are blank at the moment)
(If you proceed with using old unsupported recoveries, You'll surely ending up getting errors)
First time installation of Retrofit Dynamic Partitions ROMs:
1. Flash recovery with Retrofit Dynamic Partitions support (Download Here)
2. Enter the newly flashed recovery
3. Flash Retrofit Dynamic Partitions Converter (Download Here)
4. Wipe metadata partition
5. Flash the ROM
6. Factory Reset (Format data is recommended) if you're coming from a different ROM
7. Reboot and Enjoy
Update ROM from Standard Partitions to Retrofit Dynamic Partitions:
Follow without Factory Reset step
Update ROM from Retrofit Dynamic Partitions to Retrofit Dynamic Partitions:
1. Enter recovery
2. Flash the update
3. Reboot and Enjoy
Switch to another Retrofit Dynamic Partitions ROM:
1. Enter recovery
2. Flash the ROM
3. Factory Reset (Format data is recommended)
4. Reboot and Enjoy
Revert back to standard partition ROM:
1. Enter recovery
2. Untick "Settings > Unmount System before installing a ZIP"
3. Do "Advanced > Unmap Super Devices"
4. Flash the ROM
5. Factory Reset (Format data is recommended)
6. Reboot and Enjoy
Warning! You can't flash static partition ROM on dynamic partitions and vice versa!
All ROMs that I post here are RDP (Retrofit Dynamic Partitions)!
Click to expand...
Click to collapse
Hi, i tried to flash the "Retrofit Dynamic Partitions Converter" but its shows me the "ERROR: This package is for device: pine, olives, mi439; this device is olive.
Updater process ended with ERROR: 7" / <image>. How to fix this.
iotzbruhh said:
Hi, i tried to flash the "Retrofit Dynamic Partitions Converter" but its shows me the "ERROR: This package is for device: pine, olives, mi439; this device is olive.
Updater process ended with ERROR: 7" / <image>. How to fix this.
Click to expand...
Click to collapse
Open twrp terminal and type mi439, then hit enter. Try to flash again.
For better experience use ofox recovery.
Nem1x said:
First time installation of Retrofit Dynamic Partitions ROMs:
1. Flash recovery with Retrofit Dynamic Partitions support (Download Here)
2. Enter the newly flashed recovery
3. Flash Retrofit Dynamic Partitions Converter (Download Here)
4. Wipe metadata partition
5. Flash the ROM
6. Factory Reset (Format data is recommended) if you're coming from a different ROM
7. Reboot and Enjoy
Click to expand...
Click to collapse
NOT WORK FOR PINE !
Used recommended TWRP 3.7.0
itmasen1 said:
NOT WORK FOR PINE !
Used recommended TWRP 3.7.0
Click to expand...
Click to collapse
Try using orangefox. And read guide again!