Database Info

Is this a hard-brick?

I've had my Oneplus One since the beginning of 2015, up until now it's been honestly fantastic, with very few issues whatsoever, certainly nothing that has bothered me at any rate. That's up until last night;
My phone was lying on my desk next to me with the screen on updating some applications whilst I was writing on my computer - suddenly, it starts to vibrate, one continuous long note, I naturally picked it up and looked at it, at which point the phone turn itself off in my hand. That was unfortunately the last I ever saw of my phone alive. This happened at about 6PM yesterday evening, since then I've tried everything within my power to get it to work. I can't access the bootloader, in order to get to fastboot (which would allow me to fix all my issues by enabling me to refresh the device), nor can I access my recovery. The phone turns on and displays nothing, it vibrates, but that's it.
The phone was running the latest COS13.1.1 update (X1) which I had flashed the day before, it was running the stock kernel for the ROM, the ROM was however rooted.
I know a fair amount about android, I also know a fair amount about the OPO, to me, I think something about the LOGO partition has gone wrong. The LOHO partition being responsible for the images shown in the bootloader, fastboot, splash screen etc.... I'm just not sure how that would have happened.
Either way, I don't know what to do, the one doesn't register to my computer in fastboot or adb , so both those routes seem closed. I primarily use a Mac for my work, I'm yet to try plugging the phone into a PC.
I've submitted a ticket to OP, and have spoken to an adviser who moved my case to a 'specialist', but I'm yet to hear back on that one.
Any help would be massively useful, because I need this phone for my work, and just general communication.
Thanks for reading,
Ben

Here, try this http://http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732

Possibly Bricked

Hi
I've been browsing the forum to find some help, but nothing matches exactly my situation and it is stumping me.
Have one plus 7 pro GM1913, attempted to install the latest update today that was pushed to my phone a few days back and set the phone down with charger cable attached and then look back at it and the screen is back at the security code entry tap my code and then back to booting, then black screen.
Attempted all manner of the key combos to get into the different reboot, fastboot modes, occasionally would get back to the loading screen which would then freeze with occasionally distorted graphics (one plus logo).
And now after a bit of charging (phone doesnt indicate it is charging at all) can't even get it back to the crashdump screen I could get to.
Crashdump screen didnt indicate any errors.
So i've been looking into possibly trying to trying to unbrick it with msmdownload tool. I have managed to install the qualcomm drivers, i believe i have the right version of the msmdownload tool.
However when i try attach my phone to the pc it keeps disconnecting all the time, my running theory is the phone is on and running through the boot sequence but I can't see it, but each time it disconnects then reconnects etc. Anyway I can't maintain a connection long enough to attempt msmdownload tool.
I also can't seem to boot my phone into EDL mode, following the below instructions:
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them.
You should see the anticipated EDL mode.
I am a complete beginner at this, but considered myself relatively tech savy enough to give things a go, but there is the old adage about knowing enough to be dangerous! Any help is appreciated.

Riverseo said:
Hi
I've been browsing the forum to find some help, but nothing matches exactly my situation and it is stumping me.
Have one plus 7 pro GM1913, attempted to install the latest update today that was pushed to my phone a few days back and set the phone down with charger cable attached and then look back at it and the screen is back at the security code entry tap my code and then back to booting, then black screen.
Attempted all manner of the key combos to get into the different reboot, fastboot modes, occasionally would get back to the loading screen which would then freeze with occasionally distorted graphics (one plus logo).
And now after a bit of charging (phone doesnt indicate it is charging at all) can't even get it back to the crashdump screen I could get to.
Crashdump screen didnt indicate any errors.
So i've been looking into possibly trying to trying to unbrick it with msmdownload tool. I have managed to install the qualcomm drivers, i believe i have the right version of the msmdownload tool.
However when i try attach my phone to the pc it keeps disconnecting all the time, my running theory is the phone is on and running through the boot sequence but I can't see it, but each time it disconnects then reconnects etc. Anyway I can't maintain a connection long enough to attempt msmdownload tool.
I also can't seem to boot my phone into EDL mode, following the below instructions:
Power off the phone.
Plug in the USB cable your computer but do not connect the other end to the phone.
Hold down Volume Up and Volume Down buttons for a few seconds, and plug in the cable while you are continuing to hold them.
You should see the anticipated EDL mode.
I am a complete beginner at this, but considered myself relatively tech savy enough to give things a go, but there is the old adage about knowing enough to be dangerous! Any help is appreciated.
Click to expand...
Click to collapse
I actually start the MSM tool ,wait until it boots up, position my cursor close to the start button on the tool, then I connect my phone to cable make sure it's attached to both PC and phone , put phone in edl ( hold power button and both vol up and vol down at same time) phone should go blank and you should see a connect on the MSM tool, hit start,,,, hth

