[Q] Bootloop after RUU attempt (completely stuck!) - One (M7) Q&A, Help & Troubleshooting

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/

Related

[Q] Stuck at bootloader *Security warning* *SOLVED*

Hi
I think I made a huge mistake when relocking my bootloader, used the "fastboot oem relock" command before anything else. I was still on custom ROM (Google edition) When trying to update firmware it wouldnt let me flash it. It gets stuck on the sending image, it doesnt give a error report, it just keeps saying sending without anything happening. I then tried to unlock my bootloader again both with the old token, and also tried to get a new token from HTC Dev. Everytime it gets stuck on the "fastboot flash unlocktoken Unlock_code.bin" command. No error report, it just gets stuck at sending. Tried to leave it for up to 15 minutes without a luck.
I guess it got something do do with the bootloader version not match the recovery? My bootloader i sno locked, so cant get into recovery. I figured out that my only opition is to flash a stock RUU for my phone, but cant find anyone that works. Tried a few of them out there, both the executable desktop version and tried to flash to phone with adb commands. No luck, it just keep getting stuck. Anyone who can point me in the right direction?
This is my details from "fastboot getvar all"
C:\Android\sdk\platform-tools>fastboot getvar all
(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.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34GW902611
(bootloader) imei: 354436055220667
(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: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.057s
Thanks in advance!!
garman76 said:
Hi
I think I made a huge mistake when relocking my bootloader, used the "fastboot oem relock" command before anything else. I was still on custom ROM (Google edition) When trying to update firmware it wouldnt let me flash it. It gets stuck on the sending image, it doesnt give a error report, it just keeps saying sending without anything happening. I then tried to unlock my bootloader again both with the old token, and also tried to get a new token from HTC Dev. Everytime it gets stuck on the "fastboot flash unlocktoken Unlock_code.bin" command. No error report, it just gets stuck at sending. Tried to leave it for up to 15 minutes without a luck.
I guess it got something do do with the bootloader version not match the recovery? My bootloader i sno locked, so cant get into recovery. I figured out that my only opition is to flash a stock RUU for my phone, but cant find anyone that works. Tried a few of them out there, both the executable desktop version and tried to flash to phone with adb commands. No luck, it just keep getting stuck. Anyone who can point me in the right direction?
This is my details from "fastboot getvar all"
C:\Android\sdk\platform-tools>fastboot getvar all
(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.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH34GW902611
(bootloader) imei: 354436055220667
(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: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-f188f379dbbfee373cd551f7bc62b8435
getvar:all FAILED (unknown status code)
finished. total time: 0.057s
Thanks in advance!!
Click to expand...
Click to collapse
does the bootloader say fastboot USB?
if you issue the command fastboot devices do you see the phone?
Unlocking should just work.
If you can't get it unlocked an RUU is your best bet.
gunnyman said:
does the bootloader say fastboot USB?
if you issue the command fastboot devices do you see the phone?
Unlocking should just work.
If you can't get it unlocked an RUU is your best bet.
Click to expand...
Click to collapse
My bootloader says fastboot usb in red. I can use the adb commands, and the device answears to the comands, but it's just keep getting stuck whatever I'm trying to push to the phone. recovery, RUU, unlock token, firmware.. nothing works, and it just freezes..
Need to reset phone with powerbutton for 15 seconds to get bootloader up again.
What RUU image would be my best shot based on my information?
garman76 said:
My bootloader says fastboot usb in red. I can use the adb commands, and the device answears to the comands, but it's just keep getting stuck whatever I'm trying to push to the phone. recovery, RUU, unlock token, firmware.. nothing works, and it just freezes..
Need to reset phone with powerbutton for 15 seconds to get bootloader up again.
What RUU image would be my best shot based on my information?
Click to expand...
Click to collapse
What does the security warning mean? It came when I relocked bootloader...
You get the security warning because you locked the phone while running a custom recovery. Hang on a few minutes and I will find the RUU you need
Edit :
There may not be one for your cid.
Try another cable, usb port, or computer to send the unlock token.
Thank you so very much!!
Found my old laptop running linux. Pushed the unlock token to the phone and there it went.
Unlocked again.
Knew I was missing something basic. Strange thing though, my adb drivers seemed to working fine, and has never given me a problem before.
Thanks a million.
Happy to help.
Now UNLESS you're doing an RUU install there is NO reason to lock the Bootloader.
Leave it alone
gunnyman said:
Happy to help.
Now UNLESS you're doing an RUU install there is NO reason to lock the Bootloader.
Leave it alone
Click to expand...
Click to collapse
No need to update firmware to flash Android Revolution Google edition?
garman76 said:
No need to update firmware to flash Android Revolution Google edition?
Click to expand...
Click to collapse
No and even if you did you'd want S-off and supercid bootloader lock wouldn't matter

[Q] Returning to stock now have S-On and locked with no ROM, HELP!

I am trying to return my phone to stock to send it in for replacement (microphone stopped working). I tried to run the Tmo RUU file a couple of times before I found the tutorial on how to properly do it and I am not sure if that may situation worse.
Somehow I wiped the phone and now and am S-On and its locked (showing as tampered). I cannot get the phone to go into any mode that adb can see, although I can access the phone via fastboot commands. What are my options at this point? Is there a way to load a ROM via fastboot? Is there a way to get S-Off and unlock it so I can try the steps to go back to to 100% stock again or am I screwed?
The phone on Tmobile is currently running Hboot 1.44 if that makes a difference.
PLEASE HELP!!!
Can you get to boatloader?
yes, I am in bootloader mode right now. I just successfully unlocked the bootloader from HTCDev. So now I am unlocked with S-On. I also have TWRP 2.6.3.0 and can access recovery. I also was able to set my CID back to T-MOB010.
It seems like I can do anything i want with fastboot commands, but none in adbd. Is there a way to load a rom from fastboot?
an0ther said:
Can you get to boatloader?
Click to expand...
Click to collapse
Your ruu must match your firmware on your phone. If your firmware is higher than your ruu it won't work. What firmware is the stock tmobile and what is your phone os and cid? You can always soff, change cid to stock, rebootRUU and flash stock ruu then s-on and relock.
I am running 3.17 fw and I am not sure what the RUU fw was, most likely 2.17 or something. I did not realize it would be an issue. So what are my options to get it back to stock?
This is what Getvar all says...
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4T.20.3218.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4255mV
(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: 1.930s
an0ther said:
Your ruu must match your firmware on your phone. If your firmware is higher than your ruu it won't work. What firmware is the stock tmobile and what is your phone os and cid? You can always soff, change cid to stock, rebootRUU and flash stock ruu then s-on and relock.
Click to expand...
Click to collapse
You will have to soff to downgrade firmware on phone. Soff, get stock ruu that matches your cid, rebootRUU and flash stock ruu, s-on, and relock
Can I get S-Off through fastboot? I try and run Revone via HTC One Toolkit and it outputs with error: device not found. I am assuming it is because I cant see it in adb.
an0ther said:
You will have to soff to downgrade firmware on phone. Soff, get stock ruu that matches your cid, rebootRUU and flash stock ruu, s-on, and relock
Click to expand...
Click to collapse
Adb devices , you get nothing? Might need newer adb or try another usb port. Reboot phone and computer. Need adb.
Is adb accessible via the bootloader or recovery? I thought adb only worked when you were booted into a rom. I am completely removing the HTC drivers and installing version 3.0.0.007 to see if it helps with adb.
an0ther said:
Adb devices , you get nothing? Might need newer adb or try another usb port. Reboot phone and computer. Need adb.
Click to expand...
Click to collapse
WiKDMoNKY said:
Is adb accessible via the bootloader or recovery? I thought adb only worked when you were booted into a rom. I am completely removing the HTC drivers and installing version 3.0.0.007 to see if it helps with adb.
Click to expand...
Click to collapse
Adb is accessible from recovery. Try updating HTC drivers and your adb. Sometimes using an USB 3 port causes issues.
Ok, I tried a different computer and now the toolkit is detecting the phone in adb and fastboot, but when I try to push revone it says this adb push revone /data/local/tmp/
failed to copy 'revone' to '/data/local/tmp/': Is a directory
WTF?
I have same problem please help......!!!!
HELLO EVERYONE PLEASE HELP..............
My HTC ONE IS
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
x.xx.666.x - Bell (Canada)
modelid: PN0712000
cidnum: BM___001
I was trying to unroot my device, and i have followed commands as below, i have installed file given at below link
http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One/666/
1) fastboot oem lock
2) fastboot oem rebootRUU
3) fastboot flash zip (firmware).zip
green bar stopped at round about 90% , after waiting 2 minutes i entered
4) fastboot reboot
now phone rebooted but nothing happens only blank screen appears.
i have again unlocked it, i can access bootloader, somehow i have also managed to install recovery,
I HAVE SYSTEM BACKUP IN MY LAPTOP
but i cannot transfer my backup file from laptop to htc one
---------------------------------------
C:\HTCONE>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.666.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34PW904746
(bootloader) imei: 354439053702181
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
--------------------------------------------------
WHAT SHOULD I DO ?? PLEASE HELP
MY PREFRENCE IS TO RESOTRE IT WITH SOTCK FIRMWARE UNROOTED.
Your issue is different than mine, go start your own thread please.
vasa_pratik said:
HELLO EVERYONE PLEASE HELP..............
My HTC ONE IS
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.20.3263.16
x.xx.666.x - Bell (Canada)
modelid: PN0712000
cidnum: BM___001
I was trying to unroot my device, and i have followed commands as below, i have installed file given at below link
http://arhd.onedroid.net/db_mirror/Firmware/index.php?dir=HTC/HTC_One/666/
1) fastboot oem lock
2) fastboot oem rebootRUU
3) fastboot flash zip (firmware).zip
green bar stopped at round about 90% , after waiting 2 minutes i entered
4) fastboot reboot
now phone rebooted but nothing happens only blank screen appears.
i have again unlocked it, i can access bootloader, somehow i have also managed to install recovery,
I HAVE SYSTEM BACKUP IN MY LAPTOP
but i cannot transfer my backup file from laptop to htc one
---------------------------------------
C:\HTCONE>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.666.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34PW904746
(bootloader) imei: 354439053702181
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
--------------------------------------------------
WHAT SHOULD I DO ?? PLEASE HELP
MY PREFRENCE IS TO RESOTRE IT WITH SOTCK FIRMWARE UNROOTED.
Click to expand...
Click to collapse
you have a tmobile htc one? Me too. I had the same error but was able to get S-OFF by following this guide: http://rootzwiki.com/topic/96098-s-offdowngrade-12753111-to-1275318
If that doesn't work I would
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
boot in to recovery
Wipe -> format all data -> Yes
go back to the main menu and go to advanced then ADB sideload. Swipe to start adb sideload
on pc type adb sideload romname.zip I'd use a stock rom since they don't normally use aroma
adb sideload will automatically install the rom and reboot
now that your phone is functioning normally gain s-off using revone like usual.
try downgrading again.
I followed your steps, but I get a failed on installation of the sideload on the phone.
blu9987 said:
I would
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
boot in to recovery
Wipe -> format all data -> Yes
go back to the main menu and go to advanced then ADB sideload. Swipe to start adb sideload
on pc type adb sideload romname.zip I'd use a stock rom since they don't normally use aroma
adb sideload will automatically install the rom and reboot
now that your phone is functioning normally gain s-off using revone like usual.
try downgrading again.
p.s. you have a tmobile htc one? Me too. I had the same error but was able to get S-OFF by following this guide, which would probably let you skip everything I posted above: http://rootzwiki.com/topic/96098-s-offdowngrade-12753111-to-1275318
Click to expand...
Click to collapse
If you reboot recovery the zip will still be there labeled sideload.zip if you want to try to install it again manually.
or you could try the modified ruu in the link. It worked for me but be advised in general RUUs can be dangerous.
edit: that guide says to be on the android homescreen, i've been able to run RUUs from the locked bootloader screen just fine.
Downloading...
blu9987 said:
If you reboot recovery the zip will still be there labeled sideload.zip if you want to try to install it again manually.
or you could try the modified ruu in the link. It worked for me but be advised in general RUUs can be dangerous.
edit: that guide says to be on the android homescreen, i've been able to run RUUs from the locked bootloader screen just fine.
Click to expand...
Click to collapse
I got ARHD 22 to load via sideload (had to boot back into recovery and install form the sideload.zip). The rom boots and works as it should. Now when I try and relock the bootloader to run the RUU downgrader you linked me to revone is giving me revone failed (error code = 1).
adb push revone /data/local/tmp/
3279 KB/s (648208 bytes in 0.193s)
adb shell chmod 755 /data/local/tmp/revone
adb shell /data/local/tmp/./revone -P
revone v0.2.1
revone failed (error code = 1)
Any ideas?
blu9987 said:
If you reboot recovery the zip will still be there labeled sideload.zip if you want to try to install it again manually.
or you could try the modified ruu in the link. It worked for me but be advised in general RUUs can be dangerous.
edit: that guide says to be on the android homescreen, i've been able to run RUUs from the locked bootloader screen just fine.
Click to expand...
Click to collapse
to relock the bootloader you do fastboot oem lock from the bootloader screen, then you run the ruu i linked if you still want to use revone to get s-off.
When I run fastboot OEM lock it shows as re-locked and something about security at the top of the bootloader screen. Will flashing the ruu fix all that?
blu9987 said:
to relock the bootloader you do fastboot oem lock from the bootloader screen, then you run the ruu i linked if you still want to use revone to get s-off.
Click to expand...
Click to collapse
Sent from my Nexus 7 using Tapatalk 4

