I Was On Criskelo 18 Then I Decided To Go To Jelly Bam But
After Flashing I Found That Wifi Signals Was Not Stable (Go Up And Down Randomly) Besides Every Time I Change UI The Phone Went To Boot Loop Until I Remove The Batterry And Put It Again
Battery Someone Said That Happened Because I Flashed Over JB ROM
So I Flashed Check ROM 4.5 (Resurrection By Odin) But The Problem Still There
Then I Flashed Ultima ROM 7.1 But When I Went To Recovery Mode (CWM 6.0.1.2 Touch) I Found That Ultima.zip Is Not Showen I Decided To Remove And Put It Again From My Computer
After Installing The Phone Was Not Responding Until I Removed The Battery Then The Mobile Worked But Wifi Still Not Stable Like When I Was On Criskelo
What I Want To Say What Happened To Wifi And Why The Phone Didn't Respond Until I Removed The Battery
Sorry For The Long Story
if you think that you have problem with WIFI then you should change your kernel cause it depends on kernel not the ROM
komsa said:
if you think that you have problem with WIFI then you should change your kernel cause it depends on kernel not the ROM
Click to expand...
Click to collapse
WiFi Was Stable On Stock Kernel Until I Flashed CM10 Kernel Now I Am On Latest Stock Kernel Modem And The Problem Still There Do You Think I Should Flash Custom Kernel? And What About CWM? Thank You For Quick Responding
Related
Hello,
Today I thought, let's try out ICS! Found this guide (can't post outer links, search for "android advices ICS Android 4.0.1 XXKP2 " in google), and used it to update my phone to ICS.
Well, after trying out the rom, I would like to go back to my MIUI backup, rooted it, installed clockworkmod recovery and booted up the recovery mode. The recovery said "can't mount /cache/*" for all cache folders. So I couldn't restore my backup.
After reading some stuff I installed a recovery through Odin. Worked like a charm, no alerts of mounting failures. Restored my backup, but when it was rebooting it gave an "Kernel Panic - Upload mode" screen. Couldn't do anything, so put the battery out and back in.
After this I installed ICS again with the same steps as in the guide. This worked! Rooted and installed recovery again, no problems so far. Tried a fresh install of MIUI but with the same problems.
So I can flash ICS but I can't flash any other rom, what can be the problem?
Every help and tips are welcome!
Thanks in advance!
Same thing happened to me last nite, kernel panic, and im panic too. This happened after flashing that cm9 coz i just wanna try and see how cm9 look like and i know im not going to stick with it, just for trying. Now im back to miui.
What i did is i flashed back to stock rom, root, then flash miui, or any rom that you want. Very simple.
Rom : MIUI ICS XGT 'EXTENDED'
Kernel : Xcell-69X
Modem : XXKP8
Sent from Galaxy SII
I have the same problem I guess, tried ICS, went back to stock which I was using. Got Kernel panic upload mode several times, solution for this was flashing an older 2.3.6 version.
After this no more kernel panics...
But I can't flash any custom roms anymore.
My phone's working luckily but it doesn't work like it's supposed to
Gepstra said:
I have the same problem I guess, tried ICS, went back to stock which I was using. Got Kernel panic upload mode several times, solution for this was flashing an older 2.3.6 version.
After this no more kernel panics...
But I can't flash any custom roms anymore.
My phone's working luckily but it doesn't work like it's supposed to
Click to expand...
Click to collapse
Thats not true my friend, you flash any custom rom. Nothing need to worry about.
Rom : samsung stock firmware
Kernel : stock kernel
Modem : stock modem
Sent from Galaxy SII
Gepstra said:
I have the same problem I guess, tried ICS, went back to stock which I was using. Got Kernel panic upload mode several times, solution for this was flashing an older 2.3.6 version.
After this no more kernel panics...
But I can't flash any custom roms anymore.
My phone's working luckily but it doesn't work like it's supposed to
Click to expand...
Click to collapse
Did you make sure to flash back the old GB bootloaders? Restoring a backup wont flash them back.
Hi All,
i've been trying a few roms and recently i tried to upgrade to a newer nightly build of CM7.
I got the Kernel panic upload mode message you get when you have installed a bootloader from an ICS rom (as i did when i was trying the XXLPB).
Thing is, i tried to reflashing XXKL1 (like i did in the past) and it seems to work ok but firmware seems to be pre-rooted. Not only that but USB debugging seems to be enabled by default (after the reboot from odin).
I downloaded this firmware twice from sammobiles and its the same. I downloaded XXKI3 and that seems to work ok.
anyone know what may be going on?
When i flash KL1 then i normally flash siyahkernel with CMW then i flash cm7 but now in this state that i'm in, once i install cm7 i get a kernel panic upload error even after
I am trying to install the jellybam 3.0.0 rom and am having no luck. I tried just following inst and that didn't work after about 45 sec the android guy fell over and a red triangle popped up. Then I saw you might have to change to siyah 4.3.3 so I downloaded the zip without micswap and flashed it after the Jellybam rom. Still no luck the rom loaded, but when I rebooted the ics symbol showed up then phone turned of. Can someone tell me how to get this to work. I have the ported version and works fine.
Any help would be greatly appreciated. Also thanks for all you guys and gals do your awsome.
Can't install Jellybam???
fountain79 said:
I am trying to install the jellybam 3.0.0 rom and am having no luck. I tried just following inst and that didn't work after about 45 sec the android guy fell over and a red triangle popped up. Then I saw you might have to change to siyah 4.3.3 so I downloaded the zip without micswap and flashed it after the Jellybam rom. Still no luck the rom loaded, but when I rebooted the ics symbol showed up then phone turned of. Can someone tell me how to get this to work. I have the ported version and works fine.
Any help would be greatly appreciated. Also thanks for all you guys and gals do your awsome.
Click to expand...
Click to collapse
I had the same error....i guess you must be getting a "status 7" error while flashing jellybam.....
I used to run SHOstock3 rom v1.4, and i got the same error while flashing jellybam, so i follwed the method given by one of the experts...
1. I did a factory reset, and flashed jellybam, after which i got a status 7 error...
2. I restored the rom via CWM
3. Flashed siyah v3.4.2 with micswap..
4. since that was siyah ics, i could not use my phone, but i was able to flash jellybam over it.....
5. Im running Jellybam without any bugs...
So basically, you can do a full wipe, flash siyah, and then flash J'bam......else use an older version of siyah like i did....Hope u r problem is solved....
Thanks
Aayush_13 said:
I had the same error....i guess you must be getting a "status 7" error while flashing jellybam.....
I used to run SHOstock3 rom v1.4, and i got the same error while flashing jellybam, so i follwed the method given by one of the experts...
1. I did a factory reset, and flashed jellybam, after which i got a status 7 error...
2. I restored the rom via CWM
3. Flashed siyah v3.4.2 with micswap..
4. since that was siyah ics, i could not use my phone, but i was able to flash jellybam over it.....
5. Im running Jellybam without any bugs...
So basically, you can do a full wipe, flash siyah, and then flash J'bam......else use an older version of siyah like i did....Hope u r problem is solved....
Click to expand...
Click to collapse
Trying now...
Its working
Aayush_13 said:
I had the same error....i guess you must be getting a "status 7" error while flashing jellybam.....
I used to run SHOstock3 rom v1.4, and i got the same error while flashing jellybam, so i follwed the method given by one of the experts...
1. I did a factory reset, and flashed jellybam, after which i got a status 7 error...
2. I restored the rom via CWM
3. Flashed siyah v3.4.2 with micswap..
4. since that was siyah ics, i could not use my phone, but i was able to flash jellybam over it.....
5. Im running Jellybam without any bugs...
So basically, you can do a full wipe, flash siyah, and then flash J'bam......else use an older version of siyah like i did....Hope u r problem is solved....
Click to expand...
Click to collapse
Thanks again for sharing the info very helpful.
did that work
fountain79 said:
Thanks again for sharing the info very helpful.
Click to expand...
Click to collapse
Hi All
Did the method of installing Siyah Kernel and then flashing JellyBam work to resolve "error code 7" issue ??
Hello, I have once rooted my stock ICS S2 with this method:ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel http://forum.xda-developers.com/showthread.php?t=1501719, now i have updated OTA my S2 to stock JB 4.1.2, but I am having lots of problems since last week JB oficial update, e.g.: battery drains super fast, camera freezes, default programs dont stick, etc, etc.
My question is: can I downgrade/flash back to stock 4.0.3 via the CWM ? ( every time I need to enter CWM I need to run CWM.zip on the Recovery Mode).
Thanks.
pedrohell said:
Hello, I have once rooted my stock ICS S2 with this method:ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel http://forum.xda-developers.com/showthread.php?t=1501719, now i have updated OTA my S2 to stock JB 4.1.2, but I am having lots of problems since last week JB oficial update, e.g.: battery drains super fast, camera freezes, default programs dont stick, etc, etc.
My question is: can I downgrade/flash back to stock 4.0.3 via the CWM ? ( every time I need to enter CWM I need to run CWM.zip on the Recovery Mode).
Thanks.
Click to expand...
Click to collapse
Via CWN no...but with Odin yes.Search on XDA,there are a lot of guides how to
Actually, you can flash an ICS ROM via CWM.
Which app are giving you issues on JB?
Sent from the little guy
Hi, sorry for having disapeared, but the problem is now fixed, i downgraded from 4.1.2 via normal method, download mode, samfirmware stock firmware for my country, Odin, fingers crossed, reboot, OMG the S2 dont bypass samsung logo, shutdown and rebbot to recovery mode, wipe data/factory reset, finished ok, reboot, auto installing Googleapps, et voila back to 4.0.4.
The problem was that I live in Luxembourg and (still dont know why) I received an FOTA update from Bulgaria.
And one of the problems was e.g. everytime i opened a camera app the entire S2 frozen nothing worked I had to take off battery and reboot.
Thanks for your help.
I am facing a strange issue..I unlocked the bootloader the official way. Installed RR rom latest. Flashed Agni kernel. It was working fine.
After I switched off the device and turned on I noticed that touch is not working... System reboot to normal but touch is fully gone..
I had to flash fastboot rom edl mode to bring back the system to normal...
What might be the reason for loss of touch... Anyone please help....
Don't flash a different kernel, just try RR first, boot and make sure it works.
Once that is done, then you can try flashing the kernel and see if everything works. If it doesn't, you have your answer.
Most custom ROMs are also builded just for their kernel so if u flash custom kernel then there is chance that ROM will not work as u expected. Just think about it when you are installing a custom kernel.
Today I did flash lite mode rom . It boots up but touch was not working...nothing was flashed even gapps.
Sometimes the recovery twrp too does not work.,touch lost. Now i suspect something wrong with the hardware.
But no issues with miui roms...Thats what makes me wonder
did you do it on the computer?
sibikallikkat said:
I am facing a strange issue..I unlocked the bootloader the official way. Installed RR rom latest. Flashed Agni kernel. It was working fine.
After I switched off the device and turned on I noticed that touch is not working... System reboot to normal but touch is fully gone..
I had to flash fastboot rom edl mode to bring back the system to normal...
What might be the reason for loss of touch... Anyone please help....
Click to expand...
Click to collapse
You may want to try installing Radon Kernel. I've got an aftermarket display which also didn't work with a custom rom (Lineage OS), but after flashing Radon Kernel it worked flawlessly. You may want o try Radon 5.0 as I'm having trouble with 5.1.