yashsingh1/xdaforums huggingface dataset:
[Samsung Infuse 4G] Pony Express:
I just put mine in download and binary also says 'no'. I have lost count as to the number of roms I have flashed.

I think you are close but from my end I can't tell what is missing. I have used odin with no problem and yet my preference is Heimdall.

Maybe take some time and go through some of qkster's threads, including the link to his Heimdall tutorial. Some have found that they did not have the latest version of Java while others did not know that you have to use the same port you were using each time you use Heimdall. Others did not know that Heimdall has it's own drivers or that they should uninstall kies first.

Qkster may drop by this thread and if he has suggestions he will post. He has forgotten more about the Infuse than I know. :D
[Samsung Infuse 4G] Azrael-09:
I installed then uninstalled Kies

I do have the latest version of Java.

I downloaded a binary version of Heimdall for the Zadig driver file so that i can manually put in the samsung driver before opening the one click Heimdall

I have followed tutorials to the letter so much that when i watched the video it seemed like I was knowledgeably far beyond the video's tutorial.

Im am however, unsure what you mean by using the same port (please keep in mind that im on the computer trying to fix my phone about 45 min out of every hour for about 8 hours a day for the past 5 days)... I actually had to erase all the zip files and tar files and such just to re-grasp where i was at because my desktop was overloaded...

Oh and i read a thread about bricking your phone (good read) and i think i screwed it up somewhere in the bootloaders... its not enough to hard brick it since i can still go into DL mode but something is definately wrong.

I do appreciate your advice and concern. Thank you again.

Hopefully we can come to a conclusion soon and i can pass on my knowledge...
[Samsung Infuse 4G] qkster:
Thanks for the vote of confidence, Pony. I'm not very good at getting the drivers installed.

What you noted is all that I can recommend.

Update java. Install Samsung USB device. Install Zadig from Heimdall. Sometimes it take a reboot or two with the PC. Other times, it takes a different PC altogether. It may also work by moving the USB cord to a different usb port.

It has been almost a year since I tried Odin. No help there.

I can tell you that after you get the heimdall to work, save that cord and that usb port only for heimdall and don't install Odin over it.

With all the heimdall-1-click packages available, there are many options to restore from soft brick or return to stock.

jscott30 made a bunch of Odin packages as well if Heimdall is not working for that person.

Perseverance is the key. We have all been there. I can tell you that the more mistakes you make, the more you will learn. :)
[Samsung Infuse 4G] mikied12:
When my phone got stuck a few times and hung up in odin i by just sheer ahhh turned my phone on letting it go to the samsung screen then pulled the battery then put it in download mode and odin moved right along no just sitting there looking at it saying don't turn off.

In other words if it hangs in odin unplug pull the battery and turn it on first hopefully get your Samsung screen hold the power button until it turns off then do download mode, or pull battery then put it back and do download mode.

With me odin just took off and did its thing both times I bricked it bad.
[Samsung Infuse 4G] Azrael-09:
Thanks, thats something to try as it couldnt hurt, lol. let ya know what happens.
[Samsung Infuse 4G] Azrael-09:
Oh and in replay #18, Pony Express mentions using the same ports for heimdall as odin and there being problems. I did notice that once one works in that port, it may not work in the other. I found that by using "USBDeview" and running it as an admin, i can remove the installed drivers for samsung on my computer then re-attatch the cell phone and have them auto-upload again. Thus, making the port available.
[Samsung Infuse 4G] Azrael-09:
Well i tried it and as soon as i unplug it says FAIL! in red and does this:

<ID:0/019> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> PDA_UCKD5.tar.md5 is valid.

<OSM> PHONE_UCKD5.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/019> Odin v.3 engine (ID:19)..

<ID:0/019> File analysis..

<ID:0/019> SetupConnection..

<ID:0/019> Initialzation..

<ID:0/019> Set PIT file..

<ID:0/019> DO NOT TURN OFF TARGET!!

<ID:0/019> Get PIT for mapping..

<ID:0/019> Firmware update start..

<ID:0/019> factoryfs.rfs

<ID:0/019> Removed!!

<ID:0/019> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Last 3 lines after i unplug.
[Samsung Infuse 4G] Azrael-09:
I was curious though.. someone said i pretty much gotta go GB now but when i had my phone i could never get it to update to GB. ATT wouldnt let me, so i was always stuck with FROYO.

That matters with the pit file doesnt it?

