• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help CANNOT USE MY DEVICE AFTER EDITING THE BUILD.PROP

Zenitsu

Zenitsu

Newbie
Hello to every one,

First of all, I'm sorry for my bad english.
My Samsung S5 Dou Android device is rooted and I was trying to edit the "build.prop" file in root directory and inside it, i edit the SDK Version which is from 19 into 23, then after I rebooted it, all the apps even the file manager i use to edit the file were stopped working so now I cannot edit or back the file into its original and i tried to format the device because I thought it would work to avoid the stopped working or the error were gone, but unfortunately its not working, it's still showing the popup :< My problem is, I cannot really use the phone because all the settings or apps are not working :< I tried to use drfone or other phone formatter but its still not working because its need to enable the USB Debugging and I cannot enable it because even the settings will stopped :< Anyone there know to fix my phone? :< This is my only phone givin' from my grandfather :< Thank you guys and sorry for this complain :< Thank you!
 
If so, you can try installing a custom rom for your device. Most of them require wiping system before flsshing the rom. In most cases that would allow you to boot into your OS with everything working as expected. Then you could enable "developer Options" and in thr settings allow usb debugging.
 
Last edited:
If you know the exact model you should be able too download the software from sammobile.com, install a Samsung app called Odin on your computer (I think Odin is the right one for a phone of that vintage, but I'm not a Samsung expert) and reflash the phone completely. It won't be rooted after that, but it will be working.

If you had a custom recovery then you should have made a backup of the phone before fiddling with the system - then you could have just restored that. If you don't have a custom recovery you should think very hard before messing with anything in the system. And I can't see how a "phone formatter" would help with this in any case.
 
Give me some time and I will paste here the image of my S5's build prop..it might work for you..better than nothing, right??

You have to be stubborn with it when trying to edit the build prop again..of course..you will have to clear those force to close maybe a couple of hundreds of times before you will be able to actually get into the build prop..

That happened to me some time a while back..
 
Using the Odin utility does not require USB Debugging to be enabled. USB Debugging is necessary when you're using something like ADB to be interacting with the installed OS but Odin isn't doing anything like that. Odin is a tool to flash firmware, it's installing software not exchanging data (a one-way connection as opposed to a two-way connection).

Anyway, as it sounds like your last option at this point is to install a stock Samsung ROM. This should at least restore your S5 Duo back to working condition. Keep in mind when you flash a stock ROM you're returning your phone to its previous, un-rooted state so you'll have to go through the rooting process again if that's what you want. Also, this will also install a stock Recovery.

Go here and download the appropriate ROM for your model of S5 Duo.
https://updato.com/firmware-archive-select-model/?q=SM-G900FD&exact=1&r=&v=&rpp=100
Your S5 Duo is probably a SM-900FD but that's just an assumption -- you have to determine what phone you have and what model I.D. it is. If that's not the correct identifier than just do a search for your model.
Be sure to select a ROM that matches your model exactly. ROMs are not interchangeable so do not use one that's 'similar'. It's also important to use a ROM that matches your country and your carrier. If you do select the incorrect ROM you might be lucky and just soft-brick your device (so just need to re-flash with the correct one) but if you're not lucky you could hard-brick it. In that case you might be able to use a jig to get your phone into Recovery or Download mode but you'll most likely need to just send it in to Samsung and pay to have them restore it.

Here are some instructions on the flashing process:
https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin/
Be sure to follow the directions carefully, don't experiment with the various settings.

If you need to install a Samsung driver on your WinPC:
https://developer.samsung.com/mobile/android-usb-driver.html

If you have a problem using the most recent version of the Odin utility, don't be too surprised. It often has issues when it comes to older hardware. You can get older versions of Odin here, try using one that's specified for the version of Android you'll be working with:
https://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
Also, if you're plugging your phone into a USB hub, try plugging it directly into a USB port on your PC, at least when you're doing this flashing process. And use a good USB cable, the cheaper ones with thinner insulation and thinner gauge wiring inside just don't work as well. USB cables are NOT all the same.

If you just don't have access to a Windows PC, try using Heimdall instead. It's an Open Source equivalent to Odin and available for Linux, Mac, and Windows.
Its menu isn't an exact duplicate as Odin but very similar so just be more flexible.
https://glassechidna.com.au/heimdall/
 
if you have a custom recovery and still have access to it then all is not lost. hopefully you have made a nandroid backup. if not then lets make this a lesson learned. if you have a custom recovery, but did not make a nandroid backup, then you can always flash a custom stock rom (if there is one, available. check out the forums in xda).

so i do not mean to preach, but this is how i go about rooting a device.
1. head on over to xda and check out if there is a community of developers that is supporting the device. i always say no devs=no fun
2. read up on the rooting process. not all devices are the same. and some devices are harder to root then others.
3. check to see if there is a custom recovery like twrp. a recovery is essential when rooting. it allows you to do many things one of them is performing a nandroid backup. if you go about messing with the os like you did, you can always restore back.
4. once you have a recovery then the very first thing to do is a nandroid backup.

if there is no dev community or if there is no custom recovery then i will find a different device to root, i will never root a device without a custom recovery.
 
Last edited:
MrJavi said:
If so, you can try installing a custom rom for your device. Most of them require wiping system before flsshing the rom. In most cases that would allow you to boot into your OS with everything working as expected. Then you could enable "developer Options" and in thr settings allow usb debugging.
Click to expand...
How could I install a custom rom? By using the "apply update from external storage" like that?
 
I would like to permanently remove the root and restart the phone into its original state. So for that, I should use the "Odin-Mode"?
Hadron said:
If you know the exact model you should be able too download the software from sammobile.com, install a Samsung app called Odin on your computer (I think Odin is the right one for a phone of that vintage, but I'm not a Samsung expert) and reflash the phone completely. It won't be rooted after that, but it will be working.

If you had a custom recovery then you should have made a backup of the phone before fiddling with the system - then you could have just restored that. If you don't have a custom recovery you should think very hard before messing with anything in the system. And I can't see how a "phone formatter" would help with this in any case.
Click to expand...
 
Xavier Black said:
Give me some time and I will paste here the image of my S5's build prop..it might work for you..better than nothing, right??

You have to be stubborn with it when trying to edit the build prop again..of course..you will have to clear those force to close maybe a couple of hundreds of times before you will be able to actually get into the build prop..

That happened to me some time a while back..
Click to expand...
Thank you in advanced! SAMSUNG GALAXY S5 4.4 SM-E500 I THINK, IS MY DEVICE.
 
Don't worry about whether USB Debugging is or isn't enabled, it is not a requirement to flash the ROM. If you read through various Odin instructional sites, none of them mention the need for USB Debugging:
https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin/

https://www.sammobile.com/forum/threads/14365-how-to-flash-a-stock-rom-with-odin-mobilecrackers

https://samsungodin.com/how-to-use-odin/

Again, USB Debugging is needed if you want to enable a USB connection between you device and an external one to exchange data and commands. That involves interactions with one operating system and another. With the Odin utility, you're not exchanging data with your phone's installed OS, you're installing a new OS. And basically, having USB Debugging always enabled is a security risk as it leaves an open connection, at a fairly deep level, that's typically closed:
https://www.howtogeek.com/258788/wh...nd-is-it-safe-to-leave-it-enabled-on-android/
There is the issue where in a lot of instances of a problem, having USB Debugging enabled can be really helpful so it's a matter of damned if you do, damned if you don't.
 
So with this..if it works the advantage is you don't have to reset your phone and you won't lose any tying..If you haven't reseted your phone here's what I promise, just add what's between the quotations and then delete them:


"# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=LRX21T
ro.build.display.id=LRX21T.G900PVPU3BOG1
ro.build.version.incremental=G900PVPU3BOG1
ro.build.version.sdk=21
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.0
ro.build.date=Thu Jul 30 15:39:53 KST 2015
ro.build.date.utc=1438238393
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWHD4420
ro.build.tags=release-keys
ro.product.model=SM-G900P
ro.product.brand=samsung
ro.product.name=kltespr
ro.product.device=kltespr
ro.product.board=MSM8974
# 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=US
ro.wifi.channels=
ro.board.platform=msm8974
# ro.build.product is obsolete; use ro.product.device
ro.build.product=kltespr
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=kltespr-user 5.0 LRX21T G900PVPU3BOG1 release-keys
ro.build.fingerprint=samsung/kltespr/kltespr:5.0/LRX21T/G900PVPU3BOG1:user/release-keys
ro.build.characteristics=chameleon
# Samsung Specific Properties
ro.build.PDA=G900PVPU3BOG1
ro.build.hidden_ver=G900PVPU3BOG1
ro.config.rm_preload_enabled=0
ro.build.changelist=4781399
ro.product_ship=true
ro.chipname=MSM8974PRO
persist.sys.storage_preload=1
# end build properties
#
# from device/samsung/kltespr/system.prop
#
#
# system.prop for msm8974
#

# LCD Density
ro.sf.lcd_density=480

# Evolution RIL (8xxx)
#
# Integrate the Kineto VOWIFI changes
#rild.libpath=/system/lib/libsec-ril.so
rild.libpath=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/libsec-ril.so
rilswitch.cfilibpath=/system/lib/libcfiril.so
# End of kineto change
#
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1

debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=c2d
persist.hwc.mdpcomp.enable=true
debug.mdpcomp.logs=0
dalvik.vm.heapsize=36m
dev.pm.dyn_samplingrate=1
persist.demo.hdmirotationlock=false

ro.hdmi.enable=true
persist.speaker.prot.enable=false
qcom.hw.aac.encoder=true
#
# system props for the cne module
#
#persist.cne.feature=1

#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
mm.enable.smoothstreaming=true
media.aac_51_output_enabled=true
#37491 is decimal sum of supported codecs in AAL
#codecs: AVI AC3 ASF AAC QCP DTS 3G2 MP2TS
mm.enable.qcom_parser=37491

# VIDC: debug_levels
# 1:ERROR 2:HIGH 4:LOW 0:NOLOGS 7:AllLOGS
vidc.debug.level=1
#
ro.data.large_tcp_window_size=true

# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608

# System property for cabl
ro.qualcomm.cabl=1

#
# System props for bluetooth
# System prop to turn on hfp client
bluetooth.hfp.client=1

#
# System props for bluetooth LE Always on feature
#
ro.bluetooth.alwaysbleon=true

#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true

#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=none
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=true

ro.qc.sdk.sensors.gestures=true
ro.qc.sdk.gestures.camera=false
ro.qc.sdk.camera.facialproc=false
# system prop for NFC DT
ro.nfc.port=I2C
#property to enable user to access Google WFD settings.
persist.debug.wfd.enable=1
#property to choose between virtual/external wfd display
persist.sys.wfd.virtual=0
tunnel.audio.encode = true

#use VERY_HIGH_QUALITY for audio resampler
af.resampler.quality=4

#Buffer size in kbytes for compress offload playback
audio.offload.buffer.size.kb=32

#Enable offload audio video playback by default
av.offload.enable=true

#enable voice path for PCM VoIP by default
use.voice.path.for.pcm.voip=true

#hwui properties
ro.hwui.texture_cache_size=72
ro.hwui.layer_cache_size=48
ro.hwui.r_buffer_cache_size=8
ro.hwui.path_cache_size=32
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=6
ro.hwui.texture_cache_flushrate=0.4
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024

#disable dsp gapless mode by default
audio.offload.gapless.enabled=false

# Enable time services daemon
persist.timed.enable=true

# Keep SIM state on LPM mode
persist.radio.apm_sim_not_pwdn=1

# Don't wait the card state for RADIO POWER request
persist.radio.no_wait_for_card=1

# For sys info indication
persist.radio.add_power_save=1

# Snapshot setting
persist.radio.snapshot_enabled=1
persist.radio.snapshot_timer=22

# Control EONS (true = EONS enabled, false = EONS disabled)
persist.eons.enabled=false

# Use CP SE13 Table
persist.radio.use_se_table_only=1

# Default ECCList
ro.ril.ecclist=911,#911,*911

# Use CDMALTE Phone (For 4G model)
telephony.lteOnCdmaDevice=1

# Support Global Mode (For global mode model)
ro.config.multimode_cdma=1

# Data modules (For evolution RIL model)
ro.use_data_netmgrd=false
persist.data.netmgrd.qos.enable=false

# Use data service state for signal display (Except USC CS model)
ro.config.combined_signal=true

# Default Network Mode (For 4G / Global model)
ro.telephony.default_network=10

# Chameleon Default Operator (SPR with Chameleon)
ro.cdma.default_numeric=310000
ro.cdma.default_alpha=Chameleon

#Sprint ItsOn Property
ro.itson.path=/carrier/itson/

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.hwui.texture_cache_size=50
ro.hwui.layer_cache_size=34
ro.hwui.path_cache_size=10
ro.hwui.shape_cache_size=4
ro.hwui.gradient_cache_size=2
ro.hwui.drop_shadow_cache_size=6
ro.hwui.text_small_cache_width=2048
ro.hwui.text_small_cache_height=2048
ro.hwui.text_large_cache_width=4096
ro.hwui.text_large_cache_height=4096
ro.config.alarm_alert=Morning_flower.ogg
ro.config.ringtone=Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
sysprof.activitythread.slowloop=500
sysprof.choreographer.skip=20
sysprof.inputdispatcher.slow=1000
sysprof.inputdispatcher.stale=1000
ro.com.google.clientidbase=android-samsung
ro.security.icd.flagmode=single
ro.vendor.extension_library=libqti-perfd-client.so
persist.radio.apm_sim_not_pwdn=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.build.scafe=americano
ro.build.scafe.size=short
ro.build.scafe.shot=single
ro.build.scafe.cream=white
ro.sec.fle.encryption=true
ro.hdcp2.rx=tz
media.enable-commonsource=true
ro.secwvk=144
ro.securestorage.support=true
security.mdpp=None
ro.security.mdpp.ver=1.1
ro.security.mdpp.release=4
ro.security.vpnpp.ver=1.4
ro.security.vpnpp.release=3
security.mdpp.result=None
ro.security.mdpp.ux=Enabled
ro.security.reactive.triggered=false
ro.error.receiver.default=com.samsung.receiver.error
ro.security.reactive.active=1
ro.smps.enable=true
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=5.0_r2
persist.sys.dalvik.vm.lib.2=libart.so
ro.build.selinux=1
dalvik.vm.isa.arm.features=div
ro.config.knox=v30
ro.config.tima=1
ro.config.timaversion=3.0
ro.kernel.qemu=0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
persist.gps.qc_nlp_in_use=1
persist.loc.nlp_name=com.qualcomm.location
ro.gps.agps_provider=1
ro.pip.gated=0
ro.build.version.sdl=2101"
 
Zenitsu said:
Yes that was my problem, the USB Debugging has not been enabled since I format the phone.
Click to expand...


Actually debuging on or not, does not make any difference..every times I've rooted or flash my firmware..always forgot to activate the debug on..still the phone did what was supposed to do with that option off.

I don't know what the stigma about this that people in here always being so strict around this issue..

Bottom line..you do not need the debug feature.
 
Hey hey guys, it's actually worked and fixed! Sorry for taking it long naahh it's kinda hard to find internet cafe here lol because of the covid-19 so thats why it take me long to fix but its okay, its actually fixed! Thanks to all of you guys! If only I could donate atleast dollar and I already do it but dont have paypal hehe I appreciated you all guys for helping me, I'm so happy because this is the only phone my grandfather was giving to me and i literally will cry if I ever lose this or broke (again) hehehe. Thanks guys! Have a good day!!
 
If you fixed it by reflashing the software, then if there's a newer version available for your model (exact model) you can install that the same way. I would have thought that there would be newer than 4.4 for an S5 (my HTC M7 was a year older than the S5 and got 5.0, and Samsung eventually released 5.1 for my Note 10.1 (2014) tablet, so I'd expect at least 5.1 for the S5.
 
But you still don't say what was the method that worked for you..it sounds like was my build prop..according to your thanks..

If I were you I would keep your 4.4..
 
You must log in or register to reply here.
Back
Top Bottom