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
Related
Hi all
I have a challenge I would like your help with.
I bought the Cx-919, and after a day or so I've decided to flash it with a better ROM.
Searching the internet I found this ROM, and decided to give it a chance:
http://freaktab.com/forum/tv-player...-kitkat-v1-new-firmware-for-cx-921-and-cx-919
But since I had some bad flashes of tablets and phones in the past I've decided I would need a backup of my current rom.
I've accomplished this by using this method:
http://freaktab.com/forum/developme...p-your-rk-device-rom-with-the-new-rk-2-1-tool
I did it twice, just in case I did something wrong.
By this time I had no problem with the drivers, I have installed them successfully and both the RK2.1 and the finless ROM flash tool V 1.37 had no problem finding my device while it was connected to the computer.
When I started the flash itself things started to go bad.
The finless ROM flash tool V 1.37 log had said-
Start to run
Start to test device
Test device ok
Start to download IDB ok
Download IDB OK
Start to reset the device
Reset device failed
Device not found
And after that the status bar at the bottom said no found RKAndoroid rock usb.
I have waited for about 6-10 minutes thinking this is part of the process, before trying re -find the device.
Also the LED of the device had turned off.
I've tried to reattach the device but with no success, the computer just did not recognized my cx 919 attached.
I have tried to restart my computer, reinstalling the drivers, attach the cx 919 to different ports, and even tried to boot it to recovery. Alas nothing worked. The device is dead.
After looking in different forums I saw this post about bricked cx-919 and possible solutions:
http://freaktab.com/forum/tv-player...How-to-boot-CX919-in-quot-Mask-ROM-mode-quot=
http://forum.xda-developers.com/har...x919-ii-completely-bricked-tv-signal-t2859564
https://www.youtube.com/watch?v=sSjaB522QJs
http://freaktab.com/forum/tv-player...players-aa/11230-unbrick-cx919-circuit-method
And since I had nothing to lose I've decided to give it a try.
Alas something went wrong yet again! As I opened my cx-919 I've noticed something is different in my cx-919.
View attachment 3353734
First thing that was different- was that I had a thermal cover over the chips.
View attachment 3353735
And since I did not saw any visible NAND chip I figured it must be under the cover.
So I removed the cover, and still couldn't find the Chip I'm looking for.
{
"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"
}
Maybe it's in the back I thought, but no.
I hope one of you can maybe rise to the challenge, and help me find a way to make this device recognizable again by my computer.
So I kept on trying to fix the device, But still with no successes.
Since my device is built quit differently from other devices and uses different chips set, I figured I will try and understand what the different chips does.
Maybe by that I could find out which one is the nand chip. and try to short its 7-8 legs or 5-6 legs and get it to MASK ROM mode.
there are a few tutorials out there about how to this in the Micron chips, but i cant post any of them cause i'm a new user... so you would have to google "CX919 mask rom"
and i followed one of those.
so the small one at the bottom (RTL87) as far as i can understand is the Ethernet controller, by real take.
the one in the middle is SK hynix this is a ddr-3 chip.
that only leaves me with the rockchip RK3128 chip to be the nand chip.
now all i have to do is figuring out if there are any legs i can short together like 7-8 in the micron chip in order to get this device in MaskRom mode.
Then i need to understand how to short them- since these chip's legs are underneath the chip and not on its side.
so far no success, i will post on further development.
So I gather no new developments.........I have the same problem with one of my sticks......oh well seems to be a solid bricked stick......
I have the same device. Might have something you can try.
Hello,
Please does anybody have the correct Qualcomm Diagnostic Driver for Huawei P8Lite ALE-L04? I am trying to tweak my phone (LTE Band modify) but cant see it in diagnostic mode on my Win 10 PC's Device Manager - and so also cant see it on QPST even after installing a qualcomm driver i got from the net. If I add the COM port on QPST, it sees it as a non-diagnostic connection and so doesnt actually see the phone as connected.
Also, if there are lots of drivers that can work but I'm not setting it up properly on my PC, can someone pls send me correct procedure - and maybe one of the correct drivers? Thank you all.
Maybe you need to switch the USB mode.
Dial *#*#2846579#*#*, Background Settings -> USB Port Settings, select Manufacture Mode
Post updates! I'd like to try something similar.
dedenn said:
Maybe you need to switch the USB mode.
Dial *#*#2846579#*#*, Background Settings -> USB Port Settings, select Manufacture Mode
Post updates! I'd like to try something similar.
Click to expand...
Click to collapse
I have already applied all the above settings and allowed the default modem driver to install even before my original post.
Under Device Manager -> Modems, my device appears as "Android Adapter Modem" on COM Port 9 while:
Under Device Manager -> Ports (COM & LPT), my device shows as "Android Adapter PCUI (COM6)" and "DBAdapter Reserved Interface (COM5)".
Then on QPST, even after adding the COM9 port, the phone is not seen and therefore both QPST and QXDM cannot connect to it.
If I had the correct MSM8939 Qualcomm Diagnostic driver - or I can be shown how to switch the phone to go directly into diagnostic mode, I believe it can then be seen by QPST (as MSM8939 Diagnostic port, I think) and so can connect to QXDM.
Please any help is appreciated. Thank you.
(Pictures attached)
{
"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"
}
Can you set "Qualcomm background open setting" to open?
It asks for a password, I just figured out any 16-character string (e.g. aaaaaaaaaaaaaaaa) works (KiteKat B111 official ROM). But slill I get "Qualcom background unlock failed"...
I've used several password to try and open the Project Menu -> Background Settings -> Background Debug but none works. Even tried my bootloader unlock code. Do you have any password code I could try?
Please and pleeeaase, does anybody have the code to set Qualcomm background debug to "OPEN" in the hope that I can enter "diagnostic mode" and use QPST+QXDM on my phone?
Or is there a driver I can use on the P8-Lite ALE-L04 Qualcomm MSM3989 chipset to connect to it in diagnostic mode on QPST? Any help will really be appreciated cos i've:
1. tried a range of drivers both from xda and the internet - and non can connect my phone to my PC in diagnostic mode - probably because they are not the tailored driver for the Qualcomm Snapdragon 615 MSM8939 chipset
2. tried to contact Huawei severally but got no response from them.
3. even searched thru qualcomm website and contacted them but they told me they're a "technology provider" and therefore dont answer product specific questions. They advised i contact Huawei. Again.
Alternatively, is there another method for modifying the phone's LTE band without using QPST and QXDM?
Thanks in advance for any help.
I was only able to decompile the Java part of the ProjectMenuAct.apk that is responsible for the hidden menu (it's odexed, the virtual machine code is not in the .apk, but in ProjectMenuApk.odex file), and it was the 4.4 KitKat official ROM.
The Java code verifies the password is 16 characters long. If it's not, a message says the password is wrong. If the password has the correct length, it's sent to some native ARM code (maybe libprojectmenu.so), which I couldn't decompile (too advanced for me)... The native code returns an error that the 'backgroud unlock' was not successful, maybe it needs some other password.
For deactivating the 'background unlock' the Java code uses '0000000000000000' default password.
I got stuck here, I got rid of the phone (and got another one with similar problem .
Still stuck with my ALE-L04 and cant modify the LTE band to use Band 28 here. Any help?
Meanwhile, is there no available OEM or even better a Custom ROM for ALE-L04 to Android 6 so I can upgrade and see if it helps unlock Project menu/Background Debug and I can connect in Diagnostic Mode to QPST & QXDM and modify LTE band?
Merry Christmas!
Hi! I have a Y635-L01. Stuck in the same place here. Any news about this? I've tried the bootloader unlock code (which is also a 16-digit number), but without luck.
I'm trying to get the code from the seller, which happens to be a big carrier in Spain, but it's kind of difficult since I don't have a subscription (or a SIM card, for that matter) with them. I only bought the phone, unlocked.
Firmware for Chinese 7" Head Unit with AC8227L YT9250_AHD_00006_V004_20190610_DSP
Hello everyone !
I have a Chinese Head Unit (Motherboard Marking: YT9260-ver0.2, Model no: 8227L_demo android 9.1, Android: YT9250_AHD_00006_V004_20190610_DSP, Kernel: 3.18.22, DDR 2GB FLASH 16GB, Mediatek MT6323LGA, Foresee FSEIAD9D EMMC 16G). Unfortunetly bad rom and preloader was written to the device and now it is completly brick. When i connect to USB my computer detects it (Mediatek USB VCOM), so maybe i can save it. Can anyone send me a preloader with scatter, rom and memory dump? Could someone please give me some ideas or advice? I also attach some pictures. Best wishes, thank you.
Picture 1: https://forum.xda-developers.com/wiki/images/f/f2/Received_2334422033536330.jpeg
Picture 2: https://forum.xda-developers.com/wiki/images/7/79/Received_1345495808957345.jpeg
Picture 3: https://forum.xda-developers.com/wiki/images/b/b3/Received_537143560170706.jpeg
Picture 4: https://forum.xda-developers.com/wiki/images/3/32/20191205_082741.jpg
Picture 5: https://forum.xda-developers.com/wiki/images/c/cd/20191205_082717.jpg
Picture 6: https://forum.xda-developers.com/wiki/images/b/b4/20191205_082633.jpg
Try this link brother: https://forum.xda-developers.com/android-auto/android-head-units/everything-yt9216b-t4007063
roly_HR said:
Try this link brother: https://forum.xda-developers.com/android-auto/android-head-units/everything-yt9216b-t4007063
Click to expand...
Click to collapse
Thank you my friend.
I try, but no luck. Flash Tool always returns an error "Enable DRAm failed or DRAM not response" :crying::crying: .
Syab said:
Thank you my friend.
I try, but no luck. Flash Tool always returns an error "Enable DRAm failed or DRAM not response" :crying::crying: .
Click to expand...
Click to collapse
I did the same thing. I was able to revive the unit with that preboot + the test point recovery method.
Good luck!
Syab said:
Hello my friend.
You wrote to my post yesterday. Can you help me ? Would you like to write a step-by-step process? I've downloaded your preloader. Do I need a scatter? Thank you for your kind help.
Click to expand...
Click to collapse
Dude, don't take things like this to PM. Keep it in the main thread so that others can chime in and learn from the information here.
Launch the flash tool
Go to the download tab (it opens up to this tab)
Leave the default Download Agent, MTK_AllInOne_DA.bin
Load this scatter file (discard the included preloader) (link)
Load this preloader (link)
Your screen 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"
}
Go to the 'Memory Test' tab
Select RAM test & hit start.
Short the two test points (see picture) without power and then plug in the usb cable (connected to usb1 port).
Remove the short when the process starts
If everything worked it should pass the RAM test. If not, don't proceed.
Disconnect the USB
Repeat steps 1 - 6, then continue to 12
Press Ctrl+Alt+V , then go to Window and select "write memory".
In file path select your backups (EMMC_BOOT1.bin, EMMC_BOOT2.bin, & EMMC_USER.bin), in begin address put 0x0, in region select the correct partition to match the backup. Hit Write memory. Repeat this step 3 times, once for each region (EMMC_BOOT1, EMMC_BOOT2, & EMMC_USER)
Short the two test points (see picture) without power and then plug in the usb cable (connected to usb1 port).
Remove the short when process starts.
Your backups are restored
Velda2 said:
Dude, don't take things like this to PM. Keep it in the main thread so that others can chime in and learn from the information here.
Launch the flash tool
Go to the download tab (it opens up to this tab)
Leave the default Download Agent, MTK_AllInOne_DA.bin
Load this scatter file (discard the included preloader) (link)
Load this preloader (link)
Your screen should look like this:
Go to the 'Memory Test' tab
Select RAM test & hit start.
Short the two test points (see picture) without power and then plug in the usb cable (connected to usb1 port).
Remove the short when the process starts
If everything worked it should pass the RAM test. If not, don't proceed.
Disconnect the USB
Repeat steps 1 - 6, then continue to 12
Press Ctrl+Alt+V , then go to Window and select "write memory".
In file path select your backups (EMMC_BOOT1.bin, EMMC_BOOT2.bin, & EMMC_USER.bin), in begin address put 0x0, in region select the correct partition to match the backup. Hit Write memory. Repeat this step 3 times, once for each region (EMMC_BOOT1, EMMC_BOOT2, & EMMC_USER)
Short the two test points (see picture) without power and then plug in the usb cable (connected to usb1 port).
Remove the short when process starts.
Your backups are restored
Click to expand...
Click to collapse
I tried this method. My computer recognizes the device on COM3 port, in program the red progress 100% (Download DA 100%), then after 10 seconds the program prints Enable DRAM failed. I followed you instructions step by step, I shorted the two test points, but the program just prints Enable DRAM failed. Any idea ?
Syab said:
I tried this method. My computer recognizes the device on COM3 port, in program the red progress 100% (Download DA 100%), then after 10 seconds the program prints Enable DRAM failed. I followed you instructions step by step, I shorted the two test points, but the program just prints Enable DRAM failed. Any idea ?
Click to expand...
Click to collapse
Hmm, send me your EMMC_BOOT1.bin file. I'll extract your original preboot from it.
Velda2 said:
Hmm, send me your EMMC_BOOT1.bin file. I'll extract your original preboot from it.
Click to expand...
Click to collapse
I have no memory dump. I got the device after they had uploaded faulty rom and preloader and they didn't make a backup. I know that if the preloader gets damaged, the usb connection will not be established, but in this case it will be up because my computer recognizes the device. There may be a problem with the preloader being defective and the Flash tool cannot write to the memory. Can we write through Rx Tx? It is possible ?
I got the same head unit with the same problem. Ill try this method and see what will happen
Syab said:
[...] Can we write through Rx Tx? It is possible ?
Click to expand...
Click to collapse
This is a bit old thread so I'm not too sure if it still useful, but if so I would recommend to use Arduino Uno which can easily communicate through UART.
More infos here:
https : // ns-electric.com / knowledge-base / intro-to-arduino-uart-serial-communication (please remove spaces from link)
Short the two test points (see picture) without power and then plug in the usb cable (connected to usb1 port).
can you send photo where is two test points?
Velda2 said:
Short the two test points (see picture) without power and then plug in the usb cable (connected to usb1 port).
Click to expand...
Click to collapse
can you send photo where is two test points?
hello my friend...
My AHU is nothing Apps EQ, how to solve that problem. Please Help... any Apps/APK Equalizer AC8227L.
Cari file YT2960
OK, I just received this device:
{
"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"
}
which is sold under various names from vendors @AliExpress.
I'm trying to match this unit with one of the threads here and it seems like no one is dealing with it, but I may have missed some relevant posts, can you please help me with that? Or maybe you know about other forums where they discuss the unit...
The device has several issues (bottom line: do not buy it, the hardware is okish but the software is horrible) and I'd really like to explore ways to customize it but I'm not even able to connect to it via adb, let alone become root or install a custom firmware...
Seem like no one heard of it. Bad luck.
I'm trying to gain root access and fix some of the bull***, but I'm running short of options.
What I know so far:
Invoking "su" from the command line (or via adb) returns a "not allowed" message;
I have no firmware to patch with magisk;
the amazing temp root does not work, the device is patched.
What else could I try?
I may try the MTK Droid Tools, but I think they use the same exploit used by the amazing temp root so I guess this is not a solution. Moreover they need Windows and I can't connect to the unit with adb in windows, only with Linux (heavens know why, the Universal ADB Drivers says it's all "ok" but adb does not see the device).
Did you get anywhere with it? I just got 825x_pro for my R56 Mini.
Nowhere. There seem to be some info in the 4pda.ru forum (in russian) but I did not dig deep into into.
What's your factory setting password? 1812 takes me to factory settings and 8877 takes me to another menu which I can use to go to engineer mode
How and where to use these codes
Fake device tester says that it is android 9 instead of 10
amit1976 said:
Fake device tester says that it is android 9 instead of 10
Click to expand...
Click to collapse
What tester? Have you got a link so I could check mine please?
Have you found where to put these codes?
brodzik said:
What tester? Have you got a link so I could check mine please?
Have you found where to put these codes?
Click to expand...
Click to collapse
There are many apps on playstore , i used fake device test by appsolutely unique
amit1976 said:
There are many apps on playstore , i used fake device test by appsolutely unique
Click to expand...
Click to collapse
I just installed it and the app doesn't open, I mean the screen blinks like it's just about to start and then it goes back to home screen, any ideas?
Does anyone happen to know if there is custom rom that will work on this device please?
brodzik said:
What's your factory setting password? 1812 takes me to factory settings and 8877 takes me to another menu which I can use to go to engineer mode
Click to expand...
Click to collapse
Where to use the codes?
I got alps 825x_PRO. 10.1" It can't remember settings, video out is not working, lights are not working. Need reload firmware. So far I got 8888, 8877, 8878, for settings. But it won't remember. If anyone can help me where to get firmware. Seller Ossuret Factory Store is bad. Sending videos of different models and useless solutions. Refused to give me the firmware.
tefracky said:
Where to use the codes?
Click to expand...
Click to collapse
Hi,
You have to go to:
- The settings
- "Car infotaiment" and click in the high right corner on the "cogwheel" and you get a little window where you have to type the numbers (example: 5678; 8888, ....etc ) And you get the hidden menu !
brodzik said:
I just installed it and the app doesn't open, I mean the screen blinks like it's just about to start and then it goes back to home screen, any ideas?
Click to expand...
Click to collapse
Yup this was my experience of "Fake Device Software" Could it mean it is fake? I downloaded another and found the device advertising it's self as Android 10 but with an API level of 28 which relates to Android 9 or wear devices so ???
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.