Been using the Magisk OTA installation meathod on my Pixel 2 XL as outlined on
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Has always worked but with todays January 2019 update now once I rebooted phone goes to recovery says
"Can't load android system. your data may be corrupt" all it gives is retry or factory reset.
I have tried several times and same error
I have exactly the same problem! What I did notice is that the original boot.img's size is ~40Mb and the size of patched_boot.img is ~25Mb. I was able to get the phone to boot up normally again by reflashing boot.img.
arb1125 said:
I have exactly the same problem! What I did notice is that the original boot.img's size is ~40Mb and the size of patched_boot.img is ~25Mb. I was able to get the phone to boot up normally again by reflashing boot.img.
Click to expand...
Click to collapse
Where did you get that from?
I extracted the boot.img from the factory image zip file.
arb1125 said:
I extracted the boot.img from the factory image zip file.
Click to expand...
Click to collapse
Was is from the full 2019 jan OTA?
arb1125 said:
I extracted the boot.img from the factory image zip file.
Click to expand...
Click to collapse
I am in the bootloader but its not being detected, is it because I probably had usb debugging turned off?
Yes it was from the Jan 2019 factory image.
I used the fastboot command: fastboot boot boot.img.
I do have usb debug enabled
---------- Post added at 09:17 PM ---------- Previous post was at 09:04 PM ----------
I don't think having usb debugging disabled will affect fastboot
arb1125 said:
Yes it was from the Jan 2019 factory image.
I used the fastboot command: fastboot boot boot.img.
I do have usb debug enabled
---------- Post added at 09:17 PM ---------- Previous post was at 09:04 PM ----------
I don't think having usb debugging disabled will affect fastboot
Click to expand...
Click to collapse
I was unable to get adb devices to detect it in fastboot, i am in stock recovery now trying the adb sideload of the ota
that worked
back up and running ...phew
usb debugging was disabled. re enabled now
i did also notice the boot.img was 4.25mb vs what should be about 25-40mb
The one I extracted from the factory zip was around 40 Mb.
arb1125 said:
The one I extracted from the factory zip was around 40 Mb.
Click to expand...
Click to collapse
when I use Magisk to patch , the patched vs comes out to 4.25 and i think thats where the problem lies
I tried a few more things later this afternoon..
First I checked and saw that there is a newer version of Platform tools (platform-tools_r28.0.1-windows.zip) downloaded and worked in the new platform-tools directory.
I then flashed TWRP
I then I then tried to install Magisk17.3.zip using TWRP when install was complete I tried to reboot to system. It rebooted back to TWRP. I used fastboot to reinstall the original boot.img
I then tried to install Magisk18.1.zip using TWRP when install was complete I tried to reboot to system. It rebooted back to TWRP. I used fastboot to reinstall the original boot.img
I think I'm going to try the diagnostic version of Magisk 18.1 next.
Hopefully there is someone else who has a solution to our problem.
arb1125 said:
I tried a few more things later this afternoon..
First I checked and saw that there is a newer version of Platform tools (platform-tools_r28.0.1-windows.zip) downloaded and worked in the new platform-tools directory.
I then flashed TWRP
I then I then tried to install Magisk17.3.zip using TWRP when install was complete I tried to reboot to system. It rebooted back to TWRP. I used fastboot to reinstall the original boot.img
I then tried to install Magisk18.1.zip using TWRP when install was complete I tried to reboot to system. It rebooted back to TWRP. I used fastboot to reinstall the original boot.img
I think I'm going to try the diagnostic version of Magisk 18.1 next.
Hopefully there is someone else who has a solution to our problem.
Click to expand...
Click to collapse
Any solution on to getting this to install?
I finally got everything working by:
1) downloading platform tools version 28.0.1
2) downloading the January 2019 factory release and then unzipped it into the platform tools directory
3) booted phone into bootloader
4) ran flash-all from platform-tools
5) booted up system and skipped through set up screens.
6) went to setup and activated developer menu
7) in developer, enabled USB debugging and set default USB mode to file transfer
8) copied magisk version 18 from PC to phone main directory
9) copied trwp zip version 3.2.3-1 to phone main directory
10) rebooted phone into bootloader
11) typed fastboot boot twrp version 3 2.3-1 Img
12) phone should reboot into twrp, if not try again
13) once in twrp install twrp zip
14) I think the phone rebooted after that, not sure, anyway
15) reboot to bootloader and select recovery
16) then install magisk
17) then reboot and believe it or not it worked
I'm sorry I didn't get back to you sooner.
So if I am not using TWRP shouldn't I just be able to use magisk with standard recovery?
Every time I flash that patched boot image the phone just boots to the bootloader and does not boot.
I'm using the current stable condition at 18.0
Sent from my Pixel 2 XL using Tapatalk
Yes you should, but for some reason it doesn't work.
It seems to boot up fine if you first flash twrp and then flash magisk.
I just dirty flashed the January (2019) security update on my Google Pixel 2 XL and then reinstalled Magisk 18, but whenever I reboot my phone, Magisk is no longer installed.
I flashed the patched boot img using fastboot (I also have stock recovery) and the first time it boots, Magisk is installed and works fine, but if I reboot after that, it's no longer installed.
What fastboot command did you use to flash the modified boot image?
arb1125 said:
What fastboot command did you use to flash the modified boot image?
Click to expand...
Click to collapse
fastboot boot patched_boot.img
I think you need to use: flashboot flash boot boot.img
---------- Post added at 11:13 PM ---------- Previous post was at 11:11 PM ----------
Sorry not boot.img but patched_boot.img
Thanks, that did it.
Related
Hi Guys
My brothers lenovo K3note was runing RR rom and he did factory reset the phone, but now it only goes to TWRP and not booting into the OS
I tried to reinstall the RR rom, it installs normally but after reboot from TWRP, it goes back to TWRP instead of android Os.
What can i do now, please help
any help guys,
skyh3ck said:
Hi Guys
My brothers lenovo K3note was runing RR rom and he did factory reset the phone, but now it only goes to TWRP and not booting into the OS
I tried to reinstall the RR rom, it installs normally but after reboot from TWRP, it goes back to TWRP instead of android Os.
What can i do now, please help
Click to expand...
Click to collapse
Hello mate
Don't worry.. Just wipe system, data and cache and re-install rr rom. The same thing happened to me when i did a factory reset on that ROM.
i did all, it shows as installing but after reboot goes back to TWRP recovery only
change ur twrp recovery, i mean update your twrp recovery and you will never face this problem....
skyh3ck said:
i did all, it shows as installing but after reboot goes back to TWRP recovery only
Click to expand...
Click to collapse
I had the same problem a few days back. I tried everything but at the end, I had to flash the stock ROM using SP Flash Tool. After that, I was able to boot into Stock Android and rooted the phone again and installed the Custom Rom later.
TheRootRiffs said:
I had the same problem a few days back. I tried everything but at the end, I had to flash the stock ROM using SP Flash Tool. After that, I was able to boot into Stock Android and rooted the phone again and installed the Custom Rom later.
Click to expand...
Click to collapse
And from where have you downloaded the stock ROM?
VinayakS said:
And from where have you downloaded the stock ROM?
Click to expand...
Click to collapse
youtube(dot)com/watch?v=TySRc_DkcFk&t=251s
Follow this
TheRootRiffs said:
youtube(dot)com/watch?v=TySRc_DkcFk&t=251s
Follow this
Click to expand...
Click to collapse
Thanks, I have already downloaded from some other URL.
@ skyh3ck and VinayakS
did it help?
My phone got a bootloop to twrp 3.0.2-7 after I wanted to restore to factory settings (from settings menu), I tried flashing 'new' RR-N-v5.8.5-20170926-aio_otfp-FINAL (during flashing I had 2 errors - logs available), tried to flash with some other roms, I tried to restore some old backups - same thing = bootloop to twrp.
I don't want to brick it like the guy from this thread https://forum.xda-developers.com/k3-note/help/help-unbricking-k3-note-k50a40-charging-t3699007
Krzykor said:
@ skyh3ck and VinayakS
did it help?
My phone got a bootloop to twrp 3.0.2-7 after I wanted to restore to factory settings (from settings menu), I tried flashing 'new' RR-N-v5.8.5-20170926-aio_otfp-FINAL (during flashing I had 2 errors - logs available), tried to flash with some other roms, I tried to restore some old backups - same thing = bootloop to twrp.
I don't want to brick it like the guy from this thread https://forum.xda-developers.com/k3-note/help/help-unbricking-k3-note-k50a40-charging-t3699007
Click to expand...
Click to collapse
I did not had time to revert rooting and remove custom recovery, so can't say much at this moment.
But your bootloop issue is most probably due to presence of TWRP, you need to completely remove root & TWRP, restore stock boot and recovery, then try.
VinayakS said:
But your bootloop issue is most probably due to presence of TWRP, you need to completely remove root & TWRP, restore stock boot and recovery, then try.
Click to expand...
Click to collapse
Fortunately I've made it working again.
What I did, I flashed phone with SP FLash Tool 5.1628 and K50a40_S433_160909_ROW https://forum.xda-developers.com/k3-note/development/official-build-lenovo-k3-note-k50a40-6-t3370537. But it was not success at that time. Phone acted weirdly couldn't boot, only vibration after power on could be felt. So I tried to flash only the recovery Lenovo K3 Note Stock Recovery.img 10,2MB (also in the package but not default recovery image for S433) with the scatter map from S433 stockrom but SPFL said that it didn't end successfully, so I flashed only rocovery from stock rom S433 target_bin folder recovery.img 12800kB and then voila, it started to boot, there was a Lenovo logo, took some time to start but eventually phone is working.
Now I want to root it and / or flash correct version because my phone is actually k50-t5 not k50a40.
So thanks and good luck to those with similar problems after restoring factory settings on AIMROM.
same prob happend to me
first time encountering with TWRP loop.
downloading the stock rom
if there is any improvements will update
the solution for this(FIX)
all we need to do is reinstall a stock recovery and the again reinstall the TWRP
https://forum.xda-developers.com/k3-...-note-t3102997
follow this link..my phone just got fixed
nidheeshv said:
all we need to do is reinstall a stock recovery and the again reinstall the TWRP
https://forum.xda-developers.com/k3-...-note-t3102997
follow this link..my phone just got fixed
Click to expand...
Click to collapse
That link is incorrect / not working.
updating
VinayakS said:
That link is incorrect / not working.
Click to expand...
Click to collapse
wait i will update the link now
---------- Post added at 12:05 PM ---------- Previous post was at 11:49 AM ----------
Before proceeding download a stock and TWRP recovery from the link below
https://drive.google.com/file/d/0B2I5z1mFfUpcTUtjWUtpUmFCRWM/view
this is the stock recovery,extract this recovery and paste the contents to a folder named STOCK
https://drive.google.com/file/d/0B2I5z1mFfUpcaE5sZTk3M2Vrc1E/view
this is the TWRP recovery,extract this recovery and paste the contents to a folder named TWRP
1.install adb and fastboot on ur laptop.(am using ububtu 16.04)
2.make the phone to go to TWRP
3.plug in the usb
4.open terminal and type adb devices
5.see if device is detected ,if detected do the following
go to the STOCK rfolder u created and open terminal there.and type the following
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot
6.Now ur device will have stock recovery.
7.again repeat the above steps instead of STOCK use TWRP recovery.
8.your device will boot up with TWRP recovery build in
---------- Post added at 12:10 PM ---------- Previous post was at 12:05 PM ----------
nidheeshv said:
wait i will update the link now
---------- Post added at 12:05 PM ---------- Previous post was at 11:49 AM ----------
Before proceeding download a stock and TWRP recovery from the link below
https://drive.google.com/file/d/0B2I5z1mFfUpcTUtjWUtpUmFCRWM/view
this is the stock recovery,extract this recovery and paste the contents to a folder named STOCK
https://drive.google.com/file/d/0B2I5z1mFfUpcaE5sZTk3M2Vrc1E/view
this is the TWRP recovery,extract this recovery and paste the contents to a folder named TWRP
1.install adb and fastboot on ur laptop.(am using ububtu 16.04)
2.make the phone to go to TWRP
3.plug in the usb
4.open terminal and type adb devices
5.see if device is detected ,if detected do the following
go to the STOCK rfolder u created and open terminal there.and type the following
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot
6.Now ur device will have stock recovery.
7.again repeat the above steps instead of STOCK use TWRP recovery.
8.your device will boot up with TWRP recovery build in
Click to expand...
Click to collapse
dont download the files from the below link ,its for a different device ,its just a reference i used
the reference is
http://https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727
nidheeshv said:
wait i will update the link now
---------- Post added at 12:05 PM ---------- Previous post was at 11:49 AM ----------
Before proceeding download a stock and TWRP recovery from the link below
https://drive.google.com/file/d/0B2I5z1mFfUpcTUtjWUtpUmFCRWM/view
this is the stock recovery,extract this recovery and paste the contents to a folder named STOCK
https://drive.google.com/file/d/0B2I5z1mFfUpcaE5sZTk3M2Vrc1E/view
this is the TWRP recovery,extract this recovery and paste the contents to a folder named TWRP
1.install adb and fastboot on ur laptop.(am using ububtu 16.04)
2.make the phone to go to TWRP
3.plug in the usb
4.open terminal and type adb devices
5.see if device is detected ,if detected do the following
go to the STOCK rfolder u created and open terminal there.and type the following
adb reboot bootloader
fastboot devices
fastboot flash recovery recovery.img
fastboot reboot
6.Now ur device will have stock recovery.
7.again repeat the above steps instead of STOCK use TWRP recovery.
8.your device will boot up with TWRP recovery build in
Click to expand...
Click to collapse
dont download the files from the below link ,its for a different device ,its just a reference i used
the reference is
http://https://forum.xda-developers.com/oneplus-5/how-to/guide-fix-twrp-recovery-script-loop-t3649727
sudip_55 said:
change ur twrp recovery, i mean update your twrp recovery and you will never face this problem....
Click to expand...
Click to collapse
Exactly the same thing happened to me.
So I tried your idea and updated my TWRP, going from 2.8 to 3.1..1
But exactly the same thing happens - it still bootloops, but to the new TWRP.
I've tried flashing several different ROMs that all worked in the past. But no change.
Salvadorfreeman said:
Exactly the same thing happened to me.
So I tried your idea and updated my TWRP, going from 2.8 to 3.1..1
But exactly the same thing happens - it still bootloops, but to the new TWRP.
I've tried flashing several different ROMs that all worked in the past. But no change.
Click to expand...
Click to collapse
do as what i have mentioned above,..and give update
It worked ! Thanks.
The reason I didn't try it straight away was all the comments about wrong links etc. And some of the links afterwards didn't work. So I was looking for a recovery.img file in other places.
I read your new message, so I used the first link in your post which gave me the recovery img. The TWRP link doesn't seem to work, but I already have an up to date TWRP on the phone.
Is there some TWRP version with encryption support? Mine shows just random empty folders, doesn't ask for encryption key.
kokesh said:
Is there some TWRP version with encryption support? Mine shows just random empty folders, doesn't ask for encryption key.
Click to expand...
Click to collapse
Yes maunofrio
Like said above, always use the most recent mauronofrio's TWRP.
Thanks! Got the latest version, but now I am facing an issue with Fastboot. I'm in fastboot mode, with drivers installed, but it just keeps saying Waiting for the device. I have all drivers installed and ADB works fine when the phone is on. I didn't find the fastboot device in Device manager, when connected on any USB port.
kokesh said:
Thanks! Got the latest version, but now I am facing an issue with Fastboot. I'm in fastboot mode, with drivers installed, but it just keeps saying Waiting for the device. I have all drivers installed and ADB works fine when the phone is on. I didn't find the fastboot device in Device manager, when connected on any USB port.
Click to expand...
Click to collapse
On adb debugging
---------- Post added at 10:19 AM ---------- Previous post was at 10:17 AM ----------
Or you can install new twrp in old
EpickBroVlad said:
On adb debugging
---------- Post added at 10:19 AM ---------- Previous post was at 10:17 AM ----------
Or you can install new twrp in old
Click to expand...
Click to collapse
What I've done:
Booted old TWRP
Pushed new twrp.img into /tmp
Flashed image via old twrp
Flashed new OTA
Couldn't install magisk (system read only)
After reboot twrp overwritten by stock recovery
Fastboot works only with original xiaomi cable for some reason
Flashed twrp via fastboot. Didn't stick, stock recovery comes up all the time.
Fastboot boot twrp.img starts new twrp, flashed magisk via that one.
Now all is fine.
kokesh said:
What I've done:
Booted old TWRP
Pushed new twrp.img into /tmp
Flashed image via old twrp
Flashed new OTA
Couldn't install magisk (system read only)
After reboot twrp overwritten by stock recovery
Fastboot works only with original xiaomi cable for some reason
Flashed twrp via fastboot. Didn't stick, stock recovery comes up all the time.
Fastboot boot twrp.img starts new twrp, flashed magisk via that one.
Now all is fine.
Click to expand...
Click to collapse
Install it twice
EpickBroVlad said:
Install it twice
Click to expand...
Click to collapse
I did flash it twice in a row. And after that thrice. Didn't stick.
Hi Guys
UPDATE 2: (2/11/2019) Boot img now patched to Magisk V20.1 and added Google Drive as a mirror
UPDATE: It has come to my attention that some users are having issues with this version, please note this is still in beta and root isn't fully supported yet, also please make sure your running the latest magisk manager (version 7.3.5 at the time of this update) BEFORE flashing the patched boot IMG, those currently having issues, try flashing the stock IMG provided and installing the latest magisk manager then flashing the patched IMG
here is a working magisk patched boot img for you guys wanting root on your new android 10 open beta 1 software.
PLEASE BE AWARE THIS DOESNT COME WITH TWRP, THIS MAY ALSO BREAK THE ORIGINAL STOCK RECOVERY, BY FLASHING THIS BOOT IMG, YOU TAKE FULL RESPONSIBILITY FOR YOUR DEVICE AND NEITHER I OR XDA WILL BE HELD RESPONSIBLE
this DOESNT contain TWRP but is just rooted with magisk v20.0
simply flash the provided file in fastboot with the following command
Code:
fastboot flash boot magisk_patched.img
Code:
fastboot reboot
Please note this will ONLY work with the OnePlus 6T
i have also provided the stock android 10 boot img in case anything goes wrong
DOWNLOADS::
[CURRENT VERSION - Magisk V20.1]
Mega -> https://mega.nz/#!YI5BkICC!66fiUUdmg1EgGcTNExHZ52IoliVY4HBMBdwxErpI-co
Google Drive -> https://drive.google.com/file/d/1xyRPzsKh1kQXK0_RpdnesuR85vc6FvRf/view?usp=sharing
[OLD Versions]
[Magisk V20.0]
https://mega.nz/#!cQRFwA7b!R1yLz1ozFUTEOLXv-OREK-oF5YeUGN1PrWvSSh22vHw
Stock Boot img
https://mega.nz/#!1BAnRCoK!nu6UVAnR2yHnbaf54FEhc7U_3oEyP1q2BFMU0LK7XC4
Credits:
@oneplus for the phone and stock boot image
@topjohnwu for magisk and his boot image patcher
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Do i need a computer for this ?
techlogik said:
Trying now. Will report.
Update: Well, after a reboot, it is just sitting at the spinning animated boot logo...been like 10 minutes.
Also couldn't enter recovery after flashing the new patched boot img.
Update 2: Flashed back stock boot.img then recovery worked and phone booted fine.
Click to expand...
Click to collapse
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
charlie95113 said:
Do i need a computer for this ?
Click to expand...
Click to collapse
yes because fastboot command is needed, henced done using pc.
mywebslave said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Code:
fastboot flash boot_a magisk_patched.img
fastboot flash boot_b magisk_patched.img
Click to expand...
Click to collapse
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I also used the payload extractor and took the stock boot.img and patched it with Magisk myself. Same issue. So obviously Magisk just doesn't suppor this phone yet and Devs need to work on it.
Thx
techlogik said:
Did you try this by chance? We have the A/B partitions I don't think "fastboot flash boot ... " flashes both partitions.
Only the active partition gets flashed by default that is booting...it does that fine. I don't think Magisk is compatible on the OP6T for rooting and patching the new boot.img.
Same thing even manually flashing both. It just sits with the spinning boot animation for eternity.
I tried patching the stock boot.img myself as well, it ends up being the exact same size as the TS for this method...same problem.
Thx
Click to expand...
Click to collapse
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
mywebslave said:
Weird I was able to do the local update and install magisk to the inactive partition prior to reboot. On reboot worked fine just no recovery.
Maybe it just doesn't like this particular one. I used the latest canary version.
I'll try patching one when I get home and see how it goes. If it works out I'll post it here.
Click to expand...
Click to collapse
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
techlogik said:
Yes, I did the same thing. Also, as mentioned above, I used the payload extractor and grabbed the stock boot.img right from the Beta1 zip file.
Then, cppied over to the phone, used Magisk with Canary build as well, then flashed both boot_a and b directly with the patched file. Just sits at the animated boot spinning.
Flash stock images back, boots right up. I'm on a OP6T unlocked US phone on VZW. No problems with any other build beta or stable with twrp or magisk and custom kernels.
Thanks
Click to expand...
Click to collapse
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
So should we be using this instead?
Sent from my ONEPLUS A6013 using Tapatalk
mywebslave said:
So weird. Same setup as mine op6t, unlocked, Verizon. Haven't had a single issue. I'm gonna give it a try in a few minutes. I'll see what happens
---------- Post added at 08:19 PM ---------- Previous post was at 07:43 PM ----------
I did a fresh payload dump. Flashed to both A/B partitions, reboot, booted up fast as hell.
Here's the one I patched
magisk_patched.img
boot.img
Not sure if it makes a difference but I did mine on linux with latest platform tools.
Click to expand...
Click to collapse
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
zhenliang1102 said:
Gave this a try, no luck. Stuck in bootloop but as soon as I flashed back the stock boot, it booted up just fine
Click to expand...
Click to collapse
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
when i flash the magisk_patched.img and my cellphone reboot my cellphone does not recognize my simcard and have no network, am back on the stock boot.img
cultofluna said:
And this one?
fastboot --set_active=a
fastboot flash boot magisk_patched.img
fastboot --set_active=b
fastboot flash boot magisk_patched.img
fastboot --set_active=a
fastboot reboot
Click to expand...
Click to collapse
I doubt this would work because the patched image is only 26mb while the stock boot image is 64mb. Someone mentioned this in the OB thread
Black screen after the update
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Hy, do you have proximity sensor problem after update?! Thanks...is anything i can do?
jack5225 said:
[Solved] I am facing a serious issue. I was on Magisk v20.0 and Twrp 3.3.1-1
- I uninstalled Magisk
- Installed the OTA from local
- Installed Magisk on the second partition
- Reboot
Phone rebooted
But I am getting a totally blacked out screen. Calls work, vibration, Oneplus gestures work, just the screen is black (even in safe mode)
Can anyone please help me get this sorted (with data preserved if possible) I didn't back up the data cuz I wanted to do it after I updated to 10 (as downgrading wipes the system)
Problems:
ADB is not working (unauthorized) as I haven't turned on any developer options yet and can't due to black screen.
No way to unroot at this point without adb or twrp.
Thanks in advance.
UPDATE: Flashed boot.img and it worked. I guess magisk.img is not compatible or I am doing it wrong. My bet is on the latter.
Click to expand...
Click to collapse
Same happened to me
Phone boots to a Black screen
adb reboot bootloader -> works
fastboot flash boot boot.img -> works
Only Patched boot.img -> boots to black screen
Sent from my ONEPLUS A6010 using Tapatalk
Same for me. Softbrick and phone doesn't boot. It also encrypted my whole /data with diferent password i think and I had to wipe whole /data partition. System boots after wiping data storage but as soon as I install magisk it doesn't want to boot again. I guess I will wait for final image and TWRP support.
i couldnt flash it manually (via cmd), but all in one tool managed it well.
worked fine and quick,thank you
Crazy that some phones it is working and others it doesn't. Nothing we are doing wrong, OP has work to do still. I can imagine this official update to Q is going to cause a support fiasco...if you want to root that is. ROFL. All works fine with stock though upgrade. Understand it is Beta, but they claim a November official release
We are going to need some Dev help. Or going to need to sell this phone and upgrade to the 7t or Pro..haha
I'm asking for help because this has happened for two months now, and I'm wondering if the process has changed with the new unified Magisk.
The March Android 11 update has been posted, so -- just as I did in February::
1. On my computer, I
1a. Downloaded the factory image;
1b. Extracted the boot.img; and
1c. Sent it to my phone's Download folder.
2. On my phone, I
2a. Had Magisk "patch (the) selected file";
2b. Transferred the new patched boot image, magisk_patched_FKPSk.img, back to the computer; and
2c. Put the phone into fastboot mode.
3. Back on my computer, in adb, performed the "fastboot flash boot magisk_patched_FKPSk.img."
adb successfully flashed to boot_a, then I rebooted the phone. It rebooted surprisingly quickly.
Going into "System / Advanced / System Update," it still says
Android security update: January 5, 2021
So, what am I doing wrong? Should I force adb to flash to boot_b instead?
Thanks for any ideas!
NickEspo said:
I'm asking for help because this has happened for two months now, and I'm wondering if the process has changed with the new unified Magisk.
The March Android 11 update has been posted, so -- just as I did in February::
1. On my computer, I
1a. Downloaded the factory image;
1b. Extracted the boot.img; and
1c. Sent it to my phone's Download folder.
2. On my phone, I
2a. Had Magisk "patch (the) selected file";
2b. Transferred the new patched boot image, magisk_patched_FKPSk.img, back to the computer; and
2c. Put the phone into fastboot mode.
3. Back on my computer, in adb, performed the "fastboot flash boot magisk_patched_FKPSk.img."
adb successfully flashed to boot_a, then I rebooted the phone. It rebooted surprisingly quickly.
Going into "System / Advanced / System Update," it still says
Android security update: January 5, 2021
So, what am I doing wrong? Should I force adb to flash to boot_b instead?
Thanks for any ideas!
Click to expand...
Click to collapse
That doesn't have anything to do with Magisk. That's the firmware update you are on. If you want on a newer one you will to flash it. Then follow your previous steps. Magisk doesn't update your firmware for you.
Tulsadiver said:
That doesn't have anything to do with Magisk. That's the firmware update you are on. If you want on a newer one you will to flash it. Then follow your previous steps. Magisk doesn't update your firmware for you.
Click to expand...
Click to collapse
Ah. So then, if I understand correctly, the process is to unroot, sideload the OTA image (not just flash the factory image's boot.img file) via adb, and then perform the above steps to re-root?
NickEspo said:
Ah. So then, if I understand correctly, the process is to unroot, sideload the OTA image (not just flash the factory image's boot.img file) via adb, and then perform the above steps to re-root?
Click to expand...
Click to collapse
Yes, though I normally fastboot the factory images rather than sideload an ota. That update process will lose root, then you patch the boot.img and fastboot it to regain root. I would recommend removing all modules prior to updating as they will survive the update process (unless you wipe) and if not compatible with your update, will bootloop you once you root again.
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.
235anders15 said:
Leaving this here as i ended up boot looping from installing custom kernel, and it being a new release i was pulling my hair trying to figure this out.
Flashed through fastboot with "fastboot flash boot_a XX.img, fastboot flash boot_b XX.img"
Magisk included as thats the one i ended up using.
Save yourself the headache if you are planning on installing a custom kernel for now, and wait till the kinks have been ironed out.
Click to expand...
Click to collapse
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
sam_htc_touch said:
So I just flash the Magisk Patched into a and b slots and that should get me root using fastboot flash commands mentioned above? Sorry just wanted to double-check given that I had almost bricked my phone y'day :-D
Click to expand...
Click to collapse
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
235anders15 said:
Thats what worked for me, had to improvise as the OTA was brand new when I installed it, and bricked it with a new kernel, and had tried to fix it by flashing an old boot img but ended up complicating things even more.
You could always grab the stock 11.1.1.1 boot img and patch it in magisk manager yourself but procedure would be the same in fastboot
Click to expand...
Click to collapse
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
sam_htc_touch said:
Thanks a bunch for confirming, this gives me confidence and will go with patching mine as well
Click to expand...
Click to collapse
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
sam_htc_touch said:
Thanks a bunch @235anders15 I can confirm that I used your patched magisk image file and flashed it in both slots and have root back ..yayy! Simple process
Click to expand...
Click to collapse
Just for the benefit of all (if it matters), noticed that Magisk wasn't passing the Safety Net check and was showing failed for all 3. Used this fix and all is well now (Used the Sept 13 update on the page)
previously patching with stable 11.1.1.1 and broke some major functionality (eg: wifi crash, mess up video player and codec), now try to patch with magisk version, will update later
abhi0039 said:
I found a workaround. Firstly go to fastboot mode and flash stable.img from here https://forum.xda-developers.com/t/...os11-open-beta-2-3-and-stable-latest.4316563/ and boot into recovery. Now download TWRP and magisk and transfer to internal storage. Now flash TWRP and then download full OTA from here And put in storage https://www.xda-developers.com/oneplus-6-6t-oxygenos-11-1-1-1/
and flash it. Don't reboot once it says done. Go back and re install twrp.zip. Now reboot. Go to recovery and install magisk and clear dalvik. Now reboot and enjoy.
Thanks to
KizuYuna and Skanda Hazarika for providing stable.img and OTA respectively.
Click to expand...
Click to collapse
stable.img from there (and the other ones) dont fastboot boot on my OSS 1.1.1.1 fastboot mode.
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
F5:ed said:
I followed 235anders15 post and flashed both a and b slots, but it ended with endless boot logo (red dot with spinning white dot).
I can't go to fastboot mode, nothing.... please help!
Click to expand...
Click to collapse
Press and hold vol up, down , power at the same time for a while it will boot to fastboot.
I got boot loop after updating to 11.1.2.2
Any new boot img?
izik.avi said:
I got boot loop after updating to 11.1.2.2
Any new boot img?
Click to expand...
Click to collapse
Haven't tested yet but here you go
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
This one works great. Thank you.
The attached file in #13 above worked, thank you!
In case someone would like to now "How to do it" until next time this is how I did it:
How to install OOS update and root via created patch.img file in the Magisk app
1. Download the full version eg the OOS 11.x.x.x.zip file on the computer, and copy the file to the phone's internal memory as well.
2. Run the payload_dump program (https://androidfilehost.com/?fid=1899786940962605222) to extract a boot.img from the computer. You have to extract the payload.bin file from the OOS 11.x.x.x.zip file and place it in the Input folder, then run the exe-file and wait for payload to complete, then copy over the boot.img file found in the Output folder to the phone.
3. Go to Magisk app on the phone, click on the top install "Magisk", click "Select and patch a file", search for the boot.img file you created.
4. Now, Magisk will create a patched magic.img file from the boot.img file (can be called eg magic_patched-23000_xt8QR.img)
5. Copy the magisk_patched-xxxxxxx.img to your computer's "Root folder" where you have stored ADB files, etc
6. Now install the OOS 11.x.x.x zip file (should be in the mobile's Internal memory) via Settings> System> System updates and the "gear"> Local upgrade
7. When done, DO NOT reboot but go directly to Fastboot mode + connect cable to the computer
8. On the computer, type from your "Root folder":
fastboot flash boot magisk_patched-xxxxxxx.img
9. Reboot the phone - you are rooted!
rippledrums said:
Haven't tested yet but here you go
Click to expand...
Click to collapse
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
raymund08 said:
Is this magiskpatched.img for oneplus 6t?? Can I flash this in fastboot mode to root my oneplus 6t?
Click to expand...
Click to collapse
Yes
rippledrums said:
Yes
Click to expand...
Click to collapse
Thank you
Can confirm OP fastboot commands and patched boot img are working for 11.1.1.1.I uninstalled magisk by mistake and could regain root, quick and painless
Can anyone help me? flashed patched boot to A and B Slot. But Magisk is N/A. Any idea?