Database Develop

[Q] No S-OFF methods working

I am trying to S-OFF my HTC One and I am running into lots of issues. I've tried revone and moonshine but they both fail. I already got it unlocked with htcdev. Rooting and installing CWM went smoothly.
Info:
HBOOT 1.44.0000
I have Ubuntu 12.10 and adb version 1.0.31
revone -P fails with error -6. I have tried terminal emulator and adb shell.
moonshine fails with a strange error at the 10th step:
Moonshining(10)........................"Error: Don't drink and shine!"
I'm kinda stuck here...Any ideas?

My experience with revone was to keep on trying and after about 20 attempts it suddenly worked.

I literally tried "./revone -P" 50 times and it failed with error code -6 each time.

Revone will work fine with 1.44 hboot.
So try and re-try.
Maybe lock the bootloader and retry

It tooks 3 hours for me repeating revone command until it worked.
What firmware date you have on boot screen?
Mike

Hi,
You can try this method: [GUIDE] S-Off without PC.
It worked for me on two One's at the first try with no issues...

Julian90090 said:
I am trying to S-OFF my HTC One and I am running into lots of issues. I've tried revone and moonshine but they both fail. I already got it unlocked with htcdev. Rooting and installing CWM went smoothly.
Info:
HBOOT 1.44.0000
I have Ubuntu 12.10 and adb version 1.0.31
revone -P fails with error -6. I have tried terminal emulator and adb shell.
moonshine fails with a strange error at the 10th step:
Moonshining(10)........................"Error: Don't drink and shine!"
I'm kinda stuck here...Any ideas?
Click to expand...
Click to collapse
My idea, if it's possible on ubuntu, is to run parallel desktop, install Windows, download an all in one toolkit (Hasoon2000, etc.) and let the program flash it for you. Or, however you can get the toolkit to run. I did exactly this with my mac and my phone is unlocked, s-off, rooted and running perfectly. I do, however, have the developer edition, so my bootloader was already unlocked, but the rest the toolkit took care of. After all of your trying, maybe this is the way to go, so you can relax a little from it. Hope this helps.
-Mike

Guich said:
Revone will work fine with 1.44 hboot.
So try and re-try.
Maybe lock the bootloader and retry
Click to expand...
Click to collapse
Unless he has a US model with an updated hboot dated after May.

Julian90090 said:
I am trying to S-OFF my HTC One and I am running into lots of issues. I've tried revone and moonshine but they both fail. I already got it unlocked with htcdev. Rooting and installing CWM went smoothly.
Info:
HBOOT 1.44.0000
I have Ubuntu 12.10 and adb version 1.0.31
revone -P fails with error -6. I have tried terminal emulator and adb shell.
moonshine fails with a strange error at the 10th step:
Moonshining(10)........................"Error: Don't drink and shine!"
I'm kinda stuck here...Any ideas?
Click to expand...
Click to collapse
You may have the patched 1.44, in which case s-off won't work. Check the date of your hboot in bootloader, if it's the July release then it's been patched.
Sent from my HTC One using xda app-developers app

nkk71 said:
You may have the patched 1.44, in which case s-off won't work. Check the date of your hboot in bootloader, if it's the July release then it's been patched.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Correct, May 2013 HBoot 1.44 is okay but if you're on 1.44 June 2013 or later then you're out of luck.

It looks like I have the June 2013 patched HBOOT. Ugh hopefully a new exploit will be found.

Julian90090 said:
It looks like I have the June 2013 patched HBOOT. Ugh hopefully a new exploit will be found.
Click to expand...
Click to collapse
I had never heard of different versions of hboot 1.44.
However, will it let you fastboot flash an earlier dated 1.44 hboot .
I know if you're on for example 1.54 it won't let you downgrade hboot, but does it check for version number or date when determining whether to allow to flash .
May be worth a try
Sent from my HTC One using xda app-developers app

paul_59 said:
I had never heard of different versions of hboot 1.44.
However, will it let you fastboot flash an earlier dated 1.44 hboot .
I know if you're on for example 1.54 it won't let you downgrade hboot, but does it check for version number or date when determining whether to allow to flash .
May be worth a try
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Do you have a link to the older dated HBOOT? I can't seem to find one. Would you use fastboot to flash it?

Julian90090 said:
Do you have a link to the older dated HBOOT? I can't seem to find one. Would you use fastboot to flash it?
Click to expand...
Click to collapse
I don't think that will work, as it's been asked several times on the S-Off thread. It does mention somewhere that a few ATT users were able to restore an older OTA, but I can't confirm that. Most people with 1.54 or the patched 1.44 were not able to achieve s-off.
Don't have a link to the particular instructions, but it was discussed on the s-off thread somewhere: http://forum.xda-developers.com/showthread.php?t=2314582
Good luck
EDIT: here's the ATT downgrade thread http://forum.xda-developers.com/showthread.php?t=2394155

