[Tech Support] Help, May Have Bricked Phone! - One (M8) Q&A, Help & Troubleshooting

[DELETED]

thebeanogamer said:
So, I may have done a bad. I attempted to install Cyanogen mod on my Vodafone HTC One M8, following the exact instructions on there wiki page, even using their recovery.
Click to expand...
Click to collapse
Cyanogen Recovery? I haven't seen anyone here use it, and wan't even aware it was supported on this device. Did you get the recovery flashed and operational, than tried flashing the ROM? The exact sequence is not clear, from your description.
thebeanogamer said:
It now will not turn on unless I plug it in, when it will do one of two things. Either it will hang on a photo of a battery, or it will hang on that with the red text at the bottom. It always does the latter when plugged into the wall, and mixes it up when plugged into the computer. If it is the latter I cannot turn it off until the battery dies, but in the case of the former it waits a few seconds then powers off. No combination of buttons will turn the device on. I have backups saved, so if I can get into fastboot I can easily fix it.
Click to expand...
Click to collapse
Does the phone reboot if you hold power + vol up for a minute or 2?

[DELETED]

thebeanogamer said:
No unfortunatly to both.
Click to expand...
Click to collapse
I asked a few more questions/clarifications in my previous post. Hard to help, without the proper info.

[DELETED]

Related

Downloading...do not turn off target.

Hey guys I really need help here. I have no clue how but my phone into some weird mode displaying the message in the title. I have a stock Nexus and didn't try to flash or anything like that.
I tried everything on the internet but nothing seems like its working. I am a real noob and need any advice. Is there a way to get the phone back to normal without having to unlock it, root or something like that?
you most likely turned it on without realizing that your fingers are on the volume down and power at the same time. try pulling the battery and turn on the phone again
crazyalaa said:
Hey guys I really need help here. I have no clue how but my phone into some weird mode displaying the message in the title. I have a stock Nexus and didn't try to flash or anything like that.
I tried everything on the internet but nothing seems like its working. I am a real noob and need any advice. Is there a way to get the phone back to normal without having to unlock it, root or something like that?
Click to expand...
Click to collapse
You put your phone into download mode somehow.
At least, if your title is what your talking about.....then yea, your in download mode.
If you didn't flash anything....try just pulling the battery and restarting the phone.
I tried that. Nothing is working; the phone gets stuck on the google logo and then the logo itself goes and comes back really quickly then the phones turn off. When the phone turns off it takes 10 mins to get it up again!! No clue...
Now the phone won't turn on.
crazyalaa said:
I tried that. Nothing is working; the phone gets stuck on the google logo and then the logo itself goes and comes back really quickly then the phones turn off. When the phone turns off it takes 10 mins to get it up again!! No clue...
Click to expand...
Click to collapse
Can u boot into recovery? If so just flash a rom.
Sent from my Galaxy Nexus using xda premium
The phone isn't turning on anymore
Is the battery now dead? Will the phone turn on when its plugged in?
I got back to the same screen now, I removed the battery and phone won't even turn off. It's stuck on the same screen even without the battery??? what's going on?
Update: Ok the phone turned off and then I tried to turn it on. It goes to the Google logo and then the screen goes blank.
crazyalaa said:
I got back to the same screen now, I removed the battery and phone won't even turn off. It's stuck on the same screen even without the battery??? what's going on?
Update: Ok the phone turned off and then I tried to turn it on. It goes to the Google logo and then the screen goes blank.
Click to expand...
Click to collapse
Can you get to the bootloader?
Vol. Down + vol. Up and power together.
If so then you'll be fine. Just flash a factory image.
There are a few threads that will go through the process in more detail than I am willing to at 6:08am!
Is there a way to take my photos and contact from the phone while it's in the downloading mode or any other way before I flash it. Or am I screwed? I don't have my stuff synced with google+
crazyalaa said:
Is there a way to take my photos and contact from the phone while it's in the downloading mode or any other way before I flash it. Or am I screwed? I don't have my stuff synced with google+
Click to expand...
Click to collapse
If the phone doesnt completely reboots to android, I dont think you can get your photo's.
Can you still get in fastboot mode?
my phone is doing the same thing, the downloading screen. I am totally stock, and i can easily turn my phone on and off except i wanna get into bootloader to flash CWM recovery and i cant do so because this screen is popping up.
bendirkss said:
my phone is doing the same thing, the downloading screen. I am totally stock, and i can easily turn my phone on and off except i wanna get into bootloader to flash CWM recovery and i cant do so because this screen is popping up.
Click to expand...
Click to collapse
Are you able to boot into the OS? Or it's only giving you download mode no matter what?
Do you have adb set up if yes adb reboot boot loader that will boot you into the boot loader screen
Sent from my Galaxy Nexus using xda app-developers app
cmstlist said:
(...) it's only giving you download mode no matter what?
Click to expand...
Click to collapse
this first.
DaLoona said:
If the phone doesnt completely reboots to android, I dont think you can get your photo's.
Can you still get in fastboot mode?
Click to expand...
Click to collapse
Bfitz26 said:
Do you have adb set up if yes adb reboot boot loader that will boot you into the boot loader screen
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
he can if adb is already running on the system. seems to be that he can't.
@op, if you're stuck on download mode, try odin (damn i really hate suggesting it); i was trying to see if heimdall supports our device, have yet to find proof.
crazyalaa said:
Hey guys I really need help here. I have no clue how but my phone into some weird mode displaying the message in the title. I have a stock Nexus and didn't try to flash or anything like that.
I tried everything on the internet but nothing seems like its working. I am a real noob and need any advice. Is there a way to get the phone back to normal without having to unlock it, root or something like that?
Click to expand...
Click to collapse
Is there a big green outlined arrow box at the top of your screen that says start, and it points to your power button? If so you are just at the Odin screen instead of your boot loader screen. You get here by just holding vol down and power instead of of holding both vol up/down and power which would bring you to the bootlloader. Also your phone obviously needs to be off before doing either of these. If in fact you are at the Odin screen simply push power and your phone will boot.
sent from my nexus using all the new features of the iphone5
crazyalaa said:
Hey guys I really need help here. I have no clue how but my phone into some weird mode displaying the message in the title. I have a stock Nexus and didn't try to flash or anything like that.
I tried everything on the internet but nothing seems like its working. I am a real noob and need any advice. Is there a way to get the phone back to normal without having to unlock it, root or something like that?
Click to expand...
Click to collapse
It sounds like your volume-down button might be stuck in the pressed-down position (or just shorted out). If that is the case, every time you try to turn your phone on, you will see the screen you described. You can try pressing the volume buttons many times to see if you can get the volume-down button unstuck. If you can't, you can replace the buttons fairly cheaply.
Of course, it could be caused by something else entirely, but that's what it seems like to me.
strumcat said:
It sounds like your volume-down button might be stuck in the pressed-down position (or just shorted out). If that is the case, every time you try to turn your phone on, you will see the screen you described. You can try pressing the volume buttons many times to see if you can get the volume-down button unstuck. If you can't, you can replace the buttons fairly cheaply.
Of course, it could be caused by something else entirely, but that's what it seems like to me.
Click to expand...
Click to collapse
If the vol-down button is stuck, try booting it up with both up and down held. You might be able to get either recovery or bootloader.
cmstlist said:
If the vol-down button is stuck, try booting it up with both up and down held. You might be able to get either recovery or bootloader.
Click to expand...
Click to collapse
+1
yeah try that
cmstlist said:
Are you able to boot into the OS? Or it's only giving you download mode no matter what?
Click to expand...
Click to collapse
Its working fine now. Except when I flash CWM, vis cmd prompt like I usually do, I can only go unto cem right away and then once I boot up into the os and turn the phone off to get into recovery stock recovery comes back.
Sent from my Galaxy Nexus

