Database Develop

[Solved][Q] Stuck in loop after firmware flash.

Edit:
I might have figured it out, while I was in that red triangle / exclamation point screen, I pressed power / volume, then when the screen turned black (phone off) I let go of power and kept holding volume, and it finally entered the bootloader and RUU is now running. Will edit the thread again if that goes through. Leaving info in case anyone runs into the same issue in the future.
Edit2:
The RUU failed when the fastboot binary crashed on step 4 @ 96%, so I switched to a USB3 port and reran and it got through 100% without a hitch, now the phone is working perfectly.
-----------------------------------------------------------------------------------------------------------
Hi, my phone is s-off, bootloader unlocked, h7_wls.
I flashed 5.05.651.2_full_firmware.zip (to install the ViperOne rom - it says to update the firmware) through fastboot, running it 2 times as recommended. Then I ran fastboot reboot and the phone was stuck in a boot loop, the white screen with the HTC logo would appear, then the screen would turn black (still on as it has the IPS blue glow) then it turns off (full black) and turns on again to repeat the loop.
I've tried holding down volume + power until the home/back flash then letting go of power and holding volume, but the phone would just reboot without going into the bootloader.
I've also tried shining the LED from my other phone onto the light sensor and holding power for 15 seconds, which turns off the phone. If I turn it back on, it returns the phone into the aforementioned boot loop.
Doing the volume + power thing, and running the RUU_M7_WL_K44_SENSE60_SPCS_MR_Sprint_WWE_5.05.651.2_Radio_1.01.20.0904_2_NV_SPCS_4.38_003_release_393160_signed_2.exe file while the home/back buttons flash gets the phone into a black background with a red triangle / exclamation point but the RUU program exits with Error[170]: USB CONNECTION ERROR.
Typing adb devices while in the black screen with red triangle / exclamation point, it sees the device but says the device is offline, typing fastboot devices returns nothing.
I've tried 3 USB cables.
Not sure what to do next?
Thanks.

kevinlekiller said:
Edit:
I might have figured it out, while I was in that red triangle / exclamation point screen, I pressed power / volume, then when the screen turned black (phone off) I let go of power and kept holding volume, and it finally entered the bootloader and RUU is now running. Will edit the thread again if that goes through. Leaving info in case anyone runs into the same issue in the future.
Edit2:
The RUU failed when the fastboot binary crashed on step 4 @ 96%, so I switched to a USB3 port and reran and it got through 100% without a hitch, now the phone is working perfectly.
-----------------------------------------------------------------------------------------------------------
Hi, my phone is s-off, bootloader unlocked, h7_wls.
I flashed 5.05.651.2_full_firmware.zip (to install the ViperOne rom - it says to update the firmware) through fastboot, running it 2 times as recommended. Then I ran fastboot reboot and the phone was stuck in a boot loop, the white screen with the HTC logo would appear, then the screen would turn black (still on as it has the IPS blue glow) then it turns off (full black) and turns on again to repeat the loop.
I've tried holding down volume + power until the home/back flash then letting go of power and holding volume, but the phone would just reboot without going into the bootloader.
I've also tried shining the LED from my other phone onto the light sensor and holding power for 15 seconds, which turns off the phone. If I turn it back on, it returns the phone into the aforementioned boot loop.
Doing the volume + power thing, and running the RUU_M7_WL_K44_SENSE60_SPCS_MR_Sprint_WWE_5.05.651.2_Radio_1.01.20.0904_2_NV_SPCS_4.38_003_release_393160_signed_2.exe file while the home/back buttons flash gets the phone into a black background with a red triangle / exclamation point but the RUU program exits with Error[170]: USB CONNECTION ERROR.
Typing adb devices while in the black screen with red triangle / exclamation point, it sees the device but says the device is offline, typing fastboot devices returns nothing.
I've tried 3 USB cables.
Not sure what to do next?
Thanks.
Click to expand...
Click to collapse
oh yeah this time happened to me as well
basically all your phone is doing is rebooting
you need to get it to power down somehow. I managed to force shut it down using the hold power thing and then held volume down and power to get to the boot loader
but if anyone is having difficulty another sure fire way to get the phone to shut down is to wait for the battery to die (may take a really long time)

Bricked Z3C stuck on kernel logo