Julian90090 said:
Do you have a link to the older dated HBOOT? I can't seem to find one. Would you use fastboot to flash it?
Click to expand...
Click to collapse
I have uploaded to my dropbox
http://db.tt/gfbzlX26
hboot_1.44_Apr2013.zip
Guide flash hboot.txt
http://db.tt/rRjJ2ebS
Sent from my HTC One using xda app-developers app

Getting this error when I try to flash the older HBOOT:
Code:
[email protected]:~/Downloads$ adb reboot bootloader
[email protected]:~/Downloads$ 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 device))
finished. total time: 6.159s
[email protected]:~/Downloads$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.039s]
finished. total time: 0.039s
[email protected]:~/Downloads$ fastboot flash zip hboot_1.44_apr2013.zip
< waiting for device >
sending 'zip' (2048 KB)...
OKAY [ 0.432s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.652s

I didn't suggest using oem relock .
Could you fastboot getvar all
Then post the output here please
Sent from my HTC One using xda app-developers app

paul_59 said:
I didn't suggest using oem relock .
Could you fastboot getvar all
Then post the output here please
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I tried it without using OEM relock and it still didn't work. I had heard that you have to be locked in order to flash HBOOT.
What happened without using oem relock:
Code:
[email protected]:~$ adb reboot bootloader
[email protected]:~$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.040s]
finished. total time: 0.040s
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ fastboot flash zip hboot_1.44_apr2013.zip
sending 'zip' (2048 KB)...
OKAY [ 0.431s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 0.672s
Heres the output of fastboot getvar all:
Code:
[email protected]:~/Downloads$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37RW900975
(bootloader) imei: XXXXXXXXXXXXXXX // i don't want to share my IMEI
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4173mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.039s
Hopefully this helps....

Julian90090 said:
I tried it without using OEM relock and it still didn't work. I had heard that you have to be locked in order to flash HBOOT.
Click to expand...
Click to collapse
You only need to relock to run a RUU when s-on. Has nothing to do with what you're trying to do here.

iElvis said:
You only need to relock to run a RUU when s-on. Has nothing to do with what you're trying to do here.
Click to expand...
Click to collapse
I am S-ON trying to get S-OFF. I heard in order to flash an RUU Zip I had to have a locked bootloader.
I had originally tried flashing the zip with an unlocked bootloader, then I proceeded to try it work a locked bootloader because it didn't work.

[Q] HTC One relocked after firmware updated now soft-bricked and unable to unlock!

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

[Q]can't unlock bootloader GPe 4.4.2

It seems as if Google removed the option to unlock the bootloader on KitKat (4.4.2). Now the command "fastboot oem unlock" fails with an error and the htcdev token method does not work on GPe. Are we out of luck? Is there another way to unlock the bootloader?
C:\Minimal ADB and Fastboot>adb devices
List of devices attached
HT36Jxxxxxxx device
C:\Minimal ADB and Fastboot>adb reboot bootloader
C:\Minimal ADB and Fastboot>fastboot oem unlock
...
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.608s]
finished. total time: 0.608s
Here is my getvar all info
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.094s

Is this a GPE conversion or a genuine GPE device?

cschmitt said:
Is this a GPE conversion or a genuine GPE device?
Click to expand...
Click to collapse
Genuine GPE. Never been tampered with.

I am experiencing the same issue
cschmitt said:
Is this a GPE conversion or a genuine GPE device?
Click to expand...
Click to collapse
I am also experiencing the same "Loading custom splash failed" issue. Mine is a genuine HTC One Google Play Edition that has been updated to 4.4.2 over the air. It has never been unlocked or rooted.

applsplatz said:
I am also experiencing the same "Loading custom splash failed" issue. Mine is a genuine HTC One Google Play Edition that has been updated to 4.4.2 over the air. It has never been unlocked or rooted.
Click to expand...
Click to collapse
You are not the only one having this issue. Many other GPE owners on 4.4.2 are facing the same problem.

Waiting4MyAndroid said:
You are not the only one having this issue. Many other GPE owners on 4.4.2 are facing the same problem.
Click to expand...
Click to collapse
This is an interesting problem.
The error:
Code:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
is occurring while hboot is attempting to read the unlock splash image from pg2fs (mmcblk0p7) -- this is where the pg2fs_spcustom.img found in RUU's is written.
The traverse offset is 0x839, or the 0x840th 16-byte page in the partition. If you dump p7 using dd and check address 0x8400 it starts with 'HTCCUSSP', which is the header for the beginning of the unlock splash image.
Basically, hboot is saying that the read failed for some reason.
What doesn't make sense is that GPE users on 4.3 are able to fastboot oem unlock, but on 4.4.2 they aren't, yet the 4.4.2 OTA firmware.zip for 3.62.1700.1 only contains hboot (1.54.0000), boot, recovery, and rpm. It doesn't contain the pg2fs_spcustom.img, so how could it get changed or corrupted?
Also, the GPE 1.54.0000 hboot works fine to fastboot oem unlock on other devices. I have an AT&T One, flashed the 3.58.1700.1 firmware, then the 3.62.1700.1 firmware, locked the bootloader, and then did a fastboot oem unlock and the unlock splash screen popped right up.
I'd be interested to hear from GPE owners as to which OS version the unlock works and which it does not, and also collect a couple of mmcblk0p7 images from GPE owners on 4.2.2, 4.3, and 4.4.2 for comparison.
To dump mmcblk0p7:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7.bin
exit
exit
adb pull /sdcard/mmcblk0p7.bin
Then zip it up and post in this thread (it zips to under 100KB.)
Maybe we arrive at some solution for this.

