Database Develop

Doesn't go into recovery

I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?

It is most likely you did something wrong when you flashed the recovery img, just follow the tuto again and make sure to follow each step.
Here is a guide made by mike: http://forum.xda-developers.com/showthread.php?t=2265618

I have done that. Tried a few times. I am fairly "in the know" with rooting ect, but I just can't figure this out.

Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta

Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.

samflorin said:
Disable fast boot
Sent from my PadFone 2 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Tried that.
TarekElsakka said:
Did you reboot after flashing the recovery or did you just go straight into it? I had the same problem and what fixed it is rebooting after flashing the recovery 'fastboot flash recovery recovery.img'.
Click to expand...
Click to collapse
Tried that to.
When I press perm root, it just reboots normal like recovery doesn't even exist.

Have you tried flashing stock recovery and trying to boot in it? I know that doesn't fix anything, I am just curious if your device will actually boot into any recovery state at all. I have read on XDA about some devices not being able to boot into recovery for some reason.
Here's the stock recovery, just in case: http://forum.xda-developers.com/showthread.php?p=38504123

Okay give me a shot at that.
I noticed after flashing recovery, mine doesn't tampered like it should?

The stock recovery says it's not available anymore.

If it doesn't say TAMPERED then the recovery must have not been flashed to begin with and that is why it's not booting into it. Which recovery are you trying to install? I use TWRP 2.5.0 and I flashed it with fastboot then restarted and it booted fine. My device is S-ON, by the way, and running Trickdroid 7.5.
US Developer Edition Recovery: http://d-h.st/b5g
T-Mobile Recovery: https://www.dropbox.com/s/hvs38223dfrzsny/recovery_tmobile.img
I am not sure if either one will work with your device since I am guessing it's international? But they might be worth a shot.
Never mind, I found the stock international recovery for you: https://dl.dropboxusercontent.com/u/22045273/htc1-stock-recovery.img it was on page 4 of the thread. Give it a go.

I flashed the stock recovery and it still boots like there is no recovery there. and it doesn't say "tampered"
This is crap
EDIT: Yeah I figured it's not being flashed since it's not tampered, but no matter what I try it won't flash.
I'm navigating to the folder: CD C:\One_All-In-One_Kit_v\Data\Recoveries then typing fastboot flash recovery recovery.img and it doesn't work.
It says it's flashed ect, but doesn't boot into it, nore show tampered.

This is very weird and unfortunately I do not know the solution to that. I do not use the All-In-One-Kit, actually, but just a mini-SDK with fastboot files inside. I use shift + right click and "open command prompt window here" rather than navigate to the location, it's just much easier that way. Can you try flashing the latest TWRP recovery?

aussiesausage said:
I followed the video tutorial and when I flash recovery, then proceed to boot into recovery it fails to boot into recovery, it just flashes then boots like normal when I perm root. I don't know what's going on. I tried the clear cache command with no response.
I have searched and didn't find anything.
Anyone able to help please?
Click to expand...
Click to collapse
Are you under s-off ?

tash2013 said:
Are you under s-off ?
Click to expand...
Click to collapse
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.

Would ADB be any better?

Ugh man that's horrible. I honestly do feel your frustration because I have faced similar situations with my HTC devices (One X and One) countless times, and it sucks because you know the correct steps yet it's not working. I sure hope someone knowledgeable about this can come in and help you. Best of luck.
EDIT: I have only used ADB to sideload a ROM but I don't know about flashing recoveries. If you know how to do it, then why not? It's worth a shot for sure.
EDIT #2: And if you're not familiar with ADB, this article should get you started: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Make sure you follow all the steps to the word and also install HTC Sync Manager for the proper drivers to be loaded.

I know right, driving me nuts.
I've never done adb to flash a recovery before but don't know if I would want to be the pidgeon to try lol

aussiesausage said:
Nope S-ON
I just downloaded TWRP and flashed it ( fastboot flash recovery recovery.img ) it said all the jabber, like it worked, rebooted and still no "tampered" just reboots like nothing ever happen.
I give up.
Click to expand...
Click to collapse
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again

tash2013 said:
Try reboot to system (OS), then power off , then go to bootloader -> try enter to recovery again
Click to expand...
Click to collapse
Tried that, no go.
Also checked the drivers, re-installed no go.
I am quite up there with adb, but not with flashing recovery with a HTC device lol.

There seems to be another method for flashing recoveries besides fastboot.
http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
This is an HTC Evo section but it could work for the One as well, although I am not sure of it. I have done some Googling and I did not come across any articles/threads saying that it is possible to flash a recovery using ADB, so that might not be possible.

