yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] kf06925:
wow, the file bigdyl69 made just became very useful to me as well today. I was stuck in a boot loop when using a different one posted elsewhere here and got the error that my internal SD partition had a different major than its disk. Once I applied your one, all worked like a charm ;) :good:
[AT&T Samsung Galaxy Note I717] Tenacious--M:
I'm looking to take a short segment of a movie and put it to music. Is there an app that can do this on our phones? If so what's the easiest/best one to use?
[Galaxy S III Q&A, Help & Troubleshooting] TCox37:
My dad just got an AT&T Galaxy S III today and asked me to put a custom rom on it. I have an HTC Vivid so I am familiar with it's bootloader and flashing kernels, recoveries, going S-off etc. After successfully rooting this Galaxy I put on a custom rom which worked but he didn't like. While flashing another rom, I got an error message mid-flash (team win recovery, flashing the Energy HD 2.0 rom) which seemed to be about not being able to flash the kernel. My plan was to go in to Odin and make the phone stock and start from scratch, but now it won't do Odin, recovery, or boot up at all. Battery is 90+%. Help? Thanks
[Galaxy S III Q&A, Help & Troubleshooting] spoonymoon:
If you cant get in download mode -volume down+start+home- im afraid you bricked it :P

Download mode and odin is last option you have :rolleyes:
[Galaxy S III Q&A, Help & Troubleshooting] JJEgan:
Please be aware that the firmware on this site is for I9300 only it may brick other models .

jje
[T-Mobile, Samsung Galaxy SIII] scifan:
I think that pretty much covers it...

I know that if you triangle away, and reboot to download mode, the counter's zero... if you boot into recovery and then boot into download mode the counter's still zero...

It gets triggered when you boot into the actual rom... I wonder if you odin to JB... then actually flash down to an ICS rom, does the counter get reset on boot?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
That's SysScope running after booting up. Flashing an ics rom over a fully updated JB will most likely also trip the counter due to the 2nd part of the device check which runs during boot. Worth trying though.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Also need to find out if its the deodexing that triggers it, or something like busybox.
[T-Mobile, Samsung Galaxy SIII] 1Shotwonder:
Good info. And nice write up so your saying if we odin root66 ics we are ok to say flash gs3r7.zip to jb and the new custom rom detection wont be present?
[T-Mobile, Samsung Galaxy SIII] wideasleep1:
There's also a manual way I used to reset, back when my touchscreen died (and therefore could not even use TriangleAway) that we should 'throw into the mix' and test against JB...lemme see if I can dig up that thread...

Okay, here was the progenitor post, that may give clues if the old (ICS) way no longer works:

http://xdaforums.com/showpost.php?p=28953690&postcount=67

and the resultant manual method, which I verified worked on TMO (ICS):

http://xdaforums.com/showthread.php?t=1781471
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thanks!

Yes that is correct. I cannot guarantee you wont have any other bugs. Doing it this way you are essentially running half ics half jb. If you have no need of samsung services like media hub or all share cast, id go full jb. Otherwise id go with the ics UVALJ4 firmware and a jb rom.

That would be great! Thanks!
[T-Mobile, Samsung Galaxy SIII] MikHaiL_08:
Good job Doc... :thumbup::thumbup::thumbup:
[T-Mobile, Samsung Galaxy SIII] Woody:
Doc, I'd be more than happy to help out with this. Just shoot me a PM about where you are heading and I can see what I can do. I'm not adverse to getting in deep, so that is a non-issue.

My initial thoughts are to take a pretty simple approach and, for lack of a better few words, do a side-by-side of the new JB and the recent leaks and see what is different. Obviously it is a bit harder than than but we could breakdown the /system/apps, then move on the each partition scheme and see what the differences are and why they are different. Then start crossing off things like apps, 2boot check, something buried in on of the other partitions, ....
[T-Mobile, Samsung Galaxy SIII] elesbb:
Really Samsung? God this crap is really starting to piss me off. Love how manufacturers don't want be enjoying my device.

On a more positive note, can't Samsung deny claims for just the CPU?
[T-Mobile, Samsung Galaxy SIII] 1Shotwonder:
only thing that bothers me is the avengers movie not playing in any of the players on the GS3R7 rom. ( I have tried to reset the counter and still does not play the movie... any ideas? It does work on stock jb root66 though). Other than that I dont use any other samsung apps. The other issue I have come across is with Root Explorer when trying to modify the build.prop for GW I can edit the build.prop but it will not save the changes I believe this to be an issue with the sdcard now being sdcard0 but I am not 100% any one have a way around this or know the fix?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thanks for looking those back up. Ill be checking them out later on today.