My phone appears completely blank anyway, i've left it off charge overnight and then attempted to charge this morning, no real change. I've got no indication if the phone is charging or not or if it is even on.
When I connect via usb to my pc it is connecting and disconnecting constantly. I can't see anything via the screen.
What should edl mode on the phone look like?
Prior to this update there were never any issues with the phone, so im pretty sure it is connected to the update, just dont know how it has even wrecked the bootmodes etc

Riverseo said:
My phone appears completely blank anyway, i've left it off charge overnight and then attempted to charge this morning, no real change. I've got no indication if the phone is charging or not or if it is even on.
When I connect via usb to my pc it is connecting and disconnecting constantly. I can't see anything via the screen.
What should edl mode on the phone look like?
Prior to this update there were never any issues with the phone, so im pretty sure it is connected to the update, just dont know how it has even wrecked the bootmodes etc
Click to expand...
Click to collapse
When I go into edl it's a completely blank ,,,screen is black

Thanks for letting me know that!
I keep getting firehose communication handshake failed (i keep getting the disconnection sound from windows, like ive unplugged the usb, but it shows up in device manager) and then i do enum and it shows as connected in msm.
however if I hit start again I get sahara communication failed.

Riverseo said:
Thanks for letting me know that!
I keep getting firehose communication handshake failed (i keep getting the disconnection sound from windows, like ive unplugged the usb, but it shows up in device manager) and then i do enum and it shows as connected in msm.
however if I hit start again I get sahara communication failed.
Click to expand...
Click to collapse
I would just make sure you have all the correct drivers, especially l2, other than that iam out of ideas maybe someone with more experience will reply,, good luck

No worries cheers for the help though!

Question KDump - Boot Loop

Over the past 1 year I have purchased a total of 7 Samsung Galaxy A32 5G. One for myself (Development) and one each for my children and wife. They were (are) decent devices for the price. I’m a licensed Android Developer (among a-lot of certs and licenses) and I have tried everything. I explain this so we can skip the basic concepts.
One night one of my device wouldn’t charge properly (no water damage) I turned it off to see if it charges correctly while off.
Instead the device enters a boot loop. I noticed an error on the bottom. Seems like it said “Kernel Dump” or “KDump” but the message was too fast to read. I even attempted taking video and pausing it on that frame but it was so quick it’s blurry. I was able to read it a bit better though and It does look like it says Kernel Dump (kdump) though. I can boot into Download Mode , I cannot boot into recovery or Fastboot however. I have tried many options (Kies , Odin) and while Odin is absolutely 100% completing successfully with no issues the device continues to go into a boot loop and show this Kernal dump. . I know Linux in general has a Kdump which creates a log when the Kernal crashes. Naturally I can’t think of a way to see that log. Is there something I’m missing? Is there a solution that works?
Thank anyone for any suggestions.

