Stuck in FastBoot - Xiaomi Mi 9 SE Questions & Answers

Guys, I think I ****ed up.
I rooted my phone 3 years ago
And today, I forgot about that.
Did an atualization, and after restarting it got stuck in TWRP.
It was still "working", I could get photos and things from the phone and transfer it to a pc.
But couldn't install a rom from a pc.
Everytime I tried to use MiFlash, and clicked refresh (to show the device), my phone restarted (everytime).
So I put Global Rom into my phone, and tried to install it.
TWRP - Install - miui_GRUSGlobal_V12.5.1.0.RFBMIXM_c04478d703_11.0.zip
The thing is, after restarting, It does not get out of FastBoot.
Is It lost?

Related

Phone soft bricked after applying software updates

Hello.
The other night I applied 3 software updates to Android and ended up with an unusable phone. The updates (I assume) were like this: http://forum.xda-developers.com/tmobile-htc-one-m8/help/3-software-updates-t3268014
After the phone rebooted a couple times, it got stuck at the white HTC logo screen (I ended up falling asleep and the phone was like the after waking up, so stuck for about 6 hours) and wouldn't respond to just holding the power button. I had to hold power + vol up to get it to restart. After restarting it now boots to a black screen. It is possible to get to HBOOT and TWRP but I can't get adb to recognize it anymore so I'm not sure how to go about getting fixes on the phone.
The phone was running a custom recovery (clockwork recovery) and rooted. I then tried to get it back to stock to apply the Android 5.0 RUU and then used TWRP without flashing the recovery to root the phone again. My guess is that something about that process might have messed with something that one of the software updates was updating.
So, I have two questions:
1. Is it possible to recover files (pictures, for exampl) off the internal sd? Like I said, I cannot get adb (or windows) to recognize the phone, though it does show in the windows device manager.
2. If it's not possible to get recover those files, how can I get the phone usable at all?
Can you get it into the boot loader?
Yes, luckily I can get to the bootloader.
hatbocs said:
Yes, luckily I can get to the bootloader.
Click to expand...
Click to collapse
If so once in the bootloader can you use something like:
fastboot boot twrp-2.8.7.0.img
to boot into twrp? (note twrp-2.8.7.0.img is the filename of the twrp image that I saved it as, yours might be different)
If you can boot into twrp then you can install a rom/backup. also you could use, I think, something like "fastboot flash recovery twrp-2.8.7.0.img" as well.
-brad
I'm at work so I can't test this again to make 100% sure but if fastboot works like ADB then my phone doesn't show.
I do currently have TWRP installed however windows does not see the phone.
So if twrp works, you should be able to use that to connect to your pc. If not go and buy an OTG usb drive. Copy a Rom onto it, and then connect it to your phone. One time I messed my phone up and I used this method.
Worth a try. I'm in the middle of moving and that box of stuff isn't in this house. So I'll have to wait to report back. Thanks for the help so far.

Nexus 5x stuck at google screen [Potentially Hard-bricked]

