Related
Hello guys many users bought Yureka Plus With Stock 4.4.4 and they want to root their device without Installing Cyanogen OS.I will write some easy steps here to root your Yureka Plus.You don't need to unlock your bootloader
Note: If u Want to Root Your Device Running on CM 12.0/CM 12.1 Refer here
STEP:1 Download Kingroot App from here
STEP:2 Install and Open the App.
STEP:3 Click On Root Now (Must Have Active Internet Connection) It Will Take 3-5 Mins
STEP:4 Done, You have rooted your devices sucessfully
If u want to replace Kingroot with SuperSu then follow these steps
Step 1 Download Replace Kingroot_With_SuperSu.zip From here
Step 2 Extract all files and place mrw folder in your internal storage
Step 3 Download Terminal Emulator App from Play Store Link
Step 4 Open Terminal Emulator App and Type su (After Enter above Command, it will ask you for Root permissions, Grant Root permissions)
Step 5 Now after this copy this Command sh /sdcard/mrw/root.sh
(Now, it will start running script & you have to wait for some time, approx 2-3 minutes, make sure your mobile data is turned on.)
Step 6 Now It will automatically open
SuperSu App.
Step 7 Now, it will ask you for update Superuser binary, Click on Continue button & Select Normal Mode
Step 8 It may ask you that, other party root apps are already installed, so you have to click on OK button & it will remove Kingroot app from your phone & Supersu app will come & you are done !
Note: Deactivate Kingroot from Device Adminstrators before typing Command in Terminal Emulator
Hit Thanks If u Rooted your device suceesfully
Reserved
Kingroot Works !
It worked for me.
Not working for me
Message came as failed...
First things first, I'd like to give a shoutout to diegocr for making the test version of Lineage OS on tank devices! Before following this tutorial, your Fire TV Stick 2 needs to be unlocked and rooted before installing these mods.
{REQUIREMENTS}: A computer that has adb connections and/or an android phone with Termux commands to run adb, can be found here (simply copy and paste while following the tutorial): https://github.com/MasterDevX/Termux-ADB, you need to be connected to the same internet in order for the connecting to work properly, an already rooted tank that's unlocked, a Google Account Manager which needs to be installed for those who have issues signing into the Google Play Store along with a command you need to run to allow it to work, and a file which contains a PlayFire folder which you'll need to move on the root of the /0/sdcard directory.
Step 1: Download this version of Gapps its tvstock and the system partition has plenty of space available. Link: https://opengapps.org/
The platform needs to be arm, android version is 5.1, and the variant is tvstock.
Step 2: Now that you have Gapps downloaded, download this PlayFire folder along with Google Account Manager before even installing Gapps within TWRP (on the Fire TV Stick). Google Account Manager (Don't download the latest version or else you will get a parse error message due to incompatibility): https://www.apkmirror.com/apk/googl...unt-manager-5-1-1743759-android-apk-download/, PlayFire file w Folder (extract the file and put the PlayFire on the /sdcard directory): https://forum.xda-developers.com/attachment.php?attachmentid=4205571&d=1499532978
Step 3: After downloading and putting the PlayFire folder on the root of your sdcard, reboot into TWRP and flash the Gapps zip file with tv stock and wait until its finished then reboot your Fire TV Stick 2. You'll notice that its going to optimize from 0 to 108, its completely normal since its implementing these system apps into your android system. Upon boot and everything, be sure to connect to the internet due to Lineage OS shutting off the wifi, then run these commands for the Google Play Store to work within terminal as root. What I mean by that is you need to connect to terminal as (adb connect 192.168.x.x), then add (adb shell, su), and finally copy and paste this given command and you're all set: sh /sdcard/PlayFire/LazyNoTouch.sh
Step 4: Everything should work beyond this point. If you're having difficulty with this guide, private message me and I'll send my TWRP backup for those who have no clue what to do.
So I haven't ever really looked into putting custom roms on my fire stick before so I had to look up what PlayFire was. I haven't had time to mod mine yet but I'm a little confused as to why PlayFire (not upgraded since 2017) would be needed if the LeanBack launcher is already on the rom, Is it just reinstalling it with all the xposed and HDXposed stuff it comes with?
Could you please post or message me your twrp backup I have tried everything and can not get it working tried many times. When I run the script nothing happens still can't use Google play or login to it. Followed the steps to the tee.
Worked without any issues! thanks!
Thank you very much @theflashfromthecw it work great, but do you have a patch for working mic search ?
---------- Post added at 05:04 PM ---------- Previous post was at 04:43 PM ----------
The device is freezig after 3 minutes with the newest gapps and the linkes Google ACC manager. Any solutions ?
Try to install xposed-v87-sdk22-arm.zip with Xinstall and Downgrade option enabled before or adb install -d com.google.android.gsf.login_5.1-1743759-22_minAPI21(nodpi)_apkmirror.com.apk to downgrade if PlayStore update it afterward.
Is this still working? I have tried to get this working on FTV Tank running Lineage, but no luck with sign in..
Thanks!
update: I was able to get it working, I needed to enable developer options, and then root access because the script was not completing (needed for making changes to /system).
Thanks again for putting this together!
theflashfromthecw said:
First things first, I'd like to give a shoutout to diegocr for making the test version of Lineage OS on tank devices! Before following this tutorial, your Fire TV Stick 2 needs to be unlocked and rooted before installing these mods.
{REQUIREMENTS}: A computer that has adb connections and/or an android phone with Termux commands to run adb, can be found here (simply copy and paste while following the tutorial): https://github.com/MasterDevX/Termux-ADB, you need to be connected to the same internet in order for the connecting to work properly, an already rooted tank that's unlocked, a Google Account Manager which needs to be installed for those who have issues signing into the Google Play Store along with a command you need to run to allow it to work, and a file which contains a PlayFire folder which you'll need to move on the root of the /0/sdcard directory.
Step 1: Download this version of Gapps its tvstock and the system partition has plenty of space available. Link: https://opengapps.org/
The platform needs to be arm, android version is 5.1, and the variant is tvstock.
Step 2: Now that you have Gapps downloaded, download this PlayFire folder along with Google Account Manager before even installing Gapps within TWRP (on the Fire TV Stick). Google Account Manager (Don't download the latest version or else you will get a parse error message due to incompatibility): https://www.apkmirror.com/apk/googl...nt-manager-5-1-1743759-android-apk-download/, PlayFire file w Folder (extract the file and put the PlayFire on the /sdcard directory): https://forum.xda-developers.com/attachment.php?attachmentid=4205571&d=1499532978
Step 3: After downloading and putting the PlayFire folder on the root of your sdcard, reboot into TWRP and flash the Gapps zip file with tv stock and wait until its finished then reboot your Fire TV Stick 2. You'll notice that its going to optimize from 0 to 108, its completely normal since its implementing these system apps into your android system. Upon boot and everything, be sure to connect to the internet due to Lineage OS shutting off the wifi, then run these commands for the Google Play Store to work within terminal as root. What I mean by that is you need to connect to terminal as (adb connect 192.168.x.x), then add (adb shell, su), and finally copy and paste this given command and you're all set: sh /sdcard/PlayFire/LazyNoTouch.sh
Step 4: Everything should work beyond this point. If you're having difficulty with this guide, private message me and I'll send my TWRP backup for those who have no clue what to do.
Click to expand...
Click to collapse
Hi.... Will this method work on pre-rooted stock image ROM?
Unable to sign-in
Hi. Thanks for this guide. I have completed as you have asked. The GAPPs is installed but I am unable to sign-in to the accounts. Please advice how to fix this.
Hi guys, nice work! Will it work on a 1st generation FireTV (box, not stick)?
NihaalMoosa said:
Hi. Thanks for this guide. I have completed as you have asked. The GAPPs is installed but I am unable to sign-in to the accounts. Please advice how to fix this.
Click to expand...
Click to collapse
You must run
sh /sdcard/PlayFire/LazyNoTouch.sh
no luck
Hi
I am not able to run the script, as I have created a folder called "sdcard" on the root of the internal storage and placed the PlayFire folder there. Furthermore, I used the "sh /sdcard/PlayFire/LazyNoTouch.sh" in ADB Shell, but no luck. Do we need to root Lineage OS before we use the script? If it is, can someone kindly show me a guide, how to root, as I have never done it before.
Flash supersu
https://redirect.viglink.com/?key=e...2-1-t4016981/amp/&ref=https://www.google.com/
In twrp
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
Or im twrp without root.
adb push TV-NoTouchGsf.apk /sdcard/TV-NoTouchGsf.apk
adb shell mount -o rw /system
adb shell "mkdir /system/app/NoTouchAuthDelegate/"
adb shell "chmod 0775 /system/app/NoTouchAuthDelegate/"
adb shell "rm /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "cp /sdcard/TV-NoTouchGsf.apk /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chmod 0644 /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chown root:root /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
0815hoffi said:
Or im twrp without root.
adb push TV-NoTouchGsf.apk /sdcard/TV-NoTouchGsf.apk
adb shell mount -o rw /system
adb shell "mkdir /system/app/NoTouchAuthDelegate/"
adb shell "chmod 0775 /system/app/NoTouchAuthDelegate/"
adb shell "rm /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "cp /sdcard/TV-NoTouchGsf.apk /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chmod 0644 /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
adb shell "chown root:root /system/app/NoTouchAuthDelegate/NoTouchAuthDelegate.apk"
Click to expand...
Click to collapse
I used your suggested method without the root. It worked
If someone else wants to try this method. I did the following steps:
1. Flashed Gapps.
2. Downloaded the PlayFire (mentioned on the first page of the thread)
3. Did the unzip process and from the sub-folder (where different files exist) ran the terminal and the commands that @0815hoffi mentioned.
4. Did reboot system and when Lineage OS loaded, I manually ran the Google Account Manager (mentioned on the first page of the thread).
any advice on how to properly activate recommendations on leanback
everything else works
lars1384 said:
I used your suggested method without the root. It worked
If someone else wants to try this method. I did the following steps:
1. Flashed Gapps.
2. Downloaded the PlayFire (mentioned on the first page of the thread)
3. Did the unzip process and from the sub-folder (where different files exist) ran the terminal and the commands that @0815hoffi mentioned.
4. Did reboot system and when Lineage OS loaded, I manually ran the Google Account Manager (mentioned on the first page of the thread).
Click to expand...
Click to collapse
would this work with the latest lineage os..?
For me it has not works with the latest.
With
lineage-12.1-20200221-UNOFFICIAL-tank.zip
It has worked.
I Think MicroG support in latest is the Problem maybe.
Cant seem to download tvstock version for the gapps you mentioned. As soon as I select platform and android version.. the tvstock button gets disabled
seems like tvstock is available from android 6.0 onwards for arm platform.
Please help or point me to a compatible gapps zip
Cant find gapps for arm processor, Android 5.1 with tvstock variant. Any help would greatly be appreciated
Mhtkmr25 said:
Cant find gapps for arm processor, Android 5.1 with tvstock variant. Any help would greatly be appreciated
Click to expand...
Click to collapse
Me too. Seems like opengapps doesn't have a mirror for that one anymore. I tried everything I could think of to search for it too, I even tried to build it from source and failed. But I kept reading every post I could and the best I could come up was finding this link:
https://www.androidfilehost.com/?fid=8889791610682906163
from this post from @diegocr, who is the OP of this build of LOS 12.1 for tank:
https://forum.xda-developers.com/t/rom-unlocked-tank-lineageos-12-1.3961110/post-83220635
It works! Didn't have to mess with any scripts because I couldn't actually find the gapps .zip I needed for those anyway. It's already modified. I just had to reboot into TWRP and flash it.
I'm not sure what the actual tvstock would have had that this doesn't. It does seem stripped down, but that was what I was hoping for when I opened up the thing to short out CLK.
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
I just wanted to gather resources and guidance on workarounds for caveats found in:
nVidia Shield Experience Upgrade 9.0.0 with Android 11
Scoped storage for instance.
New Google TV launcher
Caution: I'm not responsible if you end up bricking your nVidia Shield Android TV.
Change default launcherLauncher alternativesFLauncher
https://play.google.com/store/apps/details?id=me.efesser.flauncher
https://gitlab.com/etienn01/flauncher
Example: FLauncher
Install FLauncher from Google Play store.
Open FLauncher to make sure it works.
Enable ADB over network on the nVidia Shield (developer options).
Connect ADB from a computer with android-tools.
Disable default launcher with following ADB command:
Code:
adb shell pm disable-user --user 0 com.google.android.tvlauncher
Disconnect ADB.
Press "Home" button on the nVidia Shield. This should open FLauncher.
Instructions
https://techmogulchannel.com/tutori...lt-launcher-to-custom-launcher-windows-guide/
https://www.reddit.com/r/AndroidTV/comments/o96tun/how_to_install_a_3rdparty_launcher_as_default_on/
Set scoped storage permissionsExample: Solid File Explorer
Markdown (GitHub flavored):
### Example session with nVidia Shield Android TV
#### Start ADB server
adb start-server
#### Connect (approve request on the Shield)
adb connect 192.168.86.36:5555
#### Solid Explorer
adb shell cmd appops get --uid pl.solidexplorer2
adb shell cmd appops set --uid pl.solidexplorer2 android:MANAGE_EXTERNAL_STORAGE allow
adb shell cmd appops set --uid pl.solidexplorer2 android:REQUEST_INSTALL_PACKAGES allow
#### Disconnect
adb disconnect
#### Turn off ADB server
adb kill-server
Instructions
https://www.codetd.com/en/article/10481938
https://forum.xda-developers.com/t/...adb-on-note-10-updated-to-android-11.4221617/
https://developer.android.com/train...es#enable-manage-external-storage-for-testing
https://www.reddit.com/r/androiddev/comments/mscu80/as_a_user_is_it_possible_for_me_to_grant_an_old/
Roll back to 8.2.3Download
https://developer.nvidia.com/gameworksdownload#?search=recovery os image
Instructions
https://developer.download.nvidia.c...ar/howtoflash/How-To-Flash-Recovery-Image.txt
https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
https://forum.xda-developers.com/t/3321404/
https://forum.xda-developers.com/t/4392605/#post-86397133 by @perieanuo.
Other related guides by me
Ready made Leanback Icons and Shortcuts for "regular" Android Apps
[Tool][Windows][PowerShell] Android Platform Tools Updater (ADB & Fastboot)
Thanks for this !
I just hate this google tv launcher update and those F****** ads.
Now it's clean, Flauncher looks great
Thank you for that awesome guide
I have one question regarding scoped storage permissions. I'm trying to achieve the same with Kodi like you did with Solid File Explorer.
The first command worked fine: adb shell cmd appops get --uid org.xbmc.kodi
I get the following output:
Uid mode: LEGACY_STORAGE: allow
TAKE_AUDIO_FOCUS: allow; time=+2d3h23m52s536ms ago
WAKE_LOCK: allow; time=+2d3h23m52s331ms ago; duration=+22m38s145ms
READ_EXTERNAL_STORAGE: allow; time=+14h44m6s853ms ago
WRITE_EXTERNAL_STORAGE: allow
Unfortunately, when I try to execute the 2nd command adb shell cmd appops set --uid org.xbmc.kodi android:MANAGE_EXTERNAL_STORAGE allow I get the following error:
Error: Unknown operation string: android:MANAGE_EXTERNAL_STORAGE
Is there anything that I'm missing or not possible with Kodi?
No_Reason said:
Thank you for that awesome guide
I have one question regarding scoped storage permissions. I'm trying to achieve the same with Kodi like you did with Solid File Explorer.
The first command worked fine: adb shell cmd appops get --uid org.xbmc.kodi
I get the following output:
Uid mode: LEGACY_STORAGE: allow
TAKE_AUDIO_FOCUS: allow; time=+2d3h23m52s536ms ago
WAKE_LOCK: allow; time=+2d3h23m52s331ms ago; duration=+22m38s145ms
READ_EXTERNAL_STORAGE: allow; time=+14h44m6s853ms ago
WRITE_EXTERNAL_STORAGE: allow
Unfortunately, when I try to execute the 2nd command adb shell cmd appops set --uid org.xbmc.kodi android:MANAGE_EXTERNAL_STORAGE allow I get the following error:
Error: Unknown operation string: android:MANAGE_EXTERNAL_STORAGE
Is there anything that I'm missing or not possible with Kodi?
Click to expand...
Click to collapse
Are you using the latest version of Android platform-tools? I also got some errors when following a guide, turned out the command syntax had changed a little with newer versions of adb.
https://developer.android.com/studio/releases/platform-tools#downloads
I just switched to the latest version of Android platform-tools.
adb version is giving me:
Android Debug Bridge version 1.0.41
Version 32.0.0-8006631
But I still get the same error message as mentioned above
Any idea, why it's still failing? Does the app itself need to support this?
hi,
i downgraded but the flashing is not really like described here
https://developer.download.nvidia.c...ar/howtoflash/How-To-Flash-Recovery-Image.txt
those 2 are incorrect:
- fastboot flash dtb mdarcy.dtb.img
- fastboot flash vbmeta vbmeta.img
in my case i did (the files were in "c:\adb\822" folder, i used official 8.2.2 recovery image, but tested the same for 8.2.3 and 8.2.0)
fastboot flash staging ./822/blob
fastboot flash boot ./822/boot.img
fastboot flash recovery ./822/recovery.img
fastboot flash system ./822/system.img
fastboot flash vendor ./822/vendor.img
fastboot flash dtb ./822/tegra210-darcy-p2894-0050-a08-00.dtb
(attention i choosed /tegra210-darcy-p2894-0050-a08-00.dtb because my shield was this version, to be checked before flashing in settings/about...)
I tried with and without dtb and with and without erasing user data from fastboot menu (the last option)
I guess mdarcy.dtb.img and vbmeta.img are from other recovery archives, my test was done 27 jan 2022, maybe nvidia modified those recovery archives?
anyway, for inexperienced users it should be more clear what to flash, in what order, why writing this and that, the tutos for this downgrade are a mess. someone on reddit says we should format all those partitions but he says it at the end of his post, so if you respect command orders and reboot shield you're screwed.
my 2 cts, you should write ALL partitions provided by nvidia in archive after unlocking bootloader (maybe formatting them before??? but with UPS attached, risky thing btw), reset shield, relock bootloader and maybe reset shield from bootloader menu or gui.
i hope a pro take this in hand explaining for us
in the process i managed to fry my 'away' usb port power (it works well as debug port but his power control chip is dead, tried already deactivating usd debug and usb file sharing and reflashing 3 times like i described before, but it's clearrly a hardware issue). well, this one it's on me, I had olimex usb separator with power supply conected and after reflash i set that away usb as normal port, mayhe the two devices (shield and olimex usb-iso isolator tried to power the +5V line at once and the nvidia one was the weaker one). normally nvidia should entered protected mode, but i'm not the hw designer on that one
Any you guys know how to force landscape android tv 9, whole apks I used to forces doesn't work, I have 2015 and 2017 models, please help.
No_Reason said:
I just switched to the latest version of Android platform-tools.
adb version is giving me:
Android Debug Bridge version 1.0.41
Version 32.0.0-8006631
But I still get the same error message as mentioned above
Any idea, why it's still failing? Does the app itself need to support this?
Click to expand...
Click to collapse
Hmm. I'm certainly no expert at this. But what you say about the app need to support it might make sense. With the get command on Solid Explorer, I saw that permission that I could set, but you can't.
baba702 said:
Any you guys know how to force landscape android tv 9, whole apks I used to forces doesn't work, I have 2015 and 2017 models, please help.
Click to expand...
Click to collapse
Tried hotfix 3?
https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/481434/shield-experience-upgrade-90-hotfix-image/
o-l-a-v said:
Tried hotfix 3?
https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/481434/shield-experience-upgrade-90-hotfix-image/
Click to expand...
Click to collapse
Thank you I didn't know about it I'll try
Ok just I installed hotfix 3 but I'm still have several issues, now button mapper doesn't work and the screen rotation doesn't work, any help
baba702 said:
Ok just I installed hotfix 3 but I'm still have several issues, now button mapper doesn't work and the screen rotation doesn't work, any help
Click to expand...
Click to collapse
If you use button remapper so change default launcher, use the method in the original post instead to just disable the default launcher app. Else, ask the button remapper developer I guess.
For the 2nd problem (orientation), I think there is a adb command to set it. Google it and see what you find.
Edit: Orientation, found some related info:
https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/481782/shield-experience-upgrade-90-known-issues/3206852/
I
o-l-a-v said:
If you use button remapper so change default launcher, use the method in the original post instead to just disable the default launcher app. Else, ask the button remapper developer I guess.
For the 2nd problem (orientation), I think there is a adb command to set it. Google it and see what you find.
Edit: Orientation, found some related info:
https://www.nvidia.com/en-us/geforce/forums/shield-tv/9/481782/shield-experience-upgrade-90-known-issues/3206852/
Click to expand...
Click to collapse
I give whole the permite but doesn't work the buttons remapper, something with YouTube vanced is the problem, I unistalled and that works, rotation I tried with whole permite included the energy optimization access but no work
perieanuo said:
hi,
i downgraded but the flashing is not really like described here
https://developer.download.nvidia.c...ar/howtoflash/How-To-Flash-Recovery-Image.txt
those 2 are incorrect:
- fastboot flash dtb mdarcy.dtb.img
- fastboot flash vbmeta vbmeta.img
in my case i did (the files were in "c:\adb\822" folder, i used official 8.2.2 recovery image, but tested the same for 8.2.3 and 8.2.0)
fastboot flash staging ./822/blob
fastboot flash boot ./822/boot.img
fastboot flash recovery ./822/recovery.img
fastboot flash system ./822/system.img
fastboot flash vendor ./822/vendor.img
fastboot flash dtb ./822/tegra210-darcy-p2894-0050-a08-00.dtb
(attention i choosed /tegra210-darcy-p2894-0050-a08-00.dtb because my shield was this version, to be checked before flashing in settings/about...)
I tried with and without dtb and with and without erasing user data from fastboot menu (the last option)
I guess mdarcy.dtb.img and vbmeta.img are from other recovery archives, my test was done 27 jan 2022, maybe nvidia modified those recovery archives?
anyway, for inexperienced users it should be more clear what to flash, in what order, why writing this and that, the tutos for this downgrade are a mess. someone on reddit says we should format all those partitions but he says it at the end of his post, so if you respect command orders and reboot shield you're screwed.
my 2 cts, you should write ALL partitions provided by nvidia in archive after unlocking bootloader (maybe formatting them before??? but with UPS attached, risky thing btw), reset shield, relock bootloader and maybe reset shield from bootloader menu or gui.
i hope a pro take this in hand explaining for us
in the process i managed to fry my 'away' usb port power (it works well as debug port but his power control chip is dead, tried already deactivating usd debug and usb file sharing and reflashing 3 times like i described before, but it's clearrly a hardware issue). well, this one it's on me, I had olimex usb separator with power supply conected and after reflash i set that away usb as normal port, mayhe the two devices (shield and olimex usb-iso isolator tried to power the +5V line at once and the nvidia one was the weaker one). normally nvidia should entered protected mode, but i'm not the hw designer on that one
Click to expand...
Click to collapse
this is really good info - seriously. I'm about to downgrade to 8.2.3 on the 2017_16gb model and I'm trying to take it all in. Weird how there's not a ton of good information on this. Did you follow any other videos or guides?
Alekos said:
this is really good info - seriously. I'm about to downgrade to 8.2.3 on the 2017_16gb model and I'm trying to take it all in. Weird how there's not a ton of good information on this. Did you follow any other videos or guides?
Click to expand...
Click to collapse
hi,
i did kinda mixup of some guides like
https://www.reddit.com/r/ShieldAndroidTV/comments/s3yqe1
(also tested like he said, first fastboot erase boot/staging/recovery/system/vendor, then write those)
the procedure was as simpliy as this:
__________________________________________________________________________________________________________________
How to downgrade your Shield TV Pro back to 8.2.3 (Android 9)
The first step is to go to Settings, Device Preferences, About, tap build number 7-8 times for developer options and enable USB debugging and allow debugging through your PC. Before you reboot to the bootloader, plug in a keyboard or your Shield Controller to continue, then input adb reboot bootloader (must have drivers installed), unlock bootloader, and factory reset, reboot and unplug the USB and power for a full unlock or else you'll get "write failed" when flashing.
first, wipe partitions:
fastboot erase boot
fastboot erase staging
fastboot erase recovery
fastboot erase system
fastboot erase vendor
second, flash partitions (i saved/unzipped in c:\adb\823 the files, that's why "./823/" appears below)
fastboot flash boot ./823/boot.img
fastboot flash staging ./823/blob
fastboot flash recovery ./823/recovery.img
fastboot flash system ./823/system.img
fastboot flash vendor ./823/vendor.img
I relocked bootloader at the end
fastboot oem lock (or via bootloader GUI)
Just used a simple usb keyboard ( a french one, "A" was in the place of "Q" key) and bootloader use US layout as default for keyboard.
The USB cable must be a quality one, mine was USB3 one, 1m long.
Hey, so you guys don't recommend updating to Android 11 on the 2017 Shield TV?
I'm still running Android 9 (NVidia Experience 8.2.3) and everything works well. Will I gain anything by updating?
Ghisy said:
Hey, so you guys don't recommend updating to Android 11 on the 2017 Shield TV?
I'm still running Android 9 (NVidia Experience 8.2.3) and everything works well. Will I gain anything by updating?
Click to expand...
Click to collapse
I'd wait for next stable/ non-hotfix release, and then check feedback on Reddit and the nVidia forum before doing the jump.
But I won't bother rolling back to 8.2.3 either, 9.0.0 works OK for me. If you're hosting Plex server on your Shield, definitely wait. I only use it as a media player, nothing fancy.
o-l-a-v said:
I'd wait for next stable/ non-hotfix release, and then check feedback on Reddit and the nVidia forum before doing the jump.
But I won't bother rolling back to 8.2.3 either, 9.0.0 works OK for me. If you're hosting Plex server on your Shield, definitely wait. I only use it as a media player, nothing fancy.
Click to expand...
Click to collapse
Well, I guess 9.0.1 is the stable one apparently: https://9to5google.com/2022/02/15/shield-tv-9-0-1-update-android-11/
I need to wait for the developer image because I want to root my Shield TV again. Although there's no guide here that's up to date unfortunately...
baba702 said:
I
I give whole the permite but doesn't work the buttons remapper, something with YouTube vanced is the problem, I unistalled and that works, rotation I tried with whole permite included the energy optimization access but no work
Click to expand...
Click to collapse
For the screen orientation setting, have you tried something as simple as a "forced rotation" app? I've used that for apps that normally come up in portrait that i wanted to force into landscape mode (ie YouTube Vanced, Magisk Manager, etc).
Here's one that's worked for me in the past (side loaded):
https://m.apkpure.com/set-orientation/com.googlecode.eyesfree.setorientation
o-l-a-v said:
I just wanted to gather resources and guidance on workarounds for caveats found in:
nVidia Shield Experience Upgrade 9.0.0 with Android 11
Scoped storage for instance.
New Google TV launcher
Caution: I'm not responsible if you end up bricking your nVidia Shield Android TV.
Change default launcherLauncher alternativesFLauncher
https://play.google.com/store/apps/details?id=me.efesser.flauncher
https://gitlab.com/etienn01/flauncher
Example: FLauncher
Install FLauncher from Google Play store.
Open FLauncher to make sure it works.
Enable ADB over network on the nVidia Shield (developer options).
Connect ADB from a computer with android-tools.
Disable default launcher with following ADB command:
Code:
adb shell pm disable-user --user 0 com.google.android.tvlauncher
Disconnect ADB.
Press "Home" button on the nVidia Shield. This should open FLauncher.
Instructions
https://techmogulchannel.com/tutori...lt-launcher-to-custom-launcher-windows-guide/
https://www.reddit.com/r/AndroidTV/comments/o96tun/how_to_install_a_3rdparty_launcher_as_default_on/
Set scoped storage permissionsExample: Solid File Explorer
Markdown (GitHub flavored):
### Example session with nVidia Shield Android TV
#### Start ADB server
adb start-server
#### Connect (approve request on the Shield)
adb connect 192.168.86.36:5555
#### Solid Explorer
adb shell cmd appops get --uid pl.solidexplorer2
adb shell cmd appops set --uid pl.solidexplorer2 android:MANAGE_EXTERNAL_STORAGE allow
adb shell cmd appops set --uid pl.solidexplorer2 android:REQUEST_INSTALL_PACKAGES allow
#### Disconnect
adb disconnect
#### Turn off ADB server
adb kill-server
Instructions
https://www.codetd.com/en/article/10481938
https://forum.xda-developers.com/t/...adb-on-note-10-updated-to-android-11.4221617/
https://developer.android.com/train...es#enable-manage-external-storage-for-testing
https://www.reddit.com/r/androiddev/comments/mscu80/as_a_user_is_it_possible_for_me_to_grant_an_old/
Roll back to 8.2.3Download
https://developer.nvidia.com/gameworksdownload#?search=recovery os image
Instructions
https://developer.download.nvidia.c...ar/howtoflash/How-To-Flash-Recovery-Image.txt
https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
https://forum.xda-developers.com/t/3321404/
https://forum.xda-developers.com/t/4392605/#post-86397133 by @perieanuo.
Other related guides by me
Ready made Leanback Icons and Shortcuts for "regular" Android Apps
[Tool][Windows][PowerShell] Android Platform Tools Updater (ADB & Fastboot)
Click to expand...
Click to collapse
Do you need to be rooted to Set Scoped Storage permissions or install an alternative launcher?
Is there a guide for rooting the Nvidia Shield 2017 using linux?
Thanks.
bdika
first off, huge shout out to @JengaMasterG for TWRP for these devices. Without him, this super simple method wouldn't be possible.
What You'll Need
- Android 11 most recent update
- TWRP: TWRP for Surface Duo (credits to @JengaMasterG )
- Unlocked Bootloader
- ADB/Fastboot: ADB/Fastboot Install (what i use)
- Magisk
video
YT Tutorial
Bootloader Unlock
1.) Enable Developer Options via tapping Build Number over and over in the About Device part of settings
2.) Enable USB Debugging and OEM Unlock
3.) Plug device into the computer, and type the following command in cmd.exe, hit enter
Code:
adb devices
4.) You may get a pop up on screen requesting permission, always allow it
5.) Type the following and hit enter
Code:
adb reboot bootloader
6.) Once in the bootloader, your device might not be recognized right away and will need the driver manually installed via Device manager (see video for that)
7.) Once device is recognized, type the following command
Code:
fastboot flashing unlock
8.) Allow the unlocking of the Bootloader on device screen. this will erase everything
9.) Allow the device to fully boot up, enable USB Debugging again and continue the tutorial!
Instructions
1.) Rename Magisk-vxx.x.apk to Magisk.zip
2.) Enable USB Debugging
3.) Type the following to make sure your computer sees the device (in cmd.exe)
Code:
adb devices
4.) You may get a pop up on your device's screen asking for adb permission, check the always allow and hit ok
5.) Type the follow command to reboot to bootloader (in cmd.exe)
Code:
adb reboot bootloader
6.) Once you're in the booloader and its unlocked, download the TWRP image from above
7.) Use the following fastboot command to boot into TWRP
Code:
fastboot boot twrp.img
8.) Once TWRP boots, keep your device plugged in via usb and type the following command into cmd.exe and hit enter
Code:
adb shell twrp sideload
9.) Once in sideload, you can type the following with magisk.zip and root your device!
Code:
adb sideload magisk.zip
10.) Use the following command to reboot and you're done!
Code:
adb reboot
congrats! you're rooted!
LETS GOOOO!! HEROOO!! Super easy and working on the latest December 2022 update! Felt way safer as well, not so much concern over twrp as we only booted into it, and then I just used the standard magisk and it worked excellent without worrying about all types of patches and versions aside from the latest twrp for android 12 from @JengaMasterG!
Thank you! I think the renaming the magisk file from apk to zip was probably what I was doing wrong trying to follow the other methods, on top of driver errors, that were solved by uninstalling all the drivers for the duo on my surface pro, which revealed a native 'Surface Fastboot' driver. Combine that with the 15 second ADB and it's .bat ready to go command line interface, idk... it wen't so smooth and worked perfectly.
Now I can try to see if I can improve my experience with some go to methods.. I really want to enable immersive mode and hopefully increase overall volume, if possible (many devices this can be done with engineeringmode, idk yet but hopefully it does have one and hopefully I can also calibrate the gyroscope)... obviously adblock without vpn is on the menu.... can utilize the full autoruns app to stop apps from starting up at boot like in windows... and then get into some other customizations.
cqqx2 said:
LETS GOOOO!! HEROOO!! Super easy and working on the latest December 2022 update! Felt way safer as well, not so much concern over twrp as we only booted into it, and then I just used the standard magisk and it worked excellent without worrying about all types of patches and versions aside from the latest twrp for android 12 from @JengaMasterG!
Thank you! I think the renaming the magisk file from apk to zip was probably what I was doing wrong trying to follow the other methods, on top of driver errors, that were solved by uninstalling all the drivers for the duo on my surface pro, which revealed a native 'Surface Fastboot' driver. Combine that with the 15 second ADB and it's .bat ready to go command line interface, idk... it wen't so smooth and worked perfectly.
Now I can try to see if I can improve my experience with some go to methods.. I really want to enable immersive mode and hopefully increase overall volume, if possible (many devices this can be done with engineeringmode, idk yet but hopefully it does have one and hopefully I can also calibrate the gyroscope)... obviously adblock without vpn is on the menu.... can utilize the full autoruns app to stop apps from starting up at boot like in windows... and then get into some other customizations.
Click to expand...
Click to collapse
Hello! I'm rooted, but I can only read and can't write. I am Android version 122022.821.13 of Att.
So I can't delete the apk inside the system directory
linlin2az said:
Hello! I'm rooted, but I can only read and can't write. I am Android version 122022.821.13 of Att.
So I can't delete the apk inside the system directory
Click to expand...
Click to collapse
Newer Android versions, especially stock ROM, generally doesn't let you write to the system partition. Only ROMs can do that, unless you can find a way to change the partition permissions. Root alone will not allow it, no matter what you do. I used to know of a TWRP script to fix that and make the system writable, but it doesn't work on andorid 11/12/13 anyway