Database Develop

Block OTA (Beginners guide?)

adb shell, sqllite, build prop...Any other non-tech major people around here a little lost?
I'm rooted. I don't want the new update. I can follow directions but would be more comfortable if some basic instruction were written. Treat me like I'm 10.
It looks like the best way to do this is as follows:
"From this thread:
http://forum.xda-developers.com/showthread.php?t=874871
Attached is a working sqlite3 binary.
Copy it to /system/bin
(I transfered it to my SD, then used rootexplorer (mount R/W) to copy into /system/bin))
you will now be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
--------------------------------------------------------------------------------
In your terminal:
$ adb pull /data/data/com.bn.devicemanager/databases/devicemanager.db devicemanager.db
$ sqlite3 devicemanager.db
sqlite> update registry set value='manual' where name='com.bn.device.fota.mode';
sqlite> .q
$ adb push devicemanager.db /data/data/com.bn.devicemanager/databases/devicemanager.db
$ adb reboot
"
Do I unzip the attached binary and paste that into the location or the .zip as a whole? What do I use as a terminal?
I've been flashing my DROID since day one but the NC development circle has been far from entry level user-friendly. Any help would be appreciated.

you can do it on windows too.
1) pull/get/copy the.db file from your phone to your pc
2) update the database file using sqlitebrowser. I.e run the sql command "update ......". Close sqlitebrowser.
3)push/put/copy the updated .db file to the same location overwriting the original.

britoso said:
you can do it on windows too.
1) pull/get/copy the.db file from your phone to your pc
2) update the database file using sqlitebrowser. I.e run the sql command "update ......". Close sqlitebrowser.
3)push/put/copy the updated .db file to the same location overwriting the original.
Click to expand...
Click to collapse
Progress. However...
I got SQLite on my PC. I found the devicemanager file on my NC, pasted it to my SD card for transfer over to my PC for editing. I trasnferred the file over to my PC for editing. I open SQLite but have no idea how to use it.

I just did this today using sqlite editor only!!! Its a GUI so it real simple to use.
1.Install the apk
2.reboot
3.go to extras and launch sqlite editor
4.allow it, give it the permision it needs
5.look for DeviceManagerService
6.click on devicemanager.db
7.click on registry
8.look for _id 7, name>>>> "com.bn.device.fota.mode"
9.scroll to the right and click and hold value field "auto", until a little pop up shows and select edit field
10. Change the value from auto to manual
11. Save
Done!!!
If you need the apk here is a link I just made
?d=LTSQDZ65 for megaupload (sure u guys can piece it together!)
Let me know if it helped anyone!

Yes, we totally need another thread on this. I must note that pushing the build.prop in my thread and my two Nook Colors have not updated. Dunno about this method or others. Caveat emptor!

This is exactly what I was looking for. Thank you. Very simple.
Sent from my NC using XDA App

Thanks for breaking it down for us, nookme.
Do we need to do this if we are operating from an SD bootable Froyo or CM7 ROM?

tablo said:
Thanks for breaking it down for us, nookme.
Do we need to do this if we are operating from an SD bootable Froyo or CM7 ROM?
Click to expand...
Click to collapse
In theory it should work for both, whether its a soft root mod or simply a bootable sd card that emulates froyo... It's a matter of just having root access and changing a registry setting on the device itself. Hope this shines some light! happy rooting ppl

Not noobie enough for me, sigh
So, if I have followed these directions from an earlier post have I messed something up? Not blocked updates at all? I don't understand the directions in this thread. What happens if I don't block the update? There must be a lot of people like me who had the technical skills to manage the root process but don't understand all of your coded instructions. I read in another thread that I should do a Titanium backup. How does that help after an update? Will market aps that have already been downloaded still work? Will everything revert to stock? Could someone explain what we should expect? Thanks!
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w

