Develop Bugs

[Q] Stuck on splash after Hboot flash

Edit - Problem was after flashing hboot I could not boot into recovery .... I tried multiple recovery images AmonRa and Cwm but it would never boot.
Solved - I have no idea how, I downloaded the recovery image again with the same link as the previous images, all md5sums were ok, but the 4th download worked and I was able to flash + boot into recovery again? Do I have some other problem though because I don't see why it took so many flashes for me to be able to access recovery again?
Alphrev Cm7 r2
Bravo PVT1 Ship S- OFF
Hboot-6.83.1002
Radio-5.17:52.18
C:\android\tools>fastboot devices
HT~~####93 fastboot
C:\android\tools>fastboot flash hboot bravo_alphaspl-cm7r2.img
sending 'hboot' (512 KB)...
OKAY [ 0.096s]
writing 'hboot'...
OKAY [ 0.164s]
finished. total time: 0.261s
C:\android\tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
C:\android\tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.039s]
finished. total time: 0.040s
Reboot to recovery - stuck on splash??? Using Reflex S...
Edit - After trying to boot to recovery, sat on splash screen for 40 mins and then my bootanimation randomly started... everything is just back to normal?
I can't seem to be able to flash recovery though, it just doesn't boot into it?! I've tried a couple of images and checked md5sum's but it always sticks on splash??

hmm that's strange, suppose you could try to flash a different HBOOT, then try a different recovery - that's what I'd do anyway

bortak said:
hmm that's strange, suppose you could try to flash a different HBOOT, then try a different recovery - that's what I'd do anyway
Click to expand...
Click to collapse
I shouldn't of posted really but something that usually take 10 minutes took an hour or two.... I used the exact command everytime and the same files... It just didn't work!? I'm still really confused but happy it's working

Botched my old recovery, and can't flash a new one...help?

