Good morning,
I was tryng to flash the hydrogen os and something went wrong with magisk so now the phone reboot just to fastboot mode and i cant do nothing... I already tried to restore it throw the fasboot recovery guide con this forum but the problem is that the comouter doesnt see the phone in fastboot... I already installed the adb and fastboot driver for the oneplus 6 but if i type the command fasboot devices the promp doesnt show the phone as usually... Someone can help me? Thanks
Did you already try with this?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Sent from my ONEPLUS A6000 using Tapatalk
Related
Sorry if i'm posting this in the wrong section, but i've got a problem.
So, I was in twrp 8.7.0 and i flashed the image of twrp 8.1.0 so i could install the Unity Rom, and when i rebooted into recovery it just sat on the screen with the oneplus logo on it. I have also tried going into fastboot mode and tried to flash the image from there, but it just says Error: Device Not Found.
I'm Hoping someone can help me.
Regards,
Wi_Fi.
Check your fastboot drivers on your computer
If you need help or a Teamviewer session for this. Pm me, I'll try to help you!
Regards,
Jeffrey
Are you trying to flash vía fastboot utility? Some days ago i has the same problem,and solved vía fastboot/adb commands.
Tecleado desde mi 1+1.
Can you actually get into fastboot? If so try
fastboot devices
Does your phone show up in the list? My guess like above would be a driver issue but if it can see it then you should be able to flash.
Can you boot the phone to rom?
My question is: Is there any way that i can install any custom recovery now, when I am locked out of my phone, so I can try Method 7 from this post . I have enabled USB debugging, but for some reason, my device is unauthorized from executing adb commands.
I have Xiaomi Redmi Note 3, and have forgotten its password. I have tried Method 2, 5 and 6 from this post, but to no avail.
I tried method 2 and 5 which requires ADB to be installed, but I was not able to access my phone. I have USB debugging enabled and my phone is not rooted. When I tried to run the following code:
Code:
adb devices
adb shell
it showed that my phone is unauthorized and error: device unauthorized This adb server's $ADB_VENDOR_KEYS is not set
Here's the screenshot:
When trying method 6, I had to change the path of ADB driver because the file I downloaded from the post, had its own ADB driver which clashed with my already installed ADB driver, but even after that, it again showed the above error. Here' the screenshot:
Finally I want to try method 7 from the above post, which requires custom recovery to be installed on the phone, is there any way now?
Though it seems now that the I have only one option left and that is to factory reset my phone, but if , there is any other way by which I can bypass my lock screen, please please please inform me.
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
joe2k01 said:
Install TWRP or CWM with fastboot and then flash the Unlock me! zip that I've created and you won't lose your data.
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Didn't know that such package existed... I'd still do it my way if your phone was laggy/corrupted,... Else do the package flash. Keep me updated!
Sent from Lenovo a6000 1GB version.
Thanks! a lot, could you please guide me a little bit, how should I proceed?
MGlolenstine said:
Of course you can. Just boot your phone into fastboot and do "fastboot flash recovery <recovery image name>.IMG" and you'll flash it. And you can't access the adb because your screen is locked... This is how companies prevent phone hacking
So flash custom recovery, backup the /data , factory reset and after resetting restore the /data backup. And you're good to go. I suggest you using TWRP, because I use it and it never left me hanging Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
dost25 said:
Thanks! a lot for reply, As I am still a newbie and trying to learn few things. Could you please guide me how should I proceed?
Like What files I need to download and from where? Also how should I use these files to install recovery?
Click to expand...
Click to collapse
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Ok i will try
MGlolenstine said:
OK... So first boot into fastboot. When you've done that, connect It to your pc with usb, download fastboot package from somewhere on xda(you'll find it).
Open command prompt "CD" to the directory where your fastboot is located in, put recovery image in the folder where fastboot.exe is and type "fastboot flash recovery <recovery file name>.IMG". I'm gonna update this answer in 2 days, when I get to my pc, so try to do it by these instructions, if something isn't working, comment and we'll resolve the problem. If something isn't clear, just ask. Keep me updated.
Sent from Lenovo a6000 1GB version.
Click to expand...
Click to collapse
Can unlocking my bootloader somehow brick my phone?
Everything can brick your phone. Updating my lenovo phone with official update hardbricked mine... But yeah, it can.
Hello everyone.
I'm having problem in flashing a ROM into my Blu Life Pure XL 16GB with Snapdragon (Equivalent to Redmi Note 3).
My smartphone is in the following situation: >>>It only boot into fastboot mode.<<<
I cant get into recovery mode, or EDL or anything else. Debug mode is enable and bootloader is unlocked. Tried every "button combination" and no sucess.
My PC recognize ADB interface driver, i can see my device in "fastboot devices", but if i try to type "fastboot continue" my device just get stuck on BLU logo and i must restart it. (In cant ever turn off the device)
I tried to flash a ROM through MI Flashtool, the software recognize COM port everything seems to be ok, but if i try to flash a ROM then tooks forever. The green bar gets full, more then 3 hours waiting and nothing.
I also try to enter in EDL mode to try flashing a ROM through QFIL (Qualcomm Flash Image Loader), since i can only get fastboot mode i just downloaded "fastboot EDL" that i found here on XDA however its not worked, its just get stuck in "Waiting for device...". I can list my device normally using Minimal ADB and Fastboot version 1.4.2 but no sucess with Fastboot EDL V1 and V2.
All drivers are installed and working.
Anyone else have another method?
There is another FASTBOOT EDL that works on my device?
Thanks guys.
Hi there and welcome to assist,
Unfortunately there is nothing about your question/device on XDA forum. Try a Google search first or contact the manufacturer for stock firmware and flashing instructions.
Also you can try this [GUIDE]How to reboot to EDL from fastboot
You'll have to create an account to post in the main forums if you have any other questions.
Good luck
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
TSKXDA said:
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the command "fastboot oem edl" in cmd of adb folder when device is in fastboot mode. Ur phone should go black but dont panic. Now open miflash tool and u see ur device is connected in edl mode as COMX ( X may be anything 10 or 20 like that). Now try to flash the lattest fastboot rom for over device. Remember to check the option in mi flash tool to not lock bl again. But this will wipe all your data.
Sent from my Redmi Note 7 Pro using XDA Labs
hackermssharma said:
Try the command "fastboot oem edl" in cmd of adb folder when device is in fastboot mode. Ur phone should go black but dont panic. Now open miflash tool and u see ur device is connected in edl mode as COMX ( X may be anything 10 or 20 like that). Now try to flash the lattest fastboot rom for over device. Remember to check the option in mi flash tool to not lock bl again. But this will wipe all your data.
Sent from my Redmi Note 7 Pro using XDA Labs
Click to expand...
Click to collapse
Thank you for taking time to reply to my query. I did what you suggested and got into EDL mode. Xiaomi Mi Flash picked up the device as COM10 but when I tried to flash it shows "sahara read end error with status:40" and nothing happens.
Any further idea?
TSKXDA said:
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
Click to expand...
Click to collapse
I suggest you use the older variant of the MiFlash tool.
How did you flash Peter's? Did you use "fastboot flash recovery recovery.img"? That's the only right command.
Also are you sure you have the Indian variant of the phone? Another way to bypass anti roll back would be to clear all partitions, and then flash the required ROM.
Sorry if I'm not able to help you, I'll try having a look later on.
Thank you for your support. I had to go to the service center as no solution could be found.
Wait i know what happen... Ur phone has twrp and rom successfully installed don't worry about that. Just problem is ur phone has again locked the bootloader thats why its not able to boot os because it has twrp not the official recovery. U can verify that u have bootloader locked.. when ur phone starts when there is mi logo there will not be "unlocked" written in bottom.. see... That is very easy. Just try to unlock bootloader again with mi unlock tool.
And ur good to go. I got same errors on my friends redmi 6 pro. Service center will tell u to change motherboard as it cant be fixed with edl mode. JUST TRY TO UNLOCK AGAIN WITH MI UNLOCK TOOL.
dnyaneshmoh said:
Wait i know what happen... Ur phone has twrp and rom successfully installed don't worry about that. Just problem is ur phone has again locked the bootloader thats why its not able to boot os because it has twrp not the official recovery. U can verify that u have bootloader locked.. when ur phone starts when there is mi logo there will not be "unlocked" written in bottom.. see... That is very easy. Just try to unlock bootloader again with mi unlock tool.
And ur good to go. I got same errors on my friends redmi 6 pro. Service center will tell u to change motherboard as it cant be fixed with edl mode. JUST TRY TO UNLOCK AGAIN WITH MI UNLOCK TOOL.
Click to expand...
Click to collapse
Thank you for your feedback but the phone bootloader remained unlocked as when the phone starts there is "unlocked" written in bottom.
I got the phone back from Service Center. It's working fine but strangely still the bootloader is shown as unlocked in the start animation.
Hello everyone! I am in dire need of help right now. I wanted to flash this pixel experience 13 custom rom while i was on OOS12. I unlocked my bootloader and then flashed the recovery image on the website using the cmd command in the fastboot mode. Now my device is showing me that the current image(recovery/boot) have been destroyed. I tried using this guide https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ but I still could not restore my phone and I am unable to get past fastboot mode. I tried using MSM but my device is not being recognized and I am also unable to boot into EDL mode. I am quite literally stuck without a phone and in desperate need of help. Please help a brother out!!
hasan lakha said:
Hello everyone! I am in dire need of help right now. I wanted to flash this pixel experience 13 custom rom while i was on OOS12. I unlocked my bootloader and then flashed the recovery image on the website using the cmd command in the fastboot mode. Now my device is showing me that the current image(recovery/boot) have been destroyed. I tried using this guide https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ but I still could not restore my phone and I am unable to get past fastboot mode. I tried using MSM but my device is not being recognized and I am also unable to boot into EDL mode. I am quite literally stuck without a phone and in desperate need of help. Please help a brother out!!
Click to expand...
Click to collapse
India, Europe, Global?
hasan lakha said:
Hello everyone! I am in dire need of help right now. I wanted to flash this pixel experience 13 custom rom while i was on OOS12. I unlocked my bootloader and then flashed the recovery image on the website using the cmd command in the fastboot mode. Now my device is showing me that the current image(recovery/boot) have been destroyed. I tried using this guide https://www.thecustomdroid.com/oneplus-nord-oxygenos-restoration-guide/ but I still could not restore my phone and I am unable to get past fastboot mode. I tried using MSM but my device is not being recognized and I am also unable to boot into EDL mode. I am quite literally stuck without a phone and in desperate need of help. Please help a brother out!!
Click to expand...
Click to collapse
My honest suggestions : Stay away from OOS12 ( even base ). Besides, if u want to boot into EDL, just force power off the device totally. Then press and hold both Vol +- and plug the device into the computer with MSM stared, ur device will be in EDL ( ofc, u will have to install all necessary drivers beforehand )