Develop Bugs

[ROM][GSM][ROGERS] Stock ROGERS Froyo UXJJ6 / Gingerbread UXKG1

This thread contains the stock ROGERS firmware that comes with the GT-P1000R.
Andrew_Low has provided a copy of his stock FROYO backup, which I tested on my tab and confirm that it is working. The kernel is rooted, other than that it is a clean ROGERS rom. For further details on this refer to post 2.
He was also able to capture the GINGERBREAD update (which I have not tested as of yet, any testers please post your results).
This is the stock update available from KIES. For further details on this refer to post 2.
Many thanks to him for this, if it helps you, hit his thank you button. If you find this thread helpful as well, hit my thank you button.
Instructions on flashing are not provided. If you need these files it means you know how to flash your device, have flashed a custom ROM previously, and require this to return to a stock state.
As usual FLASH AT YOUR OWN RISK, don't blame ANYONE here for ANYTHING.
PLEASE NOTE: The FROYO stock ROM is currently unavailable, will be back up soon.
Downloads can be found here
Further more, I would like to thank kpetrie77 for setting up a wiki on the Samsung Galaxy Tab, the wiki is full of great links for all things Galaxy Tab. You can find it here, and if you have anything to contribute please do so as it helps everyone here at XDA.

Thanks to theREDlegion for putting this together. Happy to try to help others both on P1000 series.
The FROYO version was rooted with SuperOneClick 2.2 - if you use this utility and unroot it will remove the superuser.apk and after a reboot, adb won't connect as root. Before you do that reboot, you'll want to remove the busybox binaries /system/xbin to reach as 'near a stock state as possible'.
The GINGERBREAD version was snagged from Kies during the update process. It seems the Check Fus Donwloader doesn't know about Rogers (but it knows about Bell?!).
Real life gets in the way for hacking, but I'm motivated to make the Tab (mine included) as useful as possible beyond stock.

Thank you. This will come in handy.

SaHiLzZ said:
Thank you. This will come in handy.
Click to expand...
Click to collapse
Glad to help.
If possible can you post your results. It might be useful info for others.
Thanks,
RED

user8525 said:
Was hoping you could answer this question. I am currently running stock froyo on my Rogers Tab. If i update to Gingerbread is there any negatives with me wanting to upgrade in the future to other builds. Does it lock the bootloader? or is the bootloader already locked?
Thanks.
Click to expand...
Click to collapse
Sorry to respond almost a month later but I have not been checking my PM's regularly for the past little bit with so many other things on the go. It is better to post these kinds of questions in the thread itself, as this would help other members with similar questions. That is why I created the thread, and this is a good question to ask and answer in the thread. It is a REALLY GOOD QUESTION, that I'm sure others would be interested in and therefore I will post it in the thread. If you would like me to remove your username please contact me.
The Samsung Gingerbread release is not locked, it is signed. You CAN flash custom kernels and ROMs, DO NOT use the PATCH tool that Chainfire has provided, if that is why you ask, see that thread. That patch is an amazing tool provided by Chainfire, there is nothing wrong with the patch it just does not apply to us. If you use it, the tool will ask you to patch, DO NOT PATCH. You will screw things up with it and have to re-flash, re-stock and re-do everything just to fix it.
If you are uncertain if you should flash anything, than DON'T FLASH ANYTHING. Read, read than read some more before continuing any further.
These stock ROM's are not SamFirmware downloads, they are STOCK Rogers firmware from the device and from the update from KIES.

theREDlegion said:
Glad to help.
If possible can you post your results. It might be useful info for others.
Thanks,
RED
Click to expand...
Click to collapse
I haven't had the opportunity to restore a tab yet. One of these days someone will lend me one for testing and I will try test these files.
Looking at the files, these will need to be restored via heimdall correct?
Also looking for the Bell Froyo rom. Any suggestions?

