Database Users

Minimal UI for LUKS encryption on the Wildfire

This is a basic gui I wrote to unlock my encrypted partitions during boot.
I'm running my /data and /sdcard partitions encrypted, and the "luksunlock" binary is launched from init.rc to read the password and unlock the encrypted partitions.
I have included my somewhat modified init.rc for those interested.
For more information about LUKS on Android see this blogpost, written by shawn (Seems I'm not allowed to have urls in the post, but Google for 'android luks' , first hit)
This works good on Wildfire, altough it should work fine on other phones as well. Just remember that you need to set up your partitions as in the luksunlock.c (or change the defines).
Dont forget to backup before you start playing around!
Good luck!

Thanks! i'll give a try!

Hi,
I tried to use your cryptsetup binary from your blog, but I have some issues that you'll sure have an answer:
I run ./cryptsetup luksFormat -c aes-plain /dev/block/loop2 and after i put the luks password it says 'Command failed', no logs, no other output, even using the -v flag...
Any clue?
Thanks in advance!
PS: the module dm-crypt is necessary for cryptsetup? could be this the error? I don't have it installed on the system because I can't find it for 2.6.35.9-cyanogenmod

tusabe said:
Hi,
I tried to use your cryptsetup binary from your blog, but I have some issues that you'll sure have an answer:
I run ./cryptsetup luksFormat -c aes-plain /dev/block/loop2 and after i put the luks password it says 'Command failed', no logs, no other output, even using the -v flag...
Any clue?
Thanks in advance!
PS: the module dm-crypt is necessary for cryptsetup? could be this the error? I don't have it installed on the system because I can't find it for 2.6.35.9-cyanogenmod
Click to expand...
Click to collapse
CM6.1 for wildfire uses a 2.6.32 kernel (see HCDR.jacob's post about his custom kernel for more info)

tusabe said:
PS: the module dm-crypt is necessary for cryptsetup? could be this the error? I don't have it installed on the system because I can't find it for 2.6.35.9-cyanogenmod
Click to expand...
Click to collapse
Yeah you really need dm-crypt support, either compiled into the kernel or as a module. You also need the AES ciphers support.

sigkill1337 said:
Yeah you really need dm-crypt support, either compiled into the kernel or as a module. You also need the AES ciphers support.
Click to expand...
Click to collapse
Hi! Yeah, that's what I was afraid of.... ok, but the problem is that i'm running CM6.1 with 2.6.35.9 which has no dm-crypt module neither compiled in kernel... where can i find some kernel with this modules included? Is for an HTC Desire (@Sympnotic )
Thanks in advance!

Great work and thanks for sharing @Sigkill. Working on building it here for my NexusOne with CM6.1.
BTW, I’m the lead on a project working on general secure Android distro – we’ve ported Tor, have an OTR IM app, and have supported other projects along those lines. Would love to talk more about supporting anyone working on this specific capability.

wow! awesome work!!! Very exciting news. Gonna give this a go on my MyTouch Slide

NathanFreitas said:
Great work and thanks for sharing @Sigkill. Working on building it here for my NexusOne with CM6.1.
BTW, I’m the lead on a project working on general secure Android distro – we’ve ported Tor, have an OTR IM app, and have supported other projects along those lines. Would love to talk more about supporting anyone working on this specific capability.
Click to expand...
Click to collapse
Seems really nice. I like the secure phone concept.

New Makefile and wiki info up
_hc from the @guardianproject has a new build process up for Crypsetup/LUKS which includes a Makefile compatible with Android NDK r5.
We have new instructions up on our wiki, as well.
I cannot post links under this account, but you can find the info on github if you search "LUKS" or just under our guardianproject account.

How did you create the encrypted partitions? Could you give some pointers for that. I am familiar with using dmcrypt/cryptsetup on desktop linux, I guess this works similar. What are the relevant device names? Did you run into any problems?

Calavera1 said:
How did you create the encrypted partitions? Could you give some pointers for that. I am familiar with using dmcrypt/cryptsetup on desktop linux, I guess this works similar. What are the relevant device names? Did you run into any problems?
Click to expand...
Click to collapse
Hi, sorry for the late answer,
/dev/block/mtdblock5 is the "userdata" partition. I formatted it and mount it to /encrypted-data during init:
mount yaffs2 [email protected] /encrypted-data nosuid nodev
The only file on this partition is "data.encrypted" file, which gets created in init.rc as a loopback device:
exec /system/bin/losetup /dev/block/loop0 /encrypted-data/data.encrypted
I created the "data.encrypted" file on my computer with cryptsetup and losetup, and copied all files from my old unencrypted userdata partition to it and then copied it back as a file to the formated userdata partition.
The sdcard "/dev/block/mmcblk0p2" partition is formated with "cryptsetup luksFormat", I did this also on my computer, saves some time. And then copy everything from the old unencrypted sdcard.
I did run in to one problem recently, my phone hung during boot, about 4 months after I started encrypting my phone.
Had to copy my data.encrypted file to my computer, mount it as a loopback device and do a fsck, and then copy it back to my phone.
I suspect this has to do with the filesystem not being umounted properly. (I have had this on my to do list for a while hehe)
Probably should make a script run during shutdown to cleanly "luksClose" the encrypted partition and then umount them. Not doing this is probably very crazy
I also want to fix it so my "/dev/block/mmcblk0p2" partition gets presented to my computer when i attach my usb cable (as it should do), so i can unlock it in ubuntu and copy images and files. Right now i have to take my memorycard out and put it into the computer.
I hope this post makes sense, it was written in haste =) Good luck!

sigkill1337 said:
Hi, sorry for the late answer,
/dev/block/mtdblock5 is the "userdata" partition. I formatted it and mount it to /encrypted-data during init:
mount yaffs2 [email protected] /encrypted-data nosuid nodev
The only file on this partition is "data.encrypted" file, which gets created in init.rc as a loopback device:
exec /system/bin/losetup /dev/block/loop0 /encrypted-data/data.encrypted
I created the "data.encrypted" file on my computer with cryptsetup and losetup, and copied all files from my old unencrypted userdata partition to it and then copied it back as a file to the formated userdata partition.
The sdcard "/dev/block/mmcblk0p2" partition is formated with "cryptsetup luksFormat", I did this also on my computer, saves some time. And then copy everything from the old unencrypted sdcard.
I did run in to one problem recently, my phone hung during boot, about 4 months after I started encrypting my phone.
Had to copy my data.encrypted file to my computer, mount it as a loopback device and do a fsck, and then copy it back to my phone.
I suspect this has to do with the filesystem not being umounted properly. (I have had this on my to do list for a while hehe)
Probably should make a script run during shutdown to cleanly "luksClose" the encrypted partition and then umount them. Not doing this is probably very crazy
I also want to fix it so my "/dev/block/mmcblk0p2" partition gets presented to my computer when i attach my usb cable (as it should do), so i can unlock it in ubuntu and copy images and files. Right now i have to take my memorycard out and put it into the computer.
I hope this post makes sense, it was written in haste =) Good luck!
Click to expand...
Click to collapse
I figured most of that out without your post and tried it on my desire (I created the luks partitions with adb on the phone though, worked anyway ). Then I couldn't figure out where my regular init.rc is stored (I could only find the one used by Clockwork Recovery), and then I figured I already spent enough time, tried a reboot (which of course didn't work). Then I couldn't even get into recovery (probably because its init.rc tries to mount /data which doesn't work? I didn't investigate any further). Flashed my backup with fastboot and was stuck again with my un-encrypted pre-experiment state
Oddly enough, it was no problem to unlock my encrypted SD-card from my computer (running ubuntu) while in recovery (clockword has an option to present the sd card to a computer connected via usb). Maybe the booted system handles this differently than recovery though? I didn't get a chance to try, as I couldn't boot after my encryption attempt.
I will try again after my algorithm and data structure exam this friday and report back

