I was unable to update to KitKat - it kept failing for me. Did some digging around, looks like it's related to bootloader. I was on 4.18, not 4.23 bootloader. When I tried to update that, it kept failing also. I found this thread, which pointed me in the right direction: http://forum.xda-developers.com/showthread.php?t=2417097
The bootloader attachment on pg 2 of that thread worked for me and I was able to install KitKat via fastboot.
Same happened to me , fastboot flash bootloader 4.23.img did it for me
I had this issue. Had to manually update my bootloader to return to stock for the OTA. Luckily Wugs tool is very informative upon failure.
Sent from my Nexus 7 using Tapatalk
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
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?
So yesterday the 8th i bought the 2nd gen xt1064 off a guy on craigslist, story short... phone is great it came with stock 5.0. Bootloader was not unlocked but i was successful in doing so. Flashed twrp 2.8.3.0 just fine, supersu v2.02 flashed but when i went to open it it hit me with a message that it did not have any binaries or what not and force closed. I tried flashing another one but it got me stuck on the bootloader warning forcing me to downgrade to 4.4.4 (21.11.23) Now stock recovery shows: KXB21.85-23 i tried the ota lollipop update but it fails.
Any solutions on getting around, also what are the commands to lock the bootloader again just in case its a requirement? Sorry for the all the Q's im coming from a galaxy s3.
Versatil2010 said:
So yesterday the 8th i bought the 2nd gen xt1064 off a guy on craigslist, story short... phone is great it came with stock 5.0. Bootloader was not unlocked but i was successful in doing so. Flashed twrp 2.8.3.0 just fine, supersu v2.02 flashed but when i went to open it it hit me with a message that it did not have any binaries or what not and force closed. I tried flashing another one but it got me stuck on the bootloader warning forcing me to downgrade to 4.4.4 (21.11.23) Now stock recovery shows: KXB21.85-23 i tried the ota lollipop update but it fails.
Any solutions on getting around, also what are the commands to lock the bootloader again just in case its a requirement? Sorry for the all the Q's im coming from a galaxy s3.
Click to expand...
Click to collapse
I sounds like you may have flashed XT1063 firmware on XT1064
Weird cuz the link to the firmwate said xt1064, ill try again.
Sent from my XT1064 using XDA Premium 4 mobile app
Versatil2010 said:
Any solutions on getting around, also what are the commands to lock the bootloader again just in case its a requirement?
Click to expand...
Click to collapse
I wouldn't bother with all the OTA.zip flying around. It's a complete mess, since Motorola published different OTAs for different ROM-versions.
Here are some usefull links to get around
[TOOL]Minimal ADB and Fastboot is prooven to work with our devices. If you are using Linux, just install adb and fastboot through your packagemanager.
Stock Firmware for Moto G (2014) flashable through fastboot. Just in case you want to return to stock.
TWRP recovery compatible with Lollipop.
[ROM][5.0.2][titan][XT1063/64]The Titan Prime ROM is a Lollipop custom ROM (the only one, as of now).
BETA-SuperSU-v2.44.zip as older versions don't work properly with our device.
And forget about relocking the bootloader. There is absolutely no benefit in doing so. Your warranty is void.
I'd like to return to stock directly to 4.4.2, and found this, but apparently the link for AHD is down. Anyone know if there's a mirror for it?
I currently have Blisspop installed. No ADB detection (adb turned on, phone says connected but PC doesn't see it), and fastboot isn't being detected. Anyone able to help?
Silly me, forgot to install Moto USB drivers on new Windows install.
Lmao bro, good to see you back buddy. So did you get it work?
TecknoFreak said:
Lmao bro, good to see you back buddy. So did you get it work?
Click to expand...
Click to collapse
I did after a bit of re-learning. Was on LGG2 for a while but it broke so I'm back on the HD. Turns out there is no official KitKat for the HD, that page is misleading and I've been spamming "System updates" on stock for half an hour.
Back on stock now (obviously) and can't manage to get CWM or PhilZ working, manually or through Myth. Just the stupid broken android. It's midnight here, so that's probably playing a factor in it. More tinkering tomorrow...
Try rooting with saferoot, then use mythtools or flashify for recovery.
Sent from my LG-D850 using XDA Free mobile app
bmatney said:
Try rooting with saferoot, then use mythtools or flashify for recovery.
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
What exactly is Saferoot? Never heard of it and Motochopper is the standard for this gen of Moto devices.
Some people have had issues if they are on the newest firmware with motochopper.
Sent from my LG-D850 using XDA Free mobile app
TecknoFreak said:
Lmao bro, good to see you back buddy. So did you get it work?
Click to expand...
Click to collapse
bmatney said:
Some people have had issues if they are on the newest firmware with motochopper.
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Okay, well I done did it this time. Got up to stock ATT 4.1.1, then when I learned 4.4.2 isn't actually available yet, flashed Blisspop, which ran terribly, trying to go back to stock again with same fxz, trying to update to 4.1.1, the update gives me invalid GPT, stuck in fastboot, and apparently my bootloader got re-locked.
Any attempt to flash anything through fastboot returns a remote failure. Think I may be ****ed here.
penser said:
Okay, well I done did it this time. Got up to stock ATT 4.1.1, then when I learned 4.4.2 isn't actually available yet, flashed Blisspop, which ran terribly, trying to go back to stock again with same fxz, trying to update to 4.1.1, the update gives me invalid GPT, stuck in fastboot, and apparently my bootloader got re-locked.
Any attempt to flash anything through fastboot returns a remote failure. Think I may be ****ed here.
Click to expand...
Click to collapse
Your bootloader is not re-locked, just your gpt partition has been made invalid by gpt downgrade done by OTA (and because of that, the lock status can't be correctly determined by bootloader anymore).
All you have to do to fix it is to extract the gpt partition from the latest att OTA update and flash it via fastboot.
(I assume that you've been on the second aka latest 4.1.1 update from att [98.5.38], then downgraded to 4.0.4 by fxz while skipping gpt and tz flash, then took ota to the first 4.1.1 att update [98.4.20], resulting in downgraded gpt, because the actual gpt on your device before you took the ota was the newer one from the second 4.1.1 att ota [98.5.38].)
EDIT:
The latest att ota is attached to this post: http://forum.xda-developers.com/showpost.php?p=52657363&postcount=13
Extract gpt_main0.bin from the zip and flash it:
Code:
fastboot flash partition gpt_main0.bin
kabaldan said:
Your bootloader is not re-locked, just your gpt partition has been made invalid by gpt downgrade done by OTA (and because of that, the lock status can't be correctly determined by bootloader anymore).
All you have to do to fix it is to extract the gpt partition from the latest att OTA update and flash it via fastboot.
(I assume that you've been on the second aka latest 4.1.1 update from att [98.5.38], then downgraded to 4.0.4 by fxz while skipping gpt and tz flash, then took ota to the first 4.1.1 att update [98.4.20], resulting in downgraded gpt, because the actual gpt on your device before you took the ota was the newer one from the second 4.1.1 att ota [98.5.38].)
EDIT:
The latest att ota is attached to this post: http://forum.xda-developers.com/showpost.php?p=52657363&postcount=13
Extract gpt_main0.bin from the zip and flash it:
Code:
fastboot flash partition gpt_main0.bin
Click to expand...
Click to collapse
Thank you, you're a life saver! Re-learning everything about the AHD, got it for another 2 years.
Just bought an at&t variant on craigslist, I did a factory reset and tried to run the 5.1 update and I get an error updating, it downloads update.. then it reboots and starts installing showing the android guy working , then about 20 seconds into it it shows the little android guy on his back with a red exclamation and says error and then proceeds to reboot. Once rebooted it says it failed to update. I'm used to Samsung phones .. hoping there's an odin type option to get a stock 5.1 or rooted stock 5.1 on this guy, any headstart info would be appreciated. thanks
Here is the AT&T 5.0.2 firmware:
http://www.filefactory.com/file/1cekivswpakf/VICTARA_ATT_XT1097_5.0.2_LXE22.46-34_cid1_CFC.xml.zip
If you want to unlock your bootloader or root your phone don't upgrade yet! While you still have 5.0.2, root is possible with mofo and unlocking the bootloader can be done with sunshine. After you upgrade to 5.1 you can't downgrade nor root it. If you unlock it now and root it now, then you can keep root when you go to 5.1. But if you go to 5.1 before that you are screwed and lose the ability to do it forever.
We don't use odin. We have a tool called RSDLite. Search for it on these forums and you will find it and instructions on how to use it.
Sent from my XT1095 using Tapatalk
thanks for the heads up.. Glad I decided to wait and not try to figure out that update.. then not be able to root.
thanks