SBF and 3G bands - Defy General

I don't own a Defy but I do own a Milestone. It looks like, from all the chatter I've read, there is still no T-Mo US firmware SBF yet. Some Americans seem to have become trapped with a foreign firmware on their handset which does not support American 3G bands.
In Milestone-land we have all the SBFs we need, but we also found a workaround to enable proper 3G on devices mis-flashed with ROMs that were meant for Euro frequencies. Maybe you guys can tell me if the Defy is similarly designed.
On the Milestone, the folder /etc/motorola/bp_nvm_default contains a number of files including these:
File_Audio
File_Audio2
File_GSM
File_Seem_Flex_Tables
generic_pds_init
If you back up these files from your original ROM (e.g. using Root Explorer), and then restore them on the new ROM after rooting, and reboot, the correct 3G behaviour returns to the Milestone.
Does this folder exist on the Defy? Do these files exist? If so, maybe one of you on the stock T-Mo US ROM could back up this whole folder to a ZIP file; then see if the folks stuck on Euro ROMs are able to use this to fix their 3G.

cmstlist said:
Does this folder exist on the Defy? Do these files exist? If so, maybe one of you on the stock T-Mo US ROM could back up this whole folder to a ZIP file; then see if the folks stuck on Euro ROMs are able to use this to fix their 3G.
Click to expand...
Click to collapse
folder exist, I have this files on my defy (Europe/CH):
File_GPRS
File_Seem_Flex_Tables
File_Audio
File_Audio6
File_Audio8
File_Logger
File_Audio4
File_Audio5_AMR_WB
File_Audio5
File_Audio7
File_Audio3
File_UMA
File_Audio2_AMR_WB
File_Audio2
File_Audio4_AMR_WB
File_Audio1_AMR_WB
File_Audio3_AMR_WB
File_GSM

Well isn't that interesting... there's a file related to UMA (wi-fi calling) even on your European Defy.
So anyway - great! - now if a T-Mo US Defy user can post a .zip of these files backed up from their stock ROM, then it would be of great value to anyone stuck with the wrong SBF on their US Defy. I don't know if it's harmful to replace more than just the 5 filenames listed above. Or for that matter I don't know if replacing any of them is harmful, so please back up whatever you are replacing as well

Confirmed, this works. See simply-android or Modmymobile for threads on this.

Related

Flashing How To

