I want to unbrick a rooted Sprint Samsung Galaxy S4 and I have the stock MDC and MJA roms. I can't find a pit file to allow for repartition. Where can I locate this?
<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> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks.
[email protected] said:
I want to unbrick a rooted Sprint Samsung Galaxy S4 and I have the stock MDC and MJA roms. I can't find a pit file to allow for repartition. Where can I locate this?
<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> aboot.mbn
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks.
Click to expand...
Click to collapse
I don't think you need the pit file. The error you are showing is from trying to Odin a stock tar that is older than mja. Just Odin either mja or mk2 and it should complete. You cannot Odin MDC after the phone has been updated.
Sent from my icrap 2 using Tapatalk HD
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
Excuse Me, I have a Note 4, and want to change the Rom from N910S (Korea) to N910U (HK).
I tried to use Odin to directly install N910U Rom but fail, with follows error message:
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help, thousand Thanks!
kwok_h said:
Excuse Me, I have a Note 4, and want to change the Rom from N910S (Korea) to N910U (HK).
I tried to use Odin to directly install N910U Rom but fail, with follows error message:
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> sboot.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help, thousand Thanks!
Click to expand...
Click to collapse
Hi mate
just have finded out what was giving the error.
I've unchecked the reactivation lock under security tab on the android Kitkat... Now can flash whatever I wanted with odin.
Sent From Out of Nowhere
N910s
Do you mean you can flash over 910s an 910u rom ? ....
i ant help i flashed my samsung galaxy y young s5360 using odin but mistakely repartition was not unchecked now my phone wont start up and also not flashed by odin plz help it showing the following erorr
"<ID:0/008> Added!!
<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> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
"
please help
I was trying to fix my IEMI problem by flashing in COMBINATION_FA60_G935FXXU1AQI2_CL7964511_QB14932435_REV00
and here is the log from odin:
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1203)..
<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> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> param.bin
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
can someone plz tell me the problem?
What bootloader version do you have now?
I'm not sure how you would fix IMEI issues with combination firmware as most you can do is wipe EFS (Which should never be done) which means you lose your IMEI until it gets reprogrammed.
The only thing you can try is reflashing stock samsung Firmware, other than that IMEI would need to be reprogrammed by flashing box.
I got the same exact log with Samsung J3 Pro... I'm trying to bypass/remove FRP because I can't use that talkback trick... Anybody know?
Hey there,
my galaxy s8 went into a bootloop after rooting with TWRP.
Currently on Android 8.0 and the cpu is Exynos.
After using Odin to reflash to stock android it failed numerous times.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5869 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> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Using Odin v3.13.1
marky2458 said:
Hey there,
my galaxy s8 went into a bootloop after rooting with TWRP.
Currently on Android 8.0 and the cpu is Exynos.
After using Odin to reflash to stock android it failed numerous times.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5869 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> cm.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Using Odin v3.13.1
Click to expand...
Click to collapse
Are you using correct firmware for your phone and region or maybe trying to use older version of firmware than what's on your phone.