Related
Hi all, my HTC One is currently running on unlocked bootloader with s-on, and on hboot 1.44.
I believe my phone is stuck on unlocked bootloader. My phone runs perfectly with no hiccups when my bootloader is unlocked, but when I try to use adb to relock my bootloader, while it does relock my bootloader successfully, I'm unable to boot into the rom, the phone just switches on into the bootloader everytime i reboot, and a "Security Warning" pops up below the "TAMPERED" and "RELOCKED" text.
I'm relocking my bootloader so that the RUU will work as I'm constantly getting error code 155 in the RUU when I try to flash back to stock. I've also tried to S-OFF my device but it kept giving me error 6 despite the fact that I was able to get on S-OFF before.
Note: I think I've done something wrong previously that got me into this situation. When I was trying to get my phone back to stock through RUU at first, I had S-OFF initially, and I followed this guide (http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html) but I forgot to flash the RUU first before I used the "writesecureflag 3" command to lock my bootloader and revert back to S-ON.
Is there a way I could revert back and get my bootloader relocked with no problems? I've done a backup before I messed up my RUU, but due to the fact that I was stuck on the bootloader screen after locking my bootloader, I had to unlock my bootloader again which wiped my whole SD card including my backup...
EDIT: added getvar
(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: 2.24.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT367xxxxxx
(bootloader) imei: 3558590xxxxxx
(bootloader) meid: 00000000000000 <- (looks fishy, could this be the source of the problem?)
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4248mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links)) <- (this too)
finished. total time: 0.050s
my meid is also all 0s so that is fine.
your firmware is version 2.24.707.1, has this been upgraded since you tried revone the first time? That could be why you are getting an error code with revone now, did you have 1.29.707.16 originally?
if you unlock your bootloader again you flash a custom recovery then install the stock rom for your carrier from your recovery. This will put your phone on a stock rom then you can re-lock again after that with fastboot oem lock.
you can gain Locked instead of Relocked using revone if you can get it to work again, which may require downgraded firmware version.
or I would run a .ruu for your device, though these could be dangerous especially if you are s-on. Also attempting to downgrade with RUU would cause a brick pretty sure.
Your phone will always bootloop when you lock the boot loader with a custom recovery installed. This is normal.
Edit:
I suppose I should offer some help also. Going to S-on was a mistake. You need to unlock the boot loader and flash a stock rom, then try to regain S-off. If you can achieve it, relock the boot loader and run the RUU. Then use Revone to set the ****Tampered**** flag to off and lock the boot loader. And if you do achieve S-off again, do NOT S-on. It is not necessary.
Sent from my One using XDA Premium 4 mobile app
blu9987 said:
my meid is also all 0s so that is fine.
your firmware is version 2.24.707.1, has this been upgraded since you tried revone the first time? That could be why you are getting an error code with revone now, did you have 1.29.707.16 originally?
if you unlock your bootloader again you flash a custom recovery then install the stock rom for your carrier from your recovery. This will put your phone on a stock rom then you can re-lock again after that with fastboot oem lock.
you can gain Locked instead of Relocked using revone if you can get it to work again, which may require downgraded firmware version.
or I would run a .ruu for your device, though these could be dangerous especially if you are s-on. Also attempting to downgrade with RUU would cause a brick pretty sure.
Click to expand...
Click to collapse
Wow thanks! I managed to lock my bootloader finally after finding and flashing a 1.29.707.3 stock rom, but my touchscreen is not responding now, which I guess is most probably an issue with the firmware? And I presume it's safer to use RUU over S-OFF? I want to try revone and S-OFF again but i cant grant adb shell superuser since i cant get my touchscreen to respond.. Oh god, endless ordeals lol...
EDIT: I'm on 1.29.707.3 currently and I have the 1.29.707.3 RUU, is it possible to flash the RUU? I'm hoping to get the RUU to run so that I can solve the touchscreen issue and possibly achieve S-OFF afterwards.
EDIT2: I went ahead with running RUU after finally being able to relock my bootloader but now I'm faced with RUU error 140
jerronchua55 said:
Wow thanks! I managed to lock my bootloader finally after finding and flashing a 1.29.707.3 stock rom, but my touchscreen is not responding now, which I guess is most probably an issue with the firmware? And I presume it's safer to use RUU over S-OFF? I want to try revone and S-OFF again but i cant grant adb shell superuser since i cant get my touchscreen to respond.. Oh god, endless ordeals lol...
EDIT: I'm on 1.29.707.3 currently and I have the 1.29.707.3 RUU, is it possible to flash the RUU? I'm hoping to get the RUU to run so that I can solve the touchscreen issue and possibly achieve S-OFF afterwards.
EDIT2: I went ahead with running RUU after finally being able to relock my bootloader but now I'm faced with RUU error 140
Click to expand...
Click to collapse
You are right, the touchscreen won't work because the drivers were updated in the firmware, but you can use an OTG cable with a mouse instead.
Anyway, first thing I would try to do is achieve s-off again (make sure you have hboot 1.44 dated before June 2013), and as Corry said, do not go back to s-on. adb should still work fine from your computer even without touchscreen, so you should be able to do it. In case your ROM is not "allowing" you proper use of adb or revone, then you can try the one I posted here: http://forum.xda-developers.com/showthread.php?t=2471174
nkk71 said:
You are right, the touchscreen won't work because the drivers were updated in the firmware, but you can use an OTG cable with a mouse instead.
Anyway, first thing I would try to do is achieve s-off again (make sure you have hboot 1.44 dated before June 2013), and as Corry said, do not go back to s-on. adb should still work fine from your computer even without touchscreen, so you should be able to do it. In case your ROM is not "allowing" you proper use of adb or revone, then you can try the one I posted here: http://forum.xda-developers.com/showthread.php?t=2471174
Click to expand...
Click to collapse
Even with ARHD 9.4 the touchscreen is still not responding, I think I need to reflash my firmware, is it possible to flash a firmware without updating hboot on S-ON?
jerronchua55 said:
Even with ARHD 9.4 the touchscreen is still not responding, I think I need to reflash my firmware, is it possible to flash a firmware without updating hboot on S-ON?
Click to expand...
Click to collapse
Just use the ROM to get S-Off, without touchscreen, just boot up the rom, and use adb from your PC.
Not possible to change firmware with S-On.
nkk71 said:
Just use the ROM to get S-Off, without touchscreen, just boot up the rom, and use adb from your PC.
Not possible to change firmware with S-On.
Click to expand...
Click to collapse
I couldnt get past my lockscreen to grant su access to adb shell without the touchscreen, but I just picked an OTG cable so I'm fine now.
Problem is, even on ARHD 9.4 I'm still getting error code -6 on revone... Bummer, I shouldn't have returned my phone back to S-ON.
EDIT: My hboot is dated 4/5/13, so it shouldnt be the patched 1.44 hboot. I'm gonna try S-OFF on the stock 1.29.707.3 instead, will post my results asap
jerronchua55 said:
I couldnt get past my lockscreen to grant su access to adb shell without the touchscreen, but I just picked an OTG cable so I'm fine now.
Problem is, even on ARHD 9.4 I'm still getting error code -6 on revone... Bummer, I shouldn't have returned my phone back to S-ON.
Click to expand...
Click to collapse
What's the date of your bootloader? If it's before June 2013 (and is version 1.44), you should be able to get it to work.
nkk71 said:
What's the date of your bootloader? If it's before June 2013 (and is version 1.44), you should be able to get it to work.
Click to expand...
Click to collapse
Nope it still didn't work, but i guess i resolved my main issue with not being able to relock my bootloader.
I'm gonna redirect my issues on the revone thread instead so yea, gave you a thanks for your help nonetheless!
jerronchua55 said:
Nope it still didn't work, but i guess i resolved my main issue with not being able to relock my bootloader.
I'm gonna redirect my issues on the revone thread instead so yea, gave you a thanks for your help nonetheless!
Click to expand...
Click to collapse
And one for you
Let me know if I can help out anyway.
If bootloader is May 2013 it shouldnt be the patched version. But it seems that there revone, not only has issues with ROMs, but also firmware. One last thing to try though: I saw one person was able to achieve S-Off using a GPe 4.2.2 ROM, (s)he didn't specify which but it worked. Since you're on the updated firmware, try getting your hands on a 4.2.2 GPe ROM and try.
I know it's all time consuming, but you never know :fingers-crossed:
Good luck
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
Hello everyone,
I am trying to get S-ON and I cant seem to figure it out, here is a little bit of background information you may need to provide proper help.
------------------------------------------------------------------
Background info:
- HTC One M7
- I have a LOCKED Bootloader
- I have tried "fastboot oem writesecureflag 3" command to try to set S-ON but i got this error: "partitions siganture failed"
- I have stock recovery
------------------------------------------------------------------
If someone can help me it would be greatly appreciated.
slicer812 said:
Hello everyone,
I am trying to get S-ON and I cant seem to figure it out, here is a little bit of background information you may need to provide proper help.
------------------------------------------------------------------
Background info:
- HTC One M7
- I have a LOCKED Bootloader
- I have tried "fastboot oem writesecureflag 3" command to try to set S-ON but i got this error: "partitions siganture failed"
- I have stock recovery
------------------------------------------------------------------
If someone can help me it would be greatly appreciated.
Click to expand...
Click to collapse
post your fastboot getvar all minus serial and IMEI and your bootloader screen
clsA said:
post your fastboot getvar all minus serial and IMEI and your bootloader screen
Click to expand...
Click to collapse
What is "getvar" and also why would you need my IMEI?
Here is a pic of my bootloader.
slicer812 said:
What is "getvar" and also why would you need my IMEI?
Here is a pic of my bootloader.
Click to expand...
Click to collapse
you have a Verizon HTC one ...why would you want s-on ?
it may be impossible to ever s-off again and you'll be stuck with stock
I said Minus your Serial and IMEI
clsA said:
you have a Verizon HTC one ...why would you want s-on ?
it may be impossible to ever s-off again and you'll be stuck with stock
I said Minus your Serial and IMEI
Click to expand...
Click to collapse
The reason I would want S-ON is to update to HTC Sense 6 Verizon does not allow updates to go through with S-OFF, as I was told by HTC, I have tested updating my device it wont work.
slicer812 said:
The reason I would want S-ON is to update to HTC Sense 6 Verizon does not allow updates to go through with S-OFF, as I was told by HTC, I have tested updating my device it wont work.
Click to expand...
Click to collapse
you phone will update with s-off
you need stock recovery
you should be using these forums before you screw up completely
http://forum.xda-developers.com/verizon-htc-one/general
clsA said:
you phone will update with s-off
you need stock recovery
Click to expand...
Click to collapse
I have the stock recovery though. And when i called HTC they said it will only update with S-ON.
slicer812 said:
I have the stock recovery though. And when i called HTC they said it will only update with S-ON.
Click to expand...
Click to collapse
lol, what did you think they would say ...shakes head
go here and do some reading
http://forum.xda-developers.com/verizon-htc-one/general
clsA said:
lol, what did you think they would say ...shakes head
go here and do some reading
http://forum.xda-developers.com/verizon-htc-one/general
Click to expand...
Click to collapse
I have looked up many things like that I just cant figure out what else i need to do I have tried restoring S-On by doing this "fastboot oem writesecureflag 3" then I get this error "partitions siganture failed"
Any suggestions?
And by the way I appreciate all your help.
slicer812 said:
I have looked up many things like that I just cant figure out what else i need to do I have tried restoring S-On by doing this "fastboot oem writesecureflag 3" then I get this error "partitions siganture failed"
Any suggestions?
And by the way I appreciate all your help.
Click to expand...
Click to collapse
regardless of what HTC told you you don't need s-on to take the OTA ...
have you downloaded the OTApkg.zip ?
what stock recovery did you use ?
what is your fastboot getvar all results ? Minus your serial and IMEI
clsA said:
regardless of what HTC told you you don't need s-on to take the OTA ...
have you downloaded the OTApkg.zip ?
what stock recovery did you use ?
what is your fastboot getvar all results ? Minus your serial and IMEI
Click to expand...
Click to collapse
What is "fastboot getvar"? Also where do I get the OTApkg.zip?
slicer812 said:
What is "fastboot getvar"? Also where do I get the OTApkg.zip?
Click to expand...
Click to collapse
fastboot is an app you run from your PC command prompt to flash your phone
fastboot flash recovery recovery.zip is an example
fastboot getvar all outputs the specs for your device
here's mine
C:\fastboot>adb reboot
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000 My phones hboot
(bootloader) version-baseband: 4T.27.3218.14 Radio
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10 < my phones software version
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34 Removed
(bootloader) imei: 354 Removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000 My MID
(bootloader) cidnum: CWS__001 My CID
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
C:\fastboot>
Click to expand...
Click to collapse
here's the only RUU I can find for your phone
http://flyhalf205.com/?dir=RUU/m7vzw
you flash them with fastboot
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip << yes two times
fastboot reboot-bootloader
Just make sure you name the RUU rom.zip not rom.zip.zip and it's in the same folder as fastboot
Don't lock your bootloader and Don't go s=on
just flash the PN07IMG_M7_WL_JB_50_VZW_2.10.605.1_DECRYPT.zip
and take all the OTA updates you want .. then flash custom recovery and re- root your phone if you want.
clsA said:
fastboot is an app you run from your PC command prompt to flash your phone
fastboot flash recovery recovery.zip is an example
fastboot getvar all outputs the specs for your device
here's mine
here's the only RUU I can find for your phone
http://flyhalf205.com/?dir=RUU/m7vzw
you flash them with fastboot
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip << yes two times
fastboot reboot-bootloader
Just make sure you name the RUU rom.zip not rom.zip.zip and it's in the same folder as fastboot
Click to expand...
Click to collapse
I used flashify app to flash my recovery but I backed up my stock recovery. My phone is on the stock recovery right now and its been on stock for over a day now. I tried to issue the command "fastboot getvar" but nothing happened and it listed command options. I do not have too much experience with this lol sorry if I'm annoying you.
slicer812 said:
I used flashify app to flash my recovery but I backed up my stock recovery. My phone is on the stock recovery right now and its been on stock for over a day now. I tried to issue the command "fastboot getvar" but nothing happened and it listed command options. I do not have too much experience with this lol sorry if I'm annoying you.
Click to expand...
Click to collapse
pretty much all i can tell you is, everything you need is above in post #12
Flash the RUU and your phone will redownload and install the updates one at a time.
Don't Relock the bootloader
Don'T go S-On !
use this custom recovery when you done taking updates
http://techerrata.com/file/twrp2/m7vzw/openrecovery-twrp-2.7.0.1-m7wlv.img
P.S I'm not Annoyed ..I'm just old and grouchy
clsA said:
pretty much all i can tell you is, everything you need is above in post #12
Flash the RUU and your phone will redownload and install the updates one at a time.
Don't Relock the bootloader
Don'T go S-On !
use this custom recovery when you done taking updates
http://techerrata.com/file/twrp2/m7vzw/openrecovery-twrp-2.7.0.1-m7wlv.img
P.S I'm not Annoyed ..I'm just old and grouchy
Click to expand...
Click to collapse
What if I install the RUU and I cant update my phone? <-- Im not sure if thats even possible. lol
Couldn't I just call verizon and have them push an RUU to my phone? They said they could do that.
elsaltu vers
slicer812 said:
What if I install the RUU and I cant update my phone? <-- Im not sure if thats even possible. lol
Couldn't I just call verizon and have them push an RUU to my phone? They said they could do that.
Click to expand...
Click to collapse
Also, would installing the RUU wipe my phone?
Have somewhat similar problem
have RUU flashed should be completely stock, but can't S-ON
https://www.dropbox.com/s/33jun0xivk0wamt/Screenshot 2014-07-13 00.02.23.png
Heres the getvar all
Btw, does the RUU contains stock recovery?
slicer812 said:
Also, would installing the RUU wipe my phone?
Click to expand...
Click to collapse
Yes RUU wipes everything
Sent from my HTC One_M8 using Tapatalk 4
---------- Post added at 09:49 PM ---------- Previous post was at 09:48 PM ----------
alwinwh said:
Have somewhat similar problem
have RUU flashed should be completely stock, but can't S-ON
https://www.dropbox.com/s/33jun0xivk0wamt/Screenshot 2014-07-13 00.02.23.png
Heres the getvar all
Btw, does the RUU contains stock recovery?
Click to expand...
Click to collapse
Yes RUU is stock everything
Don't go S-on ever!!
Sent from my HTC One_M8 using Tapatalk 4
clsA said:
Yes RUU wipes everything
Sent from my HTC One_M8 using Tapatalk 4
Click to expand...
Click to collapse
What if I install an RUU and I still can't update my phone? Also, couldn't I call Verizon and have them puch an RUU to my phone, they said they can do that?
slicer812 said:
What if I install an RUU and I still can't update my phone? Also, couldn't I call Verizon and have them puch an RUU to my phone, they said they can do that?
Click to expand...
Click to collapse
Just flash the RUU and take the updates
Sent from my HTC One_M8 using Tapatalk 4
I have been at this for a couple of days, and have had no luck. So here I am posting for help.
I need to revert a HTC One m7 Sprint to stock for my cousin who bought the phone rooted on swappa. She wants it stock so she can get OTA updates. By stock I mean no tampered flag, no unlocked flag and OTA updates, stock rom and recovery. And I'm having trouble doing so, I have no experience with anything other than Nexus devices.
Current status:
1) Flashed this (Sprint-ONE-3.04.651.2-De-Odex.zip) to the phone using CWM
2) Relocked bootloader (I relocked bootloader so I can use official ROM update utility tool to install (Sprint_HTC_One_m7wls_3_04_651_2_RUU)) on phone.
3) Phone won't boot into ROM (can't get past bootloader)
4) Now phone won't even boot into recovery
>>>fastboot oem boot
...
(bootloader) Start Verify: 3
(bootloader) Boot/Recovery signature checking...
(bootloader) TZ_HTC_SVC_HASH ret = 0
(bootloader) [ERR] Boot/Recovery image signature checking failed!
OKAY [ 1.107s]
finished. total time: 1.108s
Click to expand...
Click to collapse
I'm guessing that because S=ON it's checking signature of recovery and failing because recovery isn't stock. If this was a nexus I could just flash the official recovery.img but alas it's not, so I don't know where to turn.
Please tell me how to best proceed.
Thank you and have a nice day.
markushendrich said:
I have been at this for a couple of days, and have had no luck. So here I am posting for help.
I need to revert a HTC One m7 Sprint to stock for my cousin who bought the phone rooted on swappa. She wants it stock so she can get OTA updates. By stock I mean no tampered flag, no unlocked flag and OTA updates, stock rom and recovery. And I'm having trouble doing so, I have no experience with anything other than Nexus devices.
Current status:
1) Flashed this (Sprint-ONE-3.04.651.2-De-Odex.zip) to the phone using CWM
2) Relocked bootloader (I relocked bootloader so I can use official ROM update utility tool to install (Sprint_HTC_One_m7wls_3_04_651_2_RUU)) on phone.
3) Phone won't boot into ROM (can't get past bootloader)
4) Now phone won't even boot into recovery
I'm guessing that because S=ON it's checking signature of recovery and failing because recovery isn't stock. If this was a nexus I could just flash the official recovery.img but alas it's not, so I don't know where to turn.
Please tell me how to best proceed.
Thank you and have a nice day.
Click to expand...
Click to collapse
Can you post the out put of
Code:
fastboot getvar all
Please edit out serial + imei before posting thanks.
You will need s-off to go back to stock 100% with LOCKED bootloader, but if you just want ota's that's possible with s-on you just need Stock recovery and Rom. But best you'll get the bootloader is RELOCKED with s-on.
Also it won't boot custom software when relocked. That's why your recovery and Rom won't boot
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Can you post the out put of
Code:
fastboot getvar all
Click to expand...
Click to collapse
Sure thing:
>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 1.00.20.0913_3
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3837mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.092s
Click to expand...
Click to collapse
markushendrich said:
Sure thing:
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/guru_reset_m7_sprint_3-04-651-2-zip/
Unlock your bootloader, and use CWM to install this Rom. In Aroma installer choose YES to Stock Recovery and Radio. NO to Root.
Reboot the phone to take ota's after you've updated relock the bootloader .
I notice the version main is missing from your getvar also. Installing the ota's may fix it but I should be able to help you with that before you do anything else. It will require the bootloader to be relocked so better to do it now if you want to.
---------- Post added at 09:18 PM ---------- Previous post was at 09:07 PM ----------
Actually it would be better to unlock, flash the Rom first then relock and flash the firmware to restore the version main.
Then reboot and your done
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/651/
You can get the firmware here. Download it and rename the file to firmware.zip and put it in your fastboot folder. Then after unlocking and flashing the reset.zip. relock and flash the firmware.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
Code:
fastboot oem lock
Code:
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
< --- case sensitive.
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
You should now see your new firmware version main in the bootloader and getvar. And that's it reboot and take ota's.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Then after unlocking and flashing the reset.zip
Click to expand...
Click to collapse
Wait what? Can you explain this reset.zip? Or you copied and pasted the above from somewhere else and that step does not apply to me?
markushendrich said:
Wait what? Can you explain this reset.zip?
Click to expand...
Click to collapse
The reset zip will restore your stock Rom and recovery and Radio. But you have to Install it with a custom recovery like CWM or TWRP. Which requires the bootloader to be unlocked. Once it's installed you can take ota updates. The bootloader does not need to be locked for ota's.
Then you can relock and flash the firmware.zip which will restore your version main information. Which is missing. Caused by a recovery bug that wipes that info from the misc partition. Installing the ota updates may fix it. Or you can manually flash the firmware to fix it before you take the ota updates. :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
The reset zip will restore your stock Rom and recovery and Radio. But you have to Install it with a custom recovery like CWM or TWRP. Which requires the bootloader to be unlocked. Once it's installed you can take ota updates. The bootloader does not need to be locked for ota's.
Then you can relock and flash the firmware.zip which will restore your version main information. Which is missing. Caused by a recovery bug that wipes that info from the misc partition. Installing the ota updates may fix it. Or you can manually flash the firmware to fix it before you take the ota updates. :good:
Click to expand...
Click to collapse
Oh sorry when you said reset.zip I thought it was something totally new but you were referring to "Guru_Reset_M7_Sprint_3.04.651.2.zip". My bad.
So I followed the steps above including flashing firmware.zip. Now fastboot getvar all shows main having a version. Currently apps are being downloaded, and I will try to install the ota update after they are all done. And there is stock recovery, I confirmed by launching into recovery from fastboot after flashing "Guru_Reset_M7_Sprint_3.04.651.2.zip" in CWM, and the orange triangle with exclamation point showed up.
Thank you for helping me out!
Also one last thing, to clean everything up, how do I reset the tampered flag? And so it shows locked instead of relocked?
EDIT: First OTA was successful!
markushendrich said:
Also one last thing, to clean everything up, how do I reset the tampered flag? And so it shows locked instead of relocked?
Click to expand...
Click to collapse
For that you need s-off and this guide
http://forum.xda-developers.com/showthread.php?t=2541082
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
For that you need s-off and this guide
http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Will I lose my current progress with that guide?
markushendrich said:
Will I lose my current progress with that guide?
Click to expand...
Click to collapse
You will have to downgrade the phone again yes. And s-off is not so easy to accomplish. Unless you pay $25 for Sunshine app.
If you wanted to return it for warranty or sell the device as un-tampered stock. You can use firewater for or rumrunner to s-off both methods are free exploits but are not so simple to get them to work you will need to unlock flash a custom recovery make a nandroid of the stock rom, then root the device again. Probably need to flash a few different roms + Kernels to find something that works.
There's the possibility that neither will work and your only choice then would be Sunshine.
If there's no warranty and your friend just wants stock with ota updates I would just leave it as relocked unless your prepared to put the work in
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
There's the possibility that neither will work and your only choice then would be Sunshine.
If there's no warranty and your friend just wants stock with ota updates I would just leave it as relocked unless your prepared to put the work in
Click to expand...
Click to collapse
I'm not sure about the warranty, but I will leave it as is since it sounds like a headache and I really want to get back to my phone, and flash the new android 5.0 preview to my Nexus
Thank you so much for helping me out, you have good knowledge of this device!
markushendrich said:
I'm not sure about the warranty, but I will leave it as is since it sounds like a headache and I really want to get back to my phone, and flash the new android 5.0 preview to my Nexus
Thank you so much for helping me out, you have good knowledge of this device!
Click to expand...
Click to collapse
Your welcome, glad you got it sorted :good:
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Hi Guys,
Bought an m7 cheap on ebay. I don't know anything about the history, except to say it's been fiddled with...
It powers up but it won't boot up; it hangs on the HTC logo.
Bootloader's unlocked, it's been rooted... S-ON
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ** edited out **
(bootloader) imei: ** edited out **
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm thinking I should try and take it back to stock, but I don't know where I should go from here and I'm worried I might screw it up.
Any help would be greatly appreciated
Thanks in advance!
Go to RUU mode and flash an RUU. There's a lot of threads explaining how to go to back to stock on this forum. If it still doesn't work, it might be an internal issue like the motherboard.
Can someone please recommend an RUU to go to... I'm just worried if I use the wrong one it will cause more issues. I thought RUUs were dependent on the CID num and as that's been changed to allow custom roms... I'd be happy taking it back to a plain old vanilla HTC / Google - just something to get it back alive.
Thanks
Should also add I can't get s-off... adb devices doesn't show anything... I'm guessing usb debugging wasn't set up
mdb said:
Can someone please recommend an RUU to go to... I'm just worried if I use the wrong one it will cause more issues. I thought RUUs were dependent on the CID num and as that's been changed to allow custom roms... I'd be happy taking it back to a plain old vanilla HTC / Google - just something to get it back alive.
Click to expand...
Click to collapse
There is no ruu we can recommend because your version-main is blank the fact that you also have superCID doesn't help identifying which ruu you'll need to use.
mdb said:
Should also add I can't get s-off... adb devices doesn't show anything... I'm guessing usb debugging wasn't set up
Click to expand...
Click to collapse
You'll have to unlock the bootloader, flash a custom recovery (twrp preferred), flash a rom and use your phone like that or, if you want, from there you will be able to achieve s-off again and convert your phone to wherever you want (Stock Sense or stock GPE) by flashing a RUU.
alray said:
There is no ruu we can recommend because your version-main is blank the fact that you also have superCID doesn't help identifying which ruu you'll need to use.
You'll have to unlock the bootloader, flash a custom recovery (twrp preferred), flash a rom and use your phone like that or, if you want, from there you will be able to achieve s-off again and convert your phone to wherever you want (Stock Sense or stock GPE) by flashing a RUU.
Click to expand...
Click to collapse
Thanks so much for this... I've been learning more all day (traditionally an iOS guy)...
Am I right in thinking I would need to sideload a custom rom through twrp and then install it? If so, I'm having an issue getting my laptop to talk to the phone - "adb devices" is pretty flakey to say the least, sometimes it works sometimes it doesn't... I've read various things about Windows 8 and that adb works best on Windows 7, can you please confirm I'm on the right track here. I'd like to put the Viper rom on it.
Thanks again
In order to flash custom recovery you need to be booted to bootloader menu, and use fastboot commands. If you flash TWRP 2.8.6.0 or later, there's no need to sideload a ROM because newer TWRP recoveries have MTP option, so you use that. Try to go to bootloader, connect your phone to your laptop or PC, and issue a command fastboot devices. If it shows your phone, you're good to go
Thanks donkeyking1...
I got it working eventually, I needed to install new drivers for Windows 8 then adb started behaving properly. I ended up pushing the Viper ROM to the phone... The phone's alive now but currently it has no IMEI, baseband or OS - they're all blank. I'm wondering if it's because I've installed Viper 9 without upgrading the firmware first? My next goals are to try and S-OFF the device so I can install a stock rom, at which point hopefully I'll get OTA updates and then go back to Viper 9 - it looks great, I just can't use it! - no phone signal!
Does that sound like the right approach? I'm trying to flash different custom roms to hopefully find one that works with rumrunner. I've read that some folks have managed to S-OFF on hboot 1.57 with rumrunner, but it's picky on the rom that's installed. It doesn't work on Viper 9...
If anyone can add any help it would be much appreciated!
Thanks in advance
mdb said:
Thanks donkeyking1...
I got it working eventually, I needed to install new drivers for Windows 8 then adb started behaving properly. I ended up pushing the Viper ROM to the phone... The phone's alive now but currently it has no IMEI, baseband or OS - they're all blank. I'm wondering if it's because I've installed Viper 9 without upgrading the firmware first? My next goals are to try and S-OFF the device so I can install a stock rom, at which point hopefully I'll get OTA updates and then go back to Viper 9 - it looks great, I just can't use it! - no phone signal!
Does that sound like the right approach? I'm trying to flash different custom roms to hopefully find one that works with rumrunner. I've read that some folks have managed to S-OFF on hboot 1.57 with rumrunner, but it's picky on the rom that's installed. It doesn't work on Viper 9...
If anyone can add any help it would be much appreciated!
Thanks in advance
Click to expand...
Click to collapse
flash the 7.19.401.2 firmware and then the 7.19.401.2 RUU. If you still have imei problem after that, its most likely an hardware defect.
relock your bootloader if not already locked or re-locked:
Code:
fastboot oem lock
Code:
fastboot orm rebootRUU
fastboot flash zip M7_UL_Firmware_7.19.401.2.zip
fastbppt flash zip M7_UL_Firmware_7.19.401.2.zip
fastboot reboot-bootloader
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
fastboot reboot
*** use htc_fastboot.exe for flashing the ruu (linked below). Save all files in the same folder where you already have fastboot.exe and adb.exe on your computer.
M7_UL_Firmware_7.19.401.2.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
htc_fastboot.exe
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
mdb said:
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
Click to expand...
Click to collapse
To flash a ruu on a s-on phone there are many prerequisites:
The RUU must match your MID: 7.19.401.2 is for PN0710000
The RUU must match your CID: You have superCID so its not a problem.
The RUU must be the same version or an upgrade from your actual version, we don't know your actual version because of your blank versio-main but you have 1.57 hboot which suggest a 6.xx.xxx.x version. So 7.19.401.2 should be an upgrade.
The bootloader must be locked or re-locked.
There is no risk trying it, the worst that can happen is that the phone won't accept the ruu and nothing will be flashed.
mdb said:
Alray, just curious (still learning ), how do you know from the info I've given you that the firmware / RUU you've suggested is one to fix the issues - I've struggled to understand this the past few days - thanks!
Click to expand...
Click to collapse
Super CID + your MID. WWE firmware should work just fine. Right @alray?
donkeykong1 said:
Super CID + your MID. WWE firmware should work just fine. Right @alray?
Click to expand...
Click to collapse
:good:
Well, thanks so much for your help guys, but alas it seems the phone is k-put... Flashed the firmware and the rom no problem.... but it still shows no IMEI / IMEI SV / IMSI and it can't recognise the phone number - I'm guessing it can't read the sim. It does show the OS and IMEI in the bootloader, but once booted it's a no go.
mdb said:
Well, thanks so much for your help guys, but alas it seems the phone is k-put... Flashed the firmware and the rom no problem.... but it still shows no IMEI / IMEI SV / IMSI and it can't recognise the phone number - I'm guessing it can't read the sim. It does show the OS and IMEI in the bootloader, but once booted it's a no go.
Click to expand...
Click to collapse
Try to bend your sim tray just a little bit. Maybe your sim card is not reaching the contacts inside the phone. Or put a piece of paper under the sim and see what happens
Thanks donkeykong1, I've tried but it's not working... The fact the IMEI / IMEI SV and baseband are unknown though... they're not sim related...
It does show the baseband and IMEI in fastboot getvar all though?...
There were a lot of people with that same issue, and their phones worked fine, so I doubt it has anything to do with your sim. Your sim works in another phone?
Yeah, the sim's fine. @alray said it's likely a hardware issue if the firmware / rom didn't repair the IMEI issue, and the other threads I've looked at with the same issue are all saying the motherboard's faulty.
Although I am baffled as to why it is showing the IMEI / baseband in the bootloader, in fastboot etc. but not once the phone has booted up?...
I read on another thread (http://forum.xda-developers.com/showthread.php?t=2253514) that maybe flashing a kernal and/or radio might solve it?
Just wondering whether I should try flashing an official HTC rom? I've been in touch with the guy I got it off and he said it was originally on Orange, UK:
http://www.htcdev.com/devcenter/downloads > One M7 / v5.0.2 > Find Files : Page 6
One M7 / Orange / UK / CRC / 3.4.10 / v5.0.2 / 539.0 MB / 7.19.61.10
Was also thinking of...
http://www.htcdev.com/devcenter/downloads > One M7 / v5.0.2 > Find Files : Page 1
One M7 / HTC / EU / MR 3 / 3.4.10 / v5.0.2 / 486.0 MB / 7.19.401.22
If I did that would I need to update the firmware first like you advised originally @alray?
If I know I can revive the IMEI etc. I'll be happy to go ahead and pay to S-OFF
Thanks in advance
You need a kernel to match your firmware. If you're on 7.19.401.2, then you need 7.19.401.2 kernel. I can give you boot.img, but I don't have the whole zip, with modules. Then again, if your phone boots fine, maybe boot.img will help. I'd [email protected] to confirm my thoughts though. He's much more into this than I am