• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root .ops file for odin?

well i found out is can be opend/edited with notpad++
this is one from the prevail


Code:
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,
i think i can figure out what to do with it or how to duplicate it for the ultra... but if anyone knows anything about it please inform me/us as to what exactly it is... all im good at is plug-n-play (if A does not work, try B, then C)... i will figure it out, but help will speed it along:)
 
yea, thats what i have found too. they are all the same, you just need to rename it to match your model
 
yea, thats what i have found too. they are all the same, you just need to rename it to match your model
i've been talking to interdpth on this and he said its not that simple. If you just use one from another phone you WILL brick your phone.. he did a few times trying to figure it out.. His phone is at samsung right now cause odin bricked it so hard.. let the experts do their magic.. I also talked to Hroark13 which is who got Odin working on the prevail and he said he had to do A LOT of searching to find a phone with an exact partition map to the prevail and finally found that the galaxy mini was. so he used the ops from that and renamed it for the prevail..

The ops for the prevail will not work for the ultra. you will brick your phone and will be sending it to samsung to be fixed if you try that.

Interdpth told me that there is no phone like the ultra so the ops has to be made and he has been working hard on this for quite a while. also, he told me that the block names on the phone eg. recovery is mmcblk0p8. in Odin its 6. it has a totaly different method of how it flashes everything.. Basically he had to just try and test till it was right and hope it didnt brick it too hard but eventually it did so he is waiting for it to come back to try again..
 
Thanks for helping and looking into it maverik, I know its not an easy task... but I do think if we come together as a team and work on it together and share info with each other we would have a better chance at getting it done. I know we have a lot of people with bricked phones that will be glad to test, they got nothing to loose and a great phone to gain. I'm not try to take away glory from anyone I just see a serious need to get odin done, that's why I'm posting finding for all to alaberate on. I'm sure I'm not the only one that feels this way...

So anyone that can help out in any wat or form, please do, and share what you learn.
 
i've been talking to interdpth on this and he said its not that simple. If you just use one from another phone you WILL brick your phone.. he did a few times trying to figure it out.. His phone is at samsung right now cause odin bricked it so hard.. let the experts do their magic.. I also talked to Hroark13 which is who got Odin working on the prevail and he said he had to do A LOT of searching to find a phone with an exact partition map to the prevail and finally found that the galaxy mini was. so he used the ops from that and renamed it for the prevail..

The ops for the prevail will not work for the ultra. you will brick your phone and will be sending it to samsung to be fixed if you try that.

Interdpth told me that there is no phone like the ultra so the ops has to be made and he has been working hard on this for quite a while. also, he told me that the block names on the phone eg. recovery is mmcblk0p8. in Odin its 6. it has a totaly different method of how it flashes everything.. Basically he had to just try and test till it was right and hope it didnt brick it too hard but eventually it did so he is waiting for it to come back to try again..
thanks for setting me straight :)
 
Oh im all about teaming up on it lol. thats what this awesome community is all about:D

That is exactly why I started to look into it is because so many people have bricked or semi bricked phones and I feel bad for them. wish I could help em all..

I don't think you came off as trying to steal anyones thunder smith and your right on the money.. we need odin bad!! I'm reluctant to do certain things because we dont have a way to get back. It really hinders development on a device until you get it.

Post what you got!!

I already have extracted the /system /data kernel and recovery from a stock rooted rom
tared em up and md5 checksumed them too but we need that ops made

oh and P.S. If you can boot to the samsung screen and the phone holds enough for your pc to detect it then I can save you!!!!! just P.M me and I'll be glad to help you get your phone back
 
i did a serch for "odin ops file" and found a few ops's
i did not look into what the phone was/is so i dont know the relivance but there are didfrant setups like mavrik said... this is what i found:

So how de we go about finding out our combination for the Ultra?



