Root it, use a safe kernel, enjoy.
Sent from my Samsung GT-i9100M
ROM Dilidroid UHLPS
Kernel Siyah 4.15
Sent from my Samsung GT-i9100M
ROM Dilidroid UHLPS
Kernel Siyah 4.15
I have a safe problem .. I am on 4.0.4 , how can i avoid bricking my phone ... plz help .. M glad i saw this thread before i rooted my phone ...thanks
Sent from my GT-I9100 using xda app-developers app
Anyone?
I have actually downloaded CF-Root For LPH But it says it has problems mounting SDCard partition, so i am confused about it... i have downloaded Siyah kernel , so i wanted to ask that if i flash Siyah kernel , i would have root access ?? i just want to get rid of some stupid apps i have on stock ICS 4.0.4
Plese, need help, tried to downgrade firmware from 4.0.4 to 4.0.3 using Odin and now i'm getting an error: android.process.acore has stopped, and can't really do anything.
is there anything I could do now or is my phone bricked?
Thanks in advance!
Flash Siyah then your rooted and can get rid of your stupid apps ... and besides that you are safe from the nasty, ugly, bugly brick bug
i am trying to flash SiyahKernel 5.0.1 (Latest Version) and tried 4.1.5 also but odin is giving me error saying that cannot open serial port and says FAILED
Kindly HElp .. i have tried changing the ports too
I have a emmc bricked S2 here. Has there been any development on this where you can fix it somehow?
I've read this post (I dont understand everything):
http://xdaforums.com/showthread.php?t=1667886
And this:
http://xdaforums.com/showthread.php?t=1900612
The state of my phone is that it's completely dead. I cant get odin to recognize it. It wont wake up when I plug in a usb-jig.. Nothing wakes the screen up. Any help would be very appreciated.
don't know if i am exactly right, but I've red somewhere that the only thing you can do now is to change phone's hardware (some kind of micro scheme, maybe processor or smth).
This my screen shot from got brickbugs? apps. Its shown my emmc chips got a brick bug. So, how to solve this and remove all brickbugs inside my chips. Any guide?
thanks for helping.
Sent from my GT-I9100 using xda premium
[B]Android Version[/B]: 2.3.3
[B]Baseband Version:[/B] I9100XXKE7
[B]Kernel Version:[/B] 2.6.35.7-I9100XWKF3-CL276555 root@DELL101 #2
If you've suffered from the Superbrick bug due to wiping on an affected kernel, it is not a corrupted partition table. It's low-level damage to the internal structures of the eMMC chip that is well known to be unrecoverable via JTAG. (Josh at mobiletechvideos.com apparently gets 3-5 devices damaged like this per day - he can't repair them.)My thought was to use riffbox to clear everything on the chip, the whole partition layout and such, then repartition the chip, install bootloader etc.
I wrote earlier that I'm able to tart the phone in recovery mode, only all I see onscreen is the s2 logo, but adb kinda works, it auto-reboots after appr. 3-4 minutes.
But I'm able to start several utils trought adb such as parted.
Only thing is that the phone hangs and reboots a minute later
If, and I say IF, it is just a corrupted partition table, and not phycial errors, it should be possible to recover from this error with jtag and nand wr directly, my experience with the riffbox is that It doesn't use recovery mode or download mode, it reads/writes the nand/emmc directly.
I found a video on youtube where they recovered a s2 with emmc bug, but lame ass me forgot to save the link, this is why I orderd a molex port, jtag adapter and such.
But off course, correct me if I'm wrong and you can prove something else
Well, you're apparently quite clueless, since the contacts at Samsung referenced in that post ARE the ones I'm talking to.what was the story youve sold to service center ???
Samsung and Google are well aware of this issue since May and are working on a fix since, but as they said fix is being developed and needs extensive testing and who knows how long could it take
so as much your initiative is ok ... it is completley useless as Samsung is well aware of chips that they ordered and witch of those are affected.
got also all the information on what causes this issue - now they just need to develop a stable working fix and push it public
or maybe they did their numbers and it came out that percent of the devices/mb/chips affected is ok to just handle it via service center repairs
oh, and they well know that it is a isue wit stock samung recovery or whatever you call it - the one that comes with firmware - so your source is hmm wierd
---------- Post added at 05:11 PM ---------- Previous post was at 05:01 PM ----------
ref -> plus.google.com/111398485184813224730/posts/21pTYfTsCkB
Ok but folks: what about the solution.... Is the affected chip version 0x19 upgradeable by software to 0x25 which is supposed to have the issue addressed? This is what I wish to know if is even possible
Sent from my GT-I9100 using Tapatalk 2