To my recollection, ktoonsez's releases went from 3.1 rc5 to 3.1 final.
Last edited:
In our community there are still CWM repack released for every leak, and it is still unsafe to wipe anything. And people still wipe. You guys are lucky to have a phone similar enough to intl sgs2 that you have source, but I think given what I've read here, I'd probably odin a GB kernel and wipe/flash from there.
Sent from my SPH-D710 using xda premium
So since I was an idiot weeks ago and restored my bricked i777 with the broken ucld3 one click..it brought it back from a bad cm9 flash but now all this talk makes me want to downgrade.
Can I use I777UCKH7-CL503881 Stock Binaries from the download repository to restore everything to factory safely?
UCLD3 system isn't a problem, it's only the original UCLD3 kernel. You could flash a safe kernel and then use CWM from there, or to be more careful, you could flash a custom Gingerbread kernel and flash from recovery.
As far as using I777UCKH7-CL503881 from the download repository, if you don't need to flash bootloaders, I would use the one from the return to the store or warranty guide, which doesn't have bootloaders.
Jesus.
Reading this thread makes my noob ass feel like a child sitting around the campfire with a bunch of longtime mobsters, listening to them talk about the guy they just whacked. Except it didn't go exactly as planned, and the guy they whacked wasn't "whacked" right away. He managed to call the cops after overhearing the duo who came to his apartment for the hit talking about their hideout. Their hideout is this campfire and I'm somehow in their company, helplessly waiting for the impending shootout to take place.
That's the sense of horror this thread gave me lol.
I had been using AOKP build 32 for a little while, but for some reason my Temple Run data kept resetting itself and I had to start from scratch (not to mention the fact that it would occasionally freeze my phone and require a battery pull).
Rather than complain to the devs about a little problem with a game, I figured I'd just hop back to a Samsung/AT&T Stock ROM. Naturally I wanted to stay on ICS so I was going to grab the leak and flash it. Luckily the thread had been closed by the time I got there, or... well, you know.
I think I'll stick to 2.3.4 with root for now (despite the infuriating home button lag -- I guess it's better than 2.3.6 and wifi).
tl;dr: As a noob, disaster threads like this terrify me.
Just thought I'd post an update on my hard bricked phone:
Josh from Mobile Tech Videos got a chance to look at my phone today and according to him the eMMC chip is toast. He was unable to recover it using JTAG. Could it just have been a coincidence that several people hard bricked around the same time or did flashing have something to do with the eMMC chip becoming defective?
Will take my phone back to an ATT service center as soon as I get it back. I don't think I will have much of an issue getting a replacement
Yup. It may only affect a small percentage of users, which is why we get dangerous posts from idiots like virus1x of "it's safe for me so it's safe for you" - For example, gokhanmoral was able to wipe multiple times with siyahkernel 3.1rc6 (which was based off of the SHW-M250L update4 sources), but when he released it, multiple users hardbricked. Task650 was able to flash multiple times without trouble - but others hardbricked.Just wanted to chime in from the ET4g community to confirm this is exactly what happens to us on ICS leaks. As stated above it only occurs when flashing on a CWM repack kernel. Mobile ODIN is safe. It Is permanent hardware damage. Nothing will fix it, but I believe that some bricks (ones that will boot to download but can't get past data.img in odin) can have low level repartitions set to avoid the factory data partition. Never done it myself and can't find the link.
Sorry to hear you guys have same bug. I just wanted to confirm it happens in CWM ICS as stated above. To flash or nandroid we Odin or mobile Odin a repacked GB kernel and flash from that CWM.
Sent from my SPH-D710 using xda premium
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://xdaforums.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Cm9 its the devil. You should see how many bricks over in the epic 4touch section. Cm9 needs to be pulled and tested thoroughly. We know they aren't responsible... Well they're right they know about it and release it anyway. That is irresponsible.