Htc One Problem - One (M7) Q&A, Help & Troubleshooting

Hi everyone,
Im kind of new to the android world and stupid for me i did things without being absolutely certain. So i have an unlocked originally Rogers Htc one and i had it under the google play edition rom with cwm recovery installed, unlocked bootloader and all that good stuff. I needed to send it in for warranty purposes so i wanted to try to put it back to stock sense 5 rom. i followed tons upon tons of videos and i ended finding an RUU that might have worked so i relocked my bootloader and followed the processes but every time i did typed the "fastboot flash zip firmware.zip" command it would go 75% of the way and then stop but in the command window it said successful. Unlocked my bootloader again but i forgot that it wipes everything so now i dont even know if i have cwm installed to flash any rom at all. So basically i think my phone is bricked :'( im crying my head off. If anyone has any input on how i can convert this htc one back to stock and working or even any custom rom just so it can work please let me know im really scared at this point.
when i typed in fastboot getvar all i got this
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.631.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34GW901697
(bootloader) imei: 354439053152296
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3760mV
(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.064s
again any help with these will be greatly appreciated

You've tried to flash a firmware, not a ruu
However, you're on 1.44 hboot, you can use the revone tool for put your phone in s-off.
With the s-off you can port your phone like a stock phone (the same of when you bought it).
Now, for use the revone, you need a rom.
For install a rom, go to fastboot, reflash the CWM or the TWRP.
After, go to advanced and press: adb sideload, and, from a prompt of your pc, do this command:
Code:
adb sideload name_of_rom.zip
(you should have the rom into the adb folder).
Now the recovery will flash the rom, and you can use the revone for acheive the s-off.
When you've the s-off, you can restore a nandroid backup and relock the bootloader with the text (locked).
Or, you can change CID and MID for unbrand your phone and flash all ruu you want.
p.s. I will advice you to remove the imei and the serial number of your phone

+1 on the S-Off part, do it while you still can.
If you flash a new firmware (has to be signed of course since you're s-on), it will update your hboot to 1.54/1.55 and then you won't get a chance to get s-off.
Personally, I think that's the first thing to do. And this in turn will allow you a lot of possibilities to return fully to stock; otherwise your bootloader will always say "RELOCKED" and "TAMPERED", as opposed to just LOCKED.
IMHO

Related

[Q] No Rom and RUU not working

My terminology will probably be off or just plain wrong. Sorry but I am doing my best to give as much info as possible and appreciate the help.
I have a Sprint HTC One (US). I recently tried to put a new rom on my phone and messed up somewhere along the way. I think I wiped where I was loading the rom from :silly:. I now have no rom installed and my computer is not able to connect to or see the phone. When I try and use adb and run the "detect devices" command it comes back with nothing. So then I tried running the RUU for my phone and in versions 1.29.651.10, 1.29.615.7, and 1.29.615.6 I have received error code 155 in all of them. I read that means I need the boot loader to be locked but cannot find a way to do that if the adb is not detecting my phone.
I am able to get into TWRP v2.6.1.0. If I do not hold down the volume down key while trying to boot it will sit on the HTC logo screen.
At the top of the boot loader I have:
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0626
OpenDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013, 17:19:22:15705
I just want to be able to put the stock rom back on the phone. Any help?
Checkered Spheres said:
My terminology will probably be off or just plain wrong. Sorry but I am doing my best to give as much info as possible and appreciate the help.
I have a Sprint HTC One (US). I recently tried to put a new rom on my phone and messed up somewhere along the way. I think I wiped where I was loading the rom from :silly:. I now have no rom installed and my computer is not able to connect to or see the phone. When I try and use adb and run the "detect devices" command it comes back with nothing. So then I tried running the RUU for my phone and in versions 1.29.651.10, 1.29.615.7, and 1.29.615.6 I have received error code 155 in all of them. I read that means I need the boot loader to be locked but cannot find a way to do that if the adb is not detecting my phone.
I am able to get into TWRP v2.6.1.0. If I do not hold down the volume down key while trying to boot it will sit on the HTC logo screen.
At the top of the boot loader I have:
***TAMPERED***
***UNLOCKED***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-1.00.20.0626
OpenDSP-v31.120.274.0617
eMMC-boot
Jul 5 2013, 17:19:22:15705
I just want to be able to put the stock rom back on the phone. Any help?
Click to expand...
Click to collapse
Make sure the rom you tried to flash was sprint compatible. Might be your issue. Boot your phone in bootloader mode, select fastboot then connect usb cable to computer. Open a cmd prompt from your adb/fastboot folder and type this command:
Code:
fastboot getvar all
copy/paste output here but remove IMEI and SN
also ADB only works when phone is booted to OS or RECOVERY
FASTBOOT works when phone is in bootloader mode.
so the command to relock the bootloader is
Code:
fastboot oem lock
don't lock the bootloader yet, want to be sure if the ruu match your getvar info.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4030mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 5.564s
Checkered Spheres said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4030mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 5.564s
Click to expand...
Click to collapse
You need s-off to use these ruu because its a version downgrade (from 1.31.651.2 ----> 1.29.651.7)
So you need to s-off with revone tool before using ruu. don't forget you have a sprint version and you can't use some stuff here. You must make sure you always download srpint compatible rom and recovery (M7_WLS)
alray said:
You need s-off to use these ruu because its a version downgrade (from 1.31.651.2 ----> 1.29.651.7)
So you need to s-off with revone tool before using ruu. don't forget you have a sprint version and you can't use some stuff here. You must make sure you always download srpint compatible rom and recovery (M7_WLS)
Click to expand...
Click to collapse
So what would the order of operations be? Relock boot loader, s-off, then ruu?
Is there any problem that when I type "adb devices" it returns with nothing? I know it was able to pull the info for the getvar but am unsure how that is possible.
Checkered Spheres said:
So what would the order of operations be? Relock boot loader, s-off, then ruu?
Is there any problem that when I type "adb devices" it returns with nothing? I know it was able to pull the info for the getvar but am unsure how that is possible.
Click to expand...
Click to collapse
don't relock bootloader! Flash a sprint compatible rom, then s-off with revone. when you have s-off, remove tempered flag from bootloader and set it to ''locked'' not ''relocked'' and then flash the ruu.
btw adb commands like ''adb devices'' will only work when OS is booted or in custom recovery, not in bootloader.

[Q] Bootloop after RUU attempt (completely stuck!)

I recently tried to revert back from CM 10 to stock on my HTC one.
Everything seemed to be going fine, I found what I believed to be the right RUU(I couldnt find it in a .exe, only .zip) .
And I successfully used revone to get s-off, remove tampered and change unlocked to locked in the bootloader.
But when changing s-off back to s-on the security warning banner showed up in the bootloader and for some reason I couldn’t get into the OS anymore, it just went straight to the bootloader. I didn’t bother thinking about it since I was going to install the RUU either way. But I get the same error every time I try to install it: FAILED (remote: 12 signature verify fail). Also I couldn’t get into recovery, it just shot be back straight into the bootloader.(Correct me if i'm wrong but did the ruu.zip fail because you have to have s-off for it to work? Would make sense.) On top of that I couldn’t just get s-off again because for some reason i can only use adb commands when the phone is in the actual OS, it doesn't seem recognize it when its in bootloader/fastboot/recovery, fastboot commands work fine tho.
I was able to unlock the bootloader again using htcdev and I can now access twrp, but I can't seem to be able to factory reset, it just says: Unable to mount /data and unable to mount internal storage. The mount option in twrp does not seem to work either, trying to check data makes nothing happen. Also instead of it just launching to the bootloader directly on startup, it now gets stuck in a bootloop until you make it go into the bootloader.
As you can see i'm in quite the pickle and absolutely any help on either getting back to a functional CM or stock would be much appreciated.
The getvar all info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W903347
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4065mV
(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.045s
If any more info is needed just ask
victor_021 said:
I recently tried to revert back from CM 10 to stock on my HTC one.
Everything seemed to be going fine, I found what I believed to be the right RUU(I couldnt find it in a .exe, only .zip) .
And I successfully used revone to get s-off, remove tampered and change unlocked to locked in the bootloader.
But when changing s-off back to s-on the security warning banner showed up in the bootloader and for some reason I couldn’t get into the OS anymore, it just went straight to the bootloader. I didn’t bother thinking about it since I was going to install the RUU either way. But I get the same error every time I try to install it: FAILED (remote: 12 signature verify fail). Also I couldn’t get into recovery, it just shot be back straight into the bootloader.(Correct me if i'm wrong but did the ruu.zip fail because you have to have s-off for it to work? Would make sense.) On top of that I couldn’t just get s-off again because for some reason i can only use adb commands when the phone is in the actual OS, it doesn't seem recognize it when its in bootloader/fastboot/recovery, fastboot commands work fine tho.
I was able to unlock the bootloader again using htcdev and I can now access twrp, but I can't seem to be able to factory reset, it just says: Unable to mount /data and unable to mount internal storage. The mount option in twrp does not seem to work either, trying to check data makes nothing happen. Also instead of it just launching to the bootloader directly on startup, it now gets stuck in a bootloop until you make it go into the bootloader.
As you can see i'm in quite the pickle and absolutely any help on either getting back to a functional CM or stock would be much appreciated.
The getvar all info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W903347
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4065mV
(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.045s
If any more info is needed just ask
Click to expand...
Click to collapse
Where did you get the RUU from? It should work even if S-ON as long as the version of the RUU is the same as or newer than your current version.
EDIT: Did it say it was Encrypted or Decrypted? It needs to have an Encrypted Signature or else you'll get the Remote 12 error.
victor_021 said:
I recently tried to revert back from CM 10 to stock on my HTC one.
Everything seemed to be going fine, I found what I believed to be the right RUU(I couldnt find it in a .exe, only .zip) .
And I successfully used revone to get s-off, remove tampered and change unlocked to locked in the bootloader.
But when changing s-off back to s-on the security warning banner showed up in the bootloader and for some reason I couldn’t get into the OS anymore, it just went straight to the bootloader. I didn’t bother thinking about it since I was going to install the RUU either way. But I get the same error every time I try to install it: FAILED (remote: 12 signature verify fail). Also I couldn’t get into recovery, it just shot be back straight into the bootloader.(Correct me if i'm wrong but did the ruu.zip fail because you have to have s-off for it to work? Would make sense.) On top of that I couldn’t just get s-off again because for some reason i can only use adb commands when the phone is in the actual OS, it doesn't seem recognize it when its in bootloader/fastboot/recovery, fastboot commands work fine tho.
I was able to unlock the bootloader again using htcdev and I can now access twrp, but I can't seem to be able to factory reset, it just says: Unable to mount /data and unable to mount internal storage. The mount option in twrp does not seem to work either, trying to check data makes nothing happen. Also instead of it just launching to the bootloader directly on startup, it now gets stuck in a bootloop until you make it go into the bootloader.
As you can see i'm in quite the pickle and absolutely any help on either getting back to a functional CM or stock would be much appreciated.
The getvar all info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W903347
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4065mV
(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.045s
If any more info is needed just ask
Click to expand...
Click to collapse
Never Go S-ON !!!!
flash this with TWRP
http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
Thanks for the replies but after a few hours of nonstop research i managed to fix the problem. I simply installed CWM because TWRP had totally crapped out on me. From there I just simply sideloaded a Viperone 4.4.2 rom and everything is working fine, don't really feel the need to return to stock anymore. Can't believe how simple that turned out to be, anyway thanks for the replies and hopefully this might help other people in the same situation.
stuck
hlo sir,I m really depressed these days bcz I can't finf ruu for my htc one as it shows
TAMPERED RELOCKED SECURITY WARNING.. my cid is VODAP021 and mied is PN071400 hboot
is 1.54 and os is 2.24.980.3... I tried to flash a guru reset with same cid no. but with slight
difference in os it was 2.24.980.2 and it showed signature verify fail......so plzzzz helpppp
meee....suggest me the perfect ruu
jaspreet4140 said:
hlo sir,I m really depressed these days bcz I can't finf ruu for my htc one as it shows
TAMPERED RELOCKED SECURITY WARNING.. my cid is VODAP021 and mied is PN071400 hboot
is 1.54 and os is 2.24.980.3... I tried to flash a guru reset with same cid no. but with slight
difference in os it was 2.24.980.2 and it showed signature verify fail......so plzzzz helpppp
meee....suggest me the perfect ruu
Click to expand...
Click to collapse
Guru reset is a rom not a ruu, so you must be bootloader unlocked to flash it via custom recovery (twrp 2.6.3.3 preferred)
stuck
@aray ,sir thnx for the quik reply....sir but I m stuck can't unlock bootloader I m s-on plz tell with which ruu I would flash my phone..send link....I would really appreciate that
jaspreet4140 said:
@aray ,sir thnx for the quik reply....sir but I m stuck can't unlock bootloader I m s-on plz tell with which ruu I would flash my phone..send link....I would really appreciate that
Click to expand...
Click to collapse
No need to use ''sir''
You can unlock bootloader, it has nothing to do with being s-on! Get you identifier token then submit it to htcdev. They will instantly send you an e-mail with your unlock_code.bin. Flash it and you'll be unlocked.
Video tutorial here
And there is no RUU for your phone so the guru reset rom is the best option.
Video tutorial to use a guru reset rom here
re
@alray,thx for showing concern n my problem...when I use command 'fastboot oem get_indentifier_token' I get msg of command error.....help
jaspreet4140 said:
@alray,thx for showing concern n my problem...when I use command 'fastboot oem get_indentifier_token' I get msg of command error.....help
Click to expand...
Click to collapse
do you have your htc drivers correctly installed on your computer and the android sdk?
When you go in windows devices manager, do you see you your phone as ''My HTC'' ?
in command prompt when you do ''fastboot devices'' does it reply your phone s/n + fastboot ?
ya I downloaded htc driveres frm xda only...but I don't hve android sdk.....
but on running fastboot devices it shows my phone serial....
stuck
@alray plzz reply me........n help mee
jaspreet4140 said:
ya I downloaded htc driveres frm xda only...but I don't hve android sdk.....
but on running fastboot devices it shows my phone serial....
Click to expand...
Click to collapse
jaspreet4140 said:
@alray plzz reply me........n help mee
Click to expand...
Click to collapse
hlo sir,I m really depressed these days bcz I can't find ruu for my htc one as it shows TAMPERED RELOCKED SECURITY WARNING.. my cid is VODAP021 and mied is PN071400 hboot is 1.54 and os is 2.24.980.3... I tried to flash a guru reset with same cid no. but with slight difference in os it was 2.24.980.2 and it showed signature verify fail......so plzzzz helpppp meee....suggest me the perfect ruus
Click to expand...
Click to collapse
could i ask you to go to your other post: http://forum.xda-developers.com/showpost.php?p=52109146&postcount=41 and remove it. (EDIT and just but "deleted" as text), let's keep it here
you can get the mini-sdk from here: http://www.androidfilehost.com/?fid=23329332407585867
extract it and put the files in a simple folder, maybe something like C:\ADB\
then you need to get bootloader unlocked using HTCdev: http://www.htcdev.com/bootloader/

[Q] Rooting after 5.03.651.3 OTA Update Questions

Sprint HTC ONE
Background:
Just spent the last 15 hours flashing back to 4.06.651.4 stock rom in order to take the new OTA update 5.03.651.3. Somehow I managed to brick my phone to where it would only stay stuck on the green HTC with white background. The only thing that I was able to get to work was booting into the bootloader and play with fastboot commands. I had CWM recovery installed but could never get adb to discover the phone to sideload a rom onto the memory card. I had no backup, and pretty much had everything wiped and formatted on the phone. I went througt installing back and fourth twrp, cwm, and different stock recoveries, and hours of trying different things to no avail. What got my phone back up and going was at some point changing my cid to 11111111(not sure if this did anything for me), flashing 4.06.651.4_firmware.zip, then running Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip (ARUWizard.exe) while in fastboot oem rebootRUU mode. Since then I have installed the 4.06.651.9 OTA and then the 5.03.651.3 OTA which is where I stand at this point.
That being said, here's the state of my phone currently:
No Root
CID: 11111111 ( I don't remember what it should say incase I need to warranty the phone)
S-off
bootloader unlocked (did lock it but found out I didn't have to since I was s-off and since then unlocked)
hboot went from 1.56 to 1.57
___________________________________________
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA35RS900979
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4029mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Now this here are my questions.
Can I gain Root on being on 5.03.651.3?
If I have to reinstall a custom recovery to gain root, would I be able to flash back to the current stock recovery?
Having the new ver. of hboot 1.57, would I be able to downgrade back to 1.56 using the 4.06.651.4_firmware.zip, to flash back to stock 4.06.651.4 if I want to factory reset and unroot, s-on, and lock the bootloader if necessary?
And last of all what should the CID show from factory on the new OTA?
Basically what I want is to have factory everything rooted so I can get rid of the bloatware. Nice and simple that's all.
Much appreciated!!!
Rare5spd said:
Sprint HTC ONE
Background:
Just spent the last 15 hours flashing back to 4.06.651.4 stock rom in order to take the new OTA update 5.03.651.3. Somehow I managed to brick my phone to where it would only stay stuck on the green HTC with white background. The only thing that I was able to get to work was booting into the bootloader and play with fastboot commands. I had CWM recovery installed but could never get adb to discover the phone to sideload a rom onto the memory card. I had no backup, and pretty much had everything wiped and formatted on the phone. I went througt installing back and fourth twrp, cwm, and different stock recoveries, and hours of trying different things to no avail. What got my phone back up and going was at some point changing my cid to 11111111(not sure if this did anything for me), flashing 4.06.651.4_firmware.zip, then running Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip (ARUWizard.exe) while in fastboot oem rebootRUU mode. Since then I have installed the 4.06.651.9 OTA and then the 5.03.651.3 OTA which is where I stand at this point.
That being said, here's the state of my phone currently:
No Root
CID: 11111111 ( I don't remember what it should say incase I need to warranty the phone)
S-off
bootloader unlocked (did lock it but found out I didn't have to since I was s-off and since then unlocked)
hboot went from 1.56 to 1.57
___________________________________________
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA35RS900979
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4029mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Now this here are my questions.
1. Can I gain Root on being on 5.03.651.3?
2. If I have to reinstall a custom recovery to gain root, would I be able to flash back to the current stock recovery?
3. Having the new ver. of hboot 1.57, would I be able to downgrade back to 1.56 using the 4.06.651.4_firmware.zip, to flash back to stock 4.06.651.4 if I want to factory reset and unroot, s-on, and lock the bootloader if necessary?
And last of all what should the CID show from factory on the new OTA?
Basically what I want is to have factory everything rooted so I can get rid of the bloatware. Nice and simple that's all.
Much appreciated!!!
Click to expand...
Click to collapse
Alright, so answering your questions:
1. Yes you can get root being on 5.03.651.3.
2. 99% sure you can't, unless you RUU; but if you RUU you completely lose everything including root.
3. Yeah you can if you're S-OFF.
ROOTING INSTRUCTIONS:
http://download.chainfire.eu/450/SuperSU/UPDATE-SuperSU-v2.00.zip
Try downloading that file and then flashing it in TWRP. I haven't tested this though as the ROM that I'm using is prerooted.
There's a video by fellow member @zedomax that tells you how to do this, although the SuperSU zip in his video is outdated as the video's made in 2013 , so I linked you the latest one above.
EDIT: Oh and the factory CID for the Sprint HTC One is SPCS_001.
Thank you for taking the time to reply to my thread and answering all of my questions. I will try rooting when I get home tonight. Thanks again!!!
Rare5spd said:
Thank you for taking the time to reply to my thread and answering all of my questions. I will try rooting when I get home tonight. Thanks again!!!
Click to expand...
Click to collapse
You could also use these commands if you are S-off
fastboot oem rebootRUU
fastboot flash zip recovery.zip
fastboot reboot
this could flash a recovery since you are S-off and flash back your stock recovery... Make sure you include an android-info.txt file...
In the android-info.txt file include this:
modelid: PN0720000
cidnum: SPCS_001
mainver: 1.29.651.10
hbootpreupdate:3
with that txt file and a recovery be it stock or a custom you can do what you like.
StormyNight said:
Alright, so answering your questions:
1. Yes you can get root being on 5.03.651.3.
2. 99% sure you can't, unless you RUU; but if you RUU you completely lose everything including root.
3. Yeah you can if you're S-OFF.
Click to expand...
Click to collapse
In reference to your answer on #2, Why can't you flash back to current stock recovery?
I'm curious to know because, i'm stocked ROM rooted, TRWP (lastest version), s-On. and i've been updating my firmware OTA.
I download the OTA firmware then flashboot stock recovery, reboot phone and perform the update. Once it's done, i then flashboot custom recovery (TWRP) and flash SuperSU to gain root again. The firmware version I"m on now is 5.03.651.3.
So basically, i'm concerned that i won't be able to flash stock recovery whenever the next firmware update occurs, using the method i've just described.
The Glow said:
In reference to your answer on #2, Why can't you flash back to current stock recovery?
I'm curious to know because, i'm stocked ROM rooted, TRWP (lastest version), s-On. and i've been updating my firmware OTA.
I download the OTA firmware then flashboot stock recovery, reboot phone and perform the update. Once it's done, i then flashboot custom recovery (TWRP) and flash SuperSU to gain root again. The firmware version I"m on now is 5.03.651.3.
So basically, i'm concerned that i won't be able to flash stock recovery whenever the next firmware update occurs, using the method i've just described.
Click to expand...
Click to collapse
Huh, didn't know that. My apologies. By the way, you still be able to do it even when the next firmware update occurs.
Yesterday i tried to update my phone without success
fisrt i tried to install roms but it didnt work
then i tried to update my main version and fail also
then i dont know why i change mi CID number to HTC__001
it started to brick the screen turn gray but i solved it i don´t know how
but i noticed my phone changed to S-ON
i tried many times with many ruus to restore but i can´nt Problems CID and 152 images i locked before doing this
i insert a rom with the same rom 5.03.651.3 success at installing
it started good still the part i have to write language it stayed in HTC logo and then restart
Now im trying to get S-OFF and change my CID to another number but i don´t know wich
and try RUU again but i can not IT gave error and Rumrunner adb didnt find my device
i don´t know what else to do im also 2 days awake :crying:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.03.651.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA358S900105
(bootloader) imei: 99*****************
(bootloader) meid: 99***************
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
PS sorry im not a native english speaker. try to understand me
i can understand english very well
THANX ALL OF YOU

[SOLVED] at&t m7 relocked, s-on, tempered, security warning

To begin with, I'm not a very smart man. Some would call me an idiot. I started clicking things and I'm afraid I screwed up my phone
My AT&T M7 was bootloader unlocked, S-OFF, TWRP installed, Custom ROM (PA), and rooted. I wanted to sell it so I got a SIM Unlock code from AT&T. I went to input the unlock code and it wouldn't work. Apparently you have to be on stock hboot (which I wasn't since I did the google play edition conversion a long time ago) and on a stock ROM (which I also wasn't). So I tried to restore through an RUU.exe and it wouldn't work. RUU.zip didn't work either. So I restored my CID to CWS__001 and that didn't work (I had super CID before). I restored back to stock hboot 1.44 easily. Then I guess I somehow started just clicking random combinations of things inside of HTC One Toolkit and managed to relock my device and s-on so that I could try to restore a stock RUU. I must have done that incorrectly though because now I have no ROM installed, no recovery installed, and I'm S-ON with a message that says "security warning". I'm unable to flash a ROM since I don't have a recovery.
I went to HTC Dev to get an unlock code, which I did, but fastboot bootloader unlock says successful and does nothing. Additionally, I am unable to flash a recovery because I am S-ON.
Help! Any way to get S-OFF trough fastboot only without a ROM installed? Any way to force flash a recovery? Any way to force flash a ROM? Any way to get RUU to not spit out error 158? HELP!!!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4233mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ajr901 said:
To begin with, I'm not a very smart man. Some would call me an idiot. I started clicking things and I'm afraid I screwed up my phone
My AT&T M7 was bootloader unlocked, S-OFF, TWRP installed, Custom ROM (PA), and rooted. I wanted to sell it so I got a SIM Unlock code from AT&T. I went to input the unlock code and it wouldn't work. Apparently you have to be on stock hboot (which I wasn't since I did the google play edition conversion a long time ago) and on a stock ROM (which I also wasn't). So I tried to restore through an RUU.exe and it wouldn't work. RUU.zip didn't work either. So I restored my CID to CWS__001 and that didn't work (I had super CID before). I restored back to stock hboot 1.44 easily. Then I guess I somehow started just clicking random combinations of things inside of HTC One Toolkit and managed to relock my device and s-on so that I could try to restore a stock RUU. I must have done that incorrectly though because now I have no ROM installed, no recovery installed, and I'm S-ON with a message that says "security warning". I'm unable to flash a ROM since I don't have a recovery.
I went to HTC Dev to get an unlock code, which I did, but fastboot bootloader unlock says successful and does nothing. Additionally, I am unable to flash a recovery because I am S-ON.
Help! Any way to get S-OFF trough fastboot only without a ROM installed? Any way to force flash a recovery? Any way to force flash a ROM? Any way to get RUU to not spit out error 158? HELP!!!
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 4233mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
Try a different RUU like this one: http://www.htc1guru.com/dld/ruu_m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3_radio_4a-19-3263-13_10-38j-1157-04_release_334235_signed_2-exe/ In the future, don't use toolkits it is easy to lose track of what is really happening to your phone with them. It is better to stick with the raw commands of fastboot and adb. Use this tool to install them and most sites will give you the appropriate commands to perform the various tasks.
Try a different RUU like this one: http://www.htc1guru.com/dld/ruu_m7_u..._signed_2-exe/ In the future, don't use toolkits it is easy to lose track of what is really happening to your phone with them. It is better to stick with the raw commands of fastboot and adb. Use this tool to install them and most sites will give you the appropriate commands to perform the various tasks.
Click to expand...
Click to collapse
Holy **** you are the man! That worked! How did you know that was going to work?!?!
Thank you soooooo much! I love you. I owe you one.

M7 Sprint m7_wls - firmware/update issue

I'm having some issues with getting the firmware updated on my m7 and hoping someone can help.
I had posted some info in another thread of mine, but the thread is now over a year old so I figured I would start a new one.
First, here is my get-var output
C:\DroidTools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000146505640
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4001mV
(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.094s
Not sure why the get-var didn't finish out (Too many links) ?
Anyways I tried updating the firmware with the latest I could find for the sprint variant, but I received this error.
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware as well and still no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues though.
I was also able to flash a newer twrp recovery without any hiccups.. so not sure what is up.
I am currently running AICP 12.1 but I am getting allot of crashes on random thing, and I suspect my mega-old firmware may be contributing. I also tried the last CyanogenMod that was available (13...?) but I couldn't get data and calls to work.
I also attempted to re-lock the boot-loader and tried flashing the firmware that way, but I received a different error.
"remote 12 signature verify fail"
After that I had to scramble and remember how to unlock the boot-loader again just to get my phone to boot back up lol. I haven't had my unlock file in years so that was fun.
So I'm stuck at 1.44.0000 for now. I'm starting to wonder if i have to find an older firmware first before I can jump to a newer one?
Also slightly confused on the RUU. I am already running custom recovery and custom ROM. Is updating the RUU still necessary?
All feedback and help is welcomed.
Thanks
cloud66 said:
I'm having some issues with getting the firmware updated on my m7 and hoping someone can help.
I had posted some info in another thread of mine, but the thread is now over a year old so I figured I would start a new one.
First, here is my get-var output
C:\DroidTools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000146505640
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4001mV
(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.094s
Not sure why the get-var didn't finish out (Too many links) ?
Anyways I tried updating the firmware with the latest I could find for the sprint variant, but I received this error.
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware as well and still no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues though.
I was also able to flash a newer twrp recovery without any hiccups.. so not sure what is up.
I am currently running AICP 12.1 but I am getting allot of crashes on random thing, and I suspect my mega-old firmware may be contributing. I also tried the last CyanogenMod that was available (13...?) but I couldn't get data and calls to work.
I also attempted to re-lock the boot-loader and tried flashing the firmware that way, but I received a different error.
"remote 12 signature verify fail"
After that I had to scramble and remember how to unlock the boot-loader again just to get my phone to boot back up lol. I haven't had my unlock file in years so that was fun.
So I'm stuck at 1.44.0000 for now. I'm starting to wonder if i have to find an older firmware first before I can jump to a newer one?
Also slightly confused on the RUU. I am already running custom recovery and custom ROM. Is updating the RUU still necessary?
All feedback and help is welcomed.
Thanks
Click to expand...
Click to collapse
The firmware.zip you are trying to flash (the one linked in the other thread) isn't signed so your phone must be s-off. Sorry I should have mentioned that earlier but didn't noticed yours was s-on.
Its actually s-off now, showing "shipped s-on"?
Not sure what that means but the bootloader is definitely unlocked.
cloud66 said:
Its actually s-off now, showing "shipped s-on"?
Not sure what that means but the bootloader is definitely unlocked.
Click to expand...
Click to collapse
bootloader unlocked doesn't mean s-off. If your phone is s-off you should see "PVT SHIP S-OFF" and "Security: OFF" in your fastboot getvar all output
On a S-ON phone you can only flash signed firmware.zip and it must be done with a locked (or re-locked) bootloader
On a S-OFF phone you can flash signed or unsigned firmware.zip and the bootloader status doesn't matters (can be locked, re-locked or unlocked).
The sprint firmware linked in the other thread, the one that you are trying to flash is an unsigned zip so you need s-off first. Otherwise you can try to update the whole phone using the latest sprint RUU from htc's website, not sure it will work on hboot 1.44. Backup important files before trying, the ruu will wipe and update your rom and firmware. Btw you also need to be locked/re-locked to flash a ruu if your phone is s-on.
alray said:
bootloader unlocked doesn't mean s-off. If your phone is s-off you should see "PVT SHIP S-OFF" and "Security: OFF" in your fastboot getvar all output
On a S-ON phone you can only flash signed firmware.zip and it must be done with a locked (or re-locked) bootloader
On a S-OFF phone you can flash signed or unsigned firmware.zip and the bootloader status doesn't matters (can be locked, re-locked or unlocked).
The sprint firmware linked in the other thread, the one that you are trying to flash is an unsigned zip so you need s-off first. Otherwise you can try to update the whole phone using the latest sprint RUU from htc's website, not sure it will work on hboot 1.44. Backup important files before trying, the ruu will wipe and update your rom and firmware. Btw you also need to be locked/re-locked to flash a ruu if your phone is s-on.
Click to expand...
Click to collapse
Can you help me with an M7 that has these details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone won't boot and the version-main is blank. First time I'm handling an M7 since this is a friends and the guides all involve toolkits so kinda lost at the moment. Bootloader is locked
Unlocked the bootloader only to find it has TWRP and no OS
Renosh said:
Can you help me with an M7 that has these details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone won't boot and the version-main is blank. First time I'm handling an M7 since this is a friends and the guides all involve toolkits so kinda lost at the moment. Bootloader is locked
Unlocked the bootloader only to find it has TWRP and no OS
Click to expand...
Click to collapse
You can flash it back to stock rom using a RUU.
The latest version is here: http://dl3.htc.com/application/RUU_...691.655435036.1511537283-936972463.1506975706
Launch the .exe file with the phone in bootloader mode and showing "fastboot usb" in red
If you are not using a Windows PC you can find the .zip version of the same RUU here: https://androidfilehost.com/?fid=24588232905725176
You can flash it using fastboot in ruu mode:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
htc_fastboot reboot
If you prefer to flash a custom rom instead of stock, just make sure to choose one compatible with the Sprint variant (M7WLS). Push it to your phone memory and flash it using the "install" menu from twrp.
If the phone was sim-unlocked (working on other network than Sprint) you might have to sim-unlock again after flashing a RUU.
alray said:
You can flash it back to stock rom using a RUU.
The latest version is here: http://dl3.htc.com/application/RUU_...691.655435036.1511537283-936972463.1506975706
Launch the .exe file with the phone in bootloader mode and showing "fastboot usb" in red
If you are not using a Windows PC you can find the .zip version of the same RUU here: https://androidfilehost.com/?fid=24588232905725176
You can flash it using fastboot in ruu mode:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
htc_fastboot reboot
If you prefer to flash a custom rom instead of stock, just make sure to choose one compatible with the Sprint variant (M7WLS). Push it to your phone memory and flash it using the "install" menu from twrp.
If the phone was sim-unlocked (working on other network than Sprint) you might have to sim-unlock again after flashing a RUU.
Click to expand...
Click to collapse
Thanks I actually already managed to fix it using this thread:
https://forum.xda-developers.com/showthread.php?t=2795856
I used the full firmware but had to install this redistributable file for RUU to work (Windows 10) after locking bootloader:
https://npackd.appspot.com/p/com.microsoft.VisualCPPRedistributable/9.0.21022.8
I'll have to search for sim unlock, crap
alray said:
bootloader unlocked doesn't mean s-off. If your phone is s-off you should see "PVT SHIP S-OFF" and "Security: OFF" in your fastboot getvar all output
On a S-ON phone you can only flash signed firmware.zip and it must be done with a locked (or re-locked) bootloader
On a S-OFF phone you can flash signed or unsigned firmware.zip and the bootloader status doesn't matters (can be locked, re-locked or unlocked).
The sprint firmware linked in the other thread, the one that you are trying to flash is an unsigned zip so you need s-off first. Otherwise you can try to update the whole phone using the latest sprint RUU from htc's website, not sure it will work on hboot 1.44. Backup important files before trying, the ruu will wipe and update your rom and firmware. Btw you also need to be locked/re-locked to flash a ruu if your phone is s-on.
Click to expand...
Click to collapse
Thanks for the info. I'm going to try this sometime this week hopefully.
I've been running AICP 7.1.1 for nearly 3 weeks so far with minor hiccups now and then so i'm slightly hesitant to screw something up again :-/
I will update this as soon as I try a signed RUU from HTC.
Will a signed RUU destroy my recovery as well?
Also do I need to unlock after I flash the RUU?
Steps would be
1. relock bootloader
2. Install signed RUU
3. Relock Bootloader
4. Install TWRP
5. Install Rom
6. ?
Assuming I have these correct and everything works that is.
cloud66 said:
Thanks for the info. I'm going to try this sometime this week hopefully.
I've been running AICP 7.1.1 for nearly 3 weeks so far with minor hiccups now and then so i'm slightly hesitant to screw something up again :-/
I will update this as soon as I try a signed RUU from HTC.
Will a signed RUU destroy my recovery as well?
Also do I need to unlock after I flash the RUU?
Steps would be
1. relock bootloader
2. Install signed RUU
3. Re-unlock Bootloader (use www.htcdev.com/bootloader)
4. Install TWRP
5. Install Rom
6. ?
Assuming I have these correct and everything works that is.
Click to expand...
Click to collapse
Stock recovery will overwrite twrp when flashing a RUU, not really a concern since it will take only a few minutes to reflash twrp. And yes you'll need to re-unlock the bootloader after flashing the ruu, before you can install twrp back to your recovery partition. Steps 1 to 5 above are correct.

Categories

Resources