Droiddict said:
So, if I have followed these directions from an earlier post have I messed something up? Not blocked updates at all? I don't understand the directions in this thread. What happens if I don't block the update? There must be a lot of people like me who had the technical skills to manage the root process but don't understand all of your coded instructions. I read in another thread that I should do a Titanium backup. How does that help after an update? Will market aps that have already been downloaded still work? Will everything revert to stock? Could someone explain what we should expect? Thanks!
To disable OTA (over the air) updates:
Change the name of this file: otacerts.zip to anything else
To do this, get root explorer ($3) from the market
Run root explorer
Go to etc/security/otacerts.zip
Hit the little mount button near the top to change r/w to r/o
Rename the file otacerts.zip to otacerts.zip_DISABLED_OTA_UPDATES
Hit the little mount button again to change r/o back to r/w
Click to expand...
Click to collapse
If you read this >> http://forum.xda-developers.com/showthread.php?t=1007551
you will see that the sqlite method is used by many and is the simplest way too, again this is a GUI, so no shell command line... How can this be difficult??
Just follow my steps... it works

I have had nothing but problems with my rooted NOOK Color due to B&N auto updates. I followed your instructions and now I hope my problems are resolved and my NOOK Color will never update again.
Thank you

Failing to update rooted 2.3.4 to 2.3.6 Nexus One - I wanna cry!!

Back a year ago I rooted my nexus one phone, but the thing is I uninstalled a few stock apps. I had no idea that my updates would be a pain.
What I found out is that each new google update does a ton of asserts on files that it expects to be there. I had a problem with google books when I tried to update from 2.3.3 to 2.3.4, but someone on this forum hack a cracked version that allowed me to do so.
Now the annoying problem is back again, and this time, it's saying something about assert_failed: apply patch check ("system/app/EmailGoogle.apk...
I tried to find an EmailGoogle.apk out there, and I was able to find it, but if I was to use it, it wouldn't connect at all, then it would crash. I also placed it in system/app folder, and still same problem.
Is there a way for me to hack the update.zip so I can tell it to ignore these assertions?

AHH! I figured it out!
After much searching for updating scripts, I found out that there is indeed a file that tells your phone how to perform a patch update.
This involved me rebooting the phone 7 times (with about 5 times prior with previous experimentation)
Okay what I had were the following items
-Dropbox
-Root Explorer
-Laptop
Initially I got the error after running anon ra recovery, but I lost it when I accidently updated 2.3.4 again (I stupidly named my files as update.zip, update1.zip, update2.zip). Actually, I lost root (the phone still had the unlocked thing on it, but it was fooled). So I used this website (to root my phone again):
http://chensun.net/android-development/root-nexus-one-with-android-2-3-3-gingerbread/8/
So to get the specific error
1.you shut down your phone
2. reboot by pressing power button and down volume and hold it
3. Select recovery by navigating using the down volume, and select it by pressing power button.
4. After it reboots again, scroll down using your trackball and select Flash zip from sdcard
5. make sure you toggle signature verification to disable
6. select your update.zip
thats how you get your error
to fix:
1. So I took the signed zip file, and uploaded it to my dropbox
2. I opened the file using winrar (DO NOT UNZIP THIS FILE TO EDIT) the reason you do not want to unzip is because if you zip it up again you lose the signature, and your phone won't find the script
3. I used winrar to navigate to the following:
META-INF-->com-->google-->android
4. Open update-script using notepad
5. crtl-f on each package-name searching through the file:
emailgoogle.apk
GenieWidget.apk
Mms.apk
Talk.apk
Twitter.apk
VoiceDialer.apk
(ugh.. I forgot I uninstalled all those)
they existed twice. Once to assert to make sure the file exists, and the second to apply the patch
You have to remove both, you can keep the progress bar command there, that's just to update the progress of your update on your screen
example
;assert(apply_patch_check("/system/app/Twitter.apk", "48dcef1792760138acb1c10e2a2341dfbee69258", "e3e34aa0a72d0eaf76d80a06828bd14ea8450d34"))
apply_patch("/system/app/Twitter.apk", "-",
48dcef1792760138acb1c10e2a2341dfbee69258, 1596937,
e3e34aa0a72d0eaf76d80a06828bd14ea8450d34, package_extract_file("patch/system/app/Twitter.apk.p"));
so after repeating this over and over, it finally updated
anyways, going to sleep

