I rooted my GS4 yesterday and had no issues at all until i tried to flash a MOD to obtain wireless hotspot, but what i didnt notice was the MOD was for a Sprint version GS4. I know know if thats exactly what made my phone brick but im pretty positive because it was during the reboot that the phone got stuck on the TMO screen and apparently remaining soft-bricked. I spent the rest of the night and all of today reading and researching how to fix it myself before coming here to ask for help, so please bare with me.
I have already attempted to flash the official stock firmware using Odin, but it displays an error everytime saying it failed and something about AUTH. Sorry if im sounding vague, i am on a back up phone to use the internet and forgot to right down the exact message.. Anywho, i tried wiping everything and redoing the process and i even tried to flash the appropiate PIT file that i found but it still displays an error and says failed because of some AUTH or SEC problem.
Ive been at this diligently for almost 12 hours. My brain is filled with all these suggestions and methods that i have tried to use to restore my phone back to factory, but none of them have worked. I can still get into recovery and all that, so im assuming that there is still good chance i could fix the problem?
Also i am starting to get myself more and more confused about whether the firmware i downloaded is the right one i need for my phone, it seemed so at first but now i see theres TONS of region codes that can determine the firmware version?
Sorry if im all over the place, but i just dont know which step to take next..
I appreciate any help that is given, and im even willing to pay (some) bucks or maybe even (btc) for someone to walk me through what i need to do or what im doing wrong.
Thanks in Advance
Have you followed every single thing in the return to stock thread? Including updating your drivers, using the USB cable that came with your phone, running Odin as admin, etc?
Toleraen said:
Have you followed every single thing in the return to stock thread? Including updating your drivers, using the USB cable that came with your phone, running Odin as admin, etc?
Click to expand...
Click to collapse
No i havent tried that threads strategy, although i have done the same exact steps but only difference i see is that the firmware file name is:
M919UVUAMDL
While the one i was trying to use earlier was:
I9505XXUAMDM
This is where im getting very confused because i cant find a cut and dry way of knowing which firmware is the correct one..
koolbreez12 said:
No i havent tried that threads strategy, although i have done the same exact steps but only difference i see is that the firmware file name is:
M919UVUAMDL
While the one i was trying to use earlier was:
I9505XXUAMDM
This is where im getting very confused because i cant find a cut and dry way of knowing which firmware is the correct one..
Click to expand...
Click to collapse
You do have the T-Mobile SGS4, correct? Any files with I9505 in the name are for the international version, which is what you flashed (not the right file). All of ours will mention SGH-M919, M919, or jfltetmo in the file name. Pull the one in the thread I linked above and push that.
Crossing your fingers while doing so couldn't hurt...
Edit: I'd recommend using the "Download UVUAMDL Official TAR" in that thread as well, not the "stock tar (original)", since the MDL is official.
Toleraen said:
You do have the T-Mobile SGS4, correct? Any files with I9505 in the name are for the international version, which is what you flashed (not the right file). All of ours will mention SGH-M919, M919, or jfltetmo in the file name. Pull the one in the thread I linked above and push that.
Crossing your fingers while doing so couldn't hurt...
Edit: I'd recommend using the "Download UVUAMDL Official TAR" in that thread as well, not the "stock tar (original)", since the MDL is official.
Click to expand...
Click to collapse
Thanks so much, i feel stupid for not realizing the difference between the two haha. Im d/l the firmware from the thread you referenced as we speak so i definitely will keep my fingers crossed and let you know how it turns out!
Thanks again. Im not sure how to give a thanks on here or credit for you help but your help is definitely appreciated.
error post
If you can get into download mode i would suggest flashing stock with that then rerooting that way the program downloads all of the nessacary stuff on its own.
koolbreez12 said:
Thanks so much, i feel stupid for not realizing the difference between the two haha. Im d/l the firmware from the thread you referenced as we speak so i definitely will keep my fingers crossed and let you know how it turns out!
Thanks again. Im not sure how to give a thanks on here or credit for you help but your help is definitely appreciated.
Click to expand...
Click to collapse
Welcome!
Sent from my SGH-M919 using xda premium
Related
After the Rooting procedure failed (for some reason), my phone just went popped up with an error "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
EDITS:
Progress 1: Got into the download mode but I cant seem to find the firmware appropriate for it:
SGH-1747M
Baseband: 1747MVLLH1
Progress 2: After scouring the internet I have found SGH-1747M
The problem is its 1747MVLALH1
Rather than 1747MVLLH1
Not quite sure at the moment if this is the right firmware for my phone
Advice would be appreciated
I'm sorry, can you be more clear? Can you not use the phone at all? Also, what method of root did you use?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
If you are able to get into download mode then you are good to go, it just sounds like whatever you were flashing was either incomplete or was interrupted, otherwise referred to as a bad flash. Mosy on over to this thread, http://forum.xda-developers.com/showthread.php?t=1739426 , read it through...maybe even twice and flash the stock rom with root. Once this is working you can proceed to installing a custom recovery. The easiest way ti do this is install Clockwork Rom Manager from the market and install ClockWorkMod Recovery. Once you have a recovery (and before you flash anything from here on for that matter) make a backup, this will give you a fall back in case of future bad flashes. Let us know how it goes.
You guys could say that I "bad flash"-ed it
I did rooting before with my S2 and it had no problem but when I flashed the S3 it said that it failed and thats when this problem arose
Anyway is I747MVLALH1 the same as I747MVLLH1 (my baseband)
I'm not sure what 'rooting procedure' you used as you didn't specify, but if you use the guide i linked in my previous post and follow the directions exactly you should be ok and chalk this up as a lesson learned.
dntesinfrno said:
I'm not sure what 'rooting procedure' you used as you didn't specify, but if you use the guide i linked in my previous post and follow the directions exactly you should be ok and chalk this up as a lesson learned.
Click to expand...
Click to collapse
Its the one made by chainfire and I probably got the wrong guide thats why it went like that
I'll try your guide hopefully it works
cant post links at the moment
Thank you sir, I'll probably try the clockwork mod when its confirmed working for Rogers users
It's entirely possible with all the different variations of the GS3, which is why i emphasized you read everything very carefully first, and follow each direction exactly. If something doesn't go as it is supposed then there is a reason, 'i'll just skip that step' rarely works :cyclops:. Let me know how it goes.
dntesinfrno said:
It's entirely possible with all the different variations of the GS3, which is why i emphasized you read everything very carefully first, and follow each direction exactly. If something doesn't go as it is supposed then there is a reason, 'i'll just skip that step' rarely works :cyclops:. Let me know how it goes.
Click to expand...
Click to collapse
It worked great
you literally saved my bum from spending 600 bucks - I appreciate it
for now Im just gonna leave it at that (stock and rooted) since you did mention in the Third step that your not quite sure if it works for Rogers users as well (clockwork etc..)
gek00 said:
It worked great
you literally saved my bum from spending 600 bucks - I appreciate it
for now Im just gonna leave it at that (stock and rooted) since you did mention in the Third step that your not quite sure if it works for Rogers users as well (clockwork etc..)
Click to expand...
Click to collapse
I believe you may have just misunderstood me, but yes CWM will work with Rogers based phones although not being a Rogers user myself i cannot offer any insight to any do's or don't specific to that carrier, if there are any. In any case, i'm glad you got your phone working, i've been in that position a few times myself.
dntesinfrno said:
I believe you may have just misunderstood me, but yes CWM will work with Rogers based phones although not being a Rogers user myself i cannot offer any insight to any do's or don't specific to that carrier, if there are any. In any case, i'm glad you got your phone working, i've been in that position a few times myself.
Click to expand...
Click to collapse
Oh yes, I apologize for that I might try it later on but one last question (if its not too much of a bother)
Would you mind giving me advice on what ROM is a "go-to" at the moment for the S3
Thanks in advance
The short answer to that question is no, as it is really a personal preference as well as device dependent, meaning the same ROM may or may not run the same way on two seemingly identical phones for any number of reasons. Personally I use the JB AOKP, which is also what i used to run on my GS2 , a lot of people seem to like Cyanogenmod as well. The only way to know is flash them and find out if you like them. Just always make sure to have a recovery backup handy in case you dont like it, or if anything goes wrong during the flash. Like i said before, the important thing is to read everything in the post carefully and follow the directions .
I have sprint gs3 rooted with cwm 6.0.3.1 installed on it. I was trying to flash SuperNexus-2.0-i9300-BUILD4. Zip onto my phone. I recieved an error when it attempted to do the flash. The error was: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. This also happens when try to restore a backup not done by rom manager
Please I hope you where not successful at all. You are trying to flash an International rom. Can't you see it says it's for the I9300 not the SPH-L710??? You will brick your phone. Please stop and do about two more Weeks of reading and research.
Sent from the future via Xparent Green Tapatalk 2
Do what Ed says unless you want a $700 paperweight. Would you put Diesel fuel into your gasoline powered car?
Now I understand why carriers are locking the bootloader.
As said above, PLEASE put the phone DOWN and step away from the merchandise....now go read, read, read, and read. You should never flash roms that are not made for your specific device AND carrier. Ever. No exceptions.
Here are two links to with a wealth of information for you and anyone new to rooting and flashing roms:
http://forum.xda-developers.com/showthread.php?t=1726558
and just to drive the subject home, because it is very important:
http://forum.xda-developers.com/showthread.php?t=2156714
There is another thread HERE that you should look over.
Thank you didn't even notice that. As far as the recovery.log file, what is going on there?
Okikix said:
Thank you didn't even notice that. As far as the recovery.log file, what is going on there?
Click to expand...
Click to collapse
Use the links above and read Don't worry about the recovery log for now.
Okikix said:
Thank you didn't even notice that. As far as the recovery.log file, what is going on there?
Click to expand...
Click to collapse
as noted above don't worry about that but be thankful you got that error it just might of saved your phone.
Your device still works?!?! You should be thanking the GS3 Gods right now cause someone was looking over your shoulder lol. I seriouslyyyy question how some people here even got through the rooting process successfully... SMH
First of all I would like to say this is my first post and I am feeling very optimistic as I have seen all the great things you guys have done over here! I understand in order to solve my problem I will have to be as detailed as I can, but please bare with me as I am a noob to this stuff and seem to have run into some trouble
Okay so I got a new S3 Last week and wanted to try it out on some new custom roms, I flashed it to CM 10.1 nightly using the roms downloaded via GooManager, all was fine and I had no problems until i flashed to a newer version of the nightly build and lost my signal, it always said Emergency calls only.
This happened to me once before but I solved it by flashing a modem file via Odin, since then I had to preform full system reset as I was considering selling my phone, it didn't come to that and now I am back to square one and once again I have no signal.
I have tried flashing the same modem file as I did before with no effect this time round
I have since tried many different modems and completely forgot which one has worked in the past. I have no back up files what so ever so I need to know what it is that is causing it not to get a signal. Could it be the kernel I am using? or is there a pacific modem for my ROM which I need.
I understand this is my own fault and stupidity, you guys are my last hope, I have also tried stock firmware which also has no signal.
It is an international i9300 with UK T-Mobile.
Please help me save my phone!
I hope you didn't flash a Tmobiles modem, because international gs3 and SGH-T999 aren't similar I believe other than looking the same. And more than likely you've lost your IMEI. Please goto settings and check your IMEI. Please do not post it, just verify if it's 0 or a 16 digit string.
Sent from my Nexus 7 grouper running Clean ROM 4.0 (4.3 stock rooted) owned by an MSMC diamond camo try hard.
Welcome to the forum! Albeit not quite the right one.
You need to post this in the international forum. This is for the US/Canadian models only. They are very different from yours, and not many people here will know much about it.
Do not flash anything you find here! It is highly likely to brick your phone. If you flashed our modems. Consider yourself lucky and now you know why it isn't working. Check with the guys in the other forum for your next step though.
I wish you luck!
Sent from my SGH-T999 using xda premium
Danny123173 said:
First of all I would like to say this is my first post and I am feeling very optimistic as I have seen all the great things you guys have done over here! I understand in order to solve my problem I will have to be as detailed as I can, but please bare with me as I am a noob to this stuff and seem to have run into some trouble
Okay so I got a new S3 Last week and wanted to try it out on some new custom roms, I flashed it to CM 10.1 nightly using the roms downloaded via GooManager, all was fine and I had no problems until i flashed to a newer version of the nightly build and lost my signal, it always said Emergency calls only.
This happened to me once before but I solved it by flashing a modem file via Odin, since then I had to preform full system reset as I was considering selling my phone, it didn't come to that and now I am back to square one and once again I have no signal.
I have tried flashing the same modem file as I did before with no effect this time round
I have since tried many different modems and completely forgot which one has worked in the past. I have no back up files what so ever so I need to know what it is that is causing it not to get a signal. Could it be the kernel I am using? or is there a pacific modem for my ROM which I need.
I understand this is my own fault and stupidity, you guys are my last hope, I have also tried stock firmware which also has no signal.
It is an international i9300 with UK T-Mobile.
Please help me save my phone!
Click to expand...
Click to collapse
As stated, incorrect forum. I'd give you the proper link if I was at a computer. But thank you for the detailed panic free post. It's seriously appreciated.
You're going to end up having to flash the modem that's for your phone, or maybe Odin stock.
You are right I have no imie number just a 16 digit string :/ sorry guys for posting in the wrong arearly next time I will make sure I will post correctly.
I am strating to get concerned, is this an easy fix? I dont mind wiping any data or using a certain Rom I just don't know which modem to use, some modems show me my bars but it still wont get any service. This one currently just shows a circle and cross icon with no bars at all. I am running stock.
Sent from my GT-I9300 using xda app-developers app
Also if someone could post a link to the correct forum so I know where to head that would be great. Thanks for the help guys!!
Sent from my GT-I9300 using xda app-developers app
Solved! Thanks again guys!!
DocHoliday77 said:
Welcome to the forum! Albeit not quite the right one.
You need to post this in the international forum. This is for the US/Canadian models only. They are very different from yours, and not many people here will know much about it.
Do not flash anything you find here! It is highly likely to brick your phone. If you flashed our modems. Consider yourself lucky and now you know why it isn't working. Check with the guys in the other forum for your next step though.
I wish you luck!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I apologise thank you for the link, if I run into anymore trouble I will post to the correct section. I am glad to inform you I have solved the issue. It turns out I installed a bad modem which actually changes the file type of type of the efs folder. Causing roms to not reading it properly.
http://forum.xda-developers.com/showthread.php?t=2377731
I fixed the issue by installing a stock firmware found on this post...
http://50.23.216.69-static.reverse.softlayer.com/showthread.php?t=1646610
This firmware carries a modem file which can read the modified efs folder, and in result restoring my IMEI Number and signal even after I flashed the rom to CM 10.1.
I hope some one else can stumble on to this and it helps them, please be aware though I have an intervention Galaxy s3 and this may not work in the states or other parts of the world.
Thanks again massive help, its people like you that make this the best source of information on the internet!
Once again really sorry about posting in the wrong forums, I will try not let it happen again in the future!
Danny123173 said:
I apologise thank you for the link, if I run into anymore trouble I will post to the correct section. I am glad to inform you I have solved the issue. It turns out I installed a bad modem which actually changes the file type of type of the efs folder. Causing roms to not reading it properly.
http://forum.xda-developers.com/showthread.php?t=2377731
I fixed the issue by installing a stock firmware found on this post...
http://50.23.216.69-static.reverse.softlayer.com/showthread.php?t=1646610
This firmware carries a modem file which can read the modified efs folder, and in result restoring my IMEI Number and signal even after I flashed the rom to CM 10.1.
I hope some one else can stumble on to this and it helps them, please be aware though I have an intervention Galaxy s3 and this may not work in the states or other parts of the world.
Thanks again massive help, its people like you that make this the best source of information on the internet!
Once again really sorry about posting in the wrong forums, I will try not let it happen again in the future!
Click to expand...
Click to collapse
Congrats, I'm glad you rectified the problem! Remember for next time, when you're not able to access data or you're stuck at 2G that your IMEI has most likely went! For future reference, I recommend making an EFS backup. We've all been there before and we know the scare!
And btw, welcome to XDA, enjoy the stay lol.
Yeah I have double backed up and thanks for the tip I will keep that in mind thanks again dude!
Sent from my GT-I9300 using xda app-developers app
I ran into the same problem before, had to install stock modem to get my signal working again.
You should refer to this thread which will help you backup your efs: http://forum.xda-developers.com/showthread.php?t=2298104
I ran into the same problem after flashing a custom rom I lost my signal and imei not fixed yet
Ra2fet said:
I ran into the same problem after flashing a custom rom I lost my signal and imei not fixed yet
Click to expand...
Click to collapse
If you want help, we need more info, starting with what Rom, exactly, did you flash.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
If you want help, we need more info, starting with what Rom, exactly, did you flash.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yesterday I flashed S4 Revolution v8.0 [ROM][4.3 MJ9] then I lost my signal and imei and the baseband version is empty although I wipe my cash and data before flashing this rom.
I don't think that's a Rom we have for our device, unless I overlooked it.
Googled it and came up as an I9300 Rom. If this is what you flashed consider yourself extraordinarily lucky it's not hard bricked!
Odin flash the firmware for your model only! Hopefully that fixes it.....
And NEVER flash a Rom not for your model device.
Sent from my SGH-T999 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:
I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
cdriver said:
I rooted my old milestone many years ago but havee been keeping my devices stock ever since, until today that is. Today I decided I wanted to try to root my Samsung SGH-I747M with Telus and everything seemed to start off smoothly. Once installed the SuperSU stopped working. I tried fixs I had read online such as updating the app, but this did not work. I read on a forum that you could flash something to disable know to help fix the problem. When I tried going this avenue I was not able to reboot my phone. I tried restoring from a backup taken before flashing, but I havent done any of this in so long im not entirely sure the backup took properly. At one point I got a message saying no OS was installed but after restoring this seemed to go away. I apparently do not remember anything about rooting from my milestone and am hoping someone may be able to help me get out of this mess. I am currently downloading the stock firmware and I think I will try flashing it tomorrow. I also was hoping someone could point me in the direction of a thread on xda that went into a more detailed explanation of how rooting works, what specifically roms and flashing all is and does. Any help is greatly appreciated.
Click to expand...
Click to collapse
General section is most likely the best place for that.
Here's a How-to that should get you started: http://forum.xda-developers.com/showthread.php?t=2538991
And here is the Sticky index: http://forum.xda-developers.com/showthread.php?t=1725839 Lots of good guides and info in there!
General section is most likely the best place for that.
Click to expand...
Click to collapse
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
cdriver said:
The Only problem is I already attempted to follow this and my phone will no longer boot up. Also I tried navigating through the stickies. couldn't find much info for my device. I will be trying to flash the stock firmware tonight but I want to have a clear understanding on what flashing is and what the difference is between os firmware kernel and rom and such BEFORE flashing this firmware tonight. I hope someone will be able to help.
Click to expand...
Click to collapse
Well that info is already in the Sticky Index. Understanding what you're doing (or about to do) is really important but you gotta start reading, it's all there.
OS, firmware and ROM are the same thing.
When your phone boots, it basically goes: Bootloaders -> Kernel -> ROM (OS).
The kernel has pretty much all the "underground" controls (RAM, Mhz, governor, scheduler, BT, Wifi, etc).
I won't write everything but those are the basics.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Also, having a Canadian variant of the S3 (that's what the M is for), doesn't change much other than flashing bootloaders and stock ROM (which you'll wanna use the Canadian variant bootloaders and Telus ROM for stock). Everything else is basically the same.
Click to expand...
Click to collapse
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
cdriver said:
Sweet I will definitely check that out. So I did flash twrp to my phone. Is it possible that I flashed the version say for the i747 but not the m version and that is why the phone wont move past the samsung screen? Also should I attempt to get rid of twrp before flashing the stock firmware. This should answer all my questions and then I will explore the stickies some more.
Click to expand...
Click to collapse
If flashing a stock ROM, flash the Telus one. If flashing a custom ROM, it doesn't matter (I747 or M variant), as long as it's D2LTE.
Your recovery doesn't change anything to flashing with Odin, it will overwrite it.
Flashing the stock firmware fixed my problems. Thanks for all of your help and I will definitely be checking out the links that you sent me before trying to root again tomorrow.