[W-Project] Install CWM on Walton Primo C2

August 15, 2014, 12:58 pm

≫ Next: [GUIDE] Convert Any Phone/Tablet into KaliPwn Phone/Tablet

≪ Previous: Mtk6575 repartition solution

Wlcome back.... :)

How is going on with ur Walton Primo C2??
Have got rooted??
Sure....Ur set is rooted. :p

Facebbok Page :

Its time to install cwm on Primo C2
Lets Start:::::::::::::;

Download all files: CWM+Flashtools+ScatterFile.zip - 12.87 MB

1. Download and extract with winrar
2. Open Flastools folder
3. Open flashtool.exe

4. Click on Scatter loading

5.Click on recovery

6.Select the recovery from CWM Folder

7.Click Download

8.Click Yes

9.Turn Off ur smartphone

10.Remove battery

11.Plug it into PC via usb cable

12.You will watch these:

13.Put on battery in ur smartphone
14.Press Power+Volume Up button at same time
15.Hurraaaa.....U can see custom recovery!!!

If u got help, Do not forget to press "Thanks" button :good:

↧

[GUIDE] Convert Any Phone/Tablet into KaliPwn Phone/Tablet

August 19, 2014, 10:45 am

≫ Next: [Scripts support init.d] Developer something that should take into account

≪ Previous: [W-Project] Install CWM on Walton Primo C2

****i am not responsible for your phone or anything you do with aircrack-ng

*this guide is based on nexus 5 you can substitute it with any phone/tablet(with otg support) with this gude

if your a noob or expert just ask will guide you

------------------------------------------------------------------------------------------------
Things You Need
------------------------------------------------------------------------------------------------
1) any phone with otg support [used=Nexus 5 (rooted)]
2) OTG Cable
3) any usb wifi [used=TP-LINK TL-WN722N](if you have others let me know ill add it to the guide)
4) Ubuntu (to compile kernel)
5) if you need it for other device or compile kernel for other usb wifi device just let me know i will guide you thru

------------------------------------------------------------------------------------------------

PART A
(Compiling Kernel)

------------------------------------------------------------------------------------------------

Setting up your ubuntu machine

Code:

$ sudo apt-get update

Code:

$ sudo apt-get install oracle-java6-installer

Code:

$ sudo apt-get install git gnupg ccache lzop flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32bz2-1.0 lib32ncurses5-dev x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z1-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc libreadline6-dev lib32readline-gplv2-dev libncurses5-dev bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev squashfs-tools pngcrush schedtool dpkg-dev

Code:

$ sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so

Code:

git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/

create a file /etc/udev/rules.d/51-android.rules (as the root user)
copy paste the below code and save

Code:

# adb protocol on passion (Nexus One)

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="<username>"

# fastboot protocol on passion (Nexus One)

SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="<username>"

# adb protocol on crespo/crespo4g (Nexus S)

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="<username>"

# fastboot protocol on crespo/crespo4g (Nexus S)

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="<username>"

# adb protocol on stingray/wingray (Xoom)

SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="<username>"

# fastboot protocol on stingray/wingray (Xoom)

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="<username>"

# adb protocol on maguro/toro (Galaxy Nexus)

SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>"

# fastboot protocol on maguro/toro (Galaxy Nexus)

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="<username>"

# adb protocol on panda (PandaBoard)

SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="<username>"

# adb protocol on panda (PandaBoard ES)

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="d002", MODE="0600", OWNER="<username>"

# fastboot protocol on panda (PandaBoard)

SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="<username>"

# usbboot protocol on panda (PandaBoard)

SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d00f", MODE="0600", OWNER="<username>"

# usbboot protocol on panda (PandaBoard ES)

SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d010", MODE="0600", OWNER="<username>"

# adb protocol on grouper/tilapia (Nexus 7)

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e42", MODE="0600", OWNER="<username>"

# fastboot protocol on grouper/tilapia (Nexus 7)

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e40", MODE="0600", OWNER="<username>"

# adb protocol on manta (Nexus 10)

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee2", MODE="0600", OWNER="<username>"

# fastboot protocol on manta (Nexus 10)

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4ee0", MODE="0600", OWNER="<username>"

<username> must be replaced by the actual username of the user who is authorized to access the phones over USB.

Setting correct paths

Code:

gedit android-path.sh

cope paste the code and save it

Code:

export CC=$(pwd)/arm-eabi-4.6/bin/arm-eabi-

export CROSS_COMPILE=$(pwd)/arm-eabi-4.6/bin/arm-eabi-



export ARCH=arm

export SUBARCH=arm



export PATH=$PATH:$(pwd)/andorid_boot_tools_bin

Make it executable and source to current terminal window.
(you need to source it to your current terminal window before you compile)

Code:

 $ chmod +x android-path.sh

$ source android-path.sh

Download Source (any kernel source can be used)
1. HTC
2. Samsung
3. LG
4. Sony
5. Nexus devices

using nexus 5 andoid kernel source

Code:





$ git clone https://android.googlesource.com/kernel/msm.git

Code:

 

$ cd msm/

$ git branch -a

$ git checkout origin/android-msm-hammerhead-3.4-kitkat-mr2

Code:

$ make hammerhead_defconfig

$ make menuconfig

Adding required drivers
this is only for TP-LINK_TL-WN722N (if you have other device let me know)
quick look in wikidev will tell you that TP-LINK TL-WN722N uses ath9k_htc drivers

Enabling ath9k drivers in kernel
To enable ath9k, you must first enable mac80211 through make menuconfig when compiling your kernel. If you do not know what this means then please learn to compile kernels or rely on your Linux distribution's kernel. Below are the options you need to enable ath9k through make menuconfig.

