Develop Bugs

Hercules and ROM problems

Being new to Android I succeeded in rooting, installing TWRP to my Tmobile SII..
Then I went ahead and backed up my current stock ROM..
Then went and downloaded CM10 from their website since it's stable.
I erased the old ROM and installed CM10 as the guide suggests.
After booting, however, I had a problem. The phone was very laggy and trebuchet was constantly crashing.. I then decided that this ROM must not be stable and looked for more stable ROMS..
GalaxySbean_V13.5
MIUI.us_hercules_v4.1_2.12.28_Eng_Deo_ZipA_Signed_0xD34D
rootbox_hercules_unofficial_Feb-20-13
.. and couple more.. All running very slowly.. and crashing constantly..
What am I missing?
Is it a problem that I didn't format the internal memory?
If it makes a difference.. TWRP is version 2.4.1.0
Thank you!
I am hoping I can find something faster.. I'm sick of the stock Samsung.. :crying:

What was your flashing method or steps you took to flash? Also, update to the latest TWRP 2.4.3.0 and get the latest version of the ROM you want to flash. Also, CM10 is not as smooth as 10.1 so you might want to give the latest nightly a go.
EDIT:
A good setup would be:
-CM10.1 latest nightly
-Cerux Kernel ASDK (They both are good)
-Latest gapps (3-1-13 I think)
-Crossbreeder mod

batezippi said:
Being new to Android I succeeded in rooting, installing TWRP to my Tmobile SII..
Then I went ahead and backed up my current stock ROM..
Then went and downloaded CM10 from their website since it's stable.
I erased the old ROM and installed CM10 as the guide suggests.
After booting, however, I had a problem. The phone was very laggy and trebuchet was constantly crashing.. I then decided that this ROM must not be stable and looked for more stable ROMS..
GalaxySbean_V13.5
MIUI.us_hercules_v4.1_2.12.28_Eng_Deo_ZipA_Signed_0xD34D
rootbox_hercules_unofficial_Feb-20-13
.. and couple more.. All running very slowly.. and crashing constantly..
What am I missing?
Is it a problem that I didn't format the internal memory?
If it makes a difference.. TWRP is version 2.4.1.0
Thank you!
I am hoping I can find something faster.. I'm sick of the stock Samsung.. :crying:
Click to expand...
Click to collapse
Basically wipe factory defaults and go into mounts and format system. Flash the rom of your choice. I use a custom kernel which supports overclocking and custom governors which may help with the problem. Also you should run fix_permissions to fix the pesky FC's. I run Liquid Smooth with All Star Kernel and it is very fast and smooth. Stay away from anything 4.2 as it isn't stable yet.

batezippi said:
...After booting, however, I had a problem. The phone was very laggy and trebuchet was constantly crashing.. I then decided that this ROM must not be stable and looked for more stable ROMS...
Click to expand...
Click to collapse
I'm not an expert, but I noticed that every ROM post suggests leaving the phone alone for 10 minutes or so after first boot. Did you give CM time to settle after the flash? The ROMs all seem to need time to settle according to the forum posts. I'm running ptmr3's Jedi CM Build 2, which is android 4.2.2. It seems quite stable to me at the moment, but it also seems better after having used it for a few days and rebooted a couple times.

treefrog321 said:
I'm not an expert, but I noticed that every ROM post suggests leaving the phone alone for 10 minutes or so after first boot. Did you give CM time to settle after the flash? The ROMs all seem to need time to settle according to the forum posts. I'm running ptmr3's Jedi CM Build 2, which is android 4.2.2. It seems quite stable to me at the moment, but it also seems better after having used it for a few days and rebooted a couple times.
Click to expand...
Click to collapse
Hmm.. To be hones.. I didn't!

I am going to update TWRP and then I am going to go for this one
http://forum.xda-developers.com/showthread.php?t=1885619
EDIT*
Did that:
TEAMWIN Recovery (TWRP) 2.3.3.0 or later
Wipe
Cache
Dalvik cache
Factory Reset
System
Flash Rom
Reboot
Wait a few minutes
Reboot
Done with flash procedure
Phone is still laggy and very unresponsive.. Unusable! What am I doing wrong?