cschmitt said:
This is an interesting problem.
The error:
Code:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
is occurring while hboot is attempting to read the unlock splash image from pg2fs (mmcblk0p7) -- this is where the pg2fs_spcustom.img found in RUU's is written.
The traverse offset is 0x839, or the 0x840th 16-byte page in the partition. If you dump p7 using dd and check address 0x8400 it starts with 'HTCCUSSP', which is the header for the beginning of the unlock splash image.
Basically, hboot is saying that the read failed for some reason.
What doesn't make sense is that GPE users on 4.3 are able to fastboot oem unlock, but on 4.4.2 they aren't, yet the 4.4.2 OTA firmware.zip for 3.62.1700.1 only contains hboot (1.54.0000), boot, recovery, and rpm. It doesn't contain the pg2fs_spcustom.img, so how could it get changed or corrupted?
Also, the GPE 1.54.0000 hboot works fine to fastboot oem unlock on other devices. I have an AT&T One, flashed the 3.58.1700.1 firmware, then the 3.62.1700.1 firmware, locked the bootloader, and then did a fastboot oem unlock and the unlock splash screen popped right up.
I'd be interested to hear from GPE owners as to which OS version the unlock works and which it does not, and also collect a couple of mmcblk0p7 images from GPE owners on 4.2.2, 4.3, and 4.4.2 for comparison.
To dump mmcblk0p7:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7.bin
exit
exit
adb pull /sdcard/mmcblk0p7.bin
Then zip it up and post in this thread (it zips to under 100KB.)
Maybe we arrive at some solution for this.
Click to expand...
Click to collapse
Thank you for the detailed response. Is there a way to dump mmcblk0p7 without SU access? My phone is unrooted and S-ON.

Waiting4MyAndroid said:
Thank you for the detailed response. Is there a way to dump mmcblk0p7 without SU access? My phone is unrooted and S-ON.
Click to expand...
Click to collapse
Hmm, not that I'm aware of.

Waiting4MyAndroid said:
Thank you for the detailed response. Is there a way to dump mmcblk0p7 without SU access? My phone is unrooted and S-ON.
Click to expand...
Click to collapse
cschmitt said:
Hmm, not that I'm aware of.
Click to expand...
Click to collapse
you can try firewater temproot exploit, but i dont think it'll help much... GPE "fastboot oem unlock" no longer works

Im also having this issue. Is there anything that we can make this progress? I haved check all over the internet and there is not many people talking about this issue

cruel91 said:
Im also having this issue. Is there anything that we can make this progress? I haved check all over the internet and there is not many people talking about this issue
Click to expand...
Click to collapse
I read on another thread about someone calling Google support and was told a patch is in the works to fix this bug in kitkat. Google is aware of the problem.
**Edit**
Here is the link http://forum.xda-developers.com/showthread.php?t=2547894&page=2
Sent from my HTC One using xda app-developers app

@nkk71 I've been looking into this today.
Flashed a 1.54 GPE hboot (Aug 13th version), did an oem relock, rebooted to bootloader, then oem unlock. Unlock splash appeared, but I selected 'no' as I didn't want to wipe my device. (since I'm still s-off I use revone to unlock if needed.)
As device was rebooting I held volume down to reenter bootloader, but screen remained blank. So I issued oem readcid (still connected to usb) to check it it was alive. Crazy thing, it reported cid as 11111111, but my cid is actually set to BS_US001!
Next did fastboot reboot-bootloader, this time display is on, cid displays BS_US001 but mainver is now blank on both display and in getvar all.
Soo. Something weird happened while attempting to unlock on this hboot (or during following reboot ) that basically wiped the first few hundred bytes of p19 where current cid and mainver are stored.
I had to reflash firmware to get mainver back.
Just sharing this because maybe the attempted unlock is causing the corruption leading to the active command line overflow issue.

