Database Users

J16 = Bricked Samsung Vibrant (T-Mobile)

I too seemed to have bricked my phone with the latest update. I've been looking at the Vibrant Bible as well but find vague with a lot of information. When I say vaugue I mean I have no idea where to even start with recovering my phone.
When I turn the phone on it sticks on the Vibrant/SAMSUNG screen.
I am able to get into the recovery menu which displays the following below.
Android system recovery <2e>
Samsung Recovery Utils
-for BML -
VOL UP - up
VOL DOWN -down
POWER - select item
[options below are the only ones made available to me)
reboot system now
reinstall packages
delete all user data
delete cache data
----------------------------------------------------------
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
-- movi_checking done!...
update media, please wait
update media, finished
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
I want to re-flash the phone back to 100% out of the box stock. I downloaded and installed Odin3 v1.3 but not sure on what to do next. Can someone please assist and point me in the right direction?

you got odin, so youre in the right direction.
download "eugenes froyo that doesnt brick" and flash that through odin (read instructions carefully on his post) sidenote: the adb reboot step might be confusing too
once you successfully flashed his rom, search for the stock rom in the development forum
flash that through odin and you are 100% stock again

anthonys2r said:
you got odin, so youre in the right direction.
download "eugenes froyo that doesnt brick" and flash that through odin (read instructions carefully on his post) sidenote: the adb reboot step might be confusing too
once you successfully flashed his rom, search for the stock rom in the development forum
flash that through odin and you are 100% stock again
Click to expand...
Click to collapse
Thanks for that information. I tried exactly what is outlined in "eugenes froyo that doesnt brick" method thread, but something isnt right with my phone. I sent him the following private message in hopes of him reaching out with additional help.
quailallstar said:
Hi Eugene.
A little background info on my issue. My Samsung Tmobile Vribrant was rooted. Tmobile pushed the update available notification last week and I attempted to install it last night, wish I wouldn't have. Now my phone is stuck on the Samsgun Vibrant start up screen.
I am able to log into Android recovery and get the screen below.
I am able to get into the recovery menu which displays the following below.
Android system recovery <2e>
Samsung Recovery Utils
-for BML -
VOL UP - up
VOL DOWN -down
POWER - select item
[options below are the only ones made available to me)
reboot system now
reinstall packages
delete all user data
delete cache data
----------------------------------------------------------
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
-- movi_checking done!...
update media, please wait
update media, finished
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
I've downloaded your "eugenes froyo that doesnt brick" along with Odin3 v1.30.
Followed your instructions but when I plug in my phone this is what I see.
What is wrong here? Odin doesn't seem to be installing anything on my phone.
I'm worried that I've possibly fried my new Tmobile Vibrant.
Screen shots of what Odin3 v1.3 connected to my phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse

Had the same problem just went into recovery mode and delete all user data and
delete cache data and it worked.

kingzeus said:
Had the same problem just went into recovery mode and delete all user data and
delete cache data and it worked.
Click to expand...
Click to collapse
After you clear the cache and user data did you reboot?

quailallstar said:
I too seemed to have bricked my phone with the latest update. I've been looking at the Vibrant Bible as well but find vague with a lot of information. When I say vaugue I mean I have no idea where to even start with recovering my phone.
When I turn the phone on it sticks on the Vibrant/SAMSUNG screen.
I am able to get into the recovery menu which displays the following below.
Android system recovery <2e>
Samsung Recovery Utils
-for BML -
VOL UP - up
VOL DOWN -down
POWER - select item
[options below are the only ones made available to me)
reboot system now
reinstall packages
delete all user data
delete cache data
----------------------------------------------------------
-- Movi_check Start..!!
checksum confirmation need_checksum[0]
Not need checksum confirmation
--Movi_check already executed!!...
-- movi_checking done!...
update media, please wait
update media, finished
# MANUAL MODE #
-- Appling Muti-CSC...
Installing Muti-CSC
I want to re-flash the phone back to 100% out of the box stock. I downloaded and installed Odin3 v1.3 but not sure on what to do next. Can someone please assist and point me in the right direction?
Click to expand...
Click to collapse
this is all you need to do, download JI6 stock for odin. open odin and load the tar file. Then plug in your phone to the USB while holding down the volume buttons. Look at the upper left corner in odin to make sure the yellow box shows a port number. Also check the box on the bottom left in odin to see that it says added. Then click on start. That will wipe everything and restore everything back to stock just like it was out of the box.

mr2t32 said:
this is all you need to do, download JI6 stock for odin. open odin and load the tar file. Then plug in your phone to the USB while holding down the volume buttons. Look at the upper left corner in odin to make sure the yellow box shows a port number. Also check the box on the bottom left in odin to see that it says added. Then click on start. That will wipe everything and restore everything back to stock just like it was out of the box.
Click to expand...
Click to collapse
@mr2t32
I wil try this tonight at home and report back my results. Thanks!