sounds good man! Kinda have a feeling ill be needing help on this one! Ill shoot you a pm later on. Gotta get going for now, but wanted to respond real quick.

Its another thing I've got to figure out. If its just breaking Samsung related/downloaded stuff, or is it screwing with DRM altogether.

As to your other issue, wallets included with jb now so I assumed it wouldn't require a 'fix'. But it sounds more like a superuser problem with root explorer. Download chainfires cwm supersu from his thread and flash it. See if that helps. Not going to be related to this stuff though.
[T-Mobile, Samsung Galaxy SIII] md1008:
Does reverting back to ics roll back the flash counter? I am really liking JB TW maybe time for a change lol
[T-Mobile, Samsung Galaxy SIII] Woody:
Unfortunately I doesn't work that way. Would be sweet if it did, then all we'd have to do is roll back and we'd be good. Plus we could figure out the trigger and remedy it.
[T-Mobile, Samsung Galaxy SIII] Towle:
If I'm not mistaken, you should be able to revert to ICS then use triangleaway and your counter will stay at 0.
[T-Mobile, Samsung Galaxy SIII] scifan:
Triangle away, boot to recovery, then flash ICS on your phone...
[T-Mobile, Samsung Galaxy SIII] tdizzle404:
Well my counter is stuck at 1 lol

What exactly trips the counter? I've seen multiple answers for the question but I figured ide ask here since there are so many knowledgeable people here :)
[T-Mobile, Samsung Galaxy SIII] elesbb:
So ive been reading this and from what i can gather, it seems that samsung (or T-Mobile) placed a new apk file into the system directory (or maybe a lib file?) and that if you root your device, every time you reboot your phone, it will +1 to the flash counter?

Has anyone asked any ATT, Sprint or Verizon users if their flash counter goes up with root after each reboot as well? If it doesnt, we could probably do a system file comparison between the two to isolate the file(s) which are causing the incremental flash counter at boot.
[T-Mobile, Samsung Galaxy SIII] Woody:
That's what I was saying earlier about comparing official and leak and seeing the differences. Sprint is the only one that has had official so not sure if that would work for us. Think we need to differentiate between Samsung and TMo and see where the "fault" lies.
[T-Mobile, Samsung Galaxy SIII] elesbb:
That sounds like a good idea. I'll download one of the leaks and see if anything is obvious. It may also be a new line of code inside an apk or lib file as well. Making things a bit more difficult. As im comparing them i will check the size of each APK as well as if new code is added to them it should increase the size of the compiled apk. And i have my computer set up to show individual bytes of data.
[T-Mobile, Samsung Galaxy SIII] Towle:
That's the million dollar question lol nobody knows yet. Something checks for modifications when you boot into the rom.
[T-Mobile, Samsung Galaxy SIII] kulzboy:
Im using stock official JB rooted via the root66 method and debloated a whole bunch of apps. Would that count as a custom rom? Mine didnt trip the flash counter yet. Also avengers works fine on my end
[T-Mobile, Samsung Galaxy SIII] elesbb:
Have you checked your flash counter lately? Reboot a couple times. If you can make a list of the things you removed?
[T-Mobile, Samsung Galaxy SIII] wideasleep1:
Running stock root66 JB (stock recovery), and reboots do NOT trigger any counts.
[T-Mobile, Samsung Galaxy SIII] kulzboy:
Yes i rebooted couple of times to make sure the bloats are gone

Here are some:

Media hub

Music hub

All samsung service(scloud)

Tmobile apps

Zynga

Carrier iq apps

Svoice

Chaton

Syscope

Flipboard

Kies

Kies air

S sugges

more service

Game hub

Yahoo news

Yahoo finance

Help

Gtalk

Swype

Probably some other too ill see if i can remember

Same running stock recovery
[T-Mobile, Samsung Galaxy SIII] Towle:
De bloating won't trip the counter. As long as you have stock recovery and don't do any major modifications, you will stay at 0/no.
[T-Mobile, Samsung Galaxy SIII] razielpr:
I used the root66 and didn't trip the counter then installed twrp recovery and still didn't trip the counter then flashed wicked rom no counter trip but when i flashed a T-Mobile insecure kernel with bootanimation bang it triped the counter so it must be in the kernel because it's when i flashed the kernel that it got triped