Is anybody using the UI on another device than the Wildfire? Does it work?
How much is the performance drain when using an encrypted /data partition?

Amazing work!

Did anyone manage to make sigkill1337's luksunlock build from source ?
I would like to change the path of the data/sdcard partitions to match my device but I tried many ways using the NDK and I can't get it to compile properly.
Is there any way to do this ?
I have been trying for days, I am getting literaly insane !
@sigkill1337 : could you give me some pointers ? I would appreciate a lot.

mount manpage said:
The bind mounts.
Since Linux 2.4.0 it is possible to remount part of the file hierarchy somewhere else. The call is
mount --bind olddir newdir
or shortoption
mount -B olddir newdir
or fstab entry is:
/olddir /newdir none bind
After this call the same contents is accessible in two places. One can also remount a single file (on a single file).
This call attaches only (part of) a single filesystem, not possible submounts. The entire file hierarchy including submounts is attached a second place using
mount --rbind olddir newdir
or shortoption
mount -R olddir newdir
Note that the filesystem mount options will remain the same as those on the original mount point, and cannot be changed by passing the -o option along with --bind/--rbind. The mount options can be changed by a separate remount command, for example:
mount --bind olddir newdir
mount -o remount,ro newdir
Click to expand...
Click to collapse
If nothing helps, you should always be able to bindmount it

