Develop Bugs

QPST Connection problem.

I cannot connect to QPST and don't understand why. This is the error message I get every time I try, I have searched Google and XDA for a solution. Perhaps I am retarded, I don't know. Advise?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ANYONE????

Somebody please help!!!

I don't know how many people actually know about QPST I sure don't know enough to help. Sorry. Free bump.
Sent from my PC36100 using XDA App

I have been trying to connect my Samsung Admire to qpst for awhile and no luck. I have tried every suggestion on every forum I have found to date. Such as, pull the SD, put the phone in recovery, change the Baud rate, change the port #, use xp not W7, I downloaded every Samsung driver that worked and tried different versions of qpst. Is there not one QPST genius that can direct this noob in the right direction. Thx

For the Samsung,
Sometimes recovery mode helps, but also make sure you are using the stock rom (not aosp or CM). While QPST and others like it access the memory and firmware, the rom actually supplies the conduit. Recovery mode sometimes let's you get around some issues, but the work is still being done by the rom.
Also, while I'm not sure about Samsung, on LG phones you sometimes need LG's version of QPST, called LGnpst Lab in order to access some functions. Samsung may need similar, but I have also heard Samsungs are a bit of a pain at times.
For the OP, I know it's old but in case anyone else comes across this thread again...
Make sure the phone shows up in device manager, for HTC you need to use the HTC diagnostic drivers. If it's there, then you meed to make sure no programs are holding on to the port. CDMA Workshop or DFS, or something else may be holding the port open, the program may have been closed but didn't completely shut down or let go of the port.

Thanks Leslie I have been working on this for awhile now and I've never run across a Samsung version of QPST, I'll look harder.
And as for the stock rom replacement I have tried that twice and of course no luck but again I will try a third time.
My phone does show up in the device manager several different places and I don't have CDMA Workshop or DFS on my computer is there a way to check if some other program might be holding the port. Or should I just reboot my computer then start over? That sounds like a rhetorical question sorry.
Thanks for your help

Well I restored it back to stock, hooked it up to my XP computer and rebooted the computer. It showed up as diagnostic com4 in QPST where it had only showed COM4/unknown in W7.
I'm wondering if Link2sd may have something to do with it since it has two primary partitions. Now that I have put it back stock there is no room to rewrite the script on the second partition so that the phone recognizes the linked apps.
Should I uninstall link2sd and delete the newer partition putting everything back to normal? Or can I just unlink the apps that are linked to the newer partition and restore them to the phones internal memory?
What a freaking nightmare!! I guess I'm just to stubborn to stop trying to get this working thanks in advance to anyone who can help.
Oh and I searched for a Samsung version of QPST but found nothing.

I said there could be a Samsung version, not that there is.
Win7 has driver issues with some of this stuff and so do aftermarket roms, your problem was probably one or both.
If you are seeing a diagnostic port you are halfway there, QPST should see it now. Since it does, you are fine, don't mess with the phone or Win7, just do what you need on the XP computer. I'm sure there is soemthing you can delete on the phone to find room (boot animation, alternate languages, old version of Market, live wallpapers, etc..).
Honestly, if you are doing what I suspect, this is only the first of many similar hurdles you will face. You will have to be stubborn to get through it.

I'm having this same exact issue! I cannot figure it out for the life of me.
Using the EVO 4g with stock Rom, simple root, and amon ra recovery. When I update the drivers on my Vista laptop it says I already have the most up to date drivers.
It's killing me. If anyone can help or steer me in the right direction, that would be so awesome.
Thanks
---------- Post added at 05:50 PM ---------- Previous post was at 05:14 PM ----------
answered my own question with some thorough searching. simple fix, copied the drivers to my driver file, uninstalled in device manager and re-installed and now its showing up and the port is createble!

EVO on life support

Dear XDA Community,
This post will be as detailed as possible for those who enjoy detail.
It’s about the problems my EVO has been experiencing over the past 3 months and, after trying to fix the problems though IRC it seems that the attention should be brought to the forums for a larger audience. It was 3 months ago when I flashed a rom ( cannot remember the rom ) and my EVO took a turn for the worst.
What Happened :
When the rom was flashed and booted for the first time everything seemed normal but, the rom started to freeze at random. At first I though it was a normal process due to new ROM’s installs but, it kept repeating it over and over until it went into a boot loop syndrome.
Prior to these problems I did my daily clean/wipe dalvik rituals for ROM consumptions.​
After 15 - 30 boot-loops my battery dies and the crusade begins.
I begin looking for another ROM to flash, to rid the sickness the previous ROM infected my EVO with. I installed my favorite (SalvageMod) and, the problems began to show. Salvage installed perfectly fine (as always) but, my phone started to lag, the speed was reduced to about 35 - 50%. It’s noticeable big time. The camera stopped working and everything seemed to be falling apart.
(RECENT)In panic I started looking for ways to RUU so I can avoid any other problems. This is when I noticed that usb was not accessible. I couldn’t mount my device; [CLICK HERE FOR VIDEO], so I used a SD card reader to RUU my phone and get it back to stock.
Phone is back on stock settings but, no root and, without usb support revolutionary.io is lightyears ahead of my time.


