Database Info

htc one s brik problem [SOLVED]

Hi i have a big problem with my new htc one s
i follow all instructions: clear data, factory reset, install rom, then install boot.img
Roms boot until it shows wallpaper and top toolbar with the battery icon and time, then can read preparing phone storage.... and an error appears asking me to wait or close system process
The rom restarts and stucks at this point dont know what else do, i try installing stock recovery and clear data factory reset and try install with 3 versions of recovery whith same result, have tried some different roms and its the same.
Wonder if anyone knows what i have to do solve this..
Thankyou in advance.
--------------------------
solution on post #7

Moved To Q&A​
This is a development section, its not the place for questions.​

Which roms did you try to flash? Did you flash the correct boot.img
Sent from my HTC One S using XDA

thanks for your answer
Yes i flash [ROM][ICS] |June 13th| Energy™ -.¸¸.·´¯ Blue with the boot.img from the downloads
and [ROM] Ir2 1.78.401.2 - HTC One S Stock ROM DUO [Deodexed-Updated-Optimised]
When finish flasing from recovery reboot on fastboot and flash the boot.img and always is the same result.
I've tried to change to stock version of recovery and wipe all, reset to factory default then flash custom recovery and start the process but is the same.
when i whipe from stock or custom version of recovery there isn't any error message.
thankyou very much.

you don't flash the boot.img from recovery--read OP

boot.img
I flash it from fastboot not installing a zip from recovery. I also try installing by script like on [ROM][ICS] |June 14th| Energy™ -.¸¸.·´¯ Blue that there is an script that makes the installation always from fastboot

[solved]
Hi, find a way to make my htc one s woking again
This is the solution:
first i've to change my CID because my phone is from ORANGE spain and cannot flash a official RUU.
for this i follow this tutorial
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Second flash stock recovery and lock boot
finally i've downloaded the last europe RUU, and execute it.The process works like a charm and in 15 or 20 minutes my one s was working again.
Now i have lock boot, stock recovery and unrooted phone and have one question:
for root my phone again have to unlock and flash a custom recovery, and then.....
should I need to put back again stock recovery and lock boot for working an official RUU?? or can work without problems with unloked boot an custom recovery?
Thanks in advance.

Hey I have the exact same issue but running RUU didnt solve it. I have the US Tmobile Htc one s, S-off, supercid, hboot 1.14. I could load custom roms and mount usb storage only through recovery. my sd card does not show in fastboot. However, my phone never completely boots. It goes all the way to the lockscreen, allows me to pull the ring, then gets stuck on preparing phone storage. Flashing RUU does the same.
can anyone help?

joemanbui said:
Hey I have the exact same issue but running RUU didnt solve it. I have the US Tmobile Htc one s, S-off, supercid, hboot 1.14. I could load custom roms and mount usb storage only through recovery. my sd card does not show in fastboot. However, my phone never completely boots. It goes all the way to the lockscreen, allows me to pull the ring, then gets stuck on preparing phone storage. Flashing RUU does the same.
can anyone help?
Click to expand...
Click to collapse
i too have same prob tried all kinds of ruu's. been trying for 14 hours if you find soething please report how you did it

I have the same problem any ideas?
anyone know of any gurus in the forum knows how to fix
I've been trying for a month
any rom to put loads and after a 10-20sec reset

For you with sd-card problems, have you tried to flash stock recovery and then boot to bootloader and choose clear storage? It worked for me.
If you installed a RUU, ofcourse you already have stock recovery.
Sent from my One S using Tapatalk 4 Beta

I have the same problem, and decided to work on it today... I can say frustratingly i've not had ANY success in getting past the screen that pops up with the lock ring on the bottom...I've tried RUUs , the clear storage ... what is going on... I'm S-off as well so i really don't get why this would happen.

One S (s4)
twrp 2.5
S-on
T-mobile US
CM10.2
kernel 3.4
Hboot 2.15
openDsp v31.1.0.45.0815
current raido :1.11.50.05.28_10.27.50.08L
using the getvar method
i get this
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__203
using fastboot getvar version-main
Version-main : ( BLANK)
Click to expand...
Click to collapse
after following the steps for s-off it worked
the bootloader shows VLE PVT SHIP -S-OFF RL
CID-11111111
right after i followed the last step of the face palm method which was
boot into android and issue the 3 commands
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
Click to expand...
Click to collapse
i went into the bootloader confirmed everything then wen back to CM and it woudnt load
so i wiped everything and flashed a new version and an older 10.1 stable version which didnt work either
it would just freeze at the loading screen and restart
so i tried wiping everything and flash a stock RUU from HTC (t-mobile) 4.1.1
everything went off without a hitch
went to bootloader which showed a new version of the radio
tried to boot it up
and it did boot up but i coudnt go any further it just keeps saying
Preparing phone storage
then restarts
i tried wipe/data factory reset but it says cant mount SDCARD even though TWRP has no problem with wiping it

I have the same problem..
qwerty warrior said:
after following the steps for s-off it worked
the bootloader shows VLE PVT SHIP -S-OFF RL
CID-11111111
right after i followed the last step of the face palm method which was
i went into the bootloader confirmed everything then wen back to CM and it woudnt load
so i wiped everything and flashed a new version and an older 10.1 stable version which didnt work either
it would just freeze at the loading screen and restart
so i tried wiping everything and flash a stock RUU from HTC (t-mobile) 4.1.1
everything went off without a hitch
went to bootloader which showed a new version of the radio
tried to boot it up
and it did boot up but i coudnt go any further it just keeps saying
Preparing phone storage
then restarts
i tried wipe/data factory reset but it says cant mount SDCARD even though TWRP has no problem with wiping it
Click to expand...
Click to collapse
I have the exact same problem did you ever figure out a way of fixing it?

qwerty warrior said:
i went into the bootloader confirmed everything then wen back to CM and it woudnt load
so i wiped everything and flashed a new version and an older 10.1 stable version which didnt work either
it would just freeze at the loading screen and restart
so i tried wiping everything and flash a stock RUU from HTC (t-mobile) 4.1.1
everything went off without a hitch
went to bootloader which showed a new version of the radio
tried to boot it up
and it did boot up but i coudnt go any further it just keeps saying
Preparing phone storage
then restarts
i tried wipe/data factory reset but it says cant mount SDCARD even though TWRP has no problem with wiping it
Click to expand...
Click to collapse
exact same problem except i didnt flash a custom rom. i flashed a radio following this http://forum.xda-developers.com/showthread.php?t=1998270 ( i did everything that I was instructed to do in this page) then my wifi didnt work so i reflash the RUU. now im stuck in preparing storage which then lead to bootloop
found the solution
Originally Posted by muriani View Post
well, as a last resort, i set cid to t-mob010 (stock for my phone), ran the latest ruu for t-mobile, and same result.
I've given it up for lost.
Edit: Holy f*ckballs.
So, i didn't give up after all. Found a couple of other threads, and apparently yes, you have to relock, reset cid, and go s-on (fastboot oem writesecureflag 3) and then run the ruu.
I have a stock fresh tmous 4.1.1 one s now.

