Develop Bugs

[Guide] How to get Karmic Koala on your HTC Vision

So, for all of you guys down here that are Debian junkies, then you're gonna love this. I managed to get Ubuntu Karmic Koala on my G2 after a bit of messing around with adb. This is my first tutorial on xda-developers, so please tell me how I'm doing. Remember to hit the Thanks button at the bottom if you're satisfied
Code:
#Your warranty has been voided
#I am not the cause of any damage done to your device
#Should you accuse me, I will laugh at you
Reasons why you should follow this tutorial:
- It allows you to make use wide array of applications available in Debian/Ubuntu's repos.
- It doesn't overwrite the current Android operating system.
- It'll allow you to turn your G2, Desire Z, etc. into more than just a sub-par cellphone.
- If you're developing software/applications, this will give you the proper environment for you test them on, if you don't care for Virtualbox or don't have access to a computer at the current moment.
- This tutorial will make the best use of Android and Linux's open-source nature.
Please note that this DOES NOT replace Android nor is it a port of Ubuntu/Debian. Ubuntu/Debian support ARM EABI which is the underlying architecture of Android.
READ EVERYTHING BEFORE DOING ANYTHING. I KNOW IT'S LONG, I WROTE THIS TUTORIAL
For those of you that can't use, can't set it up, or don't care for adb, you can still get Ubuntu to work on your device using a Terminal Emulator app, but you're probably gonna be stuck at the command line. I haven't actually tried setting up the GUI using the Terminal, so I'm not 100% sure. Now, before I start the tutorial, you NEED to be rooted.
NOTE: Whenever you see a $ or a # sign, those are indicators for the next command. Please do not enter them as you're typing in the commands. The same goes for the "[email protected]:/#" sign.
Before we begin we will need the following:
On your phone, have the following installed and/or readily available
-androidVNC application
-Terminal Emulator app (use this to boot into Ubuntu shell)
-Busybox (preferably, the latest one. If you rooted your phone using the method on the xda wiki OR your custom ROM has it pre-installed, then continue)
- At least 2GB space free on your microSD card
- Loopdevice support for your ROM. I think Cyanogen and another kernel should do the trick.
On your computer have the following installed and/or on the desktop:
-Ubuntu Karmic Koala image. If you don't have it, download it from this link ->http://bit.ly/moghJ3
-adb installed and fully functioning on your computer
EDIT 4 June, 2011: For those of you having troubles getting the shell to boot up, I found an alternative bootubuntu file. Extract it and replace the one that comes with the image with this one http://bit.ly/j7zORF
Let's begin, shall we?
Step 1: Connect your phone to your computer. Make sure you have "USB Debugging" checked off in "Settings -> Applications -> Development", then mount your sd card.
Step 2: Transfer the extracted "ubuntu" folder to the root of your sd card [NOT IN ANY FOLDERS, JUST the sd card itself, for those of you who don't know]. It might take a few minutes, so you might wanna make yourself a little snack for the wait.
Step 3: When the file transfer is done, disable the USB connection, so we can make use of adb. This is where USB Debugging is CRUCIAL. Open up a command window/terminal, go to where adb is located and enter the following commands:
Code:
$ adb shell
$ cd /sdcard/ubuntu
# su
# sh ./ubuntu.sh
# bootubuntu
At this point, you've set up the Ubuntu shell, as indicated by the "[email protected]:/#" sign.
However, our shell is still incomplete. We're gonna need a GUI for actual usage. If you're fine with using the command line then stop here. If you want to give yourself a PC-like experience, then please continue. You might wanna connect to WiFi if you're in an area where your mobile data is inconsistent or restricted to an EDGE connection.
Step 4: With the command prompt/terminal window that contains your adb/ubuntu shell, let's continue entering some commands to get our GUI set up.
Code:
[email protected]:/# apt-get update
[email protected]:/# apt-get install tightvncserver
[email protected]:/# apt-get install lxde
[email protected]:/# export USER=root
[email protected]:/# vncserver -geometry 1024x800
After entering the last command, you'll be prompted to enter a password. It'll ask you to set up a second one, just press "n" then continue.
For the second and third commands, press "y" when prompted to then hit ENTER, so you can install the packages. The reason why we set the VNC server's resolution is because even though the G2/Dz's resolution is 800x480, a higher resolution will provide a better viewing experience. If you want it set up to your phone's resolution, then swap it with "800x480" to scale the server's resolution to your phone's screen size.
Step 5: Enter the following commands. After entering the first command, you'll notice there's no user indicator at the left side. DON'T PANIC. Just continue entering the following commands:
Code:
[email protected]:# cat > /root/.vnc/xstartup
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
icewm &
lxsession
Then, press Ctrl+D twice and press enter. You'll be back at "[email protected]:/#" (Conversely, if you're on Mac OS or Linux, just press Ctrl+D once)
Step 6: Go to your phone, and open up the androidVNC app. We're gonna need this to view our desktop. set the nickname to "root" and enter the password you set earlier. Set the port to "5901" and press connect.
Step 7a: And bam! You've got your own cool GNOME desktop! (Though in my experience, it switches over to lxde after a few uses.) Now, we need to get the VNC app to open up every time we boot into our shell. We need to enter a few more commands (yeah I know, it's getting a bit tedious at this point.)
Code:
[email protected]:/# cat > front
export USER=root
cd /
rm -r -f tmp
mkdir tmp
cd /
vncserver -geometry 1024×800
Again, you can replace "1024x800" with any screen resolution you desire.
Step 7b: Enter just a few more commands [trust me, we're almost done ]
Code:
[email protected]:/# cat front /root/.bashrc > temp
[email protected]:/# cp temp /root/.bashrc
Step 8: To check that everything is working, enter the following commands in your command prompt/terminal window that contains our adb/ubuntu shell that I hope you kept open all this time.
Code:
[email protected]:/# exit
# bootubuntu
And you're done! Give yourself a round of applause and a pat on the back, because now you have Ubuntu Linux running alongside Android. Yay!!!!!!
To boot into your shell AFTER you're done, use the Terminal Emulator app to access your shell:
Code:
$ su
# bootubuntu
That's it, you're finished.
Now, I don't know why this happens, but after rebooting your phone, it'll take a few extra seconds for your devices to start up. I think it's because of all the files that are in the phone's internal memory. I'm not sure. Also, the VNC server might not open up after you're done with the tutorial. It's only a minor setback, you can still manually open it yourself which is in itself relatively quick.
When you're done with the tutorial, be sure to type in "exit" in the terminal and press enter for a clean kill of Ubuntu. Otherwise, you're gonna have to redo the entire procedure.
If you have any questions, please email me at [email protected]
FAQ
- I don't have adb, can I still follow this tutorial?
A: Yes you can. However, you're probably going to be stuck at Step 3 with the command line. You can still use the shell, but you won't have a GUI.
- Why does my phone show a black screen after rebooting?
A: It's probably because of all the modding that's a result of the commands we entered.
Don't worry, Your phone will boot up normally. However, if this goes on longer than usual, you might have to install a different ROM. I've tested it on CM7 (Stable and Nightly), Stock G2 ROM, Virtuous 1.0.2, Virtuous G-Lite 1.0.2, and their respective ROM bases with no problems.
- I get an error that won't let me boot into the Ubuntu shell. Help me!!!!!
A: Yeah, you probably either downloaded an incomplete image OR you entered an important command wrong. I suggest deleting the ubuntu image from your sdcard and then copy the image you extracted onto your sdcard. Then what you have to do is redo the entire tutorial.

Interesting...
Sent from my T-Mobile G2 using XDA Premium App

Spastic909 said:
Interesting...
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
What's interesting about this?

Edit: can't wait to try this!

Ouch. . .
It's my first tutorial. . .
I just want to know what he found interesting about this tutorial. No need to get so defensive over a comment some other guy made.
Sent from my T-Mobile G2 using XDA Premium App

Didn't mean any offense dude especially if you weren't trying to be rude. You know how the internet doesn't portray emotion very well in text. Just sounded snappy. Back on topic. Can't wait to try this!
Sent from my HTC Vision using XDA Premium App

I'm not much of a software junky, so what exactly would this do? It looks easy enough to accomplish, since most of it is done through terminal, but I kinda wanna know what this DOES xD
Sent from my HTC Vision using XDA Premium App

xsteven77x said:
Didn't mean any offense dude especially if you weren't trying to be rude. You know how the internet doesn't portray emotion very well in text. Just sounded snappy. Back on topic. Can't wait to try this!
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Edit: Remember to hit that thanks button!

ohshootrawr said:
I'm not much of a software junky, so what exactly would this do? It looks easy enough to accomplish, since most of it is done through terminal, but I kinda wanna know what this DOES xD
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Well, Ubuntu is a distribution of the Debian family of Linux.
Essentially, you have access to the plethora of apps that exist in Ubuntu/Debian's repos, and it's also possible to use this shell as a test monkey for applications that you might be developing.

Any idea if this will work with the new Ubuntu 11.04? Though I do hate the new layout

boost3d23 said:
Any idea if this will work with the new Ubuntu 11.04? Though I do hate the new layout
Click to expand...
Click to collapse
in theory, yes if the image has been compiled properly. also, the new layout technically can get overwritten with lxde or whatever desktop environment you installed.

reserved for future use.

im getting some errors in terminal when trying to set this up, im running mexdroid v3 android 2.3.4
C:\push\tools>adb shell
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# su
su
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: module 'ext2' not found
←[H←[Jmkdir: can't create directory '/data/local/mnt': File exists
←[H←[Jchmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at AndroLinux.com ,G2Hacks.com and NexusOn
eHacks.net
To enter the Ubuntu Linux console just type 'bootubuntu'
# bootubuntu
bootubuntu
mknod: /dev/loop1: File exists
losetup: /dev/block/loop1: No such file or directory
mount: mounting /dev/block/loop1 on /data/local/ubuntu failed: Device or resourc
e busy
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file or dir
ectory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or director
y
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or director
y
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
umount: can't umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't umount /data/local/ubuntu/proc: No such file or directory
umount: can't umount /data/local/ubuntu/sys: No such file or directory
umount: can't umount /data/local/ubuntu: Invalid argument
losetup: /dev/block/loop1: Device or resource busy
# bootubuntu
bootubuntu
mknod: /dev/loop1: File exists
losetup: /dev/block/loop1: No such file or directory
mount: mounting /dev/block/loop1 on /data/local/ubuntu failed: Device or resourc
e busy
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file or dir
ectory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or director
y
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or director
y
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
umount: can't umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't umount /data/local/ubuntu/proc: No such file or directory
umount: can't umount /data/local/ubuntu/sys: No such file or directory
umount: can't umount /data/local/ubuntu: Invalid argument
losetup: /dev/block/loop1: Device or resource busy
#

teh5abiking said:
Well, Ubuntu is a distribution of the Debian family of Linux.
Essentially, you have access to the plethora of apps that exist in Ubuntu/Debian's repos, and it's also possible to use this shell as a test monkey for applications that you might be developing.
Click to expand...
Click to collapse
Seriously? Mmm, okay. I'm gonna try it sometime this week ;D
Sent from my HTC Vision using XDA Premium App

strker45 said:
im getting some errors in terminal when trying to set this up, im running mexdroid v3 android 2.3.4
C:\push\tools>adb shell
# cd /sdcard/ubuntu
cd /sdcard/ubuntu
# su
su
# sh ./ubuntu.sh
sh ./ubuntu.sh
modprobe: module 'ext2' not found
←[H←[Jmkdir: can't create directory '/data/local/mnt': File exists
←[H←[Jchmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at AndroLinux.com ,G2Hacks.com and NexusOn
eHacks.net
To enter the Ubuntu Linux console just type 'bootubuntu'
# bootubuntu
bootubuntu
mknod: /dev/loop1: File exists
losetup: /dev/block/loop1: No such file or directory
mount: mounting /dev/block/loop1 on /data/local/ubuntu failed: Device or resourc
e busy
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file or dir
ectory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or director
y
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or director
y
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
umount: can't umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't umount /data/local/ubuntu/proc: No such file or directory
umount: can't umount /data/local/ubuntu/sys: No such file or directory
umount: can't umount /data/local/ubuntu: Invalid argument
losetup: /dev/block/loop1: Device or resource busy
# bootubuntu
bootubuntu
mknod: /dev/loop1: File exists
losetup: /dev/block/loop1: No such file or directory
mount: mounting /dev/block/loop1 on /data/local/ubuntu failed: Device or resourc
e busy
mount: mounting devpts on /data/local/ubuntu/dev/pts failed: No such file or dir
ectory
mount: mounting proc on /data/local/ubuntu/proc failed: No such file or director
y
mount: mounting sysfs on /data/local/ubuntu/sys failed: No such file or director
y
net.ipv4.ip_forward = 1
Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
bootubuntu: cannot create /data/local/ubuntu/etc/resolv.conf: directory nonexist
ent
Setting localhost on /etc/hosts
bootubuntu: cannot create /data/local/ubuntu/etc/hosts: directory nonexistent
READY TO ROCK AND ROLL BABY!
Brought to you by NexusOneHacks.net and the open source community!
chroot: can't execute '/bin/bash': No such file or directory
Shutting down Ubuntu
umount: can't umount /data/local/ubuntu/dev/pts: No such file or directory
umount: can't umount /data/local/ubuntu/proc: No such file or directory
umount: can't umount /data/local/ubuntu/sys: No such file or directory
umount: can't umount /data/local/ubuntu: Invalid argument
losetup: /dev/block/loop1: Device or resource busy
#
Click to expand...
Click to collapse
I had this issue aswell.
To solve it firts fix your permissions in Rom manager.
Then install busy box.
This should then allow you to install ubuntu. (atleast it did with me)
Hope this is some help to you

teh5abiking said:
What's interesting about this?
Click to expand...
Click to collapse
The post dude.. would you rather I said boring? Settle down
Do u know what interesting means? It means I am interested in this..didn't think you could mistake that but guess I was wrong
Sent from my T-Mobile G2 using XDA Premium App

Spastic909 said:
The post dude.. would you rather I said boring? Settle down
Do u know what interesting means? It means I am interested in this..didn't think you could mistake that but guess I was wrong
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
hey man, i just wanna know what you found interesting about the tutorial.
i wasn't trying to be3 a smart aleck.

I really don't know **** about linux except for the few times I've had to run it on a virtual machine for rooting certain phones or to check out a few programs. With linux installed on my phone,
does that mean that I would be able to run any linux based program? For example aircrack or something like it?
Edit: I basically want to know what the purpose of doing this would be. What it would enable me to do
* I'm just sayin......

gazlufc said:
I had this issue aswell.
To solve it firts fix your permissions in Rom manager.
Then install busy box.
This should then allow you to install ubuntu. (atleast it did with me)
Hope this is some help to you
Click to expand...
Click to collapse
installed newest version of busybox 1.19.0 and fixed permissions and still received the same errors :/

strker45 said:
installed newest version of busybox 1.19.0 and fixed permissions and still received the same errors :/
Click to expand...
Click to collapse
.
Create a backup of you current rom using Rom manager.
Then install a new rom from the developer section of the G2/Desire z
First install busybox.
Second fix permissions.
Third is reboot
open adb and now try the process this should now allow you to install ubuntu.

How To Install Debian Squeeze on LG Optimus V

Hello! This is my first walkthrough for one of my first accomplishments on my first android phone, the LG Optimus V. This guide will show you how to put debian squeeze into a chroot environment on your Optimus V. Lets get started!
Just a side note before we start:
I am not responsible for any mistake you made/in the hardware/software, so any problems with your phone is your own fault. I recommend backing up before a ROM install.
1) Root your phone.
I will not cover this, but there are many guides to root an Optimus V on Google. Just search it!
2) Install Custom Recovery Image (optional if your ROM has ext2 support)
Android 2.2 Froyo currently DOES NOT have ext2 support in the kernel, so we need to install an Android build that does. I used aospCMod, which works flawlessly. Download from dl.dropbox.com/u/14791765/preinstall.zip and unzip it. Move the "preinstall" folder over to your SD card on your Optimus. Now run these commands as root (I recommend using "adb shell" and then running "su" as the shell)
Code:
# The following installs "flash_image" to /system/bin, then makes it executable
cd /mnt/sdcard/preinstall
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
cat flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
# The following flashes recovery-thunderc-v-1.2.0-GNM.img to recovery
flash_image recovery /mnt/sdcard/preinstall/recovery-thunderc-v-1.2.0-GNM.img
reboot recovery
Your phone should reboot into your newly flashed recovery partition
2.5) Install aospCMod (optional if your ROM has ext2 support)
Now, using the volume rocker, the menu button, and the back button, back up your phone, go to "Backup/Restore" -> "Backup Google proprietary system files" and press menu. This will back up your working system.
Now back at the main menu, navigate to "Flash zip menu" -> "Flash zip from Sdcard" -> "preinstall" -> "aospCMod-VM670-20110601-signed.zip". Install the ROM. Now do the same thing, but this time with "gapps-gb-20110325-signed.zip". After that, at the main menu, press "Reboot system now".
3) Create a Debian image file.
You have two options here. One, create your own (recommended) or two, download mine. I would download mine if you don't have linux and don't plan on getting it or don't really have time to set everything up. First and foremost though, you need to download dl.dropbox.com/u/14791765/debian.zip and unzip it to your SD card. My image is located here if you need it: dl.dropbox.com/u/14791765/debian-img.tar.gz Place it in your "debian" folder on your SD card. Afterwards, do these commands
Code:
cd /mnt/sdcard/debian
tar zxf debian-img.tar.gz
rm debian-img.tar.gz
If you do not want to download the whole 84 Mb file (which uncompresses to 1 Gb), create your own by doing this on Ubuntu Linux:
Code:
sudo -s
apt-get install debootstrap
dd if=/dev/zero of=debian.img seek=1024 bs=1M count=1
mke2fs -F debian.img
mkdir debian
mount -o loop debian.img debian/
debootstrap --verbose --arch armel --foreign lenny debian ftp.us.debian.org/debian
umount debian/
If you need the image file to take up less/more room, change "seek=1024" to "seek=[value-in-Mb]".
Now move your newly created "debian.img" to the "debian" folder on your SD card.
4) Install Debian
Almost done!
Back in your root shell, do these commands:
Code:
cd /mnt/sdcard/debian
sh installdebian
sh installdebian2
echo 'deb ftp.us.debian.org/debian squeeze main' > /etc/apt/sources.list
apt-get autoclean && apt-get update
export username="[insertyourfirstnamehere]"
adduser $username (this will ask for some data, put in as much or as little as you'd like)
apt-get install sudo
usermod $username -G sudo
exit
This should blah blah blah about debootstrap and configuring packages. Ignore it. It should finish in about 7-10 minutes. After that is done, the adduser command adds you to the system login files. After you enter "exit", you are all set to run Debian! To start debian, put this in your root shell/terminal emulator:
Code:
bootdebian
Wala! One ready-made LG Optimus V Debian, at your service! From here, you can install pretty much everything for Debian, including XOrg. I may post an update guide for how to install XOrg, VNC, and the like.
EDIT: If "sh installdebian" hangs on "Configuring: sysvinit", just do Control-C, and run it again.

meta1203 said:
Hello! This is my first walkthrough for one of my first accomplishments on my first android phone, the LG Optimus V. This guide will show you how to put debian squeeze into a chroot environment on your Optimus V. Lets get started!
Just a side note before we start:
I am not responsible for any mistake you made/in the hardware/software, so any problems with your phone is your own fault. I recommend backing up before a ROM install.
1) Root your phone.
I will not cover this, but there are many guides to root an Optimus V on Google. Just search it!
2) Install Custom Recovery Image (optional if your ROM has ext2 support)
Android 2.2 Froyo currently DOES NOT have ext2 support in the kernel, so we need to install an Android build that does. I used aospCMod, which works flawlessly. Download from dl.dropbox.com/u/14791765/preinstall.zip and unzip it. Move the "preinstall" folder over to your SD card on your Optimus. Now run these commands as root (I recommend using "adb shell" and then running "su" as the shell)
Code:
# The following installs "flash_image" to /system/bin, then makes it executable
cd /mnt/sdcard/preinstall
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
cat flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
# The following flashes recovery-thunderc-v-1.2.0-GNM.img to recovery
flash_image recovery /mnt/sdcard/preinstall/recovery-thunderc-v-1.2.0-GNM.img
reboot recovery
Your phone should reboot into your newly flashed recovery partition
2.5) Install aospCMod (optional if your ROM has ext2 support)
Now, using the volume rocker, the menu button, and the back button, back up your phone, go to "Backup/Restore" -> "Backup Google proprietary system files" and press menu. This will back up your working system.
Now back at the main menu, navigate to "Flash zip menu" -> "Flash zip from Sdcard" -> "preinstall" -> "aospCMod-VM670-20110601-signed.zip". Install the ROM. Now do the same thing, but this time with "gapps-gb-20110325-signed.zip". After that, at the main menu, press "Reboot system now".
3) Create a Debian image file.
You have two options here. One, create your own (recommended) or two, download mine. I would download mine if you don't have linux and don't plan on getting it or don't really have time to set everything up. First and foremost though, you need to download dl.dropbox.com/u/14791765/debian.zip and unzip it to your SD card. My image is located here if you need it: dl.dropbox.com/u/14791765/debian-img.tar.gz Place it in your "debian" folder on your SD card. Afterwards, do these commands
Code:
cd /mnt/sdcard/debian
tar zxf debian-img.tar.gz
rm debian-img.tar.gz
If you do not want to download the whole 84 Mb file (which uncompresses to 1 Gb), create your own by doing this on Ubuntu Linux:
Code:
sudo -s
apt-get install debootstrap
dd if=/dev/zero of=debian.img seek=1024 bs=1M count=1
mke2fs -F debian.img
mkdir debian
mount -o loop debian.img debian/
debootstrap --verbose --arch armel --foreign lenny debian ftp.us.debian.org/debian
umount debian/
If you need the image file to take up less/more room, change "seek=1024" to "seek=[value-in-Mb]".
Now move your newly created "debian.img" to the "debian" folder on your SD card.
4) Install Debian
Almost done!
Back in your root shell, do these commands:
Code:
cd /mnt/sdcard/debian
sh installdebian
sh installdebian2
echo 'deb ftp.us.debian.org/debian squeeze main' > /etc/apt/sources.list
apt-get autoclean && apt-get update
export username="[insertyourfirstnamehere]"
adduser $username (this will ask for some data, put in as much or as little as you'd like)
apt-get install sudo
usermod $username -G sudo
exit
This should blah blah blah about debootstrap and configuring packages. Ignore it. It should finish in about 7-10 minutes. After that is done, the adduser command adds you to the system login files. After you enter "exit", you are all set to run Debian! To start debian, put this in your root shell/terminal emulator:
Code:
bootdebian
Wala! One ready-made LG Optimus V Debian, at your service! From here, you can install pretty much everything for Debian, including XOrg. I may post an update guide for how to install XOrg, VNC, and the like.
EDIT: If "sh installdebian" hangs on "Configuring: sysvinit", just do Control-C, and run it again.
Click to expand...
Click to collapse
Cool bro

[TUT] Root 2.3.6 Argentinian

ALL THANKS TO Rodrigo José Fuentes (rodrigojfuentes) !!!!!!
NOT to ME!
http://forum.xda-developers.com/showthread.php?t=1606353
http://forum.xda-developers.com/showthread.php?t=1509095
NEW Root method for Motorola Android Phones
Hi! I just created this thread to let you know that thanks to user dettofatto and me, there's a new root method for Motorola Android Phones (I don't know if it will work for other brands).
NOTE: I tried this method with Gingerbread, I don't know if this will work with other versions.
The method is far from easy, but it works if none of the existing exploits and tricks don't.
Ok, there are some simple-like steps to root your phones:
A) if you have droid pro with 2.3.6 argentinian: http://www.mediafire.com/?aweayb68szubuci and go to 2, if you don't have:
1. If you have an unrooted gingerbread, ask for a rooted gingerbread userdata partition image (aka CG37) with a modified local.prop file and USB debugging enabled.
The value that you need to modify is ro.sys.atvc_allow_all_adb from 0 to 1.
IMPORTANT: The best you can do is to double wipe the phone and then modify local.prop an allow USB debugging, so the data partition doesn't have any of your personal information.
Then you can create a userdata partition image by typing this in the shell (with root access)
Code:
dd if=/dev/block/userdata of=/sdcard/CG37.smg
or
Code:
busybox dd if=/dev/block/userdata of=/sdcard/CG37.smg
and let it do its work.
2. Once you got your CG37.smg in the SD card, you will have to boot into linux (so you can use sbf_flash).
3. When you are in linux, you need to extract the folder contained in the zip that you can download here mediafire.com/?n100jj66130lgra
4. Then you need to copy the CG37.smg and your original SBF (the non rooted one) to that folder.
5. Now you'll have to start a terminal with root permissions, and move to the folder by typing
Code:
cd <folder>
(where folder is the folder I just mentioned, without the <>, you can drag the folder to the terminal if you don't want to type its address)
4. Then you need to resize that partition to 200 Mb, since sbf_flash won't allow you to flash a big image (approx. 1,1 Gb). You have to type this
Code:
efsck -f CG37.smg
resize2fs CG37.smg 200M
5. Then you need to type
Code:
chmod +x sbf_flash
and then you need to start your phone into bootloader and connect it to the computer, then you type
Code:
./sbf_flash -r --userdata CG37.smg ORIGINAL.sbf
(where ORIGINAL corresponds to the name of your SBF)
and let it its work.
5. Once the phone started up, you now need to run this command
Code:
bash finishroot.sh
And let it finish the work.
6. Now you have your phone rooted. You can just reboot into recovery mode and do a double wipe, because the files that we needed are now in system partition.
Info:
http://forum.xda-developers.com/showthread.php?t=1509095

1) Error:
e2fsck -f CG37.smg
Click to expand...
Click to collapse
2) When I do this:
bash finishroot.sh
Click to expand...
Click to collapse
I get this error:
Code:
finishroot.sh: line 1: ./adb: Permission denied
finishroot.sh: line 2: ./adb: Permission denied
finishroot.sh: line 3: ./adb: Permission denied
finishroot.sh: line 4: ./adb: Permission denied
finishroot.sh: line 5: ./adb: Permission denied
finishroot.sh: line 6: ./adb: Permission denied
finishroot.sh: line 7: ./adb: Permission denied
finishroot.sh: line 8: ./adb: Permission denied
finishroot.sh: line 9: ./adb: Permission denied
finishroot.sh: line 10: ./adb: Permission denied
Then I finish root on Windows with SuperOneClick 2.3.3

