Quick and dirty modified split_bootimg.pl for splitting our signed boot images.
This will strip the first 256bytes (the signature) from the image.
Advice, this will ruin unsigned boot images, if you are not a competent developer leave th alone, if you are competent
make backups before using.
#!/usr/bin/perl
######################################################################
#
# File : split_bootimg.pl
# Author(s) : William Enck <[email protected]>
# Description : Split appart an Android boot image created
# with mkbootimg. The format can be found in
# android-src/system/core/mkbootimg/bootimg.h
#
# Thanks to alansj on xda-developers.com for
# identifying the format in bootimg.h and
# describing initial instructions for splitting
# the boot.img file.
#
# Last Modified : Tue Dec 2 23:36:25 EST 2008
# By : William Enck <[email protected]>
#
# Copyright (c) 2008 The Pennsylvania State University
# Systems and Internet Infrastructure Security Laboratory
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
######################################################################
#
# Modified for signed boot images, no longer compatible with
# unsigned images. ~jcase
#
# Modded by a friend of AndIRC
#
######################################################################
Nice Job thanks 4 this!
Sent from my ADR6400L using XDA Premium App
tanks d000d
Thank you jcase
Sent from my ADR6400L using XDA Premium App
sadly, this script can not work on galaxy note GT-N7000
Related
No need to use telnet anymore, I ported dropbear sshd over. (Mostly just mangled up the authentication.)
I provide the patch with basically no support, and reserve the right to ridicule you if you ask stupid questions. (If I described something incorrectly or you have actual questions, thats different. But if you aren't comfortable cross-compiling code - or compiling it at all - then this is not for you.)
It isn't plug and play, its a patch to the dropbear shipped with the Android platform code and you are on your own getting it to cross-compile. (I used the sourcery pack.) My build is MULTICALL=1 STATIC=1 and includes dbclient, dropbear, dropbearkey. You'll want to set the root password in debug.h and follow the instructions in the patch.
Latest patch here: http://link.sigkill.net/dropbear-v1.1.patch
# A couple of hints for this script.
# debug.h - you want to set a password at the bottom
# I prefer to build STATIC=1 MULTICALL=1 but you can do what you want.
#
# It still checks /etc/shells so unfortunately you have to create that file
# and put your shell in it. (by default I use /system/bin/rootsh. Which you
# will want to create.)
# If you want key-based authentication, there's some additional prep work:
# /data/dropbear needs to be root:root 744 and
# /data/dropbear/.ssh root:root 700
# options.h | 30 +++++++++++++++---------------
# svr-auth.c | 34 +++++++++++++++++++++++++++++++++-
# svr-chansession.c | 2 ++
# 3 files changed, 50 insertions(+), 16 deletions(-)
Changelog: v1.1 initial public release
Plans:
v1.2 remove /etc/shells check
v? add configurable password
v? auto-create directories
THANK YOU!!
Hi
I've got a question. How to connect blade (on 2.2 froyo) to ad-hoc wirless?
Probably must change a "wpa_supplicant" file (and probably other's simmilar), but i don't know how
This is my "wpa_supplicant" (viewed by normal notepad) :
Code:
# Note: All file paths in this configuration file should use full (absolute,
# not relative to working directory) path in order to allow working directory
# to be changed. This can happen if wpa_supplicant is run in the background.
# Whether to allow wpa_supplicant to update (overwrite) configuration
#
# This option can be used to allow wpa_supplicant to overwrite configuration
# file whenever configuration is changed (e.g., new network block is added with
# wpa_cli or wpa_gui, or a password is changed). This is required for
# wpa_cli/wpa_gui to be able to store the configuration changes permanently.
# Please note that overwriting configuration file will remove the comments from
# it.
update_config=1
# global configuration (shared by all network blocks)
#
# Parameters for the control interface. If this is specified, wpa_supplicant
# will open a control interface that is available for external programs to
# manage wpa_supplicant. The meaning of this string depends on which control
# interface mechanism is used. For all cases, the existance of this parameter
# in configuration is used to determine whether the control interface is
# enabled.
#
# For UNIX domain sockets (default on Linux and BSD): This is a directory that
# will be created for UNIX domain sockets for listening to requests from
# external programs (CLI/GUI, etc.) for status information and configuration.
# The socket file will be named based on the interface name, so multiple
# wpa_supplicant processes can be run at the same time if more than one
# interface is used.
# /var/run/wpa_supplicant is the recommended directory for sockets and by
# default, wpa_cli will use it when trying to connect with wpa_supplicant.
#
# Access control for the control interface can be configured by setting the
# directory to allow only members of a group to use sockets. This way, it is
# possible to run wpa_supplicant as root (since it needs to change network
# configuration and open raw sockets) and still allow GUI/CLI components to be
# run as non-root users. However, since the control interface can be used to
# change the network configuration, this access needs to be protected in many
# cases. By default, wpa_supplicant is configured to use gid 0 (root). If you
# want to allow non-root users to use the control interface, add a new group
# and change this value to match with that group. Add users that should have
# control interface access to this group. If this variable is commented out or
# not included in the configuration file, group will not be changed from the
# value it got by default when the directory or socket was created.
#
# When configuring both the directory and group, use following format:
# DIR=/var/run/wpa_supplicant GROUP=wheel
# DIR=/var/run/wpa_supplicant GROUP=0
# (group can be either group name or gid)
#
ctrl_interface=DIR=/data/misc/wifi/wpa_supplicant GROUP=wifi
# IEEE 802.1X/EAPOL version
# wpa_supplicant is implemented based on IEEE Std 802.1X-2004 which defines
# EAPOL version 2. However, there are many APs that do not handle the new
# version number correctly (they seem to drop the frames completely). In order
# to make wpa_supplicant interoperate with these APs, the version number is set
# to 1 by default. This configuration value can be used to set it to the new
# version (2).
# eapol_version=1
# AP scanning/selection
# By default, wpa_supplicant requests driver to perform AP scanning and then
# uses the scan results to select a suitable AP. Another alternative is to
# allow the driver to take care of AP scanning and selection and use
# wpa_supplicant just to process EAPOL frames based on IEEE 802.11 association
# information from the driver.
# 1: wpa_supplicant initiates scanning and AP selection
# 0: driver takes care of scanning, AP selection, and IEEE 802.11 association
# parameters (e.g., WPA IE generation); this mode can also be used with
# non-WPA drivers when using IEEE 802.1X mode; do not try to associate with
# APs (i.e., external program needs to control association). This mode must
# also be used when using wired Ethernet drivers.
# 2: like 0, but associate with APs using security policy and SSID (but not
# BSSID); this can be used, e.g., with ndiswrapper and NDIS drivers to
# enable operation with hidden SSIDs and optimized roaming; in this mode,
# the network blocks in the configuration file are tried one by one until
# the driver reports successful association; each network block should have
# explicit security policy (i.e., only one option in the lists) for
# key_mgmt, pairwise, group, proto variables
# ap_scan=1
# EAP fast re-authentication
# By default, fast re-authentication is enabled for all EAP methods that
# support it. This variable can be used to disable fast re-authentication.
# Normally, there is no need to disable this.
# fast_reauth=1
# Driver interface parameters
# This field can be used to configure arbitrary driver interace parameters. The
# format is specific to the selected driver interface. This field is not used
# in most cases.
#driver_param="field=value"
# Maximum lifetime for PMKSA in seconds; default 43200
#dot11RSNAConfigPMKLifetime=43200
# Threshold for reauthentication (percentage of PMK lifetime); default 70
#dot11RSNAConfigPMKReauthThreshold=70
# Timeout for security association negotiation in seconds; default 60
#dot11RSNAConfigSATimeout=60
Sorry for my bad english.
I very needed internet in ad-hoc mode. So, anybody help me ?
wifi ad hoc is not supported by zte blade official rom even by changing wpa_supplicant this will crash your wifi.............
maybe the modded supplicant is not compatible with stock rom..........
change your rom to any cm7 and than change its wpa_supplicant to /system/bin than only the wifi adhoc will work
I am trying to edit keylayout for my PS3 bluetooth keyboard in my HTC HD2 Android 4.0.4 using tytung NexusHD2 ROM v2.9a
due to the Fn keys are simulate PS3 controler buttoms, i want to set the Fn+up, down, left, right as pgup, pgdn, home, end
i get the scancode as the code below using Testkey.apk
i write a file "Vendor_054c_Product_05af" according to my bluetooth keyboard in /proc/bus/input/devices
and i paste in /system/usr/keylayout and set permission -rw-r--r--
but it never works no matter i change
the keycode still catch the build-in Logitech, PS3 and XBOX controller keylayout
is anyone can help me out
Code:
# Copyright (C) 2011 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Sony Playstation(R)3 Bluetooth Wireless Keyboard with Pointing Stick
#
# key 0x124 DPAD_UP
# key 0x125 DPAD_RIGHT
# key 0x126 DPAD_DOWN
# key 0x127 DPAD_LEFT
key 0x124 PAGE_UP
key 0x125 MOVE_END
key 0x126 PAGE_DOWN
key 0x127 MOVE_HOME
# key 304 Square
# key 305 Cross
# key 306 Circle
# key 307 Triangle
# key 308 L1
# key 309 R1
# key 310 L2
# key 311 R2
# key 312 Select
# key 313 Start
# key 314 L3
# key 315 R3
# key 316 BUTTON_MODE
re
daviking222 said:
I am trying to edit keylayout for my PS3 bluetooth keyboard in my HTC HD2 Android 4.0.4 using tytung NexusHD2 ROM v2.9a
due to the Fn keys are simulate PS3 controler buttoms, i want to set the Fn+up, down, left, right as pgup, pgdn, home, end
i get the scancode as the code below using Testkey.apk
i write a file "Vendor_054c_Product_05af" according to my bluetooth keyboard in /proc/bus/input/devices
and i paste in /system/usr/keylayout and set permission -rw-r--r--
but it never works no matter i change
the keycode still catch the build-in Logitech, PS3 and XBOX controller keylayout
is anyone can help me out
Code:
# Copyright (C) 2011 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
# Sony Playstation(R)3 Bluetooth Wireless Keyboard with Pointing Stick
#
# key 0x124 DPAD_UP
# key 0x125 DPAD_RIGHT
# key 0x126 DPAD_DOWN
# key 0x127 DPAD_LEFT
key 0x124 PAGE_UP
key 0x125 MOVE_END
key 0x126 PAGE_DOWN
key 0x127 MOVE_HOME
# key 304 Square
# key 305 Cross
# key 306 Circle
# key 307 Triangle
# key 308 L1
# key 309 R1
# key 310 L2
# key 311 R2
# key 312 Select
# key 313 Start
# key 314 L3
# key 315 R3
# key 316 BUTTON_MODE
Click to expand...
Click to collapse
FpseCE
http://www.youtube.com/watch?v=mH_NBKtj0R8
This is my Vold , can someone help me so that i can use my sdcard as the internal memory?
# Copyright (c) 2011, The Linux Foundation. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of The Linux Foundation nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
# LGE_CHANGE For MTP
#[email protected] sdcard path change /mnt/sdcard/external_sd ->/storage/external_SD
#dev_mount sdcard2 /mnt/sdcard/external_sd auto /devices/platform/msm_sdcc.3/mmc_host
dev_mount sdcard2 /storage/external_SD auto /devices/platform/msm_sdcc.3/mmc_host
dev_mount sda /storage/USBstorage auto /devices/platform/msm_hsusb_host
dev_mount sdb /storage/USBstorage2 auto /devices/platform/msm_hsusb_host
dev_mount sdc /storage/USBstorage3 auto /devices/platform/msm_hsusb_host
dev_mount sdd /storage/USBstorage4 auto /devices/platform/msm_hsusb_host
dev_mount sde /storage/USBstorage5 auto /devices/platform/msm_hsusb_host
dev_mount sdf /storage/USBstorage6 auto /devices/platform/msm_hsusb_host
Hey guys, can anyone help me? I accidentally messed up my vold.fstab file and don't know what the original text was that I need to restore it to. Can someone just copy the text in the file and share it with me please? In case you don't know where to find it, its in system > etc > vold.fstab. You can open it as text with a root explorer. Thanks in advance!
silentshadow867 said:
Hey guys, can anyone help me? I accidentally messed up my vold.fstab file and don't know what the original text was that I need to restore it to. Can someone just copy the text in the file and share it with me please? In case you don't know where to find it, its in system > etc > vold.fstab. You can open it as text with a root explorer. Thanks in advance!
Click to expand...
Click to collapse
Code:
# Copyright (c) 2011, Code Aurora Forum. All rights reserved.
#
# Redistribution and use in source and binary forms, with or without
# modification, are permitted provided that the following conditions are
# met:
# * Redistributions of source code must retain the above copyright
# notice, this list of conditions and the following disclaimer.
# * Redistributions in binary form must reproduce the above
# copyright notice, this list of conditions and the following
# disclaimer in the documentation and/or other materials provided
# with the distribution.
# * Neither the name of Code Aurora Forum, Inc. nor the names of its
# contributors may be used to endorse or promote products derived
# from this software without specific prior written permission.
#
# THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESS OR IMPLIED
# WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
# MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT
# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS
# BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
# BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
# WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE
# OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN
# IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
dev_mount sdcard /storage/sdcard1 auto /devices/platform/msm_sdcc.3/mmc_host
dev_mount usbdisk_1.1.1 /storage/usbdisk_1.1.1 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1:1.0
dev_mount usbdisk_1.1 /storage/usbdisk_1.1 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.1
dev_mount usbdisk_1.2 /storage/usbdisk_1.2 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.2
dev_mount usbdisk_1.3 /storage/usbdisk_1.3 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.3
dev_mount usbdisk_1.4 /storage/usbdisk_1.4 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.4
dev_mount usbdisk_1.5 /storage/usbdisk_1.5 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.5
dev_mount usbdisk_1.6 /storage/usbdisk_1.6 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.6
dev_mount usbdisk_1.7 /storage/usbdisk_1.7 auto /devices/platform/msm_hsusb_host/usb1/1-1/1-1.7
You are awesome, thank you!