xxgummyxx said:
exact same problem except i didnt flash a custom rom. i flashed a radio following this http://forum.xda-developers.com/showthread.php?t=1998270 ( i did everything that I was instructed to do in this page) then my wifi didnt work so i reflash the RUU. now im stuck in preparing storage which then lead to bootloop
found the solution
Originally Posted by muriani View Post
well, as a last resort, i set cid to t-mob010 (stock for my phone), ran the latest ruu for t-mobile, and same result.
I've given it up for lost.
Edit: Holy f*ckballs.
So, i didn't give up after all. Found a couple of other threads, and apparently yes, you have to relock, reset cid, and go s-on (fastboot oem writesecureflag 3) and then run the ruu.
I have a stock fresh tmous 4.1.1 one s now.
Click to expand...
Click to collapse
thank you thanks !!!!!!! two days without finding the solution and in the last paragraph that I will write opened the sky, put it in s-on, Greetings

dosariland said:
thank you thanks !!!!!!! two days without finding the solution and in the last paragraph that I will write opened the sky, put it in s-on, Greetings
Click to expand...
Click to collapse
For about some days, I flash an RUU when I was still s-off and boot-unlocked, then I flash twrp-recovery, make the adb thinks with mmcblk* (dd flash) and flash again a RUU. As you can read here.
But same boot loop problem with "Preparing Phone Storage...".
Because dd flash (the mmcblk* file) under linux and with startet recovery did not solve my bootloop / prepairing sd card problem (I had still access to my sd card with twrp-recovery! All the time!) I really think about to enable s-on
I am only scared when I do:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
How can I re-enable s-off if my os still hangs on "Preparing Phone Storage" after putting s-on and try to flash an ruu to fix my bootloop/Preparing Phone Storage problem?
I did my s-off with rumrunner.
Would be very thankfull about help.
Greetings by I_did_it_just_tmrrow
you have to relock, reset cid, and go s-on (fastboot oem writesecureflag 3) and then run the ruu.
Click to expand...
Click to collapse
THX!!!
I leave superCID and it works! I hope my signal would be fine under stock.
THX a lot!
Greetings by I_did_it_just_tmrrow

[HELP] CWM Bootloop, Can't Access Bootloader Via ADB or VOL-

