Database Develop

[Q] Can't boot into recovery HTC one

Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
EDIT & ANSWER;
Sprint phone needed Sprint TWRP image

Have you tried
fastboot erase cache

BenPope said:
Have you tried
fastboot erase cache
Click to expand...
Click to collapse
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"

ryryzz said:
This.
Just do evrything again until you finish installing custom recoveries. Before rebooting, erase the cache with "fastboot erase cache"
Click to expand...
Click to collapse
Gave that all a shot all over again. Still can't boot into recovery

Is fast boot off?

Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
BenPope said:
Is fast boot off?
Click to expand...
Click to collapse
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium

hardstuffmuc said:
Use the original cable your One came with, go into bootloader power/vol - then open a cmd window
Now connect the One with your computer, don't use a USB 3.0 connection, and a different one then before.
In bootloader choose fastboot, that should change to fastboot USB
In cmd window point to your fastboot directory where you also copied the recovery to, I would try CWM touch for now.
Type cd c:\fastboot (or what your toolfolder is called)
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That installs the recovery, you can select it in bootloader abd boot into it.
Sent from my HTC One using xda premium
---------- Post added at 06:28 PM ---------- Previous post was at 06:23 PM ----------
You mean the fastboot option under Power Settings is unticked when booted up normally?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Same deal. On it's way to booting into recovery it goes blank, resets and reboots into system

C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.078s]
finished. total time: 0.078s
C:\adt\sdk\platform-tools>fastboot flash recovery recovery.img
sending 'recovery' (7422 KB)...
OKAY [ 1.139s]
writing 'recovery'...
OKAY [ 0.640s]
finished. total time: 1.778s
C:\adt\sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.062s]
finished. total time: 0.062s
C:\adt\sdk\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.047s
There's the last log - and then on it's way to recovery there's a red disclaimer and a pink text saying "Entering Recovery"...then after 20 seconds it resets

Did you try various recovery (versions) ? May be , you just have corrupted recovery image.

tash2013 said:
Did you try various recovery (versions) ? May be , you just have corrupted recovery image.
Click to expand...
Click to collapse
at this point I've tried stock, twrp and cwm. All with the same results

Jman12000 said:
at this point I've tried stock, twrp and cwm. All with the same results
Click to expand...
Click to collapse
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.

tash2013 said:
Ok , I see mysterious problem ))
Try, remaining unlocked, go back to s-on (you can always take s-off again) and check your recovery (enter and flashing) under s-on.
Click to expand...
Click to collapse
Is that something I can do with the revone binary? To be honest, I have no idea how to turn security back on. I can relock it and that may be about it.
I stumbled upon another thread, shares a common theme as my issue, but with a different twist. Using a superboot.img as a rooting method instead of flashing it via recovery. It somewhere says that the boot.img needs to be flashed as well, however I can't find a decent boot.img to flash. The superboot tool seems like unproven territory right now.
Here's the other thread, I've leafed through it and found no determinable answer for my particular issue.
http://forum.xda-developers.com/showthread.php?p=39852757#post39852757

Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.

Jman12000 said:
Hi -
Thanks for any help in advance. I'm a bit of a rookie round here, I've rooted and flashed my past 3 HTC phones but taken the easy route every time.
But today, I've used ADB commands to flash the revone binary and unlock and get s-off on my HTC one m7. It took me several tries, but it eventually worked (or at least said successful). So my HBOOT 1.44 says UNLOCKED & S-OFF.
So onto the next step. fastboot flash recovery recoverytwrp.img
...
Another success!
So, I reboot into bootloader and prompt recovery boot like I'm about to get HAM on twrp and flash some superuser files. It shows me a developer screen full of red print saying that it's booting into recovery, and then after a while, it just rebooted back into system.
It does this every time. I reflashed the image, I flashed the stock image, I tried the hansoon tool. each time I can't actually get into the recovery.
So this is where I'm stuck. Why can't I get anywhere with this?
Click to expand...
Click to collapse
try to install recovery again
you can download recovery from here
http://www.clockworkmod.com/rommanager

tash2013 said:
Do not apply revone to return s-on!
Use fastboot by "fastboot oem writesecureflag 3".
Be convinced that bootloader is unlocked before return to s-on.
Regarding your issue: I suspect that a certain code in HBOOT tries to install TAMPERED flag when sees custom recovery, but isn't able to do it correctly because s-off (bypassing security) and a certain mistake or exception conducts to reset phone.
Click to expand...
Click to collapse
Code:
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot oem writesecureflag 3
...
(bootloader) writesecureflag: partitions siganture pass
OKAY [ 1.665s]
finished. total time: 1.666s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fa
stboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.045s]
finished. total time: 0.046s
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
error: device not found
C:\Users\Justin\Desktop\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>ad
b reboot bootloader
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?

I've just skimmed through the posts and didn't see this mentioned
If you are still able to boot into the system, download either GooManager (for TWRP) or RomManager (for CWM) and use either of those apps to install recovery. Once done, you can use the app to boot into recovery instead of the fancy ADB commands or button presses.

Jman12000 said:
So here's where I'm at
Right now I've done all the above, I've got a *** TAMPERED *** and ***UNLOCKED*** and S-ON
I've been through 4 boots, 2 of them attempts to get to recovery. Now instead of recovery rebooting into system, it just shuts off now.
Where do you think I go from here?
Click to expand...
Click to collapse
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process

tash2013 said:
This topic seems like your problem :
http://forum.xda-developers.com/showthread.php?t=2328983&page=3
The man resolved this by flashing the same recovery many many times.
And more.. Please print here your recovery flashing process
Click to expand...
Click to collapse
So both that method through ADB shell and GooManager require root. Every rooting method requires recovery, so I don't have perm root yet.

You quoted me, but answered not to me.
Read a post #26 from my link above

Possible Solution
Hello I have the same problem and the solution was:
1. Settings - Energy- Fastboot uncheked
2. Flash Recovery usin one all-in-one-kit
3. Erase Cache 3 times
4. Unplug to PC, and load into system normal
5. Turn off phone - via stock menu NOT FORCE TO OFF pressing the off button
6. Wait 2 minutes, and boot into HBOOT - Power + Volume(-) pressing
7. Choose recovery
Ready.. May these work for you! Let me know

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

HELP - Think ive bricked my Nexus 6

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

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.

Oem bootloader locked with no os installed!!! How can i flash phone to stock?!

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.