I'm very new to ROMs and phone tweaking in general, having only flashed less than a dozen ROMs and various tweaks in the last month, but I've never encountered any issues.
My steps:
I use CWM
Nandroid backup
Wipe data
Wipe cache
Darkside Super Wipe
Flash ROM
Flash GAPPS
Wipe dalvik
Fix permissions
Reboot
Wait at least 10 minutes, never less(if you only waited literally a few minutes that might be an issue?)
Reboot, set up Google, etc.
Done.
Never encountered any issues in my young flashing life.

Try this rom
Wanna good fast stable rom? Then try All Star v7....

You might wanna try wiping cache/dalvik factory reset and system a couple of times before flashing. Sometimes that helps

[Q] Kernel flashing steps

Hi,
I am considering to flash ElementalX kernel and CleanRom on my stock nexus 7 2013 wifi. Is it correct if the steps I take are:
1. Rooted with Toolkit (i. unlock bootloader and ii. root?)
2. Flash CleanRom
3. Flash Stock kernel (is this step necessary?)
4. Flash ElementalX
Please let me know if there are other steps or things that I need to be aware. Thanks!

For step one you have to unlock boot loader in order to root. You also need to flash a custom recovery such as twrp or clockworkmod.
Also step 3 is unnecessary. After you flash cleanrom, you should just flash ElememtalX. Have fun
Sent from my Nexus 7

The toolkit will do it for you, I recommend TWRP recovery.
After that just flash the kernel.
Remember always to follow instructions.

Hi, i've got a total noob question about flashing the kernel. I've already unlocked, rooted and installed a custom rom on my Nexus (CM11) and i was just about to install the Glitch kernel for it. My question is: can i change the settings of the glitch kernel later? I mean if i choose now to overclock my cpu/gpu or underclock it, can i change it later without going into recovery and flashing the kernel again? It would be a bit of a chore to change everything all the time just to listen longer to music, or play some games at better fps... (battery vs performance)
And do i have to wipe the device before installing the kernel?
EDIT:
Ok, so i've tried to flash my kernel, but it just won't work. Always locks on boot, and i have to restore back to stock and try again. These are the steps i take:
1. install CM11 (20140324 nightly-flo build)
2. Install gapps
3. install kernel (glitch, bulletproof, elemental x - i always choose newest android 4.4.1 build)
4. brick
It doesn't matter if i go wild and choose some crazy oc and undervolting, or just as close as possible to stock (with some tweaks) it always ends the same. Light blue screen with green stripes, or it won't boot at all.
any suggestions?

DoczuPL said:
Hi, i've got a total noob question about flashing the kernel. I've already unlocked, rooted and installed a custom rom on my Nexus (CM11) and i was just about to install the Glitch kernel for it. My question is: can i change the settings of the glitch kernel later? I mean if i choose now to overclock my cpu/gpu or underclock it, can i change it later without going into recovery and flashing the kernel again? It would be a bit of a chore to change everything all the time just to listen longer to music, or play some games at better fps... (battery vs performance)
And do i have to wipe the device before installing the kernel?
EDIT:
Ok, so i've tried to flash my kernel, but it just won't work. Always locks on boot, and i have to restore back to stock and try again. These are the steps i take:
1. install CM11 (20140324 nightly-flo build)
2. Install gapps
3. install kernel (glitch, bulletproof, elemental x - i always choose newest android 4.4.1 build)
4. brick
It doesn't matter if i go wild and choose some crazy oc and undervolting, or just as close as possible to stock (with some tweaks) it always ends the same. Light blue screen with green stripes, or it won't boot at all.
any suggestions?
Click to expand...
Click to collapse
That means you're flashing the incorrect version of the kernel, from now on if you are flashing a rom see if its CAF-based or AOSP-based, for example CM is CAF-based, so you'll need to flash the correct version of the kernel, look in the kernel threads for the CAF kernel download, I know that Glitch and ElementalX have kernel compatible for CAF -based roms

DoczuPL said:
Hi, i've got a total noob question about flashing the kernel. I've already unlocked, rooted and installed a custom rom on my Nexus (CM11) and i was just about to install the Glitch kernel for it. My question is: can i change the settings of the glitch kernel later? I mean if i choose now to overclock my cpu/gpu or underclock it, can i change it later without going into recovery and flashing the kernel again? It would be a bit of a chore to change everything all the time just to listen longer to music, or play some games at better fps... (battery vs performance)
And do i have to wipe the device before installing the kernel?
EDIT:
Ok, so i've tried to flash my kernel, but it just won't work. Always locks on boot, and i have to restore back to stock and try again. These are the steps i take:
1. install CM11 (20140324 nightly-flo build)
2. Install gapps
3. install kernel (glitch, bulletproof, elemental x - i always choose newest android 4.4.1 build)
4. brick
It doesn't matter if i go wild and choose some crazy oc and undervolting, or just as close as possible to stock (with some tweaks) it always ends the same. Light blue screen with green stripes, or it won't boot at all.
any suggestions?
Click to expand...
Click to collapse
ElementalX kernels newest build is 4.4.2 not 4.4.1 and also a good tip stated above to see if you need a CAF of AOSP kernel.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

