Database Users

[TUT]-PORTING-Android To The VOGUE

the title says it
after many requests here is the guide
most of this is spread around the vogue
forum here and there, i just wanted to bring it all together
goal-seeing lately we have lost some good developers, this is a shot at getting more involvement in vogue/android development
I.SETTING UP YOUR SYSTEM
1. GETTING LINUX you will need to have Linux installed on your computer(dual-boot, vm, whatever). i recommend Ubuntu karmic (9.10) because its pretty new-user friendly. It can be found at http://www.ubuntu.com/
for you windows lovers here is a guide to setting up a ubuntu VM(virtual machine (if you really didnt know ))
2. THINGS/TOOLS YOU WILL NEED download these:
original 8/8/09 ion 1.5 build HERE(we are gonna use the bin-files and the apns-conf.xml, and a few apps)
the latest rootfs.img (find it)
these android tools (included are genext2fs (android version), split_bootimg.pl, and extract_ramdisk.sh)
after downloading, extract the zip to a folder. open a terminal and cd to the dir of the tools. click applications>accesories>terminal and type:
Code:
cd ~/whatever/
sudo rm -rf /bin/genext2fs
#dont type whats after the pound signs
#type in your password
#if you havent set up a su password yet type:
sudo passwd
#then make one, next
sudo cp -r ./whatever/genext2fs /bin/
squashfs-tools (if you have ubuntu 9.10-karmic first you will have to uninstall squashfs-tools 4.0(4.0 WILL NOT NOT NOT NOT NOT WORK) that is installed during the installation of linux ): go to system>administration>synaptic package manager. type squashfs-tools in the quick search, then right click and click mark for complete removal. then hit apply. then download and install this here http://http://ftp.us.debian.org/debian/pool/main/s/squashfs/squashfs-tools_3.3-7_i386.deb
i also strongly recommend downloading the sdk-tools v1.1(adb is almost essential when porting, for debugging purposes) enatefox has it posted on his media fire. (search for it)
3. ORGANIZATION
now that we have what we need. lets get organized.
a.mount points
we are going to use mount points while porting.
terminal:
Code:
sudo mkdir /mnt/rootfs
sudo mkdir /mnt/system
#i also have one for mounting data files
mkdir /mnt/data
b. directories
terminal:
Code:
mkdir ~/Desktop/android
mkdir ~/Desktop/android/ion
mkdir ~/Desktop/android/donut
#you get the point...
now put the ion 8/8/09 build in the ~/Desktop/android/ion folder and rename it system.sqsh then
terminal:
Code:
cd ~/Desktop/android/ion
unsquashfs ./system.sqsh
you should now have a folder called squashfs-root in the ion directory. it contains all the guts from the ion build. feel free to look around in that folder as you should get familiar with the folders and things in there
II PORTING
1. PORTING A HERO ROM(this was in zens how-to-make-a-hero-rom.txt im just adding on to it)
a. Download a rom from the dream/sapphire development forums.
b. Extract what you downloaded to ~/Desktop/android/hero. It is usually an update.zip.
c. Open the extracted folder. Inside you should see a data directory and a system directory.
d. Open the data directory and look for an app or app_s folder.
e. Open those folders and copy the apks to the system/app/ folder. Leave out what you don't need. feel free to add any custom apps. as long as they are from the same sdk number. ie 1.5, 1.6, 2.0.1, 2.1 most are pretty cross-compatible though.
f. Delete system/xbin from the rom your porting and replace it with the one from Ion.
g. Copy ~/Desktop/android/ion/squashfs-root/etc/apns-conf.xml from Ion to ~/Desktop/android/hero/system/etc/
h. Mount the latest rootfs.img
terminal:
Code:
sudo mount ~/whereever/rootfs.img -o loop /mnt/rootfs
i. Copy libaudio.so libaudioflinger.so libcameraservice.so libgps.so from /lib in the mounted rootfs over to system/lib in the rom you are porting*(donut and eclair really dont need this step because those files are in most of the latest rootfs.img's but be sure to check)
j. Edit the system/build.prop or even use the Ion build.prop.*(for donut/eclair you may want to edit the lcd density to 120 or 110 in the build.prop for qvga and 160 for 320x480)
k. Create a blank file in system/ called hero.build*(for eclair/donut create donut.build or eclair.build or eclairhero.build.....etc)
*l. for hero any systems too big to run on nand, here is a script to make a data file. put this in the ~/Desktop/android/hero directory. cut the app folder from ~/Desktop/android/hero/system and paste it to ~/Desktop/android/hero , and rename it too app_s . next run the mkdataimg.sh it should ask for you password in a terminal. type it in and then it should mount the data.img to data-mnt folder in ~/Desktop/android/hero . keep that terminal open copy the app_s folder in to data-mnt. then type y in the terminal to unmount the data.img. next:
terminal:
Code:
cd ~/Desktop/android/hero
ln -s /data/app_s ./system/app
that should make a broken symlink in system
2. Mount it and squash it
ok now that we are done porting lets put it together
terminal:
Code:
cd ~/Desktop/android/hero
genext2fs -d ./system -b 180000 -a system.ext2
sudo mount -o loop ./system.ext2 /mnt/system
sudo mksquashfs /mnt/system system.sqsh
sudo chown $USER ./system.sqsh
#and if you want
rm -rf ./system.ext2
from zenulator:
There are other little tweaks here and there but thats basically it. Now you can roll your own.
Click to expand...
Click to collapse
im gonna clean this up a bit later just wanted to get this out to you guys

nice thanks jamezelle

zen's manup456-based Eclair build contains different libaudio.so & libaudioflinger.so than the rootfs, and Eclair wouldn't boot if I replaced them with the libs from the rootfs. This might be due to the rootfs libs not being updated for Eclair yet (also why voice search/dial doesn't work) but I'm not sure. I don't know if this will be the case for 2.1, just wanted to add that in.
I really appreciate the guide and look forward to hearing more. I've learned a lot from zen as well but a lot of the work the devs do is so hard to follow because it's undocumented.
Do you know why the xbin has to be from Ion? Is it because of our kernel version or the squashfs ver that our kernel contains? I've been wanting to grab some of the tools from the xbin of other builds but have been unsure about compatibility.
Also, for more advanced Android ROM building, I'd like to add a link to zipalign optimization.

polyrhythmic said:
zen's manup456-based Eclair build contains different libaudio.so & libaudioflinger.so than the rootfs, and Eclair wouldn't boot if I replaced them with the libs from the rootfs. This might be due to the rootfs libs not being updated for Eclair yet (also why voice search/dial doesn't work) but I'm not sure. I don't know if this will be the case for 2.1, just wanted to add that in.
I really appreciate the guide and look forward to hearing more. I've learned a lot from zen as well but a lot of the work the devs do is so hard to follow because it's undocumented.
Do you know why the xbin has to be from Ion? Is it because of our kernel version or the squashfs ver that our kernel contains? I've been wanting to grab some of the tools from the xbin of other builds but have been unsure about compatibility.
Also, for more advanced Android ROM building, I'd like to add a link to zipalign optimization.
Click to expand...
Click to collapse
we need to move back to a more standardized comunity rootfs.img. i'm seeing more and more different rootfs.imgs that vary little by little. it is kind of hard to really document all of the development. but i see your point. the xbin(are just eXtended bin files) doesnt have to come from ion. the xbin in ion is actually empty
yes our kernel doesnt support LZMA compression which is what 4.0 uses. more info on it here http://www.squashfs-lzma.org/ i dont know why out kernel has not been updated to support it(you would have to ask DZO), i just know is isnt supported
thanks for the link to zipalign. i usually zipalign my apps. btw most dream and sapphire devs are already zipaligning there apks so we dont have to

I agree, I don't like forking the rootfs but the latest ones don't contain the correct WiFi files & settings for Kaiser. I know our kernel is way behind, I've asked several questions in the kernel thread about it but then the thread goes OT and I've never gotten an answer to most of the questions. Newbie16 has been compiling kernels but we've had trouble finding all the updated source files.
Oh, the PNG optimization in the zipalign thread is useful also, I easily saved 5 MB in the Eclair build.

The 8/8 file is a .img file, not .sqsh. Terminal tells me it can't find a sqash superblock on the file, or something to that extent.
EDIT: also missing a step that seems crucial... re squashing the files to make a .sqsh file to use?

ln -s help. hero nand porting
When ever I'm trying to port a hero build to nand ln -s gives me "operation not permitted" during boot. I used -a during genext2fs. Also data didn't work, even though I have the right apns-conif.xml. any idea? I was trying to port hero revolution (I think thats it ). Thanx

TheKartus said:
The 8/8 file is a .img file, not .sqsh. Terminal tells me it can't find a sqash superblock on the file, or something to that extent.
EDIT: also missing a step that seems crucial... re squashing the files to make a .sqsh file to use?
Click to expand...
Click to collapse
i fixed(add the missing steps) it but i dont have a copy of 8/8 ion personally. any ion system.sqsh build will work. if anyone has one please post it!

TheKartus said:
The 8/8 file is a .img file, not .sqsh. Terminal tells me it can't find a sqash superblock on the file, or something to that extent.
EDIT: also missing a step that seems crucial... re squashing the files to make a .sqsh file to use?
Click to expand...
Click to collapse
jamezelle said:
i fixed(add the missing steps) it but i dont have a copy of 8/8 ion personally. any ion system.sqsh build will work. if anyone has one please post it!
Click to expand...
Click to collapse
i just mounted the system.img and copied all the files to a new folder....that way then u dont have to mount the system.img everytime u are porting a rom
my steps to do that
[email protected]:~# cd Android
[email protected]:~/Android# dir
hi Inferno sensehero13 SenseHERO-v1.4_NoTheme senshero
signed-Hero_Inferno_Final signed-Hero_Inferno_Final.zip
system-2009-08-08.img system-sensehero-20091009.sqsh
TOOLS
ZipAlign.sh
[email protected]:~/Android# mkdir ion
[email protected]:~/Android# mount -o loop system-2009-08-08.img ion
[email protected]:~/Android#

Could someone please define...
Could someone please define rootfs, zIMage and the other parts that go into an Android build? If you're going from say, donut, to eclair, which ones can you reuse? I think I understand that the system.sqsh is what makes a build donut or eclair and actually is the file that has the customizations in it. But, what do the other parts do? If this is the wrong place to post this, mods, please move this. Thanks.
Sally

Hey guys, don't know if anyone else is having this issue or not.
I'm trying to work with the Topaz kernals...I downloaded the XDAndroid 2.1 system.sqsh and was able to unsquashfs it fine on my Vector Linux box...but I want to do the same to the TopazKernal16 system.sqsh (donut) but when I run unsquashfs it makes it to about 70% (highest I got to was 80% on one try) and then stops saying "killed".
any way to remedy this? also, what is the simplest way to "re"squash it?
Thanks!

iceman198 said:
Hey guys, don't know if anyone else is having this issue or not.
I'm trying to work with the Topaz kernals...I downloaded the XDAndroid 2.1 system.sqsh and was able to unsquashfs it fine on my Vector Linux box...but I want to do the same to the TopazKernal16 system.sqsh (donut) but when I run unsquashfs it makes it to about 70% (highest I got to was 80% on one try) and then stops saying "killed".
any way to remedy this? also, what is the simplest way to "re"squash it?
Thanks!
Click to expand...
Click to collapse
You just posted in the wrong forum altogether. This section is for the Vogue, not for the Topaz. Try to ask there on in one of the xdandroid threads. This project is different from xdandroid. Thanks.

egzthunder1 said:
You just posted in the wrong forum altogether. This section is for the Vogue, not for the Topaz. Try to ask there on in one of the xdandroid threads. This project is different from xdandroid. Thanks.
Click to expand...
Click to collapse
Sorry, thanks...

iceman198 said:
Sorry, thanks...
Click to expand...
Click to collapse
No prob

I would be interested in the Android's filesystem breakdown. Just some guide on what exactly is in the system, and then rootfs.img and then the modules. If someone could point me in the right direction, that would be much appreciated!
Thanks!

iceman198 said:
I would be interested in the Android's filesystem breakdown. Just some guide on what exactly is in the system, and then rootfs.img and then the modules. If someone could point me in the right direction, that would be much appreciated!
Thanks!
Click to expand...
Click to collapse
pm dzo, he will probably be able to help you there.

egzthunder1 said:
pm dzo, he will probably be able to help you there.
Click to expand...
Click to collapse
Thanks egzthunder1!

iceman198 said:
Thanks egzthunder1!
Click to expand...
Click to collapse
Not a problem. Good luck!

[HOWTO]:Recover QWERTZ layout for Milestone 2 after MOD

Hey folks !
I was seriously annoyed by the qwerty layout and the missing Umlaut's like äöü and so on, moreover it was hard to produce french accents. If it helps somebody PLEASE hit the thanks button ! Thanks ;-)
(I know it's all possible by holding down the respective key for 10^6 years and to choose the respective character, but what can I say ... 10^6 years are way to long !).
So here is how I fixed it:
Prerequisites (besides a rooted phone) :
1. Download the attached keymap from original 2.2.2 Froyo
2. Unzip the file
3. Copy it to your SD Card in your mobile phone
4. Check if you have a file called "umts_milestone2-keypad.kcm.bin" in the folder /sdcard on your phone. If so continue, if not, try to figure out how to get the first three steps done !
Now we will backup your original keymap file and copy over the new one.
5. Connect either via adb or open up a terminal directly on your phone.
6. Type
Code:
su
. (Probably you have to hit "allow" in SU message popping up on the telephone's screen).
7. Make sure you now have a
Code:
#
in the beginning of the current comand line. (If not, you don't have superuser privileges, so the next steps won't work).
8. Execute the following lines :
Code:
mount -o rw,remount /dev/block/mmcblk1p21 /system
cd /system/usr/keychars/
dd if=/sdcard/qwerty.kcm.bin of=qwerty.kcm.bin.origi.bak
dd if=/sdcard/umts_milestone2-keypad.kcm.bin of=qwerty.kcm.bin
mount -o ro,remount /dev/block/mmcblk1p21 /system
exit
exit
9. Enjoy your changed keyboard layout, changes should effect instantly !
If something is messed up you can try to copy back the backup file we created in step 8, it's called qwerty.kcm.bin.origi.bak and you could try dd'ing it back to dd if=/sdcard/qwerty.kcm.bin.
The code would be
Code:
dd if=/sdcard/qwerty.kcm.bin.origi.bak of=qwerty.kcm.bin
Remember that you'll have to be root for this as well.
I take no liability for any damage caused by this guide !
p.s. : Please remove the #+)(&$/&/% limitation of not beeing able to post to DEV forums !
p.p.s. : If you find any typos you can keep them
p.p.p.s : By #+)(&$/&/% I want to express something nice, of course !

But where is the /sdcard/qwerty.kcm.bin coming from?

carpet55 said:
But where is the /sdcard/qwerty.kcm.bin coming from?
Click to expand...
Click to collapse
1. Download the attached keymap from original 2.2.2 Froyo
Click to expand...
Click to collapse
As mentioned in the first post it is from the official 2.2.2 version of the Milestone 2.

There is just the file umts_milestone2-keypad.kcm.bin.zip, not the qwerty.kcm.bin - or am I blind? oO *kopfkratz*
---------- Post added at 09:59 PM ---------- Previous post was at 09:37 PM ----------
I copied the qwerty.kcm.bin-file from the CM7 folder /usr/keychars to /sdcard, then followed your guide.
Result: the üöaß is working again!
BUT the y and z were on the swapped. Then I swapped them in all the keylayout-files. Now it is qwertz again.

Alright ... now we can do that step by step or you just follow the guide, in this case step 2:
2. Unzip the file
Click to expand...
Click to collapse
Now you have the umts_milestone2-keypad.kcm.bin
Theeeeeeeeen, while carrying out step 8 you kind of rename to qwerty.kcm.bin :
Code:
dd if=/sdcard/umts_milestone2-keypad.kcm.bin of=qwerty.kcm.bin
.
Just do it step by step and it should work...

Cheers mate. Worked fine.
Three things:
1. I'm using Cyangenmod 7 from this forum and there is already a qwertz.kcm.bin in the /system/usr/keychars/ folder. Just copy/rename/move the file qwertz.kcm.bin to qwerty.kcm.bin
2. Isn't there an easier way to to do all this? I had the same isues with my G1 and now with the Milestone 2.
3. Where is the thanks button?

[GUIDE][LINUX] MIUI patchrom for jellybean roms

I searched and reading a lot but can't find properly guide how to use miui patchrom for jellybean roms. So i decided share what i've found and put all in one guide.
1. First of all you need linux on your machine. I use kubuntu, installed from windows (wubi) ->http://www.kubuntu.org/getkubuntu/download
2. Now you need SDK tools for linux http://developer.android.com/sdk/index.html
-download and unzip it to for egz home/your_username/android-sdk-linux
-set PATH for tools and platform-tools folders
Code:
export PATH=/home/your_username/android-sdk-linux/platform-tools:/home/your_username/android-sdk-linux/tools:$PATH
On x64 systems you are required to install some 32-bit libraries so in a terminal write:
Code:
sudo apt-get install ia32-libs
3. Download ROM which you want to patch with miui patchrom, must be deodexed and rooted. For us it must be jellybean ROM for egz 4.1.2. I suggest to use CM or AOSP based roms because stock sammy roms have a lot of differences and it's not so easy to port them. After downloading your ROM base rename it to something short and easy i use stock.zip.
In home create folder i use patchrom folder in this folder create for egz stock folder and put downloaded rom to it.
4. Download from MiCode github all necessary files https://github.com/MiCode we need:
https://github.com/MiCode/patchrom_tools/archive/jellybean.zip tools
https://github.com/MiCode/patchrom_miui/archive/jellybean.zip miui
https://github.com/MiCode/patchrom_i9100/archive/jellybean.zip i9100
https://github.com/MiCode/patchrom_build/archive/jellybean.zip build
https://github.com/MiCode/patchrom_android/archive/jellybean.zip android
all zips for jellybean, why downloading zips? because for me repo don't download all files, that way is much easiest.
Unzip all files to your stock folder which you create in step 3. Rename all folders by this way patchrom_tools_jellybean becomes tools, patchrom_miui_jellybean becomes miui ...
5. In i9100 folder you can find makefile its first of configuring files which you need to copy to stock folder and edit it.
This is my makefile, you should edit using this explanations:
'local-zip-file' = Name of your original ROM zip
'local-out-zip-file' = Name for your finished MIUI rom
'local-modified-apps' = Apps that will be modified to fit in with the framework. They need to be modified because they contact with the system
'local-miui-apps' = MIUI Apps that will be integrated into the zip
'local-remove-apps' = Apps that will be removed from the original ROM
'local-pre-zip' = Refers to codeblock that should be executed before the zip is done.
'local-after-zip' = Refers to codeblock executed after the zip is completed
'local-zip-misc' = The codeblock just described at 'local-pre-zip'. It adds some Google Apps and a buid.prop
'local-test' = Another codeblock
Code:
#
# Makefile for i9100
#
PORT_BUILD=/home/jack/patchrom/build
PORT_ROOT=/home/jack/patchrom
# The original zip file, MUST be specified by each product
local-zip-file := stock.zip
# The output zip file of MIUI rom, the default is porting_miui.zip if not specified
local-out-zip-file := MIUI_i9100.zip
# the location for local-ota to save target-file
local-previous-target-dir := ~/workspace/ota_base/i9100_4.1
# All apps from original ZIP, but has smali files chanded
local-modified-apps := LogsProvider Phone MediaProvider Settings
local-modified-jars :=
# All apks from MIUI
local-miui-removed-apps := MediaProvider Stk
local-miui-modified-apps := MiuiHome Settings Phone Mms ThemeManager MiuiSystemUI
# Config density for co-developers to use the aaps with HDPI or XHDPI resource,
# Default configrations are HDPI for ics branch and XHDPI for jellybean branch
local-density := HDPI
include phoneapps.mk
# To include the local targets before and after zip the final ZIP file,
# and the local-targets should:
# (1) be defined after including porting.mk if using any global variable(see porting.mk)
# (2) the name should be leaded with local- to prevent any conflict with global targets
local-pre-zip := local-pre-zip-misc
local-after-zip:= local-put-to-phone
# The local targets after the zip file is generated, could include 'zip2sd' to
# deliver the zip file to phone, or to customize other actions
include $(PORT_BUILD)/porting.mk
# To define any local-target
updater := $(ZIP_DIR)/META-INF/com/google/android/updater-script
pre_install_data_packages := $(TMP_DIR)/pre_install_apk_pkgname.txt
local-pre-zip-misc:
cp other/spn-conf.xml $(ZIP_DIR)/system/etc/spn-conf.xml
cp other/build.prop $(ZIP_DIR)/system/build.prop
#cp stockrom/system/app/FFFFFFFF000000000000000000000001.drbin $(ZIP_DIR)/system/app
#cp -r stockrom/system/app/mcRegistry $(ZIP_DIR)/system/app
rm -rf $(ZIP_DIR)/system/csc
rm -rf $(pre_install_data_packages)
for apk in $(ZIP_DIR)/data/media/preinstall_apps/*.apk; do\
$(AAPT) d --values resources $$apk | grep 'id=127 packageCount' | sed -e "s/^.*name=//" >> $(pre_install_data_packages);\
done
more $(pre_install_data_packages) | wc -l > $(ZIP_DIR)/system/etc/enforcecopyinglibpackages.txt
more $(pre_install_data_packages) >> $(ZIP_DIR)/system/etc/enforcecopyinglibpackages.txt
out/framework2.jar : out/framework.jar
%.phone : out/%.jar
[user=279333]@ECHO[/user] push -- to --- phone
adb remount
adb push $< /system/framework
adb shell chmod 644 /system/framework/$*.jar
#adb shell stop
#adb shell start
#adb reboot
%.sign-plat : out/%
#%.sign-plat : /home/gexudong/libra.jbmiui/out/target/product/maguro/system/app/%
java -jar $(TOOL_DIR)/signapk.jar $(PORT_ROOT)/build/security/platform.x509.pem $(PORT_ROOT)/build/security/platform.pk8 $< $<.signed
[user=279333]@ECHO[/user] push -- to --- phone
adb remount
adb push $<.signed /system/app/$*
adb shell chmod 644 /system/app/$*
So, you have to change:
local-zip-file := stock.zip name of your base rom
PORT_BUILD=/home/jack/patchrom/build to your patch for build folder
PORT_ROOT=/home/jack/patchrom to your root folder
After edit in makefile and save it in patchrom/stock folder you sholud copy from patchrom/build folder these files: porting.mk and phoneapps.mk
you can edit phoneapps.mk too add or delete files which you want.
File structure must look like this:
home
-your_username
-android-sdk-linux:
(-extras
-platform-tools
-platforms
-system-images
-tools)
-patchrom:
(-android
-build
-i9100
-miui
-stock (including: stock.zip - your base rom, makefile edited by you, phoneapps.mk edited by you, porting.mk - copied from build folder)
-tools)
6. Ok, files is prepared, now we can start. Open console and type:
cd patchrom - go to patchrom folder
cd stock - go to stock folder
cd .. - go back
make workspace - this command create temp folder in stock folder, and decompile all necessary files from stock.zip and from miui patchrom, it decompile also files which you add in makefile 'local-modified-apps'
Now in temp you have 5 folders, in reject folder you can resolve any conflicts to prepare necessary files for miui rom.
7. After fixing problems with smali type in console
make firstpatch
this command will apply all rej changes and miui patch for your decompiled files.
8. In console type:
Code:
source build/envsetup.sh
cd stock
make zipfile
Thats all.
If you have problems google it
Don't ask me for anything, use your brain!

Thank you for the information!
I think, you should add a couple of words to help linux newbies.
1. To set $PATH variable you need to edit "bashrc" file.
open terminal, run following command
Code:
gedit ~/.bashrc
gedit is an editor in Ubuntu, you can use any other editor
add to the begining
Code:
export PATH=/home/your_username/android-sdk-linux/platform-tools:/home/your_username/android-sdk-linux/tools:$PATH
save file
reboot to activate changes
test - open terminal, and execute "echo $PATH"
2. You need to generate keys to sign your rom.
http://android-dls.com/wiki/index.php?title=Generating_Keys

can I use this guide to build a miui patch rom for my galaxy nexus toro? which rom do you guys suggest me to use?

Hi,
I just need to ask a few things.
1. How do we know which local apps need to be modified. and which miui apps need to be modified.? I mean is there a pre-defined list or its hit n trial??
I can follow the instructions and run the scripts, but i need to make sure how do we select the criteria for above files. Rest i'll try to figure out myself.
Regards
Yasir

I think a couple of mistakes there are, its make fullota where you have written make firstpatch because make firstpatch will create the temp poster where the 5 folders exist. Once you've fixed the rejects, that's when you make fullota. Also, we don't need PORT_BUILD and PORT_ROOT exports.

MTK Mediatek MIUI
will this work for MTK phones? if yes is it the same process??

rnovino said:
will this work for MTK phones? if yes is it the same process??
Click to expand...
Click to collapse
maybe and you can't use then the i9100 you need to find a phone with compatible hardware or just the phone

Thanks for the guide.
Going to try this out in a few hours, installing Linux in vmware workstation 10 currently
Sent from my GT-I9100 using Tapatalk 4

Need help..
i want to port miui to my mtk phone what are the required files for mtk.......

MTK 6575 - acer z2 JB4.1.1 dual sim
which branch do i used to patching MTK6575 JB4.1.1, JB4.2-MTK or JB4.1-non MTK?
[edit]
basicly as i know, that we have doing is:
- merged Miui framework(smali) to stock framework (smali), right?
- copy lib/etc/xbin ...
- edit bootclasspath if need.
- edit updater-script.
- repack all.

alfan.y said:
which branch do i used to patching MTK6575 JB4.1.1, JB4.2-MTK or JB4.1-non MTK?
[edit]
basicly as i know, that we have doing is:
- merged Miui framework(smali) to stock framework (smali), right?
- copy lib/etc/xbin ...
- edit bootclasspath if need.
- edit updater-script.
- repack all.
Click to expand...
Click to collapse
These pages are a great help. There are many others but start here.
Porting miui to other devices http://en.miui.com/thread-4569-1-1.html
Porting miui cm10.1 based devices http://en.miui.com/thread-6395-1-1.html
Porting miui patchrom guide http://en.miui.com/thread-9630-1-1.html

Huawei Y625-U43 "soft" bricked

Hi xda-developers before read my long story sorry for my bad english and I hope you can help me…
I bought this phone recently and because I don't feel comfortable with EMUI I decided to do some modding. I rooted the phone successfully, remove some apps, install a new launcher and at this point everything was fine then i decided to install XPOSED FRAMEWORK.
I didn´t know that Huawei phones has so many problems with Xposed but I took the risk to follow Xposed installation instructions of another Huawei model. I'll write the instructions that I followed.
I changed ro.config.hwtheme in build.prop to 0, reboot and everything was fine
Then I installed a console app to use this commands:
Code:
su
mount -o rw,remount /system
cd system
lsattr
chattr -R -i *
rm –f /system/set_immutable.list
But when i used lsattr and chattr the console display COMMAND NOT FOUND then I read an alternative to that commands.
Code:
chmod –R –i *
I have a little experience with Linux but I had never seen the “-i” modificator on chmod and the console too xD it displays
Code:
“bad mode not valid –i command”
or something similar.
Finally in a moment of stupidity I executed this command
Code:
chmod –R 777 *
I Reboot, Huawei logo then black screen, I remove the baterry, reboot and the same…
Well I only have the default Android recovery on the phone…
I found a ROM but that ROM is for the Huawei Y625-U32 I tried to modify this ROM removing the getprop lines on update-script and resinging the rom with APK SIGN but always trying to flash the signature verification fails.
Finally i read apart of the 3 files that generates APK SIGN in the META-INF folder (cert.rsa, cert.sf and manifest.mf) inside com/android exists other certificates files (otacert and metadata) and this files are related with the file /security/etc/otacerts.zip inside the phone but with Android recovery everything is complicated.
Well after my long story anybody can help me? I thought of these possible solutions:
Anybody can share me a backup ROM (update.App file) of this model (I know is a bit heavy to upload 700MB aprox.)
Help me modifying the Y265-U32 ROM to pass the frustrating signature check of Android Recovery (of course if at the end would be safe to mod that ROM or not )
Or any other suggestion please XDA Friends and thanks in advance.
P.D. I want to try all possibilities before send to technical service besides that the model was released recently (April 2015) and I dont know if they can flash it and sorry for my bad english again.

I'm on Colombia and I have the same model, original firmware can be found here: http://consumer.huawei.com/co/support/downloads/detail/index.htm?id=66735&key4=Y625
This is stock ROM. I recommend you NOT modify your system if you don't know too much.
Hope this helps

Hello guys I have a Huawei Y625-U13 from Mexico. My device is Softbricked, it wont boot up, its stucked at HUAWEI's Logo. I found the firmware to make an update via SD card (dload file). But I can't install it on my device, somebody knows how to?

How to check status of dm verity? To make sure it's disabled.

Hello everybody! I recently bricked my s7e by trying to install the superman mod because I was jumping between two guides and just followed the chapter for flashing the new bootloaders and not the beginning about twrp and so on.
Now I've done everything more carefully and thoroughly and executed the file for disabling dm verity and encryption. However I want to know if it is really disabled because I don't want to make the same mistake and have to reset me device again. Can you guys help me with how I check the status of em verity and encryption? I've tried to reach but just finds posts about people having the verification fail issue.
Thanks

Anyone our there that can help me or give me an idea?

Open a TWRP root shell and type:
Code:
surya:/ # avbctl get-verity
verity is disabled.
surya:/ # avbctl get-verification
verification is disabled.

lebigmac said:
Open a TWRP root shell and type:
Code:
surya:/ # avbctl get-verity
verity is disabled.
surya:/ # avbctl get-verification
verification is disabled.
Click to expand...
Click to collapse
Does it have to be with TWRP because Pixel 5 A12 doesn't have TWRP yet

elong7681 said:
Does it have to be with TWRP because Pixel 5 A12 doesn't have TWRP yet
Click to expand...
Click to collapse
No. You can run the same command in Android too and it will work. You can find avbctl binary in /tools subfolder of my SystemRW release (see link in my signature). Good luck!
Bash:
adb shell
su
./tools/avbctl disable-verity
./tools/avbctl disable-verification

lebigmac said:
No. You can run the same command in Android too and it will work. You can find avbctl binary in /tools subfolder of my SystemRW release. Good luck!
Bash:
adb shell
su
./tools/avbctl disable-verity
./tools/avbctl disable-verification
Click to expand...
Click to collapse
Can you send me a link to where I can find your tools?

lebigmac said:
No. You can run the same command in Android too and it will work. You can find avbctl binary in /tools subfolder of my SystemRW release (see link in my signature). Good luck!
Bash:
adb shell
su
./tools/avbctl disable-verity
./tools/avbctl disable-verification
Click to expand...
Click to collapse
Trying to use this on a slightly more out of date system. Is it possible to get you to release your tools in 32bit?

strayedsoul2003 said:
Trying to use this on a slightly more out of date system. Is it possible to get you to release your tools in 32bit?
Click to expand...
Click to collapse
I'll try to compile a 32 bit version sometime in the future but I can't say when. Just subscribe to the thread in my signature and you should be notified if there's any update
Wish me luck! Thanks
elong7681 said:
Can you send me a link to where I can find your tools?
Click to expand...
Click to collapse
Just click the link in my signature

elong7681 said:
Can you send me a link to where I can find your tools?
Click to expand...
Click to collapse
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com