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 )
Related
My Redmi Note 6 Pro Global version just rebooted itself out of nowhere and now its showing MI logo and rebooting every 3-5 seconds. I didn't unlock bootloader and had MIUI 10 latest stable version installed. I can still enter fastboot mode. What can I do to fix this?
UPDATE
Over the last few days, these are the things that I've tried:
I can enter Fastboot mode and connect to my PC, but can't enter recovery mode.
I was able to unlock my bootloader (I was in the process of waiting for the 360 hours)
I tried flashing fastboot rom with MiFlash, but when MiFlash causes phone to reboot towards the end of flashing, the bootlooping problem occurs again and it cannot complete flashing.
I also tried flashing TWRP from fastboot, it says that it's successful, but when I try fastboot boot twrp.img, the same problem: MI logo and constant reboots.
I also tried to use fastboot oem edl mode and my phone is recognized as Qualcomm device, but MiFlash can't flash in this mode, saying that hello packet is not received.
At this point, I don't know what else to do and wondering if this is a hardware problem. Any ideas?
Did you tried to press VOL UP + POWER BUTTON after you flash TWRP? If flashing TWRP doesn't work Try to flash Official MIUI RECOVERY 3.0 That's all you can do. Otherwise you should give it to Mi customer service for faster solution.
I have the same problem, did you manage to solve this issue?
hello guys,
here is a solution, open your phone backpart and put your phone to edl mode by testpoint pinout,
then try to flash latest stable rom if fail then flash latest dev rom.
MI stuck at boot logo
m1s3rys1gn4l said:
hello guys,
here is a solution, open your phone backpart and put your phone to edl mode by testpoint pinout,
then try to flash latest stable rom if fail then flash latest dev rom.
Click to expand...
Click to collapse
Hello all ! same problem here !
i reinstall the last version in EDL mode every week !!
I can not handle it anymore !
sometime he match 1 day sometime 3 week ... everytime he stuck on menu and i can't reboot .
the only version i can use its 10.3.2 global ... all other version don't match !
Sorry for my english (i'm french) and thanx you for your help
hi my redmi note 6 pro is stuck on mi logo its not getting over it .
i dont have any pc or laptop at my home how can i solve this issue
during this lockdown ,and now its showing charging in shutdown mode?
Hello All i have the same problem stuck on MI logo
I have tried to wipe through Mi recovery but no use
I cant flash anything because the bootloader is locked
and i dont want to use EDL mode cuz i am stuck at home and dont have necessary tools for that
My question is can we flash anything using Fastboot command or can we ON usb debugging through fastboot be cause Mi flash wont work until USB debugging in On
Please help
Try another flash tool i.e. Qfil_flash_tool
Hi, I have even tried EDL mode to flash latest rom (android 9,miui11.0.4) using Mi flash tool,still facing the same issue.
It constantly reboots while on charging, and it doesn't turn on otherwise(2 Sec of that logo and then it fades away).
Please Help
any one find solution for this?
Hi, my problem is simpler, so is there any suggestion.
after last official update, due to the internal partition was encrypted, update wasn't finished and I am stuck on MI logo when restarted the phone.
bootloader is unlocked and I can enter to (orangefox) recovery, yet I am not sure what is the best way just to return phone to the bootable state? I presume some wiping is to be done, which is not the problem, just to have as short procedure as possible, preferably without need to re-flash clean ROM from recovery?
regards
mertcanekiz said:
I was able to unlock my bootloader (I was in the process of waiting for the 360 hours)
Click to expand...
Click to collapse
Hi, i'm in the same situation as you. How did you solve it? with the miunlock app I can't unlock it because it tells me that I have to select something on the phone first, but if the phone doesn't start I can't select anything ..
Try to remove hardware buttons from board and try
redmi 6 pro (bootloader locked)
same problem...
tried methods :
1) using mi flah tool ( error occurred : )
2) edl method (showing: device is locked)
........still stuck on miui logo .........
Hello there. I have a p01y unable to boot. It goes straight into recovery mode but I get just the dead droid with no command warning, same if I intentionally boot in recovery.
Fastboot mode is working fine and I can access it with windows
Kooza said:
Hello there. I have a p01y unable to boot. It goes straight into recovery mode but I get just the dead droid with no command warning, same if I intentionally boot in recovery.
Fastboot mode is working fine and I can access it with windows
Click to expand...
Click to collapse
It would help to know how this all started. Ultimately, you'll need to flash the firmware
Hovatek said:
It would help to know how this all started. Ultimately, you'll need to flash the firmware
Click to expand...
Click to collapse
Nevermind, I got this by aft and flashing firmware update through newly acquired recovery.
Thank you!
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.
Hi
My Redmi note 7 pro is bricked and it is in locked state .
I tried flashing fastboot rom from edl mode
But it gaves errors like
1) cannot receive hello packet
2)Only nop and sig tag can be recevied before authentication.
Please help me guys regarding this its been a while without my phone
AwesomeAman said:
Hi
My Redmi note 7 pro is bricked and it is in locked state .
I tried flashing fastboot rom from edl mode
But it gaves errors like
1) cannot receive hello packet
2)Only nop and sig tag can be recevied before authentication.
Please help me guys regarding this its been a while without my phone
Click to expand...
Click to collapse
Firstly, can you still boot into Fastboot mode? Secondly, you said you flash fastboot ROM from EDL, how you get into that EDL mode, and you're flashing by MiFlash right?
Clear the information, I might help you!
LinhBT said:
Firstly, can you still boot into Fastboot mode? Secondly, you said you flash fastboot ROM from EDL, how you get into that EDL mode, and you're flashing by MiFlash right?
Clear the information, I might help you!
Click to expand...
Click to collapse
Answers:
Yes it is going on fastboot mode
I got into edl mode by opening back Pannell of my device and i connected edl points
I am flashing via mi flash.
Actually in mi flash tool by mistake i flashed fastboot rom by selecting flash and lock.
Now when i flash the same by selecting clean all option by putting my device on edl mode
It show cannot receive hello packet.
This put me in this trouble
AwesomeAman said:
Answers:
Yes it is going on fastboot mode
I got into edl mode by opening back Pannell of my device and i connected edl points
I am flashing via mi flash.
Actually in mi flash tool by mistake i flashed fastboot rom by selecting flash and lock.
Now when i flash the same by selecting clean all option by putting my device on edl mode
It show cannot receive hello packet.
This put me in this trouble
Click to expand...
Click to collapse
Right, then you did the testpoint trick to get in EDL mode! Ofcourse now you can't use MiFlash with clean all to flash your device since your device is now in brick state. Only solution now is to find the factory images of your device, along with an authenticated prog file then use QFIL to force flash into device. You may inbox me if need further instructions!
i have the same issue pls help
LinhBT said:
Right, then you did the testpoint trick to get in EDL mode! Ofcourse now you can't use MiFlash with clean all to flash your device since your device is now in brick state. Only solution now is to find the factory images of your device, along with an authenticated prog file then use QFIL to force flash into device. You may inbox me if need further instructions!
Click to expand...
Click to collapse
Sir, I have exact same device and I am also stuck in edl mode. It looks there are no patched firehose files for violet. Is there any possible way you can help??
hi please help me ...my oneplus 9 fully bricked ...i cant go fastboot mode or recovery mode .....can anyone suggest me what to do now
SABBIRAHMED93 said:
hi please help me ...my oneplus 9 fully bricked ...i cant go fastboot mode or recovery mode .....can anyone suggest me what to do now
Click to expand...
Click to collapse
Find correct msm tool in threads run on device.
SABBIRAHMED93 said:
hi please help me ...my oneplus 9 fully bricked ...i cant go fastboot mode or recovery mode .....can anyone suggest me what to do now
Click to expand...
Click to collapse
Sorry but... how? I end up deleting crucial partition, but the i resurected the phone 5 minutes later. Just MSM...
was your OP9 a t-mo variant ?
barguybrady said:
was your OP9 a t-mo variant ?
Click to expand...
Click to collapse
no
Sheldd said:
Sorry but... how? I end up deleting crucial partition, but the i resurected the phone 5 minutes later. Just MSM...
Click to expand...
Click to collapse
can you provide me the msm file link
I have inly the fastboot menu left i need bugjaeger command to load or reflash oroper boot or recovery alont eith proper said files
Im not sure how it happened i didnt unlock critical files thankfully
I just know my commands are close to reflashing it but the good morning menu that says the bootloader is unlocked and software Integrity cannot be guaranteed just gets stuck and loops for recovery and edl and still allows the other phine into bugjaeger via fastboot on the oneplus 9 and then loops