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.
Related
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
*UPDATE* - Sorry, forgot to mention that I've idiotically re-locked the bootloader. Unlocking the bootloader would probably get rid of the "signature verify fail" message. I'm unable to flash the recovery because the bootloader is locked and I can't get into the filesystem because the phone needs to go into the OS for that.
When I try to unlock the bootlader by using "fastboot flash unlocktoken Unlock_code.bin" it gives me the error: "cannot open 'Unlock_code.bin'."
I need to be able to access and make changes to the file system by using fastboot commands and I have no idea how to do this.
*UPDATE #2* - I've managed to re-unlock the bootlader (I didn't have the Unlock_code.bin file in the same directory as the current directory in my cmd window). I've re-flashed the recovery successfully. Now when I reboot, it goes into recovery mode (still can't boot into the OS). I'm using ClockWorks for the recovery.
Now I'm unable to root the phone. I'm trying to write SuperSU v1.65 to the phone by using the command: "fastboot flash zip UPDATE-SuperSU-v1.65.zp" and I get the error message: "remote: not allowed."
I can flash the recovery.img and boot.img (can't flash system.img because there's "not enough space"), but I can't flash .zip files
When I try flashing another boot.img, I still get the same thing. The phone goes to the boot screen and can't boot. Then, it reboots and goes automatically into recovery (I can still get into the bootloader and recovery).
Any suggestions to get past these permissions?
bkhosh2 said:
Hi guys,
I've searched the entire web (including all the XDA links regarding the HTC One), tried every solution out there and still can't fix my problem. I don't know where else to turn, so I am creating a new thread in XDA Developers.
Originally, I had unlocked my bootloader and rooted the phone to use stock android. A couple days ago, I tried to re-lock the bootloader and change back to the original Sense UI; however, when I did this, I got stuck in a boot loop (the phone kept rebooting and didn't boot into the OS).
I then went back into fastboot and restored all the files and settings.
Now, the only things I can actually go into is fastboot and bootloader (cannot boot into OS or even see the boot screen). The only way the phone can connect to my PC is if I'm in fastboot. When I go into bootloader, the phone disconnects from my PC.
My phone is from Telus in Canada and I can find a couple .zip RUU files on the web for Telus, however when I try to flash the phone using the command "fastboot flash zip filename.zip", I get the error "signature verify fail."
When I tried to use the RUU.exe from BrightStar (developer version), the update failed and there was a message saying to download the original firmware.
The last thing I tried was the command "fastboot oem rebootRUU" (I did this to change the CID and MID, so I could use the Google Play RUU). When I do this, it goes to a black boot screen that has the HTC logo in grey (this is the boot screen I got from trying to use the BrightStar RUU.exe. It was originally a white screen with the HTC logo in green.). When I'm at this screen, I can communicate with the phone using fastboot commands, however when I try to change the CID, I get the error: "status read failed (too many links)," and when I try to change the MID, I get the error: "Command error !!!"
Just to remind you guys, I can only communicate with the phone using fastboot commands. No adb.
I have officially given up and gone crazy! Please Help!!!
Click to expand...
Click to collapse
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
superbellefleche said:
Try command "fastboot erase cache", then try to re-flash an other recovery (recommended : twrp 2.6.3.3)
Click to expand...
Click to collapse
I'm sorry, but I'm kind of a noob. How exactly do I re-flash a recovery. do I do this using the command: "fastboot flash recovery recovery.img" or should I try "fastboot flash zip filname.zip" (RUU.zip) again?
*UPDATE* - I've tried erasing the cache and re-flashing the recovery and I still get the error message: "signature verify fail."
I'm still waiting for someone to help me. Is anyone going to help me fix my problem or is my HTC One doomed?
If you are on Telus
Download http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
SaHiLzZ said:
If you are on Telus
Relock your bootloader
Then
fastboot oem rebootRUU
fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1_R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336571_signed_2_decrypted.zip
May have to run the flash zip command twice..
Click to expand...
Click to collapse
I've already tried that. When the bootloader is locked, I get the error: "signature verify fail."
OK.. Unlock bootloader, flash custom recovery, adb push this file: http://www.htc1guru.com/2013/11/guru-reset-3-22-661-1/, and install it from recovery.
SaHiLzZ said:
OK.. Unlock bootloader, flash custom recovery, adb push this file
Click to expand...
Click to collapse
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
bkhosh2 said:
I can't use adb commands...
I have all kinds of USB drivers installed (including the one from SDK Manager). When I type in the command "adb devices", I get nothing.
Click to expand...
Click to collapse
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
clsA said:
adb commands will work if your in twrp recovery
and the reason your ruu.zip failed is because you were not in fastboot oem rebootRUU when you tried them, seems you mixing and matching different forums of flashing .. it don't work like that.
Click to expand...
Click to collapse
I Installed the TWRP recovery instead of the ClockWorkMod and adb command work! Never using ClockWork ever again!
SaHiLzZ said:
Just to re-iterate..
1. fastboot oem rebootRUU (this will show a gray HTC logo on black screen)
2. fastboot flash zip RUU_ZIP_M7_UL_JB43_SENSE50_MR_TELUS_WWE_3.22.661.1 _R3_Radio_4A.20.3263.16_10.38k.1157.04_release_336 571_signed_2_decrypted.zip
May have to run #2 again if it shows flush error..
Click to expand...
Click to collapse
I Installed TWRP and went into the TWRP recovery and noticed the adb commands work.
That file didn't work, however the Guru file you mentioned earlier did (with the "adb push" command)! Thanks so much for your help! Everything is working perfectly again!
Thanks for posting back. Edit your title to [SOLVED]! and enjoy!
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, 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 installed the CM11 for this phone, I know not perfected yet, but it started having issues so I figured I would just go back to non-sense and be done with my CM11 trial.
At first I was just having trouble mounting DATA, then after a few reboots into TWRP 2.8.7.0 -- I lost my CACHE partition as well.
I tried using the RUU, but failed for SECURITY. I can't flash any ROMS (no DATA / CACHE) -- So I am stuck. FASTBOOT works, and I have access via TWRP, but thats it.
Carrier is Virgin Mobile.
Phone is U.S. 32-bit
Been rooted and working since we got root.
Any advice on how to proceed? Can I rebuild partitions from inside TWRP (command line?) can I find something that can be FASTBOOT or installed some other way?
Going back to stock is fine for now, what I am shooting for since it got all buggered up. And no I can't install BACKUPS either. Need partition access first..
Sorry, I think ADB is working, just can't do anything again because of the inability to mount the DATA & CACHE partitions.
The RUU failed by security because you have bootloader unlocked. Try to re-lock bootloader and re-install the RUU. That should work fine.
Been a while since I messed with this model, how do I re-lock bootloader?
****derp.
To re-Lock your bootloader Load phone into FASTBOOT and issue fastboot oem lock from command prompt. Phone will reboot and show RELOCKED.
Reboot phone in fastboot.
In adb, check with "fastboot devices" that your device is connected.
Then, in adb, type:
Code:
fastboot oem lock
And now you will have bootloader relocked.
PS: The phone only will reboot in Bootloader. That's because you don't have any OS installed.
To install the RUU, only plug the phone in fastboot and open the RUU program.
Thanks for help. seems all better now.
I have the Moto Nexus 6 (xt1100) with TRWP installed no backup saved, OEM bootloader locked and no OS currently on the phone and i cant reflash nethunter or any stock roms through TRWP or fastboot. PLZ HELP ME OUT.
You could to install by adb sideload some full ota.
There is a Android N preview that could be applied by adb sideload, once you have access to your phone, you could unlock bootloader and apply any other rom
lulzwolf said:
I have the Moto Nexus 6 (xt1100) with TRWP installed no backup saved, OEM bootloader locked and no OS currently on the phone and i cant reflash nethunter or any stock roms through TRWP or fastboot. PLZ HELP ME OUT.
Click to expand...
Click to collapse
Push a custom rom to your phone and flash it in TWRP. Command: adb push namerom.zip /sdcard/, or sideload a custom rom in also in TWRP recovery. And don`t ever relock your bootloader again if you are flasher If you have enabled ENABLE OEM UNLOCK in developer options its best to unlock it first
gee2012 said:
Push a custom rom to your phone and flash it in TWRP. Command: adb push namerom.zip /sdcard/, or sideload a custom rom in also in TWRP recovery. And don`t ever relock your bootloader again if you are flasher If you have enabled ENABLE OEM UNLOCK in developer options its best to unlock it first
Click to expand...
Click to collapse
He can't flash any ROM with a locked bootloader.
You should be able to fastboot flash a stock image, but if your fastboot isn't working then you're kinda screwed.
All I can say is give the fastboot flash another try, maybe from a different PC. Use method 2 in this guide to return to stock, then use the stock recovery to factory reset and boot it up
noidea24 said:
He can't flash any ROM with a locked bootloader.
You should be able to fastboot flash a stock image, but if your fastboot isn't working then you're kinda screwed.
All I can say is give the fastboot flash another try, maybe from a different PC. Use method 2 in this guide to return to stock, then use the stock recovery to factory reset and boot it up
Click to expand...
Click to collapse
I tried Macon's method but i am still unable to flash the phone back to stock. The OEM bootloader is locked and i cant access it without an OS installed. Is there a way i can bypass the OEM bootloader aka hack/root the phone to reflash it?
It should work if you run these commands (with the phone in bootloader) prior to flashing the custom rom zip in TWRP:
Fastboot format cache
Fastboot format userdata
Didgeridoohan said:
It should work if you run these commands (with the phone in bootloader) prior to flashing the custom rom zip in TWRP:
Fastboot format cache
Fastboot format userdata
Click to expand...
Click to collapse
"""
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
"""
"""
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
sending 'userdata' (139061 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
"""
Im still locked out of the bootloader. how do i circumvent the OEM bootlock? can i hack pass it? it is password protected somewhere, if it is can i bruteforce the password? how can i get pass it guyz?!?!
The OEM bootloader is locked and i cant gain access to the developer optios because i dont have an OS to boot into. Im looking for a way i can "bypass" "circumvent" "hack" "disable" or any other word you can think of to get around the bootloader lock and flash my phone. i can start an "adb shell" and gain access to the command line on the phone, but i dont know where i can find the "OEM Bootloader" part of the phone for modification. I have also tried running "fastboot oem get_unlock_data" but it says "(bootloader) This command is not needed to unlock. Run fastboot oem unlock" WTF.... DAMMIT FUK FUK FUK FUUUUUUUUUUUUUUUUUUUUUUUUUUJK
"""
The command i used below and its output message.
"""
[email protected]# fastboot oem unlock
"""
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.005s
"""
lulzwolf said:
"""
Created filesystem with 11/16384 inodes and 2089/65536 blocks
sending 'cache' (6248 KB)...
writing 'cache'...
(bootloader) Unlock before flashing
"""
"""
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
sending 'userdata' (139061 KB)...
writing 'userdata'...
(bootloader) Unlock before flashing
"""
Im still locked out of the bootloader. how do i circumvent the OEM bootlock? can i hack pass it? it is password protected somewhere, if it is can i bruteforce the password? how can i get pass it guyz?!?!
Click to expand...
Click to collapse
Sorry to hear that... The suggested method used to work for people unable to unlock their bootloader due to not having the setting checked in developers settings (if they had TWRP installed, of course).
I do believe you are screwed...
@lulzwolf: Contact Motorola and/or Google, because you screwed yourself by not leaving "Enable OEM Unlock" checked after you modified the firmware. There is no way to brute force the lock, unless you happen to be immortal. The encryption on the bootloader is sufficiently strong that you'll be dead long before a computer could successfully unlock it.
Lesson of the day folks: if you modify your Nexus 6, even if only to root it, leave "Enable OEM Unlock" checked! Yes, it will make your device less secure since a knowledgeable person can flash a factory image, but it's better than being permanently locked out of the device.
Just flash any rom trough TWRP. For god's sake, it even supports MTP. What's your problem?
@Lawstorant: Did you read the thread? His bootloader is locked, meaning he cannot flash anything.
@Strephon Alkhalikoi
It doesn't work that way. Locked bootloader only means that he cannot flash anything using fastboot, but he clearly said that he has TWRP. TWRP doesn't relay on fastboot (common knowledge 1) because it's a totally seperate thing, hence locked bootloader doesn't affect TWRP in any way. He can still do anything he likes. The simplest solution is to flash ANY rom trough TWRP and unlock bootloader with "Boot unlocker" app.
Locked bootloader means you cannot use fastboot, partitions are not unaccesible.
1. If you lock your Windows OS with password you can't acces it, but if you have Linux there's nothing that prevents you from browsing filse on windows partition (only encryption, but still, you can wipe it and put in, anything you want).
TL;DR You're wrong, go learn some more.
@Lawstorant, your attitude and tone need a bit of adjustment. If I am wrong, that's one thing. There is however no need to be a smart ass about it, especially with the TL;DR bit. It's juvenile, and uncalled for. That said, you are correct in that lulzwolf may not be totally screwed. Virtually everyone, including myself, has assumed he has to flash a stock image, but he really doesn't. We'll need him to answer one way or another, but the instructions to restore his device are as follows.
Boot into bootloader.
Use fastboot and issue the following commands: fastboot format userdata, fastboot format cache.
Reboot into TWRP.
Flash a custom ROM.
Unlock the bootloader, and leave it unlocked.
lulzwolf did in fact get at least as far as the two fastboot commands, but he does not say whether he got back into TWRP. Now that he has gotten the userdata and cache formatted he should be able to boot into TWRP and install a custom ROM. From there he should be able to unlock the bootloader.
So @lulzwolf, where are you getting stuck? You may not be done yet, as I erroneously assumed.
@Lawstorant: Did you read the thread? His bootloader is locked, meaning he cannot flash anything.
Click to expand...
Click to collapse
no need to be a smart ass about it,
Click to expand...
Click to collapse
formating trough fastboot won't succed, because he needs access to these partitions. Why would anyone even recommend fastboot when bootloader is locked? He's better of formatting them trough TWRP.
TWRP is answer to all questions. I don't even know why he's tinkering with his phone if he can't figure it out on his own.
Ask The_Merovingian. He wrote the guide. I simply copied it from his thread.
However, you and I do agree on one very important thing. If he doesn't know what he's doing he shouldn't be messing about with his phone, period. He did say in his opening post that he couldn't flash ROMs through TWRP, but given what's been posted, there shouldn't be any reason he can't flash a ROM, except he has a bigger issue than not having the OS.
Ok so i have solved my problem by installing a custom ROM called "Cataclysm" through the TRWP recovery tool. My problem was I tried flashing to stock with fastboot when fastboot had no access to the partitions. so i used adb to push a custom ROM and installed it in TRWP.... BOOM it was fixed! so in conclusion we have learned that fastboot cannot access partitions while the OEM bootloader is locked but TRWP can. thank you all for commenting and helping me out, and hopefully this thread can help out others who run across this problem in the future.
lulzwolf said:
I have the Moto Nexus 6 (xt1100) with TRWP installed no backup saved, OEM bootloader locked and no OS currently on the phone and i cant reflash nethunter or any stock roms through TRWP or fastboot. PLZ HELP ME OUT.
Click to expand...
Click to collapse
rofl, way to go
lulzwolf said:
Ok so i have solved my problem by installing a custom ROM called "Cataclysm" through the TRWP recovery tool. My problem was I tried flashing to stock with fastboot when fastboot had no access to the partitions. so i used adb to push a custom ROM and installed it in TRWP.... BOOM it was fixed! so in conclusion we have learned that fastboot cannot access partitions while the OEM bootloader is locked but TRWP can. thank you all for commenting and helping me out, and hopefully this thread can help out others who run across this problem in the future.
Click to expand...
Click to collapse
Which is exactly what gee2012 suggested that you should do in the second reply to your cry for help. (And at least I assumed you had tried without success. Serves me right for assuming...)
Glad it worked out. :good:
I hope you learned more than just that from this exercise. I know I did, namely a reminder to "practice what I preach". I tell people like you to search before posting and I failed to do just that. Mea culpa.