Develop Bugs

[RECOVERY] CWM 6.0.1.9 + [TOOL] Recovery Builder

Developer Koush has a tool to build from the latest sources for ClockworkMod Recovery. It gives you the most recent changes in code so you don't need to wait for an official build.
DISCLAIMER:
Neither myself nor Koush is responsible for any damages caused to your device. These are EXPERIMENTAL / BETA builds and include code that may or may not have been approved by the developer for your specific device. Proceed at your own risk.
11/28/2012
Here is the latest build that is supposed to be optimized for JB 4.2
CWM-6.0.1.9-touch-recovery.img
Just did minor testing and it works fine.
As always...use at your own risk. I am not responsible for the bad things that happen to you. That's just called karma.
Click to expand...
Click to collapse
Tool: http://builder.clockworkmod.com/
Go to the "Existing Devices" tab and select "crespo4g" and use the check-box to toggle the option for touch recovery.
Credit goes to Koush for his build tool and custom recovery.
OLD
CWM 6.0.1.3 w/ Touch for fastboot: CWM-6.0.1.3-touch-recovery.img
CWM 6.0.1.3 w/o Touch for fastboot: CWM-6.0.1.3-recovery.img
The new version includes the option to create a flashable .zip from your current ROM while preserving your privacy by leaving out the /data partition.
Click to expand...
Click to collapse

cant get this to install
andrewddickey said:
Developer Koush has a tool to build from the latest sources for ClockworkMod Recovery. It gives you the most recent changes in code so you don't need to wait for an official build.
DISCLAIMER:
Neither myself nor Koush is responsible for any damages caused to your device. These are EXPERIMENTAL / BETA builds and include code that may or may not have been approved by the developer for your specific device. Proceed at your own risk.
CWM 6.0.1.3 w/ Touch for fastboot: CWM-6.0.1.3-touch-recovery.img
CWM 6.0.1.3 w/o Touch for fastboot: CWM-6.0.1.3-recovery.img
The new version includes the option to create a flashable .zip from your current ROM while preserving your privacy by leaving out the /data partition.
Tool: http://builder.clockworkmod.com/
Go to the "Existing Devices" tab and select "crespo4g" and use the check-box to toggle the option for touch recovery.
Credit goes to Koush for his build tool and custom recovery.
Click to expand...
Click to collapse
This will not install for me for some reason. I keep trying with fastboot and it keeps failing some failed: write error or something likes that. i even put the img in a zip and it still wont flash it. I dont know what i am doing wrong

nwo122383 said:
This will not install for me for some reason. I keep trying with fastboot and it keeps failing some failed: write error or something likes that. i even put the img in a zip and it still wont flash it. I dont know what i am doing wrong
Click to expand...
Click to collapse
Which one? Touch or regular? I used the touch .img and flashed on my phone just fine.
Put it in the same folder as fastboot and rename it to "recovery.img"
Use the command:
fastboot flash recovery recovery. img

Both give me the same problem I can flash other recoveries this just will not work I'll try again tomorrow
Sent from my Nexus S 4G using Tapatalk 2

Hypothetically speaking, would this tool work on any recovery....for example, twrp....or a ps freedom port so I could use my ns4g as a ps3 factory service mode dongle?

Both give me the same problem I can flash other recoveries this just will not work I'll try again tomorrow<br />
<br />
<br />
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
I'll check when I get to the office in the morning. Might be an issue with the upload. Might have to re-up again.

hp420 said:
Hypothetically speaking, would this tool work on any recovery....for example, twrp....or a ps freedom port so I could use my ns4g as a ps3 factory service mode dongle?
Click to expand...
Click to collapse
To the best of my knowledge...no.
Only for CWM since it syncs with Koush's code.

nwo122383 said:
This will not install for me for some reason. I keep trying with fastboot and it keeps failing some failed: write error or something likes that. i even put the img in a zip and it still wont flash it. I dont know what i am doing wrong
Click to expand...
Click to collapse
My stupid fat fingers hit thanks on the wrong post
I had no issues flashing this recovery thru flash image gui...
Sent from my Nexus S 4G using Tapatalk 2

Just a little side note. When flashing a recovery or boot image via fastboot, and you have problems, try the erase command first:
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Just a good safety measure.
Later,
~WickiD~
-----
Sent from my phone
using my finger...
-----

