Develop Bugs

[Q] Rooting G2 - Failed to copy : Read-only file system

Hey,
I'm following the tutorial over at G2 Hacks:
g2hacks.co m/g2-hacks/how-to-root-g2-phone
(omit the space between 'co' and 'm/')
I came across a problem at the beginning of the cmd portion.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
EDIT: Go to 3rd post.

kpaekn said:
Hey,
I'm following the tutorial over at G2 Hacks:
g2hacks.co m/g2-hacks/how-to-root-g2-phone
(omit the space between 'co' and 'm/')
I came across a problem at the beginning of the cmd portion.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
Click to expand...
Click to collapse
If you're wanting to root, go straight to the source; the guide in the Wiki here is based on the work the devs who actually found the means to root the device.
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Sent from my T-Mobile G2 using XDA App

I was following the tutorial from the Wiki Guide:
ht tp://forum.xda-developers.co m/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
(omit the space between 'ht' and 'tp' , 'co' and 'm/')
I came across a problem under the TEMP ROOT section.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?

kpaekn said:
I was following the tutorial from the Wiki Guide:
ht tp://forum.xda-developers.co m/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
(omit the space between 'ht' and 'tp' , 'co' and 'm/')
I came across a problem under the TEMP ROOT section.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
Click to expand...
Click to collapse
Is USB debugging turned on and is the SDcard not mounted?
Sent from my T-Mobile G2 using XDA App

Sounds like the SD card is mounted on your PC and not the phone ? It needs to be mounted on the phone or this won't work.
Sent from my HTC Desire Z

All that command does is copy that file from your computer to the sdcard. You could accomplish the same thing by dragging and dropping that file to the sdcard.
The 'push' command just means "copy from location A to location B"
Sent from my HTC Vision using XDA App

You could always just mount the SDcard... but anyway, to solve this type in "adb remount" and enter the command before pushing the file
Sent from my HTC Vision using XDA App

USB debugging is on and SD is not mounted to my computer.
I tried directly copying the files onto the sdcard, but when I need to push rage, busybox, etc. I cannot access the data folder graphically from the computer.
So I'll still need to use cmd.
I tried the remount, but this is what I get:
Code:
C:\AndroidSDK\tools>adb remount
remount failed: Operation not permitted