Just to recap:

Im using (tried) both Odin 1.7 and 1.84

Files are from GTG's_Ultimate_Unbrick.zip

Files are: infuse.pit PDA_UCKD5.tar.md5 and PHONE_UUCKD5.tar.md5

Yellow com box lights up after the proper drivers are installed ( USB Composite Device, Samsung USB Composite Device, Serial gadget (modem), and USB2.0 UVC VGA

3 boxes are checked, hit start...

Pretty much it.

Version 1.84 has a "bootloaders" upload box. Im assuming i have a pretty good chance of messed up bootloaders. Should i install new ones?
[Samsung Infuse 4G] Azrael-09:
Is there a version of Heimdall where i can load my own files? cause i cant download any of them that seem like they are what im looking for.

I need one that has a "Load Package" tab.

Please let me know if anyone knows of one.
[Samsung Infuse 4G] qkster:
http://www.glassechidna.com.au/products/heimdall/

http://xdaforums.com/showthread.php?t=1348392
[Samsung Infuse 4G] drnecropolis:
Actually.. I have the gtg unbrick that will revert back to froyo on my computer..

I can zip it up and upload to my DB if you want to try it..
[Samsung Infuse 4G] Azrael-09:
That would be awesome if you could.. still no luck on this end...
[Samsung Infuse 4G] drnecropolis:
Yeah.. gimme a few and I'll get ya squared away..

Hell, with the GTG unbrick I have, you can still root with SOC.. lol

Don't make me get the hose!

---------- Post added at 07:04 PM ---------- Previous post was at 06:35 PM ----------

Aright.. here we are..

Link to a page with directions:

http://db.tt/wvppWrrh

The infuse .pit file:

http://db.tt/Vx1061Jz

And the gtg unbrick file:

http://db.tt/ZnR0vnk3

The version of odin I used to unbrick my infuse is also in the zip file.. follow the directions to the letter!

Don't make me get the hose!
[Samsung Infuse 4G] Azrael-09:
WE DID IT!!!

I got it all booted and back to stock ATT!!!

WooT! lol

Allright, gimme a sec to re-configure, re-root and re-install Aeon and ill go through the steps to show what we accomplished
[Samsung Infuse 4G] Azrael-09:
I didnt use the odin one you just posted, im sure it would have worked but i found a different way. ill post in a bit!
[Samsung Infuse 4G] drnecropolis:
Damn.. all that uploading and zipping for nothing..

Oh well, maybe someone else will see it and need it..

Don't make me get the hose!
[Samsung Infuse 4G] Azrael-09:
I really appreciate your hard work and trust me, it wont go un-noticed. Thank you, and THANK YOU ALL for your help!! Post to follow..
[Samsung Infuse 4G] drnecropolis:
I was joking around.. its no big deal.. I'm just glad you got it working!!

Would it be good to move these links into the ISET thread in case anyone wants to goto froyo?

Don't make me get the hose!
[Samsung Infuse 4G] Azrael-09:
The semi-hard-bricked phone...

Ok so basically I flashed about 6 roms before i reached Aeon 1.4. Which, by the way, is amazing.. Love it. I then decided to try out the" unofficial CM-9 mod" for the ICS look and bricked the crap outta my phone... I had no CWM, no Samsung logo, nothing... the only thing i could do was go into download mode.

Heimdall and Odin were used with about 4 pit files each and many different methods and attempts. I used different U.S.B. cords, ports.. etc.. The computer would not recognize drivers.. KIES recognized them but they weren't "correct", as it seems KIES has some problems. I basically let windows update find the drivers for me.

To do this i used "USBDeview" (ran as admin) to select and delete the usb drivers already in place and then re-plug and put phone into download mode while letting windows updater download the drivers for me.

No Heimdall was working for me so i assumed i must be missing my primary or secondary bootloaders (used to find more ram to load the next bootloader then package, then third bootloader which loads the kernel (basically the O.S.).

So (now my 6th day into it) i searched forums and such until I found someone who had used Heimdall to extract all files associated with a FROYO based Infuse 4g, before it was rooted, Then with the help of soon-to-be-mentioned individuals, was able to find a package loader version of Heimdall where i could upload those packages manually and re-attempt a flash. Lo and behold... IT WORKED! Version is found here http://www.glassechidna.com.au/products/heimdall/ and it is the first one listed in the category "Old releases" (Heimdall Suite 1.3.1 (Binaries)). It has Heimdall Frontend, which was what i was looking for. I loaded (gtgbacktostockheimdallwCommV8.tar) which contained all original files.. Firmware, kernel, cache, modem, etc.. and it did it.. Not to mention once it reinstalled it was still rooted and had CWM (PERFECT) all i had to do was go into CWM (red) from there and wipedata/format and wipe dalvik cache.. instal zip (Aeon 1.4) from zip and re-boot.. Good. as. new.
[Samsung Infuse 4G] Azrael-09:
Many thanks!!

Just wanted to drop a post in here and say a thank you to everyone that helped.. you know, besides the "Thank You" button.

Pony Express

qkstr

Thank you guys for all your support, knowledge and sticking with me through all the BS, you were tons of help

drnecropolis

Thank you for going the extra mile and attempting to help me fix my problem, awesome. =)

omanstevo

andros11

kenetix

bigjoe2675

An1mus

psal217050

mikied12

Thank you for all your help, each bit of info i received was used, tried, or used in the effort to further me in research leading to the solution.

Thanks everyone! I'll still run through the posts from time to time and if anyone needs any help i got your back, just PM me and ill help you with your problem!

Sorry for the rant, i just beleived that you guys deserved a thanks to let you know you were appreciated... Hit me up anytime.
[Samsung Infuse 4G] drnecropolis:
Don't sweat it broham.. the infuse community is amazing..

Hell, I don't even have an Infuse anymore but still check this section everyday..

You won't find a better group on this entire forum.. They are the best..

Don't make me get the hose!
[Samsung Infuse 4G] qkster:
Good job.

If you got heimdall frontend to work, you now understand about the pit file use and how to individually flash what you need.

Ex: modem, kernel, recovery, boot loaders etc

It's a good tool.

On the pc usb port that you were able to flash the phone in dl mode, save it for future restore to stock.

Check out some of the heimdall one click packages i put together

Now that you did your due diligence, you will understand.

Gl
[Samsung Infuse 4G] Azrael-09:
Yeah, definitely I'll check it out. Thanks!
[Sony Ericsson XPERIA X10 Mini] 00DSoul00:
Greetings!

I have a x10 mini pro with the locked bootloader, I can not unlock that to check with s1tool: Not Reconozigned certificate, plus I have changed the IMEI because I lost the signal when installing the ROM MiniCm7 pro v21

I want you to help me with a stock ROM keenel that is good and stable and do not spend enough battery ...

I want to change the ROM since most applications Gplay (Google play) are ceasing to be compatible with Android 2.1) and I want to change the ROM or find some way that applications that run on Android 2.2 on, run on Android 2.1

