Hey guys, I may have completely stuffed this up, I got a 2nd hand Nexus 5 I was going to give to my mum. I was going to put the Chroma custom rom on it so firstly I unlock the bootloader and installed a 3.0 TWRP. After this is all done I was planning on using ADB sideload to install the custom rom, I wanted everything to be fresh and clean. So I wiped everything off it (including \system), after I done this, I realised I forgotten to enable USB debugging.
ADB works perfectly fine, so when I do ADB devices, I can see my device, I even double check that its set up correctly by using the Nexus Toolkit and ran the driver test. So when I tried to go and adb sideload chroma.zip, it says device error: no devices found. So I double check again by using adb devices and it says XXXXXXXXXXXX sideload. So its definitely there. So chances are, its because USB debugging is not enabled and this is screwing me over.
Anyone here is able to assist me with this? is there a way to enable USB debugging from TWRP (I tried to look for build.prop but that file is missing).
EDIT: Ohh, I forgot to mention that I got the latest Google drivers installed and the lastest SDK as well.
Z-Blade said:
Hey guys, I may have completely stuffed this up, I got a 2nd hand Nexus 5 I was going to give to my mum. I was going to put the Chroma custom rom on it so firstly I unlock the bootloader and installed a 3.0 TWRP. After this is all done I was planning on using ADB sideload to install the custom rom, I wanted everything to be fresh and clean. So I wiped everything off it (including \system), after I done this, I realised I forgotten to enable USB debugging.
ADB works perfectly fine, so when I do ADB devices, I can see my device, I even double check that its set up correctly by using the Nexus Toolkit and ran the driver test. So when I tried to go and adb sideload chroma.zip, it says device error: no devices found. So I double check again by using adb devices and it says XXXXXXXXXXXX sideload. So its definitely there. So chances are, its because USB debugging is not enabled and this is screwing me over.
Anyone here is able to assist me with this? is there a way to enable USB debugging from TWRP (I tried to look for build.prop but that file is missing).
EDIT: Ohh, I forgot to mention that I got the latest Google drivers installed and the lastest SDK as well.
Click to expand...
Click to collapse
usb debugging is automatically enabled while being into TWRP. I didn't try adb sideload with TWRP 3.0 so I can't confirm that the feature is working as it should be. Did you try with a previous version of TWRP? Did you enable adb sideload from TWRP before typing your command?
Primokorn said:
usb debugging is automatically enabled while being into TWRP. I didn't try adb sideload with TWRP 3.0 so I can't confirm that the feature is working as it should be. Did you try with a previous version of TWRP? Did you enable adb sideload from TWRP before typing your command?
Click to expand...
Click to collapse
Yes, I actually tried it with the previous version first due to the fact that 3.0 is new and may have bugs in it, but since that didn't work, I tried 3.0 afterwards. However, I was able to get MTP working while it was in Recovery. So I copied the files from my computer directly into the Nexus using MTP, for some reason, copying over the ROM and GApps took me over 13 hours to transfer. I didnt care how long it took at least it got it on there.
I was able to flash Chroma and GApps onto the phone so its now all good.
Related
Hi, I've got a Nexus S 4g. I recently tried to flash it with the stock Jelly Bean image from Google's developer page - developers.google.com/android/nexus/images. While I was running flash-all.sh, the flash appeared to finish, and my terminal just said <waiting for device>. The device does boot up, and is functional, however, I can't get this thing to connect to any of my PCs via USB.
I've plugged it into my 12.10 Ubuntu laptop, and run lsusb. The device isn't listed at all, so adb doesn't work. I've also booted the phone into fastboot, and lsusb still doesn't list it (so fastboot devices doesn't list anything either). I've also plugged it into my Arch box, and tried the same steps with the same results. Before I flashed the phone, I was able to debug just fine on both machines.
Has anyone seen this behavior before? Is there any way to fix it? I've spent a bunch of time searching around for this problem, and haven't seen much. Thanks.
Well, crap. It looks like I flashed the wrong image to my phone. I've got a Nexus S 4G (d720), and it appears I flashed the i9020 image. That's what has probably caused my issue. Does anyone know if there's any way to recover from this?
Rephrase: Do you have unlocked bootloader?
Do you have adb and fastboot drivers installed?
Do you have debugging enabled in devoper settings?
kwibis said:
Rephrase: Do you have unlocked bootloader?
Do you have adb and fastboot drivers installed?
Do you have debugging enabled in devoper settings?
Click to expand...
Click to collapse
no need to have debbuging mode on
kwibis said:
Rephrase: Do you have unlocked bootloader?
Click to expand...
Click to collapse
Yes
kwibis said:
Do you have adb and fastboot drivers installed?
Click to expand...
Click to collapse
Yes
kwibis said:
Do you have debugging enabled in devoper settings?
Click to expand...
Click to collapse
Yes
The problem is that I flashed the wrong image to my device. I'm pretty sure it's hosed. The phone works fine - it boots up, I can get on wifi, but I just can't connect via USB. The image I flashed must have different USB drivers than what my device has. It looks like I'm stuck with it, or I will see if someone can "unbrick" it, and flash the proper image to it.
Well since you have unlocked bootloader I guess you have custom recovery and are rooted as well. You can download a custom rom, safe your app data with titanium backup, factory reset and wipe cache in recovery and flash proper rom. Then the drivers should work again and you can flash the correct image if wanted.
Sent from my Nexus S
Hey guys!
INFO:
OS: Win8 x64 Pro
Phone: Nexus 5
Recovery thing: TWRP
Current ROM: NONE (corrupted)
USB Driver: Google USB Driver (works 100% fine)
I was trying to install a custom ROM, but failed horribly. I formatted the Nexus 5 in TWRP. Now I have no ROM installed, and cannot install any ROM because the one on the phone was deleted. Luckily I backed up everything useful on my PC before.
I tried using ADB to fix it. In CMD, my computer recognizes my Nexus 5, and shows it in CMD but I can't do anything. When I type in "adb devices" it says "109231blahblah unauthorized". "adb shell" also says I need to accept the "authorization dialog". "adb push" also says I am unauthorized.
I think I am "unauthorized" from doing anything because I didn't enable USB debugging (stupid I know) and now I can't even change it since I have no ROM installed.
Any way to enable USB debugging in TWRP?
I think the first thing to try is to restore whatever back up you have made with TWRP. Then you can redownload the ROM and try to flash it again.
If you don't have a back up on your device, I would download a ROM that you are sure has worked on your device before (or one that can be checked with MD5 or sha hash tags) and then use adb sideload to install the ROM. You can find the TWRP documentation for adb sideload here: http://teamw.in/ADBSideload
justmpm said:
I think the first thing to try is to restore whatever back up you have made with TWRP. Then you can redownload the ROM and try to flash it again.
If you don't have a back up on your device, I would download a ROM that you are sure has worked on your device before (or one that can be checked with MD5 or sha hash tags) and then use adb sideload to install the ROM. You can find the TWRP documentation for adb sideload here: http://teamw.in/ADBSideload
Click to expand...
Click to collapse
Since he's getting the unauthorized messages, I don't think sideloading would work.. It's really weird though, sideloading should work in a custom recovery without enabling debugging in phone settings...
@Sharmster
If you can't use adb then here are your choices:
1. Use OTG Cable and a flash drive to install rom/gapps from the flash drive itself.
2. If you don't have an OTG cable then you are left with flashing the factory images(which needs fastboot) and starting all over again! Follow this guide: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Hi, This is the first time i am having this problem, i previously had a CM 11S ROM and wanted to change and try liquid smooth ROM, so i went into recovery and did a clean wipe and cleared all data then i went into ADB sideload to sideload the rom and flash it and it says error: device not found.
When i go into bootloader and do fastboot devices, i can see my device so i thought it must be an error with my recovery and i flashed the new TWRP recovery v2.7.1.1 and again did fastboot in bootloader and device is seen but when i get into recovery and try to sideload i get the same message of error device not found.
What could be the issue here?
If i had example ADB off in the ROM, is there a way of turning it back on? I've already clean wiped everything so i had no ROM installed, any other way of turning it on, think maybe that could be the issue?
Thanks in advance.
EDIT:
So i updated my SDK and i download Stock Image from Google and flashed it via fastboot and the phone booted, i turned on adb and went back into recovery and i was able to sideload the custom ROM i wanted, so either the problem was with my SDK or because maybe ADB wasn't ticked in my old ROM, but problem is solved.
Thanks.
Could be a driver issue?
Try to kill and relaunch adb server.
Did u update the SDK? Check your path for adb.exe.
Shiestie said:
Could be a driver issue?
Click to expand...
Click to collapse
I've always used the same laptop and USB port
Haven't updated my SDK and i even restarted my laptop
EDIT:
Lemme try updating my SDK and try again
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