Database Users

[Q]InvalidState on bootloader for Nexus 7 (2012) Wifi Lollipop flash

When I obtained the Lollipop image for the 2012 Wifi Nexus 7 (nakasi-lrx21p-factory-93daa4d3.tgz), I didn't want to lose my user data nor all the files on my media partition (TiBu backups, etc), so I unzipped all the images and flashed them manually so that it wouldn't erase the userdata partition.
First, I attempt to flash the bootloader, but using stupid auto-complete in the command window, I accidentally flashed boot.img instead of bootloader-grouper-4.23.img to the bootloader partition. I immediately saw what I did and panicked. I didn't reboot and then I tried to flash bootloader-grouper-4.23.img. Everytime that happens, this is what I get:
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.433s
rebooting into bootloader...
I decided to just go ahead and continue flashing everything else and it all seemed to be fine. I booted into Lollipop without any issues.
However, I was having some performance issues, so I decided to backup my media partition and go ahead and reflash it, having it wipe everything. This time, I used the enclosed flash-all.bat script and I noticed I still get the "InvalidState" when attempting to write to the bootloader.
When I flashed the boot.img to the bootloader partition, did I screw something up? Or, is there something wrong with the image Google provided and it's nothing to worry about?
I was able to install TWRP and root it, so obviously, there isn't that much of an issue, but I'm just wondering if everyone else is getting this message?
I am using the correct factory image from Google: nakasi-lrx21p-factory-93daa4d3.tgz
Thanks for any help with this. I guess I don't have anything to worry about since it flashes everything else fine and boots up, but I would like to make sure.

iBolski said:
When I obtained the Lollipop image for the 2012 Wifi Nexus 7 (nakasi-lrx21p-factory-93daa4d3.tgz), I didn't want to lose my user data nor all the files on my media partition (TiBu backups, etc), so I unzipped all the images and flashed them manually so that it wouldn't erase the userdata partition.
First, I attempt to flash the bootloader, but using stupid auto-complete in the command window, I accidentally flashed boot.img instead of bootloader-grouper-4.23.img to the bootloader partition. I immediately saw what I did and panicked. I didn't reboot and then I tried to flash bootloader-grouper-4.23.img. Everytime that happens, this is what I get:
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.433s
rebooting into bootloader...
I decided to just go ahead and continue flashing everything else and it all seemed to be fine. I booted into Lollipop without any issues.
However, I was having some performance issues, so I decided to backup my media partition and go ahead and reflash it, having it wipe everything. This time, I used the enclosed flash-all.bat script and I noticed I still get the "InvalidState" when attempting to write to the bootloader.
When I flashed the boot.img to the bootloader partition, did I screw something up? Or, is there something wrong with the image Google provided and it's nothing to worry about?
I was able to install TWRP and root it, so obviously, there isn't that much of an issue, but I'm just wondering if everyone else is getting this message?
I am using the correct factory image from Google: nakasi-lrx21p-factory-93daa4d3.tgz
Thanks for any help with this. I guess I don't have anything to worry about since it flashes everything else fine and boots up, but I would like to make sure.
Click to expand...
Click to collapse
I got the same 'Invalid State' error that you did although I didn't accidentally flash anything else.. I just ran through the ./flash-all.sh script and it just straightup failed while trying to flash the bootloader.. and then it just barreled ahead and deleted my recovery partition + everything else haha. So now I'm in a state where I can't boot at all, not even into recovery @[email protected]
Sorry, that was no help haha, just wanted to let you know that I've seen the Invalid State error as well.

I had that when I did a fastboot install of lollipop. Just ignored it and moved on as version was identical anyway

I had this same problem. What I ended up doing was downloading the Nexus Root Kit and then using that to flash the individual files and it worked fine for me. Though, now I got to figure out how to get the system to know there are actually 16GB of storage and not 6GB.
Edit: I found out what needed to be done. I just needed to do a factory reset.

This has been a known problem on Grouper for nearly a year now.
http://forum.xda-developers.com/showthread.php?t=2573015

SteveRiley said:
This has been a known problem on Grouper for nearly a year now.
http://forum.xda-developers.com/showthread.php?t=2573015
Click to expand...
Click to collapse
Thanks. I knew about that one on previous releases. I just wasn't sure if it was the same issue.
Nice to know it's nothing to worry about, but I just about had a heart attack when I realized that I flashed boot.img to the bootloader (or at least tried) and I wasn't sure if I had just perma-bricked my Nexus.
Thank goodness it didn't. I'm sure there are some safeguards from allowing that from happening and it's probably more it I were to flash something else to the boot partition that would cause an issue.
Anyways, thanks for the reminder.

