Database Info

[Recovery]Unlocked but cant get a recovery flashed?

Im kinda outta the know, but i see a few Rogers guys that cant root since the 1.94( i think) update but can unlock thru htcdev. Some of you guys are having trouble getting a flashed recovery to stick, so you cant get a rooted rom flashed. Well, there is a VERY simple solution for you guys.
You have your recovery.img in your adb/fastboot folder and your in your device bootloader.
fastboot flash recovery nameofrecovery.img
Ya ya, you tried that, But Wait!
Now
fastboot boot nameofrecovery.img
That WILL boot you into your custom recovery. Now u can nandroid and flash your rooted rom. Once booted up, go download goomanager and install recovery from there. That one WILL stick.
If you ever temporarily need to use the stock recovery, simply put the stockrecovery.img into your adb/fastboot folder and just do
fastboot boot stockrecovery.img
do whatever, after you reboot you will still have your custom recovery, since all you did was boot the stock recovery, not flash it. Also works vice versa
Added:
if you boot a cwm recovery at first steps, after installing recovery thru goomanager go make a new nandroid because twrp wont restore a cwm backup.
Hope this helps out a little:beer:

Could have used this info a few days ago
Bookmarking this.
Sent from my HTC One XL using xda premium

[Q] CM10 to sense help!

Ok so I flashed the cm10 rom today and used CMD to add the boot.img for cm10 but now I want to go back to Viperrom. I flashed the original boot.img using cmd again but I got stuck in a boot loop (kind of) what I mean by that is that if I flash cm10 from the recovery It works fine but I can't flash any other rom without triggering the bootloop so how do I fix this? I can still access both the bootloader and the recovery and I don't want to go back to stock, just to ics roms. Thank you!

Just clear system, cache and userdata and flash viper ROM in recovery, reboot to bootloader then flash the boot.img from the viper ROM zip file.
Generally you get bootloops and such when on the wrong boot.img.

frdd said:
Just clear system, cache and userdata and flash viper ROM in recovery, reboot to bootloader then flash the boot.img from the viper ROM zip file.
Generally you get bootloops and such when on the wrong boot.img.
Click to expand...
Click to collapse
Thanks, so do you have to flash the img of every rom you want to use?

[Q] Flashed boot.img in Fastboot, works - flashed in TWRP, does not work

Hey guys, thanks for all the previous help i've gotten from here.
Here's the deal, I have a 2.2, rooted and unlocked ATT HOXL. I flashed the SU binary and have root and everything. I'm on the stock 2.2 ROM.
Do you need to install a different ROM before flashing the kernel? If so, then I will wait until this download finished for CleanROM. If not, then continue below..
I flashed the boot.img for ElementalX-3.1 in Fastboot (Fastboot 1.14), rebooted phone like normal, phone came up, kernel is showing in the information page on the phone, it is running at 1.7ghz. That's fine, but then I realized I had never gotten any installer or anything. So, I went into recovery to flash the whole ZIP file. Go to reboot the phone and it hangs on boot after the first HTC logo.
I tried flashing the boot.img, then rebooting to recovery, and flashing the ZIP, then clearing the cache, and then rebooting. Still hangs. I am able to go into recovery and restore a backup if I need to, so at least my phone isn't dead, but I want to do this.
I also tried installing the ZIP, then rebooting into Fastboot and flashing the img, and then booting the phone up normal.
So as it sits now, I have the Kernel installed from ONLY the boot.img, I did not run the ZIP.
Do I need to flash a stock kernel in Fastboot, and then try just flashing the whole thing in TWRP? From what I have read, the steps for flashing the kernel on 1.14 is:
1. Flash boot.img
2. Reboot to recovery
3. Flash ZIP
4. Clear cache
5. Reboot phone as normal
Are those the correct steps? Do I need to flash a stock kernel before trying this again, or can I just start from square one, as if I were using a stock kernel?
Thanks

You can't flash kernels from recovery on the higher hboot. You have to fastboot them or use the flash image GUI app.
Some ROMs/kernels use a script that works around that, but not all do.

[Q] Installing CyanogenMod 10.2 stable

I have problems installing CyanogenMod on my HTC One S. When I install it, it gets stuck to boot loop. I was able to recover stock rom using backup I made. I have tried installing twice.
What I have been able to do:
- Unlock bootloader via HTCDev
- Install ClockworkMod
How I try to install CM:
1. I copy zip downloaded from here to phone: download.cyanogenmod.org/get/jenkins/50987/cm-10.2.0-ville.zip
2. I shutdown my phone by long pressing power button.
3. I boot to bootloader by pressing volume down and power.
4. I connect the USB cable (It doesn't boot to recovery otherwise, I don't know why. If I don't connect USB cable it instead boots to black screen.)
5. I select recovery and phone boots to ClockworkMod
6. I select wipe data/factory reset
7. I select install from zip and select the CyanogenMod zip
8. Phone says Installing update... and succeeds in it
9. I select reboot system now
10. Phone is now stuck in boot loop
What do I do wrong?

You are s-on right? You need to flash boot.img from cm-10.2 zip. Just extract the boot.img and flash it via fastboot
Sent from my HTC One S

I'm having the same problem on the C2 variant, except I'm stuck on boot animation. I did flash the boot image found in the zip file.
Anyone having the same problem?

ka_55 said:
You are s-on right? You need to flash boot.img from cm-10.2 zip. Just extract the boot.img and flash it via fastboot
Sent from my HTC One S
Click to expand...
Click to collapse
Yes I have S-ON. If I flash boot.img via fast boot will I be able to restore stock ROM if I want to? How is that done? Do I flash boot.img from my backup via fast boot?

sarcome said:
I'm having the same problem on the C2 variant, except I'm stuck on boot animation. I did flash the boot image found in the zip file.
Anyone having the same problem?
Click to expand...
Click to collapse
I don't know anything about c2 variant. Sorry
Scintillo said:
Yes I have S-ON. If I flash boot.img via fast boot will I be able to restore stock ROM if I want to? How is that done? Do I flash boot.img from my backup via fast boot?
Click to expand...
Click to collapse
I'm not sure %100 if you wil be able to restore stock rom since i didn't try with s-on, but if you have boot.img in that backup, you might need to flash it after restoring process and you should be fine
Sent from my HTC One S

[Q] Is it possible to keep my custom recovery when I update to Lollypop?

I have a N5 rooted and with custom recovery.
I plan to install the factory image via fastboot.
I don't want to lose my userdata, so I plan to extract the different .img files and flash them one by one (except userdata.img)
Can I not flash recovery.img so I can keep my custom recovery?
What are the .img files that I must flash for keeping my files, settings and my custom recovery?
Thank you on advance. You are the best!

I flashed the system and boot img's
Then booted into recovery and wiped caches
Then flashed the modified kernel for root and supersu 2.19 before booting and I've kept data and recovery fine
This boot img - http://forum.xda-developers.com/showthread.php?p=56702681
Sent from my Android 5.0 Nexus 5

Do I need other kernel for being able to root? I was only thinking of installing superSu for getting my root back.
Then, the only .img that I need to flash are the system.img and the boot.img. Am I right?
Thank You!

You need the other kernel, cf-autoroot does this for you.