http://forum.ppcgeeks.com/showthread.php?t=17473
well im changing this because of a request that a lot of people supposedly dont know how to flash. but i dont think that the link was doing anyone much good. so here is what is at the link (right now at least).
THIS IS ONLY FOR THE HTC CDMA TOUCH (VOGUE) !!
i know this first post here is now real long, but READ IT ALL before posting/pm'ing anyone. trust me, you will get through it all...every last word.
(dont get all scared either, this cant ruin your phone. if you are stuck at the htc boot screen, your device is not bricked. if you are stuck at a rainbow/tricolor screen, your phone is not bricked. have faith and patience! )
this method is for a pc running Microsoft Windows XP. if this is not your situation, still continue reading as there are methods for virtually every case.
ive been told that imcokeman's vogue unlocker will not work from a partitioned drive, though im not sure if thats the case.
if you know what flashing/the benefits of flashing are, skip this paragraph; if not, read on. flashing could be likened to installing a different Operating System on your PC. keep in mind, however, that when flashing roms to phones/pdas, the roms ARE DEVICE SPECIFIC. if you find an awesome rom for the titan and LOVE it, but you yourself have a kaiser, forget it. only roms made specifically for your device (and no, even if you have a cdma device, and they make a gsm version of your device, it still will not work) will work for your device. the benefits/advantages of flashing a custom rom onto your device are speed enhancements, addition/removal of programs/settings/reg settings you want or dont want.
now for how to..
for some slight insight on using a Mac, have a look down to the bottom where it says "HERE IS THE BOTTOM" after reading everything else, and/or go here: http://forum.xda-developers.com/show...ighlight=macos
for how to on Vista: look down to the bottom where it says "HERE IS THE BOTTOM" after reading everything else, and/or simply remove any sd cards you might have and follow below directions as normal, and/or go here: http://forum.xda-developers.com/showthread.php?t=292631
linux users: still read everything here, but have a look down at the bottom where it says "HERE IS THE BOTTOM"
for those who don't know this, flashing your phone also performs the same functions a hard reset would. all your previous apps, contacts, registry tweaks, etc will be gone. also, when you flash someone elses custom rom onto your device, keep in mind that they may have cooked in their own apps and registry tweaks.
ok, go ahead and go to this http://rapidshare.com/files/88767429/RUU.zip.html rapidshare link, and download the ruu.zip there. (if this does not work, navigate to \vogue\users on the ftp, and you should find "RUU.zip" there. if not, go to the folder there titled "jim256-jim2561" and you should find "RUU.zip" there.)
if for some reason you are unable to download the ruu from the above link/location, try my ftp dir here: ftp://up.ppcgeeks.com/Vogue/Users/jim256 - jim2561
download whatever rom image you want
if the rom you download is in nbh format (something.nbh), read on and skip step 7.
if the rom you dowloaded is an exe (something.exe), read on and skip steps 5 and 8 (or use winrar or a similar program to extract the .nbh from the .exe)
then, get imcokeman 's latest vogue unlocker tool.
for those who arent sure, you never have to have ActiveSync synchronized for this to work. you just have to have it connected, with ActiveSync recognizing that the device is there and plugged in.
1. backup all contacts/data/etc..
2. ensure your device is connected to your pc via activesync.
3. run imcokeman 's vogue unlocker and follow ALL instructions in the command prompt exactly .
4. once you have booted back up into wm and are connected to activesync again (dont worry about setting up your device again because you're just going to flash it again and erase all that in a second anyway) extract the ruu.zip to somewhere convenient.
5. (FOLLOW THIS STEP ONLY IF THE ROM YOU DOWNLOADED IS AND NBH) stick the rom you downloaded (should be something.nbh -- if the file extension is NOT NBH, stop; this will get you nowhere. as i stated above, roms are device specific, you cannot install another devices rom to your vogue.) into the RUU folder from the rapidshare/ftp link.
6a. (power-camera reset) press and hold both the camera button and the power button (top), and poke the stylus into the reset hole. you should then be presented with the tricolor screen and near the top you should see something like coke 0.4.0 ( if you do not see the coke 0.4.0, then dont bother trying to flash your device. if it does not say coke 0.4.0, the device is not unlocked, and you need to start at step 3 again).
7. (FOLLOW THIS STEP ONLY IF YHE ROM YOU DOWNLOADED IS AN EXECUTABLE). run the exe!
8. (FOLLOW THIS STEP ONLY IF THE ROM YOU DOWNLOADED IS AN NBH) run ROMUpdateUtility.exe in the ruu folder you downloaded and extracted.
9. follow the steps, be patient, be careful, and whala!
10. thank imcokeman and whoever you downloaded your rom image from.
good luck.
also, for all those that keep asking about this and are worried about this, yes, the version discrepancy is completely normal in the ruu before updating. it just means v1 of the cookers rom, so even if it is a version lower than 1.12.651.1, that is ok.
whenever you flash a custom rom, it says whatever they want it so say in the ruu, so even if it doesnt say 1.12.651.1, that doesnt mean that it is downgraded, it is just the version of the custom rom builders rom.
HERE IS THE BOTTOM
ok, for those vista/mac/linux users, there is another method of flashing., courtesy of pnyce777 in post #42 and on. this method is via the sd card. it is not required that you do step one if your card is already fat32. i will update this post as we gain more knowledge
1. Format your MicroSD card to FAT32 (YES - FAT 32 32 32!! not just plain old FAT) (again, this is not required if your card is already fat32; it is ok to have other data on the card). I have read that the card needs to be 2gb or smaller, though I'm not sure how much truth, if any, there is to that...
2. Extract the .NBH you desire to flash from the exe or zip or w/e put it on the microsd card rename it from RUU_signed.nbh to VOGUIMG.NBH
3.Put the MicroSD card in your phone and Get To the BOOTLOADER screen (camer+power+reset) it should then start updating with the .NBH on the SD card and the procedure should begin automatically.
you can also use this procedure to unlock your phone by flashing the .nbh from Cokemans unlocker just extract it and rename it VOGUIMG.NBH or if your stuck at that HTC screen and cant sync because your phone wont boot up.
i will try to provide support on this as i can, but as i have never used this method myself, pnyce777 is probably a far better resource if he is available and willing.
sorry this is now so long, wasnt supposed to be in the first place. but if you're not already used to a lot of reading, this is a good first step, because you will need to be doing a LOT of reading.
----------------------------------
If I've helped you out, $1 would be more than appreciated! donate. thanks
bump for same reason as above.
thanks for the gudie dude
Jim, great how to. As a noob, I have a qstn about different carriers. I just got a VZ touch and want to know which roms are best to use with which carrier? Some roms seem carrier specific... others seem like they will work on anything. How do you tell whats wat? I have been waiting for someone to post a ROM specifically for VZW, but I haven't found it yet.
It might also be helpful to add a glossary. Like I have read how some folks have taken a sprint kitchen moved it to a new directory (?) and merged it to make a verizon kitchen. With that people have flashed their VZ phones but it doesn't seem like something a noob should try
PapaDocta said:
thanks for the gudie dude
Click to expand...
Click to collapse
no problem
insol said:
Jim, great how to. As a noob, I have a qstn about different carriers. I just got a VZ touch and want to know which roms are best to use with which carrier? Some roms seem carrier specific... others seem like they will work on anything. How do you tell whats wat? I have been waiting for someone to post a ROM specifically for VZW, but I haven't found it yet.
It might also be helpful to add a glossary. Like I have read how some folks have taken a sprint kitchen moved it to a new directory (?) and merged it to make a verizon kitchen. With that people have flashed their VZ phones but it doesn't seem like something a noob should try
Click to expand...
Click to collapse
ok. so as for different roms saying they are for different carriers, they are most likely just referring to having the different directories (/folders) for the carriers. so what that means is that a sprint rom would actually work just fine for you, but it may have things like sprint tv or on demand on the cube or other places. it will still function just fine and everything though. it would probably look a little different than the stock vzw rom (im not sure really how it looks) and such. the only way that you could get screwed having the wrong rom for your carrier is if you were flashing the radio as well. but since you're not (in most cases), it doesnt matter really. just be sure to check the roms threads about whether they include a radio or not.
as for the glossary thing, that is probably a great idea. thanks for the tip i will get working on that.
so what you will need to do is:
1) download a kitchen: set of tools for creating/editing roms. dcd just finished his vogue kitchen; available here on xda in this vogue upgrading subforum. there is also lattisimo's older vogue kitchen available on the ftp site over at ppc geeks ("qlinks" at top of page, ftp upload/download, vogue -> users -> lattisimo? (i think?)).
2) download a verizon titan/mogul/ppc 6800 kitchen from somewhere, look in the "sys" folder contained therein, and copy the "carrier vzw" or "verizon" or "carrier customizations - verizon" folder (it will be something like that) into the "sys" folder of the vogue kitchen you have downloaded.
3) delete whichever other carrier customization was already in that folder (such as alltell or sprint or bell etc..)
4) run "buldit.bat" or "buildnb.bat" (or something similar) and flash your new rom that will be located in the "ruu" folder after the batch file (xxx.bat) is finished!
feel free to ask any more questions if that wasnt too clear (sorry :S) .
good luck!
jim256 said:
ok. so as for different roms saying they are for different carriers, they are most likely just referring to having the different directories (/folders) for the carriers. so what that means is that a sprint rom would actually work just fine for you, but it may have things like sprint tv or on demand on the cube or other places. it will still function just fine and everything though. it would probably look a little different than the stock vzw rom (im not sure really how it looks) and such. the only way that you could get screwed having the wrong rom for your carrier is if you were flashing the radio as well. but since you're not (in most cases), it doesnt matter really. just be sure to check the roms threads about whether they include a radio or not.
so what you will need to do [for verizon] is:
1) download a kitchen: set of tools for creating/editing roms. dcd just finished his vogue kitchen; available here on xda in this vogue upgrading subforum. there is also lattisimo's older vogue kitchen available on the ftp site over at ppc geeks ("qlinks" at top of page, ftp upload/download, vogue -> users -> lattisimo? (i think?)).
2) download a verizon titan/mogul/ppc 6800 kitchen from somewhere, look in the "sys" folder contained therein, and copy the "carrier vzw" or "verizon" or "carrier customizations - verizon" folder (it will be something like that) into the "sys" folder of the vogue kitchen you have downloaded.
3) delete whichever other carrier customization was already in that folder (such as alltell or sprint or bell etc..)
4) run "buldit.bat" or "buildnb.bat" (or something similar) and flash your new rom that will be located in the "ruu" folder after the batch file (xxx.bat) is finished!
feel free to ask any more questions if that wasnt too clear (sorry :S) .
good luck!
Click to expand...
Click to collapse
This is great! I will also post it over on PPCgeeks. Huge help for me to get started and hits right at the real bricking fear... if the radio is not in the user-made custom ROM it seems safe... and avoid OEM carrier ROM unless it is for your carrier.
insol said:
This is great! I will also post it over on PPCgeeks. Huge help for me to get started and hits right at the real bricking fear... if the radio is not in the user-made custom ROM it seems safe... and avoid OEM carrier ROM unless it is for your carrier.
Click to expand...
Click to collapse
yep exactly good deal
Thank you for the great guide. flashed my rom for the first(and probably not the last) time last night.
i have a sprint vogue and want to use it for verizon, can someone make me a rom that i can just flash and have it working for verizon? if so thanks, if not can you please tell me what i need to do, thanks!
this should be a sticky!
well it is over at ppcgeeks...
but this isnt the most updated copy though..
thx tho, glad it could help ya
Makavelifaison said:
i have a sprint vogue and want to use it for verizon, can someone make me a rom that i can just flash and have it working for verizon? if so thanks, if not can you please tell me what i need to do, thanks!
Click to expand...
Click to collapse
you will need to exchange that cdma vogue for a gsm model that will work on verizon.
aecabanaboy said:
you will need to exchange that cdma vogue for a gsm model that will work on verizon.
Click to expand...
Click to collapse
Sprint and Verizon are both CDMA.
Makavelifaison said:
i have a sprint vogue and want to use it for verizon, can someone make me a rom that i can just flash and have it working for verizon? if so thanks, if not can you please tell me what i need to do, thanks!
Click to expand...
Click to collapse
You can't just "make" a ROM for a different carrier. The phone itself won't work because it's registered for one comapny.
Great Thread!
Good to see there are some thorough instructions out there for noobs... Howabout an unlocker for Vista 64??? Any advice? Thanks.