Innovatorsww said:
Over the past 1 year I have purchased a total of 7 Samsung Galaxy A32 5G. One for myself (Development) and one each for my children and wife. They were (are) decent devices for the price. I’m a licensed Android Developer (among a-lot of certs and licenses) and I have tried everything. I explain this so we can skip the basic concepts.
One night one of my device wouldn’t charge properly (no water damage) I turned it off to see if it charges correctly while off.
Instead the device enters a boot loop. I noticed an error on the bottom. Seems like it said “Kernel Dump” or “KDump” but the message was too fast to read. I even attempted taking video and pausing it on that frame but it was so quick it’s blurry. I was able to read it a bit better though and It does look like it says Kernel Dump (kdump) though. I can boot into Download Mode , I cannot boot into recovery or Fastboot however. I have tried many options (Kies , Odin) and while Odin is absolutely 100% completing successfully with no issues the device continues to go into a boot loop and show this Kernal dump. . I know Linux in general has a Kdump which creates a log when the Kernal crashes. Naturally I can’t think of a way to see that log. Is there something I’m missing? Is there a solution that works?
Thank anyone for any suggestions.
Click to expand...
Click to collapse
Have you tried booting in to safe-mofe or adb booting an image, a/b slots, etc. Make sure clear data (sucks)
Not much help, I'm sure you've covered all this, and well, the basics. Good luck

I had the same issue with my A32 5G and i found a solution to this. Plug the phone in and make sure it is charging and then power it on and set it aside and let it go into the boot loop. (plugging it in is to ensure it wont die) Eventually, after a few hours, the boot loop will stop and the phone will open android recovery and allow you to facotry reset the phone. After the reset it should boot again. Not sure what the exact cause of this is but this is what worked for me. Good luck!

Neither bypass nor Filter Wizard recognizing the phone.

I think I killed my phone. I lil' story -- i decided to flash my Redmi 9A, flashed PBRP onto it and.. Black screen. I already faced it, so I just try to flash original firmware with SP Flash and... Error. Can't quite remember what it was. I try to use bypass, and although bypass does give the "Success" output, SP Flash still gives the same error. I google this error and it seems like it is an issue with drivers. OK, I remove all the drivers and try again. It got zero battery at this point. Now it's not recognized by PC at all, Windows gives no error, FIlter Wizard doesn't even recognize it, Bypass gives a driver error. I'm sure I installed all the drivers correctly. I also tried:
To use my installation of Arch Linux using this guide, no success, bypass doesn't recognize the phone
This LIveCD, where all the drivers should be properly installed, but no success, same as every other try
I'm very stuck. Any suggestions?

ignaycyhry said:
I think I killed my phone. I lil' story -- i decided to flash my Redmi 9A, flashed PBRP onto it and.. Black screen. I already faced it, so I just try to flash original firmware with SP Flash and... Error. Can't quite remember what it was. I try to use bypass, and although bypass does give the "Success" output, SP Flash still gives the same error. I google this error and it seems like it is an issue with drivers. OK, I remove all the drivers and try again. It got zero battery at this point. Now it's not recognized by PC at all, Windows gives no error, FIlter Wizard doesn't even recognize it, Bypass gives a driver error. I'm sure I installed all the drivers correctly. I also tried:
To use my installation of Arch Linux using this guide, no success, bypass doesn't recognize the phone
This LIveCD, where all the drivers should be properly installed, but no success, same as every other try
I'm very stuck. Any suggestions?
Click to expand...
Click to collapse
If u install a recovery rom and you did it wrong you can boot to fastboot, no?

