Hey, complicated story.
I have been running a rooted + SOFF DInc for 6 months without problems (or no problem big enough that a factory reset IN CWM Recovery couldn't fix.
Until today. I was unable to send/receive MMS, so I followed a threat which told me to delete /data/data/android.telephony/database ... or something like that. So I did, booted back up, and only got 1x. Dang, I said to myself, better reflash C7, and still, 1x. Dang! I said again, and flashed OMFGB, again, to no avail...just 1x.
I *228 option 1 it, and reboot into recovery to fix perms, and nothing boots. NOTHING! Just infinite white HTC Incredible screen. So I try flashing C7 nightly, OMFGB, restoring Nandroids, nothing ... except for MIUI 6.17 and C7.0.3, which both got 3G! But...none of their GAPPS worked (I flashed them with known good GAPPS).
So I pull the battery, give it 5 minutes, and while in C7.0.3, *228 1 and 2. Reboot and restore from my C7.0.3 (with my old data on it, the one aforementioned was clean), and it works....weird. I update apps, run fix permissions (running really slowly), and it reboots, but now 3G is gone! I also cannot uninstall apps....
What is wrong with my phone? Why is 3G dropping all of a sudden??
It has to do with either that bogus tip I had to delete /data/data/com.android.telephony/database or whatever (but shouldn't that be fixed by restoring?), or something to do with my hardware coinciding (but I doubt that very much).
Help!!!!!
EDIT: File I deleted:
/data/data/com.android.providers.telephony/databases/telephony.db
Flash the ruu from dougpiston.com. It will reset your stock, but it will most likely fix your problem because it's definitely software related.
Sent from my HTC Incredible
Well, I had a stock Nandroid already. I did restore that, and 3G did work. The problem was, though, that when I restored a once 3G-ified CM7 (and nightly), 1x would show up. Something MUST have changed, but I still fail to see why it perpetually changes nandroids.......
Now, it looks like *228 on any ROM is necessary. Also, fixing permissions breaks 3G. This is NOT good. I still need help. Any takers?
Is the file you deleted present in your backups? Like the other poster said, it might be worth it to try flashing the RUU.
Well, I am in an interesting situation of having no internet ATM and only 1x...but:
While in stock, I did *228, and 3G was restored. I then restored custom CM7 from CWM, and ... 3G, as before. I am just going to chill out on crackflashing, and take it slow.
BTW: How do you look at restore images? I tried in Ubuntu and Snow Leopard, but I could not open the *.img.
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....^_~
I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?
Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk
I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.
You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk
Alright, tried wiping the Dalvik Cache after flashing, problem still persists.
You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache
Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...
Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...
Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?
If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App
Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?
EDIT: Problem Solved
Downloaded Stock Sense 2.2 from here, flashed into that, Reset Data Connection in EPST (Like Here), rebooted and flashed back to CM7. Simple as that!
I realize this may be a bit of repeat thread, But I haven't really got an answer yet.
For reference: I'm running Cm7
Sometime during the day last Thursday, I lost the ability to receive texts. I can send texts, as well as make/receive calls, and data works fine as well. I just can't send them.
Things I've tried include:
Flashing to Stock Sense 2.3
Updating PRL/Profile
Manually installing Radio/PRL/Profile updates
Flashing to a fresh CM7 Install
I also feel like I should add that I tried to open EPST to reset data, but when I enter the code(##3282#) in Phone I get nothing.
Any help would be appreciated, and I'll be on until late tonight as to not keep responders waiting. Thanks.
Go to stock rooted 2.2 or MikG or a custom ROM with the old EPST, the new EPST features less. I just do it on stock 2.2 to avoid any problems when doing the restore. My radios are working, did you flash them individually?
Sent from my PC36100 using XDA Premium App
Okay
Downloading MikG right now, going to give that a try.
And I think that may be part of my problem, I just can't get the radio to update. I've attempted to install them as a combo, and separately in both ClockworkMod and Amon_RA several times. I never get any error messages, it just installs, and tells me to reboot, but nothing ever changes.
That's why I'm going to try to Reset Data in EPST. I had heard elsewhere that my MSL doesn't match what Sprint has on file, or something like that, and that resetting data should fix this.
Anyway, Thanks a lot, I'll be back in 10-15 minutes with results!
Partial Success
As soon as Stock 2.2 booted up and got to setup, the texts started pouring in. Not sure what caused this, but it seems at this point like a Gingerbread issue. For good measure I opened EPST and did a data reset and updated PRL/Profile. I'm about to flash back to CM7 and see if the changes carried over.
It worked! It was that simple all along! Thank you! Just sent myself a text via email that I received on CM7!
foxtrotftw said:
Downloading MikG right now, going to give that a try.
And I think that may be part of my problem, I just can't get the radio to update. I've attempted to install them as a combo, and separately in both ClockworkMod and Amon_RA several times. I never get any error messages, it just installs, and tells me to reboot, but nothing ever changes.
That's why I'm going to try to Reset Data in EPST. I had heard elsewhere that my MSL doesn't match what Sprint has on file, or something like that, and that resetting data should fix this.
Anyway, Thanks a lot, I'll be back in 10-15 minutes with results!
Click to expand...
Click to collapse
If you rebooted in between installing each one, the radios should've updated. You might not notice any difference, but it should work. Glad to hear that your problem is solved!
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've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Re-Install your Rom, first.
Update your Radios.
Simple.
alexdz said:
I've recently been trying out ICS ROMs for the Evo, but decided to return to Gingerbread because ICS seems to mess up GPS accuracy, no matter which ROM I try. I'm now on my third different Gingerbread ROM today because I've run into a problem I've never seen before. When I first install I'm able to turn on WiFi and connect to my router no problem, but sometime later, the phone refuses to connect. In wireless settings you can turn on WiFi, and it will think about it for awhile, and then just stop trying. Sometimes I get a com.android.settings not responding message, but not always. Anyway, I tried searching for this but couldn't really even figure out how to word it. This sound familiar to anyone? Thanks.
Click to expand...
Click to collapse
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
vdude8 said:
Try what Nickitt said first, and if that doesn't work, try this out --
Go into recovery, clear boot, dalvik, and do a factory reset. Then, install a ROM of your choice.
For some odd reason, I started having similar WiFi issues on my EVO after installing the Mason kernel, where the WiFi would indicate that it's on for a few seconds, and then move back to the off position (or, it would stay permanently in the state where it seems like it's turning on). Reflashing the ROM by itself didn't work, but clearing boot somehow did the trick.
Go figure.
Click to expand...
Click to collapse
I failed to mention initially, but I did try updating the radios as well. Regardless, I'm not having the problem anymore, and it's possible that there was simply something in my Titanium backups (done while on ICS) that it didn't like. I started thinking back on the timing and realized that the issue was showing up only after I went through the batch restore process, so this time I only restored a few apps that had data I didn't want to lose, and nothing else. So far so good.
Except of course that I'm now having a new problem that may be associated with a2sd, but I'll post that in that Deck's Reloaded thread...
Thanks!
I had a lot of force closes after restoring ICS backups in GB. Don't think the backups are backwards compatable...not all the time anyway.