Related
Before we begin, I'd like to add that I've gone through a lot of threads, guides and searched high and low through the forums for a solution, but seeing as I cannot find a solution, I'll just ask here.
In August, we bought an Asus transformer TF300T from Beijing - it was a good deal. However, the firmware was updated to 10.4.2.13 and Android went to 4.1.1 JB, meaning that http://forum.xda-developers.com/showthread.php?t=1689193 this guide does not work anymore. My device is unlocked, though (not sure how I managed that), but other than that, It cannot be used for everything I'd like to - I have no access to google store nor can I link it to my google account. So now here I am, asking for help with a chinese firmware TF300T and how to get a WW version running on it.
eestikaa said:
Before we begin, I'd like to add that I've gone through a lot of threads, guides and searched high and low through the forums for a solution, but seeing as I cannot find a solution, I'll just ask here.
In August, we bought an Asus transformer TF300T from Beijing - it was a good deal. However, the firmware was updated to 10.4.2.13 and Android went to 4.1.1 JB, meaning that http://forum.xda-developers.com/showthread.php?t=1689193 this guide does not work anymore. My device is unlocked, though (not sure how I managed that), but other than that, It cannot be used for everything I'd like to - I have no access to google store nor can I link it to my google account. So now here I am, asking for help with a chinese firmware TF300T and how to get a WW version running on it.
Click to expand...
Click to collapse
If it were mine I'd use fastboot to flash the latest ww firmware from this link. Unzip the file and find the blob to flash.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
This should put you on the latest ww firmware.
Your unit was probably unlocked when you received it if you didn't unlock.
tobdaryl said:
If it were mine I'd use fastboot to flash the latest ww firmware from this link. Unzip the file and find the blob to flash.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
This should put you on the latest ww firmware.
Your unit was probably unlocked when you received it if you didn't unlock.
Click to expand...
Click to collapse
fastboot as in from the command prompt? Not sure, i take it that I connect my device, and if I have fastboot and adb set up on my computer I just type those 2 commands in? Or in that case, where does the blob have to be?
eestikaa said:
fastboot as in from the command prompt? Not sure, i take it that I connect my device, and if I have fastboot and adb set up on my computer I just type those 2 commands in? Or in that case, where does the blob have to be?
Click to expand...
Click to collapse
Yes from the command prompt with adb and fastboot setup. Using the commands as shown assumes the blob is in the same directory as adb and fastboot. You could place it anywhere if you are willing to give the proper path in the commands but what I suggested is simpler.
I would get both adb and fastboot working properly before I did anything else to your unit. Then you have at least two methods to attempt rescue of your unit it something goes wrong later. Then once you flash twrp you will have at least three options.
eestikaa said:
fastboot as in from the command prompt? Not sure, i take it that I connect my device, and if I have fastboot and adb set up on my computer I just type those 2 commands in? Or in that case, where does the blob have to be?
Click to expand...
Click to collapse
If you use this guide for some help: [GUIDE] Help for flash more faster when you use Fastboot Line Command
tobdaryl said:
Yes from the command prompt with adb and fastboot setup. Using the commands as shown assumes the blob is in the same directory as adb and fastboot. You could place it anywhere if you are willing to give the proper path in the commands but what I suggested is simpler.
I would get both adb and fastboot working properly before I did anything else to your unit. Then you have at least two methods to attempt rescue of your unit it something goes wrong later. Then once you flash twrp you will have at least three options.
Click to expand...
Click to collapse
I checked the devices with "fastboot devices" and it does not list any devices. However, adb devices can find the device.
Okay, one last question - how high is the chance that this'll brick the device? I've been contemplating on this for a while now, and I'm still unsure if this is a safe bet.
eestikaa said:
Okay, one last question - how high is the chance that this'll brick the device? I've been contemplating on this for a while now, and I'm still unsure if this is a safe bet.
Click to expand...
Click to collapse
I cannot says you can't, but for brick a Nexus, you must have one problem with the bootloader (erase or delete or something like that).
Are there any mac detailed step by step guides of how to unlock and root the Nexus 5??
I've seen the 2 main threads here but they are step by step for windows and some of the coding has already been pointed out as wrong for the mac so I'm having a very hard time just unlocking and rooting my nexus 5 which is sitting here.
If anyone could please link me to a detailed MAC guide, I would very much appreciate it.
Thanks.
Willz said:
Are there any mac detailed step by step guides of how to unlock and root the Nexus 5??
I've seen the 2 main threads here but they are step by step for windows and some of the coding has already been pointed out as wrong for the mac so I'm having a very hard time just unlocking and rooting my nexus 5 which is sitting here.
If anyone could please link me to a detailed MAC guide, I would very much appreciate it.
Thanks.
Click to expand...
Click to collapse
I can help you out.
Download and install Android File Transfer, which will install the necessary drivers for your phone to connect to your computer. http://www.android.com/filetransfer/
Enable developer options on your phone by going to Settings > about phone and tapping the build number 7 or so times. Then go to the developer settings and enable USB debugging.
Once this is done, in your folder entitled your "username" in your Mac (the same folder that has Desktop, Documents, Downloads, etc.), create a folder titled Android.
Inside that Android folder, put these two files: http://cl.ly/SMwW and http://cl.ly/SMiC These are adb and fastboot.
Once that's done, open Terminal, type:
Code:
cd /Users/yourusername/Android
and hit enter.
Then type:
Code:
./adb devices
hit enter, and you should see your phone's serial number so long as you enabled USB debugging as described above.
Then type:
Code:
./adb reboot bootloader
hit enter, your phone will reboot to the bootloader
Download this file and place it inside the Android folder we created earlier: http://cl.ly/SMw9 This is the latest TWRP for our phones.
Into the same Terminal window, type:
Code:
./fastboot oem unlock
hit enter, WARNING: your phone will be returned to stock and your storage erased, once that's done, type
Code:
./fastboot reboot-bootloader
and hit enter to reboot back into the bootloader that is now unlocked.
Then to install TWRP, type:
Code:
./fastboot flash recovery openrecovery-twrp-2.6.3.2-hammerhead.img
and then reboot the bootloader again. I would then suggest hitting your down arrow a couple of times and booting into recovery, where TWRP will prompt you to root your device with SuperSU. Alternatively, here is the SuperSU zip that you can put onto your phone's storage and flash in TWRP. http://cl.ly/SMlk
Not sure if you missed it, but alternatively there's a Mac toolkit that's recently been posted.
http://forum.xda-developers.com/showthread.php?t=2515640
I do not want to root using a toolkit on my mac and I am trying to root on my macbook using this thread.
I keep on getting:
-bash: ./fastboot: Permission denied
after I type localhost: ./fastboot oem unlock in terminal
What's going on?
stelv said:
I do not want to root using a toolkit on my mac and I am trying to root on my macbook using this thread.
I keep on getting:
-bash: ./fastboot: Permission denied
after I type localhost: ./fastboot oem unlock in terminal
What's going on?
Click to expand...
Click to collapse
Are you cd'd into the directory where the fastboot binary is?
Also, here is a really good tutorial, Google ftw...
http://forum.xda-developers.com/showthread.php?t=1917237
0dBu said:
Are you cd'd into the directory where the fastboot binary is?
Also, here is a really good tutorial, Google ftw...
http://forum.xda-developers.com/showthread.php?t=1917237
Click to expand...
Click to collapse
Yes I am cd'd into directory and it recognizes my device until a reboot to bootloader. Then while in bootloader mode on my phone, terminal on my computer will no longer recognize my device.
I will take a look at the link though. Thank you. I dont have sdk setup on my computer, maybe thats it.
stelv said:
Yes I am cd'd into directory and it recognizes my device until a reboot to bootloader. Then while in bootloader mode on my phone, terminal on my computer will no longer recognize my device.
I will take a look at the link though. Thank you. I dont have sdk setup on my computer, maybe thats it.
Click to expand...
Click to collapse
When you're in bootloader and you type: fastboot devices what does it return?
0dBu said:
When you're in bootloader and you type: fastboot devices what does it return?
Click to expand...
Click to collapse
Its just blank after I type devices. Before I boot into bootloader though ./adb devices shows me my phones serial number
stelv said:
Its just blank after I type devices. Before I boot into bootloader though ./adb devices shows me my phones serial number
Click to expand...
Click to collapse
If adb devices shows your device you're in recovery, not bootloader
It doesn't show my device in boot loader though. Terminal says permission denied though. Maybe I'll try a different directory when I get back to my computer.
Sent from my Nexus 5
stelv said:
It doesn't show my device in boot loader though. Terminal says permission denied though. Maybe I'll try a different directory when I get back to my computer.
Sent from my Nexus 5
Click to expand...
Click to collapse
Use fastboot devices if you're in bootloader
Anyhow, the link I posted is a good tutorial, it should get you sorted. Although, even though I have ADB and Fastboot in my Path (ADB works fine), I still have to cd into the platform-tools directory to get fastboot to work. If anyone has some insight into that's I'd be all ears, but I still make it work.
Sent from my Nexus 5 using Tapatalk
Thanks guys. I got fastboot working, boot loader unlocked and twrp installed but I had to use the fastboot file from the other thread. The fastboot file in the second post this thread doesn't work correctly.
Now my next problem is I have twrp installed but it is asking me for a password and it will not backup my system. When I try to reboot I get bootloops. I can get back into fast boot though. Do I need to push a ROM file or superuser via fast boot? What is the command for that?
Sent from my Nexus 7
stelv said:
Thanks guys. I got fastboot working, boot loader unlocked and twrp installed but I had to use the fastboot file from the other thread. The fastboot file in the second post this thread doesn't work correctly.
Now my next problem is I have twrp installed but it is asking me for a password and it will not backup my system. When I try to reboot I get bootloops. I can get back into fast boot though. Do I need to push a ROM file or superuser via fast boot? What is the command for that?
Sent from my Nexus 7
Click to expand...
Click to collapse
That has happened to me also. I went ahead and flashed the factory image, and then re-flashed recovery after that and it worked fine.
Sent from my Nexus 5 using Tapatalk
0dBu said:
That has happened to me also. I went ahead and flashed the factory image, and then re-flashed recovery after that and it worked fine.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks. I saw a fix in the twrp thread as follows, so i did this. Twrp is working as normal now and no bootloops. I have the factory image downloaded too just in case. Thanks again! Everything seems to be working now.
Dees_Troy said:
If you have just used fastboot oem unlock, you should let the device boot up normally first before trying to install TWRP. If you boot TWRP first before booting normally, you will be prompted for a password. Hit cancel and got to Wipe -> Format Data. Type yes at the prompt and hit the "enter" key. Hit the home button at the bottom and Reboot -> Recovery. Unlocking the device will cause you to lose all userdata, apps, pictures, downloads, etc.
To root, when you select to reboot from the GUI in TWRP, you will be asked if you want to install SuperSU. Swiping to confirm will root your device.
Click to expand...
Click to collapse
Disclaimer: I am not responsible in any way if using anything I've made causes hard bricks,bootloops,alien abductions or any other problems.
Hey guys!
It's been some time that I've been seeing people having problems flashing the 2nd Bootloader and a custom recovery to the 2012 Kindle Fire HD 7". So,I decided to create this tool. May I present to you,
Flasher
By SafinWasi
This is a batch file which can flash the 2nd Bootloader and a custom recovery to the 2012 Kindle Fire HD 7",complete with ADB and Fast boot executables,stack override,disable auto-recovery update script as well as the 7.2.3 Bootloader downgrade to prevent red screens.
Working features:
Device verification through fastboot.
Flashing Freedom boot and TWRP/CWM Touch/CWM Stock (thanks r3pwn)
Downgrading the Bootloader to 7.2.3
Stack override
Disabling auto-update recovery script
Reboot into TWRP(optional)
Backing up boot,recovery and system partitions.
Restoring previously made backup
Click to expand...
Click to collapse
Steps to use:
Download the zip and extract it.
Read the ReadMe.txt carefully.
Install the Kindle Fire ADB drivers(if needed)
Run Flasher.bat as Administrator.
Follow the on-screen instructions.
Click to expand...
Click to collapse
Changelog:
[01/02/2014]Initial Release
[19/02/2014]Fixed a bug in the backup script
[17/03/2014]Added restore backup option
[24/06/2014]Added support for CWM Touch Advanced Edition and Stock CWM;updated TWRP to 2.7.0.0
Click to expand...
Click to collapse
Download link:
Link 1:flasher-v2-20140624-tate.rar - 31.23 MB
Link 2:flasher-v2-20140624-tate.rar
MD5 Checksum:84313f4b18008f63346853a8666523d5
Click to expand...
Click to collapse
Notes:
This tool is designed to work for Amazon OS version 7.4.6. So,using it on any other software might get you into a bootloop,but the recovery and Freedom-boot will work.Because of this,it is recommended to do the following things before using this tool:
Rooting the device.
Backing up any important data.
Placing the ROM and GApps zips on the sdcard in case you get a bootloop,so that you can just flash those in recovery after doing a complete wipe.
Preparing to lose the Amazon OS
Click to expand...
Click to collapse
Source:
https://github.com/SafinWasi/Flasher.git
Click to expand...
Click to collapse
Credits go to Hashcode,seokhun,BuQQzz,fattire,very green,r3pwn and anyone else whose work helped me.
Please hit the Thanks button if this tool helped you. Feel free to comment below to suggest any modifications,report any issues or for any help.
Thanks.
XDA:DevDB Information
Flasher, Tool/Utility for the Amazon 7" Kindle Fire HD
Contributors
Anonymous.123, SafinWasi
Version Information
Status: Beta
Beta Release Date: 2014-06-24
Created 2014-03-18
Last Updated 2014-07-01
Reserved
bump
Works as expected. Successfully flashed CyanogenMod and installed everything while being on Amazon's latest firmware.
One problem though, it doesn't get into fastboot when I connect the Kindle to the USB, I have to set it to fastboot mode manually via normal ADB method. Might be because I don't have a fastboot cable. Anyways, good work, really useful!
GMattZ said:
Works as expected. Successfully flashed CyanogenMod and installed everything while being on Amazon's latest firmware.
One problem though, it doesn't get into fastboot when I connect the Kindle to the USB, I have to set it to fastboot mode manually via normal ADB method. Might be because I don't have a fastboot cable. Anyways, good work, really useful!
Click to expand...
Click to collapse
Did you turn off the Kindle before connecting? Also,do you have the ADB drivers installed?
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Anonymous.123 said:
Did you turn off the Kindle before connecting? Also,do you have the ADB drivers installed?
Click to expand...
Click to collapse
I do have all the Fastboot and ADB drivers installed.
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
You might want to use this Bin4ry's Root Toolkit to root your Kindle. I've attached the link for you to download.
Root_with_Restore_by_Bin4ry_v33
As for fastboot, adb reboot-bootloader will not work. You'll need to issue this command:
adb shell
su
reboot bootloader
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
Well,you could use the Root with Restore by Bin4ry to root the device. But since you have OS version 7.4.8,you should keep the ROM and GApps zips on the sdcard since using my tool on any OS other than 7.4.6 might get into a bootloop.
FillTheVoid said:
Thanks for the tool. I could use some assistance. I cannot get the device in to fastboot at all.
Adb drivers are working. "fastboot -i 0x1949 getvar product" returns <waiting for device> but plugging it in while powered off just reboots into the OS.
"adb reboot-bootloader" just reboots back into the OS also. This is very frustrating. The only thing preventing me from making this device usable is that I CANNOT get into fastboot. Any suggestions?
OS version 7.4.8
I think It may have something to do with not having root. "adb shell" sets up the shell with a $ prompt but then "su" returns "error /system/bin/sh: su: not found. The device isn't rooted but I was under the impression that I didn't need root to flash the 2nd bootloader through fastboot. Am I incorrect? Thanks for anyone's time and help.
Yes I figured it out. I need root. Now unfortunately QemuRoot isn't working. Maybe the exploit has been patched? Permission to write /system/bin/sh is denied
Any suggestions?
Click to expand...
Click to collapse
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct.
The command you are looking for is (must be rooted to use this command with a USB cord otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
To root use Root Many Android. I recommend using v31 http://forum.xda-developers.com/showthread.php?t=1886460
LinearEquation said:
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct.
The command you are looking for is (must be rooted to use this command with a USB cord otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
To root use Root Many Android. I recommend using v31 http://forum.xda-developers.com/showthread.php?t=1886460
Click to expand...
Click to collapse
Thanks, I have no problem with the SDK and adb/fastboot environment, all that is working as should. It's just root that I need first which clearly I missed somewhere. Once I gain root I should be good to go. I'll try that root exploityou mentioned, (thanks for providing the version number) as the one found in this thread wasn't working. Then I'll fastboot flash back to 4.2 before attempting to install the 2nd bootloader. SHould be good to good. Thanks for your help.
FillTheVoid said:
Thanks, I have no problem with the SDK and adb/fastboot environment, all that is working as should. It's just root that I need first which clearly I missed somewhere. Once I gain root I should be good to go. I'll try that root exploityou mentioned, (thanks for providing the version number) as the one found in this thread wasn't working. Then I'll fastboot flash back to 4.2 before attempting to install the 2nd bootloader. SHould be good to good. Thanks for your help.
Click to expand...
Click to collapse
Well that was a nightmare. Because plugging my kindle in after the "fastboot -i 0x1949 getvar product" wouldn't boot into fastboot I had to issue the "adb shell su -c reboot bootloader" command myself. I then opened up the batch file for OP's flasher tool (thanks again) and entered the commands manually. I now have the second boot loader and TWRP and am Installing CM11. Thanks members of the Fire community for your help and patience and making this Fire usable.
FillTheVoid said:
Well that was a nightmare. Because plugging my kindle in after the "fastboot -i 0x1949 getvar product" wouldn't boot into fastboot I had to issue the "adb shell su -c reboot bootloader" command myself. I then opened up the batch file for OP's flasher tool (thanks again) and entered the commands manually. I now have the second boot loader and TWRP and am Installing CM11. Thanks members of the Fire community for your help and patience and making this Fire usable.
Click to expand...
Click to collapse
No problem bro.
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Bump
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
vampir4997 said:
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It should because it looks like it flashes the same files you would flash were you to do it manually complete with bootloader downgrade. You still want to rot first. Root Many Android v31 for that http://forum.xda-developers.com/showthread.php?t=1886460
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
vampir4997 said:
Does tbis work for 7.4.8? I have a fastboot cable ordered in case i need it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Most probably it will work,but you can never be too careful. Be sure to make a backup by option 2.
Bump
Do i need to be in fastboot for this? Also what is the preffered root method for 7.4.8? Sorry kind of a noob with the kindle
Sent from my Nexus 5 using XDA Premium 4 mobile app
vampir4997 said:
Do i need to be in fastboot for this? Also what is the preffered root method for 7.4.8? Sorry kind of a noob with the kindle
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My tool will boot you into Fastboot. And the preferred (and probably only) root method for 7.4.8 is the Root with restore by Bin4ry v31. LinearEquation answered this question a while ago.
Ty,sorry guess i didnt read back far enough
Sent from my Nexus 5 using XDA Premium 4 mobile app
I have a OnePlus running LiquidSmooth (Lollipop edition), which I flashed using my old Windows 7 laptop. I now have a Windows 8 laptop (no access to Windows 7 at the minute), so I have been testing out my ADB and fastboot connections as I'd heard there were issues with Windows 8.1.
I first tested my old HTC One (m7), and installed the drivers as instructed (too few posts to provide a link, but the instructions I followed should come up if you search for Nocturnal ADB Fastboot). Performed a few test commands (adb devices, adb reboot bootloader, fastboot devices, fastboot getvar all, adb push whilst in recovery) and they all worked fine.
I repeated the driver installs for my OnePlus. I'm testing my it now, and adb devices, adb reboot bootloader and fastboot devices all run fine. However, when I try fastboot get var all, I get the following:
Code:
F:\Nocturnal_ADB_Fastboot>fastboot getvar all
all:
finished. total time: 0.001s
You probably notice from the command prompt output that I'm running ADB from a USB; I have also tried from my HDD. I've also tried getvar IMEI and the result is the same.
Could you please advise whether this is a known issue, if I am doing something wrong, or if my ADB/fastboot link is broken.
Thanks!
You're not getting a response from the fastboot getvar all command because it isn't a valid command for this device. Its a valid command for most Android devices but not this one, don't worry, you're not the first person to make this mistake and you certainly won't be the last.
Ah OK, thanks for that!
Is there an equivalent command to get all of the variables? Or what variables can you get from fastboot on the one plus?
Sent from my A0001 using XDA Free mobile app
Unfortunately they've got that information locked down on this phone, I'm not sure why.
Transmitted via Bacon
Oh well, it wasn't important I was just checking my setup. Thanks for your help.
Sent from my A0001 using XDA Free mobile app
Hello wonderful xda peeps,
My
-
Mi A2
Running Android 10
xiaomi/jasmine/jasmine_sprout
10/QKQ1.190910.002/V11.0.5.0.QDIMIXM
is stuck in bootloop, how can I fix it or at least how do extract my files?
Thank you kind regards!
Micklo said:
Hello wonderful xda peeps,
My
-
Mi A2
Running Android 10
xiaomi/jasmine/jasmine_sprout
10/QKQ1.190910.002/V11.0.5.0.QDIMIXM
is stuck in bootloop, how can I fix it or at least how do extract my files?
Thank you kind regards!
Click to expand...
Click to collapse
What did you do before this happened? Is it your bootloader locked? Can you enter to recovery and/or fastboot?
SubwayChamp said:
What did you do before this happened? Is it your bootloader locked? Can you enter to recovery and/or fastboot?
Click to expand...
Click to collapse
Yes, I can enter Android Recovery and Fastboot.
Yes, the bootloader is locked.
I mistakenly clicked on "Run Graphics Test" in android recovery and it installed some update and my phone has been stuck eversince
Update
I've wiped my phone to factory reset and it is still stuck in bootloop
Micklo said:
Update
I've wiped my phone to factory reset and it is still stuck in bootloop
Click to expand...
Click to collapse
If you have enabled USB debugging and OEM unlock then you can unlock bootloader to get an easy way to send it to EDL mode and you can flash the stock ROM using MiFlash tool.
For future reference this is the first that any user have to do before to "play" with the device so you have more ways to recover it.
There is some probability that your device is trying to boot to the wrong slot, first update your platform-tools if needed https://developer.android.com/studio/releases/platform-tools then see if these commands work:
To identify your current slot type
Code:
fastboot getvar current-slot
then set as active the opposite slot with
Code:
fastboot --set-active=a
changing a for b as opposite slot
Also it exists this tool that can help you but you would need to previously enable USB debugging: https://www.xiaomitool.com/V2/ this tool allows adb (disabled by Xiaomi) to work through recovery stock.
In the case you can't unlock bootloader cause your USB debugging and OEM unlock were not previously toggled then you should have to use MiFlash tool through EDL mode using test point, also there is other tool called QFlash/Qfil.
SubwayChamp said:
If you have enabled USB debugging and OEM unlock then you can unlock bootloader to get an easy way to send it to EDL mode and you can flash the stock ROM using MiFlash tool.
For future reference this is the first that any user have to do before to "play" with the device so you have more ways to recover it.
There is some probability that your device is trying to boot to the wrong slot, first update your platform-tools if needed https://developer.android.com/studio/releases/platform-tools then see if these commands work:
To identify your current slot type
Code:
fastboot getvar current-slot
then set as active the opposite slot with
Code:
fastboot --set-active=a
changing a for b as opposite slot
Also it exists this tool that can help you but you would need to previously enable USB debugging: https://www.xiaomitool.com/V2/ this tool allows adb (disabled by Xiaomi) to work through recovery stock.
In the case you can't unlock bootloader cause your USB debugging and OEM unlock were not previously toggled then you should have to use MiFlash tool through EDL mode using test point, also there is other tool called QFlash/Qfil.
Click to expand...
Click to collapse
Thank you for your kind assistance.
Before it was stuck in boot loop:
- I enabled USB Debugging
- I did not enable OEM Unlocking
Using:
Code:
fastboot getvar current-slot
returned
Code:
current-slot: a
Now running
Code:
./fastboot --set-active=b
i got the following:
Code:
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Micklo said:
Thank you for your kind assistance.
Before it was stuck in boot loop:
- I enabled USB Debugging
- I did not enable OEM Unlocking
Using:
Code:
fastboot getvar current-slot
returned
Code:
current-slot: a
Now running
Code:
./fastboot --set-active=b
i got the following:
Code:
Setting current slot to 'b' FAILED (remote: 'Slot Change is not allowed in Lock State')
fastboot: error: Command failed
Click to expand...
Click to collapse
You are using PowerShell, try to switch firstly to CMD and then type the commands but open it as admin, and check if you have the latest platform-tools.
Also check if the tool provided with link works for you and report back.
SubwayChamp said:
You are using PowerShell, try to switch firstly to CMD and then type the commands but open it as admin, and check if you have the latest platform-tools.
Also, check if the tool provided with link works for you and report back.
Click to expand...
Click to collapse
I am using the correct code because that's how you run the command on Linux or Mac. I'm on a Mac.
The tool did not work for me.
I can't upload an image here
Micklo said:
I am using the correct code because that's how you run the command on Linux or Mac. I'm on a Mac.
The tool did not work for me.
I can't upload an image here
Click to expand...
Click to collapse
I know this is the correct command just I thought you used PowerShell from a Windows some times give errors.
The tool by Francesco Tescari works either through recovery or fastboot so you can try flashing a ROM.
But if for some reason the tool doesn't work your last chance it's either MiFlash tool or Qfil using a Windows machine.
SubwayChamp said:
I know this is the correct command just I thought you used PowerShell from a Windows some times give errors.
The tool by Francesco Tescari works either through recovery or fastboot so you can try flashing a ROM.
But if for some reason the tool doesn't work your last chance it's either MiFlash tool or Qfil using a Windows machine.
Click to expand...
Click to collapse
Thank you for your time and assistance, I eventually got a windows laptop to try it out, I got the Same Error.
I have tried MiFlash tool and I keep getting
Code:
error:"Flash bluetooth_a_error"
or
Code:
error:FAILED (remote: Flashing is not allowed in a Lock State)
I have tried XiaoMiTool V2 and it straight up didn't work.
Let me look up Qfil.
Micklo said:
Thank you for your time and assistance, I eventually got a windows laptop to try it out, I got the Same Error.
I have tried MiFlash tool and I keep getting
Code:
error:"Flash bluetooth_a_error"
or
Code:
error:FAILED (remote: Flashing is not allowed in a Lock State)
I have tried XiaoMiTool V2 and it straight up didn't work.
Let me look up Qfil.
Click to expand...
Click to collapse
It seems you are trying MiFlash tool in fastboot mode but while your device is locked fastboot mode won't work, you have to open the back cover and try test point method to send device to EDL (Emergency Download mode).
SubwayChamp said:
It seems you are trying MiFlash tool in fastboot mode but while your device is locked fastboot mode won't work, you have to open the back cover and try test point method to send device to EDL (Emergency Download mode).
Click to expand...
Click to collapse
Thank you very much, for still staying put.
I just did.
I downloaded the official Mi A2 fast boot ROM from https://bigota.d.miui.com/V11.0.14.....QDIMIXM_20200928.0000.00_10.0_62d0264480.tgz
I entered EDL mode following this guide: youtube.com/watch?v=34Zoevm-Wxc
I flashed it successfully but my phone is still stuck in the boot loop
Micklo said:
Thank you very much, for still staying put.
I just did.
I downloaded the official Mi A2 fast boot ROM from https://bigota.d.miui.com/V11.0.14.....QDIMIXM_20200928.0000.00_10.0_62d0264480.tgz
I entered EDL mode following this guide: youtube.com/watch?v=34Zoevm-Wxc
I flashed it successfully but my phone is still stuck in the boot loop
Click to expand...
Click to collapse
Use this link, there are other ways to unbrick it https://youtu.be/-B_YseC5kLk
Download from the official site linked in the video guide the recovery stock ROM, you can put it in some place in your PC and use the ADB sideload option through recovery to flash it or also you can use an USB OTG. Additionally try with other firmware, taking care to not downgrading it.
And if this doesn't work you should use other Windows version, some users report better results on Windows 7. And keep trying to switch slot.
Edit: before all try if this command work on fastboot mode: https://forum.xda-developers.com/showpost.php?p=75963934&postcount=25