Related
Let's say I root my phone and install one of those 2.2 or 2.3 roms ,would I have multi touch ?
Sorry for the noob question ,but I just couldn't find the answer.
couldn't find answer? here are min. 5 threads about it.. someone say no someone yes.. i think no
removed...
You can NOT get MT lol. Unless you crack bootloader.
haha, i love all this threds about MT its impossible guys to day when someone crack that bootloader - i dont think im going to live that long
kakawo said:
haha, i love all this threds about MT its impossible guys to day when someone crack that bootloader - i dont think im going to live that long
Click to expand...
Click to collapse
sorry for my english.I used google translate.
You can do multitouch driver as a module. This
kernel module to be unloaded from memory the old driver and load a new one. one person did it for the ebook.
can somebody help to make it to our phone.
links to the Web in a text file
andrej456 said:
sorry for my english.I used google translate.
You can do multitouch driver as a module. This
kernel module to be unloaded from memory the old driver and load a new one. one person did it for the ebook.
can somebody help to make it to our phone.
links to the Web in a text file
Click to expand...
Click to collapse
Did Any1 tried this ? My X8 is not rooted yet
This is done for other device. need to do on xperia x8.
need someone who knows well the programming language c.
yep, it has been told that this is for the devices with the 1.5 firmware and it's not working on X8
Sully.E said:
yep, it has been told that this is for the devices with the 1.5 firmware and it's not working on X8
Click to expand...
Click to collapse
sorry for my english.I used google translate.
You can compile the kernel and modules. According to this guide
http://forum.xda-developers.com/showthread.php?t=977146
only after "make clean" needs to be done "make semc_shakira_defconfig"
then "make menuconfig" and "make" or "make modules"
config file is located in /kernel\arch\arm\configs\semc_shakira_defconfig
driver is in \kernel\drivers\input\touchscreen\
synaptics_i2c_rmi.c or synaptics_i2c_rmi4.c
need to change it, add a function unload the old driver
http://translate.google.com/transla...rver.net/2010/11/blog-post.html&client=ubuntu
and change the driver under multitouch. as did the man on the G1
http://lukehutch.wordpress.com/android-stuff/
compile the kernel and modules
copy the module to your phone in /system/lib/modules/
then run the module with the command in the console "insmod"
http://linux.about.com/od/commands/l/blcmdl8_insmod.htm
only need someone who knows well the programming language c and make it to our phone.
add an example of drivers from G1
@andrej456:
It's not clear, do we have to make ONLY kernel module in /system or we have to replace driver in kernel itself too?
blagus said:
@andrej456:
It's not clear, do we have to make ONLY kernel module in /system or we have to replace driver in kernel itself too?
Click to expand...
Click to collapse
we must replace the driver in the kernel
driver is loaded into memory at boot
Here is the text of the "dmesg"
Code:
<6>[ 2.194121] msm72k_udc: reset controller
<6>[ 2.198791] synaptics_load_rmi4_func_regs: Func:f11_2D Query_Base:0x80 Cmd_Base:0x5f Ctrl_Base:0x26 Data_Base:0x18
<6>[ 2.208818] synaptics_load_rmi4_func_regs: Func:f08_BIST Query_Base:0x7e Cmd_Base:0x5e Ctrl_Base:0x20 Data_Base:0x15
<6>[ 2.219328] synaptics_load_rmi4_func_regs: Func:f01_RMI Query_Base:0x69 Cmd_Base:0x5d Ctrl_Base:0x1e Data_Base:0x13
<6>[ 2.230314] usb: notify offline
<6>[ 2.235506] msm72k_udc: suspend
<6>[ 2.331561] synaptics_ts_probe: nbr_panels:1 nbr_fingers:1 data_size:5
<6>[ 2.332454] synaptics_ts_probe: fw_rev:2 max_x:1689 max_y:2534
<6>[ 2.338291] synaptics_ts_probe: max_x 1689, max_y 2534
<6>[ 2.343406] synaptics_ts_probe: inactive_x 0 0, inactive_y 0 0
<6>[ 2.349209] synaptics_ts_probe: snap_x 0-0 0-0, snap_y 0-0 0-0
<6>[ 2.355471] input: synaptics-rmi-touchscreen as /devices/virtual/input/input0
<6>[ 2.362759] synaptics_ts_probe: Start touchscreen synaptics-rmi-touchscreen in interrupt mode
<3>[ 2.370899] cyttsp_init: Failed to request GPIO 112
<3>[ 2.375508] cyttsp_core_init: platform init failed!
<4>[ 2.380506] cyttsp-i2c: probe of 0-0024 failed with error -12
<6>[ 2.386329] cyttsp_i2c_init: Cypress TrueTouch® Standard Product I2C Touchscreen Driver (Built Jan 18 2011 @ 23:43:30) returned 0
<6>[ 2.398618] SEMC GPIO Matrix Keypad Driver: Start keypad matrix for shakira_keypad in interrupt mode
<6>[ 2.407599] input: shakira_keypad as /devices/virtual/input/input1
<6>[ 2.413983] msm72k_udc: reset
<6>[ 2.416269] msm72k_udc: portchange USB_SPEED_HIGH
need to do to when downloading our driver, old driver was unloaded from memory
need to initialize the new driver, find the old driver and unloaded from memory
about to do so
find the old driver
Code:
struct device_driver * other;
other = driver_find (SYNAPTICS_I2C_RMI_NAME, & i2c_bus_type); other = driver_find(SYNAPTICS_I2C_RMI_NAME, &i2c_bus_type);
if (other) if (other)
{ {
printk ("Previous driver found:% s \ n", other-> name); printk( "Previous driver found: %s\n" , other->name);
return-ENOMEM; return -ENOMEM;
} }
unload old driver from memory
Code:
struct i2c_driver * otherDriver;
struct device_driver * other; struct device_driver * other;
other = driver_find (SYNAPTICS_I2C_RMI_NAME, & i2c_bus_type); other = driver_find(SYNAPTICS_I2C_RMI_NAME, &i2c_bus_type);
if (other) if (other)
{ {
otherDriver = to_i2c_driver (other); otherDriver = to_i2c_driver(other);
printk (KERN_ERR "Previous driver found:% s, addr 0x% x, owner% x \ n", other-> name, (int) otherDriver, (int) other-> owner); printk(KERN_ERR "Previous driver found: %s, addr 0x%x, owner %x\n" , other->name, ( int )otherDriver, ( int )other->owner);
i2c_del_driver (otherDriver); i2c_del_driver(otherDriver);
} }
I found the source code of the ebook
I found it here
xttp://nookdevs.com/Talk:Multitouch
xttp://runserver.net/temp/synaptics_i2c_rmi.c
it does not work for our phone. will use it as an example
But there is still the problem of accessing kernel and replacing driver... I'll see what I can do, although
manutdsnake said:
You can NOT get MT lol. Unless you crack bootloader.
Click to expand...
Click to collapse
I think bootloader is cracked, check bin4ry's flasher, modify the kernel.sin with multitouch drivers, then, flash it(with bin4ry's flasher) and there you go
not yet =S
But lets pray for the developers =D
bogdan_mihai554 said:
I think bootloader is cracked, check bin4ry's flasher, modify the kernel.sin with multitouch drivers, then, flash it(with bin4ry's flasher) and there you go
Click to expand...
Click to collapse
NO, it's NOT, it's kernel from OFFICIAL Japanese update...
mukambc said:
not yet =S
But lets pray for the developers =D
Click to expand...
Click to collapse
Yeah, but can't the kernel(.sin file) be modded and then flashed??(I once flashed an X10 kernel on the x8...won't boot but hey, it flashed ), now i got Gingerbread on my x8 :>:> And i'm waiting for a M.T Kernel...So, if the bootloader's not cracked, how is it that you can flash kernels with Bin4ary's flasher?? So, just modd the .sin file(put Mt. driver) and you're done ^_^
Is Synaptics T1021A hardware capable of multitouch? It will be great if somebody will add this function for us thanx
really interesting on all about MT.
should this be stickied? so we can persuade the developer to do this..
Has anybody tried one of the USB 2 Ethernet dongles on the A500 yet? I am interested but there is no reason to fork out the money if it doesn't work.
Please let me know.
Thank you
With the correct module, this one works fine:
http://www.amazon.com/gp/product/B00484IEJS/ref=oh_o02_s00_i00_details
Module for that is (asix.ko) in my post below, if you are using stock kernel:
http://forum.xda-developers.com/showthread.php?t=1297620
fincan said:
With the correct module, this one works fine:
http://www.amazon.com/gp/product/B00484IEJS/ref=oh_o02_s00_i00_details
Module for that is (asix.ko) in my post below, if you are using stock kernel:
http://forum.xda-developers.com/showthread.php?t=1297620
Click to expand...
Click to collapse
Hi,
A little more help please....
I have the recommended usb network interface, running 3.2 w/root, copied over and loaded your asix.ko and did a successful insmod on it. The device seems live (power light and link light are active).
What do I need to do to start the network connection on the A500?
Thanks!
Hi,
this might help you from the transformer forum
http://forum.xda-developers.com/showthread.php?t=1274656
http://forum.xda-developers.com/showthread.php?p=16782015
/mm
monki-magic said:
Hi,
this might help you from the transformer forum
http://forum.xda-developers.com/showthread.php?t=1274656
http://forum.xda-developers.com/showthread.php?p=16782015
/mm
Click to expand...
Click to collapse
Thanks!
I ended up using these instructions from the thread:
Copy the asix.ko to '/system/lib/modules/'
After that I created two scripts using Script Manager
First one to load the module:
insmod /system/lib/modules/asix.ko
Then a second to startup the network (dhcp and hardcoding DNS to google DNS servers):
dhcpcd eth0
setprop net.dns1 8.8.8.8
setprop net.dns2 8.8.4.4
Thank you fincan for the reply... I tried loading the module and it failed with this in the dmesg:
<3>[ 1523.187808] asix: version magic '2.6.36.3+ SMP preempt mod_unload ARMv7 ' should be '2.6.36.3HoneyVillain-3.7+ SMP preempt mod_unload ARMv7 '
Obviously I am running HoneyVillain and was just giving it a stab to see if it would work.
Think you can work some magic for me on this?
Many thanks again.
h0mewreck3r said:
Thank you fincan for the reply... I tried loading the module and it failed with this in the dmesg:
<3>[ 1523.187808] asix: version magic '2.6.36.3+ SMP preempt mod_unload ARMv7 ' should be '2.6.36.3HoneyVillain-3.7+ SMP preempt mod_unload ARMv7 '
Obviously I am running HoneyVillain and was just giving it a stab to see if it would work.
Think you can work some magic for me on this?
Many thanks again.
Click to expand...
Click to collapse
Give the attached one a shot and let me know if it works, I have simply changed the kernel version name to HoneyVillain, it should work just fine unless there is a change in the kernel source code on the Honey Villain rom, which I doubt.
Here is the new error:
<4>[14850.069881] asix: Unknown symbol __aeabi_unwind_cpp_pr0 (err 0)
<4>[14850.074998] asix: Unknown symbol __aeabi_unwind_cpp_pr1 (err 0)
Looks like it is getting more involved.
If you have the time, it would be helpful but if not, I understand.
Have any of you got the Ubuntu 13.04 (raring ringtail) daily builds for the N7 grouper to successfully boot?
I tried the recent 20130421 and 20130420.2 builds - the kernel boots successfully but only stays alive for about 7 seconds. (I was able to observe a little bit of /proc/last_kmsg by quickly booting to a custom recovery after the failed boot).
Don't know if it makes any difference or not, but I installed by flashing the system .zip file
raring-preinstalled-armel+grouper.zip
and manually installing the boot image (raring-preinstalled-boot-armel+grouper.img) using "dd" to the LNX partition (via TWRP's command-line UI).
Yes, I did both a factory reset and a wipe of /system in TWRP prior to flashing. (Even checked the health of /data, /system, and /cache using "e2fsck" after flashing - no problems there, either).
I suppose I could try the quantal quetzal (12.04) daily builds next. Just thought I would ask though.
I did successfully flash an Ubuntu Touch Preview build through ClockworkMod Recovery. To be honest, it wasn't worth it. It's a nice little demo of the basics of the UI, but almost every app was just a placeholder image. There's nothing about it you can't pick up from watching a video of it. Restored backup to Android in ~20 minutes.
Sent from my Nexus 7 using xda app-developers app
Thanks. Yeah, I looked at a video review that gave me the same impression. That's why I tried the 13.04 nightly - iirc, the demo released mid-February was based on quantal (12.04) - I was sort of curious as to whether there was new progress in the last month. Never thought it would become a daily driver, though.
Also, it looks like the builds I referenced are something different - substantially smaller than the "desktop" release of the original ubuntu touch demo for the Nexus 7.
Probably if I spend a little more time with it, I can figure things out. (I thought maybe that these builds needed a multi-boot (kexec) loader or something.)
Kind of strange - one of the boots that I was able to recover a legible /proc/last_kmsg from seemed to be complaining that it wanted to reboot because of the USB cable state. That seems rather odd, but the boot crash was also happening from a disconnected state as well. The thing is, 7-8 seconds is pretty late in the boot process (most of the kernel drivers have initialized) - in fact, there were files with new timestamps in the /data partition suggesting some userland activity had already started up before the kernel decided it wanted to restart.
tail end of /proc/last_kmsg:
Code:
[ 7.628940] kernel_power_off: go to charger mode!
[ 7.629505] max77663-rtc max77663-rtc.0: rtc_shutdown: clean alarm
[ 7.656123] cable_detection_work_handler(): vbus_active = 0 and is_active = 1
[ 7.656235] The USB cable is connected
[ 7.656299] elan-ktf3k 1-0010: Update power source to 1
[ 7.658498] bq27541_shutdown +
[ 7.658560] bq27541_shutdown -
[ 7.659787] smb347_shutdown+
[ 7.661882] smb347_shutdown-
[ 7.662052] Restarting system with command 'chrager-mode'.
[ 7.662114]
[ 7.662174] Restarting Linux version 3.1.10-g06b7e9c ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP PREEMPT Sun Apr 21 08:23:03 UTC 2013
[ 7.662183]
32 Corrected bytes, 0 unrecoverable blocks
Hello everybody out there.
I am trying to add support for the AR9271 USB WiFi device in the CM11 release kernel on my i9507. I've managed to compile the kernel with ath9k and mac80211 (dependency) baked in instead of as modules. I believe this would skip the need to load and unload modules to get the card working. I booted successfully and plugged in my adapter with an OTG cable, but upon ifconfiging and whatnot, I could not find the adapter at all. I tried using Pcap Capture by Kismet, and that reported no connected USB NICs.
I'm losing sleep . What am I doing wrong? Does anybody have an idea? I can release my build of kernel with ath9k support if anyone wants it, although I guess anyone who answers this probably doesn't need it anyway ._.
Thanks guys.
EDIT:
Apparently Kismet Pcap only works with that one Realtek chipset in the Alfa, so that's out the window.
Anyway, I have installed the firmware file (htc_9271.fw) to /system/etc/firmware and the device shows up with lsusb with ID 13d3:3327, so it's being recognized, but the kernel still takes one look at it, laughs, and dies.
Here is the dmesg output:
<6>[14516.472685] usb 2-1: New USB device found, idVendor=13d3, idProduct=3327
<6>[14516.472716] usb 2-1: New USB device strings: Mfr=16, Product=32, SerialNumber=48
<6>[14516.472747] usb 2-1: Product: UB93
<6>[14516.472747] usb 2-1: Manufacturer: ATHEROS
<6>[14516.472777] usb 2-1: SerialNumber: 12345
It seems like the kernel just derps and doesn't load the ath9k_htc stuff it's supposed to. I do remember that when I compiled the kernel, I got errors compiling the ath9k modules. I found no patches for this problem, so I took the ath folder from the linux kernel backports (compat-wireless) and plopped it in the CM kernel drivers folder, replacing the old one. Worst way to merge code, I know. The kernel compiles fine, but according to dmesg, the drivers either aren't there, or aren't doing anything.
There is an updated thread now for rooting the AFTV2 that supports both 5.0.3.1 and 5.0.4 and maybe others in the future, see http://forum.xda-developers.com/fire-tv/general/root-amazon-fire-tv-2-updated-t3277556. The new method is simpler than this method and requires less to download and less steps to run.
To be safe run checkver.py every time you handshake since 5.0.4 is starting to roll out! Checkout the 5.0.3.1 tag in order to use this older method.
If you were able to root your AFTV2 we'd appropriate if you report your success on the poll located here.
NOTE: Root was obtained a few weeks ago so... this procedure is not the most time efficient, but it is just a few simple steps that anyone with a technical background can follow. There are ideas and some work in progress to make it easier. It depends also on serial port stability, which is somewhat random luck. Linux experience will be beneficial. The usual disclaimers apply, which means this rooting procedure comes with some risks and the scripts involved haven't been tested in all environments. Any harm that may come from rooting your device using this procedure is at your own risk and I assume no responsibility for any damage it may cause. I will do my best to help you get through it and recover if possible.
Root the Device
It's taken quite a bit of effort, but I've finally managed to create a pre-rooted system image (as well as backup the original) and provide a semi-efficient way to flash the rooted system image. Before attempting any of the steps listed below YOU MUST BE RUNNING 5.0.3.1. You should also have a unmodified/pristine system partition. You would probably know if you had any modifications and at this point that would be uncommon. If the patching fails for some reason just power off the device, reboot your computer (resets the serial port buffer), start the handshake script, then turn on the device. Once the handshake completes run the patching command again. There is no harm running the patching command two or more times. If it keeps hanging try a different computer.
To get started you will need a system that meets the following requirements:
Linux (Mac OS X or Windows w/ changes)
Python 3.x
PySerial
sudo yum install python3-pyserial # Fedora or RedHat
sudo apt-get install python3-serial # Ubuntu or Debian
USB Male A to Male A cable
R/W access to /dev/ttyACM0 (or use sudo)
ADB USB access (optional, but helpful)
Stop ModemManager (if you have it setup, which blocks handshaking)
Now run the following sequence of commands:
Code:
git clone --branch 5.0.3.1 https://gitlab.com/zeroepoch/aftv2-tools.git
cd aftv2-tools
wget http://download.zeroepoch.com/aftv2/5.0.3.1/system.root.img.gz
wget http://download.zeroepoch.com/aftv2/5.0.3.1/system.diff.gz
gunzip system.root.img.gz
gunzip system.diff.gz
adb reboot ; ./handshake.py # or restart but run ./handshake.py first
./checkver.py # STOP if it reports NO!
./patch_mmc.hs 0x00000000058e0000 system.root.img system.diff # takes ~2 hours
# last address is 0x50dce600
For Macs (see post #115, thanks @ians325) to satisfy the requirements above you will need to install python 3.5.0 for Mac OS X from python.org then run "sudo pip3 install pyserial" to install pyserial. Instead of "wget $URL" use "curl -O $URL".
Windows is working now, but it's constantly improving to make it easier for novice users. The bash script has been ported to a batch file (no cygwin needed) and the serial port has some auto-detection built in now. The files needed for Windows have already been added to the repo but the README is constantly evolving. @ImCoKeMaN (big thanks) and myself are working to improve the process and make it easier for Windows users.
Anyone interested in rooting using an Ubuntu VM should watch the YouTube video by @ultimate_spy_binns, https://www.youtube.com/watch?v=CZQqLoO6ojM. There is also a script to help automate the process if you are doing this on an Ubuntu live CD/USB found here (by @BagiMT).
To test that root is working you should first connect to adb shell and then run the command "su". You will need to accept a prompt on the screen (HDMI port) at least once. The shell should change from a dollar-sign ($) prompt to a hash (#) prompt.
If you would like to disable updates after rooting you can use the following commands:
Code:
adb shell
su
pm disable com.amazon.device.software.ota
To go back to stock in case you want to update or for whatever other reason:
Code:
wget http://download.zeroepoch.com/aftv2/5.0.3.1/system.orig.img.gz
gunzip system.orig.img.gz
adb push system.orig.img /data/local/tmp
adb shell
su
pm enable com.amazon.device.software.ota
dd if=/data/local/tmp/system.orig.img of=/dev/block/platform/mtk-msdc.0/by-name/system bs=1m
sync
reboot
I don't always have the best luck transferring large files over ADB so another option is to copy the uncompressed image file to a microSD card and changing the path to /storage/sdcard1/system.orig.img. Be extremely careful that you have the right path, that the file you are reading exists, and that the file is around 1.2 GB in size. Otherwise you may potentially trash your system.
Background Info
This root method works by rebooting the device and halting the boot process at the MediaTek preloader. Once halted at the preloader we can use the preloader binary API to send a series of MMC commands to the flash chip which allows 512 byte blocks to be read and written using a simple FIFO. Since we have both the original and modified system images we can generate a list of blocks that are different between the two images and only patch those blocks. This means we need to write less than 10 MB instead of 1.2 GB. If we had to send the entire system image at the speeds the preloader is limited to it would take about 2 weeks. If for some reason the system partition becomes unbootable that would be your only option to recover right now. By sending just the differences the patching only takes about 2 hours. There are ways to speed this up (about 5-10 minutes instead), but you'd need to obtain limited root access first using a much much more complicated procedure. I choose to provide instead a slower but much simpler series of commands.
The MT preloader is a process that runs before the regular bootloader (lk/fastboot) and of course before the kernel boots. It only shows up for about 3 seconds. Unfortunately the preloader is writable and could potentially be updated. The entire boot chain is cryptographically signed from what I've been able to inspect including the preloader. An unlocked bootloader would most likely be needed to flash a custom kernel (no kexec built-in of course, but modules/device drivers can be loaded) and create ROMs not based on stock. @rbox has been working on getting kexec working as a module but no ETA yet. So in conclusion the tools here allow you to modify the flash contents and using these facilities we have add SuperSU binaries to the system partition.
Anyone interested in how root was obtained should look at the history starting with this post. You should also read the README file from the aftv2-tools git repo. Also feel free to PM me if you have any questions.
Tips
If you want to disable the pop-up message when becoming root you can change notify=1 to notify=0 in /data/data/eu.chainfire.supersu/files/supersu.cfg. You need to reboot the device after making this change. It's also suggested to make the file read-only because it seems to get reset sometimes. (Thanks @ultimate_spy_binns)
Special Thanks
@qwertytical
@budokaiboy
great news
i never powered on my unit - awaiting root
can we have a 5.0.3.1 image to safely flash before root
otherwise the system might update to different version
now that rooting is out
amazon might be quick ...
reiteravi said:
great news
i never powered on my unit - awaiting root
can we have a 5.0.3.1 image to safely flash before root
otherwise the system might update to different version
now that rooting is out
amazon might be quick ...
Click to expand...
Click to collapse
Yeah, mine pre-ordered one is still in a box so I'd need to update it too. I guess I can do that tonight before a new version comes out.
reiteravi said:
great news
i never powered on my unit - awaiting root
can we have a 5.0.3.1 image to safely flash before root
otherwise the system might update to different version
now that rooting is out
amazon might be quick ...
Click to expand...
Click to collapse
Unfortunately you will need to do a normal update first before patching the system partition. It just takes too long to flash a full system image, original or modified, using the methods we have available to us now. Also the boot partition and other partitions are updated with each OTA. I hope we can continue to provide rooted versions of updated system images, but as you know there is no guarantee of that. I'd update now before there is any new updates and then root it. We could in theory root the older versions as well and even before first boot, but without the OTA updates and applying them in reverse I can't go back and patch the older releases. I strongly think the method used to write the system partition can not be fixed since I believe the preloader code is in a ROM.
Mac Update
A few notes for Mac users willing to experiment a little:
I installed python 3.5.0 for Mac OS X from python.org and then ran "sudo pip3 install pyserial" to install pyserial for python 3.x. The final change I needed to make was to change PORT in handshake.py and read_mmc.py/write_mmc.py (only tested reading the boot partition, but everything else should work). In my case the PORT was /dev/cu.usbmodem1430. The device filename seems to be based on the USB port it's connected to. I'm not sure if there is an easier way to find the device filename besides scanning /dev and looking for new devices matching a given pattern. Maybe others on this forum have some better ideas. The final caveat was I need to unplug and replug the USB cable after the handshake completed otherwise the read_mmc.py script would hang on the first read.
I succeeded in rooting mine! For comparison purposes, here's the md5sums of my partitions:
Code:
0e450c032ddce170667ba3ddc26cb960 DKB
a3ad800f012a153953b403ef1fa36e14 EXPDB
d693da95eb68b40e4315333bcf74918b KB
50f24ce4c7ac388b33310bff6f79636a LOGO
59071590099d21dd439896592338bf95 MISC
f9b5ef697fde92c42bbbec35e5a6cad4 PRO_INFO
8a9d058f87711c2e8ccc698647f5026b TEE1
eda2733e1d0214873d9cb9d78c68425f TEE2
97a2ccdb7a02838b26b9a57e4f31d51d boot
fbd20aa58cd63c07392080cad7627e18 lk
74f0bac463bae8141acf20594987a559 recovery
a06c3d6a8c73923ed5c38b479c4410d3 system
So my DKB, KB, and system partitions are different from yours.
NaturalBornHaxor said:
I succeeded in rooting mine! For comparison purposes, here's the md5sums of my partitions:
Code:
0e450c032ddce170667ba3ddc26cb960 DKB
a3ad800f012a153953b403ef1fa36e14 EXPDB
d693da95eb68b40e4315333bcf74918b KB
50f24ce4c7ac388b33310bff6f79636a LOGO
59071590099d21dd439896592338bf95 MISC
f9b5ef697fde92c42bbbec35e5a6cad4 PRO_INFO
8a9d058f87711c2e8ccc698647f5026b TEE1
eda2733e1d0214873d9cb9d78c68425f TEE2
97a2ccdb7a02838b26b9a57e4f31d51d boot
fbd20aa58cd63c07392080cad7627e18 lk
74f0bac463bae8141acf20594987a559 recovery
a06c3d6a8c73923ed5c38b479c4410d3 system
So my DKB, KB, and system partitions are different from yours.
Click to expand...
Click to collapse
That is awesome news! The first confirmed case I've heard of someone else repeating my success
About the DKB and KB partitions being different it makes me wonder what those partitions are for? I didn't include cache and userdata in the MD5SUM of course, which you noticed, because those change all the time. NVRAM when I looked inside appeared to have a few things that looked to be device specific. The system partition being different is actually expected because I found every time I rebooted my system partition changed checksums. Also that is the MD5SUM of the unmodified system partition. I noticed this weird MD5SUM behavior when I was first gaining root and doing some sanity checks. It happens right after daemonsu is started. My best guess is that the SuperSU tools mount the system r/w quickly and that causes the last mounted timestamp to change. Don't know for sure what causes it, but don't worry that's not unexpected. The main reason I kept those hashes in the repo was so when the next version comes out I know which partitions were changed and need to be updated by users who wish to maintain root.
------------------SOLVED-----------------
Please read on if you have problems with handshake script looping forever...
-----------------------------------------------
Hi zeroepoch,
meanwhile I received my Fire TV 2 and tried your scripts but unfortunately without success.
As far as I can see, there are 2 problems:
- The /dev/ttyACM0 device appears on rebooting the Fire TV, but only for some 100th of a second, then it disconnects again.
- If I give it another try, the device will appear as /dev/ttyACM1, next time /dev/ttyACM2, aso.. So I either have to update the handshake script for every try or reboot my computer (then it starts with /dev/ttyACM0 again).
When I first tried it, the handshake-script ran forever, it just missed the short time of availability of /dev/ttyACM0. So I reduced the sleep-timeout in the script from 0.25 to 0.001. Now the handshake script detects the serial device but runs into an I/O Error during one of the next steps (each time different, seems to be a "race condition").
Can you offer any advice? Could my Laptop be too slow somehow or is there some trick to make the Fire TV keep the port open for a longer time?
Greetings, Christian
Code:
shell:
[email protected]:~/aftv2-tools# adb reboot ; ./handshake.py
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Traceback (most recent call last):
File "./handshake.py", line 17, in <module>
dev = serial.Serial(PORT, BAUD)
File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 261, in __init__
self.open()
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 282, in open
self._reconfigurePort()
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 413, in _reconfigurePor t
termios.tcsetattr(self.fd, TERMIOS.TCSANOW, [iflag, oflag, cflag, lflag, ispeed, ospeed , cc])
termios.error: (5, 'Input/output error')
Code:
/var/log/syslog;
Nov 11 11:25:41 DeepThought systemd[1111]: Reached target Default.
Nov 11 11:25:41 DeepThought systemd[1111]: Startup finished in 15ms.
Nov 11 11:27:28 DeepThought kernel: [ 217.460463] usb 8-2: USB disconnect, device number 2
Nov 11 11:27:31 DeepThought kernel: [ 220.608049] usb 8-2: new high-speed USB device number 3 using ehci-pci
Nov 11 11:27:31 DeepThought kernel: [ 220.741857] usb 8-2: New USB device found, idVendor=0e8d, idProduct=2000
Nov 11 11:27:31 DeepThought kernel: [ 220.741860] usb 8-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Nov 11 11:27:31 DeepThought kernel: [ 220.741862] usb 8-2: Product: MT65xx Preloader
Nov 11 11:27:31 DeepThought kernel: [ 220.741864] usb 8-2: Manufacturer: MediaTek
Nov 11 11:27:31 DeepThought mtp-probe: checking bus 8, device 3: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-2"
Nov 11 11:27:31 DeepThought mtp-probe: bus: 8, device: 3 was not an MTP device
Nov 11 11:27:31 DeepThought kernel: [ 220.855737] cdc_acm 8-2:1.1: ttyACM0: USB ACM device
Nov 11 11:27:31 DeepThought kernel: [ 220.884047] usbcore: registered new interface driver cdc_acm
Nov 11 11:27:31 DeepThought kernel: [ 220.884050] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
Nov 11 11:27:31 DeepThought kernel: [ 220.924931] usb 8-2: USB disconnect, device number 3
Nov 11 11:27:31 DeepThought ModemManager[511]: <warn> (ttyACM0): tcgetattr() error: 5
Nov 11 11:27:31 DeepThought ModemManager[511]: <warn> (ttyACM0): port attributes not fully set
Nov 11 11:27:31 DeepThought kernel: [ 220.928861] cdc_acm 8-2:1.1: failed to set dtr/rts
Nov 11 11:27:31 DeepThought ModemManager[511]: <info> (tty/ttyACM0): released by modem /sys/devices/pci0000:00/0000:00:1d.7/usb8/8-2
Nov 11 11:27:31 DeepThought ModemManager[511]: <warn> (Plugin Manager) (Cinterion) [ttyACM0] error when checking support: '(Cinterion) Missing port probe for port (tty/ttyACM0)'
Nov 11 11:27:31 DeepThought ModemManager[511]: <warn> (Plugin Manager) (Nokia) [ttyACM0] error when checking support: '(Nokia) Missing port probe for port (tty/ttyACM0)'
Nov 11 11:27:31 DeepThought ModemManager[511]: <warn> (Plugin Manager) (Iridium) [ttyACM0] error when checking support: '(Iridium) Missing port probe for port (tty/ttyACM0)'
Nov 11 11:27:31 DeepThought ModemManager[511]: <warn> (Plugin Manager) (Generic) [ttyACM0] error when checking support: '(Generic) Missing port probe for port (tty/ttyACM0)'
Nov 11 11:27:33 DeepThought ModemManager[511]: <warn> Couldn't find support for device at '/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-2': not supported by any plugin
Nov 11 11:27:35 DeepThought wpa_supplicant[837]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Nov 11 11:27:36 DeepThought kernel: [ 226.092142] usb 8-2: new high-speed USB device number 4 using ehci-pci
Nov 11 11:27:37 DeepThought kernel: [ 226.225936] usb 8-2: New USB device found, idVendor=1949, idProduct=0241
Nov 11 11:27:37 DeepThought kernel: [ 226.225945] usb 8-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Nov 11 11:27:37 DeepThought kernel: [ 226.225951] usb 8-2: Product: FireTV
Nov 11 11:27:37 DeepThought kernel: [ 226.225956] usb 8-2: Manufacturer: Amazon
Nov 11 11:27:37 DeepThought kernel: [ 226.225961] usb 8-2: SerialNumber: G070GV05544205DE
Nov 11 11:27:37 DeepThought mtp-probe: checking bus 8, device 4: "/sys/devices/pci0000:00/0000:00:1d.7/usb8/8-2"
Nov 11 11:27:37 DeepThought mtp-probe: bus: 8, device: 4 was an MTP device
After taking a closer look at my syslog and doing some research on problems with /dev/ttyACM0, I finally found the problem. It's the modemmanager. That service immmediately "grabs" the device and tries to do some invalid settings, which leads to an near immediate disconnect.
After I uninstalled the modemmanger (which seemed preinstalled in debian jessie, at least I never installed it on purpose) with
Code:
apt-get remove modemmanager
both of my problems were gone. The device stayed up for 3 seconds and after reboot of the Fire TV it had the same devicename /dev/ttyACM0 again. So I could undo my changes to the handshake script and had instant success with it.
Now I'll try rooting. WHOOT!
Thank you very much for your efforts!
I'd just like to check my understanding - are the instructions you posted comprehensive to obtaining root from absolute scratch?
I know soldering of eMMC and such things were used in development, but that is not needed now after you've done the hard work, correct?
I can just follow your steps above and root the FTV2?
gu3stZA said:
Thank you very much for your efforts!
I'd just like to check my understanding - are the instructions you posted comprehensive to obtaining root from absolute scratch?
I know soldering of eMMC and such things were used in development, but that is not needed now after you've done the hard work, correct?
I can just follow your steps above and root the FTV2?
Click to expand...
Click to collapse
Yes, you're right. No need to solder anything. You just need the tools stated in the instructions.
Hardware:
- a computer running Linux (or something very close)
- a A to A USB cable
Software:
- python3 and python3-serial packages
- adb package (not necessary but recommended)
- zeroepochs scripts and patchfiles
That said, a certain amount of base knowledge regarding Linux doesn't hurt .
Thanks! I've played around with Linux but would definitely classify myself as a beginner. I guess we'll see how user-friendly the instructions are
This is good news, definitely progress, could this be integrated into ADBFire for windows
Jay794 said:
This is good news, definitely progress, could this be integrated into ADBFire for windows
Click to expand...
Click to collapse
This would be perfect. Or even adb. I've just never used Linux
zeroepoch said:
It has only been tested on a US device and I don't know at this point if non US devices are different, maybe not.
Click to expand...
Click to collapse
Hi zeroepoch,
I just used your rooting scripts successfully on a non US (in my case German) version of the Fire TV 2!
Greets,
Christian
skyball2 said:
Hi zeroepoch,
I just used your rooting scripts successfully on a non US (in my case German) version of the Fire TV 2!
Greets,
Christian
Click to expand...
Click to collapse
Thanks for the feedback. Glad to hear it worked!
Successful root under arch Linux! Thanks for your hard work.
By any chance does this root work for the original fire TV ?
Sent from my SM-N910F using Tapatalk
Savage13 said:
By any chance does this root work for the original fire TV ?
Click to expand...
Click to collapse
No. It's MediaTek specific. It may work on most MediaTek devices though.
how can u tell handshake is ok and start patching ?
reiteravi said:
how can u tell handshake is ok and start patching ?
Click to expand...
Click to collapse
It will print "Handshake Complete". Also the serial device will remain present rather than disappear after a few seconds.