Database Users

Ambitious : Try to hard debrick with an homemade JTAG LPT cable

Hello !
i'm from an engenering school in France,
i've 2 x8, one old, rooted, boot loader unlocked, nAa kernel and CM7, and the other hard bricked because of 11w34 -__-
So i want to connect my dead phone with a JTAG LPT cable homemade.
I've seen this thread here , the shematics of the X8, the reference manual of ARM1136 (msm7227 qualcomm)
so i know the JTAG pinout, i connect them, i connect the battery with other wires, and with the software H-jtag i tried to connect my phone hoping to enter in debug mod :
i can't configure the target as ARM1136 because there is a message error : "unable to load the driver"
i've read in the reference manual that ARM926 is still compatible, so i choose this one as target device and it seems to be working (i can see READY in the corner of the window )
but when i try to communicate with the phone, a new message say that it's impossible to enter in debug mod : check TDI clock and TAP config :
i put TDI clock at low level (i tried all levels )
and for the TAP configuration : i've read in the reference manual the register adress for bypass, i try something but i'm not sure to understant TAP num : is this the binairy adress of the bypass port ? there a screen, but not with my values
{
"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 is there someone who know how can i configurate the target access port connexion ?

Good luck with this dude...and report if you make it to work
sent from my ice cream

I would normally move the thread to Q&A but JTAG is an issue that has not been covered much, so it kind of fits here too.
Unfortunately I can't help you but it would be really helpful to inform us of your progress and hopefully make a guide eventually.
Thanks!
iR¡[email protected]!* via Tapatalk 2

tilakpil said:
Hello !
i'm from an engenering school in France,
i've 2 x8, one old, rooted, boot loader unlocked, nAa kernel and CM7, and the other hard bricked because of 11w34 -__-
So i want to connect my dead phone with a JTAG LPT cable homemade.
I've seen this thread here , the shematics of the X8, the reference manual of ARM1136 (msm7227 qualcomm)
so i know the JTAG pinout, i connect them, i connect the battery with other wires, and with the software H-jtag i tried to connect my phone hoping to enter in debug mod :
i can't configure the target as ARM1136 because there is a message error : "unable to load the driver"
i've read in the reference manual that ARM926 is still compatible, so i choose this one as target device and it seems to be working (i can see READY in the corner of the window )
but when i try to communicate with the phone, a new message say that it's impossible to enter in debug mod : check TDI clock and TAP config :
i put TDI clock at low level (i tried all levels )
and for the TAP configuration : i've read in the reference manual the register adress for bypass, i try something but i'm not sure to understant TAP num : is this the binairy adress of the bypass port ? there a screen, but not with my values
so is there someone who know how can i configurate the target access port connexion ?
Click to expand...
Click to collapse
Have you tried MedusaBox? It repairs hardbricks via jtag
So try it, maybe it costs alittle bit but its worth it

tilakpil: Good Luck man! If you unbrick your X8 with homemade cables etc, YOU WILL BE A HERO!

Have you tried with UART connection?
Send me a PM,I would like to test it too,so maybe we can work it out.

Hello, i'd like to join this conversation because i have a dead galaxy mini in hand and it has got the same qualcomm msm7227 chipset. I'm also trying with an homemade wiggler and openocd.
I've managed to get the IDCODE and the debugging features (i think).
In this document you can see the chipset has got 2 ARM processors, one for apps and one for modem.
Following a thread about a HTC device with a similar MSM chipset, i toggled a script to use the ARM926EJ-S CPU with the right IDCODE.
I got the debug interface up and running fine, i'm thinking on what to do now

any updates?

Sorry but the phone i was trying to unbrick is dead now.
Sent from my GT-I9003 using xda app-developers app

blala said:
Hello, i'd like to join this conversation because i have a dead galaxy mini in hand and it has got the same qualcomm msm7227 chipset. I'm also trying with an homemade wiggler and openocd.
I've managed to get the IDCODE and the debugging features (i think).
In this document you can see the chipset has got 2 ARM processors, one for apps and one for modem.
Following a thread about a HTC device with a similar MSM chipset, i toggled a script to use the ARM926EJ-S CPU with the right IDCODE.
I got the debug interface up and running fine, i'm thinking on what to do now
Click to expand...
Click to collapse
Can you explain please how you got the debug interface up and running ? and/or a link to the HTC device thread mentioned ?
Thank you.

Lex- said:
Can you explain please how you got the debug interface up and running ? and/or a link to the HTC device thread mentioned ?
Thank you.
Click to expand...
Click to collapse
The first step is to find the jtag header on your phone. Search on the net for some pictures, schematics or datasheet that may help you.
Once you found the JTAG header, you need a cable to be able to access it from a PC.
I used a wiggler cable, because it's the simplest and the cheapest. You can find many results and schematics on google if you type "wiggler cable".
Remember to use the proper voltage (3.3v), or you will fry your phone.
Once you have the cable ready and soldered, you can now move to your pc. at first i tryied openocd, but i am uncomfortable with command line debugging, so i looked for a GUI alternative.
On Windows, you can download H-JTAG, a software that will detect the cable and the CPU, and the NoICE Debugger for ARM
Here is the HTC thread, here on xda http://forum.xda-developers.com/showthread.php?t=893144

[Tut][Easy] Recover lost IMEI of your Yureka/+

Hello Guys! Yesterday I was experimenting with my Yureka and accidently I lost IMEI of my phone. I searched YuPlayGod as well as XDA. There are some methods to recover/restore/change IMEI but unfortunately they are not working or they are too difficult to follow for a normal user. I kept searching for the solution and finally came to this. This work is not mine and the credit goes to the respective authors. I just have wrote this tutorial for the reference!
Beware: Changing IMEI is illegal. This tutorial is for those who are having their valid IMEI and have accidently lost during flashing or recoving from a brick. Please refer to your country law for the same.
**Although this tutorial is fully tested as I just have recovered my IMEI, yet I take no responsibility if something wrong happens with your device.**
Difficulty level: Easy
Things Required:
A PC or a laptop with windows as the Operating System, ADB driver installed
Qualcomm USB Composite Device 901D Driver (Link Given)
CKT Qwrite_Writer Tool (Link Given)
2 valid IMEIs to write. Refer to the box or bill for IMEI. It must be there
Your Yureka and a USB data cable
Step 1
Assuming your Yu is rooted. If not, Root it. Enable USB debugging. Install Terminal Emulator and type in the following commands in sequence
$ su
# setprop sys.usb.config diag,adb
Click to expand...
Click to collapse
This basically enables USB Diag mode of your phone. Now connect your phone to PC. You would see something like “Installing device driver software” which would fail eventually. Don't worry! We are about to install the Driver.
Step 2
Extract Qualcomm USB Composite Device 901D Driver at a easy to reach location and install it. There is no executable to install. You will have to install it manually using the Device Manager. See Post 2 for instruction.
Step 3
Assuming you have done the previous 2 Steps. Now the original task begins. Extract CKT Qwrite_Writer Tool to any easy to reach location and run an executable “Qwrite_Writer.exe”. You should see the following window.
{
"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 left side is to write the IMEI, Right side is to Read.
In left side, IMEI_1 : Enter your first IMEI and check the checkbox associated with it.
In left side IMEI_2: Enter your second IMEI and check the checkbox associated with it.
** Leave other things as it is. Do not touch any other setting as you may mess with it **
Now Click the start button at the Right side of the Message Box. And voila! You got your IMEI back :laugh: :good:
Downloads:
Qualcomm USB Composite Device 901D Driver: https://www.androidfilehost.com/?fid=385035244224398036
CKT Qwrite_Writer Tool: https://www.androidfilehost.com/?fid=673368273298918104
Credit:
To the original authors of the respective stuffs.

How to install Qualcomm USB Composite Device 901D Driver
How to install Qualcomm USB Composite Device 901D Driver
------------------------------------------------------------------------------
After enabling USB Diag Mode, connect your phone to PC/Laptop. Go to Control Panel and Open Device Manager. In Device Manager you will see your phone in Other Devices section. As AO5510 in my condition. Right click it and chose “Update driver software”. Then “browse my computer for driver software”. Then “Let me pick a list of device driver on my computer”. Then Next > Have Disk > Browse > and browse to the folder where you extracted the Qualcomm USB Composite Device 901D Driver. You would see a file named “htcser.inf”. Select that file and hit Ok and then follow the On-Screen-Process to finish the installation.

androidfilehost.com/?fid=385035244224398035 (IMEI WRITER SOFTWARE) this given link is not working . please update it soon.

rohitjaiswal said:
androidfilehost.com/?fid=385035244224398035 (IMEI WRITER SOFTWARE) this given link is not working . please update it soon.
Click to expand...
Click to collapse
Link updated in OP

Link not working
itsdroid said:
Link updated in OP
Click to expand...
Click to collapse
CKT Qwrite_Writer Tool: fid=673368273298918104
not working 404 error

it worked...thanks

Enabling basebands on MZP (works with almost any Qualcomm phone).

Hi folks! Today i'll bring you a guide to enabling all the basebands in qualcomm manufactured phones, focused in Moto Z Play.
Since a lot of us got the Chinese version of this phone, i have been reading a lot of people complaining about signal problems and that's cause the MZP CN comes with band 800 only. Now i made this guide to show you how to enable the base bands in our phones (and other Qualcomm phones, so feel free to share it).
First of all, you have to get all the things to work, these are:
USB Cable of your phone
A working PC with Windows
QPST and mztool software
QDLoader HS-USB Drivers
I have uploaded the QPST with MZTool and the Drivers for your convenience, since this software have the capability to modify the imei, i can't upload directly to xda.
QPST is here
Drivers are here
Well, first of all, we have to make a backup of our radio partition, if something goes wrong or if you lost your imei in the future, etc.
For doing this we will have to turn off your phone, then start it in bootloader mode (vol down and power), and then scroll to "QCOM" and press power.
Then you have to plug the cable to your computer and install the Drivers and the QPST Software, if you had installed previously don't worry, just wait 'till the PC recognize the phone and install it, it should look 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"
}
After installing the device drivers, you should start saving the backup, for doing this, open program QFIL in the QPST folder in Start menu of your computer, then going to Tools tab and selecting "Backup/Restore QCN" option like this
Then select the folder to read/write the .qcn file (this will be the backup, so you can change the filename and the destiny folder).
Later open RF NV Manager, but first of all, you must close QFIL and open QPST Configuration program from the QPST Start Menu Folder, then open RFNV Manager (if this last one doesn't come up in the QPST Start folder, don't panic, just search for it in bin folder at QPST install folder and open the program from there)
In RF NV search for tab Setting > Comport, and in the drop down menu look for the COM port that matches with the one in the QPST Config program or the one in Windows Device Manager, then select from tab File > Read from Phone, and wait 'till it finishes. After this, scroll down in the items left box to number 1877, this is were the basebands are written, click on this and a number should appear at the right box like this
Then open mzTool and select on "Band Preference" tab the basebands you want to enable, then look for the decimal number in the right lower part and write it on RF NV, then select 'Write NV' box upper from the box you entered the code, click this a couple times just to be sure it's done
Then reboot your phone on normal startup, open the dialer and press *#*#4636#*#* to open the testing menu, and then select the phone info menu, then in the scroll down (the vertical three dots) select the radio you want to use, and that's all!

Attach files to your post or reupload files to zippyshare please. Google removed them.
Mike

Seriously we can get the Droid version and it work as unlocked?

Can it enable AT&T LTE bands on Chinese version?

Is there any way for me to use a baseband version after which i might be able to enable Volte which is not working on my rom. I am on darkness redefined rom.

i posted the similar method for enabling bands
it does display all bands supported. but actually it doesn't
i think all bands working unless mod the radio file
same tutorial in mzp thread of)'enabling dual sim in single sim device' ?

