Help Broke phone with build.prop!

[lunatic59]

I'd try reformatting first. It might just be a corrupted file system.

 

[Alex Boullé]

By reformatting what do you mean? (sorry for being unknowing about this stuff) Also, reformat with SD card in or out?

 

[lunatic59]

I'm not sure about the Galaxy Y ... can you hot swap SD cards? (remove/insert while the phone is running) or do you have to pull the battery to remove it? If the former, boot with the SD card out and then once fully booted, insert it. Then you should be able to get to menu>settings>storage>sd card and have the option there to reformat. Make sure you choose the external storage card and not the internal sd card partition. Or, you can insert it into a card reader on your PC and reformat there. Make sure to use FAT32 and not NTFS.

 

[Alex Boullé]

There is the option to reformat SD card but it is unclickable.

 

[lunatic59]

Then I 'm guessing it can't read it even being in the slot. Try it in a PC to see if it's there and maybe you can revive it, otherwise i'd say it's a goner.

 

[Alex Boullé]

Hold on, in Odin, was i supposed to select the firmware in each part (bootloader, PDA, Phone and CSC)? All i did was PDA.

 

[lunatic59]

No, you did it correctly, especially if your phone is working. You don't need to reflash the bootloader or the phone's radio. None of that would affect the SD card.

 

[scary alien]

Is your build.prop change still intact / in-effect?

I'm asking simply to try to clear up the (seemingly initial) reason for the apparent boot-loop--i.e., is/was it related to the build.prop change or coincidentally to a failing SD card and to give you a heads-up re. a future change like this.

(FYI, you can still fix the build.prop file with adb as @iowabowtech and I have indicated)

But I don't want to interrupt the Odin discussion, either...best of luck!

 

[Alex Boullé]

Ok, well, i did a factory reset and it didnt solve the SIM card bootlooping issue. So, maybe i'll go to me nearest shop or something. I have solved the initial issue, but now am faced with another one that is i cant make calls or text without a SIM. But thankyou everyone so much for the help, especially @lunatic59

 

[lunatic59]

Glad I could be of some assistance. Hope you get your sim sorted.

 

[Alex Boullé]

Any ideas what could solve the SIM card from causing bootlooping because I cant make any calls.

 

[lunatic59]

A sim card is a simple chip encoded with a unique identifier number and security key. I have seen older cards incompatible with newer phones and some that fail to authenticate a user on the network rending their phone unable to place calls or get data, but the phone still works. A sim card causing a bootloop points to a more basic electronic problem (like a short making the card completely unrecognizable.)

I guess the easiest and cheapest solution is to try a different sim card. Now be careful here, if it is some fault in the phone itself any working sim could potentially be damaged, so it's best to take it to a store and have a rep swap the sim for a working one to see if it is the card or the phone. If you try a friends sim and something happens to it ... well.

I can't think of anything in the build.prop or flashing that would have damaged the sim so I'd say it was nothing you did, just an untimely coincidence.

 

[funkylogik]

Wait. I thought it was the sd card causing the bootloops?
PS if your phone boots without them you can just use a file explorer to fix the build prop (if you still have root after all this flashing)

Well done Lunatic btw mate

 

[lunatic59]

Wait. I thought it was the sd card causing the bootloops?
PS if your phone boots without them you can just use a file explorer to fix the build prop (if you still have root after all this flashing)

Yeah, I noticed that, too, but since the op's in the UK, I'm thinking English isn't his native language.

Well done Lunatic btw mate

"If you throw grapes at a tree long enough, it will eventually fall over."

-- Jerome Howard

 

[funkylogik]