I'd rather get sigkill1337's UI to compile...
Lots of nice security tweaks and settings could be done with a pre-boot GUI
Anyway, concerning encryption, I'll use the bind option for now, thanks for the tip.
But if anyone here could give me some pointers about compiling this stuff it would be great.
I managed to compile it by integrating luksunlock in Android source externals and main.mk but when I push it to my phone and modify init.rc to call it, it just does not work...
Other modifications are working (mount, mkdir, etc.) but the GUI won't show up

Sorry for the late reply.. But you could try running it from a shell when the phone is booted, just to verify that the binary starts (thats how I tested it without having to reboot my phone all the time)
My environment for building the source was setup using one of the tutorials online, nothing out of the ordinary
Im still running this on my phone, for almost 8 months now, I havent noticed that much in performance problems, the Wildfire was slow before i started using luks.
When i get a new phone (maybe SE Arc) i will be easier to see if performance is affected

There is an Issue for getting CM support for encrypted filesystems during boot:
Issue 2736: support encrypted filesystem from boot
If you want to get that feature, just "star" it, so it may get more attention.

[Recovery] ClockworkMod Recovery 1.3.4(updated 24.06.2011)

OK, here is ClockworkMod Recovery for our beloved A500
NOTE:
If you encounter a problem with the filesystem on /data like it has become corrupt, place a blank file called "eraseData" (without the quotes) in the clockworkmod folder on your external sdcard or usb storage. This will revert back to actually formatting /data.
WARNING: by doing this you will lose everything that you have in /data/media.
Installation:
use adb (PC):
adb push recovery-thor2002ro-rev1.*.img /sdcard
adb push itsmagic /data/local
from terminal (TABLET):
su
chmod 755 /data/local/itsmagic
mount -o rw,remount /system
rm /system/etc/install-recovery.sh
mount -o ro,remount /system
dd if=/sdcard/recovery-thor2002ro-rev1.*.img of=/dev/block/mmcblk0p1
./data/local/itsmagic
"recovery-thor2002ro-rev1.*.rar" - is for flashing normally with the normal method...
"update-recovery-thor2002ro-rev1.*.zip" - flashed from recovery and press reboot/power off(v1.1 don't use "Advanced" -> "Reboot Recovery" only buttons in the main menu) after its flashed(don't try to flash from any other recovery other than mine, will not work)
Acer Recovery Installer APP thanks to Euclid's Brother http://forum.xda-developers.com/showpost.php?p=14818316&postcount=109
Video installation guide by cfcoleman
http://www.youtube.com/watch?v=cuf74JP5Jgw
Changelog:
1.1:
skips /data/media in backup/restore/format of /data
integrated "itsmagic"
additional option in advanced to run itsmagic manually
itsmagic is run on every restart/poweroff or recovery as a precautionary measure
ability to use usb storage in recovery for backups and restores...(has a priority system in place if usb stick is present on mount its used as a "sdcard", if not it falls back to microsd card), unmount and mount will also trigger this.
1.2:
flexrom backup & restore
bct + ebt + pt + gp1 backup(basically the first sectors of the flash that sc2k told you to backup when itsmagic got released...)
retrieve uid
itsmagic run at startup
usb keyboard fix
1.3.2:
fixed background disappearing
removed itsmagic from reboot/poweroff, not needed itsmagic is run at startup...
fixed flexrom not being present in advanced restore menu
1.3.3:
fixed back disappearing in Mounts and Storage menu
1.3.4(still in testing...):
added sync before md5 generation
sync and unmount of /sdcard after succesful backup
sync and unmount of /sdcard at reboot/poweroff
Thanks to sc2k for testing this.
Even though this recovery has been tested, I am not liable for any loss of data or any damages done by this recovery.

tnx for this!!
great!!

thor2002ro said:
OK, here is ClockworkMod Recovery for our beloved A500
Includes:
skips /data/media in recovery/restore/format of /data
integrated "itsmagic"
additional option in advanced to run itsmagic manually
itsmagic is run on every restart/poweroff or recovery as a precautionary measure
ability to use usb storage in recovery for backups and restores...(has a priority system in place if usb stick is present on mount its used as a "sdcard") if not it falls back to microsd card), unmount and mount will also trigger this.
NOTE:
If you encounter a problem with the filesystem on /data like it has become corrupt, place a blank file called "eraseData" (without the quotes) in the clockworkmod folder on your external sdcard or usb storage. This will revert back to actually formatting /data.
WARNING: by doing this you will lose everything that you have in /data/media.
Installation:
remove /system/etc/install-recovery.sh if present
dd the image to mmcblk0p1
run itsmagic
TO DO:
flexrom backup & restore
bl + bct backup
retrieve uid
Thanks to sc2k for testing this.
Even though this recovery has been tested, I am not liable for any loss of data or any damages done by this recovery.
Click to expand...
Click to collapse
1.before we dd the image to mmcblk0p1 ，do we have to install itsmagic first
u said u had integrated itsmagic in that recovery，but how do we run that itsmagic，from where？
2. what is the “bl” and “bct” stand for？
3. is “to do……” what we can do or something else ？i cant understand it sorry。