This post saved me when my Vibrant wouldn't boot. Very simple instructions for using Odin.
http://forum.xda-developers.com/showthread.php?t=803492

How long did you wait? It took mine about 8-10 minutes to reboot while on the "s" screen..

There is no such thing as j16. Its JI6. Just sayin.
Sent from my SGH-T959 using XDA App

Astitious said:
This post saved me when my Vibrant wouldn't boot. Very simple instructions for using Odin.
http://forum.xda-developers.com/showthread.php?t=803492
Click to expand...
Click to collapse
This is the J16 version I need to download right? Want to make sure before I mess the phone up again, lol.
http://forum.xda-developers.com/showthread.php?p=8511186#post8511186

WORKED!
I used this post http://forum.cyanogenmod.com/topic/6998-howto-recover-from-a-soft-brick-on-your-vibrant/
To un-brick my poor Vibrant. Now its time to re-root and add mobile AP Thanks all for the guidance and input.

movi_check start stuck vibrant SGH-T959
Work for me Download Mode :
pull : battery, sdcard, usb
after you pull all these things insert the battery push and hold volume up and connect the usb
you should obtain the Download Mode.

S39 said:
movi_check start stuck vibrant SGH-T959
Work for me Download Mode :
pull : battery, sdcard, usb
after you pull all these things insert the battery push and hold volume up and connect the usb
you should obtain the Download Mode.
Click to expand...
Click to collapse
Late answer much?

beren28 said:
Late answer much?
Click to expand...
Click to collapse
LOL. the guy bricked back in October and he's got the solution for him now?

So funny when people bring back old ass dead forums
Sent from my SGH-T959 using XDA Premium App

lmao i was like wtf j16? when i saw this

Restored i9020T ROM to i9020A

I was trying to restore my ATT Nexus S to the stock Android build following the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1061855
However, I didn't realize that it was the wrong version, and now my Nexus will not boot. I've done considerable searching, but it will not turn on. I hope I don't have a brick, but if there are any tips that anyone can give to a major Android amateur, I would really appreciate them.

When you say will not boot what exactly are you describing? Does it power up? Can you get to the bootloader? Does your computer recognize the phone when connected via USB?
Sent from my PC36100 using XDA Premium App

I'm not that familiar with it, but use odin to reflash the stock firmware.
Sent from my Nexus One using Tapatalk

uansari1 said:
I'm not that familiar with it, but use odin to reflash the stock firmware.
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
I would recommend this only as a matter of last resort.

If your ROM that you flashed contained a radio IMG of the T version it may be bricked.. I know the only way you can pretty much brick an android device is by flashing the wrong radio or having a bad radio flash;/ But that was predominantly with HTC models, not 100 percent sure with sammy models...
JD

JupiterDroid said:
If your ROM that you flashed contained a radio IMG of the T version it may be bricked.. I know the only way you can pretty much brick an android device is by flashing the wrong radio or having a bad radio flash;/ But that was predominantly with HTC models, not 100 percent sure with sammy models...
JD
Click to expand...
Click to collapse
Yes I looked in the thread and the ROM he flashed did include radios.
However! It's mighty hard to brick a Nexus S
My suggestion to the OP. I do not have time right now to find these things for you, but a general outline of what you need to do is:
1. Get fastboot working
2. Use fastboot to flash ClockworkMod Recovery
3. Find the i9020A stock rom and flash it.
4. Do not try to boot phone
5. Find the i9020A radio and flash it.
Or you might even find a ROM for i9020A that includes the radio, in which case you could just flash that.
OR, if you find a Nandroid backup of i9023A stock ROM, you can restore that. But you will still need to flash the proper radio.

matt2053 said:
Yes I looked in the thread and the ROM he flashed did include radios.
However! It's mighty hard to brick a Nexus S
My suggestion to the OP. I do not have time right now to find these things for you, but a general outline of what you need to do is:
1. Get fastboot working
2. Use fastboot to flash ClockworkMod Recovery
3. Find the i9020A stock rom and flash it.
4. Do not try to boot phone
5. Find the i9020A radio and flash it.
Or you might even find a ROM for i9020A that includes the radio, in which case you could just flash that.
OR, if you find a Nandroid backup of i9023A stock ROM, you can restore that. But you will still need to flash the proper radio.
Click to expand...
Click to collapse
With HTC models if you flash a bad radio thats your superphone dead! Are you sure this is retrievable on sammy devices? I hope to god it is for the OP's sake
JD

