Pulled from my US X Pure Edition.
Place in Internal Storage and flash in recovery.
Untested with flashing via TWRP as I've waited all day on complete stock ROM to capture and pull this zip.
MUST BE ON STOCK RECOVERY TO FLASH IT. If you flash it in TWRP and boot loop, without making a backup beforehand, you're on your own. You should've made a backup AS ALWAYS.
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
February 2016 Security Update OTA
Google Drive: blur_version.24.11.18.clark_retus.retus.en.us (flash in stock recovery ONLY)
MD5: e08d5e837d59d9b4ecd88f15ba2906f7
Stock odexed ROM with the February 2016 Security Update applied. No root. Flash in TWRP.
Google Drive: stock_marshmallow_for_moto_x_pure_edition-mphs24.49-18-3 (flash in TWRP)
MD5: 2a1505d2626aa1ef1d18da904a3d5093
Modified boot.img post for use with traditional SuperSU root by DaMadOne here:
http://forum.xda-developers.com/showpost.php?p=65541582&postcount=61
Stock 6.0 Marshmallow Recovery:
IMG version
Google Drive: stock-6.0-mph24.49-18-recovery.img (flash in fastboot or TWRP)
MD5: 2ac9b589a3dc14d4000cbbe082b36ba9
ZIP version
Google Drive: stock-6.0-mph24.49-18-recovery.zip (flash in TWRP)
MD5: a59bb1d9eca25608658cd67f7b4707c2
NOTE: If you get "No command" while booting into stock recovery, hold the power button and press up on the volume key. Options should now be available. I'm not sure why it does that but it used to do it on Nexus devices (and probably still does.)
Spasticdroid said:
Pulled from my US X Pure Edition.
Place in Internal Storage and flash in recovery.
Untested with flashing via TWRP as I've waited all day on complete stock ROM to capture and pull this zip.
Screenshots:
Google Drive: blur_version.24.11.18.clark_retus.retus.en.us
Click to expand...
Click to collapse
So is this captured ota or a stock twrp backup
Google~Android said:
So is this captured ota or a stock twrp backup
Click to expand...
Click to collapse
Spasticdroid said:
capture and pull this zip.
Click to expand...
Click to collapse
It's the OTA.
Hi do you know how to flash this using twrp? I tried and it failed. Thank you in advance.
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
I flashed supersu 2.66 as I had done previous but wouldn't boot past the logo. Anyone gotten this rooted?
Nexus 10
Vinrock2244 said:
Hi do you know how to flash this using twrp? I tried and it failed. Thank you in advance.
Click to expand...
Click to collapse
What error? Where's your recovery log?
Doesn't work with TWRP 3.x? Use an older version.
Doesn't work with the older TWRP 2.x? Use TWRP 3.x.
Not working with TWRP period? Flash stock recovery, flash the OTA, put TWRP back.
blkcr said:
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
Click to expand...
Click to collapse
I don't use Xposed so I wouldn't know if the OTA will work even after uninstalling it. Also, if you're not using systemless root, you'll have to wipe clean. Back up data apps using Titanium or similar. Systemless root however restores original kernel and files.
rocketsaucev2 said:
I flashed supersu 2.66 as I had done previous but wouldn't boot past the logo. Anyone gotten this rooted?
Nexus 10
Click to expand...
Click to collapse
2.67 systemless works fine.
Spasticdroid said:
2.67 systemless works fine.
Click to expand...
Click to collapse
Do you have a link handy? Is it just twrp flashable?
Nexus 10
Also in for a twrp flashable version
rocketsaucev2 said:
Do you have a link handy? Is it just twrp flashable?
Nexus 10
Click to expand...
Click to collapse
Google SuperSU Beta. Should be the first link to Chainfire's thread.
Run this in a Terminal app (with su) or TWRP's Terminal
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Then flash SuperSU 2.67.
Spasticdroid said:
Google SuperSU Beta. Should be the first link to Chainfire's thread.
Run this in a Terminal app (with su) or TWRP's Terminal
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Then flash SuperSU 2.67.
Click to expand...
Click to collapse
Got it. Thanks
Nexus 10
Just popped up on mine as well. Small.
Interesting, the zip contains baseband patches but the version in the OP remained the same. Anyone notice any differences in reception?
Decided to give this a go... Have combined storage and was on a custom stock rom with xposed and viper.
Flashed stock system and recovery, did not wipe data.
Reboot system, let everything update, verify combined storage untouched.
Stock recovery could not find the update since I have combined storage.
Tried TWRP with no success
Flashed stock recovery and sideloaded the update
Update flashed succesfully
Reboot to bootloader and flash TWRP and kernel of choice.
Reboot system
Reboot to bootloader and flash super su, xposed etc.
2.67 non systemless did not work for me. 2.64 worked fine as usual. Well maybe not, getting a lot of system fc's. Will update once I have it worked out.
So flashing 2.62-3, then flashing 2.64 got me out of bootloops and system fc's. Seems to be good to go now.
I am very interested in systemless root specifically for the security updates and benefits of root.
Using this guide
http://forum.xda-developers.com/showpost.php?p=64624664&postcount=454
and SuperSU beta should all be ok?
I am ATM on trupurexmm 2.6.2, frankenclark v0.7, xt1575 and twrp 3.0.0-1.
Can someone on an untouched stock system pull /system after the update and upload it for me? I would like to create a flashable zip so we don't have to go through all this nonsense to update.
Is there any detailed guide on how to make this OTA update work on a machine with root + twrp?
blkcr said:
Hey dude, I just got the notification. I'm using the stock ROM, rooted and obviously bootloader unlocked, also using xposed, do you know if it's safe for me to install the update from the notification? I just don't want to screw it and start from scratch.
Click to expand...
Click to collapse
Same boat here. Stock rooted with Xposed. Rooted with 2.62.
---------- Post added at 09:02 AM ---------- Previous post was at 08:54 AM ----------
There is a stock 6.0 twrp backup file available. Perhaps you could restore that, take the OTA, then root again?
bostonirishguy13 said:
Same boat here. Stock rooted with Xposed. Rooted with 2.62.
---------- Post added at 09:02 AM ---------- Previous post was at 08:54 AM ----------
There is a stock 6.0 twrp backup file available. Perhaps you could restore that, take the OTA, then root again?
Click to expand...
Click to collapse
I was thinking of this same thing.
For I, I have a stock non root twrp backup. Was thinking of flashing the stock ota mm that I have then flashing the recovery to stock then take the ota. Install twrp, then root.
Sent from XT1575,TPXMM 2.6.2,Frankenclark v0.7
shoman94 said:
Can someone on an untouched stock system pull /system after the update and upload it for me? I would like to create a flashable zip so we don't have to go through all this nonsense to update.
Click to expand...
Click to collapse
I was going to keep this to myself and one other person on here. It's unmodified, meaning no root, and odexed. Only converted to be flashable.
Also note that I have included other items in the ROM including radios/modem and an unmodified logo.bin, meaning you will get the "bootloader unlocked" splash.
Too lazy to make a thread for it. Any one wants to? Have at it.
https://drive.google.com/file/d/0B5AiGacWcBRzMTBlWmppOC1DS3c/view?usp=docslist_api
Sent from my XT1575 using Tapatalk
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
someone should write tutorial about rooting, and clarify things about new nougat so let's start
there's 2 way to root stock N :
old phh's superuser
and new systemless superSU, i'm gonna show this way
first make sure you have stock boot partition (not rooted, installed turboZ is OK) and absolutely unlocked bootloader : How to Unlock Bootloader
How to root ?
flash my custom modded TWRP(with Battery Mod Support) : https://www.androidfilehost.com/?w=files&flid=157130
Code:
fastboot flash recovery twrp.img
flash latest TurboZ Stock kernel with TWRP : TurboZ_*_N(or 7.1.1)_Stock.zip
flash latest SuperSU by chainfire with TWRP : https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
(optional) flash latest magisk with TWRP : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot system
FAQ :
Can I mount system as R/W? or swipe "allow system modification" in TWRP first screen?
Yes But just after Mounting, you need to flash TurboZ Kernel otherwise bootloop will happen
Can I update superSU in future?
Sure
any Side Effects?
Not Yet, Please test and tell me how's going on
Can I root This Installed Nougat? : https://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Yes
What About OTA and New Updates ?
after flashing kernel you can't install(sideload) OTA's, so you have to back to stock and not rooted system, update then root again
ScreenShots :
It works.. Thanks
Hi @erfanoabdi, just for your info.. Tried MagiskSU on stock kernel couldn't acquire root but tried with latest TurboZ and its worked.. Now fully rooted which passes SafetyNet as well..
silvercat said:
Hi @erfanoabdi, just for your info.. Tried MagiskSU on stock kernel couldn't acquire root but tried with latest TurboZ and its worked.. Now fully rooted which passes SafetyNet as well..
Click to expand...
Click to collapse
Oh man, thanks for testing
erfanoabdi said:
Oh man, thanks for testing
Click to expand...
Click to collapse
Damn after a reboot SafetyNet failed but everything else works..
If anyone asks why the kernel is necessary when mounting system as R/W.
This is because by default, dm-verity is enabled, and will prevent the phone from booting if it detects an unauthorized change in the system partition. Flashing the kernel will disable dm-verity, which makes it a must if you're going to be using the stock ROM but plan on making changes to the system via root access and whatnot.
If you're going to flash a custom ROM, many already come with their own kernel which disables dm-verity (and forced encryption), so flashing a custom kernel that disables it isn't needed if the ROM already has one (it most likely does). However, I do still recommend that you flash a custom kernel on the stock ROM anyway as it makes it less painful if you choose to go back to a stock ROM as you don't need to flash an entire factory image* just to make your phone work due to dm-verity being an ass. It also gives better performance, so it's quite a win-win.
* - You may be able to get around this by just flashing the boot image and then installing the kernel, but I have not tested this.
Question - do you rally need the custom kernel?
I am just curious to know. - is this a requirement for N?
Granted, I am on MM and not N, but managed to get phh's supersu installled and working without modifying the kernel.
I just flashed TWRP and installed su from there, went into playstore and installed phh's superuser.
No problem so far - all mods are working fine.
Thanks
bert269 said:
I am just curious to know. - is this a requirement for N?
Granted, I am on MM and not N, but managed to get phh's supersu installled and working without modifying the kernel.
I just flashed TWRP and installed su from there, went into playstore and installed phh's superuser.
No problem so far - all mods are working fine.
Thanks
Click to expand...
Click to collapse
Yes,
For this systemless, Only kernel needs to be based on MM (which is not available right now)
On mm you can also flash forcedsystem superSU (available in XDA) with force encryption and dm-verify Disabler patch (available in motoZ forum) only if you want chainfire's superSU
But your phh's superuser is working too
erfanoabdi said:
Yes,
For this systemless, Only kernel needs to be based on MM (which is not available right now)
On mm you can also flash forcedsystem superSU (available in XDA) with force encryption and dm-verify Disabler patch (available in motoZ forum) only if you want chainfire's superSU
But your phh's superuser is working too
Click to expand...
Click to collapse
Thank you kindly - I appreciate your response.
I am on nougat and rooted with phh supersuser so can i uninstall the phh su and follow you guide of flashing turbo kernel and super su
kethsawant said:
I am on nougat and rooted with phh supersuser so can i uninstall the phh su and follow you guide of flashing turbo kernel and super su
Click to expand...
Click to collapse
Yes you need to reflash stock boot.img from firmware's (or your TWRP backup)
Then follow OP guide
erfanoabdi said:
Yes you need to reflash stock boot.img from firmware's (or your TWRP backup)
Then follow OP guide
Click to expand...
Click to collapse
ok then i dont have a twrp back up before rooting the phone so i guess i have to flash the stock boot.img by fastboot mode from original firmware
excuse me, I am in the nougat version that you mention in the main post, but I don't know where to look for the stock boot partition or get the right one, please can you tell me?
Greetings
Getting an error
I get the error
(bootloader) Image not signed or corrupt
with both this and the official twrp recovery. And yes, my bootloader is unlocked.
Any way to fix this?
Stuck at "Your device will boot in 5 seconds"
Hi guys,
I've installed TWRP, I then flashed the TurboZ Stock kernel and it automatically rebooted.
Now it's stuck at the screen
"Your device has been unlocked and can't be trusted
...bla bla bla....
Your device will boot in 5 seconds"
I've tried living it there for hours without any luck.
I've tried flashing TurboZ Stock kernel again but with the same result.
What do I do now?
Thanks
andrea_x said:
Hi guys,
I've installed TWRP, I then flashed the TurboZ Stock kernel and it automatically rebooted.
Now it's stuck at the screen
"Your device has been unlocked and can't be trusted
...bla bla bla....
Your device will boot in 5 seconds"
I've tried living it there for hours without any luck.
I've tried flashing TurboZ Stock kernel again but with the same result.
What do I do now?
Thanks
Click to expand...
Click to collapse
Flash this: http://forum.xda-developers.com/showpost.php?p=69439969&postcount=17
erfanoabdi said:
Flash this: http://forum.xda-developers.com/showpost.php?p=69439969&postcount=17
Click to expand...
Click to collapse
Thanks for the advice, but it didn't work, it's still stuck at "Your device will boot in 5 seconds."
I forgot to mention that the system is encrypted. Does this change things?
I've tried to restore a previous TWRP backup to do a factory reset but when it start up it ask for the password but...there is not keyboard!!!
Do you think that can cause conflict if I use this TWRP? [RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z
Also after rooting I should be on the stock kernel to keep the root? if not, is any other recommended to install?
lilloscar said:
Do you think that can cause conflict if I use this TWRP? [RECOVERY][UNOFFICIAL][XT1650][griffin] TWRP 3.0.3-n2 for Moto Z
Also after rooting I should be on the stock kernel to keep the root? if not, is any other recommended to install?
Click to expand...
Click to collapse
You can use this TWRP
You need to install f2fs patched kernel to keep root
New TWRP is here (testing): https://www.androidfilehost.com/?w=files&flid=157130
Fixed ugly cursor
Updated with latest TWRP version
A new official ColorOS udpate from OPPO is available in my region and at least all Europe I guess.
This is version F1fEX_11_170327. A copy of the OTA update package is here if anyone needs it: F1EX_11_OTA_896-897_patch_201703271119_3cf702307f.zip on MEGA (56.0 MB).
A few screenshots if you want to see the changelog: http://imgur.com/a/5UiiQ
Before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After, full about phone capture: http://imgur.com/CIbWrWX
This is still Android 5.1.1 with a 3.10.28 kernel. No Marshmallow
I'm a bit amazed by the continuous support from OPPO, and especially the security patches integrated in those updates. I was not expecting this from this brand. This is part of what's preventing me from completely switching to LineageOS. This is my only smartphone and I need it to just work.
Now I wish I can unroot my phone, lol
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
Thank you!
But where can I get stock recovery?
You can extract recovery.img from the ColorOS zip.
If someone were to flash this via twrp. When they have followed this thread
https://forum.xda-developers.com/op...pdates-rooted-unlocked-devices-t3395034/page8
They would loose twrp and lose he unlocked bootloader correct?
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
kdd998 said:
This zip is only for OPPO*recovery, not for TWRP. It needs to be modified. If modified, I don't think recovery or unlocked state would change as recovery is not included in the original zip.
Click to expand...
Click to collapse
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
MiniBlu said:
The update zip does contain and flash the locked bootloader(emmc_appsboot.mbn) and also the update zips never contain a recovery.img but do have a script(install_recovery.sh) and patches that patch the latest recovery onto latest boot.img and flash it to recovery. So, yes, flashing it will lock everything down. Modifying it to remove bootloader and recovery is easy enough( I'm happy to do it) but it will also check the current build version on the phone before flashing and refuse to flash unless the rom has been updated to the "896" level, which I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now). There is a new download of full rom available for the 896 version which could also be modified to install from twrp without bootloader and recovery but it does require a full wipe. If enough people want it, I guess it would be good to have a more up to date full clean install of colouros.
Do you think it's worth the effort?
Click to expand...
Click to collapse
It would be nice if we ever go back to color os. But don't rush it. Take your time. Its not a big rush. But I would rather the time be spent in lineage first. Up to you
MiniBlu said:
I have never seen an update zip to go from 894 to 896 (891-894 is the newest update I have seen posted till now).
Click to expand...
Click to collapse
I have a 010 to 896 patch here if needed: https://mega.nz/#!hxxDxAwb!nLa3aDvz3GubMcTaxqaLowRujDt6UKcn0DohuhkclXY
Thanks for all the info. From my point of view, I don't think it's worth the effort. I'd rather work on LineageOS (maybe I'll have time on monday to try new things)
Deleted
kdd998 said:
You can, I did it.
The simplest method:
- copy ColorOS & Project Spectrum zips provided by OPPO
- boot in fastboot mode
- Install stock recovery with fastboot
- Reboot to recovery
- Install Project Spectrum
- Reboot to recovery
- Install ColorOS
You should be stock, relocked.
Click to expand...
Click to collapse
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
wakaranay said:
what if i still have my stock recovery? can i just flash spectrum os then flash color os to unroot my device? coz i rooted my device also using kingroot. i cant update ota.
Click to expand...
Click to collapse
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Jamie_oppo said:
https://www.google.com.au/amp/m.wikihow.com/Unroot-Android?amp=1
That would be the hardest way in my opinion. Try these first.
I would use the supersu app first and if that doesn't work then use the manual delete
Click to expand...
Click to collapse
both not working. i cant still update tru ota
wakaranay said:
both not working. i cant still update tru ota
Click to expand...
Click to collapse
Have you unlocked your bootloader?
Jamie_oppo said:
Have you unlocked your bootloader?
Click to expand...
Click to collapse
locked bootloader
wakaranay said:
locked bootloader
Click to expand...
Click to collapse
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Jamie_oppo said:
I guess flashing spectrum then color os should work. Not 100% but if you get to spectrum then it will work
Click to expand...
Click to collapse
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
wakaranay said:
thanks. i guess firmware flashing will also work. but i dont know what firmware or when i can get that firmware
Click to expand...
Click to collapse
Read post 3 of this thread. Miniblu made a firemware zip. Oops sorry didn't include a link
https://forum.xda-developers.com/oppo-f1/development/rom-unofficial-cyanogenmod-13-t3542718/page23
How to re install the original recovery :crying:
Op started rolling 5.1.8 update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my ONEPLUS A6003 using Tapatalk
5.1.8 is intended for India
dgunn said:
5.1.8 is intended for India
Click to expand...
Click to collapse
no it says it "also contains the 5.1.7 changes for India" since there were issues with 5.1.7 update for India, it also includes the above changes for all other phones as well, so does not seem to be region specific
True.its for all regions.
Sent from my ONEPLUS A6003 using Tapatalk
So, these guys have an actual department dedicated to fixing community reported issues?
That's incredible.
Is it possible to download it without having to install it right away? Phone is rooted and don't want to lose root in case it starts installing.
Sent from my [device_name] using XDA-Developers Legacy app
Done
To those of you that updated and are rooted, can you confirm you're not sporadically losing root like 5.1.7 was doing?
slonn said:
Is it possible to download it without having to install it right away? Phone is rooted and don't want to lose root in case it starts installing.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
If it installs it won't be active until a reboot anyway, so as long as u don't reboot it won't change, even after install
I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).
akxak said:
I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).
Click to expand...
Click to collapse
users were reporting losing root / twrp with OTA's
im on 5.1.7, if i update to 5.1.8 via system update wont it remove my twrp and root and kernel?
afaik it does...
I applied the OTA (full due to root) with the system installer and reinstalled Magisk via Magisk Manager BEFORE rebooting.
I never used TWRP on the OP 6 and rooted with Magisk, I don't need it. When I got my OP6, there was no TWRP available.
Magisk patched the boot image.
After a smooth reboot, the system was updated and Magisk kept installed.
And yes, TWRP is lost when updating that way but can be reinstalled via Fastboot if it is needed.
so what the proper procedure on installing updates without getting wiped?
so far the most logical way of doing it is downloading the OTA
installing it via twrp
then install twrp.zip in twrp after update
then magisk, then kernel and boot.
If you need TWRP, yes. If not, install via system, reapply Magisk to inactive slot before rebooting and reboot.
I am not sure whether TWRP uses the A/B structure. The system updater does so if for any reason the update dies not start, the old working system remains available and will be booted.
The anxiety whether the system will come up after an update is gone for me... I crashed my OP5 applying the Oreo update and had to setup it up from scratch... while abroad on Christmas.
akxak said:
I never lost root with 5.1.7 or any other 5.1.x rom (no twrp).
Click to expand...
Click to collapse
Of course you lose root and TWRP as it loads a stock Boot.img which includes the OOS stock kernel and stick recovery. You will lose TWRP and Magisk, you have to reflash them.
@Eric214, you did read the original question #8 I was answering?
I answered on a sporadically loss of root, which meant for me after having root, it's suddenly gone without having installed something.
Don't jump on an answer without reading the question.
akxak said:
@Eric214, you did read the original question #8 I was answering?
I answered on a sporadically loss of root, which meant for me after having root, it's suddenly gone without having installed something.
Don't jump on an answer without reading the question.
Click to expand...
Click to collapse
Well I must have read the question wrong as it sounded like some were losing TWRP and root sporadically after the update. I didn't not read it I just took it another way... sorry for confusion
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Also, just as easy to just wait for Funk Wizard to post the official FULL zip on his thread and just Flash in TWRP. Last time I jumped the gun early I was on the beta 5.1.6 build but saw no issues whatsoever. I'll sit back this time.
Eric214 said:
Of course you lose root and TWRP as it loads a stock Boot.img which includes the OOS stock kernel and stick recovery. You will lose TWRP and Magisk, you have to reflash them.
Click to expand...
Click to collapse
If you only run Magisk and stock recovery, install the update, but before reboot , re-install Magisk to the other A/B side , then reboot. Then reboot, you'll have Magisk freshly installed.
This doesn't work for TWRP!
Sent from my Brain using my Keyboard
akxak said:
If you need TWRP, yes. If not, install via system, reapply Magisk to inactive slot before rebooting and reboot.
I am not sure whether TWRP uses the A/B structure. The system updater does so if for any reason the update dies not start, the old working system remains available and will be booted.
The anxiety whether the system will come up after an update is gone for me... I crashed my OP5 applying the Oreo update and had to setup it up from scratch... while abroad on Christmas.
Click to expand...
Click to collapse
you do appreciate the A/B structure when a flash goes wrong.
ill wait for the official zip to be flashed via TWRP before going ahead with it
virtyx said:
you do appreciate the A/B structure when a flash goes wrong.
ill wait for the official zip to be flashed via TWRP before going ahead with it
Click to expand...
Click to collapse
Of course I do... the Oreo update in December led to an unplanned factory reset of my OP 5 while abroad in Europe for Christmas. With A/B, this would not have happened because the present working OS (with Magisk/root) remains untouched and the update is installed in the other partition. If for any reason the updated OS is not coming up, the systems falls back and boots the previous (working) OS from where a new update or whatever measure can be initiated.
I wonder if (and if not why) TWRP does support that, installing the full update in the unsused slot (including TWRP itself and Magisk) and then boot that slot.
With these two partitions in use, you keep your phone working and avoid a soft brick. For the manufacturer it avoids trouble for the normal user in case an OTA fails...
I followed my usual guide to upgrade...
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
The August update is 11.0.10.0. I have a patched boot with Magisk 20.4
https://yasmar.net/xda/patched_boot_11.0.10.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.10.0.img.gz
Can you tell how to to update I have only magisk Installed I want to keep magisk.
Aadil Gillani said:
Can you tell how to to update I have only magisk Installed I want to keep magisk.
Click to expand...
Click to collapse
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.
a1291762 said:
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.
Click to expand...
Click to collapse
I only have Magisk and tried the process in the link but I'm always getting the "Couldn't update, installation problem" error. Can I update my phone by simply flashing the patched boot image?
elvinguitar said:
I only have Magisk and tried the process in the link but I'm always getting the "Couldn't update, installation problem" error. Can I update my phone by simply flashing the patched boot image?
Click to expand...
Click to collapse
No, but you may be able to install the OTA if you flash the vanilla image for your version.
The update process tells you which partitions are modified. Details in my guide.
Or just flash the whole rom.
a1291762 said:
No, but you may be able to install the OTA if you flash the vanilla image for your version.
The update process tells you which partitions are modified. Details in my guide.
Or just flash the whole rom.
Click to expand...
Click to collapse
Will I lose my data by flashing the vanilla image?
elvinguitar said:
Will I lose my data by flashing the vanilla image?
Click to expand...
Click to collapse
Flashing a boot image won't lose data unless you use the wrong version and get unlucky.
Flashing any of the partitions that the OTA touches won't lose data.
a1291762 said:
The Magisk thread has the process.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
You don't need a PC because Magisk backs up the vanilla boot and restores it.
It's TWRP that comlicates otas.
Click to expand...
Click to collapse
I've unlocked my bootloader and I've read through the guide a few times now, but there's one thing I need to know before I begin. I'm running stock Android 10 build 11.0.10.0 only having the bootloader unlocked.
Am I able to flash the patched boot.img for V11.0.10.0 that you linked in your other post straight away without having installed any other boot.img previously?
I've only ever flashed Samsungs and a few Sony phones and I'd like to be thorough without cocking up.
RyanCM said:
I've unlocked my bootloader and I've read through the guide a few times now, but there's one thing I need to know before I begin. I'm running stock Android 10 build 11.0.10.0 only having the bootloader unlocked.
Am I able to flash the patched boot.img for V11.0.10.0 that you linked in your other post straight away without having installed any other boot.img previously?
I've only ever flashed Samsungs and a few Sony phones and I'd like to be thorough without cocking up.
Click to expand...
Click to collapse
Yes...
If you flash a patched boot.img then Magisk won't have a backup and you can't OTA without flashing the vanilla image. That's why the standard process is to boot the patched image and then use Magisk Manager to install Magisk.
If you're going to install TWRP then you need to install it before Magisk. There is no flashable TWRP, only the installer, and it trashes Magisk. You must use Magisk Manager to install Magisk after TWRP (or flash it from TWRP) since they both live on the same partition.
a1291762 said:
Yes...
If you flash a patched boot.img then Magisk won't have a backup and you can't OTA without flashing the vanilla image. That's why the standard process is to boot the patched image and then use Magisk Manager to install Magisk.
If you're going to install TWRP then you need to install it before Magisk. There is no flashable TWRP, only the installer, and it trashes Magisk. You must use Magisk Manager to install Magisk after TWRP (or flash it from TWRP) since they both live on the same partition.
Click to expand...
Click to collapse
Thank you. All I want to do for the meantime is root and try out Magisk. I just wasn't sure if I was able to flash the patched .img without needing to flash anything beforehand.
Hopefully I don't make a mistake here and will come back to this thread once I've succeeded/messed up.
---------- Post added at 05:02 AM ---------- Previous post was at 04:24 AM ----------
RyanCM said:
Thank you. All I want to do for the meantime is root and try out Magisk. I just wasn't sure if I was able to flash the patched .img without needing to flash anything beforehand.
Hopefully I don't make a mistake here and will come back to this thread once I've succeeded/messed up.
Click to expand...
Click to collapse
I successfully flashed the patched boot.img and installed Magisk Manager and the only options I have are to flash a zip in recovery (I don't have recovery, hindsight) and "select and patch a file". I don't know how to proceed with either of those options.
EDIT: When flashing the patched boot.img, I didn't realise I had to flash both A/B partitions and that is why it said Magisk wasn't installed. I'm now fully rooted and Magisk is installed.
RyanCM said:
EDIT: When flashing the patched boot.img, I didn't realise I had to flash both A/B partitions and that is why it said Magisk wasn't installed. I'm now fully rooted and Magisk is installed.
Click to expand...
Click to collapse
That's why the standard way is to BOOT the patched image and use Magisk Manager to install.
If you want to flash partitions, you need to use the correct set (a or b). Fastboot can tell you (getvar current-slot). Flashing both is useless, since the inactive set of partitions is only used when doing OTA (or dual boot, for some brave souls).
If you're coming from phones without a/b partitions you should definitely read about them. Several things are quite different.
Please help me boot sign.img unsing img kar do please a kar na ka leya pc ka zaroorat
Please help me boot sign.img unsing img kar do please a kar na ka leya pc ka zaroorat hai mara pass pc nahe ha bootsign.img file link=https://drive.google.com/file/d/1Q172DYs7t7bIo0K_LENCO1OAo6tg0FTz/view?usp=drivesdk and video how to boot sign.img unsing img link=https://youtu.be/ZWphK23KLew
a1291762 said:
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.10.0.img.gz
Click to expand...
Click to collapse
Offline ... can you please reup?
networxpsc said:
Offline ... can you please reup?
Click to expand...
Click to collapse
It's hosted on Google drive. It just loaded for me (private window to simulate anon user). The preview won't work because it's not that kind of file. Just click download.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone gave me the update download notification, but somehow cannot download the OTA - get an error each time. Anyone else on global has same problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Same problem here.
I have a T-mobile device converted to global & rooted. Could it have anything to do with this?
I'm on T-Mobile but bought from OnePlus directly. Same problem.
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
zander21510 said:
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
Click to expand...
Click to collapse
Thanks.
I think that the "Restore Images" option shows up when pressing the "Uninstall" in the Manager. Is it so?
Question: After OTA, can I just "Install" Magisk directly from the Magisk Manager?
Or would I need to patch the boot image and then flash it manually.
sjgoel said:
Thanks.
I think that the "Restore Images" option shows up when pressing the "Uninstall" in the Manager. Is it so?
Question: After OTA, can I just "Install" Magisk directly from the Magisk Manager?
Or would I need to patch the boot image and then flash it manually.
Click to expand...
Click to collapse
I tried the whole restore images and it failed so I tried to fastboot boot the unpatched 11.0.2.2. it booted but no wifi for. Whatever reason. I tried to download 11.0.4.4 on cellular but I don't have a stable signal so it kept failing. Can someone please post the 11.0.4.4 download image and post a link. It would be most appreciated. I cannot find any other way to download it.
zander21510 said:
you have to uninstall magisk using "restore images", then install the OTA, then reinstall magisk to the inactive slot. it's failing the check on the boot partition if you're rooted
Click to expand...
Click to collapse
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
BeardKing said:
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
Click to expand...
Click to collapse
It seems so. With an unpatched boot I can try to download, but with a patched boot it gives an error. I'm starting to lose my fondness for OnePlus.
BeardKing said:
Not that I don't believe you, but OnePlus never did this before for rooted users. It seems odd that they'd start doing this now.
Click to expand...
Click to collapse
Agree, never experienced this earlier.
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
aieromon said:
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
Click to expand...
Click to collapse
Yes, that was it. I had to MSM back to TMobile A10, unlock bootloader, convert to global A10, and then OTA to 11.0.4.4 - and then root.
aieromon said:
It looks like an increment update (593MB) and will not download for rooted devices. I was able to update on an unrooted device but keep getting error message on mine which is rooted.
I guess we have to wait for the full update zip.
Click to expand...
Click to collapse
Will wait for that full update. TY!
Disregard
If you're using the global version you can use these, 11.0.4.4.IN21AA global kernels patched and stock, tested on an IN2010.
Stock: https://www.davesanthology.com/publ....IN21AA/11.0.4.4.IN21AA_boot_stock_IN2010.img
MD5: https://www.davesanthology.com/publ....IN21AA/11.0.4.4.IN21AA_boot_stock_IN2010.md5
Patched: https://www.davesanthology.com/publ...1.0.4.4.IN21AA_boot_magisk_patched_IN2010.img
MD5: https://www.davesanthology.com/publ...1.0.4.4.IN21AA_boot_magisk_patched_IN2010.md5
For any other version you can d/load and install with a rooted device if you temporarily remove root, I've just done it this way. This assumes you have a stock and patched boot.img for your current ROM available (either in Magisk as a backup image or somewhere else). 4.4 wouldn't download whist I had the patched kernel installed, yes a new OP method.
1. Disable (no need to delete) your Magisk modules (to be safe)
2. Flash the stock boot image (for the ROM you're currently using) in fastboot:
Code:
fastboot flash boot <stock_boot>.img
3. Reboot and test, just to be sure (you shouldn't have root)
4. Boot from the patched (root) boot image (for the ROM you're currently using) in fastboot:
Code:
fastboot boot <patched_boot>.img
5. Now you'll have root back but the stock image will still be installed
6. Download the update, if it's taking a long time hit pause them resume a couple of times
7. Install the update and DO NOT REBOOT!
8. Open Magisk and install via direct method and DO NOT REBOOT!
9. Install Magisk again but this time use install to inactive slot method
10. Reboot when prompted
11. Reenable your Magisk modules
Full update is now available for download
aieromon said:
Full update is now available for download
Click to expand...
Click to collapse
Thanks.
Full update link: https://www.oneplus.com/support/softwareupgrade/details?code=PM1586920535300