Related
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
blackjack95129 said:
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
Click to expand...
Click to collapse
Anytime you root the phone it changes the stock recovery so when the OTA tries to run it fails because the recovery needed to do it is the stock one. Just wait for someone to post a updated ota that works with twrp.
For the most part, updates will be baked into roms so you won't need to take the OTA
Sent from my Tricked out HTC One
jznomoney said:
Anytime you root the phone it changes the stock recovery so when the OTA tries to run it fails because the recovery needed to do it is the stock one. Just wait for someone to post a updated ota that works with twrp.
Click to expand...
Click to collapse
On top of stock recovery, you need to have all stock apps present on the phone. They can be frozen, but they must be there. The first thing any official OTA does it check the signatures of all .apks it expects to find on the device--if any are missing, the update will abort. I learned today that when you unlock your bootloader, several HTC-specific applications are automatically deleted from the phone and this will prevent the phone from accepting the OTA. You'll need to either A) replace those apks, or B) flash a stock NAND backup, flash stock recovery, do the update, then re-flash custom recovery and continue on from there.
blackjack95129 said:
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
Click to expand...
Click to collapse
I installed it and it worked great. I have a unlocked bootloader but I am not rooted.
AT&T update file name and location?
Same experience. If I knew the location and file downloaded through AT&T Software Update, perhaps I could install it through TWRP. Anyone know? Tried?
blackjack95129 said:
I have rooted HTC One, I noticed a new software update was released by AT&T, and I wondered if it I updated it, would my root be gone? I tried to update it and after downloading the update, my phone restarted and booted into TWRP recovery and I rebooted and there was no update installed. Are any rooted HTC One users experiencing the same problem? What should I do, should i just forget about the OTA updates?
Click to expand...
Click to collapse
StanAnderson said:
Same experience. If I knew the location and file downloaded through AT&T Software Update, perhaps I could install it through TWRP. Anyone know? Tried?
Click to expand...
Click to collapse
no it will not work
Please...a little advice
Many thanks for all your help.
One question:
I have an HTC One (ATT) - SW Ver 1.26.502.10, bootloader unlocked, rooted, bloatware erased.
If I flash CM 10.1 - does this include the latest OTA update.
Many thanks
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.
Guestn/a posts Thanks: 0
So.. The Android 5.1.1 version is here and I've unrooted my phone for the update, but it still shows "Could not verify." Are there any files that cause the verifying process to know that I had rooted my device? If yes, can I delete it or what? Or are there any other ways to update without flashing a ftf file? (1. Because that ftf file is very big and my Internet speed couldn't afford it. 2. Because I don't want to wipe my apps and data) Any help would be appreciated!
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
wicozani said:
@OP, If I understand right, it's the custom recovery you might have that prevents the OTA update from completing successfully. Which, in a way, is a good thing.
Step 1: reroot your phone while you still can.
Step 2: download any of a number of flashable, pre-rooted 5.1.1 ROMs with recovery (*.zip) floating around now and flash it with your current recovery, wiping only cache and Dalvik upon exit. This is what I've done to keep all my date and settings and still be rooted and have recovery on 5.1.1.
Click to expand...
Click to collapse
After I flash this, can my phone update OTA or the same problem will happen?
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Hmm okay thankyou
wicozani said:
As far as we know, custom recoveries will always prevent OTA updates to our Xperia devices. Why are OTA updates seemingly so important to you? With your custom recovery installed, you can always simply flash the new update when it becomes available; often before the OTA update is released.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Can you give me a link for the official ROM? Thanks!
Can I use the AOSPA ROM? Does it need to unlock my bootloader to flash it?
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
giancaleone said:
Some consideration about this thread.
1) Not never the OTA updade overwrite the ROOT, example I passed from .627 to .28 through OTA update without lose the root and recovery. This depend of kind of update.
2) I think that to install a pre-rooted rom is not a good thing, because the baseband is almost always different an this can create issue related the WI-fi and carrier signal (3G, 4G).
3) I always installed the root, recovery and mod as well. But now I have understand that is not really necessary to install this. At least the stock Z2 have a good/beautiful OS and good hardware and there is no need to change some colors or icons to improve it.
I'm boring to flash and restore my data every new firmware or new mod. (now a new firmware is already certified and will be ready soon).
Maybe I will think to change the room when my phone will be obsolete
Regards
Click to expand...
Click to collapse
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Wayhome said:
Totally understand, thankyou, so I just flash the original ROM from AOSPA and without root is enough right?
Click to expand...
Click to collapse
If you do not have an unlocked bootloader, you cannot flash anything but a pre-rooted stock 5.1.1 ROM with recovery. There are several types available in the General Z2 column.
Sent from my D6503 using Tapatalk
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Wayhome said:
I have a crazy thought flashed across my mind haha, that file that I downloaded via OTA SYSTEM UPDATE is still there, can I make it as a zip file and flash it?
Click to expand...
Click to collapse
Why would you do that? You wouldn't have root and you wouldn't have a recovery; you'd be stuck, unable to root and install a recovery. Do what I said and you'll be fine.
Sent from my D6503 using Tapatalk
Can you help me to find one? That doesn't need to unlock bootloader to flash.
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.
ATT sent B180 down...
And of course, overnight, my phone tried to update - and is now stuck in a boot loop with TWRP.
Yay.
Hope everyone else is having a better day.
Rename
"/system/priv-app/DMClient/DMClient.apk"
by appending ".xxx" to the end using TWRP file manager.
Clear /cache partition.
Reboot and see if it works .
Paisley Pirate said:
ATT sent B180 down...
And of course, overnight, my phone tried to update - and is now stuck in a boot loop with TWRP.
Yay.
Hope everyone else is having a better day.
Click to expand...
Click to collapse
For those wondering about updating to B180.....
See this post and links in it for how we updated before if the phone was already unlocked bootloader/rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
reloaded 170 full version on and it worked fine. Need to clean it up, as it threw the bloat back on - but didn't lose anything. Unfortunately, between 2 jobs, and moving (working on new house now, move in a couple weeks, then work on old house to sell it) I'm not seeing much time in my future to play with it much.
Is B180 rootable?
I imagine like the other version so far, it should be.
Ad86shwks said:
Is B180 rootable?
Click to expand...
Click to collapse
I have B170 installed. But I have it debloated, rooted, and custom recovery on it. I want to update to B180. Anyway someone can make it a standalone update? Like B170?
im waiting on the files from someone and i will release a b180 stock update as well as update my rom to b180 once i get the b180 files
b180 uploaded stock preroot atm will do full stock soon b180
i installed the b180 zip. There is one problem wifi is broken.
Thanks for the hard work to update to b180.
hi5five said:
i installed the b180 zip. There is one problem wifi is broken.
Thanks for the hard work to update to b180.
Click to expand...
Click to collapse
wifi is broke? i flashed it before i uploaded it worked fine try doing a clean flash format data system cache etc then flash
Did you previously have B170, then used your zip to update to B180?
madvane20 said:
wifi is broke? i flashed it before i uploaded it worked fine try doing a clean flash format data system cache etc then flash
Click to expand...
Click to collapse
i flashed b170 stock then flashed my b180 stock if wifi is broke i can redo it but it worked on mine just let me know
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
I believe you will need to flash updates as nobody has been able to OTA after unlocking the bootloader.
dabadguycr said:
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
Click to expand...
Click to collapse
divineBliss said:
I believe you will need to flash updates as nobody has been able to OTA after unlocking the bootloader.
Click to expand...
Click to collapse
I was able to update to b140 from b130 from a unlocked bootloader but that was from before I rooted.... It was before root was available.
Thanks for that detail. I wonder which partitions aside from the boot partition get modified after rooting that then breaks OTA from working.
dabadguycr said:
I was able to update to b140 from b130 from a unlocked bootloader but that was from before I rooted.... It was before root was available.
Click to expand...
Click to collapse
---------- Post added at 10:50 PM ---------- Previous post was at 10:35 PM ----------
I don't think there's any way to put your phone back to the state where an OTA will work - at least nothing we currently have on the XDA forums here that I've seen.
You could always try what you wrote below - I expect OTA will fail. If it fails, you could flash B180 - which I believe is unrooted from what I recall @clsA writing about his method to flash B180 in the B170/B180 thread by @madvane20 - but please double check on that before doing it since you want to be able to remain unrooted.
dabadguycr said:
Question: If I unlocked the bootloader and Rooted at B140 but went back to fully stock b150 and than Flashed b160 Stock can I OTA b170 and b180 or do I need to flash? I want to keep this stock since I can't use a few apps rooted.
Click to expand...
Click to collapse
divineBliss said:
Rename
"/system/priv-app/DMClient/DMClient.apk"
by appending ".xxx" to the end using TWRP file manager.
Clear /cache partition.
Reboot and see if it works .
Click to expand...
Click to collapse
hi thanks for this advice buy my device does not have this directory or files. I am in the same boat on 170 slim and fast, got AT&T update and now in force reboot update and fail loop. i really want to find a way to make it stop force rebooting? surely something i can do in twrp terminal. any advice? but alas I might just have to reflash.
make sure u mount system in twrp that folder and file should be there and make sure to clear cache like the other post said