Database Info

CM10 Stuck at Bootscreen

After flashing CM10, coming from CleanRom 4.5 and doing a factory reset, I get stuck at the bootscreen. I've let it stay there for hours but every time I flash it, it stays stuck there, Any suggestions to get this to work? Radio is 0.19as.32.09.11_2

You have to do a full wipe, factory reset, cache, dalvik cache, system. Then flash. That should get u booted.

me 2 .... HELP!!! Please...
i did the same .. stuck at boot. but reflashed recovery and everything gone ... nothing to flash!!! including backups.... awesome!!! tried extracting and flashing boot img and cm 10 boot img came up but stalled there. ???? complete brick? says cant mount sd card. ???
18th.abn said:
You have to do a full wipe, factory reset, cache, dalvik cache, system. Then flash. That should get u booted.
Click to expand...
Click to collapse

Tried that as well, still stuck at bootscreen. Sometimes after flashing, my storage will fail to mount so I have to format it.

paperclips, what recovery are you running?

gunnyman said:
paperclips, what recovery are you running?
Click to expand...
Click to collapse
TWRP 2.2.0

How do you do that...?
Sent from my HTC One X using xda app-developers app

paperclips said:
After flashing CM10, coming from CleanRom 4.5 and doing a factory reset, I get stuck at the bootscreen. I've let it stay there for hours but every time I flash it, it stays stuck there, Any suggestions to get this to work? Radio is 0.19as.32.09.11_2
Click to expand...
Click to collapse
Did you do the update to 2.20 (doesn't matter if done safely or not)?
If so, you need to manually flash the boot.IMG in the zip.
Sent from my One X using xda app-developers app

If you are 2.20 you have to make sure to manually flash the boot.img.
Also make sure when you are about to flash you wipe everything. You have to wipe cache, dalvik, factory reset, & system. Do it twice just to be sure.
The first time I flashed CM10 I didn't wipe system. I got stuck on boot screen and it wiped my sd card and then my sd card wouldn't mount. I had to relock my bootloader, run an RUU, and start over. Second time it stuck and worked great. Went back to CR for the camera.

Butters619 said:
If you are 2.20 you have to make sure to manually flash the boot.img.
Click to expand...
Click to collapse
How does one do this, exactly? I have the extracted boot.img. Is this done using adb? TWRP? Little help?

mjwitt2 said:
How does one do this, exactly? I have the extracted boot.img. Is this done using adb? TWRP? Little help?
Click to expand...
Click to collapse
boot to bootloader
fastboot flash boot boot.img

mjwitt2 said:
How does one do this, exactly? I have the extracted boot.img. Is this done using adb? TWRP? Little help?
Click to expand...
Click to collapse
nevermind...Google is my friend Sorry.

mjwitt2 said:
How does one do this, exactly? I have the extracted boot.img. Is this done using adb? TWRP? Little help?
Click to expand...
Click to collapse
extract boot.img place it into your adb folder reboot your phone into bootloader while connected to your pc. Open a cmd prompt in your adb folder type fastboot flash boot.img it will then flash the boot.img once done reboot and your fixed.

mjwitt2 said:
How does one do this, exactly? I have the extracted boot.img. Is this done using adb? TWRP? Little help?
Click to expand...
Click to collapse
Copy the boot.img to your adb/fastboot directory on your computer. Boot the phone into the bootloader. Open a command prompt from your adb/fastboot directory on your computer. "fastboot flash boot boot.img"
You do still have to flash the zip through TWRP.
If you have 2.20, you have to flash any radio and boot.img through fastboot. Personally, the 2.20 radio has been the best for me so I haven't had the need to flash another.

gunnyman said:
boot to bootloader
fastboot flash boot boot.img
Click to expand...
Click to collapse
Thanks, Gunny. I made an id10 T error and didn't google the correct terms

Butters619 said:
Copy the boot.img to your adb/fastboot directory on your computer. Boot the phone into the bootloader. Open a command prompt from your adb/fastboot directory on your computer. "fastboot flash boot boot.img"
You do still have to flash the zip through TWRP.
If you have 2.20, you have to flash any radio and boot.img through fastboot. Personally, the 2.20 radio has been the best for me so I haven't had the need to flash another.
Click to expand...
Click to collapse
I'm pretty sure the new HBoot means no radio flashing at all.

Man, I tell you. I'm having one hell of a time flashing roms. I flashed the boot.img and now I'm hung up on the HTC DEV build screen.

mjwitt2 said:
Man, I tell you. I'm having one hell of a time flashing roms. I flashed the boot.img and now I'm hung up on the HTC DEV build screen.
Click to expand...
Click to collapse
did you flash boot.img then boot straight into recovery from the bootloader screen?
That's how I always do it

gunnyman said:
did you flash boot.img then boot straight into recovery from the bootloader screen?
That's how I always do it
Click to expand...
Click to collapse
Yes, I did. However, now I'm stuck at that build screen. hmm...on to the next guess I suppose.

mjwitt2 said:
Yes, I did. However, now I'm stuck at that build screen. hmm...on to the next guess I suppose.
Click to expand...
Click to collapse
you're using Cm10 from our Dev section built by h8rift?

Rooted 2.20 now cant boot my phone

Hi Everyone,
So i followed all the steps to temp root 2.20 including successfully installing TWRP (Team Win Recovery Project). I then downloaded the CM10 rom and extracted the boot.img as per posts and rebooted into the bootloader and flashed the boot.img from CM10 via Fastboot. However after doing then rebooting to Recovery mode in order to flash the ROM, i get stuck in the red text where it gives you a warning about it being in development mode or something.
I am able to successfully boot into the bootloader via Power+down volume. Additionally I am able to boot into the TWRP recovery just fine, however I am lost and have no clue how to restore my phone to either the CM10 ROM or most importantly at least to stock working condition.
When i got to mount the SDCARD via twrp normally i would get a pop up on my screen and allow me to access my SD card, now i get a pop up just telling me that i need to format my SD card first. I'm afraid some how my SD card got wiped or something.
Can someone please walk me through the steps on how to restore my phone. Please if possible i would appreciate using LAME terms as i do not have any experience as you can tell i screwed up :/ Can you please listed step by step instructions including commands for Fastboot/adb etc etc if needed. Thank you very much for your help and support.

I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium

subarudroid said:
I've typed and retyped a response to help. I'm so tired and my brain is mush. (More so than normal) if you can't find any resolution by morning? Pm me and I'll try and help. Something about pluggin the USB in The back of your pc something something....... snore
Sent from my One X using xda premium
Click to expand...
Click to collapse
I know you tried to help, but it appears now I have bricked the phone. Hopefully i can fix it as i still have access to Bootloader and TWRP recovery. I'll PM you in the morning, thank you.

dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"

DvineLord said:
dont factory reset in bootloader. only factory reset in twrp. sometimes evita has a hard time getting into recovery from bootloader. just keep trying to get into recovery from bootloader. also even if your phone doesn't boot all the way adb sometimes still works. so try "adb reboot recovery" while its trying to boot.
if you did corrupt your sdcard try this method to get it fixed without having to run ruu.
[How to] Fix corrupt/unmountable internal storage on the HTC One X/XL
when you get your sdcard fixed remember to wipe everything and then copy cm10 and gapps to your sdcard and flash. since boot.img is already flashed you shouldn't need to do it again.
you did flash boot.img as "fastboot flash boot boot.img"? i made the mistake of flashing boot.img to recovery instead of boot. i was freaking out. just to make sure flash recovery again "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img"
Click to expand...
Click to collapse
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.

movadoevo8 said:
Yes i did fastboot flash boot boot.img from within the Bootlader. FYI that boot.img was from inside the CM10 zip file. I belive my SD card is corrupt i will check out that link. FYI I am able to get into Recovery mode form the Boatloader if i chooser recovery. However since the SD card seems messed up i can't access it currently. Also I tried to use the method to install the CM10.zip file using TWRP recovery. That recovery has a GUI and you can click on the INSTALL button and choose the zip file you want to install, however it errors out.
What is the proper way to flash a rom when i am in the TWRP recovery? Can you provide me with the commands/steps? Thanks for all your support guys.
Click to expand...
Click to collapse
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium

You won't be able to flash anything until you fixed your sdcard using the method in that link.

Ptesmoke where have you been? DvineLord is the only one been helping here. The Q&A thread is a mess. where is edditsync chongo, rohan and the other superhero's. I feel like Hawkeye trying to shoot sh#@ down with a bow and arrow. Waiting for ironman, hulk, Thor and the other avengers to get real sh#@ done. I'm tired going to sleep now.
Sent from my One X using xda premium

ptesmoke said:
install/install from zip/browse to your zip/slide to flash (they really should patent that)
now most of us, to do a clean flash, we'd go into the "wipe" menu in TWRP before flashing , factory reset, wipe cache, wipe dalvik cache, wipe system. then we flash our rom.
hope that cleared it up!
Sent from my One X using xda premium
Click to expand...
Click to collapse
I tried to fixed corrupted SD card as per video. however after flashing the recovery.img via fastboot when it wants me to do a factory reset instead of doing the factory reset it just goes back to the HTC brilliant screen with the red warning text and sits there. If i go to twpr recovery and click on install i can't access me zip currently due to sd card issues.
Is there a way to format via PC since it lets me as long as I am in twpr and just put stock files/folders onto the SD card? Or is it possible to install the 2.20 ruu again? I re-downloaded it form HTC's site while I am in twrp however I cannot install it won't detect my phone. Thanks for your help.

"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.

If you can get into twrp and go to mount, mount usb storage and connect your phone windows should prompt you to format the SD card.
Once that's done you can drag and drop the rom you want to flash then boot into fastboot and flash the boot.img.
If you want to run the ruu you need to relock the bootloader first.
To do that you must go into fastboot usb and then type fastboot oem lock.
Sent from my HTC One XL using xda premium

DvineLord said:
"fastboot oem lock" then run ruu. ruu gets run in fastboot.
after the ruu, reunlock bootloader and flash twrp, copy cm10 and gapps to your sdcard, flash boot.img in fastboot, wipe everything except for external storage in twrp, flash cm10 and gapps in twrp, then reboot.
Click to expand...
Click to collapse
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.

movadoevo8 said:
I'm sorry i'm not too tech savy. Can you clarify how to Fastboot OEM lock. Assuming i just need to be in fastboot mode and run a command in command prompt?
Also once that is done how can i run RUU via fastboot? Right now i have HTC RUU for 2.20 from august that i downloaded from their site and not sure how i can have it detect my phone. If you could clarify and explain those steps in Lame terms i would greatly appreciate it, thanks in advance.
Click to expand...
Click to collapse
That's the command you do and the ruu is an exe file so get into fastnoot on your phone from bl and run the ruu after you've locked the bootloader

Thank you both will try that now.

Hey guys thanks for all your help and your support it worked. I had the wrong CM10 file instead of Evita i had the other one :/ That was the issue all along ugh... but all resolved could of not have done it without your support. Thanks!! I can now finally go to bed.. been at it since 10pm, now 3:11am

Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.

marcur12 said:
Maybe you can help me . I'm having the same problem. The problem is, everytime I try to use any fastboot commands, it'll say "waiting for device". I'm stressing out.
Click to expand...
Click to collapse
Make sure you have the right drivers installed, download the latest htc sync from htc's website.
Install HTC sync connect phone and let the drivers install, then make sure you close htc sync from the system tray and try again.
Like DvineLord said below make sure you're in the bootloader then select Fastboot once selected it should say in red writing Fastboot USB.

fastboot only works in bootloader btw

Hit the thanks button for the people helping you fix your boo boos.
If you can type it, click it for them, least you can do in return.
WR
Sent from my HTC One X

Sent from my HTC One XL using Tapatalk 2

Stuck in boot loop been working on it all day, please help

I have att one x evita. too long to explain everything i have tried but here is where i am
****UNLOCKED****
S-OFF
HBOOT 2.14
I currently have CLOCKWORK RECOVERY going on, I have wiped, installed from SD the CM10.2 nightly i want to install, installs with no errors, installed gapps again no errors.
unit bootloops on HTC screen, I tried again same thing only this time fastboot flashed the boot.img file, tried before and after the rom install.
Tried all the same steps from most current version TWRP.....Im lost, what should i try next.
Also i have no file structure if you mount the storage from recovery i was empty and said it need to be formatted to be used, put it in FAT32. Made it usable, copied the CM ROM directly to the root of mounted drive, since there were no folders or anything in it.
Would love some help please.....im pulling my hair out

ntilley52 said:
I have att one x evita. too long to explain everything i have tried but here is where i am
****UNLOCKED****
S-OFF
HBOOT 2.14
I currently have CLOCKWORK RECOVERY going on, I have wiped, installed from SD the CM10.2 nightly i want to install, installs with no errors, installed gapps again no errors.
unit bootloops on HTC screen, I tried again same thing only this time fastboot flashed the boot.img file, tried before and after the rom install.
Tried all the same steps from most current version TWRP.....Im lost, what should i try next.
Also i have no file structure if you mount the storage from recovery i was empty and said it need to be formatted to be used, put it in FAT32. Made it usable, copied the CM ROM directly to the root of mounted drive, since there were no folders or anything in it.
Would love some help please.....im pulling my hair out
Click to expand...
Click to collapse
Have you tried RUUing back to stock and re-rooting?

Mount usb storage in TWRP recovery and format (fat32) the sd in Windows. It looks as though you've done a factory reset in bootloader at some point which corrupts the sd card. Once you've done that I'd suggest trying to flash another ROM, if you still have problems you'll probably need to RUU as Rolltribe suggested.
Sent from my Evita

I tried mounting SD card and formating, using twrp and cwm. To try the RUU is that something that is done through fastboot USB?
timmaaa said:
Mount usb storage in TWRP recovery and format (fat32) the sd in Windows. It looks as though you've done a factory reset in bootloader at some point which corrupts the sd card. Once you've done that I'd suggest trying to flash another ROM, if you still have problems you'll probably need to RUU as Rolltribe suggested.
Sent from my Evita
Click to expand...
Click to collapse

And the format didn't work? An RUU is an exe program that's run through Windows while the phone is connected, usually in fastboot mode.
Sent from my Evita

timmaaa said:
And the format didn't work? An RUU is an exe program that's run through Windows while the phone is connected, usually in fastboot mode.
Sent from my Evita
Click to expand...
Click to collapse
no it didnt work i am trying downloading the RUU right now.
RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105.exe
this ^ is the file i am downloading does it loot correct for an ATT HTC ONE X(Evita)

That is an at&t RUU but it's a very old one. Personally I'd use the latest which is the 3.18 RUU.
Sent from my Evita

timmaaa said:
That is an at&t RUU but it's a very old one. Personally I'd use the latest which is the *****
Sent from my Evita
Click to expand...
Click to collapse
Having about the same issue on my phone. I have TWRP 2.5 on there. Tried to re-install viperxl and it goes through the install OK and then just boot loops.
Tried to use the RUU listed above and it fails with an error code of "Error 159 image error"
The RUU is going from Image version 2.20.502.7 to image ver 3.18.502.6
I had a different error with another RUU image I downloaded from HTC but didn't take notes on error.
Any idea's?

TWRP 2.5 is your problem, it's full of bugs. Download TWRP 2.6 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and flash again and you should be fine.
Sent from my Evita

timmaaa said:
TWRP 2.5 is your problem, it's full of bugs. Download TWRP 2.6 from *** Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Now you can enter recovery on your phone and flash again and you should be fine.
Sent from my Evita
Click to expand...
Click to collapse
Trying now. Thanks for the super fast reply. MUCH Appreciated.

HomeWorx said:
Trying now. Thanks for the super fast reply. MUCH Appreciated.
Click to expand...
Click to collapse
u can also try using twrp one click tool v2.6.0.0 per timmaaa suggestion on my signature link below.....
Swyped from BlueICESense_JBE

HomeWorx said:
Having about the same issue on my phone. I have TWRP 2.5 on there. Tried to re-install viperxl and it goes through the install OK and then just boot loops.
Tried to use the RUU listed above and it fails with an error code of "Error 159 image error"
The RUU is going from Image version 2.20.502.7 to image ver 3.18.502.6
I had a different error with another RUU image I downloaded from HTC but didn't take notes on error.
Any idea's?
Click to expand...
Click to collapse
RUU got me back up to stock, thanks for that, now trying to reinstall CM10

[Q] Unable to install any custom ROM

Hey there!
I'm pretty new to the Android platform. I've been on iOS for many years.
I already flashed a custom firmware on a Moto G, which worked fine. (SlimKat)
I thought about doing the same thing with my HTC One X.
GSM version (Model: PJ83100)
Current device state:
*** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.01.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 26 2012, 18:37:14:-1
Unlike the Moto G Bootloader, I'm unable to erase any partition but the cache. Example:
./fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
I am not able to boot into the OS or the recovery partition anymore, so they have probably been wiped. When I reboot the device, it's either a boot loop or it simply shuts down.
I already tried to flash CWM and TWRP. Each of those were successful, at least according to the terminal... Unfortunately, same thing happens when the phone reboots (unable to access recovery).
I also tried to flash SlimKat with the "./fastboot flash zip file_name.zip" command, even if it isn't supposed to work (I believe). It wasn't successful.
In despair, I flashed the boot image from the ROM but still without result.
I did all of those in the FastBoot window and on the RUU mode (./fastboot oem rebootRUU).
Both stuck at the same points.
If anyone knows how to fix this, it would be really appreciated.
All the posts related to the issue did not help me in any ways.
Thank you!

You need to work out why your recovery flashes aren't working, you need a custom recovery to install custom ROMs on this device, flashing them through fastboot will not work. Can you explain in detail and step by step the method you use to flash the recovery please?
Sent via Bacon

timmaaa said:
You need to work out why your recovery flashes aren't working, you need a custom recovery to install custom ROMs on this device, flashing them through fastboot will not work. Can you explain in detail and step by step the method you use to flash the recovery please?
Sent via Bacon
Click to expand...
Click to collapse
I'm doing the same thing that should be done.
./fastboot erase cache
./fastboot flash recovery openrecovery-twrp-2.7.1.0-evita.img
./fastboot reboot-bootloader
Select BOOTLOADER
Select RECOVERY
Device shows HTC logo for one-two secs
Shuts down

Did you check the md5 of the downloaded recovery? It might be corrupt.
Sent via Bacon

timmaaa said:
Did you check the md5 of the downloaded recovery? It might be corrupt.
Sent via Bacon
Click to expand...
Click to collapse
I redownloaded the file from the internet so it can't be corrupted twice.
I believe that I also tried with CWM with same results.
None of those even want to boot.
And now since yesterday, I'm not even able to boot my phone.
I contacted HTC and their hard reset procedure did nothing.
Well...

jeanchoquette56 said:
I redownloaded the file from the internet so it can't be corrupted twice.
I believe that I also tried with CWM with same results.
None of those even want to boot.
And now since yesterday, I'm not even able to boot my phone.
I contacted HTC and their hard reset procedure did nothing.
Well...
Click to expand...
Click to collapse
It can be corrupted twice, it can be corrupted a thousand times in a row, that's why you need to check the md5 like I suggested. Did you do that??
Forget what HTC have to say, any advice they would give is irrelevant for a modified device. In fact, if you've performed a factory reset from the bootloader you've also just corrupted your sd card.
Sent via Bacon

timmaaa said:
It can be corrupted twice, it can be corrupted a thousand times in a row, that's why you need to check the md5 like I suggested. Did you do that??
Forget what HTC have to say, any advice they would give is irrelevant for a modified device. In fact, if you've performed a factory reset from the bootloader you've also just corrupted your sd card.
Sent via Bacon
Click to expand...
Click to collapse
I'm not sure how to verify the md5. You want me to verifiy the file on the computer or after is has been transfered to the phone?
Like I said, I'm not able to do a factory reset from the bootloader as all "format erase --partiton--" return in errors.
These commands helped me to corrrectly install Slimkat on my Moto G, but how can you do the same when it's not possible to wipe the phone in any ways? From the recovery partition, that would be possible. I'm able to flash the recovery, but not to access it. As this said, I'm really stuck.
The One X does not have a SD card btw. At least, there look to be no slot for it.
Thank you!
Especially timmaaa

jeanchoquette56 said:
I'm not sure how to verify the md5. You want me to verifiy the file on the computer or after is has been transfered to the phone?
Like I said, I'm not able to do a factory reset from the bootloader as all "format erase --partiton--" return in errors.
These commands helped me to corrrectly install Slimkat on my Moto G, but how can you do the same when it's not possible to wipe the phone in any ways? From the recovery partition, that would be possible. I'm able to flash the recovery, but not to access it. As this said, I'm really stuck.
The One X does not have a SD card btw. At least, there look to be no slot for it.
Thank you!
Especially timmaaa
Click to expand...
Click to collapse
Ok, you don't know how to verify the md5, but you can overcome that problem by using Google to search how to do it.
So you've attempted a factory reset from the bootloader, it gave you errors, and it has corrupted your sd card.
I'm aware that this device doesn't have an sd card slot, it has internal memory (or a virtual sd card), which is commonly referred to as the sd card.
Sent via Bacon

[Q] htc one sv soft bricked :/

Hi everybody !
I think i'm in the right section to expose you my problem, and no one on this forum had been confronted to such fails ! but i'm new in this forum to write threads (altough i already read many of them)
i'll try to be quick :
a year ago i bought a htc one sv , i unlocked the bootloader and then i stopped because i was with windows 8 and it was boring with usb 3.0 (i can use windows 7 right now..!). then i got some problems with "android.phone", or android.process.media" stopped et i believed my phone dead, but i learned things, installed the TWRP recovery 2.7.0.1 and flashed therom stock odexed jelly bean which allowed me to get back to stock my phone! (the twrp was with the root (or the rom odexed...) so i became rooted! but when i updates the superuser app few months ago, i got problems of binaries so i didn't install the last supersu app update (2/3 weeks ago). unfortunately,2 weeks ago, my phone did a reboot in the night (which awoke me) but in a bootloop...
First i tried factory reset then clean storage du bootloader, but it did nothing.
at the beginning i could not acceed to the recovery, but, lucky i am, a boot in fastboot usb and now from the phone, i can go to my recovery twrp 2.7.0.1 -or 2.8.4.0 by boot fastboot usb) however, TWRP shows "no os installed"it s been 2 weeks that i'm searching, but without results... that's why i'm asking here to the best in android world ^^
the things that i already tried without results:
flash the same zip odexed from recovery and from fastboot usb
flash hboot, but i'm s-on
update recovery ( i only can boot by fastboot usb)
flash rom custom venom with the installer in the rom
find files for sdcard "pl80diag.zip et nbh et pl80img.zip et nbh"
but i'm S-on and can't be S-off, the process with moonshine stopp when the devices has to boot...
i also tried adb sideload and simple adb with the phone in recovery recovery but:
recovery is unable to mount internal storage partitions (unable to mount int-sd, etc............)
my phone shows "tampered" "unlocked" and "s-on" hboot "2.00.000".. ask for more...
from now on, when i boot the phne i don't have any more bootloop, i'm directly in the hboot..!
i tried extract rom.zip from RUU.exe of ICS but i didn't used it...
so i'm wondering if there is a way to unbrick this soft bricked devices 'casue i already tried all of the unbrick things for soft brick but the partitions being unable to mount killed all my tries... i hope i gave you many informations ! all the suggestions and ideas are welcome!
(i can't find nbh files..)
thanks for reading this busy text, i'm a bit bored of using a very old phone in remplacement if i can repair my lover htc..!
i trust you people i'll check and answer suggestions asap!

Well, you are S-on, there is not much you can do.
Flash twrp recovery 2.7.x or 2.8.x and try to flash a rom for your device model.
Don't forget to do a full wipe in twrp and to flash the boot.img of the rom you are using with fastboot.

old.splatterhand said:
Well, you are S-on, there is not much you can do.
Flash twrp recovery 2.7.x or 2.8.x and try to flash a rom for your device model.
Don't forget to do a full wipe in twrp and to flash the boot.img of the rom you are using with fastboot.
Click to expand...
Click to collapse
it that i was thinking... i already try this (i have already twrp without booting in fastboot or flashing) but the fact is : twrp cannot mount any partitions so the step "writing" is impossible.. even the wipe fails..

If i remember right, in TWRP 2.8, under Wipe - Advanced there must be a button "Repair broken filesystem".
Not sure if this is working on SV, but it is worth a try i think.
What version of this phone do you own?

old.splatterhand said:
If i remember right, in TWRP 2.8, under Wipe - Advanced there must be a button "Repair broken filesystem".
Not sure if this is working on SV, but it is worth a try i think.
What version of this phone do you own?
Click to expand...
Click to collapse
yep you're right i'v already try it on every partitions but i'll do it again !
i've got the K2_UL (i'm french) and it was on 4.2.2 JB.
by the way, thanks for your answers

