Related
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.
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..
I just received an HTC One GPE. It comes with 4.2.2; because of that, I cannot using fastboot with Windows 8.1. Then I let the OTA update to 4.4.2, then I use the command "fastboot oem unlock" but it gives me these error:
Code:
(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.589s]
finished. total time: 0.591s
Hboot version: 1.54
Extra question: after sucessfully unlock the bootloader, install the custom recovery, which guide should I follow to make S-OFF?
cruel91 said:
I just received an HTC One GPE. It comes with 4.2.2; because of that, I cannot using fastboot with Windows 8.1. Then I let the OTA update to 4.4.2, then I use the command "fastboot oem unlock" but it gives me these error:
Extra question: after sucessfully unlock the bootloader, install the custom recovery, which guide should I follow to make S-OFF?
Click to expand...
Click to collapse
you should have done some homework before updating to 4.4(.x) -> "fastboot oem unlock" no longer seems to work.
since you have a functioning ROM, you could look into firewater to S-Off
nkk71 said:
you should have done some homework before updating to 4.4(.x) -> "fastboot oem unlock" no longer seems to work.
since you have a functioning ROM, you could look into firewater to S-Off
Click to expand...
Click to collapse
As far as I know S-OFF requires the devices to be rooted, but I cannot grant any root access from now without unlock the bootloader
cruel91 said:
As far as I know S-OFF requires the devices to be rooted, but I cannot grant any root access from now without unlock the bootloader
Click to expand...
Click to collapse
firewater has a temproot exploit that may (or may not) work
nkk71 said:
firewater has a temproot exploit that may (or may not) work
Click to expand...
Click to collapse
Thank you. However, the temp-root does not work. I am downloading the stock 4.3 GPE RUU to flash over. Hoping I can get this done. I will report later
cruel91 said:
Thank you. However, the temp-root does not work. I am downloading the stock 4.3 GPE RUU to flash over. Hoping I can get this done. I will report later
Click to expand...
Click to collapse
you know that you can't downgrade without S-Off
So actually there is no solution to root/unlock_bootloader/s-off this? I guess I must stay with stock Google ROM
Correct.
sent from my mobile device
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 :'(
Hi all , i have problem with S-OFF with GPE M7 . Can you help me? I tried unlock boatloader over HTC developer but i stuck with .
(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.265s]
finished. total time: 0.266s
Miraas said:
Hi all , i have problem with S-OFF with GPE M7 . Can you help me? I tried unlock boatloader over HTC developer but i stuck with .
(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.265s]
finished. total time: 0.266s
Click to expand...
Click to collapse
Can you still boot in the OS?
alray said:
Can you still boot in the OS?
Click to expand...
Click to collapse
Yes i can, but i cannot unlock bootloader or S- OFF.
Miraas said:
Yes i can, but i cannot unlock bootloader or S- OFF.
Click to expand...
Click to collapse
What you are experiencing is the well known GPE bootloader unlock bug. The only way to unlock it require S-OFF and the only way you can achieve s-off without having an unlocked bootloader is using Sunshine s-off.
Be very careful from now, if you make a mistake and the rom can't boot anymore, your phone will be good for garbage. Once S-OFF is achieved, we can help you unlock the bootloader.
o.k Install the apk and what next? Thanks
Miraas said:
o.k Install the apk and what next? Thanks
Click to expand...
Click to collapse
Just launch the Sunshine app on your phone. It will run some tests then ask you to pay via PayPal or credit card. After you paid the phone wil reboot (may appear to bootloop). When the phone comes back on you'll be Unlocked Rooted and with s-off. All that good stuff in one shot
Danny201281 said:
Just launch the Sunshine app on your phone. It will run some tests then ask you to pay via PayPal or credit card. After you paid the phone wil reboot (may appear to bootloop). When the phone comes back on you'll be Unlocked Rooted and with s-off. All that good stuff in one shot
Click to expand...
Click to collapse
o.k i will try
Miraas said:
o.k i will try
Click to expand...
Click to collapse
Something wrong ( . Root not found .
Miraas said:
Something wrong ( . Root not found .
Click to expand...
Click to collapse
I found this but this is in M7 Verizon forum not about GPE. But same problem I think http://forum.xda-developers.com/showpost.php?p=55374349&postcount=5
Danny201281 said:
I found this but this is in M7 Verizon forum not about GPE. But same problem I think http://forum.xda-developers.com/showpost.php?p=55374349&postcount=5
Click to expand...
Click to collapse
not work for me (( any another options ? Thank for help guys
Could by problem my version 5.0.1 of android?