[Q] Bricked - black flashing screen - Galaxy Ace S5830 General

I've tried to unlock my phone the way described here. The phone booted fine for the first time, but it did not detect the SIM card and had no network. I restarted the phone, then I only got a black, flashing (2 sec interval) screen. No samsung boot logo, nothing. I can get the phone into download mode, flash it with a new firmware, but it doesn't help: flashing black screen again.
Is there any solution to this? Thanks in advance!

By flashing new firmware you should get boot ,may you do something wrong in flashing
flash firmware correctly
btw which firmware you flashed?

nims11 said:
By flashing new firmware you should get boot ,may you do something wrong in flashing
flash firmware correctly
btw which firmware you flashed?
Click to expand...
Click to collapse
I think the main problem is that when Odin reboots the phone after flashing, it only goes back into this black flashing screen state. So the Odin flashing process never completes totally.
I tried with a few firmwares, from samfirmware.com, the 2.3.3 ones.
Found a video, same problem: youtube.com/watch?v=ZINqwcqhf5k

mazsa1 said:
I think the main problem is that when Odin reboots the phone after flashing, it only goes back into this black flashing screen state. So the Odin flashing process never completes totally.
I tried with a few firmwares, from samfirmware.com, the 2.3.3 ones.
Found a video, same problem: youtube.com/watch?v=ZINqwcqhf5k
Click to expand...
Click to collapse
Problem occurs if you directly flash one package firmware
try kph or kpb . They are multipackage
after flash multipackage you can flash any one package firmware

I have exactly this same issue, last thing I got from the phone was "strage looking" (aka. corrupted) filenames in the efs partition.. is there any way flash a restore EFS ? does not matter if the phone does not make calls ..just booting is enough

remove your battery first and put in again. then remove your simcard and sd card. flash with full package latest firmware like kpn on kpb and try latest odin ( i use odin v4.42 and succesfully flashing galaxy ace and gio without problem)

crrodriguez said:
I have exactly this same issue, last thing I got from the phone was "strage looking" (aka. corrupted) filenames in the efs partition.. is there any way flash a restore EFS ? does not matter if the phone does not make calls ..just booting is enough
Click to expand...
Click to collapse
Yes, that could be the cause. EFS got screwed up during the unlock process, and Odin can't write the EFS on the Galaxy Ace as far as I know.

mazsa1 said:
Yes, that could be the cause. EFS got screwed up during the unlock process, and Odin can't write the EFS on the Galaxy Ace as far as I know.
Click to expand...
Click to collapse
Do you know any way to run fsck on the internal /dev/block/stl5 ?
---------- Post added at 04:05 PM ---------- Previous post was at 03:24 PM ----------
Ok, I found a backup stl5 image made with dd , however I have found no way to flash the efs into the phone...
---------- Post added at 04:12 PM ---------- Previous post was at 04:05 PM ----------
Ok, I found a backup stl5 image made with dd , however I have found no way to flash the efs into the phone...

hello
i same problem
any fix ?

Related

Corrupted IMEI

hi, days ago my sgs2 stop to read sim card. when i go to preferences there are no imei no imei sv and no baseband version. i tried to copy my backuped /efs folder in my phone with adb shell but nothing happened when i rebooted my phone. do you think it is an hardware problem?
Wrong thread.
But download a rom from samfirmware. They usually contain an efs file. Flash that with Odin and you'll be fine.
Sent from my GT-I9100
flashed just now. same problem. com.android.phone crashed on boot
Are you rebooting with power cable attached? I see that all the time.
Did you see the efs recovery thread?
Sent from my GT-I9100 using Tapatalk
Try to flash another ROM, with just a factory reset! Helped me!
http://forum.xda-developers.com/showthread.php?t=1068193
mariosraptor said:
http://forum.xda-developers.com/showthread.php?t=1068193
Click to expand...
Click to collapse
Make sure your SGS2 is I9100 ,, it may be I9100 G ,, which requires a differenent kernel .
---------- Post added at 05:01 AM ---------- Previous post was at 04:31 AM ----------
mariosraptor said:
http://forum.xda-developers.com/showthread.php?t=1068193
Click to expand...
Click to collapse
Make sure your SGS2 is I9100 ,, it may be I9100 G ,, which requires a differenent kernel .
You have a corrupt kernel.
Same happened to me when using mobileodin (which has now been updated)
Phone screen went a funny white colour, no boot, wouldn't charge, no recovery...****ting my pants...Only had download mode working.
I then got home and used PC and Odin flash a fresh kernel in download mode and all was good again.
Very lucky!!! Good luck to you my friend!