I hope I can help, thanks!
[Motorola Atrix HD] amccue:
So I have a rooted ATT atrix.

The screen brightness is awesome for some things but way too bright for others.

My question: Is there some way to lower the brightness settings even further than the lowest stock brightness?

I know that on certain custom roms you can go into the sys files using ES Explorer and change values there, but I'm not an expert in any sense,

I would like to keep the automatic brightness adjustment intact, just lower the range of brightness
[Motorola Atrix HD] amccue:
If I navigate to /sys/class/backlight/lcd-backlight/ then I can edit the file "brightness" to value of 1 which lowers the brightness significantly. The default minimum value seems to be 21.

When I do edit this value, then allow the screen to auto adjust brightness, the value goes back to 21.

I don't know where to set the range for the auto brightness.

I think lowering the range will save my eyes at night and also potentially save some serious battery
[Motorola Atrix HD] amccue:
https://play.google.com/store/apps/details?id=com.nnevod.loggraph&hl=en

I guess using this app will get what I want done. it'll just take some personal calibration
[Motorola Atrix HD] mandrsn1:
That is the app I use. Works well.
[Motorola Atrix HD] gabo_e30:
At night i use screen filter... its great and a lot simpler! U can find it on the play store

https://play.google.com/store/apps/details?id=com.haxor
[Galaxy S III General] sorg:
For me, it looks like:

- syscope process doesn't check ROM with every boot, but only after some event happened. This looks weird, because it looks that syscope always scan background processes at every boot and changes status to "Modified" if it finds any non-white listed root process, su binary or adb in root mode.

- you clear somehow trigger to let syscope thinks it still on the same already checked ROM.

This instruction looks too obfuscated. I believe steps count can be reduced significantly.

