I tried everything but no success yet to find my s22 U as diag mode on the win device manager
Tried via Adb
Tried via *#0808#
Tried via Terminal emulator
Rooter via Magisk
Any help?
Thanks
Samsung Android ADB Interface. It shows the correct device when you install the drivers. First he Diagnostics menu is on the phone, you don't need to plug it into your PC.
Dial *#0*# for one of the menus.
Try *#9090#
Also google "S22 DIALER CODES".
Download the Official Samsung Mobile USB drivers from the samsung site in order to get your device to show up in device manager in Windows, BTW.
g2g if I don't want to get slapped by my old lady for being on the puter again.
...
?!!
perfectswanson said:
Samsung Android ADB Interface. It shows the correct device when you install the drivers. First he Diagnostics menu is on the phone, you don't need to plug it into your PC.
Dial *#0*# for one of the menus.
Try *#9090#
Also google "S22 DIALER CODES".
Download the Official Samsung Mobile USB drivers from the samsung site in order to get your device to show up in device manager in Windows, BTW.
g2g if I don't want to get slapped by my old lady for being on the puter again.
...
?!!
Click to expand...
Click to collapse
Yea i went through the Dm+Modem+Adb option by *#0808# but does not show on device manager as Diag.
i have the samsung drivers from their site
Yeah, cause it's not going to. Read my post.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
For Service Mode,
DIAL:
*#27663368378#
Also Check this out:
perfectswanson said:
Yeah, cause it's not going to. Read my post.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
Diagnostics menu is on the phone, you don't need to plug it into your PC.
For Service Mode,
DIAL:
*#27663368378#
Also Check this out:
Click to expand...
Click to collapse
Nothing changed.
It doesn't change the device in device manager when you change the USB mode. It always says the same thing, only time the device changes in device manager, is when it's in fastboot mode, Download Mode, or EDL mode. You can change the usb settings back and forth and it will not change the device in windows. I think we're talking about different things. Try Holding Vol+ While plugging in the phone to the computer, while the phone is off, AND without touching the side-key or power button. But I think that is just High Verbosity logging. Just out of curiosity, what are you trying to accomplish?
All guides i saw show the phone as Diag on the win device manager...
I lost my imei. You have replied my other post asking about the phone is Sm-s908e.
I'm trying to backup Qcn so i can rewrite imei
Following this guide https://www.hovatek.com/forum/thread-26051.html
But not success to put the phone on Diag mode to be recognized on Qfil
Now I'm trying to flash original rom to see any change
Thanks for the help
I have managed to put the phone on diag mode using Adb.
There was a diferent code on Adb
I was using: "
Code:
setprop sys.usb.config diag,adb
"
And the code that managed to put the s22U into diag is: "
Code:
setprop sys.usb.config rndis,diag,adb
"
(Thx to this This thread)
Now that i have access to my Qcn file it looks corrupted (Or encrypted) comparing to a generic Qcn that i found here on the forum
looking what i can accomplish
Related
anyone can tell me hwo to enter diag mode?
I wanna use qxdm to monitor the radio protocol .thank u very much!
You need the QC diag drivers installed just do a search under mtty just rtask b then you will be prompted to install drivers it installs three devices ,one of them is the ZTE Diagnostics Interface 6000 CDMA , you connect qxdm or qpst via a com port.
I also want to know, but still can not understand what's meknb said,
Can explain more detail how to do.
ex: where to get drivers, what's mtty? Thanks
I had know how to use mtty, and also install the diag driver.
but while i reboot the phone, the diag interface also can not appear.
It only can appear while in bootloader mode(3 color display mode)
So how to let the diag also can appear while in normal mode, and use QXDM to take a log, since i want to catch some call log or data throughtput log.
Thanks.
Don't think you can do that it's either diag mode,normal or download mode.If you put the phone in diag mode in qpst you can use the efs file explorer to download the call and data log i think.
I have a Tab 2 7.0, and I have my IMEI Erased.
Tried every method found in the forums but no luck.
I found that QPST or NV_write method can get my IMEI back but I am unable to connect my tab to PC
when I switch my mode to modem from PDA in *#7284# and connect to my PC
My PC detects its as 7cds + comneon Suspend and failed to install the drivers.
I've Kies installed but no luck
Switched USB port but result is same
switched PC but same
tried my friend's tab (same like mine) with settings USB->Modem to see weather there is problem with my USB but again no drivers.... i. e. no probs with my tab
Tried This method
You need to swith UART and USB settings:
enter UART mode with *#9090# and select "Log via UART"
then
enter *#7284# and select "UART MODEM" and select "USB PDA".
Now Windows ask normal samsung drivers!
Click to expand...
Click to collapse
but i don't have the "log via UART" instide I have "log via USB" which upon selecting gives me an error ""LOG PATH SET FAIL".
and then on selecting Modem on Diag menu gives me the same responce...
note: I dont have the DM+MODEM+ADB but only modem or PDA option... I guess it said to be "mux menu" for us.. correct me if I am wrong
Please Help me...
akshayjoshi1993 said:
I have a Tab 2 7.0, and I have my IMEI Erased.
Tried every method found in the forums but no luck.
I found that QPST or NV_write method can get my IMEI back but I am unable to connect my tab to PC
when I switch my mode to modem from PDA in *#7284# and connect to my PC
My PC detects its as 7cds + comneon Suspend and failed to install the drivers.
I've Kies installed but no luck
Switched USB port but result is same
switched PC but same
tried my friend's tab (same like mine) with settings USB->Modem to see weather there is problem with my USB but again no drivers.... i. e. no probs with my tab
Tried This method
but i don't have the "log via UART" instide I have "log via USB" which upon selecting gives me an error ""LOG PATH SET FAIL".
and then on selecting Modem on Diag menu gives me the same responce...
note: I dont have the DM+MODEM+ADB but only modem or PDA option... I guess it said to be "mux menu" for us.. correct me if I am wrong
Please Help me...
Click to expand...
Click to collapse
anyone???
Hi,
I have a very unknown phone from China, the Yusun W808 It is based on a qualcomm MSM8225q chipset. I ordered it from FastCardTech and asked for a Pre-root when I placed the order.
Upon receiving I found out that the phone was not rooted... They only put some instructions on a piece of paper inside the box.
I followed the instructions but as expected, no results...
The instructions
1. Please open usb debugging and connect to your pc.
2. Download USB driver ( Snappea ) and install to your pc, when the phone is recognized, please turn snappea off.
3. Go to task manager and kill wandoujia helper process.
4. Extract root tool to your pc ( The known motochopper tool from djrbliss ) and click run.bat, then press enter on your keyboard, and just wait about 1 min, it will remind you to press enter again and then it shuts down and auto reboot. Meanwhile do not touch anything on your phone or pc or the phone will get bricked.
5.Check menu- if there is a # icon, if yes, it's rooted, or do it again.
The problem is that my phone can't be recognized by my pc. snappea says " cannot get phone stats" and motoshopper wont go further than "Daemon started successfully"
So my first thought is that the problem lies with the usb driver. I have no idea how I can get the right USB driver for this phone
Does someone has any idea how I can continue my quest here?
Thanks in advance
Yusun W808 = iNobel N1 = Ai Nuobei N1
Parameters
I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.
Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.
As the title says.
I'm trying to unlock the bootloader on my XZs so I can root it.
My device is listed normally when turned on w/ the command window, but in fastboot mode it disappears and when I try a command, an error comes up saying ""error: no device/emulator found". (see attached image)
As far as I'm concerned, I have all the necessary drivers, I've tried on another PC, the result is always the same.
And when I try to change the drivers (Via Device Manager>Update Driver>Browse My Computer...>Let me pick...>Have Disk...)
I get yet another error saying "The folder you specified doesn't contain a compatible software driver for your device..."
Can someone please give me a solution. This has been asked before on XDA by someone else (that thread has no replies). It seems it's always us little guys with actual problems which need solving who get little to no help at all here.
Reinstall driver again.
It doesn't work. The problem is I want to install the Google USB drivers for my Xperia phone but Windows 10 will not let me and driver signing seems to be impossible to disable (currently typing this on my laptop while it's in test mode).
1. Turn off your phone. Boot in to fastboot mode and plug the cable. After your heard the sound from the computer for new device found. Go to device manager look to usb S1 device. Reinstall driver by manual choose (do not search) from the menu with the name is Android Google. When prompt for install. Choose install anyway. After successful install driver, please check status from flashtool to make sure your device show connected in fastboot.
2. Change the usb port. Sometimes you get problem with usb port 2.0 and 3.0
Hope you can fix it asap.
Nothing by the name of 'Android Google' appears in the menu when selecting new drivers.
I clicked on 'S1boot Fastboot' under 'other devices' in Device Manager and clicked on update driver
>Browse Computer
>Let me pick
- and then there's something similar called 'Android Device' but no 'Android Google' so I click on that
- then I get three options:
Android ADB Interface Version 11.0.0.0
Android Bootloader Interface Version 11.0.0.0
Android Composite ADB Interface Version 11.0.0.0
None of them worked when I tried.
I think the solution is to have the phone on, with USB debugging enabled, connect via USB to PC, test your adb devices again, if all good, go ahead and
Rich (BB code):
adb reboot fastboot
This is because some phones use Fastbootd (notice the d..).