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
Related
I was running stock rooted G.B. 2.3.6 and just to see what would happen (I kinda knew already) I did the official upgrade to the ICS 4.0.3. Of course it went from UVKL1 to UVLE1 and I had backed everything up with Titanium Backup and also with Rom Manager. I lost root, because I did a factory reset because it wouldn't install the first 2 times. Oh, I was doing it through Kies. I wanted to do it by the book sort of.So after the install I tried to get root again but when I got into CWM recovery I had no functions working except reboot. No update.zip from sd, or anything else. I could scroll up and down and stop on the different options but when I pushed the button to make the choice it jumped back to reboot and that is all I can get. I rebooted and retried 4 or 5 times and same thing. So, now what ? I like the 4.0.3 but hate the massive amount of bloat and the ads and f**ked up notification popup/ads. I want my root back. I would be willing to start fresh again with a good, fast, everything works, custom ICS but don't know which to choose. that is one of the reasons why I tried this "official" upgrade. Again, as always, Thanks in advance for everyone who helps anyone here on XDA. K.K.-Out
Have you tried reflashing cwm?
Sent from my SGH-T989 using XDA
khkaiser13 said:
I was running stock rooted G.B. 2.3.6 and just to see what would happen (I kinda knew already) I did the official upgrade to the ICS 4.0.3. Of course it went from UVKL1 to UVLE1 and I had backed everything up with Titanium Backup and also with Rom Manager. I lost root, because I did a factory reset because it wouldn't install the first 2 times. Oh, I was doing it through Kies. I wanted to do it by the book sort of.So after the install I tried to get root again but when I got into CWM recovery I had no functions working except reboot. No update.zip from sd, or anything else. I could scroll up and down and stop on the different options but when I pushed the button to make the choice it jumped back to reboot and that is all I can get. I rebooted and retried 4 or 5 times and same thing. So, now what ? I like the 4.0.3 but hate the massive amount of bloat and the ads and f**ked up notification popup/ads. I want my root back. I would be willing to start fresh again with a good, fast, everything works, custom ICS but don't know which to choose. that is one of the reasons why I tried this "official" upgrade. Again, as always, Thanks in advance for everyone who helps anyone here on XDA. K.K.-Out[/QUOT
Try this
http://forum.xda-developers.com/showthread.php?p=3649
Vibrant- Kankwich CM9
Galaxy S2 Hercules- An amazing machine on any rom. Believe me!!
Click to expand...
Click to collapse
blackangst said:
Have you tried reflashing cwm?
Sent from my SGH-T989 using XDA
Click to expand...
Click to collapse
I haven't tried anything yet. I haven't had time. I will try as you suggest. it was on my list of things to try. Thanks, Blackangst.
khkaiser13 said:
I haven't tried anything yet. I haven't had time. I will try as you suggest. it was on my list of things to try. Thanks, Blackangst.
Click to expand...
Click to collapse
I hope it works for you. Check the md5 to make sure you don't have a corrupt download too (of cwm)
Sent from my SGH-T989 using XDA
Thanks ToledoG28, I tried that link and it wasn't a good page. I appreciate the effort. Maybe you could double check it and let me know.
OP: Here's CWM 5.0.2.6. After flashing and once youre back into your phone, you can install ROM manager and upgrade to whatever you want. Push this via Odin.
This happened to me. I had just had to wipe the cache in recovery and it booted. I would try that first
You have to use darkside wipe and darkside cache wipe. The regular recovery wipe isn't working properly.
You just need to Odin ics.
Sent from my SGH-T989 using xda premium
Guys he can't get into recovery. How can he flash super wipe etc if he can't? And how will odining ics fix that? He needs to odin the recovery i posted.
Sent from my SGH-T989 using XDA
I got it solved you guys. Thanks to all of you. I did another factory reset, and then found the actual T989 Hercules .tar file (the one I used was from a post for ICS from November or December and was actually an Infuse tar file.) and reinstalled it. I was able to after I got cwm recovery old style not touch. Touch was what was giving me problems. So I Odin the new Hercules.tar and then rereinstalled Superuser zip and everything went smooth. The only thing I am seeing as a problem is the phone won't sleep. If I have the phone plugged in, I can't shut it off. It wants to immediately turn itself back on. I like to have it shut down and charge at night sometimes. But it won't let me. Any ideas? Thanks again everybody.
i just picked up an e4gt today, i had one back in december that i rooted then sold. so im back and now there's a ton of stuff out there for this phone.
i just came over from the evo design where there is pretty much nothing happening, and before that i had an evo shift. i had cm7 installed on that and loved it.
so what rom do you guys suggest i use? i see there is cm9 available in alpha form, which has me very tempted.
im looking for a stable rom with no bloatware. and id love some advice.
BiffTirkle said:
i just picked up an e4gt today, i had one back in december that i rooted then sold. so im back and now there's a ton of stuff out there for this phone.
i just came over from the evo design where there is pretty much nothing happening, and before that i had an evo shift. i had cm7 installed on that and loved it.
so what rom do you guys suggest i use? i see there is cm9 available in alpha form, which has me very tempted.
im looking for a stable rom with no bloatware. and id love some advice.
Click to expand...
Click to collapse
Go with cm9 that darchstar has posted. It works great and I use it as my daily. After you do the base install I recommend nightly 7/24 and using the chris41g kernel b3 version with it. Great battery life and full functionality.
Sent from my SPH-D710 using xda app-developers app
Does cm9 wipe out cwm?
I'm paranoid to do anything without an option for recovery.
Sent from my SPH-D710 using Tapatalk 2
Here is your safest bet (as in super safe):
1. Download the el26 safe cwm kernel from the kernel repository in the sticky for this phone
2. Download cm9 6 and gapps
3. Follow cm9 6 download instructions
4. Let it boot
5. Use mobile Odin if you have it (highly recommend as it makes flashing so easy) and flash the el26 kernel that you downloaded in the kernel section from external sd...always check md5 sum first!
6. Once u see the blue light on ur phone in the LED, hold power+volume up to boot into recovery, once the sgs2 logo shows you can lay off the buttons
7. If you didn't do it in time or held too long, just pull the battery and go to recovery via power+volume up
8. You should be in cwm, flash the nightly of cm9, clear dalvik and cache, then flash the chris 41g b3 kernel and reboot
9. Enjoy
10. From this point forward you have a bomb rom and working recovery that will allow backup/nand/flashing safely.
Sent from my SPH-D710 using xda app-developers app
Look into Blu Kuban(team venum). No bloat, excellent help from dev. Plenty of options/mods/hacks/updates/themed apps/speed/great battery.
Ditto on Alex. Excellent support... Great battery life. It's themed so you should look at the screenshots and the video on the dev site.
Sent from my SPH-D710 using XDA
ok, i think im going to try the cm9 route, but i cannot find the correct kernel, or im doing something wrong. i got odin for android, and downloaded a couple of kernels i thought were the right ones and they didnt show up when i tried to select them with odin.
BiffTirkle said:
ok, i think im going to try the cm9 route, but i cannot find the correct kernel, or im doing something wrong. i got odin for android, and downloaded a couple of kernels i thought were the right ones and they didnt show up when i tried to select them with odin.
Click to expand...
Click to collapse
Here is the link for el26, first download.
http://forum.xda-developers.com/showthread.php?p=26295021
The chris41g kernel has its own thread in development, grab the zip format of the cwm b3 version.
Sent from my SPH-D710 using xda app-developers app
im not finding a b3 version. but i did download the first kernel from chris41g
StockCWM-EL26.zip
i hope thats correct. im going to do a nandroid backup and give it a shot later today. thanks for the help and advice!
its been several months since ive been flashing roms, and i find that it takes me a few days to get back in the swing of things before im flashing again.
The b3 kernel is at chris's goo which is linked to in this xda thread.
http://forum.xda-developers.com/showthread.php?p=28981308
Sent from my SPH-D710 using xda app-developers app
So I need to flash el26 kernel first, then I flash 41g-CWM-RC1-b3-0723.zip. then I can flash cm9 and gapps from recovery?
Sent from my SPH-D710 using Tapatalk 2
BiffTirkle said:
So I need to flash el26 kernel first, then I flash 41g-CWM-RC1-b3-0723.zip. then I can flash cm9 and gapps from recovery?
El26, boot to recovery, install cm9 per their install guide...after successful install, flash el26 again, wipe cache/dalvik, and install the chris41g kernel from there.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Sent from my SPH-D710 using xda app-developers app
dante32278 said:
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
ok, so i got cm9 on the phone. very excited, except for the launcher wont allow me to add widgets. wierd, same thing with my touchpad.
anyway i tried to flash el26 and it stalled at the splash screen, so i opened up recovery and wiped cache and dalvik, then installed the chris41g kernel. and no dice. aaaanyway. whats the benefit to the other kernels versus what i get with cm9? and is there a solution to my problem?
I read 4g is unreliable on Chris' new kernels
Sent from my SPH-D710 using Tapatalk 2
BiffTirkle said:
ok, so i got cm9 on the phone. very excited, except for the launcher wont allow me to add widgets. wierd, same thing with my touchpad.
anyway i tried to flash el26 and it stalled at the boot screen, so i opened up recovery and wiped cache and dalvik, then installed the chris41g kernel. and no dice. aaaanyway. whats the benefit to the other kernels versus what i get with cm9? and is there a solution to my problem?
Click to expand...
Click to collapse
I get that problem whatever I wipe the dalvik cache
Sent from my SPH-D710 using Tapatalk 2
well, im not sure what to do now. i love cyanogenmod, and id put up with a few hiccups if i could. but it looks like i wont be able to use this as a daily rom. very disappointing...
so, i might try the blu kuban rom.
at this point i want a debloated stable rom. im back to a rooted stock rom with el29.
i just dont want to brick my phone, i have insurance and can take it in to swap it out. its just a waste of time if i can avoid it.
any other suggestions?
BiffTirkle said:
well, im not sure what to do now. i love cyanogenmod, and id put up with a few hiccups if i could. but it looks like i wont be able to use this as a daily rom. very disappointing...
so, i might try the blu kuban rom.
at this point i want a debloated stable rom. im back to a rooted stock rom with el29.
i just dont want to brick my phone, i have insurance and can take it in to swap it out. its just a waste of time if i can avoid it.
any other suggestions?
Click to expand...
Click to collapse
Start with thread #1 on the attached link.
http://forum.xda-developers.com/showthread.php?t=1625535
To Install
Boot to recovery
Make an NAND Backup
Wipe the phone (with the Format All X2 script)
Flash Part 1
Boot the phone
Go to the updater (Under put things back to stock) and install Part 2 (Two part install is to finish theming Talk)
Reboot and Enjoy
When I did this I went to CWM to flash this through odin. Rom works very smooth. There is a ton of information in the thread but that should get you started.
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.
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
So, I'll tell the story like it is:
I have a Samsung Galaxy Note 2 from At&t. I was on a touchwiz rom, and like most everybody, the lag became unbearable. So, like the other countless times before, I downloaded the Kitkat port for Cyanogenmod. All was well and I transferred it, along with the right gapps onto my phone, went into the recovery and flashed it after wiping user data, cache, and dalvik cache. I booted it and experienced bootloop. I went back into my recovery, CWM at the time, and factory data reset it and rebooted. Bootloop persisted. Baffled, I put re flashed my old touchwiz rom and loaded CM Installer on it, installed through that service and all was well. When it booted I found out that it was an RC build of 4.3, not what I wanted. I then downloaded countess other 4.4 roms like Packman and Illusion as well as Omin, none booted successfully. I then searched on XDA for a bit and found that some older versions of CWM recovery were not compatible. So I downloaded the latest version and flashed through Odin. Tried all 4 of the previously named ROMS again and yet bootloops continue to happen. I've flashed roms before and this has never happened! What am I doing wrong?
abdullaha said:
So, I'll tell the story like it is:
I have a Samsung Galaxy Note 2 from At&t. I was on a touchwiz rom, and like most everybody, the lag became unbearable. So, like the other countless times before, I downloaded the Kitkat port for Cyanogenmod. All was well and I transferred it, along with the right gapps onto my phone, went into the recovery and flashed it after wiping user data, cache, and dalvik cache. I booted it and experienced bootloop. I went back into my recovery, CWM at the time, and factory data reset it and rebooted. Bootloop persisted. Baffled, I put re flashed my old touchwiz rom and loaded CM Installer on it, installed through that service and all was well. When it booted I found out that it was an RC build of 4.3, not what I wanted. I then downloaded countess other 4.4 roms like Packman and Illusion as well as Omin, none booted successfully. I then searched on XDA for a bit and found that some older versions of CWM recovery were not compatible. So I downloaded the latest version and flashed through Odin. Tried all 4 of the previously named ROMS again and yet bootloops continue to happen. I've flashed roms before and this has never happened! What am I doing wrong?
Click to expand...
Click to collapse
Have you tried another 4.3 ROM like
this
http://forum.xda-developers.com/showthread.php?t=2589891 or
this
http://forum.xda-developers.com/showthread.php?t=2704375
Sounds like you got wood for a 4.4 ROM. So was the latest version of TWRP 2.7.X.X? Assuming it is since it's listed right by the OMNIROM....
Are you waiting maybe up to 5-7 minutes to let it boot ? You've been beating the bejesus out of it.
Honestly I would flash one of the above and run it for a day. Then go back to flashing. Get it running stable again on stock.
That's just me.... I'm hoping that works for you after all you've thrown at it.
dicksteele said:
Have you tried another 4.3 ROM like
this
http://forum.xda-developers.com/showthread.php?t=2589891 or
this
http://forum.xda-developers.com/showthread.php?t=2704375
Sounds like you got wood for a 4.4 ROM. So was the latest version of TWRP 2.7.X.X? Assuming it is since it's listed right by the OMNIROM....
Are you waiting maybe up to 5-7 minutes to let it boot ? You've been beating the bejesus out of it.
Honestly I would flash one of the above and run it for a day. Then go back to flashing. Get it running stable again on stock.
That's just me.... I'm hoping that works for you after all you've thrown at it.
Click to expand...
Click to collapse
I thank you for your suggesion but other than what you have said, do you have any other ideas on what I'm doing wrong?
abdullaha said:
I thank you for your suggesion but other than what you have said, do you have any other ideas on what I'm doing wrong?
Click to expand...
Click to collapse
Not a clue.... Sounds like everything is good. I don't think you're doing anything wrong operational. Your phone just ain't happy.
I think it wants what it wants. And it's appearing it's not a 4.4 ROM at the moment.
That's what it's looking and sounding like to me.
abdullaha said:
So, I'll tell the story like it is:
I have a Samsung Galaxy Note 2 from At&t. I was on a touchwiz rom, and like most everybody, the lag became unbearable. So, like the other countless times before, I downloaded the Kitkat port for Cyanogenmod. All was well and I transferred it, along with the right gapps onto my phone, went into the recovery and flashed it after wiping user data, cache, and dalvik cache. I booted it and experienced bootloop. I went back into my recovery, CWM at the time, and factory data reset it and rebooted. Bootloop persisted. Baffled, I put re flashed my old touchwiz rom and loaded CM Installer on it, installed through that service and all was well. When it booted I found out that it was an RC build of 4.3, not what I wanted. I then downloaded countess other 4.4 roms like Packman and Illusion as well as Omin, none booted successfully. I then searched on XDA for a bit and found that some older versions of CWM recovery were not compatible. So I downloaded the latest version and flashed through Odin. Tried all 4 of the previously named ROMS again and yet bootloops continue to happen. I've flashed roms before and this has never happened! What am I doing wrong?
Click to expand...
Click to collapse
Are you sure that you have a kernel that support cm ROM? Just curious.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Format system with your other wipes.
What he ^^^^ said. You probably have so many fragments, wipe system three times.
And internal storage wipe may be needed as well...
But MAKE SURE you have a full backup of a complete and working rom BEFORE wiping....just in case...g
Sent from my SGH-I317 using XDA Premium 4 mobile app
dicksteele said:
Have you tried another 4.3 ROM like
this
http://forum.xda-developers.com/showthread.php?t=2589891 or
this
http://forum.xda-developers.com/showthread.php?t=2704375
Sounds like you got wood for a 4.4 ROM. So was the latest version of TWRP 2.7.X.X? Assuming it is since it's listed right by the OMNIROM....
Are you waiting maybe up to 5-7 minutes to let it boot ? You've been beating the bejesus out of it.
Honestly I would flash one of the above and run it for a day. Then go back to flashing. Get it running stable again on stock.
That's just me.... I'm hoping that works for you after all you've thrown at it.
Click to expand...
Click to collapse
Thank you! You were right! I switched back to stock and rerooted and redid the flashing and it worked like a charm! I have no idea why it didn't work the first time. Thank you for your help.
Sent from my T0LTE using XDA Premium 4 mobile app
abdullaha said:
Thank you! You were right! I switched back to stock and rerooted and redid the flashing and it worked like a charm! I have no idea why it didn't work the first time. Thank you for your help.
Sent from my T0LTE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Glad it worked. These phones are tanks, hard to crush them. But they will let you know when they are not happy with what you did.