[Q] Bootloop, can't push recovery etc

Hey everyone,
so I have an issue, I hate taking care of other peoples devices, but my dad asked me to root his Optimus 4x for him, so I did.. or at least I gave it a try.
I unlocked the bootloader, rooted it and tried to instal a custom recovery, with no success.
the OS the device had is 4.1.2 JB, and I tried to flash the ICS recovery, which caused a permanent bootloop.
luckily (I guess?) I can access the recovery (which is STOCK for some odd reason) but the device never boots back up when I restart it. I tried to wipe everything that the stock recovery allows me to, no success either. I tried to use the LG tool, I put the IMEI and hoped for the best - nope, it didnt help either. it kept on saying the device has disconnected.
SO I figured the way to go would be an adb flash of the right recovery and then flashing a custom ROM, but I cant push the recovery image to the sdcard, it says there's no such directory. this is the command I used:
adb push recovery.img /sdcard/recovery.img
I tried various combinations and at this point I'm kinda lost and confused. Perhaps some more-experienced people could give me a hand? I've spent 6 hours figuring this out
EDIT:
the only way of turning the device off is pulling the battery, I can use adb, and I tried to flash the wrong recovery accidently.
thanks

Pawelss said:
Hey everyone,
so I have an issue, I hate taking care of other peoples devices, but my dad asked me to root his Optimus 4x for him, so I did.. or at least I gave it a try.
I unlocked the bootloader, rooted it and tried to instal a custom recovery, with no success.
the OS the device had is 4.1.2 JB, and I tried to flash the ICS recovery, which caused a permanent bootloop.
luckily (I guess?) I can access the recovery (which is STOCK for some odd reason) but the device never boots back up when I restart it. I tried to wipe everything that the stock recovery allows me to, no success either. I tried to use the LG tool, I put the IMEI and hoped for the best - nope, it didnt help either. it kept on saying the device has disconnected.
SO I figured the way to go would be an adb flash of the right recovery and then flashing a custom ROM, but I cant push the recovery image to the sdcard, it says there's no such directory. this is the command I used:
adb push recovery.img /sdcard/recovery.img
I tried various combinations and at this point I'm kinda lost and confused. Perhaps some more-experienced people could give me a hand? I've spent 6 hours figuring this out
EDIT:
the only way of turning the device off is pulling the battery, I can use adb, and I tried to flash the wrong recovery accidently.
thanks
Click to expand...
Click to collapse
try to flash stock rom using KDZ method (http://forum.xda-developers.com/showthread.php?t=2069723), that lets your device like new, and then try to start again, I recommend you to use lg p880 toolkit look into download section (http://forum.xda-developers.com/showthread.php?t=2230934), and you can download CWM 6.0.4.5 and replace the recovery in files folder of p880 toolkit and get the latest recovery that allows you to instal the most recent ROM

Le'mme guess, you didn't even think about unlocking bootloader, amaright?

Rudjgaard said:
Le'mme guess, you didn't even think about unlocking bootloader, amaright?
Click to expand...
Click to collapse
Pawelss said:
I unlocked the bootloader, rooted it and tried to instal a custom recovery, with no success.
Click to expand...
Click to collapse
I bloody hope he did or do you think he's just lying to us for the fun of it?

donkanmcklaus said:
try to flash stock rom using KDZ method (http://forum.xda-developers.com/showthread.php?t=2069723), that lets your device like new, and then try to start again, I recommend you to use lg p880 toolkit look into download section (http://forum.xda-developers.com/showthread.php?t=2230934), and you can download CWM 6.0.4.5 and replace the recovery in files folder of p880 toolkit and get the latest recovery that allows you to instal the most recent ROM
Click to expand...
Click to collapse
Thanks for your suggestion, I'll try it once I'm home.
Rudjgaard said:
Le'mme guess, you didn't even think about unlocking bootloader, amaright?
Click to expand...
Click to collapse
No. As stated in the first post, I did in fact unlock the bootloader. I also confirmed it in the secret menu and it said "Unlock" which as I presume means the bootloader is unlocked.
SimonTS said:
I bloody hope he did or do you think he's just lying to us for the fun of it?
Click to expand...
Click to collapse
No, there's no reason for me to laugh the secret menu confirmed it too.
Thanks for your replies, I hope it works

I'm sorry i missed the first line, what got me was when you said you flashed recovery but it was still the same
The adb command to flash recovery is
1) adb reboot oem-unlock
2) fastboot flash recovery /path/toyour/recovery.img (not adb because you must use fastboot when in bootloader)