[Q] Unbelievable Galaxy Nexus problem.

This is my first post on the XDA forum. I registered only 2 try 2 have a reply 2 a problem that in my language (italian) is impossible to find out.
This is the best place for everything concerning android world so I hope to be lucky.
This morning my galaxy nexus, while I was playing @ paradise island, freezed and started to play several times a sound that was like an emergency (almost like the overheat processor beep in the computer cases - never heard that before). After this emergency beep the phone shutted off.
When I turned it on the Google logo appears but it start having gliches and reboot. This infinite times until the battery is removed. Sometimes it arrives to the colorful background but that times also it freeze (without gliches) and reboot.
Tryin 2 find out the problem I had a soft reset (battery off for 10 mins) but nothing.
I tried also an hard reset. The phone anyway after having selected RECOVERY MODE from the apposite menu start the google logo and when reaches the "red alert signal droid" the droid is gliched and the phone freeze and reboot. And start another time infinite reboots.
Someone know what kind of problem the phone have? It enters without problems in odin mode and the (I kind is called) bootload mode but don't start the recovery mode. I'm totally n00b, the phone is in fact stock, and I don't want 2 wait 1 month of assistance time if is a problem that can be resolved also @ home.
Please help me if you can and thanks for gifting me with your time.
- NeX - said:
.... The phone anyway after having selected RECOVERY MODE from the apposite menu start the google logo and when reaches the "red alert signal droid" the droid is gliched and the phone freeze and reboot. And start another time infinite reboots.
....
Click to expand...
Click to collapse
Sorry to ask but I don't understand gliched, can you get in Stock Recovery (the "red alert signal droid" as you call it), push volume up and power at the same time and enter the recovery menu? Or not?
Diger36 said:
Sorry to ask but I don't understand gliched, can you get in Stock Recovery (the "red alert signal droid" as you call it), push volume up and power at the same time and enter the recovery menu? Or not?
Click to expand...
Click to collapse
no I can't. The droid is gliched so the volume up + power combo doesn't work. The phone reboot some times. Some others times (like the trying I had now) the phone freezes.
Try flash the google stock images through fastboot, there are threads with instructions and links to everything you will need.
You should be able to fix whatever is wrong.
nodstuff said:
Try flash the google stock images through fastboot, there are threads with instructions and links to everything you will need.
You should be able to fix whatever is wrong.
Click to expand...
Click to collapse
If doing it I can loose warranty?
No, you can re-lock your bootloader when you are done.
matt2053 said:
No, you can re-lock your bootloader when you are done.
Click to expand...
Click to collapse
And the problem for sure is going 2 be solved? Seems super!
It MAY solve your problems, if they are software related.
If its a hardware problem it won't.
Give it a try anyway.
nodstuff said:
It MAY solve your problems, if they are software related.
If its a hardware problem it won't.
Give it a try anyway.
Click to expand...
Click to collapse
ok i'll search and try it.
to me, sounds like hardware problem.
this is the toolkit you should try - http://forum.xda-developers.com/showthread.php?t=1392310
joshtb86 said:
to me, sounds like hardware problem.
this is the toolkit you should try - http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
He is better off using fastboot and learning something.
Tool kits are the wrong way to do things, it is better to know what is actually happening when you pick an option in a toolkit.
nodstuff said:
He is better off using fastboot and learning something.
Tool kits are the wrong way to do things, it is better to know what is actually happening when you pick an option in a toolkit.
Click to expand...
Click to collapse
the problem is that I don't know anything of this stuff. I don't know how to start.
The toolkit guide is huge and I think i should do only 2 or 3 of the all listed operation...
For now i took only the kit, the pdanet for win 64 and the yakju 4.0.4 from the google page. I don't know how 2 put them on and in which order.
.....
Oh, phone of my colleague has the same issue. We don't know what to do cause we can't connect Nexus to computer. When trying to do this Fastboot 2147483647 error occurs. Adb devices gives empty list.
Sounds like a hardware problem to me
- NeX - said:
the problem is that I don't know anything of this stuff. I don't know how to start.
The toolkit guide is huge and I think i should do only 2 or 3 of the all listed operation...
For now i took only the kit, the pdanet for win 64 and the yakju 4.0.4 from the google page. I don't know how 2 put them on and in which order.
Click to expand...
Click to collapse
Learn.
It looks like rocket science to me at first(Gnex is my first smartphone), do it slowly.
- NeX - said:
no I can't. The droid is gliched so the volume up + power combo doesn't work. The phone reboot some times. Some others times (like the trying I had now) the phone freezes.
Click to expand...
Click to collapse
Not sure if this is different on other phones but for me to get to recovery its not Volume up + Power. Its Volume up + volume down + power (i.e. hold both volume buttons then hold power button until it vibrates or the google logo shows up)
WoodroweBones said:
Not sure if this is different on other phones but for me to get to recovery its not Volume up + Power. Its Volume up + volume down + power (i.e. hold both volume buttons then hold power button until it vibrates or the google logo shows up)
Click to expand...
Click to collapse
This gets you to bootloader, not recovery
Sent from my i9250

