Hello, I downloaded the 4.3 update file and sought to update, but the install failed. I am running a stocked rooted version of the previous tw rom.
After the install failed, I have decided to stay with my current setup and not take the update.
Is there anyway to delete the 4.3 update file that I downloaded? Thanks in advance!
Sent from my SCH-I535 using xda app-developers app
banditsw said:
Hello, I downloaded the 4.3 update file and sought to update, but the install failed. I am running a stocked rooted version of the previous tw rom.
After the install failed, I have decided to stay with my current setup and not take the update.
Is there anyway to delete the 4.3 update file that I downloaded? Thanks in advance!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
The update file is located at /cache/fota/update.zip . To kill the OTA update for the time being, locate the following files in /system/app, SDM.apk and SDM.odex, and rename them to SDM.apk.bak and SDM.odex.bak, then reboot the phone. If some time in future, you want to allow the update to happen, you just need to remove the .bak from those files, and reboot.
GMPOWER said:
The update file is located at /cache/fota/update.zip . To kill the OTA update for the time being, locate the following files in /system/app, SDM.apk and SDM.odex, and rename them to SDM.apk.bak and SDM.odex.bak, then reboot the phone. If some time in future, you want to allow the update to happen, you just need to remove the .bak from those files, and reboot.
Click to expand...
Click to collapse
Thanks for the reply. I checked the file that you reference, but there is no zip file in there; it's empty. Would you know why it seems to have disappeared?
Thank you!
banditsw said:
Thanks for the reply. I checked the file that you reference, but there is no zip file in there; it's empty. Would you know why it seems to have disappeared?
Thank you!
Click to expand...
Click to collapse
The system would have deleted it after the failed install.
GMPOWER said:
The system would have deleted it after the failed install.
Click to expand...
Click to collapse
thank you...I tried to install the update after reverting back to stock recovery via ez-recovery and locking the bootloader via ez-unlock.
However, the update install failed. Are people who are taking the ota using ODIN first to get back to stock firmware and then take the OTA?
I am running stock rooted TW...thanks.
banditsw said:
thank you...I tried to install the update after reverting back to stock recovery via ez-recovery and locking the bootloader via ez-unlock.
However, the update install failed. Are people who are taking the ota using ODIN first to get back to stock firmware and then take the OTA?
I am running stock rooted TW...thanks.
Click to expand...
Click to collapse
You do realize that taking the OTA will lock your bootloader forever, right?
If you wait a little bit a dev will release a stock/rooted 4.3 TW ROM that you can run with our precious insecure bootloader.
But to answer your question, yes, you most likely have to ODIN back to a previous stock firmware and then take all the OTAs from wherever you are. Apparently if you make any kinds of changes to /system the OTA will fail.
Related
I know if I update i'll lose my root but what i'm not sure of is whether I'll lose my apps and game progress/saves etc.
Does anyone know?
Thanks
You won't lose any data or game progresses.
Sent from my Nexus S using Tapatalk
Just got the OTA today, installed and running....I didn't lose the root. Everything else stays the same.
vennstrom said:
Just got the OTA today, installed and running....I didn't lose the root. Everything else stays the same.
Click to expand...
Click to collapse
Really? When I updated from 2.3.2 to 2.3.4 I lost root so I assumed this would occur again (for the OTA update).
vennstrom said:
Just got the OTA today, installed and running....I didn't lose the root. Everything else stays the same.
Click to expand...
Click to collapse
You lost root. You need to flash superuser again.
Sent from my Nexus S 4G using xda premium
yup...my bad, didn't check properly. I assumed it was not just by looking at superuser without trying.
Update: Rooted again now ^_^
vennstrom said:
yup...my bad, didn't check properly. I assumed it was not just by looking at superuser without trying.
Update: Rooted again now ^_^
Click to expand...
Click to collapse
How did you rooted again? Just flash the su.zip?
Hey guys I have a question.
I received my ota update today. It says that it's downloaded and ready to install on reboot. However I want to save the update prior to this. Where is it located on the phone? Reason being that I have a custom kernel installed and I want to 1) revert to my stock 2.3.4 nand backup 2) install 2.3.6 update 3) root again 4) make a stock 2.3.6 nand backup 5) install custom kernel again and see if it works
I already tried searching with astro on / for update,aosp, 2.3.6 but so far no hits..
alexxdj said:
How did you rooted again? Just flash the su.zip?
Click to expand...
Click to collapse
So I can DL the official OTA update and just flash the su.zip? Where to I download the appropriate su.zip file?
dccxviii said:
So I can DL the official OTA update and just flash the su.zip? Where to I download the appropriate su.zip file?
Click to expand...
Click to collapse
alexxdj said:
How did you rooted again? Just flash the su.zip?
Click to expand...
Click to collapse
Just flash the su from CWR
I got it from here: http://forum.xda-developers.com/showpost.php?p=17033340&postcount=819
Version 3 in the market is not stable according to some user
Hi everyone,
Las week the OTA update appeared in my phone. I tried to use the google-automatic procedure, but as I have my Nexus 5 rooted, the install was aborted as soon as the device was restarted.
I read the helpdesk thread, trying to update the device manually, but I can't be able to.
I have the 4.4 to 4.4.2 .zip file inside the downloads folder, I restart the device to recovery mode (I've installed TWRP), and after writing the decrypt password and mount the volume, When I try to apply the zip file
"/system/app/EmailGoogle.apk" has unexpected co
E: Error executing update binary in zip '/sdcar
Error flashing zip '/sdcard/Download/b3d1f30762
Updating partition details..
Note that the senteces is cut due to the lenght of the screen.
Before flashing, I go to mount option, and mount all the folder (system, firmware, sdcard)
Any ideas?
Now I'm thinking that when I rooted the device, I used ES File Explorer to delete some apps directly from /sys/apps, maybe is that the error, that some GApps has been removed from the device.
Thank you!
Yes Google has nicely written in app checks. If these apps are not present on check the update is aborted
Sent from my Nexus 5 using Tapatalk
So I have to reinstall the GApps package, and try to apply de update?
http://forum.xda-developers.com/showthread.php?p=26914
Sent from my Nexus 5 using Tapatalk
you modified the system apps.. what did you think was going to happen? everything would update fine?
this has been documented all over the forums. if you want the OTA, stop modifying your system or keep backups of what you modified.
Ben36 said:
http://forum.xda-developers.com/showthread.php?p=26914
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Link not valid, but thank you, I will install GApps
Zepius said:
you modified the system apps.. what did you think was going to happen? everything would update fine?
this has been documented all over the forums. if you want the OTA, stop modifying your system or keep backups of what you modified.
Click to expand...
Click to collapse
That's true, sorry... Well I gonna reinstall GApps and try to update OTA.
Thank you for fast reply!
Deiwor said:
Link not valid, but thank you, I will install GApps
That's true, sorry... Well I gonna reinstall GApps and try to update OTA.
Thank you for fast reply!
Click to expand...
Click to collapse
Flashing gapps is not going to help you. You need to fastboot flash the system and boot image from the factory image
jd1639 said:
Flashing gapps is not going to help you. You need to fastboot flash the system and boot image from the factory image
Click to expand...
Click to collapse
Oh, really? Damn.... Well then I will start from scratch next weekend, or find the way to hide the update.
Thank you jd1639
Deiwor said:
Oh, really? Damn.... Well then I will start from scratch next weekend, or find the way to hide the update.
Thank you jd1639
Click to expand...
Click to collapse
Flashing the system and boot images isn't starting from scratch... you can keep your userdata as long as you aren't using a custom ROM. Flashing those just gives you back a clean stock OS without any of your mods. No need to start from scratch. Should only take a couple minutes.
Also, your mods are the reason it failed in the first place, not because you were rooted. Rooting itself does not prevent OTA updates.
I'm trying to apply the OTA upgrade to my rooted UK Retail Moto G running 4.3. The upgrade keeps failing, even if I disable root using the option in SuperSU. Is there some step I am missing out, or must I use a clean flash and lose all my configuration? (The phone was rooted using the superboot method, and had Xposed framework, but this had been removed using the Xposed framework app.) Thanks.
What exactly does fail?
There should be an error message when you try to flash the OTA.
Look at the screen and report back, the boot.img you flashed to get root on your phone shouldn't have any impact on the update procedure.
CassandraN said:
I'm trying to apply the OTA upgrade to my rooted UK Retail Moto G running 4.3. The upgrade keeps failing, even if I disable root using the option in SuperSU. Is there some step I am missing out, or must I use a clean flash and lose all my configuration? (The phone was rooted using the superboot method, and had Xposed framework, but this had been removed using the Xposed framework app.) Thanks.
Click to expand...
Click to collapse
I am in the exact same situation i unrooted and uninstalled xposed and it fails shortly after the progress bar appears i tried twice and same in gonna flash the boot.img and recovery.img out of the factory img later and try again.
Same here I removed root update downloads then install fails It don't tell you why it failed.
Sent from my XT1032 using XDA Premium 4 mobile app
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
I spoke to Motorola and she said I may not be able to update if my bootloader is unlocked
Sent from my XT1032 using XDA Premium 4 mobile app
+1 Phone downloads the update. Restarts and gives "error". Phone is unlocked and rooted.
You either have to restore all the stock things you modified - boot / recovery OR save the OTA, flash stock and put the OTA again into the sdcard, restart and voila
darkeingel said:
You either have to restore all the stock things you modified - boot / recovery OR save the OTA, flash stock and put the OTA again into the sdcard, restart and voila
Click to expand...
Click to collapse
Do you know where i can find the "14.71.8.falcon_umts.Retail.en.GB" file to restore my uk moto G to stock without root?
I can find only the US retail files in android dev section.
PS: thanks found it
deadpunk said:
Do you know where i can find the "14.71.8.falcon_umts.Retail.en.GB" file to restore my uk moto G to stock without root?
I can find only the US retail files in android dev section.
PS: thanks found it
Click to expand...
Click to collapse
I used pauls root method 2 to root with a modified recovery i bet that's why it fails the update ill post my findings later after i flash unmodified stock recovery for anyone who's situation is the same as mine.
Skinpipe said:
I used pauls root method 2 to root with a modified recovery i bet that's why it fails the update ill post my findings later after i flash unmodified stock recovery for anyone who's situation is the same as mine.
Click to expand...
Click to collapse
I had to use method 2 to root too, and mine is also failing to update... :/ keep us informed!
xTx
darkeingel said:
You either have to restore all the stock things you modified - boot / recovery OR save the OTA, flash stock and put the OTA again into the sdcard, restart and voila
Click to expand...
Click to collapse
Well I've been able to reverse everything but the original superboot root itself. Does anyone know how that might be reversed?
CassandraN said:
Well I've been able to reverse everything but the original superboot root itself. Does anyone know how that might be reversed?
Click to expand...
Click to collapse
Flashing the boot.img from a stock firmware - from the specific firmware that you are running now even.
darkeingel said:
Flashing the boot.img from a stock firmware - from the specific firmware that you are running now even.
Click to expand...
Click to collapse
boot.img is the kernel, you only need to flash back a stock kernel if you have flashed a custom one earlier.
The superboot method does not alter the kernel, it just does some magic one-time boot that roots the phone (ie alters files in /system). You still have the original kernel in place. superboot just flashes superSU. superSU is the app itself plus certain /system file addtions and alterations.
To remove root all the /system files that rooting updates must be set back to how they were, the updater does a checksum on the files and if they differ from what they should be then the update fails.
superSU for example modifies /system/etc/install-recovery.sh as well as adding new files to /system. So /system/etc/install-recovery.sh would need to be put back to how it was.
Depending on which files the superboot method uses will depend on which files need altering back.
In general you are going to want to flash back stock /system as thats easiest (or maybe you did a nandroid and can restore /system from that).
ok, got 4.4.2 installed now
retail 8GB unlocked using Paul's method 2.
uninstalled SuperSU using the option within the app's settings
used the guide here: http://forum.xda-developers.com/showthread.php?t=2542219 to flash the stock retail gb 4.3 rom, then copied the retail gb OTA update file (found here http://forum.xda-developers.com/showthread.php?p=49390749 ) to the sdcard root and performed the update in settings -> about phone -> system update
now going to see if titanium backup worked!
xTx
tee_pot said:
ok, got 4.4.2 installed now
retail 8GB unlocked using Paul's method 2.
uninstalled SuperSU using the option within the app's settings
used the guide here: http://forum.xda-developers.com/showthread.php?t=2542219 to flash the stock retail gb 4.3 rom, then copied the retail gb OTA update file (found here http://forum.xda-developers.com/showthread.php?p=49390749 ) to the sdcard root and performed the update in settings -> about phone -> system update
now going to see if titanium backup worked!
xTx
Click to expand...
Click to collapse
Thats good. So SuperSU basically cleans itself up and reverts all /system files it changed back to their original values. Easier than restoring a stock /system.
CassandraN said:
Well I've been able to reverse everything but the original superboot root itself. Does anyone know how that might be reversed?
Click to expand...
Click to collapse
Unroot using the supersu app if that's what you mean you cant do
tee_pot said:
ok, got 4.4.2 installed now
retail 8GB unlocked using Paul's method 2.
uninstalled SuperSU using the option within the app's settings
used the guide here: http://forum.xda-developers.com/showthread.php?t=2542219 to flash the stock retail gb 4.3 rom, then copied the retail gb OTA update file (found here http://forum.xda-developers.com/showthread.php?p=49390749 ) to the sdcard root and performed the update in settings -> about phone -> system update
now going to see if titanium backup worked!
xTx
Click to expand...
Click to collapse
Same thing here. Uk retail Moto G 8Gb, restore back to 4.3 stock, copy the OTA to sdcard and go to system update...
Phone will ask to copy OTA, just tap yes and install now...
Skinpipe said:
Unroot using the supersu app if that's what you mean you cant do
Click to expand...
Click to collapse
Yes you can, superSU has an 'unroot' option. On another thread Im sure someone had issues with it as it left some junk lying behind, but for the poster in this thread it seems to have worked fine.
---------- Post added at 01:15 PM ---------- Previous post was at 01:10 PM ----------
deadpunk said:
Same thing here. Uk retail Moto G 8Gb, restore back to 4.3 stock, copy the OTA to sdcard and go to system update...
Phone will ask to copy OTA, just tap yes and install now...
Click to expand...
Click to collapse
if you restore entirely back to stock, ie stock recovery as well, then waiting for the OTA to download the 'offical' way may be better. This will then update not just Android but your stock recovery as well. Im unsure if installing from the sdcard updates the radios (ie mobile radios) or not. If not then again installing the officiall way may be better.
If someone on here knows if the mobile radios get updated I'd like to know. I see many /modem files in the update.zip. Its these Im interested in whether they get flashed or not when using the sdcard method.
rooted 4.4.2 now working:
followed the guide http://forum.xda-developers.com/showthread.php?t=2563599&highlight=mismatched to install CWM recovery
downloaded the latest SuperSU from http://download.chainfire.eu/376/SuperSU/ , copied to root of the sdcard and installed using CWM
titanium backup (free version) worked a charm, only thing it seems it didn't backup was my live wallpaper choice! bit of a pain to have to click "install" and "done" on each app (all 181 of them!) but much quicker than reinstalling and setting them up again from the Play store
now to have a play with my new kitkat!
xTx
EDIT: incidentally, where does it show what bootloader is being used? can't see anything in phone settings or fastboot...
tee_pot said:
ok, got 4.4.2 installed now
retail 8GB unlocked using Paul's method 2.
uninstalled SuperSU using the option within the app's settings
used the guide here: http://forum.xda-developers.com/showthread.php?t=2542219 to flash the stock retail gb 4.3 rom, then copied the retail gb OTA update file (found here http://forum.xda-developers.com/showthread.php?p=49390749 ) to the sdcard root and performed the update in settings -> about phone -> system update
now going to see if titanium backup worked!
xTx
Click to expand...
Click to collapse
do any of these steps wipe data and/or apps?
cause I'd like to avoid that but disabling superuser from app doesn't fix the problems of the update failing
-sandro- said:
do any of these steps wipe data and/or apps?
cause I'd like to avoid that but disabling superuser from app doesn't fix the problems of the update failing
Click to expand...
Click to collapse
Are you just disabling superSU or are you actually choosing the option to unroot, ie the option in superSU that says:
Full unroot
Cleanup for permanent unroot
If you do this is should remove root and put all /system files back as they were (ie the ones it altered during root).
Also I assume you have not modifed any system apps yourself, eg installed newer versions etc or removed any? If you have then again the update wont work. The update checks lots of files to ensure they have not been modified before it does the update.
I am S-off and rooted on Verizon. What file or files do I have to freeze via TBU to not get the soon to be released update ?
Thanks in advance
jjmstang said:
I am S-off and rooted on Verizon. What file or files do I have to freeze via TBU to not get the soon to be released update ?
Thanks in advance
Click to expand...
Click to collapse
delete or rename from .apk to .bak
system/app
HtcOMADM_SettingsPlugin_VZW.apk
HtcOMADM_VZW.apk
jjmstang said:
I am S-off and rooted on Verizon. What file or files do I have to freeze via TBU to not get the soon to be released update ?
Thanks in advance
Click to expand...
Click to collapse
A custom recovery like CWM or TWRP should also cause the update to fail.
Okay thanks for the quick responses
Figured I'd add on to these answers.
Modifying anything will pretty much mess up the OTA's. As far as I know if everything is not 100% stock (besides S-OFF & bootloader unlock) then the update will fail.
Root your phone = failed update
Custom recovery = failed update
Edit a file in /system (add a line or remove a line or change 0 to 1 in something) = failed update
Etc
Can't you just freeze the Updater 6. whatever with titanium?
Mudvayne622 said:
Can't you just freeze the Updater 6. whatever with titanium?
Click to expand...
Click to collapse
Yes, that will prevent a nag, but it would still allow you to manually update it in settings.
I'd follow what Andy said, then it's for sure unable to update
Sent from my HTC6525LVW using Tapatalk
---------- Post added at 04:13 PM ---------- Previous post was at 04:07 PM ----------
S1L3nTShaDoWz said:
Figured I'd add on to these answers.
Modifying anything will pretty much mess up the OTA's. As far as I know if everything is not 100% stock (besides S-OFF & bootloader unlock) then the update will fail.
Root your phone = failed update
Custom recovery = failed update
Edit a file in /system (add a line or remove a line or change 0 to 1 in something) = failed update
Etc
Click to expand...
Click to collapse
This is mostly true, but sometimes the overall update will fail but bits and pieces of it will actually pass. This is exactly what you don't want.
For example, a new bootloader would pass, but the system and the recovery push would fail. This could potentially lock your bootloader. It's still better to stop the update without giving it a chance to install, despite having root and a custom recovery.
Sent from my HTC6525LVW using Tapatalk
Dougau said:
A custom recovery like CWM or TWRP should also cause the update to fail.
Click to expand...
Click to collapse
It will cause it not to install, but won't stop the nag to install the OTA.
Can't you stop it by going into About/software update and unchecking auto download?
Thanks I wasn't sure. This is my first HTC (former Motorola fan). Even once the developers get ahold of the update and create a flashable zip for us do we still need to put the stock recovery back or flash the update.zip in custom recovery? I'm S-Off, BL unlocked and rooted with TWRP.
---------- Post added at 08:06 PM ---------- Previous post was at 08:01 PM ----------
OdinValknir said:
Can't you stop it by going into About/software update and unchecking auto download?
Click to expand...
Click to collapse
Once I saw this I was curious about that option. But every time I go into About/Software Update, settings crashes. Maybe due to Sense 6 Toolbox in my settings menu?
I'm not 100% sure... I am actually curious about all this too... This phone is the first and only phone I've ever unlocked/rooted/ S-off etc.... I'm currently running Venom Viper ONE ROM on Here and have neglected to flash the most current version bc it's based on 4.3
I'm still waiting to see how it all pans out... And clueless as to how to update kitkat once it does come through... Whether I can do it manually... Or if I have to go back to stock sense 6 so on and so forth... Guess we shall see
OdinValknir said:
I'm not 100% sure... I am actually curious about all this too... This phone is the first and only phone I've ever unlocked/rooted/ S-off etc.... I'm currently running Venom Viper ONE ROM on Here and have neglected to flash the most current version bc it's based on 4.3
I'm still waiting to see how it all pans out... And clueless as to how to update kitkat once it does come through... Whether I can do it manually... Or if I have to go back to stock sense 6 so on and so forth... Guess we shall see
Click to expand...
Click to collapse
You can do it manually through fastboot, all you're going to want to update is the firmware.
Sent from my HTC6525LVW using Tapatalk
BadUsername said:
You can do it manually through fastboot, all you're going to want to update is the firmware.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Through fastboot? I have never seen an option for firmware or update in fastboot... Again.. forgive me I am still relatively new to all this
OdinValknir said:
Through fastboot? I have never seen an option for firmware or update in fastboot... Again.. forgive me I am still relatively new to all this
Click to expand...
Click to collapse
It's not going to update the rom, but it'll update your baseband and other firmware, you can package it in a flashable zip and flash it in a custom recovery or with the fastboot flash command.
Sent from my HTC6525LVW using Tapatalk
andybones said:
delete or rename from .apk to .bak
system/app
HtcOMADM_SettingsPlugin_VZW.apk
HtcOMADM_VZW.apk
Click to expand...
Click to collapse
Will renaming the files with ES File Explorer work instead of TBU. I had to schedule the update for later this evening, hoping that I can rename with ES and be done with it.
GarnerArms said:
Will renaming the files with ES File Explorer work instead of TBU. I had to schedule the update for later this evening, hoping that I can rename with ES and be done with it.
Click to expand...
Click to collapse
Yessir, just rename to .bak rather than .apk
Awesome. Do I need to rename both or just the setting plug-in?
Sent from my HTC6525LVW using XDA Free mobile app
BadUsername said:
Yes, that will prevent a nag, but it would still allow you to manually update it in settings.
I'd follow what Andy said, then it's for sure unable to update
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
FYI: I froze the updater w/ TBU and the nag continued to....nag. I renamed the APK files and so far so good.
andybones said:
Yessir, just rename to .bak rather than .apk
Click to expand...
Click to collapse
Andy, good to see you on here with the M8
I had the G3 for a couple weeks...it was ok I guess, but I already have a tablet. Ha, needed to be able to hold my phone with one hand. G3 is overrated!
I'm about to root and I'll be sure to try out any ROMs you have made for the M8!!
S1L3nTShaDoWz said:
Figured I'd add on to these answers.
Modifying anything will pretty much mess up the OTA's. As far as I know if everything is not 100% stock (besides S-OFF & bootloader unlock) then the update will fail.
Root your phone = failed update
Custom recovery = failed update
Edit a file in /system (add a line or remove a line or change 0 to 1 in something) = failed update
Etc
Click to expand...
Click to collapse
I was rooted with weaksauce and it pestered me with the update relentlessly. Every time I turned on the phone I had to click a bunch of junk to get rid of it. Unfortunately I did not realize this was a full OS update, it just mentioned updating to the fancy charging thing and clicked "yes" to be rid of the annoyance. As soon as I clicked it my phone rebooted and I knew I was in trouble. Lost root and can't get it back without paying for sunshine. I'm poor!
I managed to pull the 5.0 Lollipop OTA update file and load it to Android File Host.
Word of warning, should you try to use this file to update, you will likely lose root, possibly without the chance to root once complete or even ODIN back to 4.x. This is primarily for devs to use to try to make pre-rooted and custom ROMs with.
The link to the file is below:
https://www.androidfilehost.com/?fid=95916177934552137
@muniz_ri, @RockRatt, @iB4STiD and @Joe-Tech, I believe you guys may be interested in this.
May the odds ever be in our favor.
@Apoplectic1 you awesome man, will see what i can do with it
Doesn't flash, wipes /Data stating "Footer is wrong"
Apoplectic1 said:
I managed to pull the 5.0 Lollipop OTA update file and load it to Android File Host.
Word of warning, should you try to use this file to update, you will likely lose root, possibly without the chance to root once complete or even ODIN back to 4.x. This is primarily for devs to use to try to make pre-rooted and custom ROMs with.
The link to the file is below:
https://www.androidfilehost.com/?fid=95916177934552137
@muniz_ri, @RockRatt, @iB4STiD and @Joe-Tech, I believe you guys may be interested in this.
May the odds ever be in our favor.
Click to expand...
Click to collapse
Thanks for the heads up. I will create the ROM later tonight.
DankHeals said:
Doesn't flash, wipes /Data stating "Footer is wrong"
Click to expand...
Click to collapse
It's not a flashable zip. Even if you were to flash it, it would not be able to update you due to you being rooted, it will fail I'm afraid.
muniz_ri said:
Thanks for the heads up. I will create the ROM later tonight.
Click to expand...
Click to collapse
I've probably told you this about a dozen times now, but you are the man! :highfive:
Apoplectic1 said:
I've probably told you this about a dozen times now, but you are the man! :highfive:
Click to expand...
Click to collapse
No worries and thanks for capturing the ota.
Apoplectic1 said:
It's not a flashable zip. Even if you were to flash it, it would not be able to update you due to you being rooted, it will fail I'm afraid.
Click to expand...
Click to collapse
I fully unrooted and went stock before attempting, but that's a shame. Thought it would be flashable via update in stock recovery. :/
cant wait to have this flashable.. been waiting soooo long
When O when will the wait end.... Canada S4 and I still can't install this AT&T one
How to use this file ???
DankHeals said:
Doesn't flash, wipes /Data stating "Footer is wrong"
Click to expand...
Click to collapse
Because you flashed the archived cfg file. To flash the update you have to unpack the zip file and change the extension of the CFG file to ZIP. But anyway even this cfg fails to install, so don't try because i already did.
Update via adb or external sd card using stock recovery doesn't work !
Is there a way to flash it ???
lordnihilusmd said:
Because you flashed the archived cfg file. To flash the update you have to unpack the zip file and change the extension of the CFG file to ZIP. But anyway even this cfg fails to install, so don't try because i already did.
Update via adb or external sd card using stock recovery doesn't work !
Is there a way to flash it ???
Click to expand...
Click to collapse
Thanks for the info... been looking for a way to flash this without success
W1zz_ said:
Thanks for the info... been looking for a way to flash this without success
Click to expand...
Click to collapse
You could try pushing the cfg file to /cache/fota, uninstall Safestrap, full unroot, reboot and then installing the update the standard way, but getting root afterward is iffy.
Can somebody pull out the modem?
Apoplectic1 said:
You could try pushing the cfg file to /cache/fota, uninstall Safestrap, full unroot, reboot and then installing the update the standard way, but getting root afterward is iffy.
Click to expand...
Click to collapse
Thanks man, my situation is a little more complicated however since I have the i337m(Canadian S4) wasn't sure I'd be able to install this OTA in any way. Kind of came to the conclusion that I will have to wait for a custom Rom, unless my understanding of how this all works is wrong.
I will try but i already did full unroot . When flashing via recovery it says something like frameworkres-apk has unexpected content ... Standard way ? but it will tell me software update interrupted
Apoplectic1 said:
It's not a flashable zip. Even if you were to flash it, it would not be able to update you due to you being rooted, it will fail I'm afraid.
Click to expand...
Click to collapse
It won't flash even without root. Tried flashing via stock recovery, no dice just like the others. Flashing results in wiping /data.
Short road...
Easiest way possible odin back to NB1 then take the OTA to lollipop that's the easiest way man
lordnihilusmd said:
I will try but i already did full unroot . When flashing via recovery it says something like frameworkres-apk has unexpected content ... Standard way ? but it will tell me software update interrupted
Click to expand...
Click to collapse
brownie9987 said:
Easiest way possible odin back to NB1 then take the OTA to lollipop that's the easiest way man
Click to expand...
Click to collapse
OTA from ODIN stock has never worked for me. Maybe it's because it's SIM-less?
What do you mean by Simless?