Database Develop

[Q]how can i fully exploit root features & receiving OTA updates?

Hello XDA,
Im quite sure this has already been asked on the forum but i couldn't find an answer.
I need some advise about my recently rooted Nexus 6. I want to fully enjoy from a custom recovery but i dont want to lose the option of receiving OTA updates to my phone.
What do you guys do so your nexus keeps getting the lastest of Android?
Can i use WugFresh's root toolkit to sideload OTA updates even when i have a custom recovery?
What other ways can i use to update Android?
Thanks,

No but you could use the tool kit to reload recovery and stock then take your OTA then reroot and reload TWRP.
And you can side load but it is important you understand exactly what you're doing. the kit does nothing more than you can from the command line it just tries to save you from yourself. it can be a help or hindrance. If you don't understand what's going on it will be the latter
Sent from my Benzo'd Google N6 on VZ

If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...

Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Agreed. OTA is overrated. If I was on T-Mobile or the factory image was not available. I would grab the radio and load what I wanted.
Now I am running the E radio and the i build on VZ
Sent from my Benzo'd Google N6 on VZ

Didgeridoohan said:
you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?

torecdude said:
what do you mean flashing directly?
Can i use Simple recovery switcher to eaisly switch to stock recovery without unrooting and get the OTA update?
Click to expand...
Click to collapse
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.

Didgeridoohan said:
If you've got root and/or custom recovery, since Lollipop you can forget about OTA. And if you're gonna go through the hassle of flashing stock recovery and unrooting to get the OTA, you might as well just flash the latest factory image straight away. Just remember to leave out userdata.img so you can keep your data...
Click to expand...
Click to collapse
Evolution_Freak said:
Click the link in my signature for more information on OTA updates. No modifications of any kind to system can be made for an OTA to flash successfully.
Click to expand...
Click to collapse
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.

Updating via OTA on a Nexus is an undesirable method IMO. As mentioned previously, if you download and flash the factory images, you avoid the potential update failures in an OTA from modified stock parameters. As for recovery, you don't need to flash a custom recovery, you can simply boot a custom recovery from the PC using fastboot and having the recovery image of choice in your platform tools.
fastboot boot name_of_recovery_image_here.img
I don't flash from the device any more. Keeps me out of trouble. Being connected to the PC helps remind me to move a copy of my backup to the PC before flashing.

torecdude said:
Thank you, your thread as helped me alot. But i didnt understand why did you posted OTA files that are flashable with TWRP altough we cant update lollipop with rooted devices?
Guess im going to have to unroot and flash stock recovery to OTA update directly from google or use a pure shamu rom.
Click to expand...
Click to collapse
I put the link to that thread in mine as a quick way for people who are rooted/unlocked and running a custom recovery to find. Those are not the "official" way of updating. They work because someone here put the time in to make them work for unlocked/rooted users. No, you can't use an "official" OTA process if you've altered your device but that method uses TWRP to flash just like you were flashing a custom ROM.
I'm glad my thread has helped you! Since I'm not a developer yet, it is my sole purpose here to help users with anything I can. So a comment like that is very reassuring that I'm on the right path.

[Q] ota update always failing

i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root

Spiffy Jay said:
i had twrp but i wanted ota updates now and i flashed stock recovery and locked the bootloader but after i update from ota i always end up getting installation failed why is that? i didnt root
Click to expand...
Click to collapse
You really dont need to re-lock bootloader. You could have just downloaded and flashed through twrp and then flash supersu. But i am not sure why it is failing on your end.

Same thing here, always installation failed

Try a different type c cable.. Apparently, I was having this issue
Op3t original cable : Android auto and adb side load works perfectly on my op3
But when used on op3t, android auto cannot detect and side load of ota fails.
Used the original cable from Google Nexus 6p, Android auto works perfectly but I didn't try side load adb because I already flash via TWRP instead.
Try changing cables

Found a FIX!
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares

Spiffy Jay said:
its sort of a long process if anyone is interested lmk sorry would post but doont know if anyone cares
Click to expand...
Click to collapse
I too had the same problem. Can you explain me how to get that?

sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps

Spiffy Jay said:
sure @kabeeradam so what you need to do or atleast what worked for me was go all stock recovery and rom and had bootloader locked too.
flash the beta rom from oneplus through sideload then flash the stable rom from oneplus then do the normal ota update and it should work. lmk for any other info also sorry if it looks like a mess this is my first time explaining these types of things. hope it helps
Click to expand...
Click to collapse
I am in 3.5.3 now. Locked bootloader. Still OTA gets failed. When I tried Oxygen OS 3.5.3 through sideload also gets failed. Can you give me the link for beta rom???

@kabeeradam im a complete dumbass i realized that i posted this on the wrong phone it was meant to be one the oneplus 3 not 3t but it should be the same i guess
http://downloads.oneplus.net/devices/oneplus-3/ flash open beta 10 through sideload and then flash oxygenos 3.2.8 and do normal ota update im sorry i just saw

Updatet my rooted OOS over the Air, now I haven't TWRP and SuperSu

Hi There,
I've the Problem that I havent't TWRP-Recovery and SuperSu after Updating to OOS 4.1.1 and Android 7.1.1.
Do someone know if i had to flash TWRP with qiping all Data? Or is there a Way to Flash TWRP and SuperSu without wiping? =(
Sorry I'm new to Android and started with the oneplus 3t. So i didn't know that i hadn't to update the Phone.
Or is the best opinion for me to choose a custom rom? But there are so much, i don't know what to choose.
Thanks for help! =)

Neither TWRP nor SuperSU will wipe anything.
It's totally up to you whether you need a custom ROM or not. If you want features like switching tracks just with your volume keys, you'll totally need a custom ROM since stock ones don't provide this feature. But this is just one example of many.
Regards.
Sent from my OnePlus 3T using Tapatalk

Hm okay, cause when I got my one plus I flashed trwp and had to wipe everything, cause of the encryption or something like that.
I'll try my best today evening, hopefully nothing will go wrong :-O
What do I need to center the clock?
I'll flash trwp and supersu and anything to center the clock today evening.
Don't know if I need a custom rom, are there reason for a custom rom?
Thank you so much!

m4l4g4 said:
Hm okay, cause when I got my one plus I flashed trwp and had to wipe everything, cause of the encryption or something like that.
I'll try my best today evening, hopefully nothing will go wrong :-O
What do I need to center the clock?
I'll flash trwp and supersu and anything to center the clock today evening.
Don't know if I need a custom rom, are there reason for a custom rom?
Thank you so much!
Click to expand...
Click to collapse
If you need help with anything, just ask.
I never had to wipe anything. I just wipe the phone when I want to remove the encryption.
EDIT: regular security patches is one big reason for me to install a custom ROM.

Thanks, I'll ask my questions
But why did the update delete trwp and supersu?
I was happy with OOS but missed the future of centering the clock.
May I ask which custom rom you use?

Updates remove SuperSU because they essentially flash over all non-user partitions (everything except /data, where your files, settings and user apps are stored). To root the OS, SuperSU installs its files in the /boot partition, which gets overwritten during ROM flashes. Root gets deleted any time you flash any mod (including most custom ROMs, since they also replace /boot). The only exception to this is if you flash a custom ROM that comes pre-rooted.
TWRP does not get deleted immediately during flashing, but rather when you first boot up afterwards. OOS will attempt to replace any custom recovery with the stock recovery when it first boots up after updating. You can get around this by either flashing TWRP again, or rooting immediately after flashing a ROM update, before you reboot (flash ROM, wipe cache/delvik, flash root, reboot). Most custom ROMs will not replace your custom recovery.
There's a few threads containing OPSystemUI.apk mods in the Themes, Apps and Mod section, though most of them also contain a bunch of other graphical modifications. If you only want to center your clock and nothing else, it can be achieved by modding OPSystemUI.apk yourself, though there is a bit of a learning curve to it.