jstennis1591 said:
I was trying to restore my ATT Nexus S to the stock Android build following the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=1061855
However, I didn't realize that it was the wrong version, and now my Nexus will not boot. I've done considerable searching, but it will not turn on. I hope I don't have a brick, but if there are any tips that anyone can give to a major Android amateur, I would really appreciate them.
Click to expand...
Click to collapse
I looked in the zip that you flashed, and what you did is flashed a bootloader.img that's not for your i9020a and thats why your phone isn't booting. The radio has nothing to do with the phone not booting.
To solve your problem, you're going to have to find a copy of the bootloader.img that belongs to the i9020a and flash it with Odin through download mode.
To get a copy of the bootloader.img someone with i9020a will have to dump it from there phone through adb. (I'll put the steps how later today)
To get into download mode, you'll need to hold the volume + & - buttons and plug the phone into the computer while the phone is off and Odin is running on the computer. And if that doesn't work you'll have to use jig 301k resistor connector to get into download mode (Search how to make one on nexus s or sgs forum)
That's the only way to save your phone is through Odin and download mode, sorry.
Sent from my Nexus S using XDA Premium App

For reference if you restored the i9020T bootloader to the i9020A it will hard brick. I can however fix a phone in that scenario even still with my JTAG repair. Just PM me if you need a hard bricked Nexus S of any model fixed.

I've regrettably done the same - gotten a i9020-non-A bootloader confused with the i9020A - and bricked my device by writing that incorrect bootloader (using 'fastboot flash bootloader <wrong bootloader here>.img'). The phone is now totally unresponsive (power button, vol+ & power, etc).
I don't have a Windows machine to hand, but do have a WinXP VM within a Linux host available. Based on a muddle of other XDA posts I fetched/installed Odin 1.82, the Samsung USB drivers and what I believe to be a valid i9020A image (details below).
reddv1 said:
...
To get into download mode, you'll need to hold the volume + & - buttons and plug the phone into the computer while the phone is off and Odin is running on the computer. And if that doesn't work you'll have to use jig 301k resistor connector to get into download mode ...
Click to expand...
Click to collapse
Problem is I get nada when plugging the phone in with vol button held down (pressing in the whole vol button, both + and - pressed) and plugging the phone in with Odin running and VM capturing USB devices. i.e. either I'm not using Odin correctly and/or running it within a VM doesn't work, or I need the hardware helper (USB adapter w/ resistor).
Could you offer any tips on how to drive Odin?
Plan B is to send the phone for JTAG recovery, though as I'm not in the US that's a bit of a pain.
I9020A image:
Android 2.3.3 (Build GRI54/UCKB2 Radio/KA3 Bootloader)
2.3.3 -> 2.3.4 (android.clients.google.com/packages/ota/google_crespoa/286d814dee5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip)

af3556 said:
I've regrettably done the same - gotten a i9020-non-A bootloader confused with the i9020A - and bricked my device by writing that incorrect bootloader (using 'fastboot flash bootloader <wrong bootloader here>.img'). The phone is now totally unresponsive (power button, vol+ & power, etc).
I don't have a Windows machine to hand, but do have a WinXP VM within a Linux host available. Based on a muddle of other XDA posts I fetched/installed Odin 1.82, the Samsung USB drivers and what I believe to be a valid i9020A image (details below).
Problem is I get nada when plugging the phone in with vol button held down (pressing in the whole vol button, both + and - pressed) and plugging the phone in with Odin running and VM capturing USB devices. i.e. either I'm not using Odin correctly and/or running it within a VM doesn't work, or I need the hardware helper (USB adapter w/ resistor).
Could you offer any tips on how to drive Odin?
Plan B is to send the phone for JTAG recovery, though as I'm not in the US that's a bit of a pain.
I9020A image:
Android 2.3.3 (Build GRI54/UCKB2 Radio/KA3 Bootloader)
2.3.3 -> 2.3.4 (android.clients.google.com/packages/ota/google_crespoa/286d814dee5b.signed-sojua-GRJ22-from-GRI54.286d814d.zip)
Click to expand...
Click to collapse
I think you need a windows PC, where's the link to the i9020a Odin package
Sent from my Nexus S using XDA Premium App

I dunno if this will helpful... but I was in a very similiar situation 2 days ago... I wanted to unroot my phone and restore to stock .. so I found this Odin guide... which was for nexus 4G model.. I had non-4G i9020a. So during Odin process it failed on radio ..and I thought my phone was bricked but I took out the bettery and put it back in and the phone booted into android normally..however in about phone .. everything was showing unknown and I had no signal..so with the help of fellow xdaers. I first downloaded the FULL rom for i9020A and placed it on my sd card.. Downloaded CWM and got it onto my Phone..then wiped cache, system/data etc... and installed the rom from sd card and phone was back to normal.. so if ur able to boot into the phone I would suggest what I did.. and obviously if u need detailed guide of what I did.. don't hesitate to ask... hope your phone comes back to life... (Y)
Sent from my Nexus S using XDA App

G'Day reddv1: is odin specific to each model phone? The one I have I fetched from droidangel.blogspot.com/2011/05/odin-multi-downloader-flasher-program.html, that page lists a Odin3 v1.82.rar for the i9020a. However the exe therein is named I9003_Odin3 v1.82.exe.
Can you clarify the steps required to get Odin to recognise the phone? Is this correct:
1) phone is off, odin is running on the Windows PC (w/ Samsung USB drivers installed - yes?)
2) press and hold both volume +/- buttons (i.e. press the entire vol button in)
3) plug in USB
4) ?
5) profit
forpulse: problem is my phone is bricked, i.e. won't power on. The odin guides I've found so far use it in a way that assumes the phone can be put into recovery mode, which mine can't be. (e.g. http://forum.xda-developers.com/showthread.php?t=1088494)

