Related
I got a bricked T-mobile Sensation today at the shop and after checking it out I thought it would be easy to fix but unfortunately its proving to be much more difficult than I expected. Here's what I'm working with:
Locked s-on
Hboot 1.18.0000
radio 10.14.9035.01_m
First, I tried all kinds of PG58 zips. None worked. I figure I need to be unlocked to do it. Did the HTC unlock and got to the warning screen and where it asks to choose yes or no. I can navigate to yes or no but when I choose yes it just freezes and doesn't do anything. I tried it 3 different times, same thing. I can't even choose factory reset in Hboot, it just freezes. I don't know what the eff is going on. I've been downloading RUUs but have yet to find the correct one. I don't know what firmware it has because it does not boot up.
I thought, well shoot, I have fastboot, maybe I could just s-off and root from fastboot, but I can't find any thread explaining how to do it.
Any help would be great.
Thanks!
Edit:
Found the correct RUU, 1.50.xxxx whatever. WHen I run the utility It says its rebooting into bootloader but stays in the same screen and doesn't do anything. I don't know if this helps, but when I go into the bootloader I cannot go back into hboot. It just, freezes.
Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1192300
And you need to be s-off to flash those pg58 zips, thats why they failed.
As you're on HBOOT 1.18.0000 use the revolutionary method to get S-OFF. http://revolutionary.io
The HTC unlock is a bit redundant as it doesn't give S-OFF which you need.
There are many guides here on XDA to help you. Such as:
http://forum.xda-developers.com/showthread.php?t=1192300
EDIT: Oops didn't notice that "Kazireh" has already posted the link.
You'll need the HTC drivers (download HTC Sync install it then delete HTC Sync leaving the drivers installed).
You should also get the ADB tools installed as at some stage they'll be useful.
As far as the RUU is concerned you need to make sure it's the right one for the current CID on the phone.
Kazireh said:
Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1192300
And you need to be s-off to flash those pg58 zips, thats why they failed.
Click to expand...
Click to collapse
gol_n_dal said:
As you're on HBOOT 1.18.0000 use the revolutionary method to get S-OFF. http://revolutionary.io
The HTC unlock is a bit redundant as it doesn't give S-OFF which you need.
There are many guides here on XDA to help you. Such as:
http://forum.xda-developers.com/showthread.php?t=1192300
EDIT: Oops didn't notice that "Kazireh" has already posted the link.
You'll need the HTC drivers (download HTC Sync install it then delete HTC Sync leaving the drivers installed).
You should also get the ADB tools installed as at some stage they'll be useful.
As far as the RUU is concerned you need to make sure it's the right one for the current CID on the phone.
Click to expand...
Click to collapse
Thanks for the help guys, but heres the deal:
I cannot s-off due to it not being able to boot.
I could try Junopbears s-off but I cannot unlock, as it just freezes when I try.
I found the correct ruu but again it freezes and does not boot into the bootloader.
My CID is T-mob010
I have all drivers installed, adb, fastboot, etc
If your on hboot 1.18 you have a gingerbread fw, look for that
Sent from my HTC Sensation 4G
its completely possible that the motherboard is failing. I see this in my shop all the time, though usually with the MyTouch 4G (faulty eMMC chip) but the sensation and a few other HTC's also see this. we havent come up with a solution between my two stores employees, so hopefully someone here can?
q said you did not understand, is how I explain more thoroughly I am new to the subject
and my device does not enter the system and when using the mode prop vo comand says device not found what to do? sensation with my ta hboot 1.27.0000 s-s on rl unloked help me
2strokenut said:
Thanks for the help guys, but heres the deal:
I cannot s-off due to it not being able to boot.
Click to expand...
Click to collapse
Can you get into "Fastboot USB" ?
I could try Junopbears s-off but I cannot unlock, as it just freezes when I try.
Click to expand...
Click to collapse
Junopbear is wrong as it's for 1.2x.xxxx HBOOT, try Revolutionary.
I found the correct ruu but again it freezes and does not boot into the bootloader.
My CID is T-mob010
Click to expand...
Click to collapse
Eek.
T-MOB010 == RUU x.xx.531.xxxxxxxxx according to my list.
I have all drivers installed, adb, fastboot, etc
Click to expand...
Click to collapse
Good.
There are a few "unbrick" guides, never tried to use them so can't help on that front.
nickL0V3 said:
its completely possible that the motherboard is failing. I see this in my shop all the time, though usually with the MyTouch 4G (faulty eMMC chip) but the sensation and a few other HTC's also see this. we havent come up with a solution between my two stores employees, so hopefully someone here can?
Click to expand...
Click to collapse
Yeah that's what I'm leaning toward right now, there is nothing else I can do. I have 4 or 5 Mytouchs on the shelf with bad eMMc chips so I guess this one is joining them.
gol_n_dal said:
Can you get into "Fastboot USB" ?
Junopbear is wrong as it's for 1.2x.xxxx HBOOT, try Revolutionary.
Eek.
T-MOB010 == RUU x.xx.531.xxxxxxxxx according to my list.
Good.
There are a few "unbrick" guides, never tried to use them so can't help on that front.
Click to expand...
Click to collapse
Yes the RUU was 1.50.531.xxxxxx
Yes, I can get into Fastboot usb, I can do fastboot commands, it just freezes when the RUU tries to do its thing.
Jbear would still work if the bootloader were locked, but I couldn't unlock the bootloader. Revolutionary will not work either because its run while the phone is on, which I can't do.
I think I've exhausted every option, it seems to all point to a failed eMMc chip, shame though, I really like these phones.
Thanks for the help fellas
GL
///////////////
Hi, I realize I will get a lot of flame for this, but how do I know if my AT&T One X is S-off?
See, I'm trying to flash this custom boot screen from here (http://forum.xda-developers.com/showthread.php?t=2173665) and the requirements say I must be S-off and have an unlocked bootloader.
I know for sure my bootloader is unlocked (via the HTCDev method). I also read some places that S-off means your bootload is locked? So kind of confused here.
Thanks very much XDA geniuses!!!!
toughtrasher said:
Hi, I realize I will get a lot of flame for this, but how do I know if my AT&T One X is S-off?
See, I'm trying to flash this custom boot screen from here (http://forum.xda-developers.com/showthread.php?t=2173665) and the requirements say I must be S-off and have an unlocked bootloader.
I know for sure my bootloader is unlocked (via the HTCDev method). I also read some places that S-off means your bootload is locked? So kind of confused here.
Thanks very much XDA geniuses!!!!
Click to expand...
Click to collapse
Reboot into boot loader. It'll either say S-On or S-Off.
Okay, I've done that and it says I'm S-On.
What are the benefits of S-Off and any cons? Thanks given
System write protection is turned off. Reduces chance of bricking with ruu and allows you to change things like hboot and splash screen without the need for them to be signed. It's good to have if you're knowledgeable enough to read and follow instructions.
Sent from my One X using xda app-developers app
toughtrasher said:
Okay, I've done that and it says I'm S-On.
What are the benefits of S-Off and any cons? Thanks given
Click to expand...
Click to collapse
No need to flash boot.img
Less vernerable to brick etc...
There's really no disadvatage of gaining soff, so why not?
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Thug_4_Life said:
No need to flash boot.img
Less vernerable to brick etc...
There's really no disadvatage of gaining soff, so why not?
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
There is one disadvantage. S-OFF stands for Security Off. Security Off disables security checks, verifying your hboot, software version, CID, etc. If you flash something that you're not supposed to to the emmc partitions or something not designed for evita, you will brick.
exad said:
There is one disadvantage. S-OFF stands for Security Off. Security Off disables security checks, verifying your hboot, software version, CID, etc. If you flash something that you're not supposed to to the emmc partitions or something not designed for evita, you will brick.
Click to expand...
Click to collapse
Lol I remember what happened when I flashed Sense5 rom specifically for Evo 4g lte.
Sent from my HTC One X using xda app-developers app
S-off if you need it... If not play it safe.
Sent from my HTC One X using xda app-developers app
Thug_4_Life said:
No need to flash boot.img
Less vernerable to brick etc...
There's really no disadvatage of gaining soff, so why not?
http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
exad said:
There is one disadvantage. S-OFF stands for Security Off. Security Off disables security checks, verifying your hboot, software version, CID, etc. If you flash something that you're not supposed to to the emmc partitions or something not designed for evita, you will brick.
Click to expand...
Click to collapse
For some reason, these two just seem to coincide the hell out of each other someone explain
T4L, I've followed the steps on that thread you pointed me to, but I'm stuck on step 7, inputting this to the command prompt:
adb shell chmod 744 /data/local/tmp/soffbin3
See, I read one of the posts in there that says I can use the files from Hassoon's all in one tool and just point the command prompt there, however when I type in "adb shell chmod 744" itdoesn't do anything. Then when I type in anything else after "adb shell chmod 744" it says error: cannot find device.
What do?
toughtrasher said:
For some reason, these two just seem to coincide the hell out of each other someone explain
T4L, I've followed the steps on that thread you pointed me to, but I'm stuck on step 7, inputting this to the command prompt:
adb shell chmod 744 /data/local/tmp/soffbin3
See, I read one of the posts in there that says I can use the files from Hassoon's all in one tool and just point the command prompt there, however when I type in "adb shell chmod 744" itdoesn't do anything. Then when I type in anything else after "adb shell chmod 744" it says error: cannot find device.
What do?
Click to expand...
Click to collapse
What rom are you using? a root access request pops up on your phone screen after, did you grant root?
exad said:
What rom are you using? a root access request pops up on your phone screen after, did you grant root?
Click to expand...
Click to collapse
I am using CleanROM 6 R2. It didn't pop up anything after step 7
toughtrasher said:
I am using CleanROM 6 R2. It didn't pop up anything after step 7
Click to expand...
Click to collapse
pastebin your cmd please
Make sure you're plugged into a USB 2 port, not USB 3. Anytime I get that error, it's cause I forgot to plug it in the right one.
Sent from my One X using xda app-developers app
Thanks for all your responses, guys! Really appreciate it.
I've succesfully got s-off thanks a lot to beaups! Very great person.
Now for some theming...
Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.
Post your bootloader details
Sent from my HTC Sensation 4G using xda premium
adamagic said:
Hello guys, mainly developers and their friends who might mention my case between each other.
This is a quite big problem, so maybe these few lines below deserve a second read.
From the very beginning: I bought an XE in Europe from second hand. I was about to open the bootloader by using htcdev. As a good layman I found a useless thread which's misled me: I factory reset the phone and after that I did not enable USB Debugging. On the official htc site of unlocking bootloader I chose the option from the list, titled 'Sensation EU'. Since then I've already found out this is an Asian device (cid: ASIA-HK-CHT HTC__622), so I should have chosen 'All other supported device'. In the last step by unlocking bootloader I got a question about unlocking it, or not, whereupon I asked it to do so, causing immediate freeze on the screen.
So, this smartie is bricked now - even though I can reach the bootloader(h-boot 1.29) and the recovery(stock) too - considering the following: I can't unlock it anymore by using the right 'Unlock_code.bin' file either, since it shows me the same frozen screen after choosing 'yes' (by step 12 at htcdev). Nor I can S-OFF or accomplish the RUU procedure. At the latter I can go until it's checked the P58IMG.zip file, and asking me for applying the update. When I press vol_up the brick begins updating the bootloader and never finishes. I mean I like watching that screen for hours, colorful and I'm really obsessed with the phrase 'Updating...', but I'd still like to use this sensation for calls and things. If run the execute file(RUU) on PC, while the phone is connected via 'FASTBOOT USB' it gets stuck at 'rebooting bootloader...' In fastboot I can't even erase my cache, neither in recovery.
Do you think, it'll ever be able to use for its destiny again, if I'd follow the instructions you may give me?
Thank you very much in advance.
Click to expand...
Click to collapse
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?
anything else you should know?
ganeshp said:
Post your bootloader details
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
heavy_metal_man said:
bootloader details please
also does the phone fully boot up anymore? i assume not have you tried to factory reset from the stock recovery, or even hboot?
Click to expand...
Click to collapse
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Hi,
If you can get to bootloader,you are not bricked.
adamagic said:
Thanks for your response. I can't factory reset from nowhere, it causes frostbite. So the details:
H-BOOT Pyramid 1.29.0000, LOCKED, S-ON; the phone main version is 3.32.708.151
Click to expand...
Click to collapse
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425
ganeshp said:
Flash an ruu from the bootloader
@malybru
I lost the link to ruu.. You might have it. the v8-info (something like that) URL will have it in sensation xe section
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hi,
THIS ONE?
rzr86 said:
do you mean this link?
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
Not the guide
malybru said:
Hi,
THIS ONE?
Click to expand...
Click to collapse
Yes this one
Sent from my HTC Sensation 4G using xda premium
ganeshp said:
Not the guide
Yes this one
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.
adamagic said:
Thank you guys, I really appropriate your help. The only thing is when I try to run the execute file, it stops doing anything by "rebooting bootloader"... After 20 minutes the same screen, and the guide only tells me that it takes approximately 10 minutes. When I try to flash it from bootloader, I doesn't go any further then updating bootloader.
Question: the RUU on the link you post is 3.33.707. My phone is HK and not WWE, so it's 708 and not 707. In the txt the cid version is HTC__621, mine is HTC_622. Do you think is enough if I'd just write my cid number into that? I'll givi it a go anyways, but if you have any advice...
Thank guys, you're the best.
Click to expand...
Click to collapse
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium
still nothing
malybru said:
Hi,
Click to expand...
Click to collapse
Yeah, thanks for the link, but it doesn't work either. I've written the 'cidnum: HTC__622' (without any spaces before and after that) into the txt, but after it's checked the P58IMG.zip doesn't ask me anything, just let me be in bootloader like I'd have started the device in bootloader mode without SD.
all right
ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )
adamagic said:
All right, I will try to S-OFF using your guide, but the 3rd and 4th points are not available for me. So I can only connect my phone to PC with Fastboot USB. :\ What do you think?
p.s. This is the file I could go the furthest with: RUU_PYRAMID_LE_ICS_35_S_hTC_Asia_HK_3.32.708.112_R_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_253449_signed.exe
As you see, it is still 3.32, but finally 708, but the last number from that part really makes me anxious, because it's 112, and on my phone that number is 151. I really don't want to give up, so any advice will be appropriated. (Yes, I've seen the donate me button on your profile )
Click to expand...
Click to collapse
you can try it
you don't have to lose anything at all
if it doesn't work it will just throw you an error
see how it goes
ganeshp said:
Ohh then the ruu won't work and changing the cid won't help either.
Hmm we need that ruu
Otherwise try the soff without htcdev (guide link in my signature) as you can't htcdev unlock it
Click to expand...
Click to collapse
rzr86 said:
you can try it
see how it goes
Click to expand...
Click to collapse
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.
adamagic said:
Well, I'm in command: "* daemon not running. starting it now on port 5037 *|* daemon started successfully *" and it's been nothing happening since I've started the method 10 min ago.
"Hmm we need that ruu" => which numbers must match you think in the name of the file? And where the hell to find? yahoo twice better than ggl, so I found the previous one I've showed you.
Click to expand...
Click to collapse
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium
ohh yes
ganeshp said:
Flash the ruu with phone connected from fastboot
Thats should work
Also if the ruu flashing stuck at some point.. There will be a log generated at C:/ruu post the log here (latest modified file)
Edit: btw Donate won't work for me. You can donate to devs on my behalf if you want
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Some persian guy has uploaded the file I need, but unfortunately I can't register, because I can't answer the randon question during the registration process... Somebody?
http://www.fars-gsm.com/showthread.php?t=57177
hi guys, im not new to this, and i have a good understanding of adb and fastboot. i have just purchased a htc one xl (telstra) im running Hboot 2.15 and have unlocked bootloader via htc dev, installed TWRP ver; 2.6.0.0, rooted via flashing superSU and am currently running stock android ver 4.2.2 htc sense 5.0. i sim unlocked it so i could run my vodafone sim, and radio is working fine but i think the telstra RUU isnt allowing the sims internet conectis-on, therefore i am deciding to flash another rom. i first tried flashing pacman rom unsuccessfully but have yet to flash the boot.img as i havent got S-OFF and figure it wont allow writing to that partition yet, i have had alot of problems rewriting the CID for superCID, have tried many methods including xfactor and manually via fastboot and have been unsucessfull thus far, i understand that its not possible to downgrade Hboot unless S-off is achieved, alas facepalm is not possible unless superCID is achieved, and i cannot rewrite the CID manually or using any scripts i have found, is my Hboot version the problem or is there something im missing here?
help would be much appreciated
Have you tried the hex edit method?
Sent from my Evita
Yeah it returns with an error in adb, system mounted read only, and its deffinatly rooted so I'm not sure how to make system readwrite
Sent from my Wildfire S A510e using xda app-developers app
It would seem there s no sure fire way around this. Unless someone can help me figure out the read only issue in adb using the hex edit method
Sent from my Wildfire S A510e using xda app-developers app
hex edit progress
ok so i fixed the problem by uninstalling htcsync and re installing adb and fastboot via sdk tools, i got the file pulled from my phone and hex edited it, from cid; TELST001 to cid; 11111111 and pushed the file back onto my phone as per instructions, yet when i reboot into bootloader and do fastboot oem readcid it still comes back TELST001. somehow the phone knows what is happening and is changing the hex back to original form..??
ok scratch that, it actually never pulled the file from my phone, that was a file leftover from some script that didnt work, it had a cid of telus001 and my cid reads telst001 so i know that wasnt my file, the adb shell is able to read my phone but not ble to take the mmcblk0p4 file, so when i enter the command dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4 i get 2.0 records in 2.0 records out 1024 bytes transferred at <40960> bytes. so im guessing it was successful, yet when i check my sd root the file is nowhere to be seen!? where am i going wrong here
I just remembered someone had posted a different method, try this one:
http://forum.xda-developers.com/showthread.php?t=2460148
Sent from my Evita
argh
O..K so i rebooted the one xl ad the file was there, i copied to desktop, hex edited, and did dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4 to push the file back. read as successful in adb, so i did reboot fastboot and fastboot oem readcid, CID READS TELST001 STILL i must be retarded or something
timmaaa said:
I just remembered someone had posted a different method, try this one:
http://forum.xda-developers.com/showthread.php?t=2460148
Sent from my Evita
Click to expand...
Click to collapse
ok thanks man, ill give it a go now
st3wy said:
ok thanks man, ill give it a go now
Click to expand...
Click to collapse
yeah i tried it both ways and still gets cid TELST001 :l it seems im so close, the file was the same size the names were right, all commands i entered were spot on. just cant figure this one out
st3wy said:
yeah i tried it both ways and still gets cid TELST001 :l it seems im so close, the file was the same size the names were right, all commands i entered were spot on. just cant figure this one out
Click to expand...
Click to collapse
i even tried doing echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
and still get INFOcid: TELST001
is it possible that my cid is stored somewhere other than mmcblk0p4 or mmcblk0p5??
You might be stuck in the same situation that at&t users were in after taking the 3.18 update. Basically the system partition is read only, so temp root was needed to get SuperCID in order to unlock their bootloader. The only difference being that you can unlock your bootloader just fine but can't get SuperCID in order to get s-off. I'm not sure on this, just spitballing ideas.
Sent from my Evita
timmaaa said:
You might be stuck in the same situation that at&t users were in after taking the 3.18 update. Basically the system partition is read only, so temp root was needed to get SuperCID in order to unlock their bootloader. The only difference being that you can unlock your bootloader just fine but can't get SuperCID in order to get s-off. I'm not sure on this, just spitballing ideas.
Sent from my Evita
Click to expand...
Click to collapse
sounds about right, i did read about this. so im guessing because i used temp root to spoof cid and unlock bootloader using the unlock code from that process, that there is no way to 'officially' relock the bootloader, and start the whole process again using a different method, say for instance using adb.. and thus getting bootlocker unlocked without spoofed cid and temp root possibly resulting in the ability to obtain supercid and full root? i have got supersu flashed through recovery.. but yeah obviously having serious issues with supercid atm.. thanks so much for your help this far man came a long way this arvo, just cant see the light at the ed of the tunnel... its like if i was able to flash Hboot i may be able to get around, but that requires s-off, which reuires super cid, which requires different Hboot lol
you wouldnt happen to know anyone else that might be able to brainstorm on this would you? although from looking at the threads youve made, it seems your possibly THE most educated person on this matter... idk might just have to wait for a dev to look into this and find a loophole. im not that good unfortunately. again, thanks for your help man. if you do get any ideas dont hesitate to post em up on this thread. cheers.
I'm definitely not the most educated person in this kinda stuff, I just read a lot on here and remember the ins and outs of this device. Finding a loophole around this is something that the HTC experts would have to work on, people like beaups, jcase, those kinda guys. Like I said though I'm not even sure if what I said is what's stopping you, I could be completely wrong.
Sent from my Evita
well, ive had one thaught that might be a stupid one but possibly one of the only things i am yet to try.. if i go through with the s-off and see if it works, although my phone is reading cid it may actually have supercid because like i say, its been successful in adb just hasnt returned a supercid through the fastboot commands, i guess the only question is will i brick my device if i follow through with s-off when i dont have supercid or will it just fail and all will be gravy
is there anyway to get them in on this thread so they know where im up to, or would i have to PM them exclusively and explain all over again
btw i think your right, system is read only. thats why the pushes arent working, even though they say they are in adb, either that or the phones cid and the RUU's cid are different and fastboot oem readcid is reading softwares cid and not the phones cid?
either way im going to drink a beer and go outside for a while, thanks again timmaaa, i didnt expect anyone to reply to this thread for a good while. like i said if u happen to have contact with the devs or anyone else that might be able to help, id be stoked. cheers bro and peace out!
You can try SuperCID but it just won't work. You can try contacting them and pointing them to this thread, but I think they're pretty busy guys so I don't know if they'll be able to help. The CID that shows up when using the fastboot command is definitely the phone CID and not the software CID.
Sent from my Evita
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?