Database Users

[MAGISK] in OREO | OP3/3T 8.0/8.1

SUPPORTS 3/3T oreo
UPDATE:
Installation:
1.Flash TWRP latest
2.Flash latest magisk 14.5(beta)
Reboot
This process is difficult for some people. If you dont understand do not try this.
This is only for 8.0 oreo users
IM NOT RESPONSIBLE FOR OF YOUR DEVICE
Dont get panic nothing is going to happen
Credits:
@akhilnarang for Modified TWRP
INSTALLATION
IMPORTANT
Download the necessary zip file according to your device.
DO NOT TURN ON YOUR DEVICE UNTILL THE WHOLE PROCESS END.
If you twrp replaced by stock recovery in some steps just reflash the twrp and continue.
INSTALLATION:
STEP 1: Flash modified twrp and boot into recovery
STEP 2:Flash bootloader.zip and turn off your device by power button.
STEP 2.1: Boot into bootloade and connect to pc and type in adb cmd fastboot oem selinux permissive
FOR SOME ADB NOT ACCEPT ABOVE CMD AND THOSE FOLLOW THE GUIDE AND OTHERS JUST FLASH THE MODEM.ZIP AND MAGISK
STEP 3:Again boot into twrp and choose Advanced>sideload
STEP 4: Connect device to pc and open adb cmd and type abd sideload <file_path_modem.zip>
OP3 users skip step 5 and 6
STEP 5: Turn off your device by power button and reboot into bootloader
STEP 6: Flash boot.img fastboot flash boot boot.img
STEP 7: Finally reboot into recovery and magisk 14.3 and restart the device
For people dont understand this i uploaded a video of this tutorial kindly watch tell
DOWNLOAD SECTION:
OP3T: [url]https://drive.google.com/open?id=0B2rXSbosp3PfYmttd29MeEphdlk[/URL]
OP3:[url]https://drive.google.com/open?id=0B2r...[/URL]
Magisk 14.3(beta):[url]https://drive.google.com/open?id=0B2rXSbosp3PfWHQwaUxrQmNWZTA[/URL]

??

waiting.....

I like penguins.

magisk
да уже есть рабочий magisk для oneplus 3/3t '' oreo ":good:

reported

Explain why this works. And what modifications did you do to the boot image and bootlaoder image?

Yeah, we need some major details.. what exactly are we flashing here? I understand and it's a great guide if it works, but why does it work?

Lol, flash a boot.img without sources / knowing where the image come from ?
Nope, sorry.

casual_kikoo said:
Lol, flash a boot.img without sources / knowing where the image come from ?
Nope, sorry.
Click to expand...
Click to collapse
Exactly.. I'm guessing that's the basis for another person commenting they've reported the thread.. and why we're pushing for info. Nice if it works, but we need to see/know why it works.

jbarcus81 said:
Yeah, we need some major details.. what exactly are we flashing here? I understand and it's a great guide if it works, but why does it work?
Click to expand...
Click to collapse
Actually boot loader.zip from older OOS 3.2.0. And [boot.img is from OB16(THIS STEP IS ONLY FOR 3T)]
I just downgrade the boot loader.

ZacharyTheUmbreon said:
Explain why this works. And what modifications did you do to the boot image and bootlaoder image?
Click to expand...
Click to collapse
Boot img is stock oreo boot img for 3T only.
Bootloader is downgraded for those abd is not accepting the cmd fasboot oem selinux permissive.

sparky vicky said:
Boot img is stock oreo boot img for 3T only.
Bootloader is downgraded for those abd is not accepting the cmd fasboot oem selinux permissive.
Click to expand...
Click to collapse
But you forgot to say that when you set selinux permissive via fastboot you'll have a big freeze in system

jbarcus81 said:
Exactly.. I'm guessing that's the basis for another person commenting they've reported the thread.. and why we're pushing for info.
Click to expand...
Click to collapse
Not completely sure either, but I think the "reported" comment was due to the fact the thread was started (with title referencing Magisk in Oreo) with the only text in the first post saying "uploading". And it stayed that way for hours. It felt like an unnecessary and gratuitous tease.
Not 100% sure of the timing (I dropped offline) but I think the actual guide/instructions were not posted until (hours) after the "reported" post.

