Hi, I am having a very very newbie problem. I tried going for F2FS but mistakenly flashed a ROM that is meant for F2FS-all while I only have /DATA formatted as f2fs. I ended up with a ROM that won't get past google logo and since I formatted /data, I have no ROM zips on the device.
I tried to adb push files in and adb flash google stock image but to no avail because I couldn't get the google drivers and the adb to work. I have tried Google USB Driver, Universal Driver, Naked Driver etc. And yes, I have removed previous driver before testing the new one. I already have Android SDK installed but no matter what I do, Windows could not recognize my n5. It keeps saying that the device is unrecognizable and it shows up as "unknown device" in Device Manager. Also yes, I connect to PC while it is in fastboot mode. Tried another pc, same result.
Tried to have recovery (i have TWRP 2.7.1.1) to mount USB otg but I couldn't get it to mount. Tried a cable I made myself and also one I bought from ebay. The cables both worked when the phone isnt screwed.
So now I am wondering if there is any other way to get files into the phone? Also I have an idea of moving the system files that are meant for f2fs to /data temporarily, then format /system and cache as f2fs and move the files back to /system. Would that work? Thanks in advance.
Just to confirm, you are booted into recovery when trying to use adb right?
You can use sideload function to flash your zip files in recovery, don't you?
rootSU said:
Just to confirm, you are booted into recovery when trying to use adb right?
Click to expand...
Click to collapse
No, the fastboot mode. The one with the android bot lying down and guts exposed. Recovery mode works with adb?
Rip95 said:
You can use sideload function to flash your zip files in recovery, don't you?
Click to expand...
Click to collapse
I tried adb sideload, couldn't do it because windoze doesn't recognize my n5. It kept saying "one of the device connected is malfunctioning".
hawktalon said:
No, the fastboot mode. The one with the android bot lying down and guts exposed. Recovery mode works with adb?
I tried adb sideload, couldn't do it because windoze doesn't recognize my n5. It kept saying "one of the device connected is malfunctioning".
Click to expand...
Click to collapse
Flash the factory image and get rid of f2fs. It's not ready for prime time and you're not ready for it.
The android with it's guts is recovery, push vol up
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Flash the factory image and get rid of f2fs. It's not ready for prime time and you're not ready for it.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I know. I made a silly mistake. The problem now is that I can't get any ROM files into the phone bcs adb and usb-otg isnt working. Any ideas how to get files into the phone?
hawktalon said:
No, the fastboot mode. The one with the android bot lying down and guts exposed. Recovery mode works with adb?
I tried adb sideload, couldn't do it because windoze doesn't recognize my n5. It kept saying "one of the device connected is malfunctioning".
Click to expand...
Click to collapse
You can't use adb in fastboot mode.. Flash a custom recovery and boot into it to perform sideload commands.. Not sure whether stock recovery supports it or not.
hawktalon said:
I know. I made a silly mistake. The problem now is that I can't get any ROM files into the phone bcs adb and usb-otg isnt working. Any ideas how to get files into the phone?
Click to expand...
Click to collapse
You don't need to transfer the factory images to your device to flash them.. They are flashed via fastboot.
vin4yak said:
You can't use adb in fastboot mode.. Flash a custom recovery and boot into it to perform sideload commands.. Not sure whether stock recovery supports it or not.
You don't need to transfer the factory images to your device to flash them.. They are flashed via fastboot.
Click to expand...
Click to collapse
I already have a custom recovery. TWRP 2.7.1.1. I've tried sideload commands and adb commands, the problem is that windows won't recognize the phone when connected via usb. Also, I've tried using adb in both fastboot and twrp. Neither of them worked.
I know I don't have to actually get the files into the device, and I should be using adb to flash but adb isn't working for me since Windoze decided that my device is malfunctioning and ignores all the driver I tried.
hawktalon said:
I already have a custom recovery. TWRP 2.7.1.1. I've tried sideload commands and adb commands, the problem is that windows won't recognize the phone when connected via usb. Also, I've tried using adb in both fastboot and twrp. Neither of them worked.
I know I don't have to actually get the files into the device, and I should be using adb to flash but adb isn't working for me since Windoze decided that my device is malfunctioning and ignores all the driver I tried.
Click to expand...
Click to collapse
Might be a driver issue as well?? Have you downloaded the usb_driver from SDK manager and updated the Nexus drivers from the device manager?
If you can't get adb to work then see whether "fastboot devices" returns your phone in cmd? Fire this command when the phone is in bootloader/fastboot mode. If it does, then you can go ahead with flashing the factory images.
Has to be a driver issue
You have no choice but to get the drivers working on a computer. You have to be able to push files to your phone with adb or use fastboot and the stock files to get your phone back up and rolling.
Keep on trying. I had to mess with mine a bunch as I had multiple old drivers from old phones...
You could try something like un-installing the drivers then running a registry cleaner (assuming Windows). I like Ccleaner. Give your computer a reboot and try again.
You can message me if you want computer help.
flyboy_9 said:
You have no choice but to get the drivers working on a computer. You have to be able to push files to your phone with adb or use fastboot and the stock files to get your phone back up and rolling.
Keep on trying. I had to mess with mine a bunch as I had multiple old drivers from old phones...
You could try something like un-installing the drivers then running a registry cleaner (assuming Windows). I like Ccleaner. Give your computer a reboot and try again.
You can message me if you want computer help.
Click to expand...
Click to collapse
This
And remember fastboot in bootloader and adb in recovery
Sent from my Nexus 5 using Tapatalk
I already have a custom recovery. TWRP 2.7.1.1. I've tried sideload commands and adb commands, the problem is that windows won't recognize the phone when connected via usb. Also, I've tried using adb in both fastboot and twrp. Neither of them worked.
Click to expand...
Click to collapse
Use this guide to install adb driver for your nexus (just yesterday i had the same problem) run sideload in recovery and then do this:
http://pcsupport.about.com/od/fixtheproblem/ht/update-drivers-windows-7.htm
On step 5 you will be prompted to choose device type, and driver itself. You must click google adb driver, and choose android adb interface. But you should install google adb drivers first in order to choose this driver for your nexus.
UPD. Same guide in this forum: http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
flyboy_9 said:
You have no choice but to get the drivers working on a computer. You have to be able to push files to your phone with adb or use fastboot and the stock files to get your phone back up and rolling.
Keep on trying. I had to mess with mine a bunch as I had multiple old drivers from old phones...
You could try something like un-installing the drivers then running a registry cleaner (assuming Windows). I like Ccleaner. Give your computer a reboot and try again.
You can message me if you want computer help.
Click to expand...
Click to collapse
Tried all the drivers and toolkits I can find. It still says "one of the device has malfunctioned..." and device manager shows my n5 as unknown device. I did ccleaner on registry everytime I tried new solutions. I also uninstalled the previous drivers.
rootSU said:
This
And remember fastboot in bootloader and adb in recovery
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I was afraid to be wrong so I tried both.. no difference, still couldn't get it to work.
Rip95 said:
Use this guide to install adb driver for your nexus (just yesterday i had the same problem) run sideload in recovery and then do this:
http://pcsupport.about.com/od/fixtheproblem/ht/update-drivers-windows-7.htm
On step 5 you will be prompted to choose device type, and driver itself. You must click google adb driver, and choose android adb interface. But you should install google adb drivers first in order to choose this driver for your nexus.
UPD. Same guide in this forum: http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
Click to expand...
Click to collapse
On my pc it doesn't show google adb driver, it only shows unknown device. I already have adb installed and is properly working since I can issue adb commands but my phone is not connected somehow.
On my pc it doesn't show google adb driver, it only shows unknown device. I already have adb installed and is properly working since I can issue adb commands but my phone is not connected somehow.
Click to expand...
Click to collapse
.
You didn't get it. I tried to tell you how to fix this:
Tried all the drivers and toolkits I can find. It still says "one of the device has malfunctioned..." and device manager shows my n5 as unknown device.
Click to expand...
Click to collapse
Since windows can't install driver for your nexus you should choose your device in device manager and install it by yourself (follow the guide i linked). When you fix your device driver you'll be able to use adb commands in recovery.
Rip95 said:
.
You didn't get it. I tried to tell you how to fix this:
Since windows can't install driver for your nexus you should choose your device in device manager and install it by yourself (follow the guide i linked). When you fix your device driver you'll be able to use adb commands in recovery.
Click to expand...
Click to collapse
Yes, I tried the steps in the url. It only shows my phone as unknown device, there was no adb devices listed. Also, I have tried using the manually upgrade driver method, windoze gave me the response saying "windows has determined that the best driver is installed" even though I pointed it to the driver directory. I also tried the "have disk" method, pointing to the google driver directory and on a seperate attempt pointed to naked driver and universal driver directory. It picked up the .inf file but too gave me the response "no suitable driver found... make sure it is meant to work with x64....'. Again I tried on another pc which is 32 bits, it gave me "no suitable driver found...".
This is where I am at. I am starting to suspect that the usb on my n5 is the faulty one. But then, it was working before all of this happened.
Try changing USB ports and cables on computer
Sent from my Nexus 5 using Tapatalk
Oh, well...
*uninstalling driver*
Your device looks like that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
rootSU said:
Try changing USB ports and cables on computer
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes... I tried that. Used original cables for my galaxy s2 and n5, also tried some nokia and china cables. Ports I've used them all, even gone to the extend of trying USB hubs lol..
Rip95 said:
Oh, well...
*uninstalling driver*
Your device looks like that?
View attachment 2798388
Click to expand...
Click to collapse
No, it doesn't show nexus 5. It shows unknown devices. I'll attach a picture.
No, it doesn't show nexus 5. It shows unknown devices. I'll attach a picture.
Click to expand...
Click to collapse
Looks like TWRP have adbd or device issue. You can try install Philz touch recovery via fastboot.
Sorry guys, had a big finals exam i the past months. Am back now yay! Thanks for the attemps so far guys.
Rip95 said:
Looks like TWRP have adbd or device issue. You can try install Philz touch recovery via fastboot.
Click to expand...
Click to collapse
I can't install anything right now since the phone is basically empty due to formatting /data to f2fs and I can't adb in nor sideload. It's a really big mess.
One thing I wanted to point out is that does USB gets disabled if fast charge is enabled in the kernel? I remembered turning on fast charge in elementalX when I installed it. I really don't want to send this in for warranty since this device is actually not available in my country, had to buy it from Australia and now if I have to warranty it, I ahve to send it to Australia. Plus, I'm sure this isn't covered in warranty either.
Related
I want to root my tablet so I flashed TWRP 2.6.0.0 using fastboot everything works fine.
But now I want to install the zip to root the tablet, problem is TWRP cannot mount any storage, internal sdcard external sdcard nothing at all is alway says E:Can't mount 'xxx' on anything I tap.
I tried CWM, and 2.5.0.0 and nothing seems to work.
I can boot fine in the stock OS, everything works fine but that
My bootloader is 10.6.1.27.1-20130711
Can anyone help me?
Ok now it is bad, I tried to factory reset using the bootloader (power + volume down)
It booted in the buged TWRP and now it keeps booting in TWRP and I cannot even reach the bootloader
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
aarsyl said:
Try using adb commands to boot into bootloader.
ADB reboot-bootloader is the command that I think you must use. Of course, use adb devices to see if your tab is listed.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
I cannot get this to work on Windows 8, I have Asus Transformer ADB interface lister in device manager but I cannot see my device with the adb devices command.
Also, in TWRP when I try adb sideload it says failed.
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Buster99 said:
win 8 is the worst OS you want to use when it comes to fastboot/adb (even with secpol.msc full admin access)
get your hands on a win7 / vista /xp
oh and TWRP2.6 is kinda bugged - flash 2.5 or lower
check this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12 but skip the steps you dont need (system, data userdata etc.)
cheers & gl
-Buster
Click to expand...
Click to collapse
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Matiosse said:
I'm now on my laptop with Win7,
Ok so I tried to reset my device with a needle, but I cannot get it to the bootloader.
Still stuck in TWRP, I tried to go with ADB, I installer google usb driver from Android SDK, I cannot get it to be recognized by ADB, in the device manager I only see Transformer with a yellow "!", I tried with the Asus usb driver, nothing either.
Is there something else I can do to get this recognized with ADB? (fastboot doesn't work either)
I tried unpluging all, uninstalling all and reinstalling like 3 times.
Thanks for your help
Click to expand...
Click to collapse
fastboot should work. hold Vol-down and reset the device and keep vol-down pressed. it should go to fastboot. when you're in fastboot connect it to your laptop and see if the OS recognized your device - if not you have a driver issue. resolve that by installing the asus driver or the newest google generic drivers.
when you can see your device on dosprompt/powershel with fastboot devices then continue with getting recovery to work.
btw- stuck in twrp means? booting twrp (teamwin screen) but not responding?
good luck
-Buster
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Matiosse said:
The problem is I cannot even get into fastboot, it keeps booting into TWRP, I tried to reset the tab with a needle, but I cannot reach fastboot in any ways
Click to expand...
Click to collapse
but you are still able to boot into android?
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Matiosse said:
I was until I tried a factory reset, it wasn't working in Android so I did it in the fastboot menu.
Click to expand...
Click to collapse
can you boot into twrp? and i mean just boot into it? so that you see install, backup, restore etc. buttons?
if yes - twrp has an adb mode
connect your tab in twrp to your pc (check that you can see it - adb devices) if yes type: adb reboot bootloader
and you should boot into that. test it with fastboot devices.
most important thing is that you get into fastboot or a working recovery to flash or prepare to flash a (custom) rom back onto your device.
Buster
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Matiosse said:
I can get in TWRP on 2.5.0.0
But when I try ADB sideload it fails
The message is ADB sideload complete - Failed in red + lots of errors like Unable to mount '/data' '/cache' /system' pratically everything (note that I had the same problem of mounting when I was able to boot into Android)
Click to expand...
Click to collapse
learn to crawl before you run :angel:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Matiosse said:
Well I rooted 4 different android device and not a single one of them wasn't able to mount anything in recovery mod. I knew exactly what I was doing until I got in the recovery mod who won't even recognize my internal storage meanwhile I was able to perfectly boot in Android
Click to expand...
Click to collapse
dude - you can't boot into android anymore, you can't boot into fastboot to your own accord - yet you try to sideload stuff in twrp for what ever reason.
i gave you more hints and tips in my previous posts and link to get it to work yet it eems you did none.
so don't get me wrong - but what excactly is your goal here?
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Matiosse said:
My goal is to get it working again...
I don't know if you've been reading my post but I did try everything you told me without sucess.
None of the tips I tried got me adb or fastboot working the sideload mode of TWRP doesn't work.
Click to expand...
Click to collapse
yes i read your posts - but im still unclear what you are trying to accomplish with sideload?
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?) "adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
-B
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Matiosse said:
ok from the start:
when in twrp - connect your tab to your laptop - is windows working with it (drivers ok?)
Windows isn't working with it, I tried Google usb driver, asus usb driver, universal adb driver, none of them work, this is where i'm stuck
"adb devices" shows the device? if yes - adb reboot-bootloader (or fastboot reboot bootloader, not quite sure atm since i'm at work without micro usb cable) when issued the command is the tab rebooting? - and if yes, is it rebooting into twrp or fastboot? what screen is shown after that?
Click to expand...
Click to collapse
when its connected - is device manager at least showing it as faulty or not at all? (yellow triangle exclamation mark thingy, i just installed asus on my VM) -> see attached file
UPDATE: I succeeded to go in fastboot mode
I couldn't get my tab to be recognized by windows so I installer my Nexus 4 using the toolkit, when it was succesfully installed I could manually install my tab since the "android devices" option appeared in the list when you want to manually install a driver in the devices manager. So I could choose Asus ADB interface.
Now I can boot into Android, but it will go into TWRP as soon as I restart my tablet.
Now I will try the link you sent me to get TWRP recognize my storage so I can flash a new rom, I will let you know if something go wrong.
Thanks for helping
Hi all,
My phone is not recongnized by my PC in recovery, and I can't use adb command, but it is recongnized fine in bootloader and in system.
is there a specific driver for recovery i have to install? I am using teamwin
Thanks ahead!!
david0916 said:
Hi all,
My phone is not recongnized by my PC in recovery, and I can't use adb command, but it is recongnized fine in bootloader and in system.
is there a specific driver for recovery i have to install? I am using teamwin
Thanks ahead!!
Click to expand...
Click to collapse
anyone?
david0916 said:
anyone?
Click to expand...
Click to collapse
There is no specific driver. Do you have usb debugging enabled?
I had to uninstall and reinstall drivers. Mine did the same thing.
Sent from my Nexus 5 using XDA Premium 4 mobile app
david0916 said:
Hi all,
My phone is not recongnized by my PC in recovery, and I can't use adb command, but it is recongnized fine in bootloader and in system.
is there a specific driver for recovery i have to install? I am using teamwin
Thanks ahead!!
Click to expand...
Click to collapse
I have been having the exact same issue. Ive noticed that when I am in recovery and adb doesnt recognize the device, it seems like it is actually windows that doesnt recognize because i go into Device Manager and see Nexus 5 with an exclamation, and if I try to install the drivers for it, it says it cannot find the proper drivers in the same folder that i originally installed the drivers from!
I am very confused and this is pissing me off, because I should have the damn OTA already and I dont!!!!
david0916 said:
Hi all,
My phone is not recongnized by my PC in recovery, and I can't use adb command, but it is recongnized fine in bootloader and in system.
is there a specific driver for recovery i have to install? I am using teamwin
Thanks ahead!!
Click to expand...
Click to collapse
i am not rooted and do not have a custom recovery either. bur i had the same problem when i tried to side load update 4.4.1.
the problem for me was that the google usb driver that i installed did not have proper adb support for nexus 5. this is what worked for me. universal naked driver v. .73
downloaded and unzipped in a folder in desktop.
booted into recovery on the phone
windows chimed new hardware found, device manager showed nexus5 with an exclamation mark.
right clicked to update device software, pointed to unzipped folder, done.
this way after geting out of CMD phone is still recognized as MTP, so i can transfer files back and forth.
akmsr said:
i am not rooted and do not have a custom recovery either. bur i had the same problem when i tried to side load update 4.4.1.
the problem for me was that the google usb driver that i installed did not have proper adb support for nexus 5. this is what worked for me. universal naked driver v. .73
downloaded and unzipped in a folder in desktop.
booted into recovery on the phone
windows chimed new hardware found, device manager showed nexus5 with an exclamation mark.
right clicked to update device software, pointed to unzipped folder, done.
this way after geting out of CMD phone is still recognized as MTP, so i can transfer files back and forth.
Click to expand...
Click to collapse
just updated to 4.4.2 same way. except this time is was easier. no driver issue
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
Hi,
I am not sure if I can ask about upgrading to CM here? Today I tried to follow their guide from their wiki and now my I can't access anything but recovery, and adb won't work.
I installed the recovery using fastboot and unlocked the device. That worked.
After that, I wiped data/factory reset and the next stage is to push CM to my device, but the device isn't recognized by the PC (when I type adb devices no devices appear).
Now I don't have an os and cannot do anything outside of recovery. I tried clicking on mount USB storage but it doesn't open my storage on my computer. When I connect the device my computer makes sound that a USB is connected.
I tried to /mount data and pretty much everything.
Any ideas?
Sorry for bad English.
I assume you installed TWRP recovery. If yes,
click on MOUNT option,
check SYSTEM option,
disable MTP and then
Enable MTP
.. now you should be able to see the device in your computer. Copy the zip file and flash it through recovery.
schmos said:
I assume you installed TWRP recovery. If yes,
click on MOUNT option,
check SYSTEM option,
disable MTP and then
Enable MTP
.. now you should be able to see the device in your computer. Copy the zip file and flash it through recovery.
Click to expand...
Click to collapse
No, I have CW recovery (I thought I wrote that, sorry).
You need to get adb drivers sorted out, I believe there's a guide for it on General forum.
beekay201 said:
You need to get adb drivers sorted out, I believe there's a guide for it on General forum.
Click to expand...
Click to collapse
Are you talking about this? http://forum.xda-developers.com/showthread.php?t=2588979
Because if yes it didn't change anything. In bootloader my pc recognizes my phone as "Android" but I still can't do anything.
Mr Light said:
Are you talking about this? http://forum.xda-developers.com/showthread.php?t=2588979
Because if yes it didn't change anything. In bootloader my pc recognizes my phone as "Android" but I still can't do anything.
Click to expand...
Click to collapse
You previously wrote, and I quote, "I installed the recovery using fastboot and unlocked the device. That worked."
^ This means to me that the connection between your bootloader (fastboot client) and your computer (fastboot host/server) is working, from which we can assume drivers FOR FASTBOOT are correctly setup.
You previously wrote, and I quote, "but the device isn't recognized by the PC (when I type adb devices no devices appear)"
^ This means to me that the connection between adb (on the phone) and adb (on the pc) is not working.
Now, if you are in a custom recovery, hook up the usb to the pc, start adb server on the pc, and you still don't see your device sn appear on the output of 'adb devices', then it means that the drivers FOR ADB aren't setup correctly.
Running a tool and then coming back saying it didn't work... That's not helpful at all. How did it not work? What version of the tool did you use? 1.4.2? 1.3? Keep in mind that you need (more likely than not, since you're probably running latest recovery versions) updated adb and fastboot binaries to API 21 version (Android 5.0). v1.3 of that tool doesn't seem to support API 21 yet.
Learn how to ask for help, please. Also, read the entire first post of this thread please: http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
If you still can't get it to work, there's a thread to help out troubleshooting drivers stuff, check it out at http://forum.xda-developers.com/goo...nosing-usb-driver-adb-issues-windows-t2514396
Ok... Sorry for making you confused, it's not easy for me to communicate in English.
Anyway I managed to flash twrp which is much friendlier than CWM, and then I had access to my storage again. Thanks (solved).
hello guys
how do i root this phone please.
none of the google searched guides seem to work.
1. i've unlocked the bootloader using the asus app
2. i have adb installed on my pc
3. i've enabled usb debug mode on phone and allowing installation unknown apps
4. i've installed magisk v23 by downloading from github and just installing the apk file normally
5. i've downloaded a 2.9gb zip file from asus for androind 11 firmware onto phone and pc (but its a zip file that extracts a bin file, no image file)
my problem seems to be i don't know how to CREATE AND PATCH an image file or install twrp and install image file that way.
Could someone help, there doesn't seem to be any guides for rooting in this phones forum.
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Seosam said:
Look in the twrp thread: https://forum.xda-developers.com/t/recovery-official-twrp-for-asus-zenfone-7-series.4161719/
after twrp you can flash the magisk.zip
Click to expand...
Click to collapse
i keep getting era waiting for device when i want to flash the phoben with twrp.
adb reboot bootloader (works and i enter the recovery menu start, bootloader, recovery, power off etc)
fastboot flash recovery_a twrp.img (when i type this cmd power shell just says waiting for device)
i have universal drivers installed and android sdk installed. not sure why it isn't recognising the phone?
When my phone is switched on normally, cmd recognises it, when i use adb devices. but as soon as i reboot into recovery mode using cmd "adb reboot bootloader" it stops recognising the phone on the list of devices using the cmd "adb devices"
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
no answer from phone when in fastboot mode.
but i do get a reply in cmd when phone is switched on normally.
I'll try with another cable, but if it responds to adb when in normal mode. doesn't it mean it's not a cable issue but a software driver issue?
Seosam said:
so you don`t get an answer from your phone by "fastboot devices" ?
Have you tried another usb cable and or port?
Click to expand...
Click to collapse
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
is it possible to root using adb sideload or install twrp using adb sideload?
articoceanic said:
seems when i do adb reboot bootloader it goes into what i thought was called fastboot. It even says fastboot.
but in that mode my phone isn't recognised by cmd when type adb devices, it doesn't come up.
it has 4 options reboot system now, botloader, enter recovery, reboot to bootloader, power off.
if i then select enter recovery. it enters a smaller text screen with lots of small blue writing. when inside that screen (recovery mode) cmd seems to recognise my device.
but it says it is unauthorized. this is in recovery mode.
i'm not sure why it says it is unauthorized. i've authorised my pc to control the phone through the fingerprint, when the message popped up.
but i can't push the twrp.img file through because of this.
since cmd doesn't seem to recognise phone in fastboot mode.
and cmd doesn't seem to have authorisation in recovery mode.
any ideas?
Click to expand...
Click to collapse
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Seosam said:
Thats the right mode.
Does the phone at normal start show that the bootloader is unlocked?
Your debugging mode is turned on in developer settings?
A sideload isn`t possible I think.
Click to expand...
Click to collapse
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
articoceanic said:
yes, shows bootloader is unlocked when i start the phone.
usb debugging mode is turned on.
i think for some reason in fastboot mode the device driver is not recognised in windows. have googled seems it was a very old problem that happned on phones 6 years ago. nut i haven't found anything recent to solve same error.
Click to expand...
Click to collapse
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
i think its definitely a driver issue. windows 10 seems to be overriding the drivers and installing wrong ones. and won't let me install right ones.
haven't tried in a different pc. will need to get hold of one and try.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
dont'know what happened. but weirdly i used usb 2.0 as you said and the driver listed on page 2 of this link got recognised.
[RECOVERY][OFFICIAL] TWRP for ASUS ZenFone 7 Series
*** Disclaimer *** All flashing is done at your own risk! While nothing from this thread should break your device, don't come back here blaming anyone if it does! Introduction Team Win Recovery Project 3.x, or twrp3 for short, is a custom...
forum.xda-developers.com
all this time windows 10 wouldn't let me install it. kept saying the drivers i already had was the best ones. but weirdly this time it did.
thanks friend. i think i have root access now. magisk keeps asking me to install the app tho. not sure why. i have version 23.0 installed.
but when i opne magisk it shows install icons for magisk and an unknown App. both listed as version 23.0.
Seosam said:
So you can just try it on another pc.
Have you changed from USB 3 port to a USB 2?
My Xiaomi mix2s had sometimes this too. That's worked for me.
Click to expand...
Click to collapse
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
articoceanic said:
last question friend, thanks for all your help.
where do i download apps like ad block plus adaway minmingaurd etc.
magisk dowsn't seem to have an option for that.
Click to expand...
Click to collapse
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
decade 1 said:
how solve com.asus.service keep stopping after install twrp? android 11 stock rom please answer
Click to expand...
Click to collapse
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
articoceanic said:
I'm not sure.
i only managed to root it by following the instructions here years ago.
maybe try updating the asus apps in play store? or ask some of the other people here who know more than me. or disable the asus apps. i don't use them.
sorry i couldn't help more
Click to expand...
Click to collapse
I try factory reset normal again I hope no recurrence