Rudjgaard said:
I'm sorry i missed the first line, what got me was when you said you flashed recovery but it was still the same
The adb command to flash recovery is
1) adb reboot oem-unlock
2) fastboot flash recovery /path/toyour/recovery.img (not adb because you must use fastboot when in bootloader)
Click to expand...
Click to collapse
hey, thanks for your reply.
I assume the /path/toyour/recovery.img is a path on the phone, the thing is I cant copy it to the internal storage with adb for some odd, unknown reason (well the reason is the directory doesnt exist). I'll try to return to stock first, and I'll post the result.
thank you again
EDIT:
SOOO I managed to fix it and get it all to work the device boots up normally again thank you VERY much for all your kind help. I love you guys!!

[Q] Help: Can't get to recovery or system?!?!?

Hi, Gang... Please be patient as I'm not normally playing at this level...
I recently had a kid kill my TF700 so I bought at TF701 as a replacement. I immediately unlocked it, forgetting to take the latest Asus update OTA beforehand. Anyways, I manually downloaded v11.4..1.17 and put it on a blank microSD and stuck it into the tablet where the update was recognized as available and I set the update in motion... Something went sideways after I walked away to let the update run and now I can't get back into the system and I can't get into recovery.
I have the bootloader up (1.00e as released by 10.14.1.47) and I can communicate with the device via fastboot. Can someone help me wipe and get a recovery.img and/or a full stock image onto this thing. Right now it just keeps rebooting unless I manually force it to the bootloader.
I'm hoping someone more knowledgeable can chastise me for being a moron an point me in the right direction. Ultimately, I was tying to get to the latest ASUS ROM to the the bootloader that goes with it and then move onto a custom ROM.
Many thanx.

Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
---------- Post added at 08:27 PM ---------- Previous post was at 08:19 PM ----------
I wouldnt flash a recovery/bootloader especially the new ones til you can verify an older recovery works. Try booting this one https://www.dropbox.com/s/il2m4rtxlmzjfz9/recovery.img but dont flash til someone else takes a look at this. This is an old philz touch without touch.

Still nothing...
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse

kartman_canada said:
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
Where did you get the full firmware update you tried to flash?
I can't find a recovery that is compatible with that old bootloader, so your best bet would be to update via Asus firmware.
What happens if you choose RCK in the bootloader menu? Is the stock recovery still working?
What's your SKU?
If the manual stock update doesn't work you may have to flash the system blob in fastboot, but answer above questions first and then we'll see.
If you're getting frustrated, stop and come back to it later. Don't do anything desperate! No reason for it yet.
Click to expand...
Click to collapse