Code:

Networking  --->

  Wireless  --->

    < * > Improved wireless configuration API

    < * > Generic IEEE 802.11 Networking Stack (mac80211)

You can then enable ath9k in the kernel configuration under

Code:

Device Drivers  --->[*] Network device support  --->

        Wireless LAN  --->

          Atheros Wireless Cards ---->

            < * >   Atheros 802.11n wireless cards support

            < * >   Atheros HTC based wireless card support

save and exit menuconfig
check in your .config file if you have them enable(its a hidden file)

Code:

CONFIG_ATH_COMMON=y

CONFIG_ATH9K_HW=y

CONFIG_ATH9K_COMMON=y

CONFIG_ATH9K_HTC=y

now your ready to compile

Code:

make -j4

this will take some time to compile

you should get something like this in the end

Code:

Kernel: arch/arm/boot/zImage-dtb is ready

now you need to get a boot.img from any {your device} rom and place it in boot_img (create this folder where you earlier downloaded the toolchain and the kernel)

Code:

$ cd .. # if you was in msm directory

$ git clone https://github.com/pbatard/bootimg-tools.git

$ cd bootimg-tools/

$ make

$ cd cpio/

$ gcc mkbootfs.c  -o mkbootfs -I../include

$ cd ../..

$ mkdir andorid_boot_tools_bin

$ cd andorid_boot_tools_bin/

$ cp ../bootimg-tools/mkbootimg/mkbootimg .

$ cp ../bootimg-tools/mkbootimg/unmkbootimg .

$ cp ../bootimg-tools/cpio/mkbootfs .

$ cd ..

time to create your own boot

Code:

$ unmkbootimg -i boot_img/boot.img

$ cp msm/arch/arm/boot/zImage-dtb kernel

$ mkbootimg --base 0 --pagesize 2048 --kernel_offset 0x00008000 --ramdisk_offset 0x02900000 --second_offset 0x00f00000 --tags_offset 0x02700000 --cmdline 'console=ttyHSL0,115200,n8 androidboot.hardware=hammerhead  user_debug=31 maxcpus=2 msm_watchdog_v2.enable=1' --kernel kernel --ramdisk ramdisk.cpio.gz -o boot.img