Sent From My Galaxy S3 Boricua 100%
[T-Mobile, Samsung Galaxy SIII] mike102871:
Mines already at 1. Flashing Insecure kernel didnt raise it to 2.
[T-Mobile, Samsung Galaxy SIII] razielpr:
But mine was because i check my counter every time i flash something its like paranoia and when i flashed the kernel and checked it was at 1.

Sent From My Galaxy S3 Boricua 100%
[T-Mobile, Samsung Galaxy SIII] elesbb:
I'm all sorts of confused now. -.-
[T-Mobile, Samsung Galaxy SIII] boardopboy:
For what it's worth, mine didn't trip until I used Ashaman through CWM to debloat. Using the "Recommended" option in the Aroma Installer.
[T-Mobile, Samsung Galaxy SIII] circuit.007:
I thought counter only tripped when you flashed thru odin not a kernel or rom through cwm?
[T-Mobile, Samsung Galaxy SIII] dmarco:
Yeah, apparently the JB update is intended to screw us hardcore bro:mad:
[T-Mobile, Samsung Galaxy SIII] elesbb:
Yep now its not just Odin flashed things to trip the counter. It seems just a reboot with a custom recovery? But im confused now so i ask a favor of you all:

Let me know what your flash counter is at with the following format:

ROM: <Type exact ROM name here IE Root66 method JB official update>

Flash counter status: <The number your flash counter is at>

Did you remove any apps: <Well any apps you deleted after obtaining root>

Which Recovery is installed: <Custom TWRP CWM Or stock>

Im all sorts of confuzzled cause Doc mentioned that even after obtaining root the flash counter tripped each time you rebooted. But some are saying its at zero after flashing the root66 method and reboot a couple of times and its still zero?
[T-Mobile, Samsung Galaxy SIII] kt0ce:
I agreed with this assessment.. I flashed a lot of ROM and it would stay at 0. but when I flashed Morfic kernel it tripped..
[T-Mobile, Samsung Galaxy SIII] Towle:
I don't think there has been any flash counters tripped by just flashing root66 in Odin. It's when you flash a custom recovery/rom/kernel that people have reported it tripping. I'm on the JB root66 official update with stock recovery, froze a few bloat apps, and my counter has stayed at 0.
[T-Mobile, Samsung Galaxy SIII] boardopboy:
Ok, My experience so far:

Flashed root66 JB Official through Odin. No trip. Flashed CWM. No trip. Used Ashaman's "recommended" option (dunno what apps were removed) through Aroma. Tripped. 1/Custom. Several reboots and it stayed at 1/Custom.

Used Triangle Away, counter read 0/Custom. RE-flashed root66 JB Official through Odin (I did NOT wipe the system), trip counter reads 0/Official. SEVERAL reboots later, still reads 0/Official. I still have CWM, and I have NOT frozen, or debloated anything. Full Stock with root.

Before I even had my phone, I had heard about the counter, so I watched it closely after everything I did after that first root. so I KNOW it didn't trip until after I used Ashaman through CWM. Whether it was the simple act of "installing the zip" or actually one or many of the bloats removed, i do not know.

I have not flashed any kernel or rom yet.

Edit: Since I can easily get back to a zeroed out counter simply be reflashing root66 through odin, and not lose any data... I'll go ahead and play around with different things in CWM a little later today and report back.
[T-Mobile, Samsung Galaxy SIII] scifan:
All of my testing was done with TWRP - which would cause the flash counter to trip on reboot after TWRP was installed via goomanager.

Perhaps I should try with CWM...

Basically, at this point, I"m running a "stock deodexed" JB rom on top of a root66-LJ4 image which works well - the counter doesn't trip on boot.
[T-Mobile, Samsung Galaxy SIII] razielpr:
Mine was triped when i flashed insecure kernel

Sent From My Galaxy S3 Boricua 100%
[T-Mobile, Samsung Galaxy SIII] Marquis63:
Ok quik noob? Where do I find the flash counter?
[T-Mobile, Samsung Galaxy SIII] wideasleep1:
Download mode.

What we need first is for someone with a tripped counter to see if the 'old' manual method works first...
[T-Mobile, Samsung Galaxy SIII] scifan:
If you boot into download mode you can see the status of things...
[T-Mobile, Samsung Galaxy SIII] md1008:
Its only a matter of time before samsung goes the way of HTC. It just sucks that loading software voids your warranty. I think its BS if for instance the screen blacks out to be sol because we have cm10 on our phone... lame lame lame...
[T-Mobile, Samsung Galaxy SIII] scifan:
The question is... how long before this activity will all be banned per DCMA (or is it already?)

