Develop Bugs

A boot loop in every custom ROM installed?

Hi, my Evo is a launch one (HW002). Ive been running Magnus ROM for the last month, but today I decided to give Virus's ROM a try, and after download and 3 wipes of the usual suspects (cache, dalvik, data) plus the Format All zip, I flashed my ROM but when I came back I was stuck on a boot loop. So I nand back to Magnus again, and then decide to flash Kings 2.3 Sense ROM, and also had a boot loop! This has never happened before, and I was able to nand back to Magnus..... is there something wrong with my phone, that is not letting me flash ANY new ROM at all???

Well I don't own eco but I think u should format data and stuff before flashing and go back to stock and start all over and also I would never try a rom with the name virus smh
Sent from my SGH-T959 using XDA Premium App

Droga said:
Hi, my Evo is a launch one (HW002). Ive been running Magnus ROM for the last month, but today I decided to give Virus's ROM a try, and after download and 3 wipes of the usual suspects (cache, dalvik, data) plus the Format All zip, I flashed my ROM but when I came back I was stuck on a boot loop. So I nand back to Magnus again, and then decide to flash Kings 2.3 Sense ROM, and also had a boot loop! This has never happened before, and I was able to nand back to Magnus..... is there something wrong with my phone, that is not letting me flash ANY new ROM at all???
Click to expand...
Click to collapse
What recovery are you using to flash the rom? Clockwork or Amon ra? What radios are you on? Which Virus rom were you trying to flash? I've never had trouble.trying.to boot any of his.roms, they are usually solid.
Sent from my PC36100 using XDA App

k2buckley said:
What recovery are you using to flash the rom? Clockwork or Amon ra? What radios are you on? Which Virus rom were you trying to flash? I've never had trouble.trying.to boot any of his.roms, they are usually solid.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Amons recovery, latest radio and newest Virus 2.3 ROM. Ive never had trouble flashing ANY ROM before, and all of a sudden my phone is acting up. At least it is letting nand back to my previous ROM.

Droga said:
Amons recovery, latest radio and newest Virus 2.3 ROM. Ive never had trouble flashing ANY ROM before, and all of a sudden my phone is acting up. At least it is letting nand back to my previous ROM.
Click to expand...
Click to collapse
Hmm, that's odd. Are you sure the files you're trying to flash aren't corrupted? You said you did a full wipe, including a format all, so an improper wipe is ruled out. I unfortunately don't have a lot to suggest. I think if that was happening to me, I would first try reflashing my recovery, and then try wiping and flashing again.
Sent from my PC36100 using XDA App

k2buckley said:
Hmm, that's odd. Are you sure the files you're trying to flash aren't corrupted? You said you did a full wipe, including a format all, so an improper wipe is ruled out. I unfortunately don't have a lot to suggest. I think if that was happening to me, I would first try reflashing my recovery, and then try wiping and flashing again.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Already tried that, no go.
I guess Im stuck with my ROM for the time being....

Droga said:
Already tried that, no go.
I guess Im stuck with my ROM for the time being....
Click to expand...
Click to collapse
I wish I had more to try suggesting for you. Its odd that both of the roms you tried flashing were sense based 2.3 roms. I wonder if you're phone doesn't like the kernel that comes cooked into those roms. I think virus's 2.3 rom uses the same kernel as the 2.3 king's rom. Perhaps after you flash the rom, you could power off the phone, take out the sd card, and try booting it without the sd card in it. I've heard of weird booting issues being caused by an issue with the sd card. It certainly couldn't hurt anything to try it, but I would think that if that was the issue, you'd have trouble booting any rom. I'd still try it though.

k2buckley said:
I wish I had more to try suggesting for you. Its odd that both of the roms you tried flashing were sense based 2.3 roms. I wonder if you're phone doesn't like the kernel that comes cooked into those roms. I think virus's 2.3 rom uses the same kernel as the 2.3 king's rom. Perhaps after you flash the rom, you could power off the phone, take out the sd card, and try booting it without the sd card in it. I've heard of weird booting issues being caused by an issue with the sd card. It certainly couldn't hurt anything to try it, but I would think that if that was the issue, you'd have trouble booting any rom. I'd still try it though.
Click to expand...
Click to collapse
If his phone doesn't like the stock kernel, I'd recommend flashing a custom kernel in the same session, after wiping the cache and dalvik after he flashes the rom.

