Updated to Android P, now phone won't boot unless ... - Xiaomi Mi A2 / 6X Questions & Answers

I recently updated my Mi A2 via OTA update by using Express VPN to connect to India. Everything was fine until I powered off my device. It would not turn back on (no boot animation or anything).
However, I then proceeded to plug in the charging cable. After doing so, my screen lit up and I was able to get my phone to boot.
Now the problem remains that every time I turn my device off, it won't boot unless I plug it in to a power source.
Please, anyone experienced this? Is there a way to fix it? Would an update further down the line fix an issue like this?
Please, I can use my phone normally when it's on but this thing with the not being able to boot is just bugging the freak out of me.

I've had a problem like this before, hold power only gives a vibration and doesn't boot, just keep holding the power button

It freaggin worked
Nebrassy said:
I've had a problem like this before, hold power only gives a vibration and doesn't boot, just keep holding the power button
Click to expand...
Click to collapse
I honestly didn't expect this to work but it's as you say. My phone would just vibrate and nothing more.
Following your instructions, I held the power button longger than usual and it finally booted. You sir are a legend. Thank you !!
But it would be awesome to know why this happens though. Was it due to something in the pie update? and will I need to be holding down the power button considerably longger (around 5-6 seconds) moving forward. Or will it boot like normal now?
Again, before anything else. Thank you

IjazCI said:
Yes. On pie i do have this issue. Its normal
Click to expand...
Click to collapse
Well I hope it gets fixed down the line. Thank you!!

In India, I received notification that I got pie update, I downloaded, installation process was done but when my device rebooted there was only blank screen and when I press power button, it vibrates, but after pressing buttons and volume button. . . My device successfully booted into 8.1.0 lol I don't know what happened, anyone know how fix it?

Yube0 said:
I honestly didn't expect this to work but it's as you say. My phone would just vibrate and nothing more.
Following your instructions, I held the power button longger than usual and it finally booted. You sir are a legend. Thank you !!
But it would be awesome to know why this happens though. Was it due to something in the pie update? and will I need to be holding down the power button considerably longger (around 5-6 seconds) moving forward. Or will it boot like normal now?
Again, before anything else. Thank you
Click to expand...
Click to collapse
I'm not sure why this happens, I don't know if it started right when I updated or when I made some modifications to system, but I solved it by flashing the update again in recovery

Yube0 said:
I recently updated my Mi A2 via OTA update by using Express VPN to connect to India. Everything was fine until I powered off my device. It would not turn back on (no boot animation or anything).
However, I then proceeded to plug in the charging cable. After doing so, my screen lit up and I was able to get my phone to boot.
Now the problem remains that every time I turn my device off, it won't boot unless I plug it in to a power source.
Please, anyone experienced this? Is there a way to fix it? Would an update further down the line fix an issue like this?
Please, I can use my phone normally when it's on but this thing with the not being able to boot is just bugging the freak out of me.
Click to expand...
Click to collapse
It's a strange uncommon issue !

Nebrassy said:
I'm not sure why this happens, I don't know if it started right when I updated or when I made some modifications to system, but I solved it by flashing the update again in recovery
Click to expand...
Click to collapse
Hi bro,
May i know how did you do that.
How did you flash update through recovery?

Related

HELP, My phone refuses to boot up.

