Back to stock from Beta One UI on the GS8 - Samsung Galaxy S8 Questions and Answers

Having a difficult time here.... I've got a Galaxy s8 Sprint variant.. I downloaded the Beta one UI firmware, not official just used ODIN. I'd like to go back to stock and update to newest official release, or just go straight to the latest release. I don't care if it's rooted/unlocked or whatever just stock Sprint software. I've tried a couple of stock firmwares but I keep getting errors in Odin. Currently I"m on PDA G950U1UEU5ZSAB CSCG950U1OYM5ZSAB .
Any pointers would be greatly appreciated.

tri0xinn said:
Having a difficult time here.... I've got a Galaxy s8 Sprint variant.. I downloaded the Beta one UI firmware, not official just used ODIN. I'd like to go back to stock and update to newest official release, or just go straight to the latest release. I don't care if it's rooted/unlocked or whatever just stock Sprint software. I've tried a couple of stock firmwares but I keep getting errors in Odin. Currently I"m on PDA G950U1UEU5ZSAB CSCG950U1OYM5ZSAB .
Any pointers would be greatly appreciated.
Click to expand...
Click to collapse
What errors are you getting with Odin?
What firmware are you trying to flash?

spawnlives said:
What errors are you getting with Odin?
What firmware are you trying to flash?
Click to expand...
Click to collapse
I'll cut and paste it.. but the phone says SW REV CHECK FAIL : {ab}{FUSED 5 > Binary 2
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<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> abl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!

tri0xinn said:
I'll cut and paste it.. but the phone says SW REV CHECK FAIL : {ab}{FUSED 5 > Binary 2
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> skip file list for home binary
<ID:0/003> apdp.mbn
<ID:0/003> msadp.mbn
<ID:0/003> persist.img.ext4
<ID:0/003> Home Binary Download
<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> abl.elf
<ID:0/003> FAIL! (Auth)
<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
2 things I can see
1. Use Odin version 3.13.1 it supports the new compression format of newer firmware.
2. The software check fail is due to trying to flash older firmware than what is on your phone. You will need to download firmware with a bootloader version 5 ( 5th number from right of firmware(PDA) name ).

OP can you confirm if it worked?

Hey, THanks a ton.. worked! I don't think I woulda figured that out unless I would have happened to tried a rom with the correct bootloader version. Really appreciate it. One more thing.. which should I use normally.. the home_csc or the csc. I've been using the home one since that's what I see a majority of people using but I don't see any explanation.
thanks again!

tri0xinn said:
Hey, THanks a ton.. worked! I don't think I woulda figured that out unless I would have happened to tried a rom with the correct bootloader version. Really appreciate it. One more thing.. which should I use normally.. the home_csc or the csc. I've been using the home one since that's what I see a majority of people using but I don't see any explanation.
thanks again!
Click to expand...
Click to collapse
Glad you got it sorted
Home_CSC - will keep your apps and data.
CSC - clean install same as a factory reset.

Related

[HELP] Phone Doesn't Boot

I tried to flash a stock ROM and got an error in ODIN that said:
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now my phone only boots into Odin Mode and to a screen that says:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Please Help!
Odin stock Rom tar and start from scratch.
carwashman said:
Odin stock Rom tar and start from scratch.
Click to expand...
Click to collapse
I tried multiple Stock ROMs and I get the same error. Do you know of a legit one? The ones I had could've been corrupt.
What device do you have?
carwashman said:
What device do you have?
Click to expand...
Click to collapse
The Sprint Samsung Galaxy S4. SPH-L720
You may have to try the kitkat rom.
http://forum.xda-developers.com/showthread.php?t=2663619
This is the one I used recently. I was already on NAE
carwashman said:
http://forum.xda-developers.com/showthread.php?t=2663619
This is the one I used recently. I was already on NAE
Click to expand...
Click to collapse
Is there a way to find out what I'm on without being able to elsewhere except download?
EDIT: I get the same error with that ROM.
EDIT #2: I got it to work!!! Thanks so much guys!

Stuck in bootloop from trying to downgrade from 5.0 to 4.2

