I tried to install nakasi-lrx22g (should be Android 5), but the update process complains about boot loader version. So I tried to update the bootloader via "fastboot flash boot" with the enclosed boot loader image. This worked without error message:
fastboot flash boot ./bootloader-grouper-4.23.img
sending 'boot' (2100 KB)...
OKAY [ 0.270s]
writing 'boot'...
OKAY [ 0.116s]
finished. total time: 0.385s
, but the boot loader remains 4.18:
FASTBOOT MODE
PRODUCT NAME - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.18
BASEBAND VERSION - N/A
SERIAL NUMBER - ...
SIGNING - not defined yet
LOCK STATE - unlocked
How could that happen? Is the partition write protected?
Addendum: Instead of installing the bootloader from the image I tried to install the one from that thread:
[Q] JWR66Y nakasi factory image bootloader problem
This also was unsuccessful, i.e. bootloader remained 4.18.
Addendum 2: Instead of directly installing the bootloader I replaced the one in the image with that from the mentioned thread, and now the update worked.
This is really (!) strange.
Ahkah said:
I tried to install nakasi-lrx22g (should be Android 5), but the update process complains about boot loader version. So I tried to update the bootloader via "fastboot flash boot" with the enclosed boot loader image. This worked without error message:
fastboot flash boot ./bootloader-grouper-4.23.img
sending 'boot' (2100 KB)...
OKAY [ 0.270s]
writing 'boot'...
OKAY [ 0.116s]
finished. total time: 0.385s
, but the boot loader remains 4.18:
FASTBOOT MODE
PRODUCT NAME - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.18
BASEBAND VERSION - N/A
SERIAL NUMBER - ...
SIGNING - not defined yet
LOCK STATE - unlocked
How could that happen? Is the partition write protected?
Addendum: Instead of installing the bootloader from the image I tried to install the one from that thread:
[Q] JWR66Y nakasi factory image bootloader problem
This also was unsuccessful, i.e. bootloader remained 4.18.
Addendum 2: Instead of directly installing the bootloader I replaced the one in the image with that from the mentioned thread, and now the update worked.
This is really (!) strange.
Click to expand...
Click to collapse
Use the version from that post. And the command is fastboot flash bootloader not boot.
riggerman0421 said:
Use the version from that post. And the command is fastboot flash bootloader not boot.
Click to expand...
Click to collapse
So it was finally just a dumb typo. Thanks! And of course the questions remain why fastboot did not respond with an error message when I tried to install the bootloader using a wrong command and why Google's original package failed to be installed.
It didn't give am error because it was flashing an image file(bootloader) to a correctly named partition (boot). The error was yours, flashing the file to the wrong partition. Fastboot was following the instructions you gave it. As for the bootloader file not flashing, it has been broken for a while in the factory image. I guess Google isn't worried about fixing it.
Related
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help
rohanjoshi said:
So, where do I start?
I bought this device (Nexus 2013 Wi-Fi) in late november and have not updated it since. I attempted to update it today (because I received a notification to do so) to 4.4.2 (I think).
It restarted after the update and I've been stuck in a bootloop at the "4 circles".
I have done the following:
- put the device into the boatloader
- installed the nexus root toolkit and attempted to flash stock + unroot the device to the images: 4.3 (JSS15Q), 4.3 (JSS15R), and (KOT49H)
- this was what my output looked like
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.006s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 08e8df8e
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.003s]
sending 'boot' (7018 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.027s
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
- And no, I have not tried the force flash.
- I have tried all the drive options and maybe I'm not following the directions properly but that does not seem to work (and it may be the main problem for all I know).
- I'm also not sure if I thoroughly removed all google nexus-related drivers prior to running the nexus root toolkit, so there may be that.
- I've tried some brute-force methods inspired by things I've seen here, as in:
un-packing the factory image files into the platform tools part of the android sdk files and run the following commands in the cmd.exe: fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system
fastboot flash system system.img - My guess is that the problem lies with the fact that I cannot put the device in debugging mode and I cannot have it recognized by adb.
I'm not sure where to go from here and I'm rather frustrated. Please let me know what solutions I should re-try (but perhaps more carefully?) and new ones that I should know of.
I appreciate all your help
Click to expand...
Click to collapse
Hi, rohanjoshi...
You're actually on the wrong forum... this is the forum for the first generation Nexus 7 (2012). The forum for your second generation Nexus 7 (2013) is located here...
http://forum.xda-developers.com/nexus-7-2013
--------------------------------
However, looking through your output, it seems the failure to flash is due to the bootloader being locked...
rohanjoshi said:
...
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
...
Click to expand...
Click to collapse
You need to unlock it with...
Code:
fastboot oem unlock
....or whatever the equivalent is in the toolkit you're using.
Good luck.
Rgrds,
Ged.
GedBlake said:
Hi, rohanjoshi...
You're actually on the wrong forum... this is the forum for the first generation Nexus 7 (2012). The forum for your second generation Nexus 7 (2013) is located here...
http://forum.xda-developers.com/nexus-7-2013
--------------------------------
However, looking through your output, it seems the failure to flash is due to the bootloader being locked...
You need to unlock it with...
Code:
fastboot oem unlock
....or whatever the equivalent is in the toolkit you're using.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
woops, I'll get on that!
hello guys when i try to flash the bt my wifi n7 2012 with 4.4.2 (grouper-Nakasi) is in error and do not understand why ... can someone help me?
Code:
Microsoft Windows [Versione 6.1.7601]Copyright (c) 2009 Microsoft Corporation. Tutti i diritti riservati.
C:\Users\Francesco>cd C:\Users\Francesco\Desktop\Nuova cartella\nakasi-kot49h
C:\Users\Francesco\Desktop\Nuova cartella\nakasi-kot49h>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.522s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.758s
Code:
fastboot mode
product name - grouper
variant - grouper
hw versione - er3
bootloader version - 4.23
baseband version - n/a
serial number - xxxxxxxxxxx
singning - not defined yet
lock state - unlocked
forgive my english, but I translated with tranlate
sommoomnia said:
hello guys when i try to flash the bt my wifi n7 2012 with 4.4.2 (grouper-Nakasi) is in error and do not understand why ... can someone help me?
Code:
Microsoft Windows [Versione 6.1.7601]Copyright (c) 2009 Microsoft Corporation. Tutti i diritti riservati.
C:\Users\Francesco>cd C:\Users\Francesco\Desktop\Nuova cartella\nakasi-kot49h
C:\Users\Francesco\Desktop\Nuova cartella\nakasi-kot49h>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.522s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.758s
Code:
fastboot mode
product name - grouper
variant - grouper
hw versione - er3
bootloader version - 4.23
baseband version - n/a
serial number - xxxxxxxxxxx
singning - not defined yet
lock state - unlocked
forgive my english, but I translated with tranlate
Click to expand...
Click to collapse
Hi, sommoomnia...
There known issues fastboot flashing the v4.23 bootloader that ships with **some** versions of Factory Stock, and that are known to cause 'Invalid state/ signature mismatch' errors when fastboot flashed.
For further details, see here... and also here, [WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google.
However, the second half of your output above indicates your Nexus 7 has the v4.23 bootloader already installed... so I'm a little puzzled why you're attempting to flash it again.
Rgrds,
Ged.
GedBlake said:
Hi, sommoomnia...
There known issues fastboot flashing the v4.23 bootloader that ships with **some** versions of Factory Stock, and that are known to cause 'Invalid state/ signature mismatch' errors when fastboot flashed.
For further details, see here... and also here, [WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google.
However, the second half of your output above indicates your Nexus 7 has the v4.23 bootloader already installed... so I'm a little puzzled why you're attempting to flash it again.
Rgrds,
Ged.
Click to expand...
Click to collapse
Today I wanted to do a factory reset and I used to reflash the rom to be sure to start from clean rom and I found the error ....
Hey there,
I tried to upgrade my Nexus 7 grouper using the 4.23 bootloader and some of the stock roms, cyanogenmod and miui as well as slimkat roms, it kinda didnt work out the way I wanted it to, now I am stuck on: sending 'bootloader' (2100 KB) while not having any recovery nor anything else on my nexus...
the bootloader seems broken, because it always doesnt response when I try to flash an img file..
Thankful for any help
Can you get into fastboot mode?
Did you get the bootloader-grouper-4.23.img file from one of the factory images here?
What is the md5?
I've been reading that these factory image bootloaders (JWR66Y & KOT49H) do not work.
Check out these threads:
http://forum.xda-developers.com/showthread.php?t=1907796
http://forum.xda-developers.com/showthread.php?p=45043044#post45043044
It seems like I used the bootloader from nakasi-kot49h-factory-5e9db5e1
it has got the md5 hash 797a8ddfe19bfe4c485f8a8c119f1bdd
I tried to flash the 4.23 bootloader from the second link, which is the JWR66V version, but still cannot flash it, because by device freezes and the "Flashing bootloader-grouper-4.23.img" of Nexus Root Toolkit doesnt do anything than being stuck.
edit:
Ok , I managed to get my recovery back via fastboot.exe via "fastboot flash recovery recoveryname.img"
I managed to flash normal custom roms via fastboot and adb sideload, but I cannot change the bootloader from the bricked 4.23 one to the one mentioned in the topics which should be a working one from the nexus 7 JWR66V build.
I always get the error
Code:
sending 'bootloader' (2100 KB).
OKAY [ 0.333s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
Any ideas?
The Unified Android Toolkit seems to overwrite the broken bootloader easily and after a few attempts of trying to write the factory image with the Unified Android Toolkit and trying out different usb slots, because I often got the error "Unknown Device" and thus Windows 7 could not install any drivers, it worked out.
Thanks
Greetings everyone, I just got a new XT1640. I installed on it the ATHENE_NPJS25.93-14-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml ROM from here. Went to motorola's site and unlocked the phone. But I still can't flash TWRP.
this is what happens:
Code:
fastboot flash boot twrp-3.0.2-0-athene.img
target reported max download size of 536870912 bytes
sending 'boot' (12496 KB)...
OKAY [ 0.435s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.186s]
finished. total time: 0.621s
I tried versions 3.1.1, 3.1.0 and 3.0.2 , all from the twrp site. Any ideas?
@yohanleafheart
Why do you want to brick your device ?
Check the command that you are entering, "BOOT" ???? That's "RECOVERY"
write command: fastboot flash recovery xyz.img
(Refer any Recovery or flashing thread)
EDIT:
When you used "fastboot flash boot twrp.img"
you got OKAY at last,
That means you flashed Recovery into Boot/kernel !!
If you face any kernel related problem on startup, then you will need to get original Boot.img and flash it...
Haha hey bro be careful while using commands .. u gonna poision your phone
In addition to ____Mdd's reply about TWRP being flashed to your boot (i.e. kernel!) partition, which isn't good...
The 'Image not signed or corrupt' error is normal because TWRP isn't cryptographically signed, so the bootloader reports as so. Normally, if you see [OKAY], the flash has succeeded (though in your case it's succeeded flashing to the wrong partition...) and you'd boot to recovery to ensure TWRP is not overwritten by the stock recovery (after which you can boot as normal).
If you need a stock kernel, you can pull the boot.img from the stock ROM you have and flash that to the boot partition or find the stock kernels here https://forum.xda-developers.com/showpost.php?p=72378739&postcount=262
Hopefully your device is working!
Gaaaaaaaaah didn't realize I was flashing to the wrong partition. Zomfg.
It didn't brick, i reverted to the stock before booting and relock the bootloader. I don't want the stock, I want to flash loa (did this on my s5 normally)
The problem is that even using the right command, it says that it is not signed, and wglhen I reboot in Dev mode it still won't boot on TWRP. It goes back to fastboot.
Any ideas?
I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks
unknown_geek said:
I had previously rooted my Moto G4 Plus and used multiple custom ROMs before switching back to Stock firmware.
Now, I'm unable to flash TWRP on my device. Any attempts to flash TWRP ends up with the following error:
Code:
reboot bootloader
mfastboot flash recovery twrp.img
target max-sparse-size: 256MB
sending 'recovery' (12530 KB)...
OKAY [ 0.406s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.203s]
finished. total time: 0.608s
Any further tries to reboot via adb commands results in the following:
Code:
adb reboot recovery
error: device not found
adb reboot
error: device not found
adb reboot bootloader
error: device not found
The device says the bootloader is unlocked while rebooting. the ID field shows 'bad key'(I feel this is weird).
Can someone please help me with this?
Thanks
Click to expand...
Click to collapse
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.
1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A
echo92 said:
1) That TWRP message of 'Image not signed or corrupt' is normal, since the TWRP custom recovery is not signed. After you see the [OKAY], reboot to recovery directly to fix the TWRP, else the stock recovery will overwrite it. Afterwards, you can boot as normal.
2)If you're still in the bootloader on your device, adb commands do not work - you need to use fastboot commands, or use your device volume keys to select 'Start' (to boot to system) or 'Recovery mode' (to boot to recovery) and press the power key to select. Of course, in this case, after flashing TWRP, you'll want to select 'Recovery Mode' in your bootloader and press the power key. This should then boot into TWRP.
If you find yourself in the bootloader in the future, then 'fastboot reboot' or 'fastboot continue' (both commands to be used without quotes, in the ADB terminal) may get your device rebooting to system.
3)ID Bad key is normal with an unlocked bootloader, on subsequent boots this may change to ID:N/A
Click to expand...
Click to collapse
Hi @echo92,
Thanks for pointing out what I was doing wrong. I now realize that the TWRP recovery was being overwritten by stock recovery and I didn't know adb commands don't work while still in bootloader mode.
I did boot into recovery mode from the bootloader (using the volume buttons from the phone) and it worked.
And the ID: bad key is also gone and now it shows ID: N/A.
Thanks again for your help!
Regards
____Mdd said:
It has got flashed correctly as you got "OKAY" at end of command. Try to boot into recovery and tell us what happens.
Click to expand...
Click to collapse
Hi @____Mdd,
I rebooted into recovery right after flashing TWRP and it worked fine. Now, I'm able to boot into TWRP recovery.
Thanks for your response.
Regards.
Im Facing this issue while flashing TWRP
C:\adb>fastboot flash recovery twrp.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (12644 KB) OKAY [ 0.422s]
Writing 'recovery' (bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
vaibhavhr2010 said:
Im Facing this issue while flashing TWRP
Click to expand...
Click to collapse
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?
echo92 said:
Pre flash validation errors suggest that your bootloader is locked (i.e. you have not unlocked your bootloader, or it has been re locked). Can you confirm your bootloader is unlocked, e.g. if there is a warning screen on boot saying your device is unlocked?
Click to expand...
Click to collapse
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3
vaibhavhr2010 said:
Thank You for the Reply!
Yes I have already unlocked the Bootloader.
The device status in Bootloader shows Device is Unlocked, Status Code: 3
Click to expand...
Click to collapse
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?
echo92 said:
Thanks, what device are you trying to flash TWRP to and which TWRP image are you using?
Click to expand...
Click to collapse
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.
vaibhavhr2010 said:
I'm Flashing my Moto G4 using the twrp-3.0.2-3-titan.
Click to expand...
Click to collapse
That TWRP won't work, if it's for Titan. The codename for Moto G4/plus is athene, only TWRP images specifying athene in their name will work.
https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206 or https://eu.dl.twrp.me/athene/ give these a try instead