[Q] When should U go for a PIT file?

Just as the Subject says. Only for knowledge purposes (though my phone is bricked :/ )
I get absolutely NO ERRORS while flashing ANY firmware for that matter through Odin. Though my phone is U.K Unbranded I9300XXBLG8.
It should boot-up but doesn't :/
Can't get into Recovery either. Not even a glimpse of it.
Stuck at the i9300 logo :/
Anyone care to help me and answer the following questions?
1. When is flashing a PIT File suitable? At what error u should do it?
2. Do I have a Bootloader/Recovery Problem or something?
3. Will J-Tagging help it?
4. Can someone tell me what is causing this problem? I haven't seen anyone with this problem yet. The firmware as well as CF Root flashes successfully (in Odin)... though the phone shows no positive results.
5. Should I go for PIT or J-Tagging or something else? I don't wanna risk it. All I know is that u should only flash a PIT file when u get the "Get PIT for Mapping" error. And J-Tagging is when the phone doesn't boots up. (I may be wrong)
Anyone with some suitable knowledge please drop by and help me.
Or someone who had this problem before.
My phone is a GT-i9300
CSC Version: I9300OXABLG8
Last Firmware was XXBLG8.
Pebble Blue non-branded and 16gb version.
THANK U
don't panic!
You should be able to fix it by just flashing a stock firmware with Odin
---------- Post added at 04:27 PM ---------- Previous post was at 04:25 PM ----------
you could also try removing the battery for a few minutes and then reinsert and try voting recovery again
Only go for a pit file, if you're planning to flash-lock the device, or repartition it, for that matter.
Don't panic, if your device is bricked, it's not, actually
You f***ed up your boot partition..
Goto sammobile.com/firmware, register, download latest U.K. firmware and then you should be good to go. Then you can root it and everything. DW about your SD, it'll stay as it is..
Hope I could help!
LG familyguy59/Beatsleigher
familyguy59 said:
Only go for a pit file, if you're planning to flash-lock the device, or repartition it, for that matter.
Don't panic, if your device is bricked, it's not, actually
You f***ed up your boot partition..
Goto sammobile.com/firmware, register, download latest U.K. firmware and then you should be good to go. Then you can root it and everything. DW about your SD, it'll stay as it is..
Hope I could help!
LG familyguy59/Beatsleigher
Click to expand...
Click to collapse
Yes I have a question about that. I'v been looking for the 3 part firmware. I couldn't find it there :/
I have flashed the exact same firmware u r telling.
Btw ur the only one who has said that doing the PIT file will not risk my S3 :/
AusafSal said:
Yes I have a question about that. I'v been looking for the 3 part firmware. I couldn't find it there :/
I have flashed the exact same firmware u r telling.
Btw ur the only one who has said that doing the PIT file will not risk my S3 :/
Click to expand...
Click to collapse
Lol. Why do you think that is?
CyanogenModded very skankily via XDA app. Skanky, indeed
AusafSal said:
Yes I have a question about that. I'v been looking for the 3 part firmware. I couldn't find it there :/
I have flashed the exact same firmware u r telling.
Btw ur the only one who has said that doing the PIT file will not risk my S3 :/
Click to expand...
Click to collapse
Flashing a pit is risky, and interruption could lead to hard brick, however if you do it right then all will be good, I used to flash with pit on the s1 regularly as it was a necessity coming from cm to gb, or something along those lines.
Just make sure you know what you are doing
PROGRESS!!!!!!!!!!
OK i think my phone is alive. I managed to get it into the CWM Recovery. But there seems to be one little problem. That I can't mount my SDCard. Even tried mounting in the "Mounts and Storage" Option. Im kinda hopeful but I don't know what to do now
Tried Factory/Data Resetting but that didn't do any good. Have i Effed my SDCard or something??? :/ :/
AusafSal said:
That I can't mount my SDCard.
Click to expand...
Click to collapse
any specific error messages about that in cwm?
Personally i used .pit with no issues. My story was that i changed the original partition layout and flashed stock .tar after that. CWM was functional but couldn't mount anything. So i just grabbed a .pit and flashed stock together with .pit - all fine.
And regarding the "interruptions" during .pit flashing - it was the same speed as flashing without .pit, at least for me.
If in your case it's simple filesystem corruption, connecting over adb and launching fsck on the messed up partitions should provide some results.

