Related
so, I've had my SG2 for like a month now, rooted and all, but the problem is , i can't flash any other ROMs(but stock ROMs) or kernels (except for CF root,stock and siyah kernels ) on it via CMW... each time i tried to flash anything, i end up stuck at "galaxy s2 GT-I9100" boot-up logo.... I've tried flashing CM7 then i got the boot-loop ( even with double flash, or triple didn't work for me) and i can't get into CWM when i got the boot-loop....
someone please help me.. i read alotta threads and none of them got similar issue like mine...
i guess its true what they say : every galaxy s2 is different from the rest.
Hmm....must be something you're doing wrong. Nothing to do with Galaxy S2 being different.
Have you always followed the dev's instructions while flashing roms?
Wiping data, cache? Matching up the kernels and roms?
As far as I know, there hasn't been a single person who completely failed to install VillainROM on their SGS2.
I would advise you to give it a go.
Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
What ROMs have you tried to flash?
If you're tring to flash AOSP ROms like CM7 or MIUI it's normal if you're not doing it with a comatible version of CWM. For example, cf root kernel installs a modified version of CWM on your device, which is not compatible with CM7. IF you want to flash CM7 first you have to flash codeworkx kernel http://forum.xda-developers.com/showthread.php?t=1118693, and then enter recovery (the new CWM installed with this kernel) to flash CM7.
Now if you can't flash samsung firmware based ROMs (villainROM, Leomar Revolution, Batista...), I don't know what it could be. I never had a problem flashing samsung firmware custom ROMs with the cf root CWM recovery.
tomascunill said:
What ROMs have you tried to flash?
If you're tring to flash AOSP ROms like CM7 or MIUI it's normal if you're not doing it with a comatible version of CWM. For example, cf root kernel installs a modified version of CWM on your device, which is not compatible with CM7. IF you want to flash CM7 first you have to flash codeworkx kernel http://forum.xda-developers.com/showthread.php?t=1118693, and then enter recovery (the new CWM installed with this kernel) to flash CM7.
Now if you can't flash samsung firmware based ROMs (villainROM, Leomar Revolution, Batista...), I don't know what it could be. I never had a problem flashing samsung firmware custom ROMs with the cf root CWM recovery.
Click to expand...
Click to collapse
If your phone has cf-root/kernal and cf cwm can you just flash over top codeworkx's kernel and do you have to re-root?
InFa_ReD_1 said:
If your phone has cf-root/kernal and cf cwm can you just flash over top codeworkx's kernel and do you have to re-root?
Click to expand...
Click to collapse
If you already have root then you won't loose it.
geko95gek said:
Hmm....must be something you're doing wrong. Nothing to do with Galaxy S2 being different.
Have you always followed the dev's instructions while flashing roms?
Wiping data, cache? Matching up the kernels and roms?
As far as I know, there hasn't been a single person who completely failed to install VillainROM on their SGS2.
I would advise you to give it a go.
Transmitted from a Galaxy far far away via XDA lightspeed telepathy.
Click to expand...
Click to collapse
I used to use VR 3.0 but could only work with stock kernel or cf root kernel has never booted with the ROM's kernel..
tomascunill said:
What ROMs have you tried to flash?
If you're tring to flash AOSP ROms like CM7 or MIUI it's normal if you're not doing it with a comatible version of CWM. For example, cf root kernel installs a modified version of CWM on your device, which is not compatible with CM7. IF you want to flash CM7 first you have to flash codeworkx kernel http://forum.xda-developers.com/showthread.php?t=1118693, and then enter recovery (the new CWM installed with this kernel) to flash CM7.
Now if you can't flash samsung firmware based ROMs (villainROM, Leomar Revolution, Batista...), I don't know what it could be. I never had a problem flashing samsung firmware custom ROMs with the cf root CWM recovery.
Click to expand...
Click to collapse
My phone came with CM7, but i flashed it with rooted stock coz i wanted to have a feel of it... but now i'm done with it but i can't get any roms to work... so frustrating.
i literally have tried flashing ALL Roms (ligtnung, gingerbread,vr, cm7), during the 1st few days that i got my phone it worked with VR 2.5 and 3.0, even MIUI.. but after i flashed with some Asian stock ROM via odin... nothing would work through cmw anymore...
i seriously don't know what i did wrong...
btw, right now im using basebad ver: I9100XXXKI4, kernel: 2.6.35.7-siyah [email protected]#20, build number GINGERBREAD.ZSKI3.
I really don't know. YOu should try to go the closest possible to stock and try from there. DO a full wipe, wipe data, wipe system, everything and flash a stock ROM from your country and carrier (there is a thread from infratech where you can get carrier specific ROMS). THen connect your phone to kies (maybe yo get an oficial update) and then do everything from scratch, root, install CWM, etc...
That's what I'd do but I really don't now if it's the best option.
i have almost the same problem,but me i can flash any rom,but the problem is with the kernel my phone refuse to boot on any other kernel else than cf-root and the speedmod,it freezes in the kernel loading so i must turn it off and reflash via odin cf-root or speedmod to get it works again.
tomascunill said:
I really don't know. YOu should try to go the closest possible to stock and try from there. DO a full wipe, wipe data, wipe system, everything and flash a stock ROM from your country and carrier (there is a thread from infratech where you can get carrier specific ROMS). THen connect your phone to kies (maybe yo get an oficial update) and then do everything from scratch, root, install CWM, etc...
That's what I'd do but I really don't now if it's the best option.
Click to expand...
Click to collapse
well, i'm gonna try that and see if it works, am also goin' try to see if downgrading to 2.3.4 or something would work too...
but please if you got any more ideas, just keep it coming..
thanks
Phew! NOW I HAVE CM7 RUNNING ON MY PHONE!!
I'm gonna try to explain how i fixed my issue, as clear and explanatory as i can..
lucky i didn't brick my phone during all this, because I tried so many things and none worked.I unsuccessfully tried downgrading to XWkI4, ZCKI4, and alot others via Odin... after flashing all i get is tons of error messages(on 3e recorvery) E: can't open/cache or E:failed blah bla bla to load /efs... i thought OMG! my phone is bricked! then i recalled reading somewhere that flashing the 3 tar (PDA,MODEM,CSC) files usually should work(maybe better than flashing a 1 tar file), so i found a 3 files xxKI3 rom, flashed it and BAM! it booted up this time without any error. so now i went ahead and rooted it since the tar files came unrooted, then went into CWM to flash cm7 ROM, flashed it twice and ofc i got stuck on boot logo.....i didn't panic much, i pulled out the battery, and restarted to CWM where i cleared cache/ dalvik/ and did wipe/factory reset, then i reflashed CM7 again (twice) and it worked!!!! YES, CM7 is fiannly working on my SG2!
thanks for everyone for helping, and i hope this can help others on the same boat as me..
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.
Coming from passion rc 13.1 for over a month.
Thinking of flashing a new rom.
after cache wipe it reads "E:unknown volume for path [Sd-ext]
this is totally unexpected. its my first flash error.
the flash the Miuiv4 4/27 built
it reads "status 7 installation aborted. and i reflashed it four times and still the same issue.
then I tried ICS zen 1.7 and i reflashed it four times and still the same issue.
finally I decide to flash back to Passion RC13.1 and the installation completed.
im so confused why I cant flash a new rom.
Anyone knows a solution for this?
Old recovery. Flash a kernel like glitch first then get into recovery and flash whatever you want.
Sent from samsung Vibrant
Alex9090 said:
Old recovery. Flash a kernel like glitch first then get into recovery and flash whatever you want.
Click to expand...
Click to collapse
do you mean my recovery is an old version?
my recovery is version 5.5.0.2
how does a flashing of new kernel help solve the issue?
Yes. All of our kernels come bundled with recovery. Flash a newer version.
Sent from samsung Vibrant
Ohai!
I have a Galaxy Player 5.0 USA (YP-G70), and a few days ago I installed Entropy512's kernel via the `dd` method. Everything worked nicely, until I decided to boot into ClockworkMod Recovery by holding the volume up key while booting. It booted into the recovery menu, and everything worked nice, but when I hit 'reboot' or 'shutdown', it booted right back into recovery (after seeing the SAMSUNG screen for about 5 seconds).
I've done pretty much everything I can think of. I've reflashed the kernel, flashed CM7 and CM9, and I tried flashing a stock ROM that I found. Flashing the kernel from the stock ROM causes my device to instead go into "Android System Recovery" rather than ClockworkMod Recovery, but I'm able to get back into CWM by flashing Entropy's kernel with heimdall.
I'm capable of getting root access with `adb shell`. I've wiped almost everything on the device (used the 'wipe data/factory reset' option and 'wipe cache partition' option) but still continues to boot into CWM recovery.
I'm not too interested in simply fixing the device so it's back to stock, as I *really* want CM9. I have a Droid X to keep me busy for now, so I found that my Galaxy Player has been just sitting there, collecting dust. If I can get it to run CM9, I'd have more use for it.
I apologize if I left out some important information. Any help would be appreciated!
Thanks in advance,
- Ben
Just an update, I tried an exitrecovery.zip, which did not help. I also extracted the exitrecovery.sh from the zip and executed the one command it had inside it manually in a root shell. Still stuck. Is my device bricked in some form? I'm pretty sure there is some bootflag that tells it to boot into recovery, even if everything is fine.
I would suggest to go ahead and flash CM9, because your problem may be caused by formatting/corrupting /system (the kernel has nothing to load, so it drops you into recovery).
Once you flash cm9, however, do not flash Entropy's kernel again.
Sent from my YP-G70
East gsstert
Mevordel said:
I would suggest to go ahead and flash CM9, because your problem may be caused by formatting/corrupting /system (the kernel has nothing to load, so it drops you into recovery).
Once you flash cm9, however, do not flash Entropy's kernel again.
Sent from my YP-G70
Click to expand...
Click to collapse
Thanks for the reply. I actually ended up trying so, and CM7 as well, to no avail. I also tried flashing stock, as I said in the post (I think, maybe I forgot to mention it) and it failed. (I used heimdall to flash stock)
I ended up giving up and replacing the device since it was under warranty, but I regret doing such as I *really* wanted to know why this happened in the first place. I'm anxious to get CM9 on it. Should I just put the device into download mode and use heimdall to flash CM9?
No. The safest way (and easiest, IMO) I think is to root it while on stock, install Entropy's kernel (extract the zip and dd it), and use CWM to wipe your device and install CM9, plus back up stock if you want to.
Sent from my 5.0 US with ICS
Mevordel said:
No. The safest way (and easiest, IMO) I think is to root it while on stock, install Entropy's kernel (extract the zip and dd it), and use CWM to wipe your device and install CM9, plus back up stock if you want to.
Sent from my 5.0 US with ICS
Click to expand...
Click to collapse
Apologies for the late reply.
That is what I did last time. I actually got stuck in CWM before even trying to flash CM9 or anything. I just booted into recovery, and then instantly clicked on 'reboot'.
Hmmm... that's really interesting. Although I still have no idea why it would have this problem (I've never had it on Entropy's kernel - which version are you using?), I think I know what the problem is. When you tell android to "reboot recovery", it puts a file in the boot partition that the kernel sees after the reboot and tells it to enter recovery mode. Logically, that file gets deleted so the system boots normally next time. It seems that in your case that failed to happen. But I still am wondering why...
Sent from my 5.0 US with ICS
Mevordel said:
Hmmm... that's really interesting. Although I still have no idea why it would have this problem (I've never had it on Entropy's kernel - which version are you using?), I think I know what the problem is. When you tell android to "reboot recovery", it puts a file in the boot partition that the kernel sees after the reboot and tells it to enter recovery mode. Logically, that file gets deleted so the system boots normally next time. It seems that in your case that failed to happen. But I still am wondering why...
Sent from my 5.0 US with ICS
Click to expand...
Click to collapse
Yeah, seems to be probably what happened. I actually ended up trying again on the new Galaxy Player, and things went swimmingly. I am now happily running CM9 on this device. However, I am scared to even think about booting into recovery again. (I only went into recovery to flash the kernel, and wipe the data partition)
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
TheEgonSpengler said:
I had little issue moving up to 4.0.4 so I don't have to worry about the EMMC erase bug, but I'm realizing I have no way to get up further.
Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details.
Final edit, I found a much better solution.
It does not seem as though you can flash a upgraded kernel from the CWM interface itself and reboot reliably failed on multiple kernels.
Solution
Download mobile Odin
Download the 4.4 ROM of your choice (compatable)
Gapps too stick them all somewhere you can find them (i just leave em in downloads)
Download and flash CWM 6.0.4.4 for Kitkat i777.. no clue where I found it wasn't on XDA though.
Turn the phone off (if you reboot and don't reboot too recovery you get a loop)
Boot to recovery (if you get in a loop here pull the battery THEN boot to recovery)
Now you'll notice your not on your old version of CWM anymore.
Install your ROM and Gapps.
Boot to rom
Boot back to recovery Now your once again on a different version of CWM.
I strongly advise cleaning everything up and installing it again I had some issue until I did.
GL to anyone who finds this thread. If there seems to be a need I could rewrite it with a better title.
Click to expand...
Click to collapse
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
desteele said:
Always remember that when you flash a ROM, that you typically get the Recovery that is tied to the Kernel contained in that ROM. So, you flashed the Kernel, got Recovery A, then you flashed the ROM and got Recovery B. A KK Kernel can be flashed independent of a KK ROM, and will add different/additional/improved functionality, depending on the dev, but it also contains it's own Recovery in most cases.
Click to expand...
Click to collapse
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
TheEgonSpengler said:
"Everything seems to require CWM or a version of TWRP that has no compatible kernels with 4.0.4 best I can do is Siydah and like 6.0.1.2 and looks like CWM but its rather sparse on the details. "
Yes I know, thanks for the advice.
Click to expand...
Click to collapse
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
desteele said:
Oh, sorry...sounded like you expected to find the latest recoveries on JB kernels. My bad.
Click to expand...
Click to collapse
Nah, you just can't install the latest ROM with an older recovery.
So if you want to go up you have to do the little dance I described above. (Yes I know certain walkthroughs indicate you can do the first step in recovery, I simply found that to not be true and gained me only bootloops and the joys of reflashing stock then reinstalling a updated-er version so I could try again.)
wil this work in my situation
Quick question.. am on:
android 4.1.2
Shostock v 3.0.2
my cwm v6.0.2.7.
I want to move for a slimmer kitkat rom..