Database Info

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

[Q] Evita with 2.14 hboot rom flashing issues

Hi,
I've been looking for a solution to get a ROM to work on my phone with no success for the last few days, and I wonder if anyone knew if there is anything I can try to make it work again.
Code:
Rogers Evita
S-ON
HBOOT 2.14.0000
RADIO 0.23a.32.09.29
I put the phone in bootloop by flashing a Endeavour boot.img to it (stupid, yes...), and I'm now trying to get any ROM to work on it.
Here are the steps I tried to install a custom ROM :
Unlocked the bootloader with HtcDev
Flashed TWRP (tried 2.5.0.0 and 2.4.1.0)
Pushed a ROM zip with ADB (Tried CyanogenMod for Evita 10.0 and 10.1-20130813, and Calkulin's one xl ROM v 1.2)
Wiped Cache, Dalvik Cache and Facotry Reset from TWRP
Install ROM from TWRP
TWRP consistently says 'E:Unable to mount /sdcard' when wiping cache and then 'error flashing zip <name-of-the-rom>' when installing.
I also tried to install a stock ROM with the following steps
Relock bootloader
Download stock ROM. The closest I found from mine is 'RUU_Evita_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe'
Launch it from a windows machine
The installer fails and gives me an error 155.
I also tried to retrieve the rom from this installer via the %TEMP% directory, and to install it with Hasoon's Evita toolkit. The installation also fails and gives me 12 'signature' errors.
Lastly, I also tried without success to downgrade my hboot with JET (jet-evita-0.3.3b). The process loops at 'Failed to flash HBoot!!' despite the fact I tried multiple cable / USB ports combinations. The 'jet -u' command worked to unbrick the phone, and the bootloader now works.
Do you guys know if there is something I can try to get a ROM to work ?
Thanks for your help

Well, it seems your original problem was that you didn't flash boot image. What you're going to want to do now is
1. Unlock through HTC dev.
2. Find rom you want
3. Extract boot image and flash via fastboot
4. S-Off so you won't have to flash boot image again.
Sent from my evita

pigeonagressif said:
Hi,
I've been looking for a solution to get a ROM to work on my phone with no success for the last few days, and I wonder if anyone knew if there is anything I can try to make it work again.
Code:
Rogers Evita
S-ON
HBOOT 2.14.0000
RADIO 0.23a.32.09.29
I put the phone in bootloop by flashing a Endeavour boot.img to it (stupid, yes...), and I'm now trying to get any ROM to work on it.
Here are the steps I tried to install a custom ROM :
Unlocked the bootloader with HtcDev
Flashed TWRP (tried 2.5.0.0 and 2.4.1.0)
Pushed a ROM zip with ADB (Tried CyanogenMod for Evita 10.0 and 10.1-20130813, and Calkulin's one xl ROM v 1.2)
Wiped Cache, Dalvik Cache and Facotry Reset from TWRP
Install ROM from TWRP
TWRP consistently says 'E:Unable to mount /sdcard' when wiping cache and then 'error flashing zip <name-of-the-rom>' when installing.
I also tried to install a stock ROM with the following steps
Relock bootloader
Download stock ROM. The closest I found from mine is 'RUU_Evita_Rogers_WWE_1.94.631.3_Radio_0.18as.32.09.28L_10.103.32.24L_release_268972_signed.exe'
Launch it from a windows machine
The installer fails and gives me an error 155.
I also tried to retrieve the rom from this installer via the %TEMP% directory, and to install it with Hasoon's Evita toolkit. The installation also fails and gives me 12 'signature' errors.
Lastly, I also tried without success to downgrade my hboot with JET (jet-evita-0.3.3b). The process loops at 'Failed to flash HBoot!!' despite the fact I tried multiple cable / USB ports combinations. The 'jet -u' command worked to unbrick the phone, and the bootloader now works.
Do you guys know if there is something I can try to get a ROM to work ?
Thanks for your help
Click to expand...
Click to collapse
TWRP versions 2.4.x and 2.5.x are riddled with bugs so that's why the ROM wouldn't flash.
You'll need to unlock your bootloader, then download TWRP 2.6 from here. Put the TWRP file in your fastboot folder, connect your phone, open command prompt from within fastboot folder, and issue these commands:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Extract the boot.img from the ROM zip and put that in your fastboot folder, we'll come back to that in a minute.
Now you can enter recovery, make a backup, perform a full wipe (cache/dalvik/factory reset/system), install ROM, reboot to bootloader, make sure phone is connected and it says fastboot usb on the screen, issue this command:
fastboot flash boot boot.img
(You have to do this every time you want to change ROMs because you're s-on)
Reboot phone.
Sent from my Evita

Thank you timmaaa and RollTribe for your quick answer !
I unlocked my bootloader, downloaded TWRP 2.6 and issued :
Code:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
fastboot erase cache
fastboot reboot-bootloader
Then tried to do a full wipe, but it failed :
Code:
Formatting cache using mke2efs...
Done.
Formatting data using mke2fs...
Done.
E:Unable to mount '/sdcard'
Updating partition details...
E:Unable to mount '/sdcard'
E:Unable to mount storage.
Rom installation failed with a similar log :
Code:
E:Unable to mount '/sdcard'
Error flashing zip '/sdcard/cm-10.1-20130813-NIGHTLY-evita.zip'
Updating partition details...
E:Unable to mount '/sdcard'
E:Unable to mount storage.
I've looked for a solution to the possible sdcard corruption problem, but all the posts I see link to a dead thread from team nocturnal of which I can't post the url.
There is an associated youtube video (again, can't post url but it is named 'How to Fix corrupt/unmountable internal storage on the HTC One X'), but it is not of much help without the 'recovery.img' file they use.
Is there another way to solve the sdcard issue ?
Thanks again

Ok, in fact the fix for the sd card was easy!
There is an option to wipe the sd card in TWRP that I had missed. When this was done, everything worked!
I now have a working 10.1 CM!
Thanks again

Glad we could be of help!
Sent from my evita

pigeonagressif said:
Ok, in fact the fix for the sd card was easy!
There is an option to wipe the sd card in TWRP that I had missed. When this was done, everything worked!
I now have a working 10.1 CM!
Thanks again
Click to expand...
Click to collapse
i faced the same problem
its solved by formatting sdcard0
tnx

rasoulcarrera said:
i faced the same problem
its solved by formatting sdcard0
tnx
Click to expand...
Click to collapse
Are you aware that you're replying to a thread that's 18 months old?

Yes!
And keep it in ur mind people's won't get same problems just in same time !
Isn't it?

[Q] AT&T HTC One X Unable to get past hboot/fastboot

Hi - first time posting, but I've benefited from many a XDA thread in the past. I'm hopeful that someone can help me.
I tried to put CyanogenMod on my AT&T HTC One X, and was able to unlock the bootloader and put a new boot/recovery image on it. After that, I got into a boot loop and haven't been able to get into recovery since. I've tried flashing new boot.img, new recovery (CyanogenMod and TWRP) and even though I can pause the boot loop to get to the bootloader, it won't let me into recovery.
HBOOT is 2.14, and I can get fastboot connectivity from my computer.
Any ideas/help?

Try flashing TWRP recovery again via fastboot, then I've that's finished flashing give this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now try to enter recovery.
Sent from my Evita

timmaaa said:
Try flashing TWRP recovery again via fastboot, then I've that's finished flashing give this command:
fastboot erase cache
Then:
fastboot reboot-bootloader
Now try to enter recovery.
Sent from my Evita
Click to expand...
Click to collapse
Just tried that, and no dice. Just keeps on rebooting. If I select the RECOVERY option, it just reboots again - never enters recovery.

You might need to RUU, are you s-off?
Also, where are you downloading TWRP from?
Sent from my Evita

timmaaa said:
You might need to RUU, are you s-off?
Sent from my Evita
Click to expand...
Click to collapse
No, not s-off. I tried that, but I can't get it to boot into Android (after I flash the RUU zip and try to boot, it shows "FAILED (status read failed (Too many links))".

jwallaceks said:
No, not s-off. I tried that, but I can't get it to boot into Android (after I flash the RUU zip and try to boot, it shows "FAILED (status read failed (Too many links))".
Click to expand...
Click to collapse
An RUU isn't a zip, it's an exe program. If you don't have s-off you shouldn't do it anyway.
Sent from my Evita

timmaaa said:
An RUU isn't a zip, it's an exe program. If you don't have s-off you shouldn't do it anyway.
Click to expand...
Click to collapse
Yes, if you are s-on and try to run the 3.18 RUU, you will brick. You can't run an older RUU, due to your hboot version (2.14) and s-on.

timmaaa said:
Also, where are you downloading TWRP from?
Sent from my Evita
Click to expand...
Click to collapse
So, I downloaded a fresh version of TWRP per the Evita guide on CyanogenMod, and was able to get into recovery. Thanks for the tip!
Problem is, now I'm unable to flash a ROM because I can't mount /sdcard. I've tried other recoveries, but none of them will mount it, either. Tips?

jwallaceks said:
So, I downloaded a fresh version of TWRP per the Evita guide on CyanogenMod, and was able to get into recovery. Thanks for the tip!
Problem is, now I'm unable to flash a ROM because I can't mount /sdcard. I've tried other recoveries, but none of them will mount it, either. Tips?
Click to expand...
Click to collapse
Did you do a factory reset from bootloader? If so, you've corrupted it and it'll need to be formatted. Go into TWRP recovery, connect to pc, select mount, then mount usb storage. Now you'll need to format it in Windows to fat32 format.
Sent from my Evita

timmaaa said:
Did you do a factory reset from bootloader? If so, you've corrupted it and it'll need to be formatted. Go into TWRP recovery, connect to pc, select mount, then mount usb storage. Now you'll need to format it in Windows to fat32 format.
Sent from my Evita
Click to expand...
Click to collapse
That did it! I'm up and running, now! Thanks for all your help!

Cool, no worries. Just remember never to do a factory reset from bootloader, only do that in recovery.
Sent from my Evita

[Q] Help!! Can't flash new ROMs!

Hey guys, I'm on an HTC One X (AT&T) (evita). I'm currently running ViperXL, but it's very glitchy and often restarts or loses signal. I was previously running CM10 and went through a bit of trouble flashing this ROM. I kept getting the message "Installation Aborted" with no status error when i tried to flash and am experiencing the same problem now. I know i've been using the correct ROMs for the evita version not the endeavoru version (or however it's spelled). I think what I did when I transitioned from CM10 to ViperXL was factory reset from the bootloader (accidentally pressed the volume button too many times), then reloaded CWM onto my phone, factory reset, wiped the cache/dalvik, and flashed. But, now I'm getting the installation aborted messages again and I don't plan on factory resetting (i doubt that helped in the process before anyway). I'm thinking that I would need to unroot then reroot to fix this problem, but I'm fairly noob so I'm not sure. I also believe that I lost the back up of the stock ROM and i'm not sure how much that has screwed me over.

Never factory reset from bootloader, all it does is corrupt your sd card. Please provide more details, what are your current bootloader details? Which recovery version are you using?
Sent from my Evita

timmaaa said:
Never factory reset from bootloader, all it does is corrupt your sd card. Please provide more details, what are your current bootloader details? Which recovery version are you using?
Sent from my Evita
Click to expand...
Click to collapse
Yeah haha factory resetting was a complete accident
my bootloader reads:
****tampered****
****unlocked****
evita pvt ship s-on rl
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendsp-v29.1.0.45.0622
emmc-boot
and im running clockwork mod v5.8.3.1 touch

Try changing recovery to TWRP, I'm not sure if it's going to help but it's worth a shot. Here's how:
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.
Sent from my Evita

timmaaa said:
Try changing recovery to TWRP, I'm not sure if it's going to help but it's worth a shot. Here's how:
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.
Sent from my Evita
Click to expand...
Click to collapse
I followed these steps but I cannot create a backup of my current rom in TWRP. It says its unable to locate the storage device and mount /cache

Have you formatted your sd card since corrupting it?
Sent from my Evita

timmaaa said:
Have you formatted your sd card since corrupting it?
Sent from my Evita
Click to expand...
Click to collapse
No, did the "erase cache" command cause the problem im having with my phone being unable to mount the cache?

No it shouldn't matter, so you're saying you haven't formatted the sd card since corrupting it? You'll need to do that.
Sent from my Evita

timmaaa said:
No it shouldn't matter, so you're saying you haven't formatted the sd card since corrupting it? You'll need to do that.
Sent from my Evita
Click to expand...
Click to collapse
How do you format the sd card?

Enter TWRP recovery, select mount from the menu, connect phone to pc, select mount usb storage, the card will now show up in Windows, try to access it and it'll prompt you to format it, select fat32 format and wait for it to finish.
Sent from my Evita

timmaaa said:
Enter TWRP recovery, select mount from the menu, connect phone to pc, select mount usb storage, the card will now show up in Windows, try to access it and it'll prompt you to format it, select fat32 format and wait for it to finish.
Sent from my Evita
Click to expand...
Click to collapse
I cant access the SD card. I get a "found new hardware" notification for an "htc mtp device" but I'm not sure how to access it. Its not showing up as removable storage. I'm on windows XP, should i try on a mac?

[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.