Hi, can someone tell me how to create these files from sboot.bin with an Hex Editor
1. fwbl1 bl1
2. bl2 bl2
3. el3_mon el3
4. bootloader bootloader
5. tzsw tzsw
Novi1.bin 0..0x1FFF (size 0x2000 or 8192 )
Novi_2.bin 0x2000..0x31FFF (size 0x30000 or 196608)
Novi_3.bin 0x32000..0x3dfff (size 0xC000 or 49152)
Novi4.bin 0x3E000..10EFFF (size 0xD1000 or 856064)
or can someone upload it? I am a REAL NOOB in writing,editing or anything else in Hex and bin files
I tried this one posted here,
https://forum.xda-developers.com/galaxy-s6/general/guide-repair-hard-bricked-devices-t3573865
But i never could upload more then the first Novi.bin file and after that i became a write fail.
Sorry for my english too, i am german.
Thank You very much
Related
Hi! I've just got a O2 mini XDAII in Chinese Traditional OS. I want o flash the OS to English, can someone tell me where I can download an English ROM?
I have already backup my chinese rom as a nb1 file (with ntrw) but I've got no clue where to find an English rom (*.nb1) to flash...
Thanks a million!
ftp://xda:[email protected]
Hi there. I found a nb1 file and edit the first 220 byte. But when I ntrw write to my SD card, it says that the parameter is incorrect. Any ideas what this is?
Thanks!
C:\>ntrw write o2mini_asia.nb1 f:
NTRW v2.00
Removeable media
Cylinders: 0:973
TracksPerCylinder: 16
SectorsPerTrack: 32
BytesPerSector: 512
bufsize is 65536
WriteFile(): o2mini_asia.nb1 -- The parameter is incorrect.
first of all, use the first 416 bytes instead.
Then, you should place the rom file in c:\ as well as ntrw.exe
at c:\, ntrw write filename f:
please try.
hi were can i download to flash my mini xda from chinese to english tnxxxxx
Hello, I have some question regarding moding AMSS based on Android system.
1. With my analysis, there are two SHA160 hash under AMSS header section. Does anybody know the way to calc these two hash?
- I was able to modify RECOVERY section with mkbootimg.
I thought generating hash for AMSS might be same as hash for RECOVERY.
But, RECOVERY section only included one SHA160 hash but AMSS has two.
2. Alternatively, I thought I could alter bootloader to skip the integrity check.
Which bootloader should I modify to do this job?
- I found that my phone has 3 different Bootloade: DBL, FSBL, OSBL
DBL : 128KB
FSBL : 256KB
OSBL : 1152KB
I would like to share the information about the phone but I cannot tell the name of the phone because of a circumstance.
All I can say is that the phone is based on Snapdragon(Qualcomm).
Moreover, since this phone is not from known company, no one would have information anyway.
However, I think I could upload bootloaders from the binary.
Although my question might sound vogue, I hope there is someone who could help me to solve the problem
Thank you very much.
hmm... no one can help this problem?
This post is to collect and share everything there is to know about Odin v1.52. Collecting information from your knowledge and experience. Sharing by using the section titles to search particular information.
What do these options do? What do they effect on the device? If you know something or have experience with it, spill the info. If there is a link to another post, use the section title and add the link. I attached a screenshot of it and program.
***Important*****
For this to work right......
To Post. Copy the section title from the OP and give your response. ex.
Odin3 v1.52/Option/Re-Partition
This is ....or what I know about it.............
Then to find the info, search with that section title from the OP in the post to retrieve results
Search post:
Odin3 v1.52/Option/Re-Partition
Here are the sections..............
Odin3 v1.52/Developer
Odin3 v1.52/Uses
Odin3 v1.52/General
Odin3 v1.52/ID:Com
Odin3 v1.52/Option/
Odin3 v1.52/Option/Re-Partition
Odin3 v1.52/Option/Auto Reboot
Odin3 v1.52/Option/F. Reset Time
Odin3 v1.52/Option/Dump
Odin3 v1.52/Option/Dump/AP Ram
Odin3 v1.52/Option/Dump/AP Nand
Odin3 v1.52/Option/Dump/ID
Odin3 v1.52/Option/Phone EFS Clear
Odin3 v1.52/Option/Phone Bootloader Update
Odin3 v1.52/Message
Odin3 v1.52/Control Panel
Odin3 v1.52/Control Panel/Start
Odin3 v1.52/Control Panel/Reset
Odin3 v1.52/Pit
Odin3 v1.52/Files [Download]
Odin3 v1.52/Files [Download]/PDA
Odin3 v1.52/Files [Download]/Phone
Odin3 v1.52/Files [Download]/CSC
Odin3 v1.52/Files [Download]/ETC
Odin3 v1.52/File [Dump]
Odin3 v1.52/File [Dump]/Dump
Good day and God bless!
Odin3 v1.52/Developer
Interesting info about the program and where it came from
Link
http://androidforums.com/samsung-i7500/9078-what-odin.html#post373495
"I'm pretty sure Dejan did not write this tool. Someone can correct me here if I am wrong.
There is a string in 3.95:
"c:\Documents and Settings\seungbum223.kang\My Documents\Visual Studio 2008\Projects\MultiOdin\Release\MultiOdin.pdb"
A quick search turns up a patent application "APPARATUS AND METHOD FOR UPDATING BOOT LOGO IMAGE IN PORTABLE TERMINAL" by "Jeong-Hwan Min and Seung-Bum Kang" for "SAMSUNG ELECTRONICS CO., LTD."
So I'm pretty sure that MultiOdin is from Samsung, which means no source is available. It sure would be nice to reverse engineer what it is doing so we don't need odin anymore."
Odin3 v1.52/Pit
Odin3 v1.52/Pit
9.What is the .pit file? Why are there different versions?
There are now three different versions of the .pit file. 513.pit, 512.pit and 803.pit. 513.pit only works for early firmwares and should not be used anymore. The 512.pit file is used for all Android 2.1 Eclair firmwares and the Android 2.2 Froyo firmwares up to and including the I9000XXJP3 firmware. Several sources now indicate that the 803.pit file solves several problems with the Froyo firmwares released after XXJP3 (i.e. I9000ZSJP2 and I9000XXJPC) compared to the 512.pit file and should be used when flashing those.
What exactly the pit file actually does is somewhat unclear. Initially, it was believed to be responsible for mapping partition sizes but it has recently been suggested that the .pit maps certain files to certain partitions. Since Odin is closed source we cannot be sure at the moment.
http://forum.xda-developers.com/showthread.php?t=723596
Odin3 v1.52/Pit
Odin3 v1.52/Pit
"There is very little technical information on PIT files , so this thread is an attempt to find out some real details about PIT files, and perhaps eventually be able to create our own PIT files (by modifying Samsung ones, probably).
First, what we think we know PIT files do:
- PIT files only affect the 'STL' devices. That is, it affects the OneNAND and not the MoviNAND.
- PIT files appear to control the sizing (and maybe number) of STL devices that appear in Linux.
- PIT files appear to be used by Odin to map filenames inside .tar archives to STL partitions.
STL files are quite small, at under 2KB in size. Most of the file is made up of 0s. I have tried to compare the differences between the 512 513 and 803 PIT files we have available.
All the PIT files start with 76 98 34 12 0D - probably a signature to show it is a PIT file.
[Unimportant]
The 803 PIT file then has 00s all the way to the next common point. The 512 and 513 both have common data till the next common point - but this can't be too important as the 803 just has 00s.
The next common bit seems to read the following:
"oft IBL+PBL Server\90\To boot.bin inn; C:\Program Files\ESTsof
This probably indicates something to Odin. Strange that it has C:\Program Files\ - build path for the PIT file?
Next we have some 0s with common 1s inside them, followed by the word PIT, then more 0s, and then ries.pit. All common from here on with the words 'EFS' and 'efs.rfs'. Probably telling odin to map the efs.rfs file to the 'EFS' token. Tokens probably defined either in the kernel, or in the closed source STL library. More of the same of this, with 'SBL' 'sbl.bin', 'SBL2' 'sbl.bin' -- Both SBL and SBL2 map to the same sbl.bin file?
'PARAM' to 'param.lfs'
'KERNEL' to 'zImage'
'RECOVERY' to 'zImage' (this one is interesting - could we have seperate zImage and recovery? Could save some RAM here!)
[/Unimportant]
And now we'r onto the actual changes between the PIT files. 'FACTORYFS' maps to 'factoryfs.rfs'. However, before the FACTORYFS token, there are some bytes that likely control the partition sizes.
FACTORYFS
803 : A2 04 : 41476
512 : 7A 04 : 31236
513 : CA 04 : 51716
DBDATA
803 : F0 01 : 61441
512 : 18 02 : 6146
513 : C8 01 : 51201
CACHE
803 : 8C
512 : 8C
513 : 8C
MODEM
803 : 32
512 : 32
513 : 32
So there we have it. The only real changes between the PIT files are some seemingly garbage header information in 512/513 that is missing from 803, and FACTORYFS and DBDATA have different numbers -- probably sizes.
So assuming FACTORYFS maps onto /system, we can see that the only differences in the PIT files is moving space back and forwards between /dbdata and /system. The numbers themselves don't mean anything to me - can anybody work it out? "
http://www.galaxyroot.com/tag/pit/
plz help me , my GT-i9000 can active recovery mode and downloading mode but boths Odin3 v1.3 , v1.52 , v1.7 can't recognize my phone when i plug USB cable
my system information :
model number : GT-i9000
firmware ver : 2.2
Baseband Ver : I9000DTJP3
Kernel Ver : [email protected] #7
Build number: FROYO.DTJP5
thanks !!
my usb cable is good (tested)
Anyone knows the correct offset as
0x3000 is BL1 name> bl1
0x3000 ... 0x17000 is epbl
0x17000 ... 0x68000 is BL2
0x7e000 ... 0x7eb000 + 0x190000 = 0x1fe000 sboot
Dram_training do not need to be cut, it is not used in flashing
0x244000 ... 0x1BD000 is el3mon dram
can anybody please explain these files I have my Sboot.bin which was in the phone, I don't understand how to find correct offset/size. can some plz assist me, working on a750g. broke bootloader software version U1ARL3 for sboot
here is my sboot, can someone please create or show me how to. https://drive.google.com/file/d/1CcEqe4MH__APK7H42aP3H2KGdqkAi-xx/view?usp=drivesdk
I think I found bl1 bl2. So far multidownloader says transfer done bin 1 and bl2
Hello everyone,
Can someone explain why is this error happened,I tried to extract DZ file and here is the log.
Progress extractDZFlle Done !!
Complete on extract DZ partition files
Exception on extract partition file Ionic.Zlib.ZlibException: Bad state (incorrect header check)
at Ionic.Zlib.InflateManager.Inflate(FlushType flush)
at Ionic.Zlib.ZlibCodec.Inflate(FlushType flush)
at Ionic.Zlib.ZlibBaseStream.finish()
at Ionic.Zlib.ZlibBaseStream.Close()
at Ionic.Zlib.ZlibStream.Dispose(Boolean disposing)
at System.IO.Stream.Close()
at WindowsLGFramwareExtract.Form1.DZExtractBackprocess.extractDZFlle(ArrayList contents) in L:\Working_PROJECT\WindowsLGFramwareExtract\WindowsLGFirmwareExtract\Form1.cs:line 464
patched_sgpt_1024
userdata_4980736.img_38043648
userdata_2625552.img_35688464
userdata_2621440.img_35684352
userdata_2360584.img_35423496
userdata_2359296.img_35422208
userdata_1836296.img_34899208
userdata_1835008.img_34897920
userdata_1312008.img_34374920
userdata_1310720.img_34373632
userdata_787720.img_33850632
userdata_786432.img_33849344
userdata_263432.img_33326344
userdata_262144.img_33325056
userdata_5400.img_33068312
userdata_0.img_33062912
OP_OPEN_AU_DS.img_27279360
OP_OPEN_AU_DS.img_26755072
product_2899960.img_23855096
product_2854048.img_23809184
product_2625512.img_23580648
product_2364080.img_23319216
product_2360008.img_23315144
product_2101224.img_23056360
product_1839792.img_22794928
product_1835720.img_22790856
product_1576936.img_22532072
product_1315504.img_22270640
product_1311432.img_22266568
product_1052648.img_22007784
product_791216.img_21746352
product_787144.img_21742280
product_528360.img_21483496
product_266928.img_21222064
product_262856.img_21217992
product_4784.img_20959920
product_0.img_20955136
system_other_7520248.img_20955128
system_other_7401432.img_20836312
system_other_7340032.img_20774912
system_other_7079704.img_20514584
system_other_7077888.img_20512768
system_other_6555416.img_19990296
system_other_6553600.img_19988480
system_other_2361112.img_15795992
system_other_2359296.img_15794176
system_other_1836824.img_15271704
system_other_1835008.img_15269888
system_other_1312536.img_14747416
system_other_1310720.img_14745600
system_other_792256.img_14227136
system_other_788248.img_14223128
system_other_528296.img_13963176
system_other_267968.img_13702848
system_other_263960.img_13698840
system_other_5824.img_13440704
system_other_0.img_13434880
system_7520248.img_11452408
system_7401432.img_11333592
system_7340032.img_11272192
system_7079704.img_11011864
system_7077888.img_11010048
system_6555416.img_10487576
system_6553600.img_10485760
system_6033320.img_9965480
system_5771176.img_9703336
system_5509032.img_9441192
system_5246888.img_9179048
system_4984744.img_8916904
system_4722600.img_8654760
system_4460456.img_8392616
system_4198312.img_8130472
system_3936168.img_7868328
system_3674024.img_7606184
system_3411880.img_7344040
system_3149736.img_7081896
system_2887592.img_6819752
system_2625448.img_6557608
system_2365120.img_6297280
system_2361112.img_6293272
system_2101160.img_6033320
system_1840832.img_5772992
system_1836824.img_5768984
system_1576872.img_5509032
system_1316544.img_5248704
system_1312536.img_5244696
system_1052584.img_4984744
system_792256.img_4724416
system_788248.img_4720408
system_528296.img_4460456
system_267968.img_4200128
system_263960.img_4196120
system_5824.img_3937984
system_0.img_3932160
vendor_1982456.img_3932152
vendor_1951016.img_3900712
vendor_1835496.img_3785192
vendor_1835008.img_3784704
vendor_1311208.img_3260904
vendor_1310720.img_3260416
vendor_790752.img_2740448
vendor_786920.img_2736616
vendor_528120.img_2477816
vendor_266464.img_2216160
vendor_262632.img_2212328
vendor_4320.img_1954016
vendor_0.img_1949696
vbmeta_OPEN_AU_DS.img_1904640
tee.img_1894400
dtbo.img_1878016
boot.img_1796096
laf.img_1714176
logo.bin_1697792
lk.img_1695744
sspm.img_1693696
scp.img_1681408
spmfw.img_1679360
md1img.img_1474560
vbmeta_OPEN_AU_DS.img_1445888
tee.img_1435648
dtbo.img_1419264
boot.img_1337344
laf.img_1255424
logo.bin_1239040
lk.img_1236992
sspm.img_1234944
scp.img_1222656
spmfw.img_1220608
md1img.img_1015808
rct.img_875520
efuse.img_671744
ftm.img_432128
patched_pgpt_0
preloader.img_0