I'm not sure if its just my phone, had this problem for a while now, but when it occurs, i usually just flash another rom, but basically, when it comes to my rom and flashing a rom that comes with a custom kernel, its a no go what so ever, its force close central, and boot loops and all that, no idea why, but my phone just simply doesn't play nice with any custom kernels at all, started with Jellybomb, use to love it, worked perfect, no problems, then when it updated to i believe 10, 11, not precise on what version, and he used a custom kernel, then bam, tried everything, no luck, and couldnt use that rom with my phone anymore, or any other rom that comes with custom kernels, and still cant, and i guess its time to mention it to verify if this happens to anyone else.
Parkourkid93 said:
I'm not sure if its just my phone, had this problem for a while now, but when it occurs, i usually just flash another rom, but basically, when it comes to my rom and flashing a rom that comes with a custom kernel, its a no go what so ever, its force close central, and boot loops and all that, no idea why, but my phone just simply doesn't play nice with any custom kernels at all, started with Jellybomb, use to love it, worked perfect, no problems, then when it updated to i believe 10, 11, not precise on what version, and he used a custom kernel, then bam, tried everything, no luck, and couldnt use that rom with my phone anymore, or any other rom that comes with custom kernels, and still cant, and i guess its time to mention it to verify if this happens to anyone else.
Click to expand...
Click to collapse
Try kernel cleaner
Sent from my SPH-L710 using xda premium
xblackvalorx said:
Try kernel cleaner
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
where would i find that?, and what specifically does it do?
i dont want to hijack a thread but also dont want to start a new one since there is this one. has any cspire s3 users flashed a different kernel and had success with it. im on the latest pacman rom and want a diff kernel. ive flashed one before and got a softbrick. just curious.
@ IonIcone, Keep the thread to the user that's asking the question.
Search the whole forum first / search it online, if it's a no go on both parts, then start a question
thread of your owns.
@ ParkourKid93
KernelCleaner can be downloaded here.
http://forum.xda-developers.com/attachment.php?attachmentid=1319515&d=1347395869
scripted by mattrb, you can thank him for that file.
When using kernels make sure it's for the right version
JB or AOSP. and also make sure its for the right version
4.1.x or 4.2.x
Usually when you're also installing a rom with a dif kernel ( and you CAME from a rom with STOCK kernel )
you'll need to wipe cache and dalvik cache, and re-set permissions via Custom Recovery.
If those don't work, search the original ROM thread for a [Q] of the same as yours and see if there was a fix / reply for that.
If all else fails, contact the dev of the rom with your specific issue.
I've been switching between kernels and JB versions and i've never ran into this issue. Anthrax, K747, Agat's and Stock Optimized.
Have you tried odin flash restore to stock LJ7 and re-installing the rom as well?
ionicone said:
i dont want to hijack a thread but also dont want to start a new one since there is this one. has any cspire s3 users flashed a different kernel and had success with it. im on the latest pacman rom and want a diff kernel. ive flashed one before and got a softbrick. just curious.
Click to expand...
Click to collapse
No problem bro, does sound like you flashed a wrong kernel for your phone, but like spark said, look around, their is a lot of topics on soft bricked phone, you will deffinatly find something on it
Sent from my SPH-L710 using xda premium
Spark91 said:
@ IonIcone, Keep the thread to the user that's asking the question.
Search the whole forum first / search it online, if it's a no go on both parts, then start a question
thread of your owns.
@ ParkourKid93
KernelCleaner can be downloaded here.
http://forum.xda-developers.com/attachment.php?attachmentid=1319515&d=1347395869
scripted by mattrb, you can thank him for that file.
When using kernels make sure it's for the right version
JB or AOSP. and also make sure its for the right version
4.1.x or 4.2.x
Usually when you're also installing a rom with a dif kernel ( and you CAME from a rom with STOCK kernel )
you'll need to wipe cache and dalvik cache, and re-set permissions via Custom Recovery.
If those don't work, search the original ROM thread for a [Q] of the same as yours and see if there was a fix / reply for that.
If all else fails, contact the dev of the rom with your specific issue.
I've been switching between kernels and JB versions and i've never ran into this issue. Anthrax, K747, Agat's and Stock Optimized.
Have you tried odin flash restore to stock LJ7 and re-installing the rom as well?
Click to expand...
Click to collapse
I actually tried that same exact kernel cleaner this morning, I searched and found it, had no luck with it though, and for the 'choosing the right kernel', it comes built in with the ROM, its the jelly bomb 14 ROM I'm referring to, also did wipe both caches and fixed permission, still no luck, I want to believe its my phone itself though, because I know it wouldn't be the ROM, I deff trust the ROM and developer obviously, and used his work before, but that's when he didn't use a custom kernel, but when he included the custom kernel built in, I believe jellybomb 10, or 11, then it was the last time I could of flashed any of his Roms, I do remember having similar problems with other Roms that uses custom kernels also, the only kernel my phone plays great with, is the stock optimized, and the cyanogenmon kernels, but ktoons and agats, and even anthrax (when I was using freeza fregs3, just went no go on my device
Sent from my SPH-L710 using xda premium
Related
Can I use baked snacks kernel on a different Rom? I'm looking to improve battery life
I don't see why not. Nand backup and go for it.
EVOme said:
I don't see why not. Nand backup and go for it.
Click to expand...
Click to collapse
Is that what makes it have good battery?
Sent from my PC36100 using XDA App
Rocklee99 said:
Is that what makes it have good battery?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
what? doing the nand backup? that's just in case the kernel doesn't work you can restore to the previous condition your phone was in (so do it before you flash baked's kernel)
I'm not sure if his kernels will work on other roms though, I think I tried once
I've used it on my ROM what ROM are you using that might help.
mistersquirrle said:
what? doing the nand backup? that's just in case the kernel doesn't work you can restore to the previous condition your phone was in (so do it before you flash baked's kernel)
I'm not sure if his kernels will work on other roms though, I think I tried once
Click to expand...
Click to collapse
No I meant is the kernel what gives better battery, BTW I'm using ava froyo Rom v8
Sent from my PC36100 using XDA App
Rocklee99 said:
No I meant is the kernel what gives better battery, BTW I'm using ava froyo Rom v8
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes the kernel can help with battery life. You should be ok with flashing a different kernel and that ROM but as posted do a NAND backup before flashing the kernel.
Does anyone know how good the battery is for baked snacks kernel and does anyone know where I can find his kernel #6 ?
Sent from my PC36100 using XDA App
Rocklee99 said:
Does anyone know how good the battery is for baked snacks kernel and does anyone know where I can find his kernel #6 ?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
#6 has never been available for download. I used BS 1.7 on NA 4.19 and my battery was day and a half if not better with average use...seriously. I was amazed. I tried all the baked kernels and nothing worked like that.
Now I am on BS 1.8 using the same kernel and not getting near the same batt life.
EVOme said:
#6 has never been available for download. I used BS 1.7 on NA 4.19 and my battery was day and a half if not better with average use...seriously. I was amazed. I tried all the baked kernels and nothing worked like that.
Now I am on BS 1.8 using the same kernel and not getting near the same batt life.
Click to expand...
Click to collapse
NA as in netarchy?
Sent from my PC36100 using XDA App
Baked Snack
I have no clue how you guys are doing it, but I have the 1.7 version with kernel 6.
I took it off the charger this morning (after a full charge), it is now almost dead, with very little use.
How do you guys do it? Your not shopping the images are you?
This is a newb question I know, I have searched all over the forums. i have the stock rom and am not interested in any of the roms since most of them seem to not have 4g working or some other things( cant wait until they do!). My question is how do I flash just the kernel? i have never flashed anything before and I just backed up everything with rom manager. thanks!!!
mcskibadee1 said:
This is a newb question I know, I have searched all over the forums. i have the stock rom and am not interested in any of the roms since most of them seem to not have 4g working or some other things( cant wait until they do!). My question is how do I flash just the kernel? i have never flashed anything before and I just backed up everything with rom manager. thanks!!!
Click to expand...
Click to collapse
Wipe cache, wipe dalvic, flash like you would a Rom. Don't forget to nand first.
Sent from my blah blah blah blah
Edit - I'm assuming there's a specific kernel you have that you want to flash, and you didn't mean how to extract the kernel from a full Rom - also just noticed that you said you already backed up with rom manager. You may want to consider backing up manually through recovery or using amonra instead - nobody seems to know what exactly rom manager wipes when you tell it to wipe.
mcskibadee1 said:
This is a newb question I know, I have searched all over the forums. i have the stock rom and am not interested in any of the roms since most of them seem to not have 4g working or some other things( cant wait until they do!). My question is how do I flash just the kernel? i have never flashed anything before and I just backed up everything with rom manager. thanks!!!
Click to expand...
Click to collapse
i think you're misinformed (or haven't searched hard enough) - most, if not all, sense based ROMs have everything working and some (i.e. wireless/usb tether, performance/efficiency tweaks, etc.). it's the cm/aosp roms that don't have everything working (yet).
flashing kernels is similar to flashing roms. there is a plethora of threads on the topic. read some of the stickies and many of your questions will be answered to get you started with flashing roms/kernels.
edit: sorry i never know about this is paid version i tooked from his old xda thread, BTW thanks for let me know about that
quocamole said:
i think you're misinformed (or haven't searched hard enough) - most, if not all, sense based ROMs have everything working and some (i.e. wireless/usb tether, performance/efficiency tweaks, etc.). it's the cm/aosp roms that don't have everything working (yet).
flashing kernels is similar to flashing roms. there is a plethora of threads on the topic. read some of the stickies and many of your questions will be answered to get you started with flashing roms/kernels.
Click to expand...
Click to collapse
I have been on this forum for weeks trying to decipher all the lingo. I have not seen any Evo roms that have the 4g working, If i did I would have just used one of those.Trust me, i have searched all over this forum and others before bothering or asking stupid questions. Maybe I am searching the wrong stuff, I will search for sense based roms, thank you.
Also, I have never flashed anything before. Still trying to figure that one out. Thanks for the info guys!
mcskibadee1 said:
I have been on this forum for weeks trying to decipher all the lingo. I have not seen any Evo roms that have the 4g working, If i did I would have just used one of those.Trust me, i have searched all over this forum and others before bothering or asking stupid questions. Maybe I am searching the wrong stuff, I will search for sense based roms, thank you.
Also, I have never flashed anything before. Still trying to figure that one out. Thanks for the info guys!
Click to expand...
Click to collapse
here you go:
http://forum.xda-developers.com/forumdisplay.php?f=653
all roms are there. aosp roms are usually the roms where everything is not working.
general steps to flashing (but always read the post from the developer for any special instructions):
1. download file to sd card
2a. get into recovery (either via quickboot app or via powering down then holding volume down button while powering up)
2b. navigating in recovery - volume keys to change selection, power button to select
3. nand backup
4. wipe data, cache and dalvik (only wipe cache and dalvik if you're flashing a kernel)
5. flash the rom/kernel you downloaded
6. reboot
7. drink beer
if something goes wrong, get back into recovery and restore your nand backup.
hope this gets you started.... but read, read, read.
good luck.
sorry OP - back on topic. did you wipe cache and dalvik before flashing the kernel? what's your up time and awake time (found in settings>about phone>battery). do you have any monitoring apps installed (i.e. system panel, android system info? you may have rogue app.
juancaperez2000 said:
here is the baked snak kernel 6 if you want it
Click to expand...
Click to collapse
No offense but this is why Hero quit providing stuff at xda...Thanks though
juancaperez2000 said:
here is the baked snak kernel 6 if you want it
Click to expand...
Click to collapse
good on you removing the link
Thank you quocamole, that helps.
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
So I know this will brand and certify me a n00b, but I cannot for the life of me figure how to flash kernels. I am coming from an OG EVO where I could flash from the recovery no problem, but that's not working for me in either TWRP or CWM. Do I have to flash with ODIN on a desktop each time?
Sent from my SPH-L710 using xda app-developers app
Kernels are flashed through recovery cwm/twp....as for not working, would need more info.
I flash. Kernels, anything other than ROMs and it causes a bootloop. Tried CWM and TWRP. The last thing I tried was the mod for having a GNEX navigation bar and had the same result.
We still need more info. You haven't said which ROM/kernel combo you're trying to flash. Maybe they are incompatible.
More info, please; as much as you can provide. That's the only way people can help.
Sorry about that. I have deleted a lot of files so I don't know. Do you know of any AOSP/AOKP combinations that work?
If you want to use CM10, AOKP, MIUI, or some other AOSP-based ROM, your only choices right now are the stock kernel or Ktoonsez's KT-747 kernel. The stock kernel gets flashed with the ROM and doesn't require extra work. The KT-747 kernel is in the Original Development section.
I tried the KT-747 on a AOKP nightly. It rebooted but the screen remained blank.
jjchdc said:
I tried the KT-747 on a AOKP nightly. It rebooted but the screen remained blank.
Click to expand...
Click to collapse
Sometimes the newest kernel isn't always compatible with the newest AOKP. Double check the dates of each. Also, there is both an AOSP and a Touchwiz version. Double check out that you're using the AOSP version.
Hey guys, so I've experienced my sensors getting borked when I flash AOSP based ROMS like CM10, Paranoid Android, and Jellybeer..
So I had to stay with touchwiz for awhile, until I found a temporary fix.
Oh and I am only sharing what I did, so everything that you do following what I did, is all on you.. I have no responsibility for anything that goes wrong with your phone.
**Use Triangle Away as needed**
Basically what I did was that I flashed the Peresus Kernel.
Now Peresus Kernel was only made for touchwiz based ROMs, so...
Edited 1/13/2013
1) Flash a Touchwiz based custom ROM and then flash the Peresus Kernel
2) Boot into the ROM
3) ** Edit ** Without setting up the ROM (by this I mean don't add gmail account.. etc), make sure your sensors are working
4) Reboot into Recovery
4) Full Wipe (Cache, Dalvik, Factory, Systems)
5) Flash AOSP based ROM
You should have your sensors back!!
Thanks appreciated if I've helped! :good:
Worked for me! Now if I could only get the Bluetooth working, then JellyBeer would be perfect!
EDITED
Spoke too soon, my phone got stuck on the Note II bootup screen...had to reflash CleanROM to be able to fully boot up, damn...
jeck77 said:
Worked for me! Now if I could only get the Bluetooth working, then JellyBeer would be perfect!
EDITED
Spoke too soon, my phone got stuck on the Note II bootup screen...had to reflash CleanROM to be able to fully boot up, damn...
Click to expand...
Click to collapse
Follow this:
Wipe everything...
Install aosp ROM
Boot
No cencors?
Boot recovery
FOLLOW CLOSE!
JUST install a TOUCHWIZ kernel... NO WIPING OF ANY SORT!!!
Reboot till you see a black screen......
Pull battery...
INSTALL AOSK ROM....NO WIPING ANYTHING!!!!
REBOOT AND ENJOY!
This is a 100% working fix. No if ands or buts. So enjoy
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
CLEAN ROM is the culprit, not aosp. After installing clean rom your sensors get messed up. After clean rom you can only run touchwiz, as aosp won't work. If you go from touchwiz to aosp everything is just fine.
This is the second time something insane has happend for me with clean rom that not even a NANDROID could fix. I don't know if its aroma or clean rom but I'm staying away from both for a while.
seh6183 said:
CLEAN ROM is the culprit, not aosp. After installing clean rom your sensors get messed up. After clean rom you can only run touchwiz, as aosp won't work. If you go from touchwiz to aosp everything is just fine.
This is the second time something insane has happend for me with clean rom that not even a NANDROID could fix. I don't know if its aroma or clean rom but I'm staying away from both for a while.
Click to expand...
Click to collapse
source?
hapticxchaos said:
source?
Click to expand...
Click to collapse
Myself. I tested for 2 hours yesterday with 2 bone stock notes. After clean ROM auto rotation is broken for aosp. There is no getting it back until using the fix above.
Zero issue for me on cleanrom
Sent from my SAMSUNG-SGH-I317 using xda premium
seh6183 said:
CLEAN ROM is the culprit, not aosp. After installing clean rom your sensors get messed up. After clean rom you can only run touchwiz, as aosp won't work. If you go from touchwiz to aosp everything is just fine.
This is the second time something insane has happend for me with clean rom that not even a NANDROID could fix. I don't know if its aroma or clean rom but I'm staying away from both for a while.
Click to expand...
Click to collapse
I don't know about that. My sensors were messed up when I installed JellyBeer, and that was the first ROM I installed. I hadn't even downloaded CleanROM at the time.
---------- Post added at 05:09 AM ---------- Previous post was at 04:44 AM ----------
Smittyzz said:
Follow this:
Wipe everything...
Install aosp ROM
Boot
No cencors?
Boot recovery
FOLLOW CLOSE!
JUST install a TOUCHWIZ kernel... NO WIPING OF ANY SORT!!!
Reboot till you see a black screen......
Pull battery...
INSTALL AOSK ROM....NO WIPING ANYTHING!!!!
REBOOT AND ENJOY!
This is a 100% working fix. No if ands or buts. So enjoy
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
So you're saying to install the AOSP ROM twice?
jeck77 said:
I don't know about that. My sensors were messed up when I installed JellyBeer, and that was the first ROM I installed. I hadn't even downloaded CleanROM at the time.
---------- Post added at 05:09 AM ---------- Previous post was at 04:44 AM ----------
So you're saying to install the AOSP ROM twice?
Click to expand...
Click to collapse
Its not clean ROM I don't think. I think its some phones. And yes install the ROM twice.
Do this:
FAC/sys wipe
Install jelly beer
Boot to no censors
Reboot to recover
Install a touch wiz kernel and reboot till you get a black screen.
Pull battery
Reinstall jelly beer
If you follow my steps exact they will work perfect
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
I posted something like this a while back in the cm10 thread. I flashed perseus booted and let my phone not boot (stayed at the cyanogen logo). Did a battery pull then re flash cm10.
Sent from my SGH-I317 using xda app-developers app
Xirta said:
I posted something like this a while back in the cm10 thread. I flashed perseus booted and let my phone not boot (stayed at the cyanogen logo). Did a battery pull then re flash cm10.
Sent from my SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
You are the one that told me how to fix it Lol still have the pm.
Was a great find!
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
okay first of all let me say that this is all at your own risk..
@smitty - booting to the aosp rom after flashing a touchwiz kernel is highly not recommended since it may literally hard brick your phone. of course people can do as they choose at their own risk
@seh - unless you have real source and proof, i dont think you should blame scott's rom. he puts a lot of work into his Roms and it would be not right to blame his ROM for sensor malfunction without legit source.
im sure sensor issues will work out soon on aosp themselves, but this is my current temp fix. also i dont really recommend dirty flashing. theoretically it shouldnt matter since the peresus kernel will be erased with the new rom, but I still dont recommend it. always clean wipe!
jee'sgalaxy said:
okay first of all let me say that this is all at your own risk..
@smitty - booting to the aosp rom after flashing a touchwiz kernel is highly not recommended since it may literally hard brick your phone. of course people can do as they choose at their own risk
@seh - unless you have real source and proof, i dont think you should blame scott's rom. he puts a lot of work into his Roms and it would be not right to blame his ROM for sensor malfunction without legit source.
im sure sensor issues will work out soon on aosp themselves, but this is my current temp fix. also i dont really recommend dirty flashing. theoretically it shouldnt matter since the peresus kernel will be erased with the new rom, but I still dont recommend it. always clean wipe!
Click to expand...
Click to collapse
Scotts rom changes something about the drivers, or maybe aroma does. It doesn't mess up the sensors it just changes their drivers or something so that when you flash back to aosp something is broken.
Second of all chill out, I didn't come in here "blaming" anyone for anything. I'm explaining where the problem derives from. I'm sure it's just some unintentional glitch that Scott will work out in the future.
seh6183 said:
Scotts rom changes something about the drivers, or maybe aroma does. It doesn't mess up the sensors it just changes their drivers or something so that when you flash back to aosp something is broken.
Second of all chill out, I didn't come in here "blaming" anyone for anything. I'm explaining where the problem derives from. I'm sure it's just some unintentional glitch that Scott will work out in the future.
Click to expand...
Click to collapse
what do they change about the drivers? how do you know that they do?
seh6183 said:
Scotts rom changes something about the drivers, or maybe aroma does. It doesn't mess up the sensors it just changes their drivers or something so that when you flash back to aosp something is broken.
Second of all chill out, I didn't come in here "blaming" anyone for anything. I'm explaining where the problem derives from. I'm sure it's just some unintentional glitch that Scott will work out in the future.
Click to expand...
Click to collapse
hey, let me be clear on one thing. i am chill and there's no need for you to get defensive with me.
but let me quote you for arguments sakes. "CLEAN ROM is the culprit" sounds like blaming to me. also let me quote you again here. " I'm explaining where the problem derives from."... yet you explain by using words such as "something" or "maybe" and then you're telling me that Scott's ROM changes drivers. you failed at explaining where the problem derives from and therefore i take it as blaming and not fact.
also the reason i think it's not Scott's ROM problem is because the sensors are fixed in AOSP with a flash of a kernel. kernels have nothing to do with changes in drivers since it is only a component of the OS that bridges the hardware to the programs of the OS. therefore, my theory is that the way the stock kernel bridges and the way the peresus kernel bridges the hardware and programs is different. so then when you flash a AOSP rom on top of the two different kernel, in addition to the way how all phones are a bit different, the unlucky people gets their sensors borked. this was my experience hence i will state that this is only my speculation, not fact until others chime in.
Smittyzz said:
Its not clean ROM I don't think. I think its some phones. And yes install the ROM twice.
Do this:
FAC/sys wipe
Install jelly beer
Boot to no censors
Reboot to recover
Install a touch wiz kernel and reboot till you get a black screen.
Pull battery
Reinstall jelly beer
If you follow my steps exact they will work perfect
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
Followed these instructions, and the sensors did work. Unfortunately I still didn't have Bluetooth, and I was a little concerned about the process of doing these steps to my $700 phone. So for now, I've moved onto Noteorious, and will keep that until the AOSP ROMS are worked out.
jee'sgalaxy said:
hey, let me be clear on one thing. i am chill and there's no need for you to get defensive with me.
but let me quote you for arguments sakes. "CLEAN ROM is the culprit" sounds like blaming to me. also let me quote you again here. " I'm explaining where the problem derives from."... yet you explain by using words such as "something" or "maybe" and then you're telling me that Scott's ROM changes drivers. you failed at explaining where the problem derives from and therefore i take it as blaming and not fact.
also the reason i think it's not Scott's ROM problem is because the sensors are fixed in AOSP with a flash of a kernel. kernels have nothing to do with changes in drivers since it is only a component of the OS that bridges the hardware to the programs of the OS. therefore, my theory is that the way the stock kernel bridges and the way the peresus kernel bridges the hardware and programs is different. so then when you flash a AOSP rom on top of the two different kernel, in addition to the way how all phones are a bit different, the unlucky people gets their sensors borked. this was my experience hence i will state that this is only my speculation, not fact until others chime in.
Click to expand...
Click to collapse
Hey thanks for spending all that time writing that. In the same amount of time you could have flashed Scotts rom and them tried aosp to see that stuff is broken. Such as I have done which gives me the AUTHORITY to comment on it. Until you have done testing of your own how about you just not post anything at all?
Touchwiz to Scotts rom, no sensors broken
Touchwiz to aosp, no sensors broken
Touchwiz to Scotts rom to aosp, SENSORS BROKEN
By using my iq that is over 75 I um da um deduce that maybe um that it could be um Scotts rom.
Thanks for the post OP fixed my problem.
I had tried Jellybeer in the past and all had worked. Then went over to scotts, which was equally awesome. Then went to try Jelly bam the other few aosp and couldn't get any sensors working. Followed first post instructions and everythign works now. Thanks a lot.
seh6183 said:
Hey thanks for spending all that time writing that. In the same amount of time you could have flashed Scotts rom and them tried aosp to see that stuff is broken. Such as I have done which gives me the AUTHORITY to comment on it. Until you have done testing of your own how about you just not post anything at all?
Touchwiz to Scotts rom, no sensors broken
Touchwiz to aosp, no sensors broken
Touchwiz to Scotts rom to aosp, SENSORS BROKEN
By using my iq that is over 75 I um da um deduce that maybe um that it could be um Scotts rom.
Click to expand...
Click to collapse
this is such pointless argument... again, what kernel do you flash with his aroma option. and please, i've done all the flashing (NOTErious, Scott's Clean, Saurom) and i will tell you from my experience and my AUTHORITY, that it is a kernel base problem, not scott''s problem... ill repeat again, what kernel did you flash on scott's rom? try flashing it with peresus in his aroma option and THEN flash the AOSP with full wipe..
i won't argue with you anymore.
SpecialK17 said:
Thanks for the post OP fixed my problem.
I had tried Jellybeer in the past and all had worked. Then went over to scotts, which was equally awesome. Then went to try Jelly bam the other few aosp and couldn't get any sensors working. Followed first post instructions and everythign works now. Thanks a lot.
Click to expand...
Click to collapse
SHOCKING.
I would also like to point out that in the past I flashed Scotts rom on a different device and when I went back to aosp I could not get my wifi to function. Not even a nandroid fixed it. I am very curious to know if Scotts rom or aroma is the culprit. Like I've said multiple times in this thread already to the ones that can read English.
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.