redpoint73 said:
Not completely sure either, but I think the "reported" comment was due to the fact the thread was started (with title referencing Magisk in Oreo) with the only text in the first post saying "uploading". And it stayed that way for hours. It felt like an unnecessary and gratuitous tease.
Not 100% sure of the timing (I dropped offline) but I think the actual guide/instructions were not posted until (hours) after the "reported" post.
Click to expand...
Click to collapse
Ah that could be ...

@topjohnwu is looking into it already: https://forum.xda-developers.com/on...vice-development/kernel-t3404970/post74192753

It works!
I flashed boot image and Modem.zip in twrp instead of using the terminal. Works great! Thank you.

Link for OP3 is broken - OP3:https://drive.google.com/open?id=0B2r...

Is this a working method to get magisk running as without magisk I'm hesitant to update.

wyrmeth said:
Is this a working method to get magisk running as without magisk I'm hesitant to update.
Click to expand...
Click to collapse
Wait a week and see if there's an update that doesn't require hacky workarounds.
Sent from my OnePlus3T using XDA Labs

[Guide][Treble] Install Android 9.0 Pie AOSP GSI (Windows/Mac/Linux)

Install Android 9.0 Pie AOSP GSI
Warning
You will loose all your data. Make sure to backup. You are doing this at your own risk. Neither me nor xda is responsible for any bricked devices.
Pre-Requisites
Please read carefully. Any questions which are already answered in OP will be ignored.
If you have a question, not answered in OP read last 2-3 pages. Any questions which are already answered in last 2-3 pages will also be ignored.
Not being rude, but people need to start reading.
Make sure you have unlocked the bootloader.
​Text Guide
Install Android 9.0 Pie AOSP GSI
1. Download AB Arm64 GSI from link in downloads. Unzip it. Windows users can use Winrar. Mac users can use the Unarchiver.
2. Download and unzip adb & fastboot linked in downloads section.
3. Place the extracted system image (step 1) in platform-tools folder. Rename it to system-arm64.img.
4. Power off phone.
5. Press and hold volume down and power button at the same time. You will now boot into fastboot boot.
6. Connect phone to computer.
7. Windows users open command prompt. Mac/Linux users open Terminal. Navigate to the folder where you unzipped adb & fastboot.
Windows
Code:
fastboot devices
Mac & Linux
Code:
./fastboot devices
If your device shows up, drivers were installed correctly. If not, then drivers were not installed and you need to install them.
8. Erase System
Windows
Code:
fastboot erase system
Mac & Linux
Code:
./fastboot erase system
9. Flash Android Pie GSI
Windows
Code:
fastboot flash system system-arm64.img
Mac & Linux
Code:
./fastboot flash system system-arm64.img
10. Wipe/Factory Reset
Windows
Code:
fastboot -w
Mac & Linux
Code:
./fastboot -w
11. Reboot
Windows
Code:
fastboot reboot
Mac & Linux
Code:
./fastboot reboot
11. Profit. Android 9.0 Pie. Rooting might result in broken Wi-fi. So, flash back stock boot.img if your wifi is broken after rooting.
Video Guide
Downloads
MiUnlock Tool - http://xiaomi-miui-ota-3rdrom.ks3-c...1/3.3.525.23/miflash_unlock-en-3.3.525.23.zip
Latest ADB & Fastboot :- https://developer.android.com/studio/releases/platform-tools
Setup ADB and Fastboot (if above adb & fastboot do not work) - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Android 9.0 Pie GSI Thread :- https://forum.xda-developers.com/pr...velopment/aosp-9-0-phh-treble-t3831915/page12
Android 9.0 Pie GSI Download Links :- https://github.com/phhusson/treble_experimentations/releases
Winrar (Windows) :- https://www.rarlab.com/
The Unarchiver (Mac):- https://theunarchiver.com/

@munchy_cool wow!!!, Thanks man. But sorry but i have to ask, did you try this on your A2 is it working fine without any issues?

crazykas said:
@munchy_cool wow!!!, Thanks man. But sorry but i have to ask, did you try this on your A2 is it working fine without any issues?
Click to expand...
Click to collapse
the A2 in the video is mine. I tried it for some time. Camera works, wifi works, sound works, charging works, couldnt check calls and lte as I am at work and cannot have my sim turned off for even a minute. But yes it works.

