Database Develop

SuperD latest changing physical layout

I ve noticed that many people have posted having problems with keyboard layouts after flashing a rom. I have a German G1 which was rooted to Cyanogens 4.2.14.1 before, and I never had problems keeping the phone in English but retaining the German keyboard (I ve gotten use to it).
But after flashing Super D just now (which is AWESOME), my keyboard has defaulted back to the U.S keyboard, which is really annoying.
Anyone know exactly why this problem didnt exist in Cyanogens rom and why it does exist with SuperD? Also, Im assuming this is something I have to live with, as I couldnt find an easy fix for it? I really just want the German keyboard back.
Any help would really be appreciated.

1.SuperD isnt Cyanogen
2.Most Likely in the scripts that have to do with the keyboard.
Hope that didnt sound rude but yeah =/ You would probably have to change something in the system/usr directory.

I had the same problem and solved it like so:
1.) DL and unzip the zip file I have attached
2.) copy the file to your SD card root folder
3.) open a Terminal Emulator app and type the following (press Enter after each line and allow if it ask for permission):
su
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system/usr/keychars/
dd if=/sdcard/trout-keypad-v3.kcm.bin of=trout-keypad-v3.kcm.bin
4.) Reboot your phone.
5.) Profit...
You will have to do this after every ROM flash, but it literally just takes a few seconds, so not worth mentioning.

kugelfish said:
I had the same problem and solved it like so:
1.) DL and unzip the zip file I have attached
2.) copy the file to your SD card root folder
3.) open a Terminal Emulator app and type the following (press Enter after each line and allow if it ask for permission):
su
mount -o remount,rw /dev/block/mtdblock3 /system
cd /system/usr/keychars/
dd if=/sdcard/trout-keypad-v3.kcm.bin of=trout-keypad-v3.kcm.bin
4.) Reboot your phone.
5.) Profit...
You will have to do this after every ROM flash, but it literally just takes a few seconds, so not worth mentioning.
Click to expand...
Click to collapse
This is exactly what I tried, but after the "dd if=/sdcard/trout-keypad-v3.kcm.bin of=trout-keypad-v3.kcm.bin" command in terminal, I get an error that says:
"cannot open for write: Read-only file system"
Not sure what Im doing wrong. I unzipped the file, put it on sd card, and entered in the commands.
I heard this method works for everyone, but for some reason I get this error when i try it.

Sadly, I'm not to familiar with linux or coding in general, but I would assume something went wrong when remounting. Your system folder seems to remain read-only...
Maybe someone more qualified can help with the right command line... ?
Edit
make sure there is a space between mtdblock3 and /system like so (shown red):
mount -o remount,rw /dev/block/mtdblock3SPACE/system

kugelfish said:
Sadly, I'm not to familiar with linux or coding in general, but I would assume something went wrong when remounting. Your system folder seems to remain read-only...
Maybe someone more qualified can help with the right command line... ?
Edit
make sure there is a space between mtdblock3 and /system like so (shown red):
mount -o remount,rw /dev/block/mtdblock3SPACE/system
Click to expand...
Click to collapse
Still no luck. I double checked, and its typed correctly. I tried swapping this command:
mount -o remount,rw /dev/block/mtdblock3 /system
for this one:
mount -o rw,remount /dev/block/mtdblock3 /system (found in another thread)
but it still didnt work. After I tried using the "mount -o rw,remount /dev/block/mtdblock3 /system" command that I found in the other thread, I didnt get the error, and thought this may have fixed the keyboard. But when I rebooted, the keyboard was still wrong.

Sorry dude, that's all I got. All I can say is, it works for me.
Maybe this'll help?
http://www.handy-faq.de/forum/htc_d...ogle_g1_qwertz_tastatur_wiederherstellen.html

try: mount -o rw,remount yaffs2 /system

bubonik said:
try: mount -o rw,remount yaffs2 /system
Click to expand...
Click to collapse
It worked!!! Thanks to everybody for all there help. It was this one command line that made all the difference!
So nice to have a keyboard again where all the keys actually display what they are supposed to. It was driving me crazy.
Thanks again guys