Hey I faced similar or even worse (twice), I had a similar story to yours,
FIrst itme:
I first bricked my phone, but it was cool, the phone just flashed MIUI for a fraction of a second when trying to go to recovery, other than that, nothing, I tried flashing, wich made it much much worse, black screen, no key combo did nothing, windows not just did not recognize it,it told me there was no way of recognizing it, (error 43 in devices admin, its not posible to reinstall the driver, nor do crap at this point) filter wizard showed nothing, bypassing imposible, etc.
It got pretty similar to what you had:
I just left the phone do some charging discharging cycles (at least 4 days with me checking if the phone did anything at all almost once every day, just so you know the phone was really bricked) and it eventually responded after all that (Im not quite sure what fixed this, I dont kno if it was complete discharge or what, but something happened and it vibrated when holding the pwr button.
Once that worked, I managed to install the filter by pressing volup voldown and conecting the phone to the USB port (dont use 3.0, it works worse for some reason) at the same time, you need to connect and press the buttons and connect at the same time (
at 1:30 he does it, video on spanish) and then you can install the filter.
Then you can Bypass and attempt to flash with SPflash tool, I recomend autoconcect, UART never made it for me, Im thinking thats for when you can put it in EDL mode by presing the test points, but I dont know enough to say for sure, point is, UART never worked for me, even tho I eve know what comms I was using.
second time:
I was running Custom ROM ArrowOS 12, ArrowOS13 came out some weeks ago, so I decided to lash it, it was better in some areas and worse in others, the contacts app did not work, but now Volte fingerprint(irrelevant to us redmi 9a users) and face unlock did so I decide to test some stuff, I wasnted to flsh boot.img from original MIUI ROM on top of ArrowOS13, to check if that fixed some stuff (that worked wonders on ArrowOS12) that bootloped thephone but it was fixable from recovery, I did that and decided to flash MIUI ROM to check if flashing ArrowOS13 from MIUI ROM worked, and flashing MIUI bricked my phone.
unrecgnized with error 43, not posible to fix from software, black screen no response whatsoever from any key combo (all 7 combos) no charging, no filter, no nothing, I know I had around 50% battery (days ago I remembered the exact number, now I forgot it, but just so you know, its not a hunch, I knew it had battery) I tried doing the same stuppid crap, charging and leaving it alone for couple hours, but after one night nothing worked, so I assumed I would have to repeat the procees I did before (I wrote it complete on an unbricking thread so I knew I could go back there and redo that or variate it until it worked), but I decided to do one final thing.
I knew it had battery, so I decided to try and forcedrain the battery, I took a piece of TP and gave it a turn around the phone over the buttons (this is just to not dirty the phone) then with electrical tape, I left the power button and the vol down button pressed) this for around 7 hours my plan was leaving it like that for a full day, but around 6 hours I thought I heard a vibration from the phone, so I kept it with me, then after a while I thought it happened again, but I also had my own phone with me so I thought it was that and some other things distracted me so Im guessing I missed a few, but after that I started to take time from every vibration and yeah, around every 8 - 10 minutes the phone vibrated
I decided to connect the phone (I hadnt before because it would just slowdown the battery draining process) and the phone conected to the pc, still bricked, but it was a lot better, I quickly installed the filter, wich I dont quite remeber, but it wasnt easy, I had some hickups, cmd bluescreened my PC when using Bypass like 6 times, so I switched to powershell and that worked (to do that you need to press shift+right click and open powershell here, then run "python main.py") that worked, but I did not flash using SP flash tool.
I was trying to avoid turning on the phone for fear it would go back to the previus state, but after a while pluged on the PC it showed the no battery logo so I tried to tun it on and it was bootlooped, I was able to go to recovery and fastboot (not normally, I pressed the keys, the phone try to go into those menus, it showed no battery, and in the next cycle after splash logo no matter what you did it sent you to the previus key combo menu) I tried leaving it charging on fastboot, but that did not work, I tried flahing a rom from recovery (wich said I had 47% battery) and it successfully did but when trying to reboot to system it again showed no battery logo. so I put it on fastboot and tried flashing MIUI with Miflsh, did not work but it told me the ROM was bad (same one I had use before) I made sure to extract it again and again nothing, I assume it was the antirollback, so I downloaded the next one on line 12.5.6.0 (I was on 12.5.4.0) and that finally worked (Miflash actually gave me lots of errors but you can google them and most of them have easy fixes, like creating a log folder, etc)
that was yesterday, after it worked it showed me the phone had around 60% batterywich lasted around 30 minutes to 40%, then it took 10 minutes to spend the next 20% (it told me that) and then it drained 1% every second (Im not exagerating I thought I had fried my battery with all that power button pressing) but I had hopes of it just being a configuration issue of the phone not knowing how much battery it had so I just left it power of and pluged it then so the phone knew what was his zero, now the phone as been on 100% for like 2 hours (sharing internet), so yeah, I think the battery has some issues but its better than nothing so Im happy with that.
that is my whole experience, I hope it helps you, see if you manage to get any response from the phone and if you do you can try contact me for help in any point along the way.
Update, it just got to 99% after 2 hours 10 minutes aprox IDK, I would need to test more to be sure