teh roxxorz said:
If his phone doesn't like the stock kernel, I'd recommend flashing a custom kernel in the same session, after wiping the cache and dalvik after he flashes the rom.
Click to expand...
Click to collapse
Right, which is definitely what I'd normally suggest. However, since he's trying to use the new Sense 2.3 roms, there arent really any custom kernels for those roms yet. Some people have reported success with Netarchy's, but it breaks the camera app. Other people reported loops with netarchy. Basically, there arent any custom kernels for any 2.3 GB + sense roms yet, so his kernel switching is limited. He could try another one, and may have it work, as some other people had reported. But his camera won't work!

k2buckley said:
Righ, which is definitely what I'd normally suggest. However, since he's trying to use the new Sense 2.3 roms, there arent really any custom kernels for those roms yet. Some people have reported success with Netarchy's, but it breaks the camera app. Other people reported loops with netarchy. Basically, there arent any custom kernels for any 2.3 GB + sense roms yet, so his kernel switching is limited. He could try another one, and may have it work, as some other people had reported. But his camera won't work!
Click to expand...
Click to collapse
I had already tried another ROM ( Myn's Warm Z) just to see if it is the kernels and the Sense 2.3 combination, but that didnt give me any problems at all. So Im guessing it is the kernel included in those ROMS. I will try your suggestions, though, just to see if they actually make a difference. Thanks for the kind help.

k2buckley said:
Right, which is definitely what I'd normally suggest. However, since he's trying to use the new Sense 2.3 roms, there arent really any custom kernels for those roms yet. Some people have reported success with Netarchy's, but it breaks the camera app. Other people reported loops with netarchy. Basically, there arent any custom kernels for any 2.3 GB + sense roms yet, so his kernel switching is limited. He could try another one, and may have it work, as some other people had reported. But his camera won't work!
Click to expand...
Click to collapse
True...but from what I've heard [haven't flashed it] but some have reported success with stock kernel 15, and it not breaking anything, so he could try that...

teh roxxorz said:
True...but from what I've heard [haven't flashed it] but some have reported success with stock kernel 15, and it not breaking anything, so he could try that...
Click to expand...
Click to collapse
This is true.
Hey OP, you catching this? Lol. Try flashing the stock HTC 15 kernel right after you flash the rom, but before you boot. See if that makes any difference.

This is why teamwork wins.

teh roxxorz said:
True...but from what I've heard [haven't flashed it] but some have reported success with stock kernel 15, and it not breaking anything, so he could try that...
Click to expand...
Click to collapse
k2buckley said:
This is true.
Hey OP, you catching this? Lol. Try flashing the stock HTC 15 kernel right after you flash the rom, but before you boot. See if that makes any difference.
Click to expand...
Click to collapse
I will do this and come back with results in a while.

Muy Bien amigo.
I'll be floating around.

teh roxxorz said:
This is why teamwork wins.
Click to expand...
Click to collapse
Always true!
Hopefully the different kernel helps him out!

Tried stock kernel #15: no go.
Thanks for the help, though!

Droga said:
Tried stock kernel #15: no go.
Thanks for the help, though!
Click to expand...
Click to collapse
Damn. That sucks. I'm not sure what would be causing that. You wiped, you tried a different kernel, your radios and PRI are updated, you tried booting without the SD card in place. I'm not sure what'd send you to bootloops. Did you happen to try updating to the most recently leaked radio? The one that was in the dump from the leaked gingerbread rom? Although I doubt that'd make any difference, but you never know. I flashed it the other day, and it works just as good as all the other ones. I never really notice a major difference from changing radios. But the leaked one does work.