kartman_canada said:
YayYouFixedIt said:
Im no help. Dont listen to me. Try using fastboot to run a recovery. "fastboot boot recovery.img" from the bootloader. Maybe with that old bootloader you should be using an old recovery maybe.
I'm really starting to get frustrated... (understatement)
I've got a copy of the 4.4.2 OTA image (zip and recovery.img). Should I not be able to use ADB to copy the image to the device and then boot the recovery.img? I can get the tablet to respond to fastboot but I can't get it to be recognized by ADB.
I've never had issues with custom ROMs before. This time I'm wading into unfamiliar waters. I'm note even sure how the initial update failed. Is there a way for me to update the bootloader, then add a CWM recovery, then load the ROM?
Again sorry to have to ask but any help would greatly be appreciated.
Click to expand...
Click to collapse
https://www.dropbox.com/s/il2m4rtxlmzjfz9/recovery.img
download this recovery(which is an older one compatable with that bootloader and try fastboot boot recovery.img from your older bootloader.
It should work. If you can determine that it works and all your partitions are intact. The command is" fastboot flash recovery recovery.img" I would think if you can simply get this one to boot it will be ok to flash and you should be able to flash whatever you want. Namely you will want to flash the new bootloader and recovery from the flashable zip that sbdags provides from his optimized asus stock.
If you have to adb sideload a rom from within the recovery. Then download just use the cm11 rom for now because the asus stock is over a gig and and might not sideload. the asus stock sbdags provides in this forum.
Otherwise you might be able to flash things from the microsd card.
Than if you decide to go the cm11 route. just download the asus stock from this forum from inside the rom. Be careful.
Click to expand...
Click to collapse

Fixed!
YayYouFixedIt said:
kartman_canada said:
download this recovery(which is an older one compatable with that bootloader and try fastboot boot recovery.img from your older bootloader.
It should work. If you can determine that it works and all your partitions are intact. The command is" fastboot flash recovery recovery.img" I would think if you can simply get this one to boot it will be ok to flash and you should be able to flash whatever you want. Namely you will want to flash the new bootloader and recovery from the flashable zip that sbdags provides from his optimized asus stock.
If you have to adb sideload a rom from within the recovery. Then download just use the cm11 rom for now because the asus stock is over a gig and and might not sideload. the asus stock sbdags provides in this forum.
Otherwise you might be able to flash things from the microsd card.
Than if you decide to go the cm11 route. just download the asus stock from this forum from inside the rom. Be careful.
Click to expand...
Click to collapse
Managed to fastboot to the older recovery.img. As per instructions, I then flashed the latest bootloader and recovery from sbdags. I'm now good to go with whatever ROM I want. Many thanx! I'd still like to know how the upgrade to the latest Asus update screwed up. I wasn't watching it after setting the update in motion so it's a mystery. All I know is that the unit was plugged in so it wouldn't run out of juice and when I came back to check it, it wouldn't boot to Android, I couldn't get to recovery, and it would just keep rebooting in a loop.
Lucky for me it was unlocked and I had fastboot access to the (albeit out-of-date) bootloader.
All good now. Cheers.
Click to expand...
Click to collapse

kartman_canada said:
YayYouFixedIt said:
Managed to fastboot to the older recovery.img. As per instructions, I then flashed the latest bootloader and recovery from sbdags. I'm now good to go with whatever ROM I want. Many thanx! I'd still like to know how the upgrade to the latest Asus update screwed up. I wasn't watching it after setting the update in motion so it's a mystery. All I know is that the unit was plugged in so it wouldn't run out of juice and when I came back to check it, it wouldn't boot to Android, I couldn't get to recovery, and it would just keep rebooting in a loop.
Lucky for me it was unlocked and I had fastboot access to the (albeit out-of-date) bootloader.
All good now. Cheers.
Click to expand...
Click to collapse
Good to hear. For the Asus updates you just put them in /sdcard and reboot dont you? Its fairly automatic wasnt it? Then unlock after being updated? What went wrong in your case, Hard for me to say i guess because I and others unlocked at or before 4.3.
Click to expand...
Click to collapse

Need help upgrading to 5.1, Tired of flashing all the things.

My nexus 6 is unlocked and is running stock 5.0.1, rooted. . It has twrp and is decrypted.
I tried to sideload the 5.1 ota but it doesnt work.
I tried flashing the new 5.1 factory image but that doesnt work.
I'm tired of all this now, I just want my phone running stock 5.1 , locked , encrypted ,unrooted so I can just get ota next time from Google whenever they send it out.
Any guidance on what I need to do would be appreciated.

Use Wug's Nexus Root Toolkit :good:
Edit : Now I'm currently "Optimising app..." loop.

I tried using tge NRT to flash it back to stock but it didn't work.

I would first make a TWRP backup, then I would flash the boot image (decrypted if you want and make sure its the new one), system, radio and then reboot. I flashed everything fine while keeping twrp on my phone but I didn't like not having a custom ROM plus it was a little laggy so I restored a TWRP backup. My phone did bootloop for a while but eventually it booted 5.1. I would be careful since 5.1 seems to be having some issues in general.

http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
Quote:
Originally Posted by baudi11
Same thing happened to me. Here's what I did.
1. Press and hold power, volume up, and volume down. Keep holding them down until the phone boots into bootloader mode.
2. Go back to the toolkit and click the radio button labeled "Soft bricked/bootloop"
3. Click "Flash stock plus unroot"
4. Check all the boxes under "Settings", including "Post-flash factory reset" then click OK.
5. Follow the toolkit instructions from there.
This got me out of the bootloop, successfully installed 5.1, and kept all my apps and settings. Good luck.
Click to expand...
Click to collapse
It worked for me after that. Now I'm booted in 5.1

When I try to flash the factory images directly from Google I get the following errors even though the MD5 checks out.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778070480 bytes
error: update package missing system.img
Press any key to exit...

celeriL said:
http://forum.xda-developers.com/nex...gs-nexus-root-toolkit-v1-9-8-t2947452/page101
It worked for me after that. Now I'm booted in 5.1
Click to expand...
Click to collapse
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!

Giuseppe1010 said:
Thanks so much! This worked perfectly. Exactly what I needed. The past couple days have been so annoying but now it's over. Thanks again!
Click to expand...
Click to collapse
Glad to help!

You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
HaHaa. Tried and true. Always works.

prdog1 said:
HaHaa. Tried and true. Always works.
Click to expand...
Click to collapse
rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I totally agree. Have done successful manual flash when tool kits failed. Seen on Nexus 6 already.Saved my soft brick with manual flash when tool kit failed.

Pilz said:
I agree that always works without fail and is much easier than a tool kit. I don't like tool kits because people need to learn the correct way to flash things before using one because its better to understand what you are flashing should there be an error.
Click to expand...
Click to collapse
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.

rootSU said:
I don't have anything against toolkits on some devices, so long as it is not used as a shortcut to learning the basics. That said, on a nexus, I don't really see any need to be honest.
Click to expand...
Click to collapse
Thats how I feel because its so easy my wife could do it and she doesn't know anything about flashing. Toolkits are good for non Nexus devices, I just don't see a point when we need to learn things the correct way first.
I hope the bugs get sorted out so people don't hard brick their phones anyone

rootSU said:
You also could have extracted the zip and manually flashed the images ing fastboot
fastboot flash recovery recovery.img
fastboot flash system system.img
Etc
Click to expand...
Click to collapse
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again

kingofkings11 said:
Im a complete fastboot novice since this is my first nexus device (always had samsung phones up until now) and although I managed to root and unlock the boot loader I want to make sure I learn all the basics including flashing (side loading?) subsequent updates.
So Im currently rooted, unlocked bootloader on a 5.01. custom rom. How would I go about flashing the 5.1 update manually?
Im assuming that once I extract the update zip file I will find all the images that need to be flashed....what order do i do them in? How do I take into account the boot loader locking issue people have been facing that results in a bricked device?
Thanks in advance.
EDIT: I found this thread which outlines what I need to do http://forum.xda-developers.com/nexus-6/general/using-image-to-update-nexus-6-data-loss-t3053158
I only have two question now:
1. Im assuming the system image will wipe out the custom rom im on but not the data will leaving the data cause a problem? whats the command line to wipe data?
2. This doesnt address the boot loader locking issue causing a brick that people have been facing. This process involves updating the boot loader what do i have to do to make sure I dont brick my device?
Thanks again
Click to expand...
Click to collapse
You could simply not update the bootloader. Bare minimum requirements is update system and boot (kernel). if you want to learn more about fastboot, go to general > All in one guide > Question 28.
If you do not update the bootloader, you'll never get an OTA but it doesn't seem like you're wanting that anyway.
In regards to data, yes it could cause a problem if you're using a custom rom. You can use fastboot erase data command. This also wipes your /sdcard though.

Bricked Nexus 6 and cant unlock bootloader

I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?

win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
without enabling oem unlock in the developer options, nope. but you can use the stock recovery to check if a factory reset would help.

Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).

win465 said:
Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).
Click to expand...
Click to collapse
Had you unencrypted?

