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
Related
https://doc-0k-1o-docs.googleuserco...009/*/0BzrP5DWIlpplYjFOY1MwOXFNLWc?e=download
here is the ota zip
if we flash this can we flash 4.5.141 with rsd?
any answers?
I wouldn't count on it. The ZIP seems to contain what looks like the bootloader, or at least a piece of it (ap20bl.img). Who knows what might happen after that. Motorola said a downgrade is not possible.
I would just wait for the .145 fruitcake. Then switching back and forth should be safe and painless.
ok thanks for answer
Installed 4.5.145 for fun
blttalas said:
ok thanks for answer
Click to expand...
Click to collapse
I wanted to see for myself the GPS improvements made in the update and sacrificed losing SU/root access to the phone. The update installed without a hitch and left all my apk installed apps alone. I had a handful of apps that required root (e.g. Dropbear II, busybox, Superuser, root explorer, and seeder) and will just wait until someone figures out a new method to regain access again.
sn0wba11 said:
I wanted to see for myself the GPS improvements made in the update and sacrificed losing SU/root access to the phone. The update installed without a hitch and left all my apk installed apps alone. I had a handful of apps that required root (e.g. Dropbear II, busybox, Superuser, root explorer, and seeder) and will just wait until someone figures out a new method to regain access again.
Click to expand...
Click to collapse
Did you do this via the standard update or by flashing that zip yourself?
vikingarcher said:
Did you do this via the standard update or by flashing that zip yourself?
Click to expand...
Click to collapse
Standard
Su ota survival
Has anyone tried to install the update after activating the superuser ota survival option
Root after sys 4.5.145 update?
fdaconta said:
The traditional preinstall method should still work. No wiping happens with that. I used it back when I first rooted my phone, everything stayed exactly as it was (all stock) except I had root too.
Click to expand...
Click to collapse
This response is from the developer thread. I would respond there but the policy for members with less than 10 posts is silly.
None of the existing preinstall methods (e.g. atrix-4g-moto-fastboot or superoneclick 2.3.3) work with 4.5.145.
sn0wba11 said:
Standard
Click to expand...
Click to collapse
Interesting. I tried it with my stock ROM that is rooted and unlocked -- ended up with a boot loop. Decided to flash a new ROM, so switched to the CM10 ROM. That seems to be working well and I think I will just not worry about this update for now.
vikingarcher said:
Interesting. I tried it with my stock ROM that is rooted and unlocked -- ended up with a boot loop. Decided to flash a new ROM, so switched to the CM10 ROM. That seems to be working well and I think I will just not worry about this update for now.
Click to expand...
Click to collapse
Came across a link at Android Central that used Voodoo OTA RootKeeper to restore --> Forgot I installed this awhile back; reinstalling app restored my superuser access
Re-rooted 4.5.145 after OTA
I successfully re-rooted mine last night using the pre-install method.
Read my topic here:
http://forum.xda-developers.com/showthread.php?t=2153422
From 141, to 145, back to 141.... and finally ended up with a working (and rooted) 145.
just wanted to share the original recovery image that came with the phone for anyone that is trying to get the update but dont want to have to restore their phone with kdz/tot file. just push this image to your device via adb. if you have supersu as your root, in the options of supersu you can do a clean uninstall and completely get rid of root with it. then take the OTA update so you dont have any problems with the update. or if you want to keep root you dont have to uninstall it. it seems after the 4.4.2 update, root is still there. enjoy.
d800 stock recovery
freebee269 said:
just wanted to share the original recovery image that came with the phone for anyone that is trying to get the update but dont want to have to restore their phone with kdz/tot file. just push this image to your device via adb. if you have supersu as your root, in the options of supersu you can do a clean uninstall and completely get rid of root with it. then take the OTA update so you dont have any problems with the update. or if you want to keep root you dont have to uninstall it. it seems after the 4.4.2 update, root is still there. enjoy.
d800 stock recovery
Click to expand...
Click to collapse
I'm assuming we would push this using ADB? Is there a quick guide for that? I haven't manually installed a recovery in forever.
Are you sure your root was still working after the update? On every other device I have updated to Kitkat, the Superuser app was still there, but you couldn't update the binaries. Something changed with 4.4 that makes the old root method not work. Apparently, Superuser has to be flashed every single time you update from 4.4 on. At lest, that's what I read when I was updating my Nexus and Moto X.
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
It is amazing with most of the searching I have done about this update, VS98026A, on how they say that this is the KitKat 4.4.4 update. When it isn't and we are still at 4.4.2.
hd-renegade said:
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
Click to expand...
Click to collapse
Rooted vs98024a and did OTA to vs98026a and still have Root. Pretty neat we didn't lose Root.
hd-renegade said:
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
Click to expand...
Click to collapse
I lost root. Not sure why though. And I cannot get root back as IOROOT seems to not work with 26A. It attempts to reboot to recovery and then the phone shows a little android robot on his back with belly open and a error indicator over him.
lukester01 said:
I lost root. Not sure why though. And I cannot get root back as IOROOT seems to not work with 26A. It attempts to reboot to recovery and then the phone shows a little android robot on his back with belly open and a error indicator over him.
Click to expand...
Click to collapse
You would have to downgrade to 24A, gain root using iOROOT and run OTA.
Note: To be on the safe side, I revert my phone back to vs98010b and took it from there one step at a time.
wait for new ioroot?
I think I lost root during my attempts to get the OTA to work. I was getting the 111104 error due to the Hotspotprovision.apk. And simply renaming the apk to .bak didn't work to allow the OTA. From the LG mobile windows application I did a upgrade recovery option (some had posted that this would fix the problem). That did not fix the problem though. I was only able to do the OTA after I MOVED the file Hotspotprovision.bak out of system/app. Seems the OTA was scanning for "hotspotprovision". I didn't realize I had lost root before I took the OTA to 26A.
So note to all. Do NOT simply change the name to be a .bak. And do not upgrade the recovery as this removes root. The OTA like everyone says now, does not care about root. The failure to install is simply because of the file name being in the system/app folder.
Not sure how to go back to 24A. Probably not possible without flashing a STOCK ROM I'm guessing. I guess I'm stuck waiting for someone to root 26A.
Interestingly though, with 26A unrooted I seem to be able to use the Mobile hotspot without the modified provisioning file. Previously I had to have the modified version to use the hotspot feature as it is not part of my plan.
RobertVanHagar said:
You would have to downgrade to 24A, gain root using iOROOT and run OTA.
Note: To be on the safe side, I revert my phone back to vs98010b and took it from there one step at a time.
Click to expand...
Click to collapse
lukester01 said:
I think I lost root during my attempts to get the OTA to work. I was getting the 111104 error due to the Hotspotprovision.apk. And simply renaming the apk to .bak didn't work to allow the OTA. From the LG mobile windows application I did a upgrade recovery option (some had posted that this would fix the problem). That did not fix the problem though. I was only able to do the OTA after I MOVED the file Hotspotprovision.bak out of system/app. Seems the OTA was scanning for "hotspotprovision". I didn't realize I had lost root before I took the OTA to 26A.
So note to all. Do NOT simply change the name to be a .bak. And do not upgrade the recovery as this removes root. The OTA like everyone says now, does not care about root. The failure to install is simply because of the file name being in the system/app folder.
Not sure how to go back to 24A. Probably not possible without flashing a STOCK ROM I'm guessing. I guess I'm stuck waiting for someone to root 26A.
Interestingly though, with 26A unrooted I seem to be able to use the Mobile hotspot without the modified provisioning file. Previously I had to have the modified version to use the hotspot feature as it is not part of my plan.
Click to expand...
Click to collapse
Stump Root worked for me on 26A. Had to do the brute force thing and it took about 5 minutes, but it worked.
Stump root worked on LG G2 26A
Stump root worked. It auto used the brute forth method like you said. Thanks.
Finally I can program my bluetooth call button back to use google now voice search instead of LG voice command.
snellc001 said:
Stump Root worked for me on 26A. Had to do the brute force thing and it took about 5 minutes, but it worked.
Click to expand...
Click to collapse
I used stump root successfully on my 26A as well.
I have a question about the OTA Update 26A. When I got the phone, it was not rooted. It was and is now on VS98024A. I rooted with the ioroot method, but had to use the manual method because the script did not work. It is rooted and i used the hack for the mobile hotspot, so that works. I never installed a custom recovery yet. My question is should I install this update 26A since I don't have a custom recovery, or does that have nothing to do with it?
pricer22 said:
I have a question about the OTA Update 26A. When I got the phone, it was not rooted. It was and is now on VS98024A. I rooted with the ioroot method, but had to use the manual method because the script did not work. It is rooted and i used the hack for the mobile hotspot, so that works. I never installed a custom recovery yet. My question is should I install this update 26A since I don't have a custom recovery, or does that have nothing to do with it?
Click to expand...
Click to collapse
Simply remove the modified mobile hotspot from system/app. That should allow you to take the OTA
Sent From The Trail Of Untold Truths
you will not be able to take any OTA if you add a custom recovery
pricer22 said:
I have a question about the OTA Update 26A. When I got the phone, it was not rooted. It was and is now on VS98024A. I rooted with the ioroot method, but had to use the manual method because the script did not work. It is rooted and i used the hack for the mobile hotspot, so that works. I never installed a custom recovery yet. My question is should I install this update 26A since I don't have a custom recovery, or does that have nothing to do with it?
Click to expand...
Click to collapse
If you add a custom recovery you will not be able to take any OTA updates.
lukester01 said:
If you add a custom recovery you will not be able to take any OTA updates.
Click to expand...
Click to collapse
Am I understanding the purpose of a custom recovery like TWRP is so you can flash roms or if you want to block OTA updates? At this point I am just interested in the stock rom, rooted, so I don't need a custom recovery right?
pricer22 said:
Am I understanding the purpose of a custom recovery like TWRP is so you can flash roms or if you want to block OTA updates? At this point I am just interested in the stock rom, rooted, so I don't need a custom recovery right?
Click to expand...
Click to collapse
Correct, you don't need one. Note however you won't be able to do image (nandroid) backups/restores or flash images. So be very careful with your root privileges ?
Sent from my VS980 4G
custom recovery
pricer22 said:
Am I understanding the purpose of a custom recovery like TWRP is so you can flash roms or if you want to block OTA updates? At this point I am just interested in the stock rom, rooted, so I don't need a custom recovery right?
Click to expand...
Click to collapse
Custom recovery allows you to flash roms, make nandroid backups, and do several other things. But it will make the phone so that you cannot get OTA updates. To apply updates when you have a custom recovery you will have to wait for someone to make the OTA update into a file you can flash.
TWRP
I read yesterday that i wouldn't loose root if i took the 26A Update. I am running the stock ROM but have TWRP installed. I changed the settings for the hot spot and took the update. It rebooted and I am in TWRP. I cant figure out what to do to get it to boot up the Stock Rom. Please help.
I found it. If you get stuck in TWRP
I used TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then Rebooted. No Changes made Still on 24A.
MFR73 said:
I read yesterday that i wouldn't loose root if i took the 26A Update. I am running the stock ROM but have TWRP installed. I changed the settings for the hot spot and took the update. It rebooted and I am in TWRP. I cant figure out what to do to get it to boot up the Stock Rom. Please help.
I found it. If you get stuck in TWRP
I used TWRP's awesome "terminal command" option to run the following:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then Rebooted. No Changes made Still on 24A.
Click to expand...
Click to collapse
I'm not familiar with TWRP commands, but sounds to me like the update tried to install by booting to recovery, but since it was not the stock recovery it could not update. Having a custom recovery in my experience has always made it so you can not take OTA updates. You would use the LG Mobile Support Tool to "upgrade recovery", that will basically restore the stock recovery. You will lose root. But you can update to 26A, and then use Stump root to get root again.
hd-renegade said:
Verizon pushed out yet another update this morning VS98026A. I renamed my hotspot files, put the old ones back in, powered my phone completely off for a minute. Turned the phone back on, took the OTA. Renamed the stock hotspot files to old, and placed the hacked hotspot files back. Rebooted the phone. I did not loose Root Access, and my hotspot still works.
Not really sure why Verizon push 2 updates in a week. NOTE: This is not KitKat 4.4.4
Click to expand...
Click to collapse
I have read and found out with this new update u can noot root. Your phone i have tried ioroot25 and other methods and have failed
vs98026a is not supported for ioroot. Is my message i recive
I have a little green man with his chest open with a red traingle with a !
had that happen
nicknjg88 said:
I have read and found out with this new update u can noot root. Your phone i have tried ioroot25 and other methods and have failed
vs98026a is not supported for ioroot. Is my message i recive
I have a little green man with his chest open with a red traingle with a !
Click to expand...
Click to collapse
Look back a page. I had the same problem. You need to use the LG Mobile Support Tool and upgrade your recovery. Then take the over the air update. Then root again using Stump root.
I got the 0x1111004 error, and then the 0x1117008 error when trying to take the 25B and 26A update. I tried removing all of my framework and changes, but it didn't seem to help. Resorted to full KDZ wipe to 24A, then ioroot before taking the 26A update. It updated just fine and now I'm running the latest. Now to remove all the bloatware and restore my backups...
I'm hoping they don't push out any more OTA anytime soon unless it's L.
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.
I was able to accomplish a Full Root on the latest OTA update on the phone.
Previously I was running Stock 4.4.4 KitKat with SuperSu and had issues with the OTA, since I had removed Apps.
I installed the Stock 4.4.4 ftf to the phone using the flashtool.
Then was successful in receiving the Prompt to update.
After Update, I installed. "Kingroot" for android. just google it. NOT KINGOROOT or any other.
After running kingroot, King User was installed.
In my experience, no other root method will achieve full root. I was not happy with using Kinguser, since i was a Supersu fan. But anytime I successfully removed kinguser, to swap for Supersu, I had lost partial root access, and could not uninstall apps. I could only Freeze.
I also tried Superuser, but only kinguser allowed me to fully uninstall bloatware, and other apps from the phone.
Just thought I would share.
Thanks, Iambedook. Every experience helps. Kingoroot got me into trouble once before in the past.
Can you flash back to 4.4 from 5.1.1?
iambedook said:
I was able to accomplish a Full Root on the latest OTA update on the phone.
Previously I was running Stock 4.4.4 KitKat with SuperSu and had issues with the OTA, since I had removed Apps.
I installed the Stock 4.4.4 ftf to the phone using the flashtool.
Then was successful in receiving the Prompt to update.
After Update, I installed. "Kingroot" for android. just google it. NOT KINGOROOT or any other.
After running kingroot, King User was installed.
In my experience, no other root method will achieve full root. I was not happy with using Kinguser, since i was a Supersu fan. But anytime I successfully removed kinguser, to swap for Supersu, I had lost partial root access, and could not uninstall apps. I could only Freeze.
I also tried Superuser, but only kinguser allowed me to fully uninstall bloatware, and other apps from the phone.
Just thought I would share.
Click to expand...
Click to collapse
I'd love to try this, but I'm kinda unwilling/aprehensious to take the chance with rooting apps. Can you confirm that you can use flashtool to revert back to 4.4? I just know Verizon would block such a thing in an update, they can be jerks. (like the moto razr maxx hd) Any insight is appreciated.
Astoras said:
I'd love to try this, but I'm kinda unwilling/aprehensious to take the chance with rooting apps. Can you confirm that you can use flashtool to revert back to 4.4? I just know Verizon would block such a thing in an update, they can be jerks. (like the moto razr maxx hd) Any insight is appreciated.
Click to expand...
Click to collapse
Yes, you can revert back to 4.4.4 through Flashtool. Doing so though, you will not have Advanced Calling or the refreshing Lollipop UI. Also, unless you do something about it, you will be promptly reminded all the time to update to 5.1.1.
GigaSPX said:
Yes, you can revert back to 4.4.4 through Flashtool. Doing so though, you will not have Advanced Calling or the refreshing Lollipop UI. Also, unless you do something about it, you will be promptly reminded all the time to update to 5.1.1.
Click to expand...
Click to collapse
Giga,
If I use this method to root 5.1.1., can I install dual recovery and Camera 2 and the FM tuner app? I'd also like the updated flashlight you put together but don't see that as a separate install. Should I wait or go ahead with this method for root?
Thanks, Pat
pvcdroid said:
Giga,
If I use this method to root 5.1.1., can I install dual recovery and Camera 2 and the FM tuner app? I'd also like the updated flashlight you put together but don't see that as a separate install. Should I wait or go ahead with this method for root?
Thanks, Pat
Click to expand...
Click to collapse
You may root, but I would advise against anything else. the Z5 Camera is most likely not compatible for our phones on 5.1.1, and neither is the FM Tuner. It's a whole lot I can't touch base on yet.
Astoras said:
I'd love to try this, but I'm kinda unwilling/aprehensious to take the chance with rooting apps. Can you confirm that you can use flashtool to revert back to 4.4? I just know Verizon would block such a thing in an update, they can be jerks. (like the moto razr maxx hd) Any insight is appreciated.
Click to expand...
Click to collapse
I was able to flash back to 4.4.4 after i messed things up, but after going back to 4.4.4 i am struggling to get back to 5.1.1. The updates are not appearing, stating I am at the latest version.
I would also like a confirm if this. Because I'm sitting around and waiting for a rooted 5.1.1 copy for the phone. Im on 5.0.2 right now and all is working good but still waiting. Thanks all.
I'm going to see if I can root after upgrading to 5.1.1, but I have the stock firmware just incase.
Just uploaded a rooted twrp backup with real superuser ++++much more
Tigerhoods said:
Just uploaded a rooted twrp backup with real superuser ++++much more
Click to expand...
Click to collapse
Wow!!! That sounds great, thanks Tiger
thals1992 said:
I'm going to see if I can root after upgrading to 5.1.1, but I have the stock firmware just incase.
Click to expand...
Click to collapse
Just an FYI, after I needed to revert to 4.4.4. I was struggling to receive updates to get back to 5.1.1. I had to use the Flashtool, 3-5 times to get the correct update prompts to appear. If anyone else had similar issues when reverting back, let me know, but re flashing repeatedly worked for me.
Tigerhoods said:
Just uploaded a rooted twrp backup with real superuser ++++much more
Click to expand...
Click to collapse
Wow,
Download url please
immtu said:
Wow,
Download url please
Click to expand...
Click to collapse
Just scroll down to the z3v dev section.
I was actually able to flash the stock ftf coming 5.0.2. I had to flash it with default options the first time with it failing. I then found that I have to basically flash noting to clear the error on the phone by checking everything in exclude and the other exclude box where it shows its not displaying any files in the middle of the window.
Once that went through, I was able to upgrade from stock to .44 and then the the two updates for 5.1.1. After all that I reset to factory again to test on rooting the phone. I was too, able to obtain root with King Root. I was able to install zxrecovery and xposed with no problems. I'm actually used to King Root as I had to use it on the Verizon branded 7" tablet that didn't have any other possible methods previously. I also found that Busybox was slightly out of date (difference of 2.0) and installed to /sbin which wasn't too big of an issue.
Beyond that my phone seems to get pretty warm and typically complains about not charging even on a 2 Amp charger.
Can you tell me how you avhieved root because i want it but i can't revert to kitkat for some reason (flashtool won't recognise the update file) and I'm on lollipop. I've tried kingroot(app version) and it didn't work,tried reverting didn't work and tried all the framaroot,towelroot and such apps but none worked. I want working root,xposed and twrp. I can't find any way to do it please help.
Zandermc3 said:
Can you tell me how you avhieved root because i want it but i can't revert to kitkat for some reason (flashtool won't recognise the update file) and I'm on lollipop. I've tried kingroot(app version) and it didn't work,tried reverting didn't work and tried all the framaroot,towelroot and such apps but none worked. I want working root,xposed and twrp. I can't find any way to do it please help.
Click to expand...
Click to collapse
Try King root again. I used their apk on the phone. It rebooted once at 30%, but when I got back in the app after the reboot, it successfully rooted the device.
thals1992 said:
Try King root again. I used their apk on the phone. It rebooted once at 30%, but when I got back in the app after the reboot, it successfully rooted the device.
Click to expand...
Click to collapse
Well when i tried i did it 3 times and it failed,never rebooted. I have z3 international or 6603 i think
Zandermc3 said:
Well when i tried i did it 3 times and it failed,never rebooted. I have z3 international or 6603 i think
Click to expand...
Click to collapse
Thats why then. This is only for the Z3v the Verizon variant.
Hi there,
New to the forum. After several hours of reading and searching, I became bewildered enough to decide to register and post .
This thread looked promising. I'm currently on rooted 4.4.4 with this phone. I also have a custom recovery installed. Im trying to get to 5.1.1. As of right now, I assume my only option is to wait for a 5.1.1 ftf so that I can update, because the OTA updates won't work (phone reboots into the custom recovery and the update is interrupted).
Is there an easier way to get the OTA? Or am I stuck waiting for an ftf?
To be clear, my goal is to be on 5.1.1 with root. But at this point I don't think I can get to 5.1.1 at all.