[GUIDE] How to Remove Pre-Installed Apps for FREE

First, you need to install the drivers:
http://www.samsung.com/us/support/d...R&prd_mdl_name=SPH-D700&prd_ia_sub_class_cd=P
Then you must be rooted:
http://forum.xda-developers.com/showthread.php?t=775110
Next, get the most current SDK:
http://developer.android.com/sdk/index.html
Extract the zip and put it where it's easiest for you to get to on Command Prompt. I put it in my C:\ for extremely easy access.
Now, open up Command Prompt and put in these commands in order
1.
Code:
cd C:\android-sdk-windows\tools
2.
Code:
adb devices
3.
Code:
adb shell
4.
Code:
su
5.
Code:
mount -t rfs -o remount,rw /dev/block/stl9 /system
6.
Code:
cd /system/app
7.
Code:
ls
Now you should see a list of all the pre-installed Apps on your device. To remove these apps you must use this command:​
Code:
rm "app_name.apk" or rm "odex_name.odex"
Here is a list of all the pre-installed apps on the stock Epic ROM and an explaination for most of them:
http://forum.xda-developers.com/showthread.php?t=773142
-------------------------
Here is my suggested list to use:​
Code:
rm amazonmp3.apk[LEFT]rm Asphalt5_DEMO_ANMP_Samsung_D700_Sprint_ML.apk[/LEFT]
rm MediaHub.apk
rm nascar09-prod-release.apk
[LEFT]
rm sfl-prod-release.apk
[LEFT]
rm SN28-1092-sprint-signed.apk
[LEFT]
[LEFT]rm SprintTV.apk
[LEFT]rm SprintTVWidget.apk[/LEFT]
[/LEFT]
[/LEFT]
rm SprintZone.apk
[LEFT]rm MobileAP.apk - Only if you don't pay for the $30 hotspot[/LEFT]
rm MobileAP.odex - Only if you don't pay for the $30 hotspot
[/LEFT]
[/LEFT]

Titanium backup is easier and less time consuming then messing with ADB and is free.

Eh, not really. ADB is much more resourceful and has alot more uses and options if you learn how to use it. This is only one of it's uses. Titanium Backup is just a waste of space IMO. It is very limited on the free version.

Or you can use SDX App Removal if your interested in only removing the preinstalled apps (must be rooted).
Sent from my SPH-D700 using XDA App

At the expense of sounding like a noob, which I guess I am when it comes to Android, I'm getting a real-only error. I rooted with noobnl and Titanium Backup tells me I'm rooted. What might I be doing wrong?

Try using this as the mount command:
mount -t rfs -o remount,rw /dev/block/stl9 /system
Or better yet use one of the GUI options unless you are familiar with linux and save the headache. If all you want to do is remove apps there are far easier methods that are less time consuming. Titanium backup and SDX removal tool are both free.

Sesquipedalian said:
At the expense of sounding like a noob, which I guess I am when it comes to Android, I'm getting a real-only error. I rooted with noobnl and Titanium Backup tells me I'm rooted. What might I be doing wrong?
Click to expand...
Click to collapse
Hmmm see I got that error too when I first did it, but then I did it again and it worked perfect lol...

Mine is Wildfire, I have some issues:
Can not do this:
mount /dev/block/mtdblock4 /system
or
mount -t rfs -o remount,rw /dev/block/stl9 /system
But actual there exists a directory /system/app, in which I can see all the .apk and .odex files. When I tried to delete a file, it says that 'rm failed for File-Name, read-only file system'
What should I do? thanks

xirochanh said:
Mine is Wildfire, I have some issues:
Can not do this:
mount /dev/block/mtdblock4 /system
or
mount -t rfs -o remount,rw /dev/block/stl9 /system
But actual there exists a directory /system/app, in which I can see all the .apk and .odex files. When I tried to delete a file, it says that 'rm failed for File-Name, read-only file system'
What should I do? thanks
Click to expand...
Click to collapse
Well this is for the Samsung Epic...so i have no idea what you have to do

