yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S II SGH-T989] vencc:
No problem, I just wish more people knew about the potential of this defect and to use caution when experimenting kernals, etc. I bought my phone used, no idea it had a bad chip(would recommend anyone with a S2 to run the app to check). Wouldn't have flashed at all and left it stock if I knew.
[T-Mobile Samsung Galaxy S II SGH-T989] JesusWazBlack:
My phone likes to get extremely hot while using it for a longtime on stock settings... Anyone else?
[T-Mobile Samsung Galaxy S II SGH-T989] me_is_rushin:
I have the "bad chip" never had any issues. In fact the issue was patched by Samsung and quickly by all other roms as of June 2012. http://wiki.cyanogenmod.org/w/EMMC_Bugs#Samsung_eMMC_secure_erase_bug

Whatever you are experiencing has to be something else.

---------- Post added at 07:36 PM ---------- Previous post was at 07:33 PM ----------

Any updates on Focal? Saw something on github about a lot of commits being added to fix issues and stability.
[T-Mobile Samsung Galaxy S II SGH-T989] Cameron581:
Dark side super wipe? Then flash?
[T-Mobile Samsung Galaxy S II SGH-T989] germania:
Just a heads up, the TWRP guys have fixed flashing 4.3 for hercules (NOT IN THE CURRENTLY AVAILABLE VERSION HOWEVER), so if you use it keep an eye out for an update in GooManager. The next version should support SELinux just fine.
[T-Mobile Samsung Galaxy S II SGH-T989] bsd1101:
great news
[T-Mobile Samsung Galaxy S II SGH-T989] bikeryder007:
Thanks for the heads up. This is what I have been waiting for before jumping to 4.3!
[T-Mobile Samsung Galaxy S II SGH-T989] :
A lot of these posts should be in a question and answer thread...if there is one.

- This is an alpha....gonna be glitches.

- Asking for any kind of features at this point is pointless.....the base features all gotta be smoothed out before adding more things that cause issues.

- If you don't like how some things work or don't work.....just go back to 4.2.2 until 4.3 matures. Let team chopsticks get everything running smooth and stable...then they'll add stuff. Just like every other time a new android version has come out.

- its great that twrp will be updating for the Hercules ....but keep in mind....eventually some things will stop being updated for our phone. Its getting old. Period. If you don't like the recovery you have to use....again....stick with 4.2.2 for now.

And remember....4.3 is an extremely minor change from 4.2.2.....so if you aren't into alphas and glitches.....then wait.

(End rant) ;)

-

Sent from my cell phone telephone using some sort of app...
[T-Mobile Samsung Galaxy S II SGH-T989] me_is_rushin:
There isn't.

And while I share some of your frustrations posts like this are useless (no offense) because after a couple more posts it won't be on the last page. There will still be people clicking last page and posting "where is feature x?" "why is this not working?" "I did this and this and this and now something or other isn't working. help!" etc. There is no hope for getting people to read sometimes.

Imo 4.3 is pretty substantial just not on the front end where users will notice it.
[T-Mobile Samsung Galaxy S II SGH-T989] :
So someone make one. 10.1 had one. Dev threads are for trouble shooting rom issues.....not questions about why Facebook isn't working or that someone really wants screenshot on their power button menu. Lol

Substantial update? On a nexus maybe. ;) My N7 flies now.....my S2 always did. And new features ...none that I've personally used or encountered.

And I agree....it was a useless post....I admit....because it seems no one reads back anymore. Just go straight to last page or straight to post reply.

Those are the people who will inevitably brick their phones one day. :) Then they may understand us "please read and search" people were actually trying to help.....not flame them.

Sent from my cell phone telephone using some sort of app...

---------- Post added at 04:36 PM ---------- Previous post was at 04:32 PM ----------

K....I'll shut about it now. Keep harassing the devs over silly things people....and soon you'll have to develop your own roms. LOL

