Database Develop

[Q] Stuck during convertion to GE 4.3

Hi there,
I recently fully converted my HTC one to GE (4.2.2) referring to this Thread (http://forum.xda-developers.com/showthread.php?t=2358781). I somehow didn't manage to OTA to 4.3 so I downloaded the 4.3 RUU and flashed them. After this the common camera bug appeared and ich flashed back the old 4.2.2 RUU from the same thread. After doing this I read relocking bootloader will enable OTA from 4.2.2 to 4.3 so I did this resulting in no OTA + beeing unable to unlock bootloader again. Here is the Error message. Does anyone have an idea for newbies like me?
(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.570s]
finished. total time: 0.570s
Info:
Relocked
S-OFF
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4A.17.3250.14
Thanks!

what command are you using to unlock the bootloader?
if you're using the token, don't do that
fastboot oem unlock

gunnyman said:
what command are you using to unlock the bootloader?
if you're using the token, don't do that
fastboot oem unlock
Click to expand...
Click to collapse
I used the fastboot oem unlock method.
I just figured it out somehow
I flashed the 4.3 RUU again then did the oem unlock and it worked. I think the problem was that hboot, radio etc. came from the 4.3 RUU but I "downgraded" with the 4.2.2 RUU.
At least I got it working with this thread (http://forum.xda-developers.com/showthread.php?t=2390249) using CWM but sadly it's not a full convertion
Thanks for your help.
Altough I read it is possible to fully convert with the 4.2.2 RUU and OTA update to 4.3 with no bugs I couldn't get it working. If you are planing on writing a tutorial I can contribute the "how-not-to-do" parts.
Cheers

[Q] Can't unlock bootloader

Hi,
I wanted to return 100% to stock and I flashed hboot 1.44.0000 from 1.28.401.7 and then I flashed latest 3.62.401.1 and now (S-ON and Relocked) I can´t unlock the bootloader. Here is what I have tried:
1-. Unlock via HTCDev --> After getting Unlock_code.bin and "flashing" it, my One does nothing. There is no unlock screen promt.
2-. Use renove to unlock bootloader --> As bootloader version and main version doens't match, it gives me an error (Segmentation Fault (Core dumped))
3-. Flashing official RUU of One Developer Edition --> Model ID error.
I have search for a solution here and I can't find anything... Have I locked my One forever?
Regards,
Urko

Can't unlock bootloader
urko95 said:
Hi,
I wanted to return 100% to stock and I flashed hboot 1.44.0000 from 1.28.401.7 and then I flashed latest 3.62.401.1 and now (S-ON and Relocked) I can´t unlock the bootloader. Here is what I have tried:
1-. Unlock via HTCDev --> After getting Unlock_code.bin and "flashing" it, my One does nothing. There is no unlock screen promt.
2-. Use renove to unlock bootloader --> As bootloader version and main version doens't match, it gives me an error (Segmentation Fault (Core dumped))
3-. Flashing official RUU of One Developer Edition --> Model ID error.
I have search for a solution here and I can't find anything... Have I locked my One forever?
Regards,
Urko
Click to expand...
Click to collapse
Hi,
Use the HTC One Mega tool kit, look at the attached screenshot for the same.

kash_9763 said:
Hi,
Use the HTC One Mega tool kit, look at the attached screenshot for the same.
Click to expand...
Click to collapse
There is no link right no, could you please let me a mirror link of the toolkit?
Regards,
Urko

kash_9763 said:
Hi,
Use the HTC One Mega tool kit, look at the attached screenshot for the same.
Click to expand...
Click to collapse
you need to be s-off for that
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
urko95 said:
There is no link right no, could you please let me a mirror link of the toolkit?
Regards,
Urko
Click to expand...
Click to collapse
here you go: http://forum.xda-developers.com/showthread.php?t=2490398
and BTW, it won't work. you need s-off for that to work

Can't unlock bootloader
urko95 said:
There is no link right no, could you please let me a mirror link of the toolkit?
Regards,
Urko
Click to expand...
Click to collapse
Hi,
Here you go..

you could check this: http://forum.xda-developers.com/showthread.php?t=2492469&page=5
and this: http://forum.xda-developers.com/showpost.php?p=47363868&postcount=8
Don't know if it would work though.

Htc One return back to original stock ROM to get OTA
nkk71 said:
you could check this: http://forum.xda-developers.com/showthread.php?t=2492469&page=5
and this: http://forum.xda-developers.com/showpost.php?p=47363868&postcount=8
Don't know if it would work though.
Click to expand...
Click to collapse
Hi,
Below are the details of my instrument HTC One and right now am on Revolution HD ROM 4.3+Sense5.5 rooted. I would like to go back to original stock ROM to get OTA. Kindly let me know complete detailed procedure to unroot and get back to stock as original factory reset with locked bootloader.
C:\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4148mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Here is my thread http://forum.xda-developers.com/showthread.php?p=47417362#post47417362
Kindly let me know your advice

nkk71 said:
you could check this: http://forum.xda-developers.com/showthread.php?t=2492469&page=5
and this: http://forum.xda-developers.com/showpost.php?p=47363868&postcount=8
Don't know if it would work though.
Click to expand...
Click to collapse
Nothing happens ... Here you have what I have type in CMD:
C:\Users\Urko\Desktop>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.005s]
finished. total time: 0.148s
I have tried with a new account and nothing happens. Thanks for your attention BTW
Regards,
Urko

urko95 said:
Nothing happens ... Here you have what I have type in CMD:
C:\Users\Urko\Desktop>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.005s]
finished. total time: 0.148s
I have tried with a new account and nothing happens. Thanks for your attention BTW
Regards,
Urko
Click to expand...
Click to collapse
Yeah sorry mate, didn't think it would work but was worth a shot. Like the other thread said, they had to run a full RUU, and unfortunately they're not around (unless you can get someone nice and professional from HTC on the phone, like the other guy).

nkk71 said:
Yeah sorry mate, didn't think it would work but was worth a shot. Like the other thread said, they had to run a full RUU, and unfortunately they're not around (unless you can get someone nice and professional from HTC on the phone, like the other guy).
Click to expand...
Click to collapse
So, there is no solution?
Thank you all
Regards,
Urko

urko95 said:
So, there is no solution?
Thank you all
Regards,
Urko
Click to expand...
Click to collapse
As far as I know, unfortunately not, please someone correct me if you've found another method
otherwise you'll need to contact HTC and hope they're willing to help you.
if revone would work for you (hboot 1.44) then that would work.
maybe we should ask revone and rumrunner to combine their work

nkk71 said:
As far as I know, unfortunately not, please someone correct me if you've found another method
otherwise you'll need to contact HTC and hope they're willing to help you.
if revone would work for you (hboot 1.44) then that would work.
maybe we should ask revone and rumrunner to combine their work
Click to expand...
Click to collapse
Swicthing tomorrow to a Xperia Z1... Bye HTC One forum, I will miss you :crying:
Regards,
Urko

[q] htc one gpe

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..

[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 :'(

Can't change GPE Rom

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