SaHiLzZ said:
...heimdall correct?
Also looking for the Bell Froyo rom. Any suggestions?
Click to expand...
Click to collapse
Heimdall is correct.
Have not come across a stock BELL Froyo ROM (haven't even looked really). Will see what I come across and post back.

How to flash P1000R to stock Gingerbread
I wrote up how to take the Gingerbread firmware in the OP and flash it to your device.
http://lowtek.ca/roo/2012/restore-rogers-galaxy-p1000r-to-stock/
It's short and sweet. Ubuntu (Linux) as my desktop, heimdall as the flashing tool. Key is really mapping the files in the firmware to the heimdall partition names and getting through the boot sequence (flash, recovery and allow update, reboot).

Rogers CWM flashable modem UXJJ6
Following instructions found here http://androidforums.com/galaxy-s2-...t/540640-make-my-own-cwm-flashable-modem.html I created a CWM flashable modem of the Froyo Rogers ROM.
Why? Well, this modem didn't appear to be available in this form - so here it is as an attachment.

All Things Boost Galaxy S III

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.

Going from CM11 To Stock? (Model: Sghi747)

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:

Stuck on Samsung boot screen

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.

[Q&A] [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.

[Q&A] [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.
Q&A for [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.5/8.4 ]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT][RECOVERY] [ALL IN ONE] Cf-Autoroot-twrp-T800-T805-T-700-T705 [Tab S 10.5/8.4 ]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Can this method be used Straight out of the box?
Hey guys, just wanna make sure that this method can be used straight out of the box? only ever rooted LGs so just want to check that I'm doing the right thing here?
Thanks

As long as you have the Samsung usb drivers installed on your pc you're good.

ashyx said:
As long as you have the Samsung usb drivers installed on your pc you're good.
Click to expand...
Click to collapse
Great stuff Thanks, got a bit confused with the CFAutoRoot page saying I needed to unlock the bootloader first, then I stumbled on your Method.
Thanks

AgentCP said:
Great stuff Thanks, got a bit confused with the CFAutoRoot page saying I needed to unlock the bootloader first, then I stumbled on your Method.
Thanks
Click to expand...
Click to collapse
Only Verizon and AT&T models have locked bootloaders. If you don't have one of these you should be fine.

Why root wifi only device?
I have rooted a couple of devices. I get it's purpose of unlocking hotspot, modifying cpu clock, adblocking, etc. I have the Tab S 10.5 and I am trying to find the benefit to rooting this device. Looks simple enough. But What will I gain? I think I have already answered my question though, maybe. I am rooting my note 3 so I can use that for a hotspot for this. But it seems the only real benefit is adblocking? Am I missing something. It has been a while since I have done this so maybe I have...
Anyways, thanks for the input.

Bdozier said:
I have rooted a couple of devices. I get it's purpose of unlocking hotspot, modifying cpu clock, adblocking, etc. I have the Tab S 10.5 and I am trying to find the benefit to rooting this device. Looks simple enough. But What will I gain? I think I have already answered my question though, maybe. I am rooting my note 3 so I can use that for a hotspot for this. But it seems the only real benefit is adblocking? Am manufacturers I missing something. It has been a while since I have done this so maybe I have...
Anyways, thanks for the input.
Click to expand...
Click to collapse
The way to look at is that rooting gives YOU control over your device not the manufacturer. Think of it as like administration rights on a PC.
Would you like it if pc manufacturers told you what you could and couldn't install on your pc?
Rooting allows you to install custom recoveries so you can back up your device, fix problems, try new custom or stock software, install root only apps such as titanium backup. You can modify system files and add back functionality that the manufacturer has decided to remove or disable. Add new functionality, maybe something that is found on another device. Speed up your device by overclocking to make it run smoother.
Change how things look and install apps such as xposed which reveals a ton of hidden features allowing you to customize your device to your liking.
Once you realise what root can do you'll never want a another device that isn't.

Confused
Hi, I have downloaded the file for the T800. However, when I unzip it there are only two files :cache.img & recovery.img. Am I missing something? Please excuse my ignorance, newbie!!

Blythlad said:
Hi, I have downloaded the file for the T800. However, when I unzip it there are only two files :cache.img & recovery.img. Am I missing something? Please excuse my ignorance, newbie!!
Click to expand...
Click to collapse
Yep you certainly are a nooby as you made the rookie mistake of not actually reading the first post.
Go back to the original thread and read the bit under the smiley face.

ashyx said:
Yep you certainly are a nooby as you made the rookie mistake of not actually reading the first post.
Go back to the original thread and read the bit under the smiley face.
Click to expand...
Click to collapse
Sorry, I read that bit,downloaded odin as well, however, I recall reading something somewhere about needing a .tar file? Maybe some full instructions would be nice for us new to rooting a device. Thanks for the reply

Blythlad said:
Sorry, I read that bit,downloaded odin as well, however, I recall reading something somewhere about needing a .tar file? Maybe some full instructions would be nice for us new to rooting a device. Thanks for the reply
Click to expand...
Click to collapse
The tar file is the file you have downloaded.
Just leave it as it is and flash with Odin.
I shouldn't have to provide step by step instructions, this is what XDA search and Google is for. This info is everywhere.
Basically:
Install Samsung usb drivers.
Disable Samsung kies if installed.
Boot your device into download mode - Hold POWER + VOL DOWN + HOME.
Run ODIN , connect USB cable, look for 'added' message.
Load the tar file into the AP slot, click START.
Wait for flash to complete, device will reboot and root.
Enjoy your rooted device with custom recovery.

New build posted: http://forum.xda-developers.com/galaxy-tab-s/development/root-cf-autoroot-twrp-t800-t3079488

I tried on my t800 running latest BRI firmware and worked fine. Thanks a lot.

Cannot complete root on T-800 (Lollipop 5.0.2)
I've tried rooting twice on my T-800 running 5.0.2. In both cases ODIN says passed. However, I do not see either supersu or TWRP. When I ran root validator I got the following:
Root Unavailable
su/id/echo did not execute
I had installed the supersu app manually, but even that says the binaries are not installed.
However, Knox says it has been tripped. (using Knox Status app). So looks like I have the worst of both worlds here (well, other than bricking). Is there anything I can do different? Thanks,

chanukya said:
I've tried rooting twice on my T-800 running 5.0.2. In both cases ODIN says passed. However, I do not see either supersu or TWRP. When I ran root validator I got the following:
Root Unavailable
su/id/echo did not execute
I had installed the supersu app manually, but even that says the binaries are not installed.
However, Knox says it has been tripped. (using Knox Status app). So looks like I have the worst of both worlds here (well, other than bricking). Is there anything I can do different? Thanks,
Click to expand...
Click to collapse
Have you actually read the original thread? The answer is in that thread.
http://forum.xda-developers.com/showpost.php?p=60324046&postcount=33

Works now!
Thank you for the reply. I had read that, but did not understand how it applied to me, root works now.
For anyone else in my shoes, here's what I did:
1) unchecked auto reboot
2) Once I got the Pass! message in Odin rebooted using Power+VDOWN+HOME
3) Kept pressing Power+VUP+HOME till it rebooted, at which point it says installing TWRP
4) Kept pressing Power+VUP+Home till it restarted again, and this time it goes to TWRP
5) In TWRP, I said reboot to recovery, it then asked to install SuperSU and root.