(That was not aimed at you me_is_rushing) ;)

Sent from my cell phone telephone using some sort of app...
[T-Mobile Samsung Galaxy S II SGH-T989] monkeybuttons:
Sad thing is it's happened here before.

Thederekjay is sorely missed.
[T-Mobile Samsung Galaxy S II SGH-T989] Koragg618:
Oh well, since you suggested, I made one. :D

http://xdaforums.com/showthread.php?t=2418073

Sent from my T989D running Slim Halo on Tapatalk 4.
[T-Mobile Samsung Galaxy S II SGH-T989] germania:
This has been published now as 2.6.0.3, it should be available in GooManager
[T-Mobile Samsung Galaxy S II SGH-T989] kennkanniff:
Hmmm, flashing this inside 4.3 seem to have semibricked phone. Maybe it should be flashed on 4.2...

EDIT: Odined back to CWM and rom boots again...
[T-Mobile Samsung Galaxy S II SGH-T989] FCORivers:
I used the twrp 2.6.0.2 found here http://xdaforums.com/showthread.php?p=44926790 flashed thru cwm and have successfully booted back to your ROM. Let's see if doesn't screw up in the long run like 2.6.0.0. I have faith though. Hehehe

sent through time and space from my Hercules
[T-Mobile Samsung Galaxy S II SGH-T989] germania:
Confirmed and reported back to the TWRP guys. Don't flash this version!
[T-Mobile Samsung Galaxy S II SGH-T989] bsd1101:
TWRP 2.6.0.3 will not correctly upgrade from goomanager. The filenames are reversed and cause problems. If you look to the TWRP post, you will notice I pointed this out earlier. The .tar is actually the .img, and vice versa. If you rename them, they flash properly.
[T-Mobile Samsung Galaxy S II SGH-T989] kennkanniff:
I geuss they just forgot to update the version string then as twrp still reads as 2.6.0.2?
[T-Mobile Samsung Galaxy S II SGH-T989] meekrawb:
Bsd1101 figured out that the filename extensions were reversed. Rename the files from goo from .tar to .img or .img to .tar and then use them accordingly. Or use the zip I posted in the TWRP thread.
[T-Mobile Samsung Galaxy S II SGH-T989] kennkanniff:
Okay lets move this to the openrecovery thread
[T-Mobile Samsung Galaxy S II SGH-T989] mknewman:
Only big issue I have found running this alpha 1 for a few days is the Gallery causes a reboot pretty much every time I use it. I even clearef data on the Media process and rebooted.
[T-Mobile Samsung Galaxy S II SGH-T989] JesusWazBlack:
known issue my friend
[T-Mobile Samsung Galaxy S II SGH-T989] car vs driver:
You have a corrupt file somewhere. Clear out your photos, etc from the device and you should be good to go.
[T-Mobile Samsung Galaxy S II SGH-T989] -DarkKnight-:
Why didn't it reboot in 4.2 then?
[T-Mobile Samsung Galaxy S II SGH-T989] monkeybuttons:
Same thing happened when ics came out. Sometimes things like this happen.
[T-Mobile Samsung Galaxy S II SGH-T989] car vs driver:
Beats me ... we saw this in early testing with 4.3 with two other people and that's what fixed it.

Also, without a last_kmsg after that crash I cannot provide any more insight into it than that.
[T-Mobile Samsung Galaxy S II SGH-T989] skadude66:
I just made my phone reboot my scrolling to the SD card in the gallery.. It crashes using Quickpic and the Gallery. I've uploaded the last_kmsg to 4shared.

http://www.4shared.com/office/oLCVpZM6/last_kmsg.html?

Hopefully this helps!
[T-Mobile Samsung Galaxy S II SGH-T989] JesusWazBlack:
Right here

__irq_svc+0x54/0x80) from [<c01657f8>] (msm_cpuidle_enter+0x28/0x30)

