I'm trying to flash Clockwork Mod onto a friend's TMO S3 with Odin. I was able to do this successfully with my TMO S3, both are running UVALH2.
Odin says the flash was successful, I restart the phone and try to boot into the custom recovery but it keeps taking me to the stock recovery. I tried a few more times with the same results.
Am I missing something?
Try the no tripping the flash counter method found in the stickies found in the dev section.
You should be able to get around your problem with this method.
Sent from my SGH-T999 using xda premium
kpizzle said:
I'm trying to flash Clockwork Mod onto a friend's TMO S3 with Odin. I was able to do this successfully with my TMO S3, both are running UVALH2.
Odin says the flash was successful, I restart the phone and try to boot into the custom recovery but it keeps taking me to the stock recovery. I tried a few more times with the same results.
Am I missing something?
Click to expand...
Click to collapse
The UVALH2 update includes two files that will overwrite recovery every reboot
You can fix this issue by renaming the following files using root explorer
Rename:
/system/recovery-from-boot.p to /system/recovery-from-boot.p.bak
and
/system/etc/install-recovery.sh to /system/etc/install-recovery.sh.bak
Once you've done that, reflash CWM through ROM Manager and recovery will stick
ingenious247 said:
The UVALH2 update includes two files that will overwrite recovery every reboot
You can fix this issue by renaming the following files using root explorer
Rename:
/system/recovery-from-boot.p to /system/recovery-from-boot.p.bak
and
/system/etc/install-recovery.sh to /system/etc/install-recovery.sh.bak
Once you've done that, reflash CWM through ROM Manager and recovery will stick
Click to expand...
Click to collapse
You are the man!!!
there's a little "thanks" button on my post.. feel free to click it
and no problem, glad to help!
ingenious247 said:
The UVALH2 update includes two files that will overwrite recovery every reboot
You can fix this issue by renaming the following files using root explorer
Rename:
/system/recovery-from-boot.p to /system/recovery-from-boot.p.bak
and
/system/etc/install-recovery.sh to /system/etc/install-recovery.sh.bak
Once you've done that, reflash CWM through ROM Manager and recovery will stick
Click to expand...
Click to collapse
So I just realized something. I can't even attain root access, how can I edit these files?
Can flash mrRobinson's LH2 w/root and you will have full LH2 stock with root. It is an Odin package and only flashes /system partition so no /data loss.
kpizzle said:
So I just realized something. I can't even attain root access, how can I edit these files?
Click to expand...
Click to collapse
Flash CWM through Odin, but turn off the auto reboot in Odin
That way it won't overwrite it
Then power down when it's done, and boot into recovery, Flash Superuser
Will i still be able to receive JB OTA update when the time comes, if i rename these two files and flash CWM through ROM manager?
arthaz28 said:
Will i still be able to receive JB OTA update when the time comes, if i rename these two files and flash CWM through ROM manager?
Click to expand...
Click to collapse
No, you cannot receive OTA updates unless you are on stock recovery.
So you would have to Odin back to stock before accepting the update, which is simple enough.
Or just wait for someone to take the update and make a flashable zip file which will happen pretty quickly once the OTA comes out
ingenious247 said:
No, you cannot receive OTA updates unless you are on stock recovery.
So you would have to Odin back to stock before accepting the update, which is simple enough.
Or just wait for someone to take the update and make a flashable zip file which will happen pretty quickly once the OTA comes out
Click to expand...
Click to collapse
You don't need stock recovery for any reason at all. Not anymore.
I never said you needed it. I was answering the question that was asked.
And if you don't want to flash a modified version of a stock ROM, then yes, you do need stock recovery. Some of us don't like deodexed ROMs and care to choose what we debloat.
ingenious247 said:
I never said you needed it. I was answering the question that was asked.
And if you don't want to flash a modified version of a stock ROM, then yes, you do need stock recovery. Some of us don't like deodexed ROMs and care to choose what we debloat.
Click to expand...
Click to collapse
Thank you sir!
After I was rooted, I created a backup using CWM. So, if the update comes out, I can just flash my backup stock ROM again using CWM rand I should be able to receive the OTA update, right?
(sorry I am a noob and still learning about this whole rooting, custom ROM, etc stuff)
arthaz28 said:
Thank you sir!
After I was rooted, I created a backup using CWM. So, if the update comes out, I can just flash my backup stock ROM again using CWM rand I should be able to receive the OTA update, right?
(sorry I am a noob and still learning about this whole rooting, custom ROM, etc stuff)
Click to expand...
Click to collapse
No, you would have to Odin back to stock which would overwrite CWM with stock recovery. If you're not familiar with Odin read up on it, it's really easy to use. Just make sure you get it from the correct thread for your phone model and you'll be fine.
Sent from my SGH-T999 using xda premium
Related
[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?
I just got the OTA ICS update sent to my phone. As of now it is rooted but on stock rom. My question is I have team Rogue custom recovery. Is that the same as clockwork mod and do I need to restore it back to stock recovery before I accept the ota update? thanks!
You can use sfhub's auto root tool to check if your ROM is compliant. If it isn't, it will fail the update.
http://forum.xda-developers.com/showthread.php?t=1342728
Why don't you just use sfhub's one click FF18 with root. You need to be on stock el29 to accept the update. If not it will fail.
Sent from my SPH-D710 using xda app-developers app
Stuck on triangle
cphil99 said:
I just got the OTA ICS update sent to my phone. As of now it is rooted but on stock rom. My question is I have team Rogue custom recovery. Is that the same as clockwork mod and do I need to restore it back to stock recovery before I accept the ota update? thanks!
Click to expand...
Click to collapse
Thanks for the help. I was able to revert back to stock recovery but now when trying to update either ota or manual it gets stuck on the triangle with the android a few seconds into the update. I've tried renaming the file to "update" as instructed in the video and not renaming. Same result. Any suggestions guys?
cphil99 said:
Thanks for the help. I was able to revert back to stock recovery but now when trying to update either ota or manual it gets stuck on the triangle with the android a few seconds into the update. I've tried renaming the file to "update" as instructed in the video and not renaming. Same result. Any suggestions guys?
Click to expand...
Click to collapse
I'm having the same issue.
Edit: I got it. I installed it in the folder not the root of the sd card.
Sent from my SPH-D710 using xda app-developers app
cphil99 said:
Thanks for the help. I was able to revert back to stock recovery but now when trying to update either ota or manual it gets stuck on the triangle with the android a few seconds into the update. I've tried renaming the file to "update" as instructed in the video and not renaming. Same result. Any suggestions guys?
Click to expand...
Click to collapse
If you get the the triangle, press the "Menu" capacitative button and it will show the log.
Most likely you modified or removed some ROM file or your update.zip is corrupt.
Usually folks remove some bloat way back when and forgot they did it.
If you are still rooted, you could run Auto Root Option E, OTA Compliance Check EL29->FF18 and it will tell you everything that will cause the OTA update to fail.
As an aside, the previous posters are correct and it is probably easier if you just use the FF18 ODIN OneClick.
http://forum.xda-developers.com/showthread.php?t=1721229
The Official FF18 OTA will not run under CWM or CWM-Rogue because when it goes to verify the integrity of the kernel, it will find it is different than what it was expecting.
I have a rooted FF18 OTA that will install from CWM if you want to go that route:
http://forum.xda-developers.com/showthread.php?t=1771799
I got it!
sfhub said:
If you get the the triangle, press the "Menu" capacitative button and it will show the log.
Most likely you modified or removed some ROM file or your update.zip is corrupt.
Usually folks remove some bloat way back when and forgot they did it.
If you are still rooted, you could run Auto Root Option E, OTA Compliance Check EL29->FF18 and it will tell you everything that will cause the OTA update to fail.
As an aside, the previous posters are correct and it is probably easier if you just use the FF18 ODIN OneClick.
http://forum.xda-developers.com/showthread.php?t=1721229
The Official FF18 OTA will not run under CWM or CWM-Rogue because when it goes to verify the integrity of the kernel, it will find it is different than what it was expecting.
I have a rooted FF18 OTA that will install from CWM if you want to go that route:
http://forum.xda-developers.com/showthread.php?t=1771799
Click to expand...
Click to collapse
That did it! I just downloaded and ran the new Odin file and it worked like a charm with no loss of data. Thank you so much for you help!
I wish to return to a rooted stock JB ROM from CM10.1 . CM10.1 is too buggy for me, and CM10 had one bluetooth bug in the final release that was kind of a game killer for me. I'd like to go back to stock JB but keep my custom recovery. The only files I've found for stock jellybean are full stock in that they'll flash over my recovery as well as my system. Does anyone know where I can find a root stock image that will let me flash just the system and keep my recovery like any other rom, so that I can flash back to CM10.1 when it is more stable. PS I am also on Linux and do not regularly have access to a windows machine so I do not have access to Odin, or Kies.
after you flash to stock just flash a recovery, that's what i've done.
also, this is the wrong section and you should search first.
sent from my I747
I searched and found only "One click" stock roms, and the "Fully Stock" roms. Neither of which solve my problem. Did you even read the portion of my post where I say I don't have access to Odin, or Kies or any of that? My only option for flashing is CWM. And I'm not sure how well overwritting CWM while CWM is flashing would work, but I don't think it would go well.
cehf said:
after you flash to stock just flash a recovery, that's what i've done.
also, this is the wrong section and you should search first.
sent from my I747
Click to expand...
Click to collapse
find a cwm flashable zip of a stock rom. it doesn't need to be a current version. flash that. then find the cwm flashable ota zips and flash those. you've retained root, and cwm. i have done this process as well.
i'd link you to the threads you need but i'm on my phone and it's difficult to find this way.
edit: one of the otas is here. i haven't found anything about updating to jelly bean, though. i know there's a tutorial somewhere about making cwm flashable zips, i might try making one for you after i get my sister to sleep.
sent from my I747
go to this link:
http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1
find the appropriate version for your carrier and flash via your recovery. its pre-rooted and cwm/twrp flashable, no odin or PC needed.
Russ77 said:
go to this link:
http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1
find the appropriate version for your carrier and flash via your recovery. its pre-rooted and cwm/twrp flashable, no odin or PC needed.
Click to expand...
Click to collapse
i don't see anything about cwm, only odin?
op, here is a full stock rom. here is the ota that comes after.
sent from my I747
When you're back to rooted TW, flash the recovery you want with Mobile ODIN.
Sent from my SGH-I747M
cehf said:
i don't see anything about cwm, only odin?
op, here is a full stock rom. here is the ota that comes after.
sent from my I747
Click to expand...
Click to collapse
my mistake. OP, grab mobile-odin and do that since you're already rooted
I have the Clockword recovery and CM 10.1 installed on my Sprint Galaxy S3 running on PagePlus
I would like to flash a Touchwiz rom. Which one can I flash using the Clockword Recovery (lightweight)?
Why is MD4 not flashable using Clockwork?
Thanks.
The official update is NOT flashable.using any custom recovery, custom meaning anything other than stock recovery.
And you can flash any Touchwiz rom with CWM recovery, as the MD4 update is not a ROM. OTAs are not full ROMs on their own, they are collection of files that patch the already existing apps to the most recent versions.
If you want to update to MD4, you simply need flash a custom ROM that is based on MD4 (check the thread titles and OPs), or you can flash freezas stock rooted MD4 ROM, not the update.
CNexus said:
The official update is NOT flashable.using any custom recovery, custom meaning anything other than stock recovery.
And you can flash any Touchwiz rom with CWM recovery, as the MD4 update is not a ROM. OTAs are not full ROMs on their own, they are collection of files that patch the already existing apps to the most recent versions.
If you want to update to MD4, you simply need flash a custom ROM that is based on MD4 (check the thread titles and OPs), or you can flash freezas stock rooted MD4 ROM, not the update.
Click to expand...
Click to collapse
Thanks. That makes a few things clear.
Could you provide any suggestions on a Touchwiz ROM as close to the stock as possible, but preserves root of-course and does not require me to change my recovery. Thanks a lot. (I see you mentioned freezas and I'll try to find it, but just making sure).
kniwor said:
Thanks. That makes a few things clear.
Could you provide any suggestions on a Touchwiz ROM as close to the stock as possible, but preserves root of-course and does not require me to change my recovery. Thanks a lot. (I see you mentioned freezas and I'll try to find it, but just making sure).
Click to expand...
Click to collapse
Right here
http://forum.xda-developers.com/showthread.php?t=1910947
CNexus said:
Right here
http://forum.xda-developers.com/showthread.php?t=1910947
Click to expand...
Click to collapse
Just to be doubly sure, here is what I do:
1) Download the file "MD4_update_FULL_Odex.zip" - The first link in the thread.
2) Place it on SDCard
3) Flash zip from SDCard using the CWM Based Recovery v5.5.0.4
The post in that thread confused me. And I did not want to mess up anything. I especially don't want to update the radio and firmware etc because I've flashed the phone to PagePlus and I'm not sure what that'll do to it.
Flashing Cyanogen any number of times in the past has had no effect.
Thanks agian.
kniwor said:
Just to be doubly sure, here is what I do:
1) Download the file "MD4_update_FULL_Odex.zip" - The first link in the thread.
2) Place it on SDCard
3) Flash zip from SDCard using the CWM Based Recovery v5.5.0.4
The post in that thread confused me. And I did not want to mess up anything. I especially don't want to update the radio and firmware etc because I've flashed the phone to PagePlus and I'm not sure what that'll do to it.
Flashing Cyanogen any number of times in the past has had no effect.
Thanks agian.
Click to expand...
Click to collapse
Yes, that is correct
However, I would suggest to take this opportunity to update your recovery, as you are a full revision behind
The latest CWM can be found here: http://forum.xda-developers.com/showthread.php?t=2151476
Download that recovery zip, boot into recovery, flash the recovery.zip, then go to advanced > reboot recovery, wait a bit for.it to reboot, and then flash the MD4odexed.zip
CNexus said:
Yes, that is correct
However, I would suggest to take this opportunity to update your recovery, as you are a full revision behind
The latest CWM can be found here: http://forum.xda-developers.com/showthread.php?t=2151476
Download that recovery zip, boot into recovery, flash the recovery.zip, then go to advanced > reboot recovery, wait a bit for.it to reboot, and then flash the MD4odexed.zip
Click to expand...
Click to collapse
Git it! Done, updated and everything working perfectly!
Thanks a ton.
kniwor said:
Git it! Done, updated and everything working perfectly!
Thanks a ton.
Click to expand...
Click to collapse
No problem! Dont be afraid to ask or PM me if any more questions/concerns
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