QPST link is dead.

Anyone confirm this is working? Could we upgrade to Droid MZ2 Play and enable other bands?

Hi! May I ask about the same tutorial for Moto G5S Plus (XT1804) to extend the LTE bands with the European ones? (I have Indian phone).

MZP CN comes with band 800 only
Click to expand...
Click to collapse
What does this mean? I have the RETCN variant and I'm currently connected to LTE. My operator supports LTE bands B3 and B40.
Update: just tested with Network Signal Guru and my ohone is connected to Band 07 (2600) so that one is supported too. Am I missing something?

xt1635-02 on verizon
Is it possible to use this tutorial to bring my xt1635-02 to verizon? Would I have to flash the verizon xt1635-01 rom with RSD Lite?

Hello!!
Thank you so much for your manual, it is great
do you know where i can find QPST for this purpose?

[SOLVED] Unlock BTV-DL09, problem modem

Hello everybody.
I wanted to unlock an BTV-DL09 [ Android 7 EMUI 5.04 EU ], but I'm stuck like the_wing was.
Modem no found !
Phew, got it unlocked! Moments of terror when entering the commands on the cmd...
A few mentions where I got stuck that may help someone else:
Regarding point 3:
In case your model has LTE (i.e. BTV-DL09), you actually should have a dialer application that you have to use instead of the calculator app, which didn't work for me. This is also mentioned in the DC unlocker app. In case you do it with the dialer, you have to enter following code: *#*#2846579#*#*
Regarding point 4:
Inside the "DC unlocker" app, I also got the "device not found" error, and I was wondering why. Two things I noticed:
- To enable USB debugging, it was not sufficient for me to activate the switch in the developer options, as the default USB mode for me is "charging only". I had to change it to i.e. "Device File Manager (MTP)" by tapping on the notification and then re-activate USB debugging in the developer options (which turned off after switching to MTP mode) to get USB debugging working.
- After enabling "manufacturer mode", the mode was turned off as soon as I quit the menu. So I had to stay in the menu to make sure manufacturer mode is on.
- You can check your device manager in Windows to see if the current mode is active: When doing USB debugging, the device "Android Composite ADB Interface" should show up under "Android Phone" list, whereas when you turn on manufacturer mode, some COM ports should show up under "Ports (COM and LPT)"; the one DC unlocker is searching should be named "Android Adapter PCUI". If you got some devices with not properly installed drivers you should consider installing HiSuite software on Windows first.
Regarding point 8
- When I bought the credits for DC unlocker for PayPal, I had to click on a link arrived to the PayPal e-mail for confirming your account. I then still got the "Server login error", but closing and reopening DC unlocker eventually fixed it.
Hope this helps! Happy unlocking to everybody!
Click to expand...
Click to collapse
I have installed Hisuite and Huawei data card driver.
Impossible to activate Device File Manager (MTP) and manufacturer mode, one deactivates the other, I do not know if this is the problem, but according to the tutorials it is a must.
I have a hard time understanding where the problem comes from, I even tested different USB cable, Win 7 and Win 10, I really did everything, but I'm dried.
{
"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"
}