guess who's back
old.splatterhand said:
If i remember right, in TWRP 2.8, under Wipe - Advanced there must be a button "Repair broken filesystem".
Not sure if this is working on SV, but it is worth a try i think.
What version of this phone do you own?
Click to expand...
Click to collapse
hey guys, it's been a while but i was searching during all this time. I've experienced some things with adb shell and what i saw :
my partitions are messed up, not annihilated, but messed up. 2 reasons : partitions can't be mounted in the last recovery of TWRP, and when i use Fdisk -l /dev/block/mmcblk0 and the partition table of mmcblk0 and what I see is that my partitions table are not in disk order. My partitions are overlapping.. Perhaps it will help. I tried some ext2fd and mkfs.ext4 but it as not worked properly... maybe you have ideas... because it's been about months that my phone is useless and a paperweight.
by the way on my computer under windows 10, my phone used to be in qhsus_dload..! perhaps there are issues with that!
Thanks.

colton49 said:
hey guys, it's been a while but i was searching during all this time. I've experienced some things with adb shell and what i saw :
my partitions are messed up, not annihilated, but messed up. 2 reasons : partitions can't be mounted in the last recovery of TWRP, and when i use Fdisk -l /dev/block/mmcblk0 and the partition table of mmcblk0 and what I see is that my partitions table are not in disk order. My partitions are overlapping.. Perhaps it will help. I tried some ext2fd and mkfs.ext4 but it as not worked properly... maybe you have ideas... because it's been about months that my phone is useless and a paperweight.
by the way on my computer under windows 10, my phone used to be in qhsus_dload..! perhaps there are issues with that!
Thanks.
Click to expand...
Click to collapse
Which K2 variant do you have?
Sent from my C525c using Tapatalk

