Well, I was trying to unlock the bootloader just for enable the camera2api and then lock it again. But for some reason, the data corrupts after i leave the fastboot. It doesn't matter if i unlocked, locked, or did nothing. But when I type "fastboot reboot", an error screen appears saying that the system has corrupted.
Related
I was trying to install Camera2 on it. Unlocked it with developer options ->Unlock OEM
After try some things I reset factory the cellphone and decide to forget camera2 things...
So I went to developer options and LOCKED OEM.
After that I reboot in fastboot mode and did fastboot oem lock
Now the cellphone is locked in a bootloop saying that my deveice loaded a differente operational system and a screen to visit miui.com/unlock.
The unlock aplication doesn't work. Says that I can't unlock the device.
So that means I lost my crazy brand new phone? THere's any solution? The Test Point solution will work? Is that the only solution???
Thiank you for any response.
foxdanger said:
I was trying to install Camera2 on it. Unlocked it with developer options ->Unlock OEM
After try some things I reset factory the cellphone and decide to forget camera2 things...
So I went to developer options and LOCKED OEM.
After that I reboot in fastboot mode and did fastboot oem lock
Now the cellphone is locked in a bootloop saying that my deveice loaded a differente operational system and a screen to visit miui.com/unlock.
The unlock aplication doesn't work. Says that I can't unlock the device.
So that means I lost my crazy brand new phone? THere's any solution? The Test Point solution will work? Is that the only solution???
Thiank you for any response.
Click to expand...
Click to collapse
"So I went to developer option and LOCKED OEM" can you be a little more clear. Because unlocking the bootloader locks the OEM unlock option in the developer settings.
Possible cause of your bootloop is the change in your build.prop file.
I did a similar mistake as well. My phone was stuck in a bootloop. My mistake was that I installed Magisk and forgot to uninstall it through the Magisk manager before locking the bootloader and so the system were not in their stock state.
What I did was, I just booted my phone into fastboot.
Unlocked the bootloader again by using "fastboot OEM unlock". Went into fastboot again. Checked the current active slot by "fastboot getvar current-slot" and flashed the stock boot image from the stock pie rom found on Mi website.
Njaiker said:
"So I went to developer option and LOCKED OEM" can you be a little more clear. Because unlocking the bootloader locks the OEM unlock option in the developer settings.
Possible cause of your bootloop is the change in your build.prop file.
I did a similar mistake as well. My phone was stuck in a bootloop. My mistake was that I installed Magisk and forgot to uninstall it through the Magisk manager before locking the bootloader and so the system were not in their stock state.
What I did was, I just booted my phone into fastboot.
Unlocked the bootloader again by using "fastboot OEM unlock". Went into fastboot again. Checked the current active slot by "fastboot getvar current-slot" and flashed the stock boot image from the stock pie rom found on Mi website.
Click to expand...
Click to collapse
What I did was with the phone working I entered on configuration, developer, and turned of the oem lock option.
Than I reboot in fastboot and did fastboot oem lock.
This made the cellphone unbootable. Bootloop saying that I'm trying to start a different operational system.
And I can't make fastboot unlock because I turned off the option in the system, so I can't send fastboot commands like oem edl, unlock, unlock-critical and etc...
I can't do nothing :/
I don't know how the option was working, but was... I know it should be locked, but this time wasn't. Was after I factory reset the cellphone
Your fault that you locked bootloader on a modified system. Do a research next time
Hi, so my Xiaomi MI A2 is kinda not working and I think that wiping cache partition might help but I can't access the recovery so I wanted to install TWRP. The thing is I have the boatloader locked, I have the USB depuration activated but not the OEM, so how can I unlock boatload or unlock OEM via fastboot?
Thanks
_08_ said:
Hi, so my Xiaomi MI A2 is kinda not working and I think that wiping cache partition might help but I can't access the recovery so I wanted to install TWRP. The thing is I have the boatloader locked, I have the USB depuration activated but not the OEM, so how can I unlock boatload or unlock OEM via fastboot?
Thanks
Click to expand...
Click to collapse
run "fastboot oem unlock" and "fastboot oem unlock_critical" see if its execute without error , then run " fastboot oem device-info" , let us know what the result.
shihabrumel said:
run "fastboot oem unlock" and "fastboot oem unlock_critical" see if its execute without error , then run " fastboot oem device-info" , let us know what the result.
Click to expand...
Click to collapse
It won't let me. It says:
my command: fastboot oem unlock System: FAILED (remote "flashing unlock is not allowed")
Fastboot: error: command failed.
Same with the critical. I also had an error trying another command, it said, not allowed in lock mode.
Actually, I'm trying other commands and it's the same error with all comands.
My Mi A2 was not booting
My mi a2 last updated to 19/04/05 pie version, then i install the Google camera using below steps..
1. Turn on debugging mode/oem & turn off the phone
2. Then power button+vol dwn Fastboot mode & connect to pc (Pc already have the adb)
3. In pc>adb>folder>Cmd> type "fastboot oem unlock"
4. Then factory reset the phone and reboot again to fastboot mode
5. Then boot the patched image for phone
6. Then install the magisk and gcam work perfectly.
Simply i used these methods
the***********.com/enable-camera2-api-xiaomi-mi-a2-lite-guide/
But then I tried to relock the bootloader, using below commands on cmd
1. "adb reboot-bootloader"
2."fastboot oem lock"
I tried these 2 commands 4 or 5 times
But phone is not power on with locked bootloader. Then I unlock again oem and try again,, But not working,
Then i unlock bootloader again and try these commands to lock it again,
1. "adb reboot-bootloader"
2."fastboot flashing lock"
3. "fastboot oem lock"
Unfortunately it is not work, also i can't give command "fastboot oem unlock", also i can't turn on my phone, Please help me... I want to restore my phone to working mode... Please help me, Quick, urgent :crying::crying::crying::crying:
Hi guys, it's my first post. I have my MI A2 bricked after the last update. It's stuck at android logo and I can access only fastboot, no adb. Via fastboot I tried to wipe the phone, install TWRP, unlock the bootloader, but the answer is always I cant flash or do anything with a locked phone. What can I do? Is it possible to save data?
With locked bootloader and critical all your attempts to flash anything via fastboot could not succed, unless .you have previously got developer rights and checked "OEM unlock" option. With this option ON, and using USB 2.x port, you could unlock bootloader and critical via fastboot, but have no ways to save data (which is erased with unlocking as with factory reset).
Try to reboot many times with external power off and on, phone is supposed to boot into now inactive A/B slot (which was active prior to OTA) sooner or later, then you can save data and unlock.
If nothing helps, you'll have to open case, connect "[email protected] (or EDL) pins and then flash stock ROM with MiFlash, and then unlock and reflash with fastboot.
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.
try the "fastboot continue" command
dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not
I loaded latest android drivers, and successfully accessed the phone with "adb devices". The phone is OEM unlocked in the settings and USB developer mode is set. On issuing "fastboot OEM unlock" or "fastboot flash unlock", I got a (tiny) message on the screen that said something like " the serial is not match ....., fastboot_verify_unlock fail". After 2 seconds the message disappears and reboots when the power button is pressed. The RealMe UI native boot screen has an option to load a .img file. Could I use this to load a TWRP or other bootloader? Any clues?