Problems :
Not mountable through usb cable [SD Card Reader option / Software Error]
System lag noticeable slower (BestBuy rep even confirmed its unresponsiveness)
Device will not charge when on [Either mount / Software Error],
Camera problems.
[Click Here For Second Video]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So can you guys help a member get his EVO back in business, my wallet would greatly appreciate it.
Thanks,
samthewildone
Aspiring Mathematician

​

Well, the easy way out is that now that you're back on stock and a rep has agreed the phone is not working properly and you have no USB, trade it in

I would right click on that device and uninstall the drivers. then hook the phone up to the PC and see if it automatically installs the correct drivers or find better drivers.
This may have been covered, and it looks like there's a lot more going on then just drive issues, but to get this phone into a state in which you can root it and wipe it again, you need to eliminate that variable.
Not saying that the USB drivers are even an issue, but its something worth exploring first and foremost.

Tried that, as in my thread. I uninstalled and reinstalled drivers and, it just keeps showing what that picture shows above. The phone isn't damaged but, the software is borked due to a bad bad kernel or ROM flash.

Not a solution to your problem, but if you are still s-off then you don't need Revolutionary. You can put a PC36IMG of a (reliable, ie Amon Ra) recovery on your SD card. From there you can wipe thoroughly and try flashing something else.
Unfortunately it seems like some sort of hardware failure, so the only fix could be getting a replacement.
Supersonic Evo 4G | MIUI | Tapatalk

Seems like you've gone through the same steps I would've gone through to fix it. Apart from the possible driver issue the phone should still charge when plugged into a wall charger. The fact that it doesn't, in tandem with the inability to access USB via computer, tells me that most likely you've got a hardware failure. Take it to Sprint and get a replacement. Problem solved.

Bricked LG G3 - Need help!

Hi guys, I recently decided that i would root my phone and try and install cyanogenmod (new to me) as my phone seemed quite sluggish with LG's own bloatware on it. I followed the steps from LGG3ROOT and everything seemed to work well, and at the last stage when it asked me to then remove my battery and restart the phone... the phone just stayed on the lg page - never logging into the android system.
Ive tried to plug the device into multiple machines and each time the machines have issues with the device and it says the device has issue starting (10).
Im not really sure what else i can do as the phone seems bricked. Any help would be very much appreciated as i need access to the phone and i assume the warranty is now void.
Thanks in advance.

Walshinho said:
Hi guys, I recently decided that i would root my phone and try and install cyanogenmod (new to me) as my phone seemed quite sluggish with LG's own bloatware on it. I followed the steps from LGG3ROOT and everything seemed to work well, and at the last stage when it asked me to then remove my battery and restart the phone... the phone just stayed on the lg page - never logging into the android system.
Ive tried to plug the device into multiple machines and each time the machines have issues with the device and it says the device has issue starting (10).
Im not really sure what else i can do as the phone seems bricked. Any help would be very much appreciated as i need access to the phone and i assume the warranty is now void.
Thanks in advance.
Click to expand...
Click to collapse
can you post
the guide that you used to root
your phone variant
and whether it boots into download mode
what firmware version you were running

the guide i followed was this (exactly) http://highonandroid.com/android-smartphones/how-to-root-lg-g-flex-2-g2-g3-on-lollipop/
i have a UK D855
I can get it to download mode (but cant get to recovery with the power and down buttons)
unsure exactly which firmware, i hadn't played around with the phone until this happened.
when i let the phone get stuck on the lg page the windows pc seems to recognise the device, if i put it in download mode it comes up with the device error that it is there but cannot be run.
Thanks.

You probably have either
1) A bad usb cable
2) Or your drivers arent properly installed
You are plugging it into a USB2.0 port right?

I installed the drivers from the universal LG driver tool from their site, it worked find with the phone (or so it showed) before this issue, i've also tried a different cable and a different machine for it to come up with that same driver problem (10). Ive also tried uninstalling the driver software and reinstalling, is there a way to get rid of all traces of the bad drivers? thanks again for replying

Error Image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Working Fine
This is when the device isn't put into download mode and instead is left to try and boot (where it is stuck on the LG 'life's good' page).

Any idea guys? Im having no luck with any info im getting online at the moment and i'm really in need of this phone to work.
Thanks in advance.

Can you expand the "android device" section.
See if it's android adb

sorry, i think i quite understand. Which part should i expand on?
Thanks

In
device manager, look up Android device.

Update
The phone will now only go straight to firmware update and will never go or show the download mode as it has before. This is causing my LG Flash Tool to come up with 'cant change to download mode' and im not sure why or how this has happened.

The phone is now appearing fine on the device list. Its just the last of download mode. Is there a way to force it in cmd?

Please some screenshot again. The one I linked would be fine for adb

I see you can boot on download mode, so you can restore your G3 by applying a kdz firmware with flashtool2014: http://forum.xda-developers.com/showthread.php?t=2785089
On download mode the G3 is recognized only in ports (com&lpt)

What's the Expected Level of Support from Google Support?