Droga said:
Tried stock kernel #15: no go.
Thanks for the help, though!
Click to expand...
Click to collapse
Sorry man.

teh roxxorz said:
Sorry man.
Click to expand...
Click to collapse
No worries. I was able to install a new custom ROM just now (Kings R3) and it installed just fine. I will try again to install the other ROMS just to see if it will work today.

Phone will not boot any kernel. WHY?

First a little background. I am not new to the android world whatsoever. I don't post much but have been lurking for years. I had a Verizon GS3 and just recently switched to T-Mobile a few days ago and obviously bought a T-Mobile GS3. My vzw phone had no problems. But for some reason my T-Mobile phone will not boot any kernel I try to flash. Roms flash fine but when I flash a kernel everything goes fine in recovery but my phone won't boot past the splash and I end up having to restore a backup. I know I'm flashing the right kernels. I am on touchwiz based ROMs and haven't tried any aosp Rom because for the first time ever I actually prefer an OEM skin to aosp. So basically am I missing something obvious. Anyone else having thus problem. On Verizon I had to root and unlock the bootlosder. From what I understand tmobiles bootliader was not locked down and all I had to do was root. Like I said. I've tried every touch wiz Rom and every touch wiz kernel with each Rom and none will boot past the splash screen. I always wipe dalvik and cache but even tried wiping data every time too and keep getting the same result. Any input would be appreciated. . Thanks in advance.
Sent from my SGH-T999 using xda premium

Shouldn't need to do any wiping of any kind. I only use AOSP/AOKP, though. May I ask why you even bother with custom kernels? They honestly seem like a waste of time to me.

Im just flash happy. Like to try them out. I've been on Verizon for many Years and am used to the developers over there. I'm still getting used to the devs over here. Don't know any of there work. I'm sure its all good though. Been using imoseyons lean kernel since the thunderbolt back in the day and have stuck with them. Just my personal preference. I'd like to try some of tmobolrs kernel devs work but like I said I can't get a single one to boot.
Sent from my SGH-T999 using xda premium

What kernels have you tried to flash? There are a couple that have ICS builds. Also, what version of CWM are you using?

I've tried all the tw kernels. Every single one with 2 different ICS tw ROMs. I'm not using the leaked jb tw. I'm stickung with the more stable ICS ROMs for now. I just don't understand. I've tried every one. I've been flashing a long time and don't get it. Im kinda new to Samsung though. First Samsung was the galaxy nexus. Didn't ever use Odin with it. Does anyone flash kernels with Odin. Maybe I should try that. And to answer your question I've tried twrp and the latest version of cwm from rom manager. And of course I'm using the ICS TW version of the kernels im trying.
Sent from my SGH-T999 using xda premium

It could just be your phone doesn't like them. There is another guy on CM10 and AOKP that can't get custom kernels to boot either.
Sent from my Nexus 7 using Tapatalk 2

The kernel source code was never released for any build from UVALH2 and beyond. So most of our kernels will only work with UVALEM and UVALG1 builds.
We got kind of lucky I think and ktoonsez att kernel was brought over and works. I think there's one or two others that work now too.
As far as described here go I think we've got some of the best! For an outstanding rom you should try FreeGS3. It works with most of the kernels and is an awesome stable rom. If you want a later build try wildcards XquiziT v70 based on UVALH2. Use ktoonsez kernel with it.
And just to note, the stock kernel is surprisingly good. So give it a fair shot as well. Though I can definitely see some potential advantages of custom ones as well.
Sent from my SGH-T999 using xda app-developers app

Thanks for all the info. But now I can't even get any other ROMs to boot. I don't get it. I keep having to restore my Xquizit v20 back up. Its driving me nuts
Sent from my SGH-T999 using xda premium

jasonpantuliano said:
Thanks for all the info. But now I can't even get any other ROMs to boot. I don't get it. I keep having to restore my Xquizit v20 back up. Its driving me nuts
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Have you done full Wiping?
Wipe Data/Factory Settings
Wipe cache and dalvik
Flash Rom
Fix Permission
Reboot and don't touch it for 10 minutes
Reboot.
Wipe cache and dalvik
Flash Kernel (Must be compatible with ROM)
Fix Permission
Reboot and don't touch it for 10 minutes
Reboot.
See if this will work. Sometimes you have to let it breathe so it can adjust itself.

