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...
Related
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
Woke up to an alert saying there is an update for the MM XT1752 I have.
Managed to extract the firmware since I am S-OFF, rooted and using TWRP 3.0.2-0.
Have not been brave/stupid enough to try to just flash this file yet as I can see it's an updater script one and am not up to speed on how to handle this kind of ZIP file.
I am hoping someone else can figure out if there is a way to use this as is, with out having to flash stock recovery, update, then flash TWRP back.
Phone currently stuck looping between the updater triggering and rebooting the phone into recovery mode until I can nerf that.
Wasnt aware TWRP was trying to flash that update zip (since when was that ever a good idea)?
flash fails with error code 7 and text to the effect that my device isnt a motorola/clark_retasia/clark:6.0/MPHS24.49-20-3/3:user/release-keys or a motorola/clark_retasia/clark:6.0/MPHS24.49-20-4/4:user/release-keys and is instead reporting a ro.build.fingerprint of motorola/clark_retus/clark:5.1.1/LPH23.116-18/18:user/release-keys.
Which makes sense since I was hunting around for a MM ROM a while back and appear to have flashed a US release onto my device (my carrier is VFAU in Australia).
For everyone's info, this is still 6.0 with the May 2016 update, according to http://vodafone.intelliresponse.com...stion=Motorola+Moto+X+Style+-+Software+update
psyvenrix, I had the same error as you even after flashing stock recovery. It might have to do with the custom kernel I installed. I had to flash stock system, boot and recovery before it worked.
xerox3500 said:
For everyone's info, this is still 6.0 with the May 2016 update, according to http://vodafone.intelliresponse.com...stion=Motorola+Moto+X+Style+-+Software+update
psyvenrix, I had the same error as you even after flashing stock recovery. It might have to do with the custom kernel I installed. I had to flash stock system, boot and recovery before it worked.
Click to expand...
Click to collapse
Do you have the stock recovery image (MM on vfau)? Are you able to provide a link please? Thanks.
xerox3500 said:
For everyone's info, this is still 6.0 with the May 2016 update, according to http://vodafone.intelliresponse.com...stion=Motorola+Moto+X+Style+-+Software+update
psyvenrix, I had the same error as you even after flashing stock recovery. It might have to do with the custom kernel I installed. I had to flash stock system, boot and recovery before it worked.
Click to expand...
Click to collapse
Yes still Android 6.0 . Just had the security update to my stock EU X Style. Wonder why we're not getting 6.01?
Sent from my SM-T810 using XDA-Developers mobile app
Just got this security update in the UK
Sent from my XT1572 using XDA-Developers mobile app
My Moto notified me of the update (24.221.4) last night. Is it safe to update (I'm rooted, xposed, adaway, layers .....)? If it is, does it mean getting TWRP, root etc all back or what exactly?
[Odd thing, I'm currently on 24.201.3.clark_reteu.reteu.en.EU.retfr and the update screen is in French, but the phone is in English. I flashed this firmware when I needed to start the phone fresh and this was the only firmware that worked.
Doesn't really matter, I'm in South Africa, and there is no firmware specific for South Africa anyway - probably best if I had the UK firmware in fact.]
Keep looking you'll find it.
Richy101 said:
Yes still Android 6.0 . Just had the security update to my stock EU X Style. Wonder why we're not getting 6.01?
Sent from my SM-T810 using XDA-Developers mobile app
Click to expand...
Click to collapse
I'm on 6.0.1 for a few months now, so how are we not getting 6.0.1? EU
{
"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"
}
Wysłane z mojego XT1572 przy użyciu Tapatalka
Can i just update though guys? With Root, TWRP, etc... Like, can I click "Yes, I'm in"?
tolhaje said:
I'm on 6.0.1 for a few months now, so how are we not getting 6.0.1? EU
Wysłane z mojego XT1572 przy użyciu Tapatalka
Click to expand...
Click to collapse
Who knows how Motorola work these things. Got to say I have no real complaints with my Moto X Style. Stock and still locked and running very well. Yes it has the 'paste' lag but I can live with that for now. No phone has given me the upgrade itch [emoji83] but like everyone here, like to have the latest software version! Wonder when we'll get Android N [emoji8]
Sent from my XT1572 using XDA-Developers mobile app
Can I just update while rooted etc?
Or must I go back to stock first and then update and then redo everything?
Is there an easy way to get back to where I was perhaps, like backing up and restoring data or something?
Sorry guys, but I'm not sure what to do, and others have already updated, but I'm not sure what route they followed.
EDIT: went back to unmodified stock and updated..
TWRP 3.0.0 and rooted. Clicked "Yes, I'm in" and now it's automatically rebooting into TWRP trying to flash that stuff. After booting into system, it starts the update process again and soon ends up in TWRP. Luckily I made a backup beforehand . Be careful, don't click "Yes, I'm in" yet. Do a backup!
Is there anyway to flash the Aus modems for the MXP? I'm running CM13 and I am unable to get mobile data, just get 4G! symbol.
Grtschnk said:
TWRP 3.0.0 and rooted. Clicked "Yes, I'm in" and now it's automatically rebooting into TWRP trying to flash that stuff. After booting into system, it starts the update process again and soon ends up in TWRP. Luckily I made a backup beforehand . Be careful, don't click "Yes, I'm in" yet. Do a backup!
Click to expand...
Click to collapse
I had the same result. But I went back to stock and updated.
So now a new question pops up:
How do systemless installs help if the recovery is TWRP and the update won't go through on TWRP? My supersu was done systemless (didn't work unless I forced systemless).
But this time around I'm looking at doing the xposed systemless (by romracer) as well. For now, I'm just rooted, but should I do everything systemless and an update comes along, how would one go about it? Possibly "fastboot flash recovery recovery.img" and then do the update without TWRP - if that removes TWRP?
In bootloader it still says "Device status: official"..
I chose systemless because it is claimed to be the "neater" solution. I don't really care about OTA anymore - paid attention last time, but after flashing back and forth I don't mind doing it again when another update comes out.
But back to your initial question: reflashing the stock recovery is certainly a part of the solution. Might be possible you also have to flash stock boot.img. Don't know how systemless xposed works (probably similar), but systemless root works by modifying the boot.img. So it is not stock anymore.
Regards Grtschnk
easiest way is to reflash stock system, boot and recovery. no need to wipe data (for minor updates only), then flash update. or, wait for the full system image to be posted.
as posted systemless really doesn't matter unless you just want android pay and titanium backup.
I'm running a rooted SM-J700P
Will I ever be able to get an update to Android nougat, either through a custom ROM or official update?
I was not able to flash TWRP successfully, I would have to use Odin to flash a custom ROM
Virgin mobile galaxy J700P
adhdluke said:
I'm running a rooted SM-J700P
Will I ever be able to get an update to Android nougat, either through a custom ROM or official update?
I was not able to flash TWRP successfully, I would have to use Odin to flash a custom ROM
Click to expand...
Click to collapse
Did you flash root program threw odin if you flash twrp threw odin 3.12.5 on check auto reboot pull battery boot into recovery an flash superSU SR5 2.8.2 zip then boot system !
J700P has Oreo.
I just got nougat 7.1.1 official update on my boost mobile j700p yesterday and it runs way faster and smoother
J700p
bprsk8r4272 said:
I just got nougat 7.1.1 official update on my boost mobile j700p yesterday and it runs way faster and smoother
Click to expand...
Click to collapse
Thanks for your post I'm on virgin mobile got the update today after going back to stock firmware thanks for the heads up !!
I JUST got the nougat update but now old rooting method no longer works. Is there not a new one yet?
{
"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"
}
J700P
jrock77420 said:
I JUST got the nougat update but now old rooting method no longer works. Is there not a new one yet?
Click to expand...
Click to collapse
Has any one tried twerp then superSU st 2.8.5 zip or Magisk ?
Can anyone get the Odin flash file for this? I bricked mine playing around trying to re-root and I cannot find anywhere to download it. Trying to re-flash marshmallow doesn't work
J700P
fedaykinofdune said:
Can anyone get the Odin flash file for this? I bricked mine playing around trying to re-root and I cannot find anywhere to download it. Trying to re-flash marshmallow doesn't work
Click to expand...
Click to collapse
What rooting process did you use ? Try factory reset then reinstall twrp unclick auto reboot in Odin pull battery boot twrp flash Magisk then SR superSU 2.8.2 zip an reboot see if that works it may take up to 8 minutes to boot !!
peter couniaz said:
What rooting process did you use ? Try factory reset then reinstall twrp unclick auto reboot in Odin pull battery boot twrp flash Magisk then SR superSU 2.8.2 zip an reboot see if that works it may take up to 8 minutes to boot !!
Click to expand...
Click to collapse
You should always be flashing the latest SuperSU or Magisk, older versions can cause issues.
minz1 said:
You should always be flashing the latest SuperSU or Magisk, older versions can cause issues.
Click to expand...
Click to collapse
I flashed SuperSU, I had debated factory resetting before trying it but I figured what the hell... Just ended up with a frozen boot screen, but could still interact with the UI (volume, swipe unlock, ok google, etc). Then to make things worse, I accidentally wiped system when I went back in to try again. Yeah...
I managed to build myself an odin flash file to downgrade to AQF3, but of course bootloader and fw versions stayed as BQJ2, even without root software update was still unhappy so couldn't just OTA back to 7.1.1. I went ahead and installed your Lineage 14.1 for the time being, which I'd been holding off doing until I got to test drive the official Nougat because (for some reason) I really enjoy the stock ROM.
I've spent the last 2 days scouring every shady site I could find to hunt down the stock J700PVPE2BQJ2 OTA file, either an update zip or odin flash would be fine, I think. So lame that I spent the better part of 2017 waiting for the official update instead of installing Lineage, how embarrassing.
Anyhow, if anyone would be awesome and snatch the OTA file and upload it somewhere, I'm sure there'd be many grateful people!
peter couniaz said:
Thanks for your post I'm on virgin mobile got the update today after going back to stock firmware thanks for the heads up !!
Click to expand...
Click to collapse
yup no problem
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
Frist off Im not responsible for anything that happens to your phone!!!
MUST HAVE UNLOCK BOOTLOADER!!
Steps to root
If you are on 11.2.6.6. and rooted
to take update you must flash stock boot.img can be found in link
reboot to bootloader
fastboot flash boot boot11.2.6.6 .img
once done
fastboot reboot
take update
once update is completed
reboot to bootloader
now down load the PATCHEDBOOT.IMG
and flash
fastboot flash boot patched-11.2.7.7.img
once done
fastboot reboot
BOOM NOW YOUR AR ROOTED!!!
STOCK 11.2.6.6 FIXED AND TESTED THANKS TO
mattie_49
LINKS / HELP
BOOT.IMGS
HELP
{
"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"
}
I should have read this beforehand but I did it the same way as always. Magisk, restore images, OTA updates, magisk install to inactive slot and I get this and I can't get it to go away and it didn't update either. Root is gone as well but it didn't update.
Edit: it fixed itself after the 3rd attempted update. Lost root but that's an easy. I don't know why it did it. Leaving for anyone else that might have this issue
Josh McGrath said:
View attachment 5335417
I should have read this beforehand but I did it the same way as always. Magisk, restore images, OTA updates, magisk install to inactive slot and I get this and I can't get it to go away and it didn't update either. Root is gone as well but it didn't update.
Edit: it fixed itself after the 3rd attempted update. Lost root but that's an easy. I don't know why it did it. Leaving for anyone else that might have this issue
Click to expand...
Click to collapse
please try new uploaded stock boot imgs there fixed now sorry
so, what I (a newbie to rooting without TWRP) should understand is that if I am on stock I just have to unlock bootloader and flash the patched .img?
FizzyAps said:
please try new uploaded stock boot imgs there fixed now sorry
Click to expand...
Click to collapse
Just updated through updated stock image. Thanks for all your efforts
In my case I have found that it is not necessary to flash the stock boot image in order to update. I simply installed the update, rebooted to bootloader, booted the patched boot.img (not flashed), and installed Magisk to my boot partition from there. That way you don't permanently mismatch your ROM from your boot partition in case you are not using global ROM (which is the case for me). I don't know if the boot partition actually differs between the ROMs but this feels cleaner
Won't let me download the OTA after going back to stock bootloader. I have my CN OP9 cross flashed to global. I keep getting Couldn't Update Installation Problem. Guess i'll wait for Oxygen Update.
notiflux said:
In my case I have found that it is not necessary to flash the stock boot image in order to update. I simply installed the update, rebooted to bootloader, booted the patched boot.img (not flashed), and installed Magisk to my boot partition from there. That way you don't permanently mismatch your ROM from your boot partition in case you are not using global ROM (which is the case for me). I don't know if the boot partition actually differs between the ROMs but this feels cleaner
Click to expand...
Click to collapse
You can't install they update if rooted it errors out
hmmm. im coming from rooted global 255 and I uninstalled magisk, flashed stock 255 and rebooted. tried to update to the partial 277 but it always fail. What am i missing here? maybe the stock 255 that i have is bad?
infamousvincci said:
hmmm. im coming from rooted global 255 and I uninstalled magisk, flashed stock 255 and rebooted. tried to update to the partial 277 but it always fail. What am i missing here? maybe the stock 255 that i have is bad?
Click to expand...
Click to collapse
please click the help link we have untouched stock 11.2.5.5 there
FizzyAps said:
You can't install they update if rooted it errors out
Click to expand...
Click to collapse
if it detects that your device is rooted, it will switch to downloading the full update instead of the incremental one. Maybe it is different on global ROM, but that's what worked for me
Thanks, updated from 11.2.4.4 with the stock boot img i found in the other thread with this guide.