I sent my bricked phone to MobileTechVideos and he was able to JTAG recover the phone (and left no marks, etc). However the bad news is the phone now has a very bad purple/pink tint to the screen (have tried a couple of ROMs).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

connexion2005 said:
For reference if you restored the i9020T bootloader to the i9020A it will hard brick. I can however fix a phone in that scenario even still with my JTAG repair. Just PM me if you need a hard bricked Nexus S of any model fixed.
Click to expand...
Click to collapse
hey I've COMPLETELY inadvertantly flashed a i9020t radio on my i9020a, its as bricked as ive ever seena phone. wont turn on, black screen, nothing.
My question, will it go into download mode if I plug in a 301k resistor jig
or is jtag my only hope
thanks

Good to know I'm not the only one...
Anyone have ideas for my "Flashed I9020A ROM on a D720" thread over here? http://forum.xda-developers.com/showthread.php?t=1319865

{FIX} Bricked EMMC Galaxy S2

Hello Everyone,
Few days ago, i build Mozilla OS(boot to gecko) for my galaxy s2 and flashed it, but after i did a "wipe data" in recovery, it bricked my phone:crying:,
so after a long search i found that "EMMC" partition is currepted or in other words its bricked
and now i cant flash any ROM through recovery or Odin.
WHAT IS "EMMC"
i am not a developer or any genious, so i just explain you in simple words
EMMC is a partition in which your data is stored. and if it currepts or bricked then u can,t use your phone.
NOW its time for SOLUTION
SOLUTION 1
if u still have access to the "Recovery" and "Download Mode"
then here is a simple solution which i used until i did not found the real solution for EMMC
so let,s start
Download Siyeh Kernel 5.0.1 from bottom
Go to "Download Mode" By pressing volume down+home+power button for 5 second
Connect your galaxy s2 to your computer
Start "Odin"and click on PDA file and select where you download "Siyeh Kernel" and click on start
After flashing completed your Phone restart now press Volume up+home button+power and keep pressing until you see the "Recovery Menu"
Now go to "dual boot" option and wipe data for 2nd ROM (it take some time)
Now select install zip from internal SD card or external SD card (it depend upon you that where you have a Rom file)
After installing ROM, restart phone, after galaxy s2 boot logo you will see option to boot to 2nd ROM, now press home key to start your phone as second ROM,
Yahoo, now your Galaxy s2 is alive again:victory:
if you don't have a ROM in your internal or external SD card then go to "mount and storage" and connect your phone to your computer and select the last option "mount USB, it will show your internal and external both cards on your computer. now put any Good ROM in your memory card
SOLUTION 2
it is not my work which i am going to share with u,
Thanks to hg42 for providing pit files for galaxy s2 and also for providing recovery script
here is the link to his thread http://forum.xda-developers.com/showthread.php?t=1667886
but it is basically for galaxy note so i write this thread specially for galaxy s2 users.
let me explain what is this
when your EMMC or Data partation is bricked then only way to survive is to cut off the infected part of the EMMC
it mean u just leave the bricked part of the EMMC partation
for this u need to locate the faulty part of the EMMC
emmc_find_brick_start.zip will start a script and where it stopped it mean it is the starting point of the Bricked EMMC partation and note that point for me it is 1028MB
emmc_find_brick_end.zip will start a script from downward and stopped where the fault part of EMMC is finished. note that one for me it is 2296
and i use this PIT file
i9100_16GB_u1_02_20110310_emmc_EXT4--patched--brick-between-00713-and-02323-MB--DATAFS-moved-by-01536-MiB
00713 is the stating point and 02323 is the ending pint, for you it may be different.
before starting this process please save your efs-backup to your computer or on your external SD card
Enough lesson for all of us :silly:
so let,s start
Download and copy these two file to your SD card emmc_find_brick_start.zip and emmc_find_brick_end.zip
Now go to recovery and click on install zip from SD and click on emmc_find_brick_start.zip and note where it stopped
Now run the 2nd zip emmc_find_brick_end.zip and note where it stopped
Now download pit file and find the right modify pit file for you
Now go to "download mode" and start Odin on your computer and connect galaxy s2
In Odin check the "re-partition" box and then click on pit file and load the pit file (One you have selected before)
Now click on start after it completed your phone will restart now again go to download mode and flash a stock ICS firmware
4.0.3 is good firmware
and yahoo, galaxy s2 is now fully alive
After installing ROM, do not start it and go to recovery and then go to mount and storage and format "System" and "Cache" and "Data" and "Internel SD and re install the ROM and then you can use it
I am Not Responsible for any damage and there is No Guarantee that it work for you or not
for best result please read hg42post
you can download All the necessery files from this link http://www.mediafire.com/?4f98kjl59o85oha
Best of luck all of you and please tell us if you are succeeded

