Database Users

[Q] Failure to flash recovery images using fastboot: (Protocol error)

I seem to be unable to flash any recovery images using
Code:
fastboot flash recovery IMG
. When I put the tablet into fastboot mode, attach it to the computer using a microusb adapter and run the command, I get the following error:
Code:
sending 'recovery' (9158 KB)...
FAILED (data transfer failure (Protocol error))
finished. total time: 0.057s
If I repeat the command, any number of times, I get another error:
Code:
sending 'RECOVERY' (9158 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
I've tried this with TWRP MultiROM and ClockworkMod Recovery. Why do I get this error? How can I troubleshoot/solve this in order to flash recovery images?
Device: (original) Google Nexus 7 16GB WIFI
Android Version: 4.3 (stock)
Kernel Version: 3.1.10-g1e8b3d8
PC Software: Ubuntu 13.04 with android-tools-fastboot 4.2.2+git20130218-3ubuntu3~raring
The full steps I took to unlock bootloader and attempt flashing the recovery (from a factory reset):
Put the device into developer mode by tapping the 'Build number' in 'Settings->About tablet' several times.
Enabled USB debugging in 'Settings->Developer options'.
Connected the USB cable to a laptop running Ubuntu 13.04 with android-tools-adb and android-tools-fastboot installed.
Ran
Code:
adb devices
which showed the device
Code:
adb reboot bootloader
>> rebooted into the fastboot bootloader
Code:
sudo fastboot devices
>> showed the device
Code:
sudo fastboot oem unlock
>> bootloader successfully unlocked
Code:
sudo fastboot continue
>> booted the device
Repeated the steps to enable developer mode and USB debugging
Downloaded kernel_kexec_430.zip, multirom_v12_n7-signed.zip, TWRP_multirom_n7_20130727.img to the current folder (and verified the md5sums)
Copied TWRP_multirom_n7_20130727.img to recovery.img
Copied kernel_kexec_430.zip, multirom_v12_n7-signed.zip, recovery.img to Nexus 7/Internal Storage root directory using nautilus
Ran
Code:
adb reboot bootloader
which put the device into fastboot mode
Ran
Code:
sudo fastboot flash recovery recovery.img
, which failed

Code:
flashboot flash bootloader [URL="http://d-h.st/QFd"]bootloader-grouper-4.23.img[/URL]

Running:
Code:
flashboot flash bootloader bootloader-grouper-4.23.img
has the same problem:
Code:
sending 'bootloader' (2100 KB)...
FAILED (data transfer failure (Protocol error))
finished. total time: 81.438s

lazyteq said:
Running:
Code:
flashboot flash bootloader bootloader-grouper-4.23.img
has the same problem:
Code:
sending 'bootloader' (2100 KB)...
FAILED (data transfer failure (Protocol error))
finished. total time: 81.438s
Click to expand...
Click to collapse
change usb cable and try different ports...

It seems this is a problem with the usb cable and usb ports. Fastboot seems very flaky and intemittently works on different USB ports.
Now for a story about how I softbricked and eventually unbricked the tablet.
By changing around USB ports on my laptop, I eventually managed to flash TWRP recovery. In the process of messing around, I managed to delete the os from the tablet, so I tried to reinstall the stock os.
I ran the flash-all script and it started to install. Unfortunately, fastboot decided to fail once it had erased the partitions and was starting to re-flash them. So I was left with a tablet with no os, no recovery and only a bootloader that wouldn't communicate properly with fastboot on my laptop!
I decided to try a different computer. The only one I had available was a very old Windows XP desktop with 256MB RAM and USB 1.0 ports (!). I managed to download the Android SDK on this incredibly slow machine and also installed device drivers using the Nexus 7 toolkit. I couldn't get fastboot to work for ages but eventually, after plugging the tablet out and in and repeating the
Code:
fastboot devices
command, I managed to get the device to show up.
I then managed to reflash TWRP onto the recovery partition. Fastboot was still very dodgy but seemed a bit more reliable at sending the data across than it had been on my laptop. Once I had flashed TWRP, I put the latest Cyanogenmod ROM onto a usb stick, connected it via OTG and managed to install it.
So now I have a working tablet with TWRP and Cyanogenmod and I finally have proper root permissions including the ability to use usb-otg which was one of the main reasons for rooting in the first place. I'm going to give MultiROM a miss because I really don't trust fastboot / my usb cable / my usb ports to properly flash images.

Username invalid said:
Code:
flashboot flash bootloader [URL="http://d-h.st/QFd"]bootloader-grouper-4.23.img[/URL]
Click to expand...
Click to collapse
I there, I am not at all a novice to Android but I have only owned two Nexus devices. The other two devices that I have had and modded were the Vzw Galaxy s4 and s3. I've been modding for quite a while now and am quite familiar with Android software modifying and using adb. That being said quick semi topic related question: How do I know what Bootloader my Nexus 7 has already? I just sent it in to repair at Asus and got it back compeletely wiped running stock (sent it in unlocked running Rootbox). I have previously flashed to the most recent bootloader, but I'm not sure if it still has it. I don't know what all they did to it.
Is there a way to find out exactly what bootloader it is running? Maybe there is an adb shell command I can run to find out or something?
I have searched but I couldn't find a definitive answer. And I didn't want to start a whole new thread just to ask this simple question.
Thanks for your time.

nicholi2789 said:
I there, I am not at all a novice to Android but I have only owned two Nexus devices. The other two devices that I have had and modded were the Vzw Galaxy s4 and s3. I've been modding for quite a while now and am quite familiar with Android software modifying and using adb. That being said quick semi topic related question: How do I know what Bootloader my Nexus 7 has already? I just sent it in to repair at Asus and got it back compeletely wiped running stock (sent it in unlocked running Rootbox). I have previously flashed to the most recent bootloader, but I'm not sure if it still has it. I don't know what all they did to it.
Is there a way to find out exactly what bootloader it is running? Maybe there is an adb shell command I can run to find out or something?
I have searched but I couldn't find a definitive answer. And I didn't want to start a whole new thread just to ask this simple question.
Thanks for your time.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Or you can use
Code:
fastboot getvar all
Version 4.23 is the latest released with Android 4.3.

Username invalid said:
Or you can use [Code ]fastboot getvar all[/CODE]
Version 4.23 is the latest released with Android 4.3.
Click to expand...
Click to collapse
Haha wow. Now I really feel like a noob. I guess I probably should have noticed that.
Thanks

I had the same problem and then realized I was using 3.0 usb port.
Plugged cable into 2.0 port and it suddendly worked.

I have the same error:
Code:
FAILED (command write failed (Protocol error))
In my case my phone was connected through USB HUB so i connected it to PC and everything starts working.

Did not work
sending 'recovery' (12396 KB)...
OKAY [ 0.409s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.458s

I see this also when my USB cable was too long.

I also just used a shorter cable and it worked

Bricked 2012 Wifi Only Nexus 7, Please Help

Sorry if this has been addressed but I've been searching and reading and freaking out because I can't find out how to recover my Nexus 7.
I'm trying to manually update my 2012 Wifi Only Nexus 7 to Lollipop and my computer will not see the device any longer in ADB.
I downloaded the latest sdk and the latest image file (Nakasi 5.0.2 (LRX22G).
Ran through the steps found here: http://www.androidcentral.com/how-manually-upgrade-your-nexus
At this step fastboot flash bootloader [bootloader file].img it just sat there for about an hour and didn't do anything.
***Edit- I got it to work and then got the invalidstate error.
I then read that others have had success updating to Lollipop without updating there bootloader here: http://android.stackexchange.com/qu...t-flash-bootloader-failed-remote-invalidstate
***This is because my bootloader was already on 4.23.***
I then proceeded with fastboot -w update [image file].zip
The image failed after wiping everything with an error about too many links.
Now when I try I get "C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot -w upd
ate image-nakasi-lrx22g.ziparchive does not contain 'boot.sig'"
At this point, I can't get any adb commands to work as the device is not showing up as a connected device. I've rebooted my pc and the tablet multiple times. Fastboot keeps crashing as well.
Please help me get my Nexus back up and running. Thanks so much.

The Bootloader in the factory image is not valid see here
If you still can get into fastboot on your device,
Extract the img files from the zip file and manually flash each of them.
Alternatively, you could extract all the .img files in the zip file and flash them manually one at a time. This makes things really handy if you're using the factory image to act as an update rather than a complete return to stock. If trying to update using the factory image, extract the .img from the zip file into the same directory as your bootloader and radio img files and execute the following commands in order:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
Click to expand...
Click to collapse
Quote taken from here

corkiejp said:
The Bootloader in the factory image is not valid see here
If you still can get into fastboot on your device,
Extract the img files from the zip file and manually flash each of them.
Quote taken from here
Click to expand...
Click to collapse
Thanks, this is what I get
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot flash
system system.img
sending 'system' (648819 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>

touch_rules said:
Thanks, this is what I get
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>adb devices
List of devices attached
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot flash
system system.img
sending 'system' (648819 KB)...
FAILED (command write failed (No such device or address))
finished. total time: 0.016s
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>
Click to expand...
Click to collapse
Are you in fastboot mode?
Step 4: Make sure the device is connected to the computer while in fastboot mode. Different devices may require different commands to get into fastboot mode. Make sure the device is powered off and then use the following button commands:
Nexus 7 - Vol Down + Power
Click to expand...
Click to collapse
Since you issued an Adb command first, suggest your not?
Another option would be to use Wugfresh Nexus Root toolkit and set the option to "Force Flash Mode" in Options Flash Stock.

corkiejp said:
Are you in fastboot mode?
Since you issued an Adb command first, suggest your not?
Another option would be to use Wugfresh Nexus Root toolkit and set the option to "Force Flash Mode" in Options Flash Stock.
Click to expand...
Click to collapse
Yes, I am. Please take a look at this picture. Thanks.
View attachment 3085046

Now I'm getting this At least it's different
C:\Users\John\Desktop\Nexus 7\Android\android-sdk\platform-tools>fastboot flash
system system.img
erasing 'system'...
FAILED (status read failed (Too many links))
finished. total time: 0.176s

corkiejp said:
Another option would be to use Wugfresh Nexus Root toolkit and set the option to "Force Flash Mode" in Options Flash Stock.
Click to expand...
Click to collapse
Noticed this part after I posted last, seems to be working....I'll let you know. Thanks so much. Wish I would have seen the toolkit earlier today when I started haha.

You rock corkiejp! Working like a champ now! Thanks so much.

I had exactly the same problem and ended up using Wug's toolkit and the individual images.
Sent from my Nexus 7 using XDA Free mobile app

I literally had it restore the factory image and it did it all. Made sure I had force flash checked.

Man, I really need some help here. i am in a almost exact situation here. Only thing different is that my tablet is locked. I go to wugs and flash stock image and get stuck on "waiting for device".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help would be highly appreciated!!!

Your bootloader is locked.
rayandreas said:
Man, I really need some help here. i am in a almost exact situation here. Only thing different is that my tablet is locked. I go to wugs and flash stock image and get stuck on "waiting for device". View attachment 3237509
Any help would be highly appreciated!!!
Click to expand...
Click to collapse
Hi, rayandreas...
Something is definately not quite right with your posted screenshot/output.
Transcribing it as follows, we have...
Code:
erasing 'boot'...
OKAY [ 1.154s]
finished. total time: 1.155s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 3.045s]
finished. total time: 3.045s
erasing 'recovery'...
OKAY [ 0.240s]
finished. total time: 0.241s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.014s]
finished. total time: 0.014s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.014s]
finished. total time: 0.014a
So far, so good.
I can see nothing wrong with this output, thus far... and I've seen something similar on my Nexus 7 many times when I've fastboot flashed stuff.
----
But then this bombshell hits!!
Code:
sending 'bootloader' <2100 KB>...
[COLOR=RED][B]
FAILED <remote: Bootloader is locked.>
[/B][/COLOR]
finished. total time: 0.015s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
----
WTF!!!
Bootloader is now locked!
How is this even remotely possible?
----
If the bootloader is locked, the first half of your posted output simply shouldn't have been possible... But yet, your screenshot proves otherwise.
The bootloader is either locked and NO fastboot flash commands are possible, or the bootloader is unlocked and ALL fastboot flash commands are possible...
Your Nexus 7 seems to have 'changed its mind' about its bootloader lock status, halfway through fastboot flashing!!!
----
To determine the bootloader lock status of your Nexus 7, you need to boot your Nexus 7 into it's bootloader manually...
*** shut down the device completely.
*** press and hold VOL DOWN, and press POWER ON.
*** the text in the lower left hand corner of the screen should indicate the devices bootloader locked status.
See my attached screenshot for the sort of thing you should expect to see if the bootloader is unlocked.
---
If it's locked, try unlocking it manually (ie, via fastboot), with...
Code:
fastboot oem unlock
Hope this helps.
Rgrds,
Ged.

GedBlake said:
Hi, rayandreas...
Something is definately not quite right with your posted screenshot/output.
Transcribing it as follows, we have...
Code:
erasing 'boot'...
OKAY [ 1.154s]
finished. total time: 1.155s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 3.045s]
finished. total time: 3.045s
erasing 'recovery'...
OKAY [ 0.240s]
finished. total time: 0.241s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.014s]
finished. total time: 0.014s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.014s]
finished. total time: 0.014a
So far, so good.
I can see nothing wrong with this output, thus far... and I've seen something similar on my Nexus 7 many times when I've fastboot flashed stuff.
----
But then this bombshell hits!!
Code:
sending 'bootloader' <2100 KB>...
[COLOR=RED][B]
FAILED <remote: Bootloader is locked.>
[/B][/COLOR]
finished. total time: 0.015s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
----
WTF!!!
Bootloader is now locked!
How is this even remotely possible?
----
If the bootloader is locked, the first half of your posted output simply shouldn't have been possible... But yet, your screenshot proves otherwise.
The bootloader is either locked and NO fastboot flash commands are possible, or the bootloader is unlocked and ALL fastboot flash commands are possible...
Your Nexus 7 seems to have 'changed its mind' about its bootloader lock status, halfway through fastboot flashing!!!
----
To determine the bootloader lock status of your Nexus 7, you need to boot your Nexus 7 into it's bootloader manually...
*** shut down the device completely.
*** press and hold VOL DOWN, and press POWER ON.
*** the text in the lower left hand corner of the screen should indicate the devices bootloader locked status.
See my attached screenshot for the sort of thing you should expect to see if the bootloader is unlocked.
---
If it's locked, try unlocking it manually (ie, via fastboot), with...
Code:
fastboot oem unlock
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you for even taking time for helping me thus far. I can say that it states the boot loader is locked. I have tried using wugs to unlock it but it doesn't work. I can't boot it up either. Just stays on the google splash screen. I am at a loss at what to do as of now. If I could get some help on how to rescue this thing I would be glad to donate a 12 pack or a 10 coffee or something. I received the tablet this way. I am hoping to fix it so my wife can use it.

