Related
Today I got a message to install a new firmware for my transformer. However, if I do so, the installation aborts after one third of download, and I get a Android man, and a triangle with a yellow exclamation mark. The reason is probably that my system is rooted (running stock rom B80 with 8.6.6.19).
I do not really want this update. But how can I stop the update message? I can only delay the OTA for one day in the update activity.
And, does anyone have an information about the update? Is it worth going back to unrooted? And can I root again afterwards?
pretty sure it fixes the app backup hole that you got root with so i wouldn't update.
To prevent notification Freeze DMClient app with titanium backup
also there should be a .zip labled update or something like it in your /asus/ folder if you could post the number on the file name
I am not happy to admit that, but I messed around with build.prop until the system no longer reboots. I have to restore my backup. When I am back, I will report.
Back
OK, I am back.
Installed Titanium Backup, but did not find the option you are referring to. Can you explain, please? Thanks.
I found only one asus folder on /sdcard/asus, and this is for web storage. It is empty. Where do you want me to look for the file number?
You can use this app to temp un-root your device. If you read the subject, some transformer users used this tool for OTA updates.
http://forum.xda-developers.com/showthread.php?t=1241517
Looks too dangerous. I need a rooted device for Cisco VPN. And maybe that small update is not worth the trouble.
Things might be different, if OTA updates to Android 4. But by then, there will be ROMs available too.
can you upload your dlpkgfile? Also, which locale are you in?
Update
I' ve had the same information about update.
It's still 3.2.1.
Just to finish this discussion: I purchased Titanium Pro, and found an option to disable (it is not called "freeze") the update client. Thanks for the hint.
Moto G, currently running 4.4.2 unlocked and rooted with TWRP v2.6.3.0 the firmware is tweaked to my liking with GravityBox. I am also using the Faux123 to over/under clock etc.
Very happy with the performance, features and battery life.
But I am now getting bugged by the Motorola update for 4.4.3
I did try to update and the phone got into a start, reboot loop. So I have restored to my last configuration.
It's been quite sometime since I played with configuring the above and I have gone a bit blank! Can someone please outline the steps that I have to do to complete the upgrade with minimum fuss.
As a side note. I have avoided custom ROMs so far because of all the problems that I was reading about several months ago. But perhaps enough time has elapsed for me to consider going say CM11 now? I would appreciate any comments as to me going down this route. ie. Are all bugs worked out is the Moto G fully functional, does a custom ROM truly provide worthwhile benefits?
Thanks.
I would also like to know this as well as I am currently on 4.4.2 unrooted, but really feel feel like I want to start and get my Moto G rooted and up and running with all the goody's available on the community, but feel like I should wait for the 4.4.3 rollout before I start going through the whole bootloader unlocking, rooting etc.
So I will check back on this post, and thank you to the thread starter as this saves me starting a similar topic.
Rooted 4.4.2 over here as well. Unfortunately I've had no such luck finding a way to update to 4.4.3 while being rooted. I've been through a plethora of guides and suggestions but nothing seems to be working. I'll end up getting an error no matter what I do.
Don't mean to try and hijack your thread, but I've been trying to flash the .zip for the update with both CWM and TWRP but I get an error every time. Anyone have any ideas why? Do I need to configure root-requiring apps beforehand or something?
ugh...same here! Please someone figure this out!
@Kwala Baerr I was hoping for a quick 1,2,3 Guide! I miss posted the question in the General section, then moved it here. I subsequently find a few similar posts in this section. But your message suggests that you may have already tried them which worries me! Anyway I will have a go tomorrow and post here if I get success.
Sent from my Nexus 7 using Tapatalk
@grahamgo oh yea sorry. Well I've tried just about everything. I think I've narrowed down my problem to SoftKeyz messing up my SystemUI.apk so you might still have a chance. Let me know how it goes though!
grahamgo said:
Moto G, currently running 4.4.2 unlocked and rooted with TWRP v2.6.3.0 the firmware is tweaked to my liking with GravityBox. I am also using the Faux123 to over/under clock etc.
Very happy with the performance, features and battery life.
But I am now getting bugged by the Motorola update for 4.4.3
I did try to update and the phone got into a start, reboot loop. So I have restored to my last configuration.
It's been quite sometime since I played with configuring the above and I have gone a bit blank! Can someone please outline the steps that I have to do to complete the upgrade with minimum fuss.
As a side note. I have avoided custom ROMs so far because of all the problems that I was reading about several months ago. But perhaps enough time has elapsed for me to consider going say CM11 now? I would appreciate any comments as to me going down this route. ie. Are all bugs worked out is the Moto G fully functional, does a custom ROM truly provide worthwhile benefits?
Thanks.
Click to expand...
Click to collapse
Put on your phone Us firmware http://forum.xda-developers.com/showthread.php?t=2542219 setup the phone via wifi. Update is about 163mb. After that use Mototool to root the phone and fix the white screen http://forum.xda-developers.com/showthread.php?t=2635706
mabey you can do a beckup of sms https://play.google.com/store/apps/details?id=com.riteshsahu.SMSBackupRestore and https://play.google.com/store/apps/details?id=com.riteshsahu.CallLogBackupRestore
regards
I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!
tarotsujimoto said:
I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!
Click to expand...
Click to collapse
What recovery were you on?
Kwala Baerr said:
What recovery were you on?
Click to expand...
Click to collapse
Here's the thread with information on downloading & installing PhilZ Touch recovery:
http://forum.xda-developers.com/showthread.php?t=2639583
Looks like there's a new stable release out, but I still had PhilZ Touch 6.26.6 Falcon installed.
tarotsujimoto said:
I recently upgraded my stock rooted 4.4.2 Moto G to 4.4.3. The steps you have to take depends on how many modifications you've made. But basically, you need to make sure of these things:
Do a nandroid backup of your working system!
What I did:
Uninstall Xposed modules and Xposed Framework. You *must* do this through the XPosed installer itself.
Re-install/Re-enable system apps that you disabled. For me, I used Titanium Backup, and unfroze the apps that I froze. I made a mistake on my Nexus 7 and uninstalled without backup, which made this process harder.
Repeat the same for any other root apps that made changes to your /system folder.
Uninstall Busybox. If you don't know if you have it or not, download this BusyBox Installer app, and it will tell you. If it is installed, go to the bottom right of your screen and under its preferences, there is a 'delete busybox' option as seen in their 6th screenshot. The order of this is important! Some apps require BusyBox to work and do their installing/uninstalling.
Completely unroot by going to SuperSU's Settings tab, and selecting the Full Unroot option.
Download the latest version of SuperSU onto your SD card if you don't have it already.
Download 4.4.3 update and let it install.
Go into your recovery and re-install SuperSU.
Restore your old root apps like XPosed and BusyBox. I re-installed them and re-did my settings for gravity box and saved my settings using the in-app options for XPrivacy, but you might be able to use Titanium Backup for this if your settings are too extensive.
Alternately, if you're having trouble because you can't find the system apps you need or you're getting an error while updating due to something in your /system folder, you should download stock 4.4.2, extract it, and then re-flash the stock system & boot.img using fastboot or mfastboot. For my XT1034, it was in these images: system.img_sparsechunk1, system.img_sparsechunk2, system.img_sparsechunk3 + boot.img. Yours may differ depending on your model.
Note, I did not test this particular method when I upgraded, but I did use mfastboot to revert to a complete stock 4.4.2 when I changed from CM11 awhile back using this guide.
I was able to keep my bootloader unlocked, and to keep PhilZ's recovery through the update process with no issues.
Hope that helps!
Click to expand...
Click to collapse
Im rooted running stock rom and using exposed installer with gravity box and a few other modules running and all I had to do to update to 4.3.3 was to use Moto Tool AIO v3.0 to revert back to stock kitkat recovery, after that I just accepted the update, installed it, and then went back to a custom recovery. I lost none of my exposed installs or settings, took maybe 10 minutes start to finish and was painless.
tarotsujimoto said:
Here's the thread with information on downloading & installing PhilZ Touch recovery:
http://forum.xda-developers.com/showthread.php?t=2639583
Looks like there's a new stable release out, but I still had PhilZ Touch 6.26.6 Falcon installed.
Click to expand...
Click to collapse
I have just wasted a lot of time...... I tried Philz Touch 6.43.8, no go, then an earlier version, still no go. Then I found a thread saying that there were bugs in later versions, they recommended the use of 6.26.6
I tried it and it works great. However I wasted almost 2 hours finding this out.
castuis said:
Im rooted running stock rom and using exposed installer with gravity box and a few other modules running and all I had to do to update to 4.3.3 was to use Moto Tool AIO v3.0 to revert back to stock kitkat recovery, after that I just accepted the update, installed it, and then went back to a custom recovery. I lost none of my exposed installs or settings, took maybe 10 minutes start to finish and was painless.
Click to expand...
Click to collapse
I appreciate @tarotsujimoto post and I see the logic of this approach. But I too was thinking that it might be less troublesome (but maybe take longer) to go back to factory, update it to 4.4.3 and then re-install Xposed and apps + data, etc using Titanium.
@castuis I am intrigued by your mention of using a custom recovery. Could you please expand on what you backed up and if possible more details on how you did it etc.
I have wasted too much time today getting a working Philz Touch going, (maybe I should have stayed with TWRP!). But I do like the look of Philz 6.26.6 now its working. But will have to put my 4.4.3 update attempt off for a day or so.
Thanks!
Since none of the methods mentioned works for me, I have tried to extract the system.img from the original ROM archive. But how do I mount that system.img_sparsechunk files on Linux? They can not be converted by simg2img or unyaffs either ...
I had no success with any of the "short cut" methods either. I was hoping that @castuis promise of a 10 minute method would come true, but he hasn't been back to expand on his method. I myself reverted the phone to factory, let it upgrade. Then re-rooted, installed xposed and then let Google play reinstall my apps. It's definitely not a quick method. But at least it gave me a clean install. Significant frustration, caused by using Philz touch, but switched to TWRP. Finally did a system backup with Titanium. I thought that was it. Now it looks like there will be a 4.4.4 soon. I'm thinking to ignore it and wait for the next upgrade. @nodh I would wait for 4.4.4 !
Sent from my Nexus 7 using Tapatalk
I've solved my upgrade problem: I've flashed the 176.44.1 (retail Germany, 4.4.3) stock ROM, as described here. Altough I didn't flash the recovery (to restore root with the ClockWorkMod recovey) and didn't erase userdata. Now I've got the upgrade, with all my settings preserved and even rooted again.
Hey community,
after updating my 5.0 LTE 32 Shield Tablet some month ago and rooting it, I came to the conclusion that I don't really need root, but would like to continue receiving OTAs and have a device that just works.
Prio1:
Have a tablet with the latest updates installed.
Prio2:
As 1, but rooted.
I have made a apps+sysapps backup with Titanium.
What do you recommend as the next step?
Thank you very much.
All the best, Esshahn
Some additions:
1. I noticed I'm actually having 5.0 on my Shield. It's the 5.0.1 update plus the nVidia stuff that comes up all the time in the notification center.
I really just want to undo all root and whatnot actions and have a right out of the box experience on my Shield. I already did some stupid stuff (factory reset) and therefore lost my personal data anyway, so there's nothing to lose.
I noticed this forum isn't really active. If anyone doesn't know the answer, but could point me to the right forum for help that would be nice too.
Thank you
flash the full OTA through recovery: https://forums.geforce.com/default/...hread-released-2-17-15-/post/4464815/#4464815
then reinstall supersu through recovery, no factory reset needed
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Esshahn said:
Thank you for replying.
I got annoyed by it all yesterday and flashed 2.1, now I don't have root or custom recovery anymore.
Now the fun part: When I want to update to 2.2 normally (since it's now supposed to be a standard device without any hacks), it just shows the error robot.
So now I'm stuck with 2.1 and can't move left or right.
After reading all those comments about messed up colors in 2.2 I'm wondering if its actually worth the effort to update?
Any idea on that Bogdacutu?
Thanks,
Esshahn
Click to expand...
Click to collapse
you can flash the full OTA through TWRP or CWM, no idea why it won't work with stock recovery though
the update supposedly fixes the graphics glitches that appear in various apps on update 2.1, that might be a good reason to update
Thank you!
Actually, since I didn't have CWM installed anymore, I just sideloaded the latest OTA, which worked nice.
I typically only use between 1GB and 2GB per month of data. However, this month I was notified that I had exceeded my 4GB limit. I increased the limit to 7GB and within 4 days that was exceeded. I've now shut off all cellular data. When I look in Settings > Data Usage > Cellular Data Usage it shows 7.25GB of data used by Android OS. If I tap on Android OS it lists a bunch of apps like com.qti.service.colorservice and com.quicinc.cne.CNEService.CNEServiceApp. I don't know if this list is sorted by which service/app used the most data and there's no more detail I can attain by tapping on the apps listed under Android OS.
Since I have dates and times for some of the largest downloads (868MB on March 27, 12:57AM for example), is there somewhere in the file system where I can see a list of IP addresses connected to and their timestamps to perhaps narrow down who/what is sucking up all my data?
Is there a more thorough way of wiping the phone than a factory reset?
Anybody seen this before and have any suggestions?
Did you root or mod it and are missing an uldate? Even with check for updates turned off people are reporting the same thing.
TonikJDK said:
Did you root or mod it and are missing an uldate? Even with check for updates turned off people are reporting the same thing.
Click to expand...
Click to collapse
I did root it. Then I found out I couldn't get OTA updates anymore. I side loaded the 7.1.1 Sailfish update, build NOF26W. I'm not sure if a new update has since released. After side loading the update I lost root and was unable to get it back.
Months ago, when I first rooted the phone I had the same problem where the OS would continually download the OTA update, fail installation and re-download it. At the time I stopped it through rooting and disabling the update service directly. When I lost root after sideloading the OTA update I figured it wasn't a big deal since I could turn off updates in the Developer Options.
So you're saying the turn off updates option doesn't work?
VonMoltke said:
I did root it. Then I found out I couldn't get OTA updates anymore. I side loaded the 7.1.1 Sailfish update, build NOF26W. I'm not sure if a new update has since released. After side loading the update I lost root and was unable to get it back.
Months ago, when I first rooted the phone I had the same problem where the OS would continually download the OTA update, fail installation and re-download it. At the time I stopped it through rooting and disabling the update service directly. When I lost root after sideloading the OTA update I figured it wasn't a big deal since I could turn off updates in the Developer Options.
So you're saying the turn off updates option doesn't work?
Click to expand...
Click to collapse
It does not work for everyone. Seen it a fair amount, you are the second one today. The other is over in the XL forum.
There is a new update every month. First Monday of the month is when they are released. You are one behind and a new one will be out in two days.
TonikJDK said:
It does not work for everyone. Seen it a fair amount, you are the second one today. The other is over in the XL forum.
There is a new update every month. First Monday of the month is when they are released. You are one behind and a new one will be out in two days.
Click to expand...
Click to collapse
Google wants me to RMA the phone. Not sure how that's going to help though since it's a software problem.
I'm having the same issue. But I have one month 80 gig download this month I'm already at 35 gigs. I was rooted at one point wanted my updates so I updated root is gone but everything works fine but ever since then I have been getting these massive download constantly either on Wi-Fi or cellular I turned off so many things that is not funny backup everything and it's still happening hits exactly the same as the person that first created this thread.
darhoade said:
I'm having the same issue. But I have one month 80 gig download this month I'm already at 35 gigs. I was rooted at one point wanted my updates so I updated root is gone but everything works fine but ever since then I have been getting these massive download constantly either on Wi-Fi or cellular I turned off so many things that is not funny backup everything and it's still happening hits exactly the same as the person that first created this thread.
Click to expand...
Click to collapse
If you're seeing gigs of data usage attributed to Android OS then it's likely repeatedly downloading OS updates that are failing installation. That's what happened to me.
You are correct I tried to download my update and it errored out when installing step 2 then redownloaded so in developer I turned off automatically download updates which I don't think it will help as I turned this off before I reset my room so I think it's stuck just redownloading. Have you figured out why our download is failing? Does it have to do with root that we removed?
darhoade said:
You are correct I tried to download my update and it errored out when installing step 2 then redownloaded so in developer I turned off automatically download updates which I don't think it will help as I turned this off before I reset my room so I think it's stuck just redownloading. Have you figured out why our download is failing? Does it have to do with root that we removed?
Click to expand...
Click to collapse
Removing root isn't enough. I couldn't get updates to work until I installed a factory stock image and relocked the bootloader.
As far as I know there are 3 options.
1.) Root, block updates and never update
2.) Root, block updates, side load your updates and re-root each time to re-block updates
3.) Run stock, unrooted with locked bootloader and take automatic updates
darhoade said:
You are correct I tried to download my update and it errored out when installing step 2 then redownloaded so in developer I turned off automatically download updates which I don't think it will help as I turned this off before I reset my room so I think it's stuck just redownloading. Have you figured out why our download is failing? Does it have to do with root that we removed?
Click to expand...
Click to collapse
You modded something while rooted​ that it doesnt like, or root is not completely removed. You need to flash the update yourself.
VonMoltke said:
Removing root isn't enough. I couldn't get updates to work until I installed a factory stock image and relocked the bootloader.
As far as I know there are 3 options.
1.) Root, block updates and never update
2.) Root, block updates, side load your updates and re-root each time to re-block updates
3.) Run stock, unrooted with locked bootloader and take automatic updates
Click to expand...
Click to collapse
im unlocked, no root, no twrp (verizon edition)
and i take OTA all the time...
I think root and twrp kills ota, not bootloader unlocking......
just an fyi
I think root does also because it's worked fine when I first unlocked bootloader. Also I reinstalled stock room and still can't get it's it has to be what root does to phone
Did you try disable the Automatic System Updates from the Developer Options?
High Data Use by com.quicinc.cne.CNEService.CNEServiceApp
I ran into this issue too after traveling (driving) several days on a rooted Pixel XL (with TWRP and a custom kernel), which at the time was a month behind (running NKG47L, the June OTA for "T-Mobile, Fi carriers, and Rogers").
When I got back from the trip I noticed the phone had used much more data than expected, something along the lines of 75MB per hour (almost a GB a day) -- when all that had been done with the phone (that would use data) was use navigation. Further digging showed the data use was attributed to a process named com.quicinc.cne.CNEService.CNEServiceApp, and some Googling turned up threads that mentioned QualComm and/or T-Mobile and/or Google FI cellular service, but not many examples of how people actually fixed it.
In my case it was fixed (without losing data/apps), by manually updating to the latest OTA (with this approach), and then re-rooting. But I should also mention I switched from the "T-Mobile, Fi carriers, and Rogers" series (which for July would be NKG47M), to the generic Pixel XL series (NJH47D for July).
My suspicion is the phone was downloading the July OTA with cellular data, then tried to apply it (which failed either because the phone was rooted, or had TWRP, and/or had a custom kernel), and was then repeating that sequence every hour.
So, at least in my case, the moral of the story seems to be... If you're rooted and/or running a custom recovery/kernel, make sure you're on the current OTA before spending a lot of time away from recognized WiFi until Google fixes this! Or, as mentioned in an earlier post, have "Automatic system updates" disabled in Developer Options.
com.quicinc.cne.CNEService.CNEServiceApp and com.qti.service.colorservice are backdoor trojans (they have a few other names but all belong to the same group) to access and monitor your device. You need to check to see if it establishes any strange background connections. Please don't ask me how I know but I feel that I have the responsibility to warn everyone.
Need some answers/help...
I was stock, rooted on 8.0....saw a pop-up box yesterday about OTA, didn't think much about since I thought being rooted wouldn't allow the OTA. Have seen the occasional pop-up over maybe the last couple weeks, but I don't normally restart my phone unless it starts to lag or freeze up/run slow. A restart usually fixed that. Was perfectly happy staying on 8.0. I did a shutdown on my phone this evening, and when I restarted it, bam, I'm unrooted on 10 now, specifically, QP1A.190711.020
The phone was bought from Google, unlocked in Oct 2017. I immediately unlocked bootloader and rooted at that time and have been running stock 8.0 since. TWRP and Magisk were used following instructions from the thread here on the forum.
No data was lost after the restart today and 10 seems to be running ok. I did download some data and pictures through my USB-c onto a flashdrive and it did seem to drain my battery FAST while doing it.
What I'd like to know now is how to get root back. I wouldn't mind staying on 10, but if I re-root, will another OTA break my root again? I haven't tried to do a shutdown and a restart again to see what would happen because I'm afraid my phone will brick.
I'm kind of a noob at this, and I don't always understand when you all get technical, but I can follow step-by-step instructions.
First off, how did an OTA actually get through, update and unroot my phone?
And second, can someone point me to step-by-step instructions to re-root my phone on 10, and how do I keep it from happening again?
Thanks for looking and I'd be very appreciative if someone could help me out.
Thank you.
Jim
same here
Same here.
I've got a retail (NON-Verizon) rooted, stock OG Pixel with 8.1 and I've been ignoring the nag to update to 10.
My wife has a retail (NON-Verizon) Pixel 2 that was also stock, rooted 8.1 except she just took the update and asked me about it later.
Both were done with TWRP and Magisk, albeit differing versions.
She's now unrooted at QP1A.191005.007.A1
TWRP v3.2.1-0-walleye is installed.
EDIT: TWRP seems to have been nuked by the OTA upgrade.
I just tried to reboot into TWRP recovery and it's gone.
Magisk Manager app version 5.4.0 (57) + "Latest Magisk Version: v16.0" (I'm pretty sure I rooted via v14.5(1456) though) are present.
"Update Magisk Manager" is nagging about updating /installing MagiskManager-v5.8.2
Root Checker Basic v6.4.6 is also installed.
I'm scared to death to update Magisk or attempt root without some guidance from you fine folks here.
Until then, I'll start having her backup everything she wants to keep in case things go sideways.
I didn't think I was the only one this happened to.
Ok...noticed another issue.
I had Titanium Backup Pro installed. I had several apps frozen before the forced upgrade to 10. Guess what? Those apps are listed as disabled in the app list with no button for re-enabling them. Titanium Backup Pro no longer works because I lost root with the forced update to 10, so I can't unfreeze with Titanium Backup.
Is there any way to unfreeze those apps without re-rooting? Not too sure I even want to attempt to root again.
Also, I haven't shutdown or restarted since the forced update. S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
fjm568 said:
S3NTYN3L, so you're saying you didn't have any issues restarting/rebooting? Other than TWRP being gone, no other issues?
Click to expand...
Click to collapse
Correct.
As for "other issues", none that I, or she, have noticed.
Still breathlessly waiting to hear about how I go about re-rooting without data loss.