Database Info

Unable to flash recovery

Just got a replacement phone from Sprint with hboot 2.18, and proceeded to unlock the bootloader, and downgrade my hboot to get S-OFF on my phone. I got all the way through, and flashed my PC36IMG file no problem. I currently sit with S-OFF, HBOOT 2.10.0001, and no recovery(my phone still boots, and functions fine). I tried to use fastboot and use the fastboot flash recovery recovery.img, but it fails. The error is Failed! (remote:not allowed)
Any ideas on how to fix this?

Could a MOD delete this thread? I seem to have solved my own problem. Thanks

Unacceptable lol. Please post how for others to stumble upon if they ever have your problem

Think I messed something up

Not even sure where to start. I've had my One S (TMO) for about 2 weeks now. I immediately followed all the guides to unlock my bootloader, install custom recovery and install custom ROMs. Was running Viper OneS for a while and then switched over to TrickDroid (both 7.0.0 TMOUS and 8.1.0). All of the ROMs seemed to give me some odd issues.
With Viper OneS (after patching my services.jar) I was able to install SManager and run the V6 supercharger script, but after reboot, I was no longer able to get into the ringtone and notification sounds options on the device. When I went to either screen they were just blank and I couldnt choose music from any location on the phone.
With TrickDroid 7.0.0 TMOUS, I was able to patch services.jar and run the supercharger script without any issues at all. However, after a few days of usage, I noticed that calls were no longer forwarding the voicemail number I setup using an MMI code. From there I went to TrickDroid 8.1.0 but even after patching my services.jar, my supercharger settings would not stick after reboot.
Here's where I think something went wrong. I wanted to go back to stock but rooted. Since there were no 2.35 RUUs available for download anywhere, I decided I would download the 1.84 RUU and then get the OTA update. I relocked by bootloader and ran the 1.84 RUU without any problems. Booted up the phone and got the 2.35 OTA update, again with no problems. Unlocked the bootloader and installed TRWP 2.2.2 so that I could flash supersu and root the phone and noticed that the phone was not acting right. From TWRP, its almost impossible to get the phone to reboot. When I choose to reboot, the screen goes blank, flashes once or twice and the notification light keeps turning from orange to green and then back again. I have to hold power down for about 10 seconds, then hold volume and press power to get into bootloader just to turn the phone on.
Decided to try going back to a custom ROM and noticed something else that is strange. I wanted to flash TrickDroid 7.0.0. and during the flashing, it hung on flashing the kernel for like 5 minutes when it usually takes just a second. I then flashed the fusion v2.1 kernel and it hung on "flashing boot.img" for about 5 minutes as well when it normally just takes a few seconds. After the flashing was done, I booted up the ROM and when I went into settings, the new kernel was not installed. I flashed it again in recovery and booted back to the ROM and still the stock kernel was showing.
Could I have somehow really screwed up my phone throughout this whole process? Is something corrupted on the NAND that is causing issues with rebooting recovery and flashing things?

[email protected] said:
I relocked by bootloader and ran the 1.84 RUU without any problems. Booted up the phone and got the 2.35 OTA update, again with no problems.
hung on "flashing boot.img" for about 5 minutes as well when it normally just takes a few seconds.
Click to expand...
Click to collapse
When you did the 2.35 OTA you lost the ability to flash boot.img in recovery. You will need to use fastboot or TWRP's dumlock feature from now on.

dc211 said:
When you did the 2.35 OTA you lost the ability to flash boot.img in recovery. You will need to use fastboot or TWRP's dumlock feature from now on.
Click to expand...
Click to collapse
Thanks for the info! Glad to know I didnt mess anything up .

One other issue I am noticing is that I cannot boot a recovery image from the bootloader using fastboot. My bootloader is unlocked so I boot up into fastboot mode and run the command "fastboot boot recovery recovery.img" but get an error stating "cannot load recovery". The recovery.img file is the CWM 5.8.3.1 recovery that I have renamed to make typing the command easier. To be sure I was connected, I ran fastboot devices and got back a serial number for my device.
Is this also because of the new hboot that I cannot boot directly to recovery from outside of the device? This is so silly but I really don't want to see the *tampered* message in my bootloader. I thought if I could boot directly into a custom recovery from outside of the device, I could run the RUU once more, unlock the bootloader and gain root without having to flash a custom recovery (which gives me all sorts of issues).
Any additional help would be greatly appreciated. Hboot is 1.14.0004 by the way.
EDIT: Wow.... i feel really dumb now. All posts I found while searching included the extra "recovery" in the commany. I just ran fastboot boot recovery.img and all is well.

[email protected] said:
One other issue I am noticing is that I cannot boot a recovery image from the bootloader using fastboot. My bootloader is unlocked so I boot up into fastboot mode and run the command "fastboot boot recovery recovery.img" but get an error stating "cannot load recovery". The recovery.img file is the CWM 5.8.3.1 recovery that I have renamed to make typing the command easier. To be sure I was connected, I ran fastboot devices and got back a serial number for my device.
Is this also because of the new hboot that I cannot boot directly to recovery from outside of the device? This is so silly but I really don't want to see the *tampered* message in my bootloader. I thought if I could boot directly into a custom recovery from outside of the device, I could run the RUU once more, unlock the bootloader and gain root without having to flash a custom recovery (which gives me all sorts of issues).
Any additional help would be greatly appreciated. Hboot is 1.14.0004 by the way.
Click to expand...
Click to collapse
.
I doubt that the actual recovery img is named recovery.img. If I am correct that is your problem. You would be trying to boot a recovery img that doesn't exist. It should be:
fastboot boot recovery [name of recovery file].img
Example:
fastboot boot recovery cwm_5.8.3.1_ville_recovery.img or something to that effect (not sure what the actually file name is)