[14050.519927] [<c01657f8>] (msm_cpuidle_enter+0x28/0x30) from [<c05ae55c>] (cpuidle_idle_call+0x188/0x360)

[14050.520111] [<c05ae55c>] (cpuidle_idle_call+0x188/0x360) from [<c0106238>] (cpu_idle+0x84/0xe8)

[14050.520233] [<c0106238>] (cpu_idle+0x84/0xe8) from [<40ba6bd4>] (0x40ba6bd4)

[14050.620605] subsystem-fatal-8x60: Q6 NMI was sent.

[14050.625885] charm_panic_prep: setting AP2MDM_ERRFATAL high for a non graceful reset

[14056.635986] charm_panic_prep: MDM2AP_STATUS never went low

[14056.636383] panic_prep_restart

[14056.636596] (sec_debug_set_upload_magic) 776655ee

[14056.636962] Rebooting in 5 seconds..

[14061.645446] Restarting Linux version 3.0.89-cyanogenmod-g35d5a5d (dferg@helo) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Mon Aug 19 20:44:15 EDT 2013

[14061.645538]

[14061.646575] set_dload_mode <0> ( C0175168 )

[14061.647277] Going down for restart now

[14061.648468] pm8xxx_reset_pwr_off, [1]

[14061.649108] pm8xxx_reset_pwr_off,
[T-Mobile Samsung Galaxy S II SGH-T989] mknewman:
No, that is not the problem. I went back to 10.1 nightly and have no issue with either Gallery or Quickpic, both of which are causing RRs reliably.
[T-Mobile Samsung Galaxy S II SGH-T989] car vs driver:
OK, you're right, I'm completely wrong and have never seen this before and the suggestion I offered didn't fix it for anyone else. So you really shouldn't bother trying it. Could I be wrong, sure? Could it be something entirely different than we've already seend and fixed by removing all media (photos) from internal storage? Sure. But until you try, that's my answer.

Best of luck to you.

---------- Post added at 07:09 AM ---------- Previous post was at 07:08 AM ----------

That's only the tail end of the kmsg, so it isn't really helpful. Can you pastebin or dropbox the entire thing next time?
[T-Mobile Samsung Galaxy S II SGH-T989] mknewman:
Look right above your original answer, someone else said it was a known error. I was happy to help test this new ROM as long as it didn't impede on my day to day stuff. I was mainly noticing clock was not starting on reboot. That is not usable. The gallery was an annoyance.

BTW I went thru my gallery on 10.1 and have zero corrupt photos. Every one renders.

I did a backup of 10.2 so I can go back easily. I did a File Bug Report but was not sure it did anything. I'll try to get a proper bug report to pastebin if I do.

Marc
[T-Mobile Samsung Galaxy S II SGH-T989] car vs driver:
It's a known error to who, another user? I offered a potential solution and you chose to ignore it (in the very least a validation that it isn't corruption). Validating anything in 10.1 is utterly pointless, there are far too many changes under the covers, specifically how the file systems are handled to make that a valid test to prove something on 10.2

So, at this point, I'm not going to offer any more suggestions that are based on facts from what we tested in early development when we had other users encounter the same exact problem.

Part of asking for help and pointing out problems is the willingness attempt solutions to solve the noted issue. If you clear your local storage and the problem persists, then we can at least rule out a corrupt file in the gallery. Debugging is the process of elimination, so I'm attempting to get you to rule out the obvious before we spend hours digging through code to chase down an issue.
[T-Mobile Samsung Galaxy S II SGH-T989] skadude66:
I took the last_kmsg from my reboot last night (while using the gallery) and uploaded it to 4shared. Let me know if you can access it.

http://www.4shared.com/office/oLCVpZM6/last_kmsg.html?
[T-Mobile Samsung Galaxy S II SGH-T989] car vs driver:
Hmmm .. that site doesn't like how I have my browser setup I suppose. Can you put this in google docs or dropbox instead?
[T-Mobile Samsung Galaxy S II SGH-T989] skadude66:
Sure, no problem.

