I can't connect device via qpst - Xiaomi Redmi Note 7 Questions & Answers

To summarize when I put it in diag it connects and disconnects very quickly in the QPST, showing what it should, then esn 0 and then disconnected device, this flashing all the time, I assume it was after a corrupted .qcn, I wonder if you have some solution for that and that i can recover my imei and wlan.
Here what happened to get to this problem: my Chinese note 7 had a problem, I had to reset via edl for verified account and then unlocked the bootloader. Since the time I needed edl verified it has returned without wifi and without imei. I had managed to recover the wifi but imei it not through QPST, until I used it again and the cell phone went to Orangefox direct. I tried a new one. Qsn but the computer gave a problem, I ran out of backups and I can't connect anymore, always flashing between connected and disconnected devices, from time to time appearing what should be quickly.

Related

Galaxy Tab not recognized by CDMA WS, QPST or QDXM but....

....in device manager the diag drivers and the port show up fine. I can connect with Odin in recovery and connect through ADB. I have another Tab (same model) and connects fine. Kies is installed and activated modem in diag screen and toggled. I uninstalled the drivers, wiped it back to factory and reinstalled the drivers and tried to connect again, but no luck. I can also read the sd card as well. Any ideas?
Reading some more...
....in other posts similar (which have no conclusions) it appears net.cdma.configurable.mode is set to "-1" and needs to be set to "1". Anyone know how this can be done?
a little more history into this issue; it happened after an meid repair and after I rebooted tab, were it once connected....it never did again. Anyone? Any clues or have i figured out a way to permanently turn this tab into a wifi only model?

[Q] Can't get out of emergency mode (NO USB DEBUGGING MODE)