Bricked?

Bell Galaxy S3 running stock JB rooted
I went to flash to Cyanogenmod 10.1 Nightly, it failed (Error status 7) so I attempted to reboot. Screen went black and stayed black, I left it for a few minutes, nothing happened then tried a battery pull. Now nothing. When I plug into my computer it makes the connect/disconnect chime but nothing else. If I hold down the power for ~10sec my laptop makes the disconnect chime, then when I release the power button it reconnects to my laptop (not sure if that helps any)
Just to further clarify, I cannot get to the download or recovery mod, screen is blank, no led when plugged in either.
Is it hard bricked?
I am looking at mobiletechvideos.com at their JTAG repair service. Is that my only/best option?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
If all you did was try to flash cm10.1 then you are not bricked. You might not be doing the 3 button combo correctly to get back into recovery. Do this...
Pull Battery so power down device and then put it back in.
Hold volume Down, Home, then Power Button.
Release all of them when the 1st screen pops up. It's all about timing here.
That should take you back into recovery so you can just restore the nandroid backup you should've made prior to flashing anything.
No good, the screen is pure black no matter if I just try to power on, vol up + power + home, or vol down + power + home. Black screen.
Pull your battery, leave it out, and then plug it in.. no buttons or anything, it should turn on and see if it gets to the battery charging screen (which should show a lightning bolt only).
If it gets that far, power button and home button until you feel it vibrate, let go and it should boot.. post if it doesn't..
Don't press volume buttons, just home/power combo until it vibes..
Ok, so I did like you said, pulled battery and plugged the phone in to charge. I now get a solid red LED (this did not happen with the battery in), no lightning bolt though. The red LED turns off after about 2 minutes.
mooseknuckles1 said:
Ok, so I did like you said, pulled battery and plugged the phone in to charge. I now get a solid red LED (this did not happen with the battery in), no lightning bolt though. The red LED turns off after about 2 minutes.
Click to expand...
Click to collapse
Well, at least the power connector inside isn't busted.. that's a good thing..
with it plugged in, does it turn on like normal? Just regular "boot my phone" mode, no recovery or download?
Try while the LED is on, and if nothing, try it after it goes out.. as I'm not entirely sure what that could mean..
Wiltron said:
Well, at least the power connector inside isn't busted.. that's a good thing..
with it plugged in, does it turn on like normal? Just regular "boot my phone" mode, no recovery or download?
Try while the LED is on, and if nothing, try it after it goes out.. as I'm not entirely sure what that could mean..
Click to expand...
Click to collapse
doesnt turn on at all, still just black screen. I tried the home+power button when the LED goes out, no luck.
mooseknuckles1 said:
doesnt turn on at all, still just black screen. I tried the home+power button when the LED goes out, no luck.
Click to expand...
Click to collapse
Just the power button.. no volume/home buttons..
If all that was done was updating CWM on an already rooted phone, then only your recovery is borked, which is still repairable.. but if you were flashing something else, say CF-AutoRoot or a ROM, then I need to know..
Since you said Error=7, then I can assume you already had a working copy of CWM on it.. correct?
Ya I already had CWM on it. I was trying to flash Cyanogenmod 10.1 nightly (todays release) on to the phone. I had Cyanogen10 on it a while back then switched back to stock firmware. I was curious as to the new JB4.2 so I wanted to try out Cyanogenmod 10.1
Wiltron said:
Just the power button.. no volume/home buttons..
If all that was done was updating CWM on an already rooted phone, then only your recovery is borked, which is still repairable.. but if you were flashing something else, say CF-AutoRoot or a ROM, then I need to know..
Since you said Error=7, then I can assume you already had a working copy of CWM on it.. correct?
Click to expand...
Click to collapse
the OP said in 1st post that he was flashing a rom. never mentioned cwm. the only way to have flashed a rom in the first place and gotten a status 7 would have been in a custom recovery.
reserved
Any chance you flashed an international ROM?
upndwn4par said:
Any chance you flashed an international ROM?
Click to expand...
Click to collapse
exactly.
but what all is actually accomplished before an error message?
xBeerdroiDx said:
exactly.
but what all is actually accomplished before an error message?
Click to expand...
Click to collapse
I still have a copy of the zip file on my computer, exact file name is cm-10.1-20130422-NIGHTLY-d2att.zip i cross checked with the Cyanogenmod site it says it is the proper ROM .zip to use
xBeerdroiDx said:
exactly.
but what all is actually accomplished before an error message?
Click to expand...
Click to collapse
I am not familiar with the partitions on that device, so I can't say for sure. But all it takes is one file installed in the wrong place and you'd be in trouble. And if that file gets installed in the recovery partition....
Edit:
mooseknuckles1 said:
I still have a copy of the zip file, exact file name is cm-10.1-20130422-NIGHTLY-d2att.zip i cross checked with the Cyanogenmod site it says it is the proper ROM .zip to use
Click to expand...
Click to collapse
Yup, that's the right one.
Could be the SGS3 sudden death???
upndwn4par said:
I am not familiar with the partitions on that device, so I can't say for sure. But all it takes is one file installed in the wrong place and you'd be in trouble. And if that file gets installed in the recovery partition....
Click to expand...
Click to collapse
i hear ya.
i thought thats why the script was set to check the recovery partition to ensure it was a compatible (up-to-date) platform to install from. i dont understand why it would begin installing and then check. but then, i'm no recovery coder
What about forcing download mode ? I.e. volume down+home and no battery and then plugging in the usb cord. Then put in battery after its in download mode ?
(IIRC)
Sent from my SAMSUNG-SGH-I747 using xda premium
hednik said:
What about forcing download mode ? I.e. volume down+home and no battery and then plugging in the usb cord. Then put in battery after its in download mode ?
(IIRC)
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Nope, nothing.
I want to thank everyone for the help and input so far!
There is no one in town here than can unbrick a hard bricked phone, but Toronto is only a 50min drive and there are a few places that will do it (~$70), or I can order one of those jigs online that plug into the microUSB port for about $60. It's looking like I will be going one of those routes.
mooseknuckles1 said:
Nope, nothing.
I want to thank everyone for the help and input so far!
There is no one in town here than can unbrick a hard bricked phone, but Toronto is only a 50min drive and there are a few places that will do it (~$70), or I can order one of those jigs online that plug into the microUSB port for about $60. It's looking like I will be going one of those routes.
Click to expand...
Click to collapse
um, usb jigs are about $3 on eBay.
i'm assuming you mean send it in for jtag?
xBeerdroiDx said:
um, usb jigs are about $3 on eBay.
i'm assuming you mean send it in for jtag?
Click to expand...
Click to collapse
Jig can work for the gs3. They are cheap no matter what. I used them on my cappy.
Sent from my SAMSUNG-SGH-I747 using xda premium

