Develop Bugs

[HOWTO] ADB for Macintosh Users Only for complete beginners!

I AM NOT RESPONSIBLE FOR ANY PROBLEMS YOU CAUSE!
So you are stumbling around XDA and you really want some kind of app or something, but you think you cant because you have a Mac, well I am here to tell you wrong.
The biggest and most used mistake for mac users when trying to use ADB is this:
HTML:
Inas-iMac:~ Hans$ /AndroidSDk/tools
-bash: /AndroidSDk/tools: is a directory
Inas-iMac:~ Hans$
Well this is how you do it!
Watch this!
http://www.youtube.com/watch?v=GLAMG4xU_lE
To make your phone go into debug mode go to settings/applications/development and check debug
DO NOT MOUNT PHONE! Just let it be
I did not go to deep into the process because this is made for complete beginners!

Why not follow the official SDK install instructions and add the path to bash_profile..
developer.android.com/sdk/installing.html#Installing
In my opinion that's not too hard for a newbie.. (i managed to do that) And after doing that you don't need to change directories with cd command, you can just type adb whatevercommand from your home dir which is the default location when you open the terminal.

Drag and drop is a little a fail.... one can add "alias" (linux can do it, probably mac too)
Little How-to:
Code:
$ nano ./bashrc
add and adapt the following line to bashrc:
Code:
alias adb="/home/carbonyle/android-sdk-linux_86/tools/adb"
now you just have to type "adb" from a terminal emulator to run it, eg:
Code:
$ adb shell
# reboot recovery
or
Code:
adb install ./Download/myFavortiteApp.apk
and so on...
ps: we don't need to "adb remount" at worst we can just "adb kill-server" then "adb start-server" if the device is not accessible

I'm lost. Need rooting help.

I'm lost as hell. I found this thread:
http://www.androidpolice.com/2010/06...credible-next/
I did the unrevoked thing and I see this icon called SuperUser Permissions in my app list.
Am I able to proceed and fully root or do I have to re-do the root with the Toast method? This looks too complicated and by the way I tried the ./adb thing on my mac and I get errors saying "No such file or directory".

gqstatus0685 said:
This looks too complicated and by the way I tried the ./adb thing on my mac and I get errors saying "No such file or directory".
Click to expand...
Click to collapse
adb isn't installed on a Mac out of the box; You'll need to go download the Android SDK. Untar it somewhere (I put it in ~/), then open a term, do:
Code:
cents-macbook-pro:~ $ cd android-sdk-mac_86/tools/
cents-macbook-pro:~/android-sdk-mac_86/tools $ ./adb

CentroniX said:
adb isn't installed on a Mac out of the box; You'll need to go download the Android SDK. Untar it somewhere (I put it in ~/), then open a term, do:
Code:
cents-macbook-pro:~ $ cd android-sdk-mac_86/tools/
cents-macbook-pro:~/android-sdk-mac_86/tools $ ./adb
Click to expand...
Click to collapse
Massive Brain Freeze.. What do you mean by "(I put it in ~/)"?
I downloaded the Android SDK already. I understand what terminal is so when I download the Android SDK where do I place it?
Am I pointing terminal to the directory? Android SDK is currently in a folder on my desktop.

gqstatus0685 said:
Massive Brain Freeze.. What do you mean by "(I put it in ~/)"?
I downloaded the Android SDK already. I understand what terminal is so when I download the Android SDK where do I place it?
Am I pointing terminal to the directory? Android SDK is currently in a folder on my desktop.
Click to expand...
Click to collapse
~ in most flavors of Unix/Linux is short for your home directory. In MacOS, ~ is /Users/<username>. *nix pro-tip:
Code:
cents-macbook-pro:~ $ echo ~
/Users/cent
So in my case, ~ is short for /Users/cent.
If it's on your desktop, open a terminal and type:
Code:
cd ~/Desktop/android-sdk-mac_86/tools
-OR-
Code:
cd /Users/cent/Desktop/android-sdk-mac_86/tools
And then you can proceed to issue your adb commands. Just remember to prefix it with "./", which tells MacOS to look in the current directory for the adb command.
Code:
cents-macbook-pro:~/android-sdk-mac_86/tools $ ./adb devices
List of devices attached
HT05RHL1XXXX device