munchy_cool said:
the A2 in the video is mine. I tried it for some time. Camera works, wifi works, sound works, charging works, couldnt check calls and lte as I am at work and cannot have my sim turned off for even a minute. But yes it works.
Click to expand...
Click to collapse
much appreciated man!! Reason i asked this is i ****edup my phone before cause of that fastboot boot twrp > set active b slot thing. So my warranty covered me and gave a new phone. lol. BTW what do you mean by "cannot have my sim turned off for even a minute"? Finally it will be great if you can add how to flash back the stock rom as well.. Thanks mate :good:

crazykas said:
much appreciated man!! Reason i asked this is i ****edup my phone before cause of that fastboot boot twrp > set active b slot thing. So my warranty covered me and gave a new phone. lol. BTW what do you mean by "cannot have my sim turned off for even a minute"? Finally it will be great if you can add how to flash back the stock rom as well.. Thanks mate :good:
Click to expand...
Click to collapse
not sure how you bricked it but glad you got a new phone.
"cannot have my sim turned off"
So, I have only one sim which is in my work phone. to test LTE, data etc i will have to remove the sim from that phone and put it in the Mi A2. Now, I cannot do that as I cannot have my sim (phone number) turned off for even a minute due to work.
As for going back to stock. Download stock firmware, extract it and replace pie gsi img with system.img from factory firmware zip and you will be back to stock.

munchy_cool said:
not sure how you bricked it but glad you got a new phone.
"cannot have my sim turned off"
So, I have only one sim which is in my work phone. to test LTE, data etc i will have to remove the sim from that phone and put it in the Mi A2. Now, I cannot do that as I cannot have my sim (phone number) turned off for even a minute due to work.
As for going back to stock. Download stock firmware, extract it and replace pie gsi img with system.img from factory firmware zip and you will be back to stock.
Click to expand...
Click to collapse
How did i bricked my phone. Simple. First of all no desrepect for any dev, since i did this by my one. What i did was tried to flash unofficial twrp and fastboot set slot b did not worked. Once i reboot it got stuck on a bootloop. i couldn't flash xiaomi stock fastboot zip due to "critical partition flashing is not allowed" and before you asked yes my A2 was bootloader unlocked one. Unlock critical partition thing is not for our devices like for pixel series as far as i know. So simply i couldn't fix it, neither the software guy from my purchased center. That's why im afraid. I know you are besy, but highly appreciate if you can write down how to go back to stock guideline as well. Thanks again :good:

crazykas said:
How did i bricked my phone. Simple. First of all no desrepect for any dev, since i did this by my one. What i did was tried to flash unofficial twrp and fastboot set slot b did not worked. Once i reboot it got stuck on a bootloop. i couldn't flash xiaomi stock fastboot zip due to "critical partition flashing is not allowed" and before you asked yes my A2 was bootloader unlocked one. Unlock critical partition thing is not for our devices like for pixel series as far as i know. So simply i couldn't fix it, neither the software guy from my purchased center. That's why im afraid. I know you are besy, but highly appreciate if you can write down how to go back to stock guideline as well. Thanks again :good:
Click to expand...
Click to collapse
did you try fastboot set slot a, and then reboot? that should have fixed it.
As for a guide for going back to stock from Pie.
LIke i said.
dowload fastboot firmware from here.
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
extract the zip file. open images folder. grab system.img. put it in fasboot folder. and in step where we flash pie gsi image, flash the system.img you just pasted in fastboot folder.

munchy_cool said:
did you try fastboot set slot a, and then reboot? that should have fixed it.
As for a guide for going back to stock from Pie.
LIke i said.
dowload fastboot firmware from here.
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
extract the zip file. open images folder. grab system.img. put it in fasboot folder. and in step where we flash pie gsi image, flash the system.img you just pasted in fastboot folder.
Click to expand...
Click to collapse
Thanks man. Will try at night. Can't wait ????

MTP doesn't work.

Streect said:
MTP doesn't work.
Click to expand...
Click to collapse
It works. Enable it in Developer Tools.

Thank you very much for sharing, i will try it soon
---------- Post added at 10:02 AM ---------- Previous post was at 09:39 AM ----------
No problem on Linux? Simple adb /fastboot installed on Ubuntu
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
Again: which one img do you choose, aonly or ab?

HTCDevil said:
Thank you very much for sharing, i will try it soon
---------- Post added at 10:02 AM ---------- Previous post was at 09:39 AM ----------
No problem on Linux? Simple adb /fastboot installed on Ubuntu
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
Again: which one img do you choose, aonly or ab?
Click to expand...
Click to collapse
did you read the OP at all? it's mentioned step 1 which file you need.