Thanks for the advice, i'll try to flash it again when i'm back home. Cheers guys!

Cyanogenmod

So on the cyanogenmod website, they have cm11 nightlies and snapshot builds. However, there are no instructions. Do I need to have a lokified recovery? Or can I just install cwm. Other than that, its the basic flash ROM and gapps.

stew1411 said:
So on the cyanogenmod website, they have cm11 nightlies and snapshot builds. However, there are no instructions. Do I need to have a lokified recovery? Or can I just install cwm. Other than that, its the basic flash ROM and gapps.
Click to expand...
Click to collapse
i have always flashed with freegees cwm, i think that is already lokified

Just install the recovery via freegee, then do a clean install.The gapp should be signed 4.3_kk. Once you install cm11, all the updates can be done through cmupdate or cyandelta if you're using the nightly.

FreeGee recoveries are lokified, but you have to be coming from stock 4.1.2 in order to use FreeGee.

Also the cwm on freegee needs to be Loki toggled in advanced within recovery or it will not install correctly.
2SHAYNEZ

shayneflashindaily said:
Also the cwm on freegee needs to be Loki toggled in advanced within recovery or it will not install correctly.
2SHAYNEZ
Click to expand...
Click to collapse
Never had to do that... Weird

I always go toggle it.. Weird .. Things always are different for me for some reason. Oh the joy of being a half ginger bearded bad ass lol??
2SHAYNEZ

shayneflashindaily said:
Also the cwm on freegee needs to be Loki toggled in advanced within recovery or it will not install correctly.
2SHAYNEZ
Click to expand...
Click to collapse
Never had to toggle Loki either on freegee, it mention something like that in an message while I was using freegee. Installing cwm with freezer is quit simple, choose my recovery ,then cwm is installed. The rom manager can also be used to install an older version of the recovery (they try to make unaware user buy the newest version of cwm) , I didn't really discover that until I already used freegee
Sent from my LG-E980 using Tapatalk

I used freegee to install cwm to use only once so I could install philz. Used philz to install cm 11. Everything works great so far. Battery life sucks. So I bought a spare battery and a battery dock.

The battery was bad for me as well when I first started to use cm11. I adjusted the CPU governor and turned off all the bell and whistle that I didn't need, nothing, the battery was draining quicker than I could charged, if that even made any sense. One day I soft bricked the phone, and had to reinstall. Did a clean install, and magically every thing was running smooth as butter. Even the abnormal batter drain was gone. I can only blame my previous battery issue on dirty ROM installation.

[Q] [SGS2 T-989]Wierd !!! Help plzzzz..all custom roms crashes

Hello guys i'm very new to SGS2 T-989 ...and recently got this 2 year old t-mobile sgh t989 ...and it worked fine for few day..till i trid cm11 as first custom rom on it..it too worked well until i used camera...it rebooted itself ...i thought it was because cm11 is nightly ..so i tried carbon rom ...it worked quit fine for a while......for some reson it to started rebooting after a while ..lastly i tried cm10.2 stable ...it worked quite good i updated with cm updater then after it worked good and affter a while it too strted rebooting ...i thaught of power button failure and replaced it too....and finally flashed stock JB 4.1.2 rom ...it works quite well even till now..but the problem is that i cant install custom roms on it ...any help would be honey in my throught...does any one have the issue...???.....................finally got to tell i'm new to this mobile not for customization of roms ..i tried every thing wipe/data/F.Reset/Delvik/System...and even trie super/dark wipe script too.....hmm the matter is unable to install custom roms/////

What recovery are you using? (latest is 2.8.1.0) get it here! Flashable .zip HereWich Gapps? . . . Stock 4.1.2 have some firmware upgrades so maybe you're good to go now if not you might want to try installing stock via Odin (kill any Kies process before using Odin). Find stock rom Here! You will need to register to dwl. Ooh and dont use darkside wipes scripts as they are outdated, you can/will brick your phone. Just wipe system, data, cache, dalvik and .android_secure