[Q] "Unfortunately, the process com.android.phone has stopped."

Hi guys, I'm very sorry if this has been solved already but I've been searching a lot now and none of the methods seemed to help me. I'm running a One X International. Until yesterday, I was running one of the older Cyanogenmod 10 Nightly builds but due to some performance issues and whatnot (nothing major), I decided to finally put in some work to update my phone to 10.1. My HBOOT was still on one of the older versions so after searching around, it seemed reinstalling the stock ICS and then doing some OTA updates would be the easiest way (for a n00b like me).
After doing so, I unlocked my bootloader again, re-rooted my phone, installed a newer version of CWM Recovery and finally flashed the latest stable build of CM 10.1. My first problem came after rebooting, where it would just hang at the Cyanogenmod ring loop and nothing else. I booted back to recovery and wiped everything (cache, data, dalvik etc.) and did a factory reset then reflashed the rom. This time it booted up but then, the "Unfortunately, the process com.android.phone has stopped." kept popping up. I literally can't do anything (there's a microsecond of space after I click OK before it would pop up again). I have read some people suggesting to others that they need to do a factory reset but I've tried doing that and it still didn't work. I've even tried installing the latest Nightly build of CM10.1 but it still didn't seem to make any difference.
Could someone please offer some advice? Thanks a lot in advance.
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
MarcusJKX said:
Could someone please offer some advice? Thanks a lot in advance.
Click to expand...
Click to collapse
Did you flash the boot image?, and if so, did you fastboot erase cache after flashing the boot image?
matt95 said:
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
Click to expand...
Click to collapse
I'm hoping that it's not and somehow I doubt it since I didn't have any problems like this until what I described earlier.
Did you flash the boot image?, and if so, did you fastboot erase cache after flashing the boot image?
Click to expand...
Click to collapse
I'm sorry, I'm not quite sure what you mean. Do you mean Boot image as in the bootloader? I didn't touch the bootloader except that it got upgraded whilst I updated the official HTC rom and also when I unlocked it. But I did erase everything before flashing.
MarcusJKX said:
I'm sorry, I'm not quite sure what you mean. Do you mean Boot image as in the bootloader? I didn't touch the bootloader except that it got upgraded whilst I updated the official HTC rom and also when I unlocked it. But I did erase everything before flashing.
Click to expand...
Click to collapse
he means
Code:
fastboot flash boot boot.img
matt95 said:
I had this problem and it was an hardware fault, so the only thing i could to was to send back the phone to HTC and get a new one...
Click to expand...
Click to collapse
matt95 said:
he means
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I don't think I did this. What is it for? I don't remember reading it in any guides although I read so many that I might've have forgotten.
MarcusJKX said:
I don't think I did this. What is it for? I don't remember reading it in any guides although I read so many that I might've have forgotten.
Click to expand...
Click to collapse
you have to flash the boot.img everytime u flash different rom
it is inside the zip file of the rom just extract it from there and take your phone to the bootloader and flash the boot.img...thn it will work perfectly
have a good read on how to flash a rom
http://forum.xda-developers.com/showthread.php?t=2069904
ll_r1d0_ll said:
you have to flash the boot.img everytime u flash different rom
it is inside the zip file of the rom just extract it from there and take your phone to the bootloader and flash the boot.img...thn it will work perfectly
Click to expand...
Click to collapse
Thanks a lot! I can't right now because like an idiot, I was in a rush before coz I had to leave for a few hours and really needed my phone so I thought maybe I'd try redoing the process. I got to the stage where I relocked the bootloader, factory reset, erased the rom, cache and pretty much everything but then I had to leave. Now that I'm back, the phone is out of battery coz I had it plugged in but it just wouldn't shut down for some reason so the screen remained on the bootloader wasting a ton of battery. This had happened yesterday when I was doing this and the battery would charge really slowly since the screen was constantly on. Do you know why this is? I don't think it's a hardware issue since after installing the stock rom yesterday, it could turn the phone off through the bootloader, recovery or just in the actual OS.
MarcusJKX said:
Thanks a lot! I can't right now because like an idiot, I was in a rush before coz I had to leave for a few hours and really needed my phone so I thought maybe I'd try redoing the process. I got to the stage where I relocked the bootloader, factory reset, erased the rom, cache and pretty much everything but then I had to leave. Now that I'm back, the phone is out of battery coz I had it plugged in but it just wouldn't shut down for some reason so the screen remained on the bootloader wasting a ton of battery. This had happened yesterday when I was doing this and the battery would charge really slowly since the screen was constantly on. Do you know why this is? I don't think it's a hardware issue since after installing the stock rom yesterday, it could turn the phone off through the bootloader, recovery or just in the actual OS.
Click to expand...
Click to collapse
the phone never charges in the bootloader ....as ur phone is off right now just plug it to a wall charger and leave it for around 2-3 hours and check if the Red LED turns on which will show that your phone is charging
ll_r1d0_ll said:
the phone never charges in the bootloader ....as ur phone is off right now just plug it to a wall charger and leave it for around 2-3 hours and check if the Red LED turns on which will show that your phone is charging
Click to expand...
Click to collapse
Aha didn't know that! Well I did leave it on the charger before i left although it was on the bootloader so like you said, it didn't charge. But when i came back (several hours later), the screen was black and the red LED was not on. Again like an idiot, I tried to turn it on and it went into the bootloader although it said that the battery is critically low. I then tried restarting it and now it's staying on the HTC Quietly Brilliant screen. Does it charge here? The red LED is on. If i press power+vol down then it would go into the bootloader so i guess it's not bricked right?
MarcusJKX said:
Aha didn't know that! Well I did leave it on the charger before i left although it was on the bootloader so like you said, it didn't charge. But when i came back (several hours later), the screen was black and the red LED was not on. Again like an idiot, I tried to turn it on and it went into the bootloader although it said that the battery is critically low. I then tried restarting it and now it's staying on the HTC Quietly Brilliant screen. Does it charge here? The red LED is on. If i press power+vol down then it would go into the bootloader so i guess it's not bricked right?
Click to expand...
Click to collapse
nop its not bricked and if your phone is now on just press the power button for few seconds until the 3 buttons flash and it wll turn off and when your phone will have enough battery charged it will automatically turn on (my htc one x do this) and dn you continue the steps dat i told you
ll_r1d0_ll said:
nop its not bricked and if your phone is now on just press the power button for few seconds until the 3 buttons flash and it wll turn off and when your phone will have enough battery charged it will automatically turn on (my htc one x do this) and dn you continue the steps dat i told you
Click to expand...
Click to collapse
Hmm i still can't turn it off. After holding the power button and waiting for the 3 buttons to flash, it would just reboot into the HTC screen. But it seems to be charging because when I booted into the bootloader just then, it doesn't say "power critically low" anymore.
By the way, whilst we're on the subject, do you know if it's possible to disable the ability to restart the phone by holding down the power button even when the phone is locked? I have quite a bulky case (from Ballistic) which makes the power button stick out a bit and sometimes when it's in my jeans and I kneel down to tie my shoelace, my leg would press into the button making the phone restart. This doesn't happen with the iPhone for example. on the iPhone, when the screen is locked, the power button doesn't give any response and even when the screen is unlocked, holding down the power button will only display the option to shut it off. This has always annoyed me on the One X (don't know if this is the case for other Android phones).
MarcusJKX said:
Hmm i still can't turn it off. After holding the power button and waiting for the 3 buttons to flash, it would just reboot into the HTC screen. But it seems to be charging because when I booted into the bootloader just then, it doesn't say "power critically low" anymore.
By the way, whilst we're on the subject, do you know if it's possible to disable the ability to restart the phone by holding down the power button even when the phone is locked? I have quite a bulky case (from Ballistic) which makes the power button stick out a bit and sometimes when it's in my jeans and I kneel down to tie my shoelace, my leg would press into the button making the phone restart. This doesn't happen with the iPhone for example. on the iPhone, when the screen is locked, the power button doesn't give any response and even when the screen is unlocked, holding down the power button will only display the option to shut it off. This has always annoyed me on the One X (don't know if this is the case for other Android phones).
Click to expand...
Click to collapse
very good now ur phone is charging and i hope u have flashed the boot.img too well i also have that issue with that button :/ but i keep the phone in the opposite direction like the headphone jack side goes inside pocket and the mic side is on the outside whn inside the pocket ....thats the only idea i use :/
ll_r1d0_ll said:
very good now ur phone is charging and i hope u have flashed the boot.img too well i also have that issue with that button :/ but i keep the phone in the opposite direction like the headphone jack side goes inside pocket and the mic side is on the outside whn inside the pocket ....thats the only idea i use :/
Click to expand...
Click to collapse
Yeah I guess that's the only solution then. Glad I'm not the only one!
I just got home and it looks like I was wrong. The phone's screen was off and no red LED lights were showing even though it's plugged into the wall. I disconnected it and waited a few seconds and then reconnected it and after a couple of minutes, the red LED came back but it also started up into the bootloader automatically...this thing just won't stay off!! I will see what happens after an hour or so but at the moment, I can't think of what else I can do to shut it off to charge it.
By the way, as I said earlier, I have now resetted everything, cleared everything and relocked my bootloader. Can I flash the unlock_code.bin I got previously from HTC or has my Token ID changed now and I need to obtain a new one? I did a Google search and it sounds like it will have now changed but I just wanna make sure.
EDIT: ok I need to go to bed now but I just realised that the reason why it won't switch off is BECAUSE it is plugged in. After unplugging it and selecting Power Down from the bootloader menu, it's now switched off. But as soon as i plug it in again, the screen lights up again. I guess i have to leave it like this and hope that it charges overnight but I'm a bit worried that it's not so good for the screen not to mention it seems to get a little warm after awhile. We'll see...
MarcusJKX said:
Yeah I guess that's the only solution then. Glad I'm not the only one!
I just got home and it looks like I was wrong. The phone's screen was off and no red LED lights were showing even though it's plugged into the wall. I disconnected it and waited a few seconds and then reconnected it and after a couple of minutes, the red LED came back but it also started up into the bootloader automatically...this thing just won't stay off!! I will see what happens after an hour or so but at the moment, I can't think of what else I can do to shut it off to charge it.
By the way, as I said earlier, I have now resetted everything, cleared everything and relocked my bootloader. Can I flash the unlock_code.bin I got previously from HTC or has my Token ID changed now and I need to obtain a new one? I did a Google search and it sounds like it will have now changed but I just wanna make sure.
EDIT: ok I need to go to bed now but I just realised that the reason why it won't switch off is BECAUSE it is plugged in. After unplugging it and selecting Power Down from the bootloader menu, it's now switched off. But as soon as i plug it in again, the screen lights up again. I guess i have to leave it like this and hope that it charges overnight but I'm a bit worried that it's not so good for the screen not to mention it seems to get a little warm after awhile. We'll see...
Click to expand...
Click to collapse
no u just have to use the old unlock unlock_code.bin ....just charge it for 1-2 hours only and flash the boot.img in the bootloader and your go to go
ll_r1d0_ll said:
no u just have to use the old unlock unlock_code.bin ....just charge it for 1-2 hours only and flash the boot.img in the bootloader and your go to go
Click to expand...
Click to collapse
Thanks a lot man. So turns out that once again, it wasn't actually charging and the phone was dead when I woke up. So then I found another thread where someone had a similar issue and this was suggested:
mevorach said:
Hi
I have a solution for you
make a batch file :
" @echo off
:start
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
goto start
"
put this file in the directory where you have fastboot.exe adb.exe and all other
files , also put the unlock.bin file that you have from htcdev
put your phone to bootfsatusb , and run the batch file , you will see the voltage
off the battry each time it loop , after an hour or two you will have enough power(~3.68mv) to unlock it , then charge it and do what ever you want
Click to expand...
Click to collapse
I did that and left it for a couple of hours and then the battery was at a high enough level for me to get to work again. I went through everything again remembering to flash the boot.img before flashing my new ROM and now everything is working perfectly! By the way, that guide written by hasoon2000 made a mistake I think. He said to flash the boot.img AFTER flashing the new rom which I did but then still got that com.android.phone problem. But then I flashed it again BEFORE flashing CM10.1 and now everything is smooth as butter.
Anyways, thanks all for your help. I really appreciate it!
MarcusJKX said:
Thanks a lot man. So turns out that once again, it wasn't actually charging and the phone was dead when I woke up. So then I found another thread where someone had a similar issue and this was suggested:
I did that and left it for a couple of hours and then the battery was at a high enough level for me to get to work again. I went through everything again remembering to flash the boot.img before flashing my new ROM and now everything is working perfectly! By the way, that guide written by hasoon2000 made a mistake I think. He said to flash the boot.img AFTER flashing the new rom which I did but then still got that com.android.phone problem. But then I flashed it again BEFORE flashing CM10.1 and now everything is smooth as butter.
Anyways, thanks all for your help. I really appreciate it!
Click to expand...
Click to collapse
glad to know that your htc one x is running like a fire well that method is just to show the current battery level nothing else ...and i had flashed the boot.img after the room but it worked for me cux i did fix permission wipe davlik cache and partition cache too...on some roms it works for me and on some roms it doesnt..well its better if you flash the boot.img before installing the room well um glad to help you and sort out your problem