iBolski said:
Nice to know it's nothing to worry about, but I just about had a heart attack when I realized that I flashed boot.img to the bootloader (or at least tried) and I wasn't sure if I had just perma-bricked my Nexus.
Thank goodness it didn't. I'm sure there are some safeguards from allowing that from happening and it's probably more it I were to flash something else to the boot partition that would cause an issue.
Click to expand...
Click to collapse
Well, when I first saw the error about the failed flash to the bootloader partition, I actually did flash the bootloader image to the boot partition. That appeared to work just fine -- no error, and the process finished with a success message. This would have most certainly rendered the OS unbootable, but it wouldn't have bricked the device. That's when I reminded myself that "boot" is not equivalent to "bootloader"! So I reflashed the correct bits to the boot partition.

Zenfone 2 ZE551ML not booting up

Please help, I've made the mistake of applying the marshmallow update file, while using the TWRP recovery. It was stuck on writing splashscreen, for around 2hrs. I thought about restarting the device to restore a previous backup image. That is when the screen turned off for good. No matter what i tried, I could not boot into recovery, or even fastboot. I've tried the key combinations, adb, but nothing seems to bring this up to life. Please tell me how to flash the stock zip, I don't care about the data in the phone at this point.

You probably have the same problem I have. Fixed it with this http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

dcduartee said:
You probably have the same problem I have. Fixed it with this http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
I did have the same issue,Thank you. But in the later steps, when the phone boots into fastboot, I cannot use any flash commands. It always shows FAILED (remote: flash_cmds error!). Any ideas?

Can you boot into recovery now? after doing those steps I still had twrp installed and used the recovery.img from the stock rom and then booted back to stock recovery and applied update via adb

dcduartee said:
Can you boot into recovery now? after doing those steps I still had twrp installed and used the recovery.img from the stock rom and then booted back to stock recovery and applied update via adb
Click to expand...
Click to collapse
It did work after another xFSTK download, don't know why the error was caused in the first place. Flashed TWRP and restored a previous backup.

KuntalBiswas said:
It did work after another xFSTK download, don't know why the error was caused in the first place. Flashed TWRP and restored a previous backup.
Click to expand...
Click to collapse
Happened the same to me. Still don't know why it happened xD

Screen stuck on preparing to start.. starting app.. after flashing crdroid 6.0.1

I had rooted my phone by unlocking the bootloader using adb fastboot method, then flashing the TWRP revocery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that..
but while playing a game the phone automatically rebooted and ever since have been stuck on Preparing to start.. Starting apps..
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls.
Any suggestions what I should do now? I have tried doing a factory reset from recovery but the problem persists.

khushboop said:
I had rooted my phone by unlocking the bootloader using adb fastboot method, then flashing the TWRP revocery V2.8.7.0, and then flashing superSU v2.46.
After rebooting my yureka plus, and going to recovery it started cynogen recovery only, even though update cynogen recovery option was disabled.
So I flashed TWRP again and without rebooting again, just flashed crDroidAndroid-6.0.1-20160827-tomato.zip and GApps zip file from internal memory. The phone rebooted and worked fine after that..
but while playing a game the phone automatically rebooted and ever since have been stuck on Preparing to start.. Starting apps..
I had disabled the developer options because I thought it was working fine.
The phone is working behind the preparing to start screen.. I can hear the message notification and caller ringtone when someone messages or calls.
Any suggestions what I should do now? I have tried doing a factory reset from recovery but the problem persists.
Click to expand...
Click to collapse
Try flashing it with stock rom or simple wipe the whole system and cache from twrp from advance wipe option ( but backup first ) and again flash the custom rom u used previously.

sk.shehbaz said:
Try flashing it with stock rom or simple wipe the whole system and cache from twrp from advance wipe option ( but backup first ) and again flash the custom rom u used previously.
Click to expand...
Click to collapse
It still opens in cyanogen recovery only, and there is no option for wiping dalvik cache or system. Since the usb debugging is of,f I cannot used cmd to flash twrp recovery again. By the way I still don't understand why twrp recovery is not loading.

khushboop said:
It still opens in cyanogen recovery only, and there is no option for wiping dalvik cache or system. Since the usb debugging is of,f I cannot used cmd to flash twrp recovery again. By the way I still don't understand why twrp recovery is not loading.
Click to expand...
Click to collapse
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/