Whosdaman said:
Mine is Wildfire, I have some issues:
Can not do this:
mount /dev/block/mtdblock4 /system
or
mount -t rfs -o remount,rw /dev/block/stl9 /system
But actual there exists a directory /system/app, in which I can see all the .apk and .odex files. When I tried to delete a file, it says that 'rm failed for File-Name, read-only file system'
What should I do? thanks
Click to expand...
Click to collapse
Now I can mount, to over come the read-only problem, however whenever I delete a file, it says that: rm failed for filename.apk, Directory not empty
You guys have any advice? thanks

xirochanh said:
Now I can mount, to over come the read-only problem, however whenever I delete a file, it says that: rm failed for filename.apk, Directory not empty
You guys have any advice? thanks
Click to expand...
Click to collapse
hmmmm idk....thats seems really strange. Maybe its something you cant delete

I tried to reboot in HBOOT/Recovery/ Partition Menu, then mount /system. Then I could remove apps in adb shell successfully. can anyone confirm that doing like this is ok?
My wildfire was rooted with unrevoked3

If it works then it should be fine
Sent from my SPH-D700 using XDA App

This is confirmed to still work with the DI07 update

My noob question is I am using titanium backup to remove the sprint bloatware like media hub and it looks like the program removes it but when I exit titanium it is still on the phone.

Aridon said:
Titanium backup is easier and less time consuming then messing with ADB and is free.
Click to expand...
Click to collapse
Titanium backup is the mark of the noob in my opinion.

thanks, i had been searching around for the adb commands to mount the system r/w so i could remove the bloat.

SDX Stock App Removal is tops in my opinion.
Quick, simple, and allows for back-ups.
And I also don't think Titanium is the "Mark of the noob". It would be more like the "Mark of the ADB is unnecessary for stock application removal"
Also I don't think this should be in development. And if you know ABD commands you should know that.

This thread is okay....but sdx..and root uninstaller are awsome. Thanks for this guide though my friend very useful info for those that want to experiment with adb....
Sent from my Nexus S 4G using XDA Premium App

More options is a good thing. This is also helpful for the noobs who want to get their feet wet with unix/linux shell commands.

How to get root access from kernel, with no busybox and not building any sources

