Guys and gals...
I've got a bricked X2, so things can't get any worse at present.
I took the advice which was displayed in another thread, and downloaded the Qualcomm QPST package.
x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051.html
I deleted the default comm ports in the QPST configuration tool, added both USB ports that were available, did the Volume Down + Power On keypress, connected the cable, and voila! The phone was recognised, and it was possible to browse through the phone using EFS Explorer. Using QPST Service Programming, I can view and edit a whole LOAD of stuff inside the phone. Wow.
I haven't dared change a single thing yet. I'm hoping someone can now contribute and we can begin to understand how to use this package to our advantage.
hopefully this will bring us closer to spl!!!
Great Work...
Further information
Further information...
You can configure two USB ports (called COM13 and COM15) using the QPST Configuration server.
When you do the Power On + Volume Down combination, the phone appears to enter Diagnostic mode, and shows up as being connected on COM13.
When you do the Power On + Volume Up combination, the phone appears to enter Download mode, and shows up as being connected on COM15.
I don't yet know what the significance is, or what to do about it. But again, I'm hoping that someone will be able to shed some more light on this.
I guess the main aim at this stage would be to find out how to access the WM file directories inside the phone.
Developers have disappeared in the wild
The HardSPL's project is dead and buried...
lo said:
Developers have disappeared in the wild
The HardSPL's project is dead and buried...
Click to expand...
Click to collapse
im sure it can start back now that we have this to use!
I've tried and that works.
I can backup a qcn file but I don't know what it is???
Related
I already have my samsung usb and android modem drivers installed. but everytime i plug my phone in with usb debugging on, the "Found New Hardware" window keeps popping up, why?
im not sure, but it could be the problem to why it always says "waiting for device" on superoneclick
My day job is pc tech, I have seen this a few times but going to follow the steps, first give me some info
Which version of windows?
32 or 64 bit?
How proficient are you at driver maint. *add and removeal ov drivers*
When did this start?
windows xp - 32 bit - and im pretty proficient at maintenance. i think its always been like this.
Ok, Do you always use the same USB port? and have you tried a different cable? and have you tried it on other computers? if so did it do the same thing there?
First we got to get rid of the drivers on the pc.
http://download.cnet.com/DriverMax/3000-18513_4-10572602.html
This is a free program that has a few nice features but most important is that it can tell you the name of the files that are used as drivers. After you install and register (its free, they just want to know who you are.. name, email, that kind of stuff) there will be an entry on the right side called "Installed Drivers Report". Make sure you phone is connected before you click this as it scans active drivers. it will generate a report you can scroll through and find any samsung driver entrys. Write down those file names, we will need them in a moment.
Go to device manager and remove the device there. Windows XP was kinda lame about device removal it did not actually remove the device just broke the connection. Vista and 7 give you the option to actually delete the files which make this easier. Since your on XP after the devices have all been removed UNPLUG your phone from the PC then start a search for those files in the Windows directory. Delete (or move) those files and the rerun the driver install program from here
http://forum.xda-developers.com/showthread.php?t=728929
After that it may setup and find new hardware a few times. Mine did it 3 since there are multiple different methods it can connect with and each uses differnet hardware. Also each time you use a differnt USB port it sees it as new device in a new location so it also goes through new hardware setup again.
Report back and let me know if this helped any.
okay thanks for the quick response. i will try it when I have time and ill get back to you. first, imma try it on a different computer.
also, when its plugged in and i open device manager, theres 3 yellow exclamation marks, one on the android modem, device, and in the "OTHER devices" section, the USB controllers. if that means anything.
just turn off usb debugging... and it will stop. turn it back on if you need to use it for something.
I connect my wildfire to my computer using the usb lead and set usb debugging on. Then when I try to select it from eclipse to run my program on I can select it but I can't select ok to actually make it run. It doesn't seem to recognise the phone. Any ideas how to fix this.
You may need to set up udev properly. Look around, you will find it. It should be in Android developer guide for Linux.
Yep found that and have followed it to create a new file for udev so that it can recognise my htc wildfire. The problem is that now it doesn't mount the sd card as it used to when I plug it in. Is there a more general set up I can follow that will fix this?
Would like to know as well
found a link which seems interesting. I will try to worj through it later when I get home but I think it states that I may need another line for normal mode. The catch all rule it shows is the one I have and does not recognise plugging it in normally.
not allowed to post url so will post back if it is any good.
Didn't need anything but the catch all line in the end. Restarting the phone made it all work I had obviously turned something off at some point.
Here's the problem:
Updated DVP mango using the leaked build on my own computer. Updated Dell firmware post mango on a friends computer. Now cannot connect to phone using my own computer, says phone not recognized. Tried reinstalling windows but that doesn't help. Reinstalled zune that doesn't help either. (ofcourse if windows reinstall didn't help ). Went to devmgmt.msc and reinstalled drivers from zune drivers directory but that didn't help either.
Reset my phone but no luck as it was reset to Mango when I actually bought it with Nodo.
Can anyone help please!!
http://forum.xda-developers.com/showthread.php?t=886431 does not work for me. Neither does: http://ambassadors.xbox.com/en-us/Pages/xbox-live/troubleshoot/zune-sync-devices-wizard.aspx
This is why you don't install leaked builds or beta builds.
Reboot your phone into the bootloader (hold vol - and power)
Download the WP7 Update Cab Sender from the Dev and Hacking Forums
Download the mango update cab from the Dev and Hacking Forums as well (there is a list of cabs and there is one SPECIFC to the dell venue pro)
Use the WP7 Update Cab Sender to update your phone.
Cross your fingers.
Hi,
Thanks a lot:
Forgot to mention the following: my phone was developer unlocked- (dreamspark) and operator unlocked T mobile version bought from the US.
Also: I cannot get to the bootloader mode:
Here is what I've done:
1. Not connected via usb
a. Hold vol down button and press power to start
b. Hold both vol buttons and press power to start
2. Connected via usb
Same as above a and b.
However, nothing happens and my phone still doesn't connect to my computer.
So I don't know how else to send cabs.
Just use the wireless method with zune. No need for a cable.
Sent from my GT-I5800 using XDA App
I'm getting a red text: Error: No devices were found.
I downloaded and installed the WP7 update tool before running the update cab sender batch file.
Also: my laptop is connected to the same wifi that my phone has been configured to auto-connect too.
EDIT: I've recently moved so my wifi router is different and my phone and computer are not configured to sync wirelessly over this network.
When I ran this tool, as per suggestion, it was not connected via cable.
Also, its a Dell Venue Pro that I started by keeping the Volume down button pressed and then holding the power button for a while. ( How do I know if its bootloader mode? )
I hope I'm not missing anything.
Here is what the about page of my phone says:
Dell Venue Pro
OS version: 7.1.7720.68
Firmware revision number: 2250.1800.7720.219
Hardware reivisin number: 112.576.2.0
Bootloader version: 7.27.1.0
Thanks.
Take the battery out.
Put it back in.
Hold power
and HOLD vol down
Hold these buttons untill you get to the boot loader. DO NOT RELEASE EITHER OF THEM
Hi Tried the following at least a 3 times each so not sure whats wrong: (took out battery each time and reinserted )
1.
a. Hold the power button.
b. Immediately hold the vol down button and then keep them pressed for as long as I can.
I still get the tiles.
a. Hold the vol down button first.
b. Hold the power button and keep them pressed for as long as I can.
I still get the tiles.
I also tried holding them for various stages, like releasing just after the Dell logo and just after the Windows Phone logo but neither helps.
Am I doing something very wrong here?
My bad. It is vol down, camera, power. I just tried it and it works
Where can I find specific Dell Vene Pro Cab
MJCS said:
This is why you don't install leaked builds or beta builds.
Reboot your phone into the bootloader (hold vol - and power)
Download the WP7 Update Cab Sender from the Dev and Hacking Forums
Download the mango update cab from the Dev and Hacking Forums as well (there is a list of cabs and there is one SPECIFC to the dell venue pro)
Use the WP7 Update Cab Sender to update your phone.
Cross your fingers.
Click to expand...
Click to collapse
Hi there, just wondering if you could point to the direction for the specific dell venue pro cabs ?
Just need to do the same thing as well
---------- Post added at 02:08 PM ---------- Previous post was at 01:50 PM ----------
hihi2u2 said:
Hi there, just wondering if you could point to the direction for the specific dell venue pro cabs ?
Just need to do the same thing as well
Click to expand...
Click to collapse
Also when I tried to use the cabsender, I'm getting this message as well ... ... operable program or batch file.
'llecting' is not recognised as an internal or external command,
operable program or batch file.
'/I' is not recognised as an internal or external command,
operable program or batch file.
'celog' is not recognised as an internal or external command,
etc....................
I just been given alot of the not recognised as an internal or external command ..... and ask me to 'Press any keys to continue' ... how do I get this working ?
I've basically bricked my phone by hot swapping a SD card without backup so I've got a bricked phone now ... ... just need to reflash it in someways and was hoping this would work ... ...
List of cabs:
http://forum.xda-developers.com/showthread.php?t=1306415
Thanks so now I do enter a bootloader mode, or what I think is the bootloader mode (a black screen with WP, usb cable and a laptop computer)
I fire up update sender and press S but it says cab not found.
I couldn't understand what is meant by 'Just use the wireless method in Zune'. Can someone please elaborate.
I tried to connect it to computer via usb and this happens: Unlike earlier when I used to get unknown device, I get a Windows mobile searching for drivers and then it says 'device unplugged'.
And S in update sender still doesn't work saying that no devices were found.
Any suggestions please?
There is no wireless method that would fix what you want. The wireless method is for syncing videos, photos, and music.
So can someone suggest what to do to be able to connect my phone to my computer and get future updates?
Fix: Dell Venue Pro device not recognised in windows
i bought 10 DVPs and 8 of them updated fine to mango. the other 2 wouldn't connect properly to windows. the device manager showed 4 unknown devices, following all the MS troubleshooting steps achieved nothing.
big thanks to a guy called Steven who found that the devices had been left in the incorrect USB mode by the Dell engineers back at the factory. by default they should all be in Zune mode, but these 2 weren't.
the solution is to start the EM diagnostic app on the phone, dial ##634#
then you get a photo of a dog and the "EM" screen comes up.
you get 3 menus at the top of the screen. "Phone Information", "System Information", "MMS Settings". to reveal additional menus, press each of the number keys along the top of the keyboard, 1234567890 in that order. this may take a few goes to get right so keep trying, it should eventually work, try sliding the keyboard up and down, seems fairly random to get it to work.
then scroll down to "Service Center". Switch to Zune mode. you should be good to go then, plug in to a PC and sync with Zune. when i tried this Zune failed to find an update complaining that it couldn't connect to the update service. so i set up a wireless sync with the device, and then plugged it back in and tried the zune update again, and it worked.
The situation is this: Friend got a Droid Razr M, and I went and rooted it. I have learned that it's impossible pretty much to unlock the bootloader since his was built May 24th and has the most current OTA update.
What he would like to have is the phone on the Straight Talk Network. He would also like a custom recovery and ROM. I'm a little lost on this phone and have spent 3 hours reading at least on the forum between last night and this afternoon. Is it possible someone could give me some pointers?
DanRyan85 said:
The situation is this: Friend got a Droid Razr M, and I went and rooted it. I have learned that it's impossible pretty much to unlock the bootloader since his was built May 24th and has the most current OTA update.
What he would like to have is the phone on the Straight Talk Network. He would also like a custom recovery and ROM. I'm a little lost on this phone and have spent 3 hours reading at least on the forum between last night and this afternoon. Is it possible someone could give me some pointers?
Click to expand...
Click to collapse
GSM unlock http://forum.xda-developers.com/showthread.php?p=38485323
Custom recovery for locked device is safe strap...http://blog.hash-of-codes.com/downloads/safestrap/
how tohttp://blog.hash-of-codes.com/how-to-safestrap/
As far as ROMs for safe strap I don't believe there are many at all... but IMO debloated stock works its what I use even being unlocked just a little theming here n there n its good to go... hope this helps...
Sent from my XT907 using xda app-developers app
ezknives said:
GSM unlock http://forum.xda-developers.com/showthread.php?p=38485323
Custom recovery for locked device is safe strap...http://blog.hash-of-codes.com/downloads/safestrap/
how tohttp://blog.hash-of-codes.com/how-to-safestrap/
As far as ROMs for safe strap I don't believe there are many at all... but IMO debloated stock works its what I use even being unlocked just a little theming here n there n its good to go... hope this helps...
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
I prefer using the NV Item method with CDMA NV-Items Reader Writer, offered free from CDMA-Ware.
(Credits for this go to tehjolly81 for his PagePlus guide to connect phone)
1) With the phone off, do the three-finger salute (hold Volume Up and Down and Power to boot) and boot into BP Tools mode (looks just like normal boot).
2) Now connect phone to PC via USB cable. If you are on Win7 x64 like me, Windows should find 4 new devices but won't have the drivers to install any of them. If prompted to install anything by Windows, (i.e., Add New Hardware Wizard, etc) cancel out of it.
3) Click 'Start' -> right click on 'Computer' and choose 'Properties'. Click on 'Device Manager' on the left. Here you should see 4 items from the phone that are missing a driver (they will have a yellow question mark next to them).
4) One of the items with a question mark should be labeled something similar to "QC Interface" (NOT the NMEA interface). Right click on it and choose Update Driver Software. Now choose Browse my computer for driver software -> Let me pick from a list of device drivers on my computer -> Show all devices -> Motorola -> Motorola QC Diag Port. Finish running through the wizard and it should install the correct driver. After installed, it should show the COM Port # that the diagnostic interface is installed on under the "Ports (COM & LPT)" section of Device Manager.
After getting the QC Interface and getting a com port, just download the free NV-Items reader writer from Here.
Unrar the exe and run it;
1: Select the com port of your phone and hit connect
2: Press read at the top, bottom should say this: Log message: > SPC is correct. Phone unlocked
3: In Range (Dec): put 8322 in the left box 8323 in the right box and hit read; it will prompt to save as a text file.
4: Open the file and change the first 01 to 00 under the 8322 section DO NOT MODIFY 8323. Save the changes.
5: Tap Write and select the saved text file, it should show Writing NV-items from a file: Done at the bottom.
6: Tap Mode > Reset then tap Disconnect and close the program, GSM should work fine after that.
I find this method easier and less dangerous than the Radiocomm method.
This is *IF* you want to use Straight Talk's GSM BYOP, they DO offer CDMA BYOP now, which then should just activate like a normal Verizon phone after you buy their network code and activate the MEID with them.
So, Guys. Myself thought of writing this thread so that you can prevent yourselves from entering into danger as well as get rid of it even if you enter by mistake.
As you all know that, we are currently facing an issue of SIM offline, myself got into the trouble (as per me, when i insert a sim in sim 1, device recognizes the network provider but there is no signal. sim 2 is fine) and inorder to rectify that issue, i tried all possible ways like deleting IMEI and rewriting it, changing modem etc.
But nothing worked and so thought of using NOKIA CARE SUIT (NCS) >> Product Support Tool For Store 5
& change the firmware to Nokia X2DS RM-1013 059V782 v2.1.0.13 which was the biggest mistake which i ever committed and it resulted in hard brick.
I suggest everyone not to flash 2.1.0.13 version please
In my case, i was not even able to use the volume buttons and power button inorder to get to bootloader or custom recovery. Trust me, i'm not a noob but i do know the situation in which i'm and searched everywhere and took help of lots of guys and finally found the solution to it.
Just follow these steps:
A. Requirements:
1. Nokia Firmware - Thanks to Firmware27
2. QPST_2.7.422
3. QDLoader HS-USB Driver
B. Procedure:
1. Extract Requirement - 1, 2, 3 separately.
2. Now Install requirement - 2 & in Requirement - 3, just install Setup
3. Now connect USB to NOKIA X2 & Laptop/PC
4. Click on the start menu and type QFIL in search box and open it.
5. Under "SELECT PROGRAMMER", click on the browse button and
select "rm1013_2.1.0.13_user_prog_emmc_firehose_8x10. mbn" from the Requirement - 1
6. Under "DOWLOAD", you will find "LOAD XML" and now click on that and a window will appear infront you :silly:
7. Now in the window, type *.xml in the file name so that the xml files will show up.
8. Now select "rm1013_2.1.0.12_059V787_001_rawprogram_unsparse_ui"
9. Soon another window will show up automatically and now type *.xml in the file name so that the xml files will show up.
10. Now select "P12026702dpi600_label_layout"
11. Now Click on the "DOWNLOAD" just button below the Load XML button.
- Make sure your device is connected to the PC/lappy through cable :silly:
Everything is done. Now sit back and Relax.
Your NOKIA X2 will bootup and it looks exactly like device when you purchased except the scratches and all
Note:
I'm not responsible if your device is bricked. Ofcourse if you are doing this, it means that your device might have already been bricked and i guess there is no other way except this to make it right
This works with all the snapdragon chipset devices.
my phone just showing QHSUSB_BULK but it get warning mode, after i install that files it get qloader 9008
but when i download with qspt it get on sahara cannot working
frnsl3 said:
my phone just showing QHSUSB_BULK but it get warning mode, after i install that files it get qloader 9008
but when i download with qspt it get on sahara cannot working
Click to expand...
Click to collapse
The only prob is OS which you are using and Drivers..
Thx, its helped me
Dear,
I am also having the same issue and tried ur method . But I am not able to install the last set up u provided under 2. QPST_2.7.422. it says as "The following package files could not be found:
C:\Users\AMR\Downloads\BallardAppCraftery.CraftyFileViewer_epyrqhfctk40t!App\2. QPST_2.7.422\vcredist_x86\vcredist_x86."exe subsequently the QFIL is not downloading the .xml content. A help would be greatly appreciated.
Kuttappan555 said:
Dear,
I am also having the same issue and tried ur method . But I am not able to install the last set up u provided under 2. QPST_2.7.422. it says as "The following package files could not be found:
C:\Users\AMR\Downloads\BallardAppCraftery.CraftyFileViewer_epyrqhfctk40t!App\2. QPST_2.7.422\vcredist_x86\vcredist_x86."exe subsequently the QFIL is not downloading the .xml content. A help would be greatly appreciated.
Click to expand...
Click to collapse
if you are saying that you cannot download from the link i provided.....i just checked it. Itz working fine. i saved it in my g-drive and shared the link
Hi, I tried this and everything worked fine but phone didn't boot up. I mean the flashing worked but phone did not reboot. Screenshot attached. Do you know what is missing?
Is this method still working?
Hard Bricked
Still Working??
Can someone re-upload these files or point to the right direction?