Database Users

Problem: Bootloader won't connect via USB, won't load from MicroSD

Hi,
From the bootloader I am unable to connect via USB or to flash from MicroSD.
I am running SPL-2.08.000 8G XE
I have magldr version 1.11 installed with a cyaogen mod 7 running on top of that.
On the PC, I am running Windows 7 x64.
When I run the bootloader (pwr on + hold vol dn) it says serial at the bottom and when I connect it to the Win7 machine one of three things happens.
1) Nothing.
2) On the Windows Desktop I get a message that "USB Device not Recognized"
3) On the phone, I get a white only bottom (no Serial or USB message)
This happens with both the routine to "disable drivers signature" by pressing F8, and without doing that.
I have also removed Windows Mobile Device Center 6.1 and the drv update. It still will not load. I have tried the AS drivers for Win7x64 and it says "no driver for this device found in this folder".
One possible solution was to flash the rom, via the MicroSD card, by renaming a .nbh to LEOIMG.nbh. However, I have tried several roms (1.66 roms, windows 6.5 roms, magldr 1.12 and magldr 1.13 nbhs) yet, the phone goes grey and says "Loading..." but nothing happens.
I am genuinely stuck.
I've been through a million forums and I can't seem to find a solution to my problem. As you can see I have tried several different solutions that I have found but none have worked.
My aim is to update magldr to ver 1.13 and load a newer rom.
Thank you,
P

"USB Device not Recognized"
This usually happens when cable is faulty or the jack.
It also happens when the phone is unresponsive.

crush said:
"USB Device not Recognized"
This usually happens when cable is faulty or the jack.
It also happens when the phone is unresponsive.
Click to expand...
Click to collapse
It charges... how else can I test the cable? Or the jack on the phone?
//edit: I have a spare cable and have tested it. It is not the cable. I have also cleaned the jack. A wiggle of the jack does not yeild any difference.
I went into Linux on my machine and ran
[email protected]:~$ dmesg | tail
[ 253.644057] usb 3-1: device descriptor read/64, error -62
[ 253.888054] usb 3-1: device descriptor read/64, error -62
[ 254.128061] usb 3-1: new low speed USB device using ohci_hcd and address 11
[ 254.269065] usb 3-1: device descriptor read/64, error -62
[ 254.512059] usb 3-1: device descriptor read/64, error -62
[ 254.752054] usb 3-1: new low speed USB device using ohci_hcd and address 12
[ 255.160725] usb 3-1: device not accepting address 12, error -62
[ 255.296064] usb 3-1: new low speed USB device using ohci_hcd and address 13
[ 255.705054] usb 3-1: device not accepting address 13, error -62
[ 255.705095] hub 3-0:1.0: unable to enumerate USB device on port 1
What I suppose is really unusual is that this has happened AND I'm unable to flash via MicroSD.
P

ok,
Are you using front USB port? if yes then try different port at back.
Because its strange on some motherboards that it stop reading properly from front usb's :-S this happened to me with my panasonic camera which wasn't readable at front but did work on back.
for more info you can goto these link
http://www.linux-usb.org/FAQ.html#ts6

[Q] [Help] Possible bricked Nexus 7 after 4.2 stock update

