Related
So, I just picked up my new Nexus 7, dinked around a bit with it, then wanted to unlock and root it for alternative rom support. I went about doing everything, except when I went to begin the root, which looked like it was going smoothly, I realized that I did not enable USB Debugging.
I am not able to put it back to stock, nor am I able to load anything to it. I can get into FastBoot but thats it.
Any help would be appreciated. I have searched, but I could not find anything on enabling USB debugging remotely from a Mac. I am on Mac OS.
You're fine. Just search how to setup fastboot on a Mac. (Couldn't tell you, though I'm sure its close to you'd do it on Linux, and you'll need to find the Mac fastboot binary and new system.IMG(possibly a whole reflash)), then just do these commands-
fastboot oem unlock (if you've already done this skip this step)
fastboot flash system system.img
(If this doesn't work, find the entire flash all package and do)-
./flash-all.sh
(Will be something like this, you'll have to research yourself.)
Your best bet might be to use fastboot to flash the stock recovery back on the device and then use adb sideload from recovery to flash a stock system image. That would take you completely back to stock and then you could start over.
Sent from my Galaxy Nexus using Tapatalk 4
Sorry, I should have been more specific. All of the steps listed for the all of the guides require me to eventually put my tablet into USB Debugging mode. I can't do that. I can't boot into the Android system at all. I get the lovely dead robot with read warning symbol.
Is there any way to enable USB Debugging without system access on the tablet? Is this just a paper weight now? I have rooted and such since my original Nook Color, so I am not dunce. I just don't understand how I can do any of the guides if all of them call for me to put the tablet into USB debugging mode.
You only need debugging enabled to use ADB (in recovery or the OS). Fastboot will still work regardless.
NexusChrist said:
Sorry, I should have been more specific. All of the steps listed for the all of the guides require me to eventually put my tablet into USB Debugging mode. I can't do that. I can't boot into the Android system at all. I get the lovely dead robot with read warning symbol.
Is there any way to enable USB Debugging without system access on the tablet? Is this just a paper weight now? I have rooted and such since my original Nook Color, so I am not dunce. I just don't understand how I can do any of the guides if all of them call for me to put the tablet into USB debugging mode.
Click to expand...
Click to collapse
Ddi11igaf told you wat to do.
Download the full image and reset it to stock. Start again.
You are never bricked if you can get to fastboot.
:good:
Perhaps this will help:
There is currently, for some reason, no OS installed on the tablet. I do not have any roms or a backups saved on the tablet. I just want to go back to stock and start over.
I can't get into the tablet to enable USB debugging.
Is there a way to get a rom onto the tablet without USB debugging? I realize that Fast Boot works, and so does my recovery, but there is no OS installed, and no way for me to put an OS on it if I don't have USB debugging.
We understand, but you're under the false impression that USB debugging needs to be enabled to use fastboot and flash from there. It doesn't. All you have to do is unlock the bootloader (if you didn't do that already) and flash a stock ROM from https://developers.google.com/android/nexus/images. Download the stock ROM to your Mac and use the fastboot commands someone posted above. If it's not working, it's a driver issue with your Mac.
tweaked said:
Ddi11igaf told you wat to do.
Download the full image and reset it to stock. Start again.
You are never bricked if you can get to fastboot.
:good:
Click to expand...
Click to collapse
And how would one go about putting that image on the unit to flash it?
This is what I get when I try to use the one-click method from AndroidRootz:
***************************************************************
This script will: Unroot The New Nexus 7 to Stock 4.3 & Lock your Bootloader
For more details go to AndroidRootz
***************************************************************
Warning! This will delete everything on your device! BACKUP your device!
First make sure your in FASTBOOT MODE!
Press enter to continue
sending 'bootloader' (3911 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: 07974778
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (6880 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (7424 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (603495 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Your device is now stock and unrooted
However the bootloader is still unlocked
Let your device boot up, set up your device or skip the set-up
Place your phone in USB debugging mode
Settings > Developer Options > USB Debugging, If you don't have that option
Use this guide:
Connect USB cable if your disconnected
Press enter to relock the bootloader
If I hit enter after that it simply says device not found. Again, it's asking me to put it into USB debugging, but I can't because it failed to put the OS on the device.
Looks like it was working fine, until it went to write the OS (system). Perhaps the system.img is missing or corrupt. Try downloading it direct from the link I posted above and flashing with that.
NHLWil said:
Looks like it was working fine, until it went to write the OS (system). Perhaps the system.img is missing or corrupt. Try downloading it direct from the link I posted above and flashing with that.
Click to expand...
Click to collapse
Thanks, I have it downloaded. And installed ADB and FastBoot on my Mac.
Do you have the specific steps on how to flash a rom from my computer via fastboot?
You should just be able to:
fastboot flash system system.img
If it's not working, then you'll probably need the fastboot executable from the official Android SDK for Mac, as I know someone from work had an issue flashing with one they got from elsewhere.
NHLWil said:
You should just be able to:
fastboot flash system system.img
If it's not working, then you'll probably need the fastboot executable from the official Android SDK for Mac, as I know someone from work had an issue flashing with one they got from elsewhere.
Click to expand...
Click to collapse
I was able to download it, and it sees my device, and I can perform most of the operations, however; As soon as I try to do a flash all this is what I get:
"OTT1-COMM-CK-MBP15-2400:android xxxxxx$ ./fastboot flashall flash-all.sh
error: neither -p product specified nor ANDROID_PRODUCT_OUT set"
So here is what I did, and all went well again until the System part: Run fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-jss15q.zip
And this was the output:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: 07974778
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (6880 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (7424 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (603355 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
I just did the same steps on my wife's PC and it worked perfectly.
Maybe something weird with the PC, I'm not sure. But all is well.
Thanks for the help!
NexusChrist said:
So here is what I did, and all went well again until the System part: Run fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-jss15q.zip
And this was the output:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: 07974778
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (6880 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (7424 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (603355 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Click to expand...
Click to collapse
Boot into recovery using Power+VolDown
Then redo your above steps, but skip the erase lines at the beginning.
See if that helps.
NexusChrist said:
So here is what I did, and all went well again until the System part: Run fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-flo-flo-03.14.img
fastboot reboot-bootloader
fastboot -w update image-razor-jss15q.zip
And this was the output:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.14
Baseband Version.....: none
Serial Number........: 07974778
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
sending 'boot' (6880 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (7424 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (603355 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
Click to expand...
Click to collapse
Pretty sure this error was your fastboot binary. You need the one from the SDK for a mac(I guess possibly a problem with your USB port, doubt it though since fastboot was talking to your device)
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 2.526s]
finished. total time: 2.526s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.200s]
finished. total time: 0.200s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.015s]
finished. total time: 0.015s
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
< waiting for device >
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
brad3626 said:
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Click to expand...
Click to collapse
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
adomol said:
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
Click to expand...
Click to collapse
Thank you for the help, unfortunately, it did not work.
I followed the instructions above, but the Nexus displayed "neither up nor cac partitions found" over and over
While cmd displayed:
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.213s
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.205s
Erovia said:
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
Click to expand...
Click to collapse
Wi-Fi
I have tried every one that the NRT offered.
Just read this guide and download the latest factory image from here.
Good luck.
Erovia said:
Just read this guide and download the latest factory image from here.
Good luck.
Click to expand...
Click to collapse
I read that guide.
But that guide seems to be written with the assumption that the device can boot into the OS
No ADB device is found because I can only boot into bootloader.
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Erovia said:
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Click to expand...
Click to collapse
Following from "Extract the Factory Image" part, this is what I am getting:
C:\Users\Brad>cd \Users\brad\AppData\Local\Android\android-sdk\platform-tools
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
XXX fastboot
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootlo
ader
error: device not found
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlo
ck
...
FAILED (command write failed (Unknown error))
finished. total time: 0.590s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase bo
ot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase ca
che
erasing 'cache'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase re
covery
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.022s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase sy
stem
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase us
erdata
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.018s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bo
otloader bootloader-grouper-4.23.img
error: cannot load 'bootloader-grouper-4.23.img': Invalid argument
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Erovia said:
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Click to expand...
Click to collapse
lock state - unlocked
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Erovia said:
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Click to expand...
Click to collapse
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Erovia said:
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Click to expand...
Click to collapse
I restarted, ran cmd as admin and tried every USB port and got this as the result each time:
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: XXX
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4992 KB)...
OKAY [ 5.460s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 8.518s
The Nexus was frozen at this point and had to be manually forced to restart bootloader.
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Erovia said:
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Click to expand...
Click to collapse
Thanks for your help
I bought it 13 months ago (perfect timing, coincidentally, right?), so if I could find the receipt I would still be screwed.
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Erovia said:
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Click to expand...
Click to collapse
fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [ 36.032s]
finished. total time: 36.032s
But then the N7 freezes and after manually restarting in bootloader it is still unlocked.
Then send is as it is. You can't do any more about it.
Good luck.
Hey all,
A little background: I was a little late to the Lollipop scene, and seeing as my phone wasn't getting an update anytime soon, I thought I'd crack out my ol' Nexus 7 2012 Wifi-edition. This thing was running an old version of Paranoid Android and was pretty slow and unreliable, I'd assumed I'd flashed a bad kernel or made some bad configurations or something. I very promptly downloaded the Lollipop factory image, fired up fastboot and wiped the device and attempted to flash the image.
It didn't work. I then assumed the image was bad, so I figured, as I had done in the past for KitKat, I'd download an older image and just accept the OTA. Once again the image refused to flash. It got stuck at the bootloader every time, but stubborn as I am, I tried yet an older image. flashing different versions of Jellybean, I discovered that my Nexus 7 wouldn't take any bootloader version higher than 4.18, and that if the bootloader did flash, the system.img would fail.
The procedure for flashing went as follows:
Download and extract nakasi gzipped tar images
cd into the folder containing an image
Run ./flash-all.sh, manually erase partitions and flash the zip, or extract the zip archive and manually erase partitions and flash the contained images
I noticed that the script wasn't working at all, so I took to manually flashing each image myself, and discovered that the issue usually occured with system.img and bootloader-group-x.xx.img
Looking for a solution to my problem. I'm running out of images to flash, and I have no way of transferring files to the tablet. I tried loading CWM so I could flash an unofficial image to get the thing booting, but I received errors when I tried to mount the USB storage.
Any and all help would be appreciated, I'm thinking this is a flash memory issue (i.e. one or more partitions is corrupt or formatted incorrectly), and I don't have the slightest clue how to fix it. Thanks!
EDIT: Errors and the actual process output are probably relevant.
Note that I run an Arch Linux box, but also tried the equivalent procedure using my other Windows 8.1 machine, to no avail.
Using the 4.3 jwr66y image as an example, this was the full manual process:
Code:
nakasi-jwr66y $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.978s]
finished. total time: 0.978s
nakasi-jwr66y $ fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.787s]
finished. total time: 0.787s
nakasi-jwr66y $ fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.526s]
finished. total time: 2.526s
nakasi-jwr66y $ fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.027s]
finished. total time: 0.027s
nakasi-jwr66y $ fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.423s
Using the 4.1.2 image as an example, this was the full manual process:
Code:
nakasi-jzo54k $ fastboot erase boot
erasing 'boot'...
OKAY [ 1.125s]
finished. total time: 1.125s
nakasi-jzo54k $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.633s]
finished. total time: 0.633s
nakasi-jzo54k $ fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.601s]
finished. total time: 0.601s
nakasi-jzo54k $ fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.526s]
finished. total time: 2.526s
nakasi-jzo54k $ fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.027s]
finished. total time: 0.027s
nakasi-jzo54k $ fastboot flash bootloader bootloader-grouper-3.41.img
sending 'bootloader' (2092 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 9.212s]
finished. total time: 9.498s
nakasi-jzo54k $ fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.808s
nakasi-jzo54k $ fastboot flash boot boot.img
sending 'boot' (4896 KB)...
OKAY [ 0.643s]
writing 'boot'...
OKAY [ 1.967s]
finished. total time: 2.610s
nakasi-jzo54k $ fastboot flash recovery recovery.img
sending 'recovery' (5240 KB)...
OKAY [ 0.699s]
writing 'recovery'...
OKAY [ 1.120s]
finished. total time: 1.819s
nakasi-jzo54k $ fastboot flash system system.img
erasing 'system'...
OKAY [ 2.608s]
sending 'system' (446268 KB)...
OKAY [ 58.787s]
writing 'system'...
FAILED (remote: (Unknown error code))
finished. total time: 63.412s
Flashing the 4.1.2 image produced another strange error where the tablet would continually output (in a loop) the phrase "Neither USP nor CAC partitions found" after the flash failed.
EDIT: I managed to successfully flash bootloader 4.23 from the KRT16S factory image, but I still can't get the system.img from any KitKat or Lollipop factory image to flash. I keep getting "FileWriteFailed" error messages. Anyone know how I can fix this?
Bumping because I'd like to fix my tablet at some point :$
Narwhal73 said:
Bumping because I'd like to fix my tablet at some point :$
Click to expand...
Click to collapse
I'm on the same situation as you, but mine initially started after trying to install an f2fs lollipop ROM. I also think it's because of some sort of partition screwup.
My tablet won't let me install a bootloader, always saying invalid state. Luckily mine seems to still work on 4.23.
It let's me install the boot and recovery images every time,but it always fails at the system image.
What also happens when trying to flash the system image is that it will sit saying sending image for ages. Then eventually it fails with the errors of either too many links or unknown error.
Only once has it actually sent the image using jwr66v and got the tablet booting again, but it wouldn't update and kept giving errors, so I'm trying again to see if I can manually update to latest.
I was told to try using Linux instead of windows, which I'll attempt this weekend. I'll let you know if it works, but am not too optimistic.
Sent from my LG-D802 using XDA Premium HD app
Got mine to work again, by just trying once again the terminal fastboot erase of all the partitions and then flash bootloader, reboot bootloader, then flash recovery, flash boot, flash system and finally flash userdata.
This is the same thing that wasn't working earlier but took on first try again after a break. So unfortunately I can't say I fixed it in a specific way, it just seems to be a case of persistence paid off.
Flashed the latest Google lollipop image.
Try to do the manual erase and flash again. Maybe it will take eventually like mine did.
Hope you come right.
Sent from my LG-D802 using XDA Premium HD app
I had issues flashing factory images to my N7 yesterday too. At first I did the flash all script. It hung just like yours did at flashing the system image. I did it again with trying to flash everything manually and it still wouldn't work. Finally, I rebooted into fastboot and opened a new terminal window and everything worked as it should.
Persistence doesn't work as a solution for me. Trying with multiple machines, many different terminal instances, and several attempts with each has lead to no results. I'm thinking that for some reason the partition scheme might be broken, though of course it could be something else . Anyone know how I can go about diagnosing the issue properly, or repartitioning this thing? I don't even care about the Google images anymore, as long as I can get a functional OS back on it.
Currently the Nexus 7 is sitting with bootloader version 4.18, and no other functional images flashed to it. I can't seem to get the official bootloader version 4.23
to flash.
(Sorry for letting the thread die, I was away on vacation)
Narwhal73 said:
Persistence doesn't work as a solution for me. Trying with multiple machines, many different terminal instances, and several attempts with each has lead to no results. I'm thinking that for some reason the partition scheme might be broken, though of course it could be something else . Anyone know how I can go about diagnosing the issue properly, or repartitioning this thing? I don't even care about the Google images anymore, as long as I can get a functional OS back on it.
Currently the Nexus 7 is sitting with bootloader version 4.18, and no other functional images flashed to it. I can't seem to get the official bootloader version 4.23
to flash.
(Sorry for letting the thread die, I was away on vacation)
Click to expand...
Click to collapse
Check the md5sum of your "Official" 4.23 bootloader if it isn't THIS:
df53028033c9eccf4fe5ba7bc198ce24
Then it is Wrong...
http://forum.xda-developers.com/showthread.php?t=2573015
http://forum.xda-developers.com/nexus-7/general/guide-nexus-7-2012-factory-image-root-t2937833
Those two post will explain in further details.
Let me know if you are still having issues. As long as your device is detected by ADB and fastboot it should be fairly easy to recover...
Also, are you still trying to do F2FS or Custom Kernels at this point OR just get back to Working Stock ??
sponix2ipfw said:
Check the md5sum of your "Official" 4.23 bootloader if it isn't THIS:
df53028033c9eccf4fe5ba7bc198ce24
Then it is Wrong...
http://forum.xda-developers.com/showthread.php?t=2573015
http://forum.xda-developers.com/nexus-7/general/guide-nexus-7-2012-factory-image-root-t2937833
Those two post will explain in further details.
Let me know if you are still having issues. As long as your device is detected by ADB and fastboot it should be fairly easy to recover...
Also, are you still trying to do F2FS or Custom Kernels at this point OR just get back to Working Stock ??
Click to expand...
Click to collapse
I'm not sure what F2FS is, so I'm pretty sure I wasn't trying to do that. I'm just trying to get an actual bootable OS back onto the tablet. Stock Lollipop is preferable to anything else right now and I'll worry about customising it again at a later date...
I was unaware that Google/ASUS fudged up the bootloader images for the last few major releases (that would explain my inability to flash 4.23 to the device), so I'll try the instructions in the threads you've pointed me to when I get a chance. Thanks!
I'll report back with any successes or failures at some point next week; I have exams to study for in the meantime...
Hi dude, you can Try to install Firmware stock 4.2.2 and after upgrade it using ota. My friend resolved same problem in this way.
Inviato dal mio Nexus 7 utilizzando Tapatalk
Okay, so I found time to try to fix this thing tonight. The bootloader from KRT16S flashed fine, so my N7 is once again running bootloader version 4.23. The issue with flashing the system.img persists however.
The error I get is:
Code:
writing 'system'...
FAILED (remote: (FileWriteFailed))
finished. total time: 93.175s
What is so frustrating about this is that a "write failed" error message isn't very descriptive. A write could fail for any number of reasons. Is there a way I can enable more verbose error output in fastboot?
The only thing that I can think of pinning this on is an improperly sized partition. Unless there is something someone else can think of, could someone point me to where I can get the stock partition layout, and how I can repartition the device?
EDIT: not sure of the relevance, but I have just noticed that as soon as fastboot begins sending the image for writing, the bootloader on the device freezes up. Like I can't scroll through the options, not see any live text on the screen. Same goes for userdata.img.
EDIT: Here's all the bootloader variables (S/N changed in this post for privacy), can someone make sense of the partitions? What's with the hexadecimal?:
Code:
$ fastboot getvar all
(bootloader) version-bootloader: 4.23
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) product: grouper
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: no
(bootloader) partition-size:bootloader: 0x0000000000600000
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000727f00000
(bootloader) partition-type:userdata: ext4
sponix2ipfw said:
Let me know if you are still having issues. As long as your device is detected by ADB and fastboot it should be fairly easy to recover...
Also, are you still trying to do F2FS or Custom Kernels at this point OR just get back to Working Stock ??
Click to expand...
Click to collapse
Bumping this again because I'm still having issues, anyone have any ideas about how I could go about getting my N7 back to working stock? It's recognisable by Fastboot, and I can get a working ADB connection through PhilZ recovery, but apart from that I can't do anything. It's a nice tablet and I'd like to get it back to a usable state.
After an update to my 2012 Nexus 7 a ways back, it became unbearably slow and I gave up on it. I'm assuming it was the 5-dot-something update because after doing a bit of digging just for kicks, it seems the same thing has happened to everyone else. So, I wasn't paying close enough attention and I flashed the 4.2.2 2013 nexus 7 version (from here https://developers.google.com/android/images) onto my 2012 Nexus 7. Feel free to point and laugh now.
My tablet is now stuck with showing the Google logo, and won't go past that. Plugged into my pc, it now longer shows up under devices in adb. However, if I go into recovery mode and then into sideload mode (and I've tried all the other options, clearing cache and factory reset I think), it will show up under adb, and will let me sideload. I've tried just about every file on this page https://forum.xda-developers.com/showthread.php?t=1745781 and still no luck. I've gone into the update script and removed the assert line as many suggest. Always ends up at "Aborted Installation" with no errors.
Are there any other options at this point, or do I have a new paperweight?
Thanks!
Ghoast said:
After an update to my 2012 Nexus 7 a ways back, it became unbearably slow and I gave up on it. I'm assuming it was the 5-dot-something update because after doing a bit of digging just for kicks, it seems the same thing has happened to everyone else. So, I wasn't paying close enough attention and I flashed the 4.2.2 2013 nexus 7 version (from here https://developers.google.com/android/images) onto my 2012 Nexus 7. Feel free to point and laugh now.
My tablet is now stuck with showing the Google logo, and won't go past that. Plugged into my pc, it now longer shows up under devices in adb. However, if I go into recovery mode and then into sideload mode (and I've tried all the other options, clearing cache and factory reset I think), it will show up under adb, and will let me sideload. I've tried just about every file on this page https://forum.xda-developers.com/showthread.php?t=1745781 and still no luck. I've gone into the update script and removed the assert line as many suggest. Always ends up at "Aborted Installation" with no errors.
Are there any other options at this point, or do I have a new paperweight?
Thanks!
Click to expand...
Click to collapse
Hi, Ghoast...
I think you need to reflash it.
It's been quite a while since I flashed my Nexus 7 2012, but if I remember correctly...
Long press and hold the power button and volume-down button together; this will reboot the Nexus 7 2012 into the bootloader.
Using fastboot, flash a Nakasi/Nakasig (depending on your device) Google factory image available from the first link in your post.
Sorry I don't have the time to provide more details, but I have to go out soon.
Rgrds,
Ged.
GedBlake said:
Hi, Ghoast...
I think you need to reflash it.
It's been quite a while since I flashed my Nexus 7 2012, but if I remember correctly...
Long press and hold the power button and volume-down button together; this will reboot the Nexus 7 2012 into the bootloader.
Using fastboot, flash a Nakasi/Nakasig (depending on your device) Google factory image available from the first link in your post.
Sorry I don't have the time to provide more details, but I have to go out soon.
Rgrds,
Ged.
Click to expand...
Click to collapse
I wish I could! In flashboot mode my device doesn't show up under the device list in adb. I can enter the commands but it just says <waiting on device>. Adb only seems to acknowledge it when I go into... I think it's called Recovery Mode. From there I can sideload updates, but as far as I can tell that is all I am able to do. Thanks though!
Ghoast said:
I wish I could! In flashboot mode my device doesn't show up under the device list in adb. I can enter the commands but it just says <waiting on device>. Adb only seems to acknowledge it when I go into... I think it's called Recovery Mode. From there I can sideload updates, but as far as I can tell that is all I am able to do. Thanks though!
Click to expand...
Click to collapse
Hi, Ghoast...
You're using ADB when you should be using Fastboot!
ADB doesn't work whilst the tablet is in fastboot mode.
ADB only works in fully booted Android and Recovery.
Only fastboot.exe will flash a device whilst it's in fastboot mode.
So, with the Nexus 7 booted into fastboot mode, type...
Code:
fastboot devices
If you have a successful fastboot connection (ie., assuming no driver problems), this should return your Nexus 7's serial number.
Your should then be able to flash the device using fastboot flash commands...
e.g.
Code:
fastboot flash bootloader [I]<<name-of-bootloader.img>>[/I] file
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc,
etc.
Or alternatively by running the flash-all.bat batch script file which accompanies factory stock images, although if I remember correctly there may be some problems with this method with the Nexus 7.
Be very careful when flashing the bootloader. Flashing the bootloader is the riskiest part of flashing a Nexus 7 and can potentially hardback the device if you flash the wrong one, or if, whilst flashing it, the USB is disconnected mid-flash. This would then require a motherboard replacement .
If your Nexus 7 is already running bootloader v4.23 (visible in the bottom left hand corner of the bootloader screen), there's no need to reflash it, as this is the latest version of the bootloader.
-----------------------------------------
I haven't reflashed or bothered with my Nexus 7 for about three years now, so my recollection of the precise details on reflashing it are somewhat hazy.
You can find some useful and important info on returning a Nexus 7 back to factory stock, here...
https://forum.xda-developers.com/showthread.php?t=1907796
-----------------------------------------
There are several different approaches that can be taken when flashing a Nexus device, including a Nexus 7 2012.
My own preferred method is to fully unzip the Google stock factory image to be flashed and then to fastboot flash the device partition by partition.
Apologies for the vagueness of my response - my memory isn't what it used to be, but one thing I am absolutely certain of...
ADB.exe won't flash your device.
fastboot.exe is required for flashing.
Rgrds,
Ged.
GedBlake said:
Hi, Ghoast...
You're using ADB when you should be using Fastboot!
ADB doesn't work whilst the tablet is in fastboot mode.
ADB only works in fully booted Android and Recovery.
Only fastboot.exe will flash a device whilst it's in fastboot mode.
So, with the Nexus 7 booted into fastboot mode, type...
Code:
fastboot devices
If you have a successful fastboot connection (ie., assuming no driver problems), this should return your Nexus 7's serial number.
Your should then be able to flash the device using fastboot flash commands...
e.g.
Code:
fastboot flash bootloader [I]<<name-of-bootloader.img>>[/I] file
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
etc,
etc.
Or alternatively by running the flash-all.bat batch script file which accompanies factory stock images, although if I remember correctly there may be some problems with this method with the Nexus 7.
Be very careful when flashing the bootloader. Flashing the bootloader is the riskiest part of flashing a Nexus 7 and can potentially hardback the device if you flash the wrong one, or if, whilst flashing it, the USB is disconnected mid-flash. This would then require a motherboard replacement .
If your Nexus 7 is already running bootloader v4.23 (visible in the bottom left hand corner of the bootloader screen), there's no need to reflash it, as this is the latest version of the bootloader.
-----------------------------------------
I haven't reflashed or bothered with my Nexus 7 for about three years now, so my recollection of the precise details on reflashing it are somewhat hazy.
You can find some useful and important info on returning a Nexus 7 back to factory stock, here...
https://forum.xda-developers.com/showthread.php?t=1907796
-----------------------------------------
There are several different approaches that can be taken when flashing a Nexus device, including a Nexus 7 2012.
My own preferred method is to fully unzip the Google stock factory image to be flashed and then to fastboot flash the device partition by partition.
Apologies for the vagueness of my response - my memory isn't what it used to be, but one thing I am absolutely certain of...
ADB.exe won't flash your device.
fastboot.exe is required for flashing.
Rgrds,
Ged.
Click to expand...
Click to collapse
Ged,
You were right! I was looking at the wrong thing, so thank you for that. I was able to flash the correct bootloader as the one I had on there was not the right version - I tried to update before updating the bootloader and it said it required 4.23. After updating and restarting the bootloader, I tried the flash-all bat file and got these results:
C:\nakasi-kot49h>flash-all.bat
...
FAILED (command write failed (No error))
finished. total time: 0.002s
erasing 'boot'...
FAILED (command write failed (No error))
finished. total time: 0.004s
erasing 'cache'...
FAILED (command write failed (No error))
finished. total time: 0.006s
erasing 'recovery'...
FAILED (command write failed (No error))
finished. total time: 0.007s
erasing 'system'...
FAILED (command write failed (No error))
finished. total time: 0.006s
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.004s
target didn't report max-download-size
sending 'bootloader' (3911 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.004s
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (No error))
finished. total time: 0.005s
Press any key to exit...
Lots of failing with no errors so... I dunno!
Thanks!
Ghoast said:
Ged,
You were right! I was looking at the wrong thing, so thank you for that. I was able to flash the correct bootloader as the one I had on there was not the right version - I tried to update before updating the bootloader and it said it required 4.23. After updating and restarting the bootloader, I tried the flash-all bat file and got these results:
C:\nakasi-kot49h>flash-all.bat
...
FAILED (command write failed (No error))
finished. total time: 0.002s
erasing 'boot'...
FAILED (command write failed (No error))
finished. total time: 0.004s
erasing 'cache'...
FAILED (command write failed (No error))
finished. total time: 0.006s
erasing 'recovery'...
FAILED (command write failed (No error))
finished. total time: 0.007s
erasing 'system'...
FAILED (command write failed (No error))
finished. total time: 0.006s
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.004s
target didn't report max-download-size
sending 'bootloader' (3911 KB)...
FAILED (command write failed (No error))
finished. total time: 0.004s
rebooting into bootloader...
FAILED (command write failed (No error))
finished. total time: 0.004s
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (No error))
--------------------------------------------
getvar:version-bootloader FAILED (command write failed (No error))
finished. total time: 0.005s
Press any key to exit...
Lots of failing with no errors so... I dunno!
Thanks!
Click to expand...
Click to collapse
Just to confirm, is the bootloader unlocked? If not, you can unlock it with...
Code:
fastboot oem unlock
You can't flash anything with a locked bootloader. If the bootloader is unlocked, you should see a white unlocked padlock symbol underneath the white Google logo when booting the Nexus 7. It should also say 'unlocked' in the bootloader screen in tiny letters in the bottom left hand corner.
It's also possible your fastboot executable may need updating. You can get the most up-to-date version of fastboot (and ADB) from here...
https://developer.android.com/studio/releases/platform-tools.html
Other points worth considering... Ensure you have a good USB connection between your PC and the Nexus 7. Sometimes it's also worth trying different USB cables and/or different USB ports on your PC when encountering problems when flashing a device.
Hope this helps and good luck.
Rgrds,
Ged.
I was using LineageOS (latest official build). I was trying to flash an updated bluetooth modem image, and the boot screen said my image was corrupt.
I was able to use LGUP to reinstall US99610f. Now I'm stuck at the fastboot screen on very boot, even after removing the battery. The phone is locked again, and I can't flash the unlock key through fastboot.
Code:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.026s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.068s
I'm unsure where to go from here, I've tried:
LGUP again
Hard power down/reboot
LG Mobile Flash Tool (CSE mode?), but that failed
Thanks,
Doug
DougWare said:
I was using LineageOS (latest official build). I was trying to flash an updated bluetooth modem image, and the boot screen said my image was corrupt.
I was able to use LGUP to reinstall US99610f. Now I'm stuck at the fastboot screen on very boot, even after removing the battery. The phone is locked again, and I can't flash the unlock key through fastboot.
Code:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.026s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.068s
I'm unsure where to go from here, I've tried:
LGUP again
Hard power down/reboot
LG Mobile Flash Tool (CSE mode?), but that failed
Thanks,
Doug
Click to expand...
Click to collapse
I have this same ****ing error, you get anything fixed
?
Silentwidow said:
I have this same ****ing error, you get anything fixed
?
Click to expand...
Click to collapse
I used LG's Web Chat Support, told them what happened. They were very accommodating and sent me a prepaid shipping label. They classified it as an "In Warranty - Software Failure", fixed it and shipped it back to me.
They did this even though they knew it was bootloader unlocked. Took about 2.5 weeks total to get it back.
Doug
us 996 fixed
i had a h910 flashed over to us996 that was stuck in fastboot. i had tried everything from flashing all the us996 firmwares to frp reset and came up with nothing. i then flashed H91510c_00_VTR_CA_OP_1007.kdz it not only successfully flashed but got me out of fastboot mode. i am now reflashing the us996 10f and will re root and twrp .. hope this helps someone out.