4.3 Bootloader - Galaxy S 4 Q&A, Help & Troubleshooting

Hey everyone. I flashed the MI8 leak of TW 4.3, and it was decent, but I flashed the Google Edition by Jamal2367 and WiFi doesn't work, so I'm assuming it's because of this new bootloader. Is there anyway to either go back to the 4.2.2 bootloader (I assume it's highly unlikely) or to get WiFi and everything working?
Thanks
EDIT: Went to attempt to flash MH8 again (4.2.2) and even with the aboot file in it, Odin seems to be flashing it without a problem?
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> persdata.img.ext4
<ID:0/004> system.img.ext4
<ID:0/004> modem.bin
<ID:0/004> NON-HLOS.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
So could that mean it succesfully downgraded?

nellisere said:
Hey everyone. I flashed the MI8 leak of TW 4.3, and it was decent, but I flashed the Google Edition by Jamal2367 and WiFi doesn't work, so I'm assuming it's because of this new bootloader. Is there anyway to either go back to the 4.2.2 bootloader (I assume it's highly unlikely) or to get WiFi and everything working?
Thanks
Click to expand...
Click to collapse
Try flash NON-HLOS Bin for older firmware

LastStandingDroid said:
Try flash NON-HLOS Bin for older firmware
Click to expand...
Click to collapse
Didn't try that before downgrading but looks like it did downgrade the bootloader! No more eMMC boost thing in the bootloader. Already had Knox warranty void 0x1 so couldn't see if it triggered it. Now going to try Google Edition ROM again.
EDIT: Yes, after downgrading from MI8 (4.3 inc bootloader) to MH8 worked, and now WiFi works on 4.2.2 roms!

Related

Flashing ROM odin error

Hi,
I;ve posted this issue before but no one answered my previous thread ( T_T )
the issue still hasn't changed.
Trying to flash a Australian ROM on to my N9005.
getting this error in odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENE3_N9005VAUENF1_N9005XXUENE3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<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> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing EU ROM's are fine as I'm currently using the UK 4.4.2 ROM N9005XXUGNG1
Please HELP; as it seems I cant use 4G with this ROM
you cant flash older fw, NG1 is new dont downgrade to older
Both 4.4.2
Thanks for reply!
Yes I'm aware that you can't downgrade.
Both ROM'S are 4.4.2 it just always fail at the same point no matter what.
The only thing that is different is one ROM is branded and one isn't
The one I'm trying to flash is Vodafone.
soulzsium said:
Thanks for reply!
Yes I'm aware that you can't downgrade.
Both ROM'S are 4.4.2 it just always fail at the same point no matter what.
The only thing that is different is one ROM is branded and one isn't
The one I'm trying to flash is Vodafone.
Click to expand...
Click to collapse
Your current version is GNG1 while the rom being flashed is ENE3 (older).
Try to flash the newer one.
vndnguyen said:
Your current version is GNG1 while the rom being flashed is ENE3 (older).
Try to flash the newer one.
Click to expand...
Click to collapse
N9005XXUGNG1 this was released in August
N9005XXUENE3 this was released in July
so I can't flash to a release that was a month old?
I thought that as long as the boot loader was the same version I could flash freely?
soulzsium said:
N9005XXUGNG1 this was released in August
N9005XXUENE3 this was released in July
so I can't flash to a release that was a month old?
I thought that as long as the boot loader was the same version I could flash freely?
Click to expand...
Click to collapse
Not sure if they have the same bootloader version?
You can only check for the bootloader version after install it.
vndnguyen said:
Not sure if they have the same bootloader version?
You can only check for the bootloader version after install it.
Click to expand...
Click to collapse
They are both KitKat 4.4.2 so I'm assuming yes
soulzsium said:
They are both KitKat 4.4.2 so I'm assuming yes
Click to expand...
Click to collapse
I'm not too sure, sorry. You have to check for the bootloader version.
Or you can also flash the modem (baseband) separately.
soulzsium said:
Hi,
I;ve posted this issue before but no one answered my previous thread ( T_T )
the issue still hasn't changed.
Trying to flash a Australian ROM on to my N9005.
getting this error in odin
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENE3_N9005VAUENF1_N9005XXUENE3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<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> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Flashing EU ROM's are fine as I'm currently using the UK 4.4.2 ROM N9005XXUGNG1
Please HELP; as it seems I cant use 4G with this ROM
Click to expand...
Click to collapse
The problem is your original pit file. As you can see problem is related to hidden partition that is to small for the image from your room that you want to flash(is the place where of in is stopping and give you error). To solve this you need to flash a pit file compatible with the room that you want to flash. What exactly do you want to achieve flashing this room anyway? ..
---------- Post added at 06:56 PM ---------- Previous post was at 06:39 PM ----------
If just LTD is your problem then check this:
<br />
Use ES File explorer or your favorite root explorer and go to data/property and find the persist.radio.lteon.xml file. Open it in Text Editor and if the value that is written is false, change it to true. Save and exit and reboot. Got the options back. Done.<br/>