Hi all,
I'm really hoping someone can help.
This morning I applied the stock Google 4.2 (JOP40C) update from Google's factory images page using the supplied flash-all.sh script. The tablet applied the update, rebooted - and then I saw an error message saying an app had crashed, I believe it was the launcher but basically ignored it, and after pressing "okay" a few times I just held the power button until the power off dialog came up and I turned the tablet off.
Now it won't turn back on. I've tried the long-press method (I've tried 30 seconds, 1 minute, whilst plugged in to the mains, whilst plugged in to USB, volume up/down buttons held and not held) but so far it's as dead as a can of spam. I gave it a two hour charge on a wall charger, still no difference.
When attempting a stock flash / debrick via fastboot, fastboot just says "waiting for device" and waits forever. That's the same on Windows and on Linux, both systems usually work fine with ADB and fastboot.
When connected via USB to my Ubuntu PC, dmesg says:
Code:
[15660.333585] usb 3-1: new high-speed USB device number 4 using xhci_hcd
[15665.328725] xhci_hcd 0000:03:00.0: Timeout while waiting for address device command
[15670.527680] xhci_hcd 0000:03:00.0: Timeout while waiting for address device command
[15670.731479] usb 3-1: device not accepting address 4, error -62
[15670.731578] xhci_hcd 0000:03:00.0: Bad Slot ID 3
[15670.731579] xhci_hcd 0000:03:00.0: Could not allocate xHCI USB device data structures
[15670.731582] hub 3-0:1.0: couldn't allocate port 1 usb_device
[15746.062340] usb 3-1: new high-speed USB device number 5 using xhci_hcd
[15746.080922] usb 3-1: New USB device found, idVendor=0955, idProduct=7330
[15746.080925] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[15746.080926] usb 3-1: Product: APX
[15746.080928] usb 3-1: Manufacturer: NVIDIA Corp.
[15746.080983] usb 3-1: ep 0x81 - rounding interval to 32768 microframes, ep desc says 0 microframes
[15746.080986] usb 3-1: ep 0x1 - rounding interval to 32768 microframes, ep desc says 0 microframes
When attached via USB to my Windows PC, which usually works with Android / fastboot / APX devices just fine, I see an "unknown device" appear, with the status of:
Code:
Windows has stopped this device because it has reported problems. (Code 43)
Now I'm guessing it's dead and time to call Asus, but I wanted to check first. I went to back to the PC World store I bought it from and they say because it's a month old it's not their problem (over 21 days since purchase) so it has to go back to Asus.
Can anyone give any advice? Is there a way of re-flashing the bootloader some how without the need for fastboot? Is there something like nvflash for the N7 (I've seen this mentioned before here but it didn't seem to lead anywhere). Given that I can't get it to respond to fastboot nor ADB and as the screen never comes on I guess it's dead, but I'd welcome any hints before I call Asus - thanks in advance! :good:

[Z00LD] USB Connection not working (MTP, PTP, ADB), but USB OTG works

Hello,
It's been a while since I have been facing the problem described in the title. Only now I've managed to get some time to investigate the issue. I'm using LineageOS 15.1.
I was using Lineage 14.1 before, and I had the following issues:
USB OTG was not working
MTP, PTP (and the rest) ALSO not working
After I flashed Android 8.1, USB OTG started working, but ADB, MTP and PTP still did not work. I realized it could be a hardware problem. So I tried connecting with several different USB Cables: did not work. It is also not a driver issue, since I tested in multiple computers (with Linux and Windows);
Then, I bought a new charging board (the one that also has the phone's mic.) and exchanged the old one. That did not help at all.
I was messing around with ADB over network and I happened to make the phone get recognized - about 3 times - using the setprop command:
setprop sys.usb.config adb,mtp,ptp
The problem, after the OS (Ubuntu 16.04) managed to recognize the phone, was that as soon as I unplugged the cable and then plugged it back in, the phone stopped being recognized again. Running dmesg on my PC returned this:
[15548.910595] usb 1-2: new full-speed USB device number 12 using xhci_hcd
[15549.730614] usb 1-2: device descriptor read/64, error -71
Click to expand...
Click to collapse
I also got a device not accepting address error (on dmesg), which I forgot to copy
When I boot into the bootloader (Fastboot Mode), the dmesg output is:
Bus 001 Device 008: ID 0b05:4daf ASUSTek Computer, Inc. Transformer Pad Infinity TF700 (Fastboot)
Click to expand...
Click to collapse
I appreciate your help. Any extra information needed, please ask.
Thank you.

I have the same problem with the rom lineage-14.1 and 15.1

Unable to unlock bootloader

I've read the threads about unlocking bootloader in the redmi note 7, but none of them helped.
So the main problem is whenever I connect redmi into PC, it's recognized, but when I enter Mi Unlock app (miflash_unlock-en-3.5.1128.45), the phone is showing in left-up corner "..key to shutdown" (I can't see anything before key) and it's unmounting from PC.
I tried connecting it in many moments, but the result is the same. I tried also installing drivers from xiaomi, that you can install through the app itself, but it didn't change the results.
I've installed ADB app and drivers (as shown here: https://forum.xda-developers.com/showthread.php?t=2588979) and connected my device to mi account.
As in the thread on https://forum.xda-developers.com/redmi-note-7/how-to/one-redmi-note-7-unlock-bootloader-t3890751 I tried to check via ABS if my device is listed and there is the output:
C:\adb>fastboot devices
afd9005 fastboot
C:\adb>fastboot oem device-info
...
FAILED (command write failed (Unknown error))
finished. total time: 0.005s
Click to expand...
Click to collapse
And the device goes into that mode like from mi unlock app
I'm posting below the link to the screenshots of my phone's settings, os version and things that I've read could help (I don't know how to insert photos in the post other way).https://we.tl/t-O3Z7H6AABu
I've been fighting with it for too long... Maybe someone encountered this problem and/or is able to provide the fix.

