Resetting stock ROM without usb port? - OnePlus 8T Questions & Answers

So I need to send in my 8T for trade-in. However, I'm running a custom ROM with unlocked bootloader so I need to flash stock to avoid getting denied.
Here's the problem. My usb port is broken and only allows for charging. I cannot use the MSM tool with my PC since it won't be detected. Yes I've tried everything, including cleaning the port. It's not a driver issue since it happens on multiple computers and my new phone is detected just fine.
Back in the day i used to do this all the time with Samsung phones (by downloading a ROM and flashing it in recovery from internal storage). Is it possible at all with a OnePlus? I can access Android just fine, my phone is not bricked. And it's already rooted.
Otherwise my only solution would be to either replace the usb port, or send it in with a custom rom and hope for the best.
I'd be so grateful for any help

sebas156 said:
My usb port is broken and only allows for charging.
Click to expand...
Click to collapse
- Press F to pay respects.
Well I don't know if this will help you or not... My 8T's USB connection is not stable too. But by enable ADB through devoptions, something on 8T restarts and I got a PC-recognizable USB connection back. I'm running LineageOS 18.1 / 19.1 (aka Android 11 / 12) on KB2007 and this method works on both version.
But if your PC can't detect it under EDL 9008 mode... Good luck with contacting OnePlus service center and I'll have my [ F ] key pressed...

IAAxl said:
- Press F to pay respects.
Well I don't know if this will help you or not... My 8T's USB connection is not stable too. But by enable ADB through devoptions, something on 8T restarts and I got a PC-recognizable USB connection back. I'm running LineageOS 18.1 / 19.1 (aka Android 11 / 12) on KB2007 and this method works on both version.
But if your PC can't detect it under EDL 9008 mode... Good luck with contacting OnePlus service center and I'll have my [ F ] key pressed...
Click to expand...
Click to collapse
Thanks for your respects
LUCKILY I was able to flash stock in the end. How? By trying to press the cable in 100 times. When I was just about to give up, suddenly my PC made the USB connection sound. Never was so happy to hear that sound lol. Idk what happened, but it got detected again. Well, a bit.
It took like 2 hours to get the MSM tool to work, since my device kept disconnecting during install. I bricked it 10 times over, but it worked!

sebas156 said:
Thanks for your respects
LUCKILY I was able to flash stock in the end. How? By trying to press the cable in 100 times. When I was just about to give up, suddenly my PC made the USB connection sound. Never was so happy to hear that sound lol. Idk what happened, but it got detected again. Well, a bit.
It took like 2 hours to get the MSM tool to work, since my device kept disconnecting during install. I bricked it 10 times over, but it worked!
Click to expand...
Click to collapse
LMAO
Congrats

Related

Partially bricked Mi4c mi-globe 7.2.9

