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
Related
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.
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?
I had a stock Nexus 6 onto which I loaded the MarshMallow previews.
I then decided to go back to 5.1.1 on the basis of the final release using the following:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot flash system system.img
Once I had entered the final fastboot command I also stupidly entered the command to lock the bootloader prior to rebooting
Some thing went wrong and now the phone sits on the google (while letters on black background) screen on bootup.
What are my options? I can access the bootloader, but its not showing up as a device on the on "adb devices"
Any assistance would be appreciated.
Sorry to say, but you've got a paperweight.
If by some chance you switched out the stock recovery.img with TWRP you're good, but otherwise, nope.
And in bootloader you use fastboot, as in "fastboot devices", not adb.
Boot to bootloader, unlock bootloader via fastboot (not adb!) and then move on from there (flash twrp, custom Rom or factory image).
petermuell said:
Boot to bootloader, unlock bootloader via fastboot (not adb!) and then move on from there (flash twrp, custom Rom or factory image).
Click to expand...
Click to collapse
Problem is that he can't go into settings and tick "OEM Unlocking" (due to phone not booting). Even if it was ticked prior to flashing, I don't think it stays that way after flashing a factory image. I've never tried it myself so this is of course pure speculation. It might be worth a shot.
Didgeridoohan said:
Problem is that he can't go into settings and tick "OEM Unlocking" (due to phone not booting). Even if it was ticked prior to flashing, I don't think it stays that way after flashing a factory image. I've never tried it myself so this is of course pure speculation. It might be worth a shot.
Click to expand...
Click to collapse
Thats a good point. I know when 5.1.0 came out, the OEM unlock option didn't persist after a reboot even, but does since 5.1.1.
My assumption would be it does survive a factory flash, because that data is stored in a partition that isn't touched by flashing a factory image, but like you, I have never tested it.
danarama said:
Thats a good point. I know when 5.1.0 came out, the OEM unlock option didn't persist after a reboot even, but does since 5.1.1.
My assumption would be it does survive a factory flash, because that data is stored in a partition that isn't touched by flashing a factory image, but like you, I have never tested it.
Click to expand...
Click to collapse
Hmm... This got interesting. It should survive a factory flash then.
@mittu1 Did you have OEM unlock allowed prior to locking your bootloader? If so, please, please, please run the command fastboot oem unlock and return with the result.
Yes, if you have stock recovery and can't unlock bootloader (probably because "allow OEM unlock" was not checked, or whatever reason), then you're pretty much stuck. Maybe then try this: http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
I think it was intended for people who had downgraded their bootloader accidentally.
There is a zip file for flashing that toggles the "allow OEM unlock" flag (http://forum.xda-developers.com/showpost.php?p=61258590&postcount=352). If you can boot to twrp and flash a zip from the computer, flash that file, then boot to bootloader and unlock BL via fastboot.
I've read somewhere that In the "fastboot format cache" and "fastboot format userdata" work even on locked bootloaders. I haven't tried it personally, is this true?
istperson said:
I've read somewhere that In the "fastboot format cache" and "fastboot format userdata" work even on locked bootloaders. I haven't tried it personally, is this true?
Click to expand...
Click to collapse
If you have a custom recovery (TWRP) you can, after running those commands, flash a rom through TWRP and then proceed to boot up, tick "OEM Unlocking", unlock and do whatever you then intended to do.
Edit: Or use the above mentioned zip to toggle the "OEM Unlock"-thingy...
As i understood the OP the recovery is stock also. But somebody wrote the above, and as last resort it could be tried. And if it's false info, then let's have it clarified.
istperson said:
I've read somewhere that In the "fastboot format cache" and "fastboot format userdata" work even on locked bootloaders. I haven't tried it personally, is this true?
Click to expand...
Click to collapse
They should, but if not, a foctory reset can be done from stock recovery. Select recovery mode, then at the Android press power and then volume up. Then select the factory reset from the menu. See if it boots after that
BUT try fastboot oem unlock first, if you wipe without that and then try to unlock I think it'll fail to unlock
Didgeridoohan said:
Hmm... This got interesting. It should survive a factory flash then.
Click to expand...
Click to collapse
No, it is just my assumption. I am not aware if something in first boot process unchecks that option.
Also, FYI, many of us have noticed that when we bought Nexus 6 and unboxed it, booted straight to bootloader, it would unlock, but after first boot on 5.0, had to enable OEM unlock in settings... so maybe first boot process after a "wipe" resets?
Will try and revert
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.
I was trying to install stock rom after installing RR rom. MiFlash said "flashing is not allowed for critical partitions" and when i did "fastboot flashing unlock_critical" from cmd i got "remote: Flashing Unlock is not allowed". I then used the allinone tool from xda and pressed "lock loader" to unlock it again and ended up bricking the device as it now shows "your device is corrupt. it can't e trusted and will not boot" I can't enter recovery either only fastoot and nothing works. PLEASE HELP FAST
have you tried flaashing via edl mode ?
medkim said:
have you tried flaashing via edl mode ?
Click to expand...
Click to collapse
how to do that
Hammad1029 said:
how to do that
Click to expand...
Click to collapse
reboot into edl mode and flash stock rom by mifilash tool
medkim said:
reboot into edl mode and flash stock rom by mifilash tool
Click to expand...
Click to collapse
how do I reboot into edl mode without dissembling the phone
Hammad1029 said:
how do I reboot into edl mode without dissembling the phone
Click to expand...
Click to collapse
reboot into bootloader then issue this command via adb
fastboot oem edl
medkim said:
reboot into bootloader then issue this command via adb
fastboot oem edl
Click to expand...
Click to collapse
it gives "FAILED (remote: 'Device is already locked!')"
@__harmeet reply here please
Hammad1029 said:
it gives "FAILED (remote: 'Device is already locked!')"
Click to expand...
Click to collapse
friend
first of all, you shoud unlock the bootloader
try with this guide
medkim said:
friend
first of all, you shoud unlock the bootloader
try with this guide
Click to expand...
Click to collapse
@Hammad1029 He Is Right, Firstly Unlock The Bootloader, Then Unlock Its Critical Partition And Boot Up Into EDL Mode By Typing "fastboot oem edl#
medkim said:
friend
first of all, you shoud unlock the bootloader
try with this guide
Click to expand...
Click to collapse
have tried already it says "FAILED (remote: Flashing Unlock is not allowed"
bump...
Dude, how many threads do you need to create, it won't make it any more likely that anyone will help you
Your problem is caused by that you only unlocked the bootloader and not critical partitions
Which stock rom were you on before flashing a custom one?
Nebrassy said:
Dude, how many threads do you need to create, it won't make it any more likely that anyone will help you
Your problem is caused by that you only unlocked the bootloader and not critical partitions
Which stock rom were you on before flashing a custom one?
Click to expand...
Click to collapse
I created the 2nd thread in desperation of restoring my only phone so sorry. How do I unlock the ootloader it shows the error I mentioned above
Hammad1029 said:
I created the 2nd thread in desperation of restoring my only phone so sorry. How do I unlock the ootloader it shows the error I mentioned above
Click to expand...
Click to collapse
I asked you what stock rom you were on
Nebrassy said:
I asked you what stock rom you were on
Click to expand...
Click to collapse
10.0.2
Hammad1029 said:
10.0.2
Click to expand...
Click to collapse
Are you sure?, if so, manually flash boot, system and vendor using fastboot to your current slot
Fastboot flash boot_a boot.img
Or boot_b if active slot is B etc...
Then go to developer options and enable oem unlocking, if you can't enable that option, lock the bootloader, enable the option then unlock bootloader and critical flashing
Nebrassy said:
Are you sure?, if so, manually flash boot, system and vendor using fastboot to your current slot
Fastboot flash boot_a boot.img
Or boot_b if active slot is B etc...
Then go to developer options and enable oem unlocking, if you can't enable that option, lock the bootloader, enable the option then unlock bootloader and critical flashing
Click to expand...
Click to collapse
can I claim warranty on this issue
Hammad1029 said:
can I claim warranty on this issue
Click to expand...
Click to collapse
Hi , sorry for my bad English , if you can open you phone and enter to EDL MODE and flash the stock rom of your device may be solve your problem ,
(I get the same problem trying to install a custom rom)
If you can't acces to EDL via ABD i think that you only can enter to EDL disasembly your phone .. Suertee xd
Yo también me desesperé
same problem
i got the same problem, won't start normally, hangs in boot screen so can't enter the phone to put it in usb debugging, only responce is through fastboot mode. Every attempt is failing due to locked state and unlocking is not allowed.