[ROM][Official] Kali NetHunter for the TicWatch Pro WearOS - Wear OS Software and Hacking General

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
All variants are supported (TicWatch Pro, Pro 2020, Pro 4G/LTE)
I present to you: Kali NetHunter for the TicWatch Pro WearOS
Kali NetHunter is an Android ROM overlay that turns an ordinary phone into the ultimate Mobile Penetration Testing Platform. Now it's available for your smartwatch with some limitations.
The overlay includes a custom kernel, a Kali Linux chroot, an accompanying Android application, which allows for easier interaction with various security tools and attacks.
Beyond the penetration testing tools arsenal within Kali Linux, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, WPS attacks, and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page.
NetHunter is an open-source project developed by Offensive Security and the community.
## 1. Unlock the bootloader
- Connect your watch to your PC with it's USB cable, and fire up a terminal.
- If you have set up your watch on the phone you can access settings, otherwise hold both buttons for a few seconds on the welcome screen.
- Enable developer settings by going to System -> About -> tap Build number 10 times
- Enable ADB, re-plug USB and accept debug from PC
- Reboot into bootloader with "adb reboot bootloader" from the terminal
- Unlock bootloader with "fastboot flashing unlock"
## 2. Flash vendor image, TWRP, and optimized WearOS
Download and extract the installation files into a folder. Please not this tutorial is for the TicWatch Pro 2020 (catfish), your ROM might be different on other models, please refer to @janjan's repo found here for the other ROMs.
Please note Magisk 21.0 is recommended, included in the following link.
Download link for ROM, vendor, TWRP, and Magisk: https://build.nethunter.com/contributors/re4son/catfish/
Download link for NetHunter zip. Scroll down to TicWatch for latest release: https://www.kali.org/get-kali/#kali-mobile
- Again enable ADB, and reboot to bootloader with "adb reboot bootloader"
- "fastboot flash vendor vendor.img"
- "fastboot flash recovery twrp-3.4.0-0-catfish.img"
- Boot into recovery by selecting it with the side buttons (switch with bottom one, select with upper button)
- Select "Wipe -> next page -> Format Data"
- Reboot to Recovery
- Select "Install -> ADB Sideload" and tick "Wipe Dalvik Cache, Wipe Cache
- "adb sideload 2-ROM-PWDD.190617.074-AUG-09.zip"
- Reboot & do initial setup (pair with your phone through WearOS app)
## 3. Resize system partition in TWRP
- Again enable ADB
- "adb reboot recovery"
- Select Wipe -> next page -> File System Options - select System - Resize (to have ~175MB free on /system instead of 0)
## 4. Flash and launch Magisk app to finish the rooting process
- "adb sideload Magisk-v21.0.zip"
- Reboot to System
- Launch Magisk Manager
- You might want to disable auto-update, set grant access in auto response, and disable toast notifications for easier navigation in the future
## 5. Flash NetHunter
- "adb reboot recovery"
- Select Install -> ADB Sideload
- "adb sideload" NetHunter image
- Reboot
- Start NetHunter app & chroot
- Reboot
## 6. Set NetHunter watch face
- Install Facer onto your phone from Play Store
- Search for NetHunter
- Install Facer companion app to watch
- Select & Sync
## Download link
TicWatch_Pro_NetHunter_files.zip | by yesimxev for Ticwatch Pro (2018)
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
## Additional supported apps
- Drivedroid: use "adb install" to install the latest version
Download link: https://store.nethunter.com/repo/com.softwarebakery.drivedroid_105000.apk
- TotalCommander: useful for selecting eg. a Ducky script, use "adb install" method
Download link: https://www.totalcommander.ch/android/tcandroid323-armeabi.apk
## Supported features
- Kali services
- Custom Commands
- MAC Changer
- HID Attacks
- DuckHunter
- Bad USB
- Nmap Scan
- WPS Attacks
## Upcoming features (not guaranteed)
- Nexmon, as the chipset is supported, needs some time
- Bluetooth Arsenal (internal bluetooth via blueblinder, as carwhisperer fails to r/w when SCO channel is connected)
- Router Keygen (to be optimised)
- Hijacker (if nexmon succeeds)
- Mifare Classic Tool (need to build OS with android.hardware.nfc enabled)
## Hardware limitations
- Power resource is not enough for any external adapters
Credits: The Offensive Security Team and the NetHunter community
Another extremely big thanks for @janjan for making this possible!
WearOS version: 2.17
XDA: DevDB Information
Kali Nethunter, Kernel & ROM for the TicWatch Pro
Contributors
@yesimxev
Source Code: https://gitlab.com/kalilinux/nethunter/
Kernel Source: https://github.com/yesimxev/msm-catfish-9.0-wear-os

RESERVED

Excited to try this with Catshark!
Thank you!

@yesimxev a fantastic contribution, just for the pleasure that "you do it because you can" you have my full support.
Can you upload screenshots or video, I'm curious how it interacts with the ROM when you do WPS attack, NMAP scan or any other of the functions you have enabled.
Is the ROM adapted to the much smaller screen size that the watches have?

bernarbernuli said:
@yesimxev a fantastic contribution, just for the pleasure that "you do it because you can" you have my full support.
Can you upload screenshots or video, I'm curious how it interacts with the ROM when you do WPS attack, NMAP scan or any other of the functions you have enabled.
Is the ROM adapted to the much smaller screen size that the watches have?
Click to expand...
Click to collapse
Yes I've optimised the NH app to fit. See some of my videos for HID, WPS attacks and even Konboot:

@yesimxev
Any advice for me please?
Failed before Last item in step 2. Reboot & do initial setup (pair with your phone through WearOS app)
Symptom long Boot animation for 90 seconds and booted to TWRP.
Attempt 1 using above process + JanJan files for Catshark.
Attempt 2 using Modified step + JanJan files
Modified step - Forum Post- https://forum.xda-developers.com/t/...kipjack-9aug20.3821013/page-186#post-82992173 (#3,714)
You don't need to flash the twrp. It usually cause bootloop. Use
adb reboot bootloader
fastboot boot name-of-the-twrp.img
## 1. Unlock the bootloader
## 2. Flash vendor image, TWRP, and optimized WearOS
Attempt 1
Manually
Reboot to bootloader with "adb reboot bootloader"
Fastboot flash vendor vendor.img
From TicWatch-Pro(4G)(Catshark)-EU-&-USA\TicWatch-Pro(4G)(Catshark)-EU-&-USA\Custom-ROM\TicWatch-Pro-4G-USA\ROM\2020\27-January-2020\Vendor-27-Jan-2020.zip (Vendor.img)
fastboot format userdata
fastboot format cache
"fastboot flash recovery catshark-4G-recovery.img"
From TicWatch-Pro(4G)(Catshark)-EU-&-USA\TicWatch-Pro(4G)(Catshark)-EU-&-USA\Custom-ROM\TicWatch-Pro-4G-USA\TWRP (catshark-4G-recovery.img)
Boot into recovery by selecting it with the side buttons (switch with bottom one, select with upper button)
Select "Wipe -> next page -> Format Data"
Reboot to Recovery
- Select "Install -> ADB Sideload" and tick "Wipe Dalvik Cache, Wipe Cache
"adb sideload Ticwatch-4G-USA-PWDD.190617.032-XDA-27-JAN-2020-LMKiller.zip"
- Reboot-
Symptom long Boot animation for 90 seconds and booted to TWRP.
Attempt 2
Manually
Reboot to bootloader with "adb reboot bootloader"
Fastboot flash vendor vendor.img
From TicWatch-Pro(4G)(Catshark)-EU-&-USA\TicWatch-Pro(4G)(Catshark)-EU-&-USA\Custom-ROM\TicWatch-Pro-4G-USA\ROM\2020\27-January-2020\Vendor-27-Jan-2020.zip (Vendor.img)
Fastboot format userdata
Fastboot format cache
Fastboot boot catshark-4G-recovery.img"
From TicWatch-Pro(4G)(Catshark)-EU-&-USA\TicWatch-Pro(4G)(Catshark)-EU-&-USA\Custom-ROM\TicWatch-Pro-4G-USA\TWRP (catshark-4G-recovery.img)
Boot into recovery by selecting it with the side buttons (switch with bottom one, select with upper button)
Select "Wipe -> next page -> Format Data"
Reboot to Recovery
- Select "Install -> ADB Sideload" and tick "Wipe Dalvik Cache, Wipe Cache
"adb sideload Ticwatch-4G-USA-PWDD.190617.032-XDA-27-JAN-2020-LMKiller.zip"
- Reboot-
Symptom long Boot animation for 90 seconds and booted to TWRP.

Roll back a build. Here's some instructions used by security researcher Lucas Stefanko
Installing NetHunter On the TicWatch Pro | Kali Linux Documentation
All variants are supported (TicWatch Pro, Pro 2020, Pro 4G/LTE) From unpacking to running NetHunter in 6 steps: Unlock the bootloader Flash vendor image, TWRP, and optimized WearOS Resize system partition in TWRP Flash and launch Magisk app to finish the rooting process Flash NetHunter Set...
www.kali.org