Sudo bash finishroot.sh....
Sent from My Motosola....

dettofatto said:
Sudo bash finishroot.sh....
Sent from My Motosola....
Click to expand...
Click to collapse
Code:
[email protected]:~/Desktop/236ArgenEuro$ sudo -s
[email protected]:~/Desktop/236ArgenEuro# bash finishroot.sh
finishroot.sh: line 1: ./adb: Permission denied
finishroot.sh: line 2: ./adb: Permission denied
finishroot.sh: line 3: ./adb: Permission denied
finishroot.sh: line 4: ./adb: Permission denied
finishroot.sh: line 5: ./adb: Permission denied
finishroot.sh: line 6: ./adb: Permission denied
finishroot.sh: line 7: ./adb: Permission denied
finishroot.sh: line 8: ./adb: Permission denied
finishroot.sh: line 9: ./adb: Permission denied
finishroot.sh: line 10: ./adb: Permission denied

sudo bash finishroot.sh
Click to expand...
Click to collapse
Correct finishroot.sh file:
Code:
chmod +x adb
./adb wait-for-device
./adb root
./adb remount
./adb push su /system/bin
./adb shell chmod 4755 /system/bin/su
./adb push Superuser.apk /system/app
./adb push busybox /system/bin
./adb push bootstrap-1.0.0.5-droid2.apk /system/app
./adb shell chmod 666 /system/app/Superuser.apk
./adb shell chmod 755 /system/bin/busybox
When you are in linux, you need to extract the folder contained in the zip that you can download here mediafire.com/?n100jj66130lgra
Click to expand...
Click to collapse
I attach zip to this message with correct finishroot.sh and bootstrap-1.0.0.5-droid2.apk

