I charged my Mi A2 overnight and woke this morning to find that it won't boot past the Mi A2 splash screen; it shows the splash screen for a few of seconds and then dies. I read advice to hold down power and 'up' keys, this just resulted in the same. I tried power and 'down' key and that got me as far as the Fast Boot splash screen, but no further (phone just continued to display that splash screen). I've tried taking the SIM out and turning it on - no change. I tried opening it up and disconnecting the battery for 3 minutes - no change. I'd be very grateful if anyone could suggest a fix. I know this is hugely unhelpful, but I can't remember what I did to the phone in terms of unlocking the bootloader and/or rooting, but I have a feeling I left it stock (I've owned the phone for a couple of years and haven't changed anything material since initial setup).
Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?
Martinocom said:
Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?
Click to expand...
Click to collapse
Thank you very much for your help.
Executing fastboot reboot via adb just brought me back to the Android One splash screen for a few seconds before the screen went black.
Changing the active slot to both A and B gave me the following error message:
FAILED (remote: 'Slot Change is not allowed in Lock State')
Pressing up + power when turning on just brought me to the Android One splash screen for a few seconds before the screen went black. I held those two buttons down for several minutes and the same thing kept happening: splash screen followed by black, repeatedly.
Is there anything else I can try?
You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.
Martinocom said:
You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.
Click to expand...
Click to collapse
Thank you.
If anyone reading knows of a way to get my phone to boot without losing my data I'd be very grateful for your help.
Related
Anyone!!!
Please help me, i'm entirely in despair now with my HTC N1 phone.
This place or people from XDA are my only hope, and I wish was in the right place.
Here's my concern, At the first place my POWER BUTTON is not working.
I Installed CM7.2 on my phone and it went great, I decided to install a semi-transparent status bar so I flash a .zip in it. After it reboots, it was stuck at the "X" screen.
The only thing I can do is to have a battery shock on my phone while holding the track ball, and it sends me to a white screen with skating androids.
From there I tried using the Fastboot commands but I got an error saying "FAILED <remote: not allowed>"
I'm pretty sure that "USB Debugging" is checked. And I can even erase the cache from there, but when i tried the "fastboot flash recovery file.img" or any related command like that it says "FAILED <remote: not allowed>".
When using ADB commands my phone wasn't detected. I tried all kinds of USB drivers and trick already, but got me nowhere.
Also I've seen that you cannot use ADB on a white screen, how am I going to get to a non white screen if my power button is not working?
I'm entirely helpless right not. I already went to different best cell repair shop all over our country to fix my power button, since it was the root cause of my misery but even them can't help me with that.
Please help me everyone, I'm a complete noob or even a moron on this.
I'm completely helpless right now.
I'll do anything for someone who'll help me. PLEASE!! :crying:
emeryreme said:
Anyone!!!
Please help me, i'm entirely in despair now with my HTC N1 phone.
This place or people from XDA are my only hope, and I wish was in the right place.
Here's my concern, At the first place my POWER BUTTON is not working.
I Installed CM7.2 on my phone and it went great, I decided to install a semi-transparent status bar so I flash a .zip in it. After it reboots, it was stuck at the "X" screen.
The only thing I can do is to have a battery shock on my phone while holding the track ball, and it sends me to a white screen with skating androids.
From there I tried using the Fastboot commands but I got an error saying "FAILED <remote: not allowed>"
I'm pretty sure that "USB Debugging" is checked. And I can even erase the cache from there, but when i tried the "fastboot flash recovery file.img" or any related command like that it says "FAILED <remote: not allowed>".
When using ADB commands my phone wasn't detected. I tried all kinds of USB drivers and trick already, but got me nowhere.
Also I've seen that you cannot use ADB on a white screen, how am I going to get to a non white screen if my power button is not working?
I'm entirely helpless right not. I already went to different best cell repair shop all over our country to fix my power button, since it was the root cause of my misery but even them can't help me with that.
Please help me everyone, I'm a complete noob or even a moron on this.
I'm completely helpless right now.
I'll do anything for someone who'll help me. PLEASE!! :crying:
Click to expand...
Click to collapse
You don't need to flash the recovery in this situation. Try to reboot the phone via fastboot command and issue these commands in fastboot:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase cache
Once complete, just reflash the CM 7.2 ROM again.
I am new to the forums and I need your help. The display on my LGWR went black after update even on cradle. It cannot even connect to my mobile via BT. The only thing it does is vibrate when the button is pushed and the heart sensor blinks a single time (when it turns on I guess.) as the vibration is a small one. When connected to PC running Windows 7, it is detected as Android Bootloader Interface, but ADB does not show any attached devices. Fastboot does show some alphanumerical device when (fastboot devices command is run). I have disassembled to remove the battery and tried to run it without the battery on cradle to no avail. Your help is needed as to what to do.
So it seems to hang in fastboot mode?
Try some fastboot commands then:
Code:
fastboot getvar all
fastboot reboot
Dear Ranf.
Many thanks for your reply. I ran fastboot getvar all and this is what I got. Screenshot is attached. Please guide me further.
Thanks.
Looks like you already downloaded the firmware? Right?
If so start with wiping cache and userdata:
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
I have downloaded the M1D63X boot, recovery and system (Disc Image Files) saved in my PC. They are not present in the SD card of LGWR. Shall I execute the commands or can I use fastboot and install this M1D63X on the LGWR. Thanks for your support.
The 2 format commands are basically the same as a factory reset. Please try them and then reboot.
Where did you download the file (URL please)?
Boot and recovery usually aren't trouble makers. system.img will if it's not a sparse image file.
The download like is as under Ranf:
http://forum.xda-developers.com/g-watch-r/development/fastboot-zip-factory-images-t3405311
Dear Ranf,
I tried to run Fastboot flash cache, and this is what the result was. Please guide.
Oh I see: you first need to unlock the bootloader with:
Code:
fastboot oem unlock
How can I dod that, as the screen is blank on the watch. I have tried it, fastboot says OKAY on my PC screen, but the watch does not reboot on its own and I have to manually restart it to get recognized in PC at Android ABD Interface. What can I do.
After running "fastboot oem unlock" you somehow need to acknowledge your decision (I'm a Sony SW3 user)
Either swipe the screen from tp left to bottom right or
press the power button.
Do you see anything on the watch screen when in fastboot mode?
Dear Ranf,
I finally able to unlock bootloader and formatted cache and userdata and then rebooted it, but the problem still exists i.e. black screen and only vibration.
Is there any way I can install stock Rom via fastboot and if so please guide me how and from which url should I download the files.
Thanks.
Screenshot of the fastboot format cache and userdata is attached for your perusal.
At 1st look the download you have is fine.
You need to flash 3 partitions:
Code:
fastboot flash boot M1D63X_boot.img
fastboot flash recovery M1D63X_recovery.img
fastboot flash system M1D63X_system.img
When you see errors at any of these steps post them here.
Thankfully all things well without any errors, but the watch is still the same, no display whatsoever. I am really devastated now. If there is anything else that can be done, please guide.
Screenshot of the processes is attached.
Sorry I must admit I'm a bit lost now. Best you ask @vt0r in the thread where you got the firmware from.
Thanks a lot Ranf. God Bless You.
You have done all steps that you can do, probably your display is broken...
I'm sorry...
When your watch starts, you see the lg logo?
Is there a way to check if the display is broken as when I disassembled the watch everything looked fine with no signs of wear or moisture. The battery also is not holding charge as when you put the watch on cradle it vibrates but off of it, vibration stops. How can I charge the battery manually.
Hey,
my watch had exactly the same problem.
I had to repair it. They had to replace the mainboard.
Luckily the warranty paid for this.
Lucas
Lucky for you that you had warranty left. For me there are two problems. First no warranty left and secondly replacement parts are not available here in Pakistan, so if there is any online store from I can manage the parts, do let me know Lucas.
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
vetteguy82 said:
Hey everyone
Not sure if anyone can help
I just got some used 5th gen tablets, they were in a storage unit i just purchased. I turned on one of the fire units and it says it was a kids fire, so no real use to me. I hit power to standby and left it in my office, went back to list it and it was updated with new software. The second one, seems like it is stuck in a boot loop, comes on and goes off again. So i looked at the one that updated, said it now updated, had 5.6 on it, so i said maybe i could use it. Did some research, read you can but just android on it.
Well, i read you have to downgrade to 5.3 or older to install android. Not even sure if this is right.
So i followed some youtube genius with software from rootjunky.
I used the adb to flash update-kindle-global-37.5.4.2_user_542168620.bin
Everything was working, installing 100%, then i unplugged and selected 1 from the tablet to reboot.
Needless to say, nothing comes on now, no logo, no nothing, will not respond to recovery mode, down and power.
I just tried taking the back off and unplugging the battery and holding power 20 secs, nothing.
Anyone have any ideas to salvage these, or one of them or are they paperweights haha?
Good news is, the unit had all kinds of stuff in it, i have made my money back already, these were just bonus
Any help would be great, thanks
Click to expand...
Click to collapse
Permanently bricked; can't downgrade below 5.4. Sell it for parts or take it to the target range.
Thanks
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
vetteguy82 said:
Thanks for the reply
Ok, so the one that will not turn on at all , well technically it must be on when i plug it into my pc, it does chime, and then a few seconds later it chimes again. Like it is turning itself on and off, but because you can not see anything on the screen, you can not tell.
What about the second one? It turns on and you see amazon, but then it turns itself off. It does let you go to fastboot and recovery in the corner of the screen using the buttons. However, all you see is that, recovery only says recovery, does not go into the recovery menu.
Any ideas if the second one is recoverable?
Thanks
Click to expand...
Click to collapse
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
thanks
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Davey126 said:
If you can not access the stock recovery menu there is no known method for recovering these devices with one exception: early build devices (bootloader version 5.00 & 5.01) can boot a twrp image from fastboot. If that works you'll be able to install a custom ROM (two choices) assuming nothing else is wrong with the hardware.
fastboot boot <twrp.img>
Click to expand...
Click to collapse
vetteguy82 said:
I must be doing something wrong again, i download the twrp.imga dn saved it in the fast boot adb folder. I put the kindle in fastboot mode, and plugged into pc, driver installed, from folder i went in to command prompt. in command prompt i added fastboot twrp.img and hit enter command prompt shows all the command prompts and definitions.
Is there something else i should do?
Thanks
Click to expand...
Click to collapse
You need to install this tool on the host PC. Make note of the installation folder as you will need to execute the fastboot command from there. You'll also need to copy any necessary files (eg: twrp image) to that folder unless versed in referencing other folders from the command prompt.
Keep in mind it is highly unlikely your looping device will be able to boot twrp. Only the earliest models had this vulnerability which Amazon quickly plugged.
Hi Guys,
My phone suddenly stuck at this screen since may :
Android Recovery
Xiaomi/jasmine/jasmine_sprout
9/PKQ1.180904.001/V10.0.9.0.PDIMIXM
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device.
- Try again
- Factory data reset
If i press try again, sometime it will go to fastboot screen.
I can go into recovery mode here but i not sure which step i should do next.
Reboot system nowreboot to bootloader
apply update from ADB
apply update from sd CARD
wipe data/factory reset
Mount/sstem
view recovery logs
run graphics test
run locale test
power off
I'm not a very tech savvy person, i would really appreciate some help as i have data inside my phone which i need. So if possible i would like to retain the data.
I tried like EDL,fastboot,and flashing none seem to work. Of course I may be doing it wrong.
Can anyone guide me step by step I be happy to give an reward via paypal.
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
blazessdd said:
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
Click to expand...
Click to collapse
Thank you so much for replying.
Nope, but I can do EDL to unlock bootloader, I already disassemble the device a few times.
Just that every time I try to flash it , it give me some error. like Bluetooth error or the version error .
Which I watch thousand of video to work but it's doesn't help. Or maybe I just watched the wrong video
Ok tell me exactly what are you doing and where you have downloaded the rom.
If it's corrupted and you try to flash it you will lose the data... Was debug USB activated on developer settings?
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
epilifio said:
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
Click to expand...
Click to collapse
You can try to short the edl points so you can flash the ROM again
blazessdd said:
You can try to short the edl points so you can flash the ROM again
Click to expand...
Click to collapse
I already made this attempt, "adb reboot edl" reports the message "error: '(null)' not found
Xiaomi never again
So I've had a Redmi Note 10S for about a year and I wanted to flash a rom on it! (PixelExperience to be exact), and I think I broke the system- completely
When booting the device up, the "Redmi" boot screen will show up just fine, like nothing, but then, when trying to load into anything (system, recovery, or even fastboot). The device will just.... display orange horizontal lines, to have a more exact description:
The lines will appear suddenly, doing a white blink for a split second, and then go back to orange, fading away in no time. Then, the screen stays black for a few seconds, before going back to booting into the Redmi screen.
Is there any way to fix it? Or did i just brick my phone for good?
Thank you for reading and helping, and sorry for any mistakes while writting-
NormalFery said:
So I've had a Redmi Note 10S for about a year and I wanted to flash a rom on it! (PixelExperience to be exact), and I think I broke the system- completely
When booting the device up, the "Redmi" boot screen will show up just fine, like nothing, but then, when trying to load into anything (system, recovery, or even fastboot). The device will just.... display orange horizontal lines, to have a more exact description:
The lines will appear suddenly, doing a white blink for a split second, and then go back to orange, fading away in no time. Then, the screen stays black for a few seconds, before going back to booting into the Redmi screen.
Is there any way to fix it? Or did i just brick my phone for good?
Thank you for reading and helping, and sorry for any mistakes while writting-
Click to expand...
Click to collapse
just reflash stock firmware and done, next time read installation instructions for a rom to avoid bricks
tutibreaker said:
just reflash stock firmware and done, next time read installation instructions for a rom to avoid bricks
Click to expand...
Click to collapse
I wish I could do that buuut the fastboot mode, as stated before, is unreachable. I can't access it, not recovery or the system itself, so I can't just "reflash stock firmware" because I can't access the mode to reflash it.
NormalFery said:
I wish I could do that buuut the fastboot mode, as stated before, is unreachable. I can't access it, not recovery or the system itself, so I can't just "reflash stock firmware" because I can't access the mode to reflash it.
Click to expand...
Click to collapse
mmm you may need use mtk client and spflastool to restore your device, you can get info and guide for that in youtube
tutibreaker said:
mmm you may need use mtk client and spflastool to restore your device, you can get info and guide for that in youtube
Click to expand...
Click to collapse
Sorry for the REALLY late reply, I've been trying mtk client, and after trying to write something into the device (Unsuccessfully of course, i have .img files, and the program requires .bin files, which I do not have at all) and now my device says "Dm-verity corruption"
saying that the device itself is corrupted
Also now the redmi logo does some kind of... fade out too if no volume buttons are pressed after pressing the power button (to continue the booting process)
The dm verity can be bypassed with unlocked bootloader ando fastboot commands dm-verity corrupted fix after unlocking bootloader:
Plug your phone with fastboot to PC and open command prompt.
Type:
fastboot oem cdms
Fastboot reboot and done
NormalFery said:
So I've had a Redmi Note 10S for about a year and I wanted to flash a rom on it! (PixelExperience to be exact), and I think I broke the system- completely
When booting the device up, the "Redmi" boot screen will show up just fine, like nothing, but then, when trying to load into anything (system, recovery, or even fastboot). The device will just.... display orange horizontal lines, to have a more exact description:
The lines will appear suddenly, doing a white blink for a split second, and then go back to orange, fading away in no time. Then, the screen stays black for a few seconds, before going back to booting into the Redmi screen.
Is there any way to fix it? Or did i just brick my phone for good?
Thank you for reading and helping, and sorry for any mistakes while writting-
Click to expand...
Click to collapse
Just download Fastboot flash able rom in your pc.
Extract that, then put your phone to Fastboot mode and se a file in the extracted file named (Flash_all.) Then hit these name, after that u see a CMD WILL OPEN AND NOTHING TO DO it's automatically flashed.
tutibreaker said:
The dm verity can be bypassed with unlocked bootloader ando fastboot commands dm-verity corrupted fix after unlocking bootloader:
Plug your phone with fastboot to PC and open command prompt.
Type:
fastboot oem cdms
Fastboot reboot and done
Click to expand...
Click to collapse
First off, Sorry for the delayed reply second of all
i still can't access Fastboot, as stated in the post
No fastboot, no recovery, no anything, so I can't go into fastboot mode at any point
NormalFery said:
First off, Sorry for the delayed reply second of all
i still can't access Fastboot, as stated in the post
No fastboot, no recovery, no anything, so I can't go into fastboot mode at any point
Click to expand...
Click to collapse
try this
Clone latest revision of MTKClient from GitHub and use it to flash your device.
Flash all partitions possible, skipping super and userdata.
Once you're done with that, reboot to fastboot and flash super and userdata from there.
Also wipe `md_udc` and don't forget `fastboot OEM cdms`.
Now after rebooting, you should be back on MIUI setup.
From then on, just install custom recovery and flash the ROM right away, of course not forgetting to format data.