Database Users

[Q] s4 i9506 update to 4.3 failed

tried to flash "I9506XXUBNA2_I9506OLBBNA1_XSP.zip (singapore)" to my new galaxy s4 4g+.
i used odin 1.85 at first but it failed, so i tried again with odin 3.09 i put the tar.md5 file in "AP" but still fails at "HIDDEN".
i am now only able to view "firmware upgrade encountered an issue. please select recovery mode in Kies & try again. which does not work,
the phone will not get listed.
also on that screen is :
ODIN mode
PRODUCT NAME: GT-I9506
CURRENT BINERY: Samsung official
SYSTEM STATUS: official
KNOX LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE
AP SWREV: S1, T1, R1, A1, P0
WRITE PROTECTION: enable
UDC START.
info from odin:
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9506XXUBNA2_I9506OLBBNA1_I9506XXUBMK7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> aboot.mbn
<ID:0/006> rpm.mbn
<ID:0/006> tz.mbn
<ID:0/006> sdi.mbn
<ID:0/006> NON-HLOS.bin
<ID:0/006> boot.img
<ID:0/006> recovery.img
<ID:0/006> system.img.ext4
<ID:0/006> modem.bin
<ID:0/006> cache.img.ext4
<ID:0/006> hidden.img.ext4
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
any ideas on how i can solve this?

fixed!
thanks to aresbv2000 for the solution! just install philz touch (link provided in quote).
aresbv2000 said:
flash this via odin after flashing the rom!
Click to expand...
Click to collapse
now my only issue is fixing the samsung keybord which keeps stopping every 5 seconds, manged to send the android keyboard from my old phone via wi-fi direct as a temp workaround. any clues?
update!
for complete solution click here:
http://forum.xda-developers.com/showthread.php?t=2622947

[Q] Newbie Helping : Note 3 soft bricked

Evening all ,
Hopefully someone here can help , Im somewhat of a newbie to this but was currently running Xnote Rom on 4.3 , I tried to upgrade to N9005XXUGNG1 following steps read on a well known website.
I received a "invalid ext4 image" error from odin and now stuck in a soft brick state where i can only access download mode. I am currently trying to get out of this back to a stock phone. I live in the UK and am on EE 4G.
Thanks in advance

UPDATE: Tried flashing N9005XXUDMK2_N9005OXXDMK3_N9005XXUDMJ7_HOME.tar.md5 with the following results:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXXDMK3_N9005XXUDMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

hmm..
try this..
take battery out and put it back in after 30 seconds.. then boot to download mode..
use odin to flash the latest gng1 rom..make sure to tick update bootloader in odin

take another stock ROM, you partition sizes dont seem to match to the rom u want to flash. i suggest to use the latest BTU Android 4.4.2 rom ( sammobile.com/firmware )

Killberty said:
take another stock ROM, you partition sizes dont seem to match to the rom u want to flash. i suggest to use the latest BTU Android 4.4.2 rom ( sammobile.com/firmware )
Click to expand...
Click to collapse
Could you tell me which one , as the latest i can see is the GNG1 and i am not getting on well with that at present

xinfinityoO said:
hmm..
try this..
take battery out and put it back in after 30 seconds.. then boot to download mode..
use odin to flash the latest gng1 rom..make sure to tick update bootloader in odin
Click to expand...
Click to collapse
Same problem..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005H3GGNG1_N9005XXUGNG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> 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! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Just to let you whats on my download screen too :
the little android man
ODIN MODE
PRODUCT NAME - SM-N9005
CURRENT BINARY: SAMSUNG OFFICAL
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK(KK): OFF
KNOX KERNAL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S2 T2 R2 A3 P1
WRITE PROTECTION: ENABLE
UDC START
ODIN : INVALID EXT4 IMAGE
Hope this helps ... And thanks for trying to help :cyclops:

Sometimes I get the android man and others I get a phone with a warning symbol and a pc saying " Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again".

Killberty said:
take another stock ROM, you partition sizes dont seem to match to the rom u want to flash. i suggest to use the latest BTU Android 4.4.2 rom ( sammobile.com/firmware )
Click to expand...
Click to collapse
It worked , Thank you !!! :good:

[unbrick] Samsung Note 3 n9005 brick ext4 error

