Related
hi,
I'm G1 user not under T-mobile service.
I haven't got the root. Now I use official T-mobile Firmware v1.6 and official spl.
note: I've done nothing with the rom. Every part of my g1 is official.
After my first clean the trackball(disassemble and assemble), It still works well. I'm sure Every function and key(hardware button) also trackball works well after that.
But the second day, when I turn off my g1 and boot again, I met the blue light mode for the first time.
After search in google and try every solution, It boots and works well again. I tried turn off and boot again several time. That mode did not appear again.
Now three days after that, I've met blue light mode again. Still, after tried 'take out the battery' and 'plug/unplug the charger' for about ten min, It boot again!
I've seem some guys in this forum argue about it, say, the blue light mode is caused by unofficial SPL. Now, we can sure that it is obviously not caused by unofficial SPL.
I believe it must caused by some hardware issue.
Is there someone still tried to work out the reason of blue light mode?
The blue light mode issue really drive me crazy
forgive my poor English...
Even more...
When it's in blue light mode, I can see the blue light flash once after plug the charger or put in the battery sometime.
If I put the battery in first and then plug the charger, I found the blue light flash once and then red light on shows it's charging...
I'll try my best to tell the details, if anyone needs them.
Maybe the device thinks you would be pressing the trackball..
I think it's a hardware issue.
Pressing trackball while booting does flash the blue light.
Maybe the device thinks you would be pressing the trackball..
I think it's a hardware issue.
Pressing trackball while booting does flash the blue light.
open it and make sure nothing is pressing on the trackball. Blue-light mode is accessed by pressing trackball during boot, and I have a pretty good feeling something is keeping your trackball depressed, specially since you worked on it, make sure all the mechanisms are working fine
My phone is the same way, the trackball (hardware) is messed up so I get blue-light mode every boot.
To boot it, I hold the trackball in every possible direction, then boot; eventually it does.
This is a note to most people that want to clean out their trackballs-DONT
maxisma said:
Maybe the device thinks you would be pressing the trackball..
I think it's a hardware issue.
Pressing trackball while booting does flash the blue light.
Click to expand...
Click to collapse
Thanks,maxisma and jubeh. I'm sure that the trackball is not pressed, and the trackball works 100% OK('all direction' and 'press down'...mechanisms) in android system.(I'll check it again to confirm)
happyface_0 said:
My phone is the same way, the trackball (hardware) is messed up so I get blue-light mode every boot.
To boot it, I hold the trackball in every possible direction, then boot; eventually it does.
This is a note to most people that want to clean out their trackballs-DONT
Click to expand...
Click to collapse
Thanks,happyface_0. Next time I meet the issue, I'll validate it.
I think I'll check the trackball(hardware) again and tried to find the reason.
-------------------------------------------------------------------------
I've check the trackball. It seems really that the trackball not release every time after press it down.
You may have moisture under the button in the trackball if its a similar design to blackberry (small dome type disc on top of 2 small contacts and the whole thing covered with tape) or maybe the disk is flat and not returning to its usual dome shape
Highly technical terms I know /sarcasm
Moved to Q&A
in the end...
hey, finally I've fixed the trackball button.
Like what senaia said, it's caused by moisture or dirty.
After clean the small dome type disc and 2 small contacts,covered with new scotch tape, it's recovered.
So we summed up that the blue light mode must caused by the trackball button error. Not rom/spl error not brick!
Thanks everyone!
Hey guys I think I actually did it. I was going to install the JPC Froyo Rom, and somehow booted into recovery in the ROM. Now whenever I turn the phone on it boots into recovery, and none of the button combinations work for putting it into Download mode so I can flash back to stock. On the i9000 thread it says that if you get into this situation you cannot flash back. Any of you guys run into this issue? If not then it looks like I'll be trying to convince an ATT rep to give me a new phone
Try powering off... Then hold vol up and down buttons then plug in usb.... That happened to me... Your not bricked
Sent from my SAMSUNG-SGH-I897 using XDA App
Connect to adb and run reboot command
Sent from my GT-I9000 using XDA App
Nope
Nope sorry guys I know all of what you just said. As for plugging in USB while holding volume buttons, it'll just go to that battery charging screen, and adb doesn't work because it doesn't boot past recovery. Sorry guys but yes it was bricked. It's okay though because I just went to ATT and since they can't identify the problem they just replaced the phone
Thought mine was bricked one night, too. Same scenario. Tried dropping the SIM and SD card out even though I didn't think it would make a difference, but it did. Got to download screen and reflashed with ODIN.
Good luck.
Sent from my SAMSUNG-SGH-I897 using XDA App
KCutrer1 said:
Nope sorry guys I know all of what you just said. As for plugging in USB while holding volume buttons, it'll just go to that battery charging screen, and adb doesn't work because it doesn't boot past recovery. Sorry guys but yes it was bricked. It's okay though because I just went to ATT and since they can't identify the problem they just replaced the phone
Click to expand...
Click to collapse
If you pull the battery, then put the battery in. hold both volume buttons buttons, and then plug the phone into the computer, it didn't boot to download?
Im curious if you even tried to use the Odin one click thread
There are 4 or 5 ways in that thread on how to get to download mode. And how exactly does this relate to development...just another curious thought. Well, you are getting a new phone, just hope that ATT or Samsung don't try to figure out the cause of your phone being "bricked".
AGAIN!
Okay after this I swear I won't be messing around with Froyo anymore. Here's the story: I got into download on the replacement captivate. Tried to install JPC froyo, but it never started flashing so I unplugged it from Odin and then tried to turn it back on. It goes to the normal "connect phone to computer" screen. However no attempts to get back into download mode have worked. Holding both volume buttons and power until second black screen doesn't work, booting while holding volume down doesn't work, holding both volume buttons and then inserting USB cable doesn't work. I think I'm stuck in this screen unless there's some incredible way I have yet to try. Anybody have any ideas? I would greatly appreciate feedback from the experienced users (Zilch25, designgears, kaik, reaver117), because I think I'd be pushing it trying to get it replaced a second time in such rapid succession
To flashman2002:
I put it in this section because it's in the development section that most flashing and such occurs so I thought there would be the greatest knowledge base. And yes I've pored over the one click thread and none of the methods mentioned there have any effect!
Jeez, I just scared the **** out of myself. I ran the remove lagfix script and it rebooted my phone but it was just a black screen. So I take the battery out. Bad Idea. It showed the ATT screen but just black after that. I could get it into recovery mode but not download. Then I messed some more and would only show a vague disconnected pic.
Finally I got it into download by doing this: (had odin open before hand)
1. took everything out including sim and usb cable.
2. quickly inserted battery and held volume buttons and very quickly inserted usb.
I'm pretty sure its the speed that matters because I tried about 4 times and only when I did it really fast did it work.
ThisWasATriumph said:
Jeez, I just scared the **** out of myself. I ran the remove lagfix script and it rebooted my phone but it was just a black screen. So I take the battery out. Bad Idea. It showed the ATT screen but just black after that. I could get it into recovery mode but not download. Then I messed some more and would only show a vague disconnected pic.
Finally I got it into download by doing this: (had odin open before hand)
1. took everything out including sim and usb cable.
2. quickly inserted battery and held volume buttons and very quickly inserted usb.
I'm pretty sure its the speed that matters because I tried about 4 times and only when I did it really fast did it work.
Click to expand...
Click to collapse
Nope. Unless you can do this with godly speed I dont think it'll work. I just got to the "Connect Phone to Computer" screen again.
You had the usb in before anything appeared on the screen right?
ThisWasATriumph said:
You had the usb in before anything appeared on the screen right?
Click to expand...
Click to collapse
Yeah originally. I can get to that screen now by just putting the battery in and holding power button. It seems to behave exactly like it normally would, just can't get out of it.
What screen? The screen you want has a big yellow triangle and says download.
ThisWasATriumph said:
What screen? The screen you want has a big yellow triangle and says download.
Click to expand...
Click to collapse
No it's on the phone...!...computer screen. That's what I'm saying, it's been stuck here for a while and none of the methods described on the one click thread work. I've been here before and just holding volume buttons and holding down power for it to boot twice and releasing would do it. Not so anymore. Can't get into download mode doing anything!
Well I read In the SRE thread I think that there are reports of newer phones not responding to any button combos. Bad batch they said not on purpose...
Also for the i9000 apparently you only have to hold the down volume key so since you flashed a i9000 rom try that if you haven't already.
You cant get into recovery right? Just holding volume and power then letting go of power after a bit?
Adb reboot download...
Sent from my SAMSUNG-SGH-I897 using XDA App
ThisWasATriumph said:
Well I read In the SRE thread I think that there are reports of newer phones not responding to any button combos. Bad batch they said not on purpose...
Also for the i9000 apparently you only have to hold the down volume key so since you flashed a i9000 rom try that if you haven't already.
You cant get into recovery right? Just holding volume and power then letting go of power after a bit?
Click to expand...
Click to collapse
Nope none of it works. I just got it replaced less then 3 hours ago and I already bricked it. I hope somebody finds out something that'll get this fixed. Maybe some way to force download mode through a computer application or something.
Well theres adb like mentioned above but im pretty sure that requires at least recovery mode working.
Like i said before i was stuck on the same screen so maybe theres still hope.
If all else fails someone will figure out how to JTAG these things eventually...
ThisWasATriumph said:
Jeez, I just scared the **** out of myself. I ran the remove lagfix script and it rebooted my phone but it was just a black screen. So I take the battery out. Bad Idea. It showed the ATT screen but just black after that. I could get it into recovery mode but not download. Then I messed some more and would only show a vague disconnected pic.
Finally I got it into download by doing this: (had odin open before hand)
1. took everything out including sim and usb cable.
2. quickly inserted battery and held volume buttons and very quickly inserted usb.
I'm pretty sure its the speed that matters because I tried about 4 times and only when I did it really fast did it work.
Click to expand...
Click to collapse
I know it doesn't help you out now, but when you remove the lag fix, just leave it set on the black screen. It's doing its thing. It will reboot when it's done. The home keys should still light up if you press them in this state...
Well thanks for your input anyway guys. Hopefully somebody figures something out. For now I guess I'll keep the SIM in my old iPhone 3G so I at least have a phone. Tomorrow I'll go to another ATT store in my area. Chances are the rep won't know what the hell that screen means and will replace the phone promptly.
My one wont charge or boot. I had it in a pocket in my uniform all day. I only noticed it stop working when I was leaving at the end of the day. I have a black screen and no amount of holding down power or volume keys will do anything. It wont hard reset and I cannot get to the bootloader. I dont get the charging light when I plug it into the computer or charger, however it does get pretty hot as if it is charging. I didnt do any serious software modding to it as I only unlocked the bootloader, installed twrp, and installed ARHD 9.4. Not sure what to do. Any help would be greatly appreciated.
leetlikeawping said:
My one wont charge or boot. I had it in a pocket in my uniform all day. I only noticed it stop working when I was leaving at the end of the day. I have a black screen and no amount of holding down power or volume keys will do anything. It wont hard reset and I cannot get to the bootloader. I dont get the charging light when I plug it into the computer or charger, however it does get pretty hot as if it is charging. I didnt do any serious software modding to it as I only unlocked the bootloader, installed twrp, and installed ARHD 9.4. Not sure what to do. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sounds like the device is "on" but it's locked up with the screen off. When you're holding down the PWR + VOL DOWN button(for at least ~10-15seconds), are you in a brightly lit room or can you shine at light at the sensor? I know it sounds nuts, but there seems to be some safeguard on HTC's part that it will check the light sensor before rebooting in case the buttons get pushed in your pockets.
Alternatively, plug it into your computer and use ADB(or the All in One Toolkit) to issue the "adb reboot recovery" command.
unremarked said:
Sounds like the device is "on" but it's locked up with the screen off. When you're holding down the PWR + VOL DOWN button(for at least ~10-15seconds), are you in a brightly lit room or can you shine at light at the sensor? I know it sounds nuts, but there seems to be some safeguard on HTC's part that it will check the light sensor before rebooting in case the buttons get pushed in your pockets.
Alternatively, plug it into your computer and use ADB(or the All in One Toolkit) to issue the "adb reboot recovery" command.
Click to expand...
Click to collapse
So i tried it in a very lit room but still nothing. I tried adb before but my computer is not even seeing the device. "adb devices" shows nothing and its not a driver issue because I am running linux and I was able to fastboot and adb this device before.
I was thinking the same thing that its kinda frozen. I never thought that not being able to access the battery would be an issue but in this situation it would be extremly helpfull. Maybe all I can do is wait until I am sure the battery is dead and try and charge it and see if the charging light comes on. This really sucks...
leetlikeawping said:
So i tried it in a very lit room but still nothing. I tried adb before but my computer is not even seeing the device. "adb devices" shows nothing and its not a driver issue because I am running linux and I was able to fastboot and adb this device before.
I was thinking the same thing that its kinda frozen. I never thought that not being able to access the battery would be an issue but in this situation it would be extremly helpfull. Maybe all I can do is wait until I am sure the battery is dead and try and charge it and see if the charging light comes on. This really sucks...
Click to expand...
Click to collapse
I just had this happen to me and I followed these instructions and held it closer to the light and it came back on.
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
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?