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.
Related
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Shalabh21 said:
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Click to expand...
Click to collapse
As a result of this, I am not even able to do a manual factory reset from the setting menu in OOS 2.2.3, because when i try to initiate this the phone again gets stuck at the logo screen of recovery mode.
Shalabh21 said:
I am on OOS 2.2.3 on my Oneplus X. Rooted with Twrp recovery. Was not able to flash the new and official OOS 3.1.3 zip file through TWRP, so flashed Blue_spark TWRP in recovery mode (read somewhere that it could have enabled me to flash OOS 3.1.3). Now the phone boots into OOS 2.2.3 normally, but I cant boot into recovery or bootloader and it gets stuck at the logo screen in both these modes.
Could someone please help me out with this?
Click to expand...
Click to collapse
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, and you are on the Lollipop bootloader.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
If you wanna flash the 3.1.3 zip, then use these instructions.
Download Oxygen OS 3.1.3 full ROM
Download MM based unofficial TWRP
Downloaded Modded SuperSU if you want root
You will require a PC with WinRAR & Notepad++, because as we are running custom ROMs the zip will give an error 7 saying that The package is for OnePlus, this is an onyx, we need to remove that.
Don't worry, its super easy.
- Download the OOS3 zip, copy it to your PCs desktop
- Open it with winRAR, dont extract it, just open it
- There will be a META-INF folder, open it
- Then open com, then google, then android, there will be 2 files here, updater-binary & updater script
- Double click on updater-script
- It will ask which app to use to open the file, then select to open with Notepad++ (designate it from its installed directory if it isn't visible in the initial list)
- The file will look like this
{
"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"
}
- Delete the entire first line that starts with getprop
- Now it should look like this
- Now press Ctrl+S to save the file and close the window
- WinRAR will ask weather to update changes in the archive, say yes to that
- Let it finish its job
- Done !
Moving on to the flashing now...
Assuming you on OOS2.2.3, goto settings, enable Advanced Reboot.
Then reboot to bootloader, this is fastboot mode.
Flash this recovery.
Done, now...
- Copy the modded OOS3 zip into your Device
- Boot into TWRP recovery
- Wipe system, data, cache & dalvik/art cache
- Flash the modified OOS3 zip
- Let it complete
- After it completes, press the wipe cache/dalvik button below
- Now reboot to system
- Complete the initial setup
- Goto settings, unlock developer options by tapping 7 times on build number in about phone
- Enable advanced reboot
- Then reboot to bootloader
- Flash the MM based unofficial TWRP via fastboot
- Remember to boot into this newly flash TWRP before booting into system so that it doesn't overwite it
- Done
Now you are on OOS 3.1.3, and have a working TWRP, you can proceed to flash SuperSU etc to gain root
Joshwin Aranha said:
blu.spark TWRP v41 uses the updated Marshmallow bootloader from OOS3.1.3, and you are on the Lollipop bootloader.
Lollipop Bootloader recovery won't boot on Marshmallow bootloader and Marshmallow bootloader recovery won't boot on Lollipop bootloader.
If you wanna flash the 3.1.3 zip, then use these instructions.
Download Oxygen OS 3.1.3 full ROM
Download MM based unofficial TWRP
Downloaded Modded SuperSU if you want root
You will require a PC with WinRAR & Notepad++, because as we are running custom ROMs the zip will give an error 7 saying that The package is for OnePlus, this is an onyx, we need to remove that.
Don't worry, its super easy.
- Download the OOS3 zip, copy it to your PCs desktop
- Open it with winRAR, dont extract it, just open it
- There will be a META-INF folder, open it
- Then open com, then google, then android, there will be 2 files here, updater-binary & updater script
- Double click on updater-script
- It will ask which app to use to open the file, then select to open with Notepad++ (designate it from its installed directory if it isn't visible in the initial list)
- The file will look like this
- Delete the entire first line that starts with getprop
- Now it should look like this
- Now press Ctrl+S to save the file and close the window
- WinRAR will ask weather to update changes in the archive, say yes to that
- Let it finish its job
- Done !
Moving on to the flashing now...
Assuming you on OOS2.2.3, goto settings, enable Advanced Reboot.
Then reboot to bootloader, this is fastboot mode.
Flash this recovery.
Done, now...
- Copy the modded OOS3 zip into your Device
- Boot into TWRP recovery
- Wipe system, data, cache & dalvik/art cache
- Flash the modified OOS3 zip
- Let it complete
- After it completes, press the wipe cache/dalvik button below
- Now reboot to system
- Complete the initial setup
- Goto settings, unlock developer options by tapping 7 times on build number in about phone
- Enable advanced reboot
- Then reboot to bootloader
- Flash the MM based unofficial TWRP via fastboot
- Remember to boot into this newly flash TWRP before booting into system so that it doesn't overwite it
- Done
Now you are on OOS 3.1.3, and have a working TWRP, you can proceed to flash SuperSU etc to gain root
Click to expand...
Click to collapse
Thank you very much Joshwin Aranha. This worked like a charm.
However I modified the last step and flashed OOS recovery instead. Want to use the phone without root for a while, because the main reason I rooted it in the first place was to install Greenify and save battery (battery used to drain heavily in OOS 2.2.2 and all prior versions), but unfortunately it did not have a great impact on battery life. So going back to stock version for now.
Shalabh21 said:
Thank you very much Joshwin Aranha. This worked like a charm.
However I modified the last step and flashed OOS recovery instead. Want to use the phone without root for a while, because the main reason I rooted it in the first place was to install Greenify and save battery (battery used to drain heavily in OOS 2.2.2 and all prior versions), but unfortunately it did not have a great impact on battery life. So going back to stock version for now.
Click to expand...
Click to collapse
Whatever rocks your boat buddy, glad you sorted that out.
OPX stuck at oneplus logo after following the procedure
@Joshwin Aranha
Hi, I followed the exact same procedure you mentioned, and the process goes smoothly. But when i reboot the phone is stuck at oneplus logo (when i check through my PC for the status it says it is in fastboot mode).
I can easily flash OOS 2.2.3 and move to lollipop , but the problem occurs in OOS 3.1.3 MM
P.S. - i am not rooted.
hbansal24x7 said:
@Joshwin Aranha
Hi, I followed the exact same procedure you mentioned, and the process goes smoothly. But when i reboot the phone is stuck at oneplus logo (when i check through my PC for the status it says it is in fastboot mode).
I can easily flash OOS 2.2.3 and move to lollipop , but the problem occurs in OOS 3.1.3 MM
P.S. - i am not rooted.
Click to expand...
Click to collapse
Which recovery did you use to flash OOS3 ? And did you properly wipe everything ? Try re-flashing.
Joshwin Aranha said:
Which recovery did you use to flash OOS3 ? And did you properly wipe everything ? Try re-flashing.
Click to expand...
Click to collapse
I have used official TWRP that you mentioned in the procedure. I can easily flash CM13 and get my phone running. The problem is only coming in flashing OOS 3.1.3 after OOS 2.2.3.
And yes i have tried it multiple times. With factory reset, user data erase . Everything.
One quirk which i faced 1 time was that while flashing OOS 3 via official twrp 3.0.2.0 , during system verification stage i got an error "system partition has unexpected contents". I cleaned dalvik/cache/data and the error went away but the problem still persists
hbansal24x7 said:
I have used official TWRP that you mentioned in the procedure. I can easily flash CM13 and get my phone running. The problem is only coming in flashing OOS 3.1.3 after OOS 2.2.3.
And yes i have tried it multiple times. With factory reset, user data erase . Everything.
One quirk which i faced 1 time was that while flashing OOS 3 via official twrp 3.0.2.0 , during system verification stage i got an error "system partition has unexpected contents". I cleaned dalvik/cache/data and the error went away but the problem still persists
Click to expand...
Click to collapse
Does the OOS3 zip give any errors ? Or flashes properly ? This seems like a peculiar issue nonetheless..
Joshwin Aranha said:
Does the OOS3 zip give any errors ? Or flashes properly ? This seems like a peculiar issue nonetheless..
Click to expand...
Click to collapse
It does flash properly when i try to flash from OOS 2.2.3->3.1.3 . What i have observed is that as soon as the phone starts it gets stuck on oneplus logo without "android" written below. When i plug it into my system and check the device, it responds to "fastboot devices". I guess there is some issue with the bootloader or something
hbansal24x7 said:
It does flash properly when i try to flash from OOS 2.2.3->3.1.3 . What i have observed is that as soon as the phone starts it gets stuck on oneplus logo without "android" written below. When i plug it into my system and check the device, it responds to "fastboot devices". I guess there is some issue with the bootloader or something
Click to expand...
Click to collapse
Very the md5 of the OOS3 zip to check for a corrupted download.
Original md5 is 162f12d4dfef0142a184e761da868c5f
Joshwin Aranha said:
Very the md5 of the OOS3 zip to check for a corrupted download.
Original md5 is 162f12d4dfef0142a184e761da868c5f
Click to expand...
Click to collapse
MD5 is the same for UNCHANGED zip. i guess md5 will differ on a modified zip due to the changes you mentioned in the process.
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.
Version 10.2.26.0
Version 10.2.24.0 ------------ > Stock/Root
Version 10.2.9.0
{
"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"
}
T4Ump said:
Version 10.2.24.0 - Link
Click to expand...
Click to collapse
so what do we do with this? fastboot it? is it like a full rom with magisk, rooted? cheers
vtec303 said:
so what do we do with this? fastboot it? is it like a full rom with magisk, rooted? cheers
Click to expand...
Click to collapse
Fastboot flash boot.img
It's only magisk for 10.2.24
You can create your own if you want, it's just 30s faster
Code:
fastboot flash boot boot.img
Thank you so much for posting this. I'd been trying for 2 days with twrp and magisk (19.1 and 19.2) and could never get past the recovery bootloop on my Mi 9.
Are you on global stable?
I am having boot loop too.
So far I haven't seen any root for 10.2.9.0
Does anyone have boot.img V10.2.9.0.PFAMIXM? I wanna try root, but only need that file
xxx
T4Ump said:
xxx
Click to expand...
Click to collapse
Hi, thanks for the patched one. Do you still have the stock one? My phone stuck at recovery mode
Edited: nvm. I'll download the fastboot ROM. Thank you anyway.
realm9thfeb said:
Are you on global stable?
I am having boot loop too.
So far I haven't seen any root for 10.2.9.0
Click to expand...
Click to collapse
I don't get it, what are you trying to achieve? Keep encryption and have root access?
Right now i'm on 10.2.9.0 running perfectly fine with root (magisk 19.1) but no encryption.
PriPhaze said:
I don't get it, what are you trying to achieve? Keep encryption and have root access?
Right now i'm on 10.2.9.0 running perfectly fine with root (magisk 19.1) but no encryption.
Click to expand...
Click to collapse
Hi, could you tell me how you root your phone? I installed magisk manager, chose boot.img then got magisk_patched.img. I flashed it via fastboot flash boot magisk_patched.img but I got stuck at stock recovery after rebooting. Did I miss any step?
syreg said:
Hi, could you tell me how you root your phone? I installed magisk manager, chose boot.img then got magisk_patched.img. I flashed it via fastboot flash boot magisk_patched.img but I got stuck at stock recovery after rebooting. Did I miss any step?
Click to expand...
Click to collapse
What i did was:
-Flash Stock Global ROM with Xiaomi Flash making sure to set the bat as clean all and NOT clean and lock!
-Once done it will automatically boot , and when it does simply reboot and hold down vol to go to the fastboot
-Flash Recovery img using minimal adb and fastboot
-Type "Fastboot reboot" and hold vol up to go to twrp
-In TWRP FORMAT data to get ride off encryption and reboot into recovery
-Again in TWRP now u can transfer files to the phone, so i patched "Disable_Dm-Verity_ForceEncrypt" and then patched Magisk 19.1
-That's it.
You can now reboot and it will start the phone configuration as normal but once you configure everything u will see that magisk is there and fully works.
Just one thing tho.... be careful if u will restore titanium back up apps...
Don't get me wrong; they do restore correctly but when you make a backup it becomes corrupted or at least that's what happened to me, so make sure to keep backups PRIOR to using the ROM saved in your PC or something.
EDIT: Maybe u should give a try to this twrp https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825, just got updated few hrs ago and so far seems it works really good.
syreg said:
Hi, could you tell me how you root your phone? I installed magisk manager, chose boot.img then got magisk_patched.img. I flashed it via fastboot flash boot magisk_patched.img but I got stuck at stock recovery after rebooting. Did I miss any step?
Click to expand...
Click to collapse
I have this problem too, do this steps.
1. Fastboot ROM
2. Update last version
3. Flash magisk_patched.boot
4. Factory reset
Done, you have root.
PriPhaze said:
What i did was:
-Flash Stock Global ROM with Xiaomi Flash making sure to set the bat as clean all and NOT clean and lock!
-Once done it will automatically boot , and when it does simply reboot and hold down vol to go to the fastboot
-Flash Recovery img using minimal adb and fastboot
-Type "Fastboot reboot" and hold vol up to go to twrp
-In TWRP FORMAT data to get ride off encryption and reboot into recovery
-Again in TWRP now u can transfer files to the phone, so i patched "Disable_Dm-Verity_ForceEncrypt" and then patched Magisk 19.1
-That's it.
You can now reboot and it will start the phone configuration as normal but once you configure everything u will see that magisk is there and fully works.
Just one thing tho.... be careful if u will restore titanium back up apps...
Don't get me wrong; they do restore correctly but when you make a backup it becomes corrupted or at least that's what happened to me, so make sure to keep backups PRIOR to using the ROM saved in your PC or something.
EDIT: Maybe u should give a try to this twrp https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825, just got updated few hrs ago and so far seems it works really good.
Click to expand...
Click to collapse
Thank you. I'll try your steps.
How do you know the titanium backup becomes corrupted?
T4Ump said:
I have this problem too, do this steps.
1. Fastboot ROM
2. Update last version
3. Flash magisk_patched.boot
4. Factory reset
Done, you have root.
Click to expand...
Click to collapse
Factort reset? You mean wipe data while stuck at stock recovery? I did. Somehow my phone rooted. But I realized when I charge my phone while turning off it shows mi logo & unlocked words instead of battery icon, even after I unplug the charger. So I have to press power button to turn it on and charge normally. Do you have this problem?
syreg said:
Thank you. I'll try your steps.
How do you know the titanium backup becomes corrupted?
Click to expand...
Click to collapse
Because once I moved back to revolution OS ( I sawp of ROMs quite often ) I realized that my entire apps restored with titanium were crashing , and the few that actually open correctly didn't hold my data.
They were as if you just download them for the first time from the store.
syreg said:
Thank you. I'll try your steps.
How do you know the titanium backup becomes corrupted?
Factort reset? You mean wipe data while stuck at stock recovery? I did. Somehow my phone rooted. But I realized when I charge my phone while turning off it shows mi logo & unlocked words instead of battery icon, even after I unplug the charger. So I have to press power button to turn it on and charge normally. Do you have this problem?
Click to expand...
Click to collapse
No, i dont have this problem.
Root images updated to 19.2 magisk.
10.9.20 require wipe all data after flash patched image, this is not practical at all.
1. you stuck in this rom unless you want to wipe all data every time there is new rom.
2. Magisk bug existed in the latest global stable rom, notification prompted everytime you open Magisk to install zip, you can only ignore it or installation zip brick the phone.
10.2.26.0 root/stock
Can I use those with locked bootloader ?
Sent from my MI 9 using Tapatalk
Hey guys,
I've been installing customs without issue on my RN10.
Then one stopped booting freezing on the logo and bootloops.
Reinstalled stock with miflash and Redmi bootloops.
Tried customs again and same thing.
Any suggestions or things to try?
Worried the system_root and vendor errors are my problem.
Thanks in advance for any help or tips.
Cheers.
{
"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"
}
GEoMaNTiK said:
View attachment 5541321
Click to expand...
Click to collapse
Try flashing the super image through recovery.
faced this problem the solution for me was to flash fastboot miui eu rom
SubwayChamp said:
Try flashing the super image through recovery.
Click to expand...
Click to collapse
Tried this and didn't help, thanks for the suggestion
muneeb rizwan said:
faced this problem the solution for me was to flash fastboot miui eu rom
Click to expand...
Click to collapse
Hey there, I've tried flashing via Mi Flash and although it says success, still bootloops on Redmi logo, then eventually to fastboot.
Do you remember which fastboot miui EU rom or have a link ?
I'll try anything at this stage.. think I've killed my first Xiaomi phone.
GEoMaNTiK said:
Tried this and didn't help, thanks for the suggestion
Click to expand...
Click to collapse
Also, you can fix it flashing this ROM xiaomi.eu_multi_HMNote10_V13.0.5.0.SKGMIXM_v13-12-fastboot
SubwayChamp said:
Also, you can fix it flashing this ROM xiaomi.eu_multi_HMNote10_V13.0.5.0.SKGMIXM_v13-12-fastboot
Click to expand...
Click to collapse
Thanks for this, just tried, used the windows_fastboot_first_install_with_data_format.bat and all installed with an OKAY.
No failures or errors during install. Phone bootloops on Redmi and comes back to Mi Recovery screen.
Is there a way with OrangeFox, TWRP and any other tool to fix the file system or help?
Thanks in advance.
GEoMaNTiK said:
Thanks for this, just tried, used the windows_fastboot_first_install_with_data_format.bat and all installed with an OKAY.
No failures or errors during install. Phone bootloops on Redmi and comes back to Mi Recovery screen.
Is there a way with OrangeFox, TWRP and any other tool to fix the file system or help?
Thanks in advance.
Click to expand...
Click to collapse
same with me..but i reset data in recovery ..phone booting normal back
Now I'm getting a failed to mount (block device required) but still not able to get a custom to boot. When I try to reboot, I'm getting a system partition is empty.
Next question I have, do I have to force encryption in Orangefox or turn it off?
Also DM-Verity, should both options be off or on for customs?
GEoMaNTiK said:
Now I'm getting a failed to mount (block device required) but still not able to get a custom to boot. When I try to reboot, I'm getting a system partition is empty.
Next question I have, do I have to force encryption in Orangefox or turn it off?
Also DM-Verity, should both options be off or on for customs?
Click to expand...
Click to collapse
bro im facing the same problem you have... im using rn10sunny twrp will not mount system, and didnt flash custom roms... and if i flash stock rom then it will goes to bootloop... im also in the same condition now.....
can you please contact me on telegram @KAVIKING007 for discuss about the problem.. it will help both we are getting solutions....
GEoMaNTiK said:
Thanks for this, just tried, used the windows_fastboot_first_install_with_data_format.bat and all installed with an OKAY.
No failures or errors during install. Phone bootloops on Redmi and comes back to Mi Recovery screen.
Is there a way with OrangeFox, TWRP and any other tool to fix the file system or help?
Thanks in advance.
Click to expand...
Click to collapse
I assume you are formatting data, no? The long procedure for me was, installing AEX, I couldn't install it with TWRP (in this state), used OFR, boot to the recovery that AEX provides, format data, then boot to system, check that all is ok, enable USB debugging, now go to fastboot and flash the Miui 13.
In other device was fixed just flashing the super image (from the stock ROM) onto the super partition.
Keep the OFR settings as they are.
My theory is that some custom ROMs break the sizes on the super partition and some images are not matching.
Can you please explain about OFR because i couldn't used before....
KAVIYARASU KING said:
Can you please explain about OFR because i couldn't used before....
Click to expand...
Click to collapse
OFR Orange Fox recovery, is available in the forum.
SubwayChamp said:
OFR Orange Fox recovery, is available in the forum.
Click to expand...
Click to collapse
I tried in orangefox also but same problem occurs..... that was system could not mount.... On twrp,OFR the system partition could not be mounted... I tried all the way... But no result
KAVIYARASU KING said:
I tried in orangefox also but same problem occurs..... that was system could not mount.... On twrp,OFR the system partition could not be mounted... I tried all the way... But no result
Click to expand...
Click to collapse
Try, as pointed out in previous posts, format data with AEX recovery, then flash Miui.eu 13 through fastboot.
Also you can try flashing the super image (from the stock ROM through OFR).
And, finally, you can try using Mi Flash tool BUT in EDL mode.
All of these, assuming that you are permanently flashing the custom recovery, not only booting to it.
GEoMaNTiK said:
Thanks for this, just tried, used the windows_fastboot_first_install_with_data_format.bat and all installed with an OKAY.
No failures or errors during install. Phone bootloops on Redmi and comes back to Mi Recovery screen.
Is there a way with OrangeFox, TWRP and any other tool to fix the file system or help?
Thanks in advance.
Click to expand...
Click to collapse
You did not use the correct *.bat file for a complete cleanup. The *.bat you used will leave the original data on your phone even if it is not compatible. If you have a problem and want to install a new clean Miui system, use the flash_all.bat file (in MiFlash this is the "clean all" option)
StaryMuz said:
You did not use the correct *.bat file for a complete cleanup. The *.bat you used will leave the original data on your phone even if it is not compatible. If you have a problem and want to install a new clean Miui system, use the flash_all.bat file (in MiFlash this is the "clean all" option)
Click to expand...
Click to collapse
I had already tried MiFlash before that other rom and it's .bat file.
Just tried this with MiFlash - mojito_global_images_V12.5.2.0.RKGMIXM_20210731.0000.00_11.0_global_ce90f80766.tgz
I selected flash_all.bat. Received a success on completion of flash, used this MiFlash2018-5-28-0 (as I was receiving errors on the new MiFlash versions).
And still my phone bootloops on Redmi. This almost confirms to me this phone is lost now, nothing else I can think of.
However, will wait to see if any other suggestions here.
Thanks everyone for trying to help, much appreciated.
Don't worry yesterday night i get a new solution for these problem..... Almost we will get our device soon..... Today im gonna test few steps and its work i will give the solution dude.... So don't worry....
{
"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.