Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- KERNEL COMMANDS
- cp arch/arm/configs/tiamat_defconfig ./.config
- export CCOMPILER=${HOME}/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
- make ARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig
- make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
- cp arch/arm/configs/tiamat_defconfig ./.config
- export CCOMPILER=${HOME}/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
- make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
- BUILD CLOCKWORK RECOVERY IN CM REPO
- make clobber
- . build/envsetup.sh
- make -j4 otatools
- lunch full_stingray-eng
- build/tools/device/mkvendor.sh motorola stingray /home/bigrushdog/android/system/device/motorola/stingray/boot.img
- lunch full_stingray-eng
- make -j4 recoveryimage
- ---- Made recovery image -------- out/target/product/xoom/recovery.img
- make clobber (to clean up and start over)
- 9a35354a06e01d37035c4eaaacd2ee67
- HOW TO USE GIT
- REMOTES
- git remote add coolbho https://github.com/coolbho3k/Xoom-OC.git
- git remote add cyber https://github.com/cybertronic/Xoom-OC.git
- git remote add kcrudup https://github.com/kcrudup/Xoom-OC-CP.git
- git remote add tegra git://android.git.kernel.org/kernel/tegra.git
- git remote add common git://android.git.kernel.org/kernel/common.git
- git remote add aufs http://git.c3sl.ufpr.br/pub/scm/aufs/aufs2-standalone.git
- CLONE REPO
- git clone https://bigrushdog@github.com/Tiamat-AOSP/Xoom-OC.git
- CREATE NEW BRANCH
- git checkout -b bigrushdog-exp
- CHANGE BRANCH
- git checkout bigrushdog-exp
- VIEW ALL BRANCHES
- git branch -a
- ADD REMOTE SOURCE
- git remote add cyber https://cyber@github.com/Tiamat-AOSP/Xoom-OC.git
- REMOVE REMOTE BRANCH
- git push origin :cybertronic-android-tegra-2.6.36-honeycomb
- REMOVE LOCAL BRANCH
- git brand -D local_branch
- STAGE REMOTE FOR CHERRYPICKING
- git fetch cyber
- PULL REMOTE BRANCH
- git checkout cyber (change to desired local branch)
- git pull cyber cyber-branch (pull into desired branch)
- CHERRYPICK A COMMIT
- git cherry-pick <commit tag>
- FIX PULL ERRORS
- >>>>>>>>>>>>>>>>>>>>>>>>>>>
- HEAD
- then some code THIS IS BEFORE PULL, DELETE
- then
- =================
- some more code THIS IS AFTER PULL, KEEP
- <<<<<<<<<<<<<<<<<<<<<
- COMMIT
- git checkout desired-branch
- git add 'drop file here'
- git commit -m 'commit message here'
- git push origin desired-remote-branch
- MERGE PULL REQUEST
- git checkout -b cybertronic-android-tegra-2.6.36-honeycomb android-tegra-2.6.36-honeycomb
- git pull https://github.com/cybertronic/Xoom-OC.git android-tegra-2.6.36-honeycomb
- git checkout android-tegra-2.6.36-honeycomb
- git merge cybertronic-android-tegra-2.6.36-honeycomb
- git push origin android-tegra-2.6.36-honeycomb
- GIT STASH
- Use git stash when you want to record the current state of the working directory and the index, but want to go back to a clean working directory. The command saves your local modifications away and reverts the working directory to match the HEAD commit.
- The modifications stashed away by this command can be listed with git stash list, inspected with git stash show, and restored (potentially on top of a different commit) with git stash apply. Calling git stash without any arguments is equivalent to git stash save. A stash is by default listed as "WIP on branchname …", but you can give a more descriptive message on the command line when you create one.
- MASS STORAGE INTENT
- am start -n com.android.systemui/.usb.UsbStorageActivity
- APKTOOL
- apktool d -f -t <tag> app.apk app.apk-decoded
- apktool b app.apk-decoded
- apktool if framework-res.apk <tag>
- SYNC AND BUILD CM REPO
- cd ~/android/system/
- repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
- cd ~/android/system/
- repo sync
- cd ~/android/system/device/htc/supersonic/
- ./extract-files.sh
- cd ~/android/system/vendor/cyanogen/
- ./get-rommanager
- cd ~/android/system
- cp ./vendor/cyanogen/products/cyanogen_supersonic.mk ./buildspec.mk
- . build/envsetup.sh
- lunch cyanogen_supersonic-eng
- make -j`grep 'processor' /proc/cpuinfo | wc -l` otapackage
- ~/android/system/out/target/product/supersonic/update.cm-XXXXX-signed.zip
- SYNC WITH HONEYCOMB AOSP
- repo init -u git://android.git.kernel.org/platform/manifest.git -m 3.0-base.xml
- repo forall -p -c git checkout android-3.0_r1.3
- . build/envsetup.sh; lunch 1; make
- CREATE PATCH WITH DIFF
- diff -Nur a/drivers/bluetooth b/drivers/bluetooth > patch-bt.32
- patch -p1 < ~/usr/src/patch-2.6.24-viafb
- BATCH FIND AND PUSH MODULES BUT COULD BE USED FOR ANYTHING
- for file in `ls system/lib/modules/*.ko`
- do
- adb push $file /system/lib/modules/
- done
- cd system/lib/modules ; ls -1 *.ko |awk '{print "adb push " $1 " /system/lib/modules/" }' |sh
- XOOM DATA AND BLOCK MANIPULATION
- COPY IMAGES
- cat /dev/block/mmcblk0p4 > /data/media/external/misc5.img
- cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /data/media/external/boot.img
- cat /dev/block/platform/sdhci-tegra.3/by-name/system > /data/media/external/system.img
- cat /dev/block/platform/sdhci-tegra.3/by-name/userdata > /data/media/external/userdata.img
- cat /dev/block/platform/sdhci-tegra.3/by-name/recovery > /data/media/external/recovery.img
- cat /dev/block/platform/sdhci-tegra.3/by-name/logo > /sdcard/logo.img
- FLASH IMAGES
- ./fastboot flash boot boot.img
- ./fastboot flash system system.img
- ./fastboot flash recovery recovery.img
- ./fastboot flash userdata userdata.img
- ./fastboot erase cacheB
- MOUNT FROM SHELL
- mount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/recovery mnt/recovery
- mount -r -w -t vfat /dev/block/platform/sdhci-tegra.2/mmcblk0p1 mnt/external
- ALTERNATE COPY IMAGE
- dd if=/dev/block/platform/sdhci-tegra.3/by-name/boot of=/data/boot.img
- dd if=/dev/block/platform/sdhci-tegra.3/by-name/logo of=/sdcard/external/logo.img
- LARGE BLOCK ON DEALING WITH SBF: NEED TO SORT
- convert image for splash image
- #!/bin/bash
- sudo apt-get install imagemagick
- convert -size 1280x800 xc:black logo.bmp
- dd of=tmp.bmp if=logo.bmp bs=1 count=54
- dd of=tmp.bmp if=logo.img bs=1 count=3072000 conv=notrunc oflag=append
- convert -flip tmp.bmp logo.bmp
- rm tmp.bmp
- chmod +x sbf_flash
- ./sbf_flash filename.sbf
- The output looks something like this -
- SBF FLASH 0.01 (mbm)
- === hack.sbf ===
- 00: RDL03 0x80500000-0x8054CFFF FE66 AP
- 01: CG35 0xC0680000-0xC08E37FF ABCB AP
- 02: CG47 0xC0A00000-0xC0D5C7FF 02C0 AP
- Droid found.
- >> uploading RDL03
- Uploading: 100% OK
- >> verifying ramloader
- -- OK
- >> executing ramloader
- Droid (ramloader) found.
- >> sending erase
- >> uploading CG35
- Uploading: 100% OK
- >> uploading CG47
- Uploading: 100% OK
- >> verifying CG35
- -- OK
- >> verifying CG47
- -- OK
- >> rebooting
- I found a guide for the E2, the E6 and A1200 are identical except for the different code groups, which was posted on your forum I b
- elieve. Well heres the guide(for the E2 but its applicable to the E6)
- Use SBFTool for parsing:
- 1. The cg34.smg is picture, ringtone, power up off image, and so on icons
- 2. The cg37.smg is secure setup ( notice that has 0x1000's FF head file, delete it first when modding). It's important because the flexbit in it
- 3. The cg39.smg is boot logo(not the poweron image,but before it)
- 4. The cg41.smg is usr/language , so we change fonts here
- 5. The cg42.smg /usr/setup , some setup config files
- 6. The cg43.smg / , main file system, the bin, lib, the SYSqtapp ( 0x1000 FF head file)
- 7. Beside cg39.smg, the other cg34 cg37 cg41 cg42 cg43 are cramfs file systems, you can mount -o -loop the smg in linux(root)
- # tar zcvf xxx.tar.gz mountedsmgfolder
- # tar zxvf xxx.tar.gz -C targeteditfolder
- so you can mod the files in target edit folder then
- # mkfs.cramfs targeteditfolder/xxx cg##.smg
- so you made a new cg##.smg yourself
- You can overwrite the smg content in sbf, be carefull the 0X1000 ff head file, and the origin size of smg , plast FF to your new smg to make the size the same
- Make the sbf this way will failed when flash finished ( but it works, it really flashed into your phone), because there're checksums in the position 0x300 ~ , 2 block the end of each line
- Use checksum.exe to see the checksums( if you got the value EC FA, it should write as FA EC, it must be the opsite of checksum.exe value)
- Overwite the checksums, flash will be perfectly finished"
- sudo apt-get install cramfsprogs fusecram
- mkdir /tmp/image
- fusecram /path/to/cramfs_image /tmp/image
- mount -o loop ~/olyfr_u4_1.5.2_signed_olpsattspe_p012_hwolympus_1g_1ffCG57.smg /mnt/atrix
- sort +3 -5 '/home/bigrushdog/Desktop/public_sort.xml' > new_sort.xml
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement