Hi, all.
I'm currently running a S4-Mini, but miss my old S2 i9100. The S2 had CM11 installed, but in order to install the latest CM12.1 and GApps, I needed to do a factory wipe. I performed the factory wipe from the recovery menu, and it said something about 'getting root' and something being permanently modified. That's fine by me.
Anyway, I rebooted the SGS2 and I'm stuck at the Welcome screen (and yellow triangle). Fine, I thought, I'll just try to enter Recovery mode again, in order to install the downloaded ROMs. Still stuck at the same screen. My last option, as I don't know how to use adb, is to enter 'Download' mode and try Heimdall.
Now here's the weird bit. I have used Heimdall more times than I care to remember, although not for a year or so. I found a CWM recovery image for the i9100, namely, 'CWM_6.0.4.7_I9100.zip'.
The CM wiki page (0) says that the file that Heimdall needs, should not be zip'd,as it needs to use the following syntax:
(0) http://wiki.cyanogenmod.org/w/Install_CM_for_i9100
heimdall flash --kernel zImage --no-reboot
As you'd expect, when I unzip the package, there are many files, which isn't what Heimdall seems to want. For the life of me, I can't remember how I used to do this, and it doesn't help that the recovery image link in the CM wiki, 'cwmr6047.img' doesn't work/ resolve.
Can anyone remind me where I'm going wrong, as I used to be able to do this in my sleep? I'd downloaded the latest CM12.1 Nightly, but I would be content to use XDA's preferred recovery and/ or Lollipop based ROM.
Any help gratefully appreciated.
Thanks,
Chris. and his momentarily dead i9100!
I was passed this link to a good Recovery, on the CM IRC channel (#cyanogenmod)
http://builder.unstableapps.com/#/latest/clockworkmodrecovery/i9100
At least I could get this to work with Heimdall, as it was a .img file., which I used instead of zImage. it didn't solve my connectivity problem though, and there is a thread for this, elsewhere:
http://forum.cyanogenmod.org/topic/80317-heimdall-wont-connectinitialise/
I'm hoping someone will know how to move this forward. I'll post any results.
Thanks,
Chris.
Related
I've been searching all over the forums for hours and I can't seem to get a viable solution to my problem. Here's what happened:
New Samsung Galaxy S2 AT&T
I used the cyanogenmod wiki site to flash clockworkMod recovery:
not realizing that there was a separate page specifically for the S2 for AT&T....so end result is ClockworkMod recovery 4.0.1.4 instead of 5.0.2.3 using Heimdall suite. I don't know if this makes a difference
So with reboot my back and search buttons wouldn't work so I did a factory reset, now I'm stuck in boot loop
Went into CWM recovery, did clean wipe, but it won't let me flash any zip files (gives "no file or directory" error and installation aborted)
I never flashed any ROM's, just the CWM recovery
I don't know what to do. Please help.
I apologize if this is answered elsewhere, but I made an honest effort to search for it.
just follow this thread...http://forum.xda-developers.com/showthread.php?t=1309301 and flash 3 .tar files in odin...
Thanks for the reply zking. I actually saw that thread but wasn't sure if it was applicable. I'm a little confused. I've flashed CWM recovery before on other phones (G1 and G2) without any problems, but those required that I rooted them as well. The cyanogenmod site for the SII seemed (at least to me) to have indicated that root may not be necessary to flash a ROM. Is this true or am I just misinterpreting?
So as it stands, my phone is not rooted. Can this be reason I'm having a problem with CWM recovery? It's not giving me a mounting error, just says file doesn't exist, when I know it's there. Is it looking for .tar format?
and when you say flash 3 .tar files in odin....which files are you referring to (may be dumb question)
First flashed the required firmware from here http://forum.xda-developers.com/showthread.php?t=1075278
than root accordingly as mentioned here http://forum.xda-developers.com/showthread.php?t=1126522
after rooting as per the above method you ll have CWM recovery installed...and you can start using it accordingly.
Don't listen to zking. He's getting you to flash more wrong firmware to your phone. Go to the AT&T forum and download the correct cwm from there. The AT&T version of the phone doesn't work with I9100 firmware.
Sent from my GT-I9100
Hey guys!
Since I tried building Firefox OS -Boot2Gecko- on my Samsung Galaxy S2 (i9100) (FYI: I followed this walkthrough) , I'm having quite a hard time making my phone boot on any ROM I try to install. I still have an access to CWM Recovery and to the Download mode
* After failing to flash B2G's Gaia on my phone, I tried to flash the kernel back to the original one and to restore the CM 10.1 NIGHTLY backup I made before doing all this mess. No changes: stuck at CM's boot screen.
* Tried to get back to a stock firmware and ROM, stucks at boot screen ("Samsung Galaxy S II GT-I9100" screen), even after a wipe data/factory reset, wipe cache and wipe dalvik cache.
(In fact, I achieved to boot on a stock ROM once, but after some other manipulations to get my CM 10.1 back, I now can't get it to boot on any of them anymore.)
* I tried to follow the rooting + CyanogenMod walkthrough on CM's wiki, but the same happens: stucks on boot screen. However, after a wipe data, I reach CM's boot animation, which runs indefinitely.
* Right now I tried flashing with Siyah's Kernel, since the flash counter is not any of my concerns anymore. Whatever I try, I can't get anything to get past the "Booting the primary ROM" message.
However, I installed a stable CM9 on the secondary ROM and... it actually works. But even when cloning 2nd ROM to the 1st ROM, can't get the first to boot anyway.
I am not an expert in Android OS architecture, but could it be related to some kind of modifications made by B2G's build & flashing? Maybe some files in the /data or /system partitions have been altered and are not replaced when fllashing, leading to ROMs not loading up?
Any advice on this is welcome.
PS: English is not my main language, sorry if things aren't explained clearly. Tell me if you need any clarifications about it!
hey there,
i have a similiar problem.
i got the info to reflash it using ODIN.
one user told me, that maybe the NAND-RW could be corrupted....
so iam trying it right now...
good luck
Wipe kernel/rom data with a cleaning script. You can find them in dev sections.
Well I flashed it many times with Odin (or Heimdall when I was on Linux) and I saw no improvement.
I don't think my NAND-RW is corrupted, as I can still boot on Download or Recovery mode.
Just found this tutorial, is it worth the try?
Sakujou_Kei said:
hey there,
i have a similiar problem.
i got the info to reflash it using ODIN.
one user told me, that maybe the NAND-RW could be corrupted....
so iam trying it right now...
good luck
Click to expand...
Click to collapse
Well I flashed it many times with Odin (or Heimdall when I was on Linux) and I saw no improvement.
I don't think my NAND-RW is corrupted, as I can still boot on Download or Recovery mode.
Just found this tutorial, is it worth the try?
TheATHEiST said:
Wipe kernel/rom data with a cleaning script. You can find them in dev sections.
Click to expand...
Click to collapse
This one http://forum.xda-developers.com/showthread.php?t=1363738 (Kernel) and this one http://forum.xda-developers.com/showthread.php?t=2100558&highlight=script (ROM) ?
Ok so I tried the cleaning scripts I linked on my previous message, no changes. I can still boot on Siyah's second ROM, but can't get past the "Booting primary ROM" message.
Ideas anyone?
Hi forum,
I rooted my S2 a year ago and did happily CM 10.1 updates all the time. Everything just fine.
Then 10.2 came out and I gave that a try. One of the first ones did boot but had several issues (phone app missing, no connection to Play Store, etc). I decided to do updates via CM updater. Now I am stuck with nightly from August 24th. The problem then was that I couldn't access the CWM recovery any more and hence the CM Updater. Thus I tried to flash it again with Odin. So I can boot into Odin mode and Odin recognizes the device. I tried flashing several clockworkmods to no avail. Odin hangs for ever if it comes to the actual writing.
After that the phone did not start any more but stayed in that Firmware update encountered an issue screen. I used heimdall and flashed CWM with that. That looked better and then the phone started (somehow after many attempts) again but still no recovery.
Next I installed the latest Dorimanx Kernel with Odin. So that worked. Now the phone starts reliable again but no matter what I try there is no reccovery.
ROM Manager doesn't even start btw.
What I want now is of course a working recovery. At best CWM. Then back to CM 10.1. But how?
I read a lot here and elsewhere but everything I tried just didn't work.
Thanks for help!
Cheers,
blitz-gordon
you used Odin and Heimdall on same PC?!
ROM manager is bad for s2 and could cause bootloops. Don't use it
i suggest that you flash stock rom with odin. and then you'll have to root ur s2 again
TheMasterOfToast said:
you used Odin and Heimdall on same PC?!
ROM manager is bad for s2 and could cause bootloops. Don't use it
i suggest that you flash stock rom with odin. and then you'll have to root ur s2 again
Click to expand...
Click to collapse
Yep, Ubuntu 12.04 and XP as a VM. I used heimdall on another PC though.
I know that ROM Manager is not choice number one. That was more a test which failed anyway.
Well, I thougth I could get away easier.
Thanx!
For the records.
I de-rooted the device by putting a stock image on it. Then I rooted it again and now it runs the latest CM, woohoo!
If somebody wants details I can provide a short howto.
Cheers,
blitz-gordon
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:
I recently purchased a Samsung Galaxy SII, GT-I9100 and have been trying to install LineageOS using this guide:
https://wiki.lineageos.org/devices/i9100/install
I'm at the point where I need to flash TWRP. I've downloaded TWRP 3.2.3.0 and using Heimdall, I'm able to successfully flash the image to my phone, Heimdall's output doesn't mention any errors. However, when I afterwards shut down the phone and then reboot to recovery mode, it's still the old stock recovery present.
I have spent the entire weekend trying to troubleshoot a ton of things and trying many suggested solutions, some not working, others throwing me further down the pit of despair. One of the things I've tried was to flash CF Root. My build number ends in KWMS2, so I've been trying to find a CF root build for that but the only thing I found was this post:
https://forum.xda-developers.com/galaxy-s2/help/cf-root-download-ms2-t2880023
Which then had a link to SuperSU which I sideloaded with adb, but that didn't do anything. I also found this post:
https://forum.xda-developers.com/showpost.php?p=35682278&postcount=4
And flash the CF Root image, but that also didn't help with TWRP. I've also looked at the CF Root site but it doesn't list the GT-I9100 and Firmware.Mobi lists all i9100 versions as incompatible with CF-Auto-Root (which I'm assuming is the same as CF Root).
So because of all the trouble I've had, I'm now stuck with a phone that can boot into download and recovery mode, but can't actually boot into Android and that won't install TWRP for some odd reason.
I hope someone can tell me, in detail, what I'm supposed to do to get TWRP to actually work and not just being flashed, because I'm at my wits end.
Follow this guide (the post literally one below yours!) and you will be up and running in no time.
https://forum.xda-developers.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601