Tutorial for BEFORE ugrading from WM5 to WM6.

Yes, we're all noobs!!!
I have a brand new Excalibur (I bricked my first one five mins. out of the box) and I attempt to upgrade following instructions on the tutorial posted on these forums.
What's not stated on said tutorial (and no one tells you, only after you bricked your phone) is that YOU MUST BACK UP YOUR ORIGINAL ROM before the upgrade, because if anything goes wrong, that is the only ROM you can flash to your phone to restore it, otherwise IT IS BRICKED. (Believe me, it happened to me).
So, to all you experts reading these, please, help us noobs and post here a complete guide on how to back up your original ROM.
We will thank and worship you forever!!!
These days, there is no need to backup your own Rom.
We have a collection of ROMs on this site alone. Or in my signature.
I do suggest to download one prior to updating your ROM.
This forum uses most of a collection of ROM i have uploaded for everyone.
Click here for the forum of original ROMS
Mikey1022 said:
These days, there is no need to backup your own Rom.
We have a collection of ROMs on this site alone. Or in my signature.
I do suggest to download one prior to updating your ROM.
This forum uses most of a collection of ROM i have uploaded for everyone.
Click here for the forum of original ROMS
Click to expand...
Click to collapse
I have two questions: Firstly, there is no official O2 Xda Cosmo ROM or? Secondly, if you back up the ROM first, how can you flash it back to the device? Is there a tutorial for this?
Thanks
READ this thread
uccellino said:
I have two questions: Firstly, there is no official O2 Xda Cosmo ROM or? Secondly, if you back up the ROM first, how can you flash it back to the device? Is there a tutorial for this?
Thanks
Click to expand...
Click to collapse
yeah i'm waiting for the official O2 Xda cosmo ROM. i need it badly because my camera doesn't work anymore with new ROM. and i am totally agree to write a clear reminder to backup your original ROM first before upgrading in the upgrading ROM thread. just in case for noob like me....
Mikey1022 said:
READ this thread
Click to expand...
Click to collapse
After rereading, I still have the questions:
1. How is it possible to flash back a saved backup ROM image?
2. If I use a USPL and then something goes wrong while flashing a cooked ROM, can I only re-flash my original ROM (i.e. for XDA Cosmo which doesn't exist)?
Thanks
Okay - maybe I just figured out the answer to my own question: if I flash the USPL-RUU first before flashing a ROM update, maybe this means I can reflash if something goes wrong? Is this correct, or is there a chance that the SPL get overwritten before the error and I still get stuck?
Well, in fact, it is necessary...
Mikey1022 said:
These days, there is no need to backup your own Rom.
We have a collection of ROMs on this site alone. Or in my signature.
I do suggest to download one prior to updating your ROM.
This forum uses most of a collection of ROM i have uploaded for everyone.
Click here for the forum of original ROMS
Click to expand...
Click to collapse
...When I mean original ROM, I mean the ROM that could only work on a CID-Locked-by-a-carrier Excalibur, not the HTC WW ROM release.
Also, many of us noobs are international, I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
velascoperroni said:
...When I mean original ROM, I mean the ROM that could only work on a CID-Locked-by-a-carrier Excalibur, not the HTC WW ROM release.
Also, many of us noobs are international, I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
Click to expand...
Click to collapse
Actually, it's quite easy to CID unlock your phone to load whatever ROM you want. Much easier in fact, than dumping your current ROM and restoring it. I was able to flash my first ROM within about 30 minutes of reading on this forum, and had no problems at all.
velascoperroni said:
...When I mean original ROM, I mean the ROM that could only work on a CID-Locked-by-a-carrier Excalibur, not the HTC WW ROM release.
Also, many of us noobs are international, I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
Click to expand...
Click to collapse
I completely agree with you
I just have no idea how to restore a backed-up ROM and I haven't read anything saying how to do it either. As you say, many of us a stuck with devices CID locked to some international ROM that is impossible to get.
So once again the question: Does anyone know how to re-flash a backed-up ROM?
I'm no expert but all I'm going to say is this. If you have a Rom from a different carrier that has not leaked to the public, then you are probably out of luck. You take the risk of hoping your phone will not have serious problems down the line of your contract or usage. You should pick up insurance on your phone depending on the stipulations your carrier has about lost or stolen or even broken phones. In that case you could return/replace your phone if need be after modifying it to your liking. I also would suggest that the entire reason we are here is that we don't want to be like the norm. We want what we paid for and don't want to be restricted. It's a risk. You must make that choice and succeed or fail that's not anyone's problem but your own. With all the Roms out there you should find one to your liking. If you brick your phone which seems so much more difficult than my razr modding days, than sell it for parts and lesson learned.
In the U.S. the Open Headset Alliance is our future so what we do to our phones in the future will be our choice.
Good Modding
Pfunk
C'mon guys...
Wy all the negativity?
I'm I conspiring against copyright laws if I want to have a backup of the ROM I paid for?
Is backing up a ROM frowned upon on this community? or is it so easy (from what I can gather it requires "dumping" and "restoring") that it is even insulting for me to ask you how to do it?
Yes, we are all here because we don't conform to the norm, but we are all HERE to help each other out. Why the closure? Why the elitism?
Like all of you, I want to take full advantage of the piece of technology I acquired without the restrictions installed on them by the phone corps. Yes, I would like to have the minimum risks while doing so, and yes, I would like to do it as cost effective as I can, just as anyone of you would.
It is a risk to upgrade a Cid.Locked phone with the bypass provided on this website, It happened to me and to many: USB cord unplugs and voila, bricked phone.
One alternative is to pay $40 bucks for a permanent Cid.Unlock, which will allow you to flash and flash and flash, even if you get stuck in the middle of one process.
The other, used by many here who wont pay, is to use the Cid bypass, while having a backup original rom "just in case".
What I only ask (for myself and my peer noobs) is to have this same other alternative as many, many of you.
Really, is it to hard to post the following?
1. Downoad these softwares;
2. Do this to "dump";
3. Do that to "restore";
4. To re-flash, do this.
C'mon, all for one and one for all right?
p.s. For my friend asking how to re-flash a backed up ROM, from what I've gathered, it goes something like this: your backed up ROM must be in a *.bn format (I still don't know how to even achieve this); then you must get a hold of any HTC RUU Software, extract it (Winrar) and replace the *.bn file inside the extracted folder with your *.bn file; with the HTC connected in bootloader mode, run the exe file in the extracted folder.
velascoperroni said:
...I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
Click to expand...
Click to collapse
The Official ROMs collection is as full as I can make it. To have more images, we need everyone to upload ones that are missing to something like rapidshare, mediafire, or one of a few dozen other hosting sites, then tell up here on xda dev. Or upload it to several yourself. Spreading things on the net is much easier than ripping the ROM out anyway, and you benefit from the online backups, too.
So, yes, if you aren't going to back up your ROM, hope that someone else already has. Or, even better, be that first guy who does it, to make things easier for the rest of us. Besides, we might want to see what kinda goodies are tucked in the Movistar version
Indeed!
Profezza said:
...Or, even better, be that first guy who does it, to make things easier for the rest of us. Besides, we might want to see what kinda goodies are tucked in the Movistar version
Click to expand...
Click to collapse
Thanks for the support Profezza, indeed I intend to be the first, but in order to do that, I need to know how to do it.
I'll keep my hopes up for someone to post here the procedure for backing up my own ROM.
Also, the Movistar version is pretty lame, at least it would be a language addition to the database since it is originally in Spanish.
velascoperroni said:
Thanks for the support Profezza, indeed I intend to be the first, but in order to do that, I need to know how to do it.
I'll keep my hopes up for someone to post here the procedure for backing up my own ROM.
Click to expand...
Click to collapse
My post kinda ignored that point, as... I don't actually know how it is done.
velascoperroni said:
Also, the Movistar version is pretty lame, at least it would be a language addition to the database since it is originally in Spanish.
Click to expand...
Click to collapse
I think the version # system is controlled by HTC and fairly consistent across brandings, so it looks like it is a rather old one, but yeah, it could handy just for the Spanish. And ya never know, maybe a better graphic or two in some odd corner. I'll come back and bump this if it looks like it is fading away.
velascoperroni said:
p.s. For my friend asking how to re-flash a backed up ROM, from what I've gathered, it goes something like this: your backed up ROM must be in a *.bn format (I still don't know how to even achieve this); then you must get a hold of any HTC RUU Software, extract it (Winrar) and replace the *.bn file inside the extracted folder with your *.bn file; with the HTC connected in bootloader mode, run the exe file in the extracted folder.
Click to expand...
Click to collapse
Hi velascoperroni!
Thank you for your help - this is helping me to get closer to understanding
Basically I have my old ROM image as .img files (actually 5 of them) produced by bkondisk, together with a log file saying what goes where. So now all we need to figure out is how to turn these back into a .bn file and we'll be in business. For info on bkondisk, which lets you save your ROM (as .img files), see this wiki http://wiki.xda-developers.com/index.php?pagename=bkondisk
Could anyone point me to some resources on these two file formats? Then maybe we could come up with a conversion program when one doesnt exist
Getting closer!
Great, it seems we are getting closer to our goal!!!
But still surprises me that no one has posted a complete how to... perhaps the only few who know the deal haven't read this thread yet.
Now we know the following:
1. Bkondisk: software that allows to backup ROM in *.img format.
2. The original format of the ROM is *.bn
We don't know if the *.img file needs to be converted to *.bn or if they are compatible.
I also found out about an easier method to re-flash the ROM:
1. Format your SD Card in FAT32;
2. Copy your *.bn file to your SD Card;
3. Turn off phone, insert SD Card, Turn on phone in bootloader mode;
4. The phone should automatically recognize the ROM and start the flashing process.
Uccelino: Try placing the *.img file in the SD Card instead of the *.bn file. Maybe, just maybe the phone also recognizes *img files!
Getting closer!
Great, it seems we are getting closer to our goal!!!
But still surprises me that no one has posted a complete how to... perhaps the only few who know the deal haven't read this thread yet.
Now we know the following:
1. Bkondisk: software that allows to backup ROM in *.img format.
2. The original format of the ROM is *.bn
We don't know if the *.img file needs to be converted to *.bn or if they are compatible.
I also found out about an easier method to re-flash the ROM:
1. Format your SD Card in FAT32;
2. Copy your *.bin file to your SD Card;
3. Turn off phone, insert SD Card, Turn on phone in bootloader mode.
4. The phone should automatically recognize the ROM and start the flashing process.
Uccelino: Try placing the *.img file in the SD Card instead of the *.bin file. Maybe, just maybe the phone also recognizes *img files!
Also...
Sorry for the double post back there!!
Also check out this thread I started when I bricked my first Excalibur:
http://forum.xda-developers.com/showthread.php?t=378050
I never got a feasible response to wether sprite backup would work or not, and I did not want to spend $30 bucks to find out.
velascoperroni said:
Great, it seems we are getting closer to our goal!!!
But still surprises me that no one has posted a complete how to... perhaps the only few who know the deal haven't read this thread yet.
Now we know the following:
1. Bkondisk: software that allows to backup ROM in *.img format.
2. The original format of the ROM is *.bn
We don't know if the *.img file needs to be converted to *.bn or if they are compatible.
I also found out about an easier method to re-flash the ROM:
1. Format your SD Card in FAT32;
2. Copy your *.bin file to your SD Card;
3. Turn off phone, insert SD Card, Turn on phone in bootloader mode.
4. The phone should automatically recognize the ROM and start the flashing process.
Uccelino: Try placing the *.img file in the SD Card instead of the *.bin file. Maybe, just maybe the phone also recognizes *img files!
Click to expand...
Click to collapse
I just had an idea: I will flash a ROM, back it up, and compare the *.bn files to the *.img files I get from backing up - maybe they are or are almost the same, and we can convert them
I will try. Thanks