sk.shehbaz said:
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Click to expand...
Click to collapse
Phone's hard bricked now.. even though I downloaded the flashing tools for lollipop from YUPlayGod's github page.

khushboop said:
Phone's hard bricked now.. even though I downloaded the flashing tools for lollipop from YUPlayGod's github page.
Click to expand...
Click to collapse
I still have no idea why it got bricked. So after searching on google and youtube I came across this: https://androidmtk.com/download-yu-stock-rom-for-all-models . I followed the steps and now KitKat is running except launcher is not working, instead play store open's every time I try to go to home screen. So tried the nova launcher but that still doesn't work with home button, have to open through playstore->my apps, every time. But rest is working.

sk.shehbaz said:
Get into fastboot and flash the stock rom via fastboot method.
I hope this guide can help u out
http://www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Click to expand...
Click to collapse
dude!! i tried the above method and thankfully my phone is working now the only major problem now is whatsapp is not opening...when clicked opens for 0.01 sec and returns back to previous screen (flashes) ....please somebody help me with this. Anybody can help me, Thanks in Advance.

Bricked but still have twrp

Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.

almost looks like it can't mount the system

IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.

I have no idea how it happened but I got my system mounted again that was my problem. I'm back.
thread can be closed

keeganjk said:
IDK, maybe a broken download. I'd try to restore a backup if you have one, if not Wipe > Factory Reset. If it still doesn't boot after 20 minutes, refer to this thread: https://forums.oneplus.net/threads/i-have-to-go-back-to-oxygen-os.649947/#post-16907420. Basically, download the OOS ROM onto your computer and use an ADB/USB Sideload in TWRP recovery (you can flash Oxygen Recovery from TWRP if TWRP doesn't work) to install it. May take a while to boot.
Click to expand...
Click to collapse
thanks for the reply mate

snipeez1987 said:
thanks for the reply mate
Click to expand...
Click to collapse
yw

snipeez1987 said:
Hey guys,
so I tried flashing Omni 8.0 rom and I was stuck at the boot screen. so I went back into twrp tried to reflash still nothing. I flashed a new version of twrp the one that can use multirom and it erased all my data. I flashed back the twrp I started with and now I can not sideload the full OTA zip to get back to stock. It says "cannot load one.zip" which is what I have it labeled as. I tried to download the recovery tool and I can't seem to figure out how to get the driver to work so it will see me on my comm port. Does anyone have any ideas on what to do or what happened? I'm stuck in twrp.
Click to expand...
Click to collapse
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.

ipredatorv said:
Easy fix for "Cannot load xxx.rom": you have to patch the adb.exe with a large address awareness program. Google it, I found one in another XDA thread.
Reason: the ROM filesize is too large. For small ROMs (like custom ROMs) adb would recognise it without any problems.
Click to expand...
Click to collapse
Awesome. I'll keep that in mind. I'm sure I'll mess it up again lol. Hopefully not though.

boot/twrp help

Been running twrp 3.2.1-r1 for a while now with resurrection remix on my Perry. Today it fraged itself, so I decided to try the new 3.2.3 twrp. After booting it, it seemed to flash without issue. Upon reboot, it wouldn't load. I flashed the 3.2.1 twrp I tried flashing the ROM, but the data partition wouldn't take it. I discovered that the partition size was 0. I fixed the partition size, and flashed the ROM. Everything seems to be fine, except booting. The phone defaults to twrp instead of booting the ROM. I have to reboot to boot loader, the click start to get the ROM to load. Not critical, but VERY annoying. Any help resolving this is appreciated. Thanks
Tried the fastboot OEM fb_mode_clear command, which flashes, but no change. Tried the adb wipe /misc partition, which returns invalid file.

