Develop Bugs

EVO 4G stuck at htc 4g splash screen - I searched for 2 days!!!

Hey guy's, well first off I just want to say I'm a big fan of android and especially xda-developers and all the helpful people on this site. I'm having a pretty big issue, one that I searched for a solution for 2 days now using the search function on here as well as google and many others available and I'm in a corner. I have an EVO 4G I bought from someone off craigslist and everything was fine for 3 weeks then 3 days ago the phone died and i plugged it in with no led light showing the charging status. I thought perhaps it was a bad battery so I bought another battery and with the little life the new battery has it turned on and got stuck on the HTC EVO 4G splash screen.
So I pulled the battery out and re-installed and booted into the bootloader menu only to find out more bad news. When I try to boot into recovery from the bootloader menu it goes to the HTC EVO 4G splash screen and stays there forever. I have tried to clear storage, in which it clears and says everything is ok reboots into the HTC EVO 4G splash screen and gets stuck again, So I'm really concerned now and I cant find a solution anywhere I've tried several different methods to flash amon RA recovery, I downloaded the zip file and changed the name accordingly so the bootloader menu would automatically recognize it and it said installed successfully but still to no avail, and I do not believe I am able to manually flash another recovery method because I cannot get into usb debuggine mode from the phone so I'm not sure how adb would even begin to recognise the phone.......... someone for love of all things fancy please help me!!!! I'm struggling!!! lol

Also this is what appears on my bootloader menu:
supersonic EVT2-3 SHIP S-OFF
HBOOT-2.02.0000
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.09.01

If u can boot into recovery u can mount SD card to put a new rom on it. Wipe everything except ur SD card n flash new rom
Sentt from mmy pockett

{ParanoiA} said:
If u can boot into recovery u can mount SD card to put a new rom on it. Wipe everything except ur SD card n flash new rom
Sentt from mmy pockett
Click to expand...
Click to collapse
I cannot boot into recovery

If you have a card reader,you should be able to download a Rom,put it in the root of your sd card,rename it pc36img.zip,put it back in your phone and flash it through the bootloader.
Sent from my PC36100 using XDA App

BrianBusby2038 said:
If you have a card reader,you should be able to download a Rom,put it in the root of your sd card,rename it pc36img.zip,put it back in your phone and flash it through the bootloader.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I have already attempted this method twice but I'll give it another shot

Try running RUU update. Download here:
OTA 3.70
http://www.megaupload.com/?d=86NCAM22
Link grabbed from PPCGEEKS user KarlE
this will revert you back to android 2.2, but this should fix your problem.

munesh23 said:
Try running RUU update. Download here:
OTA 3.70
Link grabbed from PPCGEEKS user KarlE
this will revert you back to android 2.2, but this should fix your problem.
Click to expand...
Click to collapse
Ok thanks I'll give it a shot any chance you could tell me the best way to apply the RUU update? name change to PC23IMG??

STRteg said:
Ok thanks I'll give it a shot any chance you could tell me the best way to apply the RUU update? name change to PC23IMG??
Click to expand...
Click to collapse
all you have to do is download that file and execute it in windows then just follow the instructions.

munesh23 said:
all you have to do is download that file and execute it in windows then just follow the instructions.
Click to expand...
Click to collapse
downloaded the file and executed it in windows and it reboots the phone from bootloader to bootloader again but phone never comes back on...

Do this, in this order...
Charge battery to full (since there's no way for you to tell how much charge there is you might as well be sure it's full...)
Boot to Bootloader
Select FASTBOOT with volume up/down
Press Power button to go into FASTBOOT
Plug phone in to PC
Run RUU.

Unknownforce said:
Do this, in this order...
Charge battery to full (since there's no way for you to tell how much charge there is you might as well be sure it's full...)
Boot to Bootloader
Select FASTBOOT with volume up/down
Press Power button to go into FASTBOOT
Plug phone in to PC
Run RUU.
Click to expand...
Click to collapse
Hey I tried this method and all was well for the most part and then the executable ruu said that it could not continue because my battery was less than 30% and my phone won't charge for some strange...

STRteg said:
Hey I tried this method and all was well for the most part and then the executable ruu said that it could not continue because my battery was less than 30% and my phone won't charge for some strange...
Click to expand...
Click to collapse
The phone doesn't charge in bootloader, turn the phone off and leave it on the charger when it's OFF until the light goes green, then start over.

Unknownforce said:
The phone doesn't charge in bootloader, turn the phone off and leave it on the charger when it's OFF until the light goes green, then start over.
Click to expand...
Click to collapse
Phone is not charging when it's off or at least there is no led lit up or anything

STRteg said:
Phone is not charging when it's off or at least there is no led lit up or anything
Click to expand...
Click to collapse
Then it's possibly a bad battery or simply a brick now, because if you can't charge it normally, doing anything to get it working again is futile... If you have another battery try that, or if you can take it to a shop and try one of their batteries in it... That's all I can think of doing...

Unknownforce said:
Then it's possibly a bad battery or simply a brick now, because if you can't charge it normally, doing anything to get it working again is futile... If you have another battery try that, or if you can take it to a shop and try one of their batteries in it... That's all I can think of doing...
Click to expand...
Click to collapse
Well I don't think its a complete brick just yet the usb port can't be bad if fastboot reads the pc when connected and vice versa, however I went to frys and bought a universal battery charger and am charging the battery to full right now. I'll let you know something soon thanks for all your help so far.

Ok so I let the battery charge, re-installed and ran the RUU executable file it flashed and installed successfully but is at the same place still gets stuck on htc evo 4g screen

What Rom and kernel were you on when you discovered it at white screen.
Also, did you just find it at the splash screen? or did it random reboot or just not boot?

Zac95 said:
What Rom and kernel were you on when you discovered it at white screen.
Also, did you just find it at the splash screen? or did it random reboot or just not boot?
Click to expand...
Click to collapse
Stock as far as I know and the phone died and when i went to recharge it and discovered the white splash screen

Ok I'm really stuck nothing is working for me the RUU ran and flashed properly just to get back stuck at the htc evo 4g screen again I was reading somewhere else that it needs to read S-ON on bootloader to flash the OTA RUU is this correct? and if so how can I change it with unrevoked if I cant get adb to recognize the device?