You can see help here https://forum.xda-developers.com/redmi-note-7/help/fastboot-issues-t3964100
Should to try another PC or use a 2.0 USB HUB. I also have same problem with my laptop (core i3 with USB 3.0 port) but it's OK on an older PC (without USB 3.0)
Update: Hi, I found a better way to fix this problem. I did with my Dell 14 5447 (with Intel chipset and Windows 7). I uninstalled Intel(R) USB 3.0 eXtensible Host controler in Program and Features. And then download and install a newer driver from Intel (https://downloadcenter.intel.com/do...100-Series-and-Intel-C220-C610-Chipset-Family).

gazavn said:
You can see help here https://forum.xda-developers.com/redmi-note-7/help/fastboot-issues-t3964100
Should to try another PC or use a 2.0 USB HUB. I also have same problem with my laptop (core i3 with USB 3.0 port) but it's OK on an older PC (without USB 3.0)
Click to expand...
Click to collapse
Oh I didn't try with USB 2.0. I have one in Mobo, so on few hours I'm going to tell if it fixed the issue

gazavn said:
You can see help here https://forum.xda-developers.com/redmi-note-7/help/fastboot-issues-t3964100
Should to try another PC or use a 2.0 USB HUB. I also have same problem with my laptop (core i3 with USB 3.0 port) but it's OK on an older PC (without USB 3.0)
Click to expand...
Click to collapse
On my main PC plugging into a USB 2.0 on back panel didn't work, neither on my dad's PC, that have in the front panel USB 2.0.
So I opened the whole thing now on the laptop without USB 3.0 drivers installed. I installed win7 and I didn't have option in driver selection "Android", so I installed xiaomi drivers and just plugged the phone. AND IT WORKED! Now I just have to wait 102 hours XD
I have 2 modules inside my laptop that are connected to motherboard (1st include 2.0 usb, and 2nd 3.0, both on different sides of laptop), so they're in some way separated. I don't know how it would behave if I installed the drivers, but for now I'm not checking it.
Thanks you for help, I would never come up with that fix!
Just leaving the specs if it's caused by hardware and for someone who has the same:
i5-8400
B360M pro-vdh
Probably not improtant in this case, but just in case:
GTX 1060 3GB
16GB ram ballistix sport lt

=Terys;81704493]On my main PC plugging into a USB 2.0 on back panel didn't work, neither on my dad's PC, that have in the front panel USB 2.0.
So I opened the whole thing now on the laptop without USB 3.0 drivers installed. I installed win7 and I didn't have option in driver selection "Android", so I installed xiaomi drivers and just plugged the phone. AND IT WORKED! Now I just have to wait 102 hours XD
I have 2 modules inside my laptop that are connected to motherboard (1st include 2.0 usb, and 2nd 3.0, both on different sides of laptop), so they're in some way separated. I don't know how it would behave if I installed the drivers, but for now I'm not checking it.
Thanks you for help, I would never come up with that fix!
Just leaving the specs if it's caused by hardware and for someone who has the same:
i5-8400
B360M pro-vdh
Probably not improtant in this case, but just in case:
GTX 1060 3GB
16GB ram ballistix sport lt
My pleasure.

T95MAX Android12 Allwinner H618

Hello,
I bought the android box 12 T95MAX H618, the box boot looped when I received it (it turns on and after 5 seconds restarts).
I managed to get the stock firmware and I reflash it with Pheonix card, but it continues, if I unplug the box or leave it off for more than 5 seconds it boots in a loop.
I tried to connect the ox to the pc with phoenix suit and phoenix USB pro but they do not detect my box, while in windows it detects the box but marks me as an unknown device.
Do you have a solution to stop restarting in a loop?

which Android version? can you show pictures of the tvbox?

donmega_icecube said:
which Android version? can you show pictures of the tvbox?
Click to expand...
Click to collapse
the T95MAX runs on android 12, and here is a photo of the model.
and the stock firmware link: https://mega.nz/file/Vpsl1RQQ#pwUFrrZOGTgvzjoUpuoOHiO9dG3UkwWRB5V7bBDaDVU

I can't connect the box to the pc, I use a usb A -> usb A cable.
1 I connect the usb port on the pc but not the boxing and I disconnect all the other cables.
2 I keep pressing the reset button in the AV port
3 I connect the usb port on the box
I hear a sound like what the box are plug and in the device manager I see this:
"Unknown USB device: Device descriptor request failed"
Everything I tried but didn't work.
- Connected turn on usb debugging mode
-All the usb ports of the pc
-Install drivers
Do you have a solution I'm desperate