Things I have Done (In this Order):
Followed This Guide for Unlocking Bootloader and Flashing ClockworkMod Recovery
Unlocked Bootloader
Flashed ClockworkMod Recovery 5.8.3.1 Touch
Flashed the EU Radio from Here (Still using Stock ROM)
Flashed CyanogenMod 10 NIGHTLY 20121012 Build
Tried to Restore Nandroid Backup (To No Avail)
Flashed Ville-Z Kernel
Flashed CyanogenMod 9 NIGHTLY 20120917 Build (After CM10 didn't work)
Held down the VOL- Button while Rebooting to try to gain access to the Bootloader several times (To No Avail)
Used the ADB Reboot Bootloader Command while in CWM several times (To No Avail)
So, I decided to root my HTC One S today, because I have a Samsung Vibrant that is running CyanogenMod 7, and I really like the abilities that come with being Rooted. I Rooted my Samsung Vibrant myself with no issues, however it seems that my HTC One S is giving me a hard time.
I think the main problem is the fact that I didn't Flash the Boot.img file from the CyanogenMod ZIP, however, now that I am unable to access the Bootloader, I can't even attempt to do that.
Also, I got the CyanogenMod 10 Nightly to get to the Boot Screen when I first flashed it (I only did "Data/Factory Reset"), however, it got Stuck while Booting, so after 15 Minutes of waiting to see if it would proceed, I rebooted it, another 15 Minutes went by with it stuck, and after about 5 Reboots, I gave up, Booted into the Bootloader, hit "Recovery" and got into CWM. Did a "Data/Factory Reset," Wiped Cache Partiton, and Wiped /system, Tried to just Restore my Nandroid Backup, and then began the flickering while its Rebooting and the Bootloop.
After that, I got thrown back into CWM, and then I did a "Data/Factory Reset," Wiped Cache Partiton, and Wiped /system, and then flashed the CM10 Nightly again. Same result, Bootloop, Tried This Solution for trying to get out of the Bootloop, to No Avail.
Then I wiped /system, Data/Factory Reset, and Cache Partiton once again, Flashed the CM9 Nightly, and the same thing happened. It Reboots, screen flickers a few times, and then i'm back to CWM.
So, i'm stuck. I can use ADB with ClockworkMod Recovery, but I can't get into the Bootloader at all. I imagine that there is a way to Flash the Boot.img from CWM, but I have no idea how, nor have I found any Threads on the topic. I would appreciate if you guys could help me on this. I've spent several hours today trying to at least gain access to the Bootloader, but to No Avail. Oh, and sorry for the Wall of Text, I wanted to make sure I covered every angle.

Can this adb command get you into bootloader mode? Use while in CWM but might work while the phone is trying to boot a ROM as well.
adb reboot bootloader
There is a corresponding fastboot command as well, fastboot reboot bootloader or maybe it is fastboot reboot-bootloader.

frdd said:
Can this adb command get you into bootloader mode? Use while in CWM but might work while the phone is trying to boot a ROM as well.
adb reboot bootloader
There is a corresponding fastboot command as well, fastboot reboot bootloader or maybe it is fastboot reboot-bootloader.
Click to expand...
Click to collapse
As stated above, adb reboot bootloader can't get me into the Bootloader. Also, Fastboot doesn't work inside of CWM. I also just tried adb reboot bootloader and fastboot reboot-bootloader while its rebooting (Trying to load the ROM?) to No Avail.
I only get:
Code:
C:\Android>fastboot reboot-bootloader
< waiting for device >
And it hangs. This is the same result I get trying fastboot reboot-bootloader from inside of CWM.

WinterPhoenix96 said:
As stated above, adb reboot bootloader can't get me into the Bootloader. Also, Fastboot doesn't work inside of CWM. I also just tried adb reboot bootloader and fastboot reboot-bootloader while its rebooting (Trying to load the ROM?) to No Avail.
I only get:
Code:
C:\Android>fastboot reboot-bootloader
< waiting for device >
And it hangs. This is the same result I get trying fastboot reboot-bootloader from inside of CWM.
Click to expand...
Click to collapse
Ah sorry didnt see it:-/ actually scanned for it but missed it, I'm on Linux so looked for small letters
Anyways I checked out the CWM-Loop-DeLooper.zip you linked from that LG Connect 4G forum, this is what it does:
Code:
ui_print("Fix'in ****");
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
package_extract_file("recovery.img","/tmp/recovery.img");
run_program("/tmp/busybox", "dd", "if=/tmp/recovery.img", "of=/dev/block/mmcblk0p13");
delete("/tmp/recovery.img");
Basically it installs busybox which is a collection of system tools, then it flashes a recovery.img to /dev/block/mmcblk0p13. Not sure what is on that partition on the One S. This might have screwed things up further since I guess that the recovery.img in that file is not for the One S at all... this is the md5sum of the file, no results when gogling it: fb0db52d705df8bb220ca9f25e3a1f6a recovery.img
Hopefully HTC's S-ON saved you or maybe you have a CWM for the LG Connect 4G. This doesnt explain why you can't get into bootloader mode though. I'd say you should run a RUU but I think you have to be in bootloader or have the phone running for that. Did flashing the Ville-Z kernel work? I f so flash a ROM that is compatible with it. I think the most recent CM-10 builds aftera say 20121004 are not compatible any longer. If Ville-Z kernel didnt flash then you need to flash a ROM that matches the kernel you had before, maybe a stock or Sense-based ROM?

frdd said:
Ah sorry didnt see it:-/ actually scanned for it but missed it, I'm on Linux so looked for small letters
Anyways I checked out the CWM-Loop-DeLooper.zip you linked from that LG Connect 4G forum, this is what it does:
Code:
ui_print("Fix'in ****");
package_extract_file("busybox", "/tmp/busybox");
set_perm(0, 0, 0777, "/tmp/busybox");
package_extract_file("recovery.img","/tmp/recovery.img");
run_program("/tmp/busybox", "dd", "if=/tmp/recovery.img", "of=/dev/block/mmcblk0p13");
delete("/tmp/recovery.img");
Basically it installs busybox which is a collection of system tools, then it flashes a recovery.img to /dev/block/mmcblk0p13. Not sure what is on that partition on the One S. This might have screwed things up further since I guess that the recovery.img in that file is not for the One S at all... this is the md5sum of the file, no results when gogling it: fb0db52d705df8bb220ca9f25e3a1f6a recovery.img
Hopefully HTC's S-ON saved you or maybe you have a CWM for the LG Connect 4G. This doesnt explain why you can't get into bootloader mode though. I'd say you should run a RUU but I think you have to be in bootloader or have the phone running for that. Did flashing the Ville-Z kernel work? I f so flash a ROM that is compatible with it. I think the most recent CM-10 builds aftera say 20121004 are not compatible any longer. If Ville-Z kernel didnt flash then you need to flash a ROM that matches the kernel you had before, maybe a stock or Sense-based ROM?
Click to expand...
Click to collapse
Thanks for the Reply!
Well, if I have LG Connect 4G's CWM now, then its the exactly the same CWM I had before, ClockworkMod Recovery 5.8.3.1 Touch. I think its more likely that HTC's S-ON prevented the Kernel Flash. I'm not sure as to what Partition /dev/block/mmcblk0p13 is on the One S either. I'll look into that when I have a chance and update this Post, but I digress.
You do have to be in at least the Bootloader to run RUU, which I can't access, so that's out of the question at the moment.
I dont believe that Flashing the Ville-Z Kernel worked, because when I tried to Flash ViperOneS ROM (Which is supposedly compatible with it), I still had the same result.
I have not tried to Flash a Stock ROM however, because when I tried Restoring my Nandroid Backup, I still had the same result. I think I'll try to flash a scrubbed version or something of the Stock ROM however, once I get home, and see if that works. I'll try a few different other Sense-Based ROM's as well that are stated to be compatible with the Stock Kernel.
Sent from my SGH-T959 using xda app-developers app
UPDATE
I found out what the /dev/block/mmcblk0p13 Partition is. Its the Data Partition (/data) on the LG Connect 4G's Partition Structure.
Also, I found a ROM that may work Here. If we are even still going down the same path for Flashing ROM's, seeing as I've now gained access to the Bootloader (See Post #7)

WinterPhoenix96 said:
Thanks for the Reply!
Well, if I have LG Connect 4G's CWM now, then its the exactly the same CWM I had before, ClockworkMod Recovery 5.8.3.1 Touch. I think its more likely that HTC's S-ON prevented the Kernel Flash. I'm not sure as to what Partition /dev/block/mmcblk0p13 is on the One S either. I'll look into that when I have a chance and update this Post, but I digress.
You do have to be in at least the Bootloader to run RUU, which I can't access, so that's out of the question at the moment.
I dont believe that Flashing the Ville-Z Kernel worked, because when I tried to Flash ViperOneS ROM (Which is supposedly compatible with it), I still had the same result.
I have not tried to Flash a Stock ROM however, because wheb I tried Restoring my Nandroid Backup, I still had the same result. I think I'll try to flash a scrubbed version or something of the Stock ROM however, once I get home, and see if that works. I'll try a few different other Sense-Based ROM's as well that are stated to be compatible with the Stock Kernel.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
WOW WinterPhoenix96. I am having the EXACT same issue. I even tried a nandroid restore to no avail. Have you found a solution to this issue yet?
-M

Gained Access To Bootloader! How To Proceed?
mbolden said:
WOW WinterPhoenix96. I am having the EXACT same issue. I even tried a nandroid restore to no avail. Have you found a solution to this issue yet?
-M
Click to expand...
Click to collapse
Actually, I saw your Forum Post as well, and I Subscribed to it to see if you ever got a solution. XD But, apparently not yet, and your case was just a Little Bit different than mine, so I started my own Forum Post.
But, The Good News. I FINALLY was able to access the Bootloader! Here's the trick: Let The Battery Die, Then Turn It Back On While Holding The VOL- Button.
So, Bootloader Information, because I don't even want to touch it unless I know for sure how to Proceed:
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0004 <---Note: I've heard that Hboot Version 1.14 causes issues with RUU.
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Aug 14 2012, 18:01:48
So, How Should I Proceed? I've heard RUU won't work on this HBOOT Version anyway, so...
Also, Refer to Post #5's Update.

What issues are caused by hboot 1.14? I think you can never use a RUU to downgrade but always run your current version's RUU or newer. This could be said to be an issue though I guess since 2.31 is the newest RUU atm

WinterPhoenix96 said:
Actually, I saw your Forum Post as well, and I Subscribed to it to see if you ever got a solution. XD But, apparently not yet, and your case was just a Little Bit different than mine, so I started my own Forum Post.
But, The Good News. I FINALLY was able to access the Bootloader! Here's the trick: Let The Battery Die, Then Turn It Back On While Holding The VOL- Button.
So, Bootloader Information, because I don't even want to touch it unless I know for sure how to Proceed:
*** TAMPERED ***
*** UNLOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.14.0004 <---Note: I've heard that Hboot Version 1.14 causes issues with RUU.
RADIO-1.08ts.50.02.16
OpenDSP-v29.1.0.45.0622
eMMC-boot
Aug 14 2012, 18:01:48
So, How Should I Proceed? I've heard RUU won't work on this HBOOT Version anyway, so...
Also, Refer to Post #5's Update.
Click to expand...
Click to collapse
I am letting the battery drain now. So far the recovery screen has been up for days. LOL I cant even turn it off. comes right back on. After it dies I will try to get into fastboot.
-M

RUUs work in HBOOT 1.14.0004 or whatever HBOOT, for that matter, unless the HBOOT in the RUU is lower than yours. In that case, it won't let you flash the ROM.
@mbolden can't you use VOL UP, DOWN and POWER to turn the phone off in recovery?

mbolden said:
I am letting the battery drain now. So far the recovery screen has been up for days. LOL I cant even turn it off. comes right back on. After it dies I will try to get into fastboot.
-M
Click to expand...
Click to collapse
Yeah I had the same
thing. It was on for days on end, then it occurred to me to try that.
usaff22 said:
RUUs work in HBOOT 1.14.0004 or whatever HBOOT, for that matter, unless the HBOOT in the RUU is lower than yours. In that case, it won't let you flash the ROM.
@mbolden can't you use VOL UP, DOWN and POWER to turn the phone off in recovery?
Click to expand...
Click to collapse
Well, I've just heard a lot of people having problems with HBOOT 1.14.0004 and trying to do RUU. Apparently something to do with the Signature Verification Failing.
Also,I haven't tried that. It may work, if you want to look into it, @mbolden.
Sent from my SGH-T959 using xda app-developers app

Guys have you tried to unplug the battery instead of waiting for it to deplete? Looks easy enough to open it up: http://www.youtube.com/watch?v=b0jGY2N2h1U
---------- Post added at 10:25 PM ---------- Previous post was at 10:22 PM ----------
BTW there is a bug in CWM that causes the phone to start and boot into recovery when turned off if plugged into USB or charger

frdd said:
Guys have you tried to unplug the battery instead of waiting for it to deplete? Looks easy enough to open it up: http://www.youtube.com/watch?v=b0jGY2N2h1U
---------- Post added at 10:25 PM ---------- Previous post was at 10:22 PM ----------
BTW there is a bug in CWM that causes the phone to start and boot into recovery when turned off if plugged into USB or charger
Click to expand...
Click to collapse
Well you see, we (or at least I do) want to be able to do Root It, but without taking apart the phone in the process. I'd rather just wait for the battery to die than permanently break the phone's hardware if I take it apart and screw up.
Also, I am aware of the CWM Bug, however, apparently I forgot to mention it. Thanks!
Btw, nobody has answered How I Should Proceed yet. (Post #7)

usaff22 said:
RUUs work in HBOOT 1.14.0004 or whatever HBOOT, for that matter, unless the HBOOT in the RUU is lower than yours. In that case, it won't let you flash the ROM.
@mbolden can't you use VOL UP, DOWN and POWER to turn the phone off in recovery?
Click to expand...
Click to collapse
I can use the VOL rocker and the power button in recover. I let my battery drain (took 2 days)and tried to boot into fastboot. The screen flickered several times and then it went straight back into CWM. No idea what to do next. Seems that if I can't get into fastboot I am sunk. I cant boot ANY ROM I am stuck in recovery. WTF!??
Any suggestions? Anyone?
-M

frdd said:
Guys have you tried to unplug the battery instead of waiting for it to deplete? Looks easy enough to open it up: http://www.youtube.com/watch?v=b0jGY2N2h1U
---------- Post added at 10:25 PM ---------- Previous post was at 10:22 PM ----------
BTW there is a bug in CWM that causes the phone to start and boot into recovery when turned off if plugged into USB or charger
Click to expand...
Click to collapse
I am kind of glad that I didnt open it up. The batt depleted, but it still only boots into CWM.. AAAARRRRGGGHHH!!! (in the voice of the Hulk!)

mbolden said:
I am kind of glad that I didnt open it up. The batt depleted, but it still only boots into CWM.. AAAARRRRGGGHHH!!! (in the voice of the Hulk!)
Click to expand...
Click to collapse
That's really odd... It worked for me... Did you try several times with holding down VOL DOWN while its Booting? It may take a few tries. OH. And its kinda tricky, because If its plugged in while its booting, it will regardless boot to CWM.
I just turned it on without plugging it in, because your battery should be able to power up your phone for like 1 Minute before it legitimately dies, because some of the battery's power is still there, your phone just shuts off when it "detects" its out of battery (Battery Stats).
So, plug it in for just a few minutes to let it get just a bit of charge, then unplug it, let it "die," and then turn it back on while holding VOL DOWN. Then plug it in once it gets to the Bootloader. If it doesn't go to the Bootloader, Rinse and Repeat. Hopefully you'll be able to get into it eventually.

I'M IN!
WinterPhoenix96 said:
That's really odd... It worked for me... Did you try several times with holding down VOL DOWN while its Booting? It may take a few tries. OH. And its kinda tricky, because If its plugged in while its booting, it will regardless boot to CWM.
I just turned it on without plugging it in, because your battery should be able to power up your phone for like 1 Minute before it legitimately dies, because some of the battery's power is still there, your phone just shuts off when it "detects" its out of battery (Battery Stats).
So, plug it in for just a few minutes to let it get just a bit of charge, then unplug it, let it "die," and then turn it back on while holding VOL DOWN. Then plug it in once it gets to the Bootloader. If it doesn't go to the Bootloader, Rinse and Repeat. Hopefully you'll be able to get into it eventually.
Click to expand...
Click to collapse
I got in FINALLY.. I switched from CWM to TWRP (because I read that it will allow you to flash the radio) I tried to flash my radio using radio-0.16.31501S.16_2_10.22.31501S.10L.zip but no matter what it still says my radio version is 1.08ts. Does that sound right? At this point I just want to return to stock so my WiFi will work. This is how this whole fiasco started. :-/ I had the Viper ROM and my Wifi kept turning on and off and would never connect to ANYTHING. So I tried many other ROMS with the same no WiFi result.
When I tried to install the stock RUU, I re-locked the bootloader and installed the RUU only to get a signature err everytime. No one had a solution to the problem. I am kind of stuck (still).
-ideas anyone?

mbolden said:
I got in FINALLY.. I switched from CWM to TWRP (because I read that it will allow you to flash the radio) I tried to flash my radio using radio-0.16.31501S.16_2_10.22.31501S.10L.zip but no matter what it still says my radio version is 1.08ts. Does that sound right? At this point I just want to return to stock so my WiFi will work. This is how this whole fiasco started. :-/ I had the Viper ROM and my Wifi kept turning on and off and would never connect to ANYTHING. So I tried many other ROMS with the same no WiFi result.
When I tried to install the stock RUU, I re-locked the bootloader and installed the RUU only to get a signature err everytime. No one had a solution to the problem. I am kind of stuck (still).
-ideas anyone?
Click to expand...
Click to collapse
Don't know much about RUU's but:
* You can't downgrade anything with a RUU
* The newer RUUs like EU 2.21 and 2.31 will upgrade your HBoot to 1.14 which further locks down the ability to flash radios any other way than with an even newer RUU
* The RUU must be for your CID (~your carrier+country) so
* Bootloader must be relocked I think.
* Check md5sum of your RUU
* Might be good info re RUUs in the shipped ROMs thread in development..
TWRP cant flash a radio anymore than CWM can, they can both do it but you need a low enough Hboot (like 1.06 or 1.09 I think) and you need to fastboot boot your twrp/cwm.img like so:
Code:
fastboot boot cwm-touch.5.8.31-ville.img
Haven't tried TWRP myself, its possible that HTC Dumlock function in TWRP can be used to flash a radio. If youre on 1.08ts you probably have a new Hboot and thats one explanation why you couldn't downgrade your radio.
Most all WIFI problems on these boards are due to people not flashing the boot.img when flashing a new ROM. I would pick any ROM, try TWRP and Dumlock if getting to fastboot is still a rare precious occasion? Sure makes things hard when getting to bootloader is problematic...

frdd said:
Don't know much about RUU's but:
* You can't downgrade anything with a RUU
* The newer RUUs like EU 2.21 and 2.31 will upgrade your HBoot to 1.14 which further locks down the ability to flash radios any other way than with an even newer RUU
* The RUU must be for your CID (~your carrier+country) so
* Bootloader must be relocked I think.
* Check md5sum of your RUU
* Might be good info re RUUs in the shipped ROMs thread in development..
TWRP cant flash a radio anymore than CWM can, they can both do it but you need a low enough Hboot (like 1.06 or 1.09 I think) and you need to fastboot boot your twrp/cwm.img like so:
Code:
fastboot boot cwm-touch.5.8.31-ville.img
Haven't tried TWRP myself, its possible that HTC Dumlock function in TWRP can be used to flash a radio. If youre on 1.08ts you probably have a new Hboot and thats one explanation why you couldn't downgrade your radio.
Most all WIFI problems on these boards are due to people not flashing the boot.img when flashing a new ROM. I would pick any ROM, try TWRP and Dumlock if getting to fastboot is still a rare precious occasion? Sure makes things hard when getting to bootloader is problematic...
Click to expand...
Click to collapse
I can confirm that the Bootloader DOES need to be Re-Locked to perform an RUU.
I don't think the HBOOT Version matters with Flashing Your Radio. I've never heard anything about newer versions causing problems with that.
Don't know what HTC Dumlock does.
Wifi problems are 90% of the time caused by your Kernel or ROM. It CAN however be caused by a Bad Radio Flash.

Same Boat - all CWM, all the time
Took me 2 hours to find this thread...whew.
Any clear set of steps to take once back in bootloader? Safe to say flash TWRP, then reflash custom roms from there? Have rooted/installed custom roms on 5 previous phones without issue...until now. This. is. killing. me.
Thanks in advance for any further tips.

Okay guys im really stucked trying to repair the phone...

Its my sisters phone, currently stucked at bootsplash screen
I shall post the bootloader information first....
** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHOP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.0909_L
OpenDSP-vs29.1.0.45.0662
eMMc-boot
Jun 11 2012
CID returned is HTC_044... No matter how i flash recovery, the phone simply reboots... means i cant get into recovery mode.
I tried reflashing boot.img from vipers and relash recovery... doesnt work.
Right now, im trying to flash RUU via zip..... I have relocked my bootloader... Current status is that I managed to send the zip file over... but its stucked at writing for the past 10 mins...
This is the RUU where i extracted the rom.zip from
"RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed"
It should be the same as my current rom... which if i read correctly, it will not get updated? that I should use the newer 3.17 RUUs for asia in order to fix?
************************ Update ************************
Okay great... now after waiting for 4332 seconds for the writing part to finish... I knew its not going to work via waiting any longer... I unplugged the USB... the command prompt shows up an error (FAILED, too many links)... I attempted to restart the phone from the HTC logo and now it doesnt start at all... cant even get into bootloader... =.=
************************ Update ************************
Okay I've managed to save my phone using this method http://unlimited.io/qhsusbdload.htm
So now im back to square one... I can go bootloader... i unlocked it again... but i still cant go recovery...
************************ Update ************************
Now its back to being bricked again... as I was working on the phone outside when i managed to unbricked it. I choose to power off the phone from bootloader menu, thinking that I could work on it when I get home... alas, when i got home... the phone doesnt turn on... and i saw the dreaded QHSUSB_DLOAD thingy again...... omg... And the above method no longer works..........

kedirakevo said:
Its my sisters phone, currently stucked at bootsplash screen
I shall post the bootloader information first....
** TAMPERED ***
*** UNLOCKED ***
EVITA PVT SHOP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.0909_L
OpenDSP-vs29.1.0.45.0662
eMMc-boot
Jun 11 2012
CID returned is HTC_044... No matter how i flash recovery, the phone simply reboots... means i cant get into recovery mode.
I tried reflashing boot.img from vipers and relash recovery... doesnt work.
Right now, im trying to flash RUU via zip..... I have relocked my bootloader... Current status is that I managed to send the zip file over... but its stucked at writing for the past 10 mins...
This is the RUU where i extracted the rom.zip from
"RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed"
It should be the same as my current rom... which if i read correctly, it will not get updated? that I should use the newer 3.17 RUUs for asia in order to fix?
Click to expand...
Click to collapse
Stuck in a similar problem not sure what to do...

I dont understand why you guys want to relock and run the ruu... why not just flash a stock rom? Less headache
Sent from my One X using xda app-developers app

If you're relocked then you can't flash the zip. The ruu is an exe you need to run it with your phone in fastboot usb
Sent from my VENOMized HoxL

exad said:
I dont understand why you guys want to relock and run the ruu... why not just flash a stock rom? Less headache
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
how do i flash rom when recovery aint working?

area51avenger said:
If you're relocked then you can't flash the zip. The ruu is an exe you need to run it with your phone in fastboot usb
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1952426
Program says phone's bootloader must be locked in order to flash ruu zip

kedirakevo said:
how do i flash rom when recovery aint working?
Click to expand...
Click to collapse
Unlock boot loader again if its relocked and just fastboot flash twrp.. use the one click tool if you don't know how to flash recovery but as long as boot loader is unlocked you can flash recovery. Once you do, recovery will work again.
Sent from my One X using xda app-developers app

exad said:
Unlock boot loader again if its relocked and just fastboot flash twrp.. use the one click tool if you don't know how to flash recovery but as long as boot loader is unlocked you can flash recovery. Once you do, recovery will work again.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
which i stated in my first post that before relocking my bootloader... I have been reflashing the recovery many times but i cant boot into recovery mode....

kedirakevo said:
which i stated in my first post that before relocking my bootloader... I have been reflashing the recovery many times but i cant boot into recovery mode....
Click to expand...
Click to collapse
When you flash recovery is it successful? When you select recovery from boot loader what happens?
Which recovery and version are you flashing?
Sent from my One X using xda app-developers app

exad said:
When you flash recovery is it successful? When you select recovery from boot loader what happens?
Which recovery and version are you flashing?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
yea command prompt claimed its sucessful... I used the latest all in one toolkit where the creator claimed to use TWRP 2.4.1.0

kedirakevo said:
yea command prompt claimed its sucessful... I used the latest all in one toolkit where the creator claimed to use TWRP 2.4.1.0
Click to expand...
Click to collapse
Maybe A bad download. Download the latest twrp.
Make sure boot loader is unlocked and you have fastboot usb on in bootloader
Then within toolkit pick flash other recovery and manually select the one you downloaded. Then try selecting recovery in bootloader.
Sent from my One X using xda app-developers app

kedirakevo said:
Program says phone's bootloader must be locked in order to flash ruu zip
Click to expand...
Click to collapse
RUU is an exe the fact it creates a rom.zip is fairly well hidden. Are you running the exe or doing some other crazy thing?
You should not be flashing anything to your phone if you are confusing zip and exe's, it means you lack the basic understanding of computers to be able to complete these tasks without failing.
How did you try to flash the recovery? What recovery did you try to flash? What were the errors given?
EDIT: you should not be using one click tools.
Use fastboot and flash recovery yourself, it is a simple task.

exad said:
Maybe A bad download. Download the latest twrp.
Make sure boot loader is unlocked and you have fastboot usb on in bootloader
Then within toolkit pick flash other recovery and manually select the one you downloaded. Then try selecting recovery in bootloader.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
wish I could try that... it bricked now.

twistedddx said:
RUU is an exe the fact it creates a rom.zip is fairly well hidden. Are you running the exe or doing some other crazy thing?
You should not be flashing anything to your phone if you are confusing zip and exe's, it means you lack the basic understanding of computers to be able to complete these tasks without failing.
How did you try to flash the recovery? What recovery did you try to flash? What were the errors given?
EDIT: you should not be using one click tools.
Use fastboot and flash recovery yourself, it is a simple task.
Click to expand...
Click to collapse
the zip file can be obtained via temp folder of the windows directory when you run the exe file.
The all in one toolkit requires the zip so I got it done via that method...
Yes I know how to do it via command prompt but the toolkit is handy...
And lastly you can say my understanding of mobile phone system isnt complete but dont insult me saying I dont understand whats zip and exe......

Bricked? Exactly what is happening.
Sent from my One X using xda app-developers app

exad said:
Bricked? Exactly what is happening.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
beats me man... Told you, was trying to flash RUU through zip then it just hung there... but I managed to save my phone... I redownloaded and reflashed recovery as you advised but still no avail! Basically, back to square one....

kedirakevo said:
the zip file can be obtained via temp folder of the windows directory when you run the exe file.
The all in one toolkit requires the zip so I got it done via that method...
Yes I know how to do it via command prompt but the toolkit is handy...
And lastly you can say my understanding of mobile phone system isnt complete but dont insult me saying I dont understand whats zip and exe......
Click to expand...
Click to collapse
I know it can be obtained from temp folder.
Why go to the effort of getting the rom.zip to use in the toolkit when you could simply just run the RUU, which you had to do to get the rom.zip in the first place? Especially when it was failing, why push on with trying to use the toolkit instead of just using the RUU as it was intended by HTC?
I have not much knowledge of the toolkit, but when it flashes zip's is it for normal ROM's or for RUU rom.zip? The rom.zip is not in a format that can normally be used by most tools, it is not the same as flashing a custom ROM.
The toolkit is likely only for installing custom ROM's via pre installed TWRP and not compatible with rom.zip.
You said you were using a RUU zip and complaining it was failing, it appeared at face value you were confusing what the RUU even is.
I am still lost why running the RUU and grabbing the rom.zip from temp folder and then flashing in a toolkit was your chosen method. This just points more towards you are confused about what a RUU is.
I am sure the RUU would work if you just let it run like it is supposed to.
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
kedirakevo said:
was trying to flash RUU through zip then it just hung there.
Click to expand...
Click to collapse
Why?
Personally because of the state you have got the phone in to I would:
1)go get the correct tools. eg fastboot, unlockcode, twrp and rom
2)Ensure phone is charged
3)fastboot oem lock
4)Run RUU.. and try actually running it which means just click next and yes a lot.. no fancy going to temp folders and trying to incorrectly install rom.zip via random tools
5)fastboot flash unlocktoken Unlock_code.bin
6)fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
7)fastboot flash boot boot.img (from desired rom)
8)boot into recovery
9)mount USB and transfer desired ROM
10)wipe data and system
11)install ROM
12)reboot in to ROM.

