Develop Bugs

[GUIDE] Installing stock kernel with ice glacier any

I recently came across a couple of threads in which it seems it was desirable (for some) to run the stock kernel, but with the ice glacier ROM. There were a couple of methods that I saw, neither of which seemed to work for me (one was an update kernel zip file package to be applied from recovery mode from the sdcard, and the other was more involved (see THISthread). The kernel provided in that thread is actually not the true STOCK kernel, as best as I can tell. It is likely equivalent, but uname -r still returns a Gr8gorilla lable.
So I decided to try the following method. First, if you have a nandroid/clockwork recovery backup of your device before installing ice, then you already have everything you need to revert to the stock kernel. Here is the procedure.
1) reboot phone into recovery
2) go into backup and restore
3) select advanced restore
4) select the very first backup set (the stock, probably first rooted one).
5) select restore boot partition
After this completes, you'll have ice but with stock kernel. However, your wireless will not work until you place the correct kernel module file corresponding to your kernel (bcm4329.ko) in the /system/lib/modules directory. In your nandroid backup set, there is a system.img file. Transfer this file to your computer, and use unyaffs to extract its contents and look for lib/modules/bcm4329.ko
6) while in recovery mode, make sure to mount /system
7) remove or rename the /system/lib/modules/bcm4329.ko file
8) adb push bcm4329.ko /system/lib/modules/bcm4329.ko
9) unmount /system from recovery, and reboot.
That's it. I tested this and ended up seeing:
Code:
Linux localhost 2.6.32.21-g899d047 #1 PREEMPT Tue Oct 26 16:10:01 CST 2010 armv7l GNU/Linux
and my wireless was working just fine. I have attached the wireless kernel module corresponding with stock kernel, and I have attached the boot.img from stock, in case you're reading this, and by some strange reason, you don't actually have an original backup.
I don't personally plan on running stock kernel, I just wanted to see if I _could_ if I wanted to.
Hope you find this useful.
Kambiz

One thing I noted btw, is that after doing this, when I did adb shell, it dropped me into a non-root shell by default, and I had to type "su" or "su - " to gain root. The other thing to note, is that the stock initrd, has the following default.prop entry:
ro.secure=1
whereas ice has:
ro.secure=0
What does this mean?! (besides double rainbow all the way across the sky)?

Setting ro.secure=0 allows adb root functions to work.
My MyGlacier 4G MINE!!!

grankin01 said:
Setting ro.secure=0 allows the "adb remount" command to work.
My MyGlacier 4G MINE!!!
Click to expand...
Click to collapse
Right. That's what I thought. But I have to say, it seemed to work anyway, because I did:
$ su -
# mount -o remount,rw /system
and then
# cd /system/lib/modules
# mv bcm4329.ko bcm4329.ko.ice
# cp /sdcard/stock-bcm4329.ko bcm4329.ko
# chmod 644 bcm4329.ko
# cd /
# mount -o remount,ro /system
Then I rebooted, and the "stock" driver file that I just put in place was persistent. So I'm not sure if clockworkmod is doing something to ensure ro.secure=0 ... I'm not sure.

No, it means that "adb root" and "adb remount" and any of the other adb root functions will have root access to your device through Android Debug Bridge (adb) by default. My adb shell always comes up with a $ prompt and I have to "su" for root. Setting this to 0 should let you type "adb root" or " adb remount" from your command shell on your desktop and allow you a root prompt device shell or rw access to system without having to "su" or "mount -o remount,rw /dev/block/mmcblk0p25 /system".
My MyGlacier 4G MINE!!!

so this is the true stock kernel?

tiger013 said:
so this is the true stock kernel?
Click to expand...
Click to collapse
Yes. I made a clockworkmod backup (nandroid backup) after rooting my phone with visionary+, but didn't alter anything else. So once I overwrote everything with Ice Glacier, I still have stock (post OTA update to 2.2.1) kernel and wireless drivers. (attached to OP).
I don't know how to convert them to a flashable update.zip, but I was able to load them using the procedure above.
EDIT:
Notice that the output of "uname -a" when run from adb shell is:
Linux localhost 2.6.32.21-g899d047 #1 PREEMPT Tue Oct 26 16:10:01 CST 2010 armv7l GNU/Linux
The Gorilla kernels have EXTRAVERSION strings added (the kernel version follows after "Linux localhost" in that string)

