AT&T OTA update; stops at Samsung splash screen - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I have been reading through many threads last night and today trying to figure out the best way to get rooted stock back on my AT&T S3 i747. I had hoped to figure it out myself, but have come to the realization that I need a little guidance.
In light of that, I'll try to give concise information. First of all, I am simply looking to end up with stock.
Series of events:
*Have had stock since given this phone in August; it was kept up to date with OTA and it was current (4.4.2) as of yesterday morning when att pushed the newest update to the phone.
*I rooted the phone in September using CF root and Supersu to both root and block Knox and it had been working very well until the attempted update yesterday.
*I no longer have a custom recovery backup
*yesterday my phone went through the update (download and install), but when it rebooted, it only made it through the Samsung splash screen and then went black.
*I am able to boot up both stock recovery and into download mode
*Using the stock recovery to reset the phone has not fixed the problem
Having never used Odin or installed a custom ROM, I am hesitant to flash anything to the phone until I verify that the new bootloader (that is now possibly there due to the OTA update) and anything I try to install won't conflict and make my problem worse.
It seems to me that I should use Odin to load a custom recovery, make a backup, and then flash a ROM. If that is correct, would the recovery ROM found in this thread be the correct one: http://forum.xda-developers.com/galaxy-s3-att/general/ucufne4-to-ucufnj1-update-t2941792
If it is not the correct ROM, what would be the correct one?
Thank you,
M

For a custom recovery, flash the most recent tar.md5 file from here using Odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/d2lte/
Boot into recovery, create a backup, and flash a custom ROM. I recommend the most recent CM10.2 so you can determine the bootloader currently installed on your phone. Once you determine the bootloader, you can decide how you want to proceed.

Thank you so much for your response.
I did as you suggested and I do indeed have the UCUFNJ1 bootloader. That does help me determine which direction I can take. Although, now having tried out a non-Samsung ROM, I may have changed my mind about keeping stock on the phone. If I decide to go back to stock, I'll just keep my eyes open for a stock ROM that states it requires that bootloader, correct?
Again, thank you so much for your help!

Related

[Q] Problem getting OTA/ Cannot search for it.