Have you tried uding odin to flash MrRobinsons root66 UVALH2? This will take you to fresh full stock plus root. Then try roms again.
Sent from my SGH-T999 using xda app-developers app

Whatever you do................
Be sure to double check before you flash that kernel. Had my first SGS3 for 12 days before hard brick set in. Terrible disease it is.......! I had to adopt a replacement shortly after to cope with the pain of the loss. Back on my feet again now though and soarin' higher than giraffe vagina on the things I learned in my days off for mourning. I can tell ya I've personally flashed the lean kernel and kt-747 with no issues. My problems were with siya mainly.

Guys, I have a serious problem.
It's similar to the one of the thread-opener.
The diference is that I cant get ANY ROM to boot, WITH the stock kernel.
And i do like the guide says: wipe/factory reset, wipe chache, wipe dalvik cache and then flash the ROM.
Everything works fine til the ROM finished flasing and runs a reboot.
My S3 shuts down screen, then turns screen on with the "Samsung Galaxy SIII-GT-I9300" and then thats it!
All i can do is to go in download mode or recovery mode. I can also flash CWM and so on, but after flashing ROMs it won't boot!
Is it possible that i broke the device by formating internal sd-card with the stock recovery tool?
Did it, after I tried to install Wickedv6 ROM and after both times when it rebooted it just reinstalled stock ROM. So i thought, ok delete the internal sd-card, so no stock ROM on it any more.
Also tried this ROM: http://forum.xda-developers.com/showthread.php?t=1875923
Same problem.
Also tried to fix the problem by rooting and then flashing ROM. No help.
Please help guys!
Best regards

ke-ironman said:
Guys, I have a serious problem.
It's similar to the one of the thread-opener.
The diference is that I cant get ANY ROM to boot, WITH the stock kernel.
And i do like the guide says: wipe/factory reset, wipe chache, wipe dalvik cache and then flash the ROM.
Everything works fine til the ROM finished flasing and runs a reboot.
My S3 shuts down screen, then turns screen on with the "Samsung Galaxy SIII-GT-I9300" and then thats it!
All i can do is to go in download mode or recovery mode. I can also flash CWM and so on, but after flashing ROMs it won't boot!
Is it possible that i broke the device by formating internal sd-card with the stock recovery tool?
Did it, after I tried to install Wickedv6 ROM and after both times when it rebooted it just reinstalled stock ROM. So i thought, ok delete the internal sd-card, so no stock ROM on it any more.
Also tried this ROM: http://forum.xda-developers.com/showthread.php?t=1875923
Same problem.
Also tried to fix the problem by rooting and then flashing ROM. No help.
Please help guys!
Best regards
Click to expand...
Click to collapse
This isn't the I9300 forum, but if you flashed a T999 rom, you bricked your phone.

Aerowinder said:
This isn't the I9300 forum, but if you flashed a T999 rom, you bricked your phone.
Click to expand...
Click to collapse
Wow, you scared the **** out of me
But i just tried to flash stock ROM: http://forum.xda-developers.com/showthread.php?t=1646610
It worked out!
What is the right forum for my GT-I9300 to post then?
And why isn't any other ROM working?

The forum you got that stock rom from is the international one. This is the US Tmobile T999 forum. The two phones are NOT compatible.
Only flash, well...anything, from that forum. Our roms will brick yours and vice versa.
Sent from my SGH-T999 using xda app-developers app

Why is this happening to my Gnexus?

