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

Help Samsung galaxy core plus duos bricked

I have an samsung galaxy core plus duos (sm-g3502t), it's bricked, blank flash, and after a google search, I fond a way to recover it, but I need a file extracted from a identical phone, can anyone help me please? ;-;
 
I have an samsung galaxy core plus duos (sm-g3502t), it's bricked, blank flash, and after a google search, I fond a way to recover it, but I need a file extracted from a identical phone, can anyone help me please? ;-;
to be honest, your phone came out in 2013!!! it is better if you move on from the phone.

also i doubt anyone would still have files associated with this device anymore.

what is your exact model number for the phone?
sm-g3502t.....never mind.

you can check here:https://www.sammobile.com/firmwares/ for any firmware updates for your phone. you just need the exact model number as firmware updates are VERY device specific. flashing the wrong one can be bad for the phone.

edit: here you go:
https://www.sammobile.com/samsung/galaxy-core-plus/firmware/#SM-G3502T

just verify that i have the right firmware for you.
 
I have the stock rom downloaded, but I need the block 0, because it's in edl mode, odin didn't recognize it, and I have a collection of cell phones so I didn't want to leave it ,-,
 
.... but I need a file extracted from a identical phone, can anyone help me please? ;-;
That's a very vague question and could be easily misinterpreted as a reference to one of thousands of files that may or may not even be relevant. Please be more specific about the actual problem you're encountering and what file you're referring to. I'm guessing it's the PIT (Partition Information Table) file for your model but ?????

.... odin didn't recognize it,..
Is that an indirect reference to the Odin utility installed on a PC, or an error message about 'Odin Mode' in your Samsung phone's Download Mode?
If the former, so you have the Samsung driver installed on your PC? Tried using a different USB cable? If you're plugging your phone into something like a USB hub try plugging it directly into a USB port on your PC instead.
If the latter, is there any other text in the error message?
 
That's a very vague question and could be easily misinterpreted as a reference to one of thousands of files that may or may not even be relevant. Please be more specific about the actual problem you're encountering and what file you're referring to. I'm guessing it's the PIT (Partition Information Table) file for your model but ?????


Is that an indirect reference to the Odin utility installed on a PC, or an error message about 'Odin Mode' in your Samsung phone's Download Mode?
If the former, so you have the Samsung driver installed on your PC? Tried using a different USB cable? If you're plugging your phone into something like a USB hub try plugging it directly into a USB port on your PC instead.
If the latter, is there any other text in the error message?

the phone is in edl mode and it's showing on devmgmt as qualcomm hs-usb qdloader 9008 the cable it's ok, and the phone screen is off

the file needed is on "/dev/block/mmcblk0" but it's better on a clean phone because it will come with all data on phone
 
so how are you entering edl? you can't just boot straight into it from what little i know of edl. and what happens when you try to go into download mode?
the phone screen is off and it's not booting, when I plug the cable it go instantly to edl mode and screen still off
 
If your very dated Core phone is stuck in a boot loop that takes you into EDL, it also has a removable battery. I'd suggest pulling the battery (even though I'm guessing it's essentially dead) and with your phone unplugged, wait a few minutes, put it back in, and try booting your phone into its Download Mode and try flashing it again:
https://www.hardreset.info/devices/samsung/samsung-g350-galaxy-core-plus/download-mode/
even without the battery it goes into edl mode
 
sad ;-; maybe my other phone can be fixed, I will open another thread

That is of course your prerogative but as much as you want to deny and/or ignore what @Dannydet posted, this is an eight-year old phone with very limited value as a daily usage phone. Google stopped supporting it years ago, as did almost all independent developers so the OS is way out of date along with the apps that are on it. Interactions with current online technology will be limited when they do work, with increased privacy and security risks. The odds are the battery is dead so using it probably involves having to have it plugged in all the time or unplugged for a few minutes at a time.
So all the time and resources you want to devote into restoring this phone just to watch it being able to boot up normally again is worth it if only for the learning experience on your end, but do you actually have plans for this phone otherwise?
 
That is of course your prerogative but as much as you want to deny and/or ignore what @Dannydet posted, this is an eight-year old phone with very limited value as a daily usage phone. Google stopped supporting it years ago, as did almost all independent developers so the OS is way out of date along with the apps that are on it. Interactions with current online technology will be limited when they do work, with increased privacy and security risks. The odds are the battery is dead so using it probably involves having to have it plugged in all the time or unplugged for a few minutes at a time.
So all the time and resources you want to devote into restoring this phone just to watch it being able to boot up normally again is worth it if only for the learning experience on your end, but do you actually have plans for this phone otherwise?
I discovered that it is hard bricked, because it is freezing when try to flash.
I was trying to fix it because my 5 years old cousin like to play minecraft even if is a old version, but I have only a android 4.0.4 tablet, and it work but it has only 512mb of RAM.
and looking at the layout and the icons give me such a nostalgia .-.
 
Back
Top Bottom