I was at work so I never got a chance to capture the D/L. It was small, around 4MB. Anyone else see it?
Probably the Nov security update posted here
McChen147 said:
november security update:
https://android.googleapis.com/pack...5f522d.signed-volantis-MRA58N-from-MRA58K.zip
Click to expand...
Click to collapse
Can install with root?
TWRP Failed to install
edgardo_0691 said:
Can install with root?
TWRP Failed to install
Click to expand...
Click to collapse
When I flashed Marshmallow, I went back to unrooted. So the OTA worked fine, but not sure if you can stall with Root.
No.
edgardo_0691 said:
Can install with root?
TWRP Failed to install
Click to expand...
Click to collapse
OTA Update
I am also unable to install the update however I am on Marshmallow 6 and every time I boot up my device it tells me that the device is untrusted.
is this part of a larger issue?
ImzTinoz said:
I am also unable to install the update however I am on Marshmallow 6 and every time I boot up my device it tells me that the device is untrusted.
is this part of a larger issue?
Click to expand...
Click to collapse
This is normal. The warning is displayed because you have modified your device. It means nothing for the functionality of your tablet.
You cannot use the OTA update if your system is modified. You must be stock unrooted, unless you used the systemless root method in which case you need to restore stock recovery and kernel, then OTA will work.
This zip is not meant to be flashed in TWRP, it's the official OTA update which needs the stock recovery and completely unmodified /system partition.
Related
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
jeraldjunkmail said:
As per the title, I read something somewhere to the effect that from here on out, OTA updates will fail on most phones if they have been rooted, and this seems to be true for the Z Ultra GPE. So, what changed when I rooted my phone, and how do I undo it so that I can do the OTA update? I have looked through the forum, but nobody seems to answer it. I am rooted with Supersu using the Towelroot method. I am hoping to not have to unlock the bootloader or anything, just want to do this the official way. (I did backup my TA partition though).
Click to expand...
Click to collapse
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Visa Declined said:
If your GPe is rooted only, the OTA should install just fine. If you made any system changes, you'll need to revert those though. I ran the OTA while I was rooted and didn't have any problems.
Click to expand...
Click to collapse
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
well at the moment that doesn't effect the GPe, and may never. There will have to be a system image flashed to put the block device in a known state before the new way could ever be used, and if there is a system.img we can always flash that to get the OTA to work... no big deal I don't think.
jeraldjunkmail said:
Not so. See:
http://bgr.com/2014/11/14/android-5-0-lollipop-updates-and-root/
As mine is rooted, no dice, the OTA fails. So, how to unroot it so that the update takes?
Click to expand...
Click to collapse
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
What is Xposed? How would I check to see if it has affected my device? Only thing I did was Towelroot and running SuperSU. I may have done something to allow writing to the external SD card, but forget how I did that. I was intentionally trying to keep this phone basically stock so that it would easily update to Lolipop. I did a Titanium backup to the externalSD card and reset it to factory and the OTA update still fails though. I assume this was due to the fact that I rooted it. The bootloader is still unmodified, secureboot is still green - yes, lock state is locked. Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
jeraldjunkmail said:
I may have done something to allow writing to the external SD card, but forget how I did that.
Click to expand...
Click to collapse
jeraldjunkmail said:
Only other thing I can think of is I installed an app that allowed me to set permissions by app (turn off location settings by app, etc) Sorry I can't give any more details than that...
Click to expand...
Click to collapse
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Visa Declined said:
If you can't figure out what system change you made to your phone, just factory reset it, and run the OTA again. There was multiple people(me included) that took the OTA successfully, our phones were rooted and SuperSU was installed.
Click to expand...
Click to collapse
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
jeraldjunkmail said:
As mentioned before, I factory reset this and wiped the cache from the stock recovery mode. Update won't take, stops shortly after it fails with "system update error". Since my last reset (been done a few times) it won't prompt me to get the OTA update, after my last reset last night. Any help is appreciated. Thanks!
{Damn thing won't work... (*&^&%^$$#}
Click to expand...
Click to collapse
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
blueether said:
The only fail-safe way I can see is to:
root
back up TA
unlock BL
hotboot custom kernel with recovery
flash 4.4.2
OTA to 4.4.3
OTA to 4.4.4
root and restore TA if you want a working camera
OTA to 5.0
Click to expand...
Click to collapse
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
jeraldjunkmail said:
As often happens, I sometimes see a solution I don't care to implement and begin to procrastinate. So, haven't looked at this problem for a while. I may have found the solution to my problems, but want to know if anyone has experience with it before proceeding. I re-installed superSU and went through the options. Buried in the options list is a box that offers "Full unroot, Cleanup for permanent unroot". What happens when I do this? does it just remove superSU or does it restore the phone back to factory status, before it was rooted? Thanks!
PS: @ blueether the solution is fine and I am sure it would work (I was going to go ahead with it until I saw that option in superSU), but have been hesitant to unlock the bootloader, etc, due to my unfamiliarity with hacking Sony products, and only want to do it as a last, final, no other option solution. Thanks for your help!
Click to expand...
Click to collapse
That's fine and I take no offence at you not wanting to unlock the BL.
I haven't tried the full unroot option in supersu so I'm not sure what the outcome is. One of the other GPe users care to comment?
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
jeraldjunkmail said:
Well, turns out that the solution to unrooting the phone is to install superSU and than look inthe settings. It will offer you an option to completely uninstall root. It did what it says, and than you can check it with a check root app from the market. It reports that the phone is not rooted. Now the question is, will it pick up the OTA update... No luck with that after a clean factory reset, so not sure what to do next.
2 questions: If I unrooted my phone, and it says it is unrooted, is this true, in the fullest extent? Does towelroot do anything more than adding some permissions ans the superuser file?
If the phone won't pick up the OTA update, why? What went wrong?
Thanks!
Click to expand...
Click to collapse
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
blueether said:
It sounds like the OTA is not being pushed at the moment/anymore. You could copy it to there the recovery can see it and manually install it
Click to expand...
Click to collapse
Can you point me inthe right direction for instructions on this process? Thanks!
Visa Declined said:
First of all, BGR is a garbage site, and I wouldn't believe anything they say, ever. Second, that article is talking about avoiding root AFTER Lollipop is installed.
Having root will not cause the OTA to fail. If your OTA is failing, it's because you made a system change on your device.
*edit
If you were using Xposed, then that is more than likely why your OTA is failing.
Click to expand...
Click to collapse
Your post is two years ago but i think you can help me,there is a new update for my phone and i am rooted i also have xposed installed so this mean i cannot update my sytem? Do i need to uninstall xposed? Im on stock rom and with TWRP recovery it would be a big help if you reply thanks.
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.
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
I have an unlocked 5X with TWRP installed (but have not yet modified system.)
I'm about to flash SuperSu but have 2 questions.
1) Will I lose functions such as the fingerprint reader if the device is rooted?
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
harryspar said:
I have an unlocked 5X with TWRP installed (but have not yet modified system.)
I'm about to flash SuperSu but have 2 questions.
1) Will I lose functions such as the fingerprint reader if the device is rooted?
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
Click to expand...
Click to collapse
1) Will I lose functions such as the fingerprint reader if the device is rooted?
if you install the stock rom you will keep this functionality otherwise you need to wait concerning CM13 build
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
there is always a risk but minor
harryspar said:
2) Is there a risk of getting in a bootloop if a firmware update is downloaded?
Click to expand...
Click to collapse
You will not be able to flash ota with a custom recovery. When a new update arrives you will have to wait for a twrp compatible zip or return to complete stock to flash the update
wickedesires said:
You will not be able to flash ota with a custom recovery. When a new update arrives you will have to wait for a twrp compatible zip or return to complete stock to flash the update
Click to expand...
Click to collapse
Right, I remember this happening with other devices, as the OTA uses a recovery script.
I wonder if there will be nag screens for OTA's. This rendered my wife's S4 so annoying to use, with a persistent notification, until I found a block method (disallowing notifications didn't work since I'd have had to disable notifications for the entire Android System UI...)
harryspar said:
I wonder if there will be nag screens for OTA's.
Click to expand...
Click to collapse
I went about 5 days before I installed the b140 update and I don't recall any annoying notifications. I know exactly what you mean though my s5 active did the same thing because I didn't want to update and lose root. I finally found a way to disable it but like you said it was very irritating.
Surprised I haven't seen any posts. 10.0.40 landed on my phone on Oct 28th. Only change is the October security update.
Hello
After rooting my Mclaren, I can't do any more system updates. Does anyone know how I can do it?
Best Regards
FilFire said:
Hello
After rooting my Mclaren, I can't do any more system updates. Does anyone know how I can do it?
Best Regards
Click to expand...
Click to collapse
You need to restore the boot image back to stock. In Magisk Manager, select uninstall and select restore images. Then reboot and try again. Howerver, depending on what method you used to root, it may not be able to restore the factory boot image. In which case you'll need to find it online.
Seems very skippable lol. Certainly not worth the effort of unrooting and rerooting.
Mine was rooted and had .35 on it. This popped up on mine too and I was able to do OTA upgrade. Not full and lose my data. Happy here
The only change was October security update
Do you have to run the OTA fixer every time there's a new OTA?
RypeDub said:
Do you have to run the OTA fixer every time there's a new OTA?
Click to expand...
Click to collapse
nope. just once after bootloader unlock
adit07 said:
nope. just once after bootloader unlock
Click to expand...
Click to collapse
Ok, so I have the update waiting to be installed, and I've ran the fixer in the past after a bootloader unlock:
What is the process to update now? Lol do I need to do anything with Magisk?
I think my phone failed to install it, or I just never tried yet cause I'm stupid and still trying to learn all this properly.