I have been dual booting stock Android 4.0.4 and CM 9.1 on my S2 for awhile now with minimal issues. However, some small things have stopped working correctly, and since I noticed that both stock Android 4.1.2 and CM 10.1 are now available for the S2, I figured it was about time to switch to those.
I fought with this all last night though but couldn't get it to work. I have been trying the following steps:
Download Android 4.1.2 stock rom from sammobile.com and flash to device using Odin 3.07. Boot up and verify everything is working correctly.
Download Siyah kernel (I'm unfortunately not sure what version as I am at work and it is on my computer at home) and flash to device using Odin 3.07. Boot up and verify everything is working correctly.
Download cm-10.1.3-i777.zip from download.cyanogenmod.org and load image on internal SD card. Boot into CWM recovery. Choose to install 2nd ROM from internal SD card and select that zip file. Verify CWM says installation completes successfully.
Boot both primary and secondary roms and verify they work correctly.
My verifications succeed until step 4, in which both fail. The primary rom (stock Android) gets stuck in an infinite loop loading the AT&T startup image. I just get a blank screen when booting the secondary rom. I've tried these steps a few times with minor variations with the exact same result.
Should I be able to get this to work? If so, what Kernel do I need? My web research seems to be inconsistant as to whether this can work or not. I haven't found anyone that definitively stated they've done this on an S2.
I did find a post for the "Googy" kernel (http://forum.xda-developers.com/showthread.php?t=2270158) that claims this should be possible, but the instructions on how to load it are less that complete. It just says "Flash Googy-Max Kernel", but I'm not sure how to do that. I only know how to flash a kernel using Odin, but Odin needs a .tar.md5 or similar file. The Googy kernel comes in zip format and contains a META-INF directory and boot.img file at its root, and Odin doesn't appear to support that format. Trying to load the zip from CWM after loading the Siyah kernel had ... less than desirable results.
Related
Ok, so I was following the wiki page on cyanogenmod's website.
Coming from 2.1 stock.
I got Cmenard's Overstock kernel installed.
Followed every step, until I got to the part where I flash cyanogenmod.
Clockworkmod recovery works fine, and I backed up the system.
But! I forgot to copy the cyanogenmod files to install to the internal sdcard before I installed the new kernel.
I'm not sure if this kernel isn't compatible with stock 2.1 system, but the system boots, it shows the swipe to unlock but the touch screen doesn't work and I have to pull the battery in order to reboot.
Whats the next course of action to take?
Should I reflash the stock kernel?
If so, do I use heimdall?
Where can I get the stock kernel to flash back?
Is it possible to brick the phone by flashing the wrong kernel?
Thanks in advance,
-drk421
If you can get back to recovery go under mounts and storage and mount usb mass storage and you can copy the files over to your phone.
Hi there. Let me just start off by saying, despite my efforts, I still have next to no idea as to what I am doing.
My Phone: Galaxy SII i9100T (Australian Telstra variant), ICS 4.03
So today I decided to root my phone and install cyanogenmod 9 following a guide in a magazine (that was written for cyanogenmod 7 if that makes a difference). Initially it told me to root with SuperOneClick, but that wasn't working for my device as the program would eventually not respond.
After snooping around on the internet I eventually ended up rooting my phone (I think) with Odin 1.85 installing an image called CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5 under the PDA option (as per instructions of one particular website). That worked.
So then I consulted the magazine again, and it said to download the heimdall suite from the cyanogenmod wiki galaxy sII page, and run a program called zadig, list all devices, and change the 'Samsung Android' driver to whatever zadig installs. However, my phone did not come up as that, it came up as two other files, one with a driver called Modem, and the other with a driver that I cannot remember the name of. I can confirm that they were my phone and no other USB devices as they disappeared when I unplugged my phone. I chose the driver that wasn't called Modem. That seemed to work fine.
Next it said to install a clockworkmod image using the heimdall suite. The image was recovery-clockwork-5.5.0.4-galaxys2 ....I eventually got that to work.
However, no matter what I do now, I cannot get into the clockworkmod recovery screen to install cyanogenmod 9. Did I do something wrong? I think I may have made a mistake with zadig, as now it lists my phone as 4 devices: Samsung_Android, Samsung_Android, Samsung, and MTP.
I know this is an absolute mess of a situation, but I desperately need help. If I cant go through with the installation of cyanogenmod, can I at least reset everything back to normal like it was out of the box?
Any help would be very much appreciated.
You could e-mail the editor of the mag and complain
Sent from my GT-I9100 using xda premium
ultimatebestusername said:
Hi there. Let me just start off by saying, despite my efforts, I still have next to no idea as to what I am doing.
My Phone: Galaxy SII i9100T (Australian Telstra variant), ICS 4.03
So today I decided to root my phone and install cyanogenmod 9 following a guide in a magazine (that was written for cyanogenmod 7 if that makes a difference). Initially it told me to root with SuperOneClick, but that wasn't working for my device as the program would eventually not respond.
After snooping around on the internet I eventually ended up rooting my phone (I think) with Odin 1.85 installing an image called CF-Root-SGS2_XW_NEE_LPG-v5.5-CWM5 under the PDA option (as per instructions of one particular website). That worked.
So then I consulted the magazine again, and it said to download the heimdall suite from the cyanogenmod wiki galaxy sII page, and run a program called zadig, list all devices, and change the 'Samsung Android' driver to whatever zadig installs. However, my phone did not come up as that, it came up as two other files, one with a driver called Modem, and the other with a driver that I cannot remember the name of. I can confirm that they were my phone and no other USB devices as they disappeared when I unplugged my phone. I chose the driver that wasn't called Modem. That seemed to work fine.
Next it said to install a clockworkmod image using the heimdall suite. The image was recovery-clockwork-5.5.0.4-galaxys2 ....I eventually got that to work.
However, no matter what I do now, I cannot get into the clockworkmod recovery screen to install cyanogenmod 9. Did I do something wrong? I think I may have made a mistake with zadig, as now it lists my phone as 4 devices: Samsung_Android, Samsung_Android, Samsung, and MTP.
I know this is an absolute mess of a situation, but I desperately need help. If I cant go through with the installation of cyanogenmod, can I at least reset everything back to normal like it was out of the box?
Any help would be very much appreciated.
Click to expand...
Click to collapse
I suggest you restart from scratch following these steps:
1. read everything about flashing and rooting you can find on this site (read stickies first)
2. same as 1.
3. same as 1.
4. flash the latest stock firmware for your phone
5. root your phone
6. finally flash some other ROM
As a general rule, do not forget to take extra precautions when you flash anything: ALWAYS DO A NANDROID BACKUP IN CWM...
Performs a wipe date , factory reset , then follow the guide;
[GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel
Simple way to root and unroot stock kernel without flashing insecure kernel.
Don't worry about custom counter and yellow triangle, with this method they never appear, because we only rooting, it's a rooting script not a custom kernel.
This rooting script included Busybox installer.
Rooting
Download this File first and put in your SDCARD
- CWM via stock recovery ;( http://dl.dropbox.com/u/34053267/CWM.zip) , or download zip from http://clockworkmod.com/rommanager
- SU-Busybox-Installer.zip ( https://dl.dropbox.com/u/34053267/SU-Busybox-Installer.zip )
Reboot to recovery.
Choose apply update from external storage.
Choose CWM.zip and wait until CWM recovery appear.
Choose install zip from sdcard or external SD
Choose and Install SU-Busybox-Installer.zip
Reboot
You are done and now your device is Rooted
Method 2
CF_Root + stock kernel + [optional] Mobile Odin Free version
Here, you use an older CF_Root kernel, and flash your newer stock kernel
Quote:
First, get a CF_Root kernel from CF_Root thread here http://forum.xda-developers.com/showthread.php?t=1103399. Just get the nearest one to your ROM. You can download any ICS kernel, it will do the job for the root only purpose
Flash the CF_Root kernel with odin
Now, flash again your stock kernel with odin. You can get a stock kernel from lyriquidperfection thread http://forum.xda-developers.com/showthread.php?t=1619525
Do not forget to thank / donate to him
No stock kernels for you? use Mobile Odin free version (see below)
After flashing the stock kernel, root will usually stay and you will be reverted back to your stock recovery instead of CWM recovery
Hi folks, mid last week I woke up to a non responsive Galaxy S2. It's been happily running stock Vodafone ICS for over a year, and somehow spontaneously went soft brick on me. Gets stuck at logo screen or goes into boot loop.
Download mode is accessible. I can flash through Odin (1.85 and 3.09) and it reports success. I have successfully put CWM (various versions) on it can can boot into them fine.
Recovery mode is also accessible and appears to be working fine. I can access external SD card no problem.
Attempting to flash through zip from external SD aborts with Mode 7, reporting bad zip or unable to read source file. I have tried removing asserts from install script (educated myself to the risks and made sure the ROM was correct!!) and multiple versions of CM (10.1.3 stable, 10.2 nightly) and multiple versions of CWM recovery (6.0.2.9 is what I've been using mostly, as recommended by CM guide)
Tried running GS2ROMNukeV2.12.zip which reported successful wipe, then attempted zip install from SD with same result (aborted mode 7). Repeated wipe and attempted stock (I9100TDVLSK_I9100THUTLSD_I9100TDVLS3_HOME.tar) from flash through Odin. Reported success, phone booted into recover and applied KOR CSC successfully, then reboot and still stuck at logo screen/boot loop.
I have attempted the fix in http://forum.xda-developers.com/showthread.php?t=1449771 as best I could wish the resources I could find, but it's hard to follow to the letter with the links broken!!!
I have not tried repartition with PIT as I'm not sure where to get an appropriate PIT file. Advice on this appreciated!
I want to make this clear because people seem to not want to believe it: I did not soft brick my phone flashing it. My best theory at this point is some kind of memory corruption or hardware failure that's causing a boot loop. Any help or suggestions would be appreciated. This week I will probably take it in to a repair shop and hope for the best, but tomorrow is a public holiday and I've got nothing to lose by trying any more suggestions.
Kaine said:
Mode 7
Click to expand...
Click to collapse
If memory serves me right this is due to an old version of Recovery, i had the same thing, updated recovery and it flashed zip fine. just as you know. :fingers-crossed:
Hello all, My end result is to dual boot firefox OS with a custom rom and dual boot using Siyah-s2-v5.0.1 as per these instructions:
developer.mozilla.org/en-US/Firefox_OS/Dual_boot_of_B2G_and_Android_on_SGS2#Boot_operations
the problem I have, is that I have a newer version of Siyah, and that's v6.0b5.
when I attempt to flash it with: heimdall flash --hidden system.img
the problem is I get an error: saying that there is no hidden partition in the PIT.
So, I go and create a list of what is in the PIT, and there is "HIDDEN" (all upppercase), sooo, I try that, and well it doesn't work.
So, I got to thinking that maybe the older version of Siyah, v5.0.1 has a lowercase hidden and that would work?
Anyways. so here I am trying to downgrade and I can't seem too! I've gone from within recovery and installed via there.
I've tried 2 different kernels, including the CF-Root kernel, and wiped all the partitions, cache, etc. but whenever I try and install Siyah-s2-v5.0.1, the yin/yang logo flashes 2x and does nothing. I force back into recovery, and its always 6.0.1.2 soooo. I'm stuck.
UNLESS, someone knows where to put the "hidden" system.img file? so that the Siyah could put it into the 2nd 2ndROM???
thanks sooo much if you can help!!!
Long story short,
Even using a custom recovery I am unable to flash any rom Execpt stock, or a modified stock rom (using Etherealrom 2.4 right now)
And I was wondering if anyone has a dump from odin or Heimdall that I could use to try to flash CM to my device, weather it's cm9 or cm10,
it may help, as from there I may be able to flash other roms.
I'm not sure what wrong with my device, but even when returning to stock, my lock screen fails to engage with a 100% stock Heimdall / odin image,
Even ones I've used in the past with no problems. but everything else seems to work fine.
And be fore you ask,
yes I have tried the manual flashing steps shown on the cm9/10/11 pages,
yes, I have tried using the TerraSilent usa kernal (multiple versions)
yes, I have tired doing a full restore of the image, even with re-partitioning from a pit file
yes, I used the preflash before trying to install cm9/10/11, and tried the various toggles
yes, in the past I was able to flash cm9, but I was on stock for a while, then when trying to switch back, this happened.
yes, I have checked my EMS partition, and even tried manually rebuilding it,
The only way I can flash anything, including sock, and modified stock roms, is from my PC, via odin, or Heimdall
So I was wondering if someone with the USA galaxy player 4 could do a dump for me, and include the pit file,
so I could attempt to get CM installed that way?