Related
Okay I was using odin one click it was at rebooting device after it completed pushing stock onto the phone thats when I discounted the usb.... should have waited two secs I know but now the phone doesn't seem to get past the att world phone screen keeps looping over and over I have tried all the key combos different times and ways, vol up and down being held doesn't get to download mode the screen remains black plunging in seems to get to charge mode where even plunging into the wall charger it loops trying to calculate the battery status... any method I haven't tried... I did get it to boot once full and was usable didn't think to redo odin at the time and restarted back to this mess...tried three different jigs using the 100k 5% X3 even through its not a full brick due to the button combos gotten no where. Please Help
Search the forum to build a jig in order to get into download mode. Or you may need to buy one just in case in the future.
http://cgi.ebay.com/ws/eBayISAPI.dl...69977&ssPageName=STRK:MESELX:IT#ht_623wt_1139
Try this:
Open Odin and plug your cable into your computer but not your phone yet
Pull battery on phone and put it back in
Hold both volume buttons down and then plug your phone in
It should go into download made and you can reflash the stock ROM
Can anyone please help, i have the exact same problem. No matter how i try to enter download mode, it just gives me a charging sign and when i start my phone, it goes into an infinite boot loop.
Try this:
1. Remove battery from phone, SIM card and MicroSD card (if you have one)
2. Wait AT LEAST 10 seconds with your phone in this state
3. Hold Volume Up/Down, don't let go
4. While holding the volume keys, insert the battery
If this worked, you should be in Download Mode almost instantly.
There are a lot of key combos for Download Mode, this is just one of them. If all the button combos don't work, you need to build/buy a JIG to force your phone into Download Mode.
norcal einstein said:
Try this:
1. Remove battery from phone, SIM card and MicroSD card (if you have one)
2. Wait AT LEAST 10 seconds with your phone in this state
3. Hold Volume Up/Down, don't let go
4. While holding the volume keys, insert the battery
If this worked, you should be in Download Mode almost instantly.
There are a lot of key combos for Download Mode, this is just one of them. If all the button combos don't work, you need to build/buy a JIG to force your phone into Download Mode.
Click to expand...
Click to collapse
Ahah Thats the same exact steps I was able to get the phone to boot that one time instead of the up down I was still attempting it to get past the loop holding the power button instead using those steps, if I had know it would have been one of the only times I would see it in there I would have pushed it to download with adb though...
can't test getting it to download mode now took it back fit the description of the standing on/off issue with the device still honored by warranty. And I wouldn't have posted without searching everywhere to make a jig, I made three of them though I noticed it still didn't get to download mode. I made sure that the last two jigs were done correct. Think that when it was disconnected from odin it wasn't done finalizing after the stock push gah >,< live and learn and do something else to the cappies XD.
Thanks for the link placing an order just in-case ~whistles looking around then side to side pushes another rom~ lalala
To offer my own advice if it ever happens again, what I've been able to do is:
1. Pull the battery out
2. Put it back in
3. Open Odin
4. Hold Both Volume Buttons (without holding the power button)
5. Plug the phone back in
It went immediately into download mode for me, Odin managed to time out several times while I was trying to flash a co-worker's Captivate to the official Froyo leak. One of those times I couldn't even get the phone to come up with any screen. I really do think this thing cannot be bricked.
BeowulfShaeffer said:
That has been my experience so far, too. I've "bricked" twice, once with an "all black" screen, and once with the phone-!-computer screen. I've yet to need a jig, though I thought I may have needed it last night when I got the "all black" screen.
Keep trying the different button press methods to get into download mode. It took me 4 attempts to get from "all black" to "phone-!-computer" to a happy robot digging away.
Click to expand...
Click to collapse
if you are out of luck, you may have to build a jig or buy one online.
http://cgi.ebay.com/ws/eBayISAPI.dl...69977&ssPageName=STRK:MESELX:IT#ht_623wt_1139
Ive used odin before changing roms and have gotten to download mode with combos on my last cappy before that night (dramatic music) en ways..
did some more digging on this bad ass info and learning community "XDA" hehe as to how it got the way it did, I found out I was updated with the new patch when I sent it for screen change to this shop, so...using odin one click with this creates a hang time to where it looked like it was finished after pushing jh6 (which was totally off should have used odin 3 and pushed jh2 then clockwork update to jh7) so thats when I disconnected (second noob mistake of the situation) basically blowing the finalization out and key combs for recovery and download mode. and im guessing the jig was made wrong too at this point >,<.
Oh
wmason92 said:
Can anyone please help, i have the exact same problem. No matter how i try to enter download mode, it just gives me a charging sign and when i start my phone, it goes into an infinite boot loop.
Click to expand...
Click to collapse
If you cant get your jig to work take it in to warranty (if your water inicators are sound and no physical damage) and say its power cycling on off at random times (which is true.. ) and it did it when you were sync to mini kies, did it an hour after the OP heh good luck
and I have yet to see the infamous yellow pc sign >,> <,< it can stay on the yellow brick road... thanks for the responses btw
Well the same thing happened to me and i got stuck with in an unlimited boot animation. Ive trying everything key combo possible and ive tried a jig but it just makes it reboot, and yes im sure im touching the right pins. If anybody can help with this dilemma i would really appreciate it. I want to return with warranty but my phone has a custom boot animation so im sure att probably wont accept it if they notice it.
wmason92 said:
Well the same thing happened to me and i got stuck with in an unlimited boot animation. Ive trying everything key combo possible and ive tried a jig but it just makes it reboot, and yes im sure im touching the right pins. If anybody can help with this dilemma i would really appreciate it. I want to return with warranty but my phone has a custom boot animation so im sure att probably wont accept it if they notice it.
Click to expand...
Click to collapse
Purchase jig from ebay, or google and try igo jig.
If your phone is turning on with jig you are not touching the right prongs. I know, I know it is not easy, but unless it if touching just right, it can turn your phone on.
Holy ******** i got it to download mode! For some reason i kept touching the same pins and nothing would happen. After about readjusting for about 5mn it finally worked!!!!
It has to be just so. Happy to hear
Wait, now its in download mode but my computer keeps saying usb device not recognized.
wmason92 said:
Wait, now its in download mode but my computer keeps saying usb device not recognized.
Click to expand...
Click to collapse
That happens try a different usb port or just borrow someone else computer, I used my networking classes computer my laptop was doing the same thing when I was change roms.
Changed the title to fit the issue, this is not a soft brick this is a boot brick that can affect the charge indicator in power off state as well. So whats the difference the soft brick is when you flash a rom incorrectly and you get the att world screen constantly staying on, the key combinations still work when the phone is like this.. in the case with a boot brick the att screen cycles over and over and the jig may or may not work I haven't been able to fully test it here in this state I have seen a packager attempt to finish once on the recent one but all the key combos I could find didn't function my noob guess is the phone forgot how to ride a bike (meaning is hasn't connected keys to recovery that was being flashed or hardware to there states without being booted normally) ultimate fix is if its in warranty (meaning no physical damage or water) take it back for power on off. the soft brick i've seen before and have fixed with odin 2-3 three times, and ive seen a blown kernel type too where keys and odin fix up like new.
wmason92 said:
Well the same thing happened to me and i got stuck with in an unlimited boot animation. Ive trying everything key combo possible and ive tried a jig but it just makes it reboot, and yes im sure im touching the right pins. If anybody can help with this dilemma i would really appreciate it. I want to return with warranty but my phone has a custom boot animation so im sure att probably wont accept it if they notice it.
Click to expand...
Click to collapse
I have the same thing happening to me. Att boot screen, then it loops on the ROM logo, over and over. I get 1 vibrate then 2 following also. I purchased a Jig on ebay but it just keeps rebooting the phone, doesn't get it into download mode.
glaze76 said:
I purchased a Jig on ebay but it just keeps rebooting the phone, doesn't get it into download mode.
Click to expand...
Click to collapse
Very odd - I've never heard of that with a jig.
glaze76 said:
I have the same thing happening to me. Att boot screen, then it loops on the ROM logo, over and over. I get 1 vibrate then 2 following also. I purchased a Jig on ebay but it just keeps rebooting the phone, doesn't get it into download mode.
Click to expand...
Click to collapse
Have a link to which one you have? It sounds like the solder points on the jig were a little weak. This can happen if they aren't good welds. If you want give one of mine a shot. I'll refund you if it reboots your phone...
Buy one HERE...
I had a boot brick happen to me just the other day. I was running Andromeda 1.1 with stock kernel & modem, and tried to tinker with swapping the AT&T boot screen using connexion2005's video on the subject (NOT insinuating any blame at all, his videos are fantastic).
I tested it successfully the first time, then flashed back the i9000_param_lfs, and pushed a new image to the device again (everything was exactly the same, with the exception of the boot_screen.bat script not making the phone ask for superuser approval while pushing the new logo_ATNT), and everything looked ok.
Reboot device, and...boink.
Black screen, no image at all on power on, only charging screen when usb cable connected. ADB, nothing. 3 button, nothing. Vol up+down, remove battery, insert usb cable, do hokey pokey, nothing. 5 attempts at the 100k resistor jig, for hours, nothing. No download, no recovery. Seems like the phone was toast.
Strange how I had just done this successfully earlier in the day, to now having it completely hard brick this phone.
I ended up taking the phone back to a local warranty center, and they swapped it (1008) for a 1010 (gps works fantastic on this one, btw)...I just hope there's no bill coming if they find out it was rooted and flashed. *crosses fingers and uses any and all karma*
Any ideas what happened? Did I scramble this things boot loader? I've heard how hard it is to fully brick this phone, and looks like I succeeded. How lucky.
I'd just like to know what went wrong so when I (or anyone else) root and flash next time, the chances of this happening are reduced (or better understood).
Thanks
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
So, my husband had a Mi5 64GB phone, the bootloader is unlocked, xiaomi.eu latest stable multi-rom was on it.
A couple of weeks ago it went dead all of a sudden. There was no live in it at all. I could not put it on, it was not recognized it was not recognised by the pc (I never linked it to the pc, so I had to install adb and miflash), no fastboot, no bootloader, nothing at all.
When charging the phone stayed cool, there were no lights, no blinking lights, again nothing.
So, as it was still in the guarantee period, I send it to a technician and got it back working again, the latest xiaomi.eu development rom was installed by the technician.
In the meanwhile my husband bought a new phone, and, as I had dropped my Mi3, I could upgrade to his Mi5.
But, after cleaning up the phone, I had some problems. I flashed something with TWRP, which worked, it booted up to miui. Then I wanted to reboot and the phone just Now, only two weeks after the repair, the phone again drops dead, exactly the same as the previous time. So I decided not to send it to the technician, as it is in another country and I have to pay the sending cost and it obviously did not do much.
What I then did get off the backpart of the phone, unscrew the top part of the phone (yes, I now broke the seal, bye bye guarantee) and I did the test point method multiple times. I did it after 'charging' the whole night. Sadly, this does not work. The computer does not recognise the phone.
What I also tried was holding a number of key combinations down a couple minutes (volume up + volume down + power), (volume down + power) and (volume up + power). So, I am now out of ideas.
The phone seems really dead, but the technician also got it working again... so I know there has to be a way to solve the problem.
Does anyone have a good suggestion (except from giving up, take my lossed and bury the phone)?
Last time i had my phone completely dead like this i held fastboot combination for 5 minutes then fastboot mode came up. And then oressing twrp combination, twrp came up and the rest was fine laterwards. I had this issue 3 times till now. And solved it similarly
Sent from my MI 5 using Tapatalk
Thanks, I will try this. With or without the phone plugged into the charger?
Sent from my MI 2S using Tapatalk
Well, power + volume down for 5 minutes does not give me anything (not charging).
Well, I tried it again and now it did work! Thank you!!!!
Sent from my MI 2S using Tapatalk
So, what I gather now with bricked Mi5 with unlocked bootloader is the following.
If the Mi5 is dead (black screen, no way to get it on), no charging light even when charging, then:
a) If it is recognised by the PC with Qualcomm 9008 try to solve it with the test points method
b) If it is not recognised by the PC, try to hold the power button + volume (= fastboot mode) down for 5 minutes or so (perhaps a couple tries are needed) and then when the bunny is on the screen power button + volume up (= recovery mode) to solve it. What I did do was charge it for a while before trying this.
Snuffie007 said:
So, my husband had a Mi5 64GB phone, the bootloader is unlocked, xiaomi.eu latest stable multi-rom was on it.
A couple of weeks ago it went dead all of a sudden. There was no live in it at all. I could not put it on, it was not recognized it was not recognised by the pc (I never linked it to the pc, so I had to install adb and miflash), no fastboot, no bootloader, nothing at all.
When charging the phone stayed cool, there were no lights, no blinking lights, again nothing.
So, as it was still in the guarantee period, I send it to a technician and got it back working again, the latest xiaomi.eu development rom was installed by the technician.
In the meanwhile my husband bought a new phone, and, as I had dropped my Mi3, I could upgrade to his Mi5.
But, after cleaning up the phone, I had some problems. I flashed something with TWRP, which worked, it booted up to miui. Then I wanted to reboot and the phone just Now, only two weeks after the repair, the phone again drops dead, exactly the same as the previous time. So I decided not to send it to the technician, as it is in another country and I have to pay the sending cost and it obviously did not do much.
What I then did get off the backpart of the phone, unscrew the top part of the phone (yes, I now broke the seal, bye bye guarantee) and I did the test point method multiple times. I did it after 'charging' the whole night. Sadly, this does not work. The computer does not recognise the phone.
What I also tried was holding a number of key combinations down a couple minutes (volume up + volume down + power), (volume down + power) and (volume up + power). So, I am now out of ideas.
The phone seems really dead, but the technician also got it working again... so I know there has to be a way to solve the problem.
Does anyone have a good suggestion (except from giving up, take my lossed and bury the phone)?
Snuffie007 said:
So, what I gather now with bricked Mi5 with unlocked bootloader is the following.
If the Mi5 is dead (black screen, no way to get it on), no charging light even when charging, then:
a) If it is recognised by the PC with Qualcomm 9008 try to solve it with the test points method
b) If it is not recognised by the PC, try to hold the power button + volume (= fastboot mode) down for 5 minutes or so (perhaps a couple tries are needed) and then when the bunny is on the screen power button + volume up (= recovery mode) to solve it. What I did do was charge it for a while before trying this.
Click to expand...
Click to collapse
If you want qualcomm 9008 open correctly then u should have to disconnect battery strips form phone's board then perform test points with proper 9008 drivers then see the results.
Click to expand...
Click to collapse
Today I replaced my cracked Redmi 4X screen. The replacement consisted of a screen+digitizer+frame assembly (no messing with a heat gun to detach screen+digitizer from frame). I think it went fairly well, took my time and didn't force anything.
However, when testing the screen halfway through reassembly, it was stuck on the mi logo. I decided to complete the reassembly, thinking maybe it did a hardware test and refused to boot as i hadn't reconnected all parts. No such luck, even when i use the old screen it doesn't boot .
The charging led also doesn't come on when attached to a charger or laptop usb port, which seems weird. I think the battery is about 50% but right now i can't even turn it off. It just reboots when holding the power button. It doesn't enter recovery when I hold the volume-up button. I do get a fastboot logo when booting with the volume-down button. But no response on the USB cable and the logo just stays on exactly like the mi logo in normal boot. I'm not sure but I think fastboot is supposed to show some kind of menu interface? Or is it normal to see a fastboot logo only?
I've read some other posts about Xiaomi phones using different brands of digitizers, having to clear the cache to reset it and accept a different brand, but when I detach the digitizer it doesn't boot either .
I could try a factory reset with mi flash but it requires Windows which i don't have easy access to (if it even detects the phone). Perhaps there's a way to rescue it that doesn't involve losing all data, i might as well just buy a new phone if i have to reinstall/configure everything. anyway.
Any ideas?
Hello everybody, I'm having this loop problem with my phone. I didn't do anything like installing another rom or any modifications to it. I accidentaly restarted the phone and now it's on this "Android One" loop forever. I can't shut down the phone, I need to disconnect the battery to do that. I tried Test Point, Mi Flash, Fastboot... Nothing works, it's like the phone is rebooting always, even in Fastboot and Test Point with Mi Flash. In Fastboot reboots after 5 seconds or something like that, it wont stay there. Same for Mi Flash, when I try to flash the original rom it disconnects after a few seconds and then it's like the phone reboots again. I don't know what else to do, I tried everything I could find on the internet.
Fastboot won't work, it's all locked and even if it wasn't the phone just reboots after a few seconds...
EDL and Mi Flash get the disconnected error, like I said, seems that it reboots with this method too...
I spent hours trying to fix this, now I have no more ideas on what to do. If anyone have something in mind that could fix this, please comment.
Thanks to all.
SOLUTION: I managed to get it working. Here is how:
I used the original USB cable (I don't know if it works with another one). I connected the USB cable to a USB 2.0 port of a Desktop PC (directly to Motherboard, I tried front USB and laptops, nothing worked for me). Then I did the short between the two EDL pins and started pressing the power button over and over. Then you can release the EDL pin short and keep pressing the power button over and over, don't stop. Now you should be able to start the Flashing with the MiFlash software. If you're lucky like me, your pressing over and over the power button will keep the device connected to the PC, and your flashing will end succesfully.
ameegox said:
In Fastboot reboots after 5 seconds or something like that, it wont stay there.
Click to expand...
Click to collapse
Seems to me like problem with USB port or cable. Had the same symptoms when was connecting to any USB port in my PC MB, solution was to connect via USB 2.0 port in my Dell monitor USB HUB, which is connected to USB on MB.
Aerobatic said:
Seems to me like problem with USB port or cable. Had the same symptoms when was connecting to any USB port in my PC MB, solution was to connect via USB 2.0 port in my Dell monitor USB HUB, which is connected to USB on MB.
Click to expand...
Click to collapse
I've been trying different ports and different cables. The phone keeps restarting when trying to flash via EDL and MiFlash. It wont let me flash because it restarts in the flashing process, and that's a constant loop.
2 days ago i woke up to my phone's screen already on (mi a2), it had been frozen for 2 hours (woke up at 3:40pm but the phone lockscreen showed 1:14pm) so i held down the power button to soft reset it but now the phone was stuck in a bootloop. Been 2 days now of trial and error and a whole load of research which now leaves me here. The bootloader is unlocked but trying to flash stock rom (have tried multiple versions) through miflash gives me "Flash bluetooth_a error", trying to flash it manually through cmd on platform tools gives me the following:
fastboot flash bluetooth_a bluetooth.img
Sending 'bluetooth_a' (556 KB) OKAY [ 0.031s]
Writing 'bluetooth_a' FAILED (remote: 'Error flashing partition : Device Error')
fastboot: error: Command failed
Anyone know how i can fix this?
ameegox said:
SOLUTION: I managed to get it working. Here is how:
I used the original USB cable (I don't know if it works with another one). I connected the USB cable to a USB 2.0 port of a Desktop PC (directly to Motherboard, I tried front USB and laptops, nothing worked for me). Then I did the short between the two EDL pins and started pressing the power button over and over. Then you can release the EDL pin short and keep pressing the power button over and over, don't stop. Now you should be able to start the Flashing with the MiFlash software. If you're lucky like me, your pressing over and over the power button will keep the device connected to the PC, and your flashing will end succesfully.
Click to expand...
Click to collapse
My MiA2 had a similar problem. It rebooted spontaneously (reason unknown to me, perhaps it landed on the couch too roughly when I took it out of my pocket) and got stuck in a boot loop as you described. Fastboot waited for 5 seconds and then the device rebooted already. Holding volume up landed me in a screen that said "no command" and then rebooted after a few seconds just like fastboot.
I solved it by connecting my MiA2 via a USB cable to my laptop, activating fastboot on the MiA2 and then keeping on pressing the power button like a madman. I kept this up for about 20 seconds. The device did not reboot in those 20 seconds. Then, I stopped pressing the power button and instead pressed it continuously for about 10 seconds. The device then finally switched itself off. And on again, automatically. But, the boot loop was now fixed: the device showed the AndroidOne logo for quite a while like it normally does when booting, then the colored line and finally the SIM unlock screen.
Thank you for posting your solution! It made me attempt pressing the power button like a madman, which stopped the device from booting during the fastboot, which finally allowed me to fix it by actually turning the device off.
I hope my solution will help anyone encoutering this problem.
With kind regards,
Sven Berkvens-Matthijsse
svenberkvens said:
My MiA2 had a similar problem. It rebooted spontaneously (reason unknown to me, perhaps it landed on the couch too roughly when I took it out of my pocket) and got stuck in a boot loop as you described. Fastboot waited for 5 seconds and then the device rebooted already. Holding volume up landed me in a screen that said "no command" and then rebooted after a few seconds just like fastboot.
I solved it by connecting my MiA2 via a USB cable to my laptop, activating fastboot on the MiA2 and then keeping on pressing the power button like a madman. I kept this up for about 20 seconds. The device did not reboot in those 20 seconds. Then, I stopped pressing the power button and instead pressed it continuously for about 10 seconds. The device then finally switched itself off. And on again, automatically. But, the boot loop was now fixed: the device showed the AndroidOne logo for quite a while like it normally does when booting, then the colored line and finally the SIM unlock screen.
Thank you for posting your solution! It made me attempt pressing the power button like a madman, which stopped the device from booting during the fastboot, which finally allowed me to fix it by actually turning the device off.
I hope my solution will help anyone encoutering this problem.
With kind regards,
Sven Berkvens-Matthijsse
Click to expand...
Click to collapse
worked like a charm on the first attempt. thanks a lot.
Thanks for your advice!! For me it was easier
Problem:
- boot loop each 5 seconds with the anroid one logo
- boot loop in recovery (pressing power+volume up) showing open android with "no command", if pressed "power + volume up" again I entered in recovery options, but the phone rebooted after few seconds and didn't let choose any option
- boot loop in fastboot mode (pressing power + volume down), rebooted after 5 seconds
Solution:
No cable connected, just entered in Fastboot (power+volume down) and continuously and repeatedly pressed volume up and volume down for 10 seconds and more. In that way the phone didn't reboot and stayed in the fastboot mode. After being sure that the phone wasn't rebooting (waited about 30 seconds without doing nothing) I powered off.
Powered on again, crossed fingers, and the phone booted normally
Hope it helps
svenberkvens said:
My MiA2 had a similar problem. It rebooted spontaneously (reason unknown to me, perhaps it landed on the couch too roughly when I took it out of my pocket) and got stuck in a boot loop as you described. Fastboot waited for 5 seconds and then the device rebooted already. Holding volume up landed me in a screen that said "no command" and then rebooted after a few seconds just like fastboot.
I solved it by connecting my MiA2 via a USB cable to my laptop, activating fastboot on the MiA2 and then keeping on pressing the power button like a madman. I kept this up for about 20 seconds. The device did not reboot in those 20 seconds. Then, I stopped pressing the power button and instead pressed it continuously for about 10 seconds. The device then finally switched itself off. And on again, automatically. But, the boot loop was now fixed: the device showed the AndroidOne logo for quite a while like it normally does when booting, then the colored line and finally the SIM unlock screen.
Thank you for posting your solution! It made me attempt pressing the power button like a madman, which stopped the device from booting during the fastboot, which finally allowed me to fix it by actually turning the device off.
I hope my solution will help anyone encoutering this problem.
With kind regards,
Sven Berkvens-Matthijsse
Click to expand...
Click to collapse
Yep I also can confirm this saved my phone. In my case, only pressing all 3 buttons (volume up, down, and power) randomly a lot for 20 seconds worked. I then turned off my phone, it restarted automatically, and then just booted normally!
Hi,
Thanks a lot for this post. Ive just created this account to say thank you here.
Tried this and pressed the POWER button like crazy for a few seconds when it was stuck in the same auto reboot loop, and it worked first time. Crazy. This had been stuck for a while and a few phone shop told me they couldn't help me with this problem. Now the Xiaomi Mi A2 works!
Thanks guys!