Couple of days ago I got this OTA notification that Android 7.1 preview is available for update. As my phone is rooted I started the manual update procedure. After the flashing was finished, I restarted the phone and then I saw it was stuck at the Google screen. Just stuck, no response. Seemed unusual to me.
Let me tell you that I have been modding my Nexus 5 for about two years. I am familiar with most of the tweaks that can be done to a Nexus device. Nexus 5 served me amazingly. I bought Nexus 5x 3 months ago.
So, after it was stuck I restarted. Still stuck. I will tell you step by step what I did then:
1. Flashed the OS 7.1 again (I dunno why, the flash.all script doesn't work for me, so I always do that manually) - result is the same.
2. Last October update (NBD90W) was available in the folder so I flashed that - same result.
3. I downloaded the previous one (NRD90S) and flashed that - same result.
4. I locked the phone and unlocked again to erase everything (not sure if that's a good idea), then flashed the OS again - same result.
5. Then I tried LGUP and the tot files to give it the factory version. LGUP detects the phone, started installing. When the installation is finished and the phone restarted - same result.
6. Now that I gave it the factory version the phone got locked!
7. I searched google for hours but couldn't find a way to unlock it as the OS is not booting and I cannot turn USB debugging on!
8. Then I tried the default recovery mode (Android recovery, from the recovery screen Power + volume up) as it doesn't require unlocking the device. Wiped the cache and restarted - same result.
9. My phone is detected by the pc and ADB. So, I wiped everything and tried ADB sideload and get this error E: footer is wrong
10. I tried Nexus root toolkit. It detects the phone in fastboot mode, then restarts it and then it again is stuck on the Google screen.
I am extremely depressed!
I am from Bangladesh and there is no authorized LG servicing center here. So, I can't ask for there help.
All that I did over the past two years was the awesome threads of xdadevelopers. So, a big thumbs up for you guys :good:.
I learnt from the web that phone can be hard bricked if a wrong bootloader is flashed. That's impossible for me as I always remove the factory image extracted files after flashing is done from the ADB>platform-tools folder.
Now, is the phone hard-bricked? If it is, what to do with it? Any kind of suggestion will be very much appreciated.

Android fails into TWRP, TWRP Won't Load Anymore, and Phone Not Recognized in Win10

Hello, I tried to install the rom Google PixelROM v7.3 for LG Nexus 5X[7.1.2] by argraurand, and now my phone will no longer boot into TWRP or the OS. I am running TWR 3.0.2-0, I didn't see anything about having to have that updated to the most recent for using this rom. I was able to install the rom fine from this TWRP, but now my phone seems to be bricked like. Sitting with the phone in the bootloader, I can't get windows/fastboot/adb to recognize my device connected to my computer, the google drivers are definitely installed as earlier it was being recognized fine by windows/fastboot/adb. My bootloader changed with this ROM being installed, but now the TWRP won't load either, and neither will the Android OS (it looks like it's about to load then just defaults into the TWRP loading screen, which just sits forever). I can get also into the download mode "firmware update" tool of the phone by pressing the volume up when booting, but even in this mode the phone isn't being recognized in windows anymore. Do I have any chance of restoring my phone, or should I start shopping? I've fixed other phones many times, but without being able to load/restore via fastboot I feel totally lost.
myselfalex said:
Hello, I tried to install the rom Google PixelROM v7.3 for LG Nexus 5X[7.1.2] by argraurand, and now my phone will no longer boot into TWRP or the OS. I am running TWR 3.0.2-0, I didn't see anything about having to have that updated to the most recent for using this rom. I was able to install the rom fine from this TWRP, but now my phone seems to be bricked like. Sitting with the phone in the bootloader, I can't get windows/fastboot/adb to recognize my device connected to my computer, the google drivers are definitely installed as earlier it was being recognized fine by windows/fastboot/adb. My bootloader changed with this ROM being installed, but now the TWRP won't load either, and neither will the Android OS (it looks like it's about to load then just defaults into the TWRP loading screen, which just sits forever). I can get also into the download mode "firmware update" tool of the phone by pressing the volume up when booting, but even in this mode the phone isn't being recognized in windows anymore. Do I have any chance of restoring my phone, or should I start shopping? I've fixed other phones many times, but without being able to load/restore via fastboot I feel totally lost.
Click to expand...
Click to collapse
Try a different USB port. Maybe even a different pc. Fastboot tools was just updated. Make sure you have the latest one.
Maybe you can get a fastboot connection in Linux. Try this:
https://forum.xda-developers.com/showthread.php?t=3526755
Sent from my Nexus 5X using Tapatalk
Thank you both, I tried both another computer, and running this linux version with the fastboot built in, nada! Guess I'm shopping for a new phone. Pixel here I come. Thanks for the help agian.

[HELP] My Zenfone 2 (ZE551ML 4GB) dilemma