cschmitt said:
@nkk71 I've been looking into this today.
Flashed a 1.54 GPE hboot (Aug 13th version), did an oem relock, rebooted to bootloader, then oem unlock. Unlock splash appeared, but I selected 'no' as I didn't want to wipe my device. (since I'm still s-off I use revone to unlock if needed.)
As device was rebooting I held volume down to reenter bootloader, but screen remained blank. So I issued oem readcid (still connected to usb) to check it it was alive. Crazy thing, it reported cid as 11111111, but my cid is actually set to BS_US001!
Next did fastboot reboot-bootloader, this time display is on, cid displays BS_US001 but mainver is now blank on both display and in getvar all.
Soo. Something weird happened while attempting to unlock on this hboot (or during following reboot ) that basically wiped the first few hundred bytes of p19 where current cid and mainver are stored.
I had to reflash firmware to get mainver back.
Just sharing this because maybe the attempted unlock is causing the corruption leading to the active command line overflow issue.
Click to expand...
Click to collapse
Thanks for the info;
interesting about the CID, the one being read by fastboot is actually stored in p4 and p5 (one possibly being a backup for the other?)... maybe when bootloader got stuck, it automatically activated SuperCID as a "safety measure"??
as for the missing version-main, this has happened a lot (and for countless reasons, and pretty much with little consistency)... but those never resulted in the Active cmdline overflow. so i don't think p19 would be the cause of that.
still all of it is very strange.

This is really irritating. I don't think I'm ever going to buy a Google Edition phone again! How am I supposed to sell this phone on eBay when it's in a half-working condition, sure it works and runs the latest version of Android, but anyone interested in buying this phone will want to unlock it as soon as they get it and when it gives them this error...they are going to be hunting me down questioning me why it can't be unlocked or rooted...

sionicion said:
This is really irritating. I don't think I'm ever going to buy a Google Edition phone again! How am I supposed to sell this phone on eBay when it's in a half-working condition, sure it works and runs the latest version of Android, but anyone interested in buying this phone will want to unlock it as soon as they get it and when it gives them this error...they are going to be hunting me down questioning me why it can't be unlocked or rooted...
Click to expand...
Click to collapse
I am contacting both Google and HTC support. Please check my post here. You can contribute by sending new support case about this issue. They would hear us
http://forum.xda-developers.com/showthread.php?t=2547894
Sent from my HTC One using Tapatalk

Does GPE 5.1 solved the problem ?

imadsaber said:
Does GPE 5.1 solved the problem ?
Click to expand...
Click to collapse
We don't know yet. I am still waiting for the OTA. I will attempt to unlock bootloader right after installing the OTA. Will report back soon. Fingers crossed.

Lollipop OTA did not fix the problem. Still getting same error when attempting to unlock the bootloader. That is so [email protected]#ked up!

if any one know anything please tell us ! thank you

Waiting4MyAndroid said:
Lollipop OTA did not fix the problem. Still getting same error when attempting to unlock the bootloader. That is so [email protected]#ked up!
Click to expand...
Click to collapse
Oh noooooooooo :'(

[Q] Unbricking Phone- Pleading for help.

