Stock Recovery and Cache for enabling OTA after CF Auto Root - Sprint Samsung Galaxy S6

These files will restore stock recovery and cache for those who have rooted with CF Auto Root, so that you can return those partitions to factory status for an OTA. Remember that any changes to /system in Lollipop nullifies OTA capability so you also need to undo any changes you've made, restore any bloat, unroot from within SuperSU, etc. For those who used CF and have done minimal mods or changes, this is merely a faster (both in terms of download time and flash time) way of restoring recovery and cache (which are modified when you flash CF Auto Root) than flashing the full stock tar. If you've deleted a whole bunch of bloat, installed Xposed, flashed mods in recovery, etc. then you probably just wanna use the full tar
Flash via Odin PDA/AP slot.
OC9:
OCF:
https://www.androidfilehost.com/?fid=24052804347756900
OE2:
https://www.androidfilehost.com/?fid=24052804347756938

Sweeet!!! DO you know of anywhere else to get the full stock TARs (particularly OE2)?? Or do you know anywhere to get full data wipe TARs? Thanks!

JoeFCaputo113 said:
Sweeet!!! DO you know of anywhere else to get the full stock TARs (particularly OE2)?? Or do you know anywhere to get full data wipe TARs? Thanks!
Click to expand...
Click to collapse
Well where do you think I pulled the recovery and cache from haha? I'll have an AFH mirror up later today

iBowToAndroid said:
Well where do you think I pulled the recovery and cache from haha? I'll have an AFH mirror up later today
Click to expand...
Click to collapse
AHHHH!! You are a God! Thanks so much :good:

I flashed the stock rom downloaded directly from Sammobile and it still didn't allow OTA. It said that my phone had been modified... Not sure if I missed something because it stuck in a bootloop with the stock ROM after TWRP unless I flash Unikernel. Maybe the newest 5.1.1 doesn't allow OTA. I tried it with the OFE ROM completely stock.

Johnrob011045 said:
I flashed the stock rom downloaded directly from Sammobile and it still didn't allow OTA. It said that my phone had been modified... Not sure if I missed something because it stuck in a bootloop with the stock ROM after TWRP unless I flash Unikernel. Maybe the newest 5.1.1 doesn't allow OTA. I tried it with the OFE ROM completely stock.
Click to expand...
Click to collapse
If you install a non-stock recovery (like TWRP) you cannot take OTA updates. Any version, doesn't matter.
Follow the guide posted at http://forum.xda-developers.com/sprint-galaxy-s6/general/how-to-to-100-stock-root-t3075448 and you will have the latest version with custom recovery and root.
Or, if OTA updates are crucial to you, Odin the TAR file and stop there.

Mine wasn't working after I flashed the stock rom from Sammobile before I flashed twrp, since it wouldn't update I figured I needed twrp to stay up to date from now on but I'm not trying to post bad information to anyone, it wasn't working for me but maybe these caches can bring back OTA. I wish there was a way to get Samsung pay working.

Related

[GUIDE] AT&T CWM-flashable UCALG1 update | no wipe, leaves root and universal search