Its my first post so i would like to say hello to You all.
I have bricked my phone. I cant enter recovery mode and i dont have software installed. I have honkong version 16gb sm-n9005. When im trying to flash offical rom N9005XXUGBOJ6 (polish XEO) by Odin I have error:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOJ6_N9005XEOGBOJ1_N9005XXUGBOJ1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> modem.bin
<ID:0/007> NON-HLOS.bin
<ID:0/007> recovery.img
<ID:0/007> rpm.mbn
<ID:0/007> sbl1.mbn
<ID:0/007> sdi.mbn
<ID:0/007> system.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)
In my phone its writthen
ODIN MODE
PRODUCT NAME SM-N9005
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Reactivation Lock: OFF
Knox Warranty Void: 0x1 (3)
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREW S2, T2, A2, A3, P3
SECURE DOWNLOAD ENABLE
UDC START
Volume Size is too big 4620288 < 4718592
ODIN : Invalid ext4 image
I have tried to find any pit file, but any pit file doesnt work. Dont know what to do next.
It would be great if you could help me.

Volume Size is too big 4620288 < 4718592
ODIN : Invalid ext4 image
AFAIK, HongKong phone can't be flashed with other region's fw due to some differences in hardware....
You must flash HK fw....

You are right, its working now. Do you know what custom rom can I install on Hong Kong version? I was trying to install Darklord note 5 port, but its bootlooping on samsung logo. So i stayed on CM 12.1.

Hard brick - Odin problems. - G900F

Hi.
Hard bricked SM-G900F
I can boot into download mode using the de-brick image HERE
Phone shows:
reactivation lock: OFF
knox warranty void: 0x1 (4)
qualcomm secureboot: enable (CSB)
AP SWAEV: S1 T1, R1, A1, P1
SECURE DOWNLOAD: ENABLE
Using Odin3 v3.11 I flash:-
G900FXXS1CPLV_G900FOXA1CPJ6_G900FXXU1CPJ1_HOME
Flash goes through fine (see below), but after reboot nothing happens.
I cannot enter download mode without the de-brick sdcard, and recovery just sits there on the samsung booting recovery screen.
If i connect the phone to my windows pc I see "qhsusb_bulk" listed in the device manager.
Any help would be awesome.
Cheers
Code:
<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> 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> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!

try a fresh download of the tar.md5 for your phone from sammobile.com/firmwares and flash it in Odin mode. Sounds like the bootloader is corrupt. So, once booted into the OS, youd have to manually move the bootloader from your debrick image to the internal SD with a terminal emulator

Screwed up flashing my Samsung Galaxy Note 4

The phone would start and all of a sudden shut off and either stay off or it would turn back on but go into the download mode, and very rarely it would turn back on properly, so being the hard headed 20 year old i am i tried to flash it without consulting help first
i have no idea what i did but now the device only loads into download mode (if it even turns on) ive tried to flash it properly now and it comes up with an error
ODIN log:
<ID:0/005> 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/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 3431 M
<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> aboot.mbn
<ID:0/005> sbl1.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> FAIL! (Write)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
what it says on the phone:
ODIN MODE (HIGH SPEED) {in red}
PRODUCT NAME: SM-N910F {in white}
CURRENT BINARY : Samsung Official {in white}
SYSTEM STATUS: Official {in white}
REACTIVATION LOCK: Off {in white}
KNOX WARRANTY VOID: 0x0 {in white}
QUALCOMM SECUREBOOT: Enabe (csb) {in grey}
RP SWREV: S1,T1,R1,A1,P1 {in grey}
SECURE DOWNLOAD: Enable {in blue}
UDC START {in red}
ODIN: flash write failure {in red}
Downloading...
Do not turn off target!!
{a progress bar that is frozen}(ive left it over night and it hasn't moved an inch)
I know this was me being hard headed and being stupid thinking it is simple but any help would be much appreciated, thank you in advance
PS
the model of the note 4 is :SM-N910F
PPS if i try to flash it again the odin log says:
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1301)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 3431 M
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005>
<ID:0/005> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

Hope it doesn't have an emmc problem.
Which files did you try to flash or was it just one?
If they latter use samfirmtool to download multiple part stock ROM by checking "binary nature" in its options.
As you are flashing one older ROM an older Odin might hekp as well not to mention other cables/USB ports.

it looks VERY emmc issue
and since you did not seek to get educated first, before doing anything... well you end up here
we try to help
so
read here, maybe it will work for you