As far as I was aware if you wipe with emmc bug kernel you cant even power on?

TheATHEiST said:
As far as I was aware if you wipe with emmc bug kernel you cant even power on?
Click to expand...
Click to collapse
Depends on what part of chip got faulty, Some even got it to boot, but started facing other problems.

Sh4dy is right and
If some part of the data partation is currepted then you can solve it through this method....
Sent from my GT-I9100 using xda app-developers app

my current rom is 4.1.2 xwlse, can i use this method (solution 1) on this rom?or this method only for ICS rom?

in my case i have a S2 with eMMC HardBrick and also the riff won't flash the resurrection code, there is a solution for to "cut" the bad part of the eMMC directly from RIFF?

some part of the data partation is currepted then you can solve it through this method.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

hufqnjhu said:
some part of the data partation is currepted then you can solve it through this method.
Click to expand...
Click to collapse
yes the first 2 GB are corrupted and the procedure of resurrection doesn't work and my S2 doesn't boot at all
here the log of my riff
http://forum.xda-developers.com/showthread.php?p=39138600#post39138600

I tried the 2nd solution before and it worked , but almost everyday phone freezes with no reasons ! , any ideas ??

You, sir, are awesome.
bilalbasra said:
Hello Everyone,
Few days ago, i build Mozilla OS(boot to gecko) for my galaxy s2 and flashed it, but after i did a "wipe data" in recovery, it bricked my phone:crying:,
so after a long search i found that "EMMC" partition is currepted or in other words its bricked
and now i cant flash any ROM through recovery or Odin.
WHAT IS "EMMC"
i am not a developer or any genious, so i just explain you in simple words
EMMC is a partition in which your data is stored. and if it currepts or bricked then u can,t use your phone.
NOW its time for SOLUTION
SOLUTION 1
if u still have access to the "Recovery" and "Download Mode"
then here is a simple solution which i used until i did not found the real solution for EMMC
so let,s start
Download Siyeh Kernel 5.0.1 from bottom
Go to "Download Mode" By pressing volume down+home+power button for 5 second
Connect your galaxy s2 to your computer
Start "Odin"and click on PDA file and select where you download "Siyeh Kernel" and click on start
After flashing completed your Phone restart now press Volume up+home button+power and keep pressing until you see the "Recovery Menu"
Now go to "dual boot" option and wipe data for 2nd ROM (it take some time)
Now select install zip from internal SD card or external SD card (it depend upon you that where you have a Rom file)
After installing ROM, restart phone, after galaxy s2 boot logo you will see option to boot to 2nd ROM, now press home key to start your phone as second ROM,
Yahoo, now your Galaxy s2 is alive again:victory:
if you don't have a ROM in your internal or external SD card then go to "mount and storage" and connect your phone to your computer and select the last option "mount USB, it will show your internal and external both cards on your computer. now put any Good ROM in your memory card
SOLUTION 2
it is not my work which i am going to share with u,
Thanks to hg42 for providing pit files for galaxy s2 and also for providing recovery script
here is the link to his thread http://forum.xda-developers.com/showthread.php?t=1667886
but it is basically for galaxy note so i write this thread specially for galaxy s2 users.
let me explain what is this
when your EMMC or Data partation is bricked then only way to survive is to cut off the infected part of the EMMC
it mean u just leave the bricked part of the EMMC partation
for this u need to locate the faulty part of the EMMC
emmc_find_brick_start.zip will start a script and where it stopped it mean it is the starting point of the Bricked EMMC partation and note that point for me it is 1028MB
emmc_find_brick_end.zip will start a script from downward and stopped where the fault part of EMMC is finished. note that one for me it is 2296
and i use this PIT file
i9100_16GB_u1_02_20110310_emmc_EXT4--patched--brick-between-00713-and-02323-MB--DATAFS-moved-by-01536-MiB
00713 is the stating point and 02323 is the ending pint, for you it may be different.
before starting this process please save your efs-backup to your computer or on your external SD card
Enough lesson for all of us :silly:
so let,s start
Download and copy these two file to your SD card emmc_find_brick_start.zip and emmc_find_brick_end.zip
Now go to recovery and click on install zip from SD and click on emmc_find_brick_start.zip and note where it stopped
Now run the 2nd zip emmc_find_brick_end.zip and note where it stopped
Now download pit file and find the right modify pit file for you
Now go to "download mode" and start Odin on your computer and connect galaxy s2
In Odin check the "re-partition" box and then click on pit file and load the pit file (One you have selected before)
Now click on start after it completed your phone will restart now again go to download mode and flash a stock ICS firmware
4.0.3 is good firmware
and yahoo, galaxy s2 is now fully alive
After installing ROM, do not start it and go to recovery and then go to mount and storage and format "System" and "Cache" and "Data" and "Internel SD and re install the ROM and then you can use it
I am Not Responsible for any damage and there is No Guarantee that it work for you or not
for best result please read hg42post
you can download All the necessery files from this link http://www.mediafire.com/?4f98kjl59o85oha
Best of luck all of you and please tell us if you are succeeded
Click to expand...
Click to collapse
First and foremost, I just joined because of this post.
Secondly, THANK YOU bilalbasra, may Allah bless your soul! :angel:
OBS, still getting a samsung logo with a yellow triangle on reboot, but quickly followed up by the correct booting (in my case cyanmod)..
Solution nr 1 worked for me (I strongly suggest noobs like me to follow 1 tutorial, and not several at once, hence all the mixup and problems).
Used 6-7 hours finding the solution. Thank you again. :laugh:

