Hello XDA Guys,
I have my Memo Pad ME172V broken while I was trieng to Root it and I have used the command "adb reboot bootloader"
so it went down and did not came back again
when I start it it goes directly to this screen " No USB cable connected"
{
"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"
}
and when I connect it to My PC I find in device manager uninstalled device "WM8950 USB Device"
I tried to install a driver for it it only accept Android ADB driver and APX driver but not running as one so I can not use ADB command with it or APX mode
After I install the driver the logo on the screen changes to a green android man with a yellow helmet and written "Ready for download"
I tried everything I know till now
Using power and volumes button in many different combinations
also tried to use Easyflash
changing the USB windows Driver
but no luck at all
PLEASE HELP ME
Thanks
Same issue here man - a friend has given me theirs to try and fix. Did you sort it out?
I've tried multiple Fastboot drivers, but fastboot devices doesn't see anything.
Any Help From XDA Profissionals
Hey Guys, any one here Can help Me
I am not an expert, but does the device still recognise external SD?
If so, maybe this will work:
1. Download a stock util from here https://www.mediafire.com/folder/23ycdy8i4f8mu/ASUS-me172v
(I previously used http://www.mediafire.com/download/3rn6cnzh95va6np/SD_RESTORE_UTIL_20130724_STOCK.ZIP)
2. Format external SD in FAT32 (so at least 4GB microSD card)
3. Extract contents of the stock util zip to the root of the SD
4. Put SD in the device and hope it'll boot from there, so you can restore a previous flash.
Maybe the device has to be rooted for this to work, in that case look here: http://forum.xda-developers.com/showthread.php?t=2216390&page=27 and search Google for Me172vRootUtil_v0.1.zip
I hope this works, and if not, maybe someone else can help you!
hi guys..
same condition.anyone has solve it..? device was working but i only went to fastboot mode then "ready for download"..
Related
SOLVED
HI, All
I have facing out weird problem. Why, when i using adb command to copy file from PC windows to android Devices using Port usb 3.0. Windows will be immediately Blue Screen. Note: in blue screen appears, Bluescreen: Physical Memory Dump
I using Windows 7 (Zotac CPU). But, when i using standart USB port in zotac. Will be running.
Anyone knows, why the problem appears?
Best regard
Solved problem
raditya gumay said:
HI, All
I have facing out weird problem. Why, when i using adb command to copy file from PC windows to android Devices using Port usb 3.0. Windows will be immediately Blue Screen. Note: in blue screen appears, Bluescreen: Physical Memory Dump
I using Windows 7 (Zotac CPU). But, when i using standart USB port in zotac. Will be running.
Anyone knows, why the problem appears?
Best regard
Click to expand...
Click to collapse
Hi, All
This problem is caused because driver in ZOTAC isnt installed properly. When you also facing out this problem. Please make sure your driver installed properly and all your hardware is in good condition.
Best regard
Android All In One Toolkit .. Data Transfer Via ADB
raditya gumay said:
Hi, All
This problem is caused because driver in ZOTAC isnt installed properly. When you also facing out this problem. Please make sure your driver installed properly and all your hardware is in good condition.
Best regard
Click to expand...
Click to collapse
Goood One...
Hii
I Developed an application named "Android All In One Toolkit" With Windows GUI...
1. Data Transfer
{
"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"
}
No Need to type single command
just put path in text box & Press Pull From Device button..
It has feature for fast data transfer over adb without mounting sd card...
It also has many more features that will make your workflow much easier..
Check out my Application
Thread : http://forum.xda-developers.com/showthread.php?t=2494319
Hello there,
my issue is that when i go in bootloader mode, i have a blackscreen, then my phone switch off. The system ui (custom rom Crdroid) and the recovery (orange fox) are working well.
I recognize also that when i reboot, i don't have anymore the MI logo where you have the status of your bootloader when it's unlocked.
More of it, when i plug it on windows , i cannot access to its usb storage (i tried also in mounting it through twrp, but same issue), nothing appears. For example, with an "adb devices" cmd command, no device can be found.
When i check the Windows devices manager, i can see an "unknown usb device" (i tried to force to reinstall drivers on it like the latest google usb driver, but windows refuse it, saying that it has the best and latest one for it).
{
"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"
}
Debugging mode is well enabled
Drivers have been reinstalled (the latest miflashtool install all what is needed)
Nothing appears on my smartphone when i plug it to windows (before i had a notification ot choose in charge mode, usb mode, etc...)
Plug to different usb port has been done without succeess
The phone doesn't appear in miflashtool obv
Restoring a previous backup didn't change the issue (i'm using the custom rom crdroid).
I guess all the things are linked but how i can fix it if i don't have access anymore to my bootloader mode to be able to flash some *.img via fastboot or if i cannot transfer files to my phone to operate in recovery, and more WHAT to do?
I hope you guys, will be able to help. The issue can be really annoying, and stuck me in "no rom update and no transfers of anything possible" situation.
Thank you beforehand
@bonbonboy
Try flashing the firmware through recovery from here https://androidfilehost.com/?fid=11410963190603850663 then reboot device and send it to bootloader via command adb reboot bootloader
It works like a charm!
Mi logo back, adb commands run, usb transfers work and no more error in the device manager.
You saved my day :good::good::good: Thanks a lot !
Recently I have found in my drawer an old Yarvik Noble 97ic+ (Tab09-410) tablet, I got around 2014. Unfortunately it had a broken DC charging connector and the microUSB wasn't enough to kickstart it back to life. So I decided to disassemble the tablet and after some time I managed to charge it and actually turn it on. It booted up and everything. I left it to charge a bit more, but after coming back I found that the tablet no longer boots and all I can get is the "YARVIK" logo stuck on the screen. I have found another customer with exactly the same problem - He charged the tablet for a bit too long and bricked it.
What I can do with the tablet is get it to show with the "adb devices" and I can get it to STOCK recovery, which unfortunately only allows to flash images verified by the manufacturer. I tried all the options in recovery - wiping the cache, data/factory reset and recovery system from backup.
The Yarvik brand, which was a small company in the Netherlands went bankrupt a while ago and there isn't any support or stock firmware images on the web. I only found some dead links on the site arctablet.com, where I also found some users that successfuly flashed a newer android - a rom for Odys Iron CM12.1 lp 5.1.1 (stock is 4.2.2)
When I reboot it into bootloader the screen is completely dark and "lsusb" command shows only the usb port without any device name.
When I tried the "adb reboot-bootloader" command in the console, the device is no longer recognized (with fastboot devices). I assumed it might be because of missing windows drivers, so after trying a whole bunch of them I connected the device to linux with same results. When I reboot it into bootloader the screen is completely dark and "lsusb" command shows only the usb port without any device name. Therefore I cannot install any custom recovery like CWM or TWRP which would allow to flash another than the original Yarvik image.
Is there anyone that could provide the original Yarvik "Tab09-410.img"? Any help is widely appreciated. Thank you for your precious time.
{
"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"
}
Bump. Anyone?
search for odys-iron-jb4.4.2-V1.04
willem
Hello everyone!
This is my first post here so I hope everything I try to explain is according to the rules as far as I read it.
I need to root my Doogee S88 pro mobile since I need test and develop some AR stuff. The standard apps are not accesible by the playstore so I need to bypass that. For doing that I need to root my phone (this is what I read at least).
So... I installed the doggee usb drivers from their website for my phone, usb debugging is activated and OEM is activated as well. I downloaded the most recen platform tools and the usb-cable should be fine since I find the phone with
Code:
adb devices
I execute the following commands:
Code:
adb devices
adb reboot bootloader
fastboot devices
I get the small Fastboot text in the lower left corner. Then if I try to execute
Code:
fastboot flashing unlock
or
fastboot flashing unlock-critical
I only get back <waiting for device>
As said I installed the usb drivers provided by doogee. But: In the device manager I can see the following:
{
"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"
}
Also I periodically (every 10 seconds) hear the sound as if a usb-device is disconnected. Afterwards the device manager refreshes the list.
So... it is a driver issue? I tried updating the drivers but picking manually the folder where driver files are located leads to no result. Automatic search as well. If it is a driver issue - where can I get the appropriate driver files? Thank you for any hint.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Unfortunately that didnt help either. Dunno... What I did was: I switched to my Lnux OS and over there it worked out of the box (only needed to install adb and fastboot from repositories).
Tablet name: Toshiba Excite AT10-A-104
Release date: 12/17/2013
Android version: 4.2.1
CPU: tostab12BL (armv7l 32-bit)
GPU: nVidia Tegra 3
I would like to access FASTBOOT mode, but I can't. As I said in the title, I never did root or factory reset or flashed anything, so tablet had always this "protection".
This is what I tried:
1) power_button + volume_down => tablet just restarts
2) USB debugging turned on > command prompt > adb reboot bootloader => tablet just restarts
But I can enter Recovery mode:
{
"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"
}
If you have any idea or if you can send me tutorial how can I enter FASTBOOT, please help. I did a lot of research but can't find solution.
consider the fact fastboot mode is simply removed by OEM.
curious what's behind the last entry in recovery menu?
aIecxs said:
consider the fact fastboot mode is simply removed by OEM.
curious what's behind the last entry in recovery menu?
Click to expand...
Click to collapse
Thank you, I thought as well that this is a dead end. Last option throws error (SD card is not mounted), don't know what it does.
guesswork, that's same option as "apply update from external storage" but it also allows unsigned update.zip (like custom ROM)?
what you could try is root with SuperSU. download SR3-SuperSU-v2.79-SR3-20170114223742.zip rename it update.zip and copy to MicroSD Card.
now insert SD Card into tablet and try the last option "apply customization from external storage"
in case that succeeds you have rooted your tablet without the need of fastboot (if that's what you're interested in). However, please note there is no way to undo rooting.
I wanted to try things out, but since I don't have fastboot mode access then I will just try to sell tablet, thanks for help.
fastboot is very limited mode, mainly used for flashing. this can be achieved with other tools like tegra-flash, nvflash.
furthermore on such ancient device there is good chance bootloader is shipped unlocked