I own the TV BOX TRANSPEED_H616 (Allwinner H616, Arm Mali-G31 MP2, Android 10, 4/64 GB).
I would like to root but can't. I can't even connect the device to the PC.
When I connect it with the USB-OTG cable, in the device manager it shows "USB device unknown (device descriptor request failed)" and I cannot find the drivers. Can someone help me?
Thank you
i have same problem.
After several attempts I managed to enter recovery mode.
I would like to root the device now but I don't know how to do it.
Can anyone help me?
Thank you
Since no one can help me, I want to try to summarize everything I understand using this device. The first thing to do is to enable the developer option and then check USB DEBUG and USB0. At this point, by connecting the USB cable to the OTG input, the device is recognized by the PC as MPT. By opening the Phoenixsuite or Powershell application from the SDK folder you can send commands to the device, you can access the custom recovery and nothing more. Unfortunately, the bootloader cannot be unlocked, and the firmware cannot be changed either through the PC or even with SD. When entering Bootloader mode the PC loses connection with the device because it changes to an unknown device without drivers. Also with Powershell if you want to unlock the bootloader this is not possible because when you send the command "./fastboot flashing unlock" it returns the message "Failed". By inserting the SD card with the firmware and starting the device with a stick inserted in the AV input and the electrical AC connector, a red indicator lights up on the display and the flashing does not start. Clearly in these conditions it is impossible to think about rooting the device. I hope that in the light of what has been said, someone can give me some research ideas or useful advice. Finally I apologize for my English (from Google)
Hello, recently I bought a transpeed X88 pro s (from transpeed official) , h616, 4gb+128gb with android 10.
But it is a fake, it's a board with hacked firmware (dispute is open) , it only have 64gb ( chip Samsung Klmcg2ketm), it warm so much (more than 90°C) with faults on gpu (changing colors, slowly,...), only way to work is with open box or fan.
Anyway, I'm in the way to root and change firmware too.
It's rooted by default, with supersu 1.82 work well and permit restart to bootloader (with reset button was impossible).
I will inform about progress.
Related
Hey all.
I use a Redmi Note 3 (Snapdragon) and upto now I used CM13. I wanted to switch back to MIUI 8, as it supports LTE, so I tried to flash the MIUI ROM using TWRP. My device bricked and doesnt go past the loading screen. The bootloader also got locked and my device is also not being detected in adb command prompt. In device manager, I can only see ADB Bootloader driver but not any other. I tried installing ADB drivers again but it doesnt work. I believe I did not enable USB debugging. I have a TWRP backup of the previous ROM on my pc but is there any way to flash it?
Please help
Hi , I am new to xda and was previously viewing the posts of other users only, now I have an issue with one of my devices. I have a phicomm passion 660 in INDIA AKA Phicomm P660 in Europe.issue is the digitizer is broken ,USB debug is not enabled, ADB and Fastboot doesn't recognise the device as it appears to be issue with Google USB drivers( which is obvious due USB debug not enabled), all I want to do is use optical mouse to use the device again for DEDICATED VR VIEWING, I can boot the device to Fastboot and in normal boot the pc recognises the device as MTP, I tried steps from many other posts but since the device is not recognised by ADB , the result is ground zero,cant install cwm through sdcard due signature verification error.so any help or direction to relevant posts would be very helpful
Hello, I own a RCA Viking Pro 10 tablet with Android 6.0 installed (RCT6303W87M7). I am having a lot of trouble rooting it for two key reasons.
1. It seems to be incompatible with most "One-Click" root applications.
2. It requires a special type of A-A USB cord, so it can not be connected to any computers.
I have looked through many root methods, but none of them seem to work. Any suggestions would be appreciated.
I have the exact same tablet and came upon those same two problems. I have, however, purchased a USB A-to-A cable and tried connecting it to a PC. I noticed that if the tablet is on when you connect it, the PC wont recognize it, but, if the tablet is turned off, the PC sort of recognizes it and begins to download and install drivers. The problem is is that once the drivers and installed, I can't find the tablet in my device manager.
One-click APKs don't work. I've tried, King Root, Kingoroot, One-Click Root, Towel Root, iRoot and virtually any and every one-click root that I come upon in the wild. I've also tried the PC root method with the USB A-to-A cable. I've used iRoot, King Root and Kingoroot. These obviously don't work because of the PC connectivity issue mentioned above.
It's a real nice tablet to dabble with, just a damn shame that there is virtually no information on it out there. If you do a google search, you will more than likely end up at this thread: https://forum.xda-developers.com/an...e-rca-viking-pro-rct6303w87dk-t3325158/page52 . Unfortunately, this thread is dedicated to an older model of this tablet running Lollipop. The only thing to do would be to keep searching and re-searching until we find something on it. Hope this helps.
so i'm still trying to root the RCT6303W87M7. i'm not really trying to install custom roms on it, i just want root access. so to update, i finally got my pc to recognize the device; but i dont beleive that it's recognizing it properly. here's what i did, making sure that USB debugging & OEM unlocking are both enabled in the developer options, i did this:
1. hold the 'power'+'volumeUP' buttons until you get into recovery mode
2. once in recovery mode, go to and select 'Reboot to bootloader'
3. when the 'Fastboot mode' message appears at the bottom of the screen, plug in the USB-A male to male cable to the PC
4. if you have your device manager open, you will notice that it is recognized as 'Android Phone'/'Android Sooner Single ADB Interface"
i tried rooting with three different 'one-click root' pc applications: iRoot(v1.8.8), Kingoroot(v1.5.0), and King Root(v3.5)
these are the results i got:
-iRoot: it connects but the message reads 'Not support mode'
-Kingroot: it detects the device and trys to connect but gets stuck in a loop trying to connect
-Kingoroot: this detects the device as 'HTC Device'. i click the 'Root' button and it trys to root, but it only gets to 19% and then it fails
i'm theorizing that maybe if i get some different drivers for the pc or maybe making sure that the 'one-click root' applications are the latest versions might help. i dont know, we'll see.
again this is for the RCA RCT6303W87M7 running Android 6.0.
if anyone tries this and has more success, please let me know.
Guys, sorry in advance if this question is kind of a duplicate, but really I spent hours here to find some solution.
I am affraid I am in a deep ****, but I need your confirmation, 'cause you are the experts.
Will make it quick and simple.
Model: Huawei P9 lite 2016
Physical Status: damaged black display, not reacting. New display(s) not working at all. Buttons are fine.
Logical status: USB debugging and other stuff is OFF, OTG is even maybe not supported. I was using HiSuite only and I had to everytime manually confirm that I want e.g. FileTrasfer. Noq I can start up the phone (even log in I think thanks to FingerPrint) and HiSuite partition appears (but not the one with data of course).
What I already tried: I installed ADB and FASTBOOT to my PC. I am able to see my phone in FASTBOOT mode only. I am starting the phone with VOL- and insterting USB cable. However due to all the functions like USB debug off, I am not able to finish any task to unlock anyting or to load another image etc. All is forbidden. When running ADB.EXE, no device is found, no matter in which mode I boot up the phone.
Again, I think this is because of disabled USB debugging mode and I have no chance to change it using standard GUI.
Any hint or am I really done?
Thanks a lot.
okay so, i just got this phone. did all updates, enabled bootloader unlocking and made my mi account, downloaded the mi unlock tool and everything.
heres where the problem comes in.
everytime i try the button combination to get into fastboot, it works. but then when i connect my phone to my computer, the fastboot splash screen turns black with little text at the top saying "press any button to shutdown" or something like that. it just wont stay on the fastboot screen, its like its exiting fastboot mode on its own.
why does it do this, and what can i do to fix it?
note: i have downloaded all drivers and software to get this to work, and nothing seems to be coming to light.
please help me, i am very confused.
update: actually, it seems to be fine before i open the mi unlock tool. it seems that when mi unlock tool is not open, it stays in fastboot mode, but as soon as i open mi unlock tool, it just kicks me out of fastboot mode, and goes to a black screen with something at the top saying the exact same thing i mentioned earlier.
Turn on the phone go into developer settings and enable usb debugging, im pretty sure that's it
Deexterity said:
Turn on the phone go into developer settings and enable usb debugging, im pretty sure that's it
Click to expand...
Click to collapse
i already have enabled usb debugging. but for some reason, it won't just stay in fastboot mode.
was thinking about calling xiaomi and seeing what they have to say. because i cant find anything on this matter, so its probably just something im doing wrong. though it may be my version of windows. i have Windows 8.1. so maybe thats the deal?
this is stressful lol
If I'm not mistaken, you should only connect the phone in fastboot mode when the program asks, not before you open it
Deexterity said:
If I'm not mistaken, you should only connect the phone in fastboot mode when the program asks, not before you open it
Click to expand...
Click to collapse
i know, i did that too. but the problem still persists... ill try some other time.
thanks for helping though
First off this is much better place to ask questions. When phone is running and you connect to pc can you access storage?
If not check drivers, try different usb cable, and try different usb ports.
If yes then can you access the phone via adb?
If not it is a pc issue probably drivers.
If so leave phone booted and connected then open unlock software. Once software is up and running go to terminal/command prompt and type "adb reboot bootloader" without quotes.
I don't think it is windows version but with Microsoft anything is possible. I still use windows 7 for all this stuff.
Had the same problem on my Desktop with Ryzen, i tried it on my laptop with Intel Celeron and it worked from the first try without any drivers installed. If you have AMD that might be the cause
Hello.
My personal experience says:
1 Install Drivers on the PC/Laptop.
2 Activate DEVELOPER OPTIONS
3 Accept O E M Unlock
4 Allow usb debugging
5 Shut down Wi-Fi and use only DATA in order to connect - verify the device to the Mi account you have. When connected, press "understood" or ""accept"" (however it pops up).
6 Connect the phone to the PC/Laptop
7 After being connected, shut down the phone and put it in FASTBOOT. Make sure your PC ""reads"" your phone. Do it through command line/power shell, and make sure it shows up as alphanumeric in command line (i hope you know what to type - e.g fastboot devices)
8 Download and use the mi unlock tool (preferable Versions 2.....). Connect through this tool to your Mi account
9 Ask for permission to unlock // unlock your phone if days-hrs have passed. Ignore any pop-up message/warning and go on.
VERY IMPORTANT NOTES:
A. The phone must be recognized from the PC as ADB INTERFACE (in device manager) both in normal and Fastboot modes. Any other case is waste of time.......
B. Use a good cable and have the mobile charged!
C. In case you have another (older) device connected to your account, disconnect-delete it or else you will end up stuck with a ""cannot unlock message""
D. The process will not work if your PC runs some Win 10 versions as well as if built with RHYZEN PROCESSOR. Prefer PCs running win 7 or 8.
E. You must have DATA connection available or else you will not be able to connect-verify the phone to/through your Mi account !!! it is a new (dual function) fail - safe procedure from xiaomi!!!
F. Make sure you have the correct drivers installed to avoid a brick - bootloop etc
Hope it helps!
Gathered from my own experience!
To summarize: The xiaomi imposes too much rodeo and much time spent of the user to just "try" to unlock a simple bootloader, better to change of apparatus and to be happy with the practicality. lol
Hello everyone. I was trying to downgrade from emui 8.1 to emui 8 using the dload method. Everything was fine until the phone rebooted and nothing was showing on the display. I let it sit for about an hour and still nothing. The phone was completely unresponsive. Plugging it into a computer, windows recognized it as a kedacom usb device named Android bootloader interface. At this point, I tried to flash the board software using the image downloader software for Hisilicon devices. Unfortunately, it did not work and gave me error 29. I realized at this point I needed to put my phone into com1 mode, so I opened it up and found the probe point near the lcd connector. I disconnected the battery and lcd connector and plugged the phone into my laptop. I shorted that test point with ground and windows still recognized it as kedacom usb device named Android bootloader interface. I tried reinstalling the huawei drivers provided by the software, but I just can't get windows to recognize it as huawei com1 interface. Am I doing something wrong here? Is it the wrong probe point I am shorting? Any help would be appreciated! Btw the bootloader is locked and phone is not rooted.
Phone's actual configuration - for whatever reson - is to boot into it's bootloader.
Try
Code:
fastboot devices
fastboot reboot
to get phone booted in default mode.
jwoegerbauer said:
Phone's actual configuration - for whatever reson - is to boot into it's bootloader.
Try
Code:
fastboot devices
fastboot reboot
to get phone booted in default mode.
Click to expand...
Click to collapse
Yes I have tried that and still nothing shows up on the screen. Device manager still shows it as a kedacom device called android bootloader interface.
WayneSeng said:
Yes I have tried that and still nothing shows up on the screen. Device manager still shows it as a kedacom device called android bootloader interface.
Click to expand...
Click to collapse
Get rid of KEDACOM USB DEVICE DRIVER, what is for Xiaomi devices, AFAIK.
Install the HUAWEI ANDROID USB DRIVER: this driver resolves all USB connection issues between Huawei Android Smartphone / Tablet and Windows 10/8.1/7 PC. It addresses all connection issues, be it transferring files between Huawei device and PC, or debugging over ADB and Fastboot.
jwoegerbauer said:
Get rid of KEDACOM USB DEVICE DRIVER, what is for Xiaomi devices, AFAIK.
Install the HUAWEI ANDROID USB DRIVER: this driver resolves all USB connection issues between Huawei Android Smartphone / Tablet and Windows 10/8.1/7 PC. It addresses all connection issues, be it transferring files between Huawei device and PC, or debugging over ADB and Fastboot.
Click to expand...
Click to collapse
Ok, so I uninstalled the kedacom usb driver and installed the huawei usb drivers. After restarting my laptop and plugging in my phone, device manager shows it as Android phone called Android sooner single adb device. Flashing the board software using Hisilicon image tool gave me error 39.
WayneSeng said:
Flashing the board software using Hisilicon image tool gave me error 39.
Click to expand...
Click to collapse
Can't help you further: don't have a device based on Hisilicon Kirin chipset.
jwoegerbauer said:
Can't help you further: don't have a device based on Hisilicon Kirin chipset.
Click to expand...
Click to collapse
What do you mean? I have a mate 10 pro bla-al00 with a kirin 970 chipset. My issue is not with connection, but with getting the phone into com1 mode and flashing the board firmware in order to unbrick the phone. Here is a tutorial I am following to do this: https://www.youtube.com/watch?v=SJxKH_unwAI&ab_channel=GSMTechZambia
I just can't get the phone into com1 mode. I short the testpoint shown in the video to ground with a piece of wire and all it does is reset the connection and device manager shows an adb device not the com port. Is it the wrong test point I am shorting to ground or am I doing something else wrong? Thanks
WayneSeng said:
What do you mean? I have a mate 10 pro bla-al00 with a kirin 970 chipset. My issue is not with connection, but with getting the phone into com1 mode and flashing the board firmware in order to unbrick the phone. Here is a tutorial I am following to do this:
I just can't get the phone into com1 mode. I short the testpoint shown in the video to ground with a piece of wire and all it does is reset the connection and device manager shows an adb device not the com port. Is it the wrong test point I am shorting to ground or am I doing something else wrong? Thanks
Click to expand...
Click to collapse
If You didnt solve, take a look at this:
HUAWEI MATE 10 HARD BRICK
Hello, i have a hard bricked Huawei mate 10 ALP-l29 with all partitions deleted. Bootloader is locked and no chance to unlock. Tried all services - nothing! Is it any hope? I like this phone damn.
forum.xda-developers.com