Good day gents and ladies
Well let me start from the beginning.
I'm was using mi-globe 6.12.22
Last week Friday evening downloaded 7.2.9 mi-globe,read around the mi-globe forum.Didn't see anything funny so flashed via twrp on Saturday morning.Hmmmmmmmm this is when all my problems started.
Basically what I should of done is download 7.2.9,new 3.0.3 twrp for norgat,go into recovery flash new recovery, restart recovery,flash 7.2.9 and then have happy days.But it wasn't to be and now I'm basically sitting with a useless mi4c device.
The device works but warms up and I only get about 4 hours battery life.
If I try boot into recovery I just get black screen.
If I connect device to PC it is not recognized, have tried 3 x different laptop/PC's and different cables.
So fastboot,mi-flash,mi-unlock are all not possible as device is not recognized.
I have been trying different solutions without any success.
I think if it would be possible to root device directly without PC then maybe it will be possible to get flashfire working and I can flash new norgat recovery?
Any suggestions would be greatly appreciated?
NB.I have tried loading Qualcomm drivers ,google drivers etc etc.no luck can't connect my device too PC,either get device not recognized or the PC doesn't even see the device.Enable USB debugging etc etc nothing works.Been fiddling for 4 days!!!!!!!
Tried to root with kingoroot,framaroot directly on device etc nothing works?
Please help,else device is a nice piece of plastic that holds paper down on my table.lol
BR
Ant
have you tried fastboot
fastboot oem edl
Click to expand...
Click to collapse
then MiFlash to flash official rom
Fastboot don't work,as PC don't see the phone?
DeAntman said:
Fastboot don't work,as PC don't see the phone?
Click to expand...
Click to collapse
Is usb charging via pc working and have you tried miui updater? , This seems weird state you have ... If none working might be tried deep flash cable flashing ... Or go to nearest service center. Hope that help. Best luck.
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
DeAntman said:
Hi,yes USB chargers device via PC but that's all.
How does one deep flash,could you post link please?
I bought the device in China about 18 months ago,Xiaomi never sold mi4c in my country so doubt they could help me locally.
Seems I have soft bricked the device?Tried every thing no solution.
If it would possible to root without USB cable I could maybe try flash new twrp via flash fire?Then could wipe all and try start again?
Click to expand...
Click to collapse
You havent answered the miui updater part, have you tried flash miui rom.zip, using miui updater apps ?
Does fastboot mode boot on your phone ? i mean the bunny sceen showed up ?
For dfc here the link http://xiaomitips.com/guide/miui-deep-flash-engineering-cable-solution-to-non-edl-device/
Please take dfc as last resort. And do research more on this... Do with your own risk. Good luck
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
DeAntman said:
Hi,
Yes sorry I have tried updater, I download rom start updater it starts but after about 2 minutes stops and phones shuts down.
I then have to restart phone with long press of power button. It restarts but nothing has changed.
Wrt fastboot it goes into fastboot but this is useless cause no Pc can see my device and if it sees it it sees unknown device, spent countless hours trying different things without any success.
Seems have soft bricked the device, phone works but gets hot and battery life maybe 4 hours if I'm lucky?
Not sure what more today?
Click to expand...
Click to collapse
Before this has your pc able to use the miflash ? Try to follow this guide to setup it correctly http://en.miui.com/thread-136188-1-1.html ... I follow this guide and the adb n fastboot even works on an old pentium 4, 512mb ram, win xp laptop.
Ps: I think, its only a matter of incorrect driver setup on your side, best luck.

USB not working after flashing Lineage OS 15.1

Hi all, a couple nights ago I flashed Lineage 15.1-20180806 to my OPO and everything went smooth. This morning I tried to connect it to my pc to transfer some pics and to my surprise the PC doesn't recognize it.
It looks like the PC is "trying" to establish a connection because the led in the phone blinks really fast for some small periods of time. The phone isn't charging when connected to the PC either.
What I have already tried:
- I already enable USB debugging in developer options
- Set MTP as default usb configuration
- Tried 2 different cables and different usb ports in PC.
I will try again in another computer when I get home but, honestly, this doesn't seem to be a problem with my PC or the cable as those were the ones I used when I flashed the rom and I also used the same cable when I transferred files to the same PC in the past. The phone was running Lineage OS 13 before the flash I think.
Any idea what else can I try to get it to work? I'm afraid I will be attached to this rom forever since I won't have a way to flash another ROM right?
EDIT:
If I go into recovery mode (TWRP) and plug the usb cable the PC recognizes it and I can transfer my files. So I'm 100% sure this is on Lineage OS. Again, when I get home I will see if ADB works while in TWRP but still would like to know if any of you guys has had this issue solved.
Thanks!
do you have anything important on your oneplus one
kallum7 said:
do you have anything important on your oneplus one
Click to expand...
Click to collapse
Nothing so far. It will become a back up phone soon.
Hi you need to follow this guide https://www.google.co.uk/amp/s/foru...neral/guide-unbrick-oneplus-one-t3013732/amp/ and even though it says it is do not use for soft brick just use it anyways
kallum7 said:
Hi you need to follow this guide https://www.google.co.uk/amp/s/foru...neral/guide-unbrick-oneplus-one-t3013732/amp/ and even though it says it is do not use for soft brick just use it anyways
Click to expand...
Click to collapse
Thank you, will give it a try and report back later.
adrek09 said:
Thank you, will give it a try and report back later.
Click to expand...
Click to collapse
okay
Is Lineage OS 15.1 supporting VoLTE by any way.
Had the same issue... and had this issue always coming back, currently with LOS18 (some devices worked, others didnt - couldnt see a pattern).
I tried all the triggers like setting File Transfer, disabling USB Debugging - nothing worked...
...until I rebooted my device (a YT703L).
In the end, it should be either (not sure which one actually)
File Transfer - always on (in DevSettings Default USB) or
USB Debugging off (also Dev Settings)
AND reboot.