dettofatto said:
2. Once you got your CG37.smg in the SD card, you will have to boot into linux (so you can use sbf_flash).
Click to expand...
Click to collapse
this may be a silly question but you mean linux on pc?? not from from the console on the phone
ok, no matter now, I know everything

Do you have a link for the sbf file.
Thanks

Hi,
could somebody reupload zip tools from this dead link (second point)?
mediafire.com/?n100jj66130lgra
Click to expand...
Click to collapse
Okay i missed another post with attachment. Well it's quite simple job, but it require a little knowledge, especially linux basics. But could it be possible to rebuild argentinian sbf with modded CM37? After it root will be possible using SuperOneClick.

radkyz said:
Hi,
could somebody reupload zip tools from this dead link (second point)?
Okay i missed another post with attachment. Well it's quite simple job, but it require a little knowledge, especially linux basics. But could it be possible to rebuild argentinian sbf with modded CM37? After it root will be possible using SuperOneClick.
Click to expand...
Click to collapse
Hmm but after flash this 200mb userdata i have only 200mb storage space... How to bring back full storage space?
Well, i flashed jackpot CM7 again, then restored my backup and i have 1,05GB, and i think i had more storage space before, could somebody confirm thattotal storage space on CM7 jackpot is 1,05
GB?

dettofatto said:
; 2. Once you got your CG37.smg in the SD card, you will have to boot into linux (so you can use sbf_flash).
Click to expand...
Click to collapse
Can somebody help me with this? Boot linux where and how? On PC? Do I need drivers? Or on phone...? What linux?
dettofatto said:
; 4. Then you need to copy the CG37.smg and your original SBF (the non rooted one) to that folder.
Click to expand...
Click to collapse
Original sbf? Original rom that is on phone, right?
dettofatto said:
; and then you need to start your phone into bootloader and connect it to the computer, then you type
Click to expand...
Click to collapse
Please explain this part?
Please please somebody help me about this, I have problems with this Rom (week signal) and I cant do anything until I root my phone...

