Related
As the title states, I rooted my revolution, but I can no longer access it via lgpnst or anything that uses adb, so I'm stuck. I have been trying to find something to update to v8 or v9 using clockworkmod (4.0.0.2), but it appears that everything being suggested requires me to have access with adb. No matter what I try, attempts to access through adb result in "device not found", or "waiting for device".
I did try a factory reset, which got me stuck in a clockworkmod reboot loop, when I used exitrecovery to fix that. If there is any sort of update or fix to be applied from clockworkmod, that would be great. At this point, I just want to get away from this ridiculous forced download and reboot process that just makes this device harder to use.
Any suggestions?
Flash a TOT with LGPNST, either ZV8 or ZV9, and you will be golden.
Re: *7/13/12*- FIX YOUR LG Revolution VS910 Firmware V4,V6,V7,V8, V9 W/ Instructions
Sent from my VS910 4G using Tapatalk 2
acfreema said:
I can no longer access it via lgpnst or anything that uses adb
Click to expand...
Click to collapse
This is the hurdle.
Oops. My bad. Missed that and focused on the mentions of ADB.
Edit: Have you tried different cables, computers, operating systems (XP for instance), or drivers? Also, make sure there are no other instances of adb on the computer. I have read that can cause problems too.
Edit x2:
acfreema said:
At this point, I just want to get away from this ridiculous forced download and reboot process that just makes this device harder to use.
Click to expand...
Click to collapse
You mean the OTA update? That can be disabled either by Titanium or a root explorer.
Sent from my VS910 4G using Tapatalk 2
I have tried all of the drivers I could find, and all of the different cables sitting around my place with no success. Right now, I don't have access to xp at home, but now I'm thinking there might be something to do with the system I've been using at home (which also runs windows 7 x64). When plugging my phone into my work computer (which runs xp), I got a usb modem prompt. There may be hope if I use a virtual machine at home.
I haven't looked into the titanium backup or root explorer, so that will happen this evening. Thanks for the suggestion.
Score! Thanks for getting me to think about the system again. I removed all of the drivers, created another administrator user account, and then logged into it and connected the phone... poof! I was prompted! I installed the drivers, and then it appeared in lgnpst! A short couple of uploads, and I'm there.
Awesome. Glad you got it going!
Sent from my VS910 4G using Tapatalk 2
I'm an amateur ROM flasher and I usually get around a problem after a few hours of messing around with the device and forums but I am absolutely stumped by this one. After unsuccessfully trying to flash a few roms, I decided to restore my phone back to what it was because I backed it up only a few hours before. All it would load is a black screen with the status bar showing the time and no signal, sometimes allowing me to slide to unlock to my saved launcher with still a black background. Not only would it never get reception, it would reboot within two minutes. This cycled until the battery would die. I ended up deleting everything on the device itself in attempt to fix something, not thinking I would delete my back ups and then my ability to ever get my phone past bootloader or recovery. I can still do fastboot commands and change the recovery, but besides that, it's a brick. Any kind of help would mean the world, thanks!
http://forum.xda-developers.com/showthread.php?t=2317989
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage And have no ROM to Flash
Sent from my HTCONE
Im geussing you dont have any other phone to download a rom to an sd card and put it in ur phone?
It would beat having to go thru all the adb setup if your not familiar with adb .
Sent from my SAMSUNG-SGH-I337 using xda premium
It's not a brick until nothing lights up our charges. And since there is no sd slot, that's out. You have access to recovery, you're fine. Download a stable Rom and just like fastboot, do an adb push of the Rom like suggested above. Wipe data, caches, and format system before flashing. No worries. All its not lost.
Sent from my HTCONE using xda premium
propjockey said:
It's not a brick until nothing lights up our charges. And since there is no sd slot, that's out. You have access to recovery, you're fine. Download a stable Rom and just like fastboot, do an adb push of the Rom like suggested above. Wipe data, caches, and format system before flashing. No worries. All its not lost.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
What ??? No sd card slot ? Thats insane.
Sent from my SAMSUNG-SGH-I337 using xda premium
captivated1971 said:
What ??? No sd card slot ? Thats insane.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Wild times were living in.
Sent from my HTCONE using xda premium
Use the tool here http://forum.xda-developers.com/showthread.php?p=40341536 makes everything easy download a Rom and then click sideload Rom. You may have to click install HTC drivers first.
Sent from my HTCONE using xda app-developers app
I smell a couple Trolls in here
No trolling on my end. Just trying to help a guy out. Maybe I'm missing the joke.
Sent from my HTCONE using xda premium
propjockey said:
No trolling on my end. Just trying to help a guy out. Maybe I'm missing the joke.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
Likely he's referring to the "Sent from my Samsung" guy aghast at the lack of an SD card slot.
propjockey said:
No trolling on my end. Just trying to help a guy out. Maybe I'm missing the joke.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
The Troll is the AT&T guy who think's he's being cute trying to tell the OP to put it on an SD card.
Yeah I see that now. Wasn't firing on all cylinders last night.
Sent from my HTCONE using xda premium
bearw815 said:
http://forum.xda-developers.com/showthread.php?t=2317989
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage And have no ROM to Flash
Sent from my HTCONE
Click to expand...
Click to collapse
Any of those adb commands results only with "error: device not found"
This may not be a fix for HTC phones, but on Samsung devices, I've had to uninstall and reinstall drivers several times. Do and uninstall, run a registry cleaner, reboot pc, reinstall drivers, reboot, and try adb again. I used to do that every so often with my Samsung devices that wouldn't be properly detected by my pc. It usually fixed my problem.
Sent from my HTCONE using xda premium
propjockey said:
This may not be a fix for HTC phones, but on Samsung devices, I've had to uninstall and reinstall drivers several times. Do and uninstall, run a registry cleaner, reboot pc, reinstall drivers, reboot, and try adb again. I used to do that every so often with my Samsung devices that wouldn't be properly detected by my pc. It usually fixed my problem.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
How would I get around to doing this on a Mac? It's all I got.
Sorry, I'm not a Mac guy. I couldn't tell you. Can you poach some time on pc at work or a friend's? You may also be able to boot a Linux live disc on your Mac and work from there. Takes some effort, but may help.
Sent from my HTCONE using xda premium
cowkong said:
How would I get around to doing this on a Mac? It's all I got.
Click to expand...
Click to collapse
No offense meant, but that information really needs to be in the first post. It could have made things significantly easier. We also really need to know what ROMs you were trying, because the problems you'r edescribing vaguely sound like you've flashed a GSM ROM somewhere along the line by accident, in which case you will need to RUU (and most of the guides are unfortunately pretty Windows-centric).
Rirere said:
No offense meant, but that information really needs to be in the first post. It could have made things significantly easier. We also really need to know what ROMs you were trying, because the problems you'r edescribing vaguely sound like you've flashed a GSM ROM somewhere along the line by accident, in which case you will need to RUU (and most of the guides are unfortunately pretty Windows-centric).
Click to expand...
Click to collapse
No offense taken. Unfortunately, a Mac is all I'm able to use at the moment. I'm trying to run CleanRom from the sprint htc one development section of this site, so I'm fairly certain it should work. My main problem right now is that using adb commands my phone is not recognized. Using fastboot, though, works absolutely fine to do whatever I need and recognizes my device. I've tried using twrp and clockworkmod recovery touch to sideload any zip file and just won't work. All it says after trying that is "failed to open driver control: no such file or directory".
Please do tell me if any other information would help you help me faster. I don't frequent forums so I'd imagine I'm quite frustrating to work with.
Anybody have any idea?
So I have a Sprint HTC One and I tried flashing a ROM that was for "all other models" and after I flashed it kept on boot looping. So then I wiped everything not thinking about deleting the other ROMs I had on the phone to restore it with. So now I can access fastboot and recovery(twrp 2.6.1.0) but I can't mount an OTG, I can't use adb, and I cant flash through fastboot. I honestly don't know what to do from here so any help would be greatly appreciated.
Herstandez said:
So I have a Sprint HTC One and I tried flashing a ROM that was for "all other models" and after I flashed it kept on boot looping. So then I wiped everything not thinking about deleting the other ROMs I had on the phone to restore it with. So now I can access fastboot and recovery(twrp 2.6.1.0) but I can't mount an OTG, I can't use adb, and I cant flash through fastboot. I honestly don't know what to do from here so any help would be greatly appreciated.
Click to expand...
Click to collapse
You are new to XDA. Please look through the
for a moment, to give yourself an understanding of how XDA works. Please make a specific note of rule #15.
Your thread is now in the correct location.
Thank you.
Herstandez said:
So I have a Sprint HTC One and I tried flashing a ROM that was for "all other models" and after I flashed it kept on boot looping. So then I wiped everything not thinking about deleting the other ROMs I had on the phone to restore it with. So now I can access fastboot and recovery(twrp 2.6.1.0) but I can't mount an OTG, I can't use adb, and I cant flash through fastboot. I honestly don't know what to do from here so any help would be greatly appreciated.
Click to expand...
Click to collapse
Since you can access recovery you need to adb sideload a rom. You can find o ut how to do that here.
If that doesn't work for you (which I suspect it won't) then you will need to take your phone back to stock by applying RUU. there are several ways to do that. Let me know if you need that information and I'll post it here for you.
MrFixit007 said:
Since you can access recovery you need to adb sideload a rom. You can find o ut how to do that here.
If that doesn't work for you (which I suspect it won't) then you will need to take your phone back to stock by applying RUU. there are several ways to do that. Let me know if you need that information and I'll post it here for you.
Click to expand...
Click to collapse
I've tried side loading and my phone isnt recognized by adb :/ and before I rooted my phone I updated to 1.31.651.2 and there isn't an RUU for it yet
Herstandez said:
I've tried side loading and my phone isnt recognized by adb :/ and before I rooted my phone I updated to 1.31.651.2 and there isn't an RUU for it yet
Click to expand...
Click to collapse
Uninstall your HTC drivers. And install the universal naked drivers http://forum.xda-developers.com/showthread.php?t=2263822
Make sure you don't have HTC sync installed, disable any anti virus and firewalls and try to sideload again.
There are ways to RUU on 1.31 but that is way too much hassle when all you need is to install a Rom.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
Uninstall your HTC drivers. And install the universal naked drivers http://forum.xda-developers.com/showthread.php?t=2263822
Make sure you don't have HTC sync installed, disable any anti virus and firewalls and try to sideload again.
There are ways to RUU on 1.31 but that is way too much hassle when all you need is to install a Rom.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
I'm trying that now, I'll let you know what happens, thank you guys so much
Konfuzion said:
Uninstall your HTC drivers. And install the universal naked drivers http://forum.xda-developers.com/showthread.php?t=2263822
Make sure you don't have HTC sync installed, disable any anti virus and firewalls and try to sideload again.
There are ways to RUU on 1.31 but that is way too much hassle when all you need is to install a Rom.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Please excuse me being a n00b, but I'm not too positive on what to do with the files in the zip :/
Herstandez said:
Please excuse me being a n00b, but I'm not too positive on what to do with the files in the zip :/
Click to expand...
Click to collapse
Did you get it figured out? You have to install the drivers manually. If you don't know how, then I would google search "how to manually install device drivers" otherwise you can just use the drivers that install when you install HTC Sync. They work just as well.
What you need to do if adb does not recognize your device is fastboot flash TWRP 2.5.0.0. The older version works. Then you will be able to use adb and you can follow all the steps I outlined here.
MrFixit007 said:
otherwise you can just use the drivers that install when you install HTC Sync. They work just as well.
here.
Click to expand...
Click to collapse
They really don't though...
Sent from my HTCONE using xda app-developers app
Konfuzion said:
They really don't though...
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
For a basic user with only one device, what about them isn't adequate? From everything I have read about them the only benefit is the multi-device capability. The fact that you get the sync program is undesirable, I completely agree, but it does seem to be the simplest way for basic users to access the drivers.
I am truely interested in the differences, as I have read this entire post and not found much enlightenment.
Thanks for the knowledge
MrFixit007 said:
For a basic user with only one device, what about them isn't adequate? From everything I have read about them the only benefit is the multi-device capability. The fact that you get the sync program is undesirable, I completely agree, but it does seem to be the simplest way for basic users to access the drivers.
I am truely interested in the differences, as I have read this entire post and not found much enlightenment.
Thanks for the knowledge
Click to expand...
Click to collapse
Main difference is you can manually install the drivers while the phone is connected via fastboot/abd and avoid the problems people run into trying to get their phones recognized while in fastboot/abd.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
Main difference is you can manually install the drivers while the phone is connected via fastboot/abd and avoid the problems people run into trying to get their phones recognized while in fastboot/abd.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Hmmm. I'll have to keep an eye out for that. I wonder if the difference in drivers would affect adb recognizing TWRP 2.6.1.0. I have seen a lot of people who have to go back to TWRP 2.5.0.0 to get adb to work.
MrFixit007 said:
Hmmm. I'll have to keep an eye out for that. I wonder if the difference in drivers would affect adb recognizing TWRP 2.6.1.0. I have seen a lot of people who have to go back to TWRP 2.5.0.0 to get adb to work.
Click to expand...
Click to collapse
I can't speak for that, but maybe.
Sent from my HTCONE using xda app-developers app
Konfuzion said:
Main difference is you can manually install the drivers while the phone is connected via fastboot/abd and avoid the problems people run into trying to get their phones recognized while in fastboot/abd.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
I tried to manually install the drivers, but no luck, windows says it cant find any drivers
MrFixit007 said:
Hmmm. I'll have to keep an eye out for that. I wonder if the difference in drivers would affect adb recognizing TWRP 2.6.1.0. I have seen a lot of people who have to go back to TWRP 2.5.0.0 to get adb to work.
Click to expand...
Click to collapse
also the device is listed as Android 1.0 and not m7wls, I don't know if that helps
MrFixit007 said:
Hmmm. I'll have to keep an eye out for that. I wonder if the difference in drivers would affect adb recognizing TWRP 2.6.1.0. I have seen a lot of people who have to go back to TWRP 2.5.0.0 to get adb to work.
Click to expand...
Click to collapse
So I was able to sideload a ROM, but now it keeps rebooting and there are no apps installed and it said the system crashed when I finished the setup
MrFixit007 said:
Hmmm. I'll have to keep an eye out for that. I wonder if the difference in drivers would affect adb recognizing TWRP 2.6.1.0. I have seen a lot of people who have to go back to TWRP 2.5.0.0 to get adb to work.
Click to expand...
Click to collapse
I also just wiped everything and reflashed the rom, after flashing it said I still had no os :/
Herstandez said:
I also just wiped everything and reflashed the rom, after flashing it said I still had no os :/
Click to expand...
Click to collapse
how did you get the adb sideload to work in the first place? i'm having the exact same problem with my device at the moment
gbau said:
how did you get the adb sideload to work in the first place? i'm having the exact same problem with my device at the moment
Click to expand...
Click to collapse
I just flashed twrp 2.5.0.0 and it worked, there's a link in this thread to it
Herstandez said:
I just flashed twrp 2.5.0.0 and it worked, there's a link in this thread to it
Click to expand...
Click to collapse
hmmm. i'm already on 2.5.0.0, but it's still not recognizing. I think it might be my drivers because it says "This device cannot start (Code 10)" in device manager
Hey guys, I do no not own this phone (just picked up a Nexus 5) but, my dad does. He has been waiting for MONTHS to get his hands on this. It is his first Android device and he was able to ditch his work iPhone for it. However, he has been having an absolutely horrible experience:
I was remotely walking him through setup (moto transfer with iCloud to gmail account, etc etc).
- He turned on his phone, set up wifi, entered account credentials, played around for a minute or two.
- After this, he was prompted for an update, I told him to accept it
- After he accepted it, the phone WILL NOT TURN on. It boots to the homescreen, says it is "activating" the device, then it needs to restart.
- When it restarts, he sees the following attached screenshot.
I am assuming this was the Kit Kat update. I know tons of people have had problems with this (yes, I read the forums before posting, even though it is not my device). However, everyone with problems seemed to be rooted/not on stock. He is COMPLETELY stock.
If he chooses to reboot normally, he gets the homescreen, activation, then, it turns off and goes back to the attached screen.
If he chooses recovery, it goes back to this screen.
I'm not sure how an OTA could jack a phone up that was completely stock.. But it has happened.
Is there anything I can do remotely to help him start using his new phone? As I said, he has been excited for months for this phone and now just wants to throw it against the wall.
Is this screenshot the fastboot screen? If so, can I use the "fastboot erase cache" command?
Any *detailed* answers would be greatly appreciated... I'd love to get this working for him ASAP.
Thanks everyone!
View attachment 2415287
This is a pretty horrible out of box experience for something he was so excited about. I'm hoping this is something I can just do while remotely controlling his PC... I feel bad for the guy
fastboot erase cache
and then flash a stock recovery
Enviado desde mi XT1052 usando Tapatalk
waiflih said:
fastboot erase cache
and then flash a stock recovery
Enviado desde mi XT1052 usando Tapatalk
Click to expand...
Click to collapse
Not having this phone myself, how do I flash a recovery if I can't access current recovery or boot? Can I flash with a locked bootloader? Is the screen my dad is seeing the fastboot screen?
Any ideas how a stock out of the box phone would encounter this?
Thanks!
Sorry it's just hard to not have a device and jump into this when there are a million threads and it is completely different than any device I've owned (also I have no hands on time with it).
Thanks again. The more details the better so that I can do this remotely.
Sent from my Nexus 5 using XDA Premium 4 mobile app
yes that screen is fastboot mode, so u can download the files for ur rom here
http://sbf.droid-developers.org/ghost/list.php
and use fastboot to flash only recovery
Enviado desde mi XT1052 usando Tapatalk
Ok. I will have to figure out how to flash sbfs via fastboot then. I'm assuming it is a simple set of commands. I will try and find a tutorial when I am not driving. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
EmperorX said:
Ok. I will have to figure out how to flash sbfs via fastboot then. I'm assuming it is a simple set of commands. I will try and find a tutorial when I am not driving. Thanks
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Which model/carrier of phone does your dad have?
Xatt said:
Which model/carrier of phone does your dad have?
Click to expand...
Click to collapse
He's on Verizon, 16gb.
So confused as to how this happens fresh out of the box. Don't know how it's possible. I'm determined to fix it for him today though so he doesn't have to wait even longer
Sent from my Nexus 5 using XDA Premium 4 mobile app
If he just bought it, why are you messing around with this? Take it back to the retailer you bought it from and tell then what happened... Get a new phone...
AT&T Moto X rocking rooted 4.4
theraffman said:
If he just bought it, why are you messing around with this? Take it back to the retailer you bought it from and tell then what happened... Get a new phone...
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
waiflih said:
yes that screen is fastboot mode, so u can download the files for ur rom here
http://sbf.droid-developers.org/ghost/list.php
and use fastboot to flash only recovery
Enviado desde mi XT1052 usando Tapatalk
Click to expand...
Click to collapse
I'm assuming I can use any of the builds from verizon there? I'd like to get him to update OTA and see if it works this time or not... Was thinking about flashing one of the three 4.2.2 ones
EmperorX said:
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
EmperorX I work for Moto. If you wouldn't mind providing the IMEI I'll get our engineers to take a look. You can PM me. Thanks!
I found this toolkit:
However, i'm assuming the fastboot menu will not work to just flash stock as you need to be in "Android or hboot"
The fastboot screen I took the picture of is not the same thing as hboot correct?
They are interchangeable terms. Hboot refers typically to an HTC bootloader
gunnyman said:
They are interchangeable terms. Hboot refers typically to an HTC bootloader
Click to expand...
Click to collapse
Awesome, looks like I may be able to fix this for him after all. Just need to remotely get androidsdk and adb setup on his computer with RSDlite as backup if this toolkit doesn't work and I *should* be able to make this happen. I think i've got enough info to do this now. Thanks guys!
EmperorX said:
He got it customized from MotoMaker... If it's a relatively simple fix (and it's not a hardware issue) I'd rather do it myself so he doesn't have to wait yet again for who knows how long.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Gotcha, makes sense not to want to go through all that. Sorry this happened to your dad. First I've heard of an issue this big on the moto x.
AT&T Moto X rocking rooted 4.4
theraffman said:
Gotcha, makes sense not to want to go through all that. Sorry this happened to your dad. First I've heard of an issue this big on the moto x.
AT&T Moto X rocking rooted 4.4
Click to expand...
Click to collapse
He was on the phone with Motorola "tier 2" support this morning for 3 hours. Their solution was to order a new phone and expedite shipping and return the old one when it gets here. I'm going to try this way first. They said this happens to "1 in 10,000" people. Lol, he's a lucky guy!
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
EmperorX said:
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
Click to expand...
Click to collapse
Sounds like the phone's partitions are all jacked up. Get a new phone is the solution.
EmperorX said:
Well, now it's stuck on the fastboot screen with the following error:
No valid PIV block in SP for system
piv validation failed (system)
boot up failed
-__-
Click to expand...
Click to collapse
what probably happened was your dad never activated the phone then tried to take an ota or something like that and it got all jacked up. Alternatively, he could have (for some reason) gotten the 4.4 OTA even though the phone was on original stock FW. This could have f'd the phone up if it skipped the 4.2.2 OTA. If you need to help you dad out, download teamviewer or logmein (remote computer access programs) and just guide him through when to plug the phone in etc.
Not sure about the error you are getting but it could be because you are flashing the wrong FW for the phone, possibly an older FW or an updated FW and the order you are flashing it could be causing the error. You can fix this relatively easily if you were more familiar with fastboot. I can try and walk you through some stuff as well on gchat if you need some help. I could also remote into your dads computer and do everything that needs to be done (he could then remove my ability to remote in clearly). All that being said Im fairly busy so just answering some questions for you would be easier but more time consuming for your dad. For starters, you probably should be flashing the 4.2.2 FW found on sbf. it is the middle fw for verizon on the list. You also can probably just use rsdlite since he hasn't set the phone up. It is super easy. Just go to the thread for rsd lite back to 100% stock and you will be good to go. Then make sure he activates and sets the phone up and everything before he takes the OTA this time.
Introduction
This kit is designed to update Stock rooted Nexus 5 devices to Android 4.4.4 while retaining all user data as well as root permissions. This will also work on non-rooted devices with an unlocked Bootloader.
Before you Start
# This kit is designed to update without wipe but anything is possible, so I strongly urge you
to back up all data. Also I am not liable for any lost information.
# Please configure all ADB drivers
# Place phone in Fastboot mode. Power down the device; (Press and hold Power + Volume Down)
until the device boots into Fastboot.
# Extract all files, open the Unfathomable EXE file in the provided folder and follow the prompts Carefully.
Instructions
Run the EXE. After your device reboots, boot your Nexus into recovery. TWRP recovery should boot. Select the reboot option and reboot system.
You will be prompted "Swipe to flash SuperSU". This will restore all Root permissions.
*Also in the event that your device is stuck in a bootloop, just wipe the cache and you should be good to go!
Downloads
Nexus 5 Auto Updater 4.4.4 by Unfathomable.zip
The Kit can also be downloaded at this Dev Host URL
http://d-h.st/mRY
[Nexus 5 Auto Updater 4.4.4 By Unfathomable.zip - 451.78 MB]
Other Information
The Nexus 7 Wi-Fi Auto-Updater 4.4.4 can be found at this URL
http://forum.xda-developers.com/showthread.php?t=2791773
XDA:DevDB Information
Nexus 5 Auto-Updater, Tool/Utility for the Google Nexus 5
Contributors
Unfathomable
Version Information
Status: Beta
Created 2014-06-29
Last Updated 2014-06-29
Got to be one of the slowest downloads for such a small file in the history of man.
Painful to say the least.
For me, almost half a gig is something other than small.
TiltedAz said:
For me, almost half a gig is something other than small.
Click to expand...
Click to collapse
Still slow to download. Had faster larger files.
Sent from my SM-G900F using XDA Premium 4 mobile app
@home said:
Still slow to download. Had faster larger files.
Sent from my SM-G900F using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And you're complaining in the OP's thread, why? Blame Dev-Host not them. Lol.
Not complaining, just stating a fact.
Sent from my SM-G900F using XDA Premium 4 mobile app
With all do respect to opinions I would greatly appreciate if this thread is used for and remains a hub for questions and support. With that being said I have taken the liberty of uploading the file into XDA's server for downloading. Please respect my wishes as I have taken my own personal time to provide the community with this tool and many more to come. Thank you all! If you have any concerns, feedback or need support please feel free to contact me at [email protected].
Sent from my Nexus 5 using XDA Premium 4 mobile app
Thanks for do us a easy way to update to v4.4.4 with stock rom! :good:
Just want to thank the op for making it so easy
It's a good idea but a little long winded when you can just flash a rooted stock ROM.zip via recovery.
Sent from my Nexus 5 using Tapatalk
Hello guys,
I am a newbie in this. I have Nexus 5 with Stock rooted 4.4.2. Will this method work for me to update to 4.4.4?
Thank you!
miserableboy said:
Hello guys,
I am a newbie in this. I have Nexus 5 with Stock rooted 4.4.2. Will this method work for me to update to 4.4.4?
Thank you!
Click to expand...
Click to collapse
Yes, it is not a requirement to be running 4.4.3. Let me know if you have any difficulties.
Out of Memory
I'm getting "error: out of memory" shortly after the update starts. It sends and writes the bootloader then reboots into the bootloader and gives me the error. What am I doing wrong?
ddukatz said:
I'm getting "error: out of memory" shortly after the update starts. It sends and writes the bootloader then reboots into the bootloader and gives me the error. What am I doing wrong?
Click to expand...
Click to collapse
A couple troubleshooting methods to help with your issue. First try booting into the recovery and wiping cache. Also try using a different USB cable as well as a different port. If this does not resolve your issue please contact me and I will find a resolution.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Unfathomable said:
A couple troubleshooting methods to help with your issue. First try booting into the recovery and wiping cache. Also try using a different USB cable as well as a different port. If this does not resolve your issue please contact me and I will find a resolution.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Same thing here. Already wiped cache but no memory message appears.
Unfathomable said:
A couple troubleshooting methods to help with your issue. First try booting into the recovery and wiping cache. Also try using a different USB cable as well as a different port. If this does not resolve your issue please contact me and I will find a resolution.
Click to expand...
Click to collapse
Not sure which one but one of these things fixed it for me.
Thanks!
ddukatz said:
Not sure which one but one of these things fixed it for me.
Thanks!
Click to expand...
Click to collapse
Thank you for bringing the issue to my attention, and no problem I'm glad I was able to help.
I also don't want to offend the developer as he did spend a lot of time on this. I do respect him, but I wanted to share my opinion. The last couple of OTA's I just downloaded the update straight from the OTA thread to my phone, I then flashed them in TWRP. I didn't loose TWRP and it even gives an option to install SuperSU binaries if it doesn't see them.
However, I do want to stay on topic. I'm curious, for people who use xposed, would this tool allow an update without needing to uninstall modules? I'm just trying to see the differences between your method and flashing an OTA. Also, would people with custom kernels be able to update as well? If they can, then this would prove useful for those with custom kernels.
Again, I don't mean to offend the OP. I'm just curious about the differences/benefits.
PsychDrummer said:
I also don't want to offend the developer as he did spend a lot of time on this. I do respect him, but I wanted to share my opinion. The last couple of OTA's I just downloaded the update straight from the OTA thread to my phone, I then flashed them in TWRP. I didn't loose TWRP and it even gives an option to install SuperSU binaries if it doesn't see them.
However, I do want to stay on topic. I'm curious, for people who use xposed, would this tool allow an update without needing to uninstall modules? I'm just trying to see the differences between your method and flashing an OTA. Also, would people with custom kernels be able to update as well? If they can, then this would prove useful for those with custom kernels.
Again, I don't mean to offend the OP. I'm just curious about the differences/benefits.
Click to expand...
Click to collapse
It flashes the image not an OTA
Sent from my Nexus 5 using Tapatalk
rootSU said:
It flashes the image not an OTA
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Oh ok. That would make sense why the file is so big. So then, isn't this basically deleting the -w from the batch file and flashing normally? Well and retaining root.