It seems that cyanogenmod is very popular with other phone users, and everyone seems to want it for the vibrant as well... but can i just ask what differs cyanogenmod from say trigger bionix or eugebes rom?
It seems like there is a crapton more work involved and that you could possibly brick your phone.
Sent from my SGH-T959 using XDA Premium App
It's a pure aosp rom, that's why people go crazy about it. I ran cm on my g1 back in the day and it made it a completely different phone.
Sent from my GT-I9000 using XDA Premium App
http://lmgtfy.com/?q=whats+so+good+about+cm7+mod
Go there
How you comparing trigger with cm7... think man, gb 2.3.3 and aosp... builded from scratch... code by code... it dont have a bit of tw. Well it dont even contain 2 frameworks like tw or any other...
Sent From My CM7 HTC Glacier Running @1.401 GHz
**delete **
Sent from my GT-I9000 using XDA Premium App
Because it's a pure AOSP ROM. Build from scratch (well, a base).
Try it if you really want to know, except for GPS issues and not so good battery life, it is AMAZING.
cashyftw said:
http://lmgtfy.com/?q=whats+so+good+about+cm7+mod
Go there
Click to expand...
Click to collapse
Lol i fount it funny, never knew about that kind of searchs, haha nice...
Sent From My CM7 HTC Glacier Running @1.401 GHz
CM is the granddaddy of AOSP ROMs. Cyanogen and his team are devs cutting actual code, writing their own device drivers and system apps. The entire CM ROM is compiled from customized source code.
Contrast this with the approach taken by ROM chefs who largely assemble their ROMs out of precompiled components borrowed from different releases of the vendor's ROM binary plus some configuration hacking where the odd component has been successfully decompiled.
That's not to belittle the achievements of the top chefs in any way - it's frankly astonishing that this school is viable at all, they seem to be operating mostly blind so it's more art than engineering in some respects.
But both approaches have their strengths. OEMs like HTC with access to detailed specs for their own hardware and low-level API's can produce better drivers and better apps that work closely rough drivers (like the camera app), but at the other extreme, AOSP code can sometimes include features the vendor left out or even implement a completely rethought and altogether superior design.
It's unfortunate that the closed source strategy of vendors with their signed modules often denies us the opportunity to combine the best of both. I'm particularly thinking of how juice defender can only control the toggling between 2G/3G radio on AOSP ROMs because the radio driver will only respond to code signed with the same key as itself. Aint signed code wonderful, eh?
Sent from my Desire HD using Tapatalk
Another reason is quick updates.
CM has updates before any major manufacturer and they're updating phones that manufacturers abandoned a long time ago.
I ran CM on my G1 and I've been seriously considering making the jump with my Vibrant any day now.
for me, it's long term support. once cm adds a phone, then that phone is typically going to be able to easily be upgraded to the newest android os and typically very shortly after it comes out. like many others, i had a g1 and because i cm i was able to get more life out of the device by ocing it and updating it 2.1 and 2.2.
go install cm7 and you will see what's good about it. the only major problem with it right now is no gps. after running cm7 i went back to biwinning and bionix, but that was short lived, i'm back on cm7 because having 2.3.3 > gps, for me.
Yep, CM7 4/21 nightly + cm7 Kang kernel, overclocked to 1.2 GHz + ondemand Governor equals the fastest I have gotten my Vibrant.
I have a Nexus S, right now it's stock 2.3.4 but when Cyanogenmod gets updated to 2.3.4 then for sure I will flash it. Why? When I already have stock? Well have you seen the the things you can do on that thing? You can add a music widget built right into the lockscreen, change themes with ease, change what the search key does, change the lock screen style, and the browser is improved ( incognito mode for one) you also get some fixes that Google almost never fixes, plus stock 2.3.3-2.3.4 disables Facebook sync with your contacts, however Cyanogenmod removes this thing that Google put... basically you can customize the thing like crazy. Plus it still remains stock, but the entire experience can change. I made my Nexus S look like Sense, changed how the notification bar and other aspects of the UI looked, changed the launcher to a themed launcher pro and changed the lockscreen to lense style, boom Sense style completely. Also if your device isn't stock you can install it and you make it stock, a problem with Sense is that a lot of the time the software disables things that some apps might need ( making things like wiimotes not work on it) but if you have Cyanogenmod, it eliminates that.
Sent from my Xoom
How is the battery life when using cm7 on our vibrant?
Too bad it doesnt have gps i actually use it so ill have to wait until gps works on it
Sent from my SGH-T959 using XDA Premium App
Related
What is cynagenmod and what's so "great" about it?
Thanks!
Sent from my SGH-T959 using XDA App
At the time cyanogen brought a lot of features we now use everyday. Os optimizations apps to sd. Things lf that nature. It is fully opensource and open to anyone to use.
I am fascinated and captivated by the vibrant screen on my epic galaxy s.
Nabeel10 said:
What is cynagenmod and what's so "great" about it?
Thanks!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The ability to customize the phone, the stability, the speed, the battery life, and it gives phones the the g1/dream froyo which I guess was deemed impossible. It also gives users great support and updates quite frequently.
duboi97 said:
The ability to customize the phone, the stability, the speed, the battery life, and it gives phones the the g1/dream froyo which I guess was deemed impossible. It also gives users great support and updates quite frequently.
Click to expand...
Click to collapse
Plus it is a large group of people that work collectively together, they along with a few others are the ones that the leading "cutting edge" devs........ they blazed the trail and now all of us and the current devs benefit from their work.
Yea. Since its built from scratch it is faster than any roms here.
The g1 roms were same speed rooted or not
When cm came it was fast! And then a rom based on cm called super d was even faster and then a european rom was fastest!
So what I'm trying to say is, CM is and will be faster than the ROMs built here overclocked or not because the ROMs found here are based on the Official Froyo made by Samsung not a Vanilla Gingerbread rom built from scratch
So I think something built frrom scratch is better than something just modified and themed
Sent from my SGH-T959 using XDA App
It's built from scratch using the AOSP source, which a lot of ROMs are not (many ROMs are merely modified versions of existing stock ROMs).
It has an extensive amount of customization and flexibility beyond any other ROM I've ever used on an Android device.
I don't mind the ROM I'm running on my Vibrant, but I miss CyanogenMod. Since the CM7 release candidate for the MT4G just hit, I think it's time for me to change it up a bit. I'm tired of my short-range wifi (seriously, less than full bars when I'm only six feet away from my 802.11n router?), non-functional GPS and totally wonky compass, anyway.
I think one of its advantages is the sheer size of the community, if you've ever used various Linux distributions the same concept applies. When your user base expands to the point where you've got dozens if not hundred of loyal users posting guides, reporting bugs, requesting features, and answering new user's questions the community really feeds on itself and builds momentum. Cyanogen is largely responsible for a lot of the momentum in the rom community, and I know it's brought more people to the community than almost any other project.
A lot of things.
The cyanogenmod options alone are worth it - VM Heap, swap, JIT, compcache, et cetera. Granted these things are more relevant to lower end devices. Then there's the native ADW launcher integration. I've never been about to replace the stock launcher with ADW and get the same results.
It's really just its use in practice. Everything works, the interface is very instant/responsive (no jagged animations/scrolling, ever), no force closes, lots of mods/hacks for it from the community, which in general is very scrutinous about performance/stability hangups. Battery life twice what you're use to.
They're the only ROM team I've donated to. I flashed hundreds of roms when I had my Magic (one of the hardware-weakest android phones) but CM is what kept it up to par, giving me an extra generation's life out of it.
I personally love all the features built in, like pulldown menu modifications, as well as pretty much customizing every aspect, NO roms like that exist for our Vibrants..
It is Cyan in color, and mod like the british music scene duh!
hmm... I might have to give cm7 a try once they get it working on the vibrant. They are working on it right? If the manufactures were smart, they would give a pre-release phone to those guys before it's available to the public. Of course, the carriers may not like it. I just purchased my vibrant 3 weeks ago (former iphone 4 user). I tried a few darkyy's roms, then toxic, then finally I stuck with trigger. I'm very satisfied with it - mainly b/c everything works nice and smooth.
I see I'm a bit late but yes, Trigger is awesome. I tried flashing others and I always come back after 2days tops.... For some reason, Trigger runs so much smoother than the other ROMs on my phone... And I have tried 2.2.1(Honestly I dont get the difference) and I am not a fan of the 2.3.3 because most say the GPS doesn't work and I use my GPS at work, yes through my phone(I'm cheap). Plus that is one of my reasons for buying a "smart phone" It has everything at your finger tips, or supposed to at least right. Hope your having fun.,..... BTW, CM is freaking awesome on every device I have seen it on...... I'm actually curious to know why it's not on the Vibrant as an official build but eh..... It will come when it's ready I suppose
Hi all,
First of all, I'm amazed and gobsmacked at how much work all the devs put into their respective ROM's, it's amazing the effort and hard work ppl put in. Passion is alive and well on XDA
Now, to business. I have my Galaxy SII, a Galaxy S, and an Acer Iconia A500. I've flashed them all with their respective ICS. I would think (and hope) that probably out of all of them, the SII has the biggest dev base and most power. The ICS ROMs for the A500 and S are almost perfect. They run completely vanilla with no or almost no bloat, they look and behave the same (icons for network activity inside the bars for example, contacts app looks the same) and have had no hiccups whatsoever.
Come the SII, the only ROMs I've seen are cooked from Samsung sources with their phone and contacts apps, they crash and reboot and if it weren't that I have gone past the point of no return in regard to effort I'd have gone back to Gingerbread days ago.
Is anyone out there developing a completely vanilla "Google" rom that isn't themed to look like ICS, but actually uses the ICS apps etc. I can't understand how the Iconia and SI can have this while the SII seemingly doesn't.
Can anyone open my eyes on this? I'd love to get something as stable onto my SII as I have with my other devices, ICS is brilliant to use on them...and barely bearable on my beloved SII.
Cheers
<:3)~
Ummmm correct me if I am wrong but that's exactly what the CM team are trying yo to do....
And you can already download and install that, so long as you are happy with the bugs at present.
Unless you meant something else???
Sent from my GT-I9100 using XDA App
You miss reading the cm9 thread. Check it out....its still alpha.
Sent from my GT-I9100 using Tapatalk
I'm more curious about the fact I would have thought the SII having a bigger user and dev base...certainly more than the A500 I thought it would have the most stable and mature code base - yet it seems the opposite is true.
I've been running 4.0.3 on my SI for weeks now and its never bugged out. Installed the A500...and Oh wow its like a brand new tablet!! I wonder is it because of Exynos or some other reason we can't have the same stability and performance right now.
Sent from my Acer Iconia A500 using Tapatalk
Your ignorance and disrespect is pretty bad (even if you don't mean it). I think you should do some reading for a while and get yourself acquainted with what's involved.
I didn't ask this to be dissed by someone...I'm sure even you would agree the development cycle and challenges for all three devices would be similar given they all use different processors. So is it easier to compile for the A8 and Tegra than the A9?
I have been looking and downloading a number of ROMs...and if someone has created a ROM in a similar vein to Thor's on the A500 and Onecosmic's on the SI, well I'd be grateful for the heads up...in fact I'm just about to download and test the Pure ROM I just spied over in dev...so see how that goes. Still I'd be happy for someones *constructive* input.
Of course I'm claiming ignorance...if I knew I wouldn't ask...geez lol
Sent from my Acer Iconia A500 using Tapatalk
It's a wonder no one bothers doing a straight AOSP compile for any device, really. CyanogenMod comes the closest. There are a few people who played with doing a straight AOSP, but they base it off CM's work and strip out the extras.
When I wanted the AOSP experience with Gapps, I installed CM7 on my SGS and installed the stock Gingerbread launcher. It was the closest I got.
Trebuchet is basically the stock ICS launcher with features added, so it won't be so bad. You can also replace it with the stock launcher as well.
Try Airbus 360s ics rom that's aosp and is fantastic he should be releasing beta 2 tonight.
sent from my iPhone 4S.
haha I bet that confused ya
You're question is a bit noob so don't expect much answers.
Here is a short one to sum it for you:
AOSP - Pure android base without modification.
CM - almost pure with modifications.
STOCK - Hardware Manufacturer (eg. Samsung's) "official originated" release.
Stock - can have it all. CAUSE - Samsung has sources and support/docs for ALL hardware API of the device.
CM/STOCK - While there are some changes BOTH use the same origin.
To sum it, for proper functionality BOTH use SAME kernel/libs base.
So if some hardware functionality broken in one it'll be broken in other =
If CM9 haz no h/w decoding === APPLIES for AOSP.
Another thing to keep in mind, CM9 currently is in the process of adding CM features so current builds are very close to AOSP with functionality.
SUM IT UP:
if (CM9 != working) AOSP.isNotWorking()!
ttg said:
if (CM9 != working) AOSP.isNotWorking()!
Click to expand...
Click to collapse
That's a piece of horrible code, dude
Please help me to understand this..........
If android runs on top of lunix
and all android versions eclair gb, ics etc start off as basically aosp then get maufacturer specific things like blur and sense.
Why is it so hard for CM9 and 10 to fully work on the E3D when CM7 worked perfectly on the Evo4g which are both htc phones?
Its a random question and even though I just recently became a member here, ive been with XDA since i hade the original moto click which was 2 yrs ago.
Also,
What do I need to do to create themes? Ive been wanting to for a while.
Thx in advance
Deep breath. It basically comes down to the huge variety of hardware. Linux has to support hardware in it's kernel (basically a software layer that tells the operating system how to use that hardware) and each new variant of the kernel is supposed to be backward compatible (though support for very old hardware is dropped so the kernel doesn't get out of control). Now Android is a completely different branch of linux (at the moment), and each manufacturer further branches aosp and creates a different kernel for every mobile phone with different hardware. The manufacturers have to release the kernel back to the community after they upgrade but this is slow and even when they do the kernel only supports the variant of android (in this case sense). Finally if they don't release an OS upgrade at all then the kernel becomes outdated and won't support features in the new OS.
Devs feel free to correct me...
Sent from my Evo 3D GSM using xda app-developers app
CM7 is by now quite old, meaning developers have had A LOT of time to test, modify, run and perfect it, even several years ago a lot of phones had perfect CM7 ports/builds.
Both CM9 and CM10 are still quite new, and thus developers have not had that much time to modify it to run as well as CM7, but in time it'll get there, no doubt about it.
And it also depends on which developers are actively working on developing for a specific phone. As for example we now have Agrabren working on a CM10 build (GSM side) doing amazing work, while other phones do not have such developers, thus it will take longer time for those phones to get perfected.
As for the themes, it depends on what ROM you're using. There are several different ways to theme something, and they're very different if you're running either Sense 3, Sense 3.6, Sense 4, CM7, CM9, CM10 or MIUI 2.3 or MIUI 4 (etc.), so you'll have to be more specific. But it would be a good start to look in the "Themes and Apps" sub forum.
grrratt said:
Deep breath. It basically comes down to the huge variety of hardware. Linux has to support hardware in it's kernel (basically a software layer that tells the operating system how to use that hardware) and each new variant of the kernel is supposed to be backward compatible (though support for very old hardware is dropped so the kernel doesn't get out of control). Now Android is a completely different branch of linux (at the moment), and each manufacturer further branches aosp and creates a different kernel for every mobile phone with different hardware. The manufacturers have to release the kernel back to the community after they upgrade but this is slow and even when they do the kernel only supports the variant of android (in this case sense). Finally if they don't release an OS upgrade at all then the kernel becomes outdated and won't support features in the new OS.
Devs feel free to correct me...
Sent from my Evo 3D GSM using xda app-developers app
Click to expand...
Click to collapse
Moonbloom said:
CM7 is by now quite old, meaning developers have had A LOT of time to test, modify, run and perfect it, even several years ago a lot of phones had perfect CM7 ports/builds.
Both CM9 and CM10 are still quite new, and thus developers have not had that much time to modify it to run as well as CM7, but in time it'll get there, no doubt about it.
And it also depends on which developers are actively working on developing for a specific phone. As for example we now have Agrabren working on a CM10 build (GSM side) doing amazing work, while other phones do not have such developers, thus it will take longer time for those phones to get perfected.
As for the themes, it depends on what ROM you're using. There are several different ways to theme something, and they're very different if you're running either Sense 3, Sense 3.6, Sense 4, CM7, CM9, CM10 or MIUI 2.3 or MIUI 4 (etc.), so you'll have to be more specific. But it would be a good start to look in the "Themes and Apps" sub forum.
Click to expand...
Click to collapse
Hey thx guys, I got a better understanding now. I appreciate you taking the time to explain that to me.
As far as themes, i will look into that thread.
BTW this site is awesome. You guys have done a great job making all of this accessible for people who refuse to hampered by the limits of a locked s-on phone.
What is the difference between Neo's Rage CM rom and Project Rachel/CounterShrike? I know that CounterShrike has the bottom status bar mod, but in terms of battery life/speed/performance, what's the difference and which one is better?
If u want to know the differences read all of the ops. Everything else is a matter of opinion. However I use neos rage.
Sent from my Rezound using xda app-developers app
CounterShrike is all about features and options. I'm trying to put as many mods in as I can in the ROM without affecting stability, and I'm trying to bring in some bugfixes along the way. It's otherwise fairly stock...I'm not really taking anything out, and I'm also not doing any tweaks outside of those that come along in the code commits I put in. I leave the tweaks up to end user preference. Neo, on the other hand, is all about minimalism and tweaks. He's bringing some features in, but not nearly as many as me, but he's also heavily debloating the ROM, and tweaking things to try to maximize performance and battery life.
I like Neo and think he does great work. In fact, it's because of him and his mentoring that I'm at the point that I can do what I'm doing with CounterShrike. My personal opinion is that you can't go wrong with either one, but they are two fundamentally different ROM philosophies, and think having them both benefits the community. It really just comes down to what you are looking for.
Spend at least three days running each one, and make sure you've explored every option in the menu before changing to the other one.
Sent from my ADR6425LVW using xda premium
One small difference is that the Counterstrike camera has working live face detection, whereas the one on RAGE currently does not.
I've been researching if the fabled MIUI camera UI can be ported, but in the meantime, Camera JB + from the Play Store is a small but good upgrade over the stock AOSP camera.
Much respect to the both Neo and Shrike for all their hard work.
Sent from my Rezound using Tapatalk 2
Project rachel was my rom that i gave to shrike. So pretty much the same thing. Although I understand he has plans to go further with it
OK I spent eight hours yesterday figuring out how to root my phone.... Success... I was finally able to figure it out.. Thanks for all the tutorials and posts that helped me do it...
I would love some direction in how to find some cool and neat and SAFE AND STABLE Roms to flash.. Is there a site with roms to choose from?? Any help or suggestions is appreciated....
Thank you again everybody
Just look in the android development section in the international forums. Viper rom is really nice, so is Arhd.
Sent from my HTC One
I second ARHD. It depends whether you like sense and want to keep it without all the bloatware, or try something more pure android. I know Google edition ROM is out now, but I like sense too much to try it. Heres some links to arhd and ge.
http://forum.xda-developers.com/showthread.php?t=2183023
http://forum.xda-developers.com/showthread.php?t=2356654
Ok great thanks for the help.... I just got home from work and can't wait to spend the rest of the day flashing different roms.. Lol. What fun! This is a thousand times better than jail breaking... I was never able to flash different firm wares on an iPhone... This is a thousand times better
Pro tip: almost all roms on here are stable and safe unless they have alpha or beta in the title
Sent from my HTC One using Tapatalk 4 Beta
Nick281051 said:
Pro tip: almost all roms on here are stable and safe unless they have alpha or beta in the title
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you for the "pro tip." I love this place.. I'm running a GPE rom and having fun... I think I want to flash something I can theme with a lot of choices... I'll look around and see if I can find a rom around here that people are theming... Thanks again
OJsakila said:
Thank you for the "pro tip." I love this place.. I'm running a GPE rom and having fun... I think I want to flash something I can theme with a lot of choices... I'll look around and see if I can find a rom around here that people are theming... Thanks again
Click to expand...
Click to collapse
For maximum themeing capabilities you can go with any of the AOSP (Android Open Source Project) based roms like Cyanogenmod (CM) AOKP, Vanilla rootbox, Slimbean, etc. They all support custom theming with hundreds uf not thousands of downloadable comaptible theme files in the Google Play store.
They are much more customizable than the GPe roms as well. But be warned, what you gain in customizability and cool factor you may tradeoff in optimal function of the phone features itself, namely camera, sound, call audio quality and BT call/streaming audio reliability.
The reason is because GPe and vanilla android 4.2.2 may look identical on the surface, but are different underneath. The GPe of the One runs on a stock Sense OS heavily modified to look and work like vanilla Android IU, but the underlying OS framework works best with the HTC hardware. While AOSP roms have hardware compatibility issues. You'll see this is a regular issue on those threads. I was using CM until the GPe roms were released. I loved the user options on CM and AOKP but was frustrated by terrible call quality and unstable BT connections. I switched to one of the GPe based roms and I gave up some cool features, but my phone works too well as a phone now to switch back.
Most people using GPe based roms are hoping the developers will adopt and incorporate the cool custom ideas from CM based roms like UI options, themes, adjustable control tile toggles, navigation bar mods, etc.
Sent from my Nexus 7 using Tapatalk 2
kayone73 said:
For maximum themeing capabilities you can go with any of the AOSP (Android Open Source Project) based roms like Cyanogenmod (CM) AOKP, Vanilla rootbox, Slimbean, etc. They all support custom theming with hundreds uf not thousands of downloadable comaptible theme files in the Google Play store.
They are much more customizable than the GPe roms as well. But be warned, what you gain in customizability and cool factor you may tradeoff in optimal function of the phone features itself, namely camera, sound, call audio quality and BT call/streaming audio reliability.
The reason is because GPe and vanilla android 4.2.2 may look identical on the surface, but are different underneath. The GPe of the One runs on a stock Sense OS heavily modified to look and work like vanilla Android IU, but the underlying OS framework works best with the HTC hardware. While AOSP roms have hardware compatibility issues. You'll see this is a regular issue on those threads. I was using CM until the GPe roms were released. I loved the user options on CM and AOKP but was frustrated by terrible call quality and unstable BT connections. I switched to one of the GPe based roms and I gave up some cool features, but my phone works too well as a phone now to switch back.
Most people using GPe based roms are hoping the developers will adopt and incorporate the cool custom ideas from CM based roms like UI options, themes, adjustable control tile toggles, navigation bar mods, etc.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
The Sense version isn't heavily modified to look like Vanilla, its heavily modified to look like Sense. All carriers start with vanilla.
As for the features--because there's a Google Play Edition (GPE). The GPE devices run vanilla android--what we call AOSP, after the Android Open Source Project...which is the project Google created in order to "Open Source" Android, make it available to everyone, and provide for a "Google Experience".
The Google Experience" comes stock on the Google Play Edition devices, and guarantees that the device comes the way Android is/was intended to be, and is designed far better in terms of functionality and usability than the Firmware(s) created by Samsung, HTC, and other manufacturers, which add additional software to run on top of the Google Experience software in order to differentiate themselves from one another, and be able to say that their phones are better. In reality their software might look better and have a few extra features, but it's slower, can take years to update, and in the end, is often more restrictive.
Because these devices require Google certification, all features are required to be in working order. And because Android is so modular, you're guaranteed to have all the drivers, libraries, etc. you need to use all the base hardware available on the device. This means that beats audio, Wifi , Bluetooth, GPS, 3d, Sound, etc. Will all work. The only thing that won't work is the IR blaster on top of the device (for turning your device into a universal remote control to change channels with on your TV, blue ray player, etc. ), and since updates come from the manufacturer and not Google, it's believed that an update may enable this in the future.
By the way, Engadget did a side by side during their review, and stated that picture quality wasn't any better on the Sense version---which means that you'll get great photos on both devices.
That's the reality. Some have made some wild speculations, and have come to some wild conclusions (entirely subjective and disproved), but this all comes from extremely authoritative reviewers...people who are given devices and whos career depends on spending a ton of time analysing these devices, and getting it right.
Sent from my Transformer TF101 using XDA Premium HD app
Jamesyboy said:
The Sense version isn't heavily modified to look like Vanilla, its heavily modified to look like Sense. All carriers start with vanilla.
As for the features--because there's a Google Play Edition (GPE). The GPE devices run vanilla android--what we call AOSP, after the Android Open Source Project...which is the project Google created in order to "Open Source" Android, make it available to everyone, and provide for a "Google Experience".
Click to expand...
Click to collapse
Thanks but you're misinterpreting what I was saying.
Sent from my Nexus 7 using Tapatalk 2
CleanROM 3.0 <stock look and feel with added performance and perks
Just so I understand this correctly, if we need to get S-OFF to flash ROMs such as Viper due to it being 1.28, correct?
Sent from my HTC One using Tapatalk 2
nope s-off is not needed. If you still can, obtain the unlock key from HTCDEV.com and use that to unlock your bootloader (this will wipe your phone completely), install a custom recovery such as CWM or TWRP, then install either superuser or supersu for the root
Then flash away
1. http://www.youtube.com/watch?v=QU7vi388dMk
2. http://www.youtube.com/watch?v=rRkAHw_GmIs
Thank you so much! So what exactly does S-OFF allow you to do besides customizing the bootloader?
Sent from my HTC One using Tapatalk 2
tanner4137 said:
Thank you so much! So what exactly does S-OFF allow you to do besides customizing the bootloader?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Restore your phone completely back to pre-rooted stock condition with the stock Sense ruu. Just like when you got it from the store.
Also is required if you want to reflash/update the phone firmware (which will completely wipe out phone data just like unlocking the bootloader).
Sent from my Nexus 7 using Tapatalk 2
kayone73 said:
Restore your phone completely back to pre-rooted stock condition with the stock Sense ruu. Just like when you got it from the store.
Also is required if you want to reflash/update the phone firmware (which will completely wipe out phone data just like unlocking the bootloader).
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
And do we need to update the firmware to install any of these ROMs?
Sent from my HTC One using Tapatalk 2
tanner4137 said:
And do we need to update the firmware to install any of these ROMs?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
NO.
Stop being so fixated on updating your firmware. Read more and ask fewer questions.
Sent from my HTC One