I got a great deal on a used nexus and got everything but the USB cable. Is it possible for me to unlock my boot loader before I buy a cable for it?
ahronzombi said:
I got a great deal on a used nexus and got everything but the USB cable. Is it possible for me to unlock my boot loader before I buy a cable for it?
Click to expand...
Click to collapse
I'm pretty sure you can't.
However, I bought one of these for the office and it works fine:
http://www.amazon.com/BlackBerry-Cable-Micro-1-0m-Black/dp/B001QATRCA/
You need to put the ROM Zip to your SD card so you are pretty stuck. Dunno if you can use Bluetooth tho'. Unless you live far off aome electronic store like Radioshack, a cable shouldn't rip our wallet clean for cash.
But in reality you don't need to be hooked up on the cable when rooting and backing up your current ROM for that matter.
I'm also pretty sure this is impossible. You need to run command prompt commands, etc. a computer just has to be available - if there is a way though, I would love to be educated.
A micro USB cable shouldn't cost that much I guess..
Recovery and rom can be flashed from sd so he would only need to pull his sd and transfer the recovery and rom to it then put it back in his phone. The root could be done from an su terminal but of course you cant use it till you root, not sure how you get around that one. I dont use rom manager but if I recall rightly you have to be rooted to use it?
You have to run fastboot oem unlock using a USB cable to root, you need wifi to transfer things to the SD card using 'Discovery' which is a pain because the UI doesn't work right yet with the Nexus or 2.1.
wesbalmer said:
You have to run fastboot oem unlock using a USB cable to root, you need wifi to transfer things to the SD card using 'Discovery' which is a pain because the UI doesn't work right yet with the Nexus or 2.1.
Click to expand...
Click to collapse
Yeah, I think there is no way around the oem unlock without a cable.
As for transferring files over Wifi, check out this app:
http://www.cyrket.com/p/android/nextapp.websharing/
Pretty awesome.
http://www.monoprice.com/products/p...=10303&cs_id=1030307&p_id=5457&seq=1&format=2
3ft USB cable $2.90 shipped.
these are what I use, they work great.
I use monoprice for anything that involves a cable... HDMI, usb cables, even my car charger. They have one for $1.16 that pulls out 1000 instead of 500 like most of the cheap ones out there.
Again, can't oem unlock without USB
but you could always download the recovery straight to your phone, or just email it to yourself.
ahronzombi said:
I got a great deal on a used nexus and got everything but the USB cable. Is it possible for me to unlock my boot loader before I buy a cable for it?
Click to expand...
Click to collapse
As others have indicated, there's nothing special about the USB cable used by the N1 - It's a standard micro USB. I use my blackberry's micro USB as a backup cable at work.
Think about the other possibilities a USB cable gets you: The ability to charge your N1 using your computer!
what you can do is some of the newest computers/laptops carry a micro adapter like this you can take out your sd card from your phone and place it here and follow the process for rooting im not sure if this would work but u can give it a try
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You have to have fastboot CLI access to root, yes? I'm pretty sure this has been said before, but I'm 95% certain you MUST be connected via USB to root. I had to do this for both my Tilt and my Fuze, and I've toyed around with doing it on the N1 but haven't broken down and done it yet (don't want to lose the OTA updates lol), but it always required android sdk + phone in fastboot mode
MaximReapage said:
You have to have fastboot CLI access to root, yes? I'm pretty sure this has been said before, but I'm 95% certain you MUST be connected via USB to root. I had to do this for both my Tilt and my Fuze, and I've toyed around with doing it on the N1 but haven't broken down and done it yet (don't want to lose the OTA updates lol), but it always required android sdk + phone in fastboot mode
Click to expand...
Click to collapse
Right - Need the USB cable to perform the initial "fastboot oem unlock" to unlock the bootloader so that custom roms and/or a superboot img can be flashed.
Related
can someone help? i want to update tot he 4.0 but i need to relock my bootloader to have it work. i dont know how since im pretty noob at this
Provided u still have the folder u used to unlock, boot ur phone into fastboot (vol dn + power) connect it to ur pc with a USB cable, then from the command prompt in the folder where fastboot.exe is, type: "fastboot oem lock" without the quotations. Good luck!
Sent from my HTC Raider X710e using xda premium
ah damn i dont think istill have it
is there another way?
oh nvm i think i do i have it i just need to look for it
thank u so much haha im so happy right now
i have one more question when i did it it said this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so idk if it worked
i tired to update and it still didnt work
anyone have a copy of this fastboot.exe file..
i dont seem to have it anymore.. need to relock also so i can install the file.
---------- Post added at 01:55 AM ---------- Previous post was at 01:27 AM ----------
an4564 said:
i have one more question when i did it it said this
so idk if it worked
i tired to update and it still didnt work
Click to expand...
Click to collapse
Mine just did the same thing...
---------- Post added at 02:01 AM ---------- Previous post was at 01:55 AM ----------
OK, so i went back in to try again, came up saying its locked..
lets see how it go's.
i tired it a few times idk if its gonna work
mine comes up saying locked now, but when i go to install it powers down and then go's into the bootloader.. hmmm
i still havent seen the update yet
i tired it a bunch of times and nothing ever comes up
you need to be more thorough with your explanation of what point you are at and what you are trying to achieve.
an4564, what device do you have, what network are you on, and what exactly are you attempting to achieve, what does "nothing ever comes up" mean to the rest of us who are not mind readers
If you get your bootloader locked just go get the RUU Download and install the ICS Update.Its simple and painless.The directions below.Credit goes to Pirate Ghost,WildChild,Chall80 for the easy directions and whomever else was involved for making this early update possible.All credit goes to them.Im not an any way taking credit but just passing along this info.Enjoy
Originally Posted by Chall80
Ok, so here we go....
First, go to this link and download the RUU(Rom Upgrade Utility) http://goo-inside.me/devs/pirateghost/vivid/RUU/RUU_HOLIDAY_ICS_35_S_CINGULAR_3.26.502.52.zip
Second, you need to use HTC Sync to sync any data that you want saved.
Third, you need to connect your device to your computer, and set it to "charge only". You need to make sure that you have "USB Debugging Enabled".
From the Home screen, press the Menu key.
Tap Settings.
Tap Applications.
Tap Development
Tap to check USB debugging.
Once you've enabled USB Debugging, and connected your device using the "charge only" setting, Double click the RUU file.
From that point on, it will prompt you for a couple things, but there are no options or choices to make. Its bulletproof.
THIS OPERATION WILL COMPLETELY WIPE YOUR ONBOARD DATA, AND RETURN YOUR PHONE TO "OUT OF BOX" CONDITION. It will have Android 4.0.3, and Sense 3.6
This is an AT&T release and does not void your warranty, unlock your bootloader, gain access to the root folder, or remove AT&T bloatware. This is perfectly legit for those who don't wish to mess with root. An RUU is the manufacturers method for upgrading phones.
I have screenshots, and just don't wanna mess with uploading them(too much of a pain). If you wanna see them, PM me and I'll email them to you.
This is painless and so worth it!!!
EDIT: This does not wipe your SD Card
i have the htc vivid for AT&T and am trying to get the ics update. i relocked my bootloader and typed in the *#*#682#*#* code and waited for the notification to come up but it never does. i have tired it multiple times
woodsytattooman said:
If you get your bootloader locked just go get the RUU Download and install the ICS Update.Its simple and painless.The directions below.Credit goes to Pirate Ghost,WildChild,Chall80 for the easy directions and whomever else was involved for making this early update possible.All credit goes to them.Im not an any way taking credit but just passing along this info.Enjoy
Originally Posted by Chall80
Ok, so here we go....
First, go to this link and download the RUU(Rom Upgrade Utility) http://goo-inside.me/devs/pirateghost/vivid/RUU/RUU_HOLIDAY_ICS_35_S_CINGULAR_3.26.502.52.zip
Second, you need to use HTC Sync to sync any data that you want saved.
Third, you need to connect your device to your computer, and set it to "charge only". You need to make sure that you have "USB Debugging Enabled".
From the Home screen, press the Menu key.
Tap Settings.
Tap Applications.
Tap Development
Tap to check USB debugging.
Once you've enabled USB Debugging, and connected your device using the "charge only" setting, Double click the RUU file.
From that point on, it will prompt you for a couple things, but there are no options or choices to make. Its bulletproof.
THIS OPERATION WILL COMPLETELY WIPE YOUR ONBOARD DATA, AND RETURN YOUR PHONE TO "OUT OF BOX" CONDITION. It will have Android 4.0.3, and Sense 3.6
This is an AT&T release and does not void your warranty, unlock your bootloader, gain access to the root folder, or remove AT&T bloatware. This is perfectly legit for those who don't wish to mess with root. An RUU is the manufacturers method for upgrading phones.
I have screenshots, and just don't wanna mess with uploading them(too much of a pain). If you wanna see them, PM me and I'll email them to you.
This is painless and so worth it!!!
EDIT: This does not wipe your SD Card
Click to expand...
Click to collapse
oh is this the update that was put out today?
an4564 said:
oh is this the update that was put out today?
Click to expand...
Click to collapse
No it is not. I don't know if there is a RUU for the newest ics.
davidcampbell said:
you need to be more thorough with your explanation of what point you are at and what you are trying to achieve.
Click to expand...
Click to collapse
i am trying to update my Velocity with the OTA ICS update, i relocked the bootloader, restarted the phone, initiated the install, it gets to the point of restarting and instead of starting the install Fastboot comes up..
Hey guys!
I swear I must be the only idiot out there who can't work out the Flashtool interface. I have rooted, installed CWM and readied my FTF file ready to flash. My problem is actually connecting the phone and getting the interface to recognize the Z.
When booting the program I plug the device in, it loads up and installs the ADB interface drivers and provides me with a prompt giving me a list of phones to choose from. The Z just isn't in there and I don't want to proceed by choosing another device 'by default'...
I have well and truely searched the hell out of this question with as many different queries as I could imagine to no avail. I have flashing experience and consider myself quite computer savvy but this has more then got me stumped!
Any suggestions?
Regards,
Josh
gibilator said:
Hey guys!
I swear I must be the only idiot out there who can't work out the Flashtool interface. I have rooted, installed CWM and readied my FTF file ready to flash. My problem is actually connecting the phone and getting the interface to recognize the Z.
When booting the program I plug the device in, it loads up and installs the ADB interface drivers and provides me with a prompt giving me a list of phones to choose from. The Z just isn't in there and I don't want to proceed by choosing another device 'by default'...
I have well and truely searched the hell out of this question with as many different queries as I could imagine to no avail. I have flashing experience and consider myself quite computer savvy but this has more then got me stumped!
Any suggestions?
Regards,
Josh
Click to expand...
Click to collapse
This is how I installed the driver for my XZ:
Install the driver first
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Select the XZ driver:
Now update the driver because your PC probably can't find the driver:
Now you have to select the driver yourself. So you have to pick it from the list
This the updated driver:
I hope that helps a little.
shadowboy23 said:
This is how I installed the driver for my XZ:
Click to expand...
Click to collapse
Thanks heaps!! I managed to get the drivers installed but the application still doesn't recognise the Z? any thoughts?
try changing the usb settings to mass storage instead of media mode or the other way round
gibilator said:
Thanks heaps!! I managed to get the drivers installed but the application still doesn't recognise the Z? any thoughts?
Click to expand...
Click to collapse
Is this what you are talking about?
To flash any stock ROM you don't need CWM. Flashtool is all I use to flash .ftf files
I download the ftf file I want and place it in the firmware folder:
I then start the flashtool app while the phone is unplugged, turned off and make sure it's in "Flashmode"
Once you click "Ok" this window should show up:
And then choose the ftf you placed in the folder. You should see this window:
And flashing will begin.
Just make sure you have full charge on your XZ before you do all this.
Wow, shadowboy23, you really went above and beyond with your assistance given here! You should really consider copying those posts over to the general thread and make a driver installation and flash tool guide (unles there is one...) But yeah, Kudos!:good::laugh::good:
Thanks!
I cannot believe that post shadowboy23 seriously thank you so much I can see the amount of time you have put in there! I myself haven't had any time to check the computer or even think about flashing my phone but will have another attempt this coming weekend and will defiantly bring you results (hopefully good news!)
Cheers again!!
Josh
I had a crack this afternoon and successfully got everything to the stage where your last step ends (on one of my 3 computers only!) and then the flashboot spits out an error message telling me the device drivers are not loaded. I will persist tomorrow afternoon when I have a fast internet connection and can download the latest version of flashboot (I have beta 4 I believe).
Incredibly frustrating process though!!
Josh
SUCCESS!!
Cheers shadowboy!! your new version fixed the issues I was having with the loader and it was all plug and play... but most of all thanks for letting me know to untick those boxes!! saved me the nightmare of having to reinstall everything
Cheers!!
Josh
Long story short, I have access to D/L mode and this is it. No recovery, no fastboot. Flashtools errors me out due to device model not matching. (My device model shows up as Android SDK built for x86). Also, ADB does not recognize device either.
With the methods being used to Root the G4's and Flex2's, is it possible to DD (Linux fun) system images from PC to device? I've been trying to comprehend Linux commands but am having some difficulties.
Tried this ="http://forum.xda-developers.com/showthread.php?t=2582142 . No luck. Ubuntu does not show partitions either. I'm sure my Flex is bricked, but I still have hope that some random method will pop up and I can get this baby rockin' again.
Thanks in advance!
pleckers87 said:
Long story short, I have access to D/L mode and this is it. No recovery, no fastboot. Flashtools errors me out due to device model not matching. (My device model shows up as Android SDK built for x86). Also, ADB does not recognize device either.
With the methods being used to Root the G4's and Flex2's, is it possible to DD (Linux fun) system images from PC to device? I've been trying to comprehend Linux commands but am having some difficulties.
Tried this ="http://forum.xda-developers.com/showthread.php?t=2582142 . No luck. Ubuntu does not show partitions either. I'm sure my Flex is bricked, but I still have hope that some random method will pop up and I can get this baby rockin' again.
Thanks in advance!
Click to expand...
Click to collapse
Tell details. What's your phone model?
Do you have download mode?
What's the error you getting?
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app
Model is D950. Originally had 4.4.x. I can enter download mode no problem. I don't have adb commands. When I type adb devices, it shows a blank space.
LG flash tools gives me a "device model different. Check device model". Mind you, tried flashing the stock TOT with the d950dll and also tried the generic dll that G2 users were using. I'll post a pic in a little bit of the error I get....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL][/IMG]
[/URL][/IMG]
pleckers87 said:
[/URL][/IMG]
Click to expand...
Click to collapse
Lols..
How did you bricked your set? I am just curious to find out..
What on screen If You normal start?
Try to connect your Phone with PC in normal mode.
Whats the Windows version?
Sent from My LG G Flex LG-F340K Stock KitKat V20D on LTE Network using XDA Free Mobile app
Alright, here goes...
Started when the volume buttons stopped registering pushes. I replaced the clickers (for lack of better term) but problem did not go away. I then attempted a backup restore via TWRP but Flex powered down (battery level was above 90% prior to restore). I then connected to computer (then running W8) and it showed up as qual_blahblah. I d/l factory partitions and followed a guide to fix partitions...well the guide did not work out in my favor because after reboot, device would show LG splash, go black and show LG splash again, followed by an android guy on his back with the yellow triangle above him. I will note that that is the only thing (android guy on back) I see when I try a normal boot up/power on.
I am running W10 on my PC currently.
First of all why did you try to restore your partitions if you had twrp and a saved backup. That should have solved any issue there. The volume buttons going bad wouldn't have been a software thing unless you used some mod that could have disabled them. Then that can be fixed via factory reset. Or restore backup.
OK so to fix your FLEX just plug it up in download mode and to your PC with lg's PC suite software installed on your PC. Not sure if windows 10 is supported for PC suite or not or if this works on win 10. May have to try someone else's pc. And make sure you have internet service on that PC.
At the top of the PC suite program window there are several options to choose from. Not sure off the top of my head what they're called but there is an option some where up there to restore from bad update or recover from bad update. Something like that. I wrote a tutorial about a year ago on how to do this. It should be in the general section. Try that out.
Back to the volume buttons or clickers as you call them. The ones that you replaced them with may be defective. If you bought some cheap Chinese BS then it could possibly be for be made as more of a universal off brand made to work in a lot of lg's but for some reason not compatible with the FLEX. I've bought a new sim card /sd card ribbon for an asus zenfone 2 before that was that very issue. Speaking from experience.....spend the extra dough and get the quality parts not Chinese sweat shop BS.
And good luck
Hey all. My wifes phone decided to brick itself. Hers is/was an unlocked unit not purchased from verizon but on their network. I noticed its now locked. It randomly reset and on boot, the screen started blinking and was unresponsive. Then it rebooted again and the "try again, factory reset" note came up at the top of the screen. Try again yielded the same pattern. So, I tried full wipe, same thing, loop back to the try again screen. Then, I tried to side load the ota. All seemed ok. Installed her sim, all good. Went to settings to change to 3 button nav and boom, fail and try again screen. Was this a delay from maybe a bad sim card? Is 3 button nav an issue? Did evil verizon lock her phone? Can they do that?
So, I ordered another 4xl because she needs a solid phone to function for work. Id still like to know if I can recover the borked unit. Any help is appreciated.
You did all the correct things. Unfortunately it sounds like a hardware issue. Anytime you factory reset you have ruled out a software issue. Further, flashing a "rescue ota" via adb that resets the phone even with a locked bootloader. You've done everything you can do, except leave the red devil.
So now, I have it working, but not trusting it. I dont dare change to 3 button nav though...hahaha Still going to use the one we bought so she has a solid phone for work.
On another note. We're now stuck in the gmail recovery loop. 2 email addresses referencing eachother for recovery of passwords. Its maddening. I thought if I could get her phone to work, there would be some google magic that may kick in.
Its all evil.
sadly my 4xl has the same problem, it seems to be a serious bug from Google and needs to be fixed. Phone can't access Fastboot mode or Recovery mode, it can only stay in 9008 mode. This situation happened when I tried to update android 12 version but failed. Hope to have help from the developer, because there will be many people facing the same situation.
Hey all.
So for carbon coupe:
1. Verizon can't just lock your phone if it is unlocked, this is something that happens during the manufacturer process. So if it randomly restarted there may be another cause.
2. You wrote that when on 3 button navigation it works fine but if you switch the phone starts boot looping. This is clearly a software issue rather than a hardware issue(there is no chip responsible for the type of navigation system), so there may be a problem with the OS. This is a good thing because it means it's fixable without the need of money.
Factory reset usually fixes most problems but not all of them, as some partition aren't changed during the process, like boot or system.
So the problem is in one of those partition, just like when you have a locked phone and after reseting it it still knows it is lock.
The solution is to flash the firmware of the phone to fix it.
For sSjBlueVN197,
if you are on this mode it's called EDL mode. If you are on this mode it means fastboot and adb aren't available. On that mode you can flash firmware to the phone, even if it is locked or bricked.
This propose of this mode is to allow developers to flash firmware if when the system is damage, and some other partitions like boot and others are also damage. It's just like an emergency mode to rescue the phone.
Anyway, for both of you, here is what you need to fix your phone:
*Keep in mind this only works on windows, and I am assuming you have ADB and Fastboot command line installed, and you have some experience using the command line, and you are using a recent version of Windows10,*
1. Remove Lmobile drivers(from device manager on windows) and install the Google one's instead. If you don't know how to do it just search on google and you will find a tutorial
2. You need to download Qualcomm drivers and QPST tool. I will leave a link to a website where you can download it.
3. After Qualcomm drivers are installed, set up QPST.
3. On your phone, if you have access to adb, run without quotes "adb reboot EDL"(for carbon coupe)
If the phone can't reach adb there are other 2 methods, one using fastboot commands and other using the testing pins(requires phone disassembly)
As my phone is working and running fine android 12 I only know the adb command.
Once on EDL mode the screen is going to be completely black, and device manager will se your phone as :
QUALCOMM HS-USB QDLOADER 9008(COM "USB port number")or something similar.
Now you can use the QPST tool to flash the firmware and boot image, or any other software that supports EDL mode.
Here is a link to a website which explains very well how to set up and use the QPST tool and where you can download all you need.
Hope this helps you!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.
#mcl said:
You are going to need also these files, that are the programmer files.
PLEASE KEEP IN MIND I DIN'T TRY OUT THIS FILES, SO THEY MAY BE FOR OTHER PHONE OR MAY NOT WORK.
So please use this files with caution, I found them on a post of XDA and they are in theory from a working Google Pixel 4XL, so they should work.
Though I didn't test them so they may just not work at all.
Click to expand...
Click to collapse
hi, i have pixel 4 xl firehose but its asking for 2 more files raw program and patch file...
pixel4-XL_firehose - Google Drive
drive.google.com
#mcl , can you advices me the method that can fix this problem . so xml file can not meet this point .
Hi,
I recently bought a Note 10 pro (M2101K6G) since my Note 6 pro died and now I'm trying to unlock the bootloader.
However, I can't seem to get the phone to show up in the MIFlash Unlock tool. (Downloaded here)
What I did:
- First I installed the xiaomi usb driver.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Then I enabled developer options and then USB Debugging and OEM Unlock.
- Then I added my Mi account to the phone and it said Added successfully. Mi account is associated with this device now.
- After that I booted to fastboot, connected the phone and startet up the Unlock Tool (batch_unlock.exe) as Administrator.
- Then I logged in in the Unlock Tool.
- However, the Unlock Tool is still empty.
Trying to start the tool first and the connect the phone didn't work either.
The log from the Unlock Tool is attached to this post.
When I do a fastboot devices my phone will show up like this. However it still won't show up in the Unlock Tool.
I also tried following many tutorials and the difference was always that the current version of the Unlock Tool is called batch_unlock.exe and the older versions are called miflash_unlock.exe.
So I also downloaded an older version (miflash_unlock-en-4.5.813.51) and tried this one.
However, I can't seem to get past the account screen (my guess is because it is outdated?):
However, here in the settings I was able to click check driver and it seems that I have a correct driver installed:
So can anyone help me get my device unlocked?
Thank you!
DocRingeling
Try this new version and run as administrator. It should work
Code:
http://miuirom.xiaomi.com/rom/u1106245679/5.5.224.55/miflash_unlock-en-5.5.224.55.zip
Click refresh few more times. I too faced this issue. Or try plugging in device to some different port.
Connect phone to PC before launching flash tool.
miravision said:
Try this new version and run as administrator. It should work
Code:
http://miuirom.xiaomi.com/rom/u1106245679/5.5.224.55/miflash_unlock-en-5.5.224.55.zip
Click to expand...
Click to collapse
I tried this and it also can't seem to find my phone:
I also tried replugging and different ports with no luck.
Try a better quality USB cable
miravision said:
Try a better quality USB cable
Click to expand...
Click to collapse
I only have the included one since this is my first USB-C device. I will try to get some cables to test tomorrow. However, data transfer works with the cable and adb and fastboot can detect the phone. Just not the unlocker.
DocRingeling said:
Hi,
I recently bought a Note 10 pro (M2101K6G) since my Note 6 pro died and now I'm trying to unlock the bootloader.
However, I can't seem to get the phone to show up in the MIFlash Unlock tool. (Downloaded here)
What I did:
- First I installed the xiaomi usb driver.
View attachment 5450915
- Then I enabled developer options and then USB Debugging and OEM Unlock.
- Then I added my Mi account to the phone and it said Added successfully. Mi account is associated with this device now.
- After that I booted to fastboot, connected the phone and startet up the Unlock Tool (batch_unlock.exe) as Administrator.
- Then I logged in in the Unlock Tool.
- However, the Unlock Tool is still empty.
View attachment 5450883
Trying to start the tool first and the connect the phone didn't work either.
The log from the Unlock Tool is attached to this post.
When I do a fastboot devices my phone will show up like this. However it still won't show up in the Unlock Tool.
View attachment 5450891
I also tried following many tutorials and the difference was always that the current version of the Unlock Tool is called batch_unlock.exe and the older versions are called miflash_unlock.exe.
So I also downloaded an older version (miflash_unlock-en-4.5.813.51) and tried this one.
However, I can't seem to get past the account screen (my guess is because it is outdated?):
View attachment 5450911
However, here in the settings I was able to click check driver and it seems that I have a correct driver installed:
View attachment 5450909
So can anyone help me get my device unlocked?
Thank you!
DocRingeling
Click to expand...
Click to collapse
....if "fastboot devices" shows up a number then your system has recognized your phone. So the problem is miflash.
Try to copy the whole miflash-folder to the root of your HDD, then run as Admin. Before do this restart your PC. Try this with different versions of miflash-unlock tool.
opg2000 said:
....if "fastboot devices" shows up a number then your system has recognized your phone. So the problem is miflash.
Try to copy the whole miflash-folder to the root of your HDD, then run as Admin. Before do this restart your PC. Try this with different versions of miflash-unlock tool.
Click to expand...
Click to collapse
MOD EDIT: Quote removed since post deleted.
This did it. I have moved it to C:\Xiaomi\miflash_unlock-en-5.5.1008.26 and then it worked like a charm.
Thank you guys so much!
DocRingeling said:
This did it. I have moved it to C:\Xiaomi\miflash_unlock-en-5.5.1008.26 and then it worked like a charm.
Thank you guys so much!
Click to expand...
Click to collapse
Please like comment share and subscribe to this channel to motivate the youtuber
Hayatzada said:
Please like comment share and subscribe to this channel to motivate the youtuber
Click to expand...
Click to collapse
Good point! Done!