Hello all,
I have big problems with my L7 P700.
I rooted it two month ago, even that time I was stuck at yellow emergency mode, but using some instruction (disable LG modem) I was able to boot phone again.
Today I believe I have totally different problem.
What I did, I found stock firmware 4.1.2 and LG drivers, I installed it. Restarted phone and pressed Volume UP + Power. Phone went to yellow emergency mode, ok... Then I tried to use KDZ_FW_EN, phone was not seen. I restarted it and it booted ok to system. Turned of again, went to emergency mode than I opened KDZ_FW_EN again. I tried to read phone information, the program chrashed. I opened it again and tried to flash firmware. There were errors, and I am pretty sure phone wasn't even properly connected to PC!
So if you don't understand me I will repeat again.
I went to emergency mode WITHOUT USB DEBUGGING ON (I disabled it one day, I remember, this time I forget to turn it on). So Under device manager I see only USB composite device and LG Modem, disabling modem isn't a fix (like two month ago when I rooted). This time I can't use any of flashing tools cos I am not in debugging mode =(. The only thing I don't understand is how I was able to destroy my phone if it wasn't even flashing it (port number was -1, some wparam 100-1000 errors, i closed program in the middle but it wasn flashing if I wasn't in debug mode?)
Phone is rooted and stuck at emergency mode, without usb debugging and hard reset bring the emergency on (BOTH VOLUME BUTTONS + MENU)
Anyone?
Yes, I had the same problem a few months ago. Try install firmware stock V20D without battery and then connect phone via cable USB to PC but turning on Emergency Mode. Next, 3GQCT and CS EMERGENCY. Of course you can change port USB. Try reinstall KDZ and drivers. If you have Windows Vista then that's the problem. I'm sure that this situation will be resolve.
Ok I made it!
Don't know how, maybe it was working all the time. I've seen that phone is connected thru Ports (COM & LPT). Opened KDZ again, even that the install for firmware usb driver failed. I again tried to flash, again there were errors (wparam,...) and port -1?, I just left phone connected, yesterday I unplugged it! After 10minutes phone restarted and here is 4.1.2 and all the data is here!
Don't know what I was doing =)
Thread can be closed now!
Great!

[Q] Replacement device USB woes

Received a replacement device yesterday that is NG2. No big deal as I CF-Rooted it, then placed TWRP on it. Did a backup of initial state and went to transfer a rom to SD card and realized the phone would not connect
to PC as a device. Now I have 2 other S4's in the house and they connect immediately so it is not a driver issue with the computer(Win8.1), or USB cable. The 2 other S4's immediately are recognized by the computer.... I
have found that this one is recognized only while in Download mode, but when booted, nothing. I reinstalled the backup I first created and did a wipe 3x and I was able to get it to go into USB mode only 1x. The USB
icon appeared in the upper left of the screen and Kies recognized the device for the first time. After that I thought I was good so I went to the CF-Root installed Superuser app and opened it. It prompted about knox so
I ran it for knox disable. Bam, no more USB. What is going on here? I have rooted and worked with 5 or 6 different S4's with no issues. This is my first at NG2, and I want to point out that it is not activated yet as well.
Does not completing the activation trigger something? I am just trying to figure out if I should just return and swap for another. I have tried to reflash back to stock and wipe and it no longer offers the USB connection I
was able to achieve at the 1 point. This is an odd one and again, it is NOT drivers or the USB cable.....
Thanks,
Lisnup65
Fixed. Returned the phone for another one.

[Q] Soft brick: USB Device Descriptor failed

Customer probably flashed a kernel which failed. Now the phone has lost ESN (null). No download mode, no recovery. Device operates other things very well.
Interestingly it rarley shows ESN. I reboot the phone tens of times, maybe only at once of 100 boots it shows up. If it shows up, voice and mobile data works, but otherwise, you need to reboot the phone, untill you can see the ESN.
Additionaly, the same applies for USB connection. I plug the cable and it says "Unknown USB Device" maybe 499 of 500 times. Now I have been trying for two days to flash IMEI /ESN back with EFS Professional, but never managed to get rid of "unknown device" error again. Tried re-installing, using another computer, Windows 7/8 and Ubuntu. No luck. I also tried the method to manually flash memory blocks as described here. But cannot get that far.
At the time once it showed up the ESN, I managed to upgrade the phone from KitKat to Lollipop, using official LG Support Tool. So it is original stock ROM and device is unrooted. But everything is still the same. After the upgrade, original recovery works now, but it has nothing to do with the situation.
Now in device manager it says "USB Device Descriptor failed". Still no download mode. I tried to copy registry values of a working G2, but couldn't manage to make it work.
Now, any other suggestions?

ATT Galaxy S5 will not connect to computer

Hi Group... Newbie here and I am sure you will figure that out by my questions and terminology ... I am a Hardware tech specializing in Microsoldering...and Iphones at that. I just bought out another store with loads of devices I am attempting to fix and sell. I have been successful on most all of them, and now have an Att Galaxy S5 that I am getting trolled by.
It powers on (Has an unlocked padlock) while booting. but all APK's ive tried says its not rooted...
I wrote Att unlock and got approved with unlock code (Not attached to an account, not lost or stolen, clean IMEI).
I restored it using power/Home/Volume up (Padlock still unlocked)
I plugged it to computer to use ODIN to restore back to original Stock but phone will not connect to computer.
Developer mode is on and debugging checked... no drop down and not recognized by computer at all. Thinking it could be a charging / Data port (Even though it charges with computer), I swapped the logic board into another "Known Good" housing that does connect. It made 0 difference.
all other Galaxies connect just fine so Cable / USB Port / Drivers all appear okay.
Since I cannot use computer and ODIN, I wanted to try SD Card to restore original Rom... but nothing I am trying works Any ideasany
TeeTopp001 said:
Hi Group... Newbie here and I am sure you will figure that out by my questions and terminology ... I am a Hardware tech specializing in Microsoldering...and Iphones at that. I just bought out another store with loads of devices I am attempting to fix and sell. I have been successful on most all of them, and now have an Att Galaxy S5 that I am getting trolled by.
It powers on (Has an unlocked padlock) while booting. but all APK's ive tried says its not rooted...
I wrote Att unlock and got approved with unlock code (Not attached to an account, not lost or stolen, clean IMEI).
I restored it using power/Home/Volume up (Padlock still unlocked)
I plugged it to computer to use ODIN to restore back to original Stock but phone will not connect to computer.
Developer mode is on and debugging checked... no drop down and not recognized by computer at all. Thinking it could be a charging / Data port (Even though it charges with computer), I swapped the logic board into another "Known Good" housing that does connect. It made 0 difference.
all other Galaxies connect just fine so Cable / USB Port / Drivers all appear okay.
Since I cannot use computer and ODIN, I wanted to try SD Card to restore original Rom... but nothing I am trying works Any ideas???
Click to expand...
Click to collapse
install this first
https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
when you put phone in download mode that time Odin should see the phone, if its not then also change USB cable, PC
under developer option check if its listed for charging only or mtp
also on dial pad try this
type *#0808# and enable MTP.
Gave up on this one...Can close post
Thank you for your suggestion but have tried all of that. I have 7 others that connect fine...same model with same cord and same computer. Have the Drivers, tried everything under *#0808#... However, I have tried testing D+ and D- as well and all is good. Changed u7000 as well and no change. I'm pretty certain that it has to be a hardware issue so I just gave up and put it in my parts bin as I don't know Android hardware the way I know Iphones and have too many hours in it to make it worth while

Categories

Resources