Unzip the file on your phone with eStrongs file manager.
Edit the update script (eStrongs again).
Rezip (eStrongs again).
Sign with ZipSigner, or toggle signature verification in recovery.
Flash.
Note, if you use the "flash zip from SD" option, you don't need to name the file "update.zip"

thanks danger-rat, seen your posts many times before, I saved lots of your comments in my evernote
I already knew about renaming update.zip, I just got into a dumb naming habit, the last 5 tries I just kept the name as it was
my root explorer (file manager) by speed software does what eStrongs does, I can edit, zip, tar, unmount folders, set permissions etc, maybe you should check it out
but i've learned two new things about your post
never heard of zipsigner, and eStrongs
thanks for showing the quicker way of doing this, the dropbox thing was a bit of a hassle, but I love editting this on my computer rather than my phone using the trackball touchpad combo :-|
I'm wondering why a solution wasn't even there when I was looking for answers around the web? I searched for hours too. I'm also glad I didn't brick my phone!

Yeah, I use Root Explorer a lot. I prefer the interface on eStrongs and love the LAN capabilities and Dropbox interface, but Root Explorer is much better when you need root permission.

[MOD] Lower Auto-Brightness levels to save battery

This is best done after you flash a ROM as you might lose some settings.
(I noticed my wall paper changed and i had to sign back into Google account)
---This framework-res.apk file is different for every ROM---
Hi,
I wanted to share a little mod that could help in extending battery life - lowering default auto-brightness levels. As all of You know our big, bright SuperLCD is an excelent display but for that it uses most of our battery:/
I like the idea of auto-brightness but I find it too bright for most of the time. Setting brightness manualy to one level makes it either too dim or it uses too much battery and switching it all the time that You go outside or turn on the light is a little bit inconvenient.
In order to lower auto-brightness levels You have to change values in framework-res.apk/res/values/arrays.xml and here is how (read whole post first )
These are stock HTC Raider values:
Click to expand...
Click to collapse
Code:
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>75</item>
<item>75</item>
<item>75</item>
<item>97</item>
<item>120</item>
<item>142</item>
<item>170</item>
<item>198</item>
<item>227</item>
<item>255</item>
</integer-array>
These are values that I use and found best for me:
Code:
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>20</item>
<item>40</item>
<item>50</item>
<item>70</item>
<item>90</item>
<item>100</item>
<item>130</item>
<item>155</item>
<item>180</item>
<item>225</item>
</integer-array>
These brightness levels are corresponding to the amount of light that light sensor is getting - the lowest value is while in the low light the highest when for example your phone is in direct sunlight. Brightness values are defined by numbers 1 is the lowest possible setting and 255 is the maximum brightness that can be set.
As You can see I was pretty aggressive with lowering these values and yet the screen is still bright in every situation. You can set them a little bit higher or lower in order to suit your preferences.
Here is a guide on how to perform this mod on any framework-res.apk using apk manager (thanks for the guide goes to desean):
1. Download APK manager and unpack somewhere
2. Grab framework-res.apk from your phone under \system\framework\ (e.g. adb pull) and place it in the "place-apk-here-for-modding" folder
3. Run Script.bat and select option 9
4. Once done, go to projects\framework-res.apk\res\values\arrays.xml and edit your values as per first post.
5. Once edited, compile the apk using option 11
6. Qn: Is this a system apk. Ans: y
7. Qn: Aside from the signatures, would .... least. Ans: y
8. Prompt: In the apk manager folder u'll find a keep folder..... done then press enter on this script. Press any key to continue . . . You have to go to "keep" folder and delete resources.arsc because arrays.xml have been changed. After this You can press any key in apk manager window.
9. Once done, input 25 in apk manager and select "unsignedframework-res.apk" by entering the number that stands for it. After selecting it You should see in apk main window in the top right corner "Current-App: unsignedframework-res.apk".
10. Now press 5 to zipalign apk. You will find your completed, zipaligned apk under place-apk-here-for-modding\unsignedframework-res.apk.
11.Rename it back to framework-res.apk and adb push the file back to your phone
Click to expand...
Click to collapse
To send it back to your phone
Prerequisites have...
The file you are pushing must be placed in the platform-tools folder of adb so if you are pushing file "framework-res.apk" this needs to be downloaded/copy and pasted in C:\android-sdk-windows\platform-tools
1: go to run and type cmd (or just open your command prompt)
2: cd C:\android-sdk-windows\platform-tools
3: adb remount
4: adb devices *if everything is set up right this should output a serial number*
5: adb push FFFFFFF.FFF /#####/###### *i hope my notes help here you need to put the file name in for the F(s) and in the pound signs you put the destination on the devices:
Code:
adb push framework-res.apk /system/framework
7. adb reboot this is how you finish
Click to expand...
Click to collapse
You have to copy the file to your phone with ADB or you will get a boot loop and have to re install your ROM.
Link for APK Manager HERE
If you have problems with apk manager showing java error (like it did) this post helped me fix that
Sources:
http://forum.xda-developers.com/showthread.php?t=1235212
http://forum.xda-developers.com/showthread.php?t=695701
http://forum.xda-developers.com/showthread.php?t=642437
APK Manager 4.9 download link (currently original thread link down)
http://www.zshare.net/download/99034654c32618ba/