As the title says, I tried to downgrade from lollipop 5.0 to 4.2 because I've had several issues and I also wanted to get root. I think part of my mistake was I wiped data/factory reset before I flashed AP. Any help would be much appreciated, as I have been at this for the past five hours. I added some info below that might help below. Thanks
- I cannot boot into recovery and get the message (Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again)
- CP is the only thing that will flash and CSC also fails
- model number is g900a AT&T
- I have used Odin 3.10.7 and 3.09, but no luck
<ID:0/003> Odin engine v(ID:3.1100)..
<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> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> persist.img.ext4
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Did you try to repair him via kies?Maybe would help.
Sent from my D6503 using Tapatalk
Hey I have also experienced the same thing before, I was panicking that time, so I fixed it by flashing the old zip file, if that does not work try following the instructions your phone gave eg. Go to kies
VoltexYT said:
Hey I have also experienced the same thing before, I was panicking that time, so I fixed it by flashing the old zip file, if that does not work try following the instructions your phone gave eg. Go to kies
Click to expand...
Click to collapse
Kies and kies3 are both not recognizing my device. I heard it could be because of usb debugging, but I can't boot into my phone to check.
Allek84 said:
Did you try to repair him via kies?Maybe would help.
Sent from my D6503 using Tapatalk
Click to expand...
Click to collapse
Both kies and kies3 are not recognizing my device.

Soft bricked my GT-i9505 and now Odin won't work. Complete(Write) operation failed.

Here's the Odin log.
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1100)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I was trying to unlock my phone before this, before I gave up because I had downloaded the wrong version (5.0.1 UK stock instead of 4.2.2 stock, was trying to use the leaked unlock codes) and then I tried flashing TWRP 3.0.2-0 in Odin 3.10-7 which "Re-Partition" was ticked automatically for some reason and I didn't know. Now my phone is soft-bricked and Odin won't cooperate. Help me please!
I will provide more info as necessary!
Jared20098 said:
Here's the Odin log.
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1100)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> SingleDownload.
<ID:0/008> recovery.img
<ID:0/008> NAND Write Start!!
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I was trying to unlock my phone before this, before I gave up because I had downloaded the wrong version (5.0.1 UK stock instead of 4.2.2 stock, was trying to use the leaked unlock codes) and then I tried flashing TWRP 3.0.2-0 in Odin 3.10-7 which "Re-Partition" was ticked automatically for some reason and I didn't know. Now my phone is soft-bricked and Odin won't cooperate. Help me please!
I will provide more info as necessary!
Click to expand...
Click to collapse
Flash a stock rom with .pit file and re-partition checked. Flash a Lollipop rom.
Lennyz1988 said:
Flash a stock rom with .pit file and re-partition checked. Flash a Lollipop rom.
Click to expand...
Click to collapse
Unfortunately that's gonna take a while due to my internet being reeeaaally crappy. It takes 3-4 hrs on average to download a 1.5 GB file.
Try changing the USB ports.I had the same problem like you 1 mouth ago and tried changing from the front USB ports to the back and it worked.
simeon112 said:
Try changing the USB ports.I had the same problem like you 1 mouth ago and tried changing from the front USB ports to the back and it worked.
Click to expand...
Click to collapse
This is an old thread but gotta say LIFE SAVER.
Was flashing pit files left right and center, a simple switch to a USB 2.0 port fixed it. Thanks
Tweakforce_LG said:
This is an old thread but gotta say LIFE SAVER.
Was flashing pit files left right and center, a simple switch to a USB 2.0 port fixed it. Thanks
Click to expand...
Click to collapse
what da heck is a PIT files and where do I get this
Pit files contain partition information about a particular Samsung phone.
Older thread with good information: https://forum.xda-developers.com/showthread.php?t=999097
Israelleite said:
what da heck is a PIT files and where do I get this
Click to expand...
Click to collapse
^^^^
audit13 said:
Pit files contain partition information about a particular Samsung phone.
Older thread with good information: https://forum.xda-developers.com/showthread.php?t=999097
Click to expand...
Click to collapse

Odin fails when i try to revert to stock rom. S7 EDGE ATT(SM-G935A)

