My TWRP was not loading (just a logo) and I forgot to root my device. I tried other versions and OrangeFox instead, and then "swipe to unlock" appeared, but touches are not working at all. Only side buttons are working.
*Everything works fine in MIUI
Twrp recovery works without root. That's why you can install magisc to root your phone using twrp. Try more twrp project and try to enter multiple times to recovery. I had the same problem and after 2-3 attempts it works. I'm using pitch black recovery And I recommend it with confidence
You can find this recovery here :
https://forum.xda-developers.com/t/...crypted_data-v2-9-0-base-twrp-v3-3-1.4000857/
As I tryed a loot of twrp project this was the most stable for me. Just flash it using fast boot. Or you can boot it Instead of flashing.
Code for boot : fastboot boot twrp.img
You can use this if you have problems on flashing the recovery.. So after you boot on it you can flash the zip file using twrp if it won't flash using your pc / cmd.
INFO:
If you want root and you got boot loop after flashing Magisk with TWRP(Phone stuck at boot process up to 2-3minutes ) boot twrp and format your DATA. DON'T WIPE! FORMAT!
**WIPE/FORMAT DATA**
*Restart your phone and be patient the boot may take some time after perform data format*
Now you should have the Magisk installed! (The data format does not wipe Magisk Manager from the system (!). It will be there.)
-------------
(!) If something goes wrong you can flash again the stock rom downloaded and repeat the process (!)
------------------
Related
Hello, I tried to install the latest paranoid android but now have a system that only freezes on boot or turns on into fastboot mode. The following is what I have done:
unlock bootloader
(system 23.1.A.1.28)
root using exploit for 5.0.2 with super su
installed recovery apk which installed some NDR tool as well to switch between recoveries
some phills touch ui was the default and teamwin only worked if selected from the NDR app and rebooted
booted into teamwin, did a full wipe
mtp wasn't working to copy ROM so did a reboot, also tried to sideload before reboot but the stupid twrp said the device was 'leo' instead of D6503 or whatever so it didn't want to work
phone stuck so tried to use fastboot to flash system pa-sirrius-rom.zip
also tried to flash system backup from twrp but it's a win.000 and win.001 file and not sure how to join them to get a working system.img??
why won't recovery boot and how do i get a working system again. how do i convert a twrp backup to one that fastboot recognises and isn't split in 2?
If you have an unlocked bootloader just download a kernel with recovery built in. Flash the kernel 'fastboot flash boot boot.img'. Your phones not booting anyway so it really doesn't matter what kernel, as long as it has built in recovery. Boot into TWRP and recovery your backup.
Edit:
I'd you have an unlocked bootloader, don't wast your time with apks that install recovery. I'm my experience they're always hacky. Just get a recovery for fota partition or a boot image with one built in.
Sent from my D6503 using Tapatalk
Thanks for the reply.
I finally found a boot.img with TWRP built in (from the cyanogen project). I also found out that I had to flash it (fastboot boot command doesn't seem to work).
I can boot the recovery just fine but it will not mount any partitions and the only thing listed in the wipe menu is "Dalavik Cache".
I have attached a screenshot of the TWRP log.
It won't let me post links because my experience is low.
i.imgur dot com cXBv1Y8.png
Edit:
I can format the system partition and even mount it from the command line, it just doesn't appear in the TWRP UI.
In the mount menu, it has a checkbox which I cannot uncheck that says "Only mount system read-only".
Edit:
Booted from the cyanogen recovery image which had its own adb sideload which I used to load cyanogen and now it's working!
I downloaded the twrp .img from the official website and flashed it using 'fastboot flash recovery twrp.img' and everything was shown Okay in cmd. Then I did 'fastboot reboot' and then after phone rebooted I went to recovery mode using volume up and power button but there was no TWRP there, only stock recovery was there. What went wrong? I flashed many times but same result
I had the same result like yours several weeks ago. And finally choose another method to install TWRP. Try below thread , it is easier.
http://en.miui.com/thread-296053-1-1.html
Your stock rom is replacing stock recovery every time you boot it.
TWRP needs a modified boot image flashed to make it permanent when used with official roms.
http://forum.xda-developers.com/red...official-twrp-3-0-2-0-recovery-redmi-t3352966
If you don't have the modified boot, make sure to boot into TWRP first after flashing it.
Handy way to get TWRP booted is to temporarily boot it using "fastboot boot <name of twrp.img>"
Once booted this way, use it to flash the TWRP image, then reboot into TWRP recovery you just flashed.
Once I had that done, after making a backup, I flashed a custom rom (xiaomi.eu) and TWRP remained permanent for me.
If your wanting to stay on an official rom, see this thread which has an Universal Boot Img Patcher.
Is Your Bootloader Unlocked? Cant flash on a locked BL buddy...
To unlock, follow the Guide y Nivu
http://en.miui.com/forum.php?mod=viewthread&tid=280561&extra=&highlight=no%2Bmore%2Bverify%2Bdevice&page=41
also read reply no. 408
2. DO NOT install the official, unmodified TWRP...
select a TWRP from here
http://forum.xda-developers.com/redmi-note-3/how-to/guide-redmi-note-3-available-twrps-t3406708
I Used the cofface TWRP
3. COPY Twrp.img to internal storage.....
fastboot boot TWRP.img
4. TWRP boots automatically... Press the button on Right to change device language....
Swipe right to allow modifications
5. Go to install... > flash Image. select TWRP.img
tap on reboot.... somewhere there, you will be asked to
1. install SuperSU
2. prevent phone from reverting to original recovery...
Swipe right on both.
Cheers!
When you do the "fastboot reboot" command, you should right away , press the volume + and power buttons together, so the phone boots into TWRP and not into the system. If you just execute the command and let it go , the stock recovery overwrites TWRP.
after entering "fastboot flash recovery twrp.IMG" don't reboot and don't entre "fastboot reboot"....you have to directly press power + vol up...you will able to boot into twrp
No matter how I try to flash the TWRP recovery image to the recovery partition, TWRP gets replaced by the crappy stock recovery!! This is absolutely maddening!
Specifically, it seems that no matter what method to use to flash the TWRP recovery, it gets overriden by the stock loader when the phone reboots.
My bootloader is UNLOCKED and I've installed a custom rom just fine by using the command fastboot boot twrp.img to boot into the twrp image. This is the only way I'm able to use TWRP at all.
I've tried:
fastboot flash recovery twrp.img
Booting into TWRP, and flashing the image over the recovery partition
Flashify to flash the TWRP over the recovery partition from within the rom
Trying to flash cyangenmod's recovery from within the rom (was pretty desperate at this point..)
I've also tried many different versions of TWRP, I can boot into them just fine but none of them stick when I flash them to the recovery partition.
It always says it's successful when I try to flash it, I reboot into recovery, and it boots into the piece of crap EmUI stock recovery screen every time
Anyone have any pointers here? It's not the end of the world but it's pretty aggravating having a completely useless recovery if I'm not near a computer,.
Try using Flashify or Flashfire.
Sadly didn't work. It doesn't seem to matter how I flash the recovery, the bootloader replaces it with the stock recovery when it boots. I'll update the OP to clarify, but thank you
I am having same issue have you found a fix
Have you tried starting completely over? Like, downloading the official MM build (b331, C564D003) from Huawei (Assuming you're on L24)?
On the new, freshly installed ROM, make sure that USB Debugging is and enable OEM Unlock are on in the developer settings.
Then, try flashing this build of TWRP again.
Before rebooting, do a Cache/Dalvik Wipe.
Boot up into the stock rom, then use 'adb reboot recovery' to see what happens next. It should work...
Hi mate,
It'd be easier to help you if you could post a screenshot of your FASTBOOT screen. There will be a line that will say FRP=LOCKED/UNLOCKED something like this.
if it is locked,
you have to install stock rom & enable OEM unlock from setting.
Then relock the boot loader. Then again unlock the boot loader.
For myself, I unlocked my BL unofficially, & this problem occurred . I solved it this way...
Hope it helps.
Cheers!
Cross-post from here
I have a frustrating issue.
After booting into fastboot mode, I type the following commands where recovery.img is the TWRP mido image. I also have lazyflasher and SuperSU on my SD card, but onto that later...
I type :
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
The phone boots into TWRP perfectly. I then flash the lazyflasher zip file. However when I try to boot back into recovery, the Mi logo briefly appears, then nothing... black screen.
So at the moment, I don't care about what is on internal storage. I went to wipe-->format data, then rebooted straight into bootloader to try and flash TWRP again. However this also gives me a black screen when I try and boot into recovery after installing Lazyflasher. I tried again, however I also flashed SuperSU immediately after lazyflasher. Rebooting into recovery from TWRP gives me a black screen again.
Should I perhaps try to flash a custom kernel? I am lost for other solutions.
TLDR: TWRP unsuccessful after: fastboot flash recovery, then fastboot boot recovery.img, then flashing lazyflasher, followed by flashing SuperSU, then choosing Reboot-->Recovery.
bigpavmate said:
Cross-post from here
I have a frustrating issue.
After booting into fastboot mode, I type the following commands where recovery.img is the TWRP mido image. I also have lazyflasher and SuperSU on my SD card, but onto that later...
I type :
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
The phone boots into TWRP perfectly. I then flash the lazyflasher zip file. However when I try to boot back into recovery, the Mi logo briefly appears, then nothing... black screen.
So at the moment, I don't care about what is on internal storage. I went to wipe-->format data, then rebooted straight into bootloader to try and flash TWRP again. However this also gives me a black screen when I try and boot into recovery after installing Lazyflasher. I tried again, however I also flashed SuperSU immediately after lazyflasher. Rebooting into recovery from TWRP gives me a black screen again.
Should I perhaps try to flash a custom kernel? I am lost for other solutions.
TLDR: TWRP unsuccessful after: fastboot flash recovery, then fastboot boot recovery.img, then flashing lazyflasher, followed by flashing SuperSU, then choosing Reboot-->Recovery.
Click to expand...
Click to collapse
Also, once just flash lazyflasher.zip /super su from twrp > next reboot into system from twrp! Do not choose reboot to recovery for the first time. Boot to system..
Okay guys, I have found the solution, although I would still like to know WHY this happened!
I used fastboot + Xiaomi Flash Tool to flash the latest stable ROM. I then enabled USB Debugging, and did all the same steps which resulted in being able to boot into recovery normally! I didn't flash lazyflasher this time because I flashed SuperSU instead, apparently it patches the dm-verity thing too. This was a suggestion from this post
Hi all,
Please help me, I cant boot into TWRP
Before that, I upgraded (xiaomi.eu) from MIUI 12 to MIUI 14 via fastboot (windows_fastboot_first_install_with_data_format)
Everything is fine, but when I try to boot into TWRP recovery, it keeps flashing TWRP logo
I tried to flash multiple versions of TWRP via fastboot also still the same
Thank you
here are some ways:
1 - try installing default recovery and boot into it then install twrp again.
2 - try installing twrp as boot and recovery both then reboot to boot
may work but take backups 1st