WOW! I was just about to ask if anyone knew how to accomplish this! Thanks dude!
Edit: Er..phone just went into a bootloop. Lemme try again..
Edit2: I first replaced the framework-res.apk using root explorer...big mistake, phone went into a bootloop and I couldnt adb to it to push the apk correctly, whoops. Just reinstalled the ROM I was using and pushed the apk using adb and all is well.
I noticed two other very similar looking values: config_autoBrightnessLcdBacklightValuesUp and config_autoBrightnessLcdBacklightValuesDown. Is it necessary to change these as well?

m0biusace said:
WOW! I was just about to ask if anyone knew how to accomplish this! Thanks dude!
Edit: Er..phone just went into a bootloop. Lemme try again..
Edit2: I first replaced the framework-res.apk using root explorer...big mistake, phone went into a bootloop and I couldnt adb to it to push the apk correctly, whoops. Just reinstalled the ROM I was using and pushed the apk using adb and all is well.
I noticed two other very similar looking values: config_autoBrightnessLcdBacklightValuesUp and config_autoBrightnessLcdBacklightValuesDown. Is it necessary to change these as well?
Click to expand...
Click to collapse
Yes you have to use adb ill put that in the first post,
to be honest i am not entirely sure what that is for i assume, that it is when you move the slider what values it displays when you slide it, i noticed a change without changing those values.
also i changed the button back lights to 200, i find it more than enough for me.

Is there a working mirror to APK manager? The link in the thread is down.

uploaded
sbddude said:
Is there a working mirror to APK manager? The link in the thread is down.
Click to expand...
Click to collapse
uploaded here
http://www.zshare.net/download/99034654c32618ba/

Serious props to you jul644 for detailing this process! I've always hated how the Hero, Evo, & now Vivid I've had never got dark enough in pitch black rooms, and now I'm excited to fix that problem. I was curious though since I just modded my battery meter using UOT Kitchen, if I could drop in the backlight-modded framework-res.apk via 7-zip replacing the UOT framework-res.apk file then flash it via recovery. I wonder if that would make me sign into Google and mess with settings like you mentioned. Thanks.

How-To with UOT
jul644 said:
You have to copy the file to your phone with ADB or you will get a boot loop and have to re install your ROM.
Click to expand...
Click to collapse
How, if it's possible, do we integrate this modded framework-res.apk into a UOT Kitchen zip flash file? I want to mod my battery icons and would like to install at the same time so one doesn't interfere with the other. Should I upload the framework-res.apk from this to UOT Kitchen (with my original SystemUI.apk) and then change the battery icons, then download and flash?
Thanks for your help!
*****EDIT - 2/15/2011*****
Ok so I did the framework-res.apk edits by decompiling/recompiling per jul644, uploaded that into UOT Kitchen along with original SystemUI.apk and com.htc.resources.apk. I chose my battery icon mod, downloaded, cleared all the caches and flashed in recovery with no problems ) Just wanted to let you guys know how to make it a recovery flashable zip instead of pushing via ADB.

ICS?
So can anyone confirm or deny if this still works wit ICS will be trying it myself, when I get a chance, but would rather not waste time if it wont work!

