Related
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?
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.
Hello,
My Droid Incredible can not connect to 3G nor can it connect to 1X. Luckily, I can still receive calls and sms. A couple of days ago, I upgraded from CM 7.0.2 or 7.0.3 to CM 7.1 RC1. A couple of hours later, I installed Synergy, wiping the cache and dalvik and data in the process. After a day of having that rom restart every 30 minutes or so, I restored the backup I had made of CM 7.1, without wiping the cache, dalvik, and data. I then noticed that I could not connect to 3G and to 1X. I thought I might just be in a dead zone, even though I have never had connectivity issues, so I didn't worry about it. Then, I noticed the same thing at my work, and anywhere I went no connectivity. I tried flashing a different kernel, Chad's incredikernel, 2.6.38.8, but that didn't work either. Any suggestions?
You need to install either liberation or the rooted leaked ota, set it up, then do *228 option 1, reboot *228 option 2. Then go back and reinstall fresh your cm7. I would fully wipe both installs, which means going to mounts and storage and wiping boot, dara, system, and cache. You have remnents of synergy on your phone. You need a real good wipe.
Thanks for the quick reply. I'm going to try that right now.
Let me know if that works. You may want to download vr superwipe.zip and keep it on your sd card to flash right before the rom, its what i use everytime. If ive helped you please hit the thanks button! Gracias
I only installed up to the root leaked ota and it works fine now. I actually think that the phone is faster with the ota than any other rom I've tried so I'm going to stay with that at least until I get home from my work.
The ota is smoking, it is what i use also.
If ive helped you, please hit the damn thanks button!
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.
Hello,
I have owned a Sprint Galaxy S III since August of 2012 and have been using it pretty much flawlessly until this week.
To give some history, I rooted it once it became a common thing to do and have CWM-based Recovery v5.5.0.4.
I have loaded many different roms - cyanogenmods, m.o.a.r., wicked, miui to try out and many others and have never had an issue.
I recently upgraded to M.O.A.R. v 6.0 at home and everything seemed great - loaded apps, settings, etc. The next day on the way to work, the phone restarted by itself. I thought was strange but chalked it up to a new rom issue. When I got to work, the frequency of the issue increased to the point that the phone was no longer usable as it would just continue to restart, boot, etc.
Restoring the rom I previously had did nothing to help the issue.
I looked up online at possibilities and came across the SD card issue. I replaced it, but still occurs. I've tried a few different roms and no matter what, it seems to continuously boot and restart based on certain locations that I am in or am passing through.
Today, I turned off 4G LTE as preferred mobile network and it seemed to keep the phone on. I have not done extensive testing, but could this be an issue? I am able to use 4G LTE at home with no problem as well as other areas, but it seems that once I am in or pass through certain locations, that it is crashing my phone? Maybe the GPS?
Are there any tips or suggestions of what I can do or try? I am at a loss as to how to fix this when it has not been an issue up until this week after flashing to MOAR v6.0. I've wiped data, cache, dalvik, many times and retried but still is happening.
Any feedback would be much appreciated.
At first it sounded like sudden death syndrome (a power button failure) but when you said turning off 4G fixed it that is very weird. Have you tried asking in the M.O.A.R thread?
------------------------
Sprint Galaxy S3
Stock - Whiplashh Rom - MIUI - Wicked Sensations
Sprint Evo 4G "OG"
Stock - Cyanogenmod 7 - MIUI - Swagged Out Stock
Hit That "Thanks" Button if I Helped You!
Could be your kernel. Or any kernel tweaks you are using
joebeem said:
Hello,
I have owned a Sprint Galaxy S III since August of 2012 and have been using it pretty much flawlessly until this week.
To give some history, I rooted it once it became a common thing to do and have CWM-based Recovery v5.5.0.4.
I have loaded many different roms - cyanogenmods, m.o.a.r., wicked, miui to try out and many others and have never had an issue.
I recently upgraded to M.O.A.R. v 6.0 at home and everything seemed great - loaded apps, settings, etc. The next day on the way to work, the phone restarted by itself. I thought was strange but chalked it up to a new rom issue. When I got to work, the frequency of the issue increased to the point that the phone was no longer usable as it would just continue to restart, boot, etc.
Restoring the rom I previously had did nothing to help the issue.
I looked up online at possibilities and came across the SD card issue. I replaced it, but still occurs. I've tried a few different roms and no matter what, it seems to continuously boot and restart based on certain locations that I am in or am passing through.
Today, I turned off 4G LTE as preferred mobile network and it seemed to keep the phone on. I have not done extensive testing, but could this be an issue? I am able to use 4G LTE at home with no problem as well as other areas, but it seems that once I am in or pass through certain locations, that it is crashing my phone? Maybe the GPS?
Are there any tips or suggestions of what I can do or try? I am at a loss as to how to fix this when it has not been an issue up until this week after flashing to MOAR v6.0. I've wiped data, cache, dalvik, many times and retried but still is happening.
Any feedback would be much appreciated.
Click to expand...
Click to collapse
Are you restoring any System Data ? I would suggest doing a Clean install. Meaning a FULL Wipe : System - Data - Dalvik - Dalvik Cache - Factory Reset ( 3x's ) . I also like to wipe Internal Storage. But that's up to you. Then Flash the Rom, and let it Boot. Do not load anything, or tweak anything. Just leave the device alone for the first 5min. Then test it to be sure everything is working correctly before loading apps, or doing any settings.
Just to update...
I clean installed MOAR 6 again - this time I upgraded CWM to latest version. I clean wiped data/cache, cache, dalvik about 3 or 4 times. Once it reinstalled, I noticed the data wasn't working at all so I did that ##72786# (forgot numbers off top of head) that reactivated phone. The data came back and I thought this was going to solve all the issues...keep in mind I did all this in the evening from home last night.
On the way to work this morning, sure enough once I got in the vicinity of work, phone restarted a few times. I was quick enough to catch it one time to turn preferred mobile networks to 3G first and disable 4G... my phone has not restarted for the rest of the day.
It's great that it seems the issue is isolated to 4G, but I don't understand how it can be fine in some areas and not in others. For instance, at home, 4G works just fine.
I think I will try to go back to stock or try an aosp rom. I've seen in some places talk of MB1 and MD4...is there a way to tell which I have or is that related to anything?
prboy1969 said:
Are you restoring any System Data ? I would suggest doing a Clean install. Meaning a FULL Wipe : System - Data - Dalvik - Dalvik Cache - Factory Reset ( 3x's ) . I also like to wipe Internal Storage. But that's up to you. Then Flash the Rom, and let it Boot. Do not load anything, or tweak anything. Just leave the device alone for the first 5min. Then test it to be sure everything is working correctly before loading apps, or doing any settings.
Click to expand...
Click to collapse
Actually, yes - I have been putting my gmail account information in and it has been syncing the apps. It's just so odd because I haven't had issues for over a year and I don't recall installing any new stuff.
well, now it happened at home when turning on 4g... damn.
joebeem said:
Just to update...
I clean installed MOAR 6 again - this time I upgraded CWM to latest version. I clean wiped data/cache, cache, dalvik about 3 or 4 times. Once it reinstalled, I noticed the data wasn't working at all so I did that ##72786# (forgot numbers off top of head) that reactivated phone. The data came back and I thought this was going to solve all the issues...keep in mind I did all this in the evening from home last night.
On the way to work this morning, sure enough once I got in the vicinity of work, phone restarted a few times. I was quick enough to catch it one time to turn preferred mobile networks to 3G first and disable 4G... my phone has not restarted for the rest of the day.
It's great that it seems the issue is isolated to 4G, but I don't understand how it can be fine in some areas and not in others. For instance, at home, 4G works just fine.
I think I will try to go back to stock or try an aosp rom. I've seen in some places talk of MB1 and MD4...is there a way to tell which I have or is that related to anything?
Click to expand...
Click to collapse
joebeem said:
Actually, yes - I have been putting my gmail account information in and it has been syncing the apps. It's just so odd because I haven't had issues for over a year and I don't recall installing any new stuff.
Click to expand...
Click to collapse
You did not mention wiping system. If you do not Wipe system, and also Factory Reset then it's really not a Clean install. I would still suggest a FULL Wipe, and Clean install. Then run the Device for a while without adding anything. See how it performs.
I ended up just flashing this - http://forum.xda-developers.com/showthread.php?t=1904099 to stock with flash reset.
I am not sure about wiping system - I always just follow the steps of the rom wipe data/cache/dalvik. I will have to research on how to wipe system.
If you never wipe system you are definitely going to run into problems.
joebeem said:
I ended up just flashing this - http://forum.xda-developers.com/showthread.php?t=1904099 to stock with flash reset.
I am not sure about wiping system - I always just follow the steps of the rom wipe data/cache/dalvik. I will have to research on how to wipe system.
Click to expand...
Click to collapse
You just do it in Recovery before you flash. If you look at my Sig on a PC / Internet Mode there is a link on how to do Full Wipe before flashing a Rom.
TEAM MiK
MikROMs Since 3/13/11