https://www.dropbox.com/s/cdmcermr29to9dx/last_kmsg.txt
[T-Mobile Samsung Galaxy S II SGH-T989] JesusWazBlack:
I said it was a known error because I've seen multiple reports of this on the 4.3 ROMs plus I had it myself when I was running this and beanstalk....I assumed yall knew it was a known error
[T-Mobile Samsung Galaxy S II SGH-T989] car vs driver:
Got it, thank you. Please leave it up there for a couple days, I sent it over to Topprospect and Mikeyman to take a look at as well.
[T-Mobile Samsung Galaxy S II SGH-T989] skadude66:
No problem! I've got plenty of space on dropbox so it won't be removed unless Dropbox does it themselves.
[T-Mobile Samsung Galaxy S II SGH-T989] kevo777:
It soft-bricked my S2 from 4.2 :confused:
[T-Mobile Samsung Galaxy S II SGH-T989] mknewman:
Ok, so I am back on 10.1 and everything is working ducky. It's pretty obvious that something changed in a bad way under the covers on 10.2 because this Gallery problem is happening with both Gallery and Quickpic. If you chose to ignore my report (and others) it will just come back and bite you when you release a production version. At least you should acknowledge that someone with 38 years in the software business and 8 years in Software Quality might have a clue and could possibly be reporting a legitimate problem. "Clearing internal storage" might be an answer for you, but it is not for me. Yes, it will get rid of the problem, as there will be no files to cause a problem. Kill the baby to cure his cold.

You know, I sent Mkeyman a donation the other day. It's not like I don't try to help this community. Your solution of clearing /sdcard is not reasonable to me so I'm choosing not to try it. There are other ways to verify if there is a corrupted file on a filesystem. You choose to ignore my attempt to try one. If you don't fix this ROM there will be someone else who does. As I said before, I was willing to help test as long as it didn't impact me in a major way.
[T-Mobile Samsung Galaxy S II SGH-T989] kennkanniff:
If you are that advanced with software and all you should know that if nobody else has the problem the problem must be on your side.

