So this is the issue I'm having
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am trying to revert back from cyanogen to Touchwiz so I can activate my phone again with Sprint, however no matter what I do and how many forum posts I've been checking out for the last few months I can't for the life of me figure out whats wrong with my phone. I've followed multiple youtube videos and nothing works so far.
interpunct said:
So this is the issue I'm having
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am trying to revert back from cyanogen to Touchwiz so I can activate my phone again with Sprint, however no matter what I do and how many forum posts I've been checking out for the last few months I can't for the life of me figure out whats wrong with my phone. I've followed multiple youtube videos and nothing works so far.
Click to expand...
Click to collapse
What firmware file are you using and where did you get it?
kdraw44 said:
What firmware file are you using and where did you get it?
Click to expand...
Click to collapse
I'm using one from samsung updates, l720t 4.4.2 android kit kat sprint
I have a l720t so yeah.
interpunct said:
I'm using one from samsung updates, l720t 4.4.2 android kit kat sprint
I have a l720t so yeah.
Click to expand...
Click to collapse
You may want to try one from here. The downloads are really slow but it's reliable. http://www.sammobile.com/
I'm thinking maybe you have a corrupted or in-complete firmware. Just a thought.
interpunct said:
So this is the issue I'm having
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I am trying to revert back from cyanogen to Touchwiz so I can activate my phone again with Sprint, however no matter what I do and how many forum posts I've been checking out for the last few months I can't for the life of me figure out whats wrong with my phone. I've followed multiple youtube videos and nothing works so far.
Click to expand...
Click to collapse
Which version of CM are you coming from?
Try a different cable, it sounds stupid but it is the problem half the time with Odin.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
<OSM> G900FXXU1ANCE_G900FOJV1ANCD_G900FXXU1ANCE_HOME.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> 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> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
device from Hong Kong
plz help me when i flash soft G900F 16GB
i have same problem.
I dont know what wrong Pls help
Thank you.
Got this issue too as far i can understand we need PIT file...
Trying to flash with PIT file right now. Will post results in a few minutes
EDIT:
Did not work still fails on the Hidden.img.ext4
The Phone says:
ODIN : Invalid EXT4 image.
ODIN log:
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Ext4)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Found a Solution
First flash the firmware of choice let it fail.
Unplug the device and plug it back in with out rebooting it let it stay in the failed download mode.
Now uncheck the PDA/AP and add the PIT file attached here.
make sure repartion is checked and PDA/AP is not
Flash PIT and the phone will reboot and start up with your new firmware.
Note the PIT is for G900F 16GB EU
My log:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
m7mel said:
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
Click to expand...
Click to collapse
danielfg87 said:
Got this issue too as far i can understand we need PIT file...
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Ext4)
Click to expand...
Click to collapse
@ danielfg87: I may be wrong but i see a difference between FAIL! (Size) and FAIL! (Ext4).
Are you sure that these aren't two different types or errors?
Also: The .pit of my SM-G900F is 4.640 bytes in size, but if i leave out the empty/00 hex data (padding?) in the end, the filesize and CRC32/MD5/SHA-1 matches the .pit you've attached.
Proof:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Well, guess what happened.
I tried to flash back the 4.640 bytes pit that i pulled from my device, but in Odin (download) mode it said:
SECURE CHECK FAIL : pit
However, after i hex-edited out the empty/null (padding) data and another flash attempt,
...it worked
My guess is that the additional padding data wasn't supposed to be there in the first place.
Perhaps the tutorial i used to pull the .pit data wasn't "universal" or "correct" enough.
Here's a photo of the error:
..
fffft said:
There is a lot of guesswork and misinformation on this subject. The flash is failing because you are flashing an incompatible firmware image from another carrier. hidden.img.ext4 contains carrier specific data and is partitioned. The failure arises from several error conditions that may arise e.g. a size mismatch between the new hidden partition and the old PIT file which refers to the old (not new) firmware structure. An undefined address location, checksum error, et cetera. If the new firmware image happens to overwrite the partition boundaries the write will fail and depending on the specifics may soft brick your phone. Worse, the reverse write will succeed but leave you open to undefined calls and an unstable system, without an easily discerned cause.
You cannot (safely) flash software from any carrier onto your device despite a lot of people claiming you can. They tried it once and it worked and have erroneously assumed that it will therefore work in all cases. That is demonstrably wrong.
Better informed users can examine the partition structure and determine if the partition would be corrupted by the new firmware. But the proper method would be to flash the proper PIT (partition information) file for the new carrier in conjunction with the new firmware. A temporary workaround might be installing a custom recovery like CWM which will often resolve the issue. But you should obtain a proper PIT file for a reliable resolution.
.
Click to expand...
Click to collapse
You are a wise man, thank you (you're spot on btw; i should've examined my device's .pit in EFS Professional's Pit Magic, then i would've knew it)
fffft said:
Better informed users can examine the partition structure and determine if the partition would be corrupted by the new firmware. But the proper method would be to flash the proper PIT (partition information) file for the new carrier in conjunction with the new firmware. A temporary workaround might be installing a custom recovery like CWM which will often resolve the issue. But you should obtain a proper PIT file for a reliable resolution.
.
Click to expand...
Click to collapse
Where can i get proper PIT (partition information) file for the new carrier in conjunction with the new firmware ?!
Can we extrat from the rom itself ?
installing a custom recovery like CWM will trip the knox,
but it will clean the pit ,partition structure ?
..
If you read post five it will tell u the file name u need for the pid. The one uploaded is messed up but try the other one.
http://forum.xda-developers.com/galaxy-s5/help/help-soft-bricked-phone-t2850714
9th file down SM-G900F_pit_16GB_SER.zip
From here
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
juDGEY2k10 said:
9th file down SM-G900F_pit_16GB_SER.zip
From here
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Click to expand...
Click to collapse
Does flashing the PIT file cause a full data wipe?
@AMoosa
yes mate
juDGEY2k10 said:
@AMoosa
yes mate
Click to expand...
Click to collapse
ok thanks. That's a pain. I have been trying to install NH6 over the top of my current NG2 ROM. It fails with the hidden.img error and I don't really want to wipe. I have flashed NG2 back on and everything is intact, so need to find a BTU-compatible NH6 I guess, unless I wipe.
how come u dont want to wipe mate no backup ?
fail
thanks a lot
I have been looking for this problem.
thanks to you my phone is back and working
you save the day
:good::good::good::good::good::good::good::good:
changing frimware from KSA to SER..
i tried to change and got the hidden.ext4.tar error... how to use the pitfile ? steps please
attari13 said:
i tried to change and got the hidden.ext4.tar error... how to use the pitfile ? steps please
Click to expand...
Click to collapse
Not all flashing needs pit file. Typically only HK device needs coz it is not compatible with another devices.
On the 1st page there was a link to the pit file's thread to download.
check the pit option in the Odin software.
S5 SM-G900F Fail (size)
Guys, After reading this post, I still don´t know what to do.
I am a total amateur, Don´t know sh** , I am just following steps I found.
What happened was that after upgrading (automatically via the mobile) my S5 (G900F - bought in UK) the mobile became useless, e.g. 1 min to open whatsapp.... or photo gallery, memory crash when playing with MadSkill Motocross, and also camera problems. So I decided to go back to kitkat 4.4.2 and following the phone specifications I downloaded the stock firmware. After flashing it, I got the fail (size).
Please what to do? Because reading about the pit file I still am not sure about which file to use, or even using it.
What I had before in my mobile was - G900FXXU1B0A3 (lollipop), and I tried the downgrade with G900FXXU1BNL9_G900FTTR1BNK6_G900FXXU1BNL9_HOME.tar (kitkat)
I just wanna put my device working again. If I need to provide any information more, please let me know.
Thanks
Iuri Marmo
Hello everyone, I'm new to this tablet and I need help. Sorry for my English
I tried putting a rom with odin and fails at the end of the installation.
My tablet is t-535
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the text in odin 3.09:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T535XXU1ANH6_T535PHE1ANH1_T535XXU1ANH6_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The solution is the pit, please give me
feuer1793 said:
Hello everyone, I'm new to this tablet and I need help. Sorry for my English
I tried putting a rom with odin and fails at the end of the installation.
My tablet is t-535
View attachment 3003086
View attachment 3003087
the text in odin 3.09:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T535XXU1ANH6_T535PHE1ANH1_T535XXU1ANH6_HOME.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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> FAIL! (Size)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The solution is the pit, please give me
Click to expand...
Click to collapse
Why a pit? I think the pit is still on the tablet but that you arez trying to flash a wrong/corrupted rom.
EDIT: you are flashing a wrong ROM. Probably because of carrier branding. Don't start playing with .pit. You will end up hard bricked after 1 little mistake!!!
Droidphilev said:
Why a pit? I think the pit is still on the tablet but that you arez trying to flash a wrong/corrupted rom.
EDIT: you are flashing a wrong ROM. Probably because of carrier branding. Don't start playing with .pit. You will end up hard bricked after 1 little mistake!!!
Click to expand...
Click to collapse
I download of sammobile 3 roms of spain, england and greece and not worked
http://forum.xda-developers.com/tab-4/general/guide-how-to-pit-file-qualcomm-device-t2932088
Well, I'm S4 I9505 user, have used almost every major custom ROMs. But due to battery drainage problems, I came back to stock kitkat. I flashed a stock kitkat rom usin mobile odin and I lost access to back and menu touch buttons but I rooted the phone and enabled soft keys by editing build.prop. All was ok and few days later I found an app on play store which had only one back button floating and it didnt even asked for root permissions. I was happy with this floating button so I tried to disable soft keys I previously enabled by editing build.prop. I used root explorer and deleted the line in build.prop I previously had added.
qemu.hw.mainkeys=1
I still remember I used to add
qemu.hw.mainkeys=0 to enable soft keys but it was changed when i deleted it. After deleting this last line, I restarted my phone and it just showed me 9505 logo then screen was all black but phone was not sleeping as it was being detected by my PC device manager. Smart switch and Kies3 arent detecting the phone. I wiped cache partition, but no success, then did factory reset. Phone has stock recovery.
I then tried to flash TWRP with odin but it said
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
<ID:0/012> Added!!
Then I flashed PIT file and this time,
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
<ID:0/012> Added!!
Now I entered both TWRP and PIT files but
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> recovery.img
<ID:0/012> NAND Write Start!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
<ID:0/012> Added!!
and my phone says,
Odin Mode
Product Name: GT-I9505
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: ENABLE
eMMC BURST MODE enabled
START {224, 1440}
BAR [240, 1440]
please help me.
MobilesGuru said:
Well, I'm S4 I9505 user, have used almost every major custom ROMs. But due to battery drainage problems, I came back to stock kitkat. I flashed a stock kitkat rom usin mobile odin and I lost access to back and menu touch buttons but I rooted the phone and enabled soft keys by editing build.prop. All was ok and few days later I found an app on play store which had only one back button floating and it didnt even asked for root permissions. I was happy with this floating button so I tried to disable soft keys I previously enabled by editing build.prop. I used root explorer and deleted the line in build.prop I previously had added.
qemu.hw.mainkeys=1
I still remember I used to add
qemu.hw.mainkeys=0 to enable soft keys but it was changed when i deleted it. After deleting this last line, I restarted my phone and it just showed me 9505 logo then screen was all black but phone was not sleeping as it was being detected by my PC device manager. Smart switch and Kies3 arent detecting the phone. I wiped cache partition, but no success, then did factory reset. Phone has stock recovery.
I then tried to flash TWRP with odin but it said
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Get PIT for mapping..
<ID:0/012> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
<ID:0/012> Added!!
Then I flashed PIT file and this time,
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
<ID:0/012> Added!!
Now I entered both TWRP and PIT files but
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> recovery.img
<ID:0/012> NAND Write Start!!
<ID:0/012> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/012> Removed!!
<ID:0/012> Added!!
and my phone says,
Odin Mode
Product Name: GT-I9505
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB: 0x30
WRITE PROTECTION: ENABLE
eMMC BURST MODE enabled
START {224, 1440}
BAR [240, 1440]
:laugh:
Click to expand...
Click to collapse
MobilesGuru said:
and I cant upload links/images too:laugh:
Click to expand...
Click to collapse
ChainFire's FlashFire was unable to flash this device before but Mobile Odin did the job.
These stock firmware I have tried
I9505XXUGNH7_I9505VFRGNH5_VD2
I9505XXUGNG8_I9505ITVGNG1_I9505XXUGNG8_HOME.tar
I haven't got a reply yet
Now phone says, firware upgrade error, please try in kies
where else I should go, I don't know. I don't believe in other forums.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally I successfully flashed the TWRP with PIT file in 3.04 Odin.
I copied Kushan V9 lite ROM to phone internal storage and now I'm going to flash them via TWRP:good:
This ROM is already rooted but I added latest Chainfire root zip too to flash.
and finally my 9505 is alive again.
here you can see my S4
MobilesGuru said:
here you can see my S4
Click to expand...
Click to collapse
Now my phone here is alive so I'm not going to use PC version of Odin.
I just got Odin mobile so I'm extracting the zip file of stock firmware.
Zip file extracted so now I have to manualy select partition which this file contained
Now I'm going to flash it. As I love to always be rooted so I didn't uncheck EverRoot.
So I'm done flashing the firmware.:silly:
MobilesGuru said:
Finally I successfully flashed the TWRP with PIT file in 3.04 Odin.
Click to expand...
Click to collapse
How did you able to fix this issue? I'm now facing it. Exactly like your case. Could you please help me out here.
Thank you!
Hello guys, I bought an older Galaxy S5 (G900F) from my friend. But he had a MIUI 7 ROM installed, I needed stock so I looked for some tutorials and what I did, I downloaded latest stock FW - https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/PHN/download/G900FXXS1CQI6/191506/, put it in Odin (AP), flashed, everything went fine till the end, when this happened -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thought it was a problem of unbranded FW and a PIT size, so I decided to try latest branded FW - https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/TNL/download/G900FXXS1CQI3/191276/, flashed through Odin, but in the end, again, the same error. Now the phone looks like this:
Is there a possibility to fix this? I am completely hopeless and really don´t know what to try. I can get into download mode, but not recovery mode. Any help or suggestion would be extremely highly appreciated. Thank you very much
Look, SM-G900F has several regional variants of firmware and some of them differ by hidden.img size significantly.
The problem is that:
1. You're trying to flash a firmware without pit-file and Odin cannot repartition the phone, but
2. This firmware does not match the current pit in your phone, hidden.img is bigger than the place for it in the phone's memory.
What to do (variants):
1. Get samfirm program (note: fw.updato.com or sammobile.com won't do) and download any FACTORY firmware for SM-G900F via this program. It contains necessary pit-file.
2. Go to this thread, download all SM-G900F pit-files from the second post and try to apply them one by one with that firmware you already have. At least one of them should work.
3. Open that firmware file bla-bla-bla.tar.md5 with 7-zip archiver and delete hidden.img from it. Save the firmware as bla-bla-bla.tar (remove .md5) and flash in Odin.
There're more variants but I think three will be enough for the moment.
The first variant is the most correct.
bbsc said:
Look, SM-G900F has several regional variants of firmware and some of them differ by hidden.img size significantly.
The problem is that:
1. You're trying to flash a firmware without pit-file and Odin cannot repartition the phone, but
2. This firmware does not match the current pit in your phone, hidden.img is bigger than the place for it in the phone's memory.
What to do (variants):
1. Get samfirm program (note: fw.updato.com or sammobile.com won't do) and download any FACTORY firmware for SM-G900F via this program. It contains necessary pit-file.
2. Go to this thread, download all SM-G900F pit-files from the second post and try to apply them one by one with that firmware you already have. At least one of them should work.
3. Open that firmware file bla-bla-bla.tar.md5 with 7-zip archiver and delete hidden.img from it. Save the firmware as bla-bla-bla.tar (remove .md5) and flash in Odin.
There're more variants but I think three will be enough for the moment.
The first variant is the most correct.
Click to expand...
Click to collapse
Oh man thank you, I thought it will remain dead, now I have some hope. But, I really don´t get HOW TO flash the pit. You mean flash the factory firmware (I have latest PHN), then I downloaded the first PIT from the post you mentioned, and now I don´t get how to flash it afterwards. I just read repartition must be ticked when flashing it
You don't need to flash pit separately.
Pit-file informs Odin how to repartition the phone's memory, it must be applied together with a firmware file.
Just look at Odin's interface carefully: there must be "repartition" option and a place where to insert a pit-file to.
bbsc said:
You don't need to flash pit separately.
Pit-file informs Odin how to repartition the phone's memory, it must be applied together with a firmware file.
Just look at Odin's interface carefully: there must be "repartition" option and a place where to insert a pit-file to.
Click to expand...
Click to collapse
This looks promising:
Found a Solution
First flash the firmware of choice let it fail.
Unplug the device and plug it back in with out rebooting it let it stay in the failed download mode.
Now uncheck the PDA/AP and add the PIT file attached here.
make sure repartion is checked and PDA/AP is not
Flash PIT and the phone will reboot and start up with your new firmware.
Note the PIT is for G900F 16GB EU
My log:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sbl1.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> aboot.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> modem.bin
<ID:0/005> cache.img.ext4
<ID:0/005> hidden.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
But it would mean he flashed it succesfully separately, am I missing something?
If you want "PHN" then you'll need this pit-file (attached).
bbsc said:
If you want "PHN" then you'll need this pit-file (attached).
Click to expand...
Click to collapse
I did it! I used first pit file for F version, flashed separately according to the procedure I found and posted above. Worked like a charm. I am so glad. Thank you for help!!
matthew1811 said:
I did it! I used first pit file for F version, flashed separately according to the procedure I found and posted above. Worked like a charm. I am so glad. Thank you for help!!
Click to expand...
Click to collapse
i experienced the same problem. So i followed the procedure above.
The thing is in second step the AP tab didn't recognize the pit file.
Any words?
I have being trying to root my Samsung Galaxy S7 Edge (Verizon). Android Version Oreo 8.0.0
Need help, tried a bunch of things I continue to get error codes from ODIN every time.
Example 1:
Log:
<ID:0/005> Added!!
<ID:0/005> Odin Engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 40m
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> RQT_CLOSE
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0/ failed 1)
<ID:0/005> Removed!!
<ID:0/004> Added!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot: prntscr.com/ n3d0xn
same issue
EquinoxPDX said:
I have being trying to root my Samsung Galaxy S7 Edge (Verizon). Android Version Oreo 8.0.0
Need help, tried a bunch of things I continue to get error codes from ODIN every time.
Example 1:
Log:
<ID:0/005> Added!!
<ID:0/005> Odin Engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 40m
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> NAND Write Start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> RQT_CLOSE
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0/ failed 1)
<ID:0/005> Removed!!
<ID:0/004> Added!!
Screenshot: prntscr.com/ n3d0xn
Click to expand...
Click to collapse
I am running into this very same issue with my SM-G930V running 8.0.0. Big bummer. I was looking forward to flashing Android Pie on my S7. I'm hoping for a solution to this problem soon.
calscoo said:
I am running into this very same issue with my SM-G930V running 8.0.0. Big bummer. I was looking forward to flashing Android Pie on my S7. I'm hoping for a solution to this problem soon.
Click to expand...
Click to collapse
If you figure out the problem could you let me know, because I'm still trying to figure it out.
EquinoxPDX said:
If you figure out the problem could you let me know, because I'm still trying to figure it out.
Click to expand...
Click to collapse
As long your are on or below U8 bootloader you can root, if you flash U9 then you can't downgrade nor root as far as today.
more info here for root u8 or below
https://forum.xda-developers.com/tm...ts-engboot-t3889844/post79228084#post79228084
zfk110 said:
As long your are on or below U8 bootloader you can root, if you flash U9 then you can't downgrade nor root as far as today.
more info here for root u8 or below
https://forum.xda-developers.com/tm...ts-engboot-t3889844/post79228084#post79228084
Click to expand...
Click to collapse
How do I find what boot loader i'm on?
EquinoxPDX said:
How do I find what boot loader i'm on?
Click to expand...
Click to collapse
go to settings, about and then look for baseband Version then start counting from right to left, 5th letter from right to left shows your bootloader version
zfk110 said:
go to settings, about and then look for baseband Version then start counting from right to left, 5th letter from right to left shows your bootloader version
Click to expand...
Click to collapse
Thank you. Baseband version: G935VVRS9CSC1 Is my device rootable?
EquinoxPDX said:
Thank you. Baseband version: G935VVRS9CSC1 Is my device rootable?
Click to expand...
Click to collapse
Quote:
Originally Posted by zfk110
As long your are on or below U8 bootloader you can root, if you flash U9 then you can't downgrade nor root as far as today unfortunately your on U9, see the 5th # its "9"
zfk110 said:
Quote:
Originally Posted by zfk110
As long your are on or below U8 bootloader you can root, if you flash U9 then you can't downgrade nor root as far as today unfortunately your on U9, see the 5th # its "9"
Click to expand...
Click to collapse
Dangit, so I just have to wait? I was looking forward to rooting.