wickid_d said:
Just a little side note. When flashing a recovery or boot image via fastboot, and you have problems, try the erase command first:
fastboot erase recovery
Then
fastboot flash recovery recovery.img
Just a good safety measure.
Later,
~WickiD~
-----
Sent from my phone
using my finger...
-----
Click to expand...
Click to collapse
I just tried this and still same error
FAILED (remote: Write Fail)
i just cant seem to get this recovery to load. i can flash any other recovery via fastboot except this one. i flashed earlier cwm and twrp. i also tried putting this in a flashable zip that didnt work and then i tried using flash image gui to get this to work and that did not work. i dont know what i am doing wrong.
i am going to try to redownlad the files and try to flash again maybe i got 2 bad downloads.
update: even after redownloading still getting that same error. but i can flash other recoveries this is perturbing me.

nwo122383 said:
i just cant seem to get this recovery to load. i can flash any other recovery via fastboot except this one.
Click to expand...
Click to collapse
Ditto. No info to provide as to why I am having trouble. No worries

This recovery Success damaged my d720 after format sdcard system and data.. cwm cant mount it after reboot... even twrp can help or stock recovery will not recognized.. but folder is there if check via adb command.
Sent from my Galaxy Nexus using xda premium

6.0.1.9
Here is the latest build that is supposed to be optimized for JB 4.2
CWM-6.0.1.9-touch-recovery.img
Just did minor testing and it works fine.
As always...use at your own risk. I am not responsible for the bad things that happen to you. That's just called karma.

andrewddickey said:
Here is the latest build that is supposed to be optimized for JB 4.2
CWM-6.0.1.9-touch-recovery.img
Just did minor testing and it works fine.
As always...use at your own risk. I am not responsible for the bad things that happen to you. That's just called karma.
Click to expand...
Click to collapse
Hmm..I found that USB mount doesn't work in 6.0.1.9 (crespo)
So I guess there'll be same issue can be occured in crespo4g.
Sent from my Nexus S using Tapatalk 2

andrewddickey said:
Here is the latest build that is supposed to be optimized for JB 4.2
CWM-6.0.1.9-touch-recovery.img
Just did minor testing and it works fine.
As always...use at your own risk. I am not responsible for the bad things that happen to you. That's just called karma.
Click to expand...
Click to collapse
Karma would be the things that happen to you when ya have it coming...not things that happen due to glitched software and such. Have you tested the primary uses for the update you posted? Any negative results found? Just a matter of curiosity...
Sent from my Nexus S 4G using XDA Premium HD app
---------- Post added at 10:57 PM ---------- Previous post was at 10:55 PM ----------
Just asking as I would hate to have to send the whole night troubleshooting my device to sort out the bad karma lol
Sent from my Nexus S 4G using XDA Premium HD app

Thanks for clearing that up for me.
Working:
Flash
Backup
Restore
Wipes
Fix Permissions
Not Working:
Mount USB
Odd:
When you select "Reboot System", it asks if you want to disable ROMs from flashing a recovery. Just hit "Back" to reboot.
That's the extent of my testing. Will do more tomorrow.
He did remove all the extra "No"s when confirming selection. That's nice.

Is there a way to flash this from my phone?
Sent from my Nexus S 4G using Tapatalk 2
---------- Post added at 03:38 AM ---------- Previous post was at 03:18 AM ----------
Nm
Sent from my Nexus S 4G using Tapatalk 2

no matter how many recoveries i try to flash through fastboot, nothing stays, it always sends me to stock recovery. any tips?

lemonoid said:
no matter how many recoveries i try to flash through fastboot, nothing stays, it always sends me to stock recovery. any tips?
Click to expand...
Click to collapse
I think you have to change a file name to install.recovery.sh.old or something like that

where is the guide or tutorial?
where is the guide or tutorial?

[Q] [VK810] Stuck in Fastboot. Need Boot Image

Hi.
As the title says, I have bricked my GPad and am stuck in Fastboot mode. I am able to pull up a command line on my computer and reboot the device from there, but that's about all I've tried. I have read online that there are commands for flashing a boot.img file, but I can't find one and I don't know how to do it. Do I wipe the device from my computer first, or just flash the .img file? Any help would be greatly appreciated.
God Bless, Mark