And do not start with, but he has it to. I havent neither has CVD; so its YOUR problem.
[T-Mobile Samsung Galaxy S II SGH-T989] foltz61:
Happens to me too. I didn't report it because of Alpha status.
[T-Mobile Samsung Galaxy S II SGH-T989] car vs driver:
You clearly don't understand the basic concept of debugging, which is similar to the process of elimination. I never said you didn't have a legitimate problem, but your inability to perform a simple validation to help further diagnose the issue only proves that you, yourself still have a lot to learn in your 38 years of d*ck waving experience. In fact, I did just the opposite, I offered you a potential solution and validation test to see if there was bad data (or at least something that the new rom didn't like) on your phone. You ignored it. The baby isn't dead, the baby is being treated by other users who care to provide better information instead of simply complaining.

Others have chosen to provide helpful information such as kernel logs and clearing internal data to test, you have not. So have fun going back to 10.1 - when you are ready to be helpful other than complaining, I'd be happy to listen.

Well, then feel free to verify file corruption by one of your other means. Comparing 10.1 to 10.2 which has an very different filesystem mechanism due to SELinux is not valid; your own experience as a Software QA person should have shown you that comparing apples to oranges yields invalid results.

That's fine if my method doesn't work for you, but using an alpha and not expecting to be impacted negatively in any way, is again a bad assumption on your part.

Also, good for you in donating to Mikeyman. We, as a team work very hard, FOR FREE and only ask that we receive reasonable feedback and useful information in return when reporting bugs.

Now out of respect for the rest of the people in this thread and the development team, feel free to ping me in PM to further the conversation if deem it necessary.
[T-Mobile Samsung Galaxy S II SGH-T989] tdt1345:
No service

How come I don't have service after flashing this rom I went back to stock still don't have service whats wrong with it
[T-Mobile Samsung Galaxy S II SGH-T989] mycars12:
Funny thing is I dirty flashed and clean flashed from both cwm and twrp and I don't have that problem

I tried replicating it by rebooting several times and adding and removing pictures from my phone, don't really know how it happened to you, I tried as well, try doing clean wipe and listen to CVD advice/solution
[T-Mobile Samsung Galaxy S II SGH-T989] me_is_rushin:
Hmm...let me just look into my magical book of "What's going on with your rom" Your page appears to be empty. If you want help at least provide some details. What recovery are you using, radio, kernel, dirty/clean flash, etc. I'm guessing something is wrong with your baseband. Flash UVMC6
[T-Mobile Samsung Galaxy S II SGH-T989] tdt1345:
I used everything that was provided on this page http://www.teamchopsticks.org/p/cm102-release-notes.html I wiped everything including delvik cache. I don't know what kernel I'm using how do I find out?
[T-Mobile Samsung Galaxy S II SGH-T989] car vs driver:
If you didn't purposefully install a 3rd party one, then you're on the stock kernel that comes with cm.
[T-Mobile Samsung Galaxy S II SGH-T989] tdt1345:
Could that be the problem?
[T-Mobile Samsung Galaxy S II SGH-T989] monkeybuttons:
No, that wouldn't be the problem. TeamChopsticks recommends staying on the stock kernel in the OP (opening post).

You said you don't have a signal even after going back to a stock ROM? If that's the case, something might have gotten corrupted, especially if you didn't use a 4.3 compatible recovery (CWM 6.0.3.7+ or TWRP 2.6.0.3+) when trying to flash a 4.3 based ROM.

You might need to ODIN your phone back to stock, but I would try flashing the latest modem for your phone first (UVMC6 for T-Mobile).
[T-Mobile Samsung Galaxy S II SGH-T989] Koragg618:
I think this belongs here. Its a logcat of the DSP Manager not working in Paranoid Android. Since its based on CM ( I think ) I felt it was necessary to post it here.

Thanks
[T-Mobile Samsung Galaxy S II SGH-T989] mycars12:
Anyone know when cm account will be integrated?

I got app and put in system/app and when I reboot it disappears, I'll try messing around with permissions
[T-Mobile Samsung Galaxy S II SGH-T989] mknewman:
Pastebin from Gallery crash

http://pastebin.com/e1TiH6CU
[T-Mobile Samsung Galaxy S II SGH-T989] me_is_rushin:
Has it rolled out already? I thought it was going to be added "soon". If it has or hasn't though you probably won't see it until we start getting official nightlies. Probably no more than a few weeks would be my guess.

Don't want to be spreading false information. See below. Straight from the horses mouth. Thanks CvD
[T-Mobile Samsung Galaxy S II SGH-T989] car vs driver:
Developers need to manually add it to their build manifests, but it does work. I've been playing with it today actually. Not sure when it'll be part of the standard manifest for 10.2 though.
[T-Mobile Samsung Galaxy S II SGH-T989] tdt1345:
I used the everything that was posted in the link. I tried using the lastest modem as well even went back to stock everything nothing is fixing my problem
[T-Mobile Samsung Galaxy S II SGH-T989] mknewman:
I've got to say, besides the warts this ROM is spectacular. Battery use is incredibly good, way better than 10.1.
[T-Mobile Samsung Galaxy S II SGH-T989] monkeybuttons:
Well, my final suggestion is to use Kies to take your phone back to stock. This will put your phone into a "factory" condition. Make sure you back up your internal sd card as it will get wiped. If Kies doesn't fix it then I'm out of suggestions.
[T-Mobile Samsung Galaxy S II SGH-T989] tdt1345:
How do I go about doing that?
[T-Mobile Samsung Galaxy S II SGH-T989] monkeybuttons:
The bottom of the linked post has instructions on how to use Kies when you don't have a stock ROM on your phone. (the section under "UPDATE")

It has always worked for me.

http://xdaforums.com/showpost.php?p=36147681
[T-Mobile Samsung Galaxy S II SGH-T989] tdt1345:
Still didn't work still no service can't register to network
[T-Mobile Samsung Galaxy S II SGH-T989] rymaples:
There are a few different posts on how to install cwm. I'm using twrp now. Can someone point me to the right post to use? Thanks
[T-Mobile Samsung Galaxy S II SGH-T989] -DarkKnight-:
Does anyone know what bugs in this ROM are preventing it from going into official nightly status?
[T-Mobile Samsung Galaxy S II SGH-T989] hatememarkz:
Doesn't the title say official

drankn BL SMOOTHIEZ ;)
[T-Mobile Samsung Galaxy S II SGH-T989] macboy3000:
It's official, but we don't have nightlies yet, just an alpha.
[T-Mobile Samsung Galaxy S II SGH-T989] me_is_rushin:
I don't believe there is any "bug requirement" for nightlies as nightlies are by there own standard usually buggy especially this early in development. I'm guessing just whenever Team Chopsticks think they are ready. No need to rush things good things take time.
[T-Mobile Samsung Galaxy S II SGH-T989] monkeybuttons:
Maybe a SIM card issue? I'm just grasping at straws now.
[T-Mobile Samsung Galaxy S II SGH-T989] BitingChaos:
My last T989 wouldn't register on T-Mobile's network. Why? Someone had reported it stolen. The IMEI was suddenly blacklisted. That is something else that can be checked. Long shot, I know.
[T-Mobile Samsung Galaxy S II SGH-T989] kennkanniff:
I always knew the consumer were gonna have problems if they start to block stolen phones.

