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
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...
Since upgrading to Windows 8 the toolkit for android and pretty much the drivers are impossible to get working.
It seems that the device has nothing on it, zip, zero. No matter how I try to recover it what ROM it tried to install it didn't work and when I try to access anything via command prompt it can not find the device.
I look at the devices on system manager and there is one listed as unknown device but I do have android phone listed as a device.
It plugs in, makes a sound knowing there is something but its unknown. Tried using the Samsung drivers, no luck there.
I need to do a complete reboot, get the original folders back on but don't know how to get it to recognise and get things going again.
jozkam said:
Since upgrading to Windows 8 the toolkit for android and pretty much the drivers are impossible to get working.
It seems that the device has nothing on it, zip, zero. No matter how I try to recover it what ROM it tried to install it didn't work and when I try to access anything via command prompt it can not find the device.
I look at the devices on system manager and there is one listed as unknown device but I do have android phone listed as a device.
It plugs in, makes a sound knowing there is something but its unknown. Tried using the Samsung drivers, no luck there.
I need to do a complete reboot, get the original folders back on but don't know how to get it to recognise and get things going again.
Click to expand...
Click to collapse
You need to disable driver signing in windows 8 to be able to install drivers for the Nexus.
Done this already, for some strange reason the device listed in Device manager now knows its a adb interface but still listed as a unknown device.
Try getting to look at the Samsung drivers but still no luck.
When you go into the device properties it states the following;-
Windows has stopped this device because it has reported problems. (Code 43)
Windows 8 doesn't seem to work very well with adb/fastboot etc...
Do you have access to another computer that has Windows 7 (or XP, Linux?)?
Thanks for you help guys so far.
I do have a Vista 32bit laptop that I can use. Going to install the Toolkit, drivers etc on there and see how far it goes.
jozkam said:
Thanks for you help guys so far.
I do have a Vista 32bit laptop that I can use. Going to install the Toolkit, drivers etc on there and see how far it goes.
Click to expand...
Click to collapse
I've read where people who are using Win8 and fastboot flashing .img files to get back to stock, it stops/locks up in varying spots...after three hours of messing with it they try another OS (Win7, Linux) and it works within minutes.
Hopefully, Vista works...and I'm sorry you have to resort to Vista!
Well I seen to be getting somewhere but still with strange issues in Device Manager.
It shows Android device with the following devices below.
- Android Composite ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (working properly)
- Google Nexus 7 BootLoader Interface (yellow exclamation mark)
Further down I have Portable Devices with MTP Device listed (yellow exclamation mark).
I have Google Nexus Toolkit installed.
jozkam said:
Well I seen to be getting somewhere but still with strange issues in Device Manager.
It shows Android device with the following devices below.
- Android Composite ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (yellow exclamation mark)
- Google Nexus 7 ADB Interface (working properly)
- Google Nexus 7 BootLoader Interface (yellow exclamation mark)
Further down I have Portable Devices with MTP Device listed (yellow exclamation mark).
I have Google Nexus Toolkit installed.
Click to expand...
Click to collapse
Is this from your Vista machine or Win8 machine now?
RMarkwald said:
Is this from your Vista machine or Win8 machine now?
Click to expand...
Click to collapse
Vista machine.
jozkam said:
Vista machine.
Click to expand...
Click to collapse
Strange. Did you install the USB drivers? Maybe download them from Asus, extract them to your Desktop, right click on your N7 in Device Manager and unistall the drivers for your device, then connect your N7 and browse to the location of the downloaded USB drivers....?
Okay following God knows how many windows updates, following restart I can see that the MTP device is now showing as working properly.
When running the toolkit (version 3.2) it shows the device number at the top under ADB mode but not under Fastboot mode.
RMarkwald said:
Strange. Did you install the USB drivers? Maybe download them from Asus, extract them to your Desktop, right click on your N7 in Device Manager and unistall the drivers for your device, then connect your N7 and browse to the location of the downloaded USB drivers....?
Click to expand...
Click to collapse
Remind me which USB drivers?
Okay, puzzling but it appears to be getting somewhere.
In device manager there is one instance of Google Nexus 7 ADB Interface under Android Device and MTP Device under Portable Devices even though it seems to reinstall the same instance of MTP device every 1 minute or so.
I am installing the Samsung drivers however, the same as before when it comes to the Toolkit. The ADB mode list of devices shows correctly, nothing underneath fastboot mode.
What would be the next stage?
I would boot into fastboot, change directory to your Android SDK - Platform Tools directory, and if you type: fastboot devices
does anything show up?
Well, I would reflash stock images completely. Hopefully you have a backup of whatever is/was on your internal sd card because doing this will erase it.
You can get the image from here (note, I am assuming you have the N7 Wifi Only): https://developers.google.com/android/nexus/images#nakasi
Then, you can revert to stock by following this post: http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764332
NOTE: Step 10 the file name will be different than shown.
Ok so I have managed to get into the ClockworkMod recovery v6.0.1.9, going with the 'install zip from sideload', used the command adb sideload nakasi-jop40c-factory-6aabb391.tar.
The screen on nexus says:
Restarting adbd...
Finding update package...
E: Cant open /tmp/update.zip
(bad)
Installation aborted.
Sorry about this I am a complete amateur when it comes to this stuff, thanks for the help so far.
UPDATE: - I used the CLEANROM 2.5 zip file and it has now gone back to its original state, YES, thank you so much.
This may have happened when I started to use Paranoid Android, they brought out a beta 5 version, which originally worked but I can't see to get it updated via the 'update recovery' step.
http://forum.xda-developers.com/showthread.php?t=1800268
Thanks once again.
RMarkwald said:
I would boot into fastboot, change directory to your Android SDK - Platform Tools directory, and if you type: fastboot devices
does anything show up?
Well, I would reflash stock images completely. Hopefully you have a backup of whatever is/was on your internal sd card because doing this will erase it.
You can get the image from here (note, I am assuming you have the N7 Wifi Only): https://developers.google.com/android/nexus/images#nakasi
Then, you can revert to stock by following this post: http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764332
NOTE: Step 10 the file name will be different than shown.
Click to expand...
Click to collapse
Steps done, back to stock which is great, thanks a lot.
Oh man just when I thought my problems were finished.
One thing I forgot to do was run the superuser zip file to give permissions on the clockworkmod recovery. Even trying to do something with Rom Manager within jellybean itself but it says I need permissions.
How can I reverse back and get the superuser.zip from working? At the moment I can not access recovery, tried using command prompts and Rom Manager but to no avail.
jozkam said:
Oh man just when I thought my problems were finished.
One thing I forgot to do was run the superuser zip file to give permissions on the clockworkmod recovery. Even trying to do something with Rom Manager within jellybean itself but it says I need permissions.
How can I reverse back and get the superuser.zip from working? At the moment I can not access recovery, tried using command prompts and Rom Manager but to no avail.
Click to expand...
Click to collapse
You can boot back into fastboot, and download the latest TWRP Recovery from here: http://teamw.in/project/twrp2/103
They even give you instructions on the command to run type in: fastboot flash recovery <name of recovery file>
Put the .img file in your Android SDK - Platform Tools folder as well.
Type in the flash recovery command, then reboot to recovery.
From there, you can flash the Superuser.zip (I assume you have it?). If not, here it is: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
You'll also want to make sure that the following files are deleted/removed:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
The reason being is that if they are there, it will reload the stock Android recovery at reboot, which will remove TWRP or CWM if you have flashed those. I would just rename them by putting a .bak on the end of the file names. But to do this, you'll need root first. You may have to: fastboot flash recovery, flash SuperSU zip, reboot, browse to those two locations to verify if those files exist/rename them, fastboot flash recovery again...reboot, and recovery may stick. When I went back to stock and fastboot flashed TWRP, I checked for those files and they weren't there, and recovery stuck just fine.
You're learning the manual way, congratulations! Not too bad is it?!
RMarkwald said:
You can boot back into fastboot, and download the latest TWRP Recovery from here: http://teamw.in/project/twrp2/103
They even give you instructions on the command to run type in: fastboot flash recovery <name of recovery file>
Put the .img file in your Android SDK - Platform Tools folder as well.
Type in the flash recovery command, then reboot to recovery.
From there, you can flash the Superuser.zip (I assume you have it?). If not, here it is: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip
You'll also want to make sure that the following files are deleted/removed:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
The reason being is that if they are there, it will reload the stock Android recovery at reboot, which will remove TWRP or CWM if you have flashed those. I would just rename them by putting a .bak on the end of the file names. But to do this, you'll need root first. You may have to: fastboot flash recovery, flash SuperSU zip, reboot, browse to those two locations to verify if those files exist/rename them, fastboot flash recovery again...reboot, and recovery may stick. When I went back to stock and fastboot flashed TWRP, I checked for those files and they weren't there, and recovery stuck just fine.
You're learning the manual way, congratulations! Not too bad is it?!
Click to expand...
Click to collapse
Wouldn't have got this far without you, really appreciate your help, now its stable with 2.54 Paranoid Android.
:good:
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?
I tried installing CM with CM Installer for MAC ... until it got stuck in bootloop.
Using adb I pushed image, still bootloop.
Reset to factory, cleared partition, flushed dalvik cache, all the same.
adb commands seem to work since I can make the phone reset and so forth.
details:
mako 16 GB
HW version - rev_11
bootloader version MAKOZ30d
baseband M9615A-CEFWMAZM02.0.1701.02
signing - production
secure boot - enabled
lock state - unlocked
recovery mode is CWM v6.0.4.7 (assuming it got installed by the CM installer for MAC)
tried by hand to resuscitate with cm-11-20141008-SNAPSHOT-M11-mako.zip and cm-11-20141107-NIGHTLY-mako.zip using sideload to no avail - still bootloops despite numerous factory resets and cache partition wipes.
any ideas please?
thanks
This is what i use: http://forum.xda-developers.com/nex...olkit-wugs-nexus-root-toolkit-v1-8-2-t2015469
Has multiple options for going back to stock, rooting, and lots of other things.
TreatnHerRight said:
This is what i use: http://forum.xda-developers.com/nex...olkit-wugs-nexus-root-toolkit-v1-8-2-t2015469
Has multiple options for going back to stock, rooting, and lots of other things.
Click to expand...
Click to collapse
That looks great ... and uses Windows only
I can boot Windows under VMWare Fusion on my MAC however not 100% sure if that would work within that environment as I need to do some USB passthrough.
Thanks for the pointer though.
ilmoomino said:
I tried installing CM with CM Installer for MAC ... until it got stuck in bootloop.
Using adb I pushed image, still bootloop.
Reset to factory, cleared partition, flushed dalvik cache, all the same.
adb commands seem to work since I can make the phone reset and so forth.
details:
mako 16 GB
HW version - rev_11
bootloader version MAKOZ30d
baseband M9615A-CEFWMAZM02.0.1701.02
signing - production
secure boot - enabled
lock state - unlocked
recovery mode is CWM v6.0.4.7 (assuming it got installed by the CM installer for MAC)
tried by hand to resuscitate with cm-11-20141008-SNAPSHOT-M11-mako.zip and cm-11-20141107-NIGHTLY-mako.zip using sideload to no avail - still bootloops despite numerous factory resets and cache partition wipes.
any ideas please?
thanks
Click to expand...
Click to collapse
Honestly, when I get into these situations I just flash the stock images and use that as a starting point. (I'm guessing your recovery is still working fine, given what you've said, so you can pull that out of the zip it sends so it doesn't write over it)
My approach, however, is usually, "damn, I messed up, let's go back to a known good point and try again" though, so keep that in mind if you decide to follow this path.
nic0lette said:
Honestly, when I get into these situations I just flash the stock images and use that as a starting point. (I'm guessing your recovery is still working fine, given what you've said, so you can pull that out of the zip it sends so it doesn't write over it)
My approach, however, is usually, "damn, I messed up, let's go back to a known good point and try again" though, so keep that in mind if you decide to follow this path.
Click to expand...
Click to collapse
That didn't work either (the restore to stock).
The USB passthrough on VMWare fusion works like a charm, ADB sees the device, passing commands on from the Windows application, rebooting and so forth.
However once it goes through the repair process at some point I get some strange cyan screen with white and lilac blinking lines and the program keeps saying "waiting for your device (or phone, or whatever" ...
Losing the will to live.
ilmoomino said:
That didn't work either (the restore to stock).
The USB passthrough on VMWare fusion works like a charm, ADB sees the device, passing commands on from the Windows application, rebooting and so forth.
However once it goes through the repair process at some point I get some strange cyan screen with white and lilac blinking lines and the program keeps saying "waiting for your device (or phone, or whatever" ...
Losing the will to live.
Click to expand...
Click to collapse
Why are you using VMWare? You should be able to download the tools you need for WIndows, Mac, or Linux.
Go and grab the Android SDK and install the "Android SDK Platoform-tools" and download 4.4.4 image from Google.
Once you have those two things, unzip the factory image and do "adb reboot bootloader" and then run "sh flash-all.sh" from a command prompt. This will use fastboot to write an img file to the partitions on the device, so if you can't run the SDK tools, for whatever reason, use fastboot to run the commands in the file. (That is, don't use recovery and adb sideload, do it through fastboot)
The -w option will wipe your data, so if you want you can try and run the last line (fastboot -w update image-occam-ktu84p.zip) without the "-w", but if it doesn't work then I'd try it again with it.
If you can boot into the bootloader and recovery then your device isn't dead. Worst case you have to go to a friend's place and flash it there.
nic0lette said:
Why are you using VMWare? You should be able to download the tools you need for WIndows, Mac, or Linux.
Go and grab the Android SDK and install the "Android SDK Platoform-tools" and download 4.4.4 image from Google.
Once you have those two things, unzip the factory image and do "adb reboot bootloader" and then run "sh flash-all.sh" from a command prompt. This will use fastboot to write an img file to the partitions on the device, so if you can't run the SDK tools, for whatever reason, use fastboot to run the commands in the file. (That is, don't use recovery and adb sideload, do it through fastboot)
The -w option will wipe your data, so if you want you can try and run the last line (fastboot -w update image-occam-ktu84p.zip) without the "-w", but if it doesn't work then I'd try it again with it.
If you can boot into the bootloader and recovery then your device isn't dead. Worst case you have to go to a friend's place and flash it there.
Click to expand...
Click to collapse
I am using VMWare Fusion since my Windows work laptop is dead (courtesy of lost charger).
So I must use my Mac (which used the CM installer where things went sour).
Doubt it is a problem since I can get ADB to work.
I have already dowloaded the Android SDK Platoform-tools and stock 4.4.4.
I used ADB on MAC, but after I copy the ROM the phone does some scroll-bar progress, then I clear partitions/factory erase/cache ... and boot loop again.
I will follow your advice and use the described process.
You are right - as long as I have bootloader I am safe.
Might go and buy Moto X+1 or Sony X3 ... as I want to go 4G but thought might use the N4 for another few months.
thanks
following instructions from nic0lette I have now my phone back to normal ...
will try CM using the same instructions ... well, using the flash-all.sh as a base script
thanks (and "thanked")
Hello,
i delete the System and Data on my LeEco Le Pro3.
TWRP is installed.
Can i flash a rom with an usb flash drive in TWRP or fastboot?
greeting gizez
Boot into TWRP and use MTP to transfer ROM file from your PC to Phone. Then flash the ROM.
I have this problem, but I can't see the phone when connected to a PC. adb sideload doesn't work (adb devices doesn't find anything). Do I need to install driver for the phone? I originally used fastboot to unlock the bootloader and flashed TWRP, then installed LineageOS and gapps just fine. I then proceeded to wipe system in TWRP (I was trying to get back to new phone setup so I can transfer stuff from old phone, which I skipped the first time).
Any idea how to get around this? I tried plugging in pen drive through an micro USB OTG and a usb-c to micro usb adapter, but it's not recognized in TWRP, either. Would very much appreciate any help!
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
marik1 said:
[...]
Go Advanced -> ADB Sideload, type "adb sideload aicp_zl1_n-12.1-NIGHTLY-20170516.zip" (zip of OS should be downloaded and put into "Minimal ADB and Fastboot" installation folder with name as same as the text of command). It should let you turn on system.
[...]
Click to expand...
Click to collapse
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
marik1 said:
You can get your data. First try to connect phone while is in TWRP. Your phone can be detected as file manager. Try this.
If not, check my theme;
https://forum.xda-developers.com/le-pro3/help/brick-t3609704
Also "adb push" command can be helpful. Sometimes phone is not current on adb devices list, but you can also try. As i remember, target should be /sdcard/0
Click to expand...
Click to collapse
Thanks, but unfortunately no luck. Both adb sideload and adb push said error - device '(null)' not found. It seems like the PC is not recognizing the phone. I checked device manager on the PC, it showed LEX727. I right-click and had it install the driver. It says driver successfully installed. Then device manager showed MTP device with a !. I again tried having driver installed, but this time it doesn't find any driver.
I'm at my wit's end... Any more suggestion?
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
marik1 said:
TWRP and/or Minimal ADB isn't trouble here? Tried you both on main menu of TWRP and in ADB Sideload mode? You can also try do it trough bootloader, for this check my link and read all.
Click to expand...
Click to collapse
Actually, the problem is solved, by using another PC. This one showed LEX727 in windows explorer as soon as i plug in the phonr (in twrp). I was able to drag and drop the zip files to the phone and go on my merry way. Now back in business!