SOLVED! Bricked note 3

Hello, I hope you could help me.
I tried to flash original rom with Odin, so I could install cwm and root, but that's what happened... It's bricked now...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005GBLGNG1_N9005XXUGNG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.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> modem.bin
<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)
Thanks!
Emil
does it start normally???certainly no so flash again with odin and get last 3.09 version
from which rom version are you starting???
rayman95 said:
does it start normally???certainly no so flash again with odin and get last 3.09 version
from which rom version are you starting???
Click to expand...
Click to collapse
I bought it yesterday. It said it needed update, so I updated , this update is from July 2014.
It was working fine, I wanted to install recovery and flashed original rom, and then it started giving me those error messages with Odin 3.09.
I've tried Odin 3.07, the same result.
Then I found a polish, 4 files stock rom (BT, Phone, PDA and CSC) it passed, but I locked it and it doesnt work good. Sometimes it does not start... What can I do?
Thanks in advance!
Emil
emilloparski said:
Hello, I hope you could help me.
I tried to flash original rom with Odin, so I could install cwm and root, but that's what happened... It's bricked now...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005GBLGNG1_N9005XXUGNG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.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> modem.bin
<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)
Thanks!
Emil
Click to expand...
Click to collapse
What did you select in Odin, which buttons? PDA? Or which? That could've bricked it...
emilloparski said:
Hello, I hope you could help me.
I tried to flash original rom with Odin, so I could install cwm and root, but that's what happened... It's bricked now...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005GBLGNG1_N9005XXUGNG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.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> modem.bin
<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)
Thanks!
Emil
Click to expand...
Click to collapse
i got desame error but ive already done with this probem. TRY tO CHANGE STOCK FIRMWARE YOU HAVE TRYING TO FLASH (THE FIRMWARE YOU HAVE TO DOWNLOAD IS NEAR IN YOUR COUNTRY NOT FAR IN YOUR COUNTRY) TRY NH1 FIRMWARE. if i help you press thanks.
emilloparski said:
Hello, I hope you could help me.
I tried to flash original rom with Odin, so I could install cwm and root, but that's what happened... It's bricked now...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGNG1_N9005GBLGNG1_N9005XXUGNG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.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> modem.bin
<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)
Thanks!
Emil
Click to expand...
Click to collapse
Well, it didn't pass. go to samobile and download your region's firmware and try again. Which bootloader did you use? KK? If you took KK you might have to try and solve the issue with bootloader. If you don't care about root, try installing another kernel and install CWM. Might fix it.
Did you tick 'Re-Partition' in Odin?
Pagnell said:
Did you tick 'Re-Partition' in Odin?
Click to expand...
Click to collapse
Ignore this one. Do NOT tick Re-partition.
Pagnell... if you want to be helpful, as least fully state what you are trying to tell.
Your question might make him tick that selection.
Solved. I was told that any stock rom from my region would work. Since I bought it and live in Bulgaria, I tried the BG one. Didn't match. Itried it 4-5 times. Then I tried highly recommended polish one which was older, but it locked my phone ( btw it's a polish imported phone ). Then I tried last german, last Bulgarian and last UK. Didn't help. Until I finally tried last Slovakian which worked and it' similiar to the last Polish that I was planning to test after that. So Slovakian Telekom finally worked. And I was about to try it even earlier, but there was this recommended 4 file polish one that everyone was talking about that "works"

[Q] G900F - odin fail to flash Lolipop

