Related
Hey all, long time lurker, first time poster....unfortunately....
So after sitting on MIUI for a good while, and having a blast with it, I decided to try out some other ROMs. I was interested in seeing Cyanogen 6, and so I went about attempting to get the latest stable, non RC ROM onto my EVO. I read into it seeing that I needed to downgrade my hboot, and found the image without a problem (running the .76 right now, had the 9something one before...)
Well, I downgraded my hboot without an issue, flashed the Cyanogen, and got into a splashloop. I figured out it was becaue I hadn't wiped my cache or data before flashing the rom, so I went into the Clockwork Recovery and wiped those, flashed once more, and it booted into Cyanogen perfectly!
Well, almost. I don't have 3G now.
For some reason, I am unable to connect to 3G no matter what I try. My nandroid's broke due to the hboot downgrading, rewiping the cache/data and reflashing cyanogen did nothing, and now for some reason, when I attempt to go back to MIUI, it still will not allow me to connect to 3G. I can send and receive texts, and make and receive calls, but alas, no data connection.
Should I get a fresh RUU and stock hboot, upgrade and restart from scratch? I just want to get back to MIUI at this point with a working, data enabled phone.....
If that's the case, that I do need to start over, where can I find a new hboot for the EVO that isn't .76? I'm pretty saavy when it comes to this stuff, but for some reason right now I just can't figure it out....
HTC EVO running MIUI v0.11 stable
.76 hboot w/ Clockwork recovery
Broken nand backup
whatdo?
Thanks in advance for the help
Sorry for the double post, but I resolved my issue.
I am unsure of what exactly went wrong, but I figured it was somewhere between downgrading my hboot, and flashing the CM 6 stable ROM that my 3G data got scrambled....
So! Using ROM Manager, I made a backup of my working (non 3G) MIUI image, and flashed the Odyxed version of the RUU found here (http://forum.xda-developers.com/showthread.php?t=836728). After flashing in Recovery, it booted into SenseUI, and worked like a charm!
My 3G hath returned, and issues have been solved. It's nice when you're able to fix things on your own, though I couldn't have done it without the help of that handy dandy search button, and the RUU keyword
Oh, yeah, and I guess xxbabiboi228xx as well.....maybe....^_~
Ugh, I'm newly rooted, and I already messed things up.
I rooted a few days ago, ran cyanogen for a bit, loved it, but wanted to try fresh, then ava, then wanted to go back to cyanogen. I felt I wanted to 'start fresh' sorta. Like I had just rooted again. I like... lost 3G. it just keeps saying "turning on" and I think it may be from updating the radio. Because, I was flashing different roms without updating the radio, and everything was working perfectly. But then, like half an hour ago, I updated the radio to the latest version, 2.15.00.09.01, and things started acting up.
So, here's a rundown of what I did. I was running Fresh before I did all of this.
Formatted SD card so I could start from scratch.
Copied the latest cyanogen to SD card
Copied the latest gapps to SD card
Copied the latest radio to SD card. 2.15.00.09.01
Turn off phone and boot into recovery
Wipe cache, the other Dvichik or something cache, and wipe/factory reset
flashed the latest radio, then flashed Cyanogen, then flashed gapps.
it did its thing, and I turned on phone, and saw that I only had 1x coverage. So, I went back to recovery, did a nandroid backup of cyanogen, flashed fresh, started up, and went to update PRL to see if that would fix it. At first, It wouldn't update, and I went and saw that the "mobile network" was just saying "turning on". I restarted the phone, and then went to update PRL, and it did update, however, my data was soooooo slow. Now, the phone went back to the mobile network just "turning on"...... So right now I'm running fresh with basically no data connection. It didn't do any of this before I updated the radio. Before I updated the radio, I had 0 problems.
Soooooo, Yes, I am a HUGE noob. I know. I knowwwww.
What can/should I do?
Is it as simple as just downloading an older radio? I THINK before I updated, I had radio version 1.39.00.05.31...
Can I just go to recovery, wipe cache, and factory reset, flash the radio, then cyanogen, then gapps?
Should I unroot, and start all over again?
I dont think that is the most recent radio. Where did you dl it from? What is your prl version? I flashed the most recent radio combo from calkulin recently, and my radio ends in .19(2.11.00.15.19). That combo included a new radio, wimax, and prl. Only use these updated radios with the most recent 3.70 software. So if I were you,i would try flashing the correct radio combo. Sorry,i dont have a link, but search calkulins posts/threads and surely you will find it . Hope that takes care of it for you!
Sent from my PC36100 using XDA App
josh995 said:
Ugh, I'm newly rooted, and I already messed things up.
I rooted a few days ago, ran cyanogen for a bit, loved it, but wanted to try fresh, then ava, then wanted to go back to cyanogen. I felt I wanted to 'start fresh' sorta. Like I had just rooted again. I like... lost 3G. it just keeps saying "turning on" and I think it may be from updating the radio. Because, I was flashing different roms without updating the radio, and everything was working perfectly. But then, like half an hour ago, I updated the radio to the latest version, 2.15.00.09.01, and things started acting up.
So, here's a rundown of what I did. I was running Fresh before I did all of this.
Formatted SD card so I could start from scratch.
Copied the latest cyanogen to SD card
Copied the latest gapps to SD card
Copied the latest radio to SD card. 2.15.00.09.01
Turn off phone and boot into recovery
Wipe cache, the other Dvichik or something cache, and wipe/factory reset
flashed the latest radio, then flashed Cyanogen, then flashed gapps.
it did its thing, and I turned on phone, and saw that I only had 1x coverage. So, I went back to recovery, did a nandroid backup of cyanogen, flashed fresh, started up, and went to update PRL to see if that would fix it. At first, It wouldn't update, and I went and saw that the "mobile network" was just saying "turning on". I restarted the phone, and then went to update PRL, and it did update, however, my data was soooooo slow. Now, the phone went back to the mobile network just "turning on"...... So right now I'm running fresh with basically no data connection. It didn't do any of this before I updated the radio. Before I updated the radio, I had 0 problems.
Soooooo, Yes, I am a HUGE noob. I know. I knowwwww.
What can/should I do?
Is it as simple as just downloading an older radio? I THINK before I updated, I had radio version 1.39.00.05.31...
Can I just go to recovery, wipe cache, and factory reset, flash the radio, then cyanogen, then gapps?
Should I unroot, and start all over again?
Click to expand...
Click to collapse
Did you try the ##DATA# (##3282#) and entering your MSL so you can restore your profile?
So my wife's Inc2 has been rooted for a few weeks and I installed a 2.3 Sense ROM for her shortly thereafter.
All of the sudden, her phone keeps rebooting and then "freezes" on a screen that has the Exclamation Point inside a triangle with a little green droid character under it. (My wife put a fresh battery in, it boots up into the ROM for about 10 seconds, then says "Powering off: Shutting down..." and goes into the error screen.)
So far, I have tried the following:
Turned airplane mode on.
Booted into safe mode.
Booted into CW Recovery, backed up, then re-flashed the ROM.
Ran a restore from a backup from a couple of weeks ago, which was pre-custom ROM.
Flashed the 2.3 Radio
Flashed a new Kernel
No matter what, I always get it to boot for a split-second and then it boots into Exclamation Point error.
Anyone think of what is causing this to do this after running for two weeks + in the current condition with no issues? What does this mysterious screen mean that it boots into? Any fix I can run via HBoot, Fastboot or Recovery?
WorldOfJohnboy said:
So my wife's Inc2 has been rooted for a few weeks and I installed a 2.3 Sense ROM for her shortly thereafter.
Click to expand...
Click to collapse
Bumping, no one seems to be able to tell me a thing on what this means, what can be done to fix, etc. Any help is appreciated.
Wipe cache, dalvik, and system, then flash a different ROM.
If it continues after that then its likely the phone. And nothing to do with root.
WorldOfJohnboy said:
So my wife's Inc2 has been rooted for a few weeks and I installed a 2.3 Sense ROM for her shortly thereafter.
All of the sudden, her phone keeps rebooting and then "freezes" on a screen that has the Exclamation Point inside a triangle with a little green droid character under it. (My wife put a fresh battery in, it boots up into the ROM for about 10 seconds, then says "Powering off: Shutting down..." and goes into the error screen.)
So far, I have tried the following:
Turned airplane mode on.
Booted into safe mode.
Booted into CW Recovery, backed up, then re-flashed the ROM.
Ran a restore from a backup from a couple of weeks ago, which was pre-custom ROM.
Flashed the 2.3 Radio
Flashed a new Kernel
No matter what, I always get it to boot for a split-second and then it boots into Exclamation Point error.
Anyone think of what is causing this to do this after running for two weeks + in the current condition with no issues? What does this mysterious screen mean that it boots into? Any fix I can run via HBoot, Fastboot or Recovery?
Click to expand...
Click to collapse
Any chance you can take a picture of said screen?
What's weird, it sounds like you're describing the stock recovery screen. But you're still able to access CWM?
You probably want to update CWM on the phone and see if that helps out, one thing you want to do instead of changing kernels is re flash the rom again. Once it reflashes wipe data/cache (Do a factory reset basically) as well as the dalvik cache and boot into the ROM without restoring anything.
Just sign into google and see if it stays up and stable at this point, if it does something that's being restored is probably the culprit or a bad app that continuously tries to run.
By the way, the phone comes with stock sense 2.1, above that is sense 3.0
2.3 is the version of android that runs behind sense. Either 2.3.3/2.3.4/2.3.5 are all versions of gingerbread.
Try a different rom, if it continues, it's probably a hardware problem. My wife's first Incredible rebooted constantly, probably upwards of 2 dozen times a day. We had it replaced and the new one has been fine.
Update: I restored a backup of a previous CWR backup back in July. Shortly after I booted into the restored ROM (it was Stock rooted), it automatically tried to download the OTA software update.
Anyone think that perhaps the phone is automatically DLing the OTA and then rebooting and failing upon doing so? That is the only thing I can come up with at this point. (Though, back when this first started happening, I was on a GB ROM with Sense 3.0, so I wouldn't think the OTA would try to push over that ROM.)
I thought I read some where that other INC2 users were having similiar issues and it was due to the new android market OTA update.
Edit: Nevermind the other thread here in the forum suggests it could be some kind of HTC OTA update that is messing things up.
WorldOfJohnboy said:
Update: I restored a backup of a previous CWR backup back in July. Shortly after I booted into the restored ROM (it was Stock rooted), it automatically tried to download the OTA software update.
Anyone think that perhaps the phone is automatically DLing the OTA and then rebooting and failing upon doing so? That is the only thing I can come up with at this point. (Though, back when this first started happening, I was on a GB ROM with Sense 3.0, so I wouldn't think the OTA would try to push over that ROM.)
Click to expand...
Click to collapse
Weird. OTAs are usually disabled. Did you wipe dalvik/cache and flash a new rom?
klarson said:
Weird. OTAs are usually disabled. Did you wipe dalvik/cache and flash a new rom?
Click to expand...
Click to collapse
I am in the process now, but I have had a GB/Sense 3.0 ROM as well as stock GB Rooted, both have ended up doing the same thing. I think I am going to manually cancel the OTA after flashing a new ROM to see if that will stop it from automatically doing so (if that is the issue).
Pretty sure its the market new market push. I had the same issue, I set the phone to airplane, shut it down before the automated shutdown to retain the airplane mode, then cleared dalvik cache and system cache, and then rebooted. I got some BS message about a failed OTA because no network was detected, told it to cancel, dl'ed the new market APK installed it, not an issue since.
Conduitz said:
Pretty sure its the market new market push. I had the same issue, I set the phone to airplane, shut it down before the automated shutdown to retain the airplane mode, then cleared dalvik cache and system cache, and then rebooted. I got some BS message about a failed OTA because no network was detected, told it to cancel, dl'ed the new market APK installed it, not an issue since.
Click to expand...
Click to collapse
It's not the new market. It has something to do with the OTA's on your phone. Regardless if the OTA was actually downloaded onto your phone or not it's going to fail because the stock recovery is no longer the default recovery which is one of the prerequisites it needs to install.
A wipe is needed to keep this from happening, at least load up the gingersense ROM and that should get rid of the temp OTA file that was downloaded to your phone.
jrizk07: I would agree with you, but this will be the 3rd time I have wiped the phone, the 2nd time loading a Gingerbread based ROM.
I wiped all items twice, and flashed this ROM: [ROM] RMK Gingerbread Sense r1 :: 2.18.605.3 (Rooted/Deodexed/Debloated)
Will let you know the results.
WorldOfJohnboy said:
jrizk07: I would agree with you, but this will be the 3rd time I have wiped the phone, the 2nd time loading a Gingerbread based ROM.
I wiped all items twice, and flashed this ROM: [ROM] RMK Gingerbread Sense r1 :: 2.18.605.3 (Rooted/Deodexed/Debloated)
Will let you know the results.
Click to expand...
Click to collapse
What i'm hoping is that the OTA files are on the phone and will get wiped with a new ROM. However if they're stored on the SD card all the wiping in the world won't help.
I'm not sure where the OTA files are stored and would like someone to verify for certain if that's the case. I'm just speculating right now on where it's stored but I know the market update is done just like the apps not an OTA.
I also know that the OTA will prompt you for the download. You know the whole download and install now or install later deal?
Well, did a wipe of all things (twice) and installed my fresh ROM. This time after installing all my Apps and doing my restores, etc, I went into the Settings under Software Update and did a check new, it says "No New Software Update Available." Also, under status, it just says the Source is Verizon Wireless, the rest are blank. (I believe at one time, all the fields were populated.)
I am holding out hope that this will work for us. Anyone know of a piece of software, etc. that will log all of the phone's operations? I am curious to see if it is trying to auto-update with OTA software updates.
I'm having the same problem. I can't even get it to wipe because when I start in recovery it goes straight to do you want to start update and if I try to start the phone it restarts and I get the exclamation point. Anyone have any ideas? Thanks!
Update
I took the sd card out and was able to boot to recovery and do a wipe. Phone is working normally for now, how would I go about disabling the OTA's so it doesn't happen again?
I can confirm this is being caused by an ota update. Have 2 inc 2's and both locked up. Both running rmk gingersense. Fixed by clearing cache and davlik. Rebooted phone and saw failed ota update error. Renamed otacerts.zip until rom is fixed. Otacerts is located in /system/etc/security.
Hey whats up guys...im really not sure what the problem is but maybe some one has experienced with before..
My droid incredible cannot connect to 3g service...i tried installing all different kinds of roms even the latest gingerbread releases but still nothing.
Some times i allows me to connect to 1x but then you see the "3g" on the top but then it instantly disconnects.
Ive so tried 3 different radio from the NIS business sense release...all failed..
Any ideas?!?!?
Or if i just need the stock radio??
Aloha! I'll see if I can help.
1) Do a nandroid backup in recovery.
2) Wipe data/cache/dalvik cache then flash rmk40's gingersense leak: http://forum.xda-developers.com/showthread.php?t=1087077
3) Reboot and skip set up. Turn on 3G and even test it out for a bit. You should have whatever signal you are used to having return.
4) reboot into recovery and wipe cache, then go into advanced and wipe dalvik cache
5) Restore your latest Nandroid backup
Let me know how this works.
SlimSnoopOS said:
Aloha! I'll see if I can help.
1) Do a nandroid backup in recovery.
2) Wipe data/cache/dalvik cache then flash rmk40's gingersense leak: http://forum.xda-developers.com/showthread.php?t=1087077
3) Reboot and skip set up. Turn on 3G and even test it out for a bit. You should have whatever signal you are used to having return.
4) reboot into recovery and wipe cache, then go into advanced and wipe dalvik cache
5) Restore your latest Nandroid backup
Let me know how this works.
Click to expand...
Click to collapse
How would this fix any 3g issues by flashing a new rom and then returning to you old Rom with a backup? I seem to have an issue changing from 1X to 3g causing me to restart my phone at times to pick up the 3g signal again.
Primarily, the people who noticed this issue were/are folks who try out the various gingersense roms available. I've been a member of XDA since January and haven't noticed users in large numbers have issues with 3G until these roms came out. Whether it's due to there not being an official base or what, idk but many users have had these issues with 3G since the May unofficial gingersense leaks:
1) 3G being present and fully functional then disappearing from the notification bar altogether even while still being enabled in Settings
2) 3G signal dropping down to 1x and not displaying again until you perform a reboot.
I have experienced this issue and know this resolved it. This rom as well as Incubus26jc or JoelZ's stock OTA gingersense leak, for whatever reason, are a solution to resolve the 3g drop issue not the only solution. Incubus26jc, JoelZ, and Nils each have recommended and note this is a fix. My (non-fact and own) answer to you would be I believe since these three roms are the unaltered and "(un)official gingerbread Sense" files, they recorrect the 3G signal that is going awry.
Try it and let me know how this works. You don't stand to lose anything except a few minutes haha
This solution fixed my problem.
Dang it actually worked. Wish i had done this a while back. Thanks for the simple fix.
Not a problem, I'm just thankful there's a fix.
Accidentally worked for me too
I had the same problem on CM7. Flashing back to my stock 2.2 Android backup fixed the problem. Flashing back to CM7 and OMGB caused the problem to return. I am on the leaked ota now, I have flashed the gingerbread radio, and I am having no 3g issues. I wish that I had found this thread earlier.
Had this exact issue with synergy rls1 and was also told to flash the rom above to fix it. It worked for awile but then 3g issues would return again, even on non sense 3 roms and even on my old virtuous nandroid. If just flashing the above rom works for you and permanetly fixes it thats cool, but if your like me the only fix is to revert back to compleet stock and i mean compleet stock rom radio recovery boot img everything the only thing not stock would be you still want to have s-off as a matter of fact make sure to check you are s-off before going stock. Once stock you need to do a factory reset from the settings menu. What this does is it compleetley wipes your phone back to stock including wiping vzw programing, wich is the key to fixing 3g. Once your phone reboots from the factory reset you will be prompted to dial *228 option 1 to reprogram your phone. Once reprogramed your 3g will be fixed. From there flash clock work or amon ra recovery and then restore your favorite nandroid or install a new rom. I personaly would stay away from sense 3 roms as after fixing mine with the above steps i not thinking installed another sense 3 rom and broke 3g again making me fix it all over again. I have stayed away from sense 3 and havent had any problems since. Note if you have a compleete stock nandroid you can just flash that then flash stock recovery and radio do the factory reset .....
Sent from my ADR6300 using XDA Premium App
Well this is why Android is all about choice.
Well, I tried to install rmk's rom and that didn't work. I also tried to go back to stock with the RUU and the PB31IMG.zip file to do a factory reset, but that didn't work either. Are there any other suggestions that I can try?
Devildog8791 said:
Well, I tried to install rmk's rom and that didn't work. I also tried to go back to stock with the RUU and the PB31IMG.zip file to do a factory reset, but that didn't work either. Are there any other suggestions that I can try?
Click to expand...
Click to collapse
If an ruu and a factory reset with new programing didn't fix your 3g issue its possibly hardware related. Can you still connect at 1x speed?
cmlusco said:
If an ruu and a factory reset with new programing didn't fix your 3g issue its possibly hardware related. Can you still connect at 1x speed?
Click to expand...
Click to collapse
No, I called Big Red and they're sending out a replacement phone. I'm one of them weird people that don't use their phone as a phone too much, but I realized that I couldn't make or receive phone calls or texts either. We got that issue fixed, but they couldn't get the data working.
I guess the world of root is gone for me since it will probably come with Gingerbread on it already. Oh well, I'm probably going to buy a new phone in December anyway, so I'll have a new Dinc to put away in the drawer.
Devildog8791 said:
No, I called Big Red and they're sending out a replacement phone. I'm one of them weird people that don't use their phone as a phone too much, but I realized that I couldn't make or receive phone calls or texts either. We got that issue fixed, but they couldn't get the data working.
I guess the world of root is gone for me since it will probably come with Gingerbread on it already. Oh well, I'm probably going to buy a new phone in December anyway, so I'll have a new Dinc to put away in the drawer.
Click to expand...
Click to collapse
Root may still be possible, check out this thread http://forum.xda-developers.com/showthread.php?t=1306400. Mabey you will get lucky and they will be out of incredibles and they will send you an incredible 2. Ive heard it happens .
cmlusco said:
Maybe you will get lucky and they will be out of incredibles and they will send you an incredible 2. Ive heard it happens .
Click to expand...
Click to collapse
Looks like they are sending me a Rezound...JK. Actually, it looks like they are sending me an OG Incredible. I'll know more tomorrow and will let you know.
Thanks for the link to the root method. I have been studying it and I have all the files downloaded just waiting.
Edit: I did get an OG Incredible, but it came with Froyo on it. I should be good to go as far as rooting it goes. I think that I have an SLCD model though which sucks.
i have tried following the instructions on another thread i found here about trying to fix a 3g issue with the incredible and new roms, but i have not been able to get my 3g back. currently i am running a stock ruu. my system info reads s follows...
Android ver
2.2
baseband ver
2.15.00.07.28
Kernel ver
2.6.32.15-gb7b01d1
htc-kernel @and18-2 #1
build number
3.21.605.1 CL231334 release-keys
software number
3.21.05.1
ClockworkMod Recovery v2.5.1.2
i have rooted again since i ruu'd and have more or less just lived with it while trying to figure it out on my own. it seems to be random sometimes i will be able to look stuff up other times not so much. i know it isn't my service area as i have a work blackberry on verizon and that is fine. does anyone think this could be a software issue or does this sound like hardware. i am really hoping it is software as i have had my incredible since launch and really don't want to get it replaced, lol. i appreciate any help you guys can give me.
could it be the radio i have flashed? i dont know a whole lot about them so i havnt done a whole lot of troubleshooting there. can i go backwards with radio flashing? i just want to be sure before i try that as to not brick.
Does your 3g disappear or drop down to 1x often? You say you tried another thread, could you link me to it so I know what you did OR could you explain what steps you have done to alleviate this?
The typical solution is to flash a stock rom then boot into the rom itself and leave it running for a minute or two, even make a call and check 3g to make sure it's working. Then restore your backup rom and enjoy life. I'll provide you a stock rom link with steps to follow in a few minutes.
found it. i followed this thread and reverted back to stock. still hasn't helped my 3g woes. could having the wrong radio cause these problems?
http://forum.xda-developers.com/showthread.php?t=817487&highlight=3g+fix
***Edit i generally don't even have the 3G symbol in my notification bar or if it is there like now it just wont connect sometimes. in settings it says mobile network is connected as well
undeclared said:
found it. i followed this thread and reverted back to stock. still hasn't helped my 3g woes. could having the wrong radio cause these problems?
http://forum.xda-developers.com/showthread.php?t=817487&highlight=3g+fix
***Edit i generally don't even have the 3G symbol in my notification bar or if it is there like now it just wont connect sometimes. in settings it says mobile network is connected as well
Click to expand...
Click to collapse
Aight, the rom link in my instructions is this one from RMK40. His link has since gone down. It is the first leaked OTA from last May prior to the flood of gingersense roms.
1. Boot into recovery and perform a Nandroid
2. In recovery, do a Factory reset/Wipe Cache/Wipe Dalvik Cache
3. Flash this
4. Boot into the rom and make a test call. Also check your 3g connection and see if it works. You can run it for ten minutes or an hour if you want to see if the connection fails, although it shouldn't.
5. Reboot into recovery and do Nandroid restore
6. Enjoy.
Post back with your results.
Edit: Here is a reference thread from where I obtained my instructions. I believe you are in the same scenario.
http://forum.xda-developers.com/showthread.php?t=1229732
i did a back up, wiped and flashed the rom, twice, both times i got boot loops :-/
maybe it's my radio?
undeclared said:
i did a back up, wiped and flashed the rom, twice, both times i got boot loops :-/
maybe it's my radio?
Click to expand...
Click to collapse
I would flash the froyo ruu thru hboot and then reboot. Then go back to hboot and select factory data reset, or boot to the os and go to Menu Settings Sd & phone storage and select factory data reset. Let it do its thing and then reboot. Once it boots up do the ota programing and your 3g should be fixed. Then you can flash cwm recovery thru hboot, and the su binary thru recovery and you will be rooted and ready to flash roms again. I have had this happen several times when using sense 3/3.5 roms ported from sprint phones.
Also that radio is old, from froyo, but that shouldt be the issue. If a factory reset dosent fix it i guess it wouldnt hurt to try updating to the newest radio. Im 95% positive factory reseting the phone from hboot or the settingd menu will fix your 3g. You have to have the stock recovery for the reset to work, that is why you need to ruu again, unless you are already on the stock recovery.
thanks i think this is working i just got done with programming and now i have 3g! gonna stress test it till later tonight i think and then it is off to flashing a new rom! any rom either of you suggest that shouldn't give me these 3g issues?
again thanks so much for your help
undeclared said:
thanks i think this is working i just got done with programming and now i have 3g! gonna stress test it till later tonight i think and then it is off to flashing a new rom! any rom either of you suggest that shouldn't give me these 3g issues?
again thanks so much for your help
Click to expand...
Click to collapse
It usually happens to me on roms ported from sprint phones, mostly after doing a *228. I would highly advise not to do a *228 on a sprint rom. If you want to be extra cautious i wold just stay away from sprint ported roms all together.