After an update unsuccessful, my phone displays a list of problems:
1 - After upgrading unsuccessful. I tried to go back to Original ROM (STOCK), then came the first problem, the screen hangs after a few minutes, generating duplicate images or shuts off completely, but with some precionadas the power button, alloy display.
2 - When I turn on the computer, device is not accepted,adb not recognizing.
2.1 - I tried other machines, already reinstalled the drivers from htc, but the computer only recognizes the device as MY HTC or fastboot.
3 - The Cellular carries not more than 10%, it is restarting the 5 in 5 minutes.
4 - some times he connects with the lcd working, and I see that it goes up to the htc logo and hangs.
Well, these are the problems. If someone managed to revive your device, please help me.:crying::crying::crying::crying:
heber_cc said:
After an update unsuccessful, my phone displays a list of problems:
1 - After upgrading unsuccessful. I tried to go back to Original ROM (STOCK), then came the first problem, the screen hangs after a few minutes, generating duplicate images or shuts off completely, but with some precionadas the power button, alloy display.
2 - When I turn on the computer, device is not accepted,adb not recognizing.
2.1 - I tried other machines, already reinstalled the drivers from htc, but the computer only recognizes the device as MY HTC or fastboot.
3 - The Cellular carries not more than 10%, it is restarting the 5 in 5 minutes.
4 - some times he connects with the lcd working, and I see that it goes up to the htc logo and hangs.
Well, these are the problems. If someone managed to revive your device, please help me.:crying::crying::crying::crying:
Click to expand...
Click to collapse
could someone help?
What is your Hboot version, and what is your base version ? Don't panic, HTC One X is currently unbrickable.
Vcek said:
What is your Hboot version, and what is your base version ? Don't panic, HTC One X is currently unbrickable.
Click to expand...
Click to collapse
Official ICS rom 2.17.707.3 Asia WWE
after giving the above mentioned error, I tried to reinstall the official rom and could not longer access my mobile device: kernel, recovery, hboot and boot belong to this rom.
not the same but STILL PROBLEM
stock rom , relocked bootloader , voodo ota rootkeeper , BUT WONT UPDATE ( it starts good and at 1/3 stops with red triangle)
PPPPLLLLEEEAAASSSEEE!!!!!!!!!!!!!!:crying:
help!
heber_cc said:
Official ICS rom 2.17.707.3 Asia WWE
after giving the above mentioned error, I tried to reinstall the official rom and could not longer access my mobile device: kernel, recovery, hboot and boot belong to this rom.
Click to expand...
Click to collapse
heber_cc said:
After an update unsuccessful, my phone displays a list of problems:
1 - After upgrading unsuccessful. I tried to go back to Original ROM (STOCK), then came the first problem, the screen hangs after a few minutes, generating duplicate images or shuts off completely, but with some precionadas the power button, alloy display.
2 - When I turn on the computer, device is not accepted,adb not recognizing.
2.1 - I tried other machines, already reinstalled the drivers from htc, but the computer only recognizes the device as MY HTC or fastboot.
3 - The Cellular carries not more than 10%, it is restarting the 5 in 5 minutes.
4 - some times he connects with the lcd working, and I see that it goes up to the htc logo and hangs.
Well, these are the problems. If someone managed to revive your device, please help me.:crying::crying::crying::crying:
Click to expand...
Click to collapse
will be having someone who knows how I can solve the problem, or part of it?
When you said "reinstall the official rom" can you tell us how did you do that.
Was it you reflash your device with a RUU ? Or a nandroid backup ?
Please also tell us what is your hboot no. written on the bootloader.
Install the official rom without any modding. Then you can update.
Sent from my EndeavorU
Vcek said:
Install the official rom without any modding. Then you can update.
Sent from my EndeavorU
Click to expand...
Click to collapse
how can I update if the battery does not want to carry more than 10%, as pointed out just above.
Related
Hi!
First off, I've been searching for the answer all afternoon, but with no luck.
Here's the thing. My GF borrowed my friends old Desire, because her Legend broke.
When we tried to boot it up, it was stuck at the white HTC screen. So i entered Hboot and tried to use recovery with no luck. Recovery was also stuck at white screen.
My friend had removed his SD card before we borrowed the phone. Could that be the problem? Both me and my friend are pretty new to rooting/flashing. All the info he could give me, was that he was running some Modaco rom, and had used Unrevoked to root the phone.
I tried to download a Modaco rom and rename it PB99IMG.ZIP and putting it at the root of our own SD card. No luck.
Then i tried to put the update.zip (CWM file) with the hope that I could then load recovery. Also no luck.
Also tried to plug in USB cable, so that I could maybe wipe phone and install a new RUU. USB was recognized in Hboot (HBOOT USB PLUG status), but no access gained on the computer. I have manually installed drivers.
My friend lives a bit far away. So is there a way I can solve this without his SD card?
Thanks in advance!
- Rasmus, Denmark
Please send the bootloader info.
Sent from my customized HTC Desire using TTP
when you run a RUU bot into FASTBOOT USB. Turn it off and then hold BACK and POWER. then run the RUU.
need more help check my guide.
davebugyi > I hope this is the info you need :
BRAVO PVT1 SHIP S-ON
HBOOT-0.93.0001
MICROP-031d
TOUCH PANEL-SYNT0101
RADIO-5.10.05.23
Aug 10 2010, 17:52.18
bortak> Awesome guide, will check it out right away!
Okay, so now i followed bortaks guide. Created a gold card, downloaded latest recommended RUU, and then ran it while connected with fastboot usb.
At first i had problems when the RUU rebooted the bootloader. The phone shut down and disconnected instead of rebooting. Tried a few times, and finally got the installation to move on by keeping the phone "alive" through pressing vol buttons -although with a black screen.
But by 29%, while updating radio, the installation froze. After some time i unplugged USB and let the installation fail. So now I'm stuck with the four triangles with exclamation marks. I can run the RUU again and again, but it keeps freezing at various stages of installation.
What to do? It's not bricked, so there must be hope?
Can I take a different approach? Through ADB perhaps?
Thanks again!
RUU installation keeps freezing on my pc! Tried to click vol button to perhaps keep the phone "alive", but then I got error 155
Can't seem to find anything on Google about RUU installs that freezes - do any of you know what to do? Can't I use ADB or anything to flash the ROM?
evilution.dk said:
Okay, so now i followed bortaks guide. Created a gold card, downloaded latest recommended RUU, and then ran it while connected with fastboot usb.
At first i had problems when the RUU rebooted the bootloader. The phone shut down and disconnected instead of rebooting. Tried a few times, and finally got the installation to move on by keeping the phone "alive" through pressing vol buttons -although with a black screen.
But by 29%, while updating radio, the installation froze. After some time i unplugged USB and let the installation fail. So now I'm stuck with the four triangles with exclamation marks. I can run the RUU again and again, but it keeps freezing at various stages of installation.
What to do? It's not bricked, so there must be hope?
Can I take a different approach? Through ADB perhaps?
Thanks again!
Click to expand...
Click to collapse
oooh dear you shouldnt have disconnected it whist it was updating the radio.
i fear you may now have a radio brick
So I can have bricked the radio - but the phone will still respond?
evilution.dk said:
So I can have bricked the radio - but the phone will still respond?
Click to expand...
Click to collapse
unfortunately yes, if you unplug the phone and turn it on, it should boot in RUU mode, at what point does it say FAIL! ?
if it is on the radio, then I'm afraid it's bricked.. if you managed to luck out somehow and it isn't, then you could try again.
When i turn it on, the black splash screen with exclamation marks comes on. If i try to turn it on with usb cable plugged in while running XP mode on virtual machine, i see the white screen with version informations. But it only says RUU with an orange background.
Tried to install the new Gingerbread RUU from the HTC hp, but it still freezes. Think I'm out of luck
hmm... stick your phone in the freezer (in a plastic bag) for 5-10 minutes then try again.
I know it may sound strange.. but it may be overheating or something.
Whoever you borrowed this from will not be happy haha
Sent from my HTC Desire using XDA App
Which RUU are you trying to install?
I had the same issue when I realised I was trying to install a 2.1 RUU on my desire which was a bit silly, I had identical problems. used the correct 2.2 RUU and all ok
voodooboy3000 - Was trying to install official 2.3 Gingerbread RUU.
elliottg61 - It was crashing all the time when he had it, so he said i could have it if I could fix it. I couldn't
I would give the original firmware a go and get it back to stock. was it originally locked to a specific provider? if not use this RUU
http://forum.xda-developers.com/showthread.php?t=869048
Your not even s-off. How did he use anything to root. Granted my experience is with the bravoC. The GSM I'm sure is different. I would find the newest ruu available and try to flash that from hboot. If it takes forever go away. Don't touch it. Don't unplug it. Don't do anything till its done. If it wont flash after 30 minutes your screwed I think. U can try it over again. But if u have an official ruu it should flash no problem. If it gonna flash.
Try flashing a shooter port on the og evo, or flash a rom on the shooter. It can seem to hang on you for a while but it just takes time.
Edit: try this just rename it and stick on root of SD card and boot phone with volume down and power and then leave it be.
http://www.filefactory.com/file/b4a4027/n/RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
Sent from my PG86100 using XDA Premium App
evilution.dk said:
voodooboy3000 - Was trying to install official 2.3 Gingerbread RUU.
elliottg61 - It was crashing all the time when he had it, so he said i could have it if I could fix it. I couldn't
Click to expand...
Click to collapse
hahahahaha! gave you your first thanks because that made me laugh
Hello,
I know booting issues are possible when opening the bootloader and messing with kernels and rom flashing but that's not my case and I couldn't find a post that helped me so I hope someone can help me out on this.
I am a member of the HTC User Trial program and I'm currently testing the 3.09.401.100 Jelly Bean ROM, all stock, not rooted, never opened the bootloader or flashed any firmware besides official HTC RUU when OTA came out late (UK device, always last to get official OTA )
Last night I left my phone on before I went to sleep and it had low battery. This morning I tried to turn it on and it didn't work so I thought that the battery went out. Naturally, I plugged my phone to the charger and the red led didn't light red to indicate charging for a 30sec-1minute period, than it flashed red a few times and afterwards it lighted up red as if the phone was charging. I've left the phone turned off to charge for about 3.5 hours (even after the led turned green, just to get it really fully charged).
Now, when I try to turn the phone on, it get's stuck in the "HTC ONE" bootscreen with the beats audio logo at the bottom.
Long press on the power button reboots the phone but the issue repeats and the phone does not boot past the boot screen with the logo.
Couldn't attach my HBOOT photo so here's a link: https://www.dropbox.com/s/oxk8yz19ew0gi6s/hboot.jpg
Same
I'm having the same problem with an unlocked bootloader
sound weird...
you aways could try to do a factory reset from the bootloader, but should be considered a last resort since you memory will be wiped clean
Bram89 said:
sound weird...
you aways could try to do a factory reset from the bootloader, but should be considered a last resort since you memory will be wiped clean
Click to expand...
Click to collapse
Contacted HTC with this issue and they are not familiar with it as well. They have asked me to send a bugreport using ADB and told me that a factory reset may be required.
I will update if anything new pops up.
What is the starting of your device's serial number? if you don't mind (eg: mine are HW251XXXXXX)
Vcek said:
What is the starting of your device's serial number? if you don't mind (eg: mine are HW251XXXXXX)
Click to expand...
Click to collapse
HT23Y******* - Do you think it's related to my specific issue?
As for the problem itself, since I have all my important data backed up, I have done a factory reset and it sorted things out. No other solution from HTC in the meanwhile.
IdanK said:
HT23Y******* - Do you think it's related to my specific issue?
As for the problem itself, since I have all my important data backed up, I have done a factory reset and it sorted things out. No other solution from HTC in the meanwhile.
Click to expand...
Click to collapse
The problem is that I think that this leaked OTA was meant for some devices only (it contains "goldfish" libs not "endeavor") and 3 devices on this forum have reported incompatible hardware issues with the new hboot.
Are you sure you flashed boot.img from bootloader ? and how did you get into user trial program or where you randomly chosen ?
Vcek said:
The problem is that I think that this leaked OTA was meant for some devices only (it contains "goldfish" libs not "endeavor") and 3 devices on this forum have reported incompatible hardware issues with the new hboot.
Are you sure you flashed boot.img from bootloader ? and how did you get into user trial program or where you randomly chosen ?
Click to expand...
Click to collapse
I got the update directly from HTC as I'm a member on the User Trial program, no flashing what so ever, just plain OTA download & install.
I was chosen to participate in the User Trial program because I'm also a member on HTC Elevate and they asked users to join the program for testing One X software update.
Hey everyone,
I have read the various topics with a similar title but none helped.
Here is my problem, I bought a used HTC Desire on eBay. It booted just fine on the first start, then I did a factory reset (from within the Android system menu).
Since then, I'm stuck at the white screen with the green HTC logo. I have tried to get into bootloader mode by removing the battery, holding vol down and power, but it just goes straight to the white screen again.
Also connected the phone to the pc, but adb isn't picking up anything...
Any ideas?
Try Power+Back button.
just got one step further:
I can get into fastboot mode with BACK + POWER. But volume keys doesn't work, is that a known issue that I can solve somehow?
Goddchen said:
just got one step further:
I can get into fastboot mode with BACK + POWER. But volume keys doesn't work, is that a known issue that I can solve somehow?
Click to expand...
Click to collapse
So you bought a Desire with broken volume keys.
Are you s-off?
abaaaabbbb63 said:
So you bought a Desire with broken volume keys.
Are you s-off?
Click to expand...
Click to collapse
looks like...
in fastboot mode it shows that it is s-on.
Goddchen said:
looks like...
in fastboot mode it shows that it is s-on.
Click to expand...
Click to collapse
Then you'll have to flash a RUU to make it work.
http://forum.xda-developers.com/showthread.php?t=1772499
It's official HTC Firmware. Your phone will boot after this.
So:
1. Install HTC Sync.
2. Download and extract the RUU.exe from the zip (It's somewhere in there)
3. Run the exe while you connect your phone in fastboot (Power+Back)
4. Wait for it to install
5. Boot
abaaaabbbb63 said:
Then you'll have to flash a RUU to make it work.
http://forum.xda-developers.com/showthread.php?t=1772499
It's official HTC Firmware. Your phone will boot after this.
So:
1. Install HTC Sync.
2. Download and extract the RUU.exe from the zip (It's somewhere in there)
3. Run the exe while you connect your phone in fastboot (Power+Back)
4. Wait for it to install
5. Boot
Click to expand...
Click to collapse
Thanks for the advice, I downloaded the 2.3 RUU and it starts the process, sais
rebooting to bootloader
erasing data
sending...
and after ~30 seconds it just shows me a screen that sais "ERROR_UNKNOWN"
On the phone I see a black screen with a silver HTC logo during the process and when I unplug the USB cable after the error it shows the hboot screen that now sais "update failed".
right before the error is shown it display "updating signature"
Goddchen said:
right before the error is shown it display "updating signature"
Click to expand...
Click to collapse
It only says "Error_Unknown"? No error number, anything?
Weird.
This may be the reason:
Now, that may not sound too bad to some of you, but there's more: the 2.3 RUU update is limited regionally, as well. It's not available to users in Germany, North America, South America, South Korea, or Japan.
Click to expand...
Click to collapse
You live in Germany, right?
Use this guide then:
Section 2, S-on
http://forum.xda-developers.com/showthread.php?t=1275632
yes I am in Germany,
made some progress (or not?)
I noticed that the device was "unlocked", so I did "fastboot oem lock" and it was "relocked".
Then the RUU update went through - nearly. At the very end if failed again and now I am stuck at a black screen with the silver HTC logo and triangles in every corner.
AW: Unable to get into bootloader or recovery mode, stuck at white HTC logo screen
Sent from my Nexus 4 using xda app-developers app
wtf... tried again flashing the 2.3 RUU, this time it worked, YEAY
But now I have a bootloop, device starts, vibrates 1 time, waits for 3 seconds, and then vibrates 7 times. And restarts...
Ok. Tests are done.
According to the screenshot above and the 7 vibrations, you have a radio brick. It's a brick that can hardly be overcome.
The only solution is flashing the RUU and hoping that the phone will eventually boot.
That's why I don't buy second hand phones.
This thread might help:
http://forum.xda-developers.com/showthread.php?t=1793369
abaaaabbbb63 said:
Ok. Tests are done.
According to the screenshot above and the 7 vibrations, you have a radio brick. It's a brick that can hardly be overcome.
The only solution is flashing the RUU and hoping that the phone will eventually boot.
That's why I don't buy second hand phones.
This thread might help:
http://forum.xda-developers.com/showthread.php?t=1793369
Click to expand...
Click to collapse
freecer did it, was able to flash the 2.3 RUU again successfully. But now I'm back at the bootloop, but now, it simply does vibrate once (no more 7 vibrations) and reboots after some seconds.
So what can I do now? RUU flashed successfully, I'm running out of ideas...
and again the freezer did it, put it in, normally started via POWER button, it booted right through into Android.
Well, let's see if it keeps running now or if this overheating issue also exists in normal operation mode...
Thanks so much for you help so far, the freezer hint saved this device and hopefully will make my gf very happy tomorrow
Hold on I thought it was some pvt1 devices that had overheating issues.
Thought it was fixed on your newer ones. Then again I've never had a problem with my pvt1 desire flashed both hboot and find countless times.
Sent from my GT-I9100 using xda app-developers app
dethrat said:
Hold on I thought it was some pvt1 devices that had overheating issues.
Thought it was fixed on your newer ones. Then again I've never had a problem with my pvt1 desire flashed both hboot and find countless times.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
it is a PCT3 device.
but the overheating-reboot issue is rendering it useless. I can use it just fine outside (-2° currently) but as soon as I'm inside, boot-loop...
Anything I can do from a hardware perspective to fix that? Sending it in for repair/replacement is not an option, it's simply not worth the cost.
do you think installing a custom rom of any kind might help?
Goddchen said:
it is a PCT3 device.
but the overheating-reboot issue is rendering it useless. I can use it just fine outside (-2° currently) but as soon as I'm inside, boot-loop...
Anything I can do from a hardware perspective to fix that? Sending it in for repair/replacement is not an option, it's simply not worth the cost.
Click to expand...
Click to collapse
It's a motherboard fault. If you don't send it to repair, you just got yourself an "Ice-Phone", or a very complex paper holder.
i think a custom rom would help a small bit, like the rom in abaaaabbbb63 sig (mildwild redux) because its small and lite unlike a sense rom. therefor it mite not overheat as quick or as often. but thats only a guess. the only dodgy thing is trying to get ur phone s-off or rooted because if ur phone overheats in the middle of the s-off/rooting progress u could brick ur phone. plus charge ur phone using ur computer coz it uses less power and the phone does'nt heat up as much as plugging into the wall.
Hi, I've just registered in this forum, though I've been reading you guys for almost a year. I just want to say that you guys are awesome, i've learned too much about android because of you.
Introduction
Said that, I recently had a problem with my P350g, I'll try to be as clear as possible hoping you can help me out.
The problem came after i installed CM 9 [stable 8] on it, at first it worked perfectly (a very few panics or reboots but i'm used to it :laugh. The next day after taking a photograph the cellphone got stuck, it had done that several times before with some other ROMs so i didn't pay much attention to it, so i took the battery off and put it again, and when I tried to turn it on, there it was, the lg logo with the 4 softkeys blinking.
-- It doesn't enter to recovery (i had recovery installed at that time) pressing [- power send] at the same time, it just stays there with the lg logo blinking.
-- It does enter to the emergency mode (yellow background with "emergency mode" in black letters) pressing [+ - power] at the same time.
-- It does enter to the fastboot mode pressing [+ power send] at the same time.
what i've already tryed:
--- i've read the wiki about this phone and try everything there (and everything found on google which is pretty much the same)
http://forum.xda-developers.com/wiki/LG_Optimus_Me
--- i've tryed using the KDZ updater as somebody on this forum recommended:
http://multidroid2.feed.nu/2012/03/27/how-to-unbrickflash-your-optimus-melg-p350-2/
using firmware from here:
http://lg-phone-firmware.com/index.php?id_mod=5
and from somewhere else on the internet, the problem here is, that when it comes to "restart the phone", it doesn't start, it just keeps getting stuck on the lg logo with the 4 softkeys blinking, after some time the KDZ updater shows an error: Upgrade Error WParam: 100 LParam: 6
--- i've tryed flashing the recovery from fastboot mode as shown on this thread:
http://forum.xda-developers.com/showthread.php?t=2131247
it flashes well, everything "succeeded" but whe it comes to reboot (flashboot reboot) the cellphone says on the screen rebooting cellphone (or something like that) but it never reboots. if I take the battery off and put it on again, and then try to turn it on, the cellphone shows at the same problem, the lg logo with 4 softkeys blinking.
--- I've also tryed this tool:
http://forum.xda-developers.com/showthread.php?t=1948326
it hasn't solved my problem either.
Computers' info
I've tried this on 2 computers:
windows 7 x86
windows 8 x64
both of them have the drivers installed, I've disabled the modem on both of them, both of them have the latest android SDK tools
both computers give me the same problems, please i need your help, i'm desperate, I've been with this problem for several days and I can't solve it. I hope you can help me out
bump!
Anybody? please, i'm desperate
Hi,
Let's hope for the good
Try to flash the rom with fastboot.
and did you overclocked it too high? maybe your nand is burned?
kD said:
Hi,
Let's hope for the good
Try to flash the rom with fastboot.
and did you overclocked it too high? maybe your nand is burned?
Click to expand...
Click to collapse
thanks for answering, yes i did overclock it really high ~804MHz can't remember the exact number, but with other roms it had been working at that level of overclock without any problems (besides the casual panics and reboots) for more than half a year.
i'm going to try flashing the rom from flashboot and see what happens
I couldn't fash a rom via fastboot
IsraelMP said:
thanks for answering, yes i did overclock it really high ~804MHz can't remember the exact number, but with other roms it had been working at that level of overclock without any problems (besides the casual panics and reboots) for more than half a year.
i'm going to try flashing the rom from flashboot and see what happens
Click to expand...
Click to collapse
Hi everybody, i tried to flash a zip containing the rom on my p350, though i could not flash it. i used the command:
fastboot flash system rom.zip
but it says the file/rom size was smaller than expected. (honestly i can't remember the actual sentence) and then it says (x < y) where x is the suposed size of the rom and y is the expected size.
i tried with several roms, and a backup a user uploaded somewhere which was suposedly legitimate.
Is there something i can do?
download lg mobile support tool (lg mobile updater)
make sure that the driver is installed on the computer
open it
let it reconize the phone then
click recover phone from CS
the phone will be returned to latest stock rom for your country
then intsall recvoery again and root again
My Method
Well you need usb debugging enabled.Remove phone's batytery and connect it to pc via usb.It will boot up (horribly of course ignore it).Then fire up the kdz updater and start the flashing process.Once the phocess starts midway anywhere in the process insert the battery.The process will complete then KDZ will sat update complete...REBOOTING....and as battery is inserted it will reboot.Voila.Hope it works for you.This is my routine method.(Bricked more than 7 times lol).
Thanks for replying
MeeDa said:
download lg mobile support tool (lg mobile updater)
make sure that the driver is installed on the computer
open it
let it reconize the phone then
click recover phone from CS
the phone will be returned to latest stock rom for your country
then intsall recvoery again and root again
Click to expand...
Click to collapse
thanks for replying, i did that, when i just plug it without pressing any button the cellphone does not get recognized by the software, when i plug it in emergency mode it does get recognized but the software gives me an error.
blazecodester said:
Well you need usb debugging enabled.Remove phone's batytery and connect it to pc via usb.It will boot up (horribly of course ignore it).Then fire up the kdz updater and start the flashing process.Once the phocess starts midway anywhere in the process insert the battery.The process will complete then KDZ will sat update complete...REBOOTING....and as battery is inserted it will reboot.Voila.Hope it works for you.This is my routine method.(Bricked more than 7 times lol).
Click to expand...
Click to collapse
thanks for the answer, I tried that way, though it keeps getting stuck in the LG logo with the 4 blinking softkeys when it comes to reboot the cellphone.
HELP!
I tried to flash RUU, end up failed!
After that my M8 unable to boot(normal boot, recovery, any...), I tried abd and fastboot command, it doesn't work.
I tried anything I can, but still black screen, not any HTC logo.
Please help:crying:
tsanren89 said:
HELP!
I tried to flash RUU, end up failed!
After that my M8 unable to boot(normal boot, recovery, any...), I tried abd and fastboot command, it doesn't work.
I tried anything I can, but still black screen, not any HTC logo.
Please help:crying:
Click to expand...
Click to collapse
You have HTC black screen with 4 (!) points in corners?
Just rerun RUU again, make sure its the correct RUU *& short data cable.
RUU(.exe from computer) should still run with this screen on
Opps sorry did not see the HTC logo was not there until posted!!!
Ahhhhhhhhhhhhhhh
Sent from my HTC One_M8 using Tapatalk
crackerjack1957 said:
You have HTC black screen with 4 (!) points in corners?
Just rerun RUU again, make sure its the correct RUU *& short data cable.
RUU(.exe from computer) should still run with this screen on
Opps sorry did not see the HTC logo was not there until posted!!!
Click to expand...
Click to collapse
Just black screen without any (!) points. :crying:
tony_5309 said:
Ahhhhhhhhhhhhhhh
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Any solution ?
Leave it to a wall charger for a few hours.
Later press & hold all power+vol up+vol down buttons for about 3 minutes and advise the outcome.
Which RUU that you flashed ? What's your firmware no. ?
I was trying to update to firmware 6.20.651.3 updated successfully
x3r0k said:
I was trying to update to firmware 6.20.651.3 updated successfully
Click to expand...
Click to collapse
I have the same problem, were you able to solve this problem?
funjai said:
I have the same problem, were you able to solve this problem?
Click to expand...
Click to collapse
Just posting you have the same problem, is not enough info, and is never the right way to post.
You were updating firmware 6.20.651.3, it was successful and now the screen is dark and the device won't boot?
You have the Sprint version phone?
Or did you not even mean to quote the previous post referencing firmware 6.20.651.3; and just have the black screen problem?
Its not clear if you give zero details. Nor is it possible for us to give you much help.
Describe your issue in detail: what version of the M8 you have, what Android version, what was happening when the issue occurred. What things you have tried so far. Describe everything specifically, step by step; and provide as much detail as possible.
redpoint73 said:
Just posting you have the same problem, is not enough info, and is never the right way to post.
You were updating firmware 6.20.651.3, it was successful and now the screen is dark and the device won't boot?
You have the Sprint version phone?
Or did you not even mean to quote the previous post referencing firmware 6.20.651.3; and just have the black screen problem?
Its not clear if you give zero details. Nor is it possible for us to give you much help.
Describe your issue in detail: what version of the M8 you have, what Android version, what was happening when the issue occurred. What things you have tried so far. Describe everything specifically, step by step; and provide as much detail as possible.
Click to expand...
Click to collapse
Yes, you are right, I'm sorry. So here's the full story. Friend of mine gave me his HTC One M8S, it was stuck in recovery. Here are the first screenshots:
https://postimg.cc/image/kp35x8n9z/
https://postimg.cc/image/p61e8t837/
After that I unlocked the bootloader and installed TWRP (i think it was 2.8.6.0). Then I tried to restore it to stuck ROM, I found this thread:
http://forum.xda-developers.com/htc...lp-thread-htc-one-m8s-to-stock-howto-t3190238
So when I tried to do that (I used HTC Europe 1.03.401.11 image), update started just fine, after some time my device just shuts down (it was connected to charger so It was not that battery was dead) and after that I was unable to turn it on.
When I connect my HTC m8s to charger red led light is blinking, but the phone is not turning on. When I connect my phone to pc, fastboot and adb are not working, strange thing is that my pc is recognizing my phone like unidentified device.
So any ideas? Is my phone gone?
Thx
funjai said:
So when I tried to do that (I used HTC Europe 1.03.401.11 image), update started just fine, after some time my device just shuts down (it was connected to charger so It was not that battery was dead) and after that I was unable to turn it on.
When I connect my HTC m8s to charger red led light is blinking, but the phone is not turning on. When I connect my phone to pc, fastboot and adb are not working, strange thing is that my pc is recognizing my phone like unidentified device.
So any ideas? Is my phone gone?
Click to expand...
Click to collapse
Try charging it for a few hours. Then hold power+vol up for a minute or so, and see if its boots at all (at least to the bootloader screen).
Neither fastboot nor adb will not work when the device is powered down like this.
I tried that already, still nothing..