Achi Shukuteki said:
Roll back a build. Here's some instructions used by security researcher Lucas Stefanko
Installing NetHunter On the TicWatch Pro | Kali Linux Documentation
All variants are supported (TicWatch Pro, Pro 2020, Pro 4G/LTE) From unpacking to running NetHunter in 6 steps: Unlock the bootloader Flash vendor image, TWRP, and optimized WearOS Resize system partition in TWRP Flash and launch Magisk app to finish the rooting process Flash NetHunter Set...
www.kali.org
Click to expand...
Click to collapse
Thank you!,
If I am comprehending correctly this great write up includes the build for catfish only.
Meaning other models, must refer to @janjan's repo found here for the other ROM.
I used the only build for my device that is available in JanJan's repo.
Thanks for your patience.

Dmcpen said:
Thank you!,
If I am comprehending correctly this great write up includes the build for catfish only.
Meaning other models, must refer to @janjan's repo found here for the other ROM.
I used the only build for my device that is available in JanJan's repo.
Thanks for your patience.
Click to expand...
Click to collapse
Indeed. Keep us posted. I havent had the time, yet, to mod mine.

Achi Shukuteki said:
Roll back a build. Here's some instructions used by security researcher Lucas Stefanko
Installing NetHunter On the TicWatch Pro | Kali Linux Documentation
All variants are supported (TicWatch Pro, Pro 2020, Pro 4G/LTE) From unpacking to running NetHunter in 6 steps: Unlock the bootloader Flash vendor image, TWRP, and optimized WearOS Resize system partition in TWRP Flash and launch Magisk app to finish the rooting process Flash NetHunter Set...
www.kali.org
Click to expand...
Click to collapse
The kali[.]org and these instructions are the same. I've updated both in the same time. I'm afraid you might have a different way to flash. Or try the stock, you don't really need to be on the custom ROM. The NetHunter kernel will be the same and if you don't need any Mobvoi apps, we'll google how to remove them
Also, are you sure you've got a US model?

yesimxev said:
The kali[.]org and these instructions are the same. I've updated both in the same time. I'm afraid you might have a different way to flash. Or try the stock, you don't really need to be on the custom ROM. The NetHunter kernel will be the same and if you don't need any Mobvoi apps, we'll google how to remove them
Also, are you sure you've got a US model?
Click to expand...
Click to collapse
Thanks!
Success!
Nethunter works
Call and Text on 4G Works!

Dmcpen said:
Thanks!
Success!
Nethunter works
Call and Text on 4G Works!
Click to expand...
Click to collapse
What was the issue?