I've been playing around with some of the JB ROMs, and was using Goo Manager and TWRP to do it. Then, because I'm an idiot, I decided I wanted to upgrade TWRP to 2.3.3.0 (I think I was running 2.3.1.0).
That's when I ran into the "TWRP doesn't always install properly" problem. I've now tried updating TWRP from within Goo Manager more than 5 times, but it's not working.
So I decided I'd install the new recovery via the FASTBOOT method.
I have HBOOT 0.92. I have ADB and FASTBOOT loaded on my laptop. (I'm pretty sure this is the way I originally installed CWM 5.0.2.0 when I first rooted my phone ages ago.)
When I boot the phone into the bootloader and choose FASTBOOT, then plug it into my laptop, I get the "FASTBOOT USB" indication that it's connected, so that's good.
However, when I open a terminal window on my laptop, navigate to my miniadb folder (where the fastboot.exe and recovery images are located), and try to flash the recovery image, I see the green bar in the upper right corner of the phone, but on the laptop I get this:
c:\miniadb>fastboot flash recovery openrecovery-twrp-2.3.3.0-inc.img
sending 'recovery' (3642 KB)... OKAY [ 11.235s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 11.268s
So then I decided to give up on TWRP and go back to CWM, but there's no joy there, either:
c:\miniadb>fastboot flash recovery recovery-clockwork-5.0.2.0-inc.img
sending 'recovery' (3064 KB)... OKAY [ 12.370s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 12.402s
What causes the "FAILED (remote: not allowed)" response? Clearly I'm sending the data to the phone, but the phone's rejecting it for some reason.
Does anyone have a suggestion for a foolproof way to get a recovery (either CWM or TWRP--at this point, I'm not picky!) back on my phone?
Thanks!
MC

Check the last two pages of the tarp thread for a twrp hboot PB31IMG.ZIP or see my direct link below.
http://goo.im/devs/tiny4579/mods/PB31IMG-TWRP-2.3.3.0.zip
This method works without fastboot.
Sent from my Galaxy Nexus using Tapatalk 2

Many thanks, tiny! I'll give that a shot.

MysticCobra said:
What causes the "FAILED (remote: not allowed)" response? Clearly I'm sending the data to the phone, but the phone's rejecting it for some reason.
Click to expand...
Click to collapse
For what it's worth, I think you need to upgrade HBOOT to 1.02 or 1.07 and unlock it through htcdev to be able to use the fastboot flash commands. But the flashable zip for TWRP should fix it for you too and that way is easier and just as reliable.

[Q] How to completely restore/un-root/s-on

So, I've no idea how to do this (noob here). I'm on the VZW HTC One. It's rooted, S-OFF, locked (relocked) boot loader, HTC Dev build. What I'd really, really like to do is completely (and I mean completely), relock/reset the phone. I would use recovery, but I can't boot into recovery. After a bit, it restarts and goes into the regular boot. I've tried to flash the default/stock recovery image, but every time I try I get this:
Code:
sending 'recovery' (16383 KB)...
OKAY [ 2.167s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 2.201s
I've got USB Debugging on, so I've got no idea what I'm doing wrong here. I've spent a lot of time looking, but I couldn't find anything that actually fit what I needed.

ingem said:
So, I've no idea how to do this (noob here). I'm on the VZW HTC One. It's rooted, S-OFF, locked (relocked) boot loader, HTC Dev build. What I'd really, really like to do is completely (and I mean completely), relock/reset the phone. I would use recovery, but I can't boot into recovery. After a bit, it restarts and goes into the regular boot. I've tried to flash the default/stock recovery image, but every time I try I get this:
Code:
sending 'recovery' (16383 KB)...
OKAY [ 2.167s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 2.201s
I've got USB Debugging on, so I've got no idea what I'm doing wrong here. I've spent a lot of time looking, but I couldn't find anything that actually fit what I needed.
Click to expand...
Click to collapse
First you need to unlock the bootloader to be able to flash items.
Check it out here: http://forum.xda-developers.com/showthread.php?t=2470340
Then follow the instructions listed here: http://forum.xda-developers.com/showthread.php?t=2475216

[Q] Bricked ?? Please Please Please Help

Hi
I have tried going back to Sense stock after trying out GPE edition lollipop flavour.
Unfortunately somewhere along the way something has gone horrible wrong and I'm now stuck in a bootloop with a Red Triangle
My bootloader is currently locked, althougth I am S-Off. I can still access fastboot and RUU but the problem is when I try to flash standard or twrp recovery i get the following error message
From RUU
./fastboot flash recovery recov.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.442s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.447s
So I currently have no os, no recovery and no way of loading a recovery back on as you can see above... am I screwed ???

Have now managed to put stock recovery back (via ruu) on and at the top of the screen it says entering recovery but never gets any further ...
Have tried again to install twrp ... no joy there what so ever

Dont' Worry I got the same problem but I fixed it!!
gsusx said:
Hi
I have tried going back to Sense stock after trying out GPE edition lollipop flavour.
Unfortunately somewhere along the way something has gone horrible wrong and I'm now stuck in a bootloop with a Red Triangle
My bootloader is currently locked, althougth I am S-Off. I can still access fastboot and RUU but the problem is when I try to flash standard or twrp recovery i get the following error message
From RUU
./fastboot flash recovery recov.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.442s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.447s
So I currently have no os, no recovery and no way of loading a recovery back on as you can see above... am I screwed ???
Click to expand...
Click to collapse
Hi
Press power,volume up and down for 90 seconds.It will enter into bootloader.
Then press recovery. If it is not going to recovery,stay in the bootloader mode. Connect to the pc.
Download this software from this website.
http://www.hasoon2000.info/
Click your phone model.
(If it is HTC ONE M8 CLICK this link http://www.hasoon2000.info/?device=One%202014%20(M8))
Unzip it.
open the software.
Unlock the bootloader by following the step shown on the software.
After,
Click any recovery but I prefer TWRP.
Install custom rom and you are good to go

Absolute legend ... thank you !!!

HTC M8S Flashing Custom Recovery Succesful but can not Boot into / Screen stays Black

Hello, i just created an Account.
I have an Problem with my HTC M8S.
I unlocked the Bootloader via HTC Dev-Website. The next step is to flash a custom Recovery. I tried so via Fastboot-Method.
I got the latest version of TWRP-Recovery and flashed it.
The Windows Command showed:
fastboot flash recovery twrp-3.1.1-0-m8.img
sending 'recovery' (20100 KB)...
OKAY [ 2.106s]
writing 'recovery'...
OKAY [ 2.583s]
finished. total time: 4.689s
after that, i cleared the cache and rebooted. I flashed it many times but it doesnt seem to be working..
When I press the Recovery option in the Fastboot menu. The HTC Logo appears and then the screen turns black. Also the Fastboot menu doesnt show that the phone is "tampered"
Hope you could understand my Problem and maybe help me.
V.M

twrp-3.1.1-0-m8.img is for HTC M8 only, won't work for your HTC M8S.
Read & search the right one here - https://forum.xda-developers.com/ht...ral/make-custom-recovery-htc-one-m8s-t3114245

Thanks a lot, it worked!