Hi guys,
I think I finally failed in flashing ROMs. I tried flashing Batman Rom on my SM-G935F, everything looked fine, it started to boot, took like 5 minutes on the Samsung screen (flashing the logo) and then dimmed all the lights and finally after another minute rebooted. Ever since that whenever I try to boot it crashes after a couple of seconds in the boot screen. Either the Samsung logo comes up (drawing the letters SAMSUNG) and then it crashes while drawing the A letter or something, or the Batman ROM logo comes up and it crashes there (distorting the yellow Batman icon with horizontal black lines).
What I have tried since:
* Reflashed the Bootloader / Modem provided by Batman ROM using Odin
* Flashed again with a second download of Batman
* Flashed again Resurrection Mod which I was previously using (it was then getting stuck at the Resurrection Mod splash screen)
* Flashed original Samsung Firmware from "samsung-updates dot ru" using the MOB CSC (I'm on Austrian A1) using Odin (I flashed all BL, AP, CP, CSC at once)
After flashing the original firmware it showed a big blue Samsung screen for installing system, tried to boot and again crashed. Its now in a state where the screen appears off, the notification light is on and switching between dark and bright blue. I can't even force it to turn of anymore using any combination of Power + (imagine all possible keys here).
What can I do? Thanks a lot in advance!
EDIT: Ok - I read only that my state is called Black screen of death, but sadly I can't force reboot or anything. I could wait for the battery to drain but since it was at 100% when it happened and nothing except the status led is on and the device being very cool - I fear it might take a month or so. Somebody suggested to use a hair dryer and put the S7 in a box to heat it up in order to trigger emergency shutdown due to overheat. Do you think it might work or is there a better alternative (USB OTG cable with something that drains the power might work??).
schneida said:
Hi guys,
I think I finally failed in flashing ROMs. I tried flashing Batman Rom on my SM-G935F, everything looked fine, it started to boot, took like 5 minutes on the Samsung screen (flashing the logo) and then dimmed all the lights and finally after another minute rebooted. Ever since that whenever I try to boot it crashes after a couple of seconds in the boot screen. Either the Samsung logo comes up (drawing the letters SAMSUNG) and then it crashes while drawing the A letter or something, or the Batman ROM logo comes up and it crashes there (distorting the yellow Batman icon with horizontal black lines).
What I have tried since:
* Reflashed the Bootloader / Modem provided by Batman ROM using Odin
* Flashed again with a second download of Batman
* Flashed again Resurrection Mod which I was previously using (it was then getting stuck at the Resurrection Mod splash screen)
* Flashed original Samsung Firmware from "samsung-updates dot ru" using the MOB CSC (I'm on Austrian A1) using Odin (I flashed all BL, AP, CP, CSC at once)
After flashing the original firmware it showed a big blue Samsung screen for installing system, tried to boot and again crashed. Its now in a state where the screen appears off, the notification light is on and switching between dark and bright blue. I can't even force it to turn of anymore using any combination of Power + (imagine all possible keys here).
What can I do? Thanks a lot in advance!
EDIT: Ok - I read only that my state is called Black screen of death, but sadly I can't force reboot or anything. I could wait for the battery to drain but since it was at 100% when it happened and nothing except the status led is on and the device being very cool - I fear it might take a month or so. Somebody suggested to use a hair dryer and put the S7 in a box to heat it up in order to trigger emergency shutdown due to overheat. Do you think it might work or is there a better alternative (USB OTG cable with something that drains the power might work??).
Click to expand...
Click to collapse
Can you boot into recovery? first press & hold home, volume up and power button till phone reboots - can take quite a while like >10 secs. When the phone reboots hold the same button combination. If you are lucky you get into recovery either custom or stock. Then try to do a factory reset.
if that fails try to flash another Samsung firmware. Was the first flash successful? What did Odin report? Was the MD5 check okay? Maybe you had a bad download?
Looks like you messed up your phone pretty good!! Good luck LJ
Thanks for your input!
I was unable to restart the phone but eventually it ran out of battery late last night. I was not able to get into recovery after that - "No command", so I reflashed the original ROM (SM-G935F_1_20170526154229_v748mkzo6s_fac) using Odin again. This was the Odin output:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem_debug.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After that I rebooted and it briefly showed "Installing system update" followed by "Erasing" followed by the Samsung logo being drawn on the screen. The logo illuminated once after that the screen went black and it rebooted. I let it reboot a couple of times but it never finished booting (it always got stuck trying to draw the SAMSUNG logo see imgur.com/a/26sGU). I tried to get into recovery mode in this state (by using Power + Home + Volume up) which led me again to "Installing system update" and two arrows within an android icon, but these stopped moving after a couple of seconds and after two minutes I shut down the phone again.
I have flashed TWRP again and I can get into TWRP recover now - so I think not all is lost!
Is there an alternative ROM that I should try to flash - something smaller or more reliable or something? Also - do I need to enable any of those options in Odin (like Re-partition)?
Thanks!
EDIT:
Ok I've tried flashing Superman ROM this time from TWRP - I followed the instructions very very closely but I ended up with this: imgur.com/a/haHa1
(please add http:// in front of the link)
schneida said:
Thanks for your input!
I was unable to restart the phone but eventually it ran out of battery late last night. I was not able to get into recovery after that - "No command", so I reflashed the original ROM (SM-G935F_1_20170526154229_v748mkzo6s_fac) using Odin again. This was the Odin output:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> cm.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem_debug.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> hidden.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After that I rebooted and it briefly showed "Installing system update" followed by "Erasing" followed by the Samsung logo being drawn on the screen. The logo illuminated once after that the screen went black and it rebooted. I let it reboot a couple of times but it never finished booting (it always got stuck trying to draw the SAMSUNG logo see imgur.com/a/26sGU). I tried to get into recovery mode in this state (by using Power + Home + Volume up) which led me again to "Installing system update" and two arrows within an android icon, but these stopped moving after a couple of seconds and after two minutes I shut down the phone again.
I have flashed TWRP again and I can get into TWRP recover now - so I think not all is lost!
Is there an alternative ROM that I should try to flash - something smaller or more reliable or something? Also - do I need to enable any of those options in Odin (like Re-partition)?
Thanks!
EDIT:
Ok I've tried flashing Superman ROM this time from TWRP - I followed the instructions very very closely but I ended up with this: imgur.com/a/haHa1
(please add http:// in front of the link)
Click to expand...
Click to collapse
I think this is a hardware issue and is not software related...
I don't know if you have come right in the meantime or given up completely?!
There is still one thing you could try. A guy on the BatmanROM thread reported a similar problem. If you can boot into TWRP you could try to reformat the partitions on your internal SD card. If that fails too than your only option is to take your phone to Samsung and see if they can help you.
My feeling is, after reading through various threads, that people flash ROMs, kernels, mods whatever they get their hands on. That probably creates lots of left-over rubbish on the SD card. Eventually, the partitions gets corrupted.
If you ever get your phone back into a normal state, I suggest be happy and leave it like that. Good luck! LJ
I've had the same problem...
Mine was on about 90% battery... took about 12 hours to discharge.
once it was dead i put it on charge and it came back to life but not without it's problems.
When I rebooted , it kept freezing on the samsung logo (Logo sort of digitised)
so what I done was to use smart switch and did an emergency restore.... all seems good now...
Sidenote.... Take out sd card doing restore
Good luck!
Hey - thanks for your support! Out of desperation I took my device to Samsung Repair Center and to my surprise they replaced the motherboard and even changed the battery without charging me anything at all!
Everything is working now - I think I'll keep away from custom ROMS, I hope the temptation doesn't come back too soon!
Related
Got a the T959W from CL. User said is was borked. It powered on, but capacitive keys didn't work. Was extremely unresponsive.
Tried The T959V Heimdall One-Click Collection
Failed after modem upload and booted up. Tried this 3x then tried checking Flash Bootloaders.
Then I could only get in in download mode.
Next I tried this thread ( GB Ext4 Starter Pack)
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> pda.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
(obviously it didn't work so I gave it another shot)
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> pda.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/004> Removed!!
Now I can't get it into Download mode. I paid $30 for it so if it's not worth fixing I'm not going to lose sleep over it, but if you have some sort of great idea I'm all ears.
Tried three button combo after letting it sit with the battery out for a while. Saw the screen before the 'Downloading' screen that tells you to press vol + or -. Pressed vol - and then screen went black again.
On another good note I have lots of fresh good batteries since I have a i897 with 2 extra batteries.
You unfortunately utilized many threads except the one's for your specific phone model. Flashing your phone with the bootloaders for the T959V was not a good idea.
Fortunately a couple of people are working hard to make a One-Click with bootloaders for your phone. Hopefully if/when they finish that will take care of your problem.
http://forum.xda-developers.com/showthread.php?p=32943946
http://forum.xda-developers.com/showthread.php?p=32787863
http://forum.xda-developers.com/showthread.php?p=32901489
Many people on here have been successful flashing on phones that appear like they are not turning on. When the one-click package is ready hopefully we can help you with that.
If you can get into download mode (thought it was vol+ not vol-), it should be able to be fixed. PM me and I can help. I have the needed files to get it going, still waiting on Heimdall to be fixed to do a 1 click, so I'm not releasing anything yet but I've saved several phones so far for other users.
My friend has a Samsung GT-S6102 and he tried to flash a custom firmware without pre-rooting the phone. The phone was stuck in bootloop and he gave the phone to me for repair because I have been flashing phones like my Xperia mini pro and Samsung Monte, etc.
However, this is the first time I had to use Odin to do something like this. As per my experience so far, the most difficult part is to find the right firmware for this phone (I require the Indian firmware). So, after lots of brainstorming in the XDA forum I flashed these files (a) BOOT_S5360DDKK1_REV05.tar (b) torino_1205.pit (c) PDA, Phone and CSC files from S6102_DDMC1_ODDMB1_DDMC1. Now after successfully completing the flash process the phone still goes to bootloop and the Samsung Galaxy logo appears upside down (mirror image). I am attaching the screenshot here for your reference. Moreover, I cannot view the download mode because of white screen when I press volume down+home+power keys. But I can still reflash following the steps as it would if it was normal.
Here's the odin flash log.
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> PDA_S6102_DDMC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MODEM_S6102_DDMC1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_S6102_ODDMB1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> BcmBoot.img
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> param.lfs
<ID:0/008> system.img
<ID:0/008> userdata.img
<ID:0/008> BcmCP.img
<ID:0/008> Transmission Complete..
<ID:0/008> Now Writing.. Please wait about 2 minutes
<ID:0/008> Receive Response from boot-loader
<ID:0/008> csc.rfs
<ID:0/008> RQT_CLOSE !!
<ID:0/008> RES OK !!
<ID:0/008> Removed!!
<ID:0/008> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Any help would be greatly appreciated. Please note that this phone is not rooted so can't go to CWM either.
So, frustrating... somebody got to have a way to revive this bricked phone.
Can somebody tell me how to root and to flash a custom kernel on an already bricked phone.....?
From the screenshot it shows that the odin version is not correct (Its for galaxy grand)
Try using Odin 3v1.8
For firmwares
Go here
Sent by typing by my fingers
@AMIT
Thank you very much for your reply Amit but I'm afraid that it's not going to work either. I've also used the older version of odin the one that you mentioned but with no luck. My only chances are if I can somehow alter the root permission and flash a custom kernel and then flash a new rom. However, I've searched many forums but nobody knows anything about rooting an already bricked phone.
It's quite easy otherwise to root a phone that's in a working condition. So sad...
Anyways, thanks a lot buddy....
Withe Screen on GT-S6102
Hello people
I'need a little help
I was trying to apply a monster rom to my girlfriend galaxy y duos.
Then it reboot and I could see the Monster boot animation but with the picture all mess up.
Then I enter in to Recovery mode an the menu was also mess up.
finaly I could enter with the odin 3 an flash the CSC_S5360_ODDLK1 pack (3 files)
then After reboot all I have is a with screen.
I can go in recovery menu or download menu, at least that I see, because all I see is a the withe screen
Can somebody help to riveve this brick
Thanks
I have a stock Galaxy note 10.1 NT8010, i hadnt used it in a few days. Went to power on and wouldnt boot. Thinking it was dead i charged it for a few hours and still wouldnt turn on. The power brick is fine, i bought a new stock cable, just waiting for that to come and rule out the cable. But its stock android no rooting or anything.
Any ideas?
Battery shows as charging ??
Odin mode ??? or Recovery Mode ???
JJEgan said:
Battery shows as charging ??
Odin mode ??? or Recovery Mode ???
Click to expand...
Click to collapse
Thanks for replying. Screen is completely dead not even a backlight.
For odin to work would i have to have it rooted previously?
For odin to work would i have to have it rooted previously?
No it does not require root .
JJEgan said:
For odin to work would i have to have it rooted previously?
No it does not require root .
Click to expand...
Click to collapse
Ok, so the pc is not picking it up at all.
I took off the back cover, disconnected the battery and reconnected.
Plugged it into the charger while the cover was still off. On the top left its making a "ti-ti-ti" noise while plugged into power.
Im guessing the motherboard/battery/screen are/is dead. Well one of the 3.
Any ideas?
amsung Tab GT-N8010 Rom doesn't Install, PIT issue, Flashing Screen, do not turn ON
I have Samsung Tab GT-N8010
When I try to turn on, its screen flashing White for half second and then Black and Continuosly till the Battery End.
I try to Install ROM 4.4.2 with ODIN 3.10.7 and get this error
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried different PIT files including 3 different N8010.pit and 8013.pit and 8020.pit
but the issue remaining same
I read all the google search including Russian websites at-least but I couldn't find the issue
I have original cable
EMMC Corrupted may be
I need Solution plz help if anyone can
rehansonu said:
amsung Tab GT-N8010 Rom doesn't Install, PIT issue, Flashing Screen, do not turn ON
I have Samsung Tab GT-N8010
When I try to turn on, its screen flashing White for half second and then Black and Continuosly till the Battery End.
I try to Install ROM 4.4.2 with ODIN 3.10.7 and get this error
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried different PIT files including 3 different N8010.pit and 8013.pit and 8020.pit
but the issue remaining same
I read all the google search including Russian websites at-least but I couldn't find the issue
I have original cable
EMMC Corrupted may be
I need Solution plz help if anyone can
Click to expand...
Click to collapse
same problem here! need help!!!!!
rehansonu said:
amsung Tab GT-N8010 Rom doesn't Install, PIT issue, Flashing Screen, do not turn ON
I have Samsung Tab GT-N8010
When I try to turn on, its screen flashing White for half second and then Black and Continuosly till the Battery End.
I try to Install ROM 4.4.2 with ODIN 3.10.7 and get this error
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried different PIT files including 3 different N8010.pit and 8013.pit and 8020.pit
but the issue remaining same
I read all the google search including Russian websites at-least but I couldn't find the issue
I have original cable
EMMC Corrupted may be
I need Solution plz help if anyone can
Click to expand...
Click to collapse
Same problem here!!!! Service center says Motherboard replacement!!! Please help.
Hello,
A bit of back story first - yesterday, my mother's Galaxy S6 (SM-G920F) suddenly rebooted to the device's logo screen ( the "Samsung Galaxy S6....powered by android" one) and it's been stuck there since. There had been no "tinkering" so to say with the device; debugging was disabled, the bootloader had not been tampered with at all, and all the updates were done through the official android route. The last major update was around a month ago, to Nougat from MM, after which I cleared the cache. The latest update was about 10 days ago, a minor Nougat one, but the cache had not been wiped.
Now down to business. The phone does not turn off at all. Holding the power button and the volume down just reboots it to the same screen. That being such, I cannot access recovery mode. I can however access Download Mode which makes be believe that all hope is not lost.
Using Odin, I attempted to flash a stock ROM, which for this model was Android v5.1.1, and now I understand why that wouldn't work. At this point instead of the logo screen, it showed a blue screen saying something along the lines of "An error has occurred while updating your phone, please use Smart Switch emergency recovery". I had tried to connect to smart switch before but it wouldn't recognize the device. I was saving initialization as a last resort.
I then flashed the most recent MM ROM for this model (which I found on sammmobile) using Odin, having read it was possible to still downgrade, and believing that perhaps Nougat was causing this problem. And it was successful, except the phone now returned to the logo screen. Again, with the same problems as before. And I still couldn't wipe the data and cache because I still couldn't access recovery mode.
Finally I connected the phone to Smart Switch and chose to initialize it. After going through all the steps, and downloading the files, it said it was successful but the phone is still stuck at the damn logo screen. I can still access download mode for what it's worth but I haven't a clue now as to what I should do next.
Any help or suggestions would be greatly appreciated. Thanks.
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
Model: SM-G920F
Region: PHN
Auto: Selected
Manual: Unselected
Binary Nature: Selected
Check CRC32: Selected
Decrypt automatically: Selected
When you write and select options given above, press "Check Update" and then press "Download" to download factory firmware for your device.
Once the download has been finished, extract the zip file that you've downloaded via SamFirm.
After unzip it, download and run this Odin (even if you have another one);
https://forum.xda-developers.com/attachment.php?attachmentid=3804544&d=1467772303
When you open it, press BL and select file which starts with BL from downloaded (from Samfirm) and extacted zip folder.
Do the same thing for AP, CP, CSC.
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
If this method doesn't fix you issue, you have to replace the motherboard then.
no luck
forumber2 said:
Download and run this;
https://forum.xda-developers.com/attachment.php?attachmentid=3803841&d=1467715462
When you open the program, type the values given here;
...
When you set 4 files to Odin, connect your phone to your PC in download mode and click "Start" on Odin.
If this method doesn't fix you issue, you have to replace the motherboard then.
Click to expand...
Click to collapse
thank you so much for your answer but it does not seem to have worked. I did everything as instructed but I'm not quite sure as to why this is happening exactly. This is the log from Odin, maybe it'll help:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> userdata.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
(when it said "please wait about two minutes" it actually proceeded to the next step very quickly)
It appears to have loaded successfully but it is still stuck at the logo screen. Could you please explain why this not working would mean I would have to replace the motherboard? Thank you once again
(also I'm running Odin with only "Auto Reboot" and "F.Reset Time" ticked, don't know if that will help)
rayofmoonshine said:
thank you so much for your answer but it does not seem to have worked. I did everything as instructed but I'm not quite sure as to why this is happening exactly. This is the log from Odin, maybe it'll help:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> cm.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> userdata.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
(when it said "please wait about two minutes" it actually proceeded to the next step very quickly)
It appears to have loaded successfully but it is still stuck at the logo screen. Could you please explain why this not working would mean I would have to replace the motherboard? Thank you once again
Click to expand...
Click to collapse
Odin log says that there's no problem.
The produce I've wrote above is the last think you can do on new Samsung devices.
forumber2 said:
Odin log says that there's no problem.
The produce I've wrote above is the last think you can do on new Samsung devices.
Click to expand...
Click to collapse
Do you have any idea what could have caused this issue? Would changing the motherboard be guaranteed to fix this and if so, how?
rayofmoonshine said:
Do you have any idea what could have caused this issue? Would changing the motherboard be guaranteed to fix this and if so, how?
Click to expand...
Click to collapse
Replacing motherboard will not help You unless You have a way to program EFS and IMEI information to it.
Samsung SGH-T779 (Galaxy Tab 2 T-Mobile)
Hey team, I've spent several hours trying to work through what's going on with this Galaxy Tab 2 which my Dad wanted to give to my son.
Here's the status of the tablet. It hasn't been regularly used for years. When plugged in you get mostly non-responsiveness. BUT, after charging it for a few days, you can unplug it and then it will allow you to try Odin mode (power + volume down) and it FAILS to try recovery mode (holding power + volume up).
Firstly, when it tries to go into recovery mode, the top left blue wording appears "booting recovery" and then regardless of how long or I continue to hold vs. releasing the power button and up volume, it goes black and then goes into a kind of boot loop where it'll flash a stagnant "SAMSUNG" logo, then go dark and freeze on a kind of "glowing" but not changing SAMSUNG logo. I can press the power button and it'll go off, and then boot up to the two SAMSUNG logos again, but stays frozen there indefinitely.
Unable to factory reset from recovery mode, I've gotten the tablet into Odin Mode. I have used https://forum.xda-developers.com/t/...-versions-samsung-rom-flashing-tools.2189539/ for my guide to which Odin version (primarily 1.85, but I've tried 3.04, 3.06, 3.07 just to see if they worked better.) I've used this guide to help with the logistics of flashing the stock firmware: https://forum.xda-developers.com/t/guide-odin-flash-guide.1671969/
The TAR files I'm using are from https://samfw.com/firmware/SGH-T779/TMB/T779UVTMF4 and show the following file names.
BOOTLOADER_T779UVTMF4_1255797_REV00_user_low_ship.tar.md5
CSC_TMB_T779TMBMF4_1255797_REV00_user_low_ship.tar.md5
MODEM_T779UVTMF4_1255797_REV00_user_low_ship.tar.md5
PLATFORM_T779UVTMF4_1255797_REV00_user_low_ship.tar.md5
I've been plugging the Platform file into the PDA slot, since there's not a PDA/Code in the file packet. I get the following message thread when running:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_T779UVTMF4_1255797_REV00_user_low_ship.tar.md5 is valid.
<OSM> PLATFORM_T779UVTMF4_1255797_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_T779UVTMF4_1255797_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_TMB_T779TMBMF4_1255797_REV00_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also tried the file here: https://a2zrom.com/samsung-sgh-t779-firmware which only has one file named:
T779UVTMF4_T779TMBTMF4_T779UVTMF4_HOME.tar.md5
I plugged this into the PDA slot and the result was the following message thread:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T779UVTMF4_T779TMBTMF4_T779UVTMF4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any direction here would be tremendously appreciated!
The only other information I can offer is that occasionally I HAVE had the SAMSUNG logo loop stall out at a greyed out horizontal battery symbol with a greyed out circle of "sun rays" before it goes black for good.
Any assistance would be greatly appreciated!
Thanks XDA wizards.
aamccarty
Same situation here. I think i will smash it with a hammer
Stay tuned, maybe we'll figure it out together.
First, don't use win 10 or 11, use win7 or Linux for flashing!!!! Than try again...
Maybe its EMMC bug aka flash chip is dead. But you can try flashing ROM with pit file for your model (don't use any others).