Ok I manage to root this phone. So I will write down some explanation for future members.
----------------
1.First of all, you must have bootable dvd to boot up Knoppix Linux on your PC.
2.You have to download attachment (Root236ArgEuro.zip) from this post: http://forum.xda-developers.com/showpost.php?p=26551654&postcount=5
3.Download file http://www.mediafire.com/download/aweayb68szubuci/CG37.smg
4.You need your rom in .sbf format (that you currently have, in this case 2.3.6 Argentinian).
5.Extract Root236ArgEuro.zip in one new folder named "root" and put your rom .sbf file in there and also CG37.smg file in that folder. Copy that folder to usb flash memory (because you will need those files in Linux)
6.Boot up in Knoppix Linux. Copy folder from your usb memory to desktop.
Now follow steps from here in original post (I'll write some notes to be all clear):
5. Now you'll have to start a terminal with root permissions, and move to the folder by typing
Code:
cd <desktop/root>
(you have to find your folder that you just copy)
4. Then you need to resize that partition to 200 Mb, since sbf_flash won't allow you to flash a big image (approx. 1,1 Gb). You have to type this
Code:
efsck -f CG37.smg
resize2fs CG37.smg 200M
5. Then you need to type
Code:
chmod +x sbf_flash
and then you need to start your phone into bootloader ( to enter bootloader:turn off your phone, press and hold volume up and down together with power on)
and connect it to the computer (with usb cable), then you type
Code:
./sbf_flash -r --userdata CG37.smg ORIGINAL.sbf
(where ORIGINAL corresponds to the name of your SBF) Instead ORIGINAL.sbf you have to write exact name of your rom name...easiest way is to simply rename your rom name to ORIGINAL.sbf (all capital letters) and code above will work as it is.
and let it its work.
5. Once the phone started up, you now need to run this command
Code:
bash finishroot.sh
And let it finish the work.
6. Now you have your phone rooted. You can just reboot into recovery mode and do a double wipe, because the files that we needed are now in system partition. If your root pass correctly, you will have new icons:SUPERUSER and DROID 2 BOOTSTRAP. Enter DROID 2 BOOTSTRAP; press bootstrap Recovery, allow superuser permision; then REBOOT Recovery; When you enter recovery do wipe user data/factory reset. Then reboot your device. Go to settings/privacy/ and do factory data reset. This should restore your internal memory from 200mb to 1Gb
[/QUOTE]

Yes, confirmed. Factory reset brings back storage.

[Solved] Mount a blank.img formated to ext? to bypass permission limitations?

I was wondering if I could mount an empty.img file so that I could add executable into it and chmod 777 them or what ever the number is maybe 666.
Then I would add the location to my $PATH variable in the "/system/etc/mkshrc" file so I could execute those programs from any directory.
What say you?
Has this been done before?

It works!
Well, I wen ahead and tried it out, I figured "What the hell, its not like I have to format my sd card." It worked!
So what I did
1) I changed directories to Downloads. ("cd ~/Downloads")
2) I created a directory for my image in Downloads, and moved into it. (mkdir image && cd ./image)
3) I created an empty 4 gig image called apps.img using dd ("dd if=/dev/zero of=apps.img bs=1MB count=0 seek=4096")
4) I formated it to ext2 ("mke2fs -F apps.img")
5) I used adb to push it to my phone ("adb push ~/Downloads/image/apps.img /storage/sdcard0/Download/")
6) Then on my phone as su I mounted the image ("mount -o loop '/storage/sdcard0/Download/apps.img' '/data/local/mnt' ") {with single quotes around the directories, the double quotes wrap the whole actual command, you don't need them} [EDIT: I used bash on the phone to do this, ie I "su" [enter] ; "bash" [enter] ; "THE ABOVE COMMAND" [enter]
7) To test I used the python interpreter as my executable so I created a folder in /data/local/mnt called apps,(note* I should have made that folder on my pc before I pushed it to my phone to ensure that the foder was actually in the apps.img file.) I created two more folders "bin" and "lib" using "File Manager" on my phone. I then moved what I needed to run python into those folders (though you'll see I forgot something)
8) I added PYTHONHOME PYTHONPATH and added the bin folder I created to $PATH in the /system/etc/bash/bashrc file (Ask and I'll explain). If you don't have bash the mkshrc file is located "/system/etc/mkshrc" on your phone (if its Sprint SGSIII) adding environment variable there will accomplish the same thing, sorta.
9) I connected my phone to pc w/usb, opened up a teminal on pc, started an adb shell
10)........
Code:
[email protected]:~$ adb devices
List of devices attached
xxxxxxxx device
[email protected]:~$ adb shell
[email protected]:/ $ su
[email protected]:/ # bash
void endpwent()(3) is not implemented on Android
localhost / # which python
/data/local/mnt/apps/bin/python
localhost / # python
'import site' failed; use -v for traceback
Python 2.6.2 (r262:71600, Mar 20 2011, 16:54:21)
[GCC 4.4.3] on linux-armv7l
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> import sys
>>> import math
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
ImportError: No module named math
>>> import io
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/home/manuel/AptanaStudio3Workspace/python-for-android/python-build/output/usr/lib/python2.6/io.py", line 63, in <module>
ImportError: No module named _fileio
>>>
localhost / # exit
[email protected]:/ # ^D
[email protected]:/ $ ^D
[email protected]:~$