OnePlus 7 Pro not detected by PC at all (only in EDL/MSM mode)

Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
Edit 2: I'm able to use USB OTG to connect to a flash drive. It's so weird that it won't establish a connection with my PC...
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
Terkitoez said:
Hello All,
First some context:
I had recently flashed Havoc OS A10 using the installation instructions in that thread after coming from MSM Extended ROM A10, but found that none of my sensors were working and Warp Charge wasn't warp charging at full power. So I flashed persist.img for the OnePlus 7 Pro in hopes of resolving that issue, but that didn't work. So instead I decided to flash stock OOS 10.3.3. I flashed it to Slot A but could not do the same to Slot B. I don't remember what happened after that (I for sure didn't flash anything that was incompatible with my phone), but I ended up being able to use the MSMTool for OP7Pro to go back to Android 9 and losing TWRP in the process.
Now the issue:
Although I have booted normally into Android 9, my phone is not being picked up by my PC regardless if it is in normal mode or Fastboot mode. Nothing shows up in Device Manager, it doesn't even refresh or make a sound as it should when it detects a new device, even after enabling USB Debugging and cycling through the different USB Configurations within the Settings app. I've tried reinstalling drivers through the TOOL ALL IN ONE, but my phone is only detected in Device Manager as a Qualcomm device when I put it in EDL/MSM mode. I've also tried connecting it to two other PCs using 4 different USB cables to no avail.
My goal is to at least get it to be recognized by my PC when it is in Fastboot mode because I think I can recover it fully after fastbooting to TWRP or installing a Fastboot ROM. Has anyone experienced this issue before and were able to resolve it? I really hope I didn't super brick the phone as I just got it last week. Any help or advice would be greatly appreciated.
Edit: I was able to update it to OOS 10.3.4 using WiFi OTA, but the issue of no sensors and not being detected by the PC still persists. If it's useful at all I've added what I see in fastboot mode down below.
PRODUCT_NAME - msmnile
VARIANT - SDM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - (my serial number)
SECURE BOOT - yes
DEVICE STATE - locked
Warm regards,
Terkitoez
Click to expand...
Click to collapse
try cleaning out the port on the phone.
MrSteelX said:
try cleaning out the port on the phone.
Click to expand...
Click to collapse
Gave the port a good couple of blasts with compressed air, but still no luck. What's weird is that it gets picked up by my computer perfectly fine while in EDL mode. Thank you for the suggestion.
amirage said:
This is a very strange issue but have you downloaded and installed the official USB drivers for this phone?
Click to expand...
Click to collapse
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Terkitoez said:
Hi amirage, yes I've installed the official OnePlus drivers and the Google ADB drivers, but no luck
Click to expand...
Click to collapse
I have to wait for something in the usb to time out, then it will load. Often more than a minute.
Im having a similar issue, it seems like Win 10 is having issues with the drivers or something cuz I can see my phone on the PC but cant access the storage at all.
It's working now!
Apologies for the silence, but I was able to miraculously get the phone to finally show up in ADB and Fastboot. I'm not exactly sure what triggered the fix or the order of things I did to get it to show up, but I did multiple flashes of Android 9 through the MSMTool and reinstallations of the OnePlus Drivers and ADB drivers in different orders until it eventually showed up on my computer. I flashed latest OOS 10 after that, successfully unlocked the phone, installed TWRP, flashed persist.img (for OP7Pro) to be safe, and installed Havoc OS A10. Sensors and Warp Charging are back and working as they should be. Thank you all for the replies.

Poco f2 pro stuck on bootloop