I'm not going to repeat this whole sequence because i have too much apps preinstalled and my ROM is heavily modified, so there is no way syscope will like it :) :)

I think, system state will change to modified if you will start to use more applications requiring root access. Just by some strange bug in syscope, exactly in your case and set of apps your ROM still not triggered "modified" flag.
[Galaxy S III General] mnitstanley:
Thanks for the good will and instructions. However, I will request you to post a video to avoid any gap between what we read and what you meant. Also, "TO SEE IS TO BELIEVE" :thumbup:

Sent from my GT-I9300
[Galaxy S III General] mossy1963:
@sort

There are not that many steps. It's actually quite straight forward, I've simply tried to break it down and make it as simple as I can for people less experienced who really want to do ota upgrades as well as the more experienced.
[Galaxy S III General] mossy1963:
There is a video in jayce ooi's web page.

Actually...in this case, doing its believing. Suck it and see.

To be honest I really don't care whether people do. I just couldn't sit here any longer and ignore the incorrect advice when my own research and experimentation has proved something different.

This SHOULD be a great help to people. I'm in work at the moment (unlike some of the serial posters round here apparently) so I won't be able to respond to every question very quickly. This is a developer community, I'd expect people to try for themselves. But check my profile...I wouldn't make something like this up.

Best of luck to anyone who has a go...it's not that tricky.
[Galaxy S III General] slaphead20:
interesting, I genuinely would give this a try if I needed it, but I don't! But it is a question that I've asked myself a few times.

On another note, it's easy to judge "serial posters".......but maybe check their profile before doing so ;)
[Galaxy S III General] mossy1963:
Haha...agreed. That is very naughty of me (slaps back of hand)
[Galaxy S III General] JJEgan:
Some cereal posters earn good money sitting in front of a computer .

Of course if Samsung service centres actually follow the instructions from Samsung in regard to rooted phones and actually look for rooted applications warranty will be invalid anyway . However not many of them actually bother to check to deep in that regards .

Samsung Notice GSM 10-71 Abnormal System Change Warranty Guide .

jje
[Galaxy S III General] carrd:
Has anyone tried to see if the SKY GO app in the uk works after this? I am sure I read somewhere that the app checks the modified atatus so if this method allows you to keep root but with a device status of Normal. This should work right?
[Galaxy S III General] slaphead20:
would be very interesting to see what happens with banking apps as well?
[Galaxy S III General] mossy1963:
Sky go does not work on jellybean yet.it says so quite clearly on play market if you want to check it out.
[Galaxy S III General] carrd:
Hopefully someone who has followed the steps will be able to test for us?
[Galaxy S III General] mossy1963:
@jj. :) I was being cheeky regarding serial posters, apologies if I offended anyone.

It's a given that anyone who uses this method and flashes a stock for return to Samsung will not have any tell-tale apps

Ps. "Cereal posters" conjures up all kinds of wonderful images :)
[Galaxy S III General] slaphead20:
The secrets out... jjegan.... international man of mystery is, in fact, a coco-pop! :D
[Galaxy S III General] mossy1963:
Yes if anyone finds any breakfast cereal in their letter box we'll know who to blame.....won't we jj?

:)
[Galaxy S III General] carrd:
I have spent my lunch time researching this and from what I can gather even if this works there is a background service that runs periodically that checks if device has been modified and set status to modified. so even if this process does work it will revert back to modified at some point.

Does anyone know more about his backgorund service? If so could it be disabled?
[Galaxy S III General] slaphead20:
I think it is syscope, earlier someone mentioned it, apparently it scans at boot, wether this is true or not, I have no idea
[Galaxy S III General] carrd:
Thanks, surely it can be disabled then? does anyone else know syscope
[Galaxy S III General] mossy1963:
The difference is I have done it...still unmodified and have been for days...another urban myth?
[Galaxy S III General] Kickasskev:
What would the result be if any of them stages were done INCORRECTLY eg battery pull timing.

Or is it a fail safe thing that CAN'T go wrong :)
[Galaxy S III General] slaphead20:
I would suggest being extremely careful when using triangle away with the phone back off, just make sure battery doesn't drop out while it's doing its thing, as triangle away has potential to brick device, so timing of removal is pretty critical at that stage I'm guessing. Nothing proven but just be careful
[Galaxy S III General] mossy1963:
Remains as modified status...for some reason interrupting the boot sequence is important, don't know why...why don't you try it and see?
[Galaxy S III General] JJEgan:
A little experiment on custom rooted rom for research purpose only .