would method #1 work for me if im using a Galaxy S2 T989D version my phone is functional, i can go to download mode, recovery, even use the phone regularily but with RR, freezes, weird FCCs. I think its soft bricked because i cannot flash any ROMs through recovery or ODIN. i cant even ODIN back to stock 4.03 jellybean. (ODIN recognizes and passes phone but no effect).
thank you for any help

Are you flashing the right ROM for your device?
You're aware that all of these is meant for the I9100 model, right?
For more info, visit your forum.
Sent from...this is not even my S2

gastonw said:
Are you flashing the right ROM for your device?
You're aware that all of these is meant for the I9100 model, right?
For more info, visit your forum.
Sent from...this is not even my S2
Click to expand...
Click to collapse
My phone got stuck on a bootlop after installing an app.
I used the stock ICS recovery menu and selected factiry wipe and now it's absolutely dead wont charge or turn on at all.
I'm guessing there's nothing I can do to fix it?
Is it worth it to buy a jig to force it into download mode?

[Help] Fully Bricked S5 G900H. How to solve?

Actually it was fully my mistake..
I tried to flash my device to Stock firmware. But mistakenly I've used wrong region's firmware and that's why Odin failed to Pass the process..
And now my device isn't working any more..
Stuck in this message..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, whenever I push the power button, it gives me this message.
Please tell me how to solve it?

I spent the same with an S4, find the correct firmware, and reflashing again.

Masum56k said:
Actually it was fully my mistake..
I tried to flash my device to Stock firmware. But mistakenly I've used wrong region's firmware and that's why Odin failed to Pass the process..
And now my device isn't working any more..
Stuck in this message..
Now, whenever I push the power button, it gives me this message.
Please tell me how to solve it?
Click to expand...
Click to collapse
pull out the battery, put back in, go into download mode (vol down + power + home) plug in to pc, open odin, pda the correct tar. then flash.

jimalfred45 said:
I spent the same with an S4, find the correct firmware, and reflashing again.
Click to expand...
Click to collapse
Yes. Now I got the correct firmware..
But how to reflash again, as I couldn't enter in Download mode?
Whenever I try to enter in Download mode, that recovery issue appears again..
Now, Kies also not detecting my phone.

Masum56k said:
Yes. Now I got the correct firmware..
But how to reflash again, as I couldn't enter in Download mode?
Whenever I try to enter in Download mode, that recovery issue appears again..
Now, Kies also not detecting my phone.
Click to expand...
Click to collapse
use odin 3.09. you just need kies for the samsung drivers. you enter download mode by having have the phone completely turned off. (pull battery) so vol down + power + home for 10 secs at the same time. just like recovery.

Masum56k said:
Yes. Now I got the correct firmware..
But how to reflash again, as I couldn't enter in Download mode?
Whenever I try to enter in Download mode, that recovery issue appears again..
Now, Kies also not detecting my phone.
Click to expand...
Click to collapse
If you cannot enter Download mode use USB JIG

