After spending almost half a day trying to get my new Xiaomi Max into a usable state, I thought I'd share my findings for anyone else stuck in the same situation.
I recently bought a used Xiaomi Max from Taobao, the Chinese equivalent of Amazon. Things were going well until MiOS decided to update itself, and the phone rebooted only to say that this phone had been associated with a previous Xiaomi account and prompted me for the password. Of course, I had no idea what the previous password was, and the phone was stuck on setup until the correct password was entered just like when you setup a Google phone in China.
Since most Google servers are blocked by the Great Firewall of China, Google services will just keep saying "No Internet detected" and won't let you use the phone until some nice person decides to send you the address to a foreign proxy server that hasn't been blocked yet since VPNs don't work until *after* you can install them on the phone. Xiaomi phones apparently have the same thing, except that you have to track down whoever previously used this phone to register a Xiaomi account.
I tried a hard reset with the same result. Flashed a new Xiaomi ROM with the same result. Xiaomi locks the bootloader Apple-style to prevent anyone from using stolen phones. It also does a great job of preventing anyone from selling their phone or giving it to a friend. The locked bootloader prevented me from using fastboot to erase anything or install anything. Google provided a plethora of answers, all of which did absolutely nothing. Apparently, Xiaomi has fixed all of the security holes which were previously used to fix this problem. Good for them; bad for us.
Finally, I noticed that the Chinese and International MiOS had different recovery systems. Since this was being changed by the MiFlash program, it could only mean that somehow, MiFlash was capable of flashing system partitions even with a locked bootloader.
I downloaded TWRP, renamed it to recovery.img in the MiOS ROM, changed the MD5 checksum in the XML file, and gave the phone one more flash. The next time that it rebooted into recovery mode, I was staring at the TWRP logo instead of the Xiaomi recovery screen. From here, I could format /data to F2FS to gain the full 32GiB of space that the phone came with, install LineageOS, install Psiphon for a VPN, and then finally use TWRP to install OpenGApps. Voila! I had a fully usable phone without having to contact Xiaomi to unlock the bootloader, installing any strange Chinese software, or selling my firstborn child to Qualcomm.
I'd like to say that this method could probably be used on other Xiaomi phones as well, but considering that I have no other Xiaomi phones to test, I'll have to leave that task to the brave souls here in the forums. In any case, I hope that this will be of help to at least one other person and save them a couple of hours of trial and error as I have endured.
oh,please tell me which xml you modified with md5?
Hey there,
Sorry for the delay. I live in China currently, and it takes a VPN to get XDA to load correctly.
I can't remember the name of the XML file off the top of my head, but it was in the root directory of the ROM and contained all of the filenames as well as their MD5 values. All you have to do is to replace recovery.img's MD5 with TWRP's MD5 and you should be able to flash without any problems. Just make sure that you boot directly to recovery, otherwise the normal OS can detect that recovery has changed and flash the original recovery.
Please help me, I brought a Xiomi Max 2, from a second hand, when i started the phone it askes from its previously mi account, but the guy that sold me it, doent answer my e-mails anymore, what could i do?
The previous owner activated device protection, so you're locked out of the phone until he releases it. You'll have to install a custom ROM instead of MiUI to be able to use the phone.
If you made a credit card to purchase the phone, make sure that you submit a request to get your money back. There are too many scammers who steal and resell phones around here.
Just tried with mi6 glob 7.12,
and twrp 3.2.1 and changed md5sum.xml
but showing "the system has been destroyed"
Tried doing this one on Redmi Note 4/4X (Snapdragon). Flashed MIUI 10.2.3 Global Stable with TWRP 3.3.1-0. Replaced the stock recovery.img with the TWRP one and then replaced md5 in the md5sum. Power Button+Volume Up only shows a blank screen after Mi logo shows up. Tried to go on with the initial setup then boot into recovery via adb but only sent me back to stock recovery
Related
So yesterday, the beta for Fortnite on android came out and I obviously signed up immediately. I selected my device, signed up, and downloaded the installer which would not open. I did not do any research, but assumed that the problem had to do with xposed. I disabled xposed and sure enough, the installer opened, but now it said that my device was not compatible. After some research, i saw that the beta was only going to be for samsung devices for about 30 days so, naturally, i tried to figure out a way to circumvent this restriction. I thought back to my early android days and my spoofing of devices with build.prop and decided to replace some of the entries such as "ro.build.vendor", "ro.build.model", etc. with those from the Galaxy S9. After a quick reboot, it actually worked to my surprise. I was clearly excited at this point and spent about 45 minutes on mobile data downloading Fortnite and then downloading the game files. Finally, the game was downloaded, i was signed into my account, and I was waiting to join a Lobby. After entering a lobby and dropping out of the bus, I was descending towards tomato town to test out my favorite game on my favorite device when suddenly the loading screen came back up(this is where my luck took a turn for the worst). I was returned to the main menu and given a message along the lines of "Fortnite cannot be played on devices that do not pass safetynet, have an unlocked bootloader, or are rooted... Attempting to bypass this check may result in permanent account ban" At this point I began to get annoyed and figure that since I had come all this way I would just keep going. I went and turned on magisk hide from the magisk manager and set it to hide xposed. I then used the option to reinstall magisk under a different package name. I continued to enable exposed again and enable x privacy(I was planning on attempting to do exactly what i had been warned against by Fortnite). I then rebooted and... well, didn't reboot. I got stuck on the green RAZER circle for a bit then the screen just went black. After a few reboots i decided to restore my build.prop through TWRP. This didn't help at all so I decided to clear the cache and dalvik(this didnt work). At this point i decided to back up my photos and the Fortnite apk to my sd card and do a reset through TWRP. The reset did nothing so i figured I would try installing a custom ROM. I downloaded and installed resurrection remix. On the first boot i was greeted with the storage decryption prompt. I entered my password and it said that it was successfully decrypted but was corrupt and i had to factory reset. I pressed the button and the device went to the RAZER logo then turned off. I tried another boot tand the same thing happened so I went to TWRP manually and did yet another reset..... it failed. This is where i panicked. I went through twrp and did a bunch of **** like try to fix contexts and repair data until finally something succeeded and I was able to wipe data. From there I again booted into resurrection remix where it just hung on the boot gif. I plugged the phone into my pc and ran "adb logcat" and it said something about missing files in vendor. I then remembered that I had the RAZER factory images downloaded. I tried the flashall.bat and that just hung on the first command that was only supposed to push 44kb. I knew I had severely fluckled up at this point so seing as there was nothing else to lose I went back into twrp and tried to flash Resurrection again. After that succeeded and i pressed reboot on TWRP I was warned that no system image was installed. Remembering about the vendor thing from before, I pulled the stock vendor image and installed it through TWRP. I was going to flash all the images manually. I was unaware that flashing to vendor would remove TWRP so afte ra unwanted reboot, TWRP was gone for good. Since then, I have tried numerous things in download mode and am always met with messages such as "write failed {no error}", "a/b permissions not supported", "bootloader update required", and many moooore.
At this point I feel that all hope is lost but I feel that I have learned a valuable lesson and can be used as a perfect example of why you should think before you act. I would like to still ask for help from peers who are most likely infinitely more knowledgeable than I am. If you feel that you can help contribute to saving my baby(RAZER phone) in any way or you feel that this helped you in some way, don't hesitate to reply to this thread.
Thank you all for reading to this point and thank you in advance for any insight you have to offer.
Firstly, may I empathize with your pain, and I do need to say..."whooops". Maybe this can only be repaired from a RMA to Razer themselves. I'm not someone who roots his Android devices as I prefer them "as is" but I am a major Linux user and faff with those OSes till I break them. maybe contact Razer with the issue, maybe they can help. And again.....you have my sympathys.
Yeah, I'm going to wait a few days and see if either I can figure anything out or someone else can help me, but after that I will probably contact them. I just hope this doesn't end up being an expensive repair if it comes to sending an RMA. Thanks for your sympathy btw ???
I hate to say this, but today I finally got Fortnite installed and ready for use, totally officially, from epic games, and I'm now awaiting my email with my login access...yes, you may kick me, I will accept a virtual kick.
See, this hurts, it really does. I’m not going to virtually kick you though. I like to be kept in the loop on developments like this. ?
Just to make sure...did you try installing the stock image?
Why don't you just flash a fastboot image from MR1?
https://s3.amazonaws.com/cheryl-factory-images/cheryl-o-global-5038.zip
Yes I tried. That was the first thing I did when things started going south for the winter but it did not do anything. It kept giving the errors that i spoke of such as "unknown command" or "failed(no error)".
So without coming here first. I got my Fortnite invite, went through the install, jumped out of the bus and ...... then received the, you can't be rooted error message. #EPICfail
I haven't done anything else yet except close Fortnite. I'm now afraid to reboot for fear of ending up in the same position as @ShaneRagans. And I really feel like Epic Games should have announced that rooted phones wouldn't be compatible. Kinda pissed about it really.
lostnsound said:
So without coming here first. I got my Fortnite invite, went through the install, jumped out of the bus and ...... then received the, you can't be rooted error message. #EPICfail
I haven't done anything else yet except close Fortnite. I'm now afraid to reboot for fear of ending up in the same position as @ShaneRagans. And I really feel like Epic Games should have announced that rooted phones wouldn't be compatible. Kinda pissed about it really.
Click to expand...
Click to collapse
Did you do everything else the OP did, like changing build.prop? Or were you able to just install and attempt to play then it shut you out?
I received that same error message, but I'm not rooted, it seems the beta hasn't been properly coded to see changes in device status and architecture as ok. I also believe that epic games have bypassed the Google play store as they cannot guarantee the stability of the app and it would be seen by Google play store as defective. Maybe its something we need to wait for them to get fixed. Remember this is a "beta" version and is still in development.
lostnsound said:
So without coming here first. I got my Fortnite invite, went through the install, jumped out of the bus and ...... then received the, you can't be rooted error message. #EPICfail
I haven't done anything else yet except close Fortnite. I'm now afraid to reboot for fear of ending up in the same position as @ShaneRagans. And I really feel like Epic Games should have announced that rooted phones wouldn't be compatible. Kinda pissed about it really.
Click to expand...
Click to collapse
As long as you did not edit anything within your system, you should be fine. The game itself did not brick my phone, I bricked my phone because I was careless. I do however agree 100% that there should have been some sort of prior notice that rooted phones would not be compatible because it would have given me some time to do proper research on returning to stock before hand.
ShaneRagans said:
So yesterday, the beta for Fortnite on android came out and I obviously signed up immediately. I selected my device, signed up, and downloaded the installer which would not open. I did not do any research, but assumed that the problem had to do with xposed. I disabled xposed and sure enough, the installer opened, but now it said that my device was not compatible. After some research, i saw that the beta was only going to be for samsung devices for about 30 days so, naturally, i tried to figure out a way to circumvent this restriction. I thought back to my early android days and my spoofing of devices with build.prop and decided to replace some of the entries such as "ro.build.vendor", "ro.build.model", etc. with those from the Galaxy S9. After a quick reboot, it actually worked to my surprise. I was clearly excited at this point and spent about 45 minutes on mobile data downloading Fortnite and then downloading the game files. Finally, the game was downloaded, i was signed into my account, and I was waiting to join a Lobby. After entering a lobby and dropping out of the bus, I was descending towards tomato town to test out my favorite game on my favorite device when suddenly the loading screen came back up(this is where my luck took a turn for the worst). I was returned to the main menu and given a message along the lines of "Fortnite cannot be played on devices that do not pass safetynet, have an unlocked bootloader, or are rooted... Attempting to bypass this check may result in permanent account ban" At this point I began to get annoyed and figure that since I had come all this way I would just keep going. I went and turned on magisk hide from the magisk manager and set it to hide xposed. I then used the option to reinstall magisk under a different package name. I continued to enable exposed again and enable x privacy(I was planning on attempting to do exactly what i had been warned against by Fortnite). I then rebooted and... well, didn't reboot. I got stuck on the green RAZER circle for a bit then the screen just went black. After a few reboots i decided to restore my build.prop through TWRP. This didn't help at all so I decided to clear the cache and dalvik(this didnt work). At this point i decided to back up my photos and the Fortnite apk to my sd card and do a reset through TWRP. The reset did nothing so i figured I would try installing a custom ROM. I downloaded and installed resurrection remix. On the first boot i was greeted with the storage decryption prompt. I entered my password and it said that it was successfully decrypted but was corrupt and i had to factory reset. I pressed the button and the device went to the RAZER logo then turned off. I tried another boot tand the same thing happened so I went to TWRP manually and did yet another reset..... it failed. This is where i panicked. I went through twrp and did a bunch of **** like try to fix contexts and repair data until finally something succeeded and I was able to wipe data. From there I again booted into resurrection remix where it just hung on the boot gif. I plugged the phone into my pc and ran "adb logcat" and it said something about missing files in vendor. I then remembered that I had the RAZER factory images downloaded. I tried the flashall.bat and that just hung on the first command that was only supposed to push 44kb. I knew I had severely fluckled up at this point so seing as there was nothing else to lose I went back into twrp and tried to flash Resurrection again. After that succeeded and i pressed reboot on TWRP I was warned that no system image was installed. Remembering about the vendor thing from before, I pulled the stock vendor image and installed it through TWRP. I was going to flash all the images manually. I was unaware that flashing to vendor would remove TWRP so afte ra unwanted reboot, TWRP was gone for good. Since then, I have tried numerous things in download mode and am always met with messages such as "write failed {no error}", "a/b permissions not supported", "bootloader update required", and many moooore.
At this point I feel that all hope is lost but I feel that I have learned a valuable lesson and can be used as a perfect example of why you should think before you act. I would like to still ask for help from peers who are most likely infinitely more knowledgeable than I am. If you feel that you can help contribute to saving my baby(RAZER phone) in any way or you feel that this helped you in some way, don't hesitate to reply to this thread.
Thank you all for reading to this point and thank you in advance for any insight you have to offer.
Click to expand...
Click to collapse
I feel your pain i locked me bootloader and bricked my phone crying atm
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
i tried many thing as well but if your bootloader is unlocked try use the 7.1.1 ver and add -i 0x1532 to the command
btw anyone wanna buy a paper for lol
Do any of you guys that bricked your phones happen to have 3 rescue?
It costs £100 but you'll get a new phone next day no questions asked.
I did this when I bricked my Samsung galaxy S6 edge+ last year.
It's expensive, but surely better than having a £500 paper weight.
Just wanted to let everyone know that Razer repaired it for $15.
Ugh, this phone has been a hot mess for me here in the US.
TWRP never seems to stay more than one time I use it, but any ways, once I get into TWRP it asks me to decrypt the data partition. I got this with the 9.6.4.0 global rom and unlocked. Are they encrypting the phones too before they ship them?
Anyone run across this and know what the decryption password is?
Every official MIUI rom force encrypts userdata. There is no password per say, it's a hardware generated key and unique for any single device. If TWRP for Max 3 wasn't buggy it would decrypt it without you even noticed it...
So reading and reading here I keep asking myself is anybody testing anything he builds before sharing it here...!?
nijel8 said:
Every official MIUI rom force encrypts userdata. There is no password per say, it's a hardware generated key and unique for any single device. If TWRP for Max 3 wasn't buggy it would decrypt it without you even noticed it...
So reading and reading here I keep asking myself is anybody testing anything he builds before sharing it here...!?
Click to expand...
Click to collapse
No-one ever managed to create a TWRP for Mi Mix 1 lithium that handled encryption correctly.
Having followed raupes attempts at Mix1, from a safe distance, I can appreciate the difficulties.
Don't know about Max3, if it has any peculiarities?
omniphil said:
Ugh, this phone has been a hot mess for me here in the US.
TWRP never seems to stay more than one time I use it, but any ways, once I get into TWRP it asks me to decrypt the data partition. I got this with the 9.6.4.0 global rom and unlocked. Are they encrypting the phones too before they ship them?
Anyone run across this and know what the decryption password is?
Click to expand...
Click to collapse
I did came across yday: https://forum.xda-developers.com/mi-max-3/how-to/news-mi-max-3-global-rom-t3825700/page30
Wasn't a pleasant surprise. Just like you I couldn't decrypt it. At the end I did wipe the storage which bricked my phone. It was a long way to get it back to life. I don't recommend wiping it. Apparently there are steps you would need to do if you wish to install EU or other roms. A user called "dogiex" shared it and you can see on the above link. Good luck...
nijel8 said:
Every official MIUI rom force encrypts userdata. There is no password per say, it's a hardware generated key and unique for any single device. If TWRP for Max 3 wasn't buggy it would decrypt it without you even noticed it...
So reading and reading here I keep asking myself is anybody testing anything he builds before sharing it here...!?
Click to expand...
Click to collapse
When i finally got the phone up and running again, I did notice it encrypting again. Sigh...
At least the phone is working again, I just cannot get AT&T to get it working on their network.
this did not work for me at all, but it didn't hard-brick my device either. It just kept failing. I'm guessing it would have worked if I wasn't on Miui 11.0.6 after a forced update (but that forced update is what caused me to lose root!)
On the other hand, having lost root on my Redmi Note 5 (redmi note 5 pro in india), I was saved by a custom TWRP desiged to decrypt whyred which worked a treat. I would love to credit the developer who tweaked it but I only have the file name which was reposted in XDA: fx_TWRP_Pie_whyred.img
Brilliant ... but my Whyred was still on some version of Miui 10. This is the md5: e9b9484ab6cb624a98df7954cb526bd1
This is the link: https://androidfilehost.com/?w=files&flid=295272&sort_by=date&sort_dir=DESC (posted on the off chance that the method used might somehow be adapted for the Mi Max 3 by one of you whizzes).
Many thanks for your efforts and patience!
Honestly, I try, but Miui updates are just too much for my tiny brain. My last three devices have been Xiaomi but as it stands now I will never buy another.
I wish I could just buy an unlocked, rooted device already loaded LineageOS.
.
rodagola said:
Hello everyone on xda, please bare with me. Here's my story
I own a Redmi Note 8 pro, chinese rom model. It was running miui 11.0.3 over android 9 If I recall correctly.
Ok so... I was tired of some of the china apps pushing their notifications over and over and auto installing stuff, so I looked up how to apply adb commands to remove such bloatware, which was a fairly simple process. I copied and pasted a list of safe stuff to delete I found around some forums.
then... there were some other packages I checked out using an app called "app inspector", which directly tells you which app is under which package (totally useful for this purpose).
I tried to be careful not go overboard since I don't have any root access, or custom recovery, and wasn't really planning to have these, just wanted to keep this as my simple daily driver cellphone, but also perform this little maneuver to get rid of some bloatware.
little did I know, I was about to somehow softbrick it. More info: I did not use a screen lock method other than the "swipe up".
Ok, so I uninstalled some packages I cannot remember exactly how they went, but they had the terms "xman" and "yman" on them I think, I wasn't so sure about them because I looked them up on the web yet they didn't appear anywhere. I think they went something among the lines of "com.android.miui.xman". I also uninstalled 2 or 3 more, but after googling, they seemed unsuspecting.
Anyways, I'm aware there's a command to reinstall the packages because they're still on the phone's ROM image. That is in case I had to restore anything back to normal. Turns out I later rebooted the phone and when it launches the lock screen, I keep swiping up but it won't take me over to the actual MIUI launcher. The screen is frozen on the lock screen.
I'm not freaking out at this time because I still tried to connect the device to the pc, and it still shows as connected, I then go to the adb console and type "adb devices", it is still recognized, however, it says next to it that it is unauthorized... damn it. So now I might not be able to run the commands that allow me to reinstall the exact packages that are rendering the phone softbricked (I guess), plus I'm not really sure which package caused this.
After about a minute or two on the lock screen, the phone takes me to the "redmi-recovery 3.0",
which displays 3 options:
Reboot to system: which basically forms a loop
Wipe date: godforbid... really don't want to do it since I likely had many files not backedup
Contact miassistant: not sure what to do with this, says "pcsuite.mi.com" at the bottom
on the miassistant option you can apparently sideload stuff, idk how to go about this, maybe it allows me to install a slightly upgraded ROM, which in turn will work the same as if it was an OTA update (so it will keep my data as it was instead of wipe)? Because the point is not to erase my user data!!
I'm not sure how to feel or what to do without losing my pictures, notes and documents
I have hopes this situation can be turned around back to normal, and like the title implies... I'm WILLING to PAY you through paypal or something to WHOEVER offers to guide me through in the best way possible. Please if you have the knowledge/experience don't hesitate I'll also be grateful timelessly.
I'm not an expert at these scenarios so I might as well ask on xda where most are really skilled! Thanks in advance to those amazing souls
Click to expand...
Click to collapse
tldr;
If you can boot into fastboot mode you can just flash a official MIUI fastboot ROM:
Xiaomi Firmware Updater (where you can download official MIUI ROMS): https://xiaomifirmwareupdater.com/
This is the current hard unbrick method: https://telegra.ph/Installing-Redmi-Note-8-Pro-firmware-via-SP-Flash-Tool-01-21
It should also work in your case and there's even a video guide.
This is another video guide for fixing a hard brick:
Both methods above will format your phone though (afaik all data will be lost).
Compass.
.
rodagola said:
are these the kind of roms that you unzip and have the BL, AP, CP, CSC files? I could try that, but I've heard installing home_csc will not override/wipe my personal data. If this is what you meant, can you confirm? Or do you reckon these linked video tutorials would not wipe the data?
Click to expand...
Click to collapse
Nope, it doesn't.
If you can boot into Fastboot, flash the ROM using Mi Flash, otherwise, use this tutorial:
.
Compass Linux and juliusjr have told you the method, so I will just add supplemential infos.
In your case, I think simple upgrade will do the trick, dirty flash is applicable both via fastboot flash (mi flash) and recovery flash (the mi assistant method). If you want to stop the ads, I will recommend you to unlock your bootloader, move to global, root, and use an adblocker (a bare minimum config, in trade of some bangking apps being blocked).
I don't know the corresponding version for miui china rom, but in global rom, prior 12.0.0.7 (the one with the early 2021 security update), you can dirty flash back and forth while keeping your data.
.
rodagola said:
Hi, thanks for your info, I would like to try the mi flash tool as I've been told before the stock recovery thing has less chances of working. However, I had dev options turned on before but didn't manage to turn on the "OEM unlock" option, will flashing original ROMs work this way? or did I need that option toogled on? That's my last doubt, and thanks a lot. Btw, the China ROM this Redmi N8P had never ever showed me any ads, but thanks a lot as well for such input
Click to expand...
Click to collapse
You still have a locked bootloader? (How do I know? You will see "Unloked" on the bottom of the screen everytime your device reboots and showing mi logo if your device is unlocked)
Hmm, mechanically it work like normal ota update. Full recovery update will ony erase nessesary partitions (system, boot, and some other things) while keeping your data intact. So doing this to your phone technically safe. You can do this with MiFlashPro, do a recovery update using a recovery rom (the 2 gigs one) greater than your current MIUI version. But please bear in mind that I have never done this before to a locked phone. A same distribution version IS A MUST (i.e. global with global).
Oh and it will need you to log in to your xiaomi account. My guess is you need the flash permission open for your account (if you have unlocked your phone you shouldn't have a problem). I have never flashed with an account that never have been used to unlock a bootloader, so I might be wrong.
If your phone is bootloader unlocked, Mi Flash is the least demanding and it can retain your data with "save user data" in the bottom right corner option on, regardless your miui version (but I think there will be some problem with installed apps if you downgrade from A10 to A9).
Hope this help.
Hello everyone! I hope someone here will be able to help me.
I purchased a new Mi Mix 2 in 2018, and last year I decided to upgrade its ROM to LineageOS. I changed ROMs in the past on other phones so I felt familiar with the process, but this time I made a mistake, and wiped the phone from the stock recovery BEFORE logging out of my old MI account. On restart, the phone now asks me for the account password to proceed.
Unfortunately I don't have access to the Mi account anymore. In fact, I only activated it once with a dummy email, so that MIUI would not bother me every time, and then forgot about it. I did not expect it to still be there after a phone reset.
Now, the login screen on the phone doesn't even give me complete information on which email (or Mi account number) it is set on, so I have no way to trace those back and try to reset the access credentials.
I don't know where that account data is stored on the phone, I wonder if it can be reset somehow? I am a software dev, so don't be afraid of being technical. Some sources I found say it is in a sort of separate partition, but I am afraid it could be in the on-chip keystore instead? Furthermore, I found out about the EDL mode on Qualcomm chips, which seems to be effectively a first-stage bootloader which could be used to access the phone data. Using `fastboot oem edl` however I get a `FAILED (remote: 'Oem edl command is not allowed Lock State')` response, which is quite self-explanatory.
Has anyone tackled this situation before? Is there any hope of recovering my Mi Mix 2?
Thanks to anyone willing to give a hand
Hi all,
I am hoping to get some help from you all. My son owns Redmi Nore 8 Pro 6/128 purchased from online mi shop here in UK (I have a proof of purchase if needed). Recently it started playing around with some apps and I decided to Factory Reset it. He created a mi account and of course forgot the password. Knowing little about Redmi's security measures I decided to wipe it from the recovery level (remembered some basic stuff from my time when I was flashing my Xperia Arc). Unfortunately the phone now boots into a lock screen on wehich I am stuck. Here is what I ahve tried:
1. Reset password on mi cloud, used the new password to unlocke the phone but the phone is not accepting it
2. Removed Note 8 Pro from mi cloud, wipe it again - still not accepting the password and showing the locked screen,
3. I used the recovery code on i.mi.com but I ahve note heard back from anyone for a wekk now.
Regards
michalcieslik said:
Hi all,
I am hoping to get some help from you all. My son owns Redmi Nore 8 Pro 6/128 purchased from online mi shop here in UK (I have a proof of purchase if needed). Recently it started playing around with some apps and I decided to Factory Reset it. He created a mi account and of course forgot the password. Knowing little about Redmi's security measures I decided to wipe it from the recovery level (remembered some basic stuff from my time when I was flashing my Xperia Arc). Unfortunately the phone now boots into a lock screen on wehich I am stuck. Here is what I ahve tried:
1. Reset password on mi cloud, used the new password to unlocke the phone but the phone is not accepting it
2. Removed Note 8 Pro from mi cloud, wipe it again - still not accepting the password and showing the locked screen,
3. I used the recovery code on i.mi.com but I ahve note heard back from anyone for a wekk now.
Regards
Click to expand...
Click to collapse
You need to choose option 2 and connect your wifi. Then use option 1 to login your Xiaomi account.
If everything you did and nothing change, you can start thinking about using custom rom (Even if your device still in lock status, just need for more skill)
You can also buy/hire to bypass Mi Account from shop. But Miui version can't be change or update or reset,... Or else it will be locked again
You can skip the hassle and custom rom it just unlock the bootloader from mtk bootloader unlock flash a custom twrp recovery from fastboot and install a rom, much debloated than stock anyways. I recommend crdroid by timjosten if you still would like stock reply and maybe we can figure out a solution