Related
Hi guys... I have a few questions for you about my Hero. Forgive me for not yet having the same level of knowledge that many of you guys have. I am certain that I can contribute in some way, as well. My phone details:
Firmware version: 1.5
Baseband version: 1.04.01.09.21
Kernel version: 2.6.27-533ce29d
Build number: 1.56.651.2 CL5027
Software version: 1.56.651.2
Hardware version: 0002
1. I've read several stories where a number of phones were returned because they couldn't be updated when the new update was released. Is this an absolute fact, that it can't be updated, or is there an error in code somewhere that made it reject the update and there is a known workaround? The answer to this question obviously dictates my forward motion.
I have the typical problem apps, and am getting no joy from youtube. Presently, I'm surfing with good speeds, but market is non-existent.
I like having Sprint tv, when I'm having to sit and wait somewhere.
I have time today and tomorrow to get things ironed out, but will be extrmemly busy after that, like 20 hours a day studying. I'm hoping to get some direction that will give me complete functionality, but will require the least setup. I am quite computer savy, and repaired this phone, to this point, in a day or 2, without asking a single question of anyone. I traced down problems, and solved issues. Seen APN, and TCP errors (don't believe it completely, since I can authenticate on the web). Know that some issues are url problems, etc.
The following questions are based upon the answer to question number 1.
2. Can this phone be updated?
2a. If yes, What do you recommend... 2.1? What rom do you suggest, for full stock-like functionality? Will I lose Sprint tv? Pointers/direction? (pancake??, superhero??)
2b. If no, What rom do you suggest, for full stock-like functionality? Will I lose Sprint tv? Pointers/direction?
Before repairing the phone, I actually tried to update it from my computer, but it was rejected. I turned off my security software and tried again. I noticed that while using XP sp2, a windows program that was incorporated starting with sp2, DEP (data execution prevention) didn't like the actions that the update was taking, and arrested it very shortly after starting (yet the window cycled forever). I assume that many people wouldn't be this observative, and recognize that this was happening. It was halting an HTC file that utilized storage memory (similar to buffer overrun exploits - the reason DEP halted it), for temporary storage of the files to be used for the update. That file was as follows:
C:\Program Files\HTC\HTC Sync\Mobile Phone Monitor\FsyncServer.exe
And the way to prevent it from continuing to do so is:
1. Click Start
2. Select Control Panel
3. Select System
4. Click the Advanced tab
5. In the Performance region select Settings
6. Click the Data Execute tab in the dialog box that opens
7. Select Turn on DEP for all programs and services except for those I select
8. Click Add.
9. The open dialog box will open. Browse and select your application.
10. Click Open
11. Click Apply
12. Click Ok
I guess what I'm sort of suggesting, is that this might be why anyone ever had problems updating, with the exception that OTA also said there wasn't an update.
So, back to the original question. Is it true that some Heros can't be updated? I don't want to force something, and brick, if you know what I mean. I completed the setting that will allow it to go forward (listed above), but haven't tried to update since. I felt that I really needed to ask you guys first, before I made a mistake that I'd regret. Should I try again? Before I started working on the phone I did try OTA and it said there wasn't an update. Now I don't have that option anymore. After repairing the phone, I've lost updates. Am I stuck with 1.5? With my run of the mill phone desires (except that it be fully functional), should I keep 1.5?
I did see gmail 2.3 apk, but is that compatible with 1.5? This looks like is would solve the market issue, if I could use it.
I did read about gscript and addressing mms (although I'm sure that's very old news to you guys), but if in fact I can't update this phone, it might be one of my only alternatives. If that is my only choice, are their also additional scripts to address everything I need to fix (all the normal issues)?
Additionally, it seems that many apps register with the phone/user. So, when you are using a used phone, many apps are still registered as functional. Does flashing a new rom affect the OS and apps? Will I loose the already registered/functioning apps? With a complete upgrade, will I gain functionality of some key features, but lose all other previously enabled apps? In other words, will I gain update, and market, and lose sprint tv?
I have read a lot. With things the way they should be, I've not been able to quite determine what I need to do. With all this being said, How do I go forward and achieve a fully functioning phone? What is the best choice of path's to take for me?
Rooting? I have seen the one-click, and think I'd be correct in that I need something containing Sense UI. Forgive me for asking a stupid question... but the rom is only the menu accessibility, correct? Is there something straight out of the box setup, or do all roms contain configuration notes?
I'm satisfied with stock features, if they work, and adding other useful things like tethering. Since I'll be so busy, I'll have little time to do much else. But don't get me wrong. I have 10 PC's in my house, with only 2 people living here. I'd love to customize the crap out of it. It's just not going to happen any time soon, due to my brutal study schedule. So for now, I just want it to work like it should, on a B mvno.
Do I go north, south, east, or west????
Could someone chime in that can give me direction, based on everything I've stated. Your response is so graciously appreciated.
Cheers!
Umm well I'm not sure why you're having problems with any update, someone who's far more experienced can maybe tell you but as far as roms I think it depends on whether you like sense or wanna go froyo. Cyanogen mod 6.1 stable (2.2) is nice & highly customizable however there's also AOSP roms (2.2) that some people feel is quicker than cyanogen however they aren't as customizable as cyanogen, in addition there are tons of GREAT themes for both. Also we've had a ton of work on an odex AOSP gingerbread rom (2.3) not yet stable but works good for most & on that note a great themer also put together a themed AOSP gingerbread rom (2.3) that looks good & about stability I'm not so sure on but I would recommend those roms. Although with these roms YES you will lose sprint apps like TV & vvm etc. However people have posted these apks in the theme thread section to work on roms like cyanogen & AOSP. If you do like sense roms there's a couple that are still live in the development section like nfinite & nfx I believe. Hope some of that info helps
Thanks so much for your response. So Cyanogen mod 6.1 stable (2.2) is highly customizable... That's good.
So let me get this straight. I need to:
root (is one-click OS version specific? Can it be used on 1.5?)
backup
save to pc
update to 2.1 (if I can, and it needs to be the rootable version found here)
re-root
and flash Cyanogen
and setup
Is this correct?
inkblots said:
Thanks so much for your response. So Cyanogen mod 6.1 stable (2.2) is highly customizable... That's good.
So let me get this straight. I need to:
root (is one-click OS version specific? Can it be used on 1.5?)
backup
save to pc
update to 2.1 (if I can, and it needs to be the rootable version found here)
re-root
and flash Cyanogen
and setup
Is this correct?
Click to expand...
Click to collapse
Sort of. I can't remember which version I was at when I rooted but I remember I downgraded to do it. But if you go in the development section you will find a thread that shows & gives you what you need to root. So you should root. Then flash a recovery image such as clockwork mod or amon ra. When I rooted I used the recovery from the downloadable app (Rom manager) in the market & that one was clockdwork mod. It's worked great for me so I've been using it ever since. Then backup whatever you are running currently. Then flash whatever rom you want. I'm about to see if I can link you to a root thread then once you do so I can give you a dl link to cm 6.1 stable. Will you be able to root on 1.5?? I don't completely know...
Edit: Ok this is the way I rooted mine, hopefully this will work for you
http://theunlockr.com/2010/09/27/how-to-root-the-htc-hero-androot-method/
Nook Rooting 101
Author’s Note: This may be long, but it provides useful info to those considering Rooting their Nook. It does NOT tell you how to root your Nook. (A sequel is intended to provide that information. But let’s start with this one.)
To the experts: feel free to post with your corrections and condemnations. The hope is that it will be improved and eventually turned into a Sticky for those new to the forum and the process.
“I got a new Nook for my birthday. What’s all this stuff about rooting?”
The Barnes & Noble Nook eReaders share some of the same electronic architecture as many smart phones and tablets. These devices work using the Android Operating system. The factory installed OS (Operating System) of the Nook limits many of the possible advanced features since it was designed primarily to be a reader. Some tech-savvy programmers have learned how to root the Nook devices to more closely emulate advanced features found on many of the Android devices.
Quick detour: Those wanting to root their Nooks are going to run into a lot of terminology. Here is a link to a glossary of many of these terms.
http://www.acertabletforum.com/foru...-dummies-guide-android-terminology-lingo.html
The number of terms addressed within this post will be a much smaller number. But these are terms that you really should understand before attempting to make changes in your Nook.
What is Rooting?
The term “root” comes from the Unix/Linux world and is used to describe a user who has “Superuser” rights or permissions to all the files and programs in the software OS. Regular users can use the software, but cannot make changes. Superuser privileges allow changes to the software code on the device.
“Rooting” means obtaining “superuser” rights to your Nook’s software. You gain the ability to load custom ROMs, install custom themes, increase performance, increase battery life, and the ability to install software that would otherwise cost extra. Rooting is essentially “hacking” your Nook.
ROMs
A stock ROM is the version of the device’s operating system that comes loaded on it when you buy it. The Nook Readers have a stock ROM.
A custom ROM is a fully standalone version of the OS, including the kernel (which makes everything run), apps, services, etc - everything you need to operate the device, except it's customized by someone in some way..
So what does the "customized" part mean? Since Android is open source, developers are free to take stock ROMs, modify them, remove garbage, optimize them, add things, and pretty much do whatever their imagination and skills allow. (And just so you know, they can also write bad programming too.)
Kernals
Another word you’ll frequently see on this site is kernel. Your Nook’s kernel controls much of the communication between the various electronic parts of the unit. An analogy is that the kernel is like programming stored in the Read Only Memory found on desktop and laptop computers. Think of the BIOS (Binary Input Output System). Some portions of the settings in this memory can be changed, such as when you install a hard disk drive. BIOS also allow other settings to be adjusted to suit the preferences of various users. But other portions of the BIOS should not be changed or your computer’s electronics cannot communicate with one another.
That is a pretty close approximation to how the kernel on your Nook is setup. Some portions of the programming were set at the factory and should not be changed. But other portions of the programming can be changed. And updates to the programming for kernels are made available.
Many of the custom ROMS you can load on your Nook will make at least some changes within the kernel of your unit. Just as there are various versions of the custom ROMs. There are versions of the programming for kernels as well. Let’s stop there for now. The subject can quickly get pretty deep. That should be enough for now.
Two Approaches
Some people who want to use one of these custom ROM systems on their Nook just install the MOD on a SD chip. (SD stands for Secure Digital.) All current Nook readers accept a Micro SD chip. A custom ROM can be loaded onto your Nook from this SD chip. Some people choose to Root their Nook with the Android Operating System operating from the SD chip. Then by powering down the Nook, they can remove the SD card. They can then restart their Nook and the regular Barnes & Noble system will operate.
At least some of the custom ROMs allow users to select whether to run the operating system (ROM) installed on the SD card, or run the native Nook operating system. You don’t need to go through the process of inserting or removing the SD card to change the OS. A series of keys are pressed as the Nook is starting to select the ROM you want it to run. This is called dual booting.
The other method of rooting consists of loading the custom ROM into the emmc. (This stands for Embedded Multi- Media Card.) This is the flash memory of your Nook that contains the original Barnes & Noble operating system. Loading the ROM into the emmc means the original B & N operating system is no longer available to run. Many advanced users report the ROMs operate a bit faster and that there are fewer problems when the Nook is run in this manner. But do remember that this means the original operating system on your Nook will no longer run. There are instructions located on this site that include steps to re-install the original system. So, this may not be as drastic a step as it might seem at first glance. There are also programs which will allow you to save all the data settings – including the OS settings currently loaded on your Nook so they can be restored later. That will not be covered in this post.
Those totally new and unfamiliar with Rooting may find it a little safer to use the SD chip method. As they gain more experience and know better what they are doing they may decide to venture out and try the emmc method for the potential advantages this method offers.
The Downside Of Custom ROMs
Of course, there are dangers of using custom ROMs which you should be aware of.
You May Void Your Warranty
As long as we’re talking about risks, this one needs to be mentioned. It's possible that custom rooting might void your warranty. The manufacturer might be able to tell that the Nook has had a custom ROM installed and not honor the warranty, in case you need to use it. Barnes & Noble hasn’t acted hostile to rooting yet, but that could change.
Something Could Go Wrong
First of all, something may go wrong with the flashing process (that's the process of installing a custom ROM) and leave your Nook in a bricked state. A Bricked Nook means it won’t operate. The chances of this are relatively low – especially if you use the SD chip method. And most of the time you can restore your Nook back to normal. Please take note of the phrase “most of the time”. You should understand that a bricked Nook is a possibility that can happen.
Try to go for a custom ROM that has been tested by time and has lots of positive feedback from users on this site. You are more likely to be successful with such a ROM.
Other Potential Problems
Custom ROMs could have bugs. Bugs are mistakes in the programming. Some are minor and won’t cause big problems. But others can be more serious.
There are appropriate locations on this site where you can post problems due to bugs. Those who post in the ROM forum will likely get an answer back and the bug will probably be acknowledged. Experienced users may even suggest methods to fix the problem.
So What‘s the Bottom Line?
Many of the people at this site have determined that the potential benefits of running these custom ROMs outweigh the risks. There are lots of experienced people here who will offer their advice if you decide to try this. But it is ultimately your responsibility to consider the risks and benefits in deciding what to do.
Quick detour: Let’s be realistic. Your Nook is never going to be an I-Phone. It was designed to be an eReader. (So was the Kindle.) Rooting can add features and capabilities to your Nook that Barnes & Noble probably won’t ever include in their stock ROMs. But rooting won’t really turn your Nook into a smart phone.
“But there are so many choices!”
Yes there are. Let’s try to understand why this is a good thing. Apple and Microsoft own the rights and hold patents on their operating systems. They jealously guard their secrets and strictly enforce their patents. And they make money selling their operating systems.
Unix is also a patented operating system. Linux is an open source operating system based on Unix. It isn’t really owned by anyone. The concept allows many users to tinker with it to improve it. The Android operating system is loosely based on Linux and is also open-source. Developers take stock ROMs and modify them to create their own unique versions. Developers of custom ROMs are able ptimize the software, unlock built-in features, and create an even better version of the Android software. The Android developers who make these custom ROMs release the software to the general public free of charge. We are fortunate to have these developers constantly working and freely sharing these custom ROMs available to everyone.
Stable versus Cool
Since ROMs are constantly being developed by many people, there are multiple flavors of ROMs available to us. Anyone who has ever done any programming knows that sometimes your new code fixes one problem but creates others. Programmers generally call these bugs.
A major portion of the ROMs may work OK, but there may be bugs in portions of the code. Groups of developers collaborate and post their versions of a MOD to be checked out and tested by other users to discover and fix all the bugs.
Then there are some general flavors of the Android system that have become established and are recognized by many. Let’s consider a few of those since you will see these mentioned frequently on this site.
Since April 2009, each Android version has been developed using a codename based on a dessert item. Released in alphabetical order, the names were Cupcake, Donut, Éclair, Froyo, Gingerbread, Honeycomb and Ice Cream Sandwich.
The Android versions distributed within the lifetime of the Nook include:
o Android 2.1 (codename Eclair)
o Android 2.2 (codename Froyo)
o Android 2.3 (codename Gingerbread)
o Android 3.0 (codename Honeycomb)
Quick detour: One further issue confusing to nubes is that at least some people will refer to a MOD by its Android number, example: 2.3. Others will use a number related to its codename, example CM7.0. Remember these people are really into this stuff. These numbers and differences really stick in their heads. Rule of thumb, if the number is below 4, it’s probably the Android number.
Let’s look at these individually. We’ll use the codenames in this list.
Eclair
Eclair is what your Barnes & Noble Nook Color runs as delivered. And even they are replacing it with Froyo.
Froyo
Many consider Froyo an improvement over Éclair. It has been in use for some time and is considered a stable platform for the Nook. Barnes & Noble is currently (as of 2/5/2012) loading this system using a method called push to update Nooks to run a stripped down version of Froyo. It is important to understand that the B & N version does not have all the features of some of the custom Froyo ROMs.
Gingerbread
The Gingerbread version that many people use has become known as CyanogenMod 7. That’s right – sometimes the system is called Gingerbread and sometimes it is called CyanogenMod 7, though many just refer to it as CM7. It was developed from the official Android Gingerbread source code, but was modified for many smart phones. There are many versions of this that will run on Nooks of various kinds. As of this writing, many consider this a good choice for a Nook operating system. It blends many recent features with at least some degree of stability. The CM 7 releases includes Bluetooth support for the Nook, meaning that you can use Bluetooth keyboards and headsets! It should be noted that Bluetooth support is still evolving.
Honeycomb
This Android system first showed up on the Motorola Xoom tablet. It offers some new features, but has not been released by the official development community. Because such development is constantly underway, some may post test versions for downloading. Be careful! This ROM is still very much in the developmental process. As an example, a few developers have been trying to take features of Honeycomb and include them in updated versions of Gingerbread. One of these versions has been given its own name: phiremod nook.
Generally, Éclair and Froyo, are considered to be stable and mostly bug free. Some versions of Gingerbread are close to being bug free, while other Gingerbread versions are still being sliced, diced, tweaked and tested. Honeycomb is still being tested. If this post stays on this site for a few months, there may be newer and more stable versions of Gingerbread. Or a stable version of Honeycomb for the Nook may become available. And some are experimenting with newer Android systems, like one called IceCreamSandwich. (Remember that this is being written in February of 2012.)
FYI: there are even new flavors of these general ROMS. There is also CM7.1 and CM7.2. And there is a version out there called CM9. So the development community is hard at work tinkering and tweaking.
Finally, as you start to explore and consider MODs for your Nook, you will often see some of these letters in the names of custom MODs.
Stable versions are those where all known issues have been addressed and resolved. This version is for everyday use.
-test / -RC versions are similar to the experimental versions, but are in the final stages of testing before being declared as "stable". There may be a few bugs left, but this version is usually stable enough for everyday use.
Experimental / -alpha versions are those where new features are being added, modified, and tweaked, and there are known bugs that are being worked on. This version is for beta / alpha testers.
Nightly builds are daily compiled builds from source. This version therefore has the latest features & tweaks, but it is also the mostly likely to have bugs and issues. These versions are probably poor choices for nubes.
So which do you want to use? Éclair came on your Nook. And currently, Barnes and Noble is pushing their stock version of Froyo out over the Internet automatically to your Nook. Gingerbread – going by the name of CyanogenMod7.0 – may be a good choice for starting out, as of the date of this writing. Yes, you can upgrade this to later versions as you become familiar with what is out there and how to root your Nook.
End of the lesson.
Hope this information was helpful. Happy Rooting!
Great info, and sure to be helpful to many. Here are a some suggestions:
A description of CM versions might be helpful, linking CM versions to Android versions.
CM 7.1 is the latest stable. You might mention nightlies, and the 7.2 RC0 Mirage release.
No mention of ICS? With all the buzz lately, I'd definitely include it in the list of Android versions, and mention it with CM9.
I think there are three choices:
Root stock B&N firmware.
Dual-boot with CM (or similar) on SD (external).
Over-write eMMC (internal) with CM (or similar).
I see a lot of confusion between these, and a lot of misconception that you have to root stock before loading either of the other options.
Was the NOOK color originally shipped with Eclair? I thought they were Froyo from day one. I know a lot of us were disappointed when B&N 1.4.1 shipped as Froyo.
Thanks for the feedback. Remember, this is Nook 101, not 201. I didn't want to provide so much info that it left folks feeling overwhelmed. I suggested they begin with CM7.0. I mentioned CM7.1 and CM7.2. This sucker is already long. I had to narrow the focus to keep from turning it into a novel.
ICS is Ice Cream Sandwich, isn't it? I mentioned that CM9 is under development, but I'm pretty sure nubes should not start with that. Besides, my understanding is that it is still very much in the RC testing phase. Isn't that right?
I said there were two approaches. But I said some MODs allow for dual booting. Again, I didn't want to overwhelm.
I read in two different places (not on XDA) that Eclair was the original OS for the Nook. I think they began to push Froyo in the Fall of 2011.
You will also note that I did not cover the various models of the Nook at all. And I didn't mention the change in the hardware of Nook Color that has happened in the past two or three months. I didn't feel qualified to explain those. I'm still a relative nube myself.
BO
First, thanks for all the hard work with the words. I saw your initial posts and can only figure you are a writer, to be so willing to set everything you have done down in an orderly manner.
I'd like to add a fourth choice to bobstro's list of possibles (and I am not so adept at all this Nooker stuff myself that I believe it is too much for beginners):
Triple boot using Racks' great info and files here in the developer's wing. That way a learner can get a very stable CM7 GB (Kang build) a working - and for an "in process" ROM - quite stable CM9 (ICS) both on one SD card, and still have an untouched B&N stock on their NC.
Believe me; it's not too hard to set up; it has the best of all worlds. And it increases the fun factor by a million!
You know what root is but I don't get a clear picture of why it is called root.
In the unix/linux world if you are a superuser you have root access. Rooting a device is gaining root access to the device. With root access there are no restrictions to what you can do to the device. Including brick it.
BTW: Bricking a device is just that. Turning a beautiful orchestration of electronic components into a paperweight or, brick.
I think I included that the term rooting comes from the unix/linux world and the business about the superuser. See, that's the problem with something so long. It's easy to miss stuff. But I wanted to be clear about some of the essential stuff. It's a balancing act. Anyway, thanks for the input.
Yes. I saw why it was called bricking. I can add that.
BO
Thanks for the suggestion. I'll look into Rack's method and see whether I can include it. Again - this post is intended to be 101, not 201 info.
I wrote some computer manuals for teachers at least for a few years. It's been awhile since I did that. I try to be clear. The problem is that sometimes I try to keep it so simple that I often go overboard - result - very long. Verbose is the word. I could never have worked for Reader's Digest.
I see that nearly 150 people have at least looked at the file (maybe at least scrolled through it), but I haven't seen all that much feedback so far.
Some are making suggestions for improvement. My concern really is have I been accurate about what I actually did include?
BO
BO
You start using the term MOD without having defined it partway down.
I found this bit potentially confusing:
FYI: there are even new flavors of these general ROMS. There is also CM7.1 and CM7.2. And there is a version out there called CM9.
What is CM if this is 101?
Thanks. I'll try to adjust the issue you raised about using MOD before it has been defined. I believe I did explain CM was CyanaMod, but I'll double check it.
BO
It's a sequence thing. You use CM before CyanogenMod, and don't link them together. You might try something like CyanogenMod (CM) to link them.
Maybe a mention of OTA updates?
Gotcha. I'll see what I can do.
Thanks!
BO
This is just purely a great, great post, especially for newbies.
Keep it up, bachon.
Back to bachon, here's a few things
1. "“Rooting” means obtaining “superuser” rights to your Nook’s software. You gain the ability to load custom ROMs, ....."
Rooting has nothing to do with loading custom ROM. In order to be able to install/loading custom ROM, the bootloader must be unsigned/unchecked. Short way of saying, you can root but it doesn't mean after root, you can install custom ROM. It's a function of the bootloader.
2. Personally, I think and I do believe some devs. think that the term "rooting" is only applied to the stock ROM/OS. When you installing/running a custom ROM, the term "rooting" is irrelevant and should not be used (since we already able to access the root directory of that OS/ROM)
3. Not a biggie, but pls rename "Kernals" to "Kernels"
The other way of saying the kernels: are the firmware drivers that handle all the communications between the hardware and the operating system.
4. If you have the "Two Approaches" sections, you should also have "Three Approaches"
5. In the "Downsides of Custom ROMs" you mentioned it will void the warranty. This is only true if you install a custom ROM in eMMC. If you're running one off uSD, you know by removing the uSD, it's back to stock. No warranty voided.
6. Since you listed "o Android 3.0 (codename Honeycomb)", you should add "Android 4.0.x (codename Ice Cream Sandwich), just to complete
7. I do think we should have a short paragraph about what CyanogenMod team and their codenames. I don't want to go way back but CM7, the "7" denotes for Gingerbread builds and on-going "9" is for Ice Cream Sandwich. Why do they skip "8"? 'Cuz "8" was reserved for Honeycomb.
I can't pass out the cigars yet, huh?
votinh said:
This is just purely a great, great post, especially for newbies.
Keep it up, bachon.
Thanks for the kind words, votinh.
Mod, you should sticky this thread.
Back to bachon, here's a few things
1. "“Rooting” means obtaining “superuser” rights to your Nook’s software. You gain the ability to load custom ROMs, ....."
Rooting has nothing to do with loading custom ROM. In order to be able to install/loading custom ROM, the bootloader must be unsigned/unchecked. Short way of saying, you can root but it doesn't mean after root, you can install custom ROM. It's a function of the bootloader.
2. Personally, I think and I do believe some devs. think that the term "rooting" is only applied to the stock ROM/OS. When you installing/running a custom ROM, the term "rooting" is irrelevant and should not be used (since we already able to access the root directory of that OS/ROM)
I'm afraid my understanding for what you are saying is insufficient to write this clearly. Can you say more about this to clarify things? I thought it was obtaining superuser rights that gave users the ability to load ROMs and other software on their Nooks. I'm going to need more information to correct this.
3. Not a biggie, but pls rename "Kernals" to "Kernels"
The other way of saying the kernels: are the firmware drivers that handle all the communications between the hardware and the operating system.
Oops! Good proof reading. Thanks. Is it OK to just add your addition to the final post, or is the rest of what I have said wrong?
4. If you have the "Two Approaches" sections, you should also have "Three Approaches"
OK. Here's my current understanding. 1. Running a custom MOD from the SD Card. 2. Installing a custom ROM in eMMC. 3. Having a dual boot capability.
Someone mentioned having two different ROMs loaded on an SD card. Does this allow the original Nook OS to run with no SD card inserted?
Any clarification needed there? I'm looking to make this VERY clear for newbies.
5. In the "Downsides of Custom ROMs" you mentioned it will void the warranty. This is only true if you install a custom ROM in eMMC. If you're running one off uSD, you know by removing the uSD, it's back to stock. No warranty voided.
Hmmm. Is there no way running or updating a ROM can brick a Nook? It seems to me that someone trying to upgrade from one custom ROM to another could follow the wrong steps and trash the contents of the emmc. Am I wrong?
6. Since you listed "o Android 3.0 (codename Honeycomb)", you should add "Android 4.0.x (codename Ice Cream Sandwich), just to be complete
7. I do think we should have a short paragraph about what CyanogenMod team and their codenames. I don't want to go way back but CM7, the "7" denotes for Gingerbread builds and on-going "9" is for Ice Cream Sandwich. Why do they skip "8"? 'Cuz "8" was reserved for Honeycomb.
Click to expand...
Click to collapse
I wondered what happened to CM8. Thanks for that. I'm so new here that I'm not sure I can really explain the CyanogenMod team and their codenames. Care to give me some tips? It would really help.
While I'm asking: why and when was the codename for Gingerbread changed to CyanogenMod?
I don't mind including Ice Cream Sandwich/CM9, but I don't know that much about it. Input from the seasoned veterans would help.
Frankly, most of the suggestions I've received seem to want to add more information. I wanted things to be clear without overwhelming. Truth is, I cannot write clearly about things I don't quite understand.
If folks will share and explain the info to me then I'm more than willing to try to put it in a form that neophytes can understand.
Finally, MOD and ROM seem to be used interchangeably by many in the Nook forums. Anybody willing to provide their 2 cents worth on the difference?
Thanks
BO
I'm afraid my understanding for what you are saying is insufficient to write this clearly. Can you say more about this to clarify things? I thought it was obtaining superuser rights that gave users the ability to load ROMs and other software on their Nooks. I'm going to need more information to correct this.
Click to expand...
Click to collapse
Obtaining superuser rights is NOT enough to load custom ROMs on the device. Take a look at the Nook Tablet as an example.
Obtaining superuser rights is enough to install other applications. It is still not 100% true. Take side-loading feature as an example, some devices, even rooted, still cannot sideloading.
OK. Here's my current understanding. 1. Running a custom MOD from the SD Card. 2. Installing a custom ROM in eMMC. 3. Having a dual boot capability.
Click to expand...
Click to collapse
What you said is MOST common mistake and should be changed.
Boot from eMMC along with running off uSD is NOT dual-booted, at least not TRUE dual-booted. People here love to call it as "dual-boot" so I go with that, but it isn't, really.
True dual-boot is one ROM in eMMC and another ROM also in eMMC. Same applied for uSD.
This is a true dual-boot:
http://forum.xda-developers.com/showthread.php?t=1448186
Someone mentioned having two different ROMs loaded on an SD card. Does this allow the original Nook OS to run with no SD card inserted?
Click to expand...
Click to collapse
The link I just provided up there is exactly what it for.
And yes, it is INDEPENDENT to eMMC. You can leave stock OS intact.
Hmmm. Is there no way running or updating a ROM can brick a Nook? It seems to me that someone trying to upgrade from one custom ROM to another could follow the wrong steps and trash the contents of the emmc. Am I wrong?
Click to expand...
Click to collapse
Dealing with eMMC, yes, if you screw it up, then you got what you have. If you only dealing with uSD and leave eMMC untouch, everything on eMMC should still be there, cleanly.
Note: the NC is virtually unbrickable unless the hardware parts broken.
While I'm asking: why and when was the codename for Gingerbread changed to CyanogenMod?
Click to expand...
Click to collapse
Gingerbread is Android mobile OS codename by Google.
CyanogenMod is a developer team. Their codename gets their teamname and as I said "7" is Gingerbread version of their work.
Note: CM7 widely known for custom ROMs, not only for NC but for many other devices
Link: http://www.cyanogenmod.com/
See their device list.
Finally, MOD and ROM seem to be used interchangeably by many in the Nook forums. Anybody willing to provide their 2 cents worth on the difference?
Click to expand...
Click to collapse
I rarely see MOD as refer to ROM but I would guess, MOD is shortcut for Modification/Modified.
ROM usually refers to OS.
Votinh (or anyone else),
When you write computer code, you have to break the instructions down into step-by-step commands. Computers have no common sense to guess what you’re telling them to do. You can’t just say, “Print”. You have to be a whole lot more specific.
I’m trying to get you to do that here. Because you (and many others on this site) understand this stuff so well, you’re using broader statements like “It’s a function of the bootloader.” I’m asking you these questions to break it back down into the step-by-step stuff. If you can get me to understand it, I think I can write it down so many other nubes will understand it and MAY stop bugging everybody by asking over and over. Please be patient and bear with me.
OK. Let’s take these one at a time. Rooting first:
You said:
“Rooting has nothing to do with loading custom ROM. In order to be able to install/loading custom ROM, the bootloader must be unsigned/unchecked.”
“Short way of saying, you can root but it doesn't mean after root, you can install custom ROM. It's a function of the bootloader.”
First, I’ve been under the impression that rooting is an absolutely essential first step in order to be able to do things like loading a custom ROM. It isn’t all that is required, but it is the FIRST requirement. Isn’t that correct?
Think of a Nook straight out of the box. If I stick a formatted SD chip in my Nook with no OS, the Nook loads the stock OS. If I stick a SD chip imaged using “generic-sd-v1.3.zip” and with the zipped archive, “Encore_CM72-MIRage-01262012.zip” loaded on the SD chip, then the Nook will expand the “MIRage*.zip” and run the CM7.2 custom ROM. Isn’t that right?
Which of these zipped archives (if any) actually contains the instructions that roots the Nook?
Which of these zipped archives (if any) actually contains the instructions that unchecks the bootloader?
Which of these zipped archives (if any) contains the instructions that alters the bootloader?
Which of these zipped archives (if any) actually loads the custom MOD?
Is it accurate to say that rooting the device is only the first step necessary before the bootloader can be unchecked?
If so, is it also accurate to say that the installation process for any custom ROMs must then uncheck and alter the bootloader before any custom ROM can be installed or loaded?
My way of thinking of it is as follows: rooting only unlocks the first lock on the device. Then the installation process for the custom ROM must unlock other locks before a custom ROM can be loaded or installed.
BO
bachon said:
[...] First, I’ve been under the impression that rooting is an absolutely essential first step in order to be able to do things like loading a custom ROM. It isn’t all that is required, but it is the FIRST requirement. Isn’t that correct?
Click to expand...
Click to collapse
No, that is not correct. Rooting is providing root access on a (in a sensible case) unrooted device. This is typically your stock firmware. You can root a NC which shipped with unrooted (locked) B&N 1.2, 1.3 or 1.4.1 firmware, for example. You can also root a NT which ships with 1.4.x firmware as well.
Loading alternate firmware is where the locked bootloader comes in. On the NC, with no locked bootloader, independent of rooting, you can install alternate firmware, either to SD card (leaving the internal eMMC firmware, rooted or not, unchanged), or over-write the internal eMMC firmware with something new. I'd expect that something new to be rooted in the case of alternate firmware, but I suppose it doesn't have to be. On the NT, this is all complicated (if B&N had their way, impossible) because of the locked bootloader, but progress is being made working around this. See the NT forums for details.
If you're going to load alternate firmware on a NC, rooting is not a requirement. In fact, a lot of people like dual-booting (sorry, the term is descriptive enough without getting into semantics, and I've yet to hear a better term) something like CyanogenMod off of SD while preserving their unrooted stock B&N firmware for "warranty purposes", since they are completely independent of each other. Boot off of SD and you get CM. Pull the SD out and boot and you get B&N.
To make it short, bachon,
bootloader is essentially a piece of low-level code that resides on the non-volatile on boards that handling how the system starts up and how it behaves during powering up. The other way to say: it is the very first thing to run soon the power provided.
If it is "signed/locked" then you have a hard time to manipulate it such loading custom ROM, even preventing alter the stock recovery, and in some case, not even allow us to touch the system kernel.
Think of a Nook straight out of the box. If I stick a formatted SD chip in my Nook with no OS, the Nook loads the stock OS. If I stick a SD chip imaged using “generic-sd-v1.3.zip” and with the zipped archive, “Encore_CM72-MIRage-01262012.zip” loaded on the SD chip, then the Nook will expand the “MIRage*.zip” and run the CM7.2 custom ROM. Isn’t that right?
Which of these zipped archives (if any) actually contains the instructions that roots the Nook?
Which of these zipped archives (if any) actually contains the instructions that unchecks the bootloader?
Which of these zipped archives (if any) contains the instructions that alters the bootloader?
Which of these zipped archives (if any) actually loads the custom MOD?
Click to expand...
Click to collapse
The "generic...." is just a container.
The "encore-...." is the actual custom ROM.
If so, is it also accurate to say that the installation process for any custom ROMs must then uncheck and alter the bootloader before any custom ROM can be installed or loaded?
Click to expand...
Click to collapse
Absolutely true.
---------- Post added at 10:21 AM ---------- Previous post was at 10:20 AM ----------
Oh, and bobstro have provided a very good example of it, down to the very specific case.
Bobstro,
So a lot of people who say "I rooted my Nook" aren't correct. They may have loaded another OS, like CyanogenMod 7.2, but that doesn't mean that they've necessarily rooted their Nook. Is that correct?
These folks would be more accurate to say "I hacked my Nook."
Is that closer to being accurate?
How and why did so many people start calling it rooting? I know about the root user in Unix. Do some of the OS installations go the extra step of actually rooting the Nook?
BO
I think you spelled Bacon wrong.
bachon said:
Bobstro,
So a lot of people who say "I rooted my Nook" aren't correct. They may have loaded another OS, like CyanogenMod 7.2, but that doesn't mean that they've necessarily rooted their Nook. Is that correct?
These folks would be more accurate to say "I hacked my Nook."
Is that closer to being accurate?
How and why did so many people start calling it rooting? I know about the root user in Unix. Do some of the OS installations go the extra step of actually rooting the Nook?
BO
Click to expand...
Click to collapse
I don't mean to jump on bobstro's toe, I hope he allows me to answer the question.
1. Again, I repeat, the term "root" should only be applied when you're dealing with STOCK ROM.
2. If you are running CM7 or any custom ROM such MIUI, .... you DON'T NEED to root since it ALREADY allows you accessing the root directory. Therefore "rooting" process is no need.
3. If you are running any custom ROM, ideally, you should not say "I'm rooting my device".
Why people using that? They say so and no one correct them so the term spreads.
I don't have the time to constantly be looking for new roms to make my phone run properly. My phone is always freezing up due to the stupid Touchwiz UI and I absolutely hate it. I am sick and tired of my phone freezing up and lagging constantly and having to do factory reset and reinstalling all my apps fresh.
So I was wondering, what can I do to fix this problem in a easier manner? I was thinking about rooting the phone, saving all my app data, unrooting, resetting the phone, rooting again, uninstall bloatware, reinstalling apps with their data, and unrooting.
Here are my concerns though. I want to be able to reset the phone using the orignal factory reset. I don't have time or care to install new roms on my phone as I want to keep my warranty and I want to be able to sell my phone in the future.
So what are my options here? What can I do and what are my steps to start doing them?
I am on AT&T Note 3 with kitkat 4.4.2 with my build number ending in NC2.
Is the Note 3 development this bad? Not one response in a couple days. Anyone have a simple answer?
I just want to know if I can factory reset if I root my device and how I could complete unroot.
joshlete said:
Is the Note 3 development this bad? Not one response in a couple days. Anyone have a simple answer?
I just want to know if I can factory reset if I root my device and how I could complete unroot.
Click to expand...
Click to collapse
Simple answer is root with towelroot, and when you want to do a complete factory reset, flash stock NC2 using the guide in this thread.
I think your original question about what options you have is a little more complicated...rooting your phone technically voids your warranty, but if you're referring to the KNOX warranty flag then towelroot doesn't trip that flag. Reflashing stock NC2 with Odin will unroot your phone automatically so no worries there either. What I'm getting at is flashing roms isn't going to void your warranty any more than rooting with towelroot will, on the other hand uninstalling system apps can cause lots of problems, so you may find it easier to flash a near-stock rom that has the bloatware already removed.
But if you're set on not flashing anything, then I'd suggest using titanium backup to freeze any apps you don't want instead of uninstalling them. If you uninstall the wrong app you could end up having to do a factory reset anyway just to get your phone working again. Freezing system apps can cause problems too but it's generally easier to unfreeze an app than try and find and reinstall a system apk. And as tempting as it is don't uninstall My Magazine you'll get FC all over the place and your email won't work properly
So if I install that stock rom, would I be able to update my phone using the internal updater? I just want to be able to install Android 5.0 when/if it comes out for the Note 3. Seeing how AT&T note 3 has little to no roms to install. Very disappointing.
The Odin files in that thread are for stock NC2 and unless you flashed a rom after your second post you're still on stock...it's the exact same AT&T stock build...flashing it won't really benefit you at all unless you rooted and made changes to your system. I assume by internal updater you mean the OTA updates that get pushed out from AT&T then yes since that is the official AT&T build if you flash it you will still get those updates provided AT&T is your carrier. There may not be a lot of roms but the ones we have are great I'd encourage you to try one or two there are a couple "debloated" stock roms I think would give you what you're looking for in terms of stability but of course it's up to you if you just want to stay stock
joshlete said:
So if I install that stock rom, would I be able to update my phone using the internal updater? I just want to be able to install Android 5.0 when/if it comes out for the Note 3. Seeing how AT&T note 3 has little to no roms to install. Very disappointing.
Click to expand...
Click to collapse
Wow... just... wow.
This POST is disappointing.
I'm on the same boat as you OP. When time comes for a new phone, my next phone will never be another Samsung phone again. I will only consider phones that are close to stock. Most likely Motorola X or Sony Z3 Compact or similar.
TouchWiz is so disappointing. It's slow and creates lags even for just checking what time it is.
Fortunately I have some time so unlike OP, I tried debloating stock rom, tried at least 5 custom roms. Most of the custom roms have either too much theme customization (really not my taste) or something else doesn't work (NFC payment or deep sleep or some other thing). And they all claim super duper fast and rock stable, but those are hyperboles. The only time I experienced one rom being faster than the other was with Galaxy S5 port rom, but that was most likely due to the fact that standby mode is disabled because we have no way to update the firmware. In other words, uses more battery but still lasts a day. Also, I never seen the battery last exceptionally longer than the stock rom, so don't trust the super long lasting battery claims.
The easiest way to get your phone run smoothly is to factory reset it, and then only install select apps that you really need and know that it won't be a resource hog reporting your every move.
Oh, and last year's Moto X (dual core) feels faster than a quad core Note3 for everyday task in my hands. I wish we had a google experience rom for n900a.
brisinger08 said:
The Odin files in that thread are for stock NC2 and unless you flashed a rom after your second post you're still on stock...it's the exact same AT&T stock build...flashing it won't really benefit you at all unless you rooted and made changes to your system. I assume by internal updater you mean the OTA updates that get pushed out from AT&T then yes since that is the official AT&T build if you flash it you will still get those updates provided AT&T is your carrier. There may not be a lot of roms but the ones we have are great I'd encourage you to try one or two there are a couple "debloated" stock roms I think would give you what you're looking for in terms of stability but of course it's up to you if you just want to stay stock
Click to expand...
Click to collapse
Could you link me to some stock roms? I lost my game in rom finding and can't seem to get a good running/looking rom.
RErick said:
Wow... just... wow.
This POST is disappointing.
Click to expand...
Click to collapse
Most useless post of the year goes to......
joshlete said:
Could you link me to some stock roms? I lost my game in rom finding and can't seem to get a good running/looking rom.
Most useless post of the year goes to......
Click to expand...
Click to collapse
UR Droid is probably the closest to stock...Knox removed, sd card write permissions fixed, etc. are the only mods...that said carl's made a ton of flashable zips too so if you did want to start making mods yourself chances are you won't have any problems while running his rom
FireKat is one you've probably run across. That is a stock rom all of the mods/optimizations/etc mega makes are from other stock builds. There's no theming or anything like that it's more like "TouchWiz optimized"...again nothing extraneous added if you want to add tethering, call recording, etc you'll have to do it yourself. FireKat is geared towards speed and battery life but it's rock solid with no known issues. All of the rom updates you see are for performance improvements as opposed to the majority of the aosp-hybrid or heavily themed roms where updates are for bug fixes.
Both devs are really helpful and responsive definitely check out their threads though since I'm not up to date with both roms. I have flashed both of them at some point and both are significant improvements over stock...of course no one can tell you what roms you'll like or should flash but I'd be pretty surprised if you have a better experience on stock than either of these roms.
I've been running a stock rooted 4.4.2 for months and it was not laggy at all.
In the application manager settings I turned off all bloatware apps that I did not use. I froze (with titanium backup) all bloatware that could not be turned off in settings and also froze anything that says "knox" in the title. I used xposed installer to install many modules that allowed me to tweak my stock rom... including greenify to auto hibernate apps, smart booster to manage ram, boot manager, and also Wanam xposed for ui customizing...
My phone has run extremely well.
I just made the jump to 4.4.4 and got it rooted (thanks to @muniz_ri and a few others).... exact same setup again... stock rooted... turn off and freeze un-needed apps... xposed modules... and again it is running nice and smooth.
I also use nova launcher prime because it feels more responsive and does more things that I want (like a home screen that will autorotate to landscape mode).
Wow, that's a lot to have for being stock .
The only way to get rid most of your concerns is to root your phone. Then you can delete all other useless apps that you don't need and slow your phone down a bit.
But installing a new Rom is the best way to have a peace in mind I think. Dynamic KitKat is one of the best roms for our phone. I've been using it for months and there is nothing I can say how much I like it. Sometimes I experience lag, but that is to be expected because of Android's ability to do multitasks.
Just my 2 cents.
OK, kind of a strange question but . . .
My daughter sent me this phone cause she got it as a freebie from TMobile and it came with the stock Gingerbread / bloatware configuration on it. I immediately Googled some info on how to root it, installed ClockworkMod and CM 11 and have been pretty happy.
Now I want to install the latest CM12 build. I grabbed the TWRP tool and the CM12 built and am ready to go, but first I would like to understand what I can safely delete and what features Google duplicates that CM provides. For example, I have three launchers on my phone (Trebuchet, Nova, and Google) and I am sure that is one, maybe two, too many. Ditto picture and sound apps.
I am not averse to actually reading documentation, but can somebody point me to a tutorial site where I can educate myself and do some reading. I prefer a skinny configuration that only has the stuff I need but I need a little guidance before I start nuking away.
Also, since I flashed this phone within hours of receiving it in the mail I never backed up anything in Gingerbread before the flash. I assume that I will have to reinstall all my apps and data after I flash to CM12 or is there a way to just flash the OS and leave the rest untouched?
Hi, I've been using my Moto G Titan (dual-sim) for about 4 years now, mostly with custom rom the whole time (CM 12.1 back then). I upgraded to a Moto G3 TE (and used custom roms from xda here) over a year ago. So then on this phone (titan) I updated the firmware and ROM and passed it on to my wife. I put on Viper OS 7.1.2 on it and initially it was working great. Over time though it increasingly slowed down and clearing the cache and such didn't seem to help (my wife didn't really complain much because she never liked using smart phones anyway and she just thought it *has* to be a poor user experience). I also had my phone (Moto G3 TE) stolen about a month ago, so while I'm waiting to get a new phone my wife and I are sharing this phone (Titan) with two different accounts. Talk about sloooooooooow! So now I realize I REALLY need a different rom. Or is it possible the RAM or something is just old and no longer working right?
I've read on here that many people suggest downgrading to stock lollipop or something like that. Others suggest a custom Marshmallow rom. I honestly don't care too much what I downgrade to as long as the most common apps (gmail, facebook, whatsapp - ones for keeping in touch and getting work done, that sort of thing) are working. Oh, and pinterest, that's the one thing my wife loves. I would like to keep an OS version that allows me to used mixed storage (mixed between adopted/portable) if possible, because that helps me with the low amount of internal memory. But I can give that up if necessary, because above all I want it to be smooth, because this lag is ridiculous! Sometimes a phone call comes in and it's ringing but it takes so long for the screen that shows I can accept/reject the call to pop up that by then the caller has already hung up (like over 10 seconds sometimes)! So yeah, I really want a rom that's responsive again and can do those most basic apps.
My questions is: if I'm on ViperOS 7.1.2 and if lollipop or marshmallow (whether stock or custom) is best - then how do I downgrade to those? I have TWRP and root and all that on here already and I'd love it if I could just do it by TWRP since that'd be the easiest for me. But I'll do whatever I need to as long as I can truly understand the step-by-step directions and not brick this phone. (Since right now it's the ONLY phone my wife and I have to work with until I get a new one in another month or two... and even still I'd like my wife to be able to use this one more easily.) I read somewhere that if I have a newer firmware maybe I can't return directly to an older OS? Any information on how to switch OS without messing up my phone would help a lot!
So, please give me a suggestion as to which OS gives you great responsiveness/speed (doesn't lag you down for phone calls especially, but no lag on any other basic programs would also be great). And regarding the OS you suggest, please tell me what steps I need to take to switch/downgrade to it and/or anything else I need to do to keep it going fast. I found this post, but to be honest, it's just not very clear to me what I'd actually have to *do*: https://forum.xda-developers.com/moto-g-2014/general/opinion-best-rom-experience-t3546088 So if you could give me a clear step-by-step guide (or point me to one or more threads/posts that I'd link the processes together), that'd be SUPER helpful! Thanks in advance for any help any of you can offer!
madagascaradam said:
Hi, I've been using my Moto G Titan (dual-sim) for about 4 years now, mostly with custom rom the whole time (CM 12.1 back then). I upgraded to a Moto G3 TE (and used custom roms from xda here) over a year ago. So then on this phone (titan) I updated the firmware and ROM and passed it on to my wife. I put on Viper OS 7.1.2 on it and initially it was working great. Over time though it increasingly slowed down and clearing the cache and such didn't seem to help (my wife didn't really complain much because she never liked using smart phones anyway and she just thought it *has* to be a poor user experience). I also had my phone (Moto G3 TE) stolen about a month ago, so while I'm waiting to get a new phone my wife and I are sharing this phone (Titan) with two different accounts. Talk about sloooooooooow! So now I realize I REALLY need a different rom. Or is it possible the RAM or something is just old and no longer working right?
I've read on here that many people suggest downgrading to stock lollipop or something like that. Others suggest a custom Marshmallow rom. I honestly don't care too much what I downgrade to as long as the most common apps (gmail, facebook, whatsapp - ones for keeping in touch and getting work done, that sort of thing) are working. Oh, and pinterest, that's the one thing my wife loves. I would like to keep an OS version that allows me to used mixed storage (mixed between adopted/portable) if possible, because that helps me with the low amount of internal memory. But I can give that up if necessary, because above all I want it to be smooth, because this lag is ridiculous! Sometimes a phone call comes in and it's ringing but it takes so long for the screen that shows I can accept/reject the call to pop up that by then the caller has already hung up (like over 10 seconds sometimes)! So yeah, I really want a rom that's responsive again and can do those most basic apps.
My questions is: if I'm on ViperOS 7.1.2 and if lollipop or marshmallow (whether stock or custom) is best - then how do I downgrade to those? I have TWRP and root and all that on here already and I'd love it if I could just do it by TWRP since that'd be the easiest for me. But I'll do whatever I need to as long as I can truly understand the step-by-step directions and not brick this phone. (Since right now it's the ONLY phone my wife and I have to work with until I get a new one in another month or two... and even still I'd like my wife to be able to use this one more easily.) I read somewhere that if I have a newer firmware maybe I can't return directly to an older OS? Any information on how to switch OS without messing up my phone would help a lot!
So, please give me a suggestion as to which OS gives you great responsiveness/speed (doesn't lag you down for phone calls especially, but no lag on any other basic programs would also be great). And regarding the OS you suggest, please tell me what steps I need to take to switch/downgrade to it and/or anything else I need to do to keep it going fast. I found this post, but to be honest, it's just not very clear to me what I'd actually have to *do*: https://forum.xda-developers.com/moto-g-2014/general/opinion-best-rom-experience-t3546088 So if you could give me a clear step-by-step guide (or point me to one or more threads/posts that I'd link the processes together), that'd be SUPER helpful! Thanks in advance for any help any of you can offer!
Click to expand...
Click to collapse
As you are currently running android nougat. I suggest you Cosmic Os 7.1.2 AOSP based.
https://forum.xda-developers.com/moto-g-2014/development/rom-cosmic-os-t3576987
I've been using it over more than 2-3 months as my daily driver. It doesn't lag and 300+ RAM is always free with no apps open in background.
Still if you want to downgrade to marshmallow or lollipop, you'll have to do it using a PC or laptop.
!!!!!!!Root2!!!!!! said:
As you are currently running android nougat. I suggest you Cosmic Os 7.1.2 AOSP based.
https://forum.xda-developers.com/moto-g-2014/development/rom-cosmic-os-t3576987
I've been using it over more than 2-3 months as my daily driver. It doesn't lag and 300+ RAM is always free with no apps open in background.
Still if you want to downgrade to marshmallow or lollipop, you'll have to do it using a PC or laptop.
Click to expand...
Click to collapse
OK, that sounds like a good start! Thanks for your suggestion! I'll wait for a few more responses and info before I decide what route to try first. If I do want to downgrade, what method do I use from PC or laptop? I've used the quickboot/adb shell commands with no trouble before, but only because I've seen step-by-step guides that tell me *what* to put in the adb shell, etc. So, can you help give me a guide on how I'd downgrade or point me to one that has a downgrade that's really fast?
madagascaradam said:
OK, that sounds like a good start! Thanks for your suggestion! I'll wait for a few more responses and info before I decide what route to try first. If I do want to downgrade, what method do I use from PC or laptop? I've used the quickboot/adb shell commands with no trouble before, but only because I've seen step-by-step guides that tell me *what* to put in the adb shell, etc. So, can you help give me a guide on how I'd downgrade or point me to one that has a downgrade that's really fast?
Click to expand...
Click to collapse
I don't recommend downgrading to Lollipop or Marshmallow as they lack RAM management and heat up the phone while gaming plus Ui is not that good. Android Nougat has better RAM management with fluid performance and battery backup is good as well.
Here's Stock Marshmallow TWRP backup thread and it's detailed enough so that you won't brick your phone
Take a Nandroid backup before.
First, what's the model of your Titan and country?
I think it's not a good idea to downgrade to older stock as it might lead to device getting bricked .... luckily I have never faced such as an issue as I always stick to custom ROMs for my Titan ....I request you to look up Titan downgrade brick stories and get a better idea about how to avoid it ....
Also have you tried using Aex 5.6 on your phone with evolution kernel? it used to work brilliantly on mine before I jumped on to renans los 16 pie builds
!!!!!!!Root2!!!!!! said:
I don't recommend downgrading to Lollipop or Marshmallow as they lack RAM management and heat up the phone while gaming plus Ui is not that good. Android Nougat has better RAM management with fluid performance and battery backup is good as well.
Here's Stock Marshmallow TWRP backup thread and it's detailed enough so that you won't brick your phone
Take a Nandroid backup before.
First, what's the model of your Titan and country?
Click to expand...
Click to collapse
Thanks for the extra advice. You didn't actually include the link for the thread though. Were you just waiting for my model # (below)? But yes, I'm used to doing the Nandroid backups through TWRP so that's no challenge for me.
It's an XT1068. I bought it from Amazon US but I'm living in Madagascar and have used it here most the time I've had it. It's also worked for me in South Africa and USA though too.
Anyway, I'll appreciate the link to the stock marshmallow twrp backup thread, in case that's the route I decide to go! I won't be doing any gaming on it though (wife's phone) and just need it to work well enough for phone calls, messages, and other important aspects of life. And yeah, I like the newer UI, but if it's too slow, I can't do much with it! So I'll have to think about the other suggestions people have given here and also weigh it in with the possibility of downgrading to marshmallow with that detailed step-by-step so I won't brick my phone.
clockstoper said:
I think it's not a good idea to downgrade to older stock as it might lead to device getting bricked .... luckily I have never faced such as an issue as I always stick to custom ROMs for my Titan ....I request you to look up Titan downgrade brick stories and get a better idea about how to avoid it ....
Also have you tried using Aex 5.6 on your phone with evolution kernel? it used to work brilliantly on mine before I jumped on to renans los 16 pie builds
Click to expand...
Click to collapse
Thanks also for your advice. I've never been bricked either, but I don't want to start, especially since we're down to 1 phone in my family right now! If someone can tell me that downgrading is definitely way smoother (as I've seen written on a few threads here, but without detailed instructions on how to do it) and if they say I can do it without bricking, then I might take that route. I haven't tried AEX on this phone, though I was using it on my Moto G3 TE before it got stolen. So yeah, that's a good idea if you say it works great. Can you link to a thread for me? Particularly when you say "with evolution kernel"... in the past I don't think I've tried a different kernel for my rom, I've always just followed step-by-steps for flashing a custom rom and gapps, that sort of thing. So if I have to do an extra step for the evolution kernel, please also tell me how or where to find the thread about it. Thanks again for your help!
madagascaradam said:
Thanks for the extra advice. You didn't actually include the link for the thread though. Were you just waiting for my model # (below)? But yes, I'm used to doing the Nandroid backups through TWRP so that's no challenge for me.
It's an XT1068. I bought it from Amazon US but I'm living in Madagascar and have used it here most the time I've had it. It's also worked for me in South Africa and USA though too.
Anyway, I'll appreciate the link to the stock marshmallow twrp backup thread, in case that's the route I decide to go! I won't be doing any gaming on it though (wife's phone) and just need it to work well enough for phone calls, messages, and other important aspects of life. And yeah, I like the newer UI, but if it's too slow, I can't do much with it! So I'll have to think about the other suggestions people have given here and also weigh it in with the possibility of downgrading to marshmallow with that detailed step-by-step so I won't brick my phone.
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g-2014/general/moto-g-indian-xt1068-marshmellow-6-0-t3313148
The links to Aex and evolution kernel for titan
madagascaradam said:
Thanks also for your advice. I've never been bricked either, but I don't want to start, especially since we're down to 1 phone in my family right now! If someone can tell me that downgrading is definitely way smoother (as I've seen written on a few threads here, but without detailed instructions on how to do it) and if they say I can do it without bricking, then I might take that route. I haven't tried AEX on this phone, though I was using it on my Moto G3 TE before it got stolen. So yeah, that's a good idea if you say it works great. Can you link to a thread for me? Particularly when you say "with evolution kernel"... in the past I don't think I've tried a different kernel for my rom, I've always just followed step-by-steps for flashing a custom rom and gapps, that sort of thing. So if I have to do an extra step for the evolution kernel, please also tell me how or where to find the thread about it. Thanks again for your help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-g-2014/development/rom-aospextended-rom-v5-8-t3829769
https://forum.xda-developers.com/moto-g-2014/development/kernel-evolution-kernel-t3514843
clockstoper said:
https://forum.xda-developers.com/moto-g-2014/development/rom-aospextended-rom-v5-8-t3829769
https://forum.xda-developers.com/moto-g-2014/development/kernel-evolution-kernel-t3514843
Click to expand...
Click to collapse
Thanks a lot! How do I use a different kernel than the one that comes with the ROM? Do I flash/install AEX first and *then* follow those directions for the evolution kernel? Or do I do the kernel first and then AEX? And I'm assuming I download the first kernel download link on that page (the one that says Marshmallow/Nougat Roms and "R10")? Basically, I'd really appreciate it if you'd offer more information on what it means to switch kernels and how to do that? Thanks again for your help!
Download Aex then install it first
madagascaradam said:
Thanks a lot! How do I use a different kernel than the one that comes with the ROM? Do I flash/install AEX first and *then* follow those directions for the evolution kernel? Or do I do the kernel first and then AEX? And I'm assuming I download the first kernel download link on that page (the one that says Marshmallow/Nougat Roms and "R10")? Basically, I'd really appreciate it if you'd offer more information on what it means to switch kernels and how to do that? Thanks again for your help!
Click to expand...
Click to collapse
Install rom first then make a backup of only boot install kernel after that , there is a another version of evolution kernel with overclock enabled if you feel that evolution is slow try evolutionX ,it's bit of a battery hog but runs like butter.
Switching kernels gives you access to better features in you kernel like updated tweaks, governors overclock ,undervolt ,sound gain boost etc which the stock kernel doesn't provide in most cases .....only few kernels are as up-to-date with extra features as evolution imo so try it if you don't like how it performs you can tweak it more with kernel aduitor ,for faster feeling phone I normally disable all animations under devoloper options .you can also flash evolutionx to see if it suits you or not just restore the boot backup you made and flash it then test ......
Get the kernel for Oreo as Aex 5.8 is Oreo
Before flashing plz make sure twrp is updated
Always backup important data into your mircosd card or PC
I recommend a full wipe ( system ,data, internal storage,caches) with twrp and then install the new ROM
Do let me know how it goes ....
clockstoper said:
Install rom first then make a backup of only boot install kernel after that , there is a another version of evolution kernel with overclock enabled if you feel that evolution is slow try evolutionX ,it's bit of a battery hog but runs like butter.
Switching kernels gives you access to better features in you kernel like updated tweaks, governors overclock ,undervolt ,sound gain boost etc which the stock kernel doesn't provide in most cases .....only few kernels are as up-to-date with extra features as evolution imo so try it if you don't like how it performs you can tweak it more with kernel aduitor ,for faster feeling phone I normally disable all animations under devoloper options .you can also flash evolutionx to see if it suits you or not just restore the boot backup you made and flash it then test ......
Get the kernel for Oreo as Aex 5.8 is Oreo
Before flashing plz make sure twrp is updated
Always backup important data into your mircosd card or PC
I recommend a full wipe ( system ,data, internal storage,caches) with twrp and then install the new ROM
Do let me know how it goes ....
Click to expand...
Click to collapse
Great, thanks for the advice! My weekend is busy but I'm going to give it a go on Monday or Tuesday and let you know how it turns out!
clockstoper said:
Install rom first then make a backup of only boot install kernel after that , there is a another version of evolution kernel with overclock enabled if you feel that evolution is slow try evolutionX ,it's bit of a battery hog but runs like butter.
Switching kernels gives you access to better features in you kernel like updated tweaks, governors overclock ,undervolt ,sound gain boost etc which the stock kernel doesn't provide in most cases .....only few kernels are as up-to-date with extra features as evolution imo so try it if you don't like how it performs you can tweak it more with kernel aduitor ,for faster feeling phone I normally disable all animations under devoloper options .you can also flash evolutionx to see if it suits you or not just restore the boot backup you made and flash it then test ......
Get the kernel for Oreo as Aex 5.8 is Oreo
Before flashing plz make sure twrp is updated
Always backup important data into your mircosd card or PC
I recommend a full wipe ( system ,data, internal storage,caches) with twrp and then install the new ROM
Do let me know how it goes ....
Click to expand...
Click to collapse
Hey, so I had a busy week and I'm just now getting to this. Do I still need to flash a superuser image in order to get superuser working on this (like for fx explorer root or those sort of things)? I have this superuser package I used last time I installed the ViperOS (that's super slow that I'm replacing now): SR1-SuperSU-v2.82-SR1-20170608224931.zip Do I still need that? I can't seem to find an updated one on here or maybe it's buried because it's too old. Maybe people don't use SuperSU anymore? Just wondering. Thanks for any help! And I'll let you know how the new image goes later today.
Use magisk it's way better
madagascaradam said:
Hey, so I had a busy week and I'm just now getting to this. Do I still need to flash a superuser image in order to get superuser working on this (like for fx explorer root or those sort of things)? I have this superuser package I used last time I installed the ViperOS (that's super slow that I'm replacing now): SR1-SuperSU-v2.82-SR1-20170608224931.zip Do I still need that? I can't seem to find an updated one on here or maybe it's buried because it's too old. Maybe people don't use SuperSU anymore? Just wondering. Thanks for any help! And I'll let you know how the new image goes later today.
Click to expand...
Click to collapse
Plus it has all the modules ....very useful ....
Link magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
clockstoper said:
Plus it has all the modules ....very useful ....
Link magisk
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Click to expand...
Click to collapse
Thanks again! So, I did try SuperSU since it looked like it'd be easy (just install that app) and the Magisk thing said better to go back to stock rom in order to make it work. But SuperSU then was a big headache, after a lot of work I got rid of it, and installed Magisk (without going back to stock rom) and everything was good. Any particular modules you'd suggest using with Magisk?
But overall: I followed your advice and everything seems good. This is my first time to use Oreo and I do like it so far. I haven't turned of animations yet, but I might soon. It's still running fairly fast like I'd expect. I still have to install a few apps on my account and I'll wait and see if that slows anything down. But my wife's account has all her stuff on it, everything logged in, and it seems like it's still smooth. I'm going to give it a few days to a week and see if anything slows it down before I report back to you.
I did have a few questions though: under the AEX extensions, it says "system app remover" and I tried to remove a couple weird apps I don't need on there (like "retro music player" - I don't have any idea how that even got there). I had to enable root for it, but it still doesn't seem to have disappeared. Any idea how to fully get rid of non-wanted system apps?
In that same area for removing system apps (built into the AEX extensions) it looks like there are quite a few theme "apps" already inside it, including even some dark themes for contacts (which I'd really appreciate). But I can't find in the rom anywhere to enable themes. If I download the substratum app, will it automatically give me access to those built-in themes or want? If you know anything about this let me know.
Also, under the aex extensions is an option for weather on the lock screen, but the weather service doesn't seem to be working at all yet. Any idea on that?
Even if you don't know about those things, that's OK, maybe I'll post and ask those questions in the AEX thread and see if anyone has anything to say there.
Overall, everything has worked great so far though, which is great and I appreciate all the advice you've given me! I'll just give it some time to see if it stays fast with regular use, and of course I need to keep making a few tweaks to it.
Glad it worked out
madagascaradam said:
Thanks again! So, I did try SuperSU since it looked like it'd be easy (just install that app) and the Magisk thing said better to go back to stock rom in order to make it work. But SuperSU then was a big headache, after a lot of work I got rid of it, and installed Magisk (without going back to stock rom) and everything was good. Any particular modules you'd suggest using with Magisk?
But overall: I followed your advice and everything seems good. This is my first time to use Oreo and I do like it so far. I haven't turned of animations yet, but I might soon. It's still running fairly fast like I'd expect. I still have to install a few apps on my account and I'll wait and see if that slows anything down. But my wife's account has all her stuff on it, everything logged in, and it seems like it's still smooth. I'm going to give it a few days to a week and see if anything slows it down before I report back to you.
I did have a few questions though: under the AEX extensions, it says "system app remover" and I tried to remove a couple weird apps I don't need on there (like "retro music player" - I don't have any idea how that even got there). I had to enable root for it, but it still doesn't seem to have disappeared. Any idea how to fully get rid of non-wanted system apps?
In that same area for removing system apps (built into the AEX extensions) it looks like there are quite a few theme "apps" already inside it, including even some dark themes for contacts (which I'd really appreciate). But I can't find in the rom anywhere to enable themes. If I download the substratum app, will it automatically give me access to those built-in themes or want? If you know anything about this let me know.
Also, under the aex extensions is an option for weather on the lock screen, but the weather service doesn't seem to be working at all yet. Any idea on that?
Even if you don't know about those things, that's OK, maybe I'll post and ask those questions in the AEX thread and see if anyone has anything to say there.
Overall, everything has worked great so far though, which is great and I appreciate all the advice you've given me! I'll just give it some time to see if it stays fast with regular use, and of course I need to keep making a few tweaks to it.
Click to expand...
Click to collapse
The ROM still has some unimplemented stuff system app remover in extensions
As for modules is use viper4android to tweak sound and
Terminal debloater to remove unwanted system apps via terminal
You need to enable it via developer options ...
And about the theme apps you found in system apps remover ,those are simply the colour overlays the system uses for automatically setting system theme based on wallpaper colour, to manually set theme you can try going into system>display >ui theme and try changing stuff there it has the pre-installed colour schemes .......
You will find the option to change the system fonts there too.....
For weather you need to enable the service by going into weather>service ......
Also to keep things smooth use greenify and greenify all the apps that don't need to run in the background .....enable agressive doze there .....
Also go into settings>extensions>system>app ops side scroll to boot up and take away boot permission from any and every app that you don't use immediately after powering your phone .....it helps speed up the phone a lot .
Go to extentions and general tweaks and turn on disable FC notifications too...
Get sd maid free and do cleanup of system cleaner and corpse finder every month end .....
Go to dialer>three dots >settings then enable proximity speakerphone it very good feature ......
Happy it all worked out for yaa ...
I have a question though ,did you do a full format in twrp ?
I mean the format data option where you need to type yes to proceed . That speed up lag on my phone after I moved from stock so next time you might wanna try that before installing a new ROM....
report
madagascaradam said:
Thanks again! So, I did try SuperSU since it looked like it'd be easy (just install that app) and the Magisk thing said better to go back to stock rom in order to make it work. But SuperSU then was a big headache, after a lot of work I got rid of it, and installed Magisk (without going back to stock rom) and everything was good. Any particular modules you'd suggest using with Magisk?
But overall: I followed your advice and everything seems good. This is my first time to use Oreo and I do like it so far. I haven't turned of animations yet, but I might soon. It's still running fairly fast like I'd expect. I still have to install a few apps on my account and I'll wait and see if that slows anything down. But my wife's account has all her stuff on it, everything logged in, and it seems like it's still smooth. I'm going to give it a few days to a week and see if anything slows it down before I report back to you.
I did have a few questions though: under the AEX extensions, it says "system app remover" and I tried to remove a couple weird apps I don't need on there (like "retro music player" - I don't have any idea how that even got there). I had to enable root for it, but it still doesn't seem to have disappeared. Any idea how to fully get rid of non-wanted system apps?
In that same area for removing system apps (built into the AEX extensions) it looks like there are quite a few theme "apps" already inside it, including even some dark themes for contacts (which I'd really appreciate). But I can't find in the rom anywhere to enable themes. If I download the substratum app, will it automatically give me access to those built-in themes or want? If you know anything about this let me know.
Also, under the aex extensions is an option for weather on the lock screen, but the weather service doesn't seem to be working at all yet. Any idea on that?
Even if you don't know about those things, that's OK, maybe I'll post and ask those questions in the AEX thread and see if anyone has anything to say there.
Overall, everything has worked great so far though, which is great and I appreciate all the advice you've given me! I'll just give it some time to see if it stays fast with regular use, and of course I need to keep making a few tweaks to it.
Click to expand...
Click to collapse
how it ended?
clockstoper said:
The ROM still has some unimplemented stuff system app remover in extensions
As for modules is use viper4android to tweak sound and
Terminal debloater to remove unwanted system apps via terminal
You need to enable it via developer options ...
And about the theme apps you found in system apps remover ,those are simply the colour overlays the system uses for automatically setting system theme based on wallpaper colour, to manually set theme you can try going into system>display >ui theme and try changing stuff there it has the pre-installed colour schemes .......
You will find the option to change the system fonts there too.....
For weather you need to enable the service by going into weather>service ......
Also to keep things smooth use greenify and greenify all the apps that don't need to run in the background .....enable agressive doze there .....
Also go into settings>extensions>system>app ops side scroll to boot up and take away boot permission from any and every app that you don't use immediately after powering your phone .....it helps speed up the phone a lot .
Go to extentions and general tweaks and turn on disable FC notifications too...
Get sd maid free and do cleanup of system cleaner and corpse finder every month end .....
Go to dialer>three dots >settings then enable proximity speakerphone it very good feature ......
Happy it all worked out for yaa ...
I have a question though ,did you do a full format in twrp ?
I mean the format data option where you need to type yes to proceed . That speed up lag on my phone after I moved from stock so next time you might wanna try that before installing a new ROM....
Click to expand...
Click to collapse
Thanks for all the extra advice! A lot of that certainly helped. It was actually slowing down again a bit within a few days, but greenify made an immediately noticeable difference, as well as a few of those other things you mentioned.
The weather thing still isn't working even though I have it enabled. Maybe because I'm in Madagascar and most services don't cover weather here?
I couldn't find the dialer either, so I couldn't get to its settings. I'm interested in what the proximity speakerphone does though.
I didn't do any format where I needed to type "yes" to proceed, but when I did wipe I chose every aspect of the storage and wiped all of it (even the memory card). So maybe that was just a simple delete rather than an actual format. I'll keep this in mind though next time I flash a system from start. Though I had the memory card formatted as mixed storage (gave 10 GB of it to the system ["expanded"] and the rest for normal portable use) and the expanded portion reads funny now in the storage settings - as if it had 128 GB and 118 GB were already used. That's strange, but it doesn't seem to affect anything so I'm not worrying about it.
Dialer is the phone app ..
madagascaradam said:
Thanks for all the extra advice! A lot of that certainly helped. It was actually slowing down again a bit within a few days, but greenify made an immediately noticeable difference, as well as a few of those other things you mentioned.
The weather thing still isn't working even though I have it enabled. Maybe because I'm in Madagascar and most services don't cover weather here?
I couldn't find the dialer either, so I couldn't get to its settings. I'm interested in what the proximity speakerphone does though.
I didn't do any format where I needed to type "yes" to proceed, but when I did wipe I chose every aspect of the storage and wiped all of it (even the memory card). So maybe that was just a simple delete rather than an actual format. I'll keep this in mind though next time I flash a system from start. Though I had the memory card formatted as mixed storage (gave 10 GB of it to the system ["expanded"] and the rest for normal portable use) and the expanded portion reads funny now in the storage settings - as if it had 128 GB and 118 GB were already used. That's strange, but it doesn't seem to affect anything so I'm not worrying about it.
Click to expand...
Click to collapse
The dialer app is what you use to call a number typing it ,it is the phone app with the telephone icon ,tap the three dots on the top right side there you will find settings ....
About the weather try changing the weather provider to Yahoo ....might work.. .
Also try getting the universal GMS doze module in magisk it stops Google services from slowing the phone ...
I personally don't use gapps at all, I have yalpstore for my app needs. if Google is not that important for you then maybe in the future you might try ROM without it .....
Hope it helps.....