Database Users

Rooting FRF85B

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.

[TOOL] XOOT 1.1: Root your XOOM and more!

PLEASE READ
Cornea, the universal toolkit tool I promised following XOOT's discontinuation, has been released! It's free, and tons better. Please check it out rather than downloading XOOT. Click here to go to the thread page. Thanks.
(XOOT will still be available for download if you want it for whatever reason.
Bugs
XP not supported properly. This will not be fixed. It has been fixed in the new version of XOOT, Cornea.
Changelog
1.1 (CURRENT VERSION)
XP x86 compatibility! (not working)
Compressed file changed from RAR to ZIP so that users don't need WinRAR or equivalent to extract XOOT
1.0
Initial release of XOOT
Sorry that this isn't in Android Development, I have less than 10 posts and I can't wait to share this...
XOOT is the easiest tool you can use to root your XOOM! It works for XP 32bit, Vista, 7 and 8 flawlessly. In fact, it does more than root. Here's the grand list:
Bootloader lock/unlock (WIPES DATA)
Root your XOOM (thanks solarnz)
Convert from a region XOOM to a GED XOOM
Flash non-flashable boot animations
Includes ADB and FASTBOOT for all your Android developing needs!
Brick your device if you are ruthless and unplug it during the progress.
HONG KONG USERS SHOULD STAY AWAY. PLEASE?
IF YOU'VE DONE OTA UPDATES READ THE POST ON THE SECOND PAGE ABOUT THE GREEN ANDROID OF DEATH.
XOOM ADB drivers are required to benefit from XOOT! Please download them and install.
Hope you guys benefit from this. It definitely works because I used it to root, flash recovery, unlock bootloader and flash boot animations.
If you're amazing at ADB, try adding more commands! All ya need is a bit of batch programming experience. If you plan to just use this and enjoy, OK! Just open and go!
FAQ included in the ZIP.
Please read: Now that XP compatibility has been added, XOOT is harder (but still easy) to open.
If you are running XOOT on Windows XP or Server 2003, rename choice_xp.exe to choice.exe. Then proceed.
If you are using XOOT on a version higher than XP, open XOOT.bat without renaming Choice_XP.exe
Have fun with your XOOM!
PLEASE NOTE THAT I AM NOT RESPONSIBLE FOR ANY ISSUES CAUSED
~Epic118

i am not responsible if this goes cockeyed, btw

has any1 tried this? cheers

Region xoom to ged xoom? What does that mean?
Sent from my MZ601 using XDA App

Region/GED Xooms
A region XOOM is one that's not in the US. It may have changes made by Motorola, and get updates slower. This is why UK Xooms have SD card read/write officially.
A GED XOOM is a XOOM that's in the US. It's known as a Google Experience Device, and cannot be modified my Motorola. This is why US Xooms have SD card readonly officially - they are not allowed to add the hacked mod to enable write.
I read this on a website. Sorry but I can't find out which one, I will give you the URL link soon...

Anyone tried yet? Am contemplating.

Will it work on a Singapore version of Motorola Xoom MZ604 on 3.2?

Hi, will it work on my Hong Kong MZ601 3G Xoom

BlueEditionE6 said:
Hi, will it work on my Hong Kong MZ601 3G Xoom
Click to expand...
Click to collapse
Be careful with your Hong Kong Xoom. They seem to have different partition set-ups and have been known to lose (misplace) 28 gb of their internal storage when rooted/modded without a particular patch made by solarnz. Have you seen this thread: http://forum.xda-developers.com/showthread.php?t=1203128 ?

Anybody with a VZW Zoom use this to unlock and root?
Sent from my LG-P925 using xda premium

Zacky32 said:
Will it work on a Singapore version of Motorola Xoom MZ604 on 3.2?
Click to expand...
Click to collapse
Should do. I think mine is a Singapore XOOM because when I first turned it on the language was set to English (Singapore).
HONG KONG XOOM owners STAY AWAY. I have read that solarnz's universal root thing doesn't work wonderfully well on those.

Sorry new on here and to root (rooted my htc magic ages ago)
Is this the real deal and will this work on my uk wifi XOOM?
Thanks
Sent from my xoom using xda premium

This for WIFI only model? or LTE/4G devices?

the green bot of !
Ok this thread is missing some things.
* Fastboot OEM Unlock Wipes your Tablet. backup first!
* The green bot of !
there is one problem that exists with all xoom roots/cwm hacks.
I had this problem as well as a bunch of other people when trying to flash CWM.
If these files are present after a OTA update then your xoom when entering recovery will show the green android robot with a explanation point instead of CWM.
if you have applied a official ota update.zip then you have one of the following two files on your xoom that will prevent CWM from working.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
If you already have root and your not trying to root with CWM then you can fix this issue with the following commands before flashing the recovery.img
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
If you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
This Wipes your Xoom also
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
after your xoom boots back up and goes into the setup screens skip setup and enable usb debugging. ( do not install a ota update! )
and restart xoot to root the stock rom.

joe ferreira said:
Ok this thread is missing some things.
* Fastboot OEM Unlock Wipes your Tablet. backup first!
* The green bot of !
there is one problem that exists with all xoom roots/cwm hacks.
I had this problem as well as a bunch of other people when trying to flash CWM.
If these files are present after a OTA update then your xoom when entering recovery will show the green android robot with a explanation point instead of CWM.
if you have applied a official ota update.zip then you have one of the following two files on your xoom that will prevent CWM from working.
/system/recovery-from-boot.p
/system/etc/install-recovery.sh
If you already have root and your not trying to root with CWM then you can fix this issue with the following commands before flashing the recovery.img
adb remount
adb shell rm /system/recovery-from-boot.p
adb shell rm /system/etc/install-recovery.sh
If you do not already have root on your xoom when you get the green bot of ! then you have to do the following with the stock moto files for your device (from moto dev).
This Wipes your Xoom also
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot -w
fastboot reboot
after your xoom boots back up and goes into the setup screens skip setup and enable usb debugging. ( do not install a ota update! )
and restart xoot to root the stock rom.
Click to expand...
Click to collapse
Thanks, didn't know about that. I'll be adding some more code to XOOT soon to tackle this.
XOOT does notify you that locking/unlocking bootloaders does wipe the device. However I will modify the main post to show this.

Can anyone tell me where to get the ged files from, I've searched for them but really don't know what I'm looking for.
Thanks in advance

@joe ferreira,
I have quoted you in my adb/fastboot/rooting guide, as I didn't know why so many newer Xoom owners are having issues flashing CWM recovery.
@epic118, I'm also really interested in whether the Xoot method works safely...it would make life a whole lot easier for a lot of people! The Xoom community is a little shy about one-click rooting methods, since one last spring bricked a whole bunch of tabs, but if proven effective and safe, folks would eat it up.
---------- Post added at 10:57 PM ---------- Previous post was at 10:47 PM ----------
toori88 said:
Can anyone tell me where to get the ged files from, I've searched for them but really don't know what I'm looking for.
Thanks in advance
Click to expand...
Click to collapse
Your stock files are available in a couple of threads pinned to the top of the General forum, or from the motodev site.

What is the best way to backup without having root capabilities yet to utilize an app like Titanium?
Sent from my Xoom using XDA App

Never mind, I was under the impression that rooting the Xoom wipes it right off the bat. It seems this is only when you unlock the boot loader.
Sent from my Xoom using XDA App

just using xoot to root my device,
i have unlocked te bootloader,
currently flashing with cwm recovery but its stuck on starting fast boot protocol support. should it stay on that for a while the first time?
EDIT:
never mind when i rebooted holding vol up and power to try go into fast boot all i get is "starting RSD protocol support 3"
i don't know what this means but it will power up normally

[Requests] Odin stock Rom for AT&T SGS3

Hi,
I just brick my phone tweaking the build.prop, so I need a Stock Odin Rom for AT&T SGS3 phone or a modify CWM recovery that look the external sd instead of internal sd, so I can flash the stock Build.prop. Any help will be appreciated, also some Donation will be sent.
Thanks
Matrox

matrox00612 said:
Hi,
I just brick my phone tweaking the build.prop, so I need a Stock Odin Rom for AT&T SGS3 phone or a modify CWM recovery that look the external sd instead of internal sd, so I can flash the stock Build.prop. Any help will be appreciated, also some Donation will be sent.
Thanks
Matrox
Click to expand...
Click to collapse
In the absence of a stock flashable ROM, and if you can still get into CWM, you can do the following:
1. Mount system in recovery
2. Pull the build.prop via ADB (I believe it's adb pull /system/build.prop) on your computer
3. Revert/fix whatever tweaks you jacked up when messing with it earlier (on your PC)
4. ADB push it back
5. ADB reboot
If build.prop is all that was wrong, hopefully this may get you back in business.

pinoymutt said:
In the absence of a stock flashable ROM, and if you can still get into CWM, you can do the following:
1. Mount system in recovery
2. Pull the build.prop via ADB (I believe it's adb pull /system/build.prop) on your computer
3. Revert/fix whatever tweaks you jacked up when messing with it earlier (on your PC)
4. ADB push it back
5. ADB reboot
If build.prop is all that was wrong, hopefully this may get you back in business.
Click to expand...
Click to collapse
Under CWM mount system, adb show error device nor found, its look that my only hope is a stock odin rom.
Thanks

Ouch, sounds like bad news. Hopefully someone will post something you can use to revert soon.
Sent from my GT-P3113 using Tapatalk 2

matrox00612 said:
Hi,
I just brick my phone tweaking the build.prop, so I need a Stock Odin Rom for AT&T SGS3 phone or a modify CWM recovery that look the external sd instead of internal sd, so I can flash the stock Build.prop. Any help will be appreciated, also some Donation will be sent.
Thanks
Matrox
Click to expand...
Click to collapse
Go to the att android dev section there is a root method posted that also has a unbrick fixboot.tar file for Odin, that will put you back in business.
http://forum.xda-developers.com/sho...ick your phone from flashing a gsm boot image
Sent from my SAMSUNG-SGH-I747

stan.s said:
Go to the att android dev section there is a root method posted that also has a unbrick fixboot.tar file for Odin, that will put you back in business.
http://forum.xda-developers.com/sho...ick your phone from flashing a gsm boot image
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
Thanks for the info, but thats the boot.img I need the system.img packed into an Odin tar.

matrox00612 said:
Thanks for the info, but thats the boot.img I need the system.img packed into an Odin tar.
Click to expand...
Click to collapse
There is no system.img released yet..Many of us are waiting for that system.img file. Its not leaked, released or created yet... But should be released, created soon. I am pretty sure the developers are working on it.
Till then we can just wait!!

masonjoe69 said:
There is no system.img released yet..Many of us are waiting for that system.img file. Its not leaked, released or created yet... But should be released, created soon. I am pretty sure the developers are working on it.
Till then we can just wait!!
Click to expand...
Click to collapse
Yes it is like that, we have to wait a little, but lets get the first dev to throw a working odin flashable file some motivation, i will donate 50 beers.

[Q] Shot self in foot, edited build.prop now N7 won't boot

I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.

lbloo said:
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
Click to expand...
Click to collapse
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.

I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?

lbloo said:
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
Click to expand...
Click to collapse
rooted stock ROM yea. I've also flashed a pure aosp ROM over stock without any reprocussions.

Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.

lbloo said:
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
Click to expand...
Click to collapse
I don't know what you picked up, but here's a stock/rooted ROM that you can flash in your cwm recovery http://forum.xda-developers.com/showthread.php?t=1776330
Aosp works too, its your choice

if you know how to use adb you can just boot to recovery and push the stock build.prop to your tab

I downloaded a stock copy of the stock build.prop, used the adb push command to push it into /system rebooted and nothing. Still hangs on black screen upon boot.
I then downloaded the stock ROM which simms22 kindly pointed me to, used the adb push command to copy the zip file into /data/media/Firmware, used CWM v6.0.1.0 to "install zip file from sdcard" and I got an error, here is the output:
Installing:/sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
Finding update package...
Opening update package...
Installing update package...
E:Error in /sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
(Status 0)
Installation aborted.
I tried both the Odexed and Deodexed files, both gave same results.
Am I missing a step in the process?

It's working now!
I was afraid I was messing up some of the adb commands so I downloaded the Nexus 7 Toolkit 2.0 (Great tool for someone like me)
- via Toolkit re-transferred the odexed and deodexed ROM files, reflashed, same errors as above
- via Toolkit re-installed CWM Recovery 6.0.1.0, reflashed, same errors as above
- via ADB Shell used CHMOD to modify file rights of the ROM files (stab in the dark), same errors as above
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Not sure why the other ROMS would not flash, but at this point I'm not going to mess around to try to figure it out.
Many thanks to simms22 and PhxkinMassacre for getting me pointed in the right direction.

prly a bad download.
after pushing the file you need to set the correct mode:
Code:
adb shell chmod 644 /system/build.prop

Me too - also hosed my own build.prop
lbloo said:
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Click to expand...
Click to collapse
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack

Looking back I don't recall resetting the file rights after modifying the file and that was likely the root cause of my problems.
You should try the chmod command a couple of posts back.

JackinNC said:
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Click to expand...
Click to collapse
What location did you push it to? /sdcard/?
Sent from my Nexus 7 using xda app-developers app

mvmacd said:
What location did you push it to? /sdcard/?
Click to expand...
Click to collapse
Yes. And, to further test, I created a little zip file called test.zip and pushed it to the tablet. I can see it just fine. It's just the grouper zip that I can't find.
Thanks
Jack

I just noticed a diff in filesize between the JRO03D_grouper.zip file I am using and one shown in a Youtube video entitled "how to put a rom to flash on a semi-bricked nexus 7 with recovery" by Youtube user metroid031993. (I'm too green to post outside links on XDA)
Mine is 261814702 bytes, the one shown in the video is 32650144 bytes.
Perhaps this is my problem, an invalid zip file. What do you think? And, can someone please tell me the correct size of JRO03D_grouper.zip?
Thanks
Jack
[Note to moderator(s): If I am heading off track in this thread, please don't hesitate to move it or to instruct me to create a new thread. I think the issue may have changed, but I have stayed here since this is where the conversation is for my root issue. Thx!]

JackinNC said:
can someone please tell me the correct size of JRO03D_grouper.zip?
Click to expand...
Click to collapse
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.

Visa Declined said:
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Click to expand...
Click to collapse
Thanks for the confirmation.
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
---------- Post added at 11:19 AM ---------- Previous post was at 10:51 AM ----------
JackinNC said:
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
Click to expand...
Click to collapse
Well, I got the grouper zip into /sdcard/ and was able to upgrade without losing anything. w00t!
Theory:
I was in the same adb "session" this time since I was using adb from the command line. Meaning, the daemon was still running from the first push I did. So, while I couldn't see the grouper zip after the first push (consistent with your experience, dark_samus), I could see it and upgrade with it after second push (also consistent). And, perhaps my previous attempts didn't work before because I was closing and opening the Nexus 7 Toolkit each time, therefore stopping and restarting the daemon, which meant that each push attempt was the first attempt for that "session."
I don't have any solid technical basis to support or refute that theory, it's just one possible theory that, if true, would result in the experience I had.
My problem is resolved. Thanks to everyone who contributed to this, I truly appreciate your help!
Jack

simms22 said:
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
Click to expand...
Click to collapse
how to put the stock image if my n7 doesnt boot to android? pls help
i have CWM already

Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
my bad i already flash a fresh stock rom again, but thanks anyways...

no force encrypt on nexus 6p running mhc19i

Hi, can some one give me a guide on the nexus 6 p running mhc19i for no force encrypt, with either a system root that will allow me to remove apps, or a systemless root that I have to go through recovery, and is there a recovery for this version at this time other then the stock one

gigawatt said:
Hi, can some one give me a guide on the nexus 6 p running mhc19i for no force encrypt, with either a system root that will allow me to remove apps, or a systemless root that I have to go through recovery, and is there a recovery for this version at this time other then the stock one
Click to expand...
Click to collapse
To decrypt you need to format the userdata partition:
Code:
fastboot format userdata
This will obviously wipe your storage so back it up to your PC first. You will also need to flash a custom kernel that doesn't force encryption first otherwise the stock kernel will just encrypt again when you boot after formatting. You need to use TWRP recovery to flash SuperSU to get root. I have detailed instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

yeh, is there a custom kernel for mhc19i

gigawatt said:
yeh, is there a custom kernel for mhc19i
Click to expand...
Click to collapse
Of course, there are many. Have you actually looked?

yes, I have looked, but most of them have an aroma installer, I am totally blind so I need one I can flash through fastboot as there is no talkback in aroma or recovery mode. Even the stock no force encrypt would be helpful thanks.

gigawatt said:
yes, I have looked, but most of them have an aroma installer, I am totally blind so I need one I can flash through fastboot as there is no talkback in aroma or recovery mode. Even the stock no force encrypt would be helpful thanks.
Click to expand...
Click to collapse
You can flash any of them via fastboot. Extract the boot.img from the zip and flash it:
Code:
fastboot flash boot boot.img
You'll just end up with the default settings. Why don't you just flash TWRP? Then you can install it the intended way.

I can flash twrp through fastboot, but I am totally blind and use a screen reader, so I would have to have some one around to use the twrp interface, since there is no speech there, so I need a kernel or modified no force encrypt boot.img I can flash through fastboot

gigawatt said:
I can flash twrp through fastboot, but I am totally blind and use a screen reader, so I would have to have some one around to use the twrp interface, since there is no speech there, so I need a kernel or modified no force encrypt boot.img I can flash through fastboot
Click to expand...
Click to collapse
Ahh, I see, that is definitely a difficult situation. So basically as I said, I believe any of them can be flashed via fastboot, but it isn't without its own work. You'd need to download the kernel zip, extract it, place the boot.img into your working directory (your fastboot folder), and use the "fastboot flash boot boot.img" command to flash it to the device. This will give you a kernel that doesn't force encryption, and you could then go on to use an app like Kernel Auditor to tweak the settings once you've booted into Android. How possible is this for you?

well I downloaded fk-r12-anykernel2.zip and unzipped it and there was no boot.img inside, so, can you send me a link to a boot.img for his kernel or the stock with no force encrypt, and am I missing any features by not flashing it through recovery, don't really care, just asking, but if you can please send me a boot.img for the verison I posted earlier in the thread.
Thanks so much for your help

gigawatt said:
well I downloaded fk-r12-anykernel2.zip and unzipped it and there was no boot.img inside, so, can you send me a link to a boot.img for his kernel or the stock with no force encrypt, and am I missing any features by not flashing it through recovery, don't really care, just asking, but if you can please send me a boot.img for the verison I posted earlier in the thread.
Thanks so much for your help
Click to expand...
Click to collapse
Apologies for the late reply, been a bit busy with my family. It looks like Franco is one of the kernels that doesn't have the boot.img directly inside the zip. There's probably a way to extract it but it's beyond my expertise. I'm in the process of extracting the boot.img from some other popular kernels for you now though, I'll update here once I have some uploaded. It might take a while because my upload speed is woefully slow.

gigawatt said:
well I downloaded fk-r12-anykernel2.zip and unzipped it and there was no boot.img inside, so, can you send me a link to a boot.img for his kernel or the stock with no force encrypt, and am I missing any features by not flashing it through recovery, don't really care, just asking, but if you can please send me a boot.img for the verison I posted earlier in the thread.
Thanks so much for your help
Click to expand...
Click to collapse
Actually, it turns out none of the kernels have an easily accessible boot.img inside the zip. Things have changed since I last unpacked a kernel. I'll see what I can find out for you.

Here my friend use this thread. From @Tigerstown
https://tapatalk.com/shareLink?url=...share_tid=3306684&share_fid=3793&share_type=t
[UPDATED 3-10-16][Stock modified boot.img for regular root/Android N decrypted boot
It contains a stock modified boot image allowing system root and no force encryption. He updates thread for every build. Flash right from fastboot. If you need anything else feel free to PM me.
Sent from my Nexus 6P using Tapatalk

toknitup420 said:
Here my friend use this thread. From @Tigerstown
https://tapatalk.com/shareLink?url=...share_tid=3306684&share_fid=3793&share_type=t
[UPDATED 3-10-16][Stock modified boot.img for regular root/Android N decrypted boot
It contains a stock modified boot image allowing system root and no force encryption. He updates thread for every build. Flash right from fastboot. If you need anything else feel free to PM me.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Is this the link you meant?
http://forum.xda-developers.com/showthread.php?t=3306684
Yours is directing to download Tapatalk.
PS. Please conduct troubleshooting help in the open forum, the information is of no use to other people searching for it if it's hidden away in an inbox.
PPS. Fantastic idea by the way, I had forgotten about that thread.

Heisenberg said:
Is this the link you meant?
http://forum.xda-developers.com/showthread.php?t=3306684
Yours is directing to download Tapatalk.
PS. Please conduct troubleshooting help in the open forum, the information is of no use to other people searching for it if it's hidden away in an inbox.
PPS. Fantastic idea by the way, I had forgotten about that thread.
Click to expand...
Click to collapse
Yes that's the correct link. I shared it from Tapatalk instead of web browser. Thank you for grabbing the correct one.
Sent from my Nexus 6P using Tapatalk

Heisenberg said:
Apologies for the late reply, been a bit busy with my family. It looks like Franco is one of the kernels that doesn't have the boot.img directly inside the zip. There's probably a way to extract it but it's beyond my expertise. I'm in the process of extracting the boot.img from some other popular kernels for you now though, I'll update here once I have some uploaded. It might take a while because my upload speed is woefully slow.
Click to expand...
Click to collapse
If they are using anykernel zip there is no boot.img.
---------- Post added at 10:38 AM ---------- Previous post was at 10:35 AM ----------
Heisenberg said:
Is this the link you meant?
http://forum.xda-developers.com/showthread.php?t=3306684
Yours is directing to download Tapatalk.
PS. Please conduct troubleshooting help in the open forum, the information is of no use to other people searching for it if it's hidden away in an inbox.
PPS. Fantastic idea by the way, I had forgotten about that thread.
Click to expand...
Click to collapse
I posted that thread in General. I should have posted in dev threads but less traffic the better for me answering the same questions over and over ??