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!!
Related
<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> 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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I tried to install stock Brazil 4.4.2, then my pit file was missing
Downloaded Stock 4.3 and tried again with pit file now i got auth failed
I ticked re-partition and im using CSB_signed_Fusion3_EUR_0325_V2
i dont know waht do anymore... pliz help
NotaHue 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> 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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I tried to install stock Brazil 4.4.2, then my pit file was missing
Downloaded Stock 4.3 and tried again with pit file now i got auth failed
I ticked re-partition and im using CSB_signed_Fusion3_EUR_0325_V2
i dont know waht do anymore... pliz help
Click to expand...
Click to collapse
You can no longer downgrade your phone to 4.3 after Flashing 4.4.2 firmware mate and and you might wanna Check this thread
but installation on 4.4.2 failed too so i need pit file for 4.4.2?
i was in 4.3 bootloader then i was trying to install 4.4.2 sotck but failed (missing pit file)
NotaHue said:
but installation on 4.4.2 failed too so i need pit file for 4.4.2?
i was in 4.3 bootloader then i was trying to install 4.4.2 sotck but failed (missing pit file)
Click to expand...
Click to collapse
Ask from this thread mate , Im sure Samersh or malybru can help you fix this situation . Have a nice day
Hi,
I have a n900w8 with some marshmallow rom (and some kernel I don't remember since I've already wiped all). I've downloaded a original stock rom from sammobile. Unfortunately, the latest version is a lollipop one, not a marshmallow one.
I've read that the bootloader cannot be downgraded after the 5.x. I think I have 5.x or higher bootloader. Are there any chance to install the custom rom? like this one(http://www.sammobile.com/firmwares/download/67302/N900UBUEBOK1_N900UUBEBOK1_UPO)
Kies3 says mi phone is not compatible with it, and kies "standard" doesn't recognise any device.
Odin gives me this error:
<ID:0/003> 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..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I've read that editing the TAR file and remove some files (like the boot.img, cache.img, hidden.img. etc). I've tried removing several of them with same (or similar) results.
If I remove the boot.bin, I get this:
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> cache.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If I remove cache.img, I get:
<ID:0/003> Removed!!
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> hidden.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If I remove hidden.bin:
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
If I remove modem.bin:
<ID:0/003> Added!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> param.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I've restored a 4.4.4 backup with twrp before doing all that
I'm running out of ideas.
Thank you very much!
leitor79 said:
Hi,
I have a n900w8 with some marshmallow rom (and some kernel I don't remember since I've already wiped all). I've downloaded a original stock rom from sammobile. Unfortunately, the latest version is a lollipop one, not a marshmallow one.
I've read that the bootloader cannot be downgraded after the 5.x. I think I have 5.x or higher bootloader. Are there any chance to install the custom rom? like this one(http://www.sammobile.com/firmwares/download/67302/N900UBUEBOK1_N900UUBEBOK1_UPO)
Kies3 says mi phone is not compatible with it, and kies "standard" doesn't recognise any device.
Odin gives me this error:
I've read that editing the TAR file and remove some files (like the boot.img, cache.img, hidden.img. etc). I've tried removing several of them with same (or similar) results.
If I remove the boot.bin, I get this:
If I remove cache.img, I get:
If I remove hidden.bin:
If I remove modem.bin:
I've restored a 4.4.4 backup with twrp before doing all that
I'm running out of ideas.
Thank you very much!
Click to expand...
Click to collapse
frist of all do a full wipe (cache,dalvik,system,data)
secend flash last modem and bootloader 5.0 i think its PB1
third flash a stock rom
its must working
because i did it
Download the stock ROM for the sm-n900w8 from sammobile.com and flash it in Odin: http://www.sammobile.com/firmwares/database/SM-N900W8/
Flashing in Odin will wipe everything and you should do a factory wipe using stock recovery before booting the newly-flashed stock ROM for the first time.
Odin failed the first time because the ROM you tried to flash has a bootloader that is either not meant for your phone or the bootloader in the ROM is older than the bootloader in the phone. Look like you are flashing the n900 stock ROM, not the n900w8 ROM. You have a Canadian note 3? You can confirm the model # by booting into download mode.
Do nothing it's gonna flash it because I have incurred same problems while flashing from lollipop to kitkat but then I just slept at night and the next morning tried with another USB cable and it worked fine .
It's nothing to do with bootloader because every stock Rom contains bootloader and it will flash it anyhow.
Sent from my SM-N900 using Tapatalk
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
Hi, I tried following the top thread on flashing my Sprint S7 to the unlocked non bloatware version, not noticing it was out of date. Now I can not get my S7 out of a bootloop, even when trying to flash the Sprint version. Could anyone walk me through the steps to get the sprint firmware back on my device and out of the bootloop? Thanks, Jon.
<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> emmc_appsboot.mbn
<ID:0/003> lksecapp.mbn
<ID:0/003> xbl.elf
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hello. I know, at least, now I know. I should have NEVER interrupted my software update and am now paying dearly. I tried to install the latest version of Odin and used the firmware from a site other than the official download site as the specific firmware I needed wasn't there. The firmware name matched my phone's model and I selected the four types of files in the Odin menu and hit start. I got this command sequence
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 4721 M
<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> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> apdp.mbn
<ID:0/003> cmnlib.mbn
<ID:0/003> cmnlib64.mbn
<ID:0/003> devcfg.mbn
<ID:0/003> emmc_appsboot.mbn
<ID:0/003> hyp.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help y'all can give will be greatly appreciated. Thanks