Has anyone managed to root stock 6.0 rom? Mine device is getting stuck at bootloader unlocked warning screen after i flash SuperSU 2.68 or 2.65 using twrp 3.0.0 r2.
Never mind, I didn't know i need custom kernel.
Wchich kernel?
QuiZr23 said:
Has anyone managed to root stock 6.0 rom? Mine device is getting stuck at bootloader unlocked warning screen after i flash SuperSU 2.68 or 2.65 using twrp 3.0.0 r2.
Never mind, I didn't know i need custom kernel.
Click to expand...
Click to collapse
I've got the same problem even with SuperSU 2.7. Wchich kernel should I use?
bump. how to root stock 6.0?
2.71 = http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
2.65 will not work for Marshmallow.
But i thought 2.68 did (have not tested that version yet myself)
I'm not able to root the 6.0 stock ROM (XT1524 EU Retail)
After installing the stock ROM, flashed logo to remove unlocked bootloader warning (works fine) then flashed TWRP (can boot from bootloader menu to recovery) but can't flash Squids kernel or super SU without my moto e getting stuck on the splash screen, it doesn't even try to boot or get to the boot animation
Sent from my MotoE2(4G-LTE) using XDA-Developers mobile app
@ivan39 - Rooting & Persistent TWRP with Stock-ROM, optional: squid kernel only after this
Take a look under this "stone":
Your downloads:
TWRP
http://forum.xda-developers.com/devdb/project/dl/?id=17768
SuperSU (both)
http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
http://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Preparation:
Flash Firmware Stock MM 6.0 EU (no root/tweaks/custom recovery/custom kernel, pure factory reset, original 6.0 ROM)
Start phone > activate Dev options, then activate Devleoper options > OEM unlocking
(Tip: Peter Crawley will stitch around in the boot animation for up to 15 minutes until the Welcome screen shows up - be patient ...)
Copy the 2 downloaded SuperSU-zips to the Internal Storage
___
Root - part 1:
(Re-)start into bootloader / Fastboot Flash mode
Connect laptop/ phone with USB data cable
Open a terminal in your fastboot folder
Check connection with
(sudo) fastboot devices
(<= should give you your phone's serial no)
Boot (NOT flash) already downloaded TWRP from (Linux) terminal with
(sudo) fastboot boot twrp-surnia-3.0.2-r1.img
TWRP > Swipe to go on
TWRP > Main menu > Install > BETA-SuperSU-v2.62-3-20151211162651.zip
TWRP > Reboot System
Open SuperSU App > Settings > should show v2.62
___
Root - part 2:
(Re-)start into bootloader / Fastboot Flash mode
Connect laptop/ phone with USB data cable
Open a terminal in your fastboot folder
Check connection with
(sudo) fastboot devices
(<= should give you your phone's serial no)
Boot (NOT flash) already downloaded TWRP from (Linux) terminal with
(sudo) fastboot boot twrp-surnia-3.0.2-r1.img
TWRP > Swipe to go on (if necessary)
TWRP > Main menu > Install > BETA-SuperSU-v2.71-20160331103524.zip
TWRP > Reboot System
Open SuperSU App > Settings > should show v2.71
___
Make TWRP persistent:
(Re-)start into bootloader / Fastboot Flash mode
Connect laptop/ phone with USB data cable
Open a terminal in your fastboot folder
Check connection with
(sudo) fastboot devices
(<= should give you your phone's serial no)
Flash already downloaded TWRP from (Linux) terminal with
(sudo) fastboot flash recovery twrp-surnia-3.0.2-r1.img
Restart into recovery
(sudo) fastboot boot twrp-surnia-3.0.2-r1.img
In TWRP restart into recovery (again)
TWRP > Main menu > Reboot > Recovery
In TWRP shut down phone
TWRP > Main menu > Reboot > Power Off
Unplug USB & test along ...
optional:
Only then install a squid kernel (i. e. r16 from here)
View attachment 3710216
yelupic said:
@ivan39 - Rooting & Persistent TWRP with Stock-ROM, optional: squid kernel only after this
Take a look under this "stone":
Your downloads:
TWRP
http://forum.xda-developers.com/devdb/project/dl/?id=17768
SuperSU (both)
http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
http://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Preparation:
Flash Firmware Stock MM 6.0 EU (no root/tweaks/custom recovery/custom kernel, pure factory reset, original 6.0 ROM)
Start phone > activate Dev options, then activate Devleoper options > OEM unlocking
(Tip: Peter Crawley will stitch around in the boot animation for up to 15 minutes until the Welcome screen shows up - be patient ...)
Copy the 2 downloaded SuperSU-zips to the Internal Storage
___
Root - part 1:
(Re-)start into bootloader / Fastboot Flash mode
Connect laptop/ phone with USB data cable
Open a terminal in your fastboot folder
Check connection with
(sudo) fastboot devices
(<= should give you your phone's serial no)
Boot (NOT flash) already downloaded TWRP from (Linux) terminal with
(sudo) fastboot boot twrp-surnia-3.0.2-r1.img
TWRP > Swipe to go on
TWRP > Main menu > Install > BETA-SuperSU-v2.62-3-20151211162651.zip
TWRP > Reboot System
Open SuperSU App > Settings > should show v2.62
___
Root - part 2:
(Re-)start into bootloader / Fastboot Flash mode
Connect laptop/ phone with USB data cable
Open a terminal in your fastboot folder
Check connection with
(sudo) fastboot devices
(<= should give you your phone's serial no)
Boot (NOT flash) already downloaded TWRP from (Linux) terminal with
(sudo) fastboot boot twrp-surnia-3.0.2-r1.img
TWRP > Swipe to go on (if necessary)
TWRP > Main menu > Install > BETA-SuperSU-v2.71-20160331103524.zip
TWRP > Reboot System
Open SuperSU App > Settings > should show v2.71
___
Make TWRP persistent:
(Re-)start into bootloader / Fastboot Flash mode
Connect laptop/ phone with USB data cable
Open a terminal in your fastboot folder
Check connection with
(sudo) fastboot devices
(<= should give you your phone's serial no)
Flash already downloaded TWRP from (Linux) terminal with
(sudo) fastboot flash recovery twrp-surnia-3.0.2-r1.img
Restart into recovery
(sudo) fastboot boot twrp-surnia-3.0.2-r1.img
In TWRP restart into recovery (again)
TWRP > Main menu > Reboot > Recovery
In TWRP shut down phone
TWRP > Main menu > Reboot > Power Off
Unplug USB & test along ...
optional:
Only then install a squid kernel (i. e. r16 from here)
View attachment 3710216
Click to expand...
Click to collapse
Thanks so much my friend, will do this at the weekend as I'm busy with work things, I have a 1st gen moto e running cm13 I can use until I got my e2 sorted, thanks so much for taking the time to point me in the right direction
Edit
Stock 6.0 ROM flashed and installed on e2 now
yelupic said:
@ivan39 - Rooting & Persistent TWRP with Stock-ROM, optional: squid kernel only after this
Take a look under this "stone":
Your downloads:
TWRP
http://forum.xda-developers.com/devdb/project/dl/?id=17768
SuperSU (both)
http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
http://download.chainfire.eu/932/SuperSU/BETA-SuperSU-v2.71-20160331103524.zip
Preparation:
Flash Firmware Stock MM 6.0 EU (no root/tweaks/custom recovery/custom kernel, pure factory reset, original 6.0 ROM)
Start phone > activate Dev options, then activate Devleoper options > OEM unlocking
(Tip: Peter Crawley will stitch around in the boot animation for up to 15 minutes until the Welcome screen shows up - be patient ...)
Copy the 2 downloaded SuperSU-zips to the Internal Storage
___
Root - part 1:
(Re-)start into bootloader / Fastboot Flash mode
Connect laptop/ phone with USB data cable
Open a terminal in your fastboot folder
Check connection with
(sudo) fastboot devices
(<= should give you your phone's serial no)
Boot (NOT flash) already downloaded TWRP from (Linux) terminal with
(sudo) fastboot boot twrp-surnia-3.0.2-r1.img
TWRP > Swipe to go on
TWRP > Main menu > Install > BETA-SuperSU-v2.62-3-20151211162651.zip
TWRP > Reboot System
Open SuperSU App > Settings > should show v2.62
___
Root - part 2:
(Re-)start into bootloader / Fastboot Flash mode
Connect laptop/ phone with USB data cable
Open a terminal in your fastboot folder
Check connection with
(sudo) fastboot devices
(<= should give you your phone's serial no)
Boot (NOT flash) already downloaded TWRP from (Linux) terminal with
(sudo) fastboot boot twrp-surnia-3.0.2-r1.img
TWRP > Swipe to go on (if necessary)
TWRP > Main menu > Install > BETA-SuperSU-v2.71-20160331103524.zip
TWRP > Reboot System
Open SuperSU App > Settings > should show v2.71
___
Make TWRP persistent:
(Re-)start into bootloader / Fastboot Flash mode
Connect laptop/ phone with USB data cable
Open a terminal in your fastboot folder
Check connection with
(sudo) fastboot devices
(<= should give you your phone's serial no)
Flash already downloaded TWRP from (Linux) terminal with
(sudo) fastboot flash recovery twrp-surnia-3.0.2-r1.img
Restart into recovery
(sudo) fastboot boot twrp-surnia-3.0.2-r1.img
In TWRP restart into recovery (again)
TWRP > Main menu > Reboot > Recovery
In TWRP shut down phone
TWRP > Main menu > Reboot > Power Off
Unplug USB & test along ...
optional:
Only then install a squid kernel (i. e. r16 from here)
View attachment 3710216
Click to expand...
Click to collapse
THANK YOU SOO MUCH
I was struggling with this yesterday, I can confirm that everything you'v written there is 100% solid.
SuperSU works, recovery works, and I have also flashed kernel - like a charm.
{
"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"
}
Root moto e 2015 (android 6.0)EASY AND FAST)
For root moto e 2015 android M you need recovery and you need flash SuperSu v2.62 (no need custom kernel but squid kernel very cool)
after flash reboot and enjoy^^
use rather handling yelupic below!!!!!
OneDiablo said:
For root moto e 2015 android M you need recovery and you need flash SuperSu v2.62 (no need custom kernel )
after flash reboot and enjoy^^
updates supersu with google play update su binary with apps and reboot
Click to expand...
Click to collapse
Yes, thank you.
But:
You need TWRP-flashable SuperSU v2.62-3 BETA to have "systemless" root (easiest way to have systemless - there are others).
You need TWRP-flashable SuperSU v2.71 BETA installed over v2.62-3 to avoid bugs under Marshmallow (SE Linux permissions). - v2.62-3 is not up to date and will cause failures sooner or later ...
Play Store updates of SuperSU is not recommended (current v2.65 Stable is behind v2.71 BETA).
(And yes, kernel isn't needed to root, but it has been asked, how to install.)
yelupic said:
Yes, thank you.
But:
You need TWRP-flashable SuperSU v2.62-3 BETA to have "systemless" root (easiest way to have systemless - there are others).
You need TWRP-flashable SuperSU v2.71 BETA installed over v2.62-3 to avoid bugs under Marshmallow (SE Linux permissions). - v2.62-3 is not up to date and will cause failures sooner or later ...
Play Store updates of SuperSU is not recommended (current v2.65 Stable is behind v2.71 BETA).
(And yes, kernel isn't needed to root, but it has been asked, how to install.)
Click to expand...
Click to collapse
Thank you for taking time to give us detailed instructions.
My E2 is now rooted, has permanent TWRP and squid kernel r16 installed.
Still on the stock 6.0 ROM for now.
Many many thanks
@yelupic
I made a topic hours after you did saying something similar.
I did not see what you said before because of the spoiler tags.
So i had to scour the web searching for ages to figure it out the hard way
Best i can tell he has given solid advice guys.
I was just not sure 2.71 was ok to install after but suspected it was ok.
I take it he is right and that would be the most up to date way of doing it (with more bugs fixed)
The various different versions of SuperSU are confusing.. i know i had to do a TON of reading myself
Related
Hello guys,
{
"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"
}
Lenovo K6 Power k33a42 is a new device released by lenovo on Dec 16, as many of you have bought this phone i would like to share how this phone can be rooted and how we can install twrp on this phone
UNLOCKING BOOT-LOADER :
Unlocking your Android phones bootloader is the first step to rooting and flashing custom ROMs
WARNING: UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.
INSTRUCTIONS:
1) Download the View attachment K33a42_bootloader_unlock.zip and View attachment drivers.zip zip archive attached here
2) On your device, turn on USB debugging and allow OEMunlocking
if there is no developer options in settings - go to the " Settings -> Device Info " and click on the item " Build number " until the display shows that " you became a developer
go back to the device's main Settings menu and go to Developer options tick "OEM unlocking " and " USB debugging'
when you connect for the first time using debugging via USB you will need to confirm the RSA fingerprint key to trust the PC
3) Extract the Unlock bootloader zip to any directory
4) Connect the device (K33a42) to a PC via USB-cable.
5. Go to the extracted directory and execute Unlock_Bootloader.bat and expect to complete the unlock process.
after the process is completed the boot loader will be unlocked.
INSTALLING TWRP :
1) Extract the folder View attachment TWRP.zip archive to any drive.
2)On your phone, turn on USB debugging (drivers for ADB must be installed).
Connect your phone to a PC via usb-cable
3) You have 2 options either you can try the TWRP (only run one time) or else you can replace the stock recovery with twrp
Use accordingly
run Flash-TWRP.bat (replace stock recovery) or
run Run-TWRP.bat (for one time only).
4) Wait for the phone to boot into TWRP.
You can now disconnect the usb-cord.
Installation is finished.
and also at the starting of the twrp recovery the language will be in Russian because the creator in SevenMaxs from lenovo-forums.ru (I'am looking forward to modify default lang to english)
here is the video which shows how to do so
https://www.youtube.com/watch?v=KOhR92EKD7A
* In the stock firmware Secure Boot is enabled by default , so any changes made to the system partiton lead to a bootloop. Therefore, when you first start TWRP set the system mode to Read Only !
So in order to proceed we need to disable the secure booting in the kernel
Now to disable Secure Boot verification in the boot.img
1. Extract boot.img using twrp backup of boot partition
(you can use android image kitchen for extracting)
2. Make changes in the ramdisk \ default.prop file
change the following line:
ro.secure = 1
to
ro.secure = 0
3. repacked boot.img and flash into the device using twrp.
I know this part may be tough for some uses hence voila i have the secure boot disabled boot image , flash this to boot partition using twrp
ROOTING
Flashing SuperSU zip via TWRP Recovery
Download and transfer the View attachment SuperSU-v2.79-201612051815.zip zip file attached here to your device’s storage.
Boot your device into TWRP recovery.
Tap on Install and select the SuperSU zip file that you transferred to your device in Step 1.
After selecting the .zip file, do Swipe to Confirm Flash on the bottom of screen to begin the flashing process.
Once SuperSU is flashed, you’ll get Reboot System option, select it.
Congratulations! Your device should be rooted now. Look for the SuperSU app in app drawer.
INSTALLING XPOSED
1)Install the xposed installer from playstore
2)Open the installer, and tap the ‘Install/Update’ button. Don’t worry if the app seems stuck here; just give it time and it will eventually show you a Superuser request, which you should make sure to grant and click reboot
Almost all the modules should work on stock rom as it is close to Aosp
modules which i can confirm to work are
: Android N-ify
; Gravitybox
: Bootmanager
:fingers-crossed:
All the credit goes to SevenMaxs
for creating the recovery
and for his guides for proper installation
orginal forum thread
please thank him :fingers-crossed::fingers-crossed:
Thank you
Thankzz.
Sent from my CAM-L21 using Tapatalk
When i try to flash SuperSU-v2.79-201612051815.zip, it says that is corrupt. What can i do ?
Plzz, fix it
Sent from my CAM-L21 using Tapatalk
I found another SuperSU, that worked for me: https://www.androidfilehost.com/?fid=385035244224405790
Thank you again ArjunrambZ and SevenMaxs!
LoverOfLife said:
When i try to flash SuperSU-v2.79-201612051815.zip, it says that is corrupt. What can i do ?
Click to expand...
Click to collapse
i will take a look at the zip, may be upload problem, well any super su zip will work,, this was thw one that i tried
Sent from my VIBE K6 Power using XDA Labs
LoverOfLife said:
Thank you
Click to expand...
Click to collapse
taweng7 said:
Thankzz.
Click to expand...
Click to collapse
taweng7 said:
Plzz, fix it
Click to expand...
Click to collapse
will uplpad today
also the secure boot disabled boot img also
:laugh:
Sent from my VIBE K6 Power using XDA Labs
I'll add adb/fastboot instruction for those who don't use Windows:
Of course you have to enable developer options, adb debug, oem unlocking
UNLOCK:
> adb reboot bootloader
> fastboot oem device-info
> fastboot oem unlock-go
(and... yes you can lock it back with fastboot oem lock)
TWRP:
> fastboot flash recovery /path/to/your/twrp.img
> fastboot oem reboot-recovery
BOOT.IMG:
> fastboot flash boot /path/to/your/ro.secure=0/boot.img
> fastboot reboot
P.S. (to manipulate your boot.img and change the default.prop file under linux you can use abootimg)
ilfastidio said:
I'll add adb/fastboot instruction for those who don't use Windows:
Of course you have to enable developer options, adb debug, oem unlocking
UNLOCK:
> adb reboot bootloader
> fastboot oem device-info
> fastboot oem unlock-go
(and... yes you can lock it back with fastboot oem lock)
TWRP:
> fastboot flash recovery /path/to/your/twrp.img
> fastboot oem reboot-recovery
BOOT.IMG:
> fastboot flash boot /path/to/your/ro.secure=0/boot.img
> fastboot reboot
P.S. (to manipulate your boot.img and change the default.prop file under linux you can use abootimg)
Click to expand...
Click to collapse
you seems to be working on linux, do u have the sources synced on ur pc?
meanwhile i will update the thread to include these to the topic
Sent from my VIBE K6 Power using XDA Labs
ArjunrambZ said:
you seems to be working on linux, do u have the sources synced on ur pc?
meanwhile i will update the thread to include these to the topic
Click to expand...
Click to collapse
I only work on linux. Windows is evil.
I have a big question: why in the default.prop of the russian TWRP.img there is ro.secure=1 ?????
It should be set to 0.
I guess that's why I bricked exactly after flashing Supersu from TWRP...
ilfastidio said:
I only work on linux. Windows is evil.
I have a big question: why in the default.prop of the russian TWRP.img there is ro.secure=1 ?????
It should be set to 0.
I guess that's why I bricked exactly after flashing Supersu from TWRP...
Click to expand...
Click to collapse
as far as i know.. having ro.secure enabled on recovery wont have any effect as we aren't changing anything withrespect to recovery.. but when we change something in system partition with a secure boot enabled kernel we get boot loops
Sent from my VIBE K6 Power using XDA Labs
ArjunrambZ said:
as far as i know.. having ro.secure enabled on recovery wont have any effect as we aren't changing anything withrespect to recovery.. but when we change something in system partition with a secure boot enabled kernel we get boot loops
Click to expand...
Click to collapse
Certainly I'm wrong, but I keep on not understanding. When you are in recovery mode you are loading the kernel inside the recovery and, of course, the default.prop inside the recovery.
That means that you flashed, or are going to flash, a boot.img with ro.secure=0 but running a recovery with ro.secure=1
From recovery you can manipulate system... but with a r0.secure=1 . I don't see a sense in this. But I'm a donkey.
I checked other official releases of twrp, and they all have ro.secure=0 in the default.prop
ilfastidio said:
Certainly I'm wrong, but I keep on not understanding. When you are in recovery mode you are loading the kernel inside the recovery and, of course, the default.prop inside the recovery.
That means that you flashed, or are going to flash, a boot.img with ro.secure=0 but running a recovery with ro.secure=1
From recovery you can manipulate system... but with a r0.secure=1 . I don't see a sense in this. But I'm a donkey.
I checked other official releases of twrp, and they all have ro.secure=0 in the default.prop
Click to expand...
Click to collapse
okay, firstly im also ain't any expert, but i get your point
i dont know why secure boot was enabled in recovery
but when i tried the procedure as explained in the thread i didnt get bootloop ( keeping secure boot in recovery) hence i came to the conclusion that it may not be valid.,, and i may be completely wrong here, if some one could clarify if would be better
Sent from my VIBE K6 Power using XDA Labs
Rooting panasonic eluga note 32GB ROM
Please provide rooting mothod for panasonic eluga note
amnv said:
Please provide rooting mothod for panasonic eluga note
Click to expand...
Click to collapse
sorry i dont have the device
Sent from my VIBE K6 Power using XDA Labs
ArjunrambZ said:
sorry i dont have the device
Sent from my VIBE K6 Power using XDA Labs
Click to expand...
Click to collapse
Its ok brother.. Thanks
My wifi is not working can someone help me? I did this process and after that it's not working
foRgaK said:
My wifi is not working can someone help me? I did this process and after that it's not working
Click to expand...
Click to collapse
i havent experienced this issue
but if u can attach a log file of turning on tbw wifi ,we can help
Sent from my VIBE K6 Power using XDA Labs
I am not responsible if your device gets bricked or gets any other damage.Proceed on your own caution.
This is only for Huawei GR5 mini & P9 lite.
This might not work on EMUI 5.0
If you want to install a custom recovery then follow these steps:
At first you need proper drivers on your device
# Download ADB drivers on your pc and unzip it to any drive:
https://mega.nz/#!pfplUJ5J
#You need to have TWRP recovery file.Link is below:
https://mega.nz/#!tLAUEDqI
#Supersu.zip file :
https://mega.nz/#!BKI3XYQL
You also need to unlock your bootloader to flash a custom recovery image.
-To unlock your bootloader first you need to get your Unlock Bootloader code.So go to:
https://emui.huawei.com/en/plugin.php?id=unlock&mod=unlock&action=apply
-Login with your Huawei ID.If you don't have one then create it.
-Click on Download tab at the top of the screen.You will be redirected to a new window.Select Unlock Bootloader tab below the search tab.
-Agree to the agreement.Provide all the information and copy the bootloader code to a file on your pc.
Unlocking Bootloader
Be aware that after you boot unlock your device it will do a factory reset.So do a backup using HiSuite.You should Know how to do that :good:
-First allow USB debugging mode in developer options.Also allow the device to be OEM unlocked in developer options.
-Go to the adb folder that you downloaded from above link and unzipped .Press shift and right click your mouse.You should see Open command window here option.Select it.Connect your device to the pc
-Type
Code:
adb devices
This should show your device Id.If your device is not detected try installing proper drivers.
-If your device is detected then type
Code:
adb reboot bootloader
This will boot your device to a window with white background and android like logo.
-Type
Code:
fastboot oem unlock 2222222222222222
Here replace 2222222222222222 with your boot unlock code.
-The device will prompt you to abort the process unless you don't want to.Select Unlock bootloader Anyway
Now your device will factory reset itself and you will have your bootloader Unlocked.Now you can flash TWRP recovery
Flash TWRP recovery
-Download and Extract TWRP from the link provided above
-Put TWRP.img file in the adb folder.Connect your device to pc.
-Type
Code:
adb reboot bootloader
This will boot your device in fastboot.
In fastboot,if your device is unlocked it will show phone unlocked FRP unlocked in red letters.
-Now type
Code:
fastboot flash recovery TWRP.img
-
Code:
fastboot reboot-bootloader
Now remove the usb connector from pc and press the power button till your device turns off.Just as it turns off Hold the power button + Vol. Up button at the same time till your device loads bootloader.This will boot your device into TWRP recovery.
Congratulations!!:laugh:
Change your language
Now if the language is in chinese or any other language follow these steps:
-Go to Settings marked by red in the main menu:
{
"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"
}
-Go to Language tab also marked by red:
-Select English
If you want to revert to stock recovery then you can just flash STOCK.img file
Root your device
To root your device you need supersu.zip file
Download it from link provided above.
-Copy the SuperSu.zip file to your sdcard.
-Boot into TWRP. (Power + Vol. Up)
-Select Install.
-Find supersu.zip file and select it.
-Swipe to confirm.
You are now rooted.
If you want to install custom roms,visit these pages:
https://forum.xda-developers.com/huawei-p9lite/development/unofficial-huawei-p9-lite-t3540493/page12#post71806235
https://forum.xda-developers.com/huawei-p9lite/development/6-0-1-aospa-paranoid-android-huawei-p9-t3544790
http://www.meticulus.co.vu/p/downloads_2.html
You know some root method for the GT3 or is the same as the GR5 mini method
Enviado desde mi HUAWEI NMO-L23 usando XDA Forums Pro.
rmoso said:
You know some root method for the GT3 or is the same as the GR5 mini method
Enviado desde mi HUAWEI NMO-L23 usando XDA Forums Pro.
Click to expand...
Click to collapse
Might be same.You can try at your own risk
ashishkafle said:
Might be same.You can try at your own risk
Click to expand...
Click to collapse
key MEGA ? are you kidding me ?
Huawei Gr5 mini, can not install supersu?
ashishkafle said:
I am not responsible if your device gets bricked or gets any other damage.Proceed on your own caution.
This is only for Huawei GR5 mini & P9 lite.
This might not work on EMUI 5.0
If you want to install a custom recovery then follow these steps:
At first you need proper drivers on your device
# Download ADB drivers on your pc and unzip it to any drive:
https://mega.nz/#!pfplUJ5J
#You need to have TWRP recovery file.Link is below:
https://mega.nz/#!tLAUEDqI
#Supersu.zip file :
https://mega.nz/#!BKI3XYQL
You also need to unlock your bootloader to flash a custom recovery image.
-To unlock your bootloader first you need to get your Unlock Bootloader code.So go to:
https://emui.huawei.com/en/plugin.php?id=unlock&mod=unlock&action=apply
-Login with your Huawei ID.If you don't have one then create it.
-Click on Download tab at the top of the screen.You will be redirected to a new window.Select Unlock Bootloader tab below the search tab.
-Agree to the agreement.Provide all the information and copy the bootloader code to a file on your pc.
Unlocking Bootloader
Be aware that after you boot unlock your device it will do a factory reset.So do a backup using HiSuite.You should Know how to do that :good:
-First allow USB debugging mode in developer options.Also allow the device to be OEM unlocked in developer options.
-Go to the adb folder that you downloaded from above link and unzipped .Press shift and right click your mouse.You should see Open command window here option.Select it.Connect your device to the pc
-Type
Code:
adb devices
This should show your device Id.If your device is not detected try installing proper drivers.
-If your device is detected then type
Code:
adb reboot bootloader
This will boot your device to a window with white background and android like logo.
-Type
Code:
fastboot oem unlock 2222222222222222
Here replace 2222222222222222 with your boot unlock code.
-The device will prompt you to abort the process unless you don't want to.Select Unlock bootloader Anyway
Now your device will factory reset itself and you will have your bootloader Unlocked.Now you can flash TWRP recovery
Flash TWRP recovery
-Download and Extract TWRP from the link provided above
-Put TWRP.img file in the adb folder.Connect your device to pc.
-Type
Code:
adb reboot bootloader
This will boot your device in fastboot.
In fastboot,if your device is unlocked it will show phone unlocked FRP unlocked in red letters.
-Now type
Code:
fastboot flash recovery TWRP.img
-
Code:
fastboot reboot-bootloader
Now remove the usb connector from pc and press the power button till your device turns off.Just as it turns off Hold the power button + Vol. Up button at the same time till your device loads bootloader.This will boot your device into TWRP recovery.
Congratulations!!:laugh:
Change your language
Now if the language is in chinese or any other language follow these steps:
-Go to Settings marked by red in the main menu:
-Go to Language tab also marked by red:
-Select English
If you want to revert to stock recovery then you can just flash STOCK.img file
Root your device
To root your device you need supersu.zip file
Download it from link provided above.
-Copy the SuperSu.zip file to your sdcard.
-Boot into TWRP. (Power + Vol. Up)
-Select Install.
-Find supersu.zip file and select it.
-Swipe to confirm.
You are now rooted.
If you want to install custom roms,visit these pages:
https://forum.xda-developers.com/huawei-p9lite/development/unofficial-huawei-p9-lite-t3540493/page12#post71806235
https://forum.xda-developers.com/huawei-p9lite/development/6-0-1-aospa-paranoid-android-huawei-p9-t3544790
http://www.meticulus.co.vu/p/downloads_2.html
Click to expand...
Click to collapse
I have unlock bootloader, completed install twpr, so after instal Supersu, reboot my phone, so Supersu icon dont appear on my screen.
Can you help me?
Whats is the download link decryption key please
steve gats said:
Whats is the download link decryption key please
Click to expand...
Click to collapse
For adb : https://mega.nz/#!pfplUJ5J!DxhLg8Qng3pAn8hdIRW-Afkpe46kC9z5F3daDJO6CDM
For stock recovery image : https://mega.nz/#!5OQF0CjK!-hVldwybHDasBXSx5JdDpXtR1X7weQbo3z0PNW5XtLc
Supersu : https://mega.nz/#!BKI3XYQL!sagih6787ZyJouGQCH0XiCkLopfskkZD88o1YM0OcfM
TWRP : https://mega.nz/#!tLAUEDqI!c6n1GF3aaf0HYshVg_YtUWrk-60z8LcIuX0Vwe-Ajeg
Hoang Hieu said:
I have unlock bootloader, completed install twpr, so after instal Supersu, reboot my phone, so Supersu icon dont appear on my screen.
Can you help me?
Click to expand...
Click to collapse
SuperSu isn't listed in menu list or what? You won't see a superSu logo when the device boots.
ashishkafle said:
For adb : https://mega.nz/#!pfplUJ5J!DxhLg8Qng3pAn8hdIRW-Afkpe46kC9z5F3daDJO6CDM
For stock recovery image : https://mega.nz/#!5OQF0CjK!-hVldwybHDasBXSx5JdDpXtR1X7weQbo3z0PNW5XtLc
Supersu : https://mega.nz/#!BKI3XYQL!sagih6787ZyJouGQCH0XiCkLopfskkZD88o1YM0OcfM
TWRP : https://mega.nz/#!tLAUEDqI!c6n1GF3aaf0HYshVg_YtUWrk-60z8LcIuX0Vwe-Ajeg
Click to expand...
Click to collapse
Can you upload them again please.
Thank you
[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
{
"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'
{
"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"
}
ArrowOS for OnePlus 9R (lemonades)ABOUTArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?Almost everything.
Bugs: You tell me.
DOWNLOADSClick here to Download
Tip: Select OEM -> Device, choose Arrow version, choose the build type: "GAPPS" or "VANILLA" to download.
INSTALLACTION- Please note: Be sure that your phone is already OOS12 based !!!
- Download Recovery here
- Download script here
- Download ROM zip file.
- Reboot phone to Fastboot mode
Code: fastboot boot recovery.img
Install in ADB -> copy-partitions-20220613-signed.zip -> Advanced -> reboot to bootloader
fastboot boot recovery.img -> Factery Reset -> Install in ADB -> ROM.zip
- Reboot
INSTRUCTIONSRead our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/ArrowOS-Devices/android_kernel_oneplus_sm8250
The download link seems broken. Also what firmware is ROM based on OOS 11 or 12 ?
With the kebab version should also work
ArrowOS - Downloads
Thanks for your work. Also I want to ask, should I use oos11 or oos12 firmware?
exthomeboy said:
With the kebab version should also work
ArrowOS - Downloads
Click to expand...
Click to collapse
I tried it, but it doesn't work.
slatera18 said:
The download link seems broken. Also what firmware is ROM based on OOS 11 or 12 ?
View attachment 5670887
Click to expand...
Click to collapse
Now it's possible, OOS 11
hiper25 said:
Now it's possible, OOS 11
Click to expand...
Click to collapse
Is also a version only for the 9R. Almost every other rom is flashable on the 8T and 9R, but not here
exthomeboy said:
Is also a version only for the 9R. Almost every other rom is flashable on the 8T and 9R, but not here
Click to expand...
Click to collapse
On my test 9R can't flash 8T ROM
They have to have to separate
hiper25 said:
Now it's possible, OOS 11
Click to expand...
Click to collapse
Yes able to download.
But there is an issue with mic volume when talking on calls. The other person hears feeble voice of me on call.
hiper25 said:
fastboot boot recovery.img
Click to expand...
Click to collapse
Isn't it the code supposed to be fastboot flash recovery <recovery_filename>.img
hiper25 said:
Reboot phone to Fastboot mode
Code: fastboot boot recovery.img
Install in ADB -> copy-partitions-20220613-signed.zip -> Advanced -> reboot to bootloader
fastboot boot recovery.img -> Factery Reset -> Install in ADB -> ROM.zip
- Reboot
Click to expand...
Click to collapse
I'm a newbie here, the last time I have installed a custom ROM on Asus phone over five years ago with lineage os.
Will I be successful if I follow below instructions, as your instructions above are short and suited for pros.
search
Install LineageOS on kebabkeyboard_arrow_left Back to the overview
warning
WARNING: These instructions only work if you follow every section and step precisely.
Do not continue after something fails!
Basic requirements
Read through the instructions at least once before actually following them, so as to avoid any problems due to any missed steps!
Make sure your computer has adb and fastboot. Setup instructions can be found here.
Enable USB debugging on your device.
Make sure that your model is actually listed in the “Supported models” section here (exact match required!)
warning
WARNING: Before following these instructions please ensure that the device is currently using Android 12 firmware.
If the vendor provided multiple updates for that version, e.g. security updates, make sure you are on the latest!
If your current installation is newer or older than Android 12, please upgrade or downgrade to the required version before proceeding (guides can be found on the internet!).
Unlocking the bootloaderinfo_outline
NOTE: The steps below only need to be run once per device.
warning
WARNING: Unlocking the bootloader will erase all data on your device! Before proceeding, ensure the data you would like to retain is backed up to your PC and/or your Google account, or equivalent. Please note that OEM backup solutions like Samsung and Motorola backup may not be accessible from LineageOS once installed.
Enable OEM unlock in the Developer options under device Settings, if present.
Connect the device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Up + Volume Down + Power.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable and port!
Now type the following command to unlock the bootloader:
fastboot oem unlock
info_outline
NOTE: At this point the device may display on-screen prompts which will require interaction to continue the process of unlocking the bootloader. Please take whatever actions the device asks you to to proceed.
If the device doesn’t automatically reboot, reboot it. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging to continue.
Flashing the dtbo partitionwarning
WARNING: This platform requires the dtbo partition to be flashed for recovery to work properly, the process to do so is described below.
Download dtbo file from here. Download the file named dtbo.img from the directory named with the latest date.
Power off the device, and boot it into bootloader mode:
With the device powered off, hold Volume Up + Volume Down + Power.
Flash the downloaded image file to your device by typing (replace <dtbo> with the actual filename!):
fastboot flash dtbo <dtbo>.img
Installing a custom recovery using fastboot
Download Lineage Recovery. Simply download the latest recovery file, named something like lineage-19.1-20220825-recovery-kebab.img.
Connect your device to your PC via USB.
On the computer, open a command prompt (on Windows) or terminal (on Linux or macOS) window, and type:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
With the device powered off, hold Volume Up + Volume Down + Power.
Once the device is in fastboot mode, verify your PC finds it by typing:
fastboot devices
If you don’t get any output or an error:
on Windows: make sure the device appears in the device manager without a triangle. Try other drivers until the command above works!
on Linux or macOS: If you see no permissions fastboot try running fastboot as root. When the output is empty, check your USB cable and port!
check
TIP: Some devices have buggy USB support while in bootloader mode, if you see fastboot hanging with no output when using commands such as fastboot getvar ..., fastboot boot ..., fastboot flash ... you may want to try a different USB port (preferably a USB Type-A 2.0 one) or a USB hub.
Flash recovery onto your device (replace <recovery_filename> with the actual filename!):
fastboot flash recovery <recovery_filename>.img
Now reboot into recovery to verify the installation.
Use the menu to navigate to and to select the Recovery option.
Ensuring all firmware partitions are consistentinfo_outline
NOTE: The steps below only need to be run once per device.
In some cases, the inactive slot can be unpopulated or contain much older firmware than the active slot, leading to various issues including a potential hard-brick. We can ensure none of that will happen by copying the contents of the active slot to the inactive slot.
To do this, sideload the copy-partitions-20220613-signed.zip package by doing the following:
Download the copy-partitions-20220613-signed.zip file from here. It should have a MD5 sum of 79f2f860830f023b7030c29bfbea7737 or a SHA-256 sum of 92f03b54dc029e9ca2d68858c14b649974838d73fdb006f9a07a503f2eddd2cd.
Sideload the copy-partitions-20220613-signed.zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload copy-partitions-20220613-signed.zip
info_outline
NOTE: The copy-partitions script was created by LineageOS developer erfanoabdi and filipepferraz
Now reboot to recovery by tapping “Advanced”, then “Reboot to recovery”.
Installing LineageOS from recovery
Download the LineageOS installation package that you would like to install or build the package yourself.
(Optionally): If you want to install an application package add-on such as Google Apps (use the arm64 architecture), please read and follow the instructions on Google Apps page
If you are not in recovery, reboot into recovery:
With the device powered off, hold Volume Down + Power.
Now tap Factory Reset, then Format data / factory reset and continue with the formatting process. This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
Return to the main menu.
Sideload the LineageOS .zip package:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
On the host machine, sideload the package using: adb sideload filename.zip.
check
TIP: Normally, adb will report Total xfer: 1.00x, but in some cases, even if the process succeeds the output will stop at 47% and report adb: failed to read command: Success. In some cases it will report adb: failed to read command: No error or adb: failed to read command: Undefined error: 0 which is also fine.
(Optionally): If you want to install any add-ons, click Advanced, then Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip those packages in sequence.
info_outline
NOTE: Add-ons aren’t signed with LineageOS’s official key, and therefore when they are sideloaded, Lineage Recovery will present a screen that says Signature verification failed, this is expected, please click Continue.
info_outline
NOTE: If you want the Google Apps add-on on your device, you must follow this step before booting into LineageOS for the first time!
Once you have installed everything successfully, click the back arrow in the top left of the screen, then “Reboot system now”.
hiper25 said:
INSTALLACTION- Please note: Be sure that your phone is already OOS12 based !!!
- Download Recovery here
- Download script here
- Download ROM zip file.
- Reboot phone to Fastboot mode
Code: fastboot boot recovery.img
Install in ADB -> copy-partitions-20220613-signed.zip -> Advanced -> reboot to bootloader
fastboot boot recovery.img -> Factery Reset -> Install in ADB -> ROM.zip
- Reboot
Click to expand...
Click to collapse
Newbie here.
Need instructions from unlocking the bootloader.
It took almost four hours to figure out and use MSM tool
Please do give me instructions from unlocking the bootloader