SHM said:
Which K2 variant do you have?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
K2_UL, but I am at a point that each try worths it.. even with other K2!
moreover I've got a full stock backup of K2_UL but it didn't work with TWRP when I tried
. from now on i have no more ideas.. ^^

colton49 said:
K2_UL, but I am at a point that each try worths it.. even with other K2!
moreover I've got a full stock backup of K2_UL but it didn't work with TWRP when I tried
. from now on i have no more ideas.. ^^
Click to expand...
Click to collapse
You need an RUU to fix you up.
http://androidruu.com/getdownload.p...0.14_2_10.49.40.11L_release_301902_signed.exe
Sent from my C525c using Tapatalk

SHM said:
You need an RUU to fix you up.
http://androidruu.com/getdownload.p...0.14_2_10.49.40.11L_release_301902_signed.exe
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
ha
I've already tried but when it as to be detected, nothing occured, but i'll try again.. do you think that could be restore my phone ( ave you read my first explanation message,)

colton49 said:
ha
I've already tried but when it as to be detected, nothing occured, but i'll try again.. do you think that could be restore my phone ( ave you read my first explanation message,)
Click to expand...
Click to collapse
Well if you can extract the RUU from the .exe program then you can boot to your hboot then select fastboot from the screen. Plug device to your pc then enter:
Confirm pc reads phone and displays serial number before proceeding...
Code:
fastboot devices
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU.zip
If terminal shows it has completed successfully then reboot:
Code:
fastboot reboot
If terminal shows it didn't complete successfully then do not reboot but try again:
Code:
fastboot flash zip RUU.zip
I went through this last weekend for my K2CL because I was converting my device to f2fs and messed up in the process.
Sent from my C525c using Tapatalk