twistedddx said:
I know it can be obtained from temp folder.
Why go to the effort of getting the rom.zip to use in the toolkit when you could simply just run the RUU, which you had to do to get the rom.zip in the first place? Especially when it was failing, why push on with trying to use the toolkit instead of just using the RUU as it was intended by HTC?
I have not much knowledge of the toolkit, but when it flashes zip's is it for normal ROM's or for RUU rom.zip? The rom.zip is not in a format that can normally be used by most tools, it is not the same as flashing a custom ROM.
The toolkit is likely only for installing custom ROM's via pre installed TWRP and not compatible with rom.zip.
You said you were using a RUU zip and complaining it was failing, it appeared at face value you were confusing what the RUU even is.
I am still lost why running the RUU and grabbing the rom.zip from temp folder and then flashing in a toolkit was your chosen method. This just points more towards you are confused about what a RUU is.
I am sure the RUU would work if you just let it run like it is supposed to.
---------- Post added at 02:33 PM ---------- Previous post was at 02:23 PM ----------
Why?
Personally because of the state you have got the phone in to I would:
1)go get the correct tools. eg fastboot, unlockcode, twrp and rom
2)Ensure phone is charged
3)fastboot oem lock
4)Run RUU.. and try actually running it which means just click next and yes a lot.. no fancy going to temp folders and trying to incorrectly install rom.zip via random tools
5)fastboot flash unlocktoken Unlock_code.bin
6)fastboot flash recovery openrecovery-twrp-2.4.1.0-evita.img
7)fastboot flash boot boot.img (from desired rom)
8)boot into recovery
9)mount USB and transfer desired ROM
10)wipe data and system
11)install ROM
12)reboot in to ROM.
Click to expand...
Click to collapse
well... as mentioned, would really love to follow your steps but.... its bricked now... again...
I did run RUU.exe once but it hung for 30 mins without activity... but then again that was when my bootloader was unlocked... then i read that i can relock and do it through ruu.zip instead.... so i went that route.......
Btw I did update my status on my first post...

