Hello everybody!
Recently I've got used Galaxy S2 (GT-I9100) from ebay. I'd like to update it from GB to JB. Found lots of great information on this forum an in the net, but still not sure if I understand the procedure right.
Some information about current system:
- rooted by previous owner, no idea how exactly.
from "About":
- Android version: 2.3.6
- Baseband: I9100XXKI3
- Kernel: 2.6.35.7-I9100XWKK5-CL754841 [email protected] #2
- Build number: GINGERBREAD.XWKK5
*#1234#:
- PDA: I9100XWKK5
- PHONE: I9100XXKI3
- CSC: Unknown
eMMC check:
- Type: VYL00M
- FwRev: 0x19
- Brick Bug: YES, insane chip
I'm using linux, so Heimdall is a way to go. I downloaded current PIT file from device, XWLSE firmware from Sammobile (includes boot.bin and factoryfs.img only), and PhilZ kernel for this firmware.
Now, if I understand it right, I have to do the following:
1. backup
2. Restart in Download mode
3. Detect device in Heimdall-frontend
4. Choose PIT file I downloaded from device before
5. Choose partition files
6. Flash
At the step 5 I have the problem: boot.img should be the BOOT partition. Different sources say also IBL+PBL, or SBL. However, I have only SBL1, SBL2 in the list.
So, I have following questions, aswers to which I couldn'd find:
1. Do miss something?
2. Why CSC is unknown? is it okay?
3. What is a right Partition Name for boot.bin? Is it OK to call it SBL1 (probably not)
4. If not, what can I do? Can I use different PIT? From where?
5. Is it safe to repartition? (brick bug)
6. If I repartition, do I need images for all partitions?
7. Why Sammobile firmware doesn't include kernel?
I'd be happy to get some answers, or links to relevant information. Meanwhile, reading the forums.
Thanks in advance for any help!
Since u are rooted already, flash using Mobile Odin. Trust me, much safer than Odin/Heimdall.
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 09:53 PM ---------- Previous post was at 09:48 PM ----------
AntonGut said:
1. Do miss something?
2. Why CSC is unknown? is it okay?
3. What is a right Partition Name for boot.bin? Is it OK to call it SBL1 (probably not)
4. If not, what can I do? Can I use different PIT? From where?
5. Is it safe to repartition? (brick bug)
6. If I repartition, do I need images for all partitions?
7. Why Sammobile firmware doesn't include kernel?
Click to expand...
Click to collapse
As for ur questions:
I have personally never used Heimdall, and so I can't answer questions related to it.
Sammobile firmwares do contain kernels (named zImage I guess).
Brickbug affects only 4.0.4 firmwares. U are safe on 2.3.6.
I have heard using PIT files with Odin is a last resort (like when u cannot flash normally), but I don't know if that applies to Heimdall also.
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
Since u are rooted already, flash using Mobile Odin. Trust me, much safer than Odin/Heimdall.
Click to expand...
Click to collapse
Thanks, will look into it.
immortalneo said:
Sammobile firmwares do contain kernels (named zImage I guess).
Click to expand...
Click to collapse
I have three XWLSE with different CSC, one XWLSD and XWLSN from sammobile. All unpacked, none contains kernel (no zImage). All have boot.bin and factoryfs.img, XWLSD also has cache.img. That's all. Not a big issue IMO, since kernels are available separately. Just currious, why is it so, would those firmwares work with older kernel, and which ones do contain kernel.
immortalneo said:
I have heard using PIT files with Odin is a last resort (like when u cannot flash normally), but I don't know if that applies to Heimdall also.
Click to expand...
Click to collapse
It seems, in Heimdall PIT is required. You don't have to repartition though, there is separate checkbox for it. Heimdall doesn't accept .tar.md5 package, but wants to have pratition images separately. If I understand it right, it looks in PIT what partitions are needed, and which image goes where. So I unpacked firmware, downloaded existing PIT, and tried to use it. However, it doesn't have anything called "boot" or "IBL+PBL", but SBL1, SBL2 and some others. That's where I stuck.
Thanks for the info on Heimdall.:thumbup:
On flashing stock firmwares, my custom kernel gets replaced by a stock one. So am sure there must be a kernel in a stock firmware.
Sorry I couldn't be of much help..
"To err is human, to forgive is divine"
Sent from my SGS II
All right, then I have to learn more about contents of firmware and its packaging
Thanks for your input, hope it'll lead me to right solution.
AntonGut said:
All right, then I have to learn more about contents of firmware and its packaging
Thanks for your input, hope it'll lead me to right solution.
Click to expand...
Click to collapse
Please share what u learn here..
And do let us know if u solve ur issue.
"To err is human, to forgive is divine"
Sent from my SGS II
Just a short update. I'm still getting courage to actually flash something on device. Just prefer to understand what I'm doing.
Here is a quite detailled guide for using Heimdall, which confirms that I understood it right in earlier posts. It just didn't mention pit-download function, and suggests to repartition, which is not a good idea according to some.
As for partition purposes, names etc, I'm still quite confused.
This thread explains, that BOOT, RECOVERY, and KERNEL partitions are basically the same, and include actual kernel and initramfs image. This kind of answers the question, where did they hide kernel in sammobile-firmware. It is also mentioned there, that "recovery" is an exact copy of "kernel". However in pit-file from my device they have different size.
Anoter problem/question is why there is boot.bin file in firmware, if partition is zero-size? (as is the case in thread mentioned above). Can it be flashed in kernel-partition? Or in SBL, as per recommendations from this guide? Did partitioning scheme change sometime between GB and JB? How does (mobile) odin handle this?
immortalneo said:
On flashing stock firmwares, my custom kernel gets replaced by a stock one. So am sure there must be a kernel in a stock firmware.
Click to expand...
Click to collapse
Is it correct, that you use sammobile firmware with mobileOdin?
I just tried opening sammobile-XWLSE with it. According to mobileOdin manual, when opening a file it finds all partitions inside it, and puts the filename next to partition names. However, I see it only finding "System" partition. "Kernel" says "None". How does it look on your device?
Screwed it up...
Finally I got courage to flash anything. Used MobileOdin, firmware from sammobile (from which only factoryfs got loaded), and PhilZ kernel.
Program reported success, but devise didn't want to start afterwards. It showed "Samsung Galaxy GT-I9100" with yellow triangle, then short pause, same again. Then PhilZ recovery menu. Reboot, shutdiwn and start again ended up in recovery each time.
I had CWM-backup from original system. Tried to restore factoryfs from this one. Seemingly succeed, but nothing starts anyways. Now not even recovery. Still available via button combination though, as well as download mode.
It would be really great if somebody can give a hint how to get this thing into working state again...
If you can get into recovery, and ur not on 4.0.4, do a factory reset and wipe cache partition.
If you can only get into Download mode, flash a stock firmware via Odin.
"To err is human, to forgive is divine"
Sent from my SGS II
What I actually did was to completely restore from CWM backup. Apparently first time i only restored system partition, and it wasn't enough. Complete restore returned my old system. I'm glad it worked.
As for your suggestion with Odin: like I say, I don't have access to windows. On the other hand "to flash the stock firmware" is what I'm trying to do from the very beginning, and can't manage so far.
Okay, finally got it up and running.
The major problem was that my archive-decompresser got only part of .tar.md5 out of sammobile-zip. No idea why. As a result I saw only some of the actual firmware contents, not all of them. So disregard my questions about "why is there no kernel inside". It's all there.
I don't understand, how those .tar.md5 passed checksum-check in mobileOdin.
After I got that sorted there were some others, but everything worked fine after some tries. For one, I could not use mobile Odin anymore, and heimdall-frontend gave errors. Console version worked fine.
Thanks for your help!
No wonder the kernel went missing!
Thanks for sharing mate! Happy you got it sorted out!
Please add [SOLVED] to the title of ur post.
"To err is human, to forgive is divine"
Sent from my SGS II
Related
So my friend has been using this site for over a year rooting his HTC Desire and said I should look into rooting my S2, and because the S2 is quite a popular phone it should be an easy hack. So I obliged and downloaded Odin and used this file.\CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4\CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.tar.
I put my phone into download mode, followed every step perfectly and it said the download was a success/pass. Now when I try to boot my phone back up it goes to the Samsung Galaxy S2 GT-I9100 screen, with a yellow triangle with an ! in the middle. And it wont boot anymore from there.
If this is an easy fix, or if there's an easy way to do this, I apoligize I'm a phone noob. Thanks for any help.
JHolwell said:
So my friend has been using this site for over a year rooting his HTC Desire and said I should look into rooting my S2, and because the S2 is quite a popular phone it should be an easy hack. So I obliged and downloaded Odin and used this file.\CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4\CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.tar.
I put my phone into download mode, followed every step perfectly and it said the download was a success/pass. Now when I try to boot my phone back up it goes to the Samsung Galaxy S2 GT-I9100 screen, with a yellow triangle with an ! in the middle. And it wont boot anymore from there.
If this is an easy fix, or if there's an easy way to do this, I apoligize I'm a phone noob. Thanks for any help.
Click to expand...
Click to collapse
1. make sure you're in the right forum for your device, and used the right file. What is your model number? (printed on the label under the battery)
2. where did you get that file? (CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4)
3. did you make a note of what your original kernel version was before you began? (this may be too much to hope for)
ctomgee said:
1. make sure you're in the right forum for your device, and used the right file. What is your model number? (printed on the label under the battery)
2. where did you get that file? (CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4)
3. did you make a note of what your original kernel version was before you began? (this may be too much to hope for)
Click to expand...
Click to collapse
1.GT-I9100M
2.I followed this topic(post 5, im with bell). http://forum.xda-developers.com/showthread.php?t=1193695. Then i googled the firmware and downloaded from here. http://hotfile.com/dl/133784983/242e8de/CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip.html(probably where I screwed up <_<)
3.And I have no idea, sorry.
Yes, I am curious about this too; could this thread be of use?
http://forum.xda-developers.com/showthread.php?t=1103399
Thanks a ton!
JHolwell said:
1.GT-I9100M
2.I followed this topic(post 5, im with bell). http://forum.xda-developers.com/showthread.php?t=1193695. Then i googled the firmware and downloaded from here. http://hotfile.com/dl/133784983/242e8de/CF-Root-SGS2_ZS_OZS_KG2-v4.1-CWM4.zip.html(probably where I screwed up <_<)
Click to expand...
Click to collapse
Yikes. That thread says:
CF-Root Thread: http://forum.xda-developers.com/showthread.php?t=1103399
We do not have a CF-Root version of our kernel so just flash any kernel using the instructions provided in the link and flash the stock kernel back (found below). Root will remain as well as the CWM app but you will loose clockwork mod recovery.
Click to expand...
Click to collapse
Which is very VERY vague, and is probably why it screwed up. You can't just flash ANY kernel - it has to be one close to the one you already have. For example, if you had ICS on the phone, and flashed an older Gingerbread kernel (which the one you downloaded is version KG2, is an older Gingerbread kernel build), then the phone wouldn't boot.
JHolwell said:
3.And I have no idea, sorry.
Click to expand...
Click to collapse
If you didn't know what version you had, then there really isn't a way to recover without flashing a whole firmware.
Download an I9100M firmware from http://samsung-updates.com/device/?id=GT-I9100M and flash that to get back to ICS. Then go back to the CF-root thread, and make sure to read the instructions in post 1. Pay particular attention to the part that says "Help! Which file do I use ?"
2.6.35.7-19100mugkkg2-cl371789dh1130.y00 (oo)@sep-48#2 . That is the default kernel for the phone
Joshua3109 said:
2.6.35.7-19100mugkkg2-cl371789dh1130.y00 (oo)@sep-48#2 . That is the default kernel for the phone
Click to expand...
Click to collapse
Only if the phone shipped with the UGKG2 build (you have one too many "k"s in there) of Android. (which isn't guaranteed).
Ok so I have that file downloaded, and I downloaded the correct file from that site. Now I'm trying to install the firmware onto my phone, but its in MD5 format, and not .TAR. I tried googling how to fix this but couldnt find anything, how would I go about changing the file so that Odin can pick it up?
JHolwell said:
Ok so I have that file downloaded, and I downloaded the correct file from that site. Now I'm trying to install the firmware onto my phone, but its in MD5 format, and not .TAR. I tried googling how to fix this but couldnt find anything, how would I go about changing the file so that Odin can pick it up?
Click to expand...
Click to collapse
Odin should pick up an md5. Mine does. Put it in the PDA box and leave everything else alone.
Okay it's back to how it was before I tried to hack my phone. Thanks for the help!
I still want to try rooting my phone, even though I failed pretty bad my first time. My Kernal is LD3 and when I went to the other topic to look for the file, they don't have it, is there a file for my kernal version?
JHolwell said:
I still want to try rooting my phone, even though I failed pretty bad my first time. My Kernal is LD3 and when I went to the other topic to look for the file, they don't have it, is there a file for my kernal version?
Click to expand...
Click to collapse
If you don't want to worry about kernel versions, use this.
EDIT to add: according to this post, you can use LP7 for rooting LD3.
samsung-updates.com/device/?id=GT-I9100M
Error establishing a database connection
how do i can get that file?
i have same problem whit yeallow triangle and noo booting
i need help please
can anyone help me. I can't get passed the yellow triangle and I need help my Model: GT-I9100 SSN:I9100GSMH
I can't remember the kernel or anything. I can get into the recovery and the download things but I cant do nothing else
thanks for any help.
ITryTooHard said:
can anyone help me. I can't get passed the yellow triangle and I need help my Model: GT-I9100 SSN:I9100GSMH
I can't remember the kernel or anything. I can get into the recovery and the download things but I cant do nothing else
thanks for any help.
Click to expand...
Click to collapse
Details.. details mate..
Start with what rom/firmware u were on. What all u did that ended in the bootloop. Rooted or not.
"To err is human, to forgive is divine"
Sent from my SGS II
yellow triangle
immortalneo said:
Details.. details mate..
Start with what rom/firmware u were on. What all u did that ended in the bootloop. Rooted or not.
well i was on a 4.0.4 and the file that i uesd to root was ( Siyah-s2-v6.0b4.tar )
the root worked but then i downloaded a app then it kept on force closing so i pulled the battery out then i could only get to t-mobile screen then would crash. but now i cant even get to that.
Click to expand...
Click to collapse
ITryTooHard said:
immortalneo said:
Details.. details mate..
Start with what rom/firmware u were on. What all u did that ended in the bootloop. Rooted or not.
well i was on a 4.0.4 and the file that i uesd to root was ( Siyah-s2-v6.0b4.tar )
the root worked but then i downloaded a app then it kept on force closing so i pulled the battery out then i could only get to t-mobile screen then would crash. but now i cant even get to that.
Click to expand...
Click to collapse
Boot your phone to download mode. (volume down- home - power)
Download the latest Siyah Kernel (6.05b (the tar file)).
Start ODIN on your PC.
Press the PDA-button, and add the SiyahKernel file.
Connect your phone to a USB drive while it's on download mode.
Press "Start" on ODIN.
Now, if this doesn't work, download another version of ODIN. After trying all the versions, try all those versions again on a different USB port. If you STILL can't flash it, try another computer (and all the USB ports on that). If it still doesn't work, you probably have need for service.
I did this on my phone yesterday, and ODIN 1.85 worked on (only) one of my USB ports, so by all means, start with 1.85 first.
Click to expand...
Click to collapse
oh okay thanks for the help
November13 said:
ITryTooHard said:
Boot your phone to download mode. (volume down- home - power)
Download the latest Siyah Kernel (6.05b (the tar file)).
Start ODIN on your PC.
Press the PDA-button, and add the SiyahKernel file.
Connect your phone to a USB drive while it's on download mode.
Press "Start" on ODIN.
Now, if this doesn't work, download another version of ODIN. After trying all the versions, try all those versions again on a different USB port. If you STILL can't flash it, try another computer (and all the USB ports on that). If it still doesn't work, you probably have need for service.
I did this on my phone yesterday, and ODIN 1.85 worked on (only) one of my USB ports, so by all means, start with 1.85 first.
Click to expand...
Click to collapse
i tryed all the things you said to do and i get passed the triangle but then it just stay's on this different screen ?
Click to expand...
Click to collapse
ITryTooHard said:
well i was on a 4.0.4 and the file that i uesd to root was ( Siyah-s2-v6.0b4.tar )
the root worked but then i downloaded a app then it kept on force closing so i pulled the battery out then i could only get to t-mobile screen then would crash. but now i cant even get to that.
Click to expand...
Click to collapse
T-Mobile screen? U sure u have an I9100 and not a SGH T989?
Check under battery to be sure.
Siyah v6 is for JB mate. That's the reason things got messed up. For 4.0.4, you should have used Siyah v5.0.1.
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 07:21 AM ---------- Previous post was at 07:17 AM ----------
ITryTooHard said:
November13 said:
i tryed all the things you said to do and i get passed the triangle but then it just stay's on this different screen ?
Click to expand...
Click to collapse
Since u can flash successfully with Odin, simply flash the stock firmware for ur device and it should boot up without issues. I suggest u flash either 4.0.3 or 4.1.2.
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 07:24 AM ---------- Previous post was at 07:21 AM ----------
November13 said:
ITryTooHard said:
Boot your phone to download mode. (volume down- home - power)
Download the latest Siyah Kernel (6.05b (the tar file)).
Start ODIN on your PC.
Press the PDA-button, and add the SiyahKernel file.
Connect your phone to a USB drive while it's on download mode.
Press "Start" on ODIN.
Now, if this doesn't work, download another version of ODIN. After trying all the versions, try all those versions again on a different USB port. If you STILL can't flash it, try another computer (and all the USB ports on that). If it still doesn't work, you probably have need for service.
Click to expand...
Click to collapse
Like I already mentioned, Siyah v6 is for stock JB. The OP has 4.0.4, so flashing the latest Siyah v6 will still result in bootloop.
And the other steps you mentioned are for when Odin flash fails. I don't think the OP has mentioned Odin flash failing yet. He has only told of being stuck in a bootloop.
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
Click to expand...
Click to collapse
i dunno what to do now
every time i try do the odin it keeps failing is there away around this or shall i just throw the phone away ?
I updated my Galaxy S2 GT-I9100 to Jelly Bean via Kies. It worked fine for 10 days and yesterday night when I was switching Wi-Fi off, it hanged. So I pulled off the battery and after that it got stuck on boot screen. I am able to get in to download mode but not to recovery mode. I flashed the phone with Official JB rom available at sam mobiles using Odin but the problem still persists. Can someone help me in reviving my phone
Had u done factory reset after flashing the update?
Since u have download mode only, ur only option would be to flash a stock firmware via odin.
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
Had u done factory reset after flashing the update?
Since u have download mode only, ur only option would be to flash a stock firmware via odin.
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
When I updated for first time using Kies, i didn't. After flashing via Odin, I can't factory reset as it's not going to recovery mode. I used stock firmware available at Sam mobiles only to flash. Please guide me what to do next?
konquerror said:
When I updated for first time using Kies, i didn't. After flashing via Odin, I can't factory reset as it's not going to recovery mode. I used stock firmware available at Sam mobiles only to flash. Please guide me what to do next?
Click to expand...
Click to collapse
Sorry, read ur first post really fast. Didn't notice that u already flashed stock JB!
If u can't get recovery mode, flash a stock ICS 4.0.3 firmware. Then, get into recovery and factory reset. That should help u boot.
Once you do that, you can either flash JB using odin again, or u can root the ICS and use Mobile Odin app to flash JB.
"To err is human, to forgive is divine"
Sent from my SGS II
Or just flash any rooted jb kernel and wipe/reset in recovery then flash stock jb again
Sent from my GT-I9100 using xda premium
immortalneo said:
Sorry, read ur first post really fast. Didn't notice that u already flashed stock JB!
If u can't get recovery mode, flash a stock ICS 4.0.3 firmware. Then, get into recovery and factory reset. That should help u boot.
Once you do that, you can either flash JB using odin again, or u can root the ICS and use Mobile Odin app to flash JB.
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
Thanks I will try that. However I searched the forum and according to this thread:
http://forum.xda-developers.com/showthread.php?t=1457458
I might have NAND rw corruption. This guide doesn't have instructions for Jelly Bean. Can you guide me how to recover a possible JB SGS2 with NAND rw corruption?
stopro said:
Or just flash any rooted jb kernel and wipe/reset in recovery then flash stock jb again
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Can you please point me to correct rooted JB kernel and instructions for the same?
stopro said:
Or just flash any rooted jb kernel and wipe/reset in recovery then flash stock jb again
Click to expand...
Click to collapse
Or that..
(Now why didn't I think of that!)
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------
konquerror;40315112according to this thread:
[url said:
http://forum.xda-developers.com/showthread.php?t=1457458[/url]
I might have NAND rw corruption.
Click to expand...
Click to collapse
Its too early to say that mate. If all other attempts fail, we will try that guide.
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
konquerror said:
Can you please point me to correct rooted JB kernel and instructions for the same?
Click to expand...
Click to collapse
Download Siyah v6 beta 5 (tar file) from www.gokhanmoral.com and flash it via Odin (select it as PDA).
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
Or that..
(Now why didn't I think of that!)
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 05:45 PM ---------- Previous post was at 05:43 PM ----------
Its too early to say that mate. If all other attempts fail, we will try that guide.
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
Download Siyah v6 beta 5 (tar file) from gokhanmoral and flash it via Odin (select it as PDA).
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
Thanks a lot. Will try and let you know the result
After flashing with Siyah Kernel, I was able to go in to recovery mode. I did a factory reset and wiped the cache after which my phone started working fine. Thanks a lot people for your help.
konquerror said:
After flashing with Siyah Kernel, I was able to go in to recovery mode. I did a factory reset and wiped the cache after which my phone started working fine. Thanks a lot people for your help.
Click to expand...
Click to collapse
Ur welcome! Thanks should go to @stopro though!
Please add [SOLVED] to the title of ur post.
"To err is human, to forgive is divine"
Sent from my SGS II
s2 stuck on startup screen
I got my galaxy s2 in january prepaid thru walmart straighttalk. Yesterday it got stuck on startup screen. The reset option will not work...is there anything else I can do? Thanx
Aphrodite
Wot rom u r on
Sent from my GT-I9100 using xda premium
Just quickly, if you got it on January, are you still under warranty? If you are, save yourself some trouble and take it back under warranty, assuming you've never messed with (rooted etc) your phone? There's things to try but warranty is there for a reason.
Sent from a galaxy far, far away
Had the same problem, seemed like a NAND corruption to me on my phone since the progress bar on the main boot logo screen was slow and was stuck half the way, which otherwise used to slide pretty quickly, indicating that the phone is having trouble reading from its NAND flash.
Before the corruption I was running RootboX 4.1 with Dorimanx Kernel 9.38.
Was all prepared to do the ODIN flashing with latest firmware for my country, kernel and possibly a PIT flash with repartition , if in case else would have failed.
However to my skeptic mind a pretty safe suggestion read here somewhere on a thread, appealed for a while, and I was amazed to see the power of hunches.
Someone reported to have restored back his set, by SIMPLY taking the battery out and leaving it naked overnight. I did the same thing last night, and guess what, sipping the morning tea, I inserted the battery again and VOILA, its ALIVE....its ALIVE.....like any other FRANKENSTEIN defying all boundaries of logic.
So someone else in the same fix, should try it at first before jumping in the ODIN waters.
Lets see for how long does it lives, which TOUCHWOOD should be for a long time, till i save enough to a buy the S4 or Note3.
Cheers.
S2 stuck at boot screen. need some help
Hello everybody,
I'm new here and came here because of a problem with my Samsung S2.
Never rooted, original updates with KIES, android 4.1.2
Two days ago i woke up and the s2 was off and didn't restart. At first it was in a splash screen loop and i could get in recovery mode tried the factory reset but it got stuck in there to... After waiting for about an hour i pulled out the battery to restart it but then it didn't get any further than the boot screen. Couldn't get into recovery mode but could get into download mode. Searched the android forums for hours and came across this post. followed several possible solutions but now i'm stuck again, nothing did the trick... Hope you guys are willing and able to help me solve this thing.
What have i done so far:
Downloaded the original firmware for my device: I9100XWLSW_I9100XXMS3_I9100ITVLS2_HOME.tar
Downloaded ODIN v3.07
Updated KIES and after restarting pc stopped all the kies processes.
Started Odin without cable connected to the S2, selected the firmware, got the S2 into download mode, connected S2 to the Pc.
Odin recognizes the comport pressed start and can see that Odin gets stuck at NAND write start!!. first it says boot in white and after about 5min got the red fail.
Tried it different times with the same result.
Went on reading this tread and cam across the possible solution to firs flash kernel (in my case i've used Siyah-s2-v6.0b5.tar), go to recovery mode, factory reset and wipe and then flash original firmware again.
Same problem ODIN gets stuck at NAND write start!!
Detail: on the S2 during all this i''ve never seen a progress bar or any other movement, However although every attempt failed, when i go in to download mode now it says
Custom binary download: yes (2 counts) -my attempts to flash kernel with Siyah-s2-v6.0b5.tar
Current binary:custom
And at the boot screen i get the yellow triangle...
I'm stuck! :silly:
Any help would be very much appreciated!
Made some screenshots:
So because this is my first post they are attached to this post.
You've been pretty thorough so far. Search for Hopper 8's 'Odin troubleshooting' thread, try all the stuff in the thread, particularly flashing the 3 part firmware. That's the only way you're fixing it yourself. Could be NAND corruption, but most of these cases are fixed by perseverance (for example, the first 7 times you try flashing stock firmware it doesn't work, but the 8th flash does for whatever reason), sometimes it's something really small/obvious tripping you up that can be a bit hard to figure out if you've trying to fix it for hours/days. Hopper's thread should enable you to try everything you possibly can to fix it.
MistahBungle said:
You've been pretty thorough so far. Search for Hopper 8's 'Odin troubleshooting' thread, try all the stuff in the thread, particularly flashing the 3 part firmware. That's the only way you're fixing it yourself. Could be NAND corruption, but most of these cases are fixed by perseverance (for example, the first 7 times you try flashing stock firmware it doesn't work, but the 8th flash does for whatever reason), sometimes it's something really small/obvious tripping you up that can be a bit hard to figure out if you've trying to fix it for hours/days. Hopper's thread should enable you to try everything you possibly can to fix it.
Click to expand...
Click to collapse
Thanks MistahBungle... I'll go and try that... I'll reply here if it worked.
http://forum.xda-developers.com/showthread.php?t=2345831. If it doesn't, it's a motherboard replacement job. I very much recommend you flash as many stock firmwares you can download (10, 20, whatever), because the alternative is expensive/means getting a new phone.
Last night I installed CWM 6.0.2.9 on my phone. Now it will no longer boot.
I tried downgrading to CWM 6.0.2.7, but the result is the same. My phone is otherwise stock, with the most recent 4.1.2 firmware.
At its' current state, I can enter CWM recovery, and I have tried doing a factory reset. It didn't help.
Is this normal? Shouldn't the original firmware work with the CWM recovery?
How to fix this:
If all else fails, will I be able to restore my phone back to working condition using ODIN and an original firmware? If so, can I use any original firmware, or must it be region specific? I live in Norway,so I might have a nordic version, but it's unbranded.
Is it likely that the CWM is working fine, and all I have to do now is to upload a custom rom? If so, can I do this through ODIN? I installed CWM while waiting for the rom to download, hence I don't have it on the SDCARD partition in the phone, and I have no way of getting it there...
Which variant of the S2 do u have?
Which guide did u follow to install CWM?
As long as u can get into Download mode, you should be able to flash a stock firmware and get ur phone up and running!
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
Which variant of the S2 do u have?
Which guide did u follow to install CWM?
As long as u can get into Download mode, you should be able to flash a stock firmware and get ur phone up and running!
Click to expand...
Click to collapse
I have the original S2 GT-i9100. It was bought in Norway, unbranded.
I'm not sure which guide I followed. I've had about 100+ web pages open since last night trying to find a solution, so finding back by looking through browser history is pretty useless.
I did as follows:
1. enable USB debug mode on phone, let windows install drivers
2. kill kies process
3. run odin 3.04
4. boot phone into recorvery
5. connect USB
6. in odin: load file (GT-I9100_JB_ClockworkMod-Recovery_6.0.2.7.tar) into PDA section
7. auto reboot and f. reset time was enabled by default. clicked start. completed without errors.
Should I have rooted the phone first? I'm very interested to figure out why this is not working.
Am I safe to install ANY stock firmware, or should I get a specific one?
Visit this thread. .....
http://forum.xda-developers.com/showthread.php?t=1877270
And download the odin flashable tar version of the kernel that matches your region and firmware version.....
You'll root your phone and install a (hopefully) fully compatible touch CWM in the process......
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
keithross39 said:
Visit this thread. .....
http://forum.xda-developers.com/showthread.php?t=1877270
And download the odin flashable tar version of the kernel that matches your region and firmware version.....
You'll root your phone and install a (hopefully) fully compatible touch CWM in the process......
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Click to expand...
Click to collapse
Thanks Keith!
By the time I got your reply I already found a solution.
I used a file called Siyah-s2-v6.0b5.tar, flashed it as PDA through Odin, and problem solved.
It can be found here:
http://d-h.st/frK
Damn, this was nerve-wrecking! At least now the phone is working again. Thanks again for your help!
Glad you got it sorted fella....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
keithross39 said:
Glad you got it sorted fella....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Click to expand...
Click to collapse
@keithross39:
Any ideas on why the device went into bootloop after flashing CWM tar? I have seen others have the same issue. Is that tar file a kernel?
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 07:30 PM ---------- Previous post was at 07:30 PM ----------
@OP:
Please add [SOLVED] to the title of ur post.
"To err is human, to forgive is divine"
Sent from my SGS II
Ok....my best guess (and it is ONLY a guess)......
The OP asked if he should have rooted first....
I'd say that played a big part in the bootlooping.
The guides I've read for modifying two of my phones state that rooting should take place before the installation of CWM.
And I doubt the .tar file was a kernel.......afaik CWM is flashed independently. ....even if it's included with siyah, dorimanx or philz....I'd guess that the mentioned kernels get flashed first, then the kernels themselves (because they provide root access) flash the included CWM.......
And I think that the .tar extension is simply a designation for any file that is suitable for use with Odin (cmiiw). I've not seen it being used anywhere else......
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
I too thought that it must be the lack of root that is causing this issue. And thanks for the suggestion on how Siyah/Dori probably work. It makes sense now. :thumbup:
'tar' is actually short for 'tarball', AFAIK. Its a type of compressed archive used in Linux. Most softwares on Linux come as tar files.
"To err is human, to forgive is divine"
Sent from my SGS II
Hi Everybody
First of sorry for what might seem some obvious questions to you all, sorry!
I've recently got an S2 and would like some guidance on rooting my phone if possible.
I'm a bit weary as to what method is best, since I've got the BrickBug version also some help on the actual files to use and the sequence of events would be great or any links also appreciated.
My Phone details are:
Model Number: GT-I9100
Android Version: 4.0.4
Baseband Version: I9100XXLQ6
Kernel Version: 3.0.15-I9100XWLPT-CL941023
[email protected]#3
SMP PREEMPT Fri Jul 27 18:08:15 KST 2012
Build Number: IMM76D.XWLPT
Or using the *#1234# method:
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100CPWLPA
As far as I can work out there appears to be two common methods for rooting.
#1 Use the Odin program and flash the Siyah Kernel S2-v4.1.5.tar file.
So does this method basically root the phone and also provide a permanent recovery utility (CWM) built in and a safe kernel, making it safe from the brick bug?
The only down side of this method that I can see, unless I've missed something is the Custom ROM Counter and a Yellow Triangle thing on boot-up. Which can be got rid off, by installing an app from the Play Store?
Or:
#2 [GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel
Download this File first and put in your SDCARD
- MOD EDIT: Links removed as its the unsafe version...
or download zip from clockworkmod.com/rommanager
- 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
Not sure what to download from the first link. So basically does this mean I download the recovery-clockwork-4.0.1.5-galaxyS2.zip or the recovery-clockwork-5.8.1.5-galaxyS2.zip version from the clockworkmod link? Is there a specific one you would recommend what's the difference?
Or does it mean the Siyah-s2-v4.1.5-CWM.zip from the SiyahKernel site?
Place the SU-Busybox-Installer.zip and the Siyah-s2-v4.1.5-CWM.zip (or one of the other two zips mentioned above).
Then Reboot into stock Recovery mode.
Then choose Apply Update From External Storage.
Then choose the recovery-clockwork-4.0.1.5-galaxyS2.zip or recovery-clockwork-5.8.1.5-galaxyS2.zip one. Then wait until the selected new recovery appears.
Or is it the Siyah-s2-v4.1.5-CWM.zip?
Then from the new recovery screen select Install Zip from SDCard or External SD.
Choose and Install the SU-Busybox-Installer.zip.
Then Reboot from recovery screen options.
This method will root the phone (SU-Busybox-Installer.zip.) and also provide a permanent recovery utility (Siyah-s2-v4.1.5-CWM.zip) and a safe kernel (Siyah-s2-v4.1.5-CWM.zip), making it safe from the brick bug?
Which method is the safest and are there any pros and cons for both.
Method 1 Seems simpler but you've got a ROM counter and a yellow triangle thing?
Method 2 I read somewhere that the phone started having severe battery issues after rooting very high current drain?
MudSlug said:
Android Version: 4.0.4
PDA: I9100XWLPT
PHONE: I9100XXLQ6
CSC: I9100CPWLPA
#1 Use the Odin program and flash the Siyah Kernel S2-v4.1.5.tar file.
So does this method basically root the phone and also provide a permanent recovery utility (CWM) built in and a safe kernel, making it safe from the brick bug?
The only down side of this method that I can see, unless I've missed something is the Custom ROM Counter and a Yellow Triangle thing on boot-up. Which can be got rid off, by installing an app from the Play Store?
Click to expand...
Click to collapse
Since u have already done ur homework, I will take the time to answer all ur questions instead of the usual "flash siyah via odin".
The first method is the easiest. And for ICS 4.0.4, use the latest Siyah v5.0.1 kernel instead. This will ROOT ur phone, give u a permanent CUSTOM RECOVERY and keep u SAFE from the Brickbug.
Yes, this will trip ur counter, which can easily be reset using Triangle Away app.
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 07:51 AM ---------- Previous post was at 07:43 AM ----------
MudSlug said:
#2 [GUIDE] ROOT/UNROOT Stock ICS Firmware without flashing unsecure kernel
Not sure what to download from the first link. So basically does this mean I download the recovery-clockwork-4.0.1.5-galaxyS2.zip or the recovery-clockwork-5.8.1.5-galaxyS2.zip version from the clockworkmod link? Is there a specific one you would recommend what's the difference?
Or does it mean the Siyah-s2-v4.1.5-CWM.zip from the SiyahKernel site?
Place the SU-Busybox-Installer.zip and the Siyah-s2-v4.1.5-CWM.zip (or one of the other two zips mentioned above).
Then Reboot into stock Recovery mode.
Then choose Apply Update From External Storage.
Then choose the recovery-clockwork-4.0.1.5-galaxyS2.zip or recovery-clockwork-5.8.1.5-galaxyS2.zip one. Then wait until the selected new recovery appears.
Or is it the Siyah-s2-v4.1.5-CWM.zip?
This method will root the phone (SU-Busybox-Installer.zip.) and also provide a permanent recovery utility (Siyah-s2-v4.1.5-CWM.zip) and a safe kernel (Siyah-s2-v4.1.5-CWM.zip), making it safe from the brick bug?
Click to expand...
Click to collapse
The 2nd method involves flashing a TEMPORARY custom recovery using ur stock recovery.
This temporary custom recovery can then be used to either
-simply root ur device without a permanent custom recovery (by flashing SU-Busybox-Installer.zip), or
-root with a permanent custom recovery (by flashing Siyah zip).
For this, u can use either recovery-clockwork-4.0.1.5-galaxyS2.zip or recovery-clockwork-5.8.1.5-galaxyS2.zip. It doesn't matter which.
The siyah zip however cannot be flashed in stock recovery.
"To err is human, to forgive is divine"
Sent from my SGS II
---------- Post added at 08:00 AM ---------- Previous post was at 07:51 AM ----------
MudSlug said:
Which method is the safest and are there any pros and cons for both.
Method 1 Seems simpler but you've got a ROM counter and a yellow triangle thing?
Method 2 I read somewhere that the phone started having severe battery issues after rooting very high current drain?
Click to expand...
Click to collapse
Method 1 - easier and safer too (if u are new to flashing and stuff).
Method 2 - risk of brickbug because it uses temporary CWM recovery.
Rooting by itself doesnot cause issues like high battery drain or whatsoever. It could either be caused by some root apps that the user installed, or it could be due to the custom kernel used to root.
I hope I was able to answer all ur questions.
"To err is human, to forgive is divine"
Sent from my SGS II
Thank you immortalneo for your reply and sorry for my late reply!
I've installed the Kies program for backups and the drivers required for Odin.
Also I've got Odin3-v1.85 as recommended by the masses.
Odin does seem to be the easiest method and the one I'll probably opt for.
Reading about the two versions of kernel the SiyahKernel S2-v4.1.5 and SiyahKernel S2-v5.0.1.
It seems that most people prefer to use the S2-v4.1.5 due to better battery life and one mentioned that S2-v4.1.5 is for ICS and the S2-v5.0.1 is better for JB? This is in retrospect to the post's dates and to the there release dates of v4.1.5, 8th Sept 2012 and v5.0.1,10th Nov 2012 that majority of opinions is to use v4.1.5? Is there any major difference, the release notes are way above my comprehension.
Do these new kernels have any real noticeable affect from a phone users point of you as to the way the phone functions, speed, battery life etc (See below)?
Also, I was all set for having ago and had a look on YouTube as some people suggested. The nearest matching video I could find was by Zedomax guide of How to Root Galaxy S2! [Easiest Method]. This method seems identical to guides that I find here. A hell of a lot comments are negative and varied from:
" wont start up, it shows the exclamation mark in the yellow triangle", "blank screen", " rooting worked but I can't copy anything to my phone now", "phone wont start up", "menu button and back button have become unresponsive", "camera no longer work". etc etc?
Though it does seem strange that after 84,517 views he has got 529 likes and only 21 dislikes?
So I'm a bit weary now.
Any ideas as to what could've went wrong for them? Or any confidence building ideas greatly appreciated.
Look forward to any replies.
MudSlug ~~~"
...
MistahBungle said:
Flash the Odin version of a pre-rooted custom kernel in order to root your phone. It takes anything 'dangerous' completely out of the equation, and we seem to get a lot of people on here having problems after they've flashed temporary CWM (possibly simply just because they're n00bs, but, anyways). In other words, it saves stuffing around. Siyah is a good choice, but obviously don't have to stick with it after you've flashed it & decided on a rom/other kernel to flash.
You end up with a rooted phone + CWM, from there you can flash whatever you want/backup/restore until your heart's content.
Click to expand...
Click to collapse
Thank you for the quick reply MistahBungle.
The Odin method is the one I would go for. Just not sure as to what version of the Siyah kernel to go for v4.1.5 or v5.0.1 due to conflicting posts?
Also the Odin method for flashing a Siyah kernel as stated on this site seems the same as the aforementioned YouTube method and all the negative comments and problems have mad me a bit weary! As there seems to be a lot of screwed up phones during and after the process.
Could this be due to the BrickBug kernel somehow? Kind of putting up a fight before being replaced?
I'm a cautious fellow by nature....
Mainly because it's a new phone and I don't want it turned into a new paperweight!
MudSlug ~~~"
...
MistahBungle said:
Problems happen when you're careless/don't know what you're doing. I've seen <10 people on here in 18 mths (out of many thousands) brick phones thru 'bad luck'.
Not sure which version of Siyah as I haven't used it/run that version of Android for ages. Should be in the first post of the Siyah thread which versions are compatible with whatever version of Android (I'd need to search myself to find out, and you're capable of doing that). The worst thing that can happen if you flash a wrong version of Siyah is your phone won't boot properly, which is easily recoverable by flashing the right version (Unless you're one of those 0.000001% of people who have a bad flash full stop).
In all honesty (and I say this to everyone who says what you've said), if you're that worried about what may/may not happen to your phone, leave it stock & enjoy it. Simple. There is no known way you can completely remove all risk from flashing. The best you can do is know what you're doing before you do it (which you've done), which makes that risk very very small.
Click to expand...
Click to collapse
Thank you MistahBungle.
Off topic: I've installed the full version of PowerAmp on my phone. But it doesn't seem to show any album art work any ideas regarding this anyone? I've used it on my previous phone without any problems, I've tried the obvious things from the settings menu, without any luck!
Off topic: I've installed the full version of PowerAmp on my phone, but it doesn't show any album art! I've used it before on my previous phone without any problems and tried various options in the settings but without any luck. Any ideas anyone?
I'll have ponder as to what to do, root or not to root! Now should I flip a coin or ask the mystical 8-ball
Hmm, decisions, decisions.
MudSlug ~~~"
There is another option......
Flash a compatible PhilZ kernel....
This is as simple as flashing a zip in stock recovery....you'll avoid the flash counter issue, and you'll have permanent touch CWM at the end of it. ...Odin is NOT required for this method....
Visit the thread....
http://forum.xda-developers.com/showthread.php?t=1877270
research which kernel matches your firmware, download the zip (not tar) and flash....simples
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
keithross39 said:
There is another option......
Flash a compatible PhilZ kernel....
This is as simple as flashing a zip in stock recovery....you'll avoid the flash counter issue, and you'll have permanent touch CWM at the end of it. ...Odin is NOT required for this method....
Visit the thread....
http://forum.xda-developers.com/showthread.php?t=1877270
research which kernel matches your firmware, download the zip (not tar) and flash....simples
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Click to expand...
Click to collapse
Thank you keithross39.
I'll have a look into that method as well. I'm suspicious that it's the BrickBug on the ICS stock that's causing these problems for the people on YouTube and it's a matter of luck as to if it works or not on ICS with the dodgy kernel.
Thanks again for the reply....
~~~"
Sorry Guys just another noob question!
Do I have to put the phone into USB debugging mode to use Odin?
It doesn't seem to be mentioned in the YouTube video and in some other posts?
Thank you for any replies in advance.
~~~"
MudSlug said:
Thank you keithross39.
I'll have a look into that method as well. I'm suspicious that it's the BrickBug on the ICS stock that's causing these problems for the people on YouTube and it's a matter of luck as to if it works or not on ICS with the dodgy kernel.
Thanks again for the reply....
~~~"
Click to expand...
Click to collapse
The general advice if you're running 4.0.4 is NOT to wipe ANYTHING while you're on the stock kernel. Once you've flashed your safe kernel (either siyah or philz) brickbug is no longer an issue. All you have to decide is do you want to use Odin or the stock recovery to do the job.....
IMO....Odin has the potential to be more risky......
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
MudSlug said:
Do I have to put the phone into USB debugging mode to use Odin?
It doesn't seem to be mentioned in the YouTube video and in some other posts?
Click to expand...
Click to collapse
Its not necessary to turn on USB debugging, because the Odin flashing is done in download mode.
Some people recommend turning it ON, but I have found that it makes NO difference at all.
"To err is human, to forgive is divine"
Sent from my SGS II
keithross39 said:
The general advice if you're running 4.0.4 is NOT to wipe ANYTHING while you're on the stock kernel. Once you've flashed your safe kernel (either siyah or philz) brickbug is no longer an issue. All you have to decide is do you want to use Odin or the stock recovery to do the job.....
IMO....Odin has the potential to be more risky......
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
Click to expand...
Click to collapse
Thanks again for your replies keithross39 and immortalneo
Yes, I was wondering if the majority of problems people were having was due to using Odin on the previous YouTube link?
I've found a good vid on YouTube by Babblingboolean (How to Root ICS Galaxy S2 and load CWM Recovery (GT-i9100 and GT-i9100M)).
This method uses: http://forum.xda-developers.com/showthread.php?t=1501719 by Rachmat3.
So in my case I guess the instructions go like this:
Download: recovery-clockwork-4.0.1.5-galaxyS2.zip and place in the phones SD. This will give me custom temporary recovery?
Download: Siyah-s2-v4.1.5-CWM.zip and place in the phones SD. This will give me a permanent custom recovery and asafe kernel free from the BrickBug and also root?
Power off phone then boot into stock recovery mode by Vol Up + Home + Power.
Then select Apply Update From External Storage option and find and select the recovery-clockwork-4.0.1.5-galaxyS2.zip
this will then install and open up the temporary CWM recovery.
Then from the open CWM recovery select Install Zip From SD Card option and find select the Siyah-s2-v4.1.5-CWM.zip. Then select reboot.
This will then replace the previous temporary recovery-clockwork-4.0.1.5-galaxyS2.zip?
Then all being well look for the SU app and the CWM app in app list or check with a market SU permissions app.
Q. Does it matter what SD location I put the two files in, phone SD or Ext SD?
Q. Then I assume it's ok to delete the two zip files from the phone after?
Sorry immortalneo if I'm paraphrasing you in your reply in post #2. I just don't want to **** this up!
If all goes well I'm thinking of trying out a JB Rom: DarkyROM HD v3.0 to get rid of some the bloatware.
Anyone had any experience of this ROM?
Hope someone out there can comment on the above method for rooting, safe, dodgy etc?
Thanks again for reading this and for any replies...
MudSlug ~~~"
MudSlug said:
Q. Does it matter what SD location I put the two files in, phone SD or Ext SD?
Q. Then I assume it's ok to delete the two zip files from the phone after?
Click to expand...
Click to collapse
Guess u have got it all figured out mate! :thumbup:
Since ur planning on flashing the temporary CWM using stock recovery, u MUST place those files in the EXTERNAL SD CARD.
And yes, u can delete the zips after ur done with them.
A word of caution while using a temporary CWM on 4.0.4:
Never wipe or format anything, nor do a nandroid restore while on temporary CWM! It will trigger the Brickbug!!
"To err is human, to forgive is divine"
Sent from my SGS II
This is the method I used to root my wife's S2. Her phone was confirmed to be at risk from the brickbug. The method worked well, but the CWM was temporary....meaning that it needed to be reflashed every time recovery was used to enable the CWM options to be used......bit of a pain, but workable.......
Edit....just read your post in it's entirety....flashing siyah afterwards will give you permanent CWM and root.....
But with your chosen procedure; you're flashing 3 zips....this seems to be a bit (forgive me) long winded, when with the PhilZ method, you just flash one.....
Sent from my Rooted, De bloated Stock JB powered S2 via PhilZ kernel and Tapatalk 2....
To be honest, I rooted my ICS using a temporary CWM.. I still have that zip in my phone even now!!
"To err is human, to forgive is divine"
Sent from my SGS II
immortalneo said:
Guess u have got it all figured out mate! :thumbup:
Since ur planning on flashing the temporary CWM using stock recovery, u MUST place those files in the EXTERNAL SD CARD.
And yes, u can delete the zips after ur done with them.
A word of caution while using a temporary CWM on 4.0.4:
Never wipe or format anything, nor do a nandroid restore while on temporary CWM! It will trigger the Brickbug!!
"To err is human, to forgive is divine"
Sent from my SGS II
Click to expand...
Click to collapse
Great thanks for the positive reply immortalneo.
Also thank you for checking my plan of attack and for the warning too. So it looks like I'm all set to give it ago then.
I'll see what other comments come in in the mean time before I make my charge.
Any other advice is always welcome too.
MudSlug ~~~"
Hi keithross39
Sorry I overlooked your reply, and thanks for the reply.
My plan was just to flash the two zips.
The 1st one was just to give me a temporary CWM recovery to allow me to flash the 2 nd Siyah v 4.1.5 kernel since apparently you can't flash Siyah from the stock recovery this would then give me a permanent CWM with root and safe from the brickbug.
Hopefully that's the correct way?
MudSlug ~~"
Sent from my GT-I9100 using xda app-developers app
Come to think of it, u can skip the first step (flashing temporary CWM) if u use Philz kernel instead of Siyah.
Its a safe kernel, which will root ur phone and install permanent CWM. And best of all, it can be directly flashed in stock recovery.
"To err is human, to forgive is divine"
Sent from my SGS II
Yippee! - I'm know Rooted.
Hi Guys
Just to let you all know that all went well and that I'm rooted now.
I used the Temporary CWM method by Rachmat3 with the aforementioned YouTube guide by Babblingboolean.
I wasn't entirely sure about Odin, since a lot of problems seem to stem from using it.
I thought before I should start that I should increase the screen time out, I didn't want to take the risk of it going off on me during a crucial moment and selecting something I shouldn't of in the recovery modes. Also using the standard recovery-clockwork-4.0.1.5-galaxyS2.zip version instead of the touch one, as I didn't want to select the wrong thing with my fat fingers!
The only snag I had was the location of the Siyah-s2-v4.1.5-CWM.zip. I couldn't find it on the external SD, so I just moved it to the internal.
Looking in my app tray, I now have two new apps: SuperSU v0.94 and CWM Manager v3.15.
I've also installed DroidWall which requires root access and seems to be working well.
I also ran the emmc bug checker app the result was: NO. Sane chip
Not sure as to whether this is actually checks anything kernel wise or just reads the kernel title?
Old Kernel Version: 3.0.15-I9100XWLPT-CL941023
[email protected]#3
SMP PREEMPT Fri Jul 27 18:08:15 KST 2012
New Kernel Version: 3.0.15-Siyah-s2-v4.1.5+
[email protected]) )
#49 SMP PREEMPT Tue Sep 11 12:21:30 PDT
2012
So I'll assume that I am safe?
Anyway a big thank you to: immortalneo and to keithross39 for your advice and patience.
I think I'll leave it for awhile before I start thinking about ROMs etc
Thanks again guys for your help and all the best.
MudSlug ~~"
Hello,
I had to downgrade my SG2 form JB to Gingerbread since I've lost my IMEI and I followed a guide that told me to do so.
As suggested, in Odin I specified the PDA file, the PHONE file and the CSC file, but I've forgotten to set the PIT file, so the phone hasn't been re-partitioned!
Anyway, the process completed correctly, I flashed again my IMEI number and the phone is working normally since a couple of days.
The fact that the device hasn't been partitioned could lead to issues?
Obviously, I'll upgrade again to JB as soon as possible using the "one archive" firmware.
Consider yourself lucky that you didn't use a pit file!
A word of advice: stay away from flashing pit files, unless you're phone is really messed up!
"To err is human, to forgive is divine."
Sent from my SGS II
immortalneo said:
Consider yourself lucky that you didn't use a pit file!
A word of advice: stay away from flashing pit files, unless you're phone is really messed up!
Click to expand...
Click to collapse
Ok, I understood
Thank you