Followed all stages boot to OS reboot device status is normal with factory restored custom rom .

to recovery and using a Nandroid backup restored Data Only

Boot up in system status it scans Device Status and shows modified now .

Remove syscope from custom rom and flash .

Boot and on status now says modified >> thats with syscope removed .

jje
[Galaxy S III General] olisun39:
How can custom binary download be NO when custom recovery is still loaded on the phone?

I tried the instructions in post 1 3 times now and the status is still custom and counter is 1

But now if I flash a original rom then the status changes to Official but the counter still remains 1
[Galaxy S III General] mossy1963:
Just to let you all know, just got home from work, dowloaded DLJ4 via checkfusdownloader, flashed via mobile Odin.

Worked a treat and now have stock 4.1.1 BTU, cwm and rooted, totally official unmodified.

Status in settings still indicates "normal" , OTA update says "latest updates have already been installed" (as opposed to failing).

Download mode indicates

custom binary download: No

system status: official

....it doesn't get any better than that...the proof of the pudding is in the eating s they say
[Galaxy S III General] mossy1963:
if you follow these instructions to the letter it will work....but to be honest I don't care.

Thought this would help all those who are finding this an issue...but getting mostly negative responses or cynicism.

I did this research and testing for myself. I have latest 4.1.1 firmware, rooted with zero binary counter and official unmodified status, should I ever wish to upgrade via OTA, Kies or return to Samsung.

If it works for anyone else...great...if it doesn't, you're doing something wrong
[Galaxy S III General] onesolo:
I can only say this:

Flash the damn firmware with mobile odin!!!
[Galaxy S III General] shawnhalu:
thanks mossy. i follow the guide & watch the video on jaycee. i was able to rooted and remain device status normal :) just fyi, i start from step 12.. =D
[Galaxy S III General] shawnhalu:
just start from step 12 and follow all the step. and u will get it. it flashes to 0 counter NO, it did not wipe the recovery so u can go in and wipe user data and cache

http://www.jayceooi.com/2012/06/19/how-to-unroot-samsung-galaxy-s3-video/
[Galaxy S III General] mossy1963:
mate I could kiss you!

As you say 1...11 is basically preamble to check status. from step 12 is where the action starts. (I may edit OP)

But I am truly grateful for you diligently following my guide and proving that it works....thank you very much
[Galaxy S III General] sorg:
Removing syscope.apk will definitely trigger "modified" flag.

Samsung programmers were smart to check in framework and SecSettings for presence of syscope.apk and trigger "modified" flag if absent.

So, need serious cleaning in framework, SecSettings and may be other services from syscope to completely remove check.

Or, find who exactly writes this flag and patch it out. I couldn't find it yet.
[Galaxy S III General] carrd:
I cannot wait to finish work and go and try trhis out. However with no intention to annoy anyone I have one question;

People that have used this method and got it working is it continuing to show status as normal, I read somewhere that syscope periodically checks for root and if finds it changes status anyone. therefore suggesting that even fiollowing this after using root apps that syscope may then pick this up.
[Galaxy S III General] bunglebp:
Hey all,

any ideas, I used Triangle away but it sets the counter to zero without resetting device, galaxy s3?? made sure device counter is not 0 ;)
[Galaxy S III General] mossy1963:
My phone status has remained unmodified since I did it over a week ago and despite flashing UK jb via mobile Odin earlier this week, still rooted. The theory about it changing to modified is pure speculation. I do find that irritating when people post speculation and misinformation. That's why I posted this in the first place
[Galaxy S III General] Eoy:
I did everything as explained here, and succeeded 2 days ago. But today, after I shut down my phone and turned it on again the status changed to "Modified" . Any ideeas?
[Galaxy S III General] mossy1963:
no mate...not a clue sorry
[Galaxy S III General] bala_gamer:
Too much steps for a simple process.

Step 1:

Install triangle away and clear your counter.

Step 2:

Enter cwm and factory reset,format system,format preload and cache.

Step 3:

Install any new rom and now your device status will be normal :)
[Galaxy S III General] ickoicko:
What I did before was:

1. Installed TriangleAway.

2. I pressed Reset Flash Counter.

3. I checked download mode and in Odin it says No and Samsung official.

Got weird when I realized I flashed 2 roms after that and it's still 0. I thought I broke my counter (lol) till I saw this post.