Database Develop

[Q] fastboot flash doesn't work

I am trying to burn stock ROM images on my Nexus One. I am trying to follow instructions in this tutorial http://forum.xda-developers.com/showthread.php?t=614850 but can't get fastboot to flash my ROM with the images nor erase the userdata partition.
When trying
-> fastboot erase userdata
I get "FAILED (remote: not allowed)" message and when trying
-> fastboot flash userimage.img
I get "sending 'userdata' (837 KB)..." but nothing happens even after 10 minutes... This is the same when trying to flash system and boot partition as well.
I can see my device and reboot it using
-> fastboot devices
-> fastboot reboot-bootloader
My HBOOT version is 0.33.0012 and I have this S-ON (can't quite figure out what this means)...
Any ideas?

When in the bootloader does it say HBOOT below the green text or FASTBOOT? You will first need to navigate to the fastboot entry (I think that's what it's called) and press the power button. Your commands should then work.

Hollow.Droid said:
When in the bootloader does it say HBOOT below the green text or FASTBOOT? You will first need to navigate to the fastboot entry (I think that's what it's called) and press the power button. Your commands should then work.
Click to expand...
Click to collapse
It says FASTBOOT USB. I can see the device and do a reboot using the fastboot tool in my PC - only the erase and flash commands don't seem to work.

smichak said:
It says FASTBOOT USB. I can see the device and do a reboot using the fastboot tool in my PC - only the erase and flash commands don't seem to work.
Click to expand...
Click to collapse
Hmmm that's weird, I only got those errors when it said HBOOT. An alternative is to flash the phone using PASSIMG.zip. It will wipe the partitions you are attempting to; userdata, system, boot etc using a completely stock rom and is done via the fastboot menu.
Edit: This is assuming you have an unlocked bootloader?

Did you run 'fastboot oem unlock' first?

Rusty! said:
Did you run 'fastboot oem unlock' first?
Click to expand...
Click to collapse
I am pretty sure my phone is unlocked as I see this open lock icon whenever I reboot it.

Hollow.Droid said:
Hmmm that's weird, I only got those errors when it said HBOOT. An alternative is to flash the phone using PASSIMG.zip. It will wipe the partitions you are attempting to; userdata, system, boot etc using a completely stock rom and is done via the fastboot menu.
Edit: This is assuming you have an unlocked bootloader?
Click to expand...
Click to collapse
Is there a tutorial or something on how to do this (the PASSIMG.zip thing) ? I don't wanna mess things up...

smichak said:
Is there a tutorial or something on how to do this (the PASSIMG.zip thing) ? I don't wanna mess things up...
Click to expand...
Click to collapse
There was but I can't put my finger on it at the moment. However I used this exact method a couple of days ago so it's still fresh:
1) Download FRG33 image format from here. Versions above this as far as I know cannot use the PASSIMG.zip method.
2) Rename to PASSIMG.zip and place in the root of the sd card
3) Reboot/boot to bootloader
4) At this point the phone will recognise the zip file and check its contents.
5) When prompted press the volume button to confirm.
This will return you to stock (Minus the recovery but from the sounds of it you don't have a custom recovery image).

You have to extract the FRG33 file and then rename the new file passimg.zip

OK thanks - the PASSIMG.zip thing did the trick. Now I'm running FRG33 stock. Any tips on how I get from here as quickly as possible to Gingerbread?

smichak said:
OK thanks - the PASSIMG.zip thing did the trick. Now I'm running FRG33 stock. Any tips on how I get from here as quickly as possible to Gingerbread?
Click to expand...
Click to collapse
Using fastboot, flash the custom recovery of your choice. Using that recovery, flash the custom GB ROM of your choice.

Did I really just brick a NEXUS?!?!

Think I may be officially bricked ... tried to sideload the OTA this morning with no luck (looped at Google splash screen). So I flashed the 5.0.1 images and went about my day. Came home and flashed the 5.1 images and looped at the Google splash again ... continued to tinker and play. Long story short, in my idiocy I oem locked. Now I can't flash any .img files cause I am locked, can't unlock because I can't boot into Android and uncheck the stupid box in dev options and trying to sideload the ota .zip again yields: "/dev/block/platform/msm_sdcc.1/by-name/system has been removed R/W; reflash device to reenable OTA updates E:Error in sideload/package.zip (Status 7)" ...
At this point I think I am screwed!! Any suggestions would be GREATLY appreciated!

Can you not get into fastboot and try to OEM unlock that way?

Xaikar said:
Can you not get into fastboot and try to OEM unlock that way?
Click to expand...
Click to collapse
I can get into fastboot but get this when I try to unlock
C:\Android\sdk\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.000s
C:\Android\sdk\platform-tools>​
And of course I cannot check that because I cannot boot into Android

So it currently says device locked?

Xaikar said:
So it currently says device locked?
Click to expand...
Click to collapse
10-4
I can get into stock recovery, but I don't know of anything to flash with the stock recovery and adb sideloading 5.1 isn't working

http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/

There's a thread about this over at the Nexus 9 help forum. Might want to check there.

Xaikar said:
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
Click to expand...
Click to collapse
Can't flash the images while locked, thanks though

ChristianJay said:
There's a thread about this over at the Nexus 9 help forum. Might want to check there.
Click to expand...
Click to collapse
Ah, thanks! Any idea which section?
Edit: Found it!

YankInDaSouth said:
Ah, thanks! Any idea which section?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312

Have you tried booting TWRP from fastboot? Maybe then you could install a ROM to boot into android.
fastboot boot recovery recovery.img

WugFresh Nexus Root Toolkit
Try the "Flash Stock + Unroot" option. It should take you back to square 1.

ajjames01 said:
Have you tried booting TWRP from fastboot? Maybe then you could install a ROM to boot into android.
fastboot boot recovery recovery.img
Click to expand...
Click to collapse
Custom recovery isn't currently on the device ...
Dusty Rhodes said:
WugFresh Nexus Root Toolkit
Try the "Flash Stock + Unroot" option. It should take you back to square 1.
Click to expand...
Click to collapse
Tried that too ... but the .img's cannot be flashed while locked, keeps failing

If you have TWRP on the device can you adb push a ROM to it and flash it so you can boot android and tick the "enable OEM unlock" box.

ajjames01 said:
If you have TWRP on the device can you a ROM to it and flash it so you can boot android and tick the "enable OEM unlock" box.
Click to expand...
Click to collapse
I don't have TWRP, sorry that was a typo. It's stock recovery as I was trying to go fully stock 5.1 ...

@YankInDaSouth
Did you try booting twrp and not flashing it and go from there?
Fastboot boot recovery twrp.img

when Google decided to add the "OEM Lock" checkbox they should have committed to every Nexus device also having SD card capability, not only for the convenience that SD cards bring but also to be able to load the images that way in the event of a catastrophe.
But I guess forcing everyone into buying cloud storage is the new modus operandi.

Try the following commands, one after the other:
fastboot format userdata
fastboot format cache
fastboot reboot-bootloader
fastboot oem unlock (if it works, great, if not, go to the next one below)
fastboot reboot

efrant said:
Try the following commands, one after the other:
fastboot format userdata
fastboot format cache
fastboot reboot-bootloader
fastboot oem unlock (if it works, great, if not, go to the next one below)
fastboot reboot
Click to expand...
Click to collapse
Still get the message about checking the box in dev options ...

Not sleeping tonight huh bro? I know the feeling when this **** happens, it sucks. I think someone will come up with a work around, a lot of brains around here.
Sent from my Nexus 9 using XDA Free mobile app

nexus 6 can not run the system

nexus 6 can not run the system, only the logo on the screen does not move
I tried to brush oem unlock firmware but failed.
I guess I broke the Recovery partition.
How can I do it? Help me!:angel::angel:

Please give a bit more detail about your setup and what happened before this

rootSU said:
Please give a bit more detail about your setup and what happened before this
Click to expand...
Click to collapse
I installed android 5.1.
root
Installed TWRP Recovery
Then I run "fastboot oem lock" this time we can not normally enter the system.
I found that running fastboot -w can enter the system, so I entered the "TWRP Recovery" to restore the backup method used to restore a backup Recovery partition.

So, let me get it straight...
You unlocked the bootloader
You then rooted
Installed recovery
THEN relocked the boot loader?
...why?
You won't be able to do anything to any partition until the boot loader is unlocked again - try that. Unlock the boot loader (make sure to enable it in Dev settings) and then it should all work again.

Good job, I think you bricked yourself.
Not sure if anyone found a work around for this.
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497

Leo D said:
nexus 6 can not run the system, only the logo on the screen does not move
I tried to brush oem unlock firmware but failed.
I guess I broke the Recovery partition.
How can I do it? Help me!:angel::angel:
Click to expand...
Click to collapse
If you have TWRP recovery installed and ONLY if you have TWRP installed, boot into bootloader. Issue the fastboot commands:
fastboot format userdata
fastboot format cache
If you do have TWRP installed, this should allow you to boot to TWRP recovery.
See if you can accomplish this and let us know.

Evolution_Freak said:
If you have TWRP recovery installed and ONLY if you have TWRP installed, boot into bootloader. Issue the fastboot commands:
fastboot format userdata
fastboot format cache
If you do have TWRP installed, this should allow you to boot to TWRP recovery.
See if you can accomplish this and let us know.
Click to expand...
Click to collapse
I went into recovery mode, nothing happens.
View Bootloader logs
Invalid boot image size!
failed to validate recovery image
Boot up failed

iRub1Out said:
So, let me get it straight...
You unlocked the bootloader
You then rooted
Installed recovery
THEN relocked the boot loader?
...why?
You won't be able to do anything to any partition until the boot loader is unlocked again - try that. Unlock the boot loader (make sure to enable it in Dev settings) and then it should all work again.
Click to expand...
Click to collapse
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.028s
Options appear before acceptance and rejection does not appear on the phone screen.

You probably bricked it.
It's been known to happen after 5.1 if you're not careful (or, in this case, relock the BL after modifying)
Why did you relock it? I still can't wrap my head around any reason for doing that?
Sent from my Nexus 6

Leo D said:
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.028s
Options appear before acceptance and rejection does not appear on the phone screen.
Click to expand...
Click to collapse
The phone is bricked. RMA to Motorola

Or if you're feeling adventurous: http://forum.xda-developers.com/showthread.php?t=3059518

brando56894 said:
Or if you're feeling adventurous: http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
Thanks for your help. But there are some questions I still do not understand.
Now the phone connected to the computer and did not see QHSUSB_BULK in Device Manager. In the Device Manager to see BootLoader interface or adb interfaces.
How can I make the phone run QHSUSB_BULK state?

stuck in fastboot, cant flash anything, cant go to recovery

my phone: Nexus 6 32gb international
marshmallow (MRA58R) with cataclysm rom
twrp custom recovery and elementalx kernel
rooted, unlocked bootloader, no xposed
1. my phone was running fine until it randomly crashed and got stuck in fastboot menu. trying to start does nothing but in bootloader logs it shows this:
Code:
failed to validate boot image ret=-1
trying to reboot recovery gives:
Code:
failed to validate recovery image ret=-1
so i guess time to flash a MRA58R factory image right? however:
2. trying to flash via "flash all" script, manual one by one flash, or using the nexus root toolkit gives:
Code:
<bootloader> failed to flash partition
FAILED <remote failure>
this happens when i try to flash recovery (Stock or twrp) or bootloader or bootimage or system or anything. i have to my knowledge adequate platform tools setup which ive used multiple times before. my sdk tools are updated as well. at this point ill try anything. and i use windows. please help

Osaab said:
my phone: Nexus 6 32gb international
marshmallow (MRA58R) with cataclysm rom
twrp custom recovery and elementalx kernel
rooted, unlocked bootloader, no xposed
1. my phone was running fine until it randomly crashed and got stuck in fastboot menu. trying to start does nothing but in bootloader logs it shows this:
Code:
failed to validate boot image ret=-1
trying to reboot recovery gives:
Code:
failed to validate recovery image ret=-1
so i guess time to flash a MRA58R factory image right? however:
2. trying to flash via "flash all" script, manual one by one flash, or using the nexus root toolkit gives:
Code:
<bootloader> failed to flash partition
FAILED <remote failure>
this happens when i try to flash recovery (Stock or twrp) or bootloader or bootimage or system or anything. i have to my knowledge adequate platform tools setup which ive used multiple times before. my sdk tools are updated as well. at this point ill try anything. and i use windows. please help
Click to expand...
Click to collapse
Is the phone unlocked?
Code:
fastboot oem unlock
Can you erase userdata and cache
Code:
fastboot -w

mywindow said:
Is the phone unlocked?
Code:
fastboot oem unlock
Can you erase userdata and cache
Code:
fastboot -w
Click to expand...
Click to collapse
the phone is unlocked. it shows unlocked status 3 or something. and no -w gives the same error (failed to flash partition).
i was wondering i dont remember if i had "allow oem unlocking" enabled in the dev options and now i cant access it. is there a way that can be a problem?

Osaab said:
the phone is unlocked. it shows unlocked status 3 or something. and no -w gives the same error (failed to flash partition).
i was wondering i dont remember if i had "allow oem unlocking" enabled in the dev options and now i cant access it. is there a way that can be a problem?
Click to expand...
Click to collapse
I doubt it, since you don't need to unlock it a little more.
You should check your USB cable, or try to switch to another port. But if the error still persists, you need to send it to repair.

I am sorry mate, but u might have to send it in for real
Maybe your nand memory is corrupted. Since ur phone just crashed for "no reason" and then got stuck in fastboot, it may be an indicator for that.
Best regards!

Osaab said:
the phone is unlocked. it shows unlocked status 3 or something. and no -w gives the same error (failed to flash partition).
i was wondering i dont remember if i had "allow oem unlocking" enabled in the dev options and now i cant access it. is there a way that can be a problem?
Click to expand...
Click to collapse
I BELIEVE once you tick it and unlock, it does not turn back off (allow OEM unlock)
But as said above, this option only allows the bootloader to accept the unlock command...
Best case is the internal storage got scrambled and your partitions/ partition table is corrupt/missing/gone, worse case and maybe more likely is hardware failure?
Not sure if you can send terminal commands, but next step is either just RMA or searching the internet for a way to manually rebuild partition table from bootloader?
I guess?
Sounds like it messed it self up pretty good somehow, sorry man.

Mi A2 has not slot b

As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.

gfpablo_ said:
As I say in the tittle, my phone has not slot b. It means that when I try to flash any .img or .zip I have an error message telling my that "XXX_b not accesible".
How can I create the partition? I have android one and everything locked as I flashed the stock image vía COM because I have no idea how to solve the partition problem.
Click to expand...
Click to collapse
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.

Catsonvi said:
You say you are trying to flash something but then you also say that everything is locked. You can't flash anything other than the stock firmware (in EDL mode) if your bootloader is locked.
Click to expand...
Click to collapse
I tried to flash it when i have everything unlocked. I tried to flash ASOP v6.6 and the result was a bricked phone. However I flashed the android one stock ROM and locked everything with the Xiaomi flash program.

You need to flash stock through EDL

Nebrassy said:
You need to flash stock through EDL
Click to expand...
Click to collapse
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b

gfpablo_ said:
That's what i've done. Although, if I try to flash TWRP from fastboot I have an error message telling me that I have no slot b
Click to expand...
Click to collapse
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375

[SOLVED]
Catsonvi said:
You can't flash the TWRP image from fastboot, since our phone does not have a seperate recovery partition and you also cannot flash ANYTHING (other than stock via EDL) if your phone's bootloader is locked.
Now since it seems that your bootloader is locked, you need to enable developer options first and then in developer options enable the "OEM unlocking" option. After that you need to go to fastboot in order to unlock the bootloader and use these commands one at the time:
fastboot flashing unlock
fastboot flashing unlock_critical
Keep in mind that after using these commands you will get a prompt on your phone to confirm that you want to unlock the bootloader and doing so will erase everything (basically like doing a factory reset).
After you fully unlock the bootloader, in order to flash TWRP with stock you need to go to the official TWRP website and find the .img and the .zip installer for the Mi A2. You need to boot the .img via fastboot with fastboot boot *location to the .img* (without the asterisks) and then transfer and flash the TWRP .zip installer with TWRP. After that you can boot into TWRP normally without fastboot booting.
If you want to flash a custom ROM you will still need to fastboot boot into the TWRP .img because the .zip you flashed is tied to the system, and since you need to wipe the system before flashing a custom ROM you will also wipe the flashed TWRP.
I still recommend reading this guide: https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
Click to expand...
Click to collapse
Thank you! I have to admit that I have no idea of whats wrong earlier. This guide solved the problem tho.