Related
Hi guys,
Recently did a big ****up with my device. Tried to unlock_critical which said already unlocked but wasnt in order to convert to 6x. Tried to oem lock again and im now locked out. Device doesnt boot and cant flash anything via fastboot.
I already figured i have to go to edl mode for flashing stock software, have opened my device now and tried to short the edl pins as explained in youtube videos.
However, no sign of this working! no light, nothing!
Im using manjaro linux which doesnt recognize the device only via adb or fastboot.
Already tried using virtualbox for miflash but i cant get the usb port to work with it.
Can you help me please?
In my case for EDL, i only need to unlock critical, then power + volume up
hafizhlf said:
In my case for EDL, i only need to unlock critical, then power + volume up
Click to expand...
Click to collapse
unlock critical does not work since the bootloader is locked and oem toggle cant be turned on since theres wrong software
Sent from my Samsung SM-T835 using XDA Labs
dr460nf1r3 said:
unlock critical does not work since the bootloader is locked and oem toggle cant be turned on since theres wrong software
Click to expand...
Click to collapse
Can you boot to fasboot and unlock bootloader, then critical_unlock
hafizhlf said:
Can you boot to fasboot and unlock bootloader, then critical_unlock
Click to expand...
Click to collapse
By flashing unlock? failed flashing unlock is not allowed..
Sent from my Samsung SM-T835 using XDA Labs
you can to find a windows laptop or pc from your friends for a while ?? I do not think you can run correctly edl mode + all the necessary tools & files from Linux,after test points...
the device must be have all the necessary drivers (first disable driver signature) fastboot etc as you know...
https://en.miui.com/thread-3524265-1-1.html
_ https://mega.nz/#!x6BkXY5A!hx8SXoBwd4-fW1UkZ1poHc7p-MFDaQ85FYH7Yk8bLZ8 (fastboot edl)
_ https://mega.nz/#!EqJwTIzB!KJF3CldYq_u7KylaL0iO6rs05RWs2_dcUfaENjJcDpU (QDLoader HS-USB Driver)
[The above driver is needed to be able to flash fastboot rom in EDL mode, with the MiFlash Tool on Xiaomi devices with Qualcomm processor and locked bootloader]
__test points > edl mode (edl no needs necessary unlocked BT) > miflash tool > fastboot rom : http://en.miui.com/download-353.html
sry for english
daitalos said:
you can to find a windows laptop or pc from your friends for a while ?? I do not think you can run correctly edl mode + all the necessary tools & files from Linux,after test points...
the device must be have all the necessary drivers (first disable driver signature) fastboot etc as you know...
https://en.miui.com/thread-3524265-1-1.html
_ https://mega.nz/#!x6BkXY5A!hx8SXoBwd4-fW1UkZ1poHc7p-MFDaQ85FYH7Yk8bLZ8 (fastboot edl)
_ https://mega.nz/#!EqJwTIzB!KJF3CldYq_u7KylaL0iO6rs05RWs2_dcUfaENjJcDpU (QDLoader HS-USB Driver)
[The above driver is needed to be able to flash fastboot rom in EDL mode, with the MiFlash Tool on Xiaomi devices with Qualcomm processor and locked bootloader]
__test points > edl mode (edl no needs necessary unlocked BT) > miflash tool > fastboot rom : http://en.miui.com/download-353.html
sry for english
Click to expand...
Click to collapse
Yes ill have access to one in a few days. thanks again for pointing out and giving those links so i dont have to search for them.
annoying as hell not to have access to my phone right now :/
Sent from my Samsung SM-T835 using XDA Labs
dr460nf1r3 said:
Yes ill have access to one in a few days. thanks again for pointing out and giving those links so i dont have to search for them.
annoying as hell not to have access to my phone right now :/
Sent from my Samsung SM-T835 using XDA Labs
Click to expand...
Click to collapse
I hope you can fix the device
take & this tool : https://mega.nz/#!cr4SUIqY!Rzlftk2OFun8XIkNQb2aXRtP7-t3f4DB92vMIl90pgw
(this is for xiaomi & not only...this tool can any work for you....for example : disable drivers signature,Install all drivers & puts the device on EDL mode ....Just,read & follow the instructions.Open this link in chrome browser & read carefully with translate help, is in Greek Language :
https://xiaomi-miui.gr/community/in...τά-Xiaomi-σε-όλα-τα-Windows-x64-x86/?pageNo=1 )
Gl
I have the same issue, fastboot mode is useless to flash anything. Booting with adb into edl mode reboots phone normally.
Getting disconnected after a half minute in EDL mode.
Hello guys, I'm having a big problem, some day earlier the A2 started to bootloop and fastboot, adb wasn't working.
So I opened the mi A2, disconnected the battery cable and booted in edl mode but after 20 sec it got disconnected and again I short it and boot in edl and it disconnecting.
A help would be amazing. Thanks in advance.
Rm789 said:
Getting disconnected after a half minute in EDL mode.
Hello guys, I'm having a big problem, some day earlier the A2 started to bootloop and fastboot, adb wasn't working.
So I opened the mi A2, disconnected the battery cable and booted in edl mode but after 20 sec it got disconnected and again I short it and boot in edl and it disconnecting.
A help would be amazing. Thanks in advance.
Click to expand...
Click to collapse
I'm in your position now. It reboots even in edl mode. How did you fix this?
hello guys
my xiaomi redmi 9a got hard bricked doe not turn on and i cant enter recovery or fastboot when i enter to edl mode does not showing up on my desktop please reply me
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
Phone info
OPPO A74 5G
Model number - CPH2197
Build number - CPH2197_11_A.12
Android 11
Developer Mode enabled
OEM Unlock enabled
USB Debugging enabled
Below are screenshots of all of the above
[Screenshots](https://imgur.com/a/qw0fUAw)
Phone is recognised by ADB but not Fastboot and as such I cannot unlock the Bootloader. Is there something I've done wrong or something else I can try?
When entering "Fastboot devices" in CMD nothing comes up.
When entering command "ADB reboot Bootloader" in CMD the phone restarts instead of loading into Bootloader.
I have tried turning phone off and the pushing power button + vol up - this just keeps restarting phone.
Any help would be much appreciated as I'd really like to root this phone all extra info in images on Imgur. Link above.
DeeSkye said:
Phone info
OPPO A74 5G
Model number - CPH2197
Build number - CPH2197_11_A.12
Android 11
Developer Mode enabled
OEM Unlock enabled
USB Debugging enabled
Below are screenshots of all of the above
[Screenshots](https://imgur.com/a/qw0fUAw)
Phone is recognised by ADB but not Fastboot and as such I cannot unlock the Bootloader. Is there something I've done wrong or something else I can try?
When entering "Fastboot devices" in CMD nothing comes up.
When entering command "ADB reboot Bootloader" in CMD the phone restarts instead of loading into Bootloader.
I have tried turning phone off and the pushing power button + vol up - this just keeps restarting phone.
Any help would be much appreciated as I'd really like to root this phone all extra info in images on Imgur. Link above.
Click to expand...
Click to collapse
Did you find a way? I tried everything but I couldn't get into fastboot
No way to enter fastboot mode for oppo phones. Now I use Oppo A74 4G version. Cannot enter fastboot mode. It's locked by Oppo. And they don't give bootloader code for unlock BL. Only way is to change phone
I've been trying run fastboot too. 4 hours later I find this thread. That explains it
Last Oppo phone I buy I guess.
Did you manage to find a workaround for this by chance?
Has anyone tried rebooting from recovery to then enter fastboor or?
Im gonna look into myself soon...
Ive seen this issue before on a different phone but cant remember how they bypassed it
Perhaps yall can try to find a post where they did so.. maybe it'll work on this phone too.
I was able too get to fastboot mode. The phone labels it "recoveryd mode", however, fastboot commands work.
1st. Connect phone and confirm ADB is connected by using "ADB devices" command.
2nd. Enter "adb reboot fastboot bootloader"
Phone will reboot into "recoveryd mode". It looks exactly like the normal recovery mode except the title displayed after you select the language and fastboot commands will work.
However, I still have not found out how to unlock the bootloader, so it does me no good.
try doing adb reboot fastboot or adb reboot bootloader
fastboot oem unlock
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
guys ,, fails
when trying to boot to fastboot and not fastbootd
Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.
Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.
To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.
From the bootloader you should be able to flash the raw image again, it should flash everything
Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.
Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.
Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?
I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!