Develop Bugs

Stuck at boot ani screen on all AOSP roms

I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.

I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta

jinxzn said:
I don't know if someone already posted this, but searched and couldn't find the answer. I get stuck at boot screen all on AOSP 4.2.2 roms that I tried, but with any TW roms are fine (no problem at all). Can anyone help? I want to run AOSP rom. Thanks.
Click to expand...
Click to collapse
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..

Zachinater said:
I think you may be using a touch wiz kernel
You can find some aosp kernels in the original development thread
Sent from my SAMSUNG-SGH-I317 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I did flashed SOAPKernel along with aosp roms.
wase4711 said:
which rom did you flash, and what did you flash?
the rom only?
the rom and GAAPS?
The rom and kernel?
you need to provide more details if you want to be helped..
Click to expand...
Click to collapse
I flashed BeanStalk, SlimBean, CyanogenMod 10.1 official nightlies, FSC rom, and IllusionRom.
I have CWM Philz_Touch 5.07.1. Every time install a new rom, I wiped Caches + Data / Factory Reset 2x.
I flashed rom only, then flashed rom and GAPPS, those 2 didn't work, I even tried rom w/ SOAPKernel and still didn't work.

ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..

wase4711 said:
ok, you should try switching to TWRP, since most of the time people have zero issues flashing AOSP roms with TWRP.
Also, after all your wipes, flash the rom and GAAPS in the same session, and reboot..
I've done this exact procedure for years, and it works for me 99.98% of the time..
Click to expand...
Click to collapse
Switched to TWRP, and did all the wipes, install rom and GAAPS. Same thing.
Planning to flash stock rom, and redo all the root/recovery procedures all over again. Do you think I should do that?

it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...

wase4711 said:
it couldnt hurt...
some phones are just tempremental; do you have an SD card in your phone?
are you installing from the sd card or internal memory?
try installing from one or the other to see if that helps; sometimes it does...
Click to expand...
Click to collapse
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.

jinxzn said:
I did try both, none work for me.
Thank you so much for your help thou. I'll now just install stock rom and re-root it, see how it goes.
Click to expand...
Click to collapse
good luck, and post back if you get it working properly

flashed stock rom and rooted and installed boot recovery, after all that, it's still not let me install any AOSP roms. Really don't why I can only flash TW roms but not AOSP roms.

[Q] How to choose a ROM

I just got my replacement HTC One V CDMA unlocked and rooted. I want to overclock and understand I need a custom ROM to do so. My first HTC One V I bricked trying to flash rhythmicrom. I unlocked, rooted, backed up using TWM. Each time I tried to flash the new ROM it would get stuck on the HTC screen with the red writing talking about developmental purposes, etc. Each time it would hang on that screen I would simply do a recovery to the back up file and everything would go back to normal. The last time I tried to flash it hung up, and when I tried to go back it would not go back. I am not sure why Rhythmicrom would not work. Is there another one I should try? Does it matter if my HTC one V is a newer version, etc? I just need a basic ROM with the ability to overclock. MMS is a necessity and the camera would be nice. Thanks for any help you can give me.

Did you make sure to flash the appropriate kernel via fastboot aftter flashing the ROM, because if not that could be the cause of your phone failing to boot. As for ROM's, well I guess that depends on whether you have a PrimoU or a PrimoC, I personally use SHPONGLE for the PrimoU, but I can't comment on the PrimoC as I do not own one

zzjoshzz said:
Did you make sure to flash the appropriate kernel via fastboot aftter flashing the ROM, because if not that could be the cause of your phone failing to boot. As for ROM's, well I guess that depends on whether you have a PrimoU or a PrimoC, I personally use SHPONGLE for the PrimoU, but I can't comment on the PrimoC as I do not own one
Click to expand...
Click to collapse
Thank you for the reply. Yes I used the kernel (boot.img) that was included with the rythmicrom rom. I have a PrimoC. I was reading and see that my problem might be caused due to maybe having a newer version of the phone and the hboot or radio might be different?

tackj said:
Thank you for the reply. Yes I used the kernel (boot.img) that was included with the rythmicrom rom. I have a PrimoC. I was reading and see that my problem might be caused due to maybe having a newer version of the phone and the hboot or radio might be different?
Click to expand...
Click to collapse
Hey, so some kernels support the newer radio and some do not. If you are on the newer radio: Baseband version 1.00.00.0928 (check in about phone in settings) then you have to use a kernel that supports the OTA, such as for sense use the FOTA kernel posted under the cdma development thread, for android 4.1 use the kernel I made that can be found in the slim bean rom thread by curtis, and for 4.2 rythmic rom's kernel should work just fine. If not, try the codefirex kernel from simon's rom (original dev. thread) but you'll lose functionality of the camera as it is an ion kernel.
I hope this helps, quote me in the reply if you have more questions, otherwise I may forget to check back here.