Hi folks,
On my way trying to get 10 usefull posts to access the developers forums, I have writen this easy tutorial. xD
THIS IS FOR S5830i DEVICES. init.rc used belongs to S5830i ramdisk
Whats all about? Well, in this tutorial I will so you how to get root access directly from Kernel only modifing init.rc and adding su to tmp folder.
THIS IS NOT UNSECURING THE BOOT.IMG TUTORIAL
Question: Axyllum why are you posting this, if there are so many tutorials on how to do this for other devices?
Answer: Simple, as you all ready imagine, partition for boot.img is just 5MB Oh my god.
Then, if my boot image is all ready 4.28MB, how can I use a busybox thats 836KB (I compiled a busybox with mount, cp, mkdir, chmod and chown that is the minimum to get root: image = 836MB). Cant use this beacuse I exceed total mounting point size.
Kernel + ramdisk = 4.28MB if you pull stock boot.img from your device.
Minimum busybox explained before = 836KB
SU image 25KB to 86KB depending on the su image you use.
This makes a total of: 5.2MB. Try to flash it. It fails? Yes, you exceeded the mounting point size.
And the solution? Follow my tutorial.
Abilites you will need to follow the turotrial:
Know how to: Un pack & repack boot.img
Know how to: Decompress Ramdisk and compress it back. (to get the famous newramdisk in many many tutorials) newramdisk is just a name, you can compress back to any name, for example axyllumramdisk or yourramdisk or how ever you want to call it.
Asuming you know how to do the explained above and after my wierd chat, lets gooooo:
1. Open init.rc in your favourite text editor.
2. Go to this line in init.rc:
mount rfs /dev/stl9 /system check=no
You should see this:
mount rfs /dev/stl9 /system check=no
mount rfs /dev/stl9 /system ro remount
Got it? lets go to step 3.
3. Overwrite both lines with this:
mount rfs /dev/stl9 /system check=no
mkdir /system/xbin
copy /tmp/su /system/xbin/su
chown root root /system/xbin/su
chmod 06755 /system/xbin/su
mount rfs /dev/stl9 /system ro remount
Make sure you are not overwriting other lines or your ramdisk could not work.
4. Paste SU image file to tmp folder. Make sure SU image has execute permissions.
5. Compress back ramdisk (the famous newramdisk).
6. Repack boot.img
7. Flash it.
8. Restart device.
9. Download superuser.apk and busybox form market and.... there you go you made your kernel with root access and no need of a busybox.
Ok, this was simple, but i imagine more than one will like to know what we did.
I'll explain:
As we cant add a busybox, how the hell am i going to mount system rw, mkdir xbin, cp su from tmp to xbin, chmod / chown permissions?
I started reading the init.rc file (i was bored and my wife wanted to go shopping --> no way i have an init.rc file to mess up with), and I saw many mkdir, copy, chmod etc... commands. (Opened a beer)
So i thought, great, there is all ready a busybox with the least i need to make this. Then why dont i use this preinstalled commands?
And i did this:
mount rfs /dev/stl9 /system check=no --> first I checked this, this instruction is where init.rc mounts system. At this point system is mounted RW.
mkdir /system/xbin --> Then as system is rw, I will create xbin folder. how? with mkdir comand.
copy /tmp/su /system/xbin/su --> Great I did not find a cp command, but found a "copy" command someware in init.rc. Search for it, you will see its used. Then why dont I use it to copy SU in tmp folder to the just created xbin folder? It worked.
chown root root /system/xbin/su --> Owner of su in xbin is: yes, root.
chmod 06755 /system/xbin/su --> Set the right permission to su. You need to chmod with 06755. --> 09364, 66666, 83823 will not work looooolll just a joke i imagine you all ready know what setting permissions is all about.
mount rfs /dev/stl9 /system ro remount --> Remount system with ro (this is the read only remount command).
I dont know if there are any other tutorials doing this, this way, i just did it my self. I Found tutorials on doing the same, but busybox, and .sh script and su were needed. To much for our small boot.img partition.
Enjoy.
Tip, dont mess your init.rc if you do not understand it.

Help with Magisk module

Hi,
It's nice you do not have to mod .prop files with Magisk module's system.prop .
But how do you mod .xml files ?
I'm struggling here...
Here is the bash I'd like to run, but it will need RW rights on /cust and /product
Code:
cp /cust/hw/eu/xml/hw_defaults.xml /cust/hw/eu/xml/hw_defaults.xml.BACKUP && cp /product/etc/xml/hw_launcher_default_config.xml /product/etc/xml/hw_launcher_default_config.xml.BACKUP && sed -ie 's/<integer settings.global.hw_4g_show="0" reset="true"/<integer settings.global.hw_4g_show="1" reset="true"/g; s/<string app_name_two_lines="false"/<string app_name_two_lines="true"/g; s/<string hw_add_4g_only="250"/<string hw_add_4g_only="208"/g; s/<string hw_data_roam_option="26006,27211"/<string hw_data_roam_option="ALL"/g' /cust/hw/eu/xml/hw_defaults.xml && sed -ie 's/<item name="config_desktopCellsOptionItems" reset="true">4x5,4x4,5x4,5x5</<item name="config_desktopCellsOptionItems" reset="true">4x6,4x5,4x4,5x4,5x5,5x6</g; s/<item name="config_IconTitleSize">12</<item name="config_IconTitleSize">9</g' /product/etc/xml/hw_launcher_default_config.xml
Any idea where to put this code into my magisk module ?
How should I'll be able to replace, via terminal cmds, files on /product & /cust (oreo huawei device)