dadof10 said:
Hi.
As the title says, I have bricked my GPad and am stuck in Fastboot mode. I am able to pull up a command line on my computer and reboot the device from there, but that's about all I've tried. I have read online that there are commands for flashing a boot.img file, but I can't find one and I don't know how to do it. Do I wipe the device from my computer first, or just flash the .img file? Any help would be greatly appreciated.
God Bless, Mark
Click to expand...
Click to collapse
Don't wipe the device! At least I wouldn't. Might not be able to get back in!
Flash recovery and then a ROM.

sleekmason said:
Don't wipe the device! At least I wouldn't. Might not be able to get back in!
Flash recovery and then a ROM.
Click to expand...
Click to collapse
Thanks for the help, Sleek. Which recovery image should I flash and where can I get it?
Sent from my SM-G900V using XDA Free mobile app

dadof10 said:
Thanks for the help, Sleek. Which recovery image should I flash and where can I get it?
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
double check and make sure it is for your device. Link to Recovery
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
sleekmason said:
double check and make sure it is for your device. Link to Recovery
Click to expand...
Click to collapse
looks like you need loki also. There may be others that would be better suited to answer this question, as I have the Google Play edition. but at least this will point you in the right direction!

sleekmason said:
double check and make sure it is for your device. Link to Recovery
---------- Post added at 02:09 PM ---------- Previous post was at 02:08 PM ----------
looks like you need loki also. There may be others that would be better suited to answer this question, as I have the Google Play edition. but at least this will point you in the right direction!
Click to expand...
Click to collapse
Ok. Thanks, I really appreciate it, take care.
Sent from my SM-G900V using XDA Free mobile app

dadof10 said:
Ok. Thanks, I really appreciate it, take care.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
I love it when I see new members breaking theyre devices....lol....because I've been there....lol.....and xda is your friend, we are here to help....anyway....I agree with the previous advice, dont wipe device, how did you get in the situation your in?....flash recovery, and try and find a rom, make sure its for the VK810, other roms (v500 or V510) will only make things worse.... last I checked there are not many VK810 roms out there, let me know how you make out....

mcerk02 said:
I love it when I see new members breaking theyre devices....lol....because I've been there....lol.....and xda is your friend, we are here to help....anyway....I agree with the previous advice, dont wipe device, how did you get in the situation your in?....flash recovery, and try and find a rom, make sure its for the VK810, other roms (v500 or V510) will only make things worse.... last I checked there are not many VK810 roms out there, let me know how you make out....
Click to expand...
Click to collapse
I was rooted, running 4.4.2. I tried to flash 4.2.2 aboot.img with Flashfy, so I could flash TWRP recovery. Didn't work out.
Flashing a recovery is what I don't know how to do in fastboot mode. Can you walk me through it? Also, I don't know which recovery to flash.
Sent from my SM-G900V using XDA Free mobile app

dadof10 said:
I was rooted, running 4.4.2. I tried to flash 4.2.2 aboot.img with Flashfy, so I could flash TWRP recovery. Didn't work out.
Flashing a recovery is what I don't know how to do in fastboot mode. Can you walk me through it? Also, I don't know which recovery to flash.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
The directions for installing are in the link I gave you, showing to push (put) the files in the proper places for your device.
You must have ADB installed on your home computer. There is a guide on how to do this in the general section ( second sticky post), or, if using Linux, the first post.
After ADB is installed, both the Loki patch and the recovery.IMG will need to be in the platform_tools folder in the ADB folder. In Linux this would be /opt/adb/platform_tools.
In either case, to install, you must open a terminal (prompt) in the path of the install, meaning you must open the terminal in platform_tools.
Then follow the commands in the recovery post to install both Loki, and the recovery.img

sleekmason said:
The directions for installing are in the link I gave you, showing to push (put) the files in the proper places for your device.
You must have ADB installed on your home computer. There is a guide on how to do this in the general section ( second sticky post), or, if using Linux, the first post.
After ADB is installed, both the Loki patch and the recovery.IMG will need to be in the platform_tools folder in the ADB folder. In Linux this would be /opt/adb/platform_tools.
In either case, to install, you must open a terminal (prompt) in the path of the install, meaning you must open the terminal in platform_tools.
Then follow the commands in the recovery post to install both Loki, and the recovery.img
Click to expand...
Click to collapse
Ok, I got it. Duhhh...I re-read it and it makes sense now. Somehow I had it in my mind that I had to open terminal emulator on my GPad, which I can't do. I'll try it tonight when I get home from work and let you know how it goes. Thanks again.
Sent from my SM-G900V using XDA Free mobile app

