Related
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!
Ok, so somehow I've managed to screw this phone up royally. Any help would be greatly appreciated.
I just switched to Android from iPhone and I think I tried too much too fast.
I successfully followed the guide to convert my AT&T HTC One to a Google Play Edition. I got S-OFF and changed the CID to GOOGL001 and successfully got 4.4 up and running.
I'd been using that for a few months and decided I wanted to try the HTC Sense Stock Software 4.3 (being new to android I just kind of wanted to try it myself in addition to stock android) I've been through a ton of steps and attempts now that I won't bore you with, but here's where I'm at now:
I'm stuck in a bootloop. My phone will load to welcome and ask for a language and then reboots about 2 seconds later.
I can successfully get into fastboot and run commands against the device. If I flash a recovery, it seems to work for one or two boots and then it will crash and restart until I flash it again (tried with TWRP and CWM)
I am currently Tampered Unlocked but can perform fastboot oem lock and unlock. I have S-ON, HBOOT 1.54 and Radio 4T.
My goal is to go back to stock for this device with 4.3 and Sense, but since I stupidly did S-ON before I changed the CID I'm not able to run the RUU exe and since my phone is in a bootloop I don't know how to get root access to run rumrunner to S-OFF.
I've been researching and trying stuff for several days now with no luck and this forum seems to have the best advice of most that I've seen. Can anyone help? Thanks so much for your time!
I had a similar experience in which I completely removed android OS from the phone If u flash the HTC with TWRP and you are able to successfully enter the recovery... TWRP has under advance button and option called adb sideload.
basically download the Google edition that successfully ran your device and place it under the adb.exe folder.
Steps
On the phone
Access recoverty TWRP
go to advance
Click on adb sideload
Swipe to activate adb sideload
Connect phone to computer.
On computer
Go to run and enter cmd press enter
go to the folder where you have the adb.exe
and the command that you enter is adb sideload «filename.zip» press enter and let it work
Sent from my HTC One using xda app-developers app
TopoX84 said:
I had a similar experience in which I completely removed android OS from the phone If u flash the HTC with TWRP and you are able to successfully enter the recovery... TWRP has under advance button and option called adb sideload.
basically download the Google edition that successfully ran your device and place it under the adb.exe folder.
Steps
On the phone
Access recoverty TWRP
go to advance
Click on adb sideload
Swipe to activate adb sideload
Connect phone to computer.
On computer
Go to run and enter cmd press enter
go to the folder where you have the adb.exe
and the command that you enter is adb sideload «filename.zip» press enter and let it work
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply and info! Ok, took your advice and flashed TWRP 2.6.3.3 to recovery. (I can only boot to recovery when I'm unlocked, not sure if that matters or not)
I'm trying to send RUU-HTC_One_GE-4.4.2-3.62.1700.1.zip (Is that the correct file I should be using)
The sideload gets to 100% but then instantly fails when it tries to run on the device:
ADB Sideload Complete
Failed
Updating partition details...
E: Unable to mount '/cache
E: Unable to mount '/cache
E: Unable to mount '/cache
Starting ADB sideload feature...
Cancelling ADB sideload...
Starting ADB sideload feature
Installing '/data/media/0/sideload.zip...
Checking for MD5 file...
Skipping Md5 check: no MD5 file found.
I've tried a few different versions with similar results (same file pre rooted) and same thing happens.
Any thoughts on what I could be doing wrong (because I'm sure that it's me that's the problem here. )
Give this a try... At the bottom of the op thread it says if adb sideload fails....
http://forum.xda-developers.com/showthread.php?t=2318497
If the link above didn't work you might want to try pushing the Rom to the phone via adb push...
See link below.
http://forum.xda-developers.com/showpost.php?p=43674827&postcount=5
Sent from my HTC One using xda app-developers app
I'm able to push the zip file ok, but when I try to do "install zip" it fails again. I get error flashing zip Updating Partition Detials
Is there anyway for me to achieve s-off from where I am now? If I change my CID back to the AT&T HTC one and then relock and s-on I would be able to use the stock ruu exe, correct?
I would look for a stock Rom GPE since you changed the CID and your s-on
I would look for a 4.3 or 4.4 stock Rom... Make sure also that TWRP is the latest . And try again both steps above. if that doesn't work my inclination would be to flash the Rom via fastboot.
try using this ROM, when i had the issues with my HTC i used it to sideload or push and it worked flawlessly.
http://forum.xda-developers.com/showthread.php?t=2460035
CtrlAltDave said:
Is there anyway for me to achieve s-off from where I am now? If I change my CID back to the AT&T HTC one and then relock and s-on I would be able to use the stock ruu exe, correct?
Click to expand...
Click to collapse
You are correct to what you said unfortunately the only way for you to perform a s-off based on the information given is using rumrunner in which you need your device to boot completely to the OS
Sent from my HTC One using xda app-developers app
no reason to post one after other where i can edit using the computer
Thanks for all of your help and patience with me. I think this phone hates me. I get error flashing with every zip I throw at the phone. I get error flashing zip in TWRP and Installation aborted with CWM. Tried with 4.3 and 4.4 stock GPE rom. Same results if I sideload or push. I also get an error when i try to fastboot flash the same roms. 99 unknown fail when bootloader unlocked and 12 signature verify fail if bootloader locked. Both of these are using fastboot oem rebootRUU and then fastboot flash zip rom.zip.
I pasted my getvar all below thinking that might help. I noticed my version-main is blank as well. Could that be causing any problems?
C:\Users\dfarrar\Desktop>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:
(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: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm beyond frustrated at this point because I've spent so much time trying to get this working and I'm at a loss. That's what I get for messing around before I learned enough I guess. Thanks again for helping me out. I owe you!
here is mine...
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*******
(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: 3756mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
the problem as i see it might be the cidnum and modelid, if you get a rom with both config it might be able to flash
CtrlAltDave said:
Thanks for all of your help and patience with me. I think this phone hates me. I get error flashing with every zip I throw at the phone. I get error flashing zip in TWRP and Installation aborted with CWM. Tried with 4.3 and 4.4 stock GPE rom. Same results if I sideload or push. I also get an error when i try to fastboot flash the same roms. 99 unknown fail when bootloader unlocked and 12 signature verify fail if bootloader locked. Both of these are using fastboot oem rebootRUU and then fastboot flash zip rom.zip.
I pasted my getvar all below thinking that might help. I noticed my version-main is blank as well. Could that be causing any problems?
C:\Users\dfarrar\Desktop>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:
(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: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
I'm beyond frustrated at this point because I've spent so much time trying to get this working and I'm at a loss. That's what I get for messing around before I learned enough I guess. Thanks again for helping me out. I owe you!
Click to expand...
Click to collapse
try this rom out .... RUU-HTC_One_GE-2.14.1700.15
http://forum.xda-developers.com/showthread.php?t=2358781&page=112
http://forum.xda-developers.com/showthread.php?t=2570785&page=3
Same errors with that rom. Won't work through adb push with twrm or cwm. Won't work with sideload and won't work fastboot flash zip. Could I have permanently broken this thing?
CtrlAltDave said:
Same errors with that rom. Won't work through adb push with twrm or cwm. Won't work with sideload and won't work fastboot flash zip. Could I have permanently broken this thing?
Click to expand...
Click to collapse
no it's not broken ...
Flash this stock recovery and also change your CID back to AT&T
fastboot oem writecid CWS__001
then
http://d-h.st/2Lr
fastboot flash recovery recovery_signed.img
Next boot into stock recovery / factory reset
this is done from the bootloader using the volume up/down to navigate and Power button to select. After you choose recovery you have to push vol up and power to see the factory reset option.
When it's done reflash TWRP recovery and try and sideload a new Rom
I recommend >> Download - ARHD 31.6
Would he be able to change back to the AT&T cod having s-on??? As far as I know you can only change with s-on only when you have supercid in place
Sent from my HTC One using xda app-developers app
TopoX84 said:
Would he be able to change back to the AT&T cod having s-on??? As far as I know you can only change with s-on only when you have supercid in place
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
yeah your right he need to get back s-off also after he gets ARHD 31.6 running
ARHD did the trick! For some reason none of the stock GPE roms would load but this one worked flawlessly. I was able to sideload and install, get supersu and then use rumrunner to get back to s-off. Plus this rom gives me everything that I wanted. I can keep kitkat and still get sense and zoe and whatnot. Never mind going back to stock, I think I'll stick with this for a while and try it out. Thanks so much for your help everyone!
To be in the safe side you might want to consider changing the cid to supercid...
Sent from my HTC One using xda app-developers app
CtrlAltDave said:
ARHD did the trick! For some reason none of the stock GPE roms would load but this one worked flawlessly. I was able to sideload and install, get supersu and then use rumrunner to get back to s-off. Plus this rom gives me everything that I wanted. I can keep kitkat and still get sense and zoe and whatnot. Never mind going back to stock, I think I'll stick with this for a while and try it out. Thanks so much for your help everyone!
Click to expand...
Click to collapse
Good to here it all worked out for you
and remember STAY S-OFF
SuperCID and S-Off for life. Thanks again!
Thanks All
Don't know if any of you will check back on this ancient post, but I read around for a long time and this totally ended up working for me. So belated thanks.
okay,
I've unlocked the bootloader, rooted it, it's s-on and installed cm11. After less than a day, I've decided to go back to stock. Unfortunately, because cm11 is kitkat 4.4 it seems I can't even use an ruu, as they'll only go to 4.3 (which it seems i can't use because with s-on, I can't downgrade firmwares).
I've used Twrp 2.6.3.3 for recovery.
i've tried to use moonshine and rum runner, but they both fail, presumably because i've got cm11 installed. Also, when I connect to the pc, it only comes up as a media player or camera (depending on the settings in cyanogenmod), I've got debugging on and i believe everything else I should have.
In device manager, it calls itself "My HTC", yet in utorrent "HTC Aria"
When running (in cmd) "adb devices" it shows my phone, but when I do "fastboot devices" nothing comes up.
i've tried installing htc drivers, but nothing seems to change it. Some have mentioned forcing drivers but I don't know where to get the specific htc one driver.
in the bootloader this is what comes up:
hboot 1.44
m7ul pvt ship s-on rh
radio 4A.12.3750.20
open dsp v31.120.274.0617
eMMC-boot
what are my next steps/options?
damiancds said:
okay,
I've unlocked the bootloader, rooted it, it's s-on and installed cm11. After less than a day, I've decided to go back to stock. Unfortunately, because cm11 is kitkat 4.4 it seems I can't even use an ruu, as they'll only go to 4.3 (which it seems i can't use because with s-on, I can't downgrade firmwares).
I've used Twrp 2.6.3.3 for recovery.
i've tried to use moonshine and rum runner, but they both fail, presumably because i've got cm11 installed. Also, when I connect to the pc, it only comes up as a media player or camera (depending on the settings in cyanogenmod), I've got debugging on and i believe everything else I should have.
In device manager, it calls itself "My HTC", yet in utorrent "HTC Aria"
When running (in cmd) "adb devices" it shows my phone, but when I do "fastboot devices" nothing comes up.
i've tried installing htc drivers, but nothing seems to change it. Some have mentioned forcing drivers but I don't know where to get the specific htc one driver.
in the bootloader this is what comes up:
hboot 1.44
m7ul pvt ship s-on rh
radio 4A.12.3750.20
open dsp v31.120.274.0617
eMMC-boot
what are my next steps/options?
Click to expand...
Click to collapse
cm 11 did'nt update your firmware
what's your results for fastboot getvar all
run it from the bootloader screen / fastboot usb (remove your serial no and iemi)
all it says is "< waiting for device >"
this leads me to believe there's a driver error?
Sorry, I'm an idiot
C:\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(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: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.056s
damiancds said:
all it says is "< waiting for device >"
this leads me to believe there's a driver error?
Sorry, I'm an idiot
C:\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-ON
(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: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.056s
Click to expand...
Click to collapse
this is the last AT&T RUU it will update you to android 4.3 >>
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
if that link is slow you can get it directly from HTC here >>
http://www.htc.com/us/support/htc-one-att/news/
you'll have to relock your bootloader
fastboot oem lock
then run the RUU with your phone sitting at the fastboot usb screen
Worked beautifully. Thank You.
there's only two niggling things. when you pull down for your notifications, in the top right used to be settings, now it's quick tiles like cm11.
Also, in my computer, the device shows up as portable media player, where it used to just show up as htc one and an icon that looked like it. (from quick reading, it seems this is normal.)
Thanks again for all your help
damiancds said:
Worked beautifully. Thank You.
there's only two niggling things. when you pull down for your notifications, in the top right used to be settings, now it's quick tiles like cm11.
Also, in my computer, the device shows up as portable media player, where it used to just show up as htc one and an icon that looked like it. (from quick reading, it seems this is normal.)
Thanks again for all your help
Click to expand...
Click to collapse
yeah welcome to android 4.3 .. it's different, wait till you get sense 5.5 in the kitkat update
clsA said:
yeah welcome to android 4.3 .. it's different, wait till you get sense 5.5 in the kitkat update
Click to expand...
Click to collapse
I know now, a rough search turned up the same....
One last question,
I'm sticking with stock, but i want to root it, everything i've done has been unsuccessful, where before first time and it was done, I was reading the guide over here, http://forum.xda-developers.com/showthread.php?t=2273376&page=2 , and it mentions that I can't root a stock rom? that means I would need to grab one of the rooted ones then, correct? I know I've seen a link to them around here, but can't seem to find it, let alone which one I should use.
damiancds said:
I know now, a rough search turned up the same....
One last question,
I'm sticking with stock, but i want to root it, everything i've done has been unsuccessful, where before first time and it was done, I was reading the guide over here, http://forum.xda-developers.com/showthread.php?t=2273376&page=2 , and it mentions that I can't root a stock rom? that means I would need to grab one of the rooted ones then, correct? I know I've seen a link to them around here, but can't seem to find it, let alone which one I should use.
Click to expand...
Click to collapse
after running the RUU your starting from scratch
1.unlock bootloader at HTCDEV.com
2. Flash custom recovery I recommend TWRP 2.6.3.3
How to flash?
1) Download your recovery
2) Put it on your adb/fastboot folder
3) Rename it to recovery.img
4) Open a CMD/Teminal windows on adb folder
5) Put your phone in fastboot
6) Flash the recovery with the command:
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
3. flash custom rom 3.17.502.3 Stock Rooted
That should do it if your Root needs updated
download and flash this same as a rom
http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
i'd installed cm11 via installer but now i wanna go back to sense
i'd installed cm11 via cm installer but now i wanna go back to stock sense,sadly i couldnt find the suitable RUU for my device.Since im really new to this android system i dont have any ideas bout flashing or locking the devices,could u guys please help me out?
i'd tried turning S off with rumrunner but at the end i was struck on an error.
here are my devices details.
m7_U S on
Hboot 1.56
CID : htc__038
version : 4.20.707.7
THANKS.
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(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: 3909mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
bzowk said:
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(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: 3909mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
Click to expand...
Click to collapse
The Guru Reset would put you back at stock if you so choose. You are given the option in Aroma to "root", chose that option since you are going on to flash ViperOne.
The Guru Reset should have the same firmware in Aroma check that you want the stock radio this will help in ViperOne. I believe the issue you had earlier was the result of incompatible firmware/radio.
Purple haze issue is more likely hardware, but there has been a lot of pseudo fixes.
Thanks for your reply! Just finished backup so starting on it now. Wish me luck!
OK - Already have a small question...
I started the Guru flash and went through the first couple of screens. On the "What to flash," it gives me the option to perform "Stock Recovery" and/or "Radio." I wanted to flash Radio due to my errors - but - on this screen it describes Radio as "Version 4M.27.3218.14 - Original Radio from the Stock ROM."
My phone, however, had the Radio listed as "4A.19.3263.13." Is this still ok or no? The Guru Flash I'm using is "Guru_Reset_M7_5.12.502.2_clsA"
I plan to stay at this screen for a few minutes so that hopefully I'll have a reply by then.
Thanks Again!
bzowk said:
OK - Already have a small question...
I started the Guru flash and went through the first couple of screens. On the "What to flash," it gives me the option to perform "Stock Recovery" and/or "Radio." I wanted to flash Radio due to my errors - but - on this screen it describes Radio as "Version 4M.27.3218.14 - Original Radio from the Stock ROM."
My phone, however, had the Radio listed as "4A.19.3263.13." Is this still ok or no? The Guru Flash I'm using is "Guru_Reset_M7_5.12.502.2_clsA"
I plan to stay at this screen for a few minutes so that hopefully I'll have a reply by then.
Thanks Again!
Click to expand...
Click to collapse
The radio (4A) is the older radio the newer version is 4M. Like I mentioned before you want to the new radio to try to solve your communication issues. Sorry for the late reply but I don't monitor this site.
majmoz said:
The radio (4A) is the older radio the newer version is 4M. Like I mentioned before you want to the new radio to try to solve your communication issues. Sorry for the late reply but I don't monitor this site.
Click to expand...
Click to collapse
Hey - I toitally understand. I just appreciate that you replied when you did. After reading your message, I had an idea. Perhaps the Phone app wouldn't open because the Radio was on such an old build. I went ahead and downloaded the newest compatible radio I could find - 4T.24.3218.09 from here. I booted to Recovery then applied the radio alone.
After reboot, it worked! I can now get into my Phone app! Since I've already set this build up, I think I'll leave it for now.
I learned a lot about radios today - Thanks again for your help!
bzowk said:
Hey - I toitally understand. I just appreciate that you replied when you did. After reading your message, I had an idea. Perhaps the Phone app wouldn't open because the Radio was on such an old build. I went ahead and downloaded the newest compatible radio I could find - 4T.24.3218.09 from here. I booted to Recovery then applied the radio alone.
After reboot, it worked! I can now get into my Phone app! Since I've already set this build up, I think I'll leave it for now.
I learned a lot about radios today - Thanks again for your help!
Click to expand...
Click to collapse
You are welcome, glad that you are back up and running! :good:
bzowk said:
Hey Guys -
After being an iPhone fanboy for a while, i wanted a change so got an HTC One (M7 - AT&T) a few months ago. Since then, I've tried a couple of ROMS and liked ViperONE the best. Recently, I decided to completely redo my phone because:
- I had too much crap on my phone
- A new major ROM version (7) was released
- My signal strength seemed to be ~30% lower than usual at work and home - didn't know why
In hopes that the result would be the updated ROM with all other files/folders from the emulated SD gone, I downloaded the RUU I thought matched and applied it. Once done, I applied the new ViperONE 7.0 ROM for HTCOne then proceeded to root and get all apps installed and configured.
The next day, i found out that when I launched the phone app, it immediately quit. ARGH! I also can't receive calls. I wouldn't think this would be a ROM issue as the phone app would hopefully be the first thing they test. Therefore I am deciding to stick with the same ROM team since I like it so much.
So... this time around, I did a bit more research and am posting before doing anything to make sure I'm doing everything correctly or with the best chance of success. Below are details about my phone as well as the plan I currently have...
Phone Specifications via Recovery Menu + FastBoot Command
- Below specs noted before I had issues -
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-CWS__001
HBOOT-1.55.0000
RADIO-4A.19.3263.13
OpenDSP-v31.120.274.0617
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT*********
(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: 3909mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Proposed Steps to Fix / Re-flash
1. Back up everything on phone (done)
2. Download following: (done)
- Newest TWRP img
- Guru Reset 5.12.502.2
- Stock Firmware stock firmware 5.12.502.2 (Just in case)
- Newest ViperONE (7.0.1) ROM for M7
3. Copy Guru Reset 5.12.502.2 to phone's root and install via TWRP in Recovery
I've never used Guru Reset before so don't know what state the phone will be in afterwards. If prompted to keep my root, should I or should I really go ahead and start all over? Depending on what the result is after that, I'd then re-root if need be then go back into recovery and flash ViperONE ROM.
Is that a good plan? If there's anything else you think may be a good idea to also add in or try (especially anything that may have a chance of fixing the radio) would be great - Thanks!
PS: I've seen online that I'm not the only one who has a "purple haze" on my M7's camera. While doing all the above, any suggestions for how any fix may be applied or is it a hardware issue? Thanks!
Click to expand...
Click to collapse
Theirs one big Flaw in your method DO NOT SKIP from 3.x firmware to 5.x firmware .. you'll end up in QHSUSB_DLOAD mode and that's No fun at all.
The correct way to get to the 5.x firmware is
3.x.502 RUU to 4.x.502 Firmware to 5.x.502 firmware
then the Guru reset
Hello all,
I've been browsing the forums for a few days now trying to fix my issue, but nothing I have found seems to be of much help, so I have decided to register here myself and get some assistance directly.
So, I rooted my phone and flashed twrp and cyanogenmod. After several bugs and overall irritation, I have decided to just go back to stock recovery, ROM, etc. (After all, I am a mechanical engineer - software is not my forté.)
In attempting to unroot my device, however, it seems that I just messed things up even further.
Steps taken:
1) Rebooted device into fastboot
2) fastboot oem lock
3) Reboot into RUU mode (black screen w/ htc logo)
4) Ran RUU.exe
5) (bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 35.173s
At this point, I thought that maybe it was because I was still S-ON so I was going to place rumrunner on the virtual SD. Now my PC won't recognize my phone, so I don't know how to flash rumrunner to go to S-OFF or if that's even the correct next step. So basically, I have bootloader and twrp, and that's it.
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35ZW915640
(bootloader) imei: 354439051027912
(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: 3658mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
Ok so I got into twrp to try and flash any ROM but data wouldn't mount.
I wiped data through twrp, which allowed me to mount data
From here I could have copied a ROM to my virtual SD and flashed through twrp, but decided to give the RUU a try again.
This time I got ERROR [155].
Checked to make sure I had the right RUU for my CID, which I do, but I'm going to try an older RUU instead.
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
MJGiuffre said:
Ok so I got into twrp to try and flash any ROM but data wouldn't mount.
I wiped data through twrp, which allowed me to mount data
From here I could have copied a ROM to my virtual SD and flashed through twrp, but decided to give the RUU a try again.
This time I got ERROR [155].
Checked to make sure I had the right RUU for my CID, which I do, but I'm going to try an older RUU instead.
Click to expand...
Click to collapse
wrong way
MJGiuffre said:
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
Click to expand...
Click to collapse
there is no ruu for your sofware, older one will not work its just how htc are made, try this ruu its the latest.( make sure you are not supercid before running it, it can mess up the phone) from your first post it looks like you are fine unless u changed it to supercid.
http://dl3.htc.com/application/RUU_...06_10.46.1718.01L_release_424933_signed_2.exe
it should work at least it worked on mine
---------- Post added at 03:07 PM ---------- Previous post was at 03:00 PM ----------
MJGiuffre said:
Since RUU wasn't working, I decided just to place the CM ROM onto the virtual SD and flash it. Finally have a phone that boots up and is running CM. Better than a paper weight, but still not a stock HTC One...
Click to expand...
Click to collapse
also u can try one of the guru resets that matches your software , or look for a stock unrooted nandroid for att htc one , u need the 5,12 sofware , older one may not work properly. also before runing a ruu make sure your bootloader is loked or relocked. good luck.