[GUIDE] AT&T CWM-flashable UCALG1 update | no wipe, leaves root and universal search
I've put together a zip file with the I747UCLG1 AT&T OTA update that can be flashed using CWM. This file
does not trip the flash counter
preserves root
does not include the Google search update to remove universal search
does not wipe /data
does require removing all themes and modifications
Standard disclaimer: I am not responsible if this bricks your phone, destroys your IMEI or kills your kids.
Prerequisites: You have to be on stock I747UCALEM for this to work. It may be rooted, but all the standard AT&T and Samsung bloatware must be there with no modifications. It's okay if some of the apps are frozen with Titanium Backup. You must not have any other mods or themes applied. The updater will check this stuff and abort if anything is wrong. I personally restored a nandroid backup I made right after rooting. If you didn't make one, you can use Odin and the instructions here to go back to stock.
To apply it:
Boot into recovery and make a nandroid backup.
Go back to AT&T UCALEM rooted stock if necessary (see above). If you're already on stock UCALEM but have framework-res.apk modications applied, you can flash this zip to restore framework-res.apk to UCALEM stock.
Make sure CWM recovery from clockworkmod.com is installed. The recovery from Team Epic will not work. You can get a zip file to flash in your current recovery to install v5.8.4.5 from here. Use one of the first two files; the ones that start with "recovery-clockwork". After you flash the zip, restart recovery through the "advanced" menu. Your recovery should say "ClockworkMod Recovery" at the top and not "CWM-based Recovery".
Put one of the zip files from below on your internal or external SD card.
Boot into recovery
Wipe cache and dalvik cache (optional?)
Flash the attached zip
(Optional) Go to Backup and Restore, Advanced Restore and restore the /data from the nandroid backup you made in step 1. If you used a nadroid backup in step 2, this should restore your data and apps. If you used Odin to flash the rooted UCALEM image, this step isn't necessary.
Reboot
Open Settings / Application Manager. Choose All tab. Click on AT&T Software update. Clear "Clear data". If you were getting OTA notifications before, this will prevent them from recurring. After doing this, your phone will know it's up-to-date.
This worked for me. I checked that my flash counter is still at 0 and Google search is still finding local stuff like apps. I still have root.
DOWNLOADS:
I747UCALG1_OTA.zip: This is the full OTA, with kernel and bootloader. You must be using the stock UCALEM kernel for this to work.
I747UCALG1_OTA_No_Bootloader.zip: This is the full OTA without the bootloader.
I747UCALG1_OTA_No_Bootloader_No_Kernel.zip: This is the OTA without the bootloader or the kernel. You can use this if you're already running a non-stock kernel.
I747UCALG1_OTA_Bootloader.zip: This is just the bootloader. You can apply this along with the "no kernel no bootloader" zip above in case you want everything but the kernel.
MODS:
This process requires the stock framework-res.apk, so at this point you'll need to reapply any mods you already applied. Here are some mods that I've rebuilt against LG1. Both are zip files you can apply through recovery.
Tether and Cell Standby Fix: This includes the mod to enable native Bluetooth and WiFi tethering from here and the fix for the incorrect reporting of Cell Standby time from here.
Tether, Cell Standby Fix, Increase Autobrightness: The same as above, but also with a mod to bump up autobrightness levels from here.
No Increasing Ring: This removes the increasing ringtone volume. The mod is from here.
OTHER PIECES:
Kernel: The UCALG1 kernel and kernel modules.
UCLG1 Modem: Just the modem from the OTA.
UCLEM Modem: The modem from the stock UCALEM firmware.
UCALG1 Bootloader
UCALG1 Bootloader (no checks): This is the LG1 bootloader will all the checks for AT&T ROMs removed from the flashing script. This can be flashed even if you're running a non AT&T ROM, but only flash it on AT&T phones!
UCALEM Bootloader
UCALEM Bootloader (no checks): This is the LEM bootloader will all the checks for AT&T ROMs removed from the flashing script. This can be flashed even if you're running a non AT&T ROM, but only flash it on AT&T phones!
LIST OF CHANGES IN OTA:
A full list of the files and partitions changed by the OTA is attached to this post.
Only 10MB? Wonder what they updated... not much need for it for me, Im on AOKP, but downloading anyways, and thanx button hit TWICE LOL
Let us know if it's a lockdown flash...
B-Naughty said:
Let us know if it's a lockdown flash...
Click to expand...
Click to collapse
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.
drothenberger said:
Doesn't seem to be. I still have my CWM recovery and I was able to flash the KT747 Sammy kernel. The OTA did flash aboot (the bootloader?) though. It tried to flash a new recovery, but I removed that part.
Click to expand...
Click to collapse
Hmmm... guess we'll just to see what users report, but for the wise, to all, use the zip provided just in case... AND FOLLOW THE OP
when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip
dave1977nj said:
when i try to do this I'm getting an error assert failed: apply_patch_check("/system/app/Flipboard.apk" E: error in sdcard/I747UCLG1_OTA.zip
Click to expand...
Click to collapse
Did you remove Flipboard or install an update?
You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.
drothenberger said:
Did you remove Flipboard or install an update?
You have to be on stock UCALEM. The OTA applies binary patches to a bunch of apps (including Flipboard.apk), so they have to be in a specific starting state for the OTA to apply correctly.
Click to expand...
Click to collapse
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?
Thanks
dave1977nj said:
yes backed up from day 1 it may have auto updated can someone tell me the stock version # of flipboard or an apk would be great! so i can install it?
Thanks
Click to expand...
Click to collapse
Here you go.
drothenberger said:
Here you go.
Click to expand...
Click to collapse
tried that still the same error message need some help please....
Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT
dave1977nj said:
tried that still the same error message need some help please....
Click to expand...
Click to collapse
What recovery are you using? Maybe give the CWM 5.8.4.5 a try (in the OP) if you're not already using it.
pinoymutt said:
Hmm, may want to consider removing the bootloader parts from the CWM until it's verified what exactly our friends at ATT had Samsung add to this. Updating bootloaders never is a good thing when it comes to ATT
Click to expand...
Click to collapse
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
drothenberger said:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
Click to expand...
Click to collapse
So if I'm on stock LG1 I flash rooted LEM and then flash your zip? Does your update include the baseband update ?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
mobilehavoc said:
So if I'm on stock LG1 I flash rooted LEM and then flash your zip?
Click to expand...
Click to collapse
I don't think I understand. You're already on UCALG1, but you want to apply the OTA to go from LEM to LG1? Why?
If you do want to do that, you do need to flash the rooted LEM tar through Odin. Then follow the rest of the instructions in the OP.
Does your update include the baseband update ?
Click to expand...
Click to collapse
Yup. It includes everything except the Google search update, recovery, and (optionally) the bootloader.
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Odin back to pure stock working fine.. some of my apps fore close though
drothenberger said:
I've put a version without a bootloader in the OP. Worked for me after I flashed stock rooted UCALEM with Odin.
Click to expand...
Click to collapse
Many thanks! You never know what kind of goodies they like to through in new bootloaders, so better safe than sorry!
ewingr said:
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Click to expand...
Click to collapse
I think there are only two ways to get rooted LG1: Start with rooted LEM and use OTA Rootkeeper to keep root when you apply the OTA or use the method in the OP. In your case, you'd have to Odin back to the rooted LEM to get root, then if you want to go back to LG1, follow the OP steps.
ewingr said:
I"m a bi confused too, but from a different perspective.
I am completely stock; got upgraded today to UCALG1. I am interested in rooting (and then possibly applying a kernel from this forum), but not sure which method I should use based on teh fact I am now on lg1.
Click to expand...
Click to collapse
Depends which method of rooting you want to use. If you are interested in the method that does not trip the counter, then yes you would flash that through ODIN (which will technically revert you back to UCLEM with root injected) and then apply the update in the OP here and in the end you should be on a a rooted UCALG1 w/o a tripped counter.
Anyone wanna pull just the baseband for cwm zip?

