Related
A while back, I posted about forcing the Fire to boot over USB instead of from the internal memory. This trick requires you to open the back of your Fire, but after that the only tool you need is a pair of tweezers, sharp scissors, bent paperclip, or anything else with a fine point that can short two things together. After that, it's all cake to boot FIREFIREFIRE, then TWRP, then adb in and have your way with the Fire's memory.
Now that 6.2.1 is here ruining our party, it's time to package this up for anyone to use.
As useful as they are now, fastboot cables may not work in the future. They rely on the bootloader to work, and it's possible that a future OTA could disable fastboot.
For the adventurous. This is mostly untested by me, and runs a good risk of fuglifying or permanently breaking your Kindle. If you haven't voided your warranty yet, this will.
Install TWRP over USB
0) You will need a PC with Linux and working adb, the .zip attached to this post, and the installer version of TWRP[/URL]. Also a microUSB cable. And something to short the contact like tweezers or a bent paperclip.
1) Unpack the rekindle .zip and copy TWRP into the directory it creates. Change directories into rekindle/
2) Open a terminal and sudo or su to root. It's easier that way.
3) Unplug the USB or AC adapter if it's plugged into the KF. But have the USB cable's A end plugged into the PC. This is very important.
4) Turn the power completely off. Do a shutdown if actually running Android, or hold the power button until there's no LED or backlight.
5) Pry open the back cover. The iFixit teardown (Google it) gives some ideas on how to do it, but be really careful because it's easy to snap the tabs along the long sides.
6) The power must still be off. If you accidentally powered it back on, turn it back off.
7) Run:
Code:
./usbboot aboot.bin u-boot.bin; ./fastboot boot twrp-blaze-2.0.0RC0.img
This will chain load aboot, FIREFIREFIRE, then TWRP.
8) Short the point shown here to the metal frame around the CPU area using your paperclip or whatever. While keeping it shorted, plug in the USB cable. This will power up the Fire with the CPU in USB boot mode.
9) If it works, you'll see some text fly by in the terminal, and you'll see the yellow triangle hopefully followed by TWRP starting up. You can follow the instructions in the TWRP post on completing the install.
Rooting 6.2.1
***This likely won't work***
There are reports of problems booting after applying this bootimage. Try the TWRP install above and one of the root update.zips instead.
0) You must already be running 6.2.1. Otherwise try a safer method.
1) Get the rooted 6.2.1 bootroot .img from here..
2) Follow the procedure to install TWRP above, but stop before step 7 (the usbboot command). You can skip downloading TWRP.
3) Run this command instead:
Code:
./usbboot aboot.bin u-boot.bin; ./fastboot flash boot 6_2_1rootboot.img
4) Then continue at step 8 until the fastboot flash command finishes.
5) Hold down the power button until it powers off (~15 seconds), and press it again to power it back up.
Windows & OSX support
Currently usbboot is built for Linux only. I had experimented with building it against libusb for Windows and OSX. Unfortunately the window to make the connection before the CPU resets again is about 2 seconds, and Windows takes a lot longer than that to enumerate new USB devices. I don't know about OSX, but I guess a libusb version (usbboot's USB code is Linux-centric) would work fine. Github is here if you want to take a crack at porting it.
Successes? Failures? Smoking hole in the ground that used to be your Kindle? Post here.
LOL really bad news for Amazon.
Can't wait for the full guide.
Thank you m8
how about a quick run down on how to do this now? I have some time and really want to mess with this thing
foxdog66 said:
how about a quick run down on how to do this now? I have some time and really want to mess with this thing
Click to expand...
Click to collapse
Moved into the main post.
EDIT
1st borked usb ports, then i got it to work
!CONFIRMED WORKING!
Proof?? Show us a pic dude!!!
How did you get the back off without scratching the hell out of it...or is it all scratched up now? Lol
foxdog66 said:
How did you get the back off without scratching the hell out of it...or is it all scratched up now? Lol
Click to expand...
Click to collapse
some scratches, and i only used 2 id/credit cards
beepFTW said:
Proof?? Show us a pic dude!!!
Click to expand...
Click to collapse
proof you say? i was in irc the whole time with Vashypooh
plus im running cm7 now
Cool! Thanks man, the whole community thanks you. Any chance of a youtube tutorial? I think many of us will need it. Haha
good work mate keep it up!
pokey9000 said:
For the adventurous. This is totally untested as of now, and runs a good risk of fuglifying or permanently breaking your Kindle. If you haven't voided your warranty yet, this will.
0) You will need a PC with Linux, adb and fastboot installed and known working, a copy of the omap4boot for Kindle Fire from this post, a copy of FIREFIREFIRE, the older TWRP 2.0 that doesn't have the FIREFIREFIRE installer (or use the other if you want to install TWRP and FIREFIREFIRE automatically). Also a microUSB cable. And something to short the contact like tweezers or a bent paperclip.
Click to expand...
Click to collapse
Hi, a silly question here, as you did say one will need a linux machine, but...
Can it be done under Windows 7 64bit?
If so - what software will I need apart from adb shell access, FIREFIREFIRE and TWRP 2.0?
dalogrus said:
Hi, a silly question here, as you did say one will need a linux machine, but...
Can it be done under Windows 7 64bit?
If so - what software will I need apart from adb shell access, FIREFIREFIRE and TWRP 2.0?
Click to expand...
Click to collapse
this has linux only binaries, use on linux
So just to be clear this works with 6.2.1 so would allow a downgrade to 6.2 or a sidegrade to the hacked 6.2.1 image with root enabled?
Sent from my Kindle Fire using xda premium
Should allow you to flash anything that can be flashed by fastboot.
Very cool. I was wondering if this CPU supports leaving it like that but still being able to boot normally, much like FIREFIREFIRE where it starts in fastboot mode, then after a short time, switches to normal boot. There is a hack for the Galaxy S phones that works like this. You short a point on the board, then leave it that way. Now when you boot, it will try to boot from USB, and if that fails, switches over to internal flash. This would be a very nice mod to have.
ttabbal said:
Very cool. I was wondering if this CPU supports leaving it like that but still being able to boot normally, much like FIREFIREFIRE where it starts in fastboot mode, then after a short time, switches to normal boot. There is a hack for the Galaxy S phones that works like this. You short a point on the board, then leave it that way. Now when you boot, it will try to boot from USB, and if that fails, switches over to internal flash. This would be a very nice mod to have.
Click to expand...
Click to collapse
Yes, it does, but it would take some soldering and more than shorting just one pin. Also we haven't identified all the boot mode pins.
dalogrus said:
Hi, a silly question here, as you did say one will need a linux machine, but...
Can it be done under Windows 7 64bit?
If so - what software will I need apart from adb shell access, FIREFIREFIRE and TWRP 2.0?
Click to expand...
Click to collapse
Not silly, I've tried to get usbboot to work on Windows when I developed a Nook Color version, but the Windows USB stack sucks. If it were to work, it would piggyback on either libusb or the Google USB driver, either of which have 32 and 64 bit versions. Windows gurus are welcome to lend a hand.
Stuck on Kindle...
I have the 6.2.1 update so tried this.
I followed the instructions but when I `fastboot reboot` the screen goes black. When I power it down manually and then turn it back on it hangs on the initial Kindle boot screen, it never gets to the animated Kindle boot screen.
Code:
# ./usbboot aboot.bin u-boot.bin; fastboot flash boot 6_2_1rootboot.img
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
< waiting for device >
sending 'boot' (3234 KB)...
OKAY [ 0.814s]
writing 'boot'...
OKAY [ 1.155s]
finished. total time: 1.969s
MintBookPro kindle # fastboot reboot
rebooting...
finished. total time: 0.001s
#
I noticed the fastboot command didn't have ./ in front of it so tried that with the same results, it just hung on the Kindle boot screen.
Out of curiosity I tried the TWRP image and that worked so I was able to install the full rooted 6.2.1 (not just the boot image) from TWRP and now I have 6.2.1 rooted.
So I don't think there was anything wrong with your app, that seemed to work fine, but the plain 6.2.1 boot image seems not to work. Which isn't your issue but anyone that tries this needs to be aware of it.
Great work pokey9000! Very interesting what you are doing.
A couple of questions if you can spare the time.
1) What bootmode is it that shorting the pin enables?
2) As I have a factory cable, would this do the same without popping the case?
Also, and this is off topic and possibly already asked and answered, but I'm curious of your thoughts of the possibility to just select boot from usb on power up from the device, maybe through a utility such as TWRP or some other. Seems that if that could be done, one could greatly increase the size of storage, effectively circumventing the current internal storage limitation. And since the usb is removable and rewritable, you could revert to an earlier version archived on a pc if any updates get pushed that break something.
mikbe.tk said:
I have the 6.2.1 update so tried this.
I followed the instructions but when I `fastboot reboot` the screen goes black. When I power it down manually and then turn it back on it hangs on the initial Kindle boot screen, it never gets to the animated Kindle boot screen.
Click to expand...
Click to collapse
Corrected my directions to hard power off. Reason is that the boot mode gets detected on cold reset, and the reboot warm resets and so doesn't detect the new bootmode. I suppose we could add something to override the boot mode when you call reboot if it detects that USB is the boot device. Code is already there to do something similar with bootmode 4003.
I noticed the fastboot command didn't have ./ in front of it so tried that with the same results, it just hung on the Kindle boot screen.
Click to expand...
Click to collapse
My bad, fixed.
Out of curiosity I tried the TWRP image and that worked so I was able to install the full rooted 6.2.1 (not just the boot image) from TWRP and now I have 6.2.1 rooted.
So I don't think there was anything wrong with your app, that seemed to work fine, but the plain 6.2.1 boot image seems not to work. Which isn't your issue but anyone that tries this needs to be aware of it.
Click to expand...
Click to collapse
Don't know about this, these directions were created w/o a Fire in my possession. I'll make a note in the OP to try the TWRP method.
About 3 weeks ago, I bricked my Kindle Fire. It was a "spare" that I had, so I started messing around with it. Got TWRP installed, downloaded a couple of ROMS, and attempted to install them. (fortunately, I made a backup of my base Amazon 6.2)
To make a long story short, the fire got stuck. I was able to adb and various other things on this forum to keep things going, but after a while, Kindle Fire Utility (adb, nothing) could see the device. I thought for sure I had an expensive paper weight.
Enter the factory cable. Because SkOrPn was in the middle of a move, my cable didn't get here right away. Then there were some issues with my PayPal address, which SkOrPn went out of his way to fix. Today, I got the cable at my office.
Looked at the cable. Thought I had been send an unmodified cable. Saw no evidence that anything had been done to the cable. An absolutely perfect professional job.
Couldn't wait to get home. Got home. Plugged cable in Fire, then in Laptop. Nothing. Now what? I thought it was supposed to boot the bootloader? adb didn't see the device. Drivers good, it sees my other Fire. I guess I was one of those 1% that hard brick the fire with no chance of getting it back.
Did a few searched on the forum. Found how to install TWRP on my device. I thought I had it already? Ran the commands. Nothing. Switched to regular cable. Nothing. I figured I was screwed. I unplugged the Fire. connected the factory cable. Ran the command. THEN hooked up the cable. JOY JOY JOY!! i GOT TWRP loaded!!!!
Restored my previously saved image, and now I have a working Kindle Fire. NOW i'm going to install some other ROM on it.
The moral is, never give up. Buy a factory cable!!! One of the things I've ever spent $15 or so on. And I recommend SkOrPn as your source. Quality work, great customer service!!!
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
Sorry for the long post. My wife doesn't understand why this would make me so excited. But you all would, I'm sure.
SteveM
a very nice post for people who have bricked their kindles and need a factory cable!
Thanks for the kind words Steve. I hope this cable gives you confidence in flashing your Kindle long into the future. Glad it worked out for you.
Oh, and you did not see any evidence of modification because I do not modify the cable, I just cut off the original micro connector and install my own, already modified of course with a resistor and all I have to do is re-solder the 4 wires back onto their original pins and then fill the entire casing with 400 degree SureBonder PDR Hot Glue (the worlds strongest known hot glue, according to them anyway lol)... That way it looks and feels like a true manufactured store bought cable. However, doing it my way is still in fact more work, but the end result clearly justifies it.
Anyway, again glad I could be of service to you and my fellow XDA friends.
Where do I run the command from?
The3rdEye said:
Where do I run the command from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=23747804&postcount=3
smoen02 said:
About 3 weeks ago, I bricked my Kindle Fire. It was a "spare" that I had, so I started messing around with it. Got TWRP installed, downloaded a couple of ROMS, and attempted to install them. (fortunately, I made a backup of my base Amazon 6.2)
To make a long story short, the fire got stuck. I was able to adb and various other things on this forum to keep things going, but after a while, Kindle Fire Utility (adb, nothing) could see the device. I thought for sure I had an expensive paper weight.
Enter the factory cable. Because SkOrPn was in the middle of a move, my cable didn't get here right away. Then there were some issues with my PayPal address, which SkOrPn went out of his way to fix. Today, I got the cable at my office.
Looked at the cable. Thought I had been send an unmodified cable. Saw no evidence that anything had been done to the cable. An absolutely perfect professional job.
Couldn't wait to get home. Got home. Plugged cable in Fire, then in Laptop. Nothing. Now what? I thought it was supposed to boot the bootloader? adb didn't see the device. Drivers good, it sees my other Fire. I guess I was one of those 1% that hard brick the fire with no chance of getting it back.
Did a few searched on the forum. Found how to install TWRP on my device. I thought I had it already? Ran the commands. Nothing. Switched to regular cable. Nothing. I figured I was screwed. I unplugged the Fire. connected the factory cable. Ran the command. THEN hooked up the cable. JOY JOY JOY!! i GOT TWRP loaded!!!!
Restored my previously saved image, and now I have a working Kindle Fire. NOW i'm going to install some other ROM on it.
The moral is, never give up. Buy a factory cable!!! One of the things I've ever spent $15 or so on. And I recommend SkOrPn as your source. Quality work, great customer service!!!
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
Sorry for the long post. My wife doesn't understand why this would make me so excited. But you all would, I'm sure.
SteveM
Click to expand...
Click to collapse
Hi there,
Where should I run that command from??
Here´s my case, I hope you could help me..
I need urgent help. Just got my kindle todasy and went through tutorial to use the rooting utitily. My kindle got stuck at loading screen and wouldn´t shut shutdown. I waited until the battery ran out. Waited for few more minutes and plugged in the data cable. The kindle now won´t stop blinking and does not get reckgonized by the pc. I did waited for the battery goes dead again, recharged then for about 30 min and nothing has changed. The loading screen keeps blinking and nothing seems to be happening. Please advise!!
andersonrel said:
Hi there,
Where should I run that command from??
Here´s my case, I hope you could help me..
I need urgent help. Just got my kindle todasy and went through tutorial to use the rooting utitily. My kindle got stuck at loading screen and wouldn´t shut shutdown. I waited until the battery ran out. Waited for few more minutes and plugged in the data cable. The kindle now won´t stop blinking and does not get reckgonized by the pc. I did waited for the battery goes dead again, recharged then for about 30 min and nothing has changed. The loading screen keeps blinking and nothing seems to be happening. Please advise!!
Click to expand...
Click to collapse
Oh boy... I'm going to hope that it was a timing issue and our posts got crossed, because I answered your question for another user just above your post.
Regardless, the answer to that question isn't going to help you. You need this...
http://forum.xda-developers.com/showthread.php?t=1621146
Never let your battery die like you did. You can always force a shutdown by keeping the power button pressed down for 20-30 seconds.
EDIT: I'd been meaning to post this guide for a while...
http://forum.xda-developers.com/showthread.php?t=1623244
and I missed the part of your post about being "stuck at loading screen" the first time I read it. I suggest you read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
make sure the device drivers are working (part 2) and learn some fastboot commands (part 3) so you can reset the bootmode on your device back to normal and reboot it.
kinfauns said:
Oh boy... I'm going to hope that it was a timing issue and our posts got crossed, because I answered your question for another user just above your post.
Regardless, the answer to that question isn't going to help you. You need this...
http://forum.xda-developers.com/showthread.php?t=1621146
Never let your battery die like you did. You can always force a shutdown by keeping the power button pressed down for 20-30 seconds.
EDIT: I'd been meaning to post this guide for a while...
http://forum.xda-developers.com/showthread.php?t=1623244
and I missed the part of your post about being "stuck at loading screen" the first time I read it. I suggest you read this guide...
http://forum.xda-developers.com/showthread.php?t=1552547
make sure the device drivers are working (part 2) and learn some fastboot commands (part 3) so you can reset the bootmode on your device back to normal and reboot it.
Click to expand...
Click to collapse
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?
andersonrel said:
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?
Click to expand...
Click to collapse
Unfortunately, if the device isn't booting up, it won't charge. Like the guide I posted above says, the device needs to load up a ramdisk before it will charge. If all you see is that KF/Android logo, then it's still in the bootloader and it's not charging your battery.
First, you'll have to get your drivers in order so you can send the device fastboot commands. I suggest you disconnect the KF from your computer and make sure it's turned off. Use the KFU driver install file and get it to install the drivers again onto your machine. I'm not sure if it will help, but it wouldn't hurt to reboot your computer after that. When it's back up and running again, open up the device manager. When you connect the KF back up to your computer, it should automatically power up again... look at what device comes up as it boots. The first thing you see (hopefully) is "Android Phone -> Android ADB Interface" appear. If you see that, you can be reasonably sure you can send it fastboot commands.
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
There's a lot of "hopefully" things that have to go right for this to work. You've got a few compounded issues that are giving you problems and all of them have to get fixed for the battery to start charging again.
andersonrel said:
Thanks for your help. I tried to run a fastboot command and get msg: ´cannot run, adbwin.dll missing´... Now I´m really not sure what it´s missing anymore..
I´m going also leave it charging for longer and it seems to be a known issue, right?
My kindle continues not being reckognized and keeps on flashing the kindle Fire/Android Logo. When I unplug it it stops flashing and I won´t get any sigh of life, even after pressing the button for longer than 30s.
I managed to find the driver on device manager and uninstalled it, thinking that maybe it would help finding the device again, but it didn´t...
Recomendations please?
Click to expand...
Click to collapse
To fix the "cannot run, adbwin.dll missing", shift + right click on the folder containing adb.exe and select something like "Run as Command"
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
To fix the "cannot run, adbwin.dll missing", shift + right click on the folder containing adb.exe and select something like "Run as Command"
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I´m gonna try this and will post results. Thanks a lot.
kinfauns said:
Unfortunately, if the device isn't booting up, it won't charge. Like the guide I posted above says, the device needs to load up a ramdisk before it will charge. If all you see is that KF/Android logo, then it's still in the bootloader and it's not charging your battery.
First, you'll have to get your drivers in order so you can send the device fastboot commands. I suggest you disconnect the KF from your computer and make sure it's turned off. Use the KFU driver install file and get it to install the drivers again onto your machine. I'm not sure if it will help, but it wouldn't hurt to reboot your computer after that. When it's back up and running again, open up the device manager. When you connect the KF back up to your computer, it should automatically power up again... look at what device comes up as it boots. The first thing you see (hopefully) is "Android Phone -> Android ADB Interface" appear. If you see that, you can be reasonably sure you can send it fastboot commands.
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
There's a lot of "hopefully" things that have to go right for this to work. You've got a few compounded issues that are giving you problems and all of them have to get fixed for the battery to start charging again.
Click to expand...
Click to collapse
I tried to connect to a different pc. It does get recognized on device manager (as kindle) for few seconds and then it dissapears again...not sure what to do now in order to charge it...any suggestions?
Hey guys thanks for all the help so far, i bricked my kindle to the point of no shell after i tried to reflash the stock rom and was stuck in no mans land. So i ordered skorpn's factory cable (thanks again for sending it up north of the border) and when i plug it into the pc it loads the "kindle fire" screen ans stays there. It shows up in device manager but not when i look for it under adb devices and device won't be found in fastboot. Tried reinstalling the drivers and still no luck. Any ideas how i can get this thing back to the point of usability? Thanks for any help you have
andersonrel said:
I tried to connect to a different pc. It does get recognized on device manager (as kindle) for few seconds and then it dissapears again...not sure what to do now in order to charge it...any suggestions?
Click to expand...
Click to collapse
Fix your drivers. Read this:
http://forum.xda-developers.com/showthread.php?p=23747671
djsaxon said:
Hey guys thanks for all the help so far, i bricked my kindle to the point of no shell after i tried to reflash the stock rom and was stuck in no mans land. So i ordered skorpn's factory cable (thanks again for sending it up north of the border) and when i plug it into the pc it loads the "kindle fire" screen ans stays there. It shows up in device manager but not when i look for it under adb devices and device won't be found in fastboot. Tried reinstalling the drivers and still no luck. Any ideas how i can get this thing back to the point of usability? Thanks for any help you have
Click to expand...
Click to collapse
First, fix your drivers:
http://forum.xda-developers.com/showthread.php?p=23747671
Then:
http://forum.xda-developers.com/showthread.php?p=25400963
kinfauns said:
You'll have to issue the "fastboot oem idme bootmode 4000" on the command line. It will tell you that it's waiting for device... The next time it loops back around in its boot up process, it will send the command and hopefully get the bootmode back to normal. Then hook it up to your stock AC wall charger and if you are lucky it should continue to boot and charge your battery.
Click to expand...
Click to collapse
Well I gave this a shot and it said: "finished. total time: 0.080s"
but it's still just flashing the android logo with kindle fire underneath.
maw230 said:
Well I gave this a shot and it said: "finished. total time: 0.080s"
but it's still just flashing the android logo with kindle fire underneath.
Click to expand...
Click to collapse
That's because you have an entirely different problem.
http://forum.xda-developers.com/showthread.php?p=25400963
soupmagnet said:
That's because you have an entirely different problem.
http://forum.xda-developers.com/showthread.php?p=25400963
Click to expand...
Click to collapse
Thank you.
hey i can't doing that, when i type that code "fastboot..........img" cmd say <Waiting for devices> ?
jakelongryan said:
hey i can't doing that, when i type that code "fastboot..........img" cmd say <Waiting for devices> ?
Click to expand...
Click to collapse
There are several reasons why you would get the typical "waiting for device" message, so...
...here is a step-by-step guide instruct you in getting it working properly, quickly and efficiently.
Step 1. Start a new thread in the Q&A section.
Step 2. Explain in GREAT detail exactly what your problem is.
Step 3. Explain in GREAT detail exactly how your problem started.
Step 4. Explain in GREAT detail exactly what you have done to remedy the situation on your own.
Step 5. Explain in GREAT detail exactly what the device does and everything you see from the moment you press the power button until the problem presents itself.
Step 6. Wait patiently until someone of appropriate knowledge is kind enough to lend a hand.
soupmagnet said:
There are several reasons why you would get the typical "waiting for device" message, so...
...here is a step-by-step guide instruct you in getting it working properly, quickly and efficiently.
Step 1. Start a new thread in the Q&A section.
Step 2. Explain in GREAT detail exactly what your problem is.
Step 3. Explain in GREAT detail exactly how your problem started.
Step 4. Explain in GREAT detail exactly what you have done to remedy the situation on your own.
Step 5. Explain in GREAT detail exactly what the device does and everything you see from the moment you press the power button until the problem presents itself.
Step 6. Wait patiently until someone of appropriate knowledge is kind enough to lend a hand.
Click to expand...
Click to collapse
great advice and exactly what im gonna do. been searching for 2 weeks now reading and learning and still stuck so be looking out for my thread
Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
l_aios said:
Hi there!
I think I may have bricked my Fire TV Stick 1 (bought at launch in Germany)...
Current situation:
- stick turns on, shows white amazon logo on black background
- continuously rebooting; ~5s black screen, ~5s amazon logo
After months not having it used, I found out I may be able to root it by now. So I did research over the vast amount of threads and posts and was overwhelmed by the information... So I tried to get started but struggled to find the right steps and therefore maybe failed.
I updated it to 5.0.5 (stock) and tried King Root, then Kingo Root, which was a success.
I tried to use the TWRP 3.0.0-7 v2 zip and used the sh command from the respective thread (I thought that was it, since all my devices before used either TWRP or CWM).
To this point, all went through and I wanted to reboot into recovery, but there was only this generic (stock?) red text recovery screen. I waited to be sure, nothing happened and I unplugged it to reboot.
It booted fine and I reflashed the TWRP zip, in case I didn't do it properly. Again it did as expected.
I then pushed the latest prerooted 5.2.0.1 zip and rebooted to recovery, but again this generic screen, so I unplugged it early, I think.
From there on, I got stuck at the white amazon logo, see above.
I did not unlock the bootloader, adb shell confirmed it not being unlocked before.
During bootloops, I did not manage to get any control via adb or fastboot.
So, is it bricked once and for all? If not, how can I save it?
I don't care about anything stored on it.
I also have a Y-USB-OTG cable and connected a keyboard before, but could not interfere yet.
(If bricked, would a Teensy be of any use? I have one from CCast rooting days)
Thanks for reading and in advance.
Click to expand...
Click to collapse
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
mjnman said:
I had same problem with my fire stick when used the USB power of my TV.
Did you try to power the fire stick TV with the power point and USB adapter?
Click to expand...
Click to collapse
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
bula1ca said:
I guess you did not read enough.
At this point in time you can only root (kingoroot or kingroot) and replace root with SuperSu on a Firestick. TWRP (recovery) can not be installed because it was not released by rbox as of yet, that particular recovery\pre-rooted image is for firetv1 upgraded to OS5 and not for firestick.
Sorry man.
Have you tried to connect to a computer via USB and run kingoroot or kingroot for windows (whatever you used)? It is a small chance that will recover but it is a slim one....
Click to expand...
Click to collapse
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
l_aios said:
I could not remember, so I just retried it with two different chargers and two different cables (both used to power my Nexus 5).
Unfortunately resulting in the very same loop... But thanks nonetheless.
Dang... Usually I don't make mistakes this dumb. Guess I learned my first lesson. I'll try to trace my mistake though, for future attempts.
I rooted it with the Kingo app, I think, and got that typical "stuck at 90%" and rebooted it like others did. It rebooted fine and Kingo verified it rooted.
I did not use Windows, I use Ubuntu, occasionally with Wine, yet I had no luck passing USB devices to it. (And always these missing libs...)
Normally, adb and fastboot (console) work fine (i.e. with my phone).
Now I have no chance to interfere with the bootloop, I think.
IIRC, sometimes I could spam commands and at one point adb was stuck at "waiting for device".
I tried to reproduce it just now, but could not get it again.
So, should I try adb or fastboot on another computer to be sure?
Would King(o) for Windows be of any help at this point? If so, what would be my best bet to catch it at some point I can recover it?
Is there any other way I could try? From my nooby perspective, could the bootsplash be an entrance for fastboot? Could it be just stuck trying to access erroneous partitions?
At this point I would try the most crazy and risky idea, since it is unusable anyway.
Thanks both of you for your answers.
Click to expand...
Click to collapse
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"IF YOU RUN INTO SOFTBRICK ISSUE (stuck at fire tv logo)
Make sure you have ADB drivers properly installed in your windows pc/laptop.
connect a genuine usb lead to the firestick/pc.
download the windows version of KINGO ROOT and install it.
open KINGO ROOT on the pc with Fire Stick connected up to pc and tv.
wait for the button to pop up and click root.
if you dont see AFTV or get enable debugging in the KINGO ROOT program on pc/laptop please unplug the stick from usb and replug it back in.
if this still wont work restart the pc/laptop or try another pc/laptop.
you should after clicking root boot back up into your homescreen, if it doesnt boot back into your homescreen automatically, wait around 5 minutes and unplug usb and re-plug it again. "
bula1ca said:
Do you still have root? Is your stick responding to the su command?
If so read this post: http://forum.xda-developers.com/fire-tv/help/guidance-recovering-bootloop-firetv-t3446902
If not:
Try kingoroot for windows however it is a slim change in my opinion as you wrote a FireTv image to your FireStick.
Copy and paste from: http://forum.xda-developers.com/fire-tv/development/guide-fire-stick-replace-king-o-root-t3440923
"[...]"
Click to expand...
Click to collapse
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
l_aios said:
Thanks for the links, but from what I see, I need to get past the bootloader splash for adb to work. I'm stuck at the white "amazon" splash, not the colored "FireTV Stick" splash after the amazon one.
Sorry for not making it clear (and for that amount of text that maybe hid it)...
From what I understand and recall, I did only flash the recovery, right? Or does it automatically flash the zip I pushed to internal storage?
And what confuses me, the first attempt booting into recovery AFTER flashing the wrong one I got the former mentioned screen with red text. Reboot worked and the Stick was running. So I did retry and got the same red text after rebooting to recovery. I assumed it did not flash again and unplugged it earlier than the first attempt. Since then it got stuck at the white bootsplash.
Since I am still a noob, it seems to me the system wasn't touched, maybe a faulty recovery integrity forcing the bootloader to loop.
Click to expand...
Click to collapse
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
bula1ca said:
I have no idea what you did however it will not automatically flash your zip, problem is you installed TRWP that was not meant for Firestick and overwrote its booting sequence. You most probably would had recover from your first attempt by re-installing a new image but once you tried to install it again it most probably finished writing the whole thing and damaged booting sequence.
Click to expand...
Click to collapse
Yeah, sad thing I got the wrong device, should have taken my time even more...
I googled the screen I got to two times before getting stuck:
http://forum.xda-developers.com/showpost.php?p=65968901&postcount=60
First time I waited approx. 15 minutes before pulling the plug to reboot. Since I noticed no difference I tried again and got the same screen. But this time I pulled the plug earlier, <1 minute.
I'd like to add that my bootloader was locked. Can I damage the booting sequence by corrupting the recovery or was my mistake that major to be able to do that?
I googled some key combinations to get into recovery or to bypass it, but I don't know if I get the right keys.
With my remote control I don't think I have enough time to hold the keys. Additionally I have a USB keyboard (Cherry KC1000; if possible, which keys btw?) and may be able to connect it via powered Y OTG cable.
So if anyone got any further input or ideas for me to rescue my FTVS, I'd be glad to receive it.
Thanks to all.
Anyone else maybe an idea?
The thing is, I cannot believe it is unsavable.
To summarize the current state (please see full details above):
- stuck in bootloop, white amazon logo
- flashed wrong recovery, after first flash the system booted, after second flash it got stuck (characteristics above)
- never flashed anything other than recovery
Strange thing it booted in first place, but now it refuses. Also I got the screen I mentioned above and unplugged as described above.
Can I possibly bypass the recovery check and try to boot directly to system? Or maybe interrupt for fastboot access?
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Kramar111 said:
If connected to PC, can you see it thru 'lsusb'? Or 'dmesg | tail'?
Click to expand...
Click to collapse
I tried both
watch -n 0.5 'dmesg | tail'
and
watch -n 0.5 'lsusb'
but with no identification whatsoever.
I double-checked with my Nexus 5 on the same port with the same cable, it identified fine.
One last bump for ideas before putting it into the trash.
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 purchased a used Fire TV 2nd gen online but when I boot it up, it goes into some kind of kiosk slideshow for 1st gen Amazon Echo devices that I can't exit.
It boots normally at first with the Fire TV logo an all but there's no config screen or anything. It boots to a white AMAZON ECHO screen with pics of the original Echo device then goes into a slide show showing all the various features of Amazon echo. The remote doesn't sync and the device will only show up on the Fire TV remote app for a few seconds before disappearing after boot. I can plug in a physical keyboard and if I press the ESC key, the screen will go black for a second before re-starting the slide show from the beginning. So far I've not been able to find any other keyboard functions that react, only the ESC key so far.
If I had to guess, I'd say it probably has a much older version of the OS on it as the slide show is for the older generations of Echo.
I'm assuming this used to be some kind of demo device, maybe from Best Buy or something but does anyone know how to get out of this slide show so it can be used as a normal device or is this thing just useless? Suggestions?
Hannover2k said:
I purchased a used Fire TV 2nd gen form ebay but when I boot it up, it goes into some kind of kiosk slideshow for Amazon Echo that I can't exit.
It boots normally at first with the Fire TV logo an all but there's no config screen or anything. It boots to a white AMAZON ECHO screen with pics of the original Echo device then goes into a slide show showing all the various features of Amazon echo. The remote doesn't sync and the device will only show up on the Fire TV remote app for a few seconds before disappearing after boot. I can plug in a physical keyboard and if I press the ESC key, the screen will go black for a second before re-starting the slide show from the beginning. So far I've not been able to find any other keyboard functions that react, only the ESC key so far.
If I had to guess, I'd say it probably has a much older version of the OS on it as the slide show is for the older generations of Echo.
I'm assuming this used to be some kind of demo device, maybe from Best Buy or something but does anyone know how to get out of this slide show so it can be used as a normal device or is this thing just useless? Suggestions?
Click to expand...
Click to collapse
Just as an update, I found that if I plug in a USB keyboard, pressing ALT+ESC will pop up a menu telling me to press the home button if I wish to return to the home screen. No remote works with it yet so that doesn't help much. Pressing ALT+Space will bring up what appears to be the FireTV search keyboard but typing doesn't bring up anything, it just echos what I type and there's no 'ENTER' key to submit anything.
If I do this immediately after the slideshow comes up, it will prompt that there's no network connection and take me to the network settings menu. I tried plugging in a LAN cable but the device doesn't seem to pull up an IP address. I manually entered an IP but was unable to find it on the network. Even tried using the APPS2FIRE app to see if it could see it in the search but it doesn't. I connected it to wifi successfully but same issue, it doesn't seem to actually pull an IP address as I can't see it on my network when I scan for it. The network settings know when the LAN is plugged in and removed though.
Plugging in USB A-A doesn't seem to do anything. I tried running the Unbrick batch file from one of the other posts but it's intended to work on non-rooted devices with the jumper trick, I think, and while it does kick off the script, it stops at 0% and never does anything. I'm sure this is an older OS that can still be rooted but I just don't know how to get to anything in it since I can't get into ADB.
Any suggestions would be appreciated though!
Hannover2k said:
I'm sure this is an older OS that can still be rooted but I just don't know how to get to anything in it since I can't get into ADB.
Any suggestions would be appreciated though!
Click to expand...
Click to collapse
If you can't get device to show up on adb devices via terminal/command prompt or access settings menu I don't think there's much you can do.
1.Try doing a scan with Fing Network Tools and see if IP shows.
2. Try downloading and installing FireTV remote App on your phone and connecting if it finds stick.
Without adb being activated on the stick, and settings menu unavailable to enable adb there is not much else for it m8, these ebay sticks are dodgy to say the least I've been stung a few times. Even bought one and opened it to find the heat shield casing missing and clk broke lol
Bertonumber1 said:
If you can't get device to show up on adb devices via terminal/command prompt or access settings menu I don't think there's much you can do.
1.Try doing a scan with Fing Network Tools and see if IP shows.
2. Try downloading and installing FireTV remote App on your phone and connecting if it finds stick.
Without adb being activated on the stick, and settings menu unavailable to enable adb there is not much else for it m8, these ebay sticks are dodgy to say the least I've been stung a few times. Even bought one and opened it to find the heat shield casing missing and clk broke lol
Click to expand...
Click to collapse
I'll give those a shot. I tried the jumper technique from the Unbrick Fire TV 2 post and was able to get partway through that process and to the prompt where it tells me to remove the jumper and press enter but it gets an error after copying the files, just before it should boot to twrp. something about the source path being empty. I can post a pic if that's helpful. I think may have forgotten to run the disable modemmanager command so I'll give that another try later. I didn't realize you had to run that every time you reboot linux. I know just enough to be dangerous with it.
Hannover2k said:
I'll give those a shot. I tried the jumper technique from the Unbrick Fire TV 2 post and was able to get partway through that process and to the prompt where it tells me to remove the jumper and press enter but it gets an error after copying the files, just before it should boot to twrp. something about the source path being empty. I can post a pic if that's helpful. I think may have forgotten to run the disable modemmanager command so I'll give that another try later. I didn't realize you had to run that every time you reboot linux. I know just enough to be dangerous with it.
Click to expand...
Click to collapse
Yeah great have a look here too
https://docs.google.com/document/u/0/d/1zYtqmf4RfLOkrPyPjf1C0CjAZf_0E1JohIlTyVY5kGs/mobilebasic
Files here
https://drive.google.com/drive/u/0/mobile/folders/1GbMTBHuFhwT_uyZaJs0ApsG_RQ5Wg_7F
Should work :good:
Bertonumber1 said:
Yeah great have a look here too
https://docs.google.com/document/u/0/d/1zYtqmf4RfLOkrPyPjf1C0CjAZf_0E1JohIlTyVY5kGs/mobilebasic
Files here
https://drive.google.com/drive/u/0/mobile/folders/1GbMTBHuFhwT_uyZaJs0ApsG_RQ5Wg_7F
Should work :good:
Click to expand...
Click to collapse
Unfortunately I can't use those methods. While I can get into the network settings, I can't get into any other settings. I never I never left it connected to wifi so I've been using a LAN cable to test. Booting without the LAN causes it to get an error and takes me to the network settings but I can't get to anything else from there.
Been messing with the jumper method from https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303 but not having any luck yet as per the attached pic. Also tried the unbrick method which gets stuck at 000000200: 0% every time. Just for the heck of it, I shorted DAT0 and ran it and it popped up an error saying it can't locate a 'system' partition. The unit still boots up with the fire tv logo and goes into that demo mode so I'm sure there's a partition present. This is really a challenge! Running out of things to try though.
Hannover2k said:
Unfortunately I can't use those methods. While I can get into the network settings, I can't get into any other settings. I never I never left it connected to wifi so I've been using a LAN cable to test. Booting without the LAN causes it to get an error and takes me to the network settings but I can't get to anything else from there.
Been messing with the jumper method from https://forum.xda-developers.com/fire-tv/development/unbrick-fire-tv-stick-2-anti-rollback-t3986303 but not having any luck yet as per the attached pic. Also tried the unbrick method which gets stuck at 000000200: 0% every time. Just for the heck of it, I shorted DAT0 and ran it and it popped up an error saying it can't locate a 'system' partition. The unit still boots up with the fire tv logo and goes into that demo mode so I'm sure there's a partition present. This is really a challenge! Running out of things to try though.
Click to expand...
Click to collapse
You may have a stick that cannot be rooted/modified via amonet, one with dl mode disabled. These devices around December 2019 started to appear on the market and there's no way round them.
Bertonumber1 said:
You may have a stick that cannot be rooted/modified via amonet, one with dl mode disabled. These devices around December 2019 started to appear on the market and there's no way round them.
Click to expand...
Click to collapse
The device is a Fire TV 2nd gen Sloane so I would expect it to work like others I've rooted, but that kiosk os might do just what you said and disabled DL mode. I'll still play with it a bit but not sure what else can be done. Maybe some new method will come along in the future so I'll just hold on to it.
Thanks for all the input though. Greatly appreciated.
Hannover2k said:
The device is a Fire TV 2nd gen Sloane so I would expect it to work like others I've rooted, but that kiosk os might do just what you said and disabled DL mode. I'll still play with it a bit but not sure what else can be done. Maybe some new method will come along in the future so I'll just hold on to it.
Thanks for all the input though. Greatly appreciated.
Click to expand...
Click to collapse
Sorry mate my bad I thought it was a stick you had I was helping some other guy in firestick tank forum and got mixed up.
Try the short method again only when you get the error :
Leave dc power on (plugged into box)
Remove USB a to USB a cable
Close terminal
Open new terminal up in amonet once again
Run the boot-rom step again BUT hit enter TWICE
Then plug USB cable back in
Pull the dc power and plug it in again
The script should go through
I followed this from another member and it always works for me, has worked on numerous Sloanes. Give it a go, worth a shot mate
Bertonumber1 said:
Sorry mate my bad I thought it was a stick you had I was helping some other guy in firestick tank forum and got mixed up.
Try the short method again only when you get the error :
Leave dc power on (plugged into box)
Remove USB a to USB a cable
Close terminal
Open new terminal up in amonet once again
Run the boot-rom step again BUT hit enter TWICE
Then plug USB cable back in
Pull the dc power and plug it in again
The script should go through
I followed this from another member and it always works for me, has worked on numerous Sloanes. Give it a go, worth a shot mate
Click to expand...
Click to collapse
Thanks for the info, it's worth a try. Just to clarify, when you say to press enter twice, do you mean to press it twice at the prompt where it tells you to remove the short and press enter?
Hannover2k said:
Thanks for the info, it's worth a try. Just to clarify, when you say to press enter twice, do you mean to press it twice at the prompt where it tells you to remove the short and press enter?
Click to expand...
Click to collapse
Hey @Hannover2k, yeah the Sloane is stubborn to root, just keep at it, once you see ***remove short and hit enter** and get an error try leaving it switched on but remove USB, then run the script again and hit enter again after you hit it once, disconnect/reconnect the dc power and plug USB in without the short (if displaying remove short) . Should go through
Another thing...
This what happened to me the other day. If your preloader is gone (it's displaying remove short when there is no short). Disconnect power, disconnect USB, run the the script and connect power and wait 50-70 seconds then plug USB back in.
As I said these Sloanes are tough but you should get it, using the short "jumper" method m8
Bertonumber1 said:
Hey @Hannover2k, yeah the Sloane is stubborn to root, just keep at it, once you see ***remove short and hit enter** and get an error try leaving it switched on but remove USB, then run the script again and hit enter again after you hit it once, diconnect/reconnect the dc power. Should go through
Another thing...
This what happened to me the other day. If your preloader is gone (it's displaying remove short when there is no short). Disconnect power, disconnect USB, run the the script and connect power and wait 50-70 seconds then plug USB back in.
As I said these Sloanes are tough but you should get it, using the short "jumper" method m8
Click to expand...
Click to collapse
Sorry is I'm missing something here. I've been trying to do your method and while I've been getting different error messages and results, I'm still not quite sure I'm doing it right.
After I get the first error after removing the short, you mention above to remove the USB then run the script again, etc. At what point do I plug the USB cable back in? Do I plug the USB back in after removing the power? When I do remove the power, do i need to reconnect the Jumper before plugging it back in?
Sorry if I'm lame, I've just done this jumper thing 100 times and can get many different results but not the one we're looking for! lol
UPDATE: Holy cow, I got it to work the very next time after posting the message! Here's what I did:
1) Ran the script, connected jumper and powered on the device.
2) Got error message.
3) Unplugged USB then re-ran script, pressing enter again after running the command.
4) Plugged USB back in.
I did not reconnect the jumper. When the USB cable was re-connected it did display a message to remove the jumper and press enter, however I did not have to do that. All kinds of stuff started flying all over the screen, then it got to;
Clearing Preloader Header
Flashing Tee
Flashing Bootloader
Flashing Unbrick Image
Flashing Boot
Booting to TWRP
I'm literally grinning ear to ear right now! Thanks for all your help with this! Even if it doesn't work at this point, I'm very happy to have gotten this far!
I can get these kiosk devices for $20 each. Box only, no power or remote. Does anyone think it would be worth it to buy a few of them and try to sell them off with refreshed imaged on them? There's a lot available so just wondering.
Hannover2k said:
Sorry is I'm missing something here. I've been trying to do your method and while I've been getting different error messages and results, I'm still not quite sure I'm doing it right.
After I get the first error after removing the short, you mention above to remove the USB then run the script again, etc. At what point do I plug the USB cable back in? Do I plug the USB back in after removing the power? When I do remove the power, do i need to reconnect the Jumper before plugging it back in?
Sorry if I'm lame, I've just done this jumper thing 100 times and can get many different results but not the one we're looking for! lol
UPDATE: Holy cow, I got it to work the very next time after posting the message! Here's what I did:
1) Ran the script, connected jumper and powered on the device.
2) Got error message.
3) Unplugged USB then re-ran script, pressing enter again after running the command.
4) Plugged USB back in.
I did not reconnect the jumper. When the USB cable was re-connected it did display a message to remove the jumper and press enter, however I did not have to do that. All kinds of stuff started flying all over the screen, then it got to;
Clearing Preloader Header
Flashing Tee
Flashing Bootloader
Flashing Unbrick Image
Flashing Boot
Booting to TWRP
I'm literally grinning ear to ear right now! Thanks for all your help with this! Even if it doesn't work at this point, I'm very happy to have gotten this far!
I can get these kiosk devices for $20 each. Box only, no power or remote. Does anyone think it would be worth it to buy a few of them and try to sell them off with refreshed imaged on them? There's a lot available so just wondering.
Click to expand...
Click to collapse
@Hannover2k Yeah that's you got it sorted then, I tried to explain that method but didn't do a very good job of it lol, make sure you push pre-rooted rom and supersu 2.82 zip to /sdcard, and flash.
Please Remember and note that you cannot flash unsigned zips such as magisk to the Sloane as you're bootloader remains incarcerated , if you're device has cleared preloader and you've entered into twrp it should work
Ps. if you can get a Sloane for that price pm me and we'll sort something, doesn't matter about power cables, remotes etc
Bertonumber1 said:
@Hannover2k Yeah that's you got it sorted then, I tried to explain that method but didn't do a very good job of it lol, make sure you push pre-rooted rom and supersu 2.82 zip to /sdcard, and flash.
Please Remember and note that you cannot flash unsigned zips such as magisk to the Sloane as you're bootloader remains incarcerated , if you're device has cleared preloader and you've entered into twrp it should work
Ps. if you can get a Sloane for that price pm me and we'll sort something, doesn't matter about power cables, remotes etc
Click to expand...
Click to collapse
After flashing the pre-rooted image the first time, everything seemed to work except whenever I restarted via the settings menu, it would show the TWRP pre boot screen but allowing it to continue to boot normally would result in a boot loop. Performing a power cycle would cause the device to skip over the TWRP menu and boot right into the device.
Tried clearing the SD partition and dalvik to free up space as it was only showing about 1.2gb free after the flash. Got the free space back but still the same boot issue after flash, though it did work after a power cycle as opposed to restarting, which I rarely do anyways.
Remembering the Kiosk was for the original echo devices, I got to thinking about it having an older OS again and maybe not liking being flashed directly to the latest version so I re-flashed it to v5.2.6.7_r1. It would boot loop after the TWRP pre login screen but after the first loop it would boot properly. Went ahead and flashed it back to 5.2.7.3_r1 and everything seems to be working perfectly now. Restarts properly and all functionality seems to be present.
I really appreciate your assistance with this. I had them send me another one so I can try this method once more and if it works again, I'll definitely let you know and we'll work something out.
-Han
Hannover2k said:
After flashing the pre-rooted image the first time, everything seemed to work except whenever I restarted via the settings menu, it would show the TWRP pre boot screen but allowing it to continue to boot normally would result in a boot loop. Performing a power cycle would cause the device to skip over the TWRP menu and boot right into the device.
Tried clearing the SD partition and dalvik to free up space as it was only showing about 1.2gb free after the flash. Got the free space back but still the same boot issue after flash, though it did work after a power cycle as opposed to restarting, which I rarely do anyways.
Remembering the Kiosk was for the original echo devices, I got to thinking about it having an older OS again and maybe not liking being flashed directly to the latest version so I re-flashed it to v5.2.6.7_r1. It would boot loop after the TWRP pre login screen but after the first loop it would boot properly. Went ahead and flashed it back to 5.2.7.3_r1 and everything seems to be working perfectly now. Restarts properly and all functionality seems to be present.
I really appreciate your assistance with this. I had them send me another one so I can try this method once more and if it works again, I'll definitely let you know and we'll work something out.
-Han
Click to expand...
Click to collapse
The recovery partition maybe corrupted.
You may try updating twrp to the latest 3.0.05 from Sloane Twrp recovery page.
There you can download the file from here :
https://www.mediafire.com/file/brae6r8lu1np5jm/firetv2_recovery_v6.zip/file
,push it to Sloane /sdcard and run command
from pc
adb shell
Then run:
sh /sdcard/firetv2_recovery_v6.zip
Reboot
That should fix it.
As soon as you update TWRP
Reboot and flash the pre-rooted firmware and supersu 2.82.zip
Then wipe cache, dalvik
Let it boot up and then factory reset (data, dalvik, cache)
Reboot and it should be okay
Bertonumber1 said:
The recovery partition maybe corrupted.
You may try updating twrp to the latest 3.0.05 from Sloane Twrp recovery page.
There you can download the file from here :
https://www.mediafire.com/file/brae6r8lu1np5jm/firetv2_recovery_v6.zip/file
,push it to Sloane /sdcard and run command
from pc
adb shell
Then run:
sh /sdcard/firetv2_recovery_v6.zip
Reboot
That should fix it.
As soon as you update TWRP
Reboot and flash the pre-rooted firmware and supersu 2.82.zip
Then wipe cache, dalvik
Let it boot up and then factory reset (data, dalvik, cache)
Reboot and it should be okay
Click to expand...
Click to collapse
Thanks for the info. The image I installed already had that version of TWRP installed on it but like I said in my last comment, flashing to an older rom then re-flashing back to the latest one seems to have resolved the issue.
No more Kiosk mode, though I wish I could have gotten a look at those files just to see what was going on there.
Anyways, all good now and I have another one of those kiosk units I'm going to try the process again on and if it works, I have access to a lot of these devices so I may refresh them and sell them cheap.
Thanks again for everyones input! Still surprised I got it working normal again.
Bertonumber1 said:
@Hannover2k Yeah that's you got it sorted then, I tried to explain that method but didn't do a very good job of it lol, make sure you push pre-rooted rom and supersu 2.82 zip to /sdcard, and flash.
Please Remember and note that you cannot flash unsigned zips such as magisk to the Sloane as you're bootloader remains incarcerated , if you're device has cleared preloader and you've entered into twrp it should work
Ps. if you can get a Sloane for that price pm me and we'll sort something, doesn't matter about power cables, remotes etc
Click to expand...
Click to collapse
Good news!
I was given a 2nd unit with the same 'issue' and was able to get it to start taking the image within a couple mins. The guy who has them can't do anything with them and has lowered his price per unit so are these worth anything to anyone?
Again, it's the box only, no power cords or remote but I don't expect that to be an issue for someone looking to replace one.
I hope I'm not breaking any rules by asking that but I'm open to any thoughts on this.
-Han
Hannover2k said:
Good news!
I was given a 2nd unit with the same 'issue' and was able to get it to start taking the image within a couple mins. The guy who has them can't do anything with them and has lowered his price per unit so are these worth anything to anyone?
Again, it's the box only, no power cords or remote but I don't expect that to be an issue for someone looking to replace one.
I hope I'm not breaking any rules by asking that but I'm open to any thoughts on this.
-Han
Click to expand...
Click to collapse
@Bertonumber1
Sus_i said:
@Bertonumber1
Click to expand...
Click to collapse
Yeah I've already replied via pm to @Hannover2k I've already bought one with power brick and remote for Roger @Sus_i hannover2k only has the Sloane itself AFAIK I got the full shebang for £27 so it's all good perhaps @Hannover2k can provide a spare and that's us got a couple to got to work on in the name of furthering development
Bertonumber1 said:
Yeah I've already replied via pm to @Hannover2k I've already bought one with power brick and remote for Roger @Sus_i hannover2k only has the Sloane itself AFAIK I got the full shebang for £27 so it's all good perhaps @Hannover2k can provide a spare and that's us got a couple to got to work on in the name of furthering development
Click to expand...
Click to collapse
Hannover2k said:
Sorry is I'm missing something here. I've been trying to do your method and while I've been getting different error messages and results, I'm still not quite sure I'm doing it right.
After I get the first error after removing the short, you mention above to remove the USB then run the script again, etc. At what point do I plug the USB cable back in? Do I plug the USB back in after removing the power? When I do remove the power, do i need to reconnect the Jumper before plugging it back in?
Sorry if I'm lame, I've just done this jumper thing 100 times and can get many different results but not the one we're looking for! lol
UPDATE: Holy cow, I got it to work the very next time after posting the message! Here's what I did:
1) Ran the script, connected jumper and powered on the device.
2) Got error message.
3) Unplugged USB then re-ran script, pressing enter again after running the command.
4) Plugged USB back in.
I did not reconnect the jumper. When the USB cable was re-connected it did display a message to remove the jumper and press enter, however I did not have to do that. All kinds of stuff started flying all over the screen, then it got to;
Clearing Preloader Header
Flashing Tee
Flashing Bootloader
Flashing Unbrick Image
Flashing Boot
Booting to TWRP
I'm literally grinning ear to ear right now! Thanks for all your help with this! Even if it doesn't work at this point, I'm very happy to have gotten this far!
I can get these kiosk devices for $20 each. Box only, no power or remote. Does anyone think it would be worth it to buy a few of them and try to sell them off with refreshed imaged on them? There's a lot available so just wondering.
Click to expand...
Click to collapse
Just wanted to add my Order of Operations to this post. I also bought one of these "Kiosk" boxes without remote or power supply for $13 off of eBay. Great deal, I thought, if I can get it to root. It appears that the order in which you perform the steps is unique to your setup. After trying all the above suggestions with no success (similar errors as listed above), here's what worked for me:
1. Plug in male-to-male USB cable between FTV2 and Linux box
2. Short DAT0 pin on FTV2 board
3. Connect FTV2 AC power
4. Run script
5. Remove short, press enter once when prompted
After TWRP installed (and I figured out how to use it), I was successful in having a usable FTV2 with all of the perks this process brings. Thanks to all who contributed to make this possible, and an extra big thanks to @Hannover2k for being the first to try this on these specifically-challenged boxes. It was a huge help!