Hi guys,
I just wanted to write this post to help anybody who lost imei number because I've lost too.. Thanks for helpskotag82
If you lost your imei number (after root, unlock or something else) this means your efs directory has failed. Maybe removed (my efs was removed). In this situation, follow with these steps:
Relock your bootloader (Look this thread: http://forum.xda-developers.com/showthread.php?t=1994961)
Enter bootloader and connect with computer with a cable (Also you can enter with using toolkit that given first step)
Choose and download RUU for your mobile (You can download from this link: http://htcruu.com/?dir=ENRC2B )
Install RUU by following Instal Shiled's steps
And then your mobile is back!
NOT:You will lose your data so if you can, backup them. Your device get back to first situation (factory building).
Thanks.
dmrc1143 said:
Hi guys,
I just wanted to write this post to help anybody who lost imei number because I've lost too.. Thanks for helpskotag82
If you lost your imei number (after root, unlock or something else) this means your efs directory has failed. Maybe removed (my efs was removed). In this situation, follow with these steps:
Relock your bootloader (Look this thread: http://forum.xda-developers.com/showthread.php?t=1994961)
Enter bootloader and connect with computer with a cable (Also you can enter with using toolkit that given first step)
Choose and download RUU for your mobile (You can download from this link: http://htcruu.com/?dir=ENRC2B )
Install RUU by following Instal Shiled's steps
And then your mobile is back!
NOT:You will lose your data so if you can, backup them. Your device get back to first situation (factory building).
Thanks.
Click to expand...
Click to collapse
is there a way to back up your imei?
Andrew149 said:
is there a way to back up your imei?
Click to expand...
Click to collapse
Yes. By copying your efs folder, you can move your IMEI to a safe zone (pc, sd card..) or you can back up with some application but I don't know these applications will run HOX+.. I haven't tried before.
HTC one x lost the IMEI and baseband
So I bumped into this thread although I dont have the htc one x+.
I have the HTC one x international model. I lost the baseband and IMEI: possibly corrupted efs folder. I dont have the backup. Do you think these instructions work in my case.
Also I cant seem to access htcruu.com website is there another website where I can download it.
http://androidfiles.org/ruu/
The biggest problem should be to get the newer RUUs, necessary through new firmware...
That site doesnt have RUU for one x. Any other reliable places My CID is 001.
thanks.
if you are able to get the RUU, is it possible to fix the IMEI issue?
spacemango80 said:
That site doesnt have RUU for one x. Any other reliable places My CID is 001.
thanks.
Click to expand...
Click to collapse
It has have look here newest one is 3.14.401.31, it is last one on the list... to be sure you need to post your full CID (HTC__001)
spacemango80 said:
if you are able to get the RUU, is it possible to fix the IMEI issue?
Click to expand...
Click to collapse
OP solved his IMEI problem by flashing RUU
kotag82 said:
It has have look here newest one is 3.14.401.31, it is last one on the list... to be sure you need to post your full CID (HTC__001)
OP solved his IMEI problem by flashing RUU
Click to expand...
Click to collapse
Yes I flashed this ROM but still my IMEI and baseband are unknown.
Cant connect to network..
thanks
one x imei
so i just got my new htc one today and i want to mess around with my one x a bit, i have seen loads of stuff about imei unlock and change and thing but how can i imei unlock to use anywhere in the world?
whats with this change imei? how would that benifit the handset?
New User
dmrc1143 said:
Hi guys,
I just wanted to write this post to help anybody who lost imei number because I've lost too.. Thanks for helpskotag82
If you lost your imei number (after root, unlock or something else) this means your efs directory has failed. Maybe removed (my efs was removed). In this situation, follow with these steps:
Relock your bootloader (Look this thread: http://forum.xda-developers.com/showthread.php?t=1994961)
Enter bootloader and connect with computer with a cable (Also you can enter with using toolkit that given first step)
Choose and download RUU for your mobile (You can download from this link: http://htcruu.com/?dir=ENRC2B )
Install RUU by following Instal Shiled's steps
And then your mobile is back!
NOT:You will lose your data so if you can, backup them. Your device get back to first situation (factory building).
Thanks.
Click to expand...
Click to collapse
Hello i'm a new user for HTC one x + 64G i bought it about a week ago and i found the ROM is customized and the device is unlocked , i would like a help from you or any one in the following :
1- is the ROM for HTC one x plus is the same as HTC one x ? i mean can i install stock rom from htc one X
2- where can i find stock ROM support Arabic Keyboard ?
i've tried to restore factory default but still the same rom as there is no backup .
thanks
7emoo said:
Hello i'm a new user for HTC one x + 64G i bought it about a week ago and i found the ROM is customized and the device is unlocked , i would like a help from you or any one in the following :
1- is the ROM for HTC one x plus is the same as HTC one x ? i mean can i install stock rom from htc one X
2- where can i find stock ROM support Arabic Keyboard ?
i've tried to restore factory default but still the same rom as there is no backup .
thanks
Click to expand...
Click to collapse
Hey,
1.ROM differ from phone to phone, you can't install HTC One X rom to HTC One X +
2.try some keyboards like swift key etc, I am using this as my default settings.
It supports multiple languages
Greetings
Sent from my HTC One X+ using xda premium
got this issue when trying to flash CM10.1... this helped to get me back working again. Need to yet try pushing that CM again...
Having the same issue...
have u solved the problem....
Info:
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.35.0000
(bootloader) version-baseband: 3.1204.168.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.17.401.1
(bootloader) serialno: FAXXXXXXXXXX
(bootloader) imei: 35XXXXXXXXXXXXX
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3761mV
(bootloader) devpower: 37
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
crazy_kamal said:
Having the same issue...
have u solved the problem....
Info:
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.35.0000
(bootloader) version-baseband: 3.1204.168.32
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.17.401.1
(bootloader) serialno: FAXXXXXXXXXX
(bootloader) imei: 35XXXXXXXXXXXXX
(bootloader) product: enrc2b_u
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PM3511000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3761mV
(bootloader) devpower: 37
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
I have the same problem. Until now, nothing (restore of cwm-/twrp-backup, flash the boot.img and so on) worked succesfully to restore the imei. I will be very happy if someone has the one-right-solution for this problem. Thanks in advance....
PS: i have hboot 1.40
thx
Thanks,dude
I get back my lost imei number very fast!!
hey everyone, i have the one x + at&t device running viperxl 1.1.0. hboot is 1.32.0000. i have lost my imei. following the op is to get the hasoon toolkit http://forum.xda-developers.com/showthread.php?t=1994961. unfortunately it looks as though that thread is locked and download links have been removed. is there any other way to lock the bootloader without the toolkit?
I've downloaded the proper ruu but stuck on this bootloader issue. Any advice would be very much appreciated.
Leebert225 said:
hey everyone, i have the one x + at&t device running viperxl 1.1.0. hboot is 1.32.0000. i have lost my imei. following the op is to get the hasoon toolkit http://forum.xda-developers.com/showthread.php?t=1994961. unfortunately it looks as though that thread is locked and download links have been removed. is there any other way to lock the bootloader without the toolkit?
I've downloaded the proper ruu but stuck on this bootloader issue. Any advice would be very much appreciated.
Click to expand...
Click to collapse
Are you s-off or s-on ? S-on carry on reading. s-off - doesn't need relocked bootloader
You should lock boot loader with
fastboot oem lock
That is the reason for hansoon toolkit ... Do it proper old fashion way
Be aware RUU WILL WIPE YOUR SD card
Sent from my HTC One using xda premium
kotag82 said:
Are you s-off or s-on ? S-on carry on reading. s-off - doesn't need relocked bootloader
You should lock boot loader with
fastboot oem lock
That is the reason for hansoon toolkit ... Do it proper old fashion way
Be aware RUU WILL WIPE YOUR SD card
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Thanks, got it fixed!
Related
LOOKS LIKE S-OFF FOR 1.54 HAS HAPPENED. NO NEED TO DOWNGRADE CHECK THE POST HERE
MODS Lock This One Up!!!
I was about to give up on s-off since I got the OTA update but there is hope.
I got s-off doing the following:
1.) Unlock your device via HTCDev
2.) Download and flash CWM Recovery
3.) Flash the stock nandroid for your phone...
a. TWRP Nandroid AT&T Thanks JEANRIVERA
b. TWRP Nandroid AT&T Thanks JEANRIVERA
c. TWRP Nandroid AT&T Thanks cschmittIf any one has other links to other devices let me know... I think this will work on all of the variants.:laugh:
Please note that this nandroid was made with TWRP and may need to be restored with TWRP.
On a side note... The original nandroid that I had linked was also created with TWRP and as I was unable to locate the restore function in my TWRP I did restore with CWM.
4.) then relock your device
Code:
fastboot oem lock
5.) grab 1847-ruu-m7-ul-jb-50-cingular-12650212.exe here and run it... Thanks cschmitt
6.) goto the tutorial here... and follow the directions...
This has worked for me... and I hope this will help someone else. All the information came from other people, I just happened to put it in the right order.
If this did not work for you there are New instructions here... Thanks domohan
IT IS IMPORTANT TO DO ALL THE STEPS IN ORDER...
I take no responsibility for anything you do with this information.
If I forgot to mention your name specifically... I'm Sorry and Thanks!
If I helped you hit the thank you button.
I see, new hboot. Downgrading it is then. Interesting that they haven't forced htc to shut off the unlocking service.
worked as advertised
Thanks a lot. A process for sure but worked for me following the ATT OTA update to .15. Although, I went on to follow the guide at wonderhowto dot com for installing the ASOP Google Edition. Thanks again.
Yeah that was the update that got me ... I am really glad that it worked for someone else... :laugh:
I am having trouble flashing the nandroid. I have tried to both flash the zip as well as unpack it and try to do a restore. Any thoughts?
---------- Post added at 06:33 PM ---------- Previous post was at 05:38 PM ----------
Ok, I actually flashed this one http://forum.xda-developers.com/showthread.php?t=2252959
Then ran the .12 RUU and am now S-OFF. Thanks for this!
well i am glad you got that working... The way i did the nandroid was by extracting the zip to clockworkmod\backups ... then choosing restore... I had TWRP but could not find the restore Nandroid option.
The only way I see this actually working is that the RUU just checks the HBOOT version, and not the build date. Otherwise, the .12 RUU would fail to install because the OTA HBOOT has a newer build date.
If this is true, then all AT&T users better get S-OFF now (if they know what S-OFF does). I have a feeling the 4.2.2 update will come out with a newer HBOOT with a higher number. Then surely, any 4.1.2 RUU will not work.
In any case, it seems to be working for those of us who weren't paying attention and downloaded the OTA... But the message is still S-OFF now while you can, 'cause they will patch the thing eventually.
I was getting Error = -6 codes and this method worked perfectly for me! Thanks so much!
This did not work for my situation...
I had S-OFF, set my CID to 11111111 and installed the latest GE rom. I decided to go back to stock, and made the mistake of S locking without knowing that I could not go back on HBOOT 1.54. Now I'm S-ON with CID 11111111, HBOOT 1.54 and Radio 4A.18
I tried this fix... I get stuck on the RUU, it show sending... but after about 5min it errors out...
Is there any hope for my situation?
This was what in my RUU log...
<T171817><DEBUG><OUT>sending 'zip'... (1029872 KB) FAILED (data transfer failure (Too many links))</OUT>
i used this and it worked flawlessly for me, great looking out man. im now s-off with tampered removed
TabascoJoe said:
This did not work for my situation...
I had S-OFF, set my CID to 11111111 and installed the latest GE rom. I decided to go back to stock, and made the mistake of S locking without knowing that I could not go back on HBOOT 1.54. Now I'm S-ON with CID 11111111, HBOOT 1.54 and Radio 4A.18
I tried this fix... I get stuck on the RUU, it show sending... but after about 5min it errors out...
Is there any hope for my situation?
This was what in my RUU log...
<T171817><DEBUG><OUT>sending 'zip'... (1029872 KB) FAILED (data transfer failure (Too many links))</OUT>
Click to expand...
Click to collapse
I'm not totally sure...
1.) do you have unlock from htcdev?
2.) can you flash a recovery?
a. if so there is hope to get back to at least a working phone till a new exploit for 1.54 is found.
b. Are you sure you re-locked your phone...
Code:
fastboot oem lock
c. SUPER CID - (allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE) So make sure the phone is locked and flash an older RUU. Then revone and you should be good to go my friend.
let me know if this works!
...and remember to hit the thank you button!
INeFFeCTiVE said:
I'm not totally sure...
1.) do you have unlock from htcdev?
2.) can you flash a recovery?
a. if so there is hope to get back to at least a working phone till a new exploit for 1.54 is found.
b. Are you sure you re-locked your phone...
Code:
fastboot oem lock
c. SUPER CID - (allows you to flash ANY ROM to the device regardless of the carrier. Just click RUU.EXE) So make sure the phone is locked and flash an older RUU. Then revone and you should be good to go my friend.
let me know if this works!
...and remember to hit the thank you button!
Click to expand...
Click to collapse
I have a working phone. I have an unlock from htcdev. i have locked it, i can flash roms and recovery in twrp.
Its when I try an RUU it get suck on sending.... and errors out
Could it be my Main Version? I used misc tool to try to get back to 1.26.502.10, but can never get it to write the last digit correctly. Here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.010
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3999mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess I was wrong on being SuperCID. Using the misctool what should I change my main version to, and how?
Thanks
Here are the steps I did to unlock bootloader, root and acquire s-off:
I went back to fully stock unrooted s-on to get the OTA just to b on the safe side. This is where I knew the update screwed up the current s-off method so I unlocked the bootloader using HTCDev. Then proceed to root and pushed the revone file to the appropriate folder location. I followed all the commands from revone up to where u Chmod 755 revone. After that since I already had root, I simply type su then proceeded with the s-off and unlock command. Removed tampered label and voila!!! Back in business with latest software.
Sent from my HTC One using xda premium
---------- Post added at 07:50 PM ---------- Previous post was at 07:48 PM ----------
I think what happened was the new update screwed up the motochopper temp root exploit and that's y I think u can't s-off with the updated software. But there is always a way...
Sent from my HTC One using xda premium
TabascoJoe said:
I have a working phone. I have an unlock from htcdev. i have locked it, i can flash roms and recovery in twrp.
Its when I try an RUU it get suck on sending.... and errors out
Could it be my Main Version? I used misc tool to try to get back to 1.26.502.10, but can never get it to write the last digit correctly. Here is my getvar output:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.010
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3999mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I guess I was wrong on being SuperCID. Using the misctool what should I change my main version to, and how?
Thanks
Click to expand...
Click to collapse
You can't use the AT&T RUU because your HBOOT is higher than the one in the RUU. S-ON is preventing any older HBOOT to be flashed.
Hi guys, will this work on T-Mobile HTC ONE? I updated not knowing they blocked from s-off.
Thanx,
Vinny
It would certainly be worth a try. The hardware is the same, so I don't see why not... as long as your boot loader is 1.44.00000 (not sure on the amount of zero's) this should work.
I'm pretty sure there are nandroid images for TMO out there so give it a try.
vinny.1967 said:
Hi guys, will this work on T-Mobile HTC ONE? I updated not knowing they blocked from s-off.
Thanx,
Vinny
Click to expand...
Click to collapse
let me know if it's work with you
me_rashad said:
let me know if it's work with you
Click to expand...
Click to collapse
Hey me_rashad, it's a no go. I also flash tmobile nand still no go. from what i research on difference forum is because tmobile update did a patch to the 1.44 HBoot so i guess we have to wait till revone or monshine dev find the way.
vinny.1967 said:
Hey me_rashad, it's a no go. I also flash tmobile nand still no go. from what i research on difference forum is because tmobile update did a patch to the 1.44 HBoot so i guess we have to wait till revone or monshine dev find the way.
Click to expand...
Click to collapse
I did get the OTA too and having the same pesky error -6. The bootloader version still says 1.44.0000, how do we know if its patched or not? Shouldn't the version number increase? What is your version?
This is my first thread here on XDA so bare with me guys. I'm going to try to add all the important details to help you help me... yeah. Anyways, on with my problem. I recently converted my AT&T HTC One with sense to a GPE. Back on sense I was on 4.3, made a backup with TWRP and currently have it saved on my computer. Once I was one the google play edition, I updated to 4.4, just in case that matters.
The phone has S-OFF and has an unlocked bootloader. Not Rooted nor does it has a custom recovery.
My question is, how do I go back to HTC Sense ? Can I install a TWRP and drag & drop the backup & restore ? Or will installing a custom recovery brick the phone ?
Bootloader screen details:
***UNLOCKED***
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.58.1700.5
Click to expand...
Click to collapse
The rest doesn't really matter
Can I install A Custom Recovery and drag the backup from TWRP to my phone and restore back to sense ?
Any help is much appreciated ! :good:
Extra Info After Using The Command "fastboot getvar all"
C:\Users\Windows Master\Desktop\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.58.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34YW910578
(bootloader) imei: Rather Not Post
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4336mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.075s
Click to expand...
Click to collapse
Tony Deavila said:
This is my first thread here on XDA so bare with me guys. I'm going to try to add all the important details to help you help me... yeah. Anyways, on with my problem. I recently converted my AT&T HTC One with sense to a GPE. Back on sense I was on 4.3, made a backup with TWRP and currently have it saved on my computer. Once I was one the google play edition, I updated to 4.4, just in case that matters.
The phone has S-OFF and has an unlocked bootloader. Not Rooted nor does it has a custom recovery.
My question is, how do I go back to HTC Sense ? Can I install a TWRP and drag & drop the backup & restore ? Or will installing a custom recovery brick the phone ?
Bootloader screen details:
The rest doesn't really matter
Can I install A Custom Recovery and drag the backup from TWRP to my phone and restore back to sense ?
Any help is much appreciated ! :good:
Extra Info After Using The Command "fastboot getvar all"
Click to expand...
Click to collapse
Installing a custom recovery won't brick your phone. You'll just have to move the TWRP recovery to your internal SD card from your computer, install TWRP then restore from within TWRP. If you wanted the latest Sense version of Android, you could look at flashing ARHD 51.0 running on 4.4.2 instead of going back to 4.3, but that's up to you. Ask if you need anymore information.
Gpe to sense
i bought a google edition htc m8, so i wanted to get it back to sense aswell as i prefer the usability of it + the phone was made to run on that software
this took me hour to work out and hours of research on xda and other websites, so here im trying to simplify everything into one post, so people can get back to sense
so first of course root your phone if u have a google edition, if you converted to GPE from sense you will already be rooted and you can start the process (with TWRP installed)
i did it successfully but it was a huge process as there are limited resources atm to help me do it, as to why i am posting this
1. first i downloaded HTC one m8 all in one toollink)
http://forum.xda-developers.com/showthread.php?t=2699065
once you download this program you will be able to put the phone into bootloader, with this program you wont have to use comand prompt on windows to change the cid in bootloader.
2. you need to change the phones cid from goog to CID-11111111, of the m8 all in one toolkit it enters it in for you and writes it straight to your phone.
3. once you do this you need to download -
Flash 1.54 Image- http://forum.xda-developers.com/show...68&postcount=3
NOW YOU NEED TO USE COMAND PROMPT- TEST PHONE WITH - FASTBOOT DEVICES- SHOULD GET A NUMBER CODE IF YOUR PHONE IS CONNECTED PROPERLY
1.FIRST ENTER fastboot oem rebootRUU
THEN- fastboot flash zip (whatever you name it).zip REDO IT TWICE 1ST WILL FAIL )- THEN SUCCESSFUL
-Boot back into Bootloader
-Boot into Recovery
-then in twrp (MUST)
-Wipe Data, Factory Reset, Advanced Wipe-Wipe System, Data, Cache
-Reboot Recovery
-Restore or Flash a Sense Rom
(i have been pretty brief in my explanation, everything you need is there for the tricky parts, but if you have problems with toolkit or anything else look it up on xda) but this post will cut down the process time!
thanks. i am not resposible for any faults or problems with your phone but if you do it correctly all should be good :good:
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
TopoX84 said:
Please remove serial number and imei from the report.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I did just as you posted this, thanks!
codejunkie83 said:
Hello all, I've been using these forums for information frequently, but this is the first time I've run into trouble. I updated my AT&T HTC One to the GPE, but decided I wanted to go back to stock with the impending HTC Sense 5.5 update around the corner. I had gotten GPE via rumrunner and the methods at htc-one.wonderhowto.com (I can't post the direct link).
I had then reverted back to a rooted stock ROM, but it would not perform OTA updates. So, my next step was to get S-ON and re-lock the device. I accomplished those, but somehow I now have no OS - I can get into recovery (stock), but cannot perform anything from there. Factory resets and wipes do nothing for me. I have access to fastboot, and have attempted running various RUUs but all of them give me error code 155, which appears to be due to the wrong version. However, I have tried all of the AT&T US RUUs I can find, so I'm sort of at a loss there.
I thought maybe I could get unlocked again so that I could load TWRP again, but running the HTCDev unlocktoken command does nothing, other than tell me it was successful - it stays on the fastboot screen instead of showing the option to choose Yes/No to unlock.
So, after hours of attempts, I'm sort of stuck. Could anyone help point me in the right direction? By the way, my device reads TAMPERED and RELOCKED in the bootloader, and S-ON. Below is the output of my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/
or you could try this which is supposed to be the latest version that at&t has gotten out
http://androidromupdate.com/2013/10/09/att-htc-one-official-4-3-ota-update-stock-ruu-3175023/
Sent from my HTC One using xda app-developers app
TopoX84 said:
Did you try ruu ?
RUU M7 UL JB 50 Cingular US 1.26.502.15 Radio 4A.17.3250.20 10.40.1150.04 Release 326691 Signed 2
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
EDIT: I also tried that latest AT&T version from androidromupdate, but it failed the same
codejunkie83 said:
Yes, I tried all of the Cingular ones on that page, to no avail. They all fail with the 155 error code.
Click to expand...
Click to collapse
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Okay, seems like I've followed all of those steps. I ran fastboot oem lock, but each time I try the RUU I get the 155 message. I had just installed the latest HTC drivers last week, as that was when I went to the GPE. I'm using the same USB port that I had been using then, so no differences there.
Thank you for your responses - if you need any more information I'll be glad to give it.
TopoX84 said:
http://androidforums.com/incredible...or-155-using-htc-rom-utility.html#post4767526
http://forum.xda-developers.com/showthread.php?t=2257921
Click to expand...
Click to collapse
Okay, so one thing that I have noticed - my main versions seems to be X.XX.1540.X, which as best I can tell is the US Dev Edition. However, my CID is CWS_001, which should have X.XX.502.X as the main version. Unfortunately, I think the conflict here is causing my RUUs to fail. Any suggestions?
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
codejunkie83 said:
So, after a long night and morning of fighting with this, I've concluded that I'm completely hosed. Here is how I stand at this time:
My CID is correct, CWS__001, which matches my carrier (AT&T)
My OS version, however, is 4.06.1540.2. This marks it as being a developer edition.
There does not exist an RUU for the OS I have currently. Also, if one did exist, I'm not certain that it would work, as that would require my CID to be different (not sure on that last bit)
All AT&T RUUs fail - this is due to low main version.
I do not have access to Android at all, only bootloader and fastboot.
I am S-ON
I am RELOCKED/TAMPERED
Because of these, I cannot flash a custom recovery to be able to load a new system of ANY version.
Because I can only access bootloader, I cannot achieve S-OFF.
And the final nail, HTC Dev unlock feature does not work. It says it is successful, but the splash screen is never displayed, and I receive the message that the splash screen could not load on my next fastboot command (no matter what command it is)
So, from this criteria, I think I'm stuck with an expensive piece of dead technology. I'm posting all of this information in hopes that someone else may get stuck in the same manner and have a miracle cure.
Click to expand...
Click to collapse
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
mb_guy said:
Have you worked through this article??
http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
codejunkie83 said:
I've tried - how would I go about restoring the stock rom/recovery? Just flash the individual images from that zip? Also, would I need to do the X.XX.502.X version (my carrier), or the X.XX.1540.X version (the currently loaded firmware)?
EDIT: No dice. I tried both, but continue to receive the message that the signature verify is failing.
Click to expand...
Click to collapse
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
mb_guy said:
I think your issue may be that you went back to S-on before going to stock and now firmware is wrong. I would follow the article to regain s-off then you can likely move ahead. There are also several articles saying going to s-on after being s-off can cause issues.
Click to expand...
Click to collapse
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
codejunkie83 said:
The problem is that I cannot access my phone's storage to push revone, or to use rumrunner. I cannot unlock the device because unlocktoken does not work - it applies the token, but nothing happens.
I wonder - can I flash the splash screen that it is missing? I think it's due to me missing the piece where it asks me to confirm I want to unlock the phone.
Click to expand...
Click to collapse
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
BTW: have you tried "fastboot oem unlock" again
mb_guy said:
I would try posting here in the main htc one forum
http://forum.xda-developers.com/htc-one/help
Lots of smart guys hang out there.
Click to expand...
Click to collapse
Thanks, will do!
Does anyone know if a fix has been implemented for the failure to unlock of bootloader 1.54 and above yet? I have had a htc one not working for over a month now and no one can seem to help me and it seems many others have the same problem. Can someone either please help or point me in the direction of someone who would be willing to help? I think I may have found a solution myself that just needs a little more work.... Thank you!
bda714 said:
Does anyone know if a fix has been implemented for the failure to unlock of bootloader 1.54 and above yet? I have had a htc one not working for over a month now and no one can seem to help me and it seems many others have the same problem. Can someone either please help or point me in the direction of someone who would be willing to help? I think I may have found a solution myself that just needs a little more work.... Thank you!
Click to expand...
Click to collapse
You got the unlock_code.bin from htcdev? and flashed it with fastboot? ' fastboot flash unlocktoken Unlock_code.bin ' and it didn't work?
If you don't have the unlock_code you may have to revert with an RUU, you can't lock and change kernels and then unlock again with standard commands(edit: if you changed kernels/flashed anything), need that unlock_code.bin if you did so. Thought I screwed myself but re-downloaded the unlock_code.bin and it unlocked no problems regardless..
bda714 said:
Does anyone know if a fix has been implemented for the failure to unlock of bootloader 1.54 and above yet? I have had a htc one not working for over a month now and no one can seem to help me and it seems many others have the same problem. Can someone either please help or point me in the direction of someone who would be willing to help? I think I may have found a solution myself that just needs a little more work.... Thank you!
Click to expand...
Click to collapse
Hello,
I will need more information regarding your device to better assist you:
-HBOOT current version
-Firmware version
-Currently installed ROM, and version
-Carrier
-CID number
-Model ID
Device info
I had previously received the google edition update to 4.4 and I have been told that google implemented some new security which no longer allows users of their rom to unlock through htc dev website. Not sure if it makes a difference but my device is a m7-ul. Is that not supposed to be a developers edition? If I put the flash unlock token in the first time it says flash success but no splash screen no change. if I put the oem unlock command in first it says remote fail. if I put flash unlock token command immediately followed by oem unlock command I get a failure to load custom splash screen error, seems it would work if I hadn't erased the files that contain the custom splash unlock screen right? Is there any way to get those back on the phone even with an otg cable or I have an mini sd card reader that I can plug in to the phone. Will read the sd card in recovery.
anyway here is the getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
bda714 said:
I had previously received the google edition update to 4.4 and I have been told that google implemented some new security which no longer allows users of their rom to unlock through htc dev website. Not sure if it makes a difference but my device is a m7-ul. Is that not supposed to be a developers edition? If I put the flash unlock token in the first time it says flash success but no splash screen no change. if I put the oem unlock command in first it says remote fail. if I put flash unlock token command immediately followed by oem unlock command I get a failure to load custom splash screen error, seems it would work if I hadn't erased the files that contain the custom splash unlock screen right? Is there any way to get those back on the phone even with an otg cable or I have an mini sd card reader that I can plug in to the phone. Will read the sd card in recovery.
anyway here is the getvar all
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
finished. total time: 0.031s
Click to expand...
Click to collapse
1- M7_UL could be any edition not necessarily Dev Edition (which is modelid: PN0712000 and cid: BS_US001)
2- fastboot oem unlock, only works on GPE hboots (and I think only on 1.54)
3- are you on a GPE bootloader (dark one), or the HTC bootloader (white one)?
nkk71 said:
1- M7_UL could be any edition not necessarily Dev Edition (which is modelid: PN0712000 and cid: BS_US001)
2- fastboot oem unlock, only works on GPE hboots (and I think only on 1.54)
3- are you on a GPE bootloader (dark one), or the HTC bootloader (white one)?
Click to expand...
Click to collapse
I was on the dark bootloader when it first happened but on my first post looking for help it was actually yourself and sahlizz who recommended that I flash the dev edition firmware from this link:
~~ORIG POST TEXT: @nkk71, do you think he can flash the Dev edition firmware 4.06.1540.x and unlock the bootloader? CID/MID already matches..
Dev firmware listed here: http://arhd.onedroid.net/db_mirror/F..._One/1540/
RE:
if it is a GPE phone, then maybe (yes long shot), "fastboot oem unlock"
otherwise get a new token and try again.
bda714 said:
I was on the dark bootloader when it first happened but on my first post looking for help it was actually yourself and sahlizz who recommended that I flash the dev edition firmware from this link:
~~ORIG POST TEXT: @nkk71, do you think he can flash the Dev edition firmware 4.06.1540.x and unlock the bootloader? CID/MID already matches..
Dev firmware listed here: http://arhd.onedroid.net/db_mirror/F..._One/1540/
RE:
if it is a GPE phone, then maybe (yes long shot), "fastboot oem unlock"
otherwise get a new token and try again.
Click to expand...
Click to collapse
sorry you got stuck, but I didnt come up with the idea of flashing a Dev Edition firmware on non-dev phone.
Here's what I recommend: is the ATT OTA to 4.x out yet (which matches your MID and CID)? if so go find it, ask for it, or wait for it and post a request for the original OTA file.
once you have your hands on that, extract "firmware.zip" from it and flash your phone back to ATT firmware, then the HTCdev unlock should work.
nkk71 said:
sorry you got stuck, but I didnt come up with the idea of flashing a Dev Edition firmware on non-dev phone.
Here's what I recommend: is the ATT OTA to 4.x out yet (which matches your MID and CID)? if so go find it, ask for it, or wait for it and post a request for the original OTA file.
once you have your hands on that, extract "firmware.zip" from it and flash your phone back to ATT firmware, then the HTCdev unlock should work.
Click to expand...
Click to collapse
I wasn't trying to place blame at all sorry if I implied that. was just trying to explain the chain of events. anyway thank you very much for your help but I am pretty sure that the ota isn't out yet. thanks again and let me know if you find anything else
bda714 said:
I wasn't trying to place blame at all sorry if I implied that. was just trying to explain the chain of events. anyway thank you very much for your help but I am pretty sure that the ota isn't out yet. thanks again and let me know if you find anything else
Click to expand...
Click to collapse
no worries, i am sorry you got stuck though.
Anyway, looks like you're right OTA not available, but shouldn't be too long: http://www.htc.com/us/go/htc-software-updates/
Once it's out, make sure to get your hands on it, good luck
Initially device had following software properties:
- Stock rooted jb rom
- S-off
- TWRP jb recovery
What messed up everything was that I flashed an ICS rom (AOKP) over my JB hboot.
Now phone doesn't boot (remains stuck at HTC logo).
I can acces only fastboot. If I try to acces recovery system remains stuck at HTC logo.
I've tried to reflash recovery (TWRP, Philz Touch, Atti's - all jb recoveries) in fastboot but with no result. It says operation succesful but still cannot acces recovery. I also did fastboot erase cache.
When entering fastboot getvar all I get the following information:
Code:
(bootloader) version-bootloader: 1.25.0002
(bootloader) version-baseband: 1.15.40.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: u�n�g"�a6����
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid:
(bootloader) product: proto
(bootloader) platform: HBOOT-8225
(bootloader) modelid: ���e����(����Q�~���Q��=��/ `oj\
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: HTC
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-02bbe6c44f94272745d8398b32e3f3e4f
getvar:all FAILED (unknown status code)
finished. total time: 0.067s
I would really appreciate it if someone could point me in the right direction to resolve this problem.
Thank you all!
Oops, reread, sorry.
I have no idea why the recovery will not reflash. Sorry for wasting time.
EDIT: I had an idea!
Because you are S-off, your recovery can access way more partions and could have just flashed another incorrect one besides your recovery etc.
Go to the s-off thread, there are a lot of partion images posted. Flash as many as you can find to the right partions and maybe see if that works.
EDIT: Lack of vibrations. Look for which partion causes it.
Hopefully I've been somewhat helpful, though unlikley,
Thanks! I will try it and give feedback.
Sent from my LG-P500 using XDA Free mobile app
That's right. Good idea @CurtisMJ! He should try zu flash radio partition (after backup of course, don't remember the partition number now), because the seven vibrations are caused by radio if I remember right.
Sent from my HTC Desire X using XDA Premium 4 mobile app
dansou901 said:
That's right. Good idea @CurtisMJ! He should try zu flash radio partition (after backup of course, don't remember the partition number now), because the seven vibrations are caused by radio if I remember right.
Sent from my HTC Desire X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have searched the entire rumrunner thread from here http://forum.xda-developers.com/showthread.php?t=2630531.
But I couldn't find any radio partitions or whatsoever. All there is are hboot images which I cannot flash because of my screwed up model id; I get the error
41 Model Id check fail
Click to expand...
Click to collapse
.
Am I looking in the wrong place? Where could I find a radio partition?
Could someone help me out with some block partitions from our device?
How can I check if device has ENG hboot?
Guys...If u are begginer why u complicate everything with S-OFF I never had issue like this.... =] And I dont see need to do S-OFF.
Sent from my HTC Desire X using Tapatalk
mefistoreyon said:
Guys...If u are begginer why u complicate everything with S-OFF I never had issue like this.... =] And I dont see need to do S-OFF.
Sent from my HTC Desire X using Tapatalk
Click to expand...
Click to collapse
You are right. But for me it's too late. Can't manage to do anything now with my softbricked device
Actually I bricked many times my phone ,but without S-OFF.And for that I think Im not able to help
One really stupid qestion.
What If to flash stock recovery+stock boot.img ?...
I will try it.
Sent from my LG-P500 using XDA Free mobile app
hey guys
i brick my phone too with exactly same var but without s-off i'm with s-on and i still can't unbrick it i try 2 stock roms but nothing.. :/ (sorry for my bad english)
This is what happens when someone doesn't read carefully ?
ICS AOKP builds are based on buggy sources and not maintained for years.
Odesláno z mého HTC Desire X pomocí Tapatalk
dfvikicha said:
i brick my phone too with exactly same var but without s-off i'm with s-on and i still can't unbrick it i try 2 stock roms but nothing.. :/ (sorry for my bad english)
Click to expand...
Click to collapse
Maybe u already know but...When u flash stock rom u have to flash too stock boot.img and recovery i think.Anyway if u are with ics hboot u can use RUU
I've sent mine back to service. Waiting to see if they fix it (it's still in waranty but you know...)
My desire x came back from service today. They replaced its motherboard!