It does work, I have done it. ICS it's just more difficult to decompile & recompile. I added it & 1% stock-style battery icons into Pirateghost's CWM .56 flashable ROM.

Keep getting errors when recompiling using stock telstra ICS+ root
error on 1st line after selecting option 11 ie. step 5 above
could not find sources????
Any suggestions what I am doing wrong????
---------- Post added at 09:37 PM ---------- Previous post was at 09:24 PM ----------
okay also getting this error twice before it de-compiles
the system cannot find the path specified
then seems to decompile happily???????????
Any suggestions?

I'm getting an 'Operation not permitted' when I try to remount before pushing the file back. Anyone else having this problem? I'm running a WCX GB ROM (no ICS, I'm on Rogers).

formicae said:
I'm getting an 'Operation not permitted' when I try to remount before pushing the file back. Anyone else having this problem? I'm running a WCX GB ROM (no ICS, I'm on Rogers).
Click to expand...
Click to collapse
are you trying to remount your sd card? if so do not, just select charge only

No, just trying to remount as per the instructions in the first post, so /system is R/W. Setting it to charge only. No dice.
I tried doing it in recovery (by mounting /system, then going through the ADB commands, all of which are successful), but the result is a bootloop once I'm done.
Edit: It's also worth noting that newer versions of APK Manager/Multi-tool seem to have different numbering for the operations. In step 9, number 22 sets the compression level, whereas I think it used to set the active APK (which I think is 25 now).

I ended up taking the stock framework-res from the ROM, modifying the arrays.xml values as per the OP instructions, then going through the UOT Kitchen (I had a battery mod anyway). Worked perfectly.
Thanks to pauley for reporting success earlier, which provided me with the workaround.

Has anyone done this that could possibly create a flashable zipped version of it? I tried to do it myself but with the new APK Multi Tool things were different to the instructions of OP and I couldn't get it to work
Edit: Nvm managed to fix it and make my own flashable zip. Thanks for the effort OP

I have tried to do this... And I keep getting an error on the recompile side...
Just wondering... Does apkmanager require windows 7 or something... Or is there some reason it wouldn't work on windows xp?
Sent from my HTC PH39100 using Tapatalk 2

rignfool said:
I have tried to do this... And I keep getting an error on the recompile side...
Just wondering... Does apkmanager require windows 7 or something... Or is there some reason it wouldn't work on windows xp?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
The errors I encountered when compiling were solved by:
1) Putting Java in the windows path
2) Putting ADB in the windows path
3) Not having any spaces in the APK Manager file path
There are no OS dependencies that I'm aware of. Just open the log from within the APK manager and you should be able to identify the error.

The problem is I don't really speak java all that well...
Could I just move the java executable to the working directory?
Sent from my HTC PH39100 using Tapatalk 2

rignfool said:
The problem is I don't really speak java all that well...
Could I just move the java executable to the working directory?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
For java, all you have to do is download the JDK (i got the 32 bit version), and then add 'C:\Program Files (x86)\Java\jdk1.7.0_03\bin' to the windows path so it becomes something like:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\MATLAB\R2011a\runtime\win64;C:\Program Files\MATLAB\R2011a\bin;C:\Program Files (x86)\MKVToolNix;C:\Program Files (x86)\Java\jdk1.7.0_03\bin;C:\Android\android-sdk\platform-tools\;C:\Android\APKMultiTools\
For Windows XP, you'd probably be running 32 bit and so it would be installed in the regular program files.

pod0087 said:
For java, all you have to do is download the JDK (i got the 32 bit version), and then add 'C:\Program Files (x86)\Java\jdk1.7.0_03\bin' to the windows path so it becomes something like:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\MATLAB\R2011a\runtime\win64;C:\Program Files\MATLAB\R2011a\bin;C:\Program Files (x86)\MKVToolNix;C:\Program Files (x86)\Java\jdk1.7.0_03\bin;C:\Android\android-sdk\platform-tools\;C:\Android\APKMultiTools\
For Windows XP, you'd probably be running 32 bit and so it would be installed in the regular program files.
Click to expand...
Click to collapse
thanks for the help! can you tell me the new number system with apk manager?