install the boot.img to your phone (this wont flash the kernel, it will temporarily boot with this kernel, after you restart you will go back to what ever kernel you had before
(this is for nexus 5 it might work for others also)

Code:

$ adb reboot bootloader

$ sudo fastboot boot boot.img

------------------------------------------------------------------------------------------------

PART B
(setting up your phone)

------------------------------------------------------------------------------------------------

this is only for TP-LINK_TL-WN722N (if you have other device let me know)

download the firmware files here
1. htc_7010.fw
2. htc_9271.fw

copy them to your phone
use a file manager with root to copy both of them to /system/etc/firmware/

install Linux deploy on your phone
fire up linux deploy and go to properties-->Distribution and select kali linux
installation path set to /sdcard/linux.img
hit the install button

after installation click start button

start your favorite ssh program and happy aircrack-ng
(SH credentials are “android” for the username (configured via Linux Deploy) and “changeme” as the password.)

↧

[Scripts support init.d] Developer something that should take into account

August 19, 2014, 12:50 pm

≫ Next: MTD porting for Samsung Galaxy MSM7x27 series

≪ Previous: [GUIDE] Convert Any Phone/Tablet into KaliPwn Phone/Tablet

Introduction:
Developers and users in general hope that this information will be of help and understand how important this issue is
to develop the script according assume smartphone

Warning:
In most of the roms we can find a folder called init.d where you will find a variety of script that are optimizations for
the system itself there is only a detail as you may have noticed the scripts that are used are the same as those used in xperia x8,
type, among other variety as well as file modifications Encourage build.prop only device in this topic we will learn to notice how
the scripts are built and running as smoothly as possible.

Because I say that the scripts are the same? Simple is good since I have seen your code and have compared with the terminals I have
the code and some things should not be there just do not serve the terminal to Encourage and lagee much scripts are not universal
trust me

Some things like values?? optimzacion kernel (sysctl) such xperia L example of code are these:
-kernel= kernel.auto_msgmni = 0
-vm= vm.block_dump = 0
-fs= fs.aio-max-nr = 65536
-net= net.core.dev_weight = 64

note: and so on the more codes each terminal should be just the scripts for each terminal

some files should not come optimizations init.d support
host file this file is normally used to block advertising terminal does support that file in init.d wonder?
comes as other files named sqlite3 that is used to access the root does support init.d ???? now the other file called zipalign that is
normally used to sign apk applications to sign in support init.d ???

the init.d support should be different for each terminal is different because each firmware should not be general
important: it is my view and my knower that is also something constructive

1.-Basic commands and file handling
command: #!/bin/bash
information: +-/home: User home directories

command cd
command to change directory.

command ls
list contents of directories

command cp
copy files/directories

command rm
delete files/directories

command mkdir
create directories

command sysctl
Configure kernel parameters at runtime

2.-All configurations such scripts
/system/etc

3.- startup file
path of the file to be started: /system/etc/init.d/init

example code:
Seed file support init.d: /system/etc/udev/rules.d/init.rules

KERNEL=="mount*", ACTION=="change", SUBSYSTEM=="platform", RUN+="/system/etc/init.d/init"

5.- permissions script
chmod 755

6.- Example of script
#!/bin/bash
# This is a comment
echo "Hello world"

7.- Conditional if o if-else
example

code if:
if value
then
values
fi

code if-else:
if value
then
values
else

8.- Code if o if-else
example:
-a file: True if the file exists
-e file: The same
-b file: True if file exists and has a special block
-c file: True if file exists and is of type character
-d file: True if file exists and is a directory
-f file: True if file exists and is a common file
-g file: True if file exists and its set bit in September GroupID
-h file: True if file exists and is a symbolic link
-k file: True if file exists and its sticky bit set
-p file: True if file exists and is a named pipe
-r file: True if file exists and is readable
-s file: True if file exists and is greater than 0
-u file: True if file exists and has the setuid bit set
-w file: True if file exists and is writable
-x file: True if file exists and has execute permissions
-O file: True if file exists and is nuetro EUID user
-G file: True if file exists and is in our group EGID
-L file: True if file exists and is a symbolic link
-S file: True if file exists and is a socket
-N file: True if file exists and has changed since the last reading

9.- Checks
example:
if [ ! -e $1 ]
then
echo “No”
fi

10.- the main thing you have to develop the script support init.d

Note: In the coming days I will do a better, more detailed documentation :fingers-crossed:

↧

MTD porting for Samsung Galaxy MSM7x27 series

August 19, 2014, 4:01 pm

≫ Next: [Q] Samsung Galaxy Core 2 Dual SIM SM-G355H

≪ Previous: [Scripts support init.d] Developer something that should take into account

MTD porting for Samsung Galaxy MSM7x27 series

I'm trying to restore this uncompleted project.

Original thread introduction by psyke83:

Quote:

Yesterday I discovered a very interesting source release from Samsung: GT-S5830G_GB_Opensource.zip

Normally, there is a shared Samsung source release for the msm7k range of devices (Ace, Mini, Callisto, Beni, Gio; there is also partial support included for my GT-I5500/Europa, but I adapted the source to properly support my phone). All of these devices usually depend on Samsung's proprietary FSR (Flex Sector Remapper) drivers in order to access the flash memory, which are taken from the stock ROMs, but our dependence on this driver locks us into the 2.6.35 kernel since we don't have access to the driver source.

The new source that I found for the GT-S5830G model, however, appears to contain modifications for the purpose of transitioning from Samsung's proprietary FSR driver to the open source MTD (via msm_nand) driver. If this can work correctly, using this driver would be much preferred over the proprietary Samsung stuff.

Here's the source that I uploaded to github: https://github.com/psyke83/android_k.../tree/purenand

Some observations that I have made, keeping in mind that I'm testing on my GT-I5500:

There are two separate configs for the cooper rev03 (Galaxy Ace): the standard defconfig that uses fsr/rfs, and a "purenand" config that uses the mtd/yaffs2 drivers instead of fsr/rfs. In other words, it's using the open drivers for flash access. Here is the diff: https://gist.github.com/3365123
The dpram driver (Samsung's driver for communication with baseband, used by RIL) is patched to support MTD instead of BML when the proper config is set.
The drivers/mtd/devices/msm_nand.c driver is modified by Samsung, but they applied their patches to an older revision of msm_nand.c from Froyo. Here is the diff when comparing this file vs the Froyo revision, so you can see more clearly the changes: https://gist.github.com/3365161
By default, the msm_nand.c driver causes the kernel to hang on my device (this is true for both this source and the older 2.6.35 Samsung source not based on purenand). I have isolated the hang to the flash_onfi_probe function.
As you can see here, Samsung added code to bypass this function on the Cooper board, and use the secondary detection method only. If I include my board to this ifdef block, it solves the issue with the kernel hanging on my device. I also need to patch some checks in the onenand detection, because the driver explicitly looks for onenand devices with a device_id of 0x40 and num_of_buffers as 0x201, but the chip on the GT-I5500 is different (device_id is 0x50, num_of_buffers is 0x101). This patch solves these problems: https://gist.github.com/3365222
Here is a dmesg log from my device after patching the code: https://gist.github.com/3360727. For comparison purposes, look at the block mapping that the fsr driver reports for my device when using the BML mapping: https://github.com/psyke83/android_d...dConfig.mk#L53
As you can see, the partitions names and order detection is correct for the msm_nand driver, but the address mappings are exactly half of what they are supposed to be (e.g. the first partition, mibib, should range from 0x00000000-0x00180000, but the mtd driver detects the memory range as 0x00000000-0x000C0000.
If I try to perform a "nandump -f /sdcard/cache.img /dev/mtd/mtd13", there are no obvious errors in the dmesg log, but the tool will dump the cache partition until the sd card becomes full (over 300mb in my case, but the real /cache partition is only 25MB), and will then output "nanddump: short write". The resulting dump will be filled with 0xFF when examined with a hex editor (even though I'm sure that the /cache partition is not blank in reality).

These are my findings so far. I'd appreciate any kernel hackers to help me out. If we can crack this problem and get open onenand drivers working, then our devices will no longer be locked to any specific kernel release.

Actual status:
galaxy5 (europa): mtd can read/write partitions (via dd). But CM doesn't seem to work completely. All tests done by psyke83:

gio (gio): mtd doesn't seem to be able to dump partitions correctly (perhaps a problem in onenand_read). All tests done by erikcas
http://madteam.co/forum/index.php?to...84130#msg84130
Furthermore erikcas managed to mount a partition but its size was reported to 0. Probably a badblock problem -> onenand_read

ace (cooper): mtd can't dump parititons correctly. All tests done by me!
More info in next post.

Last patch: https://gist.github.com/psyke83/6420048
You can apply this again 2.6.35 (purenand branch) or (with minor changes) again 3.0.8/3.0.31

psyke83 and erikcas stopped development and original thread seem abandoned, I hope that here in xda somebody can help me to restore this!

↧

[Q] Samsung Galaxy Core 2 Dual SIM SM-G355H

August 20, 2014, 1:15 pm

≫ Next: [APP][4.0+] Nokia Z Launcher 0.2.0

≪ Previous: MTD porting for Samsung Galaxy MSM7x27 series

I have tried almost all tools (towelroot, Vroot, kingo root, oneclickroot etc.) to get root access of my samsung galaxy core 2 G355H phone with no success.
My phone has android version 4.4.2.
Please help me somebody.

↧

[APP][4.0+] Nokia Z Launcher 0.2.0

August 21, 2014, 12:48 pm

≫ Next: CS918-how to make tablet optimized UI apps recognize it as a tablet in landscape mode

≪ Previous: [Q] Samsung Galaxy Core 2 Dual SIM SM-G355H

I finally made it, the Nokia Z Launcher 0.2.0 is "cracked". :D

After a few hours of looking through the obfuscated smali code I removed the root check and the Nokia log-in requirements. :eek:

Thanks to Dhiraj for posting the original apk file. http://forum.xda-developers.com/show...2&postcount=43

Attached Images

	main.jpg - [Click for QR Code] (193.0 KB)
	app_drawer.jpg - [Click for QR Code] (202.3 KB)
	settings.jpg - [Click for QR Code] (129.0 KB)
	about.jpg - [Click for QR Code] (204.1 KB)

Attached Files

Z Launcher-com.nokia.z-1-v0.2.0.apk - [Click for QR Code] (5.96 MB)

↧

CS918-how to make tablet optimized UI apps recognize it as a tablet in landscape mode

August 21, 2014, 9:38 pm

≫ Next: Ques. Blackmart

≪ Previous: [APP][4.0+] Nokia Z Launcher 0.2.0

Just got the box (with 2GB RAM and bluetooth) and so far happy with it.

I used to use UHost 1 which is one of the best Android TV stick at that time; but feel too slow now.

On Uhost, all Android apps which have tablet optimized UI will display on my TV as if my TV is a tablet in landscape mode. For example, Twitter app will display two panes (left and right), instead of one as shown on mobile phone display.

On CS918, it does not dislay the tablet UI landscape mode as I mentioned above; it displays more like a big wide mobile phone. How could I tweak CS918 to display like a tablet wth tablet UI on landscape mode?

Thanks.

↧

Ques. Blackmart

August 24, 2014, 2:51 am

≫ Next: Change 2G to 3G [common issue]

≪ Previous: CS918-how to make tablet optimized UI apps recognize it as a tablet in landscape mode

Application name blackmart what is condom was gone down 1 or 3 days the server is gone down this application is very important to me please do something and say why this blackmart application is not work please developers of xda please help me i am so much depressed please do something

↧

Change 2G to 3G [common issue]

August 24, 2014, 12:54 pm

≫ Next: [RASPBERRY PI] Android-Tools binaries (ADB/Fastboot/fsutils)

≪ Previous: Ques. Blackmart

Hey most of user posting ..
This issue in most of android devices

Issue:-
u have 3G data pack and data connection showing 2G instead of 3G

Solution :-
1.Download mobileuncle tool from playstore.
2.Open it.
3.go to engineermode
4.click on phone information
5.now last step switch gsm only,gsm auto,etc to wcdma only ...

Its done .. Enjoy 3G

This guide also work for 4G
just switch 2G/3G to LTE

enjoy 4G..

Presss thanks if i help u

↧

[RASPBERRY PI] Android-Tools binaries (ADB/Fastboot/fsutils)

August 24, 2014, 2:30 pm

≫ Next: [GUIDE] [BIN] Busybox 1.23.0 Snapshot and Building On Android (from Ubuntu chroot..)

≪ Previous: Change 2G to 3G [common issue]

Hi all,

I don't think we have a Rasp-pi forum on here, so Im posting here. Also, such a forum would probably be for those wishing to run Android on their Raspberry Pi. This thread is for those who are using their Pi for android development

I had a hard time finding android-tools packages for the debian "wheezy" build that comes with the Pi, so I back-ported them and built some binaries, attached below.

This is useful for people who plan to use their Raspberry Pi for some sort of android tinker. ing, but don't plan on doing any actual development (and hence will not need the full SDK). These should save some time. My first contribution to XDA, so enjoy!

Mirror available via PM.

MD5 Hash: AB22B0251A8A1B1209EF1342167C1E09
SHA1: FA8113237AF1C8F64FA74BF800A866A7B681CD2A

INSTALLATION
Download, cd to the directory you downloaded,

Code:

tar zxvf android-tools-pi.tar.gz && cd android-tools-pi

There should be three binaries in the directory.
Install with

Code:

dpkg -i android-tools-*.deb

Best,

amk

EDIT: Whoops.. if a mod could move this to the Pi forums I'd appreciate it. Thanks in advance.

Attached Files

android-tools-pi.tar.gz - [Click for QR Code] (548.7 KB)

↧

[GUIDE] [BIN] Busybox 1.23.0 Snapshot and Building On Android (from Ubuntu chroot..)

August 24, 2014, 7:35 pm

≫ Next: [URGENT] Help needed please help!

≪ Previous: [RASPBERRY PI] Android-Tools binaries (ADB/Fastboot/fsutils)

About Busybox: busybox.net/about.html
More on Busybox: busybox.net

This is just for anyone who wants to try, and especially those without access to a PC.

Things we'll need besides your phone:
- "Android Terminal Emulator" app
- "Complete Linux Installer" app
-internet/wifi
- latest "busybox" source

1) We need to get Ubuntu or Debian booted for a sufficient build environment. I've used both on Android but I like the better stocked terminal in the Ubuntu images. I used the app "Complete Linux Installer" which is free and works beautifully, very simple and easy. In the app you want to follow the short instructions to download an Ubuntu image, rename it to ubuntu.img, and place it in a folder named ubuntu in /sdcard. Then hit menu in the app and click the terminal screen icon that says "Launch". An Ubuntu terminal will now open in Android Terminal Emulator. Super quick and easy.

2) Let's download GCC and ncurses-devel (libncurses5-dev) as some crucial build environment tools.

Code:

apt-get install -y gcc libncurses5-dev

3) Now the cool thing about this chroot Ubuntu environment is that we still have access to the sdcard to transfer files between Android environment and the chroot jail. Extract your downloaded busybox source to your Ubuntu home with something like:

Code:

cd

tar -xf /sdcard/Download/busybox*bz2

cd busybox*

4) Now we can build busybox statically. The first thing we do is generate a Makefile by running "make" with a "defconfig" (default configuration file) Usually you will run "make configure" with other programs, but busybox compiles more like a kernel, so it uses a defconfig which has a huge checklist of options.

