Related
Hi All
I have been researching for a few hours now and still could not find a valid solution to my problem.
I have read many post and the one below is the closest one to my problem but still not solution for this.
http://forum.xda-developers.com/showthread.php?t=1819005
This is what happen...
1) I used "Nexus 7 ToolKit" to (1) Unlock my Bootloader (2) Root (3) Flash Custom ROM
-->> I did not like the custom rom and felt I prefer the stock rom
2) downloaded "nakasi-jro03d-factory-e102ba72" and tried to restore using menu (9) in "Nexus 7 ToolKit"
-->> The process stuck at "Sending system (438656 KB)" for a long time and the device heated up so I decided to turn it off after about 1 hour wait time
-->> I got the same result after a few trials as well as with fastboot.exe
3) Now I tried using fastboot.exe and "Nexus 7 ToolKit" to flash the following "bootloader-grouper-3.34.img", "system.img" and "boot.img" one by one.
-->> I could flashed system.img and boot.img but I could not flash bootloader-grouper-3.34.img. it shows
Writing bootloader ... FAILED (remote: (InvalidState)
PS: I already wipe everything in the device and factory reset many times during these process.
Any recommendation would be much appreciated! Many Thanks
I tried using option 9 in "Nexus 7 ToolKit". It failed to flash bootloader, stuck at "Sending System" and there is RED font on N7 screen saying "Signature mismatch"
im going to pm you and maybe i could walk you through how to fix it.
1. I suggest not using a Toolkit
2. You'll need to install Android SDK (if you haven't already), download the USB driver and platform-tools, and put the tools in PATH
3. Try following this: http://forums.androidcentral.com/ne...ide-factory-image-restore-your-nexus-7-a.html
When following the above guide:
- Some commands will need changed slightly to deal with updated factory images (the filename is diffrerent for the fastboot -w update image-nakasi-jrn84d.zip command)
- Will wipe out everything on your device
- Will restore the latest factory-image straight from Google (in other words, stock kernel, stock ROM, stock recovery; stock everything)
espionage724 said:
1. I suggest not using a Toolkit
2. You'll need to install Android SDK (if you haven't already), download the USB driver and platform-tools,
3. Try following this:
When following the above guide:
- Some commands will need changed slightly to deal with updated factory images (the filename is diffrerent for the fastboot -w update image-nakasi-jrn84d.zip command)
- Will wipe out everything on your device
- Will restore the latest factory-image straight from Google (in other words, stock kernel, stock ROM, stock recovery; stock everything)
Click to expand...
Click to collapse
Thanks a lot. I already tried the link you provided but i got stuck when fastboot flash bootloader.
It stuck at "Sending bootloader (2072KB)"
chaichai84 said:
Thanks a lot. I already tried the link you provided but i got stuck when fastboot flash bootloader.
It stuck at "Sending bootloader (2072KB)"
Click to expand...
Click to collapse
Hmm, that is weird. You wiped out the bootloader (and everything else) first, and then tried copying it over?
Also, what ADB drivers are you using? Google's, ASUS's, or the toolkit's? Google's ADB driver I imagine would be more up-to-date, and probably the best choice, whereas ASUS's ADB driver I think is a modified, slightly outdated Google driver, and who know's what the toolkit is using.
espionage724 said:
Hmm, that is weird. You wiped out the bootloader (and everything else) first, and then tried copying it over?
Also, what ADB drivers are you using? Google's, ASUS's, or the toolkit's? Google's ADB driver I imagine would be more up-to-date, and probably the best choice, whereas ASUS's ADB driver I think is a modified, slightly outdated Google driver, and who know's what the toolkit is using.
Click to expand...
Click to collapse
OMG!! used Naked Universal Drive and follow your advice!! it works!! now its back to normal!! Thank you so much for helping out
PS: Little things like driver hurts so bad T_T
vegandroid said:
im going to pm you and maybe i could walk you through how to fix it.
Click to expand...
Click to collapse
Hey Thanks so much for your help Greatly appreciated on your offer
chaichai84 said:
OMG!! used Naked Universal Drive and follow your advice!! it works!! now its back to normal!! Thank you so much for helping out
PS: Little things like driver hurts so bad T_T
Click to expand...
Click to collapse
Could you please give a bit more details on your solution?
I'm having the same problem and can't flash Nexus 7 due to "InvalidState"/Signature Mismatch errors, while trying to reflash the stock JB (so now all partitions are deleted, including boot, but it still will not flash the stock 3.34 bootloader....
You mention some driver issue. I am currently using a mac with the latest SDK/ADB drivers... Is there any reason that by trying to do this on a windows machine it will make any difference?
Thanks!
In my case another micro USB cable worked in combination with Naked Universal Driver.
I don't know why. I flashed several times with the other cable.
Now my Nexus is working again. Thanks to the forum!!
just got the device today
followed the tutorial on unlocking the bootloader using the comebuy upgrade tool and checked the box for erasing "CEFS" and upgraded the firmware.
shell is now rooted.
however, rebooting to bootloader and trying any fastboot command gets "waiting for device"; fastboot devices shows nothing.
wth???
i'm an experienced dev / user, but i'm not going to be happy if this device i just got for developing purposes is locked down to where i can't do that.
also, trying to install the FFOS_to_android.zip that's widely available also does not pass signature verification in the recovery...
anyone got any ideas how i can unlock this thing???
stayboogy said:
just got the device today
followed the tutorial on unlocking the bootloader using the comebuy upgrade tool and checked the box for erasing "CEFS" and upgraded the firmware.
shell is now rooted.
however, rebooting to bootloader and trying any fastboot command gets "waiting for device"; fastboot devices shows nothing.
wth???
i'm an experienced dev / user, but i'm not going to be happy if this device i just got for developing purposes is locked down to where i can't do that.
also, trying to install the FFOS_to_android.zip that's widely available also does not pass signature verification in the recovery...
anyone got any ideas how i can unlock this thing???
Click to expand...
Click to collapse
If you google "fastboot command gets "waiting for device"; you may find your answer, most likely driver problem, I use Linux so drivers aren't necessary for me.
vampirefo said:
If you google "fastboot command gets "waiting for device"; you may find your answer, most likely driver problem, I use Linux so drivers aren't necessary for me.
Click to expand...
Click to collapse
i got it figured out. i use both linux and windows; mainly linux. in linux fastboot was acting the same way. it's not now. still have to use sudo though...
i had to dd your recovery, then rebooted to bootloader and ran fastboot oem unlock and it was done.
i was initially very frustrated though.
since i got that figured out i've been trying to port my touchnav recovery to the device but i've been getting an error when i try to fastboot boot it.
funny you replied cause i'm curious what you're using to build your recovery. are you just using the last jb repo or something newer?
stayboogy said:
i got it figured out. i use both linux and windows; mainly linux. in linux fastboot was acting the same way. it's not now. still have to use sudo though...
i had to dd your recovery, then rebooted to bootloader and ran fastboot oem unlock and it was done.
i was initially very frustrated though.
since i got that figured out i've been trying to port my touchnav recovery to the device but i've been getting an error when i try to fastboot boot it.
funny you replied cause i'm curious what you're using to build your recovery. are you just using the last jb repo or something newer?
Click to expand...
Click to collapse
In Linux you need to make user rules if you don't want to use sudo to fastboot, my .50 recovery is a straight pull from CyanogenMod's 4.4 tree.
other recovery straight pull from CyanogenMod's 4.3 tree
I tried installing CM with CM Installer for MAC ... until it got stuck in bootloop.
Using adb I pushed image, still bootloop.
Reset to factory, cleared partition, flushed dalvik cache, all the same.
adb commands seem to work since I can make the phone reset and so forth.
details:
mako 16 GB
HW version - rev_11
bootloader version MAKOZ30d
baseband M9615A-CEFWMAZM02.0.1701.02
signing - production
secure boot - enabled
lock state - unlocked
recovery mode is CWM v6.0.4.7 (assuming it got installed by the CM installer for MAC)
tried by hand to resuscitate with cm-11-20141008-SNAPSHOT-M11-mako.zip and cm-11-20141107-NIGHTLY-mako.zip using sideload to no avail - still bootloops despite numerous factory resets and cache partition wipes.
any ideas please?
thanks
This is what i use: http://forum.xda-developers.com/nex...olkit-wugs-nexus-root-toolkit-v1-8-2-t2015469
Has multiple options for going back to stock, rooting, and lots of other things.
TreatnHerRight said:
This is what i use: http://forum.xda-developers.com/nex...olkit-wugs-nexus-root-toolkit-v1-8-2-t2015469
Has multiple options for going back to stock, rooting, and lots of other things.
Click to expand...
Click to collapse
That looks great ... and uses Windows only
I can boot Windows under VMWare Fusion on my MAC however not 100% sure if that would work within that environment as I need to do some USB passthrough.
Thanks for the pointer though.
ilmoomino said:
I tried installing CM with CM Installer for MAC ... until it got stuck in bootloop.
Using adb I pushed image, still bootloop.
Reset to factory, cleared partition, flushed dalvik cache, all the same.
adb commands seem to work since I can make the phone reset and so forth.
details:
mako 16 GB
HW version - rev_11
bootloader version MAKOZ30d
baseband M9615A-CEFWMAZM02.0.1701.02
signing - production
secure boot - enabled
lock state - unlocked
recovery mode is CWM v6.0.4.7 (assuming it got installed by the CM installer for MAC)
tried by hand to resuscitate with cm-11-20141008-SNAPSHOT-M11-mako.zip and cm-11-20141107-NIGHTLY-mako.zip using sideload to no avail - still bootloops despite numerous factory resets and cache partition wipes.
any ideas please?
thanks
Click to expand...
Click to collapse
Honestly, when I get into these situations I just flash the stock images and use that as a starting point. (I'm guessing your recovery is still working fine, given what you've said, so you can pull that out of the zip it sends so it doesn't write over it)
My approach, however, is usually, "damn, I messed up, let's go back to a known good point and try again" though, so keep that in mind if you decide to follow this path.
nic0lette said:
Honestly, when I get into these situations I just flash the stock images and use that as a starting point. (I'm guessing your recovery is still working fine, given what you've said, so you can pull that out of the zip it sends so it doesn't write over it)
My approach, however, is usually, "damn, I messed up, let's go back to a known good point and try again" though, so keep that in mind if you decide to follow this path.
Click to expand...
Click to collapse
That didn't work either (the restore to stock).
The USB passthrough on VMWare fusion works like a charm, ADB sees the device, passing commands on from the Windows application, rebooting and so forth.
However once it goes through the repair process at some point I get some strange cyan screen with white and lilac blinking lines and the program keeps saying "waiting for your device (or phone, or whatever" ...
Losing the will to live.
ilmoomino said:
That didn't work either (the restore to stock).
The USB passthrough on VMWare fusion works like a charm, ADB sees the device, passing commands on from the Windows application, rebooting and so forth.
However once it goes through the repair process at some point I get some strange cyan screen with white and lilac blinking lines and the program keeps saying "waiting for your device (or phone, or whatever" ...
Losing the will to live.
Click to expand...
Click to collapse
Why are you using VMWare? You should be able to download the tools you need for WIndows, Mac, or Linux.
Go and grab the Android SDK and install the "Android SDK Platoform-tools" and download 4.4.4 image from Google.
Once you have those two things, unzip the factory image and do "adb reboot bootloader" and then run "sh flash-all.sh" from a command prompt. This will use fastboot to write an img file to the partitions on the device, so if you can't run the SDK tools, for whatever reason, use fastboot to run the commands in the file. (That is, don't use recovery and adb sideload, do it through fastboot)
The -w option will wipe your data, so if you want you can try and run the last line (fastboot -w update image-occam-ktu84p.zip) without the "-w", but if it doesn't work then I'd try it again with it.
If you can boot into the bootloader and recovery then your device isn't dead. Worst case you have to go to a friend's place and flash it there.
nic0lette said:
Why are you using VMWare? You should be able to download the tools you need for WIndows, Mac, or Linux.
Go and grab the Android SDK and install the "Android SDK Platoform-tools" and download 4.4.4 image from Google.
Once you have those two things, unzip the factory image and do "adb reboot bootloader" and then run "sh flash-all.sh" from a command prompt. This will use fastboot to write an img file to the partitions on the device, so if you can't run the SDK tools, for whatever reason, use fastboot to run the commands in the file. (That is, don't use recovery and adb sideload, do it through fastboot)
The -w option will wipe your data, so if you want you can try and run the last line (fastboot -w update image-occam-ktu84p.zip) without the "-w", but if it doesn't work then I'd try it again with it.
If you can boot into the bootloader and recovery then your device isn't dead. Worst case you have to go to a friend's place and flash it there.
Click to expand...
Click to collapse
I am using VMWare Fusion since my Windows work laptop is dead (courtesy of lost charger).
So I must use my Mac (which used the CM installer where things went sour).
Doubt it is a problem since I can get ADB to work.
I have already dowloaded the Android SDK Platoform-tools and stock 4.4.4.
I used ADB on MAC, but after I copy the ROM the phone does some scroll-bar progress, then I clear partitions/factory erase/cache ... and boot loop again.
I will follow your advice and use the described process.
You are right - as long as I have bootloader I am safe.
Might go and buy Moto X+1 or Sony X3 ... as I want to go 4G but thought might use the N4 for another few months.
thanks
following instructions from nic0lette I have now my phone back to normal ...
will try CM using the same instructions ... well, using the flash-all.sh as a base script
thanks (and "thanked")
Hi all,
I have this X00TD model, and I recently updated firmware to WW-16.2017.2002.061. The phone has Android recovery, and I want to install Lineage OS. Whenever I try to install Lineage, I get the error 21 "signature verification failed". I read somewhere that I can disable the signature check in TWRP. But TWRP fails to install, whatever I try. I tried 3 different unofficial versions of TWRP (as my phone model has no official version of TWRP) and in fastboot, when I give the command "sudo fastboot flash recovery <filename>.img", nothing happens, and the process just freezes, and I need to kill the terminal to end the process. I have Ubuntu 18.04 installed. ADB and fastboot seem ok. When I type "sudo fastboot devices", my phone entry comes up. Any help would be welcome. I don't have windows os.
Thanks.
akhil520c said:
Hi all,
I have this X00TD model, and I recently updated firmware to WW-16.2017.2002.061. The phone has Android recovery, and I want to install Lineage OS. Whenever I try to install Lineage, I get the error 21 "signature verification failed". I read somewhere that I can disable the signature check in TWRP. But TWRP fails to install, whatever I try. I tried 3 different unofficial versions of TWRP (as my phone model has no official version of TWRP) and in fastboot, when I give the command "sudo fastboot flash recovery <filename>.img", nothing happens, and the process just freezes, and I need to kill the terminal to end the process. I have Ubuntu 18.04 installed. ADB and fastboot seem ok. When I type "sudo fastboot devices", my phone entry comes up. Any help would be welcome. I don't have windows os.
Thanks.
Click to expand...
Click to collapse
Fastboot flash recovery twrp.img
Sent from my ZenFone Max Pro M1 using Tapatalk
If you can't install TWRP on pie, try reverting to Oreo with AFT and then flash TWRP in fastboot. Also make sure you have unlocked the bootloader whether by the official tool or the unofficial method. THIS WILL DELETE ALL DATA SO BACK UP.
Thanks arko. Is there Asus Flash Tool available for Linux also? Will try and revert. Thanks :svetius
Tried reverting to Oreo with AFT, doesn't work. I installed windows 10, but fastboot doesn't work.
#fastboot devices gives me no output. I have the Oreo zip file, any alternate way I can install it? As you mentioned, there seems to be an issue with the pie ROM on my phone. Any way I can downgrade to Oreo using windows/Linux?
akhil520c said:
Tried reverting to Oreo with AFT, doesn't work. I installed windows 10, but fastboot doesn't work.
#fastboot devices gives me no output. I have the Oreo zip file, any alternate way I can install it? As you mentioned, there seems to be an issue with the pie ROM on my phone. Any way I can downgrade to Oreo using windows/Linux?
Click to expand...
Click to collapse
Windows 10 ? Its bcuz Driver Signature Enforcement
Disable it and reinstall adb and fastboot drivers, it will work for sure.
Windows driver security wouldn't accept drivers without proper Signatures,so like i said, just disable it and you are good to go.
:good:
Tried steps you mentioned, doesn't work. In fastboot mode, #fastboot devices gives me no output. Looks like my pie ROM is buggy. Basically, I need to install lineage on the phone.
Hi all,
Finally got everything done in about 5 mins I booted up Ubuntu Mate (32 bit) on my other laptop, and found I'd already installed adb and fastboot on it from the repositories (not from google). I booted my phone in fastboot mode, and tried the #fastboot devices command, and voila, my phone got detected! After that, it was a matter of a few minutes, following the installation instructions (of twrp and lineage) from the lineage website. Thanks for all your inputs and help
P.S: I realised (again), after more than 2 decades, that windoze mighty sucks lol.
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
GioPan_ said:
Hi,
Today I wanted change my recovery. I had the Lineage OS recovery, but i was trying to install the twrp recovery.
So, the guide of twrp says that you should boot the twrp via fastboot boot twrp.img and install via the booted twrp. But I mistaken the command and I wrote fastboot flash boot twrp.img, I tried to reboot and the device booted himself in fastboot with the enter reason "error boot prepare" and I can't boot into the system or recovery.
I tried to flash the official image downloaded from the Google Developers website, but when i run ./flash-all.sh, console get stuck. I waited for about 15 minutes but nothing. I tried even the official Android Flash Tool but after 10 seconds it says "Your device stopped responding. You may have to select restart in the bootloader menu in order for it to be recognised again."
Does anyone know how to help me? Thanks in advance.
Click to expand...
Click to collapse
Do you have tryied to run the official google tool in Windows to try to rescue it?
Estebiu said:
Do you have tryied to run the official google tool in Windows to try to rescue it?
Click to expand...
Click to collapse
Yes, I wrote in the post, I tried both the command line tool and the chrome version. Btw i'm on linux
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
I'll try this...
GioPan_ said:
Okay so, I fixed.
For anyone who will have this problem you just need to flash official Android 9 and next Android 10. Only with Android 10 you can use fastboot flash boot recovery.img (you can't use twrp in android 10 with the Pixel 3a)
Click to expand...
Click to collapse
Does this work if adb not working? I only have fastboot.
WriteLovey said:
Does this work if adb not working? I only have fastboot.
Click to expand...
Click to collapse
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
WriteLovey said:
I'm not certain I understand what you mean by PC authorized? I'm using a Windows 10 tablet. When the phone is attached to the computer it sees it as a device that can be disconnected through USB.
Click to expand...
Click to collapse
All is well. I'm back on my Pixel, yeah!
GioPan_ said:
It depends if your pc were authorized, if it was, you can use fastboot to flash the stock version of Android 9, just running the flash-all(.bat) script.
Click to expand...
Click to collapse
I just had an encounter with this. I was rooting my device (Pixel 3A) and messed up my partitions through accidentally attempting a downgrade which broke all my ****. I was unable to easily reset this device to factory, so it took me several days to figure out and root. I'm getting better though as a hacker, because a year ago this would have taken me a month.
I was able to enter recovery mode (lying down Android, NO COMMAND). From this recovery mode, adb devices -l recognized my device, although I was unable to get a shell.
At first, ADB was telling me the device was authorized, but I messed with a bunch of other stuff (tried to flash a bunch of different partitions and monkey around in general trying to install Magisk) and then ADB started telling me it wasn't authorized when I used devices -l.
Once it said unauthorized, I was unable to issue the device any commands with ADB, so I just used hardware keys to get into recovery mode. From there, I selected OTA update, and it got into sideload mode. At that point, I used adb sideload with the OTA package that I downloaded here https://developers.google.com/android/ota
^^^ That operation did successfully restore my device to factory
This following guide here describes the details of how to use hard keys to enter recovery on this phone (don't download anything from there tho, and make sure your adblock is on)
How to Hard Reset your new Google Pixel 3a [Tutorial]
In this article, you will learn how to start your Google Pixel 3a up into the Recovery Mode and perform the Hard Reset to make it work perfectly again.
thedroidguy.com
I just wanted to say, I've been wrestling this hardbrick for a couple of days with my Pixel 3a.
I've finally overcome it by sideloading the most recent OTA update after using a hard key combo to get into recovery mode. The hard key combo is hold Power Button, tap Volume Up, then release both. Then, all you need is to use the command:
adb sideload <OTA.zip>
^^^OTA wasn't the actual filename though, you can download OTA packages for Pixel 3A here: https://developers.google.com/android/ota
the OTA binaries are NOT the same as the factory images, which is here
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
Sideloading the OTA package brought my phone back from only having fastboot and recovery mode, even when flash-all.sh from the official downloaded firmware failed. Now I know how to undo damage that I cause by rooting this thing. Since I sideloaded newest firmware, it was also like applying an update. I easily got root after that, and I've logged the process. I'll make it into a guide soon
I'll just note that if you accidentally flashed the TWRP boot image instead of simply booting into it, I believe all you have to do is flash the stock boot.img to fix the problem. Obviously you can sideload the entire rom image, but that shouldn't be necessary.
Using the Windows computer (or whatever computer you are sending ADB commands from), download the full stock image directly from Google. Unzip it and then upzip the folder inside. You should find the boot.img file inside that folder. Take that file and then flash it to the phone using the normal ADB command: fastboot flash boot boot.img
While I haven't tried this myself recently, it should work in theory. The command "fastboot flash boot twrp.img" flashes the boot partition with a non-working twrp image, so replacing the faulty image with the stock boot.img should fix the problem.
If I did the same I would first attempt to manually put device in bootloader/aka fastboot mode then fastboot flash the stock boot.img , sudo fastboot flash boot boot.img --slot all
I only read the op (first post here);but I betcha that would have worked. Then sudo ./flash-all.sh and let it do it's thing.