Related
I've spent the last 2 days trying to fix my mistake. I have the GS2 ATT version, and I didn't realise there was a difference between that and the GTI9100 S2.
I wanted to give some tips I learned on how to recover your phone if you make this mistake.
First, here are some posts you'll want to look at:
http://forum.xda-developers.com/showthread.php?t=1286432 - Stock firwmware
http://forum.xda-developers.com/showthread.php?t=1285823 - Clockworkmod for the ATT
http://forum.xda-developers.com/showthread.php?t=1286192 - Cyanogenmod for our phones.
Using Odin and the stock firmware, you can recover your phone to a 95% working state. Once I got my stock firmware on there, I found that while making calls my phone made no sound, and the mic didn't work. The mic did work when I wasn't making calls though.
I reflashed the modem.bin file found on the stock firmware, not sure if its required but that is what I did first. Then, I unpacked the rooted stock firmware, and flashed JUST THE zImage file. After doing this, I rebooted, and my calls were working again.
After that, I installed the correct version of Clockworkmod, and then CM7 nightly. Now everything seems to be running great on my phone.
Hope this helps someone out there,
-Orbital
Good job thanx man.
Sent from my SAMSUNG-SGH-I777 using XDA App
Been awhile since I messed w/ android. I forgot about the different models myself until I realized I was spending half my day in the wrong section
Could you please explain the flashing of the CM Nightlies process to me? I can flash the signed base build but can't flash any of the added on nightlies...
Alucardis666 said:
Could you please explain the flashing of the CM Nightlies process to me? I can flash the signed base build but can't flash any of the added on nightlies...
Click to expand...
Click to collapse
In other words I can't flash the nightly builds like the latest 77 or any others for that matter.
Alucardis666 said:
In other words I can't flash the nightly builds like the latest 77 or any others for that matter.
Click to expand...
Click to collapse
Those are NOT for our version of the GS2, International only. Our version is here in the development forum.
Sent from my SGH-I777 using xda premium
Yes, it will return a status error 7 which means it's unmatched. Ask me how I know. I flashed international roms last night and used this fix to get me good again.
I flashed a KE7 I9100 build to my I777 and saw no ill effects other than incorrect capacitive button mapping. Which build did you flash? Did you make sure to wipe data factory reset afterwards.
So you are saying that you wre able to flash Euro ROMS and your phone booted just fine? Mine didnt boot at all. Did you flash the KERNEL for ATT on top of it ?
connexion2005 said:
I flashed a KE7 I9100 build to my I777 and saw no ill effects other than incorrect capacitive button mapping. Which build did you flash? Did you make sure to wipe data factory reset afterwards.
Click to expand...
Click to collapse
The simple thing would be to change out the sec_touchkey.kl with rootexplorer and take the sec_touchkey from system/usr/keylayout should fix the i9100 rom to work with the i777. Seeing as how this worked for the Captivate *i897* for jvr, jvs, and jvt darkyrom releases and I would assume that it would work.
daraj said:
So you are saying that you wre able to flash Euro ROMS and your phone booted just fine? Mine didnt boot at all. Did you flash the KERNEL for ATT on top of it ?
Click to expand...
Click to collapse
Personally I would think that you had a bad flash? Did you flash through Odin or CWM? From what I have been reading the gb bootloaders between the i777 and i9100 are different and I can see if you used a custom i9100 rom flashing via cwm could cause that. Since I am not too sure on the sgs2 if the differences between the euro models versus the carrier locked, the Kernel will not fix the button mapping, I learned this with the captivate when I switched over to using DarkyRom jvr and jvs builds since they were the most stable of GB for the i897 captivate. Plus if you are going to run a i9100 rom, I am sure the modem will not work with the att kernel. Especially if the situation with the cappy is any indication that att kernel needs att modem and i9000 kernel needs i9000 modem. I will be able to know more as soon as I get my i777 tomorrow.
HTH,
Charlie
Does anyone know how to remove the i9100 splash screen?
Google Talk Video does not work after updating to CyanogenMod 7 and back to stock rom. Any suggestion ?
spbluffmaster said:
Google Talk Video does not work after updating to CyanogenMod 7 and back to stock rom. Any suggestion ?
Click to expand...
Click to collapse
wipe data/factory reset
tried that three times... didnt help..
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
SO why do you say this flashes you back to 95%? Is there no 100% return to stock fix?
DiscipleDOC said:
Does anyone know how to remove the i9100 splash screen?
Click to expand...
Click to collapse
Speedy350z said:
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1311975
re: get rid of i9100 boot logo
Speedy350z said:
Did the same thing and made it back to ATT version and running CM7 for now. Still have an I9100 boot screen with a yellow logo. How do I get rid of that?
Click to expand...
Click to collapse
Use a download mode jig or flash entropy 512's stock TAR kernel with Odin from the link below.
http://forum.xda-developers.com/show....php?t=1286432
Good luck!
highaltitude said:
SO why do you say this flashes you back to 95%? Is there no 100% return to stock fix?
Click to expand...
Click to collapse
Some people need to wipe or also flash the modem for 100%.
Also, people who managed to flash a bootloader without hardbricking can't get back to stock with any confirmed method.
I have posted bootloader dumps, but no one has flashed them and I'm not messing with trying to flash them. They are dumps from my device and that is the ONLY guarantee I provide for them.
Entropy512 said:
Some people need to wipe or also flash the modem for 100%.
Also, people who managed to flash a bootloader without hardbricking can't get back to stock with any confirmed method.
I have posted bootloader dumps, but no one has flashed them and I'm not messing with trying to flash them. They are dumps from my device and that is the ONLY guarantee I provide for them.
Click to expand...
Click to collapse
i messed up and flashed an i9100 rom and am having the call prob u described. can i just flash the modem or stock rooted kernel and be back to 100%? if so do i use odin and do i need to check the box for repartition or anything like that? thx in advance!!!
Hi, i just flashed the Siyah Kernel v1.3.7beta for SGS3 on my SGS2.
I was using the CyanogenMod 9 RC1.
Now i'm stuck at the logo screen, the one with the name of the cellphone and can't get into Recovery mode, but i can get into the Download Mode.
How can i get my phone working again?
Any help will be aprecciated.
How about flashing a kernel (which supports CM9) for the correct device?
reflash the original kernal included in the CM9 thread that should restore your phone.
I'm now downloading the Samsung Drivers to try flash the Siyah Kernel for the SGS2 through the ODIN, i was just afraid that doing this could get the situation worse.
oinkylicious said:
How about flashing a kernel (which supports CM9) for the correct device?
Click to expand...
Click to collapse
Seriously, right? WTF?
Ahdriel said:
Hi, i just flashed the Siyah Kernel v1.3.7beta for SGS3 on my SGS2.
Click to expand...
Click to collapse
Why did you think this would even remotely work? Would you actually try flashing a kernel meant for an SGS2 on an SGS?
Well, maybe you would...
I don't thinked that would work, but i haven't noticed it was for the SGS3 T_T
It was my fault, i need to pay more attention.
Flashed the right Siyah Kernel through the ODIN, phone working now
Thanks for all the help and sorry about my stupidity.
You know, i'm a noob (the video in the register form says that D
Thanks, cya.
Hi all, and thanks for reading this tread,
I have some issues and I'm hoping someone here could help shed some light on.
I was on ICS 4.0.3 and avoiding 4.0.4 due to brickbug issues. but I guess I couln't resist anymore and decided to give it a try. I tried to stay far away from buggy kernel so I used mobile odin to flash I9100XWLPT plus siyah 3.5.2 on one go
the result was a failure however, kernel flashed but firmware wiped (S2 logo was appearing but nothing else / softbrick ?).
Then I said oh well its not (hard)bricked or anything so I decided to use odin to flash I9100XWLPT, than siyah. It went ok but I lost mtp connectivity, tried s3 ported ui... didn't fly as well . Maybe something wrong with siyah 3.5.2 I thought, so tried an older siyah which I did not have an issue with h4.0.3. Situation did not improve however.
Then I flashed my old 4.0.3 and wiped, all ok mtp ok, upgraded to 4.0.4, all go, mtp ok.
Flashed siyah 3.5.2, mtp fails again. Tried android's own factory reset (not the on the boot menu, one on the personalization menu). Ended up with soft brick again (no boot only charging animation and odin mode). Flashed 4.0.4 again.
But this trial and eror process is going more dangerous by the minute I guess, so I decided to ask for support.
Do I do anything wrong? I want to upgrade to 4.0.4 everything as close as possible to stock, plus root and tocuhwiz from s3. its not too much to ask I guess.
Any suggestions and any explanations are very welcome also,
I'll thank any useful comments
kind regards,
I have 4.0.4 since 4th July with its stock kernel and it works perfectly well, I upgraded from 4.0.3 but I never did any wipes just updated on top of 4.0.3 and booted the phone, rooted from chainfires CF root thread, try it that way, worked for me and still is working.
ag4751 said:
I have 4.0.4 since 4th July with its stock kernel and it works perfectly well, I upgraded from 4.0.3 but I never did any wipes just updated on top of 4.0.3 and booted the phone, rooted from chainfires CF root thread, try it that way, worked for me and still is working.
Click to expand...
Click to collapse
Thanks If all else fails I'll try that, but siyah is a good kernel and it seems to be more battery efficient too.
If its a problem I failed to check with siyah I can go 4.0.4 kernel way but it makes me nervous to run a buggy kernel.
emk2z said:
Thanks If all else fails I'll try that, but siyah is a good kernel and it seems to be more battery efficient too.
If its a problem I failed to check with siyah I can go 4.0.4 kernel way but it makes me nervous to run a buggy kernel.
Click to expand...
Click to collapse
Totally agree Siyah is good I used it on 4.0.3 but it seems to fail on 4.0.4 at the moment I have not actually tried the latest one so it may well be good but I am looking to upgrade to SG3 next week so just want to keep my phone going for the time being no more playing around with this one until I have my new one.
I am using LQ5 which is reported as the buggiest but I can honestly say I have not had any problems at all, battery life appears good enough to me, depends how much you use it I guess.
Try speedmod k30 kernel, completely safe, fast and battery efficient
Sent from my GT-I9100 using xda app-developers app
Hayth said:
Try speedmod k30 kernel, completely safe, fast and battery efficient
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Thanks, pardon me if I'm being paranoid but I just read a tread about nand corruption so, this isn't something like that I assume. (Odin flash failed and left me with soft brick out of the blue). Did not notice anything about siyah 3.5.2 either so the problem may be with my phone memory.
P.S Prior sentence reads as "Please prove me wrong"
I switched to speedmod kernel, and figured siyah had MTP problems with either 4.0.4 ics or 3.5.2
I asked same questions to those kernels' respective topics & thus this tread fulled it's purpose. Thanks kindly for anyone who read & replied
Sent from my GT-I9100 using xda app-developers app
Thread closed
Question answered, thread closed per OP's request
Hi, yesterday I bought a Galaxy S2 from AT&T and I'm a newbie at this. I want to know which is the best kernel for this phone without any brick possibilities.
Because I know the Siyah kernel, but I don't like it just because the Ying-yang symbol at booting process (That's really stupid) and I heard that the Jeboo Kernel leaves your phone with the triangle and without the possibility of booting the phone. Stuck at "Samsung Galaxy S2" and the triangle, so first of all... Is this true? (I mean the bug of the Jeboo Kernel)
And second, if it's true... Which kernel can I use?
I forgot to say...
The S2 has 4.1.2 Stock Unrooted.
Thanks in advance.
Sent from my Nexus 7 2012.
If I'm bad at English is because I'm from Argentina and I'm learning.
MlucianoEze said:
I forgot to say...
The S2 has 4.1.2 Stock Unrooted..
Click to expand...
Click to collapse
Stock unrooted. First you'll need to follow one of many threads detailing how to root the phone, and get cwm onto the i777. Then you'll need to read each kernel forum with recent support for the i777 to determine which is best suited for your needs (stability, rom choice, vanity, whatever). A few big names around here are AJK, jeboo (which works fantastically for it's designed application), and STI.
Happy flashing.
Ok. I'll do that.
Thanks.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
cyril279 said:
Stock unrooted. First you'll need to follow one of many threads detailing how to root the phone, and get cwm onto the i777. Then you'll need to read each kernel forum with recent support for the i777 to determine which is best suited for your needs (stability, rom choice, vanity, whatever). A few big names around here are AJK, jeboo (which works fantastically for it's designed application), and STI.
Happy flashing.
Click to expand...
Click to collapse
One thing more. If I leave the phone with stock unrooted kernel and I do a Factory Reset, will the phone brick?
Because of the eMMC bug with stock unrooted kernel.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
MlucianoEze said:
One thing more. If I leave the phone with stock unrooted kernel and I do a Factory Reset, will the phone brick?
Because of the eMMC bug with stock unrooted kernel.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
I'm pretty sure that stock 4.1.2 left the eMMC bug behind, the details are in creepyncrawly's repository. Creepyncrawly's signature is the best starting point for modding the I777.
MlucianoEze said:
Hi, yesterday I bought a Galaxy S2 from AT&T and I'm a newbie at this. I want to know which is the best kernel for this phone without any brick possibilities.
Because I know the Siyah kernel, but I don't like it just because the Ying-yang symbol at booting process (That's really stupid) and I heard that the Jeboo Kernel leaves your phone with the triangle and without the possibility of booting the phone. Stuck at "Samsung Galaxy S2" and the triangle, so first of all... Is this true? (I mean the bug of the Jeboo Kernel)
And second, if it's true... Which kernel can I use?
I forgot to say...
The S2 has 4.1.2 Stock Unrooted.
Thanks in advance.
Sent from my Nexus 7 2012.
If I'm bad at English is because I'm from Argentina and I'm learning.
Click to expand...
Click to collapse
MlucianoEze said:
One thing more. If I leave the phone with stock unrooted kernel and I do a Factory Reset, will the phone brick?
Because of the eMMC bug with stock unrooted kernel.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
To your initial question, there is nothing wrong with the Jebo kernel. It was, however, built specifically to go with the SHOstock3 rom. There are a variety of things that can cause the problem you stated. Flashing the wrong kernel for instance, as in flashing an ICS or Gingerbread kernel to a Jelly Bean system, will prevent the phone from booting. As far as the warning triangle at boot, that is caused by flashing a custom kernel using Odin or Heimdall. The screen can also be removed by flashing a stock kernel using Odin or Heimdall.
As far as the cap erase eMMC brick bug is concerned, that showed up in the ICS versions, and was possibly present in the 2.3.4 stock kernel. It may have been present also in the 2.3.6 stock kernel but there was never any direct evidence that it was. The 4.1.2 stock kernel is almost certainly safe. If it were my phone, I would not hesitate to perform a wipe data/factory reset with the 4.1.2 stock kernel.
creepyncrawly said:
To your initial question, there is nothing wrong with the Jebo kernel. It was, however, built specifically to go with the SHOstock3 rom. There are a variety of things that can cause the problem you stated. Flashing the wrong kernel for instance, as in flashing an ICS or Gingerbread kernel to a Jelly Bean system, will prevent the phone from booting. As far as the warning triangle at boot, that is caused by flashing a custom kernel using Odin or Heimdall. The screen can also be removed by flashing a stock kernel using Odin or Heimdall.
As far as the cap erase eMMC brick bug is concerned, that showed up in the ICS versions, and was possibly present in the 2.3.4 stock kernel. It may have been present also in the 2.3.6 stock kernel but there was never any direct evidence that it was. The 4.1.2 stock kernel is almost certainly safe. If it were my phone, I would not hesitate to perform a wipe data/factory reset with the 4.1.2 stock kernel.
Click to expand...
Click to collapse
Tour explained me very well, I understood everything! So thanks.
I will choose the kernel later.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
Finally managed to get my phone working again...But can someone tell me what went wrong?
I was running JB NEATROM with SIYAH 4.1.5 Kernel. Strde I flashed GS2Wiper and then Dorimanx 9.42 kernel, then flashed CM 10.2. Booted and found all normal. went back and flashed Gapps system showing google maps , playstore error . Unable to use phone. Tried back flashing CM 10.2 and Slimbeam Rom working fine, but when flashing Gapps system gets stuck in booting logo.
Finally flashed old siyah kernel 4.1.5 and flashed NEATROM and to my big relief system operational. I want to update to JB 4.3 .Can someone please advice
are you doing a wipe and factory reset after all the different roms you are trying?
You can often avoid bootloops by following the developers ibstructions to the letter.
Then again, if certain ROM-Kernel combo is known for having this issue you could check that same custom ROM thread for support/fix.
That's pretty much how all of these flashing works.
Sent from the little guy
gastonw said:
You can often avoid bootloops by following the developers ibstructions to the letter.
Then again, if certain ROM-Kernel combo is known for having this issue you could check that same custom ROM thread for support/fix.
That's pretty much how all of these flashing works.
Sent from the little guy
Click to expand...
Click to collapse
Gaston, good to see you mate! Been stuck in another book for a few weeks?
@ OP: Beautiful summary by gastonw right here. Read the OP of the thread 2-3 times before flashing. You want to make sure it's compatible with your device, other mods/firmware, and that you know what you're doing during the install process.
Hey hopper, no, it's the UFC era now
Sent from the little guy