if you are not sure on exact name as behold mentioned, just right click on the file (.img) wherever you have it on pc, check properties, and it will tell you exact name. at that point i just copy and paste it to command window--

[Q] bricked evo design (kingdom)

well i recently came across a evo design (codename: kingdom), or hero-s as its called in other markets.
long story short, i flashed it to a local carrier revol (similar to metro/cricket).
and during that process i foolishly flashed some non-vol items to it and it is now bricked.
it only boots to the white htc splash and restarts in a loop
i can only access hboot and fastboot. i cant even get into recovery.
the only good things i have going for me are that i have my Unlock_code.bin so i can unlock/relock my bootloader (no s-off on this device)
and that i got a copy of my non-vol items from CDMA Workshop from before i borked it, and a copy of what broke it (from whiterabbit.org)
...im just not sure if thats enough
sucks cause it would be an easy fix if i could just use adb :/
any help is appreciated...tia
-d

a little more info on what ive tried so far
ive installed new recoveries, cwm and twrp, via fastboot PH44IMG.zip...they install fine but will not boot into the recovery.
ive installed the same recoveries via fastboot usb and RUU (flashboot flash recovery recovery.img)...they install fine but will not boot into the recovery.
ive tried the 'downgrade ruu' (RUU_Kingdom_S_Sprint_WWE_2.12.651.5_Radio_1.11.00.1228_NV_SPCS_2.97_removeCIQ_release_234636_signed.exe)...it flashes fine but still a boot loop (phone was 2.12.651.8 originally i believe).
ive tried ics ruu's but all ive found are for boost so i get a cid error...when i changed the cid to sprint i got another error that i cant recall.
i got my hands on sprints newest OTA update (OTA_Kingdom_ICS_35_S_Sprint_WWE_3.14.651.0-2.12.651.8_release_27047061zjyiwl2kn4vskn.zip)....but its a 'scripted update' so it will not install via hboot or fastboot.
i extracted the above OTA update, and retrieved the firmware.zip (contains boot, hboot, radio and recovery) and installed that fine...but no recovery still even after cwm/twrp reinstall.
even though my phone is unlocked its still s-on, so the only things i can manage to install manually with "Fastboot flash" are signed binaries (boot_signed.img and recovery_signed.img) anything else i get "FAILED (remote: 12 signature verify fail)"
anyone know if i can flash the rest of the update without error?
i still have dzdata.img, splash1.nb0,NV_MFG_eMMC_SPCS_2.97_1206_PRL51082.nb, ramdisk.img, rcdata_2.97.img and tp_atmel224_20aa.img maybe one of those will overwrite the spot i fudged up...idk

Trying to escape this bootloop.

So I went and rooted, put viper 5.0.2 on it. However, I was unable to get cellular service, so I decided that putting it back to stock would be the best way to fix that (then I root it again and keep the oem ROM).
I go and RUU it. Put the '0paj5.zip' (or whatever) at "/external_sd" and boot into recovery, update the hboot back to the stock.
Now it's stuck in a boot loop, I can choose to boot recovery, update it again, reboot, or boot into a broken Viper. HTC's specific fastboot can't see the device while it's in Hboot and viper isn't getting loaded enough for ADB to see it. If I can get in and remove the hboot update zip, I think I might be able to get in and actually be useful, but I can't. Following tutorials here on xda, it said to use `fastboot oem lock` so the bootloader is relocked.
TL;DR- HBOOT update zip causing bootloop, get to pick between updating HBOOT (then restarting) and a broken OS. Will provide more details as requested.
Thanks.
EDIT: Was able to stop the loop by pulling the SD card out and now am not in as much trouble.

Phone bricked when trying to flash stock bootloader - which should be what it had already? Help!

So a while back I unlocked and rooted my phone. I did something wrong the first time around and it bricked, so I started from scratch and flashed a stock firmware image, then installed Magisk. I used TWRP, but did not install it. No problems, except the OTA updates don't work, and the phone constantly nags me about it. I had a similar problem on a prior phone (Moto G4+) when the recovery partition was modified, and flashing back to stock fixed it on that phone. I finally get around to trying to fix this, figured Magisk did something to either boot or bootloader, so I re-flash boot.img and bootloader.img using the same images and instructions I originally used to flash my phone. boot.img fails claming bad signature, but bootloader.img succeeds. Now my phone will not successfully boot and claims it needs a factory reset. If I boot to TWRP, I can decrypt and see my data is intact (I explicitly chose not to encrypt my phone for this exact reason but *shrug*). If I install TWRP, it only boots to a TWRP screen and will not accept touch input. Booting TWRP from fastboot functions normally.
So basically, my data is intact. I want it to remain intact. My bootloader is mad at me. What do I do?
I have tried flashing the bootloader.img from multiple versions of the stock ROM and all of them have the same result. Using 'fastboot flash bootloader bootloader.img'
My only theory is that the key was written to the bootloader and flashing stock it doesn't have that key, but that doesn't make sense because what's the point of encryption then (see: I explicitly did not want my phone encrypted).

Update: I was able to fix it and retain all my data by using LMSA to recover it, but I edited the flashfile.xml to remove the step where it wipes userdata.