Related
Hey y'all,
I am rooting / rom-ing my third KF.
I could not get TWRP to install so I installed CWM that comes with the KFU
I installed Jandycane and the most current gapps
From then on, the Kindle gets stuck at the boot animation
I have tried other options in KFU, but everything involving fastboot does not work. The kindle shows up as a composite device in the device manager, and is able to be adb-ed into.
In KFU, I see the bootmode being 4000. When I tried the idme command to change it to recovery, it told me that it could not accept the idme command.
I've tried going using the adb shell to push fiels and create directories, but have failed. Su does not work, mkdir does not work, and chmod does not work.
Additionally I have tried the KF Unbrick 1.1 and none of the options seem to do anything.
I am running out of options here. I have tried these procedures on two PCs without avail.
Before I installed the current rom, I have made a backup of the stock rom. Is there any way I could adb into the device and restore it? Would this be a valid way to fix this up?
Can anyone suggest anything else that I have not tried?
Anyone?
When I try to push fbmode from here: http://forum.xda-developers.com/showthread.php?t=1414832
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb push fbmode /data/local/tmp
failed to copy 'fbmode' to '/data/local/tmp': No such file or directory
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>
Now lets see if I can escalate my privileges
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell
[email protected]:/ $ su
su
Segmentation fault
[email protected]:/ #
Now lets see if I can push fbmode regardless
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell
[email protected]:/ $ cd /data/local/tmp
cd /data/local/tmp
/system/bin/sh: cd: /data/local/tmp: No such file or directory
2|[email protected]:/ $ cd /data/local/
cd /data/local/
/system/bin/sh: cd: /data/local: No such file or directory
2|[email protected]:/ $ cd /data/
cd /data/
[email protected]:/data $ ls
ls
opendir failed, Permission denied
255|[email protected]:/data $
So much for adb ... how about that fastboot
Every time I do anything with fastboot it says waiting for device:
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>fastboot -i 0x1949 flash recovery twrp.img
< waiting for device >
Are there any devices showing?
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>fastboot devices
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>
fastboot does not see any devices whereas adb does...
I have tried sending the fastboot command while the device is off and then turning it on. The kindle just hangs at the kindle fire screen.
EDIT: I switched computers, and it got back into previous state at being stuck at the animation screen
This is what happens when I try to install TWRP in KFU:
Code:
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
failed to copy 'files\fbmode' to '/data/local/fbmode': No such file or directory
Unable to chmod /data/local/fbmode: No such file or directory
/system/bin/sh: /data/local/fbmode: not found
The kindle has been told to reboot in Fastboot Mode.
< waiting for device >
Can you actually put your device into fastboot mode? You can only use fastboot commands when the bootloader has put the device into fastboot mode. If you can get output from any adb commands, you are not in fastboot mode. Look at this guide and see if you can put the KF into fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
What bootloader do you have installed on the device? (Describe the first bootlogo you see. Refer to the above guide.)
What error do you get when you attempt to set the bootmode with idme?
Where are you running your adb commands? When you are stuck on the boot animation or in recovery?
Can you even get to your recovery?
My guess is you've somehow corrupted the system software on your ROM installation. If you can get to recovery, you'll probably need to reflash your ROM. If you can get the device into fastboot mode, you can get to recovery. If can't do either of those, you'll need a factory cable or be willing to open up the case.
kinfauns said:
Can you actually put your device into fastboot mode? You can only use fastboot commands when the bootloader has put the device into fastboot mode. If you can get output from any adb commands, you are not in fastboot mode. Look at this guide and see if you can put the KF into fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
What bootloader do you have installed on the device? (Describe the first bootlogo you see. Refer to the above guide.)
What error do you get when you attempt to set the bootmode with idme?
Where are you running your adb commands? When you are stuck on the boot animation or in recovery?
Can you even get to your recovery?
My guess is you've somehow corrupted the system software on your ROM installation. If you can get to recovery, you'll probably need to reflash your ROM. If you can get the device into fastboot mode, you can get to recovery. If can't do either of those, you'll need a factory cable or be willing to open up the case.
Click to expand...
Click to collapse
That would make sense. I cannot change the bootmode from 4000, so that's why fastboot does not work. I feel dumb for not thinking this through.
It has CWM installed as I could not load TWRP initially due to a poor connection.
This is what I get when I try to change the bootmode:
Code:
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell su -c 'idme bootmode 4002'
Segmentation fault
<idme> write 4002 to offset 0x1000
C:\Users\xxx\Desktop\Kindle Fire Utility\tools>adb shell idme bootmode 4002
<idme> Invalid permission
I cannot get into recovery as I cannot get the tablet to boot into anything but the ROM istelf (or try to, as it never boots into anything but just loops the boot animation)
Tell me about this factory cable. I'm sure I have it somewhere among all of my micro USB cables...
The boot pattern is as follows: kindle fire (white orange/stock) -> jandycane boot animation that runs forever
There is no triangle or any press the power button to boot into recovery.
http://forum.xda-developers.com/showpost.php?p=30376760
soupmagnet said:
http://forum.xda-developers.com/showpost.php?p=30376760
Click to expand...
Click to collapse
I cannot get the kindle to boot into a ROM, so I cannot use the terminal app.
Can I get an adb shell and push these files?
Also, per my post above, it seems that something sketch is going on with my superuser settings...
Yes, if you have a working adb, you can absolutely push those files. The path will be slightly different though. Instead of ~/local/tmp, you will push the files to /data/local/tmp then execute:
Code:
adb shell chmod 755 /data/local/tmp/rcmode
adb shell /data/local/tmp/rcmode
Looking through your other posts I see you are trying to invoke the shell and enter the commands seperately. Try again, but only this time add "adb shell" to the command itself, as above, and see if that makes a difference.
Also, I've seen both /data/local and /data/local/tmp used but I've always used /data/local/tmp
[Edit:] if you still get a "No such file or directory" error, see if you can create it:
Code:
adb shell mkdir /data/local/tmp
Zlatty said:
I cannot get the kindle to boot into a ROM, so I cannot use the terminal app.
Can I get an adb shell and push these files?
Also, per my post above, it seems that something sketch is going on with my superuser settings...
Click to expand...
Click to collapse
KFU's included version of CWM recovery does not flash ICS (and very likely JB) ROMS correctly. This is a bug known to corrupt the flash.
It not likely you'll be able to do anything meaningful with the system currently installed on your Kindle Fire. Unfortunately for you, that probably includes using idme or pushing anything that might help you change bootmodes. Of course, I may be wrong and you might find another way out of the mess, but the easiest way for you to fix this is to use a factory cable, put the KF into fastboot mode, flash TWRP, boot into recovery so you can flash a new bootloader and ROM.
factory cable...
http://forum.xda-developers.com/showthread.php?t=1550999
fastboot mode...
http://forum.xda-developers.com/showthread.php?t=1668159
beginner's guide...
http://forum.xda-developers.com/showthread.php?t=1552547
supplement for rooting... installing a ROM... etc...
http://forum.xda-developers.com/showthread.php?t=1638452
EDIT: You can try what soupmagnet suggested while I was typing out my post, but you've already shown that you cannot access the /data partition. I think it's going to be something more than simply just an unmounted partition.
I hadn't really thought about mounting the data partition...it's worth a shot either way.
soupmagnet said:
I hadn't really thought about mounting the data partition...it's worth a shot either way.
Click to expand...
Click to collapse
Well my adventure just keeps getting worse and worse. I charged the kindle last night to ensure enough battery life for today. It is suck at the kindle fire logo now. I have the drivers loaded correctly and my computer sees the kindle. However I cannot adb or fastboot the device. It also went from composite device to adb device in the device manager.
EDIT:
Was able to install FFF and got to boot into recovery. CWM 5.2.0.7.
In adb I tried to get super user permissions
C:\android-sdk-windows\platform-tools>adb shell
~ # su
su
/sbin/sh: su: not found
~ #
Click to expand...
Click to collapse
What are my options at this point. KFU cannot download and install TWRP. I cannot manually push it since I dont have su. KFU's install super user function does not work as it tries to install TWRP.
Zlatty said:
Well my adventure just keeps getting worse and worse. I charged the kindle last night to ensure enough battery life for today. It is suck at the kindle fire logo now. I have the drivers loaded correctly and my computer sees the kindle. However I cannot adb or fastboot the device. It also went from composite device to adb device in the device manager.
EDIT:
Was able to install FFF and got to boot into recovery. CWM 5.2.0.7.
In adb I tried to get super user permissions
What are my options at this point. KFU cannot download and install TWRP. I cannot manually push it since I dont have su. KFU's install super user function does not work as it tries to install TWRP.
Click to expand...
Click to collapse
Ok, so while I was in CWM, I mounted the SD card, downloaded and transfered a flashable TWRP found here http://forum.xda-developers.com/showpost.php?p=28664718&postcount=127
I flashed the zip and now I have TWRP working.
Zlatty said:
Ok, so while I was in CWM, I mounted the SD card, downloaded and transfered a flashable TWRP found here http://forum.xda-developers.com/showpost.php?p=28664718&postcount=127
I flashed the zip and now I have TWRP working.
Click to expand...
Click to collapse
I could not get twrp to boot into normal. So I used KFU to change to 4000 mode.
Code:
***********************************************
* Activating Normal (4000) *
***********************************************
< waiting for device >
... OKAY [ 0.081s]
finished. total time: 0.082s
rebooting...
finished. total time: 0.001s
The kindle has been told to reboot in Normal Mode.
Press any key to continue . . .
Everything went better than expected.... w00t!
[Q&A] [REF] Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutor
Q&A for [REF] Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [REF] Installing Kindle Fire HD 8.9" 2nd-Bootloader + TWRP Complete Tutorial. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Flashing TWRP Help On Version 8.5.1
I broke my flashed kindle Fire HD 8.9 by dropping it on accident. This had CM.11 on it. Long story short, the new kindle fire hd comes with software version 8.5.1. I can not find any real way to root, or instal TWRP on it. I have herd people sugest rooting it the same way, which will make it unusable. They say this will work as long as you install a different rom. So basicaly, is there a better way to root the kindle? And even more so, id like some info on how to instal TWRP and a rom on version 8.5.1.
Thanks for anyone willng to help.
hunter.geek said:
I broke my flashed kindle Fire HD 8.9 by dropping it on accident. This had CM.11 on it. Long story short, the new kindle fire hd comes with software version 8.5.1. I can not find any real way to root, or instal TWRP on it. I have herd people sugest rooting it the same way, which will make it unusable. They say this will work as long as you install a different rom. So basicaly, is there a better way to root the kindle? And even more so, id like some info on how to instal TWRP and a rom on version 8.5.1.
Thanks for anyone willng to help.
Click to expand...
Click to collapse
I too would like to know this information. My kid brother gave me his old Fire HD 8.9 because he didn't want it anymore, and it's on 8.5.1. I want to root it and install CyanogenMod because the Fire OS is just sooo limited.
How to Root 8.5.1
dorekk said:
I too would like to know this information. My kid brother gave me his old Fire HD 8.9 because he didn't want it anymore, and it's on 8.5.1. I want to root it and install CyanogenMod because the Fire OS is just sooo limited.
Click to expand...
Click to collapse
From following this guide
http://forum.xda-developers.com/showpost.php?p=53567401&postcount=18
I was able to root and install TWRP, with ONE key tweak. I had to make enough space for all the apps. Seems like Amazon got wise and made a lazy attempt to block the root exploit: fill up the /system drive!!
So I before I could do the last step of code, the part in root shell, I had to
Code:
# rm /system/app/Cal*
which deletes the stock Calendar apps. Since I don't plan to run stock anyway, I figure 'meh'. After clearing up enough space on /system, all was well and I could complete the exploit.
SIDE NOTE: Maybe the above link could be added to the list of "root methods" listed in the OP, tagged with "linux friendly manual method" or similar; from what I can tell anyone getting one of these devices now a days will be running into this and will have to search for a day like I did, i.e. I just got my refurb yesterday and it had 8.5.1 on it.
Thanks!!!
rykerwilliams said:
From following this guide
http://forum.xda-developers.com/showpost.php?p=53567401&postcount=18
I was able to root and install TWRP, with ONE key tweak. I had to make enough space for all the apps. Seems like Amazon got wise and made a lazy attempt to block the root exploit: fill up the /system drive!!
So I before I could do the last step of code, the part in root shell, I had to
Code:
# rm /system/app/Cal*
which deletes the stock Calendar apps. Since I don't plan to run stock anyway, I figure 'meh'. After clearing up enough space on /system, all was well and I could complete the exploit.
SIDE NOTE: Maybe the above link could be added to the list of "root methods" listed in the OP, tagged with "linux friendly manual method" or similar; from what I can tell anyone getting one of these devices now a days will be running into this and will have to
search for a day like I did, i.e. I just got my refurb yesterday and it had 8.5.1 on it.
Click to expand...
Click to collapse
Thanks for the help guys. Believe it or not this worked completely fine. I am so tired of Amazon. Really? Making it so there isn't enough room in system storage? Well, luckily I'm not running their OS anymore. Anyways, thanks for that reply. I probably never would have guessed that in a million years.
Thanks, ---Hunter
stuck on blue kindle fire screen
I looked for the trouble shooting guide referred to in this thread but cannot find it. I used hashcodes method and my kindle is (was) stuck on the blue kindle fire screen. I performed a getver command in a command prompt and was successful in getting to fastboot mode. Now what?!
Here is the DOS record of my attempt to root KFHD 8.9, 8.5.1
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Home>cd desktop
C:\Users\Home\Desktop> cd kindlefire/stuff
C:\Users\Home\Desktop\kindlefire\stuff>adb push stack /data/local/tmp/
800 KB/s (4096 bytes in 0.005s)
C:\Users\Home\Desktop\kindlefire\stuff>adb shell
[email protected]:/ # su
su
/system/bin/sh: su: cannot execute - Permission denied
126|[email protected]:/ # dd if=/data/local/tmp/stack of=/dev/block/platform/omap/oma
p_hsmmc.1/by-name/system bs=6519488 seek=1
f=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1 <
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
[email protected]:/ # mount -o remount,rw ext4 /system
mount -o remount,rw ext4 /system
[email protected]:/ # mv /system/etc/install-recovery.sh /system/etc/install-recovery
.sh.bak
.sh /system/etc/install-recovery.sh.bak <
[email protected]:/ # mount -o remount,ro ext4 /system
mount -o remount,ro ext4 /system
[email protected]:/ # reboot bootloader
reboot bootloader
C:\Users\Home\Desktop\kindlefire\stuff>fastboot -i 0x1949 flash bootloader kfhd8
-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (243 KB)...
OKAY [ 0.021s]
writing 'bootloader'...
OKAY [ 0.046s]
finished. total time: 0.069s
C:\Users\Home\Desktop\kindlefire\stuff>fastboot -i 0x1949 flash boot kfhd8-freed
om-boot-8.4.3.img
target reported max download size of 1006632960 bytes
sending 'boot' (8173 KB)...
OKAY [ 0.447s]
writing 'boot'...
OKAY [ 0.773s]
finished. total time: 1.225s
C:\Users\Home\Desktop\kindlefire\stuff>49 flash boot kfhd8-freedom-boot-8.4.3.im
g
'49' is not recognized as an internal or external command,
operable program or batch file.
C:\Users\Home\Desktop\kindlefire\stuff>fastboot -i 0x1949 flash recovery kfhd8-t
wrp-2.6.0.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8173 KB)...
OKAY [ 0.451s]
writing 'recovery'...
OKAY [ 0.754s]
finished. total time: 1.208s
C:\Users\Home\Desktop\kindlefire\stuff>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.001s
C:\Users\Home\Desktop\kindlefire\stuff>cd..
C:\Users\Home\Desktop\kindlefire>cd\
C:\>fastboot -i 0x1949 getvar product
< waiting for device >
product: Jem-PVT-Prod-04
finished. total time: 0.011s
C:\>fastboot -i 0x1949 getvar product
< waiting for device >
product: Jem-PVT-Prod-04
finished. total time: 0.005s
C:\>
as stated earlier, I am in fastboot mode but don't know if I should restore and start over or just try to install it again. Being a noob, I am completely clueless on the lingo etc in the rooting process.
fakebackup.ab trouble
Hi,
When I try the manual rooting method I can only type in the first 3 lines of code.
When I come to restore "fakebackup.ab" it says it's unable to do it.
That's as far as I can get. Can anyone help? I have a KFHD 8.9 running 8.5.1
Thanks
RE: Trouble with Rooting
I ran into the same error. I replied thanks too early, just because I thought it was going to work. It didn't. I was somewhat successful in rooting It using key master root. It's in a different language, so Google translate could be handy. Now when I say some what rooted, I mean just that. At the end of the "rooting process", it says network failure. It does not install Super SU, or any of the other necessary kindle fire utilities needed for rooting. When I open an app like kindle free (an app that lets you download launchers and wallpapers to your kindle fire, wallpapers do not work). Anyways when opening this app, it asks for root permission (not using super SU , and in a different language). Although the bad thing is it takes a couple minutes for the root she'll to start up meaning that when I rebooted for the launcher to work, it did not because of the delay of the root shell. Next, I downloaded two root checker apps, and they said (both) that I was completely rooted. It also let me into root explorer on ES file exploorer. So, I decided that I was fully rooted, and decided to install TWRP and a Custom ROM like CM 11. Well, I failed, and again ended up bricking my kindle fire. I now have a bricked kindle fire. I would guess this is due to being rooted improperly, as I know there are extra things the root utilities install so you can safely install things like TWRP. So, Key Master root works in a way, but I would not recommend it. If you want to with your own risk (I am not responsible) here's how:
--- Install Key Master Root APK to PC or Mac
--- After which open downloads folder (or where ever you save your downloads) and find the file
--- Now plug your kindle fire in and drag and drop the file to a folder you can remember, like downloads
--- If you didn't already, download ES FIle Exploorer. It's free on the Amazon App store. You can also use any other file exploorer
--- Now navigate to where you saved the file. On ES file Exploorer, click Install, click install again, and it will install to your Kindle Fire. Press "Open" once installed.
Now once your in the app it will be in a different language, so.....:
First, since my kindles bricked I'll be doing this from memory, so if I mess up let me know so I can change it.
--- Click second option, which I believe says root
--- After which it will bring up some Chinese stuff. After that, click the option far to the left, which I believe is red.
--- it will now say network failure. I find if you leave it on that screen for about five minutes, you will have success, as I believe it's still rooting the device when it says that.
---- that's it, you should be rooted, and again I do not recommend although I could have done something wrong when flashing TWRP, so it still may work. Again, I am not responsible for anything that happens.
--Hunter
Fantastic tutorial, everything went smooth and I'm enjoying the latest CM11 nightly
help me please
my kindle fire hd 8.9 is stuck in a bootloop when i go to the cmd i type in fastboot -i 0x1949 getvar product it says waiting for device once i plug it in my kindle just turns on and starts the bootloop once again can anyone help. i have the kindle adb drivers installed.
Quick success...thanks
After much procrastination I plunged ahead with this. After quickly rooting 8.5.1 with Rootmaster I downloaded the necessary files to the Kindle and flashed the bootloader and TWRP, then the latest CM11 nightly.....went VERY quickly....no cables. Now a frequently crashing, limited device is a very useful tablet. Thank you.
Hello to everybody. I tried my luck with my kindle hd version 8.5.1, i rooted with iroot easy and fast and then i started from step nr 3 since i didnt care for the back up. I used fireflash i've placed twrp and freedom-boot where i've should and then i flashed. I turned down my device and when i tried to reopen, it wouldn't enter in recovery mode. Actually it doesnt load at all it is stuck on the kindle fire logo forever. Any possible suggestion?
I thought this thread was about 2nd boot loader not rooting!!
Anyway, I already have twrp 2.7 on my 8.9 KF. Isn't there a simple way to upgrade to 2.8.7?? I don't need to see all the nonsense about installing twrp for the first time. I'm only looking to update.
Cyanogen mod seems to have unrooted my device.
So. I installed cyanogenmod, and after installation, I downloaded a root checker app and it says i have no root access. So, it seems as CM unrooted my device. How do i reclaim my root?
I am trying to downgrade the AFTV and put on CWM......the downgrade file went across but it the downgrade got cancelled....so now i'm trying to run the command "adb push recovery.img /sdcard/" it says cannot stat 'recovery.img' no such file or directory ....I tried to "mkdir /sdcard" but it already exist
SO right now i'm just stuck on what to do
HELP PLEASE!!!!
Hello guys,
I am trying to change some permissions on a certain file on my fire tv non-rooted running kodi isengard. With Adbfire and the adb shell I am running chmod 666 on the specific file but I get the following:
Code:
Unable to chmod /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/addon_data/plugin.program.advanced.launcher/launchers.xml: Operation not permitted
Is there any chance to be able to do that without rooting ? Can't root as I have just bought the amazon fire tv, so new firmware
Thanks
Baminos said:
Hello guys,
I am trying to change some permissions on a certain file on my fire tv non-rooted running kodi isengard. With Adbfire and the adb shell I am running chmod 666 on the specific file but I get the following:
Code:
Unable to chmod /sdcard/Android/data/org.xbmc.kodi/files/.kodi/userdata/addon_data/plugin.program.advanced.launcher/launchers.xml: Operation not permitted
Is there any chance to be able to do that without rooting ? Can't root as I have just bought the amazon fire tv, so new firmware
Thanks
Click to expand...
Click to collapse
chmod isn't permitted on fat32 filesystems.
Thanks for your reply
Hello guys,
I'm brand new here in the forum and would like to root my Fire TV2 ( Version 5.2.7.3 ). I know about rooting and already own a Fire TV2 that I successfully rooted myself a few years ago. I haven't really found much about this latest version. Just a Pre-Rooted 5.2.7.3 ROM ( from rbox ). But this is of no use to me without the SU and TWRP installed. Has anyone successfully rooted a Fire TV2 with this version and can help me ?
Best regards
Maxidoman
Maxidoman said:
Hello guys,
I'm brand new here in the forum and would like to root my Fire TV2 ( Version 5.2.7.3 ). I know about rooting and already own a Fire TV2 that I successfully rooted myself a few years ago. I haven't really found much about this latest version. Just a Pre-Rooted 5.2.7.3 ROM ( from rbox ). But this is of no use to me without the SU and TWRP installed. Has anyone successfully rooted a Fire TV2 with this version and can help me ?
Best regards
Maxidoman
Click to expand...
Click to collapse
Yeah, root is still possible, here is the thread: Link
Hello Sus_i,
Thanks for the link. But I don't want to open the Fire TV Box for root. Isn't there an easier option for version 5.2.7.3, for example with the sideloading tool adblink for Windows? I could use it to install the SuperUser & TWRP Recovery.
Best regards
Maxidoman
Maxidoman said:
Hello Sus_i,
Thanks for the link. But I don't want to open the Fire TV Box for root. Isn't there an easier option for version 5.2.7.3, for example with the sideloading tool adblink for Windows? I could use it to install the SuperUser & TWRP Recovery.
Best regards
Maxidoman
Click to expand...
Click to collapse
No, unfortunately there isn't another (known) way to root/install TWRP at this fw.
Sus_i said:
No, unfortunately there isn't another (known) way to root/install TWRP at this fw.
Click to expand...
Click to collapse
Hello Sus_i,
I've changed my mind. There must always be a small risk with a root attempt. Otherwise the thrill is missing. Where can I find the required files ( python3, PySerial, adb, fastboot ) on the Internet? How do I get Linux to work on my Windows 7/10 Latop ?
Maxidoman said:
Hello Sus_i,
I've changed my mind. There must always be a small risk with a root attempt. Otherwise the thrill is missing. Where can I find the required files ( python3, PySerial, adb, fastboot ) on the Internet? How do I get Linux to work on my Windows 7/10 Latop ?
Click to expand...
Click to collapse
One way is to create a bootable USB drive with Linux. See https://ubuntu.com/tutorials/try-ubuntu-before-you-install#1-getting-started for Ubuntu instructions.
The link in post 2 includes instructions for installing python3 and PySerial, if they are not already installed. Adb and fastboot are in the Android Platform Tools at https://developer.android.com/studio/releases/platform-tools.
Another way would be to run Linux in a VM under Windows.
Maxidoman said:
Hello Sus_i,
I've changed my mind. There must always be a small risk with a root attempt. Otherwise the thrill is missing. Where can I find the required files ( python3, PySerial, adb, fastboot ) on the Internet? How do I get Linux to work on my Windows 7/10 Latop ?
Click to expand...
Click to collapse
That's easy. Grab rufus (from rufus.ie) and an ubuntu iso, then flash ubuntu with rufus to an usb stick.
Boot it as live version (depends on your laptop, press F2, F12 or something like that for the boot menu) and connect to the internet.
Then just do all requirements from the root OP thread.
Most critical part is the shorting! Don't damage the resistor, best is to use some fine flexible copper cable... but never use sharp tools or steel!
If the short doesn't work within 10 seconds, disconnect power and usb, then try again.
Good luck
Hello Guys,
Thanks for the information. I still have a few questions for understanding. I created a bootable usb stick with ubuntu-20.04.1-desktop-amd64 and now i can start ubuntu. I did not select Install rather l just try out and my latop is connected to my network via wifi. Then open a terminal and enter the following commands :
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot
Some downloads started automatically and the files were installed. The next command :
sudo apt remove modemmanager
Then I opened a new terminal in the amonet-sloane-v1.3 folder and entered the command :
sudo ./bootrom-step.sh
The following is now displayed on the screen
Picture
Is everything okay so far ?
I haven't opened the Fire TV box yet. Couldn't you first connect the USB cable for testing (without the short-circuit bridge between DAT0 and GND) to see if the connection works? I would then possibly expect the message :
Bus 001 Device 013: ID 0e8d: 2000 MediaTek Inc. MT65xx Preloader
Best regards
Maxidoman
Maxidoman said:
Hello Guys,
Thanks for the information. I still have a few questions for understanding. I created a bootable usb stick with ubuntu-20.04.1-desktop-amd64 and now i can start ubuntu. I did not select Install rather l just try out and my latop is connected to my network via wifi. Then open a terminal and enter the following commands :
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot
Some downloads started automatically and the files were installed. The next command :
sudo apt remove modemmanager
Then I opened a new terminal in the amonet-sloane-v1.3 folder and entered the command :
sudo ./bootrom-step.sh
The following is now displayed on the screen
Picture
Is everything okay so far ?
I haven't opened the Fire TV box yet. Couldn't you first connect the USB cable for testing (without the short-circuit bridge between DAT0 and GND) to see if the connection works? I would then possibly expect the message :
Bus 001 Device 013: ID 0e8d: 2000 MediaTek Inc. MT65xx Preloader
Best regards
Maxidoman
Click to expand...
Click to collapse
There are a couple of potential issues which may (or may not) cause problems.
1. The amonet log cannot be written due to a read-only file system. Try this command - "sudo chmod -R +w /cdrom/amonet-sloan-v1.3". That may or may not make the file system writable. If not, and if it does cause problems, do "mount | grep amonet" and let me know the output.
2. The adb and fastboot you installed using apt are probably not the latest versions. The latest versions are in the link I gave you above. You may not need the latest versions, though.
You can connect the USB cable without the short-circuit bridge. Execute the command "lsusb" and you should see the firestick. The file manager may also open, or you may be prompted to open the firestick with the file manager.
Sorry to be so vague, but I'd have to duplicate what you are doing to be more exact, and it has been a while since I have done it with my firestick 4k. Also, your Fire TV Box may produce different results than my firestick.
It actually looks like I only have read access. Or did I enter something wrong ?
[email protected]:/cdrom/amonet-sloane-v1.3$ sudo chmod -R +w /cdrom/amonet-sloane-v1.3
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bootrom-step.sh': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/gpt-fix.sh': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/boot.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/force_recovery.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/gpt-sloane.bin': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/lk.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/preloader.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/tz.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/unbrick.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/brom-payload': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/brom-payload/build': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/brom-payload/build/payload.bin': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/common.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/handshake.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/load_payload.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/logger.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/main.py': Read-only file system
Maxidoman said:
It actually looks like I only have read access. Or did I enter something wrong ?
[email protected]:/cdrom/amonet-sloane-v1.3$ sudo chmod -R +w /cdrom/amonet-sloane-v1.3
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bootrom-step.sh': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/gpt-fix.sh': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/boot.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/force_recovery.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/gpt-sloane.bin': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/lk.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/preloader.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/tz.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/bin/unbrick.img': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/brom-payload': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/brom-payload/build': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/brom-payload/build/payload.bin': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/common.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/handshake.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/load_payload.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/logger.py': Read-only file system
chmod: changing permissions of '/cdrom/amonet-sloane-v1.3/modules/main.py': Read-only file system
Click to expand...
Click to collapse
do "mount | grep cdrom" and let me know the output.
also how did you install the amonet zip file, and where can I get it?
If it is actually on a cdrom, you will have to copy it to the local file system. A cdrom is read-only.
Do "cp -r /cdrom/amonet-sloane-v1.3 ~" to copy it to your home directory.
Hi dcarvil,
here is the output : [email protected]:/cdrom/amonet-sloane-v1.3$ mount | grep cdrom
/dev/sdb1 on /cdrom type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
I start Ubunto from the USB stick and select Try Ubunto. The amonet-sloane-v1.3 folder including bootrom-step.sh is also on the USB stick. I have downloaded adb and fastboot (tools_r30.0.4-linux) how do I install adb and fastboot? Unfortunately, I've never worked with Linux ...
My Fire TV is not yet connected to the laptop
Maxidoman said:
Hi dcarvil,
here is the output : [email protected]:/cdrom/amonet-sloane-v1.3$ mount | grep cdrom
/dev/sdb1 on /cdrom type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
I start Ubunto from the USB stick and select Try Ubunto. The amonet-sloane-v1.3 folder including bootrom-step.sh is also on the USB stick. I have downloaded adb and fastboot (tools_r30.0.4-linux) how do I install adb and fastboot? Unfortunately, I've never worked with Linux ...
My Fire TV is not yet connected to the laptop
Click to expand...
Click to collapse
You can try to remount cdrom as writable with this command "sudo mount -o remount,rw /cdrom". If that doesn't work, just copy /cdrom/amonet-sloane-v1.3 to your home directory using the command in post 11, and execute it from there.
I'd try the adb/fastboot you installed with apt first, as you may not need the latest version. If that doesn't work, these commands should install the zip you downloaded.
sudo apt remove adb fastboot
Change to the directory where you downloaded platform-tools_r30.0.4-linux.zip (presumably Downloads). "cd Downloads", if that is where it is. If not, also change it in the "export PATH" commands below.
unzip platform-tools_r30.0.4-linux.zip
export PATH=~/Downloads/platform-tools:$PATH
Execute "adb --version" to test.
echo "PATH=~/Downloads/platform-tools:\$PATH" >> ~/.profile
echo "export PATH >> ~/.profile
dcarvil said:
You can try to remount cdrom as writable with this command "sudo mount -o remount,rw /cdrom". If that doesn't work, just copy /cdrom/amonet-sloane-v1.3 to your home directory using the command in post 11, and execute it from there.
I'd try the adb/fastboot you installed with apt first, as you may not need the latest version. If that doesn't work, these commands should install the zip you downloaded.
sudo apt remove adb fastboot
Change to the directory where you downloaded platform-tools_r30.0.4-linux.zip (presumably Downloads). "cd Downloads", if that is where it is. If not, also change it in the "export PATH" commands below.
unzip platform-tools_r30.0.4-linux.zip
export PATH=~/Downloads/platform-tools:$PATH
Execute "adb --version" to test.
echo "PATH=~/Downloads/platform-tools:\$PATH" >> ~/.profile
echo "export PATH >> ~/.profile
Click to expand...
Click to collapse
Sorry to intrude here and I dunno if I misread .
Has he even carried out the short process???
before we get into the error and software issues?
Bertonumber1 said:
Sorry to intrude here and I dunno if I misread .
Has he even carried out the short process???
before we get into the error and software issues?
Click to expand...
Click to collapse
You are welcome to intrude. I don't have this fire tv model, and don't know what the short process is. I'm just trying to help with the Linux issues, which is the extent of my knowledge. Please feel free to jump in with additional instructions.
dcarvil said:
You are welcome to intrude. I don't have this fire tv model, and don't know what the short process is. I'm just trying to help with the Linux issues, which is the extent of my knowledge. Please feel free to jump in with additional instructions.
Click to expand...
Click to collapse
hi dcarvil, I was just scanning through there mate and seen that he is talking in a hypothetical manner without the short attached.
I was thinking the read only maybe because he hasnt carried out the short. I'm not sure though but I never actually checked if my box was ro or rw, I just went straight ahead with the short and everything was kooshty :good: anyway.
Suppose we won't know until he replies,
I got a little further but now my FireTV no longer works. First I took it from a different notebook and didn't get an error message ( when i execute sudo ./bootrom-step.sh ) . Then FireTv disassembled and soldered a thin cable to Data0. FireTV started again. Everything was fine. Then follow the instructions step by step. I get this output:
[email protected]:/media/ubuntu/Windows/amonet-sloane-v1.3$ sudo ./bootrom-step.sh
[2020-09-05 11:51:29.645048] Waiting for bootrom
[2020-09-05 11:51:43.461377] Found port = /dev/ttyACM0
[2020-09-05 11:51:43.462252] Handshake
[2020-09-05 11:51:43.462759] Disable watchdog
* * * Remove the short and press Enter * * *
[2020-09-05 11:51:44.967514] Init crypto engine
[2020-09-05 11:51:44.991475] Disable caches
[2020-09-05 11:51:44.992334] Disable bootrom range checks
[2020-09-05 11:51:45.010616] Load payload from ../brom-payload/build/payload.bin = 0x48B0 bytes
[2020-09-05 11:51:45.014370] Send payload
[2020-09-05 11:51:45.637327] Let's rock
[2020-09-05 11:51:45.638437] Wait for the payload to come online...
[2020-09-05 11:51:45.642160] all good
[2020-09-05 11:51:45.642494] Check GPT
[2020-09-05 11:51:46.754204] gpt_parsed = {'PRO_INFO': (1024, 254), 'NVRAM': (2048, 10240), 'TEE1': (12288, 10240), 'TEE2': (22528, 10240), 'lk': (32768, 2048), 'boot': (34816, 51200), 'recovery': (86016, 51200), 'KB': (137216, 2048), 'DKB': (139264, 2048), 'MISC': (141312, 1024), 'LOGO': (142336, 16384), 'EXPDB': (158720, 23296), 'system': (182016, 2477600), 'cache': (2659616, 512000), 'userdata': (3171616, 12098239), '': (0, 1)}
[2020-09-05 11:51:46.755407] Check boot0
[2020-09-05 11:51:47.013076] Check rpmb
[2020-09-05 11:51:47.222409] RPMB: b'AMZN\x01\x00\x00\x00\x04\x00\x05\x01\x02\x00Xc\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
[2020-09-05 11:51:47.223998] Clear preloader header
[8 / 8]
[2020-09-05 11:51:47.712429] Flashing TEE..
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 500, in read
raise SerialException(
serial.serialutil.SerialException: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "main.py", line 164, in <module>
main()
File "main.py", line 126, in main
flash_binary(dev, "../bin/tz.img", gpt["TEE1"][0], gpt["TEE1"][1] * 0x200)
File "main.py", line 56, in flash_binary
dev.emmc_write(start_block + x, data[x * 0x200x + 1) * 0x200])
File "/media/ubuntu/Windows/amonet-sloane-v1.3/modules/common.py", line 200, in emmc_write
code = self.dev.read(4)
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 509, in read
raise SerialException('read failed: {}'.format(e))
serial.serialutil.SerialException: read failed: device reports readiness to read but returned no data (device disconnected or multiple access on port?)
The LED no longer flashes after the start, no picture .... Can I still do something or do I now have a fullbrick? The query with the bridge still works and if I remove it, this is also recognized.
Maxidoman said:
The LED no longer flashes after the start, no picture ....
Click to expand...
Click to collapse
You see, the pl header gets wiped, just behind the RPMB thing. That is a feature: in case the script errors out, you're able to start it again 'without shorting'...
Maxidoman said:
Can I still do something or do I now have a fullbrick?
Click to expand...
Click to collapse
Idk, there are some faulty eMMC chips out there, nobody knows which box is affected.
Just run the script again, without shorting this time...
My FireTv is running again :laugh:. Thank you very much to all of you for the numerous tips. But I still have two questions.
1. My FireTV does not always start correctly. Either it starts completely normally as if no TWRP was installed. Or the 5 seconds overlay with the blue bar for the normal start / TWRP selection appears and starts the box after that it gets stuck (black picture on TV)
2. Is it possible to flash older firmware directly with TWRP with this version (5.2.7.3)?
best regards
Maxidoman
Maxidoman said:
My FireTv is running again :laugh:. Thank you very much to all of you for the numerous tips. But I still have two questions.
1. My FireTV does not always start correctly. Either it starts completely normally as if no TWRP was installed. Or the 5 seconds overlay with the blue bar for the normal start / TWRP selection appears and starts the box after that it gets stuck (black picture on TV)
2. Is it possible to flash older firmware directly with TWRP with this version (5.2.7.3)?
best regards
Maxidoman
Click to expand...
Click to collapse
Hi @Maxidoman I've got the exact same error as your post above with the "multiple access on ports error,, demonstrates a willingness to read..... " during rpmb downgrade in amonet script
Could you be so kind and elaborate how you got past this error.
Another member said to update fireiso software through the pacman command,, this is well over my head as im using Ubuntu 18.04 Lts (dual boot) and am updating this to latest Ubuntu distro just now and will update fb that way..
Cheers in advance