I made the dumb mistake today of flashing my Nexus 7 with the wrong gapps and as a result setup would continuously crash.
I first tried to reboot into recovery by entering fastboot mode (power + volume buttons) but all i got was the google logo for all eternity
next I tried reverting to stock with the nexus 7 rootkit but it always failed on the fastboot check saying my device could not be detected.
Assuming my drivers were not working correctly I manually installed the google usb drivers and at this point if I look in the device manager I see Android device > Android Bootloader Interface but if I run the adb devices command I get nothing.
I feel like I'm at the end of my rope here so I could use any suggestions.
p.s. usb debugging is not enabled because I had just done a factory reset and I can't enable it because I can't really access anthing after booting up.
solved
Ok so after installing the google driver I decided to give the root tool and leaving my nexus 7 plugged in for a while I noticed that the fastboot screen was no longer frozen and decided to try the rootkit again and this time it worked like a charm so problem solved!!!
I guess I couldn't detect it with adb because usb debugging wasn't enabled but the rootkit was still able to restore it using the fastboot method.
Related
I was running an August MIUIAndroid ROM release, with no other modifications.
Downloaded the latest 12/10 release and placed it on my Internal SD. Rebooted to recovery, wiped cache, wiped dalvik cache and flashed the release.
Rebooted tablet, wherein it passed the Google logo and then just stayed blank.
Pressed volume up/down and power for a few seconds, went into fastboot. Tried to go into recovery by selecting that option in fastboot menu, tablet restarts and stays at the Google logo.
Went back into fastboot, connected the tablet to my PC with a view to using mskip's toolkit. PC doesn't recognise the tablet despite drivers being present, and the tablet becomes unresponsive in fastboot mode (can't move between menu options with volume buttons and even on disconnecting USB, have to long press power to restart).
Any help would be appreciated as I'm unsure whether ASUS will honour the warranty...
You said you can still go to bootloader, then try do manual boot(fastboot boot nameofcustomrecovery.img) and restore your backup(that is if you have any).
Tapatalked from my Ace 2
Easy
Connect it to the PC (better use the one you used in the past, with all the drivers... also use the cable that came with it)
turn it on spamming the vol until you get in the screen with start, shut down and recovery.
Go to recovery and boom, you are back to recovery
dont do nothing on the pc, just the fact that its connect will enable it:good:
Thank you for both of your replies.
This is what I did:
Connected my Galaxy Nexus to PC
Switched on USB Debugging, ADB drivers got auto-installed
Rebooted Galaxy Nexus into Bootloader, appropriate driver got installed
Switched on Nexus 7 in Bootloader mode, started praying
Swapped the Galaxy Nexus with the Nexus 7 - this time it didn't hang
Used mskip's toolkit to flash bootloader, stock recovery and stock ROM
Reason the tablet wasn't being recognised in Bootloader mode earlier was because while I had connected it to the PC many times, I'd never had USB debugging enabled (tablet was unlocked and rooted on my laptop) and had never been in Bootloader while tablet was connected to PC. So the PC didn't know what was connected to it, and presumably due to the issues with the tablet, the PC wasn't able to recognise it and download the drivers...
*huge sigh of relief* Thanks again guys!
The problem is I can't unbrick and restore my nexus to stock rom.
I can't boot the device and I'm only able to boot to bootloader. However, my computer doesn't recognize the nexus. It keeps saying Window cannot recognize it whenever I plug my tablet to the computer in bootloader. I tried uninstall and reinstall driver several times, but none of them seems to work . ----> That means I can't even use adb to restore the phone simply because my tablet is not recognized in window.
Is there anyway to fix this problem? I really need your helps as soon as possible.
Thank you for reading !
Get to bootloader. Then use Wugs toolkit, open advanced options. On the very left is something like "temp boot to recovery". Once that boots it to recovery, ADB should work. It did for me. I was in some trouble last night and got out by this. If you know how to use adb/fastboot commands, you should be good. And I uninstalled my drivers and when I plugged it in the device automagically reloaded the drivers. But you have to do it a few times. Had to do it in bootloader, recovery, and another point. Anytime it asks to load drivers/etc do it.
I can't boot to recovery through Wug Tool Kit. It keeps saying Fastboot device was not found >"<
By the way, whenever I connnected my device to computer, the bootloader freezes :|
What were you doing before you go into this situation?
I was on Glazed Jelly Bean rom and wanted to go back to stock rom. I used nexus 7 toolkit to do all the work for me. However, there was something wrong like the toolkit didnt extract the stock img right or something like that, my tablet got bootloop, and what happened next was what i had been telling you guys.
Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.
Consider deleting the drivers from Windows after uninstalling them otherwise Windows may try to be "clever" and reinstall the bad driver when you plug the device in. The Nexus 7 drivers from Asus can be downloaded here and Google's USB drivers are here
Travisdroidx2 said:
Best bet is if somehow you could get into recovery or get adb working. Might want to uninstall drivers and install again and reboot computer. I would suggest using this thread and flash things manually back to stock. http://forum.xda-developers.com/showthread.php?t=1907796 but you would need adb working.
When you power off device and use volume and power can you get it to go into boot loader then plugged into computer try to get to recovery or adb.
Click to expand...
Click to collapse
What if I couldn't get adb working?
I tried everything and windows still doesn't recognize my device in fastboot
Have you tried Nexus Root Toolkit v .1.5.4?
kiddo94 said:
I tried everything and windows still doesn't recognize my device in fastboot
Click to expand...
Click to collapse
try connecting to the usb port at the back of your computer
Paranoid flashed with the bricked kernel did this to me once right after the move to 4.1.2. Even with a full wipe and all the usual safety precautions it just stuck on bootloop forever and wouldn't let me in. I chalked it up as that's what I get for being the guy that's never satisfied with stock. I was unable to get my nexus7 fixed. I sent you a suggestion on pm though.
Never mind everyone. Thank you so much for your help.
I tried install the nexus 7's driver on another computer and it recognized my device in bootloader mode, and restore everything back to stock now. Thank you so much!!!!
Mine did that to the first time I tried. After I got it to work, the permissions were all messed up and I could not get it to download anything off the web and I was getting a playstore error 90% of the time as well. I finally just wiped everything on my tablet, installed the stock rom via N7 toolkit, then reflashed smooth rom, and all is working now. It may have been a bug with the older version of N7 toolkit, as I updated it before I reran everything.
so i have a nexus 7 stuck in a bootloop, i never enabled usb debugging, and cant get my pc to recognize the device even when it says it's in fastboot mode. bootloader is still locked and recovery mode freezes at google screen on the rare occasions when i can even select that option. tbh i think there's something wrong with my adb setup, but i followed the instructions on the android sdk site... kinda lost here sorry if this question is unclear. i also tried using the unlock option on wugfresh's nexus root toolkit but it keeps saying there is no fastboot device attached. any help would be much appreciated.
never mind, I'm just going to install a fresh motherboard.
Hi everyone !
I got a tricky situation there and I need some help. (I googled a lot before posting this.)
Few day ago I tried to root my Nexus 4 using Nexus Root Toolkit.
I'm going to explain step by step what happend :
1. My phone was on Android 4.3 stock rom and I unlocked it with NRT.
2. I did all updates from OTA to get Android 4.4.
3. Then I’ve made a HUGE MISTAKE because I've rooted my phone with the wrong modele selection in NRT. (Android 4.3 was still selected, but my phone was actually in Android 4.4).
4. While rooting, "everything was fine" exept that I’ve got a black screen just after the “Bootloader” and then nothing happend.
5. I’ve restarted my phone manually, by pressing the Power button 5 seconds. It worked, my phone actually booted but it was normal/not rooted.
Since that, ADB doesn’t work anymore on my phone.
ADB was fully functionnal before and I think I have soft-bricked something in my phone.
The problem is not my computer because :
- Yes, ADB is enabled on my phone and I tried unplug/plug USB many times. (doesn’t work)
- I've tried other USB port. (doesn’t work)
- I've tried drivers reinstallation on my computer, and restarting it many times. (doesn’t work)
- I've tried my phone on differents computers (doesn’t work)
Details :
- The “Stock ROM + Unroot” option on Nexus Root Toolkit worked (throught Bootloader mode) but ADB sill doesn’t work.
- I've tried to launch a custom recovery from Nexus Root Toolkit using Fastboot mode but I also get a black screen.
- In the stock recovery mode, the option “Apply update from adb” seems to work. (The drivers test of Nexus Root Toolkit pass, but I need to restart my phone manually to get to the Bootloader mode test.)
Any idea what I can try now ?
Lefjojo said:
Hi everyone !
I got a tricky situation there and I need some help. (I googled a lot before posting this.)
Few day ago I tried to root my Nexus 4 using Nexus Root Toolkit.
I'm going to explain step by step what happend :
1. My phone was on Android 4.3 stock rom and I unlocked it with NRT.
2. I did all updates from OTA to get Android 4.4.
3. Then I’ve made a HUGE MISTAKE because I've rooted my phone with the wrong modele selection in NRT. (Android 4.3 was still selected, but my phone was actually in Android 4.4).
4. While rooting, "everything was fine" exept that I’ve got a black screen just after the “Bootloader” and then nothing happend.
5. I’ve restarted my phone manually, by pressing the Power button 5 seconds. It worked, my phone actually booted but it was normal/not rooted.
Since that, ADB doesn’t work anymore on my phone.
ADB was fully functionnal before and I think I have soft-bricked something in my phone.
The problem is not my computer because :
- Yes, ADB is enabled on my phone and I tried unplug/plug USB many times. (doesn’t work)
- I've tried other USB port. (doesn’t work)
- I've tried drivers reinstallation on my computer, and restarting it many times. (doesn’t work)
- I've tried my phone on differents computers (doesn’t work)
Details :
- The “Stock ROM + Unroot” option on Nexus Root Toolkit worked (throught Bootloader mode) but ADB sill doesn’t work.
- I've tried to launch a custom recovery from Nexus Root Toolkit using Fastboot mode but I also get a black screen.
- In the stock recovery mode, the option “Apply update from adb” seems to work. (The drivers test of Nexus Root Toolkit pass, but I need to restart my phone manually to get to the Bootloader mode test.)
Any idea what I can try now ?
Click to expand...
Click to collapse
I foresee a total wipe in your future. First try uninstalling all the Android drivers in the Device Manager, turn off debugging on the phone, plug the phone in, and see what happens.
Sent with my Nexus® 10 minus 3
Berrydroidcafe said:
I foresee a total wipe in your future. First try uninstalling all the Android drivers in the Device Manager, turn off debugging on the phone, plug the phone in, and see what happens.
Sent with my Nexus® 10 minus 3
Click to expand...
Click to collapse
Hey ! Thanks for your repy
I tried what you told me, I uninstalled everything related to Android drivers on my computer in Device Manager and with USBDeview. I also uninstalled "Universal ADB Driver" and I restarted my computer.
I pluged my phone back in without USB Debugging and Windows reinstalled every drivers itself.
Everything worked fine, so I've installed "Universal ADB Driver" from NRT, and follow it instructions.
Then I've enabled USD Debugging, I unpluged and pluged back my phone and tried the drivers test.
But ADB still doesn't work...
Windows detect my phone, but my phone doesn't dectect my computer (it doesn't ask me if I want to accept this computer as it should do.).
yo,ve tried to reinstall NRT and to redownload the android sdk
uninstall NRT using iObit Uninstaller (it will totally delete any NRT file from HDD)
after uninstalling it wirh iObit Uninstaller shift delete on android sdk folder
restart
and now download the Android SDK 32bit (even if you have 64bit os download 32bit version is totaaly stable and compatible with the drivers)
open android SDK and install google driver
then install NRT
another thing to do is to change the usb port (allways to be an USB2 port and use the cable that camed with the phone
GOODLUCK
Try to get into fastboot power+volumes then go into toolkit on root and all should be fine
Gesendet von meinem Nexus 4 mit Tapatalk
I recently bought a refurbished 2012 Nexus 7 on 4.2. The only things that I have done on the phone are entering my Google account details and downloading a single app (papyrus). I then clicked to install the automatically downloaded software update (it downloaded 4.3), and after restarting the tablet was stuck on the Nexus X boot animation forever. Factory reset/cache wipes do not help.
I found drivers for the phone to be recognized while showing the X, and I found drivers for the phone to be recognized after selecting the a "apply update from ADB" option from stock recovery. However Windows does not recognize the phone at all in recovery mode before selecting that option. Nothing changes in the device manager when plugged/unplugged. Windows doesn't attempt to install anything. It's as if I unplugged the cord once it enters recovery from the bootloader. I assume USB debugging is off, because it would be at the default setting. I tried using the Flash Stock + Unroot option in the Nexus Root Toolkit with the Soft-Bricked/Bootloop setting in, but that fails in both normal recovery (with the device unnoticed) and sideload mode. I'm guessing that debugging needs to be on for this?
Does anyone have any suggestions for other things to try? I have no way of knowing what the original owner may or may not have done, and this was the first time that I restarted the device, so I have no way to know if the problem was caused by the OTA or not.
EDIT: It looks like I made the situation worse. I attempted running the Flash Stock + Unroot option from the bootloader. I am not sure what happened, but now the device starts at the Google page with green start in an arrow. I have the bootloader options, and start and recovery options give me a "booting failed" message in the top left and just stay on the google page. Restarting the bootloader gives me the normal bootloader android image and the options have the same effects.
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
wioneo said:
For anyone who runs into this problem, I seem to have at least temporarily solved it.
I followed the advice here to manually flash the factory image. I am now back to where I was when I bought the phone, and I will immediately enable debugging and test it's ability to restart, connect in recovery mode, etc now.
EDIT: It can restart normally (with the unlocked logo), but it is still completely unrecognized in recovery unless I choose the sideload option like before. Should I return the tablet?
Click to expand...
Click to collapse
still have a problem?
Wrong drivers, try other USB ports. Had that happen with another tablet. Only recognized in adb side load with galaxy nexus driver loading, possibly from universal adb drivers... Switched to a port on the other side and correct drivers finally worked.
Sent from my Le Pan TC1020 using Tapatalk
norwoodesteel said:
still have a problem?
Click to expand...
Click to collapse
As far as I know, no. I was never able to get the device is to be detected by my computer while in stock recovery mode, however it was detected after I flashed ClockworkMod Recovery. So I still have no idea what was causing that problem, but it is no longer relevant.