For easy updating by OTA/Factory Images and keeping root, try out Chainfire's Flashfire App see this post.
On 6.0.1 - Instructions for ElementalX method!
Update your device first to latest available image (Flashing Factory images or by OTA)
Flash latest TWRP (linked below) or Temporally Boot it.
From TWRP, Install Systemless SuperSU
Then from in TWRP, Install ElementalX kernel.
If prompted don't allow TWRP to install system supersu.
Reboot
Note: If your using systems-less method and have previously rooted with system, you will need to re-flash stock boot & system first!
Note: Nexus 9 twrp-3.0.2-0-flounder now available!
SuperSU 2.76 now available.
You may need to reflash(or update) ElemetalX kernel again after flashing latest SuperSU.
Note: ElemetalX kernel is not required to successfully root your device, optional extra.
ElementalX Kernel Update to ElementalX-N9-4.15 for 6.0.1.
flar2 said:
UPDATE!!!!
July security update
Do not install on earlier builds!
Download:
ElementalX-N9-4.15
Changes:
-July security update
Click to expand...
Click to collapse
Get an updated ElementalX Kernel for Nexus 9 here
On 6.0.1 - Instructions for ElementalX method!
Update your device first to latest available image (Flashing Factory images or by OTA)
Flash latest TWRP (linked above) or Temporally Boot it.
From TWRP, Install Systemless SuperSU
Then from in TWRP, Install ElementalX kernel.
If prompted don't allow TWRP to install system supersu.
Reboot
Note: If your using systems-less method and have previously rooted with system, you will need to re-flash stock boot & system first!
Thought I post the above here as a guide for people!
Regards
John
it's not working on Nexus 9. When you log into TWRP, the device asks for a damn password I don't even know. if you press Cancel, you would see an empty internal storage
kkyyb said:
it's not working on Nexus 9. When you log into TWRP, the device asks for a damn password I don't even know. if you press Cancel, you would see an empty internal storage
Click to expand...
Click to collapse
Same problem here, had to revert back to LMY48M.
Same here. The only other posts I found on this say to use "default_password" but doesnt work for me either.
My password is a PIN so its not the pattern issue either.
For TWRP I believe I just click cancel when request for password!
Then I mounted a USB stick in TWRP and flashed the files from that!
Anyone have any luck using titanium backup and usb stick? I can't get TiBu to find it. Otherwise everything is fine. Flashed 6.0, then TWRP, ElementalX and SuperSu.
capt730 said:
Anyone have any luck using titanium backup and usb stick? I can't get TiBu to find it. Otherwise everything is fine. Flashed 6.0, then TWRP, ElementalX and SuperSu.
Click to expand...
Click to collapse
Haven't used titanium yet since I updated!
For USB: -
The New OTG feature of M is effecting "StickMount" app (probably needs to be updated).
Edit: Stickmount has now been updated and works on Marshmallow
"ES File Explorer" is able to mount usb sticks for copying files and media from and to USB!
corkiejp said:
Haven't used titanium yet since I updated!
For USB: -
The New OTG feature of M is effecting "StickMount" app (probably needs to be updated).
"ES File Explorer" is able to mount usb sticks for copying files and media from and to USB!
Click to expand...
Click to collapse
Yeah, I have been using ES. Was trying to avoid moving backup to internal to restore apps.
kkyyb said:
it's not working on Nexus 9. When you log into TWRP, the device asks for a damn password I don't even know. if you press Cancel, you would see an empty internal storage
Click to expand...
Click to collapse
You have to format data in twrp after pressing cancel
Can someone please explain to us how to root android m since the article doesn't do a good job of explaining?
vandizzam said:
Can someone please explain to us how to root android m since the article doesn't do a good job of explaining?
Click to expand...
Click to collapse
Edited: New method now linked in OP
If you can not access files with TWRP, put them on a USB stick and Mount it in TWRP and flash them from there!
madbat99 said:
You have to format data in twrp after pressing cancel
Click to expand...
Click to collapse
I did this, and now my N9 is stuck on the new boot animation.
AhsanU said:
I did this, and now my N9 is stuck on the new boot animation.
Click to expand...
Click to collapse
You need a permissive kernel.
---------- Post added at 07:16 AM ---------- Previous post was at 07:14 AM ----------
vandizzam said:
Can someone please explain to us how to root android m since the article doesn't do a good job of explaining?
Click to expand...
Click to collapse
And you can stop calling it m now. It's marshmallow. "M" was the name of a developer preview of an unnamed version of Android. Is that what you're trying to root? Lol. Not likely. Marshmallow it is!
Edited!
The good news is Chainfire(+New Team) or working on another method to root!
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344 Which no longer has the possibility of causing a factory reset on encrypted devices!
Link to new method is a 404 error
VermontKindBud said:
Link to new method is a 404 error
Click to expand...
Click to collapse
Thanks, just put the correct link in!
capt730 said:
Anyone have any luck using titanium backup and usb stick? I can't get TiBu to find it. Otherwise everything is fine. Flashed 6.0, then TWRP, ElementalX and SuperSu.
Click to expand...
Click to collapse
Stickmount has now been updated to work with MarshMallow!
Not **quite** working. Have installed TWRP 2.8.7.0, Supersu beta 2.51 and ElementalX 4.01 kernel; was able to install adbd insecure, so adb goes root and I can su from shell there.
Still when booting into recovery, TWRP asks for password, and if I cancel cannot mount anything but cache. Supersu seems to grant SOME permissions but for example I cannot modify default.prop (neither from the device nor via adb - the latter says about read only file system).
[email protected] said:
Not **quite** working. Have installed TWRP 2.8.7.0, Supersu beta 2.51 and ElementalX 4.01 kernel; was able to install adbd insecure, so adb goes root and I can su from shell there.
Still when booting into recovery, TWRP asks for password, and if I cancel cannot mount anything but cache. Supersu seems to grant SOME permissions but for example I cannot modify default.prop (neither from the device nor via adb - the latter says about read only file system).
Click to expand...
Click to collapse
Use chainfire's method to root!
TWRP needs to be update. or follow these instructions to no-forceencrypt your device.
corkiejp said:
ElementalX Kernel method was the old way to root and didn't properly root encrypted devices, Adblockers such as "AdFree" couldn't write the hosts files.
Use chainfire's method to root!
TWRP needs to be update. or follow these instructions to no-forceencrypt your device.
Click to expand...
Click to collapse
I use Chainfire's method in EX 4.01
EX always rooted "properly"
There was no system write on the initial release. But encryption was always handled properly. Please dont spread misinformation
Related
Hello folks,
I'm at a loss currently.
I had rooted my stock .314 FW and installed XZDualRecovery.
All worked flawlessly, installing Busybox, using Titanium Backup, Adaway etc.
Now suddenly I discovered that I'm not able to remount /system read-write anymore! Root seems to work absolutely normal otherwise, it's just that if I try to remount (via ES File Explorer or manual terminal command), either nothing happens (ES File Explorer) or I get a "Permission denied" (terminal).
I absolutely don't have any idea what could be the cause of this!
And not being able to update the hosts file or doing any alterations of system files of course is a problem!
I had several rooted devices and never encountered this issue!
Any ideas??
hasenbein1966 said:
Any ideas??
Click to expand...
Click to collapse
I once had such a problem on my phone (SGS4), I was running CM with SuperUser.
Switching to SuperSU helped me back then, SU seemingly did not work correctly.
I guess you are using SuperSU on your stock ROM, so this is no option. But still I'd still assume that your problems are directly SuperSU-related...
Yes, I'm using SuperSu (current version: 2.01).
It's not possible to update to version 2.02.
EDIT!
Obviously the recovery is broken also! It's not possible to boot into recovery!
How do I repair that (and how can it be that the recovery is gone in the first place??)? Simply remove the files which are listed in the XZDualRecovery thread's uninstall instructions, then install normally?
hasenbein1966 said:
Obviously the recovery is broken also! It's not possible to boot into recovery!
How do I repair that (and how can it be that the recovery is gone in the first place??)? Simply remove the files which are listed in the XZDualRecovery thread's uninstall instructions, then install normally?
Click to expand...
Click to collapse
I am still using this one, it works flawlessly (should also be compatible with 314): http://forum.xda-developers.com/showthread.php?t=2708194
BabelHuber said:
I am still using this one, it works flawlessly (should also be compatible with 314): http://forum.xda-developers.com/showthread.php?t=2708194
Click to expand...
Click to collapse
This doesn't answer my question...
hasenbein1966 said:
This doesn't answer my question...
Click to expand...
Click to collapse
Sorry, but I do not have any experience with the DualRecovery. I can only state that I do not have such issues with the recovery I use.
So perhaps your problems go away if you use the same one - I think this could be worth a try...
The problem, and that is one reason why I ask, is that recovery and system RW HAD worked! Flawlessly!
But now no more!
How can that be?
You don't need to answer anymore. I uninstalled Dual Recovery, then tried to install CWM. After that Android didn't start at all (Bootloop). Fed up, I wiped and installed from scratch
You probably just needed to run easy root again. I have to run it twice every time. Then I install the recovery from in Windows using the tool provided, then I flash the superuser update. Zip from the chainfire website. Probably overkill, but it's worked for me about 10 times on this device. Remember to turn off firewall and antivirus and run the installers as admin in Windows.
Hello all,
I am VERY new to this and was reading a fair bit on forums etc before having a go. I really want to make my Desire X use more of its memory as its internal memory is just way to small....
I have the HTC Windroid universal tool.
I have successfully unlocked the phone (its shows unlocked on bootup)
I have then installed TWRP successfully.
I have also installed a new Kernel (NeXus) in an attempt to help.
The issue I have am having is when I used the "Gain Root" - Flash Superuser option, it ran OK and said installing (although on the phone it wouldn't access some cahces), but said it was done successfully. The SU App was then ont he phone, BUT when i ran the Root Checker app, it said the phone was NOT properly rooted. When I ran the SuperUser app it said the binary was out of date, but the install options both failed.
I have also tried to manually load the UPDATE-SuperSU-v2.02.zip but that also didn't work?
My main (and only real object) is to get the phone so I can use more memory and run more apps etc, and possibly dump some bloat stuff I will never use, but i dont know how to continue without a successful root in place?
Any ideas? I have read around a lot but cant find a solution?
HTCdesireXrookie said:
Hello all,
I am VERY new to this and was reading a fair bit on forums etc before having a go. I really want to make my Desire X use more of its memory as its internal memory is just way to small....
I have the HTC Windroid universal tool.
I have successfully unlocked the phone (its shows unlocked on bootup)
I have then installed TWRP successfully.
I have also installed a new Kernel (NeXus) in an attempt to help.
The issue I have am having is when I used the "Gain Root" - Flash Superuser option, it ran OK and said installing (although on the phone it wouldn't access some cahces), but said it was done successfully. The SU App was then ont he phone, BUT when i ran the Root Checker app, it said the phone was NOT properly rooted. When I ran the SuperUser app it said the binary was out of date, but the install options both failed.
I have also tried to manually load the UPDATE-SuperSU-v2.02.zip but that also didn't work?
My main (and only real object) is to get the phone so I can use more memory and run more apps etc, and possibly dump some bloat stuff I will never use, but i dont know how to continue without a successful root in place?
Any ideas? I have read around a lot but cant find a solution?
Click to expand...
Click to collapse
Try flashing the zip in this link http://download.chainfire.eu/396/SuperSU/ from recovery, I would advise you use the newer TWRP recovery (2.7.1) found here http://forum.xda-developers.com/htc-desire-x/orig-development/recovery-twrp-2-7-1-desire-x-t2830924 and infinityshooter's kernel http://forum.xda-developers.com/showthread.php?t=2483489
Hope it helps... (Providing you're Desire X single sim)
Thanks yes I am single sim...
How do I "Update" my TWRP?
HTCdesireXrookie said:
Thanks yes I am single sim...
How do I "Update" my TWRP?
Click to expand...
Click to collapse
Install recovery.img via Fastboot, theres quite alot of guides around xda if you do a search
Will_Xda said:
Install recovery.img via Fastboot, theres quite a lot of guides around xda if you do a search
Click to expand...
Click to collapse
OK progress report, I have uploaded the recovery img of TWRP with windroid tool fastboot. 2.7.1 now installed.
TWRP 2.7.1 looks much nicer..no grafix glitches.
installed the zip 1.94 SU you pointed me too.......
SuperSu then said it needed to update the binary when I ran the app on the phone, which I chose to do via TWRP.
Reboot completed via TWRP (all automatically)
SuperSu app then opened and seemed to work.
Rootchecker says: ROOTED!
WOOT! thanks a lot....
Now the question comes .. how do I get my Desire X to start using all its available memory eg SD car, and also how do I use priority access to get rid of default apps I never use?
PS I do appreciate the time you are taking to answer these questions!
HTCdesireXrookie said:
O
TWRP 2.7.1 looks much nicer..no grafix glitches.
installed the zip 1.94 SU you pointed me too.......
SuperSu then said it needed to update the binary when I ran the app on the phone, which I chose to do via TWRP.
Click to expand...
Click to collapse
Don't forget to update supersu to latest version by flashing flashable zip :
http://forum.xda-developers.com/showthread.php?t=1538053
Delta-flasher said:
Don't forget to update supersu to latest version by flashing flashable zip :
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
That version didn't work before? Will it be OK now I have got it working with the 1.94 version?
HTCdesireXrookie said:
That version didn't work before? Will it be OK now I have got it working with the 1.94 version?
Click to expand...
Click to collapse
It should work now.
HTCdesireXrookie said:
OK progress report, I have uploaded the recovery img of TWRP with windroid tool fastboot. 2.7.1 now installed.
TWRP 2.7.1 looks much nicer..no grafix glitches.
installed the zip 1.94 SU you pointed me too.......
SuperSu then said it needed to update the binary when I ran the app on the phone, which I chose to do via TWRP.
Reboot completed via TWRP (all automatically)
SuperSu app then opened and seemed to work.
Rootchecker says: ROOTED!
WOOT! thanks a lot....
Now the question comes .. how do I get my Desire X to start using all its available memory eg SD car, and also how do I use priority access to get rid of default apps I never use?
PS I do appreciate the time you are taking to answer these questions!
Click to expand...
Click to collapse
Niceee, if you want to remove system apps (e.g. apps you don't use like teetr) then use titanium backup or root explorer, as far as extending memory (e.g. ram or internal memory) i don't think it's possible *Anyone who knows otherwise feel free to correct me*
I'm happy to help, as there were users ready to help me when i started.
plus: are you the guy that posted on the FB group about rooting and extending memory ?
Will_Xda said:
Niceee, if you want to remove system apps (e.g. apps you don't use like teetr) then use titanium backup or root explorer, as far as extending memory (e.g. ram or internal memory) i don't think it's possible *Anyone who knows otherwise feel free to correct me*
I'm happy to help, as there were users ready to help me when i started.
plus: are you the guy that posted on the FB group about rooting and extending memory ?
Click to expand...
Click to collapse
Yeah I have Titanium backup installed now and will work through the rubbish non used apps....
As for Facebook, no that wasnt me...
By the way, I have Android 4.1.1. on the phone as stock.
Do you think its worthwhile upgrading it (somehow?) to Android 4.3? Will that be more efficient and save battery better, and be more optimised? Or will it be more bloated and cane my phone more?
Opinions please....
In fact will flashing a different ROM actually include an upgrade to a different base droid OS?
Hello everybody,
I created a tool - initially for the nexus 9 (flounder|flounder_lte) - that gets rid of the ForceEncrypt flag in a generic way (meaning it should work no matter what rom you are on). It does that by patching the currently installed boot.img.
I enhanced that tool to make it work for nexus 6 (shamu) too.
Background
The Android CDD (Compatibility Definition Document) suggests that all devices SHOULD enable full disk-encryption (FDE) by default. Even though I support every step towards more security I have to criticize this approach. FDE comes at a price. Encryption takes time because some component has to de- and encrypt the stuff on the disk at some point and in the case of the nexus 6 (aka shamu) it's the CPU's task. Even though the nexus 6's CPU has 4 quite fast cores you can still easily feel the difference between FDE in the on- or off-state. The I/O is faster and boot-times take only half as long. (I did not do any measurements)
There is an ongoing discussion about this topic in cyanogenmod's gerrit for the nexus 9. Although it's a fun read it is pretty clear that this exchange of views is not going anywhere near a useful outcome.
Because performance is important to me and my tablet does not need the extra security I created the FED-Patcher (ForceEncrypt Disable Patcher)
How does it work?
FED-Patcher is a simple flashable ZIP that is supposed to be run in a recovery that has busybox integrated (like TWRP or CWM). This is what it does:
Checks if your device is compatible
Dumps the currently installed boot.img.
Unpacks the dump of your currently installed boot.img. The unpacking process is done via a self-compiled, statically linked version of unmkbootimg.
It patches the filesystem tables which include the force-encrypt flags. This process will change "forceencrypt" to "encryptable".
Then it patches the filesystem tables to not use dm-verity. This is done by removing the "verify" mount-parameter.
Creates a new boot.img. The unpacking process is done via a self-compiled, statically linked version of mkbootimg.
Flashes the modified boot.img
Supported devices
HTC Nexus 9 WiFi (flounder)
HTC Nexus 9 LTE (flounder_lte)
Motorola Nexus 6 (shamu)
Version History
v1 - Initial version with HTC Nexus 9 WiFi (flounder) support
v2 - Added Motorola Nexus 6 (shamu) support
v3 - Added support for HTC Nexus 9 LTE (flounder_lte)
v4 - Added support for signed boot-images
v5 - Changed error handling to compensate for missing fstab files. Some roms seem not to ship with the complete set of boot-files from AOSP.
v6 - FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
v7 - FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
What do I need to make this work?
A supported device (Your nexus 6)
An unlocked bootloader
An already installed ROM with forceencrypt flag. (like cyanogenmod CM12.1)
A recovery that includes busybox (TWRP, CWM)
How do I use it?
Make a thorough, conservative backup of your data if there is any on your device
Go into your recovery (TWRP, CWM)
Flash fed_patcher-signed.zip
If your device is already encrypted (You booted your ROM at least once) you need to do a full wipe to get rid of the encryption. This full wipe will clear all your data on your data-partition (where your apps as well as their settings are stored) as well as on your internal storage so please, do a backup before. If you don't do a backup and want to restore your data... well... Call obama.
How do I know if it worked?
Go into your "Settings"-App. In "Security", if it offers you to encrypt your device it is unencrypted. If it says something like "Device is encrypted" it indeed is encrypted.
IMPORTANT: If you update your ROM you have to run FED-Patcher again because ROM-updates also update the boot-partition which effectively removes my patch. So, if you are on CM12.1 for example and you used my patch and do an update to a newer nightly you have to run FED-Patcher again. If you don't do so Android will encrypt your device at the first boot.
Is it dangerous?
Well, I implemented tons of checks that prevent pretty much anything bad from happening. But, of course, we're dealing with the boot-partition here. Even though I tested FED-Patcher quite a lot there is still room for crap hitting the fan.
Screenshot
Scroll down to the attached thumbnails.
Credits
* pbatard for making (un)mkbootimg (dunno if he is on xda)
* @rovo89 for his xposed framework - I used some of his ideas by reading the source of his xposed installer flashable ZIP for FED-Patcher.
Thank you for this!
I can easily extend support for more devices. Do you guys know of some that have forceencrypt enabled?
Excellent work.
Hello everybody,
I just released version 6!
In this release, FED-Patcher will enforce the same structure for the patched boot.img that the original boot.img had. Additionally, the kernel commandline will also be taken over. This should fix pretty much every case where devices would not boot after patching.
Enjoy
Edit: Confirmed as working for latest Chroma build. (9/18)
Can anyone confirm this working for Chroma? Truly don't want to deal with starting from scratch ...
Hello everybody,
just to let you guys know - I just checked the new marshmallow factory image for shamu (MRA58K) => FED-Patcher should work for this new image too.
Enjoy!
This worked perfect for me just flashed then formatted data and boom I'm unencrypted again thank you op
Hello everybody,
I just released v7!
FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
Enjoy!
gladiac said:
Hello everybody,
I just released v7!
FED-Patcher will now disable dm-verity in fstab to get rid of the red error sign on marshmallow roms.
Enjoy!
Click to expand...
Click to collapse
This is incredible news! Using this alongside SuperSU, is R/W access accessible on the system partition? (build.prop mods)
spunks3 said:
This is incredible news! Using this alongside SuperSU, is R/W access accessible on the system partition? (build.prop mods)
Click to expand...
Click to collapse
Yes that should work!
//EDIT: No it does not. It keeps looping after installing SuperSU with the following error:
Code:
avc: denied { execute_no_trans } for path="/system/xbin/daemonsu" dev="mmcblk0p29" ino=104419 scontext=u:r:init:s0 tcontext=u:object_r:system_file:s0 tclass=file permissive=0
Probably some selinux problem :/. I might dive into this later this week. Sorry.
//EDIT #2: Now that I think about it... Doesn't the SuperSU flashable ZIP take care of the needed policy rules so the error that I posted above does not happen? IMHO it is SuperSU's task to take care of these things.
I might have to retest with the actual SuperSU installer. I had used TWRP's SuperSU installer. Maybe that one is broken somehow...
//EDIT #3: Nope! Supersu definitely does not work. I just tried with BETA-SuperSU-v2.50.zip. The SELinux policy-set that comes with the stock marshmallow factory images lacks the necessary rules to enable SuperSU to work.
However, adding these rules is something FED-Patcher was not designed to do. IMHO the SuperSU flashable ZIP should take care of this.
FYI: Nexus 6 is a QUAD core. Not just 2.
doitright said:
FYI: Nexus 6 is a QUAD core. Not just 2.
Click to expand...
Click to collapse
Thanks, I just fixed it. Shame on me.
Thanks for your work. Please can you take moment to answer my question? I am using an Android 6 ROM, however, due to my original configuration, device encryption is active.
I will try as listed below, please critique, I am not sure if I need to wipe the phone after backing up?
1. Back up device
2. Wipe device (data, internal storage and system.)
3. Flash FED patcher
4. Flash suitable Andriod 6 boot loader and radio
5. Flash suitable rom (with encryption disabled)
Thanks
finesse said:
Thanks for your work. Please can you take moment to answer my question? I am using an Android 6 ROM, however, due to my original configuration, device encryption is active.
I will try as listed below, please critique, I am not sure if I need to wipe the phone after backing up?
1. Back up device
2. Wipe device (data, internal storage and system.)
3. Flash FED patcher
4. Flash suitable Andriod 6 boot loader and radio
5. Flash suitable rom (with encryption disabled)
Thanks
Click to expand...
Click to collapse
Hi @finesse,
FED patcher must be run after installing a rom in order to disable the forced encryption flag. If the rom does not have forced encryption enabled (pretty common on non-stock and non-cm12.1 roms) you do not need to run FED patcher at all. Background: What FED-Patcher does is that it just takes the boot-partition of the currently installed rom and modifies it.
Wiping (in TWRP: "Wipe" - "Factory reset") is essential after backing up if the phone is currently encrypted. Sadly, you cannot simply just disable the encryption. Only formatting the partition (=wiping) will get rid of it.
I hope I could help .
Hey everybody!
This project has been moved to HERE! Please post your problems, success stories and so on there from now on.
Cheers, gladiac
Will this work on anyother device having Marshmallow... Its a MY6753 device.
or any way to edit you patch and make it work on my device....
gladiac said:
Hey everybody!
This project has been moved to HERE! Please post your problems, success stories and so on there from now on.
Cheers, gladiac
Click to expand...
Click to collapse
rawdealer said:
You didn't Format the Data It's quite a large button in twrp
Click to expand...
Click to collapse
Emilius said:
OMG, please don't tell anyone
Click to expand...
Click to collapse
rawdealer said:
FORMAT DATA, the extra large button
http://forum.xda-developers.com/and...v8-forceencrypt-disable-t3234422/post63810702
Click to expand...
Click to collapse
haibane said:
Rawdealer, I got it to work lol. Just seemed odd that you had to Format Data instead of doing a full wipe of everything. I'm guessing the Format Data just had to occur after CM was installed.
Click to expand...
Click to collapse
SamS1989 said:
it does not working on my n6 (7.1.1 stock)
what i do :
- flash 7.1.1 factory image
- turned off after the flash, reboot in fastboot
- boot twrp (without flash)
- flashed the V8 fed
- wipe data/cache (in twrp)
and after the reboot the phone stil decrypted
should i do the factory reset from settings or it's good from twrp ?
Click to expand...
Click to collapse
rewrite the instructions in both threads:
flash FED-Patcher.zip
use the Format Data button!!! neither Swipe to Factory Reset! nor Advanced Wipe!
v8 works well for nexus 6 stock 7.1.1, thanks to the op @gladiac and the discoverer @rawdealer, would better someone quote this in the other thread since New members (those with few posts) are not permitted to post to development-related forums
Bump
Thanks for this.
Does FED-Patcher still not work with Nougat?
I tried to use the detailed instructions here:
https://forum.xda-developers.com/nexus-6/general/how-to-disable-force-encryption-nexus-6-t3220273
I am not a pro at any of this, including TWRP.
I downloaded the Factory Image from Google (7.1.1 July for Shamu , Nexus 6)
https://dl.google.com/dl/android/aosp/shamu-n6f27h-factory-718e138f.zip?hl=vi
I unlocked and rooted my N6, flashed TWRP.
I followed all the instructions. When I got to step 8: Flash your ROM, it wouldn't work. I kept getting Zip verification errors in TWRP. I also tried to do it in NRT.
I was told that you can't install a Google factory image via TWRP. I guess the factory image would overwrite the recovery with stock. (my guess)
And when I used NRT, I got a hash mismatch when I tried to flash the factory image it as a ZIP.
NRT would only install the factory image via "Flash Stock and Unroot" which I guess defeats the purpose of this.
So I can go back to those instructions but am unclear which Android ROM to flash at step 8.
Is it possible to access files on internal HD partitions from Remix OS? I have Remix installed on a partition on my PC drive, but it doesn't seem to see other partitions on the same drive. Must they be mounted first and if so, how can I do this?
Just use app "stickmount" developed by Chainfire, you can find it in google play, after install it click on mount, just that
Sent from my GT-I8190 using Tapatalk
Unfortunately, StickMount isn't working for me. When I start it, it asks me to use SuperSU v1.93 or newer. Then, when I click on mount mass storage device, I get a message that the mount service is busy - try again in a few seconds. I can't get past that. I have SuperSU version 2.65. When I run that, it indicates that a binary needs to be updated. When I click on update ("normal"), I get an install window but it never finishes, and doesn't work after a reboot either. If I cancel the binary update, it doesn't seem to do anything. The Apps menu shows no apps are configured, but I have no idea how to configure them. Where to go from here?
trentfox said:
Unfortunately, StickMount isn't working for me. When I start it, it asks me to use SuperSU v1.93 or newer. Then, when I click on mount mass storage device, I get a message that the mount service is busy - try again in a few seconds. I can't get past that. I have SuperSU version 2.65. When I run that, it indicates that a binary needs to be updated. When I click on update ("normal"), I get an install window but it never finishes, and doesn't work after a reboot either. If I cancel the binary update, it doesn't seem to do anything. The Apps menu shows no apps are configured, but I have no idea how to configure them. Where to go from here?
Click to expand...
Click to collapse
Are you running remix from your internal hard drive?
What version of remix are you running? I recommend the pre-rooted/ gaps / busybox installed already
deskjet390 said:
Are you running remix from your internal hard drive?
What version of remix are you running? I recommend the pre-rooted/ gaps / busybox installed already
Click to expand...
Click to collapse
Version 201 from my internal SSD. However, I think it's academic now. I tried a rooting solution that has buggered up my installation. I don't see an easy way to recover, so I will be doing the installation from scratch; this time with the current version (202), which is supposed to be rooted. No serious harm done; it's only a beta and I'm just trying it out (and enjoying it).
trentfox said:
Version 201 from my internal SSD. However, I think it's academic now. I tried a rooting solution that has buggered up my installation. I don't see an easy way to recover, so I will be doing the installation from scratch; this time with the current version (202), which is supposed to be rooted. No serious harm done; it's only a beta and I'm just trying it out (and enjoying it).
Click to expand...
Click to collapse
Yes make sure you get the prerooted deodexed nicely hacked version. It has been tested and has proper root.
I am really interested to know if you can Mount a partition on the same drive you are installed on.
The way I was doing it was booting remix off of my flash drive and then using stickmount and I could hear my HD initiate when mounted.
deskjet390 said:
Yes make sure you get the prerooted deodexed nicely hacked version. It has been tested and has proper root.
....
Click to expand...
Click to collapse
Am I correct in assuming that this is what I downloaded from the Jibe website? It is identified as 2.0 202.
trentfox said:
Am I correct in assuming that this is what I downloaded from the Jibe website? It is identified as 2.0 202.
Click to expand...
Click to collapse
No its in another thread here.
http://forum.xda-developers.com/rem...pc-hacked-edition-ota-v2-0-201-t3345968/page1
You have to download it from there.
Jides version does not have play store and is odexed
Try this post: http://forum.xda-developers.com/remix/remix-os/access-partitionincluding-windows-remix-t3356700
You have to install the rooted version from here: http://forum.xda-developers.com/remix/remix-os/remix-os-pc-hacked-edition-ota-v2-0-201-t3345968
It doesn't matter on which drive the installation is. But it has to be rooted.
We're up and running now! Installed the hacked version, added Stickmount, and now I can see all my partitions. Fantastic!
I got my Honor 9 set up with the all in one guide (https://forum.xda-developers.com/honor-9/how-to/one-guide-recovery-os-roms-t3661829). Except I could not flash supersu because in the data/data folder, I just got some weird named folders and could not find my file.
That tells me I am encrypted, right?
Now I entered TWRP and sideloaded supersu via adb - and I got root. So now my question is, am I encrypted AND got root running? Can you confirm this? I found no way inside Android on how to see if I am actually encrypted or not.
I didn't flash anything with fileencryption disabled in fstab etc...
I believe the latest version of EMUI encrypts your device by default to protect your personal data. You would probably decrypt your device yourself in the Settings > Security
But how can I check if I'm really encrypted or decrypted? What I can tell for sure is that I got root. But that would mean that the root guide can be updated to read supersu is working with data encrypted
Rommco05, I already know that I'm definitely rooted, but unsure on how to check the encryption status.
If I remeber good, there's an option in settings when you encrypt the phone (I don't remember where exactly)
This may help you
Ok so I sideloaded beta SuperSU 2.82 SR3 and I am rooted now. And I would say encrypted as if I browse /data/data through TWRP everything is just a bunch of random characters. Also phone is locked by fingerprint and password.
It can be correct
Zuzler said:
I got my Honor 9 set up with the all in one guide (https://forum.xda-developers.com/honor-9/how-to/one-guide-recovery-os-roms-t3661829). Except I could not flash supersu because in the data/data folder, I just got some weird named folders and could not find my file.
That tells me I am encrypted, right?
Now I entered TWRP and sideloaded supersu via adb - and I got root. So now my question is, am I encrypted AND got root running? Can you confirm this? I found no way inside Android on how to see if I am actually encrypted or not.
I didn't flash anything with fileencryption disabled in fstab etc...
Click to expand...
Click to collapse
Could you please tell me what you did in detail after you unlocked your phone? At the moment i have the eu version but the b180 version with unlocked bootloader. Do you think it also works with the b180? And can you provide the links where you downloaded it, because there are like 10 Million different Versions of supersu and twrp. i bless you if you tell me
I soft bricked my H9 many times, so can you confirm me pls if :
- My H9 has the stock rom
- Bootloader unlocked and frp unlocked
- TWRP is installed but i see sdcard with encrypted names
If i used "adb sideload SuperSU-v2.82-201705271822.zip" in TWRP, i will have root and i loose nothing in the phone?
Thnaks for answer
i need this information too.
if i install by twrp the file SR3-SuperSU-v2.82-SR3-20170813133244.zip , i have root but i lose navigation button and camera flash...
now i have B183 version....
which version and how have to install Supersu for have root and all working?
im tired to go back everytime to b120....