Database Users

My phone doesn't power off! please help

Hi all! I've been having a problem since some weeks ago. I flashed ICS ROM IceColdSandwich on my Desire HD, and after that, if I tried to power off my phone, instead it reboots to recovery. Even worse, if I remove the battery, when I connect it again, the phone automatically boots to recovery itself!! That was weird, so I reflashed the ROM. Same problem... So I did a full wipe, leaving nothing on the phone. I remove the battery with the phone wiped, connect it again, and... the recovery again!! even with no ROM installed...
What could it be? I'm so angry with my phone right now... Please, I need help! Thank you guys and gals!

try flashing boot.img file again
find boot.img in your zipped rom file
extract it to same place with your fastboot.exe
enter fastboot mode not recovery while usb cable plugged in
type in command prompt,
fastboot flash boot boot.img
reboot and try again

Thank you so much! That solved the problem instantly!

humm... After one day of the issue solved, I turned off the phone and the same thing happened... What can be causing the problem to go back?

requeiperrechon said:
humm... After one day of the issue solved, I turned off the phone and the same thing happened... What can be causing the problem to go back?
Click to expand...
Click to collapse
Flash new recovery.
I'd also suggest pulling the battery for much longer to see what happens once it's fully drained of all power.

Blinking Red Light - I Might Be Different

Hey guys, I know this is the 1000th time you've seen this thread. However, I might be a little different.
I've read all the red blinking threads before posting this one.
ROM: CM10 Stable Snapshot
Kernel: Franco r53
Okay, yesterday as I was downloading and I opened a game, my phone screen just turned off completely. I'm assuming it was due to overheating as the phone was getting pretty hot.
So I assumed it died, no big deal. I tried to boot up using power button, no luck.
Then I panicked and started searching XDA for all these red blinking LED of doom threads.
I managed to get the phone to boot up to the Google screen by having it on a wall charger + hold the power button for 10 seconds. But then it just shuts down. I managed to make it stick with bootloader, but only on the wall charger, which isn't much help. On a USB connection with my computer, I'm not able to even open boot loader as it would just open and turn off the phone within a few seconds.
Threw it on the charger over night, no luck.
This morning, nothing has changed.
So what's weird about my situation is, I can get it into fast boot, but only when it's on a wall charger, nothing else. And getting it to Google logo for a few seconds.
Edit: I can't RMA, because when it boots to Google logo, it says bootloader is unlocked (the little icon). And I also bought the phone off Swappa, so it's not attached to my account (is it even possible to claim warranty?)

Interesting this sounds like a hardware problem all right. Simply because you said it works on the mains charger which has an output of 1.2a were as the USB to PC chargers phone at rate of 400ma. I would try getting a replacement if you can. Also are you able to boot into recovery through boot loader if so you could try wiping everything or restoring from back up.

Okay, something weird. I tried a different method of getting into fastboot, and it worked (connected to PC).
Hold volume - (DOWN) by itself WHILE plugging in the USB cable. And now I'm in fastboot. Now I'm just trying to find a way to erase cache via toolkit x)
Edit: Weird, toolkit picks up the ADB device but manual adb doesn't using adb devices command.

I've read another user who fixed this by removing the back, then disconnecting and reconnecting the battery connector. Sorry I can't find the post but I'm sure it was in one of the I bricked my phone threads.

Yeah, I saw that, too. But I don't have the equipments for it, unfortunately

ADB won't recognize my nexus 4.
Toolkit will (so I know that toolkit is installed properly). I tried opening a command prompt through toolkit and I couldn't run anything.
Any suggestions?

draikz said:
ADB won't recognize my nexus 4.
Toolkit will (so I know that toolkit is installed properly). I tried opening a command prompt through toolkit and I couldn't run anything.
Any suggestions?
Click to expand...
Click to collapse
Adb won't work from bootloader, you should have fastboot access though

