Related
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
mikhailov1 said:
Hello,
I seem to have gotten myself into a bind, and looking ahead to the 4.4 KitKat release, I am not sure how to get myself out of it. I've already done a lot of research and troubleshooting on my own, but can't seem to resolve the problem.
I purchased an HTC One Google Play edition, and decided to root to apply a quick fix with utilizing the Nexus 5 launcher. To that end, I unlocked my bootloader and rooted. I had a Windows 7 partition on my Mac at the time, but it was giving me trouble. Since the root, I became dissatisfied with the performance of the phone, and attempted to restore to factory.
I flashed stock recovery again, and relocked the bootloader. Now the bootloader shows as "relocked" and "tampered." However, in between root and unroot attempts, I upgraded my partition to Windows 8.1. Suddenly, when in fastboot, my HTC One shows up as "USB Device not Recognized," meaning I cannot issue any commands using ADB. If I don't get "waiting for device" I get "device offline," and my device is still rooted.
Whenever I uninstall Super SU, it's right back upon reboot.
I currently have S-ON. I am unable to get S-OFF because my computer doesn't recognize the phone when in fastboot. I tried updating and downloading different HTC Drivers to no avail.
I want to attempt to get my device back to its exact status when I bought the phone. Meaning, I want to have my bootloader as locked, keep S-ON (although I don't mind having S-OFF temporarily), and flash the stock RUU/Recovery. Upon Google Search, this seems easy, but there is not much out there for the GPE. A lot of the guides I have found are for Sense versions. My phone is not a GPE conversion. It is an actual GPE phone purchased on the Play Store.
Phone is functional, but I am concerned when 4.4 comes out, the update will fail or brick.
Sorry if this thread is long. I wanted to be as detailed as possible when asking for help. Thanks again to anyone on XDA who can assist.
Click to expand...
Click to collapse
try this http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
it worked for some users
Thanks. Will try when I get home. I was able to use my Win 7 computer at work to unlock the boot loader again, but I cannot get S Off. I ran rumrunner and it looked like it was working, but then said FATAL: download update. Is there no rumrunner for GPE?
Sent from my HTC One using Tapatalk
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Prash8429 said:
You got stock rom and stock recovery ryt... lock the bootloader and check for update
Click to expand...
Click to collapse
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
mikhailov1 said:
Yeah I have stock rom and I removed TWRP and flashed stock recovery. Because I did two factory restores from bootloader, I'm assuming the stock recovery is working properly, but I'm a noob at this stuff so I could be wrong.
Going to relock the bootloader, remove SuperSU, and attempt the update when it hits. Hopefully it will work.
Thanks for your help! Since I'm a new member, how do I add to your thanks meter? Want to make sure you're properly....thanked.
Click to expand...
Click to collapse
you can still get OTA with a rooted phone, as long as you have stock recovery and flashed stock ruu.... tip if your having trouble with flashing ruu change the zip file name to something simple like ruu.zip worked for me.:good:
mikhailov1 said:
Update: Your suggestion worked perfectly! I was able to unlock my bootloader again from my windows 8.1. I'm now trying to get S-OFF and flash the stock gpe RUU. To date, the RUU fails to install, and rumrunner gives me errors that ask me to run the program again. I feel I am still stuck as I want to eliminate root and make sure I can receive OTA. Is there anything else I can do? I'm still running stock 4.3 and stock recovery for the GPE.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Can you tell me if your bootloader was 1.54 or 1.55? I have been unable to get Windows 8.1 to recognize the 1.54 bootloader. It always says "device not recognized" If yours was 1.54.0000 I will try this fix. Thanks.
I am 1.54.
Sent from my Nexus 5 using Tapatalk
Thanks for this, helped me out alot
Sent from my HTC One using XDA Premium 4 mobile app
Hey guys, so I was on 4.4 and downgraded and managed to get my 4.2.2 rom rooted.
Now I want to upgrade to 4.4, but when I attempt to go into recovery, it just restarts into android.
I attempted to flash a recovery, but it continually failed. Maybe I am doing something wrong when attempting to flash the recovery..
Attached is what I have so far.
I take it that you didn't use the directions in the SlapMyMoto to achieve root
nhizzat said:
I take it that you didn't use the directions in the SlapMyMoto to achieve root
Click to expand...
Click to collapse
Well originally I used 64 scrip to downgrade to 4.2.2 then used moto x tool kit.
I am currently unrooted on 4.2.2 right now. What is the best way to go about continuing?
when I tried using pwnmymoto it doesn't install..
derik123derik123 said:
Well originally I used 64 scrip to downgrade to 4.2.2 then used moto x tool kit.
I am currently unrooted on 4.2.2 right now. What is the best way to go about continuing?
when I tried using pwnmymoto it doesn't install..
Click to expand...
Click to collapse
please follow the directions in the guide at the below link.
also is your phones bootloader unlocked?
http://forum.xda-developers.com/showthread.php?t=2603358
dray_jr said:
please follow the directions in the guide at the below link.
also is your phones bootloader unlocked?
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
I am pretty sure I am bootloader locked.
I am now on 4.4 rooted but when I attempted to flash a recovery I'd get a preflash failure.
derik123derik123 said:
I am pretty sure I am bootloader locked.
I am now on 4.4 rooted but when I attempted to flash a recovery I'd get a preflash failure.
Click to expand...
Click to collapse
well that would be why you cant flash TWRP recovery. you can not flash TWRP or Clockwork on a device with a locked bootloader.
the only recovery you can use on a locked bootloader is Safestrap
which can be located here
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
good luck
but i would recommend re-flashing to stock and re-rooting your device so you don't have and issues because you tried to flash a unlocked bootloader recovery on a locked bootloader device
And if you had read, you'd know that selecting "recovery" in the bootloader actually boots Android with write protection off.
Also, this is why I don't like toolkits. Too many people jumping in head first without an inkling of understanding of what's going on with their phone.
Hello, I would very much appreciate any help provided.
I just got a moto x developer edition gsm. I'll be using it on tmobile.
I've rooted lots of android phones and have never had this many problems. I tried a lot of different things on these forums and have had some success but i'm stuck now.
I was able to unlock the bootloader using motorola's site. I also have TWRP recovery installed (2.6.3.1). Currently the phone has 4.2.2 (build 13.9.0Q2.x-116-x-17-57) and its rooted, working fine.
The moral of the story is that i'm unable to update to 4.4. I've tried the OTA update twice and it downloads fine, then reboots to twrp to install it and it fails, saying something about its not ghost. Although in my system version it does say ghost. I also downloaded the 4.4 rom and manually tried to install it using twrp, also fails.
I'm not totally sure if the rom i'm on now is the same one that the phone came with. The rom that's on it now was obtained from this page:
http://sbf.droid-developers.org/phone.php?device=0
(Android 4.2.2 Blur_Version.139.12.57.ghost_row.Retail.en.US) for t-mobile US
Please help me be able to update to 4.4 and ideally keep root.
Jay10826 said:
Hello, I would very much appreciate any help provided.
I just got a moto x developer edition gsm. I'll be using it on tmobile.
I've rooted lots of android phones and have never had this many problems. I tried a lot of different things on these forums and have had some success but i'm stuck now.
I was able to unlock the bootloader using motorola's site. I also have TWRP recovery installed (2.6.3.1). Currently the phone has 4.2.2 (build 13.9.0Q2.x-116-x-17-57) and its rooted, working fine.
The moral of the story is that i'm unable to update to 4.4. I've tried the OTA update twice and it downloads fine, then reboots to twrp to install it and it fails, saying something about its not ghost. Although in my system version it does say ghost. I also downloaded the 4.4 rom and manually tried to install it using twrp, also fails.
I'm not totally sure if the rom i'm on now is the same one that the phone came with. The rom that's on it now was obtained from this page:
http://sbf.droid-developers.org/phone.php?device=0
(Android 4.2.2 Blur_Version.139.12.57.ghost_row.Retail.en.US) for t-mobile US
Please help me be able to update to 4.4 and ideally keep root.
Click to expand...
Click to collapse
You need to be stock, unrooted, with stock recovery to take the OTA. Use the sbf you have to flash back your stock system and recovery and you should be good to go to accept the update.
Jay10826 said:
The moral of the story is that i'm unable to update to 4.4. I've tried the OTA update twice and it downloads fine, then reboots to twrp to install it and it fails, saying something about its not ghost. Although in my system version it does say ghost. I also downloaded the 4.4 rom and manually tried to install it using twrp, also fails..
Click to expand...
Click to collapse
that is your problem. The OTA installs will not install via 3rd party recovery like TWRP and CWM.
fastboot flash the stock recovery back on your phone and try the OTA.
Thanks for the help guys, going back to completely stock enabled me to get to 4.4. After that luckily I found out that rooting and installing twrp was very simple, unlike all the info i was reading in the developer forum. All set now
Why didn't you flash the official firmware manually using fastboot? Once done, boot into Android and run adb reboot bootloader. Fastboot flash recovery twrp.img, select recovery, adb push su.zip /sdcard/, flash su.zip, adb reboot?
Hi all, sorry if this has been asked before..
I didn't know that kit kat 4.4.2. cannot be rooted lol, so I unlocked my boot loader and spent hours trying to load recovery (TWRP or CWM), obviously with no luck.i saw something online that said 4.4 and I assumed it was good for 4.4.2. Didn't work anyways.
Is there any way to load the factory Rogers rom back on so that I don't have that unlocked bootloaeer warning on every boot ?
If yes, any idea where I can download ??
Also, will this change my status on fast boot to Locked ?
I was so looking forward to setup recovery and root, oh well, I still love the device and will be ok at stock until a fix comes out.
Any help would be very much appreciated
Thanks so much
I don't have time to give extreme details but maybe I can still help point you in the right direction.
First off the Rogers Moto X is an XT1058, not an XT1053.
Once the bootloader is unlocked you can easily root the phone with twrp - same version is used for 4.4 and 4.4.2
You can relock the bootloader but the warning is technically always present. You can overwrite the image with a different one though.
The factory firmware is available for download, you can flash it yourself with rsdlite.
There are easy to find threads with all of the details needed to restore to 100% stock or root the Moto X. A few minutes searching and you should find them. Give it a shot, if after that you have further questions by all means please ask.
Hi, thanks for the reply
You are correct, its a 1058 and I officially unlocked my bootloader with motorola and voided my warranty...
I used this link
http://dottech.org/147327/how-to-root-moto-x-on-android-4-4-kitkat-guide/a
And when I try to install the recovery in terminal, it says (bootloader) variable not supported)
It then says writing recovery, finished (so it seems to write it), but I follow instructions, then reboot using terminal command "fastboot reboot" and try to boot into recovery but its blank.I even tried just rebooting to recovery and it still didnt work...
Or it just reverts to stock boot up.
I have tried others also but cannot seem to get it working properly.
Any chance you can guide me though it ? I would really appreciate it...
Hi I did some searching and got it figured out
Thanks again for your help
Hi again,
For some reason, when I went to reboot this morning, TWRP is gone. I boot into recovery and blank screen, seems it didnt hold.
Any idea why ??
Thanks
Steve-x said:
I don't have time to give extreme details but maybe I can still help point you in the right direction.
First off the Rogers Moto X is an XT1058, not an XT1053.
Once the bootloader is unlocked you can easily root the phone with twrp - same version is used for 4.4 and 4.4.2
You can relock the bootloader but the warning is technically always present. You can overwrite the image with a different one though.
The factory firmware is available for download, you can flash it yourself with rsdlite.
There are easy to find threads with all of the details needed to restore to 100% stock or root the Moto X. A few minutes searching and you should find them. Give it a shot, if after that you have further questions by all means please ask.
Click to expand...
Click to collapse
Hi guys, yesterday i tried to install ROM "XT1058_GHOST_RETBR_5.1_LPA23.12-15_cid12_CFC.xml" to my moto X 1058 At&T (android 4.4.4) with RSD litle.
It failed and now i only can turn on the phone and it goes to bootloader menu and i cant do anything. I can connect it to my PC and RSD detect it but i cant put any kind of ROM ((
I know that my moto x is not dead yet i have hope u.u :crying:
Please someone can help me? :crying:
PS: SORRY MY ENGLISH
PS2: I ADD A SCREENSHOT WITH SOME DETAILS ABOUT MY MOTO X after DO what i explain.
First off, you have an ATT XT1058... why are you trying to flash XT1058_GHOST_RETBR.... which is for RETAIL BRAZIL!?!
Is your bootloader locked or unlocked?
EDIT: never mind, I read here -> http://forum.xda-developers.com/showpost.php?p=61834453&postcount=78 then you have a locked bootloader...
so my advice...
Try to boot into stock recovery, and wipe cache, and reboot.
If that doesn't work.. try a factory reset (also from inside stock recovery) NOTE: this will delete your data, apps, pix, music, anything on the phone's /sdcard... etc..
Next, would be to try to re-flash Stock ATT 4.4.4 SBF using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
If that doesn't work... then you have no choice but to wait until the 5.1 SBF for ATT XT1058 leaks and is posted... and flash that using mFastboot.
KidJoe said:
First off, you have an ATT XT1058... why are you trying to flash XT1058_GHOST_RETBR.... which is for RETAIL BRAZIL!?!
Is your bootloader locked or unlocked?
EDIT: never mind, I read here -> http://forum.xda-developers.com/showpost.php?p=61834453&postcount=78 then you have a locked bootloader...
so my advice...
Try to boot into stock recovery, and wipe cache, and reboot.
If that doesn't work.. try a factory reset (also from inside stock recovery) NOTE: this will delete your data, apps, pix, music, anything on the phone's /sdcard... etc..
Next, would be to try to re-flash Stock ATT 4.4.4 SBF using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 )
If that doesn't work... then you have no choice but to wait until the 5.1 SBF for ATT XT1058 leaks and is posted... and flash that using mFastboot.
Click to expand...
Click to collapse
Into bootloader any option work, only for get pictures from IMEI, ID, etc.
I will try re flash stock ATT using mfastboot cause trying do this in RSD doesnt work
One friend told me he solved his problem unlocking bootloader by a program that unlock it automatic, then he instaled android 4.4.4.
My question is that if can i do what you are telling me cause in stock recovery appear 30.BE unde AP Fastboot Flash Mode (s) line. And it mean 30.BE= android 5.1 brazil so maybe i have to do a downgrade?
i dont know if you undestand me.
Thanks for your time
NEW INFO
i will writte more datails:
After i tryed install failed Brasil ROM the info about my cellphone is the next:
Bootloader version: 30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
Bootloader is: LOCKED (and can´t be unlocked by motorola steps cause my moto x is AT&T)
Thinking about it and looking for a lot places from 2 days i have next conclusion:
How now i have bootloader version "30.BE" i have two options:
First: Downgrade android but i need unlocked bootloader for do it.
Second option: Wait until ROM android 5.1 by AT&T (i read update is ready but i cant find ROM, i only found ZIP for put in my internal memory and update android from old android but i cant access to my internal memory cause my PC does recognized like memory device)
What do you think guys?
zloopa said:
Into bootloader any option work, only for get pictures from IMEI, ID, etc.
I will try re flash stock ATT using mfastboot cause trying do this in RSD doesnt work
One friend told me he solved his problem unlocking bootloader by a program that unlock it automatic, then he instaled android 4.4.4.
My question is that if can i do what you are telling me cause in stock recovery appear 30.BE unde AP Fastboot Flash Mode (s) line. And it mean 30.BE= android 5.1 brazil so maybe i have to do a downgrade?
i dont know if you undestand me.
Thanks for your time
Click to expand...
Click to collapse
I can tell that English (or at least USA Engish) isn't your primary language, so hopefully you can understand me too
An ATT XT1058 that has never been updated to 4.4.4 or above can use Sunshine to unlock the bootloader. Since you've had 4.4.4 and above on there, you can't unlock.
30.BE is a 5.1 bootloader. That is part of your problem. Somehow, parts of the XT1058_GHOST_RETBR... 5.1 SBF did flash to your phone, but not all of it..
Are you sure you didn't unlock your bootloader? Boot to FastbootAP/Bootloader screen and tell me what you see.. Do you see LOCKED STATUS 0, or Locked Status 2, or Unlocked Status 3?
---------- Post added at 07:23 AM ---------- Previous post was at 07:18 AM ----------
zloopa said:
i will writte more datails:
After i tryed install failed Brasil ROM the info about my cellphone is the next:
Bootloader version: 30.BE (sha-34b7ccb, 2015-04-22 12:57:17)
Bootloader is: LOCKED (and can´t be unlocked by motorola steps cause my moto x is AT&T)
Thinking about it and looking for a lot places from 2 days i have next conclusion:
How now i have bootloader version "30.BE" i have two options:
First: Downgrade android but i need unlocked bootloader for do it.
Second option: Wait until ROM android 5.1 by AT&T (i read update is ready but i cant find ROM, i only found ZIP for put in my internal memory and update android from old android but i cant access to my internal memory cause my PC does recognized like memory device)
What do you think guys?
Click to expand...
Click to collapse
Your first option is not correct. You can't fully downgrade, even with an unlocked bootloader. You can partially downgrade, but that isn't 100% safe. There is a very good chance it wont work, or you'll brick even worse when trying to downgrade, or later when taking the OTA.
For your second option.. Correct. As of yet, the FULL SBF of 5.1 for ATT hasn't leaked. Only the OTA Zip file which is an incremental update, not a full update, and therefore can't be used to recover in this state. Sit tight. Its only a matter of time.
I know you probably want to use your phone NOW, so waiting isn't a good option... but it is likely your only SAFE option right now.
KidJoe said:
I can tell that English (or at least USA Engish) isn't your primary language, so hopefully you can understand me too
An ATT XT1058 that has never been updated to 4.4.4 or above can use Sunshine to unlock the bootloader. Since you've had 4.4.4 and above on there, you can't unlock.
30.BE is a 5.1 bootloader. That is part of your problem. Somehow, parts of the XT1058_GHOST_RETBR... 5.1 SBF did flash to your phone, but not all of it..
Are you sure you didn't unlock your bootloader? Boot to FastbootAP/Bootloader screen and tell me what you see.. Do you see LOCKED STATUS 0, or Locked Status 2, or Unlocked Status 3?
---------- Post added at 07:23 AM ---------- Previous post was at 07:18 AM ----------
Your first option is not correct. You can't fully downgrade, even with an unlocked bootloader. You can partially downgrade, but that isn't 100% safe. There is a very good chance it wont work, or you'll brick even worse when trying to downgrade, or later when taking the OTA.
For your second option.. Correct. As of yet, the FULL SBF of 5.1 for ATT hasn't leaked. Only the OTA Zip file which is an incremental update, not a full update, and therefore can't be used to recover in this state. Sit tight. Its only a matter of time.
I know you probably want to use your phone NOW, so waiting isn't a good option... but it is likely your only SAFE option right now.
Click to expand...
Click to collapse
I never tried to unlock bootloader and before start to trying to upgrade to 5.1 brazil, bootloader appear "DEVICE IS: LOCKED" and now appear the same "LOCKED AND STATUS 0". (check the image if you can)
The question now is: maybe you know if the solution is wait until 5.1 Android for AT&T or even if i have this ROM maybe exist a possibility that my moto doesn't get fix? Maybe the question is hard to confirm 100% but maybe it is a 90 % possible that my moto get fix with this way.
I love this phone but i was too newbie and I confused ways to change ANDROID by mys XPERIA and HTC's phones.
zloopa said:
I never tried to unlock bootloader and before start to trying to upgrade to 5.1 brazil, bootloader appear "DEVICE IS: LOCKED" and now appear the same "LOCKED AND STATUS 0". (check the image if you can)
The question now is: maybe you know if the solution is wait until 5.1 Android for AT&T or even if i have this ROM maybe exist a possibility that my moto doesn't get fix? Maybe the question is hard to confirm 100% but maybe it is a 90 % possible that my moto get fix with this way.
I love this phone but i was too newbie and I confused ways to change ANDROID by mys XPERIA and HTC's phones.
Click to expand...
Click to collapse
I hate to say it, but yeah, you're likely stuck until an ATT 5.1 SBF is posted somewhere.
KidJoe said:
I hate to say it, but yeah, you're likely stuck until an ATT 5.1 SBF is posted somewhere.
Click to expand...
Click to collapse
I have this:
http://www.filefactory.com/file/2kmrq89bx1h/XT1058_GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml.zip
What do you recommed to do?
Whit RSD or do you have some guide for fix my cellphone
zloopa said:
I have this:
http://www.filefactory.com/file/2kmrq89bx1h/XT1058_GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml.zip
What do you recommed to do?
Whit RSD or do you have some guide for fix my cellphone
Click to expand...
Click to collapse
As I said earlier... flash using mfastboot (see the requirements and option 5 in post 2 of -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 ) just use that 5.1 SBF... and I would consider including the mfastboot erase userdata command, or doing a factory reset after you flash... Yes it will erase your data, apps, SDCard, etc...
GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml
also failed
error on GPT ..
Bootloader 30BE
accidentally flashed verizon Lollipop bootloader on it ..
now LP 5.1 ATT not working on it
aamszia said:
GHOST_ATT_5.1_LPA23.12-21.1_cid1_CFC.xml
also failed
error on GPT ..
Bootloader 30BE
accidentally flashed verizon Lollipop bootloader on it ..
now LP 5.1 ATT not working on it
Click to expand...
Click to collapse
Hi in same situation. Did u fixed it?