Welcome. I hear you. Unnecessary wait.Thanks, still have to wait 29 days to unlock mi max 3 though, damn you xiaomi
Welcome. I hear you. Unnecessary wait.Thanks, still have to wait 29 days to unlock mi max 3 though, damn you xiaomi
just go to /system and rename the file " recovery-from-boot.p" to " bkp.recovery-from-boot.p "This install never seems to stick. If I flash it and then manually reboot to recovery holding vol up and power TWRP comes up ok. But after that if I reboot again it keep disappearing and going back to the stock recovery.
Try to format the date section in the cleanup and write,, yes" . Then do a reboot from recovery to recovery and sew other firmware .Hello. How do I solve this TWRP encryption problem? If that has no solution, then I bricked the phone. I'm grateful for the help.
Thanks for answering. This will not work, because after I installed TWRP, I made a backup of the original ROM and then installed the magisk. So I turned the phone back on and several apps stopped working, like Gmail, for example. So I went back to TWRP and tried to restore the backup, but it erased everything from internal memory and does not restore the backup by being encrypted. If that has no solution, I blew the phone. Any suggestions are welcome. Thanks again.Try to format the date section in the cleanup and write,, yes" . Then do a reboot from recovery to recovery and sew other firmware .
---------- Post added at 02:05 PM ---------- Previous post was at 02:03 PM ----------
Try to format the date section in the cleanup and write,, yes" . Then do a reboot from recovery to recovery and sew other firmware .
formatting the date section is the decoding of the date section . then you need to sew a new firmware . preferably localized . before the firmware, you can still make all the VIPs ,mount all the items , make a reboot from the recovery to the recovery . I pierced your Mi 3 Max . and your phone is unlocked and TWRP sees . good luck !Thanks for answering. This will not work, because after I installed TWRP, I made a backup of the original ROM and then installed the magisk. So I turned the phone back on and several apps stopped working, like Gmail, for example. So I went back to TWRP and tried to restore the backup, but it erased everything from internal memory and does not restore the backup by being encrypted. If that has no solution, I blew the phone. Any suggestions are welcome. Thanks again.
I did what you indicated, but it did not work. I had to install via Miflash tool, but it was the Chinese version. Now I need the global to be all right. Thank you again.formatting the date section is the decoding of the date section . then you need to sew a new firmware . preferably localized . before the firmware, you can still make all the VIPs ,mount all the items , make a reboot from the recovery to the recovery . I pierced your Mi 3 Max . and your phone is unlocked and TWRP sees . good luck !
Asked & answered. From official TWRP site:Cannot boot into TWRP after successful install. Tried re-flashing TWRP twice:
E:\Xiaomi Mi Max 3\>fastboot flash recovery twrp-3.2.3-0-nitrogen.img
target reported max download size of 536870912 bytes
sending 'recovery' (61128 KB)...
OKAY [ 1.324s]
writing 'recovery'...
OKAY [ 0.002s]
finished. total time: 1.328s
If I power off and use Vol UP + Power it boots into stock recovery. If I boot into android, open CMD and do "adb reboot receovery" it also boots into stock recovery. Any advice?![]()
I'm stuck on 'Boot to TWRP recovery', i've done that byYou might have your internal storage encrypted. Try this first. Download the official twrp app and install twrp image and flash twrp directly from there. Then, reboot to recovery. Then, test your reboot to recovery a second time. If the problem persists you'll need to start from scratch with this:
Installation Instructions:
- Make sure your bootloader is unlocked!
- Boot to fastboot mode
- Format your data to make sure that the installation will be clear using the command: fastboot format userdata
- Flash TWRP Recovery
- Boot to TWRP recovery
- Mount all the possible partitions
- Wipe your data,cache,Internal storage,dalvik DONT WIPE SYSTEM OR YOU WILL BRICK YOUR DEVICE
- Using MTP or OTG copy the xiaomi.eu rom to your device
- Flash the Xiaomi.eu rom
- Wipe cache and dalvik
- Reboot
>fastboot boot twrp-3.2.3-0-nitrogen.img
downloading 'boot.img'...
OKAY [ 8.293s]
booting...
OKAY [ 0.076s]
finished. total time: 8.371s
(bootloader) DP:0x0
(bootloader) token:V...4=
(bootloader) crc:1
(bootloader) cpuid:0x8xxxxxxx
(bootloader) board_version:4.19.0
(bootloader) unlocked:yes
(bootloader) off-mode-charge:1
(bootloader) charger-screen-enabled:1
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3905
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) variant:SDM EMMC
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x10000000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xC7F7FBE00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xC0000000
(bootloader) secure:yes
(bootloader) serialno:4xxxxxxx
(bootloader) product:nitrogen
(bootloader) max-download-size:536870912
(bootloader) kernel:uefi
Hold power and volume up for a while - it will boot you back to recovery unless you messed up your recovery.I'm stuck on 'Boot to TWRP recovery', i've done that by
but the device boot to a blank screen!
Retried a few times following the official instructions, also by doing fastboot reboot, and hold pwr+vol-up, no luck, stuck on MI logo...
Here's the getvar:
I know they are. Fastboot reboot is the reboot, but sometimes it doesn't work.adb and fastboot are two completely different things... Don't mix...
So? What makes you think adb works in fastboot mode!? It doesn't, so we have fastboot executable for fastboot/bootloader mode and adb executable for Android/recovery mode... Google didn't call it Android Debug Bridge(adb) for no reason...I know they are. Fastboot reboot is the reboot, but sometimes it doesn't work.
I never said that. Perhaps I didn't say it correctly. You misunderstood me. I know they are different. They keep running into some error for twrp where it reboots back to itself into a boot loop but didn't flash correctly (just look at the comment above yours). My Ticwatch Pro did the same thing. I was telling him to use adb reboot recovery in this scenario because this is not fastboot. I'll give you the benefit of the doubt. Maybe you're having a bad day. :highfive:So? What makes you think adb works in fastboot mode!? It doesn't, so we have fastboot executable for fastboot/bootloader mode and adb executable for Android/recovery mode... Google didn't call it Android Debug Bridge(adb) for no reason...
Well, it would be more simple if I can just reboot to recovery from fastboot with command. I'm not getting the adb reboot recovery, either if the twrp is loaded (which it isn't) or get loaded into android, adb server won't see the devices.I never said that. Perhaps I didn't say it correctly. You misunderstood me. I know they are different. They keep running into some error for twrp where it reboots back to itself into a boot loop but didn't flash correctly (just look at the comment above yours). My Ticwatch Pro did the same thing. I was telling him to use adb reboot recovery in this scenario because this is not fastboot. I'll give you the benefit of the doubt. Maybe you're having a bad day. :highfive:
>fastboot flash recovery twrp-3.2.3-0-nitrogen.img
target reported max download size of 536870912 bytes
sending 'recovery' (61128 KB)...
OKAY [ 8.101s]
writing 'recovery'...
OKAY [ 0.002s]
finished. total time: 8.105s
Locked bootloader? Seems like it... No errors but you can't boot/flash anything...Well, it would be more simple if I can just reboot to recovery from fastboot with command. I'm not getting the adb reboot recovery, either if the twrp is loaded (which it isn't) or get loaded into android, adb server won't see the devices.
I think the flash is fine:
I'm doing ">fastboot boot twrp-3.2.3-0-nitrogen.img" just to make sure the TWRP img is working on my phone, I'm not 100% sure this is the best method, but it's the only method I found. So with the current official version, I got blank screen with the command, and I tried adb on that, no luck, so it's not a simple display issue. The .img is MD5ed, so no problem in download...Code:>fastboot flash recovery twrp-3.2.3-0-nitrogen.img target reported max download size of 536870912 bytes sending 'recovery' (61128 KB)... OKAY [ 8.101s] writing 'recovery'... OKAY [ 0.002s] finished. total time: 8.105s
AND if I use the PWR+Vol-up method, it stucks on the MIUI logo. To make sure the method is correct, I tried with official recovery, no problem there...
Googled and found similar situation on different devices, and the solved cases are always a working TWRP. So may be I got a different variant or sth, just let me know what info I can provide to get this going. My Max 3 is the 4+64 model, come with official global 9.6.4.0 rom. I bought it from Mi Store, so no funny business, I hope
thanks guys![]()