Edit: Have a look at this thread: (MSC Mode for XPS). It could be a good workaround for your problem. MSC mode is kind of oldschool, but fine for copying things around.
If you want MTP support on Ubuntu, try this:
Connect Xperia S to an USB2 port.
Use the "lsusb" command to list your devices in a terminal
One of the lines should look like this:
Code:
Bus 002 Device 012: ID 0fce:5169 Sony Ericsson Mobile Communications AB
Note your vendor- and product id. Usually this is "0fce" for the vendor and "5169" for the product id. If you have USB debugging disabled, product id will be "0169".
unplug your phone
read this thread: humans-enabled.com
Install the newest Version of "libmtp" and copy the 69-libmtp.rules file to /etc/udev/rules.d as described
Edit: This step may not be necessary for you!
Xperia S support is implementet in the libmtp-1.1.3. release. If you use the newest version from sourceforge.net skip this and go to step 7.
type following to edit the copied file as root:
Code:
sudo gedit /etc/udev/rules.d/69-libmtp.rules
Add the following text somewhere around the sony ericsson devices that are in this file. You can find them by searching for "0fce". Remember to set the correct vendor and product id:
Code:
# Sony Xperia S
ATTR{idVendor}=="0fce", ATTR{idProduct}=="5169", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
ATTR{idVendor}=="0fce", ATTR{idProduct}=="0169", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
reboot, or use
Code:
sudo udevadm control --reload-rules
to actualise.
Plug in your device to a USB2 port, it will mount automatically. Use nautlius to copy files around.
Please let me know if it worked for you.
I tried the solution u proposed, but I can only see 1.1 gb and if I go on storage on the phone settings, it says the external storage is mounted, but nothing about the 26gb or so of the internal storage, which in fact I can't see at all in my ubuntu nautilus.
don't really know how to deal with this...which version of ubuntu do u have?
Hi memfel
I just tried it on another laptop and noticed my tutorial was not complete.
Please read my edited Tutorial again. I am quite sure it will work like that.
Thanks for your response
hi, thanks. now the difference is that it asks me if I want to use rhythmbox to see the connected device...nonetheless, still I can only see 1.5 gb partition, and not the all drive of the phone...that is, I can't move any file, because of those 1.5 gb most are already occupied... really don't know how to manage this, it's kinda crazy...
I found an app that seems to work, but the free version allows only to move 1 file or so...I can see 25gb there, through the web browser, but I find it so incredible that I'd need to pay for an app to do such a simple thing such as being able to connect the phone to my laptop and move files around...
Did you copy the libusb file to the right path?
Does it change something, if you enable the usb debugging mode?
If you don't succed with a USB connection you could still use airdroid. It works with wifi tethering or over a wlan router.
nope USB debugging doesn't seem to make any difference.
what I'm trying now is to force a copy of some gb of files, also if it shows no space. I realized after making a video that when the space that get showed up is full, then it shows more, so it went from 1.5gb to 4.4...don't know why such a move, but seems like there's a bug perhaps somewhere.
'Funny' thing is, to copy 2gb it's taking 1h....do u also need all this time?
Just tested it: It took me about 3 minutes to copy a 2 GB video to the phone.
Did you flash a newer Firmware? Do you have root access?
I have rooted my XPS, but i don't see why this should make a difference...
not rooted still, and no firmware change...really have no idea why it works this way...it's really weird I think.
Forcing copy didn't work, I got errors at one point, and all got blocked. Also, some files were copied on the phone, but when I tried to open the directory I copied, nautilus continued to crash all the time, so I am also not able to access the files that I copied...
I guess it's something broken with my ubuntu installation...perhaps going to be solved with 12.04...
Yes, they will hopefully integrate full MTP support into Ubuntu 12.
Just don't try to update your (broken) system from 11 to 12 with the update manager
let's hope I have the time to do a new install by the time 12 comes out. but in the meantime, if u have any other idea...let me know.
just to be precise...how many gb do u see when u connect ur phone?
---------- Post added at 09:44 PM ---------- Previous post was at 08:47 PM ----------
well, I retried to copy files over the allowed and visible size, it worked quite faster, and there I go, there appear some more gb of visible space...around 4.5 now...not all the disk, but still, it might mean the space shows up when needed even if at first it seems it's not there.
gparted and other partition managers do not list the phone, because it's not a mass storage device. So where did you find a size of the volume?
when u open nautilus, u will have the phone showing up...u find the name of the device on the left pane, but also on top of the pane where u see files and folders once u click on the device to open it.
if u do right click on the name above this folders and files pane, u select properties, and there u go...u see the size of the disk...
hope the description is clear enough!
Nice, didn't know that so far.
Here is a Screenshot of what i see
I guess u might see all that space perhaps because u have already a lot of stuff on the phone, or because u are rooted and somehow this influenced the connection...nonetheless, interesting that when I connect the phone via that web app that I found, it was showing me 25gb, u seem to have more...
Do u know what all the other space to 32gb is for? apps and system? or what? seems kinda lot of space that can't seem to be accessed.
See the calculation here:
www.fischerclan.de/byte_umrechner.html
So the 32GB should be like 29.8GB on our system.
I see only 27.7 of it, so there are like 2GB on some kind of hidden partition. Don't ask me, what they use it for
interesting. and rooting doesn't make those gb more available...perhaps we'll see more when roms start coming out!
Yes, can't wait for CM9!
Hi,
Same as memfel for me.
I only see a 1.8g partition after the installation of libmtp.
can't do anything on it, I straigtly have an error message.
One thing that could explains some others in the first post the phone is identified like this:
Bus 002 Device 012: ID 0fce:5169 Sony Ericsson Mobile Communications AB
Click to expand...
Click to collapse
whereas mien is seen like this
Bus 001 Device 004: ID 0fce:0169 Sony Ericsson Mobile Communications AB
Click to expand...
Click to collapse
What version of libmtp did you install?
Have you tried adding your device id manually?
Angralon said:
If you are trying to connect an Xperia S to your Ubuntu System, you will usually fail (as i did).
It took me like 4 hours until i found a solution. So let me share how it worked for me:
Click to expand...
Click to collapse
As I mentioned in the other thread, there is limited support for accessing Xperia S storage out of the box in Fedora 16. Namely, I could browse the files, copy files into XS but couldn't copy any files from it.
So, after applying udev rules you've suggested (btw, no need to reboot,
Code:
sudo udevadm control --reload-rules
will suffice) I can confirm that accessing internal storage is now two-way, hell yeah! I can see 20-odd GB of free space, however gMTP still doesn't recognize the device, as well as Rhythmbox. Banshee only recognizes it after adding ".is_audio_player" file in root of XS, however doesn't find any music in it.
Nonetheless, two-way data transferring via Nautilus is what I care about most, so I'm happy. Thanks for working solution to this!
UPDATE:
Ooops, looks like two-way doesn't exactly work as expected. Not sure what I did wrong but now I can't copy files from XS again. :/ Will need to tinker around it a little bit more...
UPDATE 2:
Some file are copying from XS happily, some don't throwing either "unspecified" or "unsupported" error in Nautilus. Weird..
---------- Post added at 05:34 PM ---------- Previous post was at 05:28 PM ----------
hercule18 said:
Hi,
Same as memfel for me.
I only see a 1.8g partition after the installation of libmtp.
can't do anything on it, I straigtly have an error message.
One thing that could explains some others in the first post the phone is identified like this:
whereas mien is seen like this
Click to expand...
Click to collapse
Difference between:
Code:
Bus 002 Device 011: ID 0fce:0169 Sony Ericsson Mobile Communications AB
and:
Code:
Bus 002 Device 012: ID 0fce:5169 Sony Ericsson Mobile Communications AB
is determined by USB debugging mode. Ideally you'd like your udev rules to read:
Code:
# Sony Xperia S
ATTR{idVendor}=="0fce", ATTR{idProduct}=="0169", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
ATTR{idVendor}=="0fce", ATTR{idProduct}=="5169", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
Related
Hi i was just looking for some quick clarification if anyone is willing.
Boot into Clockwork Recovery. -DONE
Navigate to "mounts and storage". -DONE
Select "mount USB storage". -DONE
Copy /usr/src/tegratab/boot-custom-kernel.zip to the mounted filesystem. -HOW?
I tried adb push /usr/src/tegratab/boot-custom-kernel.zip /sdcard I dont believe it worked since nothing actually happened. I didnt even get my command line back. Im just waiting though, its been about 10 minutes though, I really dont think anything is happening. Actually it just finished, and now my tab is locked up. After I fix this I hope someone will be able to tell me how to properly install this. Also when I go into the android system then turn on usb storage device and try and drag and drop it says its going to take 3 hours?
I cant seem to figure out how to copy my file to "the mounted filesystem" I dont get a filesystem that I can drag and drop my zip into, I dont see or know of a command to do it through the terminal. So how can I accomplish this?
Thanks!
DKS1282 said:
Hi i was just looking for some quick clarification if anyone is willing.
Boot into Clockwork Recovery. -DONE
Navigate to "mounts and storage". -DONE
Select "mount USB storage". -DONE
Copy /usr/src/tegratab/boot-custom-kernel.zip to the mounted filesystem. -HOW?
Click to expand...
Click to collapse
Need details--
Whose kernel is this? Is it for the gTab? Where was it compiled from (source)? Is it stable? Has it been tested? Why is the guy telling you to copy the zip file onto the internal SD via ClockworkMod when you can do it more easily by other means? Can I have a look at the contents of the zip file?
really? in order to install it you have to know all that? The zip file is over 1.5 gigs.. How do you propose I get it to you?
DKS1282 said:
really? in order to install it you have to know all that? The zip file is over 1.5 gigs.. How do you propose I get it to you?
Click to expand...
Click to collapse
This kernel better be able to sing and dance for you if it's that big. What the hell is in there? I want to see what's in there now.
DKS1282 said:
really? in order to install it you have to know all that? The zip file is over 1.5 gigs.. How do you propose I get it to you?
Click to expand...
Click to collapse
This is why I asked you for the details. A compiled kernel for the gTab, along with the most useful modules, plus the installer program, is about 3MB, max.
The complete Linux kernel source, uncompressed, is around 450MB. Compressed, it is ~100MB. A compressed 1.5GB file would therefore contain a heck of a lot more than just the kernel sources. What were you expecting to happen here? Ram a boat-load of source into the tablet and it should automatically compile and install everything for you?
Actually no... I followed a link and followed directions and I actually thought I was doing well till I saw the size of the file... Im actually going to work on recompiling the kernel again. It was a version of pershoots but I think the tutorial I was working off of is incorrect as are most of them on the net. Im learning but sadly not at the pace I would like, Im new to linux and android. Thank you all for the help so far. I'll post what ive done here in a lil bit and I was wondering if I would be able to get advice on how to install it... Ill even link the tutorial I follow. Here it is http://forum.xda-developers.com/showthread.php?t=916198
Now that Ive gone over it again its an issue in the zipping... For some reason my 28.7M file zips to 1.6gb WTF? Here is the command I used
From inside the file where the contents is to be zipped zip -r /usr/src/tegratab/boot-custom-kernel *
Yes evey time I zip it it comes out to 1.6 gigs. The system file is is pretty small but after its been ziped it actually takes most of the 1.6gb... Could I possible send the meta file, kernel file, and system file? Or maybe someone could tell me how to correctly do this? Ive followed the directions in that link and thought I was getting a legit output but I guess that im not even close.
GOOD NEWS EVERYBODY! I can save you 15% on car insurance...
Actually I was able to figure out what has happened... There were some symlinks that didnt get removed so it grabbed everything in that link and zipped it as well... after I fixed the issue it zipped correctly and I was even able to get it to install... Sadly the prolific driver for the 2303 is still not included even though it shows on the kernel menuconfig as being included, I guess Im going to try again and make it modular and see if I can get the driver file to install that way.. Ill let you know how it goes and also upload and link it if I can get it to work in case someone else wants to grab it and build off it. Im also planning on helping out the forums a little bit...
Thank you again.
DKS1282 said:
Sadly the prolific driver for the 2303 is still not included even though it shows on the kernel menuconfig as being included...
Click to expand...
Click to collapse
Attach the .config (kernel configuration file) so I can look at it.
Does running dmesg on the new kernel show the driver loading/initializing?
Are the /dev/ttyUSB* device files present? Are the permissions for those serial devices correct? I'm not sure what they ought to be, but try making them read+write for all--at least while you are testing things: chmod 666 /dev/ttyUSB* as root.
Here is actually the zipped kernel file. When it compiles it does show the drivers being installed, I just cant get the device to recognize the Prolific cable. Ive tried including them, Ive tried modular, im not sure how to make it work, or if there is something im missing entirely. Thanks again.
http://www.mediafire.com/?nil9bh3spu6sp78
DKS1282 said:
Here is actually the zipped kernel file.
Click to expand...
Click to collapse
The binary is no use to me--I don't have your hardware. The .config file is what I need.
When it compiles it does show the drivers being installed, I just cant get the device to recognize the Prolific cable.
Click to expand...
Click to collapse
The real test is the dmesg output, not whether the driver is being compiled in.
However, I think your problem is that you've compiled the wrong driver. What you need is the driver for "Prolific PL-2301/2302 based cables" which is included by enabling:
config USB_NET_PLUSB
which depends on
config USB_USBNET and
config EXPERIMENTAL
The module will be called plusb.ko, I think.
Sorry for being really uneducated on this. But I can not find any of thoes that you listed in the kernel. Also I cant even find the config file. I know where im targeting it from command line but if I try to move it it says file not found, and if I try and go there visually the file isnt there.
Id love to be able to upload what you want to see, and Id love to be able to add in the items you just suggested. But alas. neither seems possible.
Its honestly odd to me.. Ive been reading a couple different posts on the net that say you install this driver for the Prolific 2303. But not the PL2303.... So why is it included when it doesn't do what its supposed to do? Ive tried a lot of different methods and none of them work. It sucks cause I see people using it. Maybe Its not the kernel and its the android OS? I really have 0 clue at this point and about to just give my resignation at my employment.
The .config file will be present in the kernel's main directory (/usr/src/tegratab/gtab-2632/.config) if you have already built a kernel.
It looks like there are 2 drivers for Prolific hardware in the source tree. One is for host-to-host cables with Prolific chips (which is not enabled by default, and which, I think, is what you want), and the other for a Prolific USB serial port adapter (which is already enabled by default).
To build the module for the first, do a make menuconfig, then select:
Device Drivers > Network device support > USB Network Adapters > Prolific PL-2301/2302 based cables
However, you should verify what you have before you build the module. Do a "lsusb" then check the USB device IDs against the USB ID database in /var/lib/usbutils/usb.ids on a regular Linux machine.
Hints:
0. See pershoot's hints to another user here and further along in the same thread.
1. Make sure that you have downloaded the correct pershoot kernel: froyo or gingerbread.
2. You don't need to include all the modules in your kernel zip file. Just overwrite the kernel proper (zImage), the wireless driver (bcm4329.ko) and then add only the prolific driver module. Otherwise you're just wasting space on the /system partition.
3. Sign the zip file after creating it.
Thank you so much for the attempt.
But my .config file is not located where you have directed me. I checked there before, I could send you a screen shot showing you this.
Thank you for showing me where the driver for the cables where, I would not have checked network adapters looking for USB.... Alas, this has not solved my problem. The cable is still undetected by the OS. Although almost EVERY other usb is detected.
Im really not sure why this wont work. It installs 100% fine I have 0 issues on this, but the Prolific 2303 usb to serial cable will not show up in log cat or anything.. Although when i adb shell and do lsusb I see it and it has a device ID and everything.
Thank you again for the help..
DKS1282 said:
But my .config file is not located where you have directed me.
Click to expand...
Click to collapse
It is created in the kernel's top-level directory (ie. the same directory as the file REPORTING-BUGS) after you do "make menuconfig".
If you still can't find it, do,
find /some/path/ -name .config
after you've finished "make menuconfig". Replace /some/path/ with your kernel source dir (or / to search everything that is mounted).
Alas, this has not solved my problem. The cable is still undetected by the OS. Although almost EVERY other usb is detected.
Click to expand...
Click to collapse
If the driver is built as a module then the kernel will recognize it only after you have loaded the module. Load the correct module first, either plusb.ko or pl2303.ko, depending on your hardware, then check for detection/initialization messages from the module by issuing a "dmesg" command immediately after the "insmod /some/path/driver.ko" command.
Im really not sure why this wont work. It installs 100% fine I have 0 issues on this, but the Prolific 2303 usb to serial cable will not show up in log cat or anything.. Although when i adb shell and do lsusb I see it and it has a device ID and everything.
Click to expand...
Click to collapse
Still lacking details:
1. Did you download the correct kernel--Froyo/GB?
2. Are you sure you're running the new kernel after flashing the zip file?
3. Did you insmod the correct module?
4. What is the USB device ID shown?
5. Did you run dmesg--not logcat--after you insmod'ed the correct module? Can I see that dmesg output?
I can not find a .config file anywhere on this computer. it just does not exist.
Yes I am using a gingerbread version.
Insmod does not install anything for me. Although I installed the modules before even packaging the kernel. Ive verified this by checking in the the correct driver files once installed.
I dont remember the device Id exactly but its something similar to 067b:2303
I didnt run dmesg, honestly, this is way beyond me. I have absolutely no clue what im doing at all... I wasnt even hired for this job.. I was supposed to create an app that will use this specific cable on this specific device, although they did not give me the device able to use the cable... So now I have to figure out how to do this, and im just going to resign and tell them im not a hacker im a developer. Thank you very much for your effort but I am turning in my resignation here now at the end of the day. Thank you again and I'll give you thanks.
You had asked a while back if dev/ttyUSBx has shown, and I did get that to show last night. its dev/ttyUSB0 Ive tried to use a usb to serial api but the app couldn't open the serial port... Im guessing because android does not support that (since they dont really support anything) I personally dont even understand why these things sell... Its a giant useless phone that can not make phone calls. Im in the wrong business I need to sell useless products to consumers.
DKS1282 said:
I can not find a .config file anywhere on this computer. it just does not exist.
Click to expand...
Click to collapse
You a) didn't search correctly, b) haven't built the kernel yet, or, c) done a "make mrproper" and cleaned up.
Yes I am using a gingerbread version.
Click to expand...
Click to collapse
Which ROM?
I dont remember the device Id exactly but its something similar to 067b:2303
Click to expand...
Click to collapse
You cannot be vague about this. Run a Terminal emulator on the gTablet (download one from Market if needed), then type in the command in bold:
Code:
$ [B]lsusb[/B]
Send me the output of lsusb.
I didnt run dmesg,...Thank you very much for your effort but I am turning in my resignation here now at the end of the day.
Click to expand...
Click to collapse
Steady on, mate--we'll get you sorted: Just send me the lsusb output and I'll build a kernel for you--if the current kernel sources include the driver code.
You had asked a while back if dev/ttyUSBx has shown, and I did get that to show last night. its dev/ttyUSB0 Ive tried to use a usb to serial api but the app couldn't open the serial port...
Click to expand...
Click to collapse
Does the app have permissions to read/write the device? Use the chmod command I gave in an earlier post to give permissions.
Next: once the actual hardware is connected to the Prolific cable, is data appearing on /dev/ttyUSB0? Run,
Code:
$ [B]hexdump -C /dev/ttyUSB0[/B]
to see if any data appears.
But, this depends on the device. Some devices need to be triggered, either electrically or by sending commands to the port, before they will send anything back. Other devices will spit data out as soon as power is applied to them.
Which kind is yours?
lsusb returns 067b:2303
My device needs to have data sent to it in order for it to start spitting out data. Otherwise there is nothing happening. It requires a 16bit hex "Start Command". So of course $ hexdump -C /dev/ttyUSB0 returns nothing.
I have the kernel I built here, as well as the gingerbread 2.3.4 rom i am using, and Ive also included the Gaps I needed to install into 2.3.4 to activate the USB feature. (why isnt that feature standard since its really the only difference for 2.3.3 and 2.3.4?
http://www.mediafire.com/?1phzkmvhtr0li
Thank you again.
Honestly you know what would fix all of this... Being able to install windows 7 on this tablet. I know the viewsonic view pad has a dual boot android / windows 7 how cool is that?
DKS1282 said:
lsusb returns 067b:2303
My device needs to have data sent to it in order for it to start spitting out data. Otherwise there is nothing happening. It requires a 16bit hex "Start Command". So of course $ hexdump -C /dev/ttyUSB0 returns nothing.
Click to expand...
Click to collapse
That's assuming that /dev/ttyUSB0 is the correct port, which may not be the case.
Right after the tablet has booted, load both the Prolific kernel modules (or only plusb.ko, if the other is built into the kernel--you still haven't sent me your .config file), attach the Prolific cable to the tablet, then attach the actual device to the cable, then run a
Code:
$ [B]dmesg > /mnt/sdcard/dmesg.txt[/B]
command. Attach the dmesg.txt so I can look at it.
Couldnt do it. Lost the job. Thanks anyway.
Notice:
Click to expand...
Click to collapse
Sorry guys this no longer works...
Ubuntu removed alot of the files needed to run it on a phone off of their website which is why you are getting the errors on the script to try and install it.
Recapped:
Here's what I mean the website the script is going to to get the files no longer exists...
Heres an example to see for yourself: http://ports.ubuntu.com/ubuntu-ports/pool/universe/t/tightvnc/tightvncserver_1.3.9-4_armel.deb
I will try and find a new link to plug in but for now it DOES NOT WORK!
Thank you for your patience on the thread,
StrumerJohn
==== How to Install Ubuntu Linux on your HTC EVO 3D / Sensation 4G ====
Table of Contents
Post 1
1: Disclaimer
2: Pre Requirements
3: PC Guide to push to phone
4: MAC Guide to push to phone
5: Additional Scripts
6: Credits
Post 2
1: FAQs
2: Recognitions
Post 3
1: News and Updates
2: Additional Notices
Click to expand...
Click to collapse
-Disclaimer-
This has been tested on my phone and runs perfectly fine, I am not responsible for you breaking, bricking, or dropping your phone on the floor and causing the USB cable to fall out and blow up your device.
Pre Requirements:
A rooted HTC EVO 3D or Sensation 4G
A S-off'd HTC EVO 3D or Sensation 4G
netarchy's kernel (Silverneedle Test5)
Android SDK
The USB drivers for your phone. (x32) (x64)
A microSD Card
2.3 GB Free of space on your microSD card
Know how to read to directions
Click to expand...
Click to collapse
The intense Procedure:
1. Download this version of Ubuntu. [Download #1] [Download #2]
2. Unzip the Ubuntu folder to your desktop and if you want, delete the compressed one you downloaded.
3. On your phone go to Settings > Applications > Development and turn on USB debugging.
4. Plug in your USB cable (from your computer to your phone) and mount your (mirco)SD card.
5. Move or copy over the unzipped / normal Ubuntu folder. This will take a long time unless you have a class10 microSD card.
6. After moving / copying that file over, tell your phone to unmount the (micro)SD card / Set the phone to Charge Only mode.
7. Now on your computer, go to where you have Android SDK installed. (Example on my computer: E:\Program Files (X86)\Android\android-sdk )
8. When in the main SDK folder, hold shift and right click a blank area and then click on "open command window here". It should of opened the command line window with the directory of your SDK already put in. If not type cd "C:\Your directory or location of your SDK"
9. Now type "cd platform-tools"
9.5. (Optional) "type adb devices" and check if the computer recognizes your phone. If not you need to reinstall your drivers from the download link above in the requirements.
10. Type "adb shell"
11. Type "su" so we have superuser permissions
12. Type "cd /sdcard" so the directory is changed to the (micro)SD card
13. Type "cd ubuntu" so the directory is changed to the Ubuntu File
14. Type "sh ubuntu.sh" so we can install Ubuntu
15. Type "bootubuntu" to start up Ubuntu. Next time you enter Ubuntu, you just need to type "bootubuntu" from your /sdcard/ubuntu directory, there is no need to run ubuntu.sh again.
16. If you got "[email protected]" in the command line, you have sucessfully installed Ubuntu. If not make sure you installed netarchy's kernel. If it still does not install correctly please try a different ROM, I have only tested this on SteelROM 1.1. *AFTER INSTALLING ANY ROM, YOU NEED TO REINTALL THE KERNEL.*
17. Now type "apt-get update" to update Ubuntu to the latest version. Then "apt-get upgrade" to apply the update.
18. Type "apt-get install tightvncserver" to install the vncserver. (Your telling your phone to read off it self pretty much.)
19. Type "export USER=root" To make yourself a user / the user
20. Type "vncserver -geometry 1024×800" to set the screen resolution you want to display on your phone. Remember you can always zoom in by pinching, so you don't need to make this that much smaller. You should also get prompted to set a password, do so. You will need to remember this password to log in.
21. Download the AndroidVNC Viewer off the Market here.
22. Open the viewer, and put in a nickname, your PASSWORD FROM ABOVE, and for the IP Address put: 127.0.0.1 for the port put 5901. THEN SCROLL DOWN and make the COLOR FORMAT 24-bit colors (4bpp).
And finally, hit Connect to launch Ubuntu on your phone!
For Mac users:
Finder -> Applications -> Utilities (folder) -> Terminal
When you cd to where your adb is located, cd is lowercase as are most all unix commands.
If you're unsure where to go, get to adb in your Finder, right-click, get info, the pop-up will show you the path. Note in unix that the folders (subdirectories) are separated by / and not by \ like in Windows.
Once you're there, the only trick you need to know is to tell unix that adb is located where you are, so you change the adb shell command like this:
./adb shell
That's about it, all other instructions once you're inside the phone shell are the same.
OBTW - after the unzip of the initial file from the OP, just drag and drop the whole ubuntu folder to your NO NAME drive (normal sd card formatting doesn't get a name at the factory, so by now you know that your sd card mounts like that anyways I'd suppose - just put it here in case).
Click to expand...
Click to collapse
Additional Scripts
Danaff37's
danaff37 said:
That's the script catted out.
I posted a different script a few pages back that I think will help you guys. I modified it so we should have no trouble with apps in sd.. I finally got a bigger sdcard so I can test this stuff and this script works great. Please guys try this script. If you download it in phone it will change the name and add a bin on it I think, so rename it accordingly and make sure it gets into /system/bin with the right permissions (755 or rwxr-xr-x), then run it
http://db.tt/gin57Gd
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Credits:
Ubuntu Modded and Guide by: Me
Mac Guide Written by: EarlyMon
danaff37's Script by : danaff37 (of course)
Original dev of Ubuntu: Zedomax
If you have any problems beside the slow downloads because of the blown up servers, let me know below. Also I tried to type this fast, so if there is any typo's or broken links let me know too! Thanks!
Also feel free to hit the Thanks button or Donate for more Guides
FAQS
FAQS
Do I need to have everything in the android-sdk downloaded and installed?
No, you just need to have the base sdk.
When I tell the command prompt to adb devices, my phone does not show up!!
Make sure you have installed the proper drivers for your phone and for your correct operating system
I'm not getting "[email protected]" when I type / copy-&-paste "bootubuntu"
Well, this could be for a various amount of reasons, first make sure you have a rooted HTC EVO 3D/Sensation. And by root, I mean a full root, not just a temp root or S-off. If you still do not get "[email protected]", flash your device (or go though your data folder and delete all the ubuntu files, then delete the ubuntu file off of your sd card and clear your caches.), and retry the above steps. If the problem still persists, then please PM me with your exact problem.
I'm having issues within the VNC, and I get an error message when I hit "connect".
Make sure you typed your password correctly, the passwords are case sensitive. If you still cannot get in, make sure your IP Adress is set to "127.0.0.1" and your Port(s) are "5901".
The colors on my screen look all weird and disorientated, how do I fix this?
Close Ubuntu, and re-open the VNC application, then scroll down to "Color Format" and tap on "24-bit color (4 bpp)".
The on-screen keyboard does not work and I get a different letter or character for whatever character I type!
The on-screen keyboard will work now, if you install LXDE.
I'm not good with reading text! I need a video demonstration!
For a video head here: http://www.youtube.com/watch?v=YbunTRzEQCI
How do I close Ubuntu?
Two options here:
1.Logout of the server and go to your homescreen and push menu, then go to settings, then Applications, then Running Services and close any remaining open part of the server program. The service may re-open later, do not close it though. It won't use up a noticable amount of RAM, just enough to make sure the application opens quick again.
2. Logout of the server and use your favorite task killer to close the server process. The service may re-open later, do not close it though. It won't use up a noticable amount of RAM, just enough to make sure the application opens quick again.
FAQS should be in order chronologically (until the end of them).
I would like to give a huge thanks to EarlyMon, for helping out lost members. This thread would not be as peaceful if it were not for him.
And it seems I have forgotten to list another VERY helpful person here, danaff37. I am really grateful to both of these two for all of the help and work they have done to aid others.
Am I missing a question that you are pretty sure is asked ALOT (lol)? Then PM me please and I'll get it up here ASAP!
Upcoming Change log for final release:
(StrumerJohn's Zedomax Ubuntu Mod)
Made a launchable .exe for easier updating and installing of Ubuntu
Default mode LXDE for fixed keyboard
Pushes Server application to your phone
Fixed a few problems that caused people to have an error in installing
Server application updated
Fixed port issues for log in errors
News update 11/13/11
Bad news and Good News:
Ubuntu was successfully updated
Update brakes keyboard
Update breaks Apps2SD
Update takes up less space (1GB instead of 2GB)
Update ONLY works on MIUI so far
Updated script to add work around for those facing issues
Computer .exe only working on x64 Windows 7 computers ;-;
Thank you for those of you testing! Might make this open Beta...!
Version as of 12/12/11
Alpha Build 1.0
What Doesn't Work so far:
Boots to latest version only to lock up phone (Unless you are running MIUI)
Keyboard borked
Doesn't work on ICS
Audio Broken
Apps Saved on SD
What works:
Everything else
Sweeeeet.
Appreciate my help? Thank me
Wow this is amazing! Never used linux before tho...
Haven't looked at the bootubuntu script yet, but I know a lot of these couldn't work if you had any apps on sdcard at all. Each app moved to sd takes a loop device.
Sent from my PG86100 using XDA App
maazing will try tonight!!!!!!
danaff37 said:
Haven't looked at the bootubuntu script yet, but I know a lot of these couldn't work if you had any apps on sdcard at all. Each app moved to sd takes a loop device.
Click to expand...
Click to collapse
Just moved partially like moving to the SD or Actually having them Downloaded and Installed to the SD?
Interesting. Nice write up
Sent from my PG86100 using XDA Premium App
Cool...
But, why.
Cause you can?
Sent from my 3vo via Tapatalk
Because Ubuntu has some computer applications you can't normally use on your phone. In the browser download Java and check out runescape runs like shizzle but once we get new quad phones out I'm sure it would run fine. lol
This is what I wanted. Million thanks....
Sent from my PG86100 using www.psvitahacks.co app
Added to my 'Complete LIST' thread: http://forum.xda-developers.com/showthread.php?p=16132451
StrumerJohn said:
Just moved partially like moving to the SD or Actually having them Downloaded and Installed to the SD?
Click to expand...
Click to collapse
Using the stock apps to sd like under manage applications (like the same as is available on a non rooted phone). The script for ch rooting can be made to work around it though. But most aren't.
Sent from my PG86100 using XDA App
danaff37 said:
Using the stock apps to sd like under manage applications (like the same as is available on a non rooted phone). The script for ch rooting can be made to work around it though. But most aren't.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
If there are any small minor problems like that and it's not working proper, let me know. I'll mess around with some things and release a patch.
Installed successfully and works great except I can't type cause of the keyboard glitch. Anyway around it?
Sent from my PG86100 using XDA Premium App
Working with shooter rewind
akiradavis said:
Installed successfully and works great except I can't type cause of the keyboard glitch. Anyway around it?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
The only way to get around it atm (at the moment) is to use a bluetooth keyboard.
Very sweet! I will test this tomorrow when I get home. It should work on my ROM as well
Nice....can't wait for the keyboard fix.
Hi! So I'm wondering if anyone know if there is\have been any development for
the Tizzbird Stick N1 (M\G) ?
We have this Android-stick in stock at my store, but I'm not sure if I'm going to get it or not yet. Depends the development, as I'd really like to see the capabilities for it. I believe it's a lowbrand tho. so I might be out of luck.
Anyone know anything?
I searched the forums, and did a google search. Didnt find much.
regards,
Dag M.
Hi there!
I own one of those, and there are a handful of (german-speaking) people activly posting in this forum http://forum.tizzbird-tv.de/ about the Tizzbird N1. - The problem with that forum is that they heavily censor it - as soon as anyone posts info on how to "get in", or if someone asks uncomfortable questions - those posts gets deleted.
They sell it really cheap for 30€ (not all the time, but twice for one day @ redcoon) and although the Wifi-Chip (or the drivers for it) are really crappy, the media player part is really nice.
update: I've did a little research, and here is a little list of relevant links about the tizzbird n1:
==== Marketing Product Pages ====
http://valueplus.co.kr/english/product/product_player_n1.html
http://www.tizzbird.com/eng/index.php?mm_code=719&sm_code=755
http://tizzbird-tv.de/tizzbird/tizzbird-n1.html
==== Official Firmware ====
http://www.tizzbird.com/eng/index.php?mm_code=726&sm_code=727&board_search_head_word=stick+n1
http://download.tizzbird-tv.de/TizzBird_N1G_update_GMS_V3_20_13072719.tzbird
==== German Support Forum (posting info about root-access prohibited) ====
http://forum.tizzbird-tv.de/viewforum.php?f=11
==== GPL-Code for Tizzbird N10, N20 & N30 - but not for N1? ====
http://www.tizzbird.com/eng/index.php?mm_code=752&sm_code=754
==== Kernel Sources ? ====
http://www.cnx-software.com/2012/03...k-n1-android-ics-hdmiusb-dongle-media-player/
http://www.cnx-software.com/2012/07...hips-tcc8925-mini-pcs-cx-01-z900-tizzbird-n1/
https://github.com/cnxsoft/telechips-linux
Yeah, the pretend to be "community friendly and supportive" but once you actually start digging in, they get quite agressive and boot you out.
Anyways, I got a N1 a couple of days myself now (snagged it for 30 bucks at another RedCoon sale ) and I am surprised.
Got it pretty much only to tinker around with it and this thing suits more perfectly for that than I imagined.
Esp. that fact they used a simple SD card as "internal flash storage" - my guess is because a simple SD is cheaper than an actual eMMC flash chip, but it's so cool on so many levels for us.
I already found out how to replace the 4GB SD with a bigger one (have a 16GB in mine ATM).
I'll post some more details about it here later, got a few things I want to test and/or prepare first (thinking of some "easy to use cloning script"), but long story short:
You need to copy the bootloader to the very end (last few blocks) of the SD you want to use.
Once the BL is at the proper place it already boots from the new SD again, to be sure everything is as it's supposed to be one should apply an update via USB (I'm not 100% sure about a possible pointer to the BL that needs to be corrected, which the update does).
After that the partition information has to be edited to make the userdata partition larger and you're done.
thanks for the info HellcatDroid!
It would be great if you could elaborate on how to put the bootloader at the end of the sd-card.
Also I would love to get info how to get root into the stock firmware, that crippled down root-firmware that they allow to exist in the official tizzbird forum doesn't really satisfy my needs
I did it via a hex editor, but it should be doable with a few "dd" commands as well - that's one of the things I still want to try, find the propper dd params to copy the BL over.
If you dumped the original SD into a file using dd, at the very end of the image file you will find the bootloader and the very last block of the SD is a "header" telling the bootrom of the N1 a few things about it, so it can properly locate and load it.
So what you got to do is to copy those last ~230k from the image to the end of the new SD card.
As said, I'll try to write a small shell script that does it.
The rooting is even more easy (Stonecold would kill me if he'd read this, lol):
For when running on Linux (no can do on Windows, as Windows doesn't know the ext4 FS):
Since you got the SD in your PC anyways already, just mount partition 2 (e.g. if the SD is sdc on your PC, mount /dev/sdc2).
That is the partition where the Android system is sitting on.
Then just copy over the files needed for root to where they need to go, chown/chmod them properly, unmount and done
I used the "update-supersu.zip" I had for my Nexus7 to grab the required files.
But I'm planning to make a simple rooting script as well.
So if all goes as planned it'll come down to
- insert original SD
- run script 1
- insert new SD
- run script 2
- to root run script 3
brilliant! I would love to see those scripts
way easier than start tinkering with that stuff myself
One thing I wonder about - over at the official forum you said that a simple dd copy didn't work - is that if the target sd-card is bigger or also for an sd-card of equals size? because with equal size simple dd copy of the sd-card should still work, even if some things need so be exactly at the end.
Yup, just a dd didn't work because the new SD card was larger and the bootloader ended up being somewhere in the middle of the card instead of at the end.
While your thought of "dd to equal size cards" is totally correct, it might still fail due to the fact every card is not 100% exact same size counting down to last byte.
There ususally is a tiny size difference (a few bytes to kbytes) between cards, even if they are supposed to be same, so the bootloader might end up truncated or not exactely at the end.
If, however, the size of the cards is 100% the same, down to the last byte, then yes, a simple dd clone would work.
HellcatDroid said:
... There ususally is a tiny size difference (a few bytes to kbytes) between cards, even if they are supposed to be same, so the bootloader might end up truncated or not exactely at the end. ...
Click to expand...
Click to collapse
Oh! Didn't know that. I thought same marketing size means not the same size they write on the box, but at least the same size between those that are marketed with the same GB numbers on their stickers.
OK, here we go, I slapped together a few scripts for prepping a new (and larger) SD card to work in the N1 and while having the SD in the PC to aplly some root.
* hints at attachment of this post
The scripts might still have problems and not work on any Linux out there, but it's a start.
If there's more people interested and joining in on this I might continue but for now I got what I wanted - more storage and root.
Hi
I think I destroyed my MiniSC cand! The N1 is dead. I tried to insert the card in a linux and gparted did not see anything. What can I do?
thank you for your help
somade said:
Hi
I think I destroyed my MiniSC cand! The N1 is dead. I tried to insert the card in a linux and gparted did not see anything. What can I do?
thank you for your help
Click to expand...
Click to collapse
Could you post how you got there? what did you do to the sd-card that destroyed it?
Hi.
If you got a dump from a working state of the SD you can just dd it back onto the card.
If you don't, it can still be recovered but might need bit more work.
Two options:
find someone who gives you a dump of their card and use the write-card script from my above post to write it to your SD.
Problem with this: a working dump contains copyrighted code, like the bootloader, it technically it's "not OK" to share it
we come up with another script that only contains an "empty" image (i.e. only partitioning information) and that takes the bootloader and recovery from the official update and gets the card into a state that it boots into recovery and lets you install a working system using the official update from USB (option in the recovery menu)
Option 2 would be nicer, IMO.
I'll try to make up said script
Thank you for your immediate answer!.
Actually I dont know what has happened, maybe the sharp instrument I used to remove the plastic cover scratch it...But now when I put it in a card reader the led of the reader switch off and the card is heated!!!. And also when I put it in the N1 the blue led turns off!.
So I bought a new empty micro Sd .
Waiting for your script to partition the new card and then boot in recovery mode and install a firmware....
Because I am not expert to linux please give me a lot of details how to do this.
Thanks again!
HellcatDroid said:
we come up with another script that only contains an "empty" image (i.e. only partitioning information) and that takes the bootloader and recovery from the official update and gets the card into a state that it boots into recovery and lets you install a working system using the official update from USB (option in the recovery menu
Click to expand...
Click to collapse
Do you think the bootloader is even part of the offical updates? wouldn't it be "best practice" to leave the bootloader partition alone as long as possible (and normally firmware updates don't need to change the bootloader)
update: something else I've just found, those might be kernel sources for our Tizzbird N1:
http://www.cnx-software.com/2012/07...hips-tcc8925-mini-pcs-cx-01-z900-tizzbird-n1/
-->
https://github.com/cnxsoft/telechips-linux
Yep, the bootloader is in the update - at least in the 3.20 one.
And yes, usually the bootloader shouldn't be touched because that's usually the one thing that can "perma-brick" Android devices.
However, sometimes the manufacturer updates it (fixing bugs, adding functionality) - on my Nexus7 they updated the bootloader on pretty much every update and also Samsung updates their bootloaders every now and then (and every single update flashes the current one).
Last, not least, on the N1 the bootloader isn't on a partition but at unpartitioned space at the very last blocks of the SD (=> reason for a simple dd to a larger card not booting).
Ohyay at the possible kernel sources!
It'd be so cool if that's really sources able to build a kernel for the N1 with - I think we might be able to even get custom recovery (CWM and the likes) on the N1 if those sources work
OK, while trying to recreate a working SD card w/o using a dump of a working one I found out a few more things - some of them still need figuring out if we wanna do it properly.
There seem to be TWO bootloaders!
A stage1 bootloader of ~1kB size located at the third and second last block of the SD. If it's missing the N1 can't boot and it looks like ARM code (haven't tried to disassamble it yet), I assume the bootrom loads and executes that piece of code which in turn parses the header (see below) and load/starts the stage2 bootloader (the one also found in the FW update).
The very last block of the SD is a "header block" with some information beeing parsed either by the bootrom or (more likely) the stage1 bootloader.
The headerblock contains (among numerous other unkown data) the size of the ("stage2") bootloader (the one that then actually loads and boots the Linux kernel of the Android OS, this is also the one contained in the FW update) and the usable size of the SD card! (everything works fine though if the SD size is wrong and a proper FW update updates the header during writing of the bootloader and also sets the correct size).
Also, the headerblock has a checksum of which I have no clue on how it is generated.
All that is just educated guesses and might be totally off, but for now it looks like it's not too far off.
So, for now we can assume the following boot sequence:
Boot-ROM
-> loads stage1 bootloader from fixed position "SDsize - 3 blocks" (1 block = 512bytes)
stage1 bootloader at fixed position on SD
-> checks checksum of headerblock (?), gets size of stage2 bootloader from headerblock, locates stage2 bootloader based on it's size and loads/executes it
stage2 bootloader on variable position on SD
-> base initialisation of hardware
-> checks for recovery trigger (the red button on the remote control) and boots kernel from partition 6 if trigger present
-> boots kernel from partition 1 if recovery was not triggered
-> enters fastboot mode when booting the kernel fails
Kernel
-> loads base drivers and boots up the system
you're brilliant Hellcat!
And did you also find both bootloader stages inside the firmware updates?
Another question that came to my mind while reading your post (fastboot..)
Is there a way to use the Tizzbird as USB-slave? So to make use of adb and fastboot and such stuff? Okey adb could also be used via network I guess..
somade said:
Hi
I think I destroyed my MiniSC cand! The N1 is dead. I tried to insert the card in a linux and gparted did not see anything. What can I do?
thank you for your help
Click to expand...
Click to collapse
Somade, do you have a linux running on your pc? If no, download and get a knoppix running. and then contact me via pm. I have the original n1 image so no problem to recover the n1.
sebastian.heyn said:
Somade, do you have a linux running on your pc? If no, download and get a knoppix running. and then contact me via pm. I have the original n1 image so no problem to recover the n1.
Click to expand...
Click to collapse
Welcome to our rouge and non-censored Tizzbird N1 forum Sebastian!
I wonder if you found us here, if the German Tizzbird support also already knows about us
update: I just remembered, I've sent you the link as PM over in the official forums, thats how you landed here.
Sharing your sd-card image might be a copyright violation, and if you're profile name is strongly linked to you're real identity you should definitly be cautious with such things on public forums...
kaefert said:
And did you also find both bootloader stages inside the firmware updates?
Click to expand...
Click to collapse
Nope, unfortunately the stage1 bootloader is not in the update :-/
kaefert said:
Is there a way to use the Tizzbird as USB-slave? So to make use of adb and fastboot and such stuff? Okey adb could also be used via network I guess..
Click to expand...
Click to collapse
Yeah, it works, even officially XD
Go to the TizzBird settings -> "System Settings" -> "Advanced Settings"
It has an option "OTG Mode" there, set it to "Debug".
If you have your N1 connected to your PC via the micro-USB port (and hence your PC powering the N1!) you can use ADB and fastboot just as usual
I have not yet tried if that option is persistant, i.e. it survives a power loss.
When booting the kernel fails it should fall back to fastboot mode, so flashing a new kernel w/o pulling the SD should be possible - need to test this a bit more, though.
What works is, if you're rooted and and you fire the command "reboot bootloader" from a root shell, that gets you into fastboot mode no matter what (given you applied above mentioned setting first).
But needing a running system to get into fastboot mode kinda defeats the purpose of it - this aint Ouya which is a total fail when it comes to fastboot XD
---------- Post added at 09:26 AM ---------- Previous post was at 09:05 AM ----------
kaefert said:
I wonder if you found us here, if the German Tizzbird support also already knows about us
Click to expand...
Click to collapse
Eventually they will, I'd say.
And I'd love to see their faces when they do XD
Hi guys, I have the Rock Jaw Vi phone which by all sense and purpose seems to be a clone of the HTC One. It's Quad Core with 2 mega pixel camera on the front and 8 mega pixel on the back. The case and all outward appearances are that of the HTC, the phone info screen displays the following ...
Model Number = RJViJGTL32SM
Andoid version 4.2.1
Baseband version = moly.wr8.w1248.md.wg.mp.v6.p8,2013/08/12 15:55
Kernel version 3.4.5 [email protected] #1 Mon Aug 19 16:54:14 CST 2013
Build Number = 0502H026_20130819
I can get into the boot options screen by doing the On/Volume Down press but the menu's are all in Chinese and just seem to go through self diagnostics and tests. I can drag n drop file from Mac OSx but none of the apps I have found so far will communicate with the phone via USB. I am trying to get root so i can do a full back-up and then to try and put HTC Android 4.3 on it.
Do you guys have any idea on how I can achieve this or to get the phone to display it's boot options in English ?
I am pretty much clueless and stuck, any advice, tips, hacks etc would be really appreciated
I did follow a link at one stage on the web that went to SRSroot but their tool was windows only
Hmmm More messing with the phone has revealed power on with volume up depressed gets me to some very small text menu with the options;
Boot Normal
Fastboot
Boot(UART)
Boot UART is all the test screens that I was getting in Chinese but now they are touch screen buttons and labeled in english ao that's good to know.
Using fastboot-mac from HTCRootOne tries to talk to it but comes back with error: could not clear input pipe; result -536854449, is this something that's platform specific, ie it's not a true HTC so the version of fastboot-mac is no good and needing a non specific version ?
Ok that error is generated to the oem get_identifier_token...
If i do a fastboot-mac devices i get the reply "mt6589_phone_720pv2 fastboot" ...
I'm getting there slowly
Done some more digging with the phone attached to the Mac here and checking my systems profile I see that the phone is listed under usb connections as seen in the screen grab, still referring the as a HTC. Getting a new usb cable delivered to see if the phones usb cable provided is for charging only. If anyone here has any other suggestions I would be all ears or eyes as the case might be
Done more grubbing around and have found it to be a HDC One, HTC One clone .... Now to go see if any are rooted on here
Can anyone help me
Well i am pretty much stuck here so if anyone is reading this and wants to offer some help and advice I could do with it
I have looked around on the phone and can't see any bin or system folders even with show hidden i can't find them.
adb wont give me a remote shell, it complains that there is no bin/bash
when i try and do an adb backup i get 0 byte files grrrrr!!
I still need to find a way of getting root
This phone is a tricky beast for a learner - lol
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
gbl08ma said:
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
Click to expand...
Click to collapse
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
tpwuk01 said:
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
Click to expand...
Click to collapse
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
gbl08ma said:
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
Click to expand...
Click to collapse
I already had the phone in usb debug mode. Had to set the phone to use usb as MTP and not mass storage device connection type. Now it allows me to get in to the blighter with adb, fastboot still errors with pipes. That method allows me to get adb shell running and i can get android file transfer .... back to the reading part again
Thanks for the information gbl08ma - if i can find a way to back-up the rom i will share it somewhere
Hmm yummy - lots of interesting things in there .... Forgive my ignorance again please, but if i can create an update.zip file from the shell on the device that compresses all files from \ and all subdirs would that be the same thing as a safe ROM backup ? i wanna be safe before i attempt to root the phone as someone on here has a lower spec version of this phone and says it's a partial brick now.
TpwUK
Rooted
This phone is easily rooted with the motochopper
http://forum.xda-developers.com/showthread.php?p=40747604
Now should I push my luck further and go for the ROM - lol
TpwUK
I believe i own the same mobile
@tpwuk01
I also asked the same here; http://forum.xda-developers.com/showthread.php?t=2180425&page=92
but i was only able to root using frama root app, and it worked like a charm, but thats the only thing i could achieve, dont know but it seems theres no official thread of developement going on for any cloned device, mine runs the MOLY.WR8.W1248.MD.WG.MP.V6.P8 2013/08/12 15:55 Baseband.
After root i just installed some root apps, ads blockers, cant get any recovery to work, (Playing safe actually not to brick this now, since no support yet) but would have appreciated trying out kitkat on it, using antutu to view up specs, its impressive, i got to find out our 13MP camera at the back can do a great job than it currently is we only need to figure out how to change the image compression, the one i stumbled upon online was the blast, the 13MP was great also the flash light was tweaked to be 50X its current brightness, our 1GB application space was increased to 3.5GB, GPS and the rest was also modded to work really great.
Would like to hear any new updates you stumble upon bro.
Still a nice and featured packed device.
None of this is my work and all recognition goes to the awesome developers that made this possible, I will link their guides in here with some minor notes for newbies like me that may had some issues trying to unlock and root the Fire Stick (FS) 4K
DISCLAIMER: BE WARNED THAT YOU HAVE TO OPEN YOUR FIRE STICK AND IT WILL VOID YOUR WARRANTY, THIS IS NOT FOR THE FAINT OF HEART AND NEITHER THE DEVELOPERS OR MYSELF ARE RESPONSIBLE IF YOU BRICK YOUR DEVICE OR VOID YOUR WARRANTY
Ok, now let's begin:
UPDATE: Per Sus_i, this makes perfect sense:
"Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen)."
First very important, I wish I would have known this before but make sure you have a Laptop and a Monitor to Connect the FS to, so basically the USB Power cable from the FS connect it to your laptop and connect the HDMI portion to a monitor or TV
I also strongly recommend to have your FS deregistered before continuing as this will prevent your FS from automatically updating after rooting
In order to unlock the bootloader follow "THIS GUIDE"
I made a quick video on how to open your device and how to Short it using Aluminum Foil:
https://www.youtube.com/watch?v=h4I6ifBLWJ4
Process is pretty self explanitory, make a USB ISO from the image provided on that thread, boot into it and open terminal, make sure you put the file he provides on a RW location, my mistake was that I put it inside a RO folder and it would not load the script, so I mounted the kamakiri-mantis-v1.2.zip unto the /mnt directory of the usb and I was able to run the script successfully, make sure to run the commands quickly as the first time that I it finished the ./bootrom-step.sh script and I left it sitting for 10 minutes to grab a bite, I couldn't run the second script and had to start all over. After the second ./fastboot-step.sh script, your device will be on the TWRP recovery, now on the same terminal page or a new one enter these commands:
Code:
adb devices
adb shell
exit
You should see your device's serial number from the first command with "device" to the right of it and the second command will basically put you inside the device's directory assuming you have established a successful connection. The last command just put you back to your starting point, now open the firefox browser on the FireOS USB and navigate to the URL below
Download the Pre-Rooted Image from "HERE" This image contains Magisk already so you don't have to worry about installing it separately, the image is larger than the available partition on this USB so this is a good time to either get a second USB or if you want to download the file to your local hdd and pull them from there its up to you, then run these commands:
Code:
adb push <your download location you decided earlier here>/mantis-6.2.6.8-rooted_r1.zip / sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.8-rooted_r1.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
This basically installs the pre-rooted image to your device, after the last command, you should see on your monitor the Fire Stick Reboot and boot to the Amazon GUI Splash Screen, now very important if you followed my previous instructions of deregistering your device before performing all these steps, it should bring you up to the Amazon Initial Setup Screen, now what you want to do is do the following commands before continuing on terminal:
Code:
adb devices *you should see something your screen where the FS is connected to, click accept or enter can't remember*
Now it should show you in terminal your serial number and "device" next to it, meaning you can run adb commands in which you will run the following to disable OTA updates:
Code:
adb shell
su *after this command you should see something again on your screen, click the check the box "Always Remember" and click ok" *
if "su" was successful, you should see something like this:
mantis:/ $ su
mantis:/ # *the hash means you're running as root, if you don't have a "#" you are not running as root"
Than continue with these commands and should get the following results:
pm disable com.amazon.tv.forcedotaupdater.v2
***Package com.amazon.tv.forcedotaupdater.v2 new state: disabled***
pm disable com.amazon.device.software.ota
***Package om.amazon.device.software.ota new state: disabled***
pm disable com.amazon.device.software.ota.override
***Package com.amazon.device.software.ota.override new state: disabled***
After running all these commands exit adb and continue with the normal Amazon Setup including adding your amazon account. After you get to the screen where you can see all the apps, open a new web page browser in firefox and download "This Add-On" , this one is less than 200MB so it should fit on the Fire OS USB, so I would download it and copy it to /mnt for ease of access, go back to terminal and type this:
Code:
adb devices
adb push <your download location you decided earlier here>/AFTV-MM-1.7-6.2.6.8.zip/ sdcard/
adb reboot recovery *it will boot into TWRP*
adb shell
twrp install /sdcard/AFTV-MM-1.7-6.2.6.8.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
Your device will reboot and if everything went smoothly, you should have a rooted amazon fire stick 4k, Congrats :good:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Edit: S̵i̵n̵c̵e̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵ ̵c̵a̵n̵'̵t̵ ̵b̵e̵ ̵p̵a̵t̵c̵h̵e̵d̵,̵ ̵i̵t̵'̵s̵ ̵i̵n̵ ̵m̵y̵ ̵o̵p̵i̵n̵i̵o̵n̵ ̵t̵h̵e̵ ̵b̵e̵s̵t̵ ̵t̵o̵ ̵d̵o̵ ̵t̵h̵e̵ ̵s̵e̵t̵u̵p̵ ̵a̵t̵ ̵t̵h̵e̵ ̵b̵e̵g̵i̵n̵n̵i̵n̵g̵,̵ ̵p̵a̵i̵r̵ ̵t̵h̵e̵ ̵r̵e̵m̵o̵t̵e̵,̵ ̵t̵h̵e̵n̵ ̵u̵p̵d̵a̵t̵e̵ ̵t̵o̵ ̵t̵h̵e̵ ̵l̵a̵t̵e̵s̵t̵ ̵o̵v̵e̵r̵ ̵f̵i̵r̵e̵O̵S̵.̵ ̵T̵h̵a̵t̵ ̵w̵a̵y̵ ̵y̵o̵u̵ ̵a̵v̵o̵i̵d̵ ̵a̵ ̵p̵e̵n̵d̵i̵n̵g̵ ̵u̵p̵d̵a̵t̵e̵ ̵n̵a̵g̵ ̵s̵e̵t̵u̵p̵ ̵s̵c̵r̵e̵e̵n̵ ̵a̵f̵t̵e̵r̵ ̵d̵o̵i̵n̵g̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵.̵ ̵T̵h̵e̵n̵ ̵e̵n̵a̵b̵l̵e̵ ̵A̵D̵B̵ ̵a̵n̵d̵ ̵u̵n̵k̵n̵o̵w̵n̵ ̵s̵o̵u̵r̵c̵e̵s̵.̵ ̵ After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Edit: Update: meanwhile, the fix for the mentioned 'contact manufacturer' error is known...
Take a look here and here.
Edit/Update: Due to efuses (blocking the bootrom access), it isn't recommended to do any update infront of the unlock...
Sus_i said:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Click to expand...
Click to collapse
Ops Typo let me edit it, I meant to put 6.2.6.8 on the command lol, and aaaa I see I didn't know the exploit couldn't be patched great info, so than yes I will revise my instructions thank so much
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
nandroidint said:
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
Click to expand...
Click to collapse
No. If I remember correct, it has something to do with flashing, i.e. the vendor partition wasn't flashed propperly.
Maybe you flashed not the prerooted!? With the Kamakiri TWRP version is flashing full ota update packages (renamed to zip) also possible... and in the prerooted thread is such a full 6.2.6.8 ota linked.
Edit: Could be that this error is prime video related, idk. rbox said he looks into it soon...
Just for clarification: The prerooted rom is a perfect thing since years.
My suggestion 'avoid any rom flashing' from my last post is just an attempt to keep it simple for beginners.
By the way, if the stick gets all updates in front of the unlock, it makes no sense to update it after the unlock again (unless addon.d support is needed).
I hope that has become clear I very much appreciate all the prerooted stuff
thanx for the tut nandroidint this is exactly what I needed, I wasn't sure how to do the shorting so the video helped out a lot now I'm ready to do this. But I'm sorta a noob when it comes to android so I got few questions tho, 1) what are the main benefits in rooting the fIrestick 4K 2) are there different roms to install? 3) are there root only .apks? 4)also one main thing I would like to be able to do is spoofing the Mac address any idea if that's possible?
5)Oh and lastly what OTB cable do you recommend? sorry for all the questions ?
'std::bad_alloc'
After running the adb push of the manthis.zip Im getting terminate called after throwing an instance of 'std::bad_alloc'.... What Im I doing wrong?
i gave root can i remove amazon services
i dont want google launcher jsut remove services
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable ?
Can I please get some support guys ? previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
davinci2798 said:
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
Click to expand...
Click to collapse
Did you deregister before rooting like the tut says? This is why I’ve been hesitant on rooting because of the lack of support on this forum
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
tsynik said:
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
Click to expand...
Click to collapse
Nice! That’s awesome thanx for the info and reply.
davinci2798 said:
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
Click to expand...
Click to collapse
Hey so have you figured out what was the problem yet? If so could u explain how you managed to fix it? I’m going to root sometime this week and would hate to run into this issue.
USB drive for storage
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
Yes, You can use a USB drive for App loading and Movie storage.
See Troypoint.com for good video.
I suggest a single USB OTG Cable and a USB HUB for your drive.
Then you can add a Keyboard and Mouse which make it MUCH easier to type commands.
Good Luck
How might one do this on a Mac?
Thanks
gogorman said:
How might one do this on a Mac?
Thanks
Click to expand...
Click to collapse
Do what? The only thing u can do on the MacOS is to create the bootable iso usb, you can follow these steps to do so https://www.google.com/amp/s/www.le...-on-an-apple-mac-os-x-from-an-iso?hs_amp=true
After your create the bootable usb just reboot and hold down option and select the bootable usb, once in open up Firefox and download the kamakiri-mantis-v1 and open a terminal window and change the directory to where u have the kamakiri folder, in terminal type cd then just drop in the kamakiri and hit enter. From there u can just follow the tut, FYI the bootable usb you create is a Linux OS so that’s how you can do it on a Mac, you just can’t do the rooting on MacOS, just clarifying Incase that was your question.
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Step by step instructions would be great?
chinkster said:
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
RPM99 said:
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
Click to expand...
Click to collapse
The link he provided explains all that https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459 all except for when to connect to the tv, but I assume it’s after running the kamakiri script, btw it’s not software, you just download the kamakiri mantis while in the Linux usb os, open a terminal and change the directory of the terminal to the kamakiri folder in order to run the ./bootrom-step.sh and ./fastboot-step.sh commands
Edit: just follow the main guide from the link above then read this guide after, that’s the best way to understand it.