Related
Dear friends,
I would like root my g4. Marshmallow android 6 like I made with android 5.0, that in a soft root way. Is it possible?
Thanks a lot.
Kf
P.s I attached on this post the software configuration of my lg. Help me please!!!
I don't know if it is possible like in lollipop, but there is something called Magisk which is systemless root.
kenfalco_14 said:
Dear friends,
I would like root my g4. Marshmallow android 6 like I made with android 5.0, that in a soft root way. Is it possible?
Thanks a lot.
Kf
P.s I attached on this post the software configuration of my lg. Help me please!!!
Click to expand...
Click to collapse
kouzelnik3 said:
I don't know if it is possible like in lollipop, but there is something called Magisk which is systemless root.
Click to expand...
Click to collapse
Is your device unlocked?
No Root for MM for locked devices.
.
Sent from my LG-H815 using XDA Labs
How can i see if it is locked?
kenfalco_14 said:
How can i see if it is locked?
Click to expand...
Click to collapse
If you do not know it then it is likely that your device is not unlocked
You can reboot into fastboot by the command
adb reboot bootloader
and then you could execute
fastboot getvar unlock
And just before you ask not every model can be unlocked that being said only the h815 international and the h811 can be unlocked officially
Sent from my LG-H815 using XDA Labs
steadfasterX said:
If you do not know it then it is likely that your device is not unlocked
You can reboot into fastboot by the command
adb reboot bootloader
and then you could execute
fastboot getvar unlock
And just before you ask not every model can be unlocked that being said only the h815 international and the h811 can be unlocked officially
Click to expand...
Click to collapse
Do I need unlock the bootloader from lg site?
kenfalco_14 said:
Do I need unlock the bootloader from lg site?
Click to expand...
Click to collapse
Yes
Sent from my LG-H815 using XDA Labs
I tried to obtain the hardware id by adt, but I could'nt do the pc does'nt see the device. It is strange because it can see the sd cards like g4 attached device. I activated the debugging usb mode on the developer menu but I did'nt obtain the rsa device id so I think that phone can't work in usb debugging mode.
It is very stupid situation... :crying:
First, you need to check "Enable OEM unlock" in the developer menu. Then, you need to reboot into download mode from which you can get the fastboot command and then it should show you your device ID.
Here you are the tutorial which I used and it worked for me: https://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
I can't reboot in dowload mode. I push pwr+ vol - and nothing. I connected phone to my notebook and when I launch the adb command it tells me error "null" device. It is stranfe because I can see sd cards like g4...
kouzelnik3 said:
First, you need to check "Enable OEM unlock" in the developer menu. Then, you need to reboot into download mode from which you can get the fastboot command and then it should show you your device ID.
Here you are the tutorial which I used and it worked for me: https://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Click to expand...
Click to collapse
kenfalco_14 said:
I can't reboot in dowload mode. I push pwr+ vol - and nothing. I connected phone to my notebook and when I launch the adb command it tells me error "null" device. It is stranfe because I can see sd cards like g4...
Click to expand...
Click to collapse
I'm sorry but he meant the fastboot mode and not the download mode! Just follow the link provided it contains a step-by-step guide for you!
.
Sent from my LG-H815 using XDA Labs
I changed pc, finally obtained the rsa key from usb debugging, after make adb reboot bootloader and see this. Then make fastboot oem device - id and nothing,. System is waiting for device...forever. Sorry for pic.
kenfalco_14 said:
I changed pc, finally obtained the rsa key from usb debugging, after make adb reboot bootloader and see this. Then make fastboot oem device - id and nothing,. System is waiting for device...forever. Sorry for pic.
Click to expand...
Click to collapse
This is the correct mode but please show a screenshot of your terminal output and the command you have typed on your PC!
I assume that it is Windows what you are using so you may consider to try FWUL instead it has all drivers included and you have everything required already installed and you can run it without touching your main operating system..
.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
This is the correct mode but please show a screenshot of your terminal output and the command you have typed on your PC!
I assume that it is Windows what you are using so you may consider to try FWUL instead it has all drivers included and you have everything required already installed and you can run it without touching your main operating system..
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I put last lg driver vwersion., i use win7 sp 1. Pc recognize cell without problem, I have rsa debugging key, that inn other pc no had. May be that because this phone is a refurbished one? I don't know other causes.
Ciao
kenfalco_14 said:
I put last lg driver vwersion., i use win7 sp 1. Pc recognize cell without problem, I have rsa debugging key, that inn other pc no had. May be that because this phone is a refurbished one? I don't know other causes.
Ciao
Click to expand...
Click to collapse
it sounds like a driver issue.. check ur device manager if u see unknown devices.
.... or FWUL ? http://tinyurl.com/adbiso
.
steadfasterX said:
it sounds like a driver issue.. check ur device manager if u see unknown devices.
.... or FWUL ? http://tinyurl.com/adbiso
.
Click to expand...
Click to collapse
No issues in the device manager. I have a dual boot with winzoz and ubuntu. Coul I implement this tool on linux? I tried it with Virtual box but I don't know how use, archlinux is for me too advanced ...
steadfasterX said:
it sounds like a driver issue.. check ur device manager if u see unknown devices.
.... or FWUL ? http://tinyurl.com/adbiso
.
Click to expand...
Click to collapse
No issues in the device manager. I have a dual boot with winzoz and ubuntu. Could I implement this tool on linux? I tried it with Virtual box but I don't know how use it, archlinux is for me too advanced ...
kenfalco_14 said:
No issues in the device manager. I have a dual boot with winzoz and ubuntu. Could I implement this tool on linux? I tried it with Virtual box but I don't know how use it, archlinux is for me too advanced ...
Click to expand...
Click to collapse
just use ubuntu and there do
Code:
sudo fastboot devices
if that suceeds
Code:
sudo fastboot oem device-id
.
Fasboot command not found. Do I need download some tool from ubuntu dc? I think yes..
kenfalco_14 said:
Fasboot command not found. Do I need download some tool from ubuntu dc? I think yes..
Click to expand...
Click to collapse
depends on your ubuntu version. newer ones should work like this;
Code:
sudo apt update
sudo apt install android-tools-adb android-tools-fastboot
(https://www.linuxbabe.com/ubuntu/how-to-install-adb-fastboot-ubuntu-16-04-16-10-14-04)
otherwise: https://duckduckgo.com/?q=adb+fastboot+ubuntu&atb=v56-2__&ia=web
.
https://developer.sony.com/file/download/xperia-xz1-compact-driver/
How do I install it on Windows 7? I tried inf file from explorer and from device manager
Code:
amd64/
i386/
sa0117adb.inf
sa0117adb86.cat
sa0117adba64.cat
mt12345 said:
How do I install it on Windows 7? I tried inf file from explorer and from device manager
Code:
amd64/
i386/
sa0117adb.inf
sa0117adb86.cat
sa0117adba64.cat
Click to expand...
Click to collapse
If you are having problems with driver then just download 15sec adb universal driver and enjoy.[emoji5]
Sent from my [device_name] using XDA-Developers Legacy app
PrashannaGP said:
If you are having problems with driver then just download 15sec adb universal driver and enjoy.[emoji5]
Click to expand...
Click to collapse
15sec adb is installed. I need this one for fastboot
mt12345 said:
15sec adb is installed. I need this one for fastboot
Click to expand...
Click to collapse
Okay,
now you have to download ADB tool and you are good to go. Download ADB tool from GITHUB search page.[emoji5]
Sent from my P5 mini using premium XDA app
PrashannaGP said:
Okay,
now you have to download ADB tool and you are good to go. Download ADB tool from GITHUB search page.[emoji5]
Sent from my P5 mini using premium XDA app
Click to expand...
Click to collapse
adb and fastboot installed, it works with my old Nexus 5 but Xperia is not detected because (apparently?) I need to install driver above.
My question is: What is the procedure to install the driver?
mt12345 said:
adb and fastboot installed, it works with my old Nexus 5 but Xperia is not detected because (apparently?) I need to install driver above.
My question is: What is the procedure to install the driver?
Click to expand...
Click to collapse
Try this - https://www.mediafire.com/file/0dqvjix75j0dmle/Flashtool-drivers.zip/file
mt12345 said:
adb and fastboot installed, it works with my old Nexus 5 but Xperia is not detected because (apparently?) I need to install driver above.
My question is: What is the procedure to install the driver?
Click to expand...
Click to collapse
One thing i want to tell you is that,
You can install other device driver for that device too.
Just go to device manager and right click the unknown usb device and install driver from the list and choose android phone. or just download this driver and choose this using same process :- https://adbdriver.com/upload/samsung_android_usb_driver.exe
Dont worry this will work for every device.:good::good:
SXUsr said:
Try this - https://www.mediafire.com/file/0dqvjix75j0dmle/Flashtool-drivers.zip/file
Click to expand...
Click to collapse
Partial success. When I connected phone in fastboot mode, it was detected, driver installed and fastboot works. ADB doesn't.
mt12345 said:
Partial success. When I connected phone in fastboot mode, it was detected, driver installed and fastboot works. ADB doesn't.
Click to expand...
Click to collapse
Connect the phone in flash mode and uninstall the driver in device manager and start over.
mt12345 said:
Partial success. When I connected phone in fastboot mode, it was detected, driver installed and fastboot works. ADB doesn't.
Click to expand...
Click to collapse
Try this if ADB doesn't detected again
[adb kill-server]
And again try
[adb devices]
Sent from my P5 mini using XDA-Developers Legacy app
Best way to install up-to-date drivers:
Gett flashtool from the Sony website and extract the .exe with 7-Zip:
https://developer.sony.com/develop/open-devices/get-started/flash-tool
There is an executable file "Sony_Mobile_Software_Update_Drivers_x64_Setup.exe", install it
If you are trying to install the drivers in Windows 10, you need to go into safe mode and start the machine with 'driver signing disabled'
Then install the drivers.
You have to connect your phone in flashmode, go to the device manager, find the phone and manually add the right driver. Windows automatically assignes the wrong driver.
Edit: Sony driver is found here
Hi!
I am developing apps in Python/Kivy and testing them on my Moto G5. 6 months ago it worked fine. Now when I try to install Python/Kivy apps that worked 6 months ago or apps that others can install on THEIR devices, my Moto G5 with Android 8.1.0 says "app not installed". I have looked at many settings in the phone without finding a solution. Could installing a custom ROM, like ArrowOS, lineageOS or Pixel Experience be the solution to the problem?
I look forward to any input. Thank you!
Hero002 said:
Hi!
I am developing apps in Python/Kivy and testing them on my Moto G5. 6 months ago it worked fine. Now when I try to install Python/Kivy apps that worked 6 months ago or apps that others can install on THEIR devices, my Moto G5 with Android 8.1.0 says "app not installed". I have looked at many settings in the phone without finding a solution. Could installing a custom ROM, like ArrowOS, lineageOS or Pixel Experience be the solution to the problem?
I look forward to any input. Thank you!
Click to expand...
Click to collapse
You will get app not installed message for the following reason
There's not enough space on the device to install it
There's an app with the same package name already installed and the app you're trying to install with the same package name is signed with a different key
The apk is not signed
The apk is signed but with a platform key so it can only be installed to system and not to a user
The app only has 64bit libs and you are trying to install on a 32bit system
If it's an android version issue eg you need a higher version of android to install on you will get unable to parse the package so assuming your app is designed to install on 32bit Roms it will install on stock rom
If it's only designed for 64bit roms you will need a custom rom for this device
TheFixItMan said:
You will get app not installed message for the following reason
There's not enough space on the device to install it
There's an app with the same package name already installed and the app you're trying to install with the same package name is signed with a different key
The apk is not signed
The apk is signed but with a platform key so it can only be installed to system and not to a user
The app only has 64bit libs and you are trying to install on a 32bit system
If it's an android version issue eg you need a higher version of android to install on you will get unable to parse the package so assuming you app is designed to install on 32bit Roms it will install on stock rom
If it's only designed for 64bit roms you will need a custom rom for this device
Click to expand...
Click to collapse
Are we misunderstanding each other?
I am talking about test APKs that are not signed. Transferred via USB. And which could be installed 6 months ago. I HAVE uninstalled it before trying to reinstall it.
Hero002 said:
Are we misunderstanding each other?
I am talking about test APKs that are not signed. Transferred via USB. And which could be installed 6 months ago. I HAVE uninstalled it before trying to reinstall it.
Click to expand...
Click to collapse
He just listed all possible reasons for that message. You btw get an more informative error message if you use adb install, so use it and post the error here.
Hero002 said:
Are we misunderstanding each other?
I am talking about test APKs that are not signed. Transferred via USB. And which could be installed 6 months ago. I HAVE uninstalled it before trying to reinstall it.
Click to expand...
Click to collapse
Apks must be signed - if they are not signed even with just a test key they will not install
The only exception to this is if you are rooted and have changed your rom to disable signature checking
Just quickly sign the apk with a test key using this app
https://play.google.com/store/apps/details?id=com.haibison.apksigner
nift4 said:
He just listed all possible reasons for that message. You btw get an more informative error message if you use adb install, so use it and post the error here.
Click to expand...
Click to collapse
Thank you for your reply!
Someone in the Kivy forum also asked me to do that, but there isn't really any error message - see output from Ubuntu Terminal below.
The Moto G5 is connected to the PC with USB. USB file transfer is enabled, and USB debugging.
Now I have done it again with 4 APK-files:
1. A 'release' version of my app, which worked without problems 6 months ago.
2. A new 'debug' version of same app.
3. A 'Hello world' Kivy test APK file that worked for the Kivy guy who compiled it.
4. My compilation of the same Kivy test app.
As you can see, none of them work on my Moto G5 with Android 8.1.0 (the February 2019 update). I pressed <enter> twice then Ctrl-C each time:
[email protected]:~$ /home/henrik/.buildozer/android/platform/android-sdk/platform-tools/adb install -r "/mnt/4AF15A0435E762B4/DataDoc/OneDrive/PycharmProjects/2d-graphics/touchtracer/bin/GeoESPtrainingTEST__arm64-v8a-0.1-arm64-v8a-release.apk"
* daemon not running; starting now at tcp:5037
* daemon started successfully
Performing Streamed Install
^C
[email protected]:~$ /home/henrik/.buildozer/android/platform/android-sdk/platform-tools/adb install -r "/mnt/4AF15A0435E762B4/DataDoc/OneDrive/PycharmProjects/2d-graphics/touchtracer/bin/GeoESPtrainingTEST__arm64-v8a-0.1-arm64-v8a-debug.apk"
Performing Streamed Install
^C
[email protected]:~$ /home/henrik/.buildozer/android/platform/android-sdk/platform-tools/adb install -r "/mnt/4AF15A0435E762B4/DataDoc/OneDrive/PycharmProjects/PyCharm-Python-Kivy-Buildozer-problemer/Android-not-installing-anything/hello/bin/HWtest-0.1-arm64-v8a-debug.apk"
Performing Streamed Install
^C
[email protected]:~$ /home/henrik/.buildozer/android/platform/android-sdk/platform-tools/adb install -r "/mnt/4AF15A0435E762B4/DataDoc/OneDrive/PycharmProjects/PyCharm-Python-Kivy-Buildozer-problemer/Android-not-installing-anything/hello/bin/HWtest__arm64-v8a-0.2-arm64-v8a-debug.apk"
Performing Streamed Install
^C
[email protected]:~$
TheFixItMan said:
Apks must be signed - if they are not signed even with just a test key they will not install
The only exception to this is if you are rooted and have changed your rom to disable signature checking
Just quickly sign the apk with a test key using this app
https://play.google.com/store/apps/details?id=com.haibison.apksigner
Click to expand...
Click to collapse
Thank you for your reply.
I installed that 'apk-signer' app on my Moto G5, but when I try to sign the 'HWtest__arm64-v8a-0.2-arm64-v8a-debug.apk' file (selecting that file through 'File Manager +', I get the message 'apk-signer has stopped'. When I try one of the other APK-files, I get the message 'apk-signer keeps stopping' (my translation from Danish).
If I try selecting the file through the build in 'FIles' app, I can't seem to select an APK-file. When I try, 'Files' thinks I want to edit the file name...?!
Hero002 said:
Thank you for your reply!
Someone in the Kivy forum also asked me to do that, but there isn't really any error message - see output from Ubuntu Terminal below.
The Moto G5 is connected to the PC with USB. USB file transfer is enabled, and USB debugging.
Now I have done it again with 4 APK-files:
1. A 'release' version of my app, which worked without problems 6 months ago.
2. A new 'debug' version of same app.
3. A 'Hello world' Kivy test APK file that worked for the Kivy guy who compiled it.
4. My compilation of the same Kivy test app.
As you can see, none of them work on my Moto G5 with Android 8.1.0 (the February 2019 update). I pressed <enter> twice then Ctrl-C each time:
[email protected]:~$ /home/henrik/.buildozer/android/platform/android-sdk/platform-tools/adb install -r "/mnt/4AF15A0435E762B4/DataDoc/OneDrive/PycharmProjects/2d-graphics/touchtracer/bin/GeoESPtrainingTEST__arm64-v8a-0.1-arm64-v8a-release.apk"
* daemon not running; starting now at tcp:5037
* daemon started successfully
Performing Streamed Install
^C
[email protected]:~$ /home/henrik/.buildozer/android/platform/android-sdk/platform-tools/adb install -r "/mnt/4AF15A0435E762B4/DataDoc/OneDrive/PycharmProjects/2d-graphics/touchtracer/bin/GeoESPtrainingTEST__arm64-v8a-0.1-arm64-v8a-debug.apk"
Performing Streamed Install
^C
[email protected]:~$ /home/henrik/.buildozer/android/platform/android-sdk/platform-tools/adb install -r "/mnt/4AF15A0435E762B4/DataDoc/OneDrive/PycharmProjects/PyCharm-Python-Kivy-Buildozer-problemer/Android-not-installing-anything/hello/bin/HWtest-0.1-arm64-v8a-debug.apk"
Performing Streamed Install
^C
[email protected]:~$ /home/henrik/.buildozer/android/platform/android-sdk/platform-tools/adb install -r "/mnt/4AF15A0435E762B4/DataDoc/OneDrive/PycharmProjects/PyCharm-Python-Kivy-Buildozer-problemer/Android-not-installing-anything/hello/bin/HWtest__arm64-v8a-0.2-arm64-v8a-debug.apk"
Performing Streamed Install
^C
[email protected]:~$
Click to expand...
Click to collapse
Oh, that's strange... Try
Code:
adb push /path/to/my/apk /sdcard/app.apk; adb shell pm install /sdcard/app.apk
nift4 said:
Oh, that's strange... Try
Code:
adb push /path/to/my/apk /sdcard/app.apk; adb shell pm install /sdcard/app.apk
Click to expand...
Click to collapse
Just to be sure: Is that 2 commands? And could it look like this in my case:
adb push /mnt/4AF15A0435E762B4/DataDoc/bin/HWtest-0.1-arm64-v8a-debug.apk /sdcard/HWtest-0.1-arm64-v8a-debug.apk
adb shell pm install /sdcard/HWtest-0.1-arm64-v8a-debug.apk
Hero002 said:
Just to be sure: Is that 2 commands? And could it look like this in my case:
adb push /mnt/4AF15A0435E762B4/DataDoc/bin/HWtest-0.1-arm64-v8a-debug.apk /sdcard/HWtest-0.1-arm64-v8a-debug.apk
adb shell pm install /sdcard/HWtest-0.1-arm64-v8a-debug.apk
Click to expand...
Click to collapse
To make things easier
Copy the apk to your computer to a folder with a short filename and no spaces in the path
Make sure you adb is in your environmental veriables so it can be run from any path
Open a terminal window in the location where your apk is
Type
Code:
adb install nameofapp.apk
Also upload the app here or you can send me a private a message with a link if you don't want it to be public and I'll see if I can install it - I don't have this device anymore but if it installs on mine I don't see why it wouldn't on a moto g5
Also I've noted on your app name it's arm64-v8
This device stock rom is 32bit so unless your app supports 32bit roms it will not install as mentioned in my first reply to you
In this case you will need to use a custom rom that support 64bit architecture or make the app support 32bit architecture armv7
TheFixItMan said:
To make things easier
Copy the apk to your computer to a folder with a short filename and no spaces in the path
Make sure you adb is in your environmental veriables so it can be run from any path
Open a terminal window in the location where your apk is
Type
Code:
adb install nameofapp.apk
Also upload the app here or you can send me a private a message with a link if you don't want it to be public and I'll see if I can install it - I don't have this device anymore but if it installs on mine I don't see why it wouldn't on a moto g5
Also I've noted on your app name it's arm64-v8
This device stock rom is 32bit so unless your app supports 32bit roms it will not install as mentioned in my first reply to you
In this case you will need to use a custom rom that support 64bit architecture or make the app support 32bit architecture armv7
Click to expand...
Click to collapse
Thank you for your reply!
Connecting Moto G5 to my Ubuntu laptop again, I get the same result again. After a while, I pressed <enter> twice, then Ctrl-C. Here is the Terminal output:
[email protected]:/mnt/4AF15A0435E762B4/DataDoc/bin$ adb install HWtest-0.1-arm64-v8a-debug.apk
Performing Streamed Install
^C
[email protected]:/mnt/4AF15A0435E762B4/DataDoc/bin$
This particular file is a 'Hello world'-test that I could upload here, but there doesn't seem to be a way of uploading files here?
Should I put it on an Internet URL instead?
ADDITION:
I have put the file here:
http://transformation.dk/deling/HWtest-0.1-arm64-v8a-debug.apk
Hero002 said:
Thank you for your reply!
Connecting Moto G5 to my Ubuntu laptop again, I get the same result again. After a while, I pressed <enter> twice, then Ctrl-C. Here is the Terminal output:
[email protected]:/mnt/4AF15A0435E762B4/DataDoc/bin$ adb install HWtest-0.1-arm64-v8a-debug.apk
Performing Streamed Install
^C
[email protected]:/mnt/4AF15A0435E762B4/DataDoc/bin$
This particular file is a 'Hello world'-test that I could upload here, but there doesn't seem to be a way of uploading files here?
Should I put it on an Internet URL instead?
ADDITION:
I have put the file here:
http://transformation.dk/deling/HWtest-0.1-arm64-v8a-debug.apk
Click to expand...
Click to collapse
Your app installs and runs fine
The reason it won't install on stock rom on this device is because your lib files are for a 64bit devices
Stock rom on this device is 32bit and you have not included any 32bit lib alternatives armv7
If you want to install the app on this device you have two choices
1 - build the app to also include support for 32bit devices
2 - Install a custom 64bit rom on the Moto G5
TheFixItMan said:
Your app installs and runs fine
The reason it won't install on stock rom on this device is because your lib files are for a 64bit devices
Stock rom on this device is 32bit and you have not included any 32bit lib alternatives armv7
If you want to install the app on this device you have two choices
1 - build the app to also include support for 32bit devices
2 - Install a custom 64bit rom on the Moto G5
Click to expand...
Click to collapse
Great. Thank you!
I found an APK I compiled in March:
GeoESPtrainingTEST__armeabi-v7a-0.1-armeabi-v7a-release.apk
And yes - something happens - in Terminal:
[email protected]:/mnt/4AF15A0435E762B4/DataDoc/bin$ adb install GeoESPtrainingTEST__armeabi-v7a-0.1-armeabi-v7a-release.apk
Performing Streamed Install
Success
[email protected]:/mnt/4AF15A0435E762B4/DataDoc/bin$
But nothing happens on the Moto G5...!
Then I copied that APK file to Moto G5, and in 'File Manager +' I tapped on it to install it, and the installer said: "Do you want to install an update to the existing app?" I said 'yes', it installed successfully, and it worked as expected.
That seems strange... at least to me!
Hero002 said:
Great. Thank you!
I found an APK I compiled in March:
GeoESPtrainingTEST__armeabi-v7a-0.1-armeabi-v7a-release.apk
And yes - something happens - in Terminal:
[email protected]:/mnt/4AF15A0435E762B4/DataDoc/bin$ adb install GeoESPtrainingTEST__armeabi-v7a-0.1-armeabi-v7a-release.apk
Performing Streamed Install
Success
[email protected]:/mnt/4AF15A0435E762B4/DataDoc/bin$
But nothing happens on the Moto G5...!
Then I copied that APK file to Moto G5, and in 'File Manager +' I tapped on it to install it, and the installer said: "Do you want to install an update to the existing app?" I said 'yes', it installed successfully, and it worked as expected.
That seems strange... at least to me!
Click to expand...
Click to collapse
You may have had part of the apk still installed - it may have copied the apk of the 64bit version to data but failed to complete the install due to the 64bit libs and left some parts
You can do
Code:
adb shell
cd /data/app (or where ever the apk is located)
rm com.packagenameofapp.apk
And this will remove the apk but since you got it working via updating directly on the phone there's not really any need
TheFixItMan said:
To make things easier
Copy the apk to your computer to a folder with a short filename and no spaces in the path
Make sure you adb is in your environmental veriables so it can be run from any path
Open a terminal window in the location where your apk is
Type
Also upload the app here or you can send me a private a message with a link if you don't want it to be public and I'll see if I can install it - I don't have this device anymore but if it installs on mine I don't see why it wouldn't on a moto g5
Also I've noted on your app name it's arm64-v8
This device stock rom is 32bit so unless your app supports 32bit roms it will not install as mentioned in my first reply to you
In this case you will need to use a custom rom that support 64bit architecture or make the app support 32bit architecture armv7
Click to expand...
Click to collapse
He tried adb install and it didn't work!
nift4 said:
He tried adb install and it didn't work!
Click to expand...
Click to collapse
I said that because his terminal commands were messy - was just to eliminate any issues with long commands
Plus issue is solved - his app only had 64bit libs so won't install on stock rom on this device which is 32bit
TheFixItMan said:
I said that because his terminal commands were messy - was just to eliminate any issues with long commands
Plus issue is solved - his app only had 64bit libs so won't install on stock rom on this device which is 32bit
Click to expand...
Click to collapse
Sorry, I just read your quote, not the whole thread
TheFixItMan said:
You may have had part of the apk still installed - it may have copied the apk of the 64bit version to data but failed to complete the install due to the 64bit libs and left some parts
You can do
Code:
adb shell
cd /data/app (or where ever the apk is located)
rm com.packagenameofapp.apk
And this will remove the apk but since you got it working via updating directly on the phone there's not really any need
Click to expand...
Click to collapse
Yes - it works!
I tried compiling a 32bit version of the Python/Kivy 'hello world' test app by putting this line:
android.arch = armeabi-v7a
in the 'buildozer.spec' file.
(EDIT: Instead of this line:
android.arch = arm64-v8a)
In Terminal, while in the test app project folder, I ran:
$ buildozer android debug
$ buildozer android debug deploy run
And the app opened on the Moto G5!
Thank you VERY much!!!
(EDIT:
Now I tried compiling my 'real' app to 32bit using 'android.arch = armeabi-v7a', and that worked too!)
Thank you!
Hero002 said:
Yes - it works!
I tried compiling a 32bit version of the Python/Kivy 'hello world' test app by putting this line:
android.arch = armeabi-v7a
in the 'buildozer.spec' file.
(EDIT: Instead of this line:
android.arch = arm64-v8a)
In Terminal, while in the test app project folder, I ran:
$ buildozer android debug
$ buildozer android debug deploy run
And the app opened on the Moto G5!
Thank you VERY much!!!
(EDIT:
Now I tried compiling my 'real' app to 32bit using 'android.arch = armeabi-v7a', and that worked too!)
Thank you!
Click to expand...
Click to collapse
Am I kind of demanding?
I mean - it would have been VERY nice if either ADB (Android Debug Bridge) or the Package Installation App on my Moto G5 phone had given some kind of error message like for instance:
"ERROR: 64bit code found. Only 32bit code allowed."
That would have saved me a huge amount of time!
Hero002 said:
Am I kind of demanding?
I mean - it would have been VERY nice if either ADB (Android Debug Bridge) or the Package Installation App on my Moto G5 phone had given some kind of error message like for instance:
"ERROR: 64bit code found. Only 32bit code allowed."
That would have saved me a huge amount of time!
Click to expand...
Click to collapse
Would be nice but unfortunately error messages are never really that clear unless you know what's wrong
My favourite being unexpected or unknown error found - very helpful
Okay I got a problem I just got mine finally today in the mail. my Windows 10 recognizes it in ADB but as soon as I go to fastboot no matter what I do it's like it doesn't see the drivers anymore. Anybody have an idea how to get around this so I can unlock the bootloader?
Edit:. Nevermind I finally found a driver package that worked. What a deal
Have you tried installing these drivers? https://developer.android.com/studio/run/win-usb
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
DinarQ8 said:
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I've also been struggling with getting windows 10 to recognise my Pixel. I've installed the drivers (the small usb drivers zip and right click install on the driver) but file explorer isn't showing the contents (or even the phone at all).
Would using the SDK help?
Flippy125 said:
Have you tried installing these drivers? https://developer.android.com/studio/run/win-usb
Click to expand...
Click to collapse
I finally figured it out. Found the right drivers. Took me forever
DinarQ8 said:
You need to download or update SDK Platform Tools https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
I did. Didn't help. My older pixels worked and my op8. Just not this thing. I found some driver pack and it finally worked
mac796 said:
I did. Didn't help. My older pixels worked and my op8. Just not this thing. I found some driver pack and it finally worked
Click to expand...
Click to collapse
Please could you share the driver pack that worked for you?
Then just let us know which driver you installed so that the Pixel 6 was recognized. And a download link wouldn't be bad either - that helps others with the same problem.
Try Download Minimal ADB and Fastboot Tool it should work
Download Minimal ADB and Fastboot Tool (all versions)
Download the latest version of Minimal ADB and Fastboot Tool which allow you to install and setup the ADB and Fastboot files on the computer.
androidmtk.com
After you install it ensure you update SDK Platform Tools the file name " ADB "
/c/adb
cd993 said:
Please could you share the driver pack that worked for you?
Click to expand...
Click to collapse
Yet Another Universal ADB Driver Package and adbupdater for Windows
I made this installer as a kind of "update" the old driver package I had made for Ainol and Actions before. While at it I added those two tools usually used, that is adb and fastboot. Based on batch scripts, so it's open source. Self Signed, not...
forum.xda-developers.com
Sorry took me a bit to find it again
mac796 said:
Sorry took me a bit to find it again
Click to expand...
Click to collapse
Thanks will give this a try later on!
On Windows 11 the official r13 Google USB Driver pack worked - but only after booting into an alternative mode that allows unsigned drivers. For some reason Google's drivers are not signed, and Win11, with TPM+SecureBoot refuses to load those drivers in normal mode.
cd993 said:
I've also been struggling with getting windows 10 to recognise my Pixel. I've installed the drivers (the small usb drivers zip and right click install on the driver) but file explorer isn't showing the contents (or even the phone at all).
Would using the SDK help?
Click to expand...
Click to collapse
It sounds like you're talking about accessing the phone's storage via MTP. When you plug the phone into the computer, you may need to choose the new notification regarding charging and switch it to the mode to be able to access the storage. Probably defaults to "Charging this device via USB", and you need to click on it and select something like "File transfer/ Android Auto". This won't require any new Windows drivers.
Please correct me if you're not talking about accessing the phone's storage.
mac796 said:
I finally figured it out. Found the right drivers. Took me forever
Click to expand...
Click to collapse
Would you mind saying WHICH drivers? Thanks...
wsalopek said:
Would you mind saying WHICH drivers? Thanks...
Click to expand...
Click to collapse
I posted it in this thread. Read it. There's a link
mac796 said:
I posted it in this thread. Read it. There's a link
Click to expand...
Click to collapse
OK...thanks...got it.
mac796 said:
I posted it in this thread. Read it. There's a link
Click to expand...
Click to collapse
wsalopek said:
OK...thanks...got it.
Click to expand...
Click to collapse
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
roirraW edor ehT said:
Personally, I would always use the official drivers Google provides unless they just don't work for whatever reason: Get the Google USB Driver (this is for Windows). They work for me. They are rarely updated, but they are every once in a great while, sometimes years in-between.
Click to expand...
Click to collapse
I agree with this. be careful using drivers or adb/fastboot tools. Some are fine, but there's no need for it really anymore. Google has made it very easy to install drivers and Platform-Tools (adb/fastboot tool).
Google provides the Fastboot/ADB tool (Platform-Tools) and Google USB Drivers (adb/fastboot interface). This will allow any Pixel to interface with Windows using the fastboot/adb protocol. Official Google USB Driver includes support for both the Fastboot and ADB driver interface. There are 3 main drivers (Fastboot, ADB and MTP/Portable File Transfer). The MTP/Portable File Transfer driver is built-in to Windows 7-11.
Fastboot/ADB Driver Interface - Official Download Link:
When flashing a full image or unlocking your bootloader, the fastboot interface is being used.
First Download official Google USB Drivers (it's a zip file). Extract the zip (important!). Right-click on the android_winusb.inf file and hit install. You can then restart your phone to the Bootloader Screen (hold vol-down while it restarts or turns on). When you plug in your phone, Windows Device Manager will show a new device at the top: Android Device: Android Bootloader Interface.
Using the ADB interface: It's the same driver. Enable USB Debugging on your phone, then plug it in to your computer. A prompt will appear on your phone (to allow USB Debugging). The driver in Device Manager will appear as Android Device: Android Composite ADB interface.
Now you can download and use Platform-Tools to flash an Android Image, OTA or run adb/fastboot commands.
Official Download Page
"Android SDK Platform-Tools is a component for the Android SDK. It includes tools that interface with the Android platform, such as adb, fastboot, and systrace"
It's best to make Platform-Tools available system-wide. Download Platform-Tools from the above link and extract it to your C:\ drive - that way you will have a folder to add to the PATH Environment under Window System Properties Menu, Advanced, Environment Variables, System Variables, PATH (google how to do this, very easy). What this does is allow adb/fastboot commands to be run from anywhere in the system, so you don't have to be in the platform-tools folder to run adb/fastboot commands and flash an Android Image (Official or Android Fork such as ProtonAOSP).
My problem ended up being that my USB Hub went bad... Was getting Yellow Exclamation in Device Manager and an error when going into Fastboot. Once I plugged directly into the PC, no issues. New hub ordered!
Google Pixel Watch Root Guide using Magisk
{
"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"
}
ReadmeNote that this rooting process was performed with a special USB-C cradle provided by the Google Team. I would not recommend flashing the device without a stable connection to the pins under the wrist strap. I might attempt to make a 3D printed enclosure that uses pogo pins. Additionally, this process will wipe the device.
Rooting Process
Enable developer options on the watch by going to Settings > System > About > Versions > Tap Build number until you unlock developer mode
While here, note down the Build Number. It will look like RWD9.XXXXXX.XXX.XX.
Go into Developer options and enable ADB debugging
Install the latest version of ADB and Fastboot tools on a computer
https://developer.android.com/tools/releases/platform-tools
Connect watch to computer using USB and allow permanent ADB debugging access on the watch
Verify your access works by running
Code:
adb devices
Download the appropriate (LTE or Bluetooth/WIFI) firmware at the link below, making sure to download the version that matches the build number from Step 2.
Factory Images for Google Pixel Watch Devices | Google Play services | Google for Developers
developers.google.com
Verify the checksum of downloaded firmware using
Code:
sha256sum name-of-firmware.zip
Unzip the downloaded zip, then unzip the image-rXX zip inside the original zip. Then, transfer the boot.img file to the watch using
Code:
adb push boot.img /sdcard/Download
Install a file manager on the watch because it does not include one by default. We will need it to select the boot.img file the Magisk app. I used File Manager TV USB OTG Cloud from the Play Store. I recommend launching the app and granting Files and media permissions all the time like it asks you to do in the popup.
Install the latest version of the Magisk APK from the Github link below on the watch by running
Code:
adb install name-of-magisk.apk
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Launch the Magisk app, click Install, choose Select and Patch a File, then browse to the downloaded boot.img file
Click Let's Go and the magisk-patched boot image will be created in the Download folder
Transfer the image back to your computer using
Code:
adb pull /sdcard/Download/name-of-patched-image
Run
Code:
adb reboot bootloader
to reboot the watch into Fastboot
Verify the device shows up by using
Code:
fastboot devices
Unlock the bootloader of the watch using
Code:
fastboot flashing unlock
Confirm the message on the watch to unlock and wipe the device
Flash and boot the newly created Magisk image using
Code:
adb flash boot name-of-patched-image.img
Select Start in Fastboot to start the watch
After waiting an extremely long time, the watch will hopefully start and will need to be setup again
Reinstall the Magisk app using
Code:
adb install name-of-magisk.apk
Launch the app and it might prompt that it needs to restart the watch
To prevent the broken Superuser request popup where the grant button is off the screen, I recommend changing the Automatic Response prompt setting in the Magisk app to Grant. To change the option, swipe up on the Prompt text
With the watch started and setup, start an adb shell by running
Code:
adb shell
Then, run su to escalate to root privilege. The shell should change symbols from $ to # and running
Code:
whoami
should result in root
Bypassing SafetyNet
Download the YASNAC - SafetyNet Checker APK from GitHub:
Releases · RikkaW/YASNAC
Yet Another SafetyNet Attestation Checker. Contribute to RikkaW/YASNAC development by creating an account on GitHub.
github.com
Install it on the watch using
Code:
adb install name-of-yasnac.apk
(Optional) Open the app and run the SafetyNet Attestation to verify your device fails
Download the SafetyNet Fix Magisk module from GitHub:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Transfer it to watch using
Code:
adb push safetynet-fix-v2.4.0.zip /sdcard/Download
Start an adb shell with the watch using
Code:
adb shell
Elevate to root privileges with
Code:
su
Install the module with
Code:
magisk --install-module /sdcard/Download/safetynet-fix-v2.4.0.zip
Once installed, restart your watch
Now, run YASNAC SafetyNet Attestation again, and you should pass!
Interfacing with the USB PinsThe USB pins are under the watch band closest to the secondary button. From left to right, the pins are voltage, data+, data-, and ground. Google's VRP program provides the watch cradles by invitation only (still waiting for mine ). As such, a DIY solution needs to be created to make this process more accessible.
Picture courtesy of @ShinyQuagsireThe most reliable solution I can think of currently is using PCBite SP10 probes to connect to the USB pins. Once I get my PCBite, I will post a setup picture.
Another solution I'm going to try is inserting pogo pins into a replacement silicone watch band to connect to the USB pins.
Similarly, the pins have a 1.27mm spacing which you can find headers for online. That in combination with some helping hands could give a somewhat janky connection.
Troubleshooting
If booting the Magisk image results in a bootloop, you can unbrick the device by flashing the corresponding stock boot.img image using
Code:
adb flash boot boot.image
If Magisk doesn't see the file, try doing the following to your file browser app:
Settings > Apps & Notifications > App permissions > Files and media > AppName > Allow all the time
Tips
You can get into FastBoot mode by tapping on the top left and bottom right of the screen at the same time as the device is booting when the white "G" logo appears.
Wireless debugging allows you to do almost all of this guide except booting the patched boot.img file in Magisk. To enable wireless debugging, go to Settings > Developer options > Check Debug over Wi-Fi. Then, in developer options still, go to Wireless debugging and turn it on. From here, you can connect to your watch remotely from your PC using
Code:
adb connect watchip
ThanksHuge thanks to Asmita Jha (Twitter @aj_0x00) who was there during the first 2 days of the rooting attempts and helped troubleshoot throughout. Additionally, big thanks to Stack Smashing (Twitter @ghidraninja) for giving us the idea to patch the Magisk file on the watch itself, instead of patching the boot image on another device running Magisk. Additionally, thanks to the Google team who gave us access to device and the prototype cradles to interface with the watch reliably.
Future PlansTo make the process more accessible, a cheap interfacing solution needs to be created. Please reach out if have any questions, concerns, or information that would make the process easier. You can find me on Twitter @breaddisease
https://twitter.com/breaddisease
Thanks!
This is awesome!
Now we just need a way to source that craddle or design one.
Does Rooting it break the Google Pay functionality or SafetyNet (if it has one) ?
KineSight said:
Does Rooting it break the Google Pay functionality or SafetyNet (if it has one) ?
Click to expand...
Click to collapse
I'm unsure about this so far! Both of my phones don't work with the Google Pixel Watch app (degoogled OP7P and old S8+) so I can't setup my Google account with the watch to use Google Wallet. Additionally, I can't install a SafetyNet checker without the USB cradle I'll get back to you if I figure something out!
How did you get the file manager to show the .img file? I installed the same file manager, pushed the file via adb, but the file manager can't see any .img files. I tried renaming it to 'boot.jpg', pushed that, the file manager sees it, but then Magisk fails with unknown/unsupported image type.
ClarkIV said:
How did you get the file manager to show the .img file? I installed the same file manager, pushed the file via adb, but the file manager can't see any .img files. I tried renaming it to 'boot.jpg', pushed that, the file manager sees it, but then Magisk fails with unknown/unsupported image type.
Click to expand...
Click to collapse
You might need to allow the app Files and media permissions all the time, like this:
Settings > Apps & Notifications > App permissions > Files and media > AnExplorer > Allow all the time
KineSight said:
Does Rooting it break the Google Pay functionality or SafetyNet (if it has one) ?
Click to expand...
Click to collapse
I fail SafetyNet without the Universal SafetyNet Fix Magisk Module. However, I was able to install the SafetyNet Fix module with the following:
Code:
adb push safetynet-fix-v2.4.0.zip /sdcard/Download
adb shell
su
cd /sdcard/Download
magisk --install-module safetynet-fix-v2.4.0.zip
With this, I now pass SafetyNet! Still have to try Google Pay
breaddisease said:
Google Pixel Watch Root Guide using Magisk
ReadmeNote that this rooting process was performed with a special USB-C cradle provided by the Google Team. I would not recommend flashing the device without a stable connection to the pins under the wrist strap. I might attempt to make a 3D printed enclosure that uses pogo pins. Additionally, this process will wipe the device.
Rooting Process
Enable developer options on the watch by going to Settings > System > About > Versions > Tap Build number until you unlock developer mode
Go into Developer options and enable ADB debugging
Install the latest version of ADB and Fastboot tools on a computer
Connect watch to computer using USB and allow permanent ADB debugging access on the watch
Verify your access works by running
Code:
adb devices
Download the latest version of the appropriate (LTE or Bluetooth/WIFI) Google Pixel Watch OTA firmware at the link below. Note that the latest version is at the bottom of the list (thanks Google)
https://developers.google.com/android/ota-watch
Verify the checksum of downloaded firmware using
Code:
sha256sum name-of-firmware.zip
Unzip the downloaded zip, then transfer the boot.img file to the watch using
Code:
adb push boot.img /sdcard/Download
Install a file manager on the watch because it does not include one by default. We will need it to select the boot.img file the Magisk app. I used File Manager TV USB OTG Cloud from the Play Store
Install the latest version of the Magisk APK from the Github link below on the watch by running
Code:
adb install name-of-magisk.apk
Releases · topjohnwu/Magisk
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
Launch the Magisk app, click Install, choose Select and Patch a File, then browse to the downloaded boot.img file
Click Let's Go and the magisk-patched boot image will be created in the Download folder
Transfer the image back to your computer using
Code:
adb pull /sdcard/Download/name-of-patched-image
Run
Code:
adb reboot bootloader
to reboot the watch into Fastboot
Verify the device shows up by using
Code:
fastboot devices
Unlock the bootloader of the watch using
Code:
fastboot flashing unlock
View attachment 5925307
Confirm the message on the watch to unlock and wipe the device
Flash and boot the newly created Magisk image using
Code:
adb flash boot name-of-patched-image.img
Select Start in Fastboot to start the watch
After waiting an extremely long time, the watch will hopefully start and will need to be setup again
Reinstall the Magisk app using
Code:
adb install name-of-magisk.apk
Launch the app and it might prompt that it needs to restart the watch
With the watch started and setup, start an adb shell by running
Code:
adb shell
Then, run su to escalate to root privilege. The shell should change symbols from $ to # and running
Code:
whoami
should result in root
View attachment 5925313Bypassing SafetyNet
Download the YASNAC - SafetyNet Checker APK from GitHub:
Releases · RikkaW/YASNAC
Yet Another SafetyNet Attestation Checker. Contribute to RikkaW/YASNAC development by creating an account on GitHub.
github.com
Install it on the watch using
Code:
adb install name-of-yasnac.apk
(Optional) Open the app and run the SafetyNet Attestation to verify your device fails
Download the SafetyNet Fix Magisk module from GitHub:
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
Transfer it to watch using
Code:
adb push safetynet-fix-v2.4.0.zip /sdcard/Download
Start an adb shell with the watch using
Code:
adb shell
Elevate to root privileges with
Code:
su
Install the module with
Code:
magisk --install-module /sdcard/Download/safetynet-fix-v2.4.0.zip
Once installed, restart your watch
Now, run YASNAC SafetyNet Attestation again, and you should pass!
Troubleshooting/Tips
If booting the Magisk image results in a bootloop, you can unbrick the device by flashing the corresponding stock boot.img image using
Code:
adb flash boot boot.image
Additionally, you can get into FastBoot mode by tapping on the top left and bottom right of the screen at the same time as the device is booting and the white "G" logo appears.
If Magisk doesn't see the file, try doing the following to your file browser app:
Settings > Apps & Notifications > App permissions > Files and media > AppName > Allow all the time
Wireless debugging allows you to do almost all of this guide except booting the patched boot.img file in Magisk. To enable wireless debugging, go to Settings > Developer options > Check Debug over Wi-Fi. Then, in developer options still, go to Wireless debugging and turn it on. From here, you can connect to your watch remotely from your PC using
Code:
adb connect watchip
ThanksHuge thanks to Asmita Jha (Twitter @aj_0x00) who was there during the first 2 days of the rooting attempts and helped troubleshoot throughout. Additionally, big thanks to Stack Smashing (Twitter @ghidraninja) for giving us the idea to patch the Magisk file on the watch itself, instead of patching the boot image on another device running Magisk. Additionally, this wouldn't be possible without the help of the Google team who gave us access to device and the prototype cradles to interface with the watch reliably. Huge thanks to everyone running Hardwear.io this year where this method was discovered during the Hardpwn hardware hacking contest.
Future PlansTo make the process more accessable, a cheap interfacing solution needs to be created. My idea is to 3D print an enclosure and use pogo pins. Please reach out if have any questions, concerns, or information that would make the process easier. You can find me on Twitter @breaddisease
https://twitter.com/breaddisease
Thanks!
Click to expand...
Click to collapse
Cool
breaddisease said:
You might need to allow the app Files and media permissions all the time, like this:
Settings > Apps & Notifications > App permissions > Files and media > AnExplorer > Allow all the time
Click to expand...
Click to collapse
Thanks! That was it. Now the computer just refuses to recognize it as a fastboot device. It recognizes it with the watch fully on, so I know my wiring and pins are correct.
ClarkIV said:
Thanks! That was it. Now the computer just refuses to recognize it as a fastboot device. It recognizes it with the watch fully on, so I know my wiring and pins are correct.
Click to expand...
Click to collapse
Nice, good to hear! What's the output of
Code:
sudo fastboot devices
Or, if you're on Windows, an elevated terminal with
Code:
fastboot devices
Y'all realize that we already managed to root the watch a long time ago? https://forum.xda-developers.com/t/pixel-watch-successfully-bootloader-unlocked.4508253/
A lot of questions are also answered there.
Yes, it breaks safetynet. You can install this magisk module to get it back.
KineSight said:
Does Rooting it break the Google Pay functionality or SafetyNet (if it has one) ?
Click to expand...
Click to collapse
Tiebe said:
Y'all realize that we already managed to root the watch a long time ago? https://forum.xda-developers.com/t/pixel-watch-successfully-bootloader-unlocked.4508253/
A lot of questions are also answered there.
Click to expand...
Click to collapse
I was not aware that it had been done already! Thanks for the info! I thought I was the first
breaddisease said:
I was not aware that it had been done already! Thanks for the info! I thought I was the first
Click to expand...
Click to collapse
Sadly, no.
Another small thing: You shouldn't download the OTA zip, but the factory images. The OTA zip doesn't always have full boot image, and only a patch image (boot.img.p), which is used in the updating process for patching the current boot image to the newer version. The factory images always have a full boot image.
Other than that: great guide!
Tiebe said:
Sadly, no.
Another small thing: You shouldn't download the OTA zip, but the factory images. The OTA zip doesn't always have full boot image, and only a patch image (boot.img.p), which is used in the updating process for patching the current boot image to the newer version. The factory images always have a full boot image.
Other than that: great guide!
Click to expand...
Click to collapse
Ok, thanks! I updated step 6 and 8 accordingly.
Would it be an issue if someone flashed an un-updated watch with the latest boot.img? Like should I recommend flashing the appropriate version's boot.img, or updating to the latest version before flashing the latest boot.img? Thanks!
breaddisease said:
Ok, thanks! I updated step 6 and 8 accordingly.
Would it be an issue if someone flashed an un-updated watch with the latest boot.img? Like should I recommend flashing the appropriate version's boot.img, or updating to the latest version before flashing the latest boot.img? Thanks!
Click to expand...
Click to collapse
Always flash the boot.img of the version that you're currently on. Happy to help!
@breaddisease
I've also noticed that the safetynet module patched by Displax seems to work better in most cases than the original one by kdrag0n. The one by Displax is just a fork of the one by kdrag0n, with some changes.
breaddisease said:
Nice, good to hear! What's the output of
Code:
sudo fastboot devices
Or, if you're on Windows, an elevated terminal with
Code:
fastboot devices
Click to expand...
Click to collapse
I'm on Linux and 'sudo fastboot devices' didn't list any device. I can communicate via ADB over USB so I know the cable is working. In fastboot mode, the device doesn't show up under 'lsusb' either. I have tried USB 2 and 3 ports.
ClarkIV said:
I'm on Linux and 'sudo fastboot devices' didn't list any device. I can communicate via ADB over USB so I know the cable is working. In fastboot mode, the device doesn't show up under 'lsusb' either. I have tried USB 2 and 3 ports.
Click to expand...
Click to collapse
Are you providing it power through the left pin? Maybe its required for fastboot
breaddisease said:
Are you providing it power through the left pin? Maybe its required for fastboot
Click to expand...
Click to collapse
Yes, I am powering it. Verified by the watch showing its charging when fully booted. Were you on Linux or Windows for this? If Linux what Distro?