I'm using cwm 6.0.4.3 ...and I flashed stock rom the latest ...I have root and cwm backup too...stock rom works completely perfect ....prblm is with custom roms..

Keep a copy of cmw and your backups just in case and try flashing using twrp. Also read this thread , "Have you ever used odin to flash the factory 4.1.2 UVMC6 rom? Some driver stuff was updated in that version and can only be installed with odin."

I've used odin 3.0.7 to falsh stock t989 latest jb 4.1 ...stock rom works 100%....problem is with 4.2+ roms

Ok was just to be sure its not that.. did you try flashing with twrp??
Also what scheduler/governor are you using? I use sio/samsung (personnal choice) (stable, decent battery life, good performance) found out that some combinaisons crash the phone (reboot)

Just now installed twrp that u mentioned and took a backup....now I will try the cus rom process and tell u the result ...hoping this eleminates my problem...and one more thing...im just using stock rooted rom..had not done any changes with cpu governence...and have a decent battery..

Only problem is with KK and 4.3 Roms
I've changed the rrecovery to twrp latest and tried installing from CM9 worked ,
CM 10.1 even worked [4.2.2] :good: [camera crashes while using flash]
Tried 10.2 had bootloops.....whats wrong with 4.3+...help :crying:

Glad to hear that
Camera is known to crash when using the flash and battery is low.
About 10.2 idk .. maybe it has to do with CM itself (search in CM threads). Try some other roms/kernels combinaison. as long as you have a backup of a working setup you should be good. Personnaly i really liked hellkat w/diablo kernel (4.4.2) and Beanstalk w/wildkernel (4.4.4) but as they say , your mileage may vary.

K that's very helpful and ..tnx for ur sugession

Custom Kernel not Booting

I have a Galaxy note 4 SM- N910V, i just recently updated my bootloader to the CPD1. I rooted, installed TWRP, and CyanogenMod 13 beta. It works flawlessly, but ive always had an issue with bluetooth sound that was fixed when i installed a custom kernel on BPA1. Now that i am updated to CPD1, i installed CyanogenMod13, and the emotion kernel, But now my Phone wont boot pass the CyanogenMod logo at the beginning. I did wipe cache and dalvik after in installed the Kernel. I also tried a clean restore in odin, rooted, reflashed twrp. But this time i installed the Emotion Kernel first, THEN installed CyanogenMod/Gapps, and it booted perfectly BUT in settings my kernel doesnt say emotion it says "3.10.40-ga6f06c0 [email protected] #1" Any help is greatly apprecieted.
Thanks,
Deershoot3r

deershoot3r said:
I have a Galaxy note 4 SM- N910V, i just recently updated my bootloader to the CPD1. I rooted, installed TWRP, and CyanogenMod 13 beta. It works flawlessly, but ive always had an issue with bluetooth sound that was fixed when i installed a custom kernel on BPA1. Now that i am updated to CPD1, i installed CyanogenMod13, and the emotion kernel, But now my Phone wont boot pass the CyanogenMod logo at the beginning. I did wipe cache and dalvik after in installed the Kernel. I also tried a clean restore in odin, rooted, reflashed twrp. But this time i installed the Emotion Kernel first, THEN installed CyanogenMod/Gapps, and it booted perfectly BUT in settings my kernel doesnt say emotion it says "3.10.40-ga6f06c0 [email protected] #1" Any help is greatly apprecieted.
Thanks,
Deershoot3r
Click to expand...
Click to collapse
This Emotion kernel? That's a Lollipop kernel. You're supposedly on a Marshmallow unlocked bootloader. My guess is that it's incompatible.
@hsbadr's CM comes with his Multisystem kernel baked in. When you flashed his ROM you overwrote the Emotion kernel. For what it's worth there have been sporadic complaints about Bluetooth in the CM ROM.

Emotion does have a mm kernel and I also have had no luck using it.
I am running the emotion 6.0.1 rom on my verizon 910v and I just flashed the stock cdp1 kernel on top of the rom.... all is working great.

Check this out tho, after i had no luck with the emotion kernel, i reflashed the stock cdp1 kernel again just to get my phone to boot, and it wont boot with the stock kernel either, ive learned my lesson with making twrp backups haha saved my life from a fresh install