[Q] One X Stuck at bootloader

Hi all. I hope some kind person here can help me get to the bottom of this.
I unlocked my bootloader earlier from htcdev. I then installed super user.
I wanted to install Leedroid ROM so downloaded the files and used fasboot to install the version of boot.img that comes with it. Problem is that I forgot to transfer over the rom zip file to the device before doing it so now I'm stuck. I know, I just got distracted. My fault I know. I just feel totally sick at the thought of just having bought a £450 to have broken it less than a week later.
(I have successfully rooted my old desire and a wildfire in the past without bother so I do have experience of rooting....just looking like and feeling like an idiot now!)
I had a nandriod backup done from before flashing boot.img and tried to restore.. It says restore was successful but it got stuck on the HTC splash screen. Some help would be mighty appreciated.
The bootloader is now locked again but I think I still have CWM recovery installed however I can't access it any more. The phone boots directly into the bootloader and doesn't attempt to boot.
I've tried unlocking the bootloader again but now it says the battery is too low. I keep trying to turn the phone off in fastboot to let it charge but it just starts up again? Any Ideas?As I said I can't get it to charge so I can't unlock the boot loader again. I've tried running stock 1.29 RUU but again not enough juice.
Just to confirm: My HBOOT is 0.94.0000; The bootloader is relocked.
Any help would be very appreciated, I am at my wits end. Thanks in advance

http://forum.xda-developers.com/showthread.php?t=1546970
Try that. download and extract boot.img and then flash the boot.img that should then work. If not try looking for stock roms that are flashable through clock work mod and get hold of that boot.img. hope this helps
Sent from my HTC One X using XDA Premium HD app

Also if you got cwm you can go into it and charge the phone from there
Sent from my HTC One X using XDA Premium HD app

This is just a thought, maybe when the battery dies the phone will switch off on its own, and then u can charge it.

malcovitch said:
Also if you got cwm you can go into it and charge the phone from there
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for all the replies. Unfortunately, I can no longer access CWM. When I go to recovery it shows the "Quietly Brilliant" Screen then goes to fastboot menu, no CWM?

UPDATE: Ok, I have managed to unlock my bootloader again. In another thread mevorach advised running a batch script that displays the voltage and reboots the phone. Id created this script and waited until the phone charged up enough, then I ran the unlock command again.
I now have access to CWM again. Feels like I'm starting to get somewhere.
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

cosmicovertones said:
Thanks for all the replies. Unfortunately, I can no longer access CWM. When I go to recovery it shows the "Quietly Brilliant" Screen then goes to fastboot menu, no CWM?
Click to expand...
Click to collapse
That's because of low battery.
have you read this : http://forum.xda-developers.com/showthread.php?t=1609190
which recovery version that you have ? If it is 5.8.3.1, what you can try is:
attach the charger to it's usb.
the phone will boot to bootloader
scroll to power down
it will shut down
don't take out the usb cable/charger from the phone.
if the phone starts again to bootloader
scroll again to power down
(normally it will stay shut down when doing this power down the second time)
let it charge for an hour.
on PC get ready the fastboot command to unlock the bootloader
fastboot flash unlocktoken Unlock_code.bin and enter
status will show waiting for device
connect your phone and power on
and see whether the "low battery" warning still there.
if successful, unlock the phone (choose yes)
when it reboot - hold power + volume down to force it to bootloader
fastboot flash boot boot.img for the nandroid backup that you restore earlier
once done reboot the phone.
---------- Post added at 02:45 PM ---------- Previous post was at 02:43 PM ----------
cosmicovertones said:
UPDATE: Ok, I have managed to unlock my bootloader again. In another thread mevorach advised running a batch script that displays the voltage and reboots the phone. Id created this script and waited until the phone charged up enough, then I ran the unlock command again.
I now have access to CWM again. Feels like I'm starting to get somewhere.
Click to expand...
Click to collapse
that's good.
what you need now is to flash the boot.img for the nandroid backup that you have which you mentioned you restored earlier. without a correct boot.img for your nandroid backup, you will stuck on "quietly brilliant"

Thanks for your reply,
ckpv5 said:
That's because of low battery.
have you read this : http://forum.xda-developers.com/showthread.php?t=1609190
Click to expand...
Click to collapse
Yes, I've gone through all the pages.
ckpv5 said:
which recovery version that you have ? If it is 5.8.3.1, what you can try is:
Click to expand...
Click to collapse
When I managed to get into CWM I realised I was not on the latest, I have now managed to flash 5.8.3.1
ckpv5 said:
attach the charger to it's usb.
the phone will boot to bootloader
scroll to power down
it will shut down
don't take out the usb cable/charger from the phone.
if the phone starts again to bootloader
scroll again to power down
(normally it will stay shut down when doing this power down the second time)
let it charge for an hour.
on PC get ready the fastboot command to unlock the bootloader
fastboot flash unlocktoken Unlock_code.bin and enter
status will show waiting for device
connect your phone and power on
and see whether the "low battery" warning still there.
if successful, unlock the phone (choose yes)
Click to expand...
Click to collapse
I have managed to get to this step.
ckpv5 said:
when it reboot - hold power + volume down to force it to bootloader
fastboot flash boot boot.img for the nandroid backup that you restore earlier
once done reboot the phone.
that's good.
what you need now is to flash the boot.img for the nandroid backup that you have which you mentioned you restored earlier. without a correct boot.img for your nandroid backup, you will stuck on "quietly brilliant"
Click to expand...
Click to collapse
I tried to restore the boot.img that backed up earlier but it is getting stuck at the "quietly brilliant" screen.
I also tried to restore all of the nandroid backup without success.
Any ideas how I can get a working boot.img to flash?
I am currently leaving the phone on the "quietly brilliant" screen (the charge LED is on) to see if I can get enough charge to restore the stock recovery, lock the bootloader and flash the 1.29 europe RUU. Is this a good plan or should I be trying something else?

Based on my experience, when you're not sure which boot.img belongs to which nandroid, a stock boot.img will work.
But if that also fail then the next best thing to do is flash RUU and make sure you have the right official RUU for your phone. Wrong RUU will not work.

Ok, will do. Thanks for the help
I'm trying to leave the phone on charge for a couple of hours, I'll then try flash the boot_signed.img file from the RUU.zip andfailing that I'll try the whole RUU.