I'm thinking that if I can get my mkbootimg tools to work, I would mod an init script to mount the apps.img and then create links for each file in say '/mnt/apps/bin' create a link*in '/system/bin'. this should allow for phones with small or near full system partition install stuff like busybox or your own pprograms. More usefull for a developer.
I wanna try this with pythonforandroid, if I can make python and its modules. accessible during early init or just before the boot process finishes in general, and use it to run python, maybe python can handle boot in a different way, or maybe just one specific. function you might needs.
one big question I have. Does the pythonforandroid interpreter run ontop of the D VM?

Edge-Case said:
I'm thinking that if I can get my mkbootimg tools to work, I would mod an init script to mount the apps.img and then create links for each file in say '/mnt/apps/bin' create a link*in '/system/bin'. this should allow for phones with small or near full system partition install stuff like busybox or your own pprograms. More usefull for a developer.
I wanna try this with pythonforandroid, if I can make python and its modules. accessible during early init or just before the boot process finishes in general, and use it to run python, maybe python can handle boot in a different way, or maybe just one specific. function you might needs.
one big question I have. Does the pythonforandroid interpreter run ontop of the D VM?
Click to expand...
Click to collapse
I don't think so. All command-line programs I know of interface directly with the kernel.
Sent from my S3 on Sense 5 (you jelly?)