why u no flash kernel omg! just read the trouble shooting section

lilrob1213 said:
Hey, so some kernels support the newer radio and some do not. If you are on the newer radio: Baseband version 1.00.00.0928 (check in about phone in settings) then you have to use a kernel that supports the OTA, such as for sense use the FOTA kernel posted under the cdma development thread, for android 4.1 use the kernel I made that can be found in the slim bean rom thread by curtis, and for 4.2 rythmic rom's kernel should work just fine. If not, try the codefirex kernel from simon's rom (original dev. thread) but you'll lose functionality of the camera as it is an ion kernel.
I hope this helps, quote me in the reply if you have more questions, otherwise I may forget to check back here.
Click to expand...
Click to collapse
Thank you very much for you help. I checked my radio and it is 1.00.00.0928. Is this the reason why the rythmicrom kernel would not work? So you recommend using the FOTA kernel with which ROM? Sorry for the dumb questions. I tried my best to read everything I could before asking for help. I just don't want to brick my replacement phone. I am not sue they will be as understanding as they were the first time.

tackj said:
Thank you very much for you help. I checked my radio and it is 1.00.00.0928. Is this the reason why the rythmicrom kernel would not work? So you recommend using the FOTA kernel with which ROM? Sorry for the dumb questions. I tried my best to read everything I could before asking for help. I just don't want to brick my replacement phone. I am not sue they will be as understanding as they were the first time.
Click to expand...
Click to collapse
well it shouldn't have been the reason because if you type "fastboot flash boot boot.img" in command line for the kernel you want to flash then it should flash correctly and rythmic rom's kernel has supported new radio since the beginning pretty much. Unless you have a really old version or something. The FOTA kernel is for sense roms or cm9 (which is based on android 4.0 ics). I really like and very much recommend MyOneV rom that curiousnoob has ported under the cdma dev. thread. It's fast, smooth, and has the least amount of lag compared to any other sense rom that I've tried. It's my daily and go-to rom!
You shouldn't brick your phone as long as you fastboot flash the correct kernel (for primoc/cdma), even if you end up in a bootloop you can hold power button and get back to bootloader to flash a new rom or restore a backup

lilrob1213 said:
well it shouldn't have been the reason because if you type "fastboot flash boot boot.img" in command line for the kernel you want to flash then it should flash correctly and rythmic rom's kernel has supported new radio since the beginning pretty much. Unless you have a really old version or something. The FOTA kernel is for sense roms or cm9 (which is based on android 4.0 ics). I really like and very much recommend MyOneV rom that curiousnoob has ported under the cdma dev. thread. It's fast, smooth, and has the least amount of lag compared to any other sense rom that I've tried. It's my daily and go-to rom!
You shouldn't brick your phone as long as you fastboot flash the correct kernel (for primoc/cdma), even if you end up in a bootloop you can hold power button and get back to bootloader to flash a new rom or restore a backup
Click to expand...
Click to collapse
Thanks for the information. Is it necessary to wipe the sd card before installing the new ROM? This is how I bricked my last one. I read somewhere that I needed to do a full wipe including the sd card. The sd card is where my recovery was and when I wiped it I didn't have anything to recover to. I tried RUU and that did not work.
So I think I might do this kernel [KERNEL][VM/PRIMOC][ICS:Sense] FOTA-Compatible Sick Kernel
With this ROM: myOneV 9.5+CDMA
Does this look ok?

