Related
Hello all!
I have a major, major, problem. Last night I wanted to flash a new ROM, so I had everything wiped from my sdcard so it will be like new again. Sadly, I was retarded enough to also do a wipe on /system. Now there is no Android OS loaded on my phone anymore and no ROMs on my internal sdcard to flash it.
The phone would boot up and will be stuck on the screen with the white Google logo and the white unlocked lock.
I am still able to boot into Download mode, Fastboot mode and CWM. The bootloader is also unlocked.
The problem is that none of my PCs and Laptops would recognize my phone, not even trying numerous tutorials and reading different similar threads.
http://forum.xda-developers.com/showthread.php?t=1760787
http://forum.xda-developers.com/showthread.php?t=1869380
http://forum.xda-developers.com/showthread.php?t=1379875
http://forum.xda-developers.com/showthread.php?t=2370684
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1777593
Also Odin and GNEX Toolkit doesn't see that my device is plugged in, both in Fastboot mode and Download mode, so I cannot flash with that either.
I hope someone had experienced the same problem or knows a solution to my problem.
Thanks in advance!
you have a driver problem. you need to uninstall your drivers and reinstall them.
So normally my PC would detect my phone even without it having any data or OS on it?
Could you maybe point out for me what kind of drivers I actually need? I have tried so many I got really confused.
iKaosTony said:
So normally my PC would detect my phone even without it having any data or OS on it?
Could you maybe point out for me what kind of drivers I actually need? I have tried so many I got really confused.
Click to expand...
Click to collapse
Focus on getting the correct fastboot drivers installed, and try to get your computer to recognize the phone when you type "fastboot devices" while connected via USB.
Flash a stock image from Google in fastboot mode. Boot into it at least once in order to regenerate the internal storage partition, before futzing around with custom recovery, root and new ROMS etc. If you flash CWM/TWRP without first booting once into the OS, you may be unable to write files to internal storage hence blocking any further progress.
I have tried almost everything to get the drivers installed on all the PCs I have at home, non of them is regocnizing my device.
tried it on both Windows 7 64Bit and Windows XP 32Bit.
Is my warrenty void if the bootloader is unlocked?
iKaosTony said:
I have tried almost everything to get the drivers installed on all the PCs I have at home, non of them is regocnizing my device.
tried it on both Windows 7 64Bit and Windows XP 32Bit.
Is my warrenty void if the bootloader is unlocked?
Click to expand...
Click to collapse
You're holding it wrong. Either that or your USB port/USB cable has died.
Hi people,
I have my nexus 7 4g tablet already for a few months, when I bought it I had a windows PC and I rooted it, today I flashed a new rom but the rom didn't work and I accidentally deleted the OS on the Tablet, now I have searched for a solution on the net but I havent found one for Mac because I upgraded to a Macbook Air recently, don't have a windows PC no more...
Could somebody PLEASE help me? My Nexus 7 just lies here bricked doing nothing, such a waste of such a beautiful and good tablet!
Thx
Misha
Miisham9 said:
Hi people,
I have my nexus 7 4g tablet already for a few months, when I bought it I had a windows PC and I rooted it, today I flashed a new rom but the rom didn't work and I accidentally deleted the OS on the Tablet, now I have searched for a solution on the net but I havent found one for Mac because I upgraded to a Macbook Air recently, don't have a windows PC no more...
Could somebody PLEASE help me? My Nexus 7 just lies here bricked doing nothing, such a waste of such a beautiful and good tablet!
Thx
Misha
Click to expand...
Click to collapse
okay i dont know how to do it on Mac, but it similar to PC. First, you got to be fimilar with terminal (similar to CMD for windows)
second, read this http://htc-one.wonderhowto.com/how-to/install-adb-fastboot-mac-os-x-send-commands-your-htc-one-0151178/
Third, download the rom
fourth, plug nexus into computer and then reboot in into custom recovery
fifth, i only know of TWRP to use sideload. http://teamw.in/ADBSideload
pretty much you can push a rom from your computer into the the device when stuff like this happends.
PS might be other easy ways but i dont know much. I have learned from trial and error. I have also deleted the OS many times.
Might be easier to use fastboot commands to achieve the same result
---------- Post added at 07:09 AM ---------- Previous post was at 07:07 AM ----------
http://forum.xda-developers.com/showthread.php?t=1917237
nixvaldez said:
okay i dont know how to do it on Mac, but it similar to PC. First, you got to be fimilar with terminal (similar to CMD for windows)
second, read this http://htc-one.wonderhowto.com/how-to/install-adb-fastboot-mac-os-x-send-commands-your-htc-one-0151178/
Third, download the rom
fourth, plug nexus into computer and then reboot in into custom recovery
fifth, i only know of TWRP to use sideload. http://teamw.in/ADBSideload
pretty much you can push a rom from your computer into the the device when stuff like this happends.
PS might be other easy ways but i dont know much. I have learned from trial and error. I have also deleted the OS many times.
Click to expand...
Click to collapse
Your 3rd link doesn't exist?
Already thanks for the help..
Miisham9 said:
Hi people,
I have my nexus 7 4g tablet already for a few months, when I bought it I had a windows PC and I rooted it, today I flashed a new rom but the rom didn't work and I accidentally deleted the OS on the Tablet, now I have searched for a solution on the net but I havent found one for Mac because I upgraded to a Macbook Air recently, don't have a windows PC no more...
Could somebody PLEASE help me? My Nexus 7 just lies here bricked doing nothing, such a waste of such a beautiful and good tablet!
Thx
Misha
Click to expand...
Click to collapse
boot into bootloader, put tab in fastboot mode. connect tab to mac. open terminal in mac and type fastboot command to load custom recovery image. in bootloader chose recovery and restart.u will boot into custom recovery. now install a custom rom..
EDIT: u should have sdk platform-tools for mac installed and also knowledge of mac fastboot commands
moonblade said:
boot into bootloader, put tab in fastboot mode. Connect tab to mac. Open terminal in mac and type fastboot command to load custom recovery image. In bootloader chose recovery and restart.u will boot into custom recovery. Now install a custom rom..
Edit: U should have sdk platform-tools for mac installed and also knowledge of mac fastboot commands
Click to expand...
Click to collapse
thanks this helped!
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3485186
Having the exact same Problems with my OP3 running everything stock 3.2.7 expect for the fact the device is unlocked...
Would love to hear how the problem can be solved!
ELoTRIX said:
http://forum.xda-developers.com/showthread.php?t=3485186
Click to expand...
Click to collapse
Hmmm Windows 7.
I can most certainly try that but the real question now is; how the hell did it work previously on my Windows 10 machine and refuses to work now? But at least I have a solution to try out, in the mean time! Thanks!
railpressureflip said:
Okay so now that I've scanned pretty much all of what the internet has to offer on this issue, I'm helpless and forced to write a new thread here about this.
Yes, a similar question has been replied to a million times before, but absolutely none of that helped, made no difference whatsoever.
So earlier, I was on the stock rom, with TWRP flashed and root access. But wanted to switch to the community build. Tried the twrp trick to install the CB but that didn't work, so flashed the stock OP3 rom and flashed community build.
All went fine, until I tried flashing back TWRP. Used the traditional ADB method of doing that, seemed to have flashed it but tried going into recovery only to be presented with a black screen. I got fed up of that trying to fix it for a whole day so I just left it, because I could still boot into the OS and that worked fine.
Fast forward to about a week later; somehow the flash didn't work and I still have stock recovery. Now I try flashing TWRP again, but I discover that my device doesn't get detected in fastboot. It absolutely refuses to.
It DOES, however, gets detected in the OS just fine.
I've tried every which way, absolutely NOTHING seems to work AT ALL.
- OEM unlocking is checked, if that makes a difference
- USB debugging is turned on
- Uninstalled all USB drivers related to the device, and installed them via device manager (but it gave me this error:
"the folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems)
seeing as I'm on an x64 version of Windows (its worked before with my Nexus 5, I swear)
- Tried it with different adb fastboot files, from all over the internet. All of them show just that blank space after I type in 'adb devices'
- Installed universal adb drivers.
- Samsung drivers.
- Obviously the official OnePlus drivers.
- Used Usbdeview to uninstall / force stop and re-installed the drivers.
- All in one tool
Now I'm thinking, I should try to re-lock the bootloader and unlock it again, or do like hard rest sort of things. I have no idea though, how this would affect the detection in fastboot.
Anyone have any ideas? Because I'm out of all of them, and so is most of internet.
TL;DR - Adb devices detects phone while booted in OS, but not in fastboot. Tried all methods, nothing works. Going to do lock bootloader then unlock it and try again, if not that then going to do a clean wipe and install the community build again, hoping that would work. Should I?
Click to expand...
Click to collapse
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
I am having a similar issue. I have a brand new OP3. Everything stock. I'm attempting to unlock the bootloader and have found that while ADB recognises the phone, Fastboot doesn't. I'm pretty sure it's a driver issue and I have no idea how to fix.
Hello
Everything is working good
it seems to be a problem with adb Windows 10 IDK
, it is better to do it on Windows 7
Follow this :
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
abhi0502 said:
You need modified twrp by @eng.sdk.
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
Click to expand...
Click to collapse
I'm afraid you've missed the point, my friend.
If the phone does not get detected in the fastboot, it means I cannot flash anything, period. No original TWRP, no modified TWRP.
I had this exact issue and fixed it.
Fastboot would never see my device, no matter which driver package I tried or no matter how I tried to install or force the correct drivers. Turns out Windows 10 (and Windows 8) has a feature that completely prevents installation of unsigned drivers, which blocks the fastboot driver. If you're seeing "Kedracom" or "Android Device" in the device manager, then your driver is NOT actually installed. This is true even if Windows doesn't throw you an error message during install, or if you appear to force the installation. Even though it looks like you're doing the install correctly, Windows just ignores your unsigned drivers.
You need to temporarily disable the security feature to permit installation of unsigned drivers. This involves invoking a special restart function. Here's the howto for Win10: http://www.howtogeek.com/167723/how-...igned-drivers/
Once you've done this, on the next reboot you can do a forced install of the unsigned fastboot drivers you downloaded for the OP3. And simply rebooting your computer restores the security feature.
It's mostly because of the windows security over unsigned drivers.. Try the above method or just the cmd way..
Sent from my Xiaomi Mi 5 using XDA Labs
Hi,
I had a running N2AOS with CM12 install, then did a return2stock but something went wrong
I have orange/blue boot sequence and can get into TWRP without a problem, can boot into fastboot etc. from TWRP. Battery is 100% - ok, too
But system seems empty now. Maybe wiped wrong. I see a lot of empty folders incl. sdcard etc. I've basic ux knowledge - can use TWRP terminal or file manager.
Is there a chance pulling a rom in the twrp using the usb? On win 8.1 I can delete the adb/amazon drivers. then it gets recognized as "Kindle" or "Tate", but can't connect.
My primary system is macOS Sierra, but have a running windows 8.1/ubuntu laptop with usb 2/3.
I think I'm equipped perfectly and the KF7HD2 is not hard bricked, but leaking adb/kindle knowledge. and the most trys end up with "< waiting for device >"
update: when I try TWRP > mount (anything) it gets recognized by win 81 or ubuntu for a short time, but I can't read or write a thing
maybe someone could help?! I read and tried as much as possible, but don't want to kill my old kindle because my girlfriend wants to read with it
thank you very much!
best
tom
addition: can I connect via twrp console and usb or wifi to a local ip or sth to use ftpget
really nobody an idea?
I have an old Samsung Galaxy Nexus which I rooted and loaded with CWM V6.0.5.1 and an earlier version of Cyanogen some years back. I'd like to replace the old CWM with the latest TWRP and then load LineageOS to give the phone a new lease of life. The process of swapping Recoveries I found on the net involves using 'Platform Tools' including adb.exe, fastboot.exe etc etc. Adb can see the phone and act on it but Fastboot cannot. The problem seems to be that when I put the phone into Fastboot Mode it is recognised by Win10 Device Manager as a new device called "Android 1" but the driver for this new device is not loaded. I think this missing Android USB driver is the problem. Win10 cannot find the driver on line.
The procedure I was trying to follow said that you could find this driver by installing Android Studio and going through some steps with SDK Manager. I cannot get Android Studio to install properly. It seems to install and then starts downloading additional components but never finishes. There is discussion of this problem in other forums.
Does anyone have a link to the Android USB driver I am missing (which will allow fastboot to detect the phone)? Is there a simpler way to swap CWM for TWRP? Thanks for any assistance.
erich_vogt said:
I have an old Samsung Galaxy Nexus which I rooted and loaded with CWM V6.0.5.1 and an earlier version of Cyanogen some years back. I'd like to replace the old CWM with the latest TWRP and then load LineageOS to give the phone a new lease of life. The process of swapping Recoveries I found on the net involves using 'Platform Tools' including adb.exe, fastboot.exe etc etc. Adb can see the phone and act on it but Fastboot cannot. The problem seems to be that when I put the phone into Fastboot Mode it is recognised by Win10 Device Manager as a new device called "Android 1" but the driver for this new device is not loaded. I think this missing Android USB driver is the problem. Win10 cannot find the driver on line.
The procedure I was trying to follow said that you could find this driver by installing Android Studio and going through some steps with SDK Manager. I cannot get Android Studio to install properly. It seems to install and then starts downloading additional components but never finishes. There is discussion of this problem in other forums.
Does anyone have a link to the Android USB driver I am missing (which will allow fastboot to detect the phone)? Is there a simpler way to swap CWM for TWRP? Thanks for any assistance.
Click to expand...
Click to collapse
I used Odin and TWRP in a .tar file. This seemed to work ok but on rebooting the phone now gets stuck on the Google logo. I assume it is a boot loop. The solution to this according to various threads is to either re-flash a stock image or to flash with a custom ROM. I'll try the latter.
I don't think this is going to work. Odin requires .tar, .bin or .tar.md5 files and all the ROMs I can see are in .zip format. Anyone got any ideas?
erich_vogt said:
I don't think this is going to work. Odin requires .tar, .bin or .tar.md5 files and all the ROMs I can see are in .zip format. Anyone got any ideas?
Click to expand...
Click to collapse
I found some stock ROMs for the G-I9520 that were in .tar format and installed one using Odin. This seemed to work fine. I have to use Odin because the phone appears to be soft-bricked in that neither adb nor fastboot can detect it. Then I used Wugfresh's very excellent Nexus Tool Kit to try to sort out the driver issue, unlock, root and install TWRP. Again this all seemed to go fine. I how have a rooted stock G-I9250 and can boot into TWRP.
In Windows 10 Wugfresh's driver tool appeared to be saying that standard drivers included in his tool would not work properly and that it would be necessary to install drivers manually and disable "driver signature enforcement" on Windows 10. This requires booting Windows 10 into trouble shooting mode. Again this appeared to go fine although it was not clear from the choice of drivers that Windows 10 could see exactly which ones I should install. Anyway, I now have no exclamation marks in Device Manager but there are STILL problems.
I think I installed a suitable MTP driver and an adb driver which appear in different parts of Device Manager. The MTP driver says it "requires further installation". The other driver seems OK. The problem now with the phone is that in MTP mode I can see all the default folders in the internal storage but I cannot copy anything into them. Either, I guess, I do not have permission for some reason, or, the MTP driver is at fault and will not actually fully access the internal storage. So I can't download a copy of Lineage 13 onto the phone for TWRP to install. This is probably a common problem but not one I know how to fix. Any help would be appreciated.
erich_vogt said:
I found some stock ROMs for the G-I9520 that were in .tar format and installed one using Odin. This seemed to work fine. I have to use Odin because the phone appears to be soft-bricked in that neither adb nor fastboot can detect it. Then I used Wugfresh's very excellent Nexus Tool Kit to try to sort out the driver issue, unlock, root and install TWRP. Again this all seemed to go fine. I how have a rooted stock G-I9250 and can boot into TWRP.
In Windows 10 Wugfresh's driver tool appeared to be saying that standard drivers included in his tool would not work properly and that it would be necessary to install drivers manually and disable "driver signature enforcement" on Windows 10. This requires booting Windows 10 into trouble shooting mode. Again this appeared to go fine although it was not clear from the choice of drivers that Windows 10 could see exactly which ones I should install. Anyway, I now have no exclamation marks in Device Manager but there are STILL problems.
I think I installed a suitable MTP driver and an adb driver which appear in different parts of Device Manager. The MTP driver says it "requires further installation". The other driver seems OK. The problem now with the phone is that in MTP mode I can see all the default folders in the internal storage but I cannot copy anything into them. Either, I guess, I do not have permission for some reason, or, the MTP driver is at fault and will not actually fully access the internal storage. So I can't download a copy of Lineage 13 onto the phone for TWRP to install. This is probably a common problem but not one I know how to fix. Any help would be appreciated.
Click to expand...
Click to collapse
I went back to Device Manager and changed the MTP driver to the other alternative which now exists in the system. It's called "MTP USB Device" and is a Microsoft driver. This seemed to improve the situation and allowed me to see all of the contents of the folders in the phone's Internal Storage. I discovered by a process of trial and error that now I could copy files into all the folders except the folder called !ReadyToFlash. I believe this folder may have been created by TWRP when it installed. All the other folders are now behaving sensibly. I copied the Lineage 13 zip into the Downloads folder and booted the phone into Recovery Mode. TWRP 3.0.2-0 was able to install Lineage and everything seems to be working correctly although I haven't tested all the functions yet.
I notice that although the radio can see my 5GHz 802.11ac wifi it seems to be unable to connect and can only connect to the 2.4GHz wifi. I don't know if this a hardware limitation arising from the original modem or a software limitation of the Lineage modem driver. This thread, although it's just me, might give another noob attempting to reconfigure their old Galaxy Nexus a few pointers.