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 ?
Related
I have a LTE gnex. I am having problems getting my bootloader unlocked.
If I attempt to use fastboot commands at all I get the error 'fastboot is not recognized as an internal or external command, operable program or batch file.'
If I attempt to use adb devices while I am in fastboot it says "List of devices attached." If I use the adb devices command when my phone is turned on it lists my device like normal.
I feel like I am so close, but yet so far. Any ideas?
EDIT: I'm attempting this on XP, and I am on 4.0.2
I am no expert in these matters, but a few things come to mind:
1) have you got all the proper drivers installed?
2) in the cmd prompt, are you in the directory where fastboot.exe is located?
Have you followed this thread? I'd recommend downloading superboot, extract the contents, go into that folder, and then use: 'fastboot-windows oem unlock'. That should definitely do the trick. Good luck.
EDIT: I don't specifically know all the differences for the GSM/LTE/CDMA versions, but the above should be okay for all versions. To root, and install recovery, on CDMA versions, check out this google+ post.
EDIT2: Also, this thread may be worth looking into.
Assumptions:
- your drivers are loaded properly
- file names are: adb.exe and fastboot.exe
1) open the folder w/ ADB and Fastboot located in them.
2) shift + right click in any open space in the folder - choose: "open command window here"
3) type in (minus the quotes): "adb reboot bootloader"
4) the phone will reboot in the bootloader screen
5) type in: "fastboot oem unlock"
6) phone will ask you are you sure? - use the volume buttons to make the selection say "yes" and press the power button.
7) the phone will unlock and restart. the restart can take as long as 10 minutes or a tad bit longer... do NOT be alarmed!
if this doesnt work for you... either your drivers arent fully installed or your adb/fastboot programs are duds.
aldouse said:
Assumptions:
- your drivers are loaded properly
- file names are: adb.exe and fastboot.exe
1) open the folder w/ ADB and Fastboot located in them.
2) shift + right click in any open space in the folder - choose: "open command window here"
3) type in (minus the quotes): "adb reboot bootloader"
4) the phone will reboot in the bootloader screen
5) type in: "fastboot oem unlock"
6) phone will ask you are you sure? - use the volume buttons to make the selection say "yes" and press the power button.
7) the phone will unlock and restart. the restart can take as long as 10 minutes or a tad bit longer... do NOT be alarmed!
if this doesnt work for you... either your drivers arent fully installed or your adb/fastboot programs are duds.
Click to expand...
Click to collapse
^^^^^^This.....beat me to it LOL. This should work for ya just fine. Just make sure tour fast boot file is in the same as tour adb file. Hope ya her it man. It can def get frustrating
Sent from my Galaxy Nexus using Tapatalk
When I shift + right click I don't have any option to open a command window...well this is frustrating.
twiz0r said:
When I shift + right click I don't have any option to open a command window...well this is frustrating.
Click to expand...
Click to collapse
just open command prompt manually and then go to folder. Eg 'start' -> 'run' -> type 'cmd' and hit enter. Then cd c:\path to folder\ etc.
edit: plus, i gave you a few links to other threads. I really recommend to follow the steps described there if you haven't so far...
i read through all the posts and am having trouble. i have a macbook now and my htc one v is stuck in a boot loop. i need some simple instructions or a link to how to flash a kernel on mac. i have googled it ect and i may be dumb or i cant seem to find the answer and everyone is always so helpful here and im getting frustrated. thank you so much. my phone is already rooted with a custom recovery. its a virgin mobile us
Go developer.android.com and download the SDK & move it to your home directory ("~" or /Users/<username>)
Go to <sdk-location>/tools and launch "Android"
Download the platform tools
Open terminal
Open Finder to <sdk-location>/platform-tools
In terminal, type "sudo cp"; drag adb from the Finder window into the Terminal window; type "/usr/bin/"; hit enter
Enter your password
Repeat the above three steps, but drag "fastboot" instead of "adb"
Close terminal
Open terminal (it sounds weird, but just do it)
Now, and forever, do this to install a kernel:
Download kernel
Connect phone to computer
Make sure USB Debugging is enabled (Settings>Development>USB Debugging)
In terminal, type "adb reboot bootloader"
In terminal, type "fastboot flash boot"; drag in the kernel from finder; hit enter
Examples:
Code:
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
adb reboot recovery
fastboot flash boot /Users/Username/Downloads/boot.img
kalaker said:
Go developer.android.com and download the SDK & move it to your home directory ("~" or /Users/<username>)
Go to <sdk-location>/tools and launch "Android"
Download the platform tools
Open terminal
Open Finder to <sdk-location>/platform-tools
In terminal, type "sudo cp"; drag adb from the Finder window into the Terminal window; type "/usr/bin/"; hit enter
Enter your password
Repeat the above three steps, but drag "fastboot" instead of "adb"
Close terminal
Open terminal (it sounds weird, but just do it)
Now, and forever, do this to install a kernel:
Download kernel
Connect phone to computer
Make sure USB Debugging is enabled (Settings>Development>USB Debugging)
In terminal, type "adb reboot bootloader"
In terminal, type "fastboot flash boot"; drag in the kernel from finder; hit enter
Examples:
Code:
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
sudo cp /Users/Username/android-sdk-mac/platform-tools/adb /usr/bin/
adb reboot recovery
fastboot flash boot /Users/Username/Downloads/boot.img
Click to expand...
Click to collapse
kalekar, mid if i take this instructions and put them in my thread?
cybervibin said:
kalekar, mid if i take this instructions and put them in my thread?
Click to expand...
Click to collapse
No problem! You may want to clean them up a bit; I was in a hurry when I typed those.
sure thanks ill credit u for it
Moved to Q&A
Moderating from my One Xl
It's very simple. Follow whatever instructions are for the kernel, rom, whatever, but add "./" in front of the commands. So "fastboot flash boot" becomes "./fastboot flash boot"
Sent from Hoth.
MonsterNo7 said:
It's very simple. Follow whatever instructions are for the kernel, rom, whatever, but add "./" in front of the commands. So "fastboot flash boot" becomes "./fastboot flash boot"
Sent from Hoth.
Click to expand...
Click to collapse
No! That only works if he has done
Code:
cd <sdkdir>/platform-tools
other wise, it will fail and confuse him even more. Doing cp to /usr/bin/ will allow him to never have to do "./" before the command.
kalaker said:
No! That only works if he has done
Code:
cd /platform-tools
other wise, it will fail and confuse him even more. Doing cp to /usr/bin/ will allow him to never have to do "./" before the command.
Click to expand...
Click to collapse
Ok ok calm down. I do it my way multiple times a week, I've never had an issue. Sure I have to cd into the directory, but that's only one more line of code. If your way will be easier then cool.
Sent from Hoth.
Disclaimer:
I (or anyone other than yourself) am not responsible for anything that goes wrong with your phone. This process is very safe, and the likelihood of bricking your phone is so small that you have a better chance of flying to the sun without a rocket. If you read the guide here closely and do not alter from it in any way, your phone will be S-Off and fully ready to have fun with.
#2
I did not write any code or have any involvement with the development of rumrunner. If you want to donate to someone, donate to them at [email protected] via PayPal. Really guys, I didn't do anything more than test.
For Linux:
For Linux, you do not have to install anything to your hard disk. In fact, you only need a USB port or CD-ROM drive. Ubuntu (32bit) is the recommended distro, however others will work. This guide will only use the Ubuntu given below, for universality purposes.
Downloads:
Firstly, we need to get some important files. Please download all the files given below
Ubuntu 13.10 (32bit)
rumrunner (Go to One V Linux at the bottom of the page)
hboot mod (For your corresponding device, for more info see Device Identification section)
NOTE: Some variants do not have Hboot mod yet. Please be patient.
ADB and Fastboot
Unsecured boot.img
If primoc or if primou (DONT have a stock boot.img yet... can someone send that in a PM please)
Now that you have all the files, boot into Ubuntu. I will not go into detail in how to do this, as it is well documented elsewhere.
Once in Ubuntu, open a terminal for usage.
Now minimize this and place the downloaded files onto your desktop.
unzip the adb_fastboot_linux.zip file to the Desktop
Un-tar and Un-gzip your rumrunner file to the desktop. This can be done by double clicking the file, then clicking extract.
unzip the adb_fastboot_linux.zip
move Primoc_Unsecureboot.img into adb_fastboot_linux/
go to your terminal, type "cd ~/Desktop/adb_fastboot_linux/ && chmod a+x *"
now type the command "sudo ./adb reboot bootloader" (if you get waiting for device, enable USB debugging in developer settings)
If you're not unlocked, unlock at htcdev now... Else, continue
Run the command "sudo fastboot flash boot Primoc_Unsecureboot.img" then "sudo fastboot reboot"
Now....Type in "cd ~/Desktop/rumrunner_primo_0.5.6" and press enter.
Now, type in sudo soju. Respond to the prompts within the program and follow all the directions.
You should now be S-Off... want more power, well lets get it.
If your device has a hboot mod follow the following commands.
move the hboot_rumrunner_primoc.zip into adb_fastboot_linux/
"sudo adb reboot bootloader"
"sudo fastboot erase cache"
"sudo fastboot oem rebootRUU"
"sudo fastboot flash zip hboot_rumrunner_primoc.zip"
OR if it primou
"sudo fastboot flash zip hboot_rumrunner_primou.zip"
Congradulations, you are now S-OFF and can flash kernels in recovery. You also have flat out ultimate control over your phone; however, tread carefully. With great power comes great responsibility.
NOTE: Windows coming soon.
Device Identification:
It is important to know which device you have with the S-Off process. If you do not know what device you have, you can severely damage your device, possibly bricking it. To prevent this, follow the steps for identification below.
Unplug phone if plugged in
Go to settings>power>fastboot(disable)
power off phone completely
once phone is off, press volume down+power until bootloader appears
look in the top left corner, you will see either Primou or Primoc
If primou appears, you are GSM if primoc appears you are CDMA
Reserved
Im leaving this thread closed until I get a chance to write up windows as well
On the official cyanogen mod guide for the LG G3 this is stated:
Now, open a command prompt window or terminal window and open an "adb shell"
How is this done / what is meant by it?
https://wiki.cyanogenmod.org/w/Install_CM_for_d855
LennartFuchs said:
On the official cyanogen mod guide for the LG G3 this is stated:
Now, open a command prompt window or terminal window and open an "adb shell"
How is this done / what is meant by it?
https://wiki.cyanogenmod.org/w/Install_CM_for_d855
Click to expand...
Click to collapse
Download the drivers for LG G3, download the adb from Google, connect your device to computer, open command prompt, navigate to adb.exe or make a path in computer settings, verify that device is connected with command: adb devices, if your device is listed continue with command: adb shell, copy whats written in the guide you found.
Or save yourself the trouble if you aren't good with cmd and download flashify from Google Play, download the latest TWRP and flash it. Of course this will work only if you used the benders autorec app on lollipop otherwise you will get secure boot error.
But if you are on kitkat you don't need to install benders autorec, just download TWRP and flash it either with flashify or with adb.
Also if you dont want to use computer you could install terminal emulator from Google Play and you wouldn't need to use adb shell at all. Just write the stated commands, that is:
su
dd if=/sdcard/twrp-d855.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Happy flashing.
first off, huge shout out to @JengaMasterG for TWRP for these devices. Without him, this super simple method wouldn't be possible.
What You'll Need
- Android 11 most recent update
- TWRP: TWRP for Surface Duo (credits to @JengaMasterG )
- Unlocked Bootloader
- ADB/Fastboot: ADB/Fastboot Install (what i use)
- Magisk
video
YT Tutorial
Bootloader Unlock
1.) Enable Developer Options via tapping Build Number over and over in the About Device part of settings
2.) Enable USB Debugging and OEM Unlock
3.) Plug device into the computer, and type the following command in cmd.exe, hit enter
Code:
adb devices
4.) You may get a pop up on screen requesting permission, always allow it
5.) Type the following and hit enter
Code:
adb reboot bootloader
6.) Once in the bootloader, your device might not be recognized right away and will need the driver manually installed via Device manager (see video for that)
7.) Once device is recognized, type the following command
Code:
fastboot flashing unlock
8.) Allow the unlocking of the Bootloader on device screen. this will erase everything
9.) Allow the device to fully boot up, enable USB Debugging again and continue the tutorial!
Instructions
1.) Rename Magisk-vxx.x.apk to Magisk.zip
2.) Enable USB Debugging
3.) Type the following to make sure your computer sees the device (in cmd.exe)
Code:
adb devices
4.) You may get a pop up on your device's screen asking for adb permission, check the always allow and hit ok
5.) Type the follow command to reboot to bootloader (in cmd.exe)
Code:
adb reboot bootloader
6.) Once you're in the booloader and its unlocked, download the TWRP image from above
7.) Use the following fastboot command to boot into TWRP
Code:
fastboot boot twrp.img
8.) Once TWRP boots, keep your device plugged in via usb and type the following command into cmd.exe and hit enter
Code:
adb shell twrp sideload
9.) Once in sideload, you can type the following with magisk.zip and root your device!
Code:
adb sideload magisk.zip
10.) Use the following command to reboot and you're done!
Code:
adb reboot
congrats! you're rooted!
LETS GOOOO!! HEROOO!! Super easy and working on the latest December 2022 update! Felt way safer as well, not so much concern over twrp as we only booted into it, and then I just used the standard magisk and it worked excellent without worrying about all types of patches and versions aside from the latest twrp for android 12 from @JengaMasterG!
Thank you! I think the renaming the magisk file from apk to zip was probably what I was doing wrong trying to follow the other methods, on top of driver errors, that were solved by uninstalling all the drivers for the duo on my surface pro, which revealed a native 'Surface Fastboot' driver. Combine that with the 15 second ADB and it's .bat ready to go command line interface, idk... it wen't so smooth and worked perfectly.
Now I can try to see if I can improve my experience with some go to methods.. I really want to enable immersive mode and hopefully increase overall volume, if possible (many devices this can be done with engineeringmode, idk yet but hopefully it does have one and hopefully I can also calibrate the gyroscope)... obviously adblock without vpn is on the menu.... can utilize the full autoruns app to stop apps from starting up at boot like in windows... and then get into some other customizations.
cqqx2 said:
LETS GOOOO!! HEROOO!! Super easy and working on the latest December 2022 update! Felt way safer as well, not so much concern over twrp as we only booted into it, and then I just used the standard magisk and it worked excellent without worrying about all types of patches and versions aside from the latest twrp for android 12 from @JengaMasterG!
Thank you! I think the renaming the magisk file from apk to zip was probably what I was doing wrong trying to follow the other methods, on top of driver errors, that were solved by uninstalling all the drivers for the duo on my surface pro, which revealed a native 'Surface Fastboot' driver. Combine that with the 15 second ADB and it's .bat ready to go command line interface, idk... it wen't so smooth and worked perfectly.
Now I can try to see if I can improve my experience with some go to methods.. I really want to enable immersive mode and hopefully increase overall volume, if possible (many devices this can be done with engineeringmode, idk yet but hopefully it does have one and hopefully I can also calibrate the gyroscope)... obviously adblock without vpn is on the menu.... can utilize the full autoruns app to stop apps from starting up at boot like in windows... and then get into some other customizations.
Click to expand...
Click to collapse
Hello! I'm rooted, but I can only read and can't write. I am Android version 122022.821.13 of Att.
So I can't delete the apk inside the system directory
linlin2az said:
Hello! I'm rooted, but I can only read and can't write. I am Android version 122022.821.13 of Att.
So I can't delete the apk inside the system directory
Click to expand...
Click to collapse
Newer Android versions, especially stock ROM, generally doesn't let you write to the system partition. Only ROMs can do that, unless you can find a way to change the partition permissions. Root alone will not allow it, no matter what you do. I used to know of a TWRP script to fix that and make the system writable, but it doesn't work on andorid 11/12/13 anyway