I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
TheRedPandaSSN said:
I've tried multiple rooting programs to try to root the phone, but none of them seem to work. So my question is, has anyone figured out a working method to get root? (I've unlocked the boot loader already)
Click to expand...
Click to collapse
I haven't been able to root it either. How'd u unlock the bootloader ?
greeneyez15o said:
I haven't been able to root it either. How'd u unlock the bootloader ?
Click to expand...
Click to collapse
If you go into developer options it allows you to unlock the bootloader.
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
I don't think that completely unlocks the bootloader
TheRedPandaSSN said:
If you go into developer options it allows you to unlock the bootloader.
Click to expand...
Click to collapse
All that does is ALLOW the bootloader to be unlocked - it doesn't unlock it.
I just unlocked the bootloader
Used adb
"Fastboot flashing unlock"
Next im gonna try to apply root
Wish me luck
I have just ordered this phone. Will hopefully be able to share backup copies of ramdisk(boot) to be used with magisk to give root
Well if anyone is Interested in trying out mtk-su to get system-less, boot-less root it should work. It worked with my umidigi phone that also has mtk p70 soc. And running pie.
https://forum.xda-developers.com/android/development/amazing-temp-root-mediatek-armv8-t3922213
Here is device back up script project I had done based on that mtk-su.
https://github.com/mrmazakblu/Root-Backup-Helper
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (currently i used V 7.3.4, after magisk update, V20 caused device trouble. Recommend stay with mahisk v19.3) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
:::UPDATE::10-27
Successfully flashed magisk with twrp. But because the current twrp has no working touchscreen. It was done with ADB commands.
mrmazak said:
My test of using mtk-su did not work out.
But i do have backup copy of the stock boot.img , install magisk manager (use most recent version, currently i used V 7.3.4) and patch the boot.img from link below, then flash with "fastboot flash boot /file.name" to have full root.
here is stock boot file
https://androidfilehost.com/?fid=1899786940962604580
Click to expand...
Click to collapse
How'd u patch the boot.img ?
Thanks !!!
greeneyez15o said:
How'd u patch the boot.img ?
Thanks !!!
Click to expand...
Click to collapse
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
Click to expand...
Click to collapse
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
greeneyez15o said:
Sorry for the question, but wheres the option to patch local file?
---------- Post added at 01:25 PM ---------- Previous post was at 01:01 PM ----------
I followed instructions, I keep getting error cannnot load 'patched_boot.img'
Click to expand...
Click to collapse
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Code:
adb pull /sdcard/Download/patched_boot.img c:\adb\
adb reboot bootloader
fastboot flash boot c:\adb\patched_boot.img
fastboot reboot
mrmazak said:
I feel maybe I was too general in the steps. (not enough detail) sorry.
If you got to the part when it is loading patched_boot
then you got past the patching part.
so, you need to find the patched_boot.img . It should be in the download folder on device
copy this to your PC.
reboot phone to bootloader mode.
then open terminal in same window as the copied patched_boot.img file, or use the full path name in the command.
In the following example, the patched_boot.img file is saved in c:\adb
Click to expand...
Click to collapse
Got it !!! Had to reboot my computer ?
mrmazak said:
You can follow full guide found on magisk thread.
Here is general steps.
1. Install magisk manager app
2. Select install. Choose option to patch local file.
3. When complete, copy that patched_boot.img to PC
4. Fastboot flash boot patched_boot.img
I did not share the patched boot.img. you need to do this step on your own. Is better that way.
Click to expand...
Click to collapse
Does anyone manage to change the system file? when you try the phone freezes helps reboot
fafanakatr said:
Does anyone manage to change the system file? when you try the phone freezes helps reboot
Click to expand...
Click to collapse
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
mrmazak said:
Do you mean, flashing gsi image, or editing things on stock system. I have been focussed on tarp, and my tried either case.
I can do that soon and confirm if system is freeze.
OK, first time i tried to flash GSI here it is failed.
used fastboot flash system **gsi.img**
(phh v119)
it flashed without error, but will not go past bootloader splash screen. --ODD
will try again later
Click to expand...
Click to collapse
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
fafanakatr said:
I did everything according to the instructions that you suggested, and everything worked out for me, I got a root, but when I try to change the system files, the phone freezes, maybe the root is not full? Thanks for your work)
Click to expand...
Click to collapse
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
I will try to do as you suggested and let you know) I will be well waiting for your success
mrmazak said:
Well all depends on what system files you have changed.
I was able to delete the system private-app file "blu-ignite" (an unauthorized app installed program) without freezing system.
I was on magisk 19.3. when I try to update to magisk v20 then I have issues. Freezes, wifi not turn on, ect. So try to restore stock, and Will have to use custom update Chanel with magisk to force it to use the older version.
I am also trying to see if twrp can be used tethered, to install magisk. By using "adb shell twrp sideload" command. And sideloading the magisk file.
If, when I see it works I can write the the whole process.
Click to expand...
Click to collapse
thank you very much I did everything according to the instructions and everything worked out for me,I tried to turn on the camera2api but so far without success,
can you understand this?
Related
Here're the official links for Cherry Mobile One H940:
For fastboot flashable images:
Builds Available: LBY29G, LMY47O
Download: here
For OTAs:
Build: LBY29G -> LMY47O
Android Version: 5.1 (Beta) -> 5.1 Official
Download: here
Flashing Instructions:
A. Using ADB sideload (for recovery flashable update zips):
1.) Flash stock recovery.
2.) Boot to stock recovery.
3.) Perform up + power button to show menu.
4.) Select Apply update from ADB.
5.) Install ADB drivers if on Windows and not yet installed.
6.) Open cmd prompt.
7.) Change directory to where you downloaded the update zip.
8.) Issue cmd: adb sideload <update.zip filename>
9.) Wait until completed.
10.) Select reboot.
B. Using fastboot:
1.) Boot into bootloader.
2.) Flash image using fastboot flash <partition name> <image filename>.img command.
3.) Reboot using fastboot reboot command.
C. Using DD (for flashing images like system.img):
1.) Boot into custom recovery. (you could use fastboot boot custom-recovery.img so that you don't overwrite your existing one)
2.) Push image file to /sdcard using adb push command. (you might have to mount the sdcard partition before doing this)
3.) Open an ADB command shell.
4.) Go to /sdcard.
5.) Find the system partition by issuing a cat /proc/partitions command. It should be the one sized exactly 1GB (1,024,000 shown).
6.) Use dd if=/sdcard/<image filename>.img of=/dev/block/<name of partition> .
7.) Reboot either using custom recovery or just issuing an adb reboot after exiting from ADB command shell.
do you have another working file for LMY47O system.img? i'm getting a fastboot flash fail (chunk unkown) error. thanks
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
intersectRaven said:
Reuploading now. Might be a bad upload from my end. Will post updated hashes later for the system.img.
Click to expand...
Click to collapse
same problem here
thank you
Uploaded. If it still fails, you might have to use dd to restore. Odd that it fails now when it was fine before. :/
OTA Flashing Error
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
erickho0407 said:
Hello. I would like to ask why I cannot flash the OTA Update for CM1. I am currently on LBY29G, rooted, unlocked bootloader and stock recovery. Thanks.
Click to expand...
Click to collapse
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
intersectRaven said:
Go back to stock boot. Since you're rooted, I'm assuming your boot has been modified to be insecure.
Click to expand...
Click to collapse
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
erickho0407 said:
Ok By going back to "stock boot," does this mean I have to re-lock the bootloader? I believe that I have only used the ALL-IN ONE TOOL in this thread to do the 3 things mentioned above, and also installed Lucky Patcher, Greenify, Busybox (Free) and Ad-Away in relation to root access, so I am not 100% sure by what you mean. Thanks again.
Click to expand...
Click to collapse
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
intersectRaven said:
No you don't need to relock the bootloader. You just need to flash stock boot partition. This is usually replaced when rooting.
Click to expand...
Click to collapse
Ok. So this means that I reflash boot.img right (would probably use fastboot). Thank you very much for assistance
Sir
can you capture ota for myphone uno
gabisonfire98 said:
Sir
can you capture ota for myphone uno
Click to expand...
Click to collapse
Unfortunately, I don't have an Uno so no.
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Working internal detect for pc and file ?
marjoejoejoe said:
still the same problem, will try DD **update still failed, and now can't flash old build...will try to restore a backup from CWM
Click to expand...
Click to collapse
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
intersectRaven said:
I see. Very weid. Might be some form of protection now for the system partition. I'll just take it down now so that no one else uses it.
Click to expand...
Click to collapse
I'll have another go at it later today. Was able to flash my own backup using CWM
marjoejoejoe said:
I'll have another go at it later today. Was able to flash my own backup using CWM
Click to expand...
Click to collapse
Still, it should be foolproof. I already checked and double-checked the system image I uploaded and it's mountable in Linux so it should restore correctly like the previous LBY image. I can't think of any other reason aside from some sort of protection that would disallow flashing of the system image through both fastboot and dd.
*On second thought, I'm reupping the image. I just flashed it using dd on my device and it works perfectly.
success, was running a windows 7 virtual machine in OSX. it must have been a protection, you are right...ran it using OSX instead (stupid me, why i didn't use it in the first place for fastboot).
files are good to go thanks man
Need help in Flashing the Stock Recovery.
Hi Guys,
I need help in flashing the stock recovery.
I've used the ALL-IN-ONE TOOL to unlock my phone's bootloader, flash the PhilZ Touch Customer recovery and Root my CM1
[http://forum.xda-developers.com/cro.../tool-master-tool-unlock-bootloader-t2997696]
However I'm unsuccessful flashing the stock recovery from the ALL-IN-ONE TOOL so I can update my phone's software to Android 5.1.1.
Can I flash the stock recovery using one of the files here? If yes, can someone please teach me how.
Thanks in advance!
OTG
Hi,
Just a quick question, after flashing using this ROM, will CM One support OTG? Or do I need to root the phone first? Is there a way to add support for OTG?
Pardon me if this may not be much related to the topic.
I understand there is no TWRP recovery for Zenfone 8 yet, but according to other posts, their are other ways to root the phone, e.g. using Magisk boot image patch method.
I tried, but I'm not able to flash the boot image in fastboot. I'm able to boot to fastboot mode, but it's showing no device when I use "fastboot devices" with USB connection. If I enter recovery mode, "adb devices" is showing unauthorized.
I don't know how to proceed. Appreciate your help!
It's solved by plugging the USB cable to USB 2.0 port on the PC
Good to hear it worked out. I was going to suggest installing a driver when in fastboot mode.
How did you get the boot image btw? I've never tried for anything other than a Lineage OS device, for which all the files are easily accesible.
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
After opening the bootloader and rooting the phone, are there any disadvantages you discovered? Warning screen on boot, (banking) apps not working, etc.?
DerSteppo said:
After opening the bootloader and rooting the phone, are there any disadvantages you discovered? Warning screen on boot, (banking) apps not working, etc.?
Click to expand...
Click to collapse
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
OK thanks for the information!
dohanin said:
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
Click to expand...
Click to collapse
After rooting, it seems that the official ota update cannot be detected, and it cannot be seamlessly achieved by using the Magisk to install to the unused slot. Is there any other way to achieve the update? For example, OnePlus can choose to install the full ota downloaded from the official website locally.
dohanin said:
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
Click to expand...
Click to collapse
Ah, thanks that did help. I didn't know the full firmware was available from the site.
yunyou said:
After rooting, it seems that the official ota update cannot be detected, and it cannot be seamlessly achieved by using the Magisk to install to the unused slot. Is there any other way to achieve the update? For example, OnePlus can choose to install the full ota downloaded from the official website locally.
Click to expand...
Click to collapse
Do you mean you already tried this with Zenfone 8 OTA update after rooting? I did it with firmware "WW-30.11.51.67" and it's still the current one, so I don't know whether it would work or not.
dohanin said:
Do you mean you already tried this with Zenfone 8 OTA update after rooting? I did it with firmware "WW-30.11.51.67" and it's still the current one, so I don't know whether it would work or not.
Click to expand...
Click to collapse
I found ota's solution. Download the "WW-30.11.51.67" firmware from the official website and move it to the main storage directory of the phone. Then the phone should detect the update file, but if the phone does not prompt, then try to restart the device. When the phone restarts and enters the system again, the system will detect the update, and there will be an update launcher notification in the notification bar!
When the system update interface is over, when prompted to restart, install to an unused slot through the Magisk option. Select the installation to keep ROOT to achieve seamless ota.
dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
If you use DRM Info app do you still have Widevine L1 security level? (needed for netflix hd playback) thanks.
grootzy said:
If you use DRM Info app do you still have Widevine L1 security level? (needed for netflix hd playback) thanks.
Click to expand...
Click to collapse
yes, it's showing L1 in Widevine CDM
dohanin said:
yes, it's showing L1 in Widevine CDM
Click to expand...
Click to collapse
Thanks, great news that ASUS are not being dicks with the bootloader unlocking.
For anyone else who isn't too clear on the steps (like me!) - After patching the boot image with magisk you then can use adb to pull that image to a PC and then use adb reboot bootloader and then fastboot boot patched-image.img to check the rooting works without flashing anything and then use adb reboot bootloader again and then fastboot flash boot patched-image.img to write it to the flash memory if everything went smoothly. This worked for me and everything seems great. Obviously you need adb and fastboot set up on your PC for this to work. I'm not sure if this was the intended method but it is what I did.
dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
did you try hiding magisk manager by changing the magisk manager package name? (it's an option in magisk manager).
some apps detect the magisk manager app to guess rooting.
If you hide magisk app + use magiskhide on the bank app it should be working.
please check let me know
fatjoez said:
did you try hiding magisk manager by changing the magisk manager package name? (it's an option in magisk manager).
some apps detect the magisk manager app to guess rooting.
If you hide magisk app + use magiskhide on the bank app it should be working.
please check let me know
Click to expand...
Click to collapse
hi, yes i tried but while most apps are working fine, some banking apps can still detect root. however, for those apps, if i disable the magisk app beforehand, then it can be passed. i could not figure why since the magisk app is already with a random package name. i posted my query in the magisk forum too.
anyway, with this method, i don't need to use work profile now.
Hi everbody.
I hope someone can help me out.
I unlocked my Zenfone 8 with the official unlock tool and i want to relock the bootloader back.
I was using commands like fastboot oem asus-lock, fastboot flashing lock, but nothing works.
Did Asus changed something in Android 11?
In Android 10 the first command was working without problems.
Thanks
You can't lock it back.
Only to change motherboard.
dron39 said:
You can't lock it back.
Only to change motherboard.
Click to expand...
Click to collapse
Oh that's bad news. Thank you very much for your fast answer.
yunyou said:
When the system update interface is over, when prompted to restart, install to an unused slot through the Magisk option. Select the installation to keep ROOT to achieve seamless ota.
Click to expand...
Click to collapse
Can you explain further on this? Are you saying to install the firmware to an unused slot? What exactly is an unused slot? I haven't seen anything like this in magisk.
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?
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, enter bootloader do a "fastboot flash init_boot magskpatchedfile.img.
9, reboot and test,
I have removed the _a in the cmd line as it appears its not needed
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum.
Ok,, this how I flashed ,and will flash, the new updates coming out so as not to lose data ,this will NOT do a wipe plus it's faster ,,,,, I know there are multiple other ways but for now I choose this,, hth
1. Download the correct ota file here
https://developers.google.com/android/ota and copy to adb folder
2. Place phone in factory recovery and toggle to apply update from adb,,
3. Open cmd prompt in adb folder type adb sideload factoryota.zip ,,,takes 5-10 minutes to complete, reboot ,,
if rooted,
1 download correct full image zip here
https://developers.google.com/android/images. That matches ota you just flashed,
2 extract the ini.boot.img , patch with magisk and reflash in adb for root
JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
Does the screen come on at all? In your other post you said it was black. If there's nothing at all on the screen, your phone is probably bricked.
JimJamer8 said:
it doesnt turn on at all
Click to expand...
Click to collapse
Have you tried a hard reset - hold the power button down for 10 seconds or so until the phone vibrates?
JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
You didn't try the steps I listed as I never said to flash a rooted bootloader
JimJamer8 said:
i tried these steps and now i have your device is corrupt and cannot be trusted, now my phone wont turn on or boot into recovery mode, its not detected by fastboot or adb
Click to expand...
Click to collapse
You may need to disable Verity and Verification. I flashed my stock image back to the phone using the tool here: https://flash.android.com/ and checked the boxes to disable verity and verification, then followed the steps above. Important to note that booting to Bootloader tells you which slot is active, and running the command fastboot flash init_boot magisk_patched_25205_GUID.img automatically patches the active boot slot. From there you just need to run the Universal Safety net fix from KDrag0n and the latest MagiskHide and you should be good to go
hammered58 said:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, boot to bootloader do a " fastboot getvar all " to see which slot is active it tells u somewhere at the top of the list
9, still in fastboot do a "fastboot flash init_boot_a magskpatchedfile.img. The _a is the active slot
10, reboot and test,
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum
Click to expand...
Click to collapse
Thank you for the help, turned out the _a was screwing me over, works great now!
mnemonical said:
Thank you for the help, turned out the _a was screwing me over, works great now!
Click to expand...
Click to collapse
I know ,,that was messing me up too, it did not work untill I put that part in,, don't ask me why! Lol
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
googletermsofservice said:
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
Click to expand...
Click to collapse
I imagine if you can uninstall the stock youtube app you'd be able to install Vanced from there.
atom_jack said:
I imagine if you can uninstall the stock youtube app you'd be able to install Vanced from there.
Click to expand...
Click to collapse
I'll give it a try
googletermsofservice said:
Has anyone been able to get the root version of Vanced Youtube to install? I'm getting an error saying that stock app is too new and it can't be downgraded.
Click to expand...
Click to collapse
Use the non replace version of revanced and disable stock YT
Hitman478™ said:
Use the non replace version of revanced and disable stock YT
Click to expand...
Click to collapse
Revanced Manager app is just going to black screen after install
hammered58 said:
Posting my findings here on how I rooted my p7, no links ,,as always do your homework before attempting . Plus I did a complete factory image reset via adb flashall.bat, I hope I didn't miss a step, Iam coming from a pixel 4a so it's almost the same
1, install latest adb platform tools on computer
2, unlock bootloader on p7
3, Download latest release of pixel 7 factory image on computer
4, unzip and copy init_boot.img to folder in phone
5, install latest Magisk 25.2 on phone
6, patch the init_boot.img with magisk
7, transfer patched file back to adb platform tools folder
8, boot to bootloader do a " fastboot getvar all " to see which slot is active it tells u somewhere at the top of the list
9, still in fastboot do a "fastboot flash init_boot_a magskpatchedfile.img. The _a is the active slot
10, reboot and test,
This is what finally worked for me after much testing and reading in the p7p forum. There may be additional steps to get safety net and such to work there is a lot of info on the p7p forum
Click to expand...
Click to collapse
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
AxelM said:
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
Click to expand...
Click to collapse
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
googletermsofservice said:
Revanced Manager app is just going to black screen after install
Click to expand...
Click to collapse
I've it installed and it's working without any issue
AxelM said:
Question: What did this command do? "fastboot flash init_boot_a magskpatchedfile.img" does it flash or just boot? Would it also be possible to do: "fastboot boot init_boot_a magskpatchedfile.img" and than install in inactive slot with magisk?
Click to expand...
Click to collapse
Use fastboot flash init_boot "image.img" without quotes and without specific the partition, it will goes on the active one, for me it has working at first try
hammered58 said:
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
Click to expand...
Click to collapse
THX, in fact the "fastboot boot" command was used a lot with OnePlus devices because it is safer to boot in the rooted os and when there is an error you can just reboot without the command...and when you install it afterwards with magisk you know it will work
Does Universal Safetynet Fix work?
Just wanted to thank OP. My Pixel 7 arrived about an hour ago, got the bootloader unlocked no problem, then actually I flashed the latest System Image first, then had Magisk patch init_boot.img, flashed that, easy peasy.
hammered58 said:
I don't know ,,I just posted what worked for me, your mileage may very!! The "fastboot boot" cmd was usually used for something like twrp afaik
Click to expand...
Click to collapse
It's usually used to temporarily boot a patched boot image and then you can do direct install in magisk manager
It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!
jcunwired said:
It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!
Click to expand...
Click to collapse
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.
lewmur said:
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.
Click to expand...
Click to collapse
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip
jcunwired said:
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip
Click to expand...
Click to collapse
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?
lewmur said:
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?
Click to expand...
Click to collapse
Because I was in ADB and like you said, what difference does it make?
jcunwired said:
Because I was in ADB and like you said, what difference does it make?
Click to expand...
Click to collapse
The difference is that your post said you installed Magisk and used it to patch the boot.img and it didn't work. Then the edit said you solved it by using adb to sideload magisk and that solved the problem. I'm still trying to understand how it did.