sleekmason said:
The directions for installing are in the link I gave you, showing to push (put) the files in the proper places for your device.
You must have ADB installed on your home computer. There is a guide on how to do this in the general section ( second sticky post), or, if using Linux, the first post.
After ADB is installed, both the Loki patch and the recovery.IMG will need to be in the platform_tools folder in the ADB folder. In Linux this would be /opt/adb/platform_tools.
In either case, to install, you must open a terminal (prompt) in the path of the install, meaning you must open the terminal in platform_tools.
Then follow the commands in the recovery post to install both Loki, and the recovery.img
Click to expand...
Click to collapse
OK, Sleekmason, I put everything where it should be, but when I use the "adb" commands (adb push loki_flash...) I get "device not found" in terminal. As I said, I can reboot the GPad using "fastboot reboot" command, so it sees it in fastboot mode, but not in adb mode. I loaded the drivers during the adb install, so I'm pretty sure all of them are there. Is there something I'm missing? Is there a way to push the files to the GPad with fastboot?

dadof10 said:
OK, Sleekmason, I put everything where it should be, but when I use the "adb" commands (adb push loki_flash...) I get "device not found" in terminal. As I said, I can reboot the GPad using "fastboot reboot" command, so it sees it in fastboot mode, but not in adb mode. I loaded the drivers during the adb install, so I'm pretty sure all of them are there. Is there something I'm missing? Is there a way to push the files to the GPad with fastboot?
Click to expand...
Click to collapse
There is an lg recovery tool that is talked about here... But we are now out of my territory lol. maybe somebody else can chime in?

sleekmason said:
There is an lg recovery tool that is talked about here... But we are now out of my territory lol. maybe somebody else can chime in?
Click to expand...
Click to collapse
That's the first thing I tried and it wouldn't recognize the GPad either. I loaded all the drivers, but no luck. Thanks for trying, dude.

dadof10 said:
That's the first thing I tried and it wouldn't recognize the GPad either. I loaded all the drivers, but no luck. Thanks for trying, dude.
Click to expand...
Click to collapse
not saying you should, but you could always try to flash the recovery just to see if it would work.

same problem, but how I fixed it
How I got bootloop'd - I was on a trip and tried to root/flash twrp from a chromebook and as you can tell the process did not work. I ended up trying to flashfly a 4.2.2 boot.img over a 4.4.2 setup. Not the best idea. Once I returned to my windows machine, I was able to flash via adb/fastboot tools. So I found this thread and wanted to help anyone else if they arrived here and read thru the posts.
I was stuck at the fastboot text base screen on my Gpad (VK810). I dl'd the LG tools, the LG driver & tried a KDZ recover, but I was unsuccessful. Fastboot would control my device, reboots worked, but when I run fastboot devices, I only saw a single ? where the device serial number is. After a few attempts at various methods, I ended up guessing which file I had to flash.
After dl'ding a few roms from here and extracting them, it took the boot.emmc.win and flash my boot.img with that. worked with the following code and now I'm up and running.
Code:
fastboot flash boot boot.emmc.win
followed by
Code:
fastboot reboot
this worked for me and could work for you, but I can only say that it worked when I was able to access my tablet via fastboot commands.

Downgrade aboot
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
exit
exit[/HTML]
I am not able to do the above after installing Lollipop because can't get root, specifically can't update binaries in supersu and no su. Also Adbd Insecure not working. Now I am able to get into fastboot, strangely thru factory reset. Can I use 'fastboot flash aboot aboot.img' instead. Many thanks.

pakron said:
dd if=/sdcard/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
exit
exit[/HTML]
I am not able to do the above after installing Lollipop because can't get root, specifically can't update binaries in supersu and no su. Also Adbd Insecure not working. Now I am able to get into fastboot, strangely thru factory reset. Can I use 'fastboot flash aboot aboot.img' instead. Many thanks.
Click to expand...
Click to collapse
Sir or m'am, in the future, you shouldn't post the same thing in two different threads.