It started as soon as I received a phone call from my brother and we were in the middle of a conversation when the phone suddenly goes off. I tried to restart it, I even removed the battery and replaced it but when I press the power button I get the initial boot sequence showing the htc logo and then the phone would just go of. I thought that maybe the battery is low but when I plug it to a power outlet it keeps trying to boot but keeps switching off and it just does this over and over.
Please I don't know if anyone has encountered this problem before, I really don't know what to do.
scently said:
It started as soon as I received a phone call from my brother and we were in the middle of a conversation when the phone suddenly goes off. I tried to restart it, I even removed the battery and replaced it but when I press the power button I get the initial boot sequence showing the htc logo and then the phone would just go of. I thought that maybe the battery is low but when I plug it to a power outlet it keeps trying to boot but keeps switching off and it just does this over and over.
Please I don't know if anyone has encountered this problem before, I really don't know what to do.
Click to expand...
Click to collapse
Try a Hard Reset using the device buttons:
1. With the phone off. If it’s frozen or unresponsive, pull then replace the battery.
2. Press and hold the Volume Up and Volume Down buttons and power the phone back on.
3. Continue to hold Volume Up and Volume Down until a factory reset screen appears.
Hope this helps!
weepatc said:
Try a Hard Reset using the device buttons:
1. With the phone off. If it’s frozen or unresponsive, pull then replace the battery.
2. Press and hold the Volume Up and Volume Down buttons and power the phone back on.
3. Continue to hold Volume Up and Volume Down until a factory reset screen appears.
Hope this helps!
Click to expand...
Click to collapse
But this ill wipe out all my data and I don't know how to back up on windows phone.
scently said:
But this ill wipe out all my data and I don't know how to back up on windows phone.
Click to expand...
Click to collapse
At the moment you've lost all your data anyway!!!!
weepatc said:
At the moment you've lost all your data anyway!!!!
Click to expand...
Click to collapse
Well I just did that but the problem persist. I should note that occasionally it does complete its boot up and I can use the phone but it can go off at any time and once it does this, i cannot get it to completely boot up. Once it attempts a boot up and goes off I cannot even restart it by pressing the power button until I replace the battery or plug it into a power socket or the computer at which point it will just keep booting up and shutting down.
Something far wrong there. Get a replacement device.
Sent from my HTC HD7 using Board Express
weepatc said:
Something far wrong there. Get a replacement device.
Sent from my HTC HD7 using Board Express
Click to expand...
Click to collapse
I think I've fixed it, I flashed my phone and it seems to be working again. Thanks for your help though
Glad to hear you got a result ;-)
Sent from my HTC HD7 using Board Express
ya I had same issue... (random reboots and then changes not saved). Flashed the phone and all was good.
HD7 stuck in boot screen
scently said:
I think I've fixed it, I flashed my phone and it seems to be working again. Thanks for your help though
Click to expand...
Click to collapse
PaullikesWINMO said:
ya I had same issue... (random reboots and then changes not saved). Flashed the phone and all was good.
Click to expand...
Click to collapse
Hi, I have got the same problem on my HD7 and I am completely noob to many new words Goldcard, jailbroken, etc. Would you please advise me exactly what you did (i mean flahing procedure) and really appriciate any help.
Well if you have got an O2 HD7, then I would advise you to get one of the O2 ROMS from ansar, download it then press and hold the volume down button when booting up your device, connect the phone to your pc and start the app. More instructions in the HD7 development thread.
There's nothing wrong the phone. Don't hard reset or flash it. It happens from time to time, just give it some time and eventually you will see a battery icon appear. Then after awhile it will boot up.
Again, do not flash or hard reset just be patient. I believe it just needs to drain all the way down as it doesn't have enough power to fully boot.
Not booting up
Hi,
My T Mobile hd7 is been restarting after it shows the htc logo..It was all of a sudden after i connected to my pc this happened ...Tried to flash it with ansar tmobile update..problem persists...Dont knw how to use goldcard..please help me out..
Thank u and Best Regards

Some serius help needed. Bootloop, stuck, bootloader not working etc..

Hi. To start with I bought a phone from a friend which I knew was faulty but decided to take my chances and try to fix it. He claims he did nothing to the phone but don't know for sure. Phone is in constant bootloop, Goes until splash screen and reboots. Worst yet to come - even bootloader menu restarts on constant basis when i try to get into it. Meaning it goes into bootloader but restarts in few seconds before i can get to factory reset. Computer is not picking up this device but i also don't have any drivers installed but don't even know how to install them with a phone in this state. Is there anything i can do about it? Been with Samsung for the past few years and here is everything completely different so don't know much about adb but am a quick learner and can follow any steps! I can provide picture of bootloader if it would be any helpful.
michal_alton said:
Hi. To start with I bought a phone from a friend which I knew was faulty but decided to take my chances and try to fix it. He claims he did nothing to the phone but don't know for sure. Phone is in constant bootloop, Goes until splash screen and reboots. Worst yet to come - even bootloader menu restarts on constant basis when i try to get into it. Meaning it goes into bootloader but restarts in few seconds before i can get to factory reset. Computer is not picking up this device but i also don't have any drivers installed but don't even know how to install them with a phone in this state. Is there anything i can do about it? Been with Samsung for the past few years and here is everything completely different so don't know much about adb but am a quick learner and can follow any steps! I can provide picture of bootloader if it would be any helpful.
Click to expand...
Click to collapse
Send a picture of the bootloader while I find the drivers you need
Seems like battery is completely dead as it only reboots when there is power supply connected, but then it won't turn off (any charging light don't come on, not sure if it should though). Just now i've seen a vodafone logo for a very short second when I connected to pc from charger. But phone rebooted again just after.
HTC_Phone said:
Send a picture of the bootloader while I find the drivers you need
Click to expand...
Click to collapse
edit. downloaded drivers (4.8) but that didn't change anything and windows still doesn't pick up device.
After connecting my one to computer for past 3 hours its started more frequently boot and showing Vodafone menu but still restarts shortly after. Vodafone logo shows on and lights on soft buttons starts flashing like 3 times and than it keeps rebooting. Does it mean anything?
michal_alton said:
Seems like battery is completely dead as it only reboots when there is power supply connected, but then it won't turn off (any charging light don't come on, not sure if it should though).
Click to expand...
Click to collapse
Have you checked this: http://forum.xda-developers.com/showthread.php?t=2481211
michal_alton said:
After connecting my one to computer for past 3 hours its started more frequently boot and showing Vodafone menu but still restarts shortly after. Vodafone logo shows on and lights on soft buttons starts flashing like 3 times and than it keeps rebooting. Does it mean anything?
Click to expand...
Click to collapse
That almost sounds like your POWER button is stuck!! Are you able to completely power off, and it stays off.
I think i know what it is. Power button stuck and keeps restarting device. Although i can feel pressing it, this is what it looks like.
nkk71 said:
Have you checked this: http://forum.xda-developers.com/showthread.php?t=2481211
That almost sounds like your POWER button is stuck!! Are you able to completely power off, and it stays off.
Click to expand...
Click to collapse
Didn't see your comment but this is exactly how it looks to me. I can't switch off phone and in bootloader it acts like i was pressing power button. Although it operates normally meaning that it can be pressed down. Arranged warranty repair with HTC and they are collecting phone tomorrow.
michal_alton said:
Didn't see your comment but this is exactly how it looks to me. I can't switch off phone and in bootloader it acts like i was pressing power button. Although it operates normally meaning that it can be pressed down. Arranged warranty repair with HTC and they are collecting phone tomorrow.
Click to expand...
Click to collapse
Good luck mate, but definitely sounds like the power button is stuck
It's been fixed under warranty by HTC. They replaced motherboard on mine HTC. So all good