I'm a bit stuck with a weird case; I have a rooted Z3C(locked bootloader) which I achieved by following this thread https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
It's been working fine for 1,5 year, when suddenly a week ago after the battery was low and shut the phone down, it got stuck in a bootloop while it was charging (already over 40%).
Couldn't get it to boot into recovery mode(nor it was detected by flashtool), until after a few days I was able to acces TWRP, made a backup(still got that, as well of a backup from the TA partition from 1,5 year ago). And then wiped the phone with TWRP as well. After another attempt to boot (which didnt work) it was able to get into the clockworkmod recovery(it's a surprise how that got on there), and chose "restore". There was a blue light and the screen went black. And it did so for over 5 minutes which made me(and a "techie") think it had probably crashed, so we forced shut it off(power button + VOL up, vibrate 3 times).
Since then I'm pretty much stuck with the situation from earlier but instead of being in a bootloop, it is now stuck on the kernel logo "Sony xperia". I can't make it boot in any kind of mode, I can only force shut down by power button + Vol up. It When trying to boot by using power button + vol UP it doesn't do anything; when using power button + down, it directly gets stuck at kernel logo.
At all attempts to boot there is no LED apprearing, LED only goes on for about 5 seconds when plugged into laptop or charger, and last the phone is not detectable by flashtool(or xperia companion).
Currently following this thread and waiting for the battery to drain: https://forum.xda-developers.com/showthread.php?t=1849170
But I wonder if that will do the fix...
In the meantime I'd like to know if there is anyone who might have some tips of what I can try?

elfae said:
I'm a bit stuck with a weird case; I have a rooted Z3C(locked bootloader) which I achieved by following this thread https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
It's been working fine for 1,5 year, when suddenly a week ago after the battery was low and shut the phone down, it got stuck in a bootloop while it was charging (already over 40%).
Couldn't get it to boot into recovery mode(nor it was detected by flashtool), until after a few days I was able to acces TWRP, made a backup(still got that, as well of a backup from the TA partition from 1,5 year ago). And then wiped the phone with TWRP as well. After another attempt to boot (which didnt work) it was able to get into the clockworkmod recovery(it's a surprise how that got on there), and chose "restore". There was a blue light and the screen went black. And it did so for over 5 minutes which made me(and a "techie") think it had probably crashed, so we forced shut it off(power button + VOL up, vibrate 3 times).
Since then I'm pretty much stuck with the situation from earlier but instead of being in a bootloop, it is now stuck on the kernel logo "Sony xperia". I can't make it boot in any kind of mode, I can only force shut down by power button + Vol up. It When trying to boot by using power button + vol UP it doesn't do anything; when using power button + down, it directly gets stuck at kernel logo.
At all attempts to boot there is no LED apprearing, LED only goes on for about 5 seconds when plugged into laptop or charger, and last the phone is not detectable by flashtool(or xperia companion).
Currently following this thread and waiting for the battery to drain: https://forum.xda-developers.com/showthread.php?t=1849170
But I wonder if that will do the fix...
In the meantime I'd like to know if there is anyone who might have some tips of what I can try?
Click to expand...
Click to collapse
Can you enter flash mode or fastboot?

nope, I can't enter either of them.. Unless there is a way to acces flashmode or fastboot mode without using the button combinations?

I've never stayed in your situation. Try turn off, wait the flashtools send the messenger with instructions to plug the phone, press vol. down button and plug in usb.
personally, i don't like end the whole battery in Sony's 2013>2015, because my fist sony, a M2A, after shutdown by low power, never turns on again... only tree reed lights - uhh, sony with jealous of xbox -, i change the battery and the bricks continued. Not healthy to sony hardware do this, i mean.
https://www.engineerthink.com/blog/2015/11/how-to-unbrick-hard-bricked-android-phone/
But if the last option, do that.

What you are discribing to do with flashtool, I already tried, it doesn't recognise the phone. I even tried "tricks" of different buttons and tempo's bu tthat doesn't help making flashtool recognise the device.
Also I was not able to make the phone completely decharge itself. This morning, after it drained the battery all night long by letting it stuck on the Sony logo, it came up with the battery empty logo when pressing power button. It is not possible for me to drain the battery even more, except if I keep pressing the power button every minute to activate the battery logo...
I tried the instructions from the link you pasted, to get it into fastboot with adb, didn't work, at the first command it already said it couldnt find the device:
C:\adb>adb reboot fastboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found