Busybox source already comes with a couple defconfigs specifically for Android in the folder configs/ from the root of the source directory. (After successfully compiling busybox, we can go back and customize one; this entails that for each "CONFIG ..." line we see, we can uncomment it and mark it "y" or "n" to configure some option... This can be more easily done from a terminal busybox menu interface with "make menuconfig". You just need to crank font down to 7 or use telnet/ssh) For now we'll copy a defconfig already made to the root of the source directory for use.

Code:

cp configs/android_defconfig .

make defconfig

If all goes well, we now have a Makefile and are ready to compile:

Code:

LDFLAGS=-static make

Let "make" crank out the binary for a couple minutes. The extra variable we set before make is an environment variable to compile statically. When compiling is complete we'll have a few different busybox binaries at the root of the source directory. We use the one named "busybox".

5) Now let's copy it to /system/usr/bin to install for test usage.

Code:

cp ./busybox /sdcard

(Open a new terminal tab to get into Android Environment)

sysrw

mkdir -p /system/usr/bin

cp -f /sdcard/busybox /system/usr/bin

chmod 0555 /system/usr/bin/busybox

/system/usr/bin/busybox --install -s /system/usr/bin

sysro

.. and done. Run some scripts and enjoy your static busybox!

:
--------------- --------------- --------------- ---------------
:

