I had used the Nexus 7 Toolkit to unlock and root.
I then used the Toolkit to flash the factory image back.
Now I am trying to manually flash a build of grouper (Nexus 7)
fastboot -w flashall, fails with "protocol error".
Any advice?
Even if I'm trying to manually flash the factory image it fails. It seems only the Nexus 7 toolkit can use fastboot to flash this device, when I use fastboot from terminal it gives me protocol errors.
bump.
I've been stuck on this for awhile. If I trick the Nexus ToolKit into flashing my compiled image it works fine (from Windows).
If I try and flash it myself (from Linux) it gives me protocol error.
They are both using fastboot to get the job done.
Wrong cable. Was using a usb micro b1 cable. Changed to the cable which came with the Nexus 7, whatever USB Micro type it has it works without issue. Same USB port.
Related
So I am in a pickle. I am selling my Nexus 4 and I wanted to wipe it clean. Not thinking I wiped everything including system. I can't get sideload to work it keeps getting hung up when trying to reboot fastboot. If I manually reboot fastboot that throws off TWRP. I can't get ADB commands to work properly because I can't turn USB debugging on. Another issue is I have an odd radio installed. Looks like I have the .83 radio from a leak installed. So when I go to restore I get an error because my baseband radio doesn't match what the system image is looking for. Is it possible to somehow flash a radio via fastboot commands or ADB. I haven't had much luck with ADB commands. The only other thing I can think of is to try to find the leaked build that the .83 radio came from and factory restore that. I can still get into fastboot and I can still get into TWRP. This is exactly when having an SD card on a device is a lifesaver.
Download the nexus 4 jellybean factory image from Google and flash via fastboot
Sent from my Nexus 4 using Tapatalk
jdubau55 said:
So I am in a pickle. I am selling my Nexus 4 and I wanted to wipe it clean. Not thinking I wiped everything including system. I can't get sideload to work it keeps getting hung up when trying to reboot fastboot. If I manually reboot fastboot that throws off TWRP. I can't get ADB commands to work properly because I can't turn USB debugging on. Another issue is I have an odd radio installed. Looks like I have the .83 radio from a leak installed. So when I go to restore I get an error because my baseband radio doesn't match what the system image is looking for. Is it possible to somehow flash a radio via fastboot commands or ADB. I haven't had much luck with ADB commands. The only other thing I can think of is to try to find the leaked build that the .83 radio came from and factory restore that. I can still get into fastboot and I can still get into TWRP. This is exactly when having an SD card on a device is a lifesaver.
Click to expand...
Click to collapse
"This is exactly when having an SD card on a device is a lifesaver", what about your eMMC be locked now, if so neither sdcard will help you(some people had issues with eMMC in nexus 4);
but anyways download factory images and run the .bat while in fastboot mode, or use download mode and redo all partitions by yourself.
Thanks all. I used a different toolkit and did as you said. Downloaded the latest factory image and fastboot flashed it via the toolkit I had.
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.
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?
Seems I've just bricked my Nexus 7 3G. What I did:
1. After retiring my old Nexus 7 3G from car service (upgraded to Nexus 7 2013) I decided to make the system more mainstream.
2. First I decided to upgrade the TWRP to be able to flash some of the 7.1.2 ROMS. From that moment no version of TWRP I've flashed ever booted. The system booted normally, just no access to recovery. No idea why but this is not very important at the moment.
3. So I decided to go stock for the start. I downloaded factory image LMY47V and started flash_all.bat.
It went like this:
fastboot oem unlock - OK
fastboot erase boot - OK
fastboot erase cache - OK
fastboot erase recovery - OK
fastboot erase system - OK
fastboot erase userdata - OK
fastboot flash bootloader bootloader-tilapia-4.23.img - OK
fastboot reboot-bootloader - OK
ping -n 10 127.0.0.1 >nul
fastboot flash radio radio-tilapia-1231_0.18.0_0409.img - OK
fastboot reboot-bootloader - OK
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasig-lmy47v.zip - failed while flashing system (I didn't remember the error)
4. From that moment my tablet behaves like that:
- attempts to get to bootloader (all possible button-press combinations) all end up with Google logo displayed forever
- long press of power button in this state results in restart (not power-off) - again to Google logo
- I can power off by simultaneously pressing all 3 buttons
- obviously, there is no way to connect by adb or fastboot
5. So, it seems like the bootloader is gone/inaccessable. Strange - it was indeed flashed in the unsuccessful re-stock attempt.
Is there any chance to unbrick?
Here is why I gave up googling and am asking here. There seem to be 3 categories of "bricked" Nexus 7, none of which fully fits my case:
1. Unbootable system but still accessible bootloader. Usually possible to access the device via fastboot and flash recovery. Not my case.
2. Device with positively deleted or corrupt bootloader. May be my case. But flash_all.bat seemed to successfuly flash the bootloader image.
3. Nexus randomly stuck in Goole logo, which may be "repaired" by physical force or mainboard replacement. Hardware fault. May be my case, but I know I screwed it up by my flashing attempts.
There are guides for unbricking with nVidia nvflash. But the assumption is the device is visible on computer's USB. Not my case.
Ok, now I see here on xda exactly the same situation reported here https://forum.xda-developers.com/nexus-7/help/n7-tilapia-stuck-logo-fastboot-access-t3990043. Sorry, I overlooked it. Still, in that thread there is no solution.
One difference is that the OP can see his tablet on OFF state as Uknown device in Windows, I might have overlooked this symptom in mine. It would be much more hopeful situation, at least for nvflash solution.
nalott said:
Ok, now I see here on xda exactly the same situation reported here https://forum.xda-developers.com/nexus-7/help/n7-tilapia-stuck-logo-fastboot-access-t3990043. Sorry, I overlooked it. Still, in that thread there is no solution.
One difference is that the OP can see his tablet on OFF state as Uknown device in Windows, I might have overlooked this symptom in mine. It would be much more hopeful situation, at least for nvflash solution.
Click to expand...
Click to collapse
Did you try reinstalling the drivers after removing all other drivers? If the attempt is successful and the tab is recognised, try the Wugfresh Toolkit. The toolkit itself has proper drivers and instructions to install the drivers.
Also try another cable, another USB port (2.0 not 3.0), another PC/Laptop.
Hope you succeed.
Thanks for help. I will try. But I have very little hope: I was using the particular setup (PC, cable, connector, drivers) and it worked fine until the crashed factory image flash. I'm still using it with my Nexus 7 2013 without problem.