[Completed] Need to recover files from (mostly) dead Motorola XT901 - XDA Assist

I am a PC technician and don't know much about phones. A customer brought me in a mostly dead phone and wants pictures of his kids recovered. I believe this is probably possible given the state. I want to give enough information without overloading anyone looking to help, so I will put it in sections.
What I know about the phone:
I never saw it working and I'm not a phone guy. The back says the model is XT901. This customer is not a tech, so only push updates would have likely been done., if even those were done. It came in roughly 2 weeks ago. That is pretty much the extent of what I know about the phone and its OS.
What the problem is:
When booting normally the Motorola logo comes up with the swirling blue around it. It stays on that screen forever.
What the phone can do:
I can get into a couple different menu systems with different key presses (which I don't exactly remember right now. It's kind of trial and error to get into the one I want). The less helpful menu has a "Recovery" option which just makes the phone boot to the swirling logo again. By retrying with different keypress combinations I can get it to show the android on his back with the exclamation mark. From there I can reboot into a different menu, where I found QC Diag, among other things.
What I need to do:
I need to connect the phone to a Windows 7 Professional 64 bit computer to recover, especially, pictures of his kid that he didn't have backed up.
The problem I ran into:
Four devices do show up in the device manager as "Unknown device". I did manage to get the QC Diag port set up following the instructions here:
googlebought.blogspot.com
/2014/12/motorola-qc-diagnostic-driver.html (separated because I can't post links, but the information might be important)
I used the PID listed on the page since I have no idea what to change it to or even if I need to change it, but it did seem to work for one unknown device. I then right-clicked on each of the 4 "Unknown" devices and browsed to that folder. One was detected and updated, the Motorola QC Diag Port on COM3. This did not make a drive letter show up as I had hoped.
What I have tried:
Downloading a few dozen drivers to get all 4 of these devices detected, starting with the latest standard drivers for the phone, Motorola Device Manager 2.5.4 and Motorola Mobile Drivers Installation 6.4.0. This is how I got to just 4 devices listed as "Unknown". Of course, there are currently only 3 unknown since getting the QC Diag port going.
My technical abilities:
I have been a PC tech for about 15 years and am pretty good at it. I have rooted Android devices before, but frankly that's just "download a program, push a button". I am utterly unskilled in Android, but I can follow even complicated instructions.
I am hoping that there is a mode I can go into (I believe I've tried all I can get into) or a driver I can install which will allow me to browse the directories on the phone. I realize this is more complicated than it sounds because of the difference in file systems. I would imagine that since I can see these devices in certain modes this is probably possible.
Thank you in advance for any help you can offer. I'm sorry it's long-winded, but I wanted to be thorough. Hopefully it's organized enough that you can skip over any information you don't need.

XDA Visitor said:
I am a PC technician and don't know much about phones. A customer brought me in a mostly dead phone and wants pictures of his kids recovered. I believe this is probably possible given the state. I want to give enough information without overloading anyone looking to help, so I will put it in sections.
What I know about the phone:
I never saw it working and I'm not a phone guy. The back says the model is XT901. This customer is not a tech, so only push updates would have likely been done., if even those were done. It came in roughly 2 weeks ago. That is pretty much the extent of what I know about the phone and its OS.
What the problem is:
When booting normally the Motorola logo comes up with the swirling blue around it. It stays on that screen forever.
What the phone can do:
I can get into a couple different menu systems with different key presses (which I don't exactly remember right now. It's kind of trial and error to get into the one I want). The less helpful menu has a "Recovery" option which just makes the phone boot to the swirling logo again. By retrying with different keypress combinations I can get it to show the android on his back with the exclamation mark. From there I can reboot into a different menu, where I found QC Diag, among other things.
What I need to do:
I need to connect the phone to a Windows 7 Professional 64 bit computer to recover, especially, pictures of his kid that he didn't have backed up.
The problem I ran into:
Four devices do show up in the device manager as "Unknown device". I did manage to get the QC Diag port set up following the instructions here:
googlebought.blogspot.com
/2014/12/motorola-qc-diagnostic-driver.html (separated because I can't post links, but the information might be important)
I used the PID listed on the page since I have no idea what to change it to or even if I need to change it, but it did seem to work for one unknown device. I then right-clicked on each of the 4 "Unknown" devices and browsed to that folder. One was detected and updated, the Motorola QC Diag Port on COM3. This did not make a drive letter show up as I had hoped.
What I have tried:
Downloading a few dozen drivers to get all 4 of these devices detected, starting with the latest standard drivers for the phone, Motorola Device Manager 2.5.4 and Motorola Mobile Drivers Installation 6.4.0. This is how I got to just 4 devices listed as "Unknown". Of course, there are currently only 3 unknown since getting the QC Diag port going.
My technical abilities:
I have been a PC tech for about 15 years and am pretty good at it. I have rooted Android devices before, but frankly that's just "download a program, push a button". I am utterly unskilled in Android, but I can follow even complicated instructions.
I am hoping that there is a mode I can go into (I believe I've tried all I can get into) or a driver I can install which will allow me to browse the directories on the phone. I realize this is more complicated than it sounds because of the difference in file systems. I would imagine that since I can see these devices in certain modes this is probably possible.
Thank you in advance for any help you can offer. I'm sorry it's long-winded, but I wanted to be thorough. Hopefully it's organized enough that you can skip over any information you don't need.
Click to expand...
Click to collapse
Hi and welcome to XDA.
Your device has a dedicated forum here but it's very quiet as it isn't the most popular phonein the world.
You can try posting your query there or in: Android Q&A,Help and Troubleshooting.
You'll have to create an account to post in the main forums.
Good luck

Related

[Q] need help with UnBrickableResurrectorR40

I need some help. I will set up the scenario first. My Cap has had the unbrickmod performed on it about 8 months ago. I had the battery fall out ib the middle of a flash. I was getting the phone /computer "you screwed up a firmware install" animation. I tried to get it cleared up with Odin and now it is black screen no matter what I try. Can't get download, or recovery, and the usb jig won't even get it into download. I am completely unschooled and self taught with pc and phones and I think I have done pretty well. Now, I have taken another big step and after reading up on what to do next, I installed successfully, Ubuntu in my laptop (xp pro)and I can dual o.s. or boot either o.s. individually and everything seems to work fine. I downloaded UnBrickResrectR40, HIBL.zip, and java jre7.0.5. Ihave no clue about Linux or command lines,but after reading a million different claims on how to install these files i was finally able to get the java installed. But, I can't get the unbrickres file to install. I always get an error saying file not found by regex. Now I have copies in downloads,desktop, home, files, and have changed permissions and types(jar,javaw.exe,zip.gz) and still nothing. No forums or help pages help. They all give directions as if you know what you are doing already. They must figure if you got this far you are a tech or a dev, not a noob electrician who can't even type. I need some seriously slow,detailed,step by step,hand holding through this one, if someone has the patience. Back to the phone. The only thing that shows any life in the phone at all is when it is plugged into my laptop. It doesn't show up anywhere but under device manager. It shows under "universal serial bus devices" as, SEC S5PC 110 Test B/D , location 0,device is working properly,driver provider-libusb.org, driver date-7-13-2009,driver version-6.7.7600.16385, not digitally signed. That is it. I need some direction. What do I do now? Hopefully someone feels adventurous.Thanks
khkaiser13 said:
I need some help. I will set up the scenario first. My Cap has had the unbrickmod performed on it about 8 months ago. I had the battery fall out ib the middle of a flash. I was getting the phone /computer "you screwed up a firmware install" animation. I tried to get it cleared up with Odin and now it is black screen no matter what I try. Can't get download, or recovery, and the usb jig won't even get it into download. I am completely unschooled and self taught with pc and phones and I think I have done pretty well. Now, I have taken another big step and after reading up on what to do next, I installed successfully, Ubuntu in my laptop (xp pro)and I can dual o.s. or boot either o.s. individually and everything seems to work fine. I downloaded UnBrickResrectR40, HIBL.zip, and java jre7.0.5. Ihave no clue about Linux or command lines,but after reading a million different claims on how to install these files i was finally able to get the java installed. But, I can't get the unbrickres file to install. I always get an error saying file not found by regex. Now I have copies in downloads,desktop, home, files, and have changed permissions and types(jar,javaw.exe,zip.gz) and still nothing. No forums or help pages help. They all give directions as if you know what you are doing already. They must figure if you got this far you are a tech or a dev, not a noob electrician who can't even type. I need some seriously slow,detailed,step by step,hand holding through this one, if someone has the patience. Back to the phone. The only thing that shows any life in the phone at all is when it is plugged into my laptop. It doesn't show up anywhere but under device manager. It shows under "universal serial bus devices" as, SEC S5PC 110 Test B/D , location 0,device is working properly,driver provider-libusb.org, driver date-7-13-2009,driver version-6.7.7600.16385, not digitally signed. That is it. I need some direction. What do I do now? Hopefully someone feels adventurous.Thanks
Click to expand...
Click to collapse
Have you tried the Windows tool Windows32DriversAndCommandLineApp.zip ?
http://forum.xda-developers.com/showthread.php?t=1242466
Thanks for the advice
Thanks Silvertag, I appreciate the fact that you even read my post. I was running late for work, but wanted to get something on the boards.
I will check out the link you suggested. Much appreciated.

[Q] Huawei Y201 NFC U8666n-1 trouble

OK so I recently switched this neat, cheap and decent entry phone, and of course wanted to root and unlock the bootloader.
Using the technique outlined in http://forum.xda-developers.com/showthread.php?t=2066887 "[ROOT][CWM] Huawei Ascend Y201 Pro U8666" I managed to happily root the device. Meaning I could install droidwall and adfree, and uninstall one or two of the annoying Huawei apps. (Surprisingly there are less Vendor apps on this than the previous Ideos U8150 I had.)
So happy that that worked, I thought I would go to the next stage and unlock the boot loader, in preparation for maybe installing clockworkmod recovery. And eventually a ROM if I could find one that looked "safe" and sound.
Cranking up the "UnlockBootloader.exe" as before and clicking the unlock BOOTLOADER initiated something on my phone... However when I switched off my phone preparatory to rebooting, I found what I guess to be a bricked/borked device.
There's no vibrate, no flash on screen, no logo, no pink screen that other people talk about in the few reports I have found around the web. Just that the lower backlit soft buttons flash ten times and then nothing else happens. I can't even find information about what this obviously low level failure message means...
As you can guess, I have tried all sorts of things to get it going: battery removal; powering from USB while botting; any and all of the key press holds for boot; all to the same effect. Have tried several times to find anything similar on the net and can't seem to find anything similar. Especially the ten flash indicator
So my question is "Is this an absolute sign that the device is bricked?" I guess I could try to play the innocent and send it back under warranty, but I guess someone will realise it was my fault. Unless a memory failure happened at the exact time I was flashing/unlocking...
And a warning that same device owners should be careful when following the guide. I'm pretty sure I had everything as outlined. I'm running XP, didn't have it mounted, had fastboot off, etc... Although now its hard to check on the device to see if that was the case
and also
I should also perhaps add that before using UnblockBootLoader with root success, I tried the ICS "adb restore" directory traversal vulnerability, which is part of Root_with_restore, and was unsuccessful.
And that there's no life reported at a low, USB device level to my linux kernel, when plugged in now. So I can't even try a firmware patch using adb etc.
Of course I can't post a relevant cautionary note into the above mentioned thread, as I have yet to reach the 10 post milestone mark, enabling me to post in that section...
Hi,
Sorry for opening an old thread, have the same issue and just wanted to know if you manged to resolve this or it you just took it back to the shop?
Regard
No solution
No - I never managed to work out or find a solution. I just got a new one, and only went as far as the root'ing stage.
I have never seen an applicable ROM for this device anyway, so I guess it wasn't too much of an issue. And root'ing to get those crucial management apps installed, and also being able to remove some Huawei "cruft" is the real thing you need.

[HELP] Cannot factory reset a Kyocera Hydro Wave (C6740N) on Metro PCS

Greetings to all the developers and registered users on this site... Yes, this is my first post, but I read here pretty often and I used the search function, trust me! Seriously, I've tried all I could and I am at my wits end, but this is technology, we can't let it own us, we gotta continue owning it and that's what online communities like xda help us do, so thanks for all your past, present, and future contributions here. So I got this Metro PCS Kyocera Hydro Wave (C6740N) that I can't factory reset for a number of reasons, but mainly because I believe that there is either no boot-loader or no recovery partition as a result of Metro PCS flashing the ROM...
Anyway, lets get to the juice:
- Device powers on/off, but no combo of Vol -/+ and Power buttons bring up a recovery menu or anything (holding any combo down just boot-loops)
- Device has no SIM and no micro SD card, and the battery is not removable
- Device is locked... Like, pattern-locked/google account info/too many attempts/yada yada yada
- Device has no data and no WiFi connection active, so I could not use the google account to get past the lockscreen
- Device does not have USB debugging enabled/Google drivers for ADB do not work (Windows 7 auto-detects when I plug in the phone and installs a generic Microsoft driver which cannot be removed even after uninstalling the device, and also I pointed the Device Manager to the correct Google drivers I installed with the Android SDK Tools, as well as the Samsung Naked Universal Drivers I found on this forum, and Kyocera ADB drivers I found through Google which all failed, Windows returned a message stating that the most up-to-date or best driver for this device is already installed)
What I've tried (everything possible really):
- Hard reset/Recovery from phone: FAILED
- Connect to Linux and install ADB, then tried running the adb shell, adb devices, fastboot devices, etc but phone not detected: FAILED
- Connect to Windows 7 and install ADB (Android SDK Tools), I literally checked every single box and installed Platform-tools, google drivers, everything, got to the command prompt as admin, cd to the ADB directory, ran same commands as in linux, also tried commands on several forums and posts like adb shell rm /data/system/gesture.key to remove the lock but everything: FAILED
- Connect to Windows 7 and attempt to install proper drivers using RootGenius, MoboRobo, PDAnet, and several other suggestions which all were oblivious/unable to detect the device despite Windows recognizing it, so they all: FAILED
- Connect to Windows 7 and attempt running ADB through a Cygwin terminal, but the command "sudo" was not recognized/not valid, so: FAILED
- Connect to Windows 7 and use XRYViewer to extract data from the phone, possibly to see the system files and get an actual understanding of what everybody is saying you need to mount from the recovery partition, but no clue how to use this, since I can't find an XRY file in the internal storage, so: FAILED
- Connect to Windows 7 and access data/recover data from device using "Wondershare Dr.Fone for Android" and "iLike Android Data Recovery Pro" but both programs instructed me to enable USB Debugging, which is not possible, so the both also: FAILED
Despite this being my first post, I have scoured the forums here in addition to every other forum and webpage regarding this issue as well... There just isn't much about this phone except negative reviews, and I have come to the conclusion that on this particular model phone, I am out of options... I have a paperweight... I'm not very familiar with Android... So please correct me if I'm wrong...
Any input?
I'm curious if there are any options at this point, I have been trying to get through to this phone on several computers for the past couple days and it is frustrating me... Any input from the community would be much appreciated...
Mojo2XL, I guess you did not find an answer?
Mojo2XL said:
I'm curious if there are any options at this point, I have been trying to get through to this phone on several computers for the past couple days and it is frustrating me... Any input from the community would be much appreciated...
Click to expand...
Click to collapse
I have the exact same problem and it appears I am several months after your post. I just want to use this device as an e-reader but like you, I cannot get anything to recognize it!~
eenuckols said:
I have the exact same problem and it appears I am several months after your post. I just want to use this device as an e-reader but like you, I cannot get anything to recognize it!~
Click to expand...
Click to collapse
may be this:
*2767*3855# - Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
I found code in internet, but may be it works? can't check, my "wave" comes to me from USA by post for a few weeks..
barabeka said:
may be this:
*2767*3855# - Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
I found code in internet, but may be it works? can't check, my "wave" comes to me from USA by post for a few weeks..
Click to expand...
Click to collapse
doesnt work.. you can only get to emergency dialer which can only b used to make emergency calls
elliwigy said:
doesnt work.. you can only get to emergency dialer which can only b used to make emergency calls
Click to expand...
Click to collapse
okay. i will try something, when my phone will come. is your Wave locked?
barabeka said:
okay. i will try something, when my phone will come. is your Wave locked?
Click to expand...
Click to collapse
i bought another phone and they threw it in free but it has a pin code lock so i cant even get to google screen to bypass frp as im stuck at pin lockscreen and these darnphones have no recovery..
i doubt ull figure out a way as im real savvy with this stuff lol theres no recovery to boot into in order to reset and no way to update tje phone wothout knowing the pin code
any luck? i cant believe this thing is this locked down. makes apple look like chils play
warriorpluto said:
any luck? i cant believe this thing is this locked down. makes apple look like chils play
Click to expand...
Click to collapse
i believe it can be done with a pc
Did you happen to get the files the other member posted that was only available for eight days?
Mojo2XL - Sort of.
I saw a youtub video (sorry no link) that says there was a OTA update that changed the phone's firmware that solved all the problems mentioned here. Thing is I have no carrier and cannot find this new firmware, but, I am still hunting....
​
eenuckols said:
I have the exact same problem and it appears I am several months after your post. I just want to use this device as an e-reader but like you, I cannot get anything to recognize it!~
Click to expand...
Click to collapse
I'm having the same problem, I have been trying to get this thing to hard reset for a week now. There has to be a way to reset this Hydro Wave.. Has anyone dealt with this thing?
Hey hold the buttons as follows volume- & power at the exact same time while your phone is off be warned if you phone was preowned you need the goole account originally activeated with that phone if you do not have that then your in the same vote as me i cant remember any of my gmail account info to my wave from when i had it active I have litterally tried every thing to recover the info and i still can't recover it
WhiteWolf77 said:
Hey hold the buttons as follows volume- & power at the exact same time while your phone is off be warned if you phone was preowned you need the goole account originally activeated with that phone if you do not have that then your in the same vote as me i cant remember any of my gmail account info to my wave from when i had it active I have litterally tried every thing to recover the info and i still can't recover it
Click to expand...
Click to collapse
That doesn't work on this phone the hydro wave from AT&T has factory reset protection so it cannot be reset using the volume down and power button reset
Any update?
dannybz said:
Any update?
Click to expand...
Click to collapse
let me work on this, been trying to master as many FRP bypasses as i can. I don't have the device but a client is in the same boat
I accidentally stumbled upon a something weird. I've managed to make the camera crash to the home screen somehow. I believe this was a result of holding both volume buttons and opening numerous menus while using the camera. My guess is that it overloads it after a certain amount of times and causes it to crash. I've gotten the android UI to crash like this before. I will try to recreate the scenario and update you guys on this. it's on a Kyocera Hydro Wave. Running android 5.0 I believe. Try going wild until the phone starts to lag. eventually stuff will crash and the lock screen may go with it. use this to your advantage and enable USB debugging as quickly as possible because it will reset itself after about 30 seconds. Someone else on YouTube has recently told me that it worked for them. I would look into doing that.
PhoneScrambler said:
I accidentally stumbled upon a something weird. I've managed to make the camera crash to the home screen somehow. I believe this was a result of holding both volume buttons and opening numerous menus while using the camera. My guess is that it overloads it after a certain amount of times and causes it to crash. I've gotten the android UI to crash like this before. I will try to recreate the scenario and update you guys on this. it's on a Kyocera Hydro Wave. Running android 5.0 I believe. Try going wild until the phone starts to lag. eventually stuff will crash and the lock screen may go with it. use this to your advantage and enable USB debugging as quickly as possible because it will reset itself after about 30 seconds. Someone else on YouTube has recently told me that it worked for them. I would look into doing that.
Click to expand...
Click to collapse
Is there anything a little more realistic possible? Lol, I can see an update available, can't connect to WiFi to update haha. The stuff they lock these phones with anymore i swear
I'm new to this forum, but NOT new to this site . I have visited here on numerous occasions seeking the help that needed . With that being said, I would like to offer a Bonafide, Tried and True way to factory reset the Kyocera Hydrowave . I KNOW that this work's for I have done in on numerous occasions for a friend of mine that works for Metro PCS ....
Step One: Completely power off the phone .
Step Two: Hold the Power AND Volume DOWN Buttons SIMULTANEOUSLY .
Step Three: DO NOT release any buttons, even when you get to the Boot Menu . (Very Important, If you don't do it right, you have to start all over lol ) .
Step Four: Once inside the Boot Menu, ONLY release the Power Button; or the Boot Menu will close and you have to start all over again .
Step Five: Use the Volume Down Button to Highlight the Wipe/Factory Reset Option .
Step Six: Use the Power Button to Select the option .
Step Seven: Watch the bottom of the screen for the progress, and then use the Volume Up Button to restart .
And there you have it . I hope that this helps out SOMEONE out there, because I feel good giving back for the help that I have received on here .
PS.( If you would like for me to post a Video Tutorial on this, can someone please tell me how to post the Video; I guess by me being a Newbie on here, I'm not allowed to do as of yet ) . If Anyone needs to contact me, as I'm not on here very often, my email is [email protected] .
LilAnt530 said:
Is there anything a little more realistic possible? Lol, I can see an update available, can't connect to WiFi to update haha. The stuff they lock these phones with anymore i swear
Click to expand...
Click to collapse
As unrealistic as it may sound it actually works Trust me on this. its similar to the LG attack which... is nothing but entering a long password.
betanews.com/2015/09/16/bypass-the-android-lollipop-lockscreen-by-entering-a-really-long-password
Just give it a go. it already worked for one dude on youtube. it takes a while but it honestly works. If you can get it, update the phone as soon as possible turn the screen timeout off and let it update. when the phone resets the update will install and you will be able to factory reset.
I mean it couldn't hurt. if you're locked out with no factory reset and ADB tools won't work what else can you do?

[Completed] Jide Ultratablet ADB-Fastboot Recovery Flash Problem

Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
XDA Visitor said:
Where to begin? Logic would dictate, the beginning.
I'll do my best to be brief with the backstory.
Months ago I ordered a Jide Ultratablet to use as my portable workhorse. At first things were peachy until a rather monumental lag began to manifest every 15-45 seconds. It made the device impossible to utilize in any productive fashion, so I contacted Jide and opened up a support ticket. After months (in no way an exaggeration) of barely responsive correspondence, during which I sent them a video to demonstrate the problem, they finally came back to me with an email containing a link to a compressed folder containing the Remix 2.0 images, and also a link to a rather vague and complicated tutorial on how to flash Remix 1.5 manually to a device. (In fact, I tried to include a link to the tutorial, but I am unable to since I haven't posted to the forum enough. I am happy to PM it or email it to anyone who might like to help) I can only assume I am meant to apply the same logic to the Remix 2.0 files they sent me. Seemed a bit dicey at first glance, but while I'm by no means an expert, I'm no slouch in this arena and I'm a very quick study.
Now, on to the proverbial meat and potatoes:
If you were able to contact me for a link to the tutorial in question, you will have undoubtedly seen that they indicate one should use ADB-Fastboot as a means to flash the recovery image. No real surprises there. I have ADB and Fastboot installed on my PC (Windows 10). I also have the ADB drivers installed and have confirmed the addition to my PATH. (eg: ;C:\ADB) I can also confirm that it is working fine since I am able to pull up a terminal and issue the ADB command and it gives me the usual wall of commands. The problem is that my device (Ultratablet) is not being seen by ADB. I have checked my USB drivers and they are all up to date and installed properly. My PC sees the device no problem and there is no indication of any sort of connection error. I've also tried different cables and ports. Yet, I can't access it via ADB and thus am unable to issue commands to my device such as "adb reboot bootloader" or "fastboot reboot-bootloader".
My next logical approach was to attempt forcing the device into fastboot mode using the hardware button combination, which is not listed specifically for the Ultratablet anywhere, I might add. (Power key + Volume up) It brings me to a boot options menu with the selections "Continue/Fastboot Protocol/Recovery Kernel/Reboot/Poweroff/Forced Recovery". Ateempting to select Fastboot Protocol causes the display to shut off for a moment, the device to vibrate once, and then the display to turn back on back at the same menu full of selections.
So, in summary, I am expected to flash the device using fastboot and yet I can't even get the device into fastboot mode, let alone issue commands from my PC terminal. As I highlighted near the beginning, teh Jide support team is incredibly unresponsive and not overly helpful. I have notified them of this same set of issues, but I don't expect to hear back in any expedient fashion and I thought one of the mighty members here on XDA might be able to help me come up with a next step in the meantime. I'd cerainly love to be able to use my shiny new tablet.
In any case, thank you for your time.
Kind regards.
Shaiden
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
First, you'll need to create an account so you can post in the other sections.
After you have done that, you can post your questions and ask the experts here:
http://forum.xda-developers.com/android/help
You're sure to receive quality answers there.
Good luck and welcome to XDA!

No driver no support

I have a AudioVox T852 tablet that is stuck on logo, there's no button combo to enter recovery only thing it has is a reset pin hole tried numerous times and nothing my computer recognizes the tablet but can't find driver.. I reached out to the company and asked for the USB drivers and firmware if possible.. There reply was "Sorry to hear your having trouble but this tablet is no longer supported" to which I replied " No longer supported so **** me right" so how can I or what drivers can I install so I can try and fix it.. Thanks
xOwNx said:
I have a AudioVox T852 tablet that is stuck on logo,.........
Click to expand...
Click to collapse
I don't have this device and I personally can't locate any real threads for this as well...
The best thing I can do is to provide you with the following links that will, hopefully, be helpful to you.
https://voxxintl.zendesk.com/hc/en-...the-Audiovox-Tablets-T752-T852-T852SBK-T852PK
http://www.fixya.com/support/t26488427-audiovox_tablet_model_t_852_stuck
The following is a Google Search link that's specific for searching the fixya website that seems to have allot of results as well.
https://www.google.com/search?q="Audiovox T852" site:www.fixya.com
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
Yeah ive been up and down those links every link but cant do anything without the drivers i tried force installing drivers that come close but nothing. I was even thinking of writing my own usb drivers for the heck of it but ill check every other option before heading down that road ...thanks anyways
xOwNx said:
Yeah ive been up and down those links every link but cant do anything without the drivers i tried force installing drivers that come close but nothing. I was even thinking of writing my own usb drivers for the heck of it but ill check every other option before heading down that road ...thanks anyways
Click to expand...
Click to collapse
When you say that you tried force installing the drivers and came close but nothing, what do you mean "came close" exactly?
Do you have the driver install .exe to install them? When you install them, does it say they were successfully installed but you still get nothing? If so, you may have to manually configure the driver through device manager. I've had to do this with a couple of tablets to get PC to recognize the device while in fastboot.
Sent from my LGL84VL using Tapatalk
Just to be clear theres no drivers for Audiovox T852 tablet at all, even the damm company that makes them refuse to hand it over. They said since its not supported anymore anything and everything for the Audiovox T852 is deleted out there system (when does anyone actually completely delete anything?Right?) Now when i say close i mean i did force install a USB MTP Driver but with a error 10 something along service or drivers could not start. My pc reconized it T852 but with a ? But anytype of commands or software i use to try and anything just wont work without The Damm drivers.. o 1 more thing the T852 also has no fastboot mode or recovery to get into..
xOwNx said:
Just to be clear theres no drivers for Audiovox T852 tablet at all, even the damm company that makes them refuse to hand it over. They said since its not supported anymore anything and everything for the Audiovox T852 is deleted out there system (when does anyone actually completely delete anything?Right[emoji19]) Now when i say close i mean i did force install a USB MTP Driver but with a error 10 something along service or drivers could not start. My pc reconized it T852 but with a ? But anytype of commands or software i use to try and anything just wont work without The Damm drivers.. o 1 more thing the T852 also has no fastboot mode or recovery to get into..
Click to expand...
Click to collapse
It's hard to believe that the drivers haven't been stored/posted somewhere else by someone using some kind of online file sharing site or forum, even if they weren't kept by the manufacturer.
I looked up the specs for your device, the specs say that you have an Amlogic Cortex A9 CPU architecture, have you tried drivers for other devices that use Amlogic Cortex A9 processor?
Also, when in device manager, try selecting the device on the list then right click then select "properties" then select the "details" tab then click on the drop down menu under "property" that shows "device description" by default then select "hardware IDs", write down the ID values, it will be more than one line of ID codes, then do some Google searches to find drivers for those ID codes? Sometimes that will find drivers that work for those hardware IDs, even if the drivers weren't specifically built or offered by the manufacturer of your hardware. Sometimes installing a driver that matches the hardware ID gets that particular hardware ID to work and gets it recognized by the system but then the system detects another "layer" of hardware with its own hardware ID that also needs a driver. Sometimes, if you go layer by layer installing drivers for each new hardware ID that gets exposed by the last driver that you installed, you can eventually get to where each "layer" is recognized, if you are lucky enough to find drivers for each hardware ID layer, you get to where the device is completely recognized correctly. I've done this before to get hardware recognized when I had nothing to go by to identify the device or component.
Sent from my LGL84VL using Tapatalk
Dude when I'm telling you I did it all even the darn hardware id's get 0 zero nothing nada in google search results.. That's why I said I'm down to writing creating my OWN drivers I've litterly did the ins and outs and then some.. I just decided to post my problems to see what comes about if I get some sorta guidance it's a plus if I don't no biggy. Ive been at it since the first flip phones came out changing blacklisted imei with cdma workshop qpst fixing tablets computers cracking software but every so often I come across these Chinese tablets that have little to no support and I just put them aside, but nope not this time I'm seeing this issue all the way through hopefully with the help of second to none XDA COMMUNITY.... ?
xOwNx said:
Dude when I'm telling you I did it all even the darn hardware id's get 0 zero nothing nada in google search results.. That's why I said I'm down to writing creating my OWN drivers I've litterly did the ins and outs and then some.. I just decided to post my problems to see what comes about if I get some sorta guidance it's a plus if I don't no biggy. Ive been at it since the first flip phones came out changing blacklisted imei with cdma workshop qpst fixing tablets computers cracking software but every so often I come across these Chinese tablets that have little to no support and I just put them aside, but nope not this time I'm seeing this issue all the way through hopefully with the help of second to none XDA COMMUNITY.... [emoji108]
Click to expand...
Click to collapse
I know it's frustrating, I can't stand the crap that comes with messing with Chinese devices. You asked, I posted everything I could think of.
Also, I wouldn't brag about changing a blacklisted IMEI and cracking software here at XDA. That kind of thing isn't tolerated here because it's illegal in most places. Guys that do that kind of thing around here get banned from the site.
Sent from my LGL84VL using Tapatalk
I wasn't bragging is was intended so that time isn't wasted with noobish, common sense, or beginners replys that's all, but my fault going over what I said i definitely missed the point I wanted to get across..

Categories

Resources