So my dad bought a GS3 and it shows that it's a t999 model in the settings. It's on UVDMD5 has the UVDMD5 radio as well. I was going to odin flash to the new 4.3 root 66 but it threw out an error. I looked at the phone and in download mode it shows it's a i-747 so I'm super confused right now. I also have an s3 myself and when I remove the battery and check my phone it shows model: sgh-t999 and also shows t999 in download mode as well. On the new phone my dad purchased it shows model: GT-T999 where the battery goes. So yeah I'm pretty confused. I managed to flash the tmo twrp and flashed superuser zip and rooted it sucessfully but I wanted to update it to 4.3 but now I'm not even sure what firmware to flash
Looks like yet another frankenphone. Wish I knew where these things were coming from!
Its hard to tell you what to do, but if it currently had MD5 on there, you probably need to stick with T999 firmware. Well, maybe....
Install terminal emulator and enter this:
getprop ro.bootloader
This will tell you what the firmware is. You cant judge by the rom or baseband.
Anyway, almost every time ive seen these things, the recommendation is usually to see if you can return the device. Theres just too many questions and things that dont match up. If you plan on using it as is, and never care about updates and such, I guess it might be ok, but otherwise theres just too great a chance for future problems!
For starters, there's no such thing as a GT-T999. And If download mode says its an I747, id guess youre using the I747 base firmware/bootloader. However, your system and baseband are from the T999 firmware, so we can be pretty confident that flashing I747 firmware will not work. But you probably can only flash I747 firmware because thats what your bootloader appears to be! Very confusing, very messed up, I know! Its highly possible, judging by the GT-T999, that it might be a chinese knock-off.
It may or may not help, but install Phone Info - Samsung app. Then let me know what it tells you. I dont think theres going to be a lot we can do though, but ill be glad to take a look anyway.
DocHoliday77 said:
Looks like yet another frankenphone. Wish I knew where these things were coming from!
Its hard to tell you what to do, but if it currently had MD5 on there, you probably need to stick with T999 firmware. Well, maybe....
Install terminal emulator and enter this:
getprop ro.bootloader
This will tell you what the firmware is. You cant judge by the rom or baseband.
Anyway, almost every time ive seen these things, the recommendation is usually to see if you can return the device. Theres just too many questions and things that dont match up. If you plan on using it as is, and never care about updates and such, I guess it might be ok, but otherwise theres just too great a chance for future problems!
For starters, there's no such thing as a GT-T999. And If download mode says its an I747, id guess youre using the I747 base firmware/bootloader. However, your system and baseband are from the T999 firmware, so we can be pretty confident that flashing I747 firmware will not work. But you probably can only flash I747 firmware because thats what your bootloader appears to be! Very confusing, very messed up, I know! Its highly possible, judging by the GT-T999, that it might be a chinese knock-off.
It may or may not help, but install Phone Info - Samsung app. Then let me know what it tells you. I dont think theres going to be a lot we can do though, but ill be glad to take a look anyway.
Click to expand...
Click to collapse
Yes it was super confusing! It's so weird. I did the getprop ro.bootloader and I got I747UCALI5. I'm kinda scared to odin anything since I really have no idea what model I actually have so I just ended up flashing the latest PA rom & so far everything seems fine
Yup, its exactly as I expected! I747 bootloader/base firmware with T999 system and modem. These are not things that should work together and it also means there is no safe way to update your firmware. LI5 sounds like its really old btw. But tbh, I dont know if its even a real build number! I can say you will not be able to run TW kk roms and might not be able to run 4.3 ones as well. CM/aosp, im not sure about, but I know they were known to be really buggy on older firmware.
If it is an option, I strongly suggest seeing if you can get a refund. May I ask where it was bought from? I think whenever we run into these we need to start letting people know not to purchase from those sellers. For one, to protect folks from having this happen to them, but also to try and discourage this type of business practice (if you even want to call it that!). Its almost as bad as people who sell devices and then report them lost!
---------- Post added at 06:08 PM ---------- Previous post was at 06:06 PM ----------
Just checked and LI5 is a real build, but it is old. 4.1.1
DocHoliday77 said:
Yup, its exactly as I expected! I747 bootloader/base firmware with T999 system and modem. These are not things that should work together and it also means there is no safe way to update your firmware. LI5 sounds like its really old btw. But tbh, I dont know if its even a real build number! I can say you will not be able to run TW kk roms and might not be able to run 4.3 ones as well. CM/aosp, im not sure about, but I know they were known to be really buggy on older firmware.
If it is an option, I strongly suggest seeing if you can get a refund. May I ask where it was bought from? I think whenever we run into these we need to start letting people know not to purchase from those sellers. For one, to protect folks from having this happen to them, but also to try and discourage this type of business practice (if you even want to call it that!). Its almost as bad as people who sell devices and then report them lost!
---------- Post added at 06:08 PM ---------- Previous post was at 06:06 PM ----------
Just checked and LI5 is a real build, but it is old. 4.1.1
Click to expand...
Click to collapse
Just asked my dad & he said he bought it from a pawnshop which isn't surprising why there is so much confusion about the model lol. Would having an old bootloader cause problems? I was able to flash the latest PA beta but I haven't encountered any issues as of yet
I dont use non touchwiz roms, but I do remember they all started requiring certain bootloaders nrcsuse they were encountering too many bugs on older ones. I dont know any details though.
Id imagine youll encounter issues flashing any rom thst has the assert check. It checks to make sure you have a certain bootloader, and most here will be checking for T999 builds. Since yours has the I747 bootloader, it may cause trouble flashing certain roms.
That and you wont be able to easily or safely update the firmware...
Not sure theres much that could be done since it came from a pawn shop though.
DocHoliday77 said:
I dont use non touchwiz roms, but I do remember they all started requiring certain bootloaders nrcsuse they were encountering too many bugs on older ones. I dont know any details though.
Id imagine youll encounter issues flashing any rom thst has the assert check. It checks to make sure you have a certain bootloader, and most here will be checking for T999 builds. Since yours has the I747 bootloader, it may cause trouble flashing certain roms.
That and you wont be able to easily or safely update the firmware...
Not sure theres much that could be done since it came from a pawn shop though.
Click to expand...
Click to collapse
Yeah this whole situation has been odd. I'll advise my dad to avoid pawnshops from now on lol. Whenever I was in download mode I noticed the flashcount had shown 3 and I ended up using triangle away to reset it when I was still on 4.1.2 for the moment. Before I rooted it or anything it already had supersu installed but I don't think the phone was actually rooted cause everytime I would open supersu it would tell me to update the binary and it would fail each time and any other root apps I installed were denied root. The phone still had stock recovery as well. I honestly thought it was a t-999 up until I was going to flash the nc2 update and it failed and that's when I realized hey this isn't really a t999. I ended up flashing twrp instead and flashed the supersu zip to get root. I flashed paranoid android afterwards and when I went to about phone i noticed everything changed from t-999 to I747 including the modem. It was weird. I ended up reflashing att twrp just to be safe, I flashed the latest modem from at&t, and I crossed my fingers & bravely flashed a zip that updated my bootloader to the latest one for the I747 and it actually worked which was a huge sigh of relief. I reflashed paranoid android afterwards and so far no issues. Now that I updated everything I might end up just flashing a touchwiz rom from the at&t forums. Thanks for your help though, I greatly appreciate it! :good:
Related
So basically I want to rom my phone with the AOPK Jellybean rom. But i'm worried if I lose my IMEI number. There anything I can do to make sure I wont lose my IMEI number?
rayoubi said:
So basically I want to rom my phone with the AOPK Jellybean rom. But i'm worried if I lose my IMEI number. There anything I can do to make sure I wont lose my IMEI number?
Click to expand...
Click to collapse
Buy a scratch & win lotto ticket. If you lose, go ahead and flash.
As of right now some simple steps would be being in the OTA update UCLG1 having a SV05 and having TWRP (team win recovery project) instead of CWM. The number of users experiencing this issue is very low. If your in the 30 day return period I advise doing some testing because its less of a hassle going to a store for an exchange instead of sending it away.
zmore said:
Buy a scratch & win lotto ticket. If you lose, go ahead and flash.
Click to expand...
Click to collapse
What are you trying to say? lol
DudeWatsThat said:
As of right now some simple steps would be being in the OTA update UCLG1 having a SV05 and having TWRP (team win recovery project) instead of CWM. The number of users experiencing this issue is very low. If your in the 30 day return period I advise doing some testing because its less of a hassle going to a store for an exchange instead of sending it away.
Click to expand...
Click to collapse
So I should use team win recovery project instead of CWR, because it would lower my chances? I don't wanna take any chances I guess i'll be stock until we find a real solution. I don't feel like bricking my $600+ device.
Yes twrp and no flash root gtg
Sent from my SAMSUNG-SGH-I747 using xda premium
rayoubi said:
What are you trying to say? lol
So I should use team win recovery project instead of CWR, because it would lower my chances? I don't wanna take any chances I guess i'll be stock until we find a real solution. I don't feel like bricking my $600+ device.
Click to expand...
Click to collapse
Its a issue affecting a small amount of people there's a very high chance that you might not get it. I was scared to but I said screw it I'm going to find out if my phone has it, if it does ill just exchange it better now than later on when my return period is up.
No one with baseband version of UCLG1 has lost it neither with TWRP and UCLG1.
If you wanna try it download the OTA from your phone(using software update on device itself). Root using no trip method and instead pushing CWM use TWRP. Flash and see what happens.
tyshemi said:
Yes twrp and no flash root gtg
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
no flash root?
DudeWatsThat said:
Its a issue affecting a small amount of people there's a very high chance that you might not get it. I was scared to but I said screw it I'm going to find out if my phone has it, if it does ill just exchange it better now than later on when my return period is up.
No one with baseband version of UCLG1 has lost it neither with TWRP and UCLG1.
If you wanna try it download the OTA from your phone(using software update on device itself). Root using no trip method and instead pushing CWM use TWRP. Flash and see what happens.
Click to expand...
Click to collapse
I actually did root my phone with the toolkit the day I got my phone. I got a OTA update yesterday but I choosed to ignore it because I was afraid to lose my root. I do have CWR already installed but I guess I might as well use TWRP.
No trip root lol and yes twrp I have been through all roms and stock and just fine
Sent from my SAMSUNG-SGH-I747 using xda premium
tyshemi said:
No trip root lol and yes twrp I have been through all roms and stock and just fine
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
i'm sorry what does no trip root mean from just normal root. im a noob i know.
http://forum.xda-developers.com/showthread.php?t=1739426
Best root method
Sent from my SAMSUNG-SGH-I747 using xda premium
And here is twrp method use goo app it's way easier imo
http://forum.xda-developers.com/showthread.php?t=1793224
Sent from my SAMSUNG-SGH-I747 using xda premium
rayoubi said:
no flash root?
I actually did root my phone with the toolkit the day I got my phone. I got a OTA update yesterday but I choosed to ignore it because I was afraid to lose my root. I do have CWR already installed but I guess I might as well use TWRP.
Click to expand...
Click to collapse
Use OTA root keeper it should keep it.
---------- Post added at 05:57 PM ---------- Previous post was at 05:55 PM ----------
tyshemi said:
And here is twrp method use goo app it's way easier imo
http://forum.xda-developers.com/showthread.php?t=1793224
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
+1 Definitely the easiest way.
I was scared too man. I really was. This thing cost me an arm and a leg, its like the nicest thing I own and I never want to put it in dangers way. Plus if I had to pay out of pocket, I wouldn't be able to replace it for 2 months, and it would eat up all my pleasure money.
But you know what, I hate touchwiz. I hate the menus, I hate its goofy sounds and stuff. The stock keyboard is ridiculous.The battery life was really good though. I know I could of changed the launcher and some other stuff but I am really into running my devices lean and mean. This is just a thing, a mentality I guess.
I decided that at best I can provide some information to the community and possibly work with other people and get this figured out. Everyone being scared is going to ruin the test pool because we don't get the scope of info we need to really get analytical about it. At worst, well I have documented everything I've done so far and can reproduce any partition pre-flashing needed. If we all end up with phones with imeis missing in the first 30 days, and all take them back to att because "I don't know I just don't get 4g anymore", we can possibly force att and Samsung to look more in-depth And possibly give a fix.
If anything early is the time to flash if you are looking to get your hands dirty, and be fine with learning some things along the way. I spent a good 2 weeks just learning everything I could about the issue, my phone, just got real intimate with the thing XD. Once I felt comfortable that I have done everything in my power to prepare for the worse, I rooted with the "no trip" method and then installed busy box, and then goomanager from the play store. From there just go to options and then hit open recovery and it automatically detects your device and installs.
Just remember, this is a brand new device running brand new software. All of this is experimental and the fact any of it works, let alone as well as it does is amazing. I'm running aokp rc2 right now and its pretty impressive. There's some weird haptic bugs and I'm noticing that my signal strength is not even close to what it was stock. This is disappointing and o don't understand why this is. As far as I understand I'm still on the same modem? All I've done is flashed aokp and cm10 ROMs. I'm getting about 107db right now and it keeps switching from HSDPA to HSDPA +. So when I load a page, it will be slow till the HSDPA + kicks in, then it will go back down to HSDPA and loose signal strength, almost like it "cranks up" when data is being used? Anyways yea its fun and I totally understand why you want to, but bit expect it to be like 1000x better right now. But if you are down contribute either info, donate to devs, try things, send files/screenshots then come join the fun!
Sent from my SGH-I747 using Tapatalk 2
rakhov said:
I was scared too man. I really was. This thing cost me an arm and a leg, its like the nicest thing I own and I never want to put it in dangers way. Plus if I had to pay out of pocket, I wouldn't be able to replace it for 2 months, and it would eat up all my pleasure money.
But you know what, I hate touchwiz. I hate the menus, I hate its goofy sounds and stuff. The stock keyboard is ridiculous.The battery life was really good though. I know I could of changed the launcher and some other stuff but I am really into running my devices lean and mean. This is just a thing, a mentality I guess.
I decided that at best I can provide some information to the community and possibly work with other people and get this figured out. Everyone being scared is going to ruin the test pool because we don't get the scope of info we need to really get analytical about it. At worst, well I have documented everything I've done so far and can reproduce any partition pre-flashing needed. If we all end up with phones with imeis missing in the first 30 days, and all take them back to att because "I don't know I just don't get 4g anymore", we can possibly force att and Samsung to look more in-depth And possibly give a fix.
If anything early is the time to flash if you are looking to get your hands dirty, and be fine with learning some things along the way. I spent a good 2 weeks just learning everything I could about the issue, my phone, just got real intimate with the thing XD. Once I felt comfortable that I have done everything in my power to prepare for the worse, I rooted with the "no trip" method and then installed busy box, and then goomanager from the play store. From there just go to options and then hit open recovery and it automatically detects your device and installs.
Just remember, this is a brand new device running brand new software. All of this is experimental and the fact any of it works, let alone as well as it does is amazing. I'm running aokp rc2 right now and its pretty impressive. There's some weird haptic bugs and I'm noticing that my signal strength is not even close to what it was stock. This is disappointing and o don't understand why this is. As far as I understand I'm still on the same modem? All I've done is flashed aokp and cm10 ROMs. I'm getting about 107db right now and it keeps switching from HSDPA to HSDPA +. So when I load a page, it will be slow till the HSDPA + kicks in, then it will go back down to HSDPA and loose signal strength, almost like it "cranks up" when data is being used? Anyways yea its fun and I totally understand why you want to, but bit expect it to be like 1000x better right now. But if you are down contribute either info, donate to devs, try things, send files/screenshots then come join the fun!
Sent from my SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
I'm holding out on AOKP until it comes out of preview builds, don't like being a guinea pig.
My experience:
Used the root without tripping flashcounter method.
Used adb to install CWM (the touch version for AT&T, not the teamepic one)
Have flashed custom ROMs, Kernels, and mods.
Absolutely no problems.
Just make sure to download the .zip files that are specific to your device, make nandroids, and have fun!
kswa1987 said:
My experience:
Used the root without tripping flashcounter method.
Used adb to install CWM (the touch version for AT&T, not the teamepic one)
Have flashed custom ROMs, Kernels, and mods.
Absolutely no problems.
Just make sure to download the .zip files that are specific to your device, make nandroids, and have fun!
Click to expand...
Click to collapse
And avoid anything marked 'preview' or 'nightly'. (IMHO)
rayoubi said:
So basically I want to rom my phone with the AOPK Jellybean rom. But i'm worried if I lose my IMEI number. There anything I can do to make sure I wont lose my IMEI number?
Click to expand...
Click to collapse
I followed this method-- http://www.androidauthority.com/galaxy-s3-sgh-i747-att-root-99789/
Using Odin to install ClockWorkMod and then flashed the updated version of ClockWorkMod via Rom Manager & installed CM10... No issues. I've use this method 4 times now on two different S3's with no issues & IMEI still intact.
DudeWatsThat said:
Its a issue affecting a small amount of people there's a very high chance that you might not get it. I was scared to but I said screw it I'm going to find out if my phone has it, if it does ill just exchange it better now than later on when my return period is up.
No one with baseband version of UCLG1 has lost it neither with TWRP and UCLG1.
If you wanna try it download the OTA from your phone(using software update on device itself). Root using no trip method and instead pushing CWM use TWRP. Flash and see what happens.
Click to expand...
Click to collapse
I'm a Telus user up here in the great white north (canada) and my baseband is LE8 and the kernel date back to may20th.. I made a topic earlier in the international thread about a hiss/static noise problem and a helper told me to flash a new rom as my current baseband is old and he had problems with this baseband/firmware.
I'm so confused, ROMS are just different type of "OS" right? I mean if I want to officially update my firmware I gotta go through the Samsung procedure? (If I update while rooted, I'll lose root right?).
Intercrew said:
I'm a Telus user up here in the great white north (canada) and my baseband is LE8 and the kernel date back to may20th.. I made a topic earlier in the international thread about a hiss/static noise problem and a helper told me to flash a new rom as my current baseband is old and he had problems with this baseband/firmware.
I'm so confused, ROMS are just different type of "OS" right? I mean if I want to officially update my firmware I gotta go through the Samsung procedure? (If I update while rooted, I'll lose root right?).
Click to expand...
Click to collapse
I rooted LE8 with the snap dragon method then flashed cm9.. then flashed cm10 then nandroided back to cm9 then flashed LG1 from androiduser.. and my imei is still intact.. I think losing the imei is totally random in my opinion
Sent from my SAMSUNG-SGH-I747 using xda premium
Intercrew said:
I'm a Telus user up here in the great white north (canada) and my baseband is LE8 and the kernel date back to may20th.. I made a topic earlier in the international thread about a hiss/static noise problem and a helper told me to flash a new rom as my current baseband is old and he had problems with this baseband/firmware.
I'm so confused, ROMS are just different type of "OS" right? I mean if I want to officially update my firmware I gotta go through the Samsung procedure? (If I update while rooted, I'll lose root right?).
Click to expand...
Click to collapse
Roms can update your firmware it all depends on what stock version their based on.
Most of the time you will find a root injected rom lets say its le9 with this you would just have to flash it through cwm/twrp. Instant firmware update without loosing root.
Then flash any rom based on it.
Plus theres a niffty app called OTA root keeper. Get OTA without loosing root.
Anyone feel free to correct me if I'm wrong on something.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
1. Since the Galaxy S III became available as a Boost variant, there’s been an increasing amount of questions, issues, and requests for builds. I have collaborated with the powers that be, and it was determined that it might be a good idea to start a Boost only thread. This thread is dedicated to anything and everything Boost Galaxy S III related.
2. I will update and bump and sticky and edit and whatever else needs to be done the best that I can, but it is open and available to all. This is YOUR thread, just as much as it is mine. I encourage folks to ask questions, post relevant links, tutorials, helpful hints, and anything else they come across while tinkering with their new phone that may help others related to the Boost S3.
3. First and foremost, as always is the disclaimer. We are all responsible for our own actions. I am not responsible for what you do to your phone, so please do not flame me or anyone else in this thread if you do something that potentially fries your device.
4. If you post a link to something flashable, either through Odin, CWM, Heimdall, TWRP, etc, please test it on your own phone first or have someone test it before you do so. If it works, and will benefit someone, feel free to include it. I will most likely PM the dev and ask to put it in the OP.
5. And finally, please be courteous and respectful. We are all here to learn from one another, and do not need sarcasm, unkindness, flaming, or disrespect, of any kind. Thank you and enjoy.
Stock Unrooted OTA Odin Tar
This is the official, stock, right out of the box, Boost MD7. This will unroot your device, and take everything back to the way it was when you got it. Please thank the OP, Smith058, over at AF (link to OP at the bottom), since he was so gracious to let me post it here, and to let me use it to cook up something good for you folks More to come on that one! The only issue I’ve noticed on this build is there’s no boot up sound. But it flashed modem, stock recovery, put the device status back to “normal” and made the “custom” in Odin mode back to “official.” This should come in handy if you need to send it back for repair, or just want to start anew. The coming zip (once it’s uploaded) has working sound.
Stock MD7 Odin Tar Link https://mega.co.nz/#!ARkXGZCS!RITkIjvPnT51c6nyDdFvE2Z4oBNQt0PTcKnCGWuavdo
Link to Smith058’s OP(be sure to give him a shout out!)
http://androidforums.com/boost-mobile-galaxy-s3-all-things-root/753772-odin-backup-sph-l710_md7-stock.html
Stock OTA MG2 Tar:
http://www.androidfilehost.com/?fid=23212708291678209
Flashing Instructions:
1. Download and Install Odin to your PC
2. Download the ROM to your computer, and remember where you put it
3. Boot your phone into download(Odin) mode by pressing volume down, home button, and power button simultaneously
4. Once in Odin mode, connect your phone to your PC
5. Once the “COM” block turns blue, click the PDA button, and navigate to the ROM tar.
6. As a habit, I uncheck the F. Reset Time and Auto Reboot boxes as well
7. Click Start. When it’s done, pull the battery.
8. Reinsert battery, boot up, and profit
Links to Boost ROMs
Stock Rooted MD7 Flashable Zip -http://forum.xda-developers.com/showthread.php?t=2478888
Stock Unrooted MD7 Flashable Zip - http://forum.xda-developers.com/showthread.php?p=46367914#post46367914
Stock Rooted, Deodexed MG2 Zip - http://forum.xda-developers.com/showthread.php?p=47537971
One more, just to be on the safe side
jdsingle76 said:
The only issue I’ve noticed on this build is there’s no boot up sound. The coming zip (once it’s uploaded) has working sound.
Click to expand...
Click to collapse
My phone is running a rooted version of the stock MG2 ROM. While it has the Boost startup splash "4G" screen, I don't think there ever was a sound component.
Also - If I recall correctly, some custom ROMs labelled as compatible with the Sprint Galaxy S3 will cause us to LOSE 4G SERVICE, because they do not have the Boost-specific APN settings in them, and changing APN settings on Jellybean ROMs is (apparently) not possible as it was on Ice Cream Sandwich ROMs. So beware, and make sure that any ROMs that you want to flash will not kill your 4G!
SweetBearCub said:
My phone is running a rooted version of the stock MG2 ROM. While it has the Boost startup splash "4G" screen, I don't think there ever was a sound component.
Also - If I recall correctly, some custom ROMs labelled as compatible with the Sprint Galaxy S3 will cause us to LOSE 4G SERVICE, because they do not have the Boost-specific APN settings in them, and changing APN settings on Jellybean ROMs is (apparently) not possible as it was on Ice Cream Sandwich ROMs. So beware, and make sure that any ROMs that you want to flash will not kill your 4G!
Click to expand...
Click to collapse
I think it was an issue with the Tar, because when I built the flashable zips, they not only had the Boost animation, but the sound component as well. And I have seen around that some Sprint ROMs will cause issues with 4g. I know that it is possible to get into change the "guts" of your phone if you have your MSL by with JB Touchwiz ROMs by dialing ##3282# from your phone's dialer. However, for some reason, with the zip I just built, it's not cooperating. I'm going to swap out secphone.apk later today, from another stock build, and see if that fixes the issue. But thanks for the heads up. That's what this thread is all about.
I've been prompted for a system update... safe?
beneliezer said:
I've been prompted for a system update... safe?
Click to expand...
Click to collapse
If you flashed the rooted one, chances are it won't let you update, but give it a try. Additionally, if you have custom recovery, which you had to in order to flash the zip, it most likely won't let you update it either. It's an Android Software update, not a firmware. I would try it, and I'm sure it will fail, but at least you won't get prompted anymore for software updates But yes, it is safe to try.
jdsingle76 said:
If you flashed the rooted one, chances are it won't let you update, but give it a try. Additionally, if you have custom recovery, which you had to in order to flash the zip, it most likely won't let you update it either. It's an Android Software update, not a firmware. I would try it, and I'm sure it will fail, but at least you won't get prompted anymore for software updates But yes, it is safe to try.
Click to expand...
Click to collapse
jdsingle76 is correct. It won't hurt anything, it just won't work. If you accept the update, your phone will reboot into recovery, process for a few seconds, and fail with an error. However in my experience, that will not stop the software update prompts from re-occurring. If I recall, the best way to stop them was to use something like Titanium Backup and freeze something having to do with 'OTACERTS'. It's been a while, so my info may be out-of-date on that front.
can someone please reupload the stock SPH-L710 odin tar file else where before I brick my phone accidentally, its not letting me use recovery. The root method i used did not work correctly, now my phone is now working properly and i just want to get back to stock to try a different method for rooting, i need this odin file please!
nickdagreat said:
can someone please reupload the stock SPH-L710 odin tar file else where before I brick my phone accidentally, its not letting me use recovery. The root method i used did not work correctly, now my phone is now working properly and i just want to get back to stock to try a different method for rooting, i need this odin file please!
Click to expand...
Click to collapse
http://androidforums.com/boost-mob...backup-sph-l710_md7-stock-3.html#post6238089
Post #106
smith058 said:
http://androidforums.com/boost-mob...backup-sph-l710_md7-stock-3.html#post6238089
Post #106
Click to expand...
Click to collapse
Good to see ya bro. Thanks for throwing that up there. Just noticed the dropbox link was broken for too much traffic. I have the MG2 tar from Kies as well. This weekend if I get time I'll throw both of them in AFH and/or dev-host. Hope all's well, thanks for helping out!
J
Guys, i know this post is a little bit old, but i was wondering if I could flash this file with the Sprint Version (same one, SPH-L710) I know this will not harm my phone but I just want to make sure. is it safe?
erick1457 said:
Guys, i know this post is a little bit old, but i was wondering if I could flash this file with the Sprint Version (same one, SPH-L710) I know this will not harm my phone but I just want to make sure. is it safe?
Click to expand...
Click to collapse
What file from this op are you referring to? But to answer your question, yes, you can flash ant sprint file to the boost variant, and vice versa, you just might have to change apn, mmsc, stuff like that, to get mms to work.
Sent from my SPH-L710 using Tapatalk
Boost Stock 4.3
jdsingle76 said:
What file from this op are you referring to? But to answer your question, yes, you can flash ant sprint file to the boost variant, and vice versa, you just might have to change apn, mmsc, stuff like that, to get mms to work.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Thanks to all of u guys out there especially jdsingle76, Can anyone help with untouched Stock BoostMobile S3 4.3.tar ODIN ROM, i would be glad for any help in this regard, Meanwhile are we seeing Kitkat for BM S3? , Again is there a chance we can be KNOX free again in our lives?
alemosman said:
Thanks to all of u guys out there especially jdsingle76, Can anyone help with untouched Stock BoostMobile S3 4.3.tar ODIN ROM, i would be glad for any help in this regard, Meanwhile are we seeing Kitkat for BM S3? , Again is there a chance we can be KNOX free again in our lives?
Click to expand...
Click to collapse
I have not gotten my hands on a 4.3 Odin tar yet. If you do remember it'll have Knox, and I think Knox is here to stay. Ice heard rumors about Kit Kat for this phone but nothing's come out yet. Thanks for the support!
Sent from my SPH-L710 using Tapatalk
jdsingle76 said:
I have not gotten my hands on a 4.3 Odin tar yet. If you do remember it'll have Knox, and I think Knox is here to stay. Ice heard rumors about Kit Kat for this phone but nothing's come out yet. Thanks for the support!
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Thank you Jdsingle76, Boost Mobile are doing a hell of a job there keeping the 4.3 Odin tar under their sleeves.
Are your enjoying my build
Sent from my SPH-L710 using Tapatalk
knox scares me
knox bootloader scares me soo much that am still running stock unrooted, am afraid when i void my warrant i might not be able to upgrade to kitkat if it ever comes out
alemosman said:
knox bootloader scares me soo much that am still running stock unrooted, am afraid when i void my warrant i might not be able to upgrade to kitkat if it ever comes out
Click to expand...
Click to collapse
Don't fret. .. If kitkat comes out there will definitely be a custom rom made with it that you will be able to flash. With root you will have many more options than you ever will with stock.
first of all i was lucky all I had to do was go back and use a root 66 image to recover using odin.
Now i know i will sound like a newb sorry please bear with me if you can.
From the start i was on 4.1.2 on SRx Mod i decided Hay i should encrypt my phone (bad idea i got stuck in a boot loop) so after searching for how to fix it i was told to use the unbrick then i wad told to use route 66 i choose route 66. I have since successfully flashed rooted 4.1.2 but i have a few questions.
First route 66 lets you choose which recovery you wish to use. now to install a recovery (my first root it came with CWM) Should i just download the app and install CWM with rom recovery or use Goo manager to install TWRP? or should i use odin to flash it? if i should flash it where should i get the correct files?
Second.
Say I would like to update to 4.3 and take advantage of roms again. What is the safest way to go about this. Depending on rls I have been able to update via recovery and a new rom and i have had to use odin. I believe (not sure) safest way to go from a major rls to another it should be done with odin. Like going from ICS to JB so should I use odin again to root to 4.3?
So to shorten my question
How do i install recovery on a freshly rooted (re rooted via route 66) Also i am currently runnning 4.12 to update to 4.3 do i need to use odin and a 4.3 image to be safe? or can i install a 4.3 rom and it will update.
In all now that my phone is working I am weary of just trying and want to do it the correct way and now i know trying to use encryption is dumb!
THANKS in ADVANCE i appreciate your help.
When it comes to Recoveries, choos if you want CWM or TWRP. Both are good. Based on that get either Rom Manager app for CWM or Goo Manager for TWRP. Let the app install the recovery for you.
If you want 4.3, then look for Stock Mod Rom in Android Development section. Flash that rom via CWM/TWRP. Make sure to follow the instructions in the Rom's thread. Particularly the part where it wants you to flash ATT insecure kernel. The Rom is Rooted. Do not flash 4.3 via Odin.
Thanks for the refresher
I have been away for a little while and i wanted to make sure. SO to get it straight
Right now I just got back from boot loop with route 66 via odin.
To go on i simply get CWM or TWRP with the respective program (rom manager or goo manager)
Then get the 4.3 rom from the rout66 thread and update to 4.3 via recovery.
If not which rom do i use.
Edit:
Ok now i think i understand your post you directed me to use a specific rom
http://forum.xda-developers.com/showthread.php?t=2501303
So from base 4.1.2 i can update to any 4.3 rom i choose? I just want to make sure as most major releases have some issues at the beginning maybe everything is sorted and their is no problems,
One thing i want to ask is can i choose another rom as sometimes i like to switch to and from touchwiz
So i guess my question now is once i install a recovery program of my choice (i always used CWM so ill probably stick with that)
Can I install any rom no problem? as far as changing versions only go up to 4.3 dont go back down with a recovery flash?
SO AFAIK right now that everything is all good and i wont mess my phone up again when loading a rom.
Is their anything i SHOULD NOT do, Beyond common sense i know not to flash a rom for another phone ETC
I appreciate your help I haven't been following the development for a couple months So i am Rusty also its been a while since i had to start from scratch with odin and at that time we did not have the GREAT list of Official Images so I got a rooted rom that had CWM already installed. I want to get to how i was before when i was enjoying the work of the devs and loving it. being in stock reminds me of how much work the devs do YOU GUYS ARE GREAT (if any even read this thread)
BeatnikBandit said:
Thanks for the refresher
I have been away for a little while and i wanted to make sure. SO to get it straight
Right now I just got back from boot loop with route 66 via odin.
To go on i simply get CWM or TWRP with the respective program (rom manager or goo manager)
Then get the 4.3 rom from the rout66 thread and update to 4.3 via recovery.
If not which rom do i use.
Click to expand...
Click to collapse
Do not do the Red Striked part. Search for Stock Mod Rom by @saranhai
Thank you to be safe i will use the ROM you suggested although this is the only thing that worries me as i never have or really want to flash modems
YOU MUST FLASH THE T999UVUEMJ4 MODEM OR T999UVUEMJC MODEM FOR T-MOBILE GALAXY S III IN ORDER FOR DATA TO WORK; OTHERWISE YOU WILL NOT HAVE DATA
AS USUAL, I'M NOT RESPONSIBLE FOR WHAT HAPPENS TO YOUR DEVICE! ONE WRONG MOVE (Especially with the Modem) AND YOU COULD END UP WITH A VERY EXPENSIVE BRICK. PROCEED AT OWN RISK.
Click to expand...
Click to collapse
This is from the page for the
[ROM][3.9.14] .::StockMOD ROM::. | TouchWiz 4.3 | Galaxy S5 | UVUEMJC | RLS2
http://forum.xda-developers.com/showthread.php?t=2501303
I hope this is the ROM you are talking about and if so what do i do about the modem issue as I am coming from 4.1.2 IDK if i have the correct modem installed. All i have right now is Route 66 rooted 4.1.2 and CWM recovery I also created a Nandroid as soon as i got recovery so i can ave a pretty clean android to go back to if anything happens.
I am sorry i may be annoyed if i were you possibly so i hope you are hanging in there with me i really appreciate it once i do this ill be back in the game and wont need any more help. I just need to get this part sorted, THANK YOU
So other than the modem thing I think i got it, i just hope i dont have to mess with the modem IDK if I'm ready to try something that could hard brick my phone after just recovering it
Flashing the modem won't brick it. It's the exact same procedure as flashing the kernel, and the risk level is pretty much the same. As long as your device is the T999, you don't have anything to worry about. Just check the md5 on the download to make sure its not a corrupted/bad download. Even if you flash the T999L/T999V/I535 modem, it shouldn't brick. It just wouldn't get signal till you flash the correct one again. Many, many people have flashed the modems with no problems at all.
Sent from my SM-N900T using Tapatalk
THANKS DOC
I really didnt think you would answer my post!
Anyway so even though the warning says i can brick it with a modem change really all that will happen is that i will just not get Data until i install the correct one got it.
And unless anyone posts otherwise The first 4.3 rom i should install is Stock Mod Rom by @saranhai and also flash the modem T999UVUEMJC via recovery?
I tried the modem map but i had no success with getting to to work, first it said the link was not supported and i needed to revert to GMaps Classic so i did but i got the same results. Random places all over the world (some in the sea) some said city and modem some were simply city's so i think its out of date so i suppose that the worst that can happen is that i get no data i suppose i can try the other modem listed on the roms page?
If someone knows (as their are two maybe its east west cost or something of the like i live in southern California south of la but furthest from the border of Mexico in San Diego so north San Diego county but anyone that knows the area may know of the massive military base i live south east of Camp Pendleton
(off topic but if a war comes to our shores i pray i am dead already or something divine as i live very close to a large Marine Training base and camp/base in General and right next to it (on the coast) is a dual Nuclear Reactor Power plant and one reactor has been malfunctioning and AFAIK its just being maintained to keep anything catastrophic from happening (which i believe IDK for sure was the reason why it is still running but not producing power)
BeatnikBandit said:
THANKS DOC
I really didnt think you would answer my post!
Click to expand...
Click to collapse
No problem! If I am able and have something to add...
Anyway so even though the warning says i can brick it with a modem change really all that will happen is that i will just not get Data until i install the correct one got it.
Click to expand...
Click to collapse
Many people warn about that because on many devices it is true. just like a kernel or recovery though, if you flash the wrong thing to its partition, it can brick. I.e. If you flash a recovery to the modems partition.
A lot of times people bring habits from their old devices. In our case, while it is possible, it's highly unlikely you'd brick flashing the modem. We know it's not going to flash the wrong item/partition. Several people have tried flashing the I535, T999L, T999N modems and all that happened was they got no working signal. Flashed back to the correct modem and all was good again.
And unless anyone posts otherwise The first 4.3 rom i should install is Stock Mod Rom by @saranhai and also flash the modem T999UVUEMJC via recovery?
Click to expand...
Click to collapse
This would be my recommendation, yes. Just follow instructions in the OP.
I tried the modem map but i had no success with getting to to work, first it said the link was not supported and i needed to revert to GMaps Classic so i did but i got the same results. Random places all over the world (some in the sea) some said city and modem some were simply city's so i think its out of date so i suppose that the worst that can happen is that i get no data i suppose i can try the other modem listed on the roms page?
Click to expand...
Click to collapse
The map is definitely screwed up and I apologize for that! I meant to start a new one a while back but just never got around to it. Still on my to do list!
Good Luck!
Sent from my SM-N900T using Tapatalk
Well thank you guys both I appreciate you gave me the correct info fast Perseus71 and thank you for clarifying DocHoliday77 And an extra thank you for all the work you do for the S III community!
i was just about to do this althoug i downloaded the rom and the modem but now what about the "insecure Kernal" I dont want to mess my phone up again sorry for all the questions its just after you mess up your phone when yoyu come back to roms and its just like getting a traffic ticket for a little bit you drive like you just got a ticket REALLY SAFE with no nerve so sorry but thats my mindset i just messed up my phone and dont want to do it again (i just finished paying for it too so i donk want to break my just paid off 600 dollar car lol.
so yeah AFAIK the post sys all i need is the modem but do i need the kernal too as it may not be listed as it is know its needed at one point when updating versions?
THANKS AND SORRY this is probably the last thing i need as i was just about to flash but just got worried
If wifi doesnt turn on, then try the kernel. If everything boots and runs as you like, then its up to you.
Sent from my SM-N900T using Tapatalk
Hey guys, I am new to this forum here but before anyone flames me, I did read the faqs and tried to uninstall from there but it did not work out. Apparently I dont think you can get rid of CM11 since you cant install any stock firmware older than it? Before I installed CM11, I was on jellybean. I had tried to find the latest kitkat update for the s3 (att) and there is no file of it found online (tried sammobile). When I tried flashing an older firmware with ODIN, it just fails at "NAND!". Any help would be appreciated. I am COMPELETELY new at this so specific directions would be appreciated!
I really do love cyanogenmod but there are simply too many glitches and not enough guidance on how to fix em. I am, however, currently using it on my HP touchpad, if anyone remembers what it is . Maybe ill go back to using it in the future.
thanks!
Your rom (cm) has nothing to do with what firmware you can or cannot flash. Once you have updated to 4.3 firmware or newer, you can only flash the same or newer firmware in odin from now on. (Regardless of firmware you can still flash older roms btw)
Using terminal emulator, enter this to find your current firmware build:
getprop ro.bootloader
I suspect you are on a 4.3 build. So odin flash that same firmware. You can find it in these forums. After that you can get the ota to update fully to kk.
There are other methods of updating. Just check the General section. (enewman17 has a few threads that will help)
Note: anytime you go between touchwiz and non touchwiz roms, you will have to factory reset or it'll hang at boot.
DocHoliday77 said:
Your rom (cm) has nothing to do with what firmware you can or cannot flash. Once you have updated to 4.3 firmware or newer, you can only flash the same or newer firmware in odin from now on. (Regardless of firmware you can still flash older roms btw)
Using terminal emulator, enter this to find your current firmware build:
getprop ro.bootloader
I suspect you are on a 4.3 build. So odin flash that same firmware. You can find it in these forums. After that you can get the ota to update fully to kk.
There are other methods of updating. Just check the General section. (enewman17 has a few threads that will help)
Note: anytime you go between touchwiz and non touchwiz roms, you will have to factory reset or it'll hang at boot.
Click to expand...
Click to collapse
..
I am on "I747UCUEMJB"
and i am not sure what build i am on but according to my "build number"this is what it says: "cm_d2att-userbug 4.4.2 KOT49H"
The main issue is, I cannot find 4.3 update anywhere on the internet
The MJB is your current firmware/bootloader build/version.
The build number displayed in settings only represents the rom, which is often different, and doesnt really matter to much.
From this post/thread
http://forum.xda-developers.com/showthread.php?p=52341560
Direct link to MJB firmware
http://www.androidfilehost.com/?fid=23329332407590581
DocHoliday77 said:
The MJB is your current firmware/bootloader build/version.
The build number displayed in settings only represents the rom, which is often different, and doesnt really matter to much.
From this post/thread
http://forum.xda-developers.com/showthread.php?p=52341560
Direct link to MJB firmware
http://www.androidfilehost.com/?fid=23329332407590581
Click to expand...
Click to collapse
i have no idea what MJB means (i google'd it) and i just found out what my bootloader version is via download mode (its at the very bottom) and i have version 2.0?
ok downloading the giant file now. will report details. just follow instructions in the first link?
[sorry, like i said, im a noob so i really apologize for the lack of terms here]
MJB is just short for I747UCUEMJB. Sorry if I confused you. And the S/W revision being 2.0 is what Odin uses to know what firmware it is allowed to flash. In this case 2.0 tells odin it can flash the MJB firmware, or anything newer.
And yes, follow the instructions he posted and you should be fine.
Oh, and if you did not run the getprop command I posted before, please do so before flashing....just to be on the safe side. If it returns I747UCUEMJB, you are good to go. If it returns anything else, let me know before flashing.
DocHoliday77 said:
MJB is just short for I747UCUEMJB. Sorry if I confused you. And the S/W revision being 2.0 is what Odin uses to know what firmware it is allowed to flash. In this case 2.0 tells odin it can flash the MJB firmware, or anything newer.
And yes, follow the instructions he posted and you should be fine.
Oh, and if you did not run the getprop command I posted before, please do so before flashing....just to be on the safe side. If it returns I747UCUEMJB, you are good to go. If it returns anything else, let me know before flashing.
Click to expand...
Click to collapse
Cool! Got it. I think that was my main problem. I could only find 4.0 (or 4.1) and have been trying to use that on ODIN. Perhaps that was the main issue....
Oh already ran it and got "I747UCUEMJB", sorry if didnt say it properly.
Really appreciate the help! Ive at this for days and no solutions. Sometimes the hacking/custom firmware isnt for everybody
Ill update what happens. Download is taking forever.
EDIT: BTW, for the first link, which poster am I gonna have to follow? im assuming "garbage guy"?
I though you did run the command already, but just wanted to be certain is all. For some reason AT&T stopped releasing their firmware, which has been causing all kinds of problems for people.
Anyway, it sounds like you are good to go! Good luck!
Oh, and if the firmware you're downloading is a .zip or .7z file, make sure you extract it first. Odin only flashes .tar and .tar.md5 files.
DocHoliday77 said:
I though you did run the command already, but just wanted to be certain is all. For some reason AT&T stopped releasing their firmware, which has been causing all kinds of problems for people.
Anyway, it sounds like you are good to go! Good luck!
Oh, and if the firmware you're downloading is a .zip or .7z file, make sure you extract it first. Odin only flashes .tar and .tar.md5 files.
Click to expand...
Click to collapse
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
david12795 said:
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
Click to expand...
Click to collapse
Weird, I went straight to update phone and it said my phone is up to date? I thought the official 4.4 update came out for the S3?
david12795 said:
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
Click to expand...
Click to collapse
Awesome!
really glad to hear that! The only thing I can think of thst you might want to do next is backing up your nv data. The following is a copy/past from a post I made a few min ago... root is required to fo this btw, just so you know.
(Since you are looking to update though, I recommend waiting till you have updated before rooting and running this backup)
It's a super simple procedure and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
david12795 said:
Weird, I went straight to update phone and it said my phone is up to date? I thought the official 4.4 update came out for the S3?
Click to expand...
Click to collapse
That has been released, but OTA's are generally rolled out in stages over several weeks. Usually done by region. So it msy not have started in your area just yet.
Two alternatives you can try though, install kies on your computer and update through that. Or there are a couple if threads in the General section that provide the ota for download.
Enewman17 has a few threads helping folks to update so I recommend checking them out as well.
Ive heard that some people have gone to best buy and they were able to initiate the update there. I dont know much more about this though.
DocHoliday77 said:
Awesome!
really glad to hear that! The only thing I can think of thst you might want to do next is backing up your nv data. The following is a copy/past from a post I made a few min ago... root is required to fo this btw, just so you know.
(Since you are looking to update though, I recommend waiting till you have updated before rooting and running this backup)
It's a super simple procedure and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
Click to expand...
Click to collapse
Thank you! I will look into this. I just figured for some reason...I would have some data left from cyanogenmod, if that makes sense. In other words, i want my phone to be as fresh as possible. I only ask this because when I had CM, i accidentally made a backup of it through rom manager (or clockwork) and I am not sure if its in my partition somewhere.
That has been released, but OTA's are generally rolled out in stages over several weeks. Usually done by region. So it msy not have started in your area just yet.
Two alternatives you can try though, install kies on your computer and update through that. Or there are a couple if threads in the General section that provide the ota for download.
Enewman17 has a few threads helping folks to update so I recommend checking them out as well.
Ive heard that some people have gone to best buy and they were able to initiate the update there. I dont know much more about this though.
Click to expand...
Click to collapse
TIL that OTA arent as fast. Ill download KIES and give it a try.
Just installed KIES and it said my phone has the latest firmware?
david12795 said:
Thank you! I will look into this. I just figured for some reason...I would have some data left from cyanogenmod, if that makes sense. In other words, i want my phone to be as fresh as possible. I only ask this because when I had CM, i accidentally made a backup of it through rom manager (or clockwork) and I am not sure if its in my partition somewhere.
TIL that OTA arent as fast. Ill download KIES and give it a try.
Click to expand...
Click to collapse
Factory resetting with stock recovery installed wipes all data except the external sdcard. I am so sorry I should've mentioned this before. I was thinking you had already done one at some point and didn't have anything left to worry about. Still, I should have asked and I do apologize for that. Hopefully if it was really important it was saved to the external sdcard....
david12795 said:
Just installed KIES and it said my phone has the latest firmware?
Click to expand...
Click to collapse
Ok, I wasn't sure about that. I personally never need or use kies so I didn't know if it was tied to the staged rollouts. It would appear that it is though.
Give me a few min and ill post links to the threads where you can download the ota or update via a different method.
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
UCUEMJB to UCUFNE4 firmware update - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2808654.
How to update SGH-I747 yo UCUFNE4_4.4.2 - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2789917
[Download] AT&T Kitkat OTA file - thread by bkong
http://forum.xda-developers.com/showthread.php?t=2788012
I suggest trying the third one by bkong first. He posted a pure OTA file you can try to update with.
The first option is a recovery flashable firmware, but does not include the /system (ROM) portion. To fully update using this you'll flash the firmware per his instructions and then go to his development thread for the stock rom. It is here: http://forum.xda-developers.com/showthread.php?t=2788357
The second option is the OTA file, but it has been slightly modified to skip certain file checks. If the original OTA doesnt work, theres a good chance this will. (Since you are full stock now either one should flash without issue).
Hope those help! I recommend doing a bit of reading about each one (at least the OP and last few pages) and start with whichever you are most comfortable with.
Or, you could always use that most valuable tool, patience, and wait for the OTA to roll out for your area.
Good luck!
DocHoliday77 said:
Factory resetting with stock recovery installed wipes all data except the external sdcard. I am so sorry I should've mentioned this before. I was thinking you had already done one at some point and didn't have anything left to worry about. Still, I should have asked and I do apologize for that. Hopefully if it was really important it was saved to the external sdcard....
Ok, I wasn't sure about that. I personally never need or use kies so I didn't know if it was tied to the staged rollouts. It would appear that it is though.
Give me a few min and ill post links to the threads where you can download the ota or update via a different method.
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
UCUEMJB to UCUFNE4 firmware update - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2808654.
How to update SGH-I747 yo UCUFNE4_4.4.2 - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2789917
[Download] AT&T Kitkat OTA file - thread by bkong
http://forum.xda-developers.com/showthread.php?t=2788012
I suggest trying the third one by bkong first. He posted a pure OTA file you can try to update with.
The first option is a recovery flashable firmware, but does not include the /system (ROM) portion. To fully update using this you'll flash the firmware per his instructions and then go to his development thread for the stock rom. It is here: http://forum.xda-developers.com/showthread.php?t=2788357
The second option is the OTA file, but it has been slightly modified to skip certain file checks. If the original OTA doesnt work, theres a good chance this will. (Since you are full stock now either one should flash without issue).
Hope those help! I recommend doing a bit of reading about each one (at least the OP and last few pages) and start with whichever you are most comfortable with.
Or, you could always use that most valuable tool, patience, and wait for the OTA to roll out for your area.
Good luck!
Click to expand...
Click to collapse
No no! Its fine, I wasnt planning using it or anything, I just wanted to get rid of it since I have no use for it, no need to apologize. , I was fully aware that I would lose all files, other than SD ext drive. I just wanted to make sure that all files are in the right place and none of the unnecessary files are taking up space (e.g. files from cyanogenmod)
As for the update, I talked to a samsung representative and they said one can go to Best Buy and get it updated there through a technician, so Ill try that later since I am close to it ATM. If it back fires, Ill try your suggestions.
I really do appreciate for the help , I have been completely lost for days but it turns out I was just using the wrong firmware. Thanks for pointing it out. Good karma is coming your way . Hopefully one day, I will be here again and trying out a new custom firmware.
Glad I could help!
If I remember right, someone who mentioned the best buy thing had said at the time that the first store they went to did not have the update yet. But I think they found another in their area did. So if they say its up to date and cant help, you might find another store close by can. (If there is one of course!)
Just fyi so you're not too surprised if that happens.
DocHoliday77 said:
Glad I could help!
If I remember right, someone who mentioned the best buy thing had said at the time that the first store they went to did not have the update yet. But I think they found another in their area did. So if they say its up to date and cant help, you might find another store close by can. (If there is one of course!)
Just fyi so you're not too surprised if that happens.
Click to expand...
Click to collapse
Ill hope for the best and prepare for the worst.
Of course, if the worst happens, I can just use one of your links you mentioned. :good::good:
Here goes...
I got a new phone which is running great and before selling my S3, I wanted to install CM and get rid of the bloatware. Figured it would help the sale. Ha!
The S3 was already rooted and CWM installed but still using the stock OS. Here's where I really ****ed up, I didn't right down the baseband version or android version before trying to get CM installed.
CM10 wouldn't install so after some digging I read that I needed to unlock the bootloader. All the sites say to use EZ-unlock. I do. It unlocks. I restart the device and it's now hard bricked.
Before becoming a brick, I made a backup using CWM but I'm not sure how helpful it is at this point.
I don't know which Android version I'm running but it should be the latest OTA since I always installed the updates.
I tried debrick images for 4.3 and 4.4.2 without any luck.
Essentially, I need a little bit of guidance before I give up for good on this phone. How can I find out which Android version was running in order to use the right debrick img. Does it matter that I was using a custom recovery and that the phone was rooted?
Thanks for the help, guys. I've got too far down the rabbit hole and I'm trying to get out.
i live a little below the bottom of the rabbit hole. my first and only (so far , fingers crossed) brick was by trying to unlock the bootloader of my att i747 s3. guess what :banghead: they arent locked. go figure. and again :banghead: my best guess if you kept updates updated. search for whatever was the latest (which you should be on) use a debrick image for that version. and i guess youve already read the "debrick thread". if one microsd card doesnt work , try another. read too many times where one class/size would work for one user but not another.
i know this isnt much help. i would just say keep trying.
maybe even jtag might ¿ help?
good luck.
maybe try here if havent already.
http://forum.xda-developers.com/showthread.php?t=2549068
"err on the side of kindness"
thats what pretty much happend to me on my s3 i747M. i was downloading a custom rom, phone was rooted had its original os, but i installed a rom, that said it was for i747m, but it was really for the i9300. so after it seemed to install, i click reboot, and instant brick. i also made a WHOLE backup before i did anything, and have flashed a number of different roms in the past.
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
mrrocketdog said:
i live a little below the bottom of the rabbit hole. my first and only (so far , fingers crossed) brick was by trying to unlock the bootloader of my att i747 s3. guess what :banghead: they arent locked. go figure. and again :banghead: my best guess if you kept updates updated. search for whatever was the latest (which you should be on) use a debrick image for that version. and i guess youve already read the "debrick thread". if one microsd card doesnt work , try another. read too many times where one class/size would work for one user but not another.
i know this isnt much help. i would just say keep trying.
maybe even jtag might ¿ help?
good luck.
maybe try here if havent already.
http://forum.xda-developers.com/showthread.php?t=2549068
"err on the side of kindness"
Click to expand...
Click to collapse
this is only if you got bricked while upgrading to 4.4.2 i tried this method already didnt work
MhikeiMPC12 said:
thats what pretty much happend to me on my s3 i747M. i was downloading a custom rom, phone was rooted had its original os, but i installed a rom, that said it was for i747m, but it was really for the i9300. so after it seemed to install, i click reboot, and instant brick. i also made a WHOLE backup before i did anything, and have flashed a number of different roms in the past.
Not quite the same situation. I was following instructions install a new rom and it said to unlock the bootloader when in the end it wasn't necessary. EZ-unlock bricked my phone. I will keep trying with various SD cards.
Does anyone have a link to a KitKat (4.4.2) debrick dump for the I747?
Click to expand...
Click to collapse
Found the right debrick file
Update: I found this debrick file for my S3 on Koodo with 4.4. : http://d-h.st/w7g
Thanks to mitch0422 and this thread: http://forum.xda-developers.com/showthread.php?t=2598240