I'm currently on Viper DNA 1.1.0 and I'd like to be on 1.1.3 but every time I try to update from 1.1.0 to 1.1.1 i get stuck at the HTC screen after installing it. Any idea why this happens? I"m doing the whole factory reset, system wipe, dalvik wipe 3 times each and I didn't have any problems when I did this before. Any help would be greatly appreciated.
Sluggage said:
I'm currently on Viper DNA 1.1.0 and I'd like to be on 1.1.3 but every time I try to update from 1.1.0 to 1.1.1 i get stuck at the HTC screen after installing it. Any idea why this happens? I"m doing the whole factory reset, system wipe, dalvik wipe 3 times each and I didn't have any problems when I did this before. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Re download and verify md5 after the download. Especially if you are using the ota to get the update. Just go to the forum and try again.
Related
Apologies in advance for being such a n00b.
I'm currently running CM7 RC1.1 with the MR2 radio on my rooted TBolt.
Heard lots of good things about BAMF 3.0 and thought I'd give it a try.
Did a complete wipe. Installed. Immediately after boot, things started going wrong. Lots of crashes even before I could sign into my Google Acct, VZW appeared briefly and went away altogether, and I couldnt connect to any wifi network.
Tried a few reboots. Reflashed the MR2 radio. Did a complete reset. Still no success.
I'm back on CM7 now but very keen on trying BAMF. Any suggestions on what I might be doing wrong?
nulambhbk said:
Apologies in advance for being such a n00b.
I'm currently running CM7 RC1.1 with the MR2 radio on my rooted TBolt.
Heard lots of good things about BAMF 3.0 and thought I'd give it a try.
Did a complete wipe. Installed. Immediately after boot, things started going wrong. Lots of crashes even before I could sign into my Google Acct, VZW appeared briefly and went away altogether, and I couldnt connect to any wifi network.
Tried a few reboots. Reflashed the MR2 radio. Did a complete reset. Still no success.
I'm back on CM7 now but very keen on trying BAMF. Any suggestions on what I might be doing wrong?
Click to expand...
Click to collapse
Did you flash BAMF from ROM Manager or Recovery. Don't flash from ROM Manager. Flash it directly from the recovery. Also try wiping multiple times.
I did flash from recovery. Will try multiple wipes this time. Just to be clear, which selection in recovery is the proper one for a complete wipe?
Thanks for the idea!
nulambhbk said:
I did flash from recovery. Will try multiple wipes this time. Just to be clear, which selection in recovery is the proper one for a complete wipe?
Thanks for the idea!
Click to expand...
Click to collapse
Its Wipe Data/Factory Reset. There's also Wipe Cache Partition. And under advanced there's a Wipe Dalvik Cache. Make sure you Nandroid(Backup)!!!!
Btw if you don't know how to navigate in recovery menu, its volume button to scroll and the power button to select
Up and running. Thanks!
So here is the situation:
I previously had 7.1.0 rc1 thunderbolt kang and wanted to update to the latest cm7 version (7.1.1). I wipe cache and dalvik and tried installing and my phone got stuck on the boot screen. I then decided to wipe data and reinstalling but same **** happened. I then decided to try to reinstall my previous version (7.1.0) and now i have no service and my baseband version is now unknown. I've tried different radios for this version and nothing works. I need my phone for my work and having no phone right now is killing me. does anyone know why this is happening ? thanks
try loading latest .906 radio, wiping data/cache/dalvik & don't forget to format system... then install your rom
This happened to me once. All else fails, download the latest RUU and load it on the phone. You will lose root, but you will have a phone and you can reroot later....
Sent from my Eternity infected TB on XDA Mobile
just try all the radio combos until u find one that works, your phone is fine
I've tried it all folks. New kernels, factory reset, different radios, different ROMs. Every-thing. The WiFi will turn on for a quick second and I will get an error message "Unable to scan for networks" and then the Wifi will just turn on and off on and off over and over again. I've even deleted the files in the data/dhcp and data/wifi folders. Rebooted, still same issue. I've deleted the files and flashed a kernel and rebooted, still same issue.
Of course I am still in contract and will have to purchase a new phone outright from Verizon if I can't get this issue resolved......
I don't know what else to do here.....
Did you try formatting data and system before installing a new rom from recovery? If that doesn't work i would say its a hardware issue. You're not restoring system data with any backup programs are you?
Sent from my ADR6400L using Tapatalk
I've wiped pretty much everything known to man on the phone. The ROM installs are all "fresh" I haven't tried to install any APPS on the phone. Just wipe everything, factory reset / Dalvik Cache, all of it... install fresh ROM. Try to turn on Wifi, phone boot loops. No matter what ROM I install, still same issue with Wifi / boot looping.
Well guess we can close this out. I went out and paid full boat for a Samsung Nexus since I couldn't fix this issue.
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
@ajoesq I had the same problem when i installed thunderstick thru boot manager. My wifi stopped and I could get it going on my phone rom. So i booted back into thunderstick and wifi was working. Booted back to hte phone rom then into recovery and then i flashed my phone rom again without wiping or anything (Thunbershed V1.2) and it worked fine. wifi started agian.
ajoesq said:
I'd like to reopen this topic. I had been running Bamf Forever 1.10, but last night I decided to try another ROM because it's been running really slow for some reason.
Did a wipe (factory reset, Dalvik cache) and installed Thunderstick. Now WiFi is broken -- the exact same problem as described in the original post. I tried flashing a new kernel and new radios, and cannot get WiFi to work.
Does anyone have any suggestions? Will flashing back to stock ROM/unrooting help?
Thanks!
Click to expand...
Click to collapse
Run a logcat when you try to turn wifi on. Put the output on pastebin.com and post the link. This might tell us what the problem is.
I'd make sure that the radio(s) were at least at the minimum of what the ROM called for.
Sent from my HTC ThunderBolt using XDA Premium App
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
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