I am all over this but please add more thorough instructions. Thanks

Awesomeness, that is all
Sent from my ADR6400L using XDA Premium App

Yea tend to agree sounds awesome. But if we could have a more clear set of instructions. So people don't brick their tablet.
Sent from my PC36100 using XDA Premium App

to do means things he wants to add to or fix in this release.
What does dd stand for?

ibila said:
to do means things he wants to add to or fix in this release.
What does dd stand for?
Click to expand...
Click to collapse
Well thanks for explaining what to do means...
dd is the termed used to dump this image to a particular block in this case block 0p1

ibila said:
to do means things he wants to add to or fix in this release.
What does dd stand for?
Click to expand...
Click to collapse
o ,I see
"dd" is a command in linux, it can write a img to a partition or block
in this case, we can use that command like this:
dd if=/sdcard/recovery-thor2002ro-rev1.1.img of=/dev/block/mmcblk0p1

thor2002ro said:
Even though this recovery has been tested, I am not liable for any loss of data or any damages done by this recovery.
Click to expand...
Click to collapse
hmm... you could not find a smaller font?

Dexter_nlb said:
hmm... you could not find a smaller font?
Click to expand...
Click to collapse
lol not very nice though.

updated instructions...

anybody know how to do it from Windows? (no DD)

Dan2552 said:
anybody know how to do it from Windows? (no DD)
Click to expand...
Click to collapse
dd is on the tablet not windows...

thor2002ro said:
updated instructions...
Click to expand...
Click to collapse
Where are the "updated instructions"

Crsdr37 said:
Well thanks for explaining what to do means...
dd is the termed used to dump this image to a particular block in this case block 0p1
Click to expand...
Click to collapse
Hmmm there is maybe a tiny one in a million chance that your not the only participator in this thread so who knows...maybe this explanation was not for you but for kimcai.
Sorry if i just burst your bubble

docfreed said:
Where are the "updated instructions"
Click to expand...
Click to collapse
OP
10char

ibila said:
OP
10char
Click to expand...
Click to collapse
Doh! Thanks

Dexter_nlb said:
hmm... you could not find a smaller font?
Click to expand...
Click to collapse
its called "the fine print"

thor2002ro said:
updated instructions...
Click to expand...
Click to collapse
what can we do in your modified recovery？

Mod flipout

Hello,
There is someone really working on a port of any custom to this cellphone?
I have brought a new phone (Samsung Galaxy Nexus) and I want to port my old MB511 to CyanogenMOD or MIUI.
I have some experience on embedded systems, bootloaders, Linux kernel development, but nothing related to cellphone or android.
So, I really want to start a mod but I want some help in order to make it
Reading (and-developers DOT com) I realized that I need:
1) Use recover 'Open Recovery' or 2ndboot
2) Compile Cyanogen kernel or MIUI (For OMAP-3410)
3) try to boot kernel
4) port cyanogen/miui
5) copy devices binaries
Do someone have any clue or a start point in order to get any step done? I'm new.
Any help will be appreciate.

1.There is someone really working on a port of any custom to this cellphone?
NO. No anyone.
1) Use recover 'Open Recovery' or 2ndboot
Dexter_nlb FlipOut Recovery (CWM based v2.5.1.2)
http://forum.xda-developers.com/showthread.php?t=942160
polovinamozga Big Bootstrapped Recovery
http://forum.xda-developers.com/showpost.php?p=14796425&postcount=412
laidaxin 2ndInit_Installer (For MB508)
http://forum.xda-developers.com/showthread.php?t=1471549
2) Compile Cyanogen kernel or MIUI (For OMAP-3410)
Flipout's bootloader is locked. So...
3) try to boot kernel
Flipout's bootloader is locked. So...
4) port cyanogen/miui
Maybe you can ask laidaxin.
He would ready to port MB502.
He already port CM7 to MB508 success.
I hope this was useful to you

