Post Reply

Rooted Firmware G800FXXU1ANG6_SER

OP Winstrol

18th August 2014, 06:18 PM   |  #11  
Junior Member
Thanks Meter: 1
 
20 posts
Join Date:Joined: Apr 2010
Quote:
Originally Posted by Winstrol

Rooted firmware G800HXXU1ANGD_SER for SM-G800H duos for Russian region with a lot of languages - version SM-G800H duos you can download here. Attention: It is work perfect for S5mini duos from Russian, but im not tested it with S5mini duos from another regions.

Dear Winstrol, thank you for the link but I keep getting the same error. Odin fails just when it starts "system.img.ext4" . I have tried it on several odin versions 1.3, 3.07, 3.09, on different pcs and using different USB cables :s i have even tried most of the firmwares on sammobile, I always get the same error. Any help in this?

Any idea why this is happening

The following is the log from odin:

<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G800HXXU1ANGD_SER_ROOT_NO_KNOX.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> sbl1.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> FAIL! (Ext4)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
19th August 2014, 07:37 AM   |  #12  
OP Member
Flag Moscow
Thanks Meter: 19
 
34 posts
Join Date:Joined: Jan 2008
I see a lot of people have same problem for s5mini when tried reinstall system.img.ext4, but unfortunately i don't understand why it happen.. It look like probably:
1. device have region lock
2. Samsung released a lot of versions s5mini with different stuffing and every different s5mini have different CRC and when ODIN started install system.img and compare CRC for current device stuffing, see it is different and stop the installing.
My recommendation - write the letter to Samsung support..
Sorry, i have no more ideas
The Following User Says Thank You to Winstrol For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes