I've got my N7 bricked to where I can only get to fastboot. I made the mistake of locking it (couldn't get any fastboot commands to work, then that one decided to work). Now when I try to unlock it I use "fastboot oem unlock" at the command prompt it stays at "erasing userdata". It was stuck there for a few hours last nigh before I gave up. I've seen this issue online a few places, but no one seems to have an answer for it. I've tried different than USB cables and ports... No change. Here is a picture of the prompt: http://imgur.com/MevZn2n
bump...still doing the same thing.
pmd5700 said:
bump...still doing the same thing.
Click to expand...
Click to collapse
Mine is also doing the same thing and it is stuck in a loop.
Same here!!
Virgin N7 2013... No hacking... Bootloader locked... started acting weird and I attempted a system restore. It now gets stuck at the Google screen. Fastboot gets stuck at erasing userdata. I have tried multiple USB cables on Win7, OSX, and Ubuntu. Help!!!
Related
My kindle was in the stuck in the recovery loop and wouldn't connect to the pc so I tried using this tool.
http://forum.xda-developers.com/showthread.php?t=1428428&page=17
I tried using the recovery loop but it didn't work so i pressed other... looking to see more options. In the end, it connected to the pc but i think it broke it. Now when i boot up the kindle, it is stuck at the screen that says kindle fire and has the little andriod guy on it. Can anyone provide help to fix it? And is it broken?
lordofthenoobs said:
My kindle was in the stuck in the recovery loop and wouldn't connect to the pc so I tried using this tool.
http://forum.xda-developers.com/showthread.php?t=1428428&page=17
I tried using the recovery loop but it didn't work so i pressed other... looking to see more options. In the end, it connected to the pc but i think it broke it. Now when i boot up the kindle, it is stuck at the screen that says kindle fire and has the little andriod guy on it. Can anyone provide help to fix it? And is it broken?
Click to expand...
Click to collapse
You have FireFireFire installed so this should be fairly easy.
But would you please explain the so called "recovery loop"?
Yes, i do have firefirefire installed, i installed twrp firefirefire, and everything to make the kindlefire and andriod about a year ago. The recovery loop is the twrp loop where you are stuck in twrp no matter how many times you restart. That's just what i call it but yeahh sorry for making it hard for you to understand.
No biggie. I just find it best to not make assumptions around here.
Download this and flash it in recovery
http://forum.xda-developers.com/showthread.php?t=1632375
Read the thread to learn how to use the boot menu then use it to reset your bootmode.
How would i get into recovery? I can only reach the logo screen right now, i can provide a picture tomorrow if needed, thanks!
When you get to the white kindle blue fire quickly depress the power button a few times till you get the boot menu, then select --recovery-- .
soupmagnet said:
I just find it best to not make assumptions around here.
Click to expand...
Click to collapse
And...I just ate my words.
lordofthenoobs said:
How would i get into recovery? I can only reach the logo screen right now, i can provide a picture tomorrow if needed, thanks!
Click to expand...
Click to collapse
TWRP is recovery. You are stuck at the FFF screen, not the TWRP screen. Upon startup, hold the power button until it turns orange then release. Or turn your device off, enter "fastboot oem idme bootmode 5001" at the command line and turn the device on when you see "waiting for device".
From there, you can use adb to push the FFF1.4a.zip to your sdcard, or mount your sdcard to USB and transfer it like that.
My directory is to C:\kfu\fastboot... uhhh when i type in fastboot oem idme bootmode 5001 or fastboot getvar product, it doesn't do anything and just skips to the next line waiting for another input. I am currently running windows 7
except ppinrum
lordofthenoobs said:
My directory is to C:\kfu\fastboot... uhhh when i type in fastboot oem idme bootmode 5001 or fastboot getvar product, it doesn't do anything and just skips to the next line waiting for another input. I am currently running windows 7
Click to expand...
Click to collapse
Excuse me for double post, but i guess this is somewhat a bump to change my old edits because i finally decided to read some old posts but this part is the most troubling and sorry for not reading threads beforehand and rushing into a conclusion.
Pm sent unread your private messages.
lordofthenoobs said:
My directory is to C:\kfu\fastboot... uhhh when i type in fastboot oem idme bootmode 5001 or fastboot getvar product, it doesn't do anything and just skips to the next line waiting for another input. I am currently running windows 7
Click to expand...
Click to collapse
I'm pretty sure that isn't even possible.
There are two things that can happen when when you enter "fastboot getvar product":
You will see the "waiting for device" message, or you will see "kindle".
Anything else would make me wonder if either your fastboot.exe is corrupted, or there is something wrong with the procedure in which you are entering the command.
Maybe it's time to try on a Linux liveUSB.
"That's a special kind of stupid. The kind that makes me laugh"
aceniop scruples
soupmagnet said:
I'm pretty sure that isn't even possible.
There are two things that can happen when when you enter "fastboot getvar product":
You will see the "waiting for device" message, or you will see "kindle".
Anything else would make me wonder if either your fastboot.exe is corrupted, or there is something wrong with the procedure in which you are entering the command.
Maybe it's time to try on a Linux liveUSB.
"That's a special kind of stupid. The kind that makes me laugh"
Click to expand...
Click to collapse
So thepooch and i found out that it's not working because of my 3.0usb ports but i'll try again. He also recommended me to use the LinuxliveUSB as well.
We also had another problem with the install_driver.bat inside the kindle fire utility where it wouldn't install the drivers.
I tried searching for methods to install unsigned drivers but none of them worked. Does anyone have a method they that could possibly work?
Thanks!
The device is in fastboot but will to accept fastboot commands terminal instantly reverts to native prompt. The driver uninstall was a hassle and installation happens so rapidly I am inclined to think there is an issue there. The 3.0 usb could be the largest hurdle an is very likely the issue at hand. My guess is that this pc did not do the original rooting and the cable is confirmed different which lends a little more flavor to the 3.0 problem. Best bet is a different machine or a live usb on a different machine just my opinion.
You're all probably thinking "Oh he is stuck in a recovery loop and here's how you get out of it."
This all starts with the fact that I'm trying to use Kindle Fire Utility to root my device. However the normal circumstance is that it must boot into fastboot but in my case it is impossible to get past fastboot no animation and just sits there. I've been trying to my research on how to do this but I can't seem to find an answer for this. I've already told my computer to boot it back into normal mode via ubuntu with the fastboot command "fastboot -i 0x1949 oem idme bootmode 4000" and it works fine that puts me back in normal mode past the no-animation screen.
So I'm still trying to get rid of this fastboot recovery loop that still persists. I've already restored back into stock rom and the same problem persists. Has anyone have had this experience and successfully the eliminated the loop problem?
In a similar circumstance is that if I have my normal cable or factory cable plugged into between my machine and the kindle, it does the same issue and does not get past no-animation part.
I'm guessing it comes down to the fact that there is a misconfigured setting on the kindle regarding TWRP perhaps. I would appreciate ANY help whatsoever. I want to eliminate this stupid problem. Now, remember, I am able to get back into normal mode via ubuntu with the above command line so that isn't the issue here. The issue is this fastboot / does not get past no-animation stage that I want to fix.
EDIT: I've resolved this. I was missing the fff bootloader which was causing all of my issues in the first place. Sorry for wasting your time looking at this.
Hello,
i got a kindle fire 2 here, but it is stucked on the Bootlogo. it was tried to install a custom rom by a friend of mine, so i cant tell, which method he tried or on what command it failed. a backup isn't available.
anyway, i got a fastboot cable here, which my friend didn't had.
when i plug it, it start into fastboot mode an show me a flashing green traffic light. the windows device manager shows me the "Kindle Fire -> Android Composite ADB Interface" (as seen in the attachment)
the "fastboot devices -i 0x1949" command shows me a "0E6... fastboot" line.
i tried to fix it with commands from this post: http://forum.xda-developers.com/showthread.php?t=2100963
ended up, that the blue kindle logo doesn't show up. instead its now stucked in a bootloop. the logo disappers any few seconds and it seems, the device is restarting every time.
now i have no idea anymore, how to go on. tried to use the kindlefireutility2, but after i run it, it closes immediately or just shows "Initializing..."
also the FirstAide64 will not work. when i select "Completly Restore KF2 - fastboot" it shows up an Error Message "The system can not find the specified path..."
adb commands are not usable during fastboot, right? because the adb devices list is empty every time.
hopefully someone can give me a hint, what else i can try.
regards
arthur
arthur. said:
Hello,
i got a kindle fire 2 here, but it is stucked on the Bootlogo. it was tried to install a custom rom by a friend of mine, so i cant tell, which method he tried or on what command it failed. a backup isn't available.
anyway, i got a fastboot cable here, which my friend didn't had.
when i plug it, it start into fastboot mode an show me a flashing green traffic light. the windows device manager shows me the "Kindle Fire -> Android Composite ADB Interface" (as seen in the attachment)
the "fastboot devices -i 0x1949" command shows me a "0E6... fastboot" line.
i tried to fix it with commands from this post: http://forum.xda-developers.com/showthread.php?t=2100963
ended up, that the blue kindle logo doesn't show up. instead its now stucked in a bootloop. the logo disappers any few seconds and it seems, the device is restarting every time.
now i have no idea anymore, how to go on. tried to use the kindlefireutility2, but after i run it, it closes immediately or just shows "Initializing..."
also the FirstAide64 will not work. when i select "Completly Restore KF2 - fastboot" it shows up an Error Message "The system can not find the specified path..."
adb commands are not usable during fastboot, right? because the adb devices list is empty every time.
hopefully someone can give me a hint, what else i can try.
regards
arthur
Click to expand...
Click to collapse
So you have followed Steps 3 and 4?
Just below that is a method to flash back to stock, have you tried that, as the stock files are there as well?
arthur. said:
Hello,
i got a kindle fire 2 here, but it is stucked on the Bootlogo. it was tried to install a custom rom by a friend of mine, so i cant tell, which method he tried or on what command it failed. a backup isn't available.
anyway, i got a fastboot cable here, which my friend didn't had.
when i plug it, it start into fastboot mode an show me a flashing green traffic light. the windows device manager shows me the "Kindle Fire -> Android Composite ADB Interface" (as seen in the attachment)
the "fastboot devices -i 0x1949" command shows me a "0E6... fastboot" line.
i tried to fix it with commands from this post: http://forum.xda-developers.com/showthread.php?t=2100963
ended up, that the blue kindle logo doesn't show up. instead its now stucked in a bootloop. the logo disappers any few seconds and it seems, the device is restarting every time.
now i have no idea anymore, how to go on. tried to use the kindlefireutility2, but after i run it, it closes immediately or just shows "Initializing..."
also the FirstAide64 will not work. when i select "Completly Restore KF2 - fastboot" it shows up an Error Message "The system can not find the specified path..."
adb commands are not usable during fastboot, right? because the adb devices list is empty every time.
hopefully someone can give me a hint, what else i can try.
regards
arthur
Click to expand...
Click to collapse
I was having the same problem, i just booted and suddenly turned off. It was on the stock rom , so I used a factory cable and installed fff 1.4 then installed the twrp 2.5 from their site but I'm not able to get it into recovery, just an amber light and it turns off!! I'm wondering if is not compatible, I tried the otter and blaze twrp just to make sure...
What do you think? Did you managed to fix it?
Sent from my SPH-D710 using xda premium
chronicfathead said:
So you have followed Steps 3 and 4?
Just below that is a method to flash back to stock, have you tried that, as the stock files are there as well?
Click to expand...
Click to collapse
i wanted to get the restoration tool from here, but the file is not availible anymore. anyway, the device didn't received the adb commands.
i tried to flash the original stock rom back, just by using files from amazon. i don't know what happend, but after "fastboot bootloader" command the Kindle is dead. No more LED light while charging, no reaction on fastboot cable
first i thought, the battery is empty, but after one night on the charger, nothing changed. the device stays complete black.
Any chances left (even at amazon?) or is the garbage the only place this kindle belongs now?
Well Arthur, if you have not opened it should not be dead, it seems like you are on a boot loop and maybe the battery is fully discharged.
Please explain how did you tried to install the Amazon stock ROM
Sent from my SPH-D710 using xda premium
well, my first thoughts were also, that the battery is discharged. but i used next to my computer already an ipad charger and my phone-charger (both over 1A out) over night. but still no lightning of the LED.
last thing i remember, was a (afterwards clearly) stupid hint from a ebay page. [fastboot -i 0x1949 flash bootloader u-boot.bin] i used the u-boot.bin from the amazon homepage.
afterwards the kindle shut down and the lightning LED has never been seen again
Your KF will not charge if bricked, you could try a factory cable to get it into fastboot mode but if it is discharged maybe you must try another method to charge the battery... First try the factory cable!!
Sent from my SPH-D710 using xda premium
i tried with a factory cable, but again, no response from the device. As I mentioned, I tried already several charger.
And what do you mean by another charging method? Is there something i don't know yet ?
Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.
I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.
I already rooted it and was then going through the process outlined in this thread:
https://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.
And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.
It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.
I was going to try to load regular android on it, but now that seems out of the question.
Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.
Thanks,
-Joel
joeldf said:
Hi. Long time lurker, but finally found myself in a pickle. So now I'm asking for help.
I have a first get Kindle Fire that I figured I'd experiment with after getting a new Kindle HD 8. It has OS 6.3.4 and has been stock until just now.
I already rooted it and was then going through the process outlined in this thread:
https://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
so that I could add TWRP. But, after the step "Step 5: Forcing Fastboot Mode" and entering "adb reboot", the Kindle rebooted without the animated logo as the instructions said it would... except it stayed that way.
And, it's still that way. Any adb command I enter returns "error: device not found". I tried the Kindle Fire Unbrick utility, but it also couldn't find the device, even though it finished the attempt with the message that it's now unbricked - except, it's not. Even my Windows 10 PC throws up an error when I try to reconnect the USB that there's a device error.
It's not in a boot loop - it's flat stuck. I can turn it off by holding the power button for about 15 seconds. And I can turn it back on, and I've tried entering adb commands as soon as I do turn it on to see it if takes, but it doesn't. It just sits there displaying the "kindle fire" logo.
I was going to try to load regular android on it, but now that seems out of the question.
Is there anything else I could try? I will try letting it drain the battery, and then plugging it in again, but any other suggestions would be appreciated. Anything else I need to provide, please let me know.
Thanks,
-Joel
Click to expand...
Click to collapse
When it's in fastboot mode, use fastboot commands, not adb
Sent from my sailfish using XDA Labs
Thanks,
The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.
So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned
FAILED (status read failed (Too many links))
finished. total time: 0.031s
But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.
Still, thanks. I guess it wasn't stuck or bricked after all.
joeldf said:
Thanks,
The instructions were not clear on what to expect at that point, and I assumed it was stuck. It didn't occur to me to just keep going.
So I did, and it responded as it was supposed to. When I got to "fastboot -i 0x1949 oem idme bootmode 4000", it returned
FAILED (status read failed (Too many links))
finished. total time: 0.031s
But the "reboot" command took and got the white and blue. It flashed a bunch of times but finally got it to boot with the normal white and yellow logo. I think part of it was that the battery had gone down since I last posted. I'm now recharging it before going further.
Still, thanks. I guess it wasn't stuck or bricked after all.
Click to expand...
Click to collapse
Did you watch my video?
Sent from my sailfish using XDA Labs
sd_shadow said:
Did you watch my video?
Sent from my sailfish using XDA Labs
Click to expand...
Click to collapse
I watched several videos, and I think I started yours at one point, but between my 8 year old running around saying it's almost midnight (it was new years eve), and then trying to get him to go to bed, by the time I came back to this, I may have lost track of what I was watching.
Moral of the story, do this kind of thing without interruptions...
I did re-watch your video all the way through and I see that what happened was normal.
Still, there was that error trying to reset the bootmode (I didn't get what you got), otherwise, it still works and re-boots fine now. Even went into Recovery.
Next thing is trying out a new rom.
Thanks again.
MY DEVICE IS ALSO STUCK!!! After doing the fastboot reboot it gets stuck with the lifeless bootscreen and doesn't do anything from there, I've also tried to use the set boot mode but it hangs on waiting for device
I've been following the steps to unlock my bootloader, and after inputting the "fastboot flash unlock unlock.bin", the command prompt froze for a good 5 minutes. After googling a video of someone doing the same thing, I saw they got an output almost instantly, so I cancelled the operation (through ctrl c), and restarted the phone.
Since then, the phone's pop up for authorizing USB debugging never came up, I've switched the protocols, tried different PCs and even factory reset the phone, but the problem is still happening.
Does anyone know how this could be fixed, if it can at all?
Thanks in advance.