Database Info

HOW TO: Manually backup 3rd-party application settings and data

This tutorial will explain how to backup application data and settings for 3rd-party apps that do not have an export/import settings feature. Looking to upgrade your ROM but don't want to lose your todos/highscores/whatnots after a data wipe? Then read on..
(I've never used apps to SD, so I'm not completely sure how the data is stored with that. I'm assuming the entire data partition is moved to the SD though, so the procedures outlined in this guide are not necessary / do not apply to apps2sd)
Tools needed:
adb
Backing up settings
Run a adb shell in the command prompt and navigate to /data/data
Code:
c:\android-sdk-windows-1.5_r1\tools> adb shell
# cd /data/data
Find the folder of the app whose settings you want to backup. In android 1.5, M/SMS are stored in com.android.providers.telephony and bookmarks are in com.android.browser. For third party apps, you can use ls to list all installed apps and find your app folder manually, or use find - say I want to find the app folder for the Astrid todo app:
Code:
# ls
<.....lots of directories....>
com.timsu.astrid
<.....more directories....>
# find *astrid* -maxdepth 0
com.timsu.astrid
Now open a separate command prompt and use adb pull to copy the application's data folder to your computer. This does not copy the app itself, only its saved data and settings. App .apks reside in /data/apps, which you can also adb pull out if you want. In this example I pull out settings for Astrid:
Code:
c:\android-sdk-windows-1.5_r1\tools> adb pull /data/data/com.timsu.astrid d:\desktop\com.timsu.astrid
Feel free to replace d:\desktop with the location of your choice, of course. Repeat the above for each app folder you want to backup.
Restoring settings after a wipe
First thing to do is reinstall the apk, from sdcard, adb install, market, whatever. After the app is installed, you can restore settings in one of two ways: the easy way or the hard but safe (paranoid) way.
The Easy Way:
This quick and dirty method will give everyone full read/write/execute permissions on the application's settings/data. This is normally a Very Bad Idea with a normal linux computer, but realistically there is very little risk of this posing any real security issues on a device like a phone.
First, adb push the settings into the data folder, overwriting the app's stock settings (in this example, the astrid data I backed up) then adb shell into the phone and navigate to /data/data:
Code:
c:\android-sdk-windows-1.5_r1\tools> adb push d:\desktop\com.timsu.astrid /data/data/com.timsu.astrid
Done
c:\android-sdk-windows-1.5_r1\tools> adb shell
# cd /data/data
Now give full permissions to the app's data folder and its contents:
Code:
# chmod 777 com.timsu.astrid
# cd com.timsu.astrid
# chmod 777 * */*
And that's it. Launch the app and your settings/data should be restored.
The Hard Way
I'm not going to go into this in detail because if you're reading this, you probably know the commands to do this anyway. After you reinstall the app, the general idea is to run ls -l on the stock app data directory and its subdirectories to display the owner and permissions of each file/folder as setup by the android system. Write these down then adb push the backup app data folder in, which overwrites everything with directories and files owned by root. Then use chown and chmod to restore the original owners and permissions for each file and directory. Needless to say this can be quite a hassle if you're dealing with more than a few application backups.

is there any way to backup up wifi wep and wpa keys?
if there was i wouldnt mind wiping, but typing in a 63character long passkey gets very tedious after a while!

Wifi settings are stored in /data/misc/wifi:
-rw-rw---- system wifi 29620 2009-04-29 21:31 wpa_supplicant.conf

ah cool, thank you very much

Excel guide. I tried this before wiping my rom and installing a new one and it worked perfectly for 2 different applications. Great! Thanks!

good idea, can save some time.

Thanks for this

So ...
cyricc said:
Tools needed:
adb
Code:
c:\android-sdk-windows-1.5_r1\tools> adb pull /data/data/com.timsu.astrid d:\desktop\com.timsu.astrid
Click to expand...
Click to collapse
i am just wondering why would you use adb instead of just copying to the sdcard?!?
Code:
# mkdir /sdcard/my_backup_data
# cp /data/data/com.timsu.astrid /sdcard/my_backup_data
this would perform the same function "on the fly" without the need of even having a computer .. maybe add this into the OP?

I just used root explorer to copy the apks to sdcard

LucidREM said:
i am just wondering why would you use adb instead of just copying to the sdcard?!?
Code:
# mkdir /sdcard/my_backup_data
# cp /data/data/com.timsu.astrid /sdcard/my_backup_data
this would perform the same function "on the fly" without the need of even having a computer .. maybe add this into the OP?
Click to expand...
Click to collapse
And you can use "tar" instead of "cp" to also automagically save/restore the correct UID, GID & permissions... or compress data...

Hmm i cud write a batch script to do all this. If theres a huge percentage of windows users here that would like this let me know. Features im thinking of are
1 click backup of all apps or choose from list of apps
launcher icon / wifi settings backup
1 click restore of all apps or specific app

Daneshm90 said:
Hmm i cud write a batch script to do all this. If theres a huge percentage of windows users here that would like this let me know. Features im thinking of are
1 click backup of all apps or choose from list of apps
launcher icon / wifi settings backup
1 click restore of all apps or specific app
Click to expand...
Click to collapse
+1 here!
While these methods work fine, I am never one to reject a streamlined version. Thanks for this OP and Dane.

Scripting
Daneshm90 said:
Hmm i cud write a batch script to do all this. If theres a huge percentage of windows users here that would like this let me know. Features im thinking of are
1 click backup of all apps or choose from list of apps
launcher icon / wifi settings backup
1 click restore of all apps or specific app
Click to expand...
Click to collapse
that's very easy

TAR
joseangel.alv said:
And you can use "tar" instead of "cp" to also automagically save/restore the correct UID, GID & permissions... or compress data...
Click to expand...
Click to collapse
serious? so:
# tar /data/data/com.timsu.astrid /sdcard/my_backup_data/com.timsu.astrid.tar
would do this? or something different? i will look over the syntax myself .. that makes scripting so easy too

TAR
LucidREM said:
serious? so:
# tar /data/data/com.timsu.astrid /sdcard/my_backup_data/com.timsu.astrid.tar
would do this? or something different? i will look over the syntax myself .. that makes scripting so easy too
Click to expand...
Click to collapse
# tar -czf /sdcard/my_backup_data/com.timsu.astrid.tgz /data/data/com.timsu.astrid
this (i guess) would be the correct functioning

Any idea where the homescreen layout is saved ? is it specific to the launcher ur using ?
W/e i think my script covers that by backing up data folder. Alright guys these r the options i have so far. Anything missing ?
{
"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"
}

Launcher
Daneshm90 said:
Any idea where the homescreen layout is saved ? is it specific to the launcher ur using ?
Click to expand...
Click to collapse
that would depend on which launcher you have i suppose

LucidREM said:
that would depend on which launcher you have i suppose
Click to expand...
Click to collapse
Correct. Its the database folder within the specific launcher u are using. So in essense by backing up the whole /data folder or just ur specific launcher's /data folder u are preserving ur icons/widget layout.

Ok so here it is :
This assumes adb is in ur path.
Just place .bat file anywhere and run.

TAR
ok .. so i am just a sucker for the obvious i guess .. try this one out:
# lucid -archive
yay me! what this will do is to archive (tar) the whole /data/data folder .. not just one specific app .. then you can restore one part or all parts later (ok .. i did NOT script the restore portion)

[HOW-TO] Stock Apps for All!

After two days of fumbling around with adb, numerous nandroid backups, and ultimately wiping my system, I, with the help of my friend Kiraly (his xda username), have successfully installed the stock Messaging, Clock, Calculator and Browser apps onto my phone.
The Messaging app was of particular interest to me because I hate how the HTC Sense Messaging app always loads briefly when you enter a thread of messages, no matter how many messages are in the actual thread. Also, the stock Android Messaging app has a feature similar to BBM in that an icon within the thread notifies you when a message has actually sent.
By following the instructions contained hereunder, you agree to indemnify and hold harmless the original poster (the "OP"). I hereby disclaim all warranties and liability for any harm that may result by following the aforementioned instructions.
Installing these apps was fairly easy once we found out how it needed to be done. You will need the following:
A. Minimal knowledge of adb, or rather knowledge of how to copy and paste adb commands.
B. You will need full root (root and nand unlocked)
C. 1.47 kernel with the modified default.prop file http://forum.xda-developers.com/showthread.php?p=7138666
D. The Root Explorer app (this can be purchased in the Android Market)
E. You will need the following .apk files from BuglessBeast. They are the only apps that I have been able to successfully install. http://forum.xda-developers.com/showthread.php?t=700175
-Mms.apk
-Browser.apk
-DeskClock.apk
-Calculator.apk
STEP 1
Perform a nandroid backup.
STEP 2
Plug your phone into your computer via USB and mount the sd card.
STEP 3
Download the 1.47 kernel with the modified default.prop file. The stock kernel is also contained in the following link, and you can always revert back to it if need be. http://forum.xda-developers.com/showthread.php?p=7138666
STEP 4
Flash the modified 1.47 kernel .zip file to the root of your sd card (for all you rookies out there, simply drag the .zip file onto your sd card).
STEP 5
Reboot into recovery and install the kernel you just flashed. Then, reboot the phone.
STEP 6
Download the BuglessBeast ROM http://forum.xda-developers.com/showthread.php?t=700175
STEP 7
Unzip the BuglessBeast file. Open the unzipped file. Find the folder labeled "System", and open it. Then, find the folder labeled "App", and open it. Find the files labeled Mms.apk, Browser.apk, DeskClock.apk and Calculator.apk. Drag those files to your desktop.
STEP 8
Download and open the Root Explorer app. Scroll down to the bottom and click on the folder labeled "System." Then, at the top of the app, click "Mount R/W." After you click that, open the "app" folder. Each application has two files you need to delete. Do not delete any of the clock files. You will need to delete the following files and then quit the application when you have finished:
-Browser.apk
-Browser.odex
-Mms.apk
-Mms.odex
-Calculator.apk
-Calculator.odex
STEP 9
Open the Command Prompt if you are a Windows user or the Terminal application if you are a Mac user and navigate to the tools folder of the Android SDK. Do not boot into recovery.
STEP 10
Type the following commands in order. We will use the Browser.apk as an example, and I will assume the file is on your desktop:
Code:
adb shell
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
Code:
exit
Code:
adb push C:\Users\YourUserName\Browser.apk /system/app
Code:
adb shell
Code:
chmod 6755 /system/app/Browser.apk
Code:
exit
Code:
adb reboot
STEP 11
Rinse and repeat!
Thanks to frankenstein\ for the kenel, laydros for getting me started in the right direction, BuglessPete for the .apk files, and most importantly to Kiraly for all his assistance.
{
"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"
}

<3
10 char

I hope the push command is correct. On my Mac, when the files is on my desktop, the command is:
/adb push /Users/kpoz/Desktop/Browser.apk /system/app
Someone please let me know if the push command is not correct for Windows.

kpoz said:
I hope the push command is correct. On my Mac, when the files is on my desktop, the command is:
/adb push /Users/kpoz/Desktop/Browser.apk /system/app
Someone please let me know if the push command is not correct for Windows.
Click to expand...
Click to collapse
I'm using Ubuntu but I have a Windows lappy around with adb setup, I'll test it out and let you know.

neckface said:
I'm using Ubuntu but I have a Windows lappy around with adb setup, I'll test it out and let you know.
Click to expand...
Click to collapse
Great, thanks. I almost forgot to delete the "./" before "adb" when I was writing the tutorial. For whatever reason, on a Mac the command is ./adb, and on Windows it is simply adb.

kpoz said:
Great, thanks. I almost forgot to delete the "./" before "adb" when I was writing the tutorial. For whatever reason, on a Mac the command is ./adb, and on Windows it is simply adb.
Click to expand...
Click to collapse
Yup, same with Linux.

Just replaced the Sense Mms app with the stock one using this technique and it worked perfectly. Only thing I did differently was rather than deleting the stock files I just renamed them with a *.bak for easy restoring in case I ever need to.
Also I'm using Netarchy's kernel [FPS fix] and I did not need to do all the steps with the default.prop, I was able to mount the system folder with write permission.
And in case anyone is like me and just wants to replace the messaging app rather than all of them, I'll attach the apk for much quicker downloading. Its the apk straight out of the BuglessBeast ROM.

kpoz said:
I hope the push command is correct. On my Mac, when the files is on my desktop, the command is:
/adb push /Users/kpoz/Desktop/Browser.apk /system/app
Someone please let me know if the push command is not correct for Windows.
Click to expand...
Click to collapse
Push command is correct for windows. It may vary slightly depending on where you placed the apk files.

tehpsyc said:
Just replaced the Sense Mms app with the stock one using this technique and it worked perfectly. Only thing I did differently was rather than deleting the stock files I just renamed them with a *.bak for easy restoring in case I ever need to.
Also I'm using Netarchy's kernel [FPS fix] and I did not need to do all the steps with the default.prop, I was able to mount the system folder with write permission.
And in case anyone is like me and just wants to replace the messaging app rather than all of them, I'll attach the apk for much quicker downloading. Its the apk straight out of the BuglessBeast ROM.
Click to expand...
Click to collapse
Glad it worked for you! Thanks for attaching the Mms.apk.
I'm glad that slow, unresponsive Sense Messages app is long gone. You know there is something wrong with your app (*cough, HTC, *cough) when you get a "Loading" message when opening a thread, regardless of how many messages are in said thread.

initial said:
Push command is correct for windows. It may vary slightly depending on where you placed the apk files.
Click to expand...
Click to collapse
Thanks for confirming.

tehpsyc said:
Just replaced the Sense Mms app with the stock one using this technique and it worked perfectly. Only thing I did differently was rather than deleting the stock files I just renamed them with a *.bak for easy restoring in case I ever need to.
Also I'm using Netarchy's kernel [FPS fix] and I did not need to do all the steps with the default.prop, I was able to mount the system folder with write permission.
And in case anyone is like me and just wants to replace the messaging app rather than all of them, I'll attach the apk for much quicker downloading. Its the apk straight out of the BuglessBeast ROM.
Click to expand...
Click to collapse
What is the sense messenger app called? I can't find anything resembling it.
Here's a list of my HTC programs.
Code:
# ls /system/app/*htc*
/system/app/com.htc.MusicWidget.apk
/system/app/com.htc.NewsReaderWidget.apk
/system/app/com.htc.TwitterWidget.apk
/system/app/com.htc.WeatherWidget.apk
/system/app/htcbookmarkwidget.apk
/system/app/htccalendarwidgets.apk
/system/app/htccontactwidgets.apk
/system/app/htcmailwidgets.apk
/system/app/htcmsgwidgets.apk
/system/app/htcsearchwidgets.apk
/system/app/htcsettingwidgets.apk
I see the htc messenger widget but do I have to get rid of that? I don't think that's the messenger application file.

initial said:
What is the sense messenger app called? I can't find anything resembling it.
Here's a list of my HTC programs.
Code:
# ls /system/app/*htc*
/system/app/com.htc.MusicWidget.apk
/system/app/com.htc.NewsReaderWidget.apk
/system/app/com.htc.TwitterWidget.apk
/system/app/com.htc.WeatherWidget.apk
/system/app/htcbookmarkwidget.apk
/system/app/htccalendarwidgets.apk
/system/app/htccontactwidgets.apk
/system/app/htcmailwidgets.apk
/system/app/htcmsgwidgets.apk
/system/app/htcsearchwidgets.apk
/system/app/htcsettingwidgets.apk
I see the htc messenger widget but do I have to get rid of that? I don't think that's the messenger application file.
Click to expand...
Click to collapse
The Sense Messenger app is called Mms.apk. Delete the Mms.apk and Mms.odex files. It's in the OP
Do not delete htcmessengeruploader.

kpoz said:
The Sense Messenger app is called Mms.apk. Delete the Mms.apk and Mms.odex files. It's in the OP
Do not delete htcmessengeruploader.
Click to expand...
Click to collapse
Oh didn't realize it was the same. I'm using DamageControl's ROM and assumed HTC had a different label for some reason. Thanks for clearing that up.
In any case, I got a few FCs here and there and MMS is failing to send on the DC ROM. I'll tinker with it some more and see if I can figure something out.
btw, if anyone is doing this on DC's ROMs then don't bother looking for any *.odex files since his rom is de'odexed.

initial said:
Oh didn't realize it was the same. I'm using DamageControl's ROM and assumed HTC had a different label for some reason. Thanks for clearing that up.
In any case, I got a few FCs here and there and MMS is failing to send on the DC ROM. I'll tinker with it some more and see if I can figure something out.
btw, if anyone is doing this on DC's ROMs then don't bother looking for any *.odex files since his rom is de'odexed.
Click to expand...
Click to collapse
Originally, Kiraly and I tried pushing these files and then using a shell to install them, but it resulting in a ton of force closes. We couldn't open any of the apps.
Regrettably, I'm not savvy enough to attempt to fix this issue for you if you are running a ROM like DC, especially a deodexed ROM. Best of luck to you.
Maybe the install command will work for you where it failed for me.
Try the following:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
exit
adb push :\Users\YourUserName\Browser.apk /sdcard
adb shell
install /sdcard/Browser.apk /system/app
exit
adb reboot

[Q] Nexus S voice/sound recorder hidden and not installed?

Hi,i was searching for the stock voice recorder in Ice Cream Sandwich,but i did not find it...
So I've searched into phone memory (root /system/app) and i found Soundrecorde.apk ,bu if i try to install it,installation aborts saying "This application cannot be installed".
Why?

No one use voice recording on Ics?
Neo on Nexus S with Tapatalk®

bump?.......

.:Crack:. said:
bump?.......
Click to expand...
Click to collapse
???
Neo on Nexus S with Tapatalk®

..

Election Day said:
It indeed doesn't seem to work. Just like Tag.apk, SoundRecorder.apk does not show up in the app drawer, even if it's in /system/app. Apparently it just isn't compatible.
What about some Market apps?
Click to expand...
Click to collapse
There is not much compatibility for this kind of apps and Ics...
Stock Sound recorder was perfect for me on Gingerbread,i don't understand why it's not compatible anymore...
Neo on Nexus S with Tapatalk®

not sure how you tried to install but you cant install system apps like other apk you have to sign it first....anyways i signed it and installed fine but dont give an option to open after install and still don't see it
edit
just for future reference if you edit an apk or want to install a system app like a normal apk
download Sighnapktic from the market its free and it does it right from your phone really easy to use
https://market.android.com/details?id=com.stericson.signapktic&hl=en

i used Sanity with gingerbread, but I don't know if it still works with ICS
https://market.android.com/details?..._result#?t=W251bGwsMSwxLDEsImNyaS5zYW5pdHkiXQ..

Election Day said:
It indeed doesn't seem to work. Just like Tag.apk, SoundRecorder.apk does not show up in the app drawer, even if it's in /system/app. Apparently it just isn't compatible.
What about some Market apps?
Click to expand...
Click to collapse
Both of those apps don't show in the drawer because the "LAUNCHER" intent lines in their respective AndroidManifest.xmls are not present/were omitted that instruct the app to be visible in the drawer.
To the best of my recollection, SoundRecorder never officially included the lines because it was supposed to be present solely as a function for other apps to use, despite it having an actual interface. Tag, on the other hand, appears to have had those lines removed in the transition to ICS. Adding the intents in their manifests will cause them to show up in the drawer again.

XK72 said:
Both of those apps don't show in the drawer because the "LAUNCHER" intent lines in their respective AndroidManifest.xmls are not present/were omitted that instruct the app to be visible in the drawer.
To the best of my recollection, SoundRecorder never officially included the lines because it was supposed to be present solely as a function for other apps to use, despite it having an actual interface. Tag, on the other hand, appears to have had those lines removed in the transition to ICS. Adding the intents in their manifests will cause them to show up in the drawer again.
Click to expand...
Click to collapse
Once added,will the app works with its interface?
Neo on Nexus S with Tapatalk®

..

(THE REAL) Neo said:
Once added,will the app works with its interface?
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Correct.
Election Day said:
Probably yes. I'm trying to modify the xml's at the moment, but I can't get any usable output.
If I can get it to work I'll post the modded apk here.
Click to expand...
Click to collapse
Directly after this line:
Code:
<action android:name="android.intent.action.MAIN" />
Add:
Code:
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.LAUNCHER" />

..

You also just can use anycut from market and create a homescreen shortcut to soundrecorder.apk

Election Day said:
I guess this should be it. I unpacked the apk with apktool, added the lines, packed it again, unzipped it, added META-INF and rezipped it.
You can flash it with "adb push SoundRecorder.zip /system/app".
Click to expand...
Click to collapse
No changes here...i've copied the file in sistem/app,but nothing changes.
Neo on Nexus S with Tapatalk®

(THE REAL) Neo said:
No changes here...i've copied the file in sistem/app,but nothing changes.
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.

XK72 said:
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
Click to expand...
Click to collapse
Tried this and it didn't worked for me. I get this error from adb:
failed to copy 'SoundRecorder.apk' to 'system/app/SoundRecorder.apk': Permission denied

XK72 said:
I haven't looked at the attached APK yet, but try these steps:
I'm not sure if it's because the instructions have you install a ZIP file that doesn't exist (because the attachment is an APK).
The command should be: adb push SoundRecorder.apk system/app
If you happened to have changed the command to APK anyway, make sure that you specify the right path for the file
(e.g. adb push path/to/downloaded/file/SoundRecorder.apk system/app) or that you are in the same directory as the file (then use the command listed above).
If the file got pushed successfully, you may need to reboot your phone for the changes to take effect.
Try that out and if you're still not having any luck, let me know what ADB tells you. If it helps, I'll build a version with the Launcher icon visible that'll work.
Click to expand...
Click to collapse
I've not used adb,but manually copied the .apk to system/app after renaming of original file.
Obviously i've used EsGestore File,with root permissions/root mounted read and write.
File copied perfectly,rebooted phone.
But nothing happens...
Neo on Nexus S with Tapatalk®

jitzbox said:
Tried this and it didn't worked for me. I get this error from adb:
failed to copy 'SoundRecorder.apk' to 'system/app/SoundRecorder.apk': Permission denied
Click to expand...
Click to collapse
This may not be the most efficient way of doing this, but it always works for me. Assuming that you have root permissions on the phone, try the following steps:
Access the phone through ADB:
Code:
adb shell
Mount the volume as writable:
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Remove the existing SoundRecorder.apk file:
Code:
rm system/app/SoundRecorder.apk
Exit ADB:
Code:
exit
Copy the APK file (attached below) from your system to your phone, replacing path/to/file with the location of your file (e.g. c:\android) as detailed in previous post.
Code:
adb push [I]path/to/file/[/I]SoundRecorder.apk system/app
Reboot phone (might be optional):
Code:
adb reboot
(THE REAL) Neo said:
I've not used adb,but manually copied the .apk to system/app after renaming of original file.
Obviously i've used EsGestore File,with root permissions/root mounted read and write.
File copied perfectly,rebooted phone.
But nothing happens...
Neo on Nexus S with Tapatalk®
Click to expand...
Click to collapse
I'm sorry, I'm not familiar with using third-party apps for file management duties. Assuming that everything else you're doing is correct, try using the APK file attached below.

XK72 said:
This may not be the most efficient way of doing this, but it always works for me. Assuming that you have root permissions on the phone, try the following steps:
Access the phone through ADB:
Code:
adb shell
Mount the volume as writable:
Code:
mount -o remount,rw /dev/block/mtdblock4 /system
Remove the existing SoundRecorder.apk file:
Code:
rm system/app/SoundRecorder.apk
Exit ADB:
Code:
exit
Copy the APK file (attached below) from your system to your phone, replacing path/to/file with the location of your file (e.g. c:\android) as detailed in previous post.
Code:
adb push [I]path/to/file/[/I]SoundRecorder.apk system/app
Reboot phone (might be optional):
Code:
adb reboot
I'm sorry, I'm not familiar with using third-party apps for file management duties. Assuming that everything else you're doing is correct, try using the APK file attached below.
Click to expand...
Click to collapse
Using this apk,the phone shows me an app called "Recorder" in the app drawer,but i can't tap it,and all the icons showed in the same page of the app drawer.If i change page,icons of other pages are selectable...weird thing...
Now i'm rolled back to previous apk file and everything works...so scary...
Neo on Nexus S with Tapatalk®

[DIY-TUT/HOW-TO] Debloat and Save Battery

Note: This is not a ready made script that will do things for you. If you are looking for a script/tool to debloat your phone head here. This is a very basic guide, many of you might be aware how to do it already. This is for the absolute newbies like me who like learn by doing it themselves. So lets start!
First, What is Debloat? What are the benefits?
Ans: A new device (except the nexus family) always comes pre-loaded with a lot of manufacturer apps. Most of the times these apps are utterly useless to the end-user considering that there are better alternatives available on the play store. Such apps constitute the phone bloatware. Often these apps are part of the system partition on your phone ie they are system apps and cannot be uninstalled or removed like normal apps. The process of removing these apps is called as debloating!. Savvy?
Fine, Moving ahead. Whats more problematic about these apps is that many of these apps load at system start-up and keep running in the background using precious cpu and other resources apart from eating up memory. This often leads to poor performance and battery life. So once you get rid of these apps you will start experiencing better performance AND AN AWESOME BATTERY LIFE(personal experience)
Wow, I want to get rid of those stubborn apps...show me how to do it.
Sure
PRE-REQUISITES:
1. You should be rooted
2. Your phone should have the ClockWorkMod (CWM) Recovery installed.
3. You should have adb up and running
4. Turn on usb debugging.
{
"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"
}
OPTIONAL:
1. You may want to create a Nandroid Backup through CWM before doing any of the steps listed below.
2. Install abdb insecure by chainfire to run adb commands as root(insecure boot image). This will allow you to boot in to recovery through adb. Once installed the app should look like this
The PROCESS:
1. Ensure that the pre-requisites are met.
2. Connect the phone to the computer through the USB cable
3. To check whether you have properly installed adb do this
Open a command prompt window (start>run>cmd) and type this
Code:
adb devices
If adb is set up and running it should list your device in the list of attached devices some thing like this
Code:
List of devices attached
42801c7449ff097 device
4. Now use the following command to make a backup copy of all the system apps on your phone
Code:
adb pull /system/apps C:\* destination of your choice *
This will ensure that you can install back any app that you remove using this process and also it serves as a reference to the list of system apps. Look at the apps and make a list of apps that you want to get rid off. This (thanx to winwiz for compiling it)might help you to decide which one's are important and which are not, which one's can safely be gotten rid of and which should not be touched. Play carefully. Here is a list of apps that I have safely removed with great benefits to boot-up time, battery and overall performance.
Dlna.apk
Dlna.odex
BuddiesNow.apk
BuddiesNow.odex
Days.apk
Days.odex
Email.apk
Email.odex
EmailWidget.apk
EmailWidget.odex
GameHub.apk
KiesAir.apk
kieswifi.apk
kieswifi.odex
Kobo.apk
MusicHub_N1.apk
MusicHub_U1.apk
PressReader.apk
ReadersHub.apk
ReadersHub.odex
SamsungApps.apk
SamsungAppsUNA3.apk
SamsungIM.apk
SamsungWidget_News.apk
SamsungWidget_News.odex
SamsungWidget_StockClock.apk
SamsungWidget_StockClock.odex
SevenEngine.apk
SnsAccountFb.apk
SnsAccountFb.odex
SnsAccountLi.odex
SnsAccountTw.odex
SnsAccountLi.apk
SnsAccountTw.apk
SnsDisclaimer.apk
SnsDisclaimer.odex
SnsImageCache.apk
SnsImageCache.odex
SnsProvider.apk
SnsProvider.odex
SocialHub.apk
SocialHub.odex
Zinio.apk
Click to expand...
Click to collapse
You may want to add/remove apps to/from this list.
5. Moving on, Once you have decided the apps to remove reboot into CWM recovery. Use this command to do that through adb.
Code:
adb reboot recovery
Note: You must have an insecure boot image for this to work (See point number 2 in optional points)
else
use any of the common methods to boot into recovery. Use key presses or CWM Manager or do whatever, just get in to that ******g recovery.
6. Next, Once you are into the recovery type this command in the command prompt
Code:
adb shell
This will get you into the linux shell on your android device so that you can use all the linux shell commands like in a regular linux shell
7. You must now see a # or $ at the prompt (doesn't make a difference) indicating that now you are into the linux shell. Type the following command in the prompt.
Code:
mount /system
This will load the system partition into memory so that you can play around with its contents.
8. Now to the most important step. Removing the apps. Use the following command in the prompt
Code:
rm /system/app/****.apk
or
Code:
rm /system/app/****.odex
Replace **** with the name of the apk or odex file that you want to remove.
Repeat the command for all the files that you want to get rid off.
Note: Remember to press enter after each command
9. Once you have finished removing all the bloatware just type
Code:
exit
in the prompt. Thats it.
Reboot! (You may use
Code:
adb reboot
for that purpose).
You will now be greeted with a faster performing, responsive, battery conserving and most importantly a bloatware free phone.:good:
10. Thank me if this helped and don't hesitate to ask questions.
As a supplementary note I would like to recommend this app [Requires Root]. Once installed use its corpse finder feature to eliminate all the left over files belonging to the bloatware apps that we just removed. It is as easy as Search and Clean. This will free up more space in your system partition.
Troubleshooting:
Q. I removed Kies Air using the method above but it is still present in the app drawer. What to do?
Ans: This happens if you have updated Kies Air through the play store.
Go to Settings>Applications>Manage Applications
Scroll down to Kies Air --> Select it ---> Uninstall updates
Reboot!. Thats it. Kies Air is gone for good.
A Very Important Note:
I haven't tried it on a Non-Rooted phone. But I think it should work as far as you have adb working and can boot into the recovery(Stock recovery in case of Non- Rooted phones) by some means you are good to go from step number 6.. Have a list of apps to be removed before hand, speeds up the process.
Battery Saving Tips:
Coming Soon.....!

RESERVED!!

Buddy we are already having automated tool for removing bloats ...

mj.vikram said:
Buddy we are already having automated tool for removing bloats ...
Click to expand...
Click to collapse
I'm aware of that buddy. I have even mentioned it in my post.:good: As I said this method is for people who would like to understand whats happening behind the scenes...rather than just flashing a script package.

The-Droidster said:
I'm aware of that buddy. I have even mentioned it in my post.:good: As I said this method is for people who would like to understand whats happening behind the scenes...rather than just flashing a script package.
Click to expand...
Click to collapse
Thanks for taking time and writing this :good:....
Nice guide and just one more alternative for user's if you feel this is difficult process for you, using Root explorer or similar app's got to /system/apps/ and delete the required file's (as mentioned by The-Droidster in the above) and restart the mobile...

What if I just go to my system folder through a root explorer and delete these files in /system/app and then reboot my phone? And then use that corpse finder?
ICS = I SEE ASS Lol
++##» GALAXY R «##++

gitanshu said:
What if I just go to my system folder through a root explorer and delete these files in /system/app and then reboot my phone? And then use that corpse finder?
Click to expand...
Click to collapse
its same buddy, both are same but this for the people who want to learn how to use ADB they can use this because this very well explained :good: ....

gitanshu said:
What if I just go to my system folder through a root explorer and delete these files in /system/app and then reboot my phone? And then use that corpse finder?
ICS = I SEE ASS Lol
++##» GALAXY R «##++
Click to expand...
Click to collapse
I don't see any problem in doing that....but you may experience force closes if you do this when the system is online because the apps that you are removing are still running in the background. So it is better if you do it by mounting the system through recovery.

if uu have rooted phone than u can remove bloat using titanium backup or rom toolbox pro

+1 for using Adbd insecure. It's a great debugging tool on stock roms.
Sent from my GT-I9103

Adam77Root said:
+1 for using Adbd insecure. It's a great debugging tool on stock roms.
Sent from my GT-I9103
Click to expand...
Click to collapse
Yeah its like unleashing a new side of adb. Makes it all the more valuable

[TOOL][GUIDE] BareNox - Modded Nox Android Emulator

Hello Friends~!
Today I bring to you the Latest version of Nox, made portable, with a Cleaner Script to remove all the junk on your Main Machine as well as for Clones
DOWNLOAD BARENOX:
BareNox.zip (200M)
If you would rather build your own, I will now provide a written guide for how BareNox was built.
"BareNox" went through a lot of testing and a script was made to automate much of what is written below
Spoiler: WRITTEN GUIDE
Made using the latest version of Nox, which can be downloaded off the right side of this page:
System Requirements of Nox App Player – NoxPlayer
Open Nox's Multi Drive Manager and select "Add Emulator" and "Android 9" or whatever you prefer
{
"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"
}
When it is done building the machine you need to click on settings and enable root.
Spoiler: HOW TO CLEAN THE PREINSTALLED MACHINE WITH AN APP (NOT RECOMMENDED)
This method is advised against, due to the amount of time it takes to physically remove each directory within the gui, when we could remove all of these directories with a simple script. The knowledge will still be provided to show what the adb method is doing for us.
Open Nox and install a launcher app like nova, and a root explorer by selecting the apk button on the right side panel.
Spoiler: PIC
If you need the apps:
Nova
nova.apk
drive.google.com
Root Explorer
RootExplorer.apk
drive.google.com
Now open Nox's settings by clicking on the gear icon at the top right.
We need to go into General, and then put a check on root.
Spoiler: PIC
Next click on the Gaming tab and enable high fps and rendering cache. This is to allow you to be able to play higher end mobile games
Spoiler: PIC
Save settings and restart the machine
Select Nova as the Launcher app always
Spoiler: PIC
Open root explorer. Grant Superuser access forever
Delete all the items highlighted in the pictures below and close the machine.
Spoiler: PIC
Spoiler: HOW TO CLEAN THE PREINSTALLED MACHINE WITH ADB (RECOMMENDED)
This comment explains it
Spoiler: HOW TO USE THE SCRIPT AND NOVA ON ANY VERSION OF NOX
Make a new machine and enable root in settings
Make a text file and call it run.bat
Paste in this code.
Code:
adb root
adb shell rm -r /system/app/AmazeFileManager
adb shell rm -r /system/app/AppStore
adb shell rm -r /system/app/BuiltInPrintService
adb shell rm -r /system/app/CarrierDefaultApp
adb shell rm -r /system/app/CompanionDeviceManager
adb shell rm -r /system/app/CtsShimPrebuilt
adb shell rm -r /system/app/EasterEgg
adb shell rm -r /system/app/Facebook
adb shell rm -r /system/app/Helper
adb shell rm -r /system/app/LiveWallpapersPicker
adb shell rm -r /system/app/PrintRecommendationService
adb shell rm -r /system/app/PrintSpooler
adb shell rm -r /system/app/Traceur
adb shell rm -r /system/app/WallpaperBackup
adb shell rm -r /system/app/newAppNameEn
adb install nova.apk
adb reboot
Paste run.bat into the bin folder of Nox
Paste nova.apk (10M) into the bin folder of Nox
Now Run run.bat
Spoiler: VERIFIED WORKING GAMES
If there is a game you want me to test, leave a comment below.
Spoiler: BEAT PARTY
at the end of the video
Spoiler: DIABLO IMMORTAL
at the end of the video. guide is outdated
Spoiler: EPISODE STORY APP
Spoiler: MKX ONLINE
There's more that can be finessed here, have fun!
VT-Error fix
For rooted WSA (Android 12 or 13) see this guide
How To Build and Root Your Desired Flavor of WSA and install the Playstore Using LSPosed & Magisk. Plus a Premade
Hello Friends, Today I wanted to write a guide about how to use the LSPosed Github Repo on a linux machine to build your desired flavor of WSA with GAPPS and Root. If you do not already have a Linux machine or WSL, I have a fully built and...
forum.xda-developers.com

Works pretty well for me, except for trying open the multiple instances. I've wiped things clean a couple times and even tried on my other pc. Luckily the app I was trying to install had an x86 version so it'll do for now. I'll have to look into it when I have a bit more time.
Thanks for the post!

Twistt said:
Works pretty well for me, except for trying open the multiple instances. I've wiped things clean a couple times and even tried on my other pc. Luckily the app I was trying to install had an x86 version so it'll do for now. I'll have to look into it when I have a bit more time.
Thanks for the post!
Click to expand...
Click to collapse
Thank you for testing it!
Note that this issue has now been corrected

-

--

--

NotNox has had a Proper Update and is now at V2 "BareNox"
Includes the cleaning script commented on earlier.
Spoiler: HOW TO USE BARENOX
UPDATED 08/04/2022
BareNox.zip
drive.google.com
(196.2 MB ZIPPED)
Open BareNox and then bin, run MultiplayerManager.exe and add new emulator of choice
The first time you make a machine, nox will have to dl the "base" of the android version you selected from nox's servers. You only have to do this the first time you try to create an android 9 or 7 machine. You will then be able to create clones quickly as the BareNox folder will now contain the base disk and data folder.
Make sure to click on the gear icon and enable Root in system settings before running the machine
Run the remove.bat script when this lady appears on your new machine (this is when you have full read write access)
This will go through and remove the crap apps and install nova launcher for us
Spoiler: HOW TO CLEAN THE PREINSTALLED MACHINE (OR CLONES) WITH ADB
Spoiler: WRITTEN GUIDE
Go into the Binary folder of Nox or Not Nox and add a new text file called remove, paste NOVA.APK into this folder as well
Paste the contents of the script into the remove file
change the file extension from txt to .bat by renaming the file
add a new emulator and wait for it to make it to this screen, you need to hit Login later in order to get full Root, otherwise our batch will fail.
Run the remove.bat file after hitting Login Later and waiting for the garena lady to appear
this is what will be shown as the batch runs, don't do anything the machine will reset itself
select nova always and you're all set!
Spoiler: THE SCRIPT AND NOVA DL LINK
Spoiler: FILE EXPLORER OPTIONS PREREQ
View attachment 5669749
You need to have hide extensions for known file types unchecked, in order to be able to change a file from text to batch
nova.apk
drive.google.com
adb shell rm -r /system/app/AmazeFileManager
adb shell rm -r /system/app/AppStore
adb shell rm -r /system/app/BuiltInPrintService
adb shell rm -r /system/app/CarrierDefaultApp
adb shell rm -r /system/app/CompanionDeviceManager
adb shell rm -r /system/app/CtsShimPrebuilt
adb shell rm -r /system/app/EasterEgg
adb shell rm -r /system/app/Facebook
adb shell rm -r /system/app/Helper
adb shell rm -r /system/app/LiveWallpapersPicker
adb shell rm -r /system/app/PrintRecommendationService
adb shell rm -r /system/app/PrintSpooler
adb shell rm -r /system/app/Traceur
adb shell rm -r /system/app/WallpaperBackup
adb shell rm -r /system/app/newAppNameEn
adb install nova.apk
adb reboot
Spoiler: HOW THE NOX ADB SCRIPT WAS MADE
Hello Friends! I have created a guide on how to make your own Script to clean up your Nox machines (pre-installed and clones)~! Please note there is much much more that you can do here, this is just to teach you the basics to help you come up with interesting ideas!!
This video is Nerd Knowledge, and unneeded for folks that just want to quickly clean up their clones. Check out the next comment for the quick cleaning method
"BareNox" has this batch file pre-installed for your convenience

jenneh said:
NotNox has had a Proper Update and is now at V2 "BareNox"
BareNox.zip
drive.google.com
100 mb zipped!
Includes the cleaning script commented on earlier. Watch the video to see how to use it.
Note that:
THIS IS NOT A PREINSTALLED MACHINE, like "NotNox".
You will have to use multiplayermanager and add a new emulator with your choice of android version.
The first time you make a machine, nox will have to dl the "base" of the android version you selected from nox's servers. You only have to do this the first time you try to create an android 9 or 7 machine. You will then be able to create clones quickly as the BareNox folder will now contain the base disk and data folder.
Run the remove.bat script when this lady appears on your new machine (this is when you have full read write access)
This will go through and remove the crap apps and install nova launcher for us
View attachment 5669963
Click to expand...
Click to collapse
i got this error

HoangNK said:
i got this error
Click to expand...
Click to collapse
edit I am working on a fix
This issue has now been fixed

@HoangNK I apologize, I didn't mean to dismiss your VT error, I sincerely thought it was due to that mode not being enabled on the user end.
I now realize, after reinstalling windows on my laptop which has vt enabled, that I did indeed create this error. I didn't realize it at the time due to sharding, as I had nox installed in the main directory as well as the portable, so I didn't notice the problem.
I have rebuilt and verified BareNox, here's the new dl link:
BareNox.zip
drive.google.com
(196.2 mb ZIPPED)

For anyone Still experiencing the "VT Error" check your Windows Features settings. I unintentionally caused this error to myself while playing with WSL. Open up windows Features and uncheck these options, then reset
Spoiler: show

Something to consider about Emulators, they can be used to program virtual machines that have windows preinstalled faster usually than on your android device. Then you could pull your machine from the emulator and port over to any android device. I'm working on a detailed guide but it will take some time as I work to make the virtual machine's parameters more feasable for work use, i.e. a 10gb max hdd is not gonna suffice~!
To Do List: get win 10 working
Proof of Windows 7 Working in Nox:
How To Guide:
How To Install Windows Or Linux ISOs on your Android Devices - Windows 10 Nox Lab + Working Arm Distros for your phone using Termux
Update: A new thread is created to house "premade" linux distros. The first premade environment is an Ubuntu distro, installed using proot-distro in termux, Takes only a few minutes to restore the backup, else instructions are provided to build...
forum.xda-developers.com

A note to anyone checking this out from this date forward, Nox has had an update since I wrote the script. So when barenox downloads the android image from nox's server, they are different than before. Meaning that Even though one selects ROOT on startup, the ADB will not recognize the READ WRITE status thus rendering the .REMOVE.bat script useless for the time being. The adb root command does not help, I didn't bother to su into the shell bc the time factor, I could just delete in root explorer
A TLDR use the manual removal method with root explorer and manually install nova as the original thread shows how to do if you want to remove the crapware.
I'm not going to update the script, instead I am going to stop being lazy and just make my own emulators in android studio and share some builds in another thread. I'll leave a comment below whenever that happens.

Listen Linda.
I found an Amazing OS that I am trying to work out a few kinks for. It runs in vmware, has root, can play the games, has a traditional desktop feel, can run multiple apps in separate windows.
It's called prime os! I am not a creator. Just a testing a producto~!
I will make a new thread with prebuilt images of this and like 5 other prebuilt android x86_64/ chrome os forked os's that I played with this week. Putting out the word about prime in case anyone has any ideas how to get openvmtools or vmware tools to work on here. I am trying to build a stack in termux to accomplish this myself, key word trying. Maybe someone knows how.
other os's tested and built -- may add more if I find them
google chrome os - cloudready version
bliss os
android x86_64 9.0
flint os
fyde os

Spoiler: notes
as an Edit ---I am well aware that the tools are not "officially supported" so lets make them work anyway ok
This is 12 years old but still relevant
'As an update, I was able to locate the vmware tools iso for pre glibc linux distros (like our android vms) It comes with vmware workstation 17
had to pkg install tsu then run this command and am a step closer
I went through and pointed the script to the requested binary's location /system/bin/more and the others all for the most part in bin with depmod being in xbin. the program seemed to have an error at the end. going to take all the requested binaries out from system now and add them to the vmtools folder
using root explorer can copy the binaries from bin into the vmtools folder

So here's my notes on getting vmware tools to work in the android emulator.
In vmware tools on your windows pc there are isos that contain the tools.
Inside the iso is a file like this. extract it and extract the file it makes
So here is what I did, You can see the tools have an etc folder and a bin folder. and in pictures in the notes comment above, we know that the tools need certain binaries to run, or access to.
It is not just enough to point the tools to the /system/bin/binaryname because the stock binaries aren't executable.
So I obtained all the binaries the code calls for and put them into the bin folder of the tools.
I also built the missing directories such as /var/log
i changed the name of install-vmwaretools.pl to run.pl and added mkdir codes for the needed folders
Now running perl run.pl gives this interesting error
Anyone have any ideas?
It also really Did create that many folders, haha

hey there.. is there still possible to use your script to use older version of noxplayer and make that work? i get it that no more noxplayer updates will be compatible. but, that is just perfect for me.
i used noxplayer every day since 2016 and run 12 instances. it was and still is Ver. 3.8.3.1
but google as of last month has now removed games that is no longer supported by the google play.. so no more game updates for me. so i have no other choice to upgrade too.. i had off course followed guides and hacked it.. so no adds what so ever.. so hoping that you can still your very useful software to get rid of ads and malwares that they usually bring to free version.
thank you

@noxlar2 anything is possible, however i would need a copy of the version you want to fix to be able to advise better. as far as the current version i will for sure look at fixing the script for it tomorrow. kinda got super carried away on other projects and should take the time

@jenneh
wow.. fast reply back. well, just buildt me a new pc.. so, it will be with a fresh win11 and fresh noxplayer.. so i have no idea what version i must choose.. i will have my old pc system untouched in case of fall back on nox.p.. reason i always used the version i did was because of superior stability vs recent (back then + few years forwards)
also i did test latest free version on my minipc.. and it worked great as well. but, i have not done extensive testing so i don't know.

@noxlar2 Hey Congratulations on your new PC! That's always an amazing feeling. Thank you for clarifying which version. I was able to successfully get the script working again on the Latest nox and Lol it was silly, all the script needed was "adb root" added to the top.
i had to do the VT-Error fix bc of playing with WSA
got the original barenox updated -- link in the op and HERE Just remember to select root in settings before running the machine or the script wont work