oslo83 said:
Hi,
It's nice you do not have to mod .prop files with Magisk module's system.prop .
But how do you mod .xml files ?
I'm struggling here...
Here is the bash I'd like to run, but it will need RW rights on /cust and /product
Code:
cp /cust/hw/eu/xml/hw_defaults.xml /cust/hw/eu/xml/hw_defaults.xml.BACKUP && cp /product/etc/xml/hw_launcher_default_config.xml /product/etc/xml/hw_launcher_default_config.xml.BACKUP && sed -ie 's/<integer settings.global.hw_4g_show="0" reset="true"/<integer settings.global.hw_4g_show="1" reset="true"/g; s/<string app_name_two_lines="false"/<string app_name_two_lines="true"/g; s/<string hw_add_4g_only="250"/<string hw_add_4g_only="208"/g; s/<string hw_data_roam_option="26006,27211"/<string hw_data_roam_option="ALL"/g' /cust/hw/eu/xml/hw_defaults.xml && sed -ie 's/<item name="config_desktopCellsOptionItems" reset="true">4x5,4x4,5x4,5x5</<item name="config_desktopCellsOptionItems" reset="true">4x6,4x5,4x4,5x4,5x5,5x6</g; s/<item name="config_IconTitleSize">12</<item name="config_IconTitleSize">9</g' /product/etc/xml/hw_launcher_default_config.xml
Any idea where to put this code into my magisk module ?
How should I'll be able to replace, via terminal cmds, files on /product & /cust (oreo huawei device)
Click to expand...
Click to collapse
Hello,
If you are already aware that these modifications will be in the actual filesystems and not masked by Magisk, you can put that code into config.sh as a function and call that from update-binary.
Regards.

Thanks
JayminSuthar said:
If you are already aware that these modifications will be in the actual filesystems and not masked by Magisk
Click to expand...
Click to collapse
I am aware it will mod the actual files but i'm not sure how with magiskmodule I could mod some files AND THEN straighly use them to mask the originals.
JayminSuthar said:
, you can put that code into config.sh as a function and call that from update-binary.
Click to expand...
Click to collapse
You kind of lost me
I previously tried with post-fs-data.sh but i think my problem is i can't mod these file but i can make temporary copies somewhere (need to find where) then erase originals and then move temporary copies where originals where.
Instead of just should use something like:
Code:
sed -e 's/. /. /g' originalfile > /tmp/file.bak
rm originalfile
mv /tmp/file.bak originalfile