thank you! I added it to my thread

thanks for this peeps

ADB and FASTBOOT binary for Linux amd64

WARNING!!!
This binary files are for UNIX system, with amd64 architecture ONLY!!!
This morning, I'm little bit confuse to execute adb binary file which given by zeppelinrox in Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH.zip file. After check this binary file, I realize that this file is 32bit binary.
Code:
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# ls -lahrt .
total 6.4M
-rwxr-xr-x 1 root root 17K Nov 11 1999 tee.exe
-rwxr-xr-x 1 root root 16K Nov 11 1999 sleep.exe
-rwxr-xr-x 1 root root 26K Jun 20 2003 tr.exe
-rwxr-xr-x 1 root root 191K Jul 30 2003 awk.exe
-rwxr-xr-x 1 root root 133K Oct 23 2003 grep.exe
-rwxr-xr-x 1 root root 93K Oct 25 2003 sed.exe
-rwxr-xr-x 1 root root 3.2M Sep 25 2007 sh.exe
-rwxr-xr-x 1 root root 284K Jul 12 2008 zip.exe
-rwxr-xr-x 1 root root 5.4K Aug 1 2008 dexopt-wrapper
-rwxr-xr-x 1 root root 200K Apr 20 2009 unzip.exe
-rwxr-xr-x 1 root root 342K Nov 19 2011 adb-mac
-rwxr-xr-x 1 root root 333K Nov 19 2011 adb
-rwxr-xr-x 1 root root 60K Jul 15 2012 AdbWinUsbApi.dll
-rwxr-xr-x 1 root root 94K Jul 15 2012 AdbWinApi.dll
-rwxr-xr-x 1 root root 187K Jul 15 2012 adb.exe
-rwxr-xr-x 1 root root 528K Dec 16 12:46 baksmali.jar
-rwxr-xr-x 1 root root 622K Dec 16 12:46 smali.jar
-rwxr-xr-x 1 root root 20K Dec 25 15:20 ultimatic_jar_patcher_adb.bat
-rwxr-xr-x 1 root root 17K Dec 25 15:20 ultimatic_jar_patcher_adb.sh
-rwxr-xr-x 1 root root 26K Dec 25 22:31 ALL_ROMS_Ultimate_Jar_Power_Tools-Smali_Patcher_RC9.sh
drwxr-xr-x 4 root root 4.0K Mar 28 10:21 ..
drwxr-xr-x 2 root root 4.0K Mar 28 10:21 .
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# file adb
adb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped
And I'm using amd64 bit architecture
Code:
[email protected]:~# uname -a
Linux kali 3.7-trunk-amd64 #1 SMP Debian 3.7.2-0+kali5 x86_64 GNU/Linux
If you try execute adb binary which given by zeppelinrox, you will got this error message:
Code:
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# ./adb
bash: ./adb: No such file or directory
In order to execute this 32bit binary file, yo have to install ia32-libs on your system with this command:
Code:
[email protected]:~# apt-get install ia32-libs
But it will give you some errors like these:
Code:
[email protected]:~# apt-get install ia32-libs
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
ia32-libs : Depends: lib32bz2-1.0 but it is not going to be installed
Depends: lib32asound2 (> 1.0.18) but it is not going to be installed
Depends: lib32gcc1 (>= 1:4.1.1) but it is not going to be installed
Depends: lib32ncurses5 (>= 5.7+20100313) but it is not going to be installed
Depends: lib32stdc++6 (>= 4.1.1) but it is not going to be installed
Depends: lib32v4l-0 (>= 0.5.0) but it is not going to be installed
Depends: lib32z1 (>= 1:1.2.3.3.dfsg) but it is not going to be installed
PreDepends: libc6-i386 (>= 2.9-18) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
Desperate with this condition, I decide to compile adb and fastboot using amd64 architecture. So you can use adb and fastboot with your amd64 architecture. Give a try!
Here is some output that these binary files are based from amd64 architecture:
Code:
[email protected]:/tmp/adb_and_fastboot# ls -lahrt .
total 368K
-rwxr-xr-x 1 root root 91K Mar 28 11:37 fastboot
-rwxr-xr-x 1 root root 153K Mar 28 11:40 adb
-rw-r--r-- 1 root root 111K Mar 28 11:41 adb_and_fastboot.zip
drwxr-xr-x 2 root root 4.0K Mar 28 11:41 .
drwxrwxrwt 12 root root 4.0K Mar 28 11:52 ..
[email protected]:/tmp/adb_and_fastboot# file adb
adb: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.26, BuildID[sha1]=0x2bd948a70efb09cc8604f9903dd6f617686fa707, stripped
[email protected]:/tmp/adb_and_fastboot# file fastboot
fastboot: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.26, BuildID[sha1]=0xaaf735fdf5123bb446cea17c45e42bef3017c1d5, stripped
Note:
After extract these files, move them to /usr/bin directory, or /bin/ directory using this command
Code:
[email protected]:~# mv adb /bin/adb && mv fastboot /bin/fastboot
If you are about using Ultimatic Jar Patcher Tools, just overwrite original adb (which based from i386) with your adb (which based from amd64):
Code:
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# ls -lahrt .
total 6.4M
-rwxr-xr-x 1 root root 17K Nov 11 1999 tee.exe
-rwxr-xr-x 1 root root 16K Nov 11 1999 sleep.exe
-rwxr-xr-x 1 root root 26K Jun 20 2003 tr.exe
-rwxr-xr-x 1 root root 191K Jul 30 2003 awk.exe
-rwxr-xr-x 1 root root 133K Oct 23 2003 grep.exe
-rwxr-xr-x 1 root root 93K Oct 25 2003 sed.exe
-rwxr-xr-x 1 root root 3.2M Sep 25 2007 sh.exe
-rwxr-xr-x 1 root root 284K Jul 12 2008 zip.exe
-rwxr-xr-x 1 root root 5.4K Aug 1 2008 dexopt-wrapper
-rwxr-xr-x 1 root root 200K Apr 20 2009 unzip.exe
-rwxr-xr-x 1 root root 342K Nov 19 2011 adb-mac
-rwxr-xr-x 1 root root 333K Nov 19 2011 adb
-rwxr-xr-x 1 root root 60K Jul 15 2012 AdbWinUsbApi.dll
-rwxr-xr-x 1 root root 94K Jul 15 2012 AdbWinApi.dll
-rwxr-xr-x 1 root root 187K Jul 15 2012 adb.exe
-rwxr-xr-x 1 root root 528K Dec 16 12:46 baksmali.jar
-rwxr-xr-x 1 root root 622K Dec 16 12:46 smali.jar
-rwxr-xr-x 1 root root 20K Dec 25 15:20 ultimatic_jar_patcher_adb.bat
-rwxr-xr-x 1 root root 17K Dec 25 15:20 ultimatic_jar_patcher_adb.sh
-rwxr-xr-x 1 root root 26K Dec 25 22:31 ALL_ROMS_Ultimate_Jar_Power_Tools-Smali_Patcher_RC9.sh
drwxr-xr-x 4 root root 4.0K Mar 28 10:21 ..
drwxr-xr-x 2 root root 4.0K Mar 28 10:21 .
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# file adb
adb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# cp -fv $(which adb) adb
`/usr/bin/adb' -> `adb'
[email protected]:~/Downloads/Android/Tweak/Ultimatic_Jar_Patcher_Tools_RC6_ALL_DEX_ALL_OSes_NO_FLASH# file adb
adb: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.26, BuildID[sha1]=0x2bd948a70efb09cc8604f9903dd6f617686fa707, stripped
Any question? I hope this will help you.