SHM said:
Well if you can extract the RUU from the .exe program then you can boot to your hboot then select fastboot from the screen. Plug device to your pc then enter:
Confirm pc reads phone and displays serial number before proceeding...
Code:
fastboot devices
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU.zip
If terminal shows it has completed successfully then reboot:
Code:
fastboot reboot
If terminal shows it didn't complete successfully then do not reboot but try again:
Code:
fastboot flash zip RUU.zip
I went through this last weekend for my K2CL because I was converting my device to f2fs and messed up in the process.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
OK well i'll use my computer under windows 7, but i know that when i extract the ruu from the .exe (using the folder temp, you know) the file can't be flash with recovery but i'll give a try with fastboot (fastboot devices always work) if this can work you'll be my heroe haha because i've tried so many things with the adb shell the recoveries, the flash with fastboot (which taught me some things about android) but nothing worked!

colton49 said:
OK well i'll use my computer under windows 7, but i know that when i extract the ruu from the .exe (using the folder temp, you know) the file can't be flash with recovery but i'll give a try with fastboot (fastboot devices always work) if this can work you'll be my heroe haha because i've tried so many things with the adb shell the recoveries, the flash with fastboot (which taught me some things about android) but nothing worked!
Click to expand...
Click to collapse
Yea, the RUU extracted is not made to be flashed in the custom recovery or any recovery for that matter. Must be flashed with the device in RUU mode as instructed in my last comment. If you are S-On then make sure you relock the bootloader first before doing it. If you are S-Off then it does not matter. It will fix your device. Like I said, I borked my partitions last weekend and the RUU fixed it right up for me with no problems. However, I used a decrypted RUU but the process is still the same.
Sent from my C525c using Tapatalk