FynxSyndct said:
How I got bootloop'd - I was on a trip and tried to root/flash twrp from a chromebook and as you can tell the process did not work. I ended up trying to flashfly a 4.2.2 boot.img over a 4.4.2 setup. Not the best idea. Once I returned to my windows machine, I was able to flash via adb/fastboot tools. So I found this thread and wanted to help anyone else if they arrived here and read thru the posts.
I was stuck at the fastboot text base screen on my Gpad (VK810). I dl'd the LG tools, the LG driver & tried a KDZ recover, but I was unsuccessful. Fastboot would control my device, reboots worked, but when I run fastboot devices, I only saw a single ? where the device serial number is. After a few attempts at various methods, I ended up guessing which file I had to flash.
After dl'ding a few roms from here and extracting them, it took the boot.emmc.win and flash my boot.img with that. worked with the following code and now I'm up and running.
Code:
fastboot flash boot boot.emmc.win
followed by
Code:
fastboot reboot
this worked for me and could work for you, but I can only say that it worked when I was able to access my tablet via fastboot commands.
Click to expand...
Click to collapse
i was having the same issue, get the boot.img file and typed "fastboot flash boot boot.img" after moving the boot.img file into the same folder as adb/fastboot and it worked, thanks bro!

phone stuck on HTC boot screen and other stuff

I recently got a htc one m8 that is stuck on the boot screen.
i can get into the bootloader and fastboot seems to work.
I seem to be able to flash twrp but when i reboot into recovery it goes right back to the bootloader
if i reboot normally it goes back to the bootscreen with the green htc logo.
if i try to go to hboot adb doesn't recognize the device.
so i'm stuck now. i've read several tutorials and tried various things but have no idea where to go from here.
i can tell you that the bootloader says its unlocked and that its set to s-on and there is no os installed.
help

jodahall said:
I seem to be able to flash twrp but when i reboot into recovery it goes right back to the bootloader
Click to expand...
Click to collapse
Try fastboot erase cache, and flash TWRP again with fastboot.
What is your hboot number, and what TWRP version are you trying?
Also, was your phone recently updated OTA for the Stagefright patch? If so, its a known issue that this recent update does not work with TWRP for some folks.
jodahall said:
if i try to go to hboot adb doesn't recognize the device.
Click to expand...
Click to collapse
This is as it should be. adb doesn't work in hboot. You need to be booted into OS to use adb, possibly will work in recovery (but you can't boot into recovery, so that doesn't really matter).

my hboot version is 3.19.0.0000
i am trying to flash the latest twrp
I have not gotten the ota, this phone has been sitting in a drawer for about 6 months so nothing new has been applied.
I will try erase the cache and reflash the twrp

jodahall said:
i am trying to flash the latest twrp
Click to expand...
Click to collapse
What number TWRP exactly? And you're sure its the TWRP file for the M8, right?
I ask for the number, since I've seen at least a couple times where the person claims they are trying to use the "latest" or "current" TWRP. But when I ask for more info, it turns out the version is not even close to current.
Best to be specific when talking about version numbers.

Sorry the version I'm trying to install is 2.8.7.0...
The actual filename is twrp-2.8.7.0-m8.IMG
I also tried your advice and from a command window erased the cache and then reflashed. It didn't work this time so I'm downloading some older versions of twrp and will try flashing them.
One question. Does it hurt anything to erase multiple times or for that matter flash a recovery image multiple times. With my old Motorola it was recommended to flash multiple times.
Sent from my A0001 using XDA Free mobile app

oh, it worked. I am one step closer as it booted into the custom recovery.....whoohooo
I ran the command "fastboot format cache" from a dos prompt a couple of times, there were errors the first two times, then the 3rd time it created it without error.
ok onto the next steps that are in Vomers guides....
thanks for all your help

jodahall said:
Sorry the version I'm trying to install is 2.8.7.0...
The actual filename is twrp-2.8.7.0-m8.IMG
Click to expand...
Click to collapse
You are correct, that is latest version (and correct one for the M8). You might re-download just to eliminate the possibility the file wasn't corrupted.
jodahall said:
It didn't work this time so I'm downloading some older versions of twrp and will try flashing them.
Click to expand...
Click to collapse
If you are still intending on doing this, don't try any version older than 2.8.4.0 or so. TWRP versions much older than that, won't work on hboot 3.19. TWRP will install and seem to work fine, but after you flash the ROM, the ROM won't boot.
jodahall said:
One question. Does it hurt anything to erase multiple times or for that matter flash a recovery image multiple times. With my old Motorola it was recommended to flash multiple times.
Click to expand...
Click to collapse
In the technical sense, the emmc chip does have a finite number of times it can be flashed.
But in reality, I think the number of times the emmc can be flashed before failing is (supposedly) something in the thousands.
Of course, things sometimes fail before they are supposed to, and every extra flash may put you closer to that point (in theory). But I don't let that stop me from flashing what I want, whenever I want to. And flashing recovery a few extra times is not going to hurt anything much IMO.
---------- Post added at 03:31 PM ---------- Previous post was at 03:30 PM ----------
jodahall said:
thanks for all your help
Click to expand...
Click to collapse
There's a button for that!

