Database Info

whats the current att build for infuse 4g?

i have to send my infuse in under warranty, so which verison of stock should i use?
i know att will want me to have the most current operating system installed when i send it in.
thanks guys

I would just flash gtg's unbrick and the search updates under settings.
Sent from my SAMSUNG-SGH-I997 using XDA App

After using unbrick, restore to factory once booted so that it will hopefully erase all traces.
Cranky...

shg-i997uckh1
but you might want to flash ke3 and find a bootloader dump from it. if you updated to current bootloaders i believe it has a counter for number of 3rd party firmwares flashed to it. dont want the insurance company to see that. i dont know if this coulter counts cwm flashes or just download mode flashes but it somewhat can distinguish between att official and not atleast on the kernel end.

[Q] reset bootloaders/dl mode counter?

i know that the infuse bootloaders or w/e it is.
(when you enter recovery and push up to go into download mode)
tracks flashes, and currently has me at one
how do i erase this or set it back to zero basically?
flashing gtg unbrick and upgrade ota maybe?

The_Zodiac said:
i know that the infuse bootloaders or w/e it is.
(when you enter recovery and push up to go into download mode)
tracks flashes, and currently has me at one
how do i erase this or set it back to zero basically?
flashing gtg unbrick and upgrade ota maybe?
Click to expand...
Click to collapse
your gonna need the old bootloaders. a member dumped them a long time ago but i dont think any one tested them. the developers name was lost1 maybe the download link is still active. if you do the ota it will try to flash only the sbl.bin which will be for froyo an might not be compatible with the gb initial boot loader. if it's not it could either lead to a perma brick or it just wont flash at all since ther seems to be some signing on the bootloaders. the froyo bootloaders that were dumped were never really tested and the device might not accept them back either. there is a chance you are stuck with the counter and will have to pay for repairs.

edit: just flashed gtg unbrick and it resets the counter to 0 .

The_Zodiac said:
edit: just flashed gtg unbrick and it resets the counter to 0 .
Click to expand...
Click to collapse
Are you sure that's not an 8? Cuz if the unbrick resets it that means that the counter information is likely stored in param.ifs being that I don't think gtg packaged the bootloaders and that's the only partition I haven flashed that its in the unbrick. Which makes it hilarious that they made it so easy to reset.

Dani897 said:
Are you sure that's not an 8? Cuz if the unbrick resets it that means that the counter information is likely stored in param.ifs being that I don't think gtg packaged the bootloaders and that's the only partition I haven flashed that its in the unbrick. Which makes it hilarious that they made it so easy to reset.
Click to expand...
Click to collapse
Yes I'm sure because it's blank and says stock when its at 0. Lol I was very relieved.
Sent from my SAMSUNG-SGH-I997 using XDA App

How to Unroot/Return Stock

So just like that gentlemen, my SGT 7 Plus seems to be giving me trouble. It randomly shut off today and then wouldn't boot up again until I tried about 7 or 8 times. The tablet itself is great and I had no complaints with the build quality. I'm guessing it's just a lemon; will get it replaced.
Just wondering if I can ask if there's some way to unroot the device. I'm guessing I can just replace the stock recovery by using the back-up that was made during the CWM flash.

I think you could also just do a restore via kies.
Sent from my GT-P6210 using Tapatalk

Thanks! I'll just wait for some more suggestions before I go ahead. I've never used KIES before to be honest. All my previous devices have been HTC. I bought a Galaxy S II and never looked back.
How exactly do you restore via KIES? Is there something I should know about at the risk of soft-bricking it?

somebody9 said:
So just like that gentlemen, my SGT 7 Plus seems to be giving me trouble. It randomly shut off today and then wouldn't boot up again until I tried about 7 or 8 times. The tablet itself is great and I had no complaints with the build quality. I'm guessing it's just a lemon; will get it replaced.
Just wondering if I can ask if there's some way to unroot the device. I'm guessing I can just replace the stock recovery by using the back-up that was made during the CWM flash.
Click to expand...
Click to collapse
use odin3 to restore one of the stock images that are posted in the development section. there are instructions there. I've done it at least 10 times - works fine

