Key driver not found...Booting OS - M.O.J.O. General

Hi,
Having a problem with the Mojo - I wiped the OS and am back to square one. The only problem is I can't launch TWRP on the device because the device is only detected on device manager as "Fastboot" with an exclamation mark.
When I try to adb devices - nothing shows up
Any help would be greatly appreciated

Related

[HELP] my KF freeze on bootscreen!!!

Hi guys!
I have a problem with my kindle fire, brought 2 days ago...
Yesterday I've tried to root my device...and I think that I've done (because on my Fire, there was the superuser app)...but after that, I've tried to put C7 rom but the tutorial says that before this, I need install TWRP.
I've tried to install TWRP with KindleFireUtility...but after 3 steps, the program reboot my device and when it restart, remain fixed on the bootscreen (the black-screen with text: "Kindle Fire" and NO yellow triangle)
I've tried to use CMD but the problem is one: never command (on cmd) find my device...beacause also the pc NOT FIND DEVICE!!!
Please help me...I'm very desperate
PS. sorry for my poor english
you have to update the driver at this point:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
and from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and from the dev of kfu:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
b63 said:
you have to update the driver at this point:
http://forum.xda-developers.com/showpost.php?p=21720811&postcount=41
Click to expand...
Click to collapse
I can't do this! Because when I plug-in my device on PC, windows XP not recognize the device!!!
So, if I go on device manager (on pc) in the list of devices...there isn't my Kindle Fire...and then I can't re-install drivers!!
it's not kindle fire - look for "android phone" or "unknown device"
i've only find "device USB unknow" (this a translation, because I'm italian and xp says: "Periferica USB non riconosciuta").
I've uninstall this, I've restart XP and I've plug-in my device...and I try to install the driver but when I select the .ini file, there is no good for this!
which ini ? which driver set ? do you use the drivers from kfu 0.9.2 ? if yes - fine
the right driver installation file is android_winusb.inf (not the ini) in the drivers\kindle folder of kfu
nothing!
1) I plug-in the fire
2) XP says that is an unknow device
3) I open the device manager. In the "USB root HUB" there is a "Unknow Device". DoubleClick that open a window of Property.
4) I click on Driver tab and click on "Upgrade Driver". Choose the path (folder driver of kfu) and select "android_winusb.inf"...but there is a message box "The specified location does not contain information about the hardware".
So...
gave you a pm some time ago ...
I had a similar problem while trying to install TWRP the first time via KFU except I was stuck at the yellow triangle and not the Kindle Fire screen.
First I replaced run.bat in the KFU folder with the one from this post because my Kindle was 6.2.2. Next I installed the drivers for my uknown device in device manager both by pointing the unknown device to where I saved android_winusb.inf and also ran the install_drivers.bat. I got an error saying they could not install.
Next, I followed the steps here
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
Click to expand...
Click to collapse
and when I rebooted my Kindle, it booted normally and appeared as Kindle in Device Manager. So despite KFU not detecting my device, and the drivers giving me problems, I was still able to issue the command in KFU for normal boot mode and held the power button for 30 seconds and it was back to normal. I hope this helps.
nothing...I'm desperate...
I Think that the principal trouble are DRIVERS! In fact, when I plugin my device, now XP (another pc with xp) see the device but tell me that the device is unknow...
So, I try to install driver from (extras/google/usb_driver/android_winusb.inf) but xp says that "there is no information about hardware".
after 48h, now XP see my device and I reinstall the driver (android_usb.inf).
but...now I've anothere trouble: WHY the Kindle Fire Unbrick not see my KF?
While KFU see my device and show me this:
adb status: online
adb rooted: no
boot status: unknow
but if I open CMD and write "adb devices"...no device found!
What Can I Do?

[Q] Gionee Elife E7 bricked without reason

Hello everyone! This is my first thread here. I hope you can help me and that maybe in the future I can also help somebody here. I tell you my problem and I hope it's not to confusing.
I have a problem with my gionee elife e7 (32GB). The problem occured without a obvious reason. My girlfriend was using the phone which was running android 4.4 Kitkat (stock). So one day it just stopped booting. There is just a black screen and I can't enter recovery mode or factory mode by pressing buttons on the device. At least I tried unsuccessfully. Anyway the device vibrates If I hold the power button and also it is recognized by my PC. This is why I am hoping to be able to restore the smartphone again by flashing a new rom.
The device is recognized as "gionee android composite adb interface". I tried to flash the ROM with the gionee download tool but unfortunately the tool says "open COM ports fails". So I tried to deinstall all COM-ports on my PC without this problem going away. Sometimes - I don't know why - The tool doesn't show this error. But then the tool doesn't find my device when I plug it in.
Also I tried to get access to the Smartphone via ADB or Fastboot without luck. The PC didn't recognize the device.
I tried everything with Windows 8.1, Windows 7 and Windows XP via Virtualbox.
All in all I have no idea left about how to repair the smartphone. I hope some of you can help me with this. Does anybody know how I can access the smartphone again and reinstall the Android System on it?
Thank you very much
try pressing the power plus volume + and volume - simultaneously, release only the power when the phone vibrates and wait bout 10 secs pressing the volume keys. Then release them and plug the phone to the PC and check if the QLoader driver is loaded. If so try flashing in Emergency Mode.
Let me know how it went...
tried
Wrong description!
Thank you for your help! The result was that the device vibrates constantly every 3 sconds after I stop to press the powerbutton und keep pressing the Volume + and - buttons together. As soon as I release them it stops vibrating. In the Device manager it still shows the "gionee android composite adb interface".
I tried to do the same with the device plugged into a USB. What I then recognized was that the Status-LED was blinking red every second . After 10 seconds of pressing the buttons there was a little break in the blinking (like the device would try to restart or something). As I didn't get any changes in the device-manager I disconnected it. After that it stopped to blink and doensn't blink anymore if I do the exact same thing again. it only vibrates now.
I'm sorry that this might be a tough case! Anyway I am thankfull for your advice!
But do you have access to the via ADB?
RSGI said:
But do you have access to the via ADB?
Click to expand...
Click to collapse
If you have ADB access you can try:
Code:
adb shell
su
setprop sys.usb.config diag,adb
I'm not familiar with ADB but I tried to get access to it via Minimal ADB and Fastboot. Even though the smartphone is recognized as ADB Composite Device in the device manager, it don't get any connection (as shown in the screenshot)

