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
I really need help, I have tried the following, having TWRP V2.8.5.1 functioning and Fastboot also.
- Through TWRP, tried connecting the PC so I can Flash a ROM from there, but I can't seem to be able to connect the One to my PC so it will let me transfer files through cmd with adb push. My computer is a windows 10 OS with Samsung drivers and Android SDK full installed, still can't get it to work.
- Through Fastboot tried flashing cm-11-20141008-SNAPSHOT-M11-bacon.zip downloaded from Cyanogenmod page and using Oneplus One Toolkit 2.0, even though the Toolkit says the files are there, still phone continues to show 1+ logo and then rebooting.
Please I need some help.
Cheers. and thank you.
Why adb push when you can just copy the file over using a file manager (or a command prompt if you insist) and then flash from the internal storage?
I'm having the same issue but in my case I can boot into recovery or other stuff IF I HAVE THE USB PLUGGED IN
Maybe you can check and and let me know, if I found a solution I'll tell you, hoping the same from you please.
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 this could help.
Hiya. I managed to unlock bootloader/install twrp and root and went to see if i can put it back to stock.
When i try and sideload the stock firmware, my pc wont recognize adb while it's in sideload mode but it does in normal state.
I also get these errors (see pics)
I have tried installing all the drivers/changed usb ports but now i have no clue what it can be.
Any help please?
Thanks
PS. Using Windows 10
I'm having the exact same issue and I'm also really interested in a solution for this. Also tried uninstalling and reinstalling the drivers and switched USB Ports. The device gets detected without any problems in fastboot mode but as soon as I switch to Sideload Mode in stock recovery, Win 10 shows me this error and doesn't detect my device for sideloading.
Temporarily I could flash TWRP and sideload the zip via TWRP and cmd but I would also like to be able doing it without TWRP again.
Thanks in advance.
Can't anybody help us?
Just download the latest Android Studio software it contains the last ADB driver, i had the same issues after installing reboot, and ADB sideload will work !
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Today i tried to install a custom ROM update which caused a softbrick and now my device is stuck at the logo. I naturally decided to flash a stock rom in order to solve this. I went ahead and downloaded a MIUI 11 global stable one, next was rebooting into fastboot and connect it to my PC...
...When i rebooted my phone into fastboot, my PC didn't recognize the device at all. Device Manager says "USB Unknown Device (Device Descriptor Request Failed)". I verified the USB port and cable works properly with another phone, i installed USB drivers and ADB/fastboot ones, still nothing.
Is there anything I'm missing? I'm not very adept at these topics, I previously flashed mine into a PE custom ROM purely by following tutorials mindlessly.
Try the app "Xiaomi ADB/Fastboot Tools", this has the option to flash stock ROMs. The USB drivers that I have installed on my computer are "minimal ADB Fastboot 1.4.3".
You could also solve the problem with the tool "MiFlash Pro".
I hope someone in here can help me with the following problem:
I had an old Android version on my X720, which I wanted to update/install LineAge custom ROM with Android 10 on. Since the old Android was acting weird and USB debugging couldnt be enabled for some reason, I decided to wipe the System/Cache on it using TWRP recovery BECAUSE the device wasnt found on Windows 7 when plugging in via USB. Previously I installed ADB drivers and everything needed, but still Windows couldnt find the device and I was unable to move the Lineage ROM (plus GApps) to the device to be able to install it via TWRP. Anyway, now there is no OS installed and I can only boot into TWRP. I tried to ADB sideload the Lineage ROM via TWRP (via connected USB to my Notebook), but after typing "adb devices" and "adb sideload path...." etc. in Windows Terminal as Admin I always get "no devices found". So, when connecting the device to my Notebook, nothing is shown and the device doesnt appear under "Device Manager" and I think that's the main problem.
Does anyone have any solution or idea? Thanks a lot in advance!
try reading this useful thread:
https://forum.xda-developers.com/le-pro3/how-to/unbrick-leeco-phones-leeco-variants-t3847220
good luck!