To my recollection, ktoonsez's releases went from 3.1 rc5 to 3.1 final.
Last edited:
Hard bricked during CM9 upgrade from UCLD3 Leak?!
- Thread starter avus_m3
- Start date
To my recollection, ktoonsez's releases went from 3.1 rc5 to 3.1 final.
Is this really that hard to comprehend? They wouldn't keep it up to download if they knew it was causing hard bricks. Its gone now. Done. Poof. Good lord people its called common sense. Helpful in situations such as this.
Sent from my SGH-I777 using Tapatalk 2
Sent from my SGH-I777 using Tapatalk 2
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
Sent from my SPH-D710 using xda premium
darchstar and sbrissen are working on forward-porting your CDMA and WiMAX drivers to the I9100 update4 base - I think they have everything but CDMA and WiMAX working right now.
The international Note has the same issue - leaks are dangerous. Good thing the I9100 update4 source was also usable for Note with not much work.
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?
Can I use I777UCKH7-CL503881 Stock Binaries from the download repository to restore everything to factory safely?
Last edited:
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.
Thanks for the info...I went ahead and did the full restore just to be on the safe side and it went thru without a hitch
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.
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.
I wouldn't be too worried. Just stay away from the AT&T leaks as whatever AT&T touches seems to come with problems. Just use one of the ROMs based on the i9100 firmware and you'll be fine. There are plenty in our development forum and ported development forum.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
7
Right now, the general consensus is:
With the exception of I9100 leaks and kernels built from I9100 update4 sources, Samsung ICS kernels for Exynos4 devices have a SERIOUS bug that causes them to do permanent damage to the eMMC chip. This is most likely to occur when doing a major erase operation (such as a wipe in CWM, but a wipe/factory reset in stock 3e recovery is likely to be just as dangerous)
This includes kernels from:
All Epic 4G Touch ICS leaks
All GT-N7000 (International Note) ICS leaks
The UCLD3 I777 leak (probably all of the I777 ICS leaks)
Anything built from the Korean SHW-M250S/K/L bases - this is why there was just a rash of hardbricks with SiyahKernel 3.1rc6 - it was based off of the Korean M250L sources.
Right now the suspicion is that it is due to this:
https://github.com/Entropy512/kerne...59551eaf5afc3d68f2da96b0249937bd5e13#L10R1881
Samsung attempted to fix it with:
https://github.com/Entropy512/kernel_galaxys2_ics/commit/d069cc5cb9f0fd9409ea10d4037e4c0e68701b8e
but they only disabled TRIM and not ERASE (which are related)
Unfortunately there's no way to test this without risk of hardware damage... you can't declare something fixed unless you can reproduce the problem - but you can reproduce this problem once per device repair. So really only Samsung can declare it fixed - but then they'd have to actually interface with the development community.3
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.
It may only be 2-3% of users that will hardbrick - but that's still WAY too high considering that a properly working kernel has 0% chance of hardbricking unless you do something really stupid, and even then, until this recent rash of broken ICS kernels, JTAG recovery could resurrect you for $50 or so.2
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-62
You're ridiculous. Why are you on XDA. You shouldn't even be flashing anything to your devices with the level of intellect that you've shown here. The poop I took this morning made more of a difference here on XDA then you did in your post.2Hmm, odd, that's the most likely way to hose you...
Either way, do NOT flash anything or nandroid anything using the CWM-repacked UCLD3 kernel. Do NOT restore any Nandroids made with that kernel. Heimdall/Odin something else FIRST.
