Develop Bugs

[Q] getting "not allowed" when trying to update TWRP

hello,
i am S-off, unlocked, hboot 1.54.0000 and currently running TWRP 2.6.3.3. I installed 2.6.3.3 on 11-4-13 however, i'm trying to update to 2.6.3.4 and in fastboot i am getting this error...
writing 'recover'... FAILED (remote: not allowed)
this is the command i'm running with the .img file in my sdk folder...
fastboot flash recover openrecovery-twrp-2.6.3.4-m7vzw.img
i have searched the web and the only issue i find with HTC phones is that you will get this error if your bootloader is locked.... however mine is unlocked (confirmed looking at my phone right now in fastboot.
does anyone have any ideas on how i could install 2.6.3.3 last month, but this month i can't install TWRP via fastboot?
should i run the rumrunner s-off tool again to see if that fixes the issue?
i have been running cyanogen 10.2 and NOS 2.0 roms. i have tried switching back and forth and installing TWRP with each of these roms loaded and still no dice.

It looks like you're missing a y in your command if that's how you actually wrote the command.
If all else fails you can download flashify from the play store and use that to update the recovery.

midnight assassin said:
It looks like you're missing a y in your command if that's how you actually wrote the command.
If all else fails you can download flashify from the play store and use that to update the recovery.
Click to expand...
Click to collapse
OMG. you are correct. i don't know how many times i've looked at that to check and even checked in TWRP recovery forum and never noticed it. Thanks for pointing out something that should have been painfully obvious!
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7vzw.img

LOL, no problem. Flashify works too if you ever need it. I like to use fastboot too though.

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!

Problems updating TWRP

I tried to update my TWRP because the touch screen in Aroma installers isnt working. The update failed and now I don't have a recovery. What should I do?

Not nearly enough detail for any of us to help.
What is your current version TWRP?
What TWRP version did you try to update to?
How did you try to update it (fastboot, app, etc)?
Any specific error messages on failure?
Current software and firmware versions?
Hboot number?
Do a fastboot getvar all, and post the output being sure to delete IMEI and serial number)
Bootloader unlocked?

If You have root, try https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager

I have a sprint htc one m8 rooted, running Marshmallow Google play edition. I tried to flash the 3 most recent updates and it gave me an error saying I might already have it installed or something went wrong. At the moment I don't have a recovery because the app deleted it. So when I try to go into recovery it never starts and I have to restart the phone. I tried flashing them via fastboot and it says it was successful but it didn't actually work.

You try to install recovery by fastboot?

Yea it was successful but when I try to reboot into recovery in never does.

spencer311 said:
I At the moment I don't have a recovery because the app deleted it.
Click to expand...
Click to collapse
What app?
spencer311 said:
when I try to go into recovery it never starts and I have to restart the phone. I tried flashing them via fastboot and it says it was successful but it didn't actually work.
Click to expand...
Click to collapse
Try fastboot erase cache, and fastboot flash TWRP again. This alone clears up a lot of issues with TWRP not flashing properly.
What version TWRP did you try?
Difficult to help, since you failed to provide hardly any of the info I requested.

spencer311 said:
Yea it was successful but when I try to reboot into recovery in never does.
Click to expand...
Click to collapse
Or use RUU, and try again.

recovery issues

I have a Verizon xl unlocked, rooted, elemental kernel, running X firmware and I'm unable to get into recovery. I've tried multiple times and get recovery unknown. Anyone wide having this problem?

Yes, I screwed up my phone at one point and ended up restoring to stock.
But OEM recovery is not available to download.
So... I don't have recovery either.
Doesn't matter. Don't need it for anything.
Just need to wait for TWRP to drop and that'll actually be useful.

CZ Eddie said:
Yes, I screwed up my phone at one point and ended up restoring to stock.
But OEM recovery is not available to download.
So... I don't have recovery either.
Doesn't matter. Don't need it for anything.
Just need to wait for TWRP to drop and that'll actually be useful.
Click to expand...
Click to collapse
I just wanted to wipe my cache. I deleted some apps using titanium and they keep showing app stop working message. I haven't screwed my phone up yet, so i think it has something with flashing Google firmware on my Verizon xl. Just a guess

I think recovery is now tied to kernel (boot.img). Flash the stock kernel image in fastboot, then try recovery. Note that when you get into recovery, I think you hit Power-Volume up to get to option to wipe cache.
Or you probably can wipe cache in fastboot (fastboot erase cache used to work on 7.0 and under).

TechBSwift said:
I just wanted to wipe my cache. I deleted some apps using titanium and they keep showing app stop working message. I haven't screwed my phone up yet, so i think it has something with flashing Google firmware on my Verizon xl. Just a guess
Click to expand...
Click to collapse
pixel stock recovery Is without 'wipe cache partition' option
To wipe cache :
Settings/storage/cached data

jasoraso said:
I think recovery is now tied to kernel (boot.img). Flash the stock kernel image in fastboot, then try recovery.
Click to expand...
Click to collapse
I tried that on my phone earlier this week but it didn't work unfortunately.
EDIT: I did the flash-all but just checked and this command wasn't part of this like I thought.

CZ Eddie said:
I tried that on my phone earlier this week but it didn't work unfortunately.
Click to expand...
Click to collapse
I just did it and it worked

Nahh, I still can't get recovery.
I updated to SDK 25 for the latest fastboot.
Did the flash-all.bat.
Then flashed boot.img without error, but still no recovery.
I just get the pissed off Android like in my forum pic.
Code:
C:\Users\Media1\AppData\Local\Android\sdk1\platform-tools>fastboot flash boot bo
ot.img
target reported max download size of 536870912 bytes
sending 'boot_a' (26405 KB)...
OKAY [ 0.660s]
writing 'boot_a'...
OKAY [ 0.305s]
finished. total time: 0.965s

As someone mentioned earlier recovery is part of boot.img. However you should still be able to access it like I did.
You may want to find a "root" cache cleaner. Much easier...
Good luck!

CZ Eddie said:
I just get the pissed off Android like in my forum pic.
Click to expand...
Click to collapse
When you are at the screen with the pissed off Android, if you hold Power and then touch +volume, the recovery menu doesn't appear?

I don't remember the factory image for pixel now and I can't check -no PC) ..but if you unzip the image. zip you should have the recovery.image ( Nexus images) ..if it so try to flash only the recovery..
I was reading ..but really now the recovery is a part of boot.img ?

Scott said:
As someone mentioned earlier recovery is part of boot.img. However you should still be able to access it like I did.
You may want to find a "root" cache cleaner. Much easier...
Good luck!
Click to expand...
Click to collapse
Thanks Mr clean rom ????

cam30era said:
When you are at the screen with the pissed off Android, if you hold Power and then touch +volume, the recovery menu doesn't appear?
Click to expand...
Click to collapse
Oh my gosh. Nothing on the Pixel works like it did on my older phones.
lmao, thank you. That was a step I was missing. I DO HAVE RECOVERY! :good:
It's shown here for anyone else wondering what we're talking about:
https://www.youtube.com/watch?v=vZKRDDMaQV8

@CZ Eddie,
Welcome. That's why I come here. To learn, and to help others.

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