[Q] G2 stuck in Firmware Update: not recognized by KOUSH drivers

Hi All,
I've tried to flash a Lollipop KDZ file to my G2. It aborted at around 50% and since then, the phone is no longer recognized by my computer.
I had a problem like this before and I found the KOUSH drivers which made my phone connect to the computer again, but this time the phone does get seen by the computer, but it appears in Device Manager with an exclamation mark and "This device cannot start. (Code 10)" error.
Currently, all the phone will do is bootup past the LG logo and get into Firmware Update mode.
Despite the phone not being recognized by Windows 7, I tried to see if I could get in by the ADB command prompt, but typing "adb devices" gives... nothing connected..
What's the next step please?
SOLVED
I could not for the life of me connect the phone to my computer.
I just went to a random phone store (the ones where they unlock phones for € 10) and asked them to flash the phone back to standard.
This cost me € 20 to have a fully functional phone back.
Highly recommended.

Stuck on boot, can't access download mode, recovery crashes

I tried rooting my G2 using this guide, and seem to have f'ed up somehow.
The phone now won't boot (stuck at the "LG" screen, with rainbow LED), and I can't get into download mode.
The strange thing is that I do get into recovery mode, but it seems to exit abruptly. When I try to recover (by selecting yes twice), the Android recovery icon shows up for a couple of seconds, but then it goes back to the "LG" boot screen again.
I would be grateful for any help.
I've tried connecting to a computer with Ubuntu, as per this guide: http://forum.xda-developers.com/showthread.php?t=2582142, but I was unable to mount the phone.
It does show up in the device manager in Windows, under "Portable Devices".
I've disovered that the guide I followed for rooting was for G3 phones (and the G2 D805). I'm guessing this could be part of my problem.
But the guide said that I should be safe, since I had Lollipop. The Download mode should be able to save me if anything went wrong. But alas.
Before starting the rooting process I had the latest Lollipop update from LG (it was performing poorly, that's why I wanted to install a custom ROM).
Is it possible to save this phone? I'll probably look for a good deal on the 5X at Black Friday if I can't fix the G2, but I'd rather keep this phone working for a while anyway.
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
no connecting to pc
FonderPrism said:
Still having trouble with this.
If I turn on the phone and connect it to a PC (with the phone stuck at the "LG" screen) it appears my the device manager on my PC, but adb.exe reports no connected devices.
Click to expand...
Click to collapse
bro install adb driver or qualcomm driver.
link:https://www.dropbox.com/s/3hovx8h7nauy7e6/Qcomm_Drivers.zip?dl=0
kalpesh patil said:
bro install adb driver or qualcomm driver.
link:
Click to expand...
Click to collapse
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
FonderPrism said:
How do I install these? When I plug in the phone and view properties in device manager, I can't select update or uninstall driver.
(I would insert a screenshot here, but I need to have more posts on the forum first)
EDIT: I just removed the LG drivers by uninstalling the LG software + drivers, and removing any left over drivers using Nirsoft USBDeview. Then I installed Koush’s Universal ADB Driver. But adb still reports no connected devices... I guess this device is bricked after all.
Click to expand...
Click to collapse
bro i think ur phone is hard bricked.

Nexus 2012 3g bootloader issue.

I have windows 10, and am attempting to root and flash a custom recovery and ROM onto my nexus 7. Everything functions as intended until i have to enter bootloader. windows 10 is not able to recognize the device drivers when plugged in while in bootloader mode. It simply says that the device is not recognized. I read that the issue is needing to edit the .INF with updated hardware ID's for the device and reinstall the drivers using that INF file. However, trying to do that yields no results because when i uninstall the driver i cant find the device plugged in anywhere to be able to update its drivers in the device manager, and simply trying to override the devices currently installed drivers via device manager also does nothing. I even tried installing the driver update while the device was in bootloader via device manager (the device is recognized in device manager but has a yellow exclamation point and says device descriptor failed) with no results. What am i doing wrong? can anyone help? I've never had an issue this frustrating while trying to root an android device. Is it a windows 10 issue? I need a complete (and simple to understand) step-by-step please.
No help?

Categories

Resources