Yes, but i flashed backed to stock kernal.

win465 said:
Yes, but i flashed backed to stock kernal.
Click to expand...
Click to collapse
How?

Using the nexus tool kit. After that I locked the bootloader to sideload the update.

win465 said:
Using the nexus tool kit. After that I locked the bootloader to sideload the update.
Click to expand...
Click to collapse
Were you rooted before all of this too?

Nope

Evolution_Tech said:
Were you rooted before all of this too?
Click to expand...
Click to collapse
Nope

win465 said:
Nope
Click to expand...
Click to collapse
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.

Evolution_Tech said:
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.
Click to expand...
Click to collapse
Thank you for your help

Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.

RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
Click to expand...
Click to collapse
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.

Possible idea
Evolution_Tech said:
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.
Click to expand...
Click to collapse
There's some more concrete info in the first couple pages, especially regarding our N6's:
http://forum.xda-developers.com/nexus-9/help/to-toggle-allow-oem-unlock-via-fastboot-t3091119
Hope this helps.
I'll keep my eyes open for anything that seems pertinent.
Best of luck

RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.
Click to expand...
Click to collapse
I get this error message "system partition has unexpected contents" (Status 7).

win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
Can you fastboot boot twrp recovery? And if that is possible, will twrp flash zips with a locked bootloader?
Edit: I'm almost certain fastboot boot recovery won't work with a locked bootloader. I almost thought I had a good idea.

I am in the same situation. Bootloader locked and no custom recovery nor adb enabled. surprisingly enough, yesterday my phone could boot up but it's stuck now in the configuration process. I cannot access to the settings so I can check usb debugging or oem unlock. I can only access the dialer. my question is: is there anyway to do that with just a dialer code?

Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).

Didgeridoohan said:
Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).
Click to expand...
Click to collapse
Sorry for the noob question but where can I find these OTAs and how to install one of them? Does it require usb debugging to be enabled?