Bootloop after OTA update

Hi everyone.
After installing an OTA update my Nexus 5X entered in logo bootloop. The USB debugging is off and now I cant boot the phone to enable it.
He is still with OEM LOCK. I've tried the following steps:
- fastboot oem unlock -> says the oem unlock is not allowed
- fastboot flash ... -> device is locked cannot flash images
- OTA rescue https://drive.google.com/file/d/0Bz6x7k-VkpUJam5Mc1hKa09PVGc/view -> success install, still bootloop
I can enter in bootloader normally, but any fastboot modify operation (format, flash, erase) i got that fkin message "device is locked"
Any idea how can i solve it? It may just be enabling USB debugging without boot up the phone or recovery to factory image. I have no data on it, I can delete/wipe anything.
FASTBOOT MODE
PRODUCT_NAME - bullhead
VARIANT - bullhead LGH790 16GB
HW VERSION - rev_1.0
BOOTLOADER VERSION - BHZ11b
BASEBAND VERSION - M8994F-2.6.33.2.06
CARRIER INFO - N/A
SERIAL NUMBER - xxxxxxxxxxxxxxxxxxxxxxx
SIGNING - production
SECURE BOOT - enabled
DEVICE STATE - locked
RECOVERY MODE
google/bullhead/bullhead
6.0/MDA89E/2296692
user/release-keys
Thanks a lot, sorry poor english, I´m brazilian.

try this to unlock
fastboot flashing unlock
to lock
fastboot flashing lock

@ricardolipka maybe try this:
http://forum.xda-developers.com/showthread.php?t=3251740
Sent from my SM-G930V using Tapatalk

Access recovery. Use ADB push command to push ota or custom ROM. Be careful to push bullhead ROM.

@jamelnassar "fastboot flashing unlock"
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.006s
@PiousInquisitor
My windows 10 not recognize my device in COM/USB ports as the photo. The N5X boot in download mode but is not recognized by windows. I tried on two different computers, multiple versions of LG driver.
@freq_ency
I cant use adb for push, just work when I select "Apply update by ADB". At this when I check "ABD devices" got this
List of devices attached
01a13ee8d892bf8c sideload
Any other tips?
This is giving me a big headache, spend hours trying to find a way to recover it.
How a simple OTA update can do this ****?

ricardolipka said:
@jamelnassar "fastboot flashing unlock"
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.006s
@PiousInquisitor
My windows 10 not recognize my device in COM/USB ports as the photo. The N5X boot in download mode but is not recognized by windows. I tried on two different computers, multiple versions of LG driver.
@freq_ency
I cant use adb for push, just work when I select "Apply update by ADB". At this when I check "ABD devices" got this
List of devices attached
01a13ee8d892bf8c sideload
Any other tips?
This is giving me a big headache, spend hours trying to find a way to recover it.
How a simple OTA update can do this ****?
Click to expand...
Click to collapse
Yeah fine! Your device is shown in PC monitor nah. Just sideload the update. If it says denied, just try using adb push. If didn't work you have go by tot file.

freq_ency said:
Yeah fine! You devices are shown in PC monitor nah. Just sideload the update. If it says denied, just try using adb push. If didn't work you have go by tot file.
Click to expand...
Click to collapse
I've tried all OTA update via sideload, still bootloop.
https://developers.google.com/android/nexus/ota#ryu here I got the updates, also tried the android N update, not good too.

Have you tried to wipe cache in recovery? If that doesn't work try a factory reset in recovery, but that will wipe your device so be forewarned.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
Have you tried to wipe cache in recovery? If that doesn't work try a factory reset in recovery, but that will wipe your device so be forewarned.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for answer, yes both didnt work too. Several times tried...

ricardolipka said:
Thanks for answer, yes both didnt work too. Several times tried...
Click to expand...
Click to collapse
I hate to say this but I think your only option is to warrantee the device. I see you're from Brazil so that might be a problem.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
I hate to say this but I think your only option is to warrantee the device. I see you're from Brazil so that might be a problem.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
It's a big problem to me. But I'll keep trying kkkk
Thanks =D

