Database Users

[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.

Stuck in Fastboot and Rescue Mode [hifi image error]

Hi everyone, I'm done and out of any ideas. Never before have I bricked my phone . Now I don't know what to do. Played before only with Samsung phones, they were waaay easier to play with.
Let me tell you my story:
1. Got P9 Lite with L21C22B120 rom (brand C22 from Poland)
2. No newer version available, decided to debrand / apply newer - flashed L21C432B161 (~3GB update.app), info showed L21C900B161 - need to change oeminfo etc.
3. [SRK Tool ] Unlocked bootloader and installed TWRP
4. [SRK Tool + TWRP] Built Root method via adb sideload failed, so installed SuperSu via TWRP from another source - success
5. [SRK Tool] Flashed oeminfo C432 Europe - success, but after that info showed C432B161 without L21
6. Flashed once more with the same B161 firmware - perfect info L21C432B161 but UI theme and icons got corrupted like that: https://forum.xda-developers.com/p9-plus/help/wrong-icons-c900-to-c432-failed-im-t3490561 and tried to flash mentioned hw_folder with SRK Tool.
7. [TWRP] Played with wipe / factory reset - couldn't boot anymore, TWRP showed "No OS installed" and "unable to mount /data" (it had 0MB, couldn't wipe it)
8. Then RESCUE MODE showed up and still I can't pass by it - exactly like here: https://forum.xda-developers.com/p8lite/help/stuck-rescue-mode-screen-please-help-t3244872 - only fastboot&rescue available.
What I have tried several times:
1. Flashing firmware C432B161 and C432B120 - failure at 5% (incompatibility)
2. Fastboot flash boot.img, recovery.img, system.img and cust.img (extracted from B120 and B161)- success, still rescue mode loop
3. Locking and unlocking bootloader with SRK Tool, flashing stock recovery and TWRP - success, still unable to load any recovery
4. Fastboot flashing FW_hifi.img - FAILED <remote: command not allowed>
Summary:
1. Looped Rescue mode shows: Please update system again, Func no : 8 (hifi image), Error no : 1 (security verify failed)
2. Fastboot&Rescue mode shows: Phone unlocked, FRP Unlock. Fastboot works.
3. Flashing main images doesn't change enything, can't flash corrupted(?) hifi image.
4. Maybe there is something wrong with my Bootloader? Is it truly unlocked? SRK Tool shows bootloader "unlocked" but many of the fastboot commands (i.e. getvar or oem) return "Failed, remote: command not allowed"
Any ideas in any of your clever or experienced heads? Should I try to flash that magical hifi image somehow or to flash some "compatibile" firmware (don't know which one wouldn't return that error).

Tried some fastboot commands, seems like I have found the reason for ROMs incompatibility:
fastboot getvar rescue_version
rescue_version: rescue0.3
finished. total time: 0.071s
fastboot getvar rescue_phoneinfo
rescue_phoneinfo: VNS-C432B161
finished. total time: 0.011s
fastboot oem get-product-model
...
(bootloader) hi6250
OKAY [ 0.011s]
finished. total time: 0.013s
fastboot oem get-psid
...
(bootloader) SN:BUC4C16929(...)
(bootloader) IMEI:863126032(...)
(bootloader) IMEI:863126032(...)
OKAY [ 0.011s]
finished. total time: 0.012s
fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.010s
fastboot oem check-rootinfo
...
(bootloader) old_stat: SAFE
(bootloader) now_stat: SAFE
(bootloader) change_time: 0000000000
(bootloader) Check System: Decode fail
OKAY [ 0.018s]
finished. total time: 0.020s
fastboot oem get-build-number
...
(bootloader) :VNS-C432B161
OKAY [ 0.012s]
finished. total time: 0.013s
fastboot oem device-info
...
FAILED (remote: Command not allowed)
finished. total time: 0.013s
What happened to L21 model in my build and model number? Is it corrupted?

