Related
The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Are the attached zip files for the wifi model only?
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Jeltel said:
When a new OTA appears I can just apply it and it will work? Do I keep root or do I have to reroot it again?
Click to expand...
Click to collapse
You can revert to stock boot and stock recovery to apply OTA
corkiejp said:
Are the attached zip files for the wifi model only?
Click to expand...
Click to collapse
Yes, I can make a LTE compatible version though.
sejmand said:
I have this Kernel:
3.10.40-g909db78
[email protected] #1
Fri Aug 28 21:16:30 UTC 2015
Is this a stock one?
And with method shall I use to get rooted MRA58N?
Click to expand...
Click to collapse
Yes, and yes
topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Yes, I can make a LTE compatible version though.
Yes, and yes
Click to expand...
Click to collapse
A LTE compatible version would be great!!!
topjohnwu said:
You can revert to stock boot and stock recovery to apply OTA
Click to expand...
Click to collapse
So that's a no
I flashed factory image MRA58N (system gets encrypted, because it wasn't under MRA58K)
then twrp
then systemless-root (boot.img)
then superuser 2.56.....
EVERYTHING WORKS FINE:
encrypted with root!
how to flash boot.img (command for flashing)
topjohnwu said:
The hot new security update is live, and you maybe want some root love without flashing custom kernel.
(Stock Image here : https://developers.google.com/android/nexus/images#volantis)
Handy modified root compatible boot image for the latest stock image MRA58N. Pure stock kernel modified from the stock images.
You have two choices:
The traditional root in system, which breaks OTA functionality.
(It's more stable now)
New "systemless" approach, which means the root stuffs are only in DATA and BOOT, the system will stay intact and it will accept OTAs.
(Note that this method is still in beta stage according to CF)
Instructions:
System:
Unzip system-root.zip, flash the boot.img through fastboot
Flash SuperSU 2.52
Systemless:
Be sure you haven't used any other root method(like the one above), if you've rooted with other methods, please re-flash your system back to pure stock
Unzip systemless-root.zip, flash the boot.img through fastboot
Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
how to flash boot.img for system less (partition ?)
Lightnyboy said:
how to flash boot.img for system less (partition ?)
Click to expand...
Click to collapse
Unzip systemless-root.zip which will give you a "boot.img" file.
Then while in fastboot
"fastboot flash boot boot.img"
Anyone have the boot files for LTE yet?
Nice. Could you add the link to CF original post in systemless root.
thebrainkafka said:
Nice. Could you add the link to CF original post in systemless root.
Click to expand...
Click to collapse
topjohnwu said:
[*]Download SuperSU-v2.56-20151030013730.zip in this thread, and flash it through TWRP
[*]Important!! Please choose "Do not install SuperSU" when reboot in TWRP if appears.
Click to expand...
Click to collapse
Already linked? Click on "this thread" above!
Updated for LTE... Sorry for the late update.
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
topjohnwu said:
Updated for LTE... Sorry for the late update.
Click to expand...
Click to collapse
Thanks for the modified boot images for LTE, I linked back here from my thread in Q&A forum.
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
madbat99 said:
Also looks like rovo89 just put up xposed for marshmallow in his xposed for lollipop thread. Yes!
xposed marshmallow
Click to expand...
Click to collapse
I haven't run N version yet as my N9 is finally working without lags/reboots. But, the lure of the close all recent apps button (and very successful experience with xposed/gravity box on N5 after a year) in GB was too great. It works beautifully!
This may seem off-topic, but since root is required, maybe readers can allow exception.
Sent from my Nexus 9 using Tapatalk
chesterchen said:
have problems getting it to work...
am on MRA58N stock.
My exact steps.
adb reboot bootloader
Device reboots to bootloader.
fastboot flash boot boot.img (extracted from volantisg-mra58n-boot-systemless.zip)
fastboot boot twrp.img (extracted from https://dl.twrp.me/flounder/twrp-2.8.7.1-flounder.img)
From here, I manage to get into TWRP but they are asking for a PIN. I had to cancel and mounted an external USB storage and manage to flash SuperSU-v2.56-20151030013730.zip successfully. Rebooting after and not installing the the SuperSU that TWRP prompts.
After rebooting, I still don't have root. What did I do wrong?
Click to expand...
Click to collapse
You don't need to extract twrp.img, you should flash the full image "twrp-2.8.7.1-flounder.img".
That version should not ask for PIN anymore.
Note: system-less is still experimental
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
maximumentropy said:
If I want to switch from the systemless root to regular system modified root, are there specific cleanup actions to take?
Thanks!
Click to expand...
Click to collapse
Reflash the stock image then you're good
This is only for Honor 8 Pro (DUK-L09)
DISCLAIMERYOUR WARRANTY IS NOW VOID. IN NO WAY AM I RESPONSIBLE FOR THE EFFECTS YOU INFLICT ON YOUR MOBILE DEVICE BY FOLLOWING THE BELOW PROCEDURE. IMPROPER USAGE OF THE METHOD MIGHT END UP BRICKING YOUR DEVICE AND RENDERING IT UNUSABLE.
PLEASE BACKUP ALL YOUR DATA BEFORE PROCEEDING.
Purpose of this thread is to provide a working rooting method for the Honor 8 Pro. Flashing Phhsuperuser doesn't grant SYSTEM WIDE root permission.
Functions like granting -rw permissions to apps demanding them for accessing /system partition was disabled, TWRP backup wouldn't work.
With this method, you will be able to operate the phone will proper root privileges.
INSTALLATION INSTRUCTIONS
1. UNLOCK BOOTLOADER
Assuming you have a Huawei ID, use THIS PAGE to get your Unlock code.
Once you have that, enable USB debugging on your device from Developer options menu.
Make sure "Allow OEM unlock" option is selected.
Use the following set of commands via ADB/Fastboot:
adb device (this should recognize your device)
adb reboot bootloader (this will boot your phone into fastboot mode)
fastboot oem unlock *unlock key* (the part between * is where the unlock key goes)
The device will restart and then perform factory reset itself.
2. INSTALL CUSTOM RECOVERY IMAGE (Source : TWRP Thread by OldDroid)
Download TWRP recovery image from HERE
Rename the downloaded file to recovery.img
Copy it to the ADB folder that you are using.
Use the command "adb reboot bootloader" like in Step 1 to boot into Fastboot mode.
Flash the recovery using "fastboot flash recovery recovery.img" command (without quotes)
You have now flashed a custom recovery onto your phone.
3. ROOTING
Download Magisk installer zip file from THIS LINK . I had personally used v 13.3 .
Copy it to your SD card(I would suggest you to use a external card).
Switch off your device.
Boot into recovery mode by pressing Volume Up and Power Button together.
Once in, swipe to allow modifications.
Go to Wipe - Format Data
Then Go to Reboot- Recovery
You should be back into the recovery mode. Go to Install menu - Select storage - Install the Magisk zip that you downloaded.
Once it is flashed, you can Reboot to system.
Note: To confirm system wide root access, you can reboot to recovery and try to take a Nandroid backup. It should now be possible.
If anyone happens to run into a bootloop or soft bricks the device, THIS THREAD by @aKp1 will come in handy.
Thanks to @OldDroid for his TWRP thread.
I am rooted using phhs superuser, do I need to unroot first? If yes, I can't find how to unroot the Indian variant.
Going back to Stock = Unrooting
devilrulz4ever said:
I am rooted using phhs superuser, do I need to unroot first? If yes, I can't find how to unroot the Indian variant.
Click to expand...
Click to collapse
Yes you will have to unroot first. Since phhsuperuser doesn't have a option to UNROOT, you will have to flash stock ROM.
To do that, download the following: HUAWEI UPDATE EXTRACTOR and STOCK ROM .
Follow below steps:
Extract the Stock ROM
Use the Update extractor and select "Update.app" file. That should give you a list of files. Select "recovery.img" and "recovery2.img" image files and extract them.
Copy them to ADB folder. Boot your phone into fastboot mode, flash the two recovery files you copied.
Next, Copy the "dload" folder to your SD card(preferably external SD). Switch your phone off. Press Vol Up,Vol Down and Power button together. The ROM should start flashing. That brings you back to stock firmware. If you want to re-root, follow the instructions in this thread.
amulbaby said:
Yes you will have to unroot first. Since phhsuperuser doesn't have a option to UNROOT, you will have to flash stock ROM.
To do that, download the following: HUAWEI UPDATE EXTRACTOR and STOCK ROM .
Follow below steps:
Extract the Stock ROM
Use the Update extractor and select "Update.app" file. That should give you a list of files. Select "recovery.img" and "recovery2.img" image files and extract them.
Copy them to ADB folder. Boot your phone into fastboot mode, flash the two recovery files you copied.
Next, Copy the "dload" folder to your SD card(preferably external SD). Switch your phone off. Press Vol Up,Vol Down and Power button together. The ROM should start flashing. That brings you back to stock firmware. If you want to re-root, follow the instructions in this thread.
Click to expand...
Click to collapse
Thanks for your reply. I'll try this out.
The build number of the Stock ROM in Gdrive is "Duke-L09I_C675B130" while the one on the phone is "DUK-L09C675B130" are they both the same variant?
devilrulz4ever said:
Thanks for your reply. I'll try this out.
The build number of the Stock ROM in Gdrive is "Duke-L09I_C675B130" while the one on the phone is "DUK-L09C675B130" are they both the same variant?
Click to expand...
Click to collapse
Don't worry . It's the same. File name doesn't matter.
amulbaby said:
Don't worry . It's the same. File name doesn't matter.
Click to expand...
Click to collapse
Oh wait. Isn't the format data option remove some necessary apps like keyboard and others? Because that's the case before in my Honor 8. After you remove encryption, you need to reflash the region zip so that some important files will be retained.
Sent from my Honor 8 Pro using XDA Labs
adriansticoid said:
Oh wait. Isn't the format data option remove some necessary apps like keyboard and others? Because that's the case before in my Honor 8. After you remove encryption, you need to reflash the region zip so that some important files will be retained.
Click to expand...
Click to collapse
The zip I shared is for the Indian variant . As long as someone is having C675(Indian variant) installed, it shouldn't cause issues. However if you come from a different region(C432) , you will have to use region zip. I guess I mentioned that in the TWRP thread, current last post.
But formatting data can't be avoided as unlocking bootloader will wipe it in first place . More over stock ROM encrypts data on first boot, so you will have to format data(decrypt it) and proceed with rooting.
amulbaby said:
The zip I shared is for the Indian variant . As long as someone is having C675(Indian variant) installed, it shouldn't cause issues. However if you come from a different region(C432) , you will have to use region zip. I guess I mentioned that in the TWRP thread, current last post.
But formatting data can't be avoided as unlocking bootloader will wipe it in first place . More over stock ROM encrypts data on first boot, so you will have to format data(decrypt it) and proceed with rooting.
Click to expand...
Click to collapse
Wut. So you mean to tell me, that after I decrypt, I should just go ahead and flash Magisk, then reboot? No more additional zip to flash? Sorry man this is getting out of my head.
Sent from my Honor 8 Pro using XDA Labs
Tht's nice bro...u said u wll be cming up wd ths kind of thread..and u r there...thnks....really needed support for the indian variant...
i will dfntly try this....
and one more thing...currently i am facing issues with adaway..busybox...with phh superuser..since no rw permissions...can magisk solve the problem
adriansticoid said:
Wut. So you mean to tell me, that after I decrypt, I should just go ahead and flash Magisk, then reboot? No more additional zip to flash? Sorry man this is getting out of my head.
Click to expand...
Click to collapse
That's correct. As simple as that. Decrypt , flash Magisk and you are done. I don't know why many didn't try this all this while.
rexinriot said:
Tht's nice bro...u said u wll be cming up wd ths kind of thread..and u r there...thnks....really needed support for the indian variant...
i will dfntly try this....
and one more thing...currently i am facing issues with adaway..busybox...with phh superuser..since no rw permissions...can magisk solve the problem
Click to expand...
Click to collapse
Yes magisk will solve your problem. Phhsuperuser doesn't allow you to grant permissions to any app that tries fiddle with system partition. If you are already rooted , go back to stock and follow the steps outlined.
amulbaby said:
That's correct. As simple as that. Decrypt , flash Magisk and you are done. I don't know why many didn't try this all this while.
Click to expand...
Click to collapse
Dafuuuuq. I waa scared all along because of that. I didn't know things changed in Honor 8 Pro. Thanks a lot.
Sent from my Honor 8 Pro using XDA Labs
amulbaby said:
That's correct. As simple as that. Decrypt , flash Magisk and you are done. I don't know why many didn't try this all this while.
Click to expand...
Click to collapse
How to decrypt? I successfully rooted with magisk v14 but adaway is disabled after reboot, same case as phhs superuser.
devilrulz4ever said:
How to decrypt? I successfully rooted with magisk v14 but adaway is disabled after reboot, same case as phhs superuser.
Click to expand...
Click to collapse
You flashed Magisk while encrypted?
Sent from my Honor 8 Pro using XDA Labs
devilrulz4ever said:
How to decrypt? I successfully rooted with magisk v14 but adaway is disabled after reboot, same case as phhs superuser.
Click to expand...
Click to collapse
You need to wipe data (which will decrypt) and then flash Magisk.
Read point no.3 of the installation instructions.
adriansticoid said:
You flashed Magisk while encrypted?
Click to expand...
Click to collapse
Have you managed to root your device using Magisk yet?
amulbaby said:
Have you managed to root your device using Magisk yet?
Click to expand...
Click to collapse
Not yet. Maybe I'll try tomorrow.
Sent from my Honor 8 Pro using XDA Labs
amulbaby said:
You need to wipe data (which will decrypt) and then flash Magisk.
Read point no.3 of the installation instructions.
Click to expand...
Click to collapse
I wiped data, flashed Magisk v13.3 and then v14 after a successful boot (without wipe).
Hello...now i am going back to stock rom b130..from phh superuser.... i am going to follow your instructions of rooting using magisk after this...
But before that i hv one question....should i upgrade to b140 and then follow op..or should i remain in b130 rom itself and start from there..
rexinriot said:
Hello...now i am going back to stock rom b130..from phh superuser.... i am going to follow your instructions of rooting using magisk after this...
But before that i hv one question....should i upgrade to b140 and then follow op..or should i remain in b130 rom itself and start from there..
Click to expand...
Click to collapse
Stay with 130. Surprisingly, rooting by this method still allows OTA to come in.
Hi guys, I had read many posts about rooting essential phone. But those articles aren't mention if it is suitable for android Pie version. Is there anyone knows how to root my essential phone with Pie 9.0 ??
See this thread.
prabs99 said:
See this thread.
Click to expand...
Click to collapse
Thanks for your reply. I had read this thread. But in step 4. Once you're in TWRP, install the stock boot image and then the Magisk zip.
I wonder which boot image I should install, cause both NMJ32F & NMJ20D are not same as android P build number which is "PPR1.1806.10.091".
I will appreciate for your help.:laugh:
Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
eric672913 said:
Thanks for your reply. I had read this thread. But in step 4. Once you're in TWRP, install the stock boot image and then the Magisk zip.
I wonder which boot image I should install, cause both NMJ32F & NMJ20D are not same as android P build number which is "PPR1.1806.10.091".
I will appreciate for your help.:laugh:
Click to expand...
Click to collapse
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
Try this for just the boot image.
prabs99 said:
Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
Click to expand...
Click to collapse
prabs99 said:
Download the BTS (Back to Stock) file from this thread. Extract the stockboot image from the zip file. Now you flash that file from TWRP.
---------- Post added at 09:42 PM ---------- Previous post was at 09:38 PM ----------
Try this for just the boot image.
Click to expand...
Click to collapse
Got it , I will try this. Thanks so much:laugh:
eric672913 said:
Got it , I will try this. Thanks so much[emoji23]
Click to expand...
Click to collapse
Try but fail and get boot loop [emoji27] . Reboot to bootloader and flash twrp, then get into TWRP recovery , flash Magisk then boot img. Anything wrong?
Sent from my [device_name] using XDA-Developers Legacy app
eric672913 said:
Try but fail and get boot loop [emoji27] . Reboot to bootloader and flash twrp, then get into TWRP recovery , flash Magisk then boot img. Anything wrong?
Click to expand...
Click to collapse
Your doing the order wrong.
When you get into TWRP, flash the boot.img that matches the current build you are on, then flash the magisk zip, then reboot.
NaterTots said:
Your doing the order wrong.
When you get into TWRP, flash the boot.img that matches the current build you are on, then flash the magisk zip, then reboot.
Click to expand...
Click to collapse
I just got a new unrooted phone and took the Pie OTA. Just to be sure I understand you, in my case, I already have the correct boot.img and can go ahead and flash TWRP, then Magisk just like on old phones, right?
jwinstonsf said:
I just got a new unrooted phone and took the Pie OTA. Just to be sure I understand you, in my case, I already have the correct boot.img and can go ahead and flash TWRP, then Magisk just like on old phones, right?
Click to expand...
Click to collapse
That's not what I wrote
First go into settings and make sure you have the build that ends with 091.
Then from either the BTS zip you downloaded, or from the Root guide thread, make sure you have the boot.img that is tagged 091. (Personally I've been using the boot.img's that are uploaded in the OP of the Guide to root thread)
Then, go through the fastboot process to install TWRP,
boot into TWRP,
then install the boot.img,
then flash the magisk zip.
Reboot profit.
You have to flash the boot.img for the current build your running Everytime you want to flash something through TWRP.
NaterTots said:
That's not what I wrote
First go into settings and make sure you have the build that ends with 091.
Then from either the BTS zip you downloaded, or from the Root guide thread, make sure you have the boot.img that is tagged 091. (Personally I've been using the boot.img's that are uploaded in the OP of the Guide to root thread)
Then, go through the fastboot process to install TWRP,
boot into TWRP,
then install the boot.img,
then flash the magisk zip.
Reboot profit.
You have to flash the boot.img for the current build your running Everytime you want to flash something through TWRP.
Click to expand...
Click to collapse
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Sent from my [device_name] using XDA-Developers Legacy app
eric672913 said:
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Click to expand...
Click to collapse
Boot.img
eric672913 said:
I am already in 091. When flash image "boot.img" via TWRP, there are two check options : boot partion & system partion, which one should I check? Many thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Boot image should go to the boot partition.
Click on link, Download essentials zip
Reboot to bootloader
Flash twp img
Boot to recovery
Once in twrp, flash pie img first "boot partition"
Then magisk zip and well-being If you want app timer/dashboard
Reboot device
(When rebooting, press "do not install" twrp as system app)
Contains latest ph1 update boot img and latest twrp.
https://drive.google.com/file/d/1R8wMO2ELfOsjRXYfPP6_100J6OCmRshd/view
When installing Magisk zip, Sideload it.
manr1mg said:
Click on link, Download essentials zip
Reboot to bootloader
Flash twp img
Boot to recovery
Once in twrp, flash pie img first "boot partition"
Then magisk zip and well-being If you want app timer/dashboard
Reboot device
(When rebooting, press "do not install" twrp as system app)
Contains latest ph1 update boot img and latest twrp.
https://drive.google.com/file/d/1R8wMO2ELfOsjRXYfPP6_100J6OCmRshd/view
Click to expand...
Click to collapse
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??
eric672913 said:
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??
Click to expand...
Click to collapse
Im sorry for the inconveniences but for some reason when installing Magisk, I had to Sideload it. I'll see how come but for now just Sideload Magisk after you flash boot img, that should do the trick.
After you flash twrp, go into twrp, install boot.img, MAYBE make sure system is mounted THEN install magisk. I've read some of the red errors happen regardless so I'd just fire up the phone afterwords and see if it works.
eric672913 said:
Thanks for your help. As I follow the steps , I got some errors when install Magisk & well-being which encloses screen shot in attached file. Anything wrong ??
Click to expand...
Click to collapse
you are flashing the boot image as system image and not as boot. I made that mistake too. Im pretty sure your phone doesnt boot to system after flashing magisk correct? Flash stock image again, go to twrp and when flashing boot image make sure you flash it to boot, not system.
luisoman2000 said:
you are flashing the boot image as system image and not as boot. I made that mistake too. Im pretty sure your phone doesnt boot to system after flashing magisk correct? Flash stock image again, go to twrp and when flashing boot image make sure you flash it to boot, not system.
Click to expand...
Click to collapse
Thanks for your reply. I am sure that I check "boot" when flashing stock img. Now I had try the following two ways:
1. when get into TWRP, I mount system first. and then install stock img, and then magisk. there's no error.
2. using sideload, fist sideload magisk, and reboot to bootloader , and then flash stock img, there's no error.
when I restart phone. No magisk apk installed. quite werid. Need your help.
manr1mg said:
Im sorry for the inconveniences but for some reason when installing Magisk, I had to Sideload it. I'll see how come but for now just Sideload Magisk after you flash boot img, that should do the trick.
Click to expand...
Click to collapse
Now I had try the following two ways:
1. when get into TWRP, I mount system first. and then install stock img, and then magisk. there's no error.
2. using sideload, fist sideload magisk, and reboot to bootloader , and then flash stock img, there's no error.
when I restart phone. No magisk apk installed. quite werid. Need your help.:fingers-crossed:
Painful thread to read.
Anyone have a resolution for this? I have searched, but can't find an answer.
you could reset your network in settings/system
ecompton59 said:
you could reset your network in settings/system
Click to expand...
Click to collapse
Sorry I should have done a better job clarifying. It WiFi does not turn on, on my phone with Magisk installed. It does with it removed. The icon goes through the process but never turns on.
jivy26 said:
Sorry I should have done a better job clarifying. It WiFi does not turn on, on my phone with Magisk installed. It does with it removed. The icon goes through the process but never turns on.
Click to expand...
Click to collapse
TWRP is the culprit, reflash the factory rom and it will work.
qbanlinxx said:
TWRP is the culprit, reflash the factory rom and it will work.
Click to expand...
Click to collapse
Dirty flash of the rom fixed it thank you
jivy26 said:
Dirty flash of the rom fixed it thank you
Click to expand...
Click to collapse
Did you flash it through TWRP or stock installer?
Thanks
bigjailerman said:
Did you flash it through TWRP or sick installer?
Thanks
Click to expand...
Click to collapse
Twrp but what he recommends hear overwrites my rom removing magisk. When I reflash magisk it's the same issue.
I'll look into sick installer.
Dont know the exact reason but custom kernal installation fixing it.
I fixed it by running the update through the local upgrade again. It fixed it after one local upgrade with standard magisk upgrade steps.
jivy26 said:
Twrp but what he recommends hear overwrites my rom removing magisk. When I reflash magisk it's the same issue.
I'll look into sick installer.
Click to expand...
Click to collapse
What Magisk version you use?
look this https://forum.xda-developers.com/on...nofficial-twrp-touch-recovery-t3860815/page24
Flash you're boot img after twrp.
Mervingio said:
What Magisk version you use?
look this https://forum.xda-developers.com/on...nofficial-twrp-touch-recovery-t3860815/page24
Click to expand...
Click to collapse
10.1 flashing a custom kernel then Magisk and I have no WiFi issues. It is some conflict with standard OnePlus 6t kernel.
https://forum.xda-developers.com/oneplus-6t/how-to/ultimateguide-t4004367
Take a look at this...
Payload dumper
You have to use payload dumper. Extract Payload dumper after You downloaded it in a folder. Download the lastest 6t Stock Android zip file 10.0.1, extract it and take out the payload.bin file,
put it in the input folder of payload dumper and start payload dumper. Wait some time. Now in the Output folder take out the boot.img and send it trough Your phone, install Magisk in Your phone. It is still uninstalled now and it will remain unistalled now. Tap on install where Magisk is uninstalled and still Red, again tap on install and choose patch a file, it will open Your Filemanager on Your phone, choose the destination of Your boot.img. and tap on Your boot.img file.
Now magisk will flash it. After that look in Your download folder, there You will find the file magisk_patched.img, save it on Your PC. Start Your phone in to the fastboot mode and flash in minimal-adb-or-fastboot the magisk_patched.img.
You have to write fastboot flash boot. Now drag and drop the magisk_patched.img in to the window, so it will look like this:
fastboot flash boot "C:\Users\(Your Username)\Downloads\magisk_patched.img"
Hit enter, just some seconds and it is done. Now write fastboot reboot and hit enter. The phone reboots and Wifi also appears and the sound is working. You have to do it again when the next update appears. Maybe Android Oxygen OS 10.0.2
I am wondering about the next updates from android 11 (R), 12 (S), 13 (T). If it will work the same till Fuchsia OS is coming out and we will say good bye to Android and maybe goodbye to custom ROMs.
But PC Games on the Phone would be a tasty thing because Fuchsia OS is supporting APKs and EXEs too.
Have Fun.
KitsuneUK said:
I fixed it by running the update through the local upgrade again. It fixed it after one local upgrade with standard magisk upgrade steps.
Click to expand...
Click to collapse
Did you have to go all the steps again...?
full rom through local updater dont reboot
flash twrp installer dont reboot
flash magisk on inactive sloth through magisk manager
or did you just flash the rom through updater and reboot?
Thanks
bigjailerman said:
Did you have to go all the steps again...?
full rom through local updater dont reboot
flash twrp installer dont reboot
flash magisk on inactive sloth through magisk manager
or did you just flash the rom through updater and reboot?
Thanks
Click to expand...
Click to collapse
I ran through the standard upgrade process for root.
Uninstall Magisk and restore original images
update through settings > local upgrade with the full ota zip
install magisk to inactive slot. That keeps magisk installed and should let you reinstall the update.
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
paq1170 said:
Hi i am on 11.0.7.7IN11AA rooted with magisk patched boot.img. i have received the update for 11.0.8.8IN11AA.
Has anyone been able to install and re-root with no issues? Please kindly explain your steps.
Click to expand...
Click to collapse
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
MrEvilPanda said:
After the update, i flashed the patched boot.img using fastboot command. Assuming no modules are conflicting you should have a rooted device. The one module that created a problem for me was OOS NATIVE CALL RECORDING. Disabling it solved any issue.
Click to expand...
Click to collapse
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Sneakdovi said:
How did u root on 11.0.8.8?
Do I have to repeat the process of downloading stock ROM, using payload dumper to get boot.img, patching it on magisk and flashing on fastboot?
Click to expand...
Click to collapse
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot commands.
MrEvilPanda said:
Yes i had to use the payload dumper to get the boot.img and then pacth it using the magisk manager and then flashing using fastboot comma
Click to expand...
Click to collapse
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
paq1170 said:
What if i just uninstall magisk(unroot), download and install the update, download only the boot.img then patch and get root?
I am trying to avoid downloading whole stock rom because of the boot.img when i can just download it alone.
Click to expand...
Click to collapse
We only need the boot.img(correct one) to proceed with root no need to download the entire stock rom.
Where are you guys getting 11.0.8.8IN11AA? Full zip?
Nothing on Oxygen updater for me yet.
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
datnewnew said:
Hey guys, so I've installed the new OTA, then went to magisk, installed magisk to inactive slot, rebooted and now the only thing happening is boot logo spinning....
what to expect? ofc, i didn't do a backup beforehand...
Click to expand...
Click to collapse
Things like this makes me so cautious and ask so many questions. Hope you didnt soft brick your device?
Okay it worked out somehow, i was looking for a stock boot.img, and was gonna flash that to try and save it, but had trouble with my pc recognizing my oneplus in fastboot mode, so i pressed both vol up/down and power at the same time to while being connected with usb cable, to try and get into fastboot, then screen went black but my PC got some pop ups for recognizing a device with unavailable drivers, then i just press vol up and power after a minute of it being black, phone rebooted and it loaded past the booting animation into android... weird stuff worked out, even after a dozen reboots with hardware keys, even letting it spin the animation for an hour...
I'm never updating again ahahhah
edit: if you do update, make sure you disable all your magisk/xposed addons and some native os call recording module... thats what i learned while googling yesterday, and its something i did not do, that could of have possibly contributed to my headaches
What i ended up doing that worked was;
. Flash stock 11.0.7.7 boot.img to slot A & B to unroot the phone.
. Reboot and install the ota update. I had no magisk modules to uninstall.
. After updating i downloaded the stock boot.img for 11.0.8.8 then patched and flashed to get rooted again.
Its a longer process but quite safer for me.
It's the same on each firmware, providing you have the full update available to you.
Use oxygen updater and grab the full update, download and install but don't Reboot.
Open Magisk send install after OTA.
Then reboot.
If you're unable to grab the full update then probably best to update then boot lineage recovery and sideload Magisk.zip using lineage recovery, then flash and you're done.
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Mchlbenner51 said:
Could someone post boot img I can't find this 11.8.8 to download.
Thanks.
Click to expand...
Click to collapse
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
If 8.8AA is in oxygen updater (full update)
Then make your own, using someone else's comes with inherent issues and risks.
It's good practice to make your own.
h4x3r101 said:
Same here please, cant find the 11.0.8.8.IN11AA anywhere.
Click to expand...
Click to collapse
Go here: https://forum.xda-developers.com/t/...magisk_patched-boot-img.4255757/post-85522541