Related
Hello, I'd like to request information on how to use QPST with my Kaiser via USB. QPST shows 'No Phone' on all ports and I don't seem to be able to enter diagnostic mode.
Any advice would be greatly appreciated. Thanks.
i'm running Vista if that makes a difference...
I also have a PC running XP if that helps.
Nobody will help me?
i am trying to do the same thing, i have gone as far as flashing to jockyw's spl with tty enabled. but i dont know how to put it in qpst diag mode... i am using vista, but also tried under xp, with no change.
I'm trying to do the same thing. I can get the comm ports to show up and use QPST while the phone is in the tri-color bootloader state. QXDM will also works in that state but since the phone is not runing, I get no useful information.
I have not been able to get the com ports to show up with the phone is fully booted like I can with CDMA smart phones by dialing ##DIAG#.
you can get qpst to recognize it in tri color mode? the only way i was able was to put it in download mode by issuing rtask a, and radata 90000000 1. after that i installed the motoq drivers available in the frankenkaiser pack. it shows up in qpst as download mode, but it can not mess with anything because it is in dl mode. if you know how to put it in diag mode, that would be a step for me!
I have installed the wmodem drivers and put the phone in bootloader. But qpst sees nothing. Is there a diagnostic mode similar to a CDMA phone.
does anybody know more about qpst?
So after booting into BP Tools mode, how are you supposed to know that it actually is in it?
From some sources, it says that there should be a message showing "Connected in BP Tools Mode" in the notification window. The reason I ask this is because I'm having trouble running a diagnostic tool that requires the Droid be in BP Tools mode. There isn't enough information that I can find anywhere about the BP Tools mode for a Droid Turbo so I just want to make sure that my phone has it working properly.
Anyone have any ideas?
When you start your device in BP Tools mode, you will get a new application visible in app drawer called CQA Test. If you have that in your menu, you booted the device in bp tools mode.
Semseddin said:
When you start your device in BP Tools mode, you will get a new application visible in app drawer called CQA Test. If you have that in your menu, you booted the device in bp tools mode.
Click to expand...
Click to collapse
I found out that I wasn't seeing the app since I was using a different launcher than the default one. Switched back to the default launched and found it.
Thanks!
Hi,
Am a novice when it comes to rooting, unlocking android devices. So please excuse my ignorance and my long-winded style of writing. I want the expert users to educate me on this issue and so I don't want to miss any trivial (or not so trivial) information.
1) So, I got Samsung gear live from ebay. It came with a sprat-userdebug 5.0.1. After googling I found out that it's a user/refurb build and can't be updated to 5.1.1
2) Thanks to rootjunky! I used Gear live restore tool V3 and unlocked the bootloader (option 2). Faced few issues in getting the driver. However, fixed everything and unlocked it. Flast TWRPd it (option 8). Flashed recovery (option 4) and bootimage (option 5). Then I sideloaded stock image from 4.4W.2 (using boot.img and system.img). That was the version I found after googling.
3) Then I tried to update it via OTA download. Download completed and it went back to recovery mode and did't apply the download. There was an error message that said something like "Unable to verify the download"
4) Tried multiple times and no luck with that
5) Then tried to sideload new version 5.1.1 LCA43 from xda wiki page. However, when my device went to recovery mode, my pc lost the connection and i wasn't able to sideload (received - device "null" not found" - error from adb command)
6) Until this point I was able to pair my device with my samsung S5 phone and only problem was not able to install the update
7) Then I reset my watch to factory setting, restarted multiple times, went to recovery mode to boot as a new device etc. No luck
8) Then I did something I shouldn't have done (or I think I shouldn't have done). Used option 7 root gear live. When the system went to SH mode, I panicked and closed the cmd prompt and hard reset the device by holding power button
9) After this step, I was not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N
10) Tried resetting my device, restarted it, used recovery mode to restart it, revoked all debug access, deleted adbkey from my PC, uninstalled android SDK, all drivers, etc. Reinstalled it again with no help.
11)Suddenly android wear in my phone sees my wifirouter as a device (strange)
11) When I plug in the device to my Pc, I could see it in my device manager. When I use recovery tool it says unregistered device and asking me to register it via my phone. Where as am not able to pair it with my phone. Tried to pair it with a new phone (moto e) and no help either
12)Somewhere read that disabling wifi in the phone before pairing works. Tried that and no luck
So here am with a bricked device that stays in the screen where it says "install android wear in your phone" and detects nothing else. Am able to go to bootloader mode, recovery mode from the device. However when it's in recovery mode, my PC doesn't detect it. Even the recovery tool says unregistered device.
Please help in unbricking this device and thank you for reading thru the whole problem. Any help would be much appreciated!
Use Gear live restore tool v2. Lots of known issues with v3
Thanks for the reply. I will try this. However, how will I make my device discoverable? Now, none of my phones detect my device.
So I guess I will get "Unauthorized Device" error when I use recovery tool. Could you please let me know if there's other way around? Or am i missing something?
I've never used it
Pretty sure all the info you need is in the thread
http://forum.xda-developers.com/gear-live/development/utility-gear-live-watch-tool-t2846696
No luck. Tried V2. Tool doesn't recognize my watch. It says 'Device Unauthorized. Please check the confirmation dialog on your device'. My device is stuck in 'Install Android wear on your phone' screen.
unbricked using v2 of the tool. Now trying to update the os version. Will see if I can get lucky this time. Thanks for the help!
All is good now. Now my gear live is running on 5.1.1 with latest updates.
Good work
Please can you tell what exactly you done, as I'm on the same root.. and I'm using win 10... but without any luck so far..
darwchprish said:
Please can you tell what exactly you done, as I'm on the same root.. and I'm using win 10... but without any luck so far..
Click to expand...
Click to collapse
Simple procedure.
Just download v2 of this tool
Make sure to install USB drivers
Unlock bootloader - option 2
Then use option 6 to flash it. Then you'll get new OTA updates.
Refer rootjunky video - https://www.youtube.com/watch?v=x7oRjESQh_o
I'm not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N,
and ... I tried V2 and V3. Tool but doesn't recognize my watch. It says 'Device Unauthorized. My device is stuck in 'Install Android wear on your phone' screen.
darwchprish said:
I'm not able to pair my device with my phone. Now the version says 4.4W.1 - KGW42N,
and ... I tried V2 and V3. Tool but doesn't recognize my watch. It says 'Device Unauthorized. My device is stuck in 'Install Android wear on your phone' screen.
Click to expand...
Click to collapse
Follow this procedure.
1)Make sure all drivers are installed properly in your PC
2) Make sure when you connect your device to your PC, it's discovered as unauthorized device. It's ok
3) Long press power button in the device and swipe from top left to botom right corner when you see samsung gear live logo
4)This will get the device to bootloader mode
5)Now connect the device to your PC and run V2 of the tool. Your device will be discovered in fastboot mode
6)Now select option 6 to flash the device to stock. It'll flash it
7) Now swipe down to highlight start and swipe from right to left to start. If it goes to Raw dump code = 6. do a hard restart by long pressing power button. You'll get back your device in original setting.
Check rootjunky youtube video to get the live demo of this procedure.
noviceinandroid said:
No luck. Tried V2. Tool doesn't recognize my watch. It says 'Device Unauthorized. Please check the confirmation dialog on your device'. My device is stuck in 'Install Android wear on your phone' screen.
Click to expand...
Click to collapse
How did you get past this? I'm stuck here now too.
-- update after trying that procedure again, it worked to get to fastboot mode. Now I'm doing that 'option 6' to flash it.
mike061215 said:
How did you get past this? I'm stuck here now too.
-- update after trying that procedure again, it worked to get to fastboot mode. Now I'm doing that 'option 6' to flash it.
Click to expand...
Click to collapse
Good luck.
It worked -- and I finally got the OS to update an all that and now I finally have a functional Gear Live. Phew!
My Gear Live was bricked a lot... Computer detect device as RELINK HS-USB QDLoader 9008. Has anyone any idea how fix it?
lamik91 said:
My Gear Live was bricked a lot... Computer detect device as RELINK HS-USB QDLoader 9008. Has anyone any idea how fix it?
Click to expand...
Click to collapse
sounds like USB driver issue. Please install correct drivers and follow the steps mentioned above. It should be unbricked.
Where can i find correct drivers? Additionally my Gear Live doesn't turn on and has only black screen.
I am confused on how to use the tool. My watch is stuck at the Install Android Wear App and won't do anything short of turning it off. How do I enable developer mode \ debugging without being able to get to the watch settings. Please help! Thanks
pedalquickly said:
I am confused on how to use the tool. My watch is stuck at the Install Android Wear App and won't do anything short of turning it off. How do I enable developer mode \ debugging without being able to get to the watch settings. Please help! Thanks
Click to expand...
Click to collapse
You need to factory reset first of all. After that let connect to your wifi, the updates will download on their own. They put a new one out today. I can't go into how but if you look at the forum and search the answers are there. There's even a tool to use.
Sent from my SM-N910T3 using XDA-Developers mobile app
Hi everyone,
I was wondering does anyone know the Nokia TA-1004 JTAG points by any chance?
I tried looking around and I can't seem to find anything.
Because of my bricked device, I am thinking of going down the JTAG route to extract my data.
This is the absolute last resort as I REALLY don't want to loose any of my data, primarily Contacts and Messages
Hope to hear back from you wonderful lot ?
Nokia_8_fan said:
Hi everyone,
I was wondering does anyone know the Nokia TA-1004 JTAG points by any chance?
I tried looking around and I can't seem to find anything.
Because of my bricked device, I am thinking of going down the JTAG route to extract my data.
This is the absolute last resort as I REALLY don't want to loose any of my data, primarily Contacts and Messages
Hope to hear back from you wonderful lot
Click to expand...
Click to collapse
I don't know what JTAG is. Please give some more info about your bricked device, how you bricked it etc. It might be possible to recover it without hardware intervention. Looking at your current post I am guessing you have a hard brick. In that case you have 2 options:
1.) Press and hold power button for about 2-4 minutes and wait for the device to shut down. When the device shuts down, boot to fastboot mode and fix any broken partitions.
2.) If that doesn't work you need hardware based methods. You need to open your device and short some pins to enter Qualcomm EDL (Emergency Download) mode. From there you can recover your device.
emufan4568 said:
I don't know what JTAG is. Please give some more info about your bricked device, how you bricked it etc. It might be possible to recover it without hardware intervention. Looking at your current post I am guessing you have a hard brick. In that case you have 2 options:
1.) Press and hold power button for about 2-4 minutes and wait for the device to shut down. When the device shuts down, boot to fastboot mode and fix any broken partitions.
2.) If that doesn't work you need hardware based methods. You need to open your device and short some pins to enter Qualcomm EDL (Emergency Download) mode. From there you can recover your device.
Click to expand...
Click to collapse
Thanks for getting back to me.
I have done both suggestions and they don't work.
It is probably a hard bricked device, the only thing I can get is a 9008 recognition in Device Manager.
QFIL, OST and NOST doesn't seem or want to communicate with the device either
Did you open your device and short the pins required? EDL mode is different than Download mode. OST and NOST work in Download Mode not EDL. QFIL does support EDL mode. If you look at this article (https://xiaomitools.com/how-to-use-qualcomm-flash-image-loader-tool-qfil/) at Step 5 it mentions that the device should be recognised as 9008 which you mention it does. Have you installed the Qualcomm drivers? Please provide some screenshots too, it is difficult to help you without specific info about your problem
emufan4568 said:
Did you open your device and short the pins required? EDL mode is different than Download mode. OST and NOST work in Download Mode not EDL. QFIL does support EDL mode. If you look at this article (https://xiaomitools.com/how-to-use-qualcomm-flash-image-loader-tool-qfil/) at Step 5 it mentions that the device should be recognised as 9008 which you mention it does. Have you installed the Qualcomm drivers? Please provide some screenshots too, it is difficult to help you without specific info about your problem
Click to expand...
Click to collapse
@emufan4568
Sorry for my late reply, but I thought Download Mode is the same as EDL mode???
And yes, I have the Qualcomm drivers installed.
I have also shorted the EDL pins on the board, this did not do anything at all.
I have tried QFIL many times and it keeps giving me error messages.
I have done so many things and posted screenshots across the forums that I am at a complete lost!
Nokia_8_fan said:
@emufan4568
Sorry for my late reply, but I thought Download Mode is the same as EDL mode???
And yes, I have the Qualcomm drivers installed.
I have also shorted the EDL pins on the board, this did not do anything at all.
I have tried QFIL many times and it keeps giving me error messages.
I have done so many things and posted screenshots across the forums that I am at a complete lost!
Click to expand...
Click to collapse
EDL mode is Emergency Download Mode in Qualcomm devices for recovering the device at a low level. QFIL calls it download mode but it really is not. Download mode in Nokia phones is really fastboot mode or bootloader mode where you basically communicate with the bootloader and flash/erase images from the device. From what I have seen though NOST supports EDL mode too (with the Emergency Download option) but it does not really work well.
Help me.
my device is pixel 4xl with rooted android 13 beta 3.2 .
At first I saw on the lockscreen it said "cerficate expired" and face unlock didn't work.
I thought that if I restarted it would work again, but when I restarted the device it wouldn't turn on, I've tried pressing the power button for 1 minute, it still doesn't react, it doesn't even vibrate....
please help me to find the solution....
sinagaB said:
Help me.
my device is pixel 4xl with rooted android 13 beta 3.2 .
At first I saw on the lockscreen it said "cerficate expired" and face unlock didn't work.
I thought that if I restarted it would work again, but when I restarted the device it wouldn't turn on, I've tried pressing the power button for 1 minute, it still doesn't react, it doesn't even vibrate....
please help me to find the solution....
Click to expand...
Click to collapse
Hey! You may be on EDL mode.
To exit it you have to press power button and one of the volumes buttons, though I don't remember which one. Just have a look on Google and you will find something.
As for the certificate, I saw people having that problem if they replaced the front camera or the face id module. I don't if that's your case, but as you have root you may be able to recover face id functionality.
Let me know how it goes!
#mcl said:
Hey! You may be on EDL mode.
To exit it you have to press power button and one of the volumes buttons, though I don't remember which one. Just have a look on Google and you will find something.
As for the certificate, I saw people having that problem if they replaced the front camera or the face id module. I don't if that's your case, but as you have root you may be able to recover face id functionality.
Let me know how it goes!
Click to expand...
Click to collapse
Still didn't work :"(
Connect your phone to the PC(must be running windows). The open device manager and under the ports tab, do you see "Qualcomm HS-USB Qloader 9008 (COM *a number*)? Or something similar
#mcl said:
Connect your phone to the PC(must be running windows). The open device manager and under the ports tab, do you see "Qualcomm HS-USB Qloader 9008 (COM *a number*)? Or something similar
Click to expand...
Click to collapse
Yes , same.
sinagaB said:
Yes , same.
Click to expand...
Click to collapse
Then you are on EDL mode, as when you boot in that mode, the phone change how it shows up on the PC. You need to try to get out of there. If you can't, as you said you were having issues with the OS, maybe something is broken and the phone can't boot up.
When Android starts it has 2 bootloaders (the normal bootloader and the secondary one, which has EDL mode). If the standard bootloader fails, then it uses the second one which is EDL.
So here are some suggestions:
1. Try to hold the power key + volume up key for several seconds. If it doesn't work do the same with the volume down key
2. If that doesn't work there is another method, though it's riskier and might not work. Try to open the phone and disconnect the battery, leave it disconnected for some seconds, reconnect and try to boot the phone.
If none of those things worked for you, it means you will need to flash the firmware to your phone using EDL, as the bootloader is damaged.
Unfourtynaly there is not much info on using EDL on Pixel devices, though a lot of people use EDL to unlock Xiaomi's bootloader, so maybe have a look on those forums. On my profile, I tried to use the EDL mode to unlock a Pixel bootloader(mine is carrier-locked), though had no success, you will find a lot of helpful information to solve your problem, like the tools and files you will need and some overall idea of how EDL works.
Hope those help you and let me know if I can help you further
#mcl said:
#mcl said:
Then you are on EDL mode, as when you boot in that mode, the phone change how it shows up on the PC. You need to try to get out of there. If you can't, as you said you were having issues with the OS, maybe something is broken and the phone can't boot up.
When Android starts it has 2 bootloaders (the normal bootloader and the secondary one, which has EDL mode). If the standard bootloader fails, then it uses the second one which is EDL.
So here are some suggestions:
1. Try to hold the power key + volume up key for several seconds. If it doesn't work do the same with the volume down key
2. If that doesn't work there is another method, though it's riskier and might not work. Try to open the phone and disconnect the battery, leave it disconnected for some seconds, reconnect and try to boot the phone.
If none of those things worked for you, it means you will need to flash the firmware to your phone using EDL, as the bootloader is damaged.
Unfourtynaly there is not much info on using EDL on Pixel devices, though a lot of people use EDL to unlock Xiaomi's bootloader, so maybe have a look on those forums. On my profile, I tried to use the EDL mode to unlock a Pixel bootloader(mine is carrier-locked), though had no success, you will find a lot of helpful information to solve your problem, like the tools and files you will need and some overall idea of how EDL works.
Hope those help you and let me know if I can help you further
Click to expand...
Click to collapse
Click to expand...
Click to collapse
step 1&2 didn't work ,, by the way, thank you for replying my thread ... so there's no possible way to fix this , sir? bcause i'mnot an expert to this . )