Oppo Find 5 Dead Bricked - Oppo Find 5

Hi,
I have been playing with custom roms installations with my Oppo Find 5 and somehow I got it bricked.
It is so bricked that it is dead.
I charged it for 5-6 hours ... nothing
I connected it to my linux laptop and try to detect it via fastboot and pressing power + vol up ... nothing
I kept power button for 60 seconds ... nothing
I have tried to remove battery but do not know how to disconnect it ...
So, it looks like the phone is completely dead. It used to work fine ...
is there any way to bring it to life?

Did you fix the problem? Where are you from?

Yeah same here, i wiped the wrong partition on LVM. Now it doesn't boot anymore, nothing happens when i try to charge it, its just a brick.
Edit: My PC can detect my phone as "Qualcomm HS-USB QDLoader 9008" but all links that i found for unbricking are dead or not helpful.
Edit2: I think that's: http://www.androidjunkies.com/how-to-unbrick-your-oppo-find-5/ is the solution but under my windows 10, the phone keeps rebooting. I will test it under Windows 7 in the next days.
Edit3: I have my Find 5 accidentally dropped from the table during the reprogramming. At the same time the battery connection disconnected and the reprogramming started it. Probably it cant be reprogrammed with a battery so disconnect the battery when you get the same problem.

Related

Bricked Jiayu S3 Advanced help!