Disable Xposed Lollipop 5.1

I am having problems with some evidence of modules and the phone will not start. What we need is that the corresponding zip climb to disable Xposed from recovery since the beta 2 version lollipop Disable-xposed-recovery.zip not create the file. Of course I appreciate any help.
Desde mi Super Note N7000

When I had problems with xposed, I just reboot phone, just after the boot logo appears, I press power button several times until at every power key press the device vibrates slightly. After 3 or 4 vibrations, I only wait for the device to boot normally or sometimes I made it power off and power it on.

Radamantys-N7000 said:
I am having problems with some evidence of modules and the phone will not start. What we need is that the corresponding zip climb to disable Xposed from recovery since the beta 2 version lollipop Disable-xposed-recovery.zip not create the file. Of course I appreciate any help.
Desde mi Super Note N7000
Click to expand...
Click to collapse
franzpimp87 said:
When I had problems with xposed, I just reboot phone, just after the boot logo appears, I press power button several times until at every power key press the device vibrates slightly. After 3 or 4 vibrations, I only wait for the device to boot normally or sometimes I made it power off and power it on.
Click to expand...
Click to collapse
You can also use your Recovery's file manager. Goto /data/data/de.robv.android.xposed.installer and create a new file called "disabled" (without quotes and no extension).
If you cant create a new file, try copying the modules.list file and then paste it somewhere, rename it "disabled" (without quotes) and put back into that folder.
Then your phone will boot up w/ xposed disabled and you can then uncheck the module that isn't compatible, and delete the "disabled" file you created.
(this looks complicated but its actually very simple)
Hope that helps

USHERROB said:
You can also use your Recovery's file manager. Goto /data/data/de.robv.android.xposed.installer and create a new file called "disabled" (without quotes and no extension).
If you cant create a new file, try copying the modules.list file and then paste it somewhere, rename it "disabled" (without quotes) and put back into that folder.
Then your phone will boot up w/ xposed disabled and you can then uncheck the module that isn't compatible, and delete the "disabled" file you created.
(this looks complicated but its actually very simple)
Hope that helps
Click to expand...
Click to collapse
What is being proposed to modify or create a file, it is impossible to do it from recovery since we have a file manager with which to work, so the idea is to have a flashable zip to disable or delete Xposed modules. From already thank you very much for the input!
Desde mi Super Note N7000

It's actually far from impossible. You can simply boot into TWRP, then 'adb shell' from your computer. From there, simply 'touch /data/data/de.robv.android.xposed.installer/disabled'. Then you can reboot.

USHERROB said:
You can also use your Recovery's file manager. Goto /data/data/de.robv.android.xposed.installer and create a new file called "disabled" (without quotes and no extension).
If you cant create a new file, try copying the modules.list file and then paste it somewhere, rename it "disabled" (without quotes) and put back into that folder.
Then your phone will boot up w/ xposed disabled and you can then uncheck the module that isn't compatible, and delete the "disabled" file you created.
(this looks complicated but its actually very simple)
Hope that helps
Click to expand...
Click to collapse
Radamantys-N7000 said:
What is being proposed to modify or create a file, it is impossible to do it from recovery since we have a file manager with which to work, so the idea is to have a flashable zip to disable or delete Xposed modules. From already thank you very much for the input!
Desde mi Super Note N7000
Click to expand...
Click to collapse
If you get a zip of aroma file manager you can use recovery to flash that, you can use it to manage files on your device. It has a terminal built-in too, and a much nicer keyboard IMO.

syndre said:
If you get a zip of aroma file manager you can use recovery to flash that, you can use it to manage files on your device. It has a terminal built-in too, and a much nicer keyboard IMO.
Click to expand...
Click to collapse
Yea thats exactly what i used. I probably shouldve mentioned that, i kinda just assumed. Oops! lol. But yes you are correct Download the latest aromafm zip and place in correct directory, then change settings in twrp to use aroma file manager.
EDIT: Latest that worked for me was v2.00 b6
https://github.com/amarullz/AROMA-Filemanager/releases/tag/2.00

