Hey guys. I just rooted my PH-1 with magisk v-16 after updating to the OTA oreo 8.1 beta from essential. I've tried to flash an image file of the 8.1 beta image but when I boot back up it boot into nougat and my wifi is broken. Any help would be greatly appreciated.
pschambers.89 said:
Hey guys. I just rooted my PH-1 with magisk v-16 after updating to . I've tried to flash an image file of the 8.1 beta image but when I boot back up it boot into nougat and my wifi is broken. Any help would be greatly appreciated.
Click to expand...
Click to collapse
So you flashed the boot image of oreo on nougat?.. it's probably a missmatch that is happening. You should flash the same boot image that's made for the nougat build you're on.
Arju said:
So you flashed the boot image of oreo on nougat?.. it's probably a missmatch that is happening. You should flash the same boot image that's made for the nougat build you're on.
Click to expand...
Click to collapse
Sorry, I left this out of my original post. I had updated to the OTA oreo 8.1 beta from essential before rooting. So it was an 8.1 to 8.1 flash.
pschambers.89 said:
Hey guys. I just rooted my PH-1 with magisk v-16 after updating to the OTA oreo 8.1 beta from essential. I've tried to flash an image file of the 8.1 beta image but when I boot back up it boot into nougat and my wifi is broken. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Sounds like you are flashing one slot and booting in the the other slot.
Unlock the BL and manually flash the 8.1 rom image.
It flashes both slots.
Do you still have TWRP after installing Magisk? If so, you missed the step where you were supposed to flash the stock boot image in via TWRP (thus overwriting twrp) before installing Magisk.
I haven't messed this up yet on Oreo, but last time I did it on 7.1.1, this was the issue - OS looked more or less okay, but no wifi.
Related
I have an oneplus 6 with official OSS 5.1.5 and TWRP installed. But after OTA update my phone to OSS 5.1.6, i cannot boot to TWRP anymore. Is TWRP gone after OTA update? My OEM unlocking still unlocked.
Have u not read anything in these forums, tutorials or anything?
There are like 50 threads on how to upgrade and about the new partitions for op6, it is even clear when u installed twrp too
dRakeNNNN said:
I have an oneplus 6 with official OSS 5.1.5 and TWRP installed. But after OTA update my phone to OSS 5.1.6, i cannot boot to TWRP anymore. Is TWRP gone after OTA update? My OEM unlocking still unlocked.
Click to expand...
Click to collapse
Hi, just to clarify when you install an OTA on the oneplus 6 it uses the new partitioning system which is different so to remedy the situation just try reflashing TWRP enchilada installer using fastboot.
cschmid44 said:
Hi, just to clarify when you install an OTA on the oneplus 6 it uses the new partitioning system which is different so to remedy the situation just try reflashing TWRP enchilada installer using fastboot.
Click to expand...
Click to collapse
Previously, i've installed Beta(unofficial) version of TWRP, now i want to re-install TWRP with Official version , do i need to remove or do something firstly?
To fix it just download the official TWRP for oneplus 6 from the official team win recovery project page and then you put that on your phone, and flash using your currently installed TWRP then after that make sure you also install the root package as installing the new version of TWRP will modify the new boot image, Also a good time to mention that it will install in both slots (Seamless update slots) Treble slots if you will just to be aware.
cschmid44 said:
To fix it just download the official TWRP for oneplus 6 from the official team win recovery project page and then you put that on your phone, and flash using your currently installed TWRP then after that make sure you also install the root package as installing the new version of TWRP will modify the new boot image, Also a good time to mention that it will install in both slots (Seamless update slots) Treble slots if you will just to be aware.
Click to expand...
Click to collapse
Thank you for your reply, but my problem is i cannot boot into TWRP after OTA upgrade my OSS from 5.1.5 to 5.1.6
dRakeNNNN said:
Thank you for your reply, but my problem is i cannot boot into TWRP after OTA upgrade my OSS from 5.1.5 to 5.1.6
Click to expand...
Click to collapse
Just follow one of the many upgrade guides. Skip the part about upgrading to 5.1.6 but for the rest follow the steps exactly. No need to explain all this in yet another thread imo. You'll need a pc though.
that's would be great if twrp can be flashed and stays there without wiping as well as root.
Pleasssseeeeee read before creating a new thread
dRakeNNNN said:
I have an oneplus 6 with official OSS 5.1.5 and TWRP installed. But after OTA update my phone to OSS 5.1.6, i cannot boot to TWRP anymore. Is TWRP gone after OTA update? My OEM unlocking still unlocked.
Click to expand...
Click to collapse
Wait!
Don't install 5.1.6 ROM because OP has retired it. The last version availabe on OP site is the 5.1.5.
MuttleyMB said:
Wait!
Don't install 5.1.6 ROM because OP has retired it. The last version availabe on OP site is the 5.1.5.
Click to expand...
Click to collapse
I'm using 5.1.6, so far so good. I don't have any issue on 5.1.6. ?
Sent from my OnePlus6 using XDA Labs
dRakeNNNN said:
Thank you for your reply, but my problem is i cannot boot into TWRP after OTA upgrade my OSS from 5.1.5 to 5.1.6
Click to expand...
Click to collapse
You can't boot into twrp because it's not there anymore. The OTA created a completely stock version of the OS that you're now booted on. You need to reinstall twrp and magisk according to the posted guides. This is going to be the case with all OTAs. The stock updater looks for root, and when it's there, it installs a complete OS, not an incremental update.
Can anyone upload a Magisk patched boot image for 10.0.1GM57AA? The model that I have is GM1900. When I try to patch it myself on Magisk, I get an error saying "process error"
Anyone able to help?
Heelixx said:
Anyone able to help?
Click to expand...
Click to collapse
Hi.
magisk-patched 4.14.117-perf+ with twrp: https://ufile.io/3ieksyfx
flash with fastboot flash boot 4.14.117-perf+.img
meltbanana said:
Hi.
magisk-patched 4.14.117-perf+ with twrp: https://ufile.io/3ieksyfx
flash with fastboot flash boot 4.14.117-perf+.img
Click to expand...
Click to collapse
Thanks a lot for uploading this! I managed to flash it and root my device but now the wifi isn't working. I cleared the cache with TWRP but that didn't resolve the issue. Flashing back the original boot image made the wifi work again.
Heelixx said:
Thanks a lot for uploading this! I managed to flash it and root my device but now the wifi isn't working. I cleared the cache with TWRP but that didn't resolve the issue. Flashing back the original boot image made the wifi work again.
Click to expand...
Click to collapse
ok, perhaps it depends on BA (EU) or AA (global) ROM version? however you can boot the rooted one, install a downloaded version of magisk20 via magisk manager to patch your own kernel directly.
meltbanana said:
ok, perhaps it depends on BA (EU) or AA (global) ROM version? however you can boot the rooted one, install a downloaded version of magisk20 via magisk manager to patch your own kernel directly.
Click to expand...
Click to collapse
I flashed the 4.14.117-perf+.img that you uploaded and then I booted in TWRP and flashed my original stock boot image. While still in TWRP, I flashed the zip of Magisk and then I rebooted. That got it working. So I'm rooted now. Thanks for sending me the image. I appreciate it!
@Heelixx
Can you explain to me how important a magisk boot patched is? Did you leave Pie for 10? What's the procedure?
lvints said:
@Heelixx
Can you explain to me how important a magisk boot patched is? Did you leave Pie for 10? What's the procedure?
Click to expand...
Click to collapse
I was rooted on 10.0 and then I upgraded to 10.0.1
There is a procedure for upgrading to 10.0.1 and still keeping root. I wasn't aware of this and after I got the update, I restarted my device and ended up without root access.
A Magisk patched boot image is important for getting your device rooted.
If you're asking for the procedure to root your device, then you can follow this link which explains it, https://forum.xda-developers.com/oneplus-7/how-to/guide-how-to-flash-android-10-twrp-t3964131
After recently bricking my Oneplus 6 by trying to flash the latest TWRP on the latest Android 10 OTA from Oxygen Updater, I found a post from official TWRP explaining how root with a10 will take a while to implement due to changes that Google has made to their partitions.
So I guess for anyone trying this out on their own, be warned. You will probably end up bricking your device like I did and will probably end up having a bad time.
Please correct me if i'm wrong though, peace!
Edit: can confirm fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img from the other popular post is working!
If you already have a working TWRP on OOS 9 you should be fine as long as you flash a working TWRP afterwards. Blu_spark TWRP 9.101 is compatible (please not 9.101 no earlier version will work).
Also don't use Magisk 20 only 20.1.
There is already a pre-patched version out there. You can fastboot flash it (as fastboot boot doesn't work). An easier way (without a pre-patched version) is currently being worked one as you pointed out already
just updated to a10
boot into twrp, flash new bluspark twrp
flash FULL ota a10 image
reflash twrp
reboot into twrp
boot into system
boot back to twrp
install magisk 20.1
a10, twrp and root working
Hi,
I am on 9.0.9 stable with root using magisk. Is it possible to update to android 10 without loosing data and root??
nightfury04 said:
Hi,
I am on 9.0.9 stable with root using magisk. Is it possible to update to android 10 without loosing data and root??
Click to expand...
Click to collapse
havent lost data and you can root again
Blu_spark twrp
could you please provide link for blu_spark twrp img, zip files that work with android 10?
akri1337 said:
havent lost data and you can root again
Click to expand...
Click to collapse
Did you uninstall Magisk in stable 9.0.9 before updating to andeoid 10?
nightfury04 said:
Did you uninstall Magisk in stable 9.0.9 before updating to andeoid 10?
Click to expand...
Click to collapse
nope
akri1337 said:
havent lost data and you can root again
Click to expand...
Click to collapse
akri1337 said:
nope
Click to expand...
Click to collapse
It would be of great help if you could provide link to working TWRP with android 10.
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page222
i used this one
akri1337 said:
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page222
i used this one
Click to expand...
Click to collapse
Which build did u use mate? R108 is not working with android 9, I tried flashing it using my older installed twrp.
It says unsupported android version. And in github r108 says only for android 10.
r108 is the kernel not twrp
https://github.com/engstk/android_device_oneplus_enchilada/releases/tag/v9.107
akri1337 said:
r108 is the kernel not twrp
https://github.com/engstk/android_device_oneplus_enchilada/releases/tag/v9.107
Click to expand...
Click to collapse
Thanks again mate.. I will give this one a try.
there is a problem with Magisk 20.1, after all flashes the system is booting ok with Magisk working but after I give first program root access and rebooting its stuck on bootloader and not booting to system.
nightfury04 said:
Thanks again mate.. I will give this one a try.
Click to expand...
Click to collapse
I can confirm that this is working for me. I successfully upgraded from Android 9, Oxygen OS 9.0.9 to Android 10, Oxygen OS 10. Steps that I followed :
1) Flashed new twrp from link in the above post by akri1337 using my previously installed twrp : bluspark 9.85.
2) Flashed Oxygen OS 10 full update and added to queue latest bluspark twrp which I flashed in step one as it would be overwritten by flashing the full OTA update.
3) Rebooted into recovery again to switch to active slot.
4) Flashed Magisk 20.2 to regain root.
This process successfully upgraded my Oneplus 6 without any data loss.
Please note that I disabled all magisk modules just to be safe before starting the upgrade process but didn't uninstall magisk. I was on Magisk 20.2 earlier.
Hope this helps everyone.
nightfury04 said:
I can confirm that this is working for me. I successfully upgraded from Android 9, Oxygen OS 9.0.9 to Android 10, Oxygen OS 10. Steps that I followed :
1) Flashed new twrp from link in the above post by akri1337 using my previously installed twrp : bluspark 9.85.
2) Flashed Oxygen OS 10 full update and added to queue latest bluspark twrp which I flashed in step one as it would be overwritten by flashing the full OTA update.
3) Rebooted into recovery again to switch to active slot.
4) Flashed Magisk 20.2 to regain root.
This process successfully upgraded my Oneplus 6 without any data loss.
Please note that I disabled all magisk modules just to be safe before starting the upgrade process but didn't uninstall magisk. I was on Magisk 20.2 earlier.
Hope this helps everyone.
Click to expand...
Click to collapse
Which magisk? Ver 20.1 ?
Why is it that I get an error when trying to flash the full OTA update using TWRP? Something about error 7 and not have a digest file. Is there a full OTA update file that everyone is using? I tried the signed full zip from here on XDA and the one from Oxygen Updater. I get the same error with both.
GunFishin said:
Why is it that I get an error when trying to flash the full OTA update using TWRP? Something about error 7 and not have a digest file. Is there a full OTA update file that everyone is using? I tried the signed full zip from here on XDA and the one from Oxygen Updater. I get the same error with both.
Click to expand...
Click to collapse
Had this error too and couldn't flash it with twrp, flashed successfully OTA file from oxygen -> Local upgrade
chetbiz said:
Had this error too and couldn't flash it with twrp, flashed successfully OTA file from oxygen -> Local upgrade
Click to expand...
Click to collapse
Still confused as to how everyone else can flash these zip files through TWRP and I cannot.
I'm currently Magisk rooted and have TWRP installed. Will I lose root and TWRP when updating through the local upgrade method?
GunFishin said:
Still confused as to how everyone else can flash these zip files through TWRP and I cannot.
I'm currently Magisk rooted and have TWRP installed. Will I lose root and TWRP when updating through the local upgrade method?
Click to expand...
Click to collapse
Yes, you will need to flash twrp with adb and going through the hole process of installing twrp and magisk, but for me its not worked well, after first boot to Android Q with magisk 20.1 and granting some apps root access when I rebooted the phone its not booting to system and going to bootloader, I think its related to some problem with magisk 20.1.
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 May update is 11.0.5.0. I have a patched boot with Magisk 20.4
https://yasmar.net/xda/patched_boot_11.0.5.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.5.0.img.gz
Did you update from 9.0? or from previous 10.0 ROM?
smicas said:
Did you update from 9.0? or from previous 10.0 ROM?
Click to expand...
Click to collapse
I went from Pie 10.0.20.0 to Q 11.0.4.0 to 11.0.5.0.
I wasn't offered 11.0.2.0.
a1291762 said:
I went from Pie 10.0.20.0 to Q 11.0.4.0 to 11.0.5.0.
I wasn't offered 11.0.2.0.
Click to expand...
Click to collapse
Thanks,
And from 10.0.2.0 to 11.0.4.0 - did you also update the same way, or did you clean flash from fastboot?
smicas said:
And from 10.0.2.0 to 11.0.4.0 - did you also update the same way, or did you clean flash from fastboot?
Click to expand...
Click to collapse
I've been using the same process for every OTA since 10.0.4.0.
Only a few updates caused issues.
10.0.9.0 needed a newer TWRP.
Magisk 20 broke TWRP.
When I did the android 10 upgrade I had an issue with some Magisk modules that I had not upgraded. It would have been fine if I'd upgraded them first. I disabled them to boot and then installed the upgraded modules.
Does anyone have the boot img from version 11.0.10.0?
abracadabra02099 said:
Does anyone have the boot img from version 11.0.10.0?
Click to expand...
Click to collapse
There is no such version for Mi A2 Lite.
11.0.5.0 is the newest release (Android 10 with May security patches).
Hi @a1291762,
I'd like to know if
. it is possible to downgrade from 11.0.5 to latest Android 9
. it is possible to use a full working Gcam on 11.0.5 and how to install it.
Thank you!
I'm currently on v. 10.0.18 (I stopped the latest update for Pie) and I have a CSOT screen.
DekiS3 said:
Hi @a1291762,
I'd like to know if
. it is possible to downgrade from 11.0.5 to latest Android 9
. it is possible to use a full working Gcam on 11.0.5 and how to install it.
Thank you!
I'm currently on v. 10.0.18 (I stopped the latest update for Pie) and I have a CSOT screen.
Click to expand...
Click to collapse
It was only the first Android 10 (11.0.2.0) that had issues with screens. The 2 followups (11.0.4.0 and 11.0.5.0) work on all phones.
In theory, it is possible to downgrade back to 10.0.18.0 using a fastboot image.
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
To get to 10.0.20.0 you'll need to get the OTA zip and install that. I'm not sure how to do that, but this process seems like it should work: https://forum.xda-developers.com/mi-a2-lite/how-to/how-to-manual-update-v11-0-4-0-users-t4082815
It might be worth checking if people have done the downgrade successfully. For example, the Pie-Oreo downgrade caused modem issues.
There's heaps of threads where people discuss gcams, but I do not know what the state is because I use the stock camera app.
DekiS3 said:
...
Click to expand...
Click to collapse
Apparently there was a 10.0.20.0 fastboot, but it's not on the fastboot thread
I don't know where I got this URL from but 10.0.20.0 is http://bigota.d.miui.com/V10.0.20.0...0.PDLMIXM_20200327.0000.00_9.0_2baf524aaf.tgz
a1291762 said:
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 May update is 11.0.5.0. I have a patched boot with Magisk 20.4
https://yasmar.net/xda/patched_boot_11.0.5.0_204.img.gz
And the vanilla boot
https://yasmar.net/xda/vanilla_boot_11.0.5.0.img.gz
Click to expand...
Click to collapse
First of all, i never had magisk on android 8-9 before,then i want to install it on android 10 , i'm quiet understand with the fastboot step, but i don't know if its ok to do it right on a10, i mean if i just boot with your android 10 patched_boot then install magisk, did i just rooted my phone ?
I just wanted to install GCam btw
Thank you.
So as OnePlus said we released stable OOS12 for OnePlus 7, I got a notification on Oxygen OS Updater app about the update. I was on stable channel with 11.0.3.1 and after the download was available in the app I downloaded the full build (as I was rooted and unlocked) and updated it with local upgrade from system settings. After reboot I was getting option to wipe data saying data error and rebooting to recovery everytime.
After some research it turns out that the update is for Open Beta users. I flashed this boot.img and somehow managed to switch to slot A and it booted back to OOS11. Now my slot B is not bootable with OOS12.
Is there any way I can rollback to OOS11 on slot B without any data loss?
Or is there a way I can boot into OOS12 on slot B without any data loss?
Sturdy_99 said:
So as OnePlus said we released stable OOS12 for OnePlus 7, I got a notification on Oxygen OS Updater app about the update. I was on stable channel with 11.0.3.1 and after the download was available in the app I downloaded the full build (as I was rooted and unlocked) and updated it with local upgrade from system settings. After reboot I was getting option to wipe data saying data error and rebooting to recovery everytime.
After some research it turns out that the update is for Open Beta users. I flashed this boot.img and somehow managed to switch to slot A and it booted back to OOS11. Now my slot B is not bootable with OOS12.
Is there any way I can rollback to OOS11 on slot B without any data loss?
Or is there a way I can boot into OOS12 on slot B without any data loss?
Click to expand...
Click to collapse
Hi. I am in the same position. Can I get a link to the boot.img file that you used?
The link is dead
Sturdy_99 said:
So as OnePlus said we released stable OOS12 for OnePlus 7, I got a notification on Oxygen OS Updater app about the update. I was on stable channel with 11.0.3.1 and after the download was available in the app I downloaded the full build (as I was rooted and unlocked) and updated it with local upgrade from system settings. After reboot I was getting option to wipe data saying data error and rebooting to recovery everytime.
After some research it turns out that the update is for Open Beta users. I flashed this boot.img and somehow managed to switch to slot A and it booted back to OOS11. Now my slot B is not bootable with OOS12.
Is there any way I can rollback to OOS11 on slot B without any data loss?
Or is there a way I can boot into OOS12 on slot B without any data loss?
Click to expand...
Click to collapse
Hi. So I downloaded the OS12 OTA and used a payload dumper (instructions and download here, https://www.getdroidtips.com/extract-payload-bin/) to extract the boot image and then I used fastboot to flash the boot image. It booted me into OS12 and there are no issues so far.
I've attached the boot image file that I extracted. Hope this helps
Side note, it seems like I got the issue because while on OSS11, I updated to OS12 but before I rebooted, I used Magisk to patch the boot image and then rebooted.
Heelixx said:
Hi. So I downloaded the OS12 OTA and used a payload dumper (instructions and download here, https://www.getdroidtips.com/extract-payload-bin/) to extract the boot image and then I used fastboot to flash the boot image. It booted me into OS12 and there are no issues so far.
I've attached the boot image file that I extracted. Hope this helps
Side note, it seems like I got the issue because while on OSS11, I updated to OS12 but before I rebooted, I used Magisk to patch the boot image and then rebooted.
Click to expand...
Click to collapse
Did u extract the boot.img from stable Open Beta release? Can you provide the links to oos12 ota and boot.img?
Sturdy_99 said:
Did u extract the boot.img from stable Open Beta release? Can you provide the links to oos12 ota and boot.img?
Click to expand...
Click to collapse
This is where you can find the links to the OOS12 OTA, https://www.xda-developers.com/oneplus-7-7t-pro-android-12-oxygenos-12-stable/
For some reason, I thought I uploaded the boot.img file in my previous reply but it seems not. Here's the link to download the one I extracted, https://gofile.io/d/BoqcM0
Heelixx said:
This is where you can find the links to the OOS12 OTA, https://www.xda-developers.com/oneplus-7-7t-pro-android-12-oxygenos-12-stable/
For some reason, I thought I uploaded the boot.img file in my previous reply but it seems not. Here's the link to download the one I extracted, https://gofile.io/d/BoqcM0
Click to expand...
Click to collapse
Great thats open beta, looks like many have been impacted with this. Thanks for the boot .img
Where you on stable release or open beta before upgrading?
Sturdy_99 said:
Great thats open beta, looks like many have been impacted with this. Thanks for the boot .img
Where you on stable release or open beta before upgrading?
Click to expand...
Click to collapse
I was on stable release before upgrading.
Strange that it's open beta when the headline says Stable OxygenOS 12. Oneplus is confusing people
Heelixx said:
I was on stable release before upgrading.
Strange that it's open beta when the headline says Stable OxygenOS 12. Oneplus is confusing people
Click to expand...
Click to collapse
Great, Thanks, ill give it a try.
Heelixx said:
Hi. So I downloaded the OS12 OTA and used a payload dumper (instructions and download here, https://www.getdroidtips.com/extract-payload-bin/) to extract the boot image and then I used fastboot to flash the boot image. It booted me into OS12 and there are no issues so far.
I've attached the boot image file that I extracted. Hope this helps
Side note, it seems like I got the issue because while on OSS11, I updated to OS12 but before I rebooted, I used Magisk to patch the boot image and then rebooted.
Click to expand...
Click to collapse
Does that mean, it would boot fine, if you do not install magisk before rebooting? In that case, you reinstall majgisk?
mzahs said:
Does that mean, it would boot fine, if you do not install magisk before rebooting? In that case, you reinstall majgisk?
Click to expand...
Click to collapse
So it would boot fine if I don't install magisk before rebooting.
However, I did flash the update again recently and then flashed the magisk patched boot image but I got stuck in a bootloop again. I don't know if I'm doing something wrong. So I'm without root on my phone at the moment