Related
Okay,
So I have a Moto G. I have TWRP installed and I accidentally deleted my OS, I have no ROM installed and my computer will not recognize the device. Can anyone help? Please and thank you.
SoloDoloDoe said:
Okay,
So I have a Moto G. I have TWRP installed and I accidentally deleted my OS, I have no ROM installed and my computer will not recognize the device. Can anyone help? Please and thank you.
Click to expand...
Click to collapse
i dont own the device but if you download adb (android development). go to cmd and type adb devices
After you have donwloaded adb
Go to my computer....system properties ..... advanced system setting.... advanced.... enviromentel variables....path.. add the folder at the end with (;C:\(user)\location of adb)
device offliine
xmattjus said:
Just download the ROM you want to install, reboot to recovery, plug the usb cable and type "adb push (rom name).zip /sdcard/" in a terminal/console window on your PC - without quotes. You need to have installed adb, if you don't have it already just search for an installation guide with Google.
Click to expand...
Click to collapse
when i plug my device to the pc and i type adb devices i see my device listed there but it says offline! what can i do?
You need yo get the adb drivers. Goto motorola's website and install the software for our device
Sent from my Moto G using Tapatalk
jglm4u said:
when i plug my device to the pc and i type adb devices i see my device listed there but it says offline! what can i do?
Click to expand...
Click to collapse
To me the same story.I have TWRP installed and I accidentally deleted my OS.
When i plug my device to the pc and i type adb devices i see my device listed there but it says offline. NOT helping adb/USB drivers.
Answer by Motorola Support:
"We regret that after unlocking the bootloader and subsequent modification of your terminal software warranty is voided.
Also, in your specific case, we could not guarantee that your phone can be repaired. If the PCB has been damaged, the cost of repair would exceed the value of the phone, and therefore it would be irreparable."
put a usb otg with the rom in it and flash so it will be fixed!
provalpaypal said:
Answer by Motorola Support:
"We regret that after unlocking the bootloader and subsequent modification of your terminal software warranty is voided.
Also, in your specific case, we could not guarantee that your phone can be repaired. If the PCB has been damaged, the cost of repair would exceed the value of the phone, and therefore it would be irreparable."
Click to expand...
Click to collapse
This shows, in order to become a customer care executive, you need not have much knowledge about your product, and intellect is not required at all. [emoji1] [emoji1] [emoji1]
SoloDoloDoe said:
Okay,
So I have a Moto G. I have TWRP installed and I accidentally deleted my OS, I have no ROM installed and my computer will not recognize the device. Can anyone help? Please and thank you.
Click to expand...
Click to collapse
here you go this will help u to flash a rom onto your phone thank me later https://www.youtube.com/watch?v=YmCBVTgSXnY
use this tutorial, i recovered my phone with the same problem of yours with this! http://forum.xda-developers.com/showthread.php?t=2542219
SoloDoloDoe said:
Okay,
So I have a Moto G. I have TWRP installed and I accidentally deleted my OS, I have no ROM installed and my computer will not recognize the device. Can anyone help? Please and thank you.
Click to expand...
Click to collapse
Just flash stock ROM via bootloader.
Get a rom flashable zip then you can "adb sideload" the file to recovery!
device not found
xmattjus said:
Just download the ROM you want to install, reboot to recovery, plug the usb cable and type "adb push (rom name).zip /sdcard/" in a terminal/console window on your PC - without quotes. You need to have installed adb, if you don't have it already just search for an installation guide with Google.
Click to expand...
Click to collapse
Well i tried to flash the rom in your way but it is showing an error message: device not found and when i tried to find my device through adb device command... it is showing zero devices attached... pls help and revert asap
You can also try flashing a stock ROM via mfastboot or fastboot commands.
I don't know if this will be any help but sometimes even though adb recognizes my device it says device not found/device offline.
I plug the phone in and type "fastboot reboot-bootloader" it reboots to bootloader and everything works from that point on.
bro,i my adb it shows *cannot read 'sideload'* then what should i command
pliz help btw m using custom rom BissPop3.2
SoloDoloDoe said:
Okay,
So I have a Moto G. I have TWRP installed and I accidentally deleted my OS, I have no ROM installed and my computer will not recognize the device. Can anyone help? Please and thank you.
Click to expand...
Click to collapse
I know this is an old question, but just to share my experience, me too coincidently deleted OS from TWRP. I tried using ADB, but it was not detecting the phone. Then I copied custom ROM (CM 12.1 in my case) to USB drive, connected it with my phone using USB OTG and flashed the ROM. It worked like a charm
SoloDoloDoe said:
Okay,
So I have a Moto G. I have TWRP installed and I accidentally deleted my OS, I have no ROM installed and my computer will not recognize the device. Can anyone help? Please and thank you.
Click to expand...
Click to collapse
boot in twrp and plug the phone to pc.you can put rom trough mtp.install motorola drivers maybe that's the problem.works fine for me.
you can reboot to twrp and it have a mount function
Gill Android said:
I know this is an old question, but just to share my experience, me too coincidently deleted OS from TWRP. I tried using ADB, but it was not detecting the phone. Then I copied custom ROM (CM 12.1 in my case) to USB drive, connected it with my phone using USB OTG and flashed the ROM. It worked like a charm
Click to expand...
Click to collapse
i also deleted my os. and tried to flash cm13 from usb otg. but it just stuck on 'patching system image unconditionaly' for almost an hour.
JoshuaUngson said:
i also deleted my os. and tried to flash cm13 from usb otg. but it just stuck on 'patching system image unconditionaly' for almost an hour.
Click to expand...
Click to collapse
Maybe bad download. Try downloading again or try some older built.
I bricked my Nexus 5 by installing the kernal from touchcontrol.
I can get into recovery mode.
I can not mount the USB storage or access any of my phones files
I've tried installing ADB drivers but that didn't help.
Anyone know what I should do to fix this?
BleachFan21 said:
I bricked my Nexus 5 by installing the kernal from touchcontrol.
I can get into recovery mode.
I can not mount the USB storage or access any of my phones files
I've tried installing ADB drivers but that didn't help.
Anyone know what I should do to fix this?
Click to expand...
Click to collapse
Download the stock kernel zip from here https://www.androidfilehost.com/?fid=23269279319202404 and place it in the fastboot folder. Then reboot in recovery and choose adb sideload. Open cmd and type : adb sideload namekernel.zip and press enter and that should do it, then reboot.
gee2012 said:
Download the stock kernel zip from here and place it in the fastboot folder. Then reboot in recovery and choose adb sideload. Open cmd and type : adb sideload namekernel.zip and press enter and that should do it, then reboot.
Click to expand...
Click to collapse
How do I place it in the fastboot folder?
BleachFan21 said:
How do I place it in the fastboot folder?
Click to expand...
Click to collapse
Copy it to the android-sdk/platform-tools
gee2012 said:
Copy it to the android-sdk/platform-tools
Click to expand...
Click to collapse
Is that a type of program? USB isn't working on my phone as even though it makes the connecting sound when I plug it in it's not appearing on the explorer
BleachFan21 said:
Is that a type of program? USB isn't working on my phone as even though it makes the connecting sound when I plug it in it's not appearing on the explorer
Click to expand...
Click to collapse
Sorry, you`re right. Well without usb you can`t do anything. Have you made a nandroid backup to restore in recovery?
gee2012 said:
Sorry, you`re right. Well without usb you can`t do anything. Have you made a nandroid backup to restore in recovery?
Click to expand...
Click to collapse
no
BleachFan21 said:
no
Click to expand...
Click to collapse
Well then there is nothing i can tell that can help you mate, good luck
Hello,
When the phone is in recovery mode, the file explorer won't show up with your nexus files... The fact that a sound is coming proves that the phone is being detected...
If you have setup a working adb environment you can follow what @gee2012 has said and sideload the kernel and flash it... If you haven't then download the android sdk and make sure you have downloaded the usb_driver package as well...
BleachFan21 said:
no
Click to expand...
Click to collapse
First, don't yet think your phone it's bricked. The actual solution is to get the proper driver on the computer. Remember that nexus 5 does not have Sdcard and there's not way to mount to the computer via recovery. Only ADB PUSH and ADB SIDELOAD will put a Rom into your phone.
You have to check on device manager to see the status of the driver. if t shows as Nexus 5, you will have to update the driver to and adb compatible one. If it says ADB........ then, you are good to go
EDIT: @vin4yak, one day I'll go to ninja school too
1.) If your device is actually bricked then a USB cable will do you absolutely no good. Fixing a "bricked" device is something that will need to be JTAG'd for it to work again. I think you might be mistaken about what a bricked device is. Its pretty hard to brick a nexus device so I highly doubt you're device is bricked.
2.) You have to get into fastboot mode. Just search for how to do so. Then you can flash the stock img's through fastboot and you'll be back in business. I have no clue about what drivers you'll need for your setup as I haven't run windows in 9 years or so. Just get the drivers, fastboot, and get your nexus back.
Why don't you just flash a boot.img from the stock rom? Or going back to stock?
You cannot mount sdcard to the pc in recovery. You have to use adb push or adb sideload.
To make adb work in recovery you need naked usb drivers 0.73.
Then you can adb sideload a rom, or push a rom to /sdcard.
Anyway download my attachment, put your phone to fastboot mode and double click on flash.bat then report me back
Check out this thread. If you can boot into recovery, then you should be able to boot into fastboot and restore your N5 back to stock.
http://forum.xda-developers.com/showthread.php?t=2513701
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
Sent from my Nexus 5 using Tapatalk
Nexus 5 wont boot into Paranoid android, i was obviously rooted with CWM installed, i wiped the device installed a fresh copy of paranoid android then decided to do a internal storage wipe the fastboot oem unlock way. I did the wipe and rebooted but its stuck in Paranoid androids bootanimation? Can anyone help here?
Garner said:
Nexus 5 wont boot into Paranoid android, i was obviously rooted with CWM installed, i wiped the device installed a fresh copy of paranoid android then decided to do a internal storage wipe the fastboot oem unlock way. I did the wipe and rebooted but its stuck in Paranoid androids bootanimation? Can anyone help here?
Click to expand...
Click to collapse
Push or sideload a custom rom or flash the stock image i`d say. Or try a data factory reset in recovery first.
gee2012 said:
Push or sideload a custom rom or flash the stock image i`d say.
Click to expand...
Click to collapse
Thanks, I have done it the above way for some time now with various nexus devices, cant understand why its failed this time?
Garner said:
Thanks, I have done it the above way for some time now with various nexus devices, cant understand why its failed this time?
Click to expand...
Click to collapse
Maybe the OS got corrupted by the lock/unlock action. I personaly would never recommend that anyway.
gee2012 said:
Maybe the OS got corrupted by the lock/unlock action. I personaly would never recommend that anyway.
Click to expand...
Click to collapse
Possibly, what i did notice was that when it entered recovery after oem unlock CWM threw alot of mount errors up
Garner said:
Possibly, what i did notice was that when it entered recovery after oem unlock CWM threw alot of mount errors up
Click to expand...
Click to collapse
I would start from scratch and flash the stock image including userdata.img for a full wipe to erase all errors.
gee2012 said:
I would start from scratch and flash the stock image including userdata.img for a full wipe to erase all errors.
Click to expand...
Click to collapse
Gather i need the stock image from here https://developers.google.com/android/nexus/images#hammerhead never had to return to stock like this before
Garner said:
Gather i need the stock image from here https://developers.google.com/android/nexus/images#hammerhead never had to return to stock like this before
Click to expand...
Click to collapse
Yup KOT49H, good luck mate. Hope that will fix it.
gee2012 said:
Yup, good luck mate. Hope that will fix it.
Click to expand...
Click to collapse
Quick question can i flash paranoid android from adb sideload never used that feature before?
Garner said:
Nexus 5 wont boot into Paranoid android, i was obviously rooted with CWM installed, i wiped the device installed a fresh copy of paranoid android then decided to do a internal storage wipe the fastboot oem unlock way. I did the wipe and rebooted but its stuck in Paranoid androids bootanimation? Can anyone help here?
Click to expand...
Click to collapse
You have to do a facotry reset in cwm. I dont really know how cwm works but in twrp there are two options to wipe /data. The first ine actually wipes /data and reformats it while the second option just delete every file and folder except the /data/media folder which is the sdcard. You need to find the first option in cwm. Normally after unlock bl you should let the android boot up because the stock recovery does the formation right after the first boot of oem unlock.
Tapatalk-kal küldve az én Nexus 5-el
Garner said:
Quick question can i flash paranoid android from adb sideload never used that feature before?
Click to expand...
Click to collapse
Sure, but you would also flash the Gapps then in sideload too i guess. I would flash stock first however to restore the phone and partitions back to normal.
bitdomo said:
You have to do a facotry reset in cwm. I dont really know how cwm works but in twrp there are two options to wipe /data. The first ine actually wipes /data and reformats it while the second option just delete every file and folder except the /data/media folder which is the sdcard. You need to find the first option in cwm. Normally after unlock bl you should let the android boot up because the stock recovery does the formation right after the first boot of oem unlock.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Did fastboot reboot but it just booted to recovery
Garner said:
Did fastboot reboot but it just booted to recovery
Click to expand...
Click to collapse
Try fastboot reboot bootloader.
Garner said:
Did fastboot reboot but it just booted to recovery
Click to expand...
Click to collapse
I think that fastboot reboot command overwrote the commands stored in the /misc partition which tells the phone to start recovery and to a factory reset.
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
I think that fastboot reboot command overwrote the commands stored in the /misc partition which tells the phone to start recovery and to a factory reset.
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Now when it goes to reboot it says root is missing? root device?
Garner said:
Now when it goes to reboot it says root is missing? root device?
Click to expand...
Click to collapse
Yes, press install root if you flashed PA.
Garner said:
Now when it goes to reboot it says root is missing? root device?
Click to expand...
Click to collapse
You wiped /system too that is the reasone why the recovery tells you to install root and you stucked at pa boot logo. here are the 3 options you can do now:
adb push a rom zip to /sdcard
turn on adb sideload in recovery and adb sideload a rom zip
Enter to fastboot and flash factory images back.
for both adb you have to be in recovery and you have to install universal naked usb drivers 0.73 http://forum.xda-developers.com/showthread.php?t=2386956
Fot fastboot to flash factory images you need the latest usb drivers from google http://developer.android.com/sdk/win-usb.html and you need a factory image https://developers.google.com/android/nexus/images
All three method need to have adb and fastboot exes to be added to your path. If you havent done that read this topic http://forum.xda-developers.com/showthread.php?t=2588979
To flash factory images extract the downloaded file and double click on flash-all.bat
Tapatalk-kal küldve az én Nexus 5-el
gee2012 said:
Yes, press install root if you flashed PA.
Click to expand...
Click to collapse
Stuck on google logo just waiting for the official image to download 1 to 2 hours lol
bitdomo said:
You wiped /system too that is the reasone why the recovery tells you to install root and you stucked at pa boot logo. here are the 3 options you can do now:
adb push a rom zip to /sdcard
turn on adb sideload in recovery and adb sideload a rom zip
Enter to fastboot and flash factory images back.
for both adb you have to be in recovery and you have to install universal naked usb drivers 0.73 http://forum.xda-developers.com/showthread.php?t=2386956
Fot fastboot to flash factory images you need the latest usb drivers from google http://developer.android.com/sdk/win-usb.html and you need a factory image https://developers.google.com/android/nexus/images
All three method need to have adb and fastboot exes to be added to your path. If you havent done that read this topic http://forum.xda-developers.com/showthread.php?t=2588979
To flash factory images extract the downloaded file and double click on flash-all.bat
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Turned on adb sideload tried "adb sideload para" but cmd does not understand the command?
bitdomo said:
for both adb you have to be in recovery and you have to install universal naked usb drivers 0.73 http://forum.xda-developers.com/showthread.php?t=2386956
All three method need to have adb and fastboot exes to be added to your path. If you havent done that read this topic http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
@Garner
Tapatalk-kal küldve az én Nexus 5-el
Hi, I was trying to flash stock 4.4.3 to my Nexus 5 using this method. Something happened and now it won't boot up past the "Google" splash screen with the padlock.
I decided to try using Nexus Root Tool v1.8.3 to flash it, using Back to Stock > Current status: Soft-Bricked/Bootloop. I saw that there is an older thread where someone had a similar issue, but I'm still fairly new (I'd say intermediate level) at this stuff and I don't understand what they're saying and I'm on the verge of freaking out because I do everything through my phone.
I can still access the Bootloader and Recovery, so I believe there's hope, but I keep trying over and over again and the command line keeps spitting out errors, then fastboot crashes. Please help! :crying:
I tried method #2 in this guide on XDA, and fastboot picks up my phone, but some of the commands are failing, stating "FAILED (command write failed (Invalid argument))" or "FAILED (command write failed (No such device or address))" or the error mentioned in the thread title.
After trying it, my phone is still bootlooping.
seems odd that bootloader and recovery flash fine
try, long shot, fastboot format userdata obviously you will lose data, but I think that's gone anyway.
or maybe better fastboot flash a custom recovery and boot to it via fastboot, see if you can repair from there with some adb commands
otherwise it seems your partitions are messed up, I think maybe a full .tot flash with lgtool is in order
175
meangreenie said:
seems odd that bootloader and recovery flash fine
try, long shot, fastboot format userdata obviously you will lose data, but I think that's gone anyway.
or maybe better fastboot flash a custom recovery and boot to it via fastboot, see if you can repair from there with some adb commands
otherwise it seems your partitions are messed up, I think maybe a full .tot flash with lgtool is in order
Click to expand...
Click to collapse
I tried
Code:
fastboot format userdata <directory>\userdata.img
and it failed (you can see it in the 2nd screenshot in the 2nd post). Don't I need to be rooted to be able to flash a custom recovery? I'd successfully unrooted before this mess occurred.
What's .tot flashing about? I'm willing to try that if flashing custom recovery is a lost cause.
you can flash a custom recovery as long as your unlocked, root is not needed.
looking at your screen shots shows that recovery is flashing ok.
Hi! You could try to upgrade your fastboot and adb binaries with your drivers as well. Use usb2.0 port only, and restart your PC
Tapatalk-kal küldve az én Nexus 5-el
meangreenie said:
you can flash a custom recovery as long as your unlocked, root is not needed.
looking at your screen shots shows that recovery is flashing ok.
Click to expand...
Click to collapse
I got TWRP v2.7.1.1 installed. How do I do repairs using adb commands?
bitdomo said:
Hi! You could try to upgrade your fastboot and adb binaries with your drivers as well. Use usb2.0 port only, and restart your PC
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Hi. How do I upgrade the binaries? I believe everything is up-to-date, though. I'd installed everything fresh yesterday, for the purpose of flashing 4.4.3.
Also, in case it's important, TWRP showed this (see attachment):
Dalae said:
I got TWRP v2.7.1.1 installed. How do I do repairs using adb commands?
Hi. How do I upgrade the binaries? I believe everything is up-to-date, though. I'd installed everything fresh yesterday, for the purpose of flashing 4.4.3.
Click to expand...
Click to collapse
Latest drivers for phone http://developer.android.com/sdk/win-usb.html
Latest adb and fastboot in the sdk/platform tools folder in android sdk http://developer.android.com/sdk/index.html. Copy use those binaries for the flashing process.
Oh sorry as I see from the pictures you already have teh latest of everything. You could try this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
I don't know if you can repair it with adb commands, but there was a thread on the general section which had a lot of info on repairing the data partition, you might want to have a search for it.. I can't remember what it was called, sorry. .. maybe something like... corrupt data recovery
otherwise the tot method linked above should get you up and running quickly.
bitdomo said:
Latest drivers for phone http://developer.android.com/sdk/win-usb.html
Latest adb and fastboot in the sdk/platform tools folder in android sdk http://developer.android.com/sdk/index.html. Copy use those binaries for the flashing process.
Oh sorry as I see from the pictures you already have teh latest of everything. You could try this http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Click to expand...
Click to collapse
meangreenie said:
I don't know if you can repair it with adb commands, but there was a thread on the general section which had a lot of info on repairing the data partition, you might want to have a search for it.. I can't remember what it was called, sorry. .. maybe something like... corrupt data recovery
otherwise the tot method linked above should get you up and running quickly.
Click to expand...
Click to collapse
Okay, thanks. I'll try the LG Flashtool. If I have any questions, I'll ask here. Either way, I'll post results.
I flashed the firmware and everything seems hunky-dorey. :victory: Thanks for your help, both of you. I realize that restoring device factory version is optional, but what's it about? As in, under what circumstances would I want to do this?
PS: When my phone booted up, it showed that the 4.4.3 OTA update is available. If I were to update would that have any effect on my device factory version?
Dalae said:
I flashed the firmware and everything seems hunky-dorey. :victory: Thanks for your help, both of you. I realize that restoring device factory version is optional, but what's it about? As in, under what circumstances would I want to do this?
PS: When my phone booted up, it showed that the 4.4.3 OTA update is available. If I were to update would that have any effect on my device factory version?
Click to expand...
Click to collapse
you have to restore your original factory device version if it bothers you that it is not your original . Btw the name of the tot file will be your new device factory version. if you flash a tot file which has the same name as your original factory device version then you have to do nothing
Tapatalk-kal küldve az én Nexus 5-el
bitdomo said:
you have to restore your original factory device version if it bothers you that it is not your original . Btw the name of the tot file will be your new device factory version. if you flash a tot file which has the same name as your original factory device version then you have to do nothing
Tapatalk-kal küldve az én Nexus 5-el
Click to expand...
Click to collapse
Ah, alright. Thanks! I don't really care that it's not the original, as long as it doesn't have any undesirable effects. And, just for the heck of it, here's what was in the log regarding the original and the result:
[15:46: 7] 11. device factory version = LGD820AT-00-V10a-NXS-XX-OCT-09-2013-KQS81M-USER-32G+0
[15:46: 7] 12. device factory out version = LGD820AT-00-V10a-NXS-XX-OCT-03-2013-KRS59B-FACTORY-XXG+0
I installed the 4.4.3 OTA and it went smoothly. I'm free to unlock my bootloader, root, and install custom recovery now, correct?
nice to see your up and running
yes. now you can unlock and root
just one thing to watch out for, after running the unlock command you must let your phone fully boot once. this is because the original recovery is needed to complete the process during boot up.
then your free to install a custom recovery and flash a root zip, supersu by chain fire recommended by me. then when booted install and run busybox from the playstore
Great, thanks! I rooted using NRT, which installed BusyBox Free for me.
Sent from my Nexus 7 using Tapatalk
I have been getting this kinda crap on my Nexus 7 2013 and Nexus Player when I upgrade between OS Versions.
The Fix is to open up the system update ZIP file, extract the individual partitions and flash SYSTEM.img manually
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
I think it has to do with a Fastboot memory limitation or something. It could be an older version, but it seems it just can't flash everything at once. If you separate it out and flash each one separately, it works fine.
Hey all, so I bought a nexus 5 about a week ago(loving it!) and it came with boot loader unlocked. Basically I'm tryna install twrp through fastboot so I can flash SuperSU and root. Andriod version is 5.1 lollipop and I'm trying to install 2.8.5.2 twrp. I can get cmd to recognize the andriod SDK platform and is recognizes the fastboot recovery command but it says waiting for device. Do I press start on my phone or should it do this itself?
KentuckyGuy447 said:
Hey all, so I bought a nexus 5 about a week ago(loving it!) and it came with boot loader unlocked. Basically I'm tryna install twrp through fastboot so I can flash SuperSU and root. Andriod version is 5.1 lollipop and I'm trying to install 2.8.5.2 twrp. I can get cmd to recognize the andriod SDK platform and is recognizes the fastboot recovery command but it says waiting for device. Do I press start on my phone or should it do this itself?
Click to expand...
Click to collapse
You have to install drivers from here first: http://developer.android.com/sdk/win-usb.html
Is your phone booted to fastboot?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Ben36 said:
Is your phone booted to fastboot?
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
Fastboot is waiting on device if there isn't wright driver installed.
Enable use debugging
Install drivers and adb using adbinstaller.exe. Google it.
Then try "adb devices" in cmd
Yes my device was booted to fastboot. I already installed the android SDK, and the PC already installed driver. I'm gonna enable USB debugging as I forgot though. Will look into all of this and let you guys know. Just curious as to what is the start option in the fastboot menu on my phone?
Turns out I do need the drivers for adb. Thanks zagorteney! I'm gonna install them and see what happens.
Adb is irrelevant in fastboot mode
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
KentuckyGuy447 said:
Turns out I do need the drivers for adb. Thanks zagorteney! I'm gonna install them and see what happens.
Click to expand...
Click to collapse
Ben36 said:
Adb is irrelevant in fastboot mode
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
That's true. Adb and fastboot are two different things. In fastboot you don't need USB debugging enabled. You need to install drivers, when you are allready in fastboot mode (booted in bootloader).
zagorteney said:
That's true. Adb and fastboot are two different things. In fastboot you don't need USB debugging enabled. You need to install drivers, when you are allready in fastboot mode (booted in bootloader).
Click to expand...
Click to collapse
OK so when I use the adb devices command it doesn't pick up my device? Do I have to press the start option on my phone in bootloader? Also as I said when I use the fastboot recovery command it just keeps saying waiting for device. Should I press start on my device in the bootloader mode?
Try fastboot devices and see what it says
Sent from my Nexus 5 using Tapatalk
KentuckyGuy447 said:
OK so when I use the adb devices command it doesn't pick up my device? Do I have to press the start option on my phone in bootloader? Also as I said when I use the fastboot recovery command it just keeps saying waiting for device. Should I press start on my device in the bootloader mode?
Click to expand...
Click to collapse
If the phone is running normally, try the "adb devices" command and see if your device is recognized. Or if booted in to the bootloader, do "fastboot devices". Either way you should see your device as an alphanumeric string. If either recognizes your device, you have the correct drivers installed.
You will fastboot flash a custom recovery in bootloader mode.
Lots on good info in these threads:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
upndwn4par said:
If the phone is running normally, try the "adb devices" command and see if your device is recognized. Or if booted in to the bootloader, do "fastboot devices". Either way you should see your device as an alphanumeric string. If either recognizes your device, you have the correct drivers installed.
You will fastboot flash a custom recovery in bootloader mode.
Lots on good info in these threads:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Away from a working PC for a couple of days but when I get access to one, will try it and let you guys know what happens.
Alright guys thanks! Got the custom recovery installed and phone is rooted! Solution was installing the Naked (United?) Drivers for nexus 4(yes they work for nexus 5 too!) Fastboot recognized the device and installed recovery susscessfully! Now it seems I have another question,I installed elementalx kernel and reverted back to stock as stock is way easier on my battery. Just wondering when changing the settings in the elementalx installer and then reverted to stock did the config stick or revert? I noticed my phones running hotter than usual which leads me to be leave the thermel throttling didn't revert. Thanks!
EDIT: It seems battery is draining faster too!
KentuckyGuy447 said:
Alright guys thanks! Got the custom recovery installed and phone is rooted! Solution was installing the Naked (United?) Drivers for nexus 4(yes they work for nexus 5 too!) Fastboot recognized the device and installed recovery susscessfully! Now it seems I have another question,I installed elementalx kernel and reverted back to stock as stock is way easier on my battery. Just wondering when changing the settings in the elementalx installer and then reverted to stock did the config stick or revert? I noticed my phones running hotter than usual which leads me to be leave the thermel throttling didn't revert. Thanks!
EDIT: It seems battery is draining faster too!
Click to expand...
Click to collapse
Probably best if you opened a new thread for separate issues.
EDIT: Yep, so nice to be ignored.
There's no way elementalx is worse on battery than stock. It's far better.
Use options for custom hotplugging
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Ben36 said:
There's no way elementalx is worse on battery than stock. It's far better.
Use options for custom hotplugging
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Click to expand...
Click to collapse
I reinstalled to test thoughly. I see where I can disable mpdecision and use custom hotplugging in the elementalx config, is that it or is there other steps I need to take besides that? Any advice or threads on this?
EDIT: I'm guessing the overheating is causing the battery drain. Stock didn't heat my device like this. Its not bad overheating but it does get significant and the battery seems to plummet when it happens. Usually happens after playing games, although stock didn't heat up this bad or drain battery that bad while playing games. It may also be the new charger I got, will charge with stock charger to see what happens.
beekay201 said:
Probably best if you opened a new thread for separate issues.
Click to expand...
Click to collapse
True but I don't want mods thinking I'm trying to spam or troll.
Thanks guys, I've done all I needed to do. As suggested by Ben using custom hotplugging and adjusting thermal throttling, device settled back down and is running smooth and heatfree(besides heavy gaming which is usual.) Thanks everyone! Guess it'll hold me over till official Cyanogenmod 12.1 nightlies start rolling out.