Some of build.prop adb commands, some of them have no real visible effects, but worth the try.
Perquisite:
1)Rooted
2) PC with ADB and fastboot
3)ADB debug enabled in phone
4) patience
Run in cmd , each line at a time.
adb shell su -c setprop persist.dbg.volte_avail_ovr 1
adb shell su -c setprop persist.dbg.vt_avail_ovr 1
adb shell su -c setprop persist.dbg.wfc_avail_ovr 1
adb shell su -c setprop persist.dbg.ims_volte_enable 1
adb shell su -c setprop persist.dbg.radio.rat_on 1
adb shell su -c setprop persist.radio.rat_on combine
adb shell su -c setprop persist.dbg.radio.data_ltd_sys_ind 1
adb shell su -c setprop persist.dbg.radio.data_con_rprt 1
adb shell su -c setprop persist.dbg.radio.calls.on.ims 1
adb shell su -c setprop persist.dbg.audio.fluence.voicerec 1
adb shell su -c setprop persist.dbg.audio.offload.passthrough 1
adb shell su -c setprop persist.dbg.audio.feature.anc_headset.enable 1
adb shell su -c setprop persist.dbg.audio.feature.hifi_audio.enable 1
adb shell su -c setprop persist.dbg.audio.feature.maxx_audio.enable 1
adb shell su -c setprop persist.dbg.audio.feature.wsa.enable 1
adb shell su -c setprop persist.dbg.audio.feature.audiozoom.enable 1
adb shell su -c setprop persist.dbg.surface_flinger.use_content_detection_for_refresh_rate 1
adb shell su -c setprop persist.dbg.audio.dolby.ds2.enabled 1
adb shell su -c setprop persist.dbg.audio.dolby.ds2.hardbypass 1
adb shell su -c setprop persist.dbg.audio.offload.multiple.enabled 1
adb shell su -c setprop persist.dbg.audio.offload.passthrough 1
adb shell su -c setprop persist.dbg.audio.safx.pbe.enabled 1
adb shell su -c setprop persist.dbg.audio.feature.ext_hw_plugin.enable 1
adb shell su -c setprop persist.dbg.audio.feature.record_play_concurency.enable 1
adb shell su -c setprop persist.dbg.enable_async_powermode 1
adb shell su -c setprop persist.dbg.display.use_smooth_motion 1
Related
Hi all, I have a problem with my Samsung I9300. When I press the off button does not show the menu (shutdown, restart, airplane mode) and power off directly. How I can recover it?
Thank you very much.
Certainly not enough I fo to go off of to help with you problem. Rooted or not rooted? What rom you running? Did u flash any mods or theme from other rom? This is the development section only. This belongs in Q & A my friend. Little more info would be helpful. It's to early to guess
Sent from my SPH-L710 using Tapatalk 2
reverepats said:
Certainly not enough I fo to go off of to help with you problem. Rooted or not rooted? What rom you running? Did u flash any mods or theme from other rom? This is the development section only. This belongs in Q & A my friend. Little more info would be helpful. It's to early to guess
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Hello friend, thanks for answering so fast. The problem begins when the phone unlock and repair IMEI Octopusbox. I have version 4.0.4.
Greetings.
Solution:
Hello
easy to fix posted by me in other section.
root your phone.
and use this commands FOR I9300 only
Quote:
adb shell "rm /efs/FactoryApp/keystr"
adb shell "rm /efs/FactoryApp/factorymode"
adb shell "echo -n ON >> /efs/FactoryApp/keystr"
adb shell "echo -n ON >> /efs/FactoryApp/factorymode"
adb shell "chown 1000.1000 /efs/FactoryApp/keystr"
adb shell "chown 1000.1000 /efs/FactoryApp/factorymode"
adb shell "chmod 0744 /efs/FactoryApp/keystr"
adb shell "chmod 0744 /efs/FactoryApp/factorymode"
or if you have secureroot then
Quote:
adb shell su -c "rm /efs/FactoryApp/keystr"
adb shell su -c "rm /efs/FactoryApp/factorymode"
adb shell su -c "echo -n ON >> /efs/FactoryApp/keystr"
adb shell su -c "echo -n ON >> /efs/FactoryApp/factorymode"
adb shell su -c "chown 1000.1000 /efs/FactoryApp/keystr"
adb shell su -c "chown 1000.1000 /efs/FactoryApp/factorymode"
adb shell su -c "chmod 0744 /efs/FactoryApp/keystr"
adb shell su -c "chmod 0744 /efs/FactoryApp/factorymode"
for i9100 /efs/imei/keystr
Regards,
Chevli
Before 4.0 and 4.0
* Need IT's Rooted Device *
1. adb shell su -c "mount"
2. adb shell su -c "cat /proc/mtd
Now show list of your system img where stay
example : boot.img = /dev/block/mtdblock7
so you can pull out from there .. here ..
3. adb shell su -c "chmod 777 /dev/block/mtdblock7"
4. adb shell su -c "dd if=/dev/block/mtdblock7 of=/storage/sdcard0/boot.img"
(of=/storage/sdcard0/ .. this location may b change you can look at "mount" )
-----------------------------------------------------------------------------------------
After 4.1 or mmc
1. adb shell su -c "mount"
2. adb shell su -c "cat /cache/recovery/last_log"
Now show list of your system img where stay
example : boot.img = /dev/block/mmcblk0p7"
so you can pull out from there .. here ..
3. adb shell su -c "chmod 777 /dev/block/mmcblk0p7"
4. adb shell su -c "dd if=/dev/block/mtdblock7 of=/storage/sdcard0/boot.img"
(of=/storage/sdcard0/ .. this location may b change you can look at "mount" )
For someone dont' know
thanks all ...
I can't find any info on whether or not it's imperative , or possible to back up efs on this device. I typically always back them up when I am rooted bc it's my biggest fear in somehow getting corrupted or lost, and not having anyway to restore. There doesn't seem to be a topic anywhere on These boards (DNA) so I'm thinking it's either impossible to lose or very easy to restore lol. Anyone know for Sure ?
adb shell su -c "cat /proc/partitions"
adb shell su -c "cat /proc/emmc"
adb shell su -c "mkdir /sdcard/img"
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/mmcblk0p18 of=/sdcard/img/radio_config.img"
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/mmcblk0p22 of=/sdcard/img/modem_st1.img"
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/mmcblk0p23 of=/sdcard/img/modem_st2.img"
mkdir efsbak
adb pull -p /sdcard/img/radio_config.img .\efsbak
adb pull -p /sdcard/img/modem_st1.img .\efsbak
adb pull -p /sdcard/img/modem_st2.img .\efsbak
I have a question here. Recently the LG G PRO 2 android handphone received OTA update. If I let the OTA run. After OTA updated, if I still want to re-install Philz Touch Recovery, is that mean the latest newer file provided by OTA update will be overwrite when I re-install the recovery that released 1 yr ago?
Below is the command that will install the files if I re-install the recovery. I dont know if these file important or not if replaced by recovery installation. I have no idea the purpose of these files. Please advice.
What I hope is to make sure latest stable file running on my phone.
adb shell su -c "dd if=/sdcard/img/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
adb shell su -c "dd if=/sdcard/img/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot"
adb shell su -c "dd if=/sdcard/img/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot"
adb shell su -c "dd if=/sdcard/img/dbi.img of=/dev/block/platform/msm_sdcc.1/by-name/dbi"
adb shell su -c "dd if=/sdcard/img/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf"
adb shell su -c "dd if=/sdcard/img/persist.img of=/dev/block/platform/msm_sdcc.1/by-name/persist"
adb shell su -c "dd if=/sdcard/img/rpm.img of=/dev/block/platform/msm_sdcc.1/by-name/rpm"
adb shell su -c "dd if=/sdcard/img/sbl1.img of=/dev/block/platform/msm_sdcc.1/by-name/sbl1"
adb shell su -c "dd if=/sdcard/img/tz.img of=/dev/block/platform/msm_sdcc.1/by-name/tz"
adb shell su -c "dd if=/sdcard/img/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem"
i cant install su in system i test all many option and still cant please tell me
stargam said:
i cant install su in system i test all many option and still cant please tell me
Click to expand...
Click to collapse
Try this
Code:
adb devices
adb disable-verity
adb reboot
adb devices
adb shell "mkdir -p /data/local/tmp > 2/dev/null"
adb push c:\su /data/local/tmp > nul
adb shell "chmod 0777 /data/local/tmp/su"
adb shell "-c '/data/local/tmp/su'"
adb shell "setenforce 0"
adb shell "cd /"
adb shell "mount -o rw,remount -t auto /system"
adb shell "cp /data/local/tmp/su /system/bin"
adb shell "mount -o ro,remount -t auto /system"
adb reboot
adb devices
adb enable-verity
adb reboot
Ok I try
jwoegerbauer said:
Try this
Click to expand...
Click to collapse
When I test adb "mkdir-p/data/local/tmp>2/dev/null" he say no such file or directory
stargam said:
When I test adb "mkdir-p/data/local/tmp>2/dev/null" he say no such file or directory
Click to expand...
Click to collapse
1. I think you forgot to type a simple "space" between Command: "mkdir -p" and Dirname: "data/local/tmp > 2 /dev/null"
2. And the last part "> 2 /dev/null" means redirect stdout (or error stream) and ignore it.
Conclusion, maybe just a typo? or err. mssge isn't what you think --> redirection made it dissappear.
Hopefully this works...
otherwise use this code:
adb devices
adb shell "mkdir -p /data/local/tmp" 2>nul >nul
adb shell "chmod 0755 /data/local/tmp"
adb push C:\su /data/local/tmp > nul
adb shell "chmod 0777 /data/local/tmp/su"
adb shell "/data/local/tmp/su -c 'cd / && mount -o rw,remount -t auto /system'"
adb shell "cp /data/local/tmp/su /system/bin"
adb shell "/data/local/tmp/su -c 'setprop ro.build.type user-debug'"
adb reboot
Click to expand...
Click to collapse
Cheerz!
webbex said:
1. I think you forgot to type a simple "space" between Command: "mkdir -p" and Dirname: "data/local/tmp > 2 /dev/null"
2. And the last part "> 2 /dev/null" means redirect stdout (or error stream) and ignore it.
Conclusion, maybe just a typo? or err. mssge isn't what you think --> redirection made it dissappear.
Hopefully this works...
otherwise use this code:
Cheerz!
Click to expand...
Click to collapse
Thanks it work ?