CNexus said:
I don't think so. All command-line programs I know of interface directly with the kernel.
Sent from my S3 on Sense 5 (you jelly?)
Click to expand...
Click to collapse
So getting an extended set of Linux (kernel) cli programs working with Android (kernel) is a matter of having the nessissary libraries, kernel prereq., and being compiled for the target processor?
From what I have read, the Android kernel has been cut back so far from the original Linux kernel that its difficult to port "Linux apps" to Android. Something about a slimmed down version of the GNU C/C++ libraries and the Android kernel being designed to run mostly Dalvik.
I haven't tried directly running any "Linux app" (already compiled for arm) on Android yet, but my game plan for that test was to load up an .img file with the nessissary execs, libs, config, etc files (as ext3 this time) and running some scripts that get the paths variables set up and then execute the script, I wrote a short Bash script that sets up python variables and adds others to PATH etc, and it worked, I had python on the img and the img mounted to /mnt/myside and python ran but with some errors, I need to get the variables right, its driving me mad, if its not this its that, last time it was the basic "help()" command not being declaired or something.
Well thats my plan, either these "Linux apps" run on Android without problem or I am going to A) write my own kernel to be compatible with Android/ cli Linux or I am going to get as much source code as I can and practice the art of compiling against Android and/or patching the code when/where nessissary.
We'll see what happens, I've done enough today/night.

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