Just port CM7 from the Flipside.... Change libs and build.prop... They have the same processor and both have Android 2.2 I believe
Sent from my MB520 using XDA App

marquae11 said:
Just port CM7 from the Flipside.... Change libs and build.prop... They have the same processor and both have Android 2.2 I believe
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
very good ideea, but the bootloader is still locked

laluth said:
1.There is someone really working on a port of any custom to this cellphone?
NO. No anyone.
1) Use recover 'Open Recovery' or 2ndboot
Dexter_nlb FlipOut Recovery (CWM based v2.5.1.2)
http://forum.xda-developers.com/showthread.php?t=942160
polovinamozga Big Bootstrapped Recovery
http://forum.xda-developers.com/showpost.php?p=14796425&postcount=412
laidaxin 2ndInit_Installer (For MB508)
http://forum.xda-developers.com/showthread.php?t=1471549
2) Compile Cyanogen kernel or MIUI (For OMAP-3410)
Flipout's bootloader is locked. So...
3) try to boot kernel
Flipout's bootloader is locked. So...
4) port cyanogen/miui
Maybe you can ask laidaxin.
He would ready to port MB502.
He already port CM7 to MB508 success.
I hope this was useful to you
Click to expand...
Click to collapse
my recovery can't run in 2.1ROM,and the other two can't update ZIP because it can't mount system partion. I still finding the recovery and try to make a one that can help me to update to CM7 for MB502.

vladtdr said:
very good ideea, but the bootloader is still locked
Click to expand...
Click to collapse
The bravo and defy bootloader is locked yet I can flash a defy rom by deleting boot.img and devtree.img then it should be fine.
sent from my Motorola Bravo running CM7 White Rabbit Edition 1.3 with my added Beats Audio and Bravia Engine!

laluth said:
1) Use recover 'Open Recovery' or 2ndboot
Dexter_nlb FlipOut Recovery (CWM based v2.5.1.2)
http://forum.xda-developers.com/showthread.php?t=942160
polovinamozga Big Bootstrapped Recovery
http://forum.xda-developers.com/showpost.php?p=14796425&postcount=412
laidaxin 2ndInit_Installer (For MB508)
http://forum.xda-developers.com/showthread.php?t=1471549
Click to expand...
Click to collapse
Has someone fully tested any of these recovery
full backup and full restore?

laidaxin said:
my recovery can't run in 2.1ROM,and the other two can't update ZIP because it can't mount system partion. I still finding the recovery and try to make a one that can help me to update to CM7 for MB502.
Click to expand...
Click to collapse
I just done by hand boot using Big Bootstrapped Recovery method (looking source code) - and I saw some wrong mount methods. So I could I help you and maybe we can make a mod together.
I have a CWM functional om my MB511 but I don't figure out how to do next step (port CM/MIUI),
What I did:
1) copy necessary files https://github.com/iuridiniz/CharmBootstrap/assets
Code:
adb push hijack/ /sdcard/hijack
2) backup everything (adb shell as root)
Code:
#!/bin/sh
BACKUP_DIR=/sdcard/backup-`date +%s`
mkdir $BACKUP_DIR
echo "
/cdrom/cdrom_vfat.bin
/system/bin/mot_boot_mode
/sbin/adbd
/sbin/e2fsck
/sbin/fix_permissions
/sbin/killrecovery.sh
/sbin/mke2fs
/sbin/nandroid-md5.sh
/sbin/parted
/sbin/postrecoveryboot.sh
/sbin/recovery
/sbin/sdparted
/sbin/tune2fs
" | \
while read i; do
if [ -n "$i" ]; then
cp $i $BACKUP_DIR
fi
done
Figure out which partition has /system and /cdrom using mount
Code:
mount
output:
Code:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock7 /system yaffs2 ro 0 0
/dev/block/mtdblock9 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock8 /cache yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock6 /cdrom yaffs2 rw 0 0
tmpfs /tmp tmpfs rw,size=2048k 0 0
/dev/block/mtdblock0 /pds yaffs2 rw,nosuid,nodev 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw 0 0
/dev/block/vold/179:2 /data/sdext2 vfat rw,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,errors=remount-ro 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
system: /dev/block/mtdblock7 (in ro mode, need change)
cdrom: /dev/block/mtdblock6 (in rw mode, no change)
Install HIJACK BOOTSTRAP
Code:
##########################################################################
# HIJACK
mount -oremount,rw /dev/block/mtdblock7 /system
cp /sdcard/hijack/mot_boot_mode.bin /system/bin/mot_boot_mode.bin ;
cp /sdcard/hijack/hijack /system/bin/hijack ;
rm /system/bin/mot_boot_mode
ln -s hijack /system/bin/mot_boot_mode
mount -oremount,ro /dev/block/mtdblock7 /system
Install clockworkmode
Code:
################################################################3
# RECOVERY
#mount -oremount,rw /dev/block/mtdblock6 /cdrom
rm /cdrom/cdrom_vfat.bin
mkdir /cdrom/recovery
cp /sdcard/hijack/update-binary /cdrom/recovery/update-binary
cp /sdcard/hijack/update.zip /cdrom/recovery/recovery.zip
cp /sdcard/hijack/hijack /cdrom/recovery/hijack
cp /sdcard/hijack/mot_boot_mode.bin /cdrom/recovery/logwrapper
#mount -oremount,ro /dev/block/mtdblock6 /cdrom
Now If I want to boot in recovery mode I need to create this file /data/.recovery_mode
Code:
echo 1 > /data/.recovery_mode
Thanks to polovinamozga

