[GT-I9515] Smartphone Pit Partition Fail - Galaxy S 4 Q&A, Help & Troubleshooting

Good day.
Yesterday I made ​​some crap with my phone . Now I need a "low level " firmware for my GT - I9515
The PIT file is totally destroyed . In the recovery mode, I 'm no longer pure . The device has no system . Only the download mode works .
Maybe someone can help me . Otherwise, I have a 200 € paperweight .
The Engschlische language sponsored by Google . : D

Okay , I have recorded a progress . The Pit file could be installed . Look here:
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Now do not want the system . I've got only one file . Why it does not work , I state in a log file of Odin .
<ID:0/003> Removed!!
<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> 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!!

I tried a pit file called JFVELTE_EUR_OPEN.pit
and changed to (direct) usb port and then it worked. (found this link)
http://forum.xda-developers.com/showthread.php?t=2265477
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.

Odin is failing when it tries to flash aboot.mbn because the bootloader on the phone is newer than the bootloader in the rom you are trying to flash.

Related

help needed!!! stuck odin recovery on stock image

<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> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please any help????
nonliner said:
<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> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
please any help????
Click to expand...
Click to collapse
Odin troubleshooting: If Odin accidentally gives you "fail" try the following:
- Repeat procedure.
- Make sure that all actions of Kies are disabled from task manager.
- Change usb port.
- Try another usb cable (make sure it is the original).
- Try another Odin version.
- Uninstall and re-install driver.
- Use pit file.
- Try another computer.
Edit: Use Odin 3.07 / 3.04
If u are flashing firware try using diffrnt firmware and see result may be better in cases due to new and old firmware
SOLVED!!!
DO NOT USE virtual machine on a Mac!
find a regular PC with win7
and do exactly what samersh72 says here: http://forum.xda-developers.com/showthread.php?t=2265477
SOLVED
SOLVED!!!
DO NOT USE virtual machine on a Mac!
find a regular PC with win7
and do exactly what samersh72 says here: http://forum.xda-developers.com/showthread.php?t=2265477

[Odin] Pit re-partition takes no effect

Hi
I tried to re-partition my Samsung S3 mini with a custom pit file with Odin v3.07. This is Odin output, looks ok:
<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> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
I'd like to remove the recovery partition and resize following system partition instead. The download menu on the device prints a red warning "Custom pit file", which I ignore.
After rebooting the device, I can't see any change, the recovery image still boots and the red flag in the download mode disappeared.
Why does it not work, I tried already different checkbox combinations on Odin.
Regards
Edit:
The problem was, that I tried to repartition the device without flashing the images. Instead of Odin, Heimdall throws an error.

marshmallow to stock (5.0), odin errors

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

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

Help with unrooting s7edge G935P

So I wanted to root my phone tonight and thought I was doing everything right, well my phone rebooted and wouldn't connect to my carrier or anything and was checking device status the entire time..
So I decided to reboot and now I am just even more confused.. my phone at the current state is relooping into the recover reboot stage.. so I can't put the phone in USB debugging or anything like some post suggest..
I can get it to download mode but every time I try odin it fails and fails.. I have tried everything to my ability to get this phone to reboot on stock and I just cant seem to figure it out..
I am not to knowledgeable about ROM's and rooting and such and I learned my lesson.
When on the download screen is says at the bottom in red text " SW REV CHECK FAIL : [aboot] Fused 4 > Binary 2
This is the error code I get from Odin when trying to flash back to oem android on my S7 EDGE
<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> 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> NAND Write Start!!
<ID:0/003> lksecapp.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am more then open to any suggestions I just want my phone back lol

Categories

Resources