I'm in fastboot now.
I cannot get into recovery =[ When I select recovery, it would just turn off the phone and the blinking lights begins again.

Try charging overnight with other charger, not stock
Sent from my Nexus 4 using xda premium

Just tried with a nonstock charger. It blinked red. Then the battery charging screen popped up (first time ever). And now it's dead blinking red again.
Hopefully I'll see results overnight.

draikz said:
Just tried with a nonstock charger. It blinked red. Then the battery charging screen popped up (first time ever). And now it's dead blinking red again.
Hopefully I'll see results overnight.
Click to expand...
Click to collapse
That's a good sign! Sounds like it was in some serious deep hibernation! The fact that the battery icon popped up shows u didn't brick it or anything, its just really really dead! However when I had my problem, I had just a red light on all the time, it never blinked
Sent from my Google Nexus 4

Mine is constantly blinking. :'(
And it's probably not dead because I did manage to get it into fastboot. And I got adb to pick up using fast boot.
Every after reflashing recovery, I can't get into anything other than fastboot. When I try to select "Recovery" from the fastboot menu, it just turns off and continues to blink ;[

if you can get it into fastboot while plugged in your pc, scroll down in fastboot to the "power off" option. leave it there to charge up for a bit. you can check if its charging by using adb
Code:
adb shell cat /sys/class/power_supply/battery/capacity
hopefully it comes back to life after you charge it a bit. After it charges I would flash stock images just to be safe.

rayford85 said:
if you can get it into fastboot while plugged in your pc, scroll down in fastboot to the "power off" option. leave it there to charge up for a bit. you can check if its charging by using adb
Code:
adb shell cat /sys/class/power_supply/battery/capacity
hopefully it comes back to life after you charge it a bit. After it charges I would flash stock images just to be safe.
Click to expand...
Click to collapse
Okay, trying that now. It's been on the charger all night.
How does one ADB with the phone "powered off"?

So if the phone died because of heat, didn't it throttle properly? How is this possible?

Why don't you reflash stock images through fast boot? I don't understand why the need to be in recovery?
Sent from my Nexus 4 using Tapatalk 2

Lownita said:
So if the phone died because of heat, didn't it throttle properly? How is this possible?
Click to expand...
Click to collapse
I'm not really sure. I'm just assuming that it died from heat.
joshnichols189 said:
Why don't you reflash stock images through fast boot? I don't understand why the need to be in recovery?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I thought I had to factory reset it first inorder to flash factory image? (Coming from CM and Franco) At least that's how I always done it or it'd get stuck in a boot loop on my old phone.
But it is my last resort as well, because I have some precious data on this phone x)
Oh and Google pulled factory images, do you knows know where I can get a copy of one?

draikz said:
I'm not really sure. I'm just assuming that it died from heat.
I thought I had to factory reset it first inorder to flash factory image? (Coming from CM and Franco) At least that's how I always done it or it'd get stuck in a boot loop on my old phone.
But it is my last resort as well, because I have some precious data on this phone x)
Oh and Google pulled factory images, do you knows know where I can get a copy of one?
Click to expand...
Click to collapse
Mskip tool kit has images. There might be a thread in general section with them
Sent from my Nexus 4 using xda premium

rayford85 said:
Mskip tool kit has images. There might be a thread in general section with them
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I've not flashed stock before for this phone. And I'm afraid it might be different.
So question noob question.... Do I flash the booterloader and radios too? I've read that it's pretty dangerous to flash those.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Any instructions I should do differently?
EDIT: I just flashed stock, nothing happened. Still could only get to fastboot. I am now losing hope.

draikz said:
I've not flashed stock before for this phone. And I'm afraid it might be different.
So question noob question.... Do I flash the booterloader and radios too? I've read that it's pretty dangerous to flash those.
I'm following this guide: http://forum.xda-developers.com/showthread.php?t=2010312
Any instructions I should do differently?
EDIT: I just flashed stock, nothing happened. Still could only get to fastboot. I am now losing hope.
Click to expand...
Click to collapse
IF ur going to rma it don't forget to lock the bootloader :angel:

Help! N4 in endless boot loop.

