Hi,
I'm trying to install stock firmware on my SM-925F through Odin and the process keeps failing at cm.bin, having read about this it indicates i'm using the incorrect firmware. I've tried downloading various different ones through Samsung-updates and none of them seem to work.
How am I meant to know which is the correct one to use? The phone will not boot so I can't go into it and find out the build number etc.
Any help would be appreciated.
Just to add, when it fails, the phone in download mode reads "Error SW REV Check Fail Device 5 Binary 4"
Managed to get some firmware to install by removing sboot.bin & cm.bin, think it was the latest XEU version. Every time I try to flash sboot.bin by itself under CP of Odin it says:
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004>
<ID:0/004> Receive Response from boot-loader
<ID:0/004> Complete(Write) operation failed.
Hi there, I have a Samsung G925F only booting to Samsung logo, I tried different roms using latest Odin but it keep failing. Any advice on this?
Related
Guys help..
I was trying to get my phone back to basic and I tried to install an official firmware by using odin 3, and it failed..
Now I am stucked???
My phone failed and know its saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again"
What to to??
what does the log say?
Glebun said:
what does the log say?
Click to expand...
Click to collapse
log???
yes, the Odin log.
Sivasli_ said:
Guys help..
I was trying to get my phone back to basic and I tried to install an official firmware by using odin 3, and it failed..
Now I am stucked???
My phone failed and know its saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again"
What to to??
Click to expand...
Click to collapse
Before flashing, make sure you have all necessary drivers installed and that you have more than 50% (30% is the absolute minimum) of battery left. Then download a ROM (I.e. from sammobile.com/firmware) and make sure that is is the right ROM for your device. If you download something that is for a different device, you may end up bricking it.
Then boot your phone into Odin mode (I think you know how to do that?) and connect the phone to your PC. Wait for the PC to recognize the device as a serial CDC (That's what Windows 7 and Vista usually show) and then wait for Odin to recognize the device. Then (If you have not already) load all the files into Odin (PDA - ROM and kernel, Modem - Phone, CSC - CSC) and hit "Start".
Then it should download fine. If you are still having trouble, feel free to PM me and I'll gladly help via TeamViewer
Lg
Sound to me like Kies was running in the background while you made the Odin flash.....you must disable Kies before using Odin
No Kies was not running in the backgorund..
Could it be, because I was going from 4.1.2 down to 4.0.1 for example? It is a old firmware..
I solved my problem with installing an Omega Rom v43, but I still want to back to original firmware..
what does the log say?
I dont now how to look at the log..
Can I just flash the original firmware even that I am on a Omega firmware?
Glebun said:
what does the log say?
Click to expand...
Click to collapse
Here is what the log says..
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004> sboot.bin
<ID:0/004> system.img
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
Sivasli_ said:
No Kies was not running in the backgorund..
Could it be, because I was going from 4.1.2 down to 4.0.1 for example? It is a old firmware..
I solved my problem with installing an Omega Rom v43, but I still want to back to original firmware..
Click to expand...
Click to collapse
The new 4.1.2 bootloader (I assume you have it, unless you specifically replaced it with the older one) will blacklist older bootloaders and prevent them from being installed. This might be part of the problem.
I have the i9300 but when I boot up into download mode it says PRODUCT NAME: SGH-T999 (not my model, though). I think this is because I accidently installed the SGH-T999 version of cyangomenod.
So to try to fix it, I used odin 3.07 and the
"I9300ZSEMC1"
stock rom file to try to put it back onto stock. Odin "stopped working" and crashed and I soft-bricked my phone (Firmware upgrade encountered an issue message at boot).
I tried again using I9300XXEMC3 stock rom, but odin 3.04 says
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> tz.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And fails. My phone says "unsupported dev_type" in red.
Can I please get some guidance? I don't know what I did wrong. What rom should I flash with odin? Should I try to flash the SGH-T999 stock rom with odin?
zhinkk said:
I have the i9300 but when I boot up into download mode it says PRODUCT NAME: SGH-T999 (not my model, though). I think this is because I accidently installed the SGH-T999 version of cyangomenod.
So to try to fix it, I used odin 3.07 and the
"I9300ZSEMC1"
stock rom file to try to put it back onto stock. Odin "stopped working" and crashed and I soft-bricked my phone (Firmware upgrade encountered an issue message at boot).
Can I please get some guidance? I don't know what I did wrong. What rom should I flash with odin? Should I try to flash the SGH-T999 stock rom with odin?
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=2535367
Hope it help.
TheoDores said:
Try this: http://forum.xda-developers.com/showthread.php?t=2535367
Hope it help.
Click to expand...
Click to collapse
I tried following those instructions. I managed to flash the .PIT file. Now I don't see the error message at boot, my screen is just black. BUT I can "sorta" boot into recovery mode (starting recovery message shows for one second, then black screen again). So I'm still stuck.
I can STILL boot into download mode though. And if I try to use CF-Root Odin fails again (same error) and my phone says "unsupported_devtype".
Flash stock rom via Odin .
But flashing a wrong firmware for a different phone may well be a lot more than a soft brick
Did you also flash wrong recovery ???
JJEgan said:
Flash stock rom via Odin .
But flashing a wrong firmware for a different phone may well be a lot more than a soft brick
Did you also flash wrong recovery ???
Click to expand...
Click to collapse
Everytime I flash the stock rom odin fails and phone says "unsupported dev_type". In Download mode it says my phone model is T999, but it's actual GT-I9300.
And I don't think I did. I think I had clockwork mod recovery, I'm not too sure though.
You have flashed at least the T999 bootloader, which is why it says that in download mode. If flashing a full i9300 stock rom doesn't help then you'll need a new motherboard.
boomboomer said:
You have flashed at least the T999 bootloader, which is why it says that in download mode. If flashing a full i9300 stock rom doesn't help then you'll need a new motherboard.
Click to expand...
Click to collapse
That really depresses me. Are you sure this is the only solution? Because I remember when my phone WAS working I booted into download mode once and it said the same "T999 Model" and I could still use it. This only happened after I tried flashing the stock i9300 stock rom.
I think it's the cyanogenmod installer that flashed this T999 bootloader for me. When I used the cyanogenmod installer it detected my phone as a AT&T phone and I was dumb enough to click "install" thinking it would work for all galaxy S3's.
I think this guide is exactly what I need (since it restores bootloader), but I can't seem to complete all the steps: http://forum.xda-developers.com/showthread.php?t=2535367
I get to #5 but once I try to install CF-ROOT through odin it says the same unsupported dev type error on my phone.
This is the error I get when trying to use CF-ROOT through Odin3 v1.85:
<ID:0/004> Added!!
<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> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> cache.img
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
(along with the red "Unsupported dev_type" on my phone in download mode).
I think it was already rooted though, maybe someone could help me reinstall the recovery (cwm) so I can install the bootloader from that guide I just linked?
Best option is to try a rescue firmware, which might help:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=8215224728919566
Sent from my GT-I9300 using Tapatalk
boomboomer said:
Best option is to try a rescue firmware, which might help:
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6&nocache=1&z=8215224728919566
Sent from my GT-I9300 using Tapatalk
Click to expand...
Click to collapse
Will this delete my EFS? I remember I backed up efs with this guide: http://forum.xda-developers.com/showthread.php?t=1852255
I did: "adb reboot nvbackup"
By restoring to "complete" factory settings, won't this efs be deleted? Can I still backup my efs in my 'soft brick' mode I'm in?
Alright, I've tried using the rescure firmware and all the files, but every time I try I get it a FAIL on odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BOOTLOADER_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CODE_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> MODEM_I9300XXEMG4_1314436_REV00_user_low_ship.tar.md5 is valid.
<OSM> CSC_I9300OXAEMG4_KOR_FACTORY_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And my phone says in red "SECURE CHECK FAIL : PIT".
I've spent 12 hours on this now...
Did you try Kies yet?
Do you still have a custom recovery?
I'm not sure about that adb nvbackup you have done. As far as i know it's only for Qualcomm chipsets not Exynos. Maybe you have severely damaged the device. But try Kies first or if you still have root access with recovery try to flash the bootloader manually.
If everything fails contact the low level guys like @AdamOutler or @Entropy512. They might be your last hope.
DualJoe said:
Did you try Kies yet?
Do you still have a custom recovery?
I'm not sure about that adb nvbackup you have done. As far as i know it's only for Qualcomm chipsets not Exynos. Maybe you have severely damaged the device. But try Kies first or if you still have root access with recovery try to flash the bootloader manually.
If everything fails contact the low level guys like @AdamOutler or @Entropy512. They might be your last hope.
Click to expand...
Click to collapse
I tried Kies on two different computers, but whenever I connect my S3 it just says "connecting" forever and never connects to my phone. Tried solutions online, couldn't get it to work.
And I have root access, but can't boot into recovery (says "recovery booting" for a few seconds then goes black screen). So I don't know if I can flash the bootloader manually, unless I did it with odin.
And those seem like busy developers, would they really have time for me? I don't even know what I would ask. :S
Sorry I seem so clueless, I'm just upset/sad/confused/everything right now. Saved up for this phone for a while.
Try to flash the bootloader only. There are different ones. Maybe you need one that is not blacklisted if that's even possible.
Last option that comes to my mind is an external jtag flasher. Maybe you have a local service shop or similar in your area that could help with that.
DualJoe said:
Try to flash the bootloader only. There are different ones. Maybe you need one that is not blacklisted if that's even possible.
Last option that comes to my mind is an external jtag flasher. Maybe you have a local service shop or similar in your area that could help with that.
Click to expand...
Click to collapse
Hmm when I had a functional phone it said I had the ZSEMC1 stock rom, so the "bootLoader_ZSEMC1.tar.md5" flashed from odin should work? I got it off this thread: http://forum.xda-developers.com/showthread.php?t=2189063
But I don't know if I'm still on ZSEMC1 since I flashed XXEMC3 with odin (but I think it failed) and I got soft bricked.
What could go wrong? Could I hard brick it by installing that bootloader?
I have no clue but i think all I9300 bootloaders would be ok. Your problem probably is rather to find one that gets accepted. Try the latest one for I9300. There is a thread with different bootloaders somewhere here i guess.
Also try to flash a custom recovery like twrp or cwm. I'm not sure if official tools like odin have a separate bootloader check that prevents cross model flashing. No one really knows how you did that. Maybe it's necessary to be done with dd.
DualJoe said:
I have no clue but i think all I9300 bootloaders would be ok. Your problem probably is rather to find one that gets accepted. Try the latest one for I9300. There is a thread with different bootloaders somewhere here i guess.
Also try to flash a custom recovery like twrp or cwm. I'm not sure if official tools like odin have a separate bootloader check that prevents cross model flashing. No one really knows how you did that. Maybe it's necessary to be done with dd.
Click to expand...
Click to collapse
I tried the ZSEMC1 and XXEMC3 and XXEMG5 bootloaders from this thread and they didn't work: http://forum.xda-developers.com/showthread.php?t=2189063
(shows unsupported dev type)
How do I get the 'latest' boot loader? That thread is the only one I could really find.
And also I did try installing cwm through odin. It didn't "fail" but it doesn't work when I try to boot into recovery. I'm guessing this has to do with my locked bootloader?
Really don't know what to do at this point. :/
New motherboard if you have tried the fixes .
Check if 'adb shell' is working in recovery nevertheless. Maybe it's just a display issue in cwm. Also try twrp.
If all that fails go to a mobile shop near you asking for a jtag flash. It shouldn't be too expensive or something. Hardest part is probably to find one locally...
DualJoe said:
Check if 'adb shell' is working in recovery nevertheless. Maybe it's just a display issue in cwm. Also try twrp.
If all that fails go to a mobile shop near you asking for a jtag flash. It shouldn't be too expensive or something. Hardest part is probably to find one locally...
Click to expand...
Click to collapse
I tried cwm and twrp. They both install successfully on odin but have the same "recovery starting...." message and they don't work. I've tried connecting the USB when it's in this "recovery" mode but my computer doesn't detect it so I can't start up adb and interface with it.
And also, I doubt I'm going to be able to find any in northwest ohio.I wonder if this service is any good?
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Looks promising for $50.
Sorry I've been on this problem for so long guys, I'm just stubborn and can't get over the fact that it's a software brick and I need to replace hardware. :/
Hi, please can you suggest what else I can try to fix this phone.
I have Samsung S3 GT-I9300
It was working fine but suddenly, I turned it on and It is stuck on the Samsung LOGO forever.
It doesn't go to recovery mode when pressing HOME+VOL UP+POWER.
But I could go to Download mode. however Odin fails to install CWM and TWRP
this is download mode:
ODIN MODE
PRODUCT NAME:GT-I9300
CUSTOM BINARY DOWNLOAD:YES (9counts)
CURRENT BINARY: Custum
SYSTEM STATUS:Custom
I tried to install official recovery but it fails too
Code:
<ID:0/022> Added!!
<ID:0/022> Odin v.3 engine (ID:22)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Get PIT for mapping..
<ID:0/022> Firmware update start..
<ID:0/022> SingleDownload.
<ID:0/022> recovery.img
<ID:0/022> NAND Write Start!!
<ID:0/022> FAIL!
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
although it fails It says : Current binary: samsung Official .
ODIN MODE
PRODUCT NAME:GT-I9300
CUSTOM BINARY DOWNLOAD:YES (9counts)
CURRENT BINARY: Samsung Official
SYSTEM STATUS:Custom
but the problem remain the same, NO RECOVERY MODE, and still the same LOGO stuck screen.
Please Any suggestions... .??
Try the rescue firmware thread in general forum, using a pit file. Also, downgrading the bootloader might help flash to work.
boomboomer said:
Try the rescue firmware thread in general forum, using a pit file. Also, downgrading the bootloader might help flash to work.
Click to expand...
Click to collapse
Thanks for your reply .
Just before I start flashing, I want to confirm things as I am a newbie.
I have downloaded FIRMWARE FACTORY 4.1.2
GT-I9300XXEMG4_KOR_MULTI_FACTORY
from this link.
http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
Do I have to check Re-partition box too beside auto reboot and F. Reset time?
About downgrading, I don't really know which bootloader I have.
Depend on what version firmware you were on before 4.1 or 4.3. Follow the instructions in that thread.
Downgrade bootloader to BLFB, search for it.
boomboomer said:
Depend on what version firmware you were on before 4.1 or 4.3. Follow the instructions in that thread.
Downgrade bootloader to BLFB, search for it.
Click to expand...
Click to collapse
Odin fails to install again. with Re-partition selected :/
Can you please point me to this BLFB , there are bunch of threads but nothing is clear.
I appreciate your help a lot
I screwed it more trying to install this Bootloader_XXELLA_Odin.tar
now it show this message
"firmware upgrade encountered an issue. please select recovery mode in kies and try again"
i45.tinypic.com/27y2tmd.jpg
please any advices, I am still able to go download mode
1. Downgrade bootloader
2. Flash stock firmware
If the bootloader flashed correctly, then try step 2.
The bootloader you used is not ideal, I don't know if that still has the problem but it might work.
boomboomer said:
1. Downgrade bootloader
2. Flash stock firmware
If the bootloader flashed correctly, then try step 2.
The bootloader you used is not ideal, I don't know if that still has the problem but it might work.
Click to expand...
Click to collapse
because I don't know which or where to find or how to know the right bootloader to install I screwed it more.
can you please give me a link of the bootloader that I am supposed to flash?,
this is is my phone info it may help.
this is my phone: vgy.me/rCuQQD.jpg
this is what kies, show when I try to install firmware: vgy.me/nTicsC.jpg
(it's a real Samsung although it was made in china )
I don't have any links, don't use kies as it just breaks Odin.
boomboomer said:
I don't have any links, don't use kies as it just breaks Odin.
Click to expand...
Click to collapse
I just installed kies after I got this message "firmware upgrade encountered an issue. please select recovery mode in kies and try again"
but it didn't work.
I think there is no luck with this phone !!!! : (
Thanks for your help anyway.
[SOLVED]EDIT:
Here is how I solved the problem. I a xda thread I found a similar problem and someone claiming this:
-Downloaded stock firmware and extracted files
-removed .md5 off the end and extracted it again
-inside should be boot.img cache.img recovery.img system.img etc.
-used Unified Android Toolkit to create individual flashable files of each file
-flashed them in the order they came
-everything passed
Click to expand...
Click to collapse
So I tried it, and it worked till the last .tar with the system.img in it. Here I had to switch USB cables from the original Samsung one to my Usb cabel from the Amazon Fire Stick. And then it also worked. For the flashing I used Odin 3.10.6 and the firmware was the G925FXXU2COH2 one. I deactivated Auto-reboot in Odin and after flashing each file I manually restarted the phone to Download mode by holding Vol down + Home + Power.
/[SOLVED]Edit
Hey guys,
this is my current situation: Phone is stuck in cyan screen with "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software". I can't use Smart Switch because I was rooted and on "XtreStoLite Deo-Mod Edition 2.3" when the phone bricked. ODIN does recognize the phone. I used Odin3 v3.10.6.
What I did to brick it:
- Downloaded a firmware and tried to flash it to unroot the phone, following that guide
http://forum.xda-developers.com/galaxy-s6/general/how-to-unroot-unbrick-galaxy-s6-t3110608
Model SM-G925F
Model name GALAXY S6 Edge
Country Germany
Version Android 5.1.1
Changelist 5599585
Build date Wed, 12 Aug 2015 08:11:31 +0000
Product code DBT
PDA G925FXXU2COH2
CSC G925FDBT2COH3
Click to expand...
Click to collapse
Since I was on "XtreStoLite Deo-Mod Edition 2.3" the device had the XXU2COH2 BL and stuff (I guessed)
- ODIN failed directly after NAND Write Start!!
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
What I tried to fix the problem:
- Flashing TWRP form http://forum.xda-developers.com/gal...p-recovery-2-8-7-1-g925f-android-5-1-t3144866 --> Fails
-Flashing G925FXXU2COH2 stock firmware and G925FXXU2BOGB_G925FDBT2BOG8_DBT (from http://stockroms.net/file/GalaxyS6Edge/SM-G925F/Germany/5.1.1/G925FXXU2BOGB_G925FDBT2BOG8_DBT.zip)
- After finding this http://forum.xda-developers.com/galaxy-s6-edge/help/guide-s6-edge-unbrick-guide-t3187655 and some other threads I removed the hidden.img from both firmwares I already tried, repacked them and flashed with ODIN.
---> modified G925FXXU2BOGB_G925FDBT2BOG8_DBT fails after flashing modem
----> modified G925FXXU2COH2 fails like this:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
Sooo.. according to the guide I mentionied I would need to flash pit and Stock firmware at once like this:
1) Get your device to download mode by using this combo "VolumeDown-Home-Power"
2) Open an UP TO DATE ODIN.
3) Find the corresponding .PIT file for your S6 EDGE.
4) Find the corresponding stock rom for your S6 EDGE.
5) Then put them into odin CORRECTLY. Rom to "AP", .pit to PIT
6) Make Sure these are checked: "Re-partition","NAND all erase"
7) Plug your device in and then press start.
Click to expand...
Click to collapse
But I am not sure if this is the right thing to do. Also I don't know which of the provided pits for the SM-G925F I am supposed to use? http://forum.xda-developers.com/gal...925-pit-files-multi-thread-download-t3171636/ Whats the difference between them? Aaaand I'm still not sure which firmware I should be flashing
I would really appriciate your help..
Small update:
Found this suggestion on reddit and tried it
If you've tried to flash firmware off of Sammobile, and had your heart stop when the flash fails, fear no longer.
To fix the soft brick:
Open the firmware file in winrar and extract the hidden.img. Rename it as hidden.img.tar.
Load the new file into the PDA tab, and flash.
When the phone boots, the displayed image will be touchwiz teal, there will be a little android and GALAXY spelt above it. Don't freak out.
Give it a minute and it should boot.
Click to expand...
Click to collapse
After flashing the hidden.img.tar I was stuck on the Samsung Logo (before the bootanimation) but I could boot into normal Downloading mode. Tried flashing the stock firmware without the hidden.img and got
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
Click to expand...
Click to collapse
And I'm back to the screen saying I should use Smart Switch..
Well I again flashed the hidden.img.tar, then I could get in TWRP. I did restore on old backup and did a factory reset. The phone booted! So I dicided to try the unroot one more time. I was on kind a funny Baseband-Version so I decided to flash COH2 Bootloader and Modem, but Odin right after starting the NAND write and I was stuck on the Error massage from the beginning..
Flashed hidden.img.tar and the phone booted normaly.
What is going on? What do I need to flash or do to get back to stock?
In the device information I now have:
Modell: SM-G925F
Android-Version: 5.1.1
Basebandversion: G925FXXU2BOGE
Kernel-version: 3,10,61-Alex-V_1.2
Buildnumber: XtreStoLite Deo Mod v.2.3 - XXU2COH2
It is really kind of mixed up and I have know idea why I can't just flash with ODIN.
Worked for me but with very minor tweak
You guys are awesome! Thanks to you, I got myself out of a pickle.
I had softbricked my phone and I was stuck with a NAND Write error in ODIN with my G920F (Samsung Galaxy S6). Here's what I did:
Removed ".md5" at the end of "G920FXXU2BOFL_G920FOJV2BOEE_G920FXXU2BOFJ_HOME.tar.md5" (so file ends with ".tar").
Used 7zip to unpack.
Using Unified Android Toolkit, repacked each resulting ".img" file into separate ".tar" files (within Unified Android Toolkit, select 99 then 8, then 1 then 3 (auto-detect images). Resulting ".tar" files will be stored in the OUTPUT folder.
Using ODIN 3.10.7, flashed each ".tar" file, one by one, in the order that they were shown in 7zip. It's a very good idea to uncheck "Auto Reboot". After each flashing, vol down+home+button, and vol up again. Repeat until the last file. File flashing order was as follows:
- boot
- recovery
- system
- cache
- hidden
In the end, I rebooted the phone normally. Took about 6 or 7 minutes. An unusual green android screen was displayed, followed by another saying "erasing"... eventually, the phone rebooted as if it had been factory reset. Now going through the tedious process of reinstalling all of my apps.
Stuk in bootloop
spencersj said:
You guys are awesome! Thanks to you, I got myself out of a pickle.
I had softbricked my phone and I was stuck with a NAND Write error in ODIN with my G920F (Samsung Galaxy S6). Here's what I did:
Removed ".md5" at the end of "G920FXXU2BOFL_G920FOJV2BOEE_G920FXXU2BOFJ_HOME.tar.md5" (so file ends with ".tar").
Used 7zip to unpack.
Using Unified Android Toolkit, repacked each resulting ".img" file into separate ".tar" files (within Unified Android Toolkit, select 99 then 8, then 1 then 3 (auto-detect images). Resulting ".tar" files will be stored in the OUTPUT folder.
Using ODIN 3.10.7, flashed each ".tar" file, one by one, in the order that they were shown in 7zip. It's a very good idea to uncheck "Auto Reboot". After each flashing, vol down+home+button, and vol up again. Repeat until the last file. File flashing order was as follows:
- boot
- recovery
- system
- cache
- hidden
In the end, I rebooted the phone normally. Took about 6 or 7 minutes. An unusual green android screen was displayed, followed by another saying "erasing"... eventually, the phone rebooted as if it had been factory reset. Now going through the tedious process of reinstalling all of my apps.
Click to expand...
Click to collapse
After flashing boot.tar my phone is stuck in bootloop and nt coming out despite hard reset also and i m also unable to flash new fw via odin.
plz help.
it states SOLVED.....???
Hello XDA,
i have an S3 international that i havent used since some time, and when i gave it to my brother he messed up with it until finally it gives "Firmware Upgrade Encountered an Issue Please select recovery mode in Kies & try again"
i have searched a lot and tried all possible solutions( note: i've forgot what android was used but its supposed to be 4.1 or 4.2)
i have tried all possible kies and smart switch, it reaches to the end of process and says upgrade failed due to an unexpected error (give a recovery code blank space that cant be written to it) and nothing happens as if it was canceled.
i have tried flashing using odin , android 4.3 repair firmware different regions with different .pit, i even tried flashing the pit alone but i get no pit partition and fails quickly
<ID:0/003> Get PIT for mapping..
<ID:0/003> There is no PIT partition.
one flash of a .tar AP file gave this but failed:
<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> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> FAIL!
what am i supposed to do ? is it 100% damaged? no way to be fixed, how is it possible that there is no fix for such a thing.. i mean i want to format it completely i dont care for the data.. why havent samsung developed a tool that can fix this things? all tools developed like kies smart switch and others work for some times then they dont support the phone models after some time..
You're using the latest stock firmware from sammobile.com or updato.com with Odin?
Tried different USB cables and USB ports?
audit13 said:
You're using the latest stock firmware from sammobile.com or updato.com with Odin?
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
yes i've tried different usb cables , i tried different ports.. samsung kies always reach at the end of upgrade and then say failed due to an unexpected error
tried download all sort of firmwares, different regions, also repair firmware containing (AP,CSC...) but always fail in odin.
most fail says no pit partition ( which i tried to download different pit files and none worked)
another fails at NAND write ( which i tried to rebuild the .tar file and it passed the nand write but then it fails again at cache.img)
There should be no need to flash the stock firmware separately. The firmware from sammobile.com is unzipped once to create a tar.md5 file for flashing in AP/PDA.
I often get the pit error when using a non-Samsung OEM USB cable.
audit13 said:
There should be no need to flash the stock firmware separately. The firmware from sammobile.com is unzipped once to create a tar.md5 file for flashing in AP/PDA.
I often get the pit error when using a non-Samsung OEM USB cable.
Click to expand...
Click to collapse
i've downloaded several firmwares 4.1.1 & 4.1.2 & 4.3 and tried different regions for each..
i am also getting this error in some of them
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
It's possible that the memory chip inside the phone is damaged. You may have to take it to a cell repair shop to see if they can force flash it via tag.