tackj said:
Thanks for the information. Is it necessary to wipe the sd card before installing the new ROM? This is how I bricked my last one. I read somewhere that I needed to do a full wipe including the sd card. The sd card is where my recovery was and when I wiped it I didn't have anything to recover to. I tried RUU and that did not work.
So I think I might do this kernel [KERNEL][VM/PRIMOC][ICS:Sense] FOTA-Compatible Sick Kernel
With this ROM: myOneV 9.5+CDMA
Does this look ok?
Click to expand...
Click to collapse
It isn't necessary to wipe sd card, although if you get any weird bugs that no one else has reported (read threads) then yeah, I'd wipe sd card. In fact, I do actually wipe everything (except sd-ext) from twrp 2.6.1. But before I wipe I mount usb to my computer and copy over the twrp folder with my backup and any pictures I wanna save. Then, wipe everything including sd card (although not necessary I like to do it) and then mount usb again and copy the files I need (rom.zip and twrp folder). But to do a full wipe technically it's just wiping data, cache, dalvik cache, and system.
RUU will not work if you are on the newer hboot version (forgot the number but it's around here which is new vs old).
that combination works for me (I'm on new hboot and radio) so should work fine! btw that's the rom and kernel I mentioned earlier idk if you caught that or not

lilrob1213 said:
It isn't necessary to wipe sd card, although if you get any weird bugs that no one else has reported (read threads) then yeah, I'd wipe sd card. In fact, I do actually wipe everything (except sd-ext) from twrp 2.6.1. But before I wipe I mount usb to my computer and copy over the twrp folder with my backup and any pictures I wanna save. Then, wipe everything including sd card (although not necessary I like to do it) and then mount usb again and copy the files I need (rom.zip and twrp folder). But to do a full wipe technically it's just wiping data, cache, dalvik cache, and system.
RUU will not work if you are on the newer hboot version (forgot the number but it's around here which is new vs old).
that combination works for me (I'm on new hboot and radio) so should work fine! btw that's the rom and kernel I mentioned earlier idk if you caught that or not
Click to expand...
Click to collapse
Cool thank you. Yes I did catch that I just wanted to confirm that was the one you are talking about. I went to download that rom and it said it was not available any longer.

tackj said:
Cool thank you. Yes I did catch that I just wanted to confirm that was the one you are talking about. I went to download that rom and it said it was not available any longer.
Click to expand...
Click to collapse
oh right... curiousnoob is revamping it to make it better, you can either be patient or I can upload you an older version give me a second
here: https://docs.google.com/file/d/0By_o-NyPojUXNTdna3p5bGdSNVU/edit?usp=sharing it's from 09/02/2013 but it's the best I think so far... next update should be awesome-er! haha

lilrob1213 said:
oh right... curiousnoob is revamping it to make it better, you can either be patient or I can upload you an older version give me a second
here: https://docs.google.com/file/d/0By_o-NyPojUXNTdna3p5bGdSNVU/edit?usp=sharing it's from 09/02/2013 but it's the best I think so far... next update should be awesome-er! haha
Click to expand...
Click to collapse
Thank you for all of your help! Will this ROM work with the stock kernel? Just wondering. I would like to overclock so i will be flashing the sick kernel, but I was just curious. Thank you again.

tackj said:
Thank you for all of your help! Will this ROM work with the stock kernel? Just wondering. I would like to overclock so i will be flashing the sick kernel, but I was just curious. Thank you again.
Click to expand...
Click to collapse
kinda... but with stock kernel wifi didn't work... however fota kernel works so great with overclock that there's no need for stock kernel and it's not a problem, I'm happy to help

lilrob1213 said:
kinda... but with stock kernel wifi didn't work... however fota kernel works so great with overclock that there's no need for stock kernel and it's not a problem, I'm happy to help
Click to expand...
Click to collapse
Thank you for the link! I downloaded and got the ROM working now with the stock kernel. Now I am going to try and flash the sick kernel. Just to confirm, this is the one I need:
http://forum.xda-developers.com/showthread.php?t=2261819
I am going to put it in my fastboot folder, rename it boot.img and then flash it using cmd.
Does this sound right?
Also, just an FYI...I received a PM from Curiousn00b stating that the newest version is now available.

tackj said:
Thank you for the link! I downloaded and got the ROM working now with the stock kernel. Now I am going to try and flash the sick kernel. Just to confirm, this is the one I need:
http://forum.xda-developers.com/showthread.php?t=2261819
I am going to put it in my fastboot folder, rename it boot.img and then flash it using cmd.
Does this sound right?
Also, just an FYI...I received a PM from Curiousn00b stating that the newest version is now available.
Click to expand...
Click to collapse
Yup sounds flawless to me! Enjoy it! and thanks for the headsup I will probably download that and test myself

lilrob1213 said:
Yup sounds flawless to me! Enjoy it! and thanks for the headsup I will probably download that and test myself
Click to expand...
Click to collapse
Hey, I got the kernel to work! Now my wifi is operational. Now that the new version is available, do I dare ask how to go about updating? Is it just the same process? Thanks!

tackj said:
Hey, I got the kernel to work! Now my wifi is operational. Now that the new version is available, do I dare ask how to go about updating? Is it just the same process? Thanks!
Click to expand...
Click to collapse
You flashed the fota sick kernel? Well, you can update by just wiping dalvik and cache and flashing the new rom, but it's a full wipe (same process as before) is always recommended over the previous "update"

lilrob1213 said:
You flashed the fota sick kernel? Well, you can update by just wiping dalvik and cache and flashing the new rom, but it's a full wipe (same process as before) is always recommended over the previous "update"
Click to expand...
Click to collapse
Yes, I was able to flash the FOTA sick kernel. I have it set at 1.709 GHz max and 245 mhz min. with the I/O scheduler on noop. I put the governor on "performance" and did a benchmark test with antutu. My score was 7069 which didn't look all that great compared to the others. Does this sound about right? I was also only getting 6.2 fps on the 3D testing.

tackj said:
Yes, I was able to flash the FOTA sick kernel. I have it set at 1.709 GHz max and 245 mhz min. with the I/O scheduler on noop. I put the governor on "performance" and did a benchmark test with antutu. My score was 7069 which didn't look all that great compared to the others. Does this sound about right? I was also only getting 6.2 fps on the 3D testing.
Click to expand...
Click to collapse
hmmm... I have no idea... I've never really messed with benchmarks before, don't think they matter much, I'm happy just having a lag-free phone btw for typical use, I'm sure you know, performance gov. will kill your battery fairly quickly, so I usually use [email protected]$$v2 gov. or lionheart, but usually the first

lilrob1213 said:
hmmm... I have no idea... I've never really messed with benchmarks before, don't think they matter much, I'm happy just having a lag-free phone btw for typical use, I'm sure you know, performance gov. will kill your battery fairly quickly, so I usually use [email protected]$$v2 gov. or lionheart, but usually the first
Click to expand...
Click to collapse
You are right, the phone is more snappy for sure. What GHz do you use for everyday? I was using [email protected]$$v2 gov but put it on performance just during the test. I also have buzzlauncher as my launcher so I am not sure if that is taking away from the performance, but it looks nice. I am just happy that it is working, so again thanks for your help.

[MultiBoot][unofficial]MultiROM V32 [DISCONTINUED]

Whats MultiROM
Multirom is a ROM manager created by Tasssadar with the ability to load multiple ROMs without the need to remove your older one, giving you the ability to test/run multiple ROMs at once, you can also restore TWRP backup as Secondary ROMs allowing you to look at your backup to choose the right one, or maybe just have 2,3,4,5,6 working OS on your phone... just because it's cool.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack.
I Nuked my SDCard twice in porting this tool over, I'm not entirely sure what caused it, but I reverted few changes which might have been the reason, so I hope it wont happen again.
Still, I'll highly recommend you make backups and keep them on your computer. Always.
I've been using this for 2 weeks now with no serious problems, but just as well, don't be blaming me if anything goes wrong.
keep the "i cant get this to work" messages out of my PM i wont bother replying to them,
as almost anyone on this thread can help you.
you have a problem, read the main OP and if you still cant get it to work... post your problem here...
and be specific... "this is not working" will get you nowhere and no answers.​
Special Thanks:​ @Tasssadar: For The MultiROM Source.​
Sources:​MultiROM
Modified TWRP​
Download is one post below.​

Requirements:
S-off/Unlocked Bootloader
Understand How KL Zeus Work*
By Flashing That Kernel, you'd need to flash a 2nd kernel to go along with it..
if you don't follow those instruction, the main ROM wont boot.​
To Install MultiROM:
Flash Zeus Boot.img
Flash Multirom-20141228-v30-UNOFFICIAL-endeavoru.zip normally trough recovery.
Flash Multirom-20150430-v32-UNOFFICIAL-endeavoru.zip normally trough recovery (New Layout ONLY).
Reboot
To Fix Write To SDCard issue(flash on secondary ROM only):Not Needed with New Layout
Flash UPDATE-SuperSU-v2.40.zip(possible only needed on Lollipop, if no, no harm in switching to SuperSU)
Flash SDFix.zip
To Remove ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> List ROM --> Select the ROM To Remove --> Delete
To Add ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> Add ROM
To Remove ROMs:
Reboot Into MultiROM
Boot Into TWRP --> Advanced -- > MultiROM --> List ROM --> Select the ROM To Remove --> Delete
To Change Kernels:
Boot TWRP --> Advance --> MultiROM --> List ROMs --> Flash Modules Zip*
List ROMs --> Remove boot.img
List ROMs --> Add boot.img
* The Modules must be flashed 1st, as the boot.img is replaced with each flash.​
Failed Install & losing memory
MultiROM -> TWRP
adb shell dosfsck -a /dev/block/mmcblk0p14
ToDo:
-- Nothing as it stands

and another one...

Amazing you did it..well done mate glad you are still with us on our dated hox.
Sent from my One X using XDA Premium 4 mobile app

Great!!! Eager to try but its very late night here
Also waiting for your Kernel
Sent from my One X using XDA Premium 4 mobile app

Wow your are just great ...... Will Test it if i have enough time.
Maybe you get tomorrow a pm
Gesendet von meinem HTC One X mit Tapatalk

Thant said:
OK one question maybe stupid but When I install MultiROM.zip from my recovery and then I will restart the phone it will directly start in TWRP and ask me which ROM I want ot boot or how I will go in TWRP recovery when it is not on the recovery partition and it will be posible to flash custom kernel on the others roms 2,3,4 and etc.?
Click to expand...
Click to collapse
It'll be better if i answer this here,
during boot, after flashing MultiROM, MultiROM starts and prompts you to choose what to boot,
Internal (Main ROM), TWRP or other ROMs you installed.
if you want to change kernel of a secondary ROM,
You boot TWRP -->Advance --> MultiROM --> Select ROM --> Remove boot.img
Select ROM --> Add boot.img, then you get to select the kernel you want.
To Flash the Zips/Modules
TWRP -->Advance --> MultiROM --> Select ROM --> Flash Zip
Ill update the OP with these now.

I have a silly question do I have to reflash my current Rom or it will be updated in Boot List Automatically after following above instructions.
Sent from my One X using XDA Premium 4 mobile app

lalit387 said:
I have a silly question do I have to reflash my current Rom or it will be updated in Boot List Automatically after following above instructions.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The main ROM will remain untouched..
but you'll need to know how KL Zeus works to boot it.

Great! I do not have important data in the internal storage, so I can test it.

@Thunder07 I want to test it too

The Current structure of a secondary rom is...
/system 1.25GB
/data 1GB
/cache 436MB
It's a waste having this big of /system partition and small of /data partition...
So i need to know the size of the biggest bloatware ROM so i can shrink the /system partition to it.

Thunder07 said:
The Current structure of a secondary rom is...
/system 1.25GB
/data 1GB
/cache 436MB
It's a waste having this big of /system partition and small of /data partition...
So i need to know the size of the biggest bloatware ROM so i can shrink the /system partition to it.
Click to expand...
Click to collapse
It seems that the Sense based Roms do have a massive system partition. Skydragon 2.0, for example, has system at 922MB in zipped format.

ljjehl said:
It seems that the Sense based Roms do have a massive system partition. Skydragon 2.0, for example, has system at 922MB in zipped format.
Click to expand...
Click to collapse
jeez... 1GB it is then :/

Thunder07 said:
jeez... 1GB it is then :/
Click to expand...
Click to collapse
Though people should keep the really big ROMs like Sense as the 1st OS. It only seems logical enough. By the way, does running a ROM on the internal sdcard slow down the OS at all? I know external sdcards have this issue for sure on other devices.
Sent from my One X using Tapatalk

humzaahmed155 said:
Though people should keep the really big ROMs like Sense as the 1st OS. It only seems logical enough. By the way, does running a ROM on the internal sdcard slow down the OS at all? I know external sdcards have this issue for sure on other devices.
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
I am not complaining for me work perfect I have for main ROM SENSE5 LonelyX and for second SlimKat5.2a and for third CM11 nightly from 25.05.2014 and I don't see lags or something else now my phone work on CM11 for few days after this I think to start SlimKat for few days Main Rom is ok

Thant said:
I am not complaining for me work perfect I have for main ROM SENSE5 LonelyX and for second SlimKat5.2a and for third CM11 nightly from 25.05.2014 and I don't see lags or something else now my phone work on CM11 for few days after this I think to start SlimKat for few days Main Rom is ok
Click to expand...
Click to collapse
You've made me think of trying sense again.
I've only tried aosp for a long time now.
But with multirom I might flash a sense rom again. Would be great to be able to use sense camera for example while running carbon as main rom.
I'm on carbon (main rom) and slimkat (second rom) and they both work fine and smooth.
Maybe only the start up needs a little longer than usual but once it's booted it works fine.
sent from my carbonated Kitty Kat

cappuccina said:
You've made me think of trying sense again.
I've only tried aosp for a long time now.
But with multirom I might flash a sense rom again. Would be great to be able to use sense camera for example while running carbon as main rom.
I'm on carbon (main rom) and slimkat (second rom) and they both work fine and smooth.
Maybe only the start up needs a little longer than usual but once it's booted it works fine.
sent from my carbonated Kitty Kat
Click to expand...
Click to collapse
just now deleted CM11 to many bug for me I missed important notification. The phone beep but I don't see nothing on the screen. Now for this week I think to test SlimKat to see how it works I hope to be stable and don't miss any inportant notification. Whole day I thik on the question why today I have too many free hours and in the end of the day when start main rom I understand why

So I flashed the MultiROM zip through the Aroma installer, when I boot into MultiROM and try to add a secondary ROM, it installs but i can't do much with it after, it doesn't boot either, as for my primary ROM, this goes missing until I actually boot into recovery and reinstall the ROM, any ideas? Or am I supposed to use the Aroma KL Flasher for every boot image? Though it doesn't work because it only asks for a standalone image, not a modules folder.
I flashed the kernel modules through the MultiROM section but everything fails aswell, I know I'm doing something wrong though.

humzaahmed155 said:
So I flashed the MultiROM zip through the Aroma installer, when I boot into MultiROM and try to add a secondary ROM, it installs but i can't do much with it after, it doesn't boot either, as for my primary ROM, this goes missing until I actually boot into recovery and reinstall the ROM, any ideas? Or am I supposed to use the Aroma KL Flasher for every boot image? Though it doesn't work because it only asks for a standalone image, not a modules folder.
I flashed the kernel modules through the MultiROM section but everything fails aswell, I know I'm doing something wrong though.
Click to expand...
Click to collapse
When I add a secondary Rom I also go into the advanced/Multirom/ list and select the Rom I installed. I then remove boot.img, then go back and install boot.img (the boot.img I extracted from Rom), go to the directory I saved that to and it's done. Should boot after that.
@Thunder07,
My current issue seems to be a cache issue. I seem to have to fastboot cache a lot more than I like, otherwise I can't always get to TWRP. Reboot (or from poweroff) more often than not seems to get me only the internal Rom and not the MultiRom startup. I was hoping a wipe cache from device would be sufficient, but no luck.

[Q] HTC Wildfire S stuck on BOOT LOOP

Guys I need help, I have a rooted wildfire S and I flashed a few roms to check out but then when I used data2sd script on EQDKP 5.0 ROM for first time it started giving me this problem cuz every time I restart my phone except for the first restart suddenly after installing ROM) it get's into a boot loop between beats audio and HTC screen and keeps that up I tried everything I tryed using link2sd and disabled relink at boot options I changed roms but now pretty much all roms are doing the same problem except only LEWA ROM that works fine but I got tired of using nd want a sense ROM my kernel right now is 2.6.35.10 cake-gb-3.0-v1.2 at first I thought it was the data scripts but now I'm not using any data2sd kinda script and yet it has the same problem also if I pull out my battery during the loop and put it into recovery and reflash the ROM without any wipes then it starts working again until next boot :/ I also thought it might be some background processing going on so I let it run for like 6 hrs but no avail please help btw my phone is S-ON but bootloader is unlocked by HTC DEV site. PS. This is my first experience with an HTC.

Flash issues
Eagle.x2 said:
Guys I need help, I have a rooted wildfire S and I flashed a few roms to check out but then when I used data2sd script on EQDKP 5.0 ROM for first time it started giving me this problem cuz every time I restart my phone except for the first restart suddenly after installing ROM) it get's into a boot loop between beats audio and HTC screen and keeps that up I tried everything I tryed using link2sd and disabled relink at boot options I changed roms but now pretty much all roms are doing the same problem except only LEWA ROM that works fine but I got tired of using nd want a sense ROM my kernel right now is 2.6.35.10 cake-gb-3.0-v1.2 at first I thought it was the data scripts but now I'm not using any data2sd kinda script and yet it has the same problem also if I pull out my battery during the loop and put it into recovery and reflash the ROM without any wipes then it starts working again until next boot :/ I also thought it might be some background processing going on so I let it run for like 6 hrs but no avail please help btw my phone is S-ON but bootloader is unlocked by HTC DEV site. PS. This is my first experience with an HTC.
Click to expand...
Click to collapse
Which recovery are you using? And confirm your model (GSM/CDMA).
Btw, have you wiped data,cache and system before flashing a new rom?
Try out the marvellous rom and a different kernel

reply
criss_007 said:
Which recovery are you using? And confirm your model (GSM/CDMA).
Btw, have you wiped data,cache and system before flashing a new rom?
Try out the marvellous rom and a different kernel
Click to expand...
Click to collapse
1 I have gsm model
2 I'm using latest clockwork recovery
3 yes i have wiped
4 I think I've tried that but nothing tops EQDKP

Eagle.x2 said:
1 I have gsm model
2 I'm using latest clockwork recovery
3 yes i have wiped
4 I think I've tried that but nothing tops EQDKP
Click to expand...
Click to collapse
Bootloop can happen due to many reasons...wrong kernel, wrong gapps, rom is overclocked to name a few. Some roms are overclocked and this causes problems in some sets.
Try replacing the kernel files manually or flash a recommended kernel that is NOT overclocked.
I'm assuming you did the partitions as required(3 different partitions i think).

such a nube
criss_007 said:
Bootloop can happen due to many reasons...wrong kernel, wrong gapps, rom is overclocked to name a few. Some roms are overclocked and this causes problems in some sets.
Try replacing the kernel files manually or flash a recommended kernel that is NOT overclocked.
I'm assuming you did the partitions as required(3 different partitions i think).
Click to expand...
Click to collapse
Can you please suggest a kernel I'd really appreciate that and I'd prefer if you give me a quick guide too as I've never flashed a kernel before and no I only have 2 partitions one primary and one ext >< I'm sorry I'm such a nube

Eagle.x2 said:
Can you please suggest a kernel I'd really appreciate that and I'd prefer if you give me a quick guide too as I've never flashed a kernel before and no I only have 2 partitions one primary and one ext >< I'm sorry I'm such a nube
Click to expand...
Click to collapse
Try the wildfire s toolkit to flash the kernel and use minitool partition software to make the partitions as mentioned in the rom page

Stuck again
criss_007 said:
Try the wildfire s toolkit to flash the kernel and use minitool partition software to make the partitions as mentioned in the rom page
Click to expand...
Click to collapse
ughh there's no dl link on his forum >< or maybe I can't find it or maybe he took it down and about partitions I'll do that ^^ btw I'm using SmarassV2 and deadline if that makes a difference

toolkit
Eagle.x2 said:
ughh there's no dl link on his forum >< or maybe I can't find it or maybe he took it down and about partitions I'll do that ^^ btw I'm using SmarassV2 and deadline if that makes a difference
Click to expand...
Click to collapse
http://d-h.st/users/hasoon2000/?fld_id=2808
---------- Post added at 10:28 AM ---------- Previous post was at 10:09 AM ----------
Eagle.x2 said:
Can you please suggest a kernel I'd really appreciate that and I'd prefer if you give me a quick guide too as I've never flashed a kernel before and no I only have 2 partitions one primary and one ext >< I'm sorry I'm such a nube
Click to expand...
Click to collapse
And regarding help for flashing kernels and anything else, refer these threads:
http://forum.xda-developers.com/showthread.php?t=1325730
http://forum.xda-developers.com/showthread.php?t=2436684
http://forum.xda-developers.com/showthread.php?t=1680183
Please use the search feature before creating a thread though...most of these topics are already covered in the general section.

[Q&A] [ROM][CM-12.1][Un-official] D2SPR CyanogenMod 12.1

Q&A for [ROM][CM-12.1][Un-official] D2SPR CyanogenMod 12.1
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][CM-12.1][Un-official] D2SPR CyanogenMod 12.1. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Anyone have another download link for this Google drive on my phone just opens the zip as separate files when I try to download it.

bmx26 said:
Anyone have another download link for this Google drive on my phone just opens the zip as separate files when I try to download it.
Click to expand...
Click to collapse
Inside of drive, Try long pressing on it and clicking "download copy" it should download a copy to the downloads folder on your internal sdcard

using this rom cm12.1 for s3 sprint and its working great so far, only noticed two things........ camera not working and Battery but im going to see after a day or two if the battery last the same as the previous rom i was on cm12 (camera was working sort of with the camera zoom fx and viva video work around but i used high speed camera plus instead of camera zoom fx with viva video and it was good)............. so cant wait for a working camera or some kind of work around for this rom cm12.1 s3 sprint.......

Silly mod question.
Im obviously new but was trying to determine where the zip file for the lollipop mod was for sphl710. I see the gapps files but cant locate the mod zip.

brad2512 said:
Im obviously new but was trying to determine where the zip file for the lollipop mod was for sphl710. I see the gapps files but cant locate the mod zip.
Click to expand...
Click to collapse
The google drive link has the file

Open Camera worked with CM 12 about 40-50% of the time.
So maybe it will work well with this one too?
Edit:
Sorry to hear about your laptop woes.
Opening up the laptop to do work and figuring out how it all goes back together again is not a fun prospect.

Brisky86 said:
Open Camera worked with CM 12 about 40-50% of the time.
So maybe it will work well with this one too?
Edit:
Sorry to hear about your laptop woes.
Opening up the laptop to do work and figuring out how it all goes back together again is not a fun prospect.
Click to expand...
Click to collapse
it might. I was reading about some commits on github that broke cameras across the board, stock or from the play store. I tear laptops apart regularly enough to remember how, it's the process itself that sucks

After messaging mastamoon, "I imagine all the stuff that's being worked on is basically in d2-common, msm8960-common and d2kernel which d2spr shares with d2vzw. I would just make sure whoever is building for d2spr is pulling in all the necessary hacks needed at the moment. Honestly I'm not sure what isn't committed at this point, but check out commits by Dave Daynard (nardholio) & Dan Pasanen (invisiblek) and make sure you're using that stuff."
The kernel (within this ROM) he's speaking of might help with the issues revolving around the camera.

Camera Works
Just thought I'd say that both cameras work all the time for me on the 4/09 build.

You said TWRP recovery is recommended but do you think its safe to flash on CWM because that is what I use. I have been thinking of switching Recovery's but don't have a computer to do so. Might try this app called "Flashify" or this "TWRP Manager" from play store that installs it to the device.

fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Good to know thank hou
---------- Post added at 01:53 PM ---------- Previous post was at 01:49 PM ----------
ChangeOfJinzo said:
You said TWRP recovery is recommended but do you think its safe to flash on CWM because that is what I use. I have been thinking of switching Recovery's but don't have a computer to do so. Might try this app called "Flashify" or this "TWRP Manager" from play store that installs it to the device.
Click to expand...
Click to collapse
Make sure you have the latest cwm recovery and you should be fine. I'd recommend flashify, I liked it better and seemed to function better then twrp manager. Also once you install twrp there's a method to update the recovery without a computer or making a recovery updater zip, which can also flash custom kernels. Though I recommend sticking with the stock kernel untill cm12.1 becomes more stable

fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Can anyone else confirm? I've yet to get this build in particular to boot...

iBlowpot said:
Can anyone else confirm? I've yet to get this build in particular to boot...
Click to expand...
Click to collapse
Well dont you have me a little scared now lol. I was gonna flash it tonight but this is the only phone I have until I get another s3, s4, or OnePlus One (don't know which yet) did you do this?
1-boot into recovery
2-Wipe data/Factory reset
3-Wipe Cache
4-Wipe Dalvik Cache
5-Format system
6-Install ROM
7-Install 5.1 Gapps
Did you try all this in the order? I usually do 1-5 Two times to just make sure.
Also make sure you have the latest version of the recovery your on (I use CWM so 6.0.4.5 , I believe that's the latest)

ChangeOfJinzo said:
Well dont you have me a little scared now lol. I was gonna flash it tonight but this is the only phone I have until I get another s3, s4, or OnePlus One (don't know which yet) did you do this?
1-boot into recovery
2-Wipe data/Factory reset
3-Wipe Cache
4-Wipe Dalvik Cache
5-Format system
6-Install ROM
7-Install 5.1 Gapps
Did you try all this in the order? I usually do 1-5 Two times to just make sure.
Also make sure you have the latest version of the recovery your on (I use CWM so 6.0.4.5 , I believe that's the latest)
Click to expand...
Click to collapse
What're you afraid of? If it is "stuck" during installation one could press and hold the power button or remove the battery in an effort to enter recovery again (I've yet to get it beyond installation).
As for the process I use I do the same thing I've been doing for years. Same process I used to install 04/07. I've downloaded and tried at least 5 times.

iBlowpot said:
What're you afraid of? If it is "stuck" during installation one could press and hold the power button or remove the battery in an effort to enter recovery again (I've yet to get it beyond installation).
As for the process I use I do the same thing I've been doing for years. Same process I used to install 04/07. I've downloaded and tried at least 5 times.
Click to expand...
Click to collapse
A long boot can be common after a flash or an update. I've read reports of it taking 30 min for the phone to boot after one or the other.

Lrs121 said:
A long boot can be common after a flash or an update. I've read reports of it taking 30 min for the phone to boot after one or the other.
Click to expand...
Click to collapse
04/09 does not install on my end. I did not make it to the boot animation. It does not go beyond the recovery.

fangorntheent said:
Just thought I'd say that both cameras work all the time for me on the 4/09 build.
Click to expand...
Click to collapse
Can you tell us the recovery, gapps, etc that you are using? Any custom kernels? No one else is having this same luck, unfortunately.

iBlowpot said:
04/09 does not install on my end. I did not make it to the boot animation. It does not go beyond the recovery.
Click to expand...
Click to collapse
Probably a bad upload. I recommend using the new build.
FatalIll said:
Can you tell us the recovery, gapps, etc that you are using? Any custom kernels? No one else is having this same luck, unfortunately.
Click to expand...
Click to collapse
also what bootloader and firmware version

Lrs121 said:
also what bootloader and firmware version
Click to expand...
Click to collapse
Hell, just give us your phone
Also, Lrs121... You had mentioned that you may try and cherry pick updates from other builds where the camera is working. I don't know much about cm source or building but have you considered using something like 'kaleidoscope git diff' to compare builds and see maybe where the camera fix is hiding?
Edit: not necessarily kaleidoscope, but git diff in general.