So, when You have powered off phone, hold vol- and plug it to computer does led on red than green and off?
And fastboot when phone powered off (hold vol+ and plug usb) doesn't work too yes?

@yaroszek, no when "powered off phone, hold vol- and plug it to computer" the LED goed red for a few seconds and then goes off(no green at all), and the screen will show the Sony logo.
when trying to fastboot with "phone powered off (hold vol+ and plug usb)" exactly the same happens...

Cannot start phone after battery got fully depleted

Hello,
Today I didn't notice that I need to charge my phone, so it eventually turned itself off. Later I knew I received an important SMS that I wanted to check but I didn't have the charger at hand so I tried to turn it on twice. Both times the Mi logo showed up, then the phone immediately turned off. The 3rd time I tried to turn it on, nothing happened.
When I was finally able to connect a charger, nothing happened. The screen doesn't turn on, the Mi logo or battery logo doesn't show up, the small LED doesn't react either. The charger was heating up so I knew something is happening so I left my phone there. When the charger started to cool down I knew that the charging is done, so I tried to turn on my phone again but nothing happened.
I have TWRP 3.3.1-0 and LineageOS 16.0 20200422 Nightly installed.
I have tried to press Pwr+VolUp but nothing happened.
I have tried Pwr+VolDn and FASTBOOT showed up. From here I tried to reboot by holding either Pwr or Pwr+VolUp or Pwr+VolDn.
By holding Pwr+VolUp or Pwr+VolDn the device turns off.
By holding the Pwr button, the Mi logo shows up for a split second then the phone turns off.
At this point I stayed in FASTBOOT and connected my phone to my PC and tried to use the Flasher Toolkit Nikel V3 (the tool I used when I installed TWRP and the custom ROM and whenever a LineageOS update bricked the phone) to reboot or boot into recovery, TWRP.
The phone doesn't react to any commands which is really strange, never had this issue before.
If I try fastboot boot twrp-3.3.1-0-santoni.img I get the error "unlock device to use this command." Which is really really strange because I had it unlocked before.
So currently I cannot turn on my phone, I can only reach FASTBOOT and nothing else. My main goal would be to backup data (photos etc), reviving the phone is only secondary.
I was searching the whole day on the internet and couldn't find anything that helped.
Any help is highly appreciated.

Try charging with different USB and charger.
Also you may want to remove the back panel and disconnect the battery connecter from motherboard and reconnect it after few seconds and try charging with charger.
Proceed carefully if you wish to remove back panel in order to not damage any device components to be precise the fingerprint flex cable which is glued to back panel.

This is what helped me to revive my phone but I couldn't find any trusted stock ROM sources so I installed a stock ROM from androidmtk.com and xiaomistockrom.com.
Can someone please tell me if they are safe or not? And if not, can someone please link me a Redmi 4X stock ROM I could use with the XiaoMi Flash Tool?
Also, it seems the phone cannot detect anything in the 2nd SIM slot. How can I fix it?

[SOLVED] Mi A2 reboot loop

