Help Stuck on HTC One booting screen

[gypsyan]

Hello , I recently got a HTC One SV and hadn't been updated to 4.2.2 as it was my mom's phone. The problem occured as I installed the new version early before mentioned. It had appeared on my notification and updated it , since then I haven't been able to start the phone again as it remains stuck on the booting screen.

Is there any way to fix it ?
I am new to android so it would be greatly appreciated if you could help me with a tutorial or something.

I have found another thread that was similar to mine , but as I scrolled down it didn't help me solve my problem , all I can help you with is by giving you the HBOOT stats

***LOCKED***
K2_UL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40a.00.04
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 14 2013, 22:10:43:-1

 

[knoober]

Someone with more knowkedge could give better help but heres what i think (and remember i can only keep mine working by constantly reflashing backups) . But anyways as long as can get to the bootloader (and it sounds like you can) then you should be able to unlock, s off, flash a custom recovery (ive been told thst 4.2.2 and up needs TWRP 2.7.X , but if your still on 4.1.2 then you have more choices) and then you can reinstsll the stock rom. Also there is a thing cakked the RUU that i found to be usefull. It tajes you back to stock abd i dont think you need to be able to boot. All the links are in the first post of the all things root form. There is also instructions for flashing custom recovery and stock rom.
All the ppl here have been real helpfull abd im sure can answer your questions if the instructions become too tough (i had trouble till i read em like a hundred times). Good luck

 

[ModdingMyMind]

Unfortunately, he will not be able to use an RUU since the RUU for the K2_UL variant is based on ICS. Since he is S-On and the bootloader is locked to include that he is running JB this will not be possible. The RUU would have to be based on an OS which is equivalent to the OS his device is currently running in order for it to work. Otherwise, you must S-Off the device.

However, I highly recommend that you take this device back for repair since you are indeed S-On with a locked bootloader and the update caused your device to go in to a bootloop.

There isn't much that can be done unless you unlock your bootloader from the HTCDEV website and then flash a TWRP recovery to your recovery partition which is specific to your K2_UL variant. Where at that point some files and instructions can be provided.

 

[knoober]

Unfortunately, he will not be able to use an RUU since the RUU for the K2_UL variant is based on ICS. Since he is S-On and the bootloader is locked to include that he is running JB this will not be possible. The RUU would have to be based on an OS which is equivalent to the OS his device is currently running in order for it to work. Otherwise, you must S-Off the device.

However, I highly recommend that you take this device back for repair since you are indeed S-On with a locked bootloader and the update caused your device to go in to a bootloop.

There isn't much that can be done unless you unlock your bootloader from the HTCDEV website and then flash a TWRP recovery to your recovery partition which is specific to your K2_UL variant. Where at that point some files and instructions can be provided.

You see i told you therebwere smarter ppl. I didnt catch the K2_UL. I made the assumption of k2_cl. If it is still under warranty then that is probly better than what i said to do. But fir the sake of argument...
As long as hboot.can be entered he can unlock, s off, abd flash TWRP right? And from there he coukd conceivably choose the correct stock rom and be back in business right? (just trying to prove to myself that i had the right idea anyhow)
I assume hboot (thats what its called when i pull the battery/reinsert and hold vol down + power right) can be entered by the infor at the end of his podt ( the stuff i didnt read to close ).

 

[ModdingMyMind]

He won't be able to S-Off without a system on his device. If his system is still intact he should be ok. However, given the info he provided in regards to his HBoot it seems the OTA didnt process completely so it's hard to say if he is on 4.1.2 or 4.2.2 or in the midst of updating his device has a mixture of both (which is plausible since his device won't boot).

With that said I can't really recommend which tool to use to gain S-Off successfully given the current phone status. I would start with using Moonshine which is specific to the K2_UL variant. If it fails then try facepalm. If that fails then shoot for rumrunner universal. However, it can be dangerous running all of these tools to gain S-Off given the status of the phone.

What I would suggest if the person wishes not to take it in for repair and possibly a replacement is to attempt to unlock the bootloader from the HTCDEV website, install TWRP to the recovery partition via:

fastboot flash recovery recovery.img

while insuring the TWRP recovery is specific to the device of course.

If successful at doing those two things then a TWRP backup can be provided to restore your device back to 4.1.2 where you initially were at prior to accepting that update.

 

[ModdingMyMind]

Also, you don't have to pull the battery to boot in to your bootloader. Go to, Settings > Power, on your device. Scroll down and you will see, Fast boot. Make sure you untick the box. Now you can just power down your device normally and use the power and volume keys to boot in to your bootloader without the hassle of pulling your battery everytime.