Hi..!! Everyone I tried everything, I was going to unlock and root my xoom but I got stuck at this step:
7. fastboot flash boot rootboot.img
I get this error: "can't load rootboot.img"
I run fastboot reboot command and works, after reboots I try adb devices and my xoom shows but if I run adb remount I get this error:
"remount failed: Operation no permitted"
I tried everything search everywhere, update everything and NADA, I'm on a Windows 7 64bit.
Thanks and I hope somebody can direct me to the right path..
You will want to grant root access again using the adb commands. This happened to me once. You don't have permission to do this because it needs to have root access to carry on this operation. Try the root commands again to grant root access and then see what it does when trying to flash the rootboot files.
If that's not it come let us know. XDA will have your answer for sure.
Sent from my Droid using XDA Premium App
diablo2224 said:
You will want to grant root access again using the adb commands. This happened to me once. You don't have permission to do this because it needs to have root access to carry on this operation. Try the root commands again to grant root access and then see what it does when trying to flash the rootboot files.
If that's not it come let us know. XDA will have your answer for sure.
Sent from my Droid using XDA Premium App
Click to expand...
Click to collapse
I get stuck on step 7 of this guide below, so I think I never get to the point of getting root, but if I'm doing something wrong and I have to run some other commands please let me know.
1. Download the Motorola Xoom Root Zip file and unzip it. Download
2. Place the files in the SDK Tools folder.
3. adb reboot bootloader (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot rootboot.img
7. fastboot reboot (wait for reboot)
8. adb remount
9. adb shell push su /system/bin
10. adb shell ln –s /system/bin/su /system/xbin/su
11. adb shell chmod 4755 /system/bin/su
12. adb push Superuser.apk /system/app
And thanks for making some time to reply, I try to get some help on other threads with no response.
dumb question: is rootboot.img in the same directory as everything else?
It sounds to me like your flashboot can't find it.
That's a good point from the poster above. I had trouble at the start with this and the SDK tools folder because I never messed with the adb shell too often because there never really has been a need for me to do so up until I got the Xoom.
OP... like this reply says above me, I am agreeing to as well. It looks like it might not be finding your rootboot. Make sure all root files are located in the very root of the SDK tools folder, and make sure all root files are not inside a folder. If they are please drag them into the tools folder and slap them all in there. It looks like a mess but it works. Do the same type of thing if you plan on flashing an overclock kernel. Always make sure that all files are NOT in folders when flashing something like this, and that they are always placed in the very root of the tools folder located within the SDK folder. Hope this helps.
About my above post... woops. I wasn't paying attention totally. It was late. I was thinking about when you are trying to install an overclock kernel and run into this problem that says that you cannot remount in adb. It does have to do with root access though.
Thank you very much guys I found what was my problem, I was running ADB straight from CMD window without navigating to my tool folder and always worked so I thought running step 7 will work, but NO I had to cd c:.....bla bla navigate to tool folder and do step 7.
Now I'm happily Rooted thanks again for your time guys, now to set up again my beautiful screens.
I'm having that problem where i'm trying to flash Tiamat Kernel on my Xoom and when i get to the remount i'm getting - remount failed: Operation not permitted . When you say grant root access again you talking about pointing it to the platform folder ?.
It sounds like those having problems are not very familiar with adb. Don't worry, we have all been there at one point. I would suggest that you use the one click method. No its not really a one click, more like a one click at a time method. But, it goes slow and you can see what it is doing as it goes along and has a nice tutorial from the op.
Sent from my HTC HD2 using XDA Premium App
jase33 said:
It sounds like those having problems are not very familiar with adb. Don't worry, we have all been there at one point. I would suggest that you use the one click method. No its not really a one click, more like a one click at a time method. But, it goes slow and you can see what it is doing as it goes along and has a nice tutorial from the op.
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
No i'm not so good at it but i'm willing to or i want to learn . I used it for the first time when my Xoom was soft brick from installing a theme , i restored it with ADB and then use ADB to root ,so that's twice , the first time i rooted my Xoom i used the one click method because i was so afraid of ADB . Today the third time i was using it to flash a Kernel and at the remount i got into the problem above .
jawonder said:
No i'm not so good at it but i'm willing to or i want to learn . I used it for the first time when my Xoom was soft brick from installing a theme , i restored it with ADB and then use ADB to root ,so that's twice , the first time i rooted my Xoom i used the one click method because i was so afraid of ADB . Today the third time i was using it to flash a Kernel and at the remount i got into the problem above .
Click to expand...
Click to collapse
Are you trying to push something thru a ADB...???
Sent from my Xoom using XDA Premium App
lokko21 said:
Are you trying to push something thru a ADB...???
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Yes i'm trying to flash a kernel but at the remount step it's telling that : remount failed : operation is not permitted .
Hey Guys,
i hope my english is ok and you can unterstand all what i mean.
I have a Kindle Fire HD Software version 7.2.3
i try to root my Kindle, fot the root i use this Method:
http://forum.xda-developers.com/showthread.php?t=1886460
Root_with_Restore_by_Bin4ry_v17 in the cmd.exe i got and error "permission denied"
then i use QemuRoot.bat and step 2 the same error "permission denied"
Driver installed and work correctly.
Kindel settings are correct.
maybe their have an idea.
I uploaded some pictures of the error in a few minutes.
CMD returned error "permission denied"
HarldOOOandSon said:
Hey Guys,
i hope my english is ok and you can unterstand all what i mean.
I have a Kindle Fire HD Software version 7.2.3
i try to root my Kindle, fot the root i use this Method:
http://forum.xda-developers.com/showthread.php?t=1886460
Root_with_Restore_by_Bin4ry_v17 in the cmd.exe i got and error "permission denied"
then i use QemuRoot.bat and step 2 the same error "permission denied"
Driver installed and work correctly.
Kindel settings are correct.
maybe their have an idea.
I uploaded some pictures of the error in a few minutes.
Click to expand...
Click to collapse
If I understand correctly, you try to execute the batch files to Root the Kindle Fire 7" HD: RunMe.bat (Step 1) or QemuRoot.bat (Step 2), Microsoft Windows returns an error Permission Denied or Access Denied. I suspect you are using Windows 7, correct? Try to Right Hand Mouse Click on then CMD.EXE Shortcut and choose "Run As Administrator".
prokennexusa said:
If I understand correctly, you try to execute the batch files to Root the Kindle Fire 7" HD: RunMe.bat (Step 1) or QemuRoot.bat (Step 2), Microsoft Windows returns an error Permission Denied or Access Denied. I suspect you are using Windows 7, correct? Try to Right Hand Mouse Click on then CMD.EXE Shortcut and choose "Run As Administrator".
Click to expand...
Click to collapse
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
HarldOOOandSon said:
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
Click to expand...
Click to collapse
I have the same exactly issue and I do run the .exe as administrator.... i don´t know whats going on....
HarldOOOandSon said:
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
Click to expand...
Click to collapse
Had the same problem. DL my package and see if you have any better luck:
http://www.mediafire.com/?t570mx55pqw5ezw
Or here are my instructions anyways:
Instructions:
1. Install/update Java from "chromeinstall-7u10.exe"
2. Install Kindle Fire ADB Drivers with "Kindle Fire ADB drivers.exe"
3. Place your Kindle fire in ADB mode (Settings->Security->Enable ADB->On) and connect your device by USB.
4. In the "Root_with_Restore_by_Bin4ry_v18" folder run "RunMe.bat"
5. Use Option one and follow the on-screen instructions
6. In the "QemuRoot_v1.0" folder, run "RootQemu.bat"
7. Follow the onscreen instructions.
8. You should be greeted with a success prompt.
*NOTE*
This method has gotten me farther and actually installs Superuser.apk, which I can open using ES File Explorer.
HOWEVER, Root still apparently doesn't work for me.
bigtimer5 said:
Had the same problem. DL my package and see if you have any better luck:
Or here are my instructions anyways:
Instructions:
1. Install/update Java from "chromeinstall-7u10.exe"
2. Install Kindle Fire ADB Drivers with "Kindle Fire ADB drivers.exe"
3. Place your Kindle fire in ADB mode (Settings->Security->Enable ADB->On) and connect your device by USB.
4. In the "Root_with_Restore_by_Bin4ry_v18" folder run "RunMe.bat"
5. Use Option one and follow the on-screen instructions
6. In the "QemuRoot_v1.0" folder, run "RootQemu.bat"
7. Follow the onscreen instructions.
8. You should be greeted with a success prompt.
*NOTE*
This method has gotten me farther and actually installs Superuser.apk, which I can open using ES File Explorer.
HOWEVER, Root still apparently doesn't work for me.
Click to expand...
Click to collapse
Still doesn´t work for me, the RunMe.Bat did finish the process but, the RooQuemu.Bat keeps teelling that in the 2nd step the prompting the access in denied
jose87413 said:
Still doesn´t work for me, the RunMe.Bat did finish the process but, the RooQuemu.Bat keeps teelling that in the 2nd step the prompting the access in denied
Click to expand...
Click to collapse
Same thing here. Doesnt matter which tutorial I follow. I get a permission or operation denied on anything that I want to do on the Kindle Fire.
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
HarldOOOandSon said:
I try it and choose Run As Administrator but the same error.
Here the Line i file in:
echo 'ro.kernel.qemu=1' > /data/local.prop then the error "permission denied"
"[email protected]:/ $ rm -r /data/local/tmp
rm -r /data/local/tmp
rm failed for /data/local/tmp, Permission denied"
Mhhh anybody a Idea?
Driver correct install, install Android SDK Packages (SDK Tools + Plattorm Tools installed, and google Driver), and Java too.
Click to expand...
Click to collapse
Run everything again, first updating these utilities to the latest versions - these links have an updated ADB Server and API's:
https://dl.dropbox.com/u/54456659/Qmenu.zip
https://dl.dropbox.com/u/54456659/Ro...Bin4ry_v17.zip
Then follow these instructions again (Ignoring the links below):
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. When the Kindle asks to be Restored, CLICK on it (this installs the binary files).
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You now have Root.
prokennexusa said:
Run everything again, first updating these utilities to the latest versions - these links have an updated ADB Server and API's:
https://dl.dropbox.com/u/54456659/Qmenu.zip
https://dl.dropbox.com/u/54456659/Ro...Bin4ry_v17.zip
Then follow these instructions again (Ignoring the links below):
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. When the Kindle asks to be Restored, CLICK on it (this installs the binary files).
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You now have Root.
Click to expand...
Click to collapse
Thanks for the info (i'm having the same problem)
The 2nd download link does work (
Broken Link
Wilson157 said:
Thanks for the info (i'm having the same problem)
The 2nd download link does work (
Click to expand...
Click to collapse
2nd Download Link: Root_with_Restore_by_Bin4ry_v17.zip
thanks but no cigar
Thanks for the link.
I restored the kindle back to factory settings, followed your steps but i still get access denied on step 2 (exploiting) [local.prop]
(
Any help would be really really appreciated.
Step 1
Wilson157 said:
Thanks for the link.
I restored the kindle back to factory settings, followed your steps but i still get access denied on step 2 (exploiting) [local.prop]
(
Any help would be really really appreciated.
Click to expand...
Click to collapse
When you did Step 1, did you see Restore on the Kindle? Did you click on the Restore dialog and let the program reboot the Kindle? When the Kindle rebooted, was it running slow?
prokennexusa said:
When you did Step 1, did you see Restore on the Kindle? Did you click on the Restore dialog and let the program reboot the Kindle? When the Kindle rebooted, was it running slow?
Click to expand...
Click to collapse
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
Wilson157 said:
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
Click to expand...
Click to collapse
actually i've tried running the 1st step...and the kindle DOES run really slow. sorry for the confusion
Wilson157 said:
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
actually i've tried running the 1st step...and the kindle DOES run really slow. sorry for the confusion
Click to expand...
Click to collapse
yea, just tried. no go. any other ideas?
Qemu ADB Update
Wilson157 said:
Yes i saw the restore window. i did the restore, the kindle rebooted and the 1st root programe (by bin4ry) seemed to work fine, it told me i had root. When i ran the Qemu root kit it failed on step 2.
No the kindle didnt seem to run slow. it did the very 1st time i tried to root it after the 7.3.2 update, but since doing a factory reset, the kindle didnt run slow after rooting attempts.
if you get me rooted i will post you a very sexy picture of my ankle!
---------- Post added at 10:09 PM ---------- Previous post was at 10:01 PM ----------
actually i've tried running the 1st step...and the kindle DOES run really slow. sorry for the confusion
Click to expand...
Click to collapse
After the first step, do not do anything to the Kindle, leave it alone after the reboot and proceed using the following updated Qemu program.
You may download the updated version here: https://dl.dropbox.com/u/54456659/Qmenu.zip
Extract to your desktop and run the RootQemu.bat file. Choose Option 1.
littleengin said:
yea, just tried. no go. any other ideas?
Click to expand...
Click to collapse
in the words of alan partridge....A HAAAA!
Solved the issue.....Instead of running the batch file as admin, i opened up 'CMD' as admin, then navigated (using command prompt) to the folder containing the root files and ran them.....it worked!!! it passed through step 2.
However....when i run es file explorer. i cannot access root
Initialize Superuser.apk
Wilson157 said:
in the words of alan partridge....A HAAAA!
Solved the issue.....Instead of running the batch file as admin, i opened up 'CMD' as admin, then navigated (using command prompt) to the folder containing the root files and ran them.....it worked!!! it passed through step 2.
However....when i run es file explorer. i cannot access root
Click to expand...
Click to collapse
Ahhh, almost there. This is a bug in Superuser.apk - go into your Apps folder, you will see Superuser, click on it. It will open, now go to File Explorer, see if you can run as Root. I prefer Root Explorer.
Wilson157 said:
in the words of alan partridge....A HAAAA!
Solved the issue.....Instead of running the batch file as admin, i opened up 'CMD' as admin, then navigated (using command prompt) to the folder containing the root files and ran them.....it worked!!! it passed through step 2.
However....when i run es file explorer. i cannot access root
Click to expand...
Click to collapse
sorry my bad! Es file explorer was set to access root. Now i can access it. Thank you thank you thank you
I would post a picture of my ankle but the mods might class it as porn
Root and Google Play for Amazon 7" Kindle Fire HD Software Version 7.2.3
Since this thread had seen a lot of changes over the last couple of weeks, I decided it was time to consolidate everything again, so here it is the consolidated and updated link version as of 12/23/2012:
The problem "Device not Found" is usually driver related or ADB Security issue. I assume you have ADB enabled under Security - Enable ADB? Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/show....php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package. Reboot the PC and next the Kindle.
As you noted, if you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Download Root MANY ANDROID! to your desktop. Extract to your desktop.
Download Qemu automated root to your desktop. Extract to your desktop.
NOTE WINDOWS 7 USERS: You need to open a command prompt "as Administrator" when running the batch files RunMe.bat and RootQemu.bat - otherwise Windows will respond with "Permission Denied".
Root Step 1: Run RunMe.bat from Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Choose option 1 Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle. Click on Restore. When the program has completed, the Kindle will Reboot.
Root Step 2: When the Kindle reboots it will react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run RootQemu.bat from Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Follow the instructions Step-by-Step allowing Windows to re-detect the Kindle between reboots (about 2 minutes). Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Play Step 1 Move GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk to /system/app. Using Root explorer app on the Fire (be sure it has Superuser Permissions). Change permissions on both to Owner: Read-Write, Group: Read and Others: Read. Install GoogleServicesFramework.apk, AccountAndSyncSettings.apk and GoogleLoginService.apk
Play Step 2 Reboot the Kindle
Play Step 3 Download Vending.apk
Play Step 4 Using Root explorer app on the Fire (be sure it has Superuser Permissions). Move Vending.apk to /system/app with permissions set to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Download and install the Gplay3.8.17.apk to upgrade the the android market to the current Google Play market.
Play Step 8 Download google_apps - unzip to /sdcard/download
Play Step 9 Install Google Apps as needed. There is no need to move any of the apps to /system/app, just perform a normal apk install by using Root Explorer to install these apps.
I have also attached copies of these noted files to this thread.
Also, I have organized a few Google Apps & Services then zipped them into a folder you may download here: Google Apps. I have used all these Apps on my Kindle 7" HD successfully.
If you would like to disable the Amazon OTA Updates, delete or move /system/ect/security/otacerts.zip to /sdcard/download - Reboot the Kindle.
Finally, to eliminate Amazon from intercepting any Market requests, thus allowing Google Play to be the default Market move /system/app/MarketIntentProxy.apk to /sdcard/download - Reboot the Kindle
I'm also trying to do what previous users have been doing in this thread: running Rootqemu.bat but I still get permission denied on the second step. I've tried navigating to the folder using an administrator command prompt and running it through cmd, still fails on the second step with permission denied:
/system/bin/sh: cannot create /data/local.prop: Permission denied.
Have no idea where to go from here any help would be appreciated.
A Comprehensive guide to Rooting And Custom Recovery with a Non-Functioning USB Port
This is for those of us who have a broken USB port on our Xperia devices and still want to flash! If it is too difficult/expensive to get your device repaired, this method may still get you root and custom recovery.
Requirements:
As we always say with suggestions from XDA, DO THIS AT YOUR OWN RISK. I take no responsibility for you or your device.
This procedure was carried out on a Z3 Compact with stock firmware 23.4.A.1.264.
1. Xperia device with stock firmware - what I had: 23.4.A.1.264
2. KingRoot - what I had: 4.8.1
3. [NUT]'s XZDualRecovery - what I had: Z3C-lockeddualrecovery2.8.26-RELEASE.combined.zip
4. Android file exporer with root capcibility - what I had: ES File Explorer File Manager
5. Android terminal with root capability - what I had: Terminal Emulator for Android
6. Root Checker - what I had: Root Checker
STEP 1:
Use Kingroot to root the device. The version I had at the time said that there was no root method specifically available but there was a generic method which worked. If this doesnt work - try rebooting and try it. It worked for me on my second attempt.
STEP 2:
Use Root Checker to make sure the device is rooted - a dialog box should open from Kingroot asking if you want to grant it root access, press yes!
STEP 3:
Download XZDualRecovery twice - one for flashing and one for extracting (I found this easier on a PC).
STEP 4:
In the extracted version, open the install.bat in a text editor so you can read the code
STEP 5:
Search for the bit where the bat file makes the directory and transfers the necessary files
Code:
echo =============================================
echo Step2 : Sending the recovery files.
echo =============================================
adb shell "mkdir /data/local/tmp/recovery"
adb push ..\tmp\dr.prop /data/local/tmp/recovery/dr.prop
adb push ..\system\bin\chargemon /data/local/tmp/recovery/chargemon
adb push ..\system\bin\mr /data/local/tmp/recovery/mr
adb push ..\system\.XZDualRecovery\xbin\dualrecovery.sh /data/local/tmp/recovery/dualrecovery.sh
adb push ..\tmp\NDRUtils.apk /data/local/tmp/recovery/NDRUtils.apk
adb push ..\system\.XZDualRecovery\xbin\rickiller.sh /data/local/tmp/recovery/rickiller.sh
adb push ..\tmp\byeselinux.ko /data/local/tmp/recovery/byeselinux.ko
adb push byeselinux\byeselinux.sh /data/local/tmp/recovery/byeselinux.sh
adb push ..\tmp\wp_mod.ko /data/local/tmp/recovery/wp_mod.ko
adb push byeselinux\sysrw.sh /data/local/tmp/recovery/sysrw.sh
adb push ..\tmp\modulecrcpatch /data/local/tmp/recovery/modulecrcpatch
adb push ..\system\.XZDualRecovery\xbin\busybox /data/local/tmp/recovery/busybox
adb push ..\system\.XZDualRecovery\xbin\recovery.twrp.cpio.lzma /data/local/tmp/recovery/recovery.twrp.cpio.lzma
adb push ..\system\.XZDualRecovery\xbin\recovery.philz.cpio.lzma /data/local/tmp/recovery/recovery.philz.cpio.lzma
if exist {..\system\.XZDualRecovery\xbin\ramdisk.stock.cpio.lzma} (
adb push ..\system\.XZDualRecovery\xbin\ramdisk.stock.cpio.lzma /data/local/tmp/recovery/ramdisk.stock.cpio.lzma
)
adb push ..\tmp\installrecovery.sh /data/local/tmp/recovery/install.sh
STEP 6:
Make the corresponding directory /data/local/tmp/recovery with your file explorer
STEP 7:
Copy the files mentioned in the bat from the extracted version to the folder location. All the files go into one folder with the same file name apart from the last one which is renamed installrecovery.sh to install.sh.
STEP 8:
Double check everything that it mentioned in the bat file is in the correct directory on the device.
STEP 9:
Open terminal emulator and type "su" - a dialog box should open from Kingroot asking if you want to grant it root access, press yes!
STEP 10:
Use "pwd" and "cd" to see where you are and to change directory. You are trying to get to /data/local/tmp/recovery.
STEP 11:
Once your there type in "./install.sh" to start [NUT]'s recovery installer. A whole bunch of stuff should come up in the window explaining the status of the installer.
STEP 12:
If all went well - your device should reboot and go straight into TWRP. MAKE A BACKUP!!!
STEP 13:
From here I directly wiped the device and installed a new ROM. Click the thanks button if this worked for you - Happy Flashing!
Credits
@[NUT] for his custom recovery and support.
@istux for his research, suggestions and perseverance.
Finally you get it
Great work!
istux said:
Finally you get it
Great work!
Click to expand...
Click to collapse
thanks - lets hope it is useful for someone
Awsome! Very useful guide