{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome To The One Stop Xoom Shop!
AKA: Xoom Heaven. Please Enjoy Your Stay.-A thread brought to you exclusively by: StrifeSoldierVII of XDA Forums-
(This thread is best viewed on a web browser rather than the XDA app)
DISCLAIMER: I am not held responsible for any boot loops, bricks, or damages that may occur from improper usage of rooting tools. Please read and make sure that you know what you are doing, and as always... proceed with caution. I do not take any credit for all the hard working people who made all the threads that I have linked to, I have merely gathered all of the links into one giant thread to make it easy for all to find.
There will be no further updates to this thread. I am in the process of selling my Xoom. It is a wonderful device, but since getting the Galaxy Nexus and my powerful all in one PC with a touch screen, I do not use it any longer. Thanks for your understanding. Until then, have a good time y'all!
-StrifeSoldierVII
I am selling my whole bundle of items with my Xoom. If you are interested in buying it you can find my ultimate Xoom bundle here:
http://swappa.com/listing/ECH678/view
The goal - To collect as much information as I can that relates to the Xoom, while providing a one stop shop for all users: rooters and non rooters alike. This thread will not only be for the newcomers, but also for the more advanced users alike! No one else has ever attempted to make something like this, so I have personally decided to take it into my own hands and bring it alive. Please bear with me as this is an ongoing project and will take awhile for me to fully complete.
I will continue editing, updating, and adding as much content as I possibly can to this thread until I feel that it can be called a final product. Please feel free to help me build the list by giving me some suggestions as to what I could add or do. So, link back to this thread, and tell all of your Xoom buddies about this.
If you noticed something is not right, or linked improperly... please let me know and I will fix it ASAP. Thanks!
ROOT USER SECTIONS:
SDK:
What SDK Actually Means
Downloading The SDK
ADB:
What ADB Actually Means
How To Use ADB: All Commands And Options
A Real Guide On Using ADB/Fastboot On Your Xoom By okantomi of XDA
Fastboot:
What Fastboot Actually Means: All Commands And Options
Universal Xoom Root - ANY XOOM ANY UPDATE
This is the brand new rooting method from Team Tiamat. It does not matter what model you have, what country it's from, or what Honeycomb version you're running.
This will root any Xoom you throw at it without a problem!
Universal Xoom Rooting Method By Team Tiamat
ClockworkMod Recovery:
[Recovery] ClockworkMod 3.2.0.0 (R4c)
[Recovery] CWM Rogue Recovery v1.1
More will be added over time.
Recovering Your Xoom:
If you have a softbrick or a bootloop follow these instructions: This is fairly simple to solve. Since you will not be able to boot your Xoom normally you will want to boot into recovery mode. To do this: Turn the Xoom on like normal, wait about 2 seconds after your see the Dual Core logo, then press the volume down key. In the upper left corner it should now say "Android Recovery", then press the volume up key to select it. It should then bring up the recovery menu after a few seconds. If you have a Nandroid backup, I suggest that you go and restore to that point when you made the backup, otherwise you will want to select the wipe data/factory reset option to completely wipe out the entire Xoom so that you can start fresh. Wiping data and losing everything... that is a bit extreme though, which is why you NEVER go without making a Nandroid backup when it comes to flashing a file to your Xoom. It's always a good idea to make a backup before you do anything major to the system, like flashing a new custom ROM.
Stock ROMs: (US Models Only)
3G Xoom only: Honeycomb 3.0 Stock - Builds HRI39 and HRI66
Wifi and 3G Xoom: Honeycomb 3.1 Stock - Build HMJ37
Wifi Xoom only: Honeycomb 3.2 Stock - Build HTJ85B
3G Xoom only: Honeycomb 3.2 Stock - Build HTJ85B
[ROM/UPDATE] Android Honeycomb 3.2.2 - Stock & Rooted
Stock ROMs: (Euro Models Only)
This section may or may not happen. On hold until further notice.
Help needed!
Custom ROMs:
[ROM]Team Tiamat Xoom Rom 2.1 Hammerhead
[ROM] Team Tiamat Xoom Rom 2.2 - Moray
[ROM] Xoom Zone [Derivative of Tiamat Xoom Rom]
More will be added over time.
Stock Kernels: (US Models Only)
This section may or may not happen. On hold until further notice.
Help needed!
Stock Kernels: (Euro Models Only)
This section may or may not happen. On hold until further notice.
Help needed!
Custom Kernels:
[KERNEL][AOSP]Tiamat Xoom 2.1.0 "Tachi"
[KERNEL][AOSP]Tiamat Xoom 2.0.0 "Katana"
[Kernel] Launchpad 1.3.0 Gemini
[Kernel] Rogue 1.3.1 "Arcturus"
More will be added over time.
Custom Themes:
Honeycomb XML Info: For Theme Makers And Developers
[THEME] ☢ BigDX Xoom|Zoom Theme ☢
[Theme]TouchWiz for Tiamat 2.1
[Theme] US Wifi 3.2 Deodexed Honey Bread Port
[THEME - WIP] Stargate
[THEMEs] StockRed & StockGreen & StockGrey
More will be added over time.
Custom Boot Animations:
Bootanimation Installer v3.3
Boot Animation Collection - 14 Total
Xoom Forums: Boot Animations Section
Because there are just too many to list, I have included the Xoom Forums website since they now have a dedicated boot animation section. You will find all types of boot animations there.
Custom Battery Icons:
Ultimate Online Theme Kitchen: UOT - Easily Make Your Own Battery Icons
[MOD] Stock Battery and UA for Tiamat Xoom Rom 2.1
More will be added over time.
Root Apps To Help You Get Started:
Superuser
Superuser Update Fixer
Titanium Backup
ROM Manager
SetCPU for Root Users
AutoKiller Memory Optimizer
AdFree Android
Root Explorer (File Manager)
Bloat Freezer - Root
CacheMate for Root Users Free
Screenshot ER 2
LCD Density Changer
Quick Boot (Reboot)
Autostarts
Battery Calibrator
Sixaxis Controller
SuperDim [root]
adbWireless (Widget version)
MicroSD Mounter
TabletBar Hider (Root)
Virtual Button Bar
Absolute System Root Tools
More will be added over time.
Other Useful Root Information:
1. If you plan on re-locking the bootloader for some reason, please only use the stock image files straight from Motorola. The official image files can be found here. You must have a Motodev account in order to download the image files. Once you have an account, download the appropriate image file for your Xoom model, and then follow the instructions on the Motodev website for the fastboot commands to re-lock your Xoom. Once you are finished, you will be back to factory stock with no root at all. Useful if you are returning the Xoom back to a retailer, or a similar situation.
2. When using ClockworkMod Recovery, please do not update it when ROM Manager tells you there is an update, just leave it alone. Only use the CWM Recovery found in the section above, otherwise you may run into a few issues.
3. When installing a custom Rom, it is usually a good idea to not only make a Nandroid backup, but to also wipe data and caches before installing. Sometimes you can get away without having to do a data wipe, but it is not recommended. Here is what you should always do: First, back up only your apps with their data via Titanium Backup, boot into recovery mode, make a Nandroid backup of your current Rom, wipe the data and caches after that, and then finally you will want to restore your apps and their data via Titanium Backup.
4. When backing up and restoring data... DO NOT EVER back up system apps and system data or restore them! If you are on a 3.1 Rom and are updating to a 3.2 Rom, it is not a good idea to restore your system apps and system data from the previous 3.1 Rom. Doing so may cause some very strange issues, and possibly a bootloop in some cases. You only want to backup and restore your apps with their data, please remember that.
5. Make life easier: If you happen to have the Pro version of Titanium Backup, then you will like this one if you already don't know about it. Within the app you will want to bring up the menu, hit market tools, then hit market auto updates, select all, then save auto updates configuration. Thus, from here on out: Most/all apps in your market installed list will do all of the updating for you. Much easier than selecting auto update one by one for each app. And this literally takes a second to do.
NON ROOT USER SECTIONS:
Non Root Apps To Help You Get Started:
Adobe Flash Player 10.3
Adobe Reader
Adobe AIR
Equalizer
Amazon Appstore
Kindle for Android
Amazon.com Mobile App
Barcode Scanner
Beautiful Widgets
Bluetooth File Transfer
File Manager HD
CircleLauncher
ADWLauncher EX
Dolphin Browser HD
Dolphin for Pad V1.0 Beta
Easy Uninstaller
Google Sky Map
Google Earth
Music Beta By Google
Google Voice
Google Body
Tiny Flashlight + LED
GrooVe IP (For Making Phone Calls)
IMDb Movies & TV
MP3 Ringtone Maker
News360 For Tablets
Pandora Internet Radio
TuneIn Radio
PicSay Pro
PowerAMP Music Player
RealCalc Scientific Calculator
Smart Keyboard PRO
Thumb Keyboard (Phone/Tablet)
SoundHound Music Identifier
DeskSMS
SyncSMS
NVIDIA Tegra Zone
WeatherBug For Honeycomb
Writepad Stylus
Power Widget
MultiPicture Live Wallpaper (For Setting High Res Wallpapers)
Screen Filter
Night Clock
Musical Pro w/ Piano
NOOK for Android By B&N
Official eBay Android App
Quick Settings
MyBackup
XDA-Developers (Of course!)
Autorun Manager
Netflix
Wizz Bar
NFL ‘11 for Android Tablets
More will be added over time.
A Special Thanks Goes To:
All the hard working developers, as well as all the hard working people that put all of these individual threads together! Without you guys we would not get anywhere! You all are truly awesome!
Please Visit My Other Personal Threads:
Music Beta by Google: A Must Read For All Root Users!
Adding Spice To Your Xoom's Life: Skin It!
[TIP] How To Enhance Screen Quality For Xoom
[TIP] How To Get A More Stable Xoom Startup From Lockscreen
More will be added over time.
Don't be afraid to leave any comments or questions that you might have, and please don't forget to give me some kind of thanks if you found this thread was useful to you. I'm working very hard to gather and to put together all of the content by myself, so don't forget to spread the word about this thread so that more people can enjoy it.
If you appreciate what I'm doing, please consider making a donation to me. I'm a college student and all that with all of the typical expenses. I do this on my own free time when I can. Any donations would be very much appreciated. If you would like to donate, click the "Donate to me" link above my avatar picture. Thanks!
Thanks man the Xoom thread needed something like this...
This is terrific...it's the beginning of that wiki we've discussed. At the least, this should be made into a sticky.
It would be nicer if you update few more links about how to fix problem like boot lop, softbrick, motorola factory cable, back-to- stock....
okantomi said:
This is terrific...it's the beginning of that wiki we've discussed. At the least, this should be made into a sticky.
Click to expand...
Click to collapse
I think it should be as well. I might need some help with this though.
tritran18518 said:
It would be nicer if you update few more links about how to fix problem like boot lop, softbrick, motorola factory cable, back-to- stock....
Click to expand...
Click to collapse
Great idea! I was going to add that in soon, but it took me awhile to put this together and collect all the proper links. I'll get right on that.
I'm getting ready to root my Xoom, but have a question more a concern of confusion. I updated my wifi only Xoom to 3.2 when it became available manually here and the build is HMJ85B and not MZ604 as stated for my model here. I've had no issues or problems whatsoever from this, but I'm confused on how and why it took and no problems have arose whatsoever. I'm accustomed to jailbreaking idevices and I've even rooted and unlocked a few friends android phones. So in knowing what little I do know, my question and or concern is if I root my Xoom with this build currently on it, will there be a greater margin for failure or maybe bricking and should I try to manually push build MZ604 onto it before hand? Thanks to any and all input and or advice in this matter. Once again I've experienced no issue whatsoever since updating and really it improved my Xoom experience! As I know I'm a NOOB at rooting though and I'm looking for the more experienced input and direction.
Sent from my Xoom using XDA Premium App
Great, very useful thread....this should definitely be stickyed.
Sent from my GT-I9000 using XDA Premium App
rmax67 said:
I'm getting ready to root my Xoom, but have a question more a concern of confusion. I updated my wifi only Xoom to 3.2 when it became available manually here and the build is HMJ85B and not MZ604 as stated for my model here. I've had no issues or problems whatsoever from this, but I'm confused on how and why it took and no problems have arose whatsoever. I'm accustomed to jailbreaking idevices and I've even rooted and unlocked a few friends android phones. So in knowing what little I do know, my question and or concern is if I root my Xoom with this build currently on it, will there be a greater margin for failure or maybe bricking and should I try to manually push build MZ604 onto it before hand? Thanks to any and all input and or advice in this matter. Once again I've experienced no issue whatsoever since updating and really it improved my Xoom experience! As I know I'm a NOOB at rooting though and I'm looking for the more experienced input and direction.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I hope I didn't make a mistake with the build number for the 3.2 Wifi model... there's so many builds, and areas of the world. I'm trying to cover the US models... I may have matched it with the wrong build, as I have always had the 3G Xoom... I'm not too familiar with the Wifi builds. I'll double check these.
EDIT: Thanks! I did have the wrong build number for the stock 3.2 Wifi Rom. All fixed. I know I'm really tired, I mixed it up somehow.. lol. You'll be a-ok. I had the wrong build number but the link is correct.
cause it is all-in-one thread, a warning section might be usefully such as: only relock bootloader on xoom wifi version by using stock 3.0.1 image provided by Motorola...
P/s:I would like you to add links about install sdk/fastboot and how to use adb/fastboot command .
tritran18518 said:
cause it is all-in-one thread, a warning section might be usefully such as: only relock bootloader on xoom wifi version by using stock 3.0.1 image provided by Motorola...
P/s:I would like you to add links about install sdk/fastboot and how to use adb/fastboot command .
Click to expand...
Click to collapse
That's good! These are the ideas I need to make this a true all-in-one list. Thanks again! I will add these in as soon as I can. For now I need some sleep.
I need some help, XDA community! I need help putting together the stock kernels section. If you guys can help me collect the stock kernels from Honeycomb 3.0, 3.1, and 3.2, that would be great... for both the Wifi and 3G Xoom models. I would appreciate it!
The stock kernels section will be delayed for a bit until I can get a hold of the necessary files.
Am I right in thinking this is just for US Xoom's
If so a note saying that might be useful to stop non US rooting with wrong files.
Big_Ted said:
Am I right in thinking this is just for US Xoom's
If so a note saying that might be useful to stop non US rooting with wrong files.
Click to expand...
Click to collapse
Yes, this thread is currently focused on the US Xoom models only. I will add a note about this right now. Thanks!
I might get into adding the other Xoom models to my list in the near future when my thread is more complete. Until then, I apologize for that.
If someone were to help me with the other models outside of the US, I could finish this much faster. Just the US models alone is a lot of work.
EDIT: Added US only model notes to thread. Thank you! I should have added that in right away.
diablo2224 said:
I need some help, XDA community! I need help putting together the stock kernels section. If you guys can help me collect the stock kernels from Honeycomb 3.0, 3.1, and 3.2, that would be great... for both the Wifi and 3G Xoom models. I would appreciate it!
You can PM me, or post in my thread here. I'm currently still working on all sections, but the stock kernels section will be delayed for a bit until I can get a hold of them.
And more suggestions I can add into this list would be great!
Click to expand...
Click to collapse
How would you prefer submissions? You are doing a tremendous job. I know you need help.
okantomi said:
How would you prefer submissions? You are doing a tremendous job. I know you need help.
Click to expand...
Click to collapse
Thanks for the compliment!
I would actually prefer people to PM me either working links to a direct download or working links to a thread that has the files I need. I'll put the people who helped me in a special thanks section of the thread to give credit to them.
Just want to double-check before I plow away at this...as to getting completely back to stock for a return or warranty work, we do not need to create images of stock. just use the images in the first post? This will put back the stock 3e recovery and everything?
Thanks
Barsky said:
Just want to double-check before I plow away at this...as to getting completely back to stock for a return or warranty work, we do not need to create images of stock. just use the images in the first post? This will put back the stock 3e recovery and everything?
Thanks
Click to expand...
Click to collapse
It's recommended that you flash the stock images found at the Motodev website and then re-lock the bootloader for a return or warranty work. Especially since being rooted voids the warranty. That's why it's important to use the official stock images from Motodev before doing anything like this. It's said that they will never know you had been rooted in the first place by using this method, thus the warranty was never voided. Hope this was the answer you were looking for.
diablo2224 said:
. That's why it's important to use the official stock images from Motodev before doing anything like this.
Click to expand...
Click to collapse
Wait, diablo from Samsung Captivate roms? dude, you always rock
"before"? wouldn't images be used after to return it to factory condition? again, just going ultra-safe mode here
Thanks, as always!
Barsky said:
Wait, diablo from Samsung Captivate roms? dude, you always rock
"before"? wouldn't images be used after to return it to factory condition? again, just going ultra-safe mode here
Thanks, as always!
Click to expand...
Click to collapse
The stock images provided by Motodev will get you back to a completely stock factory Rom, but your bootloader will still be unlocked, which the retailers will be able to tell. You''ll want to flash the image file to get back to a factory stock Rom, and then run the Fastboot commands on their website to lock the bootloader back up. Thus the end result is: a factory stock Rom, a locked bootloader, and no trace of root. It's just as you bought it from the retailer out of the box.
I'm not sure if this is what you are looking for, but it's good info nonetheless.
diablo2224 said:
The stock images provided by Motodev will get you back to a completely stock factory Rom, but your bootloader will still be unlocked, which the retailers will be able to tell. You''ll want to flash the image file to get back to a factory stock Rom, and then run the Fastboot commands on their website to lock the bootloader back up. Thus the end result is: a factory stock Rom, a locked bootloader, and no trace of root. It's just as you bought it from the retailer out of the box.
I'm not sure if this is what you are looking for, but it's good info nonetheless.
Click to expand...
Click to collapse
Got it. Thanks much
Related
With the surge of some ROMs for our devices, and though they're related between each other to a certain degree (save for CM7), the inevitable question surges: which one has the upper hand? The stock ROM is vastly improved since 1.06 and Ganjaman's add-ons make it more mature, the MoDaCo ROM has the advantage of having been the first modded ROM, CyanogenMod7, thanks to Apache14's work, has made a stellar appearance and we actually get the official updates (such as the ones that mad-murdock presented us yesterday), Corvus has been updating his new ROM quite rapidly and it works nicely, like Fuji-Vega does... We're lucky that we're not in want of possible choices! But which is yours?
Thread moved to General.
For me corvus. It's so quick and stable, and is the only one, where's my usb 3g huawei running. Did I told you, that it's really fast?
Sent from my X10i using XDA Premium App
I agree totally, corvus is so quick. I can't wait until it can be combined with mad murdoch's HC tweaks, the vega will be Ninja then!
support
@logseman
great idea for a thread. I'm considering starting a thread on a similar line, thought id check in and avoid toe treading and see if there is a need for it.
As a newb to vega android modding, its great that there is such a wealth of info and advice, but sometimes its not clear or comprehensive (at least in one place! )
I'd like to run a "what vega setup is best for me" thread. The aim being to allow users to show exactly what setup they are running, how it performs, pro's and cons, bugs etc.
By using a standard template, we can see what works and why. We can make direct comparisons between setups without searching through threads for hours.
Users can then copy setups and try if they think they like it. Might also provide devs useful concise feedback to help them progress roms / kernels etc.
If it already exists, feel free to point me in the right direction whilst mocking my newbe stupidity, but ive read and re read the main threads and can't see it.
If you're reading this and think it would be useful, let me know, with suggestions and i'll get the ball rolling.
I.A.O.
Edit: if you want to help or collaborate, pm me.
I'm not sure how setting up a "standard configuration" would be of benefit. Primarily because of two issues: first, the same custom ROM can have dramatic performance differences between one device and the other (I am a ROM tester for Galaxy S, people claim battery lives of 4 days which I've never heard about); and second, the point of Android is that it actually doesn't force any standardisation as of now: I don't see why users would tend to a certain set up which has been done by another person instead of experimenting themselves.
Don't take me wrong, I appreciate that you take interest in this thread, but I fail to see the point of your suggestion. Android has no predefined "set-ups" as far as I know.
Yeah, i get your point. For me too its all about modding and tweaking. But i also got the impression that some people just want to get there device configured in a way that works for them quickly.
Im certainly Not saying lets all set up the same, if we wanted that we'd just bite the apple right!
I just think it would be useful to see at a glance what is working for people. I.e - "i need a rom with no lag on my vega - ah looks like cm7 ttrc2 has lag issues", without having to read 178 pages to find out.
I guess it would be more like an "at a glance" guide to roms for each device.
I used Modaco since i got my Mobii/Vega, but yesterday i flashed clockwork recovery and started using Titanium backup for real, so now i am testing some ROMs and sofar i like fuji-vega the most, fast and smooth, only some lag in appmenu when i have the device rooted.
I spent a long time using mcr8 eventually with buzz kernel but I then got bored and tried cm7 which I loved but just could not stand all the lag when scrolling etc.
I am now using corvus which seems to work well for me. I hope to switch back to cm7 when it improves a bit.
I love CM7 on my phone and would love it on the Vega, but the wifi troubles it has at this moment on the Vega made me switch to first Modaco and than Corvus. The only bad thing I can say about Corvus is that I personally would prefer Gingerbread green icons aboive the blue ones in Corvus
Slipurson said:
I used Modaco since i got my Mobii/Vega, but yesterday i flashed clockwork recovery and started using Titanium backup for real, so now i am testing some ROMs and sofar i like fuji-vega the most, fast and smooth, only some lag in appmenu when i have the device rooted.
Click to expand...
Click to collapse
I am in a similar position to you. I have only installed Modaco R8 and not really used Titanium Backup nor Clockwork Recovery. I find R8 lags after extended use (requiring a reboot) so I am interesting in changing to Corvus. I have a few questions.
What is the best way to move from Modaco to Corvus?
Can I use Clockwork Recovery/Titanium to ease the pain of transition?
How do I install CWR?
Is it best to go back to stock and then install Corvus? If so, will I lose all of my customisations?
Thanks in anticipation of a response.
What is the best way to move from Modaco to Corvus?
Click to expand...
Click to collapse
I would do a Ti Backup of everything, then a nandroid backup before flashing.
Can I use Clockwork Recovery/Titanium to ease the pain of transition?
Click to expand...
Click to collapse
Definitely use both of these, pay for Ti Backup to enable auto batch stuff
How do I install CWR?
Click to expand...
Click to collapse
Try THIS thread
Is it best to go back to stock and then install Corvus? If so, will I lose all of my customisations?
Click to expand...
Click to collapse
You would want to wipe when doing an install of a different rom anyway, so you will lose settings, most will be restored by Ti Backup though.
> I would do a Ti Backup of everything, then a nandroid backup before flashing.
Sorry, how do I do that? I have Modaco R8 with Titanium Backup installed. How do I use Ti to "backup everything", what is a "nandroid backup", and how do I restore stuff after installing a new ROM?
Cheers.
you can find this information quite easily by searching
ti backup press menu>batch>backup all user apps and system data
Then after installing cwm (download zip open
cd /path/to/folder
./install.sh for mac and linux (make sure to downlod my fixed scripts second post)
or
click install.bat for windows
then click recovery app use volume buttons and power to select backup and restore)
wipe data instal rom
ti backup from market
menu>batch>restore all user apps and system data (modaco is similar to corvus so should be safe to restore everything if things start crashing repeat install and untick all apps that are already installed in ti backup)
there you go you have transitioned
sorry if this sounds patronising it sounded like you were a noob so i included great detail
p.s. this will all become second nature after a while
hmmm atm i'm using CM7, and after switching to launcher pro it's so fast !!
adw launcher is such a crappy launcher (sry, my opinion)
anyways, my flash is pretty laggy due to the unstable nightly builds, I mean they're not in the fully power.. but I will wait, <3 cyanogem
I wish we had the HC update soon, rly =(
Ive been using Fuji-Vega since april and applying updates when they become available.
Really happy with it and cant complain. Does what i need it to do.
Very quick to use.
Corvus5 for me right now. it's stable and fast as, with oc I have been using cm7 until a few days ago and will no doubt give the latest a shot before the weekends gone, it now has oc kernel
I can't use custom ROMs because nor CM neither Corvus doesn't let my Huawei e150 connect to internet. When I'll solve this problem CM'll my choice.
CM7 for me. I've tried a few but CM7 just feels/looks slicker.
Will there ever be a fully working honeycomb rom?
Sent from my HTC HD2 using XDA Premium App
What else do we need to start getting some custom roms like CM7 and others like XxVirusxX. What is need to take an AOSP and build it for our Elocity? I recently got and Evo 4g rooted is same day, now running CM7 rom, tiamat kernel, viper undervolt Is it possible to get these to work on this elocity?
its possible to port components and features of other roms, or to compile other roms for the a7. i compiled a clockworkmod recovery that i have posted on my twitter and elsewhere than you can use to conveniently backup/switch/restore roms and data with, which will aid in additional roms being made accessible, as loading them (and recovering from them) will be more convenient.
also gotta good /device setup for the naz10 going for use in rom compiling. mebbe i'll post it up for others when i have it near complete.
How did you get the clockwork mod to flash? Also I'm assuming you finished the key mapping that hadn't been done?
bestialbub said:
its possible to port components and features of other roms, or to compile other roms for the a7. i compiled a clockworkmod recovery that i have posted on my twitter and elsewhere than you can use to conveniently backup/switch/restore roms and data with, which will aid in additional roms being made accessible, as loading them (and recovering from them) will be more convenient.
also gotta good /device setup for the naz10 going for use in rom compiling. mebbe i'll post it up for others when i have it near complete.
Click to expand...
Click to collapse
Is that why it has been so quiet in here haha
Sent from my Mynized EVo 4G
smal you can't say it wouldn't be awesome to have half the stuff you have for evo for the elocity
rombold said:
smal you can't say it wouldn't be awesome to have half the stuff you have for evo for the elocity
Click to expand...
Click to collapse
Oo of course, with out a doubt, Im just sitting back waiting for one of these great devs. Hopefully they got something good from the kernel Source
Sent from my Mynized EVo 4G
i might throw my sifted kernel source up for dev types to browse thru. just the added and modified source from elocity, not the whole package, so one can see what elocity did. pretty sure i spotted changed accelerometer settings in the kernel source that could aid in correcting that issue on a kernel level possibly.
i'm still moving slow without adb access. either have some service or kernel reconfiguration to do for that one. too many fun things to do, not enough personal time to get em all done swiftly.
Sent from my X10i using Tapatalk
Time will only tell and I got plenty of it
ayup, got the key mapping working with the latest clockworkmod recovery.
http://twitter.com/#!/bestialbub
it was confusing because it seems the newest version has a secondary back button. had to scratch my head a couple seconds until i figured to map it to the volume key and forget the key combinations for toggling display on and off.. tho power+search might toggle it (not really a useful feature of any concern).
oh, if you look at the devices existing keylayout, the volume or 'media_key' has the value of 213.
i left out instructions for flashing with apx on purpose. if you don't know how, you probably shouldn't, because i don't have a fix today for you if you break your device some how. i'll see about posting some complete apx backup scripts, along w/ a nvflash pack that doesn't have the added rom bloat + stock and my cwm recovery image. but that might be like in a week. i got that adb to work out, file permissions to finishing documenting for fun, and repacking the factory rom for cwm for fun.
nothing to exciting towards new features regular users will enjoy today, but something romheads/chefs/modders/themers will like to make software work and testing easier.
I Gotta get another male/male USB Wire, and I'll Be Watching out for Updated on This and Following you on Twitter no Also, Im Willing to try just as long as the directions are clear. Right Now im waiting on some HTC Sense 3.0 for the EVO. So im on XDA all Day haha
ROMBOLD: Check Your PM
bestialbub said:
i'll see about posting some complete apx backup scripts, along w/ a nvflash pack that doesn't have the added rom bloat + stock and my cwm recovery image. but that might be like in a week.
Click to expand...
Click to collapse
Awesome... <3
Either one would be awesome Amon ra or CWM recovery Wonder how much the tiamat kernels require to work for us?
cwm recovery is done and available for use. questions; leave at the link you download 'em from.
http://twitter.com/#!/bestialbub
i also have the factory rom repacked and install script made for use w/ cwm (and maybe factory) recovery. this should step up the ability for folks to mod and theme the existing roms. will post tomorrow, then mebbe post an nvflash/apx pack for backup/restore/recovery flashing before i get started on themeing to follow.
I finally decided to root my g2 but I'm quickly becoming overwhelmed with all the possible choices and information. This is what I'm looking for and hopefully somebody can tell me the simplest way to achieve it.
I want good gps and working Google talking navigation.
I need working wifi calling.
I want to safely over clock.
I am not overly concerned with appearance, i just want something that works well with no bugs. I've been using cm7 nightly on my nook color and I'm happy with it, but does cm play nice with gps now? I've read several threads about other roms and that's why I'm stuck. I really don't want to have to experiment with a dozen different setups. Thank you ahead of time!
Most ROMs in the dev section provide all 3 of those. Any custom ROM allows overclocking, nearly all provide WiFi calling (or you can add it later), and gapps provides your navigation/gps functionality.
You can read before installing whether or not there are known bugs (some AOSP ROMs have GPS issues), and then troubleshoot afterwards if you have issues.
Just be sure to back up with ROM manager before you flash, and you can always go back to the previous setup if you're unhappy with the way your chosen ROM performs for you.
I'd recommend the ROM in my signature to meet all of the needs you mentioned. It's fast, reliable, and has incredible support... essentially it's a moderately modded version of CM7.
Sent from my HTC Vision using XDA App
Be sure to follow the wiki for rooting its flawless.
As for rom choice I always, always end up back on CM7. Nothing beats its out of the box functionality and stability.
Sent from my HTC Vision using xda premium
I've used Virtuos Sense 2.0.0 and now I'm on InsertCoin Sense 2.1+3.0. Both are great and should fit your needs.
Basically, once you root your phone changing ROMs is easy so you can try different ones and see which you like best.
Thanks for the replies so far. If I get anything wrong or mistaken, please jump in and correct me:
From what I've read, I don't think I'd like any of the Miui-types, they seem more iPhone like than android and I really don't like the iphone.
CM7 is cm7, so it'd be the same on my G2 as my nook color, right? My NC has a built in overclock, I didn't have to add anything extra, is CM7 for the G2 the same?
I've read many threads about how good Virtuous is, but seems like just as many people say it's too resource intensive and slow. Comparing it to the stock Tmo 2.2 or 2.3, is it at least as good? Seems pointless to develop something if it's slower than stock. Is the Insertcoin just a variation of virtuous?
I'm intrigued by Dit's recommended rom, that may be my first choice to try.
I guess I'm really looking for a 1 stop shop, it took me a little while to get the market working on my NC. Do any of the mentioned rom's have everything from the start, or do I still need to add pieces (like gapps, or wifi calling) after installing the rom?
The other rom that has my interest is meXdroidMod, any opinions on it?
I've read many threads about how good Virtuous is, but seems like just as many people say it's too resource intensive and slow. Comparing it to the stock Tmo 2.2 or 2.3, is it at least as good? Seems pointless to develop something if it's slower than stock. Is the Insertcoin just a variation of virtuous?
Click to expand...
Click to collapse
Virtuos Sense 2.0.0 is Sense 2.1, so it's not slower than stock (in fact it's faster, thanks to optimizations and Virtuos OC Daemon) and doesn't have any weird issues.
InsertCoin is developed by a different team and uses a different kernel (rmk), so I wouldn't call it a variation. It's also different in that it combines elements from Sense 2.1 and 3.0, while Virtuos ROMs are either full 2.1 or full 3.0.
i guess we all missed the main point here and is how to root lol heres the best guide for rooting your G2/Desire Z:
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
about the ROMs if you like CM7 go ahead and try it for, its the same as the one you have on your nook, and yes you can overclock without adding anything
about gps on cm7 most people have had trouble with it, but you just need to try cause i really never had any problems
Yea wipe efs before flashing, it will eliminate a lot of common issues with gps and such. Superwipe + will wipe everything well. Don't forget to flash recovery and do a nandroid backup! Also to make the transition easier backup with titanium backup pro. I use virtuous glite btw it looks stock except with light overclock and it is solid. Virtouos basically took the stock rom removed a lot of the bloat and overclocked and pre-rooted it. Works great my only hiccup was I had to grab the swpye beta apk. Aside from that I just restored my apps and I was away.
kingston73 said:
Thanks for the replies so far. If I get anything wrong or mistaken, please jump in and correct me:
From what I've read, I don't think I'd like any of the Miui-types, they seem more iPhone like than android and I really don't like the iphone.
CM7 is cm7, so it'd be the same on my G2 as my nook color, right? My NC has a built in overclock, I didn't have to add anything extra, is CM7 for the G2 the same?
I've read many threads about how good Virtuous is, but seems like just as many people say it's too resource intensive and slow. Comparing it to the stock Tmo 2.2 or 2.3, is it at least as good? Seems pointless to develop something if it's slower than stock. Is the Insertcoin just a variation of virtuous?
I'm intrigued by Dit's recommended rom, that may be my first choice to try.
I guess I'm really looking for a 1 stop shop, it took me a little while to get the market working on my NC. Do any of the mentioned rom's have everything from the start, or do I still need to add pieces (like gapps, or wifi calling) after installing the rom?
The other rom that has my interest is meXdroidMod, any opinions on it?
Click to expand...
Click to collapse
Gapps is embedded in the ILWT ROM, as is the EFS wipe tool, to help eliminate GPS issues (plus radio suggestions/info in the OP). Wifi Calling can also be added during ROM install. The OP gives all the info you could possibly need in his thread. Give it a thorough read... seems to cover all the things you've mentioned. And I've had nothing but best experience with it... been running it since nightly 186.
I've successfully rooted following the wiki, I was pretty nervous about screwing it up but everything went smoothly and exactly how it was written. I installed RomManager and flashed "clockworkmod recovery" and then clicked on "backup current rom" and it rebooted the phone and gave me several choices. I used the volume button to select "backup and restore" and selected that, and now it is showing me a screen with a top hat over an orange ring, it's just sitting there with no progress bars and no words. I was following the directions from this site:
http://www.androidpolice.com/2010/0...nandroid-backup-and-clockworkmod-rom-manager/
but it doesn't look like the screens on that site right now.
Is this supposed to happen, or did I somehow screw something up when I've barely gotten started?
You still need to flash a Recovery... you can do this through Rom Manager... but use version 3.0.2.4. Or, you could check out the Recovery in my signature. 4EXT Recovery... it's pretty wonderful. After you flash your chosen Recovery you will be able to make a NANDroid backup.
Misread your post. Yeah, you probably used the trackpad... sorry.
Sent from my HTC Vision using XDA App
Did you use the power button to select?Don't, use the trackpad
I thought clicking "flash clockworkmod recovery" was flashing a recovery? My big question is what do I do right now, as things seem locked up with just the hat/orange ring on the screen. It's been that way for about 5 minutes at least. Can I power off without hurting anything? And yes, I used power to select "backup/recover".
Press it again and then use the trackpad to scroll and select,that screen is like a screensaver so to speak.
Bombadier,
Many, many thanks to you, I was afraid I'd royally screwed up. If it wasn't for your help in my ADB thread I wouldn't have made it this far, many and much thanks!
No problems happy to of helped
Last question for the night, and sorry if this is a dumb newb question. Once a rom is flashed, what is the easiest, quickest way to reinstall all my old apps?
When you log into google your apps are synced,would recommend getting titanium backup though,a good app which can backup,restore apps,upload to dropbox,uninstall system apps very useful indeed
kingston73 said:
Last question for the night, and sorry if this is a dumb newb question. Once a rom is flashed, what is the easiest, quickest way to reinstall all my old apps?
Click to expand...
Click to collapse
Before you flash a new ROM, download "Titanium Backup" off the market and use the Menu button to select Batch. Do a backup of all your apps and data (not system data), and when you flash a new ROM, reinstall Titanium, select Batch mode again, and restore all missing apps and data.
Hey guys just wanted to share this with you. I am working with Team Win to get a touch recovery on the A500. So far is still inop, but progress is bring made. We are gonna give another go tomorrow so wish us luck. Will keep you all posted.
Updates
1-5-12: So we are finding the using the tablet interface makes the recovery too large for our recovery partition. Team Win is probably going to have to build the recovery without an interface and then I will create a flashable zip that will flash the recovery as well as place a ui.zip on the external sdcard under twrp/theme(we can then just replace that ui.zip for different themes that come out, got a cool ICS one in mind already). The battery precentage is working but we are still working on the touch screen. New test build coming today and will have active logging enabled so that we can see more of what is happening, if touch is being recongnized but TWRP 2.0 is just not reacting to it. It's coming along though.
1-6-12: SO we got TWRP 2.0 up and running for the most part. Touch screen works and most all functions work. Get backup failures and is not sized properly but we are really, really close. Did install a rom and booted just fine. Release will be real soon, possible monday. Still have to get the resolution figured out as well, but what we have so far is very usable.
2-17.. So work on this has slowed way down due to dev on teamwin side has other projects that he is working on that is more important to him(which there is no problem with that, would just like to get this project completely going). But TWRP 2.0 has gone completely opensource. So just wondering if we can tackle this and get it up and running. We are on #twrp on freenode irc usually everyday M-F around 11am-1pm Mountain Time. If you are able and willing to help, please come and give us some fresh ideas.
3-8. Everything is working and is ready for release very soon. Some final testing and will be release. Data/media fixed and flexrom fixed. PLEASE HOLD!!
3-13. New features being added. We will have the ability to toggle back and forth between internal and external for backup location. Doing some code clean up and making sure all features are working properly. Have used it to install many roms/flashes and have yet to have any issues. It's coming along nicely. Huge thanks to Dees_Troy on TeamWin for his work on this. You da man!
I run TWRP 2.0 on my Evo 3D. Would love to see it on my A500. So much better then all the button presses to navigate through the recovery menu.
I would love to see TWRP 2.0 on the A500. I have it on my Sensation and think it is some of the absolute best development to come out of the Android development community recently. Best of luck guys.
Muahahaha. Can't wait!!!
Sent from my HTC EVO 3D using Tapatalk
Updated OP with some status update.
I used a steam recovry on my captivate that was full touch and really liked it. I dont remember any sort of oddities to get it running. Maybe talk to one of them and see how they got theirs set up.
if i can make one request i sed it on my phone and it was awesome. One thing the when selecting ROMS the font is small and often hard to hit the right one
IIRC you need to have the "itsmagic" script run at boot. When I came to the A500 scene it was already figured out so I'm not 100% sure on what it was or what exactly it does but I would recommend looking in to it. I'm sure some more senior A500 developers could help with its purpose.
Sooooooo close!
Updated OP, she is almost ready!
That is looking sweet, I like that 2nd gui alot better than the first one. A lot cleaner. rstuckmaier brought up an important point, are you including the "Its Magic" script in the recovery. I thought that was needed to fix the checksum values.
I don't see where any of the new recoveries do anything with "itsmagic" during the install process. The new GPL complient does nothing with itsmagic. Nor do thors.
Here are some screens of the boot up screen and a ICS theme.
pimpmaneaton said:
Here are some screens of the boot up screen and a ICS theme.
Click to expand...
Click to collapse
Great job!
cruise350 said:
That is looking sweet, I like that 2nd gui alot better than the first one. A lot cleaner. rstuckmaier brought up an important point, are you including the "Its Magic" script in the recovery. I thought that was needed to fix the checksum values.
Click to expand...
Click to collapse
Yeah the first shot we were running the phone layout, Second is a tab layout but not correct res. We should get it all figured out monday.
pimpmaneaton said:
Yeah the first shot we were running the phone layout, Second is a tab layout but not correct res. We should get it all figured out monday.
Click to expand...
Click to collapse
I'm certain you'll post it up in the DEV sections as soon as it's ready for "prime time"!
Thanks again for your dedication and hard work!
kjy2010 said:
I'm certain you'll post it up in the DEV sections as soon as it's ready for "prime time"!
Thanks again for your dedication and hard work!
Click to expand...
Click to collapse
Yes I will, no need to just have small talk about it in the DEV thread untill she is ready to Rock&Roll. I am hoping that this will breather new life into this thread and Iconia A500 communtiy. I know I have not done a whole lot, but plan on doing more. 1st-TWRP 2.0, 2nd- New Galaxy Rom.
pimpmaneaton said:
Yes I will, no need to just have small talk about it in the DEV thread untill she is ready to Rock&Roll. I am hoping that this will breather new life into this thread and Iconia A500 communtiy. I know I have not done a whole lot, but plan on doing more. 1st-TWRP 2.0, 2nd- New Galaxy Rom.
Click to expand...
Click to collapse
We need a good new Galaxy ROM! Back when these tabs first came out, M-Deejay's Galaxy port was my favorite ROM. Of course that was back when I was flash crazed, and looking for a fit to my preferences. Can't wait for it!
pimpmaneaton said:
Yes I will, no need to just have small talk about it in the DEV thread untill she is ready to Rock&Roll. I am hoping that this will breather new life into this thread and Iconia A500 communtiy. I know I have not done a whole lot, but plan on doing more. 1st-TWRP 2.0, 2nd- New Galaxy Rom.
Click to expand...
Click to collapse
Thanks for this. Read up on TWRP and it sounds and looks great. Definitely looking forward to your Galaxy offering.
Great job spear-heading these efforts. They are appreciated.
pimpmaneaton said:
I don't see where any of the new recoveries do anything with "itsmagic" during the install process. The new GPL complient does nothing with itsmagic. Nor do thors.
Click to expand...
Click to collapse
"itsmagic" is needed to recalculate the ROM checksum for the encrypted bootloader, which is verified every time you boot. Either you need to execute it (and Thors DOES do that, just read the install instructions for his 1.6 V2 recovery), or you need to incorporate its code into your recovery.
If you flash a new rom without recalculating the checksum afterwards, the checksum verification will fail and you won't be able to boot, essentially bricking the device.
FloatingFatMan said:
"itsmagic" is needed to recalculate the ROM checksum for the encrypted bootloader, which is verified every time you boot. Either you need to execute it (and Thors DOES do that, just read the install instructions for his 1.6 V2 recovery), or you need to incorporate its code into your recovery.
If you flash a new rom without recalculating the checksum afterwards, the checksum verification will fail and you won't be able to boot, essentially bricking the device.
Click to expand...
Click to collapse
If you manually install thors kernels then yes you do use itsmagic. But his flash script does not use it nor is it included in the flash zip either. I ensure you it will be tested thoroughly before its release. I have flashed virtuous galaxy with it and it booted fine.
Sent from my Sensation Rockin MIUI 1.12.16!
Welcome to the Nexus 7 Help Thread
This thread is here to help our community out as best as it can.
Why is this thread here?
There's 2 main reasons really. The first reason is to stop the development threads getting filled with questions which have nothing to do with the thread they're posted in. That then makes the thread go off-topic which is not what a development thread is there for.
The second reason is because there are too many repetitive questions being asked. The main problem with that is the fact that other users will sometimes attack the OP and 'flaming' them.
The main way which this thread will help to stop that happening is by helping you out as much as possible, while being in a friendly environment.
Below you will find the Thread Rules which I expect you all to follow and not to break them.
Thread Rules
1. Remember that while posting in this thread and across the whole site, you must not break the Forum Rules.
2. Even though this thread is for everyone to use, there'll be a lot if new members in here so no flaming or insulting anyone else.
3. As this is a help thread, remember that there is no such thing as a stupid question.
4. Even if you get your question answered by reading the 2nd it 3rd post, be sure to come back here and read some more. It will help you to learn even more.
Hall Of Fame
As I'll be keeping an eye on this thread quite a lot, I'll be adding the people to this list who have been the most helpful and are contributing the most.
1.markj338
2.
3.
4.
5.
Nexus 7 Moderators
If you report any posts, the report will go to our SM (Senior Moderator) and FSMs (Forum Specific Moderators). They are our SM - zelendel and our FSMs - Shreyas Jani, chrisd1a1, GODZSON, Divine_Madcat, babijoee and Moscow Desire. If you have any questions about this forum in particular then feel free to drop them a PM.
In post 2 there will be some really useful links so be sure to check them out.
In post 3 there'll be an FAQ which will help you out aswell
Useful Information & Links To Help You
XDA In General
First of all, I'm linking to some general XDA threads which can help you become more familiar with this site and how things run. I feel this is one thing which new users don't realize because they think it's okay to come to this site and post anywhere.
If you don't feel this applies to you, please move onto the Nexus 7 links further down this post.
XDA New User Guide - I can't stress enough how important that thread is. If you follow what that guide says, you'll be well on your way to becoming an asset to the XDA forums.
[HOW TO] Make A Substantial Thread, Post, Question & Poll - This is also a must read thread. Why, you ask? Well it's simple. Reading this will show you the best way to post your thread to ensure that people will respond and be able to help you. Rather than just giving no information or a thread title called "Mah phone brikked. Hlp me plzzz!", following that thread will give you the best chance of being helped.
[HOW TO] Make A Good Signature - This really is needed because as you'll see in a lot of signatures, mine included, is that we list our current devices and what ROM/kernel we are using. This helps people to help us. Take a look at the thread to find out what else to include in your signature.
Nexus 7 Helpful Links
I'll have these threads numbered so if you ask a question and it can be answered by looking at the first thread here, I'll say "Go to post 2 > nexus 7 > thread 1"
1. READ THIS FIRST - Nexus 7 General Section
2. [GUIDE] Flashing a factory image with fastboot/ returning to stock
3. N7 kernel test results (Performance & Battery tests)
4. Nexus 7 All-In-One Development Index
5. [Index]- 28 Jan 2013 - All for NEXUS 7 - "Nakasig/Tilapia" - (GSM/HSPA+)
6. NEXUS 7 3G-"nakasig"-For all Your Jelly Bean Discussions, Problems and Solutions
More will be added at a later date
[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]ASUS GOOGLE NEXUS 7 – GROUPER & TILAPIA (WiFi & 3G)[/SIZE]
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
[SIZE=+1]Q1: Do I need a toolkit to root this bad boy?....?[/SIZE]
Its a Nexus, imo if you need a toolkit you're either not experienced enough for rooting or too lazy Toolkits are out there and they are really straight forward, but you should get to know how to use fastboot/adb in case you need it. If you don't know what you're doing, you shouldn't be mucking around with your $200+ toy in case you screw something up and don't know how to use ADB or fastboot to restore it
[SIZE=+1]Q2: I'm thinking of getting this device/I'm new to this device. What are the main problems i should look out for? [/SIZE]
Look through the following threads - Nexus 7 defects? - List of known faults.
[SIZE=+1]Q3: Which ROM/kernel/recovery etc. would be the best choice for me? [/SIZE]
No-one can answer this for you. We all have our favorites, so just test different ones out and see which you prefer.
[SIZE=+1]Q4: When I flash my first custom ROM, how come I get stuck in a bootloop? [/SIZE]
While it's recommended that you always do a full wipe before installing, you HAVE to do a full wipe before installing your first ROM. If you don't, you N7 will not boot up.
[SIZE=+1]Q5: I flashed a new kernel and when I change frequencies, it reverts to stock settings 1.3GHz after a while. WHY??? [/SIZE]
You need a patched PowerHAL. On a very basic level, after a while the stock google PowerHAL likes to revert a lot of settings to stock. This includes the CPU clock speeds, etc. I got my PowerHAL from here
http://imoseyon.host4droid.com/grouper/beta/
And I flashed the nofreq one. It will NOT change your frequency, ever. After you flash the PowerHAL, use your favourite app (I like tricksterMOD, but support your devs by buying their apps) to set your kernel settings, and set them on boot. This is the easiest way to get settings to stick.
OR
You could use an init.d script to set a maximum clock speed. This way, you will need a kernel/ROM that supports boot.img.
http://forum.xda-developers.com/showpost.php?p=35493253&postcount=1366
This is a lot more difficult but it works
[SIZE=+1]Q6: How much overclocking is too much? Am I damaging my device? [/SIZE]
No chips are created equally. Some can take more OC than others. It is fact that too much OC can shorten the life of your CPU. A general rule I have seen used a lot is to not go around 20-30% over the stock speed. That is around 1.5GHz which most kernels get up to. However, a lot of devices can take more and will go higher. See for yourself, just don't be stupid
[SIZE=+1]Q7: What is the difference between x and y kernel governors/schedulers? [/SIZE]
See here: [GUIDE]Kernel Governors and I/O SCHEDULERS
[REF][TWEAKS] Kernel Governors, Modules, I/O Schedulers, CPU Tweaks, AIO App Configs
[SIZE=+1]Q8: I tried to boot my device into recovery from the bootloader and now it is stuck on the google screen. Is it bricked? [/SIZE]
No. Probably not. Chances are you're on an old bootloader, which has a bug that doesn't allow you to get into recovery from the BL without being connected to a computer. So, connect it to your computer, hold vol down/power for 10 secs to go back to the bootloader. You can go to the recovery from there.
[SIZE=+1]Q9: On my HTC (whatever) I could transfer files onto my sdcard while in recovery. How do I do it on the N7? [/SIZE]
You can't drag/drop in recovery between your N7 and a PC. Either boot into android and transfer your files, or use ADB while in recovery.
"adb push nameoffile /data/media" or wherever your things are (beware of how many 0's there are on your sdcard).
[SIZE=+1]Q10: My files on my "sdcard" appear under /data/media/0/0/0/0/0/0/0/0/0/0/0/0/0. WHY so many 0's?? [/SIZE]
Ask Google. It’s got to do with the multiuser feature brought to android in 4.2. Ever user has their own folder, so you might have /0 and /1. If you're having troubles with it in recovery, I would update to the latest TWRP.
[SIZE=+1]Q11: I’m trying to update my stock rooted modded N7 to 4.2 from 4.1.2 but it won't work. Help? [/SIZE]
You need to be running completely stock to update. So, you need to either flash a stock ROM or the stock image.
[SIZE=+1]Q12: When I finish watching a video the screen goes weird. Its like, washed out or something. Is my device bricked? Is my screen bricked? [/SIZE]
No. Its the tegra smartdimmer. When your device is playing a video, the Tegra 3 automatically bumps up the contrast and dims the backlight, to save battery. This is a feature. To turn it off, either use a script or tricksterMOD (which is much easier).
[SIZE=+1]Q13: Battery life on this kernel/ROM sux. I've been using it for half an hour and its dropped 30% already. Why? Restoring to my old kernel..[/SIZE]
When you flash a new ROM/kernel, you need to give it a few battery cycles before battery is reported accurately. So, flash the new kernel, drain it (not necessarily to 0%), charge it fully, drain it again, charge, then play around. Do not complain about battery or anything without doing a few cycles first.
[SIZE=+1]Q14: I am about to flash another ROM. Do I have to full wipe or can I flash it on top? (Dirty flash).[/SIZE]
Usually you can probably dirty flash. But if it causes problems, don't report them. Best thing to do is to reflash the ROM with a full wipe and see if bugs persist. I always wipe when changing to a different ROM, but when updating a ROM i don't wipe usually.
[SIZE=+1]Q15: Should I unlock the bootloader when I get the tablet if I am going to root it anyway?.[/SIZE]
I would say no. Because, if there is a problem you have sort of voided your warranty. I like to keep my devices for a month without rooting/unlocking them in case there is a fault or something. You should do the same, I’d hate to have a brand new device, root it and then find a fault and have voided your warranty. Companies can be sneaky and can probably try to avoid fixing your device under warranty if you tamper with it. However you could always relock and revert to stock, but it is much easier to be patient and make sure there are no problems
[SIZE=+1]Q16: Will rooting my tablet make it faster/awesomer and have improve battery life?[/SIZE]
Short answer: no.
Long answer: nope.
Rooting alone will not change anything relateds to battery or performance. However custom ROMs, kernels and other mods will change things. For example flashing a more optimised kernel might improve performance, especially if you overclock it. Similarly, underclocking generally improves battery life. Of course it depends on what crap you have on your device too, but that's the general idea. Usually in the OP of a ROM/kernel thread, and in the comments you can get a good idea on whether it is optimized for battery, performance or a combination.
[SIZE=+1]Q17: What’s difference between N7 “Grouper – Nakasi” and N7 3G “Tilapia – Nakasig”?.[/SIZE]
Wi-Fi (all models) = Nakasi - Grouper
3G/Wi-Fi = Nakasig - Tilapia
The Nakasi/Nakasig is the image (operating system)
and
the Grouper/Tilapia is the hardware build.
Because one of the files for the phone call apk is named "tilapia"
assert(getprop("ro.product.device") == "tilapia"
getprop("ro.build.product") == "tilapia".
[SIZE=+1]Q18: Can I use same recovery for N7 “Grouper” and N7 3G “Tilapia”? [/SIZE]
Yes, but it is preferable to use a special recovery for the tilapia. You will find 3 special recoveries for Tilapia.
[SIZE=+1]Q19: What's the difference between "Development" and "Original Development"?[/SIZE]
Here are the rough guidelines as to what should be placed in "Original Development":
*Official release of highly original and upstream custom ROMs (built from the ground up with significant original development within them).
*Official releases/development of such original ROMs, perhaps posted by the maintainer or their nominated person.
*A significant "first" in development for a device. This is something which took considerable time/effort and is generally accepted by developers to be non-trivial.
*Kernels which are built with beneficial changes that are not simply pulled from other kernels already available.
*Tools and utilities with a clear purpose, and which are well-made, and useful to users. They should have an element of originality, either in purpose or through significant improvement in the means of operation.
*Significant port of a ROM from one device to another, giving enhanced features or functionality to the users of the target device.
All other development work goes into "Android Development".
*
[INDEX]All In One Nexus 7 Index Thread (WiFi)
[Index]All for NEXUS 7 - "Nakasig/Tilapia" - (3G/GSM/HSPA+)
[GUIDE][BOOTLOADER][4.2.2] TILAPIA JDQ39 - 4.18 Flash Image Instructions (FOR 3G VERSION)
*Use the thanks button if someone helps you or answers your question*
*Read the sticked threads*
*Google probably knows the answer to your question*
<> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <> <>
Forum Rules | New Users Guide | XDA Tour | Report Posts
This FAQ is part of a Recognized Contributor Group Initiative. Please look for a similar FAQ thread when visiting another device forum.
A special thanks to those who contributed to the production of this FAQ, especially kinfauns, kidcarter93, philos64, ronnie498, fellow RC's, me
Good thread, make it a sticky !
At least good helpers will be honoured ^_^ !
Since this thread is for newbie I want to ask , can i use franco kernel on N7 3G 32GB?
nazz.rule said:
Since this thread is for newbie I want to ask , can i use franco kernel on N7 3G 32GB?
Click to expand...
Click to collapse
There is a difference in being new and being spoon fed. You will find your answer in the Franco kernel thread.
Cheers Danny
nazz.rule said:
Since this thread is for newbie I want to ask , can i use franco kernel on N7 3G 32GB?
Click to expand...
Click to collapse
Yes you can
Sent from my Nexus 7 using Tapatalk HD
Thanks to Moscow Desire, this thread is now stickied so hopefully it will be able to help as many people as possible
Sent from my Nexus 7 using xda premium
I got my nexus 7 yesterday and updated it immediately to 4.2.1. All good so far. I start using and all goes well until I remember "this thing has the swipe keyboard, right?". I start swiping and nothing happens. Check the settings, it is on. Boot the device, no effect. Enable and disable the thing and boot the tablet a few times more, still no go.
At this point I decided I'll fix that later and made another user account for my GF to use. I immediately notice that the swipe typing works on that account just fine. I check the settings and looks like it's on by default. I go back to my own profile and check the settings again, but still no go.
Any ideas?
badmoj0 said:
I got my nexus 7 yesterday and updated it immediately to 4.2.1. All good so far. I start using and all goes well until I remember "this thing has the swipe keyboard, right?". I start swiping and nothing happens. Check the settings, it is on. Boot the device, no effect. Enable and disable the thing and boot the tablet a few times more, still no go.
At this point I decided I'll fix that later and made another user account for my GF to use. I immediately notice that the swipe typing works on that account just fine. I check the settings and looks like it's on by default. I go back to my own profile and check the settings again, but still no go.
Any ideas?
Click to expand...
Click to collapse
Its definitely checked on your account?
Try this one as a quick workaround
http://forum.xda-developers.com/showthread.php?p=35596988
Sent with swag from my Kanged Nexus 7
Thanks for the tip. I tried that, but settings crashes every time I try to enable the PC layout keyboard.
I'm gonna do a factory wipe since the tablet is still almost on default anyway.
edit: Ok did reset and everything works just fine now. Now just wait for play store to install all the apps back
I have just got my new Nexus 7 and I want to root my N7 with Wug's root toolkit. I was thinking if I just don't check the box: flash custom recovery. Can I then just do the OTA updates? Because I don't want to install a Custom Rom.
Hi guys!
Just got a stock unrooted unmodded N7 32GB with build JZO54K. On first boot it found the OTA update to 4.2.1 so I happily accepted the update. A few minutes into the upgrade process I get the "dead" droid with the triangle, guess something went wrong. It boots up again into JZO54K and works fine.
I can force another attempt at the update by stopping and clearing the data for Google Services Framework and searching for updates again, but with the same results.
Am I missing something? Would like to try pure AOSP before going CM on this little beauty
How to root Nexus 7 without toolkit?
Root Nexus 7 must flash the CWM or other recoveries? In the menu of "Google Nexus 7 TOOLKIT V4.0.0", I found the button "Root" and the check "and flash recovery...". Does it mean I can root the machine without flash any recovery? Thanks.
AngryGamer025 said:
I have just got my new Nexus 7 and I want to root my N7 with Wug's root toolkit. I was thinking if I just don't check the box: flash custom recovery. Can I then just do the OTA updates? Because I don't want to install a Custom Rom.
Click to expand...
Click to collapse
If you've only rooted you can do ota's. Just as long as you don't change ANYTHING in the /system partition like installing flashable zips
frdd said:
Hi guys!
Just got a stock unrooted unmodded N7 32GB with build JZO54K. On first boot it found the OTA update to 4.2.1 so I happily accepted the update. A few minutes into the upgrade process I get the "dead" droid with the triangle, guess something went wrong. It boots up again into JZO54K and works fine.
I can force another attempt at the update by stopping and clearing the data for Google Services Framework and searching for updates again, but with the same results.
Am I missing something? Would like to try pure AOSP before going CM on this little beauty
Click to expand...
Click to collapse
Sure its completely stock? If it is, it should work... If you be got any more troubles ask Google
If you want pure AOSP there are ROMs for that you can flash, if you root
tmbu said:
Root Nexus 7 must flash the CWM or other recoveries? In the menu of "Google Nexus 7 TOOLKIT V4.0.0", I found the button "Root" and the check "and flash recovery...". Does it mean I can root the machine without flash any recovery? Thanks.
Click to expand...
Click to collapse
You can root by having all the right superuser binaries etc
But its easier to flash the recovery, and then flash the latest superuser/ supersu zip.
Sent with from my Asus Nexus Unicorn
markj338 said:
You can root by having all the right superuser binaries etc
But its easier to flash the recovery, and then flash the latest superuser/ supersu zip.
Sent with from my Asus Nexus Unicorn
Click to expand...
Click to collapse
Thank you for reply. I can understand your second sentence, but I can't understand the first one. Can you say something more? I just want to root the machine without any toolkit and recovery.
tmbu said:
Thank you for reply. I can understand your second sentence, but I can't understand the first one. Can you say something more? I just want to root the machine without any toolkit and recovery.
Click to expand...
Click to collapse
I would recommend flashing the recovery in order to get everything working properly, and to easily recover if something goes wrong
I was wondering whether it's possible to share files between the different users of the same N7? For instance to make video or music files available regardless of who is logged in.
I don't seem to be able to find anyone even discussing this anywhere at all.
Sent from my Nexus 7 using xda app-developers app
opticon78 said:
I was wondering whether it's possible to share files between the different users of the same N7? For instance to make video or music files available regardless of who is logged in.
I don't seem to be able to find anyone even discussing this anywhere at all.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The closest option to that is Multi-User App Share. It doesn't have the ability to share files though. Maybe the creator will make it possible in a future update though
Sent from my Nexus 7 using xda premium
I have seen it in the play store, but I'm not sure how that would make sharing files within the tablet possible, and since it requires rooting I can't even try it unfortunately.
Sent from my Nexus 7 using xda app-developers app