Related
Update5: 4.5.5 is out, and there is no reason NOT to update to 4.5.5. Please use the newer 4.5.5 upgrade instructions in the link below :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
Another alternative is Lollipop:
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
And these are the earlier (original) 4.5.x upgrade instructions which require modifying the Amazon update file:
Update4: For users with low computer proficiency (a.k.a "newbies"), DoLooper has written a post trying to make the instructions most accessible :
http://forum.xda-developers.com/showpost.php?p=61832754&postcount=10
If you still have questions after that, post here!
Update3: I've uploaded the 4.5.4 update file to Dropbox, now everything is super simple and you can skip steps 1)-4):
https://www.dropbox.com/s/17ngnhmvnkh1cpx/twrp_ready_update-kindle-20.4.5.4_user_454006120.zip?dl=0
md5sum : ab9468126ee7d7ff0b1c38a96313ef20
Use at your own risk (it works for me!)
If the procedure works for you, don't forget to click "Thanks"
Update2: Thanks to DoLooper, this has been established as the simplest and quickest way to get full GAPPS working. The instructions are simplified further to incorporate suggestions.
Update: Looks like the procedure worked for several people, but there is a single pitfall which appears to be common. I added some additional instructions below in red.
### Original post
I am making a separate topic out of this. Tested this yesterday, going from 4.5.2 to 4.5.4
What you need to have before you proceed : unlocked bootloader (according to reports, not really needed, skip), TWRP and rooted FireOS (4.5.3 or below). Also, download jmz tool to somewhere (can skip this too), and SuperSu flashable zip.
Important: If you have anything other than 4.5.3 right now, I recommend that you flash the 4.5.3 bootloader separately first before doing any updating business. I've attached the flashable zip with 4.5.3 bootloader as well (uboot*zip). The other bootloaders are very risky !!! 4.5.1 and 4.5.2 will not let you into TWRP by the "power" and "vol+" button push if you screw up !!!
0) If you used JMZ tool for GAPPS install or did a manual update prevention, clean up GAPPS update blockers by deleting the following dirs in /data/app (this will make your life easier later on!):
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
1) Download the latest 20-4.5.4 update to a PC ( https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin ), rename *bin to *zip, unpack, and replace the attached "updater-script" below in 20-4.5.4/META-INF/com/google/android/updater-script
2) Delete the following directories/files :
a) here you remove stuff you will not flash
20-4.5.4/recovery
20-4.5.4/images
b) here you will remove files to make room in /system to flash bigger GAPPS
20-4.5.4/system/priv-app/com.amazon.weather.apk
20-4.5.4/system/priv-app/moffice_6.0.1_default_en00105_multidex_195423.apk
20-4.5.4/system/priv-app/com.amazon.geo.client.maps.apk
(can delete more if you need space in /system and know what is useless, and a few things could just be moved to /data/app with no issues)
3)Rename (just in case, this will make OTA blocked):
20-4.5.4/system/priv-app/DeviceSoftwareOTA.apk to *apk_
4) Zip everything into update.zip. Make sure the paths in zip are the same as in the original 4.5.4 update from Amazon (QC this carefully!). Put the zip on a USB stick with FAT (if you have an OTG cable). Alternatively, upload it to the device somewhere to the Download folder
Possible pitfall: When you create your update.zip, look into it!!! It should have {system,boot.img,etc} right at the top level, just like the original Amazon update. If you have {yourpath/system, yourpath/boot.img,etc}, you need to re-zip and make sure that "yourpath" is removed.
5) Boot into TWRP, and flash the 4.5.3 bootloader. Reboot. Skip if you already have 4.5.3
6) Boot into TWRP, and flash update.zip from 4) . Then immediately after flash supersu.zip ( https://download.chainfire.eu/396/supersu/ ). Reboot to FireOS. If you choose not to flash supersu.zip here, before you reboot TWRP, it will ask you to root the device, say yes (leaving hooks for later root)
7) Re-boot to TWRP, flash a GAPPS package, such as Pico (Uni) GAPPS for KitKat ( http://www.androidrootz.com/2015/03/download-android-44x-kitkat-pa-gapps.html ). Wipe dalvik/cache and reboot to FireOS (Note: The free room in /system is still kind of limited, either remove more stuff in Step 2), or go with the smaller GAPPS. If you download my update package, you'll probably have about ~140 Mb of room in /system for GAPPS). Wipe dalvik/cache, reboot.
8) In FireOS, install jmz tool, and do small tweaks. Important, installing GAPPS via this tool is obsolete !!! Don't do it!!!. Alternatively, skip this tool, and just do it manually or via the scripts, as per here :
http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
The lockscreen ads can be reversibly blocked via this adb command :
adb shell su -c "pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.LockscreenUpdateS ervice"
(as per DoLooper's suggestion)
P.S. 4.5.4 allows the latest GAPPS to work fine, so they will update themselves over time, let them. No need anymore to keep Google Play Services at 7.0.99
kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin
link to 4.5.4.
nevermind figured it out, was being dumb and right clicking send to zip on the folder instead of adding the files to a zip
bibikalka said:
4) Zip everything into update.zip, and put it on a USB stick with FAT. Make sure the paths in zip are the same as in the original 4.5.4 update from Amazon.
Click to expand...
Click to collapse
You must use USB stick? . . .
. . . so must connect USB stick with OTG cable for step 6?
6) Boot into TWRP, and flash update.zip from 4) . Say yes when it offers to root the device.
Click to expand...
Click to collapse
I'm on rooted 4.5.3 with unlocked bootloader. Will install TWRP.
Haven't done anything like this before. Why not put update.zip in /system and flash from there? Thanks.
DoLooper said:
You must use USB stick? . . .
. . . so must connect USB stick with OTG cable for step 6?
I'm on rooted 4.5.3 with unlocked bootloader. Will install TWRP.
Haven't done anything like this before. Why not put update.zip in /system and flash from there? Thanks.
Click to expand...
Click to collapse
Sorry, I was not clear enough. Indeed, you can put this zip into the internal memory, but not /system (it'll get formatted). Instead, place it into the "Download" folder or something.
Just got done. Everything worked great. I did have to sideload SuperSu and Busybox manually though, but everything is working fine. Thank you.
With an easy way to recover (just re-install 4.5.4), I've been playing with various Xposed modules.
So far has not seen anything very attractive, and most of the system tweaks via Xposed modules don't seem to work.
Easy update 4.5.3 to 4.5.4 -- and working Gapps!!!
Very slick--thanks a lot! Finally, all Gapps updated and working perfectly!
FWIW, I wasn't prompted to root, which i guess I wouldn't be...didn't you say somewhere that root is preserved during 4.5.3 to 4.5.4 update? (Yeah, I'm still properly rooted.)
Gapps: Since JMZ's tool creates the dummy dirs you mentioned, which prevent play services and store from updating, I installed this Gapps minimal edition instead. Just uninstalled play store first--kept G+, hangouts and Gmail (although it never worked before)--and let play services update. Now everything is running great. :laugh:
DoLooper said:
Very slick--thanks a lot! Finally, all Gapps updated and working perfectly!
FWIW, I wasn't prompted to root, which i guess I wouldn't be...didn't you say somewhere that root is preserved during 4.5.3 to 4.5.4 update? (Yeah, I'm still properly rooted.)
Click to expand...
Click to collapse
Good to hear that you finally did it!
The update formats /system, so nothing survives there. But you could have had supersu in /data/app before, and that survived. You probably did root when TWRP asked about it right after the update? I think SuperSu needs something installed in /system to work properly, and that's what TWRP does.
DoLooper said:
Gapps: Since JMZ's tool creates the dummy dirs you mentioned, which prevent play services and store from updating, I installed this Gapps minimal edition instead. Just uninstalled play store first--kept G+, hangouts and Gmail (although it never worked before)--and let play services update. Now everything is running great. :laugh:
Click to expand...
Click to collapse
So you did not use JMZ's tool to install GAPPS at all? Did you just flash the minimal edition you've linked to in TWRP, and it worked? That'd be really neat if GAPPS could be flashed via recovery, just like in any other Android version. Btw, the latest Play Services provide correct positioning to Google Maps, so now it finds me on the map.
bibikalka said:
The update formats /system, so nothing survives there . . . You probably did root when TWRP asked about it right after the update?
Click to expand...
Click to collapse
If it were the least bit possible that I didn't get the root prompt, I would swear I didn't get it. I think, however, I left the tablet briefly while update.zip finished flashing. Any chance TWRP only gives you a minute or two to respond to root prompt, then defaults to yes?
Notes I took during update:
"Modified 4.5.4 update.zip installed successfully but i wasn't prompted to root. (see in twrp: HOME, WIPE CACHE, REBOOT SYSTEM) Went back to twrp HOME and flashed SUPERSU.ZIP - got success.
REBOOT."
Click to expand...
Click to collapse
That "see in twrp" is what i saw on screen after "success" with update.zip install. If TWRP always prompts to root and doesn't default to yes when there's no response, I must have done this step and will call a neurologist tomorrow. )
bibikalka said:
So you did not use JMZ's tool to install GAPPS at all? Did you just flash the minimal edition you've linked to in TWRP, and it worked?"
Click to expand...
Click to collapse
Exactly!
Couple last things:
1. Unlocked bootloader: You say unlocked bootloader required (and mine is), but JMZ shut down his thread. I assumed that was because TWRP could be installed without unlocking. Is that correct? If so, is unlocked bootloader really required to do this or is it only necessary to have TWRP?
2. Gapps: Hope you will have users install that minimal gapps. If they use JMZ's tool, to get updated play services and store they have to undo his fixes that make old Gapps work. With minimal package the store just updates itself to current version and prompts to update play services. No fuss.
3. Step 7 says "reboot to TWRP." This implies tablet reboots (or user is suppose to reboot) after "saying yes to root." Perhaps the reboot should be added? (But FWIW: Because I didn't see root prompt I flashed supersu right after flashing update, then rebooted.)
DoLooper said:
Very slick--thanks a lot! Finally, all Gapps updated and working perfectly!
...... I installed this Gapps minimal edition instead. ......
Click to expand...
Click to collapse
Thank you a million times for this. I'm on 4.5.4 rooted, and was having a horrible time getting gmail to work. I finally uninstalled framework, services, and playstore from that JMZ tool thing and gave this a shot. Gmail works great now. Only having one issue so far. On Google Play Movies, the movies and shows won't stream. They only play if downloaded first.
DoLooper said:
Notes I took during update:
"Modified 4.5.4 update.zip installed successfully but i wasn't prompted to root. (see in twrp: HOME, WIPE CACHE, REBOOT SYSTEM) Went back to twrp HOME and flashed SUPERSU.ZIP - got success.
REBOOT."
Click to expand...
Click to collapse
OK, no mystery then! And a good catch! It looks like update.zip can be safely followed by Supersu.zip, without any reboots. Supersu.zip will flash everything that's needed to have root, so TWRP does not ask for anything when you reboot the device.
DoLooper said:
Couple last things:
1. Unlocked bootloader: You say unlocked bootloader required (and mine is), but JMZ shut down his thread. I assumed that was because TWRP could be installed without unlocking. Is that correct? If so, is unlocked bootloader really required to do this or is it only necessary to have TWRP?
Click to expand...
Click to collapse
I agree, perhaps TWRP can be flashed and will work without any unlock, but I am just too lazy to test this. Do we have a confirmation for this one? I would update instructions accordingly if this is true.
DoLooper said:
2. Gapps: Hope you will have users install that minimal gapps. If they use JMZ's tool, to get updated play services and store they have to undo his fixes that make old Gapps work. With minimal package the store just updates itself to current version and prompts to update play services. No fuss.
Click to expand...
Click to collapse
Another good catch! I was not thinking about this when I wrote the original post, but having GAPPS flash properly is a pretty big deal! I may re-apply update.zip, and try the GAPPS flash, to see if it is indeed so simple.
Did you boot to FireOS after update.zip/supersu.zip, and then rebooted to TWRP, and flashed GAPPS? Or did you go straight from update.zip to supersu.zip to gapps flash, without the FireOS boot ?
DoLooper said:
3. Step 7 says "reboot to TWRP." This implies tablet reboots (or user is suppose to reboot) after "saying yes to root." Perhaps the reboot should be added? (But FWIW: Because I didn't see root prompt I flashed supersu right after flashing update, then rebooted.)
Click to expand...
Click to collapse
As above, supersu.zip flash right away is a nice simplification!
Overall, great help! And the big deal is that GAPPS are easy to flash, work fully, and require no messing around with anything else. This makes flashing 4.5.4 with GAPPS into the fastest way to get fully working GAPPS on this device !!!
Will I have to do anything special to undo the changes I made that blocked play store and services updates?
Thanks for working on this, having fully working play store will be great.
TWRP flashed fine for me without an unlocked bootloader, I already used it to make a backup.
lynnux said:
Will I have to do anything special to undo the changes I made that blocked play store and services updates?
Thanks for working on this, having fully working play store will be great.
TWRP flashed fine for me without an unlocked bootloader, I already used it to make a backup.
Click to expand...
Click to collapse
Good question ... At most you'll have to delete a couple of dummy directories in /data/app, one for the play store, and the 2nd one for the play services which prevented the updates. But perhaps the GAPPS zip will remove those itself ... Why don't you try, and post ?
lynnux said:
Will I have to do anything special to undo the changes I made that blocked play store and services updates?
Click to expand...
Click to collapse
It depends on what changes you made. Before I flashed update.zip, I did what @bibikalka suggests and found and deleted the following dirs in \data\app :
com.android.vending-1.apk
com.android.vending-2.apk
com.google.android.gms-1.apk
com.google.android.gms-2.apk
After update and before installing Gapps I searched /system for anything "google." Only found "widevine" and left it.
If you installed Gapps per the original root post, you gave this command:
pm grant com.google.android.gms android.permission.INTERACT_ACROSS_USERS
I don't know what this does. Shell command effects seem to be preserved with update, though, so would be worth finding out.
---------- Post added at 12:44 PM ---------- Previous post was at 12:23 PM ----------
bibikalka said:
OK, no mystery then! And a good catch! It looks like update.zip can be safely followed by Supersu.zip, without any reboots. Supersu.zip will flash everything that's needed to have root, so TWRP does not ask for anything when you reboot the device.
Did you boot to FireOS after update.zip/supersu.zip, and then rebooted to TWRP, and flashed GAPPS? Or did you go straight from update.zip to supersu.zip to gapps flash, without the FireOS boot ?
Click to expand...
Click to collapse
Exact steps I did:
Flash update.zip, press TWRP "Home," flash Supersu zip, reboot to system.
Go back to TWRP and flash Gapps zip, wipe cache (per instructions at minimal Gapps page), reboot to system.
FWIW, when rebooted after wipe, I got "updating" message again and it took awhile but all was fine.
4.5.4 Update bin: https://kindle-fire-updates.s3.amazonaws.com/update-kindle-20.4.5.4_user_454006120.bin (Fire HD 6 and 7 use identical files)
superSU zip: https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Gapps minimal: http://forum.xda-developers.com/showthread.php?t=2779598
I know this is basic, but how exactly do I do step 1? In root explorer or es file manager I can't figure out how to 'replace' the original update script with the one you've attached. These obviously don't work like regular files.
lynnux said:
I know this is basic, but how exactly do I do step 1? In root explorer or es file manager I can't figure out how to 'replace' the original update script with the one you've attached. These obviously don't work like regular files.
Click to expand...
Click to collapse
Download the update in a .bin file and extract (I use 7zip). Once extracted it makes a ton more sense.
lynnux said:
I know this is basic, but how exactly do I do step 1? In root explorer or es file manager I can't figure out how to 'replace' the original update script with the one you've attached. These obviously don't work like regular files.
Click to expand...
Click to collapse
ugcbrian said:
Download the update in a .bin file and extract (I use 7zip). Once extracted it makes a ton more sense.
Click to expand...
Click to collapse
Right. You do steps 1-4 on the computer. See my post above for link to the update bin file.
DoLooper said:
Right. You do steps 1-4 on the computer. See my post above for link to the update bin file.
Click to expand...
Click to collapse
Thanks. I was renaming as a .zip, but trying to make the replacement on the tablet. Since I'm using a linux laptop, I suppose I'll have to rename it as a tar or gz file to work with it there, since linux doesn't do .zips.
lynnux said:
Thanks. I was renaming as a .zip, but trying to make the replacement on the tablet. Since I'm using a linux laptop, I suppose I'll have to rename it as a tar or gz file to work with it there, since linux doesn't do .zips.
Click to expand...
Click to collapse
Okay, if you have to rename the bin file in order to extract the contents, do that. (Maybe double-click will work.) You will see the files and dirs that bibikalka's instructions refer to (excluding the "20-4.5.4," which is just for reference). After doing changes per instructions, make a compressed file named "update" containing what's left (see below). Since the extension will be tar or gz, rename it to "zip" and copy or move it to the Fire's download folder, then do step 6 (assuming you're on 4.5.3).
Your compressed file should contain:
[dir] META-INF
[dir] system
[dir] tools
boot.img
file_contexts
ota.prop
Searched XDA high and low but there is no trace of rooting ASUS Z380KL. Is it possible? May be some universal rooting tool will help?
Managed to get it rooted with kingroot. You can find the app on XDA.
Unfortunately, still no access to /system, /data, etc with any root capable file manager. They don't even ask for root permissions.
I'm afraid at this moment rooting Z380KL with KingRoot is just a fiction.
I could get root.
A China user found that a phone boot used by C8817D twrp recovery (=tmp.img).
And I added a script of a part of daemonsu.
download: <filedropper>/z380klrootkit
If there is a problem, please correct by yourself
-- temp root --
step 1. adb reboot bootloader
step 2. fastboot boot tmp.img
If a phone was waiting, you install a fastboot driver to your PC.
step 3. It's OK to stall when displaying ASUS logo.
Then, you confirm to connect to adb(type "adb shell"). this is temp-root environment.
If you didn't connect adb, you install a adb driver to your PC.
step 4. I recommend to back up a system partition by dd.
-- root --
step 1. Get ready to temp-root environment.
step 2. Execute "root.bat"
step 3. If you didn't restarts or didn't got root.
Check root.sh at temp-root or retry from backed up a system image.
-- unroot --
It's the condition to be able to become root.
This remove all files for root.
step 1. Get ready to temp-root environment.
step 2. Execute "unroot.bat"
Good luck:good:
You can actually get access to /system /data with kingroot,and no computer at all.
All you need to do is to switch to SuperSU from Kingroot.
There is a guide to do it with an app.
Could you get root by kingroot? I failed to get root by it.
Please tell me a version of kingroot.
backwardastep said:
Could you get root by kingroot? I failed to get root by it.
Please tell me a version of kingroot.
Click to expand...
Click to collapse
I have got root access on my Z380KL using the KingRoot app available in their official thread (v4.1)
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
After rooting the tab, if you want to use SuperSU instead of KingUser, you can follow the instructions in this thread to replace KingUser with SuperSU. Works perfectly fine and I now have root with SuperSU.
http://forum.xda-developers.com/xperia-z/general/super-su-xperia-device-lollipop-easy-t3119006
or better still, search for "replace kingroot with supersu w0lfdroid" in google and follow the instruction from the replace w0lfdroid website
Thank you for information.
I think it's safety way. I'll check it.
Then I wish I install a other recovery for xposed
backwardastep said:
Thank you for information.
I think it's safety way. I'll check it.
Then I wish I install a other recovery for xposed
Click to expand...
Click to collapse
I haven't found a recovery for the Z380KL yet
gladson1976 said:
I haven't found a recovery for the Z380KL yet
Click to expand...
Click to collapse
Goto here : TWRP_2.7.7_v2_Z380KL.img
Renix63 said:
Goto here : TWRP_2.7.7_v2_Z380KL.img
Click to expand...
Click to collapse
Thank you. Will check it out today
Bump
Renix63 said:
Goto here : TWRP_2.7.7_v2_Z380KL.img
Click to expand...
Click to collapse
Mirror: https://mega.nz/#!JAd1BQ6a!13mLUG4YWpuiC-8gWshKs0YOPrfimNq7sTr5bp9Ln1M
Link's dead so I had to go through a Vietnamese (pay-to-download) website and wait like 10 mins before it started downloading. Feels like my browser has a virus now lol, that site was so shady.
Unfortunately my device (Asus Zenpad 8.0 Z380KL) doesn't boot after trying to replace Kinguser-App to another SU-App. Now it stucks in a bootloop and I want to flash it. I downloaded the Firmware from Asus (WW because on device is a WW Firmware).
I copied the Zip to Sd-Card and started the device with “Volume up”. I clicked "Enter SD down mode", then the device shows another screen shortly and vibrates.
So I tried another way with ASUS Flash Tool v1.0.0.14. Unfortunately I can't select Z380KL as model. I tried with Z370 with connected device. But there is a an "Unzip image failure".
Can somebody help me flashing the firmware on the device?
Try russian forum
https://translate.googleusercontent...t=1120&usg=ALkJrhjDpGwBjJ2V5NjKi26YSfkPamx-dg
Jessi H. said:
Unfortunately my device (Asus Zenpad 8.0 Z380KL) doesn't boot after trying to replace Kinguser-App to another SU-App. Now it stucks in a bootloop and I want to flash it. I downloaded the Firmware from Asus (WW because on device is a WW Firmware).
I copied the Zip to Sd-Card and started the device with “Volume up”. I clicked "Enter SD down mode", then the device shows another screen shortly and vibrates.
So I tried another way with ASUS Flash Tool v1.0.0.14. Unfortunately I can't select Z380KL as model. I tried with Z370 with connected device. But there is a an "Unzip image failure".
Can somebody help me flashing the firmware on the device?
Click to expand...
Click to collapse
yes
Jessi H. said:
Unfortunately my device (Asus Zenpad 8.0 Z380KL) doesn't boot after trying to replace Kinguser-App to another SU-App. Now it stucks in a bootloop and I want to flash it. I downloaded the Firmware from Asus (WW because on device is a WW Firmware).
I copied the Zip to Sd-Card and started the device with “Volume up”. I clicked "Enter SD down mode", then the device shows another screen shortly and vibrates.
So I tried another way with ASUS Flash Tool v1.0.0.14. Unfortunately I can't select Z380KL as model. I tried with Z370 with connected device. But there is a an "Unzip image failure".
Can somebody help me flashing the firmware on the device?
Click to expand...
Click to collapse
I had the same issue.
SOLVED : http://forum.xda-developers.com/android/help/asus-zenpad-8-0-z380kl-bootloop-t3373051/post66714396#post66714396
Upgraded the Z380KL to official Marshmallow today (https://www.asus.com/support/Download/51/1/0/7/GVdbbhmVKFr91qyj/32/).
KingRoot failed to root the firmware but was able to flash the SuperSU through TWRP.
Copy the SuperSU update zip and TWRP recovery image to sdcard
1. Restart to bootloader mode (Volume Up and Power)
2. Connect the phone and fastboot to TWRP (do not flash TWRP)
(fastboot boot <twrp image>)
3. Install the SuperSU update zip from TWRP (you have root access now)
4. Install the TWRP image from inside TWRP (select Install and change the install zip option to install image). Select the TWRP image from sdcard.
Got official Marshmallow, TWRP and SuperSU
gladson1976 said:
Upgraded the Z380KL to official Marshmallow today
Got official Marshmallow, TWRP and SuperSU
Click to expand...
Click to collapse
can move apps to sd card after root?
hafizhans said:
can move apps to sd card after root?
Click to expand...
Click to collapse
I haven't tried that. Normally I let the apps be in the internal memory and don't move them.
Will check if it is possible to move to sd card
Hello, guys this is my first post but i am quite sure that my methods work.If there any problems then u can surely ask in the section below. This thread will be a GUIDE TO ROOT AND INSTALL CUSTOM RECOVERY FOR MOTO G 1st Gen users.
Some prerequisites are:
1. Motorola drives (https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481)
2.Fastboot and recovery files (https://www.dropbox.com/sh/9jf2va51ffg0pzq/AAAxDT-ETf7AESIcHGnfEgv7a?dl=0)
[ Let these files be downloaded and kept in Cdrive of ur pc and and place them on the desktop.. Please name this folder MOTO FILES]
3. SuperSu files https://download.chainfire.eu/696/supersu/ and[/url] paste it in ur phones internal memory and please do this after unlocking the bootloader cause bootloader unlocking will delete everything so its better to do it after unlocking bootloader
Download these files and ur done... Now lets continue to the fun part
This process involves three very simple steps :
1. Unlocking the Bootloader:-
This process is infact very easy to do. There are several guides on the internet regarding this process but the one that i suggest is by High On Android/ Max Lee . Follow his method and u can very easily unlock ur bootlader. Copy this url and see it for urself fellow guys...http://highonandroid.com/android-smartphones/how-to-unlock-bootloader-on-motorola-android-smartphone
2. Erasing ur previous recovery and installing a new one and rooting ur phone all in one process
Some users have been reporting that even after installing custom recovery , whenever they go into recovery they enter into stock recovery. The actual problem is that the stock rom of the Moto G rewrites over the new custom recovery installed.
So we have to install the recovery actually twice but it only takes a few minutes
i) Firstly be sure to have lots of juice in your phone
ii) Boot ur phone into the bootloader by power offing ur device and then pressing the volume down and power button together for 10 seconds and then leaving both of them together.
iii) Now connect ur device to ur pc/laptop
iv) Now open a cmd and enter the following commands(press enter after every command)
- cd Desktop
-cd MOTO FILES
-fastboot flash recovery Recovery2.img
-fastboot reboot-bootloader
[MAKE SURE NOT TO REBOOT UR DEVICE ]
v) Now ur phone has custom recovery installed in it and u shud now enter into recovery mode by choosing the option from the bootloader, by pressing volume down and then volume up while in bootloader mode.
vi) This will open the Philz recovery that i have provided with. I prefer the philz recovery over the cwm one. Now go on and install the SuperSu update zip file. And BOOM ur Device is now rooted !!!!.
vii) Now reboot ur phone and u must install
-ROOT CHECKER (to check root)
- and most importantly ROOT EXPLORER
viii) After following step (vii), now if u try to go into recovery, u will be booted to stock recovery. So to prevent that use the ROOT EXPLORER app and go to the root \system\etc and delete the file named install-recovery.sh .
ix) After deleting the file u will once again have to follow step (iv) and install custom recovery this will ensure u having custom recovery even after rebooting ur device and u will have ROOT access as well
On which android version , were you on before rooting . 5.01 or 5.1 .
This method works for both 5.1 and 5.01
Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849
Is the first post too heavy for you?!
Follow the steps and be happy.
Gesendet von meinem Moto G mit Tapatalk
Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!
Andus1988 said:
Remember: In some marshmallow ROMs (e. g. CM 13 and CyanPop) flashing SuperSU causes some trouble!
Click to expand...
Click to collapse
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:
Ajay P said:
Hi am new for this platform I don't know anything about it... Plz help me out my what's up number is 9901146849
Click to expand...
Click to collapse
whats the problem u facing ?
sanilch99 said:
this method works for all lollipop versions, i dunno much about the marshmallow roms as i havent used them yet :good:
Click to expand...
Click to collapse
It could cumber the inbuilt root!
sanilch99 said:
whats the problem u facing ?
Click to expand...
Click to collapse
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)
Ajay P said:
My phone is not going on twrp mode(custom Recovery) I have followed the steps from YouTube video... I have downloaded all the things which he has mentioned in his description but one of the link (platform tool zip file) is missing, it shows the link is not available.. Plz provide me that file or help me in other way.. I don't want to break my phone.. As am new to this form.. If something lost I can't resolve by myself.. So better to tell me easy way n simple... Thank u in advance
YouTube video(https://youtu.be/dB627nv6-cE)
Click to expand...
Click to collapse
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:
sanilch99 said:
if u want to install twrp recovery and u have its file then i will suggest u to use my method that i have given above and instead writing the command
fastboot flash recovery Recovery2.img u can change it to fastboot flash recovery [name of the recovery file, dont forget the .img at the end]. Thats all u have to do. I saw that video prior to installing custom recovery in my phone too and noticed that his link was broken thats how i figured out my method of installing custom recovery. Its very easy. just follow the steps. :good::good::good:
Click to expand...
Click to collapse
Thank you
thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!
notuger said:
thanks man! everything worked but your supersu was missing binary files so I had to download a new version.
Thanks for the tutorial!
Click to expand...
Click to collapse
I will recheck that super su. file and make sure its perfect... Thanks for the response:good:
Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device
Works but could be simplified
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!
issam029 said:
Once i finished steps all, When i open SuperSU, popup window says, "There is no SU binary installed, and SuperSU cannot install in it. This is the Problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
if i check with root checker,
Sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
i have edited the previous link and given the new one. You can use this SU file. It will solve ur prob.
pcgardner said:
Thanks for this useful post. I've just followed the instructions to root my XT1032 Stock Lollipop 5.1, and they work. However, I have a few comments:
[1] I had already installed Motorola Device Manager on my (Windows 7) PC, plus 'Minimal ADB and Fastboot'. This was sufficient – I didn't need to download the files in your prerequisite 2.
[2] You can use any compatible recovery image. I prefer TWRP, so downloaded openrecovery-twrp-2.8.1.0-xt1032.img.
[3] The SuperSu zip file you've linked to is out of date. The current one is version 2.46 (for Lollipop).
[4] After flashing SuperSu it's advisable to wipe the cache and Dalvik cache.
[5] Root Checker showed that BusyBox wasn't installed, so I downloaded Stephen Erickson's BusyBox installer from the Play Store. This is an essential step, as most programs requiring root won't work without BusyBox. Perhaps it could be added to the OP?
[6] You don't need to use Root Explorer – any root-compatible file manager will do. I prefer Total Commander.
[7] Having deleted (or in my case renamed) install-recovery.sh and then rebooted, I didn't need to go back to step iv and reinstall the custom recovery; in my case TWRP was still there. I think your step ix is unnecessary; at least it's worth checking which recovery you have.
I hope these points are useful and not too nit-picking!
Click to expand...
Click to collapse
Reinstallation of custom recovery is not must its just for safety precautions and I have finally updated the SuperSu link. As far as Busybox u will have to install it customly only.
issam029 said:
once i finished steps all, when i open supersu, popup window says, "there is no su binary installed, and supersu cannot install in it. This is the problem!
If you just upgraded to android 5.0, you need to manually re-root - consult the relevant forums for your device!
Plz help me on this....
If i check with root checker,
sorry! Root access is not properly installed on this device
Click to expand...
Click to collapse
use the new su files i updated the link
facing problem after unlock bootloader mood for moto g 1st gen
Thanks a lot for your information...:good:
Bro!! I have already unlock bootloader mood.. Before rooting is it necessary to clear all data & app...??
Android N Preview 2 npc91k (flashable & image with no encryption and dm verification)
This thread is for the second Android N Preview.
For Android N Preview 3 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-3-beta-npd35k-t3381845
For Android N Preview 4 see: http://forum.xda-developers.com/nexus-6/general/android-n-preview-4-beta-npd56n-t3399473
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **** The following are instruction for installing Android N Preview 2 image released by Google on 4/13/2016. After the installation you will have TWRP recovery 3.0.2-0 with the data partition erased and unencrypted if you use method 2, which means you will have ~ 3GB more space and ~ 10 seconds faster boot speed **Always backup your data before flashing something a total stranger gives you!
Method 1: Flash update through TWRP recovery (keeps your data and current recovery)
1- You need to have TWRP installed on your phone.
2- Download this flashable zip..
3- Copy to the phone internal storage and flash via recovery.
4- Reboot. Your data should still be intact and your OS is upgraded to N Preview 2. If your internal storage is unencrypted before flashing it remains unencrypted.
For some people this didn't work. It seems to be the case when you have been encrypted by your previous Android N installation, in which case TWRP seems to have difficulty reading the file, and that seemingly Preview 2 doesn't play nice with TWRP. It works best when you are unencrypted and your recovery is 3.0.2-0. Thanks to @gammaxgoblin, @blitzerking1, @Michael in ATL, @HueyT, and @PhillyFlyer for debugging and hints.
Method 2: Flash update using a computer (wipes everything, unencrypts data, and upgrades TWRP)
1- ALL of your data including the internal storage will be lost so make a backup. (If you know what you are doing and you are coming from unencrypted Marshmallow you can modify the instructions to not lose data but I won't help you with that).
2- Download this file. Note that it is NOT a flashable zip.
3- Unzip into a folder of your choice on your PC.
4- Open a command window (cmd) and cd to this directory. then run the following:
Code:
flash-all
5- Wait until prompted, then press key to reboot the phone.
6- Your data is wiped and your OS is upgraded to N with unencrypted internal storage. Your TWRP is also upgraded to 3.0.2-0.
Technical details: this is a repacking of the Google image with a modified Kernel and removed userdata and recovery images. Everything else is stock.
Problem downloading from Mega on a mobile browser? Change the page setting to "Request desktop site".
About root and other issues
To obtain root after installing this update you should flash SuperSU 2.71 (or higher) in recovery. Get it from here: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133. Despite the fact that SuperSU 2.71 is supposedly re-written for Android N, there are still some apps that seem to have a problem obtaining root. The commonest complaint on this thread so far has been about Adaway. If you want to block Ads just manually do what Adaway does. Download a hosts file from any ad block list server such as http://winhelp2002.mvps.org/hosts.htm, copy the files on your sdcard, boot the phone into recovery, and using the TWRP file manager replace the file /system/etc/hosts with this file and set its permissions to 644 (rw-r--r--).
wouldnt flash first go. redl now
no flash again
gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Same happened to me. It would not flash, same error
gammaxgoblin said:
wouldnt flash first go. redl now
no flash again
Click to expand...
Click to collapse
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
Same error for me as well. I can extract the zip and view the file it is talking about. I also tried on TWRP 3.0.1-0 and TWRP 3.0.2-0
Everything is working perfect for me with the new zip. I have a unencrypted phone and used 3.0.2 TWRP.
najoor said:
Can you open the zip that you downloaded and see if you can see the file that it is complaining about? What version of twrp are you using?
Click to expand...
Click to collapse
i tried 3.0.1 and 3.0.2 and i can also see the file
Method 2 works great
Method two works I used it myself
Shall I flash preview 2 directly from marshmallow?
Seems like TWRP is having a lot of troubles with each version of N Preview's encryption. I have same problem with both N6 and N6P, as do others in that forum too....:/
i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.
marius987 said:
i have latest twrp, download a ota update from ofiicial site in zip file and flash it over in twrp. boot normally and works fine. only flash supersu 2.71 and it's unencrypted at all.
ps. TB not works for me ind N prew2 so i flash perv1, restore from TB and flash prew2 over it.
Click to expand...
Click to collapse
Sorry for the stupid question. What do you mean for TB?
cerico76 said:
Sorry for the stupid question. What do you mean for TB?
Click to expand...
Click to collapse
I'm going to assume it stands for Titanium Backup.
Waiting for fixed method #1
outkastz said:
I'm going to assume it stands for Titanium Backup.
Click to expand...
Click to collapse
Ah,yes! Thanx!
Can someone please provide a link to the desktop website for the flashable zip?
Just to help with the installation of method 2, holding shift and right clicking a blank space in your unzipped folder, you can click open command window here. That will save you having to CD all the way to it.
Sent from my Nexus 6 using XDA-Developers mobile app
I did method 1. It upgraded fine. All my data remained. It killed root (expected this) and my TWRP. I was unencrypted before attempting.
I went and downloaded the latest TWRP and flashed via fastboot. Then downloaded latest SuperSU from http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133 and flashed it via my newly installed TWRP. Root confirmed and all is well.
Good to go Thanks!
I've got an "Invalid boot image" issue :
Any tought ?
outpox said:
I've got an "Invalid boot image" issue :
Any tought ?
Click to expand...
Click to collapse
You may have to flash a previous stable release of marshmallow or lollipop from Google first and then try this because something seems to be corrupted in your system.
UPDATE 14.05.2017: Chainfire has released autoroot for Galaxy S5 Mini G800F based on firmware 6.0.1. It can be downloaded from the official CF Autoroot website (direct link to the G800F file). It is by far the easiest and fastest method for getting root access on your device without the need for TWRP.
Procedure for rooting with CF autoroot:
1. Charge your S5 Mini's battery to at least 80% and make sure you have Samsung USB drivers installed on your PC
2. Enable USB debugging on the S5 Mini
3. Download the CF autoroot file from the link above and unpack the zip archive
4. Open ODIN as administrator (right click -> Run as administrator)
5. Put the S5 Mini in download mode and connect it via USB cable to the PC
6. After ODIN recognizes the device, click "AP" and select the autoroot file
7. Click "Start" and wait for the process to finish - shouldn't take more than a few seconds
8. When the log in ODIN says "Disconnected", unplug the USB cable from the phone and wait for it to restart itself
9. Verify proper root with a tool like Root Checker
If you want to have TWRP recovery and Xposed framework, use the guide below.
This method applies only to the S5 Mini G800F variant running Android 6.0.1. Trying this on other variants may result in bricking your device. I used this procedure to get root access and Xposed working on my European S5 Mini G800F using a German (DBT) Marshmallow firmware. Use at your own risk, I'm not responsible for anything that happens to your device. Note that this procedure voids your warranty. This guide assumes that you already have TWRP recovery or know how to flash it.
Backup everything important like contacts and photos before you begin.
Requirements for this method to work:
unrooted Samsung Galaxy S5 Mini G800F running official stock Android 6.0.1 Marshmallow
Samsung USB driver
enable USB debugging
charge your phone's battery to 100% just in case
TWRP Recovery 3.0.2 installed Official TWRP Recovery 3.1.1 is available now - check out this thread for download links
IMPORTANT NOTE ABOUT RECOVERY: Official TWRP now available
Procedure for getting root access:
1. Download Chainfire's SuperSU v2.78 SR5 [link] and store the zip file in the phone's internal memory or SD card.
2. Boot into TWRP recovery, navigate to the SuperSU zip and flash it, reboot after it finishes.
3. You should now see the SuperSU icon, open it and update the binary. Verify proper root with a tool like Root Checker.
Congratulations, you have successfully rooted your G800F! If you only want root - stop here, you're done.
Procedure for getting Xposed Framework:
1. After rooting your S5 Mini, download Xposed v87.1 built by wanam [link], Xposed uninstaller [link], and Xposed Installer APK [link]. Put all 3 files on the phone's internal memory or SD card.
2. Boot into TWRP recovery, navigate to the file named "xposed-v87.1-sdk23-arm-custom-build-by-wanam-20161125.zip" and flash it.
3. After the flashing is finished, wipe cache and dalvik then reboot.
4. Using a file manager, navigate to where you put the Xposed Installer APK and install it.
5. Open it and confirm that Xposed is installed properly.
weird enough all those files where already on my pc. i just wanted to know if it would work
it says no root
Zakipoophead27 said:
it says no root
Click to expand...
Click to collapse
Which firmware version are you trying to root and did you use the exact files I've linked?
kom-pakt said:
Which firmware version are you trying to root and did you use the exact files I've linked?
Click to expand...
Click to collapse
The netherland marshmallow firmare. And i have used all the files you linked. I even tried other one's. None work
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Tomislav3383 said:
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Click to expand...
Click to collapse
Same for me - rooting (Germany DBT) according to your instructions didn't work
Gesendet von meinem kminilte mit Tapatalk
Zakipoophead27 said:
The netherland marshmallow firmare. And i have used all the files you linked. I even tried other one's. None work
Click to expand...
Click to collapse
Tomislav3383 said:
I also have 6.0.1 Germany DBT but this didn't root my s5 mini
Click to expand...
Click to collapse
Helius61 said:
Same for me - rooting (Germany DBT) according to your instructions didn't work
Gesendet von meinem kminilte mit Tapatalk
Click to expand...
Click to collapse
When you flash the SuperSU observe the log during the process, does it reboot by itself after posting this?
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
If it reboots after this, turn off your phone and boot into recovery, go to "Wipe" and wipe cache and dalvik. Immediately after that try to flash the SuperSU again, if successful it should post this:
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
and then some more lines, at the end it should say "Done!" and then give you the option to reboot. Remember if the flashing is successful you should reboot manually, if the phone reboots by itself then the flashing failed.
Note that I always recommend to start with a freshly installed firmware i.e. wipe the entire phone, flash new firmware, flash TWRP 3.0.0 and then flash SuperSU.
Thank you very much for your instant support. I'm currently traveling and I'll try your solutions once I'm back home again. Then, I'll provide an update whether it works or not.
kom-pakt said:
When you flash the SuperSU observe the log during the process, does it reboot by itself after posting this?
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
If it reboots after this, turn off your phone and boot into recovery, go to "Wipe" and wipe cache and dalvik. Immediately after that try to flash the SuperSU again, if successful it should post this:
Code:
******************
SuperSU installer
******************
- Mounting /system, /data and rootfs
- Extracting files
- Detecting system compatibility
- System-less mode, boot image support required
- Creating image
- Mounting image
- Creating paths
- Removing old files
- Placing files
******************
Boot image patcher
******************
and then some more lines, at the end it should say "Done!" and then give you the option to reboot. Remember if the flashing is successful you should reboot manually, if the phone reboots by itself then the flashing failed.
Note that I always recommend to start with a freshly installed firmware i.e. wipe the entire phone, flash new firmware, flash TWRP 3.0.0 and then flash SuperSU.
Click to expand...
Click to collapse
Wiped cache and dalvik, got the same lines you posted, rebooted, but root is still not working.
Tomislav3383 said:
Wiped cache and dalvik, got the same lines you posted, rebooted, but root is still not working.
Click to expand...
Click to collapse
Same for me
Does this root trigger the knox counter?
Hello, had the same problem . No root after reboot.
You need to use an older twrp.
With 2.8.1.0 it all works
i did it!
it works but you gotta have twrp 3.0.2-0 and then flash the zip file.
pop ups where blocked so i just changed it from always ask to always allow.
you gotta install twrp 3.0.0-0 and then flash the twrp 3.0.2-0 .img to recovery.
after that just flash the superSU zip and your done.
hope it works for you
Helius61 said:
Thank you very much for your instant support. I'm currently traveling and I'll try your solutions once I'm back home again. Then, I'll provide an update whether it works or not.
Click to expand...
Click to collapse
Glad I can help, also check out the other solutions posted in the meantime.
Dark_Horse said:
Does this root trigger the knox counter?
Click to expand...
Click to collapse
Yes.
Snowgay said:
Hello, had the same problem . No root after reboot.
You need to use an older twrp.
With 2.8.1.0 it all works
Click to expand...
Click to collapse
Zakipoophead27 said:
i did it!
it works but you gotta have twrp 3.0.2-0 and then flash the zip file.
pop ups where blocked so i just changed it from always ask to always allow.
you gotta install twrp 3.0.0-0 and then flash the twrp 3.0.2-0 .img to recovery.
after that just flash the superSU zip and your done.
hope it works for you
Click to expand...
Click to collapse
It seems that the culprit for the failed rooting were the different versions of TWRP you were using. I will add links to 2 versions of TWRP and a note about this in the main post.
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Scharnhorst1939 said:
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Click to expand...
Click to collapse
What version of twrp do you have?
Scharnhorst1939 said:
Can someone help me? I did it like in the tutorial but it does not work. Thanks all
Click to expand...
Click to collapse
I keep updating the first post with additional information and links, read it again and follow the instructions carefully without skipping any of the steps.
thanks for answer. Now it work with Version 2.8.0
Scharnhorst1939 said:
thanks for answer. Now it work with Version 2.8.0
Click to expand...
Click to collapse
Good to hear, version 3.0.2 works too and is more up to date.