kpaekn said:
USB debugging is on and SD is not mounted to my computer.
I tried directly copying the files onto the sdcard, but when I need to push rage, busybox, etc. I cannot access the data folder graphically from the computer.
So I'll still need to use cmd.
I tried the remount, but this is what I get:
Code:
C:\AndroidSDK\tools>adb remount
remount failed: Operation not permitted
Click to expand...
Click to collapse
The adb remount error is expected (the command requires your ro.secure prop to be set to 0, which you can't do until you have rooted).
So you were able to copy files to the SD card? Just to verify again, you should try mounting the SD card to you computer (so it shows up as a device on your computer's file explorer), copy over a file, unmount the card from your computer (and remember to also hit the button on phone to do so), and then try the ADB push commands again.

Ok, with the phone on plug it into your computer and mount USB storage. Drag and drop 'su' and superuser.apk into the sdcard then unmount USB storage. Make sure USB debugging is on at this point (you'll see it in the notification task bar). Do these commands:
Code:
adb push rage /data/local/tmp/rage
adb push busybox /data/local/tmp/busybox
adb push root /data/local/tmp/root
adb shell chmod 0755 /data/local/tmp/*
Then in the terminal app type:
Code:
/data/local/tmp/rage
You'll see some message pop up saying something about 'forked #### childs' and that's temp root. Then follow the instructions on running gfree to gain full root. Btw, you can just copy and paste all those commands if you think you'll make a mistake.
You may also be able to run the '/data/local/tmp/rage' command with the 'adb shell' command, never tried it myself though.

kpaekn said:
I was following the tutorial from the Wiki Guide:
ht tp://forum.xda-developers.co m/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
(omit the space between 'ht' and 'tp' , 'co' and 'm/')
I came across a problem under the TEMP ROOT section.
This is what I type and the error I get.
Code:
C:\AndroidSDK\tools>adb push su \sdcard\su
failed to copy 'su' to '\sdcard\su': Read-only file system
How do you solve this problem?
Click to expand...
Click to collapse
Oh come on !!!
the path separator in linux (and the phone is a linux computer) is / and not \ !!!
So the command is:
Code:
C:\AndroidSDK\tools>adb push su /sdcard/su
Just to tell you something about the unix shell:
The \ char is a so called escape character that you use to tell the shell that it should not ignore the next character even if it is a white space (i.e. space)
You would use it if you have to specify a path that contains spaces:
i.e.:
Code:
mkdir dir\ with\ 3\ spaces
will create a directory with the name "dir with 3 spaces". This would not work without the \ characters.
have fun - Guhl

Haha... it's funny how simple the answer was.
Thanks for your guys' help.

V10J and NO Root: I am FRUSTRATED!

Hi everyone! I got the Nitro yesterday and I have tried EVERY possible method under the sun to get root onto my 2.3.5 V10J stock firmware. I am generally good at stuff, but the unbricking tutorial really confuses me. Is there any other way to just get CWM onto the phone and then install a pre-rooted ROM? Or an easier way to root? I tried superoneclick a 100 times, and it just behaves read only. does not allow the software to access root. This is the error I get with all rooting scripts!
---------------------------------------------------------------
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using latest zergRush exploit (21 Nov)
(2) install Busybox (1.18.4)
(3) install SU files (binary: 3.0.3 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
adb server is out of date. killing...
* daemon started successfully *
--- creating temporary directory
mkdir failed for tmp, File exists
--- cleaning
rm failed for *, No such file or directory
--- pushing zergRush
failed to copy 'files\zergRush' to '/data/local/tmp/./zergRush': Permission deni
ed
--- correcting permissions
Unable to chmod /data/local/tmp/zergRush: No such file or directory
--- executing zergRush
./data/local/tmp/zergRush: not found
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
--- pushing busybox
failed to copy 'files\busybox' to '/data/local/tmp/./busybox': Permission denied
--- correcting permissions
Unable to chmod /data/local/tmp/busybox: No such file or directory
--- remounting /system
/data/local/tmp/busybox: not found
--- checking free space on /system
failed to copy 'files\makespace' to '/data/local/tmp/./makespace': Permission de
nied
Unable to chmod /data/local/tmp/makespace: No such file or directory
./data/local/tmp/makespace: not found
--- copying busybox to /system/xbin/
/data/local/tmp/busybox: cannot open for read: No such file or directory
--- correcting ownership
Unable to chmod /system/xbin/busybox: Read-only file system
--- correcting permissions
Unable to chmod /system/xbin/busybox: Read-only file system
--- installing busybox
--install: applet not found
rm failed for /data/local/tmp/busybox, No such file or directory
--- pushing SU binary
failed to copy 'files\su' to '/system/bin/su': Read-only file system
--- correcting ownership
Unable to chmod /system/bin/su: No such file or directory
--- correcting permissions
Unable to chmod /system/bin/su: No such file or directory
--- correcting symlinks
rm failed for /system/xbin/su, Read-only file system
link failed Read-only file system
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only
file system
--- cleaning
rm failed for *, No such file or directory
--- rebooting

Apparently there is atm no way to get cwm or cwm recovery on your phone w/out going through oh no!'s rom which as a prerequisite you must follow the unbricking method.
If you want go to my profile and check out my recent posts in the nitro general subforum and youll see my little journey....which others were annoyed with ...lmao.
I am currently rooted, running stock ics and love it. I have no issues phone runs near perfect.
I did not "unbrick" my phone and just flashed an older rom (v18) and rooted.
Sparky's root method is the only method that will root this phone via ics.
I made a thread explaining in detail some steps that were not mentioned.
Dont bother with doomlord, oneclick.
Since the tapatalk search function sucks balls use the xda search function from the actual browser.
Hope that helps. Maybe someone else will chime in.
Dont fear the unbrick.
Take your time
Read slow and also read through other peoples posts and what they did wrong, how they remedied it blah blah...
Dont take any short cuts unless for sure, you know exactly what you are doing.
Make sure you have everything ready and have read through prior to doing it.
Nothing to fear flashing is pretty straight forward.
Just take your time.
:beer:
Sent from my LG-P930 using Tapatalk 2

I went from Stock ATT 2.5.6 V10J to ATT STOCK V10F .Using [GUIDE] Unbrick, Root, And Install CWM by mattman86 . Its long but doable its not even that long really .O tip uninstall all the drivers you might have installed and use the one that come with the unbricking pack ,its the key to the whole thing. Im in CM10 Nightly now .Good luck and dont get frustrated its rootable its just not a one click root.

Just keep trying to run the root. I used super one click and it took me at least 20-30 attempts to successfully root. If it asks you if your version is 2 or higher or fails to push any files to the phone, the root will not take. Just reboot the phone and keep trying.

Try using viperMOD PrimeTime v4.6, that's a lot easier and faster, despite what everyone else says, you can root 10j.
Good Luck

Bootlocked Xperia S, rooted, CWM 'installed succesfully' but can't access it?

I am trying to install CWM on my bootloader locked Xperia S.
It's all went smoothly; downgraded to gingerbread, run the rooting process, currently on a confirmed rooted ICS. Ran RecoverX and for all intentions it installs correctly with no errors. I restart my phone and tap the Sony logo numerous times... and I've tried a countless amount of times now but it just continues on loading stock ICS. It's really starting to get on my nerves now. Does anyone have any idea why it's happening? or is there any adb commands to check if CWM is installed?
RecoverX says accept any SuperUser prompts on the screen, but none appear.
RecoverX log:
Starting adb...
Wait for the device...
Check if the device is correctly rooted...
Check if busybox is installed...
Push files...
Unzip files...
Chmod files to 755...
Run installation script...
Clear temp folder...
Installation complete
Click to expand...
Click to collapse
I've also tried the older adb method via the install.bat but that says this:
Step1 : Waiting for Device.
=============================================
OK
=============================================
Step2 : Sending some files.
=============================================
mkdir failed for /data/local/tmp/cwm, Not a directory
failed to copy 'chargemon' to '/data/local/tmp/cwm': Not a directory
failed to copy 'charger' to '/data/local/tmp/cwm': Not a directory
failed to copy 'recovery.tar' to '/data/local/tmp/cwm': Not a directory
failed to copy 'sh' to '/data/local/tmp/cwm': Not a directory
failed to copy 'step3.sh' to '/data/local/tmp/cwm': Not a directory
=============================================
Step3 : Setting up files system partition.
=============================================
Unable to chmod /data/local/tmp/cwm/sh: Not a directory
Unable to chmod /data/local/tmp/cwm/step3.sh: Not a directory
sh: /data/local/tmp/cwm/step3.sh: not found
rm failed for /data/local/tmp/cwm, Not a directory
Finished!
Click to expand...
Click to collapse
Even though I clearly have access to my phone via adb. Because it's been rooted... Grr!

Nobody have any idea? Spent around 12 hours trying to sort it out yesterday so I'm completely out of things to try

For search purposes I ended up fixing it by updating the flashtool drivers for the phone (ticked every Xperia S checkbox). Well, it was either that or perhaps updating BusyBox, which is highly unlikely as I tried pretty much every version of it yesterday.

[Root] How to root z1s and get it to stick on reboot.

Z1s Root+Reovery+Deodex Android 4.3 Updated 6/18/14​
This was put together by @ayuready1989 and @Tactic13
This Not A Rom "Do NOT WIPE ANYTHING JUST FLASH AS IS"
This is a Patch to keep root on reboot as well as deodex your current rom.[
NO LONGER USED
Please use Root 4.4.4 on z1s
Once you have recovery you can flash this instead of using the script it does not require you to make the script.
First of all we would like to thank @jcase for getting the initial root, @[NUT] for the recovery @xsacha for the ta backup and @RyokoN for some of the tools, if we forgot someone just send us a message.
Okay now for the fun part.​
Make sure that you have usb debugging enabled.
Root with jcase method.
Install SuperSU from market reboot.
Run adb shell su -c "/system/xbin/kill_ric.sh"
Then adb shell su -c "mount -o remount,rw /system"
Install Recovery But use the one for the z1 Locked boatloader.
Finaly Flash Deodex + Root Devhost Minor
Optional
Backup Ta image. Ta Backup
We will keep working on this as well as start working on a rom just wanted to get this out to you guys.
You assume all the stand disclaimers when you flash this that not is to say that we wont help you.

Mine Just in case i need it.

Tactic13 said:
Mine Just in case i need it.
Click to expand...
Click to collapse
+1

This is what i get when trying to install recovery. Supersu working fine. I just used it for TB. Should I try SuperUser instead?
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices =
= =
==============================================
[ 1. Installation on ROM rooted with SuperSU ]
[ 2. Installation on ROM rooted with SuperUser ]
[ 3. Installation on unrooted ROM ]
[ 4. Exit ]
Please choose install action. [1,2,3,4]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found
=============================================
Step2 : Sending the recovery files.
=============================================
9 KB/s (29 bytes in 0.003s)
3847 KB/s (15759 bytes in 0.004s)
244 KB/s (501 bytes in 0.002s)
2880 KB/s (11798 bytes in 0.004s)
5030 KB/s (56662 bytes in 0.011s)
1504 KB/s (3082 bytes in 0.002s)
187 KB/s (385 bytes in 0.002s)
5489 KB/s (657704 bytes in 0.117s)
5318 KB/s (2875482 bytes in 0.528s)
5240 KB/s (2581087 bytes in 0.481s)
5347 KB/s (1845510 bytes in 0.337s)
384 KB/s (8658 bytes in 0.022s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Apr 30 05:38 /data/local/tmp/recovery/busybox
Press any key to continue . . .
##########################################################
#
# Installing XZDR version 2.7.123 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to allow installation.
mount: permission denied (are you root?)
blockdev: applet not found
mount: permission denied (are you root?)
Copy recovery files to system.
cp: can't create '/system/bin/recovery.twrp.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.cwm.cpio.lzma': Read-only file system
cp: can't create '/system/bin/recovery.philz.cpio.lzma': Read-only file system
chmod: /system/bin/recovery.twrp.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.cwm.cpio.lzma: No such file or directory
chmod: /system/bin/recovery.philz.cpio.lzma: No such file or directory
Rename stock mr
mv: can't rename '/system/bin/mr': Read-only file system
Copy mr wrapper script to system.
cp: can't create '/system/bin/mr': File exists
chmod: /system/bin/mr: Read-only file system
Rename stock chargemon
mv: can't rename '/system/bin/chargemon': Read-only file system
Copy chargemon script to system.
cp: can't create '/system/bin/chargemon': File exists
chmod: /system/bin/chargemon: Read-only file system
Copy dualrecovery.sh to system.
cp: can't create '/system/bin/dualrecovery.sh': Read-only file system
chmod: /system/bin/dualrecovery.sh: No such file or directory
Copy rickiller.sh to system.
cp: can't create '/system/bin/rickiller.sh': Read-only file system
chmod: /system/bin/rickiller.sh: No such file or directory
Installing NDRUtils to system.
cp: can't create '/system/app/NDRUtils.apk': Read-only file system
chmod: /system/app/NDRUtils.apk: No such file or directory
Copy disableric to system.
cp: can't create '/system/xbin/disableric': Read-only file system
chmod: /system/xbin/disableric: No such file or directory
Creating /system/.XZDualRecovery to store a backup copy of busybox.
mkdir failed for /system/.XZDualRecovery, Read-only file system
Copy busybox to system.
cp: can't create '/system/xbin/busybox': File exists
cp: can't create '/system/.XZDualRecovery/': Is a directory
chmod: /system/xbin/busybox: Read-only file system
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after itself if you see the install.bat/install.sh exit.
=============================================
=============================================
Installation finished. Enjoy the recoveries
=============================================
Press any key to continue . . .

Re run the root as well as the second set of commands and on your phone it should ask you to grant root access to adb. But i installed SuperSu and used option 1.

same here, supersu and option 1,but make sure /sbin/xbin/kill_ric.sh is ran before u install recovery a couple times(2-3) just to make sure.
this is the specific one i used, for winblows V4
http://forum.xda-developers.com/showthread.php?t=2426739

So last night jcase remotely tested the exploit and rooted my Z1s. I installed the recovery this morning as instructed here and then flashed the deodex and root zip. Now my phone cannot achieve root via the adb commands or by itself. Furthermore the su binary that supersu had installed is gone and supersu cannot install it again. Any ideas what happened?
EDIT: Hmm, i installed the updated root method from the OP and that appears to have fixed it. Now to see if root sticks.

themacman1000 said:
So last night jcase remotely tested the exploit and rooted my Z1s. I installed the recovery this morning as instructed here and then flashed the deodex and root zip. Now my phone cannot achieve root via the adb commands or by itself. Furthermore the su binary that supersu had installed is gone and supersu cannot install it again. Any ideas what happened?
EDIT: Hmm, i installed the updated root method from the OP and that appears to have fixed it. Now to see if root sticks.
Click to expand...
Click to collapse
cool. if asked to fix root after cwm flash it seems safe to always chose to fix it

ayuready1989 said:
strange, the zip doesnt touch /system/xbin/su .. try the su fix that cwm asks for when trying to reboot after flashing a zip . ive selected yes and no, still the same result. still had root.. but flash via cwm and apply the fix root fix it asks, dont disable flash recovery though
Click to expand...
Click to collapse
Oh. When I first installed the deodex via philztouch it asked if i wanted to disable flashing of stock recovery. I said yes... That must have been my problem. However, everything works now, even rebooting holds root and system r/w. Also, can you link me to how you installed xposed? Edit: Nevermind, found out how myself

themacman1000 said:
Oh. When I first installed the deodex via philztouch it asked if i wanted to disable flashing of stock recovery. I said yes... That must have been my problem. However, everything works now, even rebooting holds root and system r/w. Also, can you link me to how you installed xposed?
Click to expand...
Click to collapse
alrighty, nice to know it works, thanks for actually giving feedback @themacman1000 now time for the modules and tweaks

themacman1000 said:
Oh. When I first installed the deodex via philztouch it asked if i wanted to disable flashing of stock recovery. I said yes... That must have been my problem. However, everything works now, even rebooting holds root and system r/w. Also, can you link me to how you installed xposed? Edit: Nevermind, found out how myself
Click to expand...
Click to collapse
I installed this apk.
http://dl-count.xposed.info/modules/de.robv.android.xposed.installer_v32_de4f0d.apk
Sent from my iPad using Tapatalk

I'm curious if Z1 roms would work for the Z1s... Considering they're basically the same phone... I did a full backup on mine, now considering trying that out...

I have don't its a pain in the but to get back you will lose everything.
We don't have a 4.4.2 kernel if we did we might be able to.

It's good to see T-Mobile roms,when you're overseas you can use WiFi Calling to call back to the US free.:thumbup::thumbup:
Sent from my HTC One_M8 using Tapatalk 2

Well you have the start right here it deodex the rom and root sticks

Tactic13 said:
I have don't its a pain in the but to get back you will lose everything.
We don't have a 4.4.2 kernel if we did we might be able to.
Click to expand...
Click to collapse
I was actually thinking 4.3 roms... I figured 4.4 wouldn't work, but 4.3 maybe?

adb shell chmod 755 /data/local/tmp/pwn
/system/bin/sh: chmod755: not found
Please help

jahjah440 said:
adb shell chmod 755 /data/local/tmp/pwn
/system/bin/sh: chmod755: not found
Please help
Click to expand...
Click to collapse
There's supposed to be a space between chmod and 755.

Elysian893 said:
There's supposed to be a space between chmod and 755.
Click to expand...
Click to collapse
Thank you I actually got it working before I had forgotten to give elevated permission to write to /data
I have achieved root!

what are the steps to installing the rom for this phone? do we have to delete anything in recovery?
---------- Post added at 06:03 PM ---------- Previous post was at 05:51 PM ----------
how do i backup the TA, complete sony noob here
---------- Post added at 06:05 PM ---------- Previous post was at 06:03 PM ----------
LaosPerson said:
what are the steps to installing the rom for this phone? do we have to delete anything in recovery?
---------- Post added at 06:03 PM ---------- Previous post was at 05:51 PM ----------
how do i backup the TA, complete sony noob here
Click to expand...
Click to collapse
nevermind, i just had to read the z2 link thing

Question about rooting Fire TV2 with version 5.2.7.3

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