Database Users

M8 Eye Recovery and Root

Hello everyone. Finally i found it. I want to help everyone who search along time this recovery.
This is twrp recovery for One M8 Eye. First please unlock bootloader via HTC DEV. Than ( fastboot flash recovery twrp-m8eye-2.8.0.3.img ) After that flash UPDATE-SuperSU-v2.46.zip ( http://download.chainfire.eu/supersu). Now you have root :good::good:
Thanks Iman Mark and Chainfire
Link: https://drive.google.com/file/d/0B71KxMi9guCSN0V5bU1DSUNaX2c/view?usp=sharing
Please don't forget thanks

This update supersu no longer works. I installed that twrp and did the process for that version of supersu and it said successful. Upon checking supersu, it says the binary files are missing. Then I installed the newer supersu verison through twrp, without deleting the old supersu and now the phone is stuck on htc boot screen. This may work for some, but DO NOT install another supersu over an old one without deleting it first. You WILL get stuck on boot.

Weisheit7 said:
Then I installed the newer supersu verison through twrp
Click to expand...
Click to collapse
"Newer" meaning what? Always be specific, otherwise we can only guess. For all we know, you flashed 2.47, which is "newer" than 2.46.
You should be using the latest stable version, which is currently 2.78, which you can obtain the zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Try flashing this, and hopefully that works. I'm not certain, but as far as I know, you don't need to delete an old SuperSU app, in order for the proper updated one to work.
Also, a word of basic good practice when modding any Android device: Always make sure you are using the current updated methods according to your OS version.
The files in the OP are from July 15, 2015. That is well before Marshmallow existing. Root methods almost always need to be updated with each major OS version update. There is really no reason to have thought SuperSU from over a year ago would work on a current OS version device.

redpoint73 said:
"Newer" meaning what? Always be specific, otherwise we can only guess. For all we know, you flashed 2.47, which is "newer" than 2.46.
You should be using the latest stable version, which is currently 2.78, which you can obtain the zip from here: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Try flashing this, and hopefully that works. I'm not certain, but as far as I know, you don't need to delete an old SuperSU app, in order for the proper updated one to work.
Also, a word of basic good practice when modding any Android device: Always make sure you are using the current updated methods according to your OS version.
The files in the OP are from July 15, 2015. That is well before Marshmallow existing. Root methods almost always need to be updated with each major OS version update. There is really no reason to have thought SuperSU from over a year ago would work on a current OS version device.
Click to expand...
Click to collapse
You're right, and as of right now I have a different issue. I found a link for the Chinese ROM of the htc m8 eye and I successfully installed it. Now the device is on 4.4.4 rooted. I've tried to do the OTA update but each time in stock recovery it fails after about 20-25% and says "system/bin/reboot has unexpected contents" and fails every time. I have uninstalled supersu from the app itself, deleted all of the residual files and checked the phone for root. Root checker says it's not rooted.
How can I fix the OTA problem through stock recovery? I checked the /system/bin/reboot file and there's nothing there specifically that I can see is corrupted or changed. Is there any possibility that supersu has system permissions and is causing this error? If so, how do I fix the /reboot has unexpected contents problem? How can I delete supersu (su) from having system permissions over everything?
I cannot find a stock Chinese ROM for this device, only the rooted one. I'm at a loss here..

Weisheit7 said:
I've tried to do the OTA update but each time in stock recovery it fails after about 20-25% and says "system/bin/reboot has unexpected contents" and fails every time. I have uninstalled supersu from the app itself, deleted all of the residual files and checked the phone for root. Root checker says it's not rooted.
Click to expand...
Click to collapse
Unrooting in order to OTA doesn't work, you need the stock never rooted ROM.

redpoint73 said:
Unrooting in order to OTA doesn't work, you need the stock never rooted ROM.
Click to expand...
Click to collapse
I've read online that if you unroot it the OTA update should go through. It depends on how the root was done, correct? If root has (owner) permissions over system files, how can I put it back to stock? Are you aware of any HTC One M8 eye mels_tuhl stock rom China region? I've scoured the internet forever and cannot find one. If you need my getvar info I'll post it here and I appreciate any help you can potentially give me.

Weisheit7 said:
I've read online that if you unroot it the OTA update should go through.
Click to expand...
Click to collapse
I can't speak to what you read, if you are vague and don't reference any specific website.
What you read is not correct. Its been verified in the M8 forums many times (at least on the "regular" M8). The fact you unrooted, and the OTA doesn't work, also proved it.
Weisheit7 said:
It depends on how the root was done, correct?
Click to expand...
Click to collapse
Incorrect. I haven't seen any root method on the M8, which allows OTA updates after unrooting.
Weisheit7 said:
Are you aware of any HTC One M8 eye mels_tuhl stock rom China region?
Click to expand...
Click to collapse
Unfortunately, no.

redpoint73 said:
I can't speak to what you read, if you are vague and don't reference any specific website.
What you read is not correct. Its been verified in the M8 forums many times (at least on the "regular" M8). The fact you unrooted, and the OTA doesn't work, also proved it.
Incorrect. I haven't seen any root method on the M8, which allows OTA updates after unrooting.
Unfortunately, no.
Click to expand...
Click to collapse
Thanks for taking the time to reply. Since then I have corrected the problem. I downloaded a TWRP backup of Marshmallow from another user on here in a different thread, placed it into my TWRP backup folder, wiped system, internal storage, cache etc and then flashed the backup. Everything went well...marshmallow is on the phone and root is gone.

necaticetinkaya said:
Hello everyone. Finally i found it. I want to help everyone who search along time this recovery.
This is twrp recovery for One M8 Eye. First please unlock bootloader via HTC DEV. Than ( fastboot flash recovery twrp-m8eye-2.8.0.3.img ) After that flash UPDATE-SuperSU-v2.46.zip ( http://download.chainfire.eu/supersu). Now you have root :good::good:
Thanks Iman Mark and Chainfire
Link: https://drive.google.com/file/d/0B71KxMi9guCSN0V5bU1DSUNaX2c/view?usp=sharing
Please don't forget thanks
Click to expand...
Click to collapse
Can you provide another share of the file? The previous link has expired

Update OTA with root and TWRP

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!

Strange root / Recovery issue. Please help

Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you

The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
I would recommend nuking it... wipe the phone data and then install the latest full official firmware over whatever you have now. Then you can go back and start modding.
Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse

Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?

Should be, but it's not safe since you do not know the current root method.

Odds are fairly high that you have malware on the device. Be safe, nuke it.
Jay_Nz said:
Thanks for replying. Just a thought is it possible to flash twrp on top of the existing set up..? And keep the root as it is.?
Click to expand...
Click to collapse

Ok thanks for replying. Anti-virus shows device is clean. I'll do a clean one then as recommended . Flash official firmware first then flash twrp and probably will go for magisk root. Wish me luck as power button is mushed in and have to poke it real hard. I don't even know if bootloader is unlocked or not.. Haha

tdm said:
The axon7 has had its EDL programmer released and a leaked ZTE signed TWRP since shortly after the device went on sale. Anything is possible.
Click to expand...
Click to collapse
where to find these solutions??

Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Druboo666 said:
where to find these solutions??
Click to expand...
Click to collapse

tdm said:
Check for posts by tenfar for the signed twrp.
The firehose was included in one of the leaked update packages. I don't remember which one. I got my copy by running tcpdump while running tenfar"s twrp flasher.
Click to expand...
Click to collapse
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??

Druboo666 said:
also works in B32??i am on b32 and i am stuck with stock recovery as bootloader as been striped from b32 so this will give me TWRP back on B32??
Click to expand...
Click to collapse
I don't know, you can try.

Jay_Nz said:
Hi. I bought 2nd hand zte axon 7 a2017. I found out it has root access but there was no su app. So downloaded superuser from chainfire from play store and it said binary occupied. Downloaded hardware info app and it suggested busy box is installed, rooted, su is phh su and showed the path where it is located. So downloaded phh su from play store and got full root access.! Good but seems like there is no custom recovery. It is still on stock recovery. Is this even possible..? What is the best way to put custom recovery as I really want a nandroid back up.. Please assist. Thank you
Click to expand...
Click to collapse
I just posted some huge verbose $hit on your previous post, just sayin

Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you

Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Jay_Nz said:
Hi, Thank you for your guidance so far. Question - if the previous owner just flashed stock rom then shouldn't g that get rid of root. As you can see from this 2nd post I checked on some root apps and it said it is rooted and su is phh so I downloaded phh su from play store and now rooted apps work fine. Some one pointed out chances of my phone having a malware are quite high so I just want to clean all up and have nandroid g back up. It is an awesome phone. As per your recommendation should I flash using miflash.? Would updating from sd card in phone settings not put it back to complete stock and get rid of root and everything.? When I restart I don't get that device can't be checked for corruption message. I'm on marshmallow at the moment so flashing nougat be ok whether it if from miflash or SD card firmware update.? Appreciate your assistance. Thank you
Click to expand...
Click to collapse

Hi thanks for the reply. I downloaded zip from zte and did an update from phone settings, it pumped me to marshmallow but next release version of zte up. Then another Ota and now I'm on nougat. Checked and root access is gone as expected but funnily enough app shows no root access but busy box binary yes.. Don't know if that's normal. Did a full factory reset too. Now I'm on full Chinese variant stock rom unrooted hence getting Ota. I pressed volume and power button together and managed to get to the screen with start in green and text screen. Other options included restart, power off, reboot to recovery and bootloader and it did show bootloader is locked. I'm thinking of unlocking bootloader, installing TWRP, then root through magisk and perhaps change to A2017U (usa firmware)... Fingers crossed. Thanks again..

tdm said:
Yes, if the previous owner flashed stock only, you would not have root. He either flashed a malicious package or "helpfully" pre-rooted it for you. So you have untrusted and unknown, and regardless of what it may seem, not stock software.
There are several "return to stock" threads. I would study a couple to get a feel for how the procedure works and then follow one of them. Here's one I pulled up in a search:
https://forum.xda-developers.com/axon-7/development/rom-guide-how-to-restore-stock-a2017u-t3549227
I can't vouch for it, it's just the first one that popped up. However, it does seem to be very complete both in instructions and flashing everything from the boot stack on up to boot and system.
Note that b20 is rather old now -- I believe it's the first firmware that shipped on the device. You could make an effort to find newer files. But it's not really necessary, as you should get an OTA update notification after you boot into the stock system.
Good luck!
Click to expand...
Click to collapse
But that's for the A2017U... Be careful with that, he can brick his phone or lose signal

Problem updating from oos 4.5.14 to the latest

Hi friends,
device fully functional.
bootloader unlocked, rooted op5 6/64, everytime reboot message "Your device software can't be checked for corruption"
Tried to update via ota and reboots to TWRC and nothing happens.
Tried flashfire and device freezes
Any ideas?
Thank you

osp1 said:
Hi friends,
device fully functional.
bootloader unlocked, rooted op5 6/64, everytime reboot message "Your device software can't be checked for corruption"
Tried to update via ota and reboots to TWRC and nothing happens.
Tried flashfire and device freezes
Any ideas?
Thank you
Click to expand...
Click to collapse
Hello,
What is you current twrp recovery (file name)?
What is your magisk version?
Is your storage encryped or decrypted?
What new update(version) is shown in ota?
To which version do you want to update?
It's not that easy, you need to check some things.

strongst said:
Hello,
What is you current twrp recovery (file name)?
What is your magisk version?
Is your storage encryped or decrypted?
What new update(version) is shown in ota?
To which version do you want to update?
It's not that easy, you need to check some things.
Click to expand...
Click to collapse
3.2.0-0
17.1
Encrypted
5.1.4
Same
Thank you again

osp1 said:
3.2.0-0
17.1
Encrypted
5.1.4
Same
Thank you again
Click to expand...
Click to collapse
You know that you can't take ota when you're rooted and have custom recovery?
Which steps did you exactly take, please describe as detailed as possible.

strongst said:
You know that you can't take ota when you're rooted and have custom recovery?
Which steps did you exactly take, please describe as detailed as possible.
Click to expand...
Click to collapse
Op5 oos 4.5.14, unlocked bootloader, installed twrp, flash magisk for root and nothing else touched

osp1 said:
Op5 oos 4.5.14, unlocked bootloader, installed twrp, flash magisk for root and nothing else touched
Click to expand...
Click to collapse
If you unlock the bootloader you'll see that warning message, that's normal!
Please flash this twrp https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
Official ones are not the best choice. Then you boot to your new twrp and flash magisk uninstaller, then flash from the .ota folder the downloaded (more than 1GB) oxygenOS 5.1.4 and after it magisk 17.1 before boot.
Report back what's happening and watch the twrp log carefully for errors!

strongst said:
If you unlock the bootloader you'll see that warning message, that's normal!
Please flash this twrp https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
Official ones are not the best choice. Then you boot to your new twrp and flash magisk uninstaller, then flash from the .ota folder the downloaded (more than 1GB) oxygenOS 5.1.4 and after it magisk 17.1 before boot.
Report back what's happening and watch the twrp log carefully for errors!
Click to expand...
Click to collapse
installed the twrp you linked with no problems, but when i tried to flash the ota it says that the zip file is not compatible
this is giving me a headhache, any idea?
thanks a lot :good:

osp1 said:
installed the twrp you linked with no problems, but when i tried to flash the ota it says that the zip file is not compatible
this is giving me a headhache, any idea?
thanks a lot :good:
Click to expand...
Click to collapse
Please post a screenshot or a twrp log with your flashing attempt so I can see the exact error message. Maybe you try to flash another build and not 5.1.4...

strongst said:
Please post a screenshot or a twrp log with your flashing attempt so I can see the exact error message. Maybe you try to flash another build and not 5.1.4...
Click to expand...
Click to collapse
flashed all without problems, but now is stuck on boot animation for an hour
entered TWRP and all folders are numbers and letters ramdomly, at this point i dont care losing all my data, just want my device working

osp1 said:
flashed all without problems, but now is stuck on boot animation for an hour
entered TWRP and all folders are numbers and letters ramdomly, at this point i dont care losing all my data, just want my device working
Click to expand...
Click to collapse
That's the issue with encrypted storage, it's recommended to remove screen lock/pattern/code before such updating processes(see root guide). Go to twrp and format data(where you need to verify the format, not only wipe), that solves the issue.

strongst said:
That's the issue with encrypted storage, it's recommended to remove screen lock/pattern/code before such updating processes(see root guide). Go to twrp and format data(where you need to verify the format, not only wipe), that solves the issue.
Click to expand...
Click to collapse
done, thank you for helping me
now any idea how to root/magisk?
again, THANK YOU SO MUCH

osp1 said:
done, thank you for helping me
now any idea how to root/magisk?
again, THANK YOU SO MUCH
Click to expand...
Click to collapse
I wrote it here https://forum.xda-developers.com/oneplus-5/help/problem-updating-oos-4-5-14-to-t3931444/post79555369

strongst said:
You know that you can't take ota when you're rooted and have custom recovery?
Click to expand...
Click to collapse
Can you elaborate?
Is this OOS-specific? I've gotten OTA updates and my OP5 is rooted with TWRP.
I've not seen this mentioned before, so I'm just curious what environment would prevent OTA updates.

z0m8i3 said:
Can you elaborate?
Is this OOS-specific? I've gotten OTA updates and my OP5 is rooted with TWRP.
I've not seen this mentioned before, so I'm just curious what environment would prevent OTA updates.
Click to expand...
Click to collapse
You cannot take ota updates like on non rooted devices with custom recovery:
-you need to download the full rom rather than ota update file when system updater detects root
-you need to follow some specific installation instructions https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post72799040 otherwise you'll lost twrp, root and maybe your decrypted storage won't let you boot your device
That's what I mean

I still don't 100% follow:
For example, when I flashed Lineage, it explicitly refers to "custom recovery" in the install instructions: https://wiki.lineageos.org/devices/cheeseburger/install
Before I started using my phone, I installed su: https://download.lineageos.org/extras
strongst said:
You cannot take ota updates like on non rooted devices with custom recovery:
-you need to download the full rom rather than ota update file when system updater detects root
Click to expand...
Click to collapse
I have received OTA from Lineage about 2 or 3 updates now. When I choose to install an OTA, it will reboot into TWRP and complete the upgrade.
What did I do differently, that's allowing me to get these updates opposed to what OP is experiencing? Or is what Lineage is doing, is downloading the full image and Oxygen is not?
(I realize the OP is about Oxygen, but I'm trying to make sense of the differences in OTA updates) - Apologies for hijacking the thread, I'm genuinely curious. Thanks strongst for trying to explain!

z0m8i3 said:
I still don't 100% follow:
For example, when I flashed Lineage, it explicitly refers to "custom recovery" in the install instructions: https://wiki.lineageos.org/devices/cheeseburger/install
Before I started using my phone, I installed su: https://download.lineageos.org/extras
I have received OTA from Lineage about 2 or 3 updates now. When I choose to install an OTA, it will reboot into TWRP and complete the upgrade.
What did I do differently, that's allowing me to get these updates opposed to what OP is experiencing? Or is what Lineage is doing, is downloading the full image and Oxygen is not?
(I realize the OP is about Oxygen, but I'm trying to make sense of the differences in OTA updates) - Apologies for hijacking the thread, I'm genuinely curious. Thanks strongst for trying to explain!
Click to expand...
Click to collapse
You cannot compare a stock rom with a custom rom in hat manner. If you have further off topic questions or discussions, Please use the newbie help thread or create a new one

General Nothing OS 1.5.2 update rollout

Just received the stable Nothing OS 1.5 based on Android 13. Finally the wait is over. Check for updates.

What country are you in and what build where you on when you got the update?

bariz143 said:
What country are you in and what build where you on when you got the update?
Click to expand...
Click to collapse
I am using an Indian unit and was using 1.5 beta

Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2

bariz143 said:
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
Click to expand...
Click to collapse
You'll get it by the end of the week.

bariz143 said:
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
Click to expand...
Click to collapse
Nothing stable version 1.5.2 arrived via OTA right now in Czech Republic EU.
I was an official beta tester!

bariz143 said:
Nice. Think its a slow rollout then. Im in Europe/Sweden and no update here yet. Im on Beta 2
Click to expand...
Click to collapse
Got it overnight, Croatia

Is updating with root quite simple? Do I just need to restore the boot, apply the OTA, boot with the new magisk_boot, and if successful, install root permanently via magisk?
I haven't been able to find a guide, and the information is scattered, which makes me a bit unsure. Some questions come to mind: If something modifies the system, do I need to reflash it before the update? How can I find out if it's modified? Does installing Revanced YouTube as root modify the system? Do I need to uninstall any Magisk modules?
To be safe, should I only update when the ROM is available? Alternatively, I can sideload the update via recovery or put it in an OTA folder and run the updater?
What steps if anything goes wrong?
Maybe someone has the energy to write a short guide, which would be greatly appreciated by me and maybe others too.

dedors said:
Is updating with root quite simple? Do I just need to restore the boot, apply the OTA, boot with the new magisk_boot, and if successful, install root permanently via magisk?
I haven't been able to find a guide, and the information is scattered, which makes me a bit unsure. Some questions come to mind: If something modifies the system, do I need to reflash it before the update? How can I find out if it's modified? Does installing Revanced YouTube as root modify the system? Do I need to uninstall any Magisk modules?
To be safe, should I only update when the ROM is available? Alternatively, I can sideload the update via recovery or put it in an OTA folder and run the updater?
What steps if anything goes wrong?
Maybe someone has the energy to write a short guide, which would be greatly appreciated by me and maybe others too.
Click to expand...
Click to collapse
Open magisk, select uninstall and then restore stock images, DO NOT REBOOT, perform the OTA update, after it finishes DO NOT REBOOT, open magisk, select install, select install in the inactive slot.
After it finishes reboot when magisk ask you to.
You can only apply ota updates if system and vendor partitions are not modified.
You have to restore them if you have modified them or deselect the magisk modules that modify them.
Revanced yt is systemless, like busybox, universal safetynet fix and (obv) systemless host.
If a module modifies system it should be noted on the official repo or xda page.
After the update you can re activate all the modules that modify system and vendor.
Update when you feel it, sometimes it's good to wait, sometimes it's pointless.
If you don't have the ota update message you can update with the zip file.
You still have restore stock images, then either install the ota via dialer (which worked for me) or sideload recovery (which didn't).
After it finishes installing, reboot into fastboot and boot the modified boot.img
Open magisk and direct install it.
Depending on WHERE the operation goes wrong you could need just to boot the modified 1.1.8 boot img again to return in the previous context, maybe you could need to flash the full zip because of a soft brick or in the most extreme cases EDL mode with the guide here in xda.