Alltel CDMA Desire Thread

I am starting this thread in an effort for Alltel Desire users to find appropriate help in rooting and flashing. I have been working on the Hero and recently went to the Desire and would have found this useful. The following is what I did to get CM6 on my phone...
Use the unrevoked root method here:
http://forum.xda-developers.com/showthread.php?t=788044
Everything you need is there, you will need the HTC Sync DRIVERS installed but NOT the sync software... Just hit cancel at the install software point after the drivers have installed.
S-OFF will fail with unsupported radio... this is fine and GSM specific.... You are rooted.
Next do a nandroid, in case you want to go back... I know not af a RUU for Alltel Stock...
Next flash CM6... (or other rom.... I have not tried any others. If you do be sure it is CDMA not GSM). Here is a link to the RC1 CM6 CDMA Desire....
http://forum.cyanogenmod.com/files/file/143-update-cm-610-rc1-bravoc-signedzip
If you want google apps you can find them at the above link as well. Flash it after CM6
***To make MMS work***
This is a file I made to fix MMS on my alltel hero... It also works on the Desire.... It is below...
I will next post how I removed the branding from this when I get a chance...
Hope this helps someone from Alltel (or other regional carriers with Desire)
Make it say Alltel.....
I am merely reposting what I found here.
1) Download http://dl.dropbox.co...1098768/eri.xml to your computer (right click, save as) EDIT: if the link doesn't work refer to post #11
2) Open in notepad and change "US Cellular" to "Alltel" or whatever you want
3) Transfer your altered eri.xml on your SD Card
4) Download Es File Explorer in the Market
5) Open Es File Manager, hit Menu button, and go to Settings
6) Scroll down til you see, at the very bottom, Root Options
7) Check Root Explorer, hit ok (after reading the Disclaimer FULLY of course), and selet CyanogenMod
8) Check Mount File System
9) Go to wherever on your /sdcard you placed eri.xml
10) Long press on eri.xml, select copy
11) Hit the "/" button at the top left
12) Go into the data folder
13) Paste the eri.xml
14) Reboot your phone!
Your phone is now branded Alltel... (or whatever you decided to put there)
Alltel Shipped RUU
http://forum.xda-developers.com/showthread.php?t=832187
-Mr. X- said:
Alltel Shipped RUU
http://forum.xda-developers.com/showthread.php?t=832187
Click to expand...
Click to collapse
thanx! will file away for the future...
MIUI for cdma... loving this rom....
http://forums.miui-dev.com/forumdisplay.php?23-HTC-Desire-CDMA
alltel mms fix works for cm6 and miui roms... and also has support for many regional carriers. should work for most 2.2's... not working for 2.2 sense in post 7 BUT that is prob because mms is broke in the port and not yet working for anyone ??????????
Froyo Sense for CDMA Desire
I am not with Alltel, but another regional CDMA carrier. The Android Development section for the Desire is so messed up you can't tell what is what. I understand that most of the roms are for GSM, and I am looking for a stable Froyo Sense rom for the CDMA Desire. Anyone running one or have a link?
kenny.deford said:
I am not with Alltel, but another regional CDMA carrier. The Android Development section for the Desire is so messed up you can't tell what is what. I understand that most of the roms are for GSM, and I am looking for a stable Froyo Sense rom for the CDMA Desire. Anyone running one or have a link?
Click to expand...
Click to collapse
Only 2.2 Sense for CDMA: http://forum.xda-developers.com/showthread.php?t=806841
umm it says im on us cellular is that true and if so can I update to the true froyo 2.2 when they offer it for us cellular
Godhandfreedom said:
umm it says im on us cellular is that true and if so can I update to the true froyo 2.2 when they offer it for us cellular
Click to expand...
Click to collapse
Post 2..... it says us cellular but its not... post 2 walks you through making it say alltel if you wish
cant get the link to work????
gimme a sec i post one here really quick... here you go...
This is the eri needed. LOL listen up... this one says "halfevildruid" where the carrier name needs changed where as the instructs in post 2 say us cellular. Yeah my carrier in my phone is halfevilddruid... anyway just change that to your carrier and adhere to the rest of the instructs in post 2. The dropbox link apparently isnt working.... it's not mine
there u go
After flashing the rom my cam takes green pic's ???? does yours ?
now that you mention it... i got green tinted pics when using the flash at night in the snow... but all other pics were fine... hmmm
Yeah its at night with the flash I took some today outside and they looked fine . wish alltel would just let froyo out of the bag lol have you heard of anyother roms that work good yet?
So when USCC gets their offical release, will this give devs a more usable stable version to make roms from, almost as if alltel had released it on their own?
Was wondering if anyone could unpack the alltel ruu and make it flashable.
Sent from my desire cdma using XDA App
http://shipped-roms.com/download.ph...8.11_NV_Alltel_1.70_release_150765_signed.exe
I'm getting an Alltel Desire (BravoC) on Tuesday. I want to put a custom ROM on it, primarily to get the extra space for application storage, but I am very concerned because there are several people floating around the Internet reporting that they are not consistently receiving SMS with this phone and custom ROMs. Is this a widespread issue or fairly rare? I am looking to go with Cyanogenmod 6 (Froyo, whatever the latest "stable" subversion is), because I'm not so sure about the Gingerbread nightlies yet.
Also, is it correct that the video camera doesn't work with these ROMs?
Thanks a ton!
Mark
Camera issues.
I am using CyanogenMod 7 at the moment, but stable CyanogenMon has the same issues.
I used unrevoked to root my phone. I have tried several roms, and I am having camera issues. The screen goes blank then activity camera (in application Camera) is not responding.
I have wiped, and cleared dalvik cache. I have tried a class 10 and a class 4 card.
I have all tired fix permissions.
Any ideals?