So basicly I rooted my phone like 3 days ago so yesterday since it was going slow and all. I was trying to revert from rooted 6.0.1 to stock 6.0.1 but I have literaly tried so much stock roms for att on the internet and it failed from model dismatch. But then I found one that matched and odin passed till it failed at system.img.ext4. Here is the log:
<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> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And there is an error on the phone:
SW REV CHECK FAIL : [system]Fused 3 > Binary 1
Please help me I just got this one from insurance and if my dad finds out I broke it. I'm going to be toast!!!!
TheAndroidGuy101 said:
So basicly I rooted my phone like 3 days ago so yesterday since it was going slow and all. I was trying to revert from rooted 6.0.1 to stock 6.0.1 but I have literaly tried so much stock roms for att on the internet and it failed from model dismatch. But then I found one that matched and odin passed till it failed at system.img.ext4. Here is the log:
<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> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And there is an error on the phone:
SW REV CHECK FAIL : [system]Fused 3 > Binary 1
Please help me I just got this one from insurance and if my dad finds out I broke it. I'm going to be toast!!!!
Click to expand...
Click to collapse
Same issue here, I think you need to find a more recent version of the file - which I can't find at the moment
did you not make a back up before rooting your phone , either on your phone or smart switch so that you can revert to stock rom if needed.
all threads advise backing before flashing in case some thing like this happens.
theandroidguy101 said:
so basicly i rooted my phone like 3 days ago so yesterday since it was going slow and all. I was trying to revert from rooted 6.0.1 to stock 6.0.1 but i have literaly tried so much stock roms for att on the internet and it failed from model dismatch. But then i found one that matched and odin passed till it failed at system.img.ext4. Here is the log:
<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> boot.img
<id:0/003> recovery.img
<id:0/003> system.img.ext4
<id:0/003> fail! (auth)
<id:0/003>
<id:0/003> complete(write) operation failed.
<osm> all threads completed. (succeed 0 / failed 1)
and there is an error on the phone:
Sw rev check fail : [system]fused 3 > binary 1
please help me i just got this one from insurance and if my dad finds out i broke it. I'm going to be toast!!!!
Click to expand...
Click to collapse
pm me! I just flashed my s7 at&t. I can send you the files

Flashing stock ROM on rooted phone