SuperSU Giving 1 Flash Counter. Trying to go back to stock rom with OTA.

Hello,
I’m looking for some guidance on getting my phone back to completely stock.
Steps I’ve done:
I have re-flashed back to the stock image using Odin. After doing so I wipe/reset. I then had a flash count of 8.
I then used Chainfires method and flashed with Odin to root device, which only installs super SU. I ran triangle away and still had a flash count as one. So I ran triangle away again and clicked the box that disables superSU for an amount of time. The rom went back to official with no flash counts.
Here is where I ran into problems. I ran super SU after seeing I had no flash counts to unroot the device. As soon as I opened superSU I got a flash count back to 1 again and could not update device from original firmware. I tried several different times including full wipe reset after I unrooted with superSU.
So what I did was re-rooted device using odin and install triangle away. I ran the exact same things as before by disabling SuperSU in triangle away and I was back to the official rom and no flash count. I then disabled superSU in manage applications and removed any notifications (force stop).
My phone was able to download the update as it recognized the stock rom, but then when I attempted to install it my phone it did its normal reboot for install and said install failed custom binary etc. Checked and again I had a 1 flash counter.
Possibly where I messed up?
Things I can gather or maybe I’m wrong. I downloaded stock image from Samsung. It was a TAR file. It is a 4.1 file. In addition I know it was for the T889 for T-mobile. Is there a possibility that this is the wrong file? Is there something else I should be flashing to phone with the PDA in any of other slots? Recovery file? Why when I attempt to run superSU unroot does it add a flash counter?
I do not have my original stock image. Phone T889 T-Mobile.
I’m usually pretty good at this stuff, but have run into a rut. I want to return my phone to completely stock and get OTA updates.
Any help would be greatly appreciated! Thank you in advance!!
RSVRMAN1 said:
...I’m usually pretty good at this stuff, but have run into a rut. I want to return my phone to completely stock and get OTA updates.
Any help would be greatly appreciated! Thank you in advance!!
Click to expand...
Click to collapse
If the main goal is to go back to stock to get official OTAs, I'm pretty sure the binary count bit doesn't need to be a worry. What has worked for me is to
- factory reset/wipe data (can do this using custom recovery or just the official stock recovery actually)
- ODIN factory image (I tend to DL them from sammobile)
At that point I had no issue grabbing OTAs - not sure if this helps but I hope it does
dwitherell said:
If the main goal is to go back to stock to get official OTAs, I'm pretty sure the binary count bit doesn't need to be a worry. What has worked for me is to
- factory reset/wipe data (can do this using custom recovery or just the official stock recovery actually)
- ODIN factory image (I tend to DL them from sammobile)
At that point I had no issue grabbing OTAs - not sure if this helps but I hope it does
Click to expand...
Click to collapse
Any response will help thank you!
I downloaded from sammobile as well. Do you download the factory image and install on phone or do you flash the factory image from ODIN.
I should probably clarify I'm trying to update phone by clicking software update. When I click that currently it states. Your device has been modified. Software updates are not available.
This is why I've been going the triangle away superSU route trying to just install the original stock firmware, click update and receive the latest version.
Here some additional info on my kernal and build. I'm not sure if this is possibly wrong?
Currently phone says android 4.1.1 baseband T889UVALL4 Kernel version 3.031-598701 [email protected]#1 SMP PREEMPT Sat Jan 5 19:34:13 KST 2013
Build number JR003C.T889UVALL4
Thanks again!
RSVRMAN1 said:
Any response will help thank you!
I downloaded from sammobile as well. Do you download the factory image and install on phone or do you flash the factory image from ODIN.
I should probably clarify I'm trying to update phone by clicking software update. When I click that currently it states. Your device has been modified. Software updates are not available.
This is why I've been going the triangle away superSU route trying to just install the original stock firmware, click update and receive the latest version.
Here some additional info on my kernal and build. I'm not sure if this is possibly wrong?
Currently phone says android 4.1.1 baseband T889UVALL4 Kernel version 3.031-598701 [email protected]#1 SMP PREEMPT Sat Jan 5 19:34:13 KST 2013
Build number JR003C.T889UVALL4
Thanks again!
Click to expand...
Click to collapse
I used ODIN - and the info looks fine. I had no issue getting the OTA from UVALK8 to UVALL4 using this approach, though is there a particular reason you want to go the click-update path? I ask because sammobile has a factory image of the most current version (UVBMD1) as well... might be a plan B at least.
dwitherell said:
I used ODIN - and the info looks fine. I had no issue getting the OTA from UVALK8 to UVALL4 using this approach, though is there a particular reason you want to go the click-update path? I ask because sammobile has a factory image of the most current version (UVBMD1) as well... might be a plan B at least.
Click to expand...
Click to collapse
I plan on giving the phone to my better half and buy new note 3 eventually. I feel that if I can click and have the phone update I know everything works and wont have to touch it again, while if I install the latest then on the next update I'm unsure if it will update having to flash the new stock rom again.
I love custom roms, but it requires lots of work keeping them up to date and can have various issues that I dont want her to deal with.
I'm wondering if I should try to flash a different stock recovery rom?
Here are 3 separate roms I could install do you have one you would suggest?
cant post the link but its from stockroms dot net
Do I need to install stock recovery on my phone? I guess I thought I just needed to install the factory image. Can you flash stock recovery on Odin or where do you put this into equation?
install stock image/install recovery/root/wipe/triangle away/superSU-unroot/wipe/update
Thanks again for the quick response.
RSVRMAN1 said:
I plan on giving the phone to my better half and buy new note 3 eventually. I feel that if I can click and have the phone update I know everything works and wont have to touch it again, while if I install the latest then on the next update I'm unsure if it will update having to flash the new stock rom again.
I love custom roms, but it requires lots of work keeping them up to date and can have various issues that I dont want her to deal with.
I'm wondering if I should try to flash a different stock recovery rom?
Here are 3 separate roms I could install do you have one you would suggest?
cant post the link but its from stockroms dot net
Do I need to install stock recovery on my phone? I guess I thought I just needed to install the factory image. Can you flash stock recovery on Odin or where do you put this into equation?
install stock image/install recovery/root/wipe/triangle away/superSU-unroot/wipe/update
Thanks again for the quick response.
Click to expand...
Click to collapse
I should clarify the factory images are from note2root DOT com
Going to keep trying to reflash: Just did it again and still keep getting a binary account right after I complete the Full unroot.
Why does it go from official to custom after this last step?
Following Chainfire
If you want to unroot for some reason :
From stock rom and root by Chainfire method all you need to do : Triangle Away app ,SuperSU / setting/ full unroot. Reboot into Recovery / Factory reset.
From custom rom : reflash stock image via Odin .reroot by CF auto root,reset counter with Triangle Away App,SuperSU/Setting/Full unroot . Recovery / Factory reset.
Can find stock firmware from here
Stock T889UVALJ1 & T889UVALK8 (Post 51) http://forum.xda-developers.com/show....php?t=1969551 ( Thank , TeshXX)
Stock + root http://forum.xda-developers.com/show....php?t=1975560 ( Thank , Mr.Robinson )
Tried a different stock firmware 4.1.2 T889 and now wont recognize T-mobile. Anyone have a link to the exact T889 stock firmware that I can just odin-install
Then triangle away/supersu reset and get OTA?
Really would like to get this working. Any help is greatly appreciated.
Try Mr Robinson,
http://forum.xda-developers.com/showthread.php?t=1975560
Sent from my SGH-T889 using xda app-developers app