Same situation here...
cosmicovertones said:
I'm trying to leave the phone on charge for a couple of hours, I'll then try flash the boot_signed.img file from the RUU.zip andfailing that I'll try the whole RUU.
Click to expand...
Click to collapse
I'm having the exact same problems, and have pretty much done the same steps in my attempts to get the phone back to life. Current status is that it's locked and can't unlock it due to low battery, but that .bat file seems to be helping - battery voltage is going up, so eventually I should be able to do something.
My plan however is to try RUU (tried everything else already, when I had battery and the phone was unlocked and had clockworkmod).
Anyway please keep this thread up to date with your progress.
If you broke your phone in the first week...well, I opened the box of mine 15 minutes before bricking it, hadn't even installed the SIM card (I bought it from an amazon seller and he sent me the Asian version, Thai keyboard and all - that's what started all this).

Ok... so I flashed the boot_signed.img file from the official 1.29 ruu. The phone then rebooted and again froze on the "quietly brilliant" screen. I then locked the bootloader again and rebooted. This time it booted fine
Once booted I left it to charge fully, I then was able to run the 1.29 RUU for my phone.
Next step I unlocked the bootloader again and flashed CWM 5.8.3.1. Performed a nandroid backup and flashed the super user zip file.
It is fully functioning up to this point now.
My next step is to follow ALL the steps (this time lol) to get leedroid one xtreme v5 rom installed again.
I'm getting the phone back to 100% charge before doing the next steps, just incase I need to undo anything I REALLY don't want to run into the low battery issue again.

cfsmp3 said:
I'm having the exact same problems, and have pretty much done the same steps in my attempts to get the phone back to life. Current status is that it's locked and can't unlock it due to low battery, but that .bat file seems to be helping - battery voltage is going up, so eventually I should be able to do something.
My plan however is to try RUU (tried everything else already, when I had battery and the phone was unlocked and had clockworkmod).
Anyway please keep this thread up to date with your progress.
If you broke your phone in the first week...well, I opened the box of mine 15 minutes before bricking it, hadn't even installed the SIM card (I bought it from an amazon seller and he sent me the Asian version, Thai keyboard and all - that's what started all this).
Click to expand...
Click to collapse
As the earlier quote regadring the bat file, you will have enough power(~3.68mv) to unlock it. Once it gets to ~3.689mV you will be able to unlock the phone.
Did you have it unlocked at one point? If so you can use the same unlock file HTC sent you to unlock again.
Once you have it unlocked run the bat script again until the power is around the same level again, then flash cwm 5.8.3.1 through fastboot.
Once you have this you can turn the phone off and plug it into your charger. I had mine plugged in for over an hour. The charge was then enough to flash the boot_signed.img file from the RUU for my phone, and as I said it booted fine.
Hope this all helps, I know exactly how you feel.
My killer mistake was forgetting to transfer the leedroid rom zip to the phone and I wrongly assumed CWM could mount the internal storage as USB to transfer the rom to the phone; like earlier versions.

cosmicovertones said:
Ok... so I flashed the boot_signed.img file from the official 1.29 ruu.
Click to expand...
Click to collapse
Where did you get that file? Digging into %TEMP% or is there an official repository or something?
Why not install the full RUU, by the way, to start over?
Anyway your post gives me hope I'm currently letting the .bat file run - but the plan was to do RUU if at all possible, rather than unlock, add clockworkmod, etc...

I couldn't get it to charge much higher than was required to unlock etc.. so I needed to get CWM installed to get it to charge properly.
Also, I couldnt get the boot_signed.img to flash I assume cause the bootloader is locked.
I got the boot_signed.img by opening the RUU installer but not clicking next just having it open.
Then I got the temp folder on my pc and searched in it for zip files. Only 2 appeared. The rom was called "rom.zip"
I then copied this to my desktop and opened the zip. Then I was able to extract the boot_signed.img file to the fastboot folder on my pc and got it flashed across.
I think you're probably gonna have to unlock the bootloader to fix your problem.

