I have a Samsung Galaxy S6, model number SM-920F, provider T-mobile Netherlands,.
My phone is stuck in a bootloop but TWRP is still accessable, and I want to know the build number so I can download the right firmware and use Odin to put back to stock firmware.
Bdazzled said:
I have a Samsung Galaxy S6, model number SM-920F, provider T-mobile Netherlands,.
My phone is stuck in a bootloop but TWRP is still accessable, and I want to know the build number so I can download the right firmware and use Odin to put back to stock firmware.
Click to expand...
Click to collapse
First of all, I assume that you're using TWRP 3.0 or above
Boot into TWRP, go to Mount, check System, go back to TWRP's main menu, go to Advanced > Terminal and type this line in it:
Code:
cat /system/build.prop
And press Enter when you typed that line in Terminal
(Scroll around, and you'll see some lines
starting with G920F (Copy one of these, because that's your build number)
Sent from my Pixel XL using Tapatalk
DodoGTA said:
First of all, I assume that you're using TWRP 3.0 or above
Boot into TWRP, go to Mount, check System, go back to TWRP's main menu, go to Advanced > Terminal and type this line in it:
Code:
cat /system/build.prop
And press Enter when you typed that line in Terminal
(Scroll around, and you'll see some lines
starting with G920F (Copy one of these, because that's your build number)
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Thank you, I found it.
Bdazzled said:
Thank you, I found it.
Click to expand...
Click to collapse
Glad that it worked ?
Sent from my Pixel XL using Tapatalk
Same problem but with an Honor 9 (STL-AL09):crying:
---------- Post added at 06:02 PM ---------- Previous post was at 05:41 PM ----------
DodoGTA said:
First of all, I assume that you're using TWRP 3.0 or above
Boot into TWRP, go to Mount, check System, go back to TWRP's main menu, go to Advanced > Terminal and type this line in it:
Code:
cat /system/build.prop
And press Enter when you typed that line in Terminal
(Scroll around, and you'll see some lines
starting with G920F (Copy one of these, because that's your build number)
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I did it and it worked:good: but I can't find the build number. Can you help me ?
Please.
jacquesallet said:
Quote removed to prevent spam
Click to expand...
Click to collapse
That method only works on Samsung phones on stock ROMs or on non-stock ROMs with stock build fingerprint (aka ro.build.fingerprint property in build.prop)
So how can I find my build number? Please.
PS: when I do the manipulation, I can see:
"MacBook-Pro-de-Jacques:~ jacquesallet$ adb shell cat /system/build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NRD90M
ro.build.version.incremental=eng.jslave.20170604.040710
ro.build.version.sdk=24
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.0
ro.build.version.security_patch=2017-05-05
ro.build.version.base_os=
ro.build.date=Sun Jun 4 04:07:10 CST 2017
ro.build.date.utc=1496520430
ro.build.type=user
ro.build.user=jslave
ro.build.host=LFG1000749994
ro.build.tags=test-keys
ro.build.flavor=generic_a15-user
ro.product.model=generic_a15
ro.product.brand=Huawei
ro.product.name=generic_a15
ro.product.device=generic_a15
ro.product.board=
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=unknown
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=generic_a15
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=generic_a15-user 7.0 NRD90M eng.jslave.20170604.040710 test-keys
ro.build.fingerprint=Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave06040407:user/test-keys
ro.build.characteristics=default
# end build properties
# begin huawei emui properties
# autogenerated by build_emui_info.sh
ro.build.hw_emui_api_level=13
# end huawei emui properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.carrier=unknown
ro.setupwizard.require_network=any
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=7.0_r5
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=generic
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a15
dalvik.vm.isa.arm.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.display.id=System 5.1.0.78(055I)
ro.comp.sys_support_vndk=VA7.0-E5.0-B00005
ro.comp.sys_need_sndk=SA7.0-E5.0-B00005
MacBook-Pro-de-Jacques:~ jacquesallet$"
"ro.build.fingerprint=Huawei/generic_a15/generic_a15:7.0/NRD90M/jslave06040407:user/test-keys"
So it works isn't it?
Related
Well ever since i started flashing different roms, i keep losing service out of no where, and while it says i have service the 3G cuts on and off by its self. help??
theboo7 said:
Well ever since i started flashing different roms, i keep losing service out of no where, and while it says i have service the 3G cuts on and off by its self. help??
Click to expand...
Click to collapse
Can you state what roms you have been switching/running?
Framework43 said:
Can you state what roms you have been switching/running?
Click to expand...
Click to collapse
CynageonEris
White Widow 3.1/4.1B
Evil Eris 2.01
Ic3
theboo7 said:
CynageonEris
White Widow 3.1/4.1B
Evil Eris 2.01
Ic3
Click to expand...
Click to collapse
Have you wiped for each one?
The problem probably has to do with the build.prop
Framework43 said:
Have you wiped for each one?
The problem probably has to do with the build.prop
Click to expand...
Click to collapse
yes both factory and dalvik
theboo7 said:
yes both factory and dalvik
Click to expand...
Click to collapse
So you don't have service right now?
do
adb shell cat /system/build.prop
and see what you get
and also, try reboot
Framework43 said:
So you don't have service right now?
do
adb shell cat /system/build.prop
and see what you get
and also, try reboot
Click to expand...
Click to collapse
okay i tried reboot.lol
and i will try the other option in a minute
Framework43 said:
So you don't have service right now?
do
adb shell cat /system/build.prop
and see what you get
and also, try reboot
Click to expand...
Click to collapse
C:\android\tools>adb shell cat /system/build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=EPE54B
ro.build.display.id=WhiteWidow
ro.build.version.incremental=eng.ameer.20100522.120820
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Sat May 22 12:08:53 CDT 2010
ro.build.date.utc=1274548133
ro.build.type=eng
ro.build.user=ameer
ro.build.host=darchstar
ro.build.tags=test-keys
ro.product.model=Eris
ro.product.brand=htc
ro.product.name=opal
ro.product.device=sapphire
ro.product.board=droid
ro.product.cpu.abi=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=desirec
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=Cyanogenmod by Andrizoid
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:use
r/release-keys
# end build properties
#
# system.prop for dream_sapphire
#
ro.sf.lcd_density=160
rild.libpath=/system/lib/libhtc_ril.so
# Default network type.
ro.telephony.default_network=4
#ro.cdma.home.operator.numeric=310120
#ro.cdma.home.operator.alpha=Verizon
#ro.cdma.homesystem=128,64
#ro.cdma.data_retry_config=default_randomization=960000,960000,960000,960000,960
000
ro.cdma.home.operator.numeric = 310012
ro.cdma.home.operator.alpha = Verizon
gsm.sim.operator.numeric = 0
gsm.sim.operator.alpha = 0
gsm.sim.operator.iso-country = 0
wifi.interface=tiwlan0
wifi.supplicant_scan_interval=15
# RIL settings
ro.ril.gprsclass=10
ro.ril.hsxpa=1
# Media settings
ro.media.enc.file.format = 3gp,mp4
ro.media.enc.vid.codec = m4v,h263
ro.media.enc.vid.h263.width = 176,352
ro.media.enc.vid.h263.height = 144,288
ro.media.enc.vid.h263.bps = 64000,800000
ro.media.enc.vid.h263.fps = 1,30
ro.media.enc.vid.m4v.width = 176,352
ro.media.enc.vid.m4v.height = 144,288
ro.media.enc.vid.m4v.bps = 64000,800000
ro.media.enc.vid.m4v.fps = 1,30
#
# ADDITIONAL_BUILD_PROPERTIES
#
#ro.rommanager.developerid=cyanogenmod
ro.modversion=Cyanogenmod-Andrizoid
ro.config.ringtone=DonMessWivIt.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/
privacy.html
ro.com.google.clientidbase=android-google
keyguard.no_require_sim=true
net.bt.name=Android
ro.com.google.locationfeatures=1
ro.com.google.gmsversion=2.1_r1
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.execution-mode=int:jit
ro.media.dec.aud.wma.enabled=0
ro.media.dec.vid.wmv.enabled=0
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
C:\android\tools>
Lower the case in "Verzion"
Change it from Verizon to verizon.
Framework43 said:
Lower the case in "Verzion"
Change it from Verizon to verizon.
Click to expand...
Click to collapse
what do you mean, and how do i do this?
ill do it and put out a patch. thank you for your round-about help Framework, maybe your not such a bad guy afterall
theboo7 said:
what do you mean, and how do i do this?
Click to expand...
Click to collapse
He means pull the file off your phone:
adb pull /system/build.prop c:/path/to/where/file/will/go (best to pull it straight to your SDK/tools directory)
and then change the "Verizon" tag near the bottom to "verizon" (with lowercase V)
and then push the file back on your phone:
adb remount
adb push build.prop /system
(make sure the edited build.prop file is in your sdk/tools directory)
n1ghtwish said:
He means pull the file off your phone:
adb pull /system/build.prop c:/path/to/where/file/will/go (best to pull it straight to your SDK/tools directory)
and then change the "Verizon" tag near the bottom to "verizon" (with lowercase V)
and then push the file back on your phone:
adb remount
adb push build.prop /system
(make sure the edited build.prop file is in your sdk/tools directory)
Click to expand...
Click to collapse
did this and yet still keeps acting up
Hello everyone,
I was using VeganTab as my ROM of choice for a long time, and recently switched to CyanogenMod7 for a change and a more traditional Android feel.
With VeganTab, I had no issues using the Market. Every app I wanted to download was available in the market. Using CyanogenMod7, when I go to download apps I get a "this application is not available for your device" message on several apps. Firefox being one of them, which the gTablet should be able to support.
Why would one ROM work and the other doesn't on the same device? Has anyone else encountered this and know how to fix it?
Hello, I have one Gtab running CM7 what version/build are you on? Which apps are not showing up other than Firefox? Have you modified anything (build.prop)? If I remember right I had to modify the build.prop to get some apps to show up.
The apps in the market are set up to show only to devices that they are designed to be run on. When you change roms, your device shows up differently to the Market, so some apps might appear that weren't there before and some may dissappear. Read through the thread where you got the rom from and you may find some tips. Also as a temp. solution you can download the .apk files for many apps either to your PC or the the tablet and "side load" it (go to file manager and tap the downloaded .apk to install). Open a root file explorer and go to /system and open build.prop. Let me know what is says for product board, region and lcd density.
Thanks for the quick response Dave.
So far, Agenda Widget and Firefox are the two I can't get through the market. I haven't tried a ton of others yet.
I've been playing with the bool.prop file a little bit, based on tutorials I've seen here and at other forums. This thread seems to offer the best advice, but didn't work for me.
Below are my build.prop values at current time:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GRI40
ro.build.display.id=GRI40
ro.build.version.incremental=eng.cyanogenmod.20110505.210139
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.3
ro.build.date=Thu May 5 21:02:03 CDT 2011
ro.build.date.utc=0
ro.build.type=user
ro.build.user=cyanogenmod
ro.build.host=scout73
ro.build.tags=test-keys
ro.product.model=GTablet
ro.product.brand=passion
#ro.product.brand=nvidia
ro.product.name=passion
#ro.product.name=harmony
ro.product.device=olympus
#ro.product.device=harmony
ro.product.board=harmony
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=malata
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=harmony
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=passion-user 2.3.3 GRI40 102588 release-keys
ro.build.fingerprint=nvidia/harmony/harmony/harmony:2.2/FRF91/20101123.172729:eng/test-keys
# end build properties
#
# system.prop for harmony
#
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
# Density set to 161 to allow market to function properly
ro.sf.lcd_density=161
wifi.interface = wlan0
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval = 45
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# This is a high density device with more memory, so larger vm heaps for it.
dalvik.vm.heapsize=32m
# For emmc phone storage
ro.phone_storage = 1
# Add external mount points
ro.additionalmounts=/mnt/emmc;/mnt/usbdisk
# Add reference RIL
rild.libpath=/system/lib/libreference-ril.so
rild.libargs=-d /dev/ttyS0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.setupwizard.enable_bypass=1
keyguard.no_require_sim=1
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.0.3-Harmony
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Looks from your build.prop file that you are on an older build of CM7. The apps you mentioned, Firefox and Firefox Beta, and the Agenda Widget show up and work on mine. You could try using some of the values in my .prop file here, or update to a newer version of CM7. You might be able to install over your current build without wiping your data, but back up first of course.
Thanks Dave. Can you link me to a stable, updated version of CM7?
There is a CM7 rom hosted here at XDA:
CYANOGENMOD7.2.0-RC0-BUILD98-REPACK
Or you can go to Cyanogenmod Wiki. Don't forget to download the Gapps separately from the bottom of the same page and install them too.
I apologize in advance if it is not allowed to post a link to their wiki page .
Actually I have had this problem ALOT, no matter what version of CM7 I use on it. Its even worse when the new Market gets pushed to it, I usually have to downgrade it back and remove the MarketUpdater.apk so it stays on the old one.
I am running the ICS Alpha/Beta (forget which) right now so everything works, albeit very slow.
I had the same issue it's the odd LCD density of 161 that market doesn't like. I changed mine to 200 then do the standard market fix reboot and it should be fine.
Sent from my HTC Glacier using xda premium
Hello people, as i dig into some information about phone build prop settings and the samsung framework i found some interesting info
https://zapek.com/blog/how-to-make-your-galaxy-note-4-fast-again/
this guide is for the note 4, but works wonders on our galaxy alpha
basically it disables agressive samsung ram management, and uses the one closer do AOSP, it made my phone better, you guys can try you just need root and a build prop editor!
only works on stock samsung roms and maybe stock based roms!
Thanks man I will try it
Hi I can't find a line sys.config.samp_spcm_enable=
martinforester said:
Hi I can't find a line sys.config.samp_spcm_enable=
Click to expand...
Click to collapse
Which rom do you use?
because I found it in stock rom.
I have stock 5.0.2 oryginal rom
martinforester said:
I have stock 5.0.2 oryginal rom
Click to expand...
Click to collapse
in the #SAMP_SPCM line
victoram said:
Hello people, as i dig into some information about phone build prop settings and the samsung framework i found some interesting info
https://zapek.com/blog/how-to-make-your-galaxy-note-4-fast-again/
this guide is for the note 4, but works wonders on our galaxy alpha
basically it disables agressive samsung ram management, and uses the one closer do AOSP, it made my phone better, you guys can try you just need root and a build prop editor!
only works on stock samsung roms and maybe stock based roms!
Click to expand...
Click to collapse
Hi, can you give step by step instructions on how to do this? Thanks!
victoram said:
Hello people, as i dig into some information about phone build prop settings and the samsung framework i found some interesting info
https://zapek.com/blog/how-to-make-your-galaxy-note-4-fast-again/
this guide is for the note 4, but works wonders on our galaxy alpha
basically it disables agressive samsung ram management, and uses the one closer do AOSP, it made my phone better, you guys can try you just need root and a build prop editor!
only works on stock samsung roms and maybe stock based roms!
Click to expand...
Click to collapse
Will this only work for LL 5.x.x? I have KK 4.4.4 and can't find any of these files. Thanks.
I applied this and it works , Less Heat and Phone feels mutch more responsive and snappier .
Thanks for sharing !
cqdiep said:
Will this only work for LL 5.x.x? I have KK 4.4.4 and can't find any of these files. Thanks.
Click to expand...
Click to collapse
i think it is only on lolipop based touch wiz
victoram said:
i think it is only on lolipop based touch wiz
Click to expand...
Click to collapse
Makes sense, I should have read the title more carefully. I'm running KK without any problems.
I don't think so, I have Lollipop and I don't have any of these lines
martinforester said:
I don't think so, I have Lollipop and I don't have any of these lines
Click to expand...
Click to collapse
you shouldd only have this line: "sys.config.samp_spcm_enable=true" change it to false
=====> sys.config.samp_spcm_enable=false
you have to add these 3 manually.
sys.config.samp_enable=false
ro.config.fha_enable=true
ro.sys.fw.use_trim_settings=false
I don't have this line
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LRX22G
ro.build.display.id=LRX22G.G850FXXU2COI3
ro.build.version.incremental=G850FXXU2COI3
ro.build.version.sdk=21
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.0.2
ro.build.date=Fri Sep 11 19:17:32 KST 2015
ro.build.date.utc=1441966652
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWHD7522
ro.build.tags=release-keys
ro.product.model=SM-G850F
ro.product.brand=samsung
ro.product.name=sltexx
ro.product.device=slte
ro.product.board=universal5430
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos5
# ro.build.product is obsolete; use ro.product.device
ro.build.product=slte
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=sltexx-user 5.0.2 LRX22G G850FXXU2COI3 release-keys
ro.build.fingerprint=samsung/sltexx/slte:5.0.2/LRX22G/G850FXXU2COI3:user/release-keys
ro.build.characteristics=phone
# Samsung Specific Properties
ro.build.PDA=G850FXXU2COI3
ro.build.hidden_ver=G850FXXU2COI3
ro.config.rm_preload_enabled=0
ro.build.changelist=5614954
ro.product_ship=true
ro.chipname=exynos5430
persist.sys.storage_preload=1
# end build properties
#
# HWUI_BUILD_PROPERTIES
#
ro.hwui.texture_cache_size=24
ro.hwui.layer_cache_size=16
ro.hwui.path_cache_size=4
ro.hwui.shape_cache_size=1
ro.hwui.gradient_cache_size=0.5
ro.hwui.drop_shadow_cache_size=2
ro.hwui.r_buffer_cache_size=2
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=512
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
#
# from device/samsung/slte/system.prop
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
#
# system.prop for universal5430
#
# LCD Density
ro.sf.lcd_density=320
ro.arch=exynos5430
ro.kernel.qemu.gles=1
persist.demo.hdmirotationlock=false
#DHA
ro.config.dha_cached_max=4
ro.config.dha_empty_init=24
ro.config.dha_empty_max=24
ro.config.dha_defendth_enable=false
ro.config.dha_th_rate=1.83
#LMK Tuning
ro.config.dha_lmk_scale=1.45
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.tima=1
ro.config.timaversion=3.0
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapmaxfree=4m
dalvik.vm.heapminfree=1m
dalvik.vm.heapsize=384m
dalvik.vm.heapstartsize=8m
dalvik.vm.heaptargetutilization=0.75
ro.opengles.version=196608
ro.sf.lcd_density=480
debug.hwc.winupdate=1
debug.hwc.otf=1
ro.hdcp2.rx=tz
ro.secwvk=220
ro.securestorage.support=true
ro.build.scafe=americano
ro.build.scafe.size=short
ro.build.scafe.shot=single
ro.build.scafe.cream=white
security.mdpp=None
ro.security.mdpp.ver=1.1
ro.security.mdpp.release=5
ro.security.vpnpp.ver=1.4
ro.security.vpnpp.release=4.1
security.mdpp.result=None
ro.security.mdpp.ux=Enabled
ro.security.reactive.triggered=false
ro.error.receiver.default=com.samsung.receiver.error
ro.config.ringtone=Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Morning_flower.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.security.reactive.active=1
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.security.icd.flagmode=single
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.0_r3
persist.sys.dalvik.vm.lib.2=libart.so
ro.build.selinux=1
dalvik.vm.isa.arm.features=div
ro.config.knox=v30
ro.kernel.qemu=0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.version.sdl=2101
martinforester said:
I don't have this line sys.config.samp_spcm_enable=true
Click to expand...
Click to collapse
do you have the smart manager app?
I don't know what is it, I use "Root Browser" to browse files
martinforester said:
I don't know what is it, I use "Root Browser" to browse files
Click to expand...
Click to collapse
you probably don't have the smart manager app, it's an stock app from samsung, the line that you don't have is to disable that app from killing any tasks.
just add the 3 other lines and you should be fine.
I rooted my Alpha today and I would like to do this tweak, but I don't know how. I see the "sys.config.samp_spcm_enable=true" line in my build.prop. My question is where do I add these lines:
sys.config.samp_enable=false
ro.config.fha_enable=true
ro.sys.fw.use_trim_settings=false
Do I put them at the very bottom of the file or in the #SAMP_SPCM section where the other line is?
My first time having a rooted android so i'm a noob
Juusoavk said:
I rooted my Alpha today and I would like to do this tweak, but I don't know how. I see the "sys.config.samp_spcm_enable=true" line in my build.prop. My question is where do I add these lines:
sys.config.samp_enable=false
ro.config.fha_enable=true
ro.sys.fw.use_trim_settings=false
Do I put them at the very bottom of the file or in the #SAMP_SPCM section where the other line is?
My first time having a rooted android so i'm a noob
Click to expand...
Click to collapse
The first line you can add to #spcm as well, I think.
The second and the third lines can be added to
# ADDITIONAL_BUILD_PROPERTIES.
This is just below the #spcm section.
Note that I don't know that for sure, but I have just done it myself and it seems OK ).
Good luck mate )
Sent from my SM-G850F using Tapatalk
asetmumin99 said:
The first line you can add to #spcm as well, I think.
The second and the third lines can be added to
# ADDITIONAL_BUILD_PROPERTIES.
This is just below the #spcm section.
Note that I don't know that for sure, but I have just done it myself and it seems OK ).
Good luck mate )
Sent from my SM-G850F using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply! I already got it working few days after the post though.
Hi - so I am only posting as a last result and 4 days of stumbling around rooting, ROMs, and different devices I've finally reached a wall.
I have several LG Aristo 2's that I use on an ESX server for various development machines. They work terrific for what I have them for but the problem is I have particular phones for particular servers and I cannot pick one out of 8 devices because they are all named the same. For the past year or so I have kind of limped but now my environments are a bit more fluid and I need to be able to pick an offending perp out of the line up.
So I have been hacking around on a test phone for the past few days and have driven myself crazy trying to get the model number to change. I have tried several different ROMs, assuming this might be a problem but I just can't seem to change the model name that the devices connects over USB with.
I have updated the build.prop and changed model name, device name, and even added ro.mtp.label and ro.ptp.label.
About to give up thinking this is impossible I had a spare Blu Vivo sitting around and I went through the same process and have been successful in renaming the device doing the things in the line above.
Is this just not possible on the LG Aristo 2?
Android Version: 8.1.0
Model Number: LM-X210MA
Here is a section of my build.prop
Can anyone point me in the right direction? Beer money will be sent!
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=OPM1.171019.026
ro.build.display.id=OPM1.171019.026
ro.build.version.incremental=1832618554af2
ro.build.version.sdk=27
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=8.1.0
ro.build.version.security_patch=2018-11-01
ro.build.version.base_os=
ro.build.date=Thu Nov 22 18:55:26 KST 2018
ro.build.date.utc=1542880526
ro.build.type=user
ro.build.user=jenkins
ro.build.host=LGEACI6R1
ro.build.tags=release-keys
ro.build.flavor=cv1_lao_com-user
ro.build.ab_update=false
ro.product.model=HulkHappy
ro.product.brand=lge
ro.product.name=HulkHappy
ro.product.device=cv1
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=LGE
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=cv1
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=cv1_lao_com-user 8.1.0 OPM1.171019.026 1832618554af2 release-keys
ro.build.fingerprint=lge/cv1_lao_com/cv1:8.1.0/OPM1.171019.026/1832618554af2:user/release-keys
ro.build.characteristics=default
# end build properties
# begin build properties
# autogenerated by vendor_buildinfo.sh
ro.product.board=QC_Reference_Phone
ro.board.platform=msm8937
ro.vendor.product.manufacturer=LGE
ro.vendor.product.model=LM-X210
ro.vendor.product.brand=lge
ro.vendor.product.name=cv1_lao_com
ro.vendor.product.device=cv1
ro.ptp.label=HulkHappy
ro.mtp.label=HulkHappy
@WelpImStuck
Not sure it will solve your problem: you can programmatically change an Android device's name and its ID by means of ADB:
If OS is Android 7.1 and higher to change device's name
Code:
adb devices
adb shell settings put global <DEVICE_NAME>
If OS is Android 8 and higher to change device's ID
Code:
adb devices
adb shell settings put secure <ANDROID_ID>
@jwoegerbauer
Awesome, thank you for the information. I had been using a version of the first one and it did not get me as far along as what you just shared. So using
Code:
adb shell settings put secure global device_name "device name"
I have now at least been able to differentiate on the direct server what device is connected. In my ESX host it still shows the Model LG LM-X210G. I'd share some images but I guess my n00b status, rightly so, won't allow that.
But using my eyes:
ESX shows the USB device as: LG LM-X210G
Easy Tether shows the devices as: LMX210G1db3... (stripping the rest, but guessing its part of the serial)
Windows shows the device as: HulkHappy
... since HulkSmash destroyed the first phone I was trying this on.
Is there any where else I can look? My biggest desire is to get my ESX host in line.
jwoegerbauer said:
@WelpImStuck
Not sure it will solve your problem: you can programmatically change an Android device's name and its ID by means of ADB:
If OS is Android 7.1 and higher to change device's name
Code:
adb devices
adb shell settings put global <DEVICE_NAME>
If OS is Android 8 and higher to change device's ID
Code:
adb devices
adb shell settings put secure <ANDROID_ID>
Click to expand...
Click to collapse
Disclaimer : I don’t take any responsibility for any error/Damage/Losing data on your Xiaomi Redmi Note 9 Pro Max. If you are responsible for any mistakes, follow the flashing guide for the files. Some functions don’t operate properly and can cause serious damage to your Device.
Basic Pre-Requirements
- Enable USB Debugging on your Xiaomi Redmi Note 9 Pro Max
- Turn on the adb and fastboot.
- Unlock the bootloader of Xiaomi Redmi Note 9 Pro Max. : follow this from official MI website : External link of Official MI website
– Download and Manually Install Android USB Drivers on your PC
- Download TWRP (Unofficial) : Download
How to install TWRP on Xiaomi Redmi Note 9 Pro Max
First, Switch Off your Smartphone
Open your Mobile Fastboot
Using power off your Device and then hold the Volume Down + Power button
Now, Open the ADB folder on your PC and Laptop.
Then, Select the Address Bar in the ADB File
Type Cmd and hit the Enter button
Type the command in Cmd (Inside “Filename,” You can drag the file directly to the CMD instead of Typing.)
NOTE : Filename is the name of TWRP you downloaded above, replace the name with that.
adb Reboot Bootloader
Fastboot Devices
Fastboot Flash Recovery “TWRP filename.img” and Hit Enter
Then After Type “Fastboot reboot” and Hit Enter.
Congratulations, you have successfully installed the TWRP File on Xiaomi Redmi Note 9 Pro Max
How to Root Xiaomi Redmi Note 9 Pro Max
Download Magisk Zip and Download No verity opt encrypt.zip and Move to Mobile Storage
Then Switch your Phone
Turn On your at Recovery Mode (hold the Volume Down + Power button)
TWRP Recovery, Select INSTALL
Then Browse and Select the saved file of Magisk.Zip
Now Click Install Button
Finally, Reboot Your Device
Congratulations, you successfully Rooted your Device
supersu??
or is it magisk???
kindly correct
Then Browse and Select the saved file of SuperSU Zip
Click to expand...
Click to collapse
and i thought magisk canary build is required for android 10???
this recovery appears to be for 9s or 9 pro devices
look at the default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.actionable_compatible_property.enabled=false
ro.postinstall.fstab.prefix=/system
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
debug.atrace.tags.enableflags=0
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.usejit=true
dalvik.vm.usejitprofiles=true
dalvik.vm.dexopt.secondary=true
dalvik.vm.appimageformat=lz4
ro.dalvik.vm.native.bridge=0
pm.dexopt.first-boot=extract
pm.dexopt.boot=extract
pm.dexopt.install=speed-profile
pm.dexopt.bg-dexopt=speed-profile
pm.dexopt.ab-ota=speed-profile
pm.dexopt.inactive=verify
pm.dexopt.shared=speed
dalvik.vm.dex2oat-resolve-startup-strings=true
dalvik.vm.dex2oat-max-image-block-size=524288
dalvik.vm.minidebuginfo=true
dalvik.vm.dex2oat-minidebuginfo=true
ro.iorapd.enable=false
tombstoned.max_tombstone_count=50
persist.sys.usb.config=adb
#
# ADDITIONAL VENDOR DEFAULT PROPERTIES
#
ro.vndk.version=29
ro.vndk.lite=true
ro.zygote=zygote64_32
ro.logd.size.stats=64K
log.tag.stats_log=I
ro.bionic.arch=arm64
ro.bionic.cpu_variant=generic
ro.bionic.2nd_arch=arm
ro.bionic.2nd_cpu_variant=cortex-a9
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=generic
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a9
dalvik.vm.isa.arm.features=default
ro.minui.pixel_format=BGRA_8888
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Thu May 7 00:47:33 CST 2020
ro.system.build.date.utc=1588783653
ro.system.build.fingerprint=Redmi/curtana_global/curtana:10/QKQ1.191215.002/V11.0.7.0.QJWMIXM:user/release-keys
ro.system.build.id=QQ1D.200205.002
ro.system.build.tags=test-keys
ro.system.build.type=eng
ro.system.build.version.incremental=eng.wzsx15.20200507.004808
ro.system.build.version.release=10
ro.system.build.version.sdk=29
ro.product.system.brand=Redmi
ro.product.system.device=curtana
ro.product.system.manufacturer=Xiaomi
ro.product.system.model=Redmi Note 9S
ro.product.system.name=curtana
# end common build properties
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=QQ1D.200205.002
ro.build.display.id=omni_redmiNote9s-eng 10 QQ1D.200205.002 eng.wzsx15.20200507.004808 test-keys
ro.build.version.incremental=eng.wzsx15.20200507.004808
ro.build.version.sdk=29
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=10
ro.build.version.security_patch=2023-12-01
ro.omni.version.security_patch=2020-02-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=2020年 05月 07日 星期四 00:48:44 CST
ro.build.date.utc=1588783653
ro.build.type=eng
ro.build.user=wzsx150
ro.build.host=wzsx150-virtual-machine
ro.build.tags=test-keys
ro.build.flavor=omni_redmiNote9s-eng
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.locale=zh-CN
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=curtana
# Do not try to parse description or thumbprint
ro.build.description=curtana_global-user 10 QKQ1.191215.002 V11.0.7.0.QJWMIXM release-keys
ro.build.fingerprint=Redmi/curtana_global/curtana:10/QKQ1.191215.002/V11.0.7.0.QJWMIXM:user/release-keys
ro.omni.device=redmiNote9s
# end build properties
#
# from device/twrp/redmiNote9s/system.prop
#
#
#start system.prop
#
ro.secure=0
ro.adb.secure=0
ro.build.date.utc=1420041600
persist.sys.timezone=Asia/Shanghai
ro.sf.lcd_density=440
# for device
ro.treble.enabled=true
vendor.gatekeeper.disable_spu=true
ro.boot.init_rc=/init.rc
#end system.prop
#
# end of device/twrp/redmiNote9s/system.prop
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.bionic.ld.warning=1
ro.treble.enabled=true
persist.debug.dalvik.vm.core_platform_api_policy=just-warn
ro.kernel.android.checkjni=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.image-dex2oat-filter=verify-at-runtime
net.bt.name=Android
ro.boot.dynamic_partitions=true
ro.vendor.build.security_patch=2023-12-01
ro.vendor.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.vendor.product.cpu.abilist32=armeabi-v7a,armeabi
ro.vendor.product.cpu.abilist64=arm64-v8a
ro.product.board=curtana
ro.board.platform=atoll
ro.hwui.use_vulkan=
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.vendor.build.date=Thu May 7 00:47:33 CST 2020
ro.vendor.build.date.utc=1588783653
ro.vendor.build.fingerprint=Redmi/curtana_global/curtana:10/QKQ1.191215.002/V11.0.7.0.QJWMIXM:user/release-keys
ro.vendor.build.id=QQ1D.200205.002
ro.vendor.build.tags=test-keys
ro.vendor.build.type=eng
ro.vendor.build.version.incremental=eng.wzsx15.20200507.004808
ro.vendor.build.version.release=10
ro.vendor.build.version.sdk=29
ro.product.vendor.brand=Redmi
ro.product.vendor.device=curtana
ro.product.vendor.manufacturer=Xiaomi
ro.product.vendor.model=Redmi Note 9S
ro.product.vendor.name=curtana
# end common build properties
#
# BOOTIMAGE_BUILD_PROPERTIES
#
ro.bootimage.build.date=Thu May 7 00:47:33 CST 2020
ro.bootimage.build.date.utc=1588783653
ro.bootimage.build.fingerprint=Redmi/omni_redmiNote9s/redmiNote9s:10/QQ1D.200205.002/wzsx15005070047:eng/test-keys
#
# ADDITIONAL VENDOR BUILD PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.carrier=unknown
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.odm.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.odm.product.cpu.abilist32=armeabi-v7a,armeabi
ro.odm.product.cpu.abilist64=arm64-v8a
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.odm.build.date=Thu May 7 00:47:33 CST 2020
ro.odm.build.date.utc=1588783653
ro.odm.build.fingerprint=Redmi/curtana_global/curtana:10/QKQ1.191215.002/V11.0.7.0.QJWMIXM:user/release-keys
ro.odm.build.id=QQ1D.200205.002
ro.odm.build.tags=test-keys
ro.odm.build.type=eng
ro.odm.build.version.incremental=eng.wzsx15.20200507.004808
ro.odm.build.version.release=10
ro.odm.build.version.sdk=29
ro.product.odm.brand=Redmi
ro.product.odm.device=curtana
ro.product.odm.manufacturer=Xiaomi
ro.product.odm.model=Redmi Note 9S
ro.product.odm.name=curtana
# end common build properties
#
# ADDITIONAL ODM BUILD PROPERTIES
#
#
# ADDITIONAL PRODUCT PROPERTIES
#
ro.build.characteristics=default
ro.com.google.clientidbase=android-google
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.build.selinux=1
persist.sys.disable_rescue=true
ro.opa.eligible_device=true
net.tethering.noprovisioning=true
ro.control_privapp_permissions=enforce
ro.config.ringtone=omni_ringtone1.ogg,omni_ringtone1.ogg
ro.config.notification_sound=omni_notification1.ogg
ro.config.alarm_alert=omni_alarm1.ogg
ro.services.whitelist.packagelist=com.google.android.gms
ro.modversion=OmniROM-10-20200507-redmiNote9s-HOMEMADE
ro.omni.version=10-20200507-redmiNote9s-HOMEMADE
#
# RECOVERY UI BUILD PROPERTIES
#
Click to expand...
Click to collapse
the recovery is posted on https://unofficialtwrp.com/twrp-3-4-1-root-redmi-note-9-pro-max/ but is 9 pro recovery.
can OP confirm is this really works???
i.snehal.kiran said:
supersu??
or is it magisk???
kindly correct
this recovery appears to be for 9s or 9 pro devices
look at the default.prop
the recovery is posted on https://unofficialtwrp.com/twrp-3-4-1-root-redmi-note-9-pro-max/ but is 9 pro recovery.
can OP confirm is this really works???
Click to expand...
Click to collapse
It's for magisk, SuperSU refers to magisk we're installing.
Yes, it's not official TWRP, so it's not updated as desired but keeping in mind that both devices have same CPU, it's a workaround until real thing comes. (Official TWRP),, and yes it works,, tried myself and worked,.
i.snehal.kiran said:
the recovery is posted on https://unofficialtwrp.com/twrp-3-4-1-root-redmi-note-9-pro-max/ but is 9 pro recovery.
can OP confirm is this really works???
Click to expand...
Click to collapse
Have you tried that method in your link ?
coolvipcandy said:
Have you tried that method in your link ?
Click to expand...
Click to collapse
no i havent tried . my friend has pro max .
i am just searching for stable rooting method for him.
i will tell him to try your method then.
thanks
coolvipcandy said:
Disclaimer : I don’t take any responsibility for any error/Damage/Losing data on your Xiaomi Redmi Note 9 Pro Max. If you are responsible for any mistakes, follow the flashing guide for the files. Some functions don’t operate properly and can cause serious damage to your Device.
Basic Pre-Requirements
- Enable USB Debugging on your Xiaomi Redmi Note 9 Pro Max
- Turn on the adb and fastboot.
- Unlock the bootloader of Xiaomi Redmi Note 9 Pro Max. : follow this from official MI website : External link of Official MI website
– Download and Manually Install Android USB Drivers on your PC
- Download TWRP (Unofficial) : Download
How to install TWRP on Xiaomi Redmi Note 9 Pro Max
First, Switch Off your Smartphone
Open your Mobile Fastboot
Using power off your Device and then hold the Volume Down + Power button
Now, Open the ADB folder on your PC and Laptop.
Then, Select the Address Bar in the ADB File
Type Cmd and hit the Enter button
Type the command in Cmd (Inside “Filename,” You can drag the file directly to the CMD instead of Typing.)
NOTE : Filename is the name of TWRP you downloaded above, replace the name with that.
adb Reboot Bootloader
Fastboot Devices
Fastboot Flash Recovery “TWRP filename.img” and Hit Enter
Then After Type “Fastboot reboot” and Hit Enter.
Congratulations, you have successfully installed the TWRP File on Xiaomi Redmi Note 9 Pro Max
How to Root Xiaomi Redmi Note 9 Pro Max
Download Magisk Zip and Download No verity opt encrypt.zip and Move to Mobile Storage
Then Switch your Phone
Turn On your at Recovery Mode (hold the Volume Down + Power button)
TWRP Recovery, Select INSTALL
Then Browse and Select the saved file of SuperSU Zip
Now Click Install Button
Go again to install Button, then Browse and Install No verity opt encrypt.zip and confirm install
Finally, Reboot Your Device
Congratulations, you successfully Rooted your Device
Click to expand...
Click to collapse
what is the use of this file "No verity opt encrypt.zip"
i.snehal.kiran said:
supersu??
or is it magisk???
kindly correct
and i thought magisk canary build is required for android 10???
this recovery appears to be for 9s or 9 pro devices
look at the default.prop
the recovery is posted on https://unofficialtwrp.com/twrp-3-4-1-root-redmi-note-9-pro-max/ but is 9 pro recovery.
can OP confirm is this really works???
Click to expand...
Click to collapse
ayepandey said:
what is the use of this file "No verity opt encrypt.zip"
Click to expand...
Click to collapse
dm-verity helps prevent persistent rootkits that can hold onto root privileges and compromise devices.
No-verity helps here to suppress dm-verity.
Anyone rooted n installed custom recovery on pro max with miui 12? I tried last week and made a huge out of my phone.. bricked multiple times and finally went back to miui fastboot rom.. if anyone successfully done it, can you please give me the steps..
Is there an official TWRP for this set now?
Is the No verity opt encrypt.zip needed and if I have to use it, should it be flashed with TWRP? Is booting up safe without flashing No verity opt encrypt.zip? I'm thinking of buying this device.
Supermatt01 said:
Is the No verity opt encrypt.zip needed and if I have to use it, should it be flashed with TWRP? Is booting up safe without flashing No verity opt encrypt.zip? I'm thinking of buying this device
Click to expand...
Click to collapse
I use to flash No verity immediately after flashing TWRP on my Redmi Note 4 to avoid bootloop and brick. Don't know for Redmi Note 9.
How many of you rooted Redmi Note 9 Pro Max?
Please hit LIKE button (please be honest).
I badly want to buy it but I did not find many ppl rooted or successfully with Twrp.