Hey fellow gnex community! I recently left stock rom due to freezes and random reboots. I've tried out various rom and kernel combinations this week such as xylon/AK, Purity/AK, AOKP/franco/lean, CM10.1/trinity/franco, Rasbean/trinity, PA/lean/franco/trinity/AK and Xenon.
The problem is they all freeze and reboot constantly after 2 minutes of use. I never changed the kernel settings and this is only happening on 4.2.1 roms. My favorite rom/kernel combo would be purity/AK, Xylon/AK but they freeze, wifi disconnects and never connects back and reboots constantly.
So the question is why is this happening to my phone recently and are there specific kernel settings that will stabilize the roms or is it just my phone?
Any help would be great,
thanks.

I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD

Lord Yurij said:
I haven't had that problem before, and I have flashed several roms (though not a custom kernel in a while)
Faulty hardware perhaps?
Sent from my Transformer Pad TF300T using Tapatalk HD
Click to expand...
Click to collapse
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.

4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway

nav200 said:
but this never happened on 4.1, 4.0.4 etc. That's what's worrying me.
Click to expand...
Click to collapse
I would do a full wipe and fastboot flash the stock images from Google to see if this helps. Mind you, your internal memory will be wiped so back up all of your photos etc..

crixley said:
4.2.1 isn't exactly highly regarded for its stability....
I reccomend going back to a good 4.1.2 rom. You aret missing anything anyway
Click to expand...
Click to collapse
but I heard people change the kernel settings and the phone will become smoother/stable? I really love some of the features from 4.2.1 that's the reason I'm a bit hesitant to go back to 4.1.2

Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app

plznote said:
Try a full wipe, and fast boot a stock image on and proceed from there.
Sent from my A100 using xda app-developers app
Click to expand...
Click to collapse
I've done that twice already and usually wipe after it freezes but then still happens

Are you sure you know how to flash? Not trying to offend but it saves a lot of time if your a noob.
I currently wipe dalvik cache 3x, cache 3x, and factory reset 3x in twrp. I read somewhere its safer to wipe like this or use super wipe scripts or w.e
I am running the latest rasbeanjelly with latest rasbean gapps and latest lean kernel. I haven't had any resets and haven't tweak anything. May I also add that when I do get errors with roms normally when I flash extra mods I always go back to recovery and hit fix permissions. Idk why but it does solve some issues.
Good luck
Sent from a slice of Galaxy Nexus with some Rasbean Jelly!

lol. Ya I've been flashing roms for like a year and it's only recently these issues are popping up. I do pretty much what everyone does - wipe data, wipe cache, wipe dalvik, flash rom, flash gapps and flash kernel. I never use mods so nothing to worry about there.

Try flashing rom and gapps only without a custom kernel.
If you've fully formatted your drive, have updated recovery, and are positive you have good downloads then your problem is most likely hardware related

Try the kernel cleaner script before flashing/changing between kernels.
It's a cwm flashable .zip.

Alright will do as suggested

How about fastboot flashing the stock rom's .img-es? (Galaxy Nexus ToolKit is the easiest way to do it)

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Alright so it seems like the rom HumberOS with built in kernel did the job. Been using the phone for about 4 hours non stop and no freezes or reboots so far. Finally something stable for my phone! Thanks for the help everyone!

update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.

nav200 said:
update: After a day without any hiccups on the humber os rom, my phone finally froze and rebooted. Since I was using cwm, I decided to see if twrp would solve the problem. I restored my phone to stock and started from scratch by installing twrp. Then I decided to give PA a try and to my surprise no reboots or freezes at all but will have to wait a day to confirm.
Click to expand...
Click to collapse
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..

Sdobron said:
You did restore the factory images by running the update script included in the package right? This will make sure all data is up to date.. Fastboot erase all partitions first as well..
Click to expand...
Click to collapse
yup did all that and everything seems to be going fine so far

So... what would be causing the problem you think?
You installed TWRP and PA both at the same as I can read in the previous posts?
So that way we will never know if it's a recovery problem, or ROM problem...
Well, as long as your device doesn't freeze and/or reboot we should be happy I guess.

[Q] Quantum Rom issues

