Related
Hey guys, I've hardbricked my Xiaomi Mi 4i...
the device can't boot into fastboot mode
no led
no charging animation
doesn't get recognized by pc
only blank screen...
i've already done some researches about testpoint method of unbricking it... But unable to find the testpoints of the device... help me guys...
rid_rudro said:
Hey guys, I've hardbricked my Xiaomi Mi 4i...
the device can't boot into fastboot mode
no led
no charging animation
doesn't get recognized by pc
only blank screen...
i've already done some researches about testpoint method of unbricking it... But unable to find the testpoints of the device... help me guys...
Click to expand...
Click to collapse
Are you still able to start a fastboot flash?
If so (or you don't know) go to the Mi site and download tha stable global rom and try to fastboot flash it.
http://en.miui.com/thread-138228-1-1.html
no
no fastboot mode access...
rid_rudro said:
no fastboot mode access...
Click to expand...
Click to collapse
But can you start the fastboot via Volume Down-Power buttons?
So power down the phone, push Volume Down and keep it pushed.
Then press Power until you see the MI logo.
Release the power button, but keep the Volume down button until you see the Fastboot screen.
If that works, connect the phone to the computer and try again via fastboot flash.
elot01 said:
But can you start the fastboot via Volume Down-Power buttons?
So power down the phone, push Volume Down and keep it pushed.
Then press Power until you see the MI logo.
Release the power button, but keep the Volume down button until you see the Fastboot screen.
If that works, connect the phone to the computer and try again via fastboot flash.
Click to expand...
Click to collapse
read it carefully... the phone is hardbricked.... you can't access to fastboot mode in any condition... if i had access to fastbot mode then i didn't have to post this thread...
if yu know any other procedure of unbricking it, please help..
rid_rudro said:
read it carefully... the phone is hardbricked.... you can't access to fastboot mode in any condition... if i had access to fastbot mode then i didn't have to post this thread...
if yu know any other procedure of unbricking it, please help..
Click to expand...
Click to collapse
Sorry, i missed that in the opening post.
Most people call it bricked when it is not, i was assuming that in this case too.
Sorry.
In this case i cannot help you, i don't have that info.
When it comes to a hard bricked device, I'll just go to a Xiaomi Service Center in the nearest place around me.
I don't really know about Xiaomi's warranty policy, because they're vague. They don't have a clear policy for rooted devices. For Samsung they will void your warranty when they know it's rooted, but it's not clear in Xiaomi's case. I heard a rumor, though, that rooting doesn't void your warranty on Xiaomi, but if you want to keep to the safe side, do this.
Go to the nearest Xiaomi Service Center in your country, don't forget to bring your warranty card or at least a receipt of your Mi 4i purchase. Take your time waiting for your turn, and then when you're called, go to them and say that your phone won't turn on. If they ever ask you of what happened, just say that you want to update your MIUI version (don't mention that it is rooted), it is successful, but when you want to reboot it, it just shuts down and won't budge.
If you ever asked whether your phone is rooted or not, just say that you don't know anything about root.
How'd you bricked it? Can you explain
sharan.nyn said:
How'd you bricked it? Can you explain
Click to expand...
Click to collapse
yes, i've HARDBRICKED it...
Kreaz said:
When it comes to a hard bricked device, I'll just go to a Xiaomi Service Center in the nearest place around me.
I don't really know about Xiaomi's warranty policy, because they're vague. They don't have a clear policy for rooted devices. For Samsung they will void your warranty when they know it's rooted, but it's not clear in Xiaomi's case. I heard a rumor, though, that rooting doesn't void your warranty on Xiaomi, but if you want to keep to the safe side, do this.
Go to the nearest Xiaomi Service Center in your country, don't forget to bring your warranty card or at least a receipt of your Mi 4i purchase. Take your time waiting for your turn, and then when you're called, go to them and say that your phone won't turn on. If they ever ask you of what happened, just say that you want to update your MIUI version (don't mention that it is rooted), it is successful, but when you want to reboot it, it just shuts down and won't budge.
If you ever asked whether your phone is rooted or not, just say that you don't know anything about root.
Click to expand...
Click to collapse
the fact is, i have no xiaomi service cnter n my county..
Since you don't have service center. You'll have to unbrick it yourself. First thing you have to find is the download points for the mi4i. I would suggest posting this thread on MIUI forums.
sharan.nyn said:
Since you don't have service center. You'll have to unbrick it yourself. First thing you have to find is the download points for the mi4i. I would suggest posting this thread on MIUI forums.
Click to expand...
Click to collapse
well, i've done that too.... i have done a teardown but i was unable to find any testpoints in my mi4i... and the forum guys also don't know anything
rid_rudro said:
yes, i've HARDBRICKED it...
Click to expand...
Click to collapse
You are certainly giving us a lot of information to work with helping you...
If you want any chance of help, tell us EXACTLY what you did/were trying to do.
And yes, we already know that you HARDBRICKED your device.
I read it carefully and was able to extract that much of information from your posts.
Phobos0815 said:
You are certainly giving us a lot of information to work with helping you...
If you want any chance of help, tell us EXACTLY what you did/were trying to do.
And yes, we already know that you HARDBRICKED your device.
I read it carefully and was able to extract that much of information from your posts.
Click to expand...
Click to collapse
i was flashing a fastboot rom with miflash... before the flashing ends somehow the device got disconnected, from that moment no fastboot mode...
Since the installation was interrupted. The partition of eMMc is probably messed up.
So the only solution you have to get the phone to download mode. Don't hit and try test points. Curiousity kills
Even if you get it to download mode. You must have a partition image. Which can be obtained from someone's working mi4i. It would be a huge image. Somewhat around 16gb so it's not possible to upload such a large file
You can try to get some info from here http://forum.xda-developers.com/yureka/help/question-qualcomm-download-mode-k-t3068040
Hi! I have exactly the same problem. I was trying to find the test points in order to put the phone in fastboot mode. Are you sure this method doesn't work with the Mi4i?
juan.karl said:
Hi! I have exactly the same problem. I was trying to find the test points in order to put the phone in fastboot mode. Are you sure this method doesn't work with the Mi4i?
Click to expand...
Click to collapse
Even if you find the test points. You cant access Fastboot mode. It actually puts it to download mode
.
sharan.nyn said:
Even if you find the test points. You cant access Fastboot mode. It actually puts it to download mode
.
Click to expand...
Click to collapse
What's exactly "download mode"? Is there any option to fix this problem?
maybe this post can help -
http://forum.xda-developers.com/redmi-1s/general/how-to-revive-hard-bricked-xiaomi-redmi-t2964490
http://forum.xda-developers.com/mi-2/general/restored-hard-brick-problems-t3139766
Hey Bro u say their is no led? I also did hardbricked my MI4i ,no fastboot ,no recovery but atleast my phone have fade blinking red light when connecting to chrging.
So,if ur phone have a blinking red notification light then its possible to revive it.
But if no led thn its not.
And possibly if their is no hardware issue then definately led light is blinking.
so please tell ......light is blinking or not.if yes then i wil provide u solution for hardbricking MI4i without touching pin points.
Hi my name is Miguel and im new to xda and i have a serious problem so i bought my phone and i was using it a mp3 and stuff since i live over seas i tried to region unlock it and in the process bam phone restarted and nothing but a black screen i plug in my phone to my charger nothing happens i plug it in to my pc something happens but not on the phone but on the pc it started downloading drivers i can tell you what the bubble said because i came to europe for vacation and im staying here for a while but a friend of mine said your phone lost his boot-up and it wont do anything unless you buy a medusabox and get all the files im buying the medusabox or whatever but where can i get the files from he told me you need 4 files with ones are they any ideas?
What were you doing to region unlock it?
If you hold down the bixby, power, and volume down buttons, can you get into download mode?
I too am in a similar situation. Not trying to highjack the thread at all however I believe it's what they call EDL (Emergency Download Mode). Mine is in Qdloader 9008 but cannot use QFIL to flash it so stuck with this brick for now. The files, I have some XMLs and supposedly the programer but they haven't worked for me at all.
Good luck, please advise if you ever fix it cause I have faith and hope its just a matter of time i can unbrick mine.
ragarcia87 said:
I too am in a similar situation. Not trying to highjack the thread at all however I believe it's what they call EDL (Emergency Download Mode). Mine is in Qdloader 9008 but cannot use QFIL to flash it so stuck with this brick for now. The files, I have some XMLs and supposedly the programer but they haven't worked for me at all.
Good luck, please advise if you ever fix it cause I have faith and hope its just a matter of time i can unbrick mine.
Click to expand...
Click to collapse
Im trying to use medusabox which is what people use to recognize qualcomm mode i just need the file to install the bootloader to get it into download mode any ideas if i can get them from another s8+
The file that ur looking for isn't apart of the stock firmware? BL,AP,CP,CSC, and PIT. I think the one ur looking for is BL for bootloader. You shouldn't need a box to recognize 9008, this is something ur phone should do automatically when u plug it in while hard bricked thought that all of the boxes were made to be able to flash ur device while in EDL mode?
[LEFT[/LEFT]
huawei asker/fixer said:
Im trying to use medusabox which is what people use to recognize qualcomm mode i just need the file to install the bootloader to get it into download mode any ideas if i can get them from another s8+
Click to expand...
Click to collapse
Brittanyporter said:
The file that ur looking for isn't apart of the stock firmware? BL,AP,CP,CSC, and PIT. I think the one ur looking for is BL for bootloader. You shouldn't need a box to recognize 9008, this is something ur phone should do automatically when u plug it in while hard bricked thought that all of the boxes were made to be able to flash ur device while in EDL mode?
[LEFT[/LEFT]
Click to expand...
Click to collapse
This is very old but no all bricks dont leave in edl the devices also have groind points. All of us that tested the edl repair use qfil or the recovery script which i use on mine. You need a bit more than just the bootloader for repair. A whole barrage of sperate partitions as well as the programmer xml
https://drive.google.com/file/d/1CFRc7RljFHX1oN4WdDLUR3b3BmaGnNAc/view?usp=drivesdk
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
kool_am said:
Hey guys. I need some help. this is my wrong doing !!
I got a network unlocked T mobile which I started using with AT&T. Today I received the unlock code from T mobile to unlock bootloader which I did. then I I installed TWRP and Magisk without any issues. then I tried to fix the persis.img coz fingerpritn is not working. it didnt work so I left it alone. But I dont know why I wiped cache, data and then phone got stuck at boot loop. (no backup). I tried to install using MSM tool but it didnt work. MSM tool was not detecting the phone. then in TWRP I clicked on EDL and now the phone screen is blank. tried every possible combination of keys but no luck. was doing all this on windows 10. any help would be greatly appreciated. thanks
Click to expand...
Click to collapse
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
kool_am said:
So it turns out its not a hard brick. I'm stuck on TWRP. I'm able to get to fastboot. I tried to install Oxygen OS thru fastboot but the PC is not detecting the phone in fastboot. Mac detects it but I believe all the stock Roms are for PC use. I did try it on my MAc and was able to open a terminal window inside the Oxygen OS folder but then the fastboot device command is not found. any help would be greatly appreciated. I installed SDK and ADB drivers on PC but in device manager the device still only shows as Android device with no drivers. !! thanks
Click to expand...
Click to collapse
Solved !
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
JCroffut said:
solved how? i greatly would like to know how to flash from fastboot, i know that isnt what this thread was about but im having the exact same problems you are with msm. i can see the phone in fastboot but i have no idea how to flash or what to flash from there. I can get into recovery but i cant copy anything over to the phone and the drivers dont show up for adb. so i pretty much ONLY have fastboot and dont know what to do! 2 days since the phone been down and im lost AF
Click to expand...
Click to collapse
Can msm detect the phone when connected in fastboot. Also check device manager in pc to make sure it detects the phone as qualcomm device. Otherwise msm will not work.
Download msm. Turn phone off. Connect phone to pc. Open msm. Press start. Press volume down and power button on phone. It should be detected by msm and should start flashing the software.
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
JCroffut said:
Standby....
When plugged in the phone in EDL it shows
QUSB_BULK_CID0412 with an exclamation mark inside a yellow triangle
When i plugged in the phone and open fastboot it shows
Android with an exclamation point inside a yellow triangle
I booted up msm, clicked other, clicked start, pressed volume down and volume up and plugged it in. still says waiting for device to connect. ive also tried this with a number of keys being help, ive tried to boot from twrp straight into edl mode, none of which works
which all says to me its a driver issue of some kind, but for 3 days ive been slaving away on xda and cannot for the life of me figure out where to get the drivers.
Click to expand...
Click to collapse
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
kool_am said:
It is a driver issue for sure. When connected device manager should detect as qualcomm hd9008.......
Click to expand...
Click to collapse
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
JCroffut said:
i figured that, i am at a complete loss as to where to find the drivers. i actually might need you to hold my hand on this one a tiny bit because im about to smash the phone on the ground and say someone stole it. thats where i am with this phone haha
Click to expand...
Click to collapse
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
standby ill read through it now. we also have 2 different threads going so i can combine them if thats easier for you
kool_am said:
qualcomm hs-usb qdloader 9008 - this is the exact name of the driver.
Try this link: https://forum.xda-developers.com/t/guide-fixing-hard-bricks-qualcomm-hs-usb-qdloader-9008.3403868/
Click to expand...
Click to collapse
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
kool_am said:
Only download the qualcomm driver from this link. Or search for it online.
I have spent much more time than you trying to figure this out. I have a pc and Mac both. Mac is not compatible with a lot of the software and my pc usb ports are all bad. Point being, leave it alone for a day or so. Come back at it with a fresh start and fresh mind.
Click to expand...
Click to collapse
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
kool_am said:
If I were you, I wouldn't throw the phone away. Like I said it's a simple issue of driver. Install the correct driver and make sure you see it as qualcomm device in device manager. Trust me, from then on, it's just a matter of a few clicks.
I unbricked my phone to t mobile and then converted to global rom without any issues.
Click to expand...
Click to collapse
i sent you a private convo on here if thats ok so i dont spam the forum! You may be able to help me out if i could borrow a few minutes of your time!
JCroffut said:
i hear that. after 3 days of non stop working at it im pretty sure im just not smarter than the phone today lol. looks like this phone is now stolen and going into a trash can lol
Click to expand...
Click to collapse
i was definatly kidding tho this is my only phone and i have to solve this problem lol
I'm not sure if you have read this thread already. I messed up my phone a couple days ago as well and follow the steps there and was able to MSM my phone back to stock.
[OP8][OOS TMO 55CB] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
I try all commands and procedure like volume+/- and power button all things but still screen is black and when i connect it to pc in manager it show me qualcomm 9008..
And when i flash it with msm tool oneplus 9 msm tool india it always show me error
Wrong suggestion, so I edited it out. Good luck unbricking
noname122414 said:
Wrong suggestion, so I edited it out. Good luck unbricking
Click to expand...
Click to collapse
How?
I saw in another post that you are aware of your chinese version. So you probably already tried flashing this version ( https://forum.xda-developers.com/t/official-oneplus-9-oxygen-to-color-and-back.4256457/ ) just patch the to Oxygen again on the chinese version.
How i can patch i told my phone is stuck in Edl mode hard brick
So no fastboot commands are working? Fastboot devices says nothing? Say what you tried, and your current situation in as much detail as possible. People can only help you when they understand what happened and what is still possible to do.
Brother my device is stuck in Edl mode because when i connect to pc it show me qualcomm 9008 in device manager..
I tried all Fastboot commands, power + , power - button & power button but nothing happened still device stuck in Edl mode and also msm tools of india doesn't work
Did you ever get a good flash from msm tool? If not try the original chinese version phone came with.
Also you can try holding power button until phone reboots but nothing to boot too will just go back to edl.
Y
nujackk said:
Did you ever get a good flash from msm tool? If not try the original chinese version phone came with.
Also you can try holding power button until phone reboots but nothing to boot too will just go back to edl.
Click to expand...
Click to collapse
Yes i use msm tools many time on another devices it works but on this case it doesn't work on oneplus 9
Wolverine619 said:
Y
Yes i use msm tools many time on another devices it works but on this case it doesn't work on oneplus 9
Click to expand...
Click to collapse
Sorry bud, if you can't get a good flash with msm you're stuck far as i know.
nujackk said:
Sorry bud, if you can't get a good flash with msm you're stuck far as i know.
Click to expand...
Click to collapse
Do you told me about solution?
My phone battery was 100% when it's stuck in Edl mode any idea for 100% to 0%?
Holding the power button an unreasonable long time always worked for me did it with 6 and 7pro. Even if it goes back to edl if you have msm ready and waiting for device v when it reboots to edl should pick it up and begin flash
nujackk said:
Holding the power button an unreasonable long time always worked for me did it with 6 and 7pro. Even if it goes back to edl if you have msm ready and waiting for device v when it reboots to edl should pick it up and begin flash
Click to expand...
Click to collapse
See brother
I see what you mean. Not sure what sahara error state is. Not sure you'll be able to fix that on your own. You may need to contact oneplus see if they can help. They tend to be willing to help in most cases. But may cost you since I'm sure this wouldn't be covered under warranty.
sahara error usually happens when you flash the wrong firmware.
noname122414 said:
sahara error usually happens when you flash the wrong firmware.
Click to expand...
Click to collapse
Can anyone tell me how to fix it?
Did you try everything what's written here? https://blog.hovatek.com/how-to-fix-sahara-fail-error-in-qfil/ when nothing there first with your problem then write here again.
noname122414 said:
Did you try everything what's written here? https://blog.hovatek.com/how-to-fix-sahara-fail-error-in-qfil/ when nothing there first with your problem then write here again.
Click to expand...
Click to collapse
I don't have file's for oneplus 9
Any one know how to extract .ops file of Msm tool
Wolverine619 said:
I don't have file's for oneplus 9
Any one know how to extract .ops file of Msm tool
Click to expand...
Click to collapse
"Payload dumper 64" can get the files for you that's an application there is also a python script which does the same.
I personally used "payload dumper 64" then flashed the files vis fastboot to recover 2 Chinese variant until now( you have to use the right rom which is normally used to switch from Chinese rom to Oxygen)
This is just how I recovered the phones.
Edit: sorry it's late you are probably looking for the msm download tool files, I probably messed things up
Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
alp47470 said:
Hello everyone,
History : So i was using Rice driod on my OP 8T peacefully and i got an update on the rom. i installed the update via local update of the rom and after reboot the phone never booted back. i tried all button combos to make to boot anything like fastboot or recovery etc but nothing worked.
Problem : While connecting to PC the device shows as "Qualcomm HS Diagnostic 900E" I know it should show as 'qualcomm hs loader 900' something which indicates EDL state. So i can't perform MSM. There are not port showing in MSM either. Its blank. Even after forcefully trying to boot EDL ( button combos ), it always boots back to same state.
Fixes i have tried : Reinstalled qualcomm drivers many times, also tried many other versions of MSM including the Hydrogen OS one. No solution.
Can anyone please help me with this situation. Its been few days now and i have really no hope left with the device.
Click to expand...
Click to collapse
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
LR7875 said:
complete noob here but I have heard someone said they fixed using indian msm tool, maybe I am wrong, idk
Click to expand...
Click to collapse
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
does the computer even detect your device? what name of the device does it show up
alp47470 said:
I have tried MSM already no fix as it doesn't detect the device in EDL state. Hence no port shows up
Click to expand...
Click to collapse
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
LinhBT said:
1st, make sure your device is connected and recognized as 9008 HS-USB QDLoader.
2nd, try using MSM of 9R Ported ROM for 8T, it works in almost every situation
Click to expand...
Click to collapse
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
just a long shot, as i am on a 5t not the 8, but has windoze perhaps updated and "fixed" the usb driver on your behalf?
my 5t was invisible after unlocking, until i forced windoze to update the driver to an unsigned (working) version
[EOL][11.0][OFFICIAL] LineageOS 18.1 for Oneplus 5 & 5T
Is there anybody out there!🤭
forum.xda-developers.com
alp47470 said:
The 1st one is main problem. It doesn't recognise as 9008 HS-USB QDLoader, it always keeps showing to 900E mode.
Click to expand...
Click to collapse
That's a total different device state, it's on Diag mode, not EDL mode. Try to turn off the device COMPLETELY, then either using hardkeys ( VOL + VOL - press and hold at the same time, plug in cable ) or use Deep-Fash cable to put the device into correct EDL 9008 mode.
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
alp47470 said:
So, guys i was finally able to fix the device by EDL point method. Somehow the device was able to boot to edl anyhow. The drivers were correct and so was the cable etc, Thank you all for still helping me.
So relieved so my 8T alive again.
Click to expand...
Click to collapse
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
BillGoss said:
Could you please be more specific as to how you got it to connect in EDL mode - it would help others who end up in the same situation.
Click to expand...
Click to collapse
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Thanks for sharing that - much appreciated.
alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel.
Click to expand...
Click to collapse
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
LinhBT said:
So the localshop is using Testpoint trick. It has the same effect as using Deep-Flash cable but more trustable, only that u will have to open the back cover.
Congrats on successfully rescue the device mate
Click to expand...
Click to collapse
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly identical also have same EDL points on motherboard. Same positioning too.
alp47470 said:
Thanks bro. Actually the shop kepper didn't do anything. Instead he was saying that the battery was damaged or something (probably scamming me) or he actually didn't had any idea for real. I had read about EDL point thing, so i just asked the shopkeeper to just remove the back panel. Rest i came home and did everything lol. NGL it was scary as hell.
In the process i also discovered that 8T and 9R being mostly idenical also have same EDL points on motherboard. Same positioning too.
Click to expand...
Click to collapse
Ah I see, same here when I 1st try the Testpoint trick few years back, scary as hell cuz that was the only phone I had at that time ))))
Btw, yes, 9R and 8T shares almost everything besides of SOC's name ( Snap870 in fact is Snap865 OCing ). That's why I told u to use the MSM Tool of 9R port ROM for 8T, it passes almost every errors u may face when using MSM of 8T itself!
alp47470 said:
As you know already the phone wasn't able to go to EDL mode no matter what i did. I really don't know what caused the issue and why it wasn't booting even after using button combos (both vol) or to power off manually (vol up and power) it was went to Diagnostic Mode.
Here's what i did :
-Went to local shop for removing the back panel by those heating machines
-Unplug battery
-Then used the EDL points on the motherboard to force the device to boot EDL (this method is more seen in Mi , Redmi phones)
-The device immediately recognised by just one tap on "enum" now.
Thats how i flashed the OS, plugged the battery and panel, reboot
Click to expand...
Click to collapse
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
NZX-DeSiGN said:
Hi, I'm the same boat after a bad flash of OSS12, hard brick, black screen, not detected in Windows devices manager, no vibration with every button combination ...
Could you share where the edl points are on the OnePlus 8T motherboard please ?
I would be eternally grateful!
Click to expand...
Click to collapse
Here.. hope it helps