Related
i can only access the white screen when i chose bootloader>recovery i get the /!\ sign.
i installed the USB driver and i was able to use only the "fastboot" commends. adb commend didn't work. when i type fastboot devices i get the serial no. of the device.
when i use the adb devices commend i get: "List of devices attached" and an empty line.
is it possible to fix this phone? thanx in advance.
Asilns said:
i can only access the white screen when i chose bootloader>recovery i get the /!\ sign.
i installed the USB driver and i was able to use only the "fastboot" commends. adb commend didn't work. when i type fastboot devices i get the serial no. of the device.
when i use the adb devices commend i get: "List of devices attached" and an empty line.
is it possible to fix this phone? thanx in advance.
Click to expand...
Click to collapse
adb only works within android since it's a debugger if I'm not mistaken. Try using fastboot to flash the system images of the stock rom back to their respective partitions. (ie. fastboot flash system system.img; fastboot flash boot boot.img; etc.)
You must be unlocked for that to work however.
problem solved
after almost 10 hours of research the solution was really easy.
1.download "recovery-RA-nexus-v1.6.2.img" and fastboot it using this commend:
fastboot-windows flash recovery recovery-RA-nexus-v1.6.2.img
2.flash a rom from SD card and everything should work fine
Hi guys, I have a problem.
I want to flash my N1 with the Cyanogenmod, but I have a problem with Bootloader unlocking. I do exactly what here is written (in the N1 guide from wiki.cyanogenmod), but when I open CMD (win XP) and write "fastboot oem unlock", it just doesn't works, but "adb devices" works and shows my phone. What can I do ? Any ideas ?
You need to boot into bootloader to work with fastboot. And if "adb devices" shows your phone - you obviously didn't boot.
adb reboot bootloader
Click to expand...
Click to collapse
Also, for a more comprehensive guide, please read the Wiki.
Code:
C:\fastboot>fastboot oem unlock
'fastboot' is not recognized as a
operable program or batch file.
This is what it shows in bootloader mode.
P.S. I have already re-installed my drivers. I have to notice that when I try to reinstall the drivers (in fastboot mode), they always auto-install themselves and when I try to update them, they say that there isn't newer version.
Fastboot executable isn't in the same directory as ADB executable, and isn't in the path you're executing it from (which is C:\fastboot).
Check, what is the actual executable you're trying to run, and if you have one. It might be called fastboot-windows.exe, if you didn't get it from downloading the Android SDK.
There is a executable file named "fastboot-windows.exe", but when I try to run it, it just open and close for 1 second. Any ideas ?
I thought the message would be clear by now... Oh well.
Open command prompt.
Run:
fastboot-windows oem unlock
Click to expand...
Click to collapse
I think It's done but my computer shows this message (see attached) 5 mins and I don't know it's ready or not ? Could I turn on the phone ? (Sry for the easy questions but I'm a real noob, because that's my 1st Android phone.)
The "too many links" message doesn't look good.
Reboot your computer.
Reboot the phone.
Use different USB port in your computer.
Ok well if you want my input try "fastboot devices" this should return your S/N (starting with "HT") if it gives you the same error then I would reinstall the SDK.
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
tjpearson said:
I've been struggling for a week with this.
Trying to unlock the bootloader but whenever I get to the stage of using command prompt I get this message;
'fastboot' is not recognized as an internal or external command,
operable program or batch file
The PC just will not recognise the phone when in fastboot mode although it does when not.
Windows 7
Android 4.3
HTC Sense Version 5.5
Software number 3.62.401.1
HTC SDK API Level 5.65
USB Debugging ticked
Fast boot deticked
HTC cable used
Latest drivers installed
Any help would be appreciated, the only previous experince I have is rooting a Galaxy note and tablet with no trouble whatsoever.
tj
Click to expand...
Click to collapse
Do you have fastboot.exe on your computer? It looks like CMD isn't finding fastboot.exe 1-because you don't have it 2- because you have not started your cmd prompt from your fastboot.exe folder
can you post a screenshot of your cmd prompt when you get this error?
ADB Installer
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
tjpearson said:
Installed ADB Installer and now been able to copy and been able to submit my token.
Recieved email reply with unlock code and it came as a VLC icon, still put this onto my phone but now get message 'unable to open bin file'
Got one step further but now unable to open file.
Below is the message I get:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\tjpearson>fastboot flash unlocktoken Unlock_code.bin
error: cannot open 'Unlock_code.bin'
C:\Users\tjpearson>
Your help is very much appreciated but my wife fails to understand my pannick and she thinks out tea is more important so may not get back to you straight away.
tj
Click to expand...
Click to collapse
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
mb_guy said:
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Originally Posted by mb_guy
Think you need to open the command prompt in the adb folder, and also have the unlock_code.bin in that same folder.
Click to expand...
Click to collapse
OK, I'll try this tomorrow, thanks for the help.
Click to expand...
Click to collapse
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
alray said:
Like mb_guy said, you MUST place the bin file in the same folder where adb and fastboot are. Every time you want to flash a file to your phone it must be in that folder, otherwise fastboot won't find it and it will output you that error (can't open file). That rule apply to recovery, unlock code, rom, kernel, ruu, firmware etc etc.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
tjpearson said:
Thanks for the help because at least I've now been able to unlock bootloader.
My problem now is 'fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img' command line and yet again I'm getting error unable to open as below;
C:\Users\tjpearson>fastboot flash recovery openrecovery-twrp-2.6.3.0-m7.img
error: cannot open 'openrecovery-twrp-2.6.3.0-m7.img'
Even placing zip on root of phone and in adb folder still no joy.
tj
Click to expand...
Click to collapse
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
alray said:
''error: cannot open'' is caused because fastboot don't find the file. Is the recovery file you are trying to flash is named exactly <openrecovery-twrp-2.6.3.0-m7.img> ?
Btw I'll recommend you to flash twrp 2.6.3.3 not 2.6.3.0 as you could have issur flashing newer 4.4 rom
Code:
fastboot flash recovery <name_of_file.img>
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
tjpearson said:
Yes, named exactly the same.
It's driving me mad, if the bootloader is now unlocked is there an easier way to flash twrp and then root.
Whats the best way to check adb is actually communicating with the phone
tj
Click to expand...
Click to collapse
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
clsA said:
Do you have a Sprint phone ? and can you post a screen shot of your adb / fastboot folder containing the files or at least post your results for dir
open command prompt from your adb / fastboot folder (shift+right click - command prompt here)
type
adb devices
your device SN will be here
type
adb reboot bootloader
you should be in fastboot usb
type
fastboot devices
again your serial no should be here
type dir
you should see the contains of the folder your in
now
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
if error change the twrp name to match the one in the dir command above
Click to expand...
Click to collapse
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
tjpearson said:
I seem to have a problem adb detecting the connected phone, I'll unistall and start again and if I can then get back to you later I'd appreciate it very much.
The phone is UK on 02 Android 4.4 HTC Sense version 5.5
tj
Click to expand...
Click to collapse
can you check my guide under faq #2, if that solves it
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
tjpearson said:
Well, think I'll give up with rooting my HTC One, I have never had so much trouble routing a divice as this. My bootloader is now unlocked and that's about as far as I get.
My phone seems to have been detected once through adb that then allowed me to run unlock token but everything else just fails.
In one last attempt I've attached image of ADB folder and below is result from command line.
It must be my age because evertybing seems so complex nowadays
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
target reported max download size of 1526722560 bytes
error: cannot load 'openrecovery-twrp-2.6.3.3-m7.img': No error
C:\Android>
Click to expand...
Click to collapse
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
d -darrrrr
nkk71 said:
cannot load = MyFileNameIsWrong
and from the screenshot you posted the filename is: openrecovery-twrp-2.6.3.3-m7.img.img <- yes, double extension, next time do a "dir" in command prompt to see your filenames, not in Windows Explorer.
Click to expand...
Click to collapse
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
tjpearson said:
I love you nkk71, I really can't tell you how much I love you but I do !!!!! :victory:
Did what you said and fumbled through flashing twrp and then adding superuser after to the phones root, did recovery again and installed superuser via twrp and bingo, rooted and confirmed.
Been struggling 2 weeks with this and non stop all weekend, my wife wants a divorce but I don't care cos I'M ROOTED !!
Thanks so much for all the help, nice one :good:
tj
Click to expand...
Click to collapse
Lol
Now that the phone is good, go spend some time with your better half!!!
No guides on xda, on "how to return my marriage to stock"
Put the phone on the charger or something, and spend time with your significant other.
Sent from my HTC One using Tapatalk
One last question
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
tjpearson said:
nkk71,
Can I uninstall Superuser now and install SuperSU instead cos I've already purchased that when had the Note rooted or will it cause me more time away from the mrs with issues.
tj
Click to expand...
Click to collapse
Shouldn't be a problem, use the flashable zip from the thread: http://forum.xda-developers.com/showthread.php?t=1538053
Yeah , sorted.
Thanks again for all your help.
tj
Someone please.help...
tott2003 said:
Someone please.help...
Click to expand...
Click to collapse
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use .\ before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with .\ in the beginning.
Rashad83 said:
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use . before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with . in the beginning.
Click to expand...
Click to collapse
Cheers mate ?
Rashad83 said:
1. Connect the USB cable from the side of the phone and make sure that developer mode and USB debugging is activated.
2. Connect your phone to the PC, make sure it's connected in data transfer mode.
3. Go to adb.exe and fastboot.exe folder, hold shift and right click to open CMD or PowerShell from there. If you open PowerShell use .\ before the command, if you are using CMD just type the command without it.
4. Type in CMD: "adb devices" without parenthesis, you should see your device serial number.
5. Type then in CMD: "adb reboot bootloader" without parenthesis, you will go to fastboot mode or the "Green Start Screen" after the phone boots.
6. Type "fastboot devices" you should see you device serial number. which means you can run fastboot commands without any issues.
P.S I am using PowerShell instead of CMD, so the pictures show the commands with .\ in the beginning.
Click to expand...
Click to collapse
HOLY. ****ING. ****.
I have spent the past two days trying to figure this out. Not *one* other person on the internet, so much as I have seen, has mentioned using the side port. Seriously, you just made my day. Thank you so much! :good:
Created a new topic, disregard
When I open PowerShell and run the command "fastboot devices" my phone isn't getting detected. My phone is connected to my PC, I've installed platform tools & adb as well as the correct ROM. I'm pretty new to rooting so I'm not sure what's going on. I don't have a SIM Card so that might be the issue, but I'm trying to find a root guide that doesn't require sim.
What I've installed;
Latest USB Driver (MTP USB Device)
Latest ADB/Fastboot from android.com/studio/releases/platform-tools
Installed Fastboot ROM MIUI V13.0.6.0.SKDMIXM Stable from https://xiaomirom.com/en/rom/xiaomi.../#download-xiaomi-11t-pro-stable-fastboot-rom
Device Specs:
- MIUI Global 13.0.6 Stable (SKDMIXM)
- Android ver. 12 SKQ1.211006.001
Following this guide to root and have been following step by step up to 3:12:
WhalePC said:
When I open PowerShell and run the command "fastboot devices" my phone isn't getting detected. My phone is connected to my PC, I've installed platform tools & adb as well as the correct ROM. Not sure what's going on.
Following this guide to root and have been following step by step up to 3:12:
Click to expand...
Click to collapse
Maybe you summarized the command in your statement but with power shell the command is "./fastboot devices"
Do you see the device icon in the taskbar?
NOSS8 said:
Maybe you summarized the command in your statement but with power shell the command is "./fastboot devices"
Do you see the device icon in the taskbar?
Click to expand...
Click to collapse
Yeah i see the icon on my taskbar. Just tried running it via "./fastboot devices" and no devices show up. I haven't unlocked the bootloader yet (haven't enabled Mi Unlock status) yet is that maybe the issue? If so, is there a way to root without the need of a sim card?
WhalePC said:
Yeah i see the icon on my taskbar. Just tried running it via "./fastboot devices" and no devices show up. I haven't unlocked the bootloader yet (haven't enabled Mi Unlock status) yet is that maybe the issue? If so, is there a way to root without the need of a sim card?
Click to expand...
Click to collapse
You generally shouldn't need a SIM card to use ADB or fastboot commands.
Are you sure you have the correct drivers installed? Does the device appear under adb devices when in Android?
V0latyle said:
You generally shouldn't need a SIM card to use ADB or fastboot commands.
Are you sure you have the correct drivers installed? Does the device appear under adb devices when in Android?
Click to expand...
Click to collapse
How do i check that I have the correct drivers installed? I ran adb devices and it showed my device 3d37ace2 device was connected.
EDIT: Here's how I enter into fastboot and excute commands;
- Plug in phone into PC and wait for icon to show up on taskbar
- Open Powershell in platform-tools folder
- Power off phone and enter fastboot (hold down power button+vol down)
- Once Fastboot text shows up on my phone I run the command "fastboot devices" in powershell
WhalePC said:
How do i check that I have the correct drivers installed? I ran adb devices and it showed my device 3d37ace2 device was connected.
EDIT: Here's how I enter into fastboot and excute commands;
- Plug in phone into PC and wait for icon to show up on taskbar
- Open Powershell in platform-tools folder
- Power off phone and enter fastboot (hold down power button+vol down)
- Once Fastboot text shows up on my phone I run the command "fastboot devices" in powershell
Click to expand...
Click to collapse
This looks like a good place to start. It's possible you have a generic ADB driver installed and may need a device specific one.
V0latyle said:
This looks like a good place to start. It's possible you have a generic ADB driver installed and may need a device specific one.
Click to expand...
Click to collapse
Just reinstalled the latest ADB/Fastboot from https://androidmtk.com/download-15-seconds-adb-installer and still have the same issue. I also installed Xiaomi AB/Fastboot Tools to check if it can identify my device and it does.
Running adb shell in cmd prompt outputs:
Code:
C:\Users\Whale>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
vili:/ $
But once it's in fastboot it responds with:
Code:
C:\Users\Whale>adb shell
adb.exe: no devices/emulators found
Same for Powershell:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
3d37ace2 device
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
Currently, when my phone is turned on (not in fastboot), my device is detected as 3d37ace2 (codename: vili), but as soon as it goes to Fastboot, it no longer can detect the device.
WhalePC said:
Just reinstalled the latest ADB/Fastboot from https://androidmtk.com/download-15-seconds-adb-installer and still have the same issue. I also installed Xiaomi AB/Fastboot Tools to check if it can identify my device and it does.
Running adb shell in cmd prompt outputs:
Code:
C:\Users\Whale>adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
vili:/ $
But once it's in fastboot it responds with:
Code:
C:\Users\Whale>adb shell
adb.exe: no devices/emulators found
Same for Powershell:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
3d37ace2 device
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> adb devices
List of devices attached
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot devices
PS C:\Users\Whale\Downloads\11t pro\platform-tools> ./fastboot devices
Currently, when my phone is turned on (not in fastboot), my device is detected as 3d37ace2 (codename: vili), but as soon as it goes to Fastboot, it no longer can detect the device.
Click to expand...
Click to collapse
ADB commands won't work in fastboot and vice versa. When your device is in Android or recovery, you can use ADB commands, but when it's in bootloader mode, you have to use fastboot commands. ADB shell won't do anything for you in fastboot because there's no kernel running, much less a shell.
Since your device isn't appearing under fastboot devices it's most likely a driver issue. You need two separate drivers; the ADB driver is not device specific, but the bootloader driver is.
Case in point: This is what appears when my Pixel 5 is connected while booted into Android:
When I reboot to bootloader, this is what I see:
So, this is what I suggest:
Reboot to bootloader, connect to your PC, and look at Device Manager to see if anything comes up as unrecognized. Make sure it's the right device by unplugging the USB cable; it should disappear. You'll then need to update the driver, and point it to the the Xiaomi driver folder.
V0latyle said:
ADB commands won't work in fastboot and vice versa. When your device is in Android or recovery, you can use ADB commands, but when it's in bootloader mode, you have to use fastboot commands. ADB shell won't do anything for you in fastboot because there's no kernel running, much less a shell.
Since your device isn't appearing under fastboot devices it's most likely a driver issue. You need two separate drivers; the ADB driver is not device specific, but the bootloader driver is.
Case in point: This is what appears when my Pixel 5 is connected while booted into Android:
View attachment 5731657
When I reboot to bootloader, this is what I see:
View attachment 5731663
So, this is what I suggest:
Reboot to bootloader, connect to your PC, and look at Device Manager to see if anything comes up as unrecognized. Make sure it's the right device by unplugging the USB cable; it should disappear. You'll then need to update the driver, and point it to the the Xiaomi driver folder.
Click to expand...
Click to collapse
Thanks fam, was able to solve it by installing a different driver from this video:
.
Now I'm getting an error:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot flash boot magisk_patched.img
Sending 'boot_a' (196608 KB) OKAY [ 4.210s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
which I assume means I need to unlock my bootloader via Mi Unlock status?
WhalePC said:
Thanks fam, was able to solve it by installing a different driver from this video:
.
Now I'm getting an error:
Code:
PS C:\Users\Whale\Downloads\11t pro\platform-tools> fastboot flash boot magisk_patched.img
Sending 'boot_a' (196608 KB) OKAY [ 4.210s]
Writing 'boot_a' FAILED (remote: 'Flashing is not allowed in Lock State')
fastboot: error: Command failed
which I assume means I need to unlock my bootloader via Mi Unlock status?
Click to expand...
Click to collapse
Yep. I don't know how it works on Xiaomi devices but try fastboot flashing unlock
Unlocking your bootloader will wipe data, so if you need to back anything up, do that first.
Enter in FASTBOOT MODE: press Power+Volume down button for 4-5 sec in the same time,the phone reboot, at the vibration release the power button.Now plug in the phone to the PC.
Having the bootloader locked does not prevent seeing the device in Fastboot mode.(***Not useful at the moment)
To root you must first unlock the bootloader.(***your bootloader is locked)(FAILED (remote: 'Flashing is not allowed in Lock State')
Unlock the bootloader
You must have a Xiaomi account and a valid sim.
Procedure:
https://new.c.mi.com/global/post/101245
https://en.miui.com/unlock/index.html
Why look for tutorials on You tube'Sometimes good, sometimes fake) while on XDA(Always good )in the How to section of your device these tutorials exist and specify that the bootloader must be unlocked.
https://forum.xda-developers.com/t/root-xiaomi-11t-pro.4441213/
https://forum.xda-developers.com/t/...structions-for-xiaomi-11t-pro-global.4362515/
check debugging via USB option.
WhalePC said:
When I open PowerShell and run the command "fastboot devices" my phone isn't getting detected. My phone is connected to my PC, I've installed platform tools & adb as well as the correct ROM. I'm pretty new to rooting so I'm not sure what's going on. I don't have a SIM Card so that might be the issue, but I'm trying to find a root guide that doesn't require sim.
What I've installed;
Latest USB Driver (MTP USB Device)
Latest ADB/Fastboot from android.com/studio/releases/platform-tools
Installed Fastboot ROM MIUI V13.0.6.0.SKDMIXM Stable from https://xiaomirom.com/en/rom/xiaomi.../#download-xiaomi-11t-pro-stable-fastboot-rom
Device Specs:
- MIUI Global 13.0.6 Stable (SKDMIXM)
- Android ver. 12 SKQ1.211006.001
Following this guide to root and have been following step by step up to 3:12:
Click to expand...
Click to collapse
You will need to manually configure fastboot drivers.