johnjohn07 said:
I can't connect the box to the pc, I use a usb A -> usb A cable.
1 I connect the usb port on the pc but not the boxing and I disconnect all the other cables.
2 I keep pressing the reset button in the AV port
3 I connect the usb port on the box
I hear a sound like what the box are plug and in the device manager I see this:
"Unknown USB device: Device descriptor request failed"
Everything I tried but didn't work.
- Connected turn on usb debugging mode
-All the usb ports of the pc
-Install drivers
Do you have a solution I'm desperate
Click to expand...
Click to collapse
first thing you need plugin your box again to the computer, then you need to start to remove all unknown usb devices from your device manager, you may need to click on "view > show hidden devices" in device manager to see all unknown usb devices, remove them all, then disconnect your box.
if you have anything in your programs related to drivers for your box, uninstall them before you plug the box back in.
if this is a desktop computer, try to avoid front usb ports if possible.
if you have a second A-A USB cable, test with that if possible.
now before you plugin your box, you need to install the correct drivers, normally the manufacturer or your supplier can give you those, don't download any random T95Max drivers online because there are at least 3 different models of T95Max tvboxes as far as I know, and yours is a newer model.
after installing the drivers, then follow these steps exactly:
- unplug all cables from the tvbox
- plug in one end of the USB cable to the computer only
- have the firmware flashing software open
- press and hold the reset button which is usually placed inside the AV port in most boxes
- while holding the reset button, plugin only the USB cable, then release the reset button
if it's detected correctly, you can move on with the rest of the steps, if it's not detected, then unplug it and repeat the steps but this time plug the USB cable to a different port on the tv box, because not all ports support firmware flashing.
- i'm sure you know the remaining steps since you have the firmware and probably the software for flashing the firmware.
if you try all ports on the tv box and still not working, I would probably still try on a different computer, if that fails as well, then all I could say it might be a defective box, you could maybe try the sdcard method if possible on your tv box, or contact the supplier where you got it from
good luck

donmega_icecube said:
first thing you need plugin your box again to the computer, then you need to start to remove all unknown usb devices from your device manager, you may need to click on "view > show hidden devices" in device manager to see all unknown usb devices, remove them all, then disconnect your box.
if you have anything in your programs related to drivers for your box, uninstall them before you plug the box back in.
if this is a desktop computer, try to avoid front usb ports if possible.
if you have a second A-A USB cable, test with that if possible.
now before you plugin your box, you need to install the correct drivers, normally the manufacturer or your supplier can give you those, don't download any random T95Max drivers online because there are at least 3 different models of T95Max tvboxes as far as I know, and yours is a newer model.
after installing the drivers, then follow these steps exactly:
- unplug all cables from the tvbox
- plug in one end of the USB cable to the computer only
- have the firmware flashing software open
- press and hold the reset button which is usually placed inside the AV port in most boxes
- while holding the reset button, plugin only the USB cable, then release the reset button
if it's detected correctly, you can move on with the rest of the steps, if it's not detected, then unplug it and repeat the steps but this time plug the USB cable to a different port on the tv box, because not all ports support firmware flashing.
- i'm sure you know the remaining steps since you have the firmware and probably the software for flashing the firmware.
if you try all ports on the tv box and still not working, I would probably still try on a different computer, if that fails as well, then all I could say it might be a defective box, you could maybe try the sdcard method if possible on your tv box, or contact the supplier where you got it from
good luck
Click to expand...
Click to collapse
my box t95MAX is well detected by my pc but in the device manager there is written
"Unknown USB device: Device descriptor request failed"
How to solve this problem?
Maybe I need special drivers?

johnjohn07 said:
my box t95MAX is well detected by my pc but in the device manager there is written
"Unknown USB device: Device descriptor request failed"
How to solve this problem?
Maybe I need special drivers?
Click to expand...
Click to collapse
My friend, this exactly means it's the drivers aren't installed, that's why I sent you the steps you need to follow.
Also you can't say it's well detected if it shows unknown usb device in control panel, hearing your computer making a ding sound doesn't always mean it's a good thing

I bought this same exact box, but my issue has been not being able to install Teamviewer QS nor the Host file. I downloaded that stock firmware image and tried burning it onto a microSD card, but I kept getting failed to load error. After doing further research, it turns out you need to install MS Visual C++ Redistributal Runtimes. I downloaded the all in one file which installs all the Redistributal files.
Then using PhoenixCard Tool (v4.24), I burned the image onto the microSD card. BTW, when the process is done, you'll see many partitions were created on the card. I unplugged the power to the box, popped in the microSD card, plugged the power back in and upgrade process automatically started. It booted back up, screen loaded up all the software and all was running. Teamviewer apps still won't run though.
I wish there was a way to downgrade to Android 11, 10, or even 9. Good luck!