S3 Soft bricked. Am i wasting my time?

UPDATE EDIT: I have had some progress since my original post. Could you please read my latest posts, maybe you could help me out
Samsung S3 GT-I9300 purchased in the UK.
Its my sisters mobile and i think its soft bricked. She told me it just happened and she done nothing. I received the phone in stock condition.
The phone was orignally stuck solid on the first startup title screen and would not go any further. This is what i have done so far:
1. booted the phone into recovery mode which shows E:failed to mount /efs (invalid argument)
2. wiped cache partition
3. wiped data/factory reset
4. Installed Odin3-v3.04 and downloaded I9300XXDLIB_I9300OXFDLI1_I9300XXDLIB_HOME.tar
5. Connected phone to Odin and flashed the above .tar file which completed sucessfully.
The phone rebooted and it still got stuck on the first startup title screen.
I then looked for a different version and downloaded I9300XXEMF1_I9300EVREMF1_I9300BVEMF1_HOME.tar
this version also installed sucessfully onto the phone after repeating what i had previously done.
The phone reboots and now gets past the first title screen to the animated samsung logo but then keeps looping the animation.
The blue led in top left corner is on and is pulsing from dim to bright constantly while it loops.
Getting a little progress with the 2nd version i kept this on and patched CF-Auto-Root-m0-m0xx-gti9300.tar ontop of it.
Still the same looping when it gets to animated samsung logo
I dont know if this would of helped but i then tryed downloading the NV Generator to make a new IMEI file but cant get
the phone to respond to NV reader writer program.
Iv downloaded Adb and tryed to push the IMEI file onto the phone but it fails with error E: Signature Verification Failed
Im a beginner and this is the first time iv tryed to fix a phone and iv hit a brick wall and not sure now if im wasting my time.
can anyone help me get to the next stage?
Restore your backed up EFS would be the first step .
Do you actually have an I9300 as the NV tool is for a different phone
jje
Does your phone have a cwm or twrp now that u cf rooted it? If u do..then just flash a new rom over it after a clean wipe..(not stock) hopefully your phne should reboot to the new rom..otherwise ill think of another way..put the files into the extmem card using a card reader..or take a tar file of the new rom and flash it after clean wipe..works for me everytime i f up
JJEgan said:
Restore your backed up EFS would be the first step .
Do you actually have an I9300 as the NV tool is for a different phone
jje
Click to expand...
Click to collapse
I don't have a backed up EFS. its my sisters phone. with no backed up EFS is the phone unfixable then?
ardensedvirens said:
no backed up EFS is the phone unfixable then?
Click to expand...
Click to collapse
Correct, needs Service centre repair
Kalyan_121 said:
Does your phone have a cwm or twrp now that u cf rooted it? If u do..then just flash a new rom over it after a clean wipe..(not stock) hopefully your phne should reboot to the new rom..otherwise ill think of another way..put the files into the extmem card using a card reader..or take a tar file of the new rom and flash it after clean wipe..works for me everytime i f up
Click to expand...
Click to collapse
is cwm and twrp options in the recovery menu? where do I look to see?
the recovery menu only shows:
Android system recovery <3e>
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
sorry if this is not what you meant. im not sure what cwm and twrp is short for.
rootSU said:
Correct, needs Service centre repair
Click to expand...
Click to collapse
really? dam. how much would it cost to fix this problem?
JJEgan said:
Do you actually have an I9300 as the NV tool is for a different phone
jje
Click to expand...
Click to collapse
Yes I have I9300. I tried this after watching a video on youtube of a guy doing it for a Samsung s3. I cant post video link yet until I have 10 posts. sorry.
ardensedvirens said:
Yes I have I9300. I tried this after watching a video on youtube of a guy doing it for a Samsung s3. I cant post video link yet until I have 10 posts. sorry.
Click to expand...
Click to collapse
Samsung S3 can be like a dozen different phones, i9300 is one of them.
Glebun said:
Samsung S3 can be like a dozen different phones, i9300 is one of them.
Click to expand...
Click to collapse
Ahh yes I get you now. sorry lol.
what if I get a backup /efs from another phone. would I be able to mount it via sd card, then edit the efs to suit my phone so its not a clone of the phone iv got it from?
iv just flashed ODIN_CheckROM_V4_XXBLG8
it gives alot more options to fiddle around with. I think I could fix this phone to be honest if I keep looking into it.
OMG!! after installing the rom I just posted the phone has booted up and im in
I don't know what to do now.
is the efs fixed? should I make a backup?
how did this fix the phone?
ardensedvirens said:
Ahh yes I get you now. sorry lol.
what if I get a backup /efs from another phone. would I be able to mount it via sd card, then edit the efs to suit my phone so its not a clone of the phone iv got it from?
Click to expand...
Click to collapse
you won't be getting any help with that here since it can be used for illegal activities
---------- Post added at 11:20 PM ---------- Previous post was at 11:19 PM ----------
ardensedvirens said:
is the efs fixed?
Click to expand...
Click to collapse
you tell us - is the IMEI back?
make ioudedi
Glebun said:
you won't be getting any help with that here since it can be used for illegal activities
---------- Post added at 11:20 PM ---------- Previous post was at 11:19 PM ----------
you tell us - is the IMEI back?
Click to expand...
Click to collapse
Ok sorry I didn't know, I just thought it was just a missing folder that could be copyed.
the phone has now booted up
[Resurrection Edition] CheckROM EvoHD™ V4 [ODIN ROM]
this is what I flashed and it seems to have fixed it?
can anyone explain what has happened, I would like to understand what this rom was able to do that the others I flashed before couldn't.
if it booted it doesn't mean that EFS is okay
Glebun said:
if it booted it doesn't mean that EFS is okay
Click to expand...
Click to collapse
do you know what I could do from here to fix the efs?
should I try and pull anything from the phone onto my computer now that its booted?
when I goto status it says IMEI unknown
I know my imei number is behind the battery, how do I register it?
the fact that it booted changes nothing.
you can't repair the EFS if you don't have a backup
what is EFS? is it a folder? a file?
can anyone else explain a little more?
it is a folder.
to explain a little more - you need a new motherboard because every EFS folder is device-specific
I cant get the phone to connect to my wifi. Kies is not picking up the phone either.
is there a way I can download apps to my pc and load them onto the phone? I would like to try and get root explorer installed to see if there is an efs folder.
i tried EFS PRO. it has generated an efs.img file, is it useful?
this is what i done to get it, im not sure if its correct. can anyone tell me?
i went into Backup and selected Device Filter: International Variants
i ticked the block device box and clicked the backup button.
the operation was successful and it created the zip file with the efs.img inside it.
i have pulled this zip from the phone using QtADB_0.8.1_
does anybody know if this file can be used to fix the problem? or has it made a backup of a corrupt efs folder?

