First off I want to thank these Dev. for there hard work.
Kam187, Mastermind278, droiddev, mobileband, My420Time, rkhalil2009, Nu11u5
Don't extract the file(s) from the tar that you download, the file that you download is what you need. Load Into the PDA setting in ODIN Flasher!
View 49 Replies
I am looking to see if anyone (BH_MAN... ) has Alpha Recovery from the last BH_MAN ROMS dumped into an odin ready image. I am trying to get A2SD to work on the OTA, and I would like to be able to partition the SD card directly from the phone, which Alpha Recovery does...
View 2 Replies View RelatedHere is a brief much more complete guide to creating your own Odin images for distributing custom ROMs or making backups. Thanks to kam197, BH_MAN, chadmd23, SoulCreator, and all the other community members.
Requirements:
A Samsung Behold 2 to backup/edit/test ROMs on
Root via try3/asroot2, persistent su, or modified kernel
Working ADB connection
SD Card with ~300MB free
Cygwin - if you are working in Windows
Basic knowledge of a command line
Making the ROM Dump: The Behold 2 has 14 partitions in its flash memory, but only a few of these are useful to modify. You will want to focus on different partitions depending on what you want to do. After you make a ROM dump you will need to package it using the instructions in the following section before you can flash it. Backup your personal data? You may want to backup your data while trying out a different ROM. It is simple to do. Start an ADB shell session and obtain root access. Run the following command to dump the UserData partition: Code:
Any thoughts to when we might see overclocking? How much over clocking can this phone safely have? I know it has to do with a custom kernel but what is the holds back of making it custom?
View 2 Replies View Relatedi cannot see here where to download odin?
View 1 Replies View RelatedFrom Where Can Download Odin?
View 3 Replies View RelatedIm new to Behold. I want to flash the 1.6 r7. I was wonder is there an backup utility I can use to save my current rom before odin so I can always revert back if need be.
View 2 Replies View Relatedin odin i got everything running fine then i power off my phone and enter download mode and then i press start in odin and it tells me to plugin phones!! so how do i plugin in my phone if it is already connected via usb? it even shows my device is plugged in when i first enter download mode but odin keeps saying plugin phone.
View 3 Replies View Related1. Open up Odin Multi Download
2. Under Select OPS, choose Behold2_partition.ops
3. Click PDA, choose the PDA File you are Trying to Flash Rather it Be BH_MAN Rom / or Stock
4. Power Off Phone
5. Make sure you have it connected via USB
6. Hold and Press Volume Down, OK, Power (the red end button)
7. Phone will say Download Mode
8. Click Start on Odin Multi Downloader.
9. Wait a couple of minutes
10. Stock Touchwiz phone working again!
After countless calls to t-mobile I have *FINALLY* received my update, which means now that I've got the updated kernel I'm ready to upgrade to BH_MAN's rom... But of course if something goes wrong I'd hate to ODIN back to a buggy system. So my question is this: can anyone instruct me on the process of creating a new ODIN file on a system with the updates? Because unless the process is way over my head I'd really love to give it a shot.
View 7 Replies View Relatedi got the drivers working and adb recognises it. now odin wont recognize the phone!!! do i have to put in download mode?
View 8 Replies View Relatedi'm about to do the odin 1.6 update and i've never done anything like this on a phone before. my question is, will all my contacts and pictures and such still be on the phone after i do the update or will i have to back them all up someway ( pics to computer, contacts to sim or paper)?
View 2 Replies View RelatedOEM 1.6 Packages are uploaded now.Odin files for the 1.6 OEM update are now available! All necessary files and instructions are included in the download.To use the update you will need a Windows PC, USB cable, your Behold II, and about 5 minutes.Some users are reporting that after the update the phone will temporarily be stuck in a boot loop. This seems to happen when the user has previously installed certain custom ROMs such as Take5 and Galaxy R12.The work-around requires a complete factory wipe of the phone, meaning you will lose all of your data and apps not on the SD card.
View 49 Replies View RelatedI just got my Behold II with android 1.6 on it.
I don't understand what is root the phone , flash the phone using ODIN to save battery .
Also my phone rightnow when I check the battery information , it said " Android system 88% of battery" " Phone Standon 6% " , Is this because the new Android 1.6 making my battery drainning so fast because rightnow I am using with a little of playing around , WIFI , and then I turn off the WIFI again , the battery still didn't last for at least 24 hours . I didn't making too much calling also .
Made these earlier in Photoshop. Go ahead and use them if you'd like. I'll be updating this thread with all sorts of different wallpapers. You are more than welcome to request any certain kind of wallpaper.
View 3 Replies View Relatedwhat would happen if i flashed the galaxy kernel on my behold 2? or any other kernel for that matter... i am sort of new to this but i know alot of things too. so is this possible?
View 3 Replies View RelatedI decided to split this off to a new thread, and hope some coders will join in and start compiling a kernel. We could then merge this with the galaxy asop effort.
Here's a bit more technical information.
Galaxy
The galaxy flash files are just yaffs images and a zimage (and of course AMSS) all tarred up. The tar format needs to be oldgnu for odin to accept it.
There's no protection at all. Thats because the glaxy is released completly security unlocked (simlocks are different, not the same thing). You can flash any image you like.
AMSS - arm ELF binary for baseband
kernel - zimage
system - standard yaffs image
recovery - standard recovery format
tar - oldgnu style standard tar file
The Galaxy also has a mtd device driver which means you can read/write its partitions with dd.
/dev/mtd
Behold 2
The behold has the same image format, yaffs, zimage and AMSS. See below for specific differences per image:
AMSS - arm ELF binary for baseband
The behold 2 also contains a partitions file. This is most likely for the AMSS, and allows the layout of the baseband to change. I'm not sure if the galaxy supports the same, but probably does.
Its safe to say you should NOT try to flash an AMSS from galaxy to the behold or vice versa.
Since the radios have the same functionality, and we don't know how to recompile and AMSS, you should never flash any new AMSS with a custom rom. Only flash AMSS with official updates.
> kernel - zimage
Just like the Galaxy this is a standard zimage. There's nothing special about it and you can modify it however you want. BUT in order for it to flash the tar file needs a special header (see tar below)
Since we can change the kernel, upgrades to newer OS versions is now possible.
> System - standard yaffs image
It appears the system image format on the behold2 is DIFFERENT to that on the galaxy. If you flash a galaxy system file onto the behold 2 you will most likely end up with a brick.
I suspect the behold 2 file has the flash address embedded inside it. Flashing the galaxy system file writes to a bad address killing the bootloader. When i say BRICK i really mean BRICK. No life in the phone at all, it wont even charge. so DONT DO IT!
In order to write a custom system to the behold 2, we will need to untar or unyaffs the modified system from the sdcard on first boot. This can easily be accomodated in the init.rc of you're modified zimage.
> Recovery - standard recovery format (protected?)
The recovery image format seems to be the same - standard android format with a ramdisk, kernel etc. However flashing it using odin doesnt work. There is some sort of protection which is preventing the image being flashed. I havnt looked thoroughly at this and someone really should. I suspect either it is signed (unlikely since the other images dont seem to be protected), or there is a write address embedded in the file, like the system file.
It would be nice to be able to flash a custom recovery, or even boot from a ramdisk, but I think this wont be simple.
> tar - oldgnu style standard tar file (with header)
Both the galaxy and behold2 have a header at the top of tar. The galaxy will flash regardless of if this header is intact or not. The behold 2 however MUST have this header intact for it to flash anything.
It seems this header contains the size, and write address of the zimage. Its possible the addresses of other images like the recovery are embedded in this too. We should look more closely at this header, especially between firmware versions to see what changes. In the mean time to replace the zimage, just hexedit your new image over the existing 'kernel' file in the tar. Remember you need to keep the size the same, so pad with zero's or just leave the remainder of the old kernel in the extra space.
Progress?
The sources that samsung provided are missing patches. This means you can't compile the behold kernel simply.
Also because the partitions are different, and the memory layout is different (compare msm/board-init files) a standard galaxy kernel will not boot.
Making the changes to get it to boot are not that dificult. It would be nice if someone who actually has a behold 2 and linux knowledge could have a look at this. It takes far to long for me to do this remotly, and frankly I just dont have that much time.
All you need to do is:
- compile the galaxy kernel (test your environment)
- replace board-init in the galaxy source with that from behold2 sources
- turn on linux console
Now boot and check if the galaxy kernel is able to see device's for each partition on the behold. If not you'll need to copy the disk/flash driver from the behold 2 sources.
Once you are able to get that far, you can merge the changes into the i7500 asop project and add a kernel switch for the behold 2. Now all galaxy 2.x progress will be directly transferable to the behold2.
You will need to make a change to the init.rc to mount the drives and unyaffs the modified system.img the first time it boots. Again a simple change.
Forgot to mention HOW to flash a kernel.
1) Take the stock behold 2 PDA tar file.
2) Use jzip (must be jzip on windows, winzip etc wont work) to remove ALL files except the kernel.
3) Extract the kernel file for reference (leave it in the tar too)
3) Download HexWorkshop or similar Hex utility.
4) Use Hex Workshop compare function to compare 'kernel' and the tar. It will highlight the kernel in the tar file
5) Open new kernel in Hexworkshop. Select all and Copy
6) Highlight the same number of bytes in the tar file and paste over the original kernel
7) Flash with Odin (JUST this tar) as PDA, and of course selecting the behold ops file.
So when updating my phone, I was all like 'I know how this show goes' and like an IDIOT I put my Samsung S2 i9100 kernel file on the bootloader spot and it boots to a black screen. I can still put it in download mode, and tried to install it the correct way but that doesn't matter.
View 4 Replies View Related[Kernel - DE03] joeykrim-SDX - v0.5 - May 19th 2010
Joey had it out 5-6 hours after source was released this contains Numus' battery code and more.
when i try and download odin downloader it is saved and when i go to open it it says that "windows can not open this file" then it gives 2 options of use web service to find correct program and select a program from a list of installed programs. The file is downloaded as a .rar file if it matters. This also happens when i try to download the newest kernel.
View 5 Replies View RelatedWe can now do partial flashes with the CL14 SBL.... If you have not had the CL14 official update yet, you can follow these steps to get it:
Remember... THIS WILL PUT THE CL14 BOOTLOADER ON YOUR PHONE!
What you need:
Sprints Update Utility
1. Create a datatool back-up.
2. Download and install Sprints Update Utility found above.
3. Run the program (now called SWUpdater) and follow all the directions until it says "Flash Downloading Complete".
Once you have the official CL14 update on your phone, or if you already had it, and you would like to flash SDX/Joey's Kernel (and Max's Recovery), follow the steps below.
What you need:
CL14 official update
An SDX/Joey's Kernel
Max's Recovery
1. Create a datatool back-up... (Although you most likely wont need it if you are just flashing a kernel.... But JUST in case, you should create a datatool back-up if you aren't confident that you wont wipe your data!)
2. After downloading and installing Sprints Update Utility, go into the binary folder (C:Program FilesSamsung ElectronicsSWUpgradeModelsBinary) and move the CL14 file to a safe place, MAKE SURE IT IS NO LONGER IN THE BINARY FOLDER.
3. Find the Kernel you want to flash and put it in the binary folder.
Note: Now you should only have one file in the binary folder (the custom kernel). Also make sure that if the file you are putting into the binary folder says 7zip or winrar, extract it!! If you dont you will get the message "Cannot access bin folder!", and you will not be able to start the download.
4. On your desktop there should be a program named SWUpgrade. Run the program and follow all of the steps through the end. After every thing finishes successfully, you will end up with STOCK CL14, this includes the CL14 SBL, along with the custom kernel you put in the binary folder (you are root).
5. Double check that everything worked by going into Settings-About Phone, under BaseBand version you should see S:M900.8.0S.CL14, under Kernel version= 2.6.27 moment(at)momentdev, under Build number= Joey's name (or any other developer who's kernel you put in the binary folder).
6. Repeat steps 1-4, putting Max's recovery in the binary folder instead of the kernel.
7. You're all set.
(If you happen to want to flash one of Zefie's kernels, repeat steps 1-4 also.)
It wasn't a great thing to get the CL14 update before, because it was hard to obtain root. But now with Sprints Update Utility, and all the new kernels, we are able to get root with the CL14 SBL easily.
Don't know if anyone over here cares, but zefie over on SamsungMomentForum.com released a custom kernel with a bunch of fixes. Including a partial audio buffer fix, and a bunch of tweaks and optimizations. Also, persistent root so you can run a bunch of those programs on the market that require it. No WiFi tethering yet, but it is being worked on. Not sure if this includes the battery notification fix because I had already installed CL14 the other day and it's been working for me ever since. This was not difficult to install, once you have the software and drivers required, the update takes less than 30 seconds.
Here's a link:
Time for the first custom "ROM" (well kernel)
Does anyone know if there's a away to add a custom sound to the app drawer when it's opened. I have an old Apple Newton that I've recorded some of the default sounds off of and one of them is the Newtons app drawer opening and closing. It's pretty cool! I use to use my Newton for everything!! I'd like to customize my Beholds app drawer.
View 16 Replies View RelatedI'm using Bearsfan85's custom ROM, but have lost the voice dialer app that was in the Samsung's touch wiz ROM. As this is helpful to avoid car accidents while on the road, I was hoping to get it back. I have the .apk file but ASTRO file manager won't let me install it. I've tried to adb push it but I get a "read-only file error". For whatever reason, the commands "adb remount" or "adb shell sysrw" aren't being recognized, which I think is what I need to do to adb push the voice dialer back onto my phone.Unless of course, the Samsung apps just aren't compatible anymore.
View 16 Replies View RelatedI encountered "zero memory" issue if I flash custom ROM over another with "onepackage" and factory reset doesn't help. Now I found a fix of this issue, and this should be done if you want to flash custom ROM over another.
Download and flash BH-MAN Warheads ROM http://www.4shared.com/file/nFe93F45/BH_MAN_WarHeads.html
Make sure you put in the components correctly. After md5 check has completed, you can flash and take a little break. Once you're in the standby screen on the phone, you can turn it off and reset the Odin and select the ROM and .ops file along with the ROM.
How do i set my own ringtone, there is only a option to select the pre-installed ringtones, but i want to set my own.
View 2 Replies View RelatedI have samsung galaxy pocket duos gt s5302..I have rooted it and flashed CWM recovery then I tried to flash custom compact kernel made by Deadly. After I flashed through CWM my phone got hard bricked It wont turn on What should I do?
View 6 Replies View RelatedI have a couple of ideas for theming but have no idea on how to actually go about making them for the phone.
View 14 Replies View RelatedI know how difficult and confusing It can be to root your phone, or put a custom ROM. If you need help, I will be more than willing to answer your questions.
View 20 Replies View RelatedI am trying to create a custom boot animation and I have been following this tutorial ([Ref Tutorial] Changing the boot animation screen on google builds - xda-developers) but I can seem to be able to find the system folder. I am using take5 ROM but when I unzip it its md5 file, not a bunch of folder like the tutorial says.
View 8 Replies View Related