• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] Viper4G 4.0.0 and beyond

Hi Guys, I'm running Viper4G 3.1.6. when I try to install the latest update my Evo boots into TWRP Recovery and sits there. When I look at the commands screen from within TWRP it says

E: Can't mount INTERNAL SDCARD: /Download/Viper4G_OTA_3_1_6-3.1.7.zip. Installation aborted.

Can somebody offer me a suggestion as to how to get 3.1.7 installed?

Thank you in advance....
 
I have not updated TWRP, but I probably should. I'm still on v2.2! I think I'll do that first, then make a new backup, then try the install again.

After my earlier post I was finally successful getting the update installed by doing the update manually, but after installation I continually received a UI error, and I lost my notifications area at the top. I cleared caches, rebooted, restored, reinstalled, and always had the same result.

Oh well, I'll update TWRP and will give that a try.

EarlyMon, thank you for your reply....
 
If you had any changes made to the quicksettings layout, you'll get system UI crashes. Once you reset the default layout to quicksettings, apply the update, it'll take after that.

I was going nuts because I was getting the same errors, finally read that was causing headaches. Reset to defaults and applied the update, Ka-pow! It took! :)
 
If you had any changes made to the quicksettings layout, you'll get system UI crashes. Once you reset the default layout to quicksettings, apply the update, it'll take after that.

I was going nuts because I was getting the same errors, finally read that was causing headaches. Reset to defaults and applied the update, Ka-pow! It took! :)

I assume you are talking about vertical quicksettings, I only use the horizontal and have no issues. I've changed the horizontal and the "quick apps" (I forget what those are called) but never touched the vertical.
 
If you had any changes made to the quicksettings layout, you'll get system UI crashes. Once you reset the default layout to quicksettings, apply the update, it'll take after that.

I was going nuts because I was getting the same errors, finally read that was causing headaches. Reset to defaults and applied the update, Ka-pow! It took! :)


Granite1, I am convinced that is my problem as I reordered the vertical quick settings. Now...I just spent 15 minutes trying to find how to restore defaults and couldn't find it! Do you remember how to do this?
 
Not particularly. I just deleted a few, never rearranged them.

Personally, I'd restore your last nandroid, back everything up, then flash fresh.
 
I liked this ROM (Viper 3.1.7) because it was smooth and full of extra mods. But I've been having horrible battery life. I have pinpointed it to Google Services. I've ran it both enabled and disabled of Google Location Services but the battery life is the same. While in airplane mode, Google Services drained from 100% to 8 % in 16 hours of time. I switched to MeanBean v3.09 and I'm getting better battery life, but not as good as I was on Viper 2.0.2. Is this a Jelly Bean bug?

Did anyone else get this battery life drain on airplane mode with Viper 3.1.7?
 
I liked this ROM (Viper 3.1.7) because it was smooth and full of extra mods. But I've been having horrible battery life. I have pinpointed it to Google Services. I've ran it both enabled and disabled of Google Location Services but the battery life is the same. While in airplane mode, Google Services drained from 100% to 8 % in 16 hours of time. I switched to MeanBean v3.09 and I'm getting better battery life, but not as good as I was on Viper 2.0.2. Is this a Jelly Bean bug?

Did anyone else get this battery life drain on airplane mode with Viper 3.1.7?


Google services was randomly keeping my phone awake, sometimes for hours, when I first started using Viper. Try wiping data from the Google contacts sync app. That's what fixed it for me.
 
Clear data for Google Play services, Google Play and Google Services Framework. Reboot to recovery, and wipe the cache and dalvik cache. Reboot.

Also check and make sure all of your apps are up to date. If I have an app update I skipped for some reason, Google services is #1 on battery drain.

Once all my apps are updated, it behaves again. :)
 
Hey EM, does this update also require the quick settings to be set to default?

Last one I had to restore the stock Viper quick settings order to get the update to apply.

@ Evorob, try to reset the quick settings to the default layout and try the update again.
 
Hey EM, does this update also require the quick settings to be set to default?

Last one I had to restore the stock Viper quick settings order to get the update to apply.

@ Evorob, try to reset the quick settings to the default layout and try the update again.

I think so.

Swamped by this storm, hard to check. :(
 
It seems that a few of us have changed our quick settings to the effect that we can't get a clean install of Viper 3.1.7. Would somebody who has the default settings intact please take a screen capture of the default quick settings so we can try to reset ours to the same? Thanks so much!
 
Here are screenshots of the quicksettings for 3.1.7:
uploadfromtaptalk1375131402396.jpg
uploadfromtaptalk1375131428876.jpg

Hope this helps. :)
 
Granite1, that did the trick - thanks so much for posting the quicksettings images.

For others that might have reorganized Quicksettings in v3.1.6, I was unable to successfully complete the update to v3.1.7 because I had reorganized the order of the vertical quicksettings (in v3.1.6). Once I manually "re-reorganized" them back to their defaults per the images from Granite1 above the update was successful.
 
Awesome, being the best ROM out there...I know I would have no problem waiting for an update as most others would as well.
 
So I see that viper4g 4.0.0 (LINK) is in testing...does anyone know what the prerequisites will be to flash this ROM. I am currently running Viper 4G 3.1.7 on Android 4.1.1 with build 3.16.651.3. I would like to get current so that when this bad boy comes available I can flash it early on.
 
No details yet. Because Sprint didn't do an OTA, HTC did an RUU, Vin is probably going to use Chubbz or Capn Throwback's base for going to Android 4.3, per his posts.

It's possible that going with the new RUU will be required to get the new partition layout, but, I don't know that for a fact.
 
No details yet. Because Sprint didn't do an OTA, HTC did an RUU, Vin is probably going to use Chubbz or Capn Throwback's base for going to Android 4.3, per his posts.

It's possible that going with the new RUU will be required to get the new partition layout, but, I don't know that for a fact.


Gotcha! We shall wait and see!
 
Back
Top Bottom