Database Info

[APP] VM Heap Tool 2.4.1 [28/02/12]

Description
I wrote a small application to allow easily changing the VM heap size (no more adb pull, edit, adb push). People on CM ROMs may be familiar with a similar option, but here is a little tool for those who are not running CM. As it modifies a variable which can affect the stability of the system, be careful with how you use it More about the VM heap size is written in the application itself. And of course, if I made any mistakes or if something is incorrect please correct me.
Requirements
root
system write
busybox (1.17.x recommended)
Appearing In
Japanese Jellyfish (ZTE Blade/Orange San Francisco)
If you wish to bundle this application in your firmware feel free to, but let me know if you do and please link back to this page
Download (Android Market):
{
"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"
}
Translating VM Heap Tool
English files which can be translated have been attached (txt files), and the following fields which I will mention do not need to be translated. Once you translate something you may just attach the files in your post or add them in code tags. Of course please mention the language that you translated it to so I can appropriately add it to the application and update.
Do not translate: heapSizeUnit, aboutHeap, defaultHeap, currentHeap, version, thread, heapSizeValues. These just hold key values which should not be translated. Also please don't translate "RPLACE" inside the texts, as this is replaced inside the application on run-time.
Values are stored as
Code:
<string name="aboutHeapTitle">What is the heap?</string>
where the string's name is clearly defined, "aboutHeapTitle", and the value which should be translated is inside the <> and </> tags. Values which are used in similar situations will have a common prefix, for example:
"progress..." - used on a progress dialog to display the message
"toast..." - the little grey messages that you get at the bottom of your screen and with which you can't interact
"dialog..." - used as the title on a dialog box
and so on...
Thank you to all those who are willing to help, your contributions will be noted

great app, wont have to manually erstart on droid inc. wont restart when pushing the button.

ACD168 said:
great app, wont have to manually erstart on droid inc. wont restart when pushing the button.
Click to expand...
Click to collapse
Thanks, so the Incredible has the same problem as the Desire then... If you install ROM Manager it will restart. I'm afraid that has something to do with superuser and how the phone is rooted (correct me if I'm wrong), so some devices will restart while others will not. Sadly Google doesn't allow applications to restart the device, so it has to be done in a roundabout way which may not always work...

Awesome, now everyone can break apps by lowering the heap below the expected 24 megs!

khaytsus said:
Awesome, now everyone can break apps by lowering the heap below the expected 24 megs!
Click to expand...
Click to collapse
Yes, but I hope that most people will be smarter and try to use something like 32

The "apply" and "quit" box cover the "new heap size" box on hTC Hero

skymera said:
The "apply" and "quit" box cover the "new heap size" box on hTC Hero
Click to expand...
Click to collapse
OK, thanks for letting me know. I'll see what I can do about it, but for now you can use your trackpad (or w/e it's called) to move the focus on the button and press it.

skymera said:
The "apply" and "quit" box cover the "new heap size" box on hTC Hero
Click to expand...
Click to collapse
Should be fixed now with version 1.1, as well as support for Android 1.6 and above. Apologies that it took so long.
Icon help, anyone...?

Very nicely done!!!
Thanx!!!

The app is force closing on startup on a rooted orange San Francisco (ZTE-Blade) with stock rom.
Andy.

g1dtf said:
The app is force closing on startup on a rooted orange San Francisco (ZTE-Blade) with stock rom.
Andy.
Click to expand...
Click to collapse
Do any other rooted apps crash, such as Root Explorer, ROM Manager, etc?

Rom Manager and System App Remover both run ok, not got Root Explorer so can't try that.
Andy.

martino2k6 said:
Do any other rooted apps crash, such as Root Explorer, ROM Manager, etc?
Click to expand...
Click to collapse
Forced close for me to on ZTE-Blade Stock/Root.

What happens if you write the following two commands in a terminal emulator or adb?
Code:
ls /system/bin/su
ls /system/xbin/su