Please note I am very new to this and was only able to get this far because of hard work by @[yesimxev] and [@janjan]
Here are my notes. Use at own risk.
I had 3 failed attempts, and used [@janjan] return to stock process from:
[ROM+KERNEL+TWRP][Ticwatch Pro(Catfish)(Catshark-4G)]+[Ticwatch C2(Skipjack)[9Aug20]
-[Ticwatch Pro 4G/LTE (EU) (Catshark)-PWDD.190617.059]-[30-5-2020] - [Ticwatch Pro 2020 (Catfish-Ext)-PMP2.191203.001]-[22-6-2020] - [Ticwatch Pro (Catfish)-PWDD.190617.074]-[09-8-2020] ############################# - [Ticwatch Pro 4G/LTE (USA)...
forum.xda-developers.com
Hopefully you can learn from my mistakes with the details below.
Please note this is for the:
Ticwatch-Pro-4G(Catshark)-USA-PWDD.190617.032, your ROM might be different on other models, please refer to [@janjan](https://forum.xda-developers.com/m/490110/)'s [repo found here for the other ROM]https://forum.xda-developers.com/t/...shark-4g-ticwatch-c2-skipjack-9aug20.3821013/
Download and extract the installation files into a folder.
Please note Magisk 21.0 is recommended, included in the following link.
Download link for Magisk and Nethunter:
[https://build.nethunter.com/contrib...d.nethunter.com/contributors/re4son/catfish/)
[TicWatch_Pro_NetHunter_files.zip](https://build.nethunter.com/contributors/re4son/catfish/TicWatch_Pro_NetHunter_files.zip "TicWatch_Pro_NetHunter_files.zip")
Download link for NetHunter zip. Scroll down to TicWatch for latest release: [https://www.kali.org/get-kali/#kali-mobile](https://www.kali.org/get-kali/#kali-mobile)
**## 1. Unlock the bootloader**
- Connect your watch to your PC with it's USB cable, and fire up a terminal.
- If you have set up your watch on the phone you can access settings, otherwise hold both buttons for a few seconds on the welcome screen.
- Enable developer settings by going to System -> About -> tap Build number 10 times
- Enable ADB, re-plug USB and accept debug from PC
- Reboot into bootloader with "adb reboot bootloader" from the terminal
- Unlock bootloader with "fastboot flashing unlock"
**## 2. Flash TWRP, and optimized WearOS
- Again enable ADB, and reboot to bootloader with "adb reboot bootloader"
- "fastboot flash recovery catshark-4G-recovery" (From [@janjan] )
- Boot into recovery by selecting it with the side buttons (switch with bottom one, select with upper button)
- Select "Wipe -> next page -> Format Data"
- Reboot & do initial setup (pair with your phone through WearOS app)
**## 3. Resize system partition in TWRP**
- Again enable ADB
- "adb reboot recovery"
- Select Wipe -> next page -> File System Options - select System - Resize (to have ~175MB free on /system instead of 0)
**## 4. Flash and launch Magisk app to finish the rooting process**
- "adb sideload Magisk-v21.0.zip"
- Reboot to System
- Launch Magisk Manager
- You might want to disable auto-update, set grant access in auto response, and disable toast notifications for easier navigation in the future
**## 5. Flash NetHunter**
- "adb reboot recovery"
- Select Install -> ADB Sideload
- "adb sideload" NetHunter image
- Reboot
- Start NetHunter app & chroot
- Reboot
**## 6. Set NetHunter watch face**
- Install Facer onto your phone from Play Store
- Search for NetHunter
- Install Facer companion app to watch
- Select & Sync
Thank you and good luck.

yesimxev said:
The kali[.]org and these instructions are the same. I've updated both in the same time. I'm afraid you might have a different way to flash. Or try the stock, you don't really need to be on the custom ROM. The NetHunter kernel will be the same and if you don't need any Mobvoi apps, we'll google how to remove them
Also, are you sure you've got a US model?
Click to expand...
Click to collapse
Ha! I didn't notice the equivalence of the instructions. I should've read the first one in its entirety. I skimmed it thinking it was for a newer build. My bad.

Achi Shukuteki said:
Ha! I didn't notice the equivalence of the instructions. I should've read the first one in its entirety. I skimmed it thinking it was for a newer build. My bad.
Click to expand...
Click to collapse
Try stock for the win!

I followed the instructions to the letter on my ticwatch pro but after I adb sideloaded nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip and rebooted... it's not there.
I did it a few times and always the same result: I don't see it in the apps list, am I missing some hidden step?

Jackomel said:
I followed the instructions to the letter on my ticwatch pro but after I adb sideloaded nethunter-2022.2b-ticwatchpro-wearos-kalifs-nano.zip and rebooted... it's not there.
I did it a few times and always the same result: I don't see it in the apps list, am I missing some hidden step?
Click to expand...
Click to collapse
Did you setup the watch before flashing? Show me the /tmp/recovery.log using pastebin

yesimxev said:
Did you setup the watch before flashing? Show me the /tmp/recovery.log using pastebin
Click to expand...
Click to collapse
How do I extract that file from the watch? There is no terminal installed, even though I flashed nethunter

Just wanted to add to this that it's possible to get into the settings menu to enable ADB before pairing with your phone, by holding the top button for a couple seconds on the pairing screen. Should let you save a good chunk of time from installation by avoiding setting the watch up repeatedly

androidyl said:
Just wanted to add to this that it's possible to get into the settings menu to enable ADB before pairing with your phone, by holding the top button for a couple seconds on the pairing screen. Should let you save a good chunk of time from installation by avoiding setting the watch up repeatedly
Click to expand...
Click to collapse
I know, but left 'both buttons' in the instructions.
Jackomel said:
How do I extract that file from the watch? There is no terminal installed, even though I flashed nethunter
Click to expand...
Click to collapse
Flash NH in twrp, then run 'adb shell cat /tmp/recovery.log'

Related

[TOOL] Lx Multi Tool v1.3.2 [WIN/LIN/MAC][Unlock/Recovery/Stock/Kernel/More]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It has LINUX/UNIX and MAC support!
​
Due to the fact that there is another tool for Android called Android Multi Tools, I decided to rename this one to Lx Multi Tool, future releases will go under this name.
Features: ​Fastboot
- Unlock/Lock Bootloader
- Flash Recovery Menu (you can choose and add recoveries) - TWRP 2.8.7.1 Included
- Flash any partition (Flashing submenu)
- Flash full Stock images (you can choose and add images)
- Erase partitions (you can choose which of the partitions)
- Reboot (you can choose again...)
Adb
- Sideload .zip files (you can choose and add .zip files) - SuperSU v2.65 (Systemless!) included
- Backup (you can choose the name and place for your backup)
- Restore (you can choose your backup)
- Version (it just shows the version of your adb binaries) - platform-tools 23.1 included
- Logs (DMESG and Logcat)
- Screenshots (you can directly take screenshots to your PC with no Root)
- Reboot (lots of choices)
Others
- Refresh and delete files/folders from menus (Right click or key F5 and Del)
- Open tool folders from the menus (to add your own kernel/stock image/recovery/sideload zip files)
- Tab key support for easier keyboard navigation
- Tool-tips for all buttons
- Check for updates
- Link to xda-thread (here)
​
Download links: ​Windows x86|x64 - Linux x64 - MAC x64
All released versions can be found here.
​
[ROOT] Use SuperSU 2.62 or higher from here systemless for 6.0.1 and above.​
Known bugs/limitations: ​ - For partition Flashing, it is recommended(mandatory?) to do a reboot-bootloader if you want to flash multiple partitions one after the other. (according to the Google flashing scripts) (Implemented in 1.2.1)
- For return to stock, the tool will be stuck after your phone successfully boots, you need to reboot to fastboot again in order to flash the Radio and finish the full return to stock. (Fixed in 1.2.0)​
Changelog: ​
Check the changelog for each release here.
​
Tutorials/FAQ: ​
Q: How do I get in bootloader/fastboot mode?
Turn off the phone and turn it on by using Volume down + Power key.
Q: How do I check for updates in your tool?
Follow the instructions in the screen below.
Q: Where can I find the device driver to install it for windows?
Click here, download the driver and run the setup.
Q: How do I root my stock phone?
- Unlock bootloader.
- Flash recovery.
- Use SuperSU 2.62 systemless or higher from here.
(Usually the latest version upon tool release is included in the Sideload folder of the tool, you can either sideload it or copy it to recovery and flash it manually)
Q: I get an error "Cannot open file" on MAC, what should I do?
Open the terminal, go to your application path and paste this command:
Code:
chmod +x LxMultiTool.app/contents/macos/*
Q: What do I need to do in order to be in Fastboot or in ADB mode.
Fastboot mode will be detected only while being in bootloader.
ADB mode will be detected from Recovery (custom) and actual ROM with USB debugging active.
Refresh button needs to be used in order to check for what mode you are in.
Q: Are there any other software that I need to install in order to run this tool?
On Windows and MAC everything is bundled, so nothing needs to be installed, just run.
On Linux you need to install from your package manager libQt5Core, libQt5Widgets, libQt5Gui, libQt5Network.
If it's not enough, use ldd LxMultiTool in terminal to find out what you're missing from your environment.
Q: I have an yellow/orange/red text screen during boot, what's that?
When you unlock you usually get the Orange screen and it's normal, but if you really want to know what's this about, give a reading to this.
Q: Hey, my device is not detected, why?
On windows, you need to manually install the USB drivers, they are not included and probably they won't be included in this tool.
Also, make sure you click the connection Refresh button after connecting the device to your PC.
Q: What do i need to do in order to install a custom ROM?
1. Unlock Bootloader.
2. Flash a custom recovery of your choice.
3. Flash an insecure kernel (boot).
4. Flash custom ROM with no problems via recovery.
All those things are found and can be done via this tool.
Q: Hi, i just downloaded this tool, how do i use it?
First, extract the folder somewhere.
After that, run LxMultiTool.exe on windows by double clicking it, LxMultiTool on linux and the same on mac.
Q: Do I need android-sdk installed or something else?
No! This tool uses it's own supplied binaries for adb and fastboot, if you have android-sdk installed it will be ignored anyways.
This tool is fully portable and stand-alone.
Q: I get an error while trying to unlock the bootloader -> FAILED(remote: oem unlock is not allowed), what now?
Starting with Android 5.0, you need to enable Bootloader Unlocking from the developer settings, in order to do that, follow these steps:
- Enable Developer options
- Enable USB Debugging
- Look for the ‘OEM Unlock’ Option and toggle it.
Q: How do I use the return to stock feature?
First download the latest package from here, then extract the contents (there is an archive in the archive) untill you get the a folder like angler-mda89d
that contains the images, that folder needs to be copied in the /Data/StockPackages folder in order to be visible.
Easier steps -> Get your device in bootloader -> Start the tool -> Hit refresh -> go to Stock -> hit open folder -> copy the extracted folder with the name angler-xxxxxx in there, hit F5 or Right-click + Refresh -> you should see the folder in there like in the following screenshot. Thanks @ursa08 for the screenie.
Q: How do I enable Developer options?
- Launch the Settings
- Scroll Down and Tap on About Phone(or About Device)
- Locate the Build Number Section
- Tap on the Build Number Option 7 Times
- Go Back to the Main Settings Page
- Scroll Down and Tap on Developer Options
Q: Hi, i just bought a phone what should i do now?
Well, you firstly need to unlock your bootloader...
Q: What is logcat?
Well, you can pretty much use google for that answer, but to put it short, is that thingy that tells you what is happening behind the scenes of your phone.
It is usually used for debugging and entertaiment(?).
When you report an error/bug to somebody, it will be a blessing to provide a logcat (logfile)!
Q: What is a Custom Recovery and why do i need one?
A custom recovery is that thingy that let's you flash .zip files, use your logic and you wil get it why you need one.
Q:There are others guides/tutorials out there, should i check them instead of this?
If you manage to get things done using this one, no, otherwise yes, note that some could be outdated...
Q:What is sideload and how do I use it?
Sideload is a function from adb that let's you flash a zip file while in recovery directly from your PC.
Please note that you need to be in sideload mode on your recovery before doing this.
To enter sideload mode, in TWRP go to Advanced -> ADB Sideload -> Swipe to sideload​
Sources: ​The official and original repository can be found here.​
Bug reports/Feature requests: ​If you have any bug, or you consider a feature to be a must-have, please use the issue functionality on github for more traceability here.​
Licensing: ​Please note that this tool is open source and released under GPL v3 licence which can be read here.
Make sure you understand at least the short version of the license that's provided in the tool before using it or before contributing/forking and other related stuff.​
Tech and stuff: ​Some additional marketing for stuff used in this tool
Qt - An awesome cross-platform IDE
Vmware - For letting me test this tool on all platforms (Linux and MAC).
Icons8 - A nice platform for good-looking FREE icons. (Big thanks!)
UnixUtils - For the sed utility for Windows.
AndroidFileHost - For the awesome file-management platform for developers.​
Donations: ​Even though this tool is provided free of charge, full open-source, donations are very welcome to support the future development of this tool and to buy me a beer while coding future improvements on it.
This section will also include the hall of fame for donors, as well as on the github repository.
Special thanks for donations:
- @john7760
​
Disclaimer:​I will not be responsible for smashed screens, bricked phones or any other things that you can accuse me of, i've done this tool to help people, use it at your own risk and consider giving a THANKS if you use it and like it.​Please consider leaving some feedback, what to improve, what could be done better, what annoys you, it really helps me improve the tool.
Also, to avoid useless threads on general, Q&A or useless posts, please read the FAQ section upside, it's like a Mini-Guide!
Nice! Quick question, will this work for other phones other then nexus 6. Like sam note 3
Sent from my Nexus 6 using Tapatalk
warfenix said:
Nice! Quick question, will this work for other phones other then nexus 6. Like sam note 3
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This tool has support only for 4 nexus devices, some features might work, some not, it's all down if the commands that are used by the tool are supported by the other device.
For example all fastboot flashing commands use the command:
Code:
fastboot flash <partition> <file_to_flash>
The same goes for the rest of the commads, I will try to investigate more and see if it's worth it to create a Sam Note 3 package for the tool.
The adb features should work though.
That would be awesome as i run only linux. And cant seem to get odin or heindall to work. Tried multiple times. So if there is something you could cook up. Amazing sauce. Its a att note 3. Either way. This will work great for my n6
Sent from my Nexus 6 using Tapatalk
New update with some fixes that should have been implemented a long time ago...
- Fixed Sideload flashing
- Enabled Recovery rebooting
- Fixed open folder for Stock menu
Wow - Great work on this. Love the fact that it supports mac/nix as well.
Nice! Keep up the good work.
Thank you!
This still the go to way to unlock and flash twrp? I'm on latest stock marshmallow.
bL33d said:
This still the go to way to unlock and flash twrp? I'm on latest stock marshmallow.
Click to expand...
Click to collapse
Yes, you can unlock the bootloader and flash TWRP recovery with it.
Support to Nougat?
ipan gulopuan said:
Support to Nougat?
Click to expand...
Click to collapse
Nougat should work with no problems, I personally used it to flash bootloader, radio and vendor images for Nougat update.

Help with fixing app force close

I found an app called package signer from https://forum.xda-developers.com/android/software/tool-package-signer-1-0-t3533073 to sign the zip files in android to fix signature verfication error in some recoveries....
Developer stopped development of that app...
and also that thread is closed...
It signs correctly but one issue is, it can't able to sign zips that are greater than 20mb ......
It force closes when working with large zip files...
It is open source is github....
Sir osm0sis i have seen you are helping in zip signers..
Can you please help....
I hope some developer can fix this and post below.....
Please help by fixing that force close error of signing big zip files......
Thanks in advance...!
Edit:- See https://forum.xda-developers.com/t/...-apk-zip-within-android.3835975/post-81324327 for solution.
Nope, you should use zipsigner.jar from my Complete Shell Zip + Signing thread.
osm0sis said:
Nope, you should use zipsigner.jar from my Complete Shell Zip + Signing thread.
Click to expand...
Click to collapse
Since I dont have pc... i am using that sir...
HemanthJabalpuri said:
Since I dont have pc... i am using that sir...
Click to expand...
Click to collapse
It should work on device too if dexed, I'll add it to my thread and post instructions soon.
Reserved this too
DISCLAIMERS (please read !)
The content seen in this thread is targeted at this specific forum's device, the Realme C12, codenamed RMX2189.
Follow the instructions shown in this thread at your own risks, I will not be held responsible for bricking your device, you did this yourself.
That said, the information will be kept up to date relatively frequently, and should you follow the steps and ask questions below when unsure, everything will be fine!
No files will be directly provided. Do not use pre-created/re-uploaded content. Instead I'll teach you to gather the required files from official websites, and create the other ones yourself.​
ROM (GSI) Recommendations:
Ordered by personal preference:
1) CAOS
2) LOSQ (LineageOS GSI)
3) crDroid
I'm more than open to feedback, suggested changes & improvements!
Prerequisites for most manipulations:
Your phone, well charged if possible
The USB cable used to link your phone to your computer (the one on your charger works just fine)
A computer, with recent ADB & Fastboot (Platform Tools)
Some time, patience, and the ability to read and follow instructions!
Unlock your bootloader (otherwise this thread is useless to you as it's required for rooting as well as installing custom ROMs)
Tutorial:
Step 0 - Great! You're ready to go. Make sure to backup your phone's data before continuing on with this tutorial, as unlocking will make it factory reset (wipe)!
Step 1 - Download and Open In Depth Tool ( Attached With the Guide Down)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2 - Click “Start applying”.
Step 3 - Please read the disclaimer in detail, select the checkbox, and submit your application
Step 4 - The Application Will be checked by realme Servers..(Wait 10 mins)
Step 5 - The unlock tool apk will show the status of the unlock request- Successful
Step 6 - You can now click “Start the in-depth test” and the device will reboot automatically. The following string will display on the screen: fast boot_unlock_verify ok
Step 7 - Now Download and install the fastboot tool on your PC and ready to unlock it.
Step 8 - Now in Fastboot Mode type this command
Code:
fastboot flashing unlock
and Press enter.
Step 9 - On your phone press the Volume Up key to select "UNLOCK THE BOOTLOADER” (or press the Volume Down key if you have changed your mind to select "DO NOT UNLOCK THE BOOTLOADER”). When you click the Volume Up, your phone will reboot and enter the in-depth test mode - all user data on the phone will be erased - I recommend you perform a data backup prior to applying.
Step 10 - Now type
Code:
fastboot reboot
And there you go! Your phone will reboot and you can set it all up again, with the ability to follow the rooting tutorial below, and you can also install GSIs/custom ROMs/recovery!
Rooting with Magisk
Tutorial:
The procedure is the same whether you're on the stock RealmeUI Rom or on a custom GSI (treble) one.
Step 1 - Download the latest Magisk Manager on your phone.
Go to the link above, click the latest MagiskManager-vX.X.X.apk you see in the list to start the download, open the file and install.​
Step 2 - Download the latest Realme Official Rom from Software Update - realme depending on your region.
Step 3 - Get your ROM you downloaded above, it should be a .ozip archive. Add .zip extension to it. Extract it.
Step 4 - You should now get a folder like shown below, and..
Copy the boot.img to your phone's /sdcard/ folder (where the Android, DCIM, Download, and more are present, just drop it in there).
And here's how it shoud look inside your phone's storage in the end.
Step 5 - On your phone, open up Magisk Manager.
Click the Magisk Install button as shown below.
Then Select and Patch a File.
Go look for your boot.img you previously copied to your phone and pick it.
Click Let's go! and wait for Magisk to complete the process!
Step 6 - Link your phone to your PC, and grab the file the Magisk Manager created. It's located in your downloads folder, called magisk_patched.img.
Step 7 - Paste it where your ADB & Fastboot (Platform Tools) are located, along with the vbmeta.img file located in Stock ROM's images folder from earlier, where you grabbed the original boot.img.
You should now have a folder like this with:
adb(.exe)
fastboot(.exe)
magisk_patched.img
vbmeta.img
Extra files from the platform tools
Step 8 - Alright, we're ready to root! Turn off your phone, and get in fastboot mode like we did during the bootloader unlocking (Power + Volume Down).
Step 9 - Link your phone to your PC with the USB cable if not done already.
Step 10 - Shift + Right click in an empty space inside the folder we prepared in Step 7, and click Open Command window here.
Inside the Command window, input the following commands line by line, in order.
Code:
adb reboot bootloader
fastboot devices
And make sure your device shows up, should be a bunch of numbers and letters, a couple spaces, and fastboot.
If nothing does, go back to Step 8 and try again.
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash boot magisk_patched.img
fastboot reboot
You're done! Your phone will reboot, hopefully, without a hitch! Open up Magisk Manager, and check that it's installed.
That said, you will have issues leaving it like this. You need to hide the fact that your phone is rooted, there's no downside to doing it.
Check out the Passing SafetyNet tutorial further down below, it's quick and easy.
Getting EdXposed (Not recommended unless really needed, requires Magisk)
I very much do not recommend to EdXposed your phone unless you have a very good reason for it. It's a pain to pass SafetyNet, doesn't get updated as often as it could/should and has very niche use cases for which it's worth it.
That said, I do include it here for people who know what they're getting into and want the up-to-date instructions on how to do it.
Tutorial:
This procedure requires to be rooted with Magisk. See the tutorial above.
Step 1 - Inside Magisk Manager, go to the Modules tab (4th icon), click the search button (bottom right) and search Riru.
Step 2 - Install the Riru (Riru - Core) module, Activate it and Reboot.
Step 3 - Install the Riru - EdXposed (YAHFA or SandHook, both work fine) module, Activate it and Reboot.
Step 4 - Download and install the latest EdXposed Manager in the exact same way you did with Magisk Manager.
Step 5 - Open it up, it should say EdXposed Framework is active!
You're done! You should now be able to install EdXposed modules.
That said, you will have issues leaving it like this. You need to hide the fact that your phone is EdXposed.
It's a bit more complicated than hiding Magisk, but it's doable! Check out the Passing SafetyNet tutorial further down below, it's quick and easy.
Passing SafetyNet (Only possible with Magisk. Not with SuperSU on GSI's)
Tutorial:
For Magisk Rooted PhonesEnable Magisk Hide inside Magisk Manager's settings.​For EdXposed PhonesAgain, I highly recommend not EdXposing your phone and sticking to just Magisk if you can help it.
You should also know that this method will show you're passing SafetyNet inside Magisk but it's a pain to do and isn't as well hidden as Magisk alone.
Step 1 - Do the step for Rooted phones listed above if not done already.
Step 2 - In EdXposed Manager, get the HiddenCore Module and activate it.
Step 3 - Now, in the side-menu: Compat List > tick HiddenCore Module.
Step 4 - Then, go to Settings > Framework > Enable "App List mode".
Step 5 - Finally, Applications(Black List) and tick: Android Services Library, Chrome, Google Play services, Google Play Store, Google Services Framework​Reboot and enjoy! You're all set and SafetyNet should pass just fine.
Installing GSI's (Custom ROMs)
Tutorial:
Step 1 - Pick your poison in the Treble Forums!
Check the top of this thread if you want to see my recommendations with links to them.
Step 2 - Download the chosen ROM, A/B Arm64 version (usually nicknamed b), with (g) or without GApps (v), rooted (S) or not (N), that's entirely up to you.
It should be an .img.xz file, extract it and you'll get an .img file.​
You're ready to flash. Make sure to backup your phone's data before continuing on with this tutorial, as wiping it is required for installation!
Step 3 - Put your phone into fastboot mode (Power + Volume Up) and link it to your PC.
Step 4 - Move the .img file you downloaded to your ADB & Fastboot (Platform Tools) folder, and rename it to system.img.
Step 5 - Shift + Right click in an empty space inside the folder, and click Open Command window here.
Inside the Command window, input the following commands line by line, in order.​
Code:
fastboot reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot flash system system.img
fastboot -w
fastboot reboot
Your phone will now reboot on its own, using the new ROM you picked earlier, set it all up and enjoy!
Relock your bootloader
Tutorial:
Step 0 - Back to stock ROM by flashing it in stock recovery.
Step 1 - Download the unlock tool again to apply to exit the in-depth test.
Step 2 - Click “Apply to exit in-depth test”. You should manual operation enter the Fastboot mode(Press both the Volume up button and the Power button when power is off).
Step 3 - In the Fastboot mode, use the engineering command below on your PC to re-lock the bootloader.
- Enter the command: adb reboot bootloader
- Press “Enter” on your keyboard
- Enter the command: fastboot flashing lock
- Press “Enter” on your keyboard​Step 4 - Press the Volume Up button to select the “Lock bootloader” option (or press the Volume Down button to select “Do not lock bootloader" and keep it unlocked).
Step 5 - Then enter command fastboot reboot. The phone will reboot and exit the in-depth test mode. All user data on the phone will be erased - we recommend you perform a data backup prior to applying.
Frequently Asked Questions (FAQ)
Q: Will unlocking my bootloader void my warranty?
A: No, it will not. Unless you brick your device.
Q: Hey, I rooted/edXposed my phone, and now Netflix won't even open, or doesn't work properly, what's up with that?
A: Well, fortunately, there's an easy fix if you have Magisk. Install the liboemcrypto disabler Magisk module, activate it and reboot.​
Q: I tried unlocking my bootloader but, PC doesn't detect my phone, even though it's in fastboot mode and connected. Help?
A: Here are some things you can try:
- Try another USB port.
- Try another USB cable.
- Install the Realme USB Drivers manually from here.​
Q: Alright, I did a bunch of manipulations but something went wrong, or I'm tired of it, how do I reset everything, etc..
A:
Step 1 - Backup all the data you might have on your phone to restore it after the manipulation!
Step 2 - Download the stock ROM corresponding to your region from Software Update - realme.
Step 3 - Put the stock rom in your mobile Internal Storage or in Memory Card.
Step 4 - Put your device into recovery mode (Turn it off, then Power + Volume Down) and flash that in recovery.
Step 5 - Reboot to stock rom, all good and fresh!​

[GUIDE/TUTORIAL/HOWTO] LG G2 D802 stock to Android 11

[GUIDE/TUTORIAL/HOWTO] LG G2 D802 stock to Android 11
[GUIDE/TUTORIAL/HOWTO] LG G2 LG-D802 (Unlocked/International) stock to Android 11 R/LineageOS 18.1 with all files included
This detailed step-by-step guide helps you transform your LG G2 D802 to a powerful one with Android 11.
I wrote this because everything I read was incomplete or outdated.
Make sure your phone is a compatible LG G2. In Android, go to Settings > General > About phone > Hardware information > Model number is LG-D802.
If not, quit this tutorial.
### I'll make a few comments like this, PLEASE READ THEM !
### DO NOT CHECK FOR ANDROID UPDATES (we'll see this later).
### Netflix and Disney+ won't work.
CHANGELOG
v1. Initial release for Android 11
1) DOWNLOAD
- djibe LG G2 d802 pack: https://bit.ly/djibe-lgg2-d802-pack
(contains LG USB drivers + LG UP firmware flash tool + LGG2-D802-OneClickRootRecoveryV1.1 by somboons + TWRP 3.3.1-0 by blastagator + Magisk root).
Unzip files.
+ ROM LineageOS 18.1 Official: https://forum.xda-developers.com/t/rom-lineageos-18-1-official-d80x-unofficial-ls980-vs980.4186013/
Download latest build here: https://download.lineageos.org/d802
+ BiTGapps Package ARM 11: https://github.com/BiTGApps/BiTGApps-Release/releases
or MindTheGApps ARM 11: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
+ Charge phone to 100%
No command line will be used ! No need to be a geek.
2) INSTALL USB DRIVERS
Install LG USB drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode (Media device MTP option).
Collect all .jpg or .mp4
Use an app like Backupyourmobile to backup texts, contacts, etc.
Make sure Google account is synced, WhatsApp backups etc...
Check that backup is located on microSD card.
Then copy the backup on your PC.
Go to Settings > General > About phone > Status > IMEI.
Note EMEI (15 digits, just in case) !
3) UPGRADE TO ANDROID 5 LOLLIPOP
Check OS version: go to Settings > General > About phone > Software information
- If Android is 4.4.2: follow this chapter
- If Android is already 5: move to next chapter
Note down Software version. Mine is D80220g-208-01
Download firmware from: https://lg-firmwares.com/lg-d802-firmwares/
Download firmware for Android 5.0.x Lollipop having the generic Region (and no brand) for your country.
UK or English spoken (use this by default): https://lg-firmwares.com/downloads-file/1176/D80230d_00
France: https://lg-firmwares.com/downloads-file/680/D80230d_00
Germany: https://lg-firmwares.com/downloads-file/572/D80230d_00
Italy: https://lg-firmwares.com/downloads-file/1289/D80230d_00
During download, go to folder LGUP_LG/ and install LGUP_Install_Ver_1_14_3.msi.
Then install LGUP_8974_DLL_Ver_0_5_CODEFIRE.msi
Back to the phone: power it off.
Enter Download Mode: hold Volume+ and plug USB into your PC,
### Or try with Volume+ + Power. Hold both 3 seconds, connect to USB and release.
release buttons when Download mode screen is displayed on phone.
### If Download mode is missing, you'll have to use AutoRec (thx @lgkar): https://forum.xda-developers.com/t/autorec-kitkat-recovery-installer.2715496/
### Warning all data will be erased from phone, make sure to backup everything.
Launch LGUP from Windows Start menu.
It will detect D802.
Click on UPGRADE and in File Path select the firmware with *.kdz extension you downloaded.
Click on Start.
Don't touch anything. Lock the kids in the basement during flash.
Phone will restart automatically to ... Android 5 !
Disconnect phone from USB and close LGUP.
3) ROOT LG G2 AND FLASH TWRP 2.8 RECOVERY
We need root to flash a custom recovery.
No bootloader unlock is needed on LG G2.
Enable USB debugging: go to Settings > General > About phone > Software info.
Tap 7 times on Build number to unlock Developer options.
Back to Settings > General > Developer options.
Check ON USB debugging option.
Connect phone to USB again.
I prefer to disable antivirus for root (we never know about false positives).
Go to folder LGG2-D802-OneClickRootRecoveryV1.1/
and double click on OneClick_ROOT_RECOVERY.bat (by awesome @somboons).
When Windows command is displaying:
Code:
Waiting for device...
Allow USB debugging from the phone and check Always allow from this computer.
Root will continue.
When command prompts: Please press Ctrl+C ...
From keyboard, press Ctrl + C combo.
Then: N
### If you exit command or fail at this step, like me, just power phone off (long press Power).
When phone restarts, you will see that SuperSU app is installed. Phone is rooted.
7) UPDATE TWRP RECOVERY TO 3.3
Reboot to recovery: power off phone.
Then hold Power + Volume down until LG logo shows up, release buttons and then press again until recovery shows up.
### Like me you fail booting to Recovery ? Let phone start.
### Go back to LGG2-D802-OneClickRootRecoveryV1.1/ folder.
### In the Windows address bar, enter: cmd and press Enter.
### It will launch a command prompt in the active directory.
### Then enter:
Code:
adb reboot recovery
### Phone will restart to recovery.
Welcome to TWRP 2.8.
Normaly you can see LG-D802 device from Windows explorer (besides your hard drives).
### If not, go to Mount, check Data and tap on Enable MTP.
Copy twrp-3.3.1-0-d802-bump-blastagator-signed.zip to root folder of phone (called Internal Storage).
From TWRP recovery, go to Install > twrp-3.3.1-0-d802-bump*.zip and Swipe to Flash.
Go back to Home menu > Reboot > Recovery.
Recovery restarts to brand new 3.3 version.
Check Never show this screen during boot again and Swipe to Allow Modifications.
Go to Settings > General (first tab).
Make sure 3rd option "Use rm -rf instead of formatting" is UNCHECKED.
9) WIPE PARTITIONS
Disconnect phone from PC.
Now go to Wipe > Advanced Wipe.
Select Dalvik / ART Cache, System, Data, Internal Storage and Cache and Swipe to Wipe.
Go to Wipe > Format Data.
Type: yes and confirm with bottom right icon.
Tap on Home button > Reboot > Recovery > Swipe to Reboot.
### Always uncheck "Install TWRP app" options.
10) FLASH ANDROID, GAPPS AND MAGISK ROOT
On restart, check Never show this screen during boot again and Swipe to Allow Modifications.
Connect phone to PC.
Copy ROM + BITGAPPS + Magisk on Internal Storage folder.
Disconnect phone.
Go to Install > select lineage-18.1*.zip, and Add More Zips,
then bitgapps*.zip and Swipe to confirm Flash
Be patient.
### If it fails, install zips 1 by 1.
Then back to Home > Reboot > Recovery.
### Always uncheck "Install TWRP app" options.
OPTIONAL: go back to TWRP Install > Magisk*.zip
When done message prompts, tap on Wipe Cache/Dalvik and Swipe to Wipe, wait.
Disconnect phone from PC.
Then tap on Reboot System.
Let the phone boot (about 5 minutes).
11) ANDROID 11
Configure Android as you like.
### Over The Air (OTA) updates: download file > reboot to recovery > flash ROM and GApps > Wipe cache > Reboot
Reflash BitGApps after each update. Not needed with BitGApps. Thx to @Pierfai
- Netflix and Disney+ don't work
- Go to Settings > About.
At bottom, tap 7 times on Build number. You activated Developer options.
Go to Settings > System > Avdanced > Developer options.
Set Windows animation scale, Transition animation scale and Animator duration scale to 0.5x.
- Double Tap to Wake (D2W)
Go to Settings > Display > Advanced and activate Tap to wake.
- Tap to Sleep
Go to Settings > Display > Advanced and activate Tap to sleep.
Double tap on status bar to sleep.
- Pixel gestures
Go to Settings > System > Advanced > Gestures > System navigation, select Gesture navigation.
Enjoy,
djibe
Thanks: @aleasto, @somboons, @blastagator, LG Fans site, LineageOS team, BiTGapps team, TWRP team, topjohnwu
Thank you very much for the guide!
Walden0 said:
Thank you very much for the guide!
Click to expand...
Click to collapse
Hi, glad you liked it !
Hi djibe,
thank you for this great guide. I followed it with a little extra work: I had to run AutoRec once to re-enable the download mode on the LG G2 d802 which was on stock 4.4.2 (also LGUP was not detecting my device: used Uppercut to got it recognized correctly). Second issue might be due to my own stupid way of trying all kind of tools to get the download mode working (again Autorec helped me --> Just in case someone else has similar issues).
Only real problem I had with your guide was at point 11 after installing LineageOS: The device got stuck in a bootloop to TWRP. I guess I solved it following this note:
https://forum.xda-developers.com/t/...thermal-f2fs-2019-12-23.2898705/post-55892416
WARNING 2: DO NOT ENCRYPT F2FS - ROM and RECOVERY will BOTH bootloop and you'll be doing back to stock method!!!
If you want to use F2FS:
1) Make sure your kernel and ramdisk support f2fs (the dev of your ROM/kernel should have f2fs support noted). Dorimanx stock kernel as well as many AOSP kernels have full f2fs support.
2) Install and boot into my recovery.
3) Go to Wipe, Advanced Wipe, select /data, then click Change Partition Type. Select f2fs, and it will convert. Repeat this process for /cache.
4) Reboot the recovery, NOT reboot to system. DO NOT DO ANYTHING ELSE UNTIL YOU REBOOT RECOVERY!!!
5) Reboot OS. That's it! You're ready to go.
Click to expand...
Click to collapse
Actually I didn't want to encypt anything (not sure where I should have done this???) or have a clue what are the pros/cons of using F2FS but I converted the mentioned partitions and installed LineageOS agian: Working without boot loop!
What I recognized during the installation in TWRP: I got a red error message "E:Unable to decrypt FBE device" do I need to worry about this (basically I just want a fresher Android and the usual Gapps on the device than 4.4, nothing fancy)? Or did I miss an important point in you guide?
Thank you!
Edit: I guess I forgot to reboot between installing Lineage, Bitgapps and Magisk! --> no need to format the /data and /cache partition
I found that at step 10
"Install > Magisk*.zip
When done message prompts, tap on Wipe Cache/Dalvik and Swipe to Wipe, wait.
Disconnect phone from PC.
Then tap on Reboot System."
When we choose Reboot System, we have to uncheck those two boxes and click DO NOT INSTALL. Otherwise it will do a TWRP bootloop.
After I figure this out, I can successfully install Android 11 on my G2.
Thank you for your guide~
Hi guys, is this guide fully working ? I've just bought an old Lg G2 for my dad and I'd like to try flash android 11.
TapaSte said:
Hi guys, is this guide fully working ? I've just bought an old Lg G2 for my dad and I'd like to try flash android 11.
Click to expand...
Click to collapse
Yes it works. But you may have to take note of my previous message.
I just flashed two LG G2 last week. Happily using now.
Psix73 said:
Yes it works. But you may have to take note of my previous message.
I just flashed two LG G2 last week. Happily using now.
Click to expand...
Click to collapse
Thanks guy, which recovery Have been you using ?
For what concerns bitgapps is it ok to download the 11.0.0 R45 ?
Hi, just updated tutorial thx to your reports.
djibe89 said:
Hi, just updated tutorial thx to your reports.
Click to expand...
Click to collapse
Thanks, well done.
One question: my G2 is a D80220h-EUR-XX
Which offical LG firmwares have I to download among the several options ?
TapaSte said:
One question: my G2 is a D80220h-EUR-XX
Which offical LG firmwares have I to download among the several options ?
Click to expand...
Click to collapse
Is it Austrian ?
You can grab an English one: UK or English spoken: https://lg-firmwares.com/downloads-file/1176/D80230d_00
Ok... after a few problems to enter in download mode (it is needed to press only up volume and then connect to pc, not power button + up volume) I've succesfully flashed Android 5 and I'm ready to follow the sequent steps...
djibe89 said:
Is it Austrian ?
You can grab an English one: UK or English spoken: https://lg-firmwares.com/downloads-file/1176/D80230d_00
Click to expand...
Click to collapse
Bought in Italy but 6NE version (North Europe).
Now I can root, install twrp and then try to flash android 11...
Cool. Enjoy
It seems I'm unable to root...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TapaSte said:
It seems I'm unable to root... View attachment 5530665
Click to expand...
Click to collapse
It looks like computer is searching an USB device.
Go to Windows Device Manager to check if drivers are correctly installed.
djibe89 said:
It looks like computer is searching an USB device.
Go to Windows Device Manager to check if drivers are correctly installed.
Click to expand...
Click to collapse
How can be a driver issue if before files has been successfully pushed in phone and that it is correctly rebooted ?
The COM port can be tricky.
See Windows Device Manager
djibe89 said:
The COM port can be tricky.
See Windows Device Manager
Click to expand...
Click to collapse

[ROM][Official] Kali NetHunter for the TicWatch Pro 3 WearOS

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I present to you: Kali NetHunter for the TicWatch Pro 3 WearOS
Kali NetHunter is an Android ROM overlay that turns an ordinary phone into the ultimate Mobile Penetration Testing Platform. Now it's available for your smartwatch with some limitations.
The overlay includes a custom kernel, a Kali Linux chroot, an accompanying Android application, which allows for easier interaction with various security tools and attacks.
Beyond the penetration testing tools arsenal within Kali Linux, NetHunter also supports several additional classes, such as HID Keyboard Attacks, BadUSB attacks, WPS attacks, and much more. For more information about the moving parts that make up NetHunter, check out our NetHunter Components page.
NetHunter is an open-source project developed by Offensive Security and the community.
All variants are supported (TicWatch Pro 3 GPS/LTE/Ultra GPS/Ultra LTE) with a generic installer as of now. This means there's no custom kernel yet, however all the features work from the TicWatch Pro, except BadUSB.
## 1. Unlock the bootloader
- Connect your watch to your PC with a DIY USB cable or a 3D printed data dock, and fire up a terminal.
- If you have set up your watch on the phone you can access settings, otherwise hold both buttons for a few seconds on the welcome screen.
- Enable developer settings by going to System -> About -> tap Build number 10 times
- Enable ADB, re-plug USB and accept debug from PC
- Reboot into bootloader with `adb reboot bootloader` from the terminal
- Unlock bootloader with `fastboot oem unlock`
## 2. Flash TWRP, WearOS image, Magisk, dm-verity disabler
Please note Magisk 24.3 is recommended.
- Again enable ADB, and reboot to bootloader with `adb reboot bootloader`
- Disable vbmeta verification: `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img`
- Flash recovery `fastboot flash recovery recovery.img`
- Boot into recovery by selecting it with the side buttons (switch with bottom one, select with upper button)
- Select Wipe -> Advanced Wipe -> select Format Data
- Reboot to recovery
- Select "Install -> ADB Sideload"
- Flash OneOS with `adb sideload`
- Flash Ultra addon with `adb sideload` only if you have an Ultra watch
- Flash Mobvoi Apps with `adb sideload`
- Make a copy of your Magisk apk file to Magisk-v24.3.zip
- Flash Magisk with `adb sideload`
- Flash Disabler with `adb push Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip /sdcard/` and Install via TWRP
- Reboot & do initial setup (pair with your phone through WearOS app)
## 3. Finalise Magisk app to finish the rooting process
- Finalise Magisk installation with app `adb install Magisk-v24.3.apk`
- Launch Magisk Manager
- You might want to disable auto-update, set grant access in auto response, and disable toast notifications for easier navigation in the future
## 4. Install NetHunter
- Reboot to recovery
- Select Install -> ADB Sideload
- Flash NetHunter image with `adb sideload`
- Reboot
- Start NetHunter app & chroot
- Reboot
## 5. Set NetHunter watch face
- Install Facer onto your phone and watch from Play Store
- Search for NetHunter
- Select & Sync
### Enjoy Kali NetHunter on the TicWatch Pro 3
## Downloads
- Magisk
- TWRP images
- OneOS ROM, Mobvoi apps, Ultra addon
- vbmeta image
- dm-verity and forceencrypt disabler
- NetHunter zip
## Additional recommended apps
- TotalCommander: useful for selecting eg. a Ducky script, use "adb install" method
Download link: https://www.totalcommander.ch/android/tcandroid323-armeabi.apk
## Supported features
- Kali services
- Custom Commands
- MAC Changer
- HID Attacks
- DuckHunter
- Nmap Scan
- WPS Attacks
## Upcoming features (not guaranteed)
- Nexmon, as the chipset is supported, needs some time
- Bluetooth Arsenal (internal bluetooth via blueblinder, as carwhisperer fails to r/w when SCO channel is connected)
- Router Keygen (to be optimised)
- Hijacker (if nexmon succeeds)
- Mifare Classic Tool (need to build OS with android.hardware.nfc enabled)
## Hardware limitations
- Power resource is not enough for any external adapters, although this kernel might support Y cable in the future!
WearOS version:
XDA: DevDB Information
Kali Nethunter, Kernel & ROM for the TicWatch Pro 3
Contributors
@yesimxev
Source Code: https://gitlab.com/kalilinux/nethunter/
Reserved
Thank you so much for this
Is it working on twp3ultra?
And which stockrom img incase anything went wrong.
Thank you in advance
nelikp said:
Thank you so much for this
Is it working on twp3ultra?
And which stockrom img incase anything went wrong.
Thank you in advance
Click to expand...
Click to collapse
Yes it is, use rover for Ultra LTE and rubyfish for Ultra GPS. Link for stock ROMs is above in the OneOS dowbload page, scroll down for stock
yesimxev said:
Yes it is, use rover for Ultra LTE and rubyfish for Ultra GPS. Link for stock ROMs is above in the OneOS dowbload page, scroll down for stock
Click to expand...
Click to collapse
Thank you so much
Waiting my cable from alixpress
May i have the oneos download page sir
nelikp said:
Thank you so much
Waiting my cable from alixpress
May i have the oneos download page sir
Click to expand...
Click to collapse
Everything is there. Just scroll
Achi Shukuteki said:
Everything is there. Just scroll
Click to expand...
Click to collapse
Thanks sir
I found it
Here
Download •OneOS Wear•
wear.revtechs.me
any chance we’ll see a more vanilla rom for those of us that aren’t interested in network penetration etc, would be awesome to see a rom that could re-enable the compass in the ticwatch pro 3 ultra for example
kerode said:
any chance we’ll see a more vanilla rom for those of us that aren’t interested in network penetration etc, would be awesome to see a rom that could re-enable the compass in the ticwatch pro 3 ultra for example
Click to expand...
Click to collapse
I think the general forum would be more appropriate for that question. I was interested in the same thing, though.
kerode said:
any chance we’ll see a more vanilla rom for those of us that aren’t interested in network penetration etc, would be awesome to see a rom that could re-enable the compass in the ticwatch pro 3 ultra for example
Click to expand...
Click to collapse
Well that goes onto my list next to the enable android.hardware.nfc + android.hardware.sensor.compass in the ROM for building OneOS if it's not disabled in kernel
Edited:
My bad, kali chroot needs to be run first. Succes now
Just flashed nethunter to my twp3 but when i start nethunter app somehow there was a pop up saying "chroot is not yet installed".
Should i sideload nethunter zip again?
Can i flash zip file via twrp after push the file to the watch?.
Thanks
enter2explore said:
Edited:
My bad, kali chroot needs to be run first. Succes now
Just flashed nethunter to my twp3 but when i start nethunter app somehow there was a pop up saying "chroot is not yet installed".
Should i sideload nethunter zip again?
Can i flash zip file via twrp after push the file to the watch?.
Thanks
Click to expand...
Click to collapse
If all the steps were followed correctly, then show me /tmp/recovery.log after flashing again. Use pastebin please
yesimxev said:
If all the steps were followed correctly, then show me /tmp/recovery.log after flashing again. Use pastebin please
Click to expand...
Click to collapse
Hi @yesimxev
Already solved, it just the matter i forgot to start chroot. Work normally now.
Thanks
yesimxev said:
Well that goes onto my list next to the enable android.hardware.nfc + android.hardware.sensor.compass in the ROM for building OneOS if it's not disabled in kernel
Click to expand...
Click to collapse
awesome mate, looking forward to it!!
managed to install and chroot
but how to wps attack?
any guide would appreciate
TIA
Im stuck when running command fastboot oem unlock all I get it waiting for any device and thats it.
nemzzy668 said:
Im stuck when running command fastboot oem unlock all I get it waiting for any device and thats it.
Click to expand...
Click to collapse
Check the connection.
Achi Shukuteki said:
Check the connection.
Click to expand...
Click to collapse
Connewction is fine, ADB works, windows then also detects it when it reboots. Just fastboot that sticks. Using Windows 11
nemzzy668 said:
Connewction is fine, ADB works, windows then also detects it when it reboots. Just fastboot that sticks. Using Windows 11
Click to expand...
Click to collapse
Oh hmmm. Im on Win10. I'll leave it to the forum with that one. Unless you want to use a live Linux distro, grab the tools, you already have the files, and try that way.
Run fastboot devices first after reboot to bootloader..make sure ur watch detected.
Otherwise check ur driver

How To Guide [Close](Dual Boot)Stock ROM Android11 with VegaBobo DSU Sideloader v.2 .

*Didn't work with magisk and A12.​-》Test GSIs with DSU First​ IF It works well
-》 Use Native CustomAP (permanent installation)
If new GSI error​-》Just Reboot (back to Stock)
First, try to install the VegaBobo App apk only, if that works well for you, nice, keep using it!
!Happy using try to test New GSIs Now
-》-》Because of very boring about new installation for testing New GSI A13. ( used too many hours for restored back, too long for create our CustomAP.)​then find the easy way to....bypass​A simple app made to help users easily install GSIs via DSU's Android feature.
-》-》This process don't need CustomAP, No TWRP, No Fastboot.)​Except want to mod System.img by using CustomAP.
-》-》 I will shortly explain Step by Step tutorial here! ​-》》SAM didn't supported DSU mode with its devices, it is difficult to used DSU together with Stock Sam ROM.
We highly recommend using this app with Stock ROM, some Custom ROM builds may also work fine.
Everyone can sideload New GSI for testing without erasing your based OS Android Firmware. or Used it to be your second OS. (2IN1) OR MORE depending on Storage space.​***There are some side-effect, but no time to read all Dev documents.
Thank to VegaBobo​This is not DSU inside your Developer Options​ (DSU implement) then you can choose and select any GSIs ​( local not in Google Server) that you love but it required your Unlocked Bootloader device.​
->>Pleases read Doucuments of Developer during using my tutorial ​
GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feature.
A simple app made to help users easily install GSIs via DSU's Android feature. - GitHub - VegaBobo/DSU-Sideloader: A simple app made to help users easily install GSIs via DSU's Android feat...
github.com
this video show , i have another GSI running along with Based stock ROM.
More than Dual Boot ​( GSIs + Stock A11 ROM) ?​Requirements​
Unlocked Bootloader
VegaBobo DSU Sideloader app
GSI ( A11, A12, A13) only [not lower than version of based AndroidOS.11]
GSI Example will be "ArrowsOS-12.1-arm64_bvN-Unofficial (2.55GB ) extracted .img because there are limited 20-40% rule for working storage.(Storage of Our Tab a7 lite = only 32 GB (may be happy with your 64 GB) , about Stock may occupier about 10 GB with A11).
After this i will calculates restrict storage area for 32 GB.
if you want to test GSI with ROOT , recommend bgS or bvS varient. (if you don't known about "variant bgS , bvS please consult GSI Dev.)
Step
1. Download DSU Sideloader app at https://github.com/VegaBobo/DSU-Sideloader ( New V2.01)
you want below variant.
app-release.apk: DSU Sideloader application, recommended, support both, rooted and unrooted devices.
I will uses Unrooted mode. (clean testing)
LADB ( local adb shell app) >>local-adb shell.zip (my attach)
Not known about LADB look this.
2. If you are working with Tab A7 Lite Android 12 , must downgrade to STOCK Android 11 ( Checking your Bootloader version before downgrading.)
(All variant VegaBobo DSU Not working on Stock A12 of Tab A7 Lite. Test with my SM-T225)​
3. Install ladb.apk > then open Developer options>Wireless debugging >Pair device with piring code , and connected your tab with wifi internet.
-Open multitask 2 windows > one for LADB , the other for Pairing Code
-Pair ladb with (port number and pairing code)
4.Download GSI ( any you like but must obey the rule 20-40% the rest capacity of your storage.)
->My test drive for working booted GSI list is... ( All supported exFAT) ( Some need to mod offline-charging.)
Note: I don't have any problem with FAT32 , just want to fullfill my sd_card.
-》List of Android 12, 12L​
✓ Pixel Experience Plus 12.1 v414
Release Pixel Experience Plus 12.1 v414 · ponces/treble_build_pe
Sync with June sources of PE+ Sync with AOSP 12.1 v414 (thanks @phhusson)
github.com
✓ SparkOS
Gsi_projects - Browse /v415-Aug/SparkOS-12.6-Experimental at SourceForge.net
sourceforge.net
✓ ArrowOS
Gsi_projects - Browse /A12.1/ArrowOS-12.1/19102022 at SourceForge.net
sourceforge.net
✓ crDroid
Gsi_projects - Browse /A12.1/crDroid-8.10/16102022 at SourceForge.net
sourceforge.net
✓ CherishOS
xiaomemeindex.com
✓ SuperiorOS
xiaomemeindex.com
✓ Project Blaze
Release v20221023 · ChonDoit/treble_blaze_patches
CHANGELOG | Initial and latest Release | Fixed Safety Net | Fixed things which exist on source but not on final product (Amazing, right?) | Broken as expected | Enjoy as it or GTFO Why so big image...
github.com
✓ AOSP PHH
Release AOSP 12.1 v415 · phhusson/treble_experimentations
July security patch
github.com
Example
[Close] Pixel Experience 12.1 v416 + Plus Final version
Download https://github.com/ponces/treble_build_pe/releases/download/v416/PixelExperience_arm64-ab-slim-12.1-20221117-UNOFFICIAL.img.xz Final version Sync with November sources of PE Sync with AOSP 12.1 v416 Fix boot on Mediatek devices exFAT...
forum.xda-developers.com
LIST of BOOTed BUT NOT SUPPORTED exFAT GSIs
✓ lineage-19.1-20221011-UNOFFICIAL-arm64_bvS.img.xz
Andy Yan's personal builds // GSI - Browse /lineage-19.x at SourceForge.net
sourceforge.net
-》List of Android 13​PixelExtended 13
https://sourceforge.net/projects/thegsis/files/PixelExtended/PixelExtended-13-arm64_bgN-UNOFFICIAL.img.xz/download
5. Pre-Setting up DSU.
- install and configure
- must select Enable Unmount SD and Keep screen on during process.
- Operation mode will detected rely on you have root or not. if not it use ADB
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Warring about storage restriction ( Let you install anyway but finally fail.)
n in storage Only ) ***Don't used sd-card final process will fail. ( warring for 32GB device)
configured before install GSI ( warning Extract you GSI IMG file to SD CARD for save your internal storage.) (if not) Final process will fail. again.
Don't set specific Userdata size if you used big GSI file size.《《 let it be (default 2GB ) ,cause we use to boot testing not for real use.
Let's app auto calculate size for Image size.
-》》 if you plan on using the GSI long term make sure to set your userdata to a reasonable size because your gonna want to install apps and download things.
( App will restrict to uses your storage itself with maximum size ,depened on remain space.)
(if not) Final process will fail. again.
Extract GSI Downloaded file. >>>to keep in your sd card.>> in format of IMG (Save your installation time )
Select your GSI for installing by click inside installation box.
Installation process beginning.....show you progress status.
6. How to disconnect your SD-Card during installation process.Why ? How?
(if not ... DSU can't success install but echo..to debuging log... not installed.
(if not ) Final process will fail. again.
Very important step , normally it automatical happen.
A lot of failure , no warning about you errors . except final debugging log. bra bra.
App will disconnect sd card when finish preparing image file. and reconnect automatically also.
Step ( in this process)
1>Select img file to install.
*Remember to use GSIs compatible with your architeture, vndk implementation..
2 >show you configured before installation.
3>preparing image file (Don't close display or leave out) ** important
ADB: Default operation mode when other modes aren't available
Only prepare selected image to be installed via DSU system-app
Requires adb command to start installation (which will invoke DSU system-app to install the prepared file)
Took your time about 7-10 minutes ( set screen timeout longer + don't turn away from this page.)
If no spaces left
4 >(you will be prompted to run a shell script to invoke DSU installation activity)
- Click button See commands and copy text.
5 >copy command text
- Cluck button Copy text in below box
6 >paste Copy command from 5 to execute with LADB
7> Result of command. Unmount SD Card.
8.>Once installation finishes, Android creates a persistent notification allowing you to boot into "Dynamic System" (GSI installed via DSU), and you can boot into installed GSI, without touching your system partition, or breaking the "real userdata" partition.
THE LAST PROCESS OF INSTALLATION.
( Dynamic system updates) you must waitting till Discard & RSTART BUTTON EMERGED.
Final processing
Select -》 restart button togo into new GSI environment if it can boot.
if not >> DSU will reboot into normal Stock system , (you must discart to delete remain failure system yourself)
Select -》 discard button from noti menu to destroy this system and came back to normal Stock system.
​7. no need step 4-6​Not Recommend
-》Shizuku. ok it the same thing .LADB​
Shizuku: When running app with Shizuku (Obtained when Shizuku permission is granted)
Same as ADB, however, it does not require to run any adb command
Support tracking installation progress ¹ ² ³
Support installation diagnostics (if a common error is detected, it may give you useful information) ¹ ³
AFTER INSTALLED​I will collect storage usage information. because this is one thing that break for GSI Bootable problem beside of GSI Compatible Problem itself.
Maximum used storage.
Step to uses Sticky Mode​( make Dual Boot OS)​** Must reboot dynamic system first.
by click restart button of DSU notification. setting up new GSI and click restart DSU for caming back to Based System from notification menu.
1. enable by command
Code:
gsi_tool enable
2. Restart device. ( *not uses restart DSU button at notification.) Uses device power-off btn.
3. from now on when we restarts device it will bring you to GSI OS not back to Base OS.
4. How to exit this mode. boot to base OS (by click restart button from DSU update Notification) when you came back to based OS then use this command
Code:
gsi_tool disable
Explain in details​Multiple boot cycles (until discarded) by enabling sticky mode, or have it used for only one boot cycle by disabling sticky mode.​**The Sticky Mode**​(This is native features of Google DSU.)
if you don't use the sticky feature, once you reboot the phone/tab it goes back to your regular stock OS or whatever you were running on before and you will lose everything in the GSI that you have not saved to external media/sdcard/cloud.
If you use the sticky feature you can reboot the tab/phone and retain the GSI
installation.
Reboot to Dynamic System. (Stock ROM A11)
use this command on adb:
Code:
adb shell gsi_tool enable
or from local adb shell:
Code:
gsi_tool enable
or from local rooted shell (eg. Termux on rooted GSI):
Code:
su -c 'gsi_tool enable'
Output using command >
Code:
gsi_tool enable
When sticky mode is enabled (on base OS), device will always boot into dynamic system, instead of device's original system image.
To disable, use the same command, instead of enable , use disable
such as
Code:
gsi_tool disable
Then restart system.(not restart dsu).
Resources:-
Native Google DSU For Developer
--》GSIs can be installed via DSU without root access, using ADB, running some commands, you can read more about installation process here: https://developer.android.com/topic/dsu
Android 13 GSI Download and Install on Your Phone! [Dual boot]
The latest Android 13 Beta is out for Google Pixel devices. In this post, let us see how to download and install Android 13 GSI
shakeuptech.com
Continue..
Troubleshooting.
DSU installation finishes with no errors, but device doesn't boot into installed DSU, what should i do?
It is likely that AVB is preventing device from booting installed images, try flashing disabled vbmeta, check this for more info.
My addition answer: Need to mod system partition before flashing with odin.
* Please double check log.
** USE magisk-patch (boot.img.lz4 + vbmeta.img.lz4) in CustomAP file.tar
For non-rooted devices, Shizuku is a pretty nice operation mode, it support most features with no hassle, however, you need to install and setup Shizuku app in your device.
Shizuku mode : When running app with Shizuku (Obtained when Shizuku permission is granted)
Same as ADB, however, it does not require to run any adb command
Support tracking installation progress ¹ ² ³
Support installation diagnostics (if a common error is detected, it may give you useful information) ¹ ³
I think for DSU unlocking the bootloader isn't necessary
Abish4i said:
I think for DSU unlocking the bootloader isn't necessary
Click to expand...
Click to collapse
its not DSU inside your Developer Options.
Based on what I've read it doesn't since the developer of the App recommends that I'll just try without unlocking it.
&
See if it boots or not ( most likely boot to stock rom only )
P.S Or perhaps it is a third party instead of using directly adb commands hence bootloader part

Categories

Resources