Hello,
I've ****ed up my op nord.
The phone was running lineage 17.1 verison 29-7, I did a lock of the bootloader.
Now it's locked with the message 'your device is corrupt. It can't be trusted and will not boot.'
When I try to boot as with the power/volume up combo it show the 'Qualcomm CrashDumpMode screen
I tried to unbrick it using the EDL method, but the phone doesn't boot in EDL mode.
I've followed the instructions as written on https://www.getdroidtips.com/unbrick-oneplus-nord/.
However, the phone doesn't boot in EDL mode.
Any suggestions how to proceed?
Hi,
I facing same issue with OnePlus 9R device. I found on internet that EDL can be triggered from hardware as well. So there’s still a hope.
In case if you have resolved this issue, please let me know
i used to be able to have custom rom on this phone but i tried updating the custom rom but it put the phone in a boot loop. then i used msm download tool which got me on stock. then stock updated on its own overnight and now i cant enter edl mode. idk what to do. any help is appreciated
Related
I was on Masik X 4.1. Phone was working just fine.
I downloaded Masik X 5, installed it over 4.1. Flashing goes very well but at the end phone become dead.
No response on USB, No Driver on PC at all. Phone is complete dead.
Just noticed that I mistakenly downloaded "Masik P Tulip.zip" and flashed it blindly. There was no warning regarding File Mismatch in TWRP.
Very very bad luck.
I manged to bring phone into EDL Mode by testpoint method. Phone flashed successfully with both Qfil and Miflash.
Flashed many many times, tried all files available on different threads but phone is now permanently stuck in EDL mode and dont reboot after successful flashing.
Phone flashed successfully every time but I cant get rid of EDL Mode aka Qdloader 9008.
Plz help me to get my phone out of Qdloader 9008 mode.
Anybody please help me.................................
press power button for more than 30 seconds to get out of edl mode.
yawarniazi said:
I was on Masik X 4.1. Phone was working just fine.
I downloaded Masik X 5, installed it over 4.1. Flashing goes very well but at the end phone become dead.
No response on USB, No Driver on PC at all. Phone is complete dead.
Just noticed that I mistakenly downloaded "Masik P Tulip.zip" and flashed it blindly. There was no warning regarding File Mismatch in TWRP.
Very very bad luck.
I manged to bring phone into EDL Mode by testpoint method. Phone flashed successfully with both Qfil and Miflash.
Flashed many many times, tried all files available on different threads but phone is now permanently stuck in EDL mode and dont reboot after successful flashing.
Phone flashed successfully every time but I cant get rid of EDL Mode aka Qdloader 9008.
Plz help me to get my phone out of Qdloader 9008 mode.
Anybody please help me.................................
Click to expand...
Click to collapse
AFAIK , there's no such things as "automatically reboot after successfully flashed the device"
I was also in this condition but with different phone (it was Redmi 4 Prime (markw)), and all I did is just disconnect the battery form the circuit and then replug it, then I can boot to the system successfully
Hope it helps, but if it isn't then maybe something wrong
I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
through fastboot
I am using the universal fastboot and adb tool and trying to flash boot twrp and start over
current error: failed remote recovery a no such partition
after fastboot --set-active=b
same error
update 2
somehow, after simply trying over and over i got twrp on partition a
i think i will stay here until a kind member can direct me to an img that will work
thank you
marcadamf said:
I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
Click to expand...
Click to collapse
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
blas4me said:
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
doing so now...
thank you for the help.
I somehow got it up and rooted.
will msm work while rooted or mess up root?
I have a gm1915 wich is not listed in the link for the drivers? any thoughts?
These should work. As for MSM tools use the international version.
If you can't shut off device, hold power + Vup for about 10 seconds without being connected to a power source. If your fast enough, keep device plugged, and just press Vdown, to boot recovery.
https://drive.google.com/file/d/1JoHF6RF1THVn3pQWywaJz2URGTPxL2pH/view
not sure where you are at right now, but i installed a wrong os version (android 10 on my phone with pie on it). It would only boot into fasdtboot screen no matter what I did or tried. Could not get adb to recognize it, had no twrp or rom installed correctly. No way to fix it, could not use MSM tool as phone had to be able to be shutoff, which mine couldn't. never recognized it due to that. tried drivers to no avail. not really many answers out there, til I found out about fastboot roms.
check out this page: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
* IMPORTANT: in above link, remember to only download the OS version that fits your phone previously. DO NOT try to update your phone to a different version using that method. Also this method will NOT work on a branded phone, so if your phone is originally a T-Mobile phone then unfortunately this is not a solution for ya.
You may also want to check out this page as well: https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/
I hope this helps. The Fastboot Rom solution worked for me, it saved me from throwing my phone in the trash. I ran the bat file and it did the rest.
Hi. My phone is realme 5 pro and I've been using custom rom recently and decided to go back to stock rom. I was successfully able to go back to stock rom and then tried to flash a custom kernel which destroyed my boot.img . I was confused on what to do and accidentally locked my bootloader. Now my phone will only turn on and turns off for around 20 seconds. I can't perform fastboot, recovery mode, or open my device. I did some research and found that the only way to restore my device from its state is using edl mode(which I don't know how to use). I follow some tutorials about edl and I was able to make my device appear as "QUALCOMM HS-USB QDLoader 9008" and doesn't know what to do next.
Can I still be able to revive my device without going to a repair shop? And if possible, can you guide me?
Any answers will be appreciated!
To flash device in EDL mode you need to use msm tool then flash your stock ROM.
You need proper driver to use msm tool with your device while in EDL mode.
If you're not sure what you're doing then just give it to a professional.
Goodluck.
I brick realme 5 last year and I give it to repairing shop they opened whole parts and fixed why how that happens?
SAAAAAMMMEE Problem !! did you find a fix ?
Hello XDA Members,
Please help me i have hard bricked oneplus 8 IN2017 Tmobile while installing Custom pixel Experience ROM
and now MSM tool Unbrick tool not working its shows download complete but phone is not booting after showing oneplus logo phone goes to EDL mode.
also i am not able to flash stock fastboot rom because bootloader is locked. Please help me how to unbrick this phone
Try MSM again, on a different PC and with a different USB cable *if* you can.
Aside from that contact OnePlus.
Was this your first time using MS download tool? Have you succesfully flashed to stock with MSM before?
yes i have used msm many times and tried on different PCs nothing is working
msm tool shows successfully download complete and now i am receiving this error (PIC attached)
i think i have messed up partitions.
Hi, I accidentally bricked my phone flashing the wrong image.
Now i can't turn off the phone, cant access to recovery or fastboot. (device doesn't respond when i click any button).
'Poco' logo is in loop. Anyone knows a way to install a ROM? Any way to access fastboot in this situation?
Try pressing the buttons for a long time. It resulted for me to get to recovery mode, but no to download mode. Sometimes it works.
I bought a poco x4 gt like that too, hoping to get it fixed, I believe the way to get it is via EDL mode and miFlas, but for now miflash still doesn't recognize the image of the poco x4 gt. I hope that in some future update I will recognize it.
i have same problem
Same problem here
did anyone was able to find a fix? or at least locate the test points for EDL?
mtk devices use a different way to access edl mode. in my case I access the edl mode, the computer recognizes it, the software recognizes it, but when running it says that SPflash still does not work with the scartter version of the rom that I downloaded
how did you manage to boot into edl mode? i tried several hw key combinations but it gives me "preloader handshake failed" or several BROM error.
i think my scatterfile seems ok. its just the brom/edl connection.
when you turn it on with the volume button less pressed and it connects quickly to the pc install the MTK driver and then run the python where it will read the brom
Mine already fixed
butaw1 said:
Mine already fixed
Click to expand...
Click to collapse
what did you do?
if any one want to fix his poco x4 gt bootloop only. can't reach fastboot or recovery. at first you need auth to bypass dim 8100 security. i found a person on github name Rafon he fixed my phone and it's working perfectly right now. his username on telegram is @Rafon24
same issue
the only way of fixing is through an authorized xiaomi account sadly
i however found a way to turn it off when nothing works:
press all 3 buttons (volume up, down and power for like 20 seconds)
and then it will turn off