Xposed Alpha 3/ disable-xposed.zip not generate the file in the proper place, that file you're talking about when they say they use Aroma? Thanks
Desde mi Super Note N7000

USHERROB said:
You can also use your Recovery's file manager. Goto /data/data/de.robv.android.xposed.installer and create a new file called "disabled" (without quotes and no extension).
If you cant create a new file, try copying the modules.list file and then paste it somewhere, rename it "disabled" (without quotes) and put back into that folder.
Then your phone will boot up w/ xposed disabled and you can then uncheck the module that isn't compatible, and delete the "disabled" file you created.
(this looks complicated but its actually very simple)
Hope that helps
Click to expand...
Click to collapse
Can i just create a file "disabled" and place it somewhere else while my phone is working fine and copy it to the xposed directory when I want to disable xposed? Does this really work?
Edit : Creating this file does not disable xposed.

motorolag said:
Can i just create a file "disabled" and place it somewhere else while my phone is working fine and copy it to the xposed directory when I want to disable xposed? Does this really work?
Edit : Creating this file does not disable xposed.
Click to expand...
Click to collapse
it should work, but you have to set the correct permissions after copying to xposed data directory

Problem installing xposed
Please refer to attachment i need help.
Mine is Z1 deodexed 5.1

firdyRAY said:
Please refer to attachment i need help.
Mine is Z1 deodexed 5.1
Click to expand...
Click to collapse
Xposed doesn't work on 5.1 yet unfortunately

android 11 root problem miui 12.5

hi.I rooted the phone using magisk, it was installed and apparently rooted, but I have a problem with root file programs like root explorer or es file manager. The problem is that the rw mount does not work or I even have trouble installing busybox.
my phone : redmi note 10 pro
miui version : 12.5.8 and 12.5.9
android version : 11
magiak version : 23

I don't know deeply this case, but it was told that mounting r/w is not possible in recent Androids for system partitions.
However this is Magisk benefit that you put your files to it's tree and Magisk overmounts original files, I guess it does it using option "mount --bind".
You put file into /data/adb/modules/<module_name>/system/etc/<exemplary file> and after reboot you see it under /system/etc/.
At least the above path was checked personally by me by changing /system/etc/gps_psds.conf file to my own.

F308 said:
I don't know deeply this case, but it was told that mounting r/w is not possible in recent Androids for system partitions.
However this is Magisk benefit that you put your files to it's tree and Magisk overmounts original files, I guess it does it using option "mount --bind".
You put file into /data/adb/modules/<module_name>/system/etc/<exemplary file> and after reboot you see it under /system/etc/.
At least the above path was checked personally by me by changing /system/etc/gps_psds.conf file to my own.
Click to expand...
Click to collapse
I want to install a program as a system, but it is not possible without rw mount, do you know the solution?

I presume you have at least one Magisk module installed.
Put it into /data/adb/modules/<any_Magisk_module_name>/PATH_WHERE_YOU_WANT_TO_HAVE_IT/.
If wanted directories don't exist - create them.
Reboot.
Check.
Maybe tune permissions to make file executable.
Report result here.

F308 said:
I presume you have at least one Magisk module installed.
Put it into /data/adb/modules/<any_Magisk_module_name>/PATH_WHERE_YOU_WANT_TO_HAVE_IT/.
If wanted directories don't exist - create them.
Reboot.
Check.
Maybe tune permissions to make file executable.
Report result here.
Click to expand...
Click to collapse
I have no problem installing the module. My problem is accessing the system / app folder and making changes.

What changes do you want to perform?
Change one or more of files there, right?
If so - I repeat.
Put your modified file(s) under /data/adb/modules/<any_installed_Magisk_module_name>/system/app/ and reboot.

F308 said:
What changes do you want to perform?
Change one or more of files there, right?
If so - I repeat.
Put your modified file(s) under /data/adb/modules/<any_installed_Magisk_module_name>/system/app/ and reboot.
Click to expand...
Click to collapse
I do not want to install the module, I want to move an apk file to the system/app folder that is installed as a system and can not be deleted

I wasted my time.
Good luck.

I devoted a while to check that I was right suggesting what I suggested.