Related
Mine disappeared after full root and does not show up in my app list to re-add it. It also does. Or show up in my app drawer. It does launch fine from the launcher and show up in folder organizer though. Any thoughts?
Sent from my PG86100 using XDA App
You will need to re do the htc software update that fixes this after a wipe or s-off..go to settings system updates htc software update
Sent from my PG86100 using XDA App
pbg225 said:
You will need to re do the htc software update that fixes this after a wipe or s-off..go to settings system updates htc software update
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Yep this works.. but for some reason I switched roms (Zones OMJ v6) and it keeps telling me there is no update available..
Is the any other way to apply that update ?
pbg225 said:
You will need to re do the htc software update that fixes this after a wipe or s-off..go to settings system updates htc software update
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Didn't work for me. I now am able to select the phone app to display on that icon (couldn't before taking the update) however it still doesn't display on the lockscreen. In settings it is there and everything looks fine though.
i am having the same issue....did full root, on synergy rom, cant update htc software update, says no update to be found.
No phone app to put on the lock screen...
any help would be greatly appreciated.
Thanks!
s-off and root works on the update, maybe if you guys can't figure out another way, either nand back to stock or RUU, then update, then reroot/s-off, etc.
I completely unrooted my phone and rooted back again but did not take recovery. Updated HTC then flashed teamwins recovery and did nandroid fixed that issue.
Sent from my PG86100 using Tapatalk
Fixed. I had to revert back to stock and S-ON then start over. It was something that got messed up in restoring settings from Titanium Backup.
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
adma84 said:
So, there is nothing magical about super wipe scripts, but this one seems to have had some serious thought put into it.
http://forum.xda-developers.com/showthread.php?t=834812
I usually wipe manually but was curious what you guys do...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
There is only one superwipe for our phone. There is nothing to compare it to, and no need as it works fine. The link you posted has nothing to do with our device.
http://forum.xda-developers.com/showthread.php?p=27166189
Ta da!
I've never understood super wipes. I just do it manually.
No need for a superwipe. Just Factory Reset and wipe System and you're ready to flash. That's never once given me a problem.
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
theoner1 said:
I use superwipe mod all the time after a manual wipe. Reason because TWRP does not have option to wipe/format the BOOT partition.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
You shouldn't have to wipe boot.
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Exactly I never even heard of a Superwipe until the 3d came out. Never had to flash one since I had my g1 and i'm not going g to start now
Sent from my EVO using xda premium
SoraX64 said:
You shouldn't have to wipe boot.
Click to expand...
Click to collapse
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
theoner1 said:
Install any aosp rom, example deck cm10 8-31-12. The Rom have force close issue with the phone process at the beginning. Now if you want to go back to latest sense Rom, without wiping boot img, you will continue to have the same phone process force close issue even if you're on sense Rom. It just happen to me a couple nights ago. So wiping boot partition is my way of completely getting rid of previous issue on the last install Rom.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
SoraX64 said:
I can flash between CM and Sense all I want without the error persisting, maybe you're doing something else wrong?
Click to expand...
Click to collapse
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
theoner1 said:
I was doing something wrong at the time, I forgot to flash the superwipe. When I first booted into meanrom 3.6 the same phone process force close still there. After realizing I forgot to flash superwipe, went back to recovery, wipe completely manually follow by superwipe then install meanrom 3.6, which booted fine without phone process error. Every time I flash a New Rom I always wipe everything at least twice.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
SoraX64 said:
Are you by any chance 1.15 S-ON?
Because not a week ago I left CM10 for Viper 4G because I needed the camera to work stably, and I did not receive the force close once.
Click to expand...
Click to collapse
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
theoner1 said:
Nope orginal hboot 1.12 and s-off
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm, interesting because I have gone back and forth between CM10 and MeanRom. I have never had an issue. I love the speed and fluidity of CM10 but the Sense camera is just to good at this point.
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
firmbiz94 said:
I have then same issue...if I don't use sw I have issues bouncing between sense and cmx nands.. can't make calls on sense without it..with it I have no issues
Click to expand...
Click to collapse
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
I think a lot of people got used to using these from the og evo. CWM was thought to have trouble wiping so most would wipe two or three times to make sure it didn't miss anything. I haven't heard of that being an issue for a long, long time though.
One thing that it may help with though is if the ROM doesn't format the system partition. I've spent hours trying to track down bugs only to realize leftover system files were wreaking havoc with the new ROM.
theoner1 said:
See what I mean, I'm not the only with this issue. Superwipe work wonders for me too.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Hmm that's interesting, i remember i flashed tranquility rom and was working great! then tested cmx and at the same time tranquility was updated and that error was still present on the new tranquility rom, but i thought it was the rom so i flashed another sense rom but, this time i used superwipe after manually wiping all and no error anymore, since then i didnt use tranquility thinking it was the new update. now i always use superwipe.
time to go back to tranquility :fingers-crossed::fingers-crossed:
I have a MoPho with unlocked bootloader running 2.3.4 and everytime I try to flash back to my saved stock backup from any custom rom I keep getting an "error while flashing boot image" I tried to do an advanced restore and picked the files one at a time but I keep getting the same result. Can someone please help, thank you in advance...
Sent from my MB855 using xda app-developers app
Are you restoring using the same utility you did the nandroid backup with? Joker recovery vs twrp vs cwm recovery
Sent from my MB855 using Tapatalk 2
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
I created the back up using cwm and trying to restore through cwm...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Are you using a working recovery? Jokers? Twrp? Photon3? Or the ROM manager one? ROM manager version does not work.
Sent from my MB853 using XDA
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
As far as I know, I am using Clockworkmod Recovery v5.0.2.8. I've tried Rom Manager but I usually get an error while trying to perform a NANDroid backup...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
as mentioned previously the ROM Manager one DOES NOT WORK. 5.0.2.8 DOES NOT WORK! you NEED to user Jokers, TWRP or the 5.0.2.7-photon3 recoveries ONLY. you can find the working recoveries on my site. choose which one suits you best! don't use Jokers V4 because it won't flash google apps properly.
http://www.motosunfire.com/clockworkmod-recovery/
Ok thanks a lot, I will try the two you just recommended...
Sent from my MB855 using xda app-developers app
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Stray2thaB said:
OK I downloaded the TWRP recovery you had suggested, I backed up my current from but when I tried to restore a different from I keep getting an error "the process com.android.phone has stopped working" and I have no service now...
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
na7q said:
alright? well that doesn't say alot? as you could be using any one of 20 different ROMs. which are you using?
Click to expand...
Click to collapse
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Stray2thaB said:
I am running cm7, or rather was running cm7 coz now my phone is stuck in the boot loop limbo. Kept getting the error "com.android.phone stopped working" and I was unable to make or receive calls all day. So I thought relocking and unlocking the bootloader would do the trick but now I'm stuck on a rock and a hard place. Sssoooooo, do you have any tricks up your sleeves I could use, I would really appreciate it...
Click to expand...
Click to collapse
Stray2thaB said:
I've been able to run a hand full of fastboot commands to bring my phone back out of limbo, I am past the boot image and able to activate with the sprint network. Thank you all who took the liberty of viewing my post, I appreciate the help...
Click to expand...
Click to collapse
hmmm... CDMA user? or GSM? i remember that bug being around in the very early builds of CM7. are you on the latest nightly or stable release?
i might also recommend changing some build prop info (which could be causing this?) to make sure it tells the radio to operate in the correct mode. gsm or cdma. if you look for ro.telophony.default_network=? the ? should be a 4 for CDMA or a 7 for GSM. change to your liking. then reboot. this was an issue in CM9 for the longest time and this is how it was resolved. it's possible it could be the same for CM7.
another option is to of course start over. wipe the cache,data,system partitions, possibly even twice. flash cm7. twice to be safe. then gapps. twice to be safe. then give it another shot.
other than that it might be a bad download or a bad build. so try another if it doesn't work. hope this helps you!
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Stray2thaB said:
CDMA user, for now I am able to have my phone back on, but I will probably steer away from CM7 AND perhaps try CM10. All I keep finding is an unofficial release, is this the only one there is?
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
there will never be any officials releases unless somehow Motorola decides they want to give us drivers/source for ICS or JB. which is never. unless we get a leak.
Can't figure out why but my DNA won't boot to android unless plugged into USB. Once its up and running, USB unplugging causes phone to reboot and boot loop. Phone is rooted with s off running on ukb ROM. Boot loader and recovery are accessible.
Any ideas on what it could be? Thanks in advanced.
-homer
Try wiping data and cache in recovery and then try to boot.
Sent from my HTC6435LVW using xda app-developers app
Jaggar345 said:
Try wiping data and cache in recovery and then try to boot.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I have I've tried that through both twrp and cwm. Reflashed rom as well with no luck. I've also tried wiping sdcard and internal storage.
Try flashing a different kernel. If you aren't soff then maybe you need to flash the kernel recommended by the ROM.
If flashing a kernel does t work then you might want to go back to stock and then get your phone working and then proceed to do a clean install of the rom of your desire.
Sent from my HTC6435LVW using xda app-developers app
I did try flashing stock kernel but still same problem. Also tried the boot.IMG provided with the ROMs I've flashed but still the same result. I've tried stock ruu but never got it to work even after OEM lock the phone
Sent from my HTC6435LVW using xda app-developers app
crpalmer said:
Try flashing a different kernel. If you aren't soff then maybe you need to flash the kernel recommended by the ROM.
Click to expand...
Click to collapse
I get that about causing the phone to boot loop if the wrong kernel was flashed but my phone only boot loops after unplugging USB. While connected phone boots fine.
Sent from my HTC6435LVW using xda app-developers app
https://www.youtube.com/watch?v=iyxiCFQiexA&feature=youtube_gdata_player
Here's a link to show you guys
Sent from my HTC6435LVW using xda app-developers app
O wow watched vid. That sux bro I have 0 clue..
Sent from my HTC6435LVW using xda app-developers app
Looks like we have tried just about everything that we possibly could have. You tried ruu back to stock completely relock? Usually if that doesnt work it may be a hardware problem and you might need to get a new phone through warranty or insurance. At this point i'm out of ideas of what you could possibly do.
Narrowing Down on it being hardware related somehow. Cause everything software has been changed
Sent from my HTC6435LVW using xda app-developers app
kaliblazin707 said:
Narrowing Down on it being hardware related somehow. Cause everything software has been changed
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
yeah i was afraid of that =/ must be something relted to the usb slot. thanks anyways.
Unfortunately, i just ran into this same issue. Just wanted to post that going back RUU and relock does nothing. I believe that it is probably an indicator of a failing battery. This would explain why being on charge, the phone will operate. e.g. underpowered (voltage) when on battery alone.
elhomer90 said:
yeah i was afraid of that =/ must be something relted to the usb slot. thanks anyways.
Click to expand...
Click to collapse
Today my DNA said the Wi-Fi was "turning on" and it just hangs there. It never actually turns on or connects to a wireless network. I have tried rebooting the phone, shutdown, using airplane mode, etc. Even did a factory reset and it's still doing the same thing.
I tried "WiFi fixer" from the Play Store, that didn't help either.
Phone has always been stock, no root.
Any suggestions?
Turn off fastboot and reboot. Then see if it works. If not only option might be to restore to factory settings.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
Turn off fastboot and reboot. Then see if it works. If not only option might be to restore to factory settings.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried turning off fast boot but I will try it again.
Already did a factory reset. I'm on the stock Android version as we speak.
Did you try performing an ruu of the current version you are on?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
Did you try performing an ruu of the current version you are on?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No I have not. I've yet to dive into Rooting and different ROMs on smartphones.
Got a link?
shortstop20 said:
No I have not. I've yet to dive into Rooting and different ROMs on smartphones.
Got a link?
Click to expand...
Click to collapse
The ruu won't root or put a custom rom on your phone. The ruu will erase your phone completely and put it back to the way it came out of the box on the stock rom. In your case it will be the newest update that's the ruu I suggest using. It's very easy to do just follow the instructions on the computer screen. Hopefully it can fix the issue if it doesn't it probably hardware related and if that's the case and your within your one year warranty try and get a replacement. But we can cross that bridge when we get there. For now get the newest ruu which is 3.0.6 I believe from here.
https://drive.google.com/file/d/0B32gqnbh2ZecYTlvV1dlZTVRS0E/preview?pli=1
That is the direct download link. The ruu needs to be run on a Windows computer I recommend Windows 7 and have the phones drivers installed for it to work properly.
This is the thread where it's located on xda.
http://forum.xda-developers.com/showthread.php?t=2612740
If you have any questions feel free to direct message me or reply within this thread.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
The ruu won't root or put a custom rom on your phone. The ruu will erase your phone completely and put it back to the way it came out of the box on the stock rom. In your case it will be the newest update that's the ruu I suggest using. It's very easy to do just follow the instructions on the computer screen. Hopefully it can fix the issue if it doesn't it probably hardware related and if that's the case and your within your one year warranty try and get a replacement. But we can cross that bridge when we get there. For now get the newest ruu which is 3.0.6 I believe from here.
https://drive.google.com/file/d/0B32gqnbh2ZecYTlvV1dlZTVRS0E/preview?pli=1
That is the direct download link. The ruu needs to be run on a Windows computer I recommend Windows 7 and have the phones drivers installed for it to work properly.
This is the thread where it's located on xda.
http://forum.xda-developers.com/showthread.php?t=2612740
If you have any questions feel free to direct message me or reply within this thread.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can't get the CLI commands to run. I installed the Android SDK. Is there something else I need to do? I'm in "Fastboot USB" mode.
shortstop20 said:
I can't get the CLI commands to run. I installed the Android SDK. Is there something else I need to do? I'm in "Fastboot USB" mode.
Click to expand...
Click to collapse
Is there a specific error that the ruu gives. I'm not familiar with what your referring to. Did you follow instructions in the thread I linked? Are your drivers installed for your phone?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
shortstop20 said:
I can't get the CLI commands to run. I installed the Android SDK. Is there something else I need to do? I'm in "Fastboot USB" mode.
Click to expand...
Click to collapse
Did you first try re flashing your kernel? Might be why your WiFi is sticking.
Sent from my HTC6525LVW using xda app-developers app
grimlocksmash said:
Did you first try re flashing your kernel? Might be why your WiFi is sticking.
Sent from my HTC6525LVW using xda app-developers app
Click to expand...
Click to collapse
Hey guys, after flashing the firmware and the RUU twice using the link provided the Wi Fi is working but it's still acting a little funky here and there. Earlier this morning, the phone rebooted when I tried to turn on Wi Fi. After it booted up, I was able to turn Wi Fi on/off several times and it worked perfectly.
Any chance that putting cyanogenmod or something on there would fix these intermittent glitches?
What would I do for a bootloader and root?
Newbie here, did some reading last night but there's so much.
If you look in the original development thread you will find it. Go to the website download the one for the DNA and then follow the guide. Once you achieve soff you need to flash a custom recovery. I recommend the twrp 2.6 beta it seems to work when flashing all the kit Kat roms I haven't tried 2.7 yet but if your feeling adventurous you can try that to. To flash a recovery you need to put your phone in fastboot and then use the command fastboot flash recovery and then you have your recovery on your phone. Then you can flash what you want. If you want to do this and need any help direct message me and I can help you out.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Jaggar345 said:
If you look in the original development thread you will find it. Go to the website download the one for the DNA and then follow the guide. Once you achieve soff you need to flash a custom recovery. I recommend the twrp 2.6 beta it seems to work when flashing all the kit Kat roms I haven't tried 2.7 yet but if your feeling adventurous you can try that to. To flash a recovery you need to put your phone in fastboot and then use the command fastboot flash recovery and then you have your recovery on your phone. Then you can flash what you want. If you want to do this and need any help direct message me and I can help you out.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am trying to flash to the Sense 5 RUU to see if it corrects my Wi Fi issues but it's stuck at the following:
(bootloader) Read zipped android_info fail
What should I do?
shortstop20 said:
I am trying to flash to the Sense 5 RUU to see if it corrects my Wi Fi issues but it's stuck at the following:
(bootloader) Read zipped android_info fail
What should I do?
Click to expand...
Click to collapse
OK, I decided to take a chance and reboot the device. I'm back in fastboot mode so I'll try the RUU again.