I was attempting to flash lineageOS from https://forum.xda-developers.com/mi-pad/development/lineageos-16-0-07-12-2019-shield-blobs-t4015965. Keep in mind my firmware knowledge was less than ideal so when I got to step 5 which was "5) execute command: fastboot flash tos your path to tos.img", I copied it word for word into fastboot and obviously it didn't do anything (I didn't understand the "your path to" portion was supposed to be the file directory then) I then searched the internet trying to look for a solution, thinking I had missed a step. I came across this article https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/ and got up to step five where I executed the "fastboot oem unlock" command and unlocked my mipad's bootloader I couldn't understand the next few steps so I gave up on this set of instructions. When I reattempted to use fastboot after figuring out what "your path to" meant on the first set of instructions, my device couldn't be detected through executing "fastboot devices", my computer's device manager, or MiFlash even though all ADB drivers were initially installed and I even installed it again just to be safe. How do I get my computer to detect my mipad again? Note: my mipad is now rebooting straight to fastboot
TLDR: unlocked mipad 1 bootloader using fastboot, mipad no longer detected by computer and only reboots to fastboot. How to get mipad detected by computer
Related
I recently purchased 2 Asus TF103C stocked with Android 4.4.2 and running on an Intel processor. I'd like to load a custom OS/ ROM to them for work however I have not had any success finding a process that allows me to do so. I have managed to root the tablet successfully but that is the extent of my accomplishment to date. I understand that this is a fairly new device and not much has been uncovered yet to achieve this task. Asus is also hesistant to release an unlocked bootlooder update. If anyone is aware of a process whether through adb or the likes please raise your voice to help the community out on this one.
Vibestarter said:
I recently purchased 2 Asus TF103C stocked with Android 4.4.2 and running on an Intel processor. I'd like to load a custom OS/ ROM to them for work however I have not had any success finding a process that allows me to do so. I have managed to root the tablet successfully but that is the extent of my accomplishment to date. I understand that this is a fairly new device and not much has been uncovered yet to achieve this task. Asus is also hesistant to release an unlocked bootlooder update. If anyone is aware of a process whether through adb or the likes please raise your voice to help the community out on this one.
Click to expand...
Click to collapse
Before following steps bellow mentioned don't forget to install USB and ADB drivers
Also download minimal ADB and Fastboot tools ( for links use google search its easily available)
Configure your compute for fastboot Enable USB debugging on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode
$*adb*reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing*
fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>",
fastboot is not configured properly on your machine.
If you see "no permissionsfastboot", try running
fastboot as root.
From the same terminal, type the following command to get info of the bootloader:
fastboot oem-info
To unlock type
fastboot oem unlock
And press enter
May this will unlock your boot loader in general
Press Thanks Button If You like My Work & Posts?
fastboot oem unlock Failed
The-Immortal said:
Before following steps bellow mentioned don't forget to install USB and ADB drivers
Also download minimal ADB and Fastboot tools ( for links use google search its easily available)
Configure your compute for fastboot Enable USB debugging on the device.
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode
$*adb*reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing*
fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>",
fastboot is not configured properly on your machine.
If you see "no permissionsfastboot", try running
fastboot as root.
From the same terminal, type the following command to get info of the bootloader:
fastboot oem-info
To unlock type
fastboot oem unlock
And press enter
May this will unlock your boot loader in general
Press Thanks Button If You like My Work & Posts?
Click to expand...
Click to collapse
Hello, I tried your command suggestions to unlock the bootloader and they failed. The command 'fastboot oem-info' does not return anything and 'fastboot oem unlock' returns RESULT: FAIL (unkown OEM command) on the tablet and in the cmd window. Thanks for the suggested attempt nonetheless.
Still having this problem
fastboot oem unlock fails on the TF103C and it says RESULT:FAIL(unknown OEM command). It would be great if Asus could release a tf103c_unlock.apk utility like they have for other Asus tablets (for instance the TF701T has tf701_unlock.apk which works).
Asus, please help!
I bricked my opx I was able to bring it to life but the ****ty recovery doesn't let me flash anything so I am stuck no OS and boot loader locked and my computer isn't recognizing the dam thing I have installed SDK tools and google USB drivers but for some reason I am not able to get the Dan thing to connect right when I try via adb sideload it starts then the phone says fail...... Please help I am love this device and brand but I am getting really mad I am about a week in to trying to fix this but no luck I am using windows 10 also
Sorry to say, but you gotta follow this thread.
[GUIDE] Mega Unbrick Guide for A Hard Bricked OnePlus X
Since you may ignore the other thread you started or it may get deleted I'll copypasta here:
We can try to unlock the bootloader as it is now, but that doesn't usually work unless you checked "OEM Bootloader Unlock" in the system settings before the device was bricked. Hindsight is 20/20 but as a word of advice for the future, never ever mess with a device unless you know the bootloader is unlocked or have made it possible to unlock it later without the OS. It also doesn't void the warranty on OnePlus devices to do so.
So first things first, the recovery will normally only flash the stock ROM as provided by OnePlus. You can download that file from here: http://downloads.oneplus.net/2016-04...xygenOS_2.2.1/. For future reference, when the bootloader on a device is locked the bootloader will not boot any software that isn't complete stock. If you try and change the OS or Recovery and it's not stock, the bootloader will not load it. This goes for any Android device.
If ADB sideload is working for you but hasn't been installing on the device (as-in, it sends the file but the device fails to install it) then you should be able to just sideload the zip file. It'll be slow though since it's about 780megs. If it doesn't send it then you can try using the ADB "push" command which is like copy and paste. You "push" the file from your computer to a folder on the device (you can see what folders are available using "adb shell" and then navigating with CD "change directory" and LS "list". If you can't find the sdcard you may have to mount it). Once again, it'll push slowly but once it does you should be able to install it from the internal memory.
If that works and it boots, go to Settings -> About Phone and tap the Build Number until it says you've enabled developer settings. Go to Settings -> Development and turn on "OEM Unlocking". Power the phone down. Hold the Power key and Volume Down until it shows the OnePlus logo and "Fastboot". I believe if you have the Android SDK you have the Fastboot program (it's commandline like ADB). Open CMD or Powershell and as long as it's the only device plugged into the computer you should be able to simply type "Fastboot oem unlock" and it will unlock the bootloader. Once again, it doesn't void your warranty.
After 2-3 hours of work I finally managed to unlock my Honor5x, but my phone seems to **** up on these few steps of the xda guide:
Step 9
Boot back into the bootloader by typing the following
"adb reboot bootloader"
Step 10
Flash the recovery with the following command:
"fastboot flash recovery twrp_kiwi.img"
Step 11
Once it finishes type the following
"fastboot reboot"
My phone gets recognized by adb generally, but whenever I use the command adb reboot bootloader, immediately after my phone doesn't get recognized by fastboot, so the following steps don't work. The phone is in bootloader mode however, and it DOES say that it's unlocked.
Things I've tried:
Using different USB ports
Using different USB s
Unplugging and replugging while my phone is in fastboot
Installing TWRP from the TWRP manager app (It gives me an error with every single version that's available. The error message is "Something went wrong. Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occured. Would you like to attempt rebooting to recovery now?" Pressing the button reboot now doesn't do anything.
Re-enabled developer mode and made sure that usb debug and oem unlock are both enabled.
Computer is: Win 10 64 bit
Wtf do I do?
Araschon said:
After 2-3 hours of work I finally managed to unlock my Honor5x, but my phone seems to **** up on these few steps of the xda guide:
Step 9
Boot back into the bootloader by typing the following
"adb reboot bootloader"
Step 10
Flash the recovery with the following command:
"fastboot flash recovery twrp_kiwi.img"
Step 11
Once it finishes type the following
"fastboot reboot"
My phone gets recognized by adb generally, but whenever I use the command adb reboot bootloader, immediately after my phone doesn't get recognized by adb anymore, so the following steps don't work. The phone is in bootloader mode however, and it DOES say that it's unlocked.
Things I've tried:
Using different USB ports
Using different USB s
Unplugging and replugging while my phone is in fastboot
Installing TWRP from the TWRP manager app (It gives me an error with every single version that's available. The error message is "Something went wrong. Flashing recovery was unsuccessful. Either you already have this recovery installed or another error has occured. Would you like to attempt rebooting to recovery now?" Pressing the button reboot now doesn't do anything.
Re-enabled developer mode and made sure that usb debug and oem unlock are both enabled.
Computer is: Win 10 64 bit
Wtf do I do?
Click to expand...
Click to collapse
Install the Huawei fastboot drivers
Sent from my SM-N920T using Tapatalk
I have HiSuite, which seems to be the USB drivers for huawei, but are you talking about the ones from team android? I can't post the link because this is a new account.
So I just purchased this phone and am trying to follow the instructions on the Sony site. The rooting status in my service menu says my devices should be able to be unlocked.
Device is on android 13 on latest update, OEM unlock and USB debugging are both enabled.
I downloaded the usb drivers and the platform tools from the Sony site.
I opened a command prompt in the platform tools folder and when I run fastboot devices I get a response
When I run the command with my unlock code, I get the error
FAILED (remote: Command not supported in default implementation)
I tried to go to device manager to update the drivers, however when I do that it says the best driver is already installed.
I read in another thread to try to boot into the bootloader rather than fastboot. When I select reboot to bootloader the device seemingly shuts off.
EDIT: OK, I'm dumb and was in fastbootd mode rather than fastboot. I've now entered fastboot correctly (holding volume up while I plug it in, getting a black screen and a blue LED), updated the drivers correctly, and am now getting the error that the device is already unlocked. Now I guess I just need to verify that it is indeed unlocked, anyone have some advice on that?
EDIT 2: OK it seems to be going through the unlock process despite that error rather than the expected confirmation. After a few reboots it is now giving me the setup process again so I hope it worked. Leaving thread up for others who have the same issue to stumble accross.
I'm at a total loss here...
phone has unlocking and USB debugging toggled on.
phone is not a US phone and unlocking is allowed.
phone goes into fastboot mode (by turning on while holding volume)
"fastboot devices" command returns my phone is in fastboot and connected
"fastboot oem unlock 0xPASSWORD" returns FAILED (remote: 'Command not supported in default implementation')
and fastboot: error: Command failed
I have no idea what to do or try from here.
If I try to flash an image i get:
FAILED (remote: 'Download is not allowed on locked devices')
so, defiantly still locked out of the bootloader
Try below steps
1. Ensure you have platform tools 33.x , 34 has issues.
2. Try to reboot to bootloader from pc.
adb reboot bootloader
3. Try running
fastboot flashing unlock unlockcode
Try it :
fastboot oem unlock
or
fastboot flashing unlock
SOLVED I am so happy. I'm on day 3 of trying to get the phone to bootload.
there is definitely a difference between going into fastboot through the phone itself and through adb commands on PC.
fastboot through the phone shows the drop down menu and no blue light illuminated on phone.
fastboot through adb phone is black screen with a blue light on right corner on the phone.
the windows drivers behave differently between the two. I am running windows 10. phone model XQ-CT72
steps that solved the issue. For anyone in the future.
I downloaded and used platform tools version 33.0.3 NOT version 34.
"adb reboot bootloader" used from windows PC
opened windows device manager found my "discovered device" and forced it to use the SONY driver downloaded from sonys website. It would not detect it on its own, or even use the SONY driver without me telling it to specifically. device manager> "andorid" > properties > update driver > browse computer for driver > installed sony driver
everything worked following these instructions here https://www.droidwin.com/unlock-bootloader-and-root-sony-xperia-1-iv/
alexriethmeier said:
There is definitely a difference between going into ...
Click to expand...
Click to collapse
fastboot, part of the android bootloader, abl
fastbootd, part of recovery
I had same issue and same solution fixed it what you showed and did. I was terrified, after investing so much money on this phone and not getting it unlocked.
You won't need to go through such hassle if you just use Linux VM (a Ubuntu distro will do). The driver works out of the box.