Okay so if you are like me and have installed the OTA Update or ran the 3.18 ruu with an S-On Device chances are You are currently hard bricked which in most cases leaves 4 options, Option 1. Try to get a replacement through the carrier or Manufacturer Option 2. Send it off for a repair or Option 3 try and fix it yourself. Option 4 Toss the device and look elsewhere.
I Personally am going with Option 3 and am attempting to figure out a working Unbrick Method that does not require a RIFF box so with that said i will be working in this thread in an effort to get an unbrick project working. Feel free to add your knowledge, input, and advice in the proceeding posts below.
Please Note if you are using Windows 8 you will need to disable driver signature enforcement, while there are many ways to do this by far the easiest way is to open an Elevated Command Prompt and enter
Code:
bcdedit /set {globalsettings} advancedoptions true
when you restart your Computer choose option 7. To Disable Advanced Boot Options Enter
Code:
bcdedit /set {globalsettings} advancedoptions false
I suggest that you try reading here. I hard bricked my device before while trying to downgrade my HBOOT version from 1.14 to 1.09.
http://forum.xda-developers.com/showthread.php?t=2156231
To sum it up, he could still access his bootloader, but couldn't flash anything. By accessing rebootRUU, he managed to place his phone into a brick mode which allowed Linux to recognize and write to the boot partition. To enter that sort of brick mode, he flashed an UNSIGNED HBOOT file, which would have been fine since he was S-ON. BUT, once he sent in the command for S-ON, the device saw the UNSIGNED HBOOT and rebricked. He was then able to re-write the P4 file, which contains all your device information (IMEI, CID etc.). Then flash in the recovery, access the recovery, and flash your ROM.
I don't know how different that hard brick is from yours, but it worked for me. Can you access your bootloader btw?
d3thstalker said:
I suggest that you try reading here. I hard bricked my device before while trying to downgrade my HBOOT version from 1.14 to 1.09.
http://forum.xda-developers.com/showthread.php?t=2156231
To sum it up, he could still access his bootloader, but couldn't flash anything. By accessing rebootRUU, he managed to place his phone into a brick mode which allowed Linux to recognize and write to the boot partition. To enter that sort of brick mode, he flashed an UNSIGNED HBOOT file, which would have been fine since he was S-ON. BUT, once he sent in the command for S-ON, the device saw the UNSIGNED HBOOT and rebricked. He was then able to re-write the P4 file, which contains all your device information (IMEI, CID etc.). Then flash in the recovery, access the recovery, and flash your ROM.
I don't know how different that hard brick is from yours, but it worked for me. Can you access your bootloader btw?
Click to expand...
Click to collapse
no my device is literally hard bricked, no bootloader/hboot no os no recognition on pc other than qhsusb_dload i remember working on the same issue with the htc shooter on sprint so im trying the method we used to recover our device after intentionally bricking it which requires linux but in any case im almost there im currently trying to track down the ENG hboot for the evita atm
FragmentedLogik said:
im currently trying to track down the ENG hboot for the evita atm
Click to expand...
Click to collapse
If you find one, let Leamstears know. He has a thread posted somewhere asking for it.
Also, you might search for unbrick evita in general section. There was a thread started awhile back by my buddy.
Sent from my HTC One X using xda premium
i have you made any progress ??? my htc one s is hard briked too
https://www.dropbox.com/sh/a1n5s4r61wfh7qr/gkgxmKXwka/Evita soff partitions
Maybe this will help.
Sent from my One X using xda premium
I am not sure if this is helpful at all, but I was looking into methods used to unbrick other HTC devices and found this thread: http://forum.xda-developers.com/showthread.php?t=1522351 I am not sure what all I would need to change to get it to work for our phone. if you have any thoughts I would be more than willing to look at it.
PUfelix85 said:
I am not sure if this is helpful at all, but I was looking into methods used to unbrick other HTC devices and found this thread: http://forum.xda-developers.com/showthread.php?t=1522351 I am not sure what all I would need to change to get it to work for our phone. if you have any thoughts I would be more than willing to look at it.
Click to expand...
Click to collapse
I'm not sure it will really help. The first part is to run brickdetect.sh. That script appears to try to enumerate the partitions. I tried to enumerate my partitions using the manual steps in mirgantrophy's unbrick evita thread to no success before I sent my device off for JTAG. You could always try to run the brickdetect.sh script and see though. It doesn't do anything to your phone. It just searches dmesg (a Linux log) for the partitions being detected when you attach the bricked phone via USB. Don't run the rest of it though. ;-P
I'd like see a method to fix emmc of an htc inspire 4g(htc ace). Can any of our methods be transposed for other htc devices?
do you think this would work on a samsung device? i flashed a skyrocket rom for my S2 and it was sposed to be fine but it decided not to be. or at least work on a project for samsung devices.... dont leave us hanging
Trozzul said:
do you think this would work on a samsung device? i flashed a skyrocket rom for my S2 and it was sposed to be fine but it decided not to be. or at least work on a project for samsung devices.... dont leave us hanging
Click to expand...
Click to collapse
I definitely would not try this on any device other than the device it's intended for. Completely different chipsets.
Sent from my Evita
my htc one x does not start and charge the battery
try installing an edited rom
then restart the phone now will not start
gato06 said:
my htc one x does not start and charge the battery
try installing an edited rom
then restart the phone now will not start
Click to expand...
Click to collapse
Do you have One X (Endeavor) or One XL (Evita)?
Sent from my Evita
timmaaa said:
Do you have One X (Endeavor) or One XL (Evita)?
Sent from my Evita
Click to expand...
Click to collapse
One X at&t
gato06 said:
One X at&t
Click to expand...
Click to collapse
What ROM did you flash?
Sent from my Evita
timmaaa said:
What ROM did you flash?
Sent from my Evita
Click to expand...
Click to collapse
I try with this rom
http://forum.xda-developers.com/showthread.php?t=2174855
gato06 said:
I try with this rom
http://forum.xda-developers.com/showthread.php?t=2174855
Click to expand...
Click to collapse
Well you've bricked your phone. That ROM is not for our phone.
Sent from my Evita
How unbrick :'( You have idea?
You can either get a jtag repair or send it to HTC to have the motherboard replaced. Jtag is the cheaper option. When you get it back, make sure you stay within our forum and only flash software intended for our device.
Sent from my Evita
ran the 3.18 ruu with an S-On Device
Click to expand...
Click to collapse
i never thought run RUU with s-on device will brick it. Will it be more correct to say "run RUU on device with s-on & supper cid will brick you device"
Related
I just obtaind root today and i flashed icecoldjelly and now my phone wont turn on. is there any way that i can fix this. i love this phone and just got it to my liking please help
We don't have an icecoldjelly ROM.
Please read before you flash.
Can you get to boot?
Sent from my One X using Tapatalk 2
superchilpil said:
We don't have an icecoldjelly ROM.
Please read before you flash.
Can you get to boot?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
i got the rom from onex.com and they said the rom was for the one x, and no no boot
omarh3 said:
i got the rom from onex.com and they said the rom was for the one x, and no no boot
Click to expand...
Click to collapse
IceColdJelly is for the international One X, not the AT&T One XL.
Someone else managed to brick their phone doing this. Check this thread and do what I told the other guy:
http://forum.xda-developers.com/showthread.php?t=1953975
omarh3 said:
i got the rom from onex.com and they said the rom was for the one x, and no no boot
Click to expand...
Click to collapse
Goto - http://forum.xda-developers.com/showthread.php?p=33198089
User had similar issue and he solved
omarh3 said:
I just obtaind root today and i flashed icecoldjelly and now my phone wont turn on. is there any way that i can fix this. i love this phone and just got it to my liking please help
Click to expand...
Click to collapse
Do you have the 2.20 hboot? I imagine you do if you just rooted today. If that is the case you're lucky since hboot partition is read only and cannot be clobbered. Just re-flash TWRP recovery via fastboot and flash a ROM for the one XL and you should be good to go.
If you have pre-2.20 hboot you might be bricked.
denversc said:
Do you have the 2.20 hboot? I imagine you do if you just rooted today. If that is the case you're lucky since hboot partition is read only and cannot be clobbered. Just re-flash TWRP recovery via fastboot and flash a ROM for the one XL and you should be good to go.
If you have pre-2.20 hboot you might be bricked.
Click to expand...
Click to collapse
same thing happened to me and it was the same rom i think please help in any way you can
nvidia31337 said:
same thing happened to me and it was the same rom i think please help in any way you can
Click to expand...
Click to collapse
You flashed IceColdJelly? Your phone is completely dead?
iElvis said:
You flashed IceColdJelly? Your phone is completely dead?
Click to expand...
Click to collapse
yeah completely and says same message in device manager
nvidia31337 said:
yeah completely and says same message in device manager
Click to expand...
Click to collapse
You're bricked, sorry. There is a way out if you have access to a Linux computer; see that other thread.
yea same here cant even get into recovery, same error sound when connected to the pc. Dont have access to a linux computer, No effect when i try to put in recovery mode or anything. Looks like im going to have to get a new phone
Try the steps here:
http://unlimited.io/qhsusbdload.htm
Everyone has access to a linux computer, you download a live cd, burn it and then restart your computer to boot into linux
area51avenger said:
Try the steps here:
http://unlimited.io/qhsusbdload.htm
Everyone has access to a linux computer, you download a live cd, burn it and then restart your computer to boot into linux
Click to expand...
Click to collapse
Is this confirmed to work on One X's bricked from flashing international ROMs? I've seen it mentioned several times before that Qualcomm download mode can be recovered from using a Linux computer. But this is the first time I've actually seen the instructions. And it really doesn't look all that complicated.
Seems like quite a few people that have bricked (by flashing international ROMs) would benefit from this, and it deserves its own thread.
redpoint73 said:
Is this confirmed to work on One X's bricked from flashing international ROMs? I've seen it mentioned several times before that Qualcomm download mode can be recovered from using a Linux computer. But this is the first time I've actually seen the instructions. And it really doesn't look all that complicated.
Seems like quite a few people that have bricked (by flashing international ROMs) would benefit from this, and it deserves its own thread.
Click to expand...
Click to collapse
Cannot confirm if this can fix a corrupted hboot partition, but it's worth a shot. Haven't found any solid guides for pushing a new hboot partition to the phone while in this mode yet. Also do not want to brick my phone to test it
redpoint73 said:
Is this confirmed to work on One X's bricked from flashing international ROMs? I've seen it mentioned several times before that Qualcomm download mode can be recovered from using a Linux computer. But this is the first time I've actually seen the instructions. And it really doesn't look all that complicated.
Seems like quite a few people that have bricked (by flashing international ROMs) would benefit from this, and it deserves its own thread.
Click to expand...
Click to collapse
didn't beaups write something about this at some point, trying to find it again..
what commands do i run to un brick my phone? ive downloaded a linux based os please help. the phone is compleatley bricked but some one said i could unbrick it in this fashon
omarh3 said:
what commands do i run to un brick my phone? ive downloaded a linux based os please help. the phone is compleatley bricked but some one said i could unbrick it in this fashon
Click to expand...
Click to collapse
and ive run the commands that were in the link and it says command not found
Did you pay attention to: Type the following commands (note: linux is case sensitive)
Crappyvate said:
didn't beaups write something about this at some point, trying to find it again..
Click to expand...
Click to collapse
Totally possible. I don't recall, or haven't seen it. I've seen a few posts to the effect of "if you have Linux, it can be fixed, PM me" but that is all I've seen. Would be nice if there was a writeup we can point people to (and I can add to my index thread).
Go to Evo 4g LTE forum and go to original development. 1st page should have a thread by yarrimapirate about downgrade. He recently figured how to brick, downgrade hboot and get s-off from QHuSB. Mode. The guys is a genius. That thread may have some answers or at least some help or info for you. People in that thread are stepping over themselves trying to help people.
Good luck.
I'd post a link, but I know as soon as I step out of this thread I'll never find it again (xda app)
Edit: go here http://forum.xda-developers.com/showthread.php?t=1940512
[HBOOT][10/24/12] 1.15/1.19 downgrade tool (Linux)
hurled from my AOKP'd Evo LTE. Enjoy.
i have read for hours and tried anything and everything pleas help
I have a att htc one x firmware 2.20 i unlocked bootloader and rooted with hansons tool kit then i went to flash rom in looking back i did incorrectly but bottom line now is i lost all data as far as stock configs and backups so i lost perm root and now i can flash roms but do not take just does recovery bootloop i can still boot into fast boot and enter twrp recovery and can mount ect but since i dont have perm root no roms will boot i caint get into phone to turn debugging on and my cid was cws__oo1 then i got su cid that was chanced when i tried to use toolkit for installing jelly bean and change the hboot its now set at htc__621 so i can not install custom rom becouse no perm root i cant get perm root couse i cant enable debugging i cant flash ruu becouse i get error 131 becouse my cid is not stock any longer i cant push or pull from adb shell becouse device not found i am a noob and yea i screwd up but i have learned alot about what not to do i hope someone canhelp me with a option i was thinking maby i could install ruu for cid__621 buti belive its tided to the endeavor not the evita....please help
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Who is telling noobs to change their CIDs to Endeavor? Is there some malicious youtube tutorial floating around? This is the second one today.
iElvis said:
Who is telling noobs to change their CIDs to Endeavor? Is there some malicious youtube tutorial floating around? This is the second one today.
Click to expand...
Click to collapse
no one the tool kit did it automaticaly to update hboot so i could install jelly bean nowi caintchange it back to flashstk ruu
rootmyhtc said:
no one the tool kit did it automaticaly to update hboot so i could install jelly bean nowi caintchange it back to flashstk ruu
Click to expand...
Click to collapse
What tool kit? There is no tool kit for installing JB on this phone, nor any need of one. You must have used something for the Tegra 3 International One X, which is why your phone is now screwed up. You can't use the '621 ruu because that's for a different phone.
Can you get into recovery? You might try and see if you can switch your CID back with Hanson's toolkit.
iElvis said:
What tool kit? There is no tool kit for installing JB on this phone, nor any need of one. You must have used something for the Tegra 3 International One X, which is why your phone is now screwed up. You can't use the '621 ruu because that's for a different phone.
Can you get into recovery? You might try and see if you can switch your CID back with Hanson's toolkit.
Click to expand...
Click to collapse
yes i can and i did try to push super user and per root but debugging is off so it does not see device thanx in advance for any help
Second person in 1 day trying to change their CID to that of the Tegra3 One X. Of course, that is the wrong device, and it can only end poorly. What gives???
http://forum.xda-developers.com/showthread.php?t=2100232
redpoint73 said:
Second person in 1 day trying to change their CID to that of the Tegra3 One X. Of course, that is the wrong device, and it can only end poorly. What gives???
Click to expand...
Click to collapse
No idea. I looked over in the endeavour forums, and even those tutorials said no, you can't change your CID to run a different RUU. It must be some noob hack floating around out on the web.
I don't understand why people are so obsessed with installing jelly bean that they throw all caution out the window. I don't really feel all that much difference between my N7 and my still-on-ICS evita.
iElvis said:
I don't understand why people are so obsessed with installing jelly bean that they throw all caution out the window.
Click to expand...
Click to collapse
Just as baffling is that these folks know enough or have researched enough to be able to change their CID, but not enough to know that they are installing a ROM for the wrong device (and changing to the CID for the wrong device).
redpoint73 said:
Just as baffling is that these folks know enough or have researched enough to be able to change their CID, but not enough to know that they are installing a ROM for the wrong device (and changing to the CID for the wrong device).
Click to expand...
Click to collapse
Unbelievable... Like I said in the other thread. That was 2 people in a row yesterday.... Where are these noobs getting there half a$$ info from... Lol
Sent from my HTC One XL using Tapatalk 2
i've unlocked my att one x got supercid.. and then i decided to change it to htc_405... so... it was the wrong choice! and now i can't get back to supercid, i've tryied all guides on forum but no one works..
from adb shell.. command writes.. device not found.
also installed newest htc drivers but nothing changes.. the hasoon allin1 tool doesnt work and i dont know what to do..hellppp :crying:
Are you s-on or s-off?
Sent from my Evita
timmaaa said:
Are you s-on or s-off?
Sent from my Evita
Click to expand...
Click to collapse
i'm s-on
Wait why did you do that? The cid for at&t one x is cws_001...
Sent from my HTC One X using Tapatalk 4
panda_mode said:
Wait why did you do that? The cid for at&t one x is cws_001...
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
i know but i changed it to recieve eu update.. didn't know that he has other cpu.. so now i cant change it to supercid or the original one..
You're kinda stuck then. To change CID more than once you need s-off, but to get s-off you need SuperCID. You probably should have done some research before you did that.
Sent from my Evita
timmaaa said:
You're kinda stuck then. To change CID more than once you need s-off, but to get s-off you need SuperCID. You probably should have done some research before you did that.
Sent from my Evita
Click to expand...
Click to collapse
so any suggestions? i know that i shloud search more.. i have other one s and i thought it was similar.. but that one is not branded
denny094 said:
so any suggestions? i know that i shloud search more.. i have other one s and i thought it was similar.. but that one is not branded
Click to expand...
Click to collapse
Maybe you can hex edit your mmcblk0p4 and change the cid back to super cid or the AT&T cid. DO MORE RESEARCH ABOUT THIS. I cannot help you step by step because I have not attempted this myself. THIS IS JUST AN IDEA AND MAY BRICK YOUR PHONE. I am not responsible for what will happen of you attempt this.
In the sticky-roll up, there is a thread called "AT&T: Unlocking the bootloader through HTCdev." The title looks irrelevant to your issue, but it has information about hex editing the mmcblk0p4 file
Sent from my HTC One X using Tapatalk 4
panda_mode said:
Maybe you can hex edit your mmcblk0p4 and change the cid back to super cid or the AT&T cid. DO MORE RESEARCH ABOUT THIS. I cannot help you step by step because I have not attempted this myself. THIS IS JUST AN IDEA AND MAY BRICK YOUR PHONE. I am not responsible for what will happen of you attempt this.
In the sticky-roll up, there is a thread called "AT&T: Unlocking the bootloader through HTCdev." The title looks irrelevant to your issue, but it has information about hex editing the mmcblk0p4 file
Sent from my HTC One X using Tapatalk 4
Click to expand...
Click to collapse
yeah i've seen that one.. but if i try to take that file.. adb says "device not found" so i cant do this one too..
C:\fastboot\adb shell (>enter)
daemon started succesfully*
device not found!
with lastest htc drivers and htc sync... if i could get the mmcblk0p4 file i wont open this thread
Ah I see. Well I can't be much of help then. Sorry
Sent from my HTC One X using Tapatalk 4
denny094 said:
yeah i've seen that one.. but if i try to take that file.. adb says "device not found" so i cant do this one too..
C:\fastboot\adb shell (>enter)
daemon started succesfully*
device not found!
with lastest htc drivers and htc sync... if i could get the mmcblk0p4 file i wont open this thread
Click to expand...
Click to collapse
Ensure that USB debugging is turned on.
Verify that HTC Sync is not running.
Try other cables, USB ports and even other computers.
s79336951 said:
Ensure that USB debugging is turned on.
Verify that HTC Sync is not running.
Try other cables, USB ports and even other computers.
Click to expand...
Click to collapse
i've tried all thoose , 3 pc's (1 with win7 the other win8) always debug mode..(actually the phone is runnin viperx4) ,..on, 2 different calbles and all pc 's usb ports i'm desperate
denny094 said:
i've tried all thoose , 3 pc's (1 with win7 the other win8) always debug mode..(actually the phone is runnin viperx4) ,..on, 2 different calbles and all pc 's usb ports i'm desperate
Click to expand...
Click to collapse
Are you on a Jellybean Sense ROM currently? Does fastboot detect the device? I had a heck of a time getting adb to see the device (but fastboot was working fine), back when the s-off method first came out, while on a Jellybean Sense ROM. I tried any number of the usual fixes, such as different drivers, different USB cords, and a different PC. The only thing that worked is using an old nandroid to go back to ICS, and adb picked up the phone right away. All I can think is that the change to MTP storage somehow messed with the adb connectivity for me (but not for others, I don't know).
BTW, reported to mods to move this thread, as it should be in Q&A.
redpoint73 said:
Are you on a Jellybean Sense ROM currently? Does fastboot detect the device? I had a heck of a time getting adb to see the device (but fastboot was working fine), back when the s-off method first came out, while on a Jellybean Sense ROM. I tried any number of the usual fixes, such as different drivers, different USB cords, and a different PC. The only thing that worked is using an old nandroid to go back to ICS, and adb picked up the phone right away. All I can think is that the change to MTP storage somehow messed with the adb connectivity for me (but not for others, I don't know).
BTW, reported to mods to move this thread, as it should be in Q&A.
Click to expand...
Click to collapse
the device is running viperxl and fastboot its working well..
commands like..dunno...
fastboot oem readcid:
your cid is : HTC_405
so he has no problems..adb yes..
i dont have any ics backup and dont know how to install it..tryied to install ruu (with sense+ and not working)
denny094 said:
the device is running viperxl and fastboot its working well..
commands like..dunno...
fastboot oem readcid:
your cid is : HTC_405
so he has no problems..adb yes..
i dont have any ics backup and dont know how to install it..tryied to install ruu (with sense+ and not working)
Click to expand...
Click to collapse
If you want to get back to ICS to see if adb works: Make a nandroid of your current setup. Then just flash any stock rooted of custom ICS ROM. This is assuming you are still bootloader unlocked.
Of course, I'm not necessarily saying this will work (get adb to work). But it worked for me, and if you are out of options, then its certainly worth a try. If it doesn't work, just restore your nandroid, and you are no worse off.
What is your hboot version?
Also, RUU will not run if the CID is incorrect. So you' ve screwed yourself from running any correct RUU.
redpoint73 said:
If you want to get back to ICS to see if adb works: Make a nandroid of your current setup. Then just flash any stock rooted of custom ICS ROM. This is assuming you are still bootloader unlocked.
Of course, I'm not necessarily saying this will work (get adb to work). But it worked for me, and if you are out of options, then its certainly worth a try. If it doesn't work, just restore your nandroid, and you are no worse off.
What is your hboot version?
Also, RUU will not run if the CID is incorrect. So you' ve screwed yourself from running any correct RUU.
Click to expand...
Click to collapse
uhmm i think the cid problem i solved i've tryied again and adb worked now must be scid.. i'll do s-off.., with all in 1 toolkit or hexeditor?
denny094 said:
uhmm i think the cid problem i solved i've tryied again and adb worked now must be scid.. i'll do s-off.., with all in 1 toolkit or hexeditor?
Click to expand...
Click to collapse
That post is really confusing, your sentence structure and punctuation is all over the place. Can you clear it up a bit and ask again?
Sent from my Evita
Yeah, not sure what was being said there. Did going back to ICS fix the adb issue, or did you find another way? So you have SuperCID now? If so, do the facepalm method to get s-off.
If you are still trying to get SuperCID, I don't think hasoon's all-in-one tool will work. Believe its looking for the AT&T CID (cws__001), so any other CID, it will fail. You'll have to use the hex edit method.
Problem is solved thanks I did s-off but I would like to ask you another question.. I installed clear rom sense 5 but the device has very low signal the radio firmware is 0.24p are there new updates to increase the quality?
Inviato dal mio HTC One S usando Tapatalk 4
I'm not sure which which radio you're referring to there. Have you updated the firmware as suggested in the CR thread?
Sent from my Evita
Hi all,
I am attempting to S-off the wife's ATT HTC One X, so that I can install a Kit Kat Rom in it. Her phone is unlocked and running CM10.2, but she's S-on.
I've tried several toolkits, but they get stuck and time out waiting for the device once it reboots into the bootloader. In debugging mode, adb devices identified the phone just fine, but the computer (running Windows 8.1) says doesn't recognize the phone when in bootloader. I've got Koush's Universal ADB driver installed, installed HTC Sync for the drivers, then uninstalled the program. The drivers are still there when I navigate to them.
If this isn't the appropriate forum, then I apologize.
Many thanks in advance!
What method are you trying to use?
Sent from my HTC One X using xda premium
magnetboard said:
What method are you trying to use?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Rumrunner is one. It reboots into bootloader post the warnings then runs its 120 seconds and times out waiting for the device.
Ah, windows 8 and newer have problems with fastboot. That's why. Do you have access to a computer with windows 7 or lower?
Sent from my HTC One X using xda premium
magnetboard said:
Ah, windows 8 and newer have problems with fastboot. That's why. Do you have access to a computer with windows 7 or lower?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I can put an old HD back in with W7. I take it there is no workaround with 8.1?
Windows 8 is fine with fastboot but 8.1 is where the problems begin. No workaround yet. What see the bootloader details though? Depending on your current setup you might not even need s-off yet. S-off isn't required to flash the ROMs, but it's required to update your firmware (via an RUU). If your firmware is up to date you can just flash.
Sent from my Evita
timmaaa said:
Windows 8 is fine with fastboot but 8.1 is where the problems begin. No workaround yet. What see the bootloader details though? Depending on your current setup you might not even need s-off yet. S-off isn't required to flash the ROMs, but it's required to update your firmware (via an RUU). If your firmware is up to date you can just flash.
Sent from my Evita
Click to expand...
Click to collapse
What all do you need to know? She has her phone with her today.
She has 2.18. I don't know other details off the top of my head and walking her through to boot to bootloader would be an utter disaster, lol.
The reason for trying to get S-off was that both the KitKat versions of CM and PA stated that S-off was required.
Thanks for your help.
If your cousin can't get to the bootloader by herself, then she has absolutely no business having a modified phone. Handing a modified device to someone who has no idea about what they're doing is a bad idea. The device has root privileges, access to areas that see not normally accessible. This means it's easy top screw up the device if you don't know what you're doing. Also, if something goes wrong she's not gonna know what to do, will probably panic and screw it up even more. Return it to stock.
Sent from my Evita
timmaaa said:
If your cousin can't get to the bootloader by herself, then she has absolutely no business having a modified phone. Handing a modified device to someone who has no idea about what they're doing is a bad idea. The device has root privileges, access to areas that see not normally accessible. This means it's easy top screw up the device if you don't know what you're doing. Also, if something goes wrong she's not gonna know what to do, will probably panic and screw it up even more. Return it to stock.
Sent from my Evita
Click to expand...
Click to collapse
Appreciate the concern. This is my wife's phone, and she's handled CM10.2 just fine for the last 6 months. She's informed enough to not do something stupid, but let's me handle rooting and flashing.
Okay so my friend asked me to fix a phone that he says one day it got stuck in boot splash screen. He claims he did not try to flash a custom Rom or something but he said he hadn't.here's some of the phones info
HTC one x
***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
Can anyone sheed some light on the subject.
I don't know how to use adb and fastboot
And I have Windows xp and Mac 10.6 and lynx
Wrong forum, the evita is the HTC one XL.. Thread reported for moving to the correct forum. This part is for the international HTC one X (quad-core model)
Good luck
Mr Hofs said:
Wrong forum, the evita is the HTC one XL.. Thread reported for moving to the correct forum. This part is for the international HTC one X (quad-core model)
Good luck
Click to expand...
Click to collapse
As if by magic, it appears in the One XL forum.
I think your friend is telling fibs, phones don't just magically stop booting for no reason. Please tell him to own up to whatever activities lead to this situation, as embarrassing as it might be, I need to know how this happened in order to help properly.
Now, just to be clear, the phone is actually the HTC One XL, not the HTC One X. They look similar but are actually very different. What recovery is installed on the device?
Another question for you, why isn't your friend posting here and attempting to fix this problem himself? If he can't recover from a simple problem like this (or can't be bothered learning/trying) he honestly has no place having a modified phone. That might sound harsh but it's the truth, this is very basic knowledge, it's flashing 101. Knowing how to recover from something like this is an essential skill for anyone who owns a modified phone. If your friend isn't interested in being honest about what lead to this situation, or interested in learning how to recover from this situation, my only advice is to return to the device to stock and leave it that way. I'd strongly urge him to get on here and post himself, and do some reading to educate himself on the ins and outs of modified devices.
Sent from my Evita
sorry for being so vauge
My friend is a lady friend who had no idea how the phone could have become modified. The phone is a HTC one X and my lady friend said she would love nothing more then to have a stock phone. My friend has no intrest in leaning how the in's and out's of HTC but, I on the other hand would love to learn about HTC and Android. I come from a n Apple community and have a little knowledge but not a lot.
Anything you can tell me would help greatly, and I would be indeed greatful.
Sincerely Nanamkin
The only option for you is to return the phone to stock, giving a modified device to someone who knows nothing about them and doesn't even want a modified device is a bad idea. I'll just reiterate though, it isn't a HTC One X, it's the One XL. Is it an at&t model? Can you please retrieve the software version from Settings/About Phone? Can you please enter recovery from the bootloader screen and tell me which recovery version is installed?
Sent from my Evita
Thank you so much
timmaaa said:
The only option for you is to return the phone to stock, giving a modified device to someone who knows nothing about them and doesn't even want a modified device is a bad idea. I'll just reiterate though, it isn't a HTC One X, it's the One XL. Is it an at&t model? Can you please retrieve the software version from Settings/About Phone? Can you please enter recovery from the bootloader screen and tell me which recovery version is installed?
Sent from my Evita
Click to expand...
Click to collapse
it is AT&T
and it has TWRP 2.14
dont know the software version but when i connect to 'htc sync manger'' it says version 2.20 but im not sure.
Nanamkin said:
it is AT&T
and it has TWRP 2.14
dont know the software version but when i connect to 'htc sync manger'' it says version 2.20 but im not sure.
Click to expand...
Click to collapse
There is no TWRP 2.14 for this device, are you confusing it with the hboot number? Go to Settings/About Phone (where I said it would be earlier), and post the software version please.
Sent from my Evita
Man your GOOD
timmaaa said:
There is no TWRP 2.14 for this device, are you confusing it with the hboot number? Go to Settings/About Phone (where I said it would be earlier), and post the software version please.
Sent from my Evita
Click to expand...
Click to collapse
I am sooo sorry. you are absulotly right, and you are good! how did you know that? lol
here is the right info.
TWRP 2.3.1.0
im sorry i cant boot into the phone to check the setting/about phone for a software version. do you know any other way?
and while i was messing around i figured out how to install ADB and FASTBOOT and use it.
I'm an idiot, completely forgot you can't boot to check the software version. Facepalm. Can you please check the CID for me? Put the phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
Sent from my Evita
got it
timmaaa said:
i'm an idiot, completely forgot you can't boot to check the software version. Facepalm. Can you please check the cid for me? Put the phone in fastboot mode and issue this command:
Code:
fastboot oem readcid
sent from my evita
Click to expand...
Click to collapse
cid:11111111
Ok. To get the phone back to stock you Erik need to run an RUU, but in order to do that safely you'll first need to get s-off. To get s-off you're gonna need a booting ROM on the device. Purely for this exercise I think Kickdroid would be your best option, head to our Android Development section and find the Kickdroid thread, download it, and use TWRP recovery to install it. Look in the How-To Guide For Beginners thread in my signature for full instructions on how to flash the ROM. Please note, you'll also need to flash the boot.img from the ROM zip via fastboot after flashing the ROM.
Sent from my Evita
got it
Okay I have the Rom on my phone now what?
Nanamkin said:
Okay I have the Rom on my phone now what?
Click to expand...
Click to collapse
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
your awesome
timmaaa said:
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
Click to expand...
Click to collapse
oh yeah i was over there just a little awhile ago. i een your name so i tiend to fallow it but couldnt get the rom. thank you sooo much
timmaaa said:
Now you can get s-off, head over to the Facepalm thread and follow the instructions there.
Facepalm S-off
Click to expand...
Click to collapse
when i get done with step 6 i cant use the last 3 codes for the s-off flag because the phone wont boot into android?
Nanamkin said:
when i get done with step 6 i cant use the last 3 codes for the s-off flag because the phone wont boot into android?
Click to expand...
Click to collapse
I thought you said you had the ROM on your phone? Did you just mean the zip? If so, go to the How-To thread in my signature and follow the instructions to install the ROM and flash the boot.img. Then you can go back to the Facepalm thread. Just make sure you boot up the phone and set it up before doing the s-off process.
I got the rom to work
timmaaa said:
I thought you said you had the ROM on your phone? Did you just mean the zip? If so, go to the How-To thread in my signature and follow the instructions to install the ROM and flash the boot.img. Then you can go back to the Facepalm thread. Just make sure you boot up the phone and set it up before doing the s-off process.
Click to expand...
Click to collapse
I got the rom to boot after fallowing your directions(like you said)lol. but when i do steps 7 the 3 codes it says there are no directory. I got the first one to go but the other 2 would not work
Did you remember to extract (unzip) the file into your fastboot folder?
Sent from my Evita
got the os to boot
timmaaa said:
Did you remember to extract (unzip) the file into your fastboot folder?
Sent from my Evita
Click to expand...
Click to collapse
okay so i have the rom on the phone (kickdroid) and now i cant run the last 3 codes on step 7. any clue. I have soffbin zip unzipped in the directory but where exactly do i put it? i have it in the same folder as adb and fastboot is that right?