Thanks! Gary suggested I do the same. Good to know it works.

is there any visual mark like yellow or blue triangle on the boot screen (like other samsung device do) on GT7+ that saying our device has been flashed?
I heard samsung has a flash counter, and Im afraid if I flash even if it's stock firmware (if the counter truly exist and visually appear) the warranty will be void...

Could somebody confirm this? I'd like to avoid complications with returning the device..

somebody9 said:
Could somebody confirm this? I'd like to avoid complications with returning the device..
Click to expand...
Click to collapse
Why would there be complications? Its the stock rom, any flashing is STILL the stock rom. if you boot up odin it will say no to custom binary download and also samsung official. You should be good.

otamctech said:
use odin3 to restore one of the stock images that are posted in the development section. there are instructions there. I've done it at least 10 times - works fine
Why would there be complications? Its the stock rom, any flashing is STILL the stock rom. if you boot up odin it will say no to custom binary download and also samsung official. You should be good.
Click to expand...
Click to collapse
so if I flash stock fw there would be no flag/counter and I would be good?
how about you bro?, is there any visible mark on boot after u flash stock firmware?

dewadewi said:
so if I flash stock fw there would be no flag/counter and I would be good?
how about you bro?, is there any visible mark on boot after u flash stock firmware?
Click to expand...
Click to collapse
Nothing that I can see, but I am no expert. I don't know what would be indicated when and if we get custom roms, but the stock ROM flashing does not appear to be flagging anything. Just as a fair business practice I don't see Samsung denying service/warranty for loading the firmware THEY provide. Custom, yes. Stock, no.

My flash counter appears to stay at zero

I have flashed and reflashed roms probably over 15 times since i got my phone. I have read that booting in download mode, you can see a small white number that says your flash count. When I go there I see no number anywhere at all. It says my binary is official and system status as modified. I have downloaded triangle away and when I go into that app, it also says my flash counter is 0 and my binary is official. I have the samsung custom unlock picture boot screen. Is this normal or should I have a flash count? If its normal what triggers the flash count? Also just to make sure, if I ever need my phone to be totally stock and remove the boot unlock screen and modified status I just have to follow the guide to return to stock which involves download mode and a windows pc, right? ( Cant remember the name of the windows app you use for that)

sfetaz said:
I have flashed and reflashed roms probably over 15 times since i got my phone. I have read that booting in download mode, you can see a small white number that says your flash count. When I go there I see no number anywhere at all. It says my binary is official and system status as modified. I have downloaded triangle away and when I go into that app, it also says my flash counter is 0 and my binary is official. I have the samsung custom unlock picture boot screen. Is this normal or should I have a flash count? If its normal what triggers the flash count? Also just to make sure, if I ever need my phone to be totally stock and remove the boot unlock screen and modified status I just have to follow the guide to return to stock which involves download mode and a windows pc, right? ( Cant remember the name of the windows app you use for that)
Click to expand...
Click to collapse
the only way the flash counter is tripped if you flash custom software in odin.

Ok thanks for the info. Is there any reason for a non developer to flash custom software in Odin, like some kind of non stock release or tool?

sfetaz said:
Ok thanks for the info. Is there any reason for a non developer to flash custom software in Odin, like some kind of non stock release or tool?
Click to expand...
Click to collapse
We cant until the booloader is unlocked.

I don't know but I really don't mind if my flash counter gets to be 10000. Isn't this just for Samsung to gage how much development is being done? Why else would they care if we flash ROMs?
Sent from my SCH-I535 using xda premium

They also probably use it to see if people have tried to hide rooting the phone if you send it in.
Sent from my SCH-I535

Bricked....Ugh

