Related
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.
Good morning guys,
I see a lot of threads here about rooting 4.2.2, but in all of them it is recommended to root the phone by installing zip archive from a custom recovery.
I don't want to change stock recovery - is there any way to root it by flashing img from adb? I did it in this way on 4.2.1, by installing CF-Auto-Root-mako-occam-nexus4.img file from adb.
Can anyone advice how to get root without flashing custom recovery?
I have to ask,....why would you NOT want a custom recovery? What is the point in using a crippled stick recovery?
From my Evo LTE, yup.
Look at this How to thread in the general section, I copied and pasted relevant information. I kept a custom recovery and didn't try this method, but it says it will not flash a custom recovery.
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
2) Rename the file to customrecovery.img, and make sure it is in the same directory as your fastboot.exe file;
3) Download (to /sdcard on your device) the latest version of either ChainsDD's Superuser (not currently working), or Chainfire's SuperSU;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img
6) Wait for it to boot;
7) Navigate the menus the recovery menu on your device and select an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
8) Reboot. Done.
You can flash custom recovery via fastboot, use it to install su.zip and when you will choose restart after that, you will have question about you want custom recovery permanently or not, if you choose no then after restart you will have stock recovery
scottspa74 said:
I have to ask,....why would you NOT want a custom recovery? What is the point in using a crippled stick recovery?
From my Evo LTE, yup.
Click to expand...
Click to collapse
I want to make installing of future OTA as simple as possible. So I will get root and freeze all the system apps i don't want to be run, but when OTA comes I will be able to install it and will not receive any error messages which i had during this OTA.
It seems like this is a good solution:
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img
Click to expand...
Click to collapse
Do i understand correctly that this boots customer recovery on my phone from PC hard drive, but doesn't flash it to the phone? So, I'm able to install root.zip from it, but when i reboot the phone I don't have a custom recovery.
You can do as i mentioned in my post before or you can use as well command mentioned by ketjr81: fastboot boot nameofrecovery.img in both cases you will have had stock recovery after restart
Thank you guys, you have solved my issue. Now i have to find a ZIP with root to flash.
fatum2002 said:
Thank you guys, you have solved my issue. Now i have to find a ZIP with root to flash.
Click to expand...
Click to collapse
you find it in thread mentioned by ketjr81
Can i install CWM on locked bootloader?
Ben Ling said:
Can i install CWM on locked bootloader?
Click to expand...
Click to collapse
Yes.
An 'exploit' has recently become available for ROOTING the Nexus 7 without unlocking the BOOTLOADER.
This 'exploit' works... I have tested it myself.
Until recently, I believed that because FASTBOOT wasn't an option (as a result of a LOCKED BOOTLOADER), there was no way of FLASHING anything.
Happily, I was disabused of this notion by bftb0... and I can confirm, you can indeed install CWM (or TWRP) with a locked BOOTLOADER.
-----------------------------
Here's how...
First, you need to run this 'exploit' to acquire ROOT.
Upon reboot, you should now be rooted, with Chainfires SuperSU package and associated SU binary installed.
It's important that you are ROOTED before you proceed.
Next, get Android Terminal Emulator from PlayStore.
Download a CUSTOM RECOVERY .img of your choice... either CWM (Both 'Grouper' and 'Tilapia' variants are available)...
...or TWRP for 'Grouper' (N7 WiFi) or TWRP for 'Tilapia' (N7 3G).
Rename it to recovery.img... and copy it to the root of the Nexus 7's internal storage (emulated SD card).
In Terminal Emulator, run the following command...
Code:
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Upon completion of this command, shutdown and reboot your device into the BOOTLOADER, and from there, boot into your CUSTOM RECOVERY... in pretty much the same way had you FASTBOOT FLASHED it.
-----------------------------
You are now free to flash whatever ROMs or kernels you like.
However, a word of caution... because the BOOTLOADER remains locked, FASTBOOT is strictly off limits; it simply won't work.
So the first thing you should do after flashing TWRP or CWM is...
*** MAKE A NANDROID BACKUP ***
If the device becomes 'wedged/bootlooped' as a result of some ROM flash gone wrong, then you will have no choice but to unlock the BOOTLOADER (with full wipe) in order to fix it.
But if you have a NANDROID backup... piece of cake... just restore.
-----------------------------
Credits and kudos must go to XDA members, nhshah7, who made this 'exploit' available and bftb0, whose post pointed me in the right direction, with regard to the 'dd' command.
-----------------------------
I can confirm all of this works... my Nexus 7 is currently rooted, running a custom recovery (TWRP), with a custom ROM and Kernel (see sig) installed - all sitting behind a LOCKED BOOTLOADER.
...no Factory Reset (wipe) required...
...and no Unlocked Padlock Symbol upon boot.
Rgrds,
Ged.
Previously I installed cwm and can boot,just 1 time.
I tried to boot into but nothing.
What to do?
Sent from my Sony Xperia™ sola using XDA Premium App
@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"
SSyar said:
@GedBlake well it works for the first time for me as well,.,., used the TWRP latest..,.,.
afterwards it says "no command"
Click to expand...
Click to collapse
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.
GedBlake said:
This is really peculiar... I had a few problems myself, initially... but I just assumed I made a typo mistake in TE - but I never had a "no command" message. It took me two or three goes before I got it to work.
And it works fine now, without problems.
I recall reading, a while ago, you had to delete a file from /system called recovery-from-boot.p after flashing a custom recovery in order to get the custom recovery to stick. I never had to do this myself, maybe 'cos I'm running a custom ROM.
Are you on stock, or running a custom ROM?
Rgrds,
Ged.
Click to expand...
Click to collapse
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium
Ben Ling said:
I'm on stock JB 4.2.2 JDQ39 Wi-Fi & 3G version,so what to do now?
Sent from my Asus Google Nexus 7 using XDA Premium
Click to expand...
Click to collapse
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.
GedBlake said:
Have you tried running the dd command again?... As I previously mentioned, it took two or three attempts, before it 'stuck' on my N7.
Now I have no problem booting into TWRP... similarly, I have tested this procedure with CWM - and again no problems.
With a root capable file manager, you could try deleting (or renaming) the file recovery-from-boot.p which can be found in /system, and then try again.
Rgrds,
Ged.
Click to expand...
Click to collapse
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App
Ben Ling said:
How to boot into cwm?press volume button?
Sent from my Google Nexus 7 using XDA Premium App
Click to expand...
Click to collapse
Shut down the tablet completely.
Press and hold the VOL DOWN button... whilst holding, press the POWER button.
This will boot you into the BOOTLOADER.
Using the VOL buttons, navigate to RECOVERY.
Press the POWER button to select.
Rgrds,
Ged.
Just tested this method... again... (using dd to install a Custom Recovery)... with both CWM and TWRP... and in both instances, the installations survived a reboot. So I'm puzzled why there seems to be a problem here.
---------------------------------
I have semi-automated the process in order to avoid typing long complicated commands into Android Terminal Emulator. A process, which, by it's nature, is subject to typographical error.
Here's how...
Download the Custom Recovery of your choice to your Nexus 7.
Rename it to recovery.img
Copy it to the root of the emulated SD card (internal storage).
---------------------------------
Download this script file...
writerecovery.zip
Unzip and copy it to the root of the emulated SD card (internal storage).
(Alongside the recovery.img).
---------------------------------
Install Script Manager from Google Playstore.
Open Script Manager and locate the script file writerecovery.sh on the root of the emulated SD card.
Press ENTER on it...
Select OPEN AS... Script/Executable...
Select SU (root) from the toolbar...
Select Run...
The script will now execute the following command...
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
...writing the recovery.img to the recovery partition.
See attached thumbnails for the sort of thing you should expect to see.
---------------------------------
I have tested this method several times... switching between CWM and TWRP. And performing multiple reboots, to ensure that the Custom Recovery 'stuck' in each instance.
---------------------------------
Hope this works... if it doesn't... then I'm at a loss to explain why.
Maybe somebody with more technical knowledge can assist.
All I know, is it works for me... on my Nexus 7.
Rgrds,
Ged.
well i installed recovery using goo manager ,.,. got this response from other thread and is working for me ,.,., goo manager also has the option to restart in recovery so really good for me
Help with my Condition
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.
junisheikh said:
OK, I need help with the following Scenario with Nexus 7 2012 Wifi
My USB Port is damaged. Managed to charge batter with external wires. After that I was able to:
> Root my Nexus7 with KingRoot app (several tries does the trick)
> Install CWM (non-touch) with ROM Manager
> Boot into CWM and do a dummy Flash of Update-SuperSU.zip file just to see if it works on Locked Bootloader. It was successful.
Now I came across your thread, What I need help with is:
WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?
This is going to be a one way ride for me, if I brick I have a paperweight.
(I have however a Backup from CWM, which I can restore if the tablet manages to boot into CWM after bricking)
Need assistance, opinions, strategy with this. Response Awaited.
Click to expand...
Click to collapse
Hi, junisheikh...
To answer your question...
junisheikh said:
"WILL I BE ABLE TO FLASH A CUSTOM ROM + GAPPS on a Locked Bootloader via CWM ?"
Click to expand...
Click to collapse
Yes, you should be able to.
---
The bootloader lock state is irrelevant when it comes to flashing stuff via a Custom Recovery (such as CWM or TWRP).
All an unlocked bootloader does, is it allows the device to accept fastboot flash commands from a connected PC or Mac, and which is the usual way of flashing a Custom Recovery, and then subsequently rooting it.
I would, however, advise against using CWM. ClockWorkMod Recovery is old and hasn't been updated for quite some time, and may cause problems.
Instead, you should take a look at TWRP (TeamWin Recovery Project). This Custom Recovery has a better user interface, and is less likely to cause you problems.
---
Although your bootloader is locked, you have managed to acquire root via KingRoot... which means you can flash a Custom Recovery with the Flashify app...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
This app allows you to flash Recoveries and Boot images (stock and custom) directly from the device itself, providing the device is rooted. The free version of Flashify has a limit of 3 flashes per day. This shouldn't be a problem though... Custom Recoveries aren't something you generally flash on a regular basis.
(See my attached screenshots for a flavour of how Flashify works.)
---
You can find the latest version of TWRP for the Nexus 7 WiFi model here...
http://techerrata.com/browse/twrp2/grouper
Download to your Nexus 7, and use the Flashify app to flash.
And then download whatever Custom ROM+GAPPS you like, and flash via TWRP.
Incidentally, the NANDROID backup you've already created with CWM is NOT compatible with TWRP. So you'll need to create a new NANDROID backup, should you choose to flash TWRP.
---
junisheikh said:
This is going to be a one way ride for me, if I brick I have a paperweight.
Click to expand...
Click to collapse
This is possible, because you don't have access to fastboot (due to your broken USB port) you won't be able to fastboot flash back to Google Factory stock should you not be able to boot Android (for whatever reason) after flashing some Custom ROM. But providing you have a NANDROID backup and a Custom Recovery (CWM or TWRP) installed, you **should** be able to recover from softbricks such as bootloops. But having said that, I would tread carefully.
Hope this helps, and good luck.
Rgrds,
Ged.
im trying to use goomanager to update twrp to version openrecovery-twrp-2.6.3.1-grouper.img and it keeps timing out on the webpage (webpage not available).
i dont have access to a computer currently.. is there another way to upgrade twrp? is there a zip i can flash from recovery? (running a older ver of twrp)
joshag said:
im trying to use goomanager to update twrp to version openrecovery-twrp-2.6.3.1-grouper.img and it keeps timing out on the webpage (webpage not available).
i dont have access to a computer currently.. is there another way to upgrade twrp? is there a zip i can flash from recovery? (running a older ver of twrp)
Click to expand...
Click to collapse
Same here. Goo hasn't worked for me for several months now. Pretty much given up on it.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
joshag said:
im trying to use goomanager to update twrp to version openrecovery-twrp-2.6.3.1-grouper.img and it keeps timing out on the webpage (webpage not available).
i dont have access to a computer currently.. is there another way to upgrade twrp? is there a zip i can flash from recovery? (running a older ver of twrp)
Click to expand...
Click to collapse
Hi, joshag....
If your Nexus 7 is already rooted, you can use the apps, Flash Image GUI or Flashify to flash a Custom Recovery directly from the Nexus 7 itself.
Just install one of them (personally I prefer Flashify)... download the TWRP Recovery Image file appropriate to your particular Nexus 7 (links below)... and then use Flashify or Flash Image GUI... the on screen instructions are pretty self explanatory, just ensure you pick the FLASH RECOVERY option, and then navigate to the folder on your Nexus 7 where the TWRP recovery image downloaded to... (usually the /download folder).
So... no PC or fastboot required... just a rooted Nexus 7. (If you aren't already rooted, you're out of luck I'm afraid).
I use this method myself quite frequently, particularly when I can't be bothered booting up my laptop.
Links for TWRP Custom Recovery Images for Nexus 7 (2012)
For WiFi only model...
http://techerrata.com/browse/twrp2/grouper
For WiFi & 3G model...
http://techerrata.com/browse/twrp2/tilapia
Hope this helps.
Rgrds,
Ged.
That was easiest/most concise explanation.
Sent from my Nexus 7 using xda app-developers app
OK, I see that this subject has not been properly addressed in this forum and there are a lot of users who still use tool kits,etc. for this. That's fine but you're missing out on how to more effectively manage your device. I'm writing this off the top of my head, and on my n9 which is not so easy, so I may modify it in the future.
The first thing you want to do is learn how to use fastboot. Fastboot allows you to flash image, .img, files on your device. If you've never done that start here, http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Rooting is as simple as flashing a custom recovery on your device and then booting into that recovery and flashing Chainfires supersu.
So how do you flash a custom recovery? Well I strongly recommend twrp. Download the latest from here, https://dl.twrp.me/flounder/ I always find it easier to rename the file you download to simply recovery. Make sure you maintain the .img file extension. Download this onto your pc and remember what folder you downloaded it to.
Then download the supersu.zip file to your device. Download from here, https://download.chainfire.eu/696/SuperSU
Now you're ready to get started. Boot your device into the bootloader and connect it to your pc.
On your computer open the folder where you downloaded the twrp image. On an open area in that folder shift, right click on your mouse. You should see a pop up and a place to "open a command window here" In that command window type, fastboot devices. If you see your device's serial number you're good to go to flash the twrp image file.
OK, the Nexus 9 is not as easy to root as other Nexus devices. So start by typing, fastboot boot recovery.img. (Remember I told you to rename the twrp image file to recovery, if you didn't do that use the full name of the twrp file you downloaded for recovery.img) Once you boot into twrp go to install and find the supersu.zip you downloaded onto your device. Install it.
Then from twrp, boot back into the bootloader.
Once booted into the bootloader open a command window in the same folder as you have the twrp image downloaded. Then type fastboot flash recovery recovery.img
You're now rooted and have twrp installed.
Having major problems trying to do this on Marshmallow, lol.
This no longer works as described on 6.0. I can get you rooted but I can't get twrp to work properly. It doesn't decrypt the device. But you'll need a usb stick.
To the usb stick copy flar2's elemental x kernel, http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657. Also copy supersu, http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Boot into twrp:
fastboot boot twrp.img. Use twrp 2.8.7.0 and the full name of the image file
When you boot into twrp hit cancel. It'll boot into twrp but won't decrypt your device. In twrp go to mount and mount your usb stick. Then from twrp flash the elemental x kernel. Then flash supersu.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
This no longer works as described on 6.0. I can get you rooted but I can't get twrp to work properly. It doesn't decrypt the device. But you'll need a usb stick.
To the usb stick copy flar2's elemental x kernel, http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657. Also copy supersu, http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Boot into twrp:
fastboot boot twrp.img. Use twrp 2.8.7.0 and the full name of the image file
When you boot into twrp hit cancel. It'll boot into twrp but won't decrypt your device. In twrp go to mount and mount your usb stick. Then from twrp flash the elemental x kernel. Then flash supersu.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
so mounting the usb stick to the pc, it will be recognized by twrp?
tykalx said:
so mounting the usb stick to the pc, it will be recognized by twrp?
Click to expand...
Click to collapse
If you don't have USB stick, adb sideload worked for me to flash supersu beta 2.5.1
And I'm using stock modified kernel chainfire posted to keep selinux enforcing.
tykalx said:
so mounting the usb stick to the pc, it will be recognized by twrp?
Click to expand...
Click to collapse
No, you need a usb stick and adapter to the device. But what mrRobinson said should work too. You can do that from your pc.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
This no longer works as described on 6.0. I can get you rooted but I can't get twrp to work properly. It doesn't decrypt the device. But you'll need a usb stick.
To the usb stick copy flar2's elemental x kernel, http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657. Also copy supersu, http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Boot into twrp:
fastboot boot twrp.img. Use twrp 2.8.7.0 and the full name of the image file
When you boot into twrp hit cancel. It'll boot into twrp but won't decrypt your device. In twrp go to mount and mount your usb stick. Then from twrp flash the elemental x kernel. Then flash supersu.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, that worked.
I went and installed Busybox, not sure if I needed to?
I really want to get this thing decrypted now but am happy to wait for a Marshmallow solution rather than go back. I suppose I could flash a ROM without forced encryption from the flash drive too? As long as I do a full wipe?
I only got my N9 a week ago and haven't had time to play with it so all this encryption stuff is new to me.
---------- Post added at 09:08 PM ---------- Previous post was at 09:04 PM ----------
I am rooted but can;t copy hosts file over, system is read-only, is this an encryption thing or has something gone wrong please?
---------- Post added at 09:28 PM ---------- Previous post was at 09:08 PM ----------
One more question..
If I was to factory reset and then flash the kernel and supersu would I get an unencrypted device? Or if I hit the "decrypt data" button in the "wipe" menu in TWRP? I am scared to press it, lol.
Excuse me but this only adds confusion in case of 6.0. So far the most comprehensive guide I found here is this one (see also an answer there).
That solution involves wiping data, so you need your stuff backed up somewhere. In my case I restored playstore apps from google account and just reinstalled the rest from apks.
I answered my own questions here http://forum.xda-developers.com/nexus-9/help/decrypt-marshmallow-question-t3222592. Thanks again for the help jd1639.
jd1639 said:
This no longer works as described on 6.0. I can get you rooted but I can't get twrp to work properly. It doesn't decrypt the device. But you'll need a usb stick.
To the usb stick copy flar2's elemental x kernel, http://forum.xda-developers.com/nexus-9/orig-development/kernel-elementalx-n9-0-02-alpha-t2931657. Also copy supersu, http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Boot into twrp:
fastboot boot twrp.img. Use twrp 2.8.7.0 and the full name of the image file
When you boot into twrp hit cancel. It'll boot into twrp but won't decrypt your device. In twrp go to mount and mount your usb stick. Then from twrp flash the elemental x kernel. Then flash supersu.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
worked like a charm :good:
Any difference when already running 7.0?
I keep getting stuck in a bootloop after flashing SuperSu. Any thoughts on this? I've tried wiping caches/dalvik. Running latest stock version of 6, latest version of TWRP, installed proper ElementalX for Android version, boots fine after the kernel install.
sjrixon said:
Any difference when already running 7.0?
Click to expand...
Click to collapse
For N (and MM in some cases), you need systemless support - which the current version of SuperSU has. (Magisk 12.0 has it as well.)
Where Magisk (vice SuperSU) has advantages is being able to hide that you're rooted (Android/Samsung Pay, Visa Checkout, SafetyNet, etc.) - which is, in fact, why I am evaluating Magisk.
So far, I have seen next to no disadvantages to N - even on "moldy" SoCs (such as the TI OMAP in my Galaxy Nexus - the oldest hardware I've heard of - let alone seen - running N on a daily basis; I run N as a daily driver). I even prefer N to MM, let alone anything older, on the selfsame GNex (which utterly flies in the face of "common wisdom"; it makes me wonder, in fact, if "common wisdom" is a coverup for "fear of change", since said "common wisdom" predates Android by several years).
Hi,
Isn't is required to unlock bootloader first ?
Where this unlocking is done in this procedure ?
Thanks,
ranran
ranchu-panchu said:
Hi,
Isn't is required to unlock bootloader first ?
Where this unlocking is done in this procedure ?
Thanks,
ranran
Click to expand...
Click to collapse
That is always the first step and doesn't change. This thread covers the changing root methods on different Android versions.
madbat99 said:
That is always the first step and doesn't change. This thread covers the changing root methods on different Android versions.
Click to expand...
Click to collapse
Thanks,
Yet, I noticed in many threads of rooting in mediatek devices, that just flashing recovery.img and boot.img is the 1st procedure to make the device root.
Does it mean that mediatek device does not require unlocking the bootloader ?
Thx