Database Info

Can't boot any custom rom

Hey, first time posting something on this forum but to all devs reading this thanks alot for everything you do!
And Thanks to anyone who can help me!
Now my problem is as following,
My stock rom is RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed.exe
I followed this guide to unlock the bootloader and get root http://forum.xda-developers.com/showthread.php?t=1583427
I used this recovery "Official CWM of koush (HTC One S)" (both toutch and regular has been tested)
Then i downloaded MIUI at first and flashed that(full wipe), it installed fine so i rebooted.
Once i got passed the htc boot screen everything went black, no boot animation.
After that i tested some more Roms, ParanoidAndroid and AOKP Milestone 6.
The exact same thing happend with and exeption for AOKP where the toch keys turned on.
I also noticed it showed up as a removable device in windows from time to time when plugged in (dont if that helps).
After that i restored my one s to stock and then did all the steps again but that yeilded the same results.
I have no idea what the problem is and im hoping its something that has an easy fix and im just to dumb to see it.
If you need any more info just ask, and again thanks for any help!

Before flashing rom through CWM, did you flash boot.img through fastboot. Every rom comes with a boot.img that must be flashed through fastboot when not using TWRP.
T-MobileUS HTC One S running Stock Rooted 2.21.

fmedrano1977 said:
Before flashing rom through CWM, did you flash boot.img through fastboot. Every rom comes with a boot.img that must be flashed through fastboot when not using TWRP.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
Thanks alot! I can't belive i missed that, well it was an easy fix just as i figured.

Daikar said:
Thanks alot! I can't belive i missed that, well it was an easy fix just as i figured.
Click to expand...
Click to collapse
just use twrp and problem solved.
CWM IMO sucks in comparison. Not to mention the level of support with TWRP is so far and above ANYTHING you will get with CWM.

Viper XL and boot.img

Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!

ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Wipe flash Rom flash boot IMG sit back enjoy

ImagioX1 said:
Hey guys I just wanna to check and make sure I'm doing everything right before I flash cause I don't need anymore paperweights
1.I have successfully unlocked my bootloader and installed twrp recovery and rooted.
2. Now I want to back up my entire setup: rom, apps, setting, data, everything so that if I ever want to return to stock then I can. I have booted into twrp and ran backup and selected all options. Is that how you perform a nandroid backup in twrp or is there more to it?
3. I want to install team venom viper xl rom. Do I have to first flash boot.img first or is the kernel the same in stock and viper xl so that isn't necessary? Do I have to do I factory reset first or what?
I'm still new to this stuff so please bear with me. Thank for all your help!!
Click to expand...
Click to collapse
Different kernel. it is using the 2.41 RUU. So go ahead and flash the boot.img
Here's what you should do for any new ROM with a different kernel.
Wipe System
Factory Reset
Flash boot.img
Flash the ROM
flash gapps (if AOSP based)
reboot and have fun
When doing a nandroid backup, it is only necessary to backup
System
Data
Boot

Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?

ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
You backed up fine, it just takes up a little more space.
You have to extract the boot.img from the ROM and put it in the same folder as fastboot.exe
open command prompt, and navigate to the folder fasboot.exe is in and do the following command
fasboot flash boot boot.img
If it gets stuck at waiting for device, reboot into your bootloader, boot into fastboot from there. and then try again.

ImagioX1 said:
Ok thanks for your response but I'm still a little confused. First did I back up my current rom properly so that I can return to it later on? Secondly does viper and boot img have to be flashed or can they be installed from sdcard via twrp? If they have to be flashed whats the fastboot command.?
Click to expand...
Click to collapse
Viper is the Rom u flash it from twrp it's. azip file that's fkashable so make it easy and flash viper there and than flash the boot IMG from fastboot the command is all over the forums I thinks it fastnoot flash boot.img

don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read