Hey guys,
I am not a pro at android devices and debugging but have spent several days on tutorials on how to fix it.
The problem was as follows: My battery wasn't charging fast anymore with any adapter and cable. (i tried 3 stock poco f2 pro chargers and cables rated at 33W. It charges only full in 8 hours.
So i opened the phone and changed the USB charging port from the inside to see if this was the problem. Now it luckily charges but after installing software updates on the phone (i was on 12.0.3 and updated to 12.5.1. It worked for 10 minutes until I restarted my device. It is now stuck on MIUI logo and stays there forever.
aNow i accidentally turned off USB debugging in developer options to see if that would fix the slow charging problem. But because of this and my device is bricked and now my device is not reqognized by my laptop anymore so I can flash firmware to stock.
Does anyone know how i can actually boot it with stock firmware to unbrick my poco f2 pro?
Take it to authorized service center and let them try to fix it.
Django023 said:
Hey guys,
I am not a pro at android devices and debugging but have spent several days on tutorials on how to fix it.
The problem was as follows: My battery wasn't charging fast anymore with any adapter and cable. (i tried 3 stock poco f2 pro chargers and cables rated at 33W. It charges only full in 8 hours.
So i opened the phone and changed the USB charging port from the inside to see if this was the problem. Now it luckily charges but after installing software updates on the phone (i was on 12.0.3 and updated to 12.5.1. It worked for 10 minutes until I restarted my device. It is now stuck on MIUI logo and stays there forever.
aNow i accidentally turned off USB debugging in developer options to see if that would fix the slow charging problem. But because of this and my device is bricked and now my device is not reqognized by my laptop anymore so I can flash firmware to stock.
Does anyone know how i can actually boot it with stock firmware to unbrick my poco f2 pro?
Click to expand...
Click to collapse
can u boot into MIRecovery and fastboot?
are you able to open fastboot in phone?
Right set to fastboot and flash with mi tool
Hey huys,
Non of the above helped. I run fastboot mode on phone but phone not showing up on flash tool, probably because I turned off USB debugging?!
Django023 said:
Hey huys,
Non of the above helped. I run fastboot mode on phone but phone not showing up on flash tool, probably because I turned off USB debugging?!
Click to expand...
Click to collapse
No,Install the drivers with MIflash.https://forum.xda-developers.com/t/guide-use-xiaomi-flash-tool.4262425/
NOSS8 said:
No,Install the drivers with MIflash.https://forum.xda-developers.com/t/guide-use-xiaomi-flash-tool.4262425/
Click to expand...
Click to collapse
I can't, I get an error message in chinese
Update:
Hey guys,
I got a Poco f2 pro which I got an unlocked bootloader. I was running a rooted Poco phone and I don't know why but I accidentally turned off USB debugging in developers settings. When there was an operating system update it got stuck in a boot loop. The problem is I can only do a few things with this phone now which is: Turn on: It starts and gets stuck at the MIUI logo.
Turn on +volume up: Recovery mode = I can connect to WiFi and press download but it just keeps searching for updates and doesn't do anything.
Turn on + volume down: Fastboot = it shows fast boot is started but when plugged in my pc it doesn't find my phone.
Things I tried:
Install USB drivers, Xiaomi drivers - phone not showing
Installed Mi Pc Suite - Phone not showing
Installed MiFlash - Phone not showing
Tried different Pc's and laptops from Windows 10 and 11 - did not work
Tried different USB ports, 2.0,3.0 and type C - did not work
Does someone know how I can fix my phone and tell me what to do?
anyone has a clue what to do? I was able to boot to MIUI Rescue and connect to WiFi but it searches for update and then it says it couldn't find updates
MIUI-V12.5.1.0.RJKMIXM (N/A) -> ???
Django023 said:
anyone has a clue what to do? I was able to boot to MIUI Rescue and connect to WiFi but it searches for update and then it says it couldn't find updates
MIUI-V12.5.1.0.RJKMIXM (N/A) -> ???
Click to expand...
Click to collapse
try wipe data
NOSS8 said:
try wipe data
Click to expand...
Click to collapse
I did but after that nothing changes.
I think it crashed when going from android 10 to android 11 and maybe it is some sort of encrypted.
Django023 said:
I did but after that nothing changes.
I think it crashed when going from android 10 to android 11 and maybe it is some sort of encrypted.
Click to expand...
Click to collapse
Surely due to the root or coincidence the usb port is dead.
Try the EDL mode and download the qualcomm drivers (search on google) then connect the phone and see if it is detected.

Oneplus 8T HARD BRICKED ! HELP !!!

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

Categories

Resources