[SOLVED] Mi A2 reboot loop - Xiaomi Mi A2 / 6X Questions & Answers

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!

Related

[Q] Strange Reboot Loop, searched forum Not Addressed

Hello All
I did search the forum and still not answer for the stranger reboot loop.
I got a phone call, and answered it. The reception was crappy and hear no voice. I then looked at the phone to see if call had dropped and it was frozed on the incoming call screen. I then pulled the battery and pressed the power button to turn on the phone and It would not power on. After multiple battery pulls and many many power button presses, still nothing. It was like it was out of battery. It was stitting on the home charger before i left the house. Prior to this the phone worked fine. Over the past week or two I had to do a battery pull may be 3 times.
I got to my car and plugged it into the charger and the orange charge led came on, on the front of the device. I then pressed the power button and it vibrate once as normal and then went to the multi-colored nexus "X." he screen went black and then vibrated once again and and was back at the mulit-colored "X." Then the loop starts.
In between the restarts I try to get it to boot into the bootloader by using the "vol down and power" and the "trackball and power button" and the white screen for the boot loader flashed for a milisecond the goes to black. As long as I hold the "vol down" button the while bootloeader or recovery screen flashes every 4-5 sec for a milisecond. As soon as I let go of one of those button, it automatically goes to the full reboot loop.
THis all happens when it is plugged into a power source. As soon as i unplug it, it goes back to the power button not responding. Again it acts as if it has no battery power. But it is in the 90%.
So i am unable to do any other step as in reflashing, and or doing a recovery.
ANY IDEAS any one.
I was running Cyanogen RC3. the latest rom with amon RA 1 7 1, korean radio 5.0.8
It was running perfectly up till today. when it went into its loop.
ANY HELP WOULD BE AWESOME
THanks in advance
DD
Plug it in to the USB, adb reboot recovery, reflash rom. Or even wipe and reflash if needed.
Sounds like it could be hardware the way you have to hold the keys down and you said it wasn't responding to the power button press.
ok thanks, ill give it a try.
here is my only issue. I am not using my original computer Mac. I just sent it out to apple for repair. So i am using my companies computer. I need to set up the AndroidSDK to be able to talk to the nexus. Since the phone will not turn on i can not load the drivers. and ive tried every way and it has not installed and i cant check because it wont stay on. it just goes to the loop. and it wont turn on if its not plugged to a power source.
Any ideas or suggestion.
SOrry I am an noob, so could you please be specific in your instructions.
I as of right now have insalled the Android SDK and i am unable to see the serial number (working on an old dell, running XP sp3) because it wont turn on.
It cant manually install the drivers because I cant turn the phone on to specify the drivers.
and
I using USBDeview, the phone also has to be on to erase all HTC previously installed drivers. i think. but there were none in the usb log...i think becuase they didnt install...agains because it would not power on...:-(
any ideas...please
DD
Also
Sorry excuse me if its a sort of a duhhh question...
even if i am able to load the device bridge, if the phone will not boot can i still flash another rom, or do a recovery. The phone is not getting past the Multi-colored "X" ???
DD
It should still read the commands when it's trying to boot. You don't need to turn the phone on at all to be able to install the ADB drivers, they are independent of each other.
As strange as it started, is a strange as it went.
This morning open the phone to pull the sd and the sim to put it in a throw down phone. I replaced the battery and cover and just hit the power button. The phone does a full boot and it appears to be working properly. the sd card and sim are fine. I the odd thing is i did this multiple times yesterday and last night. I pulled both sim and sd, replaced the battery and tried to boot with the same issues as named above with nothing different.
I left the phone on charge last night and it was charging for close to 8 hours and it was still showing the orange charging light.
So after it booted this morning, and i checked everything. It showed the same amount of charge as yesterday, right before it froze, which was 75%. So that is another strange occurance.
I plan on reflashing the rom and seeing how things go.
I thank you for your assistance and time.
appericate you helping out a clueless noob.
DD

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...

My Nokia 7 Plus does not boot at all or stuck on Android One logo

My phone suddenly restarted and stuck on Android One logo and not booting further. I've turned the phone off and started after few seconds and it was still stuck on Android one logo. Then I've tried to get into recovery mode by pressing Vol Up + Power but it was not working. Also it's not responding to the charger. No battery sign and nothing. It does not respond to power button many times. I've also tried to get into fastboot mode (Vol down + Power) and even it was not working. Please help!
It's not rooted and didn't try to flash/install custom ROM.
achalj said:
My phone suddenly restarted and stuck on Android One logo and not booting further. I've turned the phone off and started after few seconds and it was still stuck on Android one logo. Then I've tried to get into recovery mode by pressing Vol Up + Power but it was not working. Also it's not responding to the charger. No battery sign and nothing. It does not respond to power button many times. I've also tried to get into fastboot mode (Vol down + Power) and even it was not working. Please help!
It's not rooted and didn't try to flash/install custom ROM.
Click to expand...
Click to collapse
Take phone to discharge batttery and automatically turn off. Plug in to charger for few minutes and press and hold volume up,volume down and power for 2/3 minutes. He should be turn off and then you can go in to recovery.
Suffering the same problem.
I'm having the same problem. Exactly what you said. I didn't root my device or even attempt to do anything. I bought Nokia because they were purely stock and delivered some quality mobile phones. I've got only this phone as my daily driver. So tell me if you have got the issue fixed and how much did it cost and how long it took. It's been stuck with that 'android one' logo and a small message that reads 'Download mode' on top. I've tried everything. And what I'm worried about is, my phone's out of warranty and I'm a student. I hope you got it fixed for some reasonable cost. Please reply to me ASAP.

Bootloop, locked bootloader, EDL flashing not working

Edit: I was suspicious of the power/volume contacts issue, so I lifted the board and was able to flash with EDL and enter the system. I might've messed up the piece while removing it from the older case. I ordered a replacement and I'll see how it goes from there.
Edit: the issue was indeed the flex cable of the side buttons. I replaced it and now it works!
=============
Hey guys, my phone's back cover and screen got shattered recently but it seemed to be working fine. I got some parts from China and assembled it today, I think it all went ok, but now the phone's stuck in an infinite bootloop (Android One screen).
So, the phone's bootloader is locked. I can't do anything through fastboot, even though I can try to send commands. Every command just reboots the phone and returns it to the loop.
After reading a lot here, I heard that my best bet was to enter EDL mode and flash the phone with MiFlash.
I'm able to get to EDL (phone shows up as COM), but after that it all goes downhill, I get a different error for each attempt of flashing: timeout, I/O exception, writing time out, resource in use, port closed, phone disconnected, strange errors, handshake error, reset status error etc.
It begins normally, flashing a few things for half a second, then fails.
I've tried two computers, multiple USB 2 and 3 ports, two images, two versions of MiFlash, three cables.
What do you guys think? This EDL flashing should've worked, but it's keen on failing in every attempt till now.
Funny thing is, while messing with the connectors, once in a few dozen loops the phone actually boots to the system, then reboots after a few seconds!
Also, I should mention that I can't turn off it for good, even if I keep power pressed for 20 seconds or more, it's like the power button is constantly pressed. I also can enter fastboot by only holding volume down while it loops, which is unusual...
Thanks!
valp88 said:
Edit: I was suspicious of the power/volume contacts issue, so I lifted the board and was able to flash with EDL and enter the system. I might've messed up the piece while removing it from the older case. I ordered a replacement and I'll see how it goes from there.
=============
Hey guys, my phone's back cover and screen got shattered recently but it seemed to be working fine. I got some parts from China and assembled it today, I think it all went ok, but now the phone's stuck in an infinite bootloop (Android One screen).
So, the phone's bootloader is locked. I can't do anything through fastboot, even though I can try to send commands. Every command just reboots the phone and returns it to the loop.
After reading a lot here, I heard that my best bet was to enter EDL mode and flash the phone with MiFlash.
I'm able to get to EDL (phone shows up as COM), but after that it all goes downhill, I get a different error for each attempt of flashing: timeout, I/O exception, writing time out, resource in use, port closed, phone disconnected, strange errors, handshake error, reset status error etc.
It begins normally, flashing a few things for half a second, then fails.
I've tried two computers, multiple USB 2 and 3 ports, two images, two versions of MiFlash, three cables.
What do you guys think? This EDL flashing should've worked, but it's keen on failing in every attempt till now.
Funny thing is, while messing with the connectors, once in a few dozen loops the phone actually boots to the system, then reboots after a few seconds!
Also, I should mention that I can't turn off it for good, even if I keep power pressed for 20 seconds or more, it's like the power button is constantly pressed. I also can enter fastboot by only holding volume down while it loops, which is unusual...
Thanks!
Click to expand...
Click to collapse
try to flash it via testpoint
q0kHaN said:
try to flash it via testpoint
Click to expand...
Click to collapse
I managed to flash it through EDL.
However, it seems like the piece that holds flex cable and side buttons is damaged. It's like the power button is always pressed (making the phone reboot over and over) or non-functional at all.
I'll change this piece and see if works properly.

Possible brick after updating twrp

Dear all,
I was on beyond 5.3 with twrp 3.3.1.7 and I wanted to update everything. Magisk, root etc was working fine.
I downloaded the patched twrp file from the beyond telegram chat and flashed it as image into the recovery partition.
The installation was finished in 2 seconds, but stupid me chose to power off instead of rebooting the recovery.
So I tried to enter recovery using the button combo but nothing happened and I was stuck with the samsung logo.
The current status is that my phone only shows the samsung logo.
Holding the power button for a minute doesn't do anything.
Pressing the button combo for recovery mode doesn't do anything.
Pressing the button combo for dl mode makes the phone reboot. It vibrates for a sec, then the samsung logo shows again.
If I keep pressing all 3 buttons the phone keeps on rebooting and vibrating each time, but dl mode never appears. If I let go of the power button the logo stays and again, nothing happens.
So basically I can't enter dl mode nor reboot.
Should I let it run dry and try again or just throw out of the window immediately? :crying:
I let the battery drain over night. Phone was finally off.
So when I plug it in, the Samsung Logo appears and doesn't change. It just stays like that forever until the battery drains.
Pressing the power button doesn't do anything, no matter how long. It doesn't reboot nor does the logo disappear.
Pressing vol+, bixby and power again does nothing.
Vol-, bixby and power makes the phone reboot. The screen turns black, the phone vibrates shortly, the logo reappears. If I keep pressing the buttons the phone reboots again, and again, and again, mever reaching download mode.
If I let go of the power button and keep pressing vol- and bixby the phone stays black and won't even show the logo. Nothing happens. If I let go of either of the two buttons the logo appears again.
It won't boot, won't go into recovery or go into dl mode.
I'm doing all this while it's plugged into the usb port of my pc, and it doesn't get recognized. Samsung 300k tool doesn't recognize it either.
Now I know the meaning of "bricked" lmao.
Does anyone know how to possibly fix this?
Pressing only the power button for a minute literally does nothing. Like hell, how is that even possible?
You can try this to go to download mode:
Vol down + bixby + usb cable connect to PC
It's advisable to charge battery first before flashing firmware.
XTrail02 said:
You can try this to go to download mode:
Vol down + bixby + usb cable connect to PC
It's advisable to charge battery first before flashing firmware.
Click to expand...
Click to collapse
I tried that for like a thousand times already but now it chose to magically work somehow.
I think I peed myself a little when that ugly turquoise screen appeared and I screamed from sheer happyness.
THANK you!!!
The problem that doesn't stop giving lmao.
Got into DL mode, got odin to start, but after like 10 seconds my phone dies and odin fails.
Now I cant get into DL mode, but rather only the "an error occurred while updating the device software. use the emergency recovery function in the smart switch pc software."
Could it be the battery that simply dies?
hoeni said:
The problem that doesn't stop giving lmao.
Got into DL mode, got odin to start, but after like 10 seconds my phone dies and odin fails.
Now I cant get into DL mode, but rather only the "an error occurred while updating the device software. use the emergency recovery function in the smart switch pc software."
Could it be the battery that simply dies?
Click to expand...
Click to collapse
Yes most probably a discharged battery. Hopefully you can go to DL mode again after charging your phone.
hello,
I've and S10e and because an important app to me I need to go back to android 9 where it works.
I've read a lot info about downgrade, but no one says ROOT/UNBRICK.
Can someone inform if there is a way of downgrade without ROOT (maintaining the warranty).
thanks in advance
P.S.: Maybe too naive question, sorry for that

Categories

Resources