Hello, soon i'm gonna receive a nexus 7 first gen, and I've been wondering... Can someone please point me to the guides to rom/custom recovery/kernel etc install? I'm an ex galaxy y rom dev, so I'm not clueless,but I was overwhelmed by the amount of work and wanted to see if someone could guide me through the process of bettering my future nexus.
What I'm looking for: overclock, paranoid possibly but cyanogenmod is fine too, being able to play long sessions of ingress over tethering.
Stock.
So you're saying you're an ex-dev yet need someone to guide you? Look in the stickies, there's plenty of guides already out. No reason for anyone to write up a new one about stuff that's already covered in detail.
Sent from my Galaxy Nexus using xda premium
sireangelus said:
Hello, soon i'm gonna receive a nexus 7 first gen, and I've been wondering... Can someone please point me to the guides to rom/custom recovery/kernel etc install? I'm an ex galaxy y rom dev, so I'm not clueless,but I was overwhelmed by the amount of work and wanted to see if someone could guide me through the process of bettering my future nexus.
What I'm looking for: overclock, paranoid possibly but cyanogenmod is fine too, being able to play long sessions of ingress over tethering.
Click to expand...
Click to collapse
Best advice you'll get is to do a nandroid backup after you install custom recovery and root.....then read the different rom features and flash and flash....til you find something you like. Its all preference .....10 people will respond to this with 10 different suggestions. Its really not gonna be helpful to you.
Sent from my cellular telephone
sireangelus said:
Hello, soon i'm gonna receive a nexus 7 first gen, and I've been wondering... Can someone please point me to the guides to rom/custom recovery/kernel etc install? I'm an ex galaxy y rom dev, so I'm not clueless,but I was overwhelmed by the amount of work and wanted to see if someone could guide me through the process of bettering my future nexus.
What I'm looking for: overclock, paranoid possibly but cyanogenmod is fine too, being able to play long sessions of ingress over tethering.
Click to expand...
Click to collapse
Hi, sireangelus...
The moderators here on XDA generally frown on 'best ROM/best Kernel' type threads and posts, so I'm not going to recommend any. Besides, it wouldn't be of much use to you anyway... ROMs and Kernels are very much a matter of subjective taste. Checkout this thread, where such discussions are allowed.
------------------------------------------
With regard to flashing anything on the Nexus 7... the first thing you need to do is get your Windows Drivers sorted out (I'm assuming you're using Windows; apologies if not - sorry, but I have no experience of Linux or Apple devices) .
Read this thread on driver installation... actually this thread is worth reading in its own right, as it contains a lot of very useful and pertinent information with regard to the use of fastboot.
------------------------------------------
Custom ROMs come in .Zip form and are flashed via a Custom Recovery, like TWRP or CWM. Once you have either of these recoveries installed you can Root, flash Custom ROMS and/or Custom Kernels.
Although there seems a lot of material to read through, opening up your Nexus 7 to Custom ROMs isn't quite as difficult or as technically challenging as it appears. Your primary goal should be to get a Custom Recovery installed first. A short synopsis is as follows...
*****
1. Get your PC drivers installed and working, so your Nexus 7 can 'talk' to your PC.
2. Hook up your Nexus 7 to your PC, boot into the bootloader, and UNLOCK the bootloader.
3. Fastboot flash a Custom Recovery, like TWRP or CWM.
4. Using that Recovery... flash the Custom ROM .Zip of your choice.
*****
You will need to know how to use fastboot. It's a powefull command line tool, and the two most important commands are...
fastboot oem unlock - used for UNLOCKING the bootloader. The Nexus 7 bootloader MUST be unlocked, before fastboot flash commands can be executed. Even if you're just returning the Nexus 7 back to factory stock, the bootloader MUST be unlocked.
fastboot flash recovery recovery.img - used for installing a Custom Recovery like TWRP or CWM, where recovery.img is the name of your Custom Recovery .img file.
For myself, I just rename Custom Recovery .img file anyway, to recovery.img, as it reduces the scope for typos at the command prompt, and it's easier to remember and type than something like openrecovery-twrp-2.6.3.0-grouper.img (for example)... which is the full name of the TWRP Custom Recovery .img file for 'grouper' Nexus 7's.
------------------------------------------
Short of 're-inventing the wheel'... and rewriting what has already been written, read the stickies at the top of this forum.
Take your time... understand what you're doing (and why you're doing it), and it's difficult to go wrong.
Good luck.
Rgrds,
Ged.
//
GedBlake said:
Hi, sireangelus...
The moderators here on XDA generally frown on 'best ROM/best Kernel' type threads and posts, so I'm not going to recommend any. Besides, it wouldn't be of much use to you anyway... ROMs and Kernels are very much a matter of subjective taste. Checkout this thread, where such discussions are allowed.
------------------------------------------
With regard to flashing anything on the Nexus 7... the first thing you need to do is get your Windows Drivers sorted out (I'm assuming you're using Windows; apologies if not - sorry, but I have no experience of Linux or Apple devices) .
Read this thread on driver installation... actually this thread is worth reading in its own right, as it contains a lot of very useful and pertinent information with regard to the use of fastboot.
------------------------------------------
Custom ROMs come in .Zip form and are flashed via a Custom Recovery, like TWRP or CWM. Once you have either of these recoveries installed you can Root, flash Custom ROMS and/or Custom Kernels.
Although there seems a lot of material to read through, opening up your Nexus 7 to Custom ROMs isn't quite as difficult or as technically challenging as it appears. Your primary goal should be to get a Custom Recovery installed first. A short synopsis is as follows...
*****
1. Get your PC drivers installed and working, so your Nexus 7 can 'talk' to your PC.
2. Hook up your Nexus 7 to your PC, boot into the bootloader, and UNLOCK the bootloader.
3. Fastboot flash a Custom Recovery, like TWRP or CWM.
4. Using that Recovery... flash the Custom ROM .Zip of your choice.
*****
You will need to know how to use fastboot. It's a powefull command line tool, and the two most important commands are...
fastboot oem unlock - used for UNLOCKING the bootloader. The Nexus 7 bootloader MUST be unlocked, before fastboot flash commands can be executed. Even if you're just returning the Nexus 7 back to factory stock, the bootloader MUST be unlocked.
fastboot flash recovery recovery.img - used for installing a Custom Recovery like TWRP or CWM, where recovery.img is the name of your Custom Recovery .img file.
For myself, I just rename Custom Recovery .img file anyway, to recovery.img, as it reduces the scope for typos at the command prompt, and it's easier to remember and type than something like openrecovery-twrp-2.6.3.0-grouper.img (for example)... which is the full name of the TWRP Custom Recovery .img file for 'grouper' Nexus 7's.
------------------------------------------
Short of 're-inventing the wheel'... and rewriting what has already been written, read the stickies at the top of this forum.
Take your time... understand what you're doing (and why you're doing it), and it's difficult to go wrong.
Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you fir the advice, ill treasure it. I didn't exactly asked for the best rom, didn't i. What i intended was to narrow it down a little bit. For example, do kernels here work both for stock and for paranoid/cyanogen?
Sent from my GT-I8750 using Tapatalk
Related
Hello,
Right now I have the stock FRF85B build on my nexus one. I want su and superuser, nothing else. I have already unlocked the bootloader. What do I do from here.?I do not want to install custom ROMs at this point.
Go to erasethis.net/wordpress I wrote an entry today similar to what you want includes links
disgustip8ted said:
Go to erasethis.net/wordpress I wrote an entry today similar to what you want includes links
Click to expand...
Click to collapse
That's great - but didn't you start with a custom recovery?
Can you drop a custom recovery on a stock recovery for FRF85B without the right Superboot?
I ask, because I am also stuck with this stock build and recovery. And when I read the instructions for installing Amon_RA, one of the prerequisites is Superboot. The problem is that there is no Superboot for this build yet.
HALP! I feel like I'm stuck in a chicken-and-egg scenario.
Ah I forgot that part. Wrote that up while at work. Inthe last section there is a link to the page where lox posts an update.zip for root access. I opened the zip and extracted the boot.img and flashed that I think,then I flashed the recovery for amon-ra.
After that is when I put the update.zip from lox on and flashed his update.zip for root access with the such utility.
The method posted in the dev section works perfectly. Root without unlocking. Then you can install a custom recovery/rom if you want.
__________________________________
N1 w/ XDA App
I second this post. I am in the EXACT same situation as the original poster and I'm frankly embarrassed that I can't figure out what to do next.
If we're making huge requests, can you write it up for mac users? There is a surprising lack of documentation for us. I hope this doesn't open me up to a flamewar - if it counts for anything I've been lustily eying windows 7..
edit: I'm an idiot and had not googled the right question. If you run a mac, and have the bootloader unlocked already please see this link:
http://theonda.org/articles/2010/03...-performance-boost-and-some-serious-geek-cred
use your brains to suss out the relevant directions, make sure you have a more updated version of ROM Manager or RA or whatever custom recovery you want and basically just ignore the stuff about custom radios etc. You're basically just using the terminal (or whatever windows / linux does) to flash the custom firmware back on.
Again if you have the bootloader already unlocked (icon appears on startup), just find generic directions for your OS on how to install custom recovery. On the mac, it's simply few terminal commands using the fastboot program linked off the page linked above.
Sorry I can't be of more help - i have to be up early and it's pushing midnight.
Hi all, I've been able to flash boot.img with fastboot (with a pc), just wondering if its possible to do it within nexus 7 itself? I could do this with other custom kernel that comes in a .zip format (using cwm touch).
So the question is how could I flash boot.img by using the device itself?
You can flash it through recovery but it will be less safe than via fastboot as fastboot will give you an error if there is one and you can choose not reboot until it is fixed.
The ota itself is flashed through recovery but it will perform the manual checks (such as md5sum) for you.
I strongly recomend to flash any firmware with fastboot but there is always other ways, search and decide what you want to do
Sent from my HTC Vision using Tapatalk 2
SpikeySpy said:
Hi all, I've been able to flash boot.img with fastboot (with a pc), just wondering if its possible to do it within nexus 7 itself? I could do this with other custom kernel that comes in a .zip format (using cwm touch).
So the question is how could I flash boot.img by using the device itself?
Click to expand...
Click to collapse
I agree with demkantor, it is much safer to use fastboot for this.
Your options for flashing a boot.img from recovery:
1. manually apply the img to the correct block using dd (assuming busybox is available in recovery. IIRC it is... meh)
2. create a flashable zip containing the boot.img and an edify script. (decompress a working flashable zip and work it out :highfive
Neither of these is as safe or simple as fastboot.
the main reason for asking this is that when i'm away from my PC, and say if i do not require speed i could easily switch to a battery saving kernel or if i need performance i could easily switch back, etc.
Is it right to say that I could get boot.img from franco's kernel and replace the boot.img in m-kernel's zip file? Do I have to modify any other config files in the zip?
Wow I miss read your post, I wads seeing hboot not boot image.
Sure flash away in recovery, I believe most devs will make one in a flash able .zip
But to be flashing one on the fly to save battery life is a little goofy, there are much better techniques to save on battery life. Usually just stick with the same kernel all the time, when you know you won't be around a charger for a while turn off sync, under clock etc.
Kernels are safe to flash in recovery as worse situation puts you in a boot loop, just make sure you make a nandroid before flashing
Oh and if for some reason you want to do it on the fly and don't have a .zip, open a terminal and type
su
flash_image boot /sdcard/boot.img
reboot
May not be the best thing to do when inside os, so I would still recommend recovery flashing or fastboot
Sent from my Nexus 7 using xda premium
flashing in recovery? but as far as im aware cwm touch could only flash flashable zip files and does not accept .img. Does it mean i have to convert the .img file to be a flashable zip?
Usually, i would boot into recovery and flash to different kernels from there since it doesn't take long so i thought it's something most people would do depending on the needs at that time.
In all my years of android I have never changed kernels on the fly, I would find what works and use it no matter to the situation. But of course I'm not saying be like me, do as you please, I just am not sure what benefit you will really get.
So the kernel you want to use is in a .img and the dev never made a flash able .zip for you to use? I haven't used clockwork for any device in a long time, is there a terminal option within it?
Sent from my Nexus 7 using xda premium
apologies if my question is a little silly as i'm new to android.
yeah for example the franco kernel which is just an img file. Usually i would just flash it in recovery if it's a zip file but only use fastboot if its a img format.
There isn't any terminal option in the recovery but there's one within the OS.
No its fine, asking questions is what this forum is for, sorry for missreading your first post!
I've never flashed a kernel from within an os before so I'm not sure if that would be an issue but I also sont think it will be necessary. I suggest looking into ways of saving battery life, if you google it or search xda you will find lots of tips. Like I said normally find a kernel that works and just flash it and stick with it, when you need to be extra carefull of battery life for a time just underclock, undervolt (still not sure how much undervolting really does) turn off sync, turn off gps, wifi, etc etc
Sent from my HTC Vision using Tapatalk 2
battery saving kernel was just one of the reasons. I just thought if I could depend less on a PC then I could literally do everything on my tablet alone.
For my case, i like m kernel as it's fast gives me the performance but then again it isn't exactly stable (though i've no idea why it just reboots at times when i'm using it), however franco seems pretty stable for me but i just hope they could increase the performance a little.
I read somewhere that says reboot could be caused by incorrect voltage settings, hence I've been trying to tweak the voltage but still unable to get a stable settings.
HERE is a great reference on kernels if you want to do a bit of research learning, may help you decide what will work best for you
I'll take a look, definitely very informative. Thanks for that mate.
Hey guys, getting my Nexus 4 for Christmas and looking to install Franco Kernel.
I was wondering the best way to install it, I have searched for tuts but nothing is clear. I know he has an app for his kernel, does this require root to use? It doesn't mention it.
Any help would be greatly appreciated.
Go here and download the All In One script: http://forum.xda-developers.com/showthread.php?t=1995688
You're going to need to unlock the bootloader (will wipe your phone), so follow the steps in doing that.
Next, you'll need the latest CWM Recovery: http://forum.xda-developers.com/showthread.php?t=1995440
Follow those steps. Then download the Franco kernel .zip from its appropriate thread and flash it in CWM.
Shnew said:
I was wondering the best way to install it, I have searched for tuts but nothing is clear. I know he has an app for his kernel, does this require root to use? It doesn't mention it.
Click to expand...
Click to collapse
First thing I'm going to tell you - Go back and read the OP. Because he actually does have instructions in it (Although very minimal).
http://forum.xda-developers.com/showpost.php?p=34375927&postcount=1
Here's the quick and simple of how to do it.
1. Download the Nexus 4 Toolkit -- http://forum.xda-developers.com/showthread.php?t=1995688 (READ THE OP COMPLETELY)
2. Unlock the bootloader.
3. Install custom recovery.
4. TAKE A BACKUP!
5. Transfer kernel files to device.
6. Use recovery to flash files.
7. Hold breath while booting.
DO NOT USE TOOLKITS. Especially if you're new to modding.
That's like saying, I want to overclockmy computer. Just give me a toolkit where I can one click and overclock my computer.
Read more here http://forum.xda-developers.com/showthread.php?t=1469909
Do it the proper way and download ADB drivers
http://forum.xda-developers.com/showthread.php?t=1514942 (enable USB debugging)
set up ADB environment
adb reboot bootloader
fastboot oem unlock
unlock bootloader on phone
download clockwork recovery or TWRP (i suggest TWRP)
put the .img file of recovery into your /platform-tools/
fastboot flash recovery <name-of-file>.img
then boot into recovery and there you can flash your ROM, gapps, kernel.
In the long run, IT WILL PAY OFF because eventually YOU will be faced with a problem with your phone and you won't be able to recover your phone because you dont know basic fastboot or adb commands all simply because you wanted to use a toolkit. People are already asking on how to use adb / fastboot in Q&A, we can reduce the clutter by not having people use toolkits and actually learning how adb / fastboot works when it isn't a very complicated thing to do at all
netsyd said:
4. TAKE A BACKUP!
Click to expand...
Click to collapse
Make sure the boot partition is checked when you are backing up. To return to the stock kernel, (if you ever need to) you will need to restore this backed up boot image.
Sent from my Nexus 4
Can I just root and use the stock recovery to flash franco kernel? I want to be able to download ota from google in the future...
hophamson said:
Can I just root and use the stock recovery to flash franco kernel? I want to be able to download ota from google in the future...
Click to expand...
Click to collapse
no you need custom recovery
Unlock the bootloader, install a custom recovery and flash the zip.
Sent from my Nexus 4, powered by CyanogenMod via XDA Developers app.
Hello all. I have been doing a bit of research for the past night on how to flash files on the galaxy s4 via command line. I just came from the HTC One XL, this is my first Samsung device, and I am wondering, is there a fastboot mode like there is on the HTC One XL? I had no problem flashing boot images and recoveries via fastboot using the HTC Bootloader. I ask because I am more comfortable flashing recovery images via the bootloader rather than using the android interface like goomanager for example -- and its just overall useful to know what commands are used to push files to the device.
If anyone might be able to link me to a thread or a brief explanation I would be very grateful. I just rooted my device and I'm ready to get going with flashing custom ROMs and Kernels! Thanks xda
TheEmpyre said:
Hello all. I have been doing a bit of research for the past night on how to flash files on the galaxy s4 via command line. I just came from the HTC One XL, this is my first Samsung device, and I am wondering, is there a fastboot mode like there is on the HTC One XL? I had no problem flashing boot images and recoveries via fastboot using the HTC Bootloader. I ask because I am more comfortable flashing recovery images via the bootloader rather than using the android interface like goomanager for example -- and its just overall useful to know what commands are used to push files to the device.
If anyone might be able to link me to a thread or a brief explanation I would be very grateful. I just rooted my device and I'm ready to get going with flashing custom ROMs and Kernels! Thanks xda
Click to expand...
Click to collapse
I'm fairly certain that "fastboot" is only an HTC thing - at least I've only ever seen it with HTC devices in my experience. The sticky guide here: http://forum.xda-developers.com/showthread.php?t=2301762 is actually very informative. I would recommend reading through it once, regardless of how much experience you have with flashing and android. It covers some device-specific topics, including our bootloader, recoveries, etc.
Aou said:
I'm fairly certain that "fastboot" is only an HTC thing - at least I've only ever seen it with HTC devices in my experience. The sticky guide here: http://forum.xda-developers.com/showthread.php?t=2301762 is actually very informative. I would recommend reading through it once, regardless of how much experience you have with flashing and android. It covers some device-specific topics, including our bootloader, recoveries, etc.
Click to expand...
Click to collapse
I have viewed this thread already but thank you for posting and looking. I guess my question is: What is the command or application to flash files in download mode? For HTC the app is fastboot, Android is adb, but what is download mode? Or I'm not sure you can even flash partitions via download mode? Haha I have just been unable to find any resources to help answer these questions
TheEmpyre said:
I have viewed this thread already but thank you for posting and looking. I guess my question is: What is the command or application to flash files in download mode? For HTC the app is fastboot, Android is adb, but what is download mode? Or I'm not sure you can even flash partitions via download mode? Haha I have just been unable to find any resources to help answer these questions
Click to expand...
Click to collapse
Odin/Hiemdal are the programs used though I haven't seen it in a CLI for the S4.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
TheEmpyre said:
I have viewed this thread already but thank you for posting and looking. I guess my question is: What is the command or application to flash files in download mode? For HTC the app is fastboot, Android is adb, but what is download mode? Or I'm not sure you can even flash partitions via download mode? Haha I have just been unable to find any resources to help answer these questions
Click to expand...
Click to collapse
Fastboot is used on all Android devices for bootloader-level commands. However, our bootloader is locked so you will not be able to fastboot flash anything whatsoever. ADB is the in-the-OS command interface. Loki is a program that we use to sidestep the locked bootloader. You use Loki to flash on a custom recovery, then flash ROMs that are lokify'd like normal. There's a recovery in the dev section that will autoloki in the event you try to flash a ROM that isn't set up.
Odin is a flashing tool, so to equate it something HTC wise... it's a RUU, 'cept it's just the baseline tool and you still need to download the ROM itself. To use it, you download the Odin ROM(normally a .tar), reboot the phone into Downloading mode, connect it to your computer, and follow the steps outlined in wherever you got the Odin ROM from. Very carefully.
unremarked said:
Fastboot is used on all Android devices for bootloader-level commands. However, our bootloader is locked so you will not be able to fastboot flash anything whatsoever. ADB is the in-the-OS command interface. Loki is a program that we use to sidestep the locked bootloader. You use Loki to flash on a custom recovery, then flash ROMs that are lokify'd like normal. There's a recovery in the dev section that will autoloki in the event you try to flash a ROM that isn't set up.
Odin is a flashing tool, so to equate it something HTC wise... it's a RUU, 'cept it's just the baseline tool and you still need to download the ROM itself. To use it, you download the Odin ROM(normally a .tar), reboot the phone into Downloading mode, connect it to your computer, and follow the steps outlined in wherever you got the Odin ROM from. Very carefully.
Click to expand...
Click to collapse
Excellent. Thank you for putting it in "HTC Terms" so I have some sort of schema I can relate it to. Everything you said is consistent with the reading I did last night, and also everything I downloaded and familiarized myself with before flashing a ROM earlier today. Everything worked flawlessly and I have a TW ROM and Kernel (Loki) all set up...I just never had a good relation to what I had been doing on my One XL. Thanks for the help everyone, adding [Solved]
I've been searching the forums and the rest of the net looking for a how to root a Nexus 7 without using a toolkit (using fastboot/adb instead). I'm in the process of learning as much as I can about the operating system itself but haven't gotten to the point yet where I know how to root a device on my own.
What I'm wondering is:
1. All the guides on rooting the N7 include flashing a custom recovery, then SuperSU, so on and so forth. Is there any way to avoid having to flash CWM or TWRP to root an N7?
2. Is there any where I can learn how to root my device without a toolkit?
If I've somehow missed an obvious thread on the subject, I apologize.
keithD9 said:
I've been searching the forums and the rest of the net looking for a how to root a Nexus 7 without using a toolkit (using fastboot/adb instead). I'm in the process of learning as much as I can about the operating system itself but haven't gotten to the point yet where I know how to root a device on my own.
What I'm wondering is, all the guides on rooting the N7 include flashing a custom recovery, then SuperSU, so on and so forth. Is there any way to avoid having to flash CWM or TWRP to root an N7? If I've somehow missed an obvious thread on the subject, I apologize.
Click to expand...
Click to collapse
Flashing SuperSu is very simple with TWRP.
1. Install Fastboot (and adb)
2. Go here: http://teamw.in/project/twrp2/103
3. Download the latest image (at time of writing, 2.6)
4. Open up the terminal (Unix/Linux) or command prompt (windows)
4.1 (If you haven't unlocked bootloader, you will need to type "fastboot oem unlock". WARNING! THIS ERASES ALL DATA
5. Type "fastboot flash recovery recoveryfilename.img" and replace recoveryfilename.img with the name of the image downloaded.
6. Install SuperSu
Click to expand...
Click to collapse
If you aren't keen on unlocking bootloader, see this thread here. It is, however, a glitchy, no good (IMHO) method which could brick your nexus and may not be compatible with all android versions.
Also, be warned, my instructions aren't bulletproof, you might be better following instructions from one of the many threads about rooting/unlocking bootloader of the nexus 7, incase of typo/stupidity on my behalf! Here is one thread for CWM http://forum.xda-developers.com/showthread.php?t=1741395
Do I need TWRP or CWM in order to root though? Or can you still root with stock recovery?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
keithD9 said:
Do I need TWRP or CWM in order to root though? Or can you still root with stock recovery?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
You would need custom recovery but you don't have to flash it permanently. You can use the command 'fastboot boot recovery nameofrecovery.img'
It will merely boot the device into a temporary custom recovery for you to root it.
Sent from my Galaxy Nexus
Aha, and there we have it. Finally clicked. I'm positive someone must have said the same thing but in a different way. Thanks for the info!
Sent from my Nexus 7 using xda app-developers app