Htc One Problem

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

[Q] Unroot help please

I need help unrooting my HTC one please. When I first go the phone I needed to transfer game data over from my previous phone and the only way to do it was by rooting. I followed a guide and it worked but I have since left it and not updated the phone in any way. I am about to get a new phone and want to remove the root as I will be giving it to a family member.
I have had a look around on google but all the guides seem very complicated and I do not understand what I am doing.
When I hold down the power / volume down it goes into a screen that says hboot 1.44 s-on . When I go into recovery its says cwm-based recovery v6.0.2.8.
I tried flashing a a 4.4.4 onto it following a guide but I got an error message. Ideally I would like to remove the root but if it was easier I would also put a new rom on it. Any help would be appreciated.
jon12355 said:
I need help unrooting my HTC one please. When I first go the phone I needed to transfer game data over from my previous phone and the only way to do it was by rooting. I followed a guide and it worked but I have since left it and not updated the phone in any way. I am about to get a new phone and want to remove the root as I will be giving it to a family member.
I have had a look around on google but all the guides seem very complicated and I do not understand what I am doing.
When I hold down the power / volume down it goes into a screen that says hboot 1.44 s-on . When I go into recovery its says cwm-based recovery v6.0.2.8.
I tried flashing a a 4.4.4 onto it following a guide but I got an error message. Ideally I would like to remove the root but if it was easier I would also put a new rom on it. Any help would be appreciated.
Click to expand...
Click to collapse
what phone do you have
post the results for fastboot getvar all minus the serial no. and IMEI
clsA said:
what phone do you have
post the results for fastboot getvar all minus the serial no. and IMEI
Click to expand...
Click to collapse
Phone is a HTC One
Code:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3916mV
(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.043s
C:\Android>
jon12355 said:
Phone is a HTC One
Code:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3916mV
(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.043s
C:\Android>
Click to expand...
Click to collapse
If you want to just return to stock just relock the bootloader
fastboot oem lock
and flash this RUU >> http://www.htc1guru.com/dld/ruu_m7_..._10-27-1127-01_release_308001_signed_2_4-exe/
If you plan on keeping and using the phone you should consider getting s-off while your still on hboot 1.44
Rumrunner should do the trick
I did the fastboot oem lock, downloaded the file from your link but during the process it said "Error [155]: unknown error"
jon12355 said:
I did the fastboot oem lock, downloaded the file from your link but during the process it said "Error [155]: unknown error"
Click to expand...
Click to collapse
You need the 1.28.401.7 ruu, not the 1.20.401.1.
correct ruu is here: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
When the first link didn't work I assumed from my current software that I needed to download the 1.28.401.7. However after running this it did start showing a percentage bar and a green bar on the phone but I still got an error. The phone is stuck on the htc screen with four triangles in each corner.
Nevermind, I ran it again and it worked. Thank you for all your help
alray said:
You need the 1.28.401.7 ruu, not the 1.20.401.1.
correct ruu is here: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
Click to expand...
Click to collapse
Yeah his version-main: was blank so i took a wild guess and missed
jon12355 said:
Nevermind, I ran it again and it worked. Thank you for all your help
Click to expand...
Click to collapse
I'm glad you got it sorted ...you should still try to s-off before taking any further updates
clsA said:
Yeah his version-main: was blank so i took a wild guess and missed
I'm glad you got it sorted ...you should still try to s-off before taking any further updates
Click to expand...
Click to collapse
1.20.401.1 is hboot 1.43 and is not update-able with ota. I only know this info because of nkk71's guide. Only thing this ruu version is causing is more trouble lol, it should be removed from crushalot's website imo... unless you have s-off and you want to be stuck with hboot 1.43 and 1.20 forever, this ruu is useless.

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