Related
hey guys,
i was wondering if there was a way like there is to change the banner name from sprint using CDMA, but to change the software name of the rom itself?
i''ve customized my rom so much and still plan on making many other changes, and i would like to reflect that on the rom name as well but can't seem to turn up anything with search...
thanks a ton
The name is in the buildprop
i know when you typed that up it was extremely clear in your mind...
but, where is buildprop? only tools i've used so far are QPST, CDMA, adb, and xUltimate....any of those have access to buildprop or is that through one of the "kitchens"?
lol. Sorry
The build.prop is in the system folder. There are many different ways to access it but the easiest way is probably with the phone itself.
You can use root explorer to mount r/w and edit it with the phone. Once you finish, remount r/o.....reboot and done.
Why is it that important to change the name of the Rom? The only place I can think that it really shows that is in about software. So unless you are trying to take credit for someone elses rom and show it off what would be the advantage ?
Most roms are built off others. Just give credit where credit is due.
this is not going to be shown to anyone else. and yeah a rom is built off another rom, but then the rom i'm downloading, which was built off another, should have that original rom's name, not the new one...so?
this is a change for me, and only for me.
thanks for the help bluebeast, made the change already
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.
I have a desire (cdma) i have tried using unrevoked and unrevoked forever to obtain s-off. I have tried on 2 different phones. Both times, after making no other changes, I lose the abilitity to send mms. I can run unrevoked, and mms will work. I run the update to get s-off and it no longer works. Is there something I am doing wrong, is there any troubleshooting I could do?
I know this issue is a month old, but we may have solved it last night on the unrevoked IRC channel.
I had the same problem, and it turned out it was because unrevoked overwrote my phone's carrier ID and it was using the MMS protocol settings for another company.
The guide here will tell you how to edit your BCID, but it doesn't say how to find the right one if you're already having the problem. http://home.kennynet.co.uk/~kenny/bcid-fix.txt
unrevoked had changed mine to UTSI_005 when it was meant to be UTSI_019. I happened to know my correct one from my previous phone, and some versions of stock CDMA ROMs have a list buried somewhere in them.
If anyone is still having this problem, which is only likely to happen with people on carriers with outsourced MMS gateways like Interop, I'll see if I can get the list.
Im still having the problem. I am on a small regional carrier --Inland Cellular. Any help is greatly appreciated.
I had basically given up on trying to fix it. They are supposed to release a RUU for froyo here soon, and I was hoping that would fix the issue, then I could put cyanogen back on.
Thanks
deepsix_69 said:
Im still having the problem. I am on a small regional carrier --Inland Cellular. Any help is greatly appreciated.
I had basically given up on trying to fix it. They are supposed to release a RUU for froyo here soon, and I was hoping that would fix the issue, then I could put cyanogen back on.
Thanks
Click to expand...
Click to collapse
The RUU may not update the /misc partition which is where the problem is. Assuming there's not another carrier named Inland Cellular and your carrier's website is inland3g.com, then they do use Interop and your problem is probably the same as mine was. According to the "telephony.db" file from the generic CDMA 2.1 RUU for the HTC Hero, your CID is UTSI_016. This is a carrier ID assigned by UTStarcom for CDMA interoperability and shouldn't change between handset models. To fix this:
Follow the instructions I linked above.
When you do the "getprop ro.cid" make sure it's something other than "UTSI_016" to confirm this is the most likely culprit.
When you get to the hex editing step, also make sure the first 8 bytes aren't "UTSI_016".
If it is the same problem, your "getprop ro.cid" and first 8 bytes of misc.img will probably be "UTSI_005".
Correct the string to "UTSI_016" and follow the directions to flash the corrected misc.img back.
You do need to already have the right MMS server address and port settings for your carrier programmed. If you've been wrestling with this for a while, I figure you've already verified those.
We just stumbled on this last night and as far as I know I'm the only test case so far, so I can't take responsibility if you brick your phone. I'd suggest joining #unrevokedtest on irc.freenode.net for more assistance.
Yep thats the right carrier. I have all the apn info, so that part shouldnt be a problem.
I do have one request if you are able to and its not too hard.
I have had problems with adb on my computer, so I have done everything through terminal on the phone and manaully moving/editing files through the root explorer.
Any chance you can modify your directions to use those methods.
If not, I guess its a good time to figure out adb a little better.
Thanks again.
deepsix_69 said:
Any chance you can modify your directions to use those methods.
Click to expand...
Click to collapse
Sorry, I didn't write them. Someone else wrote them to fix a different problem and they just happened to work for this. But I think ADB will be pretty much mandatory for the dumping and flashing parts. They have to be done in some kind of command shell.
alright i got adb all setup and working. But I am having problems right from the getgo.
I type the first command ($ /system/__unrevoked_su) and it returns and error. I tried reloading a stock rom, rerunning unrevoked and rooting it to see if a file gets created when unrevoked is ran, but I still get an error. It returns a /system/__unrevoked_su not found.
update: i did some playing around was able to verify utsi_005 so it looks like I have the same problem. But I cant complete moving/editing any of the files becuase they dont exist for some reason.
Any ideas.
OKAY, I got it to work, I had to modify your directions to get it to work for some reason, just in case someone else is having problems.
What I did was install a hexeditor on my phone. Open up sdcard/misc.img edited it for the correct UTSI_016 then saved as /sdcard/new-misc.img then entered adb
$ su
# /data/local/flash_image misc /sdcard/new-misc.img
# exit
reran unrevoked and it worked just fine.
On a side note, I suspect I could have followed your directions directly had I used a $ su instead of $ /system/__unrevoked_su but by the time i figured it out, i was already pretty close to doing it without using adb at all.
Thanks again for the help, I would have never got that figured out without your info. Now time to restore my cyanogen mod 7 and restore some apn info.
If you re-ran unrevoked after flashing the new misc.img, it may have put it back to the wrong info.
Let me know how this went, I'm quite interested in whether this is going to be a common problem for CDMA Desire users.
Well by re ran, i quess I meant I ran it once. I was rooted which broke the MMS, I updated the img file and ran unrevoked in order to fix the mms.
It worked excellent though, I would assume its a wide spread problem for certain carriers. I know it happened to 2 different phone for the carrier I am on.
I flashed cyanogen again, and its being a little difficult getting mms to work, but thats a different issue, and I am sure i will be able to get the right solution after playing/searching/reading.
Thanks again.
well, this isnt going so great. I can get mms to work on the stock rom/rooted now (I couldnt before) I tried installing cyanogen back on, and am having no luck.
Any chance you got some pointers on that?
deepsix_69 said:
I can get mms to work on the stock rom/rooted now (I couldnt before)
Click to expand...
Click to collapse
This is actually good news.
If it works on rooted stock when before it would only work on stock before rooting and not after, it means that now you just have the same problems as everyone else with Cyanogen, not a problem specific to the rooting method or the phone's carrier.
I haven't tried a non-stock ROM on mine since I squashed this bug. I have a few guesses as to how to fix it, but I need to test them first.
I have a CDMA Desire on the GCI Network in Alaska, rooted with unrevoked with s-off.
Right now the desire is running on USCC Rom.
Everything is working with the exception of MMS.
When I send an MMS, the number 970-111-1111 is attached to the message as my reply to number.
This is not my phone number.
When the message is replied to, an error is returned to the sender, 'Does not subscribe.'.
I suspect that the problem being addressed in this thread is similar.
I have searched for the misc.img file to edit and cannot find it on my phone.
If anyone can help, I would greatly appreciate it.
I do not know where to find the correct CID, nor what to do with it when I do find it.
Thanks for any and all input....
MrJustAGuy said:
I know this issue is a month old, but we may have solved it last night on the unrevoked IRC channel.
I had the same problem, and it turned out it was because unrevoked overwrote my phone's carrier ID and it was using the MMS protocol settings for another company.
The guide here will tell you how to edit your BCID, but it doesn't say how to find the right one if you're already having the problem. http://home.kennynet.co.uk/~kenny/bcid-fix.txt
unrevoked had changed mine to UTSI_005 when it was meant to be UTSI_019. I happened to know my correct one from my previous phone, and some versions of stock CDMA ROMs have a list buried somewhere in them.
If anyone is still having this problem, which is only likely to happen with people on carriers with outsourced MMS gateways like Interop, I'll see if I can get the list.
Click to expand...
Click to collapse
your doing it wrong.
this line: cat /dev/mtd/mtd0 > /sdcard/misc.img pipes the contents of /mtd0 into misc.img, thus creating the file you were looking for.
the command getprop ro.cid should return the cid value your devices is presently using. when I tried i did not receive a value, instead it echoed the command back to me. if your suspecting your cid has been mangled then this will of course return the incorrect value. for getting the correct value try an s-on gci phone.
you ever tried looking at your logcat when you send mms?
akdale said:
I have a CDMA Desire on the GCI Network in
I suspect that the problem being addressed in this thread is similar.
I have searched for the misc.img file to edit and cannot find it on my phone.
If anyone can help, I would greatly appreciate it.
I do not know where to find the correct CID, nor what to do with it when I do find it.
Thanks for any and all input....
Click to expand...
Click to collapse
I managed to get adb working and talking to the desire.
When I type in 'adb shell',
I do not get the $ prompt, but a prompt that says 'sh-3.2#'
I managed to create the misc.img, pull it to my laptop, edit it with a hex editor changing the HTC__005 to the HTC__010 that was on an unrooted gci desire, push it back to my sdcard as new-misc.img.
The following gives an error
'adb shell
$ /system/__unrevoked_su --------------- (No such file or Directory)
# /data/local/flash_image misc /sdcard/new-misc.img'
I checked, there is a /system---I don't see the unrevoked
Any help is appreciated.
ipfreelytech said:
your doing it wrong.
this line: cat /dev/mtd/mtd0 > /sdcard/misc.img pipes the contents of /mtd0 into misc.img, thus creating the file you were looking for.
the command getprop ro.cid should return the cid value your devices is presently using. when I tried i did not receive a value, instead it echoed the command back to me. if your suspecting your cid has been mangled then this will of course return the incorrect value. for getting the correct value try an s-on gci phone.
you ever tried looking at your logcat when you send mms?
Click to expand...
Click to collapse
Well, I managed to get the file changed, and it shows up in logcat when I send a mms.
This did not cure the 111-1111 phone number problem. In fact, I did not notice any difference at all except for the CID being different in logcat.
I have the same problems with my small local carrier. Also I dont have another phone to pull the info from. Nex-tech is the carrier and if anyone could help me get this info so I could change the CID I would appreciate it.
Update:
I spoke to the unrevoked team in irc and unrevoked doesn't change anything that would break mms. With that in mind my piss ant cell provider did an update to their system and all of the sudden mms is working like a champ on rooted bravoc running cm7.
So I was able to follow all of these steps. I was also able to pull, edit, then push the files back to the phone. I am not able to make it work and when I do
getprop ro.cid it only shows "getprop ro.cid" but not UTSI_016. But if I then pull the file again from the phone, it does show UTSI_016 just not when running the command getprop ro.cid.
Suggestions?
I have been able to make this work on the stock rom, and MMS is back and fully functioning.
I would however like to use Miui again but I cant get it to seem to do the MMS.
I'm on inland cellular with moto x gen 2. 2 when flashing custom roms I have no service. They don't use apns according to their tech support so how do I pull the needed info out of the stock rom and place it in custom one?
So I have what may be an obvious question, but it's not one which I have run into before. (my previous device was a Droid 2 which used a fairly generic boot loader)
I got my phone used off Ebay about 3 weeks ago. When I did, I assumed it was a stock Dinc, and so collected everything that I would need to mod it. Low and behold when it arrived and I charged it up, it had already been rooted, S-offed, and had CWM on it (the auction had not mentioned it being a rooted phone) So it took a sum total of five minutes to flash a new rom in.
Now, on further digging around, I find it has an old radio on it, (2.15.00.07.28) and also still has the old owner's phone number in it. Now, a few forum posts I have read in the past few weeks have indicated that installing a newer radio rom may improve some of the functions such as the light metering of the camera... but I have also seen that doing so may bork the S-off as this is stored in the radio rom?
What effect would it have if I put a radio rom on this already rooted and now rommed phone (Albinoman's JBb3). Should I just do it, or should I return the phone to totally stock prior to upgrading the radio software? And also, is there a way to erase the old owner's phone number from the My Phone Number field since this is now a wifi-only device and i'd rather the OS not send that info out when it's not correct.
Or am I just completely off base and don't need to worry about the radio at all?
Thanks for any help in advance!
You dont have to return to stock to flash the radio.
With radios I think it depends on your area. One radio that works great for someone may be terrible for someone else. The general consensus is that updated/newer software would improve the experience but I think with radios it varies. If you do change the radio make a backup and check the md5. Latest dinc radio is in my SIG.
Sent from my ADR6300 using xda premium
Changing your radio will not mess up s-off or anything else as long as you check the md5 and take the proper precautions. Also changing the radio will not help the camera or anything else besides your cell signal.
S-off is stored deeper than the radio, but tools like unrevoked use certain versions of radios to gain access to this setting and modify it.
No need to revert to stock, and there is NEVER a need to go s-on unless your selling the phone or sending it to HTC. I see so many people say they went s-on to fix some kind of issue, or to upgrade and then the phone messes up durring the proccess and it makes it much harder to fix.
You can remove the number by accessing epst. Dial ##778# hit edit mode and type six zeros as the password. Go to each menu option editing the info you dont want there. Replace numbers with an equal ammountvof zeros (147-237-9900 = 000-000-0000) When done hit menu and commit changes.
You can get all the different radios here. http://dinc.does-it.net/Radios/
cmlusco said:
Changing your radio will not mess up s-off or anything else as long as you check the md5 and take the proper precautions. Also changing the radio will not help the camera or anything else besides your cell signal.
S-off is stored deeper than the radio, but tools like unrevoked use certain versions of radios to gain access to this setting and modify it.
No need to revert to stock, and there is NEVER a need to go s-on unless your selling the phone or sending it to HTC. I see so many people say they went s-on to fix some kind of issue, or to upgrade and then the phone messes up durring the proccess and it makes it much harder to fix.
You can remove the number by accessing epst. Dial ##778# hit edit mode and type six zeros as the password. Go to each menu option editing the info you dont want there. Replace numbers with an equal ammountvof zeros (147-237-9900 = 000-000-0000) When done hit menu and commit changes.
You can get all the different radios here. http://dinc.does-it.net/Radios/
Click to expand...
Click to collapse
Thanks for the answers, that filled in a lot of blanks for me I Figured I didn't need to go S-on, but I didn't know if, like on my old Droid 2, there were certain situations where I'd have to revert to stock before flashing.
UPDATE, I flashed the radio yesterday to 2.15 with no problems. Got a tiny bump in my battery (which tells me the old radio was working harder than it had to)
##778# didn't work for me though, instead it rang up "welcome to verizon" and wanted me to wait to talk to an operator about placing my call.
also tried without the third hash, also tried ##3424 and ##775... all with variations on the same result; either my phone is not in service, or my phone number is inactive... none of them accessed the menu system.
::edit::
I also tried variations on #program# and #data# with no luck,and tried turning off all the radios I could get at.
Any further ideas or steps I may be missing would be greatly appreciated. I also put in an ask over on the rom forum.
eoraptor said:
also tried without the third hash, also tried ##3424 and ##775... all with variations on the same result; either my phone is not in service, or my phone number is inactive... none of them accessed the menu system.
::edit::
I also tried variations on #program# and #data# with no luck,and tried turning off all the radios I could get at.
Any further ideas or steps I may be missing would be greatly appreciated. I also put in an ask over on the rom forum.
Click to expand...
Click to collapse
Have you tried *#*#data#*#* or *#*#program#*#*
Yeah, tried those as well... but got my answer, apparently only Sense-based Roms can use ESPT, and since I'm running Albinoman's JB rom, no go for me unless I flash over to a sense-rom, make the changes, then flash back. Might be a project for tomorrow while the laundry is going... or perhaps I'll wait for beta four of the JB Rom, flash to sense, do the tweak, then flash to the new beta.
but I'm getting there. in the last week I have inserted new kernels, new radios, And troubleshot this problem, plus dialed in my Nova interface tighter and tighter, in addition to the font toying and so on I've been doing. who knows, sooner or later I might even try to compile something.
thanks for the assist though. Is much appreciated.
well, at the end of the day, I never did get EPST working. I tried several different sense roms, tried installing the APK and pushing it from ADK, the closest I got was to punch in ##788# and it would say "loading requested resource" and then, nothing.
so now I'm on to Release Candidate #2 of Albinoman's 4.1 Rom and will come back to the phone number issue later.
Alright guys, I'm posting this here because it's the closest forum to the SCH-R760x I can find (CDMA SGSII) I think you guys are the D710 but I suppose the modem works about the same.
Anyway, in a fit of despair I odined the stock files for the USCelluar Varient of the SGSII which yes... is different.
So here's my problem, it may be more than this, but this is what I've noticed.
-After odining the USCC stock files, under About Phone>Status the "user name" field showed (phonenumber)@uscc.net
-So I odined the Generic stock files ( like I should have done in the first place) with Phone EFS Clear checked and now the same field shows (phonenumber)@carrier.com
-Opened modem.bin from the stock files .tar in a hex editor and found in offset 0822A0 "@carrier.com"
-Tried editing modem.bin to @awcc.com but after saving the file and trying to odin I get a failed. (replaced character spaces with hex 00) @carrier.com=12 characters @awcc.com=9 characters
http://dl.dropbox.com/u/21311280/modem.bin <--- modem.bin file if anyone wants to give editing a shot.
I don't know if anything else beyond this needs to be changed but I'm pretty sure this is at least one of my problems (besides stupidity)
It's almost like my phone is back in the generic state and needs to be programmed for Alltel so if anyone know anything about the initial programming needed for a smartphone at Alltel that may work as well.
No I'm not Verizon, this is still Alltel now owned by Allied Wireless Communications
So anyway, any help or ideas would be greatly appreciated. Also if this would be better suited in a different section please advise.
Thanks xda, you guys have always been great and hopefully can get me through this as well.
191 said:
It's almost like my phone is back in the generic state and needs to be programmed for Alltel so if anyone know anything about the initial programming needed for a smartphone at Alltel that may work as well.
Click to expand...
Click to collapse
My first endeavor would be to look up alltel phone programming, if that wasn't possible, but could still be the fix, I'd take it in to the store and see what they know. I would say this just happened and you don't know what happened.
Sent from my SPH-D710 using XDA