Related
Help!
I recently installed the 4.06.1540.3.zip firmware onto my HTC One in preparation to install Android Revolution HD 41. After installing the firmware, I have been unable to unlock the relocked bootloader. I am able to send commands via fastboot and can successfully send the unlock code but nothing shows up on the phone. I currently have no working OS on the phone and only have stock recovery, it seems, and obviously can't send over a custom recovery until I'm unlocked which I can't do =(.
Please help, I have no phone!
Why did you lock it?
Sent from my HTC One using Tapatalk
xcrazydx said:
Why did you lock it?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Mike's directions for updating firmware required a re lock.
How to flash?
(bootloader needs to be relocked)
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Click to expand...
Click to collapse
Whaines said:
Mike's directions for updating firmware required a re lock.
Click to expand...
Click to collapse
If u r s_off ..u dont need to relock bootloader mike clearly stated tht in his post read properly before u even proceed
Sent from my HTC One using xda app-developers app
vaibhav satam said:
If u r s_off ..u dont need to relock bootloader mike clearly stated tht in his post read properly before u even proceed
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yup. I am and was s-on and followed directions. So why can't I unlock again?
Whaines said:
Yup. I am and was s-on and followed directions. So why can't I unlock again?
Click to expand...
Click to collapse
Unlock boot loader using HTC Dev instructions again?
Sent from my HTC One using xda app-developers app
you will need a new unlock bin file from HTC
Jcc1dls said:
you will need a new unlock bin file from HTC
Click to expand...
Click to collapse
Yes, and I've received one (and then kept trying and got about 30 more). I can flash it just fine but the screen on my phone never pops up to accept the unlock. This is my issue. There is no error message on the flash. It just doesn't show up and I can't accept the unlock.
Whaines said:
Yes, and I've received one (and then kept trying and got about 30 more). I can flash it just fine but the screen on my phone never pops up to accept the unlock. This is my issue. There is no error message on the flash. It just doesn't show up and I can't accept the unlock.
Click to expand...
Click to collapse
S-On, right? :crying:
1- was that a signed firmware package
2- did the update go all the way (ie you flashed it twice in a row, first one came back with "flush again immediately" and you did)
3- you confirmed everything was updated by checking your "fastboot getvar all"
4- bootloader also shows the correct firmware
if yes to above, try a factory reset in bootloader and/or stock recovery, then try a new unlock token, and hope it works.
nkk71 said:
S-On, right? :crying:
1- was that a signed firmware package
2- did the update go all the way (ie you flashed it twice in a row, first one came back with "flush again immediately" and you did)
3- you confirmed everything was updated by checking your "fastboot getvar all"
4- bootloader also shows the correct firmware
if yes to above, try a factory reset in bootloader and/or stock recovery, then try a new unlock token, and hope it works.
Click to expand...
Click to collapse
Yes, S-ON since getting S-OFF on hboot 1.5 is a pain.
I'm almost certain it was a signed firmware otherwise it wouldn't have even be able to have been flashed.
The firmware update was successful, after flashing twice. I can successfully flash that firmware and ..1540.2
Getvar shows the new firmware, as does the bootloader.
Here's the getvar:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4283mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I just don't understand why I can't get the popup on my phone. That's what I get for trying to do it the right way, I guess =(.
I'd like to at least get stock back on the phone so I can have a working phone but I can't find an RUU that will work, my firmware is too new for any that I've found. =(
Should have done s-off. No point in modding without it.
Sent from my HTC One using Tapatalk
No unlock acknowledgment
I had the same issue with my first HTC One, it was a tmobile version. I ended up having to RUU whick alligned the firmware, hboot, rom, and recovery to the same versions. Boot and go through the setup. shut down. reboot. shutdown. boot into fastboot. create a new user with HTC, submit your token. Reboot your PC. Send the bin file to the device. unlock. powerdown. flash recovery. powerdown. enter recovery. powerdown and accept the install of SU. boot into the stock ROM. powerdown. You should be set to go.
Jcc1dls said:
I had the same issue with my first HTC One, it was a tmobile version. I ended up having to RUU whick alligned the firmware, hboot, rom, and recovery to the same versions. Boot and go through the setup. shut down. reboot. shutdown. boot into fastboot. create a new user with HTC, submit your token. Reboot your PC. Send the bin file to the device. unlock. powerdown. flash recovery. powerdown. enter recovery. powerdown and accept the install of SU. boot into the stock ROM. powerdown. You should be set to go.
Click to expand...
Click to collapse
I can't find an RUU for 4.06.1540.X though. =( I believe that will fix my problem but the solution is not out there.
xcrazydx said:
Should have done s-off. No point in modding without it.
Click to expand...
Click to collapse
At the time I modded there was no solution for S-OFF for 1.5+.
As for now, the only thing I seem to be able to successfully flash via RUU are the two 4.06 firmwares from @mike1986. Unfortunately, it's just firmware and not a full RUU so I can't boot into anything but the bootloader. Any hints on where I can find a stock rom that it will let me install via fastboot since I don't have a custom recovery?
Run a ruu exe
Sent from my HTC One using Tapatalk
xcrazydx said:
Run a ruu exe
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (1103159 KB)...
OKAY [ 36.684s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 148.740s
=/ Can't seem to find one that passes the signature verification.
Whaines said:
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (1103159 KB)...
OKAY [ 36.684s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 148.740s
=/ Can't seem to find one that passes the signature verification.
Click to expand...
Click to collapse
Your CID is still CWS__001.
Get the AT&T RUU from HTC and run it. Then start the bootloader unlock process all over.
Once you've got a working phone, then attempt to s-off using rumrunner with a live CD/USB of a Linux distribution.
Sent from my HTC One using xda app-developers app
ilal2ielli said:
Your CID is still CWS__001.
Get the AT&T RUU from HTC and run it. Then start the bootloader unlock process all over.
Once you've got a working phone, then attempt to s-off using rumrunner with a live CD/USB of a Linux distribution.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I really appreciate all the help, but there either is no AT&T RUU that will run with the firmware on my phone (afaik you can't go backward when you're S-ON), or it's not where I'm able to find it on the internet. I've looked here and htc1guru.com.
Whaines said:
I really appreciate all the help, but there either is no AT&T RUU that will run with the firmware on my phone (afaik you can't go backward when you're S-ON), or it's not where I'm able to find it on the internet. I've looked here and htc1guru.com.
Click to expand...
Click to collapse
That might be the case then...
I ran this RUU:
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
I used it go return to stock for a warranty exchange and had the 3.62.401.1 firmware at the time, but I was s-off.
Hopefully someone knows a way to get a ROM back on the phone so that you can get the bootloader unlocked.
Sent from my HTC One using xda app-developers app
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Jikstah said:
After the struggle of finding a way to revert my Vodafone Australia branded HTC One back to it's former, virgin glory..
I have finally locked the bootloader, set my CID back and got a stock ROM and recovery - thanks to Guru Stock Reset ROMs, which is the closest thing I could get to being stock as there are no available RUU's.
But the last and final hurdle is S-ON. My Googling tells me all it takes is this fastboot command: "fastboot oem writesecureflag 3"
But when I throw that in a command prompt, all I get is an error:
(bootloader) partition hboot signature error
(bootloader) writesecureflag: partitions siganture failed
OKAY [ 1.624s]
finished. total time: 1.625s
Could anyone please help? I have to return my diseased pink/purple-tinted, crappy camera issue!
Click to expand...
Click to collapse
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
nkk71 said:
wow, brick alert!
you have a modded hboot in there, so you're obviously not as stock as you'd like to think. better you rethink your strategy, and/or check my guide http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
I thank you immensely.
Jikstah said:
Damn dude, how far am I from a brick? :S
and you are absolutely correct, I completely forgot about my hboot being modified at 1.55.
It's been awhile since I tampered around with my phone.
Click to expand...
Click to collapse
Luckily the signature check kept you away from a brick, had you been able to S-On with a modded hboot, then you would have had a brick.
Jikstah said:
Is it then possible to downgrade my hboot to 1.44, with my current set-up? and continue to s-on?
Click to expand...
Click to collapse
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
nkk71 said:
I'm not sure what method you used to return to stock, but obviously hboot is not stock, and so could other things as well; I would recommend following my guide, especially if you intend on going S-On.
If you do want to follow my guide, post a "fastboot getvar all" (excluding IMEI and s/n), and I'll let you know which files you need.
Click to expand...
Click to collapse
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 3782mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.067s
Surely I'm close?! Thanks again.
Jikstah said:
I mean no offence in not wanting to follow your guide, it's great - especially for those less knowledgeable, and in need.
So here's my getvar:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
Surely I'm close?! Thanks again.
Click to expand...
Click to collapse
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
nkk71 said:
no offense taken
but you have PN0714000 + VODAP021 and firmware 3.62.401.1 (.401. = WWE unbranded), so you need to get your firmware correct too; inline with the ROM you are now on.
and personally, I don't recommend going S-Off to S-On on hboot 1.55, sometimes it works fine, but sometimes it triggers "tamper detected" and the tampered is back (can't say when/if it will happen to you)
Click to expand...
Click to collapse
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Jikstah said:
Ugh, more complications.. back to the drawing board it is!
So looks like all I need is firmware and hboot?
But do you reckon, the repair center will pay any attention to these attributes? I've heard all they check is S-ON, tamper flags and unlocked bootloaders?
Click to expand...
Click to collapse
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
nkk71 said:
hboot will be part of the firmware.zip,
and I don't know what they will check, but you may have a problem when it comes back -> if you're S-On, LOCKED bootloader with firmware not matching your MID and CID, then chances are high that HTCDev won't unlock your phone.
Click to expand...
Click to collapse
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Jikstah said:
Okay, well that simplifies things..
Now I just have to find a firmware.zip
You're pretty well-versed, I must thank you again for your foresight.
Click to expand...
Click to collapse
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
nkk71 said:
I'm assuming you used Guru ROM 2.24.980.2 ? i made a quick search but came up empty on the firmware for that. you could pull it from the OTA file if you find it; within the OTA.ZIP is another firmware.zip <- that's signed original firmware
Click to expand...
Click to collapse
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Jikstah said:
Rejoice! For I have found the exact firmware for the ROM - http://forum.xda-developers.com/showpost.php?p=44452049&postcount=438
Google is truly a wonderful thing, and you Mr. nkk71.
Click to expand...
Click to collapse
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
nkk71 said:
Nice find :good: :good:
don't forget to flash it twice:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
and since firmware & ROM are 2.xx (hboot 1.54), going from S-Off to S-On should be safe
Click to expand...
Click to collapse
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Jikstah said:
Oh jeez, here we go. I put the firmware.zip into my sd card, pulled up a cmd, entered rebootRUU mode, and tried to flash firmware zip.
And...
C:\adb>fastboot flash zip firmware.zip
target reported max download size of 1526722560 bytes
sending 'zip' (28294 KB)...
OKAY [ 2.210s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 2.701s
What's wrong with my CID? I even changed it from VODAP021 to HTC__039 to see if it would run, still the same error.. :|
EDIT: Okay so I SuperCID'ed, it worked however my bootloader is still 1.55? wut.
Don't tell me I need an unlocked bootloader, I need an unlocked bootloader right? -_-
I believe you said HTCdev won't unlock it if I had a non-matching firmware to my CID/MID? ugh.
EDIT: NOPE, no luck either with an unlocked bootloader - same result.
Click to expand...
Click to collapse
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
nkk71 said:
You do realize those errors/safe-guards are actually saving you!!
There's nothing wrong with your CID, so set it back to what it's supposed to be.
And the reason it's not working (actually it is), you are flashing the wrong firmware.zip, the one you are flashing is 28294 KB (probably a modded one), whereas the one you should be flashing (from the link you posted earlier) is 41197KB.
now put the correct firmware.zip in your adb/fastboot folder and flash it, fastboot doesn't use anything from your sdcard, it uses the files on your PC.
Click to expand...
Click to collapse
Gosh, you are too good. This is definitely the big break.
But nope, freakin' adb decides to bail on me and my device can no longer be detected. WTF?! What have I done to deserve such trouble.. -_-
I was using the latest Viper Rom and my Camera busted on my phone. So naturally I needed to get the M7 back to stock. I have never done it before so I did some searching and found the method right in this same forum.
So Walking through the instructions everything went well
I locked the bootloader
went through the process of flashing the stock rom with fastboot and it keeps erroring out. I am consistently getting "FAILED (status read failed (Too many links))" I tried the RUU and I keep getting unknown errors from those too. I have tried multiple PC and different usb cables and ports. I am completely stumped.
I was under the impression that it didn't matter which stock ROM you tried but I did try many different ones.
Would anyone have any suggestions?
I'm not sure what RUU guide you used, but I and a few others have had success with the guide I wrote. Try it and follow up here or in that thread if you have issues (or if it worked for you).
http://forum.xda-developers.com/spr...de-reset-phone-using-ruu-htcfastboot-t2876110
Thanks for the links and the response. I followed your step to a tee and got to step 6 and tried to flash the firmware. I am s-off and when I pushed the firmware o am now getting;
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830
Any suggestions?
Thanks again for your help.
Just another thing I noticed with your guide
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
s-off means the bootloader is unlocked and s-on means that it is locked. so your instructions are a little unclear. I am assuming that you meant that you need the bootloader locked.
On a whim I unlocked my bootloader again using fastboot and my BIN file and my phone did finally boot back to the Viper rom instead of being stuck on the Bootloader screen. I am curious why going s-on is making the phone fail and soft bricking the phone. Maybe my HBOOT is wrong? Could my Twerk recovery corrupted HBOOT?
Thanks again for your help!
raremind said:
Thanks for the links and the response. I followed your step to a tee and got to step 6 and tried to flash the firmware. I am s-off and when I pushed the firmware o am now getting;
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830
Any suggestions?
Thanks again for your help.
Click to expand...
Click to collapse
raremind said:
Just another thing I noticed with your guide
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
s-off means the bootloader is unlocked and s-on means that it is locked. so your instructions are a little unclear. I am assuming that you meant that you need the bootloader locked.
On a whim I unlocked my bootloader again using fastboot and my BIN file and my phone did finally boot back to the Viper rom instead of being stuck on the Bootloader screen. I am curious why going s-on is making the phone fail and soft bricking the phone. Maybe my HBOOT is wrong? Could my Twerk recovery corrupted HBOOT?
Thanks again for your help!
Click to expand...
Click to collapse
I think this is the issue: since you are s-off, you should have ignored step 4 and not have locked your bootloader. A locked bootloader will not allow you to flash the firmware (it fails the security check since it wasn't created by HTC). Unlock your bootloader and try to flash the firmware file again. The reason I'm not sure is because it was my impression that an s-off phone ignores the locked/unlocked flag. But, I never lock my bootloader so I'm not sure.
By the way, s-off =/= unlocked and s-on =/= locked. Phones start as locked and s-on. Unlocking the bootloader through HTC Dev allows you to install custom recoveries and ROMs. However, it is limited because you are still s-on (security on). For example, you can only upgrade hboots, but can never downgrade to an older one. Same with RUUs. Being s-off is very flexible but more dangerous as you can access normally protected partitions. Hope that clears things up some.
Thank you again for your help. I seem to be a little more confused now. Line 4 of your guide states;
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
Click to expand...
Click to collapse
Why would I lock the the bootloader using "fastboot oem lock" if I already have s-on. You said you can not flash firmware with s-on but line 4 says I should before I flash firmware. What I just got from you, am I understanding right that I should not "fastboot oem lock" before you flash the firmware? If you are s-on the bootloader is already locked and you would not be able to do step 5.
I am s-off right now. Would I flash the firmware now, then s-on when run the RUU?
Unlocked bootloader does not = s-off.
My guess is you are unlocked not s-off.
S-OFF explained - by a Developer
So if I need to update the firmware do I need to be s-on or s-off? I need to get the phone back to stock and am having a really hard time.
raremind said:
So if I need to update the firmware do I need to be s-on or s-off? I need to get the phone back to stock and am having a really hard time.
Click to expand...
Click to collapse
Easiest way to go back to stock is to RUU. If you are s-on you need to re-lock (it will tell you in bootloader if you are s-on or s-off)
Updating firmware can be done s-on (need to re-lock bootloader) or s-off (no locking required).
BD619 said:
Easiest way to go back to stock is to RUU. If you are s-on you need to re-lock (it will tell you in bootloader if you are s-on or s-off)
Updating firmware can be done s-on (need to re-lock bootloader) or s-off (no locking required).
Click to expand...
Click to collapse
That's just the thing. I am s-on and relocked and every RUU I have tried failed. I have tried it with fastboot the exe and everything else under the sun. Everything I have tried has failed. here is what I am seeing:
Code:
*** TAMPERED ***
*** RELOCKED ***
*** Security warning ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO- 1.01.20.0984_2
OpenDSP- v32.120.274.0909
OS-5.05.651.2
eMMC-boot 2048MB
Sep 24 2014, 16:58:42:0
I rooted and flashed TEAMWIN recovery and Viper 7.1 - My Camera started acting up and I couldn't talk on calls so I wanted to get it back to stock. The only thing I was able to do successfully trying to get it back to stock was lock the bootloader. Everything beyond that has failed.
This is what I get updating the firmware:
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking..
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830s
This is what I got when I locked the bootloader:
Code:
D:\Downloads\HTC\Try this\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.199s
Trying to flash RUU I get:
Code:
D:\Downloads\HTC\Try this\Minimal ADB and Fastboot>fastboot flash zip Sprint_HTC
_One_m7wls_1.29.651.7_encrypted_ROM.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1029700 KB)...
OKAY [ 37.166s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 133.077s
Running the RUU.exe I recieve an unknown error. Am I screwed?
Ok first off you are using the wrong RUU.
You need to use the 5.05.651.2 RUU
So, you are s-on and relocked (you said s-off before so that threw me off). Because you are s-on, you may not be successful flashing the firmware, hence the security warning in the first box (see the link explaining s-off that @BD619 left). I probably need to fix my guide to reflect that issue. In the second box, you get an error trying to relock which makes sense since you are already locked. In the third box, it looks like you get an error since you are trying to flash an older RUU (not allowed since you are s-on).
At this point, as BD said, you should be able to just go here and download the ruu exe (it's the first link). I run it as an administrator just to be safe. Follow the prompts and wait around ten minutes for it to do its thing.
Don't get too frustrated. The (forced) learning process from this is very valuable. BD and I are just members who have been on here long enough to have a good understanding of what's going on. Not speaking for BD, but I started on here knowing next to nothing about Android except it's based on Linux.
Not speaking for BD, but I started on here knowing next to nothing about Android except it's based on Linux.
Click to expand...
Click to collapse
You knew more then me lol.
My first couple posts were me begging for help because I bricked my sons Epic 4G Touch lol (posted in Development...reasoning I thought it would get more exposure and I would get helped faster lol)
BD619 said:
(posted in Development...reasoning I thought it would get more exposure and I would get helped faster lol)
Click to expand...
Click to collapse
Haha, noob! I would have replied with "Cool ROM, bro".
Well thank you both! I was able to successfully flash the 5.05.651.2 RUU. Such a simple thing that was causing me such problems. I was under the impression that the RUU version didn't make a difference. I wish they would add that to the guides! Well thanks to both of you!
Hi,
I have a new Sprint HTC one m8 that has sim lock.
I tried to follow these guides I found on the interent :
1. un lock nootloader -"youtube.com/watch?v=QU7vi388dMk&feature=youtu.be"
2. root the device - "youtube.com/watch?v=rRkAHw_GmIs&feature=youtu.be"
3. s-off - "htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-firewater-any-computer-0151230/"
the 1st 2 steps went fine, The last one got my phone to stuck in the bootloader screen.
So I decided to try and root the device again but with no luck.
please help me get out of these maze.
How do I continue from here?
I read something about RUU, is that the solution?
is it possible to return to the state where the phone is bootloader locked again and from there to start over?
any help will be very much appreciated
these is what I see in my HTC one :
*** TAMPERED ***
*** UNLOCKED ***
M8_WHL PVT ShIP S-ON
HBOOT-3.16.0.000
RADIO-1.08.20.0610
OpenDSP-v45.2.2-00542-M8974_HM.0422
OS-1.54.654.15
eMMC-boot 2048MB
Jun 4 2014, 12:00:35.22989
FASBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
HBOOT
RANDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
Well that post you are following to get S-off is for a different phone, the One M7 so that could be part of the problem. I'm pretty sure the only way to get s-off is with sunshine and it costs $25
Have you looked at the directions in the thread linked below? As stated previously, you will need to S-off via Sunshine, as the Firewater exploit is no longer available.
http://forum.xda-developers.com/showthread.php?t=2718150
Additionally, you can install Bad Boyz ROM and follow the instructions in their ROM thread to SIM unlock your phone. You will still need to be S-off to do this.
http://forum.xda-developers.com/showthread.php?t=2729170
ok, but currently I am stuck in the boot loader screen,
Can I continue with the link above from this state?
or do I need to do something else before that?
hanzibar said:
ok, but currently I am stuck in the boot loader screen,
Can I continue with the link above from this state?
or do I need to do something else before that?
Click to expand...
Click to collapse
Can you get into recovery? If so, flash a ROM or restore a backup. If all else fails, RUU. RUU's can be found in the thread linked below.
http://forum.xda-developers.com/showthread.php?t=2729173
Regardless of what you do, you will HAVE TO BE S-OFF in order to SIM unlock your phone, so there is no point in trying to go through the steps to SIM unlock because it simply won't work without the device being S-off first.
Hi,
Thanks for the help, I will try the RUU. I don't have any data on the device and I prefer "to start fresh" with it
about the 's-off' - yes I know I need that in order to unlock the sim - I hope the link I have above also include 's-off' guide
hanzibar said:
Hi,
Thanks for the help, I will try the RUU. I don't have any data on the device and I prefer "to start fresh" with it
about the 's-off' - yes I know I need that in order to unlock the sim - I hope the link I have above also include 's-off' guide
Click to expand...
Click to collapse
UPDATE :
well I tried to use FUU with 2 versions of ROM :
1. Sprint_HTC_One_M8_HK_3.31.654.2_RUU
2. Sprint_HTC_One_M8_Harman_1.54.654.15_RUU.zip
in both of the I've got
ERROR[155]: unknown Error
or
ERROR [170]: USB CONNECTION ERROR
any one got any idea?
should be different if I try it directly from the device (copy the rom to its external cd)?
Don't bother with the FUU. Use the RUU, instead. Make sure you relock your bootloader with the command fastboot oem lock prior to running the RUU.
Magnum_Enforcer said:
Don't bother with the FUU. Use the RUU, instead. Make sure you relock your bootloader with the command fastboot oem lock prior to running the RUU.
Click to expand...
Click to collapse
If I am getting when writing : "fastboot oem lock" :
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.135s
should I be worried? regarding the "FAILED" or the RUU from the external cd won't mind that failure?
Magnum_Enforcer said:
Can you get into recovery? If so, flash a ROM or restore a backup. If all else fails, RUU. RUU's can be found in the thread linked below.
http://forum.xda-developers.com/showthread.php?t=2729173
Regardless of what you do, you will HAVE TO BE S-OFF in order to SIM unlock your phone, so there is no point in trying to go through the steps to SIM unlock because it simply won't work without the device being S-off first.
Click to expand...
Click to collapse
not true, I sim-unlocked my sprint htc one m8 S-on,you just need to root you phonr, either you have the stock software or a rom is not important
---------- Post added at 08:24 PM ---------- Previous post was at 08:20 PM ----------
hanzibar said:
If I am getting when writing : "fastboot oem lock" :
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = 536739196 (0x1FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.135s
should I be worried? regarding the "FAILED" or the RUU from the external cd won't mind that failure?
Click to expand...
Click to collapse
don't worry about that, you may get stucked in the bootloader but don't panic yet, just connect your phone and run the RUU, now just root your phone and follow the instructions herehttp://forum.xda-developers.com/showpost.php?p=52145162&postcount=2
activate in Sprint, is necessary?
Magnum_Enforcer said:
Have you looked at the directions in the thread linked below? As stated previously, you will need to S-off via Sunshine, as the Firewater exploit is no longer available.
http://forum.xda-developers.com/showthread.php?t=2718150
Additionally, you can install Bad Boyz ROM and follow the instructions in their ROM thread to SIM unlock your phone. You will still need to be S-off to do this.
http://forum.xda-developers.com/showthread.php?t=2729170
Click to expand...
Click to collapse
My device was bought in the USA and shipped it Israel. The device is new and was open for the very 1st time in Israel.
Apparently the phone can't be activate and be used is another carrier unless it was 1st activated in Sprint.
Is the above links will enable me to activate it from Israel?
hanzibar said:
My device was bought in the USA and shipped it Israel. The device is new and was open for the very 1st time in Israel.
Apparently the phone can't be activate and be used is another carrier unless it was 1st activated in Sprint.
Is the above links will enable me to activate it from Israel?
Click to expand...
Click to collapse
I do not know.
Magnum_Enforcer said:
I do not know.
Click to expand...
Click to collapse
any one knows?
I encountered the same problem, bought it on the US and had it shipped to my country, I factory reset it without thinking, my solution was to flash a custom rom, and don't connect it to wifi or any internet connection
guissepi said:
I encountered the same problem, bought it on the US and had it shipped to my country, I factory reset it without thinking, my solution was to flash a custom rom, and don't connect it to wifi or any internet connection
Click to expand...
Click to collapse
"dont connect it to wifi or any internet" - how can you use the device without the internet?
hanzibar said:
"dont connect it to wifi or any internet" - how can you use the device without the internet?
Click to expand...
Click to collapse
I mean, just while you're in the setup process, also try skipping everything there
guissepi said:
I mean, just while you're in the setup process, also try skipping everything there
Click to expand...
Click to collapse
I just flashed the phone with new RUU, I am guessing that is what you are refering as factory reset.
It keeps asking for activation - and it keeps failing
Hi,
I have a One M7 which has Vodafone branding, but is not network locked and has HBOOT 1.61 and S-ON. I wanted to convert it to Google Play Edition, so I did the following:
Unlocked the bootloader using instructions at HTCdev
Installed recovery using Hasoon2000's HTC One All-In-One Toolkit
When restarting recovery, it asked me if I wanted to root, I chose to root
Tested root with app on Play Store, found that it hadn't been rooted successfully
Installed SunShine to achieve S-off, temproot was unsuccessful; couldn't S-off
Booted into recovery, and for whatever reason, chose to "fix permissions"
On next reboot, I found that Play Store was missing
Performed a factory reset from recovery, rebooted
Android proceeded to do it's "updating apps" thing, but stopped halfway through and gave me the error "Unfortunately Setup Wizard Has Stopped Working". Now the error continuously pops up and I can't access anything in the OS. I also can't seem to get ADB to recognise my device any more. It either says "error: device not found", or "List of devices attached" and follows up with two blank lines.
I'm stuck as to what to do with this now. The only thing that works is fastboot:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3781mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-7661b1d7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
Click to expand...
Click to collapse
cds80 said:
Hi,
I have a One M7 which has Vodafone branding, but is not network locked and has HBOOT 1.61 and S-ON. I wanted to convert it to Google Play Edition, so I did the following:
Unlocked the bootloader using instructions at HTCdev
Installed recovery using Hasoon2000's HTC One All-In-One Toolkit
When restarting recovery, it asked me if I wanted to root, I chose to root
Tested root with app on Play Store, found that it hadn't been rooted successfully
Installed SunShine to achieve S-off, temproot was unsuccessful; couldn't S-off
Booted into recovery, and for whatever reason, chose to "fix permissions"
On next reboot, I found that Play Store was missing
Performed a factory reset from recovery, rebooted
Android proceeded to do it's "updating apps" thing, but stopped halfway through and gave me the error "Unfortunately Setup Wizard Has Stopped Working". Now the error continuously pops up and I can't access anything in the OS. I also can't seem to get ADB to recognise my device any more. It either says "error: device not found", or "List of devices attached" and follows up with two blank lines.
I'm stuck as to what to do with this now. The only thing that works is fastboot:
Click to expand...
Click to collapse
Your post is the perfect example why I say to everyone:, don't use any toolkit, learn the basic adb/fastboot commands!
Toolkits can be nice for some time but when they are not supported anymore, they will flash an outdated version of TWRP and so outdated supersu binaries which will cause issues.
Now you can flash a custom rom using twrp, or flash your stock RUU using fastboot, root your phone using the latest supersu version and s-off with sunshine.
alray said:
Your post is the perfect example why I say to everyone:, don't use any toolkit, learn the basic adb/fastboot commands!
Toolkits can be nice for some time but when they are not supported anymore, they will flash an outdated version of TWRP and so outdated supersu binaries which will cause issues.
Now you can flash a custom rom using twrp, or flash your stock RUU using fastboot, root your phone using the latest supersu version and s-off with sunshine.
Click to expand...
Click to collapse
Thanks for the reply. So I can use fastboot to flash roms without having to copy them to the phone first? For some reason I thought it was only for flashing recoveries.
cds80 said:
Thanks for the reply. So I can use fastboot to flash roms without having to copy them to the phone first? For some reason I thought it was only for flashing recoveries.
Click to expand...
Click to collapse
You can use fastboot to flash RUU (stock rom). Other roms are flashed from recovery.
Sent from my HTC One using XDA Labs
Thanks for your help. I've downloaded the second-gen 7.18.161.21 RUU for vodafone from the collection in your sig. The MD5 is reported as da17b2877fbe45da5598d2d02d89d4eb which matches my download, but I am concerned that I cannot read the .zip properly with 7zip or WinRAR to inspect the .txt file. 7zip won't open it at all, and WinRAR displays the contents but reports corruption when I try to extract.
Should I proceed to flash it?
cds80 said:
Thanks for your help. I've downloaded the second-gen 7.18.161.21 RUU for vodafone from the collection in your sig. The MD5 is reported as da17b2877fbe45da5598d2d02d89d4eb which matches my download, but I am concerned that I cannot read the .zip properly with 7zip or WinRAR to inspect the .txt file. 7zip won't open it at all, and WinRAR displays the contents but reports corruption when I try to extract.
Should I proceed to flash it?
Click to expand...
Click to collapse
Okay, having just seen your comment on "corrupted" archives actually being encrypted, I feel a little foolish. I was following another one of posts that mentioned checking the version numbers from a text file inside the archive to ensure they match.
Well, I tried flashing the RUU mentioned earlier, here's what I got:
C:\adb>fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_Vodafone_UK_7.18.161.21_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430367_signed.zip
target reported max download size of 1514139648 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 340906976 is not a multiple of the block size 4096
sending sparse 'zip' (1478649 KB)...
error: write_sparse_skip_chunk: don't care size 340906976 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 340906976 is not a multiple of the block size 4096
OKAY [ 61.452s]
writing 'zip'...
(bootloader) zip header checking...
FAILED (remote: 32 header error)
finished. total time: 61.630s
Click to expand...
Click to collapse
cds80 said:
Well, I tried flashing the RUU mentioned earlier, here's what I got:
Click to expand...
Click to collapse
If you want to flash the .21 ruu on your .51 version, you'll need too downgrade you version-main first. You'll also need to use htc_fastboot.exe not the regular fastboot.exe to flash the RUU.
Sent from my HTC One using XDA Labs
alray said:
If you want to flash the .21 ruu on your .51 version, you'll need too downgrade you version-main first. You'll also need to use htc_fastboot.exe not the regular fastboot.exe to flash the RUU.
Sent from my HTC One using XDA Labs
Click to expand...
Click to collapse
Thanks. So, it seems that I have two options: follow the instructions for flashing an older RUU, or change my CID to flash a current RUU that belongs to a different carrier (I cannot find a Vodafone RUU that matches my version). Is that correct?
Never mind, I managed to flash an older RUU following the instructions in your collection link. It's now booting properly again, and everything seems fine! Thanks for the help