I have a Nexus 4 with the latest OTA (LMY48T) that suddenly shut down one waking morning. It couldn't boot, couldn't charge, was unresponsive. Until I tried the "Power button + Vol down for 15 sec and then plug the charger" trick. I was able to bring it to charge powered off, and I thought that was that. After an hour or so, I got a bit impatient and tried turning the phone on while charging. It booted, but only until the boot animation, and then it stopped and shut down on its own. On the off chance that I was able to boot it again, it resulted in a boot loop: boots until the boot animation, stops, restarts. At this point the phone was bootloader locked, unrooted, stock everything.
Right now, I am able to occasionally access fastboot and recovery (its behavior is no longer consistent; I have to do the charging trick mentioned above quite a few times [it now fails on occasion] before I can make the phone enter fastboot). Through fastboot, I have been able to flash different builds: 4.2.2 (JDQ39), 4.4.4 (KTU84P), 5.1.1 (LMY48M), 5.1.1 (LMY48T). But all of them resulted in the same boot loop pattern. The phone boot loops until its battery drains. Yes, I've tried clearing the cache and factory resets after flashing but to no avail. Any idea what's happening? Is this a hardware issue?
I can't make it enter HS-USB QDLoader mode through the PC, hence I can't use the LG BoardDiag method. I also wanted to use the LGNPST method, but all the links for the resources I've found are now dead. Help!
Here are some videos of the boot loop:
https://youtu.be/NclrpF10OQQ
https://youtu.be/GIjONXSx8qU

Up

breakfastdude said:
Up
Click to expand...
Click to collapse
Do you mean the issue is resolved? :fingers-crossed:
If yes, how? May be some one else facing similar issue will be benefited :laugh:

nitin.chobhe said:
Do you mean the issue is resolved? :fingers-crossed:
If yes, how? May be some one else facing similar issue will be benefited :laugh:
Click to expand...
Click to collapse
Nope. Unfortunately still waiting for help here.

breakfastdude said:
Nope. Unfortunately still waiting for help here.
Click to expand...
Click to collapse
When you say that you flashed different builds (KK, LP), it means you are flashing the factory images by wiping everything, right?
I would have tried to flash TWRP and then would have tried to flash any MM ROM. See if that helps

ALE L-21 dropped into water, can't get to recovery mode

