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?
Related
When I try to save the PPP settings for verizon (they are currently set to: [email protected] and I need to change to [email protected]), the settings continue to revert back to alltel!!! I really need some help with this - why would I be able to change every other setting via QPST except for PPP username and psw? Does anyone know if this has something to do with the registry? Thanks so much!
"I'm not really sure why you are editing these fields in QPST or why you would need to. If you have Verizon, flash with the latest WM6.1 that Verizon released, then flash with this ROM. Once you do *228 and get activated these settings will all be configured automatically."
I did that - I need these settings corrected so that I can access data. I am unable to do so because the settings keep reverting back to [email protected], even after I just changed them! I just now flashed back to the Sprint Stock ROM with radio 3.43 and still is unchanged!
I don't know what to do... I'm really freaking out - I did flash to an alltel ROM in the past, but why aren't the newer ROMS overwriting the old PPP settings???? Is it a radio problem (shouldn't be because I just flashed with Sprint radio ROM)
In any case, no matter what ROM I use, I cannot edit the PPP username and psw - it always reverts back to alltel. Does anyone know what I should do? Thanks!
P.S - I also installed the dcd Verizon Wireless carrier cabs and still no go...
I'm not really sure why you are flashing with all these different ROMS to be quite honest. I'm assuming that when you flash with these ROMS you aren't letting customs run? What ROM are you eventually going to be using? Do you care about being able to enable GPS?
All I care about right now is getting the PPP username and password changed.
It seems as though I cannot access the nvm folder using EFS File Explorer. I am trying to use QXDM, but I have no idea how to use it. Does anyone know what the commands are for changing PPP in QXDM?
yoko1324 said:
All I care about right now is getting the PPP username and password changed.
It seems as though I cannot access the nvm folder using EFS File Explorer. I am trying to use QXDM, but I have no idea how to use it. Does anyone know what the commands are for changing PPP in QXDM?
Click to expand...
Click to collapse
Dude...flash with the official Verizon ROM linked below. Let customs run. Once complete dial *228 and choose option #1. Once that is complete you may have to call #8899 to get a new authentication key. Make sure your phone is unlocked with the 2.31 imcokeman unlocker, which I assume it is since you are already flashing away with various ROMs. Once you do this your settings will be fixed. You shouldn't be editing them the way you are trying. REFLASH WITH OFFICIAL VERIZON ROM...nuff said.
http://pcdphones.com/phone_downloads.aspx?bid=95&cid=1&mid=302&carrier=Verizon%20Wireless Software Upgrade on right hand side.
rzawora said:
Dude...flash with the official Verizon ROM linked below. Let customs run. Once complete dial *228 and choose option #1. Once that is complete you may have to call #8899 to get a new authentication key. Make sure your phone is unlocked with the 2.31 imcokeman unlocker, which I assume it is since you are already flashing away with various ROMs. Once you do this your settings will be fixed. You shouldn't be editing them the way you are trying. REFLASH WITH OFFICIAL VERIZON ROM...nuff said.
http://pcdphones.com/phone_downloads.aspx?bid=95&cid=1&mid=302&carrier=Verizon%20Wireless Software Upgrade on right hand side.
Click to expand...
Click to collapse
This is what I would do as well. What radio on you on. You say 3.43, but there is no 3.43. Check in Device Info in settings.
It souunds like you flashed an altel rom and let custmizations run.
Try flashing the stock rom (from verizon) and let customizations run. Then follow the steps to listed earlier in this thread (think the site was wiki pda) to get aGPS running. I wouldn't call Verizon for an A key until you are done flashing. Then the easy way to repopulate your phone is to go online to verizon my account and activate another phone on your line, then active your 6900. When you do this it automaticlly sends a new A key and don't have to try and explain to tech why you need it done.
Good luck
Okay I am doing that now. You are correct, I did let customizations run...
However, I was able to forcibly edit the NV Items using CDMA Workshop and that seemed to work...until I tried to edit the password with QPST. So I will give it a try and if it still doesn't work, I will just re-write the NV Items everytime I use QPST. Thanks guys.
kmanuel74 said:
It souunds like you flashed an altel rom and let custmizations run.
Try flashing the stock rom (from verizon) and let customizations run. Then follow the steps to listed earlier in this thread (think the site was wiki pda) to get aGPS running. I wouldn't call Verizon for an A key until you are done flashing. Then the easy way to repopulate your phone is to go online to verizon my account and activate another phone on your line, then active your 6900. When you do this it automaticlly sends a new A key and don't have to try and explain to tech why you need it done.
Good luck
Click to expand...
Click to collapse
The sreps I was refering to were in the rom thread, but here is a link.
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS
I would be very careful changing stuff to verizon already.
I went into the alltel store and they won't even activate a verizon phone yet
because if you have verizon software they will bill you on a different account on verizon (if you're still under an alltel contract), which means that you will be being billed per minute and for data as a pay as you go plan.
she said this is because verizon and alltel billing systems aren't fully integrated yet.
so if you haven't resigned a verizon contract yet, meaning you're still on your original alltel contract, be careful.
I just unlocked a brand new HTC G2 Tmobile phone. I used my sim card thats been active for years, Its Cincinnati Bell Wireless prepaid. Should work fine, but now its saying "No Service" and wont make calls/texts? Can anyone help plz?
Did you use gfree to unlock it? Worked fine for me. Try going into settings and manually searching for network, and restart 2-3 rimes. Worked for me.
No i went thru a service. it was unlockthatphone dot com
ill try that tho....
Well there's no need to.
And I dont want to be the one to tell you, but you might not be able to get service again, even with a T-Mo card. I've read that a lot of people had that problem with the unlock codes.
Well i couldnt figure out how to unlock it. Looked for hours and the guides here were so confusing id rather pay 30.00
How do i figure out if it will ever work again or not?
Someone mentioned I wireless might be CDMA and tmobile was not? Any clue how to check this?
As long as the carrier uses sim cards it's a GSM carrier (99% of the time, I know Verizon Global phones use simcards too.) if that's what you meant.
And for your question try some searching. I never bothered to find/read up on that since I unlocked it without a hitch.
I called the guy back that unlocked it for me, and he states "its impossible for an unlock code to damage 'ware in the phone, the guys on xda dont know what theyre talking about" and that he will work with me to fix this, he says hes pretty sure its my Baseband Version which is:
Baseband version 12.22.60.09bU_26.02.01.15_M2
Any thoughts on these?
Also this is from the HTC forums: http://community.htc.com/na/htc-forums/android/f/99/p/7564/33750.aspx
Actually I've unlocked my phone with an unlock code that Tmobile gave me. Customer Service said you just have to be paid up to date to get an unlock from them.
It may just be that the G2 is on a different carrier band than the carrier you were hoping to use.
Unfortunately, the onus is on you to look it up, I wouldn't expect the customer service for your company to know if your phone will work on their network or not.
so whats the deal ... If I unlock my G2 with a unlock code from TMobile; so I can use it when I head the Philippines on vacation ... I wont be able to get service even with Tmobile ???
There are reports of unlock codes not properly working on the phone all over the place. After entering in the unlock code, some phones simply cannot find a network no matter what SIM is inserted (even one that might have been working before). I met one dealer who said the same thing as your guy (unlock codes can't do that to a phone and people on the internet are stupid), so I had him try inputting in the code himself---the phone became messed up and all he could do was apologize. Some phones work fine though.
You can fix this weird state by running gfree to get subsidy unlock (there are at least two really long threads explaining this). Check out the wiki for instructions on how to do this.
Your phone unlock guy just wanted to get his $30. He knows full well that the carrier-unlock function in HTC VISION is ***DEFECTIVE***.
Problem is that the eMMC chip on the phone is write protected, so the unlock needs to be relayed through to a second mechanism and applied AFTER REBOOT, but it gets corrupted and instead of writing "0000" into the specified location on the eMMC chip, it will in some cases write it ***ENCRYPTED*** -- some function of your unlock code. Ends up being locked to a (most likely non-existent) random carrier, and the unlock code will no longer apply.
Once it has been damaged like this, the ONLY way to fix it is by running "gfree" on it, which would have unlocked you SAFELY and FOR FREE to begin with.
Find the button at the top of the page labeled "wiki" and find HTC VISION in there, and FOLLOW THE INSTRUCTIONS! This will cure your phone.
Wow Android is alot more extensive than windows phone. I'll try th e gfree but I really dont have that much experience on this phone. I barely temp rooted and overclocked this to 1427mHz. And barely reading all the perm root and s-off threads right now... I hope I can do it to mine and my wifes phone without messing something up. I tried abd and I cant seem to get it to work right. When I tried temp rooting. Can I do gfree without a computer can I do everything on the phone without abd???
Well for carrier unlocking, I think you can only do it with adb, but what do I know.
Ok so the one is carrier locked or whatever. I need adb to unlock it? and gfree to unlock my unmessed with one. Where do i find these programs and instructions to use them. Im PC literate but cell phone retarded. thanks in advance! I dont wanna pay to unlock these.....
Ok ive done a little more research. I have the JDK and the SDK kits installed. Im preparing to use GFREE. But now im stuck. my SDK MANAGER says the following error when i try to boot it up.
Failed to execute tools/android.bat:
The system cannot find the file specified
What am i doing wrong? im trying but its a slow process.
Grim4239 said:
Ok ive done a little more research. I have the JDK and the SDK kits installed. Im preparing to use GFREE. But now im stuck. my SDK MANAGER says the following error when i try to boot it up.
Failed to execute tools/android.bat:
The system cannot find the file specified
What am i doing wrong? im trying but its a slow process.
Click to expand...
Click to collapse
Navigate to the tools folder and see if there is a file inside called adb.exe. If so, download and unzip both the temp and perm gfree zip files from the wiki into that folder. You should be ready to go. When you connect your phone to the computer via usb be sure that you have the usb debugging checked (on).
Im so lost. the company is willing to refund the amount i spend to unlock the phones, so im just gonna have it done that way. Will the one with the locked carrier be able to be unlocked by a professional?
I got the temp loaded, the ADB loaded, the tools loaded. But this is what comes up
http://i46.photobucket.com/albums/f140/Diamondx0xEyez/wqeqweqw.jpg
Ok guys. Im desperate. Here is what Id be willing to do.
Im offering $20 to whomever can help me. Heres what I need.
I have 2x HTC G2 That need the FULL UNLOCK. Not the code, THE UNLOCK.
Im told its done thru this GFREE program. I am NOT smart enough to figure this out after days if trying. If someone can do the following thing for me, Ill donate that money straight to your paypal account.
-Send me a ZIP file with ALL THE NECESSDARY folders, with ALL THE NECESSARY files already placed in them, I plug in USB unlock phones, u get paid.
(I need ADK files, JDK files, all gfree files, EVEYRTHING i know itll be a big zip, but im payin so i dont mind)
I am unable to figure out these files, I am either installing the SDK files wrong or something, but I just need the files ALREADY placed in a file and just use them since im too stupid to do so desite reading many guides. Sorry ive tried. Now i just wanna use my phones.
I am using the Jiminy V Rom on Cricket
I am unable to OTA or make calls on the Cricket network. when I try and make a call I get 'Unauthorized' and when I try to OTA (*228) the system says 'unable' at the very beginning. I have done many EVO's to cricket before, and I have checked and double checked all my PST settings, my MEID/MIN/MDN/PRL particularly.
Even when OTA doesnt work , I can always get voice/text working on virtually any other phone by manually programming the MDN/MIN/Home SID & PRL.
My cricket home SID is 4923 & I am using PRL 32200
I have even loaded a working evo's PST settings into this phone (via QPST, read from one phone, write to another), and get same results even after making sure the MDN/MIN & MEID are correct.
The symptoms are exactly the same as if my MEID is not in the cricket system, yet I have triple checked them (and I had someone else program another phone with my MEID and that phone OTA'd and made calls on Cricket with no problem).
Some other data for consideration Android 2.1, build Baseband 2.15.00……007.25 kernel 2.6., Radio 2.05.00.06.10, HBOOT 0.79.0000 SHIP S-OFF
I have also tried factory builds 2.2 (3.26.651.6) and 2.1, (Baseband 2.05.00.06.10,Build 1.41.651.1) with same result. Note: they did not change the PST.
Is there a factory build which will put everything back to Sprint or should I consider updating the HBoot and /or Radio?, I assume the programming for the OTA is done in the Radio?
I am stumped.
Bump, If anybody can help me with this, its been driving me up the wall for two weeks now.,
Have you tried flashing an RUU and updating everything from there? If it isn't the MEID then it might just be your phone having a glitch. Flash it using RUU and let me know.
how do you reset PST/NAM (SPC,MIN,MDN, Etc) to factory?
I have tried RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26_release_171253.exe , hboot goes from 0.92 to 0.79, radio from 2.15 to 1.39.00.04.26, and android from 2.2 to 2.1.
But the pst/nam settings remain unchanged, mdn,min, sip, nai, etc are all cricket. even the SPC is still unlocked at 000000. ANd the S-OFF flag is off, Shouldnt the RUU's re-root the phone?
Is there an alternate way to run the RUU, I have tried putting the phone in HBOOT usb mode, then run the RUU but with three different batteries it tells me they are too low (under 30%).
Should I be in Hboot mode to run RUU? (I have been running it from the PC with the phone booted up.
To answer a couple of my own questions, none of the RUU's reset the EPST whether they where loaded from the PC via the .exe method or from the SD card PB31IMG method.
I found a reference to ##786# and found that yes that does reset the EPST (including the SPC) back to factory.
So I figured maybe the problem would be solved, so I updated PST for cricket (MDN,MIN,SID,PRL) and tried again, still no OTA and still 'Unauthoriized; when I try to make calls.
I am starting to believe I have a hardware problem, but how can most of the phone work and yet it have (apparently) problems transmitting MEID?
Seems like no interest here or everybody stumped. I am willing to pay some one to help me resolve this. contact to my email or post here, I will certainly let the forum know when I resolve this. Thanks
GDEMI said:
Seems like no interest here or everybody stumped. I am willing to pay some one to help me resolve this. contact to my email or post here, I will certainly let the forum know when I resolve this. Thanks
Click to expand...
Click to collapse
No need to pay, I forgot about this thread lol. I think you may be right that this is a hardware problem or glitch and I am actually stumped on how to help you. :|
some help here
hi...
im trying to flash my phone and make it to worj for cricket carrier and i do everything ....i think correct but when i try to make a call it ask me if i whant to make a collect phone or buy some kind of card .
i already try the qpst configuration twice and even try many plr to and no luck
righ now i have a 45713hybryd plr
and i use this
http://forum.xda-developers.com/showthread.php?t=934417
i even take to a cricket store to chek for the s/n numbers and the min and they say that everything looks ok but i can do anything on the phone
any ideas, and help
thank
Very dirrerent problem
paulinaoza said:
hi...
im trying to flash my phone and make it to worj for cricket carrier and i do everything ....i think correct but when i try to make a call it ask me if i whant to make a collect phone or buy some kind of card .
i already try the qpst configuration twice and even try many plr to and no luck
righ now i have a 45713hybryd plr
and i use this
http://forum.xda-developers.com/showthread.php?t=934417
i even take to a cricket store to chek for the s/n numbers and the min and they say that everything looks ok but i can do anything on the phone
any ideas, and help
thank
Click to expand...
Click to collapse
Your problem has different symptoms from mine (the threadstarter), it sounds like your prl is incorrect. If you have a correct prl & sid (these can vary for the market you are in , in Phoenix the SID is 4923 and I use the old nationwide non EVDO PRL of 1040) when you dial 611 you will get Cricket, regardless of your ESN/MEID being registered with Cricket, if this doesnt work do not go further. Find a PRL/SID that works (sometimes changing CDMA connect from Auto to Home only can help) . Also make sure MNC/MNC are set to 310/0. Country code/Carrier I think.
Once you get 611 to connect to Cricket, *228 (OTA) will connect to cricket, if It disconnects you before the music starts playing and says 'Sorry....' it is most likely your MEID is not registered correctly with Cricket. In Phoenix *228 always works on EVo's as long as SID/PRL/MEID are correct,
The message you are getting about a credit card required means you are connnecting to some other carriers network (usually Verizon) which is transferring you to someplace to allow you to make a call even though you are
"not authorized" on the network. Go back and check 611 & *228.*228 will load the correct prl for your area and rate plan, check after it runs to see what was loaded. It will also most likely overwrite EVDO settings including MIP, Sip, NAI, etc.
At this point your phone should work, talk & text.
I had the same problem and I look all over. I wanted to unroot and remove jimmy v rom. I was think that if i update to the new update that it will fix it self and i was right. First I had to remove the jimmy v rom, so i got ruu to update the htboot and that let me update to the new 2.3.3. It fix it self and f***ing A.
avillal87 said:
I had the same problem and I look all over. I wanted to unroot and remove jimmy v rom. I was think that if i update to the new update that it will fix it self and i was right. First I had to remove the jimmy v rom, so i got ruu to update the htboot and that let me update to the new 2.3.3. It fix it self and f***ing A.
Click to expand...
Click to collapse
Can you be more specificwhat you loaded and what versions of hboot where involved? I downgraded to 2.1 (with RUU) and hboot .79 and it did not resolve problem.
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.
Hello. The guide I'm following is found at http://forum.xda-developers.com/showthread.php?t=2221039. I'm following it character for character short of where the thread has corrections to some errors.
My end goal is getting CM7.2 on this thing and having a rooted phone. My question is basically "What do I do when I'm experiencing the following?"
When I get to:
•fastboot flash zip firmware.zip under step 7 I end up with a FAILED (remote: 41 model id check fail)
Everything prior to this point is going exactly as it should as far as I can tell. There are no other errors of any kind. When I continue through the process after this failure I end up at:
•adb shell /tmp/gfree -f under step 8
This is where the second failure occurs which I imagine is due to the firmware issue. It ends up with a bunch of lines showing things happening and then comes to:
Attempting to power cycle eMMC... Failed.
Module failed to power cycle eMMC.
These are the only issues I'm having with this guide and can't seem to figure it out. Unfortunately I can't ask on that thread because I'm under the 10 post mark as I've tried to read instead of ask questions. At this point I'm just stuck though. As of now I'm trying to flash CM7.2 using CWM as the rooted stock rom is done in that guide. So far I'm having no luck though. I'm glad I'm using this as a test dummy before getting a newer phone and attempting anything on it. Any help that can be provided is greatly appreciated. I'd love to get this sorted out.
bhd1223 said:
•adb shell /tmp/gfree -f under step 8
This is where the second failure occurs which I imagine is due to the firmware issue. It ends up with a bunch of lines showing things happening and then comes to:
Attempting to power cycle eMMC... Failed.
Module failed to power cycle eMMC.
Click to expand...
Click to collapse
From what I have read gfree works for Android 2.2.1 and you do realize if you the hboot version is correct you can just unlock at htcdev.com and flash the rom. Thats what werked for me.
lamebmx said:
From what I have read gfree works for Android 2.2.1 and you do realize if you the hboot version is correct you can just unlock at htcdev.com and flash the rom. Thats what werked for me.
Click to expand...
Click to collapse
Thanks. Actually, just after I posted that I tried to load CM 7.2 in the same way that it directed to load the rooted stock ROM in the guide. This was after using the HTC Dev Unlock. Then I discovered I needed to have 4.0+ to stream video from an app I was using. The night after that I ended up going with an Unofficial CM 10.1 port for Ace devices and making it think it was an Inspire 4G again (http://forum.xda-developers.com/showthread.php?t=2093845).
A little wonky at random times, probably hardware related, but works really well and allows me access to things I wouldn't otherwise have. I was really concerned about running non-final release or "stable" labeled ROMs which has had me holding off on getting a newer phone. After running this build for a few days which is based off a nightly, I see no reason to worry. It seems a simple process to do all this stuff although I'm sure the actually programming is more difficult.
Basically, the only thing I'm left without is S-Off. From further reading I've done this doesn't even really matter anymore. I can load custom ROMs, I can gain su access, I can do anything I want to the phone as far as I can tell. I'm happy with it is unless there is some secret of awesomeness I'm unaware of that I've yet to tap.
bhd1223 said:
Basically, the only thing I'm left without is S-Off. From further reading I've done this doesn't even really matter anymore. I can load custom ROMs, I can gain su access, I can do anything I want to the phone as far as I can tell. I'm happy with it is unless there is some secret of awesomeness I'm unaware of that I've yet to tap.
Click to expand...
Click to collapse
I just got S-OFF with this guide:
http://forum.xda-developers.com/showthread.php?t=2367322
using the proper PD98IMG.zip from this thread:
http://forum.xda-developers.com/showthread.php?t=2193681
FYI it downgrades you in the process and I have not got my phone to boot yet, but im 99% sure its cuz i have not done the upgraded RUU from the first thread (JB probably does not like GB radio etc) but unlocked and S-OFF leaves it where you should be able to fix it.
lamebmx said:
I just got S-OFF with this guide:
http://forum.xda-developers.com/showthread.php?t=2367322
using the proper PD98IMG.zip from this thread:
http://forum.xda-developers.com/showthread.php?t=2193681
FYI it downgrades you in the process and I have not got my phone to boot yet, but im 99% sure its cuz i have not done the upgraded RUU from the first thread (JB probably does not like GB radio etc) but unlocked and S-OFF leaves it where you should be able to fix it.
Click to expand...
Click to collapse
Thanks lamebmx. I was having a boot issue as well when I first installed CM7.2. Then I learned that each ROM needs to have it's own boot image flashed to the boot partition. After that no issues. When I did 10.1 I used the boot image from that as well and haven't had any issue with booting. You may have done that already but it can't hurt to re-flash if you already did, or do it if you haven't.