rayandreas said:
Thank you for even taking time for helping me thus far. I can say that it states the boot loader is locked. I have tried using wugs to unlock it but it doesn't work. I can't boot it up either. Just stays on the google splash screen. I am at a loss at what to do as of now. If I could get some help on how to rescue this thing I would be glad to donate a 12 pack or a 10 coffee or something. I received the tablet this way. I am hoping to fix it so my wife can use it.
Click to expand...
Click to collapse
Hi again, rayandreas...
If it where my tablet, I'd just fastboot flash the Google factory stock image for your device.
The Google factory stock image for your device can be found here...
https://developers.google.com/android/nexus/images#nakasi
There's little point in my re-inventing the wheel by writing yet another tutorial... full details and instructions can be found here...
[GUIDE] Flashing a Factory Image with fastboot / return to stock
----
But all of this is contingent upon successfully UNLOCKING THE BOOTLOADER.
The bootloader needs to be unlocked, before anything can be fastboot flashed.
Whilst this can be done with toolkits (such as Wugs), I personally prefer to deal with fastboot directly (instead of through a layer of GUI polished menus and dialogue boxes).
----
From power-down state, or to force boot the device into its bootloader...
** Press and hold VOL-DOWN.
** Whilst holding VOL-DOWN, press POWER ON.
** Keep BOTH buttons pressed for a good 30 seconds.
If successful, you should see a GREEN ANDROID lying on its back...
----
USB connect it to your laptop/PC. Ensure you have the correct drivers installed on your laptop/PC as per the instructions detailed in the above link.
The command is as follows...
Code:
fastboot oem unlock
Due to security considerations, this command will wipe the Nexus 7, and you will be advised of this by the Nexus 7 itself, and you'll also need to confirm the bootloader unlock request at the Nexus 7 end via a confirmation dialogue box.
(See the attached screenshot for the sort of thing you should expect to see).
If successful, you should see an unlocked padlock symbol at the bottom of the screen, underneath the Google logo, whenever the device boots.
----
Unlocking the bootloader is critical if you wish to fastboot flash anything. Even official Google factory stock images require an unlocked bootloader to be fastboot flashed. And with the Google recommendation that the bootloader is re-locked afterwards with...
Code:
fastboot oem lock
This is optional of course, and I would generally recommend against it, because if you wish to unlock the bootloader again at some future date, it will wipe/factory reset the device...
General point of advice: Once Unlocked - Leave it Unlocked.
---
Hope this helps... and good luck.
Rgrds,
Ged.