Hello everyone!
First of all - this is my first post here, so if I'm doing something wrong, please, correct me.
Three days ago i dropped my ALE-L21 into water closet (don't ask). I dismantled it and put into rice for 2 days. Today I decided to check if phone will start normally, but there is a following problem:
The phone is stuck into bootloop - after turning it on I see only the brand logo and after every 1 minute it vibrates for a while, the screen goes black and the brand logo appears once again. I tried to get it into recovery mode, but nothing happens. (none of button combination: holding power, power+volup or power+volup+voldown works. The phone always try to reboot)
I plugged it to PC and the only thing I can do is to get into fastboot (bootloader unlocked, phone rooted, but USB debugging is off, so adb doesn't see the device).
Any ideas of how can I fix that? Maybe just volume button is broken? Should I try to clean volume&power flex? Maybe there is an alternative solution to turn usb debugging mode on? Then I could try to recover it manually, with adb.

Flash the correct firmware in fastboot.

Szabi01 said:
Flash the correct firmware in fastboot.
Click to expand...
Click to collapse
How can I do that?
I can run fastboot by power+vol_down, but probably USB-debugging is turned OFF. ADB doesn't see any devices plugged in.

turbotramp said:
How can I do that?
I can run fastboot by power+vol_down, but probably USB-debugging is turned OFF. ADB doesn't see any devices plugged in.
Click to expand...
Click to collapse
If you pc doesn't recognize phone with adb or fastboot commands in fastboot you propably have some broken hardware.
But you can try this stuff if it recognize something.
Go to fastboot and flash TWRP with "fastboot flash recovery (recovery_filename_here).img" then try power + vol up, if it doesn't work you can try to extract UPDATE.APP app and flash system.img, boot.img, cust.img in fastboot. If TWRP works use this to re-install stock firmware https://forum.xda-developers.com/honor-4x/how-to/install-emui-4-1-4x-4c-g-play-g-play-t3515702.

Ok. Fastboot recognized my device, so I installed everything what you mentioned. Everything went 'OKAY', as it printed in cmd, but still there is no change. Whatever I am doing it freezes at brand logo and after some time reboots.
But I used branded ROM, which I downloaded from huawei website - it is the only one that not gives me "balong" error.
Any ideas before I give back my Huawei to the official service? Maybe there is some way to diagnose volume_up button?

edl mode; cannot receive hello packet

Mi A1 bricked, hard resetted it by opening the back cover and shorting two points.
It gets detected by mi flash tool but I cannot flash the stock room. It is giving me "cannot receive hello packet" and then it times out.
Any help will be appreciated.
Thank you.

I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?

foggs said:
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
Click to expand...
Click to collapse
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.

udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.

foggs said:
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
Click to expand...
Click to collapse
Yup, I ruined one of my usb-C cable trying do do deep flash that way. I failed, so I went to one repair shop and open up the device and did the "two point short thing", which helped to be recognized by the flash tool. Then it showed me that "hello packet" thing.
Then I dug around the Internet for couple of hours and changed the USB port on laptop. I also restarted the laptop after I reinstalled the drivers. Then it actually flashed that ROM I mentioned above. But just that ROM. I tried the latest to oldest versions and all of those ROM would flash but then they will brick the phone again. Only that one worked, i.e. helped me to get to bootloader. But alas it is stuck there, no matter how many times I clean flashed it, it is refusing to boot to system. It gives me "Your SYSTEM HAS BEEN DESTROYED" message on every boot. It only goes to bootloader if I press Volume Up + Power button while booting. And it's a dead end for now. I don't know what else to do.
Also this phone was bought in Hong Kong and its warranty won't work where I am right now. I already took it to the authorized service center and those lazy people told me to change the motherboard and it will cost around $180. So I took it back. lol

Disable driver enforcment to get the hello packet.

TrueMS said:
Disable driver enforcment to get the hello packet.
Click to expand...
Click to collapse
still no hello packet

Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package

emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
:victory: Held the power button, clicked flash.. Success :good: it's in the process of flashing now. Thank you
Edit: successful flash now to just let it charge up. Thanks again guys for the help/suggestions ?

Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?

foggs said:
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
Click to expand...
Click to collapse
Ur presist partition is damaged..thr are many guides here about recovering it

Do the "factory flash" mode in MiFlash under EDL mode as a last resort. May wipe your IMEI and MAC's, not sure.
Could not receive magic packet is solved by using USB2 port, Windows 7 x86 (32-bit) in a VM, or power-cycling the device and starting over, any or all of the above.
Deep flash cable is only for kicking the phone out of diagnostic mode and into QDFlash mode. Not necessary if using test point. I had to use testpoint method myself, couldn't get deepflash cable to work for getting out of diagnostic mode. I hope I can get it working next time though when I inevitably brick it from repartitioning; as I broke my screen when disassembling

apexashwin said:
Ur presist partition is damaged..thr are many guides here about recovering it
Click to expand...
Click to collapse
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?

foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Did you find the guide about fixing constant reboot? It's around somewhere, might be on MIUI forum.

foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Please try presist resurrector from guides section

I think i've got it back to life.
first tried to flash 7.1.2 stock the earliest one (tissot_images_7.8.23_7.1), it hung on flashing it for nearly an hour with no success, closed the miflash application then tried another 7.1.2 (tissot_images_7.10.30_7.1)flash successful, then in stalled twrp did the persist command and reboot nearly got to the home screen just never getting over the line. then i flashed January 8.0 oreo (tissot_images_8.1.10_8.0) and was able to get on to the home screen/go into settings/enable developer options but it would eventually reboot itself, went back into twrp and did the persist command again and reboot.. success (fingers crossed) now downloading/applying April security update as i type this.
Boo installation problem with the update
looks like i lost my imei, https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190 this is going to be a pain.. i'll post back when i try this. need a break from this mess ive made lol
thanks for the help/suggestions appreciated big time.
edit: up to the latest update April 1 security patch.
all done, down to 7.8.23 rom, did the stuff to get the imei back then flashed latest oreo rom

emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
Man, I was trying to fix my Redmi Note 4X for the past 6 hours and you were the ONLY guy to talk about this. Thank you so much. :victory:

THANK YOU
udaan said:
it was solved after i changed the usb port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then twrp. But after flashing aosp extended rom it gave me "the system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
man you just solved my problem and saved for me like 180 eur thank you you are a god !!!! Thanks for using this site !!!!!!!!!! <3 <3 <3

udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I was unable to flash on MiFlash and after changing USB port I managed to do it!.
Many thanks!

emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
I love you!