***** Attached is a busybox static binary (v1.23.0 August 2014 snapshot, 374 applets included!, 1.37MB size) *****
Since it's up-to-date it has some nice extras most people haven't seen like a "-I" option for xargs! Yes, that is correct, busybox xargs has its testicles back.

Code:

e.g.

> echo Hello | xargs -I{} echo {} world!

Attached Files

busybox.zip - [Click for QR Code] (988.1 KB)

↧

[URGENT] Help needed please help!

August 25, 2014, 2:21 am

≫ Next: [Q] BrickReceiver

≪ Previous: [GUIDE] [BIN] Busybox 1.23.0 Snapshot and Building On Android (from Ubuntu chroot..)

Hello Guys :)
I have made a custom ROM for my device Karbonn A8. It gets installed all right but when I boot it up after the splash screen it gets stuck on a blank screen (even bootanimation can't load). I have to manually remove the battery and restart the phone.
I am thinking it is the issue of kernel. When I go to my about phone section I see this written (in attachment) that it is patched and I also heard somewhere that ROM is patched and custom ROM can't be installed. I don't believe that as Android is a aosp and if source codes weren't there then how can someone compile a CWMR for it already!.!
I have extracted my kernel file and found all neccessary information like boot path bla bla..
I want that I can create custom kernel but Karbonn hasn't released it's kernel source(as I heard and googled) . Luckily I have found device working on this board they are symphony w68 and K-Touch w68 phone, which makes me think that probably I can get source codes..
I also want to compile CWMR for my device but I have no clue of where and how to begin :(
Can please someone help me I know my ROM is correct and 100% working.
Please any one help me :( :crying:
Need help urgently :(

Attached Thumbnails

Click image for larger version

Name: Screenshot_2014-08-25-14-01-56.png
Views: N/A
Size: 87.6 KB
ID: 2911216

↧

[Q] BrickReceiver

August 25, 2014, 4:31 am

≫ Next: [URGENT] Help needed please help!

≪ Previous: [URGENT] Help needed please help!

Hello everyone!

I really tried to find an answer for my question all over the internet but havent had any success. People who browsed android source have probably heard about this BrickReceiver class. Now, i know that Jean-Baptiste from google said that its a peace of dead code but my question is does anyone know what happens when you execute Systemservice.start("brick")? I remember testing that on emulator on a ROM i built for testing and i think i was not able to boot it back again once i executed that command, but im not sure. Anyone else tested this or knows what would happen if executed?

Thank you in advance

↧

[URGENT] Help needed please help!

August 25, 2014, 4:58 am

≫ Next: [Guide][Simple]Make your own update patch with Omega rom flasher...

≪ Previous: [Q] BrickReceiver

Hello Guys :)
I have made a custom ROM for my device Karbonn A8. It gets installed all right but when I boot it up after the splash screen it gets stuck on a blank screen (even bootanimation can't load). I have to manually remove the battery and restart the phone.
I am thinking it is the issue of kernel. When I go to my about phone section I see this written (in attachment) that it is patched and I also heard somewhere that ROM is patched and custom ROM can't be installed. I don't believe that as Android is a aosp and if source codes weren't there then how can someone compile a CWMR for it already.! I already have a CWM recovery for my device but I want to compile it on my own.
I have extracted my kernel file and found all neccessary information like boot path blah blah...
I want that I can create custom kernel but Karbonn hasn't released it's kernel source(as I heard and googled) . Luckily I have found device working on this board they are symphony w68 and K-Touch w68 phone, which makes me think that probably I can get source codes..
I also want to compile CWMR for my device but I have no clue of where and how to begin :(
Can please someone help me I know my ROM is correct and 100% working.
Please any one help me :( :crying:
Need help urgently :(
My only device please help :(

↧

[Guide][Simple]Make your own update patch with Omega rom flasher...

August 26, 2014, 3:25 am

≫ Next: [[Update patch]] Mini Cayno "X" 2 for Symphony Xplorer W68

≪ Previous: [URGENT] Help needed please help!

Hi guys...
Recently i had worked in a project (Mini Cayno X 2 link -> http://forum.xda-developers.com/andr...phony-t2858833 ..
it was a update patch for stock rom...so many buddy ask me in FB that how can i make one update patch for my rom?!!
But due to being busy i cant replay them and now i am free and try to write a small tutorial about this...i hope you will enjoy it... ;) and this is my frist tutorial in XDA... :D

Frist its not for Developer :D its for newbie modder who dont know this method... :D

Ok lets start.... :)

________________________________

Today i am going to tell you a new and uncommon way to make your own update patch...I think everybody knows about Villain rom flasher or Vrtheme...its really a good rom flasher...and you can make your own modpack with this easily...but i dont talk about this...beacuse there are a lot of guide in Xda about this...

Now i am going to tell you about Omegadorid rom flasher... This is an "Universal Flasher Tools" like villain rom flasher...
This flasher was made by JRsoft & Intronauta...
And more info and updates about "VillainTheme System" here:
(http://forum.xda-developers.com/show....php?t=1207017)

________________________________

Now i am going to how can you make your own update pack... :D

Frist for any Error or brick i am not responsible...

________________________________

Now requirments ->

1.Good file manegar or Root ecplorer...
2.good image editor like pixeler express or pic say pro...
3.Simple and common knowledge in udate script...
4.and free mind... :)

________________________________

Now download this omega flasher uploaded by Me...beacuse i lost the main thered link... :(

link -> ( http://www.mediafire.com/?pks4i2nx3w9l6d1 ) (Size: 2 mb)

After downloading make sure that what you want to add in your update patch...like i wants to add some nessesary apps,themes and some brinaries...

After decieding extract the zip in a new folder...like i extracted it in a new folder named new projects... :D

then you will see some folder like thats ->

1.META_INF,
2.MORPH,
3.tools,
4.XTRAS,
5.mod.config,
6.Reed me.txt...

Ok now frist lets talk about meta inf...i think everybody know this folder...and you must have knowladge about this folder...if you dont have then see this tutorial -> ( http://forum.xda-developers.com/show....php?t=1931585) (dont forget to say thanks to pitchblack5691 :D )

Now MORPH folder...
this is the main folder...here you can put your modded png files what you wanted to add in your apps...i will talk about it lettar...

then tools folder...in this folder you will see some files...dont touch them...this is the main files of your update pack...

then XTRAS...in this folder you can see some folder like system,sdcard,data etc etc...
if you wants to add somethings like apps in system folder then drop your apps in XTRAS/system/app..you can add fonts,new boot animations,modded build.prop and brinaries too...i will talk about this latter...

Now mod.config...This string will be added to build.prop for identify the
version or author of the mod and will be visible in
Settings - >About. Please avoid to use the character "=" into
the string.

now About readme.txt...here you will find somethings like how use this flasher etc etc...

________________________________

All done...now start making modpack.... :D.Its very easy...

Put in "/XTRAS" folder files that you want to add recreating
their full paths. Note that /XTRAS is equivalent to root path in
the internal memory:

e.g:

/XTRAS/system/etc/gps.conf
/XTRAS/sdcard/Wallpapers/MILF.jpeg
/XTRAS/data/app/Youtube.apk
/XTRAS/whateverfolder/whateverfile

you can also add system app here...just sing your app and drop it in XTRAS/system/app.you can add some app to xtras/data/app too...and in sdcard folder you can add some files like viper kernels or your lunchers downloaded themes.for example frist download all themes from your luncher settings.then search them in sdcard.if you found them,then copy the files with whole derectory like i found my themes here -> sdcard/xluncher/themes.So i copied xluncher folder and paste it to XTRAS/sdcard folder.By the same way you can add anithings in your sdcard just copy your file with whole derectory and paste it in xtras/sdcard...
i hope you understand about using XTRAS folders....

Now uses of MORPH folder...
>> Put in "/MORPH" folder your "morph themes". Note that /MORPH is
equivalent to root path in the internal memory and you must rename
folders like the apk but with extension instead the metamorph form
This process will only works in the following folders: /data/app,
/system/app and /system/framework.

e.g:

/MORPH/system/app/Settings.apk/res/drawable-hdpi/***.png
/MORPH/system/app/Settings.apk/classes.dex
/MORPH/system/framework/framework-res.apk/resources.arsc
/MORPH/data/app/****.apk/res/drawable-hdpi/**.png

you can add your modded png here...like i want to add new paltlogo...so frist i mod my platlogo.so that i extract my framwork_res by root explorer and find the paltlogo.then i found them and copy the derectory that where i found them like i found them in framwork_res/res/drawable nodpi.So i made my own logo and renamed them as same as in my stock framwork_res like platlogo.png and put them in the same derectory where i found them in stock framwork_res...like MORPH/system/framwork/framwork_res/res/drawable nodpi...done...now you add another pngs in the same way...but dont forget to renamed your pngs in same name as the main pngs...i hope you understand what i say....now your theming has been done!

>>but It's very important that you take a look to MOD.config file to
enable or disable features a/or set special commands if you need
it, i.e for setup your sdcard layout used in your recovery if you
get sdcard errors, set a mod name visible in Settings, etc..

>>ok now create zip of your updatepatch and Flash and enjoy!! :D

Having problem with update script?!!See my script -> ( http://www.mediafire.com/view/?dl1mta6j8t82w8u ) (Size: 3 kb)

######################Some KNOWN ERRORS ###############################

>>If you get (Status 0) error flashing, you need an update-binary
specific for your terminal. You must look for and extract the
"/META-INF/com/google/android/update-binary" file inside a zip
compatible with your terminal and replace it in the same path into
the UFT. You also can consider to replace the whole META-INF folder
in the MOD with the other compatible, except the updater-script!!

>>Please, report us errors if you get!!...

N.B ->to add somethings like brinaries/fonts/apps data/etc etc you must need to set permissions and Smyalink them...so,Dont forget it and if dont know how to set permission or create Smyalink then dont try to add them.in some devices all pngs are found in drawable-xhdpi/drawable-xxhdpi/drawable-mdpi...so you must need to know that in which folders your pngs are stored...for this just extract your systemui or framwork_res...then see thats where are all the pngs stored...for example:if you find all pngs in drawable-xhdpi then go to morph folder and renamed all drawable-hdpi folders to drawable-xhdpi... if you find all pngs in drawable-xxhdpi then go to morph folder and renamed all drawable-hdpi folders to drawable-xxhdpi...and if you dont understand anythings that i said then comment here...Thanks !

________________________________

Thanks for reading...
Happy modding and never stop customization.... ;)

Guide By:Me (MD.Shafikul)

________________________________

Credits: Main Credits:
>> "JRsoft" & "Intronauta" for this awesome flasher
>> "Villain Team" for the concept
>> "Stericson" for "Metamorph" system
>> "Core Utilities" for the tar binary
>> "Blades" for the 7z binary and libs
>> Builders of "zip" and "zipalign" binaries.
>> Testers, especially to:
"SuperCocoV6.5@htcmania", "lexullde@htcmania", "shayne77@xda",
"vvaleta@htcmania" and "eladios@htcmania".
>> "D.O.C@xda" for helping with the translations.

________________________________

if you like this post then dont forget to click on thanks botton.its will inspaierd me to write more guides.... :D

________________________________

About Me -> About Me:I am MD.Shafikul from Bangladesh and
a simple themer...
Current device:Symphony xplorer w68 god damn
mediatek...
Current rom:Xperia Honami v2
Current Project:Mini Cayno 'X' 2
Follow me in FB: Www.facebook.com/md.shafikul.125

________________________________

↧

[[Update patch]] Mini Cayno "X" 2 for Symphony Xplorer W68

August 26, 2014, 3:31 am

≫ Next: snapchat points, easy hack/workaround ,snapbomb

≪ Previous: [Guide][Simple]Make your own update patch with Omega rom flasher...

Hi gyus..
Welcome to Mini Cayno 'X' 2... :D
i had made many mistake in Mini Cayno X 1.but this time its super cool... :D i hope you will like it...
___________________

[Q] What are added?!
___________________

[Ans] I wants to make it Extreme...So i have added many Xteme things in it...Just see ->

1.Some Nice themes(With Omega rom flasher)...
2.New simple luncher with Awesome look...
3.Walkman with widget...
4.Pure audio Engain...
5.Viper with cool profiles...
6.Xposed,Notification toogles,app settings,greenefy with donation pack and many more...
7.New boot animations with xvipre boot sound...
8.Mini Xvipre's farmworks pngs...
9.And my own Cayno Styles pngs...
10.new notification icons...
11.New settings icons...
12.New Platlogo...
13.Dailpad background and settings background added...
14.Caller image changed...
15.Added many modded icons...

____________________

you can see screenshots here just download it... -> ( http://www.mediafire.com/?7y3sha6pxh06slv)

____________________

Requirments for installing ->

1.Its for Symphony Xplorer w68s stock or honami xperia rom users...
2.But you can try it in any Hdpi 480*800 regulations stock rom or xperia rom flashed devices...
3.If your luck is good then you wull able to use it... ;)
4.Any good recovery for flashing...
5.Letast busybox...Can download its from here ->( http://www.mediafire.com/?71qb2atcbbgu1ww) (Size: 900 kb)
6.At least needs a good luck... :D

_____________________

[Q]How to install?!!

_____________________

[Ans] just download it and go to recovery and flash it without wipe anythings...

_____________________

If you like this tgen dont forget to click on thanks botton... :D

____________________

[Q] where is the download link?!!

____________________

[Ans] opps forget to add this...here the link ->( http://www.mediafire.com/?a3j2gl97jwe1lrf) (Size: 84 mb)

___________________

Credits:

1.JRsoft & Intronauta for omega rom flasher...
2.Lovins team for Walkman...
3.(Modding my mind) for busybox flashable zip...
4.Mini Xvipre devs (X.O) for farmwork icons and new boot sound...
5.Jekko for his awesome Audio Engain...
6.All my friends in FB for suppoting me...
_________________

Do you want to make your own modpack like my MCX 2 ?!! ;)

If you wants then follow my Guide here ->( http://forum.xda-developers.com/andr...a-rom-t2858829)

(if you like my post then dont forget to click on thanks botton...)

_________________

About Me -> About Me:I am MD.Shafikul from Bangladesh and
a simple themer...
Current device:Symphony xplorer w68 god damn
mediatek...
Current rom:Xperia Honami v2
Current Project:Mini Cayno 'X' 2
Follow me in FB: Www.facebook.com/md.shafikul.125

_________________

By:Me MD.Shafikul... :P
Happy modding and never stop customization.... :D

↧

snapchat points, easy hack/workaround ,snapbomb

August 28, 2014, 1:33 am

≫ Next: samba compile issue

≪ Previous: [[Update patch]] Mini Cayno "X" 2 for Symphony Xplorer W68

i would like to bring a simple hack that would help you increase your snapchat score :)

just follow everything on the video ...

1- download FRep - Finger Replayer

2- open the app , get back on the homescreen , open snapchat

3- open snapchat , pull down the notification bar and click on tap to show console,

4- then start the recorder and then take a snap , select the person you want to bomb ..send it ..

5- turn screen off - this will turn off the recording

6 - now , all you need to do is input the number of times you want to bomb the person ...in the repeat tab..

7 - click on play ..

8- leave the rest on the app :P ;)

9- listen to abuses

should not be misused to harass anyone

you can use this to iritate your friends as well as increase your score, you will get 1000 points in half an hour :) if you set repeat to 1000!

enjoy the points ;)

↧

samba compile issue

August 29, 2014, 10:23 pm

≫ Next: [HowTo][INFO] Wifi Drop Caused by "Sign-in to WiFi Network" Notification [KitKat BUG]

≪ Previous: snapchat points, easy hack/workaround ,snapbomb

I'm compiling samba-3.6.22 for android with the sourcery arm-2010q1 compiler. The compile itself goes fine, but when I copy smbd to my device it's not recognized as a binary. I get the error

Code:

sh: ./smbd: No such file or directory

file under linux tells me:

Code:

smbd: ELF 32-bit LSB  shared object, ARM, EABI5 version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.16, not stripped

What am I overlooking?

↧

[HowTo][INFO] Wifi Drop Caused by "Sign-in to WiFi Network" Notification [KitKat BUG]

August 30, 2014, 1:06 am

≫ Next: [DEVS ONLY][BCM21553] Samsung Galaxy Pocket GT-S5300 (Cori) Development Discussion

≪ Previous: samba compile issue

Hi guys

when i updated my phone from 4.2.2 to 4.4.2 samsung roms, i faced with this bug and it drives me to crazy and certainly the madness. :crying:

i searched a lot but not found any solution, tried 2 days and finally got the solution.

whats the problem ?
When i connected my phone to my router [TP-Link] , the connection will stay for less than 2 minutes and show me this message!

Wifi Bug

Your device has been disconnected from this network. Your session has timed out.

after this, my wifi dropped and need to sign-in again, show me this message "Sign into Wi-Fi network"

and i found it caused by checking the wifi activity with Google servers, i don't know why Google should check our connectivity with their clients?!

and we should block the google client servers to pass this check process.

block this url:

Code:

clients3.google.com

----------------------------------------------

Solution A :
1- Goto your modem router configuration, type in your browser

Code:

192.168.1.1

input your username and password of your modem, defaults are :
username : admin
password : admin

if not works, read your modem's manual book. or check the behind info's label of your modem.

2- goto "Access Management" , and select the "Filter" tab.

do this settings:
Filter Type Selection = URL Filter
Active = Yes
URL Index = 1
URL = http://clients3.google.com/

3- select "Save" button and done.

your network will be fine! :good:

it should be like this

-----------------------------------------------------------------------------------------
Solution B , for who cant access to Modem settings, like free wifi services.

All actions will be done from your device.

1- goto Settings > WiFi settings
2- long-press on Connection
3- Select "Modify network config"
4- check the "Show advanced options" tick.
5- select proxy settings to Manual
6- proxy host name , input the value from 192.168.1.1 to 192.168.1.225
7- Proxy port = input one of them "8080" , "3128" , "80"
8- press the "Save".
9- turn wifi off and the On, you will not see the message ""Sign into Wi-Fi network"
10-now repeat the steps from 1 ~ 4
11- and revert back the proxy settings to "None", its Done.
12- you will be fine with this network.

------------------------------------------------------------------------------
I'll hope someone build the xposed module to bypass the "Sign into Wi-Fi network" process.

Don't forget to hit the Thanks! :D

In Persian Language , read here ,, برای فارسی زبان ها ، به اینجا مراجعه کنید

Attached Thumbnails

Click image for larger version

Name: wifi bug.png
Views: N/A
Size: 77.5 KB
ID: 2917820

Attached Images

wifi bug_fix.jpg - [Click for QR Code] (79.8 KB)

↧

[DEVS ONLY][BCM21553] Samsung Galaxy Pocket GT-S5300 (Cori) Development Discussion

September 2, 2014, 2:29 am

≫ Next: [Q] Add an application to start up - custom rom

≪ Previous: [HowTo][INFO] Wifi Drop Caused by "Sign-in to WiFi Network" Notification [KitKat BUG]

General informations:
This thread's aim is only to represent a central meeting and discussion point for BCM21553 developers and, in particular, for the open Kernel/ROM sources development for the Samsung Galaxy Pocket GT-S5300 (codenamed Cori).

Information for common users:
As already described in the previous section, if you are not a developer, please restrict your posts to the general discussion thread so that developers can maintain good communication. Every post that is not strictly respecting these rules will be reported to the forum moderators. Thanks for your understanding.

For any other BCM21553 device related question or information, please, use this thread as a reference point, instead:

[DEVS ONLY][BCM21553 series] CyanogenMod 11 for BCM21553 Development Discussion

↧

Latest Images