Stock 4.4.2 Bootloader?

Wanting to drop stock(latest) back onto my phone as the person buying it wants that. I want to say I remember reading I needed a newer bootloader for 4.4.2. I got my device on launch and got tired of waiting and went to CM11.
What if anything other than clearing data/cache and flashing the stock deodexed/rooted ROM would I need to do? If there is a bootloader, is it a separate odin file? or flashable .zip?
muqali said:
Wanting to drop stock(latest) back onto my phone as the person buying it wants that. I want to say I remember reading I needed a newer bootloader for 4.4.2. I got my device on launch and got tired of waiting and went to CM11.
What if anything other than clearing data/cache and flashing the stock deodexed/rooted ROM would I need to do? If there is a bootloader, is it a separate odin file? or flashable .zip?
Click to expand...
Click to collapse
If you're on 4.3 still you will have to Odin a stock 4.3 firmware on to the phone. You can not have a custom recovery on the phone so the Odin way will also replace the custom recovery with stock recovery. Then once your phone is stock, you can then take the update to 4.4.2
If I'm not mistaken, you should download the 4.4.2 fw and Odin that on you phone as well. Even though you are Odining your new fw, the phone must be fully stock or that update will still fail.
Eric214 said:
If you're on 4.3 still you will have to Odin a stock 4.3 firmware on to the phone. You can not have a custom recovery on the phone so the Odin way will also replace the custom recovery with stock recovery. Then once your phone is stock, you can then take the update to 4.4.2
If I'm not mistaken, you should download the 4.4.2 fw and Odin that on you phone as well. Even though you are Odining your new fw, the phone must be fully stock or that update will still fail.
Click to expand...
Click to collapse
Well I was on 4.3 stock then went to Cyanogen 4.4.2. I've now got the deodexed/rooted stock 4.4.2 from the forum here and was able to boot it using leankernel. It works and the buyer is satisfied with it. He know how to flash updated ROMs so he can change later anyway. Thanks for the response though, I was thinking noone was gonna answer.
re: latest stock rom
muqali said:
Wanting to drop stock(latest) back onto my phone as the person buying it wants that. I want to say I remember reading I needed a newer bootloader for 4.4.2. I got my device on launch and got tired of waiting and went to CM11.
What if anything other than clearing data/cache and flashing the stock deodexed/rooted ROM would I need to do? If there is a bootloader, is it a separate odin file? or flashable .zip?
Click to expand...
Click to collapse
If you want the newest/latest official stock N900T KitKat firmware why not do the following:
You need to download and Odin flash the official stock KitKat N900T NE6 firmware.
Here is the direct fast download link for it:
http://www.androidfilehost.com/?fid=23501681358537528
The above zip file also contains Odin, CF-Autoroot and TWRP 2.7.0.1 recovery.
Be sure to go into recovery before Odin flashing NE6 and do a factory data reset
and a full wipe. Optional: Then Odin flash cf-autoroot and the TWRP 2.7.0.1.
If you want more information and or instructions here is the link:
http://forum.xda-developers.com/show...60&postcount=2
If you want the older official stock N900T 4.4.2 NB4 KitKat rom you can
download it from: http://tekunix.com/downloads/TMB-N900TUVUCNB4-20140305155920.zip
and Odin flash it instead of the stock NE6 official N900T firmware.
Both the older and newer official Kitkat stock roms come with the required bootloaders/baseband.
Good luck!
Misterjunky said:
If you want the newest/latest official stock N900T KitKat firmware why not do the following:
You need to download and Odin flash the official stock KitKat N900T NE6 firmware.
Here is the direct fast download link for it:
http://www.androidfilehost.com/?fid=23501681358537528
The above zip file also contains Odin, CF-Autoroot and TWRP 2.7.0.1 recovery.
Be sure to go into recovery before Odin flashing NE6 and do a factory data reset
and a full wipe. Optional: Then Odin flash cf-autoroot and the TWRP 2.7.0.1.
If you want more information and or instructions here is the link:
http://forum.xda-developers.com/show...60&postcount=2
If you want the older official stock N900T 4.4.2 NB4 KitKat rom you can
download it from: http://tekunix.com/downloads/TMB-N900TUVUCNB4-20140305155920.zip
and Odin flash it instead of the stock NE6 official N900T firmware.
Both the older and newer official Kitkat stock roms come with the required bootloaders/baseband.
Good luck!
Click to expand...
Click to collapse
So clear data/factory reset and clear cache in recovery. Reboot into download and flash NE6, then cf-autoroot, then TWRP? I didn't see you say exactly when to flash NE6.

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