Well, I don't know if this is how I'm supposed to go about doing this, but I've been having issues recently with Quantum rom, and was planning on posting them in the actual Quantum thread, but I need 10 posts to do that because 10 posts mean something important.
Anyways, Ive been fine previously just doing
1. Wipe Dalvik, cache, and system,
2. flashing rom and gapps
3. the wipe option you get after you flash (TWRP)
Ive been doing that since i started basically, until 1.9. Anything after 1.9, it either constantly crashes, has processes constantly stopping, or on one of the versions (2.1 i think) the screen would constantly flicker (which someone else mentioned happening in the thread). So i figured I should try a clean flash, so I try wiping everything and flashing, and doing the default factory reset option and flashing, neither of which helped. In fact, after doing the clean flash it made 1.9 stop working too, so I had to restore my 1.9 backup to get it working again.
Anywho, if anyone has any advice that could help me get the newer versions working that would be great, Thanks!
EDIT: I might try flashing a different rom, to see if the issues persist elsewhere, but firstly Id like to stay on Quantum, and secondly, iirc I tried one a different rom when 4.3 first started showing up in roms, and I kept having problems, to which I just went back to Quantum.

It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk

codemonkey98 said:
It sounds to me you have a bad download. Have you tried re-downloading the ROM? I run the Quantum ROM and I have had no issues whatsoever.
I'm also looking forward to your reply about flashing another ROM.
Sent from my SAMSUNG-SGH-I497 using Tapatalk
Click to expand...
Click to collapse
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow

DanCardin said:
Well, I've tried flashing every version including and after 2.0, up to the current version, and have the same problems for each one. So i somewhat doubt that that's the problem. Ill probably try to flash somethign else some time tomorrow
Click to expand...
Click to collapse
Could be your recovery too. I believe the Quantum ROM developer recommends CWM than TWRP.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

If you do decide to change to CWM, make sure you revert to your TouchWiz backup first since TWRP and CWM backups aren't compatible. My best recommendation is to re-download the newest version (2.35 as of 11/7/13), and wipe data/factory reset, wipe /cache, wipe system, wipe dalvik cache, then install ROM and Gapps, wipe cache and dalvik again, and reboot.

iirc, i noticed a fair enough number of people on TWRP that I would prefer to stay on it (since it *should* work). I did, however just update it, tried again. For 2.31, i just get constant for closes on phone and SystemUI, and others iirc. Im trying carbonRom right now, and its working perfectly fine.
EDIT: I did get one SystemUI force close, on it, but its literally constant on quantum sadly.

also tried a couple random other roms, all work, but no Quantum rom will work after 1.9. I also tried just flashing it and not gapps, and i end up with the same thing. Now its just constant force closes though. I don't think i remember seeing any flickery screens like i was getting around 2.1X i think it was.

What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app

android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think that the leaked 4.3 bootloader (whatever end code they gave it) isn't necessary yet, since it hasn't been officially released by AT&T. I'm personally holding off on flashing any 4.4 rom until they're a bit more mature and don't have as many hiccups (although pwncake's work is superb). The UV depends on your device and how it handles it, usually, mine needs +25 than stock but it doesn't seem to shorten battery life. All throughout 4.3, it was best to keep MP-Decision off since he built one into the rom. In the case of 4.4, IIRC from Quantum v3 beta3 and forward, he removed his own MP- Decision, so you could keep it switched on.

android_geek_0507 said:
What bootloader and firmware are you using with the later quantum ROMs.... I believe that the more recent ones need the dmg2 or emj2 boot and firmware to run properly.... Also what were your settings in trickster did you disable mp-dec and UV... Were you OC using stock quantum kernel etc.
Sent from my SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.

Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)

DanCardin said:
I just flash the ROM and boot. If I should be flashing a seperate firmware slash bootloader, I'm not (and never have to my knowledge). I couldnt have gotten to the trickster settings if i wanted to due to the constant force closes.
Click to expand...
Click to collapse
Can't run Quantum either. Same boat. I think it's an issue with the Core kernel and Rev0 processors.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things