Ok. I think I'm just going to pay someone to do this for me. I'm getting a migraine.
So I'm basically typing the below:
~/android-sdk-mac_86/tools $ ./adb devices (Do I type this in one line)
List of devices attached
HT05RHL1XXXX device
I ran the thing and it doesn't show my phone listed.

I've got the time, if you have the money!
1. Make sure USB debugging is enabled. On your phone, go to Settings -> Applications -> Development, and make sure "USB debugging" is checked.
2. Make sure your USB cable is connected to your phone and computer.
3. Open a terminal
4. Type "cd ~/Desktop/android-sdk-mac_86/tools" and press enter.
5. Type "./adb devices" and press enter.
If it lists your device, you're then good to go to start following the rooting instructions!

You're the best dude. It was the USB debugging that was giving me the problem.

Good deal man, glad you got that part worked out! Have fun getting your root on!

this is the easiest way to do it....it worked for me
http://forum.xda-developers.com/showthread.php?t=701152

Do i have to keep dubugging mode on or can I turn it off before I root it. I did the command:
"cd ~/Desktop/android-sdk-mac_86/tools"
and then
adb push PC36IMG.zip /sdcard (Doesn't do anything. I tried without the space and some stuff popped up. Can I just manually put it on my SDcard?

gqstatus0685 said:
Do i have to keep dubugging mode on or can I turn it off before I root it. I did the command:
"cd ~/Desktop/android-sdk-mac_86/tools"
and then
adb push PC36IMG.zip /sdcard (Doesn't do anything. I tried without the space and some stuff popped up. Can I just manually put it on my SDcard?
Click to expand...
Click to collapse
Debugging mode needs to stay on if you want to use adb. You can turn it off once you root, but it won't hurt to leave it on.
The push command should tell you the number of bytes transfered. You need to make sure that the file you are pushing is in the current directory you're in (tools), or manually enter the path, like "./adb push ~/Downloads/PC36IMG.zip /sdcard"
But yes, you can mount the card as a disk drive and copy the file there in Finder.

[Q] help with fastboot?

i am trying to install a boot animation, but i can't remember the sequence or how to navigate to the tools folder with my command prompt. 2 weeks ago i managed to change my splash screen, but im still kinda new with this and forgot what i did. lol. i've tried searching this forum, but nothing ive found so far helps. could someone point me in a better direction? thanks!

open command prompt either by the shift right click method or using the cmd prompt... if the shift right click method doesn't work (it doesn't for me) then just do it the long way
type:
cd android-sdk-windows
cd tools
then type the commands of what you're trying to fastboot

surrealmethod said:
open command prompt either by the shift right click method or using the cmd prompt... if the shift right click method doesn't work (it doesn't for me) then just do it the long way
type:
cd android-sdk-windows
cd tools
then type the commands of what you're trying to fastboot
Click to expand...
Click to collapse
Not quite.
Code:
cd c:\android-sdk-windows\tools
That will put you in the ADB directory, assuming you have the android-sdk-windows folder on the root of your C: drive, not inside another folder (mine downloaded inside another folder, I just pulled it out and put it so it fits the above structure). Then pass the commands.
Power user tip: Just type in "cd c:\and" and then hit Tab. It will complete the rest of the folder name, then you can hit "\t" and hit Tab again to complete the next part. Tab is an auto-complete feature. I never type path names anymore.

[GUIDE] Using ADB & FASTBOOT in OSX / Mac