[Q] What are the new folders in EC05(csc, seh, sem)

I have noticed these new folders in EC05 /system/(csc, seh, sem). Does anybody know what they are? I notice they contain some sort of .bin file. I removed them yesterday from my rom and didnt notice any changes in the performance. If there is anybody that knows what they do, please let me know. As far as I know, no other phone has these files. I just sold my Evo last week and it didnt have them and it was running 2.2 or cm7.
Edit: the files are /csc, /seh, /sem
shiftr182 said:
I have noticed these new folders in EC05 /system/(ces, seh, sem). Does anybody know what they are?
Click to expand...
Click to collapse
I don't have a /system/ces.
/system/{seh,sem} contain copies of the (back) camera firmware. In EB13 and prior there was a single copy of the firmware in /system/firmware, which was moved to /system/sem in EC05. /system/seh is new, I'm not sure if it's an older or newer firmware version but it's different.
I'm not sure of their exact purpose, although I know that, depending on which firmware version your camer reports, one of /system/{seh,sem}/CE147F02.bin is read by the kernel camera driver to determine the "main software version." If nothing else, removing both CE147F02.bins may (probably?) result in your back camera not working. CE147F0[013].bin are not used by the kernel directly, but that doesn't rule them out being used by a user package.
Thank you.

[Q] CM9 on Gio S5660M

