Q&A for [How-To] Disable Forced Encryption on Nexus 9
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [How-To] Disable Forced Encryption on Nexus 9. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
You are awesome dude! I don't have enough posts so I have to post in the original post, I'll just send you my thanks here.
Some benchmarks
I can't post in the main thread, so maybe someone can post these findings up there?
All in all, it doesn't look like there's much overhead on the N9. I was actually hoping that there would be more of a difference to explain some of the baffling lag on the damn thing. My Nexus 6 saw HUGE differences once I ran it unencrypted.
(Encrypted results were snagged from AndroidPolice's article (whoops, can't post links either) on the N6. Because it didn't seem like it had much of an affect on performance, I restored the stock boot.img and ran the tests again after the encryption process completed. They're listed as Re-Encrypted below. Some odd results, but that can probably be attributed to the fact that I only ran the tests once (maybe twice).
4KB RW (MB/s)
AP - Encrypted - 3.14
Unencrypted - 3.12
Re-Encrypted - 4.33
256KB SR (MB/s)
AP - Encrypted - 39.4
Unencrypted - 40.55
Re-Encrypted - 39.48
4KB RR (MB/s)
AP - Encrypted - 18.41
Unencypted - 19.88
Re-Encrypted - 17.57
Are people seeing a better user experience doing this?
JustusIV said:
Are people seeing a better user experience doing this?
Click to expand...
Click to collapse
The difference hadn't been super noticeable except for some websites I visit that have a lot of dynamic data (comments) being MUCH faster.
atlharry said:
I can't post in the main thread, so maybe someone can post these findings up there?
All in all, it doesn't look like there's much overhead on the N9. I was actually hoping that there would be more of a difference to explain some of the baffling lag on the damn thing. My Nexus 6 saw HUGE differences once I ran it unencrypted.
(Encrypted results were snagged from AndroidPolice's article (whoops, can't post links either) on the N6. Because it didn't seem like it had much of an affect on performance, I restored the stock boot.img and ran the tests again after the encryption process completed. They're listed as Re-Encrypted below. Some odd results, but that can probably be attributed to the fact that I only ran the tests once (maybe twice).
4KB RW (MB/s)
AP - Encrypted - 3.14
Unencrypted - 3.12
Re-Encrypted - 4.33
256KB SR (MB/s)
AP - Encrypted - 39.4
Unencrypted - 40.55
Re-Encrypted - 39.48
4KB RR (MB/s)
AP - Encrypted - 18.41
Unencypted - 19.88
Re-Encrypted - 17.57
Click to expand...
Click to collapse
If we go technical
The nexus 9 most likely has an accelerator that uses our 64bit cpu which makes it faster
unlike the Nexus 6
Wanted to ask in the right place.
So I understand, I disable forced encryption and everything works as normal?
If there is an OTA update I need to NOT install it and wait for an img to be posted here on XDA. I then need to flash that image?
When I do that, I will lose any saved data on my device and have to re-setup the device?
Thanks,
-Jason
Jsunn said:
Wanted to ask in the right place.
So I understand, I disable forced encryption and everything works as normal?
If there is an OTA update I need to NOT install it and wait for an img to be posted here on XDA. I then need to flash that image?
When I do that, I will lose any saved data on my device and have to re-setup the device?
Thanks,
-Jason
Click to expand...
Click to collapse
At worst, you'll have to re-flash the original boot.img, adb sideload the update, then re-flash the no-encrypt boot.img. All without rebooting the device.
As far as i can tell though, since the N9 utilizes the HW cryptography module in the K1, it's not worth the effort since there really aren't any measurable gains. Not like it is with the N6.
atlharry said:
At worst, you'll have to re-flash the original boot.img, adb sideload the update, then re-flash the no-encrypt boot.img. All without rebooting the device.
As far as i can tell though, since the N9 utilizes the HW cryptography module in the K1, it's not worth the effort since there really aren't any measurable gains. Not like it is with the N6.
Click to expand...
Click to collapse
Oh, cool! That's cool! I didn't know that.
Getting a N9 in the next few days and plan on using adb and fastboot to unlock, root, install recovery, etc. At which point should I flash the unencrypted boot.img?
Still Encrypted
After flashing the modified boot and data reset Nexus 9 stills shows as encrypted under Security tab.
How to root after removing encryption?
Before I removed the forced encryption, I was rooted.
Now I see that root has been removed since removing forced encryption.
How do I reinstate root without re-encrypting my Nexus 9?
Neville Bailey said:
Before I removed the forced encryption, I was rooted.
Now I see that root has been removed since removing forced encryption.
How do I reinstate root without re-encrypting my Nexus 9?
Click to expand...
Click to collapse
The same way you rooted it before
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
The same way you rooted it before
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Which is what I did, but then the encryption was reinstated.
In bootloader, I flashed inject.img and patched.img and, after the tablet rebooted, it automatically encrypted the tablet.
Neville Bailey said:
Which is what I did, but then the encryption was reinstated.
In bootloader, I flashed inject.img and patched.img and, after the tablet rebooted, it automatically encrypted the tablet.
Click to expand...
Click to collapse
You dont flash the patched.img
Just flash a custom kernel
USBhost said:
You dont flash the patched.img
Just flash a custom kernel
Click to expand...
Click to collapse
Thank you - that did the trick!
Why need I close the forced encyption?
Disabling forced encryption with Nexus Root Toolkit not working on my Nexus 9
Hi everyone,
I wanted to disable the forced encryption in my Nexus 9 using the Nexus Root Tolkit v1.9.9. I succesfully installed all the drivers and apparently was able to unlock + root my device. However, when I try to disable the forced encryption the tool somehow isn't successful in flashing the new flashboot, and when the device reboots it is still encrypted.
Did anyone come accross this issue?
Thanks very much for your help!!
Thanks for the tip
could someone share the new img 5.0.1 without encryption? i could not download it from mega
Sent from my GT-N7000 using XDA Premium 4 mobile app
Related
I'm not responsible for anything blah blah
This is intended to disable forced encryption on the nexus 6. You can still encrypt the device after doing this, but it won't be automatically done.
After observing how this force encryption stuff works, I got it mostly figured out. (It's entirely a SW layer, as is already widely known). Basically when all the devices from fstab are mounted in android with the forceencrypt option, fs_mgr sets a flag for encryption (something like IF This_Device_Isnt_Encrypted; then This_Device_Needs_Encryption). on devices (looks like android only allows you to encrypt 1 device, which is probably to prevent such cases as over-resource usage ,maybe some other conflict that it doesn't support over 1 device, idk) that have forceencrypt set on them, if it can't unmount the device before doing these encryption checks - in other words if it's usy (like a file is open) - it just skips encryption all together. So if the device had a file preventing it from being unmounted, it just says "oh well, skip encryption." I found this kinda odd behavior anyway
You can still encrypt the device, it just isn't forced. Some people are complaining about the slowness of the encryption SW-layer (why force SW encryption? At least put some HW for it in the device). This makes it the way it probably should be - optional.
Stock LMY47D/LMY47E/LMY47M/LMY47I (5.1.0) - No force encrypt:
https://www.androidfilehost.com/?fid=95916177934540533
Stock LRX22C (5.0.1) - No force encrypt:
https://www.androidfilehost.com/?fid=95857557620392411
Stock LRX21O (5.0) - No force encrypt:
https://www.androidfilehost.com/?fid=95784891001613336
Prerequisites:
- You should be running the same build as the kernel you install (E.G. if you are running 5.1.0 LMY47D you should install the LM47D no force encrypt kernel)
- Your bootloader must be unlocked (fastboot oem unlock)
How-to install kernel:
1.) Reboot to boot loader
2.) Download the appropriate boot.img above
3.) Install it via fastboot (fastboot flash boot boot_noforceencrypt.img)
To disable forced encryption after kernel is installed:
1.) Reboot to boot loader
2.) Format userdata (fastboot format userdata) - This will erase all of your data (apps, sd card, etc.) - so make appropriate backups
Look who's back!! ?
Awesome work man... I'll be testing as soon as my whale arrives tomorrow.
*Also, hit me up on Hangouts... I might have something you'd be interested in. Mike is in, come December I think... Could be fun.
jjhiza said:
Look who's back!! ?
Awesome work man... I'll be testing as soon as my whale arrives tomorrow.
*Also, hit me up on Hangouts... I might have something you'd be interested in. Mike is in, come December I think... Could be fun.
Click to expand...
Click to collapse
Will do, I'm quite swamped in projects at the moment :laugh: Got one app I'm supposed to finish up by the 30th. Will I get the time, who knows
Damn it feels good to be back on a Nexus, with all the dev support. You did awesome things back with toro. I enjoyed my time with the Moto X, but the development forums were like a ghost town. Thank you for taking the time to do this, I will be trying it out tomorrow.
Ooo really interested in the read/write speeds between encrypted and non-encrypted!
And we're back! Nice work @bbedward!
bbedward said:
I'm not responsible for anything blah blah
I haven't tested this, because I don't have a nexus 6 at the moment. But this is a boot.img that (should) disable forced encryption. Rooted and non-rooted versions available.
What this does is disables forced encryption (and adds root, or not)
This isn't tested, but I'm fairly confident it will work after observing how this force encryption stuff works. Basically when all the devices from fstab are mounted in android, fs_mgr sets a flag for encryption on devices (up to 1 device I guess) that have forceencrypt set on them, if it can unmount the device or it isn't busy (if it can't it just goes on without encryption )
You can still encrypt the device, it just isn't forced. Some people are complaining about the slowness of the encryption SW-layer. This makes it the way it probably should be - optional.
Rooted (Chainfire) - no force encrypt:
https://www.androidfilehost.com/?fid=95784891001613334
Stock - No force encrypt:
https://www.androidfilehost.com/?fid=95784891001613336
Stock (in case these don't work for some reason you can just use this one to go back):
https://www.androidfilehost.com/?fid=95784891001613337
How-to:
1.) Reboot to boot loader
2.) Unlock device (fastboot oem unlock) - will wipe all data
3.) I think unlocking the device will automatically run encryption jobs, so don't do anything important because you'll need to factory reset again
4.) Download 1 of the above no force encrypt files (Chainfire rooted one, or stock one - up to you)
5.) Flash it in the bootloader (fastboot flash boot boot_noforceencrypt.img)
6.) If it works, factory reset the device and it should no longer be automatically encrypted (check in Settings -> Security)
7.) If it doesn't work, go back into the bootloader and flash the stock image.
Like I said, I don't have my own nexus 6 to test yet, but I'm just trying to help out.
Click to expand...
Click to collapse
flashed the rooted one after data wipe/factory reset trying to normal boot with this version i get an infinite loop of the chainfire auto root script running. flashed the noenforce version and was able to boot up fine but super su says no root. the encryption disable did work however.
purian23 said:
And we're back! Nice work @bbedward!
Click to expand...
Click to collapse
Affinity Nexus 6 ROM uploaded for flashing tomorrow?
djkinetic said:
flashed the rooted one after data wipe/factory reset trying to normal boot with this version i get an infinite loop of the chainfire auto root script running. flashed the noenforce version and was able to boot up fine but super su says no root.
Click to expand...
Click to collapse
I'm not sure how the chainfire stuff works entirely TBH. I saw in the thread over there people had it looping a few times before coming to.
You need to factory reset after flashing this, too. Which can be done with fastboot erase userdata.
Looks like, cf-auto root doesn't call "fastboot flash boot" just "fastboot boot" - is that a difference or is it the same thing?
djkinetic said:
flashed the rooted one after data wipe/factory reset trying to normal boot with this version i get an infinite loop of the chainfire auto root script running. flashed the noenforce version and was able to boot up fine but super su says no root. the encryption disable did work however.
Click to expand...
Click to collapse
What I'm sure everyone is dying to know is if you can run Androbench and report what the NAND scores are after disabling encryption.
bbedward said:
I'm not sure how the chainfire stuff works entirely TBH. I saw in the thread over there people had it looping a few times before coming to.
You need to factory reset after flashing this, too. Which can be done with fastboot erase userdata.
Looks like, cf-auto root doesn't call "fastboot flash boot" just "fastboot boot" - is that a difference or is it the same thing?
Click to expand...
Click to collapse
i ended up flashing noencrypt, then factory reset, then running cf root after a full reboot, end result encryption off and root with twrp =) life is good.
djkinetic said:
i ended up flashing noencrypt, then factory reset, then running cf root after a full reboot, end result encryption off and root with twrp =) life is good.
Click to expand...
Click to collapse
Looks like I misunderstood how CF-auto-root works. it just boots within the bootloader and does stuff. I'll update the OP
NeoteriX said:
What I'm sure everyone is dying to know is if you can run Androbench and report what the NAND scores are after disabling encryption.
Click to expand...
Click to collapse
Haha you just voiced what everyone lurking in this thread is hoping to see.
Thank you so much for this. Here are some quick I/O scores after disabling encryption.
http://imgur.com/DquRHEo
seoulstyle said:
Thank you so much for this. Here are some quick I/O scores after disabling encryption.
http://imgur.com/DquRHEo
Click to expand...
Click to collapse
For the lazy people, such as myself, is that an improvement?
cheami said:
For the lazy people, such as myself, is that an improvement?
Click to expand...
Click to collapse
Huge improvement. I didn't think to benchmark before, but here's some Nexus 5 scores with encryption enabled/disabled for comparison.
https://plus.google.com/+JeremyCamp1337/posts/iDyPjEuEf51
cheami said:
For the lazy people, such as myself, is that an improvement?
Click to expand...
Click to collapse
Huge improvement. Like, 5x better based on the benchmarks I've seen.
cheami said:
For the lazy people, such as myself, is that an improvement?
Click to expand...
Click to collapse
That looks like a vast improvement, faster than the note 4.
http://arstechnica.com/gadgets/2014...premium-price-still-comes-with-compromises/2/
Woot woot
Side question, if we flash this image to disable encryption, have root, and unlocked bootloader, will we still get the OTA updates?
aznalan15 said:
That looks like a vast improvement, faster than the note 4.
http://arstechnica.com/gadgets/2014...premium-price-still-comes-with-compromises/2/
Woot woot
Side question, if we flash this image to disable encryption, have root, and unlocked bootloader, will we still get the OTA updates?
Click to expand...
Click to collapse
I think so, but this boot.img would be overwritten after an OTA update so it'd turn back on the forced encryption (which would encrypt after the OTA rebooted/booted). You'd probably also lose root, assuming it formats /system.
cheami said:
For the lazy people, such as myself, is that an improvement?
Click to expand...
Click to collapse
http://i.imgur.com/XKDye36.jpg
This is someone's Androbench scores on a stock (encrypted) Nexus 6 for comparison. It's quite a lot better.
Q&A for [ROM] cm-11-20141216-UNOFFICIAL-thor
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] cm-11-20141216-UNOFFICIAL-thor. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
This is great news!! Hope somebody will release the 4.5.2 bootloader unlock or the right rooting method so that we can test this rom!.. I'ts nice to see people working on this kindle fire! Keep up the good work!:good:
xiloraptor said:
This is great news!! Hope somebody will release the 4.5.2 bootloader unlock or the right rooting method so that we can test this rom!.. I'ts nice to see people working on this kindle fire! Keep up the good work!:good:
Click to expand...
Click to collapse
Thanks ! The sooner should be a root method, crossing fingers
Is it possible to flash this from fully a rooted & safestrapped HDX Nexus 2.0.2. firmware?
Going Postal said:
Is it possible to flash this from fully a rooted & safestrapped HDX Nexus 2.0.2. firmware?
Click to expand...
Click to collapse
No.
i ve read this rom: cm-11-20141217-UNOFFICIAL-thor.zip on this topic: http://forum.xda-developers.com/kindle-fire-hdx/development/cm-11-20141216-unofficial-thor-t2974818
Cause my HDX have update automatically to FireOs 4.5.2 via wifi, then i have to wait for so long time, for any root version can apply for Fire OS 4.5.2, then use that rom, hopefully you guys can release that soon, thanks Cpasjuste, many thanks for your hardwork :good::good::good:
Dont try this ROM
Hi, I tried this ROM.
I am not on a late version of fire OS so I thought it would work - in actual fact I was on 13.3.2.4 with root access.
I now have a semi bricked kindle which just shows Amazon Kindle in white. As I have only owned the thing for a day this is somewhat gutting.
Any help anyone could offer would be appreciated.
I am getting a factory cable so will try to fix with that - if not a return is in order...
Avoid this mod like the plague...
Rob
buyaodanxin said:
Hi, I tried this ROM.
I am not on a late version of fire OS so I thought it would work - in actual fact I was on 13.3.2.4 with root access.
I now have a semi bricked kindle which just shows Amazon Kindle in white. As I have only owned the thing for a day this is somewhat gutting.
Any help anyone could offer would be appreciated.
I am getting a factory cable so will try to fix with that - if not a return is in order...
Avoid this mod like the plague...
Rob
Click to expand...
Click to collapse
Well the thread made it pretty clear...
Cpasjuste said:
There is currently a very few user which will be able to use it as you either need an unlocked bootloader or a root exploit for amazon firmware 4.5.2 (which will come someday...).
Click to expand...
Click to collapse
I am new to this - so didnt appreciate that I didnt have what the image said do you think a factory cable allow me to repair this or is it toast ?
EncryptedCurse said:
Well the thread made it pretty clear...
Click to expand...
Click to collapse
buyaodanxin said:
I am new to this - so didnt appreciate that I didnt have what the image said do you think a factory cable allow me to repair this or is it toast ?
Click to expand...
Click to collapse
How did you flash it?
D0ubl3_X said:
How did you flash it?
Click to expand...
Click to collapse
With Safestrap from Zip.
What I am guessing happened is safestrap was launched from initial bootloader - overflashed bits it shouldnt have now initial bootloader doesnt like what it sees so no booting...
Any suggestions appreciated.
That's strange. I didn't used safestrap since a while so I'm not 100% sure what happened but you probably flashed the ROM on your STOCK slot which probably erased safestrap... (Like said before you shouldn't have used this ROM in first place and you shouldn't flash to stock ROM).
The problem now is to get adb working so you can restore something but I guess it won't be enabled for you since your device do not boot the flashed kernel. I'm not sure if it will be possible to use fastboot for flashing a signed kernel made by @vortox , this is maybe your only solution.
Cpasjuste said:
That's strange. I didn't used safestrap since a while so I'm not 100% sure what happened but you probably flashed the ROM on your STOCK slot which probably erased safestrap... (Like said before you shouldn't have used this ROM in first place and you shouldn't flash to stock ROM).
The problem now is to get adb working so you can restore something but I guess it won't be enabled for you since your device do not boot the flashed kernel. I'm not sure if it will be possible to use fastboot for flashing a signed kernel made by @vortox , this is maybe your only solution.
Click to expand...
Click to collapse
I'm fairly certain that the boot image didn't flash, it's just the system that's not booting. I was reading through the bootloader source today and it *seems* that if the signature is invalid on a flashed partition, then the device will boot into fastboot mode. Had the boot image actually flashed, he would get a picture for about 2 seconds then a reboot. It wouldn't just hang if this was a sfv (signature verification failure, I decided to abbreviate because it's hell to type out).
r3pwn said:
I'm fairly certain that the boot image didn't flash, it's just the system that's not booting. I was reading through the bootloader source today and it *seems* that if the signature is invalid on a flashed partition, then the device will boot into fastboot mode. Had the boot image actually flashed, he would get a picture for about 2 seconds then a reboot. It wouldn't just hang if this was a sfv (signature verification failure, I decided to abbreviate because it's hell to type out).
Click to expand...
Click to collapse
Your right, the problem is now his system partition. With a few luck he still have adb enabled, I think its his last chance isn't it.
Can someone tell me what I need to do to move from the HDX ROM (Kernel .3.2.4) to this one?
Apollo Hartigan said:
Can someone tell me what I need to do to move from the HDX ROM (Kernel .3.2.4) to this one?
Click to expand...
Click to collapse
If I am not wrong:
Download the upload 13.3.1.0 update file from here: http://forum.xda-developers.com/showthread.php?t=2782159
Make a back-up of your data using Safestrap and copy it to your pc.
Flash one of the two backups files provided by ggow in http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 depending on device. That would install a stock version with root enabled (if not u would need to do the whole root process)
Do a factory reset of your system
Copy the 13.3.1.0 downloaded before into the root and reboot to get the update installed.
Once the system is in 13.3.1.0 u would be able to install the TRWP and later the cm.
Maybe i am missing something, can anybody confirm?
qkp said:
If I am not wrong:
Download the upload 13.3.1.0 update file from here: http://forum.xda-developers.com/showthread.php?t=2782159
Make a back-up of your data using Safestrap and copy it to your pc.
Flash one of the two backups files provided by ggow in http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 depending on device. That would install a stock version with root enabled (if not u would need to do the whole root process)
Do a factory reset of your system
Copy the 13.3.1.0 downloaded before into the root and reboot to get the update installed.
Once the system is in 13.3.1.0 u would be able to install the TRWP and later the cm.
Maybe i am missing something, can anybody confirm?
Click to expand...
Click to collapse
I can reply to myself. cm-11-20150101-UNOFFICIAL-thor.zip installed and running
I was in 13.3.2.4 with Safestrap, OTA updates disabled, root....
My steps:
1-Back up your data using Safestrap and copy it to your personal computer.
2-Select Stock rom.
3-Flash one of the two backups files provided by ggow in http://forum.xda-developers.com/kindle-fire-hdx/development/13-3-2-4-rollback-images-t2991015 depending on device (Thor in my case). That would install a stock version pointing to 13.3.0.9. In my case root was not found so I needed to use again [TOOL:FROZEN] Faznx's HDX ToolKit v0.95 to disable OTA and put root.
3-Put the http://forum.xda-developers.com/showthread.php?t=2782159 at root level. Reboot the device, that would help the system to recognize the update, sometimes it takes a while. Put also TRWP and the cyanogenmod, I put them into download folder, but it doesn't matter.
4-Update the system, it would require a reboot.
5-Once in 13.3.1.0, check OTA updates are disabled and root is enabled, using Faznx again.
6-With OTA updates disabled, switch on wifi and install a file manager.
7-Install Rashr, download it from http://forum.xda-developers.com/showthread.php?t=2334554
8-Install TRWP image using Rashr.
9-Reboot on TRWP. Swip to factory reset and install the CM build.
10-Install CM Gapps for CM11.
I have found an issue with wifi, it required a reboot to get it working. Testing the other features right now.
I would like to use the google now launcher but CM doesn't detect the launcher as launcher. Maybe it is an issue of my device. Can someone try to set the google now launcher as default launcher?
At first, thanks a lot to all involved people to making a great device gets its full potential. Great work.
As it works fine for me so far, I was wondering if it is necessary to keep all the partitions, I got an emulateed ( legacy and 0) as well as two others. I suppose, these are two from the other rom slots I created. Im not sure if they take space at all?
Again, thanks for your effort and cheers.
disTractoR said:
At first, thanks a lot to all involved people to making a great device gets its full potential. Great work.
As it works fine for me so far, I was wondering if it is necessary to keep all the partitions, I got an emulateed ( legacy and 0) as well as two others. I suppose, these are two from the other rom slots I created. Im not sure if they take space at all?
Again, thanks for your effort and cheers.
Click to expand...
Click to collapse
No you don't need to delete them they are symlink used by the system and do not use space.
From many many different threads and frankly confusing instructions I think I have puzzled together the following solid guideline for my kindle fire hdx from basic root to custom rom. Currently my firmware is 13.3.1.0.
Could someone take a look at this and tell me if I got this right or if I need to do stuff differently (or could do them better)? Don't assume that something is obvious, if it isn't written down, don't be shy to mention it. I would be ever so grateful .
Edit: I'm updating my experience as I move along the list and get more info just in case this might be useful to someone who is just as lost as I was in the beginning
Obligatory disclaimer: this is just a step-by-step guideline that worked for me. I'm not responsible if you chose to follow any of these steps and damage or brick your device.
Guideline:
-Download firmware version 3.2.3.2 and upgrade directly from any of the previous version by putting the file into the internal storage of the kindle, going to settings>device>system update on the kindle and installing the update from there.
-Root with Towelroot in the HDX toolkit downloaded from here (Edit: I got various error messages at this step but got it to work in the end. The 3rd post here shows what I did to get it working after getting error message 2 and 3 at various times)
-block OTA also with the tool in the HDX toolkit (is there a way to safely check that this worked? Edit: It worked )
-connect to wifi and install Flashify from the playstore (Edit: I ended up installing File Expert and flashify on another android device, backing up the flashify apk and sideloading it with ES File Explorer from the amazon app store to the kindle, I guess I could have also download the apk somewhere but I have trust issues.)
-download the img of TWRP 2.8.5.0. and put it in internal storage of kindle (had no problems)
-use flashify to save original stock recovery (had no problems)
-Use flashify to flash TWRP (had no problems)
- Boot into recovery mode via flashify to see if it worked (had no problems)
Now either A)
-download CM11 image and gapps and put the zip files on internal storage
-Edit: disconnect Kindle from USB afterwards
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- flash cm11 image and gapps (under install and then find them in the files)
- reboot
-Edit: I had the wifi not connecting problem that some people have with CM11 but a reboot took care of it.
-Edit 2: I couldn't get the kindle app to work on CM11 (it wouldn't synch my books, the device wasn't recognized by amazon and it would crash every time I logged in.) so I ended up replacing it with the Nexus rom. If the chance of this happening doesn't bother you then CM11 seems to still be a good choice.
or B)
- download HDX thor nexus rom and gapps and put the zip files on internal storage
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- Edit: disconnect Kindle from USB afterwards
- flash nexus rom and gapps (under install and then find them in the files)
- reboot
- Edit: I'm very happy with it, it works flawlessly. Since it's based on Jelly Bean I may try replacing it with another rom sometime in the future, but I'm in no hurry
Mostly correct, you can update directly to 3.2.3.2 no need for incremental steps. The only way to know if ota blocker worked is to check for update but there's really no need, as soon as you've run towel root just disable WiFi as it won't be needed anymore.
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
uhraman said:
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
Click to expand...
Click to collapse
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
derpadoodle said:
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
Click to expand...
Click to collapse
Thanks for your replies! Is the method uhraman hinted at the better one?
snorklm said:
Thanks for your replies! Is the method uhraman hinted at the better one?
Click to expand...
Click to collapse
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
derpadoodle said:
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
Click to expand...
Click to collapse
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
snorklm said:
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
Click to expand...
Click to collapse
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Davey126 said:
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Click to expand...
Click to collapse
Thanks for the sound advice, I will probably never feel comfortable enough for that , especially because I haven't achieved much at all yet. I haven't even flashed TWPR yet.
Yay, I did it. CM11 seems to be working as intended! Thanks again for everyone who replied and also to everyone who put so much work into making and improving all the tools and software necessary to make this kind of thing even possible, I appreciate it!
What firmware were you on to begin your process mate... ?
B3NJY said:
What firmware were you on to begin your process mate... ?
Click to expand...
Click to collapse
I was on 3.0.5 when I got the device. Amazon didn't upgrade the firmware at all before sending it out, then I upgraded to 13.3.2.3. Why do you ask?
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
snorklm said:
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
Click to expand...
Click to collapse
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Davey126 said:
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Click to expand...
Click to collapse
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
snorklm said:
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
Click to expand...
Click to collapse
Glad to hear everything is working well! My daily driver is on Nexus and I could not be happier. Everything works as it should. No need to unlock the bootloader unless you plan to do more modding. Enjoy your device!
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
johnwaters said:
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
Click to expand...
Click to collapse
Agreed, I was overwhelmed by all the different threads and possibilities at first. I ended up approaching it like any other research project for a paper or presentation and dumped every solid (and recent) piece of good advice into Evernote and sorting it out there. But writing and updating guides (especially with the fast development I have observed) would be a lot of work, I understand completely why no one would volunteer to do it and everybody would rather answer questions on a case by case basis.
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
dynein said:
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
Click to expand...
Click to collapse
First thing you want to do is block OTA (over the air updates) or your device may be upgraded by Amazon to a level that gives you less options. Suggest using HDX Toolkit (here) to both root and block OTA. Then install twrp (here). From there you can opt to replace Fire OS will several different roms including Nexus, CM11 or CM12.
Flashify is an app that allows flashing recovery and roms from from within Android vs adb or a recovery environment. You can grab it from the Play store or another market. It's a dangerous tool; use with extreme caution.
Be aware that any of the above actions, if executed incorrectly, can permanently brick your device with little/no hope of recovery (guess that's the definition of permanent). Read, read and read some more before taking any action. Be sure to keep WiFi off on your device until OTA is blocked to prevent auto-updates.
I am on 3.72 safestrap with TWRP 2.7.0.0. My system version is 13.3.1.0. I have noticed intermittent wifi problem. Sometime it drops connection for no reason, while my other devices keeps connected with no disconnection. Sometimes wifi got turned off for no reason, then back on moment later. Does anyone know what's going on? Is there any fix? Thanks.
Uhm, I do not believe safestrap is compatible with 13.3.1.0. That could be the issue.
Sent from my KFTHWI using Tapatalk
That particular firmware was always well-known for erratic Wi-Fi behavior.. My advice if you are actually on that firmware . Is to unlock your boot loader and flash
Newer firmware version . That way with an unlocked Loader we can flash any modified update and assume the benefits without being locked . You're then able to revert back to any firmware that you preferred . Or flash and android ASOP if you run out of interest in your Amazon account .
I personally have not run the actual unlock on my 7 inch or -8.9 . But my 7 inch is running the modified recovery that bypasses the boot loader checks .http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004 and then somewhere in there he actually has a stock 4.5.2 stock img that can be flashed in your new recovery . That is what I am running with gapps installed and seems to run quite smoothly with no Wi-Fi drops
Why are you posting this question when issues with your current config (including wifi problems) and paths forward (plural) have been posted here: http://forum.xda-developers.com/showpost.php?p=59741324&postcount=105
Come on mate, stop wasting people's time. Update or accept the limitations of your config as-is.
Davey126 said:
Why are you posting this question when issues with your current config (including wifi problems) and paths forward (plural) have been posted here: http://forum.xda-developers.com/showpost.php?p=59741324&postcount=105
Come on mate, stop wasting people's time. Update or accept the limitations of your config as-is.
Click to expand...
Click to collapse
Davey, I really appreciate your help in the Nexus rom thread. I respect your expertise and willingness to help other people. But this OP, if you have read it, is asking for a possible fix for the wifi problem of 3.1.0. It has nothing to do with Nexus rom. So i think it's appropriate to ask seperately.
jimyv said:
That particular firmware was always well-known for erratic Wi-Fi behavior.. My advice if you are actually on that firmware . Is to unlock your boot loader and flash
Newer firmware version . That way with an unlocked Loader we can flash any modified update and assume the benefits without being locked . You're then able to revert back to any firmware that you preferred . Or flash and android ASOP if you run out of interest in your Amazon account .
I personally have not run the actual unlock on my 7 inch or -8.9 . But my 7 inch is running the modified recovery that bypasses the boot loader checks .http://forum.xda-developers.com/kindle-fire-hdx/development/recovery-twrp-2-8-1-0-thor-t2986004 and then somewhere in there he actually has a stock 4.5.2 stock img that can be flashed in your new recovery . That is what I am running with gapps installed and seems to run quite smoothly with no Wi-Fi drops
Click to expand...
Click to collapse
Thanks, jimyv. It looks like there isn't a fix for the wifi problem if i stay with 3.1.0. Thanks for pointing me to the TWRP thread. My further qurstions will be asked in the TWRP thread.
yichen382 said:
Davey, I really appreciate your help in the Nexus rom thread. I respect your expertise and willingness to help other people. But this OP, if you have read it, is asking for a possible fix for the wifi problem of 3.1.0. It has nothing to do with Nexus rom. So i think it's appropriate to ask seperately.
Click to expand...
Click to collapse
@yichen, I appreciate your thoughtful response and apologize for the gruff post. I did read the OP but failed to explain the common roots behind your WiFi issue. In most cases the low level interface (hw drivers; binaries) remain the same regardless of which rom you are running. They are supplied by Amazon and are consistent with the base firmware level on your device. Sometimes code from other releases can be substituted and the really talented/adventurous developer may attempt to modify if source is available. It this case the easiest/best solution is to upgrade the base firmware as Amazon fixed many of the problems in 3.2.x and made further refinements in 3.2.5/3.2.6 . Hope that helps.
Thanks Davey. As always, your post is informational and easy to understand. You are the best.
Finally, I am able to get away from the buggy 3.1.0 stock firmware and now I am running CM11. Much thanks to Davey who helped me greatly along the way, also jimvy who clarified things for me. I want share my steps so if anyone in similar situation can take a reference:
1. Deleted slots in safestrap. Leave only stock slot.
2. Uninstalled safestrap in safestrap app.
3. Flahed twrp 2.8.5 using Flashify.
4. Upgraded bootloader to 3.2.3 in twrp.
5. Full wipe in twrp.
6. Flash CM11.
Now i am sitting comfortably at 3.2.3 which is just below 3.2.4. Thank you again Davey. People like you made this forum so great.
yichen382 said:
Finally, I am able to get away from the buggy 3.1.0 stock firmware and now I am running CM11. Much thanks to Davey who helped me greatly along the way, also jimvy who clarified things for me. I want share my steps so if anyone in similar situation can take a reference:
1. Deleted slots in safestrap. Leave only stock slot.
2. Uninstalled safestrap in safestrap app.
3. Flahed twrp 2.8.5 using Flashify.
4. Upgraded bootloader to 3.2.3 in twrp.
5. Full wipe in twrp.
6. Flash CM11.
Now i am sitting comfortably at 3.2.3 which is just below 3.2.4. Thank you again Davey. People like you made this forum so great.
Click to expand...
Click to collapse
Glad all is well! As for assistance, the participants in this forum are great. Much of what you read are the aggregated outputs from small number of talented developers and average users like you who are willing to share their experiences. That's how 'stuff' gets done.
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.