Question Poco X3 suddenly bricked

Hi folks,
I really hope someone is able to help. I got a Poco X3 from a friend which is causing issues. According to her the phone started to lag and shut down yesterday. No pending updates. The phone had about 10% battery left.
After the phone died she plugged it into the charger and the battery symbole appeared. after that the phone went black again and never came back to life.
I tried doing the usual "let's try to fix it" but nothing seems to work here.
I've tried the following things:
pressing the power button for 10+ seconds
pressing power + vol down for 10+ seconds
pressing power + vol up for 10+ seconds
pressing power + vol up + vol down for 10+ seconds
plugging it into the pc and checking if the device can be accessed using the explorer
plugging it into the pc and checking for adb weather or not the device can be accessed
the phone hasn't developer settings enabled as far as I'm able to guess.
the strange thing that I noticed:
when plugging it into the pc the windows sound for a connected device plays. within the device manager a new entry appears:
Code:
QUSB_BULK_CID:0404_SN:812DDxxx
Any ideas how to fix this issue?

is it deadboot like no sign of life?, are you using your phone in gaming or occasionally gets overheat while playing? because if so, must be a cpu solder melt and got shorted which is the alot of cases of poco x3 pro being deadboot, mine as well experienced this and need to brought it to technician for a "cpu reball" check in youtube many people did reballing and solved their problem.

absolutely no sign of life except the listing within the windows device manager.
as for overheating: it's not my phone and is primeraly used for social media, surfing and ocasionally providing the hotspot for a notebook. I woudln't bet that it was an issue previously.
Interesting nevertheless.
So, in short, if I understood this correctly after watching some videos, without reballing the change of getting the data from the phone is.. non existent?
I mean, it looks doable if you are a fine motorist

lechnerio said:
absolutely no sign of life except the listing within the windows device manager.
as for overheating: it's not my phone and is primeraly used for social media, surfing and ocasionally providing the hotspot for a notebook. I woudln't bet that it was an issue previously.
Interesting nevertheless.
So, in short, if I understood this correctly after watching some videos, without reballing the change of getting the data from the phone is.. non existent?
I mean, it looks doable if you are a fine motorist
Click to expand...
Click to collapse
Make sure to distinguish whether it is "POCO X3 Pro" or "POCO X3 (NFC)". These are 2 different phones.
This is not your phone, and if you had never done reballing the CPU, better not risk it. You could try to reball the CPU, with the risk of upsetting your friend when failing to do so.
Find shops that can do it and let them take the risk.
This phone has 2 year warranty in Europe. It is possible that the phone is still under warranty. Hardware issue could be repaired by Xiaomi/Redmi/Poco official repair center or customer service. However, there's chance that the data in the phone may be wiped.
If you find a non-official shop to try the repair, the warranty might be void.

lechnerio said:
Hi folks,
I really hope someone is able to help. I got a Poco X3 from a friend which is causing issues. According to her the phone started to lag and shut down yesterday. No pending updates. The phone had about 10% battery left.
After the phone died she plugged it into the charger and the battery symbole appeared. after that the phone went black again and never came back to life.
I tried doing the usual "let's try to fix it" but nothing seems to work here.
I've tried the following things:
pressing the power button for 10+ seconds
pressing power + vol down for 10+ seconds
pressing power + vol up for 10+ seconds
pressing power + vol up + vol down for 10+ seconds
plugging it into the pc and checking if the device can be accessed using the explorer
plugging it into the pc and checking for adb weather or not the device can be accessed
the phone hasn't developer settings enabled as far as I'm able to guess.
the strange thing that I noticed:
when plugging it into the pc the windows sound for a connected device plays. within the device manager a new entry appears:
Code:
QUSB_BULK_CID:0404_SN:812DDxxx
Any ideas how to fix this issue?
Click to expand...
Click to collapse
I have the same issue. Mine suddenly stopped working on Tuesday, May 30th. It had around 79% battery and I have been trying to find a solution since.

