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

Root remove sense option with viper?

dan55

Android Expert
hi guys,

just noticed that there is a remove sense option in viper aroma - does this just remove blink feed etc? do peeps go for this option?

thanks
dan
 
mmm....im not sure it is a good idea :/ as this is sense based rom - think i will keep it
 
I had been considering this option just for curiosity sake.

I'm betting it was operator error (mine),but,something went wrong:
I selected the option to remove sense & use NOVA.
Initially,everything looked normal,just as if you performed a Factory Reset on a stock phone,(language set-up/GOOGLE Sign-in).

Then,things got ugly,home screen was blank/black,only a pull-down notification bar.
Attempted to navigate from there,got into the stock settings menu list,however,the phone was non-responsive.
Re-booted,then,phone got stuck in a bootloop.
After about 30 minutes,was able to get back into recovery & restore a backup.

Perhaps a few days from now,I'll try it again.I'll do a bit of reading @ XDA & see if this has happened to others,or,if it indeed was user error on my part.
 
If this is like the Viper rom that I was a team member of, it removes a lot more than eye candy - and expects that you're going to go in and start supplementing all of the missing apps.

After a lot of work with it, I simply decided that if I wanted to try de-Sensed roms to just play around with the various CM-based derivatives.

That's fun to do and there's a lot of great stuff out there - check out NYCHitman's rom for example.

They're really different philosophies.

Viper = Sense (and yeah, Sense is on the heavy side) + more stuff to make it even heavier + plus a schizophrenic option to de-Sense things

There's basically no debloating going on in Sense with a Viper rom.

The Team Venom philosophy is to stay true to the distribution, cut back only what's necessary for bringing in the Venom Tweaks and Hub - and then tuning for performance.

Personally, I found that debloating just a little by little over time worked for me last go around. Truthfully, I never really finished - it became one of those things that I was always going to get around to.

If you like debloated Sense, those options are available in roms too - check out Bad Seed's Tranquil M8 rom.

Remember - with s-off and a nandroid backup, it only costs you a little storage to try out the others, and restore back to whatever seems most trustworthy while deciding which one to try next (or just - try next! lol).

The keys to success are -

- always check the MD5 sum to make sure you're starting out with a good download before installing the rom

- always follow the teams' instructions on what they want you to do for a rom installation

- always go to TWRP, Wipe, Advanced and choose to wipe out the cache and Dalvik cache on any rom restore or new installation (and TWRP tends to guide you right there with a button on installs - do it anyway with restores - trust me, it's important)

Hope that helps!
 
Getting ready to take a look @ another SENSE-Based ROM: (NV).

Gimme a few hours or so & I'll start another thread for it/give my 2
 
great post thanks EM

im still s-on so that does cut down the choice some what i think

im actually enjoying the whole fairly stock sense feel, as it makes a change from the aosp/hybrid roms i always used on my s3 ...... but give it time ;)

cheers
 
great post thanks EM

im still s-on so that does cut down the choice some what i think

It depends on a lot of firmware factors.

You can open (almost) any rom zip on your PC if it has a non-standard Sense kernel and find it with the file name: boot.img

Extract that to your fastboot folder. Then go into fastboot USB mode and say -

fastboot flash boot boot.img

Do that right after trying any rom that bootloops.

S-off means you don't have to do that - and you don't have to worry about bootloops, everything installs.

And that's the worst that will happen - a bootloop (cue scary music, followed by me throwing confetti and saying Don't Panic).

To cure that, you restore to whatever stock-ish rom you like, and you grab your stock rom (the real stock rom), extract its boot.img - follow the procedure above - and profit.

I know that's not supposed to work on HTCs.

I also know I've seen that work more than once.

All comes down to how much experimenting you want to do.
 
:-D yes i would be scared by a boot loop... even when a first install pauses I'm worried! :-D
..thanks EM... must sort out that s off business :-)
 
It depends on a lot of firmware factors.

You can open (almost) any rom zip on your PC if it has a non-standard Sense kernel and find it with the file name: boot.img

Extract that to your fastboot folder. Then go into fastboot USB mode and say -

fastboot flash boot boot.img

Do that right after trying any rom that bootloops.

S-off means you don't have to do that - and you don't have to worry about bootloops, everything installs.

And that's the worst that will happen - a bootloop (cue scary music, followed by me throwing confetti and saying Don't Panic).

To cure that, you restore to whatever stock-ish rom you like, and you grab your stock rom (the real stock rom), extract its boot.img - follow the procedure above - and profit.

I know that's not supposed to work on HTCs.

I also know I've seen that work more than once.

All comes down to how much experimenting you want to do.

Just so im getting this right. Extracting the boot.img from the zip file will cure a bootloop from a firmware mismatch?

How would a firmware mismatch happen? I thought you could flash to any other firmware (obviously in this case ones made for the international, not just any old carrier) as long as the hboot matched?

Man this HTC stuff is a lot harder than Samsung :p
 
Just so im getting this right. Extracting the boot.img from the zip file will cure a bootloop from a firmware mismatch?

How would a firmware mismatch happen? I thought you could flash to any other firmware (obviously in this case ones made for the international, not just any old carrier) as long as the hboot matched?

Man this HTC stuff is a lot harder than Samsung :p

No.

If you're not s-off, then depending on the model and the installer, when you flash a rom, the boot.img portion won't flash.

So, you extract it and flash it separately.

If the rom in question uses the same boot.img as other roms - such as tends to happen a lot with oem based roms - the boot.img is identical anyway and you wouldn't notice that the boot.img is what you had before.

Get s-off, it's easier.
 
So if i flashed a ROM made for a different carrier then it would be the boot.img that would cause the bootloop?

Looks like i am gonna have to go for s-off. Do i need to be on a stock ROM for s-off or can i be running a ROM?
 
Quite possibly the boot.img is the culprit, but not always. Different carriers get different variants to work on their network. So sometimes even the Rom is different. You need to be sure you read the OP of a Rom to check if it will work for your variant or not. There are a few Roms in the International One forum that will work for the Sprint variant, but not many. They use GSM radio technology, so the hardware is different. 9 times outta 10, you'll end up in a bootloop or worse. Hence why we stress you gotta do your due diligence. :)

For S-off you want to be on the stock rooted Rom, with the stock kernel (boot.img), no mods. This goes for Firewater, and if that doesn't work, Sunshine.
 
Cheers guys :thumb: For the ROMs ive been checking to make sure what variants they are anyway and so far only flashed one ROM (ARHD) and everything went well.

Looks like im gonna have to test my ability to take my phone back to stock. In my excitement to root the phone i completely forgot to back a backup of the completely stock phone so with have to find a stock ROM :thumb:
 
Back
Top Bottom