[Q] Help with root

I have followed these instructions but I get stuck in a bootloop at 3:50 https://www.youtube.com/watch?v=k2oOvf5tOCY
Can anyone help me get past that?
KingKobra813 said:
I have followed these instructions but I get stuck in a bootloop at 3:50 https://www.youtube.com/watch?v=k2oOvf5tOCY
Can anyone help me get past that?
Click to expand...
Click to collapse
Yes wipe your storage n youll. Be good to go
pbedard said:
Yes wipe your storage n youll. Be good to go
Click to expand...
Click to collapse
I wiped my internal storage and I'm still getting stuck in at the same part. Do I need to wipe my external storage as well?
Bad download or wrong file? I think you should start over with fresh downloads, downloaded from your PC, not phone. Verify md5 checksum on the stock tar. Check your Samsung driver version as well.
http://forum.xda-developers.com/showthread.php?p=56853325
Download the CF Auto-Root specific to your device as well.
If you think your sdcard is suspect, just remove it or format it. Follow the usual advice: try another USB cable on the rear of PC (USB 2.0). The original Note 4 USB cable works for me.
BTW, if you're trying to get to lollipop, don't root until you take the OTA update.
samep said:
Bad download or wrong file? I think you should start over with fresh downloads, downloaded from your PC, not phone. Verify md5 checksum on the stock tar. Check your Samsung driver version as well.
http://forum.xda-developers.com/showthread.php?p=56853325
Download the CF Auto-Root specific to your device as well.
If you think your sdcard is suspect, just remove it or format it. Follow the usual advice: try another USB cable on the rear of PC (USB 2.0). The original Note 4 USB cable works for me.
BTW, if you're trying to get to lollipop, don't root until you take the OTA update.
Click to expand...
Click to collapse
Thank you. I will try that.
KingKobra813 said:
Thank you. I will try that.
Click to expand...
Click to collapse
Forgot to mention that Flashify has become a trusted source, to me and maybe others here. You can find it on Google Play and it will download TWRP, I recommend the non-zip latest one. Flashify will also automatically prompt you to install it from where it just downloaded it and checks its integrity. Since TWRP updates frequently, could be a manual step saver.
samep said:
Bad download or wrong file? I think you should start over with fresh downloads, downloaded from your PC, not phone. Verify md5 checksum on the stock tar. Check your Samsung driver version as well.
http://forum.xda-developers.com/showthread.php?p=56853325
Download the CF Auto-Root specific to your device as well.
If you think your sdcard is suspect, just remove it or format it. Follow the usual advice: try another USB cable on the rear of PC (USB 2.0). The original Note 4 USB cable works for me.
BTW, if you're trying to get to lollipop, don't root until you take the OTA update.
Click to expand...
Click to collapse
So I used a totally different computer and new cable and I'm still getting stuck at the exact same place. Everything on ODIN said it worked but my phone just bootloops.
1) Could you tell me what is your goal, please? Example: root stock, flash custom touchwiz or CM12 ROM. If touchwiz, are you referring to NIE, NK2, OB7?
2) Are you starting with a factory reset then stock tar?
There are alternate methods but knowing your goal could simplify the process or warrant starting over with NIE stock tar. For example, you could simply Odin TWRP recovery and then flash a rooted ROM zip or SuperSU zip in recovery. Another example: I and at least one other user trying to get to the OTA for 5.0.1 (OB7), had to Odin NIE stock tar and take two OTA updates to get lollipop.
http://download.chainfire.eu/supersu
This is a recovery flash that uses custom recovery to root; same developer, different approach. (For rooting stock. If a different ROM is your goal, it most likely includes this zip in its flash zip in a folder labeled supersu.)
Using the alternative methods, you'd skip Odin if CF Auto Root but still have to Odin latest TWRP.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
samep said:
1) Could you tell me what is your goal, please? Example: root stock, flash custom touchwiz or CM12 ROM. If touchwiz, are you referring to NIE, NK2, OB7?
2) Are you starting with a factory reset then stock tar?
There are alternate methods but knowing your goal could simplify the process or warrant starting over with NIE stock tar. For example, you could simply Odin TWRP recovery and then flash a rooted ROM zip or SuperSU zip in recovery. Another example: I and at least one other user trying to get to the OTA for 5.0.1 (OB7), had to Odin NIE stock tar and take two OTA updates to get lollipop.
http://download.chainfire.eu/supersu
This is a recovery flash that uses custom recovery to root; same developer, different approach. (For rooting stock. If a different ROM is your goal, it most likely includes this zip in its flash zip in a folder labeled supersu.)
Using the alternative methods, you'd skip Odin if CF Auto Root but still have to Odin latest TWRP.
http://www.techerrata.com/file/twrp2/trltespr/openrecovery-twrp-2.8.5.0-trltespr.img.tar
Click to expand...
Click to collapse
1)My goal is to just root stock
2) I'm starting with a factory reset. I don't really know what you mean by stock tar.
What I tried was. I followed the instructions to root my phone. It got stuck in a bootloop. I did a factory reset. Set up my phone. Tried to root again using ODIN. Still getting stuck in bootloop. Then I did another factory reset and I'm just stock but the strange thing is I have Super SU installed and all the bloatware I originally removed is gone but rootchecker says I don't have root. And strangely my WiFi won't work.
KingKobra813 said:
1)My goal is to just root stock
2) I'm starting with a factory reset. I don't really know what you mean by stock tar.
What I tried was. I followed the instructions to root my phone. It got stuck in a bootloop. I did a factory reset. Set up my phone. Tried to root again using ODIN. Still getting stuck in bootloop. Then I did another factory reset and I'm just stock but the strange thing is I have Super SU installed and all the bloatware I originally removed is gone but rootchecker says I don't have root. And strangely my WiFi won't work.
Click to expand...
Click to collapse
Root stock helps me some with your goal. The alternative method of Odin TWRP them flash the zip file in the previous post would be an option.
The time that you actually root is key to your goal and suggesting steps. If you want rooted lollipop, currently the only option is take OB7 OTA (over the air) update.
Furthermore, you're having Wi-Fi issues and can't root is an indication you need to flash stock firmware in Odin rather than just root. It's always a good idea to do this if you start having problems with booting after a flash or something is not working.
There's already a thread on getting to lollipop with OTA and rooting.
http://forum.xda-developers.com/showthread.php?p=59235259
You could follow that but I'd suggest adding an extra OTA and starting over at NIE stock tar since NK2 is giving you problems. The three alpha-numeric designations for firmware I gave indicate the original stock tar starting at NIE and then NK2 (both are KitKat ROMs). The initial lollipop ROM is OB7. The stock tars available are NIE and NK2 found below.
http://forum.xda-developers.com/showthread.php?p=56853325
samep said:
Root stock helps me some with your goal. The alternative method of Odin TWRP them flash the zip file in the previous post would be an option.
The time that you actually root is key to your goal and suggesting steps. If you want rooted lollipop, currently the only option is take OB7 OTA (over the air) update.
Furthermore, you're having Wi-Fi issues and can't root is an indication you need to flash stock firmware in Odin rather than just root. It's always a good idea to do this if you start having problems with booting after a flash or something is not working.
There's already a thread on getting to lollipop with OTA and rooting.
http://forum.xda-developers.com/showthread.php?p=59235259
You could follow that but I'd suggest adding an extra OTA and starting over at NIE stock tar since NK2 is giving you problems. The three alpha-numeric designations for firmware I gave indicate the original stock tar starting at NIE and then NK2 (both are KitKat ROMs). The initial lollipop ROM is OB7. The stock tars available are NIE and NK2 found below.
http://forum.xda-developers.com/showthread.php?p=56853325
Click to expand...
Click to collapse
I would lIke to stay on kitkat. What steps would you recommend for me to root my phone?
KingKobra813 said:
I would lIke to stay on kitkat. What steps would you recommend for me to root my phone?
Click to expand...
Click to collapse
1)Download the stock tar NK2, TWRP tar for Odin and supersu zip.
2)Factory reset.
3)Power down. Battery pull is an option. Go to download mode.
4)Odin stock tar; be patient waiting for COM and tar to verify before start (one minute or 2).
5)Boot and setup.
6)Power down.
7)Odin TWRP recovery tar
8)In recovery, flash the supersu zip.
9)On first boot, follow any prompts to update su binary that SuperSu prompts you for but do not select TRWP as the option but "Normal" when asked.
10)You should be rooted.
Of course you could also follow the instructions in the stock tar thread I pointed you too. The above is the alternative method.
samep said:
1)Download the stock tar NK2, TWRP tar for Odin and supersu zip.
2)Factory reset.
3)Power down. Battery pull is an option. Go to download mode.
4)Odin stock tar; be patient waiting for COM and tar to verify before start (one minute or 2).
5)Boot and setup.
6)Power down.
7)Odin TWRP recovery tar
8)In recovery, flash the supersu zip.
9)On first boot, follow any prompts to update su binary that SuperSu prompts you for but do not select TRWP as the option but "Normal" when asked.
10)You should be rooted.
Of course you could also follow the instructions in the stock tar thread I pointed you too. The above is the alternative method.
Click to expand...
Click to collapse
I'll give that a try.
Is this the correct stock tar nk2 - https://www.androidfilehost.com/?fid=95853297432265112
KingKobra813 said:
I'll give that a try.
Is this the correct stock tar nk2 - https://www.androidfilehost.com/?fid=95853297432265112
Click to expand...
Click to collapse
Correct.
Refer to post 8 for the links to alternate rooting method files if you don't already have them.
Best wishes for success. No luck to it.

Categories

Resources