Database Develop

[Recovery] Customized CWM 3.0.1.3 fake-flash with ext4 support (03/06/2011)

OK, here's the deal. This is my attempt in customizing CWM. It features several changes in comparison to one from CM source...
Changes
removed menu entries for updating via /sdcard/update.zip (useless for fake-flash users)
stripped some "No" line entries from confirmation menus
removed some insane size values from partitioning list
added some sane size values to partitioning list
added option to add 2nd ext partition (for some data2sd variants)
added block alignment to partitioning part
added advanced backup submenu
Plans
add block alignment to partitioning part
add advanced backup submenu
add some additional wipe options
Issues
mounting /sdcard again after unmounting not possible
Installation
Just copy this file to root of your SD card and rename it to update.zip. You can also use previous non-customized version.
Source
Source for this project is available on GitHub.
CAUTION! This is still in test phase. And your phone may explode suddenly if you're not careful enough. But in general it is pretty much safe (if you stand several feet from your phone). If you encounter any problems relevant logs are /tmp/recovery.log and /data/sdparted.log which I will need for debugging.

Hi BlaY0!
does this file works even on s-off legend?
Thx

goose2600 said:
Hi BlaY0!
does this file works even on s-off legend?
Thx
Click to expand...
Click to collapse
Yes. Have fun!

Thanks a lot for this
Sent from my Legend using Tapatalk

goose2600 said:
does this file works even on s-off legend?
Click to expand...
Click to collapse
Yes, but why would you do that???
So you buy a Ferrari and put in the engine of Fiat 600? I don't get it

Thanks man, it's great.

goose2600 said:
Hi BlaY0!
does this file works even on s-off legend?
Thx
Click to expand...
Click to collapse
Well, sort of. If you go to recovery via ROM manager, you will not get CWM 3.0.0.6 and if you go to recovery from HBOOT you will not get CWM 3.0.0.6.
The only way is to go to recovery and then choose "Apply update.zip".
So, yes, it works. But it's a bit tricky.

Thanks a lot!
Really helped me!

Fantastic. Great stuff!

This is Super! Been stuck with a rom with ext4 enabled for quite some time now. And this worked!
Blay0! your the man!
Sent from my Legend using XDA App

thanks!but i don't understand !!!I'm not good at these things
i have update the file by recovery and now?where should I set???

No, you have only to put the update.zip on SD-card and that´s it.
Than you have CWM recovery in version 3.0.0.6...

My ext4 partition still can't mount. Is there any way to collect recovery logs or something?

CfYz said:
My ext4 partition still can't mount. Is there any way to collect recovery logs or something?
Click to expand...
Click to collapse
You can run
Code:
adb shell dmesg
just after trying to mount the sd-ext. Then put it in this thread.
BTW, BlaY0, if i correctly understood, in your B ROM ext4 creates with huge_files option. My ext4 partition was created being under your rom, and all had run smooth except current CWM could not mount partition saying
Code:
<6>[ 37.128723] yaffs: dev is 187695106 name is "mmcblk0p2"
<6>[ 37.128936] yaffs: passed flags ""
<4>[ 37.129150] yaffs: Attempting MTD mount on 179.2, "mmcblk0p2"
<6>[ 37.129791] yaffs: dev is 187695106 name is "mmcblk0p2"
<6>[ 37.130004] yaffs: passed flags ""
<4>[ 37.130371] yaffs: Attempting MTD mount on 179.2, "mmcblk0p2"
<3>[ 37.131561] EXT4-fs: mmcblk0p2: Filesystem with huge files cannot be mounted read-write without CONFIG_LBD.
until i turned this option off. Under working system with your kernel/modules ext4 mounts good even with huge_file option.

saw81 said:
thanks!but i don't understand !!!I'm not good at these things
i have update the file by recovery and now?where should I set???
Click to expand...
Click to collapse
as picz mentioned, you put this file in the root of your sd card.
than you switch off your phone. than on it holding the Vol- and the power button. Than select recovery. ant the red [!] screen. press Vol+ and the power button. wait for a blue menu list at the top of the screen. than select update.zip...
this is Fake Flash....

BlaY0 said:
OK, I made this update to S-ON recovery that adds ext4 support. Flash it just after you enter CWM. Test and report...
PS: This is temporary solution.
Click to expand...
Click to collapse
working perfectly. i've successfully backup and restore a CM7 with TGF's ext4 data2ext mod. everything works normal.