Lmao excellent quote mate ima use that one (until I forget it when I'm sober tomorrow)

 

[SavageRobot]

The problem originated after tweaking build.prop...isn't it best to leave SD/sim out and fix the build.prop to what it should be, as SD/sim might still be OK?

 

[funkylogik]

The problem originated after tweaking build.prop...isn't it best to leave SD/sim out and fix the build.prop to what it should be, as SD/sim might still be OK?

Exactly what I was getting at brother

 

[SavageRobot]

Exactly what I was getting at brother

Oh yea, missed that

 

[lunatic59]

Except @Alex Boullé did not simply factory reset, he reflashed his firmware which should have replaced the edited build.prop with the default file.

 

[AMOCO]

I know if I flash a stock firmware on my g2 it will wipe the sim card and sd card clean.So I would have taken out the sim card and sd card before flashing anything,
Just my 2 cents.

 

[lunatic59]

I haven't used Odin since my Galaxy S2, but i don't think i ever took out the sim or it was affected by the flash, even though all the guides say to remove the sim and sd card before flashing. I guess there is a reason for it, after all.

 

[Alex Boullé]

Its the phone thats broken because the sim card works in other phones. Any ideas of a fix. Please!

 

[Slug]

Odin doesn't go near the SIM, so the firmware flash isn't the cause.

If the phone behaves normally without the SIM, bootloops with it inserted, but other phones aren't affected, then it's almost certainly a hardware issue with that phone.

 

[Alex Boullé]

Here is my build.prop in case it can identify the issue:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.XXLJ2
ro.build.version.incremental=XXLJ2
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Thu Oct 11 19:05:33 KST 2012
ro.build.date.utc=1349949933
ro.build.type=user
ro.build.user=dpi
ro.build.host=DELL180
ro.build.tags=release-keys
ro.product.model=GT-S5363
ro.product.brand=samsung
ro.product.name=GT-S5363
ro.product.device=GT-S5363
ro.product.board=totoro
ro.product.cpu.abi=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=bcm21553
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-S5363
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-S5363-user 2.3.6 GINGERBREAD XXLJ2 release-keys
ro.build.fingerprint=samsung/GT-S5363/GT-S5363:2.3.6/GINGERBREAD/XXLJ2:user/release-keys
# Samsung Specific Properties
ro.build.PDA=S5363XXLJ2
ro.build.hidden_ver=S5363XXLJ2
ro.build.changelist=0000
ro.build.buildtag=
# end build properties
#
# system.prop for GT-S5363
#

# SEC_USE_SIPC : if SEC_USE_SIPC is on, enable libsec-ril.so and block libbrcm_ril.so
#rild.libpath=/system/lib/libsec-ril.so
rild.libpath=/system/lib/libbrcm_ril.so
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=
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.composition.type=mdp
dalvik.vm.heapsize=64m
ro.sf.lcd_density=120
#media.stagefright.enable-player=false

# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072

ro.media.enc.hprof.file.format=3gp
ro.media.enc.lprof.file.format=3gp
ro.media.enc.hprof.codec.vid=m4v
ro.media.enc.lprof.codec.vid=h263
ro.media.enc.hprof.codec.aud=aac
ro.media.enc.lprof.codec.aud=amrnb
ro.media.enc.hprof.vid.width=352
ro.media.enc.lprof.vid.width=176
ro.media.enc.hprof.vid.height=288
ro.media.enc.lprof.vid.height=144
ro.media.enc.hprof.vid.fps=30
ro.media.enc.lprof.vid.fps=30
ro.media.enc.hprof.vid.bps=384000
ro.media.enc.lprof.vid.bps=192000
ro.media.enc.hprof.aud.bps=23450
ro.media.enc.lprof.aud.bps=23450
ro.media.enc.hprof.aud.ch=1
ro.media.enc.lprof.aud.ch=1
ro.media.enc.hprof.aud.hz=8000
ro.media.enc.lprof.aud.hz=8000
ro.media.cam.preview.fps=15
dalvik.vm.jniopts=warnonly

net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/GT-S5363.xml

#
#System property for qemu
#
ro.kernel.qemu=0

#
# ADDITIONAL_BUILD_PROPERTIES
#
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.locationfeatures=1
ro.com.google.clientidbase=android-samsung
ro.com.google.gmsversion=2.3_r10
ro.setupwizard.mode=OPTIONAL
ro.config.notification_sound=13_Whistle_Default_message.ogg
ro.config.alarm_alert=1_Good_Morning.ogg
alsa.mixer.playback.master=Speaker
alsa.mixer.capture.master=Mic
alsa.mixer.playback.earpiece=Earpiece
alsa.mixer.capture.earpiece=Mic
alsa.mixer.playback.headset=Headset
alsa.mixer.capture.headset=Mic
alsa.mixer.playback.speaker=Speaker
alsa.mixer.capture.speaker=Mic
alsa.mixer.playback.bt.sco=BTHeadset
alsa.mixer.capture.bt.sco=BTHeadset
alsa.mixer.playback.bt.a2dp=BTHeadset
alsa.mixer.capture.bt.a2dp=BTHeadset
dev.sfbootcomplete=0
keyguard.no_require_sim=true
ro.config.ringtone=Classic_bell.ogg
ro.config.notification_sound=01_Cloud.ogg
ro.config.alarm_alert=Alarm_Buzzer.ogg
ro.opengles.version=131072
ro.com.google.clientidbase=android-samsung
+=wifi.interface=wl0.1
ro.error.receiver.default=com.samsung.receiver.error
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

 

[lunatic59]

The build.prop isn't the issue now. As @Slug said, it's got to be a hardware problem. The fact that this happened after you originally edited the build.prop file is only coincidental.