Edit : the problem is the usb cable itself.. Tried with HTC USB cable and its working flawlessly..!! Though it (original asus USB cable ) still works good for both charging, data sync and file transfers but not working for adb and fastboot..
Previously installed stock factory image (KTU84P) using fastboot (in boot loader)
then flashed twrp 2.7.1.1
rooted
rebooted and everything working fine.
to install a ROM through adb sideload
i formatted all partitions in recovery
started adb sideload but its in terminal adb is not detecting my device..
So i rebooted to boot loader (fastboot mode) to flash factory image but here fastboot not detecting my Nexus 7
is the problem with my nexus 7 or linux..??
i tried using windows but with no luck..
NOW My Nexus 7 doesnt have operating system dont know how to install one without using fastboot and adb sideload..
Did you try to use fastboot in Root privilege, I mean sudo in Linux?
Related
Guys..
I desperately need your support to turn my nexus back on .....
I used JROMFlasher tool and it erased all the data from my SD card.:crying:
I am stuck at google logo now..
I can boot to recovery.. But there is no ROM in my SD card.
I cannot mount USB from recovery..
I am on windows 8 and ADB is not working in my PC.
Is there any way to put ROM in to my nexus and make it work
http://bit.ly/14ddcGw
Fix your ADB before doing anything else
This is fairly easy to recover so you don't have to panic. You need to get ADB working first, or revert back to Windows 7.
Then install or boot directly into TWRP recovery using: fastboot boot twrp.img.
While in TWRP, choose the "ADB sideload" option. Then load and install the rom by typing: adb sideload rom.zip
Or you can also follow the instruction to factory reset your device: http://forum.xda-developers.com/showthread.php?t=1907796
Also Nexus devices can't mount USB storage while in recovery (as far as I know).
You can mount external usb storage via usb otg if you use twrp recovery.
If not, or you are on stock recovery, adb and fastboot will be necessary.
I got adb and fastboot to work on windows 8 64bit by strictly following the guide from wug's toolkit. Support for linux is better. The nexus 7 is recognized automatically by arch linux (just install android-tools from aur for adb and fastboot). Maybe ubuntu linux works just as easy to recover your nexus, which you can try through wubi.
Once I was at the same I was in Win8 too..
I don't remember exactly how but I was able to install ADB only using fast boot with the help of WugFress Nexus Root toolkit.... And successfully booted into the system....
You can also boot into temporary custom recovery using this toolkit....
You can get the toolkit from the link bellow....
http://goo.im/devs/WugFresh/NexusRootToolkit/NRT_v1.6.3.sfx.exe
Please press the thanks button if you like my work...
Have a good day...
Hello,
I was attempting to update from 4.3 SlimBean to 4.4 SlimKat Weekly.
I booted into CWM Recovery, wiped system, cache, dalvik cache etc, and went to flash the rom.
The rom must have been corrupt or something, as I was unable to and received an error.
I rebooted and was stuck in fastboot.
From here, I've tried both Wug's Nexus Root toolkit, and the Skip Root toolkit.
Running the return to stock and unroot whilst in fastboot in either of them caused a crash of fastboot.exe and the Skip Root equivalent.
After a reboot Wug's allowed me to atleast run the program, but I received link errors, so tried again. This time it couldn't find it, unplug, replug. Link errors, cant find it and this repeated.
Skip also allowed me to after reboot, but gave the exact same faults.
That's as far as I've really got. I occasionaly get it to run, and it seems to work only for it to get part way in, sometimes after sending the bootloader, or on the bootloader and it can not find any devices.
For some extra info, this is Running Windows 8.1, using a USB 3.0 Front panel header and tried using default cable, samsung and kindle ones too.
I'm looking for any ideas? Worst case scenario is I can try when I'm back home at the weekend and there I have a PC with XP that I have used previously to fix this style of boot error.
Cheers,
WiiManic
Stop using toolkits, issues love to pop up for those who do
Make sure bootloader is still unlocked
If not
fastboot oem unlock
Flash latest twrp or cwm or whatever, just download the image and open cmd in this location
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
Now boot to new recovery
Go to advanced
Adb sideload
On PC go to ROM of choice, maybe slimbean
adb sideload nameofrom.zip
When complete
adb sideload nameofgappsoranythingelseneeded.zip
Reboot
Sent from my Nexus 4 using XDA Premium 4 mobile app
I Softbricked my nexus 7 a while back its now in a bootloop. I am running Cyanogenmod 10.0 (I believe), Rooted and running ClockworkMod Recovery, and am NOT USB Debugging Enabled. Now attempting to reflash Nakasi JZO54K (4.1.2) to soft-bricked Nexus 7 via fastboot.
I'm trying to access my nexus 7 (2012) via adb command prompts will not recognize my android device - serials do not appear when "adb devices" is typed.
I am currently following Comminus's flashing guide. When I go to device manager in windows, the android device is named "grouper" rather than "android" as I have seen before.
I don't think the root toolkit will solve this because I don't think I can even send commands to the device at this point.
Please help someone...I really don't know where else to look for help about this.
adb commands don't work in fastboot. Only fastboot commands work in fastboot.
Download the factory image from Google, extract, and run the flash all batch script while your N7 is connected in fastboot mode.
I tried a clean install of a Lollipop ROM but the install either was corrupted because it boot loops into updating apps process. When in recovery, I cannot get ADB to see the device. When in bootloader, cannt get fastboot response. I tried my nexus 5 and can see it in ADB without problems.
Any thoughts?
What recovery are you using? Do you see your drivers for your N4 in device manager?
Hi,
I rooted my mojo and then i installed twrp, then i installed cyanogenmod 12 and i tryed to reboot but when i pressed reboot TWRP asked "Your device isnt rooted want to root? but i presed no accidentaly (one of the worst mistakes of my life) and it stucked on bootloop and i tryed to reboot it on recovery mode to fix it using fastboot but it stucks on rebooting... (on the screen of terminal on my laptop) and i waited for a long long time, but nothing happened.
Please help!
Did you use towelroot, or the USB-USB cable?
If towelroot, then you may not be able to recover the device without using a USB-USB cable. The fastboot prevents the MOJO from being bricked, because you can always re-flash it using the USB-USB method, even if the OS installed isn't working.
If you have a USB-USB cable, you need to use that to boot from TWRP again (or re-flash it to the fastboot if it won't work) and then re-wipe the MOJO and re-install CM12 + the Gapps, then re-boot the system as per the instructions. If you have any questions regarding clarification of the procedure, feel free to ask.
I used towelroot to root it and i tried fastboot to reboot it but on windows 10 don't detect it and on mac os X el capitan stucks on rebooting.....
The Windows driver should be in the same folder as fastboot. I was using Windows 7 and it didn't detect either, but the driver makes it detect correctly.
http://i.imgur.com/8O5FDgB.jpg
Windows 10 cant, but i will try with an windows 7 old (not so old) laptop
https://drive.google.com/file/d/0B3gWeKqMPK8HcjE2ZC1hOU0yUDA/view?usp=sharing
hi again, i tried with the windows 7 laptop but now fastboot dont detect it,i installed the drivers succesfully but fastboot dont detects it
https://drive.google.com/file/d/0B3gWeKqMPK8HajBUNlMyZEcxV1k/view?usp=sharing
SOLVED: the reason it didnt detected it its because on windows you needed to turn on testdriversigning and install the .inf file included on the MoDaCo mod zip on the windows.drivers and after that you needed to write "fastboot -i 0x0738 <command> , "0x0738" is the mojo´s usb vendor so it sended the commands directly to the mojo.
The problem was that the data and system partitions were corrupted so i reformated them with "fastboot -i 0x0738 erase system -w", the -w is for erase userdata. After that i booted the twrp recovery by "fastboot -i 0x738 boot <recovery.img path>" and from twrp i reinstalled android and it worked!