I've had my phone rooted until 2 days ago with MIUI10, then MIUI11, also tried all Custom ROMS everything fine until I installed the Global Stable 11.0.5 and as usally it wipes the custom recovery. I ran in this many times, and sorted also that many times by fastboot flash of the recovery. Something happened and right now I am stuck with global stable and cannot install again the custom recovery, tried I think 10 versions.
I open the commander run fastboot flash recovery ...img / fastboot boot ...img and it seems that it all went good, I wait as usuat that it boots in twrp, but instead it is taking longer and every time I end up in a normal restart and boots the system.
I am blocked and don't know what to try to get back my custom recovery, any advices are appreciated!
https://forum.xda-developers.com/showpost.php?p=80794593&postcount=957
Try this recovery: http://files.mi-room.ru/files/twrp/cepheus/3.3.1-1030/recovery.img , someone said it's the only recovery which works on his device.
Have you tried to boot into TWRP with power+vol up?
Related
Hello everyone, I need some help.
I Installed a custom rom (pac-man) on my Nokia x2 but now phone always restarts into recovery mode. no matter what i do.
I'm using cmw6.0.5.1 recovery, have tried twrp as well but no luck.
In order to boot into rom, first I've to reboot into bootloader mode and then type this command in terminal
Code:
Fastboot -i 0x0421 continue
to continue boot into rom.
Anyone know fix to this issue or any possible solutions?
You need to wipe and install the rom again
Thomson+ said:
You need to wipe and install the rom again
Click to expand...
Click to collapse
did that many times still boots into recovery. Installed another roms as well without any success.
So i flashed back stock recovery just now and it boots into system.
Hey!I have a serious problem with my phone and I really need some help
My phone was running Android 8.1 (Custom ROM) before someone cracked the screen of my phone.After that i leave the phone to a service for repair.All good since i take it back.After i went to home i do a factory reset and guess what...bootloop.I tried to flash other ROM ( I was using TWRP 3.2) but smae results...I tried to flash other version of TWRP ,but when i typed in adb fastboot boot (recovery image name).iso the phone still remains in FASTBOOT and nothing happened.
Finally I saw that an older version of TWRP was workig (cofface TWRP recovery) and i flashed the original ROM (MIUI) wich was working
Now I want to know what they did to my phone.Why i can't flash any other recovery or Custom ROMs...What can I do?
I really need some help
Hello, i have a Mi8 global version, unlocked and actually i'm on latest xiaomi.eu dev (9.1.24), but i have some problems with twrp and custom kernels.
I don't know why, but almost every recovery won't boot.
Actually i'm on TWRP 3.2.2-0711 (the only one that works) and managed to flash xiaomi.eu rom as written before.
But every other recovery on the forum won't boot, tried to flash and boot from cmd, only boot from cmd, flash with some tools, flash and with apps from playstore, restart from cmd with vol up, disconnect phone and use keys combination, but same result: only 3.2.2 works.
Every other recovery i try to flash does nothing, it just reboots normally without enter in twrp.
I have similar problem with custom kernel: only francoKernel_r4 boots fine. With every other miui compatible kernel i have bootloop.
I've tried to reflash fastboot rom with XiaomiFlash but still have same results.
Can anyone help me please? I have no more ideas what to do
IronJacob said:
Hello, i have a Mi8 global version, unlocked and actually i'm on latest xiaomi.eu dev (9.1.24), but i have some problems with twrp and custom kernels.
I don't know why, but almost every recovery won't boot.
Actually i'm on TWRP 3.2.2-0711 (the only one that works) and managed to flash xiaomi.eu rom as written before.
But every other recovery on the forum won't boot, tried to flash and boot from cmd, only boot from cmd, flash with some tools, flash and with apps from playstore, restart from cmd with vol up, disconnect phone and use keys combination, but same result: only 3.2.2 works.
Every other recovery i try to flash does nothing, it just reboots normally without enter in twrp.
I have similar problem with custom kernel: only francoKernel_r4 boots fine. With every other miui compatible kernel i have bootloop.
I've tried to reflash fastboot rom with XiaomiFlash but still have same results.
Can anyone help me please? I have no more ideas what to do
Click to expand...
Click to collapse
Did you know this thread?
https://xiaomi.eu/community/threads...neage-compatible-global-rom-compatible.48432/
lolo9393 said:
Did you know this thread?
https://xiaomi.eu/community/threads...neage-compatible-global-rom-compatible.48432/
Click to expand...
Click to collapse
No i did know. Just tried but both twrp don't work.
Btw i'll try to write in that thread too.
Thank you
Fastboot flash the recovery img, then fastboot boot the recovery img.
Then reflash recovery zip file from within twrp you just fastboot booted
https://forum.xda-developers.com/showpost.php?p=78693530&postcount=71
Use TWRP 3.2.3-1208 version from OP in this link
Stoffl_ said:
Fastboot flash the recovery img, then fastboot boot the recovery img.
Then reflash recovery zip file from within twrp you just fastboot booted
https://forum.xda-developers.com/showpost.php?p=78693530&postcount=71
Use TWRP 3.2.3-1208 version from OP in this link
Click to expand...
Click to collapse
As written on eu forum, the only recovery working is the 3.2.2.
Every other recovery, 1208 too give me:
Mi logo (unlocked) - black screen - Mi logo (unlocked) - system. But no recovery.
Tried to flash a custom rom different to xiaomi.eu but got bootloop, same with kernel flashable zips on xda. Only bootlooo...
I really don't know what to do anymore...
Yeah weird, I've literally guided a friend through the process just yesterday with that method.
Zero issues
Hello guys!
Yesterday I tried to flash the newest Lineage-built to my new G7+ (XT1965-3, bought in Germany via Amazon), but something went wrong and now I'm afraid, I bricked my phone.
It's not my first flash of Lineage, as I did this in the past already on some older Phones (SII, SIII, S5), but it's the first time, that I have a major issue.
So I followed all the steps on the Lineage-Wiki (on Win10).
After flashing the recovery (the lineage-recovery, not TWRP) I wasn't able to enter the recovery-mode, so the phone booted to StockRom. And probably this was the problem: As it didn't react to VolumeDown+Power, I reflashed the recovery a second time. After that the touch-screen is not working any more.
I am able to enter the recovery-mode and I can boot to Stock-Rom, but in both modes the phone does not react to touch, so I can only use the Volume- and Power-Buttons.
Probably I made more mistakes after that: I thought, that a factory-reset would help, but It didn't. I also relocked the bootloader, but as I saw, that it also did not bring any solution, I unlocked it a second time.
Conclusion: I have a brand new phone, with lineage-recovery, an unlocked bootloader but without touch working.
I also tried to flash Lineage, but the sideload got stuck at 47%. So Lineage is not installed and it boots into Stock, where I can not get any further without touch.
Has anyone any idea, what could be the issue and how I can fix it? I would like to start from scratch, but I don't know, what is the exact problem and if i can for example return to stock recovery.
Thank you!
---- EDIT ----
If it helps: I am able to boot TWRP via "fastboot boot twrp-xxx.img". And in TWRP the touch works!
I could flash lineage directly via TWRP from external sd-card, but i am afraid that after that I won't be able to return if something goes wron.
probably your best bet is to go right back to stock using the LMSA tool and starting fresh. I've seen others encounter similar issues on different devices and always the cleaneast solution was just to role back everything and start over.
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
joglxv said:
Thank you so much. With LMSA I managed to restore everything to stock and touch is working!
So I'm going to start from scratch and finally install Lineage.
Is is indicated to use the Lineage-Recovery, as the Lineage-Wiki says, or would it better to use TWRP?
TWRP gives me the option to flash from sd-card, which seems to me better than via sideload.
Click to expand...
Click to collapse
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
digitaljeff said:
Glad your back up and running. Take a look in the lineage thread, but it does appear most people lean towards using twrp, shouldnt have an issue with either however.
Click to expand...
Click to collapse
I'm having a similar problem. At first touch was fubar but I was able to return to stock using LMSA and now touch works. I can load TWRP with fastboot and even install a custom ROM and TWRP, but installing any custom ROM results in a boot loop during the finding and installing updates part of the phone setup during first boot. I'm tried Evolution X which I was running previously(for about a month, and then a boot loop started yesterday), PixelOS 10, and AncientOS, but all result in the boot loop on first boot after connecting to wifi.
Fixed
I fixed this somehow by manually flashing the latest stock firmware to slot a, and then extracting the evolution x Rom and manually extracting the IMG files inside and manually fastboot flashing those to slot b. I then set b as the active slot and booted up, patched the boot image with magisk, flashed that, and everything works. Not sure why twrp wouldn't do the trick.
Finally had the time to install Lineage. Now everything works.
I followed the instructions someone posted in the [ROM][OFFICIAL] LineageOS 17.1 [nightlies]-thread and the instructions of the lineage-wiki:
1. fastboot boot TWRP
2. sideload the copy-partitions.zip from lineage-wiki
3. factory reset via TWRP (wipe cache, dalvik and data)
4. sideload lineage
5. reboot bootloader
6. fastboot boot TWRP
7. sideload magisk
8. reboot system
Had a little bootloop the first time rebooting the system, but that was because I forgot to wipe data-partition in step 3. Wiping data and rebooting did it for me.
So I have a working Lineage17.1 with root via Magisk.
Thank you for the help!
I had exactly the same problem like you had. Bought a brand new moto g7 plus and after recovery flash, Touchscreen was not working anymore. I could manage to go back to the bootloader, sideloaded TWRP, but side loading lineage worked for me then. It seemed to be stuck on 47 percent, but this seems to be a normal issue, the file was there and after installing, touchscreen worked normally.
Trying to flash TWRp after unlocking bootloader. First time i tried it, said successful but booted to MIUI recovery
2nd time i tried said again successful, booted to TWRP, formatted data.
Phone then wouldnt reboot to TWRP. Instead it going straight to fastboot. I keep trying to flash again, every time saying successful, then it just boots to fastbooot, not recovery. Any ideas, phones dead at the minute
Tones1971 said:
Trying to flash TWRp after unlocking bootloader. First time i tried it, said successful but booted to MIUI recovery
2nd time i tried said again successful, booted to TWRP, formatted data.
Phone then wouldnt reboot to TWRP. Instead it going straight to fastboot. I keep trying to flash again, every time saying successful, then it just boots to fastbooot, not recovery. Any ideas, phones dead at the minute
Click to expand...
Click to collapse
The best way to recover the phone in your situation is to fastboot flash MIUI.
Get the latest MIUI fastboot ROM for your phone from here
https://xiaomifirmwareupdater.com/miui/raphael/
Install it using this guide from the official MIUI forums
https://c.mi.com/oc/miuidownload/detail?guide=2
If you see a blank page on a mobile browser, set it to view in desktop mode, for this page.
Make sure in step 5 you change the option at the bottom of the Mi Flash Tool to 'clean all' before hitting the Flash button.
MIUI will restore stock recovery when it reboots, so you need to do something to fix this. Flashing Magisk or a custom ROM will automatically preserve TWRP.
If you plan to keep MIUI and do not want Magisk, then you need to flash the vbmeta patcher from here
https://forum.xda-developers.com/k2...icial-twrp-xiaomi-redmi-t3944363/post79823568
You need to flash TWRP, then immediately boot into TWRP.
Code:
fastboot flash recovery <path to twrp>
fastboot oem reboot-recovery
At this point you need to flash something in order to preserve TWRP (either a new custom ROM, Magisk, or the vbmeta patcher)
Cheers. You know this is all familiar. Pretty sure i had the same trouble 3 years ago with my mi mix 2
Anyway, lots of hiccups on the way along with this solution. Got to the point now where it says its flashing but it never stops.
EDIT: Bit more research, shortened the path names. Got an error. Commented out device name, got a different error. Switched to USB 2.0 port an FINALLy im back up and running.
Thank you so much for the help.