Well I certainly stumbled upon this by (happy accident)!
As with all newbies who like to tinker I learnt how to recover from soft bricking one's device and am now well versed in the art of rooting, ODIN and generally ROMing to my heart's content.
Following the rooting of my device I blatted it with the rather excellent OMGBBQROM Final Release. I then installed GO Launcher HD, which is also excellent.
A while later I noticed a few issues and decided that for a balanced comparison I'd perform a recovery via the phone options to see if the symptoms persisted...
This resulted in an unwelcome boot loop so with the help of the mighty ODIN and a stock ROM I got myself back up and running.
Ever since then I get the choice of the GO Launcher HD or TouchWiz user interface when I start the device- which is cool. It also suggests that the process of flashing back to another ROM (whether it be stock or otherwise) does not wipe the entire device of everything.
I hasten to add that I do not consider this a problem in the slightest, I just find it interesting enough to share here
Anyone can have the option to choose launchers if you have 2 installed. If you go to Settings>Applications>Manage Applications and clear the defaults for the launchers, the device will ask you to choose which launcher you want anytime you navigate to the home screen(s). It will stay this way until you select "do this by default" one of the times you are given a choice of launchers.
Related
Hi all!
I've been regularly testing new ROM releases by the gurus here at XDA on my AT&T Tilt. Each install has been everything from a "close to the brick" experience, to extreme jubilation with new found speed and features. But, one issue keeps re-occuring and I'd like to ask what the best practice is for loading a new ROM image?
I ask this because it seems that each load brings new oddities and new problems that seem to occur due to past ROM images being on the device. Like right now I'm playing with a clean AT&T based ROM. Strangely though the HTC home screen is not included with this ROM, yet after the first load, whamo! the HTC home screen showed up. It was not in the installed programs list, so I couldn't easily remove it. And installs (to create an image that could be removed) failed a number of times before it worked enough to change the installation.
That's just one scenario. And I've had a lot more in very interesting ways. Like for instance, Battery Status 1.04 Ext has a seriously stong liking to my phone. That program I'd like to keep, but it's odd that it is always there, no matter what I do. And usually in some odd state that makes it hard to use until I pound it hard enough.
Also, the time seems to odd too. Every other ROM install, I'm forced to reset the time on the device at initial startup. Otherwise the time is just fine on the even number of installs.
So, what's the best routine of tasks to complete to ensure that a ROM installs as cleanly and problem free as possible. Is there a way to "clear" memory properly so nothing is left over? Dutty once helped out by suggesting that I install the OEM shipping ROM first before anything new. But that even doesn't work 100% of the time. Any suggestions are very helpful.
Thanks all for the Great ROMs. I'm having a great time playing with all the new features and abilities you guys give these awesome little machines.
Scott
weird...
The only things I can think of are obvious, but here it goes. Have you tried hard resetting / clear storage before you flash a new ROM? Are these programs being installed from your computer activesync or something? Have you tried removing your memory card?
Good Luck
When I first got my G-tab I was baffled by all the instructions and the literally thousands of posts in the forum. Even now, I haven't been able to find exactly how (or why) I should update my kernel. That said, I have TNT Lite running and I love my g-tab. Exploring the possible uses and utilities on it provides hours of fun. Now - here is my question. I stumbled on some instructions for installing the ROM and I have used those same instructions to install several patches to the Rom. I see all this commentary on Clockwork, side loading, etc. and I wonder if I am missing something. Today I just installed the .25 patch for TNT-Lite. I downloaded the rar file, unzipped it on my PC to get the Recovery folder and the update.zip file. I plugged the g-tab into the pc and switched it to usb mode. Then I moved the old recover folder and update.zip to a folder (cautious me) and put the new ones in the root. I disconnected the usb and started the g-tab in recovery mode (holding the power and volume+ key. It rebooted, applied the patch and I was done. That seems simple enough. It would seem that this would work for switching roms, applying patches and probably even upgrading the kernel (If I knew where it was and why I should do it). Am I missing something? Everything seems to work.
Sounds like you got the basics ok.
The real main reason to update the kernal as i see it is to add things like driver support for devices like gps and g3, so on, also minor fixs. If your not using your gtab for anything like this you maybe happy to stay stock. But if you like myself like to use your gtab to surf with g3 or as a sweet gps, then thats what the kernal updates allow. Im sure others can correct me if ive got anything wrong or add to what ive said.
You got the basic steps right, but installing ClockWorkMod Recovery has a lot of benefits.
First, built in backup and recovery will save your skin if the gTab get "cranky".
Second, installing ROMs and/or updates saves you a few steps. From "tar" files (TnT-lite), extract the update.zip file to a folder (I created a folder named "xda", just an example) and name it after the version of ROM/update.
CWM will flash "*.zip" file. This way you can keep multiple ROMs/updates on the card and switch between them.
CWM lets you clear cache, wipe Data partition, clear Dalvik-cache (use caution there), fix permissions and so much more! It is a great tool.
Sent from my gTablet-TnT-Lite-4.2.5 using TapatalkPro
So now we peel back another layer
OK so now the question of multiple roms comes up. I am not clear about the role of the rom - can I switch roms and keep all of my apps and data intact? I'm thinking like changing style sheets on a web page - presentation is different but the underlying data is still the same? Is it that easy?
And... if I am doing that perhaps I need to "clear cache" or "wipe data partition" but although I like to investigate new things I'm not willing to just walk up and push the big red button without knowing what it is for. So why would I "clear" or "wipe" things?
I get the impression that I could switch between ROMs just like switching between browsers on a pc - today Chrome, tomorrow, Firefox and never Internet Exploder... Is that correct? It took me quite a while to get the market working and it still doesn't work optimally but I'd hate to undo all the work I've done getting the g-tab humming along by switching roms. Can I?
So - anyone care to expound on the structure and how it all hooks together? What parts can be swapped out and what parts form the foundation? I'd hate to brick the little guy in my ignorance.
One final note if you know and you answer - where did YOU learn about this. Is there a book somewhere to read?
Thanks again for sharing your knowledge.
The Need for A Wiki
I'm in the same boat as enigma. I'm not even sure what ROM is an acronym for, though I think it means operating system. A wiki would be a big help for many people. I bet people would be glad to contribute.
Well, I don't know about Android book, especially about "hacking android book" , but this (and others) forum has plenty of reading material and guides. Not to mention people (a lot more knowledgeable and experienced than me) who will offer advice and lend a hand. And Google search comes in handy too.
Switching ROMs is almost like switching the OS, or a flavor of. Very much like switching between Linux distributions; the base OS is the same, but the overlay changes the user experience. Some things do change deep down inside, that's why is advisable to clear data.
Android, like Linux which it is based on, uses separate partitions for different parts of the OS, like boot, recovery, data, cache and user data. Plenty of write ups and discussions on the web on that.
So when flashing a ROM, you'll rewrite boot and system. Your user apps and data/preferences pertaining to those apps are stored in data partition, and since you are changing the 'OS', the apps need to be recompiled for it. Backup apps, like Titanium Backup, come extremely handy here: backup and restore apps AND appdata with a few clicks.
Backups are stored on sdcard, which is a lot like Linux /home directory, and do not get wiped during flash. Also the CWM (sometimes called Nandroid) backups are also stored there. A backup-of-the-backup is always a good habit (copy of /sdcard to your PC for safekeep).
This is just a quick rundown, hopefully that answered some of the questions.
There is a world of information available out there in "ether-world", Google is your friend.
[EDIT]:
Some links:
http://android-dls.com/wiki/index.php?title=Main_Page
http://lifehacker.com/#!5596108/how-to-choose-the-right-android-rom-for-you
and of course:
http://forum.xda-developers.com/forumdisplay.php?f=841
(use the search on top of the screen)
Sent from my gTablet-TnT-Lite-4.2.5 using TapatalkPro
Doesn't my sticky on how to flash the roms help at all? I can try to make it clearer if you have suggestions.
http://forum.xda-developers.com/showthread.php?t=892090
TeamSpeed said:
Doesn't my sticky on how to flash the roms help at all? I can try to make it clearer if you have suggestions.
http://forum.xda-developers.com/showthread.php?t=892090
Click to expand...
Click to collapse
Yes, your Sticky is as clear as Florida sky.
I just installed Thumb Keyboard on my gTab last night and I guess I got carried away getting used to it!
Yes, I have found some very good step by steps (reflashed to vegan after reading that one). Step by steps are great but I 'd like to understand why I'm doing it. The market fix...I can follow the steps and it works but why? I wish I had time to research all these things but there are so many forums,so many posts to read! The explanation that did surface in this thread was great though. Thanks. I'll keep asking questions. There are a lot of smart people out there!
I've seen a couple of threads on other phone forums with some suggestions in this arena and even some conflicting information about the best/safest way to back up user apps and then restore them after flashing a new ROM. Just wondering if there are agreed-upon best practices for this. I assume Titanium Backup is involved, whatever steps you take. Also, LauncherPro allows you to Backup/Restore homescreens and settings. I assume this would have me covered on custom icons/dock appearance/etc.
Basically, I have everything looking the way I like it with customized LauncherPro theming, and I like my array of apps. Now, I just want to experiment with flashing some different ROM/Radio combinations, but I want to be sure I have an efficient way to get me back to my preferred configuration, since I have put a good bit of time into getting just how I want it.
Any thoughts/links/procedures?
Good topic, I just back up all apps using Titainum backup and the full rom using CWR in case I need a working ROM loaded quickly. Back up the SD and your are ready for a full wipe if the new rom takes a ****.
Im in the same boat as you. Im using CM 7.0.3 and I dont think i could be any happier, however, despite spoiling myself right off the bat with Cyanogen I want to try some other ROM's. Im using titanium to backup apps, and app data as well as a daily CWR backup with rom manager, and ADWex backed up. If I was to flash a new ROM just how painless would and should it be? I understand each rom is different and require some tweakin on its own. I guess I would like to hear from the seasoned vets how they do it?
Customizing my Android phone, I've learned some things along the way that I thought other newbies like myself would be interested to know. This information can be found all over the web, but I thought speaking about these key points would be helpful...
1. If you're interested in rooting your phone, I've found the Towelroot method to be easiest. You can download the apk file for free and it makes the rooting process easy.
2. I have a method of disabling apps to improve performance that has never resulted in me crashing my phone. If you are not rooted, this probably won't be helpful. First off, get Greenify Pro and the Xposed framework, along with the ROM Toolbox. For apps that you know can be frozen safely, use ROM toolbox to freeze them, along with killing startup receivers of apps that you can safely disable from stsrtup, but can't freeze because you want to use them. Then use Greenify to hibernate apps you choose not to disable, but don't want running. I've found this method most efficient.
3. Many root their phones to remove apps that are pre-installed from your service provider, like my AT&T apps for example. I've come to realize that removing apps will not give you back usable storage space, so unless you are sure it's garbage, freezing apps is safest. Also, if you remove an app, it would be wise to backup the apk file first, just in case you need it later.
4. Since I'm a newbie, I have stayed away from custom ROMS and the sort. I've come to realize that this process is for skilled users only and many bad things can occur if this process goes awry. Always make full backups before attempting this at minimum.
5. Certain launchers, such as TouchWiz cannot be removed from Android easily, so I'd suggest you add your launcher of choice and leave the factory installed Launcher alone....
I hope this was helpful to all you newbies, good luck!!!!
Apologies in advance if this is in the wrong spot or been answered. Feel free to move or at least point me to the right spots/threads.
Here's our situation:
We have a fair sized mobile program (~1500 lines) with a mix of OS. We have been trying for awhile to convince key management that mobile has become critical. Spent the last 3 weeks effectively turning a Galaxy Tab S into a desktop. This was the linchpin that got us approval to expand. Now for the kicker:
We've been approved to roll out ~70 units to Board Members and select Directors with a standard config (apps and screens) . The problem is, they want everything deployed by December 1. The main question is, what do I use to quickly set up every one the exact same way, right down to the widgets and app screen positions? I do have general Play store and Samsung accounts, and rights to install everything on my laptop. Devices cannot be rooted (Corp policy). Any suggestions?
Thanks!
You have a week to make a full custom rom lol. Look into rom kitchen for the tab s. Widgets and default home screens are easy. Personalizing apps settings might be more difficult.
chaostic_2k1 said:
You have a week to make a full custom rom lol. Look into rom kitchen for the tab s. Widgets and default home screens are easy. Personalizing apps settings might be more difficult.
Click to expand...
Click to collapse
Can't do custom rom, device has to be stock due to corporate policy (among other factors). We don't care about personalizing most app settings (i.e. not logging them into facebook), mostly just what's on the device and the placements.
custom ROMs are Not required to be rooted. You can take a stock rom and change it. but if you're only using user apps and widgets and only need to personalize the home screen then all you need is Adb, a script and the Apk files. Turn on side loading and usb debugging, plug it in and run a script that will adb install each apk. Then set up the home screens manually. Tedious but easily done in a few days
chaostic_2k1 said:
custom ROMs are Not required to be rooted. You can take a stock rom and change it. but if you're only using user apps and widgets and only need to personalize the home screen then all you need is Adb, a script and the Apk files. Turn on side loading and usb debugging, plug it in and run a script that will adb install each apk. Then set up the home screens manually. Tedious but easily done in a few days
Click to expand...
Click to collapse
I was not aware that custom ROMs do not require root. That said, the manual home screen setup is the part we are trying to avoid. With batch install, the apps that are being installed is easy. the few that we load from the Samsung store are a bit more annoying, but still not that bad. It's that screen setup that kills us.