Hi everyone! After happily rooting my Kindle and leaving it unattended for less then a few minutes, I came back to a boot-looped Kindle HD 6 because it had taken an OTA update.
I've looked at a few threads on this forum about how to get into Fastboot mode but I can't seem to get it working right. I have a Fastboot cable but that doesn't do anything either. Can someone help me?
PROBLEM SOLVED: I switched out the Motherboard c:
merlise said:
Hi everyone! After happily rooting my Kindle and leaving it unattended for less then a few minutes, I came back to a boot-looped Kindle HD 6 because it had taken an OTA update.
I've looked at a few threads on this forum about how to get into Fastboot mode but I can't seem to get it working right. I have a Fastboot cable but that doesn't do anything either. Can someone help me?
Click to expand...
Click to collapse
This is from another thread about a boot loop thought it might help you.
powerpoint45 said:
I do not know if this would work or even the steps, but you can download the stock firmware from here: www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201596860
Also the ????????????? Besides your device from "adb devices" just means you need to install the driver for it. That should not be too hard to find out how to do. But really I think you'd need the fastboot drivers more. But in the past I have fixed a bootloop by just looking at the logs to figure out where the crash is coming from via adb logcat, then fixing that issue. But since this is using xposed it'd probably be too complicated to fix manually. Don't ask me for drivers tho cause I use Linux.
Note: the firmware update downloads as a bin file but it is just a zip file. A fastboot update might actually work with it since it is signed by Amazon.
Something like:
Wipe your device. (only if necessary)
fastboot -w
Update your ROM.
fastboot update
---------- Post added at 11:03 PM ---------- Previous post was at 10:45 PM ----------
I've gotten into fastboot on this device. I think it was either "adb reboot bootloader" or "adb reboot fastboot" that works. Keep in mind when in fastboot mode the fire hd6 screen is completely blank.
Click to expand...
Click to collapse
AlbusAngelus said:
This is from another thread about a boot loop thought it might help you.
Click to expand...
Click to collapse
Thanks for trying to help I tried just about everything, but nothing is working.
I decided to just get another used HD 6 and switch out the motherboards and see what happens. I'll come back to the rooting game as soon as there is a working custom recovery and rom up, haha. Thanks.
See my thread: http://forum.xda-developers.com/fire-hd/general/to-fastboot-t2988597
meganoahj said:
See my thread: http://forum.xda-developers.com/fire-hd/general/to-fastboot-t2988597
Click to expand...
Click to collapse
Yours was actually the first I looked at! I tried but I unfortunately couldn't get ADB to recognize the device properly. I've already switched out the motherboards so my problem is somewhat fixed for now.
Think that you need a fastboot cord to get into fastboot. Just what I've heard.
ryanyz10 said:
Think that you need a fastboot cord to get into fastboot. Just what I've heard.
Click to expand...
Click to collapse
I have a fastboot cable, but it still didn't put me into fastboot
merlise said:
I have a fastboot cable, but it still didn't put me into fastboot
Click to expand...
Click to collapse
You need to power of and then press and hold volume up while plugging in the tablet i think.
Have you searched how to get into fastboot with fastboot cable on google?
ryanyz10 said:
You need to power of and then press and hold volume up while plugging in the tablet i think.
Have you searched how to get into fastboot with fastboot cable on google?
Click to expand...
Click to collapse
I have haha, I honestly tried everything but I just couldn't get it into fastboot. When I'm feeling adventurous, I'll probably try it again, but I just ended up switching out the motherboards with another HD6 for convenience.
Related
Hi everyone,
Thank you for your time in reading this. I need help with my bricked google glass. Basically I bought a glass not directly from Google 3 weeks ago. Last night I hit factory restore and it shutdown. When it rebooted it just had a white screen displayed. I understand this as the white screen of death after much googling. As I did not get it directly from Google, I do not have support and they will not honor my warranty.
As such I have been trying all sorts of things to restore it to factory and get it to boot up:
I am doing all the activities in OSX.
1. I am able to access fastboot, fastboot devices shows my device serial, however adb devices does not and adb reboot-bootloader cannot find the device.
2. I was able to fastboot oem unlock using ubuntu as there is a known issue running this in osx. All other subsequent activities were done in osx.
3. I was able to download the factory image from the google developer site. I downloaded XE18.11 and XE18.1 as I remember the device updated to XE18.1 OTA.
4. I put the device into recovery mode by holding the picture button, pressing the power button and continue holding the picture button for 10-15 seconds.
5. When in fastboot/recovery mode, fastboot devices works, fastboot reboot-bootloader works but adb reboot-bootloader does not - it does not find the device, neither does adb devices.
6. I can fastboot flash boot boot.img but the next step hangs when I execute fastboot flash system system.img. It just hangs and does nothing. Manually triggering fastboot flash recovery recovery.img works, it's just the system.img that hangs...
However, if I fastboot -w flashall, it is able to send and write the boot, system and recovery images to the device but it still boots to a white screen after. I was expecting it to work and be restored to factory as the image files were successfully written.
The factory image for XE18.11 and XE18.1 contain the files below:
android-info.txt
boot.img
bootloader.img
fpga.img
recovery.img
system.img
userdata.img
xloader.img
7. fastboot flashall only flashes boot, system and recovery. Do I need to manually flash bootloader.img? What is the danger of doing this? I am afraid of touching the bootloader as this is the only thing letting me connect to the device.
8. What about the other image files like xloader.img, userdata.img, fpga.img...do I need to manually flash those as well?
I would appreciate any help from you experts to help me bring this back to life. I can't afford to have a very expensive brick. :crying:
If anyone can help me fix this, I am willing to donate to a charity of your choice whatever I can afford.
I am desperate and willing to try anything...
Thank you everyone!
Apologies to the mods, if this should be in the glass forum, I did not find any technical/help section there so I decided to post it here.
Alex
Any experts out there who can help me please?
i would think that fastboot flash fpga fpga.img would work?
wrecklesswun said:
i would think that fastboot flash fpga fpga.img would work?
Click to expand...
Click to collapse
You're sooooo late bro.
It's almost 3 years ago, you're replying now. :0
sachin n said:
You're sooooo late bro.
It's almost 3 years ago, you're replying now. :0
Click to expand...
Click to collapse
Don't you just love it when you're browsing q&a and see a 3 year old thread?
RAZERZDAHACKER said:
Don't you just love it when you're browsing q&a and see a 3 year old thread?
Click to expand...
Click to collapse
Lol ye. But but wayyyy too late
Glass Enterprise Edition Experience?
sachin n said:
Lol ye. But but wayyyy too late
Click to expand...
Click to collapse
Anyone do something with Glass Enterprise Edition?
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
TjPhysicist said:
My watch is now bricked because I have no way to get out of "adb sideload" mode...how did you get out of that mode? please tell me.
Click to expand...
Click to collapse
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
osikiri said:
I pushed the reset button on the back(the silver one right above the charging connectors) with a pen for about 10 seconds, and it rebooted.
Click to expand...
Click to collapse
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
---------- Post added at 08:26 AM ---------- Previous post was at 07:41 AM ----------
TjPhysicist said:
Wow ok, that's a LOT longer than I'm used to with other devices...THANK GOD I thought I had bricked it completely.
Anyway, now i have to figure out a way to get adb to work in sideload,...i mean CLEARLY it's possible lots of others doing it..
Click to expand...
Click to collapse
Ok, does anyone know how to get my computer to recognise my watch in recovery mode? It's not about 'driver' the computer plain doesn't recognise that anything is plugged in at all.
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Wikiwix said:
I know the post is quite old already, but I experience exactly the same phenomenon...
I tried multiple PCs Linux and Windows,but non of them recognized the watch (neither on 4.4W1 nor on 4.2W2).
Anyone any idea?
Click to expand...
Click to collapse
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
mrkrabs said:
I believe u need to update the drivers.....I always go-to device manager...update driver..hit select from list..and choose android adb....
Sent from my LGLS990 using XDA Free mobile app
Click to expand...
Click to collapse
The problem, as @osikiri stated, is that the device does not get recognized at all (no unknown devices in devicemanager and the sound that comes on plugging in a device does not come as well). Furthermore, afaik Linux does not even need any drivers
Had the same issue today... and the only way out way battery death and recharge
JaceAlvejetti said:
Had the same issue today... and the only way out way battery death and recharge
Click to expand...
Click to collapse
If this really helps (seems weird): I guess the exact setting could be necassary:
You simply ran out of battery while the watch was running(not recovery or fastboot) and then plugged it in and went directly (or not?) to the recovery?
Thanks in advance, would be really great to fix this!
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
MSigler said:
Anyone ever find a fix to this? I'm trying to manually install the 5.0 update and I'm having the same issue. Every post I find with search tells me to update drivers but I'm on a Mac that doesn't even use ADB drivers. I've updated the SDK.
Click to expand...
Click to collapse
I'm doing the same thing and having the same issues!
Yeah, same issue for me as described.
Windows (Win7 x64 for me) doesn't even realise that the device is connected when it is in recovery mode. Although it will connected properly when booted normally.
+1 Any ideas?
Same issue for me. I've tried removing and replacing it on the cradle, killing and restarting the adb server, entering recovery by the touchscreen or by the adb/fastboot commands, clearing debugging keys, etc... Anybody have any other ideas?
---------- Post added at 07:25 PM ---------- Previous post was at 06:46 PM ----------
Ok, so it appears that the recovery img on 4.4w2 broke adb support or something. There are a few threads that suggest you can root and flash it or just wait for the OTA. We'll see whether I get the OTA before I have time to try this out.
Lollipop OTA Update: Download and How-To (Root Required)
I made a script that roots and updates your watch to 5.0.1 in a click.
[UTILITY][RESTORE][UNLOCK][ROOT] LG G Watch Tool
My way of doing it
osikiri said:
I'm trying to update my G Watch by sideloading a zip file.
I installed the sdk tools and usb driver as usual.
On debugging mode and bootloader, the watch is detected as an ADB device normally. 'adb devices' command works.
But when I reboot and get on recovery mode, the watch disappears on the device manager and never get detected again. So I cannot use 'adb sideload' command.
I've never experienced this kind of issue with smartphones.
Do you have any solutions?
Click to expand...
Click to collapse
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
fi thought it was finally the solution, but fastboot oem unlock bricked my sony smartwatch3. I see tomorrow if with my windows pc i can fix with sony companion, otherwise i'll have to use the warranty
willisc said:
I've similar problem, and I've spent almost 3 hours to find the solution. I found that following solution work for me:
http://forum.xda-developers.com/g-watch-r/development/manual-ota-update-root-t2969845
I've changed the step slightly according to the comments inside the thread:
- Enter Bootloader (swipe top left-bottom right as soon as the LG logo pops up on boot)
- Unlock bootloader (fastboot oem unlock) and boot the watch normally once
- Turn off and re-enter bootloader
- Flash 5.0.1 Stock Recovery (fastboot boot recovery.img)
// Do Not Flash 5.0.2 stock recovery
- Enter recovery and ADB sideload the update (tap the android, select install update from ADB and enter adb sideload filename.zip)
//you might have to reinstall the ADB drivers, just follow the simple step to install ADB driver
Done.
Click to expand...
Click to collapse
Already posted this 5 times on 3 sites and just not getting a lot of help. If it's bricked, fine, tell me. If it can be fixed, give me ideas.
I can't flash the bootloader or boot in any possible way. not through adb, not through tool kit, not through nexus 7 restore, nothing.
I can access fastboot mode (power+vol down) but nothing else. Standard power on gets stuck on google screen. It is unlocked. I have tried 3 different USB ports and 6 cables with no change.
No BS please, either Yes it's bricked sorry or No, it's not bricked, here are some ideas.
now i see that i'm not alone
same problem here, nobody ? It's a powerfull tablet, maybe now is going to be a powerfull paperweight, big paperweight, so sad.
can you boot into download mode if u can then
1.put your device into download mod 2.download the official firmware for your device on your computer
3.connect yor phone into your computer and flash it
if you can't boot into download mod then sorry I think it's bricked try to bring it to a service center
Sent from my SM-N7505 using XDA Free mobile app
pls answer me so I can help you
I couldn't help myself... I love my Nexus 7.
mrdownboy said:
I couldn't help myself... I love my Nexus 7.
Click to expand...
Click to collapse
LOL
and
zidozido22, i can boot just in fastboot mode
j4k0 said:
LOL
and
zidozido22, i can boot just in fastboot mode
Click to expand...
Click to collapse
Does the PC recognize? If you run the "fastboot devices" does it return a serial number? These things are pretty difficult to hard brick and if you can still get to the bootloader, then chances are it is recoverable. It helps to mention what you did for it to get to this state as well.
es0tericcha0s said:
Does the PC recognize? If you run the "fastboot devices" does it return a serial number? These things are pretty difficult to hard brick and if you can still get to the bootloader, then chances are it is recoverable. It helps to mention what you did for it to get to this state as well.
Click to expand...
Click to collapse
yes, it sends the serial number but when I had tried to flash it then it returns an error.
.***now im trying again with SkipSoft Android Toolkit, but it is stuck waiting for adb mode
before that state, it was charging, just that.
The tablet got Android 5 from OTA, and then android 5.1, i was using it as normal, but one day, while it was charging, it just show the google logo (name) and the lock down.
My 2012 wifi did that exactly. I downloaded wugfresh Nexus Root Toolkit yours can be d/loaded from here http://forum.xda-developers.com/showthread.php?t=2389107
All i did was put my 7 in fastboot mode then ran the tool kit. I then launched the advanced utilities and then fastboot format. Then i flashed stock rom.
Worked a treat. Thought mine was toast as well good luck.
snod33 said:
My 2012 wifi did that exactly. I downloaded wugfresh Nexus Root Toolkit yours can be d/loaded from here http://forum.xda-developers.com/showthread.php?t=2389107
All i did was put my 7 in fastboot mode then ran the tool kit. I then launched the advanced utilities and then fastboot format. Then i flashed stock rom.
Worked a treat. Thought mine was toast as well good luck.
Click to expand...
Click to collapse
I tried once, but i will try it again, thank you
---------- Post added at 12:25 AM ---------- Previous post was at 12:09 AM ----------
doing that you said:
Advanced tools--> fastboot format
now it is stuck in "Fastboot Formating CACHE..."
=(
i think the main problem (one o f them) is that i cannot use adb, when i use the command
Code:
fastboot devices
i get the serial number but when i use
Code:
adb devices
the results is nothing.
j4k0 said:
I tried once, but i will try it again, thank you
---------- Post added at 12:25 AM ---------- Previous post was at 12:09 AM ----------
doing that you said:
Advanced tools--> fastboot format
now it is stuck in "Fastboot Formating CACHE..."
=(
Click to expand...
Click to collapse
I hate to be the bearer of bad news, but that's not a good sign. I haven't found anyone reporting success when it's having that issue. If you have exhausted the external possibilities such as drivers, USB cords, the PC, trying Windows and Linux, etc and still getting the same thing then that means the eMMC is probably messed up. Examples here:
http://forum.xda-developers.com/showthread.php?t=2602638
can you boot into bootloader if you can then navigate by using volume up volume down till you find the recovery and press lock button and factory reset
zidozido22 said:
can you boot into bootloader if you can then navigate by using volume up volume down till you find the recovery and press lock button and factory reset
Click to expand...
Click to collapse
They're way past the point that a factory reset would help or even work as wiping cache is not working and that is part of a factory reset. If it isn't wiping through fastboot commands, it definitely won't work through recovery.
sorry, then you should bring it to a service center
very hard and sad to hear that, thank you anyway guys...
about RMA i saw that will be expensive bcz the warranty time expired
Please! If someone can help me. I did step by step correctly and my le max 2 still with original recovery. All cmd messages are successful, but when I turn on recovery mode, this is the original EUI version. I wanted to use some rom of you but without the TWRP I can not. Some help?
lucasnoman said:
Please! If someone can help me. I did step by step correctly and my le max 2 still with original recovery. All cmd messages are successful, but when I turn on recovery mode, this is the original EUI version. I wanted to use some rom of you but without the TWRP I can not. Some help?
Click to expand...
Click to collapse
If you have your device rooted you can download rashr from the play store and flash the recovery.img from there
moto999999 said:
If you have your device rooted you can download rashr from the play store and flash the recovery.img from there
Click to expand...
Click to collapse
Unfortunately he is not. I solve the problem with unrecognized device, but it always come back. In this post: https://forum.xda-developers.com/le-max-2/development/recovery-twrp-3-0-2-0-unofficial-t3443611
The author says: "OTG is working for some people but not for others also some readers and flash drives are not being seen. Will look into fixing it."
This is kinda my problem. For now i'm using 19s indian stock
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Antisound said:
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Click to expand...
Click to collapse
Yes, I did it. But a blue screen appear fast and my smartphone turns off. It does not go into recovery at all, only after I start the phone normally. Funny that I only get message of success since the release of the bootloader until the installation of twrp.
Have you tried "fastboot boot <recovery.img>"?
sudloa said:
Have you tried "fastboot boot <recovery.img>"?
Click to expand...
Click to collapse
I forget to mention. After the "successful" twrp install, the device is not recognized. What I mean: "List of devices attached" is blank. So I can't use this command.
lucasnoman said:
I forget to mention. After the "successful" twrp install, the device is not recognized. What I mean: "List of devices attached" is blank. So I can't use this command.
Click to expand...
Click to collapse
fastboot could use in fastboot mode (shutdown then vol down + power) only and windows sohuld recognize this.
But I think your adb usb driver got conflict somehow.
You can try "usbdeview" to uninstall all adb usb drivers then use some knid of universal adb usb driver installer.
Antisound said:
Do you immediatly reboot into recovery after flashing TWRP? If not, the Stock Recovery will be restored and twrp is getting deleted again.
if you type "fastboot reboot" just hold the "volume up" key at this moment until you're in twrp...
Click to expand...
Click to collapse
This is the key part I have missed as well !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Along with the AT USB unlock code (Dial *#*#76937#*#*) to allow ADB
Thank you :laugh:
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
lucasnoman said:
Unfortunately he is not. I solve the problem with unrecognized device, but it always come back. In this post: https://forum.xda-developers.com/le-max-2/development/recovery-twrp-3-0-2-0-unofficial-t3443611
The author says: "OTG is working for some people but not for others also some readers and flash drives are not being seen. Will look into fixing it."
This is kinda my problem. For now i'm using 19s indian stock
Click to expand...
Click to collapse
Hi, You should TITLE your post Why does TWRP not stay resident ?
paulsnz2 said:
This is the key part I have missed as well !!!!!!!!!!!!!!!!!!!!!!!!!!!!
Along with the AT USB unlock code (Dial *#*#76937#*#*) to allow ADB
Thank you :laugh:
---------- Post added at 11:45 PM ---------- Previous post was at 11:40 PM ----------
Hi, You should TITLE your post Why does TWRP not stay resident ?
Click to expand...
Click to collapse
You're Welcome
Antisound said:
You're Welcome
Click to expand...
Click to collapse
I have the 820. Could NOT get windows to see this phone on stock rom. Don't recall exact steps I took, but I do remember the ADB feature within TWRP saved my day. Windows would see the phone in TWRP recovery adb mode, but could never get windows to adb connect with stock rom.
Hey people, sry I'm coming back now. Lightning struck my street and burned my pc. But I come back with another problem, when I connect my phone to the pc nothing happens. I mean, I can't transfer cause MTP doesn't work. I tried install unninstall and install again adb, and all the drivers but it did not work. So I'll need to fix this to try to install twrp again
Guys! I was being too stupid! I found my mistake... I was using another smartphone twrp... So, for who are having same issue, pay attention to this. But, thanks everybody and sry for this hahaha
So,
Yesterday i was trying to root my S7 (SM-G930V). I was going through all the lists of things to do from a website on rooting with Magisk. Using ADB and Fastboot to get it working. I'm stuck at trying to install the boot.img onto my phone but when I'm doing anything with Fastboot it is not seeing my device. i been looking around the web for any answers and got nothing. With ADB I got as far as connecting my device and rebooting it into boot-loader and all i got to do from what the website says is to download the boot.img to it using fastboot. Then the problem comes in with Fastboot not noticing my device. i have it connect with USB and all drivers up to date. I'm i missing something impotent? I'm still kinda newbie at this.
did you try a diff cable?
hiitsrudd said:
did you try a diff cable?
Click to expand...
Click to collapse
Yup, It just doesn't read the devices for some reason when its in bootloader