How to install Gapps?

munchy_cool said:
[...]
Click to expand...
Click to collapse
Two things:
1) Thank you for the guide! You got yourself another subscriber on YouTube This is my first device that supports Treble. From your experience, how stable are GSI ROMs?
2) Update your signature

speedunderx said:
How to install Gapps?
Click to expand...
Click to collapse
i didnt get time to check that. may have to install some apks. maybe the same apks which are needed for amazon fire tablets to get play store working.

soulicro said:
Two things:
1) Thank you for the guide! You got yourself another subscriber on YouTube This is my first device that supports Treble. From your experience, how stable are GSI ROMs?
2) Update your signature
Click to expand...
Click to collapse
gsi's are pretty stable, check xda thread for bugs. will update signature soon

munchy_cool said:
did you read the OP at all? it's mentioned step 1 which file you need.
Click to expand...
Click to collapse
About my last question ok, i see on YouTube it is ab. Other question not answered yet. Thanks.

HTCDevil said:
About my last question ok, i see on YouTube it is ab. Other question not answered yet. Let him answer by itself. Thanks.
Click to expand...
Click to collapse
no problem on Linux.

munchy_cool said:
no problem on Linux.
Click to expand...
Click to collapse
Great, hope gapps work and camera is mostly Stable. Thank you

HTCDevil said:
Great, hope gapps work and camera is mostly Stable. Thank you
Click to expand...
Click to collapse
it does not have gapps. you may have to manually install some apks. try with apks needed for Play Store on amazon fire tablets.
if you figure those out, please let us know.

[ROOT][TB-X505X] Rooting Lenovo Tab M10 TB-X505X

This guide is now obsolete. Please check my new guide. It has a custom recovery for this device as well as a rooting guide. Refer to this guide only for installing adb and unlocking bootloader.
This rooting guide is for the Lenovo Tab M10 X505X only.
I plan to work on a custom recovery for this tab as well and probably a custom rom in the future.
So please consider donating so that I can keep up the work.
Donations
Google Pay
This will work only on the version "TB-X505X_S001037_200718_ROW". Check it in the Settings > System > About Tablet > Build Number. If it is the newer "X505X_S001038_200819_ROW", do a factory reset and make sure it is the "TB-X505X_S001037_200718_ROW" before proceeding.
Once a custom recovery is made, OTA updates can be applied without losing root. So do not update the tablet until a custom recovery is developed for the device. I plan to develop a custom recovery for it as soon as possible, so please support me.
Anything that goes wrong in this tutorial is not my responsibilty. Proceed at your own risk.
Downloads
patched_boot.img
Step 1. ADB and Fastboot Installation [If adb and fastboot are already installed, skip to Step 2]1. Download the platform tools for your OS from this link.
2. Extract the zip file and place the contents in a folder "platform-tools".
3. To confirm if adb is working, open a command prompt "platform-tools" and run the following command.
Code:
adb version
If it returns the adb version, its done.
Step 2. Unlocking BootloaderWe have to unlock the bootloader inorder to root the device.
Warning: Unlocking bootloader wipes data on the device. It is recommended to backup your data. Proceed at your own risk.
1. Now in the tab, goto Settings > System > About Tablet. Multiple tap the "Build Number" till the developer options are enabled.
2. Goto the developer options and turn on the "OEM unlocking".​3. Power off the device.
4. Turn it on by holding Power Button + Volume Down. Once the screen turns on. leave the power button but continue holding the Volume Down button until the fastboot mode is shown.
5. Now open a command prompt in "platform-tools" and now run the following command:
Code:
fastboot oem unlock-go
Your Bootloader is now succesfully unlocked.​Step 3. RootingNow to root the tab, download the "patched_boot.img" from the top of this post. Copy the file to the "platform-tools" folder.
Make sure the tab is still in the fastboot mode. Otherwise go back into the fastboot mode as instructed before.
Now run the following command:
Code:
fastboot flash boot patched_boot.img
Congratulations, you have rooted your tab.:highfive:
To complete the process, run the following command.
Code:
fastboot reboot
Once the tab turns on, goto this link and download the latest version of Magisk apk and install it. It is required to control the root privileges for other apps.​That's all. You now have a rooted tab.:victory:
If this helped you, hit the thanks button.
And keep tuned for new stuff that are to come for this device.