Help me get a GIRLS NUMBER BACK! Flashed insecure boot image now no boot!

Guys. i got some ladys number last night.
This morning I was going to do a NANDROID backup before i rooted. I'm on stock. with a secure boot image
so using the S3 toolkit I chose the backup option flashed an insecure boot image.
From now on my phone is stuck on the samsung galaxy siii screen with a ! in the corner, but it wont go pass this.
I want to get back into my stock rom to get this number before i start messing around again
anyone got any ideas?
I've tried flashing recovery/stock-bll3 in odin
cramhead said:
Guys. i got some ladys number last night.
This morning I was going to do a NANDROID backup before i rooted. I'm on stock. with a secure boot image
so using the S3 toolkit I chose the backup option flashed an insecure boot image.
From now on my phone is stuck on the samsung galaxy siii screen with a ! in the corner, but it wont go pass this.
I want to get back into my stock rom to get this number before i start messing around again
anyone got any ideas?
I've tried flashing recovery/stock-bll3 in odin
Click to expand...
Click to collapse
stock-bll3?
Whats that? What phone have you got? you dont need to flash an insecure boot image on the i9300
rootSU said:
stock-bll3?
Whats that? What phone have you got? you dont need to flash an insecure boot image on the i9300
Click to expand...
Click to collapse
its a gt-19300
stock-bll3 is located in \Samsung Galaxy S3 ToolKit\recovery\recovery-stock-bll3-GTI9305.tar
I though seeing as I only had stock flashing that would put my phone back to the state it was in when it was able to boot stock.
The phone loaded fine when i didnt have the ! in the corner
cramhead said:
its a gt-19300
stock-bll3 is located in \Samsung Galaxy S3 ToolKit\recovery\recovery-stock-bll3-GTI9305.tar
I though seeing as I only had stock flashing that would put my phone back to the state it was in when it was able to boot stock.
The phone loaded fine when i didnt have the ! in the corner
Click to expand...
Click to collapse
if i re-installed stock would all my contacts still be stored as long as i didnt wipe the partition/catch etc?
cramhead said:
its a gt-19300
stock-bll3 is located in \Samsung Galaxy S3 ToolKit\recovery\recovery-stock-bll3-GTI9305.tar
I though seeing as I only had stock flashing that would put my phone back to the state it was in when it was able to boot stock.
The phone loaded fine when i didnt have the ! in the corner
Click to expand...
Click to collapse
Thats for a different phone! i9305 is not the same as the i9300
---------- Post added at 02:04 PM ---------- Previous post was at 02:01 PM ----------
cramhead said:
if i re-installed stock would all my contacts still be stored as long as i didnt wipe the partition/catch etc?
Click to expand...
Click to collapse
If you flash a genuine i9300 rom from sammobile.com to as close as possible as what was on it before without wiping, you may be OK...
Some report sometimes it wipes but others not.
If you flash a custom recovery (Philz / CWM / TWRP) for the i9300, you can take a nandroid backup then if the worst comes to the worst, you can use a nandroid backup explorer to extract the data.
Here's a tip for future... Take a number and say "hey let me ring that quickly to test it", then it appears on your mobile phone bill / history
Or better yet, use google contacts
Caveman method write it on the back of your hand .
jje
rootSU said:
Thats for a different phone! i9305 is not the same as the i9300
---------- Post added at 02:04 PM ---------- Previous post was at 02:01 PM ----------
If you flash a genuine i9300 rom from sammobile.com to as close as possible as what was on it before without wiping, you may be OK...
Some report sometimes it wipes but others not.
If you flash a custom recovery (Philz / CWM / TWRP) for the i9300, you can take a nandroid backup then if the worst comes to the worst, you can use a nandroid backup explorer to extract the data.
Here's a tip for future... Take a number and say "hey let me ring that quickly to test it", then it appears on your mobile phone bill / history
Or better yet, use google contacts
Click to expand...
Click to collapse
went back to stock and the NUMBER IS STILL THERE!!!! YESSSSSS Sexy time
cheers m8 x