So... I Odined the Root66 LJA stock rom over my phone...

I installed CWM, I zeroed the flash counter...

booted into the rom, and the counter stayed zero after a reboot...

Booted into recovery to verify that CWM is still there

and the flash counter changed to 1 again... I cleared the counter and rebooted the phone and the counter stayed at 0...

Starting to wonder if it will stay at 0 until I boot into the recovery again...

That's whacked...

I wonder now if TWRP would behave the same...

Rebooted and the counter stayed at 0...

(note this is not a deodexed rom)
[T-Mobile, Samsung Galaxy SIII] md1008:
So apparently its now illegal to "jailbreak" tablet's this could be good news for Google if it decides to make a tablet in house and openly allow users to mod their nexus tablets. I don't know just seems really retarded to me

www.huffingtonpost.com/mobileweb/2012/10/27/jailbreaking-tablets-illegal_n_2024754.html
[T-Mobile, Samsung Galaxy SIII] Cobra281:
ROM: stock TMO T999UVDLJA with root injected from mrRobinson's thread

Flash counter status: 1 only AFTER installing TWRP recovery via the GooManager app

Did you remove any apps: none

Which Recovery is installed: TWRP

thanks for that info!
[T-Mobile, Samsung Galaxy SIII] EvilAldo:
When the update came out I never downloaded it. I Odined to wild child's stock with root, but this time I installed twrp instead of cwm. I never removed any apps. I flashed wicked with the stock kernel when it updated to jelly bean. I've never ever tripped my counter since I've owned the phone.
[T-Mobile, Samsung Galaxy SIII] elesbb:
So it only trips when when booting to recovery? That's going to be harder to crack down but not a big deal because you can reset the counter flash stock image and be good to go.

But if it becomes "illegal" to customize your phone, then I truly believe America is on the verge of self destruction.
[T-Mobile, Samsung Galaxy SIII] roly17:
ROM : stock jb w/root 66(Mr Robinson)

Flash status : 1

Removed apps : 0

Recovery : twrp

I only just checked counter today so I honestly don't know when it got tripped. I assume it happened when I installed twrp from goomanager. I have a backup of this setup. My avengers movie works fine (even though counter is at 1), but when I try to flash a different kernel l lose the ability to view movie.

First I tried ktoonsez then I tried sairegsx. Both times it affected the movie, although media hub was the only Samsung app I use. When I restore my backup movie works again. Hope this helps.
[T-Mobile, Samsung Galaxy SIII] elesbb:
I seriously am beginning to think that the bootloader code has been changed to check for a modified recovery..
[T-Mobile, Samsung Galaxy SIII] sswb27:
I think it might be in the boot loader too. I flashed cm10 then reset the flash counter, rebooted the phone and it was back at 1. Cm10 is built from aosp code and the kernel is totally custom so I don't see how there could be anything in the ROM or kernel making it count. Only thing I could speculate would be the boot loader since it didn't trip the custom counter flashing cm10 before I odined the stock jelly bean.
[T-Mobile, Samsung Galaxy SIII] md1008:
I can confirm that entering recovery trips the counter. I am running 100% stock odex rom and I set triangle away booted into recovery the from their booted into download mode counter 1. Booted back into recovery counter 1 (didnt increase count) rebooted my phone triangle away. Power off, odin counter is zero. The second we enter recovery the counter is tripped.
[T-Mobile, Samsung Galaxy SIII] scifan:
Modified boot loader makes sense... That would explain the most... the question is what to do about it (if anything)
[T-Mobile, Samsung Galaxy SIII] wideasleep1:
With a 1 count, would you mind trying the manual method to clear, I mentioned and linked earlier? TIA!
[T-Mobile, Samsung Galaxy SIII] roly17:
I would try this, but I have to be honest. I have no idea how to use adb. I'm not a computer guy. I can follow instructions no problem. If you want to walk me through it with pm or something I can try tonight when I get home. My computer has not been recognizing phone lately for some reason. I keep getting message "hardware id is missing" but I think I remember seeing that adb is functioning. Again though I'll have to check when I get home tonight.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I will try to give it a shot later today. Otherwise, tomorrow maybe. I want to take a little more time to look at it before just entering commands and hoping for the best!!!
[T-Mobile, Samsung Galaxy SIII] m4r10:
So according to what Doc Holiday is saying I can flash a custom ROM and the only down side is the possibility of some Samsung apps not working like Media Hub and All Share?