Thanks for this thread for the TB-X505X.
Shamil Niyas said:
I plan to work on a custom recovery for this tab as well...
I plan to develop a custom recovery for it as soon as possible...
Click to expand...
Click to collapse
Have a look at this post for a TWRP that works with the TB-X505F. It might work for the TB-X505X, provided the X505X uses the SDA429 soc. That version of TWRP is unofficial and does not decrypt the data partition.
If the X505F version of TWRP works for you, then you won't need to patch the boot image - you can just install the Magisk update.zip in TWRP. This saves you from having to release a new patched boot image every time there's an OTA.
Shamil Niyas said:
Once a custom recovery is made, OTA updates can be applied without losing root.
Click to expand...
Click to collapse
With the TB-X505F/L, TB-X605F/L and TB-X705F/L we've found that you need to uninstall Magisk to apply OTAs. This is because Lenovo's OTA updater scripts verify you have unmodified boot, system, vendor and firmware partitions. So make sure you backup these partitions as stock.

Yahoo Mike said:
Thanks for this thread for the TB-X505X.
Have a look at this post for a TWRP that works with the TB-X505F. It might work for the TB-X505X, provided the X505X uses the SDA429 soc. That version of TWRP is unofficial and does not decrypt the data partition.
If the X505F version of TWRP works for you, then you won't need to patch the boot image - you can just install the Magisk update.zip in TWRP. This saves you from having to release a new patched boot image every time there's an OTA.
With the TB-X505F/L, TB-X605F/L and TB-X705F/L we've found that you need to uninstall Magisk to apply OTAs. This is because Lenovo's OTA updater scripts verify you have unmodified boot, system, vendor and firmware partitions. So make sure you backup these partitions as stock.
Click to expand...
Click to collapse
I gave a look at the TWRP image. Unfortunately, X505X does not boot into the recovery image. It would have been great if it worked. I guess it is because of the different processor, as you mentioned.
It is the same for X505X as well. OTA cannot be applied without uninstalling Magisk. So I guess OTAs are a no-go until a custom recovery is developed. The latest update is also just a boot image patch. So there is no way to use magisk on that.
Thanks for the advice.

But i updated to android 10 S001122_200915
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.

Excuse me if this was asked before. Is there a rooting method for TB-X505F? It's the model that is sold in Europe. I'm thinking of buying this.

ShAd0W_z0nE said:
Excuse me if this was asked before. Is there a rooting method for TB-X505F? It's the model that is sold in Europe. I'm thinking of buying this.
Click to expand...
Click to collapse
This post has instructions for the X505F, under "How do I root my device?".

cYBER~VeTeRaN said:
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Click to expand...
Click to collapse
I'm currently working on the twrp for this device. Once it is finished it should be able to root without downgrading.

cYBER~VeTeRaN said:
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Click to expand...
Click to collapse
Hello cYBER-VeTeRaN,
I have compiled a TWRP for X505X. You can find it here. Install the magisk zip from TWRP and you should be able to root your tablet regardless of the verison.:victory:
Hit the thanks button.

Shamil Niyas said:
Hello cYBER-VeTeRaN,
I have compiled a TWRP for X505X. You can find it here. Install the magisk zip from TWRP and you should be able to root your tablet regardless of the verison.:victory:
Hit the thanks button.
Click to expand...
Click to collapse
Thanks sir. Great job and I'm also from kerala, nice to meet you

Good afternoon.
I have this version ( Build number TB-X505F_S001142_210804 ROW ) of Android on my Lenovo TB X505F.
Can you tell me if this method works with this version of Android?