savoritz said:
use odin 3.09. you just need kies for the samsung drivers. you enter download mode by having have the phone completely turned off. (pull battery) so vol down + power + home for 10 secs at the same time. just like recovery.
Click to expand...
Click to collapse
Thanks a lot.
I've done it successfully..
Now it seems to be, my device is fully fresh. Like it took a shower.
No more root access available.. I've to Root again, right?
verny94 said:
If you cannot enter Download mode use USB JIG
Click to expand...
Click to collapse
Thanks buddy for your response..
But I don't need it anymore, solved the issue.
Sent from my SM-G900H using Tapatalk

Masum56k said:
Thanks a lot.
I've done it successfully..
Now it seems to be, my device is fully fresh. Like it took a shower.
No more root access available.. I've to Root again, right?
Thanks buddy for your response..
But I don't need it anymore, solved the issue.
Sent from my SM-G900H using Tapatalk
Click to expand...
Click to collapse
yeah, if you flashed stock rom, you need to cf auto root via odin. or if you have custom recovery. redownload superuser and reinstall the supersu into system and select cmd/trwp recovery as binary. may need to repeat last steps multiple times for it to work.

Just an FYI for future reference or if other experience this. You can still flash your firmware via ODIN when this displays on your screen.

@savoritz did yo solve your problem with your SGS5 ?

..

I have a similar problem . My phone is stuck at the startup screen . I can go into download mode and recovery mode but odin fails when I try to flash a rom , its lpg shows "NAND write Start . . . FAIL!" I have tried various odin versions , stockfirmwares , pcs and cables but the odin wont just pass . The strange thing is that odin successfully flashes custom recovery , but when I try to flash a custom rom using either stock recovery or custom recovery , during installation , the screen goes black and then returned to the main menu . Plz help me !!!! .
Update: I am sure that I placed the file in AP tab of odin and two options were checked (cant really remember them) but odin fails

.
You should be able to recover it using Samsungs Kies 3 software, go to tools/recovery and you should be able to flash it back to stock..
You could maybe boot back into download mode and re odin. I'm not sure that is possible when it's in a recovery state

waleed794 said:
I have a similar problem . My phone is stuck at the startup screen . I can go into download mode and recovery mode but odin fails when I try to flash a rom , its lpg shows "NAND write Start . . . FAIL!" I have tried various odin versions , stockfirmwares , pcs and cables but the odin wont just pass . The strange thing is that odin successfully flashes custom recovery , but when I try to flash a custom rom using either stock recovery or custom recovery , during installation , the screen goes black and then returned to the main menu . Plz help me !!!! .
Update: I am sure that I placed the file in AP tab of odin and two options were checked (cant really remember them) but odin fails
Click to expand...
Click to collapse
Use pit file and flash with odin

dposea123 said:
.
You should be able to recover it using Samsungs Kies 3 software, go to tools/recovery and you should be able to flash it back to stock..
You could maybe boot back into download mode and re odin. I'm not sure that is possible when it's in a recovery state
Click to expand...
Click to collapse
I have tried Kies but it does not detect my mobile.

fffft said:
Your device was never soft bricked, let alone fully bricked as you describe it. You made it unbootable by not being careful what you flashed. Glad you recovered, but know that you got off lightly this time.
Problem /Remedy:
Boot loop: Restore known good backup or full stock ROM from recovery mode
Unbootable, but still recognized by Odin: Flash full stock ROM with Odin in download mode
Soft brick: May require repartitioning with PIT file, followed by flashing a full stock ROM
Hard brick: JTAG (or possibly SD card bootstrap) required for repair. Usually (not guaranteed) recoverable
.
Click to expand...
Click to collapse
You are just one of all scribblers
sorry that you say it, but I got tired of watching you become lid of each pot

sorry to revive an old thread, but what if there is no available firmware for my country? what should i flash then?

shohag2018 said:
sorry to revive an old thread, but what if there is no available firmware for my country? what should i flash then?
Click to expand...
Click to collapse
what is your country

Bangladesh.

shohag2018 said:
Bangladesh.
Click to expand...
Click to collapse
SM-G900H you have ?
http://www.mrcrab.net/down-firmware/11643/Samsung-Galaxy-S5-Exynos-Octa-SM--G900H.html

S10+ now stuck on soft brick / download mode / black screen

