Database Develop

Help with Bootloader and Root. I'm stuck! XT1063

Hello!
I'm from Puerto Rico, my carrier is Claro PR. I've been trying to root my device but so far I haven't even been able to unlock the Bootloader. I get the annoying and indefinite < waiting for device > message on the Fastboot CMD screen. I have installed ADB drivers from Google and it didn't help since the Motorola drivers did not even recognize my device in Fastboot. It seems that the only time my device is recognized in Fastboot mode is when there are no ADB or Fastboot drivers installed and Device Manager lists it as a Fasboot Titan device. Quite honestly this is very frustrating since I've been searching for days to no avail. I do not wish to update to Lollipop(Until it is available officially in my area), which is what most articles I found are for. I just want root access. I'm beginning to doubt if my device is even supported and its just an extremely well made clone.
I was trying this on Windows 8.1 Pro x64. Some people told me Fastboot drivers had some issues with 8.1 so I did my best to clean out old drivers and plug the phone into different USB ports. At first I was trying on my USB 3.0 ports, people also told me USB 3.0 has issues with FB, so I used my 2.0 ports on the front of my computer case. Again, people told me that I had to use ports directly on the motherboard, so I plugged the phone into my PC's back USB ports. I also tried a different micro USB cable, same result. At that time I figured it was probably Windows causing the problems so I pulled a hard drive from and old PC, hooked it up to my own and installed my old copy of Windows 7 Ultimate x64. I installed all the essentials, from ADB to Motorola Device Manager for the drivers. My phone is still not being recognized, although I did get to have it listed under ADB Devices by using USB Debugging, yet it appears offline, as shown in the image below. I figured it was my particular PC because its custom built with salvaged parts from another PC, so I tried the procedure from my family's Dell Optiplex (running win7 Home Premium x32) only to hit the same dead-end. At this point I'm tearing off hair from my head. I don't want to be bald yet! I'm only just turning 20 at the end of the month!
A few details:
Device: Moto G 2014 16GB XT1063. Android Kitkat 4.4.4 (5.0 has yet to be released for my area)
System Version: 21.11.14.titan_amxpr.amxpr.en.PR amxpr
Build number: KXB21.85-14

Inquisitor956 said:
yet it appears offline
Click to expand...
Click to collapse
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.

doppelhelix said:
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.
Click to expand...
Click to collapse
Thanks solved a problem I had on other laptop that would not show phone

doppelhelix said:
If you connect your device with usb-debugging enabled in the developer options, a dialog pops up, presenting a RSA fingerprint, asking to allow usb-debugging. If not, type "adb version" in your terminal. If version is below 1.0.31 you have to update adb.
Click to expand...
Click to collapse
Thank you! The RSA Fingerprint popup never appeared on my phone. I kept toggling USB Debugging on and off until it did. I managed to get the keys. Now I hit another wall... (image below)
I also tried it onto the Latin America page. This time no matter how I paste my code whether manually typing it or just copy/pasting, it always returns a popup with "Your input text was not recognized as a valid dataset. Please try again." This happens on Chrome, Firefox and even Internet Explorer and combined with the really slow loading of any official Motorola page I try to enter I'm guessing the forces of life itself are preventing me from unlocking this particular phone's Bootloader.

Inquisitor956 said:
preventing me from unlocking this particular phone's Bootloader.
Click to expand...
Click to collapse
Please have a look here: https://forums.motorola.com/posts/f2061da875

doppelhelix said:
Please have a look here:
Click to expand...
Click to collapse
Thank you once again! My device IS unlockable, I was told to wait for some time before requesting my unique unlock key, since the page has been having a few hiccups. I will report back if I was successful or not.
Edit: I successfully unlocked bootloader, installed TWRP and rooted. Thank you for your assistance!

http://developer.sonymobile.com/ instructions to Unlock Bootloader - problems