Kot_Ik said:
BTW, BlaY0, if i correctly understood, in your B ROM ext4 creates with huge_files option. My ext4 partition was created being under your rom, and all had run smooth except current CWM could not mount partition saying
Code:
<6>[ 37.128723] yaffs: dev is 187695106 name is "mmcblk0p2"
<6>[ 37.128936] yaffs: passed flags ""
<4>[ 37.129150] yaffs: Attempting MTD mount on 179.2, "mmcblk0p2"
<6>[ 37.129791] yaffs: dev is 187695106 name is "mmcblk0p2"
<6>[ 37.130004] yaffs: passed flags ""
<4>[ 37.130371] yaffs: Attempting MTD mount on 179.2, "mmcblk0p2"
<3>[ 37.131561] EXT4-fs: mmcblk0p2: Filesystem with huge files cannot be mounted read-write without CONFIG_LBD.
until i turned this option off. Under working system with your kernel/modules ext4 mounts good even with huge_file option.
Click to expand...
Click to collapse
Yeah, formatting ext4 partition under B or CM adds "huge_file" to the filesystem features by default. Actually this is default for mke2fs config (will be changed in the next B release). My customized and also CM kernal got this LBD alias LBDAF support built in but stock kernel from recovery doesn't hence the error. Unfortunately LBD support can't be built as a module so there is actually no way to add this support to stock recovery if your Legend is S-ON.
But... since LBD alias LBDAF and consequently "huge_file" support in ext4 is actually support for files bigger than 2TB we kinda don't need it I guess so what we can do is as you suggested remove "huge_file" feature from ext4 filesystem like this:
Code:
tune2fs -O ^huge_file /dev/block/<ext4_partition>
e2fsck -pf /dev/block/<ext4_partition>
...and we do this via recovery or system but ext4 partition shouldn't be mounted at that point! So unmount it first or disable data2ext/a2sd and reboot, do da above job, enable data2ext/a2sd and reboot again. To check if "huge_file" feature is actually enabled in your ext4 filesystem you do:
Code:
tune2fs -l /dev/block/<ext4_partition>
...and check "Filesystem features:" line.

Customized CWM 3.0.0.6 for S-ON Legends (fake-flash)
OK, here's the deal. This is my attempt in customizing CWM.
Check 1st post for update!

hi BlaY0 !
can you release img for S-off users ? (i know we can use this but i like IMG)

New update. Check 1st post.
jinxul said:
hi BlaY0 !
can you release img for S-off users ? (i know we can use this but i like IMG)
Click to expand...
Click to collapse
No, I decided not to. Will stick to fake-flash. But if you want, you can do it yourself and post it here...
EDIT: Rather post img in the other thread.

[DEV] Kazam Thunder Q4.5 Development Thread {CWM} {SYS-IMG}