Install os manually via adb mounting boot system and the other two things (i don't remember all and i don't have any link)

You can go to Twrpmeticulus?

Thanks guys! I flashed Meticulus TWRP - still couldn't enter it but accidentally discovered the (weird) way. I could go to it only with USB cable connected to computer and by pressing Vol+, Vol- and Power simultaneously, releasing them upon Huawei Logo. From there (TWRP) I rooted my device (adb sideload SuperSU 2.65), replaced oeminfo file via this tutorial - https://forum.xda-developers.com/huawei-p9lite/how-to/request-oeminfo-c432-p9-lite-t3427386 - and voila, I could finally flash C432B161 ROM without incompatibility error. Problem solved, hifi error gone of course.

flashed wrong rom help plz!

i have a mla-l03 but the model number says YLEDU16922001380 and whenever i try and flash stock img files
FAILED (remote: Command not allowed)
finished. total time: 0.027s
is something in my way like selinux ? phones rooted also i have sesuperuser and busy box

[SOLVED] Fastboot fails, and SD flash stuck at 5%

I did something apparently pretty stupid and let my ALE-UL00 update itself after having installed iRoot (yeah I didn't know what I was doing). I really just wanted to install an English version of the OS since changing the language in the settings only changed about half of it...
Anyway, now when I boot the phone, I get a screen with three options, roughly translated "clear cache", "restore factory settings", and "reboot". Selecting any of these leads to the phone booting right back to that screen again.
I've tried to flash two different ROMs using the SD card method. Neither from Huawei's website as I can't find my model anywhere on there, but both claiming to be for my phone. So I boot into recovery mode (vol up + vol down + power) while plugged in, I see the USB emblem, and it gets stuck at 5%. If I boot in recovery mode without plugging it in, it just plain fails at 5% and gives me a link to a website that has pictures of phones (none of them mine) and no download links.
I can boot the phone in fastboot/rescue mode (vol down + power), and fastboot does recognize it. So I extracted the UPDATE.APP using Worstenbrood's tool and tried to fastboot it manually. This fails, and here's what happens:
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
XXXXXXXXXXXXXXXX fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :ALE-UL00C00B569
OKAY [ 0.074s]
finished. total time: 0.079s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock-state info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: LOCKED
OKAY [ 0.026s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.009s]
finished. total time: 0.014s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot BOOT.img
target reported max download size of 471859200 bytes
sending 'boot' (22918 KB)...
OKAY [ 0.647s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.674s
If anyone has any clue what I can try next, I'd greatly appreciate it!

mathguyjohn said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock-state info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: LOCKED
OKAY [ 0.026s]
finished. total time: 0.031s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.009s]
finished. total time: 0.014s
Click to expand...
Click to collapse
In particular, can anyone say why lock-state info says it's locked, but get-bootinfo says it's unlocked? The fastboot screen on my phone says "PHONE Unlocked"

Update: I tried holding volume up to get to the eRecovery menu. I entered my Wi-Fi password, it looked for an update, and then got a red explanation mark along with a message Google translate tells me is "get package installation failure".

Update: I guess BOTH of the ROMs I'd tried to flash from the SD card were corrupted. I found a working copy elsewhere on this forum. Though nobody responded to this particular thread, this forum was immensely helpful nevertheless, so thanks guys!

For anyone that stumbles across this comment, follow this.

JpegXguy said:
For anyone that stumbles across this comment, follow this.
Click to expand...
Click to collapse
Dude, my entire problem was that the procedure outlined in this link was not working. It's the first two words of the post title...
I don't mean to be rude, but when I had this problem, I wasted countless hours sifting through people repeating the exact same solution. If it had worked for me, I wouldn't have needed to post here. I was clear about this.
Fastboot wasn't letting me flash any of the imgs, so the only thing I could do was but the correct update.app on a micro SD card and boot into recovery mode. The only reason that didn't work was because I kept finding corrupted ROMs. The one in the post you linked to wasn't for the right model of phone, so that link would have done nothing for me.
The entire problem was that the UL00 seems woefully undersupported in the English-speaking community, so I had a difficult time finding the correct one. I did find the right one on this forum, though, and it's here: https://forum.xda-developers.com/p8lite/general/emui-4-0-1-ale-ul00c00b569ota-t3467620

VNS-L21 bricked. Black screen. Only fastboot available

hello
i had a beautiful and full working P9 Lite, VNS-L21 Dual Sim with stock Android 7.0.
wanted to downgrade to MM, but i got it bricked
boot unlocked, flashed TWRP, then OEM file and then Official (all from here : http://www.htcmania.com/showthread.php?t=1261335)
after starting official MM flashing by VOL+, VOL- and POWER, got error "Software install failed!" and dead from that moment.
flashed different TWRP and tried to boot into recovery by VOL+ and POWER, but nothing
also flashed different versions of 6.0 and 7 by fastboot, nothing. at some point boot got locked back, but unlocked it again.
disassembled, disconnected battery, nothing.
ready to try any ideea you think may be lucky.
thanks

If you're getting fastboot try and unlock your bootloader, install twrp for mm. Try and download your firmware eg L21C532B160, leave it in the zip format, place on your SD card, then boot into TWRP and flash the zip file. That should do the trick.
Sent from my HUAWEI VNS-L21 using Tapatalk

Install revolution recovery flash oem and dload c432

@slaughta8868, @Dimitardt - thanks, but in that situation only DC Phoenix or Furious Resurrector could get me out. These 2 progs are able to write absolutely anything into phone, and all needed partitions. Also able to revive by testpoint. i had access to Furious Resurrector and now phone is alive again.
but got this error, no matter what firmware is written.
any idea ?
photo fastboot http://imgur.com/a/vqoJM
C:\AndroidADB>fastboot oem get-build-number
...
(bootloader) :VNS-L21C432B130
OKAY [ 0.000s]
finished. total time: 0.000s
C:\AndroidADB>fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1470987496
OKAY [ 0.000s]
finished. total time: 0.000s
thanks

https://forum.xda-developers.com/hu...torial-rollback-n-to-mm-c432-devices-t3563955 try this

I have the same problem with my VNS-L31. Tried to rollback and it just turned off at 99% or 100% and now it does not turn back on. I can only access fastboot through the PC. No dload or recovery. Tried flashing separate system.img, boot.img etc. files but it does not work. Is there really no way other than Furious Resurrector or DC Phoenix to flash the full UPDATE.APP through fastboot? Is there no package, custom ROM, whatever, which has an android-info.txt inside?

i got same problem. after flash no vibration, no display, only fastboot accessible:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-build-number
...
(bootloader) :EVA-L09C432B136
OKAY [ 0.005s]
finished. total time: 0.006s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: RISK
(bootloader) change_time: 1463672304
OKAY [ 0.008s]
finished. total time: 0.010s

nbkappa said:
@slaughta8868, @Dimitardt - thanks, but in that situation only DC Phoenix or Furious Resurrector could get me out. These 2 progs are able to write absolutely anything into phone, and all needed partitions. Also able to revive by testpoint. i had access to Furious Resurrector and now phone is alive again.
but got this error, no matter what firmware is written.
any idea ?
photo fastboot http://imgur.com/a/vqoJM
C:\AndroidADB>fastboot oem get-build-number
...
(bootloader) :VNS-L21C432B130
OKAY [ 0.000s]
finished. total time: 0.000s
C:\AndroidADB>fastboot oem check-rootinfo
...
(bootloader) old_stat: RISK
(bootloader) now_stat: SAFE
(bootloader) change_time: 1470987496
OKAY [ 0.000s]
finished. total time: 0.000s
thanks
Click to expand...
Click to collapse
Can you show me test point image VNS-L31 please?

Test point
Here test point image