I have the i9000 jk3 files from samfirmware.com, but im looking for a CWM flashable version of it, or instructions on how to create one from the .rfs files in samsung's version. Im interested in changing some things for a personal rom, but just need JK3 as a starting point since it seems to be what everyone considers the best right now.
Related
Hi all!
Downloading custom ROMs is VERY cool, but a bit of a pain sometimes because the downloads are huge. I have a suggestion about how this could be resolved.
To explain my idea, let's look at how you would flash a ROM using the new method being suggested. You'd need the following things...
- USPL (as usual)
- Custom RUU (as usual)
- 'Control' ROM NBH
Here's the first difference. The control ROM in my proposal is the widely circulated HTC ROM NBH, which can be found here. You'd keep the NBH from this ROM (RUU_Signed.nbh) named as HTC.nbh, and it would be used by all subsequent updates.
So let's imagine that I have a device (USPL'd of course) that I want to flash to the T-Mobile ROM. I'd make sure I had a directory with the Custom RUU and Control ROM NBH in, then i'd download the file from the ROM creator. In this file would be a batch file, a ROM patch and the patcher. The batch file would patch HTC.nbh to T-Mobile spec, then run Custom RUU. The beauty of it? The download would be very small!
Would it work? YES! And to prove a point, please check out this post - where you'll find Orange, T-Mobile and Tilt ROMs in tiny downloads based off the control NBH. ROM chefs - let's start using this system, which i'm calling 'Kaiser TLR ROMs' for obvious reasons.
ROM chefs, to create the patches you just need to use bsdiff, which can be found here. Use the syntax 'bsdiff HTC.nbh YourROM.nbh YourRom.patch'. You can see a sample batch file in my link above.
So... what do u think?
TLR
I don't get it once your HTC is HardSPL'ed then there is no CID lock and you can flash any rom to your device. Most rar files containing the RUU_signed.nbh are only 40-50MB thats pretty small and can be deleted when your finished flashing. To me this seems like a lot of extra work for the cook(sometimes me) and more support issues I find it easy just to upload the ROM i made to rapidshare or some other file hosting site and people can download as they like.
40-50MB is a lot bigger than 6-7MB.
It's not a lot of extra work at all really, it's running one command line, and distributing a couple of files.
I think patching definitely has potential, not least that they are a lot easier (and a lot less illegal?) to host.
TLR
theloanranger said:
40-50MB is a lot bigger than 6-7MB.
It's not a lot of extra work at all really, it's running one command line, and distributing a couple of files.
I think patching definitely has potential, not least that they are a lot easier (and a lot less illegal?) to host.
TLR
Click to expand...
Click to collapse
Sounds interesting about the legal hosting capability for diff ROM files instead entire ROM. The ROM archive goes down in the past for the M$ pressing . If we can archive only diif ROMs, this can be one solution to take back the ROM archive into the FTP at XDA.
One offtopic question, where did you get the Orange Shipped ROM for Kaiser?
Cheers.
I didn't, it's a dump and repack, as is the T-Mo one.
TLR
I have a rom (*.nbf) that someone made there are more likes than dislikes, but I wanted to take his rom rip it back down prior to the rom so that I can remove and add my own stuff. Can you point me in the right direction. I seem to find stuff about ripping a rom but they referance a *.nbh file. all I got is the *.nbf.
also when I break the file back down does it keep all the tweeks just the way they were prior or do I have to re add them?
- Albert
I recommend HyperCore to do this. Its a kitchen up in the stickies at the top of the rom. It has a nice setup for pulling a rom apart (basically drop the nbf into the extract area and then use the panel to do the extract), and then moving it into the kitchen and then building it back into a custom rom by manipulating the OEM packages, etc.
Good luck
I have that aready but it asks for a nbh file and i have a nbf. Do you know where there may be a better cookbook?
almulder said:
I have that aready but it asks for a nbh file and i have a nbf. Do you know where there may be a better cookbook?
Click to expand...
Click to collapse
i thought that it asks for an nbf, but i think you can just rename it.... im sure someone will correct me because that doesn't sound right
anyways i always use the core pro kitchen
http://forum.xda-developers.com/showthread.php?t=313859&highlight=core+pro
very user friendly, i've had issues with hypercore...
okay, so im flashing my nook with Cyanogenmod v.11....
i found what i thought was it but doesnt appear to be.
i have a zip for NookHDplus-CWM-6046-for-internal-memory-rev0-(07-13-14) but it doesnt have the files that it is suppost to come with because people say that same thing should have more files and different files. some say it's a zip, some say it's a rar. but my question is: how do i find it? all the sources are so old that they refer to the site that shut down.
where can i get the proper version of it?
Hey all,
I'm looking at getting into firmware modding and was wondering where would be a good place to start. Initially I'm just looking at seeing what is actually in an android frimware. For example using this image
https://dl.google.com/dl/android/aosp/shamu-lmy48m-factory-336efdae.tgz
I can unzip it to the point where I get a few .img files. Doing some reading online I see a tool called binwalk to extract these, but when binwalking system.img I get an output of hundreds of GB which seems very wrong. I get the feeling that I've misunderstood something and hence this post. Can someone point me in the right direction?
Im still expirmenting with different ways of possibly, hopefully, someday over the rainbow, getting my S7 successfully downgraded. Ive taken so much time waiting for things to copy and paste, and convert, and made a custom firmware hours later, only for odin to either freeze or straight up shut down after reaching file analysis... so im exploring other ways. im not sure if its a good idea to flash only parts of the firmware? like just the AP files?
I wish samsung would allow us to say "I dont care if my phone isnt as secure" and then their butts are covered cuz we consented and we can still downgrade the bootloader and android version as desired.
i cant find any information on how to make a disk image into an lz4 file (as in oreo) since that one system file from the marshmallow stock is simply a disk image, so i went about it the other way and removed the lz4 from all of the oreo files, making them all either plain .bin or plain .img files except leaving the pit file and the meta data folder alone, and then repackaged them back into the same categorized tar.md5 files. odin checks them as legit, but just wont actually *DO* anything with them... so i got looking into my old s5 neo rom and saw that it was a 1 file version and wondered.... maybe i can make a 1 file version with a combination of the files i need/want, all into one custom tar.md5 and then maybe *that* will at least attempt a flash..... has anyone else tried this? or has already been thought about and failed?.... I only want that oreo rom with the marshmallow system image... is it really so impossible??
So glad I have an Appsung device... theyre locking their stuff down just as hardcore so... why not merge the names. Sampple is another option. heh.