View attachment 3240619
Man, it was looking promising. Went into boot loader, asked me if I wanted to unlock and then it failed : ( This is crazy!!! Please see attached pics. Any other ideas? I am at a loss...

rayandreas said:
View attachment 3240618
View attachment 3240619
View attachment 3240620
Man, it was looking promising. Went into boot loader, asked me if I wanted to unlock and then it failed : ( This is crazy!!! Please see attached pics. Any other ideas? I am at a loss...
Click to expand...
Click to collapse
Maybe your bootloader is corrupted? @GedBlake, can you provide him with latest 4.23 bootloader? I was searching the web and found out some bootloaders can be bad. Someone correct me if I said something wrong(just trying to help xD)

Fobos531 said:
Maybe your bootloader is corrupted? @GedBlake, can you provide him with latest 4.23 bootloader? I was searching the web and found out some bootloaders can be bad. Someone correct me if I said something wrong(just trying to help xD)
Click to expand...
Click to collapse
Man, I'll try anything. It is really racking my brain!
Thanks guys, for all the help so far...

rayandreas said:
Man, I'll try anything. It is really racking my brain!
Thanks guys, for all the help so far...
Click to expand...
Click to collapse
According to this article, some of bootloaders were corrupted or what. Update NRT masterlists in the toolkit and try flashing the latest bootloader if that is possible through the toolkit. Maybe it will let you to unlock the bootloader afterwards. If the toolkit can't do that for you, download latest factory image(4.4.4 or 5.1, what you desire) and extract the bootloader from the image. It will probably be named "bootloader-nakasi....." Try manually flashing it through CMD/ADB using "fastboot flash bootloader "name of bootloader file". I repeat, I don't have much experience with this tablet, but I'm doing what I can. Try doing what I suggested, maybe it'll work. You can't make it worse after all Good luck!
EDIT: In the link I posted, there are some neat instructions and a link to the new bootloader down the page. Make sure to check that out too.

I did update the NRT images and tried again with no luck. I also tried going into recovery and this is what I get. So, it looks like I have a crazy locked boot loader and no recovery at all. I am trying the other method now. We shall see!
Thanks for all the help so far. It means a lot!

rayandreas said:
I did update the NRT images and tried again with no luck. I also tried going into recovery and this is what I get. So, it looks like I have a crazy locked boot loader and no recovery at all. I am trying the other method now. We shall see!
Thanks for all the help so far. It means a lot!
View attachment 3242733
Click to expand...
Click to collapse
You actually have a recovery, a stock one. While at that screen, press Volume Up + Power for 1 sec( or only Volume Up, not sure) to access it. You can try doing a factory reset there if that helps anyhow.

[FIX] fix hard brick / qhsub_bulk after bad flash / cm12 flash from 5.1

First of all:Remember:im just making a thread, all of this wasn´t possible if not for @ccfries(He works at motorola, and sent the files to shamu´s device tree repo)
and @Casper34
See: http://forum.xda-developers.com/showpost.php?p=59562745&postcount=9 and https://android-review.googlesource.com/#/c/143010/
Requirements:
Motorola Drivers:
http://storage.googleapis.com/tetheredupgrades/MotorolaDeviceManager_2.5.4.exe
Qualcomm Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=631288&d=1308601930
Optional: If having issues use:
http://forum.xda-developers.com/showthread.php?t=2263822
Unbrick Stuff:
https://www.dropbox.com/s/8783ohne2mufiwc/Nexus6Unbrick.rar?dl=0
or
https://drive.google.com/file/d/0BwduAK2l37Oaa1BQZncwaEpNb1E/view?usp=sharing
Factory Images for Nexus 6(needs to be 5.1)
https://dl.google.com/dl/android/aosp/shamu-lmy47d-factory-6c44d402.tgz
or via RSD Lite
http://motofirmware.center/files/file/1069-shamu-lmy47e-release-keys-subsidy-default-cfcxmlzip/
FASTBOOT AND ADB NEEDS TO BE ALREADY SETTED UP
Pre Requirements:
- Disable driver signature checking
Windows 7:
https://www.youtube.com/watch?v=k4RwaI4mn6Y
Windows 8:
https://learn.sparkfun.com/tutorial...abling-signed-driver-enforcement-on-windows-8
Windows 8.1:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
- Install the drivers:
Go to device manager, Unknown devices, double click qhusb_bulk, install driver, select location and select where you extracted the drivers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Next you should extract both zip files (Unbrick and factory images)
- Then Connect your nexus 6 on your computer (now should appear as Qualcomm HS-USB QD-Loader 9008 under "COM PORTS"):
- Open the Unbrick folder and run blank-flash.bat:
- Flash Stock factory images: (Problems see #2)
Your phone should show up on the computer as fastboot.Just flash stock factory images. (Motorola via "RSD Lite" or Google one should do the trick).
Thanks:
@ccfries(HUGE Thanks to him, turns out he is the one who made the commit with the necessary files, props to him!)
@Casper34 (Huge help with his working nexus 6)
@bitdomo (helped me a lot, and i got some images from another thread of his)

Problems that may occur during or after:
Stuck at waiting for device
Check if drivers are installed correctly and restart pc
Check if you have an updated fastboot
THESE TWO ARE THE MAIN REASON OF PROBLEMS (mostly outdated fastboot)
-Drivers
http://forum.xda-developers.com/showthread.php?t=2263822
http://storage.googleapis.com/tetheredupgrades/MotorolaDeviceManager_2.5.4.exe
Fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
Problems while flashing factory images:
ccfries said:
First, fastboot flash partition gpt.bin
Then flash the other images.
If you just bricked by downgrading bootloader, the persist and modem calibration should still be happily where it was when you started.
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1. There's accurate information elsewhere in the forum on that.
-Chris
Click to expand...
Click to collapse
PS:
ccfries said:
If you lock, it clears the setting by design, so you can't lock and unlock without booting up and checking the box.
Click to expand...
Click to collapse
Wifi / Bluetooh dosen´t work:
See http://forum.xda-developers.com/showpost.php?p=59561966&postcount=3
No IMEI / No Signal
Restore EFS Backup

If wifi/bt/camera dosen´t work Then probably your /persist got somehow corrupted. (Post Under construction)
For a fix:
Flash a custom recovery, and open a terminal with the phone booted to it
run
umount /persist
mkdir /persist
mount /dev/block/platform/msm_sdcc.1/by-name/persist /persist
#e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
you will be propmpted to check / repair errors, keep pressing enter for each that it appears
then run
umount /perist
and reboot phone

Wow! Very nice. I bet you just saved some poor guys from getting yelled at from wifey. Good job and thanks for helping the community. :highfive:

wow indeed!

jayharper08 said:
Wow! Very nice. I bet you just saved some poor guys from getting yelled at from wifey. Good job and thanks for helping the community. :highfive:
Click to expand...
Click to collapse
simms22 said:
wow indeed!
Click to expand...
Click to collapse
Thanks to both, thankfully cm already merged a check for the bootloader, but i hope this can fix phones that are already bricked for people who cant use warranty (outside area, on a trip, etc).
Oh yeah, or in the case of my friend, his mom

This needs stickied
Sent from my Nexus 6 using XDA Free mobile app

@opssemnik
No worries, glad to help out!
Sent from my Nexus 6

opssemnik said:
@ccfries(Huge thanks for him, for finding an un merged commit that had the partition layout)!.
Click to expand...
Click to collapse
I authored the commit this afternoon so finding it was pretty easy. :good:

ccfries said:
I authored the commit this afternoon so finding it was pretty easy. :good:
Click to expand...
Click to collapse
Oh no wait, I DIDN´T SEE THE AUTHOR LOL.
may i ask was it hard for you to get the permission to post? afaik these files are proprietary (aside from the paritition table) or aren´t they?.
also can i ask you something a bit more offtopic?
i noticied the nexus 6 works directly with QPST (at least it can communicate with it)
but some other devices (like the nexus 5) can´t, its something that qualcomm or the manufacturer decide / make?
Once again ,props to you and motorola!
Never thought of an oem doing that, even more that the bricks can only be achieved when messing with things you shouldnt be :good::good::good:

Erm, don't mind me asking one question.
How do you back up your efs if your phone is bricked?

So I thought I would rid myself of no Xposed or CM12 on 5.1 (LMY47D) by going back to 5.0.1 and flashing CM12 again from an older nightly I had downloaded already....I think we all know what happened.
I managed to get through it all and have the blank-flash boot loader screen up but I get hung up on <waiting for device> when trying to flash factory image (LMY45D). The boot loader shows as locked and as a result I am unable to flash a factory image. Hopefully I am not breaking any rules or anything by posting this here but this is the error I am getting when running the flash-all.sh:
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.181s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.769s]
writing 'radio'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.772s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(665,0xa03911d4) malloc: *** mach_vm_map(size=1779851264) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1778070480 bytes
error: update package missing system.img​
and when I try to run em unlock:
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s​

Looks good. Does this only help the CM12 people or does it override the "enable OEM Unlock" people too?

serdaj said:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
Click to expand...
Click to collapse
First, fastboot flash partition gpt.bin
Then, fastboot reboot-bootloader
Then flash the other images.
If you just bricked by downgrading bootloader, the persist and modem calibration should still be happily where it was when you started.
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1. There's accurate information elsewhere in the forum on that.
-Chris

Damn, wish this was on here last week. Had to send my N6 off to repair centre for this as I thought it was a gonner. Fault diagnosed as 'Electrical issue - Replacement required'. Replacement is coming tomorrow hopefully. Will bookmark this, thanks.

Delboyd12 said:
Damn, wish this was on here last week. Had to send my N6 off to repair centre for this as I thought it was a gonner. Fault diagnosed as 'Electrical issue - Replacement required'. Replacement is coming tomorrow hopefully. Will bookmark this, thanks.
Click to expand...
Click to collapse
That was when he started this.... After many bricks. I know a lot of people RMAed their phones, but this can still help others!

ccfries said:
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1.
Click to expand...
Click to collapse
It would be helpful if the OP would add this to his first post.

@opssemnik Great Job can you please help me to do so with my HTC One M8 ?
i had the same problem " qualcomm hs-usb qdloader 9008 "
Thanks

bradputt said:
Erm, don't mind me asking one question.
How do you back up your efs if your phone is bricked?
Click to expand...
Click to collapse
Restore he wrote
Shamu/Hammerhead/Flounder Dkwhq www.jsand.dk

Please can someone help me?
I am stuck in the bootloader, which is locked. I can't boot the phone up. I am trying to flash stock images but nothing is happening. Just booting to the bootloader every time.
I can detect my device using fastboot devices, but every time I try and write an img it fails, because the bootloader's locked! Argh!
Thanks in advance,
Tom

Blasted kingroot - bricked my phone?

Ahh, hind sight is a wonderful thing.
After trying to use kingroot to get root access, it failed. And a few days later after rebooting.
I'm now stuck at bootup with Start Up Failed.
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I've now tried lot's of different things, over the last few hours.
RSDLite (show device brings no thing up)
Unlock bootloader (request key, but error regarding OEM unlock not being set - no access to now set it LOL)
Downloaded stock X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip, and tried using various guides on fastboot but keep getting remote failed.
I'm on stock recovery (obviously still locked).
Any thoughts, or hope from anyone?
Obviously, not sure what support Motorola would provide for what is essentially my own fault?

Have you tried manually flashing each bit of the stock firmware/image. That might help. There's a good guide here which I followed to unbrick my device. Just follow the instructions http://theunlockr.com/2015/09/22/how-to-unroot-the-motorola-moto-x-play/

Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926

Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s

sharebubbles said:
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
Click to expand...
Click to collapse
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!

DTLblaze said:
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
Click to expand...
Click to collapse
I run the unlock command, with my unique key but I get ..
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
And since I can't get into the phone, I can't therefore check the "allow OEM unclock"

Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.

DTLblaze said:
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
Click to expand...
Click to collapse
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode

Sickaxis79 said:
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.

sharebubbles said:
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
That really does sound like you bricked the device. If you where on lollipop software you wouldn't have the issue with check bootloader OEM unlock. If it was me I would either contact Motorola or go to a repair shop and have a motd experienced person take a look at it.

Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.

sharebubbles said:
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
Click to expand...
Click to collapse
Strange. This is the tool I used to unlock my bootloader.

drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
I've ben used the latest rom so far why trying to flash (and failing) when I look at recovery I have a LPD23.118-10 number that matches to an earlier 5.1.1 rom (I had been upgraded to 6.0.1 via OTA updates) - do I therefore take that LPD ID to mean that I should actually use the 5.1.1 rom - I'm in the UK, so I'm assuming I'd use the UK one rather than Europe (I'm looking at roms on https://github.com/motoxplay/stock).
Thanks

Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)

sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
And also never try kingroot.

sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
Most in the threads suggesting using rsdlite or manual flash/root and you decided to use kingroot,haha.
Welcome back.

Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
---------- Post added at 05:26 AM ---------- Previous post was at 05:14 AM ----------
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
Tried restoring it, deleted everything and the phone is still on bootloader (LOCKED) and i dont even know how to fix it, I know nothing on how to root, friend suggested it, downloaded it, installed it, didnt work and then i restarted my phone and now its stuck on bootloader screen and the screen has the message "Start up failed: your device didnt start up successfully. Use the software repair assisstant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant." <- Downloaded it, tried it and it was stuck on 6% on repairing, left it over night and it was still on 6%.
ALSO under the message "AP Fastboot Flash Mode(Secure) is there)

Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)

pravin kkr said:
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
Click to expand...
Click to collapse
Download and flash this firmware
https://mega.nz/#!H5YlDCrD!T8tAAW7nHVS-erizRiqg5-Yp_p23hKParMjjHD4diQA credits @kumeipark
Use RSD lite to flash the firmware
http://rsdlite.com/rsd-lite-download/
Moto drivers
http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
If you have problems installing device drivers using Windows 8.1 or Windows 10 follow this guide
https://www.youtube.com/watch?v=gmw86KplqmU
And don't post your contact no. in public forums for everyone to see.

what is the decryption key for the mega link
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
provide the decryption key

having some trouble flashing the magisk patched image

(edit: is my device bricked? it won't load Android now, but is in fastboot
also should i have updated Android first?
i'm thinking of keeping it stock at this point, or maybe finish rooting if possible.)
copied below is what i put in Command Prompt
and then tried downloading adb and fastboot again
i downloaded a fresh factory image for my version
and followed these instructions
How to root the Google Pixel 4 or Pixel 4 XL with Magisk
Looking to root your Google Pixel 4 or Pixel 4 XL? Here's how to unlock the bootloader and root the latest 2019 Pixel smartphones!
www.xda-developers.com
here's what i did:
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
target reported max download size of 268435456 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.199s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.348s
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
C:\adb>
C:\adb>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
then i got the latest platform-tools, because i had installed some other ADB and Fastboot from XDA in an installer with some Google Drivers.
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.355s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.424s]
Finished. Total time: 3.129s
I also downloaded drivers from Google but i'm not sure how to install the DLL file until the device is out of Fastboot?
I tried using the menu to boot to Recovery. Didn't work.
In Device Manager, should i select Android Bootloader Interface to update to this driver?
Or wait until i can select it as a normal Android device after if it's possible to boot it normally?
And what about the website Flash.Android.com? could that get me to stock safely? but not rooted.

Sanman99 said:
copied below is what i put in Command Prompt
and then tried downloading adb and fastboot again
i downloaded a fresh factory image for my version
and followed these instructions
How to root the Google Pixel 4 or Pixel 4 XL with Magisk
Looking to root your Google Pixel 4 or Pixel 4 XL? Here's how to unlock the bootloader and root the latest 2019 Pixel smartphones!
www.xda-developers.com
here's what i did:
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
target reported max download size of 268435456 bytes
sending 'boot' (65536 KB)...
OKAY [ 2.199s]
writing 'boot'...
FAILED (remote: Failed to write to partition Not Found)
finished. total time: 2.348s
Click to expand...
Click to collapse
If the next thing you did was
Sanman99 said:
adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device '(null)' not found
Click to expand...
Click to collapse
then ADB wasn't running. Use fastboot devices to ensure your PC sees your phone before flashing
Sanman99 said:
C:\adb>
C:\adb>fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
Click to expand...
Click to collapse
Correct syntax is adb reboot fastboot/bootloader/recovery
The way it works is like this:
Code:
<tool> <command> <instruction> <options>
where:
<tool> is what you are instructing to send the command to the device: ADB for Android system or recovery, fastboot for bootloader or fastbootd
<command> is what you want the device to do, i.e.: devices / reboot / flash / boot / erase / etc:
devices tells the tool to display connected ADB devices
reboot tells the device to reboot, can provide instruction for what mode you want it to reboot into, example: adb [B]reboot [/B]bootloader
flash can only be used in fastboot, tells the bootloader to flash the specified partition with the specified image, example: fastboot [B]flash [/B]boot <path to boot image
boot tells bootloader to immediately load the specified image without flashing, example: fastboot [B]boot [/B]TWRP.img
erase tells the bootloader to wipe the device; if no partition is specified, this will wipe user data. Use with extreme caution. Example: fastboot [B]erase [/B]data
<instruction> is the details for the command you're giving: adb reboot bootloader, fastboot flash boot <path to image>, fastboot boot <path to image>
<options> include details that may be necessary for various operations, example: fastboot update image-redfin-buildnumber.zip -w --skip-reboot --slot=all --force (this tells the bootloader to update using the specified update package, to wipe data, to not automatically reboot when done flashing, to flash both slots, and to ignore any baseband/bootloader requirements
<option> and <command> can be switched, for example: fastboot --skip-reboot --slot=all --force -w update image-redfin-buildnumber.zip
Sanman99 said:
then i got the latest platform-tools, because i had installed some other ADB and Fastboot from XDA in an installer with some Google Drivers.
fastboot flash boot "C:\path\magisk_patched-25200_NVE3j.img"
Sending 'boot_a' (65536 KB) OKAY [ 2.355s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.424s]
Finished. Total time: 3.129s
Click to expand...
Click to collapse
It's always important to make sure you're using the latest ADB platform tools.
What happened after you successfully flashed the patched image?

V0latyle said:
If the next thing you did was
then ADB wasn't running. Use fastboot devices to ensure your PC sees your phone before flashing
Correct syntax is adb reboot fastboot/bootloader/recovery
The way it works is like this:
Code:
<tool> <command> <instruction> <options>
where:
<tool> is what you are instructing to send the command to the device: ADB for Android system or recovery, fastboot for bootloader or fastbootd
<command> is what you want the device to do, i.e.: devices / reboot / flash / boot / erase / etc:
devices tells the tool to display connected ADB devices
reboot tells the device to reboot, can provide instruction for what mode you want it to reboot into, example: adb [B]reboot [/B]bootloader
flash can only be used in fastboot, tells the bootloader to flash the specified partition with the specified image, example: fastboot [B]flash [/B]boot <path to boot image
boot tells bootloader to immediately load the specified image without flashing, example: fastboot [B]boot [/B]TWRP.img
erase tells the bootloader to wipe the device; if no partition is specified, this will wipe user data. Use with extreme caution. Example: fastboot [B]erase [/B]data
<instruction> is the details for the command you're giving: adb reboot bootloader, fastboot flash boot <path to image>, fastboot boot <path to image>
<options> include details that may be necessary for various operations, example: fastboot update image-redfin-buildnumber.zip -w --skip-reboot --slot=all --force (this tells the bootloader to update using the specified update package, to wipe data, to not automatically reboot when done flashing, to flash both slots, and to ignore any baseband/bootloader requirements
<option> and <command> can be switched, for example: fastboot --skip-reboot --slot=all --force -w update image-redfin-buildnumber.zip
It's always important to make sure you're using the latest ADB platform tools.
What happened after you successfully flashed the patched image?
Click to expand...
Click to collapse
thanks for the quick reply
and extensive yet clear
Yes i did: Fastboot Devices
and it shows the serial number
So when i tried flashing
It didn't flash though, did it? Does that look like it flashed?
When it took 2 or 3 seconds for a 64megabyte file from my computer, isn't on the phone itself.
And said: Image missing OS version
I checked online and other users have the same problem.
I'm stuck in Fastboot. I'm downloading Android SDK Studio and updated the USB Driver again.
I can't get into Recovery or the OS.
Enter reason: error boot prepare
when trying Recovery
I'm wondering if I should get GrapheneOS or if LineageOS is up to date on Pixel 4. I might not want to tinker as much anymore. I still might use the usual apps, but at least utilize root.
Should i be using a different USB cable/cord maybe?
I don't know if I have an OEM USB-c.

Sanman99 said:
thanks for the quick reply
and extensive yet clear
Yes i did: Fastboot Devices
and it shows the serial number
So when i tried flashing
It didn't flash though, did it? Does that look like it flashed?
Click to expand...
Click to collapse
When it says OKAY, that means it successfully flashed.
Sanman99 said:
When it took 2 or 3 seconds for a 64megabyte file from my computer, isn't on the phone itself.
And said: Image missing OS version
I checked online and other users have the same problem.
Click to expand...
Click to collapse
What version of Magisk are you using and where did you download it from?
You are using boot.img, not bootloader.img, right?
You're using the correct firmware for your phone (flame)?
Sanman99 said:
I'm stuck in Fastboot. I'm downloading Android SDK Studio and updated the USB Driver again.
I can't get into Recovery or the OS.
Enter reason: error boot prepare
when trying Recovery
Click to expand...
Click to collapse
It's starting to sound like you might be using the wrong image. Try reflashing the stock boot image (unpatched).
Sanman99 said:
I'm wondering if I should get GrapheneOS or if LineageOS is up to date on Pixel 4. I might not want to tinker as much anymore. I still might use the usual apps, but at least utilize root.
Click to expand...
Click to collapse
One step at a time, I think fixing this should be pretty easy.
Sanman99 said:
Should i be using a different USB cable/cord maybe?
I don't know if I have an OEM USB-c.
Click to expand...
Click to collapse
It's worth a try. Are you using a USB A to C cable, or just C to C? If you're using a C to C cable, try using A to C.
Also, I don't know if you've noticed, but I do have a guide for rooting your device here. Check out the "Initial Root" section to make sure you're doing everything right.

V0latyle said:
When it says OKAY, that means it successfully flashed.
What version of Magisk are you using and where did you download it from?
You are using boot.img, not bootloader.img, right?
You're using the correct firmware for your phone (flame)?
It's starting to sound like you might be using the wrong image. Try reflashing the stock boot image (unpatched).
One step at a time, I think fixing this should be pretty easy.
It's worth a try. Are you using a USB A to C cable, or just C to C? If you're using a C to C cable, try using A to C.
Also, I don't know if you've noticed, but I do have a guide for rooting your device here. Check out the "Initial Root" section to make sure you're doing everything right.
Click to expand...
Click to collapse
tried the (unpatched) factory boot image now
with a different USB cable (both are USB-A to USB-C)
C:\path>fastboot flash boot "C:\path\oriole-tp1a.221005.002-factory-f28b656e\oriole-tp1a.221005.002\image-oriole-tp1a.221005.002\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 1.627s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.506s]
Finished. Total time: 2.465s
Yes i followed the steps
Here is what i originally did
Yes i downloaded a Magisk apk from the guide I mentioned which links to Github
and i updated the app after opening it
then patched the Boot.img and copied to my computer
I'm reading your thread now, which directed to this
[GUIDE] Pixel 4 "flame": Unlock Bootloader, Update, Root, Pass SafetyNet
If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4XL Pixel 4a Pixel 4a (5G) Pixel 5 Pixel 5a Pixel 6 Pixel 6 Pro For best results, use the latest stable Magisk release. Discussion...
forum.xda-developers.com
Yes i downloaded the correct Factory image
I had enabled USB Debugging
and
yep i did the
fastboot flashing unlock
and this is where the problem happened
(well unrelated, i didn't rename the patched-boot.img)
fastboot flash boot <drag and drop master root.img here>
as i copied the output...it took like 2 seconds and gave that message saying something about the OS version
and i can't get ADB working...
Should I have used the PixelFlasher tool?
I don't know what went wrong or what to do now. As I said, some others have had this same error.
i just tried again with fastboot from the SDK directory
C:\Users\path\AppData\Local\Android\Sdk\platform-tools>fastboot flash boot "C:\Users\path\Downloads\oriole-tp1a.221005.002-factory-f28b656e\oriole-tp1a.221005.002\image-oriole-tp1a.221005.002\boot.img"
Sending 'boot_a' (65536 KB) OKAY [ 1.617s]
Writing 'boot_a' (bootloader) Image missing OS version
OKAY [ 0.491s]
Finished. Total time: 2.457s

It's hard to say exactly where you're going wrong. Did you mess with vbmeta at all? You should get no error messages when flashing the original boot image.
Have you tried to boot even after getting the error message?
Pixel Flasher is useful, but it's very important that you understand how everything works under the hood, because the tool just automates what we'd otherwise have to manually do, and the tool can't necessary fix problems.

V0latyle said:
It's hard to say exactly where you're going wrong. Did you mess with vbmeta at all? You should get no error messages when flashing the original boot image.
Have you tried to boot even after getting the error message?
Pixel Flasher is useful, but it's very important that you understand how everything works under the hood, because the tool just automates what we'd otherwise have to manually do, and the tool can't necessary fix problems.
Click to expand...
Click to collapse
(edit: you were right. it wasn't the right Flame image at all. it was Oriole.)
i don't know what vbmeta is.
I can't boot into anything but fastboot.
If I go on the Flash.Android.com website, should i flash to Android 12?
wait...what if it wasn't a Pixel 4 image
is there another that has tp1a.221005.002 ?
how can i check which one this is?
i know you said check if it says Flame
i know i was in the list for Pixel 4 flame when i was about to download
but i typed Ctrl+F and to search the right code
this is what i downloaded
https://dl.google.com/dl/android/aosp/oriole-tp1a.221005.002-factory-f28b656e.zip
---
ok.... here's Flame
https://dl.google.com/dl/android/aosp/flame-tp1a.221005.002-factory-f91d46b5.zip
so i just have to flash the Boot.img from this
and then patch it again, right?

Sanman99 said:
(edit: you were right. it wasn't the right Flame image at all. it was Oriole.)
Click to expand...
Click to collapse
Yeah, that's a pretty common problem.
Sanman99 said:
i don't know what vbmeta is.
Click to expand...
Click to collapse
Don't worry about it
Sanman99 said:
I can't boot into anything but fastboot.
Click to expand...
Click to collapse
Do you mean bootloader? What do you see on the screen? Any error message at the bottom?
Sanman99 said:
If I go on the Flash.Android.com website, should i flash to Android 12?
Click to expand...
Click to collapse
Just update to the latest version, if you haven't already.
Sanman99 said:
wait...what if it wasn't a Pixel 4 image
is there another that has tp1a.221005.002 ?
Click to expand...
Click to collapse
Yes - since the Pixel 3, Google has started using what are called common system images, where the core system build is exactly the same across the entire range of phones. That makes updates much easier, because instead of having to rebuild firmware every month with the source Android update, they can just update the system image, while device specific partitions such as /product, /system_ext, /vendor_boot etc can be updated periodically.
The downside to this is that the updates can be confusing...because the build number is almost exactly the same for every phone, from the Pixel 7 all the way down through the Pixel 4a (since the 4 / 4XL are no longer supported)
As an example, the latest 4a build number is TQ1A.230105.001, and it's exactly the same for the 4a 5g, 5, 5a, and 6a. The Pixel 6, and 6 Pro are TQ1A.230105.002, and the 7 / 7 Pro are TQ1A.230105.001.A2. So there's minor differences there but for the most part the system images are very similar.
Sanman99 said:
how can i check which one this is?
i know you said check if it says Flame
Click to expand...
Click to collapse
As long as it's for the Pixel 4 (flame) it should be OK. The factory images are named in this fashion: device-buildnumber-factory-hash.zip, so yours should be flame-TP1A.221005.002-factory-f91d46b5.zip
Sanman99 said:
i know i was in the list for Pixel 4 flame when i was about to download
but i typed Ctrl+F and to search the right code
this is what i downloaded
https://dl.google.com/dl/android/aosp/oriole-tp1a.221005.002-factory-f28b656e.zip
Click to expand...
Click to collapse
Yeah that's the wrong one
Sanman99 said:
ok.... here's Flame
https://dl.google.com/dl/android/aosp/flame-tp1a.221005.002-factory-f91d46b5.zip
Click to expand...
Click to collapse
Yep
Sanman99 said:
so i just have to flash the Boot.img from this
Click to expand...
Click to collapse
Yes. Just to make absolutely sure we are on the same page, when you download the file, you'll have the original zip (using barbet for my wife's phone as an example)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Extract this to its own folder, which will have another folder inside it with the bootloader image, radio image, scripts, and the system update:
Extract the "image-sunfish.tp1a.221005.002.zip" to its own folder:
In this folder will be the various images for the system update; the one you need is boot.img:
To get running again without root, just flash this:
fastboot flash boot <drag and drop the boot.img here>
Sanman99 said:
and then patch it again, right?
Click to expand...
Click to collapse
Yep...once you're booted into Android, copy the same boot.img to your phone, making sure to delete any old ones, then patch it in Magisk, copy the magisk-patched_25200-xxxxx.img back to your PC, then flash it the same way you did the boot image.

V0latyle said:
Yeah, that's a pretty common problem.
Don't worry about it
Do you mean bootloader? What do you see on the screen? Any error message at the bottom?
Just update to the latest version, if you haven't already.
Yes - since the Pixel 3, Google has started using what are called common system images, where the core system build is exactly the same across the entire range of phones. That makes updates much easier, because instead of having to rebuild firmware every month with the source Android update, they can just update the system image, while device specific partitions such as /product, /system_ext, /vendor_boot etc can be updated periodically.
The downside to this is that the updates can be confusing...because the build number is almost exactly the same for every phone, from the Pixel 7 all the way down through the Pixel 4a (since the 4 / 4XL are no longer supported)
As an example, the latest 4a build number is TQ1A.230105.001, and it's exactly the same for the 4a 5g, 5, 5a, and 6a. The Pixel 6, and 6 Pro are TQ1A.230105.002, and the 7 / 7 Pro are TQ1A.230105.001.A2. So there's minor differences there but for the most part the system images are very similar.
As long as it's for the Pixel 4 (flame) it should be OK. The factory images are named in this fashion: device-buildnumber-factory-hash.zip, so yours should be flame-TP1A.221005.002-factory-f91d46b5.zip
Yeah that's the wrong one
Yep
Yes. Just to make absolutely sure we are on the same page, when you download the file, you'll have the original zip (using barbet for my wife's phone as an example)
View attachment 5812273
Extract this to its own folder, which will have another folder inside it with the bootloader image, radio image, scripts, and the system update:
View attachment 5812283
Extract the "image-sunfish.tp1a.221005.002.zip" to its own folder:
View attachment 5812285
In this folder will be the various images for the system update; the one you need is boot.img:
View attachment 5812289
To get running again without root, just flash this:
fastboot flash boot <drag and drop the boot.img here>
Yep...once you're booted into Android, copy the same boot.img to your phone, making sure to delete any old ones, then patch it in Magisk, copy the magisk-patched_25200-xxxxx.img back to your PC, then flash it the same way you did the boot image.
Click to expand...
Click to collapse
yeah yeah sorry i didn't reply
and thanks so much for the explanation
i was busy setting up my phone
but realized GrapheneOS isn't supposed to have root anyways
so now i have to decide if I want a custom ROM or just Stock with root, or maybe GrapheneOS and whether to put Google services on it and a bunch of apps defeating its purpose in some ways
flashing the phone went very smoothly. Then i put GrapheneOS on it.
if you have any advice about which ROM to do, i'd appreciate it
lots of features are built into Stock now anyways
in that case, i'd just reflash the Magisk patched boot image and then lock the bootloader in settings again?
or i have to reinstall Stock entirely
maybe Android Flash Tool and not that Flash.Android.com
i've done this for multiple phones over the years but i guess i've never understood it thoroughly
i can check for a guide....(and follow it carefully lol)
awesome help. this saved me a bit of stress today.

Never ever lock the bootloader unless everything is 100% bone stock. Not even a patched image. If anything is modified, locking the bootloader will prevent the device from booting Android, and it may not be possible to unlock it again. I'll have more for you on ROMs in the morning, specifically GSIs.

V0latyle said:
Never ever lock the bootloader unless everything is 100% bone stock. Not even a patched image. If anything is modified, locking the bootloader will prevent the device from booting Android, and it may not be possible to unlock it again. I'll have more for you on ROMs in the morning, specifically GSIs.
Click to expand...
Click to collapse
Or I think I got that confused with the Settings menu OEM Unlock
Not the fastboot command.
I just did whatever the GrapheneOS instructions said.

Sanman99 said:
Or I think I got that confused with the Settings menu OEM Unlock
Not the fastboot command.
I just did whatever the GrapheneOS instructions said.
Click to expand...
Click to collapse
Well, GrapheneOS sets a custom root of trust, so as long as nothing is modified, you can relock the bootloader. You won't be able to have root, though. I generally advise against locking the bootloader unless you're on bone stock firmware.
As for ROMs, I don't have a lot of experience with custom ROMs, especially not in the past 6 years or so. My daily is a Pixel 5, and I'm pretty happy with the OEM firmware. I do have a Samsung tablet that I'm running an AOSP Developer Preview GSI on; I had tried LineageOS first, didn't like it that much, then figured out how to install a GSI. The Pixel 3 and newer should be Project Treble compliant, so you could potentially use a GSI if you wanted.
By the way, GSI = Generic System Image. The idea is that it can run on almost any device, utilizing the stock kernel, and does not require porting or any other customizations to get it to run on other devices.