Yesterday i flashed my Jiayu S3 to lolipop (i tought) and i just bricked my phone!
After reboot it was just dead.. when i plug into pc with USB i hear the connect sound and after 2 seconds the disconnect sound. This keeps on going until i pull the USB plug. When i look in DeviceManager i see it refresh after every sound, but nothing pops up (unknown device or whatever). I deletet all usb drivers with usbdeview, restart pc but still no changes.
I tried with or without battery, but without it does nothing at all.. i tried holding Vol+ or - or both or with power button, but nothing.
Read some threads about unbrick and install correct usb driver for jiayu s3, but all the options they came with does not work on my device!
I'm a little despered now and don't know what to do.. i get the feeling that my 2 weeks old phone is dead? :'(
My pc has windows 7
Did the flash with SP Flashtool 5.1516
Did not untick preload in flashtool, i guess i got the wrong preload or something??
Please help!
No one..? :crying:
Lowrida said:
Yesterday i flashed my Jiayu S3 to lolipop (i tought) and i just bricked my phone!
After reboot it was just dead.. when i plug into pc with USB i hear the connect sound and after 2 seconds the disconnect sound. This keeps on going until i pull the USB plug. When i look in DeviceManager i see it refresh after every sound, but nothing pops up (unknown device or whatever). I deletet all usb drivers with usbdeview, restart pc but still no changes.
I tried with or without battery, but without it does nothing at all.. i tried holding Vol+ or - or both or with power button, but nothing.
Read some threads about unbrick and install correct usb driver for jiayu s3, but all the options they came with does not work on my device!
I'm a little despered now and don't know what to do.. i get the feeling that my 2 weeks old phone is dead? :'(
My pc has windows 7
Did the flash with SP Flashtool 5.1516
Did not untick preload in flashtool, i guess i got the wrong preload or something??
Please help!
Click to expand...
Click to collapse
so you cannot boot into recovery or fastboot either?
Lowrida said:
Yesterday i flashed my Jiayu S3 to lolipop (i tought) and i just bricked my phone!
After reboot it was just dead.. when i plug into pc with USB i hear the connect sound and after 2 seconds the disconnect sound. This keeps on going until i pull the USB plug. When i look in DeviceManager i see it refresh after every sound, but nothing pops up (unknown device or whatever). I deletet all usb drivers with usbdeview, restart pc but still no changes.
I tried with or without battery, but without it does nothing at all.. i tried holding Vol+ or - or both or with power button, but nothing.
Read some threads about unbrick and install correct usb driver for jiayu s3, but all the options they came with does not work on my device!
I'm a little despered now and don't know what to do.. i get the feeling that my 2 weeks old phone is dead? :'(
My pc has windows 7
Did the flash with SP Flashtool 5.1516
Did not untick preload in flashtool, i guess i got the wrong preload or something??
Please help!
Click to expand...
Click to collapse
Just flash it again, but this time with "Firmware upgrade " in SP Flashtool instead of "Download". Change from KK to LL needs reepartitioning, so firmware upgrade.
The reason why you don´t "see" the S3 any longer on the pc is, that the USB storage mode from KK, which is driverless for windows, don´t work right now on LL.
Once flashed to LL you will need to install a driver, for windows to connect to the S3.
@ Dior DNA:
No i can't. Phone does nothing with the buttons. Only diference if i hold Vol - then time from connect sound and disconnect sound is a little longer.. about 10 seconds. But still nothing happens.
@1testi:
Flashtools can't see my phone. I tried it a hundred times. With battery, without battery, with Vol - and with Vol +.
When i connect the USB cable i hear the connect sound and after 2 a 3 seconds i hear disconnect sound. This goes on and on until i pull the USB cable out. In devicemanager i see a refresh going on, but nothing pops up.
I'm realy despered on what to do now?
Lowrida said:
@1testi:
Flashtools can't see my phone. I tried it a hundred times. With battery, without battery, with Vol - and with Vol +.
When i connect the USB cable i hear the connect sound and after 2 a 3 seconds i hear disconnect sound. This goes on and on until i pull the USB cable out. In devicemanager i see a refresh going on, but nothing pops up.
I'm realy despered on what to do now?
Click to expand...
Click to collapse
Why the SP Flashtool isn´t working any longer? You didn´t deinstalled the driver, did you? Just try to flash again with "Firmware Upgrade".
I don´t know a way to reinstall the driver in windows without the preloader. The only thing you can do, as far as i know, is to use a linux
pc to flash again. Linux don´t need a driver for SPF, only some rules.
Lowrida said:
@ Dior DNA:
No i can't. Phone does nothing with the buttons. Only diference if i hold Vol - then time from connect sound and disconnect sound is a little longer.. about 10 seconds. But still nothing happens.
(
Click to expand...
Click to collapse
Booting into recovery or flashtool I meant regardless of pc and/or spflashtool.
If I recall correctly:
hold volup and power boots recovery
hold voldn and power boots flashtool
If you can boot recovery then which one is it? Maybe you can restore something or manually flash preloader bin from there.
After the flash i reboot and then the connect and disconnect sound appears. So i tried differend things, but could not connect. I wanted to flash again, but flashtool did not reconice the phone and nothing in DeviceManager. That's why i thought to remove the driver and try to re-install it. But that did not help..
Holding Vol - or + button with power button or both Vol buttons with power button does nothing.. i tried to hold all combinations at least 30 seconds, but nothing at all.
I have no Linux pc or any knowhow to make a Linux pc.. or a pc to install Linux on..
One last thing you can try: remove the battery, wait a little, insert the battery again. Hold vol+ key, keep holding it and press power
button, while still holding the vol+. If you don´t see anything happening then you bricked the phone.
You will need help from a professional or at least from someone with a linux machine, sorry.
I'll try that.
You have any idea what could have caused the brick?
As i wrote above, moving from KK to LL with wrong parameter "Download" in SPF.
....and a not working recovery.
You should try this method :
darmowyinternet.net/forum/temat-poradnik-jak-uruchomic-uceglony-telefon-po-wgraniu-zlego-romu-test-point_383
unfortunately you have to translate before
Ok i tried that site with google translate and i could a little make up what they are saying.
But that is a very drastically operation, and i would like to give it some other tries before dismantling my phone.
So i googled and googled.. came here: http://forum.xda-developers.com/showthread.php?t=889128
Had enough electronics lying around from my former 27mc hobby, so searched for the right resistors,
cut up a micro usb cable and give it a try... well.. nothing! Tried for about an hour and gave up.
Then i googled on Unbrick Jigs, but for what i read they are only for Samsung phones, so i gues the trick
with the resistors were also?
So googling again... came here: http://forum.xda-developers.com/showthread.php?t=2454004
Reading the tread and the comments, someone mentioned a download for "Mediatek Driver Auto Installer".
Downloaded that and installed the drivers. Plugged in my phone and... whoohoo!! Something is happening! :silly:
My devicemanager saw an "Alcatel single RNDIS interface". I unplugged and plugged my phone a few times to
be sure it was my phone. Sooo... one step further! :good:
Then i googled on this device.. came up with all sorts of network devices, not helpfull. Then googled on Jiayu with
this device. Came up with this tread: https://www.china-devices.com/topic...vcomm-drivers-onto-your-pc-win-7vistaxp-only/
It's a tread about bricked Jiayu G3 devices, but i thought, 'What the heck, lets give it a try!'.
I downloaded the "MTK Megapack - All Tools Here!" and unpacked. Wend back to device manager and manually updated the driver
of the Alcatel device. Show all devices - browse - wend to Megapack map and there were MTK drivers for the 65xx device.
And yess.. when i plug in my phone there's the device: " MTK USB Port (COM7) "
SP Flashtools sees my phone again! :good:
Tried to flash a stock preloader, but got an error: "BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) – [EMI] Enable DRAM failed!"
But for now that's a problem for tomorrow.. it's almost 2:30 and i have to got some sleep!
(sorry for the misspellings or telling things not clear, i'm tired and english is not my main language)
Grats!
You can google the error. This leds you in the right direction.
It's alive!!!!!! :laugh::silly::victory:
Because the kitkat stockrom i downloaded gave me the same error over and over i searched for something else.
So i downloaded TF Extreme lolipop 5.1 this morning and give it a try. And all went well. I pulled the usb plug and
pushed power button.. only vibration but nothing. Then pulled the battery and after few seconds put it back in
and try power again. Only 1 vibration.. then tried Vol + and - combinations but nothing. (dammn!)
Then plug the usb in and i saw the battery icon.. it was total empty! (because of a week trying).
So now it's charging and i hope it starts, can't wait!!
Thanx all for the effort in helping me out! :good:
Edit: Ok, so i could not wait and hit power! It shows green screen with Jiayu S3 logo and text "New Load". So i guess it's prepairing for first startup!
my s3 basic is not charging when on.. also when connected to pc thru usb, ipc shows device malfunctioning ,and there is no indication on phone..I try to connect to sp flash tool also no success..same error"usb device not recognized pops up every 2s.everything else is fine..Any method to upgrade to 5.1 now on official kk
Kinda need help, happened something similar
It happened something similar to me.
I flashed the whole ROM, bootloader included, I was very sure that my model, Jiayu S3 3GB ROM + 32GB RAM, was the correct, but still bricked my phone.
There's no problem at all when I plug it into my PC, I installed the lastest MTK drivers on windows 10, having to disable the signature enforcement.
The problem comes when I start flashing. I only mark the bootloader, then I press "Download" (on the lastest version of SP Flash Tools), and plug the phone, with the battery in it (I've tried without battery, pressing all possible combinations and does nothing), when I plug it in with the battery and pressing no buttons, the driver is detected as MTK USB Port. That's a good thing I guess. But It does not pass from the red bar, and gives me the known error "Enable DRAM Failed".
I've tried to google any possible solutions, reinstalling other version of the MTK drivers, on different versions of Windows, with other versions of official ROMs, and the result is always the same.
The only thing that's left to try is flashing it with an Ubuntu machine, which is something I do not expertise to be honest, but I'm gonna gather some info and try to do it.
However, if someone has any idea of what I might be doing wrong (excluding the part when I flashed the bootloader, I'll never do it again), I would be really grateful for any kind of help.
Thank you!
Kiei said:
It happened something similar to me.
I flashed the whole ROM, bootloader included, I was very sure that my model, Jiayu S3 3GB ROM + 32GB RAM, was the correct, but still bricked my phone.
There's no problem at all when I plug it into my PC, I installed the lastest MTK drivers on windows 10, having to disable the signature enforcement.
The problem comes when I start flashing. I only mark the bootloader, then I press "Download" (on the lastest version of SP Flash Tools), and plug the phone, with the battery in it (I've tried without battery, pressing all possible combinations and does nothing), when I plug it in with the battery and pressing no buttons, the driver is detected as MTK USB Port. That's a good thing I guess. But It does not pass from the red bar, and gives me the known error "Enable DRAM Failed".
I've tried to google any possible solutions, reinstalling other version of the MTK drivers, on different versions of Windows, with other versions of official ROMs, and the result is always the same.
The only thing that's left to try is flashing it with an Ubuntu machine, which is something I do not expertise to be honest, but I'm gonna gather some info and try to do it.
However, if someone has any idea of what I might be doing wrong (excluding the part when I flashed the bootloader, I'll never do it again), I would be really grateful for any kind of help.
Thank you!
Click to expand...
Click to collapse
Oeps it might be the same problem with the 32GB version as I have.
See http://forum.xda-developers.com/showpost.php?p=68036678&postcount=295
I am waiting for a stock ROM backup.
I have learned to never flash the original preloader again.
xtyphoon said:
Oeps it might be the same problem with the 32GB version as I have.
See http://forum.xda-developers.com/showpost.php?p=68036678&postcount=295
I am waiting for a stock ROM backup.
I have learned to never flash the original preloader again.
Click to expand...
Click to collapse
You're right, with the 32GB rom version (which is still unavaliable for public use) it worked! I still got it here, so anyone feel free to ask me the link too.
Thanks to xtyphoon and Dior DNA and everyone who made this possible, if you ever come to Girona city, I'll buy you a drink ;D
Kiei said:
[...]if you ever come to Girona city[...]
Click to expand...
Click to collapse
I was around there few weeks ago

Phone not recognized in Fastboot / Download

Three days ago, my phone went off by itself and I had a hard time starting again, it was just loading the bootanimation, I tried to reinstall the ROM, but it did not go into TWRP, although the message Recovery appears on the screen, I insisted and after several attempts, I got into the recovery, formatted everything and I installed the AICP ROM again, and I had to restart,my phone freezes in the LeEco bootloader, then again I insisted until the ROM finally started, but soon realized that it was taking too long to start (30 minutes waiting and nothing).
So I rebooted again, and from then on, I can not go into any mode anymore, trying to access the TWRP, the phone only stays on the Recovery screen until reboot after 2 minutes, when letting the phone try to start the ROM, it only stays on the LeEco screen and restart after 2 minutes, when entering Fastboot, it enters the screen in Fastboot mode, but is not recognized by the computer, not even as unknown device, the same for Download mode.
Is there anything I can try?
Doesn't seem like a a fried motherboard. In my experience, If you fried the CPU, you would still be able to access Fastboot, if you fried the GPU part of the chip, or if the LCD has failed you would feel vibrations..
Do you thin it is possible that you accidentally put the phone into EDL mode? It can sometimes be hard to get out of, and it will give you similar issues.
To leave EDL press and hold volume down and power for 1 minute or longer.
Try this
Install the All in One tool and use it to update your android and fastboot drivers. Afterwards see if the computer recognises the phone port connection by going to Control Panel>System> Device Manager* ( Even though, you may not see the drive, you will maybe still see unknown device or te port)
Maybe a Brick?
If it does not see the phone or show a unknown USB device with port 9008
Try placing the phone into EDL mode by pressing and holding the Vol Up (+) and Vol Down (-) together while simultaneously connecting the phone by USB cable to the computer. Do you see the port or phone now? If you see port 9008 you possibly are bricked, follow the steps on my unbricking thread., if you can not get back to TWRP, or fastboot,and the phone keeps a charge. Then I would think that you are definitely bricked.
Other possible issues
The issue could be the battery. Have you tried using other USB C Cables? If you can use a different usb cable let it charge for a couple of hours then see if you can get into TWRP again . If you can enter fastboot mode try reflashing TWRP, you can use the All in One tool for this.
tsongming said:
Doesn't seem like a a fried motherboard. In my experience, If you fried the CPU, you would still be able to access Fastboot, if you fried the GPU part of the chip, or if the LCD has failed you would feel vibrations..
Do you thin it is possible that you accidentally put the phone into EDL mode? It can sometimes be hard to get out of, and it will give you similar issues.
To leave EDL press and hold volume down and power for 1 minute or longer.
Try this
Install the All in One tool and use it to update your android and fastboot drivers. Afterwards see if the computer recognises the phone port connection by going to Control Panel>System> Device Manager* ( Even though, you may not see the drive, you will maybe still see unknown device or te port)
Maybe a Brick?
If it does not see the phone or show a unknown USB device with port 9008
Try placing the phone into EDL mode by pressing and holding the Vol Up (+) and Vol Down (-) together while simultaneously connecting the phone by USB cable to the computer. Do you see the port or phone now? If you see port 9008 you possibly are bricked, follow the steps on my unbricking thread., if you can not get back to TWRP, or fastboot,and the phone keeps a charge. Then I would think that you are definitely bricked.
Other possible issues
The issue could be the battery. Have you tried using other USB C Cables? If you can use a different usb cable let it charge for a couple of hours then see if you can get into TWRP again . If you can enter fastboot mode try reflashing TWRP, you can use the All in One tool for this.
Click to expand...
Click to collapse
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode. Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
kakobr said:
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode.sl Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
Click to expand...
Click to collapse
Well that sucks, if you feel like sending to the phone to China for repair, you can find several shops that are offering to repair any damaged Leeco for $10 and an average cost of $30 for resoldering. On the TaoBao website, use Chrome for translation. Some of their ads mention overseas repair
If it's memory it would be an easy fix for them.
If you don't want to fix it, I highly recommend the Mi8 if it's within your budget, its a perfect phone and you can find them for close to $300. My brother has a Redmi note 6 Pro which is also really nice. He paid $190.
Good Luck.
Sent from my Xiaomi MI 8 using XDA Labs
kakobr said:
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode. Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
Click to expand...
Click to collapse
Check out this possible do it yourself fix : https://forum.xda-developers.com/showpost.php?p=79302729&postcount=71

suddenly dead from dfu?

so been trying to update my axon 7 and ended up with no fastboot but unlocked, with stock oreo
played about abit further and phone would show as zte diagnostics dfu when plugged in (using stock cable)
i might of been in edl? mode (not flashing anything or doing anything as no tools would detect phone but was in device manager as zte diagnostics. i think i unplugged it to reboot but now it does nothing at all
no led, no haptic buzz no screen
tried removing sim and microsd, tried long presses and short presses. nothing
pc doesnt detect it when plugging in
any ideas? :'(

QDLOADER 9008 - Bricked/dead mobo?

Hello all!
Well, my friend´s oneplus 5 died when he was charging it, he thought it might be dead, but I decided to disassemble it and try to fix it. After battery was disconnected, I started to play around as I would do with another android to see if it would get recognized by computer... After while I figured out how to get it work as QDLOADER 9008 (windows update driver) and flashing started. I thought "well, no hw issue if this seems to work" but then, after 300 seconds of "DOWNLOADING CACHE.IMG" I started to worry. Well, after 926s, it stopped with error FIREHOSECHECKRSP FAILED, ERRNO: 258.
I tried almost everything, different cables, drivers reinstall, reconnecting and disconnecting battery, different versions of "cheeseburger", different Msmdownloadtool, fastboot/ADB cannot detect phone (which was expected) and etc. Phone always has green led light up after flashing with msmdownloadtool but nothing else is going on and I cannot get over this error. Phone is clearly hardbricked, but I am starting to believe this might be a dead chip (like memory chip, so it cannot hold/read data from it).
Do you agree guys, or do you have any other idea what to do?
Thank you!

Question - OP 8pro crashdump mode revival failed.

So my beloved OP8pro abruptly threw the Qualcomm Crashdump mode error... reached out to the one plus guys, they said the phone was not connecting to their software and will probably needs a new Mother board or ask me to find someone who does chip level repairs. Googled yesterday and found that many have revived their phones using MsmDownload tool.
So downloaded the required files and followed the instructions carefully. The phone was connected successfully and the process was pretty straight forward and finally the Download completed message came in green. As per the instruction the phone was supposed to reboot automatically but in my case the phone was dead, it is not even throwing the error like earlier when trying to switch on or none of the key combinations were working to get any kind of response from the phone..
Any way out of this? ...Plz advice guys.
Try to redo the MSM procedure again. Also you can try holding the Vol Up and Power for a minute.
Thanks @davidd..... It is not connecting still. Tried that also but still no luck..
I tried every key combinations to get some kind of response from the phone, but all seems to fail on me. Is there any other way to get it to respond?
Abruptly throwing Crashdump is a sign of motherboard error. I guess flashing via MSM just kill it faster.
I had some hours ago a non starting device. the only thing the mobile did was when i pressed vol up+down + on/off for some more seconds it vibrated shortly but nothing else.
so i tried again the MSM method but did not now how i should enter to EDL mode without display. First Windows loaded the mobile all the time with HS-USB Diagnostics 903E driver. So this was definitely wrong. After trying all possible button combinations and then plug the USB cable, i tried connect FIRST USB Cable to PC and bricked/dead OP8P THEN press vol up+down for some more seconds. If u have a look in your device manager while you do this, you may also have luck and the correct driver HS-USB QDLoader 9008 is loaded and the MSM tool can connect.
Good luck!

Categories

Resources