Related
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.
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
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.
I'm sure this has been answered before, but I haven't been able to find a straight answer.
I want to put Cyanogen 11 on my d2att S3. I downloaded the nightly (cm-11-20140217-NIGHTLY-d2att.zip) and when I try to flash it, I get this:
Code:
assert failed getprop ("ro.bootloader) = = "I747UCUEMJ2"
getprop ("ro.bootloader) = = "I747UCUEMJB"
getprop ("ro.bootloader) = = "I747MVLDMF1"
getprop ("ro.bootloader) = = "I747MVLUEMK5"
getprop ("ro.bootloader) = = "I747MUMUEMK3"
E: Error executing updater binary in zip "/sdcard/roms/cm-11-20140217-NIGHTLY-d2att.zip"
Error flashing zip "/sdcard/roms/cm-11-20140217-NIGHTLY-d2att.zip"
From what I searched it said to match the "baseband" under "About Phone" to one of the bootloader ID's. My baseband (shown on "About Phone" screen) is I747UCUEMJB, yet it still fails. I updated to the newer baseband via a modem update package (modem_CWM_I747UCUEMJB.zip), but I'm thinking that only updated the modem firmware, and not the bootloader. How do I update the bootloader to match, or does that not need to happen?
Also, I am running PhilZ Touch 6.17.8 w/ CWM 6.0.4.7 Advanced Edition. I DID do a FULL wipe before trying to install the nightly.
Any help would be appreciated.
Baseband is not the same thing as bootloader. You need to match the bootloader.
audit13 said:
Baseband is not the same thing as bootloader. You need to match the bootloader.
Click to expand...
Click to collapse
Yeah that's kinda what I was thinking... The big question now is how do I upgrade the bootloader? I can't seem to figure that out.
Ya man I'm having the same kind of issues, I flashed beanstalk 4.4.1 and running it with no problems but I'm mpt angle to flash anything and now I do have the newest cwm and boot loader......I'm lost lol. I know I shouldn't even be picky cause beanstalk is a great ROM with great features but ever since I learned to mod and flash I'm a flashaholic and love testing for the perfect one....and I guess I'm feeling a little cheated right now not being able to do that lol......I came from a crappy zte avid rooted with an unofficial xm 10 that some guys built from stock and did a great job at by the way lol but it was so limited then j got my gs3 and I was like know its on!!!.......except.....now its not on......lol
cmivxx said:
Yeah that's kinda what I was thinking... The big question now is how do I upgrade the bootloader? I can't seem to figure that out.
Click to expand...
Click to collapse
i never had this problems, just followed instructions, clean install and i was on MJB with CM11
just flash this and yu're good to go http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23
it might break your phone, it might work or not work, am not a dev or do i like messing with bootloaders/modem
happy flashing, yu re gonna be fine
The simple solution may be to flash the MJB bootloader. At the moment you have the MJ2 bootloader and the error shows that the updater-script is looking for MJB. The MJB bootloader does have some drawbacks, they can be found in many ROM threads and in the general forum.
Another option could be editing the updater-script. I've seen mentions of it in several threads. Usually they suggest deleting the first few lines. I guess you could change the MJB line to MJ2. Since I have not done any of this I suggest reading about it instead of me giving directions from memory.
winosxbuntu said:
i never had this problems, just followed instructions, clean install and i was on MJB with CM11
just flash this and yu're good to go http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23
it might break your phone, it might work or not work, am not a dev or do i like messing with bootloaders/modem
happy flashing, yu re gonna be fine
Click to expand...
Click to collapse
I know you said you aren't a dev and everything and I understand you might not have a clue and I might do the wrong thing and I totally take responsibility, but have you seenaanything similar to my problem? I have the updated boot loader and my cwm is good......I removed Knox with the Knox remover when I rooted and was able to flash beanstalk but after flashing beanstalk I haven't been able to wipe and flash anything else. Everything fails and I have to restore my nandroid of be an stock......the only things I have not tried was switching to twrp and or flashing back my 4.3 stock but rooted and without Knox and flash from there
cmivxx said:
Yeah that's kinda what I was thinking... The big question now is how do I upgrade the bootloader? I can't seem to figure that out.
Click to expand...
Click to collapse
swoopt25 said:
I know you said you aren't a dev and everything and I understand you might not have a clue and I might do the wrong thing and I totally take responsibility, but have you seenaanything similar to my problem? I have the updated boot loader and my cwm is good......I removed Knox with the Knox remover when I rooted and was able to flash beanstalk but after flashing beanstalk I haven't been able to wipe and flash anything else. Everything fails and I have to restore my nandroid of be an stock......the only things I have not tried was switching to twrp and or flashing back my 4.3 stock but rooted and without Knox and flash from there
Click to expand...
Click to collapse
yea, that will work, just try any of this stock touchwiz roms on this link http://forum.xda-developers.com/galaxy-s3-att/development
follow the instructions to restore/refresh your bootloader to MJB when yu re installing the rom and am sure yu'ill be fine
just dont over do it or rush it and end up with a hard brick..........bootloaders are not something to mess with
4.3 has be been a Pain In The Butt for everyone and with hard bricks, i have been scared like hell &am more cautioned to stay on one rom until am tired or a new version is released.
winosxbuntu said:
yea, that will work, just try any of this stock touchwiz roms on this link http://forum.xda-developers.com/galaxy-s3-att/development
follow the instructions to restore/refresh your bootloader to MJB when yu re installing the rom and am sure yu'ill be fine
just dont over do it or rush it and end up with a hard brick..........bootloaders are not something to mess with
4.3 has be been a Pain In The Butt for everyone and with hard bricks, i have been scared like hell &am more cautioned to stay on one rom until am tired or a new version is released.
Click to expand...
Click to collapse
Thanks brother for the quick reply much appreciated.......I love this community lol.......I'm gonna take it for a test drive.....and your absolutely right, that's my problem because I came from such a limited phone and limited root/ROM capabilities and had wanted the s3 for so long because there were so many different options and now that I ha e it because of 4.3's bullcrap lol I got to be extra careful and take my time.
swoopt25 said:
Thanks brother for the quick reply much appreciated.......I love this community lol.......I'm gonna take it for a test drive.....and your absolutely right, that's my problem because I came from such a limited phone and limited root/ROM capabilities and had wanted the s3 for so long because there were so many different options and now that I ha e it because of 4.3's bullcrap lol I got to be extra careful and take my time.
Click to expand...
Click to collapse
just here to help and make this place awesome :laugh:
winosxbuntu said:
just here to help and make this place awesome :laugh:
Click to expand...
Click to collapse
Well update: the idea I saidbi hadn't tried with a little push from asking your advice instead of flashing twrp I reflashed my stock (already rooted Knox removed) touchwiz 4.3 that came with the phone and wala! I can flash again.......thanks again bro seriously.......I am still curious as to why I can't do it after I wipe beanstalk and flash from there, I have to flash to stock, then wipe everything the flash what I want....all said and done though I played around a little and I actually went right back to beanstalk I love the smoothness of it.....maybe soon after a bit more reading I can jump into some custom kernals and play around.
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: