Related
I bough a GPE HTC One from the Play store. I used HTC Dev to unlock it, had enjoyed custom roms and recoveries. I wanted to learn how to revert back to stock so before the 4.4 OTA update I relocked the bootloader and restored a stock recovery (not my own original).
I received the 4.4 OTA update yesterday and I attempted to unlock the bootloader once more. I used the original bin file and went through the steps to do it again but am met with the same results. I can at times get a successful unlock command in terminal, but not the screen that is supposed to appear and unlock the device.
I've seen some threads that sort of have the same problem but none that have resolutions that work for me. I've attempted flashing RUU's but am always met with signature verification failures. I've tried fastboot oem unlock but that doesn't work either.
Hoping someone might have an idea.
TAMPERED
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.58.1700.5
eMMC-boot 2048MB
Nov 21 2013, 20:19:24.0
cid: GOOGL001
Misc:
HTC Sync manager installed then uninstalled
latest Android SDK installed for adb
debugging mode on
usb 2.0 on windows 7 x86
Hopefully someone with actual knowledge will come to help you, but why don't you try to S-off? that will give you more solution options.
Arjen_Arg said:
Hopefully someone with actual knowledge will come to help you, but why don't you try to S-off? that will give you more solution options.
Click to expand...
Click to collapse
From what I've been able to determine I'm unable to achieve S-OFF with HBOOT 1.54, or else I definitely would.
There are no RUU for GPE. The conversion RUU is not properly signed and was made from a system dump.
The GPE should be unlockable without a token or using htc dev.
fastboot oem unlock
what do you get?
You can't S-OFF on the GPE rom. you would have to flash a sense rom and then use rumrunner. You can't flash a different rom without unlocking and flashing a custom recovery...
msw141 said:
I bough a GPE HTC One from the Play store. I used HTC Dev to unlock it, had enjoyed custom roms and recoveries. I wanted to learn how to revert back to stock so before the 4.4 OTA update I relocked the bootloader and restored a stock recovery (not my own original).
I received the 4.4 OTA update yesterday and I attempted to unlock the bootloader once more. I used the original bin file and went through the steps to do it again but am met with the same results. I can at times get a successful unlock command in terminal, but not the screen that is supposed to appear and unlock the device.
I've seen some threads that sort of have the same problem but none that have resolutions that work for me. I've attempted flashing RUU's but am always met with signature verification failures. I've tried fastboot oem unlock but that doesn't work either.
Hoping someone might have an idea.
TAMPERED
RELOCKED
M7_UL PVT SHIP S-ON RH
HBOOT- 1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.58.1700.5
eMMC-boot 2048MB
Nov 21 2013, 20:19:24.0
cid: GOOGL001
Misc:
HTC Sync manager installed then uninstalled
latest Android SDK installed for adb
debugging mode on
usb 2.0 on windows 7 x86
Click to expand...
Click to collapse
That's old information. There has been an S-Off exploit for 1.54 for over a month. I've done it on a GPE just like yours. Search for Rumrunner S-Off.
---------- Post added at 07:43 PM ---------- Previous post was at 07:35 PM ----------
ipfreelytech said:
You can't S-OFF on the GPE rom. you would have to flash a sense rom and then use rumrunner. You can't flash a different rom without unlocking and flashing a custom recovery...
Click to expand...
Click to collapse
This is wrong. You CAN S-OFF a GPE. Although you need root access or unlocked bootloader.
Do you have root?
Rumrunner S-Off http://rumrunner.us/
edit. answered in post above
ipfreelytech said:
There are no RUU for GPE. The conversion RUU is not properly signed and was made from a system dump.
The GPE should be unlockable without a token or using htc dev.
fastboot oem unlock
what do you get?
You can't S-OFF on the GPE rom. you would have to flash a sense rom and then use rumrunner. You can't flash a different rom without unlocking and flashing a custom recovery...
Click to expand...
Click to collapse
I try unlock but don't succeed. This is the result:
[PG_ERROR] htc_pg_part_traverse(839):
invalid traverse range
[PG_ERROR] htc_pg_part_read(1092):
htc_pg_part_traverse failed
[DISPLAY_ERR] sp_custom partition: unlock_disp_bu:img_buf read error!
[DISPLAY_ERR] Can not load custom splash!
Loading custom splash failed!
OKAY [ 0.537s]
finished. total time: 0.538s
Arjen_Arg said:
Do you have root?
Click to expand...
Click to collapse
No root, sadly. And probably can't get it with locked bootloader and s-on either.
interesting.
Last night just for fun I relocked the bootloader on my GPE converted AT&T one. I then attempted to unlock using fastboot oem unlock and got the exact same results. I suspected it had to do with my phone being converted instead of legit GPE and also having a custom splash screen.
I'm s-off so I just unlocked using a a few quick commands while booted.
Try re-flashing the firmware.zip from the 4.4 ota for good measure. that will re-write your hboot and recovery and other firmwares.
you can download here: https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 fimrware.zip
fastboot reboot-bootloader
then attempt unlock again.
msw141 said:
I try unlock but don't succeed. This is the result:
[PG_ERROR] htc_pg_part_traverse(839):
invalid traverse range
[PG_ERROR] htc_pg_part_read(1092):
htc_pg_part_traverse failed
[DISPLAY_ERR] sp_custom partition: unlock_disp_bu:img_buf read error!
[DISPLAY_ERR] Can not load custom splash!
Loading custom splash failed!
OKAY [ 0.537s]
finished. total time: 0.538s
Click to expand...
Click to collapse
ipfreelytech said:
Try re-flashing the firmware.zip from the 4.4 ota for good measure. that will re-write your hboot and recovery and other firmwares.
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 fimrware.zip
fastboot reboot-bootloader
then attempt unlock again.
Click to expand...
Click to collapse
Well the firmware flash worked just fine. But then I tried flashboot oem unlock and I got the same error as documented earlier. I even tried the HTCdev method again, got a successful result but no unlock screen.
So I'm still stuck on relocked. But I'm encouraged that your file was able to flash with no error. Do you think there might be more files I could attempt to flash in that manner that could help?
ipfreelytech said:
interesting.
Last night just for fun I relocked the bootloader on my GPE converted AT&T one. I then attempted to unlock using fastboot oem unlock and got the exact same results. I suspected it had to do with my phone being converted instead of legit GPE and also having a custom splash screen.
I'm s-off so I just unlocked using a a few quick commands while booted.
Try re-flashing the firmware.zip from the 4.4 ota for good measure. that will re-write your hboot and recovery and other firmwares.
you can download here: https://mega.co.nz/#!DV0UEbBY!Vv6H4Ebf8WRCXrKwe5TGDUQqnvNk-9FiSjOvhjXAQvE
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 fimrware.zip
fastboot reboot-bootloader
then attempt unlock again.
Click to expand...
Click to collapse
Hi @ipfreelytech
If fastboot oem unlock didn't work for you, how did you unlock the bootloader?
SaHiLzZ said:
Hi,
If fastboot oem unlock didn't work for you, how did you unlock the bootloader?
Click to expand...
Click to collapse
When I first got my phone I unlocked via that HTCdev method by betting the unlock_code.bin file and flashing it. I wasn't aware until today that there was a different method for GPE that didn't require that. The problem now is that the oem unlock doesn't work, and HTCdev method says it works but doesn't complete.
Yeah this a new issue that we are seeing being reported more and more after 4.4 GPE update.. Unfortuantely no fix yet.
SaHiLzZ said:
Yeah this a new issue that we are seeing being reported more and more after 4.4 GPE update.. Unfortuantely no fix yet.
Click to expand...
Click to collapse
OK, understood. What do you suggest I keep an eye out for on the forums?
A new S-OFF method for 1.54 with a locked bootloader...a new firmware update where it might work again...or updated drivers for the hardware/adb? Appreciate your input.
adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
more info here: http://forum.xda-developers.com/showthread.php?t=2470340
this only works if you're s off and have root
SaHiLzZ said:
Hi @ipfreelytech
If fastboot oem unlock didn't work for you, how did you unlock the bootloader?
Click to expand...
Click to collapse
Ah Ok, that is what Guru's bootloader zip is based on. Thanks!
ipfreelytech said:
adb shell
su
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
more info here: http://forum.xda-developers.com/showthread.php?t=2470340
this only works if your s off and have root
Click to expand...
Click to collapse
This method that you used to unlock and "relocked" phone, is there any way to do it with S-On? I had previously rooted, and am now stuck, as the others (I have been posting on other threads).
I'm wondering, hoping that there is line code like this one that would allow for us to recover our phones....
doubtful. s-off is required because your modifying a "black box" partition. The solutions used to gain s-off in the first place require using an exploit to write to that partition. What i posted is just directly modifying it using dd.
elisaw99 said:
This method that you used to unlock and "relocked" phone, is there any way to do it with S-On? I had previously rooted, and am now stuck, as the others (I have been posting on other threads).
I'm wondering, hoping that there is line code like this one that would allow for us to recover our phones....
Click to expand...
Click to collapse
SaHiLzZ said:
Yeah this a new issue that we are seeing being reported more and more after 4.4 GPE update.. Unfortuantely no fix yet.
Click to expand...
Click to collapse
Hi I'm replying to you on this original thread instead of starting a new one. I received the 4.4.2 OTA update this morning and I still cannot unlock bootloader, getting the same error messages as documented earlier in this thread.
I am checking to see if you've heard of any success stories for people on a stock GPE HTC One (s-on, relocked, no root) getting their bootloader to unlock after 4.4 or 4.4.2. I've checked the forums regularly but most other people seem to have root, s-off, or customer recovery which I have neither of.
msw141 said:
Hi I'm replying to you on this original thread instead of starting a new one. I received the 4.4.2 OTA update this morning and I still cannot unlock bootloader, getting the same error messages as documented earlier in this thread.
I am checking to see if you've heard of any success stories for people on a stock GPE HTC One (s-on, relocked, no root) getting their bootloader to unlock after 4.4 or 4.4.2. I've checked the forums regularly but most other people seem to have root, s-off, or customer recovery which I have neither of.
Click to expand...
Click to collapse
Im getting this same issue after updating to 4.4.2 after i got my phone back from repair. It is completely stock now and when i try to unlock the phone it wont show the screen that asks me if im sure i want to unlock my phone, which is the last step on the htcdev site.
Im thinking its a kitkat issue.
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
Hi, I just get my HTC ONE GPE w/ android 4.4. This is my first HTC and I would like to get root access. Can u help me with a Root htc for Dummies? thanks in advance.
Herles said:
Hi, I just get my HTC ONE GPE w/ android 4.4. This is my first HTC and I would like to get root access. Can u help me with a Root htc for Dummies? thanks in advance.
Click to expand...
Click to collapse
one post above yours
http://forum.xda-developers.com/showthread.php?t=2260376
clsA said:
one post above yours
http://forum.xda-developers.com/showthread.php?t=2260376
Click to expand...
Click to collapse
I saw it, but want to be sure that it works for my Phone, cause it looks like its for regular htc, not GPE and not for 4.4. It is????
clsA said:
one post above yours
http://forum.xda-developers.com/showthread.php?t=2260376
Click to expand...
Click to collapse
Most comments says It doesnt work for 4.4
Herles said:
Most comments says It doesnt work for 4.4
Click to expand...
Click to collapse
nothing has changed that i know of
unlock bootloader at htcdev.com
flash custom recovery(TWRP) and flash SuperSU (root)
clsA said:
nothing has changed that i know of
unlock bootloader at htcdev.com
flash custom recovery(TWRP) and flash SuperSU (root)
Click to expand...
Click to collapse
Most comments are right - it doesn't work for 4.4; you'll get the following error:
(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.543s]
finished. total time: 0.543s
Click to expand...
Click to collapse
Unlocking the bootloader at htcdev.com is only for HTC One's running Sense UI, NOT for GPE HTC One's.
if its a gpe all you need to do is
get your adb/fastboot working on your comp
the unlock the boot loader using "fastboot oem unlock"
flash recovery in fastboot
get the supersu flashable zip and flash it in recovery
after that you will have root
advice for you as well is try to s-off asap to prevent any headaches later on..
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 :'(
Hello
My htc one is google play edition s-on , locked , no root , and i want to change this ROM
any solutions ?
imadsaber said:
Hello
My htc one is google play edition s-on , locked , no root , and i want to change this ROM
any solutions ?
Click to expand...
Click to collapse
unlock the bootloader and flash a custom rom or achieve s-off and convert it to another version.
alray said:
unlock the bootloader and flash a custom rom or achieve s-off and convert it to another version.
Click to expand...
Click to collapse
@alray ! i cant unlock bootloader with htc's methode
i mean when i try "fastboot flash unlocktoken Unlock_code.bin" nothing happind
imadsaber said:
@alray ! i cant unlock bootloader with htc's methode
i mean when i try "fastboot flash unlocktoken Unlock_code.bin" nothing happind
Click to expand...
Click to collapse
Google play edition is unlocked using "fastboot oem unlock" command. If it doesn't work then it means you have the infamous gpe bootloader unlock bug: http://forum.xda-developers.com/showthread.php?t=2547894
alray said:
Google play edition is unlocked using "fastboot oem unlock" command. If it doesn't work then it means you have the infamous gpe bootloader unlock bug: http://forum.xda-developers.com/showthread.php?t=2547894
Click to expand...
Click to collapse
@alray
(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.316s]
finished. total time: 0.318s
what i have to do now ??
imadsaber said:
@alray
(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.316s]
finished. total time: 0.318s
what i have to do now ??
Click to expand...
Click to collapse
Try Sunshine s-off, it's your only hope
alray said:
Try Sunshine s-off, it's your only hope
Click to expand...
Click to collapse
sunshine can't run without root :/ i dont have root
imadsaber said:
sunshine can't run without root :/ i dont have root
Click to expand...
Click to collapse
What is your android version?
alray said:
What is your android version?
Click to expand...
Click to collapse
@alray , android 5.1
imadsaber said:
@alray , android 5.1
Click to expand...
Click to collapse
Then you're right, you can't use it without root.
alray said:
Then you're right, you can't use it without root.
Click to expand...
Click to collapse
So what i have to do ?
imadsaber said:
So what i have to do ?
Click to expand...
Click to collapse
Maybe you could try to get temp root so you can use sunshine like they are doing in the verizon forum, otherwise you'are pretty much stuck locked and s-on.
alray said:
Maybe you could try to get temp root so you can use sunshine like they are doing in the verizon forum, otherwise you'are pretty much stuck locked and s-on.
Click to expand...
Click to collapse
No solution?
imadsaber said:
No solution?
Click to expand...
Click to collapse
Everything said here:
alray said:
Maybe you could try to get temp root so you can use sunshine like they are doing in the verizon forum, otherwise you'are pretty much stuck locked and s-on.
Click to expand...
Click to collapse