Related
Hey guys - I'm new to this forum, but I figure if anyone can help me, someone here can.
So, my bro got ahold of my phone and rooted it and installed Axura 2.2.5.9.
Since there is a newer version, I would like to throw it on and work out a few glitches and get whatever tweaks were put there.
So, how do I go about updating this thing? If anyone has the time or the patience, I would love to hear this in layman's terms.
Like:
Step 1 - download 'this file'
Step 2 - Plug phone in and drag/drop to 'folder x' on 'internal/external sd'
Etc. I came from an iPhone and all the lingo is different - like jailbreaking vs rooting. And saying "flash" instead of "load" or ROM instead of OS.
I would just like to update, but I'd liek to not be confused by all the different slang.
Thanks, anyone, for putting your 2 cents in to help a brother out.
this thread:
http://forum.xda-developers.com/showthread.php?t=849028
will answer all your questions
After you read the noob guide, feel free to PM me if you need clarification... I would also be curious to know if you think it could be improved. I wrote it trying to cater to the noob.
Just install download the rom you want on the sd (internal memory, dont save it in any folder) then boot into recovery (you should be able to do so by simply holding the power button for a second) now choose install zip from sd or sth like that and pick the rom file. The end.
Sent from my JPJPM V2 powered SGH-T959 using XDA App
full instructions easily available on the d4a site
click the link in my sig go down to vibrant section > roms> read the op
Its exactly like flashing any other rom, only difference being that you have an axuraXXXX.zip instead of ANYOTHERROM.zip
Cheers.
Just remember to backup your apps, since the new rom will wipe your phone.
To be safe, you may want to make a nandroid backup in CWR... always nice to have something to fall back on.
The guide has more detail like these steps, but yes, everyone is right in saying just download it and flash it. I think it's important to backup everything.
The Noob Guide is really well written. My problem now is I cant find the file to download!
A Rom you mean? You can find those in the development forum along with other tools you may need to run/flash it.
Here's a link just in case you don't know where that is
http://forum.xda-developers.com/forumdisplay.php?f=711
Yes, the ROM. I went to the daily bible thread and tried to click "Download" on the Axura subsection. It gave me an "Error 404 - file not found".
Just open one of the threads in the form link I just gave you and look for the ROM you wanted, then check the first post there for the download link.
I did that. That's when I get the Error 404.
http://forum.xda-developers.com/showthread.php?t=949372
They must have pulled that rom of the server or the host did that. Just go for another one, plenty of options out there and quite frankly Axura isn't exactly the most sought after roms around here.
Axura is truly in need of a 2.2.1 update, but seeing as though Master is happy with his Nexus, it will never be getting one. And quite frankly, Eugene's gingerclone roms, trigger, or any of the i9000 ports run much smoother to me.
Ding forget he has also gotten a thunderbolt, I thought about picking up dev on axura but I have no where near enough time to mess with it, but I agree axura is in dire need of an update to 2.2.1
This post Trigger'd by my Vibrant
THANKS GUYS
I just got Trigger and so far so good.
My only issue is that I couldnt figure out how to restore my apps in Ti. Looked like there were 0 files backed up. Oh well. One at a time.
Please suggest any changes, additions etc
Please don't try to hold me responsible if following anything here makes your phone die. Pretty please!
I have been looking through the forums, rom threads etc, and have seen a lot of questions cropping up again and again. Therefore I decided to start this project!
Basically I hope this will become a reference for newbies to get themselves accustomed to android and the galaxy s II! I will try to update it regularly with information about ROMS, Flashing and general android/samsung terminology.
If you think that I have given a wrong definition or think that anything needs clarifying more please tell me! Also, if you think that I should add anything then feel free to suggest.
Here we go...
Contents
1. Rooting
- Rooting your phone
2. Kernels
- Eplanation
- Links
3. Odin
- Guide to using Odin
4. Custom ROMs
- Risk
- Benefits
- AOSP ROMs
5. ClockWorkMod
- Explanation
- How to Backup/NANDroid
- How to Restore
- How to install a ROM using CWM
6. /efs
- What it is
- How to back it up
7. List of Custom ROMs
8. The Forums
9. Glossary
10. To Do list
RootingRooting is the process of getting 'root access'. In a nutshell this means that you can edit the system partition of your phone. The best analogy of this I can think of is if you imagine a tree! The tree you see above the ground is what you can edit on your phone normally, for example you can add music files, edit text files, etc etc. The 'roots' of the tree are the android system files themselves, they are unseen and are not usually meant to be messed with. It can also be seen as the equivelant of having administrator privilages in windows - with them you have better access to your computer.
Rooting voids your warranty! But you can un-root your phone by flashing a 'stock' ROM and Kernel.
Gaining root access however allows us to customise our phones even further, for example you can:
Edit files to create themes
Backup usefull system files
Remove bloatware and unwanted apps
Rooting the Galaxy S IIRooting the Galaxy S II is, thankfully, easy! Unlike certain other phone manufacturers *cough* HTC *cough* samsung haven't imposed any unnecessary locks on the phone, and so we dont have to hack our phones to pices to be able to root them.
Several guides already exist in the development forum on how to root you phone - it involves a custom kernel:
http://forum.xda-developers.com/showthread.php?t=1103399 (by Chainfire)
Or, here is the Noobs Guide:
http://forum.xda-developers.com/showthread.php?t=1126522 (capaxdoli)
And an extremely detailed thread from wibbsy:
http://forum.xda-developers.com/showthread.php?t=1246131 (wibbsy)
Superuser and BusyboxSuperuser is an app that is present on pretty much all custom ROMs. It allows you to manage 'superuser' rights for your phone, in other words which apps you want to allow to have root access. If you dont have it on your custom ROM then you would want to download it from the market (free). Once you have it downloaded you dont need to do anything! It will warn you when an app wants root access, and ask you to allow once, allow all the time, or never allow. It can also be seen as a firewall for your phone, you can deny access to the root of your system files to apps you dont think should be down there!
Busybox is basically a set of commands that aren't built into android to begin with, but are part of Unix (which android is based on). They add additional functionality for root application to perform their job! To be honest this is all I know about busybox, but it is very useful, and lots of root apps need it, so download it!
KernelsThis brings me along nicely to Kernels! Kernels are basically a bridge between your apps and your hardware. It controls everything that apps send to the processor, and everything the processor sends back.
This, as you can imagine, makes kernels VERY important. On XDA, you might see a kernel posted in the development forums. The are usually identified as [Kernel] in the thread title. You will probably also see more brackets in the title, these identify what modules the developer has added to the kernel, or what features it includes. For example [OC/UV 1.5GHZ]. This means that the kernel will enable the phone to be overlcoked to 1.5GHz, but also means the processor is undervolted (meaning it draws less power from the battery).
For more details look here:
http://forum.xda-developers.com/showthread.php?t=894880 (mroneeyedboh)
And here for more details on 'govenors':
http://forum.xda-developers.com/showthread.php?t=843406 (RJackson)
OdinOdin is a piece of software that allows us to flash anything we want to the phone. The file is attached to the bottom of this post.
It is perfectly safe IF USED CORRECTLY!
This is a general guide for using Odin, take a look at this picture (thanks to screamworks):
To get Odin to connect to your phone, you need to boot into 'download mode' by pressing volume down, home, and power keys at the same time, and connect your phone to your PC via USB.
Everything in red:
NEVER TOUCH
NEVER TOUCH
NEVER TOUCH
NEVER TOUCH
It's that simple! I would be more specific but most Roms, Kernels and CSCs have methods on their respective threads for using Odin with their ROM, so it best to look there.
Wait... (I hear you say...)
Why bother flashing a custom ROM if there is a risk of damaging your phone? Well, they usually come with the following benefits:
- Deodexed, basically allows deeper theming of applications
- Zipaligned, reduce the amount of RAM used when running an application
- Optimisations, meaning that the developer has tweaked the roms system files for bettery speed, battery life and stability
- Quicker Updates, Rom developers will more often then not update their rom to fix bugs FAR quicker then samsung ever will
- Additions, Developers also like to add their own additions to their ROMs, such as themes and applications
The benefits far outweigh the risk!
AOSPAOSP (Android Open Source Project) ROMs are built from the original android source. They are essentially a 'clean' version of android without any additions from manufacturers (e.g no Touchwiz, Sense, MotoBlur etc...). They are popular mainly because they are so customisable. Here is a list of the three main AOSP build you will find:
'Pure' AOSP
This is a build straight from Google's sources and does not contain any modifications whatsoever, other then those that make it run on the particular device. Here is the AOSP project website for more information:
http://source.android.com/
CyanogenMod
This is an extremely popular AOSP build that provides endless customisation to the user. The builds are fast, stable and reliable, and nearly every android device has a cyanogen mod ROM built for it. It is also popular for its 'nightly' (literally) updates. More information can be found on the Cyanogen website here:
http://www.cyanogenmod.com/
MIUI
MIUI is a chinese rom that has been heavily customised, and is influenced by iOS. Think what would happen if an android phone and an iPhone had a baby... Despite commiting the henious crime of trying to be an iPhone, it does work. MIUI Roms are essentially all about speed and looks, if that is what you are after! Here is the MIUI website for further information:
http://www.miuiandroid.com/
ClockWorkMod (CWM)
Clockworkmod is a 'custom recovery' made by xda member koush. Every phone had a recovery partition designed so that if the user messes up a ROM installation, they can recover their phone. CWM is a modified recovery installed into the recovery partition that allows advanced control over ROM recovery, installation and much more.
Features of CWM include:
- NANDroid Backup, This allows you to completely back up your existing ROM with all its files, data and apps
- Restore Backup, Restores a previous backup (obviously...)
- ROM installation, Allows you to install a ROM contained inside a flashable .zip file
- Wipe data/Factory reset, completely erases all of your data contacts, apps etc, leaving your phone 'as new'
Amongst others...
How to install CWMIf you have already rooted your phone using the CF-root Kernel, then you already have CWM! If not, then just install the kernel linked to above in the 'how to root your phone' section
How to make a NANDroid backup using CWMBackups are important because they allow you to restore your ROM incase flashing goes wrong, or you phone starts playing up and displaying wierd bugs.
To make a backup, you need to boot into CWM recovery (done through the 'cwm' app installed onto your phone when you flash the cf-root kernel). Then, you need to navigate down to 'backup/restore' using the volume keys, and select it using the home key. From here, just click 'backup' and you are all set! Leave your phone make the backup (its takes some time) and then just reboot when it tells you its finished. To restore your backup, do the same but instead of clicking backup, click 'restore' instead. Choose which backup you would like to restore and leave the phone to do its magic. Done.
How to install a ROM using CWMInstalling a ROM using CWM is a lot less hassle then installing via Odin. The ROM developer will specify which method of installing their ROM you can use, but it is usually done by a CWM flashable .zip.
To flash:
1. Boot into CWM as described above
2. Navigate to 'install zip from sd card'
3. Select it, and then navigate to 'install zip from sdcard' again!
4. Select the ROM you downloaded from your sd card
5. Navigate down to yes
6. Let CWM install you new ROM!
Note: The same process applies for flashing a kernel
The /efs folderThe /efs folder is a folder in your phone that contains information specific to YOUR phone, for example your IMEI number, product number, Wireless MAC addresses, and much more. There have been reports of people messing up their /efs folder when unlocking their phone or flashing new ROMs, here is an example from the Nexus S development forum (jump to page 111 to see everyone start to panic):
http://forum.xda-developers.com/showthread.php?t=1034130
Therefore, it is important to make a backup! Instead of just regurgitating guides on the forums already, here is a link to a very good one by Rawat:
http://forum.xda-developers.com/showthread.php?t=1068193 (Rawat)
The easiest way of doing it is by using terminal emulator rather then ADB (unless you have ADB all up and running and are confident with it)
Thank you to Godutch for suggesting this, I was never actually aware of it!
ADBADB stands for Android Debug Bridge, and is a useful tool for your device. It has many funtions including:
- Pushing .apks to your phone
- Pushing files to your phone to specific locations
- Rebooting to download and recovery
And I haven't even scratched the surface! It does a lot more trust me...
You will see guides on this forum saying 'this guide assumes you have ADB set up', which you definitely should do! However, there is a downside - it can be horifficaly complicated and fustrating to install for a newcomer to android, you have to mess around with SDKs, EXEs, Drivers, Paths, Yawwnnn....
So I'm going to let an expert describe how to do it! Here's the hard (but proper) way:
http://forum.xda-developers.com/showthread.php?t=879701 (Captainkrtek and Adrynalyne)
And here's the easy way, all nicely pacaged up for you:
http://forum.xda-developers.com/showthread.php?t=502010 (VanillaTbone)
I would write a short explanation of ADB installation for you here but it would just confuse you, so im gonna let other people do the work!
Custom Rom List
Well, Swi7chblade has done a far better job at doing a custom Rom list then me so I will give you a link to his instead
http://forum.xda-developers.com/showthread.php?t=1253665 (Swi7chblade)
Stock ROMs
Intratech has a collection of stock ROMs, Kernels and Radios all compressed up nicely for you. Link is here:
http://forum.xda-developers.com/showthread.php?t=1075278
Why stock I hear you say? Flashing back a 'stock' ROM usually helps fix random issues you might get whilst switching ROMs, like bootloops. Also, some people prefer the stock experience!
The Forums
Well, I'm not going to patronise you by telling you how to be nice to people etc, but there is often a lot of confusion with regards to the forum rules:
http://forum.xda-developers.com/announcement.php?a=81 (MikeChannon)
I often see moderators with dangerously high blood pressure stressing the following points in particular:
- Use the search button
- Post in the right forums
- Use the search button
- Don't spam/ Flame
- Use the search button
- No ETAs
- Use the search button
If you have owned a device that is supported by XDA before, or have had a look at other device forums, you may of noticed that the development forums for the GSII are slightly different. They are split into two sections:
- Original Android Development
- Android Development
This is an experiment being done by the moderators of the forum that (regardless of my own opinion) is meant to distinguish between 'original' Roms and 'derivative' Roms. For instance; cyanogenmod is a rom built from AOSP source and has been actively developed with added applications, improvements to code etc etc. It is therefore classified as 'original' and placed into the 'original android development' sub-forum. Roms that either use another Rom as a base or do not have any 'original' components are deemed 'derivative' and are placed into the 'android development' forum. Despite this, I urge you to look in both forums! The both have excellent Roms and just because some are deemed 'original' this does not mean they are superior to those that are not. There is great development going on in both forums
Useful Links
CF-ROOT and CWM: http://forum.xda-developers.com/showthread.php?t=1103399
Galaxy S II FAQ:http://forum.xda-developers.com/showthread.php?t=1065995
Korean Galaxy S II Thread: http://forum.xda-developers.com/showthread.php?t=1097347
Android Terminology (from the CM Wiki): http://wiki.cyanogenmod.com/index.php?title=Terminology
Glossary:
Flash - Put new firmware onto your phone
Firmware - A piece of software
OC - Overclock (the processor)
UC - Underclock (the processor)
Odin - Used to flash new ROMs to yor phone
ROM - a piece of firmware, usually modified by a developer
CWM - ClockWorkMod recovery, a very useful tool used to falsh new roms, kernels etc
Nandroid - A method of backing up your existing 'Rom' with all its apps, data, contacts etc. Done through CWM
.apk - The file type that android apps are contained in. To install just click on it!
AOSP - A ROM built from the original google android source, not a customised version of a manufacturers ROM
CyanogenMod - A very popular, customised, AOSP Rom
TO DO
- CWM
- Finish glossary
- ADB
- Additions to rooting section (superuser, busybox etc)
- How to do a backup via CWM
- Expand ODIN section
- Link to stock ROM list
- Create a 'Custom ROM' list with links to all current custom roms
- Explanation of AOSP (including CM, MIUI)
- Forum etiquette
- Useful links
- Backing up the /efs folder
- Custom boot animations
Nice guide, a few remarks:
root in unix terminology is the same as administrator in window, so rooting a phone means you are getting administrative powers, also rooting your phone voids warranty
maybe some other things could be included: the jig, BACKING UP /efs(this should be the most prominent caption) and adb (+adb frontends like qtadb)
nice post
great for learners like me
godutch said:
Nice guide, a few remarks:
root in unix terminology is the same as administrator in window, so rooting a phone means you are getting administrative powers, also rooting your phone voids warranty
maybe some other things could be included: the jig, BACKING UP /efs(this should be the most prominent caption) and adb (+adb frontends like qtadb)
Click to expand...
Click to collapse
Ok thanks for the hints, i will adjust the rooting section accordingly. I'm also going to add a to do list... right now...
Don't forget the /efs directory, if it gets messed up (and sometimes it does) you will loose your phone and data connection permanently and you end up with an expensive Galaxy S mediaplayer. There is no known way to retrieve it and it does get messed up flashing custom roms (many nexus s users now have, well an expensive mediaplayer after flashing a certain rom)
godutch said:
Don't forget the /efs directory, if it gets messed up (and sometimes it does) you will loose your phone and data connection permanently and you end up with an expensive Galaxy S mediaplayer. There is no known way to retrieve it and it does get messed up flashing custom roms (many nexus s users now have, well an expensive mediaplayer after flashing a certain rom)
Click to expand...
Click to collapse
Would you be ever so kind as to write me a definition to add? I'm not going to lie I had never heard of this probelm but it does sound important
willk22 said:
Would you be ever so kind as to write me a definition to add? I'm not going to lie I had never heard of this probelm but it does sound important
Click to expand...
Click to collapse
you can find a guide here: http://forum.xda-developers.com/showthread.php?t=1068193 I didn't write it, I did read about the problems about what could happen if you screw the /efs directory here: http://forum.xda-developers.com/showthread.php?p=12874457
How long before the post is ruined by idiots posting help questions in it .
Is their a way to lock it so as not to detract fro0m a very good stickie .
Just look at the FAQ page totally devoid now of being a FAQ .
Backing up EFS see topic Dev in section .
jje
JJEgan said:
How long before the post is ruined by idiots posting help questions in it .
Is their a way to lock it so as not to detract fro0m a very good stickie .
Just look at the FAQ page totally devoid now of being a FAQ .
Backing up EFS see topic Dev in section .
jje
Click to expand...
Click to collapse
In the desire dev section there is a reference thread, new suggestions are posted and once in a while the thread is cleaned: all the suggestions are added to the OP and then together with useless posts deleted....
JJEgan said:
How long before the post is ruined by idiots posting help questions in it .
Is their a way to lock it so as not to detract fro0m a very good stickie .
Just look at the FAQ page totally devoid now of being a FAQ .
Backing up EFS see topic Dev in section .
jje
Click to expand...
Click to collapse
Well I guess that is something that mabye a moderator can do? It would be a dillema though because I really would like suggestions from the community on how to improve the guide and add suggestions and amendmants... but you are right!
godutch said:
you can find a guide here: http://forum.xda-developers.com/showthread.php?t=1068193 I didn't write it, I did read about the problems about what could happen if you screw the /efs directory here: http://forum.xda-developers.com/showthread.php?p=12874457
Click to expand...
Click to collapse
Thank you, I will add this tommorow!
I've never seen definite evidence that having root voids warrantee.Looking through all the documents it only says things like if you change the software and this causes the problem they won't fix it. I suspect they would still fix a hardware fault. Samsung have given phones to known hackers. It would seem hard for them to argue that rooting invalidates warrantee when they have encouraged it.
Sent from my GT-I9100 using XDA App
drspikes said:
I've never seen definite evidence that having root voids warrantee.Looking through all the documents it only says things like if you change the software and this causes the problem they won't fix it. I suspect they would still fix a hardware fault. Samsung have given phones to known hackers. It would seem hard for them to argue that rooting invalidates warrantee when they have encouraged it.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Better safe then sorry!
Plus phones can easily be unrooted.
drspikes said:
I've never seen definite evidence that having root voids warrantee.Looking through all the documents it only says things like if you change the software and this causes the problem they won't fix it. I suspect they would still fix a hardware fault. Samsung have given phones to known hackers. It would seem hard for them to argue that rooting invalidates warrantee when they have encouraged it.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
It's true, I can't find the reference right now but a member called Kalua( he is an official samsung repair center) posted a part of the official service manual which says it voids warranty
http://gathering.tweakers.net/forum/list_category/13
it's very hard to retrieve/find indivual posts though
edit: found it: http://gathering.tweakers.net/forum/view_message/36107694
Could you explain the usb jig please. Isnt the binary clock reset when re rooting? In fact a whole how to re root your gs2 so samsung will never know guide would be great.
Sent from my GT-I9100 using XDA App
Thanks for this. It's very much appreciated by all noobs to Samsungs. I look forward to future updates
Sent from my GT-I9100 using XDA Premium App
santiago84 said:
Thanks for this. It's very much appreciated by all noobs to Samsungs. I look forward to future updates
Sent from my GT-I9100 using XDA Premium App
Click to expand...
Click to collapse
No problem! I will update everything and continue the 'to do' list as soon as i can...
Very good idea and think this will help a lot of people This will definitely be a good link to send those who are new to the device
drspikes said:
I've never seen definite evidence that having root voids warrantee.Looking through all the documents it only says things like if you change the software and this causes the problem they won't fix it. I suspect they would still fix a hardware fault. Samsung have given phones to known hackers. It would seem hard for them to argue that rooting invalidates warrantee when they have encouraged it.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
No Rooting letter from Samsung .
http://www.samfirmware.com/apps/blog/show/5267754-newsletter-by-samsung-electronics-
This looks really nice, and will be a good ref for many. I even found myself asking lots of these questions in many threads because I'm used to the HTC way of rooting.
A nice little section to add would be a "unroot your device" for people with warranty purposes. This is a question that pops up everywhere.
Keep up the good work!
Sent from my GT-I9100 using XDA Premium App
Hi everyone,
I'm new to this and sorry if some of my questions are redundant, but can anyone tell me their experiences with hacking the Nook Color? I'm still deciding on getting it and I want to put Cyanogenmod 7(Gingerbread) in it( if I buy one), but I'm not 100 percent sure. Can someone tell me if it's easy, hard, any complications, etc? Also any links or information on how to dual boot it( is that the one where it doesn't void your warranty?) would be greatly appreciated.
Sorry for all the noobness.
Welcome! There are a lot of threads here and in the Android Development sub-forum on getting started along with answers to most of your questions. See this post of mine for links on getting CM7 installed:
http://forum.xda-developers.com/showthread.php?p=16779145#post16779145
Frankly, everyone here will say that the nook is pretty awesome, especially with CM7. It's quite easy. The first time you install it might take a while (under 1 hour easy), but after a while it could really be done in a few minutes. At this point you just need to copy files mostly. Technically, I think running CM7 could void your warranty, but that said, the Nook is nearly unbrickable. You can pretty much always restore to stock if need be. The safest way to get started is to follow the SD card method from the link above.
Good luck!
It's just like learn how to swim or learn how to ride a bike.
No one ever able to do and do good first time, it takes time, always.
Someone picks things up fairly quick, some others learn at slower pace but they all get better at some points.
The only requirements are able to read and understand English and able to follow the instruction then you're off to go .......... and go far.
Lastly, if I can do it, you can do it.
Look into starting from the SDCard install options, before overwriting internal memory. If something goes wrong, you simply power off, remove the SDCard, and power up again, and you have your stock Nook Color working perfectly.
In my sig, click the link to "SD Install" for the best way to prep the MicroSD card for whatever ROM you want.
I highly recommend CM7, it's simply the best thing going for it. Again, installing to the MicroSD card is a painless way to test it out, links in verygreen's thread.
Make sure you have a SanDisk card, links in my sig to find out why if you're curious.
To this day, I still have my stock Nook Color B&N software updated and running on the internal memory - but for the life of me I can't figure out why I haven't taken the step to move CM7 to internal at this point. It's that good.
Point being, with a SanDisk MicroSD card, and CM7 installed to it, you really unlock the powerful user experience this device is capable of. Best part is, it's not a permanent thing. You simply power off, remove the MicroSD card, then power back up and you are back to stock.
Easy, painless, and tons of fun.
Thank You so much everyone for the responses. Sorry if I took too long to reply. I'm going to read over the directions right now Oh and do anyone have the list of some of the words? I'm still new to this and I don't know what "partition" or "kernel" means.
partition = dedicated space for specific usage.
kernel = sets of drivers, it is a brain of the ROM
i was a new nook owner and new to rooting as well. i had no trouble with following instructions and have been very happy with the outcome. it also helps to read a lot of other posts to see what issues may arise and how to fix things. as long as you can follow instructions properly its a breeze
Thank You all so much. I got one more question, I've been reading somewhere online that it's possible that you can go back to the original version of the nook without having to remove the SD card, and I just want to confirm if this is possible? If it's can you give me a link? Thank You sorry for so much question
Marid said:
Thank You all so much. I got one more question, I've been reading somewhere online that it's possible that you can go back to the original version of the nook without having to remove the SD card, and I just want to confirm if this is possible? If it's can you give me a link? Thank You sorry for so much question
Click to expand...
Click to collapse
On the newer nightlies, you can press the nook 'n' button while the first green cyanogenmod logo is showing and it will take you to a boot menu. You can then select to boot from emmc (internal) or the sd card, and also choose normal or recovery mode.
Sorry about this but 1 more small question, will bn update( i think ota) affect the rooted nook? If so, can you tell me how to fix it?
Hey guys,
I'm a new Nexus 7 user (Will be delivered today) and I'm just looking for some quick advice to get started.
I have had a good search/read of forum and found various rooting methods/kernels and some roms I will be trying out etc and shouldn't have any problem getting myself started, however to lower risk I'm just looking for some seasoned N7 users to maybe give me any recommendations or advice.
I'm not a n00b and dont expect/want any spoon feeding, Maybe just a few pointers to avoid any ****ups/bricks on N7/flashing techniques.
Advice/Links would be appreciated.
Easiest way you can possibly do it:
http://www.wugfresh.com/nrt/
Wilks3y said:
Easiest way you can possibly do it:
http://www.wugfresh.com/nrt/
Click to expand...
Click to collapse
Thnx, This was one of the apps I was looking at in my research so will give it a go.
I know you're not a noob because i saw you in S2 Q/A section several times. I recommand you to unlock your bootloader and flash a custom recovery with fastboot and after that you can flash superSU with the custom recovery.
PM me if you want more advices/links.
Since unlocking your bootloader wipes the device - including the psuedo-SD card, you may as well do that first - as soon as it comes out of the box - and get it over with.
The custom recoveries use a different USB VID/PID pair than the normal OS boot for the ADB endpoint - so a single driver (Asus or Google) won't talk to the custom recoveries in ADB mode unless you edit their .INF files (use notepad app, not any other editor) so you can use a single driver for fastboot/adb-OS/adb-recovery. For signed drivers this breaks their signing, but you can still install them. I suppose others get around this by installing multiple drivers - including drivers off of XDA of mysterious origin which are also unsigned.
You can find documentation of relevant USB VID/PID pairs at the bottom of this post
[REF] Nexus 7 Button Combinations
You might find the top bit of that post useful, too
Some folks claim that you need the latest version of the SDK to deal with the new 4.2.2 adb security layer. IMO, I'm not convinced (I'm using Asus drivers from 6/2012, not Google, and everything seems to work fine.) But, it certainly can't hurt to update your SDK.
After that you might as well run stock for a week or two while you are doing more reading (OK, let's say rooted stock); that way when you start ROM-hopping you will have a baseline experience to compare against.
Get yourself a decent OTG cable; maybe a USB key that has storage capacity as big as your device, too. If you want to mount Mass Storage devices as "OTG" devices on a rooted-stock ROM, use chainfire's Stickmount app from the market.
And lastly - just like with any other device, make full Nandroid backups - including for your lightly-rooted stock ROM. You never know when you might want to pull bits and pieces from them later.
Also, I consider myself decently skilled at this stuff - but because I came from a device with a real external SD card, I have managed to totally wipe out my "psuedo-SD card" twice now because I got in a hurry and wasn't paying attention. Moral: at a minimum, get copies of your Nandroid backups off of the device.
Finally, don't use a toolkit - you will learn nothing, and be unable to resolve even the most trivial of problems which eventually crop up. Underneath the hood it's all fastboot and adb anyway.
$.02
bftb0 said:
Since unlocking your bootloader wipes the device - including the psuedo-SD card, you may as well do that first - as soon as it comes out of the box - and get it over with.
...
[REF] Nexus 7 Button Combinations
...
Click to expand...
Click to collapse
The link doesn't work.. Thought I'd mention it
And have fun enjoying your new Nexus. Do yourself a favor no matter what method you use to root/flash: read everything in the op before you flash anything and its better if you wait until others post feedback. I still have a $200 paperweight that says KINDLE on the back.
Sent from my Nexus 7 using XDA Premium HD app
kilometers4 said:
The link doesn't work.. Thought I'd mention it
Click to expand...
Click to collapse
Thanks - fixed it. Dropped one digit at the end.
Thnx for advice guys, will be rom hopping for a while until I find one to stay with for a while. Currently on CM10.1.
As mentioned the lack of real ext sd is a bit of a ball ache. Really wish they had have added the slot to new nexus range.
Hi guys!
I bought a Nexus 7 a few days ago, This is my first Android device, my first tablet and my first attempt at rooting anything. so I was hoping for some help from the experienced folks because frankly i don't know what I'm doing I was hoping you could help me with a sort of beginners guide for rooting, like what i should look out for, whats the safest and easiest toolkit, rom, kernel to use. I know i have so much to learn from you guys and I've been reading some of the threads and im starting to get a bit of it already just asking for a step by step of what i should do im mainly going to use my tablet for torrents, games, and some light photo editing and lots of comics! so how do i start? hope to hear from you guys soon THANKS IN ADVANCE!
For rooting the tablet ..its safe ,the important thing is to follow the instructions .so to root it you can use one of the toolkits in the development section,I preferred wugfresh toolkit more ..but its up to you the other one is also good ... Here's a video which explains the root procedure
https://www.youtube.com/watch?v=wI0_ylxyrWA&feature=youtube_gdata_player
btw update your phone before rooting it
And for flashing Roms there are a lots of guides on how to do it..just use Google
If you got stuck in any boot loops just use the toolkit you first used, to restore to stock or restore with a nandroid backup
Most important thing when you root. before touching a file ..do a nandroid backup in recovery to always stay safe ..
That's it enjoy the forums
Sent from my Nexus 7 using xda premium
BigJoey010 said:
For rooting the tablet ..its safe ,the important thing is to follow the instructions .so to root it you can use one of the toolkits in the development section,I preferred wugfresh toolkit more ..but its up to you the other one is also good ... Here's a video which explains the root procedure
https://www.youtube.com/watch?v=wI0_ylxyrWA&feature=youtube_gdata_player
btw update your phone before rooting it
And for flashing Roms there are a lots of guides on how to do it..just use Google
If you got stuck in any boot loops just use the toolkit you first used, to restore to stock or restore with a nandroid backup
Most important thing when you root. before touching a file ..do a nandroid backup in recovery to always stay safe ..
That's it enjoy the forums
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
well said, but here are some more tips: DO NOT PANIC!! when something goes wrong, which is likely, as you are a newbie to rooting, one thing you must not do is panic. calm down and troubleshoot, what did i do wrong? how do i fix it? and according to my experience, whenever a door slams shut behind you, a new window opens. if one method doesn't work, try another method.
also, read through the entire procedure list before start doing the steps. make sure you understand what is required and how to do it before accidentally doing something stupid. believe me, its happened to me b4, not a pleasant experience when you realise you dont actually meet the criteria to install something. btw, here is a list of common names given to the nexus 7: Nexus 7 (duh!), N7, grouper (wifi only) Tilapia (wifi+3g)
good luck rooting!
Read through the stickied threads and try to understand them. It won't happen right away though; your head will probably spin the first couple of times through.
There is really no "overnight" learning curve to this stuff - even if you are an old hand with Linux/Unix.
BTW, it is important to point something out: There should be no reason for you to feel like you should be in a hurry to root. The N7 is a fantastic device, even when used in a pure stock experience.. You are not going to be missing out by not rooting immediately. Spend some time with your device getting used to the Android way of doing things, and start reading XDA with a relaxed frame of mind. There is plenty of time. It would be different if you have lots of prior Android experience - but you said it - this is your first Android device.
OK, rooting. To try and keep you safe while you are a noob, I'll give this recommendation:
If you see the word "flash" (verb) near the word "bootloader", RUN AWAY!.
The most dangerous thing you can do to an N7 is mess around with the bootloader. You can turn your device into a useless object by getting things wrong, and it is a little bit rare that you need to flash a bootloader anyway. You have been warned.
So, make sure you know the difference between bootloader and "boot partition".
Most Android devices have a single flash memory chip in them which is divided up into a number of partitions. There are 5 principal partitions and about the same number of less frequently used partitions:
THE 5 PRINCIPAL ANDROID PARTITIONS:
(B) boot - a raw blob of binary data containing a "kernel" and a "ramdisk"
(B) recovery - another raw blob of binary data containing a "kernel" and a "ramdisk"
(F) system - The "ROM" part of Android - all the factory (or customized) software, used read-only
(F) data - User data and customizations. A "factory reset" simply erases all the files here
(F) cache - a scratch area used for downloading files and other maintenance operations
B = binary, bootable
F = Filesystem
Now, the two bootable partitions - boot and recovery - are very similar in structure, but extremely different in purpose. (In fact, in stock devices, they both use a private copy of the same kernel) The "boot" partition can produce a UI (User Interface) after it starts up only in conjunction with healthy /system and /data filesystems containing the Android software. But the "recovery" partition can produce a minimal UI even if the /data and /system filesystems are completely empty of files; so it (the recovery boot) is used to do all maintenance operations - including things like installing new /system software or erasing all user data.
So, and Android "rooter" will usually replace the very minimal (and locked-down-security) stock recovery partition with a "custom recovery" that is more friendly, and the vast amount of the "flashing" operations will take place using this custom recovery.
When people talk about "ROMs", they generally mean only TWO of those five partitions mentioned above: the "boot" partition and the "system" partition. When a "ROM" is flashed using the system partition, the usual procedure is:
- The rooter makes a full Nandroid backup.
- The rooter performs a "factory reset" procedure which erases the /data*** and /cache filesystems
- The rooter then "flashes a ROM", which puts in place a new boot partition, erases the /system partition, and then re-populates the /system partition with changed Android system software.
Upon booting an Android phone/tablet after this procedure, the device will behave as if it just came from the factory - but now with a different custom version of Android software. Note that this means that all the things you customized in the previous ROM - wallpapers, settings, home screen app icons, widgets, market apps downloaded, etc - will all be gone. So, folks that make a habit of hopping from ROM to ROM generally have some tricks up their sleeves for making the re-customization of a freshly-installed ROM a little less tedious. (Things like using custom launchers that allow you to save homescreen customizations, apps to restore previously-used market apps & their data, etc, etc, etc)
*** there is some funny business with Android devices that have no removable SDcard storage devices such as the Nexus 7 - the user's "SD card" is emulated, and the files that are stored there are actually stored in the /data filesystem. So, custom recoveries usually have a "factory reset" procedure which deletes all files in /data while scrupulously avoiding erasing things in this /sdcard area ( == /data/media ). This allows you to keep things safe from wiping (pictures, music, ROM files, backups) while still installing a fresh and un-initialized ROM. Note that the stock recovery in the N7 does not do this - when you use the "factory reset" of the stock recovery, EVERYTHING in /data gets erased - everything!
While you are reading about Android, here are some questions/searches to look up that concern rooting activities... have fun!
- What is the difference between grouper/tilapia (or nakasi/nakasig )?
- What does it mean to "install a new launcher" or "install a new home app"?
- What is Android fastboot used for?
- What is the Android ADB (Android Device Bridge) program used for?
- What is the difference between a boot image and a bootloader?
- How do I go about making a Nandroid Backup?
- What are the Carbon and Titanium Backup apps for? What can they do?
- What file browsers on the market are "root aware"?
- What Android settings can be saved by the Google Play Store, and automatically restored into a new ROM?
- Is there a difference between the "Superuser" and "SuperSU" root kits?
- What are the special Hardware Button Combinations used by the Nexus 7?
- What is the Google Android SDK?
- What custom recoveries are available for the Nexus 7?
- How many unique operating modes does the Nexus 7 bootloader display? What are they called?
- What is a MD5 signature? How can it help me stay out of trouble?
- What does soft-booting a bootable image with fastboot do?
- How many (Windows PC) drivers are needed to use ADB (with both the custom recovery and also the regular OS) and fastboot (with the bootloader), 2 or 3?
- Suppose I soft-brick my N7 - how will I transfer files to and from the N7 in this situation?
- What is the difference between adb push/pull and adb sideload?
- What does "sideloading an app" mean?
- Is an Android ".apk" file the same thing as a .zip file, or different?
- In what folder in /data are market apps (.apk files) found? Same question for /system and system apps (.apk files)?
- How do I enable the developer options on my N7 tablet?
- What are the limitations of MTP or PTP file transfer modes?
- Where does the custom recovery tool store backups?
- Are the Android tools "adb" and "fastboot" available for Mac or Linux?
- What are the limitations of the Google Factory Images for the Nexus 7? How are they installed?
- I have a problem using the recovery. Where is the log file stored?
- What is the big stumbling block involved in unlocking the N7 bootloader?
- What operations can you perform using fastboot and the bootloader which you can not do any other way?
OK, that's enough for now.
Thanks Everyone!
bftb0 said:
Read through the stickied threads and try to understand them. It won't happen right away though; your head will probably spin the first couple of times through.
There is really no "overnight" learning curve to this stuff - even if you are an old hand with Linux/Unix.
BTW, it is important to point something out: There should be no reason for you to feel like you should be in a hurry to root. The N7 is a fantastic device, even when used in a pure stock experience.. You are not going to be missing out by not rooting immediately. Spend some time with your device getting used to the Android way of doing things, and start reading XDA with a relaxed frame of mind. There is plenty of time. It would be different if you have lots of prior Android experience - but you said it - this is your first Android device..
Click to expand...
Click to collapse
I do appreciate everyones input! yeah i think ill make do with the stock for a couple weeks while i study up on rooting and firmwares. well the main reason i wanted to root was for the games, as much as i want to buy the games i like, i dont have the means to
This is great. Wish I had been fortunate enough to have such great help when I first started.
And the most important rule is the one about reading before you root or flash. This will save you some heartache down the road.
Sent from my Nexus 7 using XDA Premium HD app
How's rooting related to games ? You mean overclocking ?
Sent from my Nexus 7 using xda premium
BigJoey010 said:
How's rooting related to games ? You mean overclocking ?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
sad to say i will have to torrent my games as much as i wanna pay and support the game devs i already blew all my money on steam and buying the N7. ive read somewhere that if u are using the the stock version and you try to run a torrented game it automatically shuts down
No it doesn't ...i be downloaded tons of games(torrents) and I'm on stock and they are working normally
Sent from my Nexus 7 using xda premium
UrbabBear said:
sad to say i will have to torrent my games as much as i wanna pay and support the game devs i already blew all my money on steam and buying the N7. ive read somewhere that if u are using the the stock version and you try to run a torrented game it automatically shuts down
Click to expand...
Click to collapse
All the help you were given....then you bring this up.
I doubt further help will come your way as pirating software is very much frowned upon at xda.
Sent from my cell phone telephone....
kj2112 said:
All the help you were given....then you bring this up.
I doubt further help will come your way as pirating software is very much frowned upon at xda.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
i never really liked pirating software...believe me im a huge fan of steam and i practically buy alll my games legit for the pc.. since steam wallet codes are available at a local store here.. okay i promise i wont pirate and ill try to look for the means to buy from the google store , the thing is i dont have a credit card... and i dont know if google has have something equivalent to steam wallet cards for the google play store.. i could borrow a cc and pay for it.. but is the google play store a safe place to purchase ? i nkow some people disputing alot of charges from google play to everyone, i meant no disprespect.. i was thinking along the lines of test the game if there is no lite version, then when i can i will buy the game :< im still new to the whole tablet arena and im gonna need all the help that i can get
UrbabBear said:
i never really liked pirating software...believe me im a huge fan of steam and i practically buy alll my games legit for the pc.. since steam wallet codes are available at a local store here.. okay i promise i wont pirate and ill try to look for the means to buy from the google store , the thing is i dont have a credit card... and i dont know if google has have something equivalent to steam wallet cards for the google play store.. i could borrow a cc and pay for it.. but is the google play store a safe place to purchase ? i nkow some people disputing alot of charges from google play to everyone, i meant no disprespect.. i was thinking along the lines of test the game if there is no lite version, then when i can i will buy the game :< im still new to the whole tablet arena and im gonna need all the help that i can get
Click to expand...
Click to collapse
a good way to get started is to get yourself a prepaid credit card from 7eleven and use that for purchases from the play store.
Billchen0014 said:
a good way to get started is to get yourself a prepaid credit card from 7eleven and use that for purchases from the play store.
Click to expand...
Click to collapse
as much as that service would be convenient its not available in my country thanks! i hope somebody brings it here ... i found a workaround already now just a matter of saving up for the good apps! so in the mean time lite versions here i come!
UrbabBear said:
as much as that service would be convenient its not available in my country thanks! i hope somebody brings it here ... i found a workaround already now just a matter of saving up for the good apps! so in the mean time lite versions here i come!
Click to expand...
Click to collapse
http://play.google.com/about/giftcards/ use this to see if any retailers near you sell.
Sent from my Nexus 7 using xda premium
Hey guys, what do you think are the most basic and necessary apps that i should get ? running on stock
, ive checked some and go a file manager
If you think you are going to root down the road...
If you think there is a good chance that you are going to root down the road, I would suggest unlocking the bootloader in the near future. You'll need to do this and it wipes everything on the tablet. Even if you don't root, there's isn't any major downside to having the bootloader unlocked and you can always relock it later.
It's better to do that before you've put a lot of time into customizing your tablet to perfection and then have to redo it all.