I used the OTA update and it went (as far as I can tell) without any problems. I tried to install TWRP, but when I use Wug's toolkit, or N-Cry, they cannot detect the phone in ADB. I tried removing and re-installing the drivers, but no luck. It worked fine before the update to 4.3, but obviously something has changed.
It will see the phone if I'm in fastboot, just not when the phone is up and running normally. Is this normal with the 4.3 update (I know not being able to get root at the moment is)?
Have you enabled USB debugging?
Sent using xda-developers app
chromium96 said:
Have you enabled USB debugging?
Click to expand...
Click to collapse
Yes, sorry, should have mentioned that...it is.
I tried un-checking the USB debugging box and re-checking it, un-plugging and pluggin the USB back in, rebooted computer and phone several times as well.
Did you update adb and fastboot as well?
Try updating your sdk or at least the platform-tools
I just updated the drivers using Wug's toolkit, is did that update adb and fastboot at the same time?
I'll try and update sdk and see if that helps.
I just tried installing Wug's toolkit on another computer running W7 (previous one on XP), and it seems to work great now It did ask me about alowing the RSK (I think), but then it seems to work fine. I was also able to use N-cry and get root back
Now I have to figure out how to install TWRP. I tried Wug's, but it didn't stick, when i try to boot into recovery it just give the android on his back with a red exclamation mark.
Same problem here. Followed the steps in the toolkit to install drivers, and the test always fails. The phone is seen by windows as a nexus 4, and no adb device nowhere to be seen.
I'm on Windows 8 BTW.
---------- Post added at 07:03 PM ---------- Previous post was at 06:49 PM ----------
Additionnal information : when i connect the phone, it appears as "Google Nexus ADB Interface" in the device manager. I seriously don't get it.
---------- Post added at 07:08 PM ---------- Previous post was at 07:03 PM ----------
Another : while messing aroung with the toolkit, i ended up on a tutorial about how to activate USB debug on my phone.
USB Debug is activated, but there is this step : 4.) You will see a prompt with your computer fingerprints [...]
I never get prompted for anything, would be on my computer or on the phone. Am i missing anything ?
---------- Post added at 07:25 PM ---------- Previous post was at 07:08 PM ----------
Alright sorry for spamming but finally found a solution : the phone has to be connected to the computer in camera mode -_-
Its just stuck at Download Mode when i boot my device directly goes to download mode. Its not even showing the usb icon if you press Volume up plus Connect usb to pc. Its just goes directly to download mode.
When i installed LG Drivers there's 1 conflict LGE Android MTP Device is not installing or Failed i tried it several times but the others are working (LGE Mobile USB Modem, LGE Mobile Serial Port (COM4) and Composite Device)
I tried to use Flash tool to flash the kdz. BUT it doesn't detect my phone. I dont know what else to do.
When using flash tool load the tot file and wait for it to say ready. Then you unplug and plug your USB back into the phone.
Sent from my LG-D800 using Tapatalk
---------- Post added at 02:07 PM ---------- Previous post was at 02:07 PM ----------
b4mb1_ said:
Its just stuck at Download Mode when i boot my device directly goes to download mode. Its not even showing the usb icon if you press Volume up plus Connect usb to pc. Its just goes directly to download mode.
When i installed LG Drivers there's 1 conflict LGE Android MTP Device is not installing or Failed i tried it several times but the others are working (LGE Mobile USB Modem, LGE Mobile Serial Port (COM4) and Composite Device)
I tried to use Flash tool to flash the kdz. BUT it doesn't detect my phone. I dont know what else to do.
Click to expand...
Click to collapse
For tot you need to change the port to port 41
Sent from my LG-D800 using Tapatalk
I dont understand it just doesn't detect the device. There's a problem with the MTE Driver i also tried it on my laptop or any other ports or even other drivers. Still not working its just the problem with the MTE Driver but others are fine
b4mb1_ said:
I dont understand it just doesn't detect the device. There's a problem with the MTE Driver i also tried it on my laptop or any other ports or even other drivers. Still not working its just the problem with the MTE Driver but others are fine
Click to expand...
Click to collapse
Do you have teamviewer? I want to see what's up.
Sent from my LG-D800 using Tapatalk
I do sorry i fell asleep can you please private message me your IM or any instant messaging app.
remove LG drive and setup it again , and try SKR tool -> unbrick ( u 'll need stock rom like cloudyfa ) . use TOT file to go back JB , dont use KDZ
So if you been messing around with your fire and got to the point that it wont want to get past the loading screen or something or you may have messed up during the root process you can use these steps to restore your Fire
MOD EDIT: THE FIRMWARE LINKED HERE IS NOT SAFE AT THIS TIME, LINK REMOVED AND THREAD CLOSED.
Steps.
1. MAKE SURE YOU HAVE ALL YOUR ADB DRIVERS INSTALLED!! and if you dont know how to check this thread
2. Download the amazon frimware above and keep it where you can flash it.
3. Boot into recovery (Volume Down + Power at the same time)
4. Select "adb sideload" or whatever it says using your volume keys and press the power to select
5. Now adb sideload <frimware>.bin
6. Its probably gonna take 5- 10 minutes so be patient and then once the recovery options come up make sure you wipe every thing and cache as well
7. Reboot gonna take another few minutes BE PATIENT!!
8. Now your back to your stock frimware.
I'm trying to try this method because Ive gone too far in deleting bloatware and now the Fire doesn't start properly. It get stuck on a flashing lock screen and I can't do anything (I can't concede ADB permissions so I can't operate with ADB console).
Sadly I'm trying to sideload bin into recovery mode, but It says: "device unauthorized". It weird 'cause I've the drivers installed on my PC (I've rooted and sideload Playstore before).
What can I do? :crying:
Darkside1984 said:
I'm trying to try this method because Ive gone too far in deleting bloatware and now the Fire doesn't start properly. It get stuck on a flashing lock screen and I can't do anything (I can't concede ADB permissions so I can't operate with ADB console).
Sadly I'm trying to sideload bin into recovery mode, but It says: "device unauthorized". It weird 'cause I've the drivers installed on my PC (I've rooted and sideload Playstore before).
What can I do? :crying:
Click to expand...
Click to collapse
Try installing ADB drivers in Device Manager while the Fire is in recovery. If you do it correctly, when you do ADB Devices, it should come up as Sideload.
Sent from my KFFOWI using Tapatalk
Troubleshooting
Device may not connect to PC until you select apply update from ADB,
check device manager, Fire should be listed ADB sideload or adb composite interface, when in recovery mode
If device is in adb sideload mode
Code:
adb devices
should return
Code:
G000HXXXXXXXXXXX.........sideload
if not drivers are not correct
Manually Fix Drivers
Open device manager Settings>Devices>Device Manager
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
next
you may have to reboot pc
Error
cannot read 'adb sideload update-kindle-37.5.2.2_user_522053820.bin'
Make sure Firmware.bin file is in same location, that is listed in command prompt
(ex: C:\Program Files (x86)\Minimal ADB and Fastboot>)
sd_shadow said:
recheck device manager, drivers are not correct, Fire should be listed adb composite interface, when in recovery mode
Click to expand...
Click to collapse
It's strange but when the tablet is in recovery mode, PC doesn't recognise it. The device manager doesn't show any related device. I've reinstalled drivers and nothing... Even I made the same procedure in another PC (also with W10) and nothing... There's no trail of any "Android device" in device manager when the tablet is in recovery mode. I'm seriously confused and I don't know what else to do...
Looking for a miracolous hard factory reset...
EDIT: I see that the battery is low. Does this have something to do with Recovery troubles?
i posted some basic using adb instructions in my amazon index
Using ADB
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
Darkside1984 said:
It's strange but when the tablet is in recovery mode, PC doesn't recognise it. The device manager doesn't show any related device. I've reinstalled drivers and nothing... Even I made the same procedure in another PC (also with W10) and nothing... There's no trail of any "Android device" in device manager when the tablet is in recovery mode. I'm seriously confused and I don't know what else to do...
Click to expand...
Click to collapse
try disconnecting from pc, power off fire, boot into recovery, connect to pc
---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------
you have to select apply update from ADB, before device will connect to pc
---------- Post added at 11:12 AM ---------- Previous post was at 11:03 AM ----------
Darkside1984 said:
I see that the battery is low. Does this have something to do with Recovery troubles?
Click to expand...
Click to collapse
possible, not sure if Amazon blocks flashing, if battery is low, i know motorola does.
You do not want battery to die during firmware install, it can brick a device.
Try charging battery.
sd_shadow said:
i posted some basic using adb instructions in my amazon index
Using ADB
---------- Post added at 11:00 AM ---------- Previous post was at 10:58 AM ----------
try disconnecting from pc, power off fire, boot into recovery, connect to pc
---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------
you have to select apply update from ADB, before device will connect to pc
---------- Post added at 11:12 AM ---------- Previous post was at 11:03 AM ----------
possible, not sure if Amazon blocks flashing, if battery is low, i know motorola does.
You do not want battery to die during firmware install, it can brick a device.
Try charging battery.
Click to expand...
Click to collapse
Thanks for your help.
It seems that there are some advances but a new problem appears. Finally the PC recognised the tablet into recovery's sideload option but a new error appears. I can't sideload with success 'cause of this message "You need adb 1.0.32 r never to sideload to this device. Installation aborted". Strange because I've installed the newer ADB drivers...
Darkside1984 said:
Thanks for your help.
It seems that there are some advances but a new problem appears. Finally the PC recognised the tablet into recovery's sideload option but a new error appears. I can't sideload with success 'cause of this message "You need adb 1.0.32 r never to sideload to this device. Installation aborted". Strange because I've installed the newer ADB drivers...
Click to expand...
Click to collapse
try
Code:
adb version
---------- Post added at 12:38 PM ---------- Previous post was at 12:38 PM ----------
should get
Code:
Android Debug Bridge version 1.0.32
Revision d15680a64678-android
sd_shadow said:
try
Code:
adb version
Click to expand...
Click to collapse
:-S
"Android Debug Bridge version 1.0.31"
Now I remember that "adb-setup-1.4.3.exe" installer didn't work for me. How could I install the last version?
Darkside1984 said:
:-S
"Android Debug Bridge version 1.0.31"
Now I remember that "adb-setup-1.4.3.exe" installer didn't work for me. How could I install the last version?
Click to expand...
Click to collapse
try link in my Using adb post
Wow! Hallellujah. I finally got resurrect my Fire. Thanks a million!
Darkside1984 said:
Wow! Hallellujah. I finally got resurrect my Fire. Thanks a million!
Click to expand...
Click to collapse
great
care to post some details about what worked?
Drivers version?
adb method?
Sent from my KFFOWI using Tapatalk
after side loading I needed to switch off the device and restart in order to start the final "Installing the latest software"-sequence
sd_shadow said:
great
care to post some details about what worked?
Drivers version?
adb method?
Click to expand...
Click to collapse
Sure!
I deleted my adb folder and follow the steps in your thread here. So it got the right adb version (1.0.32) and I finally could sideload properly the bin file. I think that the point is that PC just recognizes the Fire (as ADB composite) when you are into 'adb sideload' option, not in the recovery main menu.
5th Gen Kindle Fire - MT65xx Preloader problems
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
hochichi said:
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3238740
[HOWTO] How to restore firmware on your device + Amazon Firmware
hochichi said:
Hi - Noob here. 5th Gen Kindle Fire I'm trying to root. Followed the steps and had no trouble installing the ADB driver or running the .bat until...
Two things happen: 1st, Windows 7 says it fails to load a driver: MT65xx Preloader. 2nd: I get as far as the Fastboot screen but there it stops. Nothing else happens for 5-10 min until I shut it down.
I've tried downloading what were supposed to be MT65xx drivers (some off of other threads here). Windows 7 accepts none of them so far when I try to Update Driver on Unknown Device. Have tried pointing it to MT6577 USB VCOM drivers.rar, USB_Drivers.rar, and MT65xx Preloader.rar (all unzipped of course). No luck.
Any helpful advice would be appreciated.
Click to expand...
Click to collapse
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
fozzibab said:
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
Click to expand...
Click to collapse
Following your comment, I ran the .BAT while watching Device Mgr. Prior to running it, I had the Android device apparently successfully installed. It had its own folder in Dev Mgr without any [!]. Running the .BAT, that disappeared and Android migrated down to Other Devices. It's now next to the same Unknown Device that I haven't been able to update drivers for.
I tried pointing both to the latest_USB_drivers zip from Shadow's recommended thread. According to Win7, it's 'unable to install' from that unzipped folder or any of the others I've pulled from various threads.
fozzibab said:
I'm having the exact same issue. If you watch the Device Manager while the process rolls out, the MT65xx Preloader, will disappear after a few seconds and is replaced with just a generic "Android" device. At this point the rooting process hasn't even started yet, and the tablet is just sitting on the fastboot screen waiting for input.
Shadow, your solution doesn't apply. The device can still be booted back normally. It just basically sits at the fastboot screen until you power it off and turn it back on again.
Click to expand...
Click to collapse
did you try booting to recovery?
Sent from my KFFOWI using Tapatalk
sd_shadow said:
did you try booting to recovery?
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
With the Fire disconnected, I booted to recovery (Volume Down + Power) and got a list. Not knowing what to pick, I chose the Bootloader option. It started to boot in FASTBOOT mode. Plugged it in, went to Dev Mgr. Both Android Device and Unknown Device showing in Other Devices. Pointed the Android Device driver to the latest_USB drivers from your other thread. Windows says unable to install your Android. Tried same thing with Unknown Device. Unable to install.
Stucked in fastboot but computer does not recognize the phone, so i can do nothing, tried many tutorials but no communication between phone and computer.. it get connected as ALCATEL adb when plug it in computer..
g2 dead?
No charge of course?
---------- Post added at 01:51 AM ---------- Previous post was at 01:47 AM ----------
htc 3452 said:
Stucked in fastboot but computer does not recognize the phone, so i can do nothing, tried many tutorials but no communication between phone and computer.. it get connected as ALCATEL adb when plug it in computer..
g2 dead?
Click to expand...
Click to collapse
Delete lg drivers and install pdanet driver. See if that solves your connectivity problem.
Art Vanderlay said:
No charge of course?
---------- Post added at 01:51 AM ---------- Previous post was at 01:47 AM ----------
Delete lg drivers and install pdanet driver. See if that solves your connectivity problem.
Click to expand...
Click to collapse
I installed but stucked in "Updating Pdanet on your phone" then "installer failed to handshake with device" .:crying:
htc 3452 said:
I installed but stucked in "Updating Pdanet on your phone" then "installer failed to handshake with device" .:crying:
Click to expand...
Click to collapse
the screen has these msg
fastboot mode started
udc_start()
reset
portchange
fastboot: processing commands
EP1/out Fail nfo= ....
I'm trying to help a friend recover the data from his oneplus A5010. The touch screen is not responding so I can't enable anything. (file transfer... OTG... Are off).
I read in the forum that it is possible to switch usb debugging on. Using custom default.prop file and then sideload it from the recovery.
But for that I would need a help for a developer and some basic instructions on how to flash the custom file.
I checked maybe it is possible to install CWM or TWRP. But from what i can tell i can't install then without the debugging option
Other solutions are also welcome.
Do you have an OTG cable? If so, you can try plugging in an external mouse and use that to select menu items.
---------- Post added at 03:45 PM ---------- Previous post was at 03:44 PM ----------
Rethinking my previous post, I don't think that will work, as the OTG isn't natively active (thanks OnePlus). Is the screen entirely non-responsive?
Tried using OTG but it doesn't work. Mouse and keyboard are not responding
Probably the option is disabled
And touch screen is completely dead