SHM said:
Yea, the RUU extracted is not made to be flashed in the custom recovery or any recovery for that matter. Must be flashed with the device in RUU mode as instructed in my last comment. If you are S-On then make sure you relock the bootloader first before doing it. If you are S-Off then it does not matter. It will fix your device. Like I said, I borked my partitions last weekend and the RUU fixed it right up for me with no problems. However, I used a decrypted RUU but the process is still the same.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
okay thanks i'm gonna try this again and again if it does not work at the first shot! yes i'm S-ON and Unlocked.. ! okay you give me hope !!
i'll tell you if i succeed

SHM said:
Yea, the RUU extracted is not made to be flashed in the custom recovery or any recovery for that matter. Must be flashed with the device in RUU mode as instructed in my last comment. If you are S-On then make sure you relock the bootloader first before doing it. If you are S-Off then it does not matter. It will fix your device. Like I said, I borked my partitions last weekend and the RUU fixed it right up for me with no problems. However, I used a decrypted RUU but the process is still the same.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
to decrypt the RUU You use smthing on Ubuntu right ? or you tried something else because i guess it's better when decrypted

colton49 said:
to decrypt the RUU You use smthing on Ubuntu right ? or you tried something else because i guess it's better when decrypted
Click to expand...
Click to collapse
On linux in general and decrypting the RUU is way more complicated and difficult than it sounds. An encrypted RUU will do you just fine.
Sent from my C525c using Tapatalk