Hello guys!
I am on stock 4.4.2
Downloaded stock rom from sm.
Tried to flash - fail at hidden.img.ext
FLASh failed.
Now i can't boot my phone.
Knox is still on 0x0
Kies doesnt recognise my phone to try recovery...
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BNL9_G900FVFG1BNL1_G900FXXU1BNL9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<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> modem.bin
<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)
What to do?
The obvious answer is to flash the rom again in Odin.
If no joy with flashing Lollipop try and flash a Kitkat rom and then try flashing Lollipop again.
Try Odin 3.07
I had the same problem with 3.09, spend several hours flashing and downloading the FW again and again. I finally tried with Odin 3.07 and everything is OK.
apmos said:
Try Odin 3.07
I had the same problem with 3.09, spend several hours flashing and downloading the FW again and again. I finally tried with Odin 3.07 and everything is OK.
Click to expand...
Click to collapse
Will try now.
tried with 3.10.0 still nothing
Tried with stock 4.4.2. still the same....and on the other computer too with windows 7
before was doing on windows 8
So...odin 3.07:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BNL9_G900FVFG1BNL1_G900FXXU1BNL9_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<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> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
NOT GOOD AT ALL!
I can't flash any rom to G900F with odin, can't boot my phone...constantly getting FAIL (SIZE)!
What to do next?
This is info from the screen:
ODIN MODE
PN: SM-G900F
CB: Samsung Official
SS: Official
RL (KK): OFF
KWV: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV
SECURE DOWLOAD: ENABLE
UDC START
Don't get it.
I have tried SPANISH firmware LOLIPOP 5.0 (unbranded) and it worked!?!
I am on Croatian VIP network, bought it there...tried to flash VIP's 4.4.2 and 5.0
and it failed everytime no matter to ODIN version....
So? What to do next? Why i am not able to flash my branded firmware?
Usually when that message appears in odin it means the the firmware you're trying to flash has not the same partitions as your memory, try to find pit file for your VIP version and then flash again using that file
Well let it fail then remove the cable put it back reset odin check repartition and flash put file.. your phone will work but i have not idea what is tha secure boot and download i am still searching.

Lollipop update issue.

Hi guys.
I have an italian unbranded phone n9005.
Today i've tried flashing a german and a UK n9005 lollipop rom from sammobile with odin.
In both cases odin failed the last step while flashing hidden.img and gave me error "fail (size)"
Now i can still access to download mode but i have no clue of what to do.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOA5_N9005VFGGBOA2_N9005XXUGBOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<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> modem.bin
<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)
Thanks for your time
Try This
is your note3 rooted or stock ?
I have a stock Note3 LTE and downloaded the XEO (polish) from sammobile firmwares and it worked perfectly because it is an unlocked rom. You can download it from here http://samsung-updates.com/device/?id=SM-N9005&details=Galaxy_Note_3__Snapdragon Roms that are network branded can quite often fail in the way yours did.
To get out of your current position you have 2 choices...You can download the above and simply follow normal Odin procedure or you can flash your old rom again.
Uxepro said:
Hi guys.
I have an italian unbranded phone n9005.
Today i've tried flashing a german and a UK n9005 lollipop rom from sammobile with odin.
In both cases odin failed the last step while flashing hidden.img and gave me error "fail (size)"
Now i can still access to download mode but i have no clue of what to do.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUGBOA5_N9005VFGGBOA2_N9005XXUGBOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<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> modem.bin
<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)
Thanks for your time
Click to expand...
Click to collapse
Solved. Just flash an unbrand FW on an unbrand phone
billd2439 said:
is your note3 rooted or stock ?
I have a stock Note3 LTE and downloaded the XEO (polish) from sammobile firmwares and it worked perfectly because it is an unlocked rom. You can download it from here http://samsung-updates.com/device/?id=SM-N9005&details=Galaxy_Note_3__Snapdragon Roms that are network branded can quite often fail in the way yours did.
To get out of your current position you have 2 choices...You can download the above and simply follow normal Odin procedure or you can flash your old rom again.
Click to expand...
Click to collapse
Will this work on my rooted n90005.
And can you send me a link to step by step rooting guide?
Sent from my SM-N9005 using Tapatalk
Couldn't be certain but I believe if you install an official rom on a rooted phone the root is lost. That would meet it should install no problem and restore the phone to stock.

Return to stock odin FAIL