Hello, I'm having a strange issue with my GS4. I have rooted it and flashed a couple different custom ROMS on it, but I decided to go back to stock so that I could get the 4.3 OTA. I did the triangle away and then flashed stock 4.2.2 software through odin. However, when I go to search for the update, I get the following message " Your device has been modified. Software updates are not available.". In fact my device status still says CUSTOM under device status in about phone. Could this be because the flash counter is still tripped, or did I flash a bad stock firmware download?
Also strange: I've noticed that the sound my phone makes when I lock it is not the stock sound, it's still the lock sound from wicked V8 Rom.
Any help anyone could give me would be greatly appreciated. Thanks.
thunderstorm116 said:
Hello, I'm having a strange issue with my GS4. I have rooted it and flashed a couple different custom ROMS on it, but I decided to go back to stock so that I could get the 4.3 OTA. I did the triangle away and then flashed stock 4.2.2 software through odin. However, when I go to search for the update, I get the following message " Your device has been modified. Software updates are not available.". In fact my device status still says CUSTOM under device status in about phone. Could this be because the flash counter is still tripped, or did I flash a bad stock firmware download?
Also strange: I've noticed that the sound my phone makes when I lock it is not the stock sound, it's still the lock sound from wicked V8 Rom.
Any help anyone could give me would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Just my personal experience, but whenever using Odin to revert back to stock, it always works right if I flash a non-TouchWiz ROM via TWRM/CWM THEN use Odin to revert. When reverting via Odin from a modified TW something always tends to stick around.
As far as returning to official status, you should be able to use Triangle-away on a rooted/stock firmware then temporarily unroot to install the OTA. Just a question though; why do the official OTA which introduces the Knox counter? There are CWM-flashable pre-rooted, non-Knox 4.3 TMO TW ROMs out already...
lordcheeto03 said:
Just my personal experience, but whenever using Odin to revert back to stock, it always works right if I flash a non-TouchWiz ROM via TWRM/CWM THEN use Odin to revert. When reverting via Odin from a modified TW something always tends to stick around.
As far as returning to official status, you should be able to use Triangle-away on a rooted/stock firmware then temporarily unroot to install the OTA. Just a question though; why do the official OTA which introduces the Knox counter? There are CWM-flashable pre-rooted, non-Knox 4.3 TMO TW ROMs out already...
Click to expand...
Click to collapse
Thanks for quick response. So you're saying I should root, then flash a stock aosp or gpe rom, and flash stock rom from there? I actually did have a gpe rom on my phone the last time I went back to stock, but I had wicked V8 first and went back to stock in between.
Another question would be if that small thing like the lock sound would be what's making me not be able to get the ota, or is it because the flash counter is tripped still and it's saying that I'm still custom?
noob question sorry, how do you temporarily unroot?
thunderstorm116 said:
Thanks for quick response. So you're saying I should root, then flash a stock aosp or gpe rom, and flash stock rom from there? I actually did have a gpe rom on my phone the last time I went back to stock, but I had wicked V8 first and went back to stock in between.
Another question would be if that small thing like the lock sound would be what's making me not be able to get the ota, or is it because the flash counter is tripped still and it's saying that I'm still custom?
noob question sorry, how do you temporarily unroot?
Click to expand...
Click to collapse
The reason you can't OTA is because your flash counter is still tripped. If it says you are on a custom firmware then you won't be able to update via OTA.
No need to re-root. Just use Odin to flash a custom recovery. Once there, I'd flash whatever non-TouchWiz ROM you have on-hand... Wicked, the TouchWiz Infamous ROMs, GPe ROMs (maybe, I don't know about these) I would avoid. If you already have CM10.x-11, ParanoidAndroid, Liquid, etc readily available, say, on your SD card I'd flash one of them. No need to flash the gapps, kernel, whatever, just the base ROM itself. Once that's done, use Odin to flash the Stock MDL .tar. After that, I'd say flash CF-Auto Root, run Triangle Away, then in the superuser App there should be an option to unroot (or temporarily unroot). Once that's done, you should be able to update via OTA.
lordcheeto03 said:
The reason you can't OTA is because your flash counter is still tripped. If it says you are on a custom firmware then you won't be able to update via OTA.
No need to re-root. Just use Odin to flash a custom recovery. Once there, I'd flash whatever non-TouchWiz ROM you have on-hand... Wicked, the TouchWiz Infamous ROMs, GPe ROMs (maybe, I don't know about these) I would avoid. If you already have CM10.x-11, ParanoidAndroid, Liquid, etc readily available, say, on your SD card I'd flash one of them. No need to flash the gapps, kernel, whatever, just the base ROM itself. Once that's done, use Odin to flash the Stock MDL .tar. After that, I'd say flash CF-Auto Root, run Triangle Away, then in the superuser App there should be an option to unroot (or temporarily unroot). Once that's done, you should be able to update via OTA.
Click to expand...
Click to collapse
Ah, okay. I think I understand that, I'll give that a try. Thanks for all your help.
Okay, so I tried doing everything you told me to do and got some weird results and thought I'd post them for anyone else that may run into this problem.
I flashed a custom recovery through Odin, then flashed the AOSP Liquid Rom like you said. I then flashe the stock MD5 file through Odin and let it do its thing. Once it was done, that's where the weird stuff started. The phone rebooted as it should, but then it got hung on the white T-mobile screen. It just sat there for a very long time. Now I've done this enough times to know when its taking too long and there's a problem.
So I did something that I know probably shouldn't have done and I held down the power button until it turned off. I then tried to boot it again to no avail, same thing.
After this I booted into the stock recovery and decided to do a factory data reset from there. (I was pretty sure there was nothing wrong with the stock Rom as I've used it before; there must have been something still there from the Liquid Rom causing problems.) When I rebooted from the recovery this way, it finally booted right up.
I now thought that I needed to flash CF-AutoRoot and then triangle away, but no, for some strange reason my device status now reads OFFICIAL!
I searched for the update and it is now in the process of downloading.
(Strangely enough though, the lock sound from wicked V8, is STILL there. I don't get it and I don't even want to know anymore.)
Sorry for the super long post, but I thought that if anyone else was having my same problem they should see this.
Thanks again for all your help and I hope you'e having a great Thanksgiving.

[Q] Help!! ROM flashing problems

Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
dreammaster252 said:
Before I get to the point let me explain what happened. I attempted to root my S3. It did work up until I got to the point where I was ready to flash a ROM and it didn't work. I received the "status 7" error on CWM and I receive an error on TWRP that means the same thing. So what I did since I couldn't restore from a backup that I would get bootloops from, I attempted to install a ROM that was .tar or md5.tar through ODIN which only worked for original firmware (given in the screenshot). I have managed to install this ROM on my phone through TWRP but unfortunately it is for TMobile and somehow my AT&T service works on it. Here is a screenshot of the phone. I have tried flashing "aokp_task650_d2lte_kitkat_6.3.2014" that is made for the AT&T S3 but no matter what I try to flash it will not flash. I have already tried doing the "ASSERTS" method but it did not work. Can someone please help me fix this issue??? :/
Click to expand...
Click to collapse
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Larry2999 said:
The hybrid firmware thing shouldn't really happen but for some reason, cross flashing between T999 (T-Mobile) & i747 (AT&T) sometimes happens without necessarily causing a brick. I would suggest you do a complete stock restore to AT&T 4.3JB firmware (UCUEMJB). Thereafter, you can go back to flashing your preferred custom ROM. Since you appear to be able to get to TWRP, you can first, from custom recovery, remove all existing firmware including OS and then reinstall the stock firmware. It appears the bootloader is still UCUEMJB so flashing AT&T stock firmware shouldn't be a problem. Please see the thread below for 4.3 stock restore...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
dreammaster252 said:
So in this case, I just flash everything that it gives me correct? Is the stock ROM still rooted? If it is not then what rooting process do you suggest I go through? If it is a rooted ROM. Then do you recommend I unroot it and root it again or take some other alternative method? I really appreciate your help
Click to expand...
Click to collapse
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Larry2999 said:
It's a complete stock image which will take you to as near factory condition as you can get. This means it is unrooted. You would need to re-root after (successful) firmware installation. Prior to flashing the firmware, please remember to use custom recovery to remove all existing firmware including OS. Once you've restored the firmware, there are several ways to root but my preferred method is SafeRoot. You can find the download links and instructions to SafeRoot in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2565758
You can also try Option 2 in the thread below ...
http://forum.xda-developers.com/showthread.php?t=2538991
Click to expand...
Click to collapse
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
dreammaster252 said:
I am running 4.4.2 on my S3 (AOKP Task650) but unfortunately I am receiving some battery drain. Is there a Kernel I could use to prevent this and save more battery? Which Kernel do you recommend most? Also I am having issues with my Data. I get "E" for edge in a 4G LTE area? Is there a radio that I can flash or APN for this to fix that problem?
Click to expand...
Click to collapse
just to confirm, you re on ucuemjb bootloader, and installed/running Task650 4.4.4 rom 7.21.2014 (at this writing thats the latest update for the rom)
right?
sorry last time i tried to flash task650 rom, i got errors concerning the bootloader, went back to CM11 which has been my go-to-go rom and everything works fine, after you respond i will flash and get back to you on the network issues
thanks

UCUFNE4 to UCUFNJ1 update 16 gig AT&T I747

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

Softbricked to download mode, unsure which versions are in my phone

I have a few specific questions at the bottom, but first, here's the long details:
I ran the custom ROM Hyperdrive RLS 16 (4.1.2) for years and loved it, but the past week I felt it was time to upgrade to a new ROM that was more up to date. I started to try out R3ARMED (4.4.2), did a full wipe in CWM and installed the zip files provided (the ROM and a d2att specific file).
Unfortunately, in my excitement I forgot to make sure that I had a 4.4 bootloader and modem, which seems to be rather essential for this particular ROM. The install failed and I thought I may have bricked the device, but I was able to update CWM and get back into recovery mode. This time, I got through the AROMA installer for the new ROM, but on reset I got stuck in a hard bootloop. It's pretty nasty--I can't use the key combination to reboot into recovery or download mode, and I only get as far as the opening "SAMSUNG" screen before the device blacks out. However, I can use a USB jig to force reboot into download mode--it's the only interface I can get with the phone at this point. ODIN recognizes the device, and when I use Heimdall and its drivers, I'm able to use those tools to interact with the phone. So I hope I'm not completely lost, but not being able to access CWM recovery mode definitely hurts.
Here's what I've tried so far to fix it:
- Without a USB jig, load recovery images onto a 16 GB SD card, insert into phone and power up (no successes, some images actually made it so the "SAMSUNG" screen no longer showed, others corrected this issue)
- Re-flash CWM with heimdall (failed)
- Used the Ultimate Android Toolkit to convert the CWM img into a tar that ODIN can flash, and tried to load it (failed)
I'm looking into trying to flash a full recovery onto the phone to see if that can fix it. But I have a few concerns:
1. I know that once my phone gets a 4.4 bootloader and modem, I can't go back to an earlier stock version.
2. I had an unsuccessful 4.1 -> 4.4 install attempt in the process of bricking updating my phone.
3. I have no idea if the install impacted the bootloader--so I don't know whether I can try a 4.3 stock flash or need to use some of the more recent phone dumps.
My first question is, as usual, what is the best route to take to recover this phone?
My second is, are there tools I can use for a phone in ODIN mode to check the version of the bootloader/modem, check on the integrity of the file system, etc. etc.?
I have a replacement phone on its way, but I view this as an excellent learning opportunity, and would love to hear some advice.
You have an i747 or i747m?
Do you see anything about warranty bit in download mode?
On the positive side, flashing the R3ARMED rom would not have changed your bootloader and modem. If you were on 4.1.2 before the flash, you should still be on 4.1.2 bootloader and modem.
There is at least one MJB_MJB Odin flashable stock ROM with active download links, it is for the i747. If you have the i747 and not the i747M you could try it.
If you have the i747M there are Odin packages for all of the stock ROMs at sammobile.com. Or, you could extract the system.img from the i747 ROM and flash it with Heimdall. BUT only if you are careful to avoid all of the files pertaining to bootloaders, radios, etc. (*.mbn, non-HLOS.bin, etc.) This route may not be for the faint of heart, but I promise I am not the only one to have done so. I didn't do so until I read of others having done this.
dawgdoc said:
On the positive side, flashing the R3ARMED rom would not have changed your bootloader and modem. If you were on 4.1.2 before the flash, you should still be on 4.1.2 bootloader and modem.
There is at least one MJB_MJB Odin flashable stock ROM with active download links, it is for the i747. If you have the i747 and not the i747M you could try it.
If you have the i747M there are Odin packages for all of the stock ROMs at sammobile.com. Or, you could extract the system.img from the i747 ROM and flash it with Heimdall. BUT only if you are careful to avoid all of the files pertaining to bootloaders, radios, etc. (*.mbn, non-HLOS.bin, etc.) This route may not be for the faint of heart, but I promise I am not the only one to have done so. I didn't do so until I read of others having done this.
Click to expand...
Click to collapse
It's a regular i747, not i747M. Thanks for the advice... you've given me a few things to try now! Will report back later with results.

Just cant re install stock firmware

Hi all, every time I want to either install a custom rom or flash back a stock firmware it is an impossible task. Nothing works from the instructions to the firmware's themselves.
I've had a few custom firmware's on my tab s T705 tablet all of which are garbish and reboot themselves even when doing something simple like watching a video!
So wanted to flash back to stock firmware. However no matter what "stock" firmware you download for your model tablet even from reputable websites either the Samsung logo hangs at the start after a flash or twrp fails to flash a firmware.
Why is is so difficult to
a. Get hold of a stock rom
b. actually flash it and get it install!!!
Ive tried all sorts, wiped the entire tablet in twrp, used odin, used so called "stock" firmware, used and paid for skipsoft toolkit which I highly regret no as its utter usless doesn't do anything it states it does and their help section might as well not exist.
So I have a tab s with nothing on it and nothing that wants to install onto it.
What do I do? as so far its doing really nicely as a f**king paperweight.
That's really strange. I never had problem flashing the stock ROM from Odin on SM-T800.
Akopps said:
That's really strange. I never had problem flashing the stock ROM from Odin on SM-T800.
Click to expand...
Click to collapse
Seriously mate, don't know what to do, nothing seems to work. No firmware seems genuine. How can I obtain an original firmware without signing up to sites or pay for a premium server to get the file?
Thanks
Currently I wiped the entire system via TWRP except the micro sd that has the firmware zip file on.
This is a recent log from twrp when trying to install a "stock" firmware. Hopefully someone can figure out what's going wrong
Problem fixed. Just kept trying different firmware roms online and found an original 4.4.2 that worked. just updating to 6.0.1 through Samsung updates now. And keeping the downloaded file safe and going to do a android backup dump from twrp once its done.
Thanks
how to mark this thread as resolved?
New issue. All I want to do now is just root the stock firmware to allow me to use certain apps. However every time I try a root either auto cf root, supersu, kingroot. All that happens after flashing the root is the Samsung logo boot loops saying recovery cant enforce in red and blue text.
Is knox preventing it because yet again my tablet does the opposite of what the instructions say.
morgiee said:
New issue. All I want to do now is just root the stock firmware to allow me to use certain apps. However every time I try a root either auto cf root, supersu, kingroot. All that happens after flashing the root is the Samsung logo boot loops saying recovery cant enforce in red and blue text.
Is knox preventing it because yet again my tablet does the opposite of what the instructions say.
Click to expand...
Click to collapse
Try reinstalling the stock firmware, and then install TWRP and get the zip package for SuperSU and install the zip package thru TWRP.

Categories

Resources