Hi all,
xda newbe here.
I got my s10+ yesterday so Ive decided to root it and flash with custom ROM - beyondrom v5,0
what has been done in chronological steps
1. phone with stock os / bootloader locked
2. dev mode on
3. bootloader open and grayed out in stock os
4. flashing / isntalling custom recovery - twrp via odin - success
5. flashing custom rom via twrp, used usb dongle with usb key
6. aroma installer pop up as expected - ive untick apps which i dont like
6.1. then in aroma instlaller got asked something like what geo should be allocated / list of countries
6.2. i choose UK unspecified (most likely i messed up here), im located in Slovakia, i think in aroma istaller it was eastern europe option
7. ive clicked next in installer, installation went complete, aroma log saved
8. phone turn off
9. now atempt to enter recovery mode - unsuccessful
10. device immidiately boot into download mode pic no1
10.1. there is error log on the top of display in red -
Recovery: Public key used tp sign data does not match key in chain partitin desctiptor. (5)
product: Error validating footer. (6)
CUSTOM RECOVERY
VBMETA G95FXXU1AS05, 23234098A
11. not able to turn it off
11.1. after couple of hours device turn off, baterry went empty
12. connect to pc - odin - sammobile latest s10+ soft for Slovakia / TMS as the phone its from tmobile - pics no2 and no3
12.1. success, flashed with stock rom, see pic no4
12.2. device immidiate restart - boot - bang donwload mode with error log in red
product: Error validating footer. (6)
CUSTOM RECOVERY
VBMETA G95FXXU3ASG8, 24948476R
13. turned off device, bixby + vol down + cable - device on, warning, vol up, download mode with long colorfull log, but there is a red log on the botton (nAsv_TABLE: 5 I EVT 1.1 ) pic no5
Current status -
not able to turn on the phone of course
device can be turn off by instruction on download mode screen
able to enter download mode
odin recognize device
pc recognize device
as i didnt find anything related to this status i created this thread and hopefully someone of you, xda overlords, will help. Im suspicious that even after stock rom flash there is still some gap in geo support and the device ... manufacturer hardware support vs slovakia tcom soft version. Maybe Im bullshitting myself. I dont want to kill device completely.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pls advice, many thanks, your noob bunkerr

Just flash the stock firmware using odin you should be ok.
After that reinstall root..and etc.

Player04 said:
Just flash the stock firmware using odin you should be ok.
After that reinstall root..and etc.[/QUOTE
- as you can read in point 12 Ive already did a stock rom reflash. It doesnt help, or did something wrong? the phone after success in odin turn off, and then force to download mode by it self, no way to turn on phone or entry recovery mode
pls advise, thanks
Click to expand...
Click to collapse

Oh i see you flash the wrong csc file. You have to get the correct firmware country.. for me its BRI csc, so i dl bri stock firmware and flash everything (bl, ap,cp and csc) with odin

bunkrra said:
Hi all,
xda newbe here.
I got my s10+ yesterday so Ive decided to root it and flash with custom ROM - beyondrom v5,0
what has been done in chronological steps
1. phone with stock os / bootloader locked
2. dev mode on
3. bootloader open and grayed out in stock os
4. flashing / isntalling custom recovery - twrp via odin - success
5. flashing custom rom via twrp, used usb dongle with usb key
6. aroma installer pop up as expected - ive untick apps which i dont like
6.1. then in aroma instlaller got asked something like what geo should be allocated / list of countries
6.2. i choose UK unspecified (most likely i messed up here), im located in Slovakia, i think in aroma istaller it was eastern europe option
7. ive clicked next in installer, installation went complete, aroma log saved
8. phone turn off
9. now atempt to enter recovery mode - unsuccessful
10. device immidiately boot into download mode pic no1
10.1. there is error log on the top of display in red -
Recovery: Public key used tp sign data does not match key in chain partitin desctiptor. (5)
product: Error validating footer. (6)
CUSTOM RECOVERY
VBMETA G95FXXU1AS05, 23234098A
11. not able to turn it off
11.1. after couple of hours device turn off, baterry went empty
12. connect to pc - odin - sammobile latest s10+ soft for Slovakia / TMS as the phone its from tmobile - pics no2 and no3
12.1. success, flashed with stock rom, see pic no4
12.2. device immidiate restart - boot - bang donwload mode with error log in red
product: Error validating footer. (6)
CUSTOM RECOVERY
VBMETA G95FXXU3ASG8, 24948476R
13. turned off device, bixby + vol down + cable - device on, warning, vol up, download mode with long colorfull log, but there is a red log on the botton (nAsv_TABLE: 5 I EVT 1.1 ) pic no5
Current status -
not able to turn on the phone of course
device can be turn off by instruction on download mode screen
able to enter download mode
odin recognize device
pc recognize device
as i didnt find anything related to this status i created this thread and hopefully someone of you, xda overlords, will help. Im suspicious that even after stock rom flash there is still some gap in geo support and the device ... manufacturer hardware support vs slovakia tcom soft version. Maybe Im bullshitting myself. I dont want to kill device completely.
pls advice, many thanks, your noob bunkerr
Click to expand...
Click to collapse
Flash whole firmware not only ap.