kedirakevo said:
well... as mentioned, would really love to follow your steps but.... its bricked now... again...
I did run RUU.exe once but it hung for 30 mins without activity... but then again that was when my bootloader was unlocked... then i read that i can relock and do it through ruu.zip instead.... so i went that route.......
Btw I did update my status on my first post...
Click to expand...
Click to collapse
The least risky way would be to flash a stock ROM from here not an ruu. There are some untouched roms. I, myself have bricked running the telus ruu.
Sent from my One X using xda app-developers app

[Q] HTC One X doesn't work, error 7 on setup any(!) ROM

Posted my topic to incorrect thread and don't know how to move it, so re-post my question here.
Default [Q] HTC One X doesn't work, error 7 on setup any(!) ROM
Device: HTC One X AT&T USA, Android 4.0.4
HBoot 1.14 (unlocked), S-ON, cid: 11111111 (was CWS__001), rooted (CWM-SuperSU-v0.96)
Hi,
I have sim-unlocked AT&T HTC One X that I bought in USA last year and used it in 'as is' condition. A week ago it got to cyclical reboot. I made factory reset, but of course I lost all my data. In this case I decided to upgrade HBoot and setup latest CyanogenMod (yeap, I thought I have nothing to lose ).
I re-wrote cid to supercid, unlocked flashboot, rooted the phone... but made a mistake and flashed CyanogenMod boot.img before upgraded Hboot *facepalm*.
And now it's unable to load android (it just shows HTC logo with red warning text).
Of course, I tried to restore original Boot from backup, but this didn't help.
I'm able to open Bootloader and custom recovery menu (recovery-clockwork-6.0.3.1-evita.img), but unable to install any ROM (tried to use ROMs that are based on ICS, because my Hboot 1.14) - it always returns me error 7, even if all requirements are met. Tried to remove asserts from updater-script , but in this case it just shows 'Opening update package... Installing update... Installation aborted.'
I tried almost all that I found in web, used different backups and ROMs, but nothing helped.
I also tried to flash stock RUU (european, since I didn't find USA version - btw does it matter?) , but it getting Error 132 - Signature error.
Please could somebody help me to return my phone to a working state? Any advices are truly appreciated!
P.S. Unfortunately on one of the steps I lost my original backup (sdcard was formatted).
Thanks.
Click to expand...
Click to collapse
UPDATE:
I thought that since I have supercid I can use any RUU, but seems like I should use RUU exactly for CWS__001 or based on this thread I should make my phone S-Off and install any RUU. I cannot find any RUU for r CWS__001 in web, so if S-Off really helps, could you please advise correct RUU for my phone?
Thank you in advance!

Have you tried flashing a different recovery? It might help. Download TWRP 2.6 from here. Put it in your fastboot folder, connect your phone, open command prompt from within fastboot folder, issue following commands:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery and try to install your ROM again. Post results here.
Sent from my Evita
---------- Post added at 10:35 PM ---------- Previous post was at 10:34 PM ----------
PS. do not use an RUU while you have SuperCID and s-on, it will brick your phone. Try my above instructions first.
Sent from my Evita

timmaaa said:
Have you tried flashing a different recovery? It might help. Download TWRP 2.6 from here. Put it in your fastboot folder, connect your phone, open command prompt from within fastboot folder, issue following commands:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery and try to install your ROM again. Post results here.
Sent from my Evita
---------- Post added at 10:35 PM ---------- Previous post was at 10:34 PM ----------
PS. do not use an RUU while you have SuperCID and s-on, it will brick your phone. Try my above instructions first.
Sent from my Evita
Click to expand...
Click to collapse
This recovery seems pretty good, thank you!
And it looks like I understand why all ROMs gets me Error 7: all of them are for Endeavor, but my phone is Evita, isn't it?
I made all that you wrote:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
fastboot erase cache
fastboot reboot-bootloader​
Also I found this ROM (MIUIandroid 3.2.22 for the EVITA version of the HTC One X/L) and ran installation from recovery. And there are no Error 7! :victory: (of course I also flashed boot - fastboot flash boot boot.img)
The instruction for this ROM also says "Install gapps; Wipe Cache and Dalvik Cache". I installed gapps (MIUI.us_evita_v4_3.1.25_Eng_mirG.zip)
BUT unable to wipe Cache and Dalvik Cache: currently my phone says "Unable to mount '/cache' and '/data'".
How can I fix this?
Oh! And thank you for warn me about RUU installation!

Sigord said:
This recovery seems pretty good, thank you!
And it looks like I understand why all ROMs gets me Error 7: all of them are for Endeavor, but my phone is Evita, isn't it?
I made all that you wrote:
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
fastboot erase cache
fastboot reboot-bootloader​
Also I found this ROM (MIUIandroid 3.2.22 for the EVITA version of the HTC One X/L) and ran installation from recovery. And there are no Error 7! :victory: (of course I also flashed boot - fastboot flash boot boot.img)
The instruction for this ROM also says "Install gapps; Wipe Cache and Dalvik Cache". I installed gapps (MIUI.us_evita_v4_3.1.25_Eng_mirG.zip)
BUT unable to wipe Cache and Dalvik Cache: currently my phone says "Unable to mount '/cache' and '/data'".
How can I fix this?
Oh! And thank you for warn me about RUU installation!
Click to expand...
Click to collapse
Holy crap you are so lucky you didn't brick your phone by flashing those Endeavoru ROMs. Yes, you have an Evita, it'll say that at the top of your bootloader. Don't ever flash Endeavoru ROMs again, you could brick. Only ever download your ROMs from our forum, go here for Sense ROMs or here for aosp ROMs. Don't ever download from any other forum or any other site.
I'm honestly not sure why it can't mount cache/dalvik cache though. Did you use the advanced wipe feature?
Sent from my Evita

timmaaa said:
Holy crap you are so lucky you didn't brick your phone by flashing those Endeavoru ROMs. Yes, you have an Evita, it'll say that at the top of your bootloader. Don't ever flash Endeavoru ROMs again, you could brick. Only ever download your ROMs from our forum, go here for Sense ROMs or here for aosp ROMs. Don't ever download from any other forum or any other site.
I'm honestly not sure why it can't mount cache/dalvik cache though. Did you use the advanced wipe feature?
Sent from my Evita
Click to expand...
Click to collapse
Yes, I used 'Wipe cache/Dalvik' button after installation and additionally 'Advanced wipe > Dalvik cache, Cache'.
After gaps installation it shows only "E:Unable to mount '/data'"

So the gapps installation failed?
Sent from my Evita

timmaaa said:
So the gapps installation failed?
Sent from my Evita
Click to expand...
Click to collapse
Installation says "Successful" but it shows "E:Unable to mount '/data'" in logs.
Also I'm getting the same issue when trying to wipe dalvik cache and cache.

It sounds like the recovery is needing a valid /data partition before it will let you flash.
Sent from my HTC One X using xda premium

Venomtester said:
It sounds like the recovery is needing a valid /data partition before it will let you flash.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Now on loading the phone displays colored X like in Nexus but it doesn't load (of course).
How can I set a valid /data partition?

Sigord said:
Yes, I used 'Wipe cache/Dalvik' button after installation and additionally 'Advanced wipe > Dalvik cache, Cache'.
After gaps installation it shows only "E:Unable to mount '/data'"
Click to expand...
Click to collapse
Try to manually mount it by clicking the second button from the bottom left and checking everything then reflash
You may not be able to check it
-Sugardaddy

Arrow44 said:
Try to manually mount it by clicking the second button from the bottom left and checking everything then reflash
You may not be able to check it
-Sugardaddy
Click to expand...
Click to collapse
Unfortunately I'm able to check Cache, sdcard and System in Mount menu, but not Data.

You could try formatting your sd card. Backup any important data first obviously.
Sent from my Evita

timmaaa said:
You could try formatting your sd card. Backup any important data first obviously.
Sent from my Evita
Click to expand...
Click to collapse
I formatted the sd card, but all the same unable to mount \data.
I also tried to re-install my ROM zip and gapps zip but this didn't help.

Did a factory reset through TWRP, it mounted \data and now my phone is alive!
Thank you guys for all your help!!!

Ok good. Just a note: before flashing a ROM, always wipe cache/dalvik cache/factory reset/system.
Sent from my Evita

timmaaa said:
Ok good. Just a note: before flashing a ROM, always wipe cache/dalvik cache/factory reset/system.
Sent from my Evita
Click to expand...
Click to collapse
Thank you!
And just to be sure, what are my future steps if I want to flash any ROM on Android 4.2 or higher (For example, CM 10.1)?
Could you please take a look on the steps below and tell me if I missed something or understood wrong?
1. Do S-OFF based on [S-Off] Facepalm S-Off for HTC One XL
2. Load in fastboot mode and re-lock fastboot (fastboot oem lock)
3. Go to recovery and do full wipe
4. Update to 3.18 RUU by running its .exe.
If I understand correctly, this should upgrade my HBoot and Radio and get me official HTC ROM with JB 4.1.1 (is this safely with SuperCID and S-OFF?)
6. Unlock bootloader (fastboot flash unlocktoken Unlock_code.bin)
5. Downgrade touchscreen firmware.
6. Download last stable version of CM and the appropriate gapps and push it to sdcard
7. Go to recovery and create a backup
8. Do a full wipe
9. Install CM zip from sdcard
10. Install gapps
11. Flash boot (fastboot flash boot boot.img)
Thank you in advance!
PS: Probably you can advise me any other stable ROM?

Sigord said:
Thank you!
And just to be sure, what are my future steps if I want to flash any ROM on Android 4.2 or higher (For example, CM 10.1)?
Could you please take a look on the steps below and tell me if I missed something or understood wrong?
1. Do S-OFF based on [S-Off] Facepalm S-Off for HTC One XL
2. Load in fastboot mode and re-lock fastboot (fastboot oem lock)
3. Go to recovery and do full wipe
4. Update to 3.18 RUU by running its .exe.
If I understand correctly, this should upgrade my HBoot and Radio and get me official HTC ROM with JB 4.1.1 (is this safely with SuperCID and S-OFF?)
6. Unlock bootloader (fastboot flash unlocktoken Unlock_code.bin)
5. Downgrade touchscreen firmware.
6. Download last stable version of CM and the appropriate gapps and push it to sdcard
7. Go to recovery and create a backup
8. Do a full wipe
9. Install CM zip from sdcard
10. Install gapps
11. Flash boot (fastboot flash boot boot.img)
Thank you in advance!
PS: Probably you can advise me any other stable ROM?
Click to expand...
Click to collapse
You've done very well but if you get s-off first you can actually forget some of those steps. Follow the below steps.
1. Do S-OFF based on [S-Off] Facepalm S-Off for HTC One XL
2. Update to 3.18 RUU by running its exe file. This will update your phone to 2.14 hboot, and stock at&t ROM, and stock recovery. Safe to run with SuperCID as long as you s-off first.
3. Flash TWRP 2.6 again as detailed earlier.
4. Go into recovery and create a backup.
8. Do a full wipe
9. Install ROM zip from sdcard.
10. Install appropriate gapps.
Because you'll have s-off first, you don't need to relock your bootloader before the RUU. You will also not have to flash the boot.img from fastboot anymore. Part of the beauty of having s-off.
I can't really advise any ROMs. It's against the rules to ask which ROM is best/favorite/most stable, therefore I can't really answer that question. I'd just suggest having a look at a few ROMs, checking out any bugs that are noted in the first few posts, and reading some user connects to get an idea of what's working and what's not.
Sent from my Evita

timmaaa, thank you so much!
Currently I've flashed CM 10.0 (last stable), but when I'll be ready to S-OFF I'll follow your steps.
Thank you once again for your help!

No problems at all, you're welcome.
PS. If someone helps you on here, push the thanks button.
Sent from my Evita

Can't flash an OS/ROM

Okay so I rooted my one sv just fine and I went to put it back to stock I accidentally wiped the os off of it and for the past few days Iv'e tried everything to put a stock rom back on it but to no prevail. It fails when I flash a rom from my sdcard, adb sideload doesn't seem to work, when I try to fastboot flash a rom.zip it says "FAILED (remote: not allowed), and some other stuff as well that has not worked. My drivers are up to date, adb/fastboot works fine, I can still boot into twrp recovery mode, and my bootloader is unlocked (but still s-on). My rom backup got deleted but I have a stock rom of my device I downloaded that I know works. But as for now if I try to reboot the system it goes into a loop and twrp recovery says I still don't have an os.
Phone info: HTC One SV Boost mobile
***TAMPERED***
***UNLOCKED***
K2_CL PVT SHIP S-ON RL
HBOOT - 2.00.0000
RADIO - 1.12.50.0516
OpenDSP - v9.2.0268.1214
eMMC - boot
Jun 19 2013, 18:53:06:-1
If someone could help or give advice or something that would be more then appreciated. I'm not overly a noob with this but I still don't know everything just right now I'd be just happy with it booting into something other then twrp recovery or bootloader. Thanks in advance!

Because you are S-On you have to flash the boot.img separate through fastboot. Extract the boot.img from this Rom. Then redo the process again and afterwards flash the boot.img through fastboot.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 09:05 PM ---------- Previous post was at 09:02 PM ----------
Actually, because you do not have an OS... Try flashing the boot.img first. You are the first I have heard of doing this by accident lol.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Let me know if this works?
Sent from my C525c using XDA Premium 4 mobile app

First Install the rom then extract boot.img from the rom you installed put it in your adb folder run "fastboot flash boot booot.img"

Modding.MyMind said:
Because you are S-On you have to flash the boot.img separate through fastboot. Extract the boot.img from this Rom. Then redo the process again and afterwards flash the boot.img through fastboot.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 09:05 PM ---------- Previous post was at 09:02 PM ----------
Actually, because you do not have an OS... Try flashing the boot.img first. You are the first I have heard of doing this by accident lol.
Sent from my C525c using XDA Premium 4 mobile app
---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------
Let me know if this works?
Sent from my C525c using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried this in a couple different ways: I did what you just said where I flashed the boot.img before flashing the rom in recovery then flashed the boot.img after and rebooted (it was still looping) then I put my sdcard in my computer extracted the boot file to my fastboot folder (again) then deleted it from the zip file and went back into recovery to flash but before I flashed it the second time I wiped everything (cache,data system,int_sd,ect.) then after flashing I hit reboot and it said "my phone wasn't rooted do you want to install superSU?" but either way if i installed it or not it didn't do anything. So is there some other method? or any way I could get S-OFF without an os?

aRiaL_Snip3s said:
Okay so I rooted my one sv just fine and I went to put it back to stock I accidentally wiped the os off of it and for the past few days Iv'e tried everything to put a stock rom back on it but to no prevail. It fails when I flash a rom from my sdcard, adb sideload doesn't seem to work, when I try to fastboot flash a rom.zip it says "FAILED (remote: not allowed), and some other stuff as well that has not worked. My drivers are up to date, adb/fastboot works fine, I can still boot into twrp recovery mode, and my bootloader is unlocked (but still s-on). My rom backup got deleted but I have a stock rom of my device I downloaded that I know works. But as for now if I try to reboot the system it goes into a loop and twrp recovery says I still don't have an os.
Phone info: HTC One SV Boost mobile
***TAMPERED***
***UNLOCKED***
K2_CL PVT SHIP S-ON RL
HBOOT - 2.00.0000
RADIO - 1.12.50.0516
OpenDSP - v9.2.0268.1214
eMMC - boot
Jun 19 2013, 18:53:06:-1
If someone could help or give advice or something that would be more then appreciated. I'm not overly a noob with this but I still don't know everything just right now I'd be just happy with it booting into something other then twrp recovery or bootloader. Thanks in advance!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2450868
[almostRUU][K2_CL]&[How To Update After Moonshine S-Off]
Go here and download the twrp twrp recovery backup I have posted and just restore through recovery
If you are not able to side mount just take out the microSD of your device and place it a card reader of some kind on your computer.
Then place it back in the devices and restore
NOTE:
there is a file in the back up named boot.emmc.win
Rename it to boot.img
And fastboot flash boot boot.img
Fastboot reboot recovery
Then restore the backup from microSD card

russellvone said:
http://forum.xda-developers.com/showthread.php?t=2450868
[almostRUU][K2_CL]&[How To Update After Moonshine S-Off]
Go here and download the twrp twrp recovery backup I have posted and just restore through recovery
If you are not able to side mount just take out the microSD of your device and place it a card reader of some kind on your computer.
Then place it back in the devices and restore
NOTE:
there is a file in the back up named boot.emmc.win
Rename it to boot.img
And fastboot flash boot boot.img
Fastboot reboot recovery
Then restore the backup from microSD card
Click to expand...
Click to collapse
You are a wizard! I can't thank you enough

You might notice it's ICS backup, but as long as you do not mess with anything in the system
Just flash stock recovery from that folder after renaming it of course...
Relock your bootloader
Then accept all updates do you can have JB again

Yeah I just installed the latest version again and it works like the day I got it. So I can go back in and unlock bootloader and S-OFF and whatever else again? And thanks again

aRiaL_Snip3s said:
Yeah I just installed the latest version again and it works like the day I got it. So I can go back in and unlock bootloader and S-OFF and whatever else again? And thanks again
Click to expand...
Click to collapse
Yes, you can. Just make another backup and save a copy on your computer before you do anything crazy.
@russellvone - good job buddy.. Didn't even think about using a backup. But then again - first time I have seen a situation like this. So noted for myself lol :good:

aRiaL_Snip3s said:
Yeah I just installed the latest version again and it works like the day I got it. So I can go back in and unlock bootloader and S-OFF and whatever else again? And thanks again
Click to expand...
Click to collapse
Can you edit your first posts'
Title please?
Just add
[SOLVED] to the beginning