So I was at XDA DevCon and Kazam donated me one of their Thunder Q4.5 devices, I'm going to be doing my best to bring much loved XDA goodies to this device, there is no time schedule or eta's, this will go at the pace at which I can go!
I am aware that a few others won the Thunder Q4.5 during giveaways, so if you want to help in getting some development love on this device then feel free. I'm also aware that a lot of people probably don't own this device, so if it's just me documenting and bringing things to the device then so be it!
System
I've gained root and dumped /system, available here for inspecting: https://www.androidfilehost.com/?fid=23681161096071461
Recovery & Boot
CWM Recovery working on the Kazam Thunder 4.5Q
You need MTK Droid Root & Tools to install:
1) Select the "root, backup, recovery" tab
2) Select the "Install already prepared files" button and hit "Recovery and Boot"
3) For the Boot.img select the downloaded Boot.img below and for recovery select the Recovery.img below.
4) When you get the "Install patched boot to phone" window, select "Yes"
5) When you get to "Install created recovery" select "Yes".
6) When asked to reboot into recovery, that is down to you!
7) Profit!
Recovery: https://www.androidfilehost.com/?fid=95747613655040353
Patched Boot Img: https://www.androidfilehost.com/?fid=95747613655040352
Old Documentation:
This is where some tricky stuff is, I've never dealt with a device that doesn't have a dedicated /recovery other than Xperia who combine it with /boot though that is easy to deal with.
As we can see here:
Code:
Partition Information:
preloader 0x0000000000c00000 0x0000000000000000 2 /dev/misc-sd
mbr 0x0000000000080000 0x0000000000000000 2 /dev/block/mmcblk0
ebr1 0x0000000000080000 0x0000000000080000 2 /dev/block/mmcblk0p1
pro_info 0x0000000000300000 0x0000000000100000 2 /dev/block/mmcblk0
nvram 0x0000000000500000 0x0000000000400000 2 /dev/block/mmcblk0
protect_f 0x0000000000a00000 0x0000000000900000 2 /dev/block/mmcblk0p2
protect_s 0x0000000000a00000 0x0000000001300000 2 /dev/block/mmcblk0p3
seccfg 0x0000000000020000 0x0000000001d00000 2 /dev/block/mmcblk0
uboot 0x0000000000060000 0x0000000001d20000 2 /dev/block/mmcblk0
bootimg 0x0000000000600000 0x0000000001d80000 2 /dev/block/mmcblk0
recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0
sec_ro 0x0000000000600000 0x0000000002980000 2 /dev/block/mmcblk0p4
misc 0x0000000000080000 0x0000000002f80000 2 /dev/block/mmcblk0
logo 0x0000000000300000 0x0000000003000000 2 /dev/block/mmcblk0
ebr2 0x0000000000080000 0x0000000003300000 2 /dev/block/mmcblk0
expdb 0x0000000000a00000 0x0000000003380000 2 /dev/block/mmcblk0
android 0x000000002bc00000 0x0000000003d80000 2 /dev/block/mmcblk0p5
cache 0x0000000007e00000 0x000000002f980000 2 /dev/block/mmcblk0p6
usrdata 0x0000000040000000 0x0000000037780000 2 /dev/block/mmcblk0p7
fat 0x000000006fc00000 0x0000000077780000 2 /dev/block/mmcblk0p8
bmtpool 0x0000000001500000 0x00000000ff3f00a8 2 /dev/block/mmcblk0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc boot (null) 0
2 /cache ext4 /dev/block/mmcblk0p6 (null) 0
3 /data ext4 /dev/block/mmcblk0p7 (null) 0
4 /misc emmc misc (null) 0
5 /recovery emmc recovery (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p8 0
7 /system ext4 /dev/block/mmcblk0p5 (null) 0
8 /sdcard2 vfat /dev/block/mmcblk0p8 (null) 0
mbr, pro_info, nvram, seccfg, uboot, bootimg, recovery, misc, logo, ebr2, expdb, bmtpool
These are all in /dev/block/mmcblk0 and we want hold of bootimg and recovery as these are the important ones!
There is a hexadecimal offset of some sort by the looks of things:
Code:
recovery 0x0000000000600000 0x0000000002380000 2 /dev/block/mmcblk0
Converting these in to deciaml values give:
Code:
recovery 6291456 37224448 2 /dev/block/mmcblk0
The issue lies with the fact that this looks like over 2gig or something, a recovery image is not that big, should be <10mb.

Awesome, I wondered if anyone would be posting work for kazam.
I'm hoping to move onto mtk after L drops (specifically the upcoming kazam device).
Do you remember the name of the guy who was at the booth?

cybojenix said:
Awesome, I wondered if anyone would be posting work for kazam.
I'm hoping to move onto mtk after L drops (specifically the upcoming kazam device).
Do you remember the name of the guy who was at the booth?
Click to expand...
Click to collapse
Yeah I think he was called David, I've got his card around somewhere. He said he'd send me kernel source but haven't heard anything.
I don't think there are many people supporting it haha
I'll be doing what I can regarding mtk, kazam and L when it drops

matt4321 said:
Yeah I think he was called David, I've got his card around somewhere. He said he'd send me kernel source but haven't heard anything.
I don't think there are many people supporting it haha
I'll be doing what I can regarding mtk, kazam and L when it drops
Click to expand...
Click to collapse
@dave79
I have the source code, but I'm having serious problems in compiling it (Thunder2 5.0) - haven't set it up on git yet but below is the shared dropbox folder, looks like your email address is "pending" on the shared options (maybe check your email?).
https://www.dropbox.com/sh/aj0tjqzh9fzsf57/AABCgx-Yhc71CVjTcmRkM9P2a?dl=0
To build the kernel for Thunder2_50, you will need the dct folder I put in Tools - this took me ages to find and edit for the MT6582 chip (the original I downloaded didn't like the codegen file for konka82_wet_i277), for the ThunderQ 4.5 you should be OK though, I noticed a lot of stuff is missing in the Thunder2_50 source code...

Hi there,
This is Dave from Kazam. Let me know if there's anything else you need. I'll gladly share the source code of the Q4.5, just PM me with your email and I'll share my Dropbox link. (I'll upload it here when I get back from my vacation (oh yeah, I'm in Spain ).
Thanks all
Dave

Jonny said:
@dave79
I have the source code, but I'm having serious problems in compiling it (Thunder2 5.0) - haven't set it up on git yet but below is the shared dropbox folder, looks like your email address is "pending" on the shared options (maybe check your email?).
https://www.dropbox.com/sh/aj0tjqzh9fzsf57/AABCgx-Yhc71CVjTcmRkM9P2a?dl=0
To build the kernel for Thunder2_50, you will need the dct folder I put in Tools - this took me ages to find and edit for the MT6582 chip (the original I downloaded didn't like the codegen file for konka82_wet_i277), for the ThunderQ 4.5 you should be OK though, I noticed a lot of stuff is missing in the Thunder2_50 source code...
Click to expand...
Click to collapse
Wow the 4.2 mtk code base really sucks. I'm glad it's a lot better with 4.4, and I hear all the hals now work against aosp.
Thanks for uploading the sources here

I'm about to embark on the challenge of porting CM12/AOSP L to the thunder q4.5, I shall make a seperate forum thread for this project as of when I get a first build, any volunteers for testing my ports of CM12 would be great, pm me if interested, and then I'll give you a download to the first flashable zip i get compiled. Also, just to make you guys aware when flashing, if you decide to take any of my ports, I will be configuring it to install TWRP along with CM12, incase you don't already have TWRP installed, it shall be installed when flashing.
Also, this may take some time to create even an initial release, as to quote Dees_Troy on irc earlier "Porting CM to MediaTek devices is a *****"
Also, if I get the time, then I will continue to update a cm12 for this device as often as I can, I will eventually have a dropbox shared folder publicly accessible with all the versions made so far available to download.
@matt4321 You're not the only one working on bringing XDA loved stuff to this device
Note: if we can get a separate forum for the thunder q4.5, I will be moving this post to a new thread over there. Also, anyone interested in being alpha/beta testers, pm me and I'll add you to the shared dropbox where I will be uploading all the builds, as I get round to making them

Help! I flashed recovery and camera stopped working! Is there a way to bring it back to it's out-of-the-box state? (with original recovery and stuff) IT'S URGENT!!!!

drumandbassfreak said:
Help! I flashed recovery and camera stopped working! Is there a way to bring it back to it's out-of-the-box state? (with original recovery and stuff) IT'S URGENT!!!!
Click to expand...
Click to collapse
That's really weird, mine works fine. Try doing it again and see what happens. Well you'd need to flash back to stock. I don't actually have the stock files unfortunately, ask in the Q&A section to see if anyone has the stock recovery and kernel

Thanks, I'm gonna do it! I know thats weird, how in the world would be the recovery related to the camera??

How do I open The IMG that you uploaded. PowerISO says it is corrupted

drumandbassfreak said:
How do I open The IMG that you uploaded. PowerISO says it is corrupted
Click to expand...
Click to collapse
You need to mount it in Ubuntu or a similar distro to access it. That's how I did it.

Well I finally sent it to repair service, but I wanna know. Is there a way to backup stock boot and recovery IMG's? (in case i screw it up again)

drumandbassfreak said:
Well I finally sent it to repair service, but I wanna know. Is there a way to backup stock boot and recovery IMG's? (in case i screw it up again)
Click to expand...
Click to collapse
I have the factory images here https://drive.google.com/folderview?id=0B1SOxwG8KsFkMFdicjdEQXEzMTA# to use em, just flash with sp flash tools or mtk droid root and tools
Sent from my KAZAM Thunder Q45 using XDA Free mobile app

How do I enter flash mode?

ROM MIUI V5 for KAZAM THUNDER Q4.5
I'm glad to announce that I successfully ported Miui ROM for Kazam, download link will be available soon. Send me a email for request ROM

Possible explanation why nexus 5 didn't have the new device protection

So, just posted this a while ago at reddit, and some guy over there points out that maybe XDA is better place for this.
I'm just realized this afternoon by looking my android one device (sprout_b, indonesian version).
The Indian version (sprout) got updated to lollipop, and have the new device protection. Even if I flashed and used the said update on my device, I can't use the new device protection.
So I tried to compare both system files and boot.img, and found 1 partition missing on my device, FRP.
I investigated more about this, and it seems that both nexus 6 and 9 got this partition too (under the name PST).
And then, wild sudden clarity appears! FRP = Factory Reset Protection.
So, both my devices (nexus 5 and nexian journey 1 -android one- ) probably didn't receive this protection, because the partition needed for it isn't there.
For more info, here's the fstabs from both android one branch (sprout and sprout_b):
sprout:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# 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
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/oem /oem ext4 ro,context=u:object_r:oemfs:s0,nosuid,nodev wait
/devices/platform/mtk-msdc.1/mmc_host* auto vfat defaults voldmanaged=sdcard0:auto,noemulatedsd
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults defaults
sprout_b:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# 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
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/oem /oem ext4 ro,context=u:object_r:oemfs:s0,nosuid,nodev wait
/devices/platform/mtk-msdc.1/mmc_host* auto vfat defaults voldmanaged=sdcard1:auto
FRP is also mentioned in file_contexts file in boot.img:
Code:
/dev/block/mmcblk0p18 u:object_r:frp_block_device:s0
So, what do you guys think?

So its a hardware partition that attaches itself to a google account? pardon my knwledge..m a dental surgeon..

Interesting. Creating a FRP partition by taking away some space from userdata would not hurt.
The rest is to find the files which responsible to the factory reset protect.

bitdomo said:
Interesting. Creating a FRP partition by taking away some space from userdata would not hurt.
The rest is to find the files which responsible to the factory reset protect.
Click to expand...
Click to collapse
there's also this build.prop entry:
Code:
ro.frp.pst=/dev/block/platform/mtk-msdc.0/by-name/frp
in case of nexus 6:
Code:
ro.frp.pst=/dev/block/platform/msm_sdcc.1/by-name/frp
and nexus 9:
Code:
ro.frp.pst=/dev/block/platform/sdhci-tegra.3/by-name/PST
also, this article.

awaaas said:
there's also this build.prop entry:
Code:
ro.frp.pst=/dev/block/platform/mtk-msdc.0/by-name/frp
in case of nexus 6:
Code:
ro.frp.pst=/dev/block/platform/msm_sdcc.1/by-name/frp
and nexus 9:
Code:
ro.frp.pst=/dev/block/platform/sdhci-tegra.3/by-name/PST
also, this article.
Click to expand...
Click to collapse
What is the size of the FRP partition?
Can you light me up what is this factory reset protection actually do? Does it prevent to perfrom a factory reset or event after you do factory reset you still have to enter the pin lock or enter the pattern? How do you enable it on a supported device? How do you know it is enabled?

bitdomo said:
Can you light me up what is this factory reset protection actually do? Does it prevent to perfrom a factory reset or event after you do factory reset you still have to enter the pin lock or enter the pattern? How do you enable it on a supported device? How do you know it is enabled?
Click to expand...
Click to collapse
I believe it will not let you factory reset the device unless you enter your Google account username and password.

bitdomo said:
What is the size of the FRP partition?
Can you light me up what is this factory reset protection actually do? Does it prevent to perfrom a factory reset or event after you do factory reset you still have to enter the pin lock or enter the pattern? How do you enable it on a supported device? How do you know it is enabled?
Click to expand...
Click to collapse
Let say that X's phone is stolen by Y, Y then proceed to factory reset the phone from recovery mode because the lockscreen is protected by a password.
The system will let Y to do that, but, upon starting the system, the setup wizard will not allow him to pass unless you gave him the last google account username and password that was active on that phone.
Bootloader is locked and you must toggle the unlock state in developer options (like nexus 6), so no custom recovery to wipe the frp partition, and re-flashing with factory image also doesn't touching that partition too.
From android police
I don't have a device that support it, but will search about the size around.

awaaas said:
Let say that X's phone is stolen by Y, Y then proceed to factory reset the phone from recovery mode because the lockscreen is protected by a password.
The system will let Y to do that, but, upon starting the system, the setup wizard will not allow him to pass unless you gave him the last google account username and password that was active on that phone.
Bootloader is locked and you must toggle the unlock state in developer options (like nexus 6), so no custom recovery to wipe the frp partition, and re-flashing with factory image also doesn't touching that partition too.
From android police
I don't have a device that support it, but will search about the size around.
Click to expand...
Click to collapse
I played a little.
I made frp partition. As I saw from the previous link it is a 512 kb large unformated partition.
I built a kernel with adding the frp partition to the fstab and context file.
I edited the build.prop to add the ro.frp.pst string.
I could not make it work, but some data appeared on the frp partition. 35 bytes of data
I am lost at the moment what else I could do. I should somehow get logs but have no idea what I have to look for in dmesg or logcat.
Maybe there are some libs and scripts? Or we need some reverse engineering? Or it needs stock rom? Anyone knows if this feature works on the custom roms of nexus 6 or 9?

bitdomo said:
I played a little.
I made frp partition. As I saw from the previous link it is a 512 kb large unformated partition.
I built a kernel with adding the frp partition to the fstab and context file.
I edited the build.prop to add the ro.frp.pst string.
I could not make it work, but some data appeared on the frp partition. 35 bytes of data
I am lost at the moment what else I could do. I should somehow get logs but have no idea what I have to look for in dmesg or logcat.
Maybe there are some libs and scripts? Or we need some reverse engineering? Or it needs stock rom? Anyone knows if this feature works on the custom roms of nexus 6 or 9?
Click to expand...
Click to collapse
maybe the GServices check for the device?, also take a look at the note edge, the OTA to Lollipop on the sprint variant has an interesting comment
Added Factory Reset Protection. so by this thread, it also got the device protection feature?

bitdomo said:
I played a little.
I made frp partition. As I saw from the previous link it is a 512 kb large unformated partition.
I built a kernel with adding the frp partition to the fstab and context file.
I edited the build.prop to add the ro.frp.pst string.
I could not make it work, but some data appeared on the frp partition. 35 bytes of data
I am lost at the moment what else I could do. I should somehow get logs but have no idea what I have to look for in dmesg or logcat.
Maybe there are some libs and scripts? Or we need some reverse engineering? Or it needs stock rom? Anyone knows if this feature works on the custom roms of nexus 6 or 9?
Click to expand...
Click to collapse
In the article I mentioned earlier, it mentioned the new service for this, android.service.persistentdata.IPersistentDataBlockService (frameworks/base/services/core/java/com/android/server/PersistentDataBlockService.java) for it to be active.
Also, for sprout, I had to dig in more:
So, in fstab.sprout, it listed like this:
Code:
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults defaults
and in file_contexts, it listed like this:
Code:
/dev/block/mmcblk0p18 u:object_r:frp_block_device:s0
after downloading several stock rom for sprout, I looked at their scatter file (like PIT for samsung devices), and didn't found about FRP partition. So, I searched about this mmcblk0p18 mentioned earlier in file_contexts, turns out it is actually a partition called "gen", and the size is 71.5 MB. This partition is actually available in my sprout_b device, yet the corresponding feature didn't work out.

awaaas said:
In the article I mentioned earlier, it mentioned the new service for this, android.service.persistentdata.IPersistentDataBlockService (frameworks/base/services/core/java/com/android/server/PersistentDataBlockService.java) for it to be active.
Also, for sprout, I had to dig in more:
So, in fstab.sprout, it listed like this:
Code:
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults defaults
and in file_contexts, it listed like this:
Code:
/dev/block/mmcblk0p18 u:object_r:frp_block_device:s0
after downloading several stock rom for sprout, I looked at their scatter file (like PIT for samsung devices), and didn't found about FRP partition. So, I searched about this mmcblk0p18 mentioned earlier in file_contexts, turns out it is actually a partition called "gen", and the size is 71.5 MB. This partition is actually available in my sprout_b device, yet the corresponding feature didn't work out.
Click to expand...
Click to collapse
Awesome! I am checking the source code of the persistent datablock service. Now atleast I know what do I have to look for to find errors (hope i will find).
I will give it a try tomorrow. My poor phone was wiped like 10 times today.

I could not rest.... my mind was constantly ticking on this.
Well this is something.
I tell the rest tomorrow, but at first look it is working. It didnt let me pass by entering other email addresses it just jumped back to the wifi selection mode without saying anything (is that normal?). Anyway after I loged in with my google account it let me pass.

I got it working without making any new partition.
I am using the partition called "grow", 5,5 kiB in size, as it is not being used by or for anyithing. It looks like that amount of space is enough.
What I did to make it work:
I went back to stock LMY47I rom from my AOSP rom.
I added this line to /system/build.prop:
Code:
ro.frp.pst=/dev/block/platform/msm_sdcc.1/by-name/grow
I extracted the kernel's ramdisk and added the folowing lines to the following files:
fstab.hammerhead
Code:
/dev/block/platform/msm_sdcc.1/by-name/grow /peristent emmc defaults
file_contexts
Code:
/dev/block/platform/msm_sdcc\.1/by-name/grow u:object_r:frp_block_device:s0
ueventd.hammerhead.rc
Code:
/dev/block/platform/msm_sdcc.1/by-name/grow 0600 system system
Then I packed the kernel (get it) and flashed it to the phone.
I added these changes to the hammerhead device tree if someone is intrested.

awaaas said:
Bootloader is locked and you must toggle the unlock state in developer options (like nexus 6), so no custom recovery to wipe the frp partition, and re-flashing with factory image also doesn't touching that partition too.
Click to expand...
Click to collapse
So 'fastboot oem unlock' no longer works? With that you could load a custom recovery and wipe any partition.

frankusb said:
So 'fastboot oem unlock' no longer works? With that you could load a custom recovery and wipe any partition.
Click to expand...
Click to collapse
Fastboot oem unlock will be disallowed by default. You must toggle the option under developer settings to be able to do that.

awaaas said:
Fastboot oem unlock will be disallowed by default. You must toggle the option under developer settings to be able to do that.
Click to expand...
Click to collapse
It will be disallowed by default? By the Nexus 5 boot loader? In what cases? It either is or it isn't today. I can't try it on my Nexus 5.
I looked for that option under development options on my Nexus 5 and did not find anything.

frankusb said:
It will be disallowed by default? By the Nexus 5 boot loader? In what cases? It either is or it isn't today. I can't try it on my Nexus 5.
I looked for that option under development options on my Nexus 5 and did not find anything.
Click to expand...
Click to collapse
That option comes up only if you have a dedicated frp partition, but for nexus 5 it is useless to enable or disable it because the bootloader will not check the OEM enable bit on the dedicated frp partition unlike nexus 6's bootloader.

frankusb said:
It will be disallowed by default? By the Nexus 5 boot loader? In what cases? It either is or it isn't today. I can't try it on my Nexus 5.
I looked for that option under development options on my Nexus 5 and did not find anything.
Click to expand...
Click to collapse
that is the case of nexus 6 (and probably 9).
Today, my Indonesian android one device got update to LMY47O, and lazy google is lazy, they didn't rip out the device protection option bit from my device, it didn't work at the first place. They didn't even bother to edit the boot.img ramdisk, leaving Indian setting there.

formatted /persist and /firmware

Hello everyone, last night i was trying the PhilZ Touch CWM recovery and in the wipe section it has an option to format /persist and /firmware, so being very stupid i formatted those partitions and when i tried to install a new rom i couldn't connect to wifi, i fixed that with this http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308 and everything seems to work perfectly in stock rom, i must admit i was very afraid, but now i'm curious because i search a little and others phones have drm files or more folders (i only have a lost+found folder and to 2 more .bin archives) and i was wondering if any of you ever had done the same as me or know more about it and could help me if i'll have problems in the future for my stupid behavior. Thanks

kievam said:
Hello everyone, last night i was trying the PhilZ Touch CWM recovery and in the wipe section it has an option to format /persist and /firmware, so being very stupid i formatted those partitions and when i tried to install a new rom i couldn't connect to wifi, i fixed that with this http://forum.xda-developers.com/moto-x/moto-x-qa/moto-x-xt1060-issues-wifi-bluetooth-t2813308 and everything seems to work perfectly in stock rom, i must admit i was very afraid, but now i'm curious because i search a little and others phones have drm files or more folders (i only have a lost+found folder and to 2 more .bin archives) and i was wondering if any of you ever had done the same as me or know more about it and could help me if i'll have problems in the future for my stupid behavior. Thanks
Click to expand...
Click to collapse
/firmware = modem = flash NON-HLOS.bin from stock package.
And this is how /persist should look like:
Code:
[email protected]:/persist # find
.
./lost+found
./WCNSS_qcom_wlan_factory_nv.bin
./WCNSS_qcom_wlan_nv.bin
./sensors
./sensors/sensors_settings
./.bt_nv.bin
./prov
./prov/randomString1_
./prov/randomString1_/randomString2_
./prov/randomString1_/randomString3_
./prov/randomString1_/randomString4_
./prov/randomString1_/randomString5_
./data
./data/app_g
./data/app_g/randomString1_
./data/app_g/randomString1_/randomString6_
./data/app_g/randomString1_/randomString7_
./data/app_g/randomString1_/randomString8_

LuK1337 said:
/firmware = modem = flash NON-HLOS.bin from stock package.
And this is how /persist should look like:
Code:
[email protected]:/persist # find
.
./lost+found
./WCNSS_qcom_wlan_factory_nv.bin
./WCNSS_qcom_wlan_nv.bin
./sensors
./sensors/sensors_settings
./.bt_nv.bin
./prov
./prov/randomString1_
./prov/randomString1_/randomString2_
./prov/randomString1_/randomString3_
./prov/randomString1_/randomString4_
./prov/randomString1_/randomString5_
./data
./data/app_g
./data/app_g/randomString1_
./data/app_g/randomString1_/randomString6_
./data/app_g/randomString1_/randomString7_
./data/app_g/randomString1_/randomString8_
Click to expand...
Click to collapse
Thank you so much for the answer!, i only have ./lost+found ./WCNSS_qcom_wlan_factory_nv.bin y ./.bt_nv.bin, any idea what are the others for?

kievam said:
Thank you so much for the answer!, i only have ./lost+found ./WCNSS_qcom_wlan_factory_nv.bin y ./.bt_nv.bin, any idea what are the others for?
Click to expand...
Click to collapse
No, I dunno.

Working Bootable recovery for the KFFOWI (Ford)

As you know, root has been achieved on this device. Now, let's move on to recovery. The recovery.img is a lot like the boot.img, in the way that you can boot from it. In theory, if we make a 3e recovery.bin for this device (TWRP/CWM), and we boot from it, we will be able to install any rom. Let's let the Recovery.bin development start!
THIS DEVICE DOES NOT SUPPORT FLASHING RECOVERIES. YOU HAVE TO BOOT FROM THEM IN FASTBOOT.​
This device now has 2 custom recoveries, those 2 being TWRP (Team Win Recovery Project) and CM (CyanogenMod) Recovery. CyanogenMod recovery is much like the stock recovery, with the only difference being that CM Recovery can install files that don't have the Amazon ZIP Signature. TWRP, on the other hand, has a touchscreen display, and is much more user friendly than CM Recovery. The links to both are here:
CM Recovery
TWRP
You can do many things in a Custom Recovery, such as:
Install custom ROMs (Found here)
Install modifications to your current OS (XPosed Framework, Root, etc.)
Install GAPPS (Google Applications, including Play Store and Play Services)
Wipe your current ROM
Backup your current ROM
Restore a backup of a previous ROM
If you have any questions, ask them here.
Now, press the thank button here and thank the developers that made these recoveries and ROMs possible, and you are good to go.
Good Luck!

Im dumping the recovery partition right now as well as the boot as well and the other two extra bootloader stuff that may help us

I have attached the images we can use. I dont know if we need the system image file but if we do just let me know hopefully ill be able to upload it or someone else might cause its 1 GB it may take some time.

Awesomeslayerg said:
I have attached the images we can use. I dont know if we need the system image file but if we do just let me know hopefully ill be able to upload it or someone else might cause its 1 GB it may take some time.
Click to expand...
Click to collapse
Well, we just need someone to build a recovery for this device. Once that is bootable, we can install roms. Also, since we will most likely not be able to unlock the bootloader, Safestrap might be our best bet.

True.. it's a mediatek soc so there's gotta be a way to unlock the bootloader because most of the mediatek devices have unlocked bootloader I think. And besides it gives us an unlock code so we need to see what that deal is

Just leaving here partitions structure:
Model: MMC 8GND3R (sd/mmc)
Disk /dev/block/mmcblk0: 7818MB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 2097kB 1049kB KB
2 2097kB 3146kB 1049kB DKB
3 3146kB 21.4MB 18.2MB EXPDB
4 21.4MB 22.4MB 1049kB UBOOT
5 22.4MB 39.2MB 16.8MB boot
6 39.2MB 56.0MB 16.8MB recovery
7 56.0MB 56.5MB 524kB MISC
8 56.5MB 60.2MB 3670kB LOGO
9 60.2MB 65.4MB 5243kB TEE1
10 65.4MB 70.6MB 5243kB TEE2
11 70.6MB 1329MB 1258MB ext4 system
12 1329MB 1591MB 262MB ext4 cache
13 1591MB 7818MB 6227MB ext4 userdata

Hmm it looks like the MTK Droid Root and Tools V2.5.3 works now so we can flash images via that as well as recovery AND boot. But someone should get a 2nd fire and try it out because we have no scatter file.
We could possibly install a 2nd bootloader

Awesomeslayerg said:
Hmm it looks like the MTK Droid Root and Tools V2.5.3 works now so we can flash images via that as well as recovery AND boot. But someone should get a 2nd fire and try it out because we have no scatter file.
We could possibly install a 2nd bootloader
Click to expand...
Click to collapse
I have made this one and test ro readback partitions bug gets error 2004
Partition lists
storage, boot_channel & block_size maybe not good
Model: MMC 8GND3R (sd/mmc)
storage: SDMMC ????
Sometimes tablet wont boot and have to remove battery connector
Last SP Flash TOOL, linux version have much errors and force to remove battery
http://firmware.su/51343-sp-flash-tool.html
DO NO USE TO DOWNLOAD ANYTHING
UNDER CONSTRUCTION
scatter updated, UNTESTED

Lets go recovery!

idme print as su
unlock_code:
---------- Post added at 12:09 PM ---------- Previous post was at 11:52 AM ----------
There are 2 boads type and 2 preloaders......
Mine have preloader_prod.img board_id: 0025001040000015
Code:
# check if production device
if ("0025001000000015" == read_file_str("/proc/idme/board_id") ||
"0025001000010015" == read_file_str("/proc/idme/board_id") ||
"0025001010000015" == read_file_str("/proc/idme/board_id") ||
"0025001010010015" == read_file_str("/proc/idme/board_id") ||
"0025001020000015" == read_file_str("/proc/idme/board_id"))
then
ui_print("Copying preloader.img to boot partition 0 for unsecure device...");
package_extract_file("images/preloader.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
else
ui_print("Copying preloader_prod.img to boot partition 0 for secure device...");
package_extract_file("images/preloader_prod.img", "/dev/block/platform/mtk-msdc.0/mmcblk0boot0");
endif;

my /proc/idme/board_id reads 0025001040000015

Can anyone try this: http://forum.xda-developers.com/showthread.php?t=2798257?
Sent from my KFFOWI using Tapatalk

I did yesterday didn't work

Awesomeslayerg said:
I did yesterday didn't work
Click to expand...
Click to collapse
Did you try Fastboot boot recovery.img with the one it gave?
Sent from my XT912 using Tapatalk

No I'll try today

Okay i used the MTK-TWRP thing right now and used it to unpack the recovery image and it looks like we can use this to our advantage to flash unverified files by editing some of the prop settings.

Can someone try this: http://xda-university.com/as-a-developer/porting-clockworkmod-recovery-to-a-new-device? It might work.

How would we flash it?

Awesomeslayerg said:
How would we flash it?
Click to expand...
Click to collapse
Zips are flashable in flashfire...

Awesomeslayerg said:
How would we flash it?
Click to expand...
Click to collapse
Use the following commands to flash the recovery
Code:
adb shell
su
dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
- I have Cyanogenmod Recovery working except a few minor niggles
- Let you know once it's fully working
- It looks like we can't boot unsigned images that are flashed to the recovery partition
- If I boot the image from fastboot rather than flashing it then it works
- CVE-2014-0973 is patched in the bootloader