Fastboot -w ERROR: Erase successful, but not automatically formatting. - Essential Phone Questions & Answers

Hello,
my essential phone was working great. i unlocked the bootloader and installed magisk.
The problem is that i got 3 dead pixel in the middle of the screen over night.
I know need to return it to amazon.
As i tried to get back to stock i get the following error(i am on the newest Firmware):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: unknown command)
finished. total time: 0.004s
When i try to flash the stock img i get the following error:
FAILED (Write to device failed (Unknown error)) on every task
for example:
C:\Users\Cj\Desktop\handy\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash system_a system.img
Sending 'system_a' (2097360 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.010s
C:\Users\Cj\Desktop\handy\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash system_b system.img
Sending 'system_b' (2097360 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.010s
Thank you for helping.

kappagei said:
Hello,
my essential phone was working great. i unlocked the bootloader and installed magisk.
The problem is that i got 3 dead pixel in the middle of the screen over night.
I know need to return it to amazon.
As i tried to get back to stock i get the following error(i am on the newest Firmware):
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: unknown command)
finished. total time: 0.004s
When i try to flash the stock img i get the following error:
FAILED (Write to device failed (Unknown error)) on every task
for example:
C:\Users\Cj\Desktop\handy\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash system_a system.img
Sending 'system_a' (2097360 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.010s
C:\Users\Cj\Desktop\handy\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash system_b system.img
Sending 'system_b' (2097360 KB) FAILED (Write to device failed (Unknown error))
Finished. Total time: 15.010s
Thank you for helping.
Click to expand...
Click to collapse
after 4 hours of finding a error with the fastloader -w command i finally got it. it was the combination of a usb 3 port and the usb cabel from essential and a windows 10 computer.
My phone is now on oreo and and the bootloader is logged again!

Yeah don't use the usb c cable that comes with the phone for data. I have a USB c to A cable from Anker that I use.

kappagei said:
after 4 hours of finding a error with the fastloader -w command i finally got it. it was the combination of a usb 3 port and the usb cabel from essential and a windows 10 computer.
My phone is now on oreo and and the bootloader is logged again!
Click to expand...
Click to collapse
Bro, i didn't get what you are trying to say.. i am stuck with the same situation.. which cable you used to solve the problem

chauhansonu104 said:
Bro, i didn't get what you are trying to say.. i am stuck with the same situation.. which cable you used to solve the problem
Click to expand...
Click to collapse
The Essential supplied usb-c cable should not be used for anything but charging. Even Essential admits it is too poor to use for data transmission. Get a good quality usb-c cable and try again.

Related

[Q] I've inherited an original (broken?) Nexus 7

Apologies if I'm asking anything blatantly obvious, I'm relatively new to all things Android..
The Nexus 7 I have won't boot it just displays the Google logo & an open padlock.
I've been advised to try the Nexus Root Toolkit & it's Soft-Bricked/Bootloop option.. unfortunately this doesn't work:
erasing 'boot'
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
erasing 'cache'...
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
erasing 'system'
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
erasing 'userdata'
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
sending 'bootloader' (3911 KB)
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
archive does not contain 'boot.sig'
error: out of memory
Any help would be greatly appreciated
Thanks.
If the padlock is opened chances are there is a custom recovery see if u can boot into it. Hold volume up and down together and power
Sent from my SGH-T679 using Tapatalk
...Awesome... said:
If the padlock is opened chances are there is a custom recovery see if u can boot into it. Hold volume up and down together and power
Sent from my SGH-T679 using Tapatalk
Click to expand...
Click to collapse
Nope, I can't do that.. it just starts the bootloader & I can't select anything when it's on
The bootloader screen info is as follows:
FASTBOOT MODE
PRODUCT NAME - grouper
BOOTLOADER VERSION - 3.34
LOCK STATE - Unlocked
you might be able to soft-boot it (that is, have it boot a custom recovery without actually flashing it to the eMMC chip) as in:
Code:
C:\blech> fastboot boot eg-custom-recovery-imagefile-of-your-choice-goes-here.img
and have a look using adb at the kernel boot messages from that custom recovery's boot log (once it has finished booting)
Code:
C:\blech> adb shell dmesg > dmesg_log.txt
my guess (because fastboot erases are failing) is that it might boot but will not recognize any valid partition tables - you will see messages to that effect in the kernel log.
If that's the case, there is nothing you can do to fix it.

[Q] writing 'bootloader'... FAILED (remote: (Unknown error code))

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.

L5 E610 - bricked - only fastboot - Secure booting error

Hello out there,
I get a used L5 for my little son, tryed to clear all data (factory reset) and it just partically worked, some data always survied.
I thougt, no prob, then I use recovery. when I tried to boot the recovery mode I saw the Message:
Secure booting error! Cause: boot certification verifiy
HM!
OK Lets try to install a custom recovery (first rooted with kingo, then install twrp 3 with dd)
Jet I only get the Message on booting nothing else is possible. fastboot is available.
Update the ROM with KDZ updater dosn`t work " No connection to phone"
I need *.img files that I can use with fastboot. I tryed to convert a kdz with two tools I found ( a python script and a tool developed for the G series) but that dosn`t work.
Is there a simple way to convert a ZIP to a IMG?
I tryed "fastboot boot recovery.img" and to flash it, but that also dosn`t work (orig. and TWRP)
I also get this:
Code:
C:\Users\mariu>fastboot erase userdata
erasing 'userdata'...
FAILED (status read failed (Too many links))
finished. total time: 2.489s
C:\Users\mariu>fastboot erase cache
erasing 'cache'...
FAILED (status read failed (Too many links))
finished. total time: 2.487s
C:\Users\mariu>fastboot -w
Erase successful, but not automatically formatting.
File system type not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
FAILED (status read failed (Too many links))
finished. total time: 2.476s
C:\Users\mariu>fastboot flash boot C:\Temp\L5\boot.img
sending 'boot' (4864 KB)...
OKAY [ 0.463s]
writing 'boot'...
OKAY [ 1.330s]
finished. total time: 1.800s
THX for help

Fastboot Drivers

Hello guys,
I know this question is very common but I have looked many posts and couldn't find any that solved my problem.
I am trying to flash the stock moto X pure edition (xt1575) again in my device. The trouble starts because fastboot doesn't work.
I already installed Motorola device manager (2.5.4) and booted windows without driver signature enforcement.
I tried adb-setup-1.4.3.exe and installing android SDK, but still get same trouble.
The phone works and get normally funcional when android is loaded, but no responde in fastboot screen!
I am using windows 10.15063.296 (creators update). When I open device manager, now I see "Motorola adb device" with an exclamation.
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forget-windows-use-linux-is-a-usb-bootable-distro-for-your-android-recovery-needs-xda-spotlight/
jason2678 said:
A lot of windows, especially windows 10, users seem to struggle with drivers. I use Linux and never have any problems.
Maybe you could give this a try. https://www.xda-developers.com/forg...or-your-android-recovery-needs-xda-spotlight/
Click to expand...
Click to collapse
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Belotto said:
Thanks. After hours trying, I could get fastboot working.
The issue now is that I got "preflash failed" when trying the officially image available.
Enviado de meu XT1575 usando Tapatalk
Click to expand...
Click to collapse
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
I really wasn´t successful...
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> adb reboot-bootloader
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.370s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash motoboot motoboot.img
error: cannot load 'motoboot.img'
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash logo logo.bin
target reported max download size of 536870912 bytes
sending 'logo' (3687 KB)...
OKAY [ 0.137s]
writing 'logo'...
OKAY [ 0.200s]
finished. total time: 0.337s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (40960 KB)...
OKAY [ 1.518s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.888s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (41040 KB)...
OKAY [ 1.534s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.887s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (509631 KB)...
OKAY [ 17.857s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 18.357s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot reboot
rebooting...
finished. total time: 0.016s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase userdata
erasing 'userdata'...
OKAY [ 6.423s]
finished. total time: 6.423s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot erase cache
erasing 'cache'...
OKAY [ 0.031s]
finished. total time: 0.031s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.015s]
finished. total time: 0.015s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock begin
...
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.017s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US> fastboot oem lock
...
(bootloader) Please run fastboot oem lock begin first!
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\Android\sdk\platform-tools\CLARK_RETUS_MPH24.49-18_18_retus_US>
jason2678 said:
Just on bootloader and gpt.bin, or everything?
That happens when you try to downgrade the partition table, but usually as long as you flash all the other parts successfully it works. Keep a close eye on the output when you flash modem; it tends to fail on the first try.
Click to expand...
Click to collapse
Sagar_1401 said:
https://forum.xda-developers.com/showthread.php?t=2588979
This is the one... I had this on my window's 10. I upgraded to creators update and i doubted that this might not work but it did work for me
Click to expand...
Click to collapse
I have tried it before... wasn't working but i realized that i needed to push "allow oem unlock" and "usb debugging" buttons ... LOL.

Flashed 2013 Nexus 7 ROM onto 2012 Nexus 7

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.

Categories

Resources