So I dropped my phone and shattered the screen a few days ago. Just today a section of the screen failed that prevented me from unlocking the device with my pattern. Like an idiot, I kept trying to obtain the pattern unlock, but ultimately failed and now the phone is forcing me to unlock it by signing into the Google account associated with the phone. Unfortunately that only works if you have a Wifi or data connection, which I DON'T have because I had it in Airplane mode when the digitizer died.
So what are my options here? The phone DOES have an unlocked bootloader, as I loaded the Mexican ROM a while back to replace the stock U.S. one. When I boot up to Fastboot mode, it says unlocked status 3, and I can successfully see the device by using the "fastmode devices" mode. However, I cannot access the device via ADB because I didn't have USB debugging turned on.
I'm not all that familiar with Android recovery options and would just like to see if I can get into my device without having to wipe it. Ideally all I want to do is either:
A.) Somehow turn on Wifi so I can unlock the device by signing into google (I can connect a keyboard up to the phone to type in my credentials)
B.) Somehow turn on USB debugging so I can use ADB to then clear the password or turn on wifi, etc
Help!
Farfolomew said:
So I dropped my phone and shattered the screen a few days ago. Just today a section of the screen failed that prevented me from unlocking the device with my pattern. Like an idiot, I kept trying to obtain the pattern unlock, but ultimately failed and now the phone is forcing me to unlock it by signing into the Google account associated with the phone. Unfortunately that only works if you have a Wifi or data connection, which I DON'T have because I had it in Airplane mode when the digitizer died.
So what are my options here? The phone DOES have an unlocked bootloader, as I loaded the Mexican ROM a while back to replace the stock U.S. one. When I boot up to Fastboot mode, it says unlocked status 3, and I can successfully see the device by using the "fastmode devices" mode. However, I cannot access the device via ADB because I didn't have USB debugging turned on.
I'm not all that familiar with Android recovery options and would just like to see if I can get into my device without having to wipe it. Ideally all I want to do is either:
A.) Somehow turn on Wifi so I can unlock the device by signing into google (I can connect a keyboard up to the phone to type in my credentials)
B.) Somehow turn on USB debugging so I can use ADB to then clear the password or turn on wifi, etc
Help!
Click to expand...
Click to collapse
When you hold down the power button at the lockscreen, isn't there an option to turn on/off airplane mode?
TheCrazyDirectioner said:
When you hold down the power button at the lockscreen, isn't there an option to turn on/off airplane mode?
Click to expand...
Click to collapse
Huh I can't believe I didn't see that option. Unfortunately, I also had my data connection turned off as well, so simply turning off airplane mode is not sufficient.
I tried to load CWM recovery using the fastmode flash recovery cmd, thinking it would give me some sort of ADB access, but it errored out with a "remote failure" error. I'm not even sure that recovery would have let me disable the pattern lock anyways.
Thanks for the help!
Farfolomew said:
So I dropped my phone and shattered the screen a few days ago. Just today a section of the screen failed that prevented me from unlocking the device with my pattern. Like an idiot, I kept trying to obtain the pattern unlock, but ultimately failed and now the phone is forcing me to unlock it by signing into the Google account associated with the phone. Unfortunately that only works if you have a Wifi or data connection, which I DON'T have because I had it in Airplane mode when the digitizer died.
So what are my options here? The phone DOES have an unlocked bootloader, as I loaded the Mexican ROM a while back to replace the stock U.S. one. When I boot up to Fastboot mode, it says unlocked status 3, and I can successfully see the device by using the "fastmode devices" mode. However, I cannot access the device via ADB because I didn't have USB debugging turned on.
I'm not all that familiar with Android recovery options and would just like to see if I can get into my device without having to wipe it. Ideally all I want to do is either:
A.) Somehow turn on Wifi so I can unlock the device by signing into google (I can connect a keyboard up to the phone to type in my credentials)
B.) Somehow turn on USB debugging so I can use ADB to then clear the password or turn on wifi, etc
Help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=201566226
That link doesn't help me at all, since I can't unlock the phone to turn on USB debugging, nor would I even be able to unlock it even if I could control it remotely.
But anyways, great news to report! I was able to eventually load the Clockwork mod (CWM) as the recovery partition in fastboot mode. The problem earlier trying to flash CWM was that the phone's battery was too low and it threw a vague "remote failure" error. After charging it up to 100% the flash worked fine. After that, I rebooted into CWM and then flashed the Aroma file manager zip (using method VII on this page: http :// en. miui. com /thread-5684-1-1 . html) , and managed to delete the password and gesture key files, and voila! after restarting my phone I was in! Wooo!
So obviously I was only able to do this because my phone was previously rooted with bootloader unlocked. If that weren't the case (ie, default from the factory), then the only option would have been to wipe the device.
Farfolomew said:
That link doesn't help me at all, since I can't unlock the phone to turn on USB debugging, nor would I even be able to unlock it even if I could control it remotely.
But anyways, great news to report! I was able to eventually load the Clockwork mod (CWM) as the recovery partition in fastboot mode. The problem earlier trying to flash CWM was that the phone's battery was too low and it threw a vague "remote failure" error. After charging it up to 100% the flash worked fine. After that, I rebooted into CWM and then flashed the Aroma file manager zip (using method VII on this page: http :// en. miui. com /thread-5684-1-1 . html) , and managed to delete the password and gesture key files, and voila! after restarting my phone I was in! Wooo!
So obviously I was only able to do this because my phone was previously rooted with bootloader unlocked. If that weren't the case (ie, default from the factory), then the only option would have been to wipe the device.
Click to expand...
Click to collapse
why dont you take an HDMI cable then connect it to a TV or screen then you can see everything
Mine screen was broken some moths ago and I did this to use phone before new screen replacement came. Maybe it can help you.
devilsking said:
why dont you take an HDMI cable then connect it to a TV or screen then you can see everything
Mine screen was broken some moths ago and I did this to use phone before new screen replacement came. Maybe it can help you.
Click to expand...
Click to collapse
Yes, I should have immediately stopped trying to pattern-unlock it with the broke screen and waited until I could have hooked up my mouse. I didn't know it would lock me out of the pattern-unlock method after so many tries and force me to unlock using google signin. Also, with the google sign in, I assumed it used cached credentials, but it does not. It requires an active data or wifi connection to verify. Neither of those were turned on, nor could I turn them on. The only option I had was to get in there using a Recovery ROM and remove the password key files. I guess the moral of this story is don't be an idiot and absolutely try to get into your phone right away, when there are plenty of other ways to get in even if hte screen is completely broke (like you said with HDMI cable, keyboard, mouse, etc)
Also, I had a "fun" little issue after that where I tried to edit the build.props file to enable home screen rotation, but that ended up crashing the OS and I had to use fastboot to flash just the system.img that was from the stock Mexican 4.1.2 ROM. So now, I just downloaded an app that allows me to rotate my device, and thus allow me to avoid the dead part of the digitizer when I need to.
So this morning i tried this. Kingroot didn't complete the root, some error happened, i didn't mind since i was just testing to see if i could root my phone for the first time [i've never done it before and it seemed simple enough].
I quit the app, a bunch of errors showed up, one after the other [i didn't register what exactly the windows said, i'm pretty sure it was a google application that stopped working]. The phone turned itself off.
i booted it up again, and it showed me the AP Fastboot Flash Mode screen. i know this from previously doing a factory reset, so i tried doing it again. After it wiped all of my data and custom, i tried rebooting it.
it showed me the motorola icon, but a few seconds later, i was back at the fastboot screen. i'm pretty desperate right now since this is my only phone. i tried selecting the "normal powerup" command, it didn't work. this is my screen right now:
"hab check failed for boot
failed to validate boot image
fastboot reason: fall-through from normal boot mode
USB conected
hab check failed for boot
failed to validate boot image
boot up failed"
none of the other commands, aside from Recovery, work. it takes me to the no command screen and all of the known options once i use the power+volume up command: reboot system now, reboot to bootloader, apply update from ABD, etc.
sorry if this thread reads weird, i'm sort of freaking out right now and english isn't my main language. thanks in advance to anyone who might help!
Check here
If you have questions PM me I will try to help. I got the same problem on Monday and solved it yesterday.
Hello
I recently got my mi5 after ordering from aliexpress and not a big fan of MIUI and wanting the cyanogenmod experience I applied for opening up the bootloader.
Today I recieved message that the request was granted and i happily started the progress with opening up the bootloader via the miflashunlock tool.
When I used the tool it gave me a message in lines of "No need to unlock this device" So i thought " Ok, maybe the seller had to unlock the bootloader to flash the global ROM or whatever.
I proceeed to flash TWRP and it flashed fine, so my bootloader must obviously have been open all the time?
Then I did a full wipe, instralled CM13 and opengapps and rebooted.
Now the trouble started.
All I boot into is a black screen, nothing happens.
If I try to boot into recovery I get a black screen.
I CAN boot to fastboot
So i go back to fastboot to check bootloader status.
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
How can this happen? How the hell can flashing CM lock my bootloader? I never checked the bootloader in fastboot before this, but since I was able to flash TWRP I must have had an open bootloader.
I have tried to flash different ROMS via the MiFlash tool and it gives me message that the devices is locked (duh!)
I have tried to open the bootloader via the unlock tool but it says that the currenct account is different from the account info on the device. Not very strange since I installed CM13...
I have tried to both flash and boot into TWRP via fastboot but I can't do this since device is locked...
Is my only option to try this
http://en.miui.com/thread-299790-1-1.html
Or can i just throw the phone in the bin after three days and buy a new phone from another company that values openess a little more?
---------------
Booting to EDL-mode with this suggestion:
http://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
After this you can flash whatever rom you like with the miflash tool
I still end up in the same situation when trying to flash CM13
Phone boots to black screen, I boot back to fastboot and phone is locked gain.
But this is something I can try to figure out on my own
Just an update so if anyone else who ends up in my situation searches forums they might find answer here.
Every time i flash CM13 the same thing happens. Bootloader gets locked and phone can only start in fastboot.
I tried installing RessurectionRemix instead and it worked straight away.
Why the hell this happens I have no clue, but this some of you geniouses maybe knows.
Right now I really don't care since RR works just fine for me
any solution ? I have the same problem
I bought a second hand lavender and want to share my adventure so far trying to unlock from mi cloud. I will update this post when something changes.
- Mi cloud is locked with another account
- bootloader is locked
- oem unlock status is unknown
- Mi recovery mode is possible (from there you only can wipe data, connect to mi cloud or reboot)
- fastboot is possible (from there you can reboot and read some phone vars)
- booting to system is possible but the lock screen only lets you connect to wifi and unlock via account
- miui 11 seems to be installed (you see it sometimes behind the lock screen)
- adb is disabled
- The former owner doesn't know the credentials (he says he got it from another person and lost the password.. who knows..)
- Xiaomi doesn't want to help (if the phone was stolen I would give it back for free, else they should please unlock, but they don't want to..)
- Local police can't help (IMEI is unknown, only parts of the phone number are known from the lock screen but they can't search for it)
- codes like *#06# don't work with emergency call in lock screen
- 'Check "Find device" status' on mi.com after entering the lock number (tap several times in the lock icon) says that the status is enabled
- I have no chance to find out who enabled it (maybe when I have the IMEI, local police can help). IMEI might have been changed already..
- I don't want to open the phone case yet
If someone knows a shortcut to my tries, please let me know!
the lock screen
With miui 11 it seems not possible to circumvent the lockscreen with any method I found in the net (pressing volume buttons, add network, switch between wifi and lock screen).
You can only connect to existing networks. 'Add network' switches back to lock screen immediately.
fastboot
You can read variables via 'fastboot getvars all'. You may need the info that the current rom has ARB4. I will try to flash the lowest possible version with ARB4. From mi.com I found global rom V10.2.7.0.PFGMIXM to have ARB4.
(bootloader) crc:1
(bootloader) anti:4
(bootloader) DP:0x0
(bootloader) token: ......
(bootloader) hw-revision:10000
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4338
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
...
(bootloader) partition-type:vendor:raw
...
(bootloader) secure:yes
(bootloader) serialno:...
(bootloader) product:lavender
(bootloader) kernel:uefi
test point
Finally the cable worked, so probably no need to open the phone
deep flash cable
I soldered a deep flash cable with a button. Please don't try without button, the effort is worth it. Or buy a cable for some bucks.
Test it for example in fastboot: press the button and fastboot doesn't work
switching off phone
Is not that easy or not possible via buttons and fastboot has no shutdown mode.
I found that waiting some minutes in fastboot mode with disconnected cable switches the phone off
(actually from there you can go nowhere, as the battery must be empty or disconnected)
(not) switching to EDL mode with battery (at least not empty battery)
In Windows I installed Qualcomm drivers (64bit exe package), it reboots and Windows is in 'test mode' then because of test certificates.
So far, when fastboot shuts down the phone, I am in 'Mass Storage' mode.
From there I tried to go into EDL mode via cable in 2 variants: pressing button, then plug in phone first and plug in PC first.
Windows device manager and linux see the same 05c6:f000 device, which seems to be some modem (for LTE-Sticks,..) according to net.
QFIL and QPST don't see anything.
Trying things found in the net:
- USB 2.0 only (already tested with USB2 hub and Raspberry USB2 port) / edit: eventually USB3 worked fine
- Wait x seconds (all possible x tested, it's always the charging mode) / edit: yes, you have to wait some seconds, but that doesn't help with 'charging mode'
- 'when charging mode appears, try again' or so.. well.. yes / edit: retrying doesn't seem to help getting out of 'charging mode'
- 'EDL timeout', 'hello packet': I think, that doesn't apply in my current state, there should be some xxxx:9008 device first
- 'only works when battery disconnected' or when battery is empty (because of EDL timeout or so) / edit: for me it really only works this way
- usb_modeswitch isn't able to switch from f000 to some other mode.
Finally, after draining the battery, it worked!
draining the battery
- flood pinging the phone (no ports open)
- USB-OTG stick on the phone
- Keep display active (tap on your connected wifi, the 'Share Wi-Fi network' window doesn't deactivate screen, also it seems to be the brightest level)
switching to EDL mode with empty battery
The phone shut down and I retried with the cable.
When the battery is too empty, the led is blinking. Wait some seconds or a minute until the screen turns on and shows loading icon, then try again. The led should turn off and the phone seems dead.
The phone is in 9008 now and actually seems to stay there even when pressing power button or reconnecting USB.
ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
If the battery is too empty, charge it until it tries to start system. Then disconnect charger and try to switch mode.
I found that _only_ via "draining the battery" it is possible to get to the 9008 mode. Pressing power button, even with already empty battery does not work. While draining, android tries to shut down the phone (which could lead to non-9008 mode). As Xiaomi has locked the shutdown (it wrote "Can't power off, the device is locked" sometimes..) it can happily drain.
When you leave 9008 mode, you have to charge until system starts and then drain again.
Further, there seems to be some other mode, which "edl.py" recognizes as "memory dump mode". The USB ID is correct, but EDL commands are not possible.
Interestingly, I have no problems with the second hand device but my other lavender device bought from a..zon returns "Only nop and sig tag can be recevied before authentication" when trying, for example, "edl.py --loader=prog_emmc_firehose_Sdm660_ddr.mbn printgpt". As both should have the same PBL, I don't yet understand it..
There seems to be some timeout (seconds..) when switching to EDL mode, after that no commands are accepted.
I will stop here, as there are already tutorials how to unlock the mi lock in EDL mode and currently I don't want to just reflash via QFIL or QPST. I'm trying some reverse engineering meanwhile.
I can help you pm me ?
Sent from my Xiaomi Redmi Note 7 using XDA Labs
meeep said:
I bought a second hand lavender and want to share my adventure so far trying to unlock from mi cloud. I will update this post when something changes.
- Mi cloud is locked with another account
- bootloader is locked
- oem unlock status is unknown
- Mi recovery mode is possible (from there you only can wipe data, connect to mi cloud or reboot)
- fastboot is possible (from there you can reboot and read some phone vars)
- booting to system is possible but the lock screen only lets you connect to wifi and unlock via account
- miui 11 seems to be installed (you see it sometimes behind the lock screen)
- adb is disabled
- The former owner doesn't know the credentials (he says he got it from another person and lost the password.. who knows..)
- Xiaomi doesn't want to help (if the phone was stolen I would give it back for free, else they should please unlock, but they don't want to..)
- Local police can't help (IMEI is unknown, only parts of the phone number are known from the lock screen but they can't search for it)
- codes like *#06# don't work with emergency call in lock screen
- 'Check "Find device" status' on mi.com after entering the lock number (tap several times in the lock icon) says that the status is enabled
- I have no chance to find out who enabled it (maybe when I have the IMEI, local police can help). IMEI might have been changed already..
- I don't want to open the phone case yet
If someone knows a shortcut to my tries, please let me know!
the lock screen
With miui 11 it seems not possible to circumvent the lockscreen with any method I found in the net (pressing volume buttons, add network, switch between wifi and lock screen).
You can only connect to existing networks. 'Add network' switches back to lock screen immediately.
fastboot
You can read variables via 'fastboot getvars all'. You may need the info that the current rom has ARB4. I will try to flash the lowest possible version with ARB4. From mi.com I found global rom V10.2.7.0.PFGMIXM to have ARB4.
(bootloader) crc:1
(bootloader) anti:4
(bootloader) DP:0x0
(bootloader) token: ......
(bootloader) hw-revision:10000
(bootloader) unlocked:no
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:4338
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) erase-block-size: 0x200
(bootloader) logical-block-size: 0x200
(bootloader) variant:SDM EMMC
(bootloader) partition-type:userdata:ext4
...
(bootloader) partition-type:vendor:raw
...
(bootloader) secure:yes
(bootloader) serialno:...
(bootloader) product:lavender
(bootloader) kernel:uefi
test point
Finally the cable worked, so probably no need to open the phone
deep flash cable
I soldered a deep flash cable with a button. Please don't try without button, the effort is worth it. Or buy a cable for some bucks.
Test it for example in fastboot: press the button and fastboot doesn't work
switching off phone
Is not that easy or not possible via buttons and fastboot has no shutdown mode.
I found that waiting some minutes in fastboot mode with disconnected cable switches the phone off
(actually from there you can go nowhere, as the battery must be empty or disconnected)
(not) switching to EDL mode with battery (at least not empty battery)
In Windows I installed Qualcomm drivers (64bit exe package), it reboots and Windows is in 'test mode' then because of test certificates.
So far, when fastboot shuts down the phone, I am in 'Mass Storage' mode.
From there I tried to go into EDL mode via cable in 2 variants: pressing button, then plug in phone first and plug in PC first.
Windows device manager and linux see the same 05c6:f000 device, which seems to be some modem (for LTE-Sticks,..) according to net.
QFIL and QPST don't see anything.
Trying things found in the net:
- USB 2.0 only (already tested with USB2 hub and Raspberry USB2 port) / edit: eventually USB3 worked fine
- Wait x seconds (all possible x tested, it's always the charging mode) / edit: yes, you have to wait some seconds, but that doesn't help with 'charging mode'
- 'when charging mode appears, try again' or so.. well.. yes / edit: retrying doesn't seem to help getting out of 'charging mode'
- 'EDL timeout', 'hello packet': I think, that doesn't apply in my current state, there should be some xxxx:9008 device first
- 'only works when battery disconnected' or when battery is empty (because of EDL timeout or so) / edit: for me it really only works this way
- usb_modeswitch isn't able to switch from f000 to some other mode.
Finally, after draining the battery, it worked!
draining the battery
- flood pinging the phone (no ports open)
- USB-OTG stick on the phone
- Keep display active (tap on your connected wifi, the 'Share Wi-Fi network' window doesn't deactivate screen, also it seems to be the brightest level)
switching to EDL mode with empty battery
The phone shut down and I retried with the cable.
When the battery is too empty, the led is blinking. Wait some seconds or a minute until the screen turns on and shows loading icon, then try again. The led should turn off and the phone seems dead.
The phone is in 9008 now and actually seems to stay there even when pressing power button or reconnecting USB.
ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
If the battery is too empty, charge it until it tries to start system. Then disconnect charger and try to switch mode.
I found that _only_ via "draining the battery" it is possible to get to the 9008 mode. Pressing power button, even with already empty battery does not work. While draining, android tries to shut down the phone (which could lead to non-9008 mode). As Xiaomi has locked the shutdown (it wrote "Can't power off, the device is locked" sometimes..) it can happily drain.
When you leave 9008 mode, you have to charge until system starts and then drain again.
Further, there seems to be some other mode, which "edl.py" recognizes as "memory dump mode". The USB ID is correct, but EDL commands are not possible.
Interestingly, I have no problems with the second hand device but my other lavender device bought from a..zon returns "Only nop and sig tag can be recevied before authentication" when trying, for example, "edl.py --loader=prog_emmc_firehose_Sdm660_ddr.mbn printgpt". As both should have the same PBL, I don't yet understand it..
There seems to be some timeout (seconds..) when switching to EDL mode, after that no commands are accepted.
I will stop here, as there are already tutorials how to unlock the mi lock in EDL mode and currently I don't want to just reflash via QFIL or QPST. I'm trying some reverse engineering meanwhile.
Click to expand...
Click to collapse
Hello,
My lavender was bricked two days ago and I managed to unbrick it.
I think my method will help you get rid of mi cloud.
pm me
Mi.bilel said:
Hello,
My lavender was bricked two days ago and I managed to unbrick it.
I think my method will help you get rid of mi cloud.
pm me
Click to expand...
Click to collapse
You can only resolve the Problem with mi acc with a unlocked bootloader, if you bypass & go online the device get closed
Snuk265 said:
You can only resolve the Problem with mi acc with a unlocked bootloader, if you bypass & go online the device get closed
Click to expand...
Click to collapse
Do you mean it gets closed by mi cloud or by google?
meeep said:
Do you mean it gets closed by mi cloud or by google?
Click to expand...
Click to collapse
If you use the phone to go online, it will be blocked again by your existing Mi account/ mi cloud so that you cannot use it. So you have to open the bootloader to install a custom rom or after you have completed the bypass you must first delete a few system apps via twrp so that the phone is not locked
Snuk265 said:
If you use the phone to go online, it will be blocked again by your existing Mi account/ mi cloud so that you cannot use it. So you have to open the bootloader to install a custom rom or after you have completed the bypass you must first delete a few system apps via twrp so that the phone is not locked
Click to expand...
Click to collapse
ok, thank you for the info!
I'm trying to get around the lock without 'magic tools', don't know how much is possible.
Meanwhile I found a great and simple way to remove at least the mi cloud lock:
romprovider com reset-frp-bypass-mi-account-redmi-note-7
To not change the UUID of the persist partition I just mounted it and removed everything but /sensors/sensors_settings and /lost+found.
But now I don't know how to get further. As mentioned by @Snuk265 I cannot just connect to mi cloud again. Or do I?
Btw, now that the phone is unlocked, I got informations online via IMEI:
Sales Region: Cambodia
MI Activation Lock: ON
Device Status: CLEAN
Find Device Status ON
Device Status This device is PROTECTED!
Blacklist Status: CLEAN
meeep said:
I cannot just connect to mi cloud again. Or do I?
Click to expand...
Click to collapse
Ok, I tried it, now the device is locked again
meeep said:
Ok, I tried it, now the device is locked again
Click to expand...
Click to collapse
I know hehe, I was already there so I told you so
Snuk265 said:
I know hehe, I was already there so I told you so
Click to expand...
Click to collapse
I had to test this by myself!
Now, if you can tell me why even with test point and patched programmer I always get "only nop and sig", _that_ would be nice! :laugh:
With deep flash it stop working ("only nop and sig")
So I opened the case.. Tried timings, battery on/off, lcd on/off, fingerprint on/off..
Maybe it's because I'm trying with a downgraded mi rom? But sahara is running in qualcomm rom, so I don't know why this should matter.
From internet:
- I had the same problem with mine, only it came to me after changing the recovery. I confused the version of the recovery because I did not read thoroughly which one to put.
How I fixed it - I downloaded the last stable fast rum rum, unzipped, booted the boot.img file, flashed it through fastboot, without restarting immediately flashed twrp version TWRP 3.2.2-0711, restarted by holding the buttons in the recovery. There was a full wipe of everything, a restart again in Rkavery, I uploaded the last developer rum and flashed with it.
Click to expand...
Click to collapse
After leaving the phone alone over night it finally worked! yay!
Phone is unlocked! Many thanks to @Snuk265 !
Not thanks to me xd?
I think I helped too
owl7 said:
I have a Redmi note 7 the bootloader is Unlocked and I managed to install a TWRP
The Mi account is Locked
Is there a Way to Bypass or Remove mi login via TWRP ?
I bought the phone on ebay .
Thanks
Click to expand...
Click to collapse
No you can use it only with a custom rom
hello,
My redmi 6a only lights the white led when connecting the usb cable and turns the screen completely black. I can't enter recovery mode nor fastboot.
I have the deep flash usb cable, but I can't make it work either. The adb driver was installed as well as the qualcomm.
Has anyone been through this? Do you have any tips?
Hello,
Maybe you can help me with my problem
I have Mi MAx 3 but the Thing is, the bootloader is locked and the device is locked also.
Sad
For your device i dont have the images sorry
I have basically the same problem with a Mi5. Everything worked fine of course until I tried to wiped everything to reinstall a clean system, couldn't unlock the bootloader, tried various things until I got the device "clean enough" that it would just lock when connecting to a network.
I have access to EDL and flashed it clean from there, but as far as I understand though, if the bootloader is locked there is just exactly nothing that can be done, right? There's a workaround so it doesn't lock on connecting to a network and I can use the system as is (a rather old MIUI10) but it will never be possible to unlock the bootloader (because it's still linked to another Mi account somehow) and install a custom ROM, get root access, etc.
Am I right, or is there somehow a way to still unlock the bootloader?
meeep said:
Phone is unlocked! Many thanks to @Snuk265 !
Click to expand...
Click to collapse
Finally, How did you unlocked the device bro?. Which flash tool did you use bro?. Please tell me the process short and simple. I have same problem but im confused because you have told lot of stuff that im messin around. Help me please. Explain step by step short and simple bro
I charged my Mi A2 overnight and woke this morning to find that it won't boot past the Mi A2 splash screen; it shows the splash screen for a few of seconds and then dies. I read advice to hold down power and 'up' keys, this just resulted in the same. I tried power and 'down' key and that got me as far as the Fast Boot splash screen, but no further (phone just continued to display that splash screen). I've tried taking the SIM out and turning it on - no change. I tried opening it up and disconnecting the battery for 3 minutes - no change. I'd be very grateful if anyone could suggest a fix. I know this is hugely unhelpful, but I can't remember what I did to the phone in terms of unlocking the bootloader and/or rooting, but I have a feeling I left it stock (I've owned the phone for a couple of years and haven't changed anything material since initial setup).
Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?
Martinocom said:
Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?
Click to expand...
Click to collapse
Thank you very much for your help.
Executing fastboot reboot via adb just brought me back to the Android One splash screen for a few seconds before the screen went black.
Changing the active slot to both A and B gave me the following error message:
FAILED (remote: 'Slot Change is not allowed in Lock State')
Pressing up + power when turning on just brought me to the Android One splash screen for a few seconds before the screen went black. I held those two buttons down for several minutes and the same thing kept happening: splash screen followed by black, repeatedly.
Is there anything else I can try?
You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.
Martinocom said:
You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.
Click to expand...
Click to collapse
Thank you.
If anyone reading knows of a way to get my phone to boot without losing my data I'd be very grateful for your help.