So i have the Gio S5660M model, is it possible to put cyanogenmod 9 on it? do i have to take different steps from the S5660 model? If so, is there a posted guide on how to do so?
From my experience, just use the same steps.
Good luck!
Okay, well ive successfully installed it, few concerns. Uhm, where it should say my service provider, it says 302880(not sure what that means) Every few minutes, the screen will go black, or go black and then the brightness changes. I can hardly connect to the internet, sometimes my texts wont send, also wont sync my facebook which i noticed was an update in beta8. Not sure if i did something wrong, seeing as these problems shouldnt be occuring reading the changelog. any thoughts?
It sounds like you've flashed an Europe/Asia 5660 baseband as well. Undo that and you should be fine.
302880 is the MNC/MCC pair for your carrier. In this case, the Bell/Telus shared network. (Which I find somewhat odd; I would expect 302610 or 302220 for Bell/VMC/Solo or Telus/Koodo respectively.)
Good luck,
Darkshado
That sounds about right How would i go about undo ing that?
Through Odin, flash the amss image only. Or you could use dd in recovery as well.
The amss image of the S5660M rom? (sorry still new to this stuff)
How do i flash only the amss file ?
Dig some more through early Gio related threads. The explanations are there.
Hint: Tar archives can be edited. Remove what you don't want and flash with Odin.

Categories

Resources