cosmicovertones said:
I couldn't get it to charge much higher than was required to unlock etc.. so I needed to get CWM installed to get it to charge properly.
Click to expand...
Click to collapse
I got some help in IRC on the charge front. Indeed powering off the phone from the FASTBOOT menu *without* having a cable plugged in (otherwise the damn thing won't stay off) puts it in a chargeable state. What I did was plug it in the wall charger for a bit. Then they suggested that when the phone is off you can plug it to the PC and get battery status with adb, which I did - like this:
adb shell cat /sys/class/power_supply/battery/status
adb server is out of date. killing...
* daemon started successfully *
Charging
adb shell cat /sys/class/power_supply/battery/capacity
30
[plugged again to wall charger for a while]
adb shell cat /sys/class/power_supply/battery/capacity
42
So it's looking good. I'll let it charge for a while and once it's done, relock (I just installed cwm again), and try RUU.
cosmicovertones said:
I got the boot_signed.img by opening the RUU installer but not clicking next just having it open.
Then I got the temp folder on my pc and searched in it for zip files. Only 2 appeared. The rom was called "rom.zip"
Click to expand...
Click to collapse
OK, I just did and saved the file somewhere in case it's needed.
We'll see

for the RUU to run successfully you need to flash the stock recovery (to get rid of CWM) and lock the bootloader AFTER you've flashed the boot_signed.img file. This is to get the RUU to run on an unmodified phone.
Once you get that run you can re unlock, flash CWM and super user binaries if you want.
After this experience, I'll be checking and double checking the steps provided in future. What an ass I am!!! ha just goes to prove just cause I was successful on my old htc desire and the gf's wildfire it's no guarantee I know what I'm doing
Also, I've now successfully installed Leedroid One Xtremem V5.1. Just after restoring my apps using titanium backup.
Let me know how you get on
EDIT: I think the reason I had to flash the boot_signed.img file is because I flashed the leedroid boot.img then realised my mistake of not having the rom to flash and to compound the issue relocked the bootloader and the low battery. You might be able to get away with charging and running your RUU. If that fails I would restore stock recovery, lock the bootloader and retry the RUU

cosmicovertones said:
for the RUU to run successfully you need to flash the stock recovery
Click to expand...
Click to collapse
Nope It just needs to be locked, but it was happy to run with cwm installed.
So I got it to work (back to square one, because I still need to change the ROM). I actually did more stuff than needed (because I was trying two approaches as the same time), but in summary:
- That glorious 5 line .bat file works, and allows the battery to charge, so reach a state where you can at least lock/unlock and flash. For me the battery changes from 'low charge' to 'good' at 3615mV.
- You can also turn the phone off from the service menu, but you have to be sure no cable is plugged, or it will turn itself back on in a couple seconds.
- The battery charges if the phone is off, using a wall charger.
- With the phone off, you can still plug in on a PC and find battery status (whether it's charging or not) and current charge (in %) with adb (another command line tool, like fastboot).
- With 30% or more of load, you can run RUU and get the phone back to factory state.
- You can't use a RUU for a different model, if your model is from Asia you need the Asian RUU, you can't just install a European one. You don't like a Vietnamise keyboard? Tough ****.
Anyway, since I know have all the tools and more confidence I'll just go ahead and try again. Starting will a full charge of course

Awesome!! I'm glad you got it to work, and I hope this thread serves as some help for others.
The damn battery charge issue had me worried. That bat file is really a lifesaver!

Thanks for all the info. Hope not to need it but mistakes can be made.

[Q] Please Help! My HTC is encountering serious problems!

Ok so here's what i did.
I rooted the phone, installed the CWM Recovery and everything.
Next I installed the Android Revolution HD Rom 7.1.0 by doing the "Super Wipe".
It got into boot loops
Then after factory resetting and every other things I could do I tried to do the new RUU on my O2 HTC One X Unlocked.
For that you have to Re-Lock it (which I did)
And I cant go into any of the Fastboot settings etc too because its battery level is very low.
Please someone help me. I just bought this phone

WasifSal said:
Ok so here's what i did.
I rooted the phone, installed the CWM Recovery and everything.
Next I installed the Android Revolution HD Rom 7.1.0 by doing the "Super Wipe".
It got into boot loops
Then after factory resetting and every other things I could do I tried to do the new RUU on my O2 HTC One X Unlocked.
For that you have to Re-Lock it (which I did)
And I cant go into any of the Fastboot settings etc too because its battery level is very low.
Please someone help me. I just bought this phone
Click to expand...
Click to collapse
go into fastboot, flash the new recovery, boot into recovery, and let it charge. then do watever u want
Sent from my HTC One X using Tapatalk 2

Kevin Ma said:
go into fastboot, flash the new recovery, boot into recovery, and let it charge. then do watever u want
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I Re-Locked the phone
Will that flash the Recovery?

WasifSal said:
I Re-Locked the phone
Will that flash the Recovery?
Click to expand...
Click to collapse
unlock the phone again. flash the latest recovery. then go into fastboot. fastboot erase cache , then flash the kernel, go into recovery flash superwipe, flash rom and reboot and job done..
before you do all that though backup your current rom

I cannot go into the fastboot and do the stuff because it prompts me that I have less battery. There's another problem that the phone doesn't shut off. When it gets out of juice then it turns black, the notification light blinks then when its charging, it loads the Bootloader. It simply just doesn't turn off and that leads to the problem that it uses up the battery much more than the required :/
I've tried powering down from the menu but no use

WasifSal said:
I cannot go into the fastboot and do the stuff because it prompts me that I have less battery. There's another problem that the phone doesn't shut off. When it gets out of juice then it turns black, the notification light blinks then when its charging, it loads the Bootloader. It simply just doesn't turn off and that leads to the problem that it uses up the battery much more than the required :/
I've tried powering down from the menu but no use
Click to expand...
Click to collapse
well then leave it overnight to charge..see what happens in the morning then

Goku80 said:
well then leave it overnight to charge..see what happens in the morning then
Click to expand...
Click to collapse
You see the problem isn't that simple :'(
the phone in the end gets totally low on battery cuz its being gulped faster (cuz the screen is lit and can't turn off)

WasifSal said:
You see the problem isn't that simple :'(
the phone in the end gets totally low on battery cuz its being gulped faster (cuz the screen is lit and can't turn off)
Click to expand...
Click to collapse
man i am sorry then i wish i had more knowledge to give you help. hopefully someone else with more experience and knowledge can come and advise you different. just never had that issue you see.
if you say you can not go into bootloader or recovery then it does not sound right...maybe take it back to retailer or something might be the best option if no one can help out
have you tried the power button with the volume button down for ten seconds to see if the phone reboots?

Can anyone tell me the solution to this "keep turning on" habit. If that's resolved there's nothing to it then. Please help me out here :'(

WasifSal said:
Can anyone tell me the solution to this "keep turning on" habit. If that's resolved there's nothing to it then. Please help me out here :'(
Click to expand...
Click to collapse
try what i said to you in my last sentence mate

Have a look here:
http://forum.xda-developers.com/showthread.php?t=1609190

PatsFan1286 said:
Have a look here:
http://forum.xda-developers.com/showthread.php?t=1609190
Click to expand...
Click to collapse
OK so I managed to get the phone UNLOCKED (Finally)
Now when I flash the 5.8.4.0 recovery it says
"unknown partition 'recovery-clockwork-touch-5.8.4.0-endeavoru.img'
error: cannot determine image filename for 'recovery-clockwork-touch-5.8.4.0-end
eavoru.img'"
So i booted the phone into the recovery mode instead of flashing.
I am finally getting somewhere but how do i know it's charging there? I don't see the red LED turn ON :/

LATEST UPDATE:
So when I unlocked the bootloader again. Apparently that solved the "not turning off" habit of the phone.
I went into the bootloader and Power Down my phone, Now it's on charge (waiting for it to turn green)
And I have the O2 branded HTC One X. I also updated it to the 1.29.206.XX something.. I don't remember :/
And I only see one RUU for the O2 branded Phone and that is like 1.26.XXX.XX thing... Will that cause problems since I upgraded the firmware??

WasifSal said:
LATEST UPDATE:
So when I unlocked the bootloader again. Apparently that solved the "not turning off" habit of the phone.
I went into the bootloader and Power Down my phone, Now it's on charge (waiting for it to turn green)
And I have the O2 branded HTC One X. I also updated it to the 1.29.206.XX something.. I don't remember :/
And I only see one RUU for the O2 branded Phone and that is like 1.26.XXX.XX thing... Will that cause problems since I upgraded the firmware??
Click to expand...
Click to collapse
Why is it so hard for guys to flash roms. Man its getting old seeing 50,000 of the same threads over and over.
Ok on to helping
You have latest recovery. So boot to fastboot & flash the roms boot.IMG ( fastboot flash boot boot.img) now unplug the phone, press the power button. Now your back in hboot select recovery,once there click mounts & storage button , mount USB drive. Now copy the Rom to your phone. Unmount USB drive, now flash super wipe script. BUT DON'T REBOOT AFTER YOU FLASH THIS!!!!!! choose option to select another zip to flash. This time flash your Rom & reboot. Now your done. Simple huh. & to answer your ruu ?, you can't downgrade ruu's if your on 1.29, your stuck with it till a newer one comes out.
Sent from my HTC One X using xda premium

rayford85 said:
Why is it so hard for guys to flash roms. Man its getting old seeing 50,000 of the same threads over and over.
Ok on to helping
You have latest recovery. So boot to fastboot & flash the roms boot.IMG ( fastboot flash boot boot.img) now unplug the phone, press the power button. Now your back in hboot select recovery,once there click mounts & storage button , mount USB drive. Now copy the Rom to your phone. Unmount USB drive, now flash super wipe script. BUT DON'T REBOOT AFTER YOU FLASH THIS!!!!!! choose option to select another zip to flash. This time flash your Rom & reboot. Now your done. Simple huh. & to answer your ruu ?, you can't downgrade ruu's if your on 1.29, your stuck with it till a newer one comes out.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Woah! That's spot on... I was surely gonna mess up my phone if i had done the RUU.
Its charging while the screen is off as we speak. But I think there is a problem with the charge thingy.
Its off and charging.. but sooner or later it turns off due to low battery (IM SUCH A NOOB I DNT KNW IF THE LOW BATTERY IS CAUSING THE PROBLEM)
I'll wait for it to charge again though and connect to the PC again
In the meanwhile can u answer me something regarding this
1. Does the red light turns on while charging in CWM 5.8.4.0
2. Does the mount USB Drive works? :'( Cuz when the phone was working fine. The mount USB Drive failed and gave an error of having a "lunfile missing" :/

Both of your questions can be found :
http://forum.xda-developers.com/showthread.php?t=1594819

i flashed the boot.img like ray said. then i turned the phone to recovery mode it went there and then mounted the usb it worked etc.
but I didnt flashed just yet.. i wanted it to be charged so i turned it off.. I am again getting that "not turning off" habit again
OH God what am i doing wrong here

PLEASE!! Someone help me! It's got that nasty thing that gets HTC Queitly Brilliant thing again.. It's charging but won't go into the recovery mode now!!!!!!!!!!!!!!!

How can I charge my phone while on Relocked Bootloader. I need help u guys!

Solved: Power Down reboots into Recovery

Installed CWM Recovery (recovery-clockwork-6.0.4.8-m8.img) using Fastboot,
and then installed UPDATE-SuperSU-v1.94.zip
then took a nandroid backup.
Booted into Android - no problems.
But now :
- when I power down it reboots straight into CWM Recovery.
- when I select the advanced options of CWM Recovery / Power Down,
it reboots into CWM Recovery.
- when I select Fastboot/Power Down it also reboots into CWM Recovery.
From CWM Recovery I can
Boot System Now
and it boots into the system,
But when I power down, it reboots again into CWM Recovery.
ie, I can't power down.
The above only happens if a power or usb cable is connected.
If no power cable is connected, it shuts down normally.
But, if after it is fully shut down, I connect a power cable,
it again boots, by itself, into CWM Recovery !!
Notes:
- A restart from Android does an actual restart into the phone OS, not into CWM Recovery.
- if I turn back on Power/Fastboot, then I can shutdown properly even with power connected,
so the problem happens when Fastboot is off.
Anybody have any idea what is causing this
and what I can do about it?
some things I can think of trying
but I don't want to make things worse.
Have done this before on a Galaxy Nexus with no problems,
and have put CyM on an S3 with no problems.
[previously posted in the wrong forum (M7) moved here.]

undecidable said:
Installed CWM Recovery (recovery-clockwork-6.0.4.8-m8.img) using Fastboot,
and then installed UPDATE-SuperSU-v1.94.zip
then took a nandroid backup.
Booted into Android - no problems.
But now :
- when I power down it reboots straight into CWM Recovery.
- when I select the advanced options of CWM Recovery / Power Down,
it reboots into CWM Recovery.
- when I select Fastboot/Power Down it also reboots into CWM Recovery.
From CWM Recovery I can
Boot System Now
and it boots into the system,
But when I power down, it reboots again into CWM Recovery.
ie, I can't power down.
The above only happens if a power or usb cable is connected.
If no power cable is connected, it shuts down normally.
But, if after it is fully shut down, I connect a power cable,
it again boots, by itself, into CWM Recovery !!
Notes:
- A restart from Android does an actual restart into the phone OS, not into CWM Recovery.
- if I turn back on Power/Fastboot, then I can shutdown properly even with power connected,
so the problem happens when Fastboot is off.
Anybody have any idea what is causing this
and what I can do about it?
some things I can think of trying
but I don't want to make things worse.
Have done this before on a Galaxy Nexus with no problems,
and have put CyM on an S3 with no problems.
[previously posted in the wrong forum (M7) moved here.]
Click to expand...
Click to collapse
Well I haven't had this happen to me ever so, not sure how much help I'll be but...
Have you tried reflashing CWM? Perhaps clear the cache? Try to flash TWRP and see if it does the same, can always flash CWM again afterwards.

BerndM14 said:
Well I haven't had this happen to me ever so, not sure how much help I'll be but...
Have you tried reflashing CWM? Perhaps clear the cache? Try to flash TWRP and see if it does the same, can always flash CWM again afterwards.
Click to expand...
Click to collapse
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!

undecidable said:
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
Click to expand...
Click to collapse
Don't think a system reset is necessary just yet. First try to clear the cache and re-flashing CWM to see what it does. If nothing then you can try TWRP to see if it does the same thing.
Have you tried searching for a similar problem in the CWM thread if it's recovery related?
---------- Post added at 06:21 AM ---------- Previous post was at 06:10 AM ----------
undecidable said:
Yes, me neither.
My next step was the same as your suggestions,
a system reset, clear cache etc and to try flashing TWRP.
My worry is this powering on to recovery when I plug in the cable.
I was hoping to understand that a bit before trying too many things.
It is easier to make things worse than better!
Click to expand...
Click to collapse
I also just noticed the version number for the CWM you're using, are you sure that's the right version? What device variant are you using, International, Verizon etc?
I see only these versions for international
philz_touch_6.25.5-m8.img
philz_touch_6.26.6-m8.img
philz_touch_6.41.6-m8.img
philz_touch_6.43.6-m8.img
Maybe you have wrong version if you use international version.
Download newest one here and reflash. That is IF you use international.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8

BerndM14 said:
Don't think a system reset is necessary just yet. First try to clear the cache and re-flashing CWM to see what it does. If nothing then you can try TWRP to see if it does the same thing.
Have you tried searching for a similar problem in the CWM thread if it's recovery related?
Click to expand...
Click to collapse
A system reset is no problem. I already did one before starting, and it is new. So no data/apps to lose.
Yes, spent about 6 hours searching last night. Haven't come across anything like it.
Plus, there doesn't seem to be a CWM thread for the HTC One M8 - there are threads for TWRP and Philz (CWM Advanced).

got info below nevermind =oD

I also just noticed the version number for the CWM you're using, are you sure that's the right version? What device variant are you using, International, Verizon etc?
I see only these versions for international
philz_touch_6.25.5-m8.img
Click to expand...
Click to collapse
I'm not using philz, I'm using standard CWM:
http://clockworkmod.com/rommanager
which is the recommendation in the Cyanogenmod instructions:
http://wiki.cyanogenmod.org/w/Install_CM_for_m8
So I think my version of CWM is correct.

BerndM14 said:
Yeah just linked the same to you now as well. Where did you get that version from then?
Nevermind, I got where you downloaded it from http://forum.xda-developers.com/showthread.php?t=2708520
So you're on Verizon?
Click to expand...
Click to collapse
No, I have the international version, and the recovery is from
http://clockworkmod.com/rommanager
the last line on the page, labelled M8.
I think it is the official version.

Well it seems we're back to square one then, erase cache.
Hook up device to PC, go into fastboot, adb reboot bootloader
fastboot erase cache
If it doesn't work then try another recovery, Philz or TWRP. Did you want to flash CM hence why you followed their tutorial?

BerndM14 said:
Well it seems we're back to square one then, erase cache.
Hook up device to PC, go into fastboot, adb reboot bootloader
fastboot erase cache
If it doesn't work then try another recovery, Philz or TWRP. Did you want to flash CM hence why you followed their tutorial?
Click to expand...
Click to collapse
I always read about 20 tutorials first: some are vague, some unreliable, some incomplete, some assume you have more experience, to make sure I fully understand what I have to do.
I chose CWM because I've used it before on a Galaxy Nexus and an S3 and it has been reliable.
I will install Cyanogenmod as soon as it goes to Stable for the M8. I have it on the S3 and am over-the-moon happy with it. However that could be a year.
Might wait a day before I try flashing TWRP. See if I can discover more, or if anyone has an insight to offer. I mean, why would it boot when you plug in the power cable?! Too strange to not be cautious.

undecidable said:
I always read about 20 tutorials first: some are vague, some unreliable, some incomplete, some assume you have more experience, to make sure I fully understand what I have to do.
I chose CWM because I've used it before on a Galaxy Nexus and an S3 and it has been reliable.
I will install Cyanogenmod as soon as it goes to Stable for the M8. I have it on the S3 and am over-the-moon happy with it. However that could be a year.
Might wait a day before I try flashing TWRP. See if I can discover more, or if anyone has an insight to offer. I mean, why would it boot when you plug in the power cable?! Too strange to not be cautious.
Click to expand...
Click to collapse
It seems like it's an old issue with CWM though on various devices.
HTC Desire S same problem as you also CWM recovery.
Desire Z same problem also with CWM recovery.
Desire HD same problem ALSO CWM.
Don't know if there is a problem with CWM and HTC devices maybe...Those 3 are all for HTC devices. Though doing a google search you do get the same problem with different manufacturer phones also with CWM

BerndM14 said:
It seems like it's an old issue with CWM though on various devices.
HTC Desire S same problem as you also CWM recovery.
Desire Z same problem also with CWM recovery.
Desire HD same problem ALSO CWM.
Don't know if there is a problem with CWM and HTC devices maybe...Those 3 are all for HTC devices. Though doing a google search you do get the same problem with different manufacturer phones also with CWM
Click to expand...
Click to collapse
wow! Clearly the issue! And it seems changing recoveries fixes it. Will try in the next hour.
what was the search phrase you used? All I tried returned irrelevent results, though mostly I was using G not XDA.
As my father used to say, your blood is worth bottling (its a compliment).
thankyou!

undecidable said:
wow! Clearly the issue! And it seems changing recoveries fixes it. Will try in the next hour.
what was the search phrase you used? All I tried returned irrelevent results, though mostly I was using G not XDA.
As my father used to say, your blood is worth bottling (its a compliment).
thankyou!
Click to expand...
Click to collapse
https://www.google.co.za/search?q=w...ite:forum.xda-developers.com&biw=1920&bih=979
Tossed in plenty of keywords into google, of course doing it normally gives a lot of results from other sites too but I just decided to narrow it down to xda(Most sites refer help questions to xda anyways so...)
I think it's better to use Google for searches anyways, it records info from a lot of sites. XDA works on a "keyword" basis it seems and most people when making threads don't really add any keywords to it so finding it is difficult. Heck, I even had issues finding HTC__622 in a thread where I knew for a FACT HTC__622 was mentioned at least 4 times, the results in xda itself turned up nothing.
I didn't even bother to try and search within xda for this issues, went the Google route and narrowing it down to xda, much better :good:
Back to the issue though, it would still be interesting to know what actually causes it to boot into recovery when it gets plugged in, it's strange and I'm curious about it. I also think flashing either Philz or TWRP should help, there are quite a few people on here using Philz and I can't recall an issue like this being mentioned before so perhaps it's not a problem with Philz.

BerndM14 said:
Back to the issue though, it would still be interesting to know what actually causes it to boot into recovery when it gets plugged in, it's strange and I'm curious about it. I also think flashing either Philz or TWRP should help, there are quite a few people on here using Philz and I can't recall an issue like this being mentioned before so perhaps it's not a problem with Philz.
Click to expand...
Click to collapse
Thanks. I did try an XDA search from G, but you are just better at it
There is code that gets executed when you plug in the power cable:
it shows the battery charging.
The battery charging icon that is showing just before boot into CWM recovery is different from the normal battery charging icon (that I can see when I have settings /power / fastboot on).
I wonder if CWM changes that code? If that is the case, flashing TWRP might not fix it - will soon know.

Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
Now, when I power-off,
1. initially this funny black/white battery charging logo appears
with words in red at the bottom like:
This build is for Developement Purposes only
Do not distribute outside of HTC
without HTC Permission...
Click to expand...
Click to collapse
2. Then the normal green battery icon appears
3. but then the TWRP screen appears and disappears.
4. For about 2 secs the TWRP screen may flash back briefly
before returning to the green battery icon with the backlight.
5. Then it settles on the green battery icon,
and the backlight stays on for about 10 secs.
6. then the screen switches off
and it really appears to be powered off.​
But if I quickly 'touch' the power button
the TWRP screen briefly appears (with a lock over it) once
and then the green battery screen reappears.
If I unplug then replug in power,
the same things happens: steps 1-6 above.
Tried flashing TWRP 3 times - no change.
Will now try flashing philz.

undecidable said:
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
....
Will now try flashing philz.
Click to expand...
Click to collapse
Philz does exactly the same as CWM - not surprising given that it is CWM based.
So have returned to TWRP, which is at least usable.
Any idea how to file a bug against CWM?
Philz I can do on their forum here.

undecidable said:
Flashed TWRP
(openrecovery-twrp-2.7.1.0-m8.img)
much healthier but not completely normal.
Now, when I power-off,
1. initially this funny black/white battery charging logo appears
with words in red at the bottom like:
2. Then the normal green battery icon appears
3. but then the TWRP screen appears and disappears.
4. For about 2 secs the TWRP screen may flash back briefly
before returning to the green battery icon with the backlight.
5. Then it settles on the green battery icon,
and the backlight stays on for about 10 secs.
6. then the screen switches off
and it really appears to be powered off.​
But if I quickly 'touch' the power button
the TWRP screen briefly appears (with a lock over it) once
and then the green battery screen reappears.
If I unplug then replug in power,
the same things happens: steps 1-6 above.
Tried flashing TWRP 3 times - no change.
Will now try flashing philz.
Click to expand...
Click to collapse
Well removing the red development purposes text is easy enough if you have S-OFF. Remove Red Text on Splash screen
I'm not sure if the same issue with CWM is applicable to all or most users of Philz on here, like I said before, I haven't noticed any threads popping up discussing the issue, unless they discussed it in Philz thread itself.
I myself haven't noticed the issue you have with TWRP, will look into it more as I get some time, gonna be a hectic week Personally I only use custom recovery when I need it, which isn't that often, not a big "flasher" of ROMs etc, so I'm on stock recovery.

BerndM14 said:
Well removing the red development purposes text is easy enough if you have S-OFF. Remove Red Text on Splash screen
I'm not sure if the same issue with CWM is applicable to all or most users of Philz on here, like I said before, I haven't noticed any threads popping up discussing the issue, unless they discussed it in Philz thread itself.
I myself haven't noticed the issue you have with TWRP, will look into it more as I get some time, gonna be a hectic week Personally I only use custom recovery when I need it, which isn't that often, not a big "flasher" of ROMs etc, so I'm on stock recovery.
Click to expand...
Click to collapse
Yes, found the post for Remove Red Text on Splash screen early this morning. Seems to be related to Root, and separate from the TWRP issue.
I have to wonder if the TWRP problems aren't caused by the initial flashing of CWM. Anyway will post the issue on the TWRP forum tomorrow and see what they say.
Seems Philz has had this problem before, it comes from CWM, and fixed it before.
I have to say, this is the last HTC phone I buy - Samsungs are so much friendlier to flashing. Also I greatly dislike the big Tampered sign.
Reason for flashing recovery this time is I wanted root so I could remove garbage from the phone.
I don't flash ROMs much. High learning curve and risky. I do just one flash: from stock to CyangenMod. so much nicer it is worth it. I have to say if I had to choose between my old S3 with CyanogenMod and a stock M8, it would be the S3. If I can't get the garbage off the M8, I will just put it in a drawer till CyM goes stable for it.

Solved: Power Down reboots into Recovery
undecidable said:
Seems Philz has had this problem before, it comes from CWM, and fixed it before.
Click to expand...
Click to collapse
The solution! From the Philz M8 thread.
http://forum.xda-developers.com/showthread.php?p=53464839
An earlier version of Philz: 6.26.6-m8.zip.
The earlier version doesn't have the problem.
Thanks to @donmarkoni

My HTC M8 Stuck at ONE Logo once restarted. No Recovery, No DWNLD mode available.

I've seen already this thread suggested by XDA thread locator.
https://forum.xda-developers.com/htc-one-m8/help/verizon-htc-one-m8-stuck-htc-logo-t3163088
But I'd try to explain as simple as possible the whole situation which happened hours ago.
Don't know what happened but my mothers phone went off and restarted with htc one logo on it and nothing else later.
Power button itself doesnt work and is not responding.
Configuration PWR + VOL UP gives me restart but no recovery mode, giving me sound effect of restarting phone and ONE logo on it without any other reaction whatsoever.
PWR + VOL DWN zero reaction
PWR + VOL UP & DOWN pressed together restarting the phone and then gives me HTC ONE LOGO and nothing else.
when Phone is plugged in to the computer and I'm forcing the phone to restart it shows me new Device on the computer as a CD Driver every time.
So I think there is still hope to get this guy back to life.
It's running on custom rom but unknown version because it was purchased as a refurb from ebay 2 years ago and it was running just fine utill this very day.
I'm absolutely noob with flashing twrping etc so please ELI5 if possible, any type of help will be much appreciated.
Thanks in advance.

Hey, I had this same problem a couple of days ago. Here's what I did to get the phone into fastboot, from where you can install a recovery, factory reset etc.
1. Hold the power button + vol up button for about 10-20 seconds. This should shut down the phone.
2. Hold the power button + vol down button to restart the phone back into fastboot.
If you can get into fastboot, there are plenty of guides which can help you flash a twrp image. If you want me to give you some instructions on that just reply and let me know. Good luck!

Note that this phone doesn't have download mode (as some other Android devices do); nor is there a button combo to go directly to recovery. But you can almost certainly still get to bootloader, and from there boot recovery. In the current condition, you can get to bootloader by:
1) Hold Power+ vol up (as you have been) to restart the phone.
2) Once the screen goes dark (signaling it is about to reboot) let go of the buttons, and only hold vol down
3) Don't let go of vol down until the bootloader screen appears.
4) If the above sequence fails, its virtually always because the user just didn't get the timing right (either started pressing vol down too late, or let go too early). Just repeat steps 1-3 until you get to bootloader.
Once in bootloader, try to reflash the ROM, or restore a TWRP backup (if you have one). Spontaneously stuck on HTC logo screen is often a result of the OS/ROM becoming corrupt or otherwise damaged, and flashing/restoring the ROM will often fix it.

Thanks @redpoint73 I've managed to get to the preinstalled recovery.
Sadly reflashing/factory reset failed few times due corrupted files.
I'm ok with the fact that I lost the data on the phone since most of it was stored on the cloud.
Now I need ROM to flash on the phone thru recovery but I don't know which one would you reccomend.
It's my mom's phone so basically reliabilty and robustness over flashing lights and numerous unnecessary functions.
Version of android doesn't really matter.
Thanks again for help so far.
Can I put the rom I'm about to flash on external SD Card or I have to transfer it thru computer to the phone?
TWRP might be extra helpful or the recovery it's functions are just fine?

Shewie said:
Thanks @redpoint73 I've managed to get to the preinstalled recovery.
Sadly reflashing/factory reset failed few times due corrupted files.
I'm ok with the fact that I lost the data on the phone since most of it was stored on the cloud.
Now I need ROM to flash on the phone thru recovery but I don't know which one would you reccomend.
Click to expand...
Click to collapse
I'd need to know more about the phone in order to give any suggestions.
With the phone connected to computer, boot into fastboot mode, and (assuming you have fastboot setup on your computer) do the command: fastboot getvar all
Then post the results (delete IMEI and serial number before posting).
Also, what version TWRP (if that is the recovery installed)?
Shewie said:
Can I put the rom I'm about to flash on external SD Card or I have to transfer it thru computer to the phone?
Click to expand...
Click to collapse
You will be able to flash a ROM from the SD card, if using TWRP.
Shewie said:
TWRP might be extra helpful or the recovery it's functions are just fine?
Click to expand...
Click to collapse
Not sure what is being asked here (can't quite understand). Are you saying that another recovery besides TWRP is presently installed?

@redpoint73 I don't have TWRP but this...
Maybe pictures will justify the real situation.
I don't have the fastboot preinstalled on computer. (yet)
I wouldn't mind link to the pack with "must have" to complete the process

Shewie said:
@redpoint73 I don't have TWRP but this...
Maybe pictures will justify the real situation.
I don't have the fastboot preinstalled on computer. (yet)
Click to expand...
Click to collapse
You have what is called the "stock recovery" or official HTC recovery.
You can't flash anything but OTA updates, or other official (HTC) signed zips with this. You need a "custom" recovery like TWRP in order to flash things like custom ROMs. So I'm curious what you meant before when you posted:
Shewie said:
Thanks [MENTION=660462]Sadly reflashing/factory reset failed few times due corrupted files.
Click to expand...
Click to collapse
What exactly were you trying to "reflash", what were the exact steps, and the results (specific error messages, etc.).

I did the factory reset but it didn't help still stucking at ONE logo like posted initially. So this is basically the situation right now. I was able to get to recovery but nothing else.

Shewie said:
I did the factory reset but it didn't help still stucking at ONE logo like posted initially. So this is basically the situation right now. I was able to get to recovery but nothing else.
Click to expand...
Click to collapse
Okay, so you're confusing the terms. Factory reset doesn't flash/reflash anything (flash meaning to install some firmware or software to the device). The only thing that factory reset does is wipe user data.
At this point, I'd suggest the best/easiest course of action in the current conditions (stock recovery, locked bootloader) would be to run the RUU intended for your device. Your device is the AT&T version, so the RUU can be found at the bottom of the page (and instructions on how to install): http://www.htc.com/us/support/htc-one-m8-att/news/
RUU is a complete factory image. You download to a PC (PC required, won't work on Mac or Linux) connect the phone (booted into bootloader-fastboot mode) then just run the RUU, and it will do the rest.
I'm confidant this will get the phone up and running. Your mom may not like all the AT&T branding and apps, if it wasn't there before, and AT&T is not her carrier (one of the main reasons for these devices to have custom ROM - to remove carrier branding). But we can cross that bridge (if need be), after we get the phone working.

Installed Software, downloaded RUU from website provided, turned phone into fastboot before installing RUU.
Something started happening with the phone during installation but installation itself cant be finished, it's an endless process of update, phone is already plugged 3rd hour or so to the computer but the update status remain the same.
Should I try different approach?

Shewie said:
Installed Software, downloaded RUU from website provided, turned phone into fastboot before installing RUU.
Something started happening with the phone during installation but installation itself cant be finished, it's an endless process of update, phone is already plugged 3rd hour or so to the computer but the update status remain the same.
Should I try different approach?
Click to expand...
Click to collapse
It just gets stuck sometimes. Just kill the process, and start the RUU again. It will probably work fine on the next try. It's a bit scary, as it says not to stop the process or disconnect the phone while it's running. But if it gets stuck like this, there isn't anything else you can do.

Good News, it's working. But it's bloated to the bones. How I can get rid of the carrier unnecessary software?
I was to afraid to kill the process during update to avoid scenario of bricking my phone completely.
But It's working!