To port a CM7 ROM,the recovery is the first,but we still need a way to look at the logcat during booting the system,and a way to copy the .rc files to /sbin.These three things are most important!
maybe we need a 2nd-init boot thing that can only success to ports the CM,I still working on this.
if you want to work with me,pleast sent email to [email protected].

laidaxin said:
To port a CM7 ROM
Click to expand...
Click to collapse
But without upgrading the kernel will be possible to run CM7 (Gingerbread) ? I think that only CM6 (Froyo) will be possible.
Charm already has Froyo?

Defy CM9 came run with the 2.2 froyo kernel,why charm or filpout cant run 2.3 with the 2.1 kernel?
It is possable to build and run 2.3 with the older kernel.

laidaxin said:
Defy CM9 came run with the 2.2 froyo kernel,why charm or filpout cant run 2.3 with the 2.1 kernel?
Click to expand...
Click to collapse
I don't know, it's because all tutorial for defy CM9 I'found ask me to upgrade to 2.2 (from 2.1) before.

even froYo 2.2 would be such a difference! a lot of apps could be installed... do you really think you can make it! *____*

iuridiniz said:
I don't know, it's because all tutorial for defy CM9 I'found ask me to upgrade to 2.2 (from 2.1) before.
Click to expand...
Click to collapse
yes! Because some bin files can't run in the 2.1 system,like the bootmenu and the bootstrape recovery's bin files.
But the kernel can run the 2.3.So what we can do is to make a bootstrap recovery that can run in the 2.1 ROM and then jump to the 2.3.
It is difficult that we can't flash the kernel to the system,a hard work!

i think shuld bee a way to by-pass the boot loader ... no ?

spinky360 said:
i think shuld bee a way to by-pass the boot loader ... no ?
Click to expand...
Click to collapse
yes!!!This is what i do now,but so difficult that only me to work on this.

Geko90 said:
even froYo 2.2 would be such a difference! a lot of apps could be installed... do you really think you can make it! *____*
Click to expand...
Click to collapse
I agree with that! Even a 2.2 based firmware would make a difference on the Flipout, so even if Cyanogen Mod 6 is possible I would love to use it on our phone!
Of course, if CM7 is a realistic option I would prefer that

laidaxin said:
yes!!!This is what i do now,but so difficult that only me to work on this.
Click to expand...
Click to collapse
Ther is smth with wath to help u ?
on wath version of bootloader u are working ?

mark this thread for reading later on cellphone

laidaxin said:
yes!!!This is what i do now,but so difficult that only me to work on this.
Click to expand...
Click to collapse
HI,
I'll try to fix flipout recovery or bootstrap recovery on my ME511.
I've found source codes of these two recovery and tested the apk on my phone.
It seems that bootstrap recovery can backup and restore successfully, but flipout recovery can only backup, it has no response when starting to restore system partition.
I'll test them more and make a zip file to try to update it using recovery. And make some fix to let it works well on flipout or charm.
Sent from my U8500 using XDA
Edit1：
I've tested that flipout recovery can't restore successfully if bootstrap recovery is installed and then un-installed before flipout recovery is installed , but bootstrap recovery can restore successfully if flipout recovery is installed and then un-installed before bootstrap recovery is installed.
If bootstrap recovery is installed and then un-installed before flipout recovery, one way to let flipout recovery can restore again is flash sbf and start from the beginning.
Edit2：
update zip files using flipout recovery failed. I'll test bootstrap recovery after flash sbf and start from the beginning.

Razr I bootlogo