jsvenancio said:
Good afternoon.
I have this version ( Build number TB-X505F_S001142_210804 ROW ) of Android on my Lenovo TB X505F.
Can you tell me if this method works with this version of Android?
Click to expand...
Click to collapse
[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD
This version of TWRP works on the Lenovo TB-X505F (wifi). For the TB-X505X, see this thread. For the TB-X605F/L, see this thread. For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC. #include...
forum.xda-developers.com
Twrp for x505f

Umm where it says to download my os there is no link provided. Same goes for fastbook it takes me tomyour old guide and then there is no link where a person would think they would find it. Am I stupid and missing something or all the links broke/missing ?
I'd prefer to be stupid.... Just saying..

tombaldwin6 said:
Umm where it says to download my os there is no link provided. Same goes for fastbook it takes me tomyour old guide and then there is no link where a person would think they would find it. Am I stupid and missing something or all the links broke/missing ?
I'd prefer to be stupid.... Just saying..
Click to expand...
Click to collapse
Check his new guide, just flash twrp and flash magisk from there

Guys, I am stuck in a Bootloop after i tried that with the patched boot img. Can someone help?

Tamiiiiiii812 said:
Guys, I am stuck in a Bootloop after i tried that with the patched boot img. Can someone help?
Click to expand...
Click to collapse
Download rom, extract boot.img from it and flash it. Makw sure you download the right version.
You can find the rom here:- https://mirrors.lolinet.com/firmware/lenovo/Tab_M10_HD/TB-X505X/

cYBER~VeTeRaN said:
Download rom, extract boot.img from it and flash it. Makw sure you download the right version.
You can find the rom here:- https://mirrors.lolinet.com/firmware/lenovo/Tab_M10_HD/TB-X505X/
Click to expand...
Click to collapse
OMG IT WORKED. Thank you.

Thanks bro. I found what I needed..

Shamil Niyas said:
1. Download the platform tools for your OS from this link.
Click to expand...
Click to collapse
yeah, where is the link?

Booe said:
yeah, where is the link?
Click to expand...
Click to collapse
Just search for platform tools and download it.

Guys, i tried the above mentioned method but my device is showing (can,t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device) after performing a factory data reset the device reboots and the welcome menu shows up after 15-30 seconds the device automatically shut down and again shows the same message (can,t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored onnn this device). this goes again and again......

[GUIDE] OOS 13 ON KB2003

Hi, follow this guide at your risk.
This guide makes you install the KB2005 update on the KB2003 (no visible difference to me, VoLTE working 5g not tested)
#1
Follow this link: https://mega.nz/folder/qsxzXAIb#Hz1R8oc2m78rRJw-pAqX0w and download all the files in the folder
#2
Open and read the README.txt
#3
Profit.
Sorry for being so short but I have things to do.

Alex261099 said:
Hi, follow this guide at your risk.
This guide makes you install the KB2005 update on the KB2003 (no visible difference to me, VoLTE working 5g not tested)
#1
Follow this link: https://mega.nz/folder/qsxzXAIb#Hz1R8oc2m78rRJw-pAqX0w and download all the files in the folder
#2
Open and read the README.txt
#3
Profit.
Sorry for being so short but I have things to do.
Click to expand...
Click to collapse
Can you please share the link from the google drive?

hll.mltyl said:
Can you please share the link from the google drive?
Click to expand...
Click to collapse
I have no more space on gdrive... Sorry

To keep root just install Magisk to inactive slot?
Which version of Magisk should I use, Stable or Canary?

epr said:
To keep root just install Magisk to inactive slot?
Which version of Magisk should I use, Stable or Canary?
Click to expand...
Click to collapse
I'm sorry but i don't know, i'm not using magisk...

hll.mltyl said:
Can you please share the link from the google drive?
Click to expand...
Click to collapse
Direct link from google servers.
https://android.googleapis.com/packages/ota-api/package/e61f1cf7c6a55e531113091deadfb7acb96901da.zip
You can also adb sideload the package with orangefox recovery.
Just boot orangefox with fastboot ( fastboot boot orangefox.img ) and adb sideload the update.
For root I just allowed the phone to boot one time after updating then went back to orangefox and adb sideload magisk.apk.zip

Can I local install ?

kenbrownstone said:
Can I local install ?
Click to expand...
Click to collapse
yes, using my method. No root no twrp no magisk from stock

One last question, I'm running eu os but on TMobile 8t . Is there a issue if I use?

EU update is up on oxygen updater now fyi.

tay200k said:
EU update is up on oxygen updater now fyi.
Click to expand...
Click to collapse
My keeps saying in local can't verify and won't work

Oxygen updater on okay store to have the kb2003 update

Question Magisk direct install not visible

Hello together
I installed A13 today, after I patched the stock.img and flashed it "fastboot boot file.img" after restart I see that my iOS Emojis are back but I don't see the option direct install in Magisk. I just see "Choose file and patch"..
Any ideas what I could do?

paper88 said:
Hello together
I installed A13 today, after I patched the stock.img and flashed it "fastboot boot file.img" after restart I see that my iOS Emojis are back but I don't see the option direct install in Magisk. I just see "Choose file and patch"..
Any ideas what I could do?
Click to expand...
Click to collapse
You could try searching "direct install not visible in Magisk".

paper88 said:
Hello together
I installed A13 today, after I patched the stock.img and flashed it "fastboot boot file.img" after restart I see that my iOS Emojis are back but I don't see the option direct install in Magisk. I just see "Choose file and patch"..
Any ideas what I could do?
Click to expand...
Click to collapse
Are you sure you booted the right boot image?

Try with this one:
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
I think the magisk patched 1.5.2 is not really patched or there are some checks in place that allow only certain imgs to work
If it still does not work, download the stock boot, patch it with magisk select that boot img, fastboot, boot the new patched img

TheNewHEROBRINE said:
Are you sure you booted the right boot image?
Click to expand...
Click to collapse
I tried to boot the images from here:
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
I tried multiple boot images

AnotherM1m said:
Try with this one:
Click to expand...
Click to collapse
You didnt attach something

paper88 said:
You didnt attach something
Click to expand...
Click to collapse
shift enter is a special combination here on xda i've edited my previous message

AnotherM1m said:
shift enter is a special combination here on xda i've edited my previous message
Click to expand...
Click to collapse
Still no success. I just think I broke something while I did the OTA and I just need to wait till the next update. I restored first the images and installed it over OTA, after restart the update was not installed but Magisk deinstalled. Then I installed it again and restarted it and wanted to flash boot.img, but since then its not working anymore

what command on the terminal are you using for boot.img?

AnotherM1m said:
what command on the terminal are you using for boot.img?
Click to expand...
Click to collapse
Tried fastboot boot img and fastboot flash boot img

paper88 said:
I tried to boot the images from here:
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
Nothing Phone (1) [ ROM ][ OTA ][ Nothing OS ] Repo of Nothing OS
Note: This is not a support thread for issues you may have with Nothing OS ROMs. If you need help installing or updating, feel free to ask here. If you have any other issues, please ask in another thread. Regarding problems with the Phone(1)...
forum.xda-developers.com
I tried multiple boot images
Click to expand...
Click to collapse
I mean are you sure you booted the patched image and not the stock one? Are you patching the booting yourself?

paper88 said:
Tried fastboot boot img and fastboot flash boot img
Click to expand...
Click to collapse
Are you on a global device or eea?
Have you tried patching the img yourself?

TheNewHEROBRINE said:
I mean are you sure you booted the patched image and not the stock one? Are you patching the booting yourself?
Click to expand...
Click to collapse
AnotherM1m said:
Are you on a global device or eea?
Have you tried patching the img yourself?
Click to expand...
Click to collapse
I tried the stock img and patched by myself and also tried to boot the patched image from AnotherM1m

paper88 said:
I tried the stock img and patched by myself and also tried to boot the patched image from AnotherM1m
Click to expand...
Click to collapse
Do you know if you have an european device or a global one?
is your device's name Spacewar or SpacewarEEA?

AnotherM1m said:
Do you know if you have an european device or a global one?
is your device's name Spacewar or SpacewarEEA?
Click to expand...
Click to collapse
Its Spacewar EEA

paper88 said:
Its Spacewar EEA
Click to expand...
Click to collapse
Ok, the problem is that we just discovered 1.5.2 is not unified at all.
Those images are not working because they are dumped from a global device.
You need a modified eea image which i cannot find for now...

I did root my 1.5.2 EEA without issues with a self-patched 1.5.2 Stock from https://forum.xda-developers.com/t/...g-os-repo-of-nothing-os.4464039/post-87101175

Since you are very fortunate that this device has usable EDL mode, you can always dump your boot image on any firmware you're by using the EDL tool made by @mark332. (However, I suggest you try following @dedors suggestion first).

paper88 said:
Hello together
I installed A13 today, after I patched the stock.img and flashed it "fastboot boot file.img" after restart I see that my iOS Emojis are back but I don't see the option direct install in Magisk. I just see "Choose file and patch"..
Any ideas what I could do?
Click to expand...
Click to collapse
Perhaps you are simply missing a step, here are Magisk's official Installation Instructions. They give step-by-step instructions on patching.

ethical_haquer said:
Perhaps you are simply missing a step, here are Magisk's official Installation Instructions. They give step-by-step instructions on patching.
Click to expand...
Click to collapse
What did I do wrong? I do it like this since 12 months on oneplus and nothing