I finally managed to unlock the bootloader, DC unlocker did not show me information from the tablet, but despite this, I could go to the next step and proceed with the unlocking, it is because of a msie security update according to Valdemaras on cd-unlocker forum, thanks to him.

[Guide] Fix for device not working in fastboot / unable to install official driver in Windows 10 / 11

If you are getting the error as in the screenshot below, this solution is for you.
1. Download the attachment "Generic Driver.zip" and extract it
2. Click on "Update Driver" in the dialog in the screenshot.
3. Browse my computer for drivers
4. Let me pick from the list of available drivers
5. Show all devices
6. Have Disk
7. Point it to the extracted folder and click OK.
8. You will see 3 new items in the box now Choose "Android bootloader interface" in the list and click next
9. It will show you a warning. Ignore it and press Yes
That's all! Enjoy
{
"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"
}

Oneplus USB drivers were not enough on my win11 pc but your method worked, thanks very much

Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.

anuahmed89 said:
Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.
Click to expand...
Click to collapse
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com

in my case, the other devices it doesnt show when i connect it with usb and it also doesnt show USB CONNECTED notification on my status bar? it would be really helpful if someone can help with the fix, Thankks and Appreciated.

I just went through the same exercise. However, I did not want to download drivers from unknown source (or even worse - run some *magical* driver fixing executable), right?
I am using Samsung Galaxy Tab A7 Lite and the ADB drivers came from Samsung and adb was working.
However, once I put the tablet in fastboot mode the USB re-enumerated and Samsung drivers didn't cut it!
Inspecting DeviceManager gave me the USB\VID_18D1&PID_4EE0 and Google search shows this is actually a Google VID. The rest is history: Downloaded (signed!) driver from Google (specifically this) and voila - life is good!
I hope this may help others avoiding wizardry with unsigned drivers.

I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance

Dieppy said:
I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance
Click to expand...
Click to collapse
Not sure if this will help but I would run "usbview" to see what is enumerated. Since the tree is very bid these days with many hubs and USB devices already connected you might first plug-in anything known to the same USB port to see where on the tree it sits. Then plug-in the phone and look at the same spot ("bark at the same tree" ;-) )
If you nave a NIX system "lsusb" will do you similar service. Both are driver independent. Then (if the phone is recognized) get the VID and PID and google what got enumerated and you may end-up with the right driver.
In the case nothing is detected at this low level the only explanation I would have is that the boot doesn't initialize the USB interface on the phone. That would be weird and nasty.

Hey
While trying to install drivers using have disk I encounter a problem. After navigating to the android-usb.inf file I press ok and it rolls back to asking me where is the disk. I tried disabling driver enforcement but to didn't work. It's like windows doesn't want to work. I am using a win 11 copy via parallels on an M1 Mac.