Hi,
I thought I'd add this here because I've recently starting using OSX after building my own hackintosh out of PC parts. I got very fed up with Windows and the need for drivers all over the shop so I'm moved over now.
I've also just got into flashing my HTC Desire and it was made very easy by lots of the guys here. One thing that will always be useful when rooting and flashing your phone is ADB. There are lots of guides out there for ADB on Windows but I wanted to run in natively in OSX.
After a lot of research and a few failed attempts .... I've now worked out how to run ADB in OSX.
What you will need:
A Mac
USB cable
Android SDK for OSX- http://developer.android.com/sdk/index.html
At the time of writing this the version was "android-sdk_r08-mac_86" so please have a look at the above link and let me know if you can't find that same version.
So download the zip file and I would extract it to a folder where you are happy to keep it such as within your user home folder i.e. Macintosh HD/Users/{Your User Name} and for my mac it is Users/siedkins which is how I have my OSX set up.
Then open then still in Finder, open "android-sdk-mac_86" then "tools".
Now launch Terminal - ⌘ + space then type Terminal or Applications>Utilities>Terminal
Now drag and drop the file called "android" in the "tools" folder into your terminal window and you should see something like:
/Users/siedkins/android-sdk-mac_86/tools/android
Then hit enter - this should load Android SDK
Next go to Available Packages on the left and Android Repository > Android SDK Platform-tools, revision 1 -tick the box and hit "Install Selected"
It should download and install the Platform Tools which includes ADB !!!!
Now quit Android SDK after it has downloaded and go back into Finder. Now you should see a new folder "platform-tools" in the "android-sdk-mac_86" folder. Open that and you can now see a file called adb.
Now .... I am going to show you how to make your life a lot easier in Terminal to run ADB without having to navigate to the folder every time you want to launch it.
Go back to your Terminal window and type (or copy & paste):
Code:
cd ~
The screen should then look like
NAME_OF_YOUR_MACHINE:~ USERNAME$
For me I have:
Mac-Pro:~ siedkins$
Next, type
Code:
touch .bash_profile
to create your new bash / path file
Next, type
Code:
open -e .bash_profile
to open it in TextEdit.
Now into Text Edit please copy:
Code:
export PATH=${PATH}:
Then go into Finder and navigate your your "android-sdk-mac_86" folder. Then click on the "platform-tools" folder and drag and drop this into TextEdit at the end of the code above that you copied. Mine looks like:
export PATH=${PATH}:/Users/siedkins/android-sdk-mac_86/platform-tools/
Yours should look like:
export PATH=${PATH}:insert your path to the "platform-tools" folder in your Android SDK here
All you need is that one line. Then Save and exit TextEdit and then very importantly QUIT TERMINAL.
***** If you have issues being able to save the file at all then please jump to the bottom of the post*****
Now ........ to turn on USB Debugging in your handset Settings > Applications > Development > USB Debugging - ticked and also go to Settings > Connect to PC > Default connection type > Charge Only and also UNTICK "Ask me ..." there also. You can always go back here and change these settings back.
Now plug in your phone to a USB port. I noticed that if I plugged my phone into one of the standard USB ports on the front of my machine I couldn't see the phone further down the line and if I plugged it into a powered USB port on the front (I have an "akasa AK-ICR-08" which has a powered connector behind the 5 USB ports. But you guys will probably be using a MacBook or MacPro and there shouldn't be any issues with the power to your USB ports.
Now to launch ADB - re-open terminal (remember that you had quit it - very important!) then type in:
Code:
adb devices
And you should see:
List of devices attached
HXXXXXXXXXX device
where XXXXXXXX is your unique phone ID.
Now you can run all of your favourite ADB commands straight by typing:
adb shell
etc straight into Terminal. I won't go into that here as there are plenty of guides about what to do with ADB once it's installed!
Now you have ADB setup on your Mac and can run it without the need for installing HTC Sync - un-installing it - loading some modified drivers over the top !!!!
It all just works !!!!!!
Please drop me a line if you have any queries about this !
******************
If you are have user account issues such as Terminal or TextEdit says that you can't do anything then try adding "sudo" to the front of your terminal command as this will allow you to execute the account as a superuser or root user for OSX! ROOT!!! Note that you will have to enter your password to enable the superuser access rights and you won't see anything as you type in your password.
i.e. try:
Code:
sudo touch .bash_profile
then
Code:
sudo /Applications/TextEdit.app/Contents/MacOS/TextEdit .bash_profile
(slight change in the coding here to ensure that TextEdit opens
Or you could do:
Code:
sudo pico .bash_profile
This will open up the Pico text editor instead of TextEdit. Here you will have to type out all of the text then you press "ctrl+x" to exit and then you can save on the next screen. To check that has worked you can then open the file in terminal again and check it with the normal command:
Code:
open -e .bash_profile
******************
Please see post #37 for How To Use ADB Over WIRELESS !!!!
************************************************************************
EDIT - 27th JAN 2010
FastBoot
I've now found you all a precompiled version of Fast Boot:
http://developer.htc.com/adp.html
Please download and unzip the precompiled version for OSX to your "SDK/platform-tools" folder.
Rename the unzipped file from "fastboot-mac" just to "fastboot". You need to fix the permissions of the fastboot file using CHMOD in Terminal.
In Terminal navigate to your "SDK/platform-tools" folder and then type:
Code:
ls
You should see all of the files in your "platform-tools" folder such as adb, aapt, fastboot, etc.
Then type:
Code:
chmod 777 fastboot
PLEASE NOTE THAT I AM ASSUMING THAT YOU HAVE CHANGED THE FILE NAME ABOVE !
Now with the permissions fixed you should be able to run fastboot.
Connect your phone via USB and set to "charging only". Then turn off your phone and leave the USB in. Then hold the back key and then turn your phone on again. You will have a white screen with 3 skateboarding androids on.
Now in Terminal type:
Code:
fastboot devices
And you should see your unqiue phone ID! (Note that you have to be at that white screen with the skateboarders for the "fastboot devices" code to run!
Now you have a fully working fastboot !!!
Sorry this explanation is a bit short - I did write out a longer one but my browser crashed and I lost it all. However if you cannot follow the above then I think it's maybe best that you don't use fastboot as you could seriously brick your phone.
NOTE - I HAVE NEVER USED FASTBOOT TO FLASH A RADIO OR PHONE SO I PROBABLY WON'T BE ABLE TO HELP IF YOU GET ERRORS IN USING FASTBOOT OR FLASHING YOUR DEVICE ! The above information is how to shortcut the navigation to the folder. Please don't blame me if you break the recovery image of your phone!

Thanks for such a thorough step by step guide. But Im having a problem I followed the directions and at the last step I get "permission denied". Any tips for me would be truly appreciated. Thanks

dhoshman said:
Thanks for such a thorough step by step guide. But Im having a problem I followed the directions and at the last step I get "permission denied". Any tips for me would be truly appreciated. Thanks
Click to expand...
Click to collapse
which last step ?

dhoshman said:
Thanks for such a thorough step by step guide. But Im having a problem I followed the directions and at the last step I get "permission denied". Any tips for me would be truly appreciated. Thanks
Click to expand...
Click to collapse
What version of MacOS? Also are you sure your device is properly rooted? I'm assuming you are getting the error when typing "adb devices"?
EDIT: That's what I get for being distracted while typing this.. ;-)

The easiest way to get the sdk is by using homebrew, which is an amazingly useful tool. https://github.com/mxcl/homebrew
Code:
brew install android-sdk
It doesn't add adb to your path however, you have to do that manually by adding /usr/local/Cellar/android-sdk/r8/platform-tools to your path.
Hope that makes it a little bit easier.

I found that on my mac using terminal I have to always start the adb commands with a ./ otherwise it wouldn't work right. This might be common knowledge for some, but I'm a terminal newbie
So, for example:
./adb devices

Thanks for the walk through
This work great. I put the the SDK folder on the root of Macintosh HD and renamed it to AndroidSDK. Then in the .bash_profile my path was /AndroidSDK/platform-tools/ . I then made a backup of my SD card with adb pull from /mnt/sdcard to my local machine.

mun-key said:
I found that on my mac using terminal I have to always start the adb commands with a ./ otherwise it wouldn't work right. This might be common knowledge for some, but I'm a terminal newbie
So, for example:
./adb devices
Click to expand...
Click to collapse
Kind of weird. To me that would mean that you're path variable isn't setup correctly. Usually the ./ before a command means to run the command from the current directory and ignore the path variable.

It doesn't even have to be this complicated. Download the sdk, whatever files you want to push to your phone put it in the same folder. Then do the commands (./adb push). Simple.

Great and easy tutorial! Got it working in 5min ^_^

madj42 said:
Kind of weird. To me that would mean that you're path variable isn't setup correctly. Usually the ./ before a command means to run the command from the current directory and ignore the path variable.
Click to expand...
Click to collapse
Ok - that makes sense now. And reading Krisrk's reply, that's exactly how I did it.
On my device I only needed to push a single file. Don't really need adb anymore. Your post was like 12-hours too late for me though. I spent 3 hours trying to figure out why it wouldn't work, then saw the ./ in a youtube video. After that I was rooted with a new rom in minutes
thanks for all the great info guys

Just wanted to thank you! I already had ADB working on my Mac OSX but didn't have the "environment variables" in the .bash_profile. So now I can just use adb commands directly without going into the finder and find the adb!
Also, kudos for the very detailed guide with your own examples, that reads very well!

Thanks for the comments guys.
I know that you can navigate to the SDK folder and just run it from there but I thought that people might like the above guide to do the shortcut once and then never have to jump around folders again in terminal which is a bit of a pain. Plus my method removes the need for the "./" prefix.
anyways I'm easy I'm sure that everyone will have their own preferred method if you already use adb on OSX

i cannot get beyond the command:
touch .bash_profile
the terminal returns permission denied. what do i need to add or what am i doing wrong?

What type of user account do you have set up in OSX?
System Prefs > Accounts
Also what about trying the following in Terminal
Code:
sudo touch .bash_profile
And then enter the password for your user profile?
Any better?

Thanks for this!!!!!
Nobody ever shows macs love.
Sent From My HTC Evo 4G Using Tapa Talk Pro!

siedkins said:
What type of user account do you have set up in OSX?
System Prefs > Accounts
Also what about trying the following in Terminal
Code:
sudo touch .bash_profile
And then enter the password for your user profile?
Any better?
Click to expand...
Click to collapse
it popped up and asked my password, then it said i entered the wrong one and i never was asked this again. this is incredibly frustrating as i cannot even get it to work in windows
edit: ok got to the part where i bring up text edit, but it will not let me save. states i do not have permission to save. is there a way i can turn off this password crap for the time being? all i want to do is push files to my phone, i can't even get this far

Ok...
I'm trying not to look stupid, but for gods sake, im stuck at the first command. I copy paste cd~ and nothing happens. press enter nothing. I've been reading up on terminal and i still feel quite stupid considering how im stuck on step one
edit: got it! I got lost going back into the same terminal and not closing the android sdk window. there fore I was still in the sdk and not telling the computer anything. a dur. Opening a new terminal and doing all of the steps did the trick. Thanks for this btw!

thanks for the detailed guide. i've been looking all over the web for a guide to setup adb for MAC. followed the steps here and now, i'm able to use ADB on my macbook. YAY!!

monstereo said:
thanks for the detailed guide. i've been looking all over the web for a guide to setup adb for MAC. followed the steps here and now, i'm able to use ADB on my macbook. YAY!!
Click to expand...
Click to collapse
Hey just a random note, nice prof pic stig ftw

[root] for those have unlocked bootloader

May you install Magisk Manager and export the "patched" kernel, and flash the patched kernel through fastboot?

Hi mingkee.
This works whit G3311 confirmed. Build: 43.0.A.6.49 Android 7.0 Baseband MOLY.LR9.W1444.MD.LWTG.MP.V166..5, Kernel 3.18.35+
Kernel is for G3313 magisk patch.
Everything works with this for G3311 as I've tested. Try it at you're own risk.
In linux in (debain, Ubuntu, Linux Mint and all) you need tools
Terminal "sudo apt-get install android-tools-adb android-tools-fastboot"
1. Unlock bootloader https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code. Get the code
2. Go to settings/ about phone/ build number/ click 7 times. Go back to settings. Developer options/ USB debuggning ON. OEM unlock ON. And try "adb devices" in terminal GNU/Linux. Should popup a allow PC on the phone" tranfer files is necessary "MTP", on the phone.
3. In terminal "adb reboot bootloader" this is where "allow access to computer" if it's haven't appeared allow on the phone.
4. In terminal "fastboot oem unlock x0(the code). no space. Don't know why x0 doesn't exist in the code. Don't know why. It's my first Sony with the openness they got now (thank god for Lund, sweden and Jolla, Finland). But it seems pretty easy to unlock. Honor 8 have closed bootloader unlock since 8 Month. So be at ease. And maybe save you're unlock code. But it doesn't seems like you need it.
5. I did it this way.
5/1 Download https://serv8.asuscomm.com/owncloud/index.php/s/t3N4iYNUoAMnwqI "latest I think" otherwise you can look at this link https://forum.xda-developers.com/apps/magisk. A bit messy I think.
6. Terminal command "adb install (this apk) drag it from dir. Of course ADB-debugger ON. I don't know instructions for Windownsyndrom. If you need it, I can guide you or somebody else that need it. Just ask.
7. Download https://serv8.asuscomm.com/owncloud/index.php/s/QXkxRkBezJXLlQE. And the easiest way are with ADB "adb reboot bootloader". Or use buttons and cable. Blue LED should be on and black screen.
8. Teminal "fastboot devices" Permission denied. Then you need sudo. Try "sudo fastboot devices"
8/1 If you need ROOT remember
------------------------------------------------------------------------------------------------------------------------------------------------------------
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
----------------------------------------------------------------------------------------------------------------------------------------------------------
Terminal
[email protected] ~ $ sudo fastboot devices
[sudo] password for johan:
WUJ01R6*** fastboot
----------------------------------------------------------------------------------------------------------------------------------------------------------
When you see a number then you know the GNU/Linux recognize the phone and back.
So after that "fastboot flash boot "this boot patched_boot_G3313.img" or if you need root "sudo fastboot flash boot "this boot patched_boot_G3313.img" drag is the lazymans work from dir. Or cd to the dir and find the file. Works whit both ROOT and user.
Terminal
"fastboot restart"
Then you should see in the magisk app that you are rooted systemless. And can use modules.
Haven't tried any modules yet.
Just try too break it down to simple language.
This is the origin of https://forum.xda-developers.com/xperia-l1/how-to/root-l1-g3313-magisk-t3693350.

Need help at 5.
purjolini said:
Hi mingkee.
This works whit G3311 confirmed. Build: 43.0.A.6.49 Android 7.0 Baseband MOLY.LR9.W1444.MD.LWTG.MP.V166..5, Kernel 3.18.35+
Kernel is for G3313 magisk patch.
Everything works with this for G3311 as I've tested. Try it at you're own risk.
In linux in (debain, Ubuntu, Linux Mint and all) you need tools
Terminal "sudo apt-get install android-tools-adb android-tools-fastboot"
1. Unlock bootloader https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code. Get the code
2. Go to settings/ about phone/ build number/ click 7 times. Go back to settings. Developer options/ USB debuggning ON. OEM unlock ON. And try "adb devices" in terminal GNU/Linux. Should popup a allow PC on the phone" tranfer files is necessary "MTP", on the phone.
3. In terminal "adb reboot bootloader" this is where "allow access to computer" if it's haven't appeared allow on the phone.
4. In terminal "fastboot oem unlock x0(the code). no space. Don't know why x0 doesn't exist in the code. Don't know why. It's my first Sony with the openness they got now (thank god for Lund, sweden and Jolla, Finland). But it seems pretty easy to unlock. Honor 8 have closed bootloader unlock since 8 Month. So be at ease. And maybe save you're unlock code. But it doesn't seems like you need it.
5. I did it this way.
5/1 Download https://serv8.asuscomm.com/owncloud/index.php/s/t3N4iYNUoAMnwqI "latest I think" otherwise you can look at this link https://forum.xda-developers.com/apps/magisk. A bit messy I think.
6. Terminal command "adb install (this apk) drag it from dir. Of course ADB-debugger ON. I don't know instructions for Windownsyndrom. If you need it, I can guide you or somebody else that need it. Just ask.
7. Download https://serv8.asuscomm.com/owncloud/index.php/s/QXkxRkBezJXLlQE. And the easiest way are with ADB "adb reboot bootloader". Or use buttons and cable. Blue LED should be on and black screen.
8. Teminal "fastboot devices" Permission denied. Then you need sudo. Try "sudo fastboot devices"
8/1 If you need ROOT remember
------------------------------------------------------------------------------------------------------------------------------------------------------------
We trust you have received the usual lecture from the local System
Administrator. It usually boils down to these three things:
#1) Respect the privacy of others.
#2) Think before you type.
#3) With great power comes great responsibility.
----------------------------------------------------------------------------------------------------------------------------------------------------------
Terminal
[email protected] ~ $ sudo fastboot devices
[sudo] password for johan:
WUJ01R6*** fastboot
----------------------------------------------------------------------------------------------------------------------------------------------------------
When you see a number then you know the GNU/Linux recognize the phone and back.
So after that "fastboot flash boot "this boot patched_boot_G3313.img" or if you need root "sudo fastboot flash boot "this boot patched_boot_G3313.img" drag is the lazymans work from dir. Or cd to the dir and find the file. Works whit both ROOT and user.
Terminal
"fastboot restart"
Then you should see in the magisk app that you are rooted systemless. And can use modules.
Haven't tried any modules yet.
Just try too break it down to simple language.
This is the origin of https://forum.xda-developers.com/xperia-l1/how-to/root-l1-g3313-magisk-t3693350.
Click to expand...
Click to collapse
Hi, I've unlocked my phone but I don't uderstand at the 5 can you explain please ? Because I'm on Windows.
Cordially,
Atomiikz.

AtomiiKz said:
Hi, I've unlocked my phone but I don't uderstand at the 5 can you explain please ? Because I'm on Windows.
Cordially,
Atomiikz.
Click to expand...
Click to collapse
Ok Atomiikz. So download and install adb and fastboot tools. From here https://forum.xda-developers.com/showthread.php?t=2588979 install system wide. Otherwise you need to open CMD in the folder whith adb and fastboot.
The open CMD and write "adb devices" and allow on the phone. This should come upp in the command promt "CMD"
--------------------------------------
C:\Users\Mr.J>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
WUJ01R**** device
--------------------------------------
Then " adb install (drag the apk here)" and ENTER. That installs magisk app on you're phone.
Or download the apk. Transfer to the phone. Then use some file explorer like https://play.google.com/store/apps/details?id=com.mi.android.globalFileexplorer https://play.google.com/store/apps/details?id=nextapp.fx https://play.google.com/store/apps/details?id=com.estrongs.android.pop and find the apk. Then install it.
And a heads up if you never used fastboot in windows 10, in my case. I used this application http://zadig.akeo.ie/ to install fastboot drivers for (s1boot fastboot)
Good luck. Write if you have more questions.

I have a question Does the camera or screen or performance get damaged with this proccess ?