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
Related
Hi,
I recently got a nexus 10, and started working on rooting. I have unlocked it, installed CWM recovery and booted it twice. I have not rooted it yet. Now I realized, that everytime I entered the CWM recovery mode, it automatically reboots back into recovery or normal boot in about 30 seconds or so. (this is not the main problem!)
But one booting up second time, I got a notification of sytem update for 4.2 jellybean (please note initially the device was on 4.2 JB JVP15P), I clicked on install, it booted into CWM recovery, but then it failed to continue with installation, as it complained about authentication failure for the zip fle or something of that sort. So I chose to boot the device without installing the update, now it entered a boot loop. I have tried erasing cache and userdata (both using fastboot commandline, and options in the CWM - in the 30 secs I get). It did not work.
After trying it for a few times, I tried restoring some backups I had made. Initially it complained about MD5 mismatch, and then later on it complained about unable to mount cache/* and unable to mount sdcard.
I have read around and the universal solution seems to be to restore stock images. Is that the solution for me as well?
Any help would be greatly appreciated, and I am noob in this area, so pardon me if I act like one.
cheers,
brickin
I'd like to know part of the answer to this as well. The tab is running fine and TWRP works fine, but CWM constantly reboots and I have the same mounting problems within both CWM and TWRP. I've tried flashing stock image and recovery but it's made no difference.
IIRC, the newest CWM has an issue with devices that allow multiple users (aka: N7 and N10). Flash TWRP and don't look back.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 06:07 AM ---------- Previous post was at 06:05 AM ----------
Also, TWRP supports USB OTG while CWM doesn't.
Sent from my Galaxy Nexus using Tapatalk 2
I was having a similar issue with cwm. This explains everything.
Blueback22 said:
IIRC, the newest CWM has an issue with devices that allow multiple users (aka: N7 and N10). Flash TWRP and don't look back.
Sent from my Galaxy Nexus using Tapatalk 2
---------- Post added at 06:07 AM ---------- Previous post was at 06:05 AM ----------
Also, TWRP supports USB OTG while CWM doesn't.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Hi Blueback22,
Thanks a lot for your reply.
Would flashing TWRP solve everything? And also is it ok to flash TWRP now, would it be able to restore the backups I have made using CWM?
Do I need to uninstall or remove the CWM recovery image that has alreday been flashed? or will TWRP image overwrite it?
How do I solve the bootloop issue?
I am unable to get a stock image for JB version: JVP15P. Do you know where I can find the factory image for that?
OR is it ok for me to flash the JOP40C image? Would it cause any problems - (like would it cry saying checksum mismatch or something like that)?
Also, what is the solution for unable to mount sdcard problem?
Sorry for asking so many questions, but I do not wish to brick my device, hence I wish to understand what I am going to do, and ensure that it is not going to harm my device.
Your replies to this post is and will be deeply appreciated.
Thanks,
brickin
brickin said:
Hi Blueback22,
Thanks a lot for your reply.
Would flashing TWRP solve everything? And also is it ok to flash TWRP now, would it be able to restore the backups I have made using CWM?
Do I need to uninstall or remove the CWM recovery image that has alreday been flashed? or will TWRP image overwrite it?
How do I solve the bootloop issue?
I am unable to get a stock image for JB version: JVP15P. Do you know where I can find the factory image for that?
OR is it ok for me to flash the JOP40C image? Would it cause any problems - (like would it cry saying checksum mismatch or something like that)?
Also, what is the solution for unable to mount sdcard problem?
Sorry for asking so many questions, but I do not wish to brick my device, hence I wish to understand what I am going to do, and ensure that it is not going to harm my device.
Your replies to this post is and will be deeply appreciated.
Thanks,
brickin
Click to expand...
Click to collapse
If I were you, I would use WugFresh's toolkit to flash back to stock. Then I'd flash TWRP and start from scratch.
I don't know if TWRP will fix your issue all together, but I do remember hearing that there's an issue with CWM on the N10 right now.
Your CWM backups won't work on TWRP IIRC.
Here is where you can get stock images:
https://developers.google.com/android/nexus/images
Sent from my Galaxy Nexus using Tapatalk 2
Hi Blueback22,
Thanks for the help. I was able to fix the problem.
Here are the questions I had and the answers I found, please correct me if I am wrong.
1. My JB version is JVP15P, is it ok to flash JOP40C stock recovery image?
ans: yes
2. Does TWRP work perfectly with nexus 10?
ans: Atleast in my case it did, I was able to root my device, and was also able to take backups.
3. a. CWM complains E: Can't mound /sdcard !
b. CWM Keeps restarting within 30 secs or so !
c. My device is stuck in bootloop !
ans: First, try to wipe your cache, and userdata and reboot. If it does not solve, then flash stock factory image for your device and flash TWRP recovery image.
4. CWM complains E: can't mount /cache/*
ans: Wipe your cache, userdata and reboot.
Reiterating blueback22's point:
DO NOT USE CWM WITH NEXUS 10. USE TWRP INSTEAD.
Cheers,
brickin
BRICKED: OLd bootloader version wont update
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.168s]
writing 'bootloader'...
OKAY [ 0.143s]
finished. total time: 0.318s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.009s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
OKAY [ 0.145s]
finished. total time: 0.323s
C:\android-sdk\platform-tools>fastboot -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ09
Baseband Version.....: no modem
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ09'.
Update requires 'MANTALJ12'.
finished. total time: 0.063s
I tried one click root and wug's root kits, but there wasn't any luck in returning to stock and stuck in older bootloader without the possibility of returning to stock. I am stuck in Clockworkmod v6.0.1.9 loops. Tried to search the forum but I couldnt find anything.
ginsboon said:
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.168s]
writing 'bootloader'...
OKAY [ 0.143s]
finished. total time: 0.318s
C:\android-sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.009s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-manta-mantalj12.img
sending 'bootloader' (1280 KB)...
OKAY [ 0.170s]
writing 'bootloader'...
OKAY [ 0.145s]
finished. total time: 0.323s
C:\android-sdk\platform-tools>fastboot -w update image-mantaray-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MANTALJ09
Baseband Version.....: no modem
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
FAILED
Device version-bootloader is 'MANTALJ09'.
Update requires 'MANTALJ12'.
finished. total time: 0.063s
I tried one click root and wug's root kits, but there wasn't any luck in returning to stock and stuck in older bootloader without the possibility of returning to stock. I am stuck in Clockworkmod v6.0.1.9 loops. Tried to search the forum but I couldnt find anything.
Click to expand...
Click to collapse
Can you get into the boot loader and flash TWRP to see if that fixes it?
Sent from my Galaxy Nexus using Tapatalk 2
ginsboon said:
returning to stock. I am stuck in Clockworkmod v6.0.1.9 loops. Tried to search the forum but I couldnt find anything.
Click to expand...
Click to collapse
Why don't you try cwm 6.0.2.3? I also loaded 6.0.1.9 and it would reboot in about 30sec time. After going to the latest, cwm has been stable. No more random reboots.
Link to download the latest version...
http://www.clockworkmod.com/rommanager
cowabunga said:
Why don't you try cwm 6.0.2.3? I also loaded 6.0.1.9 and it would reboot in about 30sec time.
I tried to flash cwm 6.0.2.3 and twrp but failed. Still searching for some clues.
Click to expand...
Click to collapse
For OP and other N10 users with stock 4.2 JB Build JVP15P experience:
Is it possible to use the available toolkits (Wug's or mskip's) to unlock the bootloader and root a N10 with the configuration above? Both toolkits ask for Build JOP40C. I've searched the developer forum for this build and found nothing. Thanks!
Hi, I had a nexus 7 with rooted stock firmware and modified kernel and I wanted to return to stock firmware. Usually I use Nexus Root Toolkit without problem for this type of things but, after I've flashed for the first time the factory image nakasi 4.4.4 (KTU84P), now my nexus crashes on the black screen with the Google's logo. I've tried to reflash other stock firmwares but nothing is changed; flashing through fastboot the operation crashes during the sending of system.img. Could anyone help me? Maybe the nexus must be repartitioned?
PS: sorry for my bad EnglishXP
marsece said:
Hi, I had a nexus 7 with rooted stock firmware and modified kernel and I wanted to return to stock firmware. Usually I use Nexus Root Toolkit without problem for this type of things but, after I've flashed for the first time the factory image nakasi 4.4.4 (KTU84P), now my nexus crashes on the black screen with the Google's logo. I've tried to reflash other stock firmwares but nothing is changed; flashing through fastboot the operation crashes during the sending of system.img. Could anyone help me? Maybe the nexus must be repartitioned?
PS: sorry for my bad EnglishXP
Click to expand...
Click to collapse
Have you tried using a different usb port on your pc?
I've tried to use another pc and the situation is the same. Furthermore, trying to flash in different way the stock firmwares, now I can't flash any partitions from a stock image...maybe has my nexus a hardware fault?
Also I've read this http://forum.xda-developers.com/showthread.php?t=2573015 and followed its instructions, but without results.
For example, if I try to flash a bootloader this is the situation
C:\Program Files (x86)\WugFresh Development\data>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.568s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.710s
and on the nexus 7 appears "signature mismatch".
and the cases of other partitions of a stock firmware are similar
marsece said:
For example, if I try to flash a bootloader this is the situation
C:\Program Files (x86)\WugFresh Development\data>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.568s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.710s
and on the nexus 7 appears "signature mismatch".
and the cases of other partitions of a stock firmware are similar
Click to expand...
Click to collapse
Hello,
did you have another usb cable by chance?
I had an issue once with one of mine that also prevented to use adb.
Just an idea,
Nix
Nixblicker said:
Hello,
did you have another usb cable by chance?
I had an issue once with one of mine that also prevented to use adb.
Just an idea,
Nix
Click to expand...
Click to collapse
I've used the original nexus cable without problem until now, so I didn't think to try another cable. Thank you very much for the advice, now my nexus is returned to work!
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.
Apologizes in advance if I sound like a noob. I have searched and searched and am at my wits' end. Wondering if anyone can help me with a particular Nexus 7 problem I have. I can't update the bootloader of my pre-production Nexus 7 (Nakasi Wi-Fi) from version 3.24 to 4.23.
When I initially unboxed and turned on the Nexus 7 I had just been given I found out that it's a developer model running Jellybean with bootloader version 3.24.
At first tried all of the usual ways of updating the OS. Unfortunately none of the ways I tried, via Android Studio, Minimal ADB and Fastboot, and the Nexus Root Toolkit, worked.
Here is the error report that I received from Nexus Root Toolkit when I attempted a straight update to 5.1.1:
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is '3.24'.
Update requires '4.23'.
I read that if I edited android-info.txt file to read "require board=grouper require version-bootloader=3.24", I would be able to flash 4.1.2. It worked, and after a few hours of constantly updating OTA I ended up with a *slow* Nexus 7 running 5.1.1.
I decided to start over and try to update the bootloader again. I know that in some builds there were some problems with bootloader version 4.23 but what I pulled was the latest off of Android's website (developers . google . com / android / nexus / images). That didn't work. I tried to flash it through a terminal. I tried to flash it through the Nexus Root Toolkit. I tried different USB ports 2.0 and 3.0 (which shouldn't matter since I was able to update just the OS initially) and that didn't work.
The log in the terminal says:
FAILED (remote: (InvalidState))
The *extremely* small text on the Nexus screen says:
signature mismatch
failed to process command flash bootloader error (ox8)
I think that if I just update the bootloader version from 3.24 to 4.23 I'll be find. I'll be able to update straight to 5.1.1 and have a cleaner install. Unfortunately I can't find any way of doing so online. Any and all help is appreciated.
Thanks!
chingondomino said:
Apologizes in advance if I sound like a noob. I have searched and searched and am at my wits' end. Wondering if anyone can help me with a particular Nexus 7 problem I have. I can't update the bootloader of my pre-production Nexus 7 (Nakasi Wi-Fi) from version 3.24 to 4.23.
When I initially unboxed and turned on the Nexus 7 I had just been given I found out that it's a developer model running Jellybean with bootloader version 3.24.
At first tried all of the usual ways of updating the OS. Unfortunately none of the ways I tried, via Android Studio, Minimal ADB and Fastboot, and the Nexus Root Toolkit, worked.
Here is the error report that I received from Nexus Root Toolkit when I attempted a straight update to 5.1.1:
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is '3.24'.
Update requires '4.23'.
I read that if I edited android-info.txt file to read "require board=grouper require version-bootloader=3.24", I would be able to flash 4.1.2. It worked, and after a few hours of constantly updating OTA I ended up with a *slow* Nexus 7 running 5.1.1.
I decided to start over and try to update the bootloader again. I know that in some builds there were some problems with bootloader version 4.23 but what I pulled was the latest off of Android's website (developers . google . com / android / nexus / images). That didn't work. I tried to flash it through a terminal. I tried to flash it through the Nexus Root Toolkit. I tried different USB ports 2.0 and 3.0 (which shouldn't matter since I was able to update just the OS initially) and that didn't work.
The log in the terminal says:
FAILED (remote: (InvalidState))
The *extremely* small text on the Nexus screen says:
signature mismatch
failed to process command flash bootloader error (ox8)
I think that if I just update the bootloader version from 3.24 to 4.23 I'll be find. I'll be able to update straight to 5.1.1 and have a cleaner install. Unfortunately I can't find any way of doing so online. Any and all help is appreciated.
Thanks!
Click to expand...
Click to collapse
Fastboot isn't working? I'd extract the factory image and flash the files individually with fastboot.
Example:
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
fastboot reboot bootloader
fastboot flash system system.img
fastboot flash boot boot.img
And so on.
Nexus 7 (grouper) doesn't boot - Bootloader says "FAILED (remote: (FileWriteFailed))"
Hi,
My Nexus 7 (grouper) won't boot Android anymore. It automatically boots into the bootloader and when I select 'Start' or 'Recovery Mode' it just says "Booting failed".
When I try to flash a new recovery Image over fastboot I get the following Output:
[[email protected] Downloads]$ sudo fastboot flash recovery twrp-2.8.7.0-grouper.img
sending 'recovery' (11850 KB)...
OKAY [ 1.409s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 1.441s
Click to expand...
Click to collapse
It's the same, when I try to flash anything else. So I have no chance to flash a Stock-Image. I also get the same error when I try to format a partition. I'm pretty much out of ideas now. Can anybdoy help me?
yeah this same thing kept happening to me (I have no idea why) Once you get into the bootloader make sure your device shows up IE fastboot devices, then flash bootloader, then fastboot reboot-bootloader then between each succeding flash use the volume buttons to select reboot bootloader on the device. I had to flash individual partitions it would'nt do a -w update, so flash system, then reboot bootloader on device, then flash, then reboot bootloader, ect
Also booting into Android takes a bit so be patient, like 10/15 min. Maybe there's an easier way but after screwng around with it for an hour this is the only way I could get 5.1.1 on it.
productofusa said:
yeah this same thing kept happening to me (I have no idea why) Once you get into the bootloader make sure your device shows up IE fastboot devices, then flash bootloader, then fastboot reboot-bootloader then between each succeding flash use the volume buttons to select reboot bootloader on the device. I had to flash individual partitions it would'nt do a -w update, so flash system, then reboot bootloader on device, then flash, then reboot bootloader, ect
Also booting into Android takes a bit so be patient, like 10/15 min. Maybe there's an easier way but after screwng around with it for an hour this is the only way I could get 5.1.1 on it.
Click to expand...
Click to collapse
When I try to flash the bootloader I get:
[[email protected] Downloads]$ sudo fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.403s
Click to expand...
Click to collapse
And when flashing other partitions it says "FAILED (remote: (FileWriteFailed))".
Something seems to be really screwed up with my storage. Is there a way to repartition the device from fastboot? Maybe that would be help.
I'm willing to try out everything, by now.
Is it possible the files your trying to flash are somehow corrupt? try downloading again. My problem was fastboot kept crashing, not really sure what you got going on.
I will say that i've just finished flashing nexus 6,7,7, and 9 and for some reason the nexus 7 (2012) was a real pain in the butt, didn't have issues with any of the others.
Maybe someone else with another idea will chime in, good luck!
productofusa said:
Is it possible the files your trying to flash are somehow corrupt? try downloading again. My problem was fastboot kept crashing, not really sure what you got going on.
I will say that i've just finished flashing nexus 6,7,7, and 9 and for some reason the nexus 7 (2012) was a real pain in the butt, didn't have issues with any of the others.
Maybe someone else with another idea will chime in, good luck!
Click to expand...
Click to collapse
I already downloaded them multiple times. And even if they are corrupt, formatting the partitions should still work. I'm guessing on corrupt storage now, as I can't find any other explanation. Maybe I can find a cheap Motherboard somewhere on the internet. Thanks, anyways