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
Related
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.
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
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
matthi383 said:
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
Click to expand...
Click to collapse
Hello,
Did you see this thread right below yours?
Android 11 OB4
Just installed OB4, anybody got a boot.img file or magisk patched boot image file? Also any news on TWRP for Android 11? Thanks in anticipation OK I was just lazy hoping somebody Elese did the work. Ended up using my OB2 patched boot image file...
forum.xda-developers.com
Magisk canary can also cause a lot of issues. I'm using 22.0.
Hey thank you! I already saw this and tried it out before to get TWRP working as in the Oxygen OS 11 Beta but this TWRP version does not work with the official OOS11 for the Oneplus 7. It's strange that on Open Beta it works and now its not working.
Watching this thread because I'm stuck too. I either need locked bootloader or unlocked with Magisk
Does anyone already has a solution to this one?
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
WareDat said:
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
Click to expand...
Click to collapse
I wish someone would upload the fastboot ROM
Thank you man it worked ! i hope others are seeing also your intructions and files so they can use them and have root back again
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Than
Click to expand...
Click to collapse
¿GotJazz? said:
Hi - I installed OOS 11.05.1.GM21AA on my OP7P today, and patched my boot.img file with Magisk 24.1.
After going into Fastboot Mode and doing a fastboot flash boot magisk_patched_boot.img, my OP7P rebooted OK, but my OP7P isn't rooted.
Is there something new that I am missing?
Also, is there a way to get both TWRP 3.6.x and Magisk to be available in the same patched boot image? It looks like TWRP completely overwrites the Magisk modded boot.img file, and then is stuck in a Recovery bootloop.
Thanks,
¿GJ?
Click to expand...
Click to collapse
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
hammered58 said:
I had the same issue, I had to downgrade to 11.04, grab a new 11.05 ota from oxygen updater app, extract boot from that and go from there
Click to expand...
Click to collapse
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
¿GotJazz? said:
Is this the Oxygen Updater App you are referring to, or is it the incremental OTA that I would get from a "OnePlus system update" on a now unrooted and unTWRP'd phone?
Also ... Will I lose any data if I downgrade to 11.04? I've never downgraded before, so do I just install the stock 11.04 image via TWRP like I did the 11.05 image?
Lastly ... I'm assuming this will just get me root, but not including TWRP?
Click to expand...
Click to collapse
1. Yes that is the app Iam talking about.
2. Will you lose data? I always do a format (after the down grade) so I lost data but I never tried it with out formating, it might work, you could try it and see what happens .If it acts strange then it will need a format.
3. Yes you install 11.04 via twrp
4. Yes you will get root but if you want twrp you will have to reinstall
Once you down grade install the oxygen updater, let it download the update , don't let it install it, you can then grab the update from your root directory as it doesn't hide it, then your good to go, you can extract the boot.img by using payload dumper, then take the boot.img and patch that with the magisk app . ( Just install the magisk app on your downgraded 11.04 you don't need root to run the app ) ,,Then after your thru upgrading to 11.05 and after setup just reboot to bootloader and run the magisk patched boot.img, ( fastboot flash boot boot.img) reboot and wait a minute for the magisk app to appear ,it will want to install and do a reboot . Then you can install twrp if you want.
This is how I did it and it worked, you may find a simpler way once you start doing it ,, hth
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
¿GotJazz? said:
I'm reluctant to go and do a total wipe (which I have been reading will be required to downgrade).
I'm wondering if the problem I'm facing is that my OP7P needed to be rooted for Magisk 24.1 to be able to successfully patch the latest OP7P build? My OP7P isn't rooted right now although I have v24.1 installed.
I accidentally had installed the latest 11.0.5 OTA before I had a chance to attempt re-rooting.
Click to expand...
Click to collapse
Right now I have 11.05 installed and Iam rooted, tomorrow I will unroot and downgrade to 11.04 without wiping and let you know what happens iam curious myself
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
¿GotJazz? said:
I'm rooted now. I did have to wipe my OP7P to get root (due solely to my own heavy-handed approach to getting root again).
I posted in another thread, and I think that the thing that might have made a difference for me wasn't that I wiped, but possibly that I removed encryption before installing the Magisk-patched boot image.
Click to expand...
Click to collapse
I guess that's possible , I never thought of that, the only way to know is to do a fresh install only this time setup encryption then try to install magisk . But for now your rooted,, until the bug hits you or me to try another rom then we can start the whole thing over again,,
Hi Everyone, there seems to be a lot of bits and pieces in regards to updating OOS 12 and Root so I thought I put together this guide on the way I do it while retaining Root. Unless something changes, this method should work for all future OOS 12 OTA updates.
Please read through all of the steps below before attempting. I will take no responsibility if something goes wrong, this works for me on my OnePlus 9 LE2115 and it should work for other OnePlus 9/Pro models.
1. Install Oxygen Updater app from the Play Store
2. Download the Full OTA.
3. Download and install the OP Local Update app ( apk).
4. Use the OP Local Update app to flash the Full OTA (you will lose root and custom recovery).
Optional - Retaining Root
DO NOT REBOOT if you want to keep Root
5. Open Magisk and in the Magisk section, tap 'Install'.
6. Select ' Install to Inactive Slot (After OTA)'.
7. Tap ' LET'S GO', let it run and then reboot.
After the system boots back up, check to make sure you have retained Root. You will not lose any data doing it this way.
What do you do if you've rebooted, are on the new OS but don't have root? When I go back to Magisk it's asking for an IMG file... I saved the last used kernel before upgrading (11.2.10.10)
I tried installing that app, which looks like its an udpate for a system app (system updater) which is prob why it fails.
I was previously under the impression that this app was to replace the missing system updater in OOS12.
Nick James said:
What do you do if you've rebooted, are on the new OS but don't have root? When I go back to Magisk it's asking for an IMG file... I saved the last used kernel before upgrading (11.2.10.10)
Click to expand...
Click to collapse
This guide is for updating OOS 12, i have not tested it from OOS 11 to 12. It looks like you just need to flash the patched boot.img again.
Also, just to make sure, you didn't reboot the phone after flashing the Full OTA? After flashing Full OTA, you need to go straight into Magisk as per instruction.
gorilla p said:
I tried installing that app, which looks like its an udpate for a system app (system updater) which is prob why it fails.
I was previously under the impression that this app was to replace the missing system updater in OOS12.
Click to expand...
Click to collapse
Yeah, it does not replace any app, it installs a new one. The Local Updater app is only for OOS 12. In OOS 11, it's integrated into system Updater but for some reason in OOS 12, OP removed it and created a seperate app for Local OTA flashing.
Z-Blade said:
Yeah, it does not replace any app, it installs a new one. The Local Updater app is only for OOS 12. In OOS 11, it's integrated into system Updater but for some reason in OOS 12, OP removed it and created a seperate app for Local OTA flashing.
Click to expand...
Click to collapse
I rebooted per old instructions and that is what messed it up.
Used the Oxygen Updater to re-download the OTA.
Extracted the boot.img with payload dumper.
Patched boot.img
Reflashed
And we are good to go.
Nick James said:
I rebooted per old instructions and that is what messed it up.
Used the Oxygen Updater to re-download the OTA.
Extracted the boot.img with payload dumper.
Patched boot.img
Reflashed
And we are good to go.
Click to expand...
Click to collapse
Ah, right. From the other thread. Good to hear it's all sorted out.
If you are looking for the boot.img for a OP9 (not pro) LE2115_11_C.47... here you go:
Meet Google Drive – One place for all your files
Google Drive is a free way to keep your files backed up and easy to reach from any phone, tablet, or computer. Start with 15GB of Google storage – free.
drive.google.com
This is valuable if you get stuck in a position like I did on C.47 without root. Patch this file with Magisk and follow the instructions as you normally would when flashing for root:
Installation
The Magic Mask for Android
topjohnwu.github.io
Nick James said:
I rebooted per old instructions and that is what messed it up.
Used the Oxygen Updater to re-download the OTA.
Extracted the boot.img with payload dumper.
Patched boot.img
Reflashed
And we are good to go.
Click to expand...
Click to collapse
So, how did you get from e.13 to c.47 with root?
1. Download c.47
2. Install it via updater - no resart
3. install the patched_boot.img in inactiv slot
4. restart
Correct?
AxelM said:
So, how did you get from e.13 to c.47 with root?
1. Download c.47
2. Install it via updater - no resart
3. install the patched_boot.img in inactiv slot
4. restart
Correct?
Click to expand...
Click to collapse
I uninstalled Magisk (restored images).
Rebooted (I shouldn't have done this)
Updated via OTA; rebooted.
Confirmed I was on the new version; indeed I was... completely new UI... did not lose any data or apps
Used the update app to redownload the OTA, copied it to my computer, used payload dumper to get the boot.img. Moved that back to my phone, patched with magisk and reflashed and voila.
I'm not sure on the exacts in terms of versions that I was on before but I did back up the kernel prior to all this (force of habit) and it was 11.2.10.10.
Thank you, i will try
1. I will just restore the normal boot.img
2. Update via OnePlus Update app from device
3. reboot
4. install the patched_boot.img in the inactiv slot
5. restart
Done!
So to be clear, we can now upgrade like we used to, by downloading full image From Oxygen Updater, using system update complete the upgrade, then go to magisk and install to inactive slot and reboot?
I tried this with the earlier 12 release and it went poor.
Luckily, I realized before trying this, is this only for 12 to 12 udpates and not 11 to 12? If the former, it may be best to clarify.
I am not sure. But like I understood you have to unroot before...
@Nick James am I right?
AxelM said:
I am not sure. But like I understood you have to unroot before...
@Nick James am I right?
Click to expand...
Click to collapse
I dont think so. It says if you wanna keep root, follow #5, 6, 7
AxelM said:
I am not sure. But like I understood you have to unroot before...
@Nick James am I right?
Click to expand...
Click to collapse
Honestly this OS sucks. I wouldn't waste your time. I'm going to factory reset tomorrow. It's that bad.
The steps I provided is only OOS 12 to OOS 12. I have not tried these steps from OOS 11 to OOS 12. My assumptions is it should still work since you are flashing the Full OTA, it pretty much overrides everything including boot.img. This is why you shouldn't reboot after flashing the OTA if you want to keep root.
However, this is just an assumption, if someone who is currently on OOS 11 can test it out and report here, that would be great.
gorilla p said:
I dont think so. It says if you wanna keep root, follow #5, 6, 7
Click to expand...
Click to collapse
You are right for OS12 but not OS11. Therefore I assume you have to do my mentioned steps, but like @Z-Blade wrote, anyone has tested here yet...
Hello I tried it today. Like this:
1. I will just restore the normal boot.img
2. Update via OnePlus Update app from device
3. install the patched_boot.img in the inactiv slot
4. restart
Everything seems normal, but I am ony able to connect to the internet when in wlan...
I went from OOS 11 to 12... I wouldn't say the upgrade went smooth thus why I have to reinstall the OS to see if that clear things up. This OS is still really buggy from what I can see but it could be due to not clean flashing. Just beware is all I'm sayin'
So, my internet is back to live...after some reboots it works well