My SGH-T999 ids itself as SGH-i747 in download mode. Is this typical/normal? I'm having trouble flashing full ROM tars with Odin. I can flash other things with it, like CM, but never a full ROM. I'd appreciate it if one or more people could check theirs and report back, or if you just know this is normal (or isn't!) if you could please just let me know.
If you're curious and want more background, look in this thread here where we're trying to troubleshoot:
http://forum.xda-developers.com/showthread.php?t=2672790&goto=newpost
Thanks, all.
UPDATE:
Just thougth I'd update this for anyone who stumbles on this thread in the future.
While everything about the phone from the outside and most of the stuff shown by Device Info indicated it was in fact a T999, apparently it did have an SGH-i747 bootloader. I overwrote that bootloader with an SGH-T999 bootloader, and hardbricked it.
So don't do that.
Talked to a JTAG-er who said that if the download screen says SGH-i747, it has an i747 motherboard.
Word of caution to others who end up with a refurb frankenphone.
Well, it looks like it happens sometimes, anyway.
But this solution won't help me, as the problem is bigger than this.
http://forum.xda-developers.com/showthread.php?t=2088220
What is the Model Number Listed behind the Battery on the White Sticker ? Also which TAR packages you have been trying to flash ?
Sticker says SGH-T999
When you say its i747 in Download mode, did you mean the "Downloading" screen on the phone ? If that's not it, then please specify.
Perseus71 said:
When you say its i747 in Download mode, did you mean the "Downloading" screen on the phone ? If that's not it, then please specify.
Click to expand...
Click to collapse
Sorry, I didn't see this thread update. I thought we were talking on the other thread once I saw you posting over there.
Yes, that is the screen I mean. The downloading screen. (vol down, center-button, power, little android guy, yellow "you've modified this puppy" triangle, flash count=1, QUALCOM SECUREBOOT, etc etc) That's the ONLY place I see i747. Sticker and build.prop file both say t999.
The build.prop file that came with it also identified it as a t999, but I got that replaced when I flashed a TMO image with CM. Did NOT change what shows up in download mode.
My theory is that the previous owner flashed an ATT image to the phone since the settings in the "original" build.prop file were for ATT in Canada, region was set to CN, and the language was set to zl or something similar. That file is on my machine at work ... don't have access to it right now, but point being, that build.prop also had the device properties set to a t999, i747 appeared nowhere in the file.
So, something on the phone is causing the download screen to show up as an i747. I'm thinking -- but I'm looking for alternate theories if someone doesn't think this is right -- that it's in one of the initial boot files. I don't know where the binaries are that run the download screen, but I think it's a good bet it's in aboot or one of the sbl files. I'm hoping someone can help confirm or deny or say "nobody knows, let's have a beer" or whatever.
I've tried to flash the TMO-UVDMD5 firmware (which does replace those files -- or it *would* if it would flash) from a zip file in CM ... but it fails on the assert(getprop... which is checking for d2tmo in either one of two properties. It's obviously not getting d2tmo. Whatever it's getting can't be getting it from the build.prop file, as both of those properties are set to d2tmo in /system/build.prop
My bet is that the Odin flashes are failing for the same/similar reason. There is something in the binaries on the phone that the flashing software doesn't like. I know it's safety checks trying to save me from myself, but this is not a normal situation - good chance the programmers did not anticipate this.
Now ... the long of it is, my IMEI was wiped and I need to restore it. But the IMEI restoring software won't talk to my phone because it uses RMNET and the RMNET driver loads and then dies within a minute after the phone connects. I suspect for the same/similar reasons that Odin won't flash a whole ROM and CM scripts cack out on checking to see what kind of phone it is through getprop.
I'm looking to build the phone from as low a level as I can to its original state as an SGH-T999. And then restore my IMEI.
Just thougth I'd update this for anyone who stumbles on this thread in the future.
While everything about the phone from the outside and most of the stuff shown by Device Info indicated it was in fact a T999, apparently it did have an SGH-i747 bootloader. I overwrote that bootloader with an SGH-T999 bootloader, and hardbricked it.
So don't do that.
Talked to a JTAG-er who said that if the download screen says SGH-i747, it has an i747 motherboard.
Word of caution to others who end up with a refirb frankenphone.
Related
I've thoroughly trashed my efs & nv items. Long story but basically, I went into dialer menu #*9090#, picked option #3 and, thinking I had multiple backups of everything, picked yes. Dumb? Yes.
My backups were on a hard drive that I'd replaced with an SSD and got lost during that replacement. I hadn't backed up the backups - only had the single copy now lost.
Phone will boot but now shows unknown baseband, borked IMEI. I can get into download mode and have TWRP recovery installed. WIFI works, I can easily get stuff on/off the device & access an ADB shell. It's rooted/stock UVALJ1.
I did find one backup, made using QPST (.qcn file), but in trying on two different PCs & a 32bit WinXP VM I cannot get the phone recognized by QPST (drivers installed, finds port, but "No phone".)
If someone can give me a TWRP backup of their efs I *think* that may get me fixed. I know that may contain your IMEI & if it fixes me but contains the wrong IMEI, that's fairly easy to fix, assuming all the posts on fixing that issue are accurate. I'm not trying to steal an IMEI, I'm trying to make my Note 2 usable as a phone again.
Sent from my Nexus 7 using Tapatalk
LanceDiamond said:
I've thoroughly trashed my efs & nv items. Long story but basically, I went into dialer menu #*9090#, picked option #3 and, thinking I had multiple backups of everything, picked yes. Dumb? Yes.
My backups were on a hard drive that I'd replaced with an SSD and got lost during that replacement. I hadn't backed up the backups - only had the single copy now lost.
Phone will boot but now shows unknown baseband, borked IMEI. I can get into download mode and have TWRP recovery installed. WIFI works, I can easily get stuff on/off the device & access an ADB shell. It's rooted/stock UVALJ1.
I did find one backup, made using QPST (.qcn file), but in trying on two different PCs & a 32bit WinXP VM I cannot get the phone recognized by QPST (drivers installed, finds port, but "No phone".)
If someone can give me a TWRP backup of their efs I *think* that may get me fixed. I know that may contain your IMEI & if it fixes me but contains the wrong IMEI, that's fairly easy to fix, assuming all the posts on fixing that issue are accurate. I'm not trying to steal an IMEI, I'm trying to make my Note 2 usable as a phone again.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Flashing EFS from another device is not going to work.
Try to recover the IMEI using KIES emergency recovery. http://forum.xda-developers.com/showthread.php?t=2261153
If this still does not work try flashing the UVALJ1 modem.
ciphercodes said:
Flashing EFS from another device is not going to work.
Try to recover the IMEI using KIES emergency recovery. http://forum.xda-developers.com/showthread.php?t=2261153
If this still does not work try flashing the UVALJ1 modem.
Click to expand...
Click to collapse
Can't seem to get KIES to connect - the most definitive result I got was a device not supported by KIES message after uninstalling/reinstalling drivers, making sure the phone is in the right mode etc. For the most part KIES just sits at connecting forever. This is the case with both the Note 2 and a Samsung Galaxy S4. KIES isn't exactly inspiring confidence it can magically restore my entire efs & all NV items...
Just to clarify, I can access recovery just fine - I can use Odin to flash to whatever albeit the bootloader is 4.3/Knox locked. I can flash modems, ROMS, etc and access ADB shell or whatever else I'd need to do with ADB. Can't seem to get KIES to work and as I understand it what you're telling me to do in KIES won't actually restore efs, it just resets it to a stock state and lets efs rebuild - assuming the NV items are still there, which they are not. I really hope I'm wrong and I'll have to come back here once I get KIES sorted out and tell you how silly I was for not believing you in the first place!
I did re-flash the modem using TWRP, no change there.
Here's the text of the warning I foolishly ignored:
Warning: Must read below guide
All Communication between AP/CP-
will be disconnected!
To return to normal mode,you
must download efs12.tar file!
All NV data will be erased!
Really want to use RmNET?
Click to expand...
Click to collapse
This was in the ServiceMode menu accessed with dialer code *#9090# but now there isn't a menu there - just a blank screen that says ServiceMode at the top. Dialer code *#0011# produces the same result - no menu where there used to be one, just blank screen/ServiceMode. Based on that warning, this isn't something I expect KIES to fix - but as I said, I hope I'm wrong about that...
Tried KIES on another PC with same result - that was 2.x KIES.
I used Odin 3.09 to flash to T-Mobile stock rooted 4.3 from this thread: http://forum.xda-developers.com/showthread.php?t=1975560
Switching to KIES 3 got KIES talking to the phone. It says I'm on the current version of the firmware (because I am - it's what I just flashed with Odin.) If I go into Tools/Emergency nothing is listed. If I go into the second choice and enter the model number with the phone plugged in, it tells me it doesn't support firmware initialization. If I do it without the phone plugged in, it works and accepts the serial number from the phone. If I plug the phone in right after I've gotten past this point, KIES winds up going off into never never land a bit later after it tells me everything is going to be wiped and the phone will be put back to its initial state (which does sound somewhat promising.)
Its spawning this AdminDelegator process which seems to just be sitting doing nothing and the KIES window is shaded. I can close it but that's about the only interaction possible with it in this state - none of the menus work and it seems like it's waiting on something to be clicked maybe in the AdminDelegator process but that process has no window anyplace.
It's possible there is something useful buried in KIES but it's a horrible piece of software. They seem to be authoring it on at best 32bit Windows 7 and that's a stretch, I suspect they're still targeting 32bit XP. I'm on x64 Windows 8.1. I could rant much more but I'll leave it at that.
I'm going to keep working with it and see if I can get around how they've written it or I might just stick it in a 32bit XP VM and see if it's happy back in 2005, software-wise. <G>
I may wind up giving up and just getting another phone - I've already read up some on my options and the funny thing is, I still want a Note 2 - they can be had for more reasonable $ now than a year ago anyway...
LanceDiamond said:
Tried KIES on another PC with same result - that was 2.x KIES.
I used Odin 3.09 to flash to T-Mobile stock rooted 4.3 from this thread: http://forum.xda-developers.com/showthread.php?t=1975560
Click to expand...
Click to collapse
Did you verify the IMEI after this flash ?
ciphercodes said:
Did you verify the IMEI after this flash ?
Click to expand...
Click to collapse
Short answer: IMEI & baseband same as before the flash - both are "Unknown".
Prior to my messing with the dialer menu, everything was fine. I'd used Odin or TWRP recovery to flash a variety of different ROMs the last of which was the 4.3 we're talking about here and it was working. I'd used it for several days. Everything but screen mirroring worked without any problem and I had service - I read up on the screen mirroring problem and it sounded like getting the device to show "Official" might help so I tried to reset my flash counter which I did not do before going to 4.3. Flash counter wouldn't reset so I decided to go back as far as I could on modem/ROM and see if I could reset flash counter then. (I know my Knox flag is not fixable - I was just trying to change the flash counter.)
Using TWRP, I installed UVALJ1 modem & associated ROM, leaving the 4.3 Knox locked bootloader in place to see if that'd work. It did, it booted and I had service. I was actually playing with the menus to see if the old dialer code free unlock menu settings still seemed to work because someone had posted about needing to unlock - looked like the menus were still there for doing an unlock. In messing with the menus I picked the option that messed everything up and since doing that, no matter what I flash, IMEI & baseband are unknown.
Unless KIES rebuilds the entire radio - which it very well might based on it needing the correct model and then wanting a valid serial # - I think I need an efs restore to get the phone communicating with anything now.
One thing I just now did - using the free NV Items Reader Writer from this thread: http://forum.xda-developers.com/showthread.php?t=1804117
On my Note 2 configured as "DM+Modem+ADB" in Qualcomm USB settings (the only of several dialer menus I know of that still actually exists & seems to work), I can see the modem & port in device manager. But the app cannot communicate with the phone. If I change nothing, unplug the Note 2, plug in my Galaxy S4 in "DM+Modem+ADB" mode, I see modem & ports pop up in device manager and now the app can communicate with the phone.
I'm afraid, based on the text of that warning and searching for what "AP" and "CP" are, that the phone isn't going to be able to communicate with much of anything until it gets its efs fixed. This test where I just swap phones seems to be comfirming that this phone isn't responding like it should. Basically my modem & the rest of the phone are disconnected right now - at least that's my understanding. If the modem really is disconnected then obviously trying to do something to fix it via the modem is never going to work. The KIES may work - if I can ever get it sorted out. Haven't yet tried it in a VM might do that right now...
Edit:
Got KIES3 & drivers working in Windows XP SP3 VM. KIES connects to phone but if I pick Tools/Firmware Upgrade with the phone connected it just says "SGH-T889 does not support initializing" and my only choice is "OK". If I go Tools/Firmware without the phone plugged in, I can enter the model # and then it asks for serial #. If I plug the phone in at the point it goes all the way to where it says it's downloading firmware and then same result as on Windows 8 - an AdminDelegator process gets started, KIES gets sort of dimmed like it's waiting on something and nothing ever happens. If I never connect the phone KIES goes through the downloading process then gets an error with options to send a message or cancel - no information about what the message is, what the error is - just I can send it, it won't contain personal information or I can cancel.
Hey guys, I have a Samsung Galaxy S3 for Tmobile SGH T999 and I had cyanogen on it until it crapped out and got hard bricked. AFter following these links, http://forum.xda-developers.com/showthread.php?t=1949687 and http://forum.xda-developers.com/showthread.php?t=2439367, I was able to unbrick my phone and get into boot recovery mode. However, when i try to flash the stock firmware in odin, I get an error (the error is shown in the attachment). Can anyone please help me? Sorry if im posting something wrong, I am new to this forum. Thank you!
After booting into download mode, take out the sdcard before flashing with Odin. Also if kies is on the computer, uninstall it.
DocHoliday77 said:
After booting into download mode, take out the sdcard before flashing with Odin. Also if kies is on the computer, uninstall it.
Click to expand...
Click to collapse
I tried this still doesnt work.
You said there was an error msg, but im not seeing it in the screenshot.
How exactly did you brick it though? Have you tried flashing MJC or NC2 firmware from Odin?
If you are still running MD5 or earlier, you could try flashing TWRP, then boot recovery and flash the recovery firmware package in the development section.
DocHoliday77 said:
You said there was an error msg, but im not seeing it in the screenshot.
How exactly did you brick it though? Have you tried flashing MJC or NC2 firmware from Odin?
If you are still running MD5 or earlier, you could try flashing TWRP, then boot recovery and flash the recovery firmware package in the development section.
Click to expand...
Click to collapse
Sorry i meant failure not error. I bricked it because my cyanogenmod was having problems and i tried to restore it, after i did it completely bricked. Sorry can you please elaborate what is TWRP, MJC or NC2 firmware, im dont have much knowledge about these kind of things. Thank you so much for helping me, it means alot to me and I will do my best to follow your directions.
Ok, ill explain better when I get to my computer. It'll be too much to try to type on this tiny device im using right now!
But for now, TWRP is a custom recovery, like CWM. You use it when flashing roms like CM.
MJC and NC2 are just the different firmware builds you can flash in Odin. We shorthand it by just using the last 3 letters of the build version. T999UVUENC2 is what im referring to when I say NC2.
Take a look at my firmware thread. Its stickied at the top of development. Linked in my sig too.
Let me know if this helps your understanding at all. Ill explain more in what to do shortly.
Thanks for that, it gave me a better understanding. I tried to install flash and this happens when i try to flash twrp or MJC on odin
Ahhh! PIT=Partition Information Table
Odin uses this to know the partition layout of the device so it knows where to flash each part of the firmware. It usually gets this directly from the device, but occasionally it becomes corrupted or lost.
There is a thread in the General section that has all our PIT files. Should be on the first page right now, maybe second. Download the correct one for your device. (My last post has a link to my repo with all PIT files)
Now try flashing your firmware again, do everything the same way, but this time check the repartition checkbox, and click the PIT button and select the .pit file you just downloaded. Now click start and it should work. We hope....!
DocHoliday77 said:
Ahhh! PIT=Partition Information Table
Odin uses this to know the partition layout of the device so it knows where to flash each part of the firmware. It usually gets this directly from the device, but occasionally it becomes corrupted or lost.
There is a thread in the General section that has all our PIT files. Should be on the first page right now, maybe second. Download the correct one for your device. (My last post has a link to my repo with all PIT files)
Now try flashing your firmware again, do everything the same way, but this time check the repartition checkbox, and click the PIT button and select the .pit file you just downloaded. Now click start and it should work. We hope....!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1848267 are you talking about this page for the PIT file? because when i clicked this link it doesnt work and it pops up as an unsafe page on my myWOT.
Ok so i found a PIT file for my phone and when i tried to flash with the odin v3.07 it got stuck on Leave CS. I looked up a solution for this and it was to use an older version of odin, v1.85. After i tried this I made more progress but it failed again.
ojhasha said:
http://forum.xda-developers.com/showthread.php?t=1848267 are you talking about this page for the PIT file? because when i clicked this link it doesnt work and it pops up as an unsafe page on my myWOT.
Click to expand...
Click to collapse
Yes that's the thread. Which did it say was unsafe? The thread itself, or my link in the post in that thread?
If its my link, it just goes to my folder on http://androidfilehost.com. its a file sharing site solely for android stuff from sites like xda. Its perfectly safe. If that's the one being flagged its probably because it has files you can download m
ojhasha said:
Ok so i found a PIT file for my phone and when i tried to flash with the odin v3.07 it got stuck on Leave CS. I looked up a solution for this and it was to use an older version of odin, v1.85. After i tried this I made more progress but it failed again.
Click to expand...
Click to collapse
Where did you get the pit? May be that its either a corrupt download or for the wrong device.
And did you try with Odin 3.09?
DocHoliday77 said:
Yes that's the thread. Which did it say was unsafe? The thread itself, or my link in the post in that thread?
If its my link, it just goes to my folder on http://androidfilehost.com. its a file sharing site solely for android stuff from sites like xda. Its perfectly safe. If that's the one being flagged its probably because it has files you can download m
Where did you get the pit? May be that its either a corrupt download or for the wrong device.
And did you try with Odin 3.09?
Click to expand...
Click to collapse
It was invisibleK's link that was unsafe. I used your 16GB Pit file in here, http://www.androidfilehost.com/?w=files&flid=6471 and i got the same result. I dont remember where i got the other pit. I got stuck on Leave CS on the odin 3.09 and when i click start it failed again with the repartition failed.
You are still removing the sdcard before flashing, right?
I have no idea if this could help, but theres a program here on xda called PIT magic. Maybe take a look in that thread to see if you find anything useful.
You can try flashing the PIT only, no firmware selected, but I dont know if this would work or not.
Only other thing I can think of is to try everything over again with the NC2 firmware.
Try that first, but you can also try flashing cwm or TWRP with odin. If we can get recovery on there we might be able to try other stuff with that.
DocHoliday77 said:
You are still removing the sdcard before flashing, right?
I have no idea if this could help, but theres a program here on xda called PIT magic. Maybe take a look in that thread to see if you find anything useful.
You can try flashing the PIT only, no firmware selected, but I dont know if this would work or not.
Only other thing I can think of is to try everything over again with the NC2 firmware.
Try that first, but you can also try flashing cwm or TWRP with odin. If we can get recovery on there we might be able to try other stuff with that.
Click to expand...
Click to collapse
sorry i didnt respond in a while, I was really busy with homework. I tried what you said and still no sign of success. I brought my phone to a repair shop and they said the motherboard is damaged and it needs to be replaced for 150$. I hope this guy is just bull****ting me, can anyone confirm? I really hope there is still light at the end of the tunnel right now.
Its hard to say. Motherboards do go bad, usually an issue with the memory. Its pretty rare, but it does happen, and the frequency has been increasing since these devices are starting to get a little old now.
But $150 for a replacement is, imo, a rip off. You can find used boards on ebay for under $100. If you csn use a screwdriver and can be gentle with the ribbon cables, its a super easy swap. Just check the videos to see.
DocHoliday77 said:
Its hard to say. Motherboards do go bad, usually an issue with the memory. Its pretty rare, but it does happen, and the frequency has been increasing since these devices are starting to get a little old now.
But $150 for a replacement is, imo, a rip off. You can find used boards on ebay for under $100. If you csn use a screwdriver and can be gentle with the ribbon cables, its a super easy swap. Just check the videos to see.
Click to expand...
Click to collapse
do you recommend me doing it? or are there more alternatives.
If the memory itself has gone bad, that's your best option. It is possible to change just the memory chip, but the part is probably hard to find and it requires a higher level of soldering skills.
There's a video of this, if I can find it again ill post the link.
Here's the video to the emmc replacement for international S3, should be similar but will require BGA soldering skills. https://www.youtube.com/watch?v=rOYo9AcUQQI
I thought about attempting to do this for my T999v, but a EMMC chip is about 35-50 bucks.
yellowonion said:
Here's the video to the emmc replacement for international S3, should be similar but will require BGA soldering skills. https://www.youtube.com/watch?v=rOYo9AcUQQI
I thought about attempting to do this for my T999v, but a EMMC chip is about 35-50 bucks.
Click to expand...
Click to collapse
did you have my symptoms? did you ever fix your phone? if so please share, i want to get my phone back in the cheapest way possible.
PS. I charged my phone today and the red led light showed up, that means my motherboard isnt broken right?
Not necessarily. It means there is a problem and requires special drivers and programs to fix, (or the debrick sd card). It basically just means the computer sees something is plugged in. If the memory has gone bad it could very well still give the red led and/or boot from the sd.
The only good way to verify the board (or memory) needs replacing would be to go to a second shop and ask them to attempt a jtag repair. If they tell you the same thing as the first shop, ask if they can be more specific about what happened when they attempted the jtag repair. At this point though, its a pretty good guess that the memory has gone bad.
First I want to apologize for posting again couldnt figure out how to upload picture, As I stated my friend rooted his phone and then installed wrong rom. Installed
Rom for lte version, then he had issues with efs file and someone edited them and fixed them, now this image I attachedis stuck on screen, wondering if I unroot and go back to stock will that fix issue that I have shown on attachment, thank you any help is appreciated
Sent from my SGH-T999 using XDA Free mobile app
just shooting from the hip here, you don't have a backup of your previous rom? if you do, and can still get to recovery, I'd wipe everything and flash that. Baring that, you could TRY to unroot it, but I wouldn't guarantee anything. Maybe someone else has better info than me
Yea he didn't do a back up, smh, so he attempted to unroot last night and he tried flashing stock 4.3 but Odin gave him a failed. Then asked him what android version he was previously on and he says maybe 4.2 or 4.3 now phone is saying connect to lies and run recovery and still can get to download mode, told him I will try to fix it and leave it alone, any help would be appreciated on what stock rom I should flash
try kies, there is an option for "emergency recovery", then just reroot
Do I need to put phone download mode and run recovery in kies? also to go back to stock which stock rom do i flash?
Cheony81 said:
Do I need to put phone download mode and run recovery in kies? also to go back to stock which stock rom do i flash?
Click to expand...
Click to collapse
no, just turn the phone on, then connect to USB... kies will determine the firmware...
Ok cool when I turn phone on it shows the connect to kies to recovery but recovery ask for some kind of code
Cheony81 said:
Ok cool when I turn phone on it shows the connect to kies to recovery but recovery ask for some kind of code
Click to expand...
Click to collapse
also when i turn the phone on and put it into download mode this is what i have on top left corner
ODIN MODE
PRODUCT NAME:SGH-T999
CUSTOM BINARY DOWNLOAD: no
CURRENT BINARY: Samsung official
SYSTEM STATUS: none
QUALCOMM SECUREBOOT: ENABLE
Warranty Bit: 1
BOOTLOADER AP SWREV: 1
You don't need to be in odin mode to use Kies, but since you can put the phone in odin mode, go to samfirmware and download the latest firmware, then flash it. You still might have to fix the EFS though.
ok cool thank you,, ok i flashed stock rom,everything went good, but i am stil having that image on screen still,which i attached earlier,any help on how to remove that image on screen? will rooting the device and flashing rom remove that image from screen?
ok after searching on google found out its factory mode image thats on the screen, i tried doing this(http://www.droidforums.net/threads/how-to-exit-factory-mode-to-user-mode-in-s3-help.239945/) but folder is empty and no back up, would like to know if there is a fix and can someone help please.thank you
Cheony81 said:
ok after searching on google found out its factory mode image thats on the screen, i tried doing this(http://www.droidforums.net/threads/how-to-exit-factory-mode-to-user-mode-in-s3-help.239945/) but folder is empty and no back up, would like to know if there is a fix and can someone help please.thank you
Click to expand...
Click to collapse
So is this what you did?
su
echo -n ON > /efs/FactoryApp/factorymode
Are you absolutely certain you typed it in correctly? What did it say after you entered the command?
You said the folder is empty, did you actually look at the /efs folder and it was empty??? If so, I'm not sure if theres much you can do tbh. There is device specific information there so it is unique for every device. You might be able to get some stuff back (non-unique type things), but I don't know about the rest.....DRM keys and more.....
If the folder is empty, how did you determine this? What app did you use to check it out?
You said you flashed your firmware via Odin right? Not Mobile Odin? Big difference so i just want to make sure.
It would be a big help if you could elaborate on your OP. What exactly did he flash, and how did he flash it? What was the original problem? What were the efs issues you eluded to? And more importantly what did someone edit and supposedly fix?
The only problem I have ever seen related to the efs on this device is the one you originally posted about, the FactoryMode window. Aside from that very rare issue, I have never seen any problem with the efs on the Qualcomm S3's. Many people automatically go there because OTHER devices store different information there and they expect it to be the exact same for some reason. Anyway, what I am trying to say here, is other than getting rid of FactoryMode, I can't think of anything else anyone would need to touch on that partition. This is why it is very important to know what the other person "fixed", and how.
In the meantime, go to Settings > About Device > Status, and verify the IMEI is there and that it matches the one printed on the sticker under the battery. (Am I correct in guessing all of this started with some sort of IMEI issue?) If the IMEI is anything but correct (missing, zeroed, incorrect, etc), PM me directly. Do not worry about posting again until we solve that. Chances are, if the IMEI is the problem, fixing it will solve the rest too. Unfortunately, we are not allowed to post, link or discuss that in the public forum, so I can only help via PM if that is the problem.
i have my friends phone and he's galaxy s3 is stuck on download mode and its looping there everytime
it happened out of nowhere, he wasn't playing around with it it just happened
now its stuck on downloading and wont go to recovery for me to initialize the device through kies or smartswitch
NO ACCESS TO RECOVERY MODE AT ALLL
i tried numerous ways to retrieve the phone into working condition but no success at all
thru odin i get the pit error and when i place a pit to repartititon with the stock tar file or the cwm recovery tar i failed
it says complete write operation failed and it takes a long time to set up connection with the device before showing me the fail
its a tmobile sgh-t999 prob 16 gb
any genius here got any ideas?
What firmware build was on the device and what build did you try to flash using Odin?
Did you try different versions of odin?
Different driver versions?
Different USB cable?
Different USB port?
If kies is installed on the computer, get rid of it. It interferes with Odin.
If none of that helps it may be a hardware failure.
Sent from my SGH-T999 using Tapatalk
The same thing has happened to my wife's phone and I have done almost the same steps to fix it with similar results.
If you tried everything I mentioned and are sure you weren't flashing an older firmware build (only after 4.3), then theres a good chance it's a hardware failure, probably with the memory.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
If you tried everything I mentioned and are sure you weren't flashing an older firmware build (only after 4.3), then theres a good chance it's a hardware failure, probably with the memory.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
OK, uninstalled Kies and tried to flash T999UVUEOH1_T999TMBEOH1_TMB rom with odin again and got there is no pit partition error. Would post some pictures of the boot screen and a screenshot of the odin program but need 10 posts. Well not sure what version was on phone before all this happened.) Also the ODIN bootloader screen says SYSTEM STATUS: NONE Warrenty Bit: 0 BOOTLOADER AP S?AEV: 1 among other things...forgot to mention I used ODIN v3.10.6 because v3.10.7 gave me a win32 error when I tried to run it on my Windows XP PC.
Here's my suggestion to at least get the phone running a ROM:
download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...5QWImOPDJboTA_V3D5S9eA&bvm=bv.107763241,d.dmo
download the tar version of TWRP 2.8.6.0 from here: https://dl.twrp.me/d2tmo/
download the latest cm12.1 for the phone from here and save it to a micro SD card: https://download.cyanogenmod.org/?device=d2tmo&type=nightly
place the micro SD card into the phone;
boot the phone into download mode;
open Odin 3.07 and uncheck everything except f. reset time;
click on PDA and browse to the tar TWRP file and select it;
connect the phone and it should show up as a com port in Odin;
flash TWRP;
when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
perform a full wipe of system, data, and cache;
flash CM12.1 from the micro SD card;
reboot the phone.
Hopefully, the above steps will get the phone booted so you can confirm the installed bootloader and modem.
Followed your guide step by step but flash failed in odin Get Pit for mapping..
There is no PIT partition.
All threads completed. (succeed 0 / failed 1):crying: BTW thank for all your help.
You got the pit error flashing twrp in Odin? Any other errors? What model number is shown at the top of the screen when the phone is in download mode?
The only times I've encountered this type of behavior it turned out to be a hardware failure (memory). If that is indeed the case here, I'm afraid there won't be much you can do for it. Don't get me wrong, I'm not saying you should just give up, but you should probably at least start looking at other options.
The main reasons I believe this to be the case are
1. It just died while nothing was being done (not being used)
2. Pit errors indicate either the partition table has been corrupted, or the partitions themselves have. Because it cannot detect any system (SYSTEM STATUS: NONE), it's more likely to be the partitions them selves, not the partition information table (pit).
Something else that doesn't look good, (but that I've never seen before) is the S?AEV. It should be SWREV. (Software Revision). It may mean nothing, but I've never seen it before so I thought I'd point it out.
As I said, I'm not saying you should give up yet. I've been wrong before and I'd hope to be again in this case. But I wouldn't put too much more time and effort into it as I've never seen one of these types of failures restored. They are pretty rare, but they do happen.
My best suggestion at this point is to start looking into replacing either the motherboard or the device. Motherboards can be found for reasonable prices, but you do have to be careful when buying one. (Let us know if you want to do this and we'll give you some tips on what to look for).
I'm sorry that this happened and that there doesn't seem to be much I can do to help. If you had any important data (pics or whatever), there's a small chance it can still be recovered. Don't get your hopes up too much for it, but using ADB while in download mode MIGHT allow you to copy your stuff to the computer. I can't remember if this can be done from download mode though, and if the data partition is also hosed you'd be out of luck there anyway.
If i think of anything else you can try, I'll certainly let you know. Audit13 might have a few ideas you can try too. As I said though, you should also start looking into other options. Let us know what you want to do and we'll continue to help as best as we can!
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
The only times I've encountered this type of behavior it turned out to be a hardware failure (memory). If that is indeed the case here, I'm afraid there won't be much you can do for it. Don't get me wrong, I'm not saying you should just give up, but you should probably at least start looking at other options.
The main reasons I believe this to be the case are
1. It just died while nothing was being done (not being used)
2. Pit errors indicate either the partition table has been corrupted, or the partitions themselves have. Because it cannot detect any system (SYSTEM STATUS: NONE), it's more likely to be the partitions them selves, not the partition information table (pit).
Something else that doesn't look good, (but that I've never seen before) is the S?AEV. It should be SWREV. (Software Revision). It may mean nothing, but I've never seen it before so I thought I'd point it out.
As I said, I'm not saying you should give up yet. I've been wrong before and I'd hope to be again in this case. But I wouldn't put too much more time and effort into it as I've never seen one of these types of failures restored. They are pretty rare, but they do happen.
My best suggestion at this point is to start looking into replacing either the motherboard or the device. Motherboards can be found for reasonable prices, but you do have to be careful when buying one. (Let us know if you want to do this and we'll give you some tips on what to look for).
I'm sorry that this happened and that there doesn't seem to be much I can do to help. If you had any important data (pics or whatever), there's a small chance it can still be recovered. Don't get your hopes up too much for it, but using ADB while in download mode MIGHT allow you to copy your stuff to the computer. I can't remember if this can be done from download mode though, and if the data partition is also hosed you'd be out of luck there anyway.
If i think of anything else you can try, I'll certainly let you know. Audit13 might have a few ideas you can try too. As I said though, you should also start looking into other options. Let us know what you want to do and we'll continue to help as best as we can!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Wow, thanks Doc for replying. I was hopeful for a better result. BTW it does say SWREV I just couldn't quite make out the W at the time so I put ? to indicate that. I do have a little experience working on these phones (replaced the entire LCD/screen and USB port on my Note2) The model of the phone is listed as SGH-T999 in ODIN mode and it is a T-mobile phone. How much is motherboard and what should I look for as far as part number?
Found this with a quick ebay search: http://m.ebay.com/itm/Samsung-Galax...Board-Motherboard-s3-/221940485670?nav=SEARCH
I searched for "galaxy s3 T999 motherboard". That one is 68.50 obo.
It's been a while since I've looked, and it looks like there's a lot fewer of them available now. (Used to get tons of results).
You can also look for an I747 (AT&T) board. The I747 and T999 are fully compatible. No other models will fit into the case. (The T999V and I747M would probably also work. I'm not sure about the T999L or T999N models though. I'm guessing they would, but really have no idea for sure.)
Some terms to search for would be: Galaxy S3 T999 motherboard, I747 motherboard, mainboard, etc.
Also search for the same models with broken screens. Many times people sell these cheap and everything inside works perfectly. Might be cheaper too.
Watch out for certain words and phrases in the listing though. Some sellers will try a little wordplay to make it sound better than it is. If i find an example, I'll post it. Stuff like cracked screen won't power on can be changed to sound like it's only the screen won't come on, when it's really the whole device. Either ask for clarification, or move on.
I like the ones that are very specific, like cracked screen, but does appear to boot up and gives boot sounds.
Ask the seller for the imei number and check it yourself on swappa. I'd also call t-mobile and verify with them.
I hope that helps. Feel free to ask if you're wondering about a specific listing or anything else.
Oh and if buying from an eBay store, make sure they've got very good ratings. Individual people often won't have many ratings, but can sometimes be more trustworthy and more willing to give specifics. Sometimes....
You can also check places like Swappa and Craigslist.
Sent from my SGH-T999 using Tapatalk
The simplest way to get a replacement motherboard would be to look in the used market for a t999 that has smashed or defective screen with working internals.
If it is not too expensive, a jtag repair centre may be able to force flash a rom.
Hi, I'm new to the forum and was wondering if someone could help me just clarify a few things specific to my S9 that I am trying to remove frp from.After trying a lot of the youtube guides on bypassing the FRP using the "easy tools" and failing I thought of reflashing the OS. Since that doesn't exactly just work and you need a combination file, I was looking to figure out what combo file I need. The number from recovery menu is 10/QP1A.###/G960WVLS7ETH1 and the IC on the back of the phone is 649E-SMG960U.I found a tutorial saying you can make the combination file from the official firmware, but after getting that from SamMobile I could not find the sboot.bin.Iz4 in BL section. Then I tried looking online for a faster download of my firmware but none had the exact numbers right or the correct files in BL. (They had the right Ap files though). I also tried looking for a combo file directly but the same problem is I don't know the exact numbers/version that I need to make sure its correct for me to apply it into ODIN.I found a few links to combo files but they are all usually for android 8
Samsung SM-G960W Combination File ROM (Flash File)
Download Samsung SM-G960W Combination File (original flash file, rom) without any password for Free. We also provide the combination file for all Samsung devices.
samsungcombinationfile.com
Samsung Galaxy S9 SM-G960W Combination Firmware
Samsung Galaxy S9 SM-G960W Combination Firmware Samsung G960W Galaxy S9 Combination Firmware is a stable
www.full-repair-firmware.com
I just need to figure out what the software version (or baseband version?). Some threads say your phone model number must be the same and others say it only matters for the processor to be the same. Can I download the G960U files instead of a G960W or am I reading the wrong thing. Also can someone help with the bootloader version / build version. I think it is bootloader version 7 but its in place of the U that is written in most guides. and then the revision would be 1 right?Just would like some confirmation that I am looking for the right file. By what I have looked into so far the combo file with version G960U + android 8, bootloader version 7, and revision 1 will work regardless of the other numbers. or does it have to be G960W? F? X? any letter that has the same processor? Anything else I need to make sure of, is there an easier way to remove frp?Any help is appreciated, Thanks!
Update: Finally got into my frp locked S9. For anyone wondering I went with the combination file titled: COMBINATION_FAC_FA80_G960USQU7ASJ1_FACFAC_CL13230190_QB26521439_REV01_user_mid_noship_MULTI_CERT.tar that I got from the second link above.
I can conclude that the version of android does not make a difference since the combination file is simply like entering safe mode on your device. I'm not an expert but the SM-G960U file worked on SM-G960W phone and I made sure to get a file with same boot loader version and revision number, ignoring the letters that tell dates. From there I was able to OEM unlock and then reinstall the latest firmware I got from SamMobile.
Hi, I also needed to remove the google frp on my phone. I've tried so many different solutions online but nothing would work. ive tried every file in the link you've posted. a lot would Fail when it was loading it into my phone through Odin. always got Auth Fail or some other failure. some would cause infinite boot loop. some i couldnt use because it had password protection to unzip, i doubt it would have worked anyway lol.
My phones recover screen code or PDA? was G960WVLU9FUE2 I do not know what any of the letters or numbers mean after G960w, but i assume the 9 and the 2 are what are important and no files online match those numbers in the same file. I actually didnt find any combination files for U9 without needing to pay for it.
In the end i ended up just guessing the pattern password. I found a glitch that lets me keep guessing without a timer cool down. Now idk if this glitch is caused by my attempts of using these combination files then restoring it with the files from sammobile. but the glitch is easy to do.
First i did a factory reset. then when it boots up it asks to enter a network then to enter the pattern or sign into google. i dont know both so i started guessing the pattern. after a few tries it starts giving a timer cool down. I noticed you can bypass this timer by simply turning the screen off and on, then u can attempt again. when you fail the timer is still counting down from the previous attempt. like a 30 second cool down, but after screen turn off and a failed guess, the timer would be counting from like 22 seconds. then another attempt the timer would be at like 8 seconds until it resets back to 30 seconds when the timer runs out after another failed attempt.
I hope this info helps others get into their phones if Odin can't help you. Even if guessing passwords is a long tedious task.
Here's a tip for guessing node patterns. most people start from the top left corner and usually only use 5 maybe 6 nodes.