If I understand you correctly, /cust and /product are directly in the root of your device, not in /system? In that case you can't use Magisk to Magic Mount the files. That can only be done to /system or /vendor.
You should be able to edit the files in place though, you'll just have to mount the partitions as rw (and then back to ro when you're done). Something like this (but check the command syntax first, I don't know it fully from memory):
Code:
mount -o rw,remount /cust
<Do your thing here>
mount -o ro,remount /cust

Didgeridoohan said:
If I understand you correctly, /cust and /product are directly in the root of your device, not in /system? In that case you can't use Magisk to Magic Mount the files. That can only be done to /system or /vendor.
You should be able to edit the files in place though, you'll just have to mount the partitions as rw (and then back to ro when you're done). Something like this (but check the command syntax first, I don't know it fully from memory):
Code:
mount -o rw,remount /cust
<Do your thing here>
mount -o ro,remount /cust
Click to expand...
Click to collapse
You caught it up, I forgot about the rootfs being ro

I'll try and report.

It worked, thank you very much.
Now I'm facing some problem to make a module submission...
Code:
Bad Request:*https://github.com/oslo83/EMUI_Tap2wake*is not a valid Magisk Module!
Reason:*module.prop*does not exist on*masterbranch
....

[Pixel 3 android P ] how to use magisk to move file into /vendor partition

Hi everyone,
in pixel 2, I can get super su for adb shell, and can remount the system, /vendor partition
mount -o rw,remount -t auto /vendor
mount -o rw,remount -t auto /system
but in pixel 3 with magisk 18 or 19, I always fail to remount /vendor
blueline:/ # mount -o rw,remount -t auto /vendor
mount: '/dev/block/dm-1'->'/vendor': I/O error
I need to modify some file under/vendor/etc
I've disable Preserve AVB 2.0/dm-verity and Preserve forceencryption in advanced Settings from Magisk, unfortunately do no avail,
any idea is appreciated

misslebulletttttt said:
Hi everyone,
in pixel 2, I can get super su for adb shell, and can remount the system, /vendor partition
mount -o rw,remount -t auto /vendor
mount -o rw,remount -t auto /system
but in pixel 3 with magisk 18 or 19, I always fail to remount /vendor
blueline:/ # mount -o rw,remount -t auto /vendor
mount: '/dev/block/dm-1'->'/vendor': I/O error
I need to modify some file under/vendor/etc
I've disable Preserve AVB 2.0/dm-verity and Preserve forceencryption in advanced Settings from Magisk, unfortunately do no avail,
any idea is appreciated
Click to expand...
Click to collapse
This isn't working for me either. Tried with TWRP and regular module install. My changes to files on /vendor/etc just get overwritten. On magisk 18 and Pie.

If there's a Magisk mask active (modules magic mounting files) you might have issues if you want to do something other than systemless modifications.
The real partitions are found in /sbin/.magisk/mirror, you can try editing that. Or, editing in recovery (TWRP) should always work, since Magisk isn't active then.

loserinru said:
This isn't working for me either. Tried with TWRP and regular module install. My changes to files on /vendor/etc just get overwritten. On magisk 18 and Pie.
Click to expand...
Click to collapse
so do I, want to move some file to /vendor/etc, adb push definitely not working, so copy to /sdcard,
mount -o rw,remount -t auto /vendor
cp /sdcard/XXX /vendor,
however
mount -o rw,remount -t auto /vendor
always show mount: '/dev/block/dm-1'->'/vendor': I/O error,
tried with the movement in TWRP, but after booting into system, it's gone,
any other method to overcome ?

Didgeridoohan said:
If there's a Magisk mask active (modules magic mounting files) you might have issues if you want to do something other than systemless modifications.
The real partitions are found in /sbin/.magisk/mirror, you can try editing that. Or, editing in recovery (TWRP) should always work, since Magisk isn't active then.
Click to expand...
Click to collapse
Hi, I've copied the new file to sdcard, boot into TWRP, in TWRP do the file movement from sdcard to /vendor/etc with success, however, every time after booting into system, the modification is gone, same as the guy replied in the second thread,
any method for the movement is pretty appreciated

Magisk is not active in TWRP, so there's something else going on... Check /sbin/.magisk/mirror/vendor/etc if the modification is there, and take a look at the Magisk log (you'll need the Canary debug build for more verbose logging) if anything shows there.

Didgeridoohan said:
Magisk is not active in TWRP, so there's something else going on... Check /sbin/.magisk/mirror/vendor/etc if the modification is there, and take a look at the Magisk log (you'll need the Canary debug build for more verbose logging) if anything shows there.
Click to expand...
Click to collapse
I solved this by modifying the install script of Magisk,
if [ -z $KEEPVERITY ]; then
if $SYSTEM_ROOT; then
- KEEPVERITY=true
+ KEEPVERITY=false
ui_print "- System-as-root, keep dm/avb-verity"
else
KEEPVERITY=false
fi
fi
and install Magisk again in TWRP
this can help to disable dm-verity completely, now I can remount /vendor without I/O error

Didgeridoohan said:
If there's a Magisk mask active (modules magic mounting files) you might have issues if you want to do something other than systemless modifications.
The real partitions are found in /sbin/.magisk/mirror, you can try editing that. Or, editing in recovery (TWRP) should always work, since Magisk isn't active then.
Click to expand...
Click to collapse
Riiii I always do system edits threw twrp instead of Un mounting modules like viper and air audio plug-in and do systemless system edits threw the OS
Sent from my SM-J327P using Tapatalk