So I goofed really hard. was wiping my n7 and re-installing http://forum.xda-developers.com/showthread.php?t=2077396 but when I went to wipe the cache and I accidentally wiped my entire n7 fresh so there went my zip with the rom and gapps. I can still get into recovery team win recovery project v2.5.0.0) and bootloader but I cant access my storage so re-put it on and when I try and use the ADB sideload wont work. im at a loss everything I see online needs me to be in developer mode which I cant get to. Anyone have a way I can fix this?
how many of these do we need to see every day?
fix your ADB issues/drivers FIRST!
usb debugging has nothing to do with recovery, usb debugging ONLY applies to the booted OS. custom recoveries have a working adb daemon for you to attach to.
get the right drivers for ADB and either adb sideload or adb push a new rom to /data/media/0
Or connect a usb stick with usb otg and install a new rom or a nandroid backup from there. Or do a factory reset with fastboot.
Pirateghost said:
how many of these do we need to see every day?
fix your ADB issues/drivers FIRST!
usb debugging has nothing to do with recovery, usb debugging ONLY applies to the booted OS. custom recoveries have a working adb daemon for you to attach to.
get the right drivers for ADB and either adb sideload or adb push a new rom to /data/media/0
Click to expand...
Click to collapse
Or fastboot, if there are adb issues (generally became my method of choice on some Android devices because of weird adb quirks). Either way, agree with the sentiment.
Related
Earlier today I flashed Kaos Droid to try it out, but it put my Nexus in a state where it would not go past the screen that says Google and has the lock at the bottom. Since I have TWRP, Reboot to recovery from boot loader didn't work. I tried fixing the problem in not Windows and Ubuntu, but Windows kept on ending up as unknown device and no matter what drivers I tried to make it use it would not take, and in Linux it didn't show up in adb devices. I got lucky and it rebooted into TWRP after my fifth try of selecting recovery from the boot loader. I restored from backup, but I don't want this to happen again, if that ever happens. What should I do to get it in adb devices? Thanks.
Sent from an 8-core device from 2015
usb debugging
Try
Code:
adb kill-server
adb start-server
Can't remember if you need superuser permissions or not.
thebobp said:
Try
Code:
adb kill-server
adb start-server
Can't remember if you need superuser permissions or not.
Click to expand...
Click to collapse
I tried that, didn't work.
sonikot said:
usb debugging
Click to expand...
Click to collapse
How could I turn that on from bootloader? It was and is on before flashing the ROM and after restore.
Should have been able to run fastboot commands, either to try to reboot into the existing recovery, reboot into a recovery image, or flash a new recovery.
Sent from my Nexus 7 using xda premium
jcracken said:
Earlier today I flashed Kaos Droid to try it out, but it put my Nexus in a state where it would not go past the screen that says Google and has the lock at the bottom. Since I have TWRP, Reboot to recovery from boot loader didn't work. I tried fixing the problem in not Windows and Ubuntu, but Windows kept on ending up as unknown device and no matter what drivers I tried to make it use it would not take, and in Linux it didn't show up in adb devices. I got lucky and it rebooted into TWRP after my fifth try of selecting recovery from the boot loader. I restored from backup, but I don't want this to happen again, if that ever happens. What should I do to get it in adb devices? Thanks.
Sent from an 8-core device from 2015
Click to expand...
Click to collapse
Have a look at the Device Manager in Windows with your tablet plugged in. If there's that yellow triangle, just right click and choose update driver. Then you just browse and point Windows to where you have your N7 drivers.
akbar26 said:
Have a look at the Device Manager in Windows with your tablet plugged in. If there's that yellow triangle, just right click and choose update driver. Then you just browse and point Windows to where you have your N7 drivers.
Click to expand...
Click to collapse
That's the thing, I pointed it to official N7 drivers, Google USB Drivers, SuperOneClick drivers, and a bunch of other ones. It would never take--saying either that the best drivers are already installed (even though none were installed) or no suitable drivers exist in that directory.
I'm having a similar issue here, except I can get to the "X" boot animation.
jcracken said:
That's the thing, I pointed it to official N7 drivers, Google USB Drivers, SuperOneClick drivers, and a bunch of other ones. It would never take--saying either that the best drivers are already installed (even though none were installed) or no suitable drivers exist in that directory.
Click to expand...
Click to collapse
same problem here ... did u ever solve it ?
sonikot said:
usb debugging
Click to expand...
Click to collapse
Sometimes it seems to me that, even though USB debugging is "on", it really isn't.
Several times I have had to un-check and re-check "USB debugging" before adb would recognize the device.
Just my experience. Your milage may vary.
i'm in the same boat !
,
Any ?
Are you on 4.2.2? There now should be a security dialog upon executing an ADB command on the device, it will prompt you to allow the command to be executed.
If tou aren't on 4.2.2 - then it seems to be either a driver or a ROM issue
Yes I'm on 4.2.
I had this problem too and reinstalling the SDK tools fixed it for me for some reason.
Sent from my Paranoid 3.0 Nexus7 running M-Kernel mr1
I reinstall sdk without sucess
Maybe try using wugfresh toolkit. I've seen people say they couldn't use adb or fastboot but the toolkit worked. Doesn't really make sense to me since the toolkit just sends the commands for you but hey, worth a shot. It will walk you through uninstalling current drivers and doing a fresh driver install also.
Sent from my Paranoid 3.0 Nexus7 running M-Kernel mr1
travisjustin said:
Maybe try using wugfresh toolkit. I've seen people say they couldn't use adb or fastboot but the toolkit worked. Doesn't really make sense to me since the toolkit just sends the commands for you but hey, worth a shot. It will walk you through uninstalling current drivers and doing a fresh driver install also.
Sent from my Paranoid 3.0 Nexus7 running M-Kernel mr1
Click to expand...
Click to collapse
I use this kit. Remove all drivers. Then install the driver again. The drivers has been install in fastboot mode and recovery mode. The nexcus is recognized in these mode by the wugfresh toolkit.
Unfortunately in normal mode, when i active usb debug mode, i get a unkown device on windows 7 32 with any possibility to update the drivers.
I get error unkow device, device is stop error 43
Cable is stock and also try another one.
I get same message error on another computer with windows 8
I confirm that my usb issue is solved.
After a factory reset, i reinstall the last release Usb ROM and USB comes back to life on my nexus.
The nexus is no more recognized as unkown device by my computer and i can install the adb driver.
During this story, i try also to get acces via wifi but was unable to connect even with adb over wifi enable on the nexus.
That why Timur recommands me to made a full factory reset.
My problem seems to be due to corrupt data that block every connections between the computer and the nexus (adb wifi and usb) based on last 4.2.2 new safety features.
So far i recommand full wipe between two rom install to avoid such trouble.
Thank a lot to timur for his support during the week end.
If your nexus is rooted, go in recovery mode and install a new rom from zip.
How to ?
Download rom of your choice via wifi
You can download a rom directly from your nexus to sd.
Check here for download (example)
http://mehrvarz.github.com/nexus-7-usbrom/
Download Google applications on your nexus via wifi
Download from here : http://donandroid.com/gapps
Before installing new rom make a save using titanium backup.
https://play.google.com/store/apps/details?id=com.keramidas.TitaniumBackup&hl=fr
Save all your application and data in batch mode.
Create titanium.zip on your nexus 7 sd.
Then from recovery mode make a full wipe but without erasing sd data.
Follow these instructions :
Unless you format the system partition and system caches, you aint wiped nothing, there is only one way to carry out a proper full wipe, and thats the full wipe the correct way.
1. Boot into recovery
2. Wipe the cache partition
3. Go to advanced and wipe dalvik and batt stats.
4. Go back to mounts and storage and format system, then data, then cache.
5. Go back and install the rom zip file from the sd card.
6. Reboot.
No need to wipe data/factory reset, the contents of your internal and external sd cards are untouched.
From Recovery mode
- install titanium.zip.
- install gapps.zip
Reboot
Go to titanium backup and recover all your data.
Et voila...
I Did something really stupid, I have a Nexus 7, rooted, unlocked, went to twrp and did a back up of the stock rom, it said successful, then rebooted used the rom, everything perfect but I had tablet mod on it, decided to go back to full stock, booted to recovery, wiped everything, tried to restore and my backup is not there, and I deleted the rom as well, so now I have no rom to flash and I'm stock in recovery, anyway to push a rom into the nexus in recovery or bootloader? I tried flashing it with root toolkit 1.5.5 but it doesn't find the tablet,(all the drivers are installed), any and all help is appreciated...
Your PC won't see your N7 in Android because you haven't turned on USB debugging, and probably can't now.
You should be able to push an updated TWRP in fastboot that will see your 4.2 backup. The older version can't find its backups in 4.2,as you've discovered.
I'm not the lowest of the low, but I am the slowest of the slow.
I did have it on, I can see the tablet from control panel, but when I run the kit it says adb device not found..
Sent from my EVO using xda app-developers app
The drivers will let your PC see the N7, but you have to be in USB debugging for ADB to work. You lost it when you wiped your system, as the failure of the toolkit to see the ADB proves.
I'm not the lowest of the low, but I am the slowest of the slow.
exglynco said:
The drivers will let your PC see the N7, but you have to be in USB debugging for ADB to work. You lost it when you wiped your system, as the failure of the toolkit to see the ADB proves.
I'm not the lowest of the low, but I am the slowest of the slow.
Click to expand...
Click to collapse
USB Debugging doesn't need to be on for ADB through recovery to work.. Why would it? The system isn't even on it is in recovery.
Try the toolkit in fastboot.
Sent from my Full Android on Grouper using Tapatalk 2
joshnichols189 said:
USB Debugging doesn't need to be on for ADB through recovery to work.. Why would it? The system isn't even on it is in recovery.
Try the toolkit in fastboot.
Sent from my Full Android on Grouper using Tapatalk 2
Click to expand...
Click to collapse
when I'm in the bootloader it says it's in fastboot mode, but the toolkit wont find it!
I running recovery 2.3.2.1
tried adb sideload as well and it says "cannot read sideload" any ideas? getting a little crazy here..
Can anybody give me specific commands in ADB or fast boot I'm an idiot when it comes to that, on how to try to push a ROM into the device so I can flash it from recovery, or maybe a link to where I can read about it, I would really appreciate it..
Sent from my EVO using xda app-developers app
While in recovery, type in the following:
Code:
adb push <name of ROM zip> /sdcard
You need to open a command prompt window, change directories (cd) to your Android SDK - platform tools directory, and to make things easy, move the ROM zip file into that directory as well (platform-tools that is). Then type the adb push command above.
EDIT: This puts the ROM zip on the root of your sd card (/sdcard). I have a ROM folder on my sd card, so I would type:
Code:
adb push <name of ROM zip> /sdcard/ROM
This just shows that you can push a file into a folder on your sd card.
Hi there.
I have a Nexus 4 with a failed root through Nexus 4 Root toolkit.
The toolkit unlocked the bootloader with no problems but it failed at applying SuperSU-v1.45.zip through ADB through CWM
I am pretty certain that this process failed because I did not Enable USB debugging before starting.
So, I think the question I want to ask is: Is it possible to Enable USB debugging so I can apply perform adb sideload SuperSU-v1.45.zip
Do I have any other options? At present the device won't boot into Android OS. The states I currently have are either
1. fast boot mode
and then Recovery Mode -> CWM
2. Just a black screen, the Google logo, and an unlocked padlock
Any pointers would be greatly appreciated
Thanks!
jon.
Why CWM? TWRP is a lot better.
And Android USB debugging has no job in recovery so it isn't necessary if you're sideloading
Oh, and a few extra bits of info:
* I am on a mac
* I am pretty sure it's the adb ruining the party because when I do this:
(null) latform-tools jonwhittlestone$ adb devices
List of devices attached
(null) latform-tools jonwhittlestone$
Ahh thanks Lawstorant. Maybe my question isn't warranted then, or I'm barking up the wrong tree with ADB/USB debugging. Needless to say, I didn't enable it and surely this is not going to stop me rooting?
How can I get replace CWM with TWRP bearing in mind I can't get into the OS anymore - I'm a total Android root newbie as of this morning?
jonwhittlestone said:
Ahh thanks Lawstorant. Maybe my question isn't warranted then, or I'm barking up the wrong tree with ADB/USB debugging. Needless to say, I didn't enable it and surely this is not going to stop me rooting?
How can I get replace CWM with TWRP bearing in mind I can't get into the OS anymore - I'm a total Android root newbie as of this morning?
Click to expand...
Click to collapse
You shouldnt have used a toolkit.
Anyways, i think that you are misunderstanding this. You DO NOT need usb debugging enabled for adb to work while in a custom recovery. Adb works by default in a custom recovery.
I would suggest pushing a rom onto your phone (download a rom on your mac, put the phone into cwm, and run "adb push rom.zip /sdcard/").
After that go back to the phone and choose: wipe data/factory reset, wipe cache partiiton, advanced> wipe dalvik cache. Then go to install zip from sdcard and install the rom that you just pushed.
*Download the newest TWRP .img file from TWRP website
*Rename it to recovery.img to get rid of that long name
*Go into bootloader but don't choose anything (fastboot mode)
*In ADB type: fastboot flash recovery file_location/recovery.img
Sideloading in TWRP is in Advanced menu
consonant edbreach
Chromium_ said:
You shouldnt have used a toolkit.
Click to expand...
Click to collapse
Thanks Chroumium_, the procedure is becoming clearer. I should have known better to use a toolkit for sure.
I had actually followed Lawstorant's advice and put on twsrp, nevertheless - when I try to push a zip with adb, I get the following
(null)latform-tools jonwhittlestone$ adb push cm-10.2-20130815-rootandboot-mako.zip /sdcard/
error: device not found
Is this because I don't have the correct Nexus 4 drivers? The way I've always handled File transfers is with Android File Transfer so presumably I have go the correct drivers.
I am guessing if I had removable media, I could have put the zip on that...
jonwhittlestone said:
Thanks Chroumium_, the procedure is becoming clearer. I should have known better to use a toolkit for sure.
I had actually followed Lawstorant's advice and put on twsrp, nevertheless - when I try to push a zip with adb, I get the following
(null)latform-tools jonwhittlestone$ adb push cm-10.2-20130815-rootandboot-mako.zip /sdcard/
error: device not found
Is this because I don't have the correct Nexus 4 drivers? The way I've always handled File transfers is with Android File Transfer so presumably I have go the correct drivers.
I am guessing if I had removable media, I could have put the zip on that...
Click to expand...
Click to collapse
Im pretty sure that mac doesnt require any drivers to be installed. Try running these commands first:
Code:
adb kill server
adb start server
Also make sure that your adb is up to date (using the sdk manager). If its still not working try other usb ports or cables if you have any.
At this point adb is the only way to move the zip onto the phone, since the nexus 4 doesnt not support usb mass storage.
Chromium_ said:
Im pretty sure that mac doesnt require any drivers to be installed. Try running these commands first:
Code:
adb kill server
adb start server
Also make sure that your adb is up to date (using the sdk manager). If its still not working try other usb ports or cables if you have any.
At this point adb is the only way to move the zip onto the phone, since the nexus 4 doesnt not support usb mass storage.
Click to expand...
Click to collapse
Thanks to both - I've now solved and rooted
I reflashed with the stock google image
Followed androidpolice.com/2013/07/24/how-to-flash-your-nexus-4-to-android-4-3-jwr66v-and-root-it-right-now/
And - got the official TRSW from Gooapps on the Market
Flashed the SU update using the shell script - all details in the link above.
current supersu is 1.65
Can i enable usb debugging via locked phone [pin screen lock]
ok so i have a phone its an lg k5 or in mexico lg q6 a friend has asked me to unlock it with out doing any kind of hard reset or format so he he can access the pictures and other things on the phone since it belongs to his brother who passed away. anyways does anybody know of any way i can enable usb debugging so i can reset the lock screen via ADB ?? or maybe some other way?
Hello,
So a few days ago my nexus 4 got a virus that started hijacking my text messages and made it so that the phone would not mount as mass storage to a computer. Also adb wouldn't work and i did have usb debug on. Anyway so I have TWRP installed so I just did a storage format totally wiping android and the virus from the phone. After I did that I tried pushing a nandroid backup that I have over and adb told me that the device was not found. I tried pushing the file in the bootloader, the recovery and when its trying to boot an android that's not there. Then I tried re-installing all of the usb drivers and adb. Still nothing. The I tried the adb sideload in TWRP. Still nothing. So dose anyone have any ideas about what this could be?
Thanks a bunch,
You can't use adb commands in fastboot. You should be able to do an adb push while sitting in recovery; don't use sideload unless you are sideloading something. If you can't get it to work, flash a rom and do it from within android.
well,
I have a LG G2 d805/802 with TWRP recovery. I just wipe all data, internal storage, EVERYTHING...
I read a lot about ADB sideload, but it just don't start on phone (starting adb sideload feature...), but windows can recognize my device normally.
When I sideload the ROM.zip nothing happens. I think I have to make the feature starts.
Other way is to try flash from OTG, but my TWRP 2.6.3.2 just don't recognized my otg-memory.
Any ideias for what I supposed to do?
note: I think my device is not rooted.
1. If you device is not rooted, how could you get custom recovery on your device?
2. I don't think "sideload" is an universal adb command, meaning it supported on some devices and some others don't.
3. If "sideload" doesn't work in your case, why not just push the .zip file over and flash it using custom recovery?
gabrieelheringeer said:
well,
I have a LG G2 d805/802 with TWRP recovery. I just wipe all data, internal storage, EVERYTHING...
I read a lot about ADB sideload, but it just don't start on phone (starting adb sideload feature...), but windows can recognize my device normally.
When I sideload the ROM.zip nothing happens. I think I have to make the feature starts.
Other way is to try flash from OTG, but my TWRP 2.6.3.2 just don't recognized my otg-memory.
Any ideias for what I supposed to do?
note: I think my device is not rooted.
Click to expand...
Click to collapse
I gave sideload a good effort last week for a couple hours on Verizon G2 VS980 after doing the same thing you did. Eventually, I gave up and just did an adb push command to copy the file to my phone and then installed it using twrp as votinh suggests.
SOLVED
I realized the phone will never actually start the adb sideload feature. so, when i put the "abd sideload file.zip" command i just wait. it take a few minutes to start the process.