DvineLord said:
don't be confused. read.
you always have to flash boot.img in fastboot "fastboot flash boot boot.img" then flash the zip in twrp make sure to wipe, and don't download international roms. you still have to flash the boot.img from your backed up rom.
like a hundred threads asking the same stuff because no one wants to read
Click to expand...
Click to collapse
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.

ImagioX1 said:
I'm sorry but I did read. I saw that if you have the same kernel as that of the rom you're flashing you don't have to flash boot.img. So I asked to see if stock and viper have the same kernel. I don't want to flash anything that will brick my phone.
Now one more question if you don't mind answering. I also saw that you can't downgrade RUU. So if viper is based on 2.41 RUU and stock is 2.20 RUU then will I be able to go stock after flashing viper?
I really do appreciate yalls help. i would be where I am if it weren't for you.
Click to expand...
Click to collapse
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom.
If you want true stock 2.20 then you will have to relock your bootloader and then run the 2.20 RUU. You would only want to do this if making a warranty claim or something. If you want stock rooted, then yes, do what I said above
Sent from my HTC One XL using xda app-developers app

absolutelygrim said:
Yes. Just wipe you system and do a factory reset , and flash the boot.IMG for 2.20 and then flash the Rom
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Ok got it. I do appreciate your help. Flashing now.

downgrading only refers to the ruu not the zipped roms. so you can't run 1.85 ruu after running 2.20 ruu/ota but you can still flash a rom based on 1.85.
if you are reflashing the same rom you don't have to reflash boot.img but if you are flashing a new rom then you need to flash boot.img. 7-zip will tell you the crc32 of files so you see tell if it's a different checksum.

Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?

ImagioX1 said:
Viper Xl's great. Seems to be slightly slower than stock on some task, but the lack of bloatware, and the extensive customization is worth it. Haven't found any bugs or nothing so far. If anyones familiar with viperxl though what is the last app in the app drawer? Its got a chinese name? When it loads it says Dolby Surround but all the writing is in chinese?
Click to expand...
Click to collapse
That's because you flashed the Voodoo mod, it's apart of the mod, theres a chinese part and a english one called "Dolby Digital" or "Dolby Surround"

When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?

CrossFire78 said:
When I flash ViperXL 3.1.0 JB do I need to flash a radio too? My phone has hboot 1.4 and software 2.2, so I understand that I cant flash radio with hboot 1.4? Does this mean I need to downgrade my hboot/software version?
Click to expand...
Click to collapse
Most people have good luck w/out flashing another radio.

ronnie498 said:
Most people have good luck w/out flashing another radio.
Click to expand...
Click to collapse
Hmm. Might there be a patch I'm missing out on? I just flashed one file -ViperXL 3.1.0 JB - Android File Host (692MB)
edit- Works now after another reinstall installed boot image first this time.

[Q] Please help, no Android installed, cannot install, phone stuck on HTC logo