Hi all,
I fiddled around with the bootlogo.
There are the partitions mmcblk0p3 (ulogo) and 0p4 (logo). Format is RGB 24 bit, image data for both is 540x540 pixel starting at byte 536. You have to mirror the image horizontally to show it right.
Both logos seem to be signed. Exchanging ulogo for logo seems possible but sometimes gives an error, exchanging ulogo by modified ulogo gives "Service needed. Code corruped" image at boot. For me, this is a lot more convenient than the ugly BOOTLOADER UNLOCKED warning.
Disclaimer: I take no responsibility for any harm done by my above advice. You may permanently brick your phone by overwriting the wrong partition!
EDIT:
Please, people, all of you who do not know what they are doing here, DO NOT TRY.

Could you give me the necessary commands to do it? Is it dangerous - can it destroy our beloved raz?
Thx
Sent from my XT890 using xda app-developers app

Thorstenk said:
Could you give me the necessary commands to do it? Is it dangerous - can it destroy our beloved raz?
Click to expand...
Click to collapse
Yep, this really is dangerous. If for any reason your partition layout does not match mine, or you do anything wrong, you can overwrite the fastboot bootloader (that thing in partitions 1 and 2)
Code:
~ # /system/bin/parted /dev/block/mmcblk0 print
Model: MMC 008G92 (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 131kB 11.7MB 11.5MB bos
2 16.9MB 28.4MB 11.5MB bosbackup
3 33.7MB 34.7MB 1049kB ulogo
4 50.5MB 51.5MB 1049kB logo
5 52.6MB 64.1MB 11.5MB boot
6 69.3MB 80.9MB 11.5MB recovery
7 86.1MB 86.2MB 131kB cid
8 86.2MB 88.3MB 2097kB sp
9 88.3MB 96.7MB 8389kB panic
10 96.7MB 97.3MB 524kB devtree
11 97.3MB 97.8MB 524kB devtreeBackup
12 97.8MB 106MB 8389kB ext4 pds
13 106MB 107MB 524kB misc
14 107MB 778MB 671MB ext4 cache
15 778MB 935MB 157MB cdrom
16 935MB 2219MB 1283MB ext4 system
17 2219MB 7818MB 5600MB ext4 userdata
This is my partition layout. You should ALWAYS save any partition before overwriting. Save it persistent to your PC!
device: dd if=/dev/block/mmcblk0p3 of=/tmp/0p3backup
pc: adb pull /tmp/0p3backup
As I said overwriting the logo partitions does never give the possibility to show a customized logo as long as you don't have the private key to sign your logos.
If you do anything wrong, recovery procedure may be impossible or at least complicated (there is some kind of unbrick for razr i here on sda but I never tried that!)

Hi PosixCompatible,
thanks for the answer.
The second command is clear to me, executed in a cmd window.
Code:
device: dd if=/dev/block/mmcblk0p3 of=/tmp/0p3backup
pc: adb pull /tmp/0p3backup
But where does the first command to be run? Also in a cmd window?
This command just saves original ulogo block, right? (since identifier "mmcblk0p3" from your first post matches the command's )
Thx!

Andro1dism said:
Hi PosixCompatible,
thanks for the answer.
The second command is clear to me, executed in a cmd window.
Code:
device: dd if=/dev/block/mmcblk0p3 of=/tmp/0p3backup
pc: adb pull /tmp/0p3backup
But where does the first command to be run? Also in a cmd window?
This command just saves original ulogo block, right? (since identifier "mmcblk0p3" from your first post matches the command's )
Thx!
Click to expand...
Click to collapse
Bueno, yo tengo el "droid" como boot animación y no me trae problemas
Well, I have the "droid" as boot animation and brings me no problems
http://www.4shared.com/zip/R5taBL1sba/bootanimation.html
...es de mi disco.
is ... my record.
... también hay otra con sonido, pero no la probé todavía
There is another ... with sound, but not tried it yet
http://www.4shared.com/rar/AWtIVc-Nba/bootanimation_droid.html
Aclaro, la que tiene sonido no la he probado.
Clarify, the one I have not tested sound.

Thanks for the explanation - as I don't want to kill my phone I will probably not risk that. Let us know if you find a more safe way. The bootloader unlocked logo sucks!
Sent from my XT890 using xda app-developers app

Andro1dism said:
Hi PosixCompatible,
thanks for the answer.
The second command is clear to me, executed in a cmd window.
Code:
device: dd if=/dev/block/mmcblk0p3 of=/tmp/0p3backup
pc: adb pull /tmp/0p3backup
But where does the first command to be run? Also in a cmd window?
This command just saves original ulogo block, right? (since identifier "mmcblk0p3" from your first post matches the command's )
Thx!
Click to expand...
Click to collapse
maybe this tool can help you: http://forum.xda-developers.com/showthread.php?t=2653458
it contains the option flash bootloader image.

Thorstenk said:
Thanks for the explanation - as I don't want to kill my phone I will probably not risk that.
Click to expand...
Click to collapse
It is safe as long as you have a backup ready (I was taking a risk that maybe fastboot would not start with a wrong image - but as I have proved that now overwriting logos itself is safe) and do not overwrite the wrong partition.
The tool paulle linked does not help you. Flashing a wrong image by fastboot is not possible as it gets verified before being written to flash that therefore fails.
PatricioJP links just explain how to exchange the android bootanimation. That is the one which gets loaded by the user roms kernel/surfaceflinger and does not help us here.

Thanks!
So did you exchange the ulogo with logo partition just by dd one over the other? Do I have to specify the block size or is it just a dd if=logo partition of=ulogo partition ?
Thorsten
Sent from my XT890 using xda app-developers app

Thorstenk said:
Thanks!
So did you exchange the ulogo with logo partition just by dd one over the other? Do I have to specify the block size or is it just a dd if=logo partition of=ulogo partition ?
Click to expand...
Click to collapse
if=logo of=ulogo would (mostly) display the Motorola logo instead of the unlocked logo, yes. No additional options needed.
"mostly" because when in fastboot and selecting options from there, it gives an error message instead of the logo.
I personally modified some bytes in ulogo and flashed that back so I get the "service required" message.

----

---

ihaveabu said:
Just got the Axon 7. So far so good!
One weird quirk. There's no encryption menu in the Security section in Settings. Even the ZTE manual says you can find encryption settings on the phone, but they're not there.
The phone does not ask for a password/pattern to unlock the phone upon booting. Only at lockscreen.
Can anyone confirm if encrypting the Axon 7 is possible?
Click to expand...
Click to collapse
The device should have FDE by default, google mandates this if device is capable and rolling out with Android M. So it might be that the UI designers at ZTE did not port(translate) over the right panel since i think the Chinese models can't be encrypted. The option also might have been moved. And the ZTE bootloader does not implement startup passwords from what i know
See more here
https://source.android.com/security/encryption/
and
http://android.stackexchange.com/questions/127076/how-does-marshmallow-encryption-work-technically

----

ihaveabu said:
I see so the phone can be encrypted and not require a password/pattern at the boot screen?
Click to expand...
Click to collapse
Similar to self-encrypting disks, the /data "is" always encrypted, it's just that when you have not set a lockscreen protection, it uses salted default password to decrypt it.

----

I was checking the boot.img and ramdisk and I just might have seen encryption related parameter in default.prop.
I will check again later. Or someone here will do that for us?
EDIT: This was inside fstab.qcom
Code:
# Android fstab file.
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
#TODO: Add 'check' as fs_mgr_flags with data partition.
# Currently we dont have e2fsck compiled. So fs check would failed.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1,discard wait,verify
# /dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,check,forceencrypt=footer
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,discard wait,check,forceencrypt=/dev/block/bootdevice/by-name/cryptkey
/dev/block/bootdevice/by-name/userdata /data ext4 nosuid,nodev,barrier=1,noauto_da_alloc,discard wait,check,forceencrypt=/dev/block/bootdevice/by-name/cryptkey
/devices/soc/74a4900.sdhci/mmc_host* /storage/sdcard1 vfat nosuid,nodev wait,voldmanaged=sdcard1:auto,encryptable=footer
/dev/block/zram0 none swap defaults zramsize=536870912
/dev/block/bootdevice/by-name/frp /frp emmc defaults defaults
# Usb Host
/devices/soc/6a00000.ssusb/6a00000.dwc3/xhci-hcd.0.auto* /storage/usbotg vfat nosuid,nodev wait,voldmanaged=usbotg:auto,encryptable=footer
Got also taht info form android stackexchange:
Only ext4 and f2fs filesystems currently support fast encryption. Added the forceencrypt flag to encrypt on first boot.
Click to expand...
Click to collapse

I can confirm that the Axon 7 is already encrypted. I just added my Android for Work profile on it, and it works flawlessly.

Would be nice if we could have a way to decrypt. Someone's going to have to make a kernel that supports that too. I run my my Nexus 6 decrypted. And while it doesn't make a huge difference, it does increas the device speed and boot time imo.

Glad to know the Axon 7 is already encrypted, but in case someone wants to know, there is still an option to encrypt device. It isn't found in the ZTE settings app, but a quick search using Action Launcher 3's activities widget led me to discover the device encryption option is still available. Just FYI.

----