My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Ragarianok said:
Did you flash the MM bootloader compatible TWRP mentioned in the OP for LineageOS? That solves error 7.
Click to expand...
Click to collapse
I did not do that. I remembered all the steps but forgot that. That is the primary cause of my problem. Anyway to solve it?
LethalHoe said:
My Zenfone 2 (ZE551ML 4GB) dilemma:
*•*I unlocked the bootloader with the official bootloader app
*•*I flashed the latest TWRP via adb. In the recovery screen, I saw an android showing error. That's when the panic started.
*•*I Then I rooted my phone with the one click Zenfone root application (available in XDA)
*•*I installed the official TWRP manager from the playstore and flashed with it. That also didn't solve my problem. Actually, a new problem set in. The phone started bootlooping IN RECOVERY.
*•*I rebooted the phone and then flashed an old version of TWRP for my phone. That solved the problem.
*•*Now, I wanted to flash Lineage OS in my phone. According to a YouTube tutorial, I copied my required files (the custom ROM and OpenGAPPS) to my Micro SD and then from twrp's advanced wipe, deleted everything except for Micro SD. I know that was an extremely stupid move but please bear with me.
*•*Deleting everything made things hundred times worse. It seemed impossible to get the phone into recovery mode again. But after a long time, I did.
*•*Now onto flashing the new ROM. I did a factory reset with twrp and then flashed the ROM and immediately got Error 7. By googling a bit, I found that the only way to solve this problem was by deleting the assert lines from the updater-script in meta/com/google/android inside the ROM.
*•* When I reflashed it, the process completed but it showed an error: (E:unknown command [log])
*•* Then I overlooked it again as a quick google said it didn't matter. Then I successfully flashed OpenGAPPS. I rebooted my phone and it kept bootlooping until it was back in the recovery screen. Weird right?
*•*I didn't seem to find any workaround so I decided to restore stock ROM. I downloaded it and flashed it. It succeeded. I rebooted my phone. And. .
*•*My phone now vibrates when I power on the phone and then it shows a black screen. It reboots automatically. I know it does as the phone vibrated periodically after the reboot
*•* I also can't go into the bootloader menu. My phone seems dead but I really need to revive it. I can't afford a new phone. Could you guys help me out please?
Click to expand...
Click to collapse
xfstk is the only way. go to following thread and do as suggested. one advice when you get into bootloader. flash raw without AFT. that is best.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

HELP! (sm g532m) pc doesn't recognize device, can't enter recovery mode either.

Hi everyone.
so, I'm new to this world of roms, but i've been playing with a samsung sm- g532m, is an old phone, don't use it anymore.
i've installed many roms in this phone with twrp and gone back to stock rom with odin, and until now everything went fine.
I installed the lineage 14.1 for this model, and it went smooth, it charged to the logo, then to the first settings, but after maybe 1 minute it restarts itself, and i have to do the same. no matter how fast i try to do that, when it's supposed to set everything, it restarts.
i've tried using odin but the pc doesn't recognise the device. it's not the usb cable, because i've used it with other phones and there's no problem.
i've tried goind to recovery mode, hard reset but nothing, the android logo the green thing doesn't show, it just start the phone to the lineage logo.
When i installed the rom with twrp, i checked that it would install the twrp...like i said, i'm new. don't know what went wrong.
I thank you guys in advance, and hope you can help me.
shimatta_cosha said:
Hi everyone.
so, I'm new to this world of roms, but i've been playing with a samsung sm- g532m, is an old phone, don't use it anymore.
i've installed many roms in this phone with twrp and gone back to stock rom with odin, and until now everything went fine.
I installed the lineage 14.1 for this model, and it went smooth, it charged to the logo, then to the first settings, but after maybe 1 minute it restarts itself, and i have to do the same. no matter how fast i try to do that, when it's supposed to set everything, it restarts.
i've tried using odin but the pc doesn't recognise the device. it's not the usb cable, because i've used it with other phones and there's no problem.
i've tried goind to recovery mode, hard reset but nothing, the android logo the green thing doesn't show, it just start the phone to the lineage logo.
When i installed the rom with twrp, i checked that it would install the twrp...like i said, i'm new. don't know what went wrong.
I thank you guys in advance, and hope you can help me.
Click to expand...
Click to collapse
Did you follow the patching to not make it crashes every 90 seconds? That sounds like one.
Also, if you want to boot recovery from OS, install ADB on computer and do these quickly
> let it boot and unlock screen
> plug in USB and turn on file transfer
> on PC: adb reboot recovery

Categories

Resources