Im trying to return to stock and Odin fails at the very end of the flash each time. I was running blisspop before trying to flash, and i did a factory reset as well before trying to flash.
this is what the log says in odin
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<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> modem.bin
<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)
You put the phone in recovery mode or download mode during flashing?
skrcer1 said:
Im trying to return to stock and Odin fails at the very end of the flash each time. I was running blisspop before trying to flash, and i did a factory reset as well before trying to flash.
this is what the log says in odin
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1100)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<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> modem.bin
<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)
Click to expand...
Click to collapse
Download mode
androidtweaker1 said:
You put the phone in recovery mode or download mode during flashing?
Click to expand...
Click to collapse
Download mode
Are all the usb drivers installed?
skrcer1 said:
Download mode
Click to expand...
Click to collapse
androidtweaker1 said:
Are all the usb drivers installed?
Click to expand...
Click to collapse
Yes I have successfully flashed on this PC before
androidtweaker1 said:
You put the phone in recovery mode or download mode during flashing?
Click to expand...
Click to collapse
lol what question man stop kiding
ext 4 fail mean not same pit with your phone ty another stock rom or trick pit option with your pit ( if you want only this rom )
popmpopm said:
lol what question man stop kiding
ext 4 fail mean not same pit with your phone ty another stock rom or trick pit option with your pit ( if you want only this rom )
Click to expand...
Click to collapse
I tried using a different pit and it didn't seem to help.
I asked because some people use recovery mode while flashing.
Thanks for the additional info though :good:
popmpopm said:
lol what question man stop kiding
ext 4 fail mean not same pit with your phone ty another stock rom or trick pit option with your pit ( if you want only this rom )
Click to expand...
Click to collapse
popmpopm said:
lol what question man stop kiding
ext 4 fail mean not same pit with your phone ty another stock rom or trick pit option with your pit ( if you want only this rom )
Click to expand...
Click to collapse
how do I find the correct pit file for my rom? Im pretty sure i have the correct one but just in case??
androidtweaker1 said:
I asked because some people use recovery mode while flashing.
Thanks for the additional info though :good:
Click to expand...
Click to collapse
custom roms work and this stock rom actually did boot up even though it said failed in odin, although it was buggy in some places. Any ideas how to go back completely to stock?
What version of odin you using.
Asking because I was unable to flash stock whenever I used 3.10
3.07 worked for me
skrcer1 said:
custom roms work and this stock rom actually did boot up even though it said failed in odin, although it was buggy in some places. Any ideas how to go back completely to stock?
Click to expand...
Click to collapse
im using 3.10, ill try 3.07 and report back.
androidtweaker1 said:
I asked because some people use recovery mode while flashing.
Thanks for the additional info though :good:
Click to expand...
Click to collapse
androidtweaker1 said:
What version of odin you using.
Asking because I was unable to flash stock whenever I used 3.10
3.07 worked for me
Click to expand...
Click to collapse
Still a fail...
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOC7_G900FOJK1BOC2_G900FXXU1BOC7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<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> 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> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Same as before, I put in the pit file, put in the firmware, factory wiped my phone, put into download mode, plugged it in then started the flash.
I remember I had the same issue before but the XEO (polish firmware) flashed properly, I just tried it again and it works. Why wont my other stock firmware work? It should be the same european pit as the XEO firmware. Maybe a different bootloader or something? Or maybe it is a different pit? I want to install the ILO firmware, what pit does it need?
If you have custom recovery try flashing a stock rom through that method. If using Odin method, try taking the battery out of your phone first, put it back in and then boot phone directly into download mode, then try flashing. From the log you posted it looks as though you have a bad stock rom file. Try downloading another one or use different version of Odin like 3.07. Here is the link to all the CSC codes that may help: http://forum.xda-developers.com/showthread.php?t=800257 If you cant find any help with that link try this one: http://www.galaxys5update.com/galaxy-s5-sm-g900f-europe-android-4-4-2-g900fxxu1ance-firmware-stock-rom-list/ Hope this helps you out some.
skrcer1 said:
Still a fail...
<ID:0/003> Added!!
<ID:0/003> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900FXXU1BOC7_G900FOJK1BOC2_G900FXXU1BOC7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<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> 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> modem.bin
<ID:0/004> cache.img.ext4
<ID:0/004> hidden.img.ext4
<ID:0/004> FAIL! (Size)
<OSM> All threads completed. (succeed 0 / failed 1)
Same as before, I put in the pit file, put in the firmware, factory wiped my phone, put into download mode, plugged it in then started the flash.
I remember I had the same issue before but the XEO (polish firmware) flashed properly, I just tried it again and it works. Why wont my other stock firmware work? It should be the same european pit as the XEO firmware. Maybe a different bootloader or something? Or maybe it is a different pit? I want to install the ILO firmware, what pit does it need?
Click to expand...
Click to collapse
try to flash this last stock rom mega:///#!1AgXRSJC!qLhH124dDQE7marSruk89mAbVROJxGFF3bvXloyHYFc
for xeo you have last boj1
hi,
this happened to me and i followed the instructions from here : https://www.reddit.com/r/GalaxyS6/comments/35zshn/howto_fix_a_failed_odin_flash_softbrick_hiddenimg/
and this fixed it so i could go back to complete stock
odin 3.09 and usb 2.0 cable try
Usb 2.0 port used for flash frm lap
So I looked inside the md5 file and there is no such file hidden.img.ext4 maybe that is what the problem is? Can someone really show the line to normal stock ROM that can be flashed without all those trouble.
guys just tried flashing again with 6.0.1 netherlands and the same thing is happening, i think the problem was the XEO csc from the xeo 5.0 firmware but how do i fix it?!?!?!?!

Categories

Resources