DanCardin said:
I tried flashing the new beta 8 of v3, and it worked with the odd restart and FC on the side. But the restarts were starting to get a bit annoying so I tried reflashing, and now I just get infinite boot animations no matter what I do. And if I try to restore my nandroid backup, there's this flash every 2 or 3 seconds around the boot animation. Sigh
EDIT: actually, completely reflashing works, but still ends up with the random reboots when doing random things
Click to expand...
Click to collapse
I get the same thing...

supahdaniel said:
I get the same thing...
Click to expand...
Click to collapse
sorry to hear of your problems. it is not the rom. enough folks are running it and I have had flawless installs. Read the OP and follow the directions, it works.
there is a new TWRP (from their site) that I downloaded as a .tar file and flashed with odin. flashes 4.4 roms now so you might try that rout.
my suggestion, in its limited knowledge is this:
put the rom, superuser, and the gapps on your SD card.
Reboot into the new TWRP and format the system- your phone is now blank.
install rom zip
install superuser zip
reboot.
first boot may take a bit, but not forever. Set up CM stuff and go from there
---------- Post added at 12:29 PM ---------- Previous post was at 12:17 PM ----------
Demminex said:
Would anyone know why when I enable ART mode on Quantum 4.4 Beta3 Rom, my phone continually has pop up messages with unexpected errors? -Such as calendar storage issues or the google keyboard(This should probably be in the ROM section but I can't write there.)
Click to expand...
Click to collapse
search the quantum thread about google settings. you have to turn on google now and disable notifications. also, I've been using the swift keyboard and don't have to deal with the google or android keyboard. that seems to have helped.
enable art after loading apps and be prepared for a wait for android to upgrade.

[Q] Bootloop - Only boots right after cache/dalvik wipe - Kindle Fire CM10.2 20131206

If I boot into recovery, wipe cache and dalvik (I fix permissions too, although this probably isn't necessary), then it boots right up like nothing is wrong with no fanfare.
If I'm lucky, this will even persist for an additional reboot. Otherwise on subsequent reboots it just bootloops forever until I go back to recovery and wipe cache/dalvik again, and then it boots right up again. Once into the ROM, everything runs fine, no issues at all.
I've tried rolling back a nightly or two but it doesn't seem to make a difference. Was there some major change in the last few weeks that I missed? How far do I need to roll back to get this to work?
It's my gf's tablet so I don't really want to wipe data if I can avoid it. Was even thinking of dirty flashing up to CM11.
Any insight is appreciated.

With my phone this problem ended up being using the wrong baseband version for the ROM/kernel that I was using. I was able to fix it by resetting it back to stock using ODIN (tool which can be used to recover Samsung devices) but from the sounds of it you have no such luxury.
Do you have any backups of when everything worked? If not try to find a way to get back to stock however you can. Aside from that make sure that you are using the correct ROM for your hardware.
Good luck and keep us updated.

czahrien said:
With my phone this problem ended up being using the wrong baseband version for the ROM/kernel that I was using. I was able to fix it by resetting it back to stock using ODIN (tool which can be used to recover Samsung devices) but from the sounds of it you have no such luxury.
Do you have any backups of when everything worked? If not try to find a way to get back to stock however you can. Aside from that make sure that you are using the correct ROM for your hardware.
Good luck and keep us updated.
Click to expand...
Click to collapse
The kindle is wifi only, so I don't think there are any baseband issues. Will update when/if I fix it.
Restoring to stock is a good idea. It's been over a year since this thing was stock, so it's quite possible we missed a firmware update or something.
Sent from my Nexus 5 using XDA Premium 4 mobile app

Mine does this after I installed the new sgt7 4.4.2 rom. Did you end up fixing yours?

whatever100 said:
Mine does this after I installed the new sgt7 4.4.2 rom. Did you end up fixing yours?
Click to expand...
Click to collapse
Not yet, but I think it worked fine on cm10.2 for awhile.
Sent from my Nexus 5 using XDA Premium 4 mobile app

UPDATE - I dirty flashed cm11 and gapps as if I were updating any other nightly, and the issue appears to be gone. So freaking annoying, lol.