[Q] Partitions corrupt on internal memory

Hi,
I have a rooted Galaxy S3 I9300. One fine day, it just died on me, and is now perennially stuck on the Samsung logo.
I have CWM recovery installed, and I can boot into the recovery and the download mode just fine. However, in the recovery, I see that I am not able to mount even a single partition, including data, system etc. So flashing a new ROM etc. is out of the question. Also, I have tried flashing ROM's and PIT files using ODIN, and each time I get a big red FAIL message.
Also, using adb, I am unable to manually mount any partition, giving me the error message that there is no such file and directory.
At this point, I know people will say that my eMMC is fried, but here is the thing - I can access whatever files are there on the memory using adb. It's just mounting that is the problem. Can anyone suggest what the solution to this problem can be?
Try downgrading the bootloader to BLFB before flashing a full stock firmware and pit.
boomboomer said:
Try downgrading the bootloader to BLFB before flashing a full stock firmware and pit.
Click to expand...
Click to collapse
Should I use this zip file to flash via CWM?
http://forum.xda-developers.com/showpost.php?p=36433966&postcount=105
Also, will I be able to flash the Android 4.1.1 firmware over this bootloader, because that is the version of the full recovery firmware available on XDA?
Yes, but I would advise finding an Odin version as it's safer flashing the bootloader that way.
If the bootloader will flash then use the 4.3 rescue firmware and pit file from the general forum. Flashing 4.1 will result in your efs folder not being read.
Bootloader is irrelevant to firmware, earlier versions have less warranty checks but don't use BLFB bootloader to flash a lot of things as it isn't SDS safe
boomboomer said:
Yes, but I would advise finding an Odin version as it's safer flashing the bootloader that way.
If the bootloader will flash then use the 4.3 rescue firmware and pit file from the general forum. Flashing 4.1 will result in your efs folder not being read.
Bootloader is irrelevant to firmware, earlier versions have less warranty checks but don't use BLFB bootloader to flash a lot of things as it isn't SDS safe
Click to expand...
Click to collapse
OK. I will flash the 4.3 firmware once I reach home.
I have downloaded the 4.1.1 rescue firmware too. Can I use the PIT file included in this firmware to go along with the 4.3 firmware?
Yes.
Now suddenly, my phone has stopped booting. No boot screen, nothing. I can't even charge my phone now. Does that mean the device is gone beyond repair? :crying:
You can try and search the i9300 forums for an unbrick method that uses an SD card to fix the bootloader and get you up and running.
Alexander_the_B0ss said:
You can try and search the i9300 forums for an unbrick method that uses an SD card to fix the bootloader and get you up and running.
Click to expand...
Click to collapse
I tried searching for that, but doesn't that require a JTAG device or something?
Nope
---------- Post added at 02:24 AM ---------- Previous post was at 02:23 AM ----------
parag14 said:
I tried searching for that, but doesn't that require a JTAG device or something?
Click to expand...
Click to collapse
If you give me a couple of minutes i will find the thread for you
Alexander_the_B0ss said:
Nope
---------- Post added at 02:24 AM ---------- Previous post was at 02:23 AM ----------
If you give me a couple of minutes i will find the thread for you
Click to expand...
Click to collapse
Please do, because I have been tearing my hair out but couldn't find a thread which wouldn't require disassembling the phone.
Here you go http://forum.xda-developers.com/galaxy-s3/general/galaxy-s-iii-gt-i9300-hard-brick-fix-t1916796 but it requires for you to dissasemble the phone and I can make you a copy of the file needed.
Alexander_the_B0ss said:
Here you go http://forum.xda-developers.com/galaxy-s3/general/galaxy-s-iii-gt-i9300-hard-brick-fix-t1916796 but it requires for you to dissasemble the phone and I can make you a copy of the file needed.
Click to expand...
Click to collapse
Ah! I have read this thread already, but I don't think that I would be able to do this by myself. I would probably need a professional to do this. Thanks for your help, though, but looks like I'll have to buy a new phone now ..
If you can deliver it to me i can do this. Where are you from?

Categories

Resources