Qucker Fix for adb & fastboot on Linux amd64
This fixed it for me without the hassel. After you have followed a regular install of adb or whatever binary you are trying to use. Then:
dpkg --add-architecture i386
apt-get update
apt-get install ia32-libs
apt-get install libncurses5:i386
reboot
//edit- Running Kali - Linux amd 64 gnome Version 3.4.2 just by the way.

maylonious said:
This fixed it for me without the hassel. After you have followed a regular install of adb or whatever binary you are trying to use. Then:
dpkg --add-architecture i386
apt-get update
apt-get install ia32-libs
apt-get install libncurses5:i386
reboot
//edit- Running Kali - Linux amd 64 gnome Version 3.4.2 just by the way.
Click to expand...
Click to collapse
Yeah, this is happened (breaking dependencies) if you didn't include mirror on your source.list at the end of Kali Linux Installation. Anyway, just running some command like this
Code:
[email protected]:~# echo "deb http://http.kali.org/kali kali main non-free contrib" > /etc/apt/source.list
[email protected]:~# echo "deb-src http://http.kali.org/kali kali main non-free contrib" >> /etc/apt/source.list
[email protected]:~# echo "deb http://security.kali.org/kali-security kali/updates main contrib non-free" >> /etc/apt/source.list
[email protected]:~# dpkg --add-architecture i386
[email protected]:~# apt-get update
[email protected]:~# apt-get install ia32-libs
Should fix the problem. I made this thread for them who stuck on breaking dependencies. :highfive:

