Any thoughts? - Droid Incredible Q&A, Help & Troubleshooting

So I rooted my DInc and installed Virtuous 3.1.0 and switches to the Virtuous custom kernel.
Problem is, I tried to install chars kernel and just kept getting a reboot loop, no matter what version I tried. So then I restored and tried to instell SkyRaider from ROM Manager... but when I went rebooted and tried to setup my phone, it would just reboot the phone back to the setup. I did do a wipe before installing SkyRaider and chars kernel. Any thoughts on what's wrong?
Sent from my ADR6300 using XDA App

Did you also wipe dalvik cache too? It's under advanced in recovery... I do that before each kernel install without issue.

Common mistake I do believe don't "wipe" when installing a kernel just wide cache partition and advanced/ dalvik I hope that helps. I know a few people were doing full wipes when installing kernels
Sent from my Incredible using XDA App

Thank you for the help! =D
Got chads kernel installed with out any trouble this time. Gonna give SkyRaider ROM a try now.
Update - Got SkyRaider 3.5 installed, but I don't like the default lock screen, and no matter what I do, I can't change it. I've tried installing both lock screens in ROM Manager (didn't work), tried deleting the HtcLockScreen.apk in root explorer (didn't work), and tried to change the lock screen in both the terminal emulator and through adb shell - lockscreen in the sdk. Any one have any ideas on how to get rid of the default lock screen?

Related

[Q] Cannot run any Kernel besides HTC Stock?!

Hey guys, I feel like I have ran out of options on this problem so I figured I would post and see what you guys think. I am currently running Myn's RLS 2 and ever since I flashed the first version I have not been able to get past running the HTC Stock Kernel. If I flash any other Kernel my phone runs for a bit and then will freeze up and randomly reboot. Even during reboots sometimes it will reboot again. Do I need to be running SetCpu at all to help with this, or is it another problem? Any suggestions would be greatly appreciated. Thank You.
Depends on which kernel you want to run ... some play better with certain roms. I notice that you mention Netarchy's kernel in your signature ... have you tried his universal 4.1.9? Anyway ... whenever I install a different kernel, here's the procedure I use ...
Boot into recovery (I use RA) ... wipe cache and dalvik cache twice each ... flash the kernel ... wipe cache and dalvik again ... reboot.

[Q] can't run any new rom, hangs at white htc incredible screen on boot

I rooted the incredible using unrevoked, no problem.
Installed and ran root apps, no problem, backed up everything using titanium backup and rom manager (nandroid) and so forth, installed cw recovery 3.0.0.8.
When I install the skyraider 4 rom from rom manager, it reboots and installs, but then when it reboots again it hangs at the white htc incredible screen (and I've let it wait as long as a half an hour). I have to take out the battery to be able to reboot it.
I can boot back to recovery and then re-install and boot back to the stock rooted rom just fine. But I can't get a new rom installed and working.
I've looked at previous threads about this problem:
http://forum.xda-developers.com/showthread.php?t=1038402
http://forum.xda-developers.com/showthread.php?t=1023358
http://forum.xda-developers.com/showthread.php?t=991953
http://forum.xda-developers.com/showthread.php?t=739646
http://forum.xda-developers.com/showthread.php?t=620621
and several other threads on other sites.
The only suggestions to come out of those, other that starting over from scratch (which I've done multiple times now), were to reformat the sd card, which I've also done, and to downgrade to cm recovery 2.5.1.2. Rom manager only shows versions as old as 3.0.0.5. I have put the PB31IMG.zip file on the sd card and loaded that before to help recover but I don't see how that helps with installing a new rom.
Any other suggestions? The main reason I even need a new rom is because bluetooth doesn't work in the stock rom (known issue: http://community.htc.com/na/htc-forums/android/f/91/p/2336/8570.aspx )
It sounds like you are not wiping cache and Davlik (in advanced). The constant reboot of the white screen is a classic symptom of not performing a cache and Davlik wipe
patsfan1130 said:
It sounds like you are not wiping cache and Davlik (in advanced). The constant reboot of the white screen is a classic symptom of not performing a cache and Davlik wipe
Click to expand...
Click to collapse
appreciate your help, yeah I've been doing that everytime in rom manager. I tried it several times manually in cm recovery, too, and still the white screen.
I'll just see if verizon can exchange it, or else I'll sell it for another phone with working bluetooth.
Might try reverting to the 2.5.1.2 recovery as I've heard the 3.x.x.x ones don't wipe consistently.
Sent from my ADR6300 using XDA App
when im change roms im not use Rom manager,im just use rom manager for Backup Current Rom.I use quickboot for install a new Rom
1.open quickboot
2.choose recovery
3.wipe date/factory reset
4.drop down to yes delete all user data
5.go back to the first panel and choose advance(5 and 6 optional)
6.and then wipe Dalvik Cache
7.install zip from sd card.
8.good lock,(xdadevelopers and me are not responsable for any damage in your cell.)
Im running the skyrider 4.0 and is a wonderfull Rom,highly recommended.
when im change roms im not use Rom manager,im just use rom manager for Backup Current Rom.I use quickboot for install a new Rom
1.open quickboot
2.choose recovery
3.wipe date/factory reset
4.drop down to yes delete all user data
5.go back to the first panel and choose advance(5 and 6 optional)
6.and then wipe Dalvik Cache
7.install zip from sd card.
8.good lock,(xdadevelopers and me are not responsable for any damage in your cell.)
Im running the skyrider 4.0 and is a wonderfull Rom,highly recommended.
k_nivesout said:
Might try reverting to the 2.5.1.2 recovery as I've heard the 3.x.x.x ones don't wipe consistently.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
.
There is a flash of CWM 2.5 that temporarily lets you use that to flash the rom then when you reboot it will revert back. Try that.

[Q] MAJOR Problems, Error occurred while attempting to run privileged commands

Alrighty....seems as if I have some MAJOR problems here.
Background, I have a DInc 1, rooted using Unrevoked, and the only ROM I put on it was Cyanogen Mod 7. S-off is all set up, and there is the Superuser features have worked fine 75% of the time. Everything was up and running quite well for some time. Then this weekend, I installed a few different DWLauncher themes, and things still seemed to be ok. Sunday night, I installed Words with Friends, and that is when all hell broke lose.
Now, I really can't run anything. Apps are force closing all over the place, Google framework stuff is force closing and when I even try to report a problem, even that force closes. So, I uninstalled the Words with Friends App, and changed themes, thinking those were the culprits, but seems like the damage has been done. Nothing really works and everything is force closing.
Went into the ROM Manager (premium) and did a fix permissions and it gave me the "error occurred while attempting to run privileged commands" error. I ran it a handful of times, and it worked once last night. I thought it would have cleared a bunch of stuff up, but it didn't really help at all. Kept the phone off all night, and when I got to work this morning, I started working on it. Fine, time to ditch everything and start from scratch. So, downloaded a different ROM (Cyanogen MOD nightly), and also tried a few others, which it let me download, but when I click to install, no matter what options I click from wiping cache, wiping Dalvik, backing up or anything, it always gave me the same error. So, back to ROM manager, trying to boot in recovery, error, boot into CM recovery, error.
Edit, as I finished typing this, I tried to install the nightly one more time, but did not click wipe Dalvik, and it is installing things. As soon as everything installed, it was more of the same, apps crashing all over the place. I was able to go into ROM manager and boot into CM recovery, which is now allowing me to fix problems. So, it seems as if was working properly, for the first couple of hours, but around 10 pm, roughly 12 hours after the install, app crash-o-rama again. Also, from ROM Manager, when I try to flash ClockworkMod Recovery, it force closes.
So, I am kinda stuck. No matter what ROM I download, it gives me the same error. At this point, I don't care what ROM is on there (I do have preferences), but I just want the phone working again. Is there anyway to force a wipe and install?
Thanks in advance
You can, instead of installing the ROM through ROM Manager, just download the ROM zip file, put it on your SD card, do the full wipe/factory reset/dalvik in Recovery, then flash the ROM zip from there.
I've had issues trying to install a ROM that's downloaded from ROM Manager.
Here's what I do before flashing the ROM zip file:
Wipe user data/factory reset
Wipe dalvik (under the Advanced menu in Recovery)
Wipe /boot, /system, /data, /cache (under Mounts and Storage in Recovery)
THEN flash the ROM zip file.
Hope this helps!
Thanks for the reply. It has been a long day of working on this phone. I have to pull my battery so many times, almost as many times as my blackberry.
I have installed about 4 different ROM versions until it would allow me to clean everything up, Dalvik and system cache, but as of now, everything is back up and running.....for now. Let's hope it stays that way.
If it doesn't, it seem like I will go the way of skipping the ROM Manager and just boot straight into recovery and do it all that way.
Thanks again
ROM manager isn't exactly reliable software. Most devs recommend a clockwork flash rather than ROM manager. Don't know why there are so many issues with it, but its pretty much not worth using to flash ROMs. It's fix permission feature is exactly the same routine that clockwork uses though. Updating the superuser might be something to try too.
ROM manager only wipes once and cwm3 doesn't wipe properly.... I've always read that you should wipe data cache and dalvik 3 times each before installing a new ROM wich is why you should use cwm.
Sent from my Synergy Rom using XDA App
:facepalm:
Re: multiple wipes
http://cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache
k_nivesout said:
:facepalm:
Re: multiple wipes
http://cvpcs.org/blog/2011-06-05/time_to_wipe_data/cache
Click to expand...
Click to collapse
Awesome link!
That you all for the info. I tried a few things, installed a few ROMS, wiped them each time, and back to the CM7 nightlies and it all seems to be working fine now. Let's hope it stays that way.
Next time I have problems, I will have to do everything out side of ROM Manager and see if it has a better result..
Thanks again
Actually this has happened to me, usually happens when installing or Uninstalling certain hardware.
After reinstalling my roms to get it to work right when it did it few hours later to infuriate me. The only thing that did work was booting into Recovery and install my rom again but with what the guy said.
Wipe all data, everything, factory reset.
Then install your rom, then make sure you don't install or Uninstall certain hardware.
Sent from my HTC Droid Incredible -CyanogenMod- 157#build/Chads IncrediKernel ("Using" XDA Forums App)

[Q] ROM issues

A huge problem seems to have arisen on my Desire Z.
After using Andromadus 8 for a while I decided to try some other ROMS.
They were:
- Andromadus V10 and 11
- Virtuous Quattro RC3
- Ice Cream JIBwich 1.1
- BlissDroid
- Android Revolution HD 7.0
All of these ROMS flashed after using Superwipe G2 however were stuck on the initial boot screen.
I left some of these ROMS on for more than an hour on the boot screen to no avail.
The only ROMS that still seem to function are Andromadus V8 and MIUI ICS (however with no Wi-FI)
Please can anyone give an indication of what is wrong?
Some roms don't want you to wipe anything because the flashing will do it for you. Although it could've been that the roms have problems?
Sent from my CM7 G2!
i've done v11 on my phone after superwipe with no problems. But i have a G2 with desireZ Hboot and i clear dalvik cache before i run superwipe in rom manager. Make sure RM is updated to current then try flashing them. I don't think superwipe gets the dalvik. I've also ran quattro with no problem.
Cleared dalvik and checked all the MD5. Everything seems fine except it doesn't work
Tried a ordinary factory reset/data wipe?
-Nipqer
starop013 said:
i've done v11 on my phone after superwipe with no problems. But i have a G2 with desireZ Hboot and i clear dalvik cache before i run superwipe in rom manager. Make sure RM is updated to current then try flashing them. I don't think superwipe gets the dalvik. I've also ran quattro with no problem.
Click to expand...
Click to collapse
Superwipe does clear dalvik cache.
I am at my wits end
ONLY Andromadus 8 works for some reason
I cleared it and cleared it, and reflashed every combination of roms
BUT only 8 works and I'm tired of not having my camera anymore
I've even tried bare Sense 2 ROMS to no avail. Every ROM is stuck on bootloops
Does anyone have a solution?
Sounds like the boot.img is failing to flash for some weird reason.
If you have the eng hboot you should be able to use 'fastboot flash boot boot.img' (rip it from a rom.zip)
-Nipqer
Have you tried flashing from recovery directly? RM is great for convenience, but I just don't trust it to do things properly. I've had this happen to me sometimes where a ROM looks like it's flashed, but hasn't. Weird, I know. Try the following, it worked for me before:
1. Flash SuperwipeG2+ext4 (if you want the ext4 filesystem)
2. Flash your ROM
3. Check to see if it worked
4. If it didn't work, flash your ROM again without wiping
Usually that fixes it for me. In 4EXT recovery, you can check the partition sizes to see if the ROM installed properly. Not sure if CWM does that as well.
Nipqer said:
Sounds like the boot.img is failing to flash for some weird reason.
If you have the eng hboot you should be able to use 'fastboot flash boot boot.img' (rip it from a rom.zip)
-Nipqer
Click to expand...
Click to collapse
Nipqer
You sir are a legend
An obvious solution that makes me wonder why I didn't think of it
Thank you, thank you
flashing through recovery is just easier for some, and if your not near a computer. but for best results always fastboot -w and flash rom via fastboot, just makes life easy the first time. and im ocd a little so i also flash superwipe and manually wipe data/cache. so if you dont wont any issues, fastboot wipe, fastboot flash... your golden!

CM7.2 - Reboot on GPS Lock after all GPS Fix methods

Alright after all what I have done, I am still getting reboots when I open Google Maps and GPS is just about to lock to a location.
Things I have done:
1. Start from scratch - Format and wipe /system, /data, /cache, /sdcard, /sd-ext, delvick cache, run Caulkin's Format ALL, again wiped everything above, and last did VR_SUPERWIPE.zip
2. Flashed STOCK Sense Rom 4.67.651.3 (new ota update)[ROM] and rebooted into Stock Rom.
http://forum.xda-developers.com/showthread.php?t=1455340
3. Used MSL Reader + ##GPSCLRX# (##4772579#) method. Updated PRL while in SENSE Rom, and everything under settings > about phone > updates
4. Repeated Step 1
5. Flashed CM7.2 supersonic
6. Used Titanium backup to install only apk files for applications, not data files. Nothing from system was restored.
7. Did the Google Play updates to all apps, rebooted, Did more updates.
8. No task killers were installed, only major change is I went from ADW Launcher to GO Launcher EX.
Now I open the maps, I am on 3G speeds, maps load up, but within 5 seconds the GPS Locks, and booom Reboot.
Sometimes after the reboot, while in the middle of the CM7 boot animation, it will reboot again.
Only way to get everything back to stable is to wipe delivk cache again.
Extra steps taken:
Method 1 - Failed
1. Wipe Delvik cache
2. Flash Qualcomm Vision GPS Driver v1.1 (Flash 3.zip)
Method 2 - Failed
1. Wipe Delvik cache
2. Flash GPS_Supersonic_FIX_Flash2.zip http://forum.xda-developers.com/showpost.php?p=14534313&postcount=2478
I am really fed up now with my Evo 4g.... I need someone to help me out:crying:
UPDATE 08-24-2012
Roms Tried:
CM7.2
CM7.1
CM6.1
Decks ReLoaded
{LOTK]ReLoaded
Senseless_EVO v.1.1 (not asop)
Stock RUU 1.32.651.1
Shooter Rom on Sense3.0
Team DIRT's Rom
MIUI
CIUI
Lewa OS
Now on Nitrous ROM
Recoveries Tried:
CWM 5.2.*
Team Win's - TWRP
Now on RA-supersonic-v4.3-smelkusMOD
GPS Fix'sTried:
GPS_Supersonic_FIX_Flash2.zip - Qualcomm Vision GPS Driver v1.0
GPS_Supersonic_FIX_Flash3.zip - Qualcomm Vision GPS Driver v1.1
GPSCLRX Sense Workaround with CWM flash of CM7.2
Last try was on GPS_Supersonic_FIX_Flash3.zip
WIPE method:
Factory Reset
Cache
Delvik Cache
Data
SDCARD - ext3
SDCARD - .android_secure
BOOT
System
DATA:Battery Stats
DATA:Rotate Settings
Cache again
Delvik Cache again
Repeat ALL above again - (Yes, I know its excessive):cyclops:
Any other suggestions?
________________________________________________________________________
Device: HTC Evo 4G
Rom: CyanogenMod 7.2
Kernel: 2.6.37.6-cyanogenmod-g0799e00
Hardware: 0003
Baseband: 2.15.00.12.19
PRI: 2.15_003
NV: 2.15_003
PRL: 60683
HBOOT: 2.10.0001
Recovery: CWM 5.0.2.2
Have u attempted using another aosp rom like reloaded to see if the problem lies in cm7.2. I can verify that gps is flawless with reloaded.
Also, switch to amonra or smelkus recovery. Clockwork always causes problems
fitz420 said:
Also, switch to amonra or smelkus recovery. Clockwork always causes problems
Click to expand...
Click to collapse
how would flashing another recovery resolve issues at this point of time?
Whats the latest AMONRA version?
rcatank said:
how would flashing another recovery resolve issues at this point of time?
Whats the latest AMONRA version?
Click to expand...
Click to collapse
It wont fix anything. It will eliminate a bad flash/wipe from possible problems. Just do the sense ##gpsclrx# and flash to a different aosp like decks or reloaded and see if the problem persists.
still having issues
So I have been through most AOSP roms lately.. And I am still stuck on the reboot when I load up maps. Now though its getting worst.
Maps works for may be 10 seconds, get a good lock, but then within 10 seconds it reboots. Then gets stuck in a boot loop, until the battery is burning hot.
Another issue is now I get random reboots even while surfing the internet, loading and restoring from Go Backup / Titanium. All Google Inc apps are always fresh from Play store though. Since I moved to AmonRA and then TWRP, it didn't help what so ever. So finally I moved to RA-supersonic-v4.3-smelkus. I replaced my Samsung 32gb class 10 card with what came with the phone which was Sandisk 16gb class 4, but same issue. BTW, I always used 1gb of ex3 partition for A2SD when I loaded up any of the roms like MIUI, CM7.2, CM7.1, most any of the ICS beta's posted in the past month, and finally also tested Revolver, and the latest Deck's Reloaded GB2.3.5 with Mason G d15rc3 kernal. I found Saveged Zen to be no good with any of the roms, nor did I find Tiamat any help.
Now I am with RA 4.3 smelkus recovery, and Deck's latest rom with Mason Gd15 kernal, and the GPS Flash 3 zip. Still issues
I have been trying to produce logcat's but, the reboots are not letting me save anything before the dump to file happens.
try a sense rom and see if you are still having issues. I have run CIUI and GTR twinturbo, which are both cm7.2 based and have NO gps issues after flashing the GPS supersonic flash3.zip
Try unrooting and see if you have the same issue, it could be a hardware issue you could get replaced with sprint. Otherwise re root and try again.
Sent from my PC36100 using xda premium
BigSmoke53 said:
Try unrooting and see if you have the same issue, it could be a hardware issue you could get replaced with sprint. Otherwise re root and try again.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
id try a stock rooted rom before going through unrooting and rerooting .

Categories

Resources