Bricked HTC One

So I've posted this problem here before:
http://forum.xda-developers.com/htc-one/help/please-confirm-totally-bricked-t2831685
Just wondering if any of you would know how to fix it.
Probably no one will want to read that much, so here's the short version:
-Can't enter bootloader
-Can't enter recovery
-ABD doesn't work
-Fastboot doesn't work
Reasons why I think it still can get fixed:
-It stills turns on.
-Battery has ran out a couple of times, so it still charges.
-Windows 8 makes a pulg-in sound when I connect the phone to the laptop.
The phone also keeps rebooting each 6 to 10 seconds, so it is actually a plug-in, and plug-out, and a plug-in, and so on...
It doesn't list anything inside Device Manager.
Some people have tried Dexter's fix for bricked devices, but I think it only works for devices listed at least as QHSUSB_DLOAD.
Mine is not recognized that way... or at all.
That plug-in sound though.
HTC Drivers Installed:
setup_3.1.24.5_htc.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTC Driver 4.10.0.001.exe
HTC Sync Manager
KomuroXV said:
So I've posted this problem here before:
http://forum.xda-developers.com/htc-one/help/please-confirm-totally-bricked-t2831685
Just wondering if any of you would know how to fix it.
Probably no one will want to read that much, so here's the short version:
-Can't enter bootloader
-Can't enter recovery
-ABD doesn't work
-Fastboot doesn't work
Reasons why I think it still can get fixed:
-It stills turns on.
-Battery has ran out a couple of times, so it still charges.
-Windows 8 makes a pulg-in sound when I connect the phone to the laptop.
The phone also keeps rebooting each 6 to 10 seconds, so it is actually a plug-in, and plug-out, and a plug-in, and so on...
It doesn't list anything inside Device Manager.
Some people have tried Dexter's fix for bricked devices, but I think it only works for devices listed at least as QHSUSB_DLOAD.
Mine is not recognized that way... or at all.
That plug-in sound though.
HTC Drivers Installed:
setup_3.1.24.5_htc.exe
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTC Driver 4.10.0.001.exe
HTC Sync Manager
Click to expand...
Click to collapse
So wait. Why can't you enter? Because it reboots too fast? Can you shut off your phone? If yes do it so and then try to reboot to bootloader. And if it reboots there too every 5 to 6 seconds, you're gonna have a big problem. Within 5-6 seconds you can't hide the rooted state of your device and this also means that you can't return it.
But if you can get to your bootloader and if you can fastboot connect it, I'd recommend using a RUU if you are S-OFF. Otherwise I'd try to reinstall another recovery and from the recovery I'd reinstall a new OS.
Anyways, just try to get to the bootloader and do what I told you to. If my instructions were too unaccurate, just mention or quote me, I'll get back to you.
LibertyMarine said:
So wait. Why can't you enter? Because it reboots too fast? Can you shut off your phone? If yes do it so and then try to reboot to bootloader. And if it reboots there too every 5 to 6 seconds, you're gonna have a big problem. Within 5-6 seconds you can't hide the rooted state of your device and this also means that you can't return it.
But if you can get to your bootloader and if you can fastboot connect it, I'd recommend using a RUU if you are S-OFF. Otherwise I'd try to reinstall another recovery and from the recovery I'd reinstall a new OS.
Anyways, just try to get to the bootloader and do what I told you to. If my instructions were too unaccurate, just mention or quote me, I'll get back to you.
Click to expand...
Click to collapse
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
KomuroXV said:
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
Click to expand...
Click to collapse
I wonder if this is a damaged partition - and it's tricky to solve
@nkk71 what do you think?
stovie_steve said:
I wonder if this is a damaged partition - and it's tricky to solve
@nkk71 what do you think?
Click to expand...
Click to collapse
I made a video, hope it helps.
https://www.youtube.com/watch?v=GMuo-kvIGIc
Suggestions: Mute it :silly:
KomuroXV said:
I made a video, hope it helps.
https://www.youtube.com/watch?v=GMuo-kvIGIc
Suggestions: Mute it :silly:
Click to expand...
Click to collapse
only thing i noticed in the video is your holding volume up not volume down. Volume up plus power will not load the bootloader
clsA said:
only thing i noticed in the video is your holding volume up not volume down. Volume up plus power will not load the bootloader
Click to expand...
Click to collapse
I've tried both.
Here's another one anyways.
https://www.youtube.com/watch?v=1zyA6XGFEpo&list=UUzlEfhRw_dyaJ7aAFpWC7-A
KomuroXV said:
First of all, thank you for replying.
On topic.
Phone is actually turned off right now.
Battery died again.
Only way to turn it back on is connecting it to the wall charger and sometimes to the laptop.
But as soon as I do...
1. Phone turns on.
2. Shows the white screen with only the green HTC logo.
3. If it's plugged to the laptop then I hear that "plug in" sound Windows does.
4. After a few seconds phone reboots... and reboots... and reboots... doing the same I just stated.
I also get to hear the Windows "plug-out" sound everytime it turns off to reboot.
Not sure of why I can't enter the boot loader.
This problem started after I decided to turn off my phone while it was installing a custom recovery (Process was being slow and I am OCD like that)
My paranoic guesses are that I screwed it so bad I wiped the bootloader also, but is that even possible?
Click to expand...
Click to collapse
Hmmm, as the others said this might be really hard to solve.
Most likely this here won't solve your problem but it's better to try it than to just let it be:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
I heard about that this here could get some devices to fully boot after they had been in such a strange loop as your phone is:
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
I couldn't watch the second video (it's private) where you pressed the volume down button. But I believe you're right.
@stovie_steve what is the indication for this damaged partition? I can't imagine which partition would lead into a such behaviour.
Anyways.. @KomuroXV just try what I've writtten if it doesn't work, just mention or quote again, I'll try to look up what it could be.
Good luck!
LibertyMarine said:
Hmmm, as the others said this might be really hard to solve.
Most likely this here won't solve your problem but it's better to try it than to just let it be:
Hold your HTC One below a bright lights source and hold the power button for about 15 seconds or even longer. The charging light will light up. Then hold down the volume down button and try different key combinations!
I heard about that this here could get some devices to fully boot after they had been in such a strange loop as your phone is:
A: Hold volume down and volume up button and the power button for about 90 seconds. If this doesn't work, try holding your phone below bright light again
I couldn't watch the second video (it's private) where you pressed the volume down button. But I believe you're right.
@stovie_steve what is the indication for this damaged partition? I can't imagine which partition would lead into a such behaviour.
Anyways.. @KomuroXV just try what I've writtten if it doesn't work, just mention or quote again, I'll try to look up what it could be.
Good luck!
Click to expand...
Click to collapse
Oh... I fixed the private video thing, sorry about that.
I've tried the bright light + power + volume down button combination before but it never managed to make the phone to boot properly.
It did have some little behaviour changes though...
Like... it was more responsive for the button combination making it turn off kind of faster, just to reboot again some seconds after anyway.
Tried it again just now, but still nothing different. :/
Same stuff as before.
I could make another video if you guys wanted to make sure, but it'd be me just pressing the volume down + power under the bright light for nothing but the loop, besides the responsiveness I've told you it seems to get to pressing the buttons.
Anyway, just tell me if making another video would help.
By the way.
Some months ago (Yeah, I have a lot of time dealing with this) I was able to turn it on with or without the charger, now it seems like it's only possible when it's "charging" or connected to the laptop, regardless of bright light or not.
Guess that was because it had charge before, now it doesn't and it's unable to actually charge the battery.
Which would explain why the orange little charging light is off now.
I'm open to any new ideas. :/
Thank you guys for all your support.
KomuroXV said:
Oh... I fixed the private video thing, sorry about that.
I've tried the bright light + power + volume down button combination before but it never managed to make the phone to boot properly.
It did have some little behaviour changes though...
Like... it was more responsive for the button combination making it turn off kind of faster, just to reboot again some seconds after anyway.
Tried it again just now, but still nothing different. :/
Same stuff as before.
I could make another video if you guys wanted to make sure, but it'd be me just pressing the volume down + power under the bright light for nothing but the loop, besides the responsiveness I've told you it seems to get to pressing the buttons.
Anyway, just tell me if making another video would help.
By the way.
Some months ago (Yeah, I have a lot of time dealing with this) I was able to turn it on with or without the charger, now it seems like it's only possible when it's "charging" or connected to the laptop, regardless of bright light or not.
Guess that was because it had charge before, now it doesn't and it's unable to actually charge the battery.
Which would explain why the orange little charging light is off now.
I'm open to any new ideas. :/
Thank you guys for all your support.
Click to expand...
Click to collapse
hey guys, sorry been/am a bit busy lately, so don't get to respond/contribute much
OP, looks like your power button is messed up? (ie it's continually "pressed") you can try to nudge a little, to see if it gets unpressed
after "nudging" a little, don't even bother pressing it, when the phone reboots, just hold voldown to get to bootloader
EDIT: be gentle :silly: :laugh:
nkk71 said:
hey guys, sorry been/am a bit busy lately, so don't get to respond/contribute much
OP, looks like your power button is messed up? (ie it's continually "pressed") you can try to nudge a little, to see if it gets unpressed
after "nudging" a little, don't even bother pressing it, when the phone reboots, just hold voldown to get to bootloader
EDIT: be gentle :silly: :laugh:
Click to expand...
Click to collapse
hey @nkk71, but in what way does that explain the fact that it only boots when the phone is connected to a power source? And he also holds down the powerbutton the first time. I can't find an explanation for this.
@KomuroXV but what nkk suggested is a good idea, but just be very very gentle. I f#cked up my powerbutton pressing it too much. Luckily HTC believed my (altered) story and I got a replacement.
What you can try is to just go with a paper edge between the power button and the Magnesium surrounding then try to much it upwards and downwards, this may help "unstucking" your powerbutton if that's even the case.
I'm gonna test the with my phone how long it takes to reboot if I hold down the power button (will post again in a few min). If it's about the same as shown in your vid, it might really be a stuck power button.
LibertyMarine said:
hey @nkk71, but in what way does that explain the fact that it only boots when the phone is connected to a power source? And he also holds down the powerbutton the first time. I can't find an explanation for this.
Click to expand...
Click to collapse
1) battery drains, he plugs it in -> boom, it turns on
2) it reboots no matter what button combo he tries
3) it's not even staying on the bootsplash long enough (from the video) to consider it a bootloop
it's just a thought, but that's what it looks like to me
(if it were even going slightly further than the bootsplash, or even bootlooping back to bootloader, then it could be something else, it just looks to me as if the power button is constantly pressed)
nkk71 said:
1) battery drains, he plugs it in -> boom, it turns on
2) it reboots no matter what button combo he tries
3) it's not even staying on the bootsplash long enough (from the video) to consider it a bootloop
it's just a thought, but that's what it looks like to me
(if it were even going slightly further than the bootsplash, or even bootlooping back to bootloader, then it could be something else, it just looks to me as if the power button is constantly pressed)
Click to expand...
Click to collapse
@KomuroXV and @nkk71 I mistreated my phone and yeah, seems to have about the same time to reboot.
And yeah, I now saw in the first video he didn't first hold down the power button. So your thesis is very probable.
So yeah only way is to try and get the button unstuck and if this doesn't work I'd return it to the manufacturer. Shouldn't be something you have to pay for. Only bad thing is that if they notice the altered motherboard...
LibertyMarine said:
@KomuroXV and @nkk71 I mistreated my phone and yeah, seems to have about the same time to reboot.
And yeah, I now saw in the first video he didn't first hold down the power button. So your thesis is very probable.
So yeah only way is to try and get the button unstuck and if this doesn't work I'd return it to the manufacturer. Shouldn't be something you have to pay for. Only bad thing is that if they notice the altered motherboard...
Click to expand...
Click to collapse
For a second there I thought it could be this, but it looks like it's not.
I nudged it.
Carefully cleaned with the edge of a paper too.
God, I basically gave a blowjob to that power button just in case there was any dust inside of it.
But it looks like there's not anything.
It was a good theory though.
But still it wouldn't explain, why did it happen just after I interrupted the custom recovery flashing?
Let explain again in case I didn't do it clearly last time.
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
Doesn't really look like a hardware problem.
Seriously, it's the most well taken care phone I've ever had.
I bought it a tempered glass screen protector, an UAG case which for me made the phone indestructible.
Still, guess it wasn't silly-owner-proof.
*facepalms*
:silly:
KomuroXV said:
For a second there I thought it could be this, but it looks like it's not.
I nudged it.
Carefully cleaned with the edge of a paper too.
God, I basically gave a blowjob to that power button just in case there was any dust inside of it.
But it looks like there's not anything.
It was a good theory though.
But still it wouldn't explain, why did it happen just after I interrupted the custom recovery flashing?
Let explain again in case I didn't do it clearly last time.
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
Doesn't really look like a hardware problem.
Seriously, it's the most well taken care phone I've ever had.
I bought it a tempered glass screen protector, an UAG case which for me made the phone indestructible.
Still, guess it wasn't silly-owner-proof.
*facepalms*
:silly:
Click to expand...
Click to collapse
I'm gonna sleep now, will answer tomorrow evening. I have an important meeting tomorrow.
KomuroXV said:
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
Click to expand...
Click to collapse
i dont see how flashing / interrupting flashing a recovery could cause that, the recovery is in a different partition than bootloader, so even if you were unable to enter recovery (due to bad flash), you should be able to get to bootloader
but when you say it got stock at 40%, i'm seriously surprised, as flashing a recovery literally takes 2 seconds:
Code:
C:\ADB3>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1514139648 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.209s]
writing 'recovery'...
OKAY [ 1.144s]
finished. total time: 2.354s
maybe try covering the light sensors completely, and hold voldown, when it reboots again.... maybe (though i doubt it), it will forego the simulated battery pull
KomuroXV said:
[...]
I flashed a Custom Recovery through fastboot.
I was Unlocked, S-Off, Rooted, everything good.
All went smoothly at CMD screen.
But the process in the phone was being slow and it looked like if it was stuck to me.
Which it wasn't I guess... but I panicked and turned off the phone like at 40% of the install.
Then all this happened.
That broken power button thing would be way too much coincidence.
My theory is that since I was flashing Custom Recovery through fastboot (bootloader) and I interrupted it.
Now, every time it turns on, it tries to log into fastboot and continue the process I stopped.
Just that now.... it doesn't has the files needed to complete it, or maybe just got corrupted.
Since it can't finish that ghost recovery flashing process, it gives error and reboots.... and reboots... and reboots...
[...]
Click to expand...
Click to collapse
How did you turn it off? Did you press the power button very hard/strong?
Did you flash the recovery with fastboot
or did you flash your recovery within rebootRUU and with an firmware.zip ?
Because the method via fastboot (fastboot flash recovery recovery.img) doesn't indicate a percentage. And btw. I had issues with this method too and interrupted the installation several times, didn't cause any problems. To the theory that your phone wants to continue flashing recovery is not true. This isn't possible since your phone should boot correctly and if it wanted to boot into recovery you could prevent that with pressing the vol. down button. That didn't work in your case so I think that this theory doesn't work out.
If you flashed it with a firmware zip, was there another hboot.img that you installed too without knowing/wanting? Because interrupting a hboot flash will brick your device. but if that happend you wouldn't be able to boot your phone. So I think this isn't true either.
i have exactly the same problem, is very strange beacause i was updating my ROM