Ancora.ops
Code:
0,partition
1,dbl
2,osbl
3,amss
4,emmcboot
5,adsp
6,boot
7,system
8,cache
9,userdata
10,recovery
11,persist
12,preload
apollo_0531.ops
Code:
0,boot
1,Sbl
2,logo
3,efs
4,zImage
5,factoryfs
6,datafs
7,cache
8,
9,modem
EUROPA_I5500_v1.0.ops
Code:
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,
EUROPA_I5508_v1.0.ops
Code:
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,
spica.ops
Code:
0,boot
1,Sbl
2,logo
3,zImage
4,factoryfs
5,datafs
6,cache
7,
8,modem
9,efs
spica_jc3.ops
Code:
0,boot
1,Sbl
2,logo
3,zImage
4,datafs
5,factoryfs
6,cache
7,
8,modem
9,efs
TASS_v1.0.ops
Code:
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,

GIO_v1.0.ops
Code:
0,mibib
1,qcsbl
2,oemsbl
3,amss
4,arm11boot
5,boot
6,recovery
7,system
8,data
9,csc
10,


So how de we go about finding out our combination for the Ultra?
 
Interdpth told me he just tried shit till he got it right. I don't know if he actually found a reference from another phone or what

what Hraork13 told me he did was he got the PHONE, PDA, and BOOT files from the prevail and looked at them in a hex editor

then he dowloaded the same odin files from other samsung phones until he found one that mached almost exactly (Galaxy Mini) and used the ops from that odin package and tested it. when it worked he just renamed it for his Odin package.

I have been doing this for the TU but haven't found one yet I've looked at about 6-7 different phones so far but I also havent had much time to spend on this... Family and work have consumed most of my time the past week or so..

a turn-key ops would be the fastest solution for us and it would save Interdpth a whole lot of headache as well. we just need a few people searching on this and we might just find one.

So,
1. find a list of Samsung phones
2. pick one
3. search for that phones odin package(if it has one)
4. use a HEX editor to open the TU files and files from whatever phone you chooes and compare them
5. If they match then you would try to find out a mount map of that phone as well.. Ask one of the devs in the forum to give you one
adb shell
$su
#cat /proc/partitions
and it will print out all the mount points for that device. get em to paste it for you somwhere and see if it matches the TU's map. (really this part is more important than checking the odin packages) if the journaling system (ext4), the type of memory(EMMC), and the mount point numbers & types (dev/block/mmcblk0p(15) system) are all identical then we should be good with that ops file
 
WHOO HOO... WHOO HOO... YEEHAW... WHOO HOO... |:back_flips:|

lol i hope it works! it WILL be one of the bigest steps in the develepment of this phone :)
 
For the Samsung Galaxy Wonder

Code:
 179        0    3864576 mmcblk0
 179        1     106495 mmcblk0p1
 179        2        500 mmcblk0p2
 179        3       3596 mmcblk0p3
 179        4          1 mmcblk0p4
 179        5       5120 mmcblk0p5
 179        6      20000 mmcblk0p6
 179        7       3072 mmcblk0p7
 179        8       5632 mmcblk0p8
 179        9       6488 mmcblk0p9
 179       10       3072 mmcblk0p10
 179       11       3072 mmcblk0p11
 179       12       8192 mmcblk0p12
 179       13       7680 mmcblk0p13
 179       14       5120 mmcblk0p14
 179       15     547840 mmcblk0p15
 179       16      61440 mmcblk0p16
 179       17    1136640 mmcblk0p17
 179       18      51200 mmcblk0p18
 179       19        500 mmcblk0p19
 179       20       3596 mmcblk0p20
 179       21       5120 mmcblk0p21
 179       22      20000 mmcblk0p22
 179       23       5120 mmcblk0p23
 179       24       7000 mmcblk0p24
 179       25       5120 mmcblk0p25
 179       26       5120 mmcblk0p26
 179       27       5120 mmcblk0p27
 179       28    1787904 mmcblk0p28
 179       32    1927168 mmcblk1
 179       33    1926144 mmcblk1p1


It seems to be verry close with same layout but idk If this is close enough
 
Well... if you use yours and brick it... I'm sure you will find out the right combo by the end of the day... LOL ... there are a few people that have bricked phones.... maybe team Weaver would be a great option for someone. They could have a running phone in a few mins.
 
Back
Top Bottom