Hello everybody, I'm having this loop problem with my phone. I didn't do anything like installing another rom or any modifications to it. I accidentaly restarted the phone and now it's on this "Android One" loop forever. I can't shut down the phone, I need to disconnect the battery to do that. I tried Test Point, Mi Flash, Fastboot... Nothing works, it's like the phone is rebooting always, even in Fastboot and Test Point with Mi Flash. In Fastboot reboots after 5 seconds or something like that, it wont stay there. Same for Mi Flash, when I try to flash the original rom it disconnects after a few seconds and then it's like the phone reboots again. I don't know what else to do, I tried everything I could find on the internet.
Fastboot won't work, it's all locked and even if it wasn't the phone just reboots after a few seconds...
EDL and Mi Flash get the disconnected error, like I said, seems that it reboots with this method too...
I spent hours trying to fix this, now I have no more ideas on what to do. If anyone have something in mind that could fix this, please comment.
Thanks to all.
SOLUTION: I managed to get it working. Here is how:
I used the original USB cable (I don't know if it works with another one). I connected the USB cable to a USB 2.0 port of a Desktop PC (directly to Motherboard, I tried front USB and laptops, nothing worked for me). Then I did the short between the two EDL pins and started pressing the power button over and over. Then you can release the EDL pin short and keep pressing the power button over and over, don't stop. Now you should be able to start the Flashing with the MiFlash software. If you're lucky like me, your pressing over and over the power button will keep the device connected to the PC, and your flashing will end succesfully.

ameegox said:
In Fastboot reboots after 5 seconds or something like that, it wont stay there.
Click to expand...
Click to collapse
Seems to me like problem with USB port or cable. Had the same symptoms when was connecting to any USB port in my PC MB, solution was to connect via USB 2.0 port in my Dell monitor USB HUB, which is connected to USB on MB.

Aerobatic said:
Seems to me like problem with USB port or cable. Had the same symptoms when was connecting to any USB port in my PC MB, solution was to connect via USB 2.0 port in my Dell monitor USB HUB, which is connected to USB on MB.
Click to expand...
Click to collapse
I've been trying different ports and different cables. The phone keeps restarting when trying to flash via EDL and MiFlash. It wont let me flash because it restarts in the flashing process, and that's a constant loop.

2 days ago i woke up to my phone's screen already on (mi a2), it had been frozen for 2 hours (woke up at 3:40pm but the phone lockscreen showed 1:14pm) so i held down the power button to soft reset it but now the phone was stuck in a bootloop. Been 2 days now of trial and error and a whole load of research which now leaves me here. The bootloader is unlocked but trying to flash stock rom (have tried multiple versions) through miflash gives me "Flash bluetooth_a error", trying to flash it manually through cmd on platform tools gives me the following:
fastboot flash bluetooth_a bluetooth.img
Sending 'bluetooth_a' (556 KB) OKAY [ 0.031s]
Writing 'bluetooth_a' FAILED (remote: 'Error flashing partition : Device Error')
fastboot: error: Command failed
Anyone know how i can fix this?

ameegox said:
SOLUTION: I managed to get it working. Here is how:
I used the original USB cable (I don't know if it works with another one). I connected the USB cable to a USB 2.0 port of a Desktop PC (directly to Motherboard, I tried front USB and laptops, nothing worked for me). Then I did the short between the two EDL pins and started pressing the power button over and over. Then you can release the EDL pin short and keep pressing the power button over and over, don't stop. Now you should be able to start the Flashing with the MiFlash software. If you're lucky like me, your pressing over and over the power button will keep the device connected to the PC, and your flashing will end succesfully.
Click to expand...
Click to collapse
My MiA2 had a similar problem. It rebooted spontaneously (reason unknown to me, perhaps it landed on the couch too roughly when I took it out of my pocket) and got stuck in a boot loop as you described. Fastboot waited for 5 seconds and then the device rebooted already. Holding volume up landed me in a screen that said "no command" and then rebooted after a few seconds just like fastboot.
I solved it by connecting my MiA2 via a USB cable to my laptop, activating fastboot on the MiA2 and then keeping on pressing the power button like a madman. I kept this up for about 20 seconds. The device did not reboot in those 20 seconds. Then, I stopped pressing the power button and instead pressed it continuously for about 10 seconds. The device then finally switched itself off. And on again, automatically. But, the boot loop was now fixed: the device showed the AndroidOne logo for quite a while like it normally does when booting, then the colored line and finally the SIM unlock screen.
Thank you for posting your solution! It made me attempt pressing the power button like a madman, which stopped the device from booting during the fastboot, which finally allowed me to fix it by actually turning the device off.
I hope my solution will help anyone encoutering this problem.
With kind regards,
Sven Berkvens-Matthijsse

svenberkvens said:
My MiA2 had a similar problem. It rebooted spontaneously (reason unknown to me, perhaps it landed on the couch too roughly when I took it out of my pocket) and got stuck in a boot loop as you described. Fastboot waited for 5 seconds and then the device rebooted already. Holding volume up landed me in a screen that said "no command" and then rebooted after a few seconds just like fastboot.
I solved it by connecting my MiA2 via a USB cable to my laptop, activating fastboot on the MiA2 and then keeping on pressing the power button like a madman. I kept this up for about 20 seconds. The device did not reboot in those 20 seconds. Then, I stopped pressing the power button and instead pressed it continuously for about 10 seconds. The device then finally switched itself off. And on again, automatically. But, the boot loop was now fixed: the device showed the AndroidOne logo for quite a while like it normally does when booting, then the colored line and finally the SIM unlock screen.
Thank you for posting your solution! It made me attempt pressing the power button like a madman, which stopped the device from booting during the fastboot, which finally allowed me to fix it by actually turning the device off.
I hope my solution will help anyone encoutering this problem.
With kind regards,
Sven Berkvens-Matthijsse
Click to expand...
Click to collapse
worked like a charm on the first attempt. thanks a lot.

Thanks for your advice!! For me it was easier
Problem:
- boot loop each 5 seconds with the anroid one logo
- boot loop in recovery (pressing power+volume up) showing open android with "no command", if pressed "power + volume up" again I entered in recovery options, but the phone rebooted after few seconds and didn't let choose any option
- boot loop in fastboot mode (pressing power + volume down), rebooted after 5 seconds
Solution:
No cable connected, just entered in Fastboot (power+volume down) and continuously and repeatedly pressed volume up and volume down for 10 seconds and more. In that way the phone didn't reboot and stayed in the fastboot mode. After being sure that the phone wasn't rebooting (waited about 30 seconds without doing nothing) I powered off.
Powered on again, crossed fingers, and the phone booted normally
Hope it helps

svenberkvens said:
My MiA2 had a similar problem. It rebooted spontaneously (reason unknown to me, perhaps it landed on the couch too roughly when I took it out of my pocket) and got stuck in a boot loop as you described. Fastboot waited for 5 seconds and then the device rebooted already. Holding volume up landed me in a screen that said "no command" and then rebooted after a few seconds just like fastboot.
I solved it by connecting my MiA2 via a USB cable to my laptop, activating fastboot on the MiA2 and then keeping on pressing the power button like a madman. I kept this up for about 20 seconds. The device did not reboot in those 20 seconds. Then, I stopped pressing the power button and instead pressed it continuously for about 10 seconds. The device then finally switched itself off. And on again, automatically. But, the boot loop was now fixed: the device showed the AndroidOne logo for quite a while like it normally does when booting, then the colored line and finally the SIM unlock screen.
Thank you for posting your solution! It made me attempt pressing the power button like a madman, which stopped the device from booting during the fastboot, which finally allowed me to fix it by actually turning the device off.
I hope my solution will help anyone encoutering this problem.
With kind regards,
Sven Berkvens-Matthijsse
Click to expand...
Click to collapse
Yep I also can confirm this saved my phone. In my case, only pressing all 3 buttons (volume up, down, and power) randomly a lot for 20 seconds worked. I then turned off my phone, it restarted automatically, and then just booted normally!

Hi,
Thanks a lot for this post. Ive just created this account to say thank you here.
Tried this and pressed the POWER button like crazy for a few seconds when it was stuck in the same auto reboot loop, and it worked first time. Crazy. This had been stuck for a while and a few phone shop told me they couldn't help me with this problem. Now the Xiaomi Mi A2 works!
Thanks guys!

Screen is dead after disconnecting/reconnecting battery.

My phone went to an endless bootloop after a botched attempt to install TWRP. I tried hard pressing the power button to no avail, and I can't access fastboot either. That's why I removed the back cover and disconnected the flex cable from the battery on the phone's motherboard.
Later on, I reconnected my phone's battery after my shift ended, then I tried to flash my stock rom through SP Flash Tool + bypass tool python script and it went through with a success. However, this time, my screen seems to be completely dead but my phone is still showing some signs of life (short vibration when pressing the power button, but since then it seems that it takes a few seconds more from pressing the power button to turn it on. ) I reconnected and disconnected everything to see whether or not I missed out something but the issue still persists.
The computer reads the device as "Android ADB interface" and the adb console reads it as *device id* unauthorized when I ran adb devices command. There's no notification light whenever I plug it into the charger.
Is my screen dead, or is my motherboard toast? I need to know as I don't want to spend money to buy a replacement LCD only to know that the motherboard's dead. I don't really care about the IMEI as I'm just going to use it as an authorization device for work. I can just always connect to Wi-Fi. Please advise.

One problem after another, so it seems.
Turns out I already unbricked the phone, but the thing is that my display's backlight got busted for some reason. Unless I shine a flashlight through it, I won't know what's in the screen. I'm currently on the way to get a replacement screen, and a new battery cover.
I guess this will be the last Xiaomi device that I'll ever get. This is the only time that I experienced such flimsy build quality since the LG G4.

Maybe you have destroyed a lil cable or something.