<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
Related
Hello guys.
I have a SM-N9005 free from carrier.
My note was originaly on a 4.3 Fw french unlocked version. Since the french havent released the 4.4.2 fw i went right ahead and tryed to upgrade via ODIN to 4.4.2. So i downloaded the AUT (Swiss no carrier) version of 4.4.2, and tryed to flash it with ODIN 3.09.
The thing is right on the end i get an error on ODIN and now i am stuck with this screen! But KIES doesnt recognize my Note 3.
http://i2.wp.com/androidcentral.us/wp-content/uploads/2013/09/Firmware-upgrade-error.png
The ODIN info in the end is the following:
<OSM> N9005XXUENA6_N9005AUTENA2_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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! (Size)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me?!
PunK_BoY said:
Hello guys.
I have a SM-N9005 free from carrier.
My note was originaly on a 4.3 Fw french unlocked version. Since the french havent released the 4.4.2 fw i went right ahead and tryed to upgrade via ODIN to 4.4.2. So i downloaded the AUT (Swiss no carrier) version of 4.4.2, and tryed to flash it with ODIN 3.09.
The thing is right on the end i get an error on ODIN and now i am stuck with this screen! But KIES doesnt recognize my Note 3.
http://i2.wp.com/androidcentral.us/wp-content/uploads/2013/09/Firmware-upgrade-error.png
The ODIN info in the end is the following:
<OSM> N9005XXUENA6_N9005AUTENA2_N9005XXUENA2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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! (Size)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone help me?!
Click to expand...
Click to collapse
Try Poland Fw 4.4.2 which works flawless with many
I am trying to do that but from sammobile its taking me 9 hours to download it! Can i take it from any other place faster?!
PunK_BoY said:
I am trying to do that but from sammobile its taking me 9 hours to download it! Can i take it from any other place faster?!
Click to expand...
Click to collapse
If u downloading threw sammobile u need o register with Tera for fast download otherwise try from below link for Mega
http://forum.xda-developers.com/showthread.php?t=2608458&page=2
jdomadia said:
If u downloading threw sammobile u need o register with Tera for fast download otherwise try from below link for Mega
http://forum.xda-developers.com/showthread.php?t=2608458&page=2
Click to expand...
Click to collapse
Tks. Now downloading from MEGA. Will give feedback.
ITS ALIIIIIIVE!!!! Thank you very much dear sir!
PunK_BoY said:
ITS ALIIIIIIVE!!!! Thank you very much dear sir!
Click to expand...
Click to collapse
Good to hear enjoy
I am having the same issue atm..
I know this thread is old but it's the only one I've found where the issue is identical to mine. I've been looking on sammobile for the poland version but there are so many different ones listed under Poland with what I'm guessing are the different carriers. Can you link me the version that you had previously mentioned? Would really help me a lot.
Cheers.
Edit: it worked!! But now.. I don't have the same network settings like 4G :/
<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
Now I've searched just about all of Google on this, but I haven't been able to find a solution yet. Everyone here seems to know the most about this kind of stuff so I figured I'd make an account and explain my situation.
Backstory / How it happened
So, earlier today I figured I'd root my AT&T S7 Edge, I used a tutorial from Max Lee (I can't post links yet but if you need to find it I'm sure you can Google it) to get the job done, and after a while I managed to get the thing rooted. I knew absolutely nothing about what the hell flashing, roms, bricked phones, bootloops etc. were and now I only know a bit about them. So the phone was rooted just fine, I had SuperSU running, and a few other root apps, but then I figured I'd install xposed installer. So I went ahead and downloaded the wrong version (whoops) and it installed its framework and then said it needed to reboot my phone, low and behold we have a bootloop. It stays at the AT&T logo indefinitely if I'd let it. I'll happily admit to that being completely my mistake, I read the warning that it may cause a bootloop but I went ahead and installed it anyway thinking I could fix it if it happened. (This thread is my walk of shame I suppose)
Solutions I've tried
Now that the background has been explained, I'll go through the list of solutions I've tried, mind you I'm no expert at any of this so some of the info I give may seem redundant or nonsensical.
- Rebooting into recovery and clearing cache and factory resetting in every order you can imagine
* Only interesting thing I could find is that it still says custom on both the download mode (the one where you press vol down, power, and home) and when you reboot the phone and it goes through the initial animation, it shows custom with a little settings-looking icon just before it goes through the AT&T animation and takes a **** on my self esteem.
- Waiting ~1 hour for the AT&T logo to change to something other than an AT&T logo (I was desperate)
* Yeah nothing came out of that one...
- Flashing every stock firmware I could find on the internet, with every version of Odin I could find.
* Kept getting the same error, "FAIL! (Auth)". I looked it up and all I found was old threads from 2013 on the Galaxy S4, with some now-irrelevant information, I couldn't seem to get it to work, but I'm positive that's what I need to do unless you guys know another solution. Here's the full log:
Code:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Don't know what I did but after that at the download screen it says at the top left "SW REV CHECK FAIL : [aboot]Fused 4 > Binary 2
Sorry for the wall of text, I tried to format it as nicely as possible to make it somewhat readable. If anyone needs more info let me know.
Can you flash TWRP? If you can maybe you can boot into TWRP and then try to flash any rom from XDA and see if it comes alive...
alehawk said:
Can you flash TWRP? If you can maybe you can boot into TWRP and then try to flash any rom from XDA and see if it comes alive...
Click to expand...
Click to collapse
Thank you for the response
I've tried getting TWRP to work, but apparently there still isn't a way to get it working on the AT&T, I was under the impression that it was only for international and Korean versions. I haven't been able to find any version of TWRP that works for my device.
However I just did try some newer stock firmware from, "theandroidsoul" which partially worked, being that I'm desperate and don't know what I'm doing I just tried flashing all three:
G935AUCS4API2 - This one worked more than the others, but it seems at some point it disconnects for whatever reason, causing it to fail. After that my phone gave me the whole "You messed up go use smart switch" deal, and smart switch was saying my device was unsupported. That said I'm not sure what is causing the fake USB disconnect cause I can hear the windows sound for the USB disconnecting, but I'm not sure why.
Here's the log:
Code:
<ID:0/005> Odin engine v(ID:3.1203)..
<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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> tz.mbn
<ID:0/005> hyp.mbn
<ID:0/005> devcfg.mbn
<ID:0/005> pmic.elf
<ID:0/005> rpm.mbn
<ID:0/005> cmnlib.mbn
<ID:0/005> keymaster.mbn
<ID:0/005> apdp.mbn
<ID:0/005> msadp.mbn
<ID:0/005> cmnlib64.mbn
<ID:0/005> sec.dat
<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> __XmitData_Write
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
And here's the log after another try (I factory reset and wiped cache again to give it another go)
Code:
<ID:0/005> Odin engine v(ID:3.1203)..
<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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> xbl.elf
<ID:0/005> tz.mbn
<ID:0/005> hyp.mbn
<ID:0/005> devcfg.mbn
<ID:0/005> pmic.elf
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/005> Removed!!
<ID:0/005> Added!!
I found it interesting that it got even less far than before.
G935AUCS2APH1 - Stopped at lksecapp.mbn then went to FAIL! (Auth). There was no disconnect or reconnect
G935AATT2APG1 - Same as above
I seem to be stuck in a similar situation. Did you ever find a fix?
wunderkinder said:
I seem to be stuck in a similar situation. Did you ever find a fix?
Click to expand...
Click to collapse
I had the at&t s7 edge before and had the same problem but not sure if it was the same odin error.
But this is how you flash a stock rom on the at&t:
-You must use the princecomsy odin (search for it on google)
-Here is the stock rom with the latest security update (type "G935AUCS4BRA1" in the google search bar)
(I wasn't allowed to post links)
unzip and flash
tell me how it goes
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!!
Help! I have a Tab 4 SM-T530NN that I need the firmware for and I can't find a US copy anywhere. I tried a SM-T530NU version of the firmware and it mostly loaded. The MODEM.BIN part failed. The tablet boots and looks ready except it will not allow me turn on the WIFI, which I guess is due to the modem load failing. Any suggestions ?
this is the messages ODIN showed:
C:\Users\Jerry\Downloads\SM-T530NUUEU1BOE5_XAR_SERVICE_LP\AP_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 1971 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> persist.img.ext4
<ID:0/007> modem.bin
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ttold12 said:
Help! I have a Tab 4 SM-T530NN that I need the firmware for and I can't find a US copy anywhere. I tried a SM-T530NU version of the firmware and it mostly loaded. The MODEM.BIN part failed. The tablet boots and looks ready except it will not allow me turn on the WIFI, which I guess is due to the modem load failing. Any suggestions ?
this is the messages ODIN showed:
C:\Users\Jerry\Downloads\SM-T530NUUEU1BOE5_XAR_SERVICE_LP\AP_T530NUUEU1BOE5_CL4910899_QB4956020_REV00_user_low_ship_MULTI_CERT.tar.md5
<ID:0/007> Odin engine v(ID:3.1401)..
<ID:0/007> File analysis..
<ID:0/007> Total Binary size: 1971 M
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> NAND Write Start!!
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> persist.img.ext4
<ID:0/007> modem.bin
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
I finally found a source that had a SM-T530NN firmware file, they had to pull it from their archives for me. all is good now, I have my Tab 4 working again. I just have to remember next time to check the battery level before starting a system restore. my bad....
ttold12 said:
I finally found a source that had a SM-T530NN firmware file, they had to pull it from their archives for me. all is good now, I have my Tab 4 working again. I just have to remember next time to check the battery level before starting a system restore. my bad....
Click to expand...
Click to collapse
I am having the same problem while installing LineageOS 18.1. Can you share the source for the firmware? I am having a really hard time finding this model number online.
Thanks in advance!