Ok so I've been rooted and unlocked for a while now, but stayed with the stock rom as when I tried out Synergy Nightlies it gave me some errors. So I went to try out CleanRom 2.1, people liked it and I didn't notice any flashing errors. So I flashed it through CWM 6.0.1 and it gave me the yellow exclamation mark saying I had unauthorized data on my phone. So I followed the sticky on how to unbrick my phone using the 2 boot loaders and the root66 stock image. My issue is that when running the root66 stock image through Odin it fails at _XmitData_Read, which seems to be somewhere in system.img.ext4. I've tried rebooting the computer, the phone, Odin, it just doesn't work. So when I reboot my phone after the failure I get Odin auto loading saying:
Odin Mode
Product Name: SCH-I535
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Qualcomm Secureboot: Enable
Then an image of a phone, 2 dots, a yellow exclamation, 2 dots and a computer are shown with the message "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Anyone able to help me?

can you still get to odin mode? also if you have kies installed on the computer erase it.

kidhudi said:
can you still get to odin mode? also if you have kies installed on the computer erase it.
Click to expand...
Click to collapse
Kies isn't installed on the computer and yes I am still able to get into Odin Mode.

I'm under the impression that "unauthorized software" message comes from the locked bootloader (if I'm wrong about that someone plese correct me.)
Sounds like you're functional enough to be able to Odin back to stock and go from there - that's what I'd try. See the stickied thread in the Q&A forum.

I would run the FULL VRALF stock image through ODIN to return to stock. That is always the safest way out of a sticky situation.

Thanks guys, according to another post the version of EZ-Unlock I used most likely gave a false report and never actually unlocked my phone. The problem with going back to stock, which if what I'm trying to do, is that it fails.

Could be an USB issue - an intermittent connection would be most likely to cause problems while sending the system partition since that's the biggest. I've had problems using adb from time to time if I plug into one of the front-panel ports on my PC but no trouble with one on the back.
Maybe try switching ports or try a different cable ...

Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app

Strange.... i was able to flash syergy on thefirst try. Never used odin during the whole process....
If youre rooted you need to make sure you have a custom recovery in place like cwm or twrp. Make sure you make a nand-backup.
I used casual to flash unsecure bootloader, with that and recovery in place you should be able to flash roms without any hitches....
I could never find a comprehensive guide on using odin so i never got around to testing it

kintwofan said:
Actually what usb plug are you using on your computer? You should be using one in the back of your computer by the power supply. Seen the front jacks not work correctly for large transfers. Finally, try another usb cable.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So far I've tried 3 different USB cables and both a desktop, both front and back ports and a laptop, each one fails on the write of XmitData under system.img.ext4
I had a custom recovery installed and Odin is only being used to get me back to a stock rom, otherwise I did all my flashing under CWM 6.0.1 or twrp. I think the whole fake unlocked bootloader just hard bricked the software.
EDIT: Come to think of it I remember waking up to my phone in download mode. I think Verizon tried to install the update to my phone while I was sleeping. Granted it failed at the end, but I'm wondering if that did something to brick me now.

If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app

kintwofan said:
If you can get in download mode it can be saved. I woud re download the stock firmware or the 66, but personally i would go bone stock. You may just have a bad download.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Yea, I'm currently downloading at the speed of slug the newest update from the forums, will probably just redownload at home, since it's going to take over an hour >.<
EDIT:
Does anyone have a link for an older EZ-Unlocker, that is known to work, so that I don't get this problem yet again.

FIXED!
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.

LlirasChosen said:
Ok, so using the newest stock rom from the dev forum worked. Can someone please give me a link to an old EZ-Unlocker so I can flash without worrying about another massive brick in my palm. I'm guessing that running the original root66 stock rom through dropbox somehow corrupted it.
Click to expand...
Click to collapse
I personally suggest not using the app if you already had trouble. Just root your phone using the Debug Root method in Development, download the aboot.img from Adam Outlers thread HERE to your phone, and run the commands at the very bottom in Terminal Emulater app (from the market).
That way you know for sure your bootloader is unlocked. This is what I have done and never had an issue.
Edit: Glad you got your issue resolved!