Switched to Dalvik from ART on Moto G 2014 and now phone will not power on.

Got a Moto G 2014 from WIND Mobile last week. Allowed updates to go through, finished at 4.4.4. Switched to ART assuming it would improve performance. It did not, and I had an issue where every time I boot up it would optimize every app. This made bootup take about 10 minutes. I decided to troubleshoot I would switch back to Dalvik. Began switch to Dalvik with 80% remaining battery. During the runtime switch, it booted up fine. I decided to power it off and then back on again and watch the bootup process as a test just to make sure everything was now fine.
Now, it doesn't respond when I try to power it on. No backlight, nothing on screen, no vibrate, nothing. Holding power and volume down does nothing. Holding power for 120 seconds (something I read online) does nothing.
I would appreciate any help I can get with this from anyone who has faced this issue.
Hold power and vol down to power up in bootloader mode and do a factory reset
danieliop said:
Hold power and vol down to power up in bootloader mode and do a factory reset
Click to expand...
Click to collapse
Holding power and volume down does not respond either. I've tried holding both down for as long as 120 seconds and no luck.
Oh, damn. Plugging the USB does something?
danieliop said:
Oh, damn. Plugging the USB does something?
Click to expand...
Click to collapse
Plugging into USB also has no response. It used to vibrate and display a battery status screen immediately after being plugged in. But now, I plug it in and nothing at all.
matt0401 said:
Plugging into USB also has no response. It used to vibrate and display a battery status screen immediately after being plugged in. But now, I plug it in and nothing at all.
Click to expand...
Click to collapse
That's really weird. Try to get it replaced, as it seems to be dead.
matt0401 said:
Plugging into USB also has no response. It used to vibrate and display a battery status screen immediately after being plugged in. But now, I plug it in and nothing at all.
Click to expand...
Click to collapse
Yeah that's my next step. Doesn't give me a lot of confidence in this phone. I think anyone planning on trying ART before the Android 5.0 update should beware. Make sure they've backed up their important data and are able to return their phone for replacement, because what triggered this bricking for me was switching back from ART to Dalvik. I made no changes to the bootloader, ROM, etc. This was completely stock.
Thanks for replying!
Re-Flash!
matt0401 said:
Got a Moto G 2014 from WIND Mobile last week. Allowed updates to go through, finished at 4.4.4. Switched to ART assuming it would improve performance. It did not, and I had an issue where every time I boot up it would optimize every app. This made bootup take about 10 minutes. I decided to troubleshoot I would switch back to Dalvik. Began switch to Dalvik with 80% remaining battery. During the runtime switch, it booted up fine. I decided to power it off and then back on again and watch the bootup process as a test just to make sure everything was now fine.
Now, it doesn't respond when I try to power it on. No backlight, nothing on screen, no vibrate, nothing. Holding power and volume down does nothing. Holding power for 120 seconds (something I read online) does nothing.
I would appreciate any help I can get with this from anyone who has faced this issue.
Click to expand...
Click to collapse
I believe you're gonna have to re-flash your device. Are you able to enter the boot loader? if yes, then re-flash the device with Stock firmware using ADB. Search the forums for instructions or reply and I'll post them myself. Do post your Device Model also.
KrishnaSagar said:
I believe you're gonna have to re-flash your device. Are you able to enter the boot loader? if yes, then re-flash the device with Stock firmware using ADB. Search the forums for instructions or reply and I'll post them myself. Do post your Device Model also.
Click to expand...
Click to collapse
It's actually already completely stock. I made no changes to it, besides enabling developer options and changing the runtime to ART (and then back to Dalvik). Model number is XT1064.
matt0401 said:
It's actually already completely stock. I made no changes to it.
Click to expand...
Click to collapse
I know, but since it ain't booting up, you have to re-flash the stock firmware.
KrishnaSagar said:
I know, but since it ain't booting up, you have to re-flash the stock firmware.
Click to expand...
Click to collapse
Sorry about the confusion, that does make sense. By accessing the boot loader, are you referring to the menu you reach when you hold power and volume down as you power on the phone? If not, what do you mean by accessing the boot loader?
Yep
matt0401 said:
Sorry about the confusion, that does make sense. By accessing the boot loader, are you referring to the menu you reach when you hold power and volume down as you power on the phone? If not, what do you mean by accessing the boot loader?
Click to expand...
Click to collapse
Yes. Thats the boot loader menu.
KrishnaSagar said:
Yes. Thats the boot loader menu.
Click to expand...
Click to collapse
Okay. So I have no access to that at all. Power and volume down doesn't do anything. Windows seems to recognize it somehow, I hear the device-plugged-in sound, but the device manager doesn't seem to show it listed. I'm guessing I don't have any options left for fixing this, so I'm going to bring it back and see if I can get it replaced on the spot or begin an RMA process.
Try this! All credit goes to Falcon G
matt0401 said:
Okay. So I have no access to that at all. Power and volume down doesn't do anything. Windows seems to recognize it somehow, I hear the device-plugged-in sound, but the device manager doesn't seem to show it listed. I'm guessing I don't have any options left for fixing this, so I'm going to bring it back and see if I can get it replaced on the spot or begin an RMA process.
Click to expand...
Click to collapse
This may just be your lucky day! Falcon G has posted a guide on how to unbrick Hard Bricked devices.
Follow this guide: http://forum.xda-developers.com/mot...rick-hard-bricked-moto-g-2nd-gen-5-0-t2966010
Cheerio!!
First connect your charger to phone and leave it for 2-3 hr may be your battery is dead. Same thing happen to a member of my whatsapp group now his phone is perfect
KrishnaSagar said:
This may just be your lucky day! Falcon G has posted a guide on how to unbrick Hard Bricked devices.
Follow this guide: http://forum.xda-developers.com/mot...rick-hard-bricked-moto-g-2nd-gen-5-0-t2966010
Cheerio!!
Click to expand...
Click to collapse
vikasb32 said:
First connect your charger to phone and leave it for 2-3 hr may be your battery is dead. Same thing happen to a member of my whatsapp group now his phone is perfect
Click to expand...
Click to collapse
For anyone interested in some followup, I went to WIND to see if it could be replaced. They refused to replace it, because there were a few scuff marks around the edge from when I dropped it the night I got it. I went home and called Motorola tech support to look into an RMA. They had me go through the troubleshooting steps. This involved me plugging it back into the charger (now it's been unplugged from my charger all day because I brought it with me for returning). Looks like leaving it unplugged for a while to let the battery discharge did the trick. This time, when I plugged it into the charger, the white LED came on, and I got the white screen with the battery indicator. It was fine.
Here's hoping I don't run into that again.

Android 11/R Beta Bricked my P4XL today

If anyone knows how to fix this please help. I'm researching it now but I'm making this thread in hopes someone knows what I need to do.
I can boot the device and it gets to the lock screen and I can unlock it but then it keeps turning the screen off and going back to the lock screen. If I don't touch it it will continue to do this in a loop. If I press the power button it will turn the screen off and stay off. If I unlock the former process repeats and I can't do anything. I can restart the phone, or power it off. When I go to fastboot mode I can't find anywhere to factory reset it. I try to enter rescue or recovery mode and it justs boots to a screen with a dead android and says "no command".
I'm assuming I'm going to have to use adb to fix it. I've done this with phones in the past but I know nothing about the P4XL and haven't messed with my phones in a geeky manner in quite a while so my knowledge is rusty.
PS. The android 11 beta ran fine for a few days besides some normal bugs. All in all it worked fine. This problem randomly happened today while I was using soundcloud hooked to my JBL boombox.
Evidently I'm the only person in the world who has a bricked Pixel 4 XL with android 11 because I'm not finding any info on how to fix it. I'm not even finding anyone with the same problem.
imucarmen said:
If anyone knows how to fix this please help. I'm researching it now but I'm making this thread in hopes someone knows what I need to do.
I can boot the device and it gets to the lock screen and I can unlock it but then it keeps turning the screen off and going back to the lock screen. If I don't touch it it will continue to do this in a loop. If I press the power button it will turn the screen off and stay off. If I unlock the former process repeats and I can't do anything. I can restart the phone, or power it off. When I go to fastboot mode I can't find anywhere to factory reset it. I try to enter rescue or recovery mode and it justs boots to a screen with a dead android and says "no command".
I'm assuming I'm going to have to use adb to fix it. I've done this with phones in the past but I know nothing about the P4XL and haven't messed with my phones in a geeky manner in quite a while so my knowledge is rusty.
PS. The android 11 beta ran fine for a few days besides some normal bugs. All in all it worked fine. This problem randomly happened today while I was using soundcloud hooked to my JBL boombox.
Click to expand...
Click to collapse
When you are in the phase with the dead android and the "no command" hold the power button and just click the volume up button so you can go to the advanced recovery menu and from there hard reset your phone or install via adb an other rom.
Cheers.
Escribis said:
When you are in the phase with the dead android and the "no command" hold the power button and just click the volume up button so you can go to the advanced recovery menu and from there hard reset your phone or install via adb an other rom.
Cheers.
Click to expand...
Click to collapse
Thanks! Worked! I found a tutorial on verizon's site saying to do what you just explained but it was saying to release both the power and volume up and when I did that, nothing would happen. Your instructions worked flawlessly. Thank you!
imucarmen said:
Thanks! Worked! I found a tutorial on verizon's site saying to do what you just explained but it was saying to release both the power and volume up and when I did that, nothing would happen. Your instructions worked flawlessly. Thank you!
Click to expand...
Click to collapse
You are welcome.
Happy that your problem is solved.
?
I had the same issue and it persisted until I gave up and got a replacement through my phone carrier via insurance. You may be out of luck my friend...
EtherealJoey said:
I had the same issue and it persisted until I gave up and got a replacement through my phone carrier via insurance. You may be out of luck my friend...
Click to expand...
Click to collapse
You shouldn't root or be installing beta software on your phone if you filed an insurance claim over a soft brick.

Categories

Resources