SHM said:
On linux in general and decrypting the RUU is way more complicated and difficult than it sounds. An encrypted RUU will do you just fine.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
ok i'll try with the encrypted and if it doesn't work after many tries i'll try to decrypt it! i'm gonna try all of this right now ! just have to remember where extract the ruu

SHM said:
On linux in general and decrypting the RUU is way more complicated and difficult than it sounds. An encrypted RUU will do you just fine.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
I've got a huge pb, it seems that i can't relock my bootloader and well i'm s-on...
because fastboot oem lockfail
even htc bootloader unlock fails when i put the phone in a recovery to be recognized.. ****.. but if i can lock it it'll work..

colton49 said:
I've got a huge pb, it seems that i can't relock my bootloader and well i'm s-on...
because fastboot oem lockfail
even htc bootloader unlock fails when i put the phone in a recovery to be recognized.. ****.. but if i can lock it it'll work..
Click to expand...
Click to collapse
What do you mean by putting the phone in "recovery"? You shouldn't be in your recovery when using fastboot. You should be in your bootloader. Power off device, then press and hold the volume down key and the power key. Release when you see your hboot appear. Using your volume keys to move up and down you want to highlight the option, fastboot. Hit the power button to select fastboot. You are now in fastboot mode. You will see fastboot in red text. Plug your device into your pc and you should now see, fastboot usb, in red text. Using the terminal on your pc proceed to lock your bootloader using fastboot. Then proceed with my instructions in the other post.
Sent from my C525c using Tapatalk

SHM said:
What do you mean by putting the phone in "recovery"? You shouldn't be in your recovery when using fastboot. You should be in your bootloader. Power off device, then press and hold the volume down key and the power key. Release when you see your hboot appear. Using your volume keys to move up and down you want to highlight the option, fastboot. Hit the power button to select fastboot. You are now in fastboot mode. You will see fastboot in red text. Plug your device into your pc and you should now see, fastboot usb, in red text. Using the terminal on your pc proceed to lock your bootloader using fastboot. Then proceed with my instructions in the other post.
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
yeah of course i did it. Being in the recovery was just a try with a toolkit which is used to relock.
i know how fastboot works but i've got error messages with fastboot oem lock and by flashing the ruu the last thing after the signature checking fails because of my bootloader unlocked i guess.