I was flashing root(was already rooted) and because i had an bad USB cable it failed midway and now the phone is stuck in "Firmware upgrade encountered an issue. please select Recovery mode in Kies & try again." I learned that i have to flash stock ROM to restore my phone but i dont know what was my latest update (I know its either G900FXXS1CPK1 or G900FXXS1CPLV) before i rooted the phone. Can I just flash the newest version?
peeaarrll said:
I was flashing root(was already rooted) and because i had an bad USB cable it failed midway and now the phone is stuck in "Firmware upgrade encountered an issue. please select Recovery mode in Kies & try again." I learned that i have to flash stock ROM to restore my phone but i dont know what was my latest update (I know its either G900FXXS1CPK1 or G900FXXS1CPLV) before i rooted the phone. Can I just flash the newest version?
Click to expand...
Click to collapse
yes, but sometimes samsung sneaks some stuf fin that you dont want, so you could try the older version first and all that would happen if it doesnt like that one is fail in odin, then youd just go to the most recent one
youdoofus said:
yes, but sometimes samsung sneaks some stuf fin that you dont want, so you could try the older version first and all that would happen if it doesnt like that one is fail in odin, then youd just go to the most recent one
Click to expand...
Click to collapse
hii, really sorry for not replying faster i have just been down in the dumps because of this.I tried doing that but it said no PIT partition so i got that and tried it with that but then it says
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
Now im stuck here and i dont know what to do. Please help.
peeaarrll said:
hii, really sorry for not replying faster i have just been down in the dumps because of this.I tried doing that but it said no PIT partition so i got that and tried it with that but then it says
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
Now im stuck here and i dont know what to do. Please help.
Click to expand...
Click to collapse
If its failing, youre probably just trying to flash the wrong tar.md5. What version of android were you on before this issue? 6.0.1?
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
try this tar.md5
https://www.sammobile.com/firmwares/download/71369/G900FXXU1CPE1_G900FOXA1CPE1_BTU/
youdoofus said:
If its failing, youre probably just trying to flash the wrong tar.md5. What version of android were you on before this issue? 6.0.1?
---------- Post added at 10:32 AM ---------- Previous post was at 10:30 AM ----------
try this tar.md5
Click to expand...
Click to collapse
yeah i was on 6.0.1. Will the UK version work if im in another country?
peeaarrll said:
yeah i was on 6.0.1. Will the UK version work if im in another country?
Click to expand...
Click to collapse
i only grabbed the uk version because you mentioned the baseband in your post which was a UK version. Its the g900f, so it should be able to accept that version. I think the only difference is the radios and default language. But if you go to www.sammobile.com/firmwares, you can select whichever version you actually need
there is a dropbox above the tar download links thatll allow you to choose whiever one you actually need
https://www.sammobile.com/firmwares/database/SM-G900F/BTU/
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
downloading from this site is always super slow, but its directly from the source. I always keep a copy of the one i need on my hdd for safety
youdoofus said:
i only grabbed the uk version because you mentioned the baseband in your post which was a UK version. Its the g900f, so it should be able to accept that version. I think the only difference is the radios and default language. But if you go to www.sammobile.com/firmwares, you can select whichever version you actually need
there is a dropbox above the tar download links thatll allow you to choose whiever one you actually need
---------- Post added at 12:27 PM ---------- Previous post was at 12:26 PM ----------
[/COLOR]downloading from this site is always super slow, but its directly from the source. I always keep a copy of the one i need on my hdd for safety
Click to expand...
Click to collapse
i tried flashing in now but i still get the same error could it happen because of the USB cable or something else?I got this the first time
<ID:0/003> Odin engine v(ID:3.1101)..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
aand this the second time:
<ID:0/003> Odin engine v(ID:3.1101)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
should i just continue trying until it succeds, im hesitant to do that because thats how i got it broken(i went fine until about half way through the process it just disconnected from the PC. and when i tried to boot it had the error i stated in the post.)
peeaarrll said:
i tried flashing in now but i still get the same error could it happen because of the USB cable or something else?I got this the first time
<ID:0/003> Odin engine v(ID:3.1101)..
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
aand this the second time:
<ID:0/003> Odin engine v(ID:3.1101)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
should i just continue trying until it succeds, im hesitant to do that because thats how i got it broken(i went fine until about half way through the process it just disconnected from the PC. and when i tried to boot it had the error i stated in the post.)
Click to expand...
Click to collapse
id definitely try a different cable and make sure that you dont touch the cable, phone or computer while its doing its thing. Since its borked anyways and wont boot, its not likely that youll make it any worse by trying odin again or even repeatedly. Also, did you download the oldest baseband of the same android version you were running? Thats also pretty important
youdoofus said:
id definitely try a different cable and make sure that you dont touch the cable, phone or computer while its doing its thing. Since its borked anyways and wont boot, its not likely that youll make it any worse by trying odin again or even repeatedly. Also, did you download the oldest baseband of the same android version you were running? Thats also pretty important
Click to expand...
Click to collapse
I have now downloaded the latest baseband version and tried to flash it but it says that it fail because of size, here is the log of the code;
<ID:0/004> Odin engine v(ID:3.1101)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
peeaarrll said:
I have now downloaded the latest baseband version and tried to flash it but it says that it fail because of size, here is the log of the code;
<ID:0/004> Odin engine v(ID:3.1101)..
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
Click to expand...
Click to collapse
no, not the latest, the oldest. The first one in the same android version you were on
youdoofus said:
no, not the latest, the oldest. The first one in the same android version you were on
Click to expand...
Click to collapse
i downloaded the first one in the same android version i am and tried flashing it but it shows the same error
<ID:0/004> FAIL! (Size)
peeaarrll said:
i downloaded the first one in the same android version i am and tried flashing it but it shows the same error
<ID:0/004> FAIL! (Size)
Click to expand...
Click to collapse
how big is the file? and you might need a different version of odin if its giving you that error
youdoofus said:
no, not the latest, the oldest. The first one in the same android version you were on
Click to expand...
Click to collapse
youdoofus said:
how big is the file? and you might need a different version of odin if its giving you that error
Click to expand...
Click to collapse
well in the end i got tired and remembered what i read somewhere to try to flash PIT and ROM individualy and i did. In the end i only flashed PIT and I booted the phone it and updated it.Everthing seems to work fine.
sorry for causing you so much trouble.
peeaarrll said:
well in the end i got tired and remembered what i read somewhere to try to flash PIT and ROM individualy and i did. In the end i only flashed PIT and I booted the phone it and updated it.Everthing seems to work fine.
sorry for causing you so much trouble.
Click to expand...
Click to collapse
Oh, no trouble at all! I'm just glad that you got it working man!!

Categories

Resources