The adb and fastboot executables are not working on android 6.0.1.
I copied them to /bin and then tried to execute.
Each gives the following error:
Code:
sush: //bin/adb: not executable: 64-bit ELF file
(with fastboot adb is replaced in the error with fastboot)
I've read about it here and i think it could be fixed with giving the compiler a parameter to use android's linker instead of libld.so. The guys seen in the forum i linked passed this option to linker, these made the executable work:
Code:
--dynamic-linker=/system/bin/linker
And this to FPC:
Code:
-k--dynamic-linker=/system/bin/linker
I would be glad if you could do that, because i can't find any adb and fastboot (arm) executables to run in my phone, only shady executables which maybe stole my whole life.

[Q] Nexus 7 (2013) + USB to ethernet fails!

Nexus 7 (2013) + USB-to-ethernet adapter ASIX: eth0 appears in netcfg.
ifconfig eth0 192.168.11.2 netmask 255.255.255.0 up
route add default gw 192.168.11.1 dev eth0
But it's impossible to ping the gateway. Has anyone managed to make work Nexus 7 (2013) + USB-to-ethernet?

Are you using stock? Because I'm pretty sure that has to be added before it will work.
On my MK808b Android stick, the Deva had to manually add the .ko files and other stuff.
Sent from my Nexus 7 using xda premium

gregoiregentil said:
Nexus 7 (2013) + USB-to-ethernet adapter ASIX: eth0 appears in netcfg.
ifconfig eth0 192.168.11.2 netmask 255.255.255.0 up
route add default gw 192.168.11.1 dev eth0
But it's impossible to ping the gateway. Has anyone managed to make work Nexus 7 (2013) + USB-to-ethernet?
Click to expand...
Click to collapse
I was able to ping the gateway using the above commands, minus the "up" on the end of the ifconfig line, (rooted Nexus 7 2013, ASIX usb ethernet) but have not been able to get DNS working... tried the command below but it did not work:
setprop net.dns1 8.8.8.8
Just found this:
code.google.com/p/android/issues/detail?id=58868
going to try dhcp tonight...

Thanks tog42. That's a useful post. After dozens of tries, I have managed to get a dhcp addresss on the rooted Nexus 7 2013 from my router. My router doesn't seem to do a great job and that's part of the problem. But I still don't manage to set a fixed IP address on the tablet and then ping the router.
Yes, I noticed dhcpd_eth0 missing in the logcat. I'm happy to see that there is a filed bug for this.

Hi, I can't seem to get DNS working with DHCP or a static setup... was DNS working when you got your DHCP address?
Thanks!

