Related
My wife has a rooted nexus 7 2012 wifi and she unintentionally accepted the ota Android 4.3 update. So of course it unrooted her.
I originally had a hell of a time rooting this tablet using wugfresh nexus toolkit. Took me several days to succeed and the same thing is happening again. My Windows 7 laptop keeps installing the wrong drivers even though I selected the option to disable the auto driver configuration. Also USBDeview never shows the installed Samsung adb drivers yet when I try to install them I am warned they are already installed. It's already been hours and who knows how many retries and reboots!
So even though I'm a newbie I decided to go the Android sdk route.
1. Where do I download the files I need to just root the darn tablet?
2. What do I do next?
Please keep it simple........
Anyone want to walk me through it on the phone?
Thanks
If you are new to using SDK, check this out for a well laid out tut on how to get set up and rooted.
I now have android sdk set up.
What are the commands I should issue to root?
Thanks
now you need to flash a custom recovery then flash a root zip file via windows command prompt...Have you figured out how to interface with your device and the windows command prompt? eg;
-a good first command is "adb devices" and see if it lists your device, if it does your golden...
-then you would issue "adb reboot bootloader"
-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"
-then while in bootloader toggle with the volume keys to "recovery" option and press power
-now you will be in your new recovery you just flashed and you can push the zipped root file you chose to the sdcard, "adb push rootyouchose.zip /sdcard/"
-once its been pushed you can flash it in recovery and reboot, and you are now rooted
-this is the latest cwm recovery that you could flash in fastboot as described above
-this would be the root file you want to push then flash in recovery
-this may be of some help, scroll down halfway
Thank you so much for helping. You can't know how much it is appreciated.
-a good first command is "adb devices" and see if it lists your device, if it does your golden...
Got that. It works!!
-then you would issue "adb reboot bootloader"
Worked! Got the Android on his back.
-once in bootloader you would issue "fastboot flash recovery whateverrecoveryouchose.img"
Is recovery image on my pc or the tablet?
Why do I have to indicate the img name here if I will later select it
When I write
Fastboot flash......... Img
I get
Unknown partition 'the image file name'
"error : cannot determine image filename for. '.......'
You need to have downloaded a recovery image, that is what you flash I linked to one on my last post, that file is called "recovery-clockwork-touch-6.0.4.3-grouper.img" so you would issue,
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img
"fastboot flash recovery" is telling it to flash a recovery file and "recovery-clockwork-touch-6.0.4.3-grouper.img" is the recovery file in this case to be flashed so, combined its, "fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img"
I do not use Windows, I use a terminal instead of windows command prompt so I can't be specific as I am not too familiar with windows command prompt. With terminal it is much easier in my opinion but you need to be running nix or Mac OS to have a terminal
OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.
I have the proper drivers installed and it connects fine with my Windows 7 laptop.
From a Windows 7 command prompt
1. "abd devices "
Correctly returns the attached nexus
2. "abd reboot bootloader "
Correctly reboots the tablet
3. **here's where things breakdown :
I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)
" openrecovery-twrp-grouper.img"
However, when I now issue the command
"fastboot flash recovery openrecovery-twrp-grouper.img"
I get an error :
Cannot open openrecovery-twrp-grouper.img
The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.
So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?
Do I need to put the recovery image somewhere special in the nexus file structure?
I'm stuck.
Thanks
Anderson2 said:
OK, still can't get past the final stage in rooting my wife's nexus 2012 nexus 7.
I have the proper drivers installed and it connects fine with my Windows 7 laptop.
From a Windows 7 command prompt
1. "abd devices "
Correctly returns the attached nexus
2. "abd reboot bootloader "
Correctly reboots the tablet
3. **here's where things breakdown :
I downloaded the latest twrp openrecovery img for grouper and renamed it (for simpler typing)
" openrecovery-twrp-grouper.img"
However, when I now issue the command
"fastboot flash recovery openrecovery-twrp-grouper.img"
I get an error :
Cannot open openrecovery-twrp-grouper.img
The same thing happened with the clockwork-touch recovery img. That is why I downloaded the twrp img which I am more familiar with anyway.
So, am I missing a step between rebooting the bootloader and flashing the recovery? After the bootloader is rebooted and I get the Android on his back with an empty belly, do I need to do something else before flashing?
Do I need to put the recovery image somewhere special in the nexus file structure?
I'm stuck.
Thanks
Click to expand...
Click to collapse
Hi, Anderson2...
If I may throw in my couple of cents...
The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.
Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.
For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...
Code:
fastboot devices
This is purely diagnostic, and hopefully confirms a working fastboot connection.
You should see something like this...
Code:
025d2d424bxxxxx fastboot
A serial number followed by the word fastboot. If you see this, you can go ahead and run...
Code:
fastboot flash recovery recovery.img
(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).
My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".
If fastboot can't find it.. it can't open it.
Hope this helps.
Rgrds.
Ged.
GedBlake said:
Hi, Anderson2...
If I may throw in my couple of cents...
The recovery.img file to be fastboot flashed (TWRP or CWM, it really doesn't matter which) needs be to stored on your PC... on the same PATH as the FASTBOOT.EXE file. The easiest way of accomplishing this, is to copy it directly into the folder that contains your FASTBOOT and ADB executables.
Where this folder is located on your PC depends on how you have fastboot setup, but it's usually stored in a folder called /Platform-Tools (if I remember correctly). But because I've never bothered myself installing the whole Android SDK (of which Fastboot is a part of) on my PC, I'm not sure of it's precise PATH (ie. it's location) but I think it's somewhere in the Android SDK folder.
For myself, I just maintain a simple folder on the Windows desktop containing the FASTBOOT.EXE and ADB.EXE files and a few necessary Windows .DLL files. When I wish to fastboot flash a Custom Recovery, I simply copy the Custom Recovery .img file (TWRP or CWM) into this folder, rename it to recovery.img (renaming it thus makes typing at the command prompt easier, and reduces the scope for potential typos)... boot the Nexus 7 into the bootloader, hook it up to my PC via USB. And then open a command prompt on the folder, and run...
Code:
fastboot devices
This is purely diagnostic, and hopefully confirms a working fastboot connection.
You should see something like this...
Code:
025d2d424bxxxxx fastboot
A serial number followed by the word fastboot. If you see this, you can go ahead and run...
Code:
fastboot flash recovery recovery.img
(This command assumes an unlocked bootloader... indicated by an unlocked padlock symbol under the Google logo upon boot. If it isn't, you should unlock it with fastboot oem unlock BEFORE fastboot flashing the Custom Recovery).
My point is, though... the 'recovery.img' to be flashed must be in the same folder as the FASTBOOT.EXE file, or as you have discovered, you will get the error "Cannot open recovery-twrp-grouper.img".
If fastboot can't find it.. it can't open it.
Hope this helps.
Rgrds.
Ged.
Click to expand...
Click to collapse
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.
Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.
Anderson2 said:
Thank you very much! That is very helpful. I had assumed the recovery img should be on the tablet. No wonder fastboot could not find it! I'm sure that will solve my problem.
Thank you for helping. I'm slowly learning my way around the adb, fastboot commands as I'm sure I'll need them again when 4.4 unroots me again.
Click to expand...
Click to collapse
No, problem Anderson2... glad to help.
Adb and fastboot are indeed powerful and useful tools, and I would strongly recommend anybody wishing to 'modify' their Nexus 7 (everything from rooting to flashing Custom ROMs) to familiarise themselves with the fundamentals of their operation... rather than relying on toolkits.
There are actually ways of flashing TWRP or CWM Custom Recoveries directly from the Nexus 7 itself, without recourse to either fastboot or the need for a PC... by using apps like Flash Image GUI or Flashify. But these apps need you to be already rooted, unfortunately.
So to summarize how to acquire root the old fashioned way....
---------------------------------------
1). Unlock the bootloader first with fastboot oem unlock. For security reasons, this will factory reset the device... ie., WIPE everything on it.
...but I assume your Nexus 7's bootloader is already unlocked, given it's been rooted once before.
And so swiftly skipping forward to step 2...
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery recovery.img... where 'recovery.img' is the Custom Recovery of your choice. Reboot the device by using the Custom Recovery's own reboot option.
3). Download Chainfire's UPDATE-SuperSU-v1.65.zip root package directly to your Nexus 7. This DOES need to be on the Nexus 7. Most Android browsers (including Chrome) download stuff to the /download folder on the devices internal storage. You'll need to remember the location, for when you come to flash it with either CWM or TWRP.
4). Boot the Nexus 7 into the bootloader. Although you can do it with adb reboot bootloader, you can also do it manually as follows...
- Shut down the Nexus 7 completely.
- Press and hold the VOL-DOWN button... whilst holding, press the POWER-ON button for about 5-10 seconds. The device should now boot into the bootloader.
5). Boot into your Custom Recovery... whilst in the bootloader, use the VOL-KEYS to navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. The device will now boot into either CWM or TWRP Custom Recovery.... whichever one you fastboot flashed earlier.
6). Now to ROOT!
** If using TWRP... tap on the INSTALL button, and then navigate to the /download folder on the Nexus 7's internal storage, and where Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on it, and Swipe to Confirm Flash.
** If using CWM... tap on the INSTALL ZIP option, followed by CHOOSE ZIP FROM /SDCARD... tap on the folder 0/... this gives you access to the internal storage of the Nexus 7... from which you can navigate to the /download folder, where again, Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on NO (the first default option) or YES - Install UPDATE-SuperSU-v1.65.zip.
On every screen in the CWM filemanager (by which you navigate) there is ALWAYS a ++++Go Back++++ option at the bottom of the screen. So you can always backout out of anything. In CWM you can also use the VOL UP and DOWN keys to scroll, with the POWER-BUTTON to select an option.
Once you have flashed Chainfire's SuperSU root package, reboot the device with the Custom Recovery's own reboot option.
Upon reboot, and whichever Custom Recovery you're using , it ***MIGHT*** suggest you are unrooted... and offer to fix root for you. Ignore it, and continue to reboot.
---------------------------------------
And that's it... that's how you root a first generation Nexus 7 (2012).
Hope this is of use and... Good luck.
Rgrds,
Ged.
GedBlake said:
No, problem Anderson2... glad to help.
Adb and fastboot are indeed powerful and useful tools, and I would strongly recommend anybody wishing to 'modify' their Nexus 7 (everything from rooting to flashing Custom ROMs) to familiarise themselves with the fundamentals of their operation... rather than relying on toolkits.
There are actually ways of flashing TWRP or CWM Custom Recoveries directly from the Nexus 7 itself, without recourse to either fastboot or the need for a PC... by using apps like Flash Image GUI or Flashify. But these apps need you to be already rooted, unfortunately.
So to summarize how to acquire root the old fashioned way....
---------------------------------------
1). Unlock the bootloader first with fastboot oem unlock. For security reasons, this will factory reset the device... ie., WIPE everything on it. I assume your bootloader is already unlocked.
So swiftly skipping forward to step 2....
2). Fastboot flash a Custom Recovery (CWM or TWRP) with fastboot flash recovery recovery.img... where 'recovery.img' is the Custom Recovery of your choice. Reboot the device by using the Custom Recovery's own reboot option.
3). Download Chainfire's UPDATE-SuperSU-v1.65.zip root package directly to your Nexus 7. This DOES need to be on the Nexus 7. Most Android browsers (including Chrome) download stuff to the /download folder on the devices internal storage. You'll need to remember the location, for when you come to flash it with either CWM or TWRP.
4). Boot the Nexus 7 into the bootloader. Although you can do it with adb reboot bootloader, you can also do it manually as follows...
- Shut down the Nexus 7 completely.
- Press and hold the VOL-DOWN button... whilst holding, press the POWER-ON button for about 5-10 seconds. The device should now boot into the bootloader.
5). Boot into your Custom Recovery... whilst in the bootloader, use the VOL-KEYS to navigate to the RECOVERY MODE option, and press the POWER BUTTON to select. The device will now boot into either CWM or TWRP Custom Recovery.... whichever one you fastboot flashed earlier.
6). Now to ROOT!
** If using TWRP... tap on the INSTALL button, and then navigate to the /download folder on the Nexus 7's internal storage, and where Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on it, and Swipe to Confirm Flash.
** If using CWM... tap on the INSTALL ZIP option, followed by CHOOSE ZIP FROM /SDCARD... tap on the folder 0/... this gives you access to the internal storage of the Nexus 7... from which you can navigate to the /download folder, where again, Chainfires UPDATE-SuperSU-v1.65.zip is awaiting. Tap on NO (the first default option) or YES - Install UPDATE-SuperSU-v1.65.zip.
On every screen in the CWM filemanager (by which you navigate) there is ALWAYS a ++++Go Back++++ option at the bottom of the screen. So you can always backout out of anything. In CWM you can also use the VOL UP and DOWN keys to scroll, with the POWER-BUTTON to select an option.
Once you have flashed Chainfire's SuperSU root package, reboot the device with the Custom Recovery's own reboot option.
Upon reboot, and whichever Custom Recovery you're using , it ***MIGHT*** suggest you are unrooted... and offer to fix root for you. Ignore it, and continue to reboot.
---------------------------------------
And that's it... that's how you root a first generation Nexus 7 (2012).
Hope this is of use and... Good luck.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thank you all very much. I greatly appreciate your help.
This post should be a sticky!
One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?
Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.
Anderson2 said:
Thank you all very much. I greatly appreciate your help.
This post should be a sticky!
One more question, this nexus 7 2012 is my wife's. But I also own a nexus 7I this one a 2013 which is currently rooted with Android 4.3 and twrp Nandroid backups. I'm afraid that when the 4.4 ota upgrade comes along it might again unroot both our tablets. Are the rooting commands or procedures different for the 2013 nexus 7 (other than using a flo recovery img,) or do I do exactly the same as described above?
Again, you guys are wonderful to help us newbies out. Many thanks to all. Wish I could do something in return.
Click to expand...
Click to collapse
Hello again, Anderson2...
Well, you sort of are already doing something in return.... you're asking questions.
Questions that require answers. Those answers, whoever posts them, may be of assistance to somebody else. Somebody else looking for a solution to a similar problem.
I always look upon these forums as a means of sharing. Not everybody can know everything. God knows, I don't know everything.... and I've been messing around with Android for three years now. So don't worry so much about it being a quid pro quo sort of arrangement.
I know what I know primarily as a result of my own experiences and what I've learned here from the many (in most cases, more knowledgeable) posters here on XDA. What you learn today, you can pass on to others, tomorrow (metaphorically speaking). We, all of us, stand on the shoulders of each other.
With regard to the second generation Nexus 7 (2013)... I'm afraid I really don't know much about it... but I'd be surprised if rooting it deviated significantly from rooting the first generation Nexus 7....
Namely...
1). Unlock the bootloader.
2). Flash a Custom Recovery.
3). Using that Custom Recovery, flash some SU root package... probably from Chainfire.
Anyway, I've found this tutorial here...
http://forum.xda-developers.com/showthread.php?t=2382051
...and it appears to follow a very similar template.
The Nexus 7 (2013) forum itself, which is also worth visiting, is located here....
http://forum.xda-developers.com/nexus-7-2013
Rgrds,
Ged.
[GUIDE] [6.3.3] 1st Gen Kindle Drivers, Rooting, Bootloaders & Recovery, and OtterX
Hello everyone! I am new to working with the Kindle Fire, however, I am by no means new to rooting and tinkering with my devices. Yesterday, I inherited a Kindle Fire with software version 6.3.3 from my brother and I was completely unsure of how to root the device. I am writing this guide because many of the existing guides were unclear and lead me to screw up multiple times. In addition, some claimed to work with the 6.3.3 software version, however, they were designed for an older version of the firmware and would not actually work.
I WILL NOT BE HELD LIABLE IF YOU BRICK YOUR DEVICE USING THESE INSTRUCTIONS! FOLLOW ALL DIRECTIONS CAREFULLY AND REMEMBER TO BACKUP YOUR DATA! YOUR DATA WILL BE WIPED DURING THIS PROCESS. ONLY CONTINUE IF YOU UNDERSTAND THE RISKS! THESE INSTRUCTIONS ARE IN SEQUENTIAL ORDER, FOLLOW EACH STEP! YOU CANNOT SKIP ANY OF THE STEPS!
0. Checking MD5 Hashes
It is very important to check the MD5 hash of every file that you download for this guide. You may use your favorite MD5 checksum utility. Personally, I prefer using this tool created by Microsoft because it is lightweight and extremely fast. Unfortunately, it does take some knowledge of the Command Prompt to use. To begin, download the file and extract it to any folder that you would like. To use the tool, place the file that you are checking within the same folder as the tool. Then, hold shift on your keyboard and right click. Choose the option to open a new Command Prompt window. Then, issue the following commands:
Code:
fciv.exe <exact name of file you are checking>
This will tell you the MD5 checksum of the file that you are checking and you will want to compare it to the value that is listed with the download. Again, you will want to do this for every file that is downloaded for this guide to ensure that you do not damage your device or need to restart the process.
1. Drivers
One problem that I faced while rooting my Kindle Fire was the installation of drivers. Basically, this guide requires you to use unsigned drivers that Windows will refuse to install under normal circumstances. On Windows 8, Windows 8.1, and in the Windows 10 Technical preview, you need to enable Test Mode. Although you can just disable the driver signature verification for one boot, I found this inefficient because I needed to tinker with the drivers multiple times, with each successive installation requiring a reboot of the computer.
To enable Test Mode on Windows 8, Windows 8.1, and Windows 10 Technical Preview, you need some experience with the Command Prompt. Open an Administrative Command Prompt by typing "cmd" into the Start menu and right clicking on the Command Prompt icon. From there, choose the option to open the program with Administrative privileges. Then, issue the following commands:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Reboot your computer.
Next, you will want to download the KFU utility from this XDA developer thread. We will NOT be using the Kindle Fire Utility for this guide because I was unable to get it working with 6.3.3, instead we will be using the included set of drivers because they worked relatively well with this process. After downloading the latest version of KFU, extract it to a folder on your Desktop. Unplug your Kindle Fire if it is plugged in to your computer or the drivers may not install correctly. You will want to open the "install_drivers.bat" file and follow the prompts. One prompt will ask you if you want to run the unsigned driver, you should choose "Install this driver software anyway!". Please restart your computer before continuing with this guide!
Now, you may plug in your Kindle Fire. Before continuing, please ensure that the installation of applications is allowed on the device by opening the settings drop down, clicking "More", and clicking on "Device". From there, check the box that allows the installation of applications. Next, you will want to navigate to the folder in the "Kindle Fire Utility" called "Tools". From here, hold shift on your keyboard and right click. Then, choose the option to open a Command Prompt window. We are going to test to make sure that the Kindle Fire is recognized by the "adb" program. To do this, we are going to issue the following commands:
Code:
adb kill-server
adb usb
adb devices
If you typed these commands correctly, any old instances of the "adb" server will be destroyed. Then, it will start a new server that will work with USB devices. Finally, it will list the connected devices. If the driver installation has succeeded, you will see the serial number of your Kindle Fire as well as an "Online" status. If you do not see your device or it is not marked as "Online", you may need to repeat the steps for installing the drivers. Do NOT continue until these commands list your device as "Online" because it could theoretically damage the device. If you are unable to get these drivers working, I recommend using the GhostBuster utility to remove old Kindle Fire and Android phone drivers.
2. Rooting the Device
This is where you want to back up anything important on the device!
Since I was unable to find an official root method from the Kindle Fire community for patch 6.3.3, I looked into using other methods. Using SafeRoot was suggested by some people and it worked very well for my Kindle Fire. So, to continue, please download the SafeRoot package from this XDA Developers link. Extract these files to a folder of your choice, preferably somewhere that is easy to access. We are NOT using the Kindle Fire Utility for this step because it simply was not compatible with software version 6.3.3.
Now, run the "install.bat" file and follow ALL of the on-screen instructions. The utility will ask you if you wish to install Busybox on your device. Busybox is a powerful utility that combines many powerful Unix utilities into a single file. You can read more about it here. You will want to choose yes when it asks you if it can install Busybox. After following all of the instructions, you should have a SuperUser application on your device that allows you run root commands!
It is NORMAL for the SafeRoot utility to show a lot of errors towards the end relating to read only files. If there are any other errors, your device may not be rooted!
3. Flashing FFF and the TWRP Recovery (Non-OtterX)
First, you will want to download the FBMode file. This file will allow your device to boot into the Fastboot mode, which allows you to flash new bootloader and recovery images. In addition, you will want to download the FireFireFire bootloader image that we will be flashing to the device. You will also need a custom recovery for this device, which can be found here. If you ignore everything else in this guide, just please remember to MD5 check ALL of these files! This is extremely important because a bad flash could BRICK your device!
Extract each of these files to the "Tools" folder inside of the Kindle Fire Utility folder that we used earlier to install the driver. Again, open a Command Prompt window inside of the Tools folder by holding shift and right clicking, then choosing the option to open a new Command Prompt window. Type these commands EXACTLY to copy the "fbmode" file to the device. This file will put the device in Fastboot mode.
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell
You will notice that the Command Prompt window looks slightly different because we are now in a shell for the device. This means we are directly issuing commands to the device! Type the following commands exactly to reboot the device in Fastboot mode. Remember, the "exit" command will need to be typed TWICE!
Code:
su
cd /data/local/tmp
./fbmode
exit
exit
adb reboot
If you did everything correctly, you will now be in Fastboot mode! No, you did not brick your Kindle. The device will not boot into the OS until we tell it to so it WILL remain at the Kindle Fire logo indefinitely, even upon rebooting the device. Depending on your operating system, you may need to toy with the driver installation to 'see' the device again.
Test to make sure that the Kindle still responds to commands before continuing by issuing the following command within the same command prompt window that we used previously to copy the "fbmode" file.
Code:
fastboot -i 0x1949 reboot
The kindle should reboot into the Fastboot mode again! If not, please use this post to get the drivers working. In my case, the device responded to the reboot command, however, it did NOT show up when I checked the connected devices by issuing the following command:
Code:
fastboot -i 0x1949 devices
If all is well and the Kindle rebooted, it is time to flash the bootloader and recovery images! Remember to check the MD5 hash for these files! You WILL need to know the name of your recovery image, it should be named something very similar to "openrecovery-twrp-2.2.2.1-blaze.img".
This is NOT the FireFireFire file, which is named "fff-u-boot_v1.5.bin". DO NOT flash the FireFireFire file to the recovery partition! If you get any errors during this part of the process, DO NOT continue! You may brick your device!
Code:
fastboot -i 0x1949 flash recovery <REPLACE ME WITH THE NAME OF RECOVERY IMAGE FILE>
Next, we will flash the bootloader image! Issue the following command to the device using the same Command Prompt window that we used to flash the recovery image.
Code:
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
Now, we will take the device out of Fastboot mode and make sure that our flashes were successful! If you got any errors during the flashing process, DO NOT continue! You may brick your device!
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
When you reboot, you should get a new Kindle Fire logo that will be White & Blue. Follow the on-screen instructions to enter the Recovery mode and make sure that the Team Win Recovery image boots. If it does, congratulations! You now have a custom recovery and bootloader on your Kindle device!
4. Installing OtterX Bootloader and Recovery Images
Now that you have a custom bootloader and recovery image flashed, you can now experiment with the OtterX project if you wish. Remember that the OtterX project fundamentally alters the device and it may be extremely difficult to revert these changes to the device! OtterX recoveries, boot loaders, and ROMs are not compatible with stock recoveries, boot loaders, and ROMs. If you still wish to use the device as a Kindle, do not proceed!
Now that the disclaimer is out of the way, let's continue! To continue, you will need the OtterX Bootloader and a copy of the TWRP Recovery for OtterX (Fundamentally different than the TWRP recovery from the last step!). Again, REMEMBER TO CHECK THE MD5 CHECKSUMS OF THESE FILES! A corrupted file could brick your device!
To make sure that the wrong recovery and bootloader are not applied, delete the old copies from your Tools folder inside of the Kindle Fire Utility folder. Then, copy over the OtterX versions of the bootloader and recovery images. Again, open a Command Prompt window inside of the Tools folder by holding shift and right clicking, then choosing the option to open a new Command Prompt window. Enter the following commands exactly!
You will need to know the name of your bootloader file. It should be named similarly to "otterx-u-boot_v2.05.bin". Make sure it says OtterX in the name of the file! Power on the device to the Kindle Fire screen and issue the following command on your computer.
Code:
fastboot flash bootloader <Name of OtterX Bootloader File>
Now, reboot the device after the flash has fully completed! You should see a new boot logo, meaning that the flash was successful! Before we continue, we will need to change the partition layout of the device. This will erase all of your files that exist on the device, you should have backed then up a few steps ago! At the bootloader screen, short press the power button to enter the boot menu. Then, use short presses of the power button to navigate to the advanced menu. Then, use a long press to enter that menu. Now, use short presses to navigate down to the "Partition Mode" button and use a long press to enter the submenu. Use short presses to press the navigate down to the Confirm button, and finally use one last long press to start the process.
After this has been completed, reboot the device. Again at the Kindle Fire screen, enter the following command on your computer.
You will need to know the name of your recovery file. It should be named similarly to "otterx-twrp-2.7.1.0-recovery.img". Make sure it says OtterX in the name of the file!
Code:
fastboot flash recovery <Name of Recovery Image>
fastboot oem recovery
After issuing both commands, you should see the TWRP recovery screen again! If you do, congratulations! You have flashed the OtterX recovery and bootloader images to your device,
5. Installing OtterX ROMs
I have found that the easiest way to install ROMs to this device is through a function called "adb sideloading". To begin, you will need an OtterX ROM file. I personally recommend Cyanogenmod because it seems fairly stable on this tablet (with my few hours of experience) and I use it as a daily driver on my Galaxy S3.
To begin, grab a copy of ANY OtterX ROM file. You can download Cyanogenmod ROMs from this website. Next, you will also want to download a Google Apps package for your device. You can get that from this website as well.
From the TWRP recovery menu, select the "Wipe" option and then choose "Factory Reset". Follow the onscreen prompts to reset the files on your device. If you get any errors, mount the partitions shown in the "Mounts" menu on the main screen.
Next, go to the Advanced section and choose "ADB Sideload". You should choose the boxes to wipe both caches. To continue, you will need a more up-to-date version of the adb program. You will want just the SDK tools, not the full Android Studio. You can download those tools from this website. After the tools are installed, open up the SDK manager and choose the "Install x Packages" button at the bottom to update the tools. After this is complete, navigate to "C:\Program Files (x86)\Android\android-sdk\platform-tools" on your hard drive. If you are using a 32 bit computer, navigate to "C:\Program Files\Android\android-sdk\platform-tools". Copy your ROM image to this folder and rename it something easy to work with, such as "CM11-OtterX-M12.zip".
Now, you will want to slide the bar across on your device that says "Swipe to Sideload", as well as open a new Command Prompt window on your computer. You can do this by holding shift and right clicking "Open New Command Prompt Window". Now, you will want to issue the following command to make sure your computer can see your Kindle device.
Code:
adb devices
Your device serial number should be listed here and it should say "Sideload" next to the name.
Now, you will want to issue the following command:
Code:
adb sideload <Name of ROM File ZIP>
Now, you will need to wait about 5 minutes while your device is flashed with a new ROM. In my case, the ROM stopped flashing at around 47% with an "Unknown Command" error, however, my device finished the flash okay and the ROM booted just fine. As long as your TWRP recovery shows "Success!", the ROM flash was probably okay. If the ROM flash had failed, you would still be able to try the flash again without harming anything.
You can now go back to the main menu and choose to reboot your device. If the flash was successful, you should see a boot logo for whichever ROM you chose to install. Remember, the initial boot can take a long time.
After verifying that the ROM installed correctly, copy the Google Apps package to your device's internal storage. Depending on which ROM you used, the device should show up as an MTP compatible device in Windows when powered on. Then, reboot into the recovery menu and choose "Install". Then, choose the Google Apps package that you copied to the device to install them. Upon rebooting, the device will update roughly 30-50 apps depending on how much bloatware is installed with your ROM. After that is complete, you will have access to the Google Play store and many useful apps.
Congratulations, you just installed an OtterX rom onto your device!
We need a new update for 2016
ajwgeek said:
Hello everyone! I am new to working with the Kindle Fire, however, I am by no means new to rooting and tinkering with my devices. Yesterday, I inherited a Kindle Fire with software version 6.3.3 from my brother and I was completely unsure of how to root the device. I am writing this guide because many of the existing guides were unclear and lead me to screw up multiple times. In addition, some claimed to work with the 6.3.3 software version, however, they were designed for an older version of the firmware and would not actually work.
I WILL NOT BE HELD LIABLE IF YOU BRICK YOUR DEVICE USING THESE INSTRUCTIONS! FOLLOW ALL DIRECTIONS CAREFULLY AND REMEMBER TO BACKUP YOUR DATA! YOUR DATA WILL BE WIPED DURING THIS PROCESS. ONLY CONTINUE IF YOU UNDERSTAND THE RISKS! THESE INSTRUCTIONS ARE IN SEQUENTIAL ORDER, FOLLOW EACH STEP! YOU CANNOT SKIP ANY OF THE STEPS!
0. Checking MD5 Hashes
It is very important to check the MD5 hash of every file that you download for this guide. You may use your favorite MD5 checksum utility. Personally, I prefer using this tool created by Microsoft because it is lightweight and extremely fast. Unfortunately, it does take some knowledge of the Command Prompt to use. To begin, download the file and extract it to any folder that you would like. To use the tool, place the file that you are checking within the same folder as the tool. Then, hold shift on your keyboard and right click. Choose the option to open a new Command Prompt window. Then, issue the following commands:
Code:
fciv.exe <exact name of file you are checking>
This will tell you the MD5 checksum of the file that you are checking and you will want to compare it to the value that is listed with the download. Again, you will want to do this for every file that is downloaded for this guide to ensure that you do not damage your device or need to restart the process.
1. Drivers
One problem that I faced while rooting my Kindle Fire was the installation of drivers. Basically, this guide requires you to use unsigned drivers that Windows will refuse to install under normal circumstances. On Windows 8, Windows 8.1, and in the Windows 10 Technical preview, you need to enable Test Mode. Although you can just disable the driver signature verification for one boot, I found this inefficient because I needed to tinker with the drivers multiple times, with each successive installation requiring a reboot of the computer.
To enable Test Mode on Windows 8, Windows 8.1, and Windows 10 Technical Preview, you need some experience with the Command Prompt. Open an Administrative Command Prompt by typing "cmd" into the Start menu and right clicking on the Command Prompt icon. From there, choose the option to open the program with Administrative privileges. Then, issue the following commands:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Reboot your computer.
Next, you will want to download the KFU utility from this XDA developer thread. We will NOT be using the Kindle Fire Utility for this guide because I was unable to get it working with 6.3.3, instead we will be using the included set of drivers because they worked relatively well with this process. After downloading the latest version of KFU, extract it to a folder on your Desktop. Unplug your Kindle Fire if it is plugged in to your computer or the drivers may not install correctly. You will want to open the "install_drivers.bat" file and follow the prompts. One prompt will ask you if you want to run the unsigned driver, you should choose "Install this driver software anyway!". Please restart your computer before continuing with this guide!
Now, you may plug in your Kindle Fire. Before continuing, please ensure that the installation of applications is allowed on the device by opening the settings drop down, clicking "More", and clicking on "Device". From there, check the box that allows the installation of applications. Next, you will want to navigate to the folder in the "Kindle Fire Utility" called "Tools". From here, hold shift on your keyboard and right click. Then, choose the option to open a Command Prompt window. We are going to test to make sure that the Kindle Fire is recognized by the "adb" program. To do this, we are going to issue the following commands:
Code:
adb kill-server
adb usb
adb devices
If you typed these commands correctly, any old instances of the "adb" server will be destroyed. Then, it will start a new server that will work with USB devices. Finally, it will list the connected devices. If the driver installation has succeeded, you will see the serial number of your Kindle Fire as well as an "Online" status. If you do not see your device or it is not marked as "Online", you may need to repeat the steps for installing the drivers. Do NOT continue until these commands list your device as "Online" because it could theoretically damage the device. If you are unable to get these drivers working, I recommend using the GhostBuster utility to remove old Kindle Fire and Android phone drivers.
2. Rooting the Device
This is where you want to back up anything important on the device!
Since I was unable to find an official root method from the Kindle Fire community for patch 6.3.3, I looked into using other methods. Using SafeRoot was suggested by some people and it worked very well for my Kindle Fire. So, to continue, please download the SafeRoot package from this XDA Developers link. Extract these files to a folder of your choice, preferably somewhere that is easy to access. We are NOT using the Kindle Fire Utility for this step because it simply was not compatible with software version 6.3.3.
Now, run the "install.bat" file and follow ALL of the on-screen instructions. The utility will ask you if you wish to install Busybox on your device. Busybox is a powerful utility that combines many powerful Unix utilities into a single file. You can read more about it here. You will want to choose yes when it asks you if it can install Busybox. After following all of the instructions, you should have a SuperUser application on your device that allows you run root commands!
It is NORMAL for the SafeRoot utility to show a lot of errors towards the end relating to read only files. If there are any other errors, your device may not be rooted!
3. Flashing FFF and the TWRP Recovery (Non-OtterX)
First, you will want to download the FBMode file. This file will allow your device to boot into the Fastboot mode, which allows you to flash new bootloader and recovery images. In addition, you will want to download the FireFireFire bootloader image that we will be flashing to the device. You will also need a custom recovery for this device, which can be found here. If you ignore everything else in this guide, just please remember to MD5 check ALL of these files! This is extremely important because a bad flash could BRICK your device!
Extract each of these files to the "Tools" folder inside of the Kindle Fire Utility folder that we used earlier to install the driver. Again, open a Command Prompt window inside of the Tools folder by holding shift and right clicking, then choosing the option to open a new Command Prompt window. Type these commands EXACTLY to copy the "fbmode" file to the device. This file will put the device in Fastboot mode.
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell
You will notice that the Command Prompt window looks slightly different because we are now in a shell for the device. This means we are directly issuing commands to the device! Type the following commands exactly to reboot the device in Fastboot mode. Remember, the "exit" command will need to be typed TWICE!
Code:
su
cd /data/local/tmp
./fbmode
exit
exit
adb reboot
If you did everything correctly, you will now be in Fastboot mode! No, you did not brick your Kindle. The device will not boot into the OS until we tell it to so it WILL remain at the Kindle Fire logo indefinitely, even upon rebooting the device. Depending on your operating system, you may need to toy with the driver installation to 'see' the device again.
Test to make sure that the Kindle still responds to commands before continuing by issuing the following command within the same command prompt window that we used previously to copy the "fbmode" file.
Code:
fastboot -i 0x1949 reboot
The kindle should reboot into the Fastboot mode again! If not, please use this post to get the drivers working. In my case, the device responded to the reboot command, however, it did NOT show up when I checked the connected devices by issuing the following command:
Code:
fastboot -i 0x1949 devices
If all is well and the Kindle rebooted, it is time to flash the bootloader and recovery images! Remember to check the MD5 hash for these files! You WILL need to know the name of your recovery image, it should be named something very similar to "openrecovery-twrp-2.2.2.1-blaze.img".
This is NOT the FireFireFire file, which is named "fff-u-boot_v1.5.bin". DO NOT flash the FireFireFire file to the recovery partition! If you get any errors during this part of the process, DO NOT continue! You may brick your device!
Code:
fastboot -i 0x1949 flash recovery <REPLACE ME WITH THE NAME OF RECOVERY IMAGE FILE>
Next, we will flash the bootloader image! Issue the following command to the device using the same Command Prompt window that we used to flash the recovery image.
Code:
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
Now, we will take the device out of Fastboot mode and make sure that our flashes were successful! If you got any errors during the flashing process, DO NOT continue! You may brick your device!
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
When you reboot, you should get a new Kindle Fire logo that will be White & Blue. Follow the on-screen instructions to enter the Recovery mode and make sure that the Team Win Recovery image boots. If it does, congratulations! You now have a custom recovery and bootloader on your Kindle device!
4. Installing OtterX Bootloader and Recovery Images
Now that you have a custom bootloader and recovery image flashed, you can now experiment with the OtterX project if you wish. Remember that the OtterX project fundamentally alters the device and it may be extremely difficult to revert these changes to the device! OtterX recoveries, boot loaders, and ROMs are not compatible with stock recoveries, boot loaders, and ROMs. If you still wish to use the device as a Kindle, do not proceed!
Now that the disclaimer is out of the way, let's continue! To continue, you will need the OtterX Bootloader and a copy of the TWRP Recovery for OtterX (Fundamentally different than the TWRP recovery from the last step!). Again, REMEMBER TO CHECK THE MD5 CHECKSUMS OF THESE FILES! A corrupted file could brick your device!
To make sure that the wrong recovery and bootloader are not applied, delete the old copies from your Tools folder inside of the Kindle Fire Utility folder. Then, copy over the OtterX versions of the bootloader and recovery images. Again, open a Command Prompt window inside of the Tools folder by holding shift and right clicking, then choosing the option to open a new Command Prompt window. Enter the following commands exactly!
You will need to know the name of your bootloader file. It should be named similarly to "otterx-u-boot_v2.05.bin". Make sure it says OtterX in the name of the file! Power on the device to the Kindle Fire screen and issue the following command on your computer.
Code:
fastboot flash bootloader <Name of OtterX Bootloader File>
Now, reboot the device after the flash has fully completed! You should see a new boot logo, meaning that the flash was successful! Before we continue, we will need to change the partition layout of the device. This will erase all of your files that exist on the device, you should have backed then up a few steps ago! At the bootloader screen, short press the power button to enter the boot menu. Then, use short presses of the power button to navigate to the advanced menu. Then, use a long press to enter that menu. Now, use short presses to navigate down to the "Partition Mode" button and use a long press to enter the submenu. Use short presses to press the navigate down to the Confirm button, and finally use one last long press to start the process.
After this has been completed, reboot the device. Again at the Kindle Fire screen, enter the following command on your computer.
You will need to know the name of your recovery file. It should be named similarly to "otterx-twrp-2.7.1.0-recovery.img". Make sure it says OtterX in the name of the file!
Code:
fastboot flash recovery <Name of Recovery Image>
fastboot oem recovery
After issuing both commands, you should see the TWRP recovery screen again! If you do, congratulations! You have flashed the OtterX recovery and bootloader images to your device,
5. Installing OtterX ROMs
I have found that the easiest way to install ROMs to this device is through a function called "adb sideloading". To begin, you will need an OtterX ROM file. I personally recommend Cyanogenmod because it seems fairly stable on this tablet (with my few hours of experience) and I use it as a daily driver on my Galaxy S3.
To begin, grab a copy of ANY OtterX ROM file. You can download Cyanogenmod ROMs from this website. Next, you will also want to download a Google Apps package for your device. You can get that from this website as well.
From the TWRP recovery menu, select the "Wipe" option and then choose "Factory Reset". Follow the onscreen prompts to reset the files on your device. If you get any errors, mount the partitions shown in the "Mounts" menu on the main screen.
Next, go to the Advanced section and choose "ADB Sideload". You should choose the boxes to wipe both caches. To continue, you will need a more up-to-date version of the adb program. You will want just the SDK tools, not the full Android Studio. You can download those tools from this website. After the tools are installed, open up the SDK manager and choose the "Install x Packages" button at the bottom to update the tools. After this is complete, navigate to "C:\Program Files (x86)\Android\android-sdk\platform-tools" on your hard drive. If you are using a 32 bit computer, navigate to "C:\Program Files\Android\android-sdk\platform-tools". Copy your ROM image to this folder and rename it something easy to work with, such as "CM11-OtterX-M12.zip".
Now, you will want to slide the bar across on your device that says "Swipe to Sideload", as well as open a new Command Prompt window on your computer. You can do this by holding shift and right clicking "Open New Command Prompt Window". Now, you will want to issue the following command to make sure your computer can see your Kindle device.
Code:
adb devices
Your device serial number should be listed here and it should say "Sideload" next to the name.
Now, you will want to issue the following command:
Code:
adb sideload <Name of ROM File ZIP>
Now, you will need to wait about 5 minutes while your device is flashed with a new ROM. In my case, the ROM stopped flashing at around 47% with an "Unknown Command" error, however, my device finished the flash okay and the ROM booted just fine. As long as your TWRP recovery shows "Success!", the ROM flash was probably okay. If the ROM flash had failed, you would still be able to try the flash again without harming anything.
You can now go back to the main menu and choose to reboot your device. If the flash was successful, you should see a boot logo for whichever ROM you chose to install. Remember, the initial boot can take a long time.
After verifying that the ROM installed correctly, copy the Google Apps package to your device's internal storage. Depending on which ROM you used, the device should show up as an MTP compatible device in Windows when powered on. Then, reboot into the recovery menu and choose "Install". Then, choose the Google Apps package that you copied to the device to install them. Upon rebooting, the device will update roughly 30-50 apps depending on how much bloatware is installed with your ROM. After that is complete, you will have access to the Google Play store and many useful apps.
Congratulations, you just installed an OtterX rom onto your device!
Click to expand...
Click to collapse
We need new links for kindle fire first gen 6.3.4 . these methods available don't work. thank you
ataraxioss said:
We need new links for kindle fire first gen 6.3.4 . these methods available don't work. thank you
Click to expand...
Click to collapse
no, this still works with 6.3.4
Sent from my KFFOWI using Tapatalk
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
there is one link to goo.im which is down
With the Fall of Goo.im I will be posting Mirrors OtterX files here:
Otter X Twrp and Bootloader Mirrors
Sent from my KFFOWI using Tapatalk
I've just tried it
Still not working on my kindle fire. sounds to be rooted but can't install twrp.
i was hoping to flash it with Miui 7.
thank you for your precious time, i wish the old links in kindle fire utility could still work.
ataraxioss said:
Still not working on my kindle fire. sounds to be rooted but can't install twrp.
i was hoping to flash it with Miui 7.
thank you for your precious time, i wish the old links in kindle fire utility could still work.
Click to expand...
Click to collapse
did you verify root? try root checker
Sent from my KFFOWI using Tapatalk
reply
sd_shadow said:
did you verify root? try root checker
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
once it is frozen on "trying to disable knox.." nothing goes right after that. the kindle fire does not reboot and i guess supersu is not updating either.
Ps: i have rooted and installed twrp many times before, then i did a factory reset on the kindle fire.
ataraxioss said:
once it is frozen on "trying to disable knox.." nothing goes right after that. the kindle fire does not reboot and i guess supersu is not updating either.
Ps: i have rooted and installed twrp many times before, then i did a factory reset on the kindle fire.
Click to expand...
Click to collapse
Factory reset doesn't unroot, just reinstall supersu app
Sent from my XT1060 using Tapatalk
So I got up to this point.
Test to make sure that the Kindle still responds to commands before continuing by issuing the following command within the same command prompt window that we used previously to copy the "fbmode" file.
Code:
fastboot -i 0x1949 reboot
The kindle should reboot into the Fastboot mode again! If not, please use this post to get the drivers working. In my case, the device responded to the reboot command, however, it did NOT show up when I checked the connected devices by issuing the following command:
Code:
fastboot -i 0x1949 devices
If all is well and the Kindle rebooted, it is time to flash the bootloader and recovery images! Remember to check the MD5 hash for these files! You WILL need to know the name of your recovery image, it should be named something very similar to "openrecovery-twrp-2.2.2.1-blaze.img". "
Click to expand...
Click to collapse
The kindle won't restart. When I plug it into my computer I get the error "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." The kindle is stuck on the start up screen where it says "Kindle Fire." Any help would be greatly appreciated. I know nothing about any of this stuff so I am stumped from here on out.
Also nothing is showing up in device manager that is related to the Kindle.
thealy1234 said:
So I got up to this point.
Test to make sure that the Kindle still responds to commands before continuing by issuing the following command within the same command prompt window that we used previously to copy the "fbmode" file.
Code:
fastboot -i 0x1949 reboot
The kindle should reboot into the Fastboot mode again! If not, please use this post to get the drivers working. In my case, the device responded to the reboot command, however, it did NOT show up when I checked the connected devices by issuing the following command:
Code:
fastboot -i 0x1949 devices
If all is well and the Kindle rebooted, it is time to flash the bootloader and recovery images! Remember to check the MD5 hash for these files! You WILL need to know the name of your recovery image, it should be named something very similar to "openrecovery-twrp-2.2.2.1-blaze.img". "
The kindle won't restart. When I plug it into my computer I get the error "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." The kindle is stuck on the start up screen where it says "Kindle Fire." Any help would be greatly appreciated. I know nothing about any of this stuff so I am stumped from here on out.
Also nothing is showing up in device manager that is related to the Kindle.
Click to expand...
Click to collapse
try a different USB port or cable
Sent from my Motorola XT1060 using XDA Labs
sd_shadow said:
try a different USB port or cable
Sent from my Motorola XT1060 using XDA Labs
Click to expand...
Click to collapse
This was the problem. Turns out this doesn't work when the kindle is plugged into a USB 3.0 port.
That being solved, I now have a different problem. I get the following error when I try and push the recovery image onto my kindle after I added the Otterbox bootloader file: "target reported max download size of 402653184 bytes error: cannot load 'recovery.img': No error."
(I renamed the file to recovery.img on the advice of someone else)
Also note that I had to get the otter recovery image from a different source than what was listed in the guide, for the provided link was broken.
Any ideas would be appreciated.
Thanks
thealy1234 said:
This was the problem. Turns out this doesn't work when the kindle is plugged into a USB 3.0 port.
That being solved, I now have a different problem. I get the following error when I try and push the recovery image onto my kindle after I added the Otterbox bootloader file: "target reported max download size of 402653184 bytes error: cannot load 'recovery.img': No error."
(I renamed the file to recovery.img on the advice of someone else)
Also note that I had to get the otter recovery image from a different source than what was listed in the guide, for the provided link was broken.
Any ideas would be appreciated.
Thanks
Click to expand...
Click to collapse
[6.3.4][6.3.3] Flashing FFF and TWRP without Fastboot Cable with Video
Sent from my XT1060 using Tapatalk
sd_shadow said:
[6.3.4][6.3.3] Flashing FFF and TWRP without Fastboot Cable with Video
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I have followed that guide to the T and I still get that error. It worked just fine when I was installed the TWRP recovery.
For some reason when I am trying to install the otterx twrp version, I am getting that error returned to me.
thealy1234 said:
I have followed that guide to the T and I still get that error. It worked just fine when I was installed the TWRP recovery.
For some reason when I am trying to install the otterx twrp version, I am getting that error returned to me.
Click to expand...
Click to collapse
try OtterX bootloader and OtterX twrp from my post
OtterX files here:
Otter X Twrp and Bootloader Mirrors
Sent from my XT1060 using Tapatalk
The 2.8.5.0 file that you provide worked. One more step closer...
I appreciate the help.
---------- Post added at 10:45 PM ---------- Previous post was at 10:26 PM ----------
I just can't win today.
Now I am stuck because TWRP cannot mount /data for some reason...
thealy1234 said:
The 2.8.5.0 file that you provide worked. One more step closer...
I appreciate the help.
---------- Post added at 10:45 PM ---------- Previous post was at 10:26 PM ----------
I just can't win today.
Now I am stuck because TWRP cannot mount /data for some reason...
Click to expand...
Click to collapse
mount data is ify with OtterX, try adb push with OtterX twrp 2.7.1.0
---------- Post added at 01:11 AM ---------- Previous post was at 01:10 AM ----------
Started a Thread [How To] Fix OtterX Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
After your help + plenty of head scratching I finally managed to install everything 100%.
Biggest hangup was before I realized this process wouldn't work on a USB 3.0 port....
I'm having an issue with being able to actually install drivers on my computer with Windows 10. I attempted to follow the guide but I am getting denied on an error with "bcdedit -set TESTSINGING ON".
"An error has occurred setting the element data. The value is protected by Secure Boot policy and cannot be modified or deleted."
Any advice for a workaround on installing the drivers?
I have been asked to port my "Beginners Guide" from the TF700 forum for the TF300. Since both tablets are very similar, that was not too hard to do
If I have missed to update a link specific for the TF300, do let me know please.
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
These instructions assume that you are on the latest Asus bootloader: 10.6.1.27.5
To determine which bootloader you currently have:
From an "Off" state, boot the tablet with Volume Down and Power into the bootloader menu. Read the small script in the upper left. You'll see
US_epad-10.6.1.27.5-20130801" or similar.
US or WW, JP, CN is your SKU or region
10.6.1.27.5 is your bootloader version
20130801 is the build date (and immaterial in most cases).
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
This is just common sense. It is not inherently risky to flash custom ROMs. But something can wrong at any time and you have to be careful. If you are, this is a safe procedure.
Basically the process of flashing a custom ROM on the TF300 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recovery
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Go to Asus website: https://www.asus.com/support/Download/28/1/0/9/8BmzkQ4yoz5WzBrW/32/
Choose "Android" for OS and look for the "Utilities" on the resulting page.
Download the Asus Unlock Tool v7 (not v8! It says v7 is for ICS but it'll work fine on JB - see below)
The tool downloads as a .rar file which is an archive you have to decompress. 7zip is a free and very good Windows tool that will do it for you
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk you extracted from the .rar archive to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
Update 2/15: Google added another wrinkle: It now checks even sideloaded apps and refuses to install them if they are considered not secure. The Unlock tool seems to fail their test. v8 does not install at all anymore. v7 will install if you allow "less secure apps" in your Google account settings. On the web - not your Google account on the tablet
July 2015: And another wrinkel... It seems to be pretty consistent now that the Unlock Tool hangs on the Google account password step. I suspect something changed on the Google side. It probably doesn't allow the tool to check/compare the password anymore. There have been quite a few security changes lately and the unlock tool never gets updated so I suspect that Google now is blocking access by the tool to it's servers.
The work-around is easy enough: Delete the Google account from the tablet (Settings > Accounts), then run the tool again. If that doesn't do it, do a factory reset from Settings, reboot and during the initial setup establish a WiFi connection but skip the google account setup, then run the tool
Click to expand...
Click to collapse
This can be a 5 Minute operation that goes without a hitch or a very frustrating experience with lots of error messages. There is no definite rhyme or reason for this. For some people it works like a charm, for others it works after 15, 25 or 55 attempts, for some never.... This problem is widely discussed on several forums. Google it if you hit that roadblock.
To check if you are unlocked, boot the tablet and read the tiny script. It should say:
The device is unlocked.
Installing a custom recovery on your tablet
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up. Try it but do not push Volume Up when the 'Wipe data' icon is flashing!
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it to get the drivers, then uninstall the program from your PC if you don't want it. The drivers will stay.
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows Vista, 7, 8, 10:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for adb) and the corresponding drivers. Takes about 15 seconds.
On Windows 8 and 10 you need to turn off the driver verification feature. Here's a great video on how to do it:
https://www.youtube.com/watch?v=afrvSGiMAtk
Or - even better - here's a quick command line toggle to achieve the same (thank you @Jack_Hardin):
Jack_Hardin said:
If you're running W10, you can disable Device Driver Signing without following the procedure in the linked video, but by (more simply) right-clicking on the Start button, selecting Command Prompt (Admin) and then typing:
Code:
BCDEDIT /set nointegritychecks ON
Doing the same with OFF at the end of the string, as easy to guess as it looks, will reenable them.
Click to expand...
Click to collapse
Jack_Hardin said:
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Win7 and Win8 users seem to have the best luck wth the drivers sbdags provided here: http://forum.xda-developers.com/showthread.php?t=2646279
It's fine if you want to use his Recovery Install Tool from that thread. But I highly recommend you familiarize yourself with basic fastboot commands! There are lots of tuturials all over the web.
Linux:Check out this site https://code.google.com/p/adb-fastboot-install/
iOS:[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers or:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
The fun begins
Fastboot does not play well with USB 3.0, so use a USB 2.0 port for this. And no hubs and such....
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8: Shift + right click and select "Open command window here".
For Win XP click here
select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
Click me: View attachment 3070087
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the drivers I linked to above. And if Windows does not cooperate at all, PM me and I can hook you up with a Puppy Linux live CD with fastboot/adb set up already.
Let's assume everything is good:
On your computer go here: https://dl.twrp.me/tf300t/
Download the latest version of TWRP.
FYI ONLY: If, for whatever reason, you want to format your data partition:
Formatting /data starting with TWRP 2.7.x and later takes a lot longer than in previous versions (up to 90 minutes). LET IT FINISH. DO NOT INTERRUPT THE FORMATTING.
Rename the file to twrp.blob and place it into the same directory as your fastboot.exe. Note: More recent versions of TWRP download with an .img extension. Leave the extensions as is, rename the first part to watever is easy to type
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
or
Code:
fastboot -i 0x0B05 flash recovery twrp.img
This will flash the recovery to the recovery partition
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
You may get a dialog in TWRP offering to root the stock rom. You can accept or cancel it - doesn't matter. I assume you are going to install a custom rom and they are rooted anyway.
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet. TWRP is very user friendly. You basically cannot do anything of consequence "by accident", so don't be shy.
To create your Nandroid (a full system backup) touch "Backup", leave the default selection as they are and swipe the button to create a nandroid of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Hint:
It's a good idea to have at least one good nandroid on external media. Sooner or later you will format your data partition and if you're like me, you may forget to backup your nandroids in the heat of the moment..
Installing a custom ROM
From here on out it's as easy as downloading the installation file of your custom ROM, booting into TWRP, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you see a "signed" in the zip file name (best_rom_ever_signed.zip), make sure you check "verify zip signature" under the "Install" menu. Some devs sign their ROM zips - a better way to ensure file integrity than md5 sum.
Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: http://forum.xda-developers.com/transformer-tf300t/development
It is mandatory to do a Factory Wipe in TWRP before installing a custom ROM or going from one ROM base to another (a so called clean install).
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES - AND I REPEAT: NEVER! - use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
FREE ADVICE
There are alternative methods to flash a recovery to your device using apps like GooManager (currently not supported anyway), TWRP Manager or Flashify from the Play Store which do it right from your tablet. These apps "save you the trouble" of getting ADB and fastboot set up and working on your PC. These methods still exist and they do work - mostly - and if you have root. But I would not recommend them.
If you are not willing to invest the time to learn the basics about ADB and fastboot (google "adb fastboot xda tutorial") and install the necessary drivers on your PC, you should not be flashing anything to your tablet!
GET ADB AND FASTBOOT WORKING!
Sooner or later you will do something stupid (I have done it and so will you) and ADB/fastboot may save your bacon IF you had it working when you didn't really need it.
Hit the 'Thanks' button and rate the thread 5 stars if this helped you
Click to expand...
Click to collapse
Save it for later
Mine
sbdags said:
@stamatis could we sticky this please.
Brilliant post Bernd :good:
Click to expand...
Click to collapse
Can we make that happen here to @stamatis
Thx Josh
Nice one Bernd! :good::good:
boot sequence
Hi,
Is normal to see three TUX and some phrases at the power on ?
Can I hide it ?
tnkx
Nicola
You mean the penguins?
That's normal I'd you're running a Rom that uses _that's preinit scripts. You can't hide them - why would you?
thank you SO much
I love you!
Wow, I've never had so much trouble rooting a device before! And days ago, I rooted my T700 without any problems. So, I guess I should have expected the hubby's TF300T to be problematic! Recoveries didn't work, I tried multiple ones. Eventually, I had a recovery that didn't recognize any partitions. I used fastboot to erase them all and put the stock ROM back on--wouldn't boot up. This thread was an immense help! I've moved the other recoveries and ROMs into my non-working folder!
Thanks again!
Lynne
Awesome
What a well written guide! I have a decent understanding of fastboot and adb (although minimal experience), and I perfectly understood every step.
My advice to all newbies like me.... Read stuff ALL of the way through (and understand it), BEFORE stepping off in it.
ok im a bit lost... i have rooted both Nexus 7s, nook hd and hd+, a tf101, and a few tv boxes.. so im not sure why this is hanging up... im trying to root and install the TWRP recovery on a tf300... followed the instructions and even have the char string that means... every thing should be good to go.... have checked that the twrp is in the dir of adb... but when i try to push the twrp.blob to the tf300, it just give me.. this error..
c:\adb>fastboot devices
015d14febf64041b fastboot
c:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6800 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
so.. at this point i not sure what else to trouble shoot... the tablet is in fastboot mode.. adb sees the tablet.. at least that is what the char string confirms.... so any help would be very much appreciated.. just a bit lost on this...
chris
scuzzo said:
ok im a bit lost... i have rooted both Nexus 7s, nook hd and hd+, a tf101, and a few tv boxes.. so im not sure why this is hanging up... im trying to root and install the TWRP recovery on a tf300... followed the instructions and even have the char string that means... every thing should be good to go.... have checked that the twrp is in the dir of adb... but when i try to push the twrp.blob to the tf300, it just give me.. this error..
c:\adb>fastboot devices
015d14febf64041b fastboot
c:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6800 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
so.. at this point i not sure what else to trouble shoot... the tablet is in fastboot mode.. adb sees the tablet.. at least that is what the char string confirms.... so any help would be very much appreciated.. just a bit lost on this...
chris
Click to expand...
Click to collapse
The bootloader is unlocked yes ?
What is your bootloader version ?
Try a different USB port ?
Thx Josh
lj50036 said:
The bootloader is unlocked yes ?
What is your bootloader version ?
Try a different USB port ?
Thx Josh
Click to expand...
Click to collapse
hello,
bootloader is unlocked or at least it says it is at the boot screen.. "your device is unlocked"..
real time... just swapped ports... its says it pushed the recovery.... so... will continue along this path.... and see how it goes.... i think its good to go... just as you suggested... port swap... cool... i bought this just so i could root it and put the kit kat kis rom on it.... thanks for your help and big ups to OP.... great guide ...
thanks again.!
Nice guide!
I've been wanting to put a custom rom on my transformer for a long time. This guide worked like a charm.
The only problem I had was when I tried to flash TWRP recovery, but switching USB port fixed that problem.
I flashed the latest CM12.1 nightly and it works fine.
Many thanks!
Help please, I'm stuck!
I'm trying to flash recovery,
after typing:
fastboot -i 0x0B05 flash recovery twrp.blob
I got this on tablet screen:
"Starting Fastboot USB download protocol"
for about 25-30 already and nothing happens, any ideas?
thanks
You won't see anything on the tablet screen, but what does the command window say?
Go back, read the guide again, it's all in there....
Sent from my K00C using Tapatalk
berndblb said:
You won't see anything on the tablet screen, but what does the command window say?
The command window didn't say anything, just blinking cursor after my command line
Go back, read the guide again, it's all in there....
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Mishka79 said:
I'm trying to flash recovery,
after typing:
fastboot -i 0x0B05 flash recovery twrp.blob
I got this on tablet screen:
"Starting Fastboot USB download protocol"
for about 25-30 already and nothing happens, any ideas?
thanks
Click to expand...
Click to collapse
Thanks,
After writing the question, I've restarted my tablet and did all the steps again.
The second time everything worked as it should. :good:
thanks for your great guide
Really great guide
Amazing guide thanks for the help
Thank you for this good tutorial but I have one question.
I'm a newbie here, here is my dilemma: I've flashed CM android 5.1.1 successfully from stock 4.2. (Thanks for this detailed tutorial), but I lost my root privileges, now I can't use my root apps. How do I apply root to this ROM? My device is an ASUS TF300T. I've tried Kingo Root and King Root but no success.
I would really appreciate your help and inputs.
Cheers!
ANDROIDYER said:
I'm a newbie here, here is my dilemma: I've flashed CM android 5.1.1 successfully from stock 4.2. (Thanks for this detailed tutorial), but I lost my root privileges, now I can't use my root apps. How do I apply root to this ROM? My device is an ASUS TF300T. I've tried Kingo Root and King Root but no success.
I would really appreciate your help and inputs.
Cheers!
Click to expand...
Click to collapse
I have not used CM in quite a while but I think you have to enable root in Developer Options. I think it is not enabled by default.
If hat does not work you can go to Chainfire's website and download the flashable SuperSU and just flash it in recovery
Thanks and a couple of notes on TF300T
Thanks so much for the great guide. My 300TF was nearly bricked due to slowness and freeze-ups. I'd stopped using it. The process worked and am now running KatKiss. Couple of problems and their solutions for anyone who may have the 300TF:
-When trying to "Unlock Bootloader" I kept getting to "enter Google password" but when I did so (correctly) it was not accepted. The solution was to do another factory reset and NOT install google services. Didn't ask for password after that.
-Used fastboot command line to install "twrp.blob" but nothing happened and it timed out. I had to take out other usb connect programs first (in my case "easy-tether" and my LG phone connect app.) After that everything went as per your guide.
Thanks again
Geneg
Hey Everybody!
I do have the following problem:
About a year ago, my Zuk Z1 lost both IMEIs. At that time I didn't know much about Android, TWRP, ADB, Qualcomm diagnostics ports etc... I learned as I went along on my journey to restore my modem connections. Unfortunately, while I tried different things I flashed one or more wrong images onto my Z1. At that time I gave up and put the phone away.
Recently, I dug it up again and while I do now know a little more about the inner workings of this phone and Android in general, I cannot get the diagnostic port 0x9008 or even the vendor ID 0x2b4c to show up under my PC.
Symptoms:
- when in Fastboot, the device registers as "unknown" usb device in windows (and as 0000:0000 in linux)
- I can set the device to register as 0x05c6 0x902d when booting into Android (NucleaROM V3.0.0 [6.0.1]), going to terminal and issuing "setprop sys.usb.config rndis,diag,adb" as root (via the terminal command "su"), but that port results in an error ("failed to enter edl mode") when trying to flash the recovery CM12.1 via QFIL (from this tutorial: androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/ )
- I can still access the phone from windows via adb (I can connect via "adb shell")
- I can still flash roms via TWRP (version 3.0.2-0)
I am about to try using the "dd" command to try to manually write the files (e.g. boot.img, emmc_appsboot.mbn, NON-HLOS.bin, etc...) from one of the recovery roms I have ("cm-12.1-20150903-EXPERIMENTAL-YOG4PAP25I-ham-signed-factory-f68f53c14c") to the partitions listed in the "partitions.xml" file therein. (I cannot use TWRP to install this rom, because it seems to be not an update (?) and there is no "META-INF/com/google/android/update-binary" file...)
My question is now: Does using "dd" to write the partitions manually work (I don't want to completely break the partitions, so I would like to have an opinion from someone who has more knowledge in this than me... )? If so, what would I need to do (e.g. under the TWRP terminal the partitons seem to be read-only, as "dd" there gives me "permission denied"; how and where do I proceed: from within Android under terminal or is there a way to do that from TWRP (terminal)? how do I remove write protection? etc.)?
If the "dd"-way does not work or if there is a better way (remember: fastboot does not work) how else can I restore the affected partitions (e.g. via "adb"? or a completely different way?)?
Do you need any other infos (command-outputs, etc.)?
Thanks for any help! I am happy about any hint you may give me!
Best regards,
ts101
Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...
Let me link you my ingenious, allmighty Axon 7 Companion Thread.
Try to install twrp with MiFlash if you can enter edl mode
macerf said:
Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...
Click to expand...
Click to collapse
Your phone works normally
You don't have fastboot
You have stock recovery
If this is the case then most surely you have EDL working...
Install TWRP from EDL mode:
This is taken from Controllerboy's guide
BE SURE THAT WINDOWS SHOWS FILE NAME EXTENSIONS!
A) Flashing TWRP Recovery to your device.
Q: Why do I need TWRP?
A: TWRP is a custom recovery system. It lets your backup your system in case anything goes wrong. It also lets you flash custom ROMs and zip files containing patches like viper4android or A.R.I.S.E. (audio) and root your device via SuperSU.
0) Boot up a windows computer with a 64bits processor. Verify your Axon 7 is charged at least 75%. Temporarily disable your antivirus software to allow axon7tool to work.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery"
21) Wait until it finishes
22) Your phone should reboot
23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP
24) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
NOTE: if you have problems connecting to your phone as QUSB_BULK, download Zadig and replace your drivers with WinUSB ones. If axon7tool doesn't recignise your device even when connected as QUSB_BULK, try killing adb.exe via task manager before retrying.
Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.
macerf said:
Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.
Click to expand...
Click to collapse
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again
Choose an username... said:
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again
Click to expand...
Click to collapse
Hello and thanks for the advice. Unfortunately it does not change anything.. I have done exactly as you say but the result does not change anything...io have connected the device, Open command window, type "adb devices ", is viewed as "Cd07b2e9 device ", I type "adb reboot EDL ", it restarts in EDL, then go to management Devices and is viewed as "QUSB_BULK ", Run command "Axon7tool-r GPT boot recovery " but it says "Failed to connect ", then I'll return to Device Manager, hold volume up & Down & Power, Icon disappears and returns after a few seconds, close window and launch command "Axon7tool-r GPT boot recovery " but still give "failed to connect "...
So, recapping: I have bootloader unlocked, I can get into EDL but PC does not see device although on Device Manager it exists...
I now launch device into the wall... problem solved.
if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.
kitcostantino said:
if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.
Click to expand...
Click to collapse
Of course I'm kidding... have just purchased this device, have a great hardware but the software does not go well for nothing. I have had a dozen phones, I changed about 60 ROMs, so for me it is not difficult to change the software...ma in this case have problems. Is it possible that I fail to solve this problem? Be a way to reset everything and start from scratch? Okay, the bootloader be unlocked but not be any other way to go back? I have seen many guides but not able to solve the problem. I fail to make flash of TWRP, fail to do downgrade to MM....io hope someone help me... thanks.
are you using a USB 2.0 or 3.0 port? it may not apply to this scenario, but with Motorola and RSD Lite, I always had to use usb 2.0 ports or it wouldnt see my device when flashing.
also, the steps @choose an username listed out are the best way to start from scratch, but obviously you have to be able to have your computer see the phone in the desired mode.
@DrakenFX has several guides in the axon 7 forums that should help once the computer sees the phone as well.
I use USB 3.0 with original cable ... but if you now tell me that maybe this is my problem, then I use USB 2.0. Thank you...
Good morning...
Nothing to do... I put the original cable on USB Port 2.0, have redone procedure from window PowerShell, on command "adb devices " Everything OK, on command "adb reboot EDL " It enters EDL mode, but then all the procedures are failed... if command "Axon7tool-R recovery GPT boot "I always get out of the inscription " Failed to connect ", it remains in EDL and I just have to reboot... I replaced the drivers with Zadig 2.3 but did not change anything... are there any other moors to make flash of TWRP? exist lthough an app that do this? I remember that for LG G3 I'll fix everything with an app...