My phone isn't rooted, I ran the update from Xiaomi from the settings menu and after a bit of time my phone was stuck on the splash screen for miui. I tried rebooting multiple times but I couldn't get my phone to boot up.
Did some searching over the web and tried to recover my phone using the MIFLASH tool, which showed my phone but would say its locked. I tried the unlock tool and the phone still wouldn't unlock due to asking for auth.
The last thing I tried was the EDL method, when I plug my phone into my PC it's listed in the device manager as Android BootLoader and not a com port.
I did install the drivers from MIFlash, there were no error messages, but I did see some Chinese text listed.
Is there anything I can do or have I been going about it wrong?
Did you managed to fix your phone my friend?
xxphoneuser said:
My phone isn't rooted, I ran the update from Xiaomi from the settings menu and after a bit of time my phone was stuck on the splash screen for miui. I tried rebooting multiple times but I couldn't get my phone to boot up.
Did some searching over the web and tried to recover my phone using the MIFLASH tool, which showed my phone but would say its locked. I tried the unlock tool and the phone still wouldn't unlock due to asking for auth.
The last thing I tried was the EDL method, when I plug my phone into my PC it's listed in the device manager as Android BootLoader and not a com port.
I did install the drivers from MIFlash, there were no error messages, but I did see some Chinese text listed.
Is there anything I can do or have I been going about it wrong?
Click to expand...
Click to collapse
.... you have to unlock your bootloader first.
Related
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
yakub234go said:
You have to use full unbrick method(xfstk + raw) to restore ur device fully
xfstk will restore ur fastboot image
Click to expand...
Click to collapse
Thanks for the response. I've tried this a dozen times, but unfortunately (this is going to sound weird) since it's not completely bricked it is only detected as Moorefield for a few seconds when started. This allows the xfstk tool to detect it and begin the download, but not long enough to complete the process so it times out. The only development access I have to the phone now is via adb, but since I don't have root I'm very limited in what I can do via command line. Since I can't access fastboot I can't achieve root. It's just a comedy of errors now.
kidnova said:
The backstory: I have no experience with rooting and or flashing custom ROMs. Prior to today my ze551ml was completely stock, running on the official android M update. I had a need to do a factory reset, but the phone would simply reboot. I assumed this was a problem with the update so I download and attempted to install the downgrade to l. Naturally it crashed mid downgrade and I thought it to be bricked. So, I started Googling and realized I was able to get into fastboot mode, but not recovery. Following a guide I located I attempted to flash the preroot ROM located at the link below:
http://forum.xda-developers.com/zenfone2/development/rom-pre-root-img-t3079590
Well, it appeared to have worked, but now the phone refused to boot at all after being turned off. So, more Googling and I proceeded to follow the full unbricking guide below:
http://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Partway through step 1.3 the phone restarted itself and booted right up into Android L! Success I thought to myself, but it was not to be. I proceeded to download the FOTA L update and it downloaded fine, but when I clicked to install it simply rebooted the phone. Tried a couple of other times with the same result. I realized that Supersu was installed so I did the full unroot assuming that was the problem, but to no avail. It appears that the updates can't install because the phone is incapable of entering fastboot or recover mode. Anytime I attempt to enter fastboot via hard key or through adb the phone hangs on the ASUS logo. Adb detects the phone when it's connected via USB, but of course fastboot can't because I can't get it into fastboot mode at all.
Any tips on how to get fastboot operational again so I can start applying updates again? Every guide I've located has started with "boot into fastboot/recovery" which simply isn't an option. Any help is appreciated.
Edit: Well, I think I've reached the end of the internet trying to google for a solution. The phone works, but it looks like it's stuck on build 2.13.40.13 until the end of its life. If anybody has any ideas I'm still hoping for a solution, but I can't find anything describing how to restore fastboot if the OS is intact.
Click to expand...
Click to collapse
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
sukhwant717 said:
seems like you did not install droidboot.bin correctly... only way is use xFSTK again.i have updated the link to latest raw firmware 2.20.40.194 and use the same guide and commands..
Click to expand...
Click to collapse
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
kidnova said:
The problem is that it's only recognized as Moorefield for a few seconds which isn't enough time for xFSTK to complete the install. Do you know of a way to force the device to stay connected as Moorefield?
Click to expand...
Click to collapse
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
mrperalta said:
Plug the phone to the PC, be sure the phone is completely off and then hold power + vol- for a few seconds. You must see the "Moorefield" driver permanent in the device manager.
Btw... I got the same problem (four lines, not bootloader, not OS; xFSTK FW+OS failed) and I'm stuck in this step :/
Click to expand...
Click to collapse
I've tried this many times, but it only shows Moorefield for a few seconds. I'm assuming this is because it has a fully operational OS so it doesn't stay in the generic USB device mode.
EDIT: I misread your original post. Holding power and volume DOWN does keep connect it in Moorefield. Thanks so much for that. The problem now is that once xFSTK gets to downloading the OS it reboots the phone which takes it out of USB mode and disconnects the tool. I'm still stuck where I was before, but that's a little progress. Any other thoughts?
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
kidnova said:
New update. I'm able to get to the point of loading the OS from xFSTK by skipping the FW part, however it continuously fails. My assumption is because it can't overwrite the existing OS. Any other ideas?
Click to expand...
Click to collapse
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
"those who are not able to keep device connected. take care of few steps
1. in xFSTK option menu change the flag override value to 0x80000807 not 0x800000807 ( don't forget to click gp value over ride)
2. while connecting to xFSTK attach usb to computer. hold power button for 20 seconds to make sure it power downs completely. then hold the power button down and click power button. wait till device vibrate or computer makes detection sound. leave power button but keep holding the volume button for few seconds"
Click to expand...
Click to collapse
-sukhwant717
mrperalta said:
Kidnova, reading this post I could fixed my problem. The "issue" was in the xFSTK where you put the flag (0x800000807). A guy on the threat said to put "0x80000807" instead of "0x800000807" (note that there is "0" from difference).
-sukhwant717
Click to expand...
Click to collapse
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
kidnova said:
You guys are lifesavers! I've got fast boot again. Now to see if I can continue without screwing it up.
FINAL EDIT: I have a 100% functional stock Zenfone 2. Thanks everybody for your help.
Click to expand...
Click to collapse
Hi, got the same issues, I've read many posts. Tried all of the million options. What was your final way of doing it, do you remember?
Hey guys,
I would have liked to get the OREO update, because it said every time is up-to-date, and I wasn't patient. because all of these already get it, and the battery life was terrible with, and I have just 30 days to cancel the phone if I'm unsatisfied with it, so it was urgent for me to update and try it.
But I didn't know enough from the newest devices, so that I need unlocked bootloader to flash STOCK ROM or ROOT or for flash RECOVERY
Mine is XT1789-06, I tried to flash first this ROM:
https://androidfilehost.com/?fid=962187416754456314
It didn't tell this is TMO. :/
This changed my baseband to TMO and my boot image to T-mobile, after I didn't have signal and the fingerprint sensor didn't work.
I wanted fix it with RETAIL ROM flashing.
I tried to flash this: https://androidfilehost.com/?w=files&flid=241773
After that my phone didn't boot, says your device is corrupt.
Cause this I tried to flash back the previous version so this: NASH_RETAIL_7.1.1_NPXS26.122-68-4_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
from here https://firmware.center/firmware/Motorola/Moto Z2 Force/Stock/
But no result. The baseband stucked on TMO, the phone is not start up. Fall back to fast boot mode.
After and mean while these things I tried many things.
The Motorola Device Manager isn't working at all.
The Software Upgrade Assistant what the phone want when show boot up failed message isn't working just say processing device information and isn't going further. I don't understand why the phone ask it, because that is for verizon phones.
The RSD lite says the model name is Fastboot nash S and isn't start to flash anything, when I press the start it says the phone failed to switch to fastboot mode, but it's in that.
I tried already flash more different ROMs, but didn't work one of them .
Recovery is unable, the phone isn't rooted, the bootloader is locked, however sometimes it showed ""Your device software cannot be checked for corruption. Please lock the bootloader", but I checked in the powershell and in fastboot mode I looked what phone says, so it's locked.
I was thinking maybe if I unlock it will solve the problem, but I can't turn it on, so the developer options are unavailable and I don't know maybe it won't help, if I can do it somehow.
Now if I want turn on the phone it's going to fastboot mode right away or say your device is corrupt... and after.
I can't try flash it through Qualcomm 9008 because the PC recognise the device for fastboot device.
In the device manager the computer shows Motorola ADB interface.
I try to unbrick for 3 days, please help me.
Thanks a lot in advance.
Same here, if you find anything out DM me
I already contacted with the phone, I will bring back to Repait it.
I couldn't find out nothing, I tried everything what was possible.
i think i found a solution i just dont know how it works exactly, something to do with a batch file and a full flash of the phone
https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 im going to try this and let you know
Hi, my phone has been dead for like 2 weeks now I even did a remote session in which they tried doing the MSMDownloadtool thing and it did nothing, no vibrations, black screen they just said its fully dead. fast forward to today it just started to react again.
When it tries to boot it boots straight to the OnePlus recovery mode and tells me to input a password, obviously I dont have one seen as its been set and if I click forget password it says it will format everything but it just turns off.
After a few boots I managed to get it to fastboot to realise the bootloader is now locked. the bootloader has always been unlocked since the first day I got it so it must of happened during the MSMDownloadTool process but the issue is now I cant unlock the bootloader because it says "remote: oem unlock is not allowed"
Any suggests that preferably not run MSMDownloadtool because thats been ran so many times already. Thanks
Essentially. No OS, Broken recovery, Locked bootloader and MSMDownloadTool doesnt seem to work. I imagine its just fully locked down and finished but its worth a try
First try the MSMDownload tool with the very first stock Oxygen OS
Then re-lock the bootloader using Adb
I had the same problem and now its fine
LJAM96 said:
Hi, my phone has been dead for like 2 weeks now I even did a remote session in which they tried doing the MSMDownloadtool thing and it did nothing, no vibrations, black screen they just said its fully dead. fast forward to today it just started to react again.
When it tries to boot it boots straight to the OnePlus recovery mode and tells me to input a password, obviously I dont have one seen as its been set and if I click forget password it says it will format everything but it just turns off.
After a few boots I managed to get it to fastboot to realise the bootloader is now locked. the bootloader has always been unlocked since the first day I got it so it must of happened during the MSMDownloadTool process but the issue is now I cant unlock the bootloader because it says "remote: oem unlock is not allowed"
Any suggests that preferably not run MSMDownloadtool because thats been ran so many times already. Thanks
Essentially. No OS, Broken recovery, Locked bootloader and MSMDownloadTool doesnt seem to work. I imagine its just fully locked down and finished but its worth a try
Click to expand...
Click to collapse
I think that your only option is to try the MSM Download Tool. You may have to run it for a few times before it succeeds. I bricked my phone and recovered with the Mega Unbrick Guide (at first attempt). Following the instructions to the letter is most important.
Guys, I have a bricked bootloader locked phone that only goes to fastboot. I've already tried test point method. It recognized on PC but when I flash miui10 it takes like 222 seconds and it shows me an error saying "time out" error. It was almost done flashing! Is there how to save this device? I've also tried older miui versions and same thing. When I think it's getting there... Error! I need some help
Use xiaomitool.
Sergido said:
Use xiaomitool.
Click to expand...
Click to collapse
I've already tried too. There's no way to activate USB debugging. The phone only goes to fastboot.
Update: I got to flash with a beta version of XiaoMiFlash and it took 1200 seconds and it succeeded, but it did boot. Same thing
Ricardoqueiroz said:
Guys, I have a bricked bootloader locked phone that only goes to fastboot. I've already tried test point method. It recognized on PC but when I flash miui10 it takes like 222 seconds and it shows me an error saying "time out" error. It was almost done flashing! Is there how to save this device? I've also tried older miui versions and same thing. When I think it's getting there... Error! I need some help
Click to expand...
Click to collapse
try testpoint method or xiaomitool method in a different PC/ Laptop, with full driver. Best is Win 7.
Good luck.
It took some doing
Ricardoqueiroz said:
Guys, I have a bricked bootloader locked phone that only goes to fastboot. I've already tried test point method. It recognized on PC but when I flash miui10 it takes like 222 seconds and it shows me an error saying "time out" error. It was almost done flashing! Is there how to save this device? I've also tried older miui versions and same thing. When I think it's getting there... Error! I need some help
Click to expand...
Click to collapse
I tryed everything and had no success. Bootlooder locked after doing a factory data reset, and find device error when trying to boot.
In the end, I downloaded the very latest version of Mi Flash Pro miflash_pro-en-3.3.1212.88, one slightly older didn't work. I wrote the global ROM in recovery mode. It got stuck at 4.99% when I gave up watching it and after it rebooted it didn't work. I then did it again and it went through, much to my surprise. I then did a wipe date and for once, that also worked. Rebooted phone, set country and this time the phone was back Happy Days
use edl mode
Do this: fastboot boot 'last_boot_used_system.img'
Only do BOOT of lasted used boot.img in your phone!
I have a bricked Redmi Note 5 Pro. Stock firmware, locked bootloader, did literally nothing that would cause this. Just updated firmware (it happened few years ago, just now decided to try and repair it), and after update It's stuck in Mi-Recovery 3.0, with options only for "Reboot", "Wipe Data" and "Connect with MIAssistant", with red text at the bottom "This MIUI version can't be installed on this device" (see photo). Tried everything form this menu, nothing solves the problem. I can boot into fastboot but can't use it as the bootloader is locked and debugging is off. I can go into EDL mode but can't flash as I need to log in into Mi Account, and my sister (this phone was hers) forgot the password and even the account which was connected to this device. I was looking for MiFlash that bypasses authorization but can't find any that is not marked as malware (anyone knows of any that is safe?). At was past the warranty and I've tried to ask few phone-repair shops but the said that is unrepairable.
Any ideas what I can check or try next to solve this problem?
BTW. Does anyone knows why all of this happened? As I already said, never did anything with OS, only updated it which caused brick. My only idea is, as this phone was bought not from official store, that it might be a phone that was bought cheaper in china, then flashed with modified global OS and after update it was replaced with official global OS which bricked the phone. No idea if something like this is possible.
Edit [Sep 19, 2021]: I got somewhere. Used Firehose file to flash whyred global image without authenitcation. Got into system. I can at least go into fastboot and it's detected correctly in windows. Now I'm trying to get root, flash TWRP and any non-stock OS. Couldn't flash directly via fastboot because of anti-rollback check. Tried to do "fastboot boot twrp_rn5pro.img" which resulted in FAIL in console (status read failed - too many links) and "The system has been destroyed - click the power button to shutdown".
Edit2 [Sep 19, 2021]: Looks like my bootloader is still locked and that's why I can't flash custom recovery. But when I look in the phone settings it says that my phone is already unlocked. Checking in fastboot via PC says otherwise. Enabled OEM unlocking, but fastboot still says "FAILED (remote: Token Verify Failed, Reboot the device". Can't unlock it using MiUnlock cause they say that I need to set my account as available to unlock in unlock status on my device, but I can't do it as my device says that it's already unlocked.
Edit3 [Sep 20, 2021]: I've tried other tool: XiaoMiTool V2 (by Francesco Tescari). As the option "My device works normally I want to mod it" didn't work I chose "My device is bricked I want to unbrick it". Selected option without unlocking bootloader (wouldn't work). And it actually auto-detected that it's chinese phone and flashed chinese OS (MIUI 10.3 Stable). At the boot I got a prompt that this device is locked and I need to log into my Mi account (the one I logged in in the last ROM - from first Edit), after logging in it let me go through setup (luckily there was English). But phone still says that it's unlocked while it's still locked in fastboot. So in the end it didn't got me anywhere, but at least I know that orginally it was a chinese phone.
Edit4 [Sep 20, 2021]: Finally solved the problem! Used this tutorial. Did everything like shown on video and at the end I have MIUI 12 with unlocked bootloader (this time it's actually unlocked - checked with fastboot). Managed to flash TWRP using dummy.img and flashing to recovery. Couldn't boot from img, but vol+ + power did the job. With working recovery I can do everything else I wanted to do.
I had the same issue, which I also managed to fix. I thought I'd share what I did here.
My phone was bricked with access to MIUI recovery and Fastboot. My phone was locked, however my phone was not linked to my Mi account, and so I couldn't unlock it using the Mi Unlock tool. The only way to get into EDL mode was via the testpoint method. It's not as scary as people may think.
Many of the YouTube videos on testpoint show that you have to touch the two terminals while pushing the cable into the phone. Several times I was able to activate EDL mode without doing both at the same time - i.e. I could just connect the cable and touch the two terminals (I used a paper clip) and the phone would enter EDL mode. I think it might have had something to do with me pressing the power button. In my case, I had to have the battery disconnected from the circuit to get into EDL mode.
I used the Xiaomi Flash tool. Always remember to select not to relock the bootloader. I think it's stupid that relocking is the default option and that the radio buttons are at the bottom of the program and sometimes not visible on a laptop. That's how I got into this mess in the first place!
One of the things that I think causes the "MIUI version" problem is attempting to install the incorrect stock ROM. The phones may be fussy about which stock ROM they will accept. In my case, I thought the phone was a global version, then worked out that it was probably a Chinese version.
I replaced the firehose files in all the ROMs I attempted flashing with the ones supplied on XDA. The Xiaomi Flash tool reported success several times, but when starting up the phone it would go into recovery with the "MIUI version" message. I tried about six different MIUI ROMs with the testpoint method, both global and Chinese, before stumbling on the one that worked (after replacing the firehose files): whyred_images_V11.0.2.0.PEICNXM_20191023.0000.00_9.0_cn
When I got back into MIUI, I linked the phone to my MI account and then attempted flashing the latest LineageOS (which was what I was trying to do in the first place), using the Lineage recovery. The phone wasn't accepting the Lineage recovery, so I flashed OrangeFox-R11.0-Stable-whyred. I had to boot to Orangefox in order to flash it. You copy the Orangefox zip file to your phone using your computer when you have MIUI up and running, then you enter Fastboot and run the following command from your computer:
fastboot boot recovery.img
From Orangefox, you then select the Orangefox zip file on your phone and swipe to install.
Once that was done, I rebooted to recovery and did a wipe of the phone. It wasn't enough for me to wipe Dalvik/ ART Cache and Cache (as recommended), I had to also wipe System, Vendor and Data. (I tried just the first two and the LOS installation was corrupt, even though it was reported as being successful.) I then copied LOS to a micro SD card, inserted it into the phone and mounted it, before flashing LOS by navigating to the zip file on the SD card, selecting it and selecting wipe to install.
Finally success!
I think the key with the testpoint method is to keep trying ROMs until you stumble on the one that works. If the Xiaomi Flash tool reports success, I think it means you are doing something right. I also wonder if a lot of people who have the "MIUI version" issue have a phone with the Chinese ROM and don't realise it.
Hope this helped someone!
by any chances how do you unlock bootloader if you just bypass the mi account?
yoshukii19 said:
by any chances how do you unlock bootloader if you just bypass the mi account?
Click to expand...
Click to collapse
No hacking ... Why did you bypass mi account???
drnightshadow said:
No hacking ... Why did you bypass mi account???
Click to expand...
Click to collapse
the reason is I got my phone Redmi Note 5 Pro on fb marketplace by swapping my old phone, when I'm using it there's no mi account logged in on my phone then I tried to install the latest MIUI 12 by flashing it on MiFlash but I didn't notice that I didn't change the setting on clean all so it locked my bootloader, after I manage to fix the issue about my phone because it doesn't open and it only boot on recovery with a message "This MIUI...." and make it boot by flashing cn official rom, it says that my phone is locked and I need to logged in the old mi account, I already ask the previous owner but he said he doesn't have an access on that account, even the number and email are already lost
drnightshadow said:
No hacking ... Why did you bypass mi account???
Click to expand...
Click to collapse
If it's locked and you haven't registered the phone with Mi Account, then you will need to use test point. There are a lot of claims that it's not necessary, but I tried many of them and it wouldn't work. I think they are a load of rubbish to get you to pay money. Test point is not that hard, but you need to pick the right ROM.
Aurora333 said:
If it's locked and you haven't registered the phone with Mi Account, then you will need to use test point. There are a lot of claims that it's not necessary, but I tried many of them and it wouldn't work. I think they are a load of rubbish to get you to pay money. Test point is not that hard, but you need to pick the right ROM.
Click to expand...
Click to collapse
Why did you quote me?!?