Don't know what just happened, but here's the best I can explain and hopefully someone smarter than me can figure it out!
My G2 is rooted and running stock 4.4.2 version 24A and I have TWRP 2.7.0.0. I think, besides the hotspot hack, the only thing I had done to it is quarantine LG SetupWizard with App Quarantine. My phone has been trying to push through updates for months, but it never does it successfully becasue of root. Just now, I tried something different to see if I could get the OTA update to install...it was tring to install 26A. I took SetupWizzard out of quarantine and in Superuser I checked OTA survival. After it downloaded the OTA and rebooted it went straight to recovery. From recovery I tried to reboot to system, but it went straight into recovery. So, I restored the backup I made yesterday and tried to reboot back to system again and still it's going to recovery. Any ideas??
Fixed!
Found this thread after a search and reading a thread on the G3.
http://forum.xda-developers.com/showthread.php?t=2451696
Tsip85 said:
Don't know what just happened, but here's the best I can explain and hopefully someone smarter than me can figure it out!
My G2 is rooted and running stock 4.4.2 version 24A and I have TWRP 2.7.0.0. I think, besides the hotspot hack, the only thing I had done to it is quarantine LG SetupWizard with App Quarantine. My phone has been trying to push through updates for months, but it never does it successfully becasue of root. Just now, I tried something different to see if I could get the OTA update to install...it was tring to install 26A. I took SetupWizzard out of quarantine and in Superuser I checked OTA survival. After it downloaded the OTA and rebooted it went straight to recovery. From recovery I tried to reboot to system, but it went straight into recovery. So, I restored the backup I made yesterday and tried to reboot back to system again and still it's going to recovery. Any ideas??
Click to expand...
Click to collapse
The reason why this is happening is you are trying to install the update OTA with a custom recovery. The way these OTA updates work is the OS downloads the file and stores it in a secure location. It has an auto-run updating sequence to allow the OS to update in the regular recovery. Because you have TWRP, TWRP has no idea where to find the file to update the device and therefore, does nothing. However, when you boot up the phone again, it realizes the phone has not yet been updated and goes back into recovery to make sure the update goes through. It is a continuous cycle that therefore never completes it's self. To fix this, run these instructions:
Because the G2 does not have an external SD card, you should do this: use TWRP's awesome "terminal command" option to run the following: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You need to get this PERFECTLY or else you will destroy your phone. Hope this helps.
mach01 said:
The reason why this is happening is you are trying to install the update OTA with a custom recovery. The way these OTA updates work is the OS downloads the file and stores it in a secure location. It has an auto-run updating sequence to allow the OS to update in the regular recovery. Because you have TWRP, TWRP has no idea where to find the file to update the device and therefore, does nothing. However, when you boot up the phone again, it realizes the phone has not yet been updated and goes back into recovery to make sure the update goes through. It is a continuous cycle that therefore never completes it's self. To fix this, run these instructions:
Because the G2 does not have an external SD card, you should do this: use TWRP's awesome "terminal command" option to run the following: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
You need to get this PERFECTLY or else you will destroy your phone. Hope this helps.
Click to expand...
Click to collapse
Thank you. I started searching for a solution and found a thread that had those exact instructions. And this little lesson has now led me to searching for something that will let me quickly and easily switch recoveries if I want to take an OTA.
Tsip85 said:
Thank you. I started searching for a solution and found a thread that had those exact instructions. And this little lesson has now led me to searching for something that will let me quickly and easily switch recoveries if I want to take an OTA.
Click to expand...
Click to collapse
Glad it helped. As for a recovery switcher, you might want to consider using a simple one of the Play Store. They are convenient and easy to use. This thread is really great: http://www.xda-developers.com/simple-recovery-switcher/
Hope this helps.
Tsip85 said:
Thank you. I started searching for a solution and found a thread that had those exact instructions. And this little lesson has now led me to searching for something that will let me quickly and easily switch recoveries if I want to take an OTA.
Click to expand...
Click to collapse
Would you mind sharing that link I need to find my bosses g2 please help
chazla86 said:
Would you mind sharing that link I need to find my bosses g2 please help
Click to expand...
Click to collapse
Yes...check the link I posted on the second post.
Related
I rooted my Nexus One with the 1-click androot and today I've received the 2.2.1 update (FRG83) OTA. I don't want to install it because it'll unroot, but the notification is really persistent and irritating, and I'm afraid I'm going to accidentally hit the install button.
How can I make it go away?
Install a custom recovery, make sure it works, try to flash the rom, it will fail because it needs to stock recovery to install, delete the update from /cache/.
That will at least leave you with a little time before it tries to notify you again. Best thing to do is load a rooted custom rom with a build.prop mod to make it think it's a version better/same so it won't try and update you.
I thought I had to have an unlocked bootloader in order to install a custom recovery or flash custom roms. Is this not the case?
I also have rooted with the one click but have clockworkmod recovery with stock rom. I just received the update ota and I am confused as to what would happen if I attempt to install it. Will it just abort or will it brick the device? Would just a battery pull and reboot be all thats necessary? Has any new roots come out for this update? I really dont want to lose my root. Any and all help is appreciated.
tenbeau said:
I also have rooted with the one click but have clockworkmod recovery with stock rom. I just received the update ota and I am confused as to what would happen if I attempt to install it. Will it just abort or will it brick the device? Would just a battery pull and reboot be all thats necessary? Has any new roots come out for this update? I really dont want to lose my root. Any and all help is appreciated.
Click to expand...
Click to collapse
I was in the same boat as you yesterday. I didn't think of the recovery so I hit update because I was tired of the notification. The phone applied the update successfully and I don't have root anymore. I have no idea how that impacts the recovery since ClockworkMod says the ClockworkMod recovery is installed.
Would like to know as well. Do not want to lose one-click root and would love to get rid of that stupid notification.
check out post #102 here:
http://forum.xda-developers.com/showthread.php?t=791124&page=11
this user says he has gotten it to stop via this method. I cannot verify yet as I have not received the OTA
For me that seems to have stopped the OTA nagg screen.
Using quickboot to reboot then clearing the notification, I have not got another OTA nagg screen. I like the 1 click root, turn on when needed off when not.
tinymiata said:
For me that seems to have stopped the OTA nagg screen.
Using quickboot to reboot then clearing the notification, I have not got another OTA nagg screen. I like the 1 click root, turn on when needed off when not.
Click to expand...
Click to collapse
I'm willing to try anything after 100+ "install later" replies Quickboot here I come
Thank you! I don't know why Quick Boot worked, but it seems that it has. It's now been a couple of hours without a notification message when they were coming back every few minutes. Thanks!
wouldn't it be cool if we got around Google's grand plan to force us to update by driving us crazy!?
Hi, I used PwnMyMoto-1.4.3-TMobile.apk to get root on my T-mobile Moto X.
http://forum.xda-developers.com/showthread.php?t=2444957
Today, there was an OTA update that downloaded and said it would install. Now the phone is stuck in a boot loop. It boots OK but about 45 seconds after loading it shuts down and reboots. I'm guessing its because the PwnMyMoto removed the stock recovery or altered it to be unable to install the OTA update. However I guess the phone still sees the downloaded OTA update and wants to install it, so it reboots the phone to try to install.
I can't post in the PwnMyMoto thread because I'm too new to XDA
I have froze the ota apk to try to prevent this
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
emerica243 said:
I have froze the ota apk to try to prevent this
Click to expand...
Click to collapse
what do you mean by this? Can you tell me how to do that?
jackashe said:
what do you mean by this? Can you tell me how to do that?
Click to expand...
Click to collapse
Freezing a particular app can be done using Titanium Backup. Its available for download on play store. Titanium Backup requires root permissions. Freezing an app will leave the app on your phone but it wont work cuz its frozen lol... the app wont be uninstalled. this way if you decide later that you need the app then you can just unfreeze it and use it.
OK, I have TB and I know it supports freeze. I didn't realize you could freeze the OTA capability as a separate program. However given that I already downloaded the update, its too late to freeze.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
jackashe said:
small update. I used the T-mobile bundle here to get stock recovery.img and put that on my phone (because PwnMyMoto removes it) and then the OTA update installed. I guess instead I could have removed the downloaded update if I knew where it was!! After the OTA I lost root
http://sbf.droid-developers.org/ghost_rcica/list.php
Click to expand...
Click to collapse
FSRBIKER said:
You always have the option to unlock your bootloader with the T-Mobile version. I plan on unlocking the Dev edition I will be buying and then buying a SquareTrade warranty and that will cover any issues I might ever have including breaking/water damage.
Click to expand...
Click to collapse
Yup I almost unlocked the boot loader but instead I was able to flash stock recovery. I wish android itself was smart enough to not try to install OTA when recovery was gone. I finally read through the jcase thread and I think I might have been able to delete the downloaded OTA by running:
Code:
fastboot erase cache
fastboot erase userdata
But I didn't try that. I also don't know what exactly that would have erased.
I will certainly look into a SquareTrade warranty!
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
so if we freeze updater and ota, we should be covered?
not sure about the other suspect apk with is fota.apk. I rename otacerts.apk as well. I may be a little paranoid about this but bricking is definitely not an option
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
jackashe said:
Yeah, root is great... I guess I'll just have to keep fingers crossed that jcase works on 4.2.2 post OTA but since it hasn't even been pushed to all carriers maybe it won't happen. Yes, I should have NOT gotten the OTA, but once it had downloaded my phone was totally unusable until I restored recovery and it installed itself.
Click to expand...
Click to collapse
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
shane1 said:
Curious have you tried to reroot, and for future reference I believe ota are usually in cache under the previous build # for Verizon at least.
Click to expand...
Click to collapse
I did try rooting again using PwnMyMoto-1.4.3-TMobile.apk but it failed to install (since one of the exploits it used is patched)
I have t-Mobile but how would I get to the cache? My phone would boot for about 45 seconds and in that time-frame I could adb shell into the phone but could not find the path for the OTA update. Do you mean it would be in /cache/some-build/ or so?
Yes in cache and you would have to attempt from a PC , which might not have been possible because the phone kept rebooting. Also I am sry for your loss
Would ota root keeper do anything for us?
Sent from my XT1058 using XDA Premium 4 mobile app
IncredibleHulk6 said:
Argh, I'm having the same problem. I have a Sprint version with unlocked bootloader and PwnMyMoto 1.1. Began after OTA update today. I have about 20 seconds after booting up that I'm able to do things on the phone before it goes into a loop; I've tried uninstalling the camera and disabling the gallery, which I thought were the two things that were updated. Safe mode doesn't work, nor does trying to enter recovery through fastboot. I've even tried factory resetting the phone from settings, but it can't do this before the power-down process begins. I haven't had any success with working through adb and the command prompt on this phone (device not found). At this point, I'm SOL and out of ideas with a bricked phone. Any other ideas?
UPDATE... Tried the fastboot erase cache & userdata; essentially performed a hard reset of device. Not the most convenient thing, but at least I have a working phone now.
Click to expand...
Click to collapse
Can you please tell me how you did this? Thanks in advance
Perhaps this thread helps http://forum.xda-developers.com/showthread.php?p=46179190#post46179190
Erk, after getting into the same post-Root update loop, I flashed back to stock using the recipe here: http://forum.xda-developers.com/showthread.php?p=46175635&postcount=8
I now have 13.9.0Q2.X-116-X-17-51 installed.
When I go to System updates to update to the OTA update 13.0Q2.X-116-X-17-54, I get told that I am already updated to the latest version.
Any help would be much appreciated!
jayboyyyy said:
sorry if i or many people would have seeen this earlier we could have stopped you. Always be patient next time because you may have lost root forever now. Not that we know a patch will come through to allow us to maintain root in 4.3, but jcase said he proabbly wouldn't make a rot for 4.3 because it could be a pain and he doens't want to waste any of the exploits he knows of. You could always figure out a way your phone is bad and go exchange it and root again and don't take OTA until someone has figured out something to do to maintain root. It would be worth it for me.
Click to expand...
Click to collapse
manfly9884 said:
Can you please tell me how you did this? Thanks in advance
Click to expand...
Click to collapse
You have to make sure you have downloaded & installed the Android SDK and the latest Motorola Android drivers to your computer. On your phone, shut it down before it has the chance to re-enter the boot loop cycle. Then press the down button simultaneously with the power button for a few seconds and release the down button a split second before releasing the power button. This enters the bootloader (you may have to try it a few times to get it). Plug your phone into the computer and open a command prompt on the computer; type "fastboot erase cache", hit enter, type " fastboot erase userdata" and hit enter. You'll see confirmation in the command prompt and your phone will reboot as factory reset.
So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.
Seems you need a .19 stock system partition image to get rid of the bootloop. Hope somebody can backup his system after OTA and share his image,otherwise you have to wait for official release or take risk to downgrade.
----------------------------
If you can boot from TWRP, you can try put the Xposed-Disabler-Recovery.zip in an USB SD card(maybe need formatted to particular filesystem like ext4) linked your phone with otg cable,then mount the sdcard and flash the zip file via TWRP.
If you're not worried about going back with a full wipe to KK, you can follow this link here Seeing that you can get your phone into fastboot, it'll work fine.
HAXTREME said:
If you're not worried about going back with a full wipe to KK, you can follow this link here Seeing that you can get your phone into fastboot, it'll work fine.
Click to expand...
Click to collapse
Thank you! This seems to have solved the problem (whatever exactly it was) and the mobile data is fine which was what I was most unsure about.
I'm curious, my device was a XT1092GB (or at least, I believe it was a GB) and now shows as a 'reteu' where I believe it used to show as 'retgb'. This isn't a problem as it all seems to work, but should I be expecting the Lollipop OTA update to come through? I deliberately didn't follow through on the last part of that thread and install 5.0 that way, I didn't want to tempt fate! However, I would like the update if possible and am unsure which way to go about doing it.
Again, many thanks for all the suggestions everyone. This is why android is awesome
Its a stock EU 4.4.4 so the OTA should come through. Even if it doesn't, I'm sure there's a 5.0 retgb firmware doing the rounds on this forum.
HAXTREME said:
Its a stock EU 4.4.4 so the OTA should come through. Even if it doesn't, I'm sure there's a 5.0 retgb firmware doing the rounds on this forum.
Click to expand...
Click to collapse
I guess even if the 5.0 OTA doesn't come through (for the reasons as given here, any following OTA updates should be fine, right?
If not, do you reckon then 5.0 rom given in the link you sent would be appropriate or would this be a better route?
Thanks for the help!
Just got a update for my LG G Flex D950 from AT&T. I didn't think twice, and hit update. Now my phone will only go to TWRP. I'm using TWRP v2.8.6.0 any suggestions? All I've done is root it, it has the original ROM it came with.
mine is also soft bricked
I was not rooted and the update installed fine. Just curious what it was....
Edit:
Oh wait this explains everything
(Not really, not at all actually)
http://www.att.com/esupport/softwareUpdateArticle.jsp?sid=KB423840&cv=820
Update summary**
Effective September 17, 2015, AT&T released a software update for the LG G Flex (D950). This update will be available via Firmware Over The Air (FOTA)*using a Wi-Fi connection.****
*
What's changing?
Device security improvements
What to expect after the update**
Although there should be no impacts to settings or data, we recommend that you back up your important files and media prior to upgrading the software.
bryanizmir said:
I was not rooted and the update installed fine. Just curious what it was....
Click to expand...
Click to collapse
My mom, uncle, and I all have the same phone, the only difference is mine is rooted with TWRP, so something with it being rooted, or with TWRP has screwed it up, and I have no idea which it is
try the steps here. scroll down to the terminal commands and that will get you going.
http://www.androidayos.com/2014/10/0...download-mode/
(How to Fix bricked LG G2 stuck in Recovery after taking OTA update
If you have LG G2 rooted and installed with TWRP recovery then suddenly and automatic OTA update came around but then its too late that your phone just stuck in TWRP Recovery. If you bricked your phone after doing an OTA Update with root and TWRP installed and happens that it stuck at recovery. This can be fixed either by installing the official firmware via flashtool using the KDZ file but sometimes your phone can’t boot into Download mode and it won’t connect to the computer, so this could be a very frustrating situation.
Before doing anything else you may first try this, this has been reportedly worked on some LG G2 users at Androidcentral forum and thanks to the folks at XDA-developers for this workaround.
On your TWRP terminal command type this codes.
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then hit enter and reboot.)
I have the same problem. Rooted/TWRM and soft brick.
I get to terminal window, but no keyboard
tap on select when in terminal
---------- Post added at 05:10 PM ---------- Previous post was at 05:05 PM ----------
That should open the keyboard
I don't have select, I have home, back and the icon that put me in the terminal window from the folders
Do you see this?
Full phone
Sonny beach, trying it now
Got it, now how do I get that software update to go away?
Your phone should keep the update... at least mine did
Mine didn't, in fact it just bricked again, because I accidentally hit the update again
Hi Guys, I have the same problem although I have CWM instead of TWRP. I got the D950 ATT version rooted on stock 4.4.2 and the updated came up on my phone yesterday but I kept on clicking remind me later. Until last night I noticed my phone was booted on CWM and when I tried to reboot, it just went back again to recovery. Also tried restoring from my backup, goes normally and completes but after reboot it just goes back to CWM again. I hope there is someone who can help coz I have pictures and files I need from it...
Those same commands should work. Those are Linux commands for the base system
Texas_Dave said:
Those same commands should work. Those are Linux commands for the base system
Click to expand...
Click to collapse
I guess you are right, although I did it via fastboot it still worked and got all my files back. Thanks for the quick reply. And by the way the update notification is still active, do you think I still have to unroot before installing the update or would it be ok not to unroot and just defrost all the bloatwares that came with the stock OS then accept the update? I am just afraid that it might brick my phone if I went through with it...
I'm still soft bricking twice a day, because they force the update when I'm not looking. If someone has a way to unroot or better get rid of that fota crap, I sure would like to know how
Texas_Dave said:
I'm still soft bricking twice a day, because they force the update when I'm not looking. If someone has a way to unroot or better get rid of that fota crap, I sure would like to know how
Click to expand...
Click to collapse
I just wish IOroot had a way to support the G flex on android 4.4.2 so we do not have to go back to JB just to root. At least from KK we only have to do this new software update, then root the device, install recovery and we are good to go. I guess that would be too much to ask right now on a low activity device like ours. For now all I did to stop the update nag, I froze the software update file from Titanium backup rebooted and now the nag is silenced for a while until we get news that it's ok to do the update on our rooted devices running KK.
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
My best guess, based on what Chainfire replied to me when I asked about OTA, is that because you're somehow rooted the OTA will refuse to install. He said that using the "unroot" function in v2.63 (and I suppose in subsequent versions) he was able to apply the OTA and then just had to re-root.
As to the OTA, I read in the long-distant past that once it's been provided to your device you sort of go to the back of the queue, and even pressing the "check for system update" button has no effect. One day your turn will come again. When it happens, before you press the "install now" button, use the unroot function, reboot, and give it another go.
And I would really appreciate it if you could report back on the success or failure, just so we all know - thanks...
And before I close... your alternative is just to download the full ROM from Google, unzip everything in sight (including the zip within the zip), copy system.img to a convenient folder, and use Fastboot to flash system. After that you'll need to re-root (simple flash) and when you reboot everything will be as it was, apart from the version and security update date. I did it myself to MMB29S a week or so ago.
But my lawyer advises me to advise you to take a full backup first and store it off your device before you do anything to your device - just in case, you know?
I will definitely reply if I get the update again in a few days. If it doesn't I'll probably do it manually. I was just really surprised I hadn't gotten the error, just so used to it. Thank you for the info though.
Correct me if I'm wrong, but to install an OTA don't you need to be completely stock, including recovery?
If I'm not mistaken but since 4.3 (I'm probably wrong) if your rooted (before systemless root) when you try to the ota you will always get the dead Android because rooting changes the system files causing the update when it does is checks to think your system is corrupt.
Also it was really bad when people tried going from 5.x.x to 6.x even doing it manually some of us got bootlooped or when starting the phone up after updating manually saying system is corrupt but still starting up fine. Leaving like me having to completely clear out everything and installing the factory image just to not be corrupt and able to use Android pay.
Systemless root though I've not had a single problem and still able to use AP. And is also the first time in years I've gotten as far as I did with the OTA.
Rbh50815 said:
OK I got the notification to update today it's MMB29S, I am on K. I am rooted but stock, unlocked using systemless root for root. I've always been rooted and expected it to fail and have to install manually but this time because I'm not rooted like the old way. So i downloaded and went to install to my surprise dead Android with the triangle didn't show but it went to custom recovery screen twrp. I just hit restart because I've never not had a fail and never seen it do this before. Well when it restarted I was not updated and still on K. I also for the life of me can't get it to redo the ota. Tried to clear system service in apps and recheck but nothing.
So my question is since I'm new to systemless root what should I have done when it went to custom recovery? So that way if I can get it to pop up again I can be updated. Thank you in advance for any help and it would be awesome if possible to update this way without having to manually do it.
Click to expand...
Click to collapse
These small ota's can be done with boot modifications because they don't include any boot.img changes and if they do then they just blanket overwrite what's already there. The only part that is checked is /system. However TWRP won't ever install an ota update for compatibility reasons. Even if you reflash the stock recovery then you'll fail the ota because when you installed TWRP it protected itself (by modifying /system) from being overwritten by the stock recovery which is what unmodded stock android will always do on boot by default. And there are 2 things the ota verification looks for when updating: 1. It looks for whether /system has been ever mounted as Read/Write. 2. It hash checks the /system, if it finds any mismatch it fails. As for the update not showing up again, the ota checker hides the update after a failure to stop from flooding the download server. If you want to extract the update zip you can look in /cache for the zip. But since you don't have an unmodded /system you might as well just download the newest factory image and manually flash the system.img
You can use Wug NRT, unroot with MMB29S provided in the NRT , then root.