Uh oh - Droid Incredible Q&A, Help & Troubleshooting

Alright. My Inc is having some problems. Here are some facts
Bought on December 23, 2010
Rooted it somewhere in January
Ran CM6 till CM7 came out
Here's what's was going down after I flashed to CM7
Flash CM7
Every 15 minutes my google maps app will randomly crash. No matter what I'm doing a "GOOGLE MAPS HAS STOPPED RESPONDING" sign will appear.
Random reboots in the middle of doing nothing
Re-flashed to stock, then back to CM7 and everything seemed okay... until a few days ago
Suddenly while browsing the internet EVERYTHING CRASHES. EVERYTHING.
The browser, music, messaging, screenshot it, even google frameworks.
wtfman.jpg
reboot my phone, this occurs again after a few hours.
Next day it happens again. Now, my phone got stuck in a boot-loop
So I flash back to CM6. Now here's my phone's symptoms.
Home button won't work. It vibrates on press, but doesn't do anything.
Search button won't work
No lock screen will ever come up. Ever. It's set, but it never appears.
I cannot receive calls. People will call me, and it will immediately show up in my call log, but the answer screen simply doesn't show up.
What did I do wrong? How do I fix this?
Alternatively, how can I flash back to stock and make it look like I never rooted it? I believe I'm still within my warranty.

What hboot and radio are u on? I know if your not using a gingerbread radio with cm7 it likes to go all wonky at times. I would wipe everything try a fresh install of cm7 and flash a gingerbread radio as well.
Sent from my Droid Incredible

sounds like you didn't wipe everything correctly. Did you wipe cache, devcache (probably spelled that wrong), data, datadata? Also did you restore apps through TI backup or any other backup app?

jackbtha1 said:
What hboot and radio are u on? I know if your not using a gingerbread radio with cm7 it likes to go all wonky at times. I would wipe everything try a fresh install of cm7 and flash a gingerbread radio as well.
Sent from my Droid Incredible
Click to expand...
Click to collapse
hboot 0.92.0000
radio-2.15.00.07.28
POQbum said:
sounds like you didn't wipe everything correctly. Did you wipe cache, devcache (probably spelled that wrong), data, datadata? Also did you restore apps through TI backup or any other backup app?
Click to expand...
Click to collapse
I did not wipe errything the first few flashes. But my last flash I wiped my cache, data, etc.

Try flashing the 7.07 Gingerbread radio, get it here http://pvillecomp.com/?page_id=18 and see if that helps.

Are there any alternatives to that?

Try flashing another ROM and see what happens. Make sure you wipe cache, dalvik, format system, and boot. Nandroid before you attempt that. Give Joelz Prime Xl 3d a try.
Sent from my HTC Droid Incredible using XDA App

First update that old Froyo radio with the new stock not leaked and totally safe because Verizon officially released it radio that jackbtha1 suggested.
Second, boot into recovery and run "fix permissions." That option always helps me when my phone decides to FC everything. It has helped me so that I run it after every rom flash now

Related

[Q] Weird problem installing custom ROMs

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?

[Q] Anybody else having trouble restoring apps on CM7 nightlies?

I have an Evo (003 Hardware) and while switching ROMs, at least twice now, I've had trouble restoring some apps using Titanium Backup. The weird thing is, I'ts only some apps, that are having the restore problem, while others seem to be restored, but without their settings saved. (Google Listen is an example of the former, while AdwEX is of the later.
I've verified the backups themselves, and they come back without errors, I've also tried flashing different ROMs like Myn's new Warm Z, MIUI, and Koni's Elite II. Those have no trouble restoring. Seems the problem is confined to the nightlies, as I'd installed RC1 before without issues.
Anybody have an idea what's wrong?
When re-flashing the roms, try a clean install, and also flashing the latest gapps. Not flashing them has been seen lately to cause a few apps not restoring, or some just missing completely. Best to do it in 2 recovery sessions, backup, flash rom, reboot, flash gapps, reboot.
teh roxxorz said:
When re-flashing the roms, try a clean install, and also flashing the latest gapps. Not flashing them has been seen lately to cause a few apps not restoring, or some just missing completely. Best to do it in 2 recovery sessions, backup, flash rom, reboot, flash gapps, reboot.
Click to expand...
Click to collapse
I always do a fresh install. Wipe data, cache and Dalvik, plus flash Calkulin's Format All.
I haven't tried flashing ROM and gapps in different sessions, as that brought trouble pre-rc1, I'll try that now, though.
Well I practice the 2 recovery session as a standard, sometimes it works in 1 session, but when it doesn't the 2 session step bring me no problems; but let me know what happens.
turns out, that wasn't the problem. Two-session flashing didn't bring any issues, which I was glad to see (although it did switch the wallpaper, that's just weird). What did help was this post from the rc1 thread http://forum.xda-developers.com/showpost.php?p=11722822&postcount=1603, where this exact problem is described, but I happened to miss it while searching somehow. anyways, it finally restored the apps, but not their data. I guess that's better than nothing, but again, just plain annoying.
Ah I see. Well now backup the apps and data and you should be set now.

[Q] Rooted Inc2 Keeps rebooting

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.

[Q] Can't connect to 3G/1X

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!

Cannot connect to 3g

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.

Categories

Resources