Guys Here I Present Some time of Work and For people Who are lazy this will help !!!
These zips and tar.md5's are for people who don't know how to start these are the latest OFFICAL CWM recoveries touch and non touch versions
These are the offical versions taken from the official site and I converted them to flasble zips and tar.md5's
P3100 Normal -----> flasble tar.md5 HERE
P3100 Touch ------> flasble tar.md5 HERE
P3100 Normal -----> flasble zip HERE
P3100 Touch -----> flasble zip HERE
-------------------------------------------------------------------------------------------------------------------
P3110 Normal ----->flasble tar.md5 HERE
P3110 Touch ------> flasble tar.md5 HERE
P3110 Normal -----> flasble zip HERE
P3110 Touch ------> flasble zip HERE
-------------------------------------------------------------------------------------------------------------------
P3113 Normal ------> flashble tar.md5 HERE
P3113 Touch ------> flashble tar.md5 HERE
P3113 Normal -----> flashble zip HERE
P3113 Touch -----> flashble zip HERE
-------------------------------------------------------------------------------------------------------------------
How to flash tar.md5'sFlash with Odin as PDA
How to flash zip filesFlash from exsiting recovery
please write the version number.
I think
GT-P3100 and GT-P3110: CWM 6.0.2.7
GT-P3113: CWM 6.0.2.3
Right?
Whats the point if I made my own with philz?
Sent from my LG-P690b using Tapatalk 2
Luigi2012SM64DS said:
Whats the point if I made my own with philz?
Click to expand...
Click to collapse
??
I love PhilZ more then CWM.
Awesome man thanks, for some reason the latest recovery, compiling from source, won't boot and hasn't booted for awhile for the p3113. Been using 6.0.2.3. +1 for the flashable zips, no easy way for people to tar files if they don't have a linux box!
CodyF86 said:
(..) +1 for the flashable zips, no easy way for people to tar files if they don't have a linux box!
Click to expand...
Click to collapse
Sure, it is easy now for Windows user - because of mythi have a look: http://forum.xda-developers.com/showthread.php?t=2387138
Android-Andi said:
Sure, it is easy now for Windows user - because of mythi have a look: http://forum.xda-developers.com/showthread.php?t=2387138
Click to expand...
Click to collapse
ah nice. Everytime I've tried to use a tar file made in windows though it never works out very well, but I'm sure that works, a-ok!
Godbless Ubuntu.
CodyF86 said:
ah nice. Everytime I've tried to use a tar file made in windows though it never works out very well, but I'm sure that works, a-ok!
Godbless Ubuntu.
Click to expand...
Click to collapse
I haven´t tried if it works No need to flash it at the moment. But i think it will work...
i only converted a recovery.img without problems to a recovery.tar.md5 using mythi´s script.
Android-Andi said:
I haven´t tried if it works No need to flash it at the moment. But i think it will work...
i only converted a recovery.img without problems to a recovery.tar.md5 using mythi´s script.
Click to expand...
Click to collapse
Oh im sure it works, Gonna try to see why the latest recovery isn't booting from source at some point soon.
Thanks for your support guys !!!!
P3113 Normal ------> flashble tar.md5
Click to expand...
Click to collapse
I keep getting "MD5 hash value is invalid" in Odin when trying to flash this
gooffeyguy said:
I keep getting "MD5 hash value is invalid" in Odin when trying to flash this
Click to expand...
Click to collapse
rename into recovery.tar.md5 and it will work
Thanks, that worked
That happens because @mythi changed the name of the file after he build the *.tar.md5
There is an md5 added into this file (for your safety) wich needs the same filename as at the buildingprocess. (sorry for my bad english i hope you understand)
Android-Andi said:
That happens because @mythi changed the name of the file after he build the *.tar.md5
There is an md5 added into this file (for your safety) wich needs the same filename as at the buildingprocess. (sorry for my bad english i hope you understand)
Click to expand...
Click to collapse
Or like I said remove the .md5 extension. Leave it as .tar. Thats easier I guess.
Android-Andi said:
That happens because @mythi changed the name of the file after he build the *.tar.md5
There is an md5 added into this file (for your safety) wich needs the same filename as at the buildingprocess. (sorry for my bad english i hope you understand)
Click to expand...
Click to collapse
Thanks It is safer to keep the md5 just rename recoveryXXXXX.tar.md5 to recovery..tar.md5
Links no longer open?
Sent from my GT-P3113 using Tapatalk HD
you can find links in first post here http://forum.xda-developers.com/showthread.php?t=2391355
Can I flash through stock recovery
Sent from my GT-P3110 using xda app-developers app
no, for *.tar.md5 you have to use odin.
for *.zip you need a custom recovery
Related
hey guys,
I've got a problem with dbl.mbn... When Im flashing my (test) ROM it is stuck on this.. I've got the dbl.mbn and some other files from broodplank1337 to fix some bugs in my ROM..
Floris
FlorisNL said:
hey guys,
I've got a problem with dbl.mbn... When Im flashing my (test) ROM it is stuck on this.. I've got the dbl.mbn and some other files from broodplank1337 to fix some bugs in my ROM..
Floris
Click to expand...
Click to collapse
Have you tried remaking the md5 package?
broodplank1337 said:
Have you tried remaking the md5 package?
Click to expand...
Click to collapse
nope.. this is the way I installed it:
open the tar file with 7zip
putted the files in
made it an tar.md5 file
flashed
FlorisNL said:
nope.. this is the way I installed it:
open the tar file with 7zip
putted the files in
made it an tar.md5 file
flashed
Click to expand...
Click to collapse
it doesnt work like that. you need to rebuild the whole package again
broodplank1337 said:
it doesnt work like that. you need to rebuild the whole package again
Click to expand...
Click to collapse
and how im gonna do that?
If you have cygwin on your pc then do this
cd <to whichever location you'r rom files are in>
tar -cvf blablabla.tar <file1> <file2> <file3>..........
md5sum -t blablabla.tar >> blablabla.tar
mv blablabla.tar > blablabla.tar.md5
hi, please i need help about unpack and repack galaxy mini stock roms (.tar.md5) cause i wanna remove bootloader (arm11boot) to avoid physical domage to my mini;
i didn't find the rom what im searching for in this thread: http://forum.xda-developers.com/showthread.php?t=1551586
i need this middle east rom: http://www.hotfile.com/dl/155191960/b13d98c/S5570JPKT2_S5570OJPKT2_EGY.zip.html but without bootloader;
thankx
Send a pm to annson08.. Include the link and he may do it for you..
kitrax59 said:
Send a pm to annson08.. Include the link and he may do it for you..
Click to expand...
Click to collapse
Don’t give me a fish, teach me how to fish.
I would like to help you fishing but I'M NOT RESPOSIBLE IF YOU ENDED BY CACHING A SHARK
I had downloaded a rom with removed bootloader from annson08 thread, by opening the .tar archive i noticed that he did just removed the arm11boot file from the package nothing else.
so maybe removing this file from your ROM and flashing it like usual will do the trick
Do It At Your Own Risk
Unpack rom..search bootanimation.zip.....replace with any other of ur choice
....repack
Sent from my GT-S5570 using xda premium
bilel2301 said:
hi, please i need help about unpack and repack galaxy mini stock roms (.tar.md5) cause i wanna remove bootloader (arm11boot) to avoid physical domage to my mini;
i didn't find the rom what im searching for in this thread: http://forum.xda-developers.com/showthre...?t=1551586
i need this middle east rom: http://www.hotfile.com/dl/155191960/b13d...Y.zip.html but without bootloader;
thankx
Click to expand...
Click to collapse
unpack rom and its contents
open boot.image
in that remove arm11 boot
pack your rom !
flash it via odin
abdovar said:
I would like to help you fishing but I'M NOT RESPOSIBLE IF YOU ENDED BY CACHING A SHARK
I had downloaded a rom with removed bootloader from annson08 thread, by opening the .tar archive i noticed that he did just removed the arm11boot file from the package nothing else.
so maybe removing this file from your ROM and flashing it like usual will do the trick
Do It At Your Own Risk
Click to expand...
Click to collapse
i know that he just removed arm11boot but when i did that with many method i didn't succed to add it to "odin multi downloader" it crashs every time when i add the new file without bootloader i think that is not just unpack,remove and repack there is something special to make odin fish a fish not a shark
bilel2301 said:
i know that he just removed arm11boot but when i did that with many method i didn't succed to add it to "odin multi downloader" it crashs every time when i add the new file without bootloader i think that is not just unpack,remove and repack there is something special to make odin fish a fish not a shark
Click to expand...
Click to collapse
He wrote it in his thread...
I believe the method requires linux (/cygwin)...
Edit: no, I couldn't find it... :sad:
Typed on a small touchscreen
a.cid said:
He wrote it in his thread...
I believe the method requires linux (/cygwin)...
Edit: no, I couldn't find it... :sad:
Typed on a small touchscreen
Click to expand...
Click to collapse
yeah i used cygwin too but i failed to make the output file work on odin!!!
i used this method from yagya:
Code:
cd firmware_directory
// Goes inside firmware directory
tar -cf firmware_name.tar amss mibib oemsbl qcsbl boot.img recovery.img system.rfs csc.rfs
// This will create a tar_file named firmware_name.tar containing all the files mentioned afterwards. You'll need to check if all files except arm11boot are included or not and add (or remove) to or from above list.
md5sum firmware_name.tar >> firmware_name.tar
// Checks md5sum of the tar file.
mv firmware_name.tar >> firmware_name.tar.md5
// Renames the firmware file. The outcome of this is your flashable zip file.
[optional] gzip firmware_name.tar.md5
//zips the firmware_name.tar.md5 file as gz format. It is easier while sharing the file since it reduces the file size by almost 50 %.
you did everything correct but the problem of Odin crashing is its a md5 file then you remove the arm11boot md5 of file changes which makes the Odin crash
steps to correct it:-
1. extract everything from package
2. delete arm11boot
3. then download a software which can create a tar package
4. with that software create an empty tar package
5. put all the files in that tar package
then then you are ready to flash
dhlalit11 said:
you did everything correct but the problem of Odin crashing is its a md5 file then you remove the arm11boot md5 of file changes which makes the Odin crash
steps to correct it:-
1. extract everything from package
2. delete arm11boot
3. then download a software which can create a tar package
4. with that software create an empty tar package
5. put all the files in that tar package
then then you are ready to flash
Click to expand...
Click to collapse
it doesn't work also!!!! i flash it with (.tar) odin freeze in "download amss" and with (.tar.md5) odin crash also like using cygwin!!! i think that i really need help from annson08, i pm him but he didn't answer :/ :/
bilel2301 said:
it doesn't work also!!!! i flash it with (.tar) odin freeze in "download amss" and with (.tar.md5) odin crash also like using cygwin!!! i think that i really need help from annson08, i pm him but he didn't answer :/ :/
Click to expand...
Click to collapse
hey sorry for the late reply, really busy at the moment. I believe yagya made a tutorial about this...wait....hmmmm....ahh here it is,
http://handyinformation.freevar.com/showthread.php?tid=8&pid=12#pid12
that's not how I do things but that link also works.
annson08 said:
hey sorry for the late reply, really busy at the moment. I believe yagya made a tutorial about this...wait....hmmmm....ahh here it is,
http://handyinformation.freevar.com/showthread.php?tid=8&pid=12#pid12
that's not how I do things but that link also works.
Click to expand...
Click to collapse
the link that you send to me is the link of my thread in yagya's forum
i try yagya's method but it doesn't work for me :/ :/
please when you have time pm how to do it thankx
Cus im trying to cook my own rom with a stock kernel, and then test it out on my 5830i, heres the question, Would that work?
or can i somehow get the lockscreen out of it and flash it on xxla2, would that also work?
im doing it only for the lockscreen cus it looks nice.
any help will be appreciated.
S5839i = s5830i
GermainZ said:
S5839i = s5830i
Click to expand...
Click to collapse
Okay thanks!
and do you maybe know how to take the lockscreen out of 5839i stock ROM? i downloaded it from samfirmware.com and i have a .md5 file and i dunno how to extract it
cwm
GermainZ said:
S5839i = s5830i
Click to expand...
Click to collapse
in my s5839i it not run cwm of s5830
i run it and it was error (status 7) pliz help me
5830 =/= 5839i
5830i = 5839i
Dowload CWM from unbrick tutorial
On dev section and try again.
Verify zip, make sure if the file isnt corrupted. If is the right zip.
And, 'install zip from sd card' not :'install update.zip' if have both options.
Sent from my GT-S5830i using xda app-developers app
help 2
_framos said:
5830 =/= 5839i
5830i = 5839i
Dowload CWM from unbrick tutorial
On dev section and try again.
Verify zip, make sure if the file isnt corrupted. If is the right zip.
And, 'install zip from sd card' not :'install update.zip' if have both options.
Sent from my GT-S5830i using xda app-developers app
Click to expand...
Click to collapse
i run update istall from samsug default recovery and it serror (status 7)
in cwm site havn'nt this file with me, have only for s5830
can you update this file... i can't find it. or if you cant send me a link.
Qnrx said:
Okay thanks!
and do you maybe know how to take the lockscreen out of 5839i stock ROM? i downloaded it from samfirmware.com and i have a .md5 file and i dunno how to extract it
Click to expand...
Click to collapse
Split it with Split2FUS take the pda rename it from tar.md5 to tar open it with wirar extract system.img you can open it with DiskInternals Linux reader.
Lockscreens are in android.policy.odex or android.policy.jar but you need to deodox it.
Why don't you just take the file android.policy.jar from a custom rom ? you can then extract it with backsmali.jar with the command java -jar baksmali.jar android.policy.jar -o nameofthefolder .
I want to add firekernel into VO-1 CM7 rom but i wanna ask if it's ok to just DRAG and DROP kernel files into rom.zip.
It's safe or not ?
Install ROM and then install fire kernel zip....
pvrx said:
Install ROM and then install fire kernel zip....
Click to expand...
Click to collapse
I want to integrate kernel in rom ...
Its safe. Drag and drop boot.img and system files from the kernel's flashable zip into the rom's zip.
tj_droid said:
Its safe. Drag and drop boot.img and system files from the kernel's flashable zip into the rom's zip.
Click to expand...
Click to collapse
Thanx man !
tj_droid said:
Its safe. Drag and drop boot.img and system files from the kernel's flashable zip into the rom's zip.
Click to expand...
Click to collapse
What do u mean?
Do u mean that I can just paste all the kernel files into Rom.zip via WinRAR?
I had tried it today,but it just made my device bootloop...
SOS!!!
Dragonkind said:
What do u mean?
Do u mean that I can just paste all the kernel files into Rom.zip via WinRAR?
I had tried it today,but it just made my device bootloop...
SOS!!!
Click to expand...
Click to collapse
Yes, drag and drop kernel files work 100%.
Just drag the right kernel ...
I'm not a "recognised dev" and honestly I'm only a bit better than a noob but usually to create a flashable rom i do this things:
1)i customize my rom and i flash the kernel i want..
2)i do a nandroid backup, i extract the /system folder which is ".tar" using "zArchive" (I'm not sure about the name you can search on play store "tar opener")
3)i "steal" a meta-inf folder from other rom and finally i create a zip file with a)boot.img; b)meta-inf; c)system.
To do this i don't need to switch my computer on!!
Inviato dal mio GT-S5830 con Tapatalk 2
Hi,
I want to use stock backup to made my own ROM
But I don't know how to switch with backup to a flashable ROM..
I search "kitchen" but all I find was not compatible with HTC ONE M7..
Thanks a lot for your help
nathan30 said:
Hi,
I want to use stock backup to made my own ROM
But I don't know how to switch with backup to a flashable ROM..
I search "kitchen" but all I find was not compatible with HTC ONE M7..
Thanks a lot for your help
Click to expand...
Click to collapse
you should use Google
http://forum.xda-developers.com/showthread.php?t=2626007
http://androidforums.com/motion-4g-...as-android-kitchen-deodxing-cooking-roms.html
clsA said:
you should use Google
http://forum.xda-developers.com/showthread.php?t=2626007
http://androidforums.com/motion-4g-...as-android-kitchen-deodxing-cooking-roms.html
Click to expand...
Click to collapse
You again
Thanks for your link. For the first, is it compatible with all model of phone ?
nathan30 said:
You again
Thanks for your link. For the first, is it compatible with all model of phone ?
Click to expand...
Click to collapse
Yes building a rom is pretty much the same across all htc devices
getting the updater-script correct is the tricky part
clsA said:
Yes building a rom is pretty much the same across all htc devices
getting the updater-script correct is the tricky part
Click to expand...
Click to collapse
Okay thanks a lot, I had to put "thanks" again
clsA said:
Yes building a rom is pretty much the same across all htc devices
getting the updater-script correct is the tricky part
Click to expand...
Click to collapse
Sorry to come again..
I download Kitchen by Dsixda to try. I download the rooted twrp backup and I put the file in the folder in the kitchen directory.
But kitchen say the files of the backup doesn't match and so it don't see any ROM...
The backup is composed with 3 files :
recovery.log
system.ext4.win000
system.ext4.win001
Thanks a lot..
nathan30 said:
Sorry to come again..
I download Kitchen by Dsixda to try. I download the rooted twrp backup and I put the file in the folder in the kitchen directory.
But kitchen say the files of the backup doesn't match and so it don't see any ROM...
The backup is composed with 3 files :
recovery.log
system.ext4.win000
system.ext4.win001
Thanks a lot..
Click to expand...
Click to collapse
your answer is in the first link
http://forum.xda-developers.com/showthread.php?t=2626007
This link ?
I need to unpack the file ? Because I don"t have a system.img...
nathan30 said:
http://forum.xda-developers.com/showthread.php?t=2626007
This link ?
I need to unpack the file ? Because I don"t have a system.img...
Click to expand...
Click to collapse
Here
--- Go ahead and make a copy of your boot and system backup and paste them in the original_update folder which can be found in the kitchen directory. From a 'TWRP backup' the boot.img will be originally named boot.emmc.win and the system.img will originally be named system.ext4.win. Go ahead and change them respectively to boot.img and system.img (It is that easy).
Click to expand...
Click to collapse
Yes sorry I don't read enough...
the first file (1gb) system.ext4.win000 is system
the other (53mb)system.ext4.win001 is boot.img or no ?
nathan30 said:
Yes sorry I don't read enough...
the first file (1gb) system.ext4.win000 is system
the other (53mb)system.ext4.win001 is boot.img or no ?
Click to expand...
Click to collapse
no their both system.img ..just split
just open them one at a time to the same folder
okay great. Unzip the two files, in one folder system ?
So I don't need boot.img ?
nathan30 said:
okay great. Unzip the two files, in one folder system ?
So I don't need boot.img ?
Click to expand...
Click to collapse
yes you do
the boot.img will be originally named boot.emmc.win
Click to expand...
Click to collapse
I don't have this file in the backup..
nathan30 said:
I don't have this file in the backup..
Click to expand...
Click to collapse
here's a normal backup of mine
boot.emmc.win < boot.img
boot.emmc.win.md5
cache.ext4.win
cache.ext4.win.md5
data.ext4.win < data.img
data.ext4.win.md5
recovery.emmc.win < recovery.img
recovery.emmc.win.md5
recovery.log
system.ext4.win < system.img
system.ext4.win.md5
Click to expand...
Click to collapse
all the files you need were in the orig link i gave you here
6.09.401.5
http://forum.xda-developers.com/showpost.php?p=54894697&postcount=7526
I download the backup on the thread you give me and I just have the two files...
clsA said:
here's a normal backup of mine
all the files you need were in the orig link i gave you here
6.09.401.5
http://forum.xda-developers.com/showpost.php?p=54894697&postcount=7526
Click to expand...
Click to collapse
I see your edit and I download one of this link : https://www.androidfilehost.com/?fid=23622183712462462
But there is not all the file, just the two I said before...
I had to download the ota maybe ? (557mb)
Thanks in advance
nathan30 said:
I see your edit and I download one of this link : https://www.androidfilehost.com/?fid=23622183712462462
But there is not all the file, just the two I said before...
I had to download the ota maybe ? (557mb)
Thanks in advance
Click to expand...
Click to collapse
The kernel is the boot.img
The stock recovery is their also
clsA said:
here's a normal backup of mine
all the files you need were in the orig link i gave you here
6.09.401.5
http://forum.xda-developers.com/showpost.php?p=54894697&postcount=7526
Click to expand...
Click to collapse
clsA said:
The kernel is the boot.img
The stock recovery is their also
Click to expand...
Click to collapse
Oh okayyyy, so I have to download the stock rom rooted (this http://goo.gl/zN5ARs) for the system.img
And the stock kernel (this https://www.androidfilehost.com/?fid=23622183712462443) to rename in boot.img ?
I need to put stock recovery and firmware or it's not necessary ?
nathan30 said:
Oh okayyyy, so I have to download the stock rom rooted (this http://goo.gl/zN5ARs) for the system.img
And the stock kernel (this https://www.androidfilehost.com/?fid=23622183712462443) to rename in boot.img ?
I need to put stock recovery and firmware or it's not necessary ?
Click to expand...
Click to collapse
Not needed for a custom Rom