Related
Hello all,
I would like to share a method that solved this tricky issue with my S4 GT-I9500. While flashing with some new ROMs, I ended up with a generic IMEI on my S4. I read everything I could find here in XDA foruns, and no method worked for me. This one below, from fellow colleage douglasgalves at brasildroid foruns saved my phone. Here the link to the original post (portuguese only, sorry)
http://brasildroid.com.br/discussoe...efs-resolver-esse-problema-11.html#post299796
The method is quite simple, and althogh it does not make complete sense (why Trinida Tobago for example) it worked for me! Here it is.
1. You have a I9500 with a generic IMEI.
2. Install a official stock ROM with ODIN. Not any Stock ROM, but specifically Trinida & Tobago April 2013 ROM. You can browse it on Sammobile, or also get it from this link on XDA -> http://forum.xda-developers.com/showthread.php?t=2257645
The ROM I used is:
Build Date: 24.04.2013
Region: TTT (Trinidad and Tobago)
PDA: I9500UBUAMDK
Changelist: 534999 Android: 4.2
3. Once installation is finished, disconnect the cable;
4. Reboot to recovery and wipe data and cache;
5. Install KIES on your PC and let it update to its latest version.
6. Once KIES is updated, connect your S4 to the PC, no need for USB Debug, etc, just connect it.
7. KIES will detect it and say a new version of firmware is available. Perform the update. It takes a long time.
8. Once the update is finished, you get a dialog in KIES asking you to disconnect and connect the cable again, with a confirm button "Confirm". This is the moment it fixes your IMEI. One more reboot and voilà, your IMEI should be back.
I have no idea how/why this worked, if someone more experienced can explain, I would like to understand.
Also, no idea if this would work on other models, with a different ROM, or on a Mac instead of a PC, or with steps on different order. All I know is that, by doing exactly this, I gave life back to my beloved S4.
Now, off to make some 5 backups of the /efs folder before flashing ROMs again.
Good luck there with your generic-IMEIed S4s!
Did some more tweaking to try to understand what happened. Hope some guru can jump in and help me.
1. After I recovered my IMEI, I installed Philz Touch 5.11.2. It went well, I rebooted in CWM recovery, then chose Reboot->Root. It rebooted the phone. Then I went to make a backup of the /efs folder with Root Explorer, and discovered that despite it looking as rooting went well, the phone was not rooted.
Question 1: Why does Philz did not get to root the device? At that stage the firmware version was MG9 for region TTT (Trinidad & Tobago). Is that firmware somehow imcompatible for Philz to root?
Then ...
2. I flashed Firmware for Colombia with ODIN (my phone was bought in Colombia) from April, version UBUAMDE. Got Generic IMEI again. Then followed the same procedure from post 1, and got my IMEI back with KIES. The strange thing is that on KIES, my phone still shows as TTT (Trinidad) after that.
Question 2: It looks like more than the ROMs, it is the last step on KIES that recovers the IMEI. Is it so tha ODIN may be screwing up the IMEI?
Question 3: why I keep with my phone showing as TTT? Is that a problem?
3. Then I flashed the ChainFire recovery. Strangely, this went well and rooted my phone, so it may be something with Philz. I again flashed Philz and it installed well.
Question 4: may I get any problems by using Philz but having rooted with Chainfire?
Thanks a lot for any clarification you gurus out there can give me!
Thanks
You've given a considerable amount of hope to those that are stuck on the genereic imei. Thank you for providing this solution.
However, I am stuck:
After using ODIN 3.07; clicking nothing other than PDA for selecting the firmware you said to download: Hotfile:GT-I9500-TTT-I9500UBUAMDK-1366814146.zip The firmware was successfully installed.
Then before the boot completed, I went into recovery and wiped data and cache. The phone restarted and it booted up, Kies was already updated to the latest version. So once the phone booted up, I connected the phone to the computer and kies displayed this message:
Your device's current firmware version is not supported to update firmware via Kies.
Current firmware version: PDA:MDK / PHONE:MDK / CSC:MDK (XXX)
How can I go about resolving this issue?
As I said in the second post, I also got successful using the ROM for Colombia from April.
I would sugesst you to go to sammobile's firmware database. Download any older ROM which supports firmware via KIES (there is an icon showing that over there) and do the same procedure. It looks like what really solves it is the final step in KIES.
Sent from my GT-I9500 using XDA Premium 4 mobile app
I think this is due to flashing Previous Version of Modem (Its Including in Stock Firmware). When You flash Previous Version of Modem, Somehow IMEI retains. Here are some facts:
1) When we try to Flash any MOD of any dev then its depend on which Modem (i.e country's Firmware) the dev is using.
2) After flashing the MOD, Our IMEI becomes Fake.
3) Flashing Previous Version of Modem take back the IMEI.
In your above method you did the same. You flashed the Whole stock firmware but too old by date. After flashing, it retains.
BTW, have you checked your IMEI after flashing the Firmware using ODIN.? It was there.? was it Generic.?
Notice that I never refer to mod ROMs. I got a fake IMEI by flashing stock ROMs with ODIN.
Even during the recovery process, when I flashed the old stock ROM, the IMEI is not back. It only gets back at the last step with KIES.
When checking the IMEI after flashing with ODIN I get always the generic 499 IMEI.
Looks to me like something not going well with ODIN and 9500.
Sent from my GT-I9500 using XDA Premium 4 mobile app
partimers said:
Notice that I never refer to mod ROMs. I got a fake IMEI by flashing stock ROMs with ODIN.
Even during the recovery process, when I flashed the old stock ROM, the IMEI is not back. It only gets back at the last step with KIES.
When checking the IMEI after flashing with ODIN I get always the generic 499 IMEI.
Looks to me like something not going well with ODIN and 9500.
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flashing ROM from ODIN given you Fake IMEI.? This is something strange. We all flashed from ODIN & never got that. BTW, If its like that, I would recommend above ^ ^ your steps but wait...... Did you flashed any other country's firmware.?
Disturbed™ said:
Flashing ROM from ODIN given you Fake IMEI.? This is something strange. We all flashed from ODIN & never got that. BTW, If its like that, I would recommend above ^ ^ your steps but wait...... Did you flashed any other country's firmware.?
Click to expand...
Click to collapse
It is indeed strange Disturbed, but I can reproduce it. I flash for example, April ROMs (happened with all countries that I tested, Trinidad, Colombia and Brazil), the IMEI gets generic. It is not that the /efs folder is deleted. It is there, it is just that somehow, the IMEI does not get correctly read from the files that are there.
It only gets fixed after KIES updates the ROM for the latest one, and only at the very last stage where KIES ask to disconnect/reconnect the cable.
I first get into trouble when after flashing CWM Philz, I tried to restore stock ROM.
I live in Brazil, but travel very often on business to Colombia, and bought the phone on a good sale. That is why I am trying different countries, but the problem first happened when re-installing Stock ROM for the first time, and at that time I was just using the ROM for Colombia.
Only when things got bad (generic IMEI) I tried other countries ROMs, modems, etc, and finally got to this method that fixed it for me.
[/QUOTE]
Hi have you taken a backup of the EFS and saved?
U are a lucky guy u hv it all this working
As per what i know possibly there will be 1 more folder in the system root other then efs main which has imei details etc which must be corrupted and takes place while flashing so u have fake imei
Also check do u have any lockscreen issue???
I m telling this coz I was mad solving imei issue for 2 days with note 2 just a week ago
Sent from my GT-I9505 using XDA Premium 4 mobile app
exclaimed said:
I connected the phone to the computer and kies displayed this message:
Your device's current firmware version is not supported to update firmware via Kies.
Current firmware version: PDA:MDK / PHONE:MDK / CSC:MDK (XXX)
How can I go about resolving this issue?
Click to expand...
Click to collapse
*FIX*
I had the same problem, so I did the following to fix the problem:
Root the device,
Install CSC Changer,
Select the CSC which matches the firmware you are trying to update,
Then start the guide above again from the beginning (including reinstalling the firmware through Odin, even if you are currently using it - to remove the root...)
and now Kies is updating my device!
*UPDATE*
IMEI is not fixed...
Thank you for your suggestion.
I've tired CSC Changer, but to no avail. After changing my CSC to TTT, the phone is restarted, and I put it in download mode; follow all the steps above, but I still see XXX on KIES.
I even tried changing my CSC by opening Preconfig via android terminal emulator, but I still see XXX on KIES.
exclaimed said:
Thank you for your suggestion.
I've tired CSC Changer, but to no avail. After changing my CSC to TTT, the phone is restarted, and I put it in download mode; follow all the steps above, but I still see XXX on KIES.
I even tried changing my CSC by opening Preconfig via android terminal emulator, but I still see XXX on KIES.
Click to expand...
Click to collapse
Please note that KIES does not require Download mode, just connect the phone to the PC running KIES. Maybe it is that, I don`t know.
Hi have you taken a backup of the EFS and saved?
U are a lucky guy u hv it all this working
As per what i know possibly there will be 1 more folder in the system root other then efs main which has imei details etc which must be corrupted and takes place while flashing so u have fake imei
Also check do u have any lockscreen issue???
I m telling this coz I was mad solving imei issue for 2 days with note 2 just a week ago
Sent from my GT-I9505 using XDA Premium 4 mobile app[/QUOTE]
Hey 123hiten, I had no lockscreen issues, only Generic IMEI. Solve it with KIES.
So now I have tried this solution in many different ways,
even though kies does update the FW, it doesn't restore the IMEI,
So on several occasions after updating and not see'ing the IMEI being restored
I put the old Columbian FW back on and restarted the process following every last detail exactly as stated but to no avail....
So I can only conclude that this solution must not work for the I9500 (Exynos S4)....
SmilerOnline said:
So now I have tried this solution in many different ways,
even though kies does update the FW, it doesn't restore the IMEI,
So on several occasions after updating and not see'ing the IMEI being restored
I put the old Columbian FW back on and restarted the process following every last detail exactly as stated but to no avail....
So I can only conclude that this solution must not work for the I9500 (Exynos S4)....
Click to expand...
Click to collapse
It is really frustrating when a solution works in some cases and not on others. Sorry to hear it did not fix it for you. But for my I-9500 it fixed it perfectly. I do not know why :/
One thing I may remark: the IMEI only came back on the very last stage, when after finishing the upgrade to latest firmware in KIES, I rebooted the phone, disconnect the cable, connected it again and pressed "Confirm" on KIES. At that exact point it fixed it. I did not have to do anything with CSC.
partimers said:
It is really frustrating when a solution works in some cases and not on others. Sorry to hear it did not fix it for you. But for my I-9500 it fixed it perfectly. I do not know why :/
One thing I may remark: the IMEI only came back on the very last stage, when after finishing the upgrade to latest firmware in KIES, I rebooted the phone, disconnect the cable, connected it again and pressed "Confirm" on KIES. At that exact point it fixed it. I did not have to do anything with CSC.
Click to expand...
Click to collapse
I did exactly as you said but the Kies button said "OK" not "Confirm"...
and the only reason the CSC change was required for me was to allow my device to be updated by kies (if your device was from Columbia & you updated it with that fw that may be why you didn't need to change the csc... as the csc was already the Columbia csc)
Device is from Colombia but somehow it let me update via KIES using the TTT rom
Sent from my GT-I9500 using XDA Premium 4 mobile app
partimers said:
Device is from Colombia but somehow it let me update via KIES using the TTT rom
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
@partimer, I am curious, what app or program did you use to backup your IMEI after restoring it to its original form or did you just copy the efs folder.
Thanks.
Copy the efs folder using root Explorer to the Sd card. From there I created a tarball and backed it up to my file server and cloud.
Sent from my GT-I9500 using XDA Premium 4 mobile app
From my time on the S2 I had efs problems too. It was established that the IMEI number is individual to each device and is not included on any firmware be it stock or custom. Several roms now automatically create backups when being flashed so it's worth exploring your system to find any backups.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Hi! I am having major issues with my s4 i337 after switching from att to tmobile. The phone was unlocked so I took it upon myself to unlock it. It is unlocked but sometimes or rather most of the time does not pick up the network. When it does have data connection, it is Edge. I flashed the NC1 to root my phone, then reflashed to NJ4 (to unlock) but now nothing works. No wifi, camera fails, no multitasker, no voice assistant. Please help!!!!! I don't know what to do. I should have never unrooted it to unlock. I should have paid the $35 to get an unlock code. Can I fix this?
I have tried multiple APN settings,
Tried reflashing what I found online as att official firmware but it fails on ODIN.
So reflashed to NJ4, it is a bit laggy as well. Tried wifi which is greyed out, Camera still shows failed, pressing the home button to open multitasker and voice assistant brings up a blank grey screen. Phone is no longer connected as a mass storage device, only charges and can connect to ODIN.
I have attempted to factory reset which doesn't go through, unroot through SU which gets stuck on uninstalling and even trying to do an emergency recovery on Kies where it fails and gets stuck on kies failure mode.
I am on 4.4.4
I'm not sure what you mean by re flash to nj4, but have you flashed the nb1 tar? http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I'm not sure what you mean by re flash to nj4, but have you flashed the nb1 tar? http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
No I have not tried that one! Should I try it and which version should I use since I am rooted?
jd1639 said:
I'm not sure what you mean by re flash to nj4, but have you flashed the nb1 tar? http://forum.xda-developers.com/showthread.php?p=50912149
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I guess I was following outdated information for rooting. =[ Which was dated 2013.... Should have sensed something was wrong.
I flashed this and it worked perfectly as you suggested! THANK YOU SO MUCH. No more sleepless nights combing through forums, thanks to you! Everything works and is back to normal, I was about to just throw away this phone thinking I permanently broke it. AGAIN MANY THANKS! I'm scared to root it now.
Although I have one more question, if you could please answer.
After booting and everything working, in the notification, it says unauthorized access and to restart to reset changes made, if I dismiss it, will this fix be permanent and not revert to the unworkable state it was in? When I reboot manually?
vannicuhh said:
No I have not tried that one! Should I try it and which version should I use since I am rooted?
Click to expand...
Click to collapse
It doesn't really matter since you can root the device in either case. The rootable nb1 can be directly rooted. The other one, you'll have to update to nc1 to root. Flashing with odin, you will lose and will have to re-root. Also, see "Index All things AT&T...." by Gutt13 in the General Forum
vannicuhh said:
Hi! I am having major issues with my s4 i337 after switching from att to tmobile. The phone was unlocked so I took it upon myself to unlock it. It is unlocked but sometimes or rather most of the time does not pick up the network. When it does have data connection, it is Edge. I flashed the NC1 to root my phone, then reflashed to NJ4 (to unlock) but now nothing works. No wifi, camera fails, no multitasker, no voice assistant. Please help!!!!! I don't know what to do. I should have never unrooted it to unlock. I should have paid the $35 to get an unlock code. Can I fix this?
I have tried multiple APN settings,
Tried reflashing what I found online as att official firmware but it fails on ODIN.
So reflashed to NJ4, it is a bit laggy as well. Tried wifi which is greyed out, Camera still shows failed, pressing the home button to open multitasker and voice assistant brings up a blank grey screen. Phone is no longer connected as a mass storage device, only charges and can connect to ODIN.
I have attempted to factory reset which doesn't go through, unroot through SU which gets stuck on uninstalling and even trying to do an emergency recovery on Kies where it fails and gets stuck on kies failure mode.
I am on 4.4.4
Click to expand...
Click to collapse
ODINing to NB1 should definitely help, but as far as mobile data if it still isn't working I thought i read somewhere that T-Mobile needs the AWS bands or something and you'll have to follow the process to enable those. There's a thread somewhere in the General section to do it on 4.4
So when this phone was on stock fng2 firmware long ago when it was current firmware. I sent it off to a guy who was offering very cheap unlock. used it fine since then. but wanted to put stock rom on it and make it completely Samsung official with no problems. so it is ready for selling. but when I get the latest firmware which is ok3 and flash with odin. after booting in those crashes start happening about 2 times per second. phone is useless. I made it to settings menu and looked at baseband and software version both show unknown so I flash stock ok3 modem still samething. then I try these full firmware images:I flash od2, same thing oh1, same thing, factory reset doesn't do a thing on the rom with issues. then I try fng2 it works perfect. then I use use od2 oh1 ok3 update.zip to get ti to latest version and it works perfect. modems upgrade and work fine. but when on latest version I reset phone from the settings menu to factory default same issue after phone as booted. so currently phone is useless if it is ever resetted. so no selling. any solutions.
the issue seems to reside with the modem. probably guy messed up a lot of settings in service mode?
You name it I have tried it most likely
any ideas anyone?
anyway to reset nvram to factory default.
i have reseted it in service mode. were it says a golden backup exists. that didnt solve anything
I've tried many many things but nothing seems to work for that issue. Only way I've gotten around it is by doing a dirty flash of kitkat with odin.
Well i rooted my note4 an everything went well but then out of the blue i cant play back any video when ever i try it instantly reboots does any one know what could be the problem......i unrooted phone an flashed back original firmware plus factory reset .....
Sm-n910 said:
Well i rooted my note4 an everything went well but then out of the blue i cant play back any video when ever i try it instantly reboots does any one know what could be the problem......i unrooted phone an flashed back original firmware plus factory reset .....
Click to expand...
Click to collapse
Did you reinstall the stock firmware via ODIN? Did you download the last firmware via SAMMOBILE?
Seems like you might have flashed the wrong firmware mate
Sent from my SM-N910T3 using Tapatalk
I know these are much tougher to find - can't be obtained from SamFirm or SamMobile. So I'll be uploading one for each bootloader version. Firmware is universal on U models so you can use the other 4 files from any other matching collection. Can probably even mix and match builds, if you can't find files for the exact same build. Can't mix and match bootloaders though, so the other 4 files have to at least be from the same bootloader.
USERDATAs for any other CSCs can be gotten from SamFirm - for the latest version. If you need an old USERDATA for a CSC that's not commonly found on SamMobile (ACG, LRA, TFN, etc), let me know and I can probably get it.
https://www.androidfilehost.com/?w=files&flid=283206
Can I use the userdata file for G55USQU5CRF5 with the other four files being from the build G55USQS5CRF5? I'm not sure what the difference between SQU and SQS is, and if it is significant. Thank you!
zeiguy17 said:
Can I use the userdata file for G55USQU5CRF5 with the other four files being from the build G55USQS5CRF5? I'm not sure what the difference between SQU and SQS is, and if it is significant. Thank you!
Click to expand...
Click to collapse
Yes, you can. There basically is no difference
I'm begging someone to help me. I flashed my AT&T S8+ to the G955U1 unlocked firmware, then got accepted into the beta and installed it via OTA update. I now want to go back to a AT&T rom so I can have stuff like Wi-fi calling and VOLTE back. I've tried so many different roms with ATT userdata and they all fail with ODIN. I'm guessing its something to do with bootloader version. Is there any way I can get back to a AT&T ROM from the G955U1 Pie beta firmware.
sean8102 said:
I'm begging someone to help me. I flashed my AT&T S8+ to the G955U1 unlocked firmware, then got accepted into the beta and installed it via OTA update. I now want to go back to a AT&T rom so I can have stuff like Wi-fi calling and VOLTE back. I've tried so many different roms with ATT userdata and they all fail with ODIN. I'm guessing its something to do with bootloader version. Is there any way I can get back to a AT&T ROM from the G955U1 Pie beta firmware.
Click to expand...
Click to collapse
Well the beta has to still be Bootloader 5, so just flash any 5 build
iBowToAndroid said:
Well the beta has to still be Bootloader 5, so just flash any 5 build
Click to expand...
Click to collapse
I finally managed to get Odin to flash a ROM. All of them I tried were bootloader 5. But now the problem is I cant get OTA updates. My phone is back to being a AT&T one with the AT&T boot screen and wi-fi calling etc etc. But everytime I check for updates it says its up to date even though I have CRL1 and the latest AT&T firmware is U5CSA4. I would update form SD card but that wipes the phone every time. I had to do that 4 or 5 times just to get to CRL1 because it kept saying my phone is up to date.
sean8102 said:
I finally managed to get Odin to flash a ROM. All of them I tried were bootloader 5. But now the problem is I cant get OTA updates. My phone is back to being a AT&T one with the AT&T boot screen and wi-fi calling etc etc. But everytime I check for updates it says its up to date even though I have CRL1 and the latest AT&T firmware is U5CSA4. I would update form SD card but that wipes the phone every time. I had to do that 4 or 5 times just to get to CRL1 because it kept saying my phone is up to date.
Click to expand...
Click to collapse
1. AT&T phones don't OTA if you're using a carrier other than AT&T - even their own MVNOs
2. If you are using AT&T, OTA rollouts are staged. It just came out less than a week ago, so your phone might not have been green-lit yet
3. Both 1 and 2 are really irrelevant anyways, because you can just Odin flash any update you want. Using HOME CSC will ensure data isn't wiped
iBowToAndroid said:
1. AT&T phones don't OTA if you're using a carrier other than AT&T - even their own MVNOs
2. If you are using AT&T, OTA rollouts are staged. It just came out less than a week ago, so your phone might not have been green-lit yet
3. Both 1 and 2 are really irrelevant anyways, because you can just Odin flash any update you want. Using HOME CSC will ensure data isn't wiped
Click to expand...
Click to collapse
I am using AT&T. I know rollouts are staged but I've never had it tell me my phone is up to date when it is 7 versions behind which it was because I had to start at CRF5 since that is the newest AT&T Userdata file I could find. I checked after doing the update from SD card method each time, making sure to put the date on my phone forward since AT&T only lets you manually check once a day. No matter what it said I was up to date despite being several versions behind.
I'm gonna try using Odin to flash one more time because not being able to do OTA update is a HUGE PIA. Dose it matter that the user data is called "ATT_G955USQU5CRF5" despite the firmware being USQS because I couldn't find a USQUCRF5 and besides AT&T's update history shows USQSCRF5 anyways. What I did was downloaded a verizon G955USQS5CRF5 ODIN file (because for some reason AT&T odin files are really hard to find) and replaced the Verizon user data with the AT&T one.
Also if I flash say CSA4 verizon with the verizon user data the put my AT&T sim card in it dose it not download all the the carrier bloatware and what not? dose that basically turn it back into a AT&T phone? or could I take that CSA4 and flash it with the CRF5 AT&T user data?
sean8102 said:
I am using AT&T. I know rollouts are staged but I've never had it tell me my phone is up to date when it is 7 versions behind which it was because I had to start at CRF5 since that is the newest AT&T Userdata file I could find. I checked after doing the update from SD card method each time, making sure to put the date on my phone forward since AT&T only lets you manually check once a day. No matter what it said I was up to date despite being several versions behind.
I'm gonna try using Odin to flash one more time because not being able to do OTA update is a HUGE PIA. Dose it matter that the user data is called "ATT_G955USQU5CRF5" despite the firmware being USQS because I couldn't find a USQSCRF5 and besides AT&T's update history shows USQSCRF5 anyways. What I did was downloaded a verizon G955USQS5CRF5 ODIN file and replaced the Verizon user data with the AT&T one.
Also if I flash say CSA4 verizon with the verizon user data the put my AT&T sim card in it dose it not download all the the carrier bloatware and what not? dose that basically turn it back into a AT&T phone? or could I take that CSA4 and flash it with the CRF5 AT&T user data?
Click to expand...
Click to collapse
1. I have no idea what the difference is between SQS and SQU. Even on the same network, it seems to be completely random as to which one gets assigned to each new update. I don't think it matters
2. Don't flash userdata if you're going to Odin flash a different carrier's version. Just do the normal 4 files
Sorry for the late reply. But just wanted to say that this method of getting from a G955U1 (US Unlocked) firmware back to AT&T branded firmware did end up working. I did eventually start getting OTA updates after using the method I mentioned (flashing Verizon USQS5CRF5 ROM files with AT&T G955USQS5CRF5 USERDATA file using ODIN Odin3 v3.13.1 3B Patched). Then updating to the then latest version using the update.zip method using files from the "Firmware Science" site (I think that's the name). Then about two days after AT&T released a new update I actually got it OTA. However after it installed successfully my chrome app became broken. Opening it and hitting the ... button in the top right would open the menu but all the options just said "chrome". Tried clearing the cache and files of Chrome but then it just crashed when launched. Had to do a reset (not a big deal since I had a Samsung SmartSwitch backup on my SD Card). Just hope that dose not happen every OTA, but guessing it was a weird fluke.
sean8102 said:
Sorry for the late reply. But just wanted to say that this method of getting from a G955U1 (US Unlocked) firmware back to AT&T branded firmware did end up working. I did eventually start getting OTA updates after using the method I mentioned (flashing Verizon USQS5CRF5 ROM files with AT&T G955USQS5CRF5 USERDATA file using ODIN Odin3 v3.13.1 3B Patched). Then updating to the then latest version using the update.zip method using files from the "Firmware Science" site (I think that's the name). Then about two days after AT&T released a new update I actually got it OTA. However after it installed successfully my chrome app became broken. Opening it and hitting the ... button in the top right would open the menu but all the options just said "chrome". Tried clearing the cache and files of Chrome but then it just crashed when launched. Had to do a reset (not a big deal since I had a Samsung SmartSwitch backup on my SD Card). Just hope that dose not happen every OTA, but guessing it was a weird fluke.
Click to expand...
Click to collapse
Hey I am in the same boat. Can you please help pointing to the files you used to ODIN to get back to ATT version.
SC1 USERDATA was added a few days ago, for anyone wanting to jump to Pie
USERDATA added for bootloader 6
USERDATA added for bootloader 7
Ive been researching and reading most of the day about returning to stock on an att 955u. The only download i can find that wont take 6 hours is from samfirm and is G955USQS7DSL2. Can i use this and the userdata from your link to return this back to stock?
jetracer said:
Ive been researching and reading most of the day about returning to stock on an att 955u. The only download i can find that wont take 6 hours is from samfirm and is G955USQS7DSL2. Can i use this and the userdata from your link to return this back to stock?
Click to expand...
Click to collapse
Since the USERDATA is TA5, I would recommend using a build that's closer to that one. You can get TA3 from SamFirm under regions/CSCs ACG, CCT, LRA, SPR, TFN, or VZW.
When you say "returning to stock", what firmware is currently on the device?
iBowToAndroid said:
Since the USERDATA is TA5, I would recommend using a build that's closer to that one. You can get TA3 from SamFirm under regions/CSCs ACG, CCT, LRA, SPR, TFN, or VZW.
When you say "returning to stock", what firmware is currently on the device?
Click to expand...
Click to collapse
I was on a verizon build. I ended up returning to stock with G955USQS6DSG4, got one update and now says no firmware. Currently shows G955USQU6DSH8.
SamMobile actually had pretty decent speed.
jetracer said:
I was on a verizon build. I ended up returning to stock with G955USQS6DSG4, got one update and now says no firmware. Currently shows G955USQU6DSH8.
SamMobile actually had pretty decent speed.
Click to expand...
Click to collapse
Do you have all of AT&T's apps and bloatware now? If so, it should be updating at least to SJ3, if not up to TA5. You would need an active AT&T SIM inserted in order to pull the update though
iBowToAndroid said:
Do you have all of AT&T's apps and bloatware now? If so, it should be updating at least to SJ3, if not up to TA5. You would need an active AT&T SIM inserted in order to pull the update though
Click to expand...
Click to collapse
Yea just uninstalled and disabled a bunch of att and samsung bloat. I am currently running an att sim. Should i possible download the v7 files and try again? Shouldn't matter that the firmware was from "tmobile" right its the userdata that counts iirc.
jetracer said:
Yea just uninstalled and disabled a bunch of att and samsung bloat. I am currently running an att sim. Should i possible download the v7 files and try again? Shouldn't matter that the firmware was from "tmobile" right its the userdata that counts iirc.
Click to expand...
Click to collapse
What do the 3 service provider codes show as, under Software Information?