I'm having some problems following the instructions from http://developer.sonymobile.com/ regarding setting up Android Studios and the recommended 'fastboot' drivers on Win 10. I have done some vocoder development in the past and have a background in tech development and dedicated microprocessor programming, but i'm in over my head here. I could use a little help.
This is on a Sony Xperia Z Model C6606 4.3 T-Mobile variant Build 10.4.C.0.814. Even though I checked (by *#*#7378423#*#*) and got unlock bootloader allowed: No.; T-Mobile tier 2 technical support indicated that I should try the OEM method anyway. When I checked their site, I plugged in all the info about my phone and it indicated that I could unlock the boot loader. :Big Grin:
Now to the problems. This is where you hear the *blub blub* as I wade into the deep end.
Their instructions read in part, "1. Download and install the Android SDK."; which I did, including loading the Google USB drivers.
2. If you’re running Windows, you also need to download and install an updated Fastboot driver. This is the standard android_winusb.inf-file, with a few lines of code added to enable Fastboot to support Sony & Sony Ericsson devices. Replace the original android_winusb.inf-file with the downloaded file in the usb_driver folder, located in the Android SDK > extras > google folder on your computer. If you can’t find the usb_driver folder, make sure you are running Google USB Driver package revision 4 or higher in your Android SDK. If not, install the Google USB Driver Packager using the Android SDK manager.
Note: Google USB Driver Packager is ver. 11
After a visit to the device manager, following numerous tips from various sources and floundering about, I looked at the two INFs and found some discrepancies. The first is the one from the Sony 'fastboot driver' link above for their version of android_winusb.inf. The error I get here is based on the fact that this download contains NO CABS and the Google USB cabs do not have the installation files the Sony INF needs. On the other hand the Google USB 'extras' loaded by Android Studio do not include specific support for the Sony Xperia Z. :forehead slap:
Short version, I can't connect to fastboot.
I have tried both INFs and in each case with USB debugging enabled on the Z, I powered it down, held the VOL up button as I plugged the cable into the USB port. In all cases I got the blue light but no windows prompt asking for a driver! Even when I open a command window in the directory where the INF resides I DO NOT get a list of adb devices. If I enter 'fastboot devices' from the command prompt, I get the stock windows error that 'fastboot' isn't a recognized command.
If I could get a little direction here as to next steps, I would really appreciate it. Thanks.

Download an install flashtool, you'll find a link here in the forum. Can't search myself right now as I'm on the phone with slow Internet. In the thread is everything explained and it's very simple to use.

Oops
The correct folder is \AppData\Local\Android\sdk\platform-tools. No wonder it wouldn't load fastboot. Ultimately however, fastboot with the OEM unlock code didn't work. "FAILED (remote: Command not allowed)". BUMMER!
Thanks anyway. Now I'm off to flash what I can...

Best mehod is to install 15 second adb install-it installs adb and fastboot and can be open anywhere
give it a try
http://forum.xda-developers.com/showthread.php?p=48915118

ManagementCritic said:
....Even though I checked (by *#*#7378423#*#*) and got unlock bootloader allowed: No.....
Click to expand...
Click to collapse
Your bootloader cannot be unlocked. Blame your operator...

Hey ptmaniac,
Thanks for the response.
Yeah, I get that. I wrote in another thread how I had attempted to negotiate a remedy through both the OEM and the carrier; not that I expected a good result, but probing for what was left unsaid. I wanted to see if I could determine their reasons and motivation and whether they would consider any alternatives. The only admission was that they could, but would not. Best guess? It has to do with existing agreements they are unwilling to revisit.
ptmaniac said:
Your bootloader cannot be unlocked. Blame your operator...
Click to expand...
Click to collapse

@ManagementCritic
No problem,
In my country it's the same endless loop unfortunately... the carrier says i should talk to the oem, the oem says the phone was locked at carrier request and they can't do anything about it so i should talk to the carrier instead
I still blame myself from buying a full priced device locked to the carrier, i thought all of them could be unlocked anyway by submitting imei to the sony developer website... if i had researched a bit more i would have figured out that i should have bought it unlocked directly from the oem... lesson learned i guess.

New Nexus 6 on Marshmallow without SIM Card - Can I still update to 7.1.1?

Bought a new in box N6 that comes with Android 6.0.1. Checking system update via WiFi can't find any updates to 7.1.1. Are system updates tied to having carrier service? I'd like to just use this device as an e-reader and for media consumption. Is there a way to force this update without root? Thanks!

I'm not really sure don't have a Nexus 6 yet although im sure it'd be possible thru recovery possibly
Sent from my LG-M153 using Tapatalk

New in box Nexus 6 devices come with Android 5.0 standard, thus yours isn't new if it comes with Android 6.0.1. Updates are not tied to having carrier service, but if you want stock Android 7.1.1 on the device you'll have to flash a ROM using ADB (Android Debug Bridge). OTA (Over The Air) updates for the Nexus 6 do not go past Android 7.0.0, even though Android 7.1.1 ROMs are available for download from Google. For more information on how to manually update the N6, please check out the sticky posts in the General forum.
P.S. None of this requires root.

Strephon Alkhalikoi said:
New in box Nexus 6 devices come with Android 5.0 standard, thus yours isn't new if it comes with Android 6.0.1. Updates are not tied to having carrier service, but if you want stock Android 7.1.1 on the device you'll have to flash a ROM using ADB (Android Debug Bridge). OTA (Over The Air) updates for the Nexus 6 do not go past Android 7.0.0, even though Android 7.1.1 ROMs are available for download from Google. For more information on how to manually update the N6, please check out the sticky posts in the General forum.
P.S. None of this requires root.
Click to expand...
Click to collapse
Hmm, well mine was sealed when I got it, so how can that be? I would manually update, as I'm not new to rooting (have had rooted Galaxy S3, Sony Xperia Z3C, etc), but unfortunately, I'm one of those unlucky ones that have that dreaded "Unknown USB Device (Device Descriptor Request Failed) when connecting to Windows 10. I see that plenty of other Nexus owners have had this issue as well. I can't for the life of me solve this, and I've tried every suggestion I've googled. Any idea how else I can update without using a computer, or maybe you know a workaround to this Windows 10 BS?

"New" Nexus 6: Was your box shrinkwrapped? If so, it's a rewrap as Nexus 6 boxes do not come shrinkwrapped. On a new Nexus 6 you have a label that must be cut to get into the box. In this case, the version of Android on your device is a dead giveaway that it isn't new. I purchased mine brand new from Amazon 19 months ago, when Android 6.x was readily available for the device, and out of the box it came with Android 5.0.
Unknown USB issue: https://forum.xda-developers.com/android/general/fix-unknown-usb-device-device-t3375320
I can't guarantee the above will be of much help as I don't have this issue on any of my Windows 10 devices.

Do you have a phone with the same size SIM chip? Have you tried just putting it into the Nexus 6 to see if it will update that way?

Strephon Alkhalikoi said:
"New" Nexus 6: Was your box shrinkwrapped? If so, it's a rewrap as Nexus 6 boxes do not come shrinkwrapped. On a new Nexus 6 you have a label that must be cut to get into the box. In this case, the version of Android on your device is a dead giveaway that it isn't new. I purchased mine brand new from Amazon 19 months ago, when Android 6.x was readily available for the device, and out of the box it came with Android 5.0.
Unknown USB issue: https://forum.xda-developers.com/android/general/fix-unknown-usb-device-device-t3375320
I can't guarantee the above will be of much help as I don't have this issue on any of my Windows 10 devices.
Click to expand...
Click to collapse
Not shrinkwrapped. Just the sticker cover on the box sealing it. Anyway, I saw that link, but not sure what key would be appropriate for the Nexus 6, as the key the poster wrote on that might be for the HTC? I think i would need to change that to the device ID for this, but since my computer won't even recognize the N6, no details appear for me. WOuld you happen to know it? Thanks
Paul1201 said:
Do you have a phone with the same size SIM chip? Have you tried just putting it into the Nexus 6 to see if it will update that way?
Click to expand...
Click to collapse
I have one in my iPhone. Not sure if it's the same size, but will try that. I was hoping I wouldn't have to ever put a SIM in this, but I'm at last resort now.

@radiohead14 - There were a lot of problems with the early MM releases and windows drivers.
Can you try booting to a Linux flash drive? Then you could use ADB to sideload 5.1.1. Then go back to windows and I'll bet it finds the phone correctly. You should be good to go upgrading again after doing that. Once windows finds the phone, you should be ok in the future.

ktmom said:
@radiohead14 - There were a lot of problems with the early MM releases and windows drivers.
Can you try booting to a Linux flash drive? Then you could use ADB to sideload 5.1.1. Then go back to windows and I'll bet it finds the phone correctly. You should be good to go upgrading again after doing that. Once windows finds the phone, you should be ok in the future.
Click to expand...
Click to collapse
I was able to upgrade to 7.0 after putting my SIM in (so I guess updates are tied to having carrier service), but in-between the updates from 6.0.1, i kept testing the USB connection. unfortunately it still won't get recognized, so at this point, I don't think it's the Android version. I'm just gonna return it.

radiohead14 said:
I was able to upgrade to 7.0 after putting my SIM in (so I guess updates are tied to having carrier service), but in-between the updates from 6.0.1, i kept testing the USB connection. unfortunately it still won't get recognized, so at this point, I don't think it's the Android version. I'm just gonna return it.
Click to expand...
Click to collapse
I certainly understand not wanting to deal with it. Particularly if your not comfortable with Linux. The thing is, the advice to roll back to 5.1.1 was specific as the last release that had a high probability of working with win10. If you are somewhat comfortable with Linux, it's easier to get it connected and will help prove whether it's the device or win10.

ktmom said:
I certainly understand not wanting to deal with it. Particularly if your not comfortable with Linux. The thing is, the advice to roll back to 5.1.1 was specific as the last release that had a high probability of working with win10. If you are somewhat comfortable with Linux, it's easier to get it connected and will help prove whether it's the device or win10.
Click to expand...
Click to collapse
Ok, I'll give it a shot. Do you have a link where I could follow instructions to how? Thanks!

radiohead14 said:
Ok, I'll give it a shot. Do you have a link where I could follow instructions to how? Thanks!
Click to expand...
Click to collapse
How to create a bootable Linux Mint USB drive using Windows Accurate, though the current release of mint is 18. You could use Ubuntu (Mint is a derivation of Ubuntu) but I link to mint because most users find it easier.
For Nexus 4 but still accurate for N6. Not mentioned is;
in some cases it's also needed to restart adb with:
adb kill-server
adb start-server
Or completely reboot the system
I assume you know this, but as a reminder, If you have just enabled the ADB debug option on your phone and created a new connection, the ADB command might list your device as unauthorized. Just check the screen of your phone then to authorize the new connection.
In case you hadn't seen this thread: nexus 6 one beginners guide.
I would be happy to help you through this. The only thing is I'm traveling the next 2 days so it will be intermittent and late before I can get on a computer
P.S.
the "sudo" command referenced is to gain elevated privileges. you shouldn't be prompted to enter a password when using a bootable flash drive.
the "whoami" command will tell you who you are logged in as.

Asus Zenfone GO (ZB551KL) IMEI NULL ( 0 )

Like the topic says, my ZB551KL Zenfone Go won't register network operators and i suspect it's because the IMEI of the phone is 0 after applying official update. I've tried to Root the phone by downgrading to version WW_V13.2.8.13 and installing KingRoot and using Xposed IMEI modules but this fuxed up the phone and sent it into a bootloop. So i reinstalled the WW_V13.2.8.13 firmware again (the only firmware that KingRoot will work on, so basically the only way to root the phone) and rooted the phone again and tried to open the diagnostics port through adb shell, but when i execute the command: "setprop sys.usb.config diag,adb" it says setprop: not found.....so i am guessing i can't open the diagnostics port this way. And Xposed IMEI changer won't work cause Xposed fux up my phone into a bootloop.
So if anyone has any idea how i could change my IMEI back to what it originally was i am all ears. I was reading something about using a HEX editor, but i don't know how to get the IMEI files out of the phone or how to write them back into the phone.
And yes i've tried installing every official firmware, factory reset many times etc.... IMEI is 0 until i somehow change it myself. And when i do my SIM cards will be able to register on the network again. So any help is very much appreciated.

Honestly, they should just ship android with rooting options. Rooting newer devices is a huge pain in the neck right now.

This device is just downgrade as someone posted before and use kingroot, the problem is to enable diag port.

How we can root zb551kl

same problem here.. pls help

dbfonseca said:
This device is just downgrade as someone posted before and use kingroot, the problem is to enable diag port.
Click to expand...
Click to collapse
yep enable diag port take the hell out of me

i enabled diagnotic mode
eyobaaa said:
yep enable diag port take the hell out of me
Click to expand...
Click to collapse
how to recover imei from zero ?? i enabled diagnostic mode on this device

Basically you have to boot to fastboot then flash CSC firmware (also called RAW firmware) to enable qualcomm diag port.
Note that there are 2 kinds of this: 1 is the kind that connects via QDLoader 9008/QFIL to recover from hardbrick, and one that installs a very raw form of android and enables the diag port. You need the latter. Since I don't have the files anymore, you basically run this bat script file that connects via fastboot and hot-boots its own kernel that allows the diag port.
Then use this program called FactoryTool_WriteIMEI_v1.0.2 (Factory_tool_wingtech_v1.0.2.0.exe) to write the IMEI (since official qpst dont support dual Sim). You may need to fire up QPST/QFIL to get a proper com port for the software to work. Then flash first old firmware and you're good to prevent it getting corrupt again.
---
Problem is that this seems to be a symptom of a failing board since ever since the LCD started to flicker when in battery mode and OK when USB is plugged in. Baseband and IMEI becomes corrupt again when you update your system. Also periodically phone shuts down and becomes a 9008 device (hardbrick) but also comes back. Left it alone for days and it was fine after but problem came back after trying a game (solder cracks?) Will try to reflow the motherboard.
May I ask if you changed your LCD? This started happening to mine when I installed a system update after replacing the LCD+digitizer. It seems the phone is downloading the Chinese software update since it detects the (chinese?) panel and installs an incompatible Chinese modem baseband firmware. Upgrading to latest downloadable firmware also corrupts the IMEI slowly (Sim 1 first then Sim 2).

I need help to unlock bootloader

Hello everyone,
I've decided to unlock my device to flash vanilla android but I couldn't unlock it. I've tried almost everything but even the latest MiUnlock doesn't recognize my device on fastboot, the PC itself recognizes it before and after getting into fastboot, I hear usb device connected sound and can see the phone under Windows devices.
Adb devices command works if the phone is switched on, my dev settings are ok, oem unlocking and adding account under dev settings are ok, I've tried it with disabled windows signature enforcement too but nothing happened. MiUnlock simply doesn't want to see the device on fastboot.
Can anybody help me, please?

abstra said:
Hello everyone,
I've decided to unlock my device to flash vanilla android but I couldn't unlock it. I've tried almost everything but even the latest MiUnlock doesn't recognize my device on fastboot, the PC itself recognizes it before and after getting into fastboot, I hear usb device connected sound and can see the phone under Windows devices.
Adb devices command works if the phone is switched on, my dev settings are ok, oem unlocking and adding account under dev settings are ok, I've tried it with disabled windows signature enforcement too but nothing happened. MiUnlock simply doesn't want to see the device on fastboot.
Can anybody help me, please?
Click to expand...
Click to collapse
The issue that you are experiencing is strictly with your PC.
You need to ensure that you are using an account that has admin privileges, and be sure that you antivirus is not neutering your usb drivers and Miflash program.
Next, if you are using a newer computer with usb 3 ports, you will need to use a USB hub ( USB 2 is your best option.) , then the phone will be seen in fastboot. As long as you have setup developer options, and your MiCloud account is setup.
Finally, it will take 2 weeks to unlock the bootloader , after your first request. Some people who had been syncing the phone to MiCloud for some time before attempting were able to immediately unlock. Personally we have 3 Mi8's in our house and I had to wait 2 weeks on each one.
To reiterate, your main issue is probably the usb ports, and your antivirus the the 2nd most likely culprit. Worst case use another computer. The process is much easier on older PC's.
you can use the the All in one tool to double check that your drivers, adb , and system wide privileges are up to date and setup correctly. https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
Instructions are available on that thread.

Thanks for your help, I've already tried almost everything you've said up there and even gave a try on virtualbox Windows 7 with USB 2.0 setup.
I remember I've unlocked my friend's device last year on an only USB 2.0 computer, my laptop has unfortunately only two 3.0s and one USB-C. The phone can be seen under fastboot devices command if MiUnlock is not running, if I click on that cr*p program my device either falls from fastboot devices list or says press any key to shutdown.
The main problem is the ports and that damned program itself, how come it lockdowns the connection and after that pc couldn't even show my phone in devices list but can be seen in device manager. I'm literally shocked by the cheapness of this very software.

abstra said:
Thanks for your help, I've already tried almost everything you've said up there and even gave a try on virtualbox Windows 7 with USB 2.0 setup.
I remember I've unlocked my friend's device last year on an only USB 2.0 computer, my laptop has unfortunately only two 3.0s and one USB-C. The phone can be seen under fastboot devices command if MiUnlock is not running, if I click on that cr*p program my device either falls from fastboot devices list or says press any key to shutdown.
The main problem is the ports and that damned program itself, how come it lockdowns the connection and after that pc couldn't even show my phone in devices list but can be seen in device manager. I'm literally shocked by the cheapness of this very software.
Click to expand...
Click to collapse
Again the issue is with windows, I have personally dealt with the exact same issue. That is why I recommended using an older computer that has not been recently updated.
But you are absolutely right, Xiaomi has not made any development improvements with their desktop applications in over a year and that is ridiculous.
I would suggest using alternate versions of the software : I just did a google search and on this link people were saying just one week ago that this linked software worked for them, note its a video, the software link is in the description : https://www.youtube.com/watch?v=l_PEAJ-n2_c
Finally, I am personally using this version of Mi Flash : https://androidfilehost.com/?fid=11410932744536991669 on a brand new intel PC.
and the last time that I unlocked a xiaomi phone I used unlocker software from here ( Note the multiple versions at bottom of page)
https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/
If one doesn't work try another. just be sure that you have developer options setup correctly and that you are signed in a syncing with mi-cloud. You will get it unlocked eventually. I can assure you that it was a Pain in the A*$ for me too!

Thanks man, these are the exactly same links I’ve found and checked out while trying to connect my phone but I just gave up after three days of struggling and pressing volume+power buttons and ordered a USB 2.0 hub online. Unfortunately there are no older computers around me or anyone I can ask for because of you know, the quarantine. I’m actually using cloud actively, so I should better be prepared for an immediate unlocking, and backup my data beforehand as usual.

Just wanted to write about the news, I've backed up my data and connected my device to MiUnlock on USB 2.0 Hub and ta-da it's immediately unlocked without any waiting time. That was a smooth process, I'm shocked but happy.

abstra said:
Just wanted to write about the news, I've backed up my data and connected my device to MiUnlock on USB 2.0 Hub and ta-da it's immediately unlocked without any waiting time. That was a smooth process, I'm shocked but happy.
Click to expand...
Click to collapse
Nice, so my original suggestion about using 2.0 usb was correct. I am glad that you have the issue sorted. I am also surprised about you being able to avoid the wait time. That is a nice break. Enjoy your phone.
PS: Be sure to make a full TWRP backup and save it to your desktop. That backup will save you if you ever experience a bad issue.

tsongming said:
Nice, so my original suggestion about using 2.0 usb was correct. I am glad that you have the issue sorted. I am also surprised about you being able to avoid the wait time. That is a nice break. Enjoy your phone.
PS: Be sure to make a full TWRP backup and save it to your desktop. That backup will save you if you ever experience a bad issue.
Click to expand...
Click to collapse
Thanks man, and yes that was all about fastboot which is written to be used with older usb versions. After plugging in the hub, it’s connected directly in just milliseconds. I am surprised that I’ve really skipped the waiting for two weeks or maybe more and yeah it makes me happy.
I made a full data backup before unlocking and then all the dangerous partitions including modem, efs and bluetooth in TWRP to avoid any irreversible loss. I never skip my recovery backups since 2010 and my first Android smartphone which was an HTC Desire A8181, I learned it in a hard way to never skip them, if you do, you either lose your data or your mobile device identification. :victory:
A question from a Xiaomi-newbie; If I run clean all and lock command on MiFlash, should I wait for an unknown time to unlock the device again? Or does Xiaomi let users to lock/unlock their devices anytime without waiting if you’ve unlocked your bootloader once before?

abstra said:
Thanks man, and yes that was all about fastboot which is written to be used with older usb versions. After plugging in the hub, it’s connected directly in just milliseconds. I am surprised that I’ve really skipped the waiting for two weeks or maybe more and yeah it makes me happy.
I made a full data backup before unlocking and then all the dangerous partitions including modem, efs and bluetooth in TWRP to avoid any irreversible loss. I never skip my recovery backups since 2010 and my first Android smartphone which was an HTC Desire A8181, I learned it in a hard way to never skip them, if you do, you either lose your data or your mobile device identification. :victory:
A question from a Xiaomi-newbie; If I run clean all and lock command on MiFlash, should I wait for an unknown time to unlock the device again? Or does Xiaomi let users to lock/unlock their devices anytime without waiting if you’ve unlocked your bootloader once before?
Click to expand...
Click to collapse
I have only unlocked my device once. But I wouldn't think there would be an issue to unlock a second time. In fact, I have read about some people needing to wait 72 hours to unlock it again after relocking. if using Mi-Flash just try to be sure uncheck that lock bootloader box, that is unless you want it locked.
One last thing, if you ever decide to restore the phone using the flashall.bat method, the bootloader stays unlocked.