Hello, I've been lurking on XDA for some time now since I first rooted my OG Dinc and I just recently got the Dinc 4g LTE running on the 2.17.605 version with sense 4.1. I have also rooted it and installed TWRP recovery after following the fakecid guide. On the stock rooted Rom, I have no usability issues, but when I tried to use the Viper 2.0.0 Rom, I was unable to dial out, the people app wasn't syncing with my google account and was generally quite glitchy. I would like to use this Rom to take advantage of the features, but I can't use it as a daily driver with these conditions.
What have I missed and what should I do to fix this?
Thanks for hearing me out,
Raven744
Raven744 said:
Hello, I've been lurking on XDA for some time now since I first rooted my OG Dinc and I just recently got the Dinc 4g LTE running on the 2.17.605 version with sense 4.1. I have also rooted it and installed TWRP recovery after following the fakecid guide. On the stock rooted Rom, I have no usability issues, but when I tried to use the Viper 2.0.0 Rom, I was unable to dial out, the people app wasn't syncing with my google account and was generally quite glitchy. I would like to use this Rom to take advantage of the features, but I can't use it as a daily driver with these conditions.
What have I missed and what should I do to fix this?
Thanks for hearing me out,
Raven744
Click to expand...
Click to collapse
Boot into twrp and fix permissions. That will fix the sync issue. Generally glitchy it's a little broad, off you post specific issues we can probably help.
Sent from my ADR6410LVW using Xparent Blue Tapatalk 2
I've had the Google account sync issue on two consecutive installs of v2. Both times I've booted to TWRP and wiped cache & dalvik. Fixed it both times. Other than that, this ROM has been rock solid for me. No dialing issues.
same here, wipe cache and dalvic and all is ok. did this on viper1 and viper2, worked both times
I did the fix perms and wipes pre flash to no effect. I still don't have the people app syncing. Did you guys do this post-flash? Also dialer still doesn't work.
Thanks guys! Doing what you recommended post-flash helped clear up the issues.
i just previously ran the vipers 2.0 rom because i didnt knotice the 2.1.1 patch for sence 4.1 andnow i still have no problems.....
did you flash it right
1. boot into recover> wipe> factory data reset
2. wipe> cache
3. wipe> dalvik cache
4. install zip> your rom ( viper 2.0.0)> and use there full wipe script and install
5 install zip > your rom ( viper 2.1.1)
6. reboot, problems should be fixed
Related
Hey thunderbolt community!
Just got myself a thunderbolt and rooted it (s-off, busy box, super user). I flashed syenergy rom and after reboot it was terribly slow. Now I might of messed up so here I the process I took.
- Rooted (as stated above)
- Downloaded ROM
- Downloaded Kernel
- Booted into clockwork
- Wiped cache
- Wiped dalvik
- Flashed ROM
- Flashed Kernel
- Rebooted
Rom booted but was so slow and not usable. Was I supposed to do a full wipe because it was still stock rom? I am coming from a rooted CM7 incredible so I am quite experienced. Please help!
First off this is the wrong section
Second yea u need to always wipe everything when switching to a new ROM. I use Synergy and the first boot will always be laggy. Synergy let's your Google account download all the apps that u previously had which really slows the phone down. What I'd do is wipe EVERYTHING. Then flash the ROM again. During setup, only setup your Google account and leave for Facebook or whatever other accounts u set up for later as it may speed up things for the first boot. And then I'd just put the phone down n let it do what it needs to do. Synergy is a fast and smooth ROM. The first boot is always laggy on any ROM that allows Google to auto download previous apps. Hope this helps
Sent from my SICKLY INFECTED VirusBolt Synergy 3.0 using XDA Premium App
wetbo529 said:
Hey thunderbolt community!
Just got myself a thunderbolt and rooted it (s-off, busy box, super user). I flashed syenergy rom and after reboot it was terribly slow. Now I might of messed up so here I the process I took.
- Rooted (as stated above)
- Downloaded ROM
- Downloaded Kernel
- Booted into clockwork
- Wiped cache
- Wiped dalvik
- Flashed ROM
- Flashed Kernel
- Rebooted
Rom booted but was so slow and not usable. Was I supposed to do a full wipe because it was still stock rom? I am coming from a rooted CM7 incredible so I am quite experienced. Please help!
Click to expand...
Click to collapse
Follow these procedures:
- Normally you'd perform a nandroid first after flashing into clockwork recovery, but I don't know that you'd want to do that since the ROM is running poorly; your call (I would anyway)
- Wipe Data I always do this, no matter what. That might sound extreme, but I've never had one issue with any of the three android phones I've owned.
- Wipe Cache
- Wipe Dalvik
- Flash Rom
- Flash Radio (if necessary)
- Reboot
Play with the ROM for a while before you flash a different kernel. You might find one of two things: 1) The kernel that came with the ROM is plenty fast and does everything you need, which leads to 2) The kernel you flashed originally could be the cause of the slowness.
Ir's possible the ROM is the issue, so following the above procedure will rule everything else out. Let us know how it goes.
Hi,
I'm running CyanogenMod 7 Nightly on an Incredible S. I was on Nightly #68 and today I updated to #89. For the update, I backuped my rom, wiped the Data and Dalvik cashes as is recommended. When the update was done, I had to re-setup my phone from the Android's first boot screens as well reinstall all of my apps and set the options like they were beforehand manually.
I'd like to know if there is a way to make updating roms a little quicker by not having to go through this whole process every time? ie: update rom and still have the phone as it was. I could understand that it may not be possible when going from CM to Virtuous Unity for example. But I'm wondering if I'm missing a step when it comes to simply updating the version of a single rom?
Thanks for any help!
You need a partition with the stable ROM and one to experiment with Nightlies.
lifehacker.com/5826050/how-to-dual-boot-multiple-roms-on-your-android-phone
There is no need to do any wipe going from one nightly to the next.
If you do wipe don't wipe data and you don't have to do set up again.
I do recommend titanium backup for times that you have to do full wipe.
Alright, thanks guys! I should be good to go now!
Sent from my Incredible S using xda premium
I have been running MIUI on an x2 for a few days and I went to use my Camcorder and it crashes. I tried several different ones and it just keeps failing. It starts to record and then does a FC. I downloaded different cameras and they do the same thing. I even tried some different once through downloading the Apks from this device and from the Atrix.
Does anyone have any ideas?
Probably a silly question but did u manually do a reboot, or go into applications and clear the catch and data. Also when you installed the miui did u do the three wipes first?
Sent from my DROID X2 using XDA
Lol good question. I have done these. I can try to reflash it?
Sent from my Milestone X2 using XDA
Lol, sorry if that was obvious but I know I usually over look the easy stuff. I have only ever had these problems when I didn't wipe the data and catch after I flashed
Sent from my DROID X2 using XDA
I am going to try to do that. Thank you for trying though.
No prob hope u get it
Sent from my DROID X2 using XDA
From what I have been able to read its something to do with permission settings for the camcorder. If I can just get help how to change this to the proper settings that would be great!!
This is a bug that has been with the rom since the beginning.
I hope you find a workaround.
If you follow Aceoyame on twitter you can see his progress on the next release based on Dragonkillerz work on cm9. Some are saying this summer, just in time to take some video
Sent from my DROID X2 using XDA
lol, Yeah from what I have been reading I think its about the permissions. But I am trying to figure out exactly what file.
I wanted to give an update. Talked with Ace and he said there will be an update out to fix this sometime in the next week. Great news!
Sent from my Milestone X2 using XDA
That is great news. Good on ya mate.
@ twobrare
I got tired of the camcorder not working and wanted to switch roms.
To make a long story short, I am back on MIUI beta and the camcorder seems to be...
working now!
What I did (or what I can remember I did, because you know how it goes SBF'ing, flashing roms, and clearing caches over and over again)
Booted into BSR and made back-up of the MIUI setup I was running (with camcorder not working)
SBF'd to 2.3.4 kernel factory reset / cleared cache and dalvik cache
*did not root yet*
rebooted into stock recovery and flashed 2.3.5 kernel.
Then did Zerg Rush Root method.
Installed BSR(not the cm7 version) the original.
Booted into BSR and factory reset / cleared cache and dalvik again...
Flashed Eclipse 2.2 custom rom.
Booted into op system / skipped everything / got to homescreen checked wifi to see error when trying to toggle on/off.
Got pissed, took a drink of a nice northwest local IPA and said Im going back to MIUI and Im doing it with 2.3.5 kernel installed.
This is where I got a little fuzzy... but I think this is what I did...
Did a operating system factory reset (just internal sd card)
Booted back into op system I think I had to re-install BSR (original)
Booted into BSR and restored my latest backed up MIUI.
When I got back to MIUI I noticed WIFI was working and when I went to Camera APP switched to video it didnt FC.
Instead it recorded a 25 second video with no problems. I have been playing with it ever since with no problems.
I hope this may help you in your quest to get camcorder in MIUI.
joshahouck
joshahouck said:
@ twobrare
I got tired of the camcorder not working and wanted to switch roms.
To make a long story short, I am back on MIUI beta and the camcorder seems to be...
working now!
What I did (or what I can remember I did, because you know how it goes SBF'ing, flashing roms, and clearing caches over and over again)
Booted into BSR and made back-up of the MIUI setup I was running (with camcorder not working)
SBF'd to 2.3.4 kernel factory reset / cleared cache and dalvik cache
*did not root yet*
rebooted into stock recovery and flashed 2.3.5 kernel.
Then did Zerg Rush Root method.
Installed BSR(not the cm7 version) the original.
Booted into BSR and factory reset / cleared cache and dalvik again...
Flashed Eclipse 2.2 custom rom.
Booted into op system / skipped everything / got to homescreen checked wifi to see error when trying to toggle on/off.
Got pissed, took a drink of a nice northwest local IPA and said Im going back to MIUI and Im doing it with 2.3.5 kernel installed.
This is where I got a little fuzzy... but I think this is what I did...
Did a operating system factory reset (just internal sd card)
Booted back into op system I think I had to re-install BSR (original)
Booted into BSR and restored my latest backed up MIUI.
When I got back to MIUI I noticed WIFI was working and when I went to Camera APP switched to video it didnt FC.
Instead it recorded a 25 second video with no problems. I have been playing with it ever since with no problems.
I hope this may help you in your quest to get camcorder in MIUI.
joshahouck
Click to expand...
Click to collapse
Nand backup your miui and let Ace know of your discovery! He's trying to find a correction
Sent from MB870 W/ Cm7.2 Rc1
SUCESS I THINK YES...
I've been struggling with this for about a week and I am not able to figure this one out. I hope someone here can give me a hand.
I've unlocked my phone using HTCDEV and rooted using TWRP 2.4.3 gaining root and recovery access. All seemed to work well but every GOOGLE app crashes now on start up. I can't go to the market as it crashes "Unfortunately Google play store has stopped". It does this with all Gapps.
I've flashed the GAPPS through recovery since I can't access Play.Google. and it made no difference. I can't log in to Google accounts as soon as try it gives me "google account manager has stopped".
I've tried to RUU back to rom 3.16. but RUU fails to update the phone although the restoral screen shows the scrolling dots indicating it is updating, but it goes on forever. the bootloader shows "TAMPERED" "Unlocked" and this came after using FASTBOOT OEM LOCK command in an attempt to reflash the unit. I have tried to flash to other roms like CM10 but it only gets to the point of the spinning logo and just sits there and spins, etc. Other roms get stuck as well in the first boot up logo of the rom or give a black screen. I can use TWRP to restore the backup each time so the phone works seemingly ok except for anything with Gapps.
I assumed I can't not flash JB roms without S-off and I tried to use Dirty Racun to obtain S-off but I get errors with each step so gave up on that for now. I've resolved myself to sticking with the stock rooted rom but I can't do much without Google Voice which is my text and phone account.
Can anyone shed some light on this for me? I've searched the forums here and elsewhere for dozens of hours and have not been able to find a solution for this or any help that might help me "stumble" into a solution. I don't mind flashing another rom if I could get one to take hold just so I can get this unit working.
I think the TWRP recovery or a old verion of Superuser might have caused this glitch. I did the rooting and recovery using this guide here htcevohacks.com/htc-evo-4g-lte-root/how-to-root-htc-evo-4g-lte-unlock-bootloadertwrp-recovery and the provided TWRP would not accept any input so I replaced it with 2.4.3.0 and recovery then recovery seemed to work and backup/restore but still can't flash any roms successfully. I didn't notice Superuser v0.87 here as being old (my goof) and didn't get a more recent version until after the flashing was done. LIke I said, where I'm left at now is everything seems to work but anything having to do with Gapps just crashes on start.
Any help please?
Couple things you could do if you wanted a new rom. First go to the q&a section there is a sticky titled don't panic it will let you know to fast boot the bootimg for being son or find a rom that has son kernel installer for sense mean bean does
Sent from my EVO using Tapatalk 2
I had this issue today when I flashed viper 4g ROM before doing my s off. I tried every approach and what I ended up doing is a factory reset, cache wipe, D. cache wipe, Android secure wipe, sd ext. wipe (I always do the wipe 3x in a row on each) then I reinstalled my viper rom (comes with the latest google apps) and off I go. Solved all my google sign in related issues. You could also try to locate a downloadable version of goomanager which will automatically check for the latest version of gapps that is compatible with your rom and download it. Doesn't need to have a google playstore link to work either.
Sent from my EVO using xda premium
thicklizard said:
Couple things you could do if you wanted a new rom. First go to the q&a section there is a sticky titled don't panic it will let you know to fast boot the bootimg for being son or find a rom that has son kernel installer for sense mean bean does
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thicklizard, Thanks, I'll check this out now. Are you saying the rom Mean Bean is a ROM and might take hold flashing it with my s-on situation? Is MeanBean an xda developers rom? I've always had good luck with just about everything from XDA, so would love to try it. My hope is a new rom would solve whatever "hell" my phone is stuck in. Thanks! I'll see if I can find it.
dominicsdad said:
I had this issue today when I flashed viper 4g ROM before doing my s off. I tried every approach and what I ended up doing is a factory reset, cache wipe, D. cache wipe, Android secure wipe, sd ext. wipe (I always do the wipe 3x in a row on each) then I reinstalled my viper rom (comes with the latest google apps) and off I go. Solved all my google sign in related issues. You could also try to locate a downloadable version of goomanager which will automatically check for the latest version of gapps that is compatible with your rom and download it. Doesn't need to have a google playstore link to work either.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
dominicsdad, I'm going to check out what was suggested about Mean Bean but I did try several JP type GB apps, etc. None of them would restore the function. THis has been so frustrating. I'm a guy that can folllow the posts and the guides I read, etc., but not having the core understanding or depth shows it's ugly face for a non-connected guy like me. WHy did you do an SD wipe? That's where I keep my backups which have been the only thing that has let me get back from a few botched rom attempts. I will try the goo manager if I can find a flashable version since I'm locked out otherwise with any kind of app install. I was surprised to see the EVO LTE didn't have a file manager as I was going to try and just install google voice which would at least allow me to use the phone.
THanks!
billaggie said:
Thicklizard, Thanks, I'll check this out now. Are you saying the rom Mean Bean is a ROM and might take hold flashing it with my s-on situation? Is MeanBean an xda developers rom? I've always had good luck with just about everything from XDA, so would love to try it. My hope is a new rom would solve whatever "hell" my phone is stuck in. Thanks! I'll see if I can find it.
Click to expand...
Click to collapse
Thicklizard,
Update, I installed Mean Bean and solved my problem. It gave me a scare thinking it would backfire with the 2 duplicate rom installs it requires but I had to put some faith in something working and it worked. Thank you for getting me on the right track!!!!!! Bill
I followed all of the instructions. I bought the Note when it came out, for a pretty penny. I may not be a developer, (yet), but the point I'm making is that I've been doing this for a while now.
TWRP - Running a 4.1 Rom Black Jelly
Fixed my batter charger port - navigation keys don't work
Looking for my beloved AOKP that should have it - I want 4.3
Wipe everything - Reboot into CWM recovery
Wipe everything, the Dalvik, system, cache, data, everything
Updating apps - 92 then right before I'm about to reach the promised land, it reboots!
Next time it reboots there are 60 something apps, still reboots
Reboot loops!
Even when I go back to wipe everything all over again in CWM like Cache Dalvik, and even system, it simply does not boot.
I even formatted system and re-installed the entire operation, twice!
So what's the problem? This is exasperating. I just want a navigation bar, and 4.3.
Thanks.
Have you followed the AOKP thread? Fuze haz developed his own version of CWM recovery to help with the hangups that done are experiencing with 4.3.
Sent from my Big Ass Outlaw Phone.
Thanks. Yes but i am such a lurker i havent asked enough questions to go to that vip forum. I also have read the forum and cant find the fix. Im on a 4.1 stable rom blackjelly now with the customized cwm recovery they provided. I have a floating navbar that is annoying and im surviving just fine. So i guess its no big deal, just frusterating.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
So you are wanting AOKP 4.3 and wanting the navigation bar correct? You can haz. Give the custom recovery that Fuze posted in his op.
When I flashed with TWRP I had a similar boot issue. The message read updating app #of 40... which was odd.Then I rebooted and it read updating app #of 80.
After that I got a 20 minute bootloop and figured I better restore my nandroid and wait. While attempting to get into recovery it then booted and was good to go.
Give the custom cwm in the AOKP thread a shot.
Sent from my Big Ass Outlaw Phone.