Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/sho....php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3Remove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291
Amazing! Thanks
I can confirm this worked on Android 10/Q. I can't use the canary patch method for magisk because I forgot to remove the modules before upgrading to Android 10. This method works like a charm, it removed the incompatible modules allowed me to by pass the bootloop.
Thank you so much for sharing!
For those who are wondering, these are the steps:
adb reboot bootloader
fastboot flash boot image-new.img
fastboot reboot
Done!
wao20 said:
For those who are wondering, these are the steps:
adb reboot bootloader
fastboot flash boot image-new.img
fastboot reboot
Done!
Click to expand...
Click to collapse
Second step should be:
fastboot boot image-new.img
Tulsadiver said:
Here is a fastboot bootable image to boot you into Magisk core-only mode. If you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-new.img
You will boot with root but modules disabled.
Tested by me and @123SIT whom contributed on the project.
Made from Pixel 3 XL but should work on the Pixel 3 also.
Image
https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
Thanks to @ApeironTsuka for his guide and everyone on the Magisk support thread like @jcmm11 for their patience and help.
Click to expand...
Click to collapse
Any idea if this works on the Pixel 2 and 2XL?
Sent from my Pixel C using Tapatalk
Alxoom33 said:
Any idea if this works on the Pixel 2 and 2XL?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
No, but you have TWRP. You don't need it.
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Sent from my Pixel 2 XL using Tapatalk
Alxoom33 said:
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Click to expand...
Click to collapse
Only since the update to android 10
Alxoom33 said:
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I just came across a time when I couldn't even boot TWRP on my Pixel 2. Here is a boot with root, core-mode Magisk image for Pixel 2 XL.
https://www.androidfilehost.com/?fid=1899786940962594367
Tulsadiver said:
I just came across a time when I couldn't even boot TWRP on my Pixel 2. Here is a boot with root, core-mode Magisk image for Pixel 2 XL.
https://www.androidfilehost.com/?fid=1899786940962594367
Click to expand...
Click to collapse
Yeah, I remember those days. Thanks for the image. Can it be flashed in TWRP or strictly adb/fastboot?
Sent from my Pixel 2 XL using Tapatalk
Alxoom33 said:
Yeah, I remember those days. Thanks for the image. Can it be flashed in TWRP or strictly adb/fastboot?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've only used fastboot.
Tulsadiver said:
Here is a fastboot bootable image to boot you into Magisk core-only mode. If you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-new.img
You will boot with root but modules disabled.
Tested by me and @123SIT whom contributed on the project.
Made from Pixel 3 XL but should work on the Pixel 3 also.
Image
https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
Thanks to @ApeironTsuka for his guide and everyone on the Magisk support thread like @jcmm11 for their patience and help.
Click to expand...
Click to collapse
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
FcukBloat said:
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
Click to expand...
Click to collapse
Here is a link to it on my GDrive. Can you please let me know when you've got it so I can delete it?
https://drive.google.com/file/d/1rg5wENhILz8ah8jSdLne2OtaLYGOhdBI/view?usp=sharing
sliding_billy said:
Here is a link to it on my GDrive. Can you please let me know when you've got it so I can delete it?
https://drive.google.com/file/d/1rg5wENhILz8ah8jSdLne2OtaLYGOhdBI/view?usp=sharing
Click to expand...
Click to collapse
got it! thanks this time too!
FcukBloat said:
got it! thanks this time too!
Click to expand...
Click to collapse
No problem. It's good to be a pack rat. I hope it worked.
FcukBloat said:
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
Click to expand...
Click to collapse
Mega link seems to be working. Open with chrome, not mega app.
Edit: I've added a AFH download link.
i tried with chromium based browser (vivaldi) from both phone and pc and link didn't work, probably it was a WiFi problem, thanks for adding alternative link though. and your core mode image worked like a charme! and thanks again also to sliding billy for initial mirror support
Just what I needed. Thank you
How did you create it? I want to make sure I have one of these images on hand in the future when I need to fix things
Simply works, thank you!
Holy cow, thanks man. I can't believe @topjohnwu let this slide through. Without TWRP wtf are you supposed to do, reflash the whole OTA/factory image?!
EDIT: Wait, now I can boot and apparently have root but I can't access any of my rooted apps. It says "waiting for root". Magisk Manager gives me an "app not installed" error but it is installed on the device. When I click it it says "upgrade to full Magisk Manager" and does nothing. How am I supposed to delete the module folder?
EDIT: Can't access terminal, can't do anything. Permission denied via ADB as well.
EDIT: DO NOT DELETE MAGISK MANAGER OR ALTER IT IN ANY WAY WHEN USING CORE MODE. You will be stuck like me. I had to nuke my phone and reflash everything. PIA
Related
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?
hi Guys!
I just wanted to share my work with you.
I created a working TWRP recovery for the Pixel on Android O developer preview 4, that can boot and decrypt the /data partition. I don't own a Pixel XL, so I can't test, but @Chainfire did a few quick tests and it seems to be working on his Pixel XL too. So I would say you can try and see if it works for you. Please keep in mind, that I didn't test it, and neither Chainfire, or myself or anyone else can be blamed if it doesn't work, or damages your phone (shouldn't actually, but who knows..).
If you are still not scared enough, please follow this link to the Pixel forums and check out my work:
https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
Good luck!
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
sahilarora2003 said:
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
Click to expand...
Click to collapse
Its in the instructions but here is the command and you shouldn't flash it but instead fastboot it.
fastboot boot trwp.img
flash the latest supersu 2.82 sr1
NVM. Mission accomplished. Thank you for help.
feimummy said:
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
Click to expand...
Click to collapse
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
SR2 flash fine
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
You can try SR2 flash fine.
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
feimummy said:
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
Click to expand...
Click to collapse
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
gubacsek said:
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
Click to expand...
Click to collapse
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
——————————The final outcome——————————
I have solved the problem with this SuperSU version:
https://forum.xda-developers.com/showpost.php?p=72686197&postcount=10481
Thanks a lot.
feimummy said:
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
Click to expand...
Click to collapse
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
gubacsek said:
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
Click to expand...
Click to collapse
Sr2 flash fine!
caballon said:
Sr2 flash fine!
Click to expand...
Click to collapse
Great! Nice to see that everything is working I had this itching, you know, when something is not as it should be, because I wanted to have Android O, but there was no recovery to do what I want... Now this feeling is gone, and I'm relaxed again
The only thing missing is a flashable zip. Is my current "itch"
Very nice. I booted into TWRP with no issue. I had already used boot-to-root so I did not have to flash SR2 in TWRP but nice knowing we have it working for the XL.
Thank you for making this sir.
Work like a charm in Final Android O!!! Thanks man.
caballon said:
Work like a charm in Final Android O!!! Thanks man.
Click to expand...
Click to collapse
Same here!
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
liam_davenport said:
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
Click to expand...
Click to collapse
Had this already sometimes on 7.1.2 with twrp rc 1 and 2. Must be an encryption error. Only way for me to use the phone again was to start all over with flashing factory image with flash-all.bat.
liam_davenport said:
People have successfully rooted O Final?
Click to expand...
Click to collapse
Reboot until you get prompted for your PIN in recovery, then flash SuperSU v2.82 SR3 from here.
While I tried to root using TWRP and all the suggested ways i continued to get errors, bootloops, corrupted boot, etc. I downloaded the rooted developers OS Image, then used magisk to patch the boot image. If anyone has any interest in the Boot.img or the developers OS image, let me know i can post links and instructions if needed. This will require the bootloader unlocked (i have read you can unlock with a keyboard, but i never had any luck and used a controller). Please reply with requests if needed.
Just one question: When you install the NEXT developer image, how will you go about retaining Magisk and your boot.img patch? Don't need a step-by-step-- just in simple terms. Curious.
EDIT: Found my answer: https://forum.xda-developers.com/showpost.php?p=77162700&postcount=85
I have a question i dont want create a thread for this so with root its possible to use 2 usb drive ?because for only the one right on the HDMI cable Work
laharl_22 said:
I have a question i dont want create a thread for this so with root its possible to use 2 usb drive ?because for only the one right on the HDMI cable Work
Click to expand...
Click to collapse
I'm not sure, but i think its possible to use 2 USB drives now if you turn off adb debugging or use a hub.
Michajin said:
I'm not sure, but i think its possible to use 2 USB drives now if you turn off adb debugging or use a hub.
Click to expand...
Click to collapse
Thanks it work
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
samjoandco said:
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
Click to expand...
Click to collapse
What version are you on? I downloaded the full zip, put the unzipped file on a USB from a computer. Then Took the USB to my Shield ran magisk manager 6.0 and installed, selecting patch boot, selecting the file from the USB. Magisk places the patched boot into my download folder where i pulled back onto my computer the fastboot flash boot boot.img (or patched_boot.img whatever the file is called that got patched).
I have the patched 7.1 boot.img right now. I have the full developers files, with drivers and patch all in it for 7.1 with magisk manager if you want i can put it on my Google drive for the whole thing. It is 1.09 Gb for the full files.
samjoandco said:
This is really good, thanks, so i can use flash this 7.0.2 boot.img on top of the latest "nv-recovery-image-shield-atv-7.1.0-dev_rooted" without any issues?
@Michajin Can you please share your boot.img that is patched with magisk?
Click to expand...
Click to collapse
Guess i Didn't read very well! Here is the Boot.img for magisk 7.1.
fastboot flash boot boot.img
Use 7-zip to unzip, had to make it a tar to upload here (12mbs)
How to fix a bootloader who not boot ? I have only bootloader IS unlocked warning screen and NVIDIA logo but no os and unable to boot bootloader or twrp
laharl_22 said:
How to fix a bootloader who not boot ? I have only bootloader IS unlocked warning screen and NVIDIA logo but no os and unable to boot bootloader or twrp
Click to expand...
Click to collapse
I am assuming you have a nvidia shield 2017
Download the full image from nvidia here
https://developer.nvidia.com/gameworksdownload#?search=SHIELD%20TV%202017%20Developer&tx=$additional,shield
Connect via fastboot (plug in controller press A - B and power on)
From fastboot connect with a computer via A-A usb cable
unzip the file from nvidia into the folder where your fastboot drivers are
run the flash-all.bat file
Michajin said:
Guess i Didn't read very well! Here is the Boot.img for magisk 7.1.
fastboot flash boot boot.img
Use 7-zip to unzip, had to make it a tar to upload here (12mbs)
Click to expand...
Click to collapse
Thanks Michajin, much appreciated, I will try it on the weekend! :highfive::good:
One question:
I am on the latest 7.1.0 but not on developer image, can i just unlock the bootloader and flash the boot image to get root ?
or i need to installed the developer version (nv-recovery-image-shield-atv-7.1.0-dev_rooted)?
I dont want to install everything again.
samjoandco said:
Thanks Michajin, much appreciated, I will try it on the weekend! :highfive::good:
One question:
I am on the latest 7.1.0 but not on developer image, can i just unlock the bootloader and flash the boot image to get root ?
or i need to installed the developer version (nv-recovery-image-shield-atv-7.1.0-dev_rooted)?
I dont want to install everything again.
Click to expand...
Click to collapse
As far as i know Unlocking erases data anyways. You unlock you have to reinstall everything anyways.
The boot image works only on developer image? Thanks
gas80 said:
The boot image works only on developer image? Thanks
Click to expand...
Click to collapse
I don't know what the differences are between the dev image and the regular version. I believe the dev version is just pre-rooted. I think it will work, but i have only tested on the dev image. Flash at your own risk.
Hi there,
I need help. Im looking for a ROM thats flashable with TWRP so i can install it. Previously I had Lineageos installed but it wasnt running smooth enough.
I cant install the rooted recovery file from Nvidia with TWRP.
The reason why im wanting to use TWRP is because i want to use Magisk with the Shield.
Ive allready patched a stock boot image with magisk version 17.1
my current Twrp version is 3.2.1-1
Thank you very much
cheers
[Edit]
I solved the problem by following this post
thanks
Michajin said:
What version are you on? I downloaded the full zip, put the unzipped file on a USB from a computer. Then Took the USB to my Shield ran magisk manager 6.0 and installed, selecting patch boot, selecting the file from the USB. Magisk places the patched boot into my download folder where i pulled back onto my computer the fastboot flash boot boot.img (or patched_boot.img whatever the file is called that got patched).
I have the patched 7.1 boot.img right now. I have the full developers files, with drivers and patch all in it for 7.1 with magisk manager if you want i can put it on my Google drive for the whole thing. It is 1.09 Gb for the full files.
Click to expand...
Click to collapse
Could you please upload it on google drive. That would be greatly appreciated. :good:
gambaaa said:
Could you please upload it on google drive. That would be greatly appreciated. :good:
Click to expand...
Click to collapse
I dont know if it sent, here is a link for the dev image with magisk installed on the boot.img. The original and patched boot.img are in the zip file., along with the magisk app.
Please flash at you own risk, i have the 2017 shield and it worked for me. I ran the flash-all.bat.
Here is a link to the file on my GDrive ( I will be blocking access after the weekend)
Goodluck,
Michajin
Michajin said:
I dont know if it sent, here is a link for the dev image with magisk installed on the boot.img. The original and patched boot.img are in the zip file., along with the magisk app.
Please flash at you own risk, i have the 2017 shield and it worked for me. I ran the flash-all.bat.
Here is a link to the file on my GDrive ( I will be blocking access after the weekend)
https://drive.google.com/open?id=15sJ6YFmwiAZX0mXQk_ANq5Nfvs9E8oJF
Goodluck,
Michajin
Click to expand...
Click to collapse
Great job! I will try it this week-end. So I just plug my nvidia shield via usb and run the flash-all.bat ? Also, do I need to unlock my bootloader before doing anything. I have stock 8.0 oreo
gambaaa said:
Great job! I will try it this week-end. So I just plug my nvidia shield via usb and run the flash-all.bat ? Also, do I need to unlock my bootloader before doing anything. I have stock 8.0 oreo
Click to expand...
Click to collapse
Yes, as far as i know you have to have an unlocked bootloader. You plug in your Sheild VIA a-a USB, you might have to install the sheild drivers. Press AB on your controller and power on. That will get you into fastboot. You have to run the unlock bootloader command WARNING this will wipe your DATA. All the drivers you need will be on this page available to download https://developer.nvidia.com/shield-open-source and for instructions on how-to goto here http://nv-tegra.nvidia.com/gitweb/?...;f=README_NEW_SHIELD;hb=rel-24-uda-r1-partner (the instructions tell how to do flash each file, i found it faster to do the flash-all.bat, but be patient, i think it takes about 30 minutes)
Michajin said:
Yes, as far as i know you have to have an unlocked bootloader. You plug in your Sheild VIA a-a USB, you might have to install the sheild drivers. Press AB on your controller and power on. That will get you into fastboot. You have to run the unlock bootloader command WARNING this will wipe your DATA. All the drivers you need will be on this page available to download https://developer.nvidia.com/shield-open-source and for instructions on how-to goto here http://nv-tegra.nvidia.com/gitweb/?...;f=README_NEW_SHIELD;hb=rel-24-uda-r1-partner (the instructions tell how to do flash each file, i found it faster to do the flash-all.bat, but be patient, i think it takes about 30 minutes)
Click to expand...
Click to collapse
Wonderful! Thanks for the explanation!
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
cubano2031 said:
Is there any way to root this phone? I would like to root just to edit the build.prop for the camera api in order to install the Gcam port ....
Click to expand...
Click to collapse
Sent from my LGE LM-X410.FGN using XDA Labs
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Rebel_X said:
Do you mind to elaborate about the steps taken to get and patch boot image?
What I did is I grabbed the "boot_X-FLASH-ALL-8F02.sin" file, used UnSIN tool to convert it to "boot.img" and then Android Image Kitchen AIK to unpack and repack the image (this step is necessary on older Xperia phone, is that the case here?), then finally patch the repacked boot image using Magisk.
But when flashing the new patched boot image, I get a non functional touch screen and wifi. I was able to control the phone using ScrCpy tool to mirror the phones screen on my computer and control the phone from the window that appears on the computer. But since WIFI won't even turn on, I couldn't even verify that Magisk was working or not.
What is worse, is that if I tried to flash the original untouched Boot image SIN or the converted IMG, the phone still has non-working touch-screen and WIFI.
FlashTool by Androxyde and EMMA tools do NOT support this phone yet. I ended up using Newflasher tool to go back to stock (still unlocked bootloader) and everything works fine, but no root.
I have the US model I3223 btw.
Thank you kindly, awaiting your response.
Click to expand...
Click to collapse
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
Thanks a lot!! And it was as simple as that. It works fine. :good:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
MAREK10747 said:
I can do kernel with magisk for you I need only sin file boot_X-FLASH-ALL from .ftf file Who want to get the kernel , please send to me pm with this file and variant (I32XX or I42XX) !!
Click to expand...
Click to collapse
Hi,me devie is I4293
I have unrar the rom , so i get the boot_X-FLASH-ALL-8F02.sin
would you mind to make the kernel for me?
the file is here :
https://drive.google.com/file/d/1sywqfBtELSTgRXtTBEvlI454K_1ul-1h/view?usp=sharing
my gmail is [email protected]
you can send it to me.
thank you.
Zaben said:
Magisk Manager (the app) was able to patch boot_X-FLASH-ALL-8F02.sin directly and return an img file. I used fastboot to flash the patched boot.
Click to expand...
Click to collapse
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
yishisanren said:
You patched boot with magisk19 or 19.1?
Now i use magisk19.1, my phone always go into a boot loap.
Click to expand...
Click to collapse
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Zaben said:
See https://forum.xda-developers.com/10-plus/how-to/magisk-19-1-7-1-2-notes-t3926611
Click to expand...
Click to collapse
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
yishisanren said:
So now Xperia 10 or 10 plus can not be rooted by magisk. Because Maigsk 19.1 will be failed
Click to expand...
Click to collapse
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
wang4632 said:
yes, i think so. it caused looping on my Xperia 10. (by Maigsk 19.1)
do you know any place and download older version of Maigsk??
Click to expand...
Click to collapse
older version can not patch boot.img, because when you click "install the zip",it will let you update the new verison.
Any news on the boot loop situation? I also encounterd this problem and back to running original boot.img. having an unlocked bootloader is useless without root ?
Zaben said:
If you have an unlocked bootloader, the patched boot generated by Magisk Manager did work for me.
Click to expand...
Click to collapse
Did you lose any feature like super vivid mode and camera focusing after unlocking the bootloader?
can't find the driver, the model is l421dual sim, can't rooting, have i already patched the boot img?
My I4293 stuck in bootloop~~help ~!
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
This phone cannot be rooted at this time due to the lack of the img.patch and no driever.
Zack_U said:
After installing Magisk19.3 with TWRP, my phone stuck in bootloop and can not enter the recovery mode.
I tried to flash I4293_53.0.A.6.96_1318-2077_R1A.ftf (Factory ftf. downloaded from experifirm) with flashtool to solve this problem.
when I tried to create bundle, I found that I4293 did not show in the ID list.
I can't do anything about it.
Anybody can help me plz~~ I'm fresh in XDA and just try to root my phone first time :crying:
Click to expand...
Click to collapse
Are you still stuck? For all of the latest Sony phones try NewFlasher instead.
https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426
Flashtool doesn't support our phones. Magisk 19.1+ currently doesn't work with our phones. Hopefully 19.4 will fix that.
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
T4gB0t said:
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
Click to expand...
Click to collapse
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Hw4ng3r said:
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Click to expand...
Click to collapse
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
T4gB0t said:
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
Click to expand...
Click to collapse
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Hw4ng3r said:
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Click to expand...
Click to collapse
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
T4gB0t said:
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
Click to expand...
Click to collapse
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Hw4ng3r said:
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Click to expand...
Click to collapse
I downloaded the software from the official website and used payload dumper to extract the boot image. To be sure that I understood everything... you suggested to use "fastboot boot patched.img" instead of "fastboot flash boot patched.img", and once the phone restarted to go to magisk manager and click direct install.
Do I need Magisk Manager canary or the normal version for this to work and do I have to mantain the canary version or can I install the normal version once it is rooted?
Either 22.1 or Canary works for A11
Hw4ng3r said:
Either 22.1 or Canary works for A11
Click to expand...
Click to collapse
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
T4gB0t said:
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
Click to expand...
Click to collapse
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
T4gB0t said:
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
Click to expand...
Click to collapse
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Hw4ng3r said:
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Click to expand...
Click to collapse
So not Magisk v.23 but Magisk canary?
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Hw4ng3r said:
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Click to expand...
Click to collapse
Okay thanks, I'll try with v.23 first and If that does not work than I'll try with the canary one. Thank you very much!!!
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Wacko1805 said:
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay thank you, I'll try if the other method does not work
T4gB0t said:
Okay thank you, I'll try if the other method does not work
Click to expand...
Click to collapse
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Hw4ng3r said:
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Click to expand...
Click to collapse
I'm sorry to bother you again, but I tried with "fastboot boot patched.img" and it still did not work. It got stuck while booting again with "unable to parse kernel log" as error message. Do you have any other suggestions?
P.S. I got a full backup with "adb backup -apk -all -shared -f /path/to/location" today and thought about just doing a factory reset, trying to root the phone, restore the backup. Do you think that might actually work? Thank you for your help!
How exactly did you patched your boot.img?
FSadino said:
How exactly did you patched your boot.img?
Click to expand...
Click to collapse
I tried doing it with magisk (both v.23 and canary)