If you have rooted the san fran with stock rom and this will not work, root again. Worked for me no probs, even if it says you are rooted. Just root again. It appears that when the San Fran is turned off then on, it unroots (with original rom" Well, that is what I have found after testing. I have stock rom rooted and have picked out all the Orange "tat"
Hope that helps.

System Write Required
Just tried running the app, but ran into an error: "System write required". I have root, adb is installed and recognize Android is read only by default, so I assume that I have to change permissions to include write?

Guilden_NL said:
Just tried running the app, but ran into an error: "System write required". I have root, adb is installed and recognize Android is read only by default, so I assume that I have to change permissions to include write?
Click to expand...
Click to collapse
You can't change that without using a rooting method which unlocks NAND on your device. The application already remounted the partition to write, but wasn't able to write to it because you most likely don't have NAND unlocked.

martino2k6 said:
You can't change that without using a rooting method which unlocks NAND on your device. The application already remounted the partition to write, but wasn't able to write to it because you most likely don't have NAND unlocked.
Click to expand...
Click to collapse
Well guess us Slide owners can't use this until we have s-off. No system r/w for us yet

No love on the MyTouch 3G getting NAND unlocked for Write. Ah well, the MT3G is truly a dog so I am not going to spend anymore time with it. It'll do the job for now, and I use the Nexus One as my main phone anyway.
Thanks for the tip though! At least I know where the issue is on this device.

kapslock4 said:
If you have rooted the san fran with stock rom and this will not work, root again. Worked for me no probs, even if it says you are rooted. Just root again. It appears that when the San Fran is turned off then on, it unroots (with original rom" Well, that is what I have found after testing. I have stock rom rooted and have picked out all the Orange "tat"
Hope that helps.
Click to expand...
Click to collapse
Didn't work but used clockwork and installed custom ROM and worked
Sent from my BladeVillain using XDA App

PC-Android Root File Manager - Android Commander by PanPiotr [WIN][ROOT][ADB]

Hey xda,
I have found a very cool application for windows users: Android Commander.
Its a File Manager for Windows that lets you browse the root directories of your phone within a nice gui. No more typing lines of adb shell commands!
Download: Visit Website http://androidcommander.com/
Functions:
File Actions
Copy Files
Delete Files
Push Files from PC
Pull Files to PC
Create Directories
Edit File Properties (Permissions, etc)
Select Multiple Files
Sign Files
Read Device Info
Open a ADB Shell console
Read logcat
Virtual Input (havent tried it)
Screenshots (Tested and found buggy on CM9)
Screenshots from the Website:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

It's been around for quite a while. Very useful.

Ah, ok. I didn't kne it and found it useful to have it written down somewhere.
Sent from my GT-I9003 using XDA

I do know Why its always keeps on loading

NO Root Acces
Does anyone can help me, I have no root access over my phone?
When I run Android Commander, the bottom status bar says "Root Access : NO"
I don't understand what went wrong.
I tried to click the status bar, it just keep on loading.

Doesn't even find my HTC Sensation (adb drivers installed+rooted), while both QTADB and Droid Manager are able to access the phone.
So it's a no go for me, too bad, looks promising.

Thank you

@Taraen;
br im a new bie can you send some tutorials on how to use this?

thanks bro, this is realy good app. :highfive: i searched for app like this very long time :good:

link broken? giving up..
downloaded doesent seem to work for me or find my device.

does not show my phone as root ?

viditshah36 said:
does not show my phone as root ?
Click to expand...
Click to collapse
Maybe because you are runing jb mr1 4.2.2

For all those that get "Root Access : NO" on rooted phone, it's because adbd is running in "secure" mode.
Try adbd Insecure v1.30. It worked for me:
http://forum.xda-developers.com/showthread.php?t=1687590

It won't show my device
it says my Galaxy nexus(4.3 +rooted) is offline and that I should reboot it.
done the reboot, nothing changed, tried insecure adb, the same message.
can someone help me.

I need to to modify swap file as im using androidcommander with rooted note 2 4.3
thank u people

works just fine with Chainfires Insecure Mode app and KitKat on my Nexus 5.
You need to overwrite the files that are in $ROOT/Android Commander DIR/bin/ with the ones that are from an up-to-date sdk.
There are 4 files.
Here; I'll make it easier for you all.
Android Commander Update Files for 4.3+ Support

doesn't work with my gt p3110 with 4.2.2 works fine with droid 4.1 and below

Awesome
krylon360 said:
works just fine with Chainfires Insecure Mode app and KitKat on my Nexus 5.
You need to overwrite the files that are in $ROOT/Android Commander DIR/bin/ with the ones that are from an up-to-date sdk.
There are 4 files.
Here; I'll make it easier for you all.
Android Commander Update Files for 4.3+ Support
Click to expand...
Click to collapse
Brother. Yes it does the magic. Its working when the files are replaced by the fresh files.:good::fingers-crossed:
---------- Post added at 10:47 AM ---------- Previous post was at 10:42 AM ----------
lohtse said:
doesn't work with my gt p3110 with 4.2.2 works fine with droid 4.1 and below
Click to expand...
Click to collapse
Above files as mentioned are for 4.3+ but you are on 4.2.2.

First search, first result..just what I needed when I needed it..worked perfectly for me! Big Thanks. :good:

Cannot access data/data
imakulate said:
First search, first result..just what I needed when I needed it..worked perfectly for me! Big Thanks. :good:
Click to expand...
Click to collapse
I am successful in connecting the device , but I can't access the path data/data . When I click on data/ it doesn't displays anything.I require it for development purpose, so has to access the database file of the apps
And one more, can I backup apps along with data like Titanium backup

KitKat issue - Unable to delete stuff on ext SD card

Just got my Sony Xperia Z3. Still messing around to get a feel of the UI.
Was not able to uninstall File Commander as I find the UI badly design. So installed ASTRO File Manager, tried deleting a file from ext SD card. pops up a notice saying that due to KitKat design, 'write' to ext SD card is prohibited.
I uninstalled ASTRO File Manager and installed SOLID Explorer, deletion from ext SD card was not allowed as well.
Tried deleting same file using File Commander and it worked
{
"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"
}
!
Probably will try File Expert but expecting the same rejection.

It is a well known issue with KitKat and is brought in on purpose by google.
Basically in an effort to increase security protection to the user only system apps can write to the SDcard. There is a way around it but you need root. Just google "Write to SD card KitKat" for further information and how to revert it.

gregbradley said:
It is a well known issue with KitKat and is brought in on purpose by google. Basically in an effort to increase security protection to the user only system apps can write to the SDcard.
Click to expand...
Click to collapse
You believe in Santa Claus, too ?
Google tries to force you into using their cloud services, that's all magic.
But it's correct: You need root to edit the file platform.xml. After doing that, everything is ok again.
But DO NOT ROOT, yet ! You'll lose all DRM keys (making the horribly bad Z3 camera even worse) and X-Reality. And believe me: You really do not want to lose that.

Chefproll said:
You believe in Santa Claus, too ?
Click to expand...
Click to collapse
What does this mean?
Google tries to force you into using their cloud services, that's all magic.
Click to expand...
Click to collapse
If you say so
But it's correct: You need root to edit the file platform.xml. After doing that, everything is ok again.
But DO NOT ROOT, yet ! You'll lose all DRM keys (making the horribly bad Z3 camera even worse) and X-Reality. And believe me: You really do not want to lose that.
Click to expand...
Click to collapse
Yes I know, its an old issue and well known how to get around it. And trust me, if I want to unlock my bootloader I will.

The only way around it is to save files in your File Explorer's App folder. With FX Explorer, for example, save your files into Android/data/nextapp.fx/files/
You'll be able to write and delete all you want.
File Commander works across all folders because it's a system apk.

Presumably with root you could just convert your file manager app of choice to a system app with the likes of Titanium and it would then work ok? Or just use one that uses root anyway (like Root Explorer).

Work root you just add one line to platform.xml and then it works just like it did before
Sent from my D6603 using XDA Free mobile app

3Shirts said:
Presumably with root you could just convert your file manager app of choice to a system app with the likes of Titanium and it would then work ok? Or just use one that uses root anyway (like Root Explorer).
Click to expand...
Click to collapse
Of course, with root you can get around any software restriction. However, in 2 - 3 years it'll be moot (hopefully sooner). It's like when Android dropped the menu key and everyone was pissed. After 2 years no one cares about the lack of a menu key anymore.

My First Build!!! Lollipop From Source!! Nww with 5.0.2_r1 and Tethering and F2FS

Hi all,
New Build!!! With Fixed Location Service!!!!
http://d-h.st/Plzo
Could you please test this out, @jiri.bati.novak and @sur1k?
----------------------------------------------------------------------------
Merry Christmas all and to celebrate, here's the new build with Android 5.0.2_r1
Here's a Screenshot:
{
"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"
}
Enjoy the New Year Celebrations!! As before, please let me know if you face any issues.
-----------------------------------------------------------------------------------------------------------------------
As promised, here is the New Tar file containing Android 5.0.1!!
Remember to Backup Data!! This build also adds mounting USB Drives using an OTG cable. (Thanks to Cyanogenmod's work). You can go to Settings > Storage to mount and unmount drives. I'm working on having a notification to enable mounting/unmounting from Notification tray itself. As before, /data is F2FS. The Kernel has been reworked to a better Dithering solution for the display. Tethering support (USB/WiFi/Bluetooth).
Follow the guides below to Flash (Sorry I don't know how to make OTA package yet)
jiri.bati.novak
I will post all the diffs later.
If you like this, please feel free to thank me!
-----------------------------------------------------------------------------------------------------------
I have moved on to AOSP 5.0.1!! I will upload the files later but for now here's a Screenshot:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I've managed to build the system from source. This is a Nexus7 3G build and I do not know whether it will work on the WiFi version. Please note that this is not a ROM and I am a total noob (who does not yet know how to build a ROM).
Please don't hold me responsible if your device goes Kaput. I will look into the issue but I do not have any idea what I'd be doing
Find the Archive here:
This archive has:
boot.img (F2FS supporting kernel with errdiff dither for better colour rendering)
System.img (Has WiFi/USB/Bluetooth Tethering Support)
Userdata.img
radio.img (For Flashing Radio)
openrecovery.img (TWRP to format /data to F2FS)
bootloader.img (If you completely mess up)
fastboot (linux)
adb (linux)
lollipop flash.sh (Must be Run as Root)
Only experienced users! Must use Linux.
Use TWRP to backup your data as it is a destructive process. This is not "ALL-F2FS". Only the /data partition is in F2FS.
1. Untar
2. Reboot into fastboot mode
3. Run "lollipop-flash" as root
4. Once flashing is done it will reboot to fastboot. Boot to recovery and format the /data partition to F2FS
The following steps can be done later after booting for the first time
5. In Recovery mode, Install RIL Fix. Open recovery supports MTP and OTG so you can copy the fileform your PC. Or you can use a OTG cable and a pendrive to flash the file.
6. Reboot Sytem
7. Verify System is usable
8. Install Gapps-Lollipop
9. Wipe cache, format data and change filesystem to F2FS and then wipe /data (Just to be sure)
10 Enjoy.
You can then restore /data from your backup using TWRP
Please note, I am fairly new to ROM building hence the complicated process. I will not be responsible for if your device is bricked. If you like this then suggest what else I should add to this. If you need any help please feel free to Message Me!
Thanks:
@rjwil1086 and @ajbiz11

Nice work.. Are you willing to share the steps you used to build from source?

Can you upload the 5.0.1 images, please? ☺

Couldn't get it to work in Linux Mint so I used Nexus Root Toolkit. Any differences in 5.0.1? Anyway to root?

Post Updated!!!
Hi, Posted my new build! With USB Mass Storage support for USB-OTG!! You can also root with Super-SUv2.37 . I've been doing it and it's working perfectly.

Why the kernel does not support overclock.
Sent from my GT-I9300 using XDA Free mobile app

@slashworkninja great work, man... :good: does the new image contain the ril fix, or do we need to flash it as it was with the 5.0?

It unfortunately doesn't. You need to flash it in recovery.
Sent from my C6902 using XDA Free mobile app

@slashworkninja good job, but the location services are still not working, any progress on that?

jiri.bati.novak said:
@slashworkninja good job, but the location services are still not working, any progress on that?
Click to expand...
Click to collapse
Can you explain what the problem is? I can get a GPS lock on my Nexus 7 and Maps and Navigation are working too.

slashworkninja said:
Can you explain what the problem is? I can get a GPS lock on my Nexus 7 and Maps and Navigation are working too.
Click to expand...
Click to collapse
Well, I did not test the GPS outdoors for the lack of time and according to the GPS status app it should ve working, but the "network location" seems to be offline - for example the chronus widget cannot get the location for the weather forecast, Google maps are "waiting for location", same for the "News & weather" app... I think that there may be some trouble with fused location or Google Play services, but I cannot figure out anything from the logcat output...
Which version of Google Play services package are you using, can you check it?

I believe this is a Play Services bug. Try installing/updating Maps and the other Google apps. Turn on High Accuracy Mode in Location settings. Try clearing the app's cache too from App settings.

slashworkninja said:
I believe this is a Play Services bug. Try installing/updating Maps and the other Google apps. Turn on High Accuracy Mode in Location settings. Try clearing the app's cache too from App settings.
Click to expand...
Click to collapse
I have the same suspicion, but I've tried all the suggested steps with no luck. Still, reinstalling the apps is not the solution, it must be in the play services itself or the fused location service. That is why I was asking for the version of your - apparently working - config...

Can you give me some logs? I'll take a look. Also, can you confirm that 3G data is working?

slashworkninja said:
Can you give me some logs? I'll take a look. Also, can you confirm that 3G data is working?
Click to expand...
Click to collapse
3G Data is working correctly, no problems with mobile data whatsoever. Had the tablet with me today, now I did get the logcat of the google maps starting and clicking on "current location" fab, which displays the last known position the system got from GPS lock. So true, GPS is working correctly, only the "network location" is going haywire.... Google Play Services version 6.5.99 (1642632-434)...

That's surprising as I'm using an older version! I have everything updated too.
Sent from my Nexus 7 using XDA Free mobile app

slashworkninja said:
That's surprising as I'm using an older version! I have everything updated too.
View attachment 3064607
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
Hmmm, I will try downgrading to same version again, which is what I wanted to do anyway... Next on list is the clean-slate reflash...

@slashworkninja So... I have ended reflashing 5.0.1 from the start. Just noticed, that the backup services is set to debug-only cache. Well, there goes my setup, nevermind though... Still no network location, same version of play services as you. Oh well, seems like getting lollipop work properly on tilapia is going to be harder than it seems... If only I had fast machine, I would try to build for myself, but with my setup, I'm looking on three to four days of grinding, not to talk about disk usage...

I'm sorry it happened. But I did take a look at the logcat.
I am fairly new to this but I think this might be the issue:
W/ResourcesManager(21400): Asset path '/system/framework/com.android.media.remotedisplay.jar' does not exist or contains no resources.
W/ResourcesManager(21400): Asset path '/system/framework/com.android.location.provider.jar' does not exist or contains no resources.
Click to expand...
Click to collapse
These files do exist in the locations. So maybe there is a mismatch somewhere.

I checked, and these files do exist, at least after clean reflash...

[Guide] Instant 10%+ Performance Boost!!! Remove Nubia backdoors,loggers,trackers, etc. ROOT OR TWRP REQUIRED

Hello everyone today I bring to the table a constantly updated guide.
In my free time I will add to this guide my many methods of creating a stock os out of Nubias OS whilst retaining nubias gaming suite,lights, etc. I know many feel cheated on antutu scores because Nubia presented 510k and most people couldnt even attain 450k on a RM3S.
Well the ones I have worked on easily hits 515k in the max optimal conditions, whilst hitting 505k-510k in concurrent runs or runs in regular conditions. YES the phone thermal throttles, eventually leaving a reduced score of 450k-470k, HOWEVER that is higher than the current reported average of 435k.
Todays method shall be called Method #1
METHOD #1
REMOVE WOODPECKER- Nubias tracker
Background: it logs information from your phone including sensitive personal app information. This program (binary) runs 24/7 and dumps logs to root and to internal storage. If youre connected to internet data or wifi, it will connect to nubias servers amd start dumping information, I have reproducible evidence through a packet dumper.
This program runs from the moment you first boot your phone till when its broken or out of battery. Unless removed. Yes I know you can opt-out but that is simply a facade, it ALWAYS runs anyway.
Removal- a10-a11
1.Obtain a root file explorer or use twrp to perform the steps below
2. Using your explorer navigate to root and put in the search wood
3.Wait for it to load the files and remove them ALL, delete them, shamwow them.
4. If there are files that arent removable change their permissions to none, these are created by woodpecker on boot and will be gone when done.
5.Repeat 2, 3, and 4 but use Wood (to be clear perform the search with a capital W, it matters for some explorers.)
5. Open your init.rom.rc it is located in the root directory remove the lines that are associated with woodpecker. You can remove freezerd lines as well for less agressive ram management but will require additional steps.
6.Enter your vendor build.prop and change woodpeckers line to false, it is the only line containing the word woodpecker.
7.Reboot and perform a search, you will see no woodpecker files show up.
8.System ram usage will decrease by an average of 200mb, Phone temps idle lower(by a very small amount admittably), network usage will decrease.
For those thinking is this illegal? Unfortunately not, Nubia is operating on the same legal grounds any other company data harvesting is. Feel free to research.
A9- Same as above but woodpeckers permissions must be set to none, then after a reboot it is deletable.
Done.
Method #2
I really recommend reinstalling the game launcher and home launcher as user apps as well, or modifying your preferred launchers code to call nubias recents(attached to nubia launcher)but it will require the nubia launcher installed ideally as a user app not system user 0. This is the current only working method to use a custom launcher with RECENTS on Nubia A11 OS I will update this more indepth when I next log in.
6/01/2021
Method #3 A10-A11 (Android 10 & 11)
Tcpdump has been added as a binary in all RM3 & 3S A11 updates and some A10 it is highly recommended to remove permissions, and delete the bin. It will be located in your system bins. You can also search for it with tcpdump entered in a root explorer.
I will continue to add more in my free time!

Wouldn't removing the woodpecker app do the trick?

Interested on this. However, I'm unable to find init.rom.c even using search. Could you give what's the partition name / folder where it is located?

danishajaz said:
Wouldn't removing the woodpecker app do the trick?
Click to expand...
Click to collapse
Nope, its simply there to fool you, regardless theres a woodpecker in the system bin.

leipnacht said:
Interested on this. However, I'm unable to find init.rom.c even using search. Could you give what's the partition name / folder where it is located?
Click to expand...
Click to collapse
What rom version are you using? If you cant locate the init file that creates it on boot, maybe youre on A9, for A9 removing the file in system bin should be enough from my memory but I dont have an A9 available to test it out right now, you could always look through the inits there arent many, youll find many more things that you may want to change as well. Anyways let me know which rom youre running and ill be glad to debug further

Updated for Tcpdump removal, nubia secretly snuck this binary into their rom, there is absolutely no reason at all they should have a binary capable of sniffing ALL OF YOUR INTERNET TRAFFIC preinstalled.

SilentDevGuy said:
What rom version are you using? If you cant locate the init file that creates it on boot, maybe youre on A9, for A9 removing the file in system bin should be enough from my memory but I dont have an A9 available to test it out right now, you could always look through the inits there arent many, youll find many more things that you may want to change as well. Anyways let me know which rom youre running and ill be glad to debug further
Click to expand...
Click to collapse
This was last March 2021 so it's probably A9.
I'm using the CN ROM and it's on Android 11 now and has root access by Magisk
I can now see the init.rom.c file
What's the name of file explorer you are using?
I tried deleting using FX File Explorer it says can't delete, file is read-only
Also I tried deleting using adb shell and even used su root, can't delete it
{
"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"
}

RED MAGIC 3
ROOTED ANDROID 11 CHINA ROM
USE
MIXPLORER,,APK
GO TO ROOT FOLDER SEARCH TYPE
''WOOD''
GO TO THE LOCATION OPEN FOLDER OR FILE
AND
SLECT FILE PROPERTY
CHANGE PERMISSION
644 rw-r-r
THEN DELETE