Couple of weeks ago I tried updating my MT7_L09 to Lollipop while playing Dota. I didn't read something properly and probably filled it with bad firmware. Anyway I was completely beat so I tried getting the local phone shop to repair it. They had no luck either.
A week after getting it back I thought I'd have another crack at it. Somehow I got fastboot to come up and very carefully tried to fix it. Read absolutely everything I could before flashing things. Lost fastboot again.
Current phone status is:
Normal start - Vibrate Once, Black Screen
Recovery - Absolutely no feedback, Black Screen
Fastboot - Vibrate Once, Black Screen
Three Button Hard Reset - Huawei Ascend logo forever. If I hold in the buttons for >20 sec (including power), I get a series of LED flashes upon releasing all the buttons (3x Green, 1x Red, repeated 3x). I read somewhere that this indicates modem failure or something?
Tried every MT7_L09 UPDATE.APP i could find to no avail. Tried running adb and fastboot against each device state. Tried multiple cables. Tried multiple SD cards. Tried multiple computers. Tried B328 just now.
Since I got an out of warranty screen repair a bit over a month ago, Huawei wants $44 for me to send the phone to their service centre in Sydney before they tell me how much it will cost to fix it.
Should I play dumb and try returning it to Vodafone or is their something I haven't tried?
Thanks for reading
Same.
News?
I ended up returning it to Vodafone and ~selectively~ telling the truth.
"It was updating and then it never turned back on. I charged it for days and got nowhere. I tried going into recovery mode and couldn't even get that working"
Vodafone lady marked my phone condition on the service form as "as new" under everything. They sent it off to Huawei techs who gave up and then a few days later I got given a completely new phone much to my shock.
Moral of the story is that the stock recovery beats any custom ones because if you don't have access to the 3 button reset you're screwed.
Good luck
My infuse was bricked, all rebooting over and over, so I decided to use GTG ultimate unbrick, and then a power outage happened and my phone was in the middle of it and now it has a black screen and has not even turned on. Before it was bricked it had full battery, and I have tried taking out the battery for a while and then putting it back in. My computer wont recognize any device now and the phone won't do anything. Any help?
dplant227 said:
My infuse was bricked, all rebooting over and over, so I decided to use GTG ultimate unbrick, and then a power outage happened and my phone was in the middle of it and now it has a black screen and has not even turned on. Before it was bricked it had full battery, and I have tried taking out the battery for a while and then putting it back in. My computer wont recognize any device now and the phone won't do anything. Any help?
Click to expand...
Click to collapse
Download mode jig or cascading boot.
Neither have the guarantee of working. The former requires building (taking apart a USB cable and popping in a 10k resistor between pins 4 and 5 IIRC - don't believe me if you go this way, look it up) or buying a jig, the other borrows/copies the first 80MB of the emmc of a working device via dd (so you need a friend with the same carrier device - which I assume is AT&T and not Rogers).
Good luck!
OfficerJimLahey said:
Download mode jig or cascading boot.
Neither have the guarantee of working. The former requires building (taking apart a USB cable and popping in a 10k resistor between pins 4 and 5 IIRC - don't believe me if you go this way, look it up) or buying a jig, the other borrows/copies the first 80MB of the emmc of a working device via dd (so you need a friend with the same carrier device - which I assume is AT&T and not Rogers).
Good luck!
Click to expand...
Click to collapse
Alright but where can I find how to do these to fix it? Would it be easier to just get a new device?
dplant227 said:
Alright but where can I find how to do these to fix it? Would it be easier to just get a new device?
Click to expand...
Click to collapse
Download mode hints / YouTube video on how to make a Jig; the cascading boot I linked earlier. If you want to go that route (cascade), you may want to scan that post, and reply back here on what you would need a fellow user to do (sorry, I'm doing a give-a-man-a-fish/teach-a-man-to-fish moment, may also call it a comprehension exercise ).
With all that said, and in regard to your last question, depends on what you call easier - for some the monetary option can be quite difficult. The decision (fix or replace) would be totally be up to you.
Your hand may be forced though. The Infuse turns five next month (based on original/official announcement), and the respective forums have been reminiscent of crickets for the past year.
I sold mine last year before I even knew about cascading boot, otherwise (and if I had the same carrier - mine was of the Rogers variety) I would have gladly helped (i.e. shared the cascade block file).
So I've been using my OnePlus for about 2 years. The phone was kept in a rugged armor case, never dropped nor was it ever exposed to any sort of moisture. The device was never rooted nor was the bootloader ever unlocked.
At the end of August 2020 last month I was using maps when it suddenly crashed and went into Qualcomm Crashdump mode. I thought not a big deal, xda would have a fix to this.
I came home and for two weeks I tried different builds of the msmdownload tool with different methods to revive the phone. None of them worked. The 9.0 build did end up booting the phone but only for a short while before it got stuck, shut off and went into crash dump mode again. I can only boot into fastboot mode and that only sometimes (ofc EDL mode as well).
Fed up, I contacted OnePlus and scheduled a remote session with them. As was no surprise they used the msmdownload tool as well (build 10.3.0). And it obviously did not work and adviced me to visit the nearest support center. Unfortunately there is no service center nearby in my country so I dug deeper trying to find people with similar issue. Now this is the funny part.
On the brands own community app I found 5-6 other people who faced the exact same issue. They tried everything and when nothing worked they eventually went to the service center and were told that apparently the motherboard needs to be changed and it will cost as much as the phones value in today's date. Here's the interesting fact. All these 6 users were on the latest OOS 10.3.5 and faced this issue in the span of those 4 weeks. August to September of 2020.
The purpose of this thread:
1) To diagnose the issue with the help of the xda community as I believe that there is no way that the mobo could get fried this way.
2) To possibly find a solution as the phone is in absolute scratch less condition.
3) and most important, to find other people than those 6 who have faced this exact issue in the past couple of months so that it could be raised with OnePlus. Im hoping that OnePlus could at least diagnose it and release a tool for the fix if there are enough of us. Wishful thinking maybe but worth a shot.
Hoping for your support. Peace.
Guess what might be 7th person. My oneplus 6 keeps shutting down all of a sudden and some times even wont start or something might start but again goes off while booting. So, then i have to start it after 10 mins and so and start it again and that too wait for 5 to 10 mins after starting before start using it or else it goes off again. Cant use it for heavy usage any more like before. Sometimes even turns off all of sudden. i have used all msm tools to reinstall but no use. Funny thing is while evening setting up the phone after flashing it goes off. Dont no if its hardware problem or not. I also have not dropped my phone.. Can any one find whats the problem?
@ms2020 has the same exact problem as you describe here but on 6t. We did all we could. I even tagged osmosis and he said if msm tool won't work then unfortunately it's a no go...
Same problem here. I have two OnePlus 6. One has OOS 10.3.5 with a locked bootloader, the other one has a custom rom.
6 weeks ago I was using google chrome on the one with OOS and suddenly the phone froze for few seconds and went to crash dump mode. I tried every msm tools version and every suggestions I found, but none of them worked.
The one with custom rom hasn't had any problem so far.
flash713 said:
@ms2020 has the same exact problem as you describe here but on 6t. We did all we could. I even tagged osmosis and he said if msm tool won't work then unfortunately it's a no go...
Click to expand...
Click to collapse
@saban56
When did you lot face this issue? I'll be raising the issue with OnePlus. Hopefully they could diagnose this and release some tool to fix this if there are enough people out there.
yawarkhalid said:
@saban56
When did you lot face this issue? I'll be raising the issue with OnePlus. Hopefully they could diagnose this and release some tool to fix this if there are enough people out there.
Click to expand...
Click to collapse
I think it was around August 19th or 20th.
yawarkhalid said:
@saban56
When did you lot face this issue? I'll be raising the issue with OnePlus. Hopefully they could diagnose this and release some tool to fix this if there are enough people out there.
Click to expand...
Click to collapse
This leads me to believe perhaps the same will eventually happen to me. I've had my 6t go to crash dump mode several times. A few times when I wasn't using my device and went to use it it was on crash dump and some other random times on various custom roms.
Crazy thing is every time I have been able to boot back to system by holding power + my volume +&- untill I see fastboot screen then release and every time I could hit start from bootloader and phone would reboot back to system like nothing ever happened. However this seems to be happening more and more as time goes on. Seeing how it's happened with some of you guys and you weren't bootloader unlocked or rooted just like if happened with @ms2020 then I would lean towards thinking this is a hardware issue and man if it is ... I remember when my Nexus 6p bit it. By the time they gave people some sort of refund on that it was probably more than a year later. I hope for all of us that that's not the case but it sure seems that way to me. ?
Are you thinking it was something in an OOS update? Possibly?
flash713 said:
This leads me to believe perhaps the same will eventually happen to me. I've had my 6t go to crash dump mode several times. A few times when I wasn't using my device and went to use it it was on crash dump and some other random times on various custom roms.
Crazy thing is every time I have been able to boot back to system by holding power + my volume +&- untill I see fastboot screen then release and every time I could hit start from bootloader and phone would reboot back to system like nothing ever happened. However this seems to be happening more and more as time goes on. Seeing how it's happened with some of you guys and you weren't bootloader unlocked or rooted just like if happened with @ms2020 then I would lean towards thinking this is a hardware issue and man if it is ... I remember when my Nexus 6p bit it. By the time they gave people some sort of refund on that it was probably more than a year later. I hope for all of us that that's not the case but it sure seems that way to me.
Are you thinking it was something in an OOS update? Possibly?
Click to expand...
Click to collapse
Whaaat, my OP 6 also went to crashdump mode like 2 or 3 times but got rebooted automatically soon after, never happened since.This was also around the time of August. man the part where you told abt your nexus 6p, it hit me. I also had the 6p and it suffered the same fate, sadly there was no support for the phone where i live and it's just lying dead in my drawer ever since. Just hope this doesn't happen again...
flash713 said:
This leads me to believe perhaps the same will eventually happen to me. I've had my 6t go to crash dump mode several times. A few times when I wasn't using my device and went to use it it was on crash dump and some other random times on various custom roms.
Crazy thing is every time I have been able to boot back to system by holding power + my volume +&- untill I see fastboot screen then release and every time I could hit start from bootloader and phone would reboot back to system like nothing ever happened. However this seems to be happening more and more as time goes on. Seeing how it's happened with some of you guys and you weren't bootloader unlocked or rooted just like if happened with @ms2020 then I would lean towards thinking this is a hardware issue and man if it is ... I remember when my Nexus 6p bit it. By the time they gave people some sort of refund on that it was probably more than a year later. I hope for all of us that that's not the case but it sure seems that way to me.
Are you thinking it was something in an OOS update? Possibly?
Click to expand...
Click to collapse
It's obviously a software issue after the latest update. My phone was never once dropped or exposed to moisture or charged with anything except the in box charger in the one year. There is no possiblity that mine was a hardware issue as OP suggests.
Sidenote: was any of your phones at less than 10% of storage remaining? My phone was below 10% odlf storage.
Also confirm your storage? 6/64 or 6/128? Mine was 6/64.
I have a similar problem, my OnePlus 6 is sometimes just freezing in the system, then shuts down and goes to CrashDump mode. I have this problem since half a year. Sometimes it just reboots normally.
What I also notices: When my phone shuts down because of low battery and I plug it in, it should enter the charging mode, where it shows the battery percentage and some animation, but mine goes into CrashDump Mode.
flo071 said:
I have a similar problem, my OnePlus 6 is sometimes just freezing in the system, then shuts down and goes to CrashDump mode. I have this problem since half a year. Sometimes it just reboots normally.
What I also notices: When my phone shuts down because of low battery and I plug it in, it should enter the charging mode, where it shows the battery percentage and some animation, but mine goes into CrashDump Mode.
Click to expand...
Click to collapse
I had my 6t do same thing! Low battery, plugged it in and went to crash dump. When I get low battery again I'm going to see if I can make it do it again. I hope OnePlus can hook us up with a fix before more of our devices end up needing work done on them and are not able to be used because of it. So far I've been lucky enough to always get out of crash dump my holding volume +&- button and power down until I see fastboot screen and releasing then at bootloader screen just hit power and I reboot back in to system.
Op has gotta be right about this being software issue. I'm going to roll back on msm tool to a previous OOS. When I update from 9xx I'll stop a few OOS's before 10.3.5 and see if any of this occurs while on an earlier version of OOS. Worth a shot. I'll report back in this same post in a few days as to what OOS I'm on and if I have this low battery plug in crash dump or crash dump any other way.
flash713 said:
I had my 6t do same thing! Low battery, plugged it in and went to crash dump. When I get low battery again I'm going to see if I can make it do it again. I hope OnePlus can hook us up with a fix before more of our devices end up needing work done on them and are not able to be used because of it. So far I've been lucky enough to always get out of crash dump my holding volume +&- button and power down until I see fastboot screen and releasing then at bootloader screen just hit power and I reboot back in to system.
Op has gotta be right about this being software issue. I'm going to roll back on msm tool to a previous OOS. When I update from 9xx I'll stop a few OOS's before 10.3.5 and see if any of this occurs while on an earlier version of OOS. Worth a shot. I'll report back in this same post in a few days as to what OOS I'm on and if I have this low battery plug in crash dump or crash dump any other way.
Click to expand...
Click to collapse
Any update??
yawarkhalid said:
Any update??
Click to expand...
Click to collapse
Just had another crash dump and "Attecomp" below where it said crash dump. My device is a T-Mobile model that's been converted to Global. Since I started flashing roms back in the Nexus S days I've always kept dev options on and usb debugging checked... Currently flashing OOS in twrp. Will report back if I boot up to system or whatever happens. I do know I had 65-70% battery when this happened. I was on Pixen Android 11 with no extra mods or anything installed at the time.
Six or seven times previous I've always been able to manually do the button press , enter fastboot mode, hit power and I would boot system. This time when I did that and it looped around back to crash dump mode again. So I manually booted twrp and waiting for it to finish flashing now... Fingers crossed. ?
I'm good. I did a clean twrp install of latest OOS 10.3.6, Corvus and finalize, formatted data and im back booted up now and setting up phone.
flash713 said:
Just had another crash dump and "Attecomp" below where it said crash dump. My device is a T-Mobile model that's been converted to Global. Since I started flashing roms back in the Nexus S days I've always kept dev options on and usb debugging checked... Currently flashing OOS in twrp. Will report back if I boot up to system or whatever happens. I do know I had 65-70% battery when this happened. I was on Pixen Android 11 with no extra mods or anything installed at the time.
Six or seven times previous I've always been able to manually do the button press , enter fastboot mode, hit power and I would boot system. This time when I did that and it looped around back to crash dump mode again. So I manually booted twrp and waiting for it to finish flashing now... Fingers crossed.
I'm good. I did a clean twrp install of latest OOS 10.3.6, Corvus and finalize, formatted data and im back booted up now and setting up phone.
Click to expand...
Click to collapse
So this is the update. A person in my town had the same issue. Went to a local repair shop. They informed that its an issue of the IC. I think its jargon for the mobo in the local market. So they repaired his "IC" and apparently his phone is running fine now. Costed about 40USD. Will take it to them in a few days and report back. Still cant understand how its a hardware issue though.
yawarkhalid said:
Any update??
Click to expand...
Click to collapse
Just read that crash dump happens due to a kernel issue on OnePlus 6/6t. Read that on a telegram group.
Also see this for details: https://github.com/Ashutosh-s-Test-...mmit/a7611e75d6b4262b22475e0e12a9ecf84cf5e443
This must mean that this is one way that crash dump occurs. Because not all crash dumps are the same. If so then how come I've been there 7-8 times and always gotten back to a working device by going to fastboot mode manually and rebooting system.
And some people are stuck in crash dump and cannot do anything about it.
Every time I've been to crash dump mode I could always do the manual button press to enter fastboot mode and then hot exit that and reboot system by selecting "start " using power button when it's at the bootloader mode. Except yesterday...
Yesterday I had just installed OOS and Pixen 11 and booted system and setup my phone. All was good and my battery was at 55%. Then I booted twrp to flash magisk debug for root and instead of rebooting system like I selected from twrp it went to crash dump and when I tried the usual solution instead of rebooting to system it looped around right back to crash dump again. I booted twrp and installed OOS + Corvus and formatted data and booted fine. ?
yawarkhalid said:
So I've been using my OnePlus for about 2 years. The phone was kept in a rugged armor case, never dropped nor was it ever exposed to any sort of moisture. The device was never rooted nor was the bootloader ever unlocked.
At the end of August 2020 last month I was using maps when it suddenly crashed and went into Qualcomm Crashdump mode. I thought not a big deal, xda would have a fix to this.
I came home and for two weeks I tried different builds of the msmdownload tool with different methods to revive the phone. None of them worked. The 9.0 build did end up booting the phone but only for a short while before it got stuck, shut off and went into crash dump mode again. I can only boot into fastboot mode and that only sometimes (ofc EDL mode as well).
Fed up, I contacted OnePlus and scheduled a remote session with them. As was no surprise they used the msmdownload tool as well (build 10.3.0). And it obviously did not work and adviced me to visit the nearest support center. Unfortunately there is no service center nearby in my country so I dug deeper trying to find people with similar issue. Now this is the funny part.
On the brands own community app I found 5-6 other people who faced the exact same issue. They tried everything and when nothing worked they eventually went to the service center and were told that apparently the motherboard needs to be changed and it will cost as much as the phones value in today's date. Here's the interesting fact. All these 6 users were on the latest OOS 10.3.5 and faced this issue in the span of those 4 weeks. August to September of 2020.
The purpose of this thread:
1) To diagnose the issue with the help of the xda community as I believe that there is no way that the mobo could get fried this way.
2) To possibly find a solution as the phone is in absolute scratch less condition.
3) and most important, to find other people than those 6 who have faced this exact issue in the past couple of months so that it could be raised with OnePlus. Im hoping that OnePlus could at least diagnose it and release a tool for the fix if there are enough of us. Wishful thinking maybe but worth a shot.
Hoping for your support. Peace. ✌
Click to expand...
Click to collapse
Same happend with my oneplus 6 it went into crashdump mode all of a sudden i dont know what to do please help.
Deeksha Naurange said:
Same happend with my oneplus 6 it went into crashdump mode all of a sudden i dont know what to do please help.
Click to expand...
Click to collapse
Try msmdownload tool. Look for the link on xda. Thats your only option. If that works, it works. Else you cant do anything. My scrathless OP6 is as good as a brick right now.
Deeksha Naurange said:
Same happend with my oneplus 6 it went into crashdump mode all of a sudden i dont know what to do please help.
Click to expand...
Click to collapse
Have you tried holding down power+ volume +&- until you see fastboot mode?? Then select power while you are in "start" screen? Does it reboot back to crash dump when you do this or does your phone boot back up? I have seen crash dump 15 times on my 6t and only one time this didnt work. One time i wqs sent back to crash dump and because i always enable dev options and usb debugging immediately after i boot anything i flashed a rom and was able to boot up and had my phone back.
If you dont have an unlocked bootloader and enable dev options and usb debugging immediately then you should because this has been an issue for many months now w/the 6 and 6t.
If you have a lock screen enabled see funk wizards how to root thread and using twrp file mananger delete lockscreen.db and if other directories are present that he talks about on his thread delete them too then flash a rom.
Search high and low and read up. If for oneplus 6 and or 6t search both sections as theyre so much alike... Everything you need to know is already here. See my signiture for link to "how to navigate xda 2021."
If this does not work use msm tool. If msm tool doesnt work thats the end of the road.
(Edited 9:38pm central time)
I faced this same issue after 2 years of usage of the Oneplus6, QUALCOM CRASH DUMP and the device status locked,,device bricked and helpless after trying all possibilities,
Flaw seems to be at Oneplus factory hardware IC
My camera is practically unusable, it locks very much on the front. I only get it sometimes when I restart my phone, but imagine you in a situation of taking a quick photo having to ask people to wait for your phone to restart before you can take a photo. Besides it shut down when I'm using it, and I can only call after a few minutes.
Hi. My close friend has this issue. I'm posting this because she can't figure it out by herself. A month ago, her phone downloaded an update and she installed it. Since then, the phone has restarted by itself without any reason, just random restarts and the frequency of restarts was more frequent with each day. Fast forward to this day and the phone is constantly turning up and shows the POCO logo and restarts by itself. This loop is not ending until the battery is completely dead. When trying to access fastboot or recovery mode, she can get there but only for few seconds (until the device restarts again) which is not enough time to make any changes / factory reset. She did not accessed developer tools in system, so the bootloader is still locked. Holding down power button does nothing. ONE SINGLE UPDATE screwed up whole phone. Can't do ****. There's no SD card or SIM card in the slot. Is there any "hack" to stop the phone from restarting itself? Note when the battery is completely empty and she plugs the charger, the whole nightmare starts again. I'm lost. Did you guys have any ideas what to do? Or is the repair centre only solution? (She cracked glass of the display, i'm not sure if that voids warranty. [it's not glass COVER, it's the glass which is part of the display])
Is this device unlocked? If not, then RMA.
If it is, my best guess is to get the device into recovery (or fastboot?) and immediately connect to PC.
If it holds, leave it there as it will charge, although at much slower rate.
When charged, use TWRP to try to reboot to system.
If it doesn't work, then factory reset.
Sadly, i can not get to recovery because in about 2 seconds the device will reboot. There's literally no time to make any changes - factory reset. Also the device is not unlocked. I hope RMA accept the phone even though it has cracked screen . Thanks for response anyway
Then RMA it is. If you're in EU they'll have to take it, even with the cracked screen.
But does the reboot happen even when connected to PC? Two seconds is enough to plug it in if you're fast...
Yeah, we tried every possible idea we can think of. Pressing the toggle button from different angles with different intensity to make sure it isn't stuck inside, covering up the proximity sensor (yeah makes no sense but even that we tried, lol). Tried with connected to PC as with classical charging brick. No change. Back in those days where smartphones doesn't have unibody construction and you were able to take down the back cover and remove battery it was way simple. Nowadays it's not possible to stop the phone from booting itself until battery is completely empty. My friend says the problem started about month ago, when the phone annouced that there is an update available so she downloaded it and installed it. Before that, there was no problem with the phone whatsoever. Maybe it's caused by some kind of virus but IDK which apps she was using. She didn't have rooted phone not unlocked bootloader in developer tools. Also i googled that it may be caused by "Airtel Thanks" app which she didn't have installed aswell. I will keep this thread updated as what happend to the phone cause i'm also interested what went wrong and to help future users who will struggle with this problem a solution. Thank you.
CaptainFedora, did you solve the problem? I have the same issue...
Yeah, actually. Sorry for not posting the answer although it was definitely her fault. It was the power button being pressed down (which made continuous bootloop). But the button was somehow pressed deep into the phone's body. So complete dissasembly was needed.
Btw. my friend lives in other country so we discussed this problem over internet. If i could have the phone physically with me i would definitely know what was the problem.
Hi.
Yesterday I had the same problem, the device kept restarting every 10 seconds, it didn't even come to any screen besides the first one with the POCO logo in yellow.
Things I tried that did NOT work:
restart
hard restart
fastboot (it did enter the fastboot mode, but only showing the picture of the 2 robots and after 10 seconds restarting again to the POCO logo image)
plug it to power
plug it to computer
After 3 hours of continuous restarting and trying anything I could find in the internet and I could imagine of (except extracting the battery because it seemed complicated and difficult to revert), I tried randomly something that miraculously worked...don't ask me why.
pressing the power button shortly and quickly around 30 times (it might have worked after 10 or 20, but I just kept doing it a little longer
Afterwards it just started as if nothing had happened...doesn't make any sense, but I just wanted to tell you in case you are in a similar situation and desperate to not lose all the images and videos as I was yesterday.
So, i've been flashing custom ROMS on my android phones for many many years. Never really screwed up... Except now. Let me explain;
I was going to flash LineageOS on my OnePlus 8 phone. Nothing I haven't done before. I follow the guide as the maintainer described (for your reference, https://wiki.lineageos.org/devices/instantnoodlep/install).
Towards the end of the process when I got to Installing LineageOS from recovery I'm asked to format data. Here something went horribly wrong. As the process of formatting finished. All that's left to do is reboot. And so I reboot. This was the last time I ever got any sign of life from my phone. Because after shutting down, it never started back up. No sign of life at all. No fastboot, no adb, not even a splash screen. I've tried to boot it with any combination of keys. But no matter which one (reset, boot to recovery, even boot to EDL). nothing. Not even a buzz or a battery indicator when I plug it into the charger either. Bricked beyond anything I've ever seen.
In the 3 days since it happened I've:
- Charged my phone for 20+ hours
- attempted rescue using fastboot/ adb
- followed the steps from about every comment in this thread: https://forum.xda-developers.com/t/cannot-unbrick-cannot-enter-edl-mode.4148589/ (on USB3 and USB2, with the oneplus official cable and 3rd party cables)
- followed the steps this friendly youtuber explained:
- pressed any button and any combination of buttons on my phone for at least multiple minutes
- screamed at the phone really loud
Obviously none of these steps did the trick. My computer (I tried 3 computers actually, and both in Windows and Linux) just does not recognize the phone anymore. Nothing in device manager. Not even when i'm attempting to EDL.
Quite honestly I'm just stumped. It's not even recognized by device manager. If I didn't know any better I'd suspect the hardware itself failed at the exact same time as the software. I hope any of you can help me out.
One option you can try is getting an EDL cable.
Xryphon said:
One option you can try is getting an EDL cable.
Click to expand...
Click to collapse
Hi Xryphon,
That's interesting actually. I didn't know there were specialized cables for this. I was just using regular USB C. I'll look into getting one.