ricardolipka said:
It's a big problem to me. But I'll keep trying kkkk
Thanks =D
Click to expand...
Click to collapse
I thought it might be a problem. With a locked bootloader you're limited to using the stock recovery to sideload the ota or a factory reset. There really aren't any other options.
Sent from my Nexus 9 using XDA Free mobile app
---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------
I did see one user say he sideloaded a custom Rom in the stock recovery. I ready don't believe him but it's worth a try.
Sent from my Nexus 9 using XDA Free mobile app

Does the "fastboot boot" command work for anyone here?

I'm using the fastboot binary from HTC's website. I tried to use it to boot TWRP without flashing it, but in download mode, it just hangs forever after saying "Flash images success (1/1)" and "Start downloading", with the cursor stuck on the second of those. The fastboot command is also hung, after printing "booting..." I eventually have to force reset the phone using all 3 buttons.
I also tried it from the bootloader screen and that just fails immediately, saying "booting... FAILED (remote: unlock device to use this command)" even though I'm unlocked (and S-OFF).
The reason I'm doing this btw is so I can try to back up the stock recovery before overwriting it with TWRP, but I don't know how to do that without root, for which I need TWRP... so if anyone knows another way, that'd be great too!

supeRUUser said:
I'm using the fastboot binary from HTC's website. I tried to use it to boot TWRP without flashing it, but in download mode, it just hangs forever after saying "Flash images success (1/1)" and "Start downloading", with the cursor stuck on the second of those. The fastboot command is also hung, after printing "booting..." I eventually have to force reset the phone using all 3 buttons.
I also tried it from the bootloader screen and that just fails immediately, saying "booting... FAILED (remote: unlock device to use this command)" even though I'm unlocked (and S-OFF).
The reason I'm doing this btw is so I can try to back up the stock recovery before overwriting it with TWRP, but I don't know how to do that without root, for which I need TWRP... so if anyone knows another way, that'd be great too!
Click to expand...
Click to collapse
You can't. Read twrp FAQ.

yldlj said:
You can't. Read twrp FAQ.
Click to expand...
Click to collapse
I don't see anything at twrp.me/FAQ about this...
Are you saying there is no way to make a backup of the stock recovery, at all? How do the ones posted here get made?

supeRUUser said:
I don't see anything at twrp.me/FAQ about this...
Are you saying there is no way to make a backup of the stock recovery, at all? How do the ones posted here get made?
Click to expand...
Click to collapse
You need 2 phones.
Taken from twrp faq
6. How do I backup stock recovery prior to flashing TWRP? You can't. The "fastboot boot" command appears to be disabled on the 10's ABOOT, so TWRP must be fastboot flashed over stock recovery. You can however, extract the stock recovery.img from the OTA firmware.zip when it's received and use that to install the OTA.
[*]An alternate method to obtain a stock recovery is listed below, but it requires 2 devices (either owned by you, or help from someone else in the forum):
Someone fastboot flash twrp and immediately make a backup of boot and upload it to XDA.
Once the above is available, someone else download that boot.img to their device, and fastboot flash twrp to the BOOT partition of their device.
Once the above is done, reboot the device, which will bring up TWRP, and then backup stock RECOVERY in TWRP, and upload to XDA.
Then, from within TWRP, use the Image install feature in TWRP to flash the stock boot.img

They're probably pulled from the RUUs.

Barracuz said:
They're probably pulled from the RUUs.
Click to expand...
Click to collapse
Yep. That's how I get stock recoveries for people who need them.
---------- Post added at 08:24 AM ---------- Previous post was at 08:20 AM ----------
supeRUUser said:
I don't see anything at twrp.me/FAQ about this...
Are you saying there is no way to make a backup of the stock recovery, at all? How do the ones posted here get made?
Click to expand...
Click to collapse
Download the latest RUU for your model, and use nkk71's RUU decrypt tool to extract the firmware (with the -f flag). The stock recovery will be in there.

Duh, OK, that should have been obvious. Thanks.

supeRUUser said:
Duh, OK, that should have been obvious. Thanks.
Click to expand...
Click to collapse
It's not obvious if you don't know about the decrypt tool, and a lot of people don't. You're welcome