HI guys, Ive not been here in a while as I sold my Kindle, However 8 months later, its come back.. The user has said he deleted a navigation program that did not work off the kindle and since then the Kindle is in a continual Boot loop, it will not go passed the orange "Kindle fire logo, it looks like its running, as the image is moving (like its processing) but nothing happens.
I got a factory cable, plugged that in and it just says Fastboot in orange on the screen, nothing else happens. I look in the device drivers and the Kindle is listed there Android ADB Device. The kindle was rooted but on a stock rom (if nothing has been changed. I'm sort of poking around in the dark, any help would be greatly received.
I dont mind wiping the kindle back to factory settings, I've even tried this with KFF but nothing seems to happen on the command screen, Deamon tools load and then it just stops and waits for ever.
Anyone any idea's ?
Thank you in advance
John
You have to flash stock files to fix, I think.
Sent from my KFHD running CM11
Thanks for the info wire55, I'll keep reading up and refreshing my memory.. strange thing is, I seem to able to run adb commands on the Kindle with the normal usb lead, but when I use the factory cable, it puts it into fast boot, but adb doesnt seem to want to communicate with the kindle then ?
Think I may have it, I hadn't changed the path in the Environmental Variables to where I had downloaded the latest KFF, it seems to be accepting the restore image files.. Fingers crossed lol
Yea.... This is the software that's fixed it .. I did try another KFF but it said there was a problem booting and it kept looping into reset to factory default.. So I downloaded and tried this, which has worked .. Thanks again for the help Wire55 :good:
{
"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"
}
You don't do adb in fastboot. You do fastboot in fast boot.
Sent from my KFHD running CM11
---------- Post added at 11:49 PM ---------- Previous post was at 11:42 PM ----------
Your very welcome, if I had thought about it, I would have linked you to that tool. ☺
Sent from my KFHD running CM11
Related
I'm a newb..
Atrix HD with unlocked bootloader and rooted. Installed cwm recovery, flashed to the latest nightly cm 11 for atrix hd, rebooted and stuck at cyanogenmod loading screen (head with the spinning circle around it). left it that way over night with no change still stuck on bott.
I've spent several hours following several guides with no success
I think the problem started whn I did a factory reset and clear cache in cwm before I flashed cm 11. it gave an error on data or something.
fastforward several hours later I now have philz touch 6 recovery which I read on this guide http://forum.xda-developers.com/showthread.php?t=2577447 you could use to fix the corrupted data partition. problem is when booted to philz recovery the driver for phone is not installed correctly.
{
"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"
}
The phone is recognized fine in fastboot mode however.
Is there a way to fix the corrupted data partition using fastboot?
I've already tried fastboot -w and reflashing but that did not work.
I have the latest motorola drivers and latest sdk with google usb installed etc.
Unfortunately I was stupid and didn't make a nandroid backup so I hope there is another way to get this phone working.
thanks
Solved
After 2 days of monkeying around I finally got it fixed.
I never could get the phone recognized in recovery mode (philz mod) and using ADB as suggested by the guide I linked.
Finally what worked is I downloaded the stock rom zip, extracted it, edited the xml file in MS word deleting the 2 lines with "getvar" in them, booted the phone into fastboot mode, connected the phone to my PC and made sure it was recognized in device manager, loaded the xml from the stock rom into RSD Lite and flashed back to stock, rebooted, and all was working fine.
I know there's a million and 1 guides that say to do what I just described and believe me I tried the exact things I posted above for the better part of 2 days and rsd lite would always fail with some kind of error. Finally I rebooted my PC, downloaded the stock rom again, edited the xml, and tried one last time and it finally worked...I don't know what made the difference.
Now if I could just find a trick around this darn subsidy (hard) lock this Atrix HD would be back in business.
Micromax Canvas A1 India. Yesterday evening the phone suddenly turned off. Since then whenever I want to turn on, it shows last following screens and turns off again.
{
"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"
}
It's not rooted. Just upgraded to lollipop over OTA last week. Tried clearing cache from recovery, didn't gelp. Yet to factory reset. But want to know if there is anyway to do it by not factory resetting. Have some data in it.
since you can't really get in to the OS, you can't really do anything besides a factory reset. install a custom recovery if you don't have one already either from ADB or from a toolkit, go on to the recovery, get a backup. Then do a reset. If the data on your phone that you want to save is all app data, google probably already backed them up. plus, with google's restoring feature when starting up the phone and login in to a google account for the first time (or after a reset) you can restore apps, app settings and even wallpapers and homescreen icons just from a touch.
flash the stock rom.
You must have messed things up. Flash the stock lollipop.
to do so, you need to switch your device off, and then press the "Volume up" and "power" button at the same time. then by using volume up select the "fastboot" option. Then connect your phone to your PC.
https://drive.google.com/file/d/0BzS3UbVEklJCVDh3dG9kTFdyT1k/view?usp=sharing Download this ( SDK File ) and install drivers from http://adbdriver.com/downloads/ here. Then open SDK File ( after extracting it ) give it a command "fastboot devices" - if you get something like this,
continue. After this give the command "OEM Unlock". Let it do the thing. After thant do not do anything. stay calm the first boot will take 10-20 mins. Now if your phone is good, then https://www.google.com/url?q=http:/...s-cse&usg=AFQjCNEzNufF7sIICgRpx58wVOczOYDCrw relock your bootloader with this. DO NOT UNLOCK YOUR BOOTLOADER WITH THIS TOOL.
Press thanks if i helped.
---------- Post added at 10:37 AM ---------- Previous post was at 10:15 AM ----------
Another simple way.
https://www.youtube.com/watch?v=W9Co-2QBRZU
This requires an unlocked bootloader and adb drivers.
ADB Drivers once again - http://adbdriver.com/downloads/
Turns out, something was wrong with the Android system. When I turned it on, it would stay black after showing that "process system isn't responding" message. But if I pressed power + volume down, it'll show that it took a screenshot(you can hear the sound and see the white border of the screenshot), which was of course all black. Not exactly sure what went wrong. Factory resetting from recovery fixed it.
Here is the situation I have an HTC ONE (M7) Here which does absolutely nothing but show this message...
It does not have usb debugging enabled and adb will not register it. I can however connect to it via fastboot....
Ive gotten as far as unlocking the bootloader... But now cannot seem to get any further as everything I have read uses ADB and i cannot get it to recognize ADB Device.
Basically from what i am reading.... Is flash custom recovery such as TWRP (Which i have downloaded) and i want to just reinstall stock rom etc. Not trying to root or anything here, just simply trying to reinstall factory software for HTC One (M7) - Telus Canada to hopefully resolve the issue.
Please any help is greatly appreciated I have been up now for nearly 20 Hours trying to get this done.
Exactly like this
dugie33 said:
Here is the situation I have an HTC ONE (M7) Here which does absolutely nothing but show this message...
It does not have usb debugging enabled and adb will not register it. I can however connect to it via fastboot....
Ive gotten as far as unlocking the bootloader... But now cannot seem to get any further as everything I have read uses ADB and i cannot get it to recognize ADB Device.
Click to expand...
Click to collapse
Because you are boote din bootloader mode. ADB can't work when in bootloader mode, only from custom recovery or from a booted rom + usb debug on. Here a nice table I made last week to explain the same thing to another guy:
{
"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"
}
Basically from what i am reading.... Is flash custom recovery such as TWRP (Which i have downloaded) and i want to just reinstall stock rom etc. Not trying to root or anything here, just simply trying to reinstall factory software for HTC One (M7) - Telus Canada to hopefully resolve the issue.
Click to expand...
Click to collapse
Post the output of "fastboot getvar all" (remove your imei and sn before posting)
Hello everybody,
I have run into a major issue with my Kindle Fire HD (Tate).
I have CM12 installed on it (Candy 5) and I reset it to "Factory data reset" in the settings menu as I wanted to give it to my mother as she has never had a tablet before.
After it wiped the data the device rebooted, but instead of going back into CM12 it instead took me to TWRP and just shows the blue "teamwin" screen and goes no further.
I found instructions online on how to resolve this issue using either Fastboot or ADB; but neither of them work for me.
Fastboot just doesn't recognize it. Using "fastboot devices" doesn't return anything.
ADB recognizes it and even shows the device ID number but ADB version 1.0.31 says it is "offline" and ADB 1.0.32 says its "unauthorized".
I have tried this on 3 different computers and several different USB cables. 2 of the computers I tried are running Windows 10 and the other has Ubuntu and they all have the same issue. I am also using a USB 2 port as I read that USB 3 isn't compatible.
Can anybody give me some suggestions on how to fix this or point me in the right direction of where I can get the answers myself?
Thanks in advance.
Have you tried booting into twrp using hardware keys?
Sent from my Amazon Tate using Tapatalk
letrain02 said:
Have you tried booting into twrp using hardware keys?
Click to expand...
Click to collapse
Yes I have. It just takes me to the same "teamwin" logo screen that I get stuck at.
Just to be clear, this is the screen I am getting stuck on:
{
"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"
}
Well unfortunately the Tate needs a factory (fastboot) cable to fast boot. Only the 8.9 can fastboot from the commands you mentioned. I just did bootloader and twrp to my Tate yesterday and got stuck in boot loop and made my own fastboot cable. It's fairly easy if you have a good cable to work with. I cut 4 open till I got one that actually had a spot to soldier on pin 4.
Sent from my Amazon Tate using Tapatalk
Hello to all!
Two years after I bought my awesome 6/128 ZUK Z2 Pro ("international" rom, android 6.0.1, ZUI 2.1.120, no updates), I decided to mess with it. After getting some trouble done, I flashed via QFIL the stock 1.9 (possibly updated to 2.5 yet? not sure...) and the SuperSU, which I couldn't flash on stock ZUI 3.1.194. Last two days I was trying to find a way to flash TWRP but I couldn't, because I tried through fastboot and it always told me "waiting for device". I could only boot TWRP through the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", as it was described at a guide here (BTW, guys thanks a lot for everything you share with us!). But still, it didn't let me install some roms I've tried (AOSP 6.7, AOSP 7.0), because "Updater process ended with ERROR:7". Also, after flashing the SuperSU, I couldn't open the stock recovery, it automatically redirected me to fastboot.
My (big) problem started when I randomly chose "Boot to FFBM" through fastboot, so the "All Failed" screen was appeared. It couldn't be so bad, but is behaved like having a bad stroke, and the "buttons" on the bottom or anything else, can't be selected or scrolled properly. After rebooting (holding the power button), it sent me there, again. So now, it is impossible to boot at the rom. I can still boot into bootloader, but it doesn't recognize QFIL yet, in order to install the rom again. I can also boot into twrp via the "fastboot -i 0x2b4c boot recovery-TWRP-3.0.2-20160712-ZUK_Z2_PRO-CN-wzsx150.img", but nevertheless i cannot install another rom.
{
"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"
}
I mean, I REALLY need your help, otherwise I had to buy another phone! (I'm stuck with my mother's, old J5 2015 for now)
I still cannot boot into stock recovery, and I can install nothing from that twrp. I think my only hope is, if you know another command through powershell, which my phone can obey (except it often tells me "waiting for device"). Or else, this would be the hard way for me of learning what "hard-brick" is.
Thanks in advance for your time, sorry for grammar/spelling mistakes, I would really appreciate any help given! :crying:
Images:
Oh, unfortunately the images aren't shown, I hope they are here:
For some reason they aren't shown, I got them by a shareable link in google Drive.. If anyone is interested in helping me, I can send the images private. In fact, I would even pay some bucks for this!
Ok, I noticed that there are also many "bricked" (or not) cases from another members here that haven't be answered, but since I found the solution for my case I'm leaving the thread for anyone who possibly need it:
https://zukfans.eu/community/thread...-read-this-before-creating-a-new-thread.7603/
In my case, the answer was on the last Q & A, about the accidentally stuck to the FFBM mode, so I just thanked this guy. Have a nice day!