[SOLVED!!] Customer ID Error on RUU - AT&T, Rogers HTC One X, Telstra One XL

So my ATT One X is soft bricked and when I run RUU_Evita_UL_Cingular_US-1.82.502 It gives me the customer ID error.
I rooted, unlocked bootloader, and flashed CMR, but it is now no longer rooted and the bootloader is relocked.
I did modify the CID to "11111111" to unlock the bootloader, but without me being rooted I am unable to put the original "mmcblk0p4" back on (idk if that even matters.) I have no backups and absolutely everything is erased.
I did flash the stock recovery img file, but I don't know if it was relevant to international One X or if there is one specifically for ATT One X.
I guess a fix would be making a goldcard, without an sd card somehow....
Thanks for the Help.

Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium

_MetalHead_ said:
Never seen that error before. Have you tried running the 1.85 RUU? I have RUU'd multiple times while still having the SuperCID so I don't think that's the issue.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I was actually using the 1.7 RUU
I'll try 1.82 then 1.85. Hopefully that will work.
Thanks for the quick reply! :good:

Have you tried to relocking the boot loader?
fastboot oem lock
Then run ruu.
The ruu will flash the stock recovery.
Sent from my HTC One X using xda premium

Still not going through and getting same error....
Any ideas?
Thanks.

Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium

18th.abn said:
Are in Canada? That would mean u need to use the rogers ruu, not the evita. Or, are u positive u changed your cid to 11111111 and not ROGER001. There were tutorials in the beginning doing this before supercid 11111111 was found. But customer I'd means either, rogers or evita typically. Evita ruu won't work on rogers and vice versa:thumbup:
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
No. I'm in US on ATT network. And yes I did change the CID to 11111111 because I used that method to unlock my bootloader.
I've tried several RUUs for my phone and still get same error. If I were to verify I had changed the CID I would have to be rooted.
Is it possible to root a soft-bricked device????

What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
---------- Post added at 08:51 PM ---------- Previous post was at 08:44 PM ----------
I was stuck with a soft brick when I interrupted the installation of a ROM that was a bad download.
I was able to do what I said in my previous post and it fixed me right up

gunnyman said:
What's the error number?
Depending on what it is, there are different fixes.
if you can still do fastboot commands I'd unlock the bootloader again then push the twrp with USB support.
Once you do that you can flash the rom of your choice by copying it to your phone from TWRP.
Click to expand...
Click to collapse
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.

ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse

