My S4 is failing to install the 4.3 OTA update. It is stock and was rooted with the de la Vega procedure. The only change I did was to install the AOSP browser and disable some bloat. I would appreciate any advice on how to get the 4.3 OTA update to work.
jhom52 said:
My S4 is failing to install the 4.3 OTA update. It is stock and was rooted with the de la Vega procedure. The only change I did was to install the AOSP browser and disable some bloat. I would appreciate any advice on how to get the 4.3 OTA update to work.
Click to expand...
Click to collapse
It won't update because you're rooted. I had the same problem. I Odined back to stock and everything was fine after that. Lost root obviously, but not a big deal to me.
It also needs all that bloat you removed back.
Thanks for the advice. I was hoping that I didn't have to unroot. But, I will Odin back.
jhom52 said:
My S4 is failing to install the 4.3 OTA update. It is stock and was rooted with the de la Vega procedure. The only change I did was to install the AOSP browser and disable some bloat. I would appreciate any advice on how to get the 4.3 OTA update to work.
Click to expand...
Click to collapse
I just found out why mine won't update - the Xposed Installer updates /system/bin/app_process to install its hooks, and the installer sees that file as modified and fails. If you've got Xposed installed, start the installer and select the "Uninstall (restore app_process)" option. Then the OTA should apply without error - of course, you've got to have all of the bloat restored first.
I wrote a shell script that checks for the necessary files. Push the attached to your sdcard, open a terminal window and do the following:
$ su
# sh /sdcard/otachecker.txt
Click to expand...
Click to collapse
or /mnt/extSdCard/otachecker.txt if you put it on the external SD card.
The script will tell you what files are missing and what files are tampered with. If all is good to go, you won't see any output.
Success. Odin back to MI1 and then installed 4.3 OTA. Now waiting for a root exploit for 4.3.
jhom52 said:
Success. Odin back to MI1 and then installed 4.3 OTA. Now waiting for a root exploit for 4.3.
Click to expand...
Click to collapse
did you use the Vega MI1 odin?
guharajdeep said:
did you use the Vega MI1 odin?
Click to expand...
Click to collapse
No, I used the no wipe method in the xda s4 android development section, http://forum.xda-developers.com/showthread.php?t=2301259
Related
Title says it all. I understand it screws up the search function (but can be fixed with an APK reload, but will the OTA cause any other issues?
huh I didn't get a software update.. and I just checked.... none for me on AT&T
If you are rooted with a stock rom, you can not install the update because you are rooted. There are 2 ways to install the update 1) unroot your phone, accept the update, and reroot your phone or 2) flash a custom factory rom with the update already installed.
And yes the update does disable the universal search on your phone and not sure if there are any other issues.
palillo2006 said:
If you are rooted with a stock rom, you can not install the update because you are rooted. There are 2 ways to install the update 1) unroot your phone, accept the update, and reroot your phone or 2) flash a custom factory rom with the update already installed.
And yes the update does disable the universal search on your phone and not sure if there are any other issues.
Click to expand...
Click to collapse
Or open up superuser/info and check boxes:
Temp unroot
Ota survival
droidstyle said:
Or open up superuser/info and check boxes:
Temp unroot
Ota survival
Click to expand...
Click to collapse
Future ROMs will have the update, right? So, if we wanted to, we could just wait?
I was on ME7. I was rooted, and safestrap. I was running hyperdrive. I've removed hyperdrive, removed safestrap, took the MI1 update and lost root.
Now I keep getting a notice for another update and it keeps failing the update when I try to install.
What can I do to fix this?
jim2029 said:
I was on ME7. I was rooted, and safestrap. I was running hyperdrive. I've removed hyperdrive, removed safestrap, took the MI1 update and lost root.
Now I keep getting a notice for another update and it keeps failing the update when I try to install.
What can I do to fix this?
Click to expand...
Click to collapse
You can either disable the OTA update notification and remain on MI1, or return your system to stock and take the update. Which would you like to do?
Freezing SDM will stop the update notifications.
Flashing a no-wipe ROM will get you to stock and allow the OTA to proceed, which will get you from MI1 to MJ7.
You can then easily re-root.
k1mu said:
You can either disable the OTA update notification and remain on MI1, or return your system to stock and take the update. Which would you like to do?
Freezing SDM will stop the update notifications.
Flashing a no-wipe ROM will get you to stock and allow the OTA to proceed, which will get you from MI1 to MJ7.
You can then easily re-root.
Click to expand...
Click to collapse
I'd like to return to stock, take the update and then re-root. What rom do I need to flash and do I flash with Odin? If so, what on odin do i click?
Thank you for your time and help.
jim2029 said:
I'd like to return to stock, take the update and then re-root. What rom do I need to flash and do I flash with Odin? If so, what on odin do i click?
Thank you for your time and help.
Click to expand...
Click to collapse
In the General forum, read this.
In the Q&A Forum (here), read this.
k1mu said:
In the General forum, read this.
In the Q&A Forum (here), read this.
Click to expand...
Click to collapse
Tired to flash it... Failed. Now phone boots to a screen with Firmware upgrade encountered an issue. Please use software repair assistant & try again.
Can't use phone and I need it for work tomorrow.... I'm screwed.
Please delete this thread...
Thank You.
OK, so i am rooted and have TWRP. The OTA update keeps failing to install and I cannot see the error because it goes away so fast. Is this because I have a custom recovery?
thanks,
aaronc_98 said:
OK, so i am rooted and have TWRP. The OTA update keeps failing to install and I cannot see the error because it goes away so fast. Is this because I have a custom recovery?
thanks,
Click to expand...
Click to collapse
Hi, aaronc_98...
Short answer is 'yes'.
You need to be running 100% unmodified official factory stock for a Google OTA to work.
Any deviation from factory stock, such as a custom recovery, as well as the root su binary and the SuperSU app will likely cause the OTA to abort, and with no changes made.
Rgrds,
Ged.
I have a VZ LG G3 that I rooted using StumpRoot. I am trying to do the Verizon system update to Lollipop. It downloads it and then it reboots, but almost immediately it shows me error 0x1117008, and then just reboots again and tells me the update failed. It doesnt give me any other info. Currently my phone shows Android version 4.4.2 and software version VS98511C and shows the Software status as Modified. Is there a way to get Lollipop? Would I have to unroot first? (If so, what is the best way? SuperSU offers me that option). I appreciate any help. Thanks.
mugsisme said:
I have a VZ LG G3 that I rooted using StumpRoot. I am trying to do the Verizon system update to Lollipop. It downloads it and then it reboots, but almost immediately it shows me error 0x1117008, and then just reboots again and tells me the update failed. It doesnt give me any other info. Currently my phone shows Android version 4.4.2 and software version VS98511C and shows the Software status as Modified. Is there a way to get Lollipop? Would I have to unroot first? (If so, what is the best way? SuperSU offers me that option). I appreciate any help. Thanks.
Click to expand...
Click to collapse
You will have to flash back to either stock 12b via KDZ or go back to 10b and upgrade that way. Once rooted, you cannot update to LP via the OTA. Unrooting won't fix it either as it has already been modified.
If you flash back to 12b via KDZ, it will still show your software as modified, but the OTA will take.
Then you can use the one-click root method (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951) to root LP.
iBolski said:
You will have to flash back to either stock 12b via KDZ or go back to 10b and upgrade that way. Once rooted, you cannot update to LP via the OTA. Unrooting won't fix it either as it has already been modified.
If you flash back to 12b via KDZ, it will still show your software as modified, but the OTA will take.
Then you can use the one-click root method (http://forum.xda-developers.com/lg-g3/general/guide-root-lg-firmwares-kitkat-lollipop-t3056951) to root LP.
Click to expand...
Click to collapse
Thank you for the reply. How do I go back to 10b? Also, if I want to use the KDZ method, can it be done with a Linux machine?
Thanks.
mugsisme said:
Thank you for the reply. How do I go back to 10b? Also, if I want to use the KDZ method, can it be done with a Linux machine?
Thanks.
Click to expand...
Click to collapse
Not sure about Linux. I believe it all has to be done via Windows if using the KDZ or TOT methods.
Here is the link to flash back via KDZ:
http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
mugsisme said:
I have a VZ LG G3 that I rooted using StumpRoot. I am trying to do the Verizon system update to Lollipop. It downloads it and then it reboots, but almost immediately it shows me error 0x1117008, and then just reboots again and tells me the update failed. It doesnt give me any other info. Currently my phone shows Android version 4.4.2 and software version VS98511C and shows the Software status as Modified. Is there a way to get Lollipop? Would I have to unroot first? (If so, what is the best way? SuperSU offers me that option). I appreciate any help. Thanks.
Click to expand...
Click to collapse
Same but im already on 10b and never updated after root. Im confused and need help!
csongcuan said:
Same but im already on 10b and never updated after root. Im confused and need help!
Click to expand...
Click to collapse
10b is great, and everything just works. I am not sure why any one wants to "upgrade" to 23c given Google has not fixed the memory leak issues, but if you want to, read on.
If you have rooted, you do not want to upgrade by OTA. OTA is patches to the unmodified stock firmware. It will fail if your phone is in anyway modified. Here is what you can do:
1. Install TWRP manager from Google Play.
2. From TWRP manager you can choose your phone model and download and install TWRP recovery.
3. Follow the instruction from this link to use TWRP to install the 23c
http://forum.xda-developers.com/verizon-lg-g3/development/rom-rom-base-lp-upgrade-bump-t3051884
Jasmine ROM is basically stock with root, which is probably what you want.
acefr said:
10b is great, and everything just works. I am not sure why any one wants to "upgrade" to 23c given Google has not fixed the memory leak issues, but if you want to, read on.
If you have rooted, you do not want to upgrade by OTA. OTA is patches to the unmodified stock firmware. It will fail if your phone is in anyway modified. Here is what you can do:
1. Install TWRP manager from Google Play.
2. From TWRP manager you can choose your phone model and download and install TWRP recovery.
3. Follow the instruction from this link to use TWRP to install the 23c
http://forum.xda-developers.com/verizon-lg-g3/development/rom-rom-base-lp-upgrade-bump-t3051884
Jasmine ROM is basically stock with root, which is probably what you want.
Click to expand...
Click to collapse
So Jasmine ROM also has the notification issues over Wifi or is that fixed with a mod of some sort?
Anthony-m said:
So Jasmine ROM also has the notification issues over Wifi or is that fixed with a mod of some sort?
Click to expand...
Click to collapse
There is an IPv6 fix that you can flash to solve it.
I upgraded using the Verizon tool on the computer. I was rooted.
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
If you have this exact problem, unbrick instructions here:
Try using Phone Flash Tool from the Dell site, and this zip:
https://mega.co.nz/#!Vgw1CTYT!y1_tSTCMmzrhJSQy0lxwY59iyRhdJovC-IDMF25PB4k
It's the new boot firmware binaries packed in the developer edition firmware zip with the xml changed to point to the new files.
For the flashing process of this zip, start with the tablet completely off and disconnected, then in Phone Flash Tool, load the zip file, click "Start to flash" (the button near the bottom should be blue/clickable), then once it's counting attempts (attempt #0, attempt #1, etc.) then connect USB. It should proceed to flash.
Click to expand...
Click to collapse
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
xBIGREDDx said:
I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
What is the process to unroot on our device?
Install es file explorer or root explorer.
Grant root access to the app.
in es you need to enable root explorer in the settings menu.
Go to
Code:
/system/bin
delete su (mine was not locate in here)
/system/xbin
delete su (mine was here)
/system/app/Superuser.apk delete this
SuperSu has a selection of uninstall options in the app's menus.
vampirefo said:
Well, yeah anytime a update via OTA is available unroot and revert the device to stock, the update is designed to go over a stock tablet.
Click to expand...
Click to collapse
I've applied plenty of OTAs in the past to other devices on top of rooted systems, and never had a problem as bad as bootlooping.
(Not saying it's not my fault, as I knew there was a risk, I guess I was just running on a series of good luck, or maybe other companies write better OTA pre-checking features.)
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
kage69 said:
good you mentioned this
supersu - complete unroot - update worked
i forgot to uninstall xposed - modifications where gone after reboot (batterie percentage etc. from gravitybox)
has anyone tried rooting after update? could the kitkat method work?
Click to expand...
Click to collapse
It's hard to say, as lollipop was just released, only you guys with lollipop can test and see.
Neither SDC nor myself have lollipop so we can't test.
sent from my kingSing T1 via taptalk
On mine, I forgot to un-root with no issues, but it defaults to encrypting the tablet and now I can't re-root.
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
old root method dont work :crying:
kage69 said:
old root method dont work :crying:
Click to expand...
Click to collapse
Well you tried, did you get an error? Can you give more details?
sent from my kingSing T1 via taptalk
xBIGREDDx said:
EDIT: Turns out the root was not the problem. It was the developer edition firmware. I flashed the new firmware from the OTA update separately and now I'm booting fine.
ORIGINAL POST:I just received the Lollipop OTA, and I installed it. I did not remove my Superuser installation or my Busybox installation first. Now I am bootlooping.
So, take this as a warning, do not install the OTA if you have modified your system.
Now I am going to try to find a way to fix this...
Click to expand...
Click to collapse
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
ely105 said:
Will the same rooting procedure work fine after you have upgraded to Lollipop on the 7840? Wanted to try but not sure if everything will work. Also since i'm on a Mac the .bat file doesn't run out of the box...
Click to expand...
Click to collapse
@kage69 says no, only you guys with lollipop can confirm or deny if root works or not.
sent from my kingSing T1 via taptalk
the tool flashes temp cwm but the tab dont boot to recovery
stays in bootloader where you can choose boot normal, power down and recovery
choosing recovery boots to stock recovery
there were errors while flashing, ill post them tomorrow
reading a book in bed on my lollipopped tab now
hope we can root it again, need that for customizations and airaudio
see u tomorrow
So how were you able to flash after bootlooping the first time when you tried to update with root? I cannot get into the bootloader or anything :silly:
Does any one have the ota so I can patch the stock firmware to investigate rooting it?
might be stored in cache i think
cant get to that without root
kage69 said:
might be stored in cache i think
cant get to that without root
Click to expand...
Click to collapse
Yeah I we hoping someone captured it before updating
xBIGREDDx said:
Hmm, I also had the developer firmware installed from their opensource site; maybe that's it? The only other thing would have been Busybox, I think...
EDIT: HEY IT WORKS! I just pulled the firmware binaries out of the update.zip, and flashed with xfstk-downloader, and now I'm on the Encrypting screen! Thanks!
Click to expand...
Click to collapse
Exactly which binaries did you flash back? In the zip I see:
dnx_fwr_ann_a0-mofd_v1.bin
dnx_fwr_ann_a0-mofd_v1-DBG.bin
dnx_fwr_blackburn_preqs_preqs.bin
dnx_fwr_blackburn_qs_qs.bin
dnx_fwr_preqs.bin
dnx_fwr_qs.bin
ifwi_ann_a0-mofd_v1.bin
ifwi_ann_a0-mofd_v1-DBG.bin
ifwi_preqs.bin
ifwi_qs.bin