Hey guys,
I was trying to restore my kindle back to stock, but i've ran into an issue where i can't sideload, access google play store anymore. Went through a lot of the guides uninstalled and reinstalled drivers by all the different guides, attempted to load twrp and use KFFirstaide to no avail.
While going through one of the other guides to install all the adb and fastboot drivers with the android SDK repository I noticed i don't have a complete Hardware ID, Could this be an issue why i can't get the Fire HD 6 to sideload anything or even Fastboot with a fastboot cable?
( can't post a link to the image because of my posts being up 10 =( )
USB\VID_1949&PID_00F2&REV_????&MI_00
USB\VID_1949&PID_00f2&MI_00
Related
I have a rooted Google Nexus 10 tablet with Clockwork Mod and Android 4.4.2. The Google USB driver worked fine on my Windows 7 laptop and I was able to use adb to push files to my tablet. I foolishly let the automatic 4.4.3 OTA download and install. Now, my tablet is stuck in bootloop AND Windows has completely forgotten my Google USB driver and thus adb can't see the tablet, so I can't transfer over the 4.4.3 image or flash in Clockwork Mod via sideload. Yes, Clockwork Mod works great and I can boot into recovery mode. I've seen a thousand postings that all talk about stuff you do from Android like enabling USB debugging, etc, but this is all worthless when you can't boot Android. In retrospect, I wish I had kept a backup image on my SD card. So three questions:
1. How can I get the update image onto my tablet, either by sideload or adb push?
2. Is the factory image (4.4.3 (KTU84L) ) correct or since I'm rooted, am I supposed to use a modified one?
3. Would the manual update method be as simple as copying over the factory OTA to my SD Card ahead of time, booting into recovery mode and flashing?
Thanks in advance to anyone who can help.
Well, no response from anybody. I just saw this on another post: "Having USB Debugging ticked WHILE IN ANDROID has absolutely no effect on whether or not your computer can see the device WHILE IN RECOVERY OR FASTBOOT. "
This is very informative. I just wonder if "adb devices" ever shows anything if you're in recovery mode. I wonder also if the Windows 7 driver is supposed to work. I have a feeling this driver is based on communicating with Android itself, so of course it won't work. So maybe fastboot is the way to go? That's what I'll try next.
fastboot
This looks relevant - it has a ton of fastboot commands:
http://forum.xda-developers.com/showthread.php?t=2024259&page=3
So I am no stranger too rooting, but i managed to do something wrong when dirty flashing a rom update.
Gapps no longer works, my device is un-rooted and the 'gapps stopped working' notification pops up every 1 second, making my device unusuable.
I'm using the Amazon Fire 7" running SlimLP. To be clear, this was all working at a point.
I could boot TWRP and fix this with a backup I made, but here's the problem: Fastboot commands isn't working.
I can use ADB and boot into fastboot mode, but once there my commands have no effect and the Windows 7 CMD just displays <waiting for device>.
Also, my stock recovery seems to be deleted so I have no recovery whatsoever.
I have all the correct drivers and used the google sdk drivers to no effect. Also, in device manager my device shows up as 'Android Bootloader interface' and shows: This device cannot start. (Code 10).
So to Sumarise
My device needs a backup flashed
Fastboot commands are unresponsive
I have no root.
I have all the drivers installed
I am using a 2015 Kindle fire 7"
With a windows 7 64 bit laptop
Please help!!!
Thanks in advance
If you need any more info, drop me to a comment and I will get back to you ASAP, I'm desperate!
I can use flashfire, and Im open to any workarounds.
amaramar2000 said:
So I am no stranger too rooting, but i managed to do something wrong when dirty flashing a rom update.
Gapps no longer works, my device is un-rooted and the 'gapps stopped working' notification pops up every 1 second, making my device unusuable.
I'm using the Amazon Fire 7" running SlimLP. To be clear, this was all working at a point.
I could boot TWRP and fix this with a backup I made, but here's the problem: Fastboot commands isn't working.
I can use ADB and boot into fastboot mode, but once there my commands have no effect and the Windows 7 CMD just displays <waiting for device>.
Also, my stock recovery seems to be deleted so I have no recovery whatsoever.
I have all the correct drivers and used the google sdk drivers to no effect. Also, in device manager my device shows up as 'Android Bootloader interface' and shows: This device cannot start. (Code 10).
So to Sumarise
My device needs a backup flashed
Fastboot commands are unresponsive
I have no root.
I have all the drivers installed
I am using a 2015 Kindle fire 7"
With a windows 7 64 bit laptop
Please help!!!
Thanks in advance
If you need any more info, drop me to a comment and I will get back to you ASAP, I'm desperate!
I can use flashfire, and Im open to any workarounds.
Click to expand...
Click to collapse
Please don't cross-post; found this exact text in three different threads. My earlier response here. Others have basically said the same thing. You're done.
I had TWRP installed and all was good. Then I tried an OTA update. Update failed and now I can't get into recovery or fastboot. When I try it stops at the 1+ logo with Fastboot Mode written under the logo. This happens if I try Volum Up + power button or adb reboot-bootloader. Device is listed with ADB but won't show up for fastboot.
How do I get back to stock recovery and get the update installed?
Thanks!
Is fastboot installed properly on your PC?
Drivers?
If not and you get it working, you can use fastboot to flash a new recovery. Otherwise read ahead.
Does your phone boot? Is it rooted?
If so, you can try to flash a new recovery via tools like FlashFire, Flashify, Rashr, etc.
If none of those work for you, you can try the un-bricking methods.
I've had my Oneplus 2 hardbrick 3 times on me so far. The solution was to put the phone into a Qualcomm QHUSB_BULK mode, installing unsigned drivers in Windows, and using Chinese software to push recovery files to your phone.
For my first two hard bricks (My phone wasn't responding to anything - it would just show up in the device manager when plugged into the PC). I was able to write the stock recovery and boot files onto my phone by using Method 1 from this OnePlus Forums thread: https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/.
I was then able to boot to recovery and dirty flash my OS without any data loss this way.
The last hard brick was much worse and required me to completely reinstall everything on my phone via one of the other methods (I used this link: http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449 and ended up with H2OS, which I then replaced with OOS 3.1.0) - if it comes to that I would recommend checking out the other methods in the OnePlus Forum link below to hopefully avoid going through H2OS - but if not, this one worked.
Also, for updates: You'll need to to reflash (dirty flash) your rom first (this is to unroot/undo any modifications you made to the system, otherwise the OTA will fail) and then flash the OTA. You should be able to use TWRP for this.
Thanks for the reply. Got fastboot working on a different computer.
Phone boots just fine. Not rooted. Just can't access recovery mode or install updates
I tried loading stock recovery (as per this thread) with no change. Thinking I'll have to treat it like it's bricked. Would rather not have to wipe phone though, but doesn't look like I have much choice .
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
CrazyArjun said:
For the past two days I had faced the issue of connecting the device in fastboot mode. Mobile is working fine, loaded with latest firmware OTA updates from OnePlus.
I would like to install TWRP on my mobile but the device is getting detected in the fastboot mode. Tried various steps, reinstalled adb & fastboot as well as OnePlus drivers nothing works. However my mobile is being detected in the adb mode. If I run the command adb devices, it displays my mobile serial number but in fastboot it just sits at the waiting for the device screen.
After a lot of googling, xda search & Oneplus forums search, nothing found. Then I tried reinstalling the adb interface drivers manually, where I have noticed that Win10 installed the latest drivers adb drivers updated in the month of Sep16. Here I have selected the older version driver which was released in the year 2014 and installed it successfully. I run the fastboot devices command again Voila... It worked. no restart, no rebooting the phone. Immediately worked.
Lesson learnt : - Always do not use latest drivers, sometimes try the older drivers if something is not working in your phone.
Click to expand...
Click to collapse
can you share those drivers,,facing same issue actually
Im using Ubuntu 18.04.3. All was fine until the point it said success. Ive then unplugged the phone to see if it boots and it didnt respond to the power button until several minutes later. Now it does attempt to boot but ive left it for like 15 minutes and nothing - stuck on the xperia animation. Ive attempted to reboot into win10 and use the companion app to fix my phone but it says that the bootloader is unlocked.
Ive considered using fastboot to flash TWRP or relocking the bootloader and move from there, but literally every command i give it returns 'FAILED (command write failed (Success))'
Attempts to use windows to do that also went nowhere: Im unable to install the drivers. Ive downloaded the sdk studio, installed the google drivers plugin, located the folder with them, but when i connect my device it doesnt show in the device manager. If i connect it in fastboot mode, it shows as 'Android', but windows refuses to install the drivers claiming that they are incompatible.
EDIT: nvm, managed to install the drivers on windows, sucessfully flash TWRP and fix it from there
I guess a lesson was learned today: dont use linux for this kind of stuff
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Ur device's bootloader still unlocked?
T0B3R said:
Hi People,
I hope I am putting this question in the proper location.
I have had several attempts ate flashing a new ROM to my device as it was the Chinese version & kinda useless to me not having Play store or several other APPs I want. I also wanted to try ROOT a phone for the first time.
I managed to get as far as getting ADB & fastboot working & TWRP installed on the device. The first ROM I had put in my file storage was corrupt so I tried the Lineage 17 version which "seemed"to install with a success message, but the phone would only boot into TWRP. so I tried the Havoc ROM from the thread in this site area. Same thing, would only boot into TWRP. Then I thought I would start over & install the factory ROM from: https://xiaomifirmwareupdater.com/miui/olivelite/stable/V12.0.2.0.QCPMIXM/ with ADB & fastboot. I got a success message from the MiFlash tool but the device is now saying the "MIUI verson cannot be installed on this device" in one screen from the Redmi-Recovery 3.0 menu that's now on it.
From here I can Reboot, wipe data or connect with MiAssistant. When I try MiAssistant (PC Suite) the phone does not connect to my PC but I can see the ADB device from device manager and ./adb fastboot devices shows a serial number -but connected as sideload if that makes a difference?
I hope I explained well enough to be understood. Is there anything I can do from here to get it working or is it fully stuffed?
Click to expand...
Click to collapse
You should flash China factory rom, if you can.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com