gunnyman said:
ArcriusOneX said:
It's error #131.
Can I unlock bootloader without root? I have tried running the adb shell in cmd, but the device cannot be found.
I was able to check if I had the SuperCID, and unfortunately it has changed back to stock.[/QUOTEhmm I've never switched my CID back so I am not sure if it will work, but try this
get to the bootloader (power volume down)
from bootloader select fastboot
once in fastboot mode
with phone plugged into usb type
fastboot flash unlocktoken Unlock_code.bin just like you did to unlock the bootloader in the first place just make sure that adb, fastboot, and the unlock.bin file are all in the same directory on your computer
once you are unlocked you should be able to do the rest
Error 131 is related to using the wrong RUU for your CID SuperCID will override this error. If you flashed your CID back to the AT&T one the only RUU you can flash (I think) is the 1.85 one
Click to expand...
Click to collapse
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse

ArcriusOneX said:
gunnyman said:
Yeah I actually was able to unlock the bootloader already. Sorry I spoke too soon!
How do I go about pushing the twrp?
Click to expand...
Click to collapse
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse

gunnyman said:
ArcriusOneX said:
download it from and follow the directions here http://forum.xda-developers.com/showthread.php?t=1703626
very simple and straightforward
Click to expand...
Click to collapse
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse

ArcriusOneX said:
gunnyman said:
SUCCESS!!!! :laugh::laugh::laugh:
Thank you so much! You resurrected my phone!
I'm guessing this is similar to CMR?? Looks a lot nicer.
Click to expand...
Click to collapse
yeah I like it better myself it's faster.
glad you're all fixed
Click to expand...
Click to collapse

Related

Broken One X

Quite recently I received HTC One X at&t, I unblocked the loader this way http://forum.xda-developers.com/showthread.php?t=1734558, but there was a failure and I lost the original files. Phone ceased to be loaded, and only was in cyclic reset. I tried to stitch an original insertion, it was established, but phone everything also reboots. Then I thought that a problem in CID and the unblocked loader. I replaced the CID back with CWS __ 001, and blocked the loader. Tried to stitch once again, but changed nothing. Now I have phone which only enters into fastboot and I can't make anything with it.
Can prompt something? Thanks.
I think you should try a RUU
Sent from my unknown using xda premium
JakeOcn said:
I think you should try a RUU
Click to expand...
Click to collapse
I tried to flash successfully, but nothing changed, still does not boot
http://forum.xda-developers.com/member.php?u=4623496
Dromych said:
Quite recently I received HTC One X at&t, I unblocked the loader this way http://forum.xda-developers.com/showthread.php?t=1734558, but there was a failure and I lost the original files. Phone ceased to be loaded, and only was in cyclic reset. I tried to stitch an original insertion, it was established, but phone everything also reboots. Then I thought that a problem in CID and the unblocked loader. I replaced the CID back with CWS __ 001, and blocked the loader. Tried to stitch once again, but changed nothing. Now I have phone which only enters into fastboot and I can't make anything with it.
Can prompt something? Thanks.
Click to expand...
Click to collapse
can u even reach Hboot? i am sure u know how to. if u can reach that screen.. its fixable
if u cant ..mssg niceppl with u r problem .. talk to him .. he can help you out.. hopefully
i suggest you to claim warranty.. if u have it
Ruu will work just fine.
Change your cid back to 11111111 and relock your bootloader, fastboot oem lock, ruu:beer: pm me once Ruu is done and we get your imei n sn fixed up
Added- you probably have to change your imei, s/n back to factory also before inserting simcard. Get the info off the box and pm me
Sent from my EVO using xda premium
18th.abn said:
Ruu will work just fine.
Change your cid back to 11111111 and relock your bootloader, fastboot oem lock, ruu:beer: pm me once Ruu is done and we get your imei n sn fixed up
Added- you probably have to change your imei, s/n back to factory also before inserting simcard. Get the info off the box and pm me
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I do not have access to adb, do this: (
Dromych said:
I do not have access to adb, do this: (
Click to expand...
Click to collapse
Get adb then.
atticusmas said:
Get adb then.
Click to expand...
Click to collapse
How I can receive it?, I have the blocked loader, fastboot, native CID and native recovery, the RUU installation gives of nothing.
U need the ruu.exe that matches your device branding and firmware version. E.g. evita 1.85 or rogers 1.73. Download it to pc, turn phone to fastboot USB in bootloader, plug in to USB and double click ruu.exe file. Follow on screen directions.
Sent from my EVO using xda premium
Dromych said:
How I can receive it?, I have the blocked loader, fastboot, native CID and native recovery, the RUU installation gives of nothing.
Click to expand...
Click to collapse
Install the android sdk on your computer. Then you have adb
Sent from my One X using xda premium
atticusmas said:
Install the android sdk on your computer. Then you have adb
Sent from my One X using xda premium
Click to expand...
Click to collapse
I have not loaded the firmware, you know? Cyclic reboot, reinstall the RUU does not fix this problem
I installed this firmware RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17.32.09.12_10.86.32.08L_release_262092_signed.exe, all going well, but the result is your phone does not boot. After an unsuccessful unlock
Have u tried booting after ruu, without unlocking bootloader?
Sent from my EVO using xda premium
I didn't understand exactly what you did..but if you can boot to hboot you can fix this..
1. first you need to have adb and fastboot installed and working correctly.
2. take out your simcard.
3. relock your bootloader, run command fastboot oem lock
4. run the at&t ruu since you changed your cid back to cws__001.
5. after ruu just let it boot, it should boot. if ruu ran correctly...
6. if you are able to boot, now go to the bootloader again check your imei sn and mb.
7. if above information are correct(matching your box), root your phone and supercid it.
8. run the tool again. follow instructions
niceppl said:
I didn't understand exactly what you did..but if you can boot to hboot you can fix this..
1. first you need to have adb and fastboot installed and working correctly.
2. take out your simcard.
3. relock your bootloader, run command fastboot oem lock
4. run the at&t ruu since you changed your cid back to cws__001.
5. after ruu just let it boot, it should boot. if ruu ran correctly...
6. if you are able to boot, now go to the bootloader again check your imei sn and mb.
7. if above information are correct(matching your box), root your phone and supercid it.
8. run the tool again. follow instructions
Click to expand...
Click to collapse
1 point. - I can not get access to adb
3-4. I locked the boot loader, and returned to the cid CWS_001
5. I flashed RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09.12_10.86.32.08L_release_262092_signed.exe
6. in the hboot, all my data is displayed correctly
7. ooops... phone restarts all the time on a white logo HTC, I can not boot system
Why can't you get access to adb?
You say your info is correct in hboot. So boot into hboot, plug your phone into your computer and run adb. Easy no?
cmaxwe said:
Why can't you get access to adb?
You say your info is correct in hboot. So boot into hboot, plug your phone into your computer and run adb. Easy no?
Click to expand...
Click to collapse
adb does not work in hboot.
Dromych said:
1 point. - I can not get access to adb
3-4. I locked the boot loader, and returned to the cid CWS_001
5. I flashed RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09.12_10.86.32.08L_release_262092_signed.exe
6. in the hboot, all my data is displayed correctly
7. ooops... phone restarts all the time on a white logo HTC, I can not boot system
Click to expand...
Click to collapse
the cid is cws__001 not cws_001
are you sure the ruu flashed without any problems？
did you installed htc_sync if not install it and ruu again
Sent from my HTC PH39100 using xda app-developers app
niceppl said:
the cid is cws__001 not cws_001
are you sure the ruu flashed without any problems？
did you installed htc_sync if not install it and ruu again
Sent from my HTC PH39100 using xda app-developers app
Click to expand...
Click to collapse
Yes, Cid CWS__001, RUU flashed without problems, but does not fix the problem
drivers are installed
Dromych said:
Yes, Cid CWS__001, RUU flashed without problems, but does not fix the problem
drivers are installed
Click to expand...
Click to collapse
unlock recovery and flash a custom rom see if it can boot
Sent from my HTC One XL using xda app-developers app
niceppl said:
unlock recovery and flash a custom rom see if it can boot
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
How can I unlock the recovery? I have locked bootloader
I can not flash a custom recovery via fastboot

supercid says 11111111 on 2.20 but cant unlock bootloader

i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
very simple to fix. The fact that you got to the "ready to unlock?" screen means the unlock token works.
go into settings on the phone go to power. Turn OFF fastboot.
Power off the phone completely.
Boot to bootloader
send the unlock.bin again
this time it will stick.
saketh91 said:
i updated to 2.20 ruu and thank god i already had supercid set to 11111111.but now when i try to unlock bootloader from htcdev,it doesn't stick.please help
Click to expand...
Click to collapse
Sometimes the phone can get confused about its locked state.
To fix:
-Force reboot the phone. Hold the power button for 10+ seconds until bottom lights flash and then stop.
-Boot in to bootloader
Now force the phone to lock even if you think it is locked already.
-fastboot oem lock
-fastboot flash unlocktoken Unlock_code.bin
Sending "fastboot oem lock" tends to get the phone back on the right track so it doesn't just keep rebooting in to a relocked state.
get into bootloader manually volume down + power.
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
yes root will happen.
unlock bootloader. Install twrp recovery. Flash the root package found here http://forum.xda-developers.com/showthread.php?t=1673935
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Ethere said:
Thanks so much gunny. One quick question. I got the bootloader unlocked without a problem. Now, twrp recovery...can I just do that through GooManager, or should I do it another way?
Click to expand...
Click to collapse
I think you may have to use fastboot flash recovery recovery.img because of the new limitations of the new HBOOT. It might be only for boot.imgs though
That worked rohan32 Thanks so much to both of you. Now I have an unlocked bootloader and TWRP installed. Going for root now. Thank you thank you thank you! You guys have saved me from wanting another phone!
[EDIT]Rooted as well. Again, thank you both so much!
thanks everyone i solved my problem.dint except quick replies from you guys.
Ethere said:
Wow, so I've been under the impression that if I updated to 2.20 via the RUU that I couldn't do anything. I know my supercid is definitely 11111111. I can still unlock the bootloader if this is the situation? Root wouldn't happen though right?
Click to expand...
Click to collapse
If you stay away from the AT&T cid you will be fine.
In theory things could change but at the moment so long as you have super cid prior to RUU flashing you will be fine.
OK I just got my AT&T HOX today and from what I've read hear there is no way to root it? Since I have 2.20.502.7 710RD but if I use super cid I can flash roms?
Without root you can't get super Cid
Please update the title and add "Resolved"
Sent from my HTC One XL using xda premium

Need help finding my RUU

baseband: 0.17.31501S.10_2_10.27.31501S.10L
CID: HTC_K18
Image Version: 1.84.461.11
I can't find my ruu and i was searching here:
http://forum.xda-developers.com/showthread.php?t=1543588 (i have the s4 version)
the closest one found was with my baseband version but had a different image version.
Try this one
http://www.filefactory.com/file/zfv..._2_10.27.31501S.10L_release_265369_signed.exe
Sent from my HTC One S using xda app-developers app
mirror
blackcell1 said:
Try this one
http://www.filefactory.com/file/zfv..._2_10.27.31501S.10L_release_265369_signed.exe
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
thats the one i was talking about but as you can see the image version is different from mine
i have 1.84.461.11 and the download have 1.84.666.9.
my question is if it will be compatible?
Hi you, why you not change CID to supper CID 1111111?, you can flash any RUU file if you want.
thanhthao2002 said:
Hi you, why you not change CID to supper CID 1111111?, you can flash any RUU file if you want.
Click to expand...
Click to collapse
cause someone told me that i need to have s-off to supercid and i can't s-off one s.
i don't know if i need s-off or just unlocked bootloader?
LSGio said:
cause someone told me that i need to have s-off to supercid and i can't s-off one s.
i don't know if i need s-off or just unlocked bootloader?
Click to expand...
Click to collapse
You need S-OFF if you have an S3. If you have an S4, just an unlocked bootloader is fine.
Sent from my HTC One S using Tapatalk 2
usaff22 said:
You need S-OFF if you have an S3. If you have an S4, just an unlocked bootloader is fine.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
i have s4 but can you please give me a link on how to supercid?
thank you!
LSGio said:
i have s4 but can you please give me a link on how to supercid?
thank you!
Click to expand...
Click to collapse
Reboot phone into fastboot mode, open cmd window on your computer linking to the adb path.
fastboot oem writecid 11111111. Being SuperCID you can flash whatever RUU, but not receive OTA updates.
Sent from my HTC One S using Tapatalk 2
usaff22 said:
Reboot phone into fastboot mode, open cmd window on your computer linking to the adb path.
fastboot oem writecid 11111111. Being SuperCID you can flash whatever RUU, but not receive OTA updates.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
first i have to say that i have a S4 version that i checked with cpu spy and you told me that i only need unlocked bootloader so its unlocked and when i try to supercid it says: FAILED (status read failed (Too many links)) and then i get stuck in bootloader mode and i have to get it out of bootloader mode manually (command fastboot reboot-bootloader didn't help cause i got a respond of waiting for device)
and then when i boot again into fastboot usb and type fastboot getvar cid it says HTC__K18 like the old one.
what do i have to do?
is there any way to s-off htc one s?
LSGio said:
first i have to say that i have a S4 version that i checked with cpu spy and you told me that i only need unlocked bootloader so its unlocked and when i try to supercid it says: FAILED (status read failed (Too many links)) and then i get stuck in bootloader mode and i have to get it out of bootloader mode manually (command fastboot reboot-bootloader didn't help cause i got a respond of waiting for device)
and then when i boot again into fastboot usb and type fastboot getvar cid it says HTC__K18 like the old one.
what do i have to do?
is there any way to s-off htc one s?
Click to expand...
Click to collapse
There is a link to Super CID instructions in the dev forum at http://forum.xda-developers.com/showthread.php?t=1671643
Also, there is no s-off yet for HTC One S.
Third, what carrier do you have? I did not recognize your CID. If there is a RUU that you think exists that Football has not posted in his thread, than I suggest PM ing him. Thats how I was able to get the three Bell Mobility RUUs onto FileFactory. But I am curious about your carrier as it may already be in his list.
Cheers,
AKToronto
AKToronto said:
There is a link to Super CID instructions in the dev forum at http://forum.xda-developers.com/showthread.php?t=1671643
Also, there is no s-off yet for HTC One S.
Third, what carrier do you have? I did not recognize your CID. If there is a RUU that you think exists that Football has not posted in his thread, than I suggest PM ing him. Thats how I was able to get the three Bell Mobility RUUs onto FileFactory. But I am curious about your carrier as it may already be in his list.
Cheers,
AKToronto
Click to expand...
Click to collapse
My carrier is cellcom, israel.

[Q] Can't update firmware, Unlocked/Tampered S-ON

I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.
seth50k said:
I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.
Click to expand...
Click to collapse
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium
31ken31 said:
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?
seth50k said:
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?
Click to expand...
Click to collapse
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?
RollTribe said:
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?
Click to expand...
Click to collapse
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.
seth50k said:
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.
Click to expand...
Click to collapse
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.
RollTribe said:
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.
Click to expand...
Click to collapse
I've tried running RUU, it gets about halfway and fails. Do I need to flash the stock recovery and relock first, then run a RUU?
U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium
If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app
breezedragon said:
U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.
seth50k said:
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.
Click to expand...
Click to collapse
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
exad said:
If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Unlock, flash a sense rooted rom, soff and then ruu up to 3.18
Sent from my One X using xda app-developers app
RollTribe said:
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?
seth50k said:
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?
Click to expand...
Click to collapse
Yup, you can swap the last two if you want
RollTribe said:
Yup, you can swap the last two if you want
Click to expand...
Click to collapse
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yep, looks like it's bricked. http://forum.xda-developers.com/showthread.php?t=2181929
seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.
RollTribe said:
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.
Click to expand...
Click to collapse
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.
Sorry about your phone. It's Jtagg or new phone.
---------- Post added at 02:34 PM ---------- Previous post was at 02:34 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.
Click to expand...
Click to collapse
They state on their site that after unlocking the bootloader, RUU/OTA could brick you.
If you plan to try warranty with HTC, do not mention that you unlocked. They will charge you 200 straight up no matter what you say.
RollTribe said:
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
But was it the 3.18? It applies specifically for the AT&T 3.18 (and for some 3.17 JB RUUs on other carriers, and reported by some folks on this forum).
If you were able to run the 3.18 RUU successfully with SuperCID and S-on, I believe this is the first I've heard of it.
---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
Click to expand...
Click to collapse
SuperCID as implemented on the AT&T One X is a mod/hack, and therefore not explicitly "allowed" by HTC. They can't really be held responsible for the effects of it.
SuperCID shouldn't be "expected" to brick under these conditions (worked fine with pre-JB RUUs), and nobody here has really been able to explain exactly why the phone bricks from SuperCID. But unfortunately, it does.

Phone won't get past boot screen

Was running cm10.2 with the new Torched Kernel. After running for a day, the phone froze and shut down. Ever since, the phone now won't get past the htc splash screen. I just RUU'd to 3.18 and it is still doing it. What's happening?
mikel.canovas said:
Was running cm10.2 with the new Torched Kernel. After running for a day, the phone froze and shut down. Ever since, the phone now won't get past the htc splash screen. I just RUU'd to 3.18 and it is still doing it. What's happening?
Click to expand...
Click to collapse
Can you get to bootloader? Fastboot access? You were soff previously correct?
Sent from my One Xl using Tapatalk 2
jrior001 said:
Can you get to bootloader?
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
Yeah, and fastboot. ADB for some reason doesn't seem to be recognized, but fastboot is. That may be my computer though. I cannot get to recovery from bootloader, it does the sam hang on the htc screen
Thanks,
Mikel
mikel.canovas said:
Yeah, and fastboot. ADB for some reason doesn't seem to be recognized, but fastboot is. That may be my computer though. I cannot get to recovery from bootloader, it does the sam hang on the htc screen
Thanks,
Mikel
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/evita
From twrp's site grap the 2.6.3 recovery.IMG and with phone in bootloader where you see "fastboot usb" type in cmd promt fastboot flash recovery openrecovery-twrp-2.6.3.0-evita.img
And the fastboot reboot-bootloader
Then navigate and try to get to recovery again
If you get that far flash ROM again, just that for now and relax for a bit
Sent from my One Xl using Tapatalk 2
Getting an error after writing recovery. Saying FAILED (remote: not allowed)
mikel.canovas said:
Getting an error after writing recovery. Saying FAILED (remote: not allowed)
Click to expand...
Click to collapse
And that RUU ran fine? Is your bootloader still unlocked? Really the RUU is the best thing...thats the goto when everything else fails
Sent from my One Xl using Tapatalk 2
jrior001 said:
And that RUU ran fine? Is your bootloader still unlocked? Really the RUU is the best thing...thats the goto when everything else fails
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
No bootloader is "relocked". I was in fastboot when I ran the RUU since ADB is not being recognized when in bootloader. RUU was successful, didn't seem like anything went wrong
Bootloader unlocked or relocked?
If I couldn't boot the phone, I would restore my last known good nandroid (you did make one, right???). Going for the RUU is a bit of the nuclear option, when there are easier ways to recover.
redpoint73 said:
Bootloader unlocked or relocked?
If I couldn't boot the phone, I would restore my last known good nandroid (you did make one, right???). Going for the RUU is a bit of the nuclear option, when there are easier ways to recover.
Click to expand...
Click to collapse
Bootloader says relocked. Can't RUU with unlocked bootloader. I can't get into recovery to perform nandroid. RUU seemed to be the only option for me. And it didn't work
mikel.canovas said:
Bootloader says relocked.
Click to expand...
Click to collapse
You need to unlock bootloader again to flash TWRP.
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Thanks for the help,
Mikel
mikel.canovas said:
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Thanks for the help,
Mikel
Click to expand...
Click to collapse
Were you s-off prior to all this? What hboot/few version did you have?
Best guess is that the ruu didn't complete properly either. And you may have to go through process and pull unlock token again. Been a since I had to ruu but I vaugely remember having to do that all over again
Sent from my One Xl using Tapatalk 2
mikel.canovas said:
unlocking bootloader fails. Saying unlock token check failed. It shouldn't fail though, it's the same unlock token I've been using in the past. But that doesn't change the fact that my phone should be booting up after the RUU. How come that is happening?
Click to expand...
Click to collapse
Using the unlock token is known to sometimes fail and require repeated attempts, just keep trying.
Not sure why the RUU didn't work, that is weird.
jrior001 said:
Were you s-off prior to all this? What hboot/few version did you have?
Best guess is that the ruu didn't complete properly either. And you may have to go through process and pull unlock token again. Been a since I had to ruu but I vaugely remember having to do that all over again
Sent from my One Xl using Tapatalk 2
Click to expand...
Click to collapse
I've done the RUU twice now. Same results. Was s-off with 2.14 hboot
mikel.canovas said:
Bootloader says relocked. Can't RUU with unlocked bootloader. I can't get into recovery to perform nandroid. RUU seemed to be the only option for me. And it didn't work
Click to expand...
Click to collapse
You can RUU with an unlocked bootloader, especially since you're s-off.
Sent from my Evita
timmaaa said:
You can RUU with an unlocked bootloader, especially since you're s-off.
Sent from my Evita
Click to expand...
Click to collapse
I already have RUU'd twice though. And I'm pretty sure you can't. It fails and that error is fixed by relocking the bootloader
mikel.canovas said:
I already have RUU'd twice though. And I'm pretty sure you can't. It fails and that error is fixed by relocking the bootloader
Click to expand...
Click to collapse
You absolutely can RUU with a locked bootloader as long as you're s-off, I've done it on two Evitas, so have many others. It must have failed for another reason.
Sent from my Evita
timmaaa said:
You absolutely can RUU with a locked bootloader as long as you're s-off, I've done it on two Evitas, so have many others. It must have failed for another reason.
Sent from my Evita
Click to expand...
Click to collapse
Then why has it failed 3 times? RUU is reporting successful. So what's the error?
Which error code is it giving you?
Sent from my Evita
timmaaa said:
Which error code is it giving you?
Sent from my Evita
Click to expand...
Click to collapse
RUU gives no error. It shows that it's successful

Categories

Resources