Related
I rooted my phone yesterday using the toolkit from the development forums. I created a backup of my stock ROM before I flashed anything new but apparently I messed that up b.c trying to restore that, the toolkit told me I have no restore files. Anyway I flashed the unofficial cm10 build and I am having some radio issues, so I wanted to go back to stock until a more official build comes out. I have tried doing that through the toolkit a few times but it continues to fail.
Looking around online I found the stock ROM from Google and dl'd it (mysid-imm76k-factory-98d21321.tar is the file) I am pretty noobish when it comes to flashing stuff and i have never seen a .tar but I found that Odin can flash .tar. so my plan was to get the odin app flash that file and hope I did everything okay.
A couple questions: is this going to work okay? Do I need to flash kernels or radios or anything else or is this a complete return to stock? Will this keep me rooted and unlocked?
you dont need ODIN.
use this:
http://forum.xda-developers.com/showthread.php?t=1626895
Zepius said:
you dont need ODIN.
use this:
http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thank you. Don't know why I couldn't find that.
Any chance you could explain what odin is/.tar files are? And how they are different?
unrefine said:
Thank you. Don't know why I couldn't find that.
Any chance you could explain what odin is/.tar files are? And how they are different?
Click to expand...
Click to collapse
ODIN is a firmware restore program for all samsung phones.
here's a decent webpage on what ODIN is/does
http://forum.jakar.co/android-hack/1341254634/
Guys...Im not a total newbie but I have a couple of question. I have my SM-N900T rooted with N900TTMBBMI7..used odin, CF-Root etc etc and its working great...so I have dabbled enough in this so I am a bit dangerous. I have CWM recovery and Titanium backup and can/do make backups before I add any apps, etc.
I would like to upgrade to N900TUVUDNF1 and I have seen that in this thread http://forum.xda-developers.com/showthread.php?t=2761451 there is a deodexed, rooted version by Jovy23 so that is great...I do have a couple of questions I want to be clear on before I start this process :
1) I see that people talk about needing a specific bootloader...do I? Can anyone clarify that for me?
2) I have lots of apps installed on my N900TTMBBMI7 now as you can imagine. Would the process be to install N900TUVUDNF1 with odin as per the instructions and THEN, install Titanium backup and restore my apps? I dont want to spend a lot of time getting the phone back to what I have now if I can avoid it.
3) Will the N900TUVUDNF1 install wipe out my CWM recovery ? Do I need to re-install it after flashing N900TUVUDNF1 ?
4) If something goes really wrong, the process to revert would be to install CWM recovery and restore my N900TTMBBMI7 backup?
Anything else you guys would like to advise me of will be greatly appreciated...
thanks!!
re: NF1 firmware
calderonr said:
Guys...Im not a total newbie but I have a couple of question. I have my SM-N900T rooted with N900TTMBBMI7..used odin, CF-Root etc etc and its working great...so I have dabbled enough in this so I am a bit dangerous. I have CWM recovery and Titanium backup and can/do make backups before I add any apps, etc.
I would like to upgrade to N900TUVUDNF1 and I have seen that in this thread http://forum.xda-developers.com/showthread.php?t=2761451 there is a deodexed, rooted version by Jovy23 so that is great...I do have a couple of questions I want to be clear on before I start this process :
1) I see that people talk about needing a specific bootloader...do I? Can anyone clarify that for me?
2) I have lots of apps installed on my N900TTMBBMI7 now as you can imagine. Would the process be to install N900TUVUDNF1 with odin as per the instructions and THEN, install Titanium backup and restore my apps? I dont want to spend a lot of time getting the phone back to what I have now if I can avoid it.
3) Will the N900TUVUDNF1 install wipe out my CWM recovery ? Do I need to re-install it after flashing N900TUVUDNF1 ?
4) If something goes really wrong, the process to revert would be to install CWM recovery and restore my N900TTMBBMI7 backup?
Anything else you guys would like to advise me of will be greatly appreciated...
thanks!!
Click to expand...
Click to collapse
#1: The NF1 bootloader is part of the official Samsung N900T NF1 Kitkat firmware.
Here is the direct download link for the firmware:
chrome://mega/contenthttp:
https://mega.co.nz/#!ioglFaQD!IzrjOKfoQXnfzTVjItUnjVvqzVSoG4s0wkKLTvit9BY
#2: You will need to restore your apps with titanium backup after odin
flashing the official stock NF1 firmware.
#3: Odin flashing the NF1 firmware will wipe cwm recovery so you will need
to odin flash TWRP recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
#4: Before flashing TWRP you will need to odin flash cf-autoroot which
can be found here:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
#5: Once you flash NF1 firmware you cannot revert back to MI7 firmware
it will either bootloop or get stuck on boot screen if you try doing it.
In other words you cannot downgrade the firmware once it's updated to NF1.
Good luck!
Misterjunky said:
#1: The NF1 bootloader is part of the official Samsung N900T NF1 Kitkat firmware.
Here is the direct download link for the firmware:
chrome://mega/contenthttp:
https://mega.co.nz/#!ioglFaQD!IzrjOKfoQXnfzTVjItUnjVvqzVSoG4s0wkKLTvit9BY
#2: You will need to restore your apps with titanium backup after odin
flashing the official stock NF1 firmware.
#3: Odin flashing the NF1 firmware will wipe cwm recovery so you will need
to odin flash TWRP recovery which can be found here:
https://dl.dropboxusercontent.com/u/45687485/openrecovery-twrp-2.7.2.0-hltetmo-4.4.img.tar
#4: Before flashing TWRP you will need to odin flash cf-autoroot which
can be found here:
https://dl.dropboxusercontent.com/u/45687485/CF-Auto-Root-hltetmo-hltetmo-smn900t.tar.md5
#5: Once you flash NF1 firmware you cannot revert back to MI7 firmware
it will either bootloop or get stuck on boot screen if you try doing it.
In other words you cannot downgrade the firmware once it's updated to NF1.
Good luck!
Click to expand...
Click to collapse
Wow, thanks for the quick reply..I am glad you answered because I was totally under the impression that reverting back was indeed possible..I would have been in a wold of hurt if something went wrong and I could not revert since I use this device for work as well. So this of course begs a few more followup questions
1) The firmware at https://mega.co.nz/#!ioglFaQD!IzrjOK...4s0wkKLTvit9BY I assume is NOT rooted and therefore I would have to root with CF-Root etc...correct?
2) What is exactly the bootloader in this context? You are not refering to TWRP/CWM I assume? Is it the built in code to get the startup going? I am familiar with Linux bootloader like LILO and GRUB...is it the same concept?
3) Understood on restoring apps with Titanium backup...you refer only to the official firmware. Are you suggesting that I should not use the stock rooted NF1 I found?
4) Understood that flashing NF1 will wipe out CWM. You state to odin flash TWRP. Does that mean I should NOT use CWM and switch to TWRP? I am more familiar with CWM and I would like to continue using that one if possible.
5) Lastly and more importantly, why will reverting back to MI7 will cause the bootloop or stuck on boot screen? Any solution to that at all?
Again, thanks for your suggestions and quick reply!!
calderonr said:
Wow, thanks for the quick reply..I am glad you answered because I was totally under the impression that reverting back was indeed possible..I would have been in a wold of hurt if something went wrong and I could not revert since I use this device for work as well. So this of course begs a few more followup questions
1) The firmware at https://mega.co.nz/#!ioglFaQD!IzrjOK...4s0wkKLTvit9BY I assume is NOT rooted and therefore I would have to root with CF-Root etc...correct?
2) What is exactly the bootloader in this context? You are not refering to TWRP/CWM I assume? Is it the built in code to get the startup going? I am familiar with Linux bootloader like LILO and GRUB...is it the same concept?
3) Understood on restoring apps with Titanium backup...you refer only to the official firmware. Are you suggesting that I should not use the stock rooted NF1 I found?
4) Understood that flashing NF1 will wipe out CWM. You state to odin flash TWRP. Does that mean I should NOT use CWM and switch to TWRP? I am more familiar with CWM and I would like to continue using that one if possible.
5) Lastly and more importantly, why will reverting back to MI7 will cause the bootloop or stuck on boot screen? Any solution to that at all?
Again, thanks for your suggestions and quick reply!!
Click to expand...
Click to collapse
Be careful who you listen to on xda.
If your knox warranty flag is 0x0 DO NOT follow those instructions if you want it to stay that way.
To check, boot into download mode (reboot with volume+power+voldown.
If it's 0x0 and you want to keep it that way, you'll want to know that if you upgrade, flashing a custom recovery WILL ALWAYS trip knox once your bootloader is on kitkat.
The caveat is that if you want kitcat, you have to upgrade your bootloaders for things to work properly.
Now, with all that out of the way...
I would recommend going up to NF4 (bypassing NF1) as it is the latest.
I have a link in my sig with all the files for NF4 which also contains the upgrade method that doesn't trip knox.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
---------- Post added at 11:27 AM ---------- Previous post was at 11:16 AM ----------
In case you can't see my sig due to being in xda app or tapatalk:
NF4 files and instructions: http://forum.xda-developers.com/showthread.php?t=2834398
Or if you're dead set on NF1, there's a link to that thread at the top of the NF4 post. The instructions in post 2 of the nf4 thread are valid for nf1 add well.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Be careful who you listen to on xda.
If your knox warranty flag is 0x0 DO NOT follow those instructions if you want it to stay that way.
To check, boot into download mode (reboot with volume+power+voldown.
If it's 0x0 and you want to keep it that way, you'll want to know that if you upgrade, flashing a custom recovery WILL ALWAYS trip knox once your bootloader is on kitkat.
The caveat is that if you want kitcat, you have to upgrade your bootloaders for things to work properly.
Now, with all that out of the way...
I would recommend going up to NF4 (bypassing NF1) as it is the latest.
I have a link in my sig with all the files for NF4 which also contains the upgrade method that doesn't trip knox.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Toastido...Thanks for the reply...I have already tripped the warranty counter so lets say that at this point I am OK with that
So a few questions for you :
1) I am OK going to NF4 and I assume that the files/links you pointed me to below will still work on a tripped knox flag? Correct?
2) Does the same apply that if I go to NF4 there is no way to revert back to MI7?
3) Does your NF4 upgrade link/instructions contain the bootloader needed ? I assume so but want to make sure just in case I need anything else other than what you pointed me to. I am asking this because you stated "if you want kitcat, you have to upgrade your bootloaders for things to work properly. "
4) Can I continue to use CWM or do I have to switch to TWRP?
5) What about rooting? Is your firmware rooted or do I need to do it myself? If so, what do you recommend for rooting?
Thanks!!!
calderonr said:
Toastido...Thanks for the reply...I have already tripped the warranty counter so lets say that at this point I am OK with that
So a few questions for you :
1) I am OK going to NF1 and I assume that the files/links you pointed me to below will still work on a tripped knox flag? Correct?
2) Does the same apply that if I go to NF1 there is no way to revert back to MI7?
3) Does your NF1 upgrade link/instructions contain the bootloader needed ? I assume so but want to make sure just in case I need anything else other than what you pointed me to. I am asking this because you stated "if you want kitcat, you have to upgrade your bootloaders for things to work properly. "
4) Can I continue to use CWM or do I have to switch to TWRP?
Thanks!!!
Click to expand...
Click to collapse
Hey!
1) yes. I'd recommend just flashing the full package in desktop odin in that case. Power of your device completely for 10 to 30 seconds then boot directly to download mode.
2) yes. Once you go up from jb to kk you cannot go back. This is due to bootloader update efuses.
3) yes they do.
4) you can use cwm if you want, just make sure to get the correct one. Usually they are tagged kk or 4.4. Using jb versions will no longer work.
I assume you meant nf4, but the same applies to either.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Hey!
1) yes. I'd recommend just flashing the full package in desktop odin in that case. Power of your device completely for 10 to 30 seconds then boot directly to download mode.
2) yes. Once you go up from jb to kk you cannot go back. This is due to bootloader update efuses.
3) yes they do.
4) you can use cwm if you want, just make sure to get the correct one. Usually they are tagged kk or 4.4. Using jb versions will no longer work.
I assume you meant nf4, but the same applies to either.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Yeap...I meant NF4 and I sent in an edit but you beat me to it..ok...I will give this a try...I did ask one more question on the edit that I am not sure where it went...
5) About rooting...if I use odin to flash the full package as I have done before (selecting PDA), how would you recommend I root the NF4 since I assume the stock firmware is NOT rooted. Do you recomend CF-Root?
thanks aod sorry to pestering I want to make sure I do this right the first time!!
calderonr said:
Yeap...I meant NF4 and I sent in an edit but you beat me to it..ok...I will give this a try...I did ask one more question on the edit that I am not sure where it went...
5) About rooting...if I use odin to flash the full package as I have done before (selecting PDA), how would you recommend I root the NF4 since I assume the stock firmware is NOT rooted. Do you recomend CF-Root?
thanks aod sorry to pestering I want to make sure I do this right the first time!!
Click to expand...
Click to collapse
Np. As for number 5, yes, CF-Auto-Root is the best (maybe the only?) method for fw beyond ne6. If you do this and find supersu missing, a simple install from the play store afterwards will fix you right up.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
toastido said:
Np. As for number 5, yes, CF-Auto-Root is the best (maybe the only?) method for fw beyond ne6. If you do this and find supersu missing, a simple install from the play store afterwards will fix you right up.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Click to expand...
Click to collapse
Toastido :
Not trying to be dense here but help me understand this. Its re. the inability to go back to MI7 from NF4. You say it has to do with the bootloader, BUT, if I take a CWM backup BEFORE I flash NF4, would not that backup contain the MI7 bootloader in it, so when/if I restore the backup, would not that also restore the MI7 bootloader and the device would not even notice it had flashed NF4 before? Granted I would have to re-clash the JB compatible CWM before I restored, but would that not work? If not, can you explain why?
Thanks!!
calderonr said:
Toastido :
Not trying to be dense here but help me understand this. Its re. the inability to go back to MI7 from NF4. You say it has to do with the bootloader, BUT, if I take a CWM backup BEFORE I flash NF4, would not that backup contain the MI7 bootloader in it, so when/if I restore the backup, would not that also restore the MI7 bootloader and the device would not even notice it had flashed NF4 before? Granted I would have to re-clash the JB compatible CWM before I restored, but would that not work? If not, can you explain why?
Thanks!!
Click to expand...
Click to collapse
No it would not work. The reason, as stated in a previous post, is due to eFused bootloaders. Once the efuse is tripped, it cannot be reset, and the bootloader will fail if it's value is lower than the fused value. Otherwise just flashing the bootloader backwards would work. If you go the odin route you will be protected by odin mode. If you try via recovery of a nandroid that contains the bootloader, it'll either just not work, or (worse) brick your device.
The fuses are tripped in a sequential order. 0,1,2,3 etc. JB BL can only operate on fused value of 1 or lower. KK BL can only install and function (depending on current version) at 3 or lower.
NB4 will fuse to 2. NE6 through NF4 I believe will fuse to 3, thus preventing the JB BL from functioning.
Hope that helps.
Sent from my leanKernel 3.4 powered stock 4.4.2 (NF4) SM-N900T
Let me know how it goes. I have to update mine to.. I'm on NB4 with no issues but I should update anyways.
Sent from my SM-N900T using XDA Free mobile app
The development for the AT&T I747 has been discontinued by the developer. Thank you for your support.
WARNING: YOU COULD BRICK YOUR PHONE
UCUFNJ1 4.4.2 incremental update contains firmware.... bootloaders and modem baseband.
MUST BE ON UCUFNE4 FIRMWARE TO CONTINUE!!! Guide can be found here. http://forum.xda-developers.com/gal...are-update-t2808654/post53984772#post53984772
This is the perfect time to use this update to return your S3 to stock for resale or whatever. Download and save these files for when you are ready to return your phone to stock.
*This is a rooted NE4 system.img, stock recovery.img and boot.img. The install script will format system and factory data reset. /media is safe.*
1. Flash restore zip in a custom recovery. CWM, TWRP, Philz. https://www.androidfilehost.com/?fid=95784891001611561
2. Boot your phone and go through setup.
3. Use triangle away and clear your counter. http://forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114
4. *Optional* If you want a clean un-rooted phone for the update do this now! , Go into SuperSu >settings>full unroot.
5. Reboot your phone.
6. Search for the OTA in the about settings, download and let the phone update.
Or download this and place in the root of your phones internal storage. Reboot into recovery and select the update from update.zip https://www.androidfilehost.com/?fid=95784891001611091
Advanced users.
The original OTA cfg file. https://www.androidfilehost.com/?fid=95784891001611092
.cfg file goes in root/cache/fota
Rename the .cfg extension to .zip and you can rename it update.zip yourself or you can actually flash it in a custom recovery once renamed. if you choose not to use the stock recovery to update.
*You will loose root during the update* But the bootloader is not locked so you can still Odin your favorite recovery and flash SuperSU.
TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.8.1.0-d2att.tar
SuperSU http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip?retrieve_file=1
Once you flash your favorite recovery via Odin, you need to be ready to hold the Volume Up, Power and Home button combo when Odin reboots your phone. If you don't catch it, once the OS boots it will replace recovery with the stock version. Once SuperSU is installed your recovery will stick.
Flashable Rooted NJ1 system.img and boot.img
MD5: 6df80e42df56ddf90512f4162e645cb3
Download: https://www.androidfilehost.com/?fid=95784891001613266
Flashable NJ1 Bootloaders and modem. *Must be on NE4 bootloaders prior to flashing.*
Download: https://www.androidfilehost.com/?fid=95832962473396872
Thanks enewman for writing this up.
Doing Vice Versa Method?
Just to be clear, what if my galaxy s3 is on UCUFNJ1 and I want to go back to UCUFNE4, I can still ODIN the custom recovery and flash SuperSU?
Galaxy S3 I747
Baseband: I747UCUFNJ1
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
mattsternc said:
For the advanced users, should we be able to install the update without any issues? I saw in another thread that someone had installed but now their phone will not boot past the Samsung logo to anything other than a black screen.
Also, do we know what this update contains yet? Other than new bootloaders, removal of root, etc.
Click to expand...
Click to collapse
You know if your not wanting to return your phone to stock I really wouldn't mess with this update. Far as the user who couldn't boot... Idk I wasn't there to watch them update. This whole mess with the S3 is exhausting. We haven't got a real Odin release so I'm woking with what I can extract from my phone after updating. The system.img in ne4 zip is 100% stock except for root. So I know the update worked because I did it. Also not sure what was updated either... The kernel yes... Firmware yes, all the system apps get patched so without decompiling ne4 and nj1 apps and comparing them afraid I have no idea what the update fixes or improves.
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
OKAstro said:
Thanks for all you do for us S3 owners, enewman17.
If we upgrade to the new NJ1 firmware, and then flash your latest SRX Rom, I assume we cannot then use your "restore.zip" to once again go back to NE4 stock since we would be on NJ1 bootloader? If so, is there a way to go back to NJ1 stock if we later want to sell our phone?
Click to expand...
Click to collapse
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
enewman17 said:
I have the nj1 system dump, I'll get it uploaded so anyone who updates can restore back to stock.
Click to expand...
Click to collapse
Thanks again my man.
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Ark42 said:
Towelroot no longer works after the NJ1 update. Can the CF-AutoRoot still be used? The only version at http://autoroot.chainfire.eu/ says it's for 4.0.4.
Click to expand...
Click to collapse
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Agreed! I'm the same boat as you.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Ark42 said:
Yeah, I saw that, but I never had a custom recovery before, that I know of at least, and I suspect a lot of other people finding this thread in the coming days are going to be in the same boat as me. They just want SuperSU so their favorite 1 or 2 apps that require SU can continue to work.
Has anybody tried CF-AutoRoot yet on the NJ1 4.4.2?
Click to expand...
Click to collapse
Tell you what, when I get home from work I will try cfauto root and see if it works.
enewman17 said:
Not sure if it still works but read the op you can Odin a custom recovery then flash super su.
Click to expand...
Click to collapse
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
A BIG thanks to you. I can't live without AdAway, TiBackup and Xposed anymore! The few days without root left me a little grumpy.
And regarding the NJ1 update as a whole...I THINK the baseband upgrade IS an actual upgrade. Since NE4, I always thought Wifi operated was somewhat choppy/throttled. THIS looks to have been improved back to ICS "standards". Re: voice, I've had a handful of dropped calls, broken up calls, and choppy data in low signal areas over the past few months on with NE4. Initial observations (albeit a tad premature) lead me to believe that this has improved as well based on a weeks worth of data use and a few calls in a "controlled" environment (the area and physical structure of my work office complex is not cellular signal friendly to begin with) I have also noticed that boot-up time has improved a bit as well. Thanks again for your efforts with the ATT GS3!
I flashed CF-Auto ROOT via Odin without success, unable to gain root access. Followed your instructions via TWRP and flashed SuperSu 2.16, my SGS3-i747 is properly rooted and functioning perfectly on UCUFNJ1. As always, thank you very kindly for all your valuable time, effort, hard work and guidance. Be well, sir!
mwrobe1 said:
I can confirm this as a root method for NJ1. You were exactly right regarding immediately booting into recovery after installing TWRP thru Odin. The files provided in your links (TWRP 2.8.1.0 Odin tar. http://techerrata.com/file/twrp2/d2a....1.0-d2att.tar and
SuperSU http://download.chainfire.eu/589/Sup...etrieve_file=1)
worked exactly as stated.
Click to expand...
Click to collapse
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Ark42 said:
What version of Odin do we need to flash that TWRP, or do you have a link handy?
I've seen quite a lot of different Odins out there and don't want to brick my phone by using the wrong one.
Any pitfalls to watch out for if using TWRP for the first time? I'm sure there is going to be a bunch of people having to do this now that both CF-AutoRoot and TowelRoot doesn't work anymore.
For me, personally, I just use root for AdFree and to edit the font fallback order to properly support Japanese instead of Chinese glyphs on shared Han-unified Unicode codepoints.
Click to expand...
Click to collapse
Use Odin 3.0.7
Not really any pitfalls to TWRP. It has an easy clean user interface and it works.
Once you have flash Super Su, in my how to ne4 update there is a flashable stock recovery. You just flash it with TWRP and once you reboot, stock recovery will be back on you phone.
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
Bob2014 said:
Hi enewman17,
Thanks for your posts and work. I'm hoping you can help me get the new NJ1 update installed and rooted.
Here's where I'm at: AT&T SGS3 on rooted stock NE4, installed using your guides from back in June this year.
The OTA NJ1 update downloaded but failed to install (as did the NE4 OTA back then, I assume because I was rooted).
My phone still has the TWRP recovery from the previous update, so I was hoping I could install using the original OTA cfg file download from the "advanced" section in your OP so as to avoid factory reset, etc.
I downloaded the file, renamed to update.zip, and copied to my SD card. However, when I boot into TWRP and try to install it, I get an error after the system check, something like "assert failed ro.secure==1". I guess I'm doing something wrong, maybe I'm mistaken about how the original OTA is supposed to work?
Again, I'm trying to end up with a stock, but rooted, NJ1 firmware but hopefully without having to reset/lose data and settings on the phone. I don't really care right now about resale or making it look like I haven't messed with it.
Thanks for any help you can provide! Let me know if I can provide any additional details.
Click to expand...
Click to collapse
I'll get my stock rooted system dump up later so you can flash in TWRP or CWM.
Do you guys want it packaged with the stock recovery?
mattsternc said:
I am actually looking to do the exact same thing. Currently rooted, with a lot of the AT&T apps frozen via Titanium Backup.
Hope there is some way to accomplish this without returning to stock!
Thanks in advance!
Click to expand...
Click to collapse
New galaxy user, here its a s3 for ATT 4.4.2 i747CUCFNE4. I have rooted using the Cf Auto-Root method.
Along the lines of trying to flash a new task manager apk, (for I had to factory reset my phone because the original task manager was missing) I came across a thread that had s5 apps (settings apk) and tried flashing this apk(don't laugh I know.) Then I couldn't get my phone to boot through the standard setup wizard. So I tried booting into recovery and factory resetting my phone clearing cache, dalvik, and partition.
My biggest problem arose when I chose to format system from ghe recovery.
I know all this can be fixed with odin but I can't find a 4.4.2 os link, I have read I can't simply downgrade my os. A link to a 4.4.2 stock rom thread would be greatly appreciated. I also have the Ktoonsez kernel installed if that makes any difference.
AT&T never released a full 4.4.2 ROM. AT&T released 4.3 and 4.4.2 via OTA updates only.
Since you are on the NE4 bootloader, do not flash anything that will attempt to downgrade the bootloader or the modem. A mismatched modem/bootloader combination may cause other problems.
Have a look here: http://forum.xda-developers.com/showthread.php?t=2789917
Ok I just reviewed your link in your response but just to be clear I'm starting where it says step 3: stock deodex and root and finishing the walkthrough from there?
And also will this reset me to my factory kernel?? Either or it doesnt matter to me I'm still trying to find one that I find suitable.
And I appreciate the speedy response you've been a huge help.
If you just want to get your phone up and running, I would flash Philz and then CM11. Confirm the bootloader and modem then decide if a stock ROM would be best.
I am always paranoid when it comes to flashing bootloaders on the s3 so I prefer to know exactly whan my phone is running.
I have never used the thread I linked because I no longer have an s3 i747m. Infact, I haven't had my s3 for several months.
Ok and my last question is you can flash Philz and CWM 11 through odin?
Nevermind I see it now greatly appreciated
I hope it all goes well. With CM11, you will also need to flash Gapps via CWM as CM11 does not include certain apps such as the Play store.
Now odin wont recoginize or open any of my rom files. Li see the rom im trying to flash by name but when i click open it only opens the next folder instead of initiating the flash. I really just need someone who has a 4.4.2 stock rom in md5 format.(edited or not.)
As a last effort if i get no answer im going to try to downgrade to another os and reupdate to 4.4.2 right after. Ive been searching for days now all i see are guides from how to upgrade to a different os . If it does include 4.4.2 they only posted the update and not the entire rom.
And when i do find someone posting a full rom for 4.4.2 its either not for 747i or its not a md5 file so someone plz help me.
glyph2 said:
Now odin wont recoginize or open any of my rom files. Li see the rom im trying to flash by name but when i click open it only opens the next folder instead of initiating the flash. I really just need someone who has a 4.4.2 stock rom in md5 format.(edited or not.)
As a last effort if i get no answer im going to try to downgrade to another os and reupdate to 4.4.2 right after. Ive been searching for days now all i see are guides from how to upgrade to a different os . If it does include 4.4.2 they only posted the update and not the entire rom.
And when i do find someone posting a full rom for 4.4.2 its either not for 747i or its not a md5 file so someone plz help me.
Click to expand...
Click to collapse
DO NOT downgrade to a bootloader older than your NE4 -- doing so will cause a hard brick.
You did mean i747 instead of 747i, didn't you?
Odin is designed to not flash any stock rom that would install a bootloader than the one on your phone. this is to save you from hard bricking your phone. Since you are on 4.4.2, any stock rom in a .tar.md5 format has an older bootloader than your NE4. As far as I know, the only stock NE4 rom on the forums is in a .zip format for flashing from recovery, it was posted by enewman17. (The thread audit13 linked.) If you tried to flash an older bootloader and baseband package through recovery you will probably hardbrick the phone.
Otherwise, there are roms based on TW in the forums: S3Rx, TMS3KK, Likewise, and others. Some use the stock kernel, others give you an option from their Aroma install. The iBubbler's kernel in a couple of these roms is reported to be excellent.
I'm guessing you pulled your S5 apk from either the S3Rx or Likewise thread.
I appreciate everyones feedback and guideance. Yeah I meant i747. It gets pretty easy to misread something when all you've been doing was researching roms and guides. And now its back to researching and finding one of the roms you mentioned. Much appreciated everyone I hope u all have a blessed day..
i know this a zip , but maybe could find help in the thread.
http://forum.xda-developers.com/showthread.php?t=2788357
good luck.
"all I can really do, is stay out of my own way and let the will of heaven be done"
Hey, sup?
I need your help, I'm trying to go back to stock firmware on my i747, currently I'm running CM11 latest snapshot.
Background: Some time ago, I accidently erased my imei. Took the phone to a guy who restored it but the phone doesn't work with 3G now, only 2G. So I wanted to try going back to stock firmware to see if that fixes the issue.
I tried downloading the CUEMJB file from here, but it doesn't work (keeps looping the same page) http://androidromupdate.com/att-samsung-galaxy-s3-sgh-i747-odin-stock-firmware/
Can you help me? Also, it is safe what I'm trying to do?
Thank you!
Triple check to make sure the imei displayed in About Device matches exactly to the one on the sticker under the battery.
If it does, and after you get stock working again, PM me and I can probably help.
As for the looping, do you mean the Web page? Just get the stock files from enewman17's thread. It's either in General or Development, can't remember for sure. Probably General.
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Triple check to make sure the imei displayed in About Device matches exactly to the one on the sticker under the battery.
If it does, and after you get stock working again, PM me and I can probably help.
As for the looping, do you mean the Web page? Just get the stock files from enewman17's thread. It's either in General or Development, can't remember for sure. Probably General.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thank you. Yes the IMEI matches.
I was able to download the file.
Unfortunately, the thing didn't went ok. After flashing my phone is unresponsive, black screen, no more boot
If I connect it to the computer at this point, it tries to search for a QHSUSB_DLOAD driver. Not sure what is that, I think I bricked my phone.
I've seen some guides for unbricking by placing a sd card in the phone at boot but so far it haven't worked
Going to one of the 4.4.2 bootloaders and modems for your device may fix the issue, maybe without going back to stock. But I do recall that a return to stock has been required by many. If you are on newer bootloader and modem than 4.3, do not use a 4.3 (MJB) file no matter the source. As Doc said use one of the releases by enewman17 that you can flash in your custom recovery, NE4 is here. enewman17 also has threads for MJB, NJ1, and NJ2 stock ROMs; all of these are flashed in a custom recovery. With the i747 I have continually seen it recommended that you upgrade bootloader and modem sequentially, that is upgrade to NE4 before going to NJ1, and NJ1 before going to NJ2. I can provide links to enewmans other threads if necessary.
BTW, the 4.3 release was not a full rom, it was an update/patch. Files I have seen run 100 mb or less. If that is the file you want, and can use w/o bricking your device see this thread http://forum.xda-developers.com/showthread.php?t=2722660 Only use it if you are on 4.1.1, 4.1.2, or 4.3 bootloader and modem.
Another way to get a 4.3 Odin flashable update is here. You must be on 4.1.1 or 4.1.2 bootloader and modem to use this as instructed.
dawgdoc said:
Going to one of the 4.4.2 bootloaders and modems for your device may fix the issue, maybe without going back to stock. But I do recall that a return to stock has been required by many. If you are on newer bootloader and modem than 4.3, do not use a 4.3 (MJB) file no matter the source. As Doc said use one of the releases by enewman17 that you can flash in your custom recovery, NE4 is here. enewman17 also has threads for MJB, NJ1, and NJ2 stock ROMs; all of these are flashed in a custom recovery. With the i747 I have continually seen it recommended that you upgrade bootloader and modem sequentially, that is upgrade to NE4 before going to NJ1, and NJ1 before going to NJ2. I can provide links to enewmans other threads if necessary.
BTW, the 4.3 release was not a full rom, it was an update/patch. Files I have seen run 100 mb or less. If that is the file you want, and can use w/o bricking your device see this thread http://forum.xda-developers.com/showthread.php?t=2722660 Only use it if you are on 4.1.1, 4.1.2, or 4.3 bootloader and modem.
Another way to get a 4.3 Odin flashable update is here. You must be on 4.1.1 or 4.1.2 bootloader and modem to use this as instructed.
Click to expand...
Click to collapse
Thank you very much.
But I'm with a phone that doesn't boot now. What would you recommend to do if there's something to bring it back
Alright! I just tried the SD card method w/ one of the files in the threads linked. Phone boots!
So it seems my bootloader is bad right?
japi2000 said:
Thank you very much.
But I'm with a phone that doesn't boot now. What would you recommend to do if there's something to bring it back
Click to expand...
Click to collapse
Can you get into recovery? If so you can flash the appropriate stock rom by enewman17.
Do you recall what bootloader and modem you were on? If you have TWRP as your recovery there are terminal commands you can use within the recovery to determine your bl/modem versions. This may also hold true for CWM and Philz Recoveries, but I don't know for certain.
If you can not get to recovery you may need to put a debrick image on an external sdcard to boot and then restore your device.
dawgdoc said:
Can you get into recovery? If so you can flash the appropriate stock rom by enewman17.
Do you recall what bootloader and modem you were on? If you have TWRP as your recovery there are terminal commands you can use within the recovery to determine your bl/modem versions. This may also hold true for CWM and Philz Recoveries, but I don't know for certain.
If you can not get to recovery you may need to put a debrick image on an external sdcard to boot and then restore your device.
Click to expand...
Click to collapse
Yes sir. With the SD card method I managed to boot the phone. Yay!
I don't recall bootloader and modem unfortunately. I know I was using CM11 one of the latest snapshots for d2lte.
I have access to download mode. Screen reads bootloader RP SWREV:2
I have access to recovery (its a basic one though). Reads Android system recovery <3e>
What do you recommend from here?
japi2000 said:
Yes sir. With the SD card method I managed to boot the phone. Yay!
I don't recall bootloader and modem unfortunately. I know I was using CM11 one of the latest snapshots for d2lte.
I have access to download mode. Screen reads bootloader RP SWREV:2
I have access to recovery (its a basic one though). Reads Android system recovery <3e>
What do you recommend from here?
Click to expand...
Click to collapse
That is the stock recovery. If you were successfully running one of the latest CM11 snapshots, you were probably on one of the three 4.4.2 bootloaders ( and modems ), they are NE4, NJ1, and NJ2. This would explain why the MJB (4.3) image you downloaded and flashed would soft brick your phone. It looks like that flash may be responsible for you being back on stock recovery, at best guess. Before anything else, do a factory reset from the stock recovery. This is frequently necessary to boot when going from a CM/AOSP LP rom back to stock.
Since you can get to download mode, I think the best bet would be to install a custom recovery. TWRP for the i747 is here, the top image is flashable with Odin while in download mode. Remember not to reboot from Odin. Instead remove the cable, pull the battery, then boot straight to recovery. Once you have TWRP loaded, boot into recovery and use the terminal emulator in it to determine bootloader and modem with these commands:
Code:
getprop ro.bootloader
getprop | grep version.baseband
Once you know the version of bootloader and modem you had been on, reflash that version from TWRP you will probably need the file on an external sdcard to do so. After this you can flash your rom of choice from TWRP, stock or otherwise. Since you were having imei issues go with one of enewman's stock roms, as @DocHoliday77 suggested. He can then help you with the imei issues if still necessary. Any other ideas Doc?
Ok, so
Bootloader = I747UCUEMJB
I don't get anything when running getprop | grep version.baseband in the recovery.
This is what I've done so far.
Booted w/ the sdcard trick (bootloader in the sdcard).
Installed twrp
Installed the following files:
AT&T_I747UCUEMJB.zip
d2att_I747UCUEMJB_bootloader.zip
d2att_I747UCUEMJB_modem.zip
d2att_Kernel_Stock_init.d_4_3_MJB_v1.0.zip
That brought the phone to life again (w/ stock 4.3). Then I flashed CM12 from the recovery. All went ok.
Problem is, I still don't have 3G connectivity, only edge.
What would you recommend try next?
Thank you
Alright, I was able to upgrade to UCUFNJ1 for both the bootloader and baseband. Still no 3G. Ideas?
Pm me. As I said before, if the imei is correct, I might be able to help. I can't do it here though because it's against forum rules to post the info publicly. (Too many people want it for illegal use).
When you pm me, include your current bootloader and baseband. (Just so I don't have to keep coming back here for reference). Also include how it was lost and if you know how it was restored.
I know you've already posted some of this, but I get lots of PM's so it'll help me keep track of everything without going back and forth between here and there.
Also, you need to be stock for this to work, so don't flash anything else just yet.
Glad to hear you got it running again BTW!
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Pm me. As I said before, if the imei is correct, I might be able to help. I can't do it here though because it's against forum rules to post the info publicly. (Too many people want it for illegal use).
When you pm me, include your current bootloader and baseband. (Just so I don't have to keep coming back here for reference). Also include how it was lost and if you know how it was restored.
I know you've already posted some of this, but I get lots of PM's so it'll help me keep track of everything without going back and forth between here and there.
Also, you need to be stock for this to work, so don't flash anything else just yet.
Glad to hear you got it running again BTW!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Alright thank you
Alright, I'm happy to say that with the help of our fellow DocHoliday77 I was able to solve the issue !
Thanks everyone!
Glad you have it working.
Way to go Doc.
Damn japi2000. You did that quick good job.
Thank you!
I can't believe I went from a almost dead phone to a fully working one in only a few days, even with the 3G/4G working again !
This forum and people are amazing! Thank you!