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

[Q] Rooted etc., then flashed RUU, now unable to install recovery or run su!

This is my saga thus far:
1. Followed the guide ... more or less. For some reason it wouldn't install CWM as PG58IMG.zip via fastboot automatically (it detected it, said it was parsing, then just went back to the menu), but I was able to install the img using fastboot flash recovery recovery.img (where recovery.img was the CWM img). Anyway, everything worked properly, I had the SuperUser app, I could use 'su' in the terminal, etc.
2. I flashed 4EXT Recovery. Also worked perfectly.
3. Played around a bit, whatever.
4. Did a backup via 4EXT.
5. I bought this phone used from eBay, so I wanted to ensure there was nothing malicious hiding in the system partition. So I used RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe, which is precisely what was installed before. That was successful too.
6. Then, when I set things up, Google started "recovering" my apps, i.e., downloading a bunch of apps I had on my old phone. I was not impressed by this. So I went to Settings > Storage > Factory Reset.
7. Then I reinstalled the RUU. I'm not sure if it was necessary or not.
Now I seem to be stuck. I'm not bricked -- I can do everything an unrooted user can do. But I'm pretty sure I'm NOT rooted. The Superuser app's gone, and when I type su in the terminal, it says "permission denied" (which is interesting, shouldn't it say it can't find it at all?). In the bootloader/fastboot, it says S-OFF. It also says **LOCKED** above that. I'm not sure whether that refers to system access (i.e., root permissions) or the SIM (phone was unlocked before). But the strangest part is with ADB. When the phone is on in normal mode, I can install apps, push/pull, etc. But within the bootloader, adb's not recognizing the device at all! What's particularly weird is that the fastboot command IS recognizing it! And when I do fastboot getvar cid, it's still 11111111. But it won't let me flash a custom recovery.
So, I seem to be stuck. It seems to be S-OFF, but I can't flash a recovery. I can't even restore my backup, since I need the custom recovery to do that!
Any ideas as to what I can do to re-root my phone?
EDIT: I'm watching a YouTube vid of the phone being S-OFF'd. When he started off, his bootloader screen looked identical to mine except it said S-ON. When he finished, it said S-OFF, but it also said **Revolutionary** instead of **LOCKED**. OK, so, if I try running Revolutionary again, will it fix things, or will it do nothing or even brick my phone? Will I have to do the S-ON procedure and then start anew?

You have s-off with a locked 1.27 hboot. That's ok, at least you have s-off so you have access. Don't worry about the "locked" bootloader! adb will not connect in bootloader. That is normal. You must use fastboot when in bootloader. As far as a recovery goes, you'll need a PG58IMG with the correct mid in order for it to flash. From bootloader:
Code:
fastboot getvar mid
You can use 7zip to extract the PG58IMG and notepad++ to view the android-info.txt. Make sure your mid is listed... If it's not listed then you can add it, pack it all back up, put on root of sd and flash through bootloader.
Once you have your recovery you will have to flash superuser to regain root access.

I had this exact issue the other day on a gingerbread RUU, to fix it I ran revolutionary even though I was s off already, then rebooted the phone, and flashed this recovery from bootloader
http://db.tt/CElPBgty
This is the only one I managed to get to work, others just said 'parsing' then did nothing
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

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] installing trickdroid screwed up my phone again. stuck on htc screen.

I was installing trickdroid and everything froze up. I cannot get into my recovery and even if I could trickdroid ended up deleting EVERYTHING I had on my sd card even though what I was doing had nothing to do with the contents of my sd.
I am able to get into fastboot. And have managed to install TWRP on my phone. I don't have any recoveries on the phone itself so even twrp is useless to me right now.
I have tried multiple times to go into cmd and use the fastboot command line and tried doing a few recoveries. They all seem to go through but upon reboot it just gets stuck on the htc developers screen forever.
WTF can I do?? =/

