Related
Hi all,
I had a nice, long, detailed post typed out but then my browser at work crashed, so here is the revised edition:
I recently (three days ago) bought a TF300T tablet. Absolutely love it. As any android fan does, I immediately wanted to root it to get the full benefit of the device. I followed the step-by-step guide on the cyanogenmod wiki and have been successful (after a few hours of figuring things out) in unlocking the device. I am aware at this point that my device is unlocked and my Asus warranty is voided. I am also aware I may have to follow different steps to root it, and am willing to do so accordingly.
I'm not set on using cyanogenmod, but that seems to be the most popular and well-known one so I'd like to use one that is established.
So, up until now I have followed that guide but I am having an issue with flashboot. When I go to do the 'fastboot devices' command, I get nothing. It just jumps to the next line, as if I sent a blank command. When I type 'adb devices' it works fine and shows some letters&numbers so I know my device is recognized.
With all that being said, can anyone advise me on which step I'm doing wrong, if any?
Also, I'm -really- cautious about potentially bricking this thing. I still have 30 days at Best Buy but I'm also an employee there and my co-workers know I'm trying to root so if I brick it, it may not be as easy to return it as with a normal customer. I also have the Accidental Damage & Handling plan so if I DO brick it, I can smash it and get a new one without too much incident, if it comes down to it (which obviously is a LAST resort)
My device is as following:
Asus Transformer Pad TF300T unlocked, firmware .29.
I' have about 15 tabs open in Google Chrome right now after SEARCHing the forums, specifically the TF300 forum, and I'm filtering through all the posts right now. If I find a solution I will post asking for this thread to be deleted.
I'm very tech-savvy, but completely new to android. I don't own a smartphone, and this is my first android device, so this is an incredible learning experience. If anyone feels so kind, could you please explain the different terminiologies used in the rooting scene? I hear stuff about blobs, .build files, DE, WW, US stuff. What's what? And what does it all mean?
Thanks so much, and here's to hoping my computer doesn't crash as soon as I press "post"!!
-Opethfan89
*edit* Forgot to add that when I use the command
fastboot flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
the command prompt just stays stuck on "waiting for device", while my device is stuck on "Starting fastboot USB download protocol"
Slight resolution
So I am just posting with a slight update to what I've been trying to get this working. I uninstalled the ADK, all drivers, and started over from scratch. I installed ADB using the method listed on the CyanogenMod wiki, and it works fine (I can use all ADB commands from command prompt and it lists my device when I use the 'adb devices' command.
So I'm continuing to follow the steps on the CyanogenMod wiki page and I get back to the part about Fastboot. I boot into fastboot mode, plug the device in, and the new development is that my computer DOES recognize fastboot only in device manager. I do have a yellow exclamation mark near it meaning I don't have the proper driver installed.
So now my newest question is, how do I install the driver for -just- fastboot, or where can I find the .inf file so I'm able to install it myself?
I'm SO close to rooting this device I can just taste it!! Any device is very much appreciated
Thanks!
Opethfan89
Are you following this guide?
http://forum.xda-developers.com/showthread.php?t=1668173
Pretty easy to follow and the easiest way to install recovery and root device.
Yes I have followed that guide and like I said I get to the step where fastboot SHOULD be recognized by my computer but it isn't. It shows up in my device manager with a yellow exclamation point so I literally just need the driver to make things work and I should be rooted.
This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.
Have you tried to see the index on tf300t development?
Hope you have all you need and all process.
For Fastboot : [GUIDE] Help for flash more faster when you use Fastboot Line Command
And for Drivers:
ASUS Android USB Drivers.zip - 2012/04/13 - MD5 Sum: 43af8f39ed421caabecd6c4a2de17212 - Size: 8.28 MB (8687221 bytes)
ASUS Pad PC Suite (PC version V1.0.41) - MD5 Sum: 02d7661affefeb0ae05f577b6b24b37a - Size: 145.09 KB (148570 bytes)
ASUS Sync V1.0.82 - MD5 Sum: a7d229ee2f2678819e6a99711d1f572d - Size: 62.18 MB (65195236 bytes)
You will find all you need for your TF300t in this index
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop
philos64 said:
You don't need to use android sdk except if you to use commands line.
Use the guide about [URL "http://forum.xda-developers.com/showpost.php?p 27218675&postcount 20"][GUIDE] Help for flash more faster when you use Fastboot Line Command[/URL] and you will see than it's easy and faster to push something
I haven't use android sdk though it's installed on my laptop
Click to expand...
Click to collapse
I think you do need to install android sdk because of the fastboot files are in there and need it to use fastboot that could be the reason why his computer does not recognize the tablet when he is in fastboot mode. If you look at your android manager you will see a file under android tools that fastboot files are installed.
you need to specify device id
fastboot -i 0x0b05 flash recovery recovery-clockwork-5.5.0.4-tf300t.img
Click to expand...
Click to collapse
try that op
IT WORKED!!!!
EndlessDissent said:
This thread has the drivers you need: http://forum.xda-developers.com/showthread.php?t=1661653
There are no special fast boot drivers. Just install the Asus drivers, and you'll be good to go.
Also, I know this is off-topic, and I mean no offense to you, but every time I see a thread about driver problems in Windows, I feel a thousand times better about using Linux. No drivers to install. It just works.
Click to expand...
Click to collapse
See, I think that's where I messed up. None of the guides say to download ASUS' drivers, and in my anxiousness to root I must have overlooked that step. I will try this today and post my results accordingly!! Also, no offense taken by the linux comment, and I've used linux in the past, but I've had quite a few times where it doesn't "just work" (Like using a broadcom wireless card on my old laptop. I had to learn how to use ndiswrapper and whatnot, not a pleasant experience for a linux newb at that time!!)
I recently removed my Linux partition (was using ubuntu 10.10 because I hate unity!!) and can re-install it if it will make my rooting process easier?
vel0city said:
As long as you have the android sdk installed and the asus pad suite driver installed it should work no problem
Click to expand...
Click to collapse
Yea I didn't download the asus pad suite drivers, and I think that is what is causing my issue. I wish I could post links to the guides I am following but none of them specify that. They just say to download the android SDK and all drivers are included.
FlyingPoo said:
you need to specify device id
try that op
Click to expand...
Click to collapse
I did do that, flyingpoo. At one point my cmd line showed "Sending file recovery.img (5***kb)" but the tablet never picked it up, so I know there is just some miscommunication between the tablet and the PC. When I typed adb devices in cmd line, I see the device listed, but when I type fastboot devices in cmd line, it just goes to a blank line.
I will try the above listed solutions and hope that something works. Thank you all so much for your help!
*edit* This guy, right here? Yea, he's freakin ecstatic! I installed the drivers from EndlessDissents' post, and it worked!! As soon as I booted into fastboot mode, my computer recognized the device. I then used the command that FlyingPoo used (which I tried in the past), and it showed:
Code:
c:\recovery1>fastboot -i 0x0b05 flash recovery recovery.img
sending 'recovery' <5306 KB>...
OKAY [2.417s]
writing 'recovery'...
OKAY [2.053s]
finished. total time: 4.473s
So now I'm following the next few steps to root it. I've backed up my apps using Astro as well as the ASUS backup suite, and I'm using CWM for a backup of my entire system at the moment.
Thank you again to everyone who responded. I always get hung up on the simplest step, but once that is overcome everything else is a smooth ride downhill
One last noobish question to ask, and then I think I'll be done:
I've downloaded the root-signed.zip file, as well as the latest CyanogenMod file I could find (The official wiki didn't have one listed for any asus products, for some reason?) as well as a google apps for cyanogenmod. I put the files on my SD card but nothing on there is detected within CWM. So the noobish question is which directory do I need to put the files in for CWM to detect it?
That being said, I'm also wanting to backup my system to my external SD card and I selected the option in CWM to backup but it said no sd\ext was detected. Any thoughts?
Thanks again everyone for your responses.
*EDIT* For anyone following this thread, I did figure it out. Another guide I referenced specifies that you copy the files to the INTERNAL SD card (which is kind of confusing, as SD card explicitly refers to an external memory card) and then choose it from CWM. So for me, I downloaded the files on my computer, copied them to my SD card, put the SD card in my tablet, and copied the files to the root directory of the internal storage on my tablet.
Thanks again everyone, I now have root (at least, I'm pretty sure I do?)
Mod, please feel free to close this thread as necessary.
Disclaimer: By following this guide, you understand and accepts that I, and any developers mentioned in this guide, will NOT be held responsible in the event that your device stops functioning or dies. While I try my best to make everything as clear and concise as it can be, accidents will happen should you not follow everything like a hawk. Read the replies and make the best decision for yourself.
Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial
This tutorial DOES NOT work for the 2013 HD model, only for the 2012 model. Following the guide with the newer model WILL CAUSE your heart to race after doing so because you'll end up with red screens and/or bootloops. So please, don't do it.
I'm going to lead you through installing Hashcode's 2nd-Bootloader and TWRP in order to start flashing custom ROMs and make backups. First, let's go over the basics and why I'm doing this in the first place. I wrote this guide to be used on a Windows computer, but as long as you can do the same things on Mac/Linux, the whole guide applies. If there are any issues, please first refer to the troubleshooting portion at the end of the guide.
+Note: As of Amazon OS update 7.3.x+, there has been a lot of issues with rooting and flashing the 2nd-bootloader. Many users reported bootloops during the completion of the guide. Those with tablets running 7.3.0 or higher, please proceed with caution, and make sure you have a factory cable on hand if you wish to advance. I strongly recommend you make backups in Step 2. If you want guaranteed success, use this tool to revert back to 7.2.3 before using the guide. You will need to flash a brand-new 7.2.3 on top to revert, so you will lose everything if you don't backup your files first.
++Note: As of December 2013, Hashcode updated the freedom-boot.img to Amazon 7.4.6 so there should be no more bootloops or any other issues like that for those running 7.4.6 or lower, but to be safe, revert back regardless. If your tablet is running anything higher than 7.4.6, you will run into issues when completing the guide. Again, if you revert back to 7.2.3 like I pointed to above, then you will have no issues. If you didn't revert, always make sure your tablet is running the same or lower version than Hashcode's freedom-boot.img.
===== 1. Why do we need a 2nd bootloader? =====
The stock Amazon bootloader doesn't play nice with Android even though it has Android at its core. We can still use fastboot commands with it, but other than that, it's quite locked-down. In other words, normal exploits used to unlock the bootloader on other Android devices, for example, like the Nexus series by Google or the handsets by HTC don't apply here. In order to use the same features, like a custom ROM, custom kernel, custom recovery, we must bypass Amazon's software by installing a 2nd bootloader.
===== 2. Why are you posting a tutorial? =====
I'm doing this because the lack of a guide means that people like myself, who are not proficient developers, keep running into issues and some ended up bricking their devices. This means that they end up with a heavy paperweight, with no chance of fixing, other than hoping that they're lucky with a fastboot cable (not the one that came with the device) and find their way back to the beginning. I'm sick of seeing so many questions about the exact same issues so I thought, why not just make a guide everyone can follow and thus make the world a better place.
===== 3. Do I need any special equipment/knowledge? =====
You don't need any special equipment, provided that you follow this guide word-for-word and be careful. I recommend a factory cable, just in case, which can be found in various online dealers, like eBay. This is just in case you make a mistake and you brick the device. I successfully installed the 2nd-Bootloader + TWRP and flashed CM10.1 without a factory cable, within minutes. The key is make sure you don't miss anything, and if you're not sure, don't make any random guesses. As far as knowledge, yes, and no. Know what you're dealing with. Anything underneath the ROM has the chance to brick the device, so know what you're getting into.
===== 4. Can't I just use FireFireFire or another automatic tool to install the bootloader + TWRP? =====
Definitely not. This is the exact reason why there are so many threads in the Q&A section about bricked devices in the first place. Never use a tool that wasn't made for the version of your tablet. The Kindle Fire (1st gen), the Kindle Fire 2 (2nd gen), and the Kindle Fire HD 7" & 8.9" (3rd gen) are not the same devices, at all. Due to the way the bootloader behaves, flashing the files that are only compatible for the Kindle Fire 2 on a Kindle Fire HD 7" will definitely brick it. This is because the bootloader is so-named for a program that checks the booting process before the device actually boots, and if there are any bad sectors that don't match, the device won't boot.
How do you avoid this? By following guides like mine, and first knowing exactly what model you have. Yes, the Kindle Fire 2 and the Kindle Fire HD 7" look similar, and Amazon seriously have problems with their naming method, but a bit of research tells you that the Kindle Fire HD actually contains an HD resolution screen, 1280x800 for the 7" and 1920x1200 for the 8.9". Also, ONLY the Kindle Fire HD 7" and 8.9" models have a front-facing camera while the other models don't have one at all. If you want to be sophisticated about it, you can use working fastboot to identify the tablet.
+Note: if you know 100% that you have the right model, skip to Step 1 and begin the guide. This part is only for those with knowledge of fastboot and would like to confirm scientifically that they have the right model. You don't need to know how to use ADB or fastboot in order to successfullly complete the guide and install custom ROMs:
In CMD, type:
Code:
fastboot -i 0x1949 getvar product
Hitting enter will return with <waiting for device>. If you connect your powered-off Kindle Fire HD 7" or 8.9" at this point, it will reboot into fastboot mode, and on CMD, it will return with "tate-xxx-xxx" for the 7" and "jem-xxx-xxx" for the 8.9". I cannot stress this enough, please know your stuff before you end up crying about how you made a simple mistake that cost you $200, or however many in other currencies, but I do know that universally, it's quite a lot of money.
===== 5. What is Android SDK, ADB, and Fastboot? =====
Android SDK is a package with the tools for an Android developer to modify devices and collect data to help them create builds and maintain a device. Included in the package is what we commonly use around here in the development world, called ADB (Android Debug Bridge) and Fastboot. ADB allows a computer to communicate with a device by means of a USB cable, allowing a developer to push and pull data between the two devices, and this is the way some root methods are discovered.
Fastboot is the term we use to refer to a diagnostic tool built into Android. This is because fastboot is the first thing a developer turns to when their device is bricked. Factory cables are designed to power the devices into fastboot, and that's all they're really good for. While ADB is for communication between two devices, pushing and pulling data, fastboot is all about writing data into the partitions on a device. We call this process "flashing".
Generally, ADB commands in command prompts start with "adb" (i.e. "adb reboot bootloader" which commands a typical Android device to boot into bootloader mode, another name for fastboot mode). ADB commands can only be used when both devices are fully booted up, and ADB debugging is selected on the Android device. After the device boots into fastboot, the device no longer recognizes ADB commands, only fastboot commands. Likewise, in fastboot mode, commands begin with "fastboot" (i.e. "fastboot oem unlock" which unlocks the bootloader on many Android devices). While in fastboot mode, the only safe way to exit is by typing "fastboot reboot" although the usual power button will be fine for most cases.
On the Kindle Fire HD 7" and 8.9", you will notice that the fastboot commands look something like this: "fastboot -i 0x1949 flash boot boot.img" ("flash" is the command to flash a file, "boot" is the partition to flash the file into, and "boot.img" is the image file containing the booting information). The reason why there's a "-i 0x1949" is simply because of the locked-down bootloader. After we install the 2nd-bootloader, this part commands the device to flash the files into the stock bootloader, because the 2nd-bootloader doesn't accept fastboot commands.
To install the Android SDK and be able to use ADB + fastboot, go to this link: Android SDK. After you hit download, just be patient, and you will need a video reference to help set up the package properly, so click here: Video on Installation of Android SDK. To check if it installed properly, once you're done with the video, open up a command prompt (for Windows, hold the Windows key + R, and type cmd, then hit Enter), and type either "adb" or "fastboot" and hit Enter. For both cases, you should get a block of text that tells you what each command does.
To check if your device can work with ADB, enable ADB on the device (may be called USB debugging), and connect it to the computer. If there are any drivers installing, let them finish. Then, on the command prompt, type "adb devices" and hit Enter. If your ADB drivers work, you should see a line of letters and characters. Same thing with fastboot. Always do this check before you start messing around to make sure your devices are receiving the commands.
===== 6. I bricked my Kindle! Help! =====
Calm down. You know you have a brick when the Kindle dies completely. It doesn't respond in anyway, even plugging in the USB won't do anything. It is also considered a brick if you have a red screen, which is commonly associated with trying to mod the system of Amazon OS 7.3.0 or higher without first flashing the Amazon OS 7.2.3 bootloader. Your only hope is to purchase a factory cable (not the same one that came with your device in the box) and go from there. To restore the device to factory settings and unbrick, go to this thread: KFHD System Restore Tool and follow the directions.
Alternatively, if you are reading this after you made a mistake and ended up with either scenarios above, and have made backups from Step 1 below, use the instructions from #7 to boot into fastboot using a regular USB cable, and restore with instructions found in Step 1. If you do have a factory cable, simply open up command prompt, plug in the cable to the device and the computer, and proceed with the second line of code in the last set of codes.
===== 7. How do I get into fastboot mode without a factory cable? =====
This relies on you having a working device (as long as it can boot at all, you're good). If you wish to enter fastboot mode to flash system images like new versions of TWRP or restore Amazon OS 7.2.3 if you've got freezing or bootloops, then you need a regular USB cable that came with the device, or any other mini-USB cable that fits the device and the computer. Again, you need to have Android SDK installed before you can use fastboot. Turn the device off, and leave it unplugged. Go to your computer, open command prompt, and type this:
Code:
fastboot -i 0x1949 getvar product
Hit enter, and it should return with <waiting for device>. If it doesn't, your fastboot drivers aren't working. Install Android SDK and go from there. If it does, connect your turned-off Kindle to the computer. Two things will happen: one, the command prompt will show "Tate-xxx-xxx" (something there), and two, your Kindle should reboot into fastboot mode. To exit fastboot mode, after you finished flashing what you needed, type this:
Code:
fastboot -i 0x1949 reboot
If you can fully boot into the ROM, you can use ADB to boot into fastboot, but you must still use the same command above to reboot out of fastboot mode. Then make sure ADB is turned on through settings, connect the device to the computer using a regular USB cable, and type this:
Code:
adb shell su -c "reboot bootloader"
And that's all for the basics! Let's move on to the actual process.
Step 1: Rooting
+Note: Some users reported not being able to root on 7.4.1, so go into Settings and check your software version. 7.2.3 is what you want to see. I provided two root methods in case one doesn't work. If both fails, please try the second one again, using a different mode.
Before you can do anything else, you need to root the device first. Rooting is the process of acquiring superuser (administrator) access on a Linux system, allowing you to modify just about anything with regards to software. It is generally very safe to do, provided you follow the correct guides and you use the correct tools, and if there are no tools, the knowledge to manually root the device. On many other Android devices, rooting also installs a custom recovery, but the Kindle Fire HD 7" is different. You must root first before you do any modifications.
Go to this thread: QEMU Root by sparkym3, and download the necessary attachments. Use any decompressing software to unzip the files, and install the Kindle Fire HD 7" ADB drivers (this may fail, no need to worry). Then jump to your device, go to Settings and turn on ADB, then plug it into your computer. At this time, your computer should report that the ADB Composite Interface has been installed. What this means is that your ADB drivers work. Go ahead and use that thread's instructions to root the device.
Alternatively, you can use this if the first method failed: Root_with_Restore_by_Bin4ry, same idea. Make sure your ADB drivers are working, and that ADB is turned on in Settings. Open the RunMe.bat file, choose option 1. Now it will ask for your Amazon account password to restore, go ahead and type in your password and proceed. After the device reboots, it will be sluggish, now run the first method again, and you'll be back to normal with root.
To check if you're rooted, when the device is on, go to the Amazon Appstore, install "ES File Manager" or any other root application, you want to see the window asking for superuser permissions. Once it installs, open it, go to settings, and turn on root browsing. If it asks for superuser permissions, you have root access, and you can move on to the next step. If the root programs say you have root, but you don't see the window asking for the permission, remember to go to the app listing, and tap on superuser to initialize the daemon, then try to check for root again.
Recap:
1. Download the root tools from the two threads
2. Proceed to root by using the provided tools
3. Check if you successfully have root access using any root application
Step 2: Grabbing Files and Backing Up
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP for the Kindle Fire HD 7. Download ONLY two files: the TWRP recovery image, and the freedom-boot image. That's all, and transfer both of those to the root of the sdcard, now you can move on to Step 3: Installation if you wish to skip backing up.
I will go through the steps to backup. Remember that it is not mandatory that you do this; should you follow the guide very closely, you do not require backing up whatsoever. This just serves as an extraneous step for those who feel comfortable working with ADB and would like to participate in modding the device, in which case these files would come in handy in case the device is bricked. Again, it is NOT mandatory.
Connect the device to the computer through a normal USB cable, turn on ADB through settings. Open up the command prompt (CMD) on your computer: hold down the Windows key, and press R. This will open up Run, type "cmd" and hit Enter. Now, enter the following lines of code one-by-one, wait for a line to finish before going to the next one.
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img"
mkdir C:\KFHD7Backup
adb pull /sdcard/stock-boot.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-recovery.img/ [C:\KFHD7Backup]
adb pull /sdcard/stock-system.img/ [C:\KFHD7Backup]
Now open up the Computer folder, and in the C: drive you will find a folder called "KFHD7Backup" with all of those files that you just pulled in there. Once you're at this stage, you have finished backing up. Take that folder and put it somewhere safe, on a USB drive, or an external flash drive.
If you need to flash these to restore the device in case you have bricked it, boot into fastboot mode (if you have the fastboot cable, plug it into the device and the computer, if you don't have a fastboot cable, look at #7 above). Place the folder and the files back to the C: drive before attempting to restore (if you know how to use the cd command, feel free to change the location of the files). Once you're in fastboot, start with the first line of code to command CMD to locate the backups folder, then proceed with the second, one-at-a-time:
Code:
cd C:/KFHD7Backup
fastboot -i 0x1949 flash boot stock-boot.img
fastboot -i 0x1949 flash recovery stock-recovery.img
fastboot -i 0x1949 flash system stock-system.img
fastboot -i 0x1949 reboot
+Note: Be patient, as some of the codes take a while due to the amount of data being transferred between the device and your computer. If nothing happens after you hit Enter on a line of code or it just hangs at nothing, close the command prompt, open it up again, and retry. It might seem scary, but if there are no codes being executed in the command prompt (you'll see data transfers with kB/s and such if there's communication), it's safe to unplug the cable or close the command prompt. Feel free to reboot your computer, then plug the cable in and try again.
Also, know that these files, when flashed through fastboot, will revert your device back to the state of when these backups were made, so once you have TWRP, these files are no longer important. The backups you make in TWRP will be just as useful, and can save you both time and patience. If, however, you want to revert to a completely stock Amazon OS software for warranty purposes, or to redo this process for any reason, they will come into play because these backups retain your apps and your settings. Otherwise, use the KFHD System Restore Tool to go completely stock.
After you have backed-up (optional), and you have the two needed files on the sdcard (TWRP image and freedom-boot image, ignore the Amazon OS and the stack override files), you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Download both the required files and move them to sdcard
3. Use ADB to make backups (optional)
4. Use fastboot to restore the images you backed up if there are issues
Step 3: Installation
You might have noticed that Hashcode made a pretty extensive thread to help you flash the bootloader, but another coder has since developed an automatic app to do all the work for you: FireFlash. Go ahead and download the .apk file. Move that file to the sdcard, and on the device, install it using "ES File Manager" (tap on that file) or "Easy Installer" (after it finishes scanning, select it and install), both found on the Amazon Appstore. You will then find it in the applications listing, go ahead and open it.
The first thing you notice is that there are spots to plug in files for different partitions. This is where those files from Hashcode come into play. Plug the freedom-boot.img into the boot partition space, plug the TWRP recovery.img into the recovery partition, and make sure to hit "apply stack". If you are NOT on the 7.2.3 bootloader (you'll see red letters warning you), then hit the check box next to that to flash the 7.2.3 bootloader, otherwise you'll see a red screen after you reboot. If you don't see that warning, you're fine, move on.
Check that "disable recovery auto update" box, leave everything else alone, unplug the cable, and hit flash (the first option). You will see a progress window, and just hit OK. Then, turn off the device. Now, when you turn it on, this is the way to enter recovery every time: the moment you turn it on, you'll see the yellow Kindle title. Immediately hold down the Volume Up button (leftmost from the power button) before it turns blue, and once it does, count to three in your head and let go and you'll see the TWRP splash logo. Once you're in TWRP, you're done. Just hit reboot, and everything's finished. Now you can browse the 7" Development forum for custom ROMs.
If you want to save space, you can now go ahead and delete all the files we just used; you no longer have a need for any of them. Keep FireFlash, though, because in the future you might want to update TWRP, then leave everything blank, plug the update image into the recovery partition and hit flash. Only use Hashcode's TWRP builds as of now, because he specifically altered those builds to work on the Kindle Fire HD 7" and 8.9" so the official ones on the TWRP site won't work. If you flash those (especially the "blaze" codename), you will brick the device, so don't do it!
Recap:
1. Download FireFlash and install on device using file manager or installer
2. Plug in the required files in the correct areas, and check the necessary checkboxes
3. Flash, and boot into TWRP to confirm successful installation of both 2nd-Bootloader and TWRP recovery
Step 4: Flashing Custom ROMs
This is what you've been waiting for, the ability to load custom ROMs. You have a few choices at this point in time. This list contains (somewhat, if not) stable releases only:
1. Kinology by psych0phobia & JulianPaoloThiry (Amazon OS base + ICS modifications)
2. CyanogenMod 11 by Hashcode (AOSP, Android 4.4 KitKat)
3. ParanoidAndroid Port by jb2kred (AOKP, Android 4.2.2 Jelly Bean)
4. PAC-man by goldflame09 (AOKP, Hybrid of CM and PA, Android 4.3 Jelly Bean)
Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP. Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache. After these two things are done, go ahead and flash the .zip file, and wait for it to finish. After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot. After you rebooted, wait 5 minutes, then reboot again, and you're all done!
Now, in case your custom ROM doesn't automatically include GApps, and you would know if you boot up and you don't see Play Store or Google Maps in the app drawer, follow this. Go to this link. You will notice a table, and on the left side, you see the CM version that corresponds to the Android version number. All the custom ROMs should use the row that corresponds to the Android version. For example, CM10.1 runs 4.2.2, CM10.2 runs 4.3, so click on the one that corresponds. If your ROM runs 4.2.2, use the 4.2.2 row, etc. After you finish downloading that .zip file, move it to the sdcard, and boot into TWRP. From there, if you want to be fancy, wipe cache and Dalvik cache before flashing, but you don't have to unless there are problems after you restart. If there are problems, like freezing on boot, or crashing, then boot back into TWRP and wipe the two cache partitions.
Generally, you only need to flash the file and you're done, but you can never be too safe. This also applies to ROMs: if you're moving from ROM to ROM, say Kinology to CM10.1, you MUST wipe EVERYTHING except the sdcard itself, and this includes the "Factory Reset" option. However, if you're moving from one update of a ROM to another, say a nightly of CM10.1 to a newer nightly of CM10.1, you can just simply flash the update over the old one, no wiping needed (this is called dirty-flashing). However, again, if you notice problems afterward, simply boot back in TWRP and wipe the two cache partitions. Remember to always make backups before you make changes to an otherwise stable build. If there are issues that you can't seem to resolve, you can always restore back to the previous build.
Recap:
1. Download .zip for ROM + GApps and move to sdcard
2. Boot into TWRP, make backups, and wipe the necessary partitions
3. Flash ROM, and wipe cache + Dalvik cache, then reboot
4. Wait for 5 minutes after successful reboot, then reboot again
5. If there's no GApps for your ROM, use the link to download the proper version.
6. Move the file to sdcard, then boot into TWRP and flash.
7. Reboot, and if there are problems, reboot back into TWRP and wipe cache partitions.
Troubleshooting
1. Red screen upon reboot: You didn't check the checkbox in FireFlash to flash the Amazon OS 7.2.3 bootloader, causing the 7.3.x bootloader to crash, hence the red screen.
Solution: Plug it factory cable, then follow #6. If you made backups using ADB in Step 2, then flash those image files using the commands provided in Step 2.
2. Bootloop after reboot: Commonly associated with not following instructions in FireFlash like ignoring the stack override or just forgetting to check the box, or being on Amazon OS 7.3.x+.
Solution: Plug it factory cable, then follow #6. If you made backups using ADB in Step 2, then flash those image files using the commands provided in Step 2.
3. Device fails to boot at all: You flashed the wrong version of an image for another device to your device. This is common with users who use Kindle Fire Utility or FireFireFire which were made for the 1st & 2nd gen devices on a 3rd gen device (KFHD 7" & 8.9").
Solution: Plug it factory cable, then follow #6.
4. Fastboot doesn't detect device: All the commands hang at "waiting for device" in the terminal, even if ADB worked before.
Solution: Make sure Android SDK is installed by going into command prompt and type "adb" then hit Enter. You should see a block of text instructing you to use ADB commands. Find a Windows computer, because ADB & fastboot works best on a Linux system, therefore Macs and OS X will not yield proper results.
Go to the QEMU root thread, and pick up the drivers. Then hold Windows key + R, type "devmgmt.msc" and hit Enter. In Device Manager, if Kindle shows up as "Tate-PVT-08" then right click on that item, Update Driver Software, choose Browse, and select the option to pick from a list. Now navigate to the Kindle drivers you downloaded, and install. Now your fastboot should work.
5. Stuck at boot logo: Device boots after flashing with FireFlash and hangs at the splash screen.
Solution: Plug it factory cable, then follow #6.
6. Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done.
Credits: Hashcode, fattire, and verygreen for the work on the bootloader, stanga72 for the app FireFlash, sparkym3 & Bin4ry for their rooting methods, onemeila for the restore tool, and myself for the creation of this guide.
If your video can help guide and more for noobs,many thanks.
quan_1986 said:
If your video can help guide and more for noobs,many thanks.
Click to expand...
Click to collapse
Unfortunately, I don't have a spare KFHD7 to do a video on. I can't start over on mine because I have too many things on there and starting over would mean losing absolutely everything and I can't afford that.
I did try to be as clear as possible in the instructions above, so point out any mistakes or anything confusing you can find. The goal is to help the people out.
WOW!
seokhun said:
Disclaimer: By following this guide, you understand and accepts that I, or any other developers mentioned in this guide, will NOT be held responsible in the event that your device stops functioning or dies. While I try my best to make everything as clear and concise as it can be, accidents will happen should you not follow everything like a hawk.
Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial
I'm going to lead you through installing Hashcode's 2nd-Bootloader and TWRP in order to start flashing custom ROMs and make backups. First, let's go over the basics and why I'm doing this in the first place.
===== 1. Why do we need a 2nd bootloader? =====
The stock Amazon bootloader doesn't play nice with Android even though it has Android at its core. We can still use fastboot commands with it, but other than that, it's quite locked-down. In other words, normal exploits used to unlock the bootloader on other Android devices, for example, like the Nexus series by Google or the handsets by HTC don't apply here. In order to use the same features, like a custom ROM, custom kernel, custom recovery, we must bypass Amazon's software by installing a 2nd bootloader.
===== 2. Why are you posting a tutorial? =====
I'm doing this because the lack of a guide means that people like myself, who are not proficient developers, keep running into issues and some ended up bricking their devices. This means that they end up with a heavy paperweight, with no chance of fixing, other than hoping that they're lucky with a fastboot cable (not the one that came with the device) and find their way back to the beginning. I'm sick of seeing so many questions about the exact same issues so I thought, why not just make a guide everyone can follow and thus make the world a better place.
===== 3. Do I need any special equipment/knowledge? =====
You don't need any special equipment, provided that you follow this guide word-for-word and be careful. I recommend a factory cable, just in case, which can be found in various online dealers, like eBay. This is just in case you make a mistake and you brick the device. I successfully installed the 2nd-Bootloader + TWRP and flashed CM10.1 without a factory cable, within minutes. The key is make sure you don't miss anything, and if you're not sure, don't make any random guesses. As far as knowledge, yes, and no. Know what you're dealing with. Anything underneath the ROM has the chance to brick the device, so know what you're getting into.
===== 4. Can't I just use FireFireFire or another automatic tool to install the bootloader + TWRP? =====
Definitely not. This is the exact reason why there are so many threads in the Q&A section about bricked devices in the first place. Never use a tool that wasn't made for the version of your tablet. The Kindle Fire (1st gen), the Kindle Fire 2 (2nd gen), and the Kindle Fire HD 7" & 8.9" (3rd gen) are not the same devices, at all. Due to the way the bootloader behaves, flashing the files that are only compatible for the Kindle Fire 2 on a Kindle Fire HD 7" will definitely brick it. This is because the bootloader is so-named for a program that checks the booting process before the device actually boots, and if there are any bad sectors that don't match, the device won't boot.
How do you avoid this? By following guides like mine, and first knowing exactly what model you have. Yes, the Kindle Fire 2 and the Kindle Fire HD look similar, and Amazon seriously have problems with their naming method, but a bit of research tells you that the Kindle Fire HD actually contains an HD resolution screen, 1280x800 for the 7" and 1920x1200 for the 8.9". Also, ONLY the Kindle Fire HD 7" and 8.9" models have a front-facing camera while the other models don't have one at all. If you want to be sophisticated about it, you can use working fastboot to identify the tablet.
In CMD, type: fastboot -i 0x1949 getvar product. Hitting enter will return with <waiting for device>. If you connect your powered-off Kindle Fire HD 7" or 8.9" at this point, it will reboot into fastboot mode, and on CMD, it will return with "tate-xxx-xxx" for the 7" and "jem-xxx-xxx" for the 8.9". I cannot stress this enough, please know your stuff before you end up crying about how you made a simple mistake that cost you $200, or however many in other currencies, but I do know that universally, it's quite a lot of money.
===== 5. I bricked my Kindle! Help! =====
Calm down. You know you have a brick when the Kindle dies completely. It doesn't respond in anyway, even plugging in the USB won't do anything. Your only hope is to purchase a factory cable (not the same one that came with your device in the box) and go from there. To restore the device to factory settings and unbrick, there are two methods:
1. Go to this thread: KFHD System Restore Tool and follow the directions.
2. Download this file: Amazon OS 7.2.3. Once it finishes, place that file in the same folder as your fastboot.exe (this is found in the Android SDK folder, so if you haven't installed the Android SDK, do so) which should be the platform-tools folder. Rename the file to amazon723.bin for easier flashing (or rename it however you want, but use that name later on).
Now plug the device into the computer using the factory cable, and the device should reboot into fastboot mode (you'll see "fastboot" in orange on the device). From there, type this command and hit enter:
fastboot -i 0x1949 flash boot amazon723.bin
Now the OS will be flashed, and after it finishes, type:
fastboot -i 0x1949 reboot
After the reboot completes, you'll be back at the very start.
===== 6. How do I get into fastboot mode without a factory cable? =====
This relies on you having a working device (as long as it can boot at all, you're good). If you wish to enter fastboot mode to flash system images like new versions of TWRP or restore Amazon OS 7.2.3 if you've got freezing or bootloops, then you need a regular USB cable that came with the device, or any other mini-USB cable that fits the device and the computer. Turn the device off, and leave it unplugged. Go to your computer, open command prompt, and type this:
fastboot -i 0x1949 getvar product
Hit enter, and it should return with <waiting for device>. If it doesn't, your fastboot drivers aren't working. Install Android SDK and go from there. If it does, connect your turned-off Kindle to the computer. Two things will happen: one, the command prompt will show "Tate-xxx-xxx" (something there), and two, your Kindle should reboot into fastboot mode. To exit fastboot mode, after you finished flashing what you needed, type this:
fastboot -i 0x1949 reboot
And that's all for the basics! Let's move on to the actual process.
Step 1: Rooting
+Note: Some users reported not being able to root on 7.3.1, so go into Settings and check your software version. 7.2.3 is what you want to see. I provided two root methods in case one doesn't work.
Before you can do anything else, you need to root the device first. Rooting is the process of acquiring superuser (administrator) access on a Linux system, allowing you to modify just about anything with regards to software. It is generally very safe to do, provided you follow the correct guides and you use the correct tools, and if there are no tools, the knowledge to manually root the device. On many other Android devices, rooting also installs a custom recovery, but the Kindle Fire HD 7" is different. You must root first before you do any modifications.
Go to this thread: QEMU Root by sparkym3, and download the necessary attachments. Use any decompressing software to unzip the files, and install the Kindle Fire HD 7" ADB drivers (this may fail, no need to worry). Then jump to your device, go to Settings and turn on ADB, then plug it into your computer. At this time, your computer should report that the ADB Composite Interface has been installed. What this means is that your ADB drivers work. Go ahead and use that thread's instructions to root the device. Alternatively, you can use this if the first method failed: Root_with_Restore_by_Bin4ry, same idea.
To check if you're rooted, when the device is on, go to the Amazon Appstore, install "ES File Manager". Once it installs, open it, go to settings, and turn on root browsing. If it asks for superuser permissions, you have root access, and you can move on to the next step.
Recap:
1. Download the root tools from the two threads
2. Proceed to root by using the provided tools
3. Check if you successfully have root access using any root application
Step 2: Grabbing Files and Backing Up
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP 2.4.4.0 for the Kindle Fire HD 7. If you have ADB installed (you should), then use the command prompt (CMD) to make backups just in case things go wrong. It's not required, but if you want to be safe, follow Hashcode's step 1 in that thread. Open CMD, connect the Kindle with ADB turned on, copy-paste the first line, hit enter, wait, then do the same thing for the remaining 4 lines of code. Otherwise, download all the files from step 2, except the stack.
Now, after you have backed-up (optional), and you have downloaded all the needed files (freedom-boot.img and TWRP recovery.img, you don't need the stack override file because that's provided in FireFlash, read Step 3), go ahead and transfer all of those to the root of the sdcard. Once that's done, you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Use ADB to make backups (optional)
3. Download the required files and move them to sdcard
Step 3: Installation
You might have noticed that Hashcode made a pretty extensive thread to help you flash the bootloader, but another coder has since developed an automatic app to do all the work for you: FireFlash v1.1. Go ahead and download the .apk file. Move that file to the sdcard, and on the device, install it using "ES File Manager" (tap on that file) or "Easy Installer" (after it finishes scanning, select it and install), both found on the Amazon Appstore. You will then find it in the applications listing, go ahead and open it.
The first thing you notice is that there are spots to plug in files for different partitions. This is where those files from Hashcode come into play. Plug the freedom-boot.img into the boot partition space, plug the TWRP recovery.img into the recovery partition, and make sure to hit "apply stack". If you are NOT on the 7.2.3 bootloader (you'll see red letters warning you), then hit the check box next to that to flash the 7.2.3 bootloader, otherwise you'll see a red screen after you reboot. If you don't see that warning, you're fine, move on.
Leave that "disable recovery auto update" function checked, leave everything else alone and hit flash. You will see a progress window, and just hit OK. Then, you will either be automatically rebooted into TWRP, in which case skip to step 4, or you will do it manually: go ahead and turn off the device, you no longer need the computer. When you turn it on, here's how to do it: push the power button, and the instant you see the orange "Kindle" logo, hold down the volume-up button (leftmost from the power button) while the orange turns into blue, then you can let go. This will enter you into TWRP, and it will take a minute, so be patient.
Once you're in TWRP, you're done. Just hit reboot, and everything's finished. Now you can browse the 7" Development forum for custom ROMs.
Recap:
1. Download FireFlash v1.1 and install on device using file manager or installer
2. Plug in the required files in the correct areas, and check the necessary checkboxes
3. Flash, and boot into TWRP to confirm successful installation of both 2nd-Bootloader and TWRP recovery
Step 4: Flashing Custom ROMs
This is what you've been waiting for, the ability to load custom ROMs. You have a few choices at this point in time:
1. Kinology by psychophobia (Amazon OS 7.3.1 base + Android Ice Cream Sandwich modifications)
2. CyanogenMod 10.1 by Hashcode (AOSP with custom 1.5GHz kernel, Android Jelly Bean 4.2.2) *read below
3. ParanoidAndroid Port by -a- (CM10.1 base, AOKP, Android Jelly Bean 4.2.2)
4. CyanogenMod 10.1 Tablet UI by Jester6 (same properties as Hashcode's CM10.1 build, Tablet UI = just looks nicer with dual-pane)
5. ParanoidAndroid Port by jb2kred (same properties as -a-'s ParanoidAndroid build)
Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store, found on goo.im, use the top row), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP. Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache. After these two things are done, go ahead and flash the .zip file, and wait for it to finish. After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot. After you rebooted, wait 5 minutes, then reboot again, and you're all done!
+If you want to use CM10.1, be sure to also download the alternate 1.2GHz kernel, as myself and some others have experienced some freezing on the 1.5GHz kernel. Flashing the 05/08 alpha will automatically install the 1.5GHz kernel, and if it freezes on the boot animation, simply turn it off, turn it on, boot into TWRP, and flash the 1.2GHz kernel and reboot. Alternatively, this is where the backup you made comes in handy, in case you forgot to download the 1.2GHz.
Recap:
1. Download .zip for ROM + GApps and move to sdcard
2. Boot into TWRP, make backups, and wipe the necessary partitions
3. Flash ROM, and wipe cache + Dalvik cache, then reboot
4. Wait for 5 minutes after successful reboot, then reboot again
Credits: Hashcode, fattire, and verygreen for the work on the bootloader, stanga72 for the app FireFlash v1.1, sparkym3 and Bin4ry for their rooting methods, and myself for the creation of this guide.
Click to expand...
Click to collapse
You have made my day... Thanks A LOT!!!!:victory:
vlavlix said:
You have made my day... Thanks A LOT!!!!:victory:
Click to expand...
Click to collapse
I made the guide with people like you in mind. Thank you for trusting it
This post needs to be pinned!
Awesome work, Keep it up! :good:
One last question.
seokhun said:
Disclaimer: By following this guide, you understand and accepts that I, or any other developers mentioned in this guide, will NOT be held responsible in the event that your device stops functioning or dies. While I try my best to make everything as clear and concise as it can be, accidents will happen should you not follow everything like a hawk.
Installing Kindle Fire HD 7" 2nd-Bootloader + TWRP Complete Tutorial
I'm going to lead you through installing Hashcode's 2nd-Bootloader and TWRP in order to start flashing custom ROMs and make backups. First, let's go over the basics and why I'm doing this in the first place.
===== 1. Why do we need a 2nd bootloader? =====
The stock Amazon bootloader doesn't play nice with Android even though it has Android at its core. We can still use fastboot commands with it, but other than that, it's quite locked-down. In other words, normal exploits used to unlock the bootloader on other Android devices, for example, like the Nexus series by Google or the handsets by HTC don't apply here. In order to use the same features, like a custom ROM, custom kernel, custom recovery, we must bypass Amazon's software by installing a 2nd bootloader.
===== 2. Why are you posting a tutorial? =====
I'm doing this because the lack of a guide means that people like myself, who are not proficient developers, keep running into issues and some ended up bricking their devices. This means that they end up with a heavy paperweight, with no chance of fixing, other than hoping that they're lucky with a fastboot cable (not the one that came with the device) and find their way back to the beginning. I'm sick of seeing so many questions about the exact same issues so I thought, why not just make a guide everyone can follow and thus make the world a better place.
===== 3. Do I need any special equipment/knowledge? =====
You don't need any special equipment, provided that you follow this guide word-for-word and be careful. I recommend a factory cable, just in case, which can be found in various online dealers, like eBay. This is just in case you make a mistake and you brick the device. I successfully installed the 2nd-Bootloader + TWRP and flashed CM10.1 without a factory cable, within minutes. The key is make sure you don't miss anything, and if you're not sure, don't make any random guesses. As far as knowledge, yes, and no. Know what you're dealing with. Anything underneath the ROM has the chance to brick the device, so know what you're getting into.
===== 4. Can't I just use FireFireFire or another automatic tool to install the bootloader + TWRP? =====
Definitely not. This is the exact reason why there are so many threads in the Q&A section about bricked devices in the first place. Never use a tool that wasn't made for the version of your tablet. The Kindle Fire (1st gen), the Kindle Fire 2 (2nd gen), and the Kindle Fire HD 7" & 8.9" (3rd gen) are not the same devices, at all. Due to the way the bootloader behaves, flashing the files that are only compatible for the Kindle Fire 2 on a Kindle Fire HD 7" will definitely brick it. This is because the bootloader is so-named for a program that checks the booting process before the device actually boots, and if there are any bad sectors that don't match, the device won't boot.
How do you avoid this? By following guides like mine, and first knowing exactly what model you have. Yes, the Kindle Fire 2 and the Kindle Fire HD look similar, and Amazon seriously have problems with their naming method, but a bit of research tells you that the Kindle Fire HD actually contains an HD resolution screen, 1280x800 for the 7" and 1920x1200 for the 8.9". Also, ONLY the Kindle Fire HD 7" and 8.9" models have a front-facing camera while the other models don't have one at all. If you want to be sophisticated about it, you can use working fastboot to identify the tablet.
In CMD, type: fastboot -i 0x1949 getvar product. Hitting enter will return with <waiting for device>. If you connect your powered-off Kindle Fire HD 7" or 8.9" at this point, it will reboot into fastboot mode, and on CMD, it will return with "tate-xxx-xxx" for the 7" and "jem-xxx-xxx" for the 8.9". I cannot stress this enough, please know your stuff before you end up crying about how you made a simple mistake that cost you $200, or however many in other currencies, but I do know that universally, it's quite a lot of money.
===== 5. I bricked my Kindle! Help! =====
Calm down. You know you have a brick when the Kindle dies completely. It doesn't respond in anyway, even plugging in the USB won't do anything. Your only hope is to purchase a factory cable (not the same one that came with your device in the box) and go from there. To restore the device to factory settings and unbrick, there are two methods:
1. Go to this thread: KFHD System Restore Tool and follow the directions.
2. Download this file: Amazon OS 7.2.3. Once it finishes, place that file in the same folder as your fastboot.exe (this is found in the Android SDK folder, so if you haven't installed the Android SDK, do so) which should be the platform-tools folder. Rename the file to amazon723.bin for easier flashing (or rename it however you want, but use that name later on).
Now plug the device into the computer using the factory cable, and the device should reboot into fastboot mode (you'll see "fastboot" in orange on the device). From there, type this command and hit enter:
fastboot -i 0x1949 flash boot amazon723.bin
Now the OS will be flashed, and after it finishes, type:
fastboot -i 0x1949 reboot
After the reboot completes, you'll be back at the very start.
===== 6. How do I get into fastboot mode without a factory cable? =====
This relies on you having a working device (as long as it can boot at all, you're good). If you wish to enter fastboot mode to flash system images like new versions of TWRP or restore Amazon OS 7.2.3 if you've got freezing or bootloops, then you need a regular USB cable that came with the device, or any other mini-USB cable that fits the device and the computer. Turn the device off, and leave it unplugged. Go to your computer, open command prompt, and type this:
fastboot -i 0x1949 getvar product
Hit enter, and it should return with <waiting for device>. If it doesn't, your fastboot drivers aren't working. Install Android SDK and go from there. If it does, connect your turned-off Kindle to the computer. Two things will happen: one, the command prompt will show "Tate-xxx-xxx" (something there), and two, your Kindle should reboot into fastboot mode. To exit fastboot mode, after you finished flashing what you needed, type this:
fastboot -i 0x1949 reboot
And that's all for the basics! Let's move on to the actual process.
Step 1: Rooting
+Note: Some users reported not being able to root on 7.3.1, so go into Settings and check your software version. 7.2.3 is what you want to see. I provided two root methods in case one doesn't work.
Before you can do anything else, you need to root the device first. Rooting is the process of acquiring superuser (administrator) access on a Linux system, allowing you to modify just about anything with regards to software. It is generally very safe to do, provided you follow the correct guides and you use the correct tools, and if there are no tools, the knowledge to manually root the device. On many other Android devices, rooting also installs a custom recovery, but the Kindle Fire HD 7" is different. You must root first before you do any modifications.
Go to this thread: QEMU Root by sparkym3, and download the necessary attachments. Use any decompressing software to unzip the files, and install the Kindle Fire HD 7" ADB drivers (this may fail, no need to worry). Then jump to your device, go to Settings and turn on ADB, then plug it into your computer. At this time, your computer should report that the ADB Composite Interface has been installed. What this means is that your ADB drivers work. Go ahead and use that thread's instructions to root the device. Alternatively, you can use this if the first method failed: Root_with_Restore_by_Bin4ry, same idea.
To check if you're rooted, when the device is on, go to the Amazon Appstore, install "ES File Manager". Once it installs, open it, go to settings, and turn on root browsing. If it asks for superuser permissions, you have root access, and you can move on to the next step.
Recap:
1. Download the root tools from the two threads
2. Proceed to root by using the provided tools
3. Check if you successfully have root access using any root application
Step 2: Grabbing Files and Backing Up
Once you're rooted successfully, you need to grab the files we'll need for the installation. Go to Hashcode's thread: Kindle Fire 2nd-bootloader + TWRP 2.4.4.0 for the Kindle Fire HD 7. If you have ADB installed (you should), then use the command prompt (CMD) to make backups just in case things go wrong. It's not required, but if you want to be safe, follow Hashcode's step 1 in that thread. Open CMD, connect the Kindle with ADB turned on, copy-paste the first line, hit enter, wait, then do the same thing for the remaining 4 lines of code. Otherwise, download all the files from step 2, except the stack.
Now, after you have backed-up (optional), and you have downloaded all the needed files (freedom-boot.img and TWRP recovery.img, you don't need the stack override file because that's provided in FireFlash, read Step 3), go ahead and transfer all of those to the root of the sdcard. Once that's done, you can move on to step three.
Recap:
1. Go to Hashcode's 2nd-bootloader thread
2. Use ADB to make backups (optional)
3. Download the required files and move them to sdcard
Step 3: Installation
You might have noticed that Hashcode made a pretty extensive thread to help you flash the bootloader, but another coder has since developed an automatic app to do all the work for you: FireFlash v1.1. Go ahead and download the .apk file. Move that file to the sdcard, and on the device, install it using "ES File Manager" (tap on that file) or "Easy Installer" (after it finishes scanning, select it and install), both found on the Amazon Appstore. You will then find it in the applications listing, go ahead and open it.
The first thing you notice is that there are spots to plug in files for different partitions. This is where those files from Hashcode come into play. Plug the freedom-boot.img into the boot partition space, plug the TWRP recovery.img into the recovery partition, and make sure to hit "apply stack". If you are NOT on the 7.2.3 bootloader (you'll see red letters warning you), then hit the check box next to that to flash the 7.2.3 bootloader, otherwise you'll see a red screen after you reboot. If you don't see that warning, you're fine, move on.
Leave that "disable recovery auto update" function checked, leave everything else alone and hit flash. You will see a progress window, and just hit OK. Then, you will either be automatically rebooted into TWRP, in which case skip to step 4, or you will do it manually: go ahead and turn off the device, you no longer need the computer. When you turn it on, here's how to do it: push the power button, and the instant you see the orange "Kindle" logo, hold down the volume-up button (leftmost from the power button) while the orange turns into blue, then you can let go. This will enter you into TWRP, and it will take a minute, so be patient.
Once you're in TWRP, you're done. Just hit reboot, and everything's finished. Now you can browse the 7" Development forum for custom ROMs.
Recap:
1. Download FireFlash v1.1 and install on device using file manager or installer
2. Plug in the required files in the correct areas, and check the necessary checkboxes
3. Flash, and boot into TWRP to confirm successful installation of both 2nd-Bootloader and TWRP recovery
Step 4: Flashing Custom ROMs
This is what you've been waiting for, the ability to load custom ROMs. You have a few choices at this point in time:
1. Kinology by psychophobia (Amazon OS 7.3.1 base + Android Ice Cream Sandwich modifications)
2. CyanogenMod 10.1 by Hashcode (AOSP with custom 1.5GHz kernel, Android Jelly Bean 4.2.2) *read below
3. ParanoidAndroid Port by -a- (CM10.1 base, AOKP, Android Jelly Bean 4.2.2)
4. CyanogenMod 10.1 Tablet UI by Jester6 (same properties as Hashcode's CM10.1 build, Tablet UI = just looks nicer with dual-pane)
5. ParanoidAndroid Port by jb2kred (same properties as -a-'s ParanoidAndroid build)
Once you have the .zip files for the ROMs with GApps (Google apps, like Play Store, found on goo.im, use the top row), place them on the sdcard, and turn off the device. Turn it on, hold Volume-Up before the logo turns blue, and enter TWRP. Once there, immediately do two things: make a backup, and after that, wipes: system, factory reset, cache, and Dalvik cache. After these two things are done, go ahead and flash the .zip file, and wait for it to finish. After it finishes, go ahead and again, wipe cache and Dalvik cache, then reboot. After you rebooted, wait 5 minutes, then reboot again, and you're all done!
+If you want to use CM10.1, be sure to also download the alternate 1.2GHz kernel, as myself and some others have experienced some freezing on the 1.5GHz kernel. Flashing the 05/08 alpha will automatically install the 1.5GHz kernel, and if it freezes on the boot animation, simply turn it off, turn it on, boot into TWRP, and flash the 1.2GHz kernel and reboot. Alternatively, this is where the backup you made comes in handy, in case you forgot to download the 1.2GHz.
Recap:
1. Download .zip for ROM + GApps and move to sdcard
2. Boot into TWRP, make backups, and wipe the necessary partitions
3. Flash ROM, and wipe cache + Dalvik cache, then reboot
4. Wait for 5 minutes after successful reboot, then reboot again
Credits: Hashcode, fattire, and verygreen for the work on the bootloader, stanga72 for the app FireFlash v1.1, sparkym3 and Bin4ry for their rooting methods, and myself for the creation of this guide.
Click to expand...
Click to collapse
Once I've flashed the cm10.1 zip and installed the 1.2GHz kernel, how do i install the GAPPS? because I didn't install them meanwhile I was in TWRP..
vlavlix said:
Once I've flashed the cm10.1 zip and installed the 1.2GHz kernel, how do i install the GAPPS? because I didn't install them meanwhile I was in TWRP..
Click to expand...
Click to collapse
Simply go to the goo.im page, and click on Gapps. Go back up to step 4, I've added an explanation.
Thanks for the guide, I have been away from this area of the community for awhile, and have gotten lost with what has happened. Spent hours, looking for what I had missed. Got everything working :good:
iMJets said:
Thanks for the guide, I have been away from this area of the community for awhile, and have gotten lost with what has happened. Spent hours, looking for what I had missed. Got everything working :good:
Click to expand...
Click to collapse
You sure? If you installed a custom ROM, change your signature, haha. I'm glad it worked out fine!
Can someone just make then video how to I'm tire of amazon I want cm 10 I'm my kindle thanks
Sent from my Nexus 7 using Tapatalk 2
Cheers mate, followed to a tee and now have my Kindle Fire HD 7" OC'ed to 1500MHz and jester's TabUI CM 10.1 ROM on. Sweetness....
esema1o said:
Can someone just make then video how to I'm tire of amazon I want cm 10 I'm my kindle thanks
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I already went out of my way to create a super-extensive guide for you. If you need a video, go bother someone else to do it. My instructions are as clear and as simple as they could get.
Katalystik said:
Cheers mate, followed to a tee and now have my Kindle Fire HD 7" OC'ed to 1500MHz and jester's TabUI CM 10.1 ROM on. Sweetness....
Click to expand...
Click to collapse
I'm glad! Enjoy the custom ROMs!
esema1o said:
Can someone just make then video how to I'm tire of amazon I want cm 10 I'm my kindle thanks
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You actually need to read the tutorial. Its word for word, there's no video needed. If you are scared to do this don't do it. You will just mess up your device, which is more of a pain to fix. As always make sure you have a fastboot cable.
iMJets said:
You actually need to read the tutorial. Its word for word, there's no video needed. If you are scared to do this don't do it. You will just mess up your device, which is more of a pain to fix. As always make sure you have a fastboot cable.
Click to expand...
Click to collapse
Yea I'm lil nerves well I'm not gone do it I all ready got me Google table nexus 7 so I'm just gone leave this table like this oh well thanks
Sent from my Nexus 7 using Tapatalk 2
maybe I'm being stupid but when I try this on my rooted kfhd7 and type fastboot -i 0x1949 getvar product I get <waiting for device> then connect my device and nothing happens. tried this when device powered off as well. Any ideas?
thanks
rhodri11 said:
maybe I'm being stupid but when I try this on my rooted kfhd7 and type fastboot -i 0x1949 getvar product I get <waiting for device> then connect my device and nothing happens. tried this when device powered off as well. Any ideas?
thanks
Click to expand...
Click to collapse
You don't have fastboot drivers. Did you install Android SDK and configure it properly? By that I mean installing the package, downloading the required components using the installer, and adding the path to system.
seokhun said:
You don't have fastboot drivers. Did you install Android SDK and configure it properly? By that I mean installing the package, downloading the required components using the installer, and adding the path to system.
Click to expand...
Click to collapse
Hmm strange one this. I have tried using fastboot on my windows and linux system with the KFHD off and the when connected they still don't go into fastboot. Been told I could probably get away with using root toolbox and rebooting into fastboot that way?
In the mean time I have just followed step 2, backup the images on the kindle, and now it says to use FireFlash v1.1. I am running 7.3.0. Is FireFlash v1.1 okay to use with my version or will I have to do it the manual way?
Thanks
rhodri11 said:
Hmm strange one this. I have tried using fastboot on my windows and linux system with the KFHD off and the when connected they still don't go into fastboot. Been told I could probably get away with using root toolbox and rebooting into fastboot that way?
In the mean time I have just followed step 2, backup the images on the kindle, and now it says to use FireFlash v1.1. I am running 7.3.0. Is FireFlash v1.1 okay to use with my version or will I have to do it the manual way?
Thanks
Click to expand...
Click to collapse
As I previously said, you don't have working fastboot drivers. Go back to the guide, in #5, and install Android SDK. Then the commands will work.
You can use FireFlash, but if you see the red letters warning you to flash the 7.2.3 bootloader once you open up the app, CHECK THAT BOX. The rest of the guide applies.
seokhun said:
As I previously said, you don't have working fastboot drivers. Go back to the guide, in #5, and install Android SDK. Then the commands will work.
You can use FireFlash, but if you see the red letters warning you to flash the 7.2.3 bootloader once you open up the app, CHECK THAT BOX. The rest of the guide applies.
Click to expand...
Click to collapse
I am able to communicate with the kindle through adb commands but fastboot still not working. Have installed AndroidSDK on my windows 7 machine, extracted it, run and and made sure the tools, platform tools, and usb drivers were installed, which they are. Fastboot does run.. it just hangs there "waiting for device"
Sorry but have I missed a crucial step?
edit:
Have also tried fastboot using Linux android bundle (again, adb devices shows the kindle, but nothing from fastboot) and then tried sudo add-apt-repository ppa:nilarimogard/webupd8, updated everything then apt-get install android-tools-adb android-tools-fastboot. Again, run adb devices and it shows up, but fastboot doesn't work.
Hey guys found out how to ROOT ASUS TF300T latest ROOT for TF300T V10.6.1.27.5 ! locked bl.
just follow the steps
Instruction:
1. Download the rooting application. (This app can root many other devices )
VRoot_1.6.0.3690
http://www.mediafire.com/download/v3...3690_Setup.exe
2. Install the app. This is a Chinese app so I will guide you. Below is a step by step screenshot attached guide.
3. Start VROOT and root now!
4. Now we need to install SuperSU from play store to replace the Chinese root manager called 授权管理 1.0.4.
5. Go to play store and install SuperSU.
6. Start SuperSU and you will be asked for permission by 授权管理 1.0.4, choose 允许(means allow). (Should be the right side option.)
7. SuperSU will prompt to install SU binary, go ahead with OK and it will display successful.
8. Now, freeze 授权管理 1.0.4 in titanium backup, just in case you need it again.
Note: If you uninstall straight away from app manager, you need to make sure SuperSU updated the binary.
9. Re-run SuperSU to make sure everything is alright. You will be prompt again to install SU binary, just do what it asked.
10. After that, you are rooted with SuperSU and 授权管理 1.0.4 will not be there anymore.
Optional
11. If you want to be more assured, in SuperSU app, prepare for a Reinstall in settings. (NOT Full unroot NOT Switch superuser app)
12. SuperSU will be removed and go back to play store to re-download and install.
13. Start SuperSU and SuperSU will prompt to install SU binary, go ahead with OK and it will display successful.
ITS 100% WORKING! PERSONALLY TESTED.
CREDITS:-
zhuhang
oRIGINL tHREAD:- http://forum.xda-developers.com/showthread.php?t=2434453
Ѕlαчєя™(For informing me).
manikkumar20 said:
Hey all please help me.
I just got my Tab repaired..CHANGED MOTHERBOARD after a HARD BRICK.
Now i am running ASUS Transformer Pad TF300T Firmware: V10.6.1.27.5 LOCKED.
i dont wanna unlock at this time. please guys help me how can i root it?
Thanks in advance
BTW Motochopper not working, Unlock Root not working.
Click to expand...
Click to collapse
Hi there,
Have you tried downgrading to .15.3 and rooting with motochopper? See my post in this thread for more information.
Good luck on getting root access.
1337 H4X0R said:
Hi there,
Have you tried downgrading to .15.3 and rooting with motochopper? See my post in this thread for more information.
Good luck on getting root access.
Click to expand...
Click to collapse
Can i downgrade without root and CWM?? i have unlocked bootloader.???
Plz tell me the steps. i cnt find exact guide for Locked bootloader to downgrade 27.5 to 15.3?
thx
manikkumar20 said:
Can i downgrade without root and CWM?? i have unlocked bootloader.???
Plz tell me the steps. i cnt find exact guide for Locked bootloader to downgrade 27.5 to 15.3?
thx
Click to expand...
Click to collapse
So you want to downgrade to .15.3 from .27.5 with a locked bootloader. Okay, thats easy because thats what I did to get root after I lost it to a OTA update.
DO THIS AT YOUR OWN RISK-I TAKE NO RESPONSIBILITY IF YOU ACCIDENTLY BRICK YOUR DEVICE!!!!
Downgrade to .15.2 from .27.5 or similar.
1. Download the .15.3 firmware for your device and region from ASUS' website. MAKE SURE THE SKU IS THE SAME AS YOUR DEVICE. e.g., I have WW, so I used the WW firmware. To find out your SKU, go to about tablet and in the build no., it will tell you your SKU, eg build-stuff-here.WW.10.more-number.27.1.
2. Extract the .zip file you downloaded twice. There is a .zip inside a .zip. You should end up with a blob file and a folder. The blob file is the one we need.
3. Make sure your device is backed up via the ASUS app backup, and that all important stuff is backed up.
4. Make sure you have the correct ADB and fastboot drivers. VERY IMPORTANT.
5. If you don't have the Android SDK or access to the fastboot/adb command line, download and install this. It's what I use.
6. Restart your PC to make sure your drivers and software are installed properly.
7. Get your device into bootloader mode. You can do this by...
7ai. Whilst the device is connected to the pc, type "adb devices" (Without quotes) in adb to see if your device is connected properly. If you see your devices serial no., it's working properly. Or else, make sure you have the right files and the device is connected to your pc.
7aii. Type "adb reboot bootloader" (Without quotes) and hit enter. Your device will boot into the bootloader.
****or****
7b. Press and hold the volume down and power buttons until it goes into bootloader mode.
8. Copy and paste the blob file to the root of where your fastboot is running from. If you used minimalistic adb and fastboot. Right click the shortcut, click properties and then open file location. Copy and paste the blob file to there.
9. Make sure your tablet is the only android device plugged in.
10. Execute "fastboot devices" (Without quotes) to make sure that your device is set up properly. If you see your devices serial no., it's working properly. Or else, make sure you have the right drivers/software and the device is connected to your pc.
11. If all is well, execute this command.
Code:
fastboot -i 0x0B05 flash staging blob
DO NOT INTERRUPT YOUR DEVICE DURING THIS OR YOU WILL HAVE END UP WITH A BRICKED DEVICE!!!!
12. It will send the file to your device. When you see blue progress bar, it is now flashing the blob file.
13. Go make yourself a cup of coffee. This may take a while, and staring at it will only make you anxious. Take this advice seriously.
14. When you get back, it should of successively completed.
15. Run "fastboot reboot" (without quotes" to reboot device.
You should now be downgraded.
You may/may not have a problem with the launcher (this happened to me). But if you do, follow these steps...
1. You should be able to log in, but then as soon as you do so, launcher force closes.
You have two options.
2. Swipe down on the right side of the status bar to reveal the quick settings, and then click on settings to go to the settings app.
3. In settings the settings app, Select apps, then all apps.
4. Navigate to "launcher" then clear cache then data, then finally force close.
5. Hit hit the home button, and everything should work as normal
****or****
6. In setting, choose launcher and switch to the ICS launcher.
7. Reboot as prompted
This post will be updated with more information soon. I'm proofreading for any mistakes now...
If you want root, use mottochoper, and then install and use the XPOSED framework because it makes your stock rom feel like a custom one. Its pretty straightforward from there.
If you have any questions, just ask, and remember...
Hit the "THANKS" button, it's a good habit to get into.
FYI, I won't respond to your queries in the next 12 hours since I need to have my sleep, you know. It's nearing the darkness of the night in my side of the sorld. Thanks for your understanding. Speaking of thanks, hit the "THANKS" button if I helped you. I spent a lot of time typing this up!
1337 H4X0R said:
So you want to downgrade to .15.3 from .27.5 with a locked bootloader. Okay, thats easy because thats what I did to get root after I lost it to a OTA update.
DO THIS AT YOUR OWN RISK-I TAKE NO RESPONSIBILITY IF YOU ACCIDENTLY BRICK YOUR DEVICE!!!!
Downgrade to .15.2 from .27.5 or similar.
1. Download the .15.3 firmware for your device and region from ASUS' website. MAKE SURE THE SKU IS THE SAME AS YOUR DEVICE. e.g., I have WW, so I used the WW firmware. To find out your SKU, go to about tablet and in the build no., it will tell you your SKU, eg build-stuff-here.WW.10.more-number.27.1.
2. Extract the .zip file you downloaded twice. There is a .zip inside a .zip. You should end up with a blob file and a folder. The blob file is the one we need.
3. Make sure your device is backed up via the ASUS app backup, and that all important stuff is backed up.
4. Make sure you have the correct ADB and fastboot drivers. VERY IMPORTANT.
5. If you don't have the Android SDK or access to the fastboot/adb command line, download and install this. It's what I use.
6. Restart your PC to make sure your drivers and software are installed properly.
7. Get your device into bootloader mode. You can do this by...
7ai. Whilst the device is connected to the pc, type "adb devices" (Without quotes) in adb to see if your device is connected properly. If you see your devices serial no., it's working properly. Or else, make sure you have the right files and the device is connected to your pc.
7aii. Type "adb reboot bootloader" (Without quotes) and hit enter. Your device will boot into the bootloader.
****or****
7b. Press and hold the volume down and power buttons until it goes into bootloader mode.
8. Copy and paste the blob file to the root of where your fastboot is running from. If you used minimalistic adb and fastboot. Right click the shortcut, click properties and then open file location. Copy and paste the blob file to there.
9. Make sure your tablet is the only android device plugged in.
10. Execute "fastboot devices" (Without quotes) to make sure that your device is set up properly. If you see your devices serial no., it's working properly. Or else, make sure you have the right drivers/software and the device is connected to your pc.
11. If all is well, execute this command.
Code:
fastboot -i 0x0B05 flash staging blob
DO NOT INTERRUPT YOUR DEVICE DURING THIS OR YOU WILL HAVE END UP WITH A BRICKED DEVICE!!!!
12. It will send the file to your device. When you see blue progress bar, it is now flashing the blob file.
13. Go make yourself a cup of coffee. This may take a while, and staring at it will only make you anxious. Take this advice seriously.
14. When you get back, it should of successively completed.
15. Run "fastboot reboot" (without quotes" to reboot device.
You should now be downgraded.
You may/may not have a problem with the launcher (this happened to me). But if you do, follow these steps...
1. You should be able to log in, but then as soon as you do so, launcher force closes.
You have two options.
2. Swipe down on the right side of the status bar to reveal the quick settings, and then click on settings to go to the settings app.
3. In settings the settings app, Select apps, then all apps.
4. Navigate to "launcher" then clear cache then data, then finally force close.
5. Hit hit the home button, and everything should work as normal
****or****
6. In setting, choose launcher and switch to the ICS launcher.
7. Reboot as prompted
This post will be updated with more information soon. I'm proofreading for any mistakes now...
If you want root, use mottochoper, and then install and use the XPOSED framework because it makes your stock rom feel like a custom one. Its pretty straightforward from there.
If you have any questions, just ask, and remember...
Hit the "THANKS" button, it's a good habit to get into.
FYI, I won't respond to your queries in the next 12 hours since I need to have my sleep, you know. It's nearing the darkness of the night in my side of the sorld. Thanks for your understanding. Speaking of thanks, hit the "THANKS" button if I helped you. I spent a lot of time typing this up!
Click to expand...
Click to collapse
Thanks man.
I ll try it today.
I hope i ll not get Hard Bricked 2 time!
1337 H4X0R said:
So you want to downgrade to .15.3 from .27.5 with a locked bootloader. Okay, thats easy because thats what I did to get root after I lost it to a OTA update.
DO THIS AT YOUR OWN RISK-I TAKE NO RESPONSIBILITY IF YOU ACCIDENTLY BRICK YOUR DEVICE!!!!
Downgrade to .15.2 from .27.5 or similar.
1. Download the .15.3 firmware for your device and region from ASUS' website. MAKE SURE THE SKU IS THE SAME AS YOUR DEVICE. e.g., I have WW, so I used the WW firmware. To find out your SKU, go to about tablet and in the build no., it will tell you your SKU, eg build-stuff-here.WW.10.more-number.27.1.
2. Extract the .zip file you downloaded twice. There is a .zip inside a .zip. You should end up with a blob file and a folder. The blob file is the one we need.
3. Make sure your device is backed up via the ASUS app backup, and that all important stuff is backed up.
4. Make sure you have the correct ADB and fastboot drivers. VERY IMPORTANT.
5. If you don't have the Android SDK or access to the fastboot/adb command line, download and install this. It's what I use.
6. Restart your PC to make sure your drivers and software are installed properly.
7. Get your device into bootloader mode. You can do this by...
7ai. Whilst the device is connected to the pc, type "adb devices" (Without quotes) in adb to see if your device is connected properly. If you see your devices serial no., it's working properly. Or else, make sure you have the right files and the device is connected to your pc.
7aii. Type "adb reboot bootloader" (Without quotes) and hit enter. Your device will boot into the bootloader.
****or****
7b. Press and hold the volume down and power buttons until it goes into bootloader mode.
8. Copy and paste the blob file to the root of where your fastboot is running from. If you used minimalistic adb and fastboot. Right click the shortcut, click properties and then open file location. Copy and paste the blob file to there.
9. Make sure your tablet is the only android device plugged in.
10. Execute "fastboot devices" (Without quotes) to make sure that your device is set up properly. If you see your devices serial no., it's working properly. Or else, make sure you have the right drivers/software and the device is connected to your pc.
11. If all is well, execute this command.
Code:
fastboot -i 0x0B05 flash staging blob
DO NOT INTERRUPT YOUR DEVICE DURING THIS OR YOU WILL HAVE END UP WITH A BRICKED DEVICE!!!!
12. It will send the file to your device. When you see blue progress bar, it is now flashing the blob file.
13. Go make yourself a cup of coffee. This may take a while, and staring at it will only make you anxious. Take this advice seriously.
14. When you get back, it should of successively completed.
15. Run "fastboot reboot" (without quotes" to reboot device.
You should now be downgraded.
You may/may not have a problem with the launcher (this happened to me). But if you do, follow these steps...
1. You should be able to log in, but then as soon as you do so, launcher force closes.
You have two options.
2. Swipe down on the right side of the status bar to reveal the quick settings, and then click on settings to go to the settings app.
3. In settings the settings app, Select apps, then all apps.
4. Navigate to "launcher" then clear cache then data, then finally force close.
5. Hit hit the home button, and everything should work as normal
****or****
6. In setting, choose launcher and switch to the ICS launcher.
7. Reboot as prompted
This post will be updated with more information soon. I'm proofreading for any mistakes now...
If you want root, use mottochoper, and then install and use the XPOSED framework because it makes your stock rom feel like a custom one. Its pretty straightforward from there.
If you have any questions, just ask, and remember...
Hit the "THANKS" button, it's a good habit to get into.
FYI, I won't respond to your queries in the next 12 hours since I need to have my sleep, you know. It's nearing the darkness of the night in my side of the sorld. Thanks for your understanding. Speaking of thanks, hit the "THANKS" button if I helped you. I spent a lot of time typing this up!
Click to expand...
Click to collapse
Found another way...chk OP..
manikkumar20 said:
Found another way...chk OP..
Click to expand...
Click to collapse
Nice!
Confirmed and working on .27.5 WW.
Does it works? Want to upgrade from 27.1 to 27.5 to root
joujou333 said:
Does it works? Want to upgrade from 27.1 to 27.5 to root
Click to expand...
Click to collapse
working for sure..done it personally on 27.5 ROM STOCK AND LOCKED BL.
Not to derail the thread but I rooted my ASUS TF300TG with latest 10.2.6.10 firmware with Kingo from http://www.kingoapp.com successfully on locked bootloader.
chrismine said:
Not to derail the thread but I rooted my ASUS TF300TG with latest 10.2.6.10 firmware with Kingo successfully on locked bootloader.
Click to expand...
Click to collapse
Worked for me. Thanks. 10.6.1.27.5
:good:
the version I have from there site is in English, why this one is in Chinese?
Sent from my ASUS Transformer Pad TF300TG using Tapatalk 4
Kobo
Arc, Arc 7, Arc 7HD and Arc 10HD
With the release of not 1 but 3 new devices from Kobo and no specific device forum I thought it time we consolidated any and all root / development available information on them under one roof. All credit for others work will be acknowledged if known.
If anyone has any info they feel should be added please post it and ill add it
The following devices and development status are list below
Kobo Arc - Root + recovery (POSSIBLE PROBLEM WITH NEW SYSTEM UPDATE, Arctic may no longer work)
Kobo Arc 7 - Root
Kobo Arc 7HD - Root + recovery
Kobo Arc 10HD - Root + recovery
Please support development on these projects, sign up to XDA and join in, we need all the help that we can get!
Kobo Arc
Root
Enable unknown sources In security options
Download arctic.apk to your tablet from http://zhuoweizhang.net/Arctic.apk and install, it will do the rest and install Chainfires SU
Enjoy your root access
Please note, the Arctic patch for the original arc may no longer work after a recent system update, possible solution would be to use fiddler to check what response the device receives to with the update, then hardreset device, connect to an access point directed to a proxy with fiddler running and change the response it gets, going to be a pure pain in the bum but it should work, ill maybe add that info later. Or work on a way to flash a ROM from stock recovery....
Credit to
zhuowei @ http://zhuoweizhang.net/ for Arctic.apk
Chainfire for SU
Recovery Mod
Root needed first!
And something like ROM Toolbox for all the various apps needed
Install the android SDK on your computer, you will need to add the google usb drivers, you will find them in the "extras"
Enable usb debug on the arc and install the generic google adb usb drivers
Plug in the device and let it install drivers, it WILL fail one device, manually install drivers for the failed "arc" device that's highlighted with an error, click on it and update the driver, browse, let me pick my own, show all devices, click next and have disc. Click browse and navigate to your android SDK>extras>google USB driver, for the correct drivers, select "ADB interface"
Delete or rename the file on the device located at /etc/install-recover.sh this will make the custom recovery persistent
Copy the recovery.img to the SDCard, either by using drag and drop in windows ( to root of "internal storage") or by adb push "adb push recovery.img /sdcard/
The next job is to open up a command window on your computer and navigate to adb folder, SDK>platform-tools. Type the following exactly, even better copy and paste them!
adb shell
su
cat /sdcard/recovery.img > /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
exit adb shell (ctrl+C) and type
adb reboot recovery
and bobs your uncle, one happy new recovery
Original ROM files
recovery Recovery
xloader Xloader
system System
misc Misc
logos Logos
crypto Crypto
cache Cache
bootlogo Bootlogo
bootloader Bootloader
boot Boot
efs Efs
Custom ROM files
Credit to
Me for recovery mod
Kobo Arc 7
Root
Fully setup device
Download impactor on PC from http://www.cydiaimpactor.com/
Download android SDK on PC, from http://developer.android.com/sdk/index.html
Run SDK manager and acquire the google USB drivers
Enable dev mode on device by going to settings, about kobo, and tap build number 7 times
Enable USB debug mode in developer options
Enable unknown sources in security options
Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.
Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver\android_winusb.inf, for the correct drivers, select ADB interface
Run the impactor program downloaded earlier, once loaded, click on start
Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)
Go to the market place and download SU by Chainfire
EDIT: Impactor was updated which will now make the above work
Credit to
http://www.cydiaimpactor.com/ for the rooting tool
Chainfire for SU
howlinwolf430 for trying the unlock with the new impactor available above
Recovery Mod
howlinwolf430 has a working Recovery img up and running, tests continue but we look forward to seeing this soon!
Kobo Arc 7HD
Root
Fully setup device
Download impactor on PC from http://www.cydiaimpactor.com/
Download android SDK on PC, from http://developer.android.com/sdk/index.html
Run SDK manager and acquire the google USB drivers
Enable dev mode on device by going to settings, about kobo, and tap build number 7 times
Enable USB debug mode in developer options
Enable unknown sources in security options
Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.
Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver, for the correct drivers, select ADB interface
Run the impactor program downloaded earlier, once loaded, click on start
Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)
Go to the market place and download SU by Chainfire
Credit to
http://www.cydiaimpactor.com/ for the rooting tool
Chainfire for SU
Recovery Mod
Ensure SU is working and you can get SU access with adb shell
download the recovery.img attached in to your adb folder
with the device connected to computer type the following
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
ctrl-c
adb reboot recovery
Make sure you allow recovery to make changes when prompted or it will automatically revert to stock recovery
Kobo 7HD notes
Fastboot and Bootloader modes are ONLY available via adb/fastboot commands, there are NO hardware button combos.
adb reboot bootloader / fastboot reboot-bootloader
adb reboot recovery / fastboot reboot recovery
Recovery can be accessed by turning off the device, holding down "VOL DOWN" and turning on, keep VOL DOWN pressed until booted
APX mode can be accessed by plugging in a USB cable connected to a computer, turning off the device, holding down "VOL UP" and turning on, keep VOL UP pressed until booted, note that the screen remains BLACK and as far as I have worked out it is completely useless without certain files we do not have access to.
Kobo Arc 10HD
Root
Fully setup device
Download impactor on PC from http://www.cydiaimpactor.com/
Download android SDK on PC, from http://developer.android.com/sdk/index.html
Run SDK manager and acquire the google USB drivers
Enable dev mode on device by going to settings, about kobo, and tap build number 7 times
Enable USB debug mode in developer options
Enable unknown sources in security options
Plug in device and let it install a USB composite device and a arc 7hd drive, it will fail on the third, go to device manager, and manually install drivers for the "arc" device that's highlighted with an error.
Click on it and update the driver, browse, let me pick my own, show all devices, click next, have disc. click browse and navigate to your android SDK>extras>google usb driver, for the correct drivers, select ADB interface
Run the impactor program downloaded earlier, once loaded, click on start
Check your device screen, you should see an error message, click on decline then decline again and finally decline again, (not sure that makes any difference)
Go to the market place and download SU by Chainfire
http://www.cydiaimpactor.com/ for the rooting tool
Chainfire for SU
Recovery Mod
Ensure SU is working and you can get SU access with adb shell
download the recovery.img attached in to your adb folder
with the device connected to computer type the following
adb push recovery.img /sdcard/
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
ctrl-c
adb reboot recovery
Make sure you allow recovery to make changes when prompted or it will automatically revert to stock recovery
Kobo 10HD notes
Fastboot and Bootloader modes are ONLY available via adb/fastboot commands, there are NO hardware button combos.
adb reboot bootloader / fastboot reboot-bootloader
adb reboot recovery / fastboot reboot recovery
Recovery can be accessed by turning off the device, holding down "VOL DOWN" and turning on, keep VOL DOWN pressed until booted
APX mode can be accessed by plugging in a USB cable connected to a computer, turning off the device, holding down "VOL UP" and turning on, keep VOL UP pressed until booted, note that the screen remains BLACK and as far as I have worked out it is completely useless without certain files we do not have access to.
EDIT: 16th Feb 2014
Arc 10HD received an OTA update "update-ota832-ota932.zip" around the 10th of Feb. Initial look in to this suggests not only are there some system updates the but the bootloader is updated too, its only about 17MB
Edit 6
10HD received a OTA update
Edit 5
thanks to howlinwolf430 Arc 7 now has root, I need to confirm this and the method but I believe the new impactor has added another vulnerability that allows ROOT Thus the guide for the 7HD and the 7 is the same
Edit 4
Recovery img is now complete for the Arc 10HD and 7HD! There are some small configuration changes needed to fix some mounting issues but it backs up and restores just fine
Edit 3
Source code now available for all arcs, git for everything available https://github.com/dazza9075
Recovery Roms for Arc 7HD and 10HD almost complete, just testing to see if it restores correctly
Edit 2
Please note, the Arctic patch for the original arc may no longer work after a recent update
Bootloaders on the 7HD and 10HD appear to be unlocked.
Edit 1
Development on the Arc 7 has stagnated and I no longer have one to directly play with although I do have access if need be.
Sent from my arc 10HD using xda app-developers app
Support needed!
Hi everyone, if your reading this and have some experience in building custom ROMs for unsupported devices and wish to give us a guiding hand please jump on board and help where you can. We currently have working custom recovery's on all devices ( Arc 7 needing a little bit of testing ) but we are needing some support for the next steps!
Many thanks!
Arctic,apk
I have ordered a Kobo Arc online. Any idea if the Arctic.apk does or does not work on them with the system update. Just looking for confirmation
Nice work...I hope it won't remain an isolated effort
@dazza9075: I just ordered the Arc 10HD - can I safely update the software once I get it and root it AFTER? I didn't see any notes indicating otherwise, but I know from my other Android devices that usually the root/recovery methods are tied to a specific version.
Note I don't even know yet if it will require an update - I'm super-new to the Kobo ecosystem.
BTW: thanks for the work done - I never use an Android phone/tablet/media device that does not have root access and a recovery mechanism to save the day.
kayge said:
I have ordered a Kobo Arc online. Any idea if the Arctic.apk does or does not work on them with the system update. Just looking for confirmation
Click to expand...
Click to collapse
after the most recent and probably last system update it is disabled. I stopped my arc from updating so cant confirm without a full reset but the original author of the arctic apk has said it no longer works, I cant see any reason for him to lie.
Ipse_Tase said:
@dazza9075: I just ordered the Arc 10HD - can I safely update the software once I get it and root it AFTER? I didn't see any notes indicating otherwise, but I know from my other Android devices that usually the root/recovery methods are tied to a specific version.
Note I don't even know yet if it will require an update - I'm super-new to the Kobo ecosystem.
BTW: thanks for the work done - I never use an Android phone/tablet/media device that does not have root access and a recovery mechanism to save the day.
Click to expand...
Click to collapse
ok, Kobo will do a system update as soon as you turn the thing on, you cant even get around that (although some fiddling with fiddler might fool it if we can ID what is going on). however, to date there hasn't been an update that disables it. and if there was we can simply flash my stock ROMs which already have root and are flashable.
what we are lacking however is a custom ROM for any of the arcs. More importantly than that we are lacking people to help us!
Weird, I could not install the ADB drivers from the SDK (Win 7 64-bit Enterprise). Had to use my trusted Nexus Root Toolkit and worked fine with that.
I'm liking it so far....appreciate your work to document the rooting procedure.
Let's hope development will pick up at some point, it's a good device (I have the ARC 10HD - got it on sale + coupon in Canada).
Been meaning to ask: have any of you guys found a good screen protector for the Arc 10HD?
I realize this is off topic (sorry OP) but I feel there is ZERO chances I would get an answer elsewhere than in this thread - the only valuable one on XDA re Kobo.
Ipse_Tase said:
Been meaning to ask: have any of you guys found a good screen protector for the Arc 10HD?
I realize this is off topic (sorry OP) but I feel there is ZERO chances I would get an answer elsewhere than in this thread - the only valuable one on XDA re Kobo.
Click to expand...
Click to collapse
Actually I don't, I have a leather case for mine that acts as a stand and protector,i don't sell them either but I suspect that will change soon
Sent from my arc 10HD using xda app-developers app
Ipse_Tase said:
Weird, I could not install the ADB drivers from the SDK (Win 7 64-bit Enterprise). Had to use my trusted Nexus Root Toolkit and worked fine with that.
I'm liking it so far....appreciate your work to document the rooting procedure.
Let's hope development will pick up at some point, it's a good device (I have the ARC 10HD - got it on sale + coupon in Canada).
Click to expand...
Click to collapse
Bazaar, I thought they were the same drivers, well I'm glad it worked eventually, if you or anyone else wants to help with dev you could try searching if there are other devices with the same SoC , we are looking for same gpu/CPU combo that already has a working custom ROM.
Sent from my arc 10HD using xda app-developers app
Yep...I am looking in the Transformer TF-701t forums. I'm not on the software side of Hi Tech, so I'll have to do some reading as I am as frustrated as you with the lack of interest in this platform.
BTW: you may want to add to your tutorial that after booting in Recovery for the first time, the user should accept to make boot.img changes - as otherwise all the frequent updates will wipe the recovery you installed. I was too quick to reboot and now I have to push recovery again.
Or if you think this is not safe to make permanent (I did it on every other Android device I own) maybe that should be stated too. People might want to get OTA updates and it is my understanding that with a custom recovery you won't be getting them. Hell, I'm still hoping we will get a stock KitKat at some point.
Thanks...for being the only one that cares
PS. From what I read about Netflix (big user....I "cut the cord" a year ago) it seems we need 4.3 for Netflix to run in HD (DRM ****). All I can say is that I don't get HD now - so it seems true.
One good reason to hope for a Kobo upgrade. I am already plagued with Ouya being stuck at 4.1.2
Very surprised at the pack of interest in the Kobo tablets, given the impressive combination of awesome specs and very low price. Have an Arc 7 32gb and an Arc 7 16gb in the family and gathering my forces to root em both.
I've read the forum but am a bit thick. Bottomline, are the root guides here conformed working on the latest updates since November 2013?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
JoshReuben said:
I've read the forum but am a bit thick. Bottomline, are the root guides here conformed working on the latest updates since November 2013?
Click to expand...
Click to collapse
I just rooted my ARC 10HD 2 days ago, AFTER it got the last update (something one cannot prevent when setting it up for the first time).
JoshReuben said:
Very surprised at the pack of interest in the Kobo tablets, given the impressive combination of awesome specs and very low price. Have an Arc 7 32gb and an Arc 7 16gb in the family and gathering my forces to root em both.
I've read the forum but am a bit thick. Bottomline, are the root guides here conformed working on the latest updates since November 2013?
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Should work fine, they updated the bootloader a couple of days ago on the 10HD but nothing appears to have changed, some system updates, some app updates, not a lot else from first impression
Ipse_Tase said:
I just rooted my ARC 10HD 2 days ago, AFTER it got the last update (something one cannot prevent when setting it up for the first time).
Click to expand...
Click to collapse
it updated the other day. ive been away for a bit so cant be sure when.
Kobo contact
I could not find a way to send an email to Kobo support or get in touch with someone in this company. As a legitimate user I have a legitimate question for them: what are the plans moving forward with software upgrades?
They don't seem to realize that part of the problem of not selling more devices is also the complete lack of communication (including advertising) from this company.
Mind blowing...
That being said, I love my Arc 10HD and seeing how much better my old Xoom is with KitKat, I can only imagine what it would mean for the Kobo family.
PS. I ended up buying this screen protector:
http://www.illumishieldstore.com/iL...e-Anti-Fingerprint-Replacements/dp/B00F6FJHNU
Ipse_Tase said:
I could not find a way to send an email to Kobo support or get in touch with someone in this company. As a legitimate user I have a legitimate question for them: what are the plans moving forward with software upgrades?
They don't seem to realize that part of the problem of not selling more devices is also the complete lack of communication (including advertising) from this company.
Mind blowing...
That being said, I love my Arc 10HD and seeing how much better my old Xoom is with KitKat, I can only imagine what it would mean for the Kobo family.
PS. I ended up buying this screen protector:
http://www.illumishieldstore.com/iL...e-Anti-Fingerprint-Replacements/dp/B00F6FJHNU
Click to expand...
Click to collapse
Ask your question at http://kobo.frontlinesvc.com/app/ask
They are usually pretty quick to get back to you, as for upgrades, I've not heard any news of anything so really don't know what the official line is, I've not heard any news on new devices either so we may get at least one supported is upgrade. Ideally though we need to nail our own ROM to be sure
Sent from my arc 10HD using xda app-developers app
The One-for-All Guide to rooting, improving, and fixing various errors in Xiaomi Redmi Go!Hello everyone! This thread that I made is for all people who wants to modify and gain full access, as well as to repair their Xiaomi Redmi Go devices the well-guided way, I've noticed that nobody has made an all-in-one guide for this phone so I decided to do it, this thread will keep on expanding depending on what I will discover about this phone, but for now, here is the thread, i expect that you have at least a little amount of knowledge when it comes to phones such as ADB and Developer Options.
What can we do with Xiaomi Redmi Go:
1. We can root it, and the best root manager for this phone is Magisk, SuperSU is also good, but if you're planning to use your phone for mobile banking, then Magisk is right for you. (Unfortunately this isn't true right now due to ctsProfile being hard to manipulate, Redmi Go supports hardware backed key attestation which means your device will definitely be not certified no matter what you do, so until we get a new method, don't root your phone if you want to use apps like Google Pay
2. TWRP is the current custom recovery available for this phone, it has flaws, but its currently the best out there, so its worth the shot to install it, the thread for it will guide you.
3. No custom kernels, people said that they have managed to install AOSP 9 and GSI on this device and made it boot up, but for me, it's better to wait for the official ROM update, after all, the device is still supported.
Prerequisites:
1. Xiaomi Redmi Go
2. An internet connection, a strong one is recommended if you want to download a ROM.
3. A computer with SDK Platform Tools ready to use, this is required, the link is here: https://developer.android.com/studio/releases/platform-tools
Don't forget to also get its driver! The link is also here: https://developer.android.com/studio/run/win-usb
The drivers are tricky to install but I will guide you on doing it in the easiest way possible, please continue on the thread.
4. SD card, your user data will be erased later, better back your files up, this is a warning.
5. Turning on "OEM unlocking" and USB Debugging in Developer Options, this is also really important!
Table of contents:
1. Unlocking the bootloader (and setting up ADB)
2. Rooting
3. Applying the custom recovery
4. Additional modifications
5. Stock ROM links
6. Bonus Section
WARNING: I am not responsible for anything that happens to your device as you follow my guide, do not blame me if you turned your device into a paperweight, made it explode, made it fly or whatever it may be, you chose to modify this phone and you should be accountable for it, you must know the consequences of what you're doing, try to point your finger at me because of what YOU did and I will laugh at you.
I am ready to assist though, so please feel free to ask some questions!
Let us begin, this will take several minutes, so please be patient and avoid rushing.
1. Unlocking the bootloader.
NOTE: This requires your computer to have SDK Platform Tools extracted to any location as long as its easy to access, and its really complicated to talk about it here, this step doesn't include the method where you request a code from Xiaomi, but I've provided a link for it.
A. First, get your phone up, and open the folder on where the SDK Platform Tools are placed, make sure that your in the directory where you see the .exe files of the SDK, now, hold Shift on the keyboard and click "Open Command Prompt here" and type "adb reboot bootloader", without quotes don't forget! This applies to all the steps that I will provide, don't forget to change the USB connection mode of your phone to PTP for it to be detected by ADB! (Only applies to Windows 8/8.1) Once your phone is asking for an authorization, check "Always allow this computer" then tap allow.
B. Once your device has been booted up into Fastboot or the bootloader, check first if your device is being detected, type "fastboot devices", if yes then proceed, if no, then stop here for now.
1B. If this happens then you may have to check your drivers and see if its installed correctly, once your device can be seen at "adb devices" it should also been seen in "fastboot devices" and when the phone is in adb sideload, if not then you have to reinstall ADB, get the proper drivers and do it again.
C. Now, type "fastboot oem unlock-go", the terminal will warn you that all of your user data will be removed, if you have them backed up then and go ahead and enter the command, if not, then just type "fastboot reboot" and start backing up your files, then do this again.
D. The phone will boot up and say "Erasing", to confirm that your phone has its bootloader unlocked, once it boots up again see if it says "Unlocked" on the bottom part of your screen, if there is then congratulations, it should be unlocked at this point.
1D. https://www.getdroidtips.com/unlock-bootloader-xiaomi-redmi-go/, this one particular link provides you on how to unlock the bootloader by entering a certain code, I believe this is a safer method but requires a bit of time, go here if you're interested.
NOTE: The phone supports the command "fastboot flashing unlock_critical" if you are going to unlock your phone with the normal command (fastboot oem unlock_go/fastboot flashing unlock), consider using this 2nd command too, what it does is that it allows you to also flash partitions you supposedly don't have access to, just be very careful not to flash any wrong file! It will be useful to make the "flash_all.bat" script work that you can find on the fastboot ROM for this device, more below!
Once your bootloader has been unlocked, you can now proceed to the other steps that I provided here, don't forget to enable USB Debugging on your Developer Options.
1.2 Setting up ADB
1. Grab your phone, unlock and open your Developer Options then enable "USB Debugging", then change your connection type to "PTP" if you are using Windows 8/8.1, I am not sure if this is required on 7, but it is not needed on Windows 10.
2. Go to this link: https://developer.android.com/studio/releases/platform-tools and download the .zip file, then extract it to a location that is easy to access, like your desktop.
3. Get the official Google drivers here: https://developer.android.com/studio/run/win-usb download the .zip file as well, and extract it too.
4. Go to the extracted folder of your SDK Platform Tools, and go to the directory where you can see various .exe files such as "adb.exe", now, hold the Shift key then click the Right mouse button, then click "Open command prompt here" If this doesn't work for you, open up CMD with admin rights, then type in cd *the location of your platform tools* say on mine, I will input cd C:\Users\James\Downloads\platform-tools_r31.0.3-windows\platform-tools then enter
5. Open your Device Manager by pressing Windows + R, put "devmgmt.msc" without any quotes then Enter, do not close the Device Manager until you're done with all the steps! And please be fast here too or else ADB will not work, now go to your extracted folder of the Google USB driver, and look for the file "android_winusb.inf", copy the location path of it as you will need the exact location path of the file later, in my case it was "C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\android_winusb.inf".
4A. There are 3 main ADB devices that you have to install, Android ADB Interface, Android Bootloader Interface and Android Composite ADB Interface, so I will divide this into 3 sections, have your Device Manager, and the exact location of the .inf.
NOTE: Turn off the internet connection of your computer, why? Because, if you let Windows install the drivers for you, the drivers may be incorrect and will break things apart, as we will encounter several "Unknown devices" in the Device Manager and we have to update them with the extracted files from Google.
Android ADB Interface
1. Now, make sure that USB Debugging is enabled, now plug in your phone and let the drivers install WHILE your computer is offline, now go to your Device Manager after the driver installation and you should see that there is a driver named "Android" with an exclamation mark.
2. Select the "Android" driver with an exclamation mark, then click "Update device driver", click "Browse my computer for driver software" then click "Let me pick from the list of devices on my computer", click Next, then click "Have Disk", now, remember the location path you copied earlier? Now paste that path (like C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\) to the white bar under "Copy manufacturers files from:", overwrite the A:\ with your copied path then Browse, select the "android_winusb.inf" and click OK, now, select the "Android ADB Interface", once the driver has been installed and the interface doesn't give errors such as "The device cannot start", then you're good to go.
NOTE: If you plug your phone and there is no "Android" device with exclamation mark, you can proceed to try and see if adb detects your device by typing "adb devices" in the command right now, it should be since this is what I experienced when setting up my device in Windows 10, this step usually applies only if you are using Windows 8/8.1
Android Bootloader Interface
1. To test, go to the command prompt you opened earlier, and type "adb devices", the device should now be detected at this point, when it does, type "adb reboot bootloader".
2. Now, make sure USB Debugging is enabled on the device before booting it into bootloader, now plug in your phone again and let the drivers install WHILE your computer is offline, Go to your Device Manager after the driver installation and you should see that there is a driver named "Android" with an exclamation mark.
3. Select the "Android" driver with an exclamation mark, then click "Update device driver", click "Browse my computer for driver software" then click "Let me pick from the list of devices on my computer", click Next, then click "Have Disk", now, remember the location path you copied earlier? Now paste that path (like C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\) to the white bar under "Copy manufacturers files from:", overwrite the A:\ with your copied path then Browse, select the "android_winusb.inf" and click OK, now, select the "Android Bootloader Interface", once the driver has been installed and the interface doesn't give errors such as "The device cannot start", then you're good to go.
Android Composite ADB Interface
1. Before proceeding, type "fastboot devices", the device should now also be detected on fastboot, now, type "fastboot reboot", and afterwards, enable "USB Debugging" on the Developer Options, then go your command prompt, then type "adb reboot recovery".
2. Now, now plug in your phone again and let the drivers install WHILE your computer is offline, now go to your Device Manager after the driver installation and you should see that there is a driver named "Android" with an exclamation mark.
3. Select the "Android" driver with an exclamation mark, then click "Update device driver", click "Browse my computer for driver software" then click "Let me pick from the list of devices on my computer", click Next, then click "Have Disk", now, remember the location path you copied earlier? Now paste that path (like C:\Users\Symphony\Desktop\latest_usb_driver_windows\usb_driver\) to the white bar under "Copy manufacturers files from:", overwrite the A:\ with your copied path then Browse, select the "android_winusb.inf" and click OK, now, select the "Android Composite ADB Interface", once the driver has been installed and the interface doesn't give errors such as "The device cannot start", then you're good to go.
2. Applying the recovery/custom recovery
A. Open up your phone and ensure that USB Debugging has been enabled, now, open up your command prompt just like in Step 1 in Unlocking the Bootloader and type "adb reboot bootloader"
B. Next up, type "fastboot flash recovery path/to/recovery.img", substitute the path/to/ with the actual location of your recovery, and please make sure that the name of the image is "recovery.img"! Or else it will not overwrite/update the recovery, you can also put your recovery.img directly within the platform-tools folder so that all you have to type is "fastboot flash recovery recovery.img" then press enter.
C. Once your done, reboot the phone and press Volume Up + Power at the same time, and the recovery will start. (You may want to do this else the recovery will be automatically removed and replaced with the stock one)
1C. For the stock recovery, once you press the combination, the phone will say "No command", at this point, hold your Power button and press Volume up one time to get into recovery.
https://forum.xda-developers.com/android/development/recovery-twrp-3-3-0-redmi-t3929282 here is the link of the TWRP recovery, I encourage you to follow the steps mentioned in the post properly.
WARNING: The fix I provided below is now pushed here for 1 certain reason, before you try to root your phone and do everything else, you must decrypt your internal storage first and it is quite easy, first you must get the decrypt.zip linked in this thread (if the .zip cannot be found, I still have a copy of it), go to TWRP and do "format data", not Wipe Data! How so? Once you reboot to TWRP, it will show you the "Wipe" button, tap that, then the "Format Data" button should show up, this will require you to type in "yes" so type it in, then once it is done formatting, go back to the main TWRP screen, tap "Reboot", then "Reboot to Recovery", afterwards you must go to "Install" then proceed to install the "decrypt.zip", after that you can now flash .zip files from your internal storage too, but beware that you must do this every time you update your device!
3. Rooting your phone
A. To get started, install TWRP for your phone first.
B. Get the .zip file of Magisk/SuperSU so you can install them, the links are https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 and https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
C. Reboot your phone to recovery or just plug it in, open the command prompt again just like in the previous step and put "adb reboot recovery" without quotes.
D. Tap "Install" on your TWRP recovery and select the respective installation .zip file of your chosen root management app, and wait for it to finish.
1D. The .zip for both SuperSU and Magisk can be installed through "adb sideload", if incase you don't have an SD card! It may also work with fastboot as well but I need someone to confirm this.
E. When it's done, wipe the cache first, then reboot.
1E. If the root management app didn't appear in your phone after boot, just install the APK of it in the Play Store and check if root has been applied, if not, repeat step C and D again.
BONUS: It may be useful also to grab EdXposed or LSposed for Magisk and the link is here: https://forum.xda-developers.com/t/...or-of-xposed-oreo-pie-q-r-2020-07-19.4070199/ and here: https://forum.xda-developers.com/t/...e-magisk-module-edxposed-alternative.4228973/, please choose only one! You will use the normal Xposed if you're using a different root management app such as SuperSU, the link is here: https://forum.xda-developers.com/showthread.php?t=3034811
What this does is that if the app is an Xposed/EdXposed/LSposed framework module, any modifications it does to your phone will be based on memory only, it won't modify your phone directly which means your device will be clean, and if it incase the said modification bricks your phone, you can easily recover from it too!
BONUS 2: I also recommend getting the Busybox module from Magisk itself, it can easily be downloaded from the Magisk app, you will need this module if you want your root applications to work more efficiently and avoid errors, as most of them requires Busybox to work, don't use the Busybox installer apps on Play Store as they modify /system directly, only use it if you are using SuperSU.
4. Additional modifications
Once you've managed to root your phone and everything else, what I recommend you could do with your device is to get the following apps:
Titanium Backup - It has the ability to back up apps on your phone, and even its data! this app could do so much more than with what I just mentioned.
LSpeed - A root boosting app that has almost every root tweak packed into it, its really convenient to use! I do not recommend using Entropy tweaks as I heard it is a placebo.
Greenify - For me, this is the only legit battery saving app aside from LSpeed which also offers tons of battery saving features, it requires Xposed to have more options you have to buy it to gain full functionality
ROM Toolbox - This app pretty much contains everything a rooted user needs, such as a terminal and root-based file manager.
System app uninstaller (optional) - Just in case if you're planning to remove some bloatware (the list of it is below)
Root Browser - An alternative to ROM Toolbox, this root explorer is really popular and gets the job done without any interruptions.
Terminal emulator - This will allow you to enter various commands on your phone, like being able to reboot the phone without using any keys.
In order to make the phone as fluid as possible, just leave it with stock ROM installed, try to also use lite apps like Facebook Lite to reduce RAM and battery consumption.
Kernel Adiutor - Another great root application, it's like LSpeed but it doesn't automate tweaks, it instead allows you to modify most of it on your own, then it reapplies your tweaks every time your cellphone will boot up if you tap the "Apply on startup" switch. the link for the app is here: https://m.apkpure.com/kernel-adiutor-root/com.grarak.kerneladiutor
NOTE: Most of these apps can be found on the Play Store, and please don't install any more similar root boosting apps such as HEBF, scripts such as V6 Supercharger, or modifying files like build.prop, it is due to the fact that this will conflict with LSpeed, as LSpeed contains most of the tweaks that past scripts and apps provide, this will result in your phone slowing down a lot, Greenify will require Xposed Framework which is mentioned above on the Rooting section, the link to LSpeed is here https://github.com/Paget96/LSpeed, because the app has been removed from Play Store.
WARNING: The perf.zip https://forum.xda-developers.com/android/development/-t3935220 here, that was provided in Xiaomi Redmi Go forum section must be applied with extreme caution, you have to make a backup of your build.prop in /system, and build.prop + default.prop in /vendor for easy recovery, you can use ZipMe to easily make a backup for these files.
5. Stock ROM links
https://xiaomirom.com/en/rom/redmi-go-tiare-global-fastboot-recovery-rom/, this link so far provides all the ROMs (both recovery and fastboot) available for download on this phone, and they are actually light enough, so it will be easy to download them.
https://xiaomifirmwareupdater.com/archive/miui/tiare/ a new link I've found recently, this rom contains the .tgz format of the latest ROM for the Xiaomi Redmi Go, which could be used for fastboot and Mi Flash Tool, just search for the model and go for Global.
NOTE: Most of the ROMs for this phone provided on several sites, even on the actual Xiaomi website, has an invalid format of .zip, and doesn't contain a flashall script, as a result, Mi Flash Tool will never be able to use these ROMs, you could not also use adb sideload and fastboot for these ROMs, only the stock recovery of the phone could install the ROM, due to the links provided above finally giving the latest ROM versions for the phone, extracting the stock recovery is very easy now, you can do it yourself but if you need a link, tell me.
5A. Applying the stock ROM
This section will be divided into 2 sections, flashing the ROM through recovery, flashing the ROM through fastboot manually, or automatically with flash_all.bat
Stock recovery method.
A. Download the stock ROM with .zip format and put it into your SD Card.
B. Flash your recovery back to stock with the steps given above, boot into your stock recovery, then using your Power button and volume keys to navigate, select "Apply update from SD card".
C. Select the .zip file and wait for the update to finish.
D. The device will boot up automatically after, if not, just go back to the main menu of the recovery and select "Reboot system", enjoy!
Fastboot manual flashing method.
A. Ensure that you have prepared your device and computer for ADB, now grab the ROM given in this thread in .tgz format, and keep extracting the file until you see the files such as "flash-all.sh" after extraction, as you need to extract the .tgz ROM two times before you could use it properly.
B. Now go to the extracted folder of the stock ROM, go the "images" folder and copy the following image files: boot.img, system.img, recovery.img (make a backup of this file somewhere!), vendor.img, cache.img, userdata.img, persist.img, and splash.img.
C. Paste them to the extracted folder of your SDK Platform Tools where various .exe files are located such as "adb.exe", or in my case the location is "C:\Users\Symphony\Downloads\platform-tools_r29.0.4-windows\platform-tools".
D. Now open your command prompt on this directory, or Shift + Right click, then plug in your phone, now type "adb reboot bootloader" so your phone will go to bootloader, don't forget to enable "USB Debugging" and PTP connection mode before rebooting! (only applies to Windows 8/8.1, it may vary on Windows 7 but it is different on 10, no need for PTP connection mode, you can just turn on USB debugging and that's all)
E. Now, this is a little tricky, but try to follow me as much as you can, make sure first that you are detected with "fastboot devices", input the following commands that I will give so you can flash the ROM to your phone, now go to the command prompt and:
To flash the boot.img to your phone, put the command: "fastboot flash boot boot.img"
For the recovery, the command is: "fastboot flash recovery recovery.img"
For the system or main OS: "fastboot flash system system.img"
For cache: "fastboot flash cache cache.img"
For persist: "fastboot flash persist persist.img"
For the vendor or additional system files: "fastboot flash vendor vendor.img"
For data or apps: "fastboot flash userdata userdata.img"
For splash or probably boot animation: "fastboot flash splash splash.img"
D. After that, type "fastboot reboot", and enjoy!
Fastboot automatic flashing method (NEW!)
A. Extract the fastboot ROM 2 times as instructed, after getting the files, grab all the files and copy it to the directory of your platform tools where files such as "adb.exe" can be found, just copy all the files in there and that's all you have to do.
B. Open the "flash_all.bat" on Notepad and remove the following lines:
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *tiare" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *tiare" || exit /B 1
Afterwards, save the .bat file, that should be ready to use now
C. As instructed above, you must also do "fastboot flashing unlock_critical" after unlocking your bootloader the normal way, this will act as your 2nd unlock command, without this, the flash_all.bat will not work as it should be.
D. Boot up your phone in fastboot mode, open up your adb devices and make sure that your phone is seen in "fastboot devices", once it does, type in "flash_all.bat" without any quotes and execute it, the command will now automatically flash everything without you doing anything else, it will also automatically reboot after doing so.
Bonus section:
1. TWRP-compatible stock ROM
For this part, in order for you to generate a TWRP-flashable stock ROM is by basically making it yourself, you have to make sure that your patch is latest, and its pretty much a good idea to just tick everything in the backup selection except for the recovery, as well as the cache as you don't need those.
Once you have it, go ahead and keep it somewhere safe but easy to find, so if case that you need to use it, you could get it immediately, this is extremely useful so please just do it, as of now, I've confirmed that only the /data backup was usable, but please try to confirm if other partition backups are working for you.
Certain custom ROMs that can boot up in this device could be flashed through TWRP though, and the links of them are provided here in this thread.
2. GSI, AOSP 9 and custom ROMs
The link for AOSP is provided here: https://forum.xda-developers.com/android/development/redmi-aosp-9-t3922192
The link for GSI is right here: https://forum.xda-developers.com/android/general/tested-gsi-redmi-t3924705
These images/ROMs can be applied with TWRP, just make sure to follow the steps mentioned in these posts to avoid inconvenience, don't forget to take precautions too! I haven't tried them, but so far I believe that these are stable to use.
There are also custom ROMs released for the device but I am lazy to link all of them, they can easily be found by going here: https://forum.xda-developers.com/tags/xiaomi-redmi-go/
Please take note that I haven't tested these custom ROMs yet and I most likely never will, since the stock ROM for the device is already good enough, you can comment here and tell me what custom ROMs are stable so I can link them here for future reference.
3. Current status
My phone is still working, yes! and it's still staying strong, updated to 2.25 using the fastboot method and it is still fast, the only issue currently is that SafetyNet is a lot more secure than before, so it will be impossible to use stuff like Google Pay for now.
I usually decided to lay low and just stay with my LSpeed, Kernel Adiutor and Greenify, all I had to do is to tinker with these apps and my phone just reached into a whole new level! The performance improvement is nice, that I didn't need to use a custom ROM anymore.
4. How to install a OTA update after rooting your device
Due to the changes made by Google on SafetyNet, and the fact that this device will always require you to wipe the device every update, it is pretty much the same, it doesn't matter anymore if you are certified or not, you will still receive an OTA update even if your device is not certified as long as you are using the stock ROM, you only won't be able to install it, and if you want to install the OTA update you must install it by flashing the updated fastboot ROM, I have links for it above, you can try installing the OTA updates yourself through the settings but you will still have to do a factory reset anyway, you have to also unroot also and revert to stock recovery, else the installation will fail, and your device may slower afterwards.
5. Bloatware you can safely remove (NEW!)
So, like I said above, as much as how lightweight the device is, there are still bloatware that you can remove if you really want, but it's only 3 of them:
Mi Video
Mint Browser
Mi Music
The rest such as Mi Share and Mint Launcher are also bloatware, you can remove them but to me they are useful so I didn't, do not remove the "Cleaner" app, if it however says something like "com.CleanMaster", you can try removing it but take caution as your Play Store may be removed along with it too.
Credits to everyone who made the apps/tools that I mentioned here! such as @topjohnwu for the Magisk, and @YasiR Siddiqui for the TWRP, @Paget96 for the awesome LSpeed app, @rovo89 for the Xposed Framework and many more, you guys totally rock!
Hello and thank you for this tutorial. I'd like to ask. Do You know a way where I can unlock the bootloader without permissions or oem unlock? I have a soft-bricked device and for me, there is no way I can get into the OS and manually switch the Oem unlock setting. I've tried different softwares, different adb commands, different region firmwares, still no luck. I can't also get into the the download mode. I mean, yeah, I get the "no command" screen but after pressing power button + up volume button my phone restarts into the fastboot mode and there is no way I can normally boot. It's looping to fastboot mode over and over...
TheAngryGuitarist said:
Hello and thank you for this tutorial. I'd like to ask. Do You know a way where I can unlock the bootloader without permissions or oem unlock? I have a soft-bricked device and for me, there is no way I can get into the OS and manually switch the Oem unlock setting. I've tried different softwares, different adb commands, different region firmwares, still no luck. I can't also get into the the download mode. I mean, yeah, I get the "no command" screen but after pressing power button + up volume button my phone restarts into the fastboot mode and there is no way I can normally boot. It's looping to fastboot mode over and over...
Click to expand...
Click to collapse
Can you please elaborate all of what you've done so far? I will also ask you a few questions.
1. Is your phone usable with the platform tools? I mean with adb and such.
2. Did you try going into recovery and flashing stock ROM through there?
3. Is your phone being detected by "fastboot devices"? The fastboot mode of Redmi Go is its download mode, and i've provided the link for the stock ROM that's usable thru fastboot mode, as well as on how to apply it.
My phone is usable with adb and such, the recovery mode was not working, only the fastboot. I've tried flashing stock rom with the flash tool but I had no success with a bricked soft and a locked bootloader. I've finally fixed it by going into the edl mode by test point method then I flashed the stock rom, and I've fixed my problem this way. I couldn't unlock the bootloader manually from adb or the unlocker tool, but I've did it in the edl way.
TheAngryGuitarist said:
Hello and thank you for this tutorial. I'd like to ask. Do You know a way where I can unlock the bootloader without permissions or oem unlock? I have a soft-bricked device and for me, there is no way I can get into the OS and manually switch the Oem unlock setting. I've tried different softwares, different adb commands, different region firmwares, still no luck. I can't also get into the the download mode. I mean, yeah, I get the "no command" screen but after pressing power button + up volume button my phone restarts into the fastboot mode and there is no way I can normally boot. It's looping to fastboot mode over and over...
Click to expand...
Click to collapse
TheAngryGuitarist said:
My phone is usable with adb and such, the recovery mode was not working, only the fastboot. I've tried flashing stock rom with the flash tool but I had no success with a bricked soft and a locked bootloader. I've finally fixed it by going into the edl mode by test point method then I flashed the stock rom, and I've fixed my problem this way. I couldn't unlock the bootloader manually from adb or the unlocker tool, but I've did it in the edl way.
Click to expand...
Click to collapse
Can you please elaborate the term "edl mode"?
Good job then, usually, before you modify the phone and start doing something crazy out of stock, your number one step is to really unlock the bootloader, and in order to make things more easier, you should allow your OEM to be unlocked through the developer options, after that you can now unlock the bootloader with fastboot.
_XblackshadowX_ said:
Can you please elaborate the term "edl mode"?
Good job then, usually, before you modify the phone and start doing something crazy out of stock, your number one step is to really unlock the bootloader, and in order to make things more easier, you should allow your OEM to be unlocked through the developer options, after that you can now unlock the bootloader with fastboot.
Click to expand...
Click to collapse
Yes, it's the emergency download mode. You use it when there is nothing you can do about the soft of your device. It automatically unlock the bootloader and you can flash the stock rom. Well, my problem was another. I did not tried to flash roms or recoveries with a locked bl. My phone automatically rebooted into the fastboot mode and from there I was not able to start my phone normally. I've tried rebooting fastboot from adb, unlock bl from adb, no success. I had to dissamembly the phone and make a short-circuit to the test points while slowly pushing in the mtp cable with the battery disconnected. Once I saw the Qualcomm driver on device manager I was able to flash the stock rom. You can search if you want to, for the test pins of this device. Btw, thank for your advice, you are really helpful to the community! ?
TheAngryGuitarist said:
Yes, it's the emergency download mode. You use it when there is nothing you can do about the soft of your device. It automatically unlock the bootloader and you can flash the stock rom. Well, my problem was another. I did not tried to flash roms or recoveries with a locked bl. My phone automatically rebooted into the fastboot mode and from there I was not able to start my phone normally. I've tried rebooting fastboot from adb, unlock bl from adb, no success. I had to dissamembly the phone and make a short-circuit to the test points while slowly pushing in the mtp cable with the battery disconnected. Once I saw the Qualcomm driver on device manager I was able to flash the stock rom. You can search if you want to, for the test pins of this device. Btw, thank for your advice, you are really helpful to the community!
Click to expand...
Click to collapse
Woah, you really had to open the phone before doing it, that's an interesting method!
That part where your phone booted into fastboot was kind of scary, any ideas why it booted into fastboot in the first place? It has to be reported if incase, seems like a dangerous bug.
_XblackshadowX_ said:
Woah, you really had to open the phone before doing it, that's an interesting method!
That part where your phone booted into fastboot was kind of scary, any ideas why it booted into fastboot in the first place? It has to be reported if incase, seems like a dangerous bug.
Click to expand...
Click to collapse
I'm not really sure if a malware caused this issue or a failed system update over-night.
TheAngryGuitarist said:
I'm not really sure if a malware caused this issue or a failed system update over-night.
Click to expand...
Click to collapse
I usually had failed system updates numerous times because when i install them, the phone has already been modified by a lot, and that's actually riskier.
That's why i recommend unrooting and putting back the stock recovery before updating first, still works on mine even with "Device is not certified" by Play Store.
The TWRP linked here is for Pie 9, I couldn't get it to boot on my phone, it shows vertical lines.
This is the older version for Oreo 8...
https://forum.xda-developers.com/android/general/twrp-xiaomi-redmi-beta-t3918993
I formatted the phone from TWRP it so it was no longer encrypted.
Mounted the drive from TWRP and installed the "decrypt.zip" from the other TWRP...
https://forum.xda-developers.com/android/development/recovery-twrp-3-3-0-redmi-t3929282
I unlocked the bootloader successfully.
In the setting up ADB step, I don't clearly understand. When I connect my device to the pc, no drivers are installing. And there is no driver named "Android" with an exclamation mark. But my device is getting recognized in "portable devices >> redmi go". I'm very new with adb it would be a lot of help.
I've attached the screenshot of my device manager,
bhattinb said:
I unlocked the bootloader successfully.
In the setting up ADB step, I don't clearly understand. When I connect my device to the pc, no drivers are installing. And there is no driver named "Android" with an exclamation mark. But my device is getting recognized in "portable devices >> redmi go". I'm very new with adb it would be a lot of help.
I've attached the screenshot of my device manager,
Click to expand...
Click to collapse
Did you try turning on USB Debugging on Developer Options? Did you try installing the USB drivers from Google?
_XblackshadowX_ said:
Did you try turning on USB Debugging on Developer Options? Did you try installing the USB drivers from Google?
Click to expand...
Click to collapse
Yeah, I've done everything you told, I also turned the connection mode to PTP also. Somehow it just not showing that android with an exclamation mark.
after that, I even tried to use the 15-second ADB installer. after installing that I tried to flash recovery but that just didn't do anything. After using that flashing command, I had the same stock recovery.
I'm really thankful you took the time to answer my question.
Help!! My device stuck on screen saying your system has been destroyed. What I had done is locked the bootloader using command fastboot oem lock then this happened. Now i can boot device in stock recovery and bootloader too but when i am trying to unlock bootloader it says device is lock and also i am not able to flash anything. Plz help.
I am not able to flash TWRP on my redmi go
How to update the redmi go to the latest version without formatting/Factory Reset should I just follow Fastboot flashing method and if so which files should I just flash. Thank you
bhattinb said:
I unlocked the bootloader successfully.
In the setting up ADB step, I don't clearly understand. When I connect my device to the pc, no drivers are installing. And there is no driver named "Android" with an exclamation mark. But my device is getting recognized in "portable devices >> redmi go". I'm very new with adb it would be a lot of help.
I've attached the screenshot of my device manager,
Click to expand...
Click to collapse
Hi! sorry for the late reply, if this is the case then it's fine, you can just connect the device, open up adb tools, type adb devices and ensure that your USB debugging is on, and the device will connect immediately, at that point all you need is the adb driver for Fastboot
akki_007 said:
Help!! My device stuck on screen saying your system has been destroyed. What I had done is locked the bootloader using command fastboot oem lock then this happened. Now i can boot device in stock recovery and bootloader too but when i am trying to unlock bootloader it says device is lock and also i am not able to flash anything. Plz help.
Click to expand...
Click to collapse
oh no, but why lock your bootloader? you can try using a recovery ROM, you must have a spare SD Card within you, grab a recovery ROM, put it in your sd card then put it into the phone and use it on stock recovery, you should be able to apply it and boot back into the system, please update me
igpraan said:
I am not able to flash TWRP on my redmi go
Click to expand...
Click to collapse
you must have unlocked bootloader if you want to do so.
niknah said:
The TWRP linked here is for Pie 9, I couldn't get it to boot on my phone, it shows vertical lines.
This is the older version for Oreo 8...
https://forum.xda-developers.com/android/general/twrp-xiaomi-redmi-beta-t3918993
I formatted the phone from TWRP it so it was no longer encrypted.
Mounted the drive from TWRP and installed the "decrypt.zip" from the other TWRP...
https://forum.xda-developers.com/android/development/recovery-twrp-3-3-0-redmi-t3929282
Click to expand...
Click to collapse
that's strange, the TWRP I linked isn't giving me any vertical lines