TL;DR: Really three questions
What kind of effort can/should we expect from Google Support?
Is there an escalation support path for real troubleshooting?
What's the best course of action to attempt to determine root cause?
The Setup
While driving to work this morning my stock Pixel 2 XL (locked, not rooted etc.) entered a boot loop then settled on this error (image):
Code:
Android Recovery
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device
I couldn't do much since I was driving but I selected 'Try again' a number of times when traffic stopped before giving up.
When I arrived at work I continued fiddling with it for a few hours, select 'Try again', power off, power on, fastboot etc.
Although debugging was enabled prior, could only see a device in fastboot or when in adb sideload mode.
When I attempted to go into recovery mode it would just take me back to the same screen.
I just assumed I'd have to wipe and start over
About 2 hours ago I was getting ready to factory reset/wipe the phone but thought I'd try fidgeting once more like I had been doing all day.
I don't know what I did but it booted to a screen displaying this error:
Code:
No valid operating system could be found.
The device will not boot.
Visit this link on another device
g.co/ABH
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then the phone turned off.
I turned it back on, and I don't think I did anything differently, and suddenly it booted normally.
The only unusual thing I saw was a notification stating that Android was finishing up system updates - or something to that effect.
With the phone up, I backed up what little data had not yet been backed up, booted into safe mode then booted back into normal mode.
So far so good...?
My Complaint
I contacted Google support earlier in the day and the experience was just sad.
The person said that I would need to factory reset my phone.
But then quickly said that before doing so I would need to backup my data.
So I asked "How?" and they said "plug it into your machine and you can see it on your computer"
I went along with their script, specifically asking for detailed step by step instructions on what to do, how to do it and what to look for.
When I said it didn't work they said I would have to take it to a repair center first to get it repaired then once fixed I could back it up then perform the factory reset.
*smh*
Later, about 2.5 hours ago now, once the phone came back up, I backed up what little data needed backing up and contacted support a second time.
This time, the person said: "Now, if we need to restart the phone and check if the boot looping is triggered or not. If it does, then we need to do some troubleshooting steps here."
So I naturally asked "What are the troubleshooting steps if it enters into that state again?" but they couldn't provide any.
I just want to know root cause. Since this was an OS boot problem, surely there's a log somewhere that might reveal what happened or at the very least provide a clue. Right?

It's this phone still recoverable… without sending it to 3rd parties?

this is my pop's phone, he said he forgot how he got here, but…
here it is, nothing really works. cannot boot to android or recovery, cannot even see the bios(?) logo.
booting to bootloader is fine, but somehow it's like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the BL and Baseband are both N/A.
tried these methods:
fastboot update system.zip
return "FAILED (remote: flash write failure)"
fastboot flash bootloader bootloader.img
return "FAILED (remote: Verify bootloader image failed on production device.)"
fastboot boot twrp.img
return "FAILED (status read failed (No such device))"
any ideas?

It's probably nuked some partitions on the UFS chip, judging by the "no such device" error. Your best bet is desoldering that UFS chip and repartitioning it.

Its the 128GB model with the Toshiba chipset. These chipsets are notorious for dying out of the blue. Most likely the chip is dead. As the user above says it nuked a partition, this seems wrong because even if the whole chip was written over with zeroes, the BL would still be able to be identified. This is the chipsets job to identify the BL version. My suggestion is to get a RMA for a new one and see if its possible that you can refuse the 128 gb model. These models are completely unstable and Google should be ashamed of it.

djared704 said:
Its the 128GB model with the Toshiba chipset. These chipsets are notorious for dying out of the blue. Most likely the chip is dead. As the user above says it nuked a partition, this seems wrong because even if the whole chip was written over with zeroes, the BL would still be able to be identified. This is the chipsets job to identify the BL version. My suggestion is to get a RMA for a new one and see if its possible that you can refuse the 128 gb model. These models are completely unstable and Google should be ashamed of it.
Click to expand...
Click to collapse
RMA?

Homeboy76 said:
RMA?
Click to expand...
Click to collapse
I have one last resort solution. This seems very mis-typical as I don't see it working. Keep pressing "Reboot bootloader" until you see at least a "Baseband = (Code)" It could be hundreds of times. If you dont see it after constantly rebooting, try to keep booting the stock recovery. Over and over. I just dealt with a user that had a 32gb pixel with a issue like yours, except he had a valid baseband code. If this doesnt work you may have to go to the shop and get it fixed or RMA.

djared704 said:
I have one last resort solution. This seems very mis-typical as I don't see it working. Keep pressing "Reboot bootloader" until you see at least a "Baseband = (Code)" It could be hundreds of times. If you dont see it after constantly rebooting, try to keep booting the stock recovery. Over and over. I just dealt with a user that had a 32gb pixel with a issue like yours, except he had a valid baseband code. If this doesnt work you may have to go to the shop and get it fixed or RMA.
Click to expand...
Click to collapse
thanks for the replies... somehow i didn't receive notifications about the replies, i thought i didn't get any reply
i actually tried rebooting so many times, and nothing changed. so i just got him a new phone, problem solved.