Solved.
Took a few hours but I finally managed to find a ruu for my usa tmobile device that had the 1.84 update.
With this I was able to get into my bootloader
using the cmd prompt i did an oem lock and locked up my bootloader (this all over xda and you can find out how to use it that way, it's a lot more detailed)
i was then able to install the ruu through fastboot on my pc
that's the only way I was able to get a single damn thing working.
this morning i tried trickdroid again and the same **** happened. something about the boot.img they have you install, who knows.

I assume your phone is s4 since you are in US
Make sure the Trickdroid you are installing is for your phone--which one you doing
How are you flashing boot.img and when. I wipe all including System, flash rom, reboot into bootloader and fastboot boot.img "fastboot flash boot boot.img" where boot.img is exact name of the boot file image
What is your hboot
Wipe System also as part of your flashing and don't rewipe in Aroma
The OP pages have detailed info on flashing Rom and how to do Tweaks when you get to that point

rugmankc said:
I assume your phone is s4 since you are in US
Make sure the Trickdroid you are installing is for your phone--which one you doing
How are you flashing boot.img and when. I wipe all including System, flash rom, reboot into bootloader and fastboot boot.img "fastboot flash boot boot.img" where boot.img is exact name of the boot file image
What is your hboot
Wipe System also as part of your flashing and don't rewipe in Aroma
The OP pages have detailed info on flashing Rom and how to do Tweaks when you get to that point
Click to expand...
Click to collapse
I made certain I was using an s4 version of the roms. I believe the last one I tried was 7.0?
I was using the boot.img through fastboot. Perhaps I was doing that wrong... i put the phone in fastboot. then it reads fastboot usb. from my computer i went to the folder where i have all my android files and typed in the command for the cmd prompt to run the boot.img and then it showed it installed correctly. but nope.
I played with it again today and I seem to be able to flash ANY rom I have tried so long as I don't actually fastboot any boot.img files. The mixture between the rom and flashing the boot.img on trickdroid really screwed things up but at least I'm up and running again /sigh
I've used trickdroid for a while so it was very surprising that things went so wrong.
Now i just have to wait for the more popular roms to hopefully add wifi calling lol. For right now I've flashed the latest cm10 nightly. Everything is working as it should.

if you are under .13 hboot you don't need to fastboot the kernels. don't remember if you said which hboot you are on
but, glad you got it

[Q] [Help] My HTC One S not booting on after rooting

Hi Everyone,
This is the first time I am playing with a mobile software.
I did the unlock bootloader as per the instructions given in htc website, and my phone status shows unlocked, but it is still S-ON.(Hboot 2.51)
I was planning to install a custom rom either CM11 or MIUI5.
After reading many threads in xda as well as in other sites, I tried to do a S-OFF to install a custom ROM.
I tried Rumrummer, Moonshine and firewater, but nothing has made my mobile as S-OFF.
I tried to restore back to the original stock rom, and followed the process in htconeforum(how-unbrick-restore-htc-one-s-stock-relocked)
So, I tried to do an oem lock and it got relocked.
Now, I tried to do an RUU, and it didn't work with data transfer error.
Only Hboot comes on my phone with the below details
***Tampered***
***Relocked***
My Phone doesn't start now; tried pushing lot of CWM and TRWM recoveries, it got stuck in sending recovery for long time, and i exit.
Can anyone please help me and let me know, how can i restore back to htc rom or go forward and install custom rom.
Thanks,
Deepak

deepak_raja20 said:
Hi Everyone,
This is the first time I am playing with a mobile software.
I did the unlock bootloader as per the instructions given in htc website, and my phone status shows unlocked, but it is still S-ON.(Hboot 2.51)
I was planning to install a custom rom either CM11 or MIUI5.
After reading many threads in xda as well as in other sites, I tried to do a S-OFF to install a custom ROM.
I tried Rumrummer, Moonshine and firewater, but nothing has made my mobile as S-OFF.
I tried to restore back to the original stock rom, and followed the process in htconeforum(how-unbrick-restore-htc-one-s-stock-relocked)
So, I tried to do an oem lock and it got relocked.
Now, I tried to do an RUU, and it didn't work with data transfer error.
Only Hboot comes on my phone with the below details
***Tampered***
***Relocked***
My Phone doesn't start now; tried pushing lot of CWM and TRWM recoveries, it got stuck in sending recovery for long time, and i exit.
Can anyone please help me and let me know, how can i restore back to htc rom or go forward and install custom rom.
Thanks,
Deepak
Click to expand...
Click to collapse
Well i got S-OFF with Rumrummer but i got it till my 7th try. you should keep trying with it

Stuck in sending recovery/sending zip flash
Some how , I managed to push CWM recovery to my phone.
But when I select install from zip, it says "Error mounting SDCard".
I tried the fastboot oem lock using all in one tool kit and now it says Tampered, Relocked.
So, i am trying to run factory RUU exe , it stuck at sending recovery.
I tried to push the .zip factory RUU, and it says sending and stuck there.
Even I tried the adb sideload, it says data transfer failed.
Looks like all the data on the SD card(in my case internal storage) is gone during erase and I don't have any flash zips on the device and I am not able to send any flash zips to the device.
The drivers are installed correctly, and my HBoot 2.15 says fastboot usb when in bootloader, but when i type adb devices, it gives no device.
Can some one please help me in getting my phone back.
Thanks,
Deepak

deepak_raja20 said:
Some how , I managed to push CWM recovery to my phone.
But when I select install from zip, it says "Error mounting SDCard".
I tried the fastboot oem lock using all in one tool kit and now it says Tampered, Relocked.
So, i am trying to run factory RUU exe , it stuck at sending recovery.
I tried to push the .zip factory RUU, and it says sending and stuck there.
Even I tried the adb sideload, it says data transfer failed.
Looks like all the data on the SD card(in my case internal storage) is gone during erase and I don't have any flash zips on the device and I am not able to send any flash zips to the device.
The drivers are installed correctly, and my HBoot 2.15 says fastboot usb when in bootloader, but when i type adb devices, it gives no device.
Can some one please help me in getting my phone back.
Thanks,
Deepak
Click to expand...
Click to collapse
I suggest you get the OTG USB cable. Load the ROM on a Flash USB and then use TWRP to install the ROM (Remember to mount the OTG in TWRP) Check Amazon, it only cost less than $3. I've never push the ROM to the phone. Saves a lot of time when you have multiple phones.