And I can flash my phone back to stock and use triangle away in case of having to send in the phone?

Is this what the situation is right now? Trying to figure out how to make those Samsung apps work with custom ROMs?
[T-Mobile, Samsung Galaxy SIII] scifan:
well... that does explain a few things... and yeah, my phone shows up as modified under status... hmmm... time to play a little more.

I managed to get myself to a point where MOST things were happy, except I couldn't install Some updates from the google play store... going to go back to LJ4 + LJA system now...
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yes, in the event you have to send it in for warrany service, you can set everything back to stock with zero flash count. It requires doing things in a certain order, but can be done. Biggest issue here is theres no set it and forget it like before, so if something happens to make the device inaccessible (other than hard brick), itll make it more difficult to set it back to stock before sending it in. In ICS you only had to worry about Odin flashing the stock fw, provided you kept you counter at zero.

Ill post instructions on all of this later.

There are two things im concerned about though. First is if there is any other new detection methods we havent found (not likely, but I still wonder about when its coming more than if), and second is it really just the Samsung related apps that it screws with, or is it all drm protected media in general?

I could be wrong but I just cant see why Sammy woulda done this intentionally, as in, I wonder if this problem is an unintended side effect they didnt see coming? I just dont see a reason to intentionally break features because you want to customize the device. Especially when its the one manufacturer thats been somewhat developer friendly in the past. If they really wanted to stop us theyd have locked down their bootloaders like HTC and Verizon! But to literally punish some of their most intelligent users (and reviewers) by taking away functions makes no sense to me at all. (Especially when its content we paid for....usually! ;)) And not to mention it guarantees we wont be buying it from Samsung....its just not good business!

I hope all that made sense, but as i stated, my original point is that I dont know yet if it does ONLY break Samsung apps, or if itll create a problem with all DRM protected content.

If any of you are willing to try, let me know please if ANY drm content (including stuff from Samsung) will play while having a tripped counter. Also, see if any of it will work while the counter is at zero, but the status in settings says modified.

Thanks again to everyone for all your feedback, and as always if youve seen something different from what ive stated, please let us know! :cool:
[T-Mobile, Samsung Galaxy SIII] elesbb:
All that wonderful fantastic info sent from your phone!? Man doc you truly are dedicated! Thanks so much for this surplus of information!
[T-Mobile, Samsung Galaxy SIII] m4r10:
Thanks. You are great at explaining all this. Good luck and God speed.
[T-Mobile, Samsung Galaxy SIII] wideasleep1:
Unless your adb is already working, I think the easiest way is to d/l mskip's Toolkit:

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

it will provide updated drivers (see Step 1), but if you already have Kies installed, I'd delete it first to prevent conflicts.

Once your S3 is properly detected, you can simply choose your phone model, and then choose 21: Open command prompt for manual input. Then IIRC I simply copy/pasted (and I *think* I did these one at a time, and hit enter at each):

adb shell

su

echo -n '\x00' | dd obs=1 count=1 seek=4193796 of=/dev/block/mmcblk0

Pulled phone and rebooted, still had dead digitizer, but after a reboot back into Download mode, I had 0 trips and Samsung/Official for all settings. :)

Edit: I'm curious if this still works (it's as easy as TriangleWay, frankly), and if it doesn't, we know JB has moved those count reset blocks elsewhere, and we'd need to relocate them.
[T-Mobile, Samsung Galaxy SIII] mike102871:
Yes this does reset the counter. But as soon as you go into custom recovery, it does trip the counter. I odin flashed the prerooted stock jb. Media hub avengers movied played . Flashed twrp via rom tool box and media hub movies no longer play. Movie wont play after a counter reset either. But the command does reset via adb until recovery rebootdd
[T-Mobile, Samsung Galaxy SIII] saranhai:
huh interesting little thing...rooted and nothing else, all i did was remove Syscope.apk from /system/app after root, the counter is not tripped and everything is good and official in download mode, but in settings/about/status, it shows "modified"
[T-Mobile, Samsung Galaxy SIII] Towle:
Flashing a stock image in Odin fixes that.
[T-Mobile, Samsung Galaxy SIII] saranhai:
yes i know, just found it interesting how it says "modified". was it the deleting of apps that did it?
[T-Mobile, Samsung Galaxy SIII] Towle:
It has to be. I am on JB root66 official update with stock recovery and kernel. Froze about 10 bloat apps and disabled CIQ. Flash counter is 0 and doesn't show modified.