So today my Nexus 7 got bricked by my little child. Somehow my child managed to get to TWRP going to recovery and deleted everything!!!!!. He somehow deleted the backups and the bootloader/baseband versions. My Nexus 7 was running an old version of Paranoind android and it was on 4.23 i believe. Since I now have a new Computer and my recovery/backup files have been erased from my old one I cannot fix my tablet. I currently use Nexus Root Toolkit v1.8.1 by Wug's masterpiece and it freezes when I tried to flash stock and unroot my tablet using the soft- brick/bootloader method.
My tablet is stuck at the bootloader and I have no idea how to fix it. it seems like it cannot get the baseband version according from the bootloader version on the tablet screen since it says n/a.
Here is some information from that says on the tablets screen " when i press start on the bootloader screen on the top left it says " Booting failed" and on the screen it shows google and the unlocked sign.
Does anyone know how to fix this?
edit: I somehow was able to get the bootloader version from the method i tried above. It says 4.23 but it still froze. The baseband version is still n/a tho :\
and it's the Nexus 7 16 GB wifi tablet
Edit 2: when i try to flash stock it says
sending 'bootloader' (3911 KB)...
FAILED (data transfer failure (Too many links))
finished. total time: 8.440s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.636s
archive does not dcontain 'boot.sig'
error: out of memory
Click to expand...
Click to collapse
WiFi tablets don't have a baseband version that only applies to mobile networks. Try this
http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from one of my 47 iPads running android C3P0
Related
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help
rohanjoshi said:
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help
Click to expand...
Click to collapse
Hi, rohanjoshi...
You're actually on the wrong forum... this is the forum for the first generation Nexus 7 (2012). The forum for your second generation Nexus 7 (2013) is located here...
http://forum.xda-developers.com/nexus-7-2013
--------------------------------
However, looking through your output, it seems the failure to flash is due to the bootloader being locked...
rohanjoshi said:
...
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
...
Click to expand...
Click to collapse
You need to unlock it with...
Code:
fastboot oem unlock
....or whatever the equivalent is in the toolkit you're using.
Good luck.
Rgrds,
Ged.
GedBlake said:
Hi, rohanjoshi...
You're actually on the wrong forum... this is the forum for the first generation Nexus 7 (2012). The forum for your second generation Nexus 7 (2013) is located here...
http://forum.xda-developers.com/nexus-7-2013
--------------------------------
However, looking through your output, it seems the failure to flash is due to the bootloader being locked...
You need to unlock it with...
Code:
fastboot oem unlock
....or whatever the equivalent is in the toolkit you're using.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
woops, I'll get on that!
My Nexus 7 16GB 2012 has started to randomly reboot, it's running 4.4.2 and has been fine for months. This morning I switched it in, turned off the Airplane Mode and after 30 seconds or so it locked up, then reset. This happens every time I turn off Airplane Mode and switch on WiFi.
I'm wondering if there is some sort of corrupt RAM causing the issue? I've tried to do a Factory Reset, but this also fails and I end up back at square one. So I tried Nexus Root Tookit to go back to stock (all I've done previously is unlock the bootloader, no root). This also fails:
sending 'bootloader' (3911 KB)...
OKAY [ 0.516s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.745s
Any suggestions on what to try next?
This may of course be a hardware fault, the device was bought in Summer 2012 on release.
Hi, you need download image of 4.4 and flash it, because 4.4.2 image has corrupt bootloader. If not work try 4.2.2 image and update to kitkat OTA
Cheers, E11
estape11 said:
Hi, you need download image of 4.4 and flash it, because 4.4.2 image has corrupt bootloader. If not work try 4.2.2 image and update to kitkat OTA
Cheers, E11
Click to expand...
Click to collapse
Thanks for the tip, I'll give that a try.
I have been able to use the Nexus Toolkit to temporarily flash the TWRP. I test my hypothesis about an invalid file system and that fails:
/data/media/0/TWRP errno=30
Anyway, it's downloading the image now so lets see if that fixes the problem.
nigelw said:
Thanks for the tip, I'll give that a try.
I have been able to use the Nexus Toolkit to temporarily flash the TWRP. I test my hypothesis about an invalid file system and that fails:
/data/media/0/TWRP errno=30
Anyway, it's downloading the image now so lets see if that fixes the problem.
Click to expand...
Click to collapse
I'm trying KRT16S and the "Back to Stock" option. The Nexus goes to bootloader mode (so I have Android on back with open door). The flashstock.bat runs in a command tool and displays no errors, but nothing appears on the Nexus 7? The script completes, Nexus reboots and is in exactly the same state.
It doesn't seem to want to accept any kind of update.
nigelw said:
I'm trying KRT16S and the "Back to Stock" option. The Nexus goes to bootloader mode (so I have Android on back with open door). The flashstock.bat runs in a command tool and displays no errors, but nothing appears on the Nexus 7? The script completes, Nexus reboots and is in exactly the same state.
It doesn't seem to want to accept any kind of update.
Click to expand...
Click to collapse
Mmm try enter in recovery and do factory reset, if doesnt work, try image of 4.2.2 I'm sure that works
PD. And use Nexus toolkit
Enviado desde mi Xperia P mediante Tapatalk
lagoskon said:
Give a try with twrp 2.6.3.0.
Latest has issues with backups
Στάλθηκε από το Nexus 7 μου χρησιμοποιώντας Tapatalk 2
Click to expand...
Click to collapse
From TWRP I'm able to Wipe and do Factory Reset. It says successful, but when I restart nothing has changed, still got 4.4.2 installed.
I also tried Back to stock with 4.2.2 JDQ39, device goes to Bootloader mode but fails with this error:
sending 'bootloader' (2096 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: ()
finished. total time: 0.873s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.637s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (No such device or address))
finished. total time: 0.000s
Hey there,
I tried to upgrade my Nexus 7 grouper using the 4.23 bootloader and some of the stock roms, cyanogenmod and miui as well as slimkat roms, it kinda didnt work out the way I wanted it to, now I am stuck on: sending 'bootloader' (2100 KB) while not having any recovery nor anything else on my nexus...
the bootloader seems broken, because it always doesnt response when I try to flash an img file..
Thankful for any help
Can you get into fastboot mode?
Did you get the bootloader-grouper-4.23.img file from one of the factory images here?
What is the md5?
I've been reading that these factory image bootloaders (JWR66Y & KOT49H) do not work.
Check out these threads:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?p=45043044#post45043044
It seems like I used the bootloader from nakasi-kot49h-factory-5e9db5e1
it has got the md5 hash 797a8ddfe19bfe4c485f8a8c119f1bdd
I tried to flash the 4.23 bootloader from the second link, which is the JWR66V version, but still cannot flash it, because by device freezes and the "Flashing bootloader-grouper-4.23.img" of Nexus Root Toolkit doesnt do anything than being stuck.
edit:
Ok , I managed to get my recovery back via fastboot.exe via "fastboot flash recovery recoveryname.img"
I managed to flash normal custom roms via fastboot and adb sideload, but I cannot change the bootloader from the bricked 4.23 one to the one mentioned in the topics which should be a working one from the nexus 7 JWR66V build.
I always get the error
Code:
sending 'bootloader' (2100 KB).
OKAY [ 0.333s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
Any ideas?
The Unified Android Toolkit seems to overwrite the broken bootloader easily and after a few attempts of trying to write the factory image with the Unified Android Toolkit and trying out different usb slots, because I often got the error "Unknown Device" and thus Windows 7 could not install any drivers, it worked out.
Thanks
Hi, I had a nexus 7 with rooted stock firmware and modified kernel and I wanted to return to stock firmware. Usually I use Nexus Root Toolkit without problem for this type of things but, after I've flashed for the first time the factory image nakasi 4.4.4 (KTU84P), now my nexus crashes on the black screen with the Google's logo. I've tried to reflash other stock firmwares but nothing is changed; flashing through fastboot the operation crashes during the sending of system.img. Could anyone help me? Maybe the nexus must be repartitioned?
PS: sorry for my bad EnglishXP
marsece said:
Hi, I had a nexus 7 with rooted stock firmware and modified kernel and I wanted to return to stock firmware. Usually I use Nexus Root Toolkit without problem for this type of things but, after I've flashed for the first time the factory image nakasi 4.4.4 (KTU84P), now my nexus crashes on the black screen with the Google's logo. I've tried to reflash other stock firmwares but nothing is changed; flashing through fastboot the operation crashes during the sending of system.img. Could anyone help me? Maybe the nexus must be repartitioned?
PS: sorry for my bad EnglishXP
Click to expand...
Click to collapse
Have you tried using a different usb port on your pc?
I've tried to use another pc and the situation is the same. Furthermore, trying to flash in different way the stock firmwares, now I can't flash any partitions from a stock image...maybe has my nexus a hardware fault?
Also I've read this http://forum.xda-developers.com/showthread.php?t=2573015 and followed its instructions, but without results.
For example, if I try to flash a bootloader this is the situation
C:\Program Files (x86)\WugFresh Development\data>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.568s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.710s
and on the nexus 7 appears "signature mismatch".
and the cases of other partitions of a stock firmware are similar
marsece said:
For example, if I try to flash a bootloader this is the situation
C:\Program Files (x86)\WugFresh Development\data>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.568s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.710s
and on the nexus 7 appears "signature mismatch".
and the cases of other partitions of a stock firmware are similar
Click to expand...
Click to collapse
Hello,
did you have another usb cable by chance?
I had an issue once with one of mine that also prevented to use adb.
Just an idea,
Nix
Nixblicker said:
Hello,
did you have another usb cable by chance?
I had an issue once with one of mine that also prevented to use adb.
Just an idea,
Nix
Click to expand...
Click to collapse
I've used the original nexus cable without problem until now, so I didn't think to try another cable. Thank you very much for the advice, now my nexus is returned to work!
Nexus 7 (grouper) doesn't boot - Bootloader says "FAILED (remote: (FileWriteFailed))"
Hi,
My Nexus 7 (grouper) won't boot Android anymore. It automatically boots into the bootloader and when I select 'Start' or 'Recovery Mode' it just says "Booting failed".
When I try to flash a new recovery Image over fastboot I get the following Output:
[[email protected] Downloads]$ sudo fastboot flash recovery twrp-2.8.7.0-grouper.img
sending 'recovery' (11850 KB)...
OKAY [ 1.409s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 1.441s
Click to expand...
Click to collapse
It's the same, when I try to flash anything else. So I have no chance to flash a Stock-Image. I also get the same error when I try to format a partition. I'm pretty much out of ideas now. Can anybdoy help me?
yeah this same thing kept happening to me (I have no idea why) Once you get into the bootloader make sure your device shows up IE fastboot devices, then flash bootloader, then fastboot reboot-bootloader then between each succeding flash use the volume buttons to select reboot bootloader on the device. I had to flash individual partitions it would'nt do a -w update, so flash system, then reboot bootloader on device, then flash, then reboot bootloader, ect
Also booting into Android takes a bit so be patient, like 10/15 min. Maybe there's an easier way but after screwng around with it for an hour this is the only way I could get 5.1.1 on it.
productofusa said:
yeah this same thing kept happening to me (I have no idea why) Once you get into the bootloader make sure your device shows up IE fastboot devices, then flash bootloader, then fastboot reboot-bootloader then between each succeding flash use the volume buttons to select reboot bootloader on the device. I had to flash individual partitions it would'nt do a -w update, so flash system, then reboot bootloader on device, then flash, then reboot bootloader, ect
Also booting into Android takes a bit so be patient, like 10/15 min. Maybe there's an easier way but after screwng around with it for an hour this is the only way I could get 5.1.1 on it.
Click to expand...
Click to collapse
When I try to flash the bootloader I get:
[[email protected] Downloads]$ sudo fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.403s
Click to expand...
Click to collapse
And when flashing other partitions it says "FAILED (remote: (FileWriteFailed))".
Something seems to be really screwed up with my storage. Is there a way to repartition the device from fastboot? Maybe that would be help.
I'm willing to try out everything, by now.
Is it possible the files your trying to flash are somehow corrupt? try downloading again. My problem was fastboot kept crashing, not really sure what you got going on.
I will say that i've just finished flashing nexus 6,7,7, and 9 and for some reason the nexus 7 (2012) was a real pain in the butt, didn't have issues with any of the others.
Maybe someone else with another idea will chime in, good luck!
productofusa said:
Is it possible the files your trying to flash are somehow corrupt? try downloading again. My problem was fastboot kept crashing, not really sure what you got going on.
I will say that i've just finished flashing nexus 6,7,7, and 9 and for some reason the nexus 7 (2012) was a real pain in the butt, didn't have issues with any of the others.
Maybe someone else with another idea will chime in, good luck!
Click to expand...
Click to collapse
I already downloaded them multiple times. And even if they are corrupt, formatting the partitions should still work. I'm guessing on corrupt storage now, as I can't find any other explanation. Maybe I can find a cheap Motherboard somewhere on the internet. Thanks, anyways