Sprint US model. was S-On (and never ever changed. still is) Phone was rooted with CWM recovery. I decided to take it back to it's out of the box condition (unroot, lock, stock FW, etc) using the same all in one tool I used so easily before.
1. I used the superuser app to remove it's root permissions and uninstall itself.
2. Using the "One M8 All In One Toolkit v.2.x" I locked the boot loader. In adb it displayed the following....
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(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 = -1610744452 (0x9FFDFD7C)
(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 (Unknown error))
finished. total time: 1.249s​
So that seemed to work fine as when in the bootloader it stated it was relocked.
3. Next I used the same program to flash the stock RUU (which I believed due to matching model and version #'s as was existing on my phone. ) However this process failed.
...
(bootloader) Start Verify: 3
OKAY [ 0.016s]
finished. total time: 0.016s​
At this point it prompted to select my file. I selected my stock firmware 2.16.651.4 (which was verified as correct version.) and selected ok. adb window then showed this.....
target reported max download size of 1826418688 bytes
sending 'zip' (39248 KB)...
OKAY [ 2.436s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.189s​
I then tried this same process with a newer stock firmware 3.30.651.2 and that succeeded to a certain point. It changed from the Grey HTC logo to one with a progress bar, going through a few steps but failed giving a similar permissions error. Went back it into boot loader and saw it did do a partial flash as the hboot now said 3.19 vs 2.16 as before. as not the hboot and ver. are that of the second try.
And this is where I stand stuck at this spot, and when trying a normal boot of phone it never loads ROM and just stays on the screen with the green HTC logo w/ white background. I have pondered, read every page I could find everywhere on XDA forums and after several days of trying to figure this out, I am fatigued beyond belief with this stupid phone and have all but given up. I have absolutely no answers or clues to why this is happening much less how to go about fixing it. Desperately seeking any answers from anyone who can guide me to get it back operational. For now it's become a $600 paper weight. :confused :crying:

Get rid of the toolkit and run the RUU as an exe

Unbricking Phone- Pleading for help.
BD619 said:
Get rid of the toolkit and run the RUU as an exe
Click to expand...
Click to collapse
I tried that. Both with HTC and a generic exe And they both failed. (those were stock w/ root).
Where Can I get the FULL stock no root, etc RRU.exe I found nothing but zip files. for 2.16.651.4 and 3.30.651.2

cbandchikin said:
I tried that. Both with HTC and a generic exe And they both fail.
Click to expand...
Click to collapse
Is there an error when they fail?

cbandchikin said:
I tried that. Both with HTC and a generic exe And they both failed. (those were stock w/ root).
Where Can I get the FULL stock no root, etc RRU.exe I found nothing but zip files. for 2.16.651.4 and 3.30.651.2
Click to expand...
Click to collapse
Links to the official HTC RUU's can be found in the link below, in the first post.
http://forum.xda-developers.com/showthread.php?t=2729173
These are totally stock, without root.

Yeah as s-on it will fail to install anything modified

BD619 said:
Is there an error when they fail?
Click to expand...
Click to collapse
Im Re-downloading the RUU ( from the same place as Magnum Enforcer Links to in the next post.) When I run this I will post screenshot of error.

So Based on comments so far, to get this phone back to stock and working as it did out of box, I need to ....
1. Turn S-off and change CID to Super CID
2. Flash stock RUU
3. Change CID back to original Carrier CID and change back to S-on
4. profit
If this is the case, how do I turn S-off. As "Sunshine" (the only thing I've found that does this) is an apk, and since I cant boot to ROM ..... ? If I can figure that out then I think I might be able to do the rest just fine.

You don't need SuperCID to run a RUU

Magnum_Enforcer said:
You don't need SuperCID to run a RUU
Click to expand...
Click to collapse
So I ran the RUU I redownloaded. I was taking screenshots everytime there was a change in the status, waiting for it to error like it did last time and wouldn't you know it went through the entire process without error and now the phone is bad to it's old self. This is the exact things I've been doing with no positive results. Could I have managed SOMEHOW to ended up downloading the wrong RUU? I compared and verified the successful RRU with the 1st one I tried and they are indeed the exact same version. So that wasn't it.
and yes I did this all with S-On. At no point was it ever S-Off. Bootloader showed modified. Apparently you dont need S-off to run HTC's Stock RUU. My only guess is that during this troubleshooting the bootloader was showing "Tampered" (as expected) once that changed to modified, then it was able to run successfully.

Apparently you don't need S-off to run HTC's Stock RUU
Click to expand...
Click to collapse
Our phones come S-ON so why would it need to be S-OFF to RUU.

I don't trust ruu exec , flash the firmware manually in the ruu mode, should work even if s-on as long as you are flashing the correct version(sometimes it asks you to repeat flashing and you have to do it again)
Then flash recovery in fastboot, then ur good to flash anything in the recovery.
And don't worry as long you can boot into the bootloader your phone isn't bricked (at least 90% of the time)

HTC One M7 - can not update to android 5.

Hello everyone
First of all sorry for my english. I'm not a native english so please forgive me if I say something wrong. Second - this is my first thread here (since now, reading informations from here was enough to handle all of my problems but at this moment well... I surrender and need some advice) so please be understanding.
I have a problem with HTC M7. My friend gave it to me for a little hardware fix and software update. I fixed the hardware but I'm stuck on firmware update.
I wanted to update firmware to 5.05.651.2 with automatic updates but it crashes somewhere in the middle with red triangle sign.
So I started to read. First I've read that I need to unlock bootloader, so I made it with fastboot - nothing changed. Later found some info that I need a stock firmware to enable updates. So I downloaded some firmware but failed to install it (tried with fastboot). Next info I found that to install stock firmware I need to root the device. So I've rooted it. Still nothing. Trying to flash in "rebootRUU" mode with fastboot gave me info that no "android-info.txt" was found. Some more reading and searching and I've noticed that my HTC is probably Sprint version (to be honest I do not know what is the difference). So I downloaded some Sprint firmware. Still no effect... Ehh I'm depressed and I'm begging for help:crying:
So at this moment I have:
Android ver. 4.4.2
HTC Sense ver. 6.0
Software ver. 5.03.651.3
Kernel ver. 3.4.10-gf22c859
(translated from Polish menu)
Info from bootloader:
*** RELOCKED ***
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HBOOT - 1.44.0000
RADIO-1.00.31.0603
OpenDSP-v31.120.274.0617
eMMC-BOOT
Jul 5 2013, 17:19:22:3
Custom recovery installed from file: openrecovery-twrp-2.5.0.0-m7wls
Root made with iRoot app.
Also I don't know if it was earlier, but now lockscreen on android is in Chinese while all the rest is in Polish :/
Maybe it's important - friend told me that phone is from Shanghai (I don't know where does he have that info from).
If any additional information is needed please write and I will post it asap.
What I would like to achieve? I would like to install latest available stock firmware (without any changes, cool apps or any additional software). Just an basic android with Google store available. My friend is not advanced android user. He just want latest software.
I would probably fight with this device more but also a big problem are dead links all over the forums (htc1guru etc). I'm counting that maybe some of you here have backups of roms. Or maybe I just don't know how to find a proper one.
Full step-by-step manual what should I do would be great but of course I appreciate any other suggestions or advice. Just need some help.
(one more thing - for those who want to write "use search, there are a lot of manuals on the web, we won't make it for you etc" please, I spent couple of hours searching and reading and I don't understand or I don't know how to use info's I found. I'm not an Android user for last couple of years)
Thank you in advance for any help

See comment in red below
qwe1234 said:
Hello everyone
First of all sorry for my english. I'm not a native english so please forgive me if I say something wrong. Second - this is my first thread here (since now, reading informations from here was enough to handle all of my problems but at this moment well... I surrender and need some advice) so please be understanding.
I have a problem with HTC M7. My friend gave it to me for a little hardware fix and software update. I fixed the hardware but I'm stuck on firmware update.
I wanted to update firmware to 5.05.651.2 with automatic updates but it crashes somewhere in the middle with red triangle sign. Indicating that your software partition isn't 100% stock. The ota update will only replace the required files to be updated, not the whole system. Before updating, the updater-script check integrity of all files to be updated. If only one of these file isn't as expected, the updater-script will abort and the update will not install ----> red triangle
So I started to read. First I've read that I need to unlock bootloader bootloader lock/unlock status isn't related to ota update, so I made it with fastboot - nothing changed. Later found some info that I need a stock firmware to enable updates. So I downloaded some firmware but failed to install it (tried with fastboot). Next info I found that to install stock firmware I need to root the device You don't need root to install firmware. So I've rooted it. Still nothing. Trying to flash in "rebootRUU" mode with fastboot gave me info that no "android-info.txt" was found indicating that you are not using the correct file. Some more reading and searching and I've noticed that my HTC is probably Sprint version (to be honest I do not know what is the difference The sprint variant is a CDMA phone). So I downloaded some Sprint firmware. Still no effect... Ehh I'm depressed and I'm begging for help:crying:
So at this moment I have:
Android ver. 4.4.2
HTC Sense ver. 6.0
Software ver. 5.03.651.3
Kernel ver. 3.4.10-gf22c859
(translated from Polish menu)
Info from bootloader:
*** RELOCKED ***
M7_WLS PVT SHIP S-OFF RH
CID-11111111
HBOOT - 1.44.0000 old bootloader version not matching your software version
RADIO-1.00.31.0603
OpenDSP-v31.120.274.0617
eMMC-BOOT
Jul 5 2013, 17:19:22:3
Custom recovery installed from file: openrecovery-twrp-2.5.0.0-m7wls twrp 2.5.0.0 is really outdated and won't work with recent files. Not a problem for now since you will not need to use twrp to fix it, just fyi
Root made with iRoot app.
Also I don't know if it was earlier, but now lockscreen on android is in Chinese while all the rest is in Polish :/
Maybe it's important - friend told me that phone is from Shanghai (I don't know where does he have that info from).
If any additional information is needed please write and I will post it asap.
What I would like to achieve? I would like to install latest available stock firmware (without any changes, cool apps or any additional software). Just an basic android with Google store available. My friend is not advanced android user. He just want latest software.
I would probably fight with this device more but also a big problem are dead links all over the forums (htc1guru etc). I'm counting that maybe some of you here have backups of roms. Or maybe I just don't know how to find a proper one.
Full step-by-step manual what should I do would be great but of course I appreciate any other suggestions or advice. Just need some help.
(one more thing - for those who want to write "use search, there are a lot of manuals on the web, we won't make it for you etc" please, I spent couple of hours searching and reading and I don't understand or I don't know how to use info's I found. I'm not an Android user for last couple of years)
Thank you in advance for any help
Click to expand...
Click to collapse
download these 3 files and save it in the folder where you already have fastboot.exe and adb.exe on your computer.
https://androidfilehost.com/?fid=24052804347850182
https://androidfilehost.com/?fid=24588232905725176
https://androidfilehost.com/?fid=24341993505161791
First update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot reboot-bootloader
You need to do the "fastboot flash zip" command twice. First time you'll get the "remote: 90 hboot pre-update! Please flush image again immediately" error. Second time the firmware will flash completely and should see a "OK/ flash sucessful" message. You can disregard the progress bar on the phone screen, it might not indicate 100% but if fastboot tell you "OK/ flash sucessful" it's alright
Then you can confirm everything is alright with
Code:
fastboot getvar all
your version-main should now be 6.23.651.10 and your hboot 1.61 instead of 1.44
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Make sure the phone is fully charged before doing all that and if something goes wrong post here and wait (do not skip any steps).
If everything went ok, the phone should reboot to the latest stock android version and the old twrp version replaced with the stock recovery. If the phone was sim-unlocked it might be relocked to Sprint again and you'll have to sim-unlock again (you can find the procedure in the "Sprint htc one" forum section, in the "general" sub-section.

My friend Thank You very much for all the instructions... but...
Last step:
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Click to expand...
Click to collapse
ended with error ;(
fastboot gave following:
processing file 2/5...
error: cannot load 'C:\Users\x101ch\AppData\Local\Temp\tmpp6r0paxd'
htc_fastboot finished. total time: 297.909s
Phone restarted once in the middle like you said.
I rebooted with "fastboot reboot" . Startup screen show up and now there is a black screen with dimmed backlight. Power button doesn't do anything. Any of commands in fasboot also don't work. Ahh...
One more thing. I haven't noticed that you changed command from fastboot to htc_fastboot so I changed htc_fastboot file name to just fastboot and used command fastboot. Don't know if it matters...

qwe1234 said:
I rebooted with "fastboot reboot" . Startup screen show up and now there is a black screen with dimmed backlight. Power button doesn't do anything. Any of commands in fasboot also don't work. Ahh...
Click to expand...
Click to collapse
Now you probably understand why I said
if something goes wrong post here and wait (do not skip any steps).
Click to expand...
Click to collapse
Rebooting after a failed/incomplete flash can hard brick your phone. If you can't get fastboot connectivity again, there is not much you can do. Sorry

Ahhh. My bad;( I didn't want to leave everything turned on for so many hours. Well nevermind.
What do you think if I open up the phone nad reset it manually by unplugging the battery? Is there a chance to boot it to bootloader? Like I mentioned te start screen appeared so it looks like the phone hangs later. Am I thinking right?

qwe1234 said:
Ahhh. My bad;( I didn't want to leave everything turned on for so many hours. Well nevermind.
What do you think if I open up the phone nad reset it manually by unplugging the battery? Is there a chance to boot it to bootloader? Like I mentioned te start screen appeared so it looks like the phone hangs later. Am I thinking right?
Click to expand...
Click to collapse
maybe or let the battery drain then plug the phone again and try to boot in bootloader with vol down and power.

Ok. I will try to do that tomorrow and will post the result. Thanks again

Ufff...
I'm in bootloader again.
Unplugged battery directly on mainboard and connected again rebooted the phone. So... whats next? I promise I won't do anything more without a consult

qwe1234 said:
Ufff...
I'm in bootloader again.
Unplugged battery directly on mainboard and connected again rebooted the phone. So... whats next? I promise I won't do anything more without a consult
Click to expand...
Click to collapse
:good::good:
Can you post an update of your "fastboot getvar all" please (hide your imei and serialno before posting)

alray said:
:good::good:
Can you post an update of your "fastboot getvar all" please (hide your imei and serialno before posting)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.02.20.0922
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 99000146554636
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
htc_fastboot finished. total time: 0.623s

qwe1234 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.02.20.0922
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 99000146554636
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
htc_fastboot finished. total time: 0.623s
Click to expand...
Click to collapse
try to flash the ruu again and post a screenshot of your cmd window if it doesn't work

alray said:
try to flash the ruu again and post a screenshot of your cmd window if it doesn't work
Click to expand...
Click to collapse
Alray... I don't know how to thank you. You're the best
Second flash went with a success at every step. Now everything seems to be absolutely ok. Firmware is updated.
Tomorrow I will check sim-lock and I will try to make a phone call and if everything will be ok I think it's gonna be the end
Thank you very much again

qwe1234 said:
Alray... I don't know how to thank you. You're the best
Second flash went with a success at every step. Now everything seems to be absolutely ok. Firmware is updated.
Tomorrow I will check sim-lock and I will try to make a phone call and if everything will be ok I think it's gonna be the end
Thank you very much again
Click to expand...
Click to collapse
:good:
you're welcome!

So I checked and the phone probably has a sim-lock. It shows notification that the simcard is wrong (translated from polish so in english it may be in some other words). I checked the subforum like you said in first reply and I found threads: [GUIDE] [fixed] SIM UNLOCK after lollipop and [GUIDE] Sprint sim unlock & Flash. I don't want to mess up anything (again) so could you please tell me which one is right for me?

qwe1234 said:
So I checked and the phone probably has a sim-lock. It shows notification that the simcard is wrong (translated from polish so in english it may be in some other words). I checked the subforum like you said in first reply and I found threads: [GUIDE] [fixed] SIM UNLOCK after lollipop and [GUIDE] Sprint sim unlock & Flash. I don't want to mess up anything (again) so could you please tell me which one is right for me?
Click to expand...
Click to collapse
So it looks like I'm stupid.
I tried to unlock the phone. Again bootloader unlocked, phone rooted. I wanted to unlock it with terminal commands using HtcOMADM_SPCS but I cannot install it. I've installed twrp (this time version 3.1.1.0) but it keeps saying that footer is wrong and signature verification failed...
Any more help, please? ;(

Hey sorry, don't mean to hijack this thread.
But would the same instructions apply for updating any older HTC m7 as far as the firmware and RUU is concerned?
I'm getting crickets on my thread, and just needed a general confirmation on the process again since it's been awhile.
I'm looking to flash a more current ROM and newer twrp recovery(or whatever is the best out there now).
Just confirming the process you described would still work the same way.
Thanks!
alray said:
See comment in red below
download these 3 files and save it in the folder where you already have fastboot.exe and adb.exe on your computer.
https://androidfilehost.com/?fid=24052804347850182
https://androidfilehost.com/?fid=24588232905725176
https://androidfilehost.com/?fid=24341993505161791
First update your firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot flash zip 6.23.651.10_full_firmware.zip
fastboot reboot-bootloader
You need to do the "fastboot flash zip" command twice. First time you'll get the "remote: 90 hboot pre-update! Please flush image again immediately" error. Second time the firmware will flash completely and should see a "OK/ flash sucessful" message. You can disregard the progress bar on the phone screen, it might not indicate 100% but if fastboot tell you "OK/ flash sucessful" it's alright
Then you can confirm everything is alright with
Code:
fastboot getvar all
your version-main should now be 6.23.651.10 and your hboot 1.61 instead of 1.44
Now you can flash the RUU, similar process but you must use the fastboot version linked above (htc_fastboot.exe):
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
fastboot reboot
Your phone might reboot by itself once, just wait until fastboot reports "OK". Again you can disregard the progress bar on your phone.
Make sure the phone is fully charged before doing all that and if something goes wrong post here and wait (do not skip any steps).
If everything went ok, the phone should reboot to the latest stock android version and the old twrp version replaced with the stock recovery. If the phone was sim-unlocked it might be relocked to Sprint again and you'll have to sim-unlock again (you can find the procedure in the "Sprint htc one" forum section, in the "general" sub-section.
Click to expand...
Click to collapse

cloud66 said:
Hey sorry, don't mean to hijack this thread.
But would the same instructions apply for updating any older HTC m7 as far as the firmware and RUU is concerned?
Click to expand...
Click to collapse
Since yours is also a Sprint HTC One, yes the same procedure should work.
I'm getting crickets on my thread
Click to expand...
Click to collapse
quote me next time and I'll be notified, just like you did in this thread.
I'm looking to flash a more current ROM and newer twrp recovery(or whatever is the best out there now).
Click to expand...
Click to collapse
Don't forget that only Sprint roms and Sprint recovery will work on your phone (roms or recovery for the gsm/m7ul won't work). Make sure the custom rom you want to flash is compatible with the Sprint variant (it will be mentioned in the OP of the rom thread if it's compatible with Sprint/M7_WLS). Flash the Sprint TWRP version:
twrp-3.1.1-0-m7wls.img not twrp-3.1.1-0-m7.img

alray said:
quote me next time and I'll be notified, just like you did in this thread.
Click to expand...
Click to collapse
Hey again. Alray can I ask you for a little bit more help? I've tried every way to sim unlock i found but without any success. Last method I used was from this video: https://www.youtube.com/watch?v=e6hHUae1TMs but when I want to run Unlock helper it crashes. Have no idea what am I doing wrong...;(

alray said:
Since yours is also a Sprint HTC One, yes the same procedure should work.
quote me next time and I'll be notified, just like you did in this thread.
Don't forget that only Sprint roms and Sprint recovery will work on your phone (roms or recovery for the gsm/m7ul won't work). Make sure the custom rom you want to flash is compatible with the Sprint variant (it will be mentioned in the OP of the rom thread if it's compatible with Sprint/M7_WLS). Flash the Sprint TWRP version:
twrp-3.1.1-0-m7wls.img not twrp-3.1.1-0-m7.img
Click to expand...
Click to collapse
Hey so looks like I'm running into an issue when updating my firmware.
I'm getting this:
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware and no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues.
Also flashed twrp recovery without any issues.
Rom is still working, everything is still normal....
Thoughts?

Also wanted to add that I was able to update TWRP to 3.1 and flash ICE ROM 7.1.1 and gapps without any issues. So far running semi-stable.
Tried updating firmware with s-on after i re-locked my bootloader, but that did not work either. I was still getting some weird error so I unlocked my bootloader again and then was able to flash the nougat rom just fine. It's strange that it's working with such an older version of the firmware... oh well.
Will still hold out for any suggestions. I'm sure I will run into some issues soon with the firmware being that out-of-date. Signal issues, battery issues, etc.