Related
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
reflash
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
thesm4rt1 said:
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
Click to expand...
Click to collapse
I will definitely be trying that. Will be back in a couple of hours and let you know how it went. Thank you!
bbonline said:
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Butters619 said:
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Click to expand...
Click to collapse
I did do the factory wipe.
By the way, I tried what I was told to do and nothing happened. It successfully flashes the boot image and recovery, but when it tries to boot into the recovery, it just freezes in the recovery with the word TEAMWIN and a blue background....No menu or options.... I did try several different ways by downloading and installing several versions of the CWM and TWRP, but no success. Any other suggestions? Will I be stuck with this piece of brick now? Please help.
bbonline said:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Butters619 said:
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Click to expand...
Click to collapse
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
bbonline said:
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
Click to expand...
Click to collapse
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Butters619 said:
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Click to expand...
Click to collapse
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
bbonline said:
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
Click to expand...
Click to collapse
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
Darn.... I just hope I don't have to deal with sending it for any repair. Gave you thanks!
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
But only if they reboot and look, which from what I've seen here, they never seem to do.
iElvis said:
But only if they reboot and look, which from what I've seen here, they never seem to do.
Click to expand...
Click to collapse
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
Butters619 said:
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Click to expand...
Click to collapse
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
trichrome1 said:
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
Click to expand...
Click to collapse
Nope once you unlocked it won't ever say locked again. Just re-locked
gunnyman said:
Nope once you unlocked it won't ever say locked again. Just re-locked
Click to expand...
Click to collapse
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
You should probably double check that. Anybody with an AT&T One X had to have SuperCID to unlock their bootloader so that wouldn't matter. I have unlocked two AT&T One Xs and run the 1.85 RUU on both (one of them a couple times) and I have run the 2.20 RUU on one. every time it says RELOCKED.
Mine did this to when going to 4.5.
I did the following to get back into Recovery.
Use fastboot to flash the boot.img from the cleanrom 4.5 zip.
"fastboot flash boot boot.img"
I then flashed the recovery (TWRP 2.2.1.4 at the moment) again to the phone.
next I erased Cache.
"fastboot erase cache"
I then used the phone itself to reboot the bootloader and went into recovery. It took about 10 minutes but recovery finally booted.
At this point I had no access to anything on the SD card. so I selected mount and mounted the sd card as disk drive to access it through my PC. I was forced to format the drive at this point and loaded a fresh copy of the ROM onto the drive for flashing.
You probably just got a wrong recovery. The recovery on twrp website didn't work for me. The one I downloaded from the development section works fine.
Sent from my One X using xda app-developers app
trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
Screenshots PLS
Okay so i was having wifi issues on Trickdroid 7.0.0 TMOUS.. so i did a little searching and what not and found out i had to flash 2.3.5 parts/radio to get it working. before hand i was getting full bars/4g. After i flashed both 2.3.5 extra partitions, and the 2.3.5 radio i reboot to find out my wifi finally works, then i notice i have no signal.. i tried rebooting, etc didnt work. tried restoring the backup i made through clockwork before i flashed the radio; didnt work. tried taking out my SIM card and putting it back in, didnt work. ive tried flashing miui, trickdroid 8.x.x, a nandroid posted from stock 2.3.5, nothing will bring back my signal. so i thought maybe my SIM card is messed up, i put it in my backup go phone and i get full bars.
also, i tried RUU both 1.5.x and 1.8.x and both give me RUU error 155 after its done "sending files"..
any help would be awesome. could i flash a older radio or something??
edit: im on hboot 1.09 btw
Okay looks like no one knows how to fix this?
tried flashing a older radio and no go, and just flashed RUU 1.84 and no go as well. i flashed the international trickdroid and upon first boot i had signal (no 4g) and i was able to send a text to myself and received it. then i restarted my phone and.. gone that was before i flashed the RUU.
stratax said:
Okay looks like no one knows how to fix this?
tried flashing a older radio and no go, and just flashed RUU 1.84 and no go as well. i flashed the international trickdroid and upon first boot i had signal (no 4g) and i was able to send a text to myself and received it. then i restarted my phone and.. gone that was before i flashed the RUU.
Click to expand...
Click to collapse
Try this.
Originally Posted by ckpv5 View Post
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One S after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img / unlocked bootloader
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
---------- Post added at 09:54 PM ---------- Previous post was at 09:41 PM ----------
stratax said:
Okay so i was having wifi issues on Trickdroid 7.0.0 TMOUS.. so i did a little searching and what not and found out i had to flash 2.3.5 parts/radio to get it working. before hand i was getting full bars/4g. After i flashed both 2.3.5 extra partitions, and the 2.3.5 radio i reboot to find out my wifi finally works, then i notice i have no signal.. i tried rebooting, etc didnt work. tried restoring the backup i made through clockwork before i flashed the radio; didnt work. tried taking out my SIM card and putting it back in, didnt work. ive tried flashing miui, trickdroid 8.x.x, a nandroid posted from stock 2.3.5, nothing will bring back my signal. so i thought maybe my SIM card is messed up, i put it in my backup go phone and i get full bars.
also, i tried RUU both 1.5.x and 1.8.x and both give me RUU error 155 after its done "sending files"..
any help would be awesome. could i flash a older radio or something??
edit: im on hboot 1.09 btw
Click to expand...
Click to collapse
So can you post the link to where you got the "2.3.5 extra partitions" and the radio from. And how did you flash them on your phone?
dc211 said:
Try this.
---------- Post added at 09:54 PM ---------- Previous post was at 09:41 PM ----------
So can you post the link to where you got the "2.3.5 extra partitions" and the radio from. And how did you flash them on your phone?
Click to expand...
Click to collapse
thank you for your reply. this is where i got it. http://forum.xda-developers.com/showthread.php?p=32170653 from "Rsotbiemrptson" i also got the radio update from him, what he posted.. http://forum.xda-developers.com/showthread.php?t=1657831&page=285 look at my quote at the bottom.
stratax said:
thank you for your reply. this is where i got it. http://forum.xda-developers.com/showthread.php?p=32170653 from "Rsotbiemrptson" i also got the radio update from him, what he posted.. http://forum.xda-developers.com/showthread.php?t=1657831&page=285 look at my quote at the bottom.
Click to expand...
Click to collapse
This is a tricky one but I got a few ideas. Need a little bit more info. What version of hboot do you have?
---------- Post added at 11:10 PM ---------- Previous post was at 11:02 PM ----------
dc211 said:
This is a tricky one but I got a few ideas. Need a little bit more info. What version of hboot do you have?
Click to expand...
Click to collapse
Oh i see 1.09 now. I understand why the updated adsp wcnss would fix your wifi but I can't really figure out what broke your radio. You flashed a bunch of different roms so you ruled that out. I would go ahead and try flashing the 2.35 radio again and see if that helps. If not flash an older radio and see.
I know how to undo all the changes you made but lets see what a new radio flash does first. Don't just flash the one you have but re-download it fresh and flash with that.
dc211 said:
This is a tricky one but I got a few ideas. Need a little bit more info. What version of hboot do you have?
---------- Post added at 11:10 PM ---------- Previous post was at 11:02 PM ----------
Oh i see 1.09 now. I understand why the updated adsp wcnss would fix your wifi but I can't really figure out what broke your radio. You flashed a bunch of different roms so you ruled that out. I would go ahead and try flashing the 2.35 radio again and see if that helps. If not flash an older radio and see.
I know how to undo all the changes you made but lets see what a new radio flash does first. Don't just flash the one you have but re-download it fresh and flash with that.
Click to expand...
Click to collapse
okay thank you. i will try a few more things. i really hope its not blacklisted, i really dont think it is though since it happened RIGHT afterwards.
oh other details is i didnt wipe or anything i just flashed both, partition parts/radio then rebooted and wifi worked then had no service.
stratax said:
okay thank you. i will try a few more things. i really hope its not blacklisted, i really dont think it is though since it happened RIGHT afterwards.
oh other details is i didnt wipe or anything i just flashed both, partition parts/radio then rebooted and wifi worked then had no service.
Click to expand...
Click to collapse
Since it just happened after you flashed new stuff that leads me to believe that was the cause. I'm pretty sure I know how to fix. But if it were me I'd start with re-flashing the radio.
I just installed the OTA 2.3.5 update over 1.84 RUU and still no go, im going to try to install the radio through recovery and see if that fixes it.
edit: well that was dumb.. now i have the updated hboot :l
stratax said:
I just installed the OTA 2.3.5 update over 1.84 RUU and still no go, im going to try to install the radio through recovery and see if that fixes it.
edit: well that was dumb.. now i have the updated hboot :l
Click to expand...
Click to collapse
Sorry to hear that! I didn't expect you to try that route. However, it should have resolved your issue the OTA would have overwritten everything you did. You couldn't get a cell signal after the RUU or OTA?
dc211 said:
Sorry to hear that! I didn't expect you to try that route. However, it should have resolved your issue the OTA would have overwritten everything you did. You couldn't get a cell signal after the RUU or OTA?
Click to expand...
Click to collapse
Still a no go.. D: im going to try and install trickdroid 7.0.0 and re-install that radio just to double check.
stratax said:
Still a no go.. D: im going to try and install trickdroid 7.0.0 and re-install that radio just to double check.
Click to expand...
Click to collapse
You can't reinstall the radio, those days are over for you. Sorry to be the bearer of bad news. You're stuck with 2.x RUU's only from now on to change radios.
Since your in this spot you might try the latest CM10 nightly they have implemented the radio firmware into the rom itself. That might allow you to sidestep your problem. Also check under about -> phone and see if your imei matches whats on the box that came with the phone.
Okay, i now know its not blacklisted. I just unlocked it with the unlock .exe and put a extra AT&T SIM card laying around and put in the AT&T APN and everything and still says "disconnected because service is unavailable". sooooo, thats good news! i guess..
im going to try to flash a nightly and see if that works. my brother just told me they are probably working on the 4g towers here and maybe thats why it isnt working on this phone and a few other people.. that would be cool, but frustrating that ive done all this.
edit: with the at&t SIM card it just says "no service" in the notifications bar. With the T-Mobile SIM card it says "Emergency calls only". weird
edit2: Still doesnt work with cyanogenmod 10.
stratax said:
Okay, i now know its not blacklisted. I just unlocked it with the unlock .exe and put a extra AT&T SIM card laying around and put in the AT&T APN and everything and still says "disconnected because service is unavailable". sooooo, thats good news! i guess..
im going to try to flash a nightly and see if that works. my brother just told me they are probably working on the 4g towers here and maybe thats why it isnt working on this phone and a few other people.. that would be cool, but frustrating that ive done all this.
edit: with the at&t SIM card it just says "no service" in the notifications bar. With the T-Mobile SIM card it says "Emergency calls only". weird
edit2: Still doesnt work with cyanogenmod 10.
Click to expand...
Click to collapse
im suck in the same place man i hope someone finds out
Yeah I thought today it might be fixed but its not. It finally finds T-Mobile if I search for it but it won't connect to it. It won't connect to att either when I put my att sim in. So I think its the phone having issues.. I've been seeing a lot of other people having them as well.
When I select any network or even automatic registration it says "can't connect right now. Try again later."
I uploaded two screen shots. It won't even let me call T-Mobile..
Sent from my HTC One S using xda app-developers app
stratax said:
Yeah I thought today it might be fixed but its not. It finally finds T-Mobile if I search for it but it won't connect to it. It won't connect to att either when I put my att sim in. So I think its the phone having issues.. I've been seeing a lot of other people having them as well.
When I select any network or even automatic registration it says "can't connect right now. Try again later."
I uploaded two screen shots. It won't even let me call T-Mobile..
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
yep dude same here that sucks man it happened after i put a rom on too
I'm glad I'm not the only one.. this is probably the last htc I will get. I hear it is happening on the one x as well. Tomorrow I'll call T-Mobile and ask about it.
Sent from my HTC One S using xda app-developers app
Can you check under about -> phone and see if your imei matches whats on the box that came with the phone. If you do can you give me the first 4 or 5 digits
stratax said:
I'm glad I'm not the only one.. this is probably the last htc I will get. I hear it is happening on the one x as well. Tomorrow I'll call T-Mobile and ask about it.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
same here man this sucks now i have to start all over but i didnt get it from t mobile but i went in there to get a sim card to see if that was it and they said they cant do nothing so i guess we are suck with a $600 ipod touch with ICS lol
dc211 said:
Can you check under about -> phone and see if your imei matches whats on the box that came with the phone. If you do can you give me the first 4 or 5 digits
Click to expand...
Click to collapse
I don't have the box, and the sticker on the back is mostly worn since I used the phone for a while without the sim cover (I bought it new without it). but I just looked in my google dashboard, and typed *#06# and it matched and I can see the last three digits on the sticker clearly and they match with both as well. the first 5 digits are: 35990
thanks.
ragin69 said:
same here man this sucks now i have to start all over but i didnt get it from t mobile but i went in there to get a sim card to see if that was it and they said they cant do nothing so i guess we are suck with a $600 ipod touch with ICS lol
Click to expand...
Click to collapse
I didn't get it from tmobile either, I bought it new from somebody. had the stickers and everything on it. I swear, every HTC phone I have ever had, has had at least 1 major issue. well, the g1 didn't.
edit: even people on the one v are having the issues:http://forum.xda-developers.com/showthread.php?t=1679461 serious HTC wtf
I changed my CID back to CID__001 from superCID and re-locked phone. Now when I go back to unlock with unlock_code.bin it does not work.
So I regenerate a token identifier....
C:\Users\M\HOX>fastboot oem get_identifier_token
< waiting for device >
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO639E7B248BDCAB6CBEA0577A98CD11AD
INFO0B20640D8180AB31F0B0DC2DDC62EB6A
INFO2524B5D27105D40678D5CC2C0E492220
INFO6A98F11162989E19E5F326B78E38D72E
INFO31E8D7A04B433C18C204D007D4B58689
INFO693ABAC1650EB10FC962312231F9E548
INFOF8D103A3EE4DD17F2D807751D006C739
INFO6254FA142E08F7DDBDF777300D8C8BE5
INFO4A6BA0CE58FFAAF25646B8B8A21CF068
INFO50F67F9A30A6DD984D50E497AF32485D
INFOFF19DBAB976D7F81CDC9E8320BD25E9D
INFOA56BB0B240AB81E35CD9742922C28320
INFOC02CF3A74B8589948155024DA23D31EC
INFO7620755FE9B5CA879B4968E79E239B39
INFOBFC9203AD5ED5373F568492B61B20700
INFO0C5B33DEA9E101B475EAF0E3CD4076F7
INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Users\M\HOX>
On HTC site I get error code 160 mid not allowed when I try to generate a a new .bin
My Token identifier prior to the change was
<<<< Identifier Token Start >>>>
1A5036DDFCC755FA08619C55D40C47D0
A6FB8A57A0F9482C9174A6FA83921F0A
8D639270F2DCA79AD36FFB093D79F319
B9A66170322959FC5A93C12CB3500DF5
C6D42B624710F209FF4A4B70F5EAA9F3
B1947CFA26A96C7969F2788CAA631583
1C643ED6FEA902F1349AC5219AB8648C
C405010F564F16D1F63E3EA5DE089BE6
02D0CC3CBBFDDBBC74B8844144333E0E
BB70889A1F45259AE20ADCE88E7A201A
CF4BEB1A6F44E3162C63959FB800CF99
1E081824821F45DD2BEC4420A29A8F06
F4271D50F0F124EF324F5E41A34CE420
10572E09220654655A467B7AE1EAFB51
1D52CB57BA7154FB9CAC9F782494AF35
D76D2762018B42BEA736906581D9D1BE
<<<<< Identifier Token End >>>>>
The HTCDev.com site won't work with the AT&T CID, that's why it was changed in the first place.
I don't know why you changed the CID, what you hope to gain from it, and I don't recommend it. I don't see how its going to help your situation at all, really it just makes things harder for you (as you see you can't unlock the bootloader now).
I would also kindly suggest you back off from trying any new things, without at least coming on here and asking first if its a good idea. From your other thread, its apparent you are new to this phone, and are doing some things that are not necessarily the best way forward.
redpoint73 said:
The HTCDev.com site won't work with the AT&T CID, that's why it was changed in the first place.
I don't know why you changed the CID, what you hope to gain from it, and I don't recommend it. I don't see how its going to help your situation at all, really it just makes things harder for you (as you see you can't unlock the bootloader now).
I would also kindly suggest you back off from trying any new things, without at least coming on here and asking first if its a good idea. From your other thread, its apparent you are new to this phone, and are doing some things that are not necessarily the best way forward.
Click to expand...
Click to collapse
This phone is crap, from the confusing naming convention , bootloader lock, S-ON and the most fascinating that I just realized last night NO ADB IN BOOTLOADER OR STOCK RECOVERY. Way too complicated to work with.
So I am stuck now because I cannot RUU or get into past bootloader to change the recovery back to TWRP.
ADB works fine in bootloader. Looks like pilot error.
Complaining isn't going to help your case, might hurt it (discourage those of use who have been trying to help you).
Palmetto_X said:
This phone is crap, from the confusing naming convention , bootloader lock, S-ON and the most fascinating that I just realized last night NO ADB IN BOOTLOADER OR STOCK RECOVERY. Way too complicated to work with.
So I am stuck now because I cannot RUU or get into past bootloader to change the recovery back to TWRP.
Click to expand...
Click to collapse
I'm new to the onex myself, so I would like to know why you relocked it after all that work to get it unlocked? Just got mine unlocked with a custom Rom installed, and I don't know why you'd undo that.
Sent from my HTC One XL using Tapatalk 2
sizemore2000 said:
I'm new to the onex myself, so I would like to know why you relocked it after all that work to get it unlocked? Just got mine unlocked with a custom Rom installed, and I don't know why you'd undo that.
Click to expand...
Click to collapse
OP stated in another thread he bought his bootloader unlocked too.
But yes, I agree, there was not point in him relocking it. He wanted to return to stock. I suggested he flash a stock rooted ROM, but he either didn't listen, or was already too far down the relocking path (removed TWRP).
redpoint73 said:
ADB works fine in bootloader. Looks like pilot error.
Complaining isn't going to help your case, might hurt it (discourage those of use who have been trying to help you).
Click to expand...
Click to collapse
Tell me about ADB in bootloader? What do you mean pilot error?
thanks for hanging with me
I think you should PILOT the closest vehicle over the phone to end this misery for everyone
954wrecker said:
I think you should PILOT the closest vehicle over the phone to end this misery for everyone
Click to expand...
Click to collapse
Aren't you supposed to be in school?
Palmetto_X said:
Tell me about ADB in bootloader? What do you mean pilot error?
thanks for hanging with me
Click to expand...
Click to collapse
ADB should work fine in bootloader. Are you getting any error message, or no response when you try to use adb?
Does the phone show up if you type:
adb devices
If not, try to re-install HTC Sync.
---------- Post added at 12:05 PM ---------- Previous post was at 11:37 AM ----------
How did you end up with no TWRP? Did the RUU run partially, and return the phone to stock recovery? Or did you do something else to go to stock recovery?
redpoint73 said:
ADB should work fine in bootloader. Are you getting any error message, or no response when you try to use adb?
Does the phone show up if you type:
adb devices
If not, try to re-install HTC Sync.
---------- Post added at 12:05 PM ---------- Previous post was at 11:37 AM ----------
How did you end up with no TWRP? Did the RUU run partially, and return the phone to stock recovery? Or did you do something else to go to stock recovery?
Click to expand...
Click to collapse
Nothing shows up in adb devices.....I even ran adb logcat and went through all the menus on the phone seeing if it would catch
I will try to re install sync
In attempting to fix the RUU problem I have I would flash stock recovery, stock boot.img, relock, try to RUU......my last genius move was rename cid , stock recovery, boot.img, relock...........now I am dead in the water
Palmetto_X said:
Nothing shows up in adb devices.....I even ran adb logcat and went through all the menus on the phone seeing if it would catch
I will try to re install sync
Click to expand...
Click to collapse
This is the entire cause of your RUU troubles. Your computer is simply not talking to the phone.
Re-install HTC Sync, and try a different USB ports. Problems with the PC not seeing the phone are almost always due to one of these 2 things. Last resort is to use a different PC (if possible).
If adb doesn't see the phone, the RUU won't run either. Get the PC to see the phone, and the RUU will run.
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Wait, you said you relocked. So you must have had an adb/fastboot connection at some point.
Something is royally screwed here. It really seems to me that you are doing things to the phone, that you shouldn't. Seriously, don't do anything more to the phone, unless we tell you to. NOTHING.
How did you flash stock recovery?
What is the state of the phone now?
Flashing boot.img was not a good idea. Stock boot.img + CM10 will result in the phone not booting (wrong kernel), assume that is the state you are now in?
redpoint73 said:
This is the entire cause of your RUU troubles. Your computer is simply not talking to the phone.
Re-install HTC Sync, and try a different USB ports. Problems with the PC not seeing the phone are almost always due to one of these 2 things. Last resort is to use a different PC (if possible).
If adb doesn't see the phone, the RUU won't run either. Get the PC to see the phone, and the RUU will run.
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Wait, you said you relocked. So you must have had an adb/fastboot connection at some point.
Something is royally screwed here. It really seems to me that you are doing things to the phone, that you shouldn't. Seriously, don't do anything more to the phone, unless we tell you to. NOTHING.
How did you flash stock recovery?
What is the state of the phone now?
Flashing boot.img was not a good idea. Stock boot.img + CM10 will result in the phone not booting (wrong kernel), assume that is the state you are now in?
Click to expand...
Click to collapse
I just tried it on another PC and got RUU 2.2 to work. Thank you very much for your persistence.
Ouch. 2.20 RUU means you are now stuck with the 1.14 hboot. Fine if you want to stay stock, but a bit of a pain for flashing custom ROMs, as you now have to flash boot.img separately from fastboot. You also can't flash radios now.
1.73 or 1.85 would have been better. Did you try to run those RUUs on this other PC first?
He deserves hboot 1.14 after talking trash earlier. Hopefully he didn't even try the earlier ruu's
Sent from my HTC One XL
Well, he said he wanted to put it back to stock. If you never plan to root it, 1.14 isn't an issue.
iElvis said:
Well, he said he wanted to put it back to stock. If you never plan to root it, 1.14 isn't an issue.
Click to expand...
Click to collapse
He seems to know a decent amount of tricks (at least enough to be dangerous!). I'd be surprised if he never plans to root. But that's just a guess.
so... theres a way to permanently brick your CID to the point where it cant be changed/unlocked again? :/ now i'm REALLY going to read up on how to relock and get my phone back to the 2.20 RUU (came on that, no sense trying to get an earlier one) for selling it....
redpoint73 said:
He seems to know a decent amount of tricks (at least enough to be dangerous!). I'd be surprised if he never plans to root. But that's just a guess.
Click to expand...
Click to collapse
I'd like him to root his phone and brick it. Then he can come back here to whine about how crappy the phone is when he's the retard.
ok like the title says ive been messing with this thing for a week now and im getting to the point im about to smash it with a hammer
its stuck in a boot loop and i have no backup to load apparently. it was rooted when i got it and my roomate messed it up while i was at work im not sure how or what was done but no matter what i try to do i cant get it out of this loop. im not familiar with android at all ive been reading and searching but i cant find anything helpful ive tried to ruu a few times not really knowing which files to use i finally found out that the radio needed to be the same found a matching file but still no luck i know im gonna get flamed for being so uneducated in this matter but i have indeed searched and i feel im left with no other option then to ask for assistance here
i can get to the boot loader and im just going to type down exactly what i see on it although i dont really know what any of it means
***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
jun 11 2012,14:36:28
fastboot usb
vol up
vol down
power
fastboot
recovery
factory reset
clear storage
simlock
image crc
power down
im in need of a thourough stepo by step instruction on how to fix this thing i dont care if its by means of a custom rom stock rom whatevers easiest. i know how to utilize fastboot with instruction and ive changed back and forth between cwm and twrp but no matter how many tuts i follow i always end up in a loop and im not sure why again i apologize for being such a noob but ive come to realize that this forum is the best at fixing stupid problems like mine fairly quickly
thanks in advance for your help....
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Edit: Also, I'm assuming you have no knowledge of adb and fastboot commands? Because you might need to learn. And did you try this ruu? It's for your firmware version. http://forum.xda-developers.com/showthread.php?t=1814217
RollTribe said:
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Click to expand...
Click to collapse
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
frankthebunny said:
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
Click to expand...
Click to collapse
frankthebunny said:
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
Click to expand...
Click to collapse
Alright, so I'm assuming the problem is there is no ROM on the phone or someone did factory reset in bootloader. So if the ruu helps, great (it should). If not, then I'm sure we'll figure it out.
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
frankthebunny said:
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
Click to expand...
Click to collapse
Yup. Since you're on an older hboot there's no preparation needed. I'm assuming you don't really want to get into all this rooting stuff and just want a working phone? If you want help with rooting, come back here when the ruu is done, but if you like it stock, then you should be good to go :beer:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
actually i would like to root it after i get it all fixed and put a custom rom on it and what not. like i said earlier i can follow instructions this was just a difficult spot to start from ya know.
twistedddx said:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
right on ill do that. is there anything else i should be downloding now to prepare for what ever it is i need to do to protect my phone from messing up again?
exad said:
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
Click to expand...
Click to collapse
yeah it is an at&t phone. at least it says on the top of it however im using straight talk t-mobile i believe.
will i need to root it again in order to utilize the t-mobile carrier?
No need to root for your carrier.
But you will need to root again to install other roms.
So is this phone back up and running again yet?
Sent from my HTC One XL using xda app-developers app
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
frankthebunny said:
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
Click to expand...
Click to collapse
What ruu?
Did you relock the bootloader?
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
heres the name of the file
htc_one_x_RUU_2.20.502.7_att_us_08022012
frankthebunny said:
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
Click to expand...
Click to collapse
First do :
fastboot oem readcid and tell me what it says
if it's CWS__001 then do:
fastboot oem lock
And chill, your phone will work when I'm done with you.
it say
cid: 11111111
frankthebunny said:
it say
cid: 11111111
Click to expand...
Click to collapse
ok hopefully since it didn't say CWS__001 you didn't use the lock command.
do:
fastboot oem writecid CWS__001 (be sure to note there are two "_")
then do
fastboot oem readcid
It should now say CWS__001
please confirm
nice ok ive changed it now to CWS__001
Hello everyone,
I am in trouble but not sure if I bricked my HTC One X AT&T hboot 1.09 or not
Here is what happened:
I had Android 4.0.3 running and rooted with bootloader unlocked.
S-ON for sure.
Yesterday I tried to install custom rom or I thought if anything wrong goes bad I would upgrade it to the latest
4.2.2 from HTC.
with some commands from the fastboot I believe I distressed the entire system to the point where it cannot boot.
the only thing my device is doing now is just booting to the screen where HTC in green and the red text beneath it or I can go to the
bootloader menu.
I tried to fix this by flashing openrecovery-twrp-2.4.1.0-evita.img
it worked, and I was able to push several ROMs but non of them got installed, I kept getting error status 7.
I wiped everything from the recovery and then locked the bootleader and now I am really really stuck.
just the bootloader is showing.
One last experiment I tried to do, I put my device into fastboot and run the RUU for one of the ROM I downloaded for my device
but I only see a black screen with HTC logo and it kept me waiting more than half hour, I knew this will not work but I thought I would try.
Is my device done and I should through it away or there is a hope of fixing it?
I had this device for more than 2 years so no way AT&T would help, that's my guess.
Please guys, any suggestion? I am all for fixing it.
It was a stupid mistake ahhhh.
Thanks in advance.
Wrong forum mate, this is for the international hox quad-core version. You have to be in the at&t HTC one XL forum.
Mr Hofs said:
Wrong forum mate, this is for the international hox quad-core version. You have to be in the at&t HTC one XL forum.
Click to expand...
Click to collapse
Sorry, is there anyway someone can move this thread to the appropriate forum.
I apologize.
I will report this one to get it moved. Good luck in the correct section
Moved to: AT&T, Rogers HTC One X, Telstra One XL > One X Q&A, Help & Troubleshooting.
(mod team)
Looks like you've possibly made several mistakes there. First problem is you've been lurking in the wrong forum, which means you've probably been trying to flash ROMs that aren't for our device. Our device forum is here:
http://forum.xda-developers.com/forumdisplay.php?f=1538
Bookmark that page and make sure you stay within our forum. Flashing ROMs/kernels/radios that aren't intended for our device can very easily result in a bricked phone.
I think your phone is fine as long as you can get it into the bootloader. Your problem when you were flashing ROMs is that TWRP 2.4.x and 2.5.x are buggy and are basically useless. This is probably a blessing in disguise if you were attempting to flash the wrong ROM, it probably saved your ass. Download at least TWRP 2.6 from here and you should be able to flash with no problems, just make sure they're actually our Evita ROMs that you're flashing.
Now, just to make sure this doesn't happen again, what were the commands you issued through fastboot that "distressed" your system? I need to know what you were doing that caused your device to falter. Also, don't ever run a jb RUU while you're s-on or you'll definitely brick your phone, doing that (SuperCID + s-on + jb RUU) has a 100% kill rate.
As a piece of advice, I'd suggest you stop "experiencing" with your device because the experiments you've been conducting could have easily bricked your phone on several occasions. You're extremely lucky. It seems to me that you need to do some research about our device and what you can and can't do with it. A good place to start would be my Evita FAQ and How-To Guide For Beginners threads in my signature, and build from there.
Sent from my Evita
You are not bricked. With this phone, as long as the screen comes on, you are almost certainly not bricked. You just don't know how to recover.
shakash3obd said:
with some commands from the fastboot I believe I distressed the entire system to the point where it cannot boot.
Click to expand...
Click to collapse
What the heck does "some commands" mean? You need to be specific about the exact steps you took. If you don't know the commands you tried, that is a problem, as it implies you are not being careful while modding the phone.
shakash3obd said:
I tried to fix this by flashing openrecovery-twrp-2.4.1.0-evita.img
it worked, and I was able to push several ROMs but non of them got installed, I kept getting error status 7.
Click to expand...
Click to collapse
That is a very outdated version of TWRP, and probably part of your problem. Use an up to date version.
shakash3obd said:
One last experiment I tried to do, I put my device into fastboot and run the RUU for one of the ROM I downloaded for my device
but I only see a black screen with HTC logo and it kept me waiting more than half hour, I knew this will not work but I thought I would try.
Click to expand...
Click to collapse
You can't (and shouldn't) just run any RUU. You should run the proper RUU for your carrier version (AT&T) and with s-on it has to be equal or later then the hboot version on the phone. Also do not run a Jellybean RUU on the phone, since SuperCID + S-on will brick the device on most Jellybean RUUs. You're okay if the screen is coming on, but don't run any RUUs unless somewhere here specifically instructs you to.
You have a couple options to proceed:
1) Re-unlock the bootloader, install an updated TWRP version, and try flashing a custom ROM.
2) If still on hboot 1.09, try running the 1.73 or 1.85 RUU (do you remember what build number you were on when you unlocked the bootloader?).
shakash3obd said:
I had this device for more than 2 years so no way AT&T would help, that's my guess.
Click to expand...
Click to collapse
AT&T warranties phones for 1 year. So you are out of the warranty period, if that is what you are wondering about. And warranty covers manufacturing defects, not damage done by the owner due to their negligence.
Besides, you don't need a repair or replacement. You just need to know how to recover properly from what you have done.
timmaaa said:
Download at least TWRP 2.6 from here and you should be able to flash with no problems, just make sure they're actually our Evita ROMs that you're flashing.
...
Now, just to make sure this doesn't happen again, what were the commands you issued through fastboot that "distressed" your system?
....
Click to expand...
Click to collapse
Thanks for stopping by,
I believe that I cannot flash any recovery mod such as clockwork or TWRP now, because as I explained. I locked the bootloader again.
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
I didn't mean 'distressed' I was trying to say I destroyed, spilling correction mistake.
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me :crying:
redpoint73 said:
That is a very outdated version of TWRP, and probably part of your problem. Use an up to date version.
You have a couple options to proceed:
1) Re-unlock the bootloader, install an updated TWRP version, and try flashing a custom ROM.
2) If still on hboot 1.09, try running the 1.73 or 1.85 RUU (do you remember what build number you were on when you unlocked the bootloader?).
Click to expand...
Click to collapse
Thanks for your comments.
I put the command I used in the previous reply.
As far as the version of TWRP, I originally tried the latest one, but it wont flash at at that's why I tried an older version.
Again in my previous reply i said that I am not able to Re-unlock the bootloader.
Yes I am still in hboot 1.09 but don't remember the build number unfortunately.
Because all what I am in is because of my lack of knowledge of custom roms, would you be able to
point me to where I can download 1.73 or 1.85 RUU?
Also, Do you think I will be able to run RUU even from the bootloader menu. I tried to run RUU from the bootloader and it got stock in the
black screen with HTC logo forever!!
shakash3obd said:
Thanks for stopping by,
I believe that I cannot flash any recovery mod such as clockwork or TWRP now, because as I explained. I locked the bootloader again.
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
I didn't mean 'distressed' I was trying to say I destroyed, spilling correction mistake.
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me :crying:
Click to expand...
Click to collapse
I won't judge you, I'm here to try and help you. Go to htcdev and try unlocking the bootloader again from scratch, hopefully that'll work. If not, I'm really not sure what you can do. In future, just be careful and make sure know exactly what you're doing before you do it. Fastboot commands have very specific functions and should only be used in specific situations, issuing random commands is a bad idea. I you're unsure about anything or if you have any question at all please feel free to ask here or in my q&a thread.
Sent from my Evita
timmaaa said:
Go to htcdev and try unlocking the bootloader again from scratch, hopefully that'll work.
Sent from my Evita
Click to expand...
Click to collapse
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
shakash3obd said:
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
Click to expand...
Click to collapse
That message suggests that you haven't copied the identifier token correctly. You need to make sure you copy the whole thing, including all of the arrows at the beginning and end.
Sent from my Evita
shakash3obd said:
I just did that and I got the following message from htcdev website
Unlocking Bootloader Instructions
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
So, that's another route that will lead to no fix
Thanks again
Click to expand...
Click to collapse
That error message simply means you cut and pasted the token incorrectly (included an extra character or characters that you were not supposed to). Follow the instruction very carefully and exactly for what exactly needs to be cut and pasted.
---------- Post added at 03:43 PM ---------- Previous post was at 03:37 PM ----------
shakash3obd said:
would you be able to
point me to where I can download 1.73 or 1.85 RUU?
Click to expand...
Click to collapse
All you will mostly likely ever need for this device is in my Index thread:
http://forum.xda-developers.com/showthread.php?t=1671237
shakash3obd said:
Also, Do you think I will be able to run RUU even from the bootloader menu. I tried to run RUU from the bootloader and it got stock in the
black screen with HTC logo forever!!
Click to expand...
Click to collapse
RUU is meant as a recovery tool, and therefore is intended to work while the phone is in almost any condition (as long as the screen comes on), including bootloader.
The reason the RUU did not work, is likely because it was the wrong RUU.
---------- Post added at 03:54 PM ---------- Previous post was at 03:43 PM ----------
shakash3obd said:
I attempted to unlock it using the htcdev unlock bin file that they sent me but in the terminal I got the message
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.148s
that's why I am stock in the bootloader.
Click to expand...
Click to collapse
The bootloader unlock is a bit finicky, and its known to fail for some folks for no good reason (even if you did it all correct), possibly even numerous times. I would suggest just making sure you do the steps correctly and keep trying.
shakash3obd said:
to be honest with you, there were 10's of fastboot commands that I tried some are related to s-off even.
but I think what killed the system is this
fastboot flash file.img
and the file was extracted from a ROM
CARBON-KK-NIGHTLY-20140319-1133-endeavoru
I now realize it's wrong. Please do not judge me
Click to expand...
Click to collapse
The only judgement I have of you, is that you seem to be rushing forward a bit too much, and not researching properly.
Fastboot (and phone modding in general) is not a place to be experimenting. You should not be trying fastboot commands haphazardly. I've seen more than a few devices on this forum bricked with a couple careless fastboot commands. I would recommend you not running any fastboot commands, unless you have obtained them from one of the established guides on this forum, or from a reputable/knowledgeable contributor on this forum.
redpoint73 said:
All you will mostly likely ever need for this device is in my Index thread:
http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Hey guys, I got my device unlocked, i think I copied an extra character.
Now I have an unlocked bootloader + recovery mod 2.6.0.
What should I do next?
should I download RUU from your thread or should should I do something else?
I
I am waiting right here right now until my phone is fixed.
Thank you so much guys
EDIT:
I tried to download RUU 1.73 and the links were down
so i downloaded 1.85 for now.
Waiting for your other instructions. Sir.
shakash3obd said:
Hey guys, I got my device unlocked, i think I copied an extra character.
Now I have an unlocked bootloader + recovery mod 2.6.0.
What should I do next?
should I download RUU from your thread or should should I do something else?
Click to expand...
Click to collapse
Download a custom ROM, move it to your phone, and flash it.
If a custom ROM is what you wanted to begin with, no reason to go backward and RUU (since you were able to get the bootloader unlocked again, and custom recovery installed).
redpoint73 said:
Download a custom ROM, move it to your phone, and flash it.
If a custom ROM is what you wanted to begin with, no reason to go backward and RUU (since you were able to get the bootloader unlocked again, and custom recovery installed).
Click to expand...
Click to collapse
This is actually my original intention, I don't want to have all the junk that comes from HTC and the one from AT&T.
Any recommendation to get something like the kitkat rom that is stable and reliable.
I am asking for recommendation because after all trouble I went through last night, I just want to get my phone to something very nice and stable other than the RUU with HTC and AT&T stuff.
Really appreciate your help.
shakash3obd said:
Any recommendation to get something like the kitkat rom that is stable and reliable.
I am asking for recommendation because after all trouble I went through last night, I just want to get my phone to something very nice and stable other than the RUU with HTC and AT&T stuff.
Click to expand...
Click to collapse
Best/recommended/favorite ROM discussions are not allowed on XDA. They are each good in their own way, and everyone has different preferences. Part of the fun of flashing custom ROMs is trying them out, to see what you like the best.
Try any of the ROMs on my Index thread, and you won't need to worry about a brick. But read through the specific ROM thread as some ROMs have specific flashing procedures.
Bear in mind that KitKat means you will be on an AOSP ROM. Sense is limited to Jellybean, for now.
---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------
shakash3obd said:
Thank you so much guys
Click to expand...
Click to collapse
Feel free to click the "Thanks" button for any posts that you found helpful.
redpoint73 said:
Best/recommended/favorite ROM discussions are not allowed on XDA.
Try any of the ROMs on my Index thread, and you won't need to worry about a brick. But read through the specific ROM thread as some ROMs have specific flashing procedures.
Bear in mind that KitKat means you will be on an AOSP ROM
.
Click to expand...
Click to collapse
I will check the index of yours when I find it since I am always lost in the xda forum.
Sorry to ask for something not allowed in XDA, I will start looking for AOSP ROM since I want something like KitKat.
If we can forget about "recommendation/best ROM" will anyone can point me to where to find KitKat like ROM for my device or
give a list of names or links to threads in XDA. Or even the whole forum starting point for which i can find these type of ROMs
just to avoid bricking my device since it's S-On
redpoint73 said:
RUU is meant as a recovery tool, and therefore is intended to work while the phone is in almost any condition (as long as the screen comes on), including bootloader.
The reason the RUU did not work, is likely because it was the wrong RUU.
Click to expand...
Click to collapse
What I was afraid of is happening, I run RUU 1.85 and I am right now passed 50 minute with the phone screen is black with HTC logo on it.
is this normal?
should I be doing anything? or just wait more or unplug the phone from the PC?