Long time lurker first time poster. I had a Nexus One two years ago so I was here very very often.. Since I got my Desire S a year ago, I haven't been able to flash a custom rom OR S-OFF.
Unlocked with HTCdev, rooted, HBOOT 2.00.0002 (downgrading hboot never worked either), S-ON
Last night I tried again to get onto ICS (official RUU doesn't install either). I installed 4EXT touch, flashed recovery, had my ROM (Fallout) on SD ready. Rebooted phone into new recovery to find that is was still the OLD revolutionary recovery and not 4EXT. This was 4am so I thought I'd try the usual wiping + rom flash. It went through normally and said completed although the progress bar only got about 1/3rd before jumping straight to finished. Rebooted.. stuck at white HTC logo screen.
My issues are that I cannot install HTC Sync phone drivers without phone powering up to be recognised by the PC, AND I cannot turn USB debugging on for obvious reasons
My phone is veryvery important and I'm now scared I won't be able to get it working again. Please help me.
TLDR; stuck on White HTC logo screen, no Android installed, cannot see how I can install one, help!
If anyone could shine some light on what I need to do next, I'd be very grateful.
Thanks in advance.. and afterwards

How did you flash the recovery? In fastboot? And did you flash the boot.img (also in fastboot) of the Rom you flashed?
You should definitely have read more before flashing anything...

teadrinker said:
How did you flash the recovery? In fastboot? And did you flash the boot.img (also in fastboot) of the Rom you flashed?
You should definitely have read more before flashing anything...
Click to expand...
Click to collapse
For the 4EXT recovery I 'flashed' it from inside the touch app thinking that was enough these days.. naively. Had just been fighting with GF at 4am and was fed up and about to go to bed and in Revolutionary recovery so I thought what the hay, I'll wipe etc in here and use this to try and flash the rom.
I did not flash the boot.img. I goofed. I understand that but now I'm just desperate for any route back to a functional device.
I never stopped installing ROMs and etc on my old Nexus One but that was a while ago and everything just seemed to work. Desire S is being a nightmare.

Decide what you want to do.
If you want to upgrade the phone to official ROM - relock your bootloader and run RUU.
If you want to use custom ROMs - flash the recovery from fastboot and don't forget to flash the kernel from fastboot too.
I won't get into any more details, searching for the right info with these pointers will get you whatever you might need.

Thank you, I'm all fixed. Simply found an old 2.3.5 ROM and flashed and booted fine. Reason I was so stuck was because I had formatted my PC since last installing phone drivers so I couldn't do much hurdur

[Q] Boot loops after flashing ANY rom

I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?

Do you have the latest TWRP 2.4.1.0 ? (did you try reflashing your recovery?)
What android did you have before unlocking your bootloader? 4.0.3 or 4.0.4?
(and don`t panic If nothing works there is always a solution by relocking your phone and flash the ruu for your phone from here)
http://www.androidfiles.org/ruu/?dir=VilleC2
take a look here:
http://forum.xda-developers.com/showpost.php?p=37498221&postcount=309

impactor said:
I have S3 right here and I tried flashing Trickdroid ICS, JB as well as JellyBean Official TWRP zip.
It is S-ON, so after flashing the zip, I go to fastboot and flash boot.img.
I did it already 2-3 times with every rom, but every time I get boot loop. Phone restarts as soon as the first HTC logo disappears.
What is wrong with that?
Click to expand...
Click to collapse
What's was you on before flashing a custom rom? because just a guess but I think it was 4.0.3 if that is so then try TrickDroid for S3 and get v3 which is 4.0.3 so should work.

It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?

impactor said:
It was stock, but I didn't check the version before flashing.
So, TD 3.0, then TD 5.0 and it will work?
By the way, what is better? TD 5.0 or JellyBean Official TWRP?
Click to expand...
Click to collapse
No only v3 but if you can get an RUU thats more up to date then do that and the v4/5 should work.

So you didn't install a custom kernal before
Sent from my KFTT using xda premium

KindleFireGuy said:
So you didn't install a custom kernal before
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
Em what he said he did.

You cannot flash S4 roms with an S3 phone, have you made sure that the Roms you flash are specifically assigned for S3? Cuz most are S4

Thanks, guys. That was HBOOT problem. I flashed latest RUU and then I was able to use JB roms.

I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!

pcout64 said:
I am terribly sorry to bump this thread but it is EXACTLY what I need. I read through it and am slightly confused with what you guys said.
Here's my situation:
I have a HTC Evo 3D and have tried running multiple ROMs and on every ROM I run into a boot loop. I use TWRP 2.2.0 and boot that onto my phone using the code "Fastboot boot twrp-shooter.img", then from there I go into TWRP and add the ROM to the root of my SDcard. Then I use TWRP to wipe my cache, delvik cache, system, and do a factory reset. Then I go to install from SDcard and install my desired ROM that I am trying. It is successful and when I reboot it shows the HTC logo, then the loading screen for the ROM, then it goes black, then back to the HTC logo and it continues to loop the same booting sequence over and over.
Am I doing something wrong? Is there something different that I should use or do?
I've been trying to figure out this issue for more than 36 hours and I am borderline psycho right now, I really need answers!
Click to expand...
Click to collapse
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone

asdfasdfvful said:
1. check if you are s-on or s-off. If you are s-on, you will also need to flash the kernel (boot.img) from a computer (after you flash the zip)
2. make sure your rom is compatible with your phone
Click to expand...
Click to collapse
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002

pcout64 said:
I already know that I am s-on, and that all I need is the RUU because all I want is to get right the hell back to stock. The problem is that I can't find a RUU that is compatible with my phone!! Your help searching for one would be amazing!!
HTC Evo 3D CDMA Sprint
Mainver: 2.95.652.5
CID: SPCS_002
Click to expand...
Click to collapse
Still new to xda, but check this out?
http://forum.xda-developers.com/wiki/HTC_Evo_3D/CDMA
(ctrl + f and find "ruu")

My mainver is not listed, I have already seen this page
The page was last edited in November of 2012, I think it's a bit out of date

[Q] Having Issues Flashing Rage ROM

Hello, all. I am a pretty experienced flasher, and I have been running HatkaXL on my device for quite some time now. I saw where a new ROM had developed, and tried to flash it last night (with no luck). My device is S-ON (I would consider going S-OFF, I just do not understand the terminology with SuperCID and all that good stuff). Anyway, I downloaded the ROM, patch, and wiped (completely). I formatted /system, performed a factory data reset, wiped the cache and dalvik cache. I installed the ROM and patch, and tried to reboot afterwards. I went into a bootloop. I did a restore, downloaded both files again, but I put the boot.img file aside and flashed it separately (after the ROM and patch the next time). I still got a bootloop. Any suggestions?

Worked fine for me. I flashed it a few times due to trying to mod it and being unsuccessful lol.
Sent from my HTC One XL using Tapatalk 2

Method of Recovery
InflatedTitan said:
Worked fine for me. I flashed it a few times due to trying to mod it and being unsuccessful lol.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Just out of curiosity, were you using TWRP or CWM? I have been running the supported version of CWM (I have always liked it better for some reason). I think it's the cool hat and orange eye, but just wanted to see if maybe you used TWRP?!? Note: HatkaXL has been flashing flawlessly on CWM, so...just wondering.

mikenjen0524 said:
Just out of curiosity, were you using TWRP or CWM? I have been running the supported version of CWM (I have always liked it better for some reason). I think it's the cool hat and orange eye, but just wanted to see if maybe you used TWRP?!? Note: HatkaXL has been flashing flawlessly on CWM, so...just wondering.
Click to expand...
Click to collapse
I would use TWRP 2.3.3.1 or below (no issues and is compatible with all roms) If you intend to switch, after flashing a new recovery you should always fastboot erase cache.
When you say you flashed the boot.img seperately did you flash it in CWM or using fastboot? It should be done with fastboot.
SuperCID is just a changed CID to 11111111 or 22222222 from default. Default CID is different from carrier to carrier. If you have an AT&T phone and had to root/unlock bootloader, you have SuperCID.

Thanks
exad said:
I would use TWRP 2.3.3.1 or below (no issues and is compatible with all roms) If you intend to switch, after flashing a new recovery you should always fastboot erase cache.
When you say you flashed the boot.img seperately did you flash it in CWM or using fastboot? It should be done with fastboot.
SuperCID is just a changed CID to 11111111 or 22222222 from default. Default CID is different from carrier to carrier. If you have an AT&T phone and had to root/unlock bootloader, you have SuperCID.
Click to expand...
Click to collapse
I never knew about the fastboot erase cache thing (thanks). I got it just a few minutes ago. It would not go with just flashing the two files and then rebooting. I had to manually boot into bootloader, reboot my computer (to get fastboot to recognize my device), and then flashed the boot.img via adb. I don't know why it was such a bugger, but I finally got it.