Related
Hello,
My wife has a Nexus 4.
I unlocked the bootloader, flashed TWRP, rooted it, and installed busybox.
Yesterday she handed me her phone and it was sitting in TWRP.
She said she got a message saying there was an update and she clicked okay.
I asked her if she saw anything going on but she wasn't paying attention so I didn't know if the update was applied or not.
So... I just rebooted the system from within TWRP.
Looking at her "about phone" it still shows that she is on 4.2.1 and when I check for updates it says she is up to date.
Questions:
What to do now?
Why wasn't the update applied? ... in the past on my Nexus 7 I have done OTA updates with rootkeeper installed and TWRP applied them automatically.
Was the update file deleted from her phone or can I find it somewhere in TWRP and apply it?
Is it like a normal .zip that you install or is it another process?
I'm in the same situation, unsure what to do.
I don't want to have to to do a factory reset for a minor update.
EDIT: Also installing the OTA.ZIP in TWRP fails
Got there in the end:
a) If you want to keep your data & settings and are running the stock rom; only flash boot.img, system.img, and recovery.img (optional) with fastboot.
Here is the JOP40D factory image if you need it. occam-jop40d-factory-ca7602f0.tgz - 327.21 MB
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2145848
Once I did that i was able to flash the OTA.ZIP, no loss of data. I used wugfreshes tool for the flashing btw.
I lost root and my APN settings
alexroborock said:
Got there in the end:
http://forum.xda-developers.com/showthread.php?t=2145848
Once I did that i was able to flash the OTA.ZIP, no loss of data. I used wugfreshes tool for the flashing btw.
I lost root and my APN settings
Click to expand...
Click to collapse
There must be a better way to do this.
That is a huge security risk flashing someone else's untrusted image onto your phone.
What about adb sideload?
You can download the image directly from Google
Sent from my Nexus 4 using Tapatalk 2
You need stock recovery for the ota update to work.
Sent from my Nexus 4 using xda app-developers app
Got my N4 yesterday. Rooted stock 4.2.1, installed latest version of TWRP, setup google account. Got the update to 4.2.2 message and clicked ok.
My TWRP recovery installed the update automatically without any problems.
silverramsrt said:
Got my N4 yesterday. Rooted stock 4.2.1, installed latest version of TWRP, setup google account. Got the update to 4.2.2 message and clicked ok.
My TWRP recovery installed the update automatically without any problems.
Click to expand...
Click to collapse
Did you lose root?
Rizy7 said:
Did you lose root?
Click to expand...
Click to collapse
Yes. The update replaced the recovery_from_boot.p or whatever file and the insecure boot image I had. I just reflashed TWRP, did a factory reset and installed CM anyway.
I just received the notice about the OTA update for android 5.0, if I install it will I keep custom recovery and able to install SuperSU for root access or do I lose complete root access and custom recovery?
If you have enabled ota survival in supersu you won't lose root (not 100% sure). Custom recovery will stay as is.
I think ota will fail quite surely as this time the script looks whether the complete system partition was tampered with which you have done by rooting
So either you first flash a fresh stock system.img or, which would be quicker and what i have done, do a fresh flash with lollipop factory img
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
stock Recovery
Masrepus said:
this time the script looks whether the complete system partition was tampered with which you have done by rooting
Click to expand...
Click to collapse
The KK-to-L OTA update for Nexus 4 works the old way - by validating signature for every file to patch.
tom.stanis said:
The KK-to-L OTA update for Nexus 4 works the old way - by validating signature for every file to patch.
Click to expand...
Click to collapse
Not true, it patches the entire system block directly so OTA will fail in the OP's case.
venu123 said:
Not true, it patches the entire system block directly so OTA will fail in the OP's case.
Click to expand...
Click to collapse
In attached file there is updater script from "LRX21T-from-KTU84P" OTA update. There you can see that it verifies files on system partiton.
Hmm strange..
How come all over the internet people tell you not to do 5.0 ota cause it checks the whole partition hash??
Well.. For me it's too late anyways xD and a fresh install feels really nice (sorry for OT )
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
stock Recovery
Masrepus said:
Hmm strange..
How come all over the internet people tell you not to do 5.0 ota cause it checks the whole partition hash??
Well.. For me it's too late anyways xD and a fresh install feels really nice (sorry for OT )
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
stock Recovery
Click to expand...
Click to collapse
I discovered that the stock rom was available in the development section, I'm up to date.
Masrepus said:
How come all over the internet people tell you...
Click to expand...
Click to collapse
Do you believe in everything what people tell you? It's always better to check by yourself.
tom.stanis said:
Do you believe in everything what people tell you? It's always better to check by yourself.
Click to expand...
Click to collapse
Well.. If quite a few different sources say that the ota mechanism is different this time, i believe it, yes.
And manually downloading the ota wasn't really sensible to me as my internet speed is really slow.
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
stock Recovery
Has it been confirmed possible to download & install the OTA successfully on a rooted device running 4.4.4?
edfernandez2 said:
Has it been confirmed possible to download & install the OTA successfully on a rooted device running 4.4.4?
Click to expand...
Click to collapse
Yes, but you have to unroot (use the clean-up function of SuperSU) and reflash stock recovery (use flashify and transfer recovery.img to your phone from the official 4.4.4 factory image from googles own download page). Also, uninstall all apps that modify your system files, like Xposed framework and mods, BetterBattery etc. I'm not sure if you have to re-lock your bootloader too - I don't think so, but i did it to be sure anyway.
I did all that, and applied the OTA without any problems when the update notification appeared on my phone. You loose no data, but you do loose root.
So today I flashed my VZW Developer edition Moto X back to stock 4.4.4 to download the 5.1 OTA update. I got everything installed an am now trying to obtain root again. Since I have the Dev edition, my bootloader is unlocked so theoretically, I should just be able to flash superuser to get root, right?
Well, I installed my custom recovery TWRP and downloaded the lastest recovery flashable supersu zip file and flashed the zip. When I reboot and open SuperSU it tells my that SU binaries are not installed.
I tried installing both ChainsDD and Clockworkmods version of Superuser as well as SuperSU with TWRP and clockwork recoveries and nothing is working.
Can anyone help me obtain root again?
Thanks!
I flashed this in twrp and it work.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Have you checked this thread out? http://forum.xda-developers.com/showthread.php?t=3140217
[HOW TO] How to Root 5.1 with (unlocked bootloader)
Sent from my XT1575
Thanks guys. Turns out the version of SuperSU I downloaded was not the latest version. I downloaded the beta version and that worked great. Thanks!
Sent from my XT1060 using Tapatalk
dgwood12 said:
So today I flashed my VZW Developer edition Moto X back to stock 4.4.4 to download the 5.1 OTA update. I got everything installed an am now trying to obtain root again. Since I have the Dev edition, my bootloader is unlocked so theoretically, I should just be able to flash superuser to get root, right?
Well, I installed my custom recovery TWRP and downloaded the lastest recovery flashable supersu zip file and flashed the zip. When I reboot and open SuperSU it tells my that SU binaries are not installed.
I tried installing both ChainsDD and Clockworkmods version of Superuser as well as SuperSU with TWRP and clockwork recoveries and nothing is working.
Can anyone help me obtain root again?
Thanks!
Click to expand...
Click to collapse
Would you be able to point me to a thread with the steps to flash stock. I haven't done this since I got the phone and it's true what they say. "If you don't use it you lose it." I just want to get rid of this constant reminder that I have an update to install.
Thanks!!
whopua said:
Would you be able to point me to a thread with the steps to flash stock. I haven't done this since I got the phone and it's true what they say. "If you don't use it you lose it." I just want to get rid of this constant reminder that I have an update to install.
Thanks!!
Click to expand...
Click to collapse
visit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 read post 1 and 2... But Post 2 is mostly what you want.
Anybody figure out to get tether to work?
If you are on Verizon network, all you have to do is add net.tethering.noprovisioning=true to your build.prop. You'll need root for that, and can edit build.prop with any text editor/ root explorer. I can confirm that it works fine with VZW LP 5.1. The benefit of doing this simple procedure instead of using a Xposed module is that you can tethering without having root or Xposed installed. This is especially useful of you plan on using Android Pay which will not work if the phone is rooted.
Sent from my DROID MAXX using Tapatalk
Johnny Wong said:
If you are on Verizon network, all you have to do is add net.tethering.noprovisioning=true to your build.prop. You'll need root for that, and can edit build.prop with any text editor/ root explorer. I can confirm that it works fine with VZW LP 5.1. The benefit of doing this simple procedure instead of using a Xposed module is that you can tethering without having root or Xposed installed. This is especially useful of you plan on using Android Pay which will not work if the phone is rooted.
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
Thanks, worked perfect!
KidJoe said:
visit -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425 read post 1 and 2... But Post 2 is mostly what you want.
Click to expand...
Click to collapse
Real quick before I get started. It seems like option 6 is the right one. I am rooted really just for tether, root explorer, and call master. How do I check to make sure I didn't download Xposed? I don't think I did but I want to be sure first. I haven't tinkered with this since I got it.
Thanks again!!
how did you flash back to 4.4.4?
Johnny Wong said:
If you are on Verizon network, all you have to do is add net.tethering.noprovisioning=true to your build.prop. You'll need root for that, and can edit build.prop with any text editor/ root explorer. I can confirm that it works fine with VZW LP 5.1. The benefit of doing this simple procedure instead of using a Xposed module is that you can tethering without having root or Xposed installed. This is especially useful of you plan on using Android Pay which will not work if the phone is rooted.
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
Android Pay works with root. In order to setup cards you have to uncheck "enable supersu" within supersu first, then setup your cards in Android Pay, then you can go back to supersu and re-enable it by checking the box.
Sent from my Nexus 6 using XDA Free mobile app
whopua said:
Real quick before I get started. It seems like option 6 is the right one. I am rooted really just for tether, root explorer, and call master. How do I check to make sure I didn't download Xposed? I don't think I did but I want to be sure first. I haven't tinkered with this since I got it.
Thanks again!!
Click to expand...
Click to collapse
option 6 only flashes stock recovery.
How did you tether? If you rooted to tether, you likely modified something. You'll need to undo that. Unless you used the Wifi Tether for Root APK, in which case you should be fine with just stock recovery back on there.
Are people getting OTA update on Verizon. It sure sounds like it but I've not got any notification
SR3TLAW said:
Are people getting OTA update on Verizon. It sure sounds like it but I've not got any notification
Click to expand...
Click to collapse
Yes they are, but its rolling out in phases or waves.. so it could be anywhere from a couple of days to a couple of weeks until your phone gets it.
If you can't wait, copies of the OTA Zip files needed were posted in the "waiting room" thread, which you can copy to your phone, and manually install via stock recovery. (Of course just like all past OTA's, your phone has to be stock, stock recovery, no Xposed, etc or the OTA zip wont install)
KidJoe said:
Yes they are, but its rolling out in phases or waves.. so it could be anywhere from a couple of days to a couple of weeks until your phone gets it.
If you can't wait, copies of the OTA Zip files needed were posted in the "waiting room" thread, which you can copy to your phone, and manually install via stock recovery. (Of course just like all past OTA's, your phone has to be stock, stock recovery, no Xposed, etc or the OTA zip wont install)
Click to expand...
Click to collapse
Thank-you
KidJoe said:
option 6 only flashes stock recovery.
How did you tether? If you rooted to tether, you likely modified something. You'll need to undo that. Unless you used the Wifi Tether for Root APK, in which case you should be fine with just stock recovery back on there.
Click to expand...
Click to collapse
I am using WiFi Tether. So option 6 will unroot my device for the OTA? Also I went to the motorola software image page and they only had KXA21.12-L1.26.1-1 available. I have KXA21.12-L1.26-3. Will this end up being a problem? I cannot find the recovery image for 26-3 anywhere... yet.
whopua said:
I am using WiFi Tether. So option 6 will unroot my device for the OTA? Also I went to the motorola software image page and they only had KXA21.12-L1.26.1-1 available. I have KXA21.12-L1.26-3. Will this end up being a problem? I cannot find the recovery image for 26-3 anywhere... yet.
Click to expand...
Click to collapse
It will be a problem, I experienced it. Fortunately somebody in the waiting room thread posted a link to the stock L26 version of 4.4.4 and that got me my ota. With the L26.1 recovery image I couldn't get past the L26.4 ota on my DE to get the 5.1 ota.
Sent from my Nexus 6 using XDA Free mobile app
Fly135s said:
It will be a problem, I experienced it. Fortunately somebody in the waiting room thread posted a link to the stock L26 version of 4.4.4 and that got me my ota. With the L26.1 recovery image I couldn't get past the L26.4 ota on my DE to get the 5.1 ota.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Is there a link available? I'm trying to get my ducks in a row before I make any attempt.
Thanks
whopua said:
Is there a link available? I'm trying to get my ducks in a row before I make any attempt.
Thanks
Click to expand...
Click to collapse
Keep in mind this was done on my XT1060 developer edition with the bootloader unlocked.
http://forum.xda-developers.com/showthread.php?p=62855579
[Waiting Room]Verizon XT1060 Lollipop (5.1) OTA & FXZ thread
http://forum.xda-developers.com/showthread.php?p=62874513
[Waiting Room]Verizon XT1060 Lollipop (5.1) OTA & FXZ thread
I used the second link in this post labeled "here"
Here's good instructions for dirty flashing to stock, I used option 5:
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Once I had the 5.1 ota I ensured I had SuperSU 2.46 zip in my download folder. Then I flashed TWRP 2.8.7.0 and immediately rebooted into TWRP recovery and installed the SuperSU zip and had root.
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 01:06 PM ---------- Previous post was at 01:05 PM ----------
Fly135s said:
Keep in mind this was done on my XT1060 developer edition with the bootloader unlocked.
http://forum.xda-developers.com/showthread.php?p=62855579
[Waiting Room]Verizon XT1060 Lollipop (5.1) OTA & FXZ thread
http://forum.xda-developers.com/showthread.php?p=62874513
[Waiting Room]Verizon XT1060 Lollipop (5.1) OTA & FXZ thread
I used the second link in this post labeled "here"
Here's good instructions for dirty flashing to stock, I used option 5:
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Once I had the 5.1 ota I ensured I had SuperSU 2.46 zip in my download folder. Then I flashed TWRP 2.8.7.0 and immediately rebooted into TWRP recovery and installed the SuperSU zip and had root.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
There's also a link to the full 5.1 sbf in the waiting room thread.
Sent from my Nexus 6 using XDA Free mobile app
I haven't downloaded any security patches since I followed the main guide and rooted my phone.
I now have seen the news regarding the security update and how many critical flaws there are so I would like to update.
How can I do so without losing root?
Losing root shouldn't really be a concern. All you need to do is flash SuperSU again afterwards, which takes about a minute.
https://play.google.com/apps/testing/eu.chainfire.flash
This is an app by Chainfire called Flashfire. It works perfectly for what you want. I have used it myself on a few occasions. Let me know how it worked for you.
Sent from my Nexus 6P using XDA-Developers mobile app
+1 FlashFire
If you are impatient and don't want to wait for the OTA zip, just download the factory image and flash the following files using flashfire.
boot.img
system.img
vendor.img
Remember to disable security before you flash or you will have an issue with the vendor.img.
Heisenberg said:
Losing root shouldn't really be a concern. All you need to do is flash SuperSU again afterwards, which takes about a minute.
Click to expand...
Click to collapse
Hey, so I'm rooted with stock ROM and EX kernel but received the April update, any info why I got it?
I thought if you're rooted you weren't supposed to get an OTA update.
Sent from my Nexus 6P using Tapatalk
Doodsz said:
Hey, so I'm rooted with stock ROM and EX kernel but received the April update, any info why I got it?
I thought if you're rooted you weren't supposed to get an OTA update.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
You'll still receive the OTA, you just can't flash it via the traditional method.
I remember using the FlashFire method a month ago. The update worked and I didn't lose root, but I lost TWRP in the process.
ZabiGarma said:
I remember using the FlashFire method a month ago. The update worked and I didn't lose root, but I lost TWRP in the process.
Click to expand...
Click to collapse
Yes the update replaces TWRP with standard recovery. But I believe you can flash TWRP with Flash Fire.
Sent from my Nexus 6P using XDA-Developers mobile app
dratsablive said:
Yes the update replaces TWRP with standard recovery. But I believe you can flash TWRP with Flash Fire.
Click to expand...
Click to collapse
I couldn't flash it with FlashFire. I had to reinstall it from PC, which ended up with TWRP asking for a password, meaning I had to end up wiping the phone, which was worse than doing the regular OTA update.
ZabiGarma said:
I couldn't flash it with FlashFire. I had to reinstall it from PC, which ended up with TWRP asking for a password, meaning I had to end up wiping the phone, which was worse than doing the regular OTA update.
Click to expand...
Click to collapse
The new version of twrp 3.0.2.0 has been fixed. At least for me it worked.
Nice, I haven't installed the latest TWRP. I'll give it a try.
What I don't recall, though, is if last time I lost the applications I installed by flashing them with TWRP (like viper4android) or which rely on root.
I always remove security before flashing updates. Only issue is setting up the Imprint and adding cards back to Android Pay.
dave2metz said:
https://play.google.com/apps/testing/eu.chainfire.flash
This is an app by Chainfire called Flashfire. It works perfectly for what you want. I have used it myself on a few occasions. Let me know how it worked for you.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Is FlashFire no longer available?
dratsablive said:
Yes the update replaces TWRP with standard recovery. But I believe you can flash TWRP with Flash Fire.
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
If you use FlashFire just deselect recovery from the list when you load the latest update.
Sent from my Nexus 6P using XDA-Developers mobile app
Flash stock recovery and then ADB sideload the update. Links can be found in general. Then when it's done reflash twrp and SuperSU. Pretty easy. I've done it.
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
ponzi314 said:
I know theres treads out there but i feel like they are complicating things or old posts. I am currently rooted with TWRP and stock rom. I want to get rid of damn android update notification. I have the april patches and this is for the may patches. I tried downloading the incremental zip and flashing it in twrp but that didnt work. Can i sideload it with adb? Do I need to remove root before doing that?
Click to expand...
Click to collapse
You must do the following:
1. Return to complete stock - that means get rid of root and TWRP. Best way to do that is download the factory image from Google, extract the boot, recovery, and system images from the factory image, and Flash those, for example: fastboot flash recovery recovery.img Don't flash data.img so you can keep your data.
2. OTAs depend on stock recovery to load, so now that you're back to stock, you have 2 choices. You can simply boot your phone normally, wait for the notification for the update, install it, and you're done - or, you can access android's stock recovery and side load the OTA zip using ADB. Good luck
Sent from my Nexus 6P using Tapatalk
Gamer_Josh said:
*EDITED*
I just faced a similar situation. I was still on the stock launch image (MDA89D), but rooted and using Xposed. I just never took the time before then to update to a newer build, but finally wanted to.
I was going to sideload the most recent OTA update manually via ADB. Then I realized that the Nexus Root Toolkit by WugFresh (link here) should work for that. I performed a nandroid backup, attempted to unroot via SuperSu (which failed), disabled my Xposed modules uninstalled Xposed, then used the Sideload OTA Update option in the toolkit's Advanced Utilities to install the latest OTA (downloaded from Google's site here).
I was a little doubtful that it would work for me on the first try, but it did! I re-rooted using the Toolkit, got things re-enabled, and it's all good.
Also, if you use Xposed, the GravityBox module allows you to suppress notifications, so you could get rid of the update one.
Best of luck getting updated!
Click to expand...
Click to collapse
I forgot to mention that I also had TWRP recovery installed. The result was like it is with a normal OTA update, as none of my data/apps/settings were affected. Worked like a charm!
DJBhardwaj said:
The best way to flash an OTA while your phone is rooted and has TWRP, is by installing it through the FlashFire app. Easy and extremely reliable.
Link: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
Click to expand...
Click to collapse
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.
ponzi314 said:
I tried doing it via the app but it doesnt work. It says its installing then reboots and im still on same version. I used Default settings in the app.
Click to expand...
Click to collapse
You are sure that you used the correct OTA file?
DJBhardwaj said:
You are sure that you used the correct OTA file?
Click to expand...
Click to collapse
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
ponzi314 said:
Pretty Sure. My build is MHC19Q and i used the incremental zip from https://android.googleapis.com/packa...rom-MHC19Q.zip which i got from http://forum.xda-developers.com/showpost.php?p=63049054&postcount=3
Click to expand...
Click to collapse
That's weird. It has worked for me everytime, and most users here.
DJBhardwaj said:
That's weird. It has worked for me everytime, and most users here.
Click to expand...
Click to collapse
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.
tech_head said:
I just download the monthly update and use fastboot without the wipe option and it does the incremental.
I've done this for the last three months, including this one.
Once you are rooted and have TWRP, just use fastboot for updates.
Click to expand...
Click to collapse
Sideloading the update, right?
DJBhardwaj said:
Sideloading the update, right?
Click to expand...
Click to collapse
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.
tech_head said:
I guess you can call it that.
The bottom line is, once you root or install TWRP; the only reliable method is some sort of flash.
If you rooted the phone manually and didn't use some one click tool, then this should be easy.
I shy away from the one click tool because if the tool is not updated or becomes unsupported, what then.
Click to expand...
Click to collapse
I also avoid using any toolkits. Yes I know they are fast and easy, and of course someone's hardwork. But I like to everything manual, same as you. :highfive:
I usually like to do things like that manually, because I like to know how things work. But I was under a bit of a time crunch at that point, so decided to try the Nexus Root Toolkit. Though I do understand the procedure of sideloading OTA updates via ADB, from researching and reading on the forums here.
Anywho, I hope you are able to get it going OP.
The OTA fixed it for me, thank you so much!