HigherStateD said:
Been running twrp 3.2.1-r1 for a while now with resurrection remix on my Perry. Today it fraged itself, so I decided to try the new 3.2.3 twrp. After booting it, it seemed to flash without issue. Upon reboot, it wouldn't load. I flashed the 3.2.1 twrp I tried flashing the ROM, but the data partition wouldn't take it. I discovered that the partition size was 0. I fixed the partition size, and flashed the ROM. Everything seems to be fine, except booting. The phone defaults to twrp instead of booting the ROM. I have to reboot to boot loader, the click start to get the ROM to load. Not critical, but VERY annoying. Any help resolving this is appreciated. Thanks
Tried the fastboot OEM fb_mode_clear command, which flashes, but no change. Tried the adb wipe /misc partition, which returns invalid file.
Click to expand...
Click to collapse
TW RP is not clearing the BCB correctly. The boot loader control block. I'll post the commands you need to fix it in a minute when I pull over. Driving right now
---------- Post added at 01:40 AM ---------- Previous post was at 01:37 AM ----------
This version of TWRP is not reading and clearing the bootloader control block (BCB). So, if you do a factory reset via Settings->Backup & Reset->Factory Data Reset, you'll be stuck in a TWRP bootloop.
The quick workaround is to reboot to bootloader, then proceed from there to Start. However, you'll need to do this *every* time until the BCB is cleared.
To clear the BCB manually, issue this command in TWRP terminal:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M

The quick workaround is to reboot to bootloader said:
Thanks for the reply. I tried the command to zero out misc, it returns misc not found, which is of, as I can clearly see the file in an ls file list.
Click to expand...
Click to collapse

Got it by CD to the dir misc is located then executing the following: dd if=/dev/zero of=misc
Could use some help flashing the latest twerp, but since no ROMs need the added 64 bit support, I don't see it as necessary yet.

HigherStateD said:
Got it by CD to the dir misc is located then executing the following: dd if=/dev/zero of=misc
Could use some help flashing the latest twerp, but since no ROMs need the added 64 bit support, I don't see it as necessary yet.
Click to expand...
Click to collapse
The old twrp has the same issue. Just go ahead and Flash the new one. It's just a problem that May come up when you format or if you do a factory reset

madbat99 said:
The old twrp has the same issue. Just go ahead and Flash the new one. It's just a problem that May come up when you format or if you do a factory reset
Click to expand...
Click to collapse
Tried flashing the new twrp from within the old one. I get a kernel error when trying to load after successful flash.

HigherStateD said:
Tried flashing the new twrp from within the old one. I get a kernel error when trying to load after successful flash.
Click to expand...
Click to collapse
Are you flashing it to the recovery partition? Try flashing it with Flashify. but it should work if you choose select install image in TWRP and select the recovery partition.

madbat99 said:
Are you flashing it to the recovery partition? Try flashing it with Flashify. but it should work if you choose select install image in TWRP and select the recovery partition.
Click to expand...
Click to collapse
Yes.. Phone boots fine. Only issue is with recovery. New twrp flashed either in twrp or fastboot generates kernel error. After flashing old twrp, recovery works fine

HigherStateD said:
Yes.. Phone boots fine. Only issue is with recovery. New twrp flashed either in twrp or fastboot generates kernel error. After flashing old twrp, recovery works fine
Click to expand...
Click to collapse
Which version of the E4 do you have?

madbat99 said:
Which version of the E4 do you have?
Click to expand...
Click to collapse
XT1765 by metro

HigherStateD said:
XT1765 by metro
Click to expand...
Click to collapse
I've seen other people with the Metro version and the T-Mobile one which have the same model number and it works fine for them. Don't know exactly why it's not working for you I sse you resized some partitions and had trouble clearing the BCB. So you may have done some other things that I don't know about. All I can say is that if the previous version was working you should stick with that one.

madbat99 said:
I've seen other people with the Metro version and the T-Mobile one which have the same model number and it works fine for them. Don't know exactly why it's not working for you I sse you resized some partitions and had trouble clearing the BCB. So you may have done some other things that I don't know about. All I can say is that if the previous version was working you should stick with that one.
Click to expand...
Click to collapse
I tried to flash the 3.2.3 after my system went into a boot loop for an unknown reason. I was able to eventually clear the BCB with a modified command in the twrp terminal. Is there a way of checking the size of the recovery partition? I'm thinking the added 4~MB of the 3.2.3 twrp might be causing an issue. Perhaps overrunning the size of the partition. Can't think of any other reason it wouldn't work.

HigherStateD said:
I tried to flash the 3.2.3 after my system went into a boot loop for an unknown reason. I was able to eventually clear the BCB with a modified command in the twrp terminal. Is there a way of checking the size of the recovery partition? I'm thinking the added 4~MB of the 3.2.3 twrp might be causing an issue. Perhaps overrunning the size of the partition. Can't think of any other reason it wouldn't work.
Click to expand...
Click to collapse
I flashed it on mine no problem. the recovery partition is bigger than it needs to be. Don't go messing around changing partition sizes or you're asking for trouble.