Code:
Flash at your own risk, i am NOT Responsible for any damage to your device, by flashing this you acknowledge that you have the required skills to recover your device in case something goes wrong
.
Hey guys last few days ive been dealing with trying to get the current twrp to read encrypted OREO data since our device got updated to OREO a few days back, finally today i was able to get TWRP to decrypt oreo data, and so we can make full nandroids and access data from twrp while on OREO.
FLashing instructions:
1.Download OREO TWRP 3.1.2
2.Boot into fastboot mode
3.Run these command:
Code:
fastboot flash recovery recovery.img
Code:
fastboot oem reboot-recovery
4.Optional Step; How to root OREO
Doownload Magisk 16.0
5.Boot into TWRP and flash magisk 16 zip
6.Reboot and enjoy!
All credits go to @shakalaca, all i did was replace zimage to oreo one.
Download file has the wrong name "twrp-3.2-OREO-Z01GD.img" "should be "twrp-3.2.1-OREO-Z01GD.img" my mistake! sorry, but rest assured it is the correct file, so flash away =]
Great work! However, for some reason my recovery fails to mount /data, saying that it's an invalid argument. If I go under change filesystem and make it EXT4, after a format of it I can access it.
Did you change the data partition format at some point? Thats odd, on my phone data was mounted correctly, I've even made a few nandroids, can you pull the recovery log and post it?
After I saw the problems with mounting the partition I tried to flash the system again, but I still get the same problem. The data partition should be EXT4, at least that's what it was in all my previous Nougat backups.
Since the recovery can't mount the data partition to write the log to here is a photo.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Question did you upgrade to oreo, if so did you follow the steps on my stock rom thread? The only that can happen is if you flashed oreo with no firmware and then went into twrp restored nougat system, this will encrypt your data to nougat which oreo recovery cant decrypt, but your screenshot says otherwise..hmm please can explain exactly what you did to flash the oreo recovery, thanks.
When flashing Oreo I used your no firmware image, I wiped the data partition first, then I booted into the system and went through the initial setup and went back to the stock Asus recovery to flash the firmware, then during boot there was a prompt that the device needs to be reset to factory settings so I did that.
After that I went though the initial set up again and flashed the new TWRP recovery, but during the Oreo flash I was using the old Nougat recovery, maybe that caused the problem.
I also tried reflashing everything according to the steps you wrote but it doesn't help.
EDIT: Is it possible that a wipe failed? Can I somehow force the relevant partitions to be recreated and the encryption keys to get regenerated?
Have you tried formating your storage with the oreo twrp?
I do wipe the internal storage and/or data but each time I reboot again the same problem occurs. The recovery says it decrypts Oreo user data, but it fails to mount it.
EDIT: I just tried flashing the no firmware ROM again and wiping internal storage after the initial setup, but at boot android encrypts it again and TWRP fails to mount it. So it has to be encryption that is causing this, but that makes little sense since TWRP seems to be able to decrypt the data partition just fine for other people. And TWRP also says the it succeeds in decrypting data but after that it fails to mount it.
panzerbeetle said:
I do wipe the internal storage and/or data but each time I reboot again the same problem occurs. The recovery says it decrypts Oreo user data, but it fails to mount it.
EDIT: I just tried flashing the no firmware ROM again and wiping internal storage after the initial setup, but at boot android encrypts it again and TWRP fails to mount it. So it has to be encryption that is causing this, but that makes little sense since TWRP seems to be able to decrypt the data partition just fine for other people. And TWRP also says the it succeeds in decrypting data but after that it fails to mount it.
Click to expand...
Click to collapse
Try this restore a nougat system partiton with oreo twrp boot it, then go back to oreo twrp and format internal.
So I flashed the old Nougat ROM without wiping anything using the new 3.2.1-0 TWRP and on boot it complained about failed decryption and I had to wipe data to continue booting, but now with Nougat TWRP mounts all partitions without any problems. But because of the new firmware I don't have sound on Nougat anymore, so I am forced to either somehow restore the old firmware or stay on Oreo.
Ok now flash oreo twrp, and format internal storage in advanced wipe, if that doesn't work, im going to try and make flashable firmware zips, unsure if we can downgrade tho, im almost certain you issue is that your data partition is still encrypted with nougat keys, at least that the only thing i can think of atm.
On a second note, it would helpful if someone else posted their experience with the oreo twrp, curius to know if your the only person with the issue, as in my device ive got no issue mounting data and storage on my oreo twrp.
It still won't budge even when I format the data and internal storage partitions on Oreo, on Nougat TWRP perfectly decrypts and mounts all the partitions. I was trying to look into where exactly the encryption keys are stored in Android, but from the looks of it, they should be generated on the first boot of each phone. And I do see the encryption screen pop up, so Oreo should be generating its own encryption keys and Nougat its own. It makes little sense that TWRP would fail to decrypt and mount Oreo. Maybe the next TWRP version will fix my bizarre problem.
EDIT: If the new Oreo TWRP can decrypt the partitions encrypted by Nougat when I flash it, wouldn't that mean that it should be able to decrypt data partition no matter what in the case I have Nougat encryption leftover?
panzerbeetle said:
It still won't budge even when I format the data and internal storage partitions on Oreo, on Nougat TWRP perfectly decrypts and mounts all the partitions. I was trying to look into where exactly the encryption keys are stored in Android, but from the looks of it, they should be generated on the first boot of each phone. And I do see the encryption screen pop up, so Oreo should be generating its own encryption keys and Nougat its own. It makes little sense that TWRP would fail to decrypt and mount Oreo. Maybe the next TWRP version will fix my bizarre problem.
EDIT: If the new Oreo TWRP can decrypt the partitions encrypted by Nougat when I flash it, wouldn't that mean that it should be able to decrypt data partition no matter what in the case I have Nougat encryption leftover?
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=962187416754475116 hey @panzerbeetle can you flash this please, it should fix your user data not mounting.
Awesome work, that fixed it!
What was the problem anyway?
I ran into the same issue, I updated to oreo 8.0.0 OTA on the ZS511KL before doing this and am on the 15.0410.1803.51 build with the March 1, 2018 security patch, bootloader unlocked through the official link (which I'm reminded of every time I power up the device)....the link you provided in the 2nd to last comment still did not fix the issue for me when I try to backup or flash zip files for magisk....this is my first go with ADB but I got TWRP up, but my results are the exact same as Panzerbeetle. I tried to flash the most up to date magisk 16.3 which failed, then the 16.0 which failed again...I've rooted before through ODIN on other devices which is a breeze, but I'm lost as to where I'm going wrong on this, any help or guidance is MUCH appreciated. I've been roaming through this site for about 3 years and just now created an account to see where I'm going wrong with this setup..
panzerbeetle said:
Awesome work, that fixed it!
What was the problem anyway?
Click to expand...
Click to collapse
Sooo...apparently i had uploaded the wrong recovery all along....i downloaded the one that was on mediafire and data did not mount, so i dumped my twrp and uploaded it for you guys to test, and yep it was my mistake all along, i apologies =/
rafyvitto said:
Sooo...apparently i had uploaded the wrong recovery all along....i downloaded the one that was on mediafire and data did not mount, so i dumped my twrp and uploaded it for you guys to test, and yep it was my mistake all along, i apologies =/
Click to expand...
Click to collapse
No problem, glad you managed to find the problem. Thanks again!
Saul93 said:
I ran into the same issue, I updated to oreo 8.0.0 OTA on the ZS511KL before doing this and am on the 15.0410.1803.51 build with the March 1, 2018 security patch, bootloader unlocked through the official link (which I'm reminded of every time I power up the device)....the link you provided in the 2nd to last comment still did not fix the issue for me when I try to backup or flash zip files for magisk....this is my first go with ADB but I got TWRP up, but my results are the exact same as Panzerbeetle. I tried to flash the most up to date magisk 16.3 which failed, then the 16.0 which failed again...I've rooted before through ODIN on other devices which is a breeze, but I'm lost as to where I'm going wrong on this, any help or guidance is MUCH appreciated. I've been roaming through this site for about 3 years and just now created an account to see where I'm going wrong with this setup..
Click to expand...
Click to collapse
Apparently you have a chinese asus zenfone 4 pro variant? if you do this twrp will most defiantly not work for you, send me your boot.img and i should be able to make one that works on your device.
Related
Unofficial release -TWRP recovery for the Samsung Galaxy Tab S3 - SM-T820/T825, Qualcomm MSM8996
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.2.1-0 Released
Dec 9, 2017
TWRP 3.2.1-0 is out now for most currently supported devices.
What's new in 3.2.1-0:
What's new in 3.2.1-0:
* minui fixes (cryptomilk)
* Better android-8.0 compatibility in ROM trees (Dees_Troy)
* Fix missing library in android-8.0 (nkk71)
* Fix inconsistent SDCard naming (DevUt)
* Default to TWRP restore instead of adb backup restore to fix restore on fresh TWRP boot (jlask)
Update 18/5/2018
TWRP 3.2.1-1 build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below) >> to be added
NTFS support
F2FS support >> To be added
Twrp app support
IMPORTANT:
PLEASE READ ALL OF THIS POST BEFORE FLASHING ANYTHING TO YOUR DEVICE.
WHATEVER YOU DO BEFORE FLASHING ANYTHING MAKE A BACKUP OF YOUR DEVICE AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE, DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
Flash with ODIN using the AP slot.
1. Put your device in DOWNLOAD mode.
2. Uncheck Auto reboot.
3. Load the respective file below into the AP slot and hit start.
4. After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
Failure to implicitly comply with step 4 will result in stock recovery replacing TWRP at first boot
NOTE: Since android 5.1.1 it is necessary to enable OEM Unlock.
Settings -> Developer Options -> OEM unlocking
ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
DOWNLOAD -
Device must be running at least AQD6 or later firmware. Earlier firmware may need the previous builds:
UPDATE: 18/5/2018 TWRP 3.2.1-1
twrp_3.2.1-1_T820_28518
twrp_3.2.1-1_T825_29518
UPDATE: 8/5/2017 TWRP 3.1.0-1
twrp_3.1.0-1_sm-t820_AQD6
twrp_3.1.0-1_sm-t825_AQD6
Previous builds:
SM-T820:
https://www.androidfilehost.com/?fid=745425885120721426
SM-T825:
https://www.androidfilehost.com/?fid=673368273298945058
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then Magisk needs flashing below to disable dm-verity.
Follow the instructions below to disable dmverity, forced encryption and mount internal storage(DATA):
MARSHMALLOW AND NOUGAT ONLY!:
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install Magisk
5. Reboot
OREO ONLY!:
To disable forced encryption, mount internal storage(DATA) and disable dm-verity:
1. Boot to TWRP
2. Install the Forced encryption patch: Tabs3_oreo_forced encryption_disabler
3. Format DATA using the *FORMAT DATA button* under the wipe options.
(NOTE - THIS WILL WIPE ALL INTERNAL STORAGE!)
4. Install Magisk
5. Reboot and check DATA is mountable
Done.
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
INSTRUCTIONS TO USE ADB BACKUP:
https://www.droidorigin.com/take-adb-backup-using-twrp-v3-1-0-0/
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @suzook, @jonathonalexander, Teamwin
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
RESERVED
Delete
Deleted.
ashyx said:
How do you mean it bootloops? I thought you said that you were able to mount the partitions and flash supersu?
Click to expand...
Click to collapse
I can. It flashes, and boots to TWRP., Partitions are mounted. But I can never reboot to system. It winds up bootlooping, even without flashing SuperSU.
suzook said:
I can. It flashes, and boots to TWRP., Partitions are mounted. But I can never reboot to system. It winds up bootlooping, even without flashing SuperSU.
Click to expand...
Click to collapse
Ah right, the issue isn't twrp, it's dmverity. If you allow modifications to system in twrp it triggers dm-verity which causes a boot loop.
To remedy this you need to disable it by either flashing SuperSU and/or the boot patch
Be aware that after flashing the boot patch you will need to FORMAT (not wipe) /DATA
The other alternative is to disable 'allow modifications to system'
However if you choose to disable modifications you will need to reflash twrp each time you reboot as it will be replaced by stock recovery.
.
ashyx said:
Ah right, the issue isn't twrp, it's dmverity. If you allow modifications to system in twrp it triggers dm-verity which causes a boot loop.
To remedy this you need to disable it by either flashing SuperSU and/or the boot patch
Be aware that after flashing the boot patch you will need to FORMAT (not wipe) /DATA
The other alternative is to disable 'allow modifications to system'
However if you choose to disable modifications you will need to reflash twrp each time you reboot as it will be replaced by stock recovery.
.
Click to expand...
Click to collapse
Format data for me at this point is fine, as I'm starting fresh again. Where is this boot patch? Will give it a try tonight.
suzook said:
Format data for me at this point is fine, as I'm starting fresh again. Where is this boot patch? Will give it a try tonight.
Click to expand...
Click to collapse
Its in the first post.
ashyx said:
Its in the first post.
Click to expand...
Click to collapse
, TWRP flashed, booting, and making backups. Supersu....No good. It flashes, but I have NO ROOT. Thoughts?
its failing on the boot.img patcher it states boot.img not found.
suzook said:
, TWRP flashed, booting, and making backups. Supersu....No good. It flashes, but I have NO ROOT. Thoughts?
its failing on the boot.img patcher it states boot.img not found.
Click to expand...
Click to collapse
I need the recovery log after installing supersu and boot.img patcher.
ashyx said:
I need the recovery log after installing supersu and boot.img patcher.
Click to expand...
Click to collapse
https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view?usp=drivesdk
suzook said:
https://drive.google.com/file/d/0BwPAGUQCA8FDN2pGWV9HSmdYNDQ/view?usp=drivesdk
Click to expand...
Click to collapse
Looks like Chainfires script can't find partitions defined as block devices. I must say a bit of an oversight by CF if that's the case.
Try this, recovery log if possible please after installing.
https://www.androidfilehost.com/?fid=529152257862715887
If there is still an issue I will patch the boot image manually.
.
ashyx said:
Looks like Chainfires script can't mount partitions defined as block devices. I must say a bit of an oversight by CF if that's the case.
Try this, recovery log if possible please after installing.
https://www.androidfilehost.com/?fid=529152257862715887
If there is still an issue I will patch the boot image manually.
.
Click to expand...
Click to collapse
Thanks, will give it a go, and post results and recovery log.
Edit...So flash this new recovery, then SuperSU, and the patch?
suzook said:
Thanks, will give it a go, and post results and recovery log.
Edit...So flash this new recovery, then SuperSU, and the patch?
Click to expand...
Click to collapse
Yes apply the patch after supersu to be on the safe side.
Wow, I haven't got the tab in my hands yet, and there's already recovery & root!
Have some beer: Confirmation number: 49581192XS319942M
ashyx said:
Yes apply the patch after supersu to be on the safe side.
Click to expand...
Click to collapse
Quick question, can I flash the latest TWRP you updated with the current TWRP installed? Or should I Odin it?
suzook said:
Quick question, can I flash the latest TWRP you updated with the current TWRP installed? Or should I Odin it?
Click to expand...
Click to collapse
Yep. Just extract it from the tar archive and then select install in twrp.
ashyx said:
Yep. Just extract it from the tar archive and then select install in twrp.
Click to expand...
Click to collapse
Latest TWRP does not mount partitions again
https://drive.google.com/file/d/0BwPAGUQCA8FDcmdCUWNXUnNRdEk/view?usp=drivesdk
Log
suzook said:
Latest TWRP does not mount partitions again
https://drive.google.com/file/d/0BwPAGUQCA8FDcmdCUWNXUnNRdEk/view?usp=drivesdk
Log
Click to expand...
Click to collapse
Damn, even defining the boot device in the command line doesn't allow named partitions to mount.
Back to the previous twrp then.
Looks like manual patching of the boot image is going to be required.
ashyx said:
Damn, even defining the boot device in the command line doesn't allow named partitions to mount.
Back to the previous twrp then.
Looks like manual patching of the boot image is going to be required.
Click to expand...
Click to collapse
Ok, sounds good. Ready to test whenever you need. I'm available rest of day, and all weekend. Thanks.
About this project
This project provides repackaged Stock Oreo roms that can be flashed by TWRP. Modifications from stock are listed below.
As we are now moving into the Oreo world, I've decided that now is a good time to make a few changes to how things were done previously with Nougat. Please pay attention to the next few sections.
Modifications from stock
Note - It seems that I can't get DM-verity nor forced encryption disabled. The location of the fstab.qcom file is no longer in the Boot image. I found a similar file in the system image, but changing that appears to have had no effect. In order to disable these, use Magisk. UPDATE - Resolved since soak test 2, and soak test 1 with Aroma installer
DM-verity is disabled
Forced encryption of the data partition is disabled. It is still possible to encrypt the partition if you wish (optional with Aroma installer)
The partition table and boot loader are not included, which makes it safer to up/down-grade.
Do not attempt to apply standard OTAs over these builds. They'll probably fail, worst case they will brick your phone
Differences from previous Nougat builds
These roms are suitable for all channels. Previously there was separate firmware for different regions (e.g. retin had a separate build from retus), but as a general rule you are safe with any region's firmware.
I have now started using the Aroma installer for Oreo builds. Some of the below is now customisable at install time. Aroma installer zips will have "-aroma" in their filename.
The modified boot logo will no longer be included in the rom download. A separate zip will be provided to just flash the modified logo.
EFS will be erased on install! If your persist is intact, EFS will recreate itself. With the amount of exposure that the lost IMEI issue has had, all should be very familiar with the importance of backing up persist and EFS. And those that have had a compromised persist, will know that they should be hanging on to their EFS backups for dear life. Full details of the issue and solution (for those with intact persist) is here: Fix Persist, resolve IMEI=0, Volte, 4G, Explanation, Requirements From my perspective, the EFS is erased installing OTAs for a reason. I don't know what it is myself, but the folks at Motorola build it into their OTAs and they know far better than I do.
As a mitigation to the risk of people forgetting/losing their EFS and / or Persist backups, I will have a very crude backup system integrated into the zips. However, it will take some skill / knowledge to restore from these backups, and they should not be relied upon over the long term. Refer to the second post for more details.
Important information if downgrading to Nougat and Custom Oreo roms
The Oreo roms will change the ownership of specific files and folders in the /persist folder. As a result of this, stock Nougat will have issues such as lost IMEI, no Volte, no 4G, etc. In order to overcome these issues, either follow the instructions in the link above, or flash the following zip in TWRP.
potter-stock-persist-fix.zip
Additionally, the latest Nougat builds with the Aroma installer will apply the persist fix when installed.
Another potential issue is that, as a result of various partitions being updated, the new Oreo blobs may not be compatible with existing Nougat roms (stock or custom), or even current Custom Oreo roms. This may result in issues such as the fingerprint reader not working, etc.
UPDATE: Some custom roms are now using the Oreo blobs. However, if you require the older Nougat blobs, you can downgrade through one of the following methods:
1) install one of the latest Stock Nougat TWRP flashables. This will ensure that all affected partitions are compatible with Stock Nougat and Custom Oreo roms. You can get these from this thread here:
[Nougat][Stock][Rom] TWRP Flashable Stock Builds
2) install one of the firmware-only zips from the below folders. Note that if this results in other odd behaviour, you may need to install and boot into a full stock Nougat firmware as above. The main benefit of these zips is that they are much smaller, ~50MB rather than ~1.4GB.
https://www.androidfilehost.com/?w=files&flid=273039
potter-firmware-92-14.zip is for retin, retla, retbr
potter-firmware-93-14.zip is for retus, retapac, reteu
Out of respect for the purpose of this thread, please keep questions about whether or not to use Nougat or Oreo firmware for particular custom ROMs in the thread for the custom ROM you are trying to use. I do not support other custom ROMs - the maintainers of those custom ROMs should provide guidance.
Usage
Steps to flash
Ensure you have the latest TWRP
Download an appropriate zip from one of the links below
Copy to the phone or SD card
BACKUP YOUR DATA, INCLUDING EFS AND PERSIST
Flash the zip via TWRP
Optionally flash Magisk etc - NOTE - in order to disable dm-verity and forced encryption you must flash magisk before rebooting Resolved since Soak Test 2 and Soak Test 1 Aroma installer, Magisk is optional
Reboot
Profit?
How you can help with new builds
If your phone gets an OTA notification for a build that has not been released, please pull it and share it in this thread:
When the notification is received, allow your phone to download the OTA
Power off and boot into recovery
Go to Advanced -> File Manager
Navigate to /cache
There will be a file Blur_Version_x.y.z.potter.blah.zip - Note - Oreo OTAs may not be named this way, they may be named according to the version of the rom that is currently installed
Copy it to internal storage or the sdcard
Copy to PC (optional)
Upload to Mega, Google Drive, wherever
Share the link
You can also remove the file from the /cache folder to prevent any auto-updates from happening.
Latest versions
The 85-13 series is released to most channels except retus, and the last update was to 85-17-2.
The 85-17 series is released to the retus channel.
However, all releases can be used with all channels.
Official Oreo OPSS28.85-17-6-2 (Oreo 8.1, 1 February 2019 security patches) - Aroma Installer
Android File Host - potter-twrp-flashable-OPSS28.85-17-6-2-aroma.zip
Official Oreo OPSS28.85-17-6 (Oreo 8.1, 1 February 2019 security patches) - Aroma Installer
Android File Host - potter-twrp-flashable-OPSS28.85-17-6-aroma.zip
All versions that I have created will be placed in this folder (or the Archive sub-folder) at Android File Host:
Android File Host - Potter TWRP Flashable Stock Oreo
Modified Boot Logo
Optional, only needs to be flashed once. Replaces the warning screen with the standard logo. Can't hide the N/A. If you want to hide the N/A, go to the themes forum.
potter-logo.zip
Kernel Sources
Kernel sources are provided by Motorola:
https://github.com/MotorolaMobilityLLC/kernel-msm/
XDA:DevDB Information
Potter Oreo TWRP Flashable, ROM for the Moto G5 Plus
Contributors
NZedPred
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Version Information
Status: Stable
Created 2018-08-17
Last Updated 2019-12-28
FAQs
Frequently Asked Questions
What is the 'very crude backup system integrated into the zips'?
This is a script that is run at the start of the install. It's purpose is very simple - it creates "dd backups" (i.e. bit-perfect images) of the modemst1/2 and persist partitions. They are stored in your sdcard as "backup_yyyymmddHHMMSS_modemst1.img", etc., where yyyymmddHHMMSS represents the date and time the script was run.
For this to work, your data partition must be mounted. I haven't included any checks for this (I'm not really a shell script person - it would take me hours to get this sort of thing right) - this is what puts the "crude" in "very crude backup system". UPDATE - the aroma installers now check that data is mounted, and abort the install if not. Most of the time the data partition will be mounted in TWRP, so this will work 99% of the time. Caution should still be applied, and you should still copy these or any other backups to cloud storage to be safe.
OK, so if I needed to use these backups, how do I restore them?
To restore these, you will have to reboot into TWRP and open up a shell or use adb. The commands to restore each partition are as follows (replacing yyyymmddHHMMSS with the appropriate values of course):
Code:
dd if=/sdcard/backup_yyyymmddHHMMSS_modemst1.img of=/dev/block/bootdevice/by-name/modemst1
dd if=/sdcard/backup_yyyymmddHHMMSS_modemst2.img of=/dev/block/bootdevice/by-name/modemst2
dd if=/sdcard/backup_yyyymmddHHMMSS_persist.img of=/dev/block/bootdevice/by-name/persist
Note that these commands are very powerful, and applied incorrectly can result in you bricking your phone if you overwrite the wrong partition.
So are dm-verity and forced encryption now not able to be disabled?
OK some history... Nougat had fstab (file system table) in the boot image. So in those days, I would open up the image, and edit the fstab.qcom file, do the appropriate changes, repack the boot image, and all is fine.
Now, under Oreo, the fstab file is not in the boot image, it's under /system/vendor/etc/fstab.qcom or similar. Editing that file appears to have no effect. For now, Magisk is the easiest way of disabling both, but you must make sure to install it immediately after installing the rom and before rebooting.
Update - this is now resolved in the second Oreo soak test download. dm-verity is still disabled in the boot image, but a completely different way. Once this is done, disabling forced encryption works as expected.
Which partitions are modified?
The short of it is this - boot, system and 'firmware'-related partitions. None of the bootloader partitions are updated. The full list of partitions that are written is:
modem
fsg
dsp
boot
system
oem
Note that this list applies to the Nougat and Oreo flashable zips.
TWRP is no longer installed after flashing this
I believe this is related to dm-verity (see above). You will have to first reinstall TWRP via fastboot. When TWRP is back, install magisk immediately after installing the rom, and before rebooting.
I'm having problems with an Oreo custom rom after installing this rom, what can I do?
Refer to the OP, the section about downgrading to Nougat - the same approach applies. Oreo Custom roms will have been based upon the available Nougat blobs that were available. As the blobs have been updated in the Oreo release, the issue is that they are not compatible. So install a full TWRP Nougat zip and then install your Oreo Custom rom.
Dirty or clean flash?
I did a dirty flash, as I came from the latest Nougat stock rom. Keep in mind that this is nothing more than the OTA applied to the previous Nougat build and packaged into a TWRP zip. So, as long as you have come from (the latest) Stock Nougat, you should be able to dirty flash, as that would be the use-case for the OTA. If you were on another rom, clean flash required.
Once you are on one of these builds, you can dirty flash subsequent builds. Again, this would be just like flashing one OTA after the other. Also note that these builds are complete in their own right, you don't need to incrementally flash - you can flash the latest to get the full install.
My device was encrypted, and I really need to decrypt it. How can I do this?
Sorry, but the only way is to format the data partition. That means you will need to backup your data, and your internal storage as well (/sdcard). After backing up, use TWRP to format the partition. From the TWRP main menu, select Wipe > Format Data. Then follow the on-screen instructions.
Is it 32 bit or 64 bit
32 bit. We've known this would be the case for a long time.
How can I create flashable zips myself?
I created the guide below, and it has been updated for Oreo. A word of warning, it is not for the faint of heart. You will need to have a good understanding of the Linux command line, and be able to understand the techniques that are being taught, rather than expecting that the process is a 'step-by-step'. Adaptability is key here.
[GUIDE] Creating TWRP Flashbale Stock roms
What are the new Aroma zips?
The aroma zips use the Aroma installer. Some of you may have seen the Aroma installer for Open Gapps. The key here is that I, as the packager, can build in selection options into the installer. It's all available as a nice GUI for the users to pick and choose from the options I've provided. Here are the options that are available:
Do backups - does the backups as mentioned earlier in the FAQs.
Erase EFS - erases modemst1 and modemst2, as described in the first post. Also DDR is erased, but I'm not sure what purpose that has but it may as well go together with these.
Install Firmware - installs the following partitions - modem, fsg, dsp; each of these has something to do with hardware / connectivity.
Install System - Installs the following partitions - boot, system, oem.
Apply patches - as long as Install System is selected, will install the patched boot image with dm-verity disabled, and will edit the fstab (filesystem table) to disable forced encryption.
On soak test 2 or later, I have my IMEI but no signal. What can I do?
In all cases where this has happened, the user's phone has relied upon an EFS backup for IMEI, due to flashing another persist. In these cases, it appears that the only way to get a signal is to use the firmware (i.e. modem, fsg, dsp - refer previous FAQ) from soak test 1. We're probably seeing here that the EFS does in fact need to be recreated to be valid. Unfortunately for these users, by not having their own persist, they are stuck with an old EFS and the newer firmwares appear to not work.
To do this
if you are already on Soak Test 2 or later, download the Soak Test 1 firmware download at either of these links:
Android File Host - oreo-soak1-firmware.zip
Dropbox - oreo-soak1-firmware.zip
If you are on Soak Test 1, install Soak Test 2 or later / official aroma installer and de-select firmware
My fingerprint is not working on my custom ROM
Refer to the thread for your custom ROM, and ask questions there. In short, Nougat and Oreo firmware are not compatible with each other. Many custom ROMs are now using Oreo firmware, whereas previously (before October 2018) pretty much all custom ROMs were using Nougat firmware. It's messy now, but please ask the questions in the right place (which is NOT this thread).
My touchscreen isn't working after flashing, even within TWRP
This seems to happen somewhat rarely, although I don't know what the cause is. As it affects TWRP as well, and TWRP uses the 'modem' partition for getting its firmware blobs, I guess it's possible that this particular partition is getting a conflicting modification whilst flashing, which is causing problems (but this is purely speculation on my part).
To solve, fastboot flashing the stock ROM appears to work. It may also be possible whilst in TWRP to manually flash the partitions via ADB, but that takes a bit of work and knowledge. Until someone can truly work out what's happening and the minimum required to fix it, stick with fastboot.
Update - refer to post #3 for the latest information about this issue.
Touch screen unresponsive even in TWRP
The below post has the latest information on the Touch Screen Unresponsive issue
Likely Cause
From the testing that I've done to reproduce the issue, as far as I can tell the issue is that Stock Oreo is not able to be safely applied over the top of old builds of Stock Nougat. Furthermore, it doesn't seem to matter if you were on Custom ROMs after you were last on Stock Nougat, just what Stock Nougat build you were on last.
Avoiding the Issue
Again the key here is what build of Stock you were on last (and I guess booted into). So, if you were never on Stock Oreo, and you aren't sure what version of Stock Nougat you were on last, then the safest path to getting these builds working is to first flash the latest Nougat Stock ROM.
Get the latest from this thread: [Nougat][Stock][Rom] TWRP Flashable Stock Builds
Once you have flashed the latest Nougat, boot once to make sure everything is working. After that, you should be able to safely upgrade to Oreo.
Fixing the Issue
If you have been affected by the issue, most people have been able to get back the touch screen functionality by flashing a fastboot version of the ROM. However, as long as you have a PC handy you will be able to flash using TWRP as well via adb, using the steps detailed below. A third option is to connect a USB Mouse via an USB OTG adapter.
Note that for either method via TWRP, you cannot use the versions of the ROM with the Aroma installer, as the mouse is not supported within, and there is no way of providing input by adb.
Downloads
The 92-14 or 93-14 versions should be suitable. They are in these links (these do not erase EFS, so for the paranoid, you will retain your IMEI):
twrp-flashable-potter-NPNS25.137-92-14-no-erase-modemst.zip
twrp-flashable-potter-NPNS25.137-93-14-no-erase-modemst.zip
TWRP Commands
Once in TWRP, connect your USB cable. To copy the downloaded file into your internal storage (adapt the filename for the version you downloaded):
Code:
adb push twrp-flashable-potter-NPNS25.137-92-14-no-erase-modemst.zip /sdcard/
If you want to backup, you can do this via the command line as well. I haven't tested this myself, but the commands are available here: https://www.pocketables.com/2014/10/using-twrps-new-adb-interface.html
The example provided uses the following to back up system, data and boot, and compress:
Code:
adb shell twrp backup SDBOM
You will need to do a clean flash, so these commands will wipe data / factory reset and then install
Code:
adb shell
twrp wipe data
twrp install /sdcard/twrp-flashable-potter-NPNS25.137-92-14-no-erase-modemst.zip
reboot
After the reboot, you should have your touch screen functionality back. Then reboot to recovery, and install Oreo as normal. If for any reason the Oreo flash doesn't work, try the steps again, but rather than installing the latest Oreo, install an earlier one.
Awesome bro...
You Rock...
you even included auto backup of efs and persist ... wow thats very thoughtfull and nice of you...
hatsoff..
:good::good:
Thanks dude, downloading
Edit: working like a charm, again thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks for uploading. Two questions though...
1. which one would be suitable for retin? (India)
2. Are there any bugs?
working for retin also thnx
Question: I'd like to flash this, but I'm planning to roll back in the future to take the OTA back up to O. If I restore nougat system, boot, persist, recovery, oem will that still be possible? I see some other stuff in the zip like adspo.bin, fsg.mbn, and modem. Not sure if those it lead to OTA failures or a brick.
also, nice job on the persist/efs script!
Worked on retin also thanks. Great work!!!!
I'm pretty sure forced encryption of the data partition is still enabled.
pfonck said:
I think forced encryption of the data partition is still enabled (formatting the data partition in TWRP does not help).
Click to expand...
Click to collapse
If that's the case magisk is probably needed to turn it off. Sorry, but I've only tested it with magisk installed. Moto have changed the fstab location, I thought I got it but maybe it's cosmetic and doesn't do anything. Will update OP when I get a chance.
NZedPred said:
If that's the case magisk is probably needed to turn it off. Sorry, but I've only tested it with magisk installed. Moto have changed the fstab location, I thought I got it but maybe it's cosmetic and doesn't do anything. Will update OP when I get a chance.
Click to expand...
Click to collapse
Yes, when you do;
rom installation > format data > flash magisk
everything is okay
verified.
Did Moto make Oreo 64bit?
redbeard1083 said:
Question: I'd like to flash this, but I'm planning to roll back in the future to take the OTA back up to O. If I restore nougat system, boot, persist, recovery, oem will that still be possible? I see some other stuff in the zip like adspo.bin, fsg.mbn, and modem. Not sure if those it lead to OTA failures or a brick.
also, nice job on the persist/efs script!
Click to expand...
Click to collapse
Good question, and this is something that I needed to consider before doing this, in case everyone installed this and we'd have no path to get to official Oreo.
Refer to the section in the OP "Important information if downgrading to Nougat". Basically you need to follow all of that to be able to get notification of the OTAs. Once the official public Oreo OTA is available, I will then put together a zip based upon the pre-requisite nougat rom with the official Oreo OTA.
I also believe that one or both of the 1 July 2018 and/or 1 August 2018 patches were announced, but neither were for Oreo. I do intend to keep Nougat up to date as well in its thread.
NZedPred said:
Good question, and this is something that I needed to consider before doing this, in case everyone installed this and we'd have no path to get to official Oreo.
Refer to the section in the OP "Important information if downgrading to Nougat". Basically you need to follow all of that to be able to get notification of the OTAs. Once the official public Oreo OTA is available, I will then put together a zip based upon the pre-requisite nougat rom with the official Oreo OTA.
I also believe that one or both of the 1 July 2018 and/or 1 August 2018 patches were announced, but neither were for Oreo. I do intend to keep Nougat up to date as well in its thread.
Click to expand...
Click to collapse
How did a recovery come in? with volume - and power enters and I say without command
JC Pzy said:
How did a recovery come in? with volume - and power enters and I say without command
Click to expand...
Click to collapse
I've only just added something to the FAQ (post 2) that covers this. Sorry, it was unexpected and didn't come up when I was testing as I always had magisk installed. Follow these steps:
TWRP is no longer installed after flashing this
I believe this is related to dm-verity (see above). You will have to first reinstall TWRP via fastboot. When TWRP is back, install magisk immediately after installing the rom, and before rebooting.
NZedPred said:
I've only just added something to the FAQ (post 2) that covers this. Sorry, it was unexpected and didn't come up when I was testing as I always had magisk installed. Follow these steps:
TWRP is no longer installed after flashing this
I believe this is related to dm-verity (see above). You will have to first reinstall TWRP via fastboot. When TWRP is back, install magisk immediately after installing the rom, and before rebooting.
Click to expand...
Click to collapse
I do not have a PC to reinstall the recovery
NZedPred said:
Good question, and this is something that I needed to consider before doing this, in case everyone installed this and we'd have no path to get to official Oreo.
Refer to the section in the OP "Important information if downgrading to Nougat". Basically you need to follow all of that to be able to get notification of the OTAs. Once the official public Oreo OTA is available, I will then put together a zip based upon the pre-requisite nougat rom with the official Oreo OTA.
I also believe that one or both of the 1 July 2018 and/or 1 August 2018 patches were announced, but neither were for Oreo. I do intend to keep Nougat up to date as well in its thread.
Click to expand...
Click to collapse
Maybe I'll try tweaking the zip to see if we can run it without the stuff we can't easily backup/restore with twrp. I'll take a stab at it shortly and let you know what happens if we flash just system, boot, and OEM.
redbeard1083 said:
Maybe I'll try tweaking the zip to see if we can run it without the stuff we can't easily backup/restore with twrp. I'll take a stab at it shortly and let you know what happens if we flash just system, boot, and OEM.
Click to expand...
Click to collapse
You can give it a go, but I've already done some very brief testing. Using the Nougat modem partition on the Oreo system results in things like 3G only, fingerprint not working.
JC Pzy said:
I do not have a PC to reinstall the recovery
Click to expand...
Click to collapse
I'm guessing you don't have root either? If you did, you could try installing it from a shell from within the rom:
Code:
su
dd if=/path/to/twrp.img of=/dev/block/bootdevice/by-name/recovery
Hi,
after flashing TWRP 3.5.2_11-Nebrassy on my Redmi Note 10 (sunny) and flashing Havoc OS after reboot I always come back to twrp. Cannot boot Havoc OS. And I see E: Unable to decrypt FBE device. What should I do to resolve this problem?
dario-20 said:
Hi,
after flashing TWRP 3.5.2_11-Nebrassy on my Redmi Note 10 (sunny) and flashing Havoc OS after reboot I always come back to twrp. Cannot boot Havoc OS. And I see E: Unable to decrypt FBE device. What should I do to resolve this problem?
Click to expand...
Click to collapse
Always wipe dalvic cache data storage and format data before you flash any rom
It
akoaypinoy said:
Always wipe dalvic cache data storage and format data before you flash any rom
Click to expand...
Click to collapse
It was done! But still have the same error and still come back to trwp instead of the new rom (Havoc). :-(
dario-20 said:
It
It was done! But still have the same error and still come back to trwp instead of the new rom (Havoc). :-(
Click to expand...
Click to collapse
How you flash havoc? Vanilla or Gapps version?
akoaypinoy said:
How you flash havoc? Vanilla or Gapps version?
Click to expand...
Click to collapse
Gapps
If you installed a new rom, clear the data and delvik cache at the end.
StaryMuz said:
If you installed a new rom, clear the data and delvik cache at the end.
Click to expand...
Click to collapse
I did this. Every time when I reboot it always comes back to twrp. Strange! In my opinion it is a matter of error: E: Unable to decrypt FBE device. How to overcome it?
Ok, finally I found solution: Installed OrangeFox https://forum.xda-developers.com/t/orangefox-recovery-for-redmi-note-10-sunny-mojito.4293709/
and no problem! Maybe this will be helpfull for somebody else...
dario-20 said:
I did this. Every time when I reboot it always comes back to twrp. Strange! In my opinion it is a matter of error: E: Unable to decrypt FBE device. How to overcome it?
Ok, finally I found solution: Installed OrangeFox https://forum.xda-developers.com/t/orangefox-recovery-for-redmi-note-10-sunny-mojito.4293709/
and no problem! Maybe this will be helpfull for somebody else...
Click to expand...
Click to collapse
That's weird, havoc is not kind of caf rom , hnnn
akoaypinoy said:
That's weird, havoc is not kind of caf rom , hnnn
Click to expand...
Click to collapse
After this installation I cannot boot into recovery! Probably I installed twrp in wrong way for the very first time. But still don't know how to make it right. It means when I install twrp in the wright way I cannot install Havoc... Maybe tommorow I will try to come back to twrp...
The correct way to install TWRP is to run it without installing it first and then install it to the ramdisk. If you do it any other way, you will delete the boot and replace it only with the recovery one. Then the phone can't go anywhere but recovery.
only boot from twrp. dont flash it
inn0ichi said:
only boot from twrp. dont flash it
Click to expand...
Click to collapse
Thank you very much for your responses. What does it mean exactly now in my situation? What steps should be exactly taken now by me?
dario-20 said:
Thank you very much for your responses. What does it mean exactly now in my situation? What steps should be exactly taken now by me?
Click to expand...
Click to collapse
fastboot boot twrp.img
Automatic it reboot to twrp recovery ,next steps is
Go to mount and check if mtp is enable once mtp enable go to your phone storage then paste twrp.image on internal storage of your phone ,once you place that twrp. Disconnect your USB cord on phone then go to advance/flash on ramdisk/then you will click the TWRP img. And flash .
That's it
I recommend a different procedure. Take the boot.img file from the ZIP file of the installed ROM. Then flash it in fastboot with the fastboot flash boot boot.img command. This should boot the ROM normally. You will at that point have a stock recovery of the ROM. To change it you must follow the specific installation procedure, otherwise you will not start the ROM again. If you cannot get the boot.img from the ZIP file, you must reinstall the entire ROM.
akoaypinoy said:
fastboot boot twrp.img
Automatic it reboot to twrp recovery ,next steps is
Go to mount and check if mtp is enable once mtp enable go to your phone storage then paste twrp.image on internal storage of your phone ,once you place that twrp. Disconnect your USB cord on phone then go to advance/flash on ramdisk/then you will click the TWRP img. And flash .
That's it
Click to expand...
Click to collapse
Thanks but: Now I am on OrangeFox recovery (which I cannot boot - it was the last flashed recovery). Typing fastboot boot twrp.img gives back: not found
What do you suggest in this situation?
StaryMuz said:
I recommend a different procedure. Take the boot.img file from the ZIP file of the installed ROM. Then flash it in fastboot with the fastboot flash boot boot.img command. This should boot the ROM normally. You will at that point have a stock recovery of the ROM. To change it you must follow the specific installation procedure, otherwise you will not start the ROM again. If you cannot get the boot.img from the ZIP file, you must reinstall the entire ROM.
Click to expand...
Click to collapse
In the ZIP file of HAVOC ROM there were no boot.img file :-(
So I am still on OrangeFox which I cannot boot. I only can boot the ROM (HAVOC). So if I understand you well I should reinstall my ROM (loosing my data), yes?
Reinstalling the ROM will not delete the data itself. You must not delete data before or after installation.
Reinstallation should not need data deletion.
For what reason are you trying to change the recovery included in the ROM?
I can also offer to pull the boot.img from the ZIP ROM. But you would have to give me a link to the ZIP file you used.
StaryMuz said:
Reinstalling the ROM will not delete the data itself. You must not delete data before or after installation.
Reinstallation should not need data deletion.
For what reason are you trying to change the recovery included in the ROM?
I can also offer to pull the boot.img from the ZIP ROM. But you would have to give me a link to the ZIP file you used.
Click to expand...
Click to collapse
Okay but now I cannot install anything because I have no access to recovery! Maybe I explain what I did:
1. Installed TWRP in wrong way (Error: unable to decrypt FBE device and unable to mount data)
2. Installed OrangeFox (zip file through TWRP)
3. Installed Havoc OS
4. Now I have no access to OrangeFox. I have access only to recovery of Havoc OS ROM. But it is useless because I can do nothing with it.
4. How can I start the new flashing of TWRP the proper way? I don't care about the present HAVOC OS because I have a backup of my all data.
5. I want TWRP or OrangeFox recocery for installing Magisk (rooting) what is now impossible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reboot to recovery → I return to the same recovery as above.
dario-20 said:
In the ZIP file of HAVOC ROM there were no boot.img file :-(
So I am still on OrangeFox which I cannot boot. I only can boot the ROM (HAVOC). So if I understand you well I should reinstall my ROM (loosing my data), yes?
Click to expand...
Click to collapse
orangefox is that your recovery now. Orangefox and twrp are recovery both. The difference is that orangefox can no flash the kernel unlike twrp. Please be specific what you are doing,
Orangefox and twrp are recovery
HavocOS is a rom
Before you do make specific, or else you get messed.
dario-20 said:
Okay but now I cannot install anything because I have no access to recovery! Maybe I explain what I did:
1. Installed TWRP in wrong way (Error: unable to decrypt FBE device and unable to mount data)
2. Installed OrangeFox (zip file through TWRP)
3. Installed Havoc OS
4. Now I have no access to OrangeFox. I have access only to recovery of Havoc OS ROM. But it is useless because I can do nothing with it.
4. How can I start the new flashing of TWRP the proper way? I don't care about the present HAVOC OS because I have a backup of my all data.
5. I want TWRP or OrangeFox recocery for installing Magisk (rooting) what is now impossible.
View attachment 5449627View attachment 5449629
Reboot to recovery → I return to the same recovery as above.
Click to expand...
Click to collapse
Everytime you install a new make it read . Because other rom have own recovery. (Ex. Pixelplus) once you install that automatically you have a pe recovery once it reboot , so the proper way to maintain twrp is "flash current twrp" which you can find in advance in twrp recovery. Remember once you flash a new rom don't reboot and go to advance then flash the current twrp. After that reboot.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP recovery 3.6.1 for lancelot(redmi 9 | lancelot/galahad)
Code:
I am not responsible for your brick devices.
The recovery is fully working and has been tested.
If you encounter a problem, write here, maybe they will help you.
Before you accuse me of doing something wrong, take a look at how you use your smartphone.
You don't need to blame me for turning your device into a brick with my recovery, it's not my fault.
Attention!The recovery is fully operational, it can make backups, install backups, it was tested only on custom Roms, but not on MIUI, but it should also work there.
Install:
To install, simply flash img to the recovery section and then reboot.
If you want to flash via fastboot, do the following:
fastboot --disable-verity --disable-verification flash vbmeta your_name_vbmeta.img
fastboot erase recovery
fastboot flash recovery your_name_recovery.img
fastboot reboot recovery
After that, you will find yourself in a new recovery.
Be careful when flashing!
Version Information
Status: Stable
Changelog:
Spoiler
24.03.2022
- inital build
- mtp not worked (For full operation, flash the ROM again through a new recovery!)
downloads:
Mega | GDrive
Information:
TWRP recovery for lancelot/galahad | redmi 9
Contributors
Furry__wolf
Credits:
TheGame455
Randomas3000
zubairk22oct
GADGETNiK
ExpressLuke
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp
https://github.com/Redmi-MT6768/omni_device_xiaomi_lancelot
Hi,
I'm currently on MIUI V12.5.4.0.RJCEUXM. I follow your instructions, flash vbmeta, erase, etc., but TWRP is still replaced by MIUI recovery after reboot to system. I can reboot to recovery directly from fastboot, but then /sdcard contains folders with weird names. I guess it is encrypted.
My goal is to create IMEI backup, but I'm afraid to run imei-backup.zip, when /sdcard is not proper. I have tried SHRP with the same results.
I have 2 questions:
- Is there alternative of imei-backup, that saves data to external SD or USB-OTG?
- If I use this TWRP to install LineageOS or CrDroid, would I get normal access to /sdcard?
popej said:
Hi,
I'm currently on MIUI V12.5.4.0.RJCEUXM. I follow your instructions, flash vbmeta, erase, etc., but TWRP is still replaced by MIUI recovery after reboot to system. I can reboot to recovery directly from fastboot, but then /sdcard contains folders with weird names. I guess it is encrypted.
My goal is to create IMEI backup, but I'm afraid to run imei-backup.zip, when /sdcard is not proper. I have tried SHRP with the same results.
I have 2 questions:
- Is there alternative of imei-backup, that saves data to external SD or USB-OTG?
- If I use this TWRP to install LineageOS or CrDroid, would I get normal access to /sdcard?
Click to expand...
Click to collapse
Use another recovery. So that it is not replaced by this archive
popej said:
Hi,
I'm currently on MIUI V12.5.4.0.RJCEUXM. I follow your instructions, flash vbmeta, erase, etc., but TWRP is still replaced by MIUI recovery after reboot to system. I can reboot to recovery directly from fastboot, but then /sdcard contains folders with weird names. I guess it is encrypted.
My goal is to create IMEI backup, but I'm afraid to run imei-backup.zip, when /sdcard is not proper. I have tried SHRP with the same results.
I have 2 questions:
- Is there alternative of imei-backup, that saves data to external SD or USB-OTG?
- If I use this TWRP to install LineageOS or CrDroid, would I get normal access to /sdcard?
Click to expand...
Click to collapse
You can backup the whole flash using the instructions provided in this thread.
The problem with restoring recovery is because you haven't rooted (via magisk) the device after flashing recovery. That's why the phone restores the recovery. IMEI (and other numbers like MACs) sits on a dedicated partition, so you can back the partition without having access to the data partition. Currently TWRP is unable to decrypt data when A12+ is used.
Thanks for your advice.
I'm on A11 MIUI. I didn't expect problems with encryption, but maybe it is MIUI problem.
I have made a backup to microSD with SHRP. SHRP can read partitions used for IMEI. For some reasons I couldn't make backup with TWRP.
I forgot about Magisk. With Magisk SHRP stay permanently. Probably tweak in SHRP or zip provided by OP can do the same, but I haven't tested.
My question is if I can format data and install custom A11 system without worrying about encryption?
When you format the data partition, the system will encrypt it again with the fist boot after flashing the ROM.
My Redmi 9 is on Pixel Experience Plus 12.1 with Pixel Experience recovery. Bad battery drain on idle so I want to try crDroid or PixelPlus.
Can I install this version of TWRP over Pixel Experience recovery? I want to install via Fastboot. I am already on Pixel Experience recovery so do I need to issue :
fastboot --disable-verity --disable-verification flash vbmeta your_name_vbmeta.img
or can I just go:
fastboot erase recovery
fastboot flash recovery your_name_recovery.img
fastboot reboot recovery
dataworx said:
My Redmi 9 is on Pixel Experience Plus 12.1 with Pixel Experience recovery. Bad battery drain on idle so I want to try crDroid or PixelPlus.
Can I install this version of TWRP over Pixel Experience recovery? I want to install via Fastboot. I am already on Pixel Experience recovery so do I need to issue :
fastboot --disable-verity --disable-verification flash vbmeta your_name_vbmeta.img
or can I just go:
fastboot erase recovery
fastboot flash recovery your_name_recovery.img
fastboot reboot recovery
Click to expand...
Click to collapse
Use a better full installation using vbmeta
Furry__wolf said:
Use a better full installation using vbmeta
Click to expand...
Click to collapse
Thanks for the reply - so I can just copy the vbmeta.img file from my original MIUI rom, and use that? Or does it need to be modified first?
dataworx said:
Thanks for the reply - so I can just copy the vbmeta.img file from my original MIUI rom, and use that? Or does it need to be modified first?
Click to expand...
Click to collapse
Use this vbmeta. It is patched for use on custom ROMs
Furry__wolf said:
Use this vbmeta. It is patched for use on custom ROMs
Click to expand...
Click to collapse
Thank you for your time and advice. I'll be able to tackle this tomorrow morning.
dataworx said:
Thank you for your time and advice. I'll be able to tackle this tomorrow morning.
Click to expand...
Click to collapse
No problem
I don't know if this is been asked before but after I flashed twrp recovery I noticed that on twrp internal memory doesn't show as it normal, can't access anythin, is there a way to fix that? (Lancelot)
hi iam install lineage os 18.1 twrp version is 3.5.2 this rom is very good and smooth and best battery...but install anu A12 custom rom whit twrp 3.5.2 its very slow and bad ram performance
what is problem? twrp is down virsion for A12?
Hi Everyone, twrp will be gone after some time by the miui Recovery. Though I flashed the vbmeta from Post #10.
What am I doing wrong?
morfikov said:
When you format the data partition, the system will encrypt it again with the fist boot after flashing the ROM.
Click to expand...
Click to collapse
Hello and thanks for your work here friend .
any way to make TWRP or SHRP decrypt internal storage ? I know about formatting data to make internal storage available , but a way to decrypt after booting ? On Android 10 I had no problem but on Android 11 Decryption doesn't work .
hi, when I try flashing this on miui 13 and reboot to recovery, it just reboots and goes into system ui. I'm using redmi 9 prime
Can anyone help me installating twrp for my poco m2, i tried but either i fot stucked into boot loop or my old miui recovery somehow replaced the file , can anyone plz.... Help via deskshare or any other way,
Vedant2 said:
Can anyone help me installating twrp for my poco m2, i tried but either i fot stucked into boot loop or my old miui recovery somehow replaced the file , can anyone plz.... Help via deskshare or any other way,
Click to expand...
Click to collapse
I had the same problem that I would fastboot flash the recovery, but still MIUI recovery would come up instead. You need to enter fastboot mode using Power+VolDown buttons and no cable connected, not via "adb reboot fastboot".
What tricked me is that (at least on MIUI 13) there are two fastboot modes.
When doing "abd reboot fastboot", the screen shows "FASTBOOTD" in BLUE letters. In this fastboot mode, "fastboot flash" finishes with "OKAY", but will actually do nothing.
When phone is off and you start it by pressing POWER + VOL_DOWN buttons, you get "FASTBOOT" (no D) in ORANGE letters. Only this fastboot will actually flash a new recovery!
It also prints "USB downloading..." on screen.
Hi,
I tried to update my P6 using the magisk OTA update method:
-Unistall / Restore image
-Install OTA, no reboot
-Install magisk on inactive slot
-Reboot
My phone was on the SQ3A.220705.001.B2 update, few months old.
When I rebooted, I was prompted with the "device corrupted" message. I pressed the power key to continue, and was stuck at the Google logo boot loop.
I forced turned off the phone (hold power + vol up a few sec), and the phone rebooted, no corruption message to my surprise, and booted correctly. However, my system did not update (still on SQ3A.220705.001.B2).
I'm a rookie on device rooting, but my understanding is that my inactive slot (partition b) as the update installed but is corrupted and goes in boot loop, while partition a is not updated but not corrupted either.
The thing is, I only did "install on inactive slot", so magisk was uninstalled on partition a, and rebooting made me lost root on that partition.
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
SleinBuyt said:
Is there any way to de-corrupt partition b without losing data ? Because without root on partition a, it seems like I'll need to reinstall it, meaning a factory reset...
I've searched a bit on here, saw that it was probably an avb bug (but rookie me doesn't know what avb is), and that OTA update using magisk inactive partition was not recommended for P6 and P7.
Any help would be greatly appreciated, thanks !
Click to expand...
Click to collapse
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Strephon Alkhalikoi said:
Be certain you're running the latest version of ADB. Google provides a link to the package you can download and extract. Then download a factory image from Google, extract the files from the zip to the same folder ADB was wxtracted to, and edit "flash-all.bat" in a text editor. You're looking for a snippet of text, "-w". Delete that text and save the file. From there, connect the unit to your PC and flash the ROM.
This will restore both partitions to working condition without removing data, but you will lose root in the process and will need to root again.
Click to expand...
Click to collapse
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
SleinBuyt said:
Ok I'll find out how to flash ROM using adb beacause I don't remember, and I'll do what you said.
After that, I should be able to force boot to partition b (the updated one) using adb, right? And will I be able to root without losing data ?
Click to expand...
Click to collapse
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
SleinBuyt said:
Ok so I've searched a bit, since my bootloader is unlocked I'll be able to root without losing data. The only question that remains :
You told me to download a factory image and to flash it with adb. Can I download the lasted version, for example the one that I failed to update to? If so, after flashing, will my de va ice be updated to the lasted version ?
Because that means that it's a way to update my phone, if I don't want to get the corruption error :
-download lasted update
-flash using adb, with the edited .bat
-Reboot and re-flash magisk
-done
Click to expand...
Click to collapse
m_pastuszek said:
I think that the easiest way is with Pixel Flasher, it makes everything automatically with data preserve.
Click to expand...
Click to collapse
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Strephon Alkhalikoi said:
@SleinBuyt : Yes
@m_pastuszek : While he could do that he should learn how to do it without a tool first. That way he can understand what is going on when the tool is working.
Click to expand...
Click to collapse
I agree on this side, but actually editing script that makes something similar comes down to the same thing
That was the same case for me.
After latest OTA update, no matter how many time I tried to flash full factory image via fastboot, stil showing device corrupted.
A couple of things everyone having this issue should be aware of.
Currently, "Flash to Inactive Slot" breaks verification/dm-verity on the Pixel 6/7, and I believe that's responsible for the "Device corrupted" error. The Magisk devs are aware but don't have a fix yet. I haven't been able to test because there have been no OTAs since I disabled those myself (which PixelFlasher can do for you), but I believe disabling them should prevent that problem during OTAs, but be advised I think doing so requires wiping /data when you do it.
Also, if you're still getting "device corrupted" even after reflashing stock, first watch for any errors during flashing in PixelFlasher (I may have a fix for anyone that has USB issues on Windows devices, but it involves the registry so it makes some people nervous), but if it isn't working then try Google's Android Flash Tool by finding your device and desired firmware here and clicking Flash. You'll need to be using Chrome. That's never failed for me. Once you have it up and running again *then* use PixelFlasher to patch and flash the boot image.
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Jaitsu said:
ALSO, for anyone on T1B1/QPR2: Magisk currently is not working at all with these versions. It'll boot, but you'll have no root. No one knows why yet as far as I'm aware. You'll have to stick to earlier/non beta builds until there's an answer for that if you want root.
Click to expand...
Click to collapse
To root the Pixel 6 on QPR2 Beta 1 you can patch the Pixel 7 boot image and then flash that on the Pixel 6.
Compression method of ramdisk in Pixel 6 boot image is incorrect · Issue #6441 · topjohnwu/Magisk
After switching to the beta version can't patch boot img and succesfully get root, with the stable version works. Device: Pixel 6a Android version: Android 13 QPR2 Beta 1 (T2B1.221118.006) Magisk v...
github.com
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
SleinBuyt said:
UPDATE : I did it, I used ADB for the sake of trying it, next time I'll look into PixelFlasher I guess. The message is gone.
Exact step followed :
-I first trained to use adb by flashing magisk, but ended up patching the wrong boot.img (the one from the A13 update, while being on A12), which sent me in a bootloop.
-I then flashed the A13 ROM, with the modified flash-all file
-Rebooted bootloader, flashed magisk
-Rebooted device.
Took me 2h lol, each step was learning something.
Thanks everyone!
Click to expand...
Click to collapse
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Lughnasadh said:
Just make sure you have the A13 bootloader on both slots if you haven't already, since it sounds like you just updated from A12 to A13?
🛑❗⚠️ WARNING! Read this before your initial upgrade to Android 13!⚠️❗🛑
***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Tensor devices, regardless of whether or not you're rooted! What this means: Once Android 13...
forum.xda-developers.com
Click to expand...
Click to collapse
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
SleinBuyt said:
I mean, the objective was to update my device and keep root, wich is now done. Why do I need the A13 bootloader on both slots, and if it's important how should I do it ?
Click to expand...
Click to collapse
It's important if you don't want to brick your device. Did you read the link I gave you?
Lughnasadh said:
It's important if you don't want to brick your device. Did you read the link I gave you?
Click to expand...
Click to collapse
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
SleinBuyt said:
Sorry I didn't see, I've read now.
So If ok reboot to fastboot, plug in, and with adb :
fastboot flash bootloader --slot=all flash-all.img
I should be good ?
Click to expand...
Click to collapse
fastboot flash bootloader --slot=all <A13 bootloader image>
My situation is a bit bizarre. I'm on beta and recently got an update notification that was 190mb. I went to magisk to restore images and magisk says stock backup does not exist. From there and went ahead and use my PC to flash my stock boot image and rebooted. Once an Android it's still says the same thing but when I go back to the update it says installation problem Even though I am on stock. That's where I'm at right now. Haven't messed with it since just rolled with no root and stock boot image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lughnasadh said:
fastboot flash bootloader --slot=all <A13 bootloader image>
Click to expand...
Click to collapse
And it's done ! Thanks for potentially saving my phone later !