Hey guys I was on CM 12 latest stable I believe, and downloaded the Lollipop image from here : http://www.androidauthority.com/2012-nexus-7-wifi-lollipop-factory-image-566274/
It won't let me update, it's probably an easy fix but I'm not sure what file to flash. Running flash-all.bat runs and then says it's missing some files and that my bootloader is 4.18, instead of 4.23.
What's going on? I tried to download bootloader 4.23 and flash it myself but got this:
C:\Users\Nemesis\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.270s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.410s
C:\Users\Nemesis\Desktop\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>f
astboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.270s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.410s
EDIT: fixed the problem by replacing the bootloader in the archive with this one http://forum.xda-developers.com/showpost.php?p=45043044&postcount=15
Related
Hi There.
I just got a brand new Nexus 4 today and the first thing I tried to do was to update to the 4.3 Android version. I downloaded the factory image from Android.com. When I tried to run the flash-all.sh script I got this error:
macyccam-jwr66v trant_macbook$ ./flash-all.sh
sending 'bootloader' (2201 KB)...
OKAY [ 0.139s]
writing 'bootloader'...
FAILED (remote: not supported in locked device)
finished. total time: 0.142s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (54321 KB)...
OKAY [ 3.397s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 3.399s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ10o
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.48
Serial Number........: 027af952120bb5bf
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MAKOZ10o'.
Update requires 'MAKOZ20i'.
finished. total time: 0.012s
Click to expand...
Click to collapse
Is something wrong with my bootloader ?
xDer_ said:
Hi There.
I just got a brand new Nexus 4 today and the first thing I tried to do was to update to the 4.3 Android version. I downloaded the factory image from Android.com. When I tried to run the flash-all.sh script I got this error:
Is something wrong with my bootloader ?
Click to expand...
Click to collapse
Your bootloader seems like it's locked. You need to unlock it first with fastboot by running "fastboot oem unlock". Note that this will wipe all data on your device, which you probably don't mind since you just got the device.
I wanted to go stock rom, So I downloaded factory Image from google.
But, When send system partion, stop and not flashing.
I were waiting for 30 minutes, But, Not sending,
I tried with Nexus Root Kit, and flash-all.bat, but nothing work.
what can I do?
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.034s]
finished. total time: 0.034s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.106s]
finished. total time: 0.106s
erasing 'recovery'...
OKAY [ 0.035s]
finished. total time: 0.035s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.117s]
finished. total time: 0.117s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 5.003s]
finished. total time: 5.004s
sending 'bootloader' (3911 KB)...
OKAY [ 0.662s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.895s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
sending 'radio' (16384 KB)...
OKAY [ 2.124s]
writing 'radio'...
OKAY [ 0.672s]
finished. total time: 2.797s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: 1231_0.18.0_0409
Serial Number........: 015d2a5045640411
--------------------------------------------
checking product...
OKAY [ 0.040s]
checking version-bootloader...
OKAY [ 0.023s]
checking version-baseband...
OKAY [ 0.031s]
sending 'boot' (4992 KB)...
OKAY [ 0.674s]
writing 'boot'...
OKAY [ 0.208s]
sending 'recovery' (5532 KB)...
OKAY [ 0.738s]
writing 'recovery'...
OKAY [ 0.230s]
erasing 'system'...
OKAY [ 0.115s]
sending 'system' (625578 KB)...
I'm not an expert in the field but I have done a great deal of reading around this subject.
I have come across other posts with this issue and the solution was to format the system partition using custom recovery, then try the flash again.
Which firmware version are you trying to flash? It also looks like the bootloader is failing to write, but as you already have version 4.23 this shouldn't present a problem.
If you use Wug's toolkit to flash back to stock, use one of these firmwares: JWR66V, KRT16O, KRT16S (assuming you have Nexus 2012 Wi-Fi) - other versions contain a corrupted 4.23 bootloader.img
http://forum.xda-developers.com/showthread.php?t=2625843
please see my last comment for fix
click thanks if i helped
[email protected]:/home/zarkpafilis/Desktop/razor-kot49h# bash flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.751s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.990s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
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........: 015d4a5f0020180c
--------------------------------------------
checking product...
FAILED
Device product is 'grouper'.
Update requires 'flo'.
finished. total time: 0.177s
[email protected]:/home/zarkpafilis/Desktop/razor-kot49h#
The device is nexus 7 32 gb wifi (grouper). I cant find any grouper image here , so I downloaded the latest razor one. I bought the tablet in 2013(xmas)
[email protected]:/home/zarkpafilis/Desktop/razor-kot49h# ls
bootloader-flo-flo-04.02.img flash-all.sh image-razor-kot49h.zip
flash-all.bat flash-base.sh
[email protected]:/home/zarkpafilis/Desktop/razor-kot49h#
Im trying to boot nagasig latest. It seems it may work
It did not: - Now im stuck with a bootloader mode device that fails to boot!
[email protected]:/home/zarkpafilis/Desktop# cd nakasig-kot49h
[email protected]:/home/zarkpafilis/Desktop/nakasig-kot49h# bash flash-all.sh
\...
(bootloader) Bootloader is already unlocked
OKAY [ 0.591s]
finished. total time: 0.591s
erasing 'boot'...
OKAY [ 0.032s]
finished. total time: 0.032s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.132s]
finished. total time: 0.133s
erasing 'recovery'...
OKAY [ 0.032s]
finished. total time: 0.032s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.193s]
finished. total time: 0.194s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.616s]
finished. total time: 8.616s
sending 'bootloader' (3911 KB)...
OKAY [ 0.760s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.987s
rebooting into bootloader...
OKAY [ 0.021s]
finished. total time: 0.021s
sending 'radio' (16384 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
rebooting into bootloader...
archive does not contain 'boot.sig' - it stayed there
Now the tablet is not recognized with adb devices!
Fastboot recognizes it as blah blah
I managed to get it working again , but it misses flo and tiltapia (or something) - I downloaded the wifi versions of the image , the latest versions.
Downloading nakasi earliest version - It is sending system , it should work.
I couldnt do adb reboot-fastboot so I manually refreshed the fastboot again and then it got detected
It finisehn , my tablet is back on life - I will leave this thread so others can see it. Thanks people for doing nothing!
I dont know why but I keep solving stuff myself without help on forums
Sorry couldnt post links
I used nakasi-jzo54k
I tried doing the instructions from the developers page (new user so i cant post a link)
but I always get this error when I execute flash-all.bat
sending 'bootloader'...
okay [ 0.500s]
writing 'bootloader'
FAILED <remote: <invalidState>>
finished. total time: 0.734s
rebooting into bootloader...
Okay [ 0.20s ]
finished; total time: 0.21s
sending 'radio' <43814 KB>...
OKAY [ 5.428s]
writing 'radio'
Failed <remote: <invalidSize>>
finished. total time: 5.460s
rebooting into bootloader...
FAILED <command write failed <unknown error>>
finished. total time: 5.004s
archive does not contain 'boot.sig'
error: out of memory
press any key to exit
I am currently on lollipop and I want to downgrade to jellybean so I downloaded the razorg 4.3.1 image. Any chance its wrong?
Here is what my device says on bootloader
fastboot mode
product name - tilapia
variant - tilapia
mw version - pr
bootloader version 4.23
baseband version- na
signing - not defined yet
lock state - unlocked
UPDATE: I DOWNLOADED THE WRONG IMAGE FILE. I AM ON JELLYBEAN NOW.
My Nexus 7 (2013 Mobile) was rooted and updated to stock Android 6.0 a year ago, no 3rd party ROM/recovery is installed. Last week while checking emails, it rebooted suddenly then remained at Google letters and unlock icon, I can enter fastboot mode by pressing power and volume- buttons together, the last line shows status unlocked; then if select "Recovery mode", it reboots then shows a dead robot with an exclamation mark only. I downloaded the latest factory image "razorg-mob30x", connect it to my PC and enter adb command "flash-all.bat" (I modified the bat file by removing -w, so it won't wipe the user data), then it shows: FAILED (remote: flash write failure)
sending 'bootloader' (3915 KB)...
OKAY [ 0.135s]
writing 'bootloader' ...
FAILED (remote: flash write failure)
finished. total time 90.811s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time 0.012s
sending 'radio' (76038 KB)...
OKAY [ 2.393s]
writing 'radio' ...
FAILED (remote: flash write failure)
finished. total time 92.549s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time 0.013s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
----------------------------------------------------
Bootloader Version...: FLO-04.08
Basedband Version...: DEB-Z00_2.44.0_0213
Serial Number................: 0879222a
----------------------------------------------------
checking product...
OKAY [ 0.005s]
checking version-bootloader...
OKAY [ 0.006s]
checking version-baseband...
OKAY [ 0.006s]
sending 'boot' (7422 KB)
OKAY [ 0.243s]
writing 'boot' ...
FAILED (remote: flash write failure)
finished. total time 90.151s
Press any key to exit...
Click to expand...
Click to collapse
What else I can do to resuce my pad? Does this mean the memory is physically damaged?
Please advise. Your help is much appreciated.