Notice (4/16/14): I'm no longer here. I've said "goodbye" to AT&T and their locked bootloader schemes. I'm voting with my wallet - I've sold my I337 and switched to T-Mobile. My apologies to the community, but you're now on your own here.
NOTICE: These instructions are pretty much obsolete. If you'd like to run a pure stock MF3 rom based on this exact method of neutering the MF3 OTA update, then read this thread. This thread shall remain for informational purposes only.
A quick THANKS to djbliss (motochopper root exploit), TeamWin (TWRP recovery), Chainfire (SuperSU), and all of the Guinea pigs that tested some of this stuff out for me in this thread.
What is this?
This is not technically a ROM, but by the time you are done, you will be running the stock, (albeit rooted) I337UCUAMF3 ROM provided by AT&T. Unlike the original MF3 OTA patch, if you perform the steps outlined in this thread, you will not lose your custom recovery, and your bootloader (including aboot) will remain untouched.
Here's what the neutered version does:
It will flash a new boot.img, which primarily includes the MF3 Kernel.
It will flash the RPM partition, which as far as I can tell is strictly for power management. I kept it in the package because it seems harmless.
It will update many files in your /system partition, bringing you up to the latest MF3 build (the whole point).
It will flash the new MF3 modem/Baseband, along with its counterpart, the NON-HLOS partition as well. The NON-HLOS partition will cause some problems with your sound (keep reading), but I've added a patch here that will solve this problem while creating another (WiFi breaks). I've kept this included in the original neutered patch, just in case someone is able to find a very easy fix for the sound and/or WiFi.
Can I go back?
From my experience, if you do not update the bootloaders, it is fully possible to return to the I337UCUAMDB or I337UCUAMDL stock versions. I used Odin, personally, but you could simply restore nandroid backups or flash a new rom. Your modem/Baseband will stay at I337UCUAMF3, along with your RPM partition - unless you use Odin or otherwise flash older versions manually. Personally, I found ZERO side-effects of performing these steps and then restoring my MDL-based nandroid backup.
Bugs?
At this time, you will have to choose between either having sound, or having WiFi. Can't have both. This is completely related to the NON-HLOS modem that's included and expected in the MF3 build. As mentioned above, the new NON-HLOS modem will kill your sound capabilities without having the new bootloaders, etc. I have no idea why, so I've provided a "fix" for this - a flashable .zip that will restore your NON-HLOS modem back to the MDL version. If you revert to this MDL NON-HLOS modem, you will lose WiFi capabilities. If someone finds a more proper fix for this, please let everyone know. Otherwise, you're welcome to keep switching back and forth as you please. See the section in this post about flashing just the modems.
Anything else?
In addition to all this, I've provided a modified, deodexed SecSettings.apk that will not scan for SysScope and will not mark your system as "Custom". This add-on package also removes SysScope entirely from the OS. This add-on optional, and you can choose not to flash this part if you wish. This package is based on my previous mod, located here (some minor changes in Status.smali to match the new MF3 build, but otherwise the same steps were performed to create this new SecSettings.apk). Basically, if you perform all of the steps outlined in this method, you will find yourself with an "official" status, and will have the original "Galaxy S4" boot logo (not the custom/padlock logo), regardless of the root or custom recovery.
Warnings and Caveats:
I have not extensively tested the I337UCUAMF3 operating system, and I WILL NOT be providing tech support for this operating system. Take it AS-IS, and ask your questions about the OS in the Q&A forum. This thread will be only for the process of getting you to I337UCUAMF3.
NOTICE: This is only intended for the I337 - a.k.a. the AT&T Galaxy S4. I have only tried this on my 16Gb, original device. You may try it on other devices, but there is of course a very high risk of bricking your non-i337 device. You've been warned.
WARNING: I am not responsible if you brick your device. Follow the instructions very, very closely, and you will be fine.
ANOTHER WARNING: There are mixed reports about certain things being broken with the MF3 update, such as the "free unlock with hidden menu" and tethering, etc. If these are important to you, you might want to make a full backup of your EFS just in case. Most custom recoveries (including the provided TWRP recovery) can help you do this. The EFS partition does not appear to be touched during the update, but just in case the new kernel or new modem does something to it on-the-fly, it would be a good idea to have a backup.
Okay, great. So what do we do?
Click the "Click to show content" button below to begin.
Download all these prerequisites. Get the downloads started now, and just read-ahead so you are familiar with the next steps.
openrecovery-twrp-2.6.0.0-jflteatt.img
Original is found on TWRP's website.
NOTE: You can download your own recovery.img if you'd like. Continue reading instructions for more details.
MDL-noSecure.zip
MF3-Neutered.zip
UPDATE-SuperSU-v1.41.zip
Original is found on Chainfire's website.
remove-SysScope.zip
modem-fix.zip
motochopper-mod.zip
Put each and every one of these downloads onto the root of your internal SDCard (/sdcard/).
Make a full Nandroid backup of your device - include system, data, and everything.
Make a backup of everything that is on your internal SDCard - it's possible to accidently wipe it.
Wipe data. Be careful not to wipe your SDCard!
Odin to stock, unrooted MDB package. Instructions here.
Allow the device to reboot fully into the clean, stock MDB. This will clear your "Custom" status, by the way.
When returning to MDB, some apps will likely force-close when they start. This is due to data problems with these apps. You could wipe data again to remove these, but there is risk of wiping your SDcard if you do it wrong. Otherwise, just clock OK and get through them all before continuing.
Run Motocopper - Use custom version that I've provided, OR you can download the original version here http://forum.xda-developers.com/showthread.php?t=2252248
NOTE: If you use the original version, be sure not to allow it to restart your device! At the end when it prompts you to "Press Enter to reboot..." - DO NOT REBOOT.
Install a custom recovery using your ADB shell. Do NOT mistype the partition number at the end, or you can easily hard-brick your device.
Code:
# dd if=/sdcard/openrecovery-twrp-2.6.0.0-jflteatt.img of=/dev/block/mmcblk0p21
# reboot recovery
Note: You should be able to use your own recovery. You will need to install it using the method above, however. Programs like GooManager will not work at this stage.
Allow the device to reboot directly into recovery. Do not leave recovery until instructed to do so.
Flash MDL-noSecure.zip
NOTE: This is the original AT&T I337UCUAMDL update, but with the "ro.secure" check removed, and the recovery removed. Otherwise it is the same thing.
Flash MF3-Neutered.zip
Flash UPDATE-SuperSU-v1.41.zip
Flash remove-SysScope.zip
NOTE: This package will also clear your dalvik cache, just in case.
Flash modem-fix.zip
NOTE/BUG: If you skip this, you will lose all audio. If you flash this modem-fix, you will lose WiFi. Currently working on investigating this!
Wipe Data/Cache.
Reboot the device into system.
Enjoy I337UCUAMF3.
Click the "Thanks" button if this has helped you.
But I only want to flash the new modem (Baseband). Do I have to do all that crazy stuff?
Certainly not! You can flash just the modem itself, very easily. You need to be rooted, or have a custom recovery first.
The Manual Method - requires root (advanced users, but technically easier and quicker!):
Download the .zip I created of all the modems I've ever had here.
Make a nandroid backup for safekeeping. Note that a nandroid backup will not typically backup your current modem - this is just a precaution in case you mess things up and have to use Odin to restore your modems or something. Better safe than sorry!
Unzip contents to your sdcard.
Fire up your ADB shell.
Type the following very carefully. DO NOT GET THE PARTITION NUMBER WRONG or you could easily brick your device. Badly.
Code:
su
dd if=/sdcard/modem-MF3.bin of=/dev/block/mmcblk0p2
reboot
Start testing it out!
NOTE: The included NON-HLOS.bin is intended for mmcblk0p1. If you are on an MDL-based ROM and/or Kernel, don't flash this file yet, unless you're being experimental. Here's why:
If you have an MDL-based ROM/Kernel... said:
If you have an MDB NON-HLOS.bin and an MF3 modem.bin, Wi-Fi will break.
If you have an MF3 NON-HLOS.bin and an MF3 modem.bin, sound will break.
If you have an MDL NON-HLOS.bin and an MF3 modem.bin, .... Nothing seems broken. Sound and Wi-Fi are working.
Click to expand...
Click to collapse
The Automatic Method - requires custom recovery (recommended for flashaholics):
CPA Poke has offered a flashable version of the modem as an option here.
I just want the original, unaltered I337UCUAMDF patch. Where can I find it?
You can download it here. This was taken straight from \cache\fota\2400258.cfg. You can rename it as a .zip if you'd like to mess with it. Please note that this file may not be flashable on your device if you have customized your /system partition or have made other modifications to your device. This patch performs a series of integrity checks, and will not install if it fails any of them. If it fails, you should be safe, as the patch sequence aborts before making changes if it fails the checks.
BE FOREWARNED: Flashing this file directly will cause you to lose root, lose your custom recovery, and lose the ability to obtain root in the future (as far as we know). In other words, DO NOT install this unaltered, original update if you EVER want to have root again, flash custom ROMs, or have the ability to make/restore nandroid backups. You've been warned.
How can I make my own neutered version of the OTA patch?
Check out post #2 in this thread for all the details on how to customize your OTA patch file, including the warnings and potential ways you can hard brick your device.
What was changed in this patch?
If you were to flash the original patch without neutering it first, you'll be stuck with a stock MF3 build (or higher). As far as we can tell, this patch does blow some e-fuses in the device, incrementing a number such that it is impossible to return back to an older build (MDB or MDL). There is currently no known cure for this condition if this is the case, especially considering we have locked bootloaders on the I337 at this time.
For a complete list of all the files that this patch touches on your system, you can check out my previous post here.
Can I use this in my own ROM?
Certainly! In fact I encourage it. I'd like to see some cool ROMs be built using the MF3 base. It's got some nice improvements on the MDL base, so any stock-based ROMs should benefit. You have my full permission to use this complete process or any parts/pieces/packages/methods herein. I would like to see my name mentioned in your "thanks" list if you have one, but this is of course completely optional.
Where can I download a full system and kernel dump of the work you did? (ADDED 7-12-13)
You can download it right here. Apart from the SysScope mod mentioned above and injecting root, this is the full, stock image. This is NOT directly flashable, so don't even try. This will only be useful for ROM developers and advanced users. The modems and bootloaders have nothing to do with these packages, but these might be required for everything to work correctly (i.e. sound and WiFi).
This was created from my device after performing all the steps above, using these commands while the device was in recovery, from a root ADB shell:
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/system-MF3.img
dd if=/dev/block/mmcblk0p20 of=/sdcard/boot-MF3.img
Do you have this available as a ROM I can flash? (ADDED 8-6-13)
Indeed! If you want to install this as a ROM, check out my newer thread here.
Anything I can do to help here?
If this information and tutorial helped you out, just simply hit the "THANKS" button. It's great to know the work was appreciated. Another way that you can help is to provide feedback in this thread about how it worked for you, and if there's any improvements that can be made. Lastly, if you're interested in helping financially to help recover the costs of the JTAG box I now need to recover my S4, you're certainly welcome to assist by using the donate link on the left. Keep in mind that I'm not technically a Dev here - I'm just another forum member that's providing information to other members. It's what this whole community is about.
How can I make my own neutered version of the OTA patch?
With lots of careful snipping. But first, you need a copy of the original OTA patch. You can download this from my post above, or you can download one yourself straight from AT&T.
To download your own copy, the process is not terribly complicated - just risky. Here's the steps I performed to obtain the original update file from AT&T:
Make sure you have root before continuing. If you screw this up and allow the update to install, you're pretty much SOL.
If you are running the stock MDL rom, you can simply launch the updater in Settings -> More... -> About device -> Software update and let it download. Just don't reboot your phone until you've then frozen the AT&T update applications (all 3 of them) from performing the update. Keep in mind that your device will eventually reboot on its own, thanks to AT&T and their way of forcing updates.
Pull the update file from /cache/fota/2400258.cfg, and put it somewhere on your computer that you can work with it. It's just a .zip file in disguise, so you can simply rename it appropriately.
Delete the original .cfg from the device.
As mentioned, freeze or disable the updater applications.
You now have your own copy of the OTA update.
Great - you've got the file. Time to grab the scissors and perhaps something to steady the hands and numb the pain. A keyboard works too in this case. Here's what to do:
Save a backup copy of your update file. One copy for safekeeping (in case you want to start over) and another to work on. Do it now.
Open the update file using basically any .zip editor. I used 7zip because it performed quickly, whilst Win7's zip capabilities were VERY SLOW dealing with this file.
[*]From the root directory of the file, delete:
aboot.mbn
sbl2.mbn
sbl3.mbn
tz.mbn
The entire "recovery" directory.
Within the file, browse to META-INF\com\google\android and pull a copy of the updater-script. This file does all the magic.
Edit the updater-script using a text editor, preferably something like Notepad++ (great program! I recommend it). Make the following changes:
Remove the following line:
Code:
assert(getprop("ro.secure")=="1");
Edit the following line from:
Code:
"/system/tts/lang_SVOX/svox-lh0pt2en-US22.pil",
to
Code:
"/system/tts/lang_SVOX/svox-lh0pt2en-US22.pil");
Remove the following line (it's right after the last one you edited):
Code:
"/system/recovery.img");
Remove the following lines:
Code:
delete("/system/recovery-from-boot.p",
"/system/etc/install-recovery.sh");
and remove:
Code:
ui_print("Unpacking new recovery...");
package_extract_dir("recovery", "/system");
and remove:
Code:
set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");
and remove:
Code:
ui_print("Update sbl2 ota");
assert(write_backup_fota("/dev/block/mmcblk0p4", "/dev/block/mmcblk0p22"));
assert(package_extract_file("sbl2.mbn", "/dev/block/mmcblk0p4"));
assert(erase_backup_fota("/dev/block/mmcblk0p22"));
ui_print("Package sbl2 Done.");
ui_print("Update sbl3 ota");
assert(write_backup_fota("/dev/block/mmcblk0p5", "/dev/block/mmcblk0p22"));
assert(package_extract_file("sbl3.mbn", "/dev/block/mmcblk0p5"));
assert(erase_backup_fota("/dev/block/mmcblk0p22"));
ui_print("Package sbl3 Done.");
ui_print("Update aboot ota");
assert(write_backup_fota("/dev/block/mmcblk0p6", "/dev/block/mmcblk0p22"));
assert(package_extract_file("aboot.mbn", "/dev/block/mmcblk0p6"));
assert(erase_backup_fota("/dev/block/mmcblk0p22"));
ui_print("Package aboot Done.");
and remove:
Code:
ui_print("Update tz ota");
assert(write_backup_fota("/dev/block/mmcblk0p8", "/dev/block/mmcblk0p22"));
assert(package_extract_file("tz.mbn", "/dev/block/mmcblk0p8"));
assert(erase_backup_fota("/dev/block/mmcblk0p22"));
ui_print("Package tz Done.");
Save it, and put the modified updater-script back inside the update file where you found it, replacing the old one.
Upload it to your SDCard and flash. See all the warnings here in this post and in the original post about what to do with this thing.
NOTES and WARNINGS:
A careful reader will be able to easily tell what each part of the updater-script does, and you can choose whether or not to keep it, modify it, or delete it.
Keep in mind that the update will fail if it does not pass all of those integrity checks. You can technically remove all of the integrity checks, and the update will still process, patching files left-and-right. However, depending on how heavily you have modified your system, you will probably run into extreme problems (soft brick most likely).
CRITICAL WARNING ABOUT BOOTLOADERS: At this time, do NOT allow the update package to only partially update your bootloader! Failure to update the entire bootloader will result in a hard brick. For example, if you were to include the parts that update sbl2 and sbl3, but not include tz and aboot... your chain of trust will be violated, and the device will refuse to boot normally (a.k.a. QDL Mode or Emergency Boot). The only theoretically known way out of this is JTAG. You don't want to go there. So, simply put: regarding bootloaders, it's all or nothing. The bootloader updates included in this package are: sbl2.mbn sbl3.mbn aboot.mbn tz.mbn. It's like any good D&D campaign - if you separate these party members, the campaign is toast.
REMINDER: At this time, it appears that flashing the new bootloader will trip an e-fuse. This is a hardware device that is only capable of incrementing a number. If the number on the e-fuse is higher than the bootloader you are trying to flash (with Odin, for example), the device will refuse to take the update. In other words, if you flash the MF3 bootloader, there is no known way to return to the MDB or MDL bootloaders at this time.
Nice...as usual. Just to help make it clear, are you allowing other developers to use this to put into their ROMs (with credit given of course)?
Again, thanks for your work.
scott14719 said:
Nice...as usual. Just to help make it clear, are you allowing other developers to use this to put into their ROMs (with credit given of course)?
Again, thanks for your work.
Click to expand...
Click to collapse
Certainly! I've updated the OP with, "You may also use any of the packages created or modified here for inclusion in your ROMs." at the end of it to clarify. Thanks for bringing it up. :good:
thanks man!!.. you put alot of work into this!!! very nice job:good:
Aou said:
Certainly! I've updated the OP with, "You may also use any of the packages created or modified here for inclusion in your ROMs." at the end of it to clarify. Thanks for bringing it up. :good:
Click to expand...
Click to collapse
Just an fyi... Dropbox ha temporally disabled the down load. At least that's the error in getting.
Sent from my SAMSUNG-SGH-I337 using xda premium
spdwiz18 said:
Just an fyi... Dropbox ha temporally disabled the down load. At least that's the error in getting.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
Figures. >_<
Looks like I'll need a better place to upload these... I'll upload them elsewhere and update the OP as soon as I can find a good place to put them.
Thanks for notifying me!!
Aou said:
Figures. >_<
Looks like I'll need a better place to upload these... I'll upload them elsewhere and update the OP as soon as I can find a good place to put them.
Thanks for notifying me!!
Click to expand...
Click to collapse
You dida great job, but think there may be an easier way to update if you are interested.
Food for thought.
This will only work with yours since you are updated.
dd if system and boot to the sdcard as system.img and boot.img.
Use kitchen to extract system and build update zip from that. This would create less flashes as it would have root and everything else built in.
Just a thought. If it sound likeva c goid idea. Great! If not its ok.
Again. Great job.
Sent from my SAMSUNG-SGH-I337 using xda premium
Just wondering what's up with sound. So weird modem would mess with that
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
spdwiz18 said:
You dida great job, but think there may be an easier way to update if you are interested.
Food for thought.
This will only work with yours since you are updated.
dd if system and boot to the sdcard as system.img and boot.img.
Use kitchen to extract system and build update zip from that. This would create less flashes as it would have root and everything else built in.
Just a thought. If it sound likeva c goid idea. Great! If not its ok.
Again. Great job.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I haven't actually build a ROM yet, but this might be a good time to try!
jetlitheone said:
Just wondering what's up with sound. So weird modem would mess with that
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
iknorite? Perhaps a more experienced Dev could shed some light on what's going on with this. If a solution is found, I would love to incorporate it into this project.
Also, an update: I added instructions in post #2 on how you can obtain and neuter your own OTA update file. I have no intentions of hiding any of my work.
Aou said:
I haven't actually build a ROM yet, but this might be a good time to try!
iknorite? Perhaps a more experienced Dev could shed some light on what's going on with this. If a solution is found, I would love to incorporate it into this project.
Also, an update: I added instructions in post #2 on how you can obtain and neuter your own OTA update file. I have no intentions of hiding any of my work.
Click to expand...
Click to collapse
You've tried different kernels and such
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Aou said:
I haven't actually build a ROM yet, but this might be a good time to try.
If you want or need help in this. Just ask.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I already sort of updated to the latest version I337UCUAMF3. Is there any hope left for me? Can I roll back to the previous versions and get my root back or should I just sit and wait and hope someone releases a root for the newer version?
Mrkqql143 said:
I already sort of updated to the latest version I337UCUAMF3. Is there any hope left for me? Can I roll back to the previous versions and get my root back or should I just sit and wait and hope someone releases a root for the newer version?
Click to expand...
Click to collapse
You can probably do the Samsung update utility through kies
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
jetlitheone said:
You can probably do the Samsung update utility through kies
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
I am saying I already updated. Is there a way for me to go back using the utility?
Mrkqql143 said:
I am saying I already updated. Is there a way for me to go back using the utility?
Click to expand...
Click to collapse
Yes it'll update you backwards since the new update isn't up on their site haha do an emergency firmware update or whatever
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Mrkqql143 said:
I am saying I already updated. Is there a way for me to go back using the utility?
Click to expand...
Click to collapse
Last I read odin was a no go if you take the update so you're stuck until someone figures out how to get around it.
EDIT: Let me know if the above works if you try.
If I am rooted with supersu 1.41 (custom status removed) and cwm recovery - can I just flash the neutered ota.zip and get the modem update that came with the ota zip?
Thanks for the clarification.
Noobla_Khan said:
Last I read odin was a no go if you take the update so you're stuck until someone figures out how to get around it.
EDIT: Let me know if the above works if you try.
Click to expand...
Click to collapse
Nope. Odin is a NO go!
Mrkqql143 said:
Nope. Odin is a NO go!
Click to expand...
Click to collapse
Yup knew odin was a no go, I was wondering if you could emergency back with Kies due to them not having the update on the web yet as stated above.
Related
PLEASE READ EVERYTHING BEFORE ATTEMPTING TO INSTALL
This is a rooted, de-odexed, busybox, nano, ad-blocking hosts file, uncensored DNS resolv.conf but otherwise completely stock version of the 2.15.531.3 OTA for the T-Mobile G-2. This is not an update. It is a complete ROM.
I built this for my own use but anyone can take it and customize it as they see fit. I am a "Privacy and Security by Default" minded person so I have built it with a few alterations along those lines.
The ad blocking hosts file is to block known adware/malware from first boot. Updates to the hosts file as new threats are learned can be done by installing AdFree from Market or manually updating the hosts file yourself. I am not affiliated with the creators of AdFree in anyway. You can install it or not if you want or manually update your hosts file manually or not if you want.
The uncensored DNS resolv.conf I have included is because many ISP's and networks censor the Internet by controlling what you get directed to through DNS that is not what the official DNS record would require. They also hijack bad requests and typos through DNS redirects to their own search and ad pages. Google logs all DNS queries and what IP address it came from if you use the "open" Google DNS servers. I have included alternate secure and uncensored DNS settings as that is what I use myself.
I have now included a link to download a version of this ROM without those two customizations. I have not tested it myself but it should work fine for you if you choose to install it.
I used dsixda's kitchen to do the modifications and without that, I would probably not have done this at all. http://forum.xda-developers.com/showthread.php?t=633246
You will need to be rooted with S-OFF, Clockworkmod Recovery and engineering hboot to install this.
See this wiki guide for all information on rooting and downgrading the G2: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
See this thread for general information on the G2 also: http://forum.xda-developers.com/showthread.php?t=916431
THIS ROM IS SET TO WIPE THE SYSTEM BEFORE INSTALLING. MAKE SURE YOU HAVE A BACKUP OF ANYTHING IMPORTANT BEFORE INSTALLING THIS! The reason for this is that I can see potentially major problems if it is installed like an update. THIS IS FOR CLEAN INSTALLS ONLY.
You will need to install the radio that came with this OTA manually before installing this ROM. The radio version to install is 12.52.60.25U_26.08.04.30_M3.
Download the radio here: http://www.mediafire.com/file/51rr1vff4wamedg/TMOUS_G2_12.52.60.25U_26.08.04.30_M3_radio.img
Rename the file to radio.img and install it from fastboot. You need the Android SDK tools and platform tools installed on your computer and the engineering hboot installed on your G2 to do this. Shutdown the phone completely. Then hold the trackpad button while powering the phone back on. Connect the phone with the USB cable. Open a command prompt and change to the directory where the radio.img file is. Issue the following command:
fastboot flash radio radio.img
Wait for the radio to update completely and successfully and then disconnect the USB cable. Select "REBOOT BOOTLOADER" and verify from the fastboot screen afterwards that the radio is installed. Then select "BOOTLOADER" and from the bootloader select "RECOVERY" to proceed to install the ROM.
INSTALL THIS AT YOUR OWN RISK. I am not responsible for what you do with this and there is no implied warranties and guarantees.
I recommend a full wipe/factory reset from within recovery before installing this just to be safe. ***This does not revert you to S-ON or un-root the G2.***
MAKE SURE YOU HAVE BACKUPS OF ANYTHING AND EVERYTHING BEFORE INSTALLING THIS.
I do not plan to do any customizations of this but I will try to answer any questions that may come up.
***Update: I may post a version without the uncensored DNS setting and ad blocking hosts file as it is a simple tweak and there seems to be a calling for it. Stay tuned...***
***Update: There is now a link to download a version without the ad blocking hosts file and the uncensored DNS resolv.conf.***
Download: http://www.mediafire.com/file/b4w4a...d_S_TMOUS_2.15.531.3_signed_080311_215742.zip
Download without ad blocking hosts and uncensored DNS resolv.conf (untested by me, please let me know if there are any errors): http://www.mediafire.com/file/mh1zk...d_S_TMOUS_2.15.531.3_signed_080411_152226.zip
Good luck and have fun!
Awesome! Thanks!
Hey, can you tell us how you temp-rooted? That is actually all I'm interested in; I've been running Visionary on 2.2 to temp-root on boot, and that serves my purposes. I'd just like to be able to keep doing the same thing, although I realize Visionary won't work, but would you be able to put together a Visionary-like app that does give us temp-root on the new 2.3.4?
Thanks again!
Thanks bro! Can't wait to give it a go
Sent from my HTC Vision using XDA App
RebelScum75 said:
Awesome! Thanks!
Hey, can you tell us how you temp-rooted? That is actually all I'm interested in; I've been running Visionary on 2.2 to temp-root on boot, and that serves my purposes. I'd just like to be able to keep doing the same thing, although I realize Visionary won't work, but would you be able to put together a Visionary-like app that does give us temp-root on the new 2.3.4?
Thanks again!
Click to expand...
Click to collapse
In the DZ/G2 wiki are instructions for downgrading the 2.3.x factory installs using fre3vo to gain temp-root. As far as I know, there isn't any way to gain permanent root on an installed 2.3.x system.
spookievision said:
This is a rooted, de-odexed, busybox, nano, ad-blocking hosts file, uncensored DNS resolv.conf but otherwise completely stock version of the 2.15.531.3 OTA for the T-Mobile G-2. This is not an update. It is a complete ROM.
I built this for my own use but anyone can take it and customize it as they see fit.
I used dsixda's kitchen to do the modifications and without that, I would probably not have done this at all.
You will need to be rooted with S-OFF, Clockworkmod Recovery and engineering hboot to install this.
See this wiki guide for all information on rooting and downgrading the G2: http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
THIS ROM IS SET TO WIPE THE SYSTEM BEFORE INSTALLING. MAKE SURE YOU HAVE A BACKUP OF ANYTHING IMPORTANT BEFORE INSTALLING THIS! The reason for this is that I can see potentially major problems if it is installed like an update. THIS IS FOR CLEAN INSTALLS ONLY.
You will need to install the radio that came with this OTA manually before installing this ROM. The radio version to install is 12.52.60.25U_26.08.04.30_M3.
INSTALL THIS AT YOUR OWN RISK. I am not responsible for what you do with this and there is no implied warranties and guarantees.
I recommend a full wipe/factory reset before installing this just to be safe.
MAKE SURE YOU HAVE BACKUPS OF ANYTHING AND EVERYTHING BEFORE INSTALLING THIS.
I do not plan to do any customizations of this but I will try to answer any questions that may come up.
Download: http://www.mediafire.com/file/b4w4a...d_S_TMOUS_2.15.531.3_signed_080311_215742.zip
Good luck and have fun!
Click to expand...
Click to collapse
I have a couple of questions. You say that we need to have a rooted phone already, but at the bottom you say that you recommend a full swipe/factory reset before installing this ROM. Wouldn't a factory reset get rid of the root and s-off?
Also, how do you install a radio and where would we get it from?
Thanks!
konoplya said:
I have a couple of questions. You say that we need to have a rooted phone already, but at the bottom you say that you recommend a full swipe/factory reset before installing this ROM. Wouldn't a factory reset get rid of the root and s-off?
Also, how do you install a radio and where would we get it from?
Thanks!
Click to expand...
Click to collapse
Flashing a radio: http://forum.xda-developers.com/showthread.php?t=896597
I would get the radio that is designed for this ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1202429
A factory reset will get rid of the entire ROM image on your phone. It will not change the s-off factor.
spookievision said:
In the DZ/G2 wiki are instructions for downgrading the 2.3.x factory installs using fre3vo to gain temp-root. As far as I know, there isn't any way to gain permanent root on an installed 2.3.x system.
Click to expand...
Click to collapse
spookievision,
To make this a "turn-key" pure vanilla stock GB rom, can you include the radio that seems to be missing, take away AdFree, and that other thing with config file you mentioned (forgive my noobness) and make a "white-wall" clean stock rom that can be flashed using CWM?
I want to experience this "stock" for myself, but i'm from CM7 and don't have any experience with flashing radios, and this config, AdFree files.. I would like to simply download, do a nan-backup (of my old CM7 rom), then flash without having to worry about any of the other stuff.
Thanks,
lawalty said:
spookievision,
To make this a "turn-key" pure vanilla stock GB rom, can you include the radio that seems to be missing, take away AdFree, and that other thing with config file you mentioned (forgive my noobness) and make a "white-wall" clean stock rom that can be flashed using CWM?
I want to experience this "stock" for myself, but i'm from CM7 and don't have any experience with flashing radios, and this config, AdFree files.. I would like to simply download, do a nan-backup (of my old CM7 rom), then flash without having to worry about any of the other stuff.
Thanks,
Click to expand...
Click to collapse
I have updated the first post with additional information about the radio and some more links. Unfortunately, I do not know how to get the radio to update through recovery so it has to be manually installed separately.
I have posted a new link and more information in the first post.
Who has successfully OC the official GB??
Need a link to proper kernal that wont breakanything
mike102871 said:
Who has successfully OC the official GB??
Need a link to proper kernal that wont breakanything
Click to expand...
Click to collapse
Any alternate kernel can potentially break things as they aren't what the system is compiled to work with originally. HTC hasn't released the kernel source for this version yet to my knowledge so alternates that would be the most compatible won't be available until they do.
I just flashed this rom through clockwork without wiping anythingfirst. It does install as a clean rom just like a new phone. Is rooted, Very nice. Ididnt install the radio suggested as the one i hadinstalled was a newer one than listed.
mike102871 said:
Ididnt install the radio suggested as the one i hadinstalled was a newer one than listed.
Click to expand...
Click to collapse
How'da have the radio? What version do you have, and how can I get my hands on it? Can you spare a link? Is so, how do I know what to flash?
Thanks.
mike102871 said:
I just flashed this rom through clockwork without wiping anythingfirst. It does install as a clean rom just like a new phone. Is rooted, Very nice. Ididnt install the radio suggested as the one i hadinstalled was a newer one than listed.
Click to expand...
Click to collapse
Without the proper radio, you might run into issues with data connectivity and WiFi Calling and potentially battery life issues. Let us know what you find.
And I'm glad you like it.
spookievision said:
I have updated the first post with additional information about the radio and some more links. Unfortunately, I do not know how to get the radio to update through recovery so it has to be manually installed separately.
Click to expand...
Click to collapse
I suspect that is what the fotaBoot "file" is for. I think it forces reboot to bootloader to flash the firmware.zip. just a theory and keep in mind, my rooted rom broke everything but the bootloader.
sent from my cyanogen(mod) vision
gee one said:
I suspect that is what the fotaBoot "file" is for. I think it forces reboot to bootloader to flash the firmware.zip. just a theory and keep in mind, my rooted rom broke everything but the bootloader.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
That is why I have manual radio instructions as I don't quite understand the factory update method yet. Which rooted ROM broke?
spookievision said:
That is why I have manual radio instructions as I don't quite understand the factory update method yet. Which rooted ROM broke?
Click to expand...
Click to collapse
It was my own attempt to make a rooted rom. I applied the system patches through CWM, modded the boot and recovery to use the new kernel, but did not flash the hboot nor radio. Stuck on boot screen with a broken recovery! It's still a work in progress.
sent from my cyanogen(mod) vision
gee one said:
It was my own attempt to make a rooted rom. I applied the system patches through CWM, modded the boot and recovery to use the new kernel, but did not flash the hboot nor radio. Stuck on boot screen with a broken recovery! It's still a work in progress.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I see. You have to break a few before you learn. And I've broken plenty in the past myself.
lawalty said:
How'da have the radio? What version do you have, and how can I get my hands on it? Can you spare a link? Is so, how do I know what to flash?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=970809&highlight=radio
The first one in the list. Came out 7/14
mike102871 said:
http://forum.xda-developers.com/showthread.php?t=970809&highlight=radio
The first one in the list. Came out 7/14
Click to expand...
Click to collapse
FYI: If you are looking for the radio that came with this OTA, I put a link to it in the first post of this thread.
Will I be okay? Or will I possibly brick my phone?
I only want to ask this once, so for future reference, do official updates wipe EVERYTHING on the phone, or just the modem/kernel?? If so, why will EK02 not work on EG31?
It will be fine I had the same on my fiance epic
Sent from my SPH-D710 using XDA App
Gomenkiyo said:
Will I be okay? Or will I possibly brick my phone?
I only want to ask this once, so for future reference, do official updates wipe EVERYTHING on the phone, or just the modem/kernel?? If so, why will EK02 not work on EG31?
Click to expand...
Click to collapse
The official OTA "patch" update will fail if you have CWM because the integrity check for your zImage will fail.
You can use one of the modified EK02 patch updates which bypass this problem.
sfhub said:
The official OTA "patch" update will fail if you have CWM because the integrity check for your zImage will fail.
You can use one of the modified EK02 patch updates which bypass this problem.
Click to expand...
Click to collapse
I'm on EG30 rooted with your auto root script. I haven't changed my zImage, but I have 'tinkered' in system, specifically clearing battery stats and attempting to replace the voice talk apk with google voice search apk (a rename trick I stumbled upon). I have reversed the voice talk apk, overwriting it with the original that I backed up first. Given all that, would you have any idea what my odds are that the OTA will pass validation on my device? If it won't, is my best option to use your "Option C" to apply the EK02 zImage, then flash the EK02 modem? I wanted to ask this in your thread, but I don't have the posts yet.
Thanks
wraith404 said:
I'm on EG30 rooted with your auto root script. I haven't changed my zImage, but I have 'tinkered' in system, specifically clearing battery stats and attempting to replace the voice talk apk with google voice search apk (a rename trick I stumbled upon). I have reversed the voice talk apk, overwriting it with the original that I backed up first. Given all that, would you have any idea what my odds are that the OTA will pass validation on my device? If it won't, is my best option to use your "Option C" to apply the EK02 zImage, then flash the EK02 modem? I wanted to ask this in your thread, but I don't have the posts yet.
Thanks
Click to expand...
Click to collapse
I can answer my own question in part now. I just got the update, and it installed successfully. So at very least, clearing battery data doesn't affect the verification, nor do timestamps of apks in system/bin as long as they are the right versions.
wraith404 said:
I'm on EG30 rooted with your auto root script. I haven't changed my zImage, but I have 'tinkered' in system, specifically clearing battery stats and attempting to replace the voice talk apk with google voice search apk (a rename trick I stumbled upon). I have reversed the voice talk apk, overwriting it with the original that I backed up first. Given all that, would you have any idea what my odds are that the OTA will pass validation on my device? If it won't, is my best option to use your "Option C" to apply the EK02 zImage, then flash the EK02 modem? I wanted to ask this in your thread, but I don't have the posts yet.
Click to expand...
Click to collapse
The auto root portion is fine. When you installed EG30+CWM, that basically changed your zImage. The linux "kernel" is still stock, but the initramfs was repacked with CWM, which changes the checksum on zImage. You should use Option C to reinstall EG30 and that will take care of that.
As to the file changes, if you look in the updater-script file in the OTA update.zip, you'll see all the files it is checking for validity (all the asserts). If you changed or removed any of them, it will fail.
Honestly if you started making changes to /system besides what the rooting package put in place, unless you are very organized, you might have forgotten which changes you made. If you can really reverse your changes/removals, then go for it. If you can't remember, it is probably quicker just to flash the stock EG30 kernel/ROM in ODIN. That will guarantee all the ROM files and kernel are present and the stock versions.
http://forum.xda-developers.com/showthread.php?t=1282420
sfhub said:
The auto root portion is fine. When you installed EG30+CWM, that basically changed your zImage. The linux "kernel" is still stock, but the initramfs was repacked with CWM, which changes the checksum on zImage. You should use Option C to reinstall EG30 and that will take care of that.
As to the file changes, if you look in the updater-script file in the OTA update.zip, you'll see all the files it is checking for validity (all the asserts). If you changed or removed any of them, it will fail.
Honestly if you started making changes to /system besides what the rooting package put in place, unless you are very organized, you might have forgotten which changes you made. If you can really reverse your changes/removals, then go for it. If you can't remember, it is probably quicker just to flash the stock EG30 kernel/ROM in ODIN. That will guarantee all the ROM files and kernel are present and the stock versions.
http://forum.xda-developers.com/showthread.php?t=1282420
Click to expand...
Click to collapse
I don't quite understand the relationship of the different version zImages you provide - I get CWM vs stock, just not version 'traversal'. From the sound of it, I should use that script to perhaps swap back and for between CWM/stock for whatever version I am at, but not to try to use them to swap between versions. Is that accurate? And is that because they aren't overwriting the system partition?
Thanks, this has been informative.
sfhub said:
The official OTA "patch" update will fail if you have CWM because the integrity check for your zImage will fail.
You can use one of the modified EK02 patch updates which bypass this problem.
Click to expand...
Click to collapse
Could you link me to this specific patch, and please?
Sent from my SPH-D710 using XDA App
Gomenkiyo said:
Could you link me to this specific patch, and please?
Click to expand...
Click to collapse
All the relevant EK02 links are in the Reference Section (2nd post) of the Auto Root sticky:
[ROOT][NCIQ][EG30/EG31/EK02] Auto root your existing stock ROM (w/o ODIN/ROM Flash)
Specifically look at Referece Section #A10
Sprint OTA is the official update, which requires everything to be stock EG30, Modem/Kernel/Recovery/ROM
Rooted OTA is a very slightly modified version that only requires stock EG30 Modem/ROM
---------- Post added at 11:48 PM ---------- Previous post was at 11:44 PM ----------
wraith404 said:
I don't quite understand the relationship of the different version zImages you provide - I get CWM vs stock, just not version 'traversal'. From the sound of it, I should use that script to perhaps swap back and for between CWM/stock for whatever version I am at, but not to try to use them to swap between versions. Is that accurate? And is that because they aren't overwriting the system partition?
Click to expand...
Click to collapse
In theory it is best to match your Kernel and Modem release version #s. In practice, so far, it has been ok to mix/match kernel and modem version #s.
I provide the different versions for people who want to
1) have the kernels match their modems
or
2) try different stock kernels to see if problems are addressed
The kernels have their own partition. They have no effect on the files kept in /system (ie your ROM). That's not to say they have no effect on the behavior of the ROM, just no effect on the files themselves.
sfhub said:
A
In theory it is best to match your Kernel and Modem release version #s. In practice, so far, it has been ok to mix/match kernel and modem version #s.
I provide the different versions for people who want to
1) have the kernels match their modems
or
2) try different stock kernels to see if problems are addressed
The kernels have their own partition. They have no effect on the files kept in /system (ie your ROM). That's not to say they have no effect on the behavior of the ROM, just no effect on the files themselves.
Click to expand...
Click to collapse
I think I get it now, thanks. I've also been looking at your scripts and the copy2sd files, which also shed some light. I'm used to my N1, and the way Samsung has things combined sort of threw me.
wraith404 said:
I think I get it now, thanks. I've also been looking at your scripts and the copy2sd files, which also shed some light. I'm used to my N1, and the way Samsung has things combined sort of threw me.
Click to expand...
Click to collapse
I came from another platform also. The biggest surprise for me was this phone uses the same Kernel+initramfs for both Recovery and Android. I'm used to having them separate and independently updatable.
I think it is actually an oversight or bug because they actually have a separate partition for recovery which duplicates the contents of the boot image. They just aren't using it.
I'm on EG30 rooted with your auto root script. I haven't changed my zImage, but I have 'tinkered' in system, specifically clearing battery stats and attempting to replace the voice talk apk with google voice search apk (a rename trick I stumbled upon). I have reversed the voice talk apk, overwriting it with the original that I backed up first. Given all that, would you have any idea what my odds are that the OTA will pass validation on my device? If it won't, is my best option to use your "Option C" to apply the EK02 zImage, then flash the EK02 modem? I wanted to ask this in your thread, but I don't have the posts yet.
Thanks
If you are disciplined about your changes you have a reasonable chance of having the OTA work. Any changes to config files, binaries, drivers, apps would need to be undone. If you made changes to build.prop undo those. If you removed apps, put them back.
Make sure you have EG30 (not EG30+CWM) BEFORE accepting the OTA, which it sounds like you have.
If it doesn't work, theres a post in the FAQ section of the auto root thread that explains what to do. I believe it is FAQ #E12.
I've put together a zip file with the I747UCLH9 AT&T OTA update that can be flashed using CWM/TWRP. This file
preserves root
does not include the Google search update (so you can keep universal search if you want it)
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 I747UCALG1 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 UCALG1 rooted stock if necessary (see above). If you're already on stock UCALG1 but have framework-res.apk modications applied, you can flash this zip to restore framework-res.apk to UCALG1 stock.
Make sure CWM recovery from clockworkmod.com or TWRP is installed. The recovery from Team Epic will not work.
Put one of the zip files from below on your internal or external SD card.
Boot into recovery
Flash the attached zip
Wipe cache and dalvik cache (optional?)
(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 UCALG1 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.
Here's an alternative way to apply the OTA that doesn't require having stock UCALG1 installed first:
Download all the files in the PIECES section below.
Go into recovery and flash them all before rebooting. Make sure you flash the kernel file after the ROM file.
DOWNLOADS:
I747UCALH9_OTA.zip: This is the full OTA, with kernel and bootloader. You must be using the stock UCALG1 kernel for this to work. MD5: dabaddcfadd250e8389fe387cd3a9ba2
I747UCALH9_OTA_no_kernel.zip: This is the OTA without the kernel. You can use this if you're already running a non-stock kernel. MD5: 7e304f087f7d3e2096c7e30f745df38c
I747UGLH9_OTA_no_kernel_bootloader_modem.zip: This is the OTA without the kernel, bootloader, or modem. It's just the ROM updates. MD5: 6602fd89a3b49db1ab9128c9d9725812
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 LH9. All 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.
No Increasing Ring: This removes the increasing ringtone volume. The mod is from here.
No Increasing Ring + Call Recording: This is the same mod as above but with call recording enabled, as described here.
Remove Wifi Notification: This removes the Wifi notification when connected to Wifi. The mod is from here.
15 Toggles in ICS blue: Customizes the toggles in the notification bar. The mod is from here. You can replace the system/framework/lidroid-res.apk file in this zip with any one of the various themed versions on XDA if you want a different look.
15 Toggles in ICS blue - no brightness bar: The same mod as the one above, but also removes the brightness bar from the notifications drop down.
Extended Power Menu: Adds three choices to the Reboot option in the Power menu: Reboot, Recovery, and Download. The mod is from here.
PIECES:
Bootloader: This zip installs just the LH9 bootloader. MD5: 750ce5b2d0fd4476998a8b9e8194c26a
Modem: The modem can be found in this thread.
ROM: This zip installs a complete rooted copy of the LH9 ROM. Unlike the OTA zip above, it does not require that an unmodified LG1 ROM is already installed, but it is much larger (700 MB). You can flash this and all the other pieces in this section to flash an entire LH9 installation. MD5: 1df5aa24f2fe8fd65299a86f050da947
Kernel: This zip will install just the LH9 kernel and associated kernel modules. MD5: 62475e6701aac016732fb0d7d4b781db
TROUBLESHOOTING:
If the zip file aborts with an error, it's most likely because one of the files it wants to patch has been modified from stock LG1. The OTA is not a complete ROM but is a set of binary patches to the LG1 files, so the files it wants to patch must be unchanged from LG1.
The zip file checks that the files are unmodified before proceeding and prints out the first modified file it finds if something is wrong. If something does wrong, read the error message because it will tell you want the problem is. If you want to post to this thread, include the full error message in your post. This normally includes the string "assert".
CREDITS:
Tether mod: electron73
Cell Standby fix: bala_gamer and Anderilux
No Increasing Ring mod: yoelsd and criskelo
Enable Call Recording mod: wanam
Remove Wifi Notification mod: vlara
15 Toggles mod: wanam, Celmerine for the flashlight fix, and electron73 for the ICS themed lidroid-res.apk file.
Extended Power Menu mod: magn2o and sphinx02
good start.. but still need a version that can be applied on top of lh1
thanks
Great work! Before I give it a try, I wanted to ask if the mods are also rebuilt against LH9. It doesn't seem so from the description, so I wanted to make sure before I decide to give it a go. Thanks.
Can I use the OP steps if I updated the OTA but it said it failed?
This is what my phone info says now
Sent from my SAMSUNG-SGH-I747 [AT&T GS3 Stock Rom] using xda-developers app
So my question is if your using a custom rom there's really no need to update this right? I mean if I flash back to stock and then update and reflash a custom rom its kinda defeats the purpose I'm assuming.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I wanted to add to my prior post that Even tho it says that it told me it failed on install I seem to have all the new features, except the stock browser won't load pages (chrome works though)
Sent from my SAMSUNG-SGH-I747 [AT&T GS3 Stock Rom] using xda-developers app
lgkahn said:
good start.. but still need a version that can be applied on top of lh1
thanks
Click to expand...
Click to collapse
+1 :good:
lgkahn said:
good start.. but still need a version that can be applied on top of lh1
thanks
Click to expand...
Click to collapse
Why? Just restore your nandroid from LG1 (you have one, right?) or ODIN back to LG1, then apply the OTA. The OTA is a patch against LG1, so it can't be applied on top of LH1. If you refuse to go back to LG1, you'll need to wait for AT&T to release the full LH9 ROM as an Odin file.
bracketologist said:
Great work! Before I give it a try, I wanted to ask if the mods are also rebuilt against LH9. It doesn't seem so from the description, so I wanted to make sure before I decide to give it a go. Thanks.
Click to expand...
Click to collapse
Yes, they are. The OP had a typo that I've since corrected. Thanks for pointing it out.
accrews2001 said:
Can I use the OP steps if I updated the OTA but it said it failed?
Click to expand...
Click to collapse
Probably not, because the OTA is a patch for LG1 and is not complete. You're best bet is to go back to LG1 and then apply the zip.
lunercrab said:
So my question is if your using a custom rom there's really no need to update this right? I mean if I flash back to stock and then update and reflash a custom rom its kinda defeats the purpose I'm assuming.
Click to expand...
Click to collapse
In addition to the ROM, the OTA also updates the modem, kernel, and bootloader. The modem is already available in the modem thread. I will eventually make a zip with the kernel and can also make one with just the bootloader if anyone's interested.
To answer your question, if you go back to LG1, flash the OTA, then reflash your custom ROM, you will have changed the modem, kernel, and bootloader but not the ROM.
no i dont have a lg1 backup as i never installed lg1 to my phone just went direct from the originally release firmware or whater to lh1
drothenberger said:
Quote:
Originally Posted by accrews2001
"Can I use the OP steps if I updated the OTA but it said it failed? "
Probably not, because the OTA is a patch for LG1 and is not complete. You're best bet is to go back to LG1 and then apply the zip.
Click to expand...
Click to collapse
I thought your OP steps included going back to LG1?
drothenberger said:
If you didn't make one, you can use Odin and the instructions here to go back to stock.
To apply it:
1.Boot into recovery and make a nandroid backup.
2.Go back to AT&T UCALG1 rooted stock if necessary (see above). If you're already on stock UCALG1 but have framework-res.apk modications applied, you can flash this zip to restore framework-res.apk to UCALG1 stock.
Click to expand...
Click to collapse
accrews2001 said:
I thought your OP steps included going back to LG1?
Click to expand...
Click to collapse
Yes, you're right. If you follow all the steps, you'll first go back to LG1 regardless of what ROM you're on now. Sorry for the confusion.
Thank you! Upgraded successfully.
Worked fine for me. Only additional step is that I had to restore root using the Voodoo OTA app. So I would recommend that anybody who wants to install this update install Voodoo OTA restore first and backup their root access before they flash this.
Edit: BTW I used TWRP 2.2.2 recovery which did not work before when I tried to use the downloaded OTA.
woody1 said:
Worked fine for me. Only additional step is that I had to restore root using the Voodoo OTA app. So I would recommend that anybody who wants to install this update install Voodoo OTA restore first and backup their root access before they flash this.
Click to expand...
Click to collapse
That should not be necessary, although it won't hurt. I did not do anything special to preserve root and did not lose it.
I modified the original OTA upgrade script so it keeps the correct permissions on the /system/xbin/su binary, which should be all that's necessary.
drothenberger said:
That should not be necessary, although it won't hurt. I did not do anything special to preserve root and did not lose it.
I modified the original OTA upgrade script so it keeps the correct permissions on the /system/xbin/su binary, which should be all that's necessary.
Click to expand...
Click to collapse
It's quite possible that I had temporarily disabled root while I before I flashed this update, so it may not be necessary to back up root. Might not be a bad idea, though.
Failed Update
I had rooted my phone using mskip's QCom Toolkit. I used the ALLINONE rooting option, which should be stock with root.
Tried to run the OTA update and failed as expected, but when I tried using the CWM flash method as the OP described, it fails with error "assert failed: apply_patch_check". Not sure if mskip's rooting method makes any modifications to stock. I tired using Voodoo OTA to temporarily disable root, but still same issue.
Current baseband is I747UCLG1
Any pointers? Thanks
What if i have added Google Wallet will i lose that.
I have stock I747UCALG1 Phone Rooted with tether added and Google Wallet. if i use above process will i be fine? I dont want to loose Google Wallet.
I know i have frozen some bloat apps but not sure if i removed any i may have will that mess it up?
drothenberger said:
In addition to the ROM, the OTA also updates the modem, kernel, and bootloader. The modem is already available in the modem thread. I will eventually make a zip with the kernel and can also make one with just the bootloader if anyone's interested.
Click to expand...
Click to collapse
I made a kernel zip for myself, so here it is. I successfully used it to return to the stock kernel after installing the ktoonsez kernel. Perhaps somebody else can make a better kernel zip. I just did
dd if=/dev/block/mmcblk0p7 of=boot.img, dropped that into ktoonsez's installer, swapped in the stock modules, removed his custom app and init.d stuff, and re-zipped it. It works.
The reason was to avoid having to do a full nandroid restore if ktoonsez's kernel didn't work for some reason. I have no reason to think it won't work, I just always make backups.
chenew said:
Tried to run the OTA update and failed as expected, but when I tried using the CWM flash method as the OP described, it fails with error "assert failed: apply_patch_check".
Any pointers? Thanks
Click to expand...
Click to collapse
I need to see the full error message, specifically which file the apply_patch_check is failing for.
tazz0710 said:
What if i have added Google Wallet will i lose that.
I have stock I747UCALG1 Phone Rooted with tether added and Google Wallet. if i use above process will i be fine? I dont want to loose Google Wallet.
I know i have frozen some bloat apps but not sure if i removed any i may have will that mess it up?
Click to expand...
Click to collapse
I don't know much about how Google Wallet is installed, but I suspect you will lose it. I think I read in the other OTA thread that Google Wallet was not applying for people on LH9.
Also, you won't be to apply my zip if you have the tether modification installed. All modifications have to be removed -- you must be on stock LG1. You can apply the tether mod in the OP after you updated to LH9 if you want. I'm not sure about Google Wallet, though.
battro same
drothenberger said:
I need to see the full error message, specifically which file the apply_patch_check is failing for.
The error I get is right after "Verifying current system"
assert failed: apply_patch_check("EMMC: /dev/block/mmcblk0p7 : 5712128 : fb95a5d43d651be3972f96e8d6d2eb181a9fc66b : 5703936 : c1662e87c5d06b735cb46b9673876727f65cb48b","fb95a5d43d651be3972f96e8d6d2eb181a9fc66b")
E:Error in /sdcard/I747UGLH9_OTA.zip
(Status 7)
Installation aborted.
Thanks!
Click to expand...
Click to collapse
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!W0JHQKAK!pA52fCAkUxTMia9A21KL1TrR8bmJT10jhNlBvn5j-Mk
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Click to expand...
Click to collapse
Can you please PM @DocHoliday77 to help him build the Stock ROM for us? He does not have the AT&T Device, but can surely help us in building the ROM. Greatness of him!!
He may ask for some other files for building AT&T ROM for us. If he can build the ROM for us, then we dont have to take the pains of testing the CFG file!!
Thanks man!!
Thank you for sharing this. We'll be hard at work on this now
Sent from my SGH-I747 using XDA Premium 4 mobile app
bkong said:
Here is the ota file I just pulled from my s3. It's a cfg file though, and the recommended way to install is via adb sideload.
Stock users please test it. People who are rooted, use xposed, TiBu to freeze bloat, tell me how to update without a factory reset. I have already tried unrooting and using stock recovery, I am now unfreezing all bloat and uninstall xposed to see if it works.
https://mega.co.nz/#!PJ40jDCY!I2A0Di...381MaXx3_0dl8I
Devs, is there a way to modify the update script so it doesn't check for modified system status? I'm worried I can't update because of tripped knox and if so I'm screwed
Click to expand...
Click to collapse
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
stoobie-doo said:
Anybody have this hosted on a different mirror? The link asks me for a decryption key.
Click to expand...
Click to collapse
Wait until later tonight or tomorrow when enewman17 or docholiday release a flashable
Sent from my SGH-I747 using XDA Premium 4 mobile app
@bkong
Link is bad, clicking it links to a url with "..." in the middle
CNexus said:
@bkong
Link is bad, clicking it links to a url with "..." in the middle
Click to expand...
Click to collapse
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
bkong said:
reuploaded it with new link, does it work now?
I'm also waiting for a flashable zip because I can't get adb working and ota fails every damn time.
Click to expand...
Click to collapse
you can't just flash an update.zip through stock recovery?
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Success!
used the odin flashable 4.3 file from http://forum.xda-developers.com/showthread.php?t=2722660 , went back to stock 4.3 and then used the OTA provided by the OP to get to 4.4.2
edit: please wait for the devs to work their magic to get fully working and easily flashable roms
Jakeuten said:
you can't just flash an update.zip through stock recovery?
Click to expand...
Click to collapse
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
DocHoliday77 said:
Appears to be working! I've got someone who is going to try to get me everything I need to build a rom from the AT&T release, so if all goes well I should have it up this afternoon! :fingers-crossed:
Click to expand...
Click to collapse
could you make an update.zip for users with stock recovery as well?
bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Click to expand...
Click to collapse
OTA shouldn't wipe any of your data. The way it works is it patches the existing files on your device with any changes to bring it up to date. Shouldn't touch any user data at all.
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
It'll be recovery flashable. Im not sure yet if Ill be trying to create an Odin flashable one. Will need to have someone pull the system.img slightly differently if I do. (Would need to Odin flash 4.3, flash TWRP, boot straight to recovery and flash the OTA, then while still in recovery dump the partition.) Even then, no guarantee it would work quite right. These things can be a little finicky.
How is Knox blocking TWRP though? You should be able to flash that via Odin. Since you updated using the OTA though, every time you reboot, it will rewrite the stock recovery. So when you flash TWRP via Odin, uncheck the Auto Reboot box, then after the flash is successful, pull the battery. Then put it back in and boot straight to recovery and flash your rom.
Jakeuten said:
could you make an update.zip for users with stock recovery as well?
Click to expand...
Click to collapse
I will try. No guarantees though. Its been a long time since I've messed with OTA's, so I'm not completely sure I will remember exactly what to do with it. I should be able to do it though. Just not making promises!
bkong said:
I believe that wipes all your data so I wanted to avoid that, and it might not work according to some peoples experience,
Awesome, will this be an odin flashable tar that will keep your data? I have been struggling for the past few hours trying to update without losing all my data. I flashed this rom [http://forum.xda-developers.com/showthread.php?t=2498233] that is stock and includes knox but Adb doesn't work for me and the at&t software update says its up to date, which its not, so I think the rom might have a problem, and I'm trying to figure out how to reinstall twrp so I can restore my backup but knox is blocking me. Hopefully I can just odin your rom and towelroot and be done with it.
Click to expand...
Click to collapse
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
stoobie-doo said:
Not sure whether you can use Mobile Odin Pro to do that. Extracting the file from the OTA.zip and renaming it from 2400258.cfg to 2400258.zip makes it recognized in MOP, and the options are there to avoid the wipe, but I know earlier OTAs like that did wipe.
Note - I have only gone so far as loading it into MOP; waiting to see if someone more foolhardy than me is willing to actually do it.
Click to expand...
Click to collapse
Tempted to try it (flash through stock recovery) but not my phone lol
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
DocHoliday77 said:
Unless MO is written to specifically handle it, it will probably fail. (Im not sure if it is or isn't)
Sorry if I was misinformed about it wiping data. On TMobile neither OTA's or flashing in Odin ever wipes data. Afaik, Odin will only wipe data if there is a data.img included in the .tar file. Our OTA's have never touched anything but dalvik on the data partition either from what I remember.
Click to expand...
Click to collapse
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Just tried and ADB sideload of this file to my S3. After renaming the .cfg file to .zip.
I get an "assert failed" on "getprop("ro.product.device") == "d2att""
Any suggestions? I'm wondering if the phone is reporting something other than d2att?
So no one tested this via stock recovery? Need to know if the update can be done through stock recovery.
stoobie-doo said:
Let me be more precise; the technique I was talking about is found at http://forum.xda-developers.com/showthread.php?t=1767827 and applies the OTA in a way that wipes. Not sure whether MO would do the same or not; I haven't played with it since the upgrade to 4.3 last year and my memory is hazy.
Click to expand...
Click to collapse
Just tried this method.
I got the assert failure again, and it happily wiped my internal SD but didn't install the OTA.
Good thing I'm not using this device for anything critical, I'd be rather pissed off.
Some tips for those who already took the OG5 OTA update and want root (will be obvious to most of you, and most of this has already been covered in other posts, but some might benefit from this guide with download links included):
1. Copy the BeastMode kernel zip to your phone or SD card.
2. Start Odin3 v3.10.6
3. Place the TWRP tar in the AP slot
4. Uncheck Auto Reboot in the options tab
5. Flash TWRP -- when it's finished flashing, disconnect USB and pull the battery for 10 seconds (on my phone, if I put the battery in too soon, it boots without pressing the power key)
6. Put the battery back in and boot to TWRP
7. Install the modified kernel zip you copied in step 1, and reboot.
8. Since you're in TWRP, might as well clear the cache.
At this point, there are a number of ways to get SuperSU on your phone. My TWRP asked me if I wanted it to install SuperSU, I said yes, but I already had SuperSU installed on my phone, anyway.
You can also use TWRP to install the SuperSU zip.
My phone complained about "KNOX has unfortunately stopped", so I just used Titanium to freeze all the KNOX apps, which cured that.
Be very patient the first time you run apps that request root. It will pop up the "grant" dialog eventually, but sometimes it's slow to do that after a boot.
NOTES: Some users are reporting that TWRP won't load. It may have to do with tripping that reactivation lock with Odin. Once done, it's possible TWRP can't deal with it. So you may be able to get around that by using Odin to install CWM recovery instead of TWRP.
Also, try rebooting recovery again after the flash to make sure the root prompt is clear. If it is booting the system, go into security and disable the reactivation lock.
Still getting the business about slow to wake or launcher not responding? Try adding the line below to end of your build.prop but have one empty line at bottom with no added spaces to the end this line:
ro.HOME_APP_ADJ=1
(thanks to samep for the added info in NOTES)
Will this process work on the Galaxy s5 with og5 5.11
Will this process work on the Galaxy s5 with og5 5.11, I no this is the note section but it appears to be the same build number in the same manufacturer is it possible for someone to report this kernel to the galaxy s5 and root it that way? What exactly is happening here on the note for those of you that wouldn't work on the s5?
Dmary said:
Will this process work on the Galaxy s5 with og5 5.11, I no this is the note section but it appears to be the same build number in the same manufacturer is it possible for someone to report this kernel to the galaxy s5 and root it that way? What exactly is happening here on the note for those of you that wouldn't work on the s5?
Click to expand...
Click to collapse
PM sent.
Sent from my SM-N910P using Tapatalk
So, its been about a year since I rooted a phone, but I feel like I'm missing something at the beginning of the instructions. In the video
https://www.youtube.com/watch?t=32&v=k2oOvf5tOCY
it goes over the auto root process, but that hasn't been updated. Is that something I need to run first anyway? Wouldn't it not work due to the mismatch of android version?
Oh, never mind. It froze at the TWRP screen, but a restart fixed that.
I would like to know if it's possible on the S5 as well...G900V...Everywhere i've read says it's not.
samep said:
PM sent.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
When I try to flash twrp, odin says failed. Any suggestions?
Thanks so much for this guide! Just got a new Note 4 and I'm about to root as well. Is TWRP still giving issues installing? Should I just go with CMW recovery? any other tips would be greatly appreciated. Just want to make sure I cover all bases before I begin...
Newbie_from_NJ said:
Thanks so much for this guide! Just got a new Note 4 and I'm about to root as well. Is TWRP still giving issues installing? Should I just go with CMW recovery? any other tips would be greatly appreciated. Just want to make sure I cover all bases before I begin...
Click to expand...
Click to collapse
TWRP is fine for most. Steps 4, 5 and 6 are important to assure TWRP recovery sticks.
If you decide to flash a custom ROM and get a binary failure, reboot recovery and try again.
Sent from my SM-N910P using Tapatalk
samep said:
Steps 4, 5 and 6 are important to assure TWRP recovery sticks.
Click to expand...
Click to collapse
Step 6, in order to do this, i will need to press button combinations on the phone, correct?
Do you happen to know them? If not, I'm sure Google to the rescue.
Sent from my SM-N910P using Tapatalk
Newbie_from_NJ said:
Step 6, in order to do this, i will need to press button combinations on the phone, correct?
Do you happen to know them? If not, I'm sure Google to the rescue.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
From power off, Vol+, Home + Power.
Sent from my SM-N910P using Tapatalk
I am also curious about whether this would work on a G900V.
Anyone try this on their 920v????
samep said:
PM sent.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Could you please reply about G900V? I would greatly appreciate it.
AcidBurn22 said:
Could you please reply about G900V? I would greatly appreciate it.
Click to expand...
Click to collapse
I sent the PM to not clutter this thread with off-topic discussion.
Sorry, I don't have this phone, nor have I rooted one.
If you need help or don't know where to start, I'd suggest reading thread below before asking in thread:
http://forum.xda-developers.com/showpost.php?p=61688768&postcount=1
Reading through the OP's threads, the same thing started at OE1 update that started here, you can no longer downgrade in Odin once taking this one and later updates; it progressively worsens. Regarding your carrier, it appears that root prior to OG5 update is a prerequisite as well as steps to keep root in the update process (those do not apply here). But I don't claim to know any more about it than you so read, search and ask in the appropriate thread. Best wishes for success; perhaps it's not as grim as I describe it. I only researched a few minutes, following closed threads to links to next thread, starting here:
http://forum.xda-developers.com/showpost.php?p=61682294&postcount=242
If you have a choice, don't take the OE1 update until you're rooted and clear on how to keep root through updates. But again, I'm not claiming to know any more than yourself, possibly less with the effort I gave.
Anyone else finding this through search, please keep this thread on topic. Refer to your specific thread regarding phone model and carrier. Thanks.
Sent from my SM-N910P using Tapatalk
DaggettBeaver said:
Some tips for those who already took the OG5 OTA update and want root (will be obvious to most of you, and most of this has already been covered in other posts, but some might benefit from this guide with download links included):
1. Copy the BeastMode kernel zip to your phone or SD card.
2. Start Odin3 v3.10.6
3. Place the TWRP tar in the AP slot
4. Uncheck Auto Reboot in the options tab
5. Flash TWRP -- when it's finished flashing, disconnect USB and pull the battery for 10 seconds (on my phone, if I put the battery in too soon, it boots without pressing the power key)
6. Put the battery back in and boot to TWRP
7. Install the modified kernel zip you copied in step 1, and reboot.
8. Since you're in TWRP, might as well clear the cache.
At this point, there are a number of ways to get SuperSU on your phone. My TWRP asked me if I wanted it to install SuperSU, I said yes, but I already had SuperSU installed on my phone, anyway.
You can also use TWRP to install the SuperSU zip.
My phone complained about "KNOX has unfortunately stopped", so I just used Titanium to freeze all the KNOX apps, which cured that.
Be very patient the first time you run apps that request root. It will pop up the "grant" dialog eventually, but sometimes it's slow to do that after a boot.
NOTES: Some users are reporting that TWRP won't load. It may have to do with tripping that reactivation lock with Odin. Once done, it's possible TWRP can't deal with it. So you may be able to get around that by using Odin to install CWM recovery instead of TWRP.
Also, try rebooting recovery again after the flash to make sure the root prompt is clear. If it is booting the system, go into security and disable the reactivation lock.
Still getting the business about slow to wake or launcher not responding? Try adding the line below to end of your build.prop but have one empty line at bottom with no added spaces to the end this line:
ro.HOME_APP_ADJ=1
(thanks to samep for the added info in NOTES)
Click to expand...
Click to collapse
Thanks for this. I have Sprint SM-N910P 5.1.1 and want to root to debloat it.
I have rooted my previous phones. Where do I get the OG5 so I can proceed in rooting my Note 4?
Thanks in advance.:good:
Reivaj1803 said:
Thanks for this. I have Sprint SM-N910P 5.1.1 and want to root to debloat it.
I have rooted my previous phones. Where do I get the OG5 so I can proceed in rooting my Note 4?
Thanks in advance.:good:
Click to expand...
Click to collapse
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
samep said:
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I wasn't aware of the latest update, thanks for the heads up.
I have never tried Chainfire auto root. I found Chainfire post http://forum.xda-developers.com/note-4/orig-development/sm-n910-cf-auto-root-t2897428
I'll try this route.
Thank you sir, greatly appreciate it. ???
samep said:
Chainfire auto root for Note 4 has been updated. You could root with that. OK1 is the latest update; no reason to go back to an old update. You can still run a custom OG5 ROM if you like. I just don't recommend going backwards in Odin. Some stock tars just aren't able to flash after more recent updates are taken.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have an issue I'm hoping you could help me with.
I posted this in the Chainfire thread, but have not received any response.
I rooted my Sprint Note 4 SM-N910P via Chainfire Auto Root. With the exception of 1 issue of being stuck in the bootloader where I had to remove the battery and then boot into recovery manually, all went well.
Once it was done and rebooted I got a message during boot, 'Set Warranty Bit: Kernel'
I have SM-N910P 5.1.1 and SU with Titaniun Backup Pro. Reason was to get rid of the bloatware.
I have un-installed the bloatware via TB and the confirmations show they have been deleted with strikethrough but no sooner that I go to check top confirm, they are active with the strikethrough removed.
I also get, out of the blue, prompt to download massive amounts of bloatware I never had to begin with "Sprint Default Configuration: Select to Install New Sprint Default Apps". At first thought it was an update so i downloaded it and along came uber, nba, stock care racing, sprint fun app and sprint international app and a few others.
I tried the same with those, to un-install via TB, and while some have been un-installed, the remaining have not and I get the message prompt to install again.
Anyone idea how I got this and how I can get rid of it?
Reivaj1803 said:
I have an issue I'm hoping you could help me with.
I posted this in the Chainfire thread, but have not received any response.
I rooted my Sprint Note 4 SM-N910P via Chainfire Auto Root. With the exception of 1 issue of being stuck in the bootloader where I had to remove the battery and then boot into recovery manually, all went well.
Once it was done and rebooted I got a message during boot, 'Set Warranty Bit: Kernel'
I have SM-N910P 5.1.1 and SU with Titaniun Backup Pro. Reason was to get rid of the bloatware.
I have un-installed the bloatware via TB and the confirmations show they have been deleted with strikethrough but no sooner that I go to check top confirm, they are active with the strikethrough removed.
I also get, out of the blue, prompt to download massive amounts of bloatware I never had to begin with "Sprint Default Configuration: Select to Install New Sprint Default Apps". At first thought it was an update so i downloaded it and along came uber, nba, stock care racing, sprint fun app and sprint international app and a few others.
I tried the same with those, to un-install via TB, and while some have been un-installed, the remaining have not and I get the message prompt to install again.
Anyone idea how I got this and how I can get rid of it?
Click to expand...
Click to collapse
I believe it was determined that titanium wasn't working correctly due to lack of busybox. OsmOsis wrote a nice script to install busybox that works for systemless root as well as the traditional system root method.
Goto the link below and look for his link to busybox installer and install that in recovery.http://forum.xda-developers.com/showpost.php?p=40409356&postcount=1
If you don't want the custom recovery, use Stericson Busybox in Google Play, instead.
The Sprint apps are likely getting pushed by a root folder /preload You can't freeze this with titanium and how you deal with that may leave indicators to detect that you modified system. Mounting to delete may trigger that and make it not possible to full un-root to take OTA for update. But you could just freeze the preloaded applications after they update. If you use the application manager in Settings, you get the option to remove updates and disable some apps but not all apps. I'm not sure how this applies to preload.
If OTA capability is not of importance, you can consider taking further steps to get a better kernel, make root more stable and modify system and read only partitions for more customization like deleting the preload directory.
So the solution would depend on your preferences. Retain OTA capability with strict SELinux Enforcing mode or go for more customization, not caring for OTA updates but waiting for update stock tar and electing a more stable root with custom kernel? Which would you prefer?
Sent from my SM-N910P using Tapatalk
samep said:
I believe it was determined that titanium wasn't working correctly due to lack of busybox. OsmOsis wrote a nice script to install busybox that works for systemless root as well as the traditional system root method.
Goto the link below and look for his link to busybox installer and install that in recovery.http://forum.xda-developers.com/showpost.php?p=40409356&postcount=1
If you don't want the custom recovery, use Stericson Busybox in Google Play, instead.
The Sprint apps are likely getting pushed by a root folder /preload You can't freeze this with titanium and how you deal with that may leave indicators to detect that you modified system. Mounting to delete may trigger that and make it not possible to full un-root to take OTA for update. But you could just freeze the preloaded applications after they update. If you use the application manager in Settings, you get the option to remove updates and disable some apps but not all apps. I'm not sure how this applies to preload.
If OTA capability is not of importance, you can consider taking further steps to get a better kernel, make root more stable and modify system and read only partitions for more customization like deleting the preload directory.
So the solution would depend on your preferences. Retain OTA capability with strict SELinux Enforcing mode or go for more customization, not caring for OTA updates but waiting for update stock tar and electing a more stable root with custom kernel? Which would you prefer?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I actually did remove and disabled most the apps that I was able to. The rest there were not options, other than root.
My preference was to root, maintain OTA capabilities and remove the bloatware.
What option/s would best suit that preference?