I was flashing the zui with qfil and now my zuk is with a black screen and vibrate every 32 seconds
Qfil error: https://imgur.com/a/pUjb3IB
Chewbaccaun said:
I was flashing the zui with qfil and now my zuk is with a black screen and vibrate every 32 seconds
Qfil error: https://imgur.com/a/pUjb3IB
Click to expand...
Click to collapse
Well use this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/lenovo-z2-plus-zuk-z2-plus-hard-brick-t3713126
JV Spartacus said:
Well use this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/lenovo-z2-plus-zuk-z2-plus-hard-brick-t3713126
Click to expand...
Click to collapse
problem solved
Nothing helps..?
(I will post this also here, cos no one answered @ zukfans yet)
Hi! I think I need to ask help now.
I've managed to hard brick my Z2 with QFIL trying to update the phone from zui 2.something to 3.5. Well obviously that did not end up good.
My phone went to a stage described in some cases: White light blinking every 15 seconds or something and phone vibrating. Ok, I tried to shut the phone down by keeping and releasing after second blink. Did not work. Then I tried to hold for two or more minutes. It seemed to work first but suddenly also that didnt work (kept power pushed for ten minutes or more). Ok, the I made the cable described here. I did a jumper cable from my usb extension cord. Windows reacted to the phone but did not recognize it. Nothing showed up in device manager or QFIL or MiFlash. The phone keeped on vibrating and a left it like this for the night. I guess battery ran out and phone finally shutdown.
I continued and same results. One time windows recognized a unknown device for some seconds but it did not show up in device manager or MiFlash. After that nothing. Now the phone only blinks the light. It vibrates only when trying to charge it or plugged in PC. I don't now if it's on or not. Anyways, the same results with windows: reaction, but no recognition. I've tried to pull usb out and change to another slot etc.
Also I've installed Zuk 1.05 drivers, MiFlash and tried also with Qualcomm drivers. Uninstalled everything and tried again. Nothing seems to help.
Could this be because of Windows 7? Or bad extension cord? Or what...? Any advice would be appreciated.
edit: It was not Windows problem I guess. I installed fresh Windows 10 with no help. Actually worse. No Windows is not reacting at all. Maybe it's the jumper cable I created. I didn't want to ruin my only USB-C.
edit: Ok. Back to Win7. Now there is no reaction at all also in Win7. The phone vibrates when connected to pc. Otherwise phone seems to be off. No lights flashing. If power is held down white led flashes briefly but no vibration.
edit: Now if I connect the phone to laptop the led blinks every 0.5 seconds... I have no idea how turn the phone off. It seems to be off while not touched because nothing is happening...
@Pelepako
Try this,just a copy paste
2.0). Turn off the phone. If the phone boots up (reboots) then immediately to point 2.1
2.1). Put wire on the 2nd contact on the left
. And together with the wire insert into the PC (at the same time the phone is already connected by cable).
2.2). After 5-10 seconds, take out the usb plug with the wire. Remove the wire and insert the plug back.
2.2.1). If you do not have a bootlap, but it hangs on MI, on the boot process, etc. Hold the POWER button and insert the USB plug with the wire into the usb port. The screen goes out and you get what you want.
3.1). Your device in EDL mode.
3.2). Click REFRESH in Miflash and see your device in COM format.
3.3). Flash firmware at your discretion.
Thanks for the instructions.
Still nothing. Windows 10 does not recognize the phone in any way. The phone vibrates almost immediately when plugged in. Then nothing. Sometimes (before) I got Windows to recognize it as "unknown device".
2.0 Turning off the phone. I'm unpluggin the battery. I guess that does the job? At least nothing is flashing or vibrating.
2.1 I inserted a paper clip as in the picture.
Dunno if it's a driver thing. I've installed different Zuk driver version, Qualcomm, MiFlash, QFil, ADB.. you name it. I've turned on the Test Mode in Windows (driver signature). I've tried two different cables. One of them is the original. Tried the paper clip trick and the wire connect trick. Nothing is working. There has to be some flaw that I'm not noticing. Can't be the only one who really got his phone bricked...
About the drivers:
Ive installed zuk 1.05. Is it ok? Tried also 1.06 and 1.08.
How to install ADB. I've used ADB installer and installed system-wide. Should I also install the device driver (Google)?
Qualcomm drivers. Cannot manually install. With Miflash etc. some Qualcomm drivers get installed.
Do I need to install Fastboot and ADB "executables"? Where do I need these in my situation? Nowhere?
What abou QFIL? Is it necessary if I'm using MiFlash?
narshi shukla said:
@Pelepako
Try this,just a copy paste
2.0). Turn off the phone. If the phone boots up (reboots) then immediately to point 2.1
2.1). Put wire on the 2nd contact on the left
. And together with the wire insert into the PC (at the same time the phone is already connected by cable).
2.2). After 5-10 seconds, take out the usb plug with the wire. Remove the wire and insert the plug back.
2.2.1). If you do not have a bootlap, but it hangs on MI, on the boot process, etc. Hold the POWER button and insert the USB plug with the wire into the usb port. The screen goes out and you get what you want.
3.1). Your device in EDL mode.
3.2). Click REFRESH in Miflash and see your device in COM format.
3.3). Flash firmware at your discretion.
Click to expand...
Click to collapse
Ok. Just found out that the only 2.0 port is broken. There is no second pin. At least anymore. I might have broken it in some point.
Other reason for malfunctioning could be the circuit board of the phone. The previous owner in all his wisdom had glued the battery cover with super glue. As I opened it it ripped of some of those circuit materials that conduct electricity. The broken part is near the usb port of the phone. Maybe if I put the cover back it will work cos the ripped parts are still glued to the back cover..
So back to the issue.
The broken part of the phone seems to be speaker so it should not affect the connection I guess. I also fixed with conductive silver paint. Still, no help.
Just found out that the charger and probably also the cable are not original ones. Maybe this is the reason for this is not working. I cannot come up with any other solutions. Now I would need to know which usb cable would qualify for the procedure. How can tell which is a proper cable before buying it? Also does the micro-usb cable work if I have the convertor dongle (Samsung made)?
edit:
Ok. Sometimes the led blinks every 0.5 sec. Sometimes phone vibrates every fifteen or something seconds. Only way to get the computer to react is with modded usb extension cord -> green to black. This way Windows recognizes an unknown device. That's it. I cannot install Qualcomm drivers for this or do anything else. This way Windows makes this connected sound every 0.5 seconds and the phone led blinks. After a while it stops and the phone is marked as "unknown device". Also if I connect the phone to a charger it blinks all the time (0.5s) and vibrates occasionally. Then after a while the led calms down and blinks every 15 seconds. And then back to 0.5s with vibration. All these symptoms seem unclear and I haven't found anyone suffering from same kind of problems...
Really am I the first that really bricked this one? I didn't even use the phone yet. Just checked it and tried to update the system cos it was old version.
I assume that the phone has to be off after disconnecting battery cable so that should not be the problem here.
@narshi shukla
I turned the phone off by removing battery. It does not reboot after shut down before I connect it to computer. Few seconds after connecting to pc it vibrates shortly. Nothing else happens after that. Same with and without the wire.
I've tried so many different methods that I'm giving up with this I guess. Am I the only one who got his phone permanently bricked. After all I tried to flash by following instructions. The flash failed and phone went on crazy vibration and screen on for some seconds after that it was vibrating every 15 seconds. Then suddenly it stopped doing that. Now it does only if I plug it to pc or charger.
The "black green wire trick" is strange. If I only connect those two wires nothing new happens BUT if I connect green to black and black to green by tying instead only touching the phone vibrates and led blinks every 0,5 seconds and windows also makes the connection sound even though it is not working.
narshi shukla said:
@Pelepako
Try this,just a copy paste
2.0). Turn off the phone. If the phone boots up (reboots) then immediately to point 2.1
2.1). Put wire on the 2nd contact on the left
. And together with the wire insert into the PC (at the same time the phone is already connected by cable).
2.2). After 5-10 seconds, take out the usb plug with the wire. Remove the wire and insert the plug back.
2.2.1). If you do not have a bootlap, but it hangs on MI, on the boot process, etc. Hold the POWER button and insert the USB plug with the wire into the usb port. The screen goes out and you get what you want.
3.1). Your device in EDL mode.
3.2). Click REFRESH in Miflash and see your device in COM format.
3.3). Flash firmware at your discretion.
Click to expand...
Click to collapse
Related
Hello everyone,
having major USB issues on my GNex. It's not charging anymore, but when the phone is off, it displays a charging animation. I could get it to charge once since this occurred, I left it plugged in overnight on my Mac (phone turned off). Did the same thing last night, no charge at all.
Mac OSX does not recognize the device, my Windows machine keeps telling me something like "the connected device is not working properly and can't be used... ". This message pops up every few seconds, so I guess it's constantly connecting and disconnecting. I can't access the internal storage on both systems.
My first guess was a hardware defect. But when I try to boot into recovery mode, a screen instantly pops up that shows Andy and displays a message: "Downloading. Do not turn off target.". In the upper left corner it displays " ODIN MODE" in small red letters.
When I press the power button in this screen (there is a big arrow pointing to the button with "start" written in it) the phone just normally reboots.
I can't get into fastboot mode because of this. I can get into CWM Recovery when i use the reboot into recovery option built in the ROM.
I dunno much about Odin (next to nothing). Has it something to do with Samsungs Kies? Could it be that something has put my phone in this "ODIN MODE" and it constantly tries to download something, making the USB port unusable? The port is not completely broken, as the phone displays a charging animation when it's turned off... so there is some connectivity left!
Thoughts coming up that this could be some kind of software issue. If there is a possibility to get out of the Odin Mode, it may solve the problem.
The phone is unlocked and rooted, running AOKP Milestone 5 and franco kernel.
I tried to restore an older nandroid, but it did not change anything.
Would send it in for exchange, but not able to relock the bootloader due to no fastboot access. If it can be confirmed that this is a hardware problem, I have to pay for the repair, I'm fine with that.
Has anybody any ideas that could be helpful? Any help is much appreciated, thank you in advance!
Do a search and you will find at least 30 helpful threads. Basically you only need to replace your USB charging board and it works again. Should be a warranty issue, but Samsung has really been an ass on handling this issue lately and claiming water damage.
I have mentioned it many times here: this problem can be probably solved by thoroughly cleaning your USB with soft toothbrush.
True, I also cleaned my port but it only fixed it temporarily.
Thanks guys. Tried to clean the port, nothing changed.
Ordered an OEM charging board off ebay, hope changing it will fix the issue.
Only thing I'm wondering about is, that the phone is stuck in Odin Mode when I boot it up with Vol. - and the Power Switch. So I downloaded Odin but it does not recognize the phone...
I am also facing the same problem. I am currently using the phone by charging the battery externally. Can someone confirm that changing the USB flex cable is the solution ?
Just posted in another thread but it is definitely the USB port for me. Using an HTC Vision (Google g2)
Hello everyone. My brother has the SM-T320. It doesn't power on at all. But if I plug the tablet directly into an outlet or laptop, it turns on but immediately goes to "recovery booting" and looping and not actually turning on. I can press the Power+Volume Down buttons to go to Download mode. I have three laptops at my disposal. I installed the Samsung USB drivers on two, and just Samsung Kies on the other. I have also tried different Odin versions (3.07 and 3.09) and it still won't connect. I also bought a different battery, and even if I leave it charging (aka bootlooping), if I disconnect it, it turns off. Essentially, I think the firmware is messed up and simply doesn't recognize the battery. So that's why I wanted to flash a stock recovery. Any ideas what I can try? Thanks a lot for the help!
I should also mention that I tested battery connection (tablet plugged into an outlet with the battery removed) with a volt meter and I gut 4.45V, which I think is fine?
mark1995n said:
Hello everyone. My brother has the SM-T320. It doesn't power on at all. But if I plug the tablet directly into an outlet or laptop, it turns on but immediately goes to "recovery booting" and looping and not actually turning on. I can press the Power+Volume Down buttons to go to Download mode. I have three laptops at my disposal. I installed the Samsung USB drivers on two, and just Samsung Kies on the other. I have also tried different Odin versions (3.07 and 3.09) and it still won't connect. I also bought a different battery, and even if I leave it charging (aka bootlooping), if I disconnect it, it turns off. Essentially, I think the firmware is messed up and simply doesn't recognize the battery. So that's why I wanted to flash a stock recovery. Any ideas what I can try? Thanks a lot for the help!
Click to expand...
Click to collapse
OK so it is in download mode when you connect it to Odin?
Hey everyone, I got the problem partly fixed. I was able to reset it to original firmware by using the Samsung kies3 software. It somehow was able to recognize the device even though Odin couldn't. However, turns out, the reason tablet would turn on only when plugged in is because the battery wasn't connected completely. The battery connector on the motherboard itself is separating and so the pins are not touching the board completely. My ghetto temporary fixed was to cut and stick part of a bobby pin over it to clamp it in place. However, this will probably damage the connector/board in the long term. I'm not very good with soldering parts/pins that are this small, and nor do I have special equipment besides solder and soldering iron, so I'm trying to figure another clever way of holding it strongly in place. If anyone has any idea how to go about that, it would be appreciated.
My 1020 got bricked while flashing through WPInternals.
In the middle of the flashing the USB got disconnected and after that I have blank screen. The power button pressing does make phone vibrate. Also soft reset combination makes vibration. However I am not getting anything on my laptop on USB connection. No connection notification. Nothing on device manager. I tried combinations to get it detected but nothing works.
So the question is, Is there any way I can blindly send force flashing to one of the USB port and make it happen ?
JTAG is the only option ?
Removed the display. Disconnect the battery. Remove the protective cover from the processor. Looking at the diagram R3209. Complete with a thin wire the resistor into the casing and at the same time connected to the computer. Defined as "Nokia Emergency Connectivity". After that, you run WPInternals, and continue from the point where the error occurred.
booker50rus said:
Removed the display. Disconnect the battery. Remove the protective cover from the processor. Looking at the diagram R3209. Complete with a thin wire the resistor into the casing and at the same time connected to the computer. Defined as "Nokia Emergency Connectivity". After that, you run WPInternals, and continue from the point where the error occurred.
Click to expand...
Click to collapse
Honestly, I did not understand what to connect to what.
Remove the display
The picture 1 shows what you need to remove. CAREFULLY remove all protection, or only in the marked area.
The picture 2 shows what you'll see under the removed protection. Looking for R3209 marked in the picture 3
After it is found, connect USB cable TO THE PHONE. NOT TO THE COMPUTER. The cable should be connected ONLY by phone
For one or two seconds before doing a short circuit of the resistor R3209 on the metal area of the body (picture 4), AND THIS TIME connect it to your computer
The phone shall be determined by the computer as "Nokia Emergency Connectivity" or "CareSuite Emergency Connectivity"
Run the program WPInternals
Make or restore the bootloader or unlock the bootloader. Depending on where you broke the phone last time.
After the program sends the phone into reboot, connect a known-CHARGED battery WITHOUT DISCONNECTING the computer. The phone should start to boot.
Have you tried all the options in WP Internals first? Including instructions on how to recover from bricked phone? I haven't got the application in front of me, but I seem to remember there are different flashing modes you should probably experiment with before opening up your phone.
GeoffreyK said:
Have you tried all the options in WP Internals first? Including instructions on how to recover from bricked phone? I haven't got the application in front of me, but I seem to remember there are different flashing modes you should probably experiment with before opening up your phone.
Click to expand...
Click to collapse
There are no longer any options. The phone is not defined in any way. And no the program will not see it without initializing it as a device in the system. The only option is to short out the memory, so she rebooted. What I'm suggesting. The operation is not difficult and takes no more than 10 minutes for anything.
try to charge the phone, at least 1 hour, then try to make hard reset, that works for my
GeoffreyK said:
Have you tried all the options in WP Internals first? Including instructions on how to recover from bricked phone? I haven't got the application in front of me, but I seem to remember there are different flashing modes you should probably experiment with before opening up your phone.
Click to expand...
Click to collapse
Yeah, phone is not detected by USB connection. I have already changed USB flex cable of the phone so its not an issue.
jeovanyerazo said:
try to charge the phone, at least 1 hour, then try to make hard reset, that works for my
Click to expand...
Click to collapse
Phone does not hard reset without OS in the memory.
booker50rus said:
Remove the display
The picture 1 shows what you need to remove. CAREFULLY remove all protection, or only in the marked area.
The picture 2 shows what you'll see under the removed protection. Looking for R3209 marked in the picture 3
After it is found, connect USB cable TO THE PHONE. NOT TO THE COMPUTER. The cable should be connected ONLY by phone
For one or two seconds before doing a short circuit of the resistor R3209 on the metal area of the body (picture 4), AND THIS TIME connect it to your computer
The phone shall be determined by the computer as "Nokia Emergency Connectivity" or "CareSuite Emergency Connectivity"
Run the program WPInternals
Make or restore the bootloader or unlock the bootloader. Depending on where you broke the phone last time.
After the program sends the phone into reboot, connect a known-CHARGED battery WITHOUT DISCONNECTING the computer. The phone should start to boot.
Click to expand...
Click to collapse
I will try this, need time to open the phone again. Specially I have never opened the processor part before.
Try what I told you, it's a software problem not hardware. Try hard reset.
jeovanyerazo said:
Try what I told you, it's a software problem not hardware. Try hard reset.
Click to expand...
Click to collapse
its a software problem only, but as I have described - mobile is not getting detected via USB and as the previous flash did not happen completely there is no OS in the memory. The phone only vibrates on power or reset combination.
On connecting the charger the start button blinks once in a while and thats the only response I am getting.
booker50rus said:
Remove the display
The picture 1 shows what you need to remove. CAREFULLY remove all protection, or only in the marked area.
The picture 2 shows what you'll see under the removed protection. Looking for R3209 marked in the picture 3
After it is found, connect USB cable TO THE PHONE. NOT TO THE COMPUTER. The cable should be connected ONLY by phone
For one or two seconds before doing a short circuit of the resistor R3209 on the metal area of the body (picture 4), AND THIS TIME connect it to your computer
The phone shall be determined by the computer as "Nokia Emergency Connectivity" or "CareSuite Emergency Connectivity"
Run the program WPInternals
Make or restore the bootloader or unlock the bootloader. Depending on where you broke the phone last time.
After the program sends the phone into reboot, connect a known-CHARGED battery WITHOUT DISCONNECTING the computer. The phone should start to boot.
Click to expand...
Click to collapse
Super cool man, thanks. I opened only tiny window from protective cover and sorted R3209. USB was detected and restored the Bootloader. Flashing was easy after that.
booker50rus said:
Remove the display
The picture 1 shows what you need to remove. CAREFULLY remove all protection, or only in the marked area.
The picture 2 shows what you'll see under the removed protection. Looking for R3209 marked in the picture 3
After it is found, connect USB cable TO THE PHONE. NOT TO THE COMPUTER. The cable should be connected ONLY by phone
For one or two seconds before doing a short circuit of the resistor R3209 on the metal area of the body (picture 4), AND THIS TIME connect it to your computer
The phone shall be determined by the computer as "Nokia Emergency Connectivity" or "CareSuite Emergency Connectivity"
Run the program WPInternals
Make or restore the bootloader or unlock the bootloader. Depending on where you broke the phone last time.
After the program sends the phone into reboot, connect a known-CHARGED battery WITHOUT DISCONNECTING the computer. The phone should start to boot.
Click to expand...
Click to collapse
Hi,
My 1020 got bricked while flashing with WPInternals and now won't switch on. No Vibrate when I push the power button either. I would like to try this method but can't figure out how to remove the protective plate on the CPU. I cannot find any help on Google nor YouTube. Can someone please enlighten me on which way the metal cover opens please?
Thanks in advance.
I've tried the same thing with a lumia 525 but accidently broken the resistor.. Can I do something with it?
Sometime you have to wait a few minutes or so for the phone to behave properly, especially with a blown firmware running.
There are many modes to a phone and each will be a different device to the PC.
There is normal mode
there is flash mode
there is emergency mode
and there is a recovery mode too.
and a couple of other modes uefiflash/bootemmc/bootmsc too.
each of these modes can be accessed by a combination of button presses that seems to change from phone to phone.
there is plug into usb port holding down volume up.
there is plug into usb port, hold down power and press volume down.
there is plug into usb port, hold down power and hold down volume up.
there is plug into usb port, hold down power, release, then press volume up
and like I mentioned before if the phone has a flat battery is will cycle from 0-5% battery charging then cycle 5-0% and reset the phone. it sometimes takes up to 5 min with the phone connected, trying multiple restarts to get the phone to appear to windows. sometimes it will appear and disappear, if you interrupt the boot process by having wpinternals running it will not disappear again and sometimes you have to do a complete reset cycle by holding down the power button until it vibrates with it still plugged into the pc, then immediately do another reset cycle.
the phone can crash on boot, so it fails to appear and in my experience it's behaviour is not consistent at all. boot one minute shows in device managed and then can take 10 minutes sometimes before it appears again. it seems to be very erratic behaviour. so keep at it.
opening up the phone and removing the metal shielding from the pcb to get access to the bypass test points should be a god damn last resort and not some first step as suggested to the op.
expect many pcb's to be damaged by this advice.
Ok, so I managed to remove the cover but a bit confused about the instructions for the resistor. Is there a special sort of wire I need to touch the resistor with while performing this "shorting" procedure or will any wire do? Intructions seem a little vague to the non electronically minded...
BeLlSiBuB said:
Intructions seem a little vague to the non electronically minded.
Click to expand...
Click to collapse
and still you've gone as far as removing the shielding?
if you think you can safely do it, the instruction state you need to short resistor R3209 as the phone boots. short means contact both sided of the resistor with something conductive and of the right shape and size to only touch those two parts of that resistor. maybe needle pointed tweezers or some tiny screwdriver?
jethro tarw said:
and still you've gone as far as removing the shielding?
if you think you can safely do it, the instruction state you need to short resistor R3209 as the phone boots. short means contact both sided of the resistor with something conductive and of the right shape and size to only touch those two parts of that resistor. maybe needle pointed tweezers or some tiny screwdriver?
Click to expand...
Click to collapse
Dude, thanx for your help! I have some metal tweezers. Do I need to put plastic protective cover on the end or them? Ive got some bubble wrap!
---------- Post added at 06:26 PM ---------- Previous post was at 06:18 PM ----------
All I seem to get is the Windows light coming on when I try to perform this. It also come on when I press volum down or volum up button and insert the usb.
Actually, the light comes on when I put it into the electric charger (not pc charger) as well, but stays on for longer.
BeLlSiBuB said:
Dude, thanx for your help! I have some metal tweezers. Do I need to put plastic protective cover on the end or them? Ive got some bubble wrap!
---------- Post added at 06:26 PM ---------- Previous post was at 06:18 PM ----------
All I seem to get is the Windows light coming on when I try to perform this. It also come on when I press volum down or volum up button and insert the usb.
Actually, the light comes on when I put it into the electric charger (not pc charger) as well, but stays on for longer.
Click to expand...
Click to collapse
you just need to charge the battery.
jethro tarw said:
you just need to charge the battery.
Click to expand...
Click to collapse
Really?
Can WPInternals kill a battery when it "Stopped working" and crashes?
Ahh, I thought you said "Change the battery". The battery was fully charged when it got bricked. I'm not sure how to charge this battery. I left it on charge for about 4 hours before attempting shorting procedure. I don't thing it is charging while plugged in now despite that light breifly coming on.
Dear,
today I received a new Xiaomi Mi5s (3/64 GB) but the phone will not turn on. I have tried everything, holding the power button for a long time, holding it in combination with Vol+ and Vol- buttons, connecting it to a laptop, charging it for a few hours but the phone will not boot.
It only blinks the red LED above the screen and that also stops after a few minutes of charging.
Could you please help me how to resolve this problem? Is it possible to resolve it without sending the phone back?
Thank you in advance!
The battery maybe depleted? Because when my Mi4s battery reached 0%, it does the same thing (on red led blinks whenever I tried to turn it on).
Try charging for like a hour, and then try to turn it on again.
Where did you buy it from?
Try a different charger/cable and turn it on while it's connected to power.
If that doesn't help, contact your seller, maybe they fuc*** up the flash to an international rom..
Thank you all for the input but nothing helped. I charged it with the original charger, with a laptop and with a different charger, for an hour, overnight and more than 12 hours. Nothing worked.
I bought it from TopOne on AliExpress.
In that case immediately contact them via the aliexpress website and ask for warranty.
I have been in contact with them and sent them an unpacking video and the video of the problem and this is their response:
"Dear Marko,
We got the problem about your phone.
Please hold 2-5 days. After we working out the multi-language rom, we will teach you flash it.
It may sove this problem.
Please trust us, we will keep contacting with you.
Have a nice day.
Best Regards"
Do you think I should trust them or open a dispute? I heard from multiple sources that TopOne is a trustworthy seller.
Do you think that this problem could be solved by flashing? I tried to boot it in recovery mode and also connecting it to a PC, but the PC did not react, it did not recognize anything being connected.
Check aliexpress site first, regarding their dispute rules. How long, after receiving the article, can you open a dispute?
But yeah, I would trust them, although it looks bad (if it's not turning on, doing nothing at all, you can't flash it normally) for your phone.
Thank you for the help. I'm going to try to flash the Fastboot via the Deep flash cable according to these instructions: http://forum.xda-developers.com/mi-5s/how-to/how-to-flash-hard-bricked-mi-5s-mi-5s-t3490252
MiFlashTool chinese version, this is it. Just connect phone, it will popup
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Do you mean that I should try to connect it just with normal USB cable? Or should I create a deep flash cable first?
Also, after I flash the Fastboot, what are the next steps, flashing the recovery and ROM? Could you please also send me a link to instructions what to do after Fastboot flashing?
Thank you in advance!
Boze... Just use the official tool and this will download the firmware and flash, if u just see a red LED. It's super easy and you get official anything.
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
I tried to create a deep flash cable from the original USB cable but didn't succeed. There were 4 wires: white, green and 2 red wires. There was no black wire. There is also a possibility I haven't connected them properly. Should I maybe try to buy a new cable and try again or?
UPDATE: I have bought a new cable and tried again. This cable had white, green, red and black wires. No success again.
When I connect the phone to the PC, the red LED starts blinking but nothing happens. This happens in both cases, when the black and green wires are connected and when they are not connected, so I assume that this makes no difference. Am I doing something wrong?
mnavijalic said:
UPDATE: I have bought a new cable and tried again. This cable had white, green, red and black wires. No success again.
When I connect the phone to the PC, the red LED starts blinking but nothing happens. This happens in both cases, when the black and green wires are connected and when they are not connected, so I assume that this makes no difference. Am I doing something wrong?
Click to expand...
Click to collapse
Check your device manager
Code:
Windows+R -> devmgmt.msc
Under the COM & LPT Ports section, is there any Qualcomm 9008? If yes, then you are good to go flashing your phone with MiFlash.
Red LED blinking with no display, AFAIK, only means three things:
1. No battery juice left
2. Phone is in emergency download (EDL) mode (port 9008)
3. Phone is in diagnostic mode (Port 900E)
You can only flash the phone on port 9008, not 900E.
awaaas said:
Check your device manager
Code:
Windows+R -> devmgmt.msc
Under the COM & LPT Ports section, is there any Qualcomm 9008? If yes, then you are good to go flashing your phone with MiFlash.
Red LED blinking with no display, AFAIK, only means three things:
1. No battery juice left
2. Phone is in emergency download (EDL) mode (port 9008)
3. Phone is in diagnostic mode (Port 900E)
You can only flash the phone on port 9008, not 900E.
Click to expand...
Click to collapse
Yes, I have checked the Device manager and nothing shows up. The computer does not react at all when I connect the phone. There is no port 9008 or 900E. I also installed MiFlash Tool and refreshed it when I connect it, but it doesn't recognize the phone being connected.
Red LED is blinking as soon as I connect it. The battery cannot be without juice, because I have tried multiple times to charge it for a few hours. The red LED was also blinking then (but not for long, maybe for a minute or so). Also, when I took it off the charger, both the charger and the phone were pretty warm.
Actually the wire colors do not need to match the video, I'm not sure if there's even a standard for the wire colors on USB. It's well possible that you have the wrong wires connected
Really? Because everywhere I checked it said the following:
1. Black - GND
2. Red - Power (+5V)
3. Green - Data +
4. White - Data -
If this is not 100% correct, I'm going to try to connect the other 2 wires today (possibly black and white). The goal is to connect the Data+ and GND wires if I'm correct?
Do you have a Multimeter? With that you can check the pins and cables and discover which is which.
Yes, I have it and plan to do so today after work. I will report here if I succeed or give up.
I have an issue very similar to this thread: https://forum.xda-developers.com/nexus-7-2013/nexus-7-2013-qa/unable-to-nexus-7-fastboot-mode-t3966600
I got mine for parts on ebay with "power issue." It had low battery and it charged up fine overnight, but when it boots up to either system or recovery it just stays on the Google logo.
It boots into Fastboot fine, but it will not connect to my computer. Computer has the lastest Manjaro linux with android-tools and connects to my Xiaomi Mix 2S fine, but neither "fastboot devices" or "lsusb" will show anything about the nexus, in USB 2 or 3 ports.
I opened it and reseated the silver cable between the boards, and also tried several different micro-usb cables, no dice. The port and circuit boards look completely fine. The screw seals show that it has been taken apart before.
I was not able to boot it to enable usb debugging, does fastboot need that?
Update: I did actually get it to boot, when I opened it I unplugged the battery and held the power button for a while to drain all the power. Fastboot still does not work, but I was able to factory reset it and install the last two updates. Curiously, I cannot connect to it with USB, maybe the data lanes are dead? And then after using it a half hour, it froze and I had to hold the power button to turn it off, and now its back stuck at the google logo.
Ekterm said:
I cannot connect to it with USB, maybe the data lanes are dead?
Click to expand...
Click to collapse
Measure the data lanes:
https://forum.xda-developers.com/showpost.php?p=80212550&postcount=4
and
https://forum.xda-developers.com/showpost.php?p=80218074&postcount=6
It's a different USB issue but the measurements must be the same.