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...
Good day guys,
I need a help with my nexus 4, I had a rooted rom in my nexus 4 with clockwork mode recovery, I tried to wipe my data through clockwork mode but by mistake I did system wipe. Now there is no rom in the device, I can only access to fastboot mode and clockwork recovery mode, also I tried to install rom through toolkit but my PC & Mac doesn't read any device connected and no device shown in device manger in my windows 7 with using different usb cables and ports. I installed samsung drivers and adb drivers but still I cannot see the device in device manager.
Please if any body can help me to install rom back to my device.:crying:
alhawi6 said:
Good day guys,
I need a help with my nexus 4, I had a rooted rom in my nexus 4 with clockwork mode recovery, I tried to wipe my data through clockwork mode but by mistake I did system wipe. Now there is no rom in the device, I can only access to fastboot mode and clockwork recovery mode, also I tried to install rom through toolkit but my PC & Mac doesn't read any device connected and no device shown in device manger in my windows 7 with using different usb cables and ports. I installed samsung drivers and adb drivers but still I cannot see the device in device manager.
Please if any body can help me to install rom back to my device.:crying:
Click to expand...
Click to collapse
In cwm there should be an option to mount the device as usb storage. Try that. It should let you plug the phone into the pc and simply copy the zip onto the phones internal sd.
If thats not working try this to set up the drivers. Then plug the phone in and boot into the bootloader/fastboot mode. The open command prompt and cd to the android-sdk/platform-tools directory. Then run the following command:
Code:
adb push /path/to/rom/on/pc/ /mnt/sdcard/
still not working
Still not connected to windows, I cannot do any thing with my device
Download any ROM and do the following:
1. Connect phone to PC when in fastboot
2. Install drivers (if required)
3. Flash latest version of CWM using fastboot flash recovery name_of_recovery.img
4. Reboot phone into fastboot using fastboot reboot-bootloader
5. Boot into CWM
6. Install drivers (if required)
7. Select 'Install via sideload'
8. Flash ROM using adb sideload name_of_rom.zip
9. Follow instructions in CWM
If that still doesn't work, go back to stock using this guide (and read ALL of it):
http://forum.xda-developers.com/showthread.php?t=2010312
EddyOS said:
Download any ROM and do the following:
1. Connect phone to PC when in fastboot
2. Install drivers (if required)
3. Flash latest version of CWM using fastboot flash recovery name_of_recovery.img
4. Reboot phone into fastboot using fastboot reboot-bootloader
5. Boot into CWM
6. Install drivers (if required)
7. Select 'Install via sideload'
8. Flash ROM using adb sideload name_of_rom.zip
9. Follow instructions in CWM
If that still doesn't work, go back to stock using this guide (and read ALL of it):
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Thank you for your quick replay
My problem now that I cannot connect my device to PC, I installed drivers every thing and when I open fast boot or recovery mode and plug the cable, nothing indicates on my PC that there is a device connected even device manager not showing any device connected... I am stuck now, I cannot install any rom to get phone life back.
don't worry! the biggest problem would be that you had no drivers installed!
nexus are super easy to recover and you can play with them safely (except if you flash wrongs kernels from other devices haha)
do what my mate gets up in the post! and it will fixed it.
alhawi6 said:
Thank you for your quick replay
My problem now that I cannot connect my device to PC, I installed drivers every thing and when I open fast boot or recovery mode and plug the cable, nothing indicates on my PC that there is a device connected even device manager not showing any device connected... I am stuck now, I cannot install any rom to get phone life back.
Click to expand...
Click to collapse
It's not that it's not showing, it might already be installed correctly. When you have the Nexus 4 connect in fastboot it will show in Device Manager as 'Android Bootloader Interface' under the heading of 'Android Phone (see attached)
alhawi6 said:
Thank you for your quick replay
My problem now that I cannot connect my device to PC, I installed drivers every thing and when I open fast boot or recovery mode and plug the cable, nothing indicates on my PC that there is a device connected even device manager not showing any device connected... I am stuck now, I cannot install any rom to get phone life back.
Click to expand...
Click to collapse
Try with a different USB cable also could be your USB port on your computer
Sent from my Nexus 4
spaceman860 said:
Try with a different USB cable also could be your USB port on your computer
Sent from my Nexus 4
Click to expand...
Click to collapse
It seems that it will never works. I tried all the recommendations given but still device not detected by PC.
same problem for me.. help me
alhawi6 said:
Good day guys,
I need a help with my nexus 4, I had a rooted rom in my nexus 4 with clockwork mode recovery, I tried to wipe my data through clockwork mode but by mistake I did system wipe. Now there is no rom in the device, I can only access to fastboot mode and clockwork recovery mode, also I tried to install rom through toolkit but my PC & Mac doesn't read any device connected and no device shown in device manger in my windows 7 with using different usb cables and ports. I installed samsung drivers and adb drivers but still I cannot see the device in device manager.
Please if any body can help me to install rom back to my device.:crying:
Click to expand...
Click to collapse
i've the same problem in my nexus 4.. Could u recover from that?
Hello,
I just got the OTA message for 4.4 and tried to install it but I got a bootloop. After clearing the cache and performing a factory reset in TWRP (which got installed through Nexus Toolkit) it still didn't work. Someone told me to perform a complete format through TWRP which I did (hindsight, I know) and now TWRP says I have no OS installed, adb won't see my device (I have the drivers installed) and when I go into the bootloader (which says FASTBOOT MODE) fastboot still won't recognize the device (nothing shows up on my PC either but that can be normal).
I'm at my wit's end here, is there anyone who can help me?
You need to realize that if you want to install OTA, you need to use stock recovery. Even though it is possible to flash through TWRP, it can still run into problems. Especially when you made root modifications to your device.
You don't have to do a full wipe for everything. There is a method to flash factory firmware without wiping data (link in my signature). After that if it still don't boot due to existing data, boot into a custom recovery and do a factory reset without wiping the internal storage.
But since you have custom recovery already, just go into the Development section, find a stock KitKat rom, download it and sideload it using TWRP (which is enabled it in the Advance menu).
eksasol said:
You need to realize that if you want to install OTA, you need to use stock recovery. Even though it is possible to flash through TWRP, it can still run into problems. Especially when you made root modifications to your device.
You don't have to do a full wipe for everything. There is a method to flash factory firmware without wiping data (link in my signature).
But since you have custom recovery already, just go into the Development section, find a stock KitKat rom, download it and sideload it using TWRP (which is enabled it in the Advance menu).
Click to expand...
Click to collapse
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
fverswijver said:
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
Click to expand...
Click to collapse
If it is connected adb should see your device while in TWRP. Fastboot only work in fastboot mode (bootloader screen), not in recoveries. If you have the UND installed then they both should work, if not it wasn't installed correctly. If you are using Windows 8 you need to disable driver signature before you can install UND (search google for that).
You could also make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
eksasol said:
If it is connected adb should see your device while in TWRP. Fastboot only work in fastboot mode (bootloader screen)
Click to expand...
Click to collapse
I tried both. ADB devices gives me an empty line and fastboot devices (when in bootloader screen) gives me nothing at all. I've tested 2 different computers (both windows 7 x64) and it still won't detect it. When in TWRP windows tries to detect my device but it says "Unknown Device" and gives the yellow triangle.
fverswijver said:
Yes I've tried that but I don't know how to sideload it. adb doesn't see my device, fastboot doesn't either and windows doesn't recognize the device (although I have the adb naked drivers installed).
Click to expand...
Click to collapse
You might have to point the drivers to your phone. If you go into device manager, see if your Nexus 4 has an error. If it does, right click it, and then update the driver. Do a manual install, and point it to the .ini file for the driver
fverswijver said:
I tried both. ADB devices gives me an empty line and fastboot devices (when in bootloader screen) gives me nothing at all. I've tested 2 different computers (both windows 7 x64) and it still won't detect it. When in TWRP windows tries to detect my device but it says "Unknown Device" and gives the yellow triangle.
Click to expand...
Click to collapse
Fix your drivers, uninstall them and select the checkbox to delete the driver files, search Google on how to disable driver signature and try reinstalling the driver again.
or
Make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
eksasol said:
Make a bootable Ubuntu flashdrive, and use the ADB/Fastboot for Ubuntu link in my signature to install them.
Click to expand...
Click to collapse
I did this and still the same, adb gives an empty list and fastboot gives nothing.
fverswijver said:
I did this and still the same, adb gives an empty list and fastboot gives nothing.
Click to expand...
Click to collapse
Try using a different cable and on different computers.
eksasol said:
Try using a different cable and on different computers.
Click to expand...
Click to collapse
I've tried 3 different computers, 2 different OSes and 3 different cables. Nothing seems to work. I'm really starting to panic now.
fverswijver said:
I've tried 3 different computers, 2 different OSes and 3 different cables. Nothing seems to work. I'm really starting to panic now.
Click to expand...
Click to collapse
Just to clarify, see attachment for the correct name of the device if UND is installed correctly.
If you tried it with Ubuntu, make sure you do the 1st step from here also:
http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Same here
i installed the ota update normally with twrp installed everything went fine but im kind of disappointed in this update:/
eksasol said:
Just to clarify, see attachment for the correct name of the device if UND is installed correctly.
Click to expand...
Click to collapse
These are my findings:
Ubuntu:
- Bootloader (fastboot)
-- running lsusb in Ubuntu shows no device
- TWRP (adb)
-- running lsusb shows no device
Windows 7 (3 different computers)
- Bootloader (fastboot)
-- Windows gives the following popup, no device listed in Device Manager
- TWRP (adb)
-- Windows gives the same popup as on fastboot and this appears in the Device Manager:
fverswijver said:
These are my findings:
Ubuntu:
- Bootloader (fastboot)
-- running lsusb in Ubuntu shows no device
- TWRP (adb)
-- running lsusb shows no device
Windows 7 (3 different computers)
- Bootloader (fastboot)
-- Windows gives the following popup, no device listed in Device Manager
- TWRP (adb)
-- Windows gives the same popup as on fastboot and this appears in the Device Manager:
Click to expand...
Click to collapse
Is file transfering working atleast? If it is, then it's a software problem. If it isn't, then it could be a hardware problem, you can try replacing the USB charging board for the phone. Also some roms with corrupt files can cause this issues, so try a different roms if you haven't.
File transfer used to work but atm I'm unable to even connect it to a computer so I can't actually transfer any files. If I could I would flash a rom but no files = no flashing.
fverswijver said:
File transfer used to work but atm I'm unable to even connect it to a computer so I can't actually transfer any files. If I could I would flash a rom but no files = no flashing.
Click to expand...
Click to collapse
Get one of these: http://www.ebay.com/sch/i.html?_nkw=nexus+4+usb+charging+port+replacement&_sacat=0
If it don't work, then use the phone as a door stopper.
hey guys, I'm having the same problem here but with a Nexus 5 now.
Its been over a month and I've kind of gave up over the situation.
I couldn't resist to write a comment on the thread, since it appears to be the same problem as mine.
long story short, I decided to order an USB charging port to replace the one on the phone (as my last attempt).
Otherwise I will consider using the device as a door stopper.
Do not despair! Check this out: http://highonandroid.com/android-ro...r-android-in-a-bootloop-with-no-os-using-adb/
http://highonandroid.com/android-roms/how-to-copy-files-over-to-your-android-in-a-bootloop-with-no-os-using-adb/
i installed nokia xl rom into my device un fortunately i wipe the os and later i copy a rom file into my sd card and tried to flash tjat but it showing unable to open the zip. iam stuck with my company logo on the screen. twrp cannot open the zip and flash the rom. please help me in this issue.
thanks in advance
So I deleted everything in my phone, including the Rom I wanted to flash (smart, right?) and all I have is TWRP Recovery mode and Download Mode. When I put my phone into any mode, my PC does not recognize it and I therefor cannot fix it... I've tried it on three computers with downloading and updating the drivers. The first time it works after installing and updating the drivers, but when I put it in the second time it does not work. I need to unplug my phone in download mode while doing the LG program, and the computer won't recognize or find my phone. All help is greatly appreciated and thanks to repliers in advance
Day 2 of not having a phone: I can't do this xD I need to fix it somehow, if anyone can help me please do
Boot to recovery and start adb sideload mode. Then from your computer just adb sideload rom.zip
If your phone doesnt install the drivers once in sideload mode then manually search for the adb bridge driver from the android sdk and install it.
x714x said:
Boot to recovery and start adb sideload mode. Then from your computer just adb sideload rom.zip
If your phone doesnt install the drivers once in sideload mode then manually search for the adb bridge driver from the android sdk and install it.
Click to expand...
Click to collapse
Tried that and it would say "device not found." and other error codes. One time I was able to load my device onto the computer and after it completed the CM 11 transfer it stopped. I may have to order an OTG cable or something...
A friend of mine rooted my phone for me a while back. He's no longer around and I'm still pretty unfamiliar with the process without using twrp. I'm not sure what method he used. I was going to try flashing a stock os via adb but adb doesn't detect my phone. I'm sure it's a driver issue but I can't seem to fix the problem. I also have trouble transferring files with a USB cable. My computer sees the phone but as far as opening it to explore or transfer files, it doesn't work. I downloaded drivers from a link I saw in another thread on xda and installed some file with a weird format and that didn't fix the problem.
Can somebody please point me in the right direction?
First of all, I'd suggest you to try with a different cable. The one shipped with the RP2 is optimized for power and might cause issues when using it for data trasfer.
Secondly, generally speaking you should install adb platform tools (I don't remember installing specific drivers for the adb, to be honest). You probably want to install the google usb driver as well for the fastboot as well.
If you confirm that those solution do not provide a solution to you, we might look at other causes.
Once everything is workin, you can proceed to update (since you have root permissions, I am assuming you see the OTA but you don't know how to proceed). The procedure that I followed is this:
1. Download razer factory images for mr1
1. perform a nand backup with TWRP
3. extract the factory images somewhere, open the "flash_all.bat/.sh":
3.1. make the fastboot variable point to the actual fastboot executable (if you are not familiar with relative paths, use full path and it will work seamlessly)
3.2 remove/comment the line
Code:
fastboot erase userdata
4. run the script
5. reboot your phone and perform the OTA update
6. install arter12 kernel
7. In magisk installer download the zip and flash it with TWRP
So I've been troubleshooting for the past few hours. I'm familiar with the process that needs to be done. The issue I'm running into now is a driver issue. I deleted the Google driver and installed a Samsung driver just for laughs. I can view my phone and transfer files now flawlessly. But it still isn't detected by adb. I was just going to wipe my phone and reflash the stock rom with adb fastboot. I wonder if there's a way to flash the stock rom with the Razer bootloader until I figure out what's going on with adb?
The google drivers are for fastboot (bootloader), not adb. For adb I just let windows do the automatic install (I'm sorry, I just assumed you are using windows, tell me if that is not the case).
Keeping the assumption that you are using windows, try to uninstall all driver (both from installed apps and from installed driver. For the second step you will need to show in device manager, all hidden devices and uninstall all of them).
Reboot windows and reconnect phone, I'd expect it to be automatically recognized as Razer Phone 2.
As per bootloader, in W10 sometimes it's a pain in the ass installing the drivers as you might need to manually install them.