[Q] HTC Inspire 4G bricked help!

Hi there, I have a HTC Inspire 4G phone that is not working anddont know what to do, Actually I have knowledge in samsungs only, (download mode recovery etc) but this phone does not turn on at all, after pressing the power button there is a little red led at the left and turns on and thats it, pressing power and vol - doesnt do anything,
When I plugged it in the computer after 5 mins around the computer recognizes an "android phone" or "my htc" nothing else happens.
when I leave the phone alone, suddently it turns on vibrating constantyl and shows a white screen with a HTC green logo but nothing else happens
:silly: this is crazy right? , please help
Dc-18 said:
Hi there, I have a HTC Inspire 4G phone that is not working anddont know what to do, Actually I have knowledge in samsungs only, (download mode recovery etc) but this phone does not turn on at all, after pressing the power button there is a little red led at the left and turns on and thats it, pressing power and vol - doesnt do anything,
When I plugged it in the computer after 5 mins around the computer recognizes an "android phone" or "my htc" nothing else happens.
when I leave the phone alone, suddently it turns on vibrating constantyl and shows a white screen with a HTC green logo but nothing else happens
:silly: this is crazy right? , please help
Click to expand...
Click to collapse
What happened before this?
Did someone try doing something like down grading?
Your symptoms sound like someone tried to flash a froyo ruu on a device that had gingerbread on it which means your bootloader is possibly messed.
Sent from my GT-I9505 using xda app-developerfs app
some time ago was rooted, a friend of mine tried to format it, he selected all the delete options, and then it did not continue to boot
Dc-18 said:
some time ago was rooted, a friend of mine tried to format it, he selected all the delete options, and then it did not continue to boot
Click to expand...
Click to collapse
I haven't the slightest what you're trying to say here.
bananagranola said:
I haven't the slightest what you're trying to say here.
Click to expand...
Click to collapse
the 1 post is the original and current problem..
Is your bootloader unlocked? Is it S-Off? Did you flash a custom ROM? Did you wipe /system? What exactly did you do to get it into that state?
bananagranola said:
Is your bootloader unlocked? Is it S-Off? Did you flash a custom ROM? Did you wipe /system? What exactly did you do to get it into that state?
Click to expand...
Click to collapse
Im not really sure if the bootloader is unlocked since I didnt use this phone before, but pressing power button + vol- doesnt do anything, my friend who is the owner said that the phone was rooted he wiped everything in the system options, after that the phone did not start anymore and got the problems mentioned before
He might of formated something for the phone to boot up properly, tryed flashing ruu or ADB(ANDROID DEVICE BRIDGE)
Sent from my Desire HD using XDA Premium HD app
JustPlayingHard said:
He might of formated something for the phone to boot up properly, tryed flashing ruu or ADB(ANDROID DEVICE BRIDGE)
Sent from my Desire HD using XDA Premium HD app
Click to expand...
Click to collapse
That may work, is there any thread to see how to do this? Thanks for your help guys
Dc-18 said:
pressing power button + vol- doesnt do anything
Click to expand...
Click to collapse
Did you do that when the phone was off?
bananagranola said:
Did you do that when the phone was off?
Click to expand...
Click to collapse
Yep, removed the battery and tried but doesn't do anything
Dc-18 said:
Yep, removed the battery and tried but doesn't do anything
Click to expand...
Click to collapse
Wait, you tried that when the battery wasn't in the phone?
bananagranola said:
Wait, you tried that when the battery wasn't in the phone?
Click to expand...
Click to collapse
Nup, of course when the battery was on the phone, what I meant is I removed the battery and insert it again and tried but didn't work
Dc-18 said:
Nup, of course when the battery was on the phone, what I meant is I removed the battery and insert it again and tried but didn't work
Click to expand...
Click to collapse
It didn't turn on? What did it do?
bananagranola said:
It didn't turn on? What did it do?
Click to expand...
Click to collapse
Nothing at all

Categories

Resources