tog42 said:
Hi, I can't seem to get DNS working with DHCP or a static setup... was DNS working when you got your DHCP address?
Thanks!
Click to expand...
Click to collapse
Hi tog42 did you manage to get this working? (or anyone else?)

According to one of the manufacturers, there's a small error in the code for 4.3 on the N7 2013. Currently, no device natively works as designed with this model.
They've been notified and the next software update should incorporate it. Otherwise, the above might work in some cases.

Can you tell us your source of this statement?

BobjGear.
+ the representative of a Chinese OEM. (that one I'm not at liberty to disclose)

I have confirmed that USB ethernet works automatically with DHCP after applying the init.flo.rc patch from here: https://code.google.com/p/android/issues/detail?id=58868

And how would one go about doing that merge?
That was in 15J ... Does 15Q have that already done?

danvee said:
And how would one go about doing that merge?
That was in 15J ... Does 15Q have that already done?
Click to expand...
Click to collapse
15Q is not fixed... I used the boot.img from the 15Q factory image and used the tools from here: http://forum.xda-developers.com/showthread.php?t=2319018 to split the boot.img which unpacked the ramdisk, patched the file in the ramdisk, repacked it, created a new boot.img and flashed it. (Made a couple of mistakes the first time though and the Nexus was stuck in a boot loop but was able to restore from one of my backups.)

Sounds wayyy too complex for the average user.
Might need to wait for them to officially incorporate it.

tog42 said:
15Q is not fixed... I used the boot.img from the 15Q factory image and used the tools from here: http://forum.xda-developers.com/showthread.php?t=2319018 to split the boot.img which unpacked the ramdisk, patched the file in the ramdisk, repacked it, created a new boot.img and flashed it. (Made a couple of mistakes the first time though and the Nexus was stuck in a boot loop but was able to restore from one of my backups.)
Click to expand...
Click to collapse
Hey Tog42, I used the same tools, split_boot did the split and unpack, only edited init.flo.rc as per the patch, then used repack_ramdisk and mkbootimg (using the outputs from boot_info). Flashed and it boot loops so I restored it.
So any tips? Maybe I made the same mistakes you did the first time round?
Appreciate any advice.

cz32 said:
Hey Tog42, I used the same tools, split_boot did the split and unpack, only edited init.flo.rc as per the patch, then used repack_ramdisk and mkbootimg (using the outputs from boot_info). Flashed and it boot loops so I restored it.
So any tips? Maybe I made the same mistakes you did the first time round?
Appreciate any advice.
Click to expand...
Click to collapse
Hi cz32, I was using different tools when I was having the issues with boot loops... these tools worked the first time, I used all of the info provided by boot_info. Also, I patched the init.flo.rc file (patch originalfile patchfile) instead of manually editing it.

Fix was done.
Check here for progress on getting it added into the next update.
http://code.google.com/p/android/issues/detail?id=58868

For those of you who got this working would any of you be so kind as to post some sort of walkthrough or guide as to how you exactly did it? I really would like to get this USB to ethernet adapter working with my N7. Thanks!

tog42 said:
Hi cz32, I was using different tools when I was having the issues with boot loops... these tools worked the first time, I used all of the info provided by boot_info. Also, I patched the init.flo.rc file (patch originalfile patchfile) instead of manually editing it.
Click to expand...
Click to collapse
Thanks that's ok now, it was the ramdisk offset.
So I have a bootable device with "service dhcpcd_eth0 /system/bin/dhcpcd -ABDKL" and "service iprenew_eth0 /system/bin/dhcpcd -n" in the init.flo.rc. Switching off WiFi and plugging in doesn't work, but if I plug in then go into terminal and 'dhcpcd eth0' then it gets an IP and the browser connects, but mail apps, play store etc have no connectivity.
This is an LTE btw..
Any thoughts?
edit: some variables;
1. Boot nexus with wifi switched off, run dhcpcd eth0 = no connectivity except able to browse IP addresses in chrome
2. Use wifi then switch wifi off, plug in eth0 (same router) and dhcpcd = normal chrome browsing, no other apps have connectivity.
[email protected]:/ # dmesg | grep eth
<6>[15811.115203] asix 2-1:1.0: eth0: register 'asix' at usb-msm_hsusb_host-1, ASIX AX88772 USB 2.0 Ethernet, f4:f9:51:e1:2a:48
<6>[15894.166778] ADDRCONF(NETDEV_UP): eth0: link is not ready
<6>[15894.237640] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
<6>[15894.239318] asix 2-1:1.0: eth0: link down
<6>[15896.031555] asix 2-1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
<7>[15904.802978] eth0: no IPv6 routers present
With wlan off and etho0 connected:
lo UP 127.0.0.1/8 0x00000049 00:00:00:00:00:00
eth0 UP 0.0.0.0/0 0x00001043 f4:f9:51:e1:2a:48
sit0 DOWN 0.0.0.0/0 0x00000080 00:00:00:00:00:00
[email protected]:/ # dhcpcd eth0
dhcpcd[2638]: version 5.5.6 starting
dhcpcd[2638]: eth0: rebinding lease of 192.168.0.13
dhcpcd[2638]: eth0: acknowledged 192.168.0.13 from 192.168.0.1
dhcpcd[2638]: eth0: checking for 192.168.0.13
dhcpcd[2638]: eth0: leased 192.168.0.13 for 86400 seconds
dhcpcd[2638]: forked to background, child pid 2673
[email protected]:/ # cat /proc/net/route
Iface Destination Gateway Flags RefCnt Use Metric Mask MTU Window IRTT
eth0 00000000 0100A8C0 0003 0 0 226 00000000 0 0 0
eth0 0000A8C0 00000000 0001 0 0 226 00FFFFFF 0 0 0
[email protected]:/ # ip route show
default via 192.168.0.1 dev eth0 metric 226
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.13 metric 226
And with wlan working:
[email protected]:/ # ip route show
default via 192.168.0.1 dev wlan0
192.168.0.0/24 dev wlan0 scope link
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.9
192.168.0.1 dev wlan0 scope link
[email protected]:/ # cat /proc/net/route
Iface Destination Gateway Flags RefCnt Use Metric Mask MTU Window IRTT
wlan0 00000000 0100A8C0 0003 0 0 0 00000000 0 0 0
wlan0 0000A8C0 00000000 0001 0 0 0 00FFFFFF 0 0 0
wlan0 0000A8C0 00000000 0001 0 0 0 00FFFFFF 0 0 0
wlan0 0100A8C0 00000000 0005 0 0 0 FFFFFFFF 0 0 0
[email protected]:/ # getprop net.dns1
192.168.0.1
[email protected]:/ # getprop net.dns2
(ISP dns)

hotsammysliz said:
For those of you who got this working would any of you be so kind as to post some sort of walkthrough or guide as to how you exactly did it? I really would like to get this USB to ethernet adapter working with my N7. Thanks!
Click to expand...
Click to collapse
I don't have it working, but as far as I can tell I've followed the same steps as people who do and it could just be different for LTE.
So the steps are (and ask if you want me to expand on any of these), and maybe get tog42 to confirm!
- Obtain boot.img - either from Google or from the device
- Get these tools http://forum.xda-developers.com/showthread.php?t=2319018
- Use split_boot to unpack the img, this will create a Ramdisk folder './split_boot boot.img' (have the img and tools in the same folder)
- In Ramdisk folder, edit or patch init.flo.rc as per http://code.google.com/p/android/issues/detail?id=58868
- Use repack_ramdisk to pack the ramdisk folder that split_boot unpacked './repack_ramdisk ramdisk boot.img-ramdisk.gz'
- Use boot_info to obtain the info needed for the next step './boot_info boot.img'
- Use mkbootimg to put the now packed ramdisk and kernel back into boot.img './mkbootimg --kernel boot.img-kernel --ramdisk boot.img-ramdisk.gz --base 0x80200000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3' --pagesize 2048 -o new_boot.img' (changing the base, cmdline, pagesize to match the info you obtained with boot_info)
- Backup the device
- Unlock the bootloader (example http://www.wugfresh.com/nrt/)
- Flash the new boot.img temporarily to test
- If it works flash permanent.
Problems I had
- First attempt wouldn't boot, the ramdisk offset was incorrect when using mkbootimg, the mkbootimg I have doesn't allow it to be changed so I used a hex editor and changed it on the complete boot.img.
- DHCP doesn't work as per my last post, I'm not sure if I have missed something or if something else is required for an LTE, as I think most people would be doing this on a wifi. Anyone please comment!
So take that as a draft and get someone who actually made it work to confirm first

almost there
cz32 said:
I don't have it working, but as far as I can tell I've followed the same steps as people who do and it could just be different for LTE.
So the steps are (and ask if you want me to expand on any of these), and maybe get tog42 to confirm!
- Obtain boot.img - either from Google or from the device
- Get these tools http://forum.xda-developers.com/showthread.php?t=2319018
- Use split_boot to unpack the img, this will create a Ramdisk folder './split_boot boot.img' (have the img and tools in the same folder)
- In Ramdisk folder, edit or patch init.flo.rc as per http://code.google.com/p/android/issues/detail?id=58868
- Use repack_ramdisk to pack the ramdisk folder that split_boot unpacked './repack_ramdisk ramdisk boot.img-ramdisk.gz'
- Use boot_info to obtain the info needed for the next step './boot_info boot.img'
- Use mkbootimg to put the now packed ramdisk and kernel back into boot.img './mkbootimg --kernel boot.img-kernel --ramdisk boot.img-ramdisk.gz --base 0x80200000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=flo user_debug=31 msm_rtb.filter=0x3F ehci-hcd.park=3' --pagesize 2048 -o new_boot.img' (changing the base, cmdline, pagesize to match the info you obtained with boot_info)
- Backup the device
- Unlock the bootloader (example http://www.wugfresh.com/nrt/)
- Flash the new boot.img temporarily to test
- If it works flash permanent.
Problems I had
- First attempt wouldn't boot, the ramdisk offset was incorrect when using mkbootimg, the mkbootimg I have doesn't allow it to be changed so I used a hex editor and changed it on the complete boot.img.
- DHCP doesn't work as per my last post, I'm not sure if I have missed something or if something else is required for an LTE, as I think most people would be doing this on a wifi. Anyone please comment!
So take that as a draft and get someone who actually made it work to confirm first
Click to expand...
Click to collapse
I need help!
first thanks for your input it helped me throught :highfive: and must I mention I used Cygwin and did all the steps until I tried to use mkbootimg :silly:
At that point it was responding:
-bash: ./mkbootimg: cannot execute binary file
so I did file mkbootimg and I realized it was a 64bit file so I went ahead and found a 32bit version of the file on github.com
I tried to run the cmd with mkbootimg.32bit and it responded the same thing:
-bash: ./mkbootimg.32bit: cannot execute binary file
I'm almost done with the procedure as I know how to flash the boot.img after that, im just stuck at mkbootimg...
Any help with this? and please dont say it's cygwin and theres nothing to do, perhaps I need a package or a file for cygwin to execute mkbootimg??
Kind Regards,
Eastwoods

[Q] adbd always starts up! How do I have it start up only when required?

Hi,
I have a nexus one running PA-3.99rc2 with the following superuser modifications:
* replaced stock superuser app with SuperSU (system app)
* installed adbtoggle (system app)
* I do have the exposed framework and xprivacy installed, with no restrictions on the settings app, the adbtoggle app and the supersu app.
In the developer options, I have
* "Root Access" set to disabled.
* USB debugging" unchecked
* "select debug app" -> no debug app selected
However, what happens is that whenever I connect a USB cable, I can just run 'adb shell' and get a root prompt.
C:\> adb shell
[email protected]:/
Click to expand...
Click to collapse
This is possible irrespective of the adb toggle setting or the root access setting or the USB debugging setting.
I am simply handed a shell even when USB debugging is turned off, whether I asked for it or not.
I haven't tried it over wifi but I have reason to believe that it would be accessible all the same.
When I toggle ADB using the app or the settings panel, I do see the notification that usb debugging was turned on or off - but in reality it has no effect on the actual state of the debug bridge (which is permanently on.)
I did notice:
[email protected]:/ # cd /
cd /
[email protected]:/ # grep -e 'start adbd' init*
grep -e 'start adbd' init*
init.mahimahi.usb.rc: start adbd
init.mahimahi.usb.rc: start adbd
init.mahimahi.usb.rc: start adbd
init.mahimahi.usb.rc: start adbd
init.mahimahi.usb.rc: start adbd
init.rc: start adbd
init.usb.rc: start adbd
init.usb.rc: start adbd
init.usb.rc: start adbd
init.usb.rc: start adbd
Click to expand...
Click to collapse
All the init scripts in "/" have exec, and are owned by root: "-rwxr-x--- root root", unmodified since the ROM's installation.
Are the init scripts starting up adbd irrespective of my settings? Or am I having/doing something wrong?
Has anyone else observed this behaviour?
Is there any way to fix this behaviour and have adbd run only when asked to?
Thanks in advance,
fruit-salad
===================
[email protected]:/ # uname -a
uname -a
Linux localhost 2.6.38.8-evervolv-02117-g69a13bd #1 PREEMPT Sat Sep 28 03:33:41
PDT 2013 armv7l GNU/Linux
I'm running Paranoid Android 3.99.1-RC2- Release 2 from (d-h.st/BuG)
gApps not installed yet.
boot, system and cache were wiped before install, however I did retain my sd-ext partition.
I don't have any old odex files on the sd-ext, a2sd re-optimized the apps on my sd-ext when enabled.
UPDATE:
========
my default.prop has:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
persist.sys.strictmode.disable=true
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
Click to expand...
Click to collapse
but trying to change
persist.service.adb.enable=1 to persist.service.adb.enable=0
and
persist.sys.usb.config=mass_storage,adb to persist.sys.usb.config=mass_storage
isn't helping. Changes are lost after an update.
According to ?t=2209401 build.prop isn't editable -- is default.prop also not editable?
I did remount / "rw" before editing.
Help?

[ROOT] FireTV2 - SSH unable to connect

All I've done is root, reboot, disable updates, reboot, install system tools via adbfire, reboot, install ssh, reboot.
So in theory this should affect all who attempt to use it.
Installed SSH via adbFire, started via ADB shell:
ADB Shell:
Code:
[email protected]:/ $ sshstatus
ssh is not running
1|[email protected]:/ $ su
[email protected]:/ # sshstart
[3993] Nov 29 04:11:19 Running in background
Mac:
Code:
$ ssh [email protected]
Warning: Permanently added '10.10.10.117' (RSA) to the list of known hosts.
CANNOT LINK EXECUTABLE DEPENDENCIES: "libc.so" is 32-bit instead of 64-bit
ADB Shell:
Code:
[3995] Nov 29 04:11:22 Child connection from 10.10.10.115:64826
[3995] Nov 29 04:11:23 Pubkey auth succeeded for 'root' with key md5 96:54:9d:f7:95:9e:4e:27:61:b3:7e:9c:fe:57:25:72 from 10.10.10.115:64826
[3995] Nov 29 04:11:23 Exit (root): Disconnect received
Looking at the filesystem you can see that both the 32bit and 64bit library files are there (output trimmed).
Code:
[email protected]:/ # find /|grep libc
/system/lib/libc.so
/system/lib64/libc.so
If I do the crazy thing of renaming the 32bit libc (so that it does not load, forcing usage of 64bit lib) it does allow SSH to work but that is way too risky of a configuration, so I won't use that.

It sounds like there is a linker path problem. The tools probably need to be properly updated for 64-bit support.

zeroepoch said:
It sounds like there is a linker path problem. The tools probably need to be properly updated for 64-bit support.
Click to expand...
Click to collapse
Zeroepoch is exactly correct. adbFire's ssh tools are 32-bit and compiled for the ATV/1. I don't have an eta for an update, sorry.