chanukya said:
Thank you for the reply. I had read that, but did not understand how it applied to me, root works now.
For anyone else in my shoes, here's what I did:
1) unchecked auto reboot
2) Once I got the Pass! message in Odin rebooted using Power+VDOWN+HOME
3) Kept pressing Power+VUP+HOME till it rebooted, at which point it says installing TWRP
4) Kept pressing Power+VUP+Home till it restarted again, and this time it goes to TWRP
5) In TWRP, I said reboot to recovery, it then asked to install SuperSU and root.
Click to expand...
Click to collapse
That did it! Thanks bro, made my night!
Sent from my Galaxy S5

chanukya said:
Thank you for the reply. I had read that, but did not understand how it applied to me, root works now.
For anyone else in my shoes, here's what I did:
1) unchecked auto reboot
2) Once I got the Pass! message in Odin rebooted using Power+VDOWN+HOME
3) Kept pressing Power+VUP+HOME till it rebooted, at which point it says installing TWRP
4) Kept pressing Power+VUP+Home till it restarted again, and this time it goes to TWRP
5) In TWRP, I said reboot to recovery, it then asked to install SuperSU and root.
Click to expand...
Click to collapse
Did you see the red android after rebooting?
Supersu should have already been installed before booting into twrp.

chanukya said:
I've tried rooting twice on my T-800 running 5.0.2. In both cases ODIN says passed. However, I do not see either supersu or TWRP. When I ran root validator I got the following:
Root Unavailable
su/id/echo did not execute
I had installed the supersu app manually, but even that says the binaries are not installed.
However, Knox says it has been tripped. (using Knox Status app). So looks like I have the worst of both worlds here (well, other than bricking). Is there anything I can do different? Thanks,
Click to expand...
Click to collapse
I have an apology to make. Your troubles seemed to have been due to the SuperSu script not running because it had become corrupt. I realised something was wrong when you said you had to install SuperSu with TWRP.
All fixed now.
Sent from my SM-T805 using XDA Free mobile app

No clue... any help?
Sorry for the questions....
I have SM-T805 with 4.4.2 and build KOT49H.T805XXU1ANH1...
1 - Can i root without tripping knox? (i've done it on GS3 and GS4, no issues on knox, counter remains 0x0);
2 - The cf.auto root files are locked at specific builds? Or can i use the sm-t805 on chainfire page?;
3 - Can i update to lollipop or any other official firmware? And without tripping knox?
Thanks, in advance.
---------- Post added at 08:23 PM ---------- Previous post was at 08:18 PM ----------
Sorry for the questions....
I have SM-T805 with 4.4.2 and build KOT49H.T805XXU1ANH1...
1 - Can i root without tripping knox? (i've done it on GS3 and GS4, no issues on knox, counter remains 0x0);
2 - The cf.auto root files are locked at specific builds? Or can i use the sm-t805 on chainfire page?;
3 - Can i update to lollipop or any other official firmware? And without tripping knox?
Thanks, in advance.