Develop Bugs

"Recovery booting". Can access download mode however.

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.

New Xiaomi Mi5s not booting

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.

Fastboot reboots immediately when connected over USB

So I was going to unlock my boot loader and do all the fun rooting things now that Magisk is working, and when I got to the point of entering fastboot to run the necessary commands, it would just reboot as soon as I entered fastboot mode. To be clear, I turned off my phone, waited a bit, power+vol down, saw the fastboot screen for <1 second, then it started booting.
So I tried unplugging from USB, and could get into fastboot fine, and stay in it as long as I wanted selecting whatever options I wanted, then, as soon as I connected the USB cable (that came with the phone), it would reboot.
So I did a factory reset, didn't set up a pin, fingerprint or anything similar, same thing, about a half second of the fastboot screen, then a boot screen.
I tried booting into fastboot with adb, same thing.
I'm not sure what is happening here, and I've never had this kind of problem before. Anyone have any advice?

I would try using a different cable, and/or a different USB port. I've seen and experienced it being very picky.
My new rig I built has us 3.0 on the front and 2.0 in the back, my pixel absolutely hates being plugged into the 3.0 port, when I plug it in, it does nothing but spam connection/disconnection, once I plugged it into a 2.0 port it works fine

If you are using any kind of hub or extension cord remove them and plug in directly to the PC. I had this problem on my 1st 2XL but so far the 2nd hasn't given me a problem. I did move my PC closer to my desk to eliminate any extensions I had.
EDIT: I'm using my old USB cord from my Pixel 1 plugged into my USB 3.1 port.

Ah, I only have one USC C cable and one USB C port. I'll grab a USB A to C cable after work. Will update in about 9 hours.
Thanks!

USB A to USB C cable did it. Thanks for the help!

Ultimate Bricked Zuk z2

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

Is my Nexus 7 bricked?

I have the Nexus 7 2013 WiFi flo tablet with LineageOS installed.
I’ve not used it in over 12 months but today I was using it.... it turned off, loaded up the Google screen with a locked padlock and won’t go further.
In recovery mode it has TWRP, but the screen and volume buttons are unresponsive, the power button works but I can’t swipe to unlock or click anything.
I’ve plugged it into my MacBook and it’s not detected, I plugged it into a windows laptop and it says the device is unrecognised or malfunctioned.
I installed the android SDK on both and the USB driver on the windows machine.
Also changed between 5 different cables and different ports.
I can’t reflash and I can’t touch the recovery.
What can I do?
Thanks

Retrospock said:
...
Also changed between 5 different cables and different ports.
I can’t reflash and I can’t touch the recovery.
What can I do?
Thanks
Click to expand...
Click to collapse
All these problems, including no USB, are caused by poor connection between the PCBs.
Try this simple trick https://forum.xda-developers.com/showpost.php?p=66952073&postcount=3
If it does not help, you'll have to re-seat the wide, silver cable on both ends. Disconnect the battery first of course and watch https://www.youtube.com/watch?v=C9PwK9eGrCY
:good:

k23m said:
All these problems, including no USB, are caused by poor connection between the PCBs.
Try this simple trick https://forum.xda-developers.com/showpost.php?p=66952073&postcount=3
If it does not help, you'll have to re-seat the wide, silver cable on both ends. Disconnect the battery first of course and watch https://www.youtube.com/watch?v=C9PwK9eGrCY
:good:
Click to expand...
Click to collapse
I got frustrated earlier with the google screen and I squeezed, the Lineage loading bar came on!
I came here to report this finding and saw your reply... I've tried reseating that cable so I'll wait and see hownwe get on. Thank you very much for the help