I currently have my bootloader unlocked, S-OFF, TWRP recovery, and rooted stock verizon software (Most recent mini-update pushed from VZW around Thanksgiving). My question is whether my current configuration will allow me to accept the new 4.3 OTA update from verizon when it starts to roll out. Is custom recovery going to be a problem? I haven't messed with the stock software, other than adding superuser app. Thanks.
For all the other updates, stock recovery was necessary. I wouldn't see why the 4.3 update would be any different.
I still suggest waiting until the devs take the update and make a flashable Rom from it.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
kdj67f said:
For all the other updates, stock recovery was necessary. I wouldn't see why the 4.3 update would be any different.
I still suggest waiting until the devs take the update and make a flashable Rom from it.
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is it possible to flash or adb stock recovery back?
Yes, the stock recovery and files are posted here. I have reflashed the stock recovery and ota'd myself. As easy as flashing a custom recovery. You might want to read all the other ota threads here...
Sent from my HTC6500LVW using XDA Premium 4 mobile app
flyinfool2 said:
Is it possible to flash or adb stock recovery back?
Click to expand...
Click to collapse
yes, very.
search you'd find this thread.. http://forum.xda-developers.com/showthread.php?t=2485319
there you find this:
"
Arrow 1.10.605.10 Stock [Firmware/Radio] [Kernel] zips
Full Firmware, Boot.img, and Radio updates
Ok, so you now have the latest stock software.
You likely want to have the firmware and radios updated that came along with the OTA.
If that is the case, I have supplied the firmware.zip here that will update the firmware and radios to the latest version.
How to flash the Full firmware/radio zip:
Separate Radios, Recoveries, and Kernels are also available below,
if you are on a custom rom or don't need/want the full firmware!
Download the appropriate firmware version for your stock based rom:
1.10.605.10 firmware.zip
1.10.605.15 firmware.zip
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip
It will say that the update did not finish, to flush again, repeat the above step:
fastboot flash zip firmware.zip
Quote:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
If you have any questions or issues, let me know.
Stock m7vzw
Kernels, Radios, Recoveries!
Kernel Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
****In case anyone wants just the stock kernel and modules:
1.10.605.10 stock kernel
1.10.605.15 Insecure stock kernel - R/W enabled
Flash in Recovery, wipe cache and dalvik, reboot.
Radio Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
I went ahead and made these baseband zips as well.
Basebands/Fastboot Flashable:
These radio.zips must be flashed the same way as the firmware zip at the top of this post.
With the exception that it will not need to be reflushed/reflashed a second time during the process."
http://www.androidfilehost.com/?fid=23212708291682230 - flash in recovery
Great info, Thanks!
flyinfool2 said:
I currently have my bootloader unlocked, S-OFF, TWRP recovery, and rooted stock verizon software (Most recent mini-update pushed from VZW around Thanksgiving). My question is whether my current configuration will allow me to accept the new 4.3 OTA update from verizon when it starts to roll out. Is custom recovery going to be a problem? I haven't messed with the stock software, other than adding superuser app. Thanks.
Click to expand...
Click to collapse
You have to have stock recovery to OTA. But can I ask why you'd want to OTA anyway? Devs will have a rooted stock zip in no time after the update is pushed. There is literally no reason to OTA. A lot of ppl, for whatever the reason, think it's important to have the official OTA. If you want stock unrooted backups I get that. I do that sometimes in case of emergencies. Other than that you really don't need to OTA. You can reflash stock recovery easy enough and OTA if you want but I wouldn't. Since you have an unlocked bootloader and all then at most you would have to flash superuser again but the general rule is never OTA.
---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------
andybones said:
yes, very.
search you'd find this thread.. http://forum.xda-developers.com/showthread.php?t=2485319
there you find this:
"
Arrow 1.10.605.10 Stock [Firmware/Radio] [Kernel] zips
Full Firmware, Boot.img, and Radio updates
Ok, so you now have the latest stock software.
You likely want to have the firmware and radios updated that came along with the OTA.
If that is the case, I have supplied the firmware.zip here that will update the firmware and radios to the latest version.
How to flash the Full firmware/radio zip:
Separate Radios, Recoveries, and Kernels are also available below,
if you are on a custom rom or don't need/want the full firmware!
Download the appropriate firmware version for your stock based rom:
1.10.605.10 firmware.zip
1.10.605.15 firmware.zip
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip firmware.zip
It will say that the update did not finish, to flush again, repeat the above step:
fastboot flash zip firmware.zip
Quote:
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot!
The bar will only fill up to 100% once you type the following command:
fastboot reboot-bootloader (this reboots the device to bootloader)
That's it, you're done. You can now reboot and will be running the latest firmware and radios.
If you have any questions or issues, let me know.
Stock m7vzw
Kernels, Radios, Recoveries!
Kernel Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
****In case anyone wants just the stock kernel and modules:
1.10.605.10 stock kernel
1.10.605.15 Insecure stock kernel - R/W enabled
Flash in Recovery, wipe cache and dalvik, reboot.
Radio Only!!!__>>>>>>
(included in the above firmware zips as well, if you flash those, you do not need this too)
I went ahead and made these baseband zips as well.
Basebands/Fastboot Flashable:
These radio.zips must be flashed the same way as the firmware zip at the top of this post.
With the exception that it will not need to be reflushed/reflashed a second time during the process."
http://www.androidfilehost.com/?fid=23212708291682230 - flash in recovery
Click to expand...
Click to collapse
Well damn andy. Dropped the knowledge bomb on him
Yeah it's not worth OTA'ng, especially given the experience vzw S4 owners had with getting their root exploits and such closed...
Flashable OTA update question
So my One is unlocked and S-off. I manually updated to firmware version .15, however, my ROM is still version .10. (I could not download the version .15 ROM version as it was taking way too long) I keep getting the constant nag about the software update. I want to stay current, but dont want to lose ROOT or worse.
First, how do you use a flashable rom file to update your current rom? I dont what to have to backup and flash a new rom and restore all my settings everytime if I can avoid it. Is there a way to just update like what the OTA does?
Here was my thought. I would make a backup and clean install the current version (.15) of a custom, stock ROM. This would prevent future OTA's correct? Then, I would just update with flash-able files as they are released to keep my ROM up to date and ROOT privileges, etc safe?
Or would it be possible to update my current .10 ROM to .15, disable all OTA's and then flash updates as they are released?
BreakingVZW said:
You have to have stock recovery to OTA. But can I ask why you'd want to OTA anyway? Devs will have a rooted stock zip in no time after the update is pushed. There is literally no reason to OTA. A lot of ppl, for whatever the reason, think it's important to have the official OTA. If you want stock unrooted backups I get that. I do that sometimes in case of emergencies. Other than that you really don't need to OTA. You can reflash stock recovery easy enough and OTA if you want but I wouldn't. Since you have an unlocked bootloader and all then at most you would have to flash superuser again but the general rule is never OTA.
---------- Post added at 09:25 AM ---------- Previous post was at 09:24 AM ----------
Click to expand...
Click to collapse
This is my wifes phone, so she is not concerned with having any custom operating ROM. For me however, I have always been a hacker at heart, and I love to run different ROMS on my own phone. For her phone, I just want the ability to run the most recent stock software, with root, so that I can make backups and freeze unnecessary apps to my liking. If a rooted stock zip is just around the corner, then I see no need to take the OTA update as you stated. Thanks for the insight. I just didn't realize that I could get the same result (an updated stock, rooted update) without taking the OTA. I appreciate the help! :good:
What can I do in the meantime to prevent my wife from accidentally accepting the OTA (it just began pushing on her phone)? I know the update wont take without stock recovery installed, but is there an easy way to prevent the repeated download and prompt for install?
EDIT: I found another thread with a flashable file to stop OTA...thanks all
For whatever reason I can't get the OTA to apply. It gets about 25 to 30% of the way through the installation and then gives me the red Triangle/Exclamation point. I first tried after flashing back to the 1.10.605.15 recovery and after that failed I flashed the full 1.10.605.15 firmware with the same result. Any ideas?
wpsantennas said:
For whatever reason I can't get the OTA to apply. It gets about 25 to 30% of the way through the installation and then gives me the red Triangle/Exclamation point. I first tried after flashing back to the 1.10.605.15 recovery and after that failed I flashed the full 1.10.605.15 firmware with the same result. Any ideas?
Click to expand...
Click to collapse
I have that. Haven't figured it out yet either. I did the stock recovery too. s-off and unlocked.
Had the same exact problem as WPSantennas and paganhobbit. Endded up using this thread http://forum.xda-developers.com/showthread.php?t=2475216 to return to S-On, Locked Bootloader at 1.10.605.8 (For mine to work right on this tutorial I had to skip the 2nd 'fastboot oem rebootRUU' after failing for it work.) I think the latest OTA doesn't really like if you have modified or deleted their stock bloat apps for some reason. IMO, The update is not impressive at all and I'd advise to stay at 4.2.2 but this is may be good to do if you want to bump to KitKat in the future. Hope this helps!
EDIT: Here's the link to the RUU I used since the link on the original was dead: http://www.android-edge.com/Login/uploads/PN017IMG_M7_1.10.605.8.zip
I ended up RUU-ing as well, going back to .10. Then it updated to .15 and the 4.3 update without a problem. I didn't re-lock or go S-On to do this. I had tried three different "official stock recovery" files I found, but 4.3 wouldn't update successfully with any of them.
A new problem is it doesn't seem to want to remember my WiFi connections for some reason now. If I go out of range and come back, I have to re-enter the WPA2 key all over again. I suspect it's Verizon's ploy to make me use more data
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?
Trying to update firmware to 1.10.605.10 after S-OFF.
Changing recovery to stock, then taking OTA errors out for me using the stock ROM.
Thanks!
Yeah ...its been posted here
http://forum.xda-developers.com/showthread.php?t=2465774
Sent from my Nexus 7 using Tapatalk 4
I tried flashing the modified zip, as well as the original, with twrp recovery and both received an error.
The modified zip gave this error -
"Error flashing zip '/sdcard/modified_OTAPkg.zip' Updating partition details..."
The rom I am using is the VZW Stock Rooted deodex, should I be using something different?
Wozzie said:
The rom I am using is the VZW Stock Rooted deodex, should I be using something different?
Click to expand...
Click to collapse
The update doesn't work with a deodexed ROM. It also likely doesn't work if you've removed some of Verizon's bloat software on the stock odexed ROM.
@CNexus wants to make an updated flashable zip for rooted users, as well as a fully flashable ROM (if I am reading that right), but needs the right framework files.
Both the modified zips, and the modified recovery won't work for me for some reason.
The modified zip just errors out in TWRP.
If I try the stock recovery method -
Fastboot signed stock recovery
Take the OTA w stock ROM
Errors out
or
Flash Andy's odex stock ROM
Fastboot signed stock recovery
Take OTA
Updates firmware to .10
Fastboot TWRP, flash SU
Restore stock ROM from TWRP backup
Firmware is back to .08 now
Does restoring the stock ROM in TWRP downgrades my firmware to .08 again?
Confused :/
gzbrambila said:
Both the modified zips, and the modified recovery won't work for me for some reason.
The modified zip just errors out in TWRP.
If I try the stock recovery method -
Fastboot signed stock recovery
Take the OTA w stock ROM
Errors out
or
Flash Andy's odex stock ROM
Fastboot signed stock recovery
Take OTA
Updates firmware to .10
Fastboot TWRP, flash SU
Restore stock ROM from TWRP backup
Firmware is back to .08 now
Does restoring the stock ROM in TWRP downgrades my firmware to .08 again?
Confused :/
Click to expand...
Click to collapse
Restoring a backup generally completely wipes out the current software in place. If you flashed the odexed ROM, took the OTA with the stock recovery, then restored a backup of .08, then you lost the .10 update because it was on that installed ROM. You overwrote it.
If you want the update, which was so small and negligible that it's not really even important enough to take, then you have to flash the odexed ROM, take the update with the stock recovery, and stay on that ROM. That's the only way that works presently. No one has released a working odexed or deodexed ROM with the update included, nor is there a working flashable zip that doesn't require you to be on and stay on the stock odexed ROM.
IceDragon59 said:
Restoring a backup generally completely wipes out the current software in place. If you flashed the odexed ROM, took the OTA with the stock recovery, then restored a backup of .08, then you lost the .10 update because it was on that installed ROM. You overwrote it.
If you want the update, which was so small and negligible that it's not really even important enough to take, then you have to flash the odexed ROM, take the update with the stock recovery, and stay on that ROM. That's the only way that works presently. No one has released a working odexed or deodexed ROM with the update included, nor is there a working flashable zip that doesn't require you to be on and stay on the stock odexed ROM.
Click to expand...
Click to collapse
Thank you. That makes perfect sense now.
gzbrambila said:
Thank you. That makes perfect sense now.
Click to expand...
Click to collapse
Actually if you took the update while on stock recovery...the actual firmware portion did update and will stay updated regardless of what rom software version you are running. The update was both a software (.10) AND firmware update.
Sent from my Nexus 7 using Tapatalk 4
gzbrambila said:
Trying to update firmware to 1.10.605.10 after S-OFF.
Changing recovery to stock, then taking OTA errors out for me using the stock ROM.
Thanks!
Click to expand...
Click to collapse
As stated earlier the OTA doesn't play well with deodex ROMs. I figured out how to do this with no issue. Be warned as this will wipe your device. Download the decrypted RUU and boot into RUU mode and follow Zarboz's instuctions for installation. That will get you back to stock. What I did was:
relock bootloader for RUU flash
flash the RUU
OTA (don't set up your phone bc bootloader unlock will wipe it again )
unlocked bootloader again
installed custom recovery via fastboot
made unrooted stock nandroid
flash SuperSU
Also, once you have custom recovery installed you can pull the recovery_signed.img from the decrypted RUU zip and copy/paste it into fastboot directory and flash stock recovery at will for updates for your stock ROM. Tested that method and it works. I did it this way bc I was having the same issues with failed updates so I said screw it and went full on RUU
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
I recently unlocked the bootloader of an HTC One (M8) running Kitkat, installed TWRP then flashed a .ZIP file to root the phone. Now Lollipop has been released there's an OTA available on the phone but I'm not able to update through it. I've seen different posts all over the place about how you have to just install the stock recovery or how you have to use an RUU or how you have to use a NANDroid backup so the opinions are quite conflicting.
I basically just want the phone to run the stock unrooted version of Android so I'm able to perform the official OTA updates to Lollipop so how do I go about this? Any help is greatly appreciated!
Charlular said:
I recently unlocked the bootloader of an HTC One (M8) running Kitkat, installed TWRP then flashed a .ZIP file to root the phone. Now Lollipop has been released there's an OTA available on the phone but I'm not able to update through it. I've seen different posts all over the place about how you have to just install the stock recovery or how you have to use an RUU or how you have to use a NANDroid backup so the opinions are quite conflicting.
I basically just want the phone to run the stock unrooted version of Android so I'm able to perform the official OTA updates to Lollipop so how do I go about this? Any help is greatly appreciated!
Click to expand...
Click to collapse
No need to unroot. You just need a stock recovery.
Charlular said:
I basically just want the phone to run the stock unrooted version of Android so I'm able to perform the official OTA updates to Lollipop so how do I go about this? Any help is greatly appreciated!
Click to expand...
Click to collapse
Let me try to clarify the confusion based on my experience with the Lollipop OTA update. First, you need to remember that, during the OTA update, the software checks for two things: 1) the version of the recovery; and 2) whether any system files has been modified (described in my earlier post).
As a result, you only need stock recovery (from 4.4.4 or 5.0.1) to initiate the OTA update (as mentioned by the other poster). If no system files were altered as a result of your root access, your OTA should finish without errors.
However, root itself and what people do after they have root access often mean some system files were altered. Hence, they need to use either RUU or TWRP backup to restore they all files back to the factory version.
Finally, as for RUU vs. TWRP:
The RUU or TWRP version must match that to your carrier version of M8. The RUU is the better option, but not available for all carrier versions. When RUU is not available, people rely on TWRP nandroid backup generated by other users.
Bottom line or my advice:
First do a TWRP backup before you start anything. If anything goes wrong, you can always revert back to the working status as it is now.
To begin, go back to stock recovery, and see if the OTA update will go through. If not, you will see red triangle. Then hold Vol + and tap power button once to see the error messages. See my post above. If you ran into the same error as I did, you'll know what to do (RUU or TWRP backup to return to stock).
ikeny said:
Let me try to clarify the confusion based on my experience with the Lollipop OTA update. First, you need to remember that, during the OTA update, the software checks for two things: 1) the version of the recovery; and 2) whether any system files has been modified (described in my earlier post).
As a result, you only need stock recovery from (4.4.4 or 5.0.1) to initiate the OTA update (as mentioned by the other poster). If no system files were altered as a result of your root access, your OTA should finish without errors.
However, root itself and what people do after they have root access often mean some system files were altered. Hence, they need to use either RUU or TWRP backup to restore they all files back to the factory version.
Finally, as for RUU vs. TWRP:
The RUU or TWRP version must match that to your carrier version of M8. The RUU is the better option, but not available for all carrier versions. When RUU is not available, people rely on TWRP backup generated by other users.
Bottom line or my advice:
First do a TWRP backup before you start anything. If anything goes wrong, you can always revert back to a work status as it is now.
To begin, go back to stock recovery, and see if the OTA update will go through. If not, you will see red triangle. Then hold Vol + and tap power button once to see the error messages. See my post above. If you ran into the same error as I did, you'll know what to do (RUU or TWRP backup to return to stock).
Click to expand...
Click to collapse
A very well-worded answer
I have rooted my Nexus 7 wifi 2012 tablet with TWRP
I don't want to keep un-rooting, applying ota updates then re-rooting my tablet. Is there an easy way. Maybe modified images i can use on a rooted tablet which i can install via the install option in twrp recovery loader.
I also notice that Nexus root tool kit has a ota sideload update option in the advanced menue.
So my question is where are the modifies ota update files if they exist as I don't want to keep un-rooting, rerooting each time to apply official ota updates. I have searched the net and can't find modifies ota updates?
My OTA failed due to root and modifications so I extracted system.img and boot.img from the 5.1 tarball and flashed them using Nexus Root Toolkit. Works well.
I'm going through the same issue - I want to keep running stock, but every time an OTA update comes in, it bugs me for an update until I go through the whole process of finding the files elsewhere, using the Toolkit to flash them etc etc.
Is there a better way to do this automatically? Can I find the downloaded OTA package on the Nexus and just flash it from there?
Since Lollipop, you can't take an OTA in any way (official or sideload) if you've modified your system. Rooting, custom recovery or kernel. Unrooting does not help since the system already has been modified.
Easiest way to upgrade and still keep your data is to flash the factory image but leave out userdata.img. This can be easily done through NRT (No wipe mode) if command prompt is scary. Yes you'll have to reroot... But hey, this is a Nexus, it's easy.
I assume that means waiting for someone to post the update?
If you want to wait for someone to make a prerooted image, then yes. Otherwise just download the official factory image (Google it) and go for it.
Google doesn't always release OTAs and factory images at the same time, so some waiting will probably always be involved...
Drives me crazy. TWRP used to be able to intercept a OTA flash, flash the needed images, detect you lost root and ask to restore root.
Somewhere that disappeared.
I just flashed a very old stock and took every OTA to 5.0.2, rooted, setup... now getting bombarded with 5.1.1 update notification. Ugh
Didgeridoohan said:
Since Lollipop, you can't take an OTA in any way (official or sideload) if you've modified your system. Rooting, custom recovery or kernel. Unrooting does not help since the system already has been modified.
Easiest way to upgrade and still keep your data is to flash the factory image but leave out userdata.img. This can be easily done through NRT (No wipe mode) if command prompt is scary. Yes you'll have to reroot... But hey, this is a Nexus, it's easy.
Click to expand...
Click to collapse
I need to flash the latest lollipop image to my rooted nexus with TWRP. I know where to find the images but don't remember how to flash it. What exactly are the steps and how do I leave out userdata.img ?
And what are the steps to reroot lollipop?
Thanks
i keep getting the offer to download the 5.1 update but when i do it dloads it then tries to reboot into recovery to flash it but it obviously boots into TWRP recovery which is no good.
So the question is when it dloads the update where does it dload to?
and could i flash it from TWRP if i find it?