Related
I'm trying to update to 4.1.2 and I'm getting "apply_patch_check("system/lib/libwebrtc_audio_preprocessing.so" as not being the original file.
I have no idea what changed that or how I can return it to normal. Any ideas?
Not enough information.
Was your phone completely stock and unaltered before you tried going to 4.1.2? What method are you using to get to 4.1.2?
garyd9 said:
Not enough information.
Was your phone completely stock and unaltered before you tried going to 4.1.2? What method are you using to get to 4.1.2?
Click to expand...
Click to collapse
I was on stock, then used CF-AutoRoot. Pretty much nothing besides that. According to other threads, if I used voodoo OTA and just unfreeze the AT&T apps it should work, it has for them.
Would this be due to some other root app?
OmegaNemesis28 said:
I was on stock, then used CF-AutoRoot. Pretty much nothing besides that. According to other threads, if I used voodoo OTA and just unfreeze the AT&T apps it should work, it has for them.
Would this be due to some other root app?
Click to expand...
Click to collapse
Okay.. so you were NOT completely stock. You also didn't mention what method you used for the update. Was it pushed to you over the air, or did you download it and copy it to your phone?
If you are following instructions from other threads on the update, then you might consider posting this question on one of those other threads.
I can tell you what *I* did, but I won't support that: I used ODIN to get my phone 100% back to stock (ODIN to replace the stock firmware/kernel/recovery, factory reset to erase the phone) and then installed the update via external SD. After the update was installed, I used ODIN to replace recovery, and then used that recovery to re-root and restore my backups.
Take care
Gary
garyd9 said:
Okay.. so you were NOT completely stock. You also didn't mention what method you used for the update. Was it pushed to you over the air, or did you download it and copy it to your phone?
If you are following instructions from other threads on the update, then you might consider posting this question on one of those other threads.
I can tell you what *I* did, but I won't support that: I used ODIN to get my phone 100% back to stock (ODIN to replace the stock firmware/kernel/recovery, factory reset to erase the phone) and then installed the update via external SD. After the update was installed, I used ODIN to replace recovery, and then used that recovery to re-root and restore my backups.
Take care
Gary
Click to expand...
Click to collapse
Sorry.
And no, I guess not completely stock. Just CF-AutoRoot.
I tried both OTA update and copying the update to my /cache and using ODIN. Where is where I was getting the error.
If I flash back to stock and don't factory reset/erase my phone, would this still fix any modded files like audio_preprocessing in my /system/? Flashing back to a stock ROM won't erase my apps/settings correct? I'm still pretty new to this.
What backup method did you use? ADB nandroid or something like Titanium?
OmegaNemesis28 said:
I tried both OTA update and copying the update to my /cache and using ODIN. Where is where I was getting the error.
Click to expand...
Click to collapse
That statement is confusing. You got the error trying the OTA or when updating via a manual copy to /cache?
OmegaNemesis28 said:
If I flash back to stock and don't factory reset/erase my phone, would this still fix any modded files like audio_preprocessing in my /system/?
Click to expand...
Click to collapse
If you flash back to stock via ODIN, it should completely rewrite everything in /system to revert it back to factory (as well as unroot your device.)
OmegaNemesis28 said:
Flashing back to a stock ROM won't erase my apps/settings correct? I'm still pretty new to this.
Click to expand...
Click to collapse
It shouldn't, but that doesn't mean it won't. That's why I'm a big fan of backing things up.
OmegaNemesis28 said:
What backup method did you use? ADB nandroid or something like Titanium?
Click to expand...
Click to collapse
I have an external memory card and use TWRP (replacement recovery) to backup. I ALSO backup with titanium backup pro to the external sdcard.
Gary
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.
thanks to @NSTar1 for getting the file name...
and thank you to the anonymous donor that sent me the ZVE TOT file to share!!
ZVE TOT file here: LS980ZVE_03.zip
Use this to go directly to stock ZVE then root with Stump. ZVE is now the suggested firmware for every Sprint G2 owner who wants to run on stock. If you are on stock ZVD and just want to manually flash the OTA update instead... keep reading below.
ZVD -> ZVE update can be DOWNLOADED HERE.
Zip can be flashed thru stock recovery (don't try to take OTA with TWRP installed)... If taking OTA from ZVD -> ZVE and you are rooted and also want root in ZVE you must unroot completely before taking OTA and then reroot using Stump! If you do not unroot first, you risk root not working properly when you boot into ZVE.. and Stump will detect you as already rooted and will not attempt to run. To avoid this just be sure to fully unroot by opening SuperSu and going into the Settings/Options and selecting the uninstall root option. Then reboot. Then continue with the OTA.
Directions:
1. Remove USB cable from phone.
2. Power phone off.
3. Press and hold volume down + power until you boot into stock recovery.
4. Select "update with adb"
Rename edde6cf75ecbda8e54a279c5e41a564bed335b6b.ls980zvd_19-ls980zve_03_update.zip file into ls980zvd_19-ls980zve_03_update.zip
Code:
adb sideload LS980ZVD_19-LS980ZVE_03_update.zip
sure there are other ways to manually update... This is just one.
Be sure to unroot before taking OTA then root with Stump after.
Alternate Directions to skip using ADB:
1. Must be rooted... stick OTA zip file in the /cache directory
2. Unroot completely (install SuperSu then use SuperSu settings for full unroot)
3. Power off and boot into stock recovery (vol down + power)
4. Select the Update from cache option... then select the update zip you placed in /cache
OTA Security Rundown:
There was a "security patch" included with this update...
I've confirmed ZVE has blocked IORoot (DATROOT method) properly. ZVD blocked "reboot into recovery" but you could still manually flash DATROOT.zip.
TowelRoot has also been blocked. All new updates from any phone should be blocking futex at this point so this came at no surprise.
PurpleDrake root method for G3 and other LG's does not work on this model.
Stump root the only other LG root left and is confirmed to root ZVE - GET STUMP HERE
Stump root will not run if it detects su/daemonsu files.. even if root is broken. Be sure to unroot before taking ZVE or you will get stuck with broken root and Stump will not run... your only option will be to flash the ZVE TOT and start over fresh.. then root with Stump.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ZVC -> ZVD OTA can be DOWNLOADED HERE
Click to expand...
Click to collapse
hi
You sir are pure greatness!!
autoprime said:
✓✓
Click to expand...
Click to collapse
The file seems to be gone, same for the screen capture
I had ZVD, root, and TWRP. Root was done via AutoRec, and I also had Dorimanx kernel to restore Knock On. After doing the official OTA process, phone boot loops into TWRP. I'll attempt to restore/etc.
hunterintustin said:
The file seems to be gone, same for the screen capture
Click to expand...
Click to collapse
Looks like the filename needs to be capitalized. This links works:
http://android.clients.google.com/p...4bed335b6b.LS980ZVD_19-LS980ZVE_03_update.zip
- 007
"update 3*
ok rather than waste any more time.. just gonna tot back to zvc (can confirm downgrading still works)
then will take ota's up to a 100% stock ZVE. i will then try to root with stump. "
How did you do it to begin with?
There's no way to flash this in TWRP yet correct? So the only way to take it is to tot back and then update right? I saw someone that was rooted and running custom rom/kernel tried to install the update and boot looped but that's to be expected.
If you try to update with custom recovery you will have to tot to get your device to boot.
Taking OTA with custom recovery will disable booting into Android. Unless someone modifies this and makes it flashable you will have to tot and take updates.
rootlinux said:
If you try to update with custom recovery you will have to tot to get your device to boot.
Taking OTA with custom recovery will disable booting into Android. Unless someone modifies this and makes it flashable you will have to tot and take updates.
Click to expand...
Click to collapse
I might .tot and take updates once someone confirms that stump root will work with ZVE.
barleysoda said:
"update 3*
ok rather than waste any more time.. just gonna tot back to zvc (can confirm downgrading still works)
then will take ota's up to a 100% stock ZVE. i will then try to root with stump. "
How did you do it to begin with?
There's no way to flash this in TWRP yet correct? So the only way to take it is to tot back and then update right? I saw someone that was rooted and running custom rom/kernel tried to install the update and boot looped but that's to be expected.
Click to expand...
Click to collapse
I forget how I rooted with ZVC/D to be honest.. but I had confirmed working root before the OTA. Took the OTA.. su and daemonsu remained on the phone yet I could not get a root shell. IORoot is blocked. TowelRoot is blocked. Purpledrake doesn't work. Stump root would try to run but then detect the phone was rooted (it saw su and daemonsu in /system/xbin).
So I just used TOT to get back to ZVC... took ZVC -> ZVD OTA... took ZVD -> ZVE OTA. Ran Stump. Stump worked.
I am not 100% sure if it was just a fluke with me or what... I would say it is risky to take the OTA while rooted and expect to keep root. It may work.. it may not. It WILL work if you UNROOT first.. take OTA.. then root with Stump.
AFAIK, there is no way to flash the OTA with TWRP... but I haven't tried. Though if you have TWRP installed then you would have the downgraded bootstack that works with Loki... so that would not work with the patches in the OTA zip file. They would have to be removed... so only System gets patched.
rootlinux said:
If you try to update with custom recovery you will have to tot to get your device to boot.
Taking OTA with custom recovery will disable booting into Android. Unless someone modifies this and makes it flashable you will have to tot and take updates.
Click to expand...
Click to collapse
If I tot back to ZVC and then run the ZVC to ZVD OTA and then the ZVD to ZVE OTA is there a way to get TWRP back once on ZVE or am I stuck with stock recovery?
EDIT* Has anyone that has tot and then updated to ZVE and then root with Stump tried Autorec to install TWRP?
barleysoda said:
If I tot back to ZVC and then run the ZVC to ZVD OTA and then the ZVD to ZVE OTA is there a way to get TWRP back once on ZVE or am I stuck with stock recovery?
Click to expand...
Click to collapse
barleysoda said:
If I tot back to ZVC and then run the ZVC to ZVD OTA and then the ZVD to ZVE OTA is there a way to get TWRP back once on ZVE or am I stuck with stock recovery?
Click to expand...
Click to collapse
you would need to downgrade your bootstack and patch your boot.img (run autorec) to get TWRP installed... tho that has yet to be confirmed.
if you plan on not flashing any aosp-type roms and just want a twrp to make backups and flash mods in.. I may have something for you later tonight or tomorrow
autoprime said:
you would need to downgrade your bootstack and patch your boot.img (run autorec) to get TWRP installed... tho that has yet to be confirmed.
if you plan on not flashing any aosp-type roms and just want a twrp to make backups and flash mods in.. I may have something for you later tonight or tomorrow
Click to expand...
Click to collapse
Thanks Prime, I don't run ASOP roms but I do run the stock ones and 2faced ZVD. I am waiting to see if autorec works with ZVE so that I can get TWRP back and mostly run backups, mods and stock based roms.
I am running ZVD stock rom, rooted, wifi tether mod and SIM unlock mod. Can I just run this update zip and keep everything all that? Also, does this update like Windows would update (keeping all programs and settings) or does this perform a full wipe?
ChrisFSU said:
I am running ZVD stock rom, rooted, wifi tether mod and SIM unlock mod. Can I just run this update zip and keep everything all that? Also, does this update like Windows would update (keeping all programs and settings) or does this perform a full wipe?
Click to expand...
Click to collapse
If you are rooted you need to unroot.
If you have a custom recovery it will probably crash your device.
If you have lots of mods or removed some important files it may crash your device.
Best thing to do is back up your device, move backup to PC.
TOT back to stock then take ota updates. No one has reported success with root on ZVE so I would hold off.
If you can gain root then run autorec and move backup back to device.
Restore data partition only as a system restore will effect the updated files and cause issues.
Just my thoughts on it.
Sounds easy enough.
rootlinux said:
If you are rooted you need to unroot.
If you have a custom recovery it will probably crash your device.
If you have lots of mods or removed some important files it may crash your device.
Best thing to do is back up your device, move backup to PC.
TOT back to stock then take ota updates. No one has reported success with root on ZVE so I would hold off.
If you can gain root then run autorec and move backup back to device.
Restore data partition only as a system restore will effect the updated files and cause issues.
Just my thoughts on it.
Click to expand...
Click to collapse
great advice from top to bottom.. except where you mention no one reporting ZVE root. In OP I mention I have confirmed root with Stump.
but as you said.. you should unroot first. must have stock recovery. all system mods(including tether) must be reversed or the system check will fail before the OTA even tries to patch in the update. SIM unlock should be fine.. unless u edited the build.prop.. if so you must put the build.prop back to how it was exactly.
or u can tot back to zvc.. then ota to zvd then zve then root.
the update works by checking your system partition to make sure it's untouched. the updates are patches... so the original file must be exact for the patch to work. this is why OTA fails if you change system files... it sees an md5 of one of the files is bad and aborts the update before the patching even starts.
after system is confirmed to be perfect and match all md5 sums.. system gets patched.. then recovery and boot get flash.. then the bootloader and modem gets updated. OTA.. data does NOT get wiped. but if you tot back to zvc it WILL get wiped.
How can i update this via sd card? I put it on the internal memory and it still won't show up when I select that option.
_Epic said:
How can i update this via sd card? I put it on the internal memory and it still won't show up when I select that option.
Click to expand...
Click to collapse
not sure if that works... you could put it into /cache and choose that method tho. root would be needed of course.
autoprime said:
not sure if that works... you could put it into /cache and choose that method tho. root would be needed of course.
Click to expand...
Click to collapse
Stock recovery gives me the option to install via sd card. It also gives me a install via cache. and then the adb method. I guess I will just wait to automatically receive the update. I can't seem to get ADB to ever work on my computer.
_Epic said:
Stock recovery gives me the option to install via sd card. It also gives me a install via cache. and then the adb method. I guess I will just wait to automatically receive the update. I can't seem to get ADB to ever work on my computer.
Click to expand...
Click to collapse
right.. but i think it wants external sdcard.. which we dont have. that.. or the file needs to be named something specific.. maybe just "update.zip" ?
you arent rooted? if you root you can use root explorer or es file explorer to put the update in /cache/ and then you can update without adb. or you can step your adb game up! comes in handy sometimes.
When you get and accept the ota update it downloads into your storage, would it be possible to use the stock recovery to find it and reinstall?
Pp.
PanchoPlanet said:
When you get and accept the ota update it downloads into your storage, would it be possible to use the stock recovery to find it and reinstall?
Pp.
Click to expand...
Click to collapse
Can't you pull the recovery.img out?
Sent from my SM-G925T using XDA Free mobile app
Sorry but I don't pull anything.
I just download.
Pp.
I've posted the G925T's OF6 stock recovery over in the OP of this thread. Is that what you're looking for?
Aou said:
I've posted the G925T's OF6 stock recovery over in the OP of this thread. Is that what you're looking for?
Click to expand...
Click to collapse
Was wondering if I find ota download that I accepted when I updated, can I use that downloaded ota file and use stock recovery to reinstall update.
When you accept ota a file is download into your storage (don't know where ) just wanted to find and reflash.
After ota phone went from great to awesome, but decided to play with smartswitch and reinstall / restore after back up, but after restore I lost the ability to disable tmobile my account app.
After ota I had the ability to disable, after smartswitch no option to disable? ???
Pp. Thanks for input.
Still no answer to my question. ???
Pp.
PanchoPlanet said:
Was wondering if I find ota download that I accepted when I updated, can I use that downloaded ota file and use stock recovery to reinstall update.
When you accept ota a file is download into your storage (don't know where ) just wanted to find and reflash.
After ota phone went from great to awesome, but decided to play with smartswitch and reinstall / restore after back up, but after restore I lost the ability to disable tmobile my account app.
After ota I had the ability to disable, after smartswitch no option to disable? ???
Pp. Thanks for input.
Click to expand...
Click to collapse
Sorry, I must have accidentally marked this as "Read" or something.
To answer the first question: no. Even if you found the OTA update.zip, it's useless once you are already updated. The update.zip files only contain patches for files, and patches for whole partitions. The first thing it does is check to see what version you currently have, and if it doesn't match what it's expecting, it will abort. Past that, even if you fool it somehow, it verifies every single file that it is going to patch. If it finds something it is not expecting, it will abort.
As for disabling the T-Mobile app, I don't really know. I think on 5.0.2 I disabled it, but then I rooted right away and started freezing all the bloat soon after. On 5.1.1 leak, I think I still had that disabled. By the time OF6 came around, I believe it was still disabled. Don't know for sure now, because I'm rooted again and have all this stuff frozen with TiBu.
As the title suggests, my LG G4 is having some trouble taking the 13B update. I am rooted, but still very stock.
I've narrowed down the problem file and I really just want some advice on it, I can fix it but I need to know what the repercussions of the fix will be...
According to the logs in /cache/fota the problem file is app_process64. Upon inspection, something has modified it and nicely backed it up. By modified I mean it's a 0-Byte dummy file, with a 17 KB original file next to it. Of course the obvious fix for the OTA is to restore the original, which is how I fixed the last OTA I had trouble with, but I need to know what might have done this in the first place, and is it safe to undo using root browser?
I am, as always, fully prepared to lose everything and start over with my Titanium Backups and copy of my /sdcard.
EDIT: Looked closer and it appears to have been modified 9/18/15. The file I fixed for the last OTA to work (install-recovery.sh) is also a 0-Byte dummy with a backup again. Weird.
The only thing I can think of that would mess with the system like that is busybox, and I do see that the dummies are symlinked to ../xbin/daemonsu so maybe I should try unistalling the busybox applets.
EDIT 2: It wasn't busybox, and I'm not willing to unroot to test if it was supersu. I'm just going to go for it. Wish me luck.
EDIT 3: Well I guess it was required to be like that for root. After restoring the backups and rebooting SuperSU reports no binaries and closes. *Sigh* At least the OTA worked. But I guess now I need to find a 13B Stock Rooted image to get my root back, right?
Yep, you cannot be rooted or have modified system files, so solutions would include to find and flash an unrooted system image, or find and flash a rooted, 13B image or what you did - unroot step by step.
You can either find and flash one of the many rooted 13B images or take your current image and use the root injection method to make it rooted, then flash it.
Backup your current rooted image as cheap insurance and leave it on internal storage until you very the rooted image is good.
divineBliss said:
Backup your current rooted image as cheap insurance and leave it on internal storage until you very the rooted image is good.
Click to expand...
Click to collapse
Good advice... but how would I backup the system if I have no root?
Starcruiser322 said:
Good advice... but how would I backup the system if I have no root?
Click to expand...
Click to collapse
Look for the "low effort root" G4 thread that refers to using the "dd" command to dump the system partition to internal storage.
Post a link here when you find it.
EDIT: HERE http://forum.xda-developers.com/g4/orig-development/root-tmo-vzw-intl-variants-soon-root-lg-t3164765
That thread refers to another thread that has the dd command you need to backup your system image.