Your phone is on the "EDL" mode aka Emergency DownLoad mode. From what I've seen I don't think that's actually possible to flash anything again with it since Xiaomi encrypted some stuff.
Link that may be useful :
Xiaomi POCO X3 Pro - Прошивки MIUI - 4PDA
Xiaomi POCO X3 Pro - Прошивки MIUI
4pda.to
https://xiaomitools.com/download/poco-x3-pro-qcn-file/
[GUIDE] How to return to Stock/Flash Images with QFIL
Here is a step by step guide on how to flash the stock rom with QFIL and by extension any image. Download and install the Qualcomm drivers from here Download either of the firmware from here Download the support files...
forum.xda-developers.com
[GUIDE] Backup, edit and restore QCN. Fixing lost IMEI.
Introduction This is a guide to backup and restore the QCN, and to edit other's QCN in case you lost your IMEI and you don't have a backup of your QCN. There are other ways to do some steps (the most popular is via Fastboot) but I'm gonna...
forum.xda-developers.com
Good luck finding stuff inside these.

The same happened on my Poco x3 pro. is there anyway to flash stock using edl mode for FREE?

Haynzu said:
The same happened on my Poco x3 pro. is there anyway to flash stock using edl mode for FREE?
Click to expand...
Click to collapse
I too have a Poco X3 Pro and the EDL tool by bkerler (it's a FOSS project) automatically loads this particular loader which is in an EDLAuth folder so I think it's totallly worth a shot.
Mind you I'm rather out of touch on Xiaomi's EDL authentication implementation so I cannot guarantee you anything.

lechnerio said:
absolutely no sign of life except the listing within the windows device manager.
as for overheating: it's not my phone and is primeraly used for social media, surfing and ocasionally providing the hotspot for a notebook. I woudln't bet that it was an issue previously.
Interesting nevertheless.
So, in short, if I understood this correctly after watching some videos, without reballing the change of getting the data from the phone is.. non existent?
I mean, it looks doable if you are a fine motorist
Click to expand...
Click to collapse
If you manage to reboot it in EDL you can dump the userdata partition with a tool such as the one I linked above, although I don't really know how you could decrypt it if needed.
The only way to reboot it in EDL (VID: 05C6 , PID: 9008) probably is shorting the proper test points (pins) on its motherboard while the device is booting.
Here at XDA someone provided a photo to point them, however I cannot confirm whether they are the correct ones.

Micky99 said:
I too have a Poco X3 Pro and the EDL tool by bkerler (it's a FOSS project) automatically loads this particular loader which is in an EDLAuth folder so I think it's totallly worth a shot.
Mind you I'm rather out of touch on Xiaomi's EDL authentication implementation so I cannot guarantee you anything.
Click to expand...
Click to collapse
Hi there! Thanks for this infomation i'm willing to try this. Is there any video tutorial for this out there? I'm such a noob when it comes to these stuffs

Haynzu said:
Hi there! Thanks for this infomation i'm willing to try this. Is there any video tutorial for this out there? I'm such a noob when it comes to these stuffs
Click to expand...
Click to collapse
Just follow the readme in the repo to setup everything needed (possibly on baremetal linux I'd suggest) or boot the ISO provided by its dev and run ./edl printgpt --memory=ufs, if the device enters the firehose mode you can then use ./edl r <rest of the command, according to the readme> to dump any partition.
Unfortunately the loader linked to our device might not work , so you might have to wait an indefinite amount of time before we get a fully working one.
Don't forget you're gonna have to decrypt the dump of the userdata partition, and I don't know how to help you with that.

NotesOfReality said:
Just follow the readme in the repo to setup everything needed (possibly on baremetal linux I'd suggest) or boot the ISO provided by its dev and run ./edl printgpt --memory=ufs, if the device enters the firehose mode you can then use ./edl r <rest of the command, according to the readme> to dump any partition.
Unfortunately the loader linked to our device might not work , so you might have to wait an indefinite amount of time before we get a fully working one.
Don't forget you're gonna have to decrypt the dump of the userdata partition, and I don't know how to help you with that.
Click to expand...
Click to collapse
Thanks! I'll give this a try