It is so freaking stupid governments do not see that the only consequence will be that carriers will sell more phones.

And yet people support it, fools.

Sorry for the OT.
[T-Mobile Samsung Galaxy S II SGH-T989] BitingChaos:
I agree with blocking phones. There needs to be more and better blocking. If you prevent people from using stolen phones, you remove the incentive to steal phones in the first place (since they become useless).

Apple is doing an AWESOME thing with iOS 7. If the phone is stolen, it is effectively dead. Why?

* Remote wipe. This has been built-in since the iOS 4.x days (2010). Part of the "Find my iPhone" app. The second that phone gets online, all my stuff is secure-wiped.

* If the user turns off the device and tries to factory wipe it, any iOS device that had iOS 7 installed simply will not activate unless they log in with *my* user credentials. Apple/iTunes will block device activation, preventing it from being used as a phone or even as an iPod touch. It will simply not function.

I believe I read that Samsung is working on something similar for their devices. There is so far nothing that comes close to this sort of protection on Android (programs like Cerberus are easily wiped from a device, and nothing can completely stop the device from working).

I can basically shut down a device immediately before even contacting my carrier to report it stolen. Yeah, my phone is gone, but I at least know no one else will be able to use it.

Back to the issue tdt1345 was having, any time my (new) T989 or T959 couldn't work, I had to use Odin to restore back to stock.

T989UVMC6_T989TMB_T989UVMC6_HOME.tar.md5 (783 MB) is the file I use for my T989.

The steps I took (and I did this this past weekend after losing my signal)

* flash TWRP with Odin

* reboot to TWRP

* run that Super Wipe script I've seen recommended 100% and NOT recommended 100% so many times in various threads (some people say it's required, some people say to AVOID it at all costs - my personal experience is that it has fixed every <=4.2 issue I've encountered).

* boot back to Odin and flash stock. the "stock" image does not flash /data, so that is why I'd use the super-wipe script.

When 4.1.2 loaded, I had my connection back. From there I flashed TWRP again, did a super-wipe, and put CM10.1 back on.