m4l4g4 said:
Hm okay, cause when I got my one plus I flashed trwp and had to wipe everything, cause of the encryption or something like that.
Click to expand...
Click to collapse
You are mixing things up a bit but don't worry, I'll explain.
You need to unlock the bootloader first, and that always wipes your data for security reasons. So if your phone is stolen, the thief won't be able to access your data by installing TWRP or a custom rom. After unlocking you install TWRP (custom recovery), and use it to flash stuff. (roms, mods, etc)
After that you only lose data if you (or a rom) mess things up, and your data becomes unaccessible, or you relock your bootloader for whatever reason. That's why you should always backup to a computer before doing major flashing/upgrades, etc.
If you upgrade the rom you'll lose root and/or TWRP, but you can flash it again as explained by others.

Hi there,
so I've flashed TWRP and SuperSu again. You are all right, i haven't to wipe anything. I really mixed up things. But now everything is working for me.
Okay, i have to learn how to get my OPSystemUI.apk modify it and flash it back?
I will seach the threads and learn.

Question after TWRP and root

Hi,
I am all new to Xiaomi (so a big noob into this).
I would like to flash the TWRP and to root the phone.
So here are my questions:
1.After that, will my phone received the OTA updates?
2.Or is better to take the rom from the xiaomi.eu and install them?
3.But with this, will I lose all the settings/application from the phone?
Thank you in advance for the answers.

A little up for my question :angel:

ozzii said:
Hi,
I am all new to Xiaomi (so a big noob into this).
I would like to flash the TWRP and to root the phone.
So here are my questions:
1.After that, will my phone received the OTA updates?
2.Or is better to take the rom from the xiaomi.eu and install them?
3.But with this, will I lose all the settings/application from the phone?
Thank you in advance for the answers.
Click to expand...
Click to collapse
If you unlock you receive ota updates, but if you install twrp and magisk root you can't have ota. You should use a patched boot image maybe.
It is better you install xiaomi eu rom, it updates via ota with twrp also installed.
If you pass to xiaomi eu you have to format data, so you lose your apps and settings just first time

Thank you @HTCDevil for the explanation.
So sad that the root can't be kept.
So I will install twrp and the eu rom. With this I have 2 on the 3 things.
The phone is new so no data yet.....
Thank you again.

ozzii said:
Thank you @HTCDevil for the explanation.
So sad that the root can't be kept.
So I will install twrp and the eu rom. With this I have 2 on the 3 things.
The phone is new so no data yet.....
Thank you again.
Click to expand...
Click to collapse
You can root after installing xiaomi eu.

HTCDevil said:
You can root after installing xiaomi eu.
Click to expand...
Click to collapse
Yes you are right, but I will need to do this on every update, right?
If I understand correct I will need to do if rooted:
-manual update of the rom
-new root of the new rom
Also, will I lose all the settings after an update of the xiami eu image?

ozzii said:
Yes you are right, but I will need to do this on every update, right?
If I understand correct I will need to do if rooted:
-manual update of the rom
-new root of the new rom
Also, will I lose all the settings after an update of the xiami eu image?
Click to expand...
Click to collapse
Xiaomi eu has ota update, it flashes rom in twrp and wipe dalvik / cache automatically, so you don't lose data or settings. If you lose magisk you simply reinstall in twrp, related app and settings stay there

Thank you again @HTCDevil for your help.
Now I am ready for working with my MI9.

General [IMG] Boot + magisk patched boot images

Hi, I have decided to gather boot images and magisk patched images to one thread for now. I will try to edit this thread to be up-to-date. You can let me know what could you want next or if anything is wrong etc.
Stock boot.img files (direct links): ​
EU NE2213_11_A.12​
Stock boot.img - link
EU NE2213_11_A.10​
Stock boot.img - link
​Magisk patched boot.img are here a file that can be downloaded (I am using magisk canary usually, but in Magisk, you can change the channel from the canary to stable etc.) - names as the versions come. ​
Below this there are those magisk patched files which you just flash (or boot and then flash directly from the Magisk app) via fastboot ​

Reserved

Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?

HessNL said:
Don't you need to patch vendor_boot.img as well like OnePlus 9 pro ?
Click to expand...
Click to collapse
Apparently not. I have patched that stock boot via magisk, then via fastboot boot <patchedimage.img> booted (and also tested if it actually boots) and when it booted, via magisk app I did "Direct install (recommended)", rebooted and done.

Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it

Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.

HessNL said:
Oh okay you had a temporary boot we that's good to know well it works that's the most important thing ain't it
Click to expand...
Click to collapse
Yes, because this is probably and currently the most secure option to root it as we haven't got twrp available yet.
BuBbLeFIZzY said:
Noob question I been on locked bootloader for years so haven't been in the root scene, but I have US model NE2215 I'm guessing I need to wait for the firmware to be available to get the boot img? Did I just got my phone too early? Already oem unlocked now just waiting for twrp and root info. I always wanted a OnePlus phone because the community is big, but doesn't seem like much people upgraded from 9 pro.
Click to expand...
Click to collapse
That's not that you have it early. The phone itself is early in spite of rooting and doing things like rooting, custom recoveries, ROMs etc. I currently can't find boot img for your model, but once I do, I will post it here for you with patched one.

Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future

fozzy056 said:
Thank you kouzelnik3 for this thread !
I was going to dl original firmware and patch it myself but found your thread in time with all ready to flash
Rooted OP10 pro done, now i can't wait to see some TWRP and roms in the future
Click to expand...
Click to collapse
You're really welcome, I wanted to unite those currently quite hard rooting stuff!
And yes, I can't wait to see twrp too!

Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.

GeekMcLeod said:
Is there a known stock boot.img of the NE2215_11_A.10? I assume I shouldn't use the 2213_11_A.10.
Click to expand...
Click to collapse
Not yet unfortunately. Or I don't know about it yet. :/

kouzelnik3 said:
Not yet unfortunately. Or I don't know about it yet. :/
Click to expand...
Click to collapse
Yeah.. I googled a lot last night once I got my phone trying to find it to root it. I need me that extra bit of customization.
Is there a way I can get it from my phone?

what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this

Johnstan725 said:
what am i doing wrong here rooted for 7+ years and some reason can't get this working.
Just moved over from ColorOS to Oxygen - when i try to flash the boot.img (patched one) all i get is this
Click to expand...
Click to collapse
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone

Johnstan725 said:
Ignore me but for anyone else that tries looks like i had to reboot bootloader and flash the img via bootloader...
thought it's normally flashed via fastboot?! weird phone
Click to expand...
Click to collapse
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.

g96818 said:
You should wipe the phone and start all over or else you won't be able to take ota updates. Never flash the patched boot image since you bypass the magisk backup feature. You have to wait for the full update package to update if you flash the boot. Ppl have previously had update issues after flashing.
Click to expand...
Click to collapse
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?

Johnstan725 said:
Wiped the phone already, what difference would it make if i remove root or flash stock boot then flash ota and reflash boot?
Click to expand...
Click to collapse
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.

g96818 said:
Not sure what else magisk does during the backup process, but doing what you’re describing didn’t work for users on 8T and they usually ended up soft bricking. Everyone who flashed it vice installing from magisk app had to wait for op to post the full rom or for someone to post a repacked fastboot rom to update.
You do what you need to do, I’m just giving you some experience and recommendations since you just wiped and flashed the boot.
Click to expand...
Click to collapse
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?

Johnstan725 said:
Interesting.
I moved over from ColorOS to oxygen OS, wiped the device then just booted a patched boot img, and installed direct.
I assume I flash ota and go onto magisk and do inactive slot? Where does the issue lie what method should I have gone down?
Click to expand...
Click to collapse
Hmmm. Well you should be fine if you patched the boot and let magisk do the install. I only suggested wiping since you said you flashed the img from the bootloader.
You might run into the same problem I have with the 9RT. I too upgraded from color to oos and couldn’t update at all, even though I rooted from the magisk app. I had to wait for someone to make a fastboot rom. I had no problems updating color following my method, but not oos after switching. Hopefully that’s not the case for you.