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.

MIUI_CM7 v2 and GApps Ported to SD Card, 03 Jul 2012

MIUI: http://www.mediafire.com/?oqvzpc61x3s5w44
GApps: http://www.mediafire.com/?1c2br6sw6330lwn
These flashable zips and corresponding procedure are intended for intermediate to advanced users, i.e. those who have 1) unlocked their Atrix, 2) partitioned their SD card for dual boot, and 3) have a working knowledge of ClockWorkMod (CWM) Recovery and how to install and configure dual boot. If you are not in this category or would simply like a refresher, you can review some of my other threads on this topic, namely:
Dual Boot threads:
http://forum.xda-developers.com/showthread.php?t=1651356
http://forum.xda-developers.com/showthread.php?t=1642185
http://forum.xda-developers.com/showthread.php?t=1645344
Please understand this MIUI port is not a “dual boot flashable zip” (DBFZ); rather it is a single boot flashable zip of MIUI ported to SD card. However it should preserve your existing primary ROM (ROM1) along with /cache and /data, and thus is actually more versatile than DBFZ which gives you two ROMs that you may not even want.
I strongly recommend that after flashing MIUI, you first reboot to MIUI before flashing GApps.
To reboot to ROM1 after installing MIUI, you could fastboot flash a ROM1 boot image (easiest and fastest way), or configure dual boot as described here ( http://forum.xda-developers.com/showthread.php?t=1645344 ) . I have often found it convenient to simply extract the /Boot directory of an existing DBFZ and customize from there by inserting the boot images of my choice.
If you presently have dual boot and need to wipe the /cache and /data partitions of your second ROM (ROM2) before installing MIUI, then CWM-flash these zips:
Wipe /cache: http://www.mediafire.com/?mc881zjhl9oqr0q
Wipe /data: http://www.mediafire.com/?4k4fey6gxe1nbn0
Now you may be wondering... How do I backup an existing ROM2 since stock recovery tools cannot backup an SD card-based ROM? Here is one way:
Boot phone to CWM 5.0.2.0, connect it to ADB-enabled computer and enter:
Code:
adb devices (make sure device is listed)
adb shell (should get # sign, indicating “root” on Android)
umount /cache (since internal memory /cache is mounted by default)
mount /sdcard
mkdir /sdcard/ROM2-backup
cat /dev/block/mmcblk1p2 /sdcard/ROM2-backup/system.img
cat /dev/block/mmcblk1p3 /sdcard/ROM2-backup/cache.img
cat /dev/block/mmcblk1p4 /sdcard/ROM2-backup/data.img
Standard disclaimers apply. In short, I am not responsible for any harm you or your phone may incur by using any or all of this material.
Many thanks to stevendeb25 (MIUI ported to Atrix), www.angeeks.com (GApps), the CM/Photon/Atrix/Android dev teams and to Koush (CWM Recovery).

yeah....downloading...

tks mate,tks very much,u make my wish come true and every one here who love miui,is there any way i can help u 'cause i dont have visa to donate for u
Sent from my MB860 using Tapatalk 2

mafiarock93 said:
tks mate,tks very much,u make my wish come true and every one here who love miui,is there any way i can help u 'cause i dont have visa to donate for u
Sent from my MB860 using Tapatalk 2
Click to expand...
Click to collapse
Thank you... I am so glad to know that you and your friends can benefit in some way from this little project.
If you have PayPal, you can click the "Donate to me" button, and it takes you to my PayPal donation site. I would probably use the funds to buy a faster SD for experimentation.
Take care.

[L3] [MOD] CWM recovery for e400 [CM/MIUI/SDMERGE]

Hi to all!! I've done a little modification to the original CWM to add support to the secondary partition we use in every CM/MIUI etc...
All is done! Now works without an error of mounting "/sd-ext" due to an "unknown volume type!!" in recovery.fstab.
I also included the recovery for the SDMerge and also a linux script. Sorry, but the archive is too big to post it here on xda so i had to upload it on 4shared.
Requirements:
1) Rooted phone (obviously!!)
Instuctions Windows:
1) Download the package from 4shared
2) Extract it in any folder you prefer
3) Make sure you have USB Debugging on
4) Run "CWM-Installer.bat" as administrator
5) Hit enter
6) Wait, if it takes too long simply disconnect the device and reconnect it immediatly.
5) Enjoy the new recovery!!:victory:
Instructions Ubuntu/Debian/Mint:
1) Download the package from 4shared
2) Extract it
3) Make sure you have the sdk properly installed with adb (if not check here: http://forum.xda-developers.com/showthread.php?t=2100673 )
4) Run the script by typing
Code:
./CWM-Installer.sh
5) Enjoy the new recovery
The script is for stock roms but it works well even on CM or CM-Based ROMs so don't worry if you get errors, it's normal.
If you want your old recovery back you can open the CWM-Installer.bat with an editor and replace this
Code:
Files\adb push Files\recovery.img /data/local/recovery.img
With this:
Code:
Files\adb push Files\[COLOR=Red]CWMrecovery_orig[/COLOR].img /data/local/recovery.img
or if you want the recovery for the SDMerge just replace:
Code:
Files\adb push Files\recovery.img /data/local/recovery.img
with this:
Code:
Files\adb push Files\SDmergerecovery.img /data/local/recovery.img
And then run the script again.
Feel free to post comments!!
Download here:
http://www.4shared.com/archive/8HmnogYQ/CWM-Installer-E400tar.html

wow, long time no see...
keep it up buddy

yayakuya said:
wow, long time no see...
keep it up buddy
Click to expand...
Click to collapse
Thanks yaya, I was busy with work and home and I haven't internet at home so I can't download the huge GBs of a repo.

Works like said great job keep it up buddy!

Cobmaster said:
Hi to all!! I've done a little modification to the original CWM to add support to the secondary partition we use in every CM/MIUI etc...
All is done! Now works without an error of mounting "/sd-ext" due to an "unknown volume type!!" in recovery.fstab.
Requirements:
1) Rooted phone (obviously!!)
Instuctions:
1) Download the attachment
2) Extract it in any folder you prefer
3) Make sure you have USB Debugging on
4) Run "CWM-Installer.bat" as administrator
5) Hit enter
6) Wait, if it takes too long simply disconnect the device and reconnect it immediatly.
5) Enjoy the new recovery!!:victory:
The script is for stock roms but it works well even on CM or CM-Based ROMs so don't worry if you get errors, it's normal.
IT DOESN'T WORK WITH SDMerge MOD!!!
If you want your old recovery back you can open the CWM-Installer.bat with an editor and replace this
Code:
Files\adb push Files\recovery.img /mnt/extra-sd/recovery.img
With this:
Code:
Files\adb push Files\[COLOR=Red]CWMrecovery_orig[/COLOR].img /mnt/extra-sd/recovery.img
And then run the script again.
Feel free to post comments!!
Click to expand...
Click to collapse
i created a flashable zip for the recovery her it is please thank me.:good:

jeffreyvh said:
i created a flashable zip for the recovery her it is please thank me.:good:
Click to expand...
Click to collapse
I used the script written a long time ago for who has only the device rooted but hasn't the recovery installed... Btw good job!

@Cobmaster, could you make similar recovery specifically for data2sdext on stock rom?
I already create similar mod based on this tutorial and it works flawlessly but lack of support from recovery (i.e can't backup/restore from sd-ext)

andwie said:
@Cobmaster, could you make similar recovery specifically for data2sdext on stock rom?
I already create similar mod based on this tutorial and it works flawlessly but lack of support from recovery (i.e can't backup/restore from sd-ext)
Click to expand...
Click to collapse
Are you talking about e405? Or you want a recovery modded to support the partition table in stock rom?
I think I can but I need more specs of the partitioning you use for the sd. I need the specific "/dev/block/mmcblk***" of the partitions in the sd. Nothing more (and a little bit of time obviously!).

Cobmaster said:
Are you talking about e405? Or you want a recovery modded to support the partition table in stock rom?
I think I can but I need more specs of the partitioning you use for the sd. I need the specific "/dev/block/mmcblk***" of the partitions in the sd. Nothing more (and a little bit of time obviously!).
Click to expand...
Click to collapse
it's for stock rom in E400 (E400 and E405 shared the same partitioning system though).
it's the same partition structure created by CWM recovery :
swap -> /dev/block/mmcblk1p1
ext4 -> /dev/block/mmcblk1p2 -> mounted as /data
vfat -> /dev/block/mmcblk1p3
thanks again for your effort

andwie said:
it's for stock rom in E400 (E400 and E405 shared the same partitioning system though).
it's the same partition structure created by CWM recovery :
swap -> /dev/block/mmcblk1p1
ext4 -> /dev/block/mmcblk1p2 -> mounted as /data
vfat -> /dev/block/mmcblk1p3
thanks again for your effort
Click to expand...
Click to collapse
Here it is, to flash it use my script replacing the recovery.img with the one attached and report if it works or not.
Btw, are you sure that the "/data" partition is ext4? Because if it's wrong the recovery doesn't mount it.

Very sorry for the very late reply, I just had the time to test your new recovery (I had to create flashable zip for it since the script didn't work) and it work perfectly.
Now we have alternative to increase data partition without having to edit apps like gellmar's StockMergE400, means it will be compatible with all stock-based rom :victory:
Thanks again @Cobmaster :good:

Don't worry about it. It's very pleasing to see that it works.

hi!
 @Cobmaster, could you make recovery for E405?
after make SDMerge MOD from '' lgl3e405.blogspot.com/2013/05/sd-merge-mod-for-e405-under-testing.html''. i can't restore my backup and i can't mount internal sd.
can you help me. Sorry for my english. i am not good

dricoarmani said:
hi!
@Cobmaster, could you make recovery for E405?
after make SDMerge MOD from '' lgl3e405.blogspot.com/2013/05/sd-merge-mod-for-e405-under-testing.html''. i can't restore my backup and i can't mount internal sd.
can you help me. Sorry for my english. i am not good
Click to expand...
Click to collapse
Could you give me the link of the recovery for e405?
and if you can give me the partition layout of your phone using this: https://play.google.com/store/apps/details?id=com.cls.partition
Or this:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo

Cobmaster said:
Could you give me the link of the recovery for e405?
and if you can give me the partition layout of your phone using this: https://play.google.com/store/apps/details?id=com.cls.partition
Or this:
https://play.google.com/store/apps/details?id=me.kuder.diskinfo
Click to expand...
Click to collapse
How about L5 E455 users? what do you think would happen if i try this recovery on e455?
will it brick it for good ?
-Rant
most of my previous droid phones were SE and then Sony and i never had to deal with any of this
int mem/int sd/ext sd crap. just int mem and sdcard .period
now i've two Chinese tablets and a sammy and now this e455 cuz i needed an affordable dual sim.
man, it's a clusterF. most my backups wont work cuz they've restored on the wrong partition and
yesterday i got some error message like "this dosnt work on emulated storage" and i was like wtf?
/Rant off

Axims said:
How about L5 E455 users? what do you think would happen if i try this recovery on e455?
will it brick it for good ?
-Rant
most of my previous droid phones were SE and then Sony and i never had to deal with any of this
int mem/int sd/ext sd crap. just int mem and sdcard .period
now i've two Chinese tablets and a sammy and now this e455 cuz i needed an affordable dual sim.
man, it's a clusterF. most my backups wont work cuz they've restored on the wrong partition and
yesterday i got some error message like "this dosnt work on emulated storage" and i was like wtf?
/Rant off
Click to expand...
Click to collapse
It will probably get bricked. It's a matter of kernel...
Sent from my LG-E400 using xda premium

Cobmaster said:
It will probably get bricked. It's a matter of kernel...
Sent from my LG-E400 using xda premium
Click to expand...
Click to collapse
hi all,
i have a problem with sdmerge roms. when i install a rom with sdmerge wipe doesn't work.
in cwm i see wipe done succesfully, but nothing happens, and when i reboot i have the same background, same apps etc...
with this update i could fix the problem?

lomax84 said:
hi all,
i have a problem with sdmerge roms. when i install a rom with sdmerge wipe doesn't work.
in cwm i see wipe done succesfully, but nothing happens, and when i reboot i have the same background, same apps etc...
with this update i could fix the problem?
Click to expand...
Click to collapse
only use gellmar recovery, because it is fixed for sdmerge

kien_vip said:
only use gellmar recovery, because it is fixed for sdmerge
Click to expand...
Click to collapse
Where can i find gellmar recovery?
Do you mean step1?
Inviato dal mio LG-E400 con Tapatalk 2

lomax84 said:
Where can i find gellmar recovery?
Do you mean step1?
Inviato dal mio LG-E400 con Tapatalk 2
Click to expand...
Click to collapse
it contain in step 2 or you can see it on some sdmerge rom

[RECOVERY][Experimental][OS2SD/Internal][f2fs]TWRP2.8.0.0-multi

TWRP 2.7.1.0 multi-mode recovery. 2.7.1.0 v3 was the first release for p500, (thanks to @HardLight for advising, testing, and posting it. And for making a p500 OS2SD ROM to justify it.)
v1 and up are for thunderc (Optimus V/S), there's a separate thread over there in the appropriate forum.
Now with f2fs! Thanks @HardLight
OS2SD/Internal All-In-One. Switch modes under Advanced. It tells you on the title bar which mode it's in.
It'll flash gapps or PurePerformances or what have you to either the p2/p4 sdcard partitions for OS2SD or the internal partitions.
This has a special partitioner to set up your card for OS2SD. In OS2SD mode, go to Advanced then Partition. Set your sizes, it isn't aware yet of the whole card size (yet) so it'll just tell you if you go over and refuse to format it.
Whatever is left after your system/swap/data is your /sdcard size.
If it's in Internal mode the partitioner does sd-ext and swap instead. same deal, the leftover space is your /sdcard size.
Under the Wipe -> advanced menu, you can now select either system or data and press the 'repair or change filesystem' bar at the bottom, select change filesystem, select f2fs.
TLS enabled, system/data MTD swap on internal mode to match post-7/12/2014 androidarmv6 builds. Won't flash older ROMS or ones without the MTD swap correctly.
I am working on making it compatible with older builds too... but not yet. You may have to use a new update-binary to flash older zips. Or grab the older one from this zip file.
download, shared folder here:
Experimental, may be glitchy! Enjoy!
source on github

reserved
reserved against whatever need

reserved
I suspect I'll need more than one extra post to cover important stuff that won't fit in the OP.

On the portal today was announced a recovery-switcher app. One could have the mtd swapped and not-mtd swapped recoveries, or a cwm and a twrp recovery on the sdcard and use the app to switch between them. Do not know if this baby would work on a P500, though.
Would rather have a decent all-in-one, but that 5meg limitation may make this impractical (for example, the cwm has lost its sdcard partitioning functions).

bigsupersquid said:
TWRP 2.7.1.0 multi-mode recovery. v4. ...
OS2SD/Internal All-In-One. Switch modes under Advanced. It tells you on the title bar which mode it's in.
It'll flash gapps or PurePerformances or what have you to either the p2/p4 sdcard partitions for OS2SD or the internal partitions.
Experimental, may be glitchy! Enjoy!
source on github
Click to expand...
Click to collapse
So if understand correctly i'll flash the mod "buttons search<->power" & other zip files normally and not have to put the files into the rom manually or edit the updater script etc.:victory: thanks a lot
testing...

Dovidhalevi said:
On the portal today was announced a recovery-switcher app. One could have the mtd swapped and not-mtd swapped recoveries, or a cwm and a twrp recovery on the sdcard and use the app to switch between them. Do not know if this baby would work on a P500, though.
Would rather have a decent all-in-one, but that 5meg limitation may make this impractical (for example, the cwm has lost its sdcard partitioning functions).
Click to expand...
Click to collapse
that thing on portal reflashes the recovery every time to change it.
you could just as easily use flashable zip recoveries...
xdema said:
So if understand correctly i'll flash the mod "buttons search<->power" & other zip files normally and not have to put the files into the rom manually or edit the updater script etc.:victory: thanks a lot
testing...
Click to expand...
Click to collapse
that specific mod, you'd have to fix the updater-script to use it for os2sd, because it specifies MTD mounts.
mount("yaffs2", "MTD", "system", "/system");
pa_gapps and CrossBreeder and other more generic zips use
busybox mount /system
//edit: proper syntax:
run_program("/sbin/busybox","mount","/system");
instead of trying to call out the filesystem type.

bigsupersquid said:
that thing on portal reflashes the recovery every time to change it.
you could just as easily use flashable zip recoveries...
that specific mod, you'd have to fix the updater-script to use it for os2sd, because it specifies MTD mounts.
mount("yaffs2", "MTD", "system", "/system");
pa_gapps and CrossBreeder and other more generic zips use
busybox mount /system
instead of trying to call out the filesystem type.
Click to expand...
Click to collapse
i'll check the updater script, thanks for the pureperformance thinks, i discover a another method to speed up the p500 :fingers-crossed:

bump
f2fs enabled for OS2SD.
uses updater script like so:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p4", "/data");
to use f2fs /data go into Wipe menu, advanced, select data checkbox, press 'repair or change filesystem' bar, change filesystem, f2fs. accept.
you only have to do that once to change from the default ext4 partition type.
it handles /system f2fs as well.
mount("f2fs", "EMMC", "/dev/block/mmcblk0p2", "/system");
change the filesystem the same way as data.
new 3.0.101 kernel but I noticed no differences in recovery except the working f2fs. Thanks @HardLight.
for now, attached .img for you who really have to experiment. I haven't tested this one very much on thunderg, just thunderc. basics tested on thunderg.
flashable zip added to shared folder linked in OP.
there's a little something extra in the shared folder...
I'm also uploading ROMs for the adventurous.
f2fs-system and f2fs-data os2sd builds if you're brave enough to try them. change both system and data to f2fs in recovery before flashing the rom unless you've already done that with an earlier version.
I don't have cell service to test but it's basically an androidarmv6 build plus 3.0.101 kernel and f2fs os2sd. everything else looks like it works to me.
I added Email, Apollo, Speech Recorder (which tunes up voice search I think), emojii in messaging and aosp keyboard, and extra wallpapers. Including Grass live wallpaper (which does actually work on armv6, it just looks for some network function and errors out ... I patched it,) and it reverts to building libcamera. Plus hackers keyboard because I like arrow and tab in terminal. No voice search in hackers keyboard though.
...

bump for twrp 2.8.0.0
no other fixes or anything, just a rev up for twrp.
I'll upload in an hour or so. //edit: well, maybe not so soon. I can't test at the moment since my o1 went into a no-boot loop. perfectly good running rom on it too. bah.
take me the evening to fix it.

bigsupersquid said:
bump for twrp 2.8.0.0
no other fixes or anything, just a rev up for twrp.
I'll upload in an hour or so. //edit: well, maybe not so soon. I can't test at the moment since my o1 went into a no-boot loop. perfectly good running rom on it too. bah.
take me the evening to fix it.
Click to expand...
Click to collapse
i'm testing your's 0509
in this you made the on boot fix?
##fix "add_tid_to_cgroup failed to write" errors
chmod 0660 /dev/cpuctl
# allow reading kernel command line
chmod 0644 /proc/cmdline
Click to expand...
Click to collapse
thanks
could you say to me if it's normal this:
i make the wipe of the /system in twrp, then if i go to "repair or change fs" it show size 390mb, used 110mb
but if i make a wipe or a "change fs", used space shouldn't be 0mb?
is the same for /data.
i un/mounted the partitions before, but have always some mb used in both.
hum minitool show me that the two f2fs partitions are fully used, maybe it can't read the f2fs, however i've formatted the partitions again in ext4 and now retry the f2fs format via twrp
edit: however, after 2nd format in the end /data have 144 mb used, /system 110mb. so i suspect it's normal

xdema said:
i'm testing your's 0509
in this you made the on boot fix?
thanks
could you say to me if it's normal this:
i make the wipe of the /system in twrp, then if i go to "repair or change fs" it show size 390mb, used 110mb
but if i make a wipe or a "change fs", used space shouldn't be 0mb?
is the same for /data.
i un/mounted the partitions before, but have always some mb used in both.
hum minitool show me that the two f2fs partitions are fully used, maybe it can't read the f2fs, however i've formatted the partitions again in ext4 and now retry the f2fs format via twrp
edit: however, after 2nd format in the end /data have 144 mb used, /system 110mb. so i suspect it's normal
Click to expand...
Click to collapse
looks normal to me, ext4 uses "only" about 16MB after format but f2fs uses a lot more.
minitool will only work right if your kernel supports f2fs and I doubt m$ware does right now.
and the fix din't get migrated from the overrides in thunderc to p500 yet, sorry, was a 'for fun' build to share after a recent repo sync.
this one probably has a built libcamera instead of the froyo as well. (reversion)

reverted to twrp 2.7.1.0
2.8 kept bootlooping my o1.
one too many passes with kdz, it's total blackout no power, and I'll have to jtag it now.
be a while before I release another update unless I find an o1 with fastboot.

bigsupersquid said:
reverted to twrp 2.7.1.0
2.8 kept bootlooping my o1.
one too many passes with kdz, it's total blackout no power, and I'll have to jtag it now.
be a while before I release another update unless I find an o1 with fastboot.
Click to expand...
Click to collapse
My 01 does have fastboot e.e

andrea210701 said:
My 01 does have fastboot e.e
Click to expand...
Click to collapse
I meant that I can use. HardLight pointed me to the method to enable it... if I hadn't completely fried my firmware. no backlight even, much less lg logo or emergency mode.
eventually I'll find another p500 for development (I can't use gsm phone on my service) but the going rate on ebay is $50 and I can't justify that for a hobby.
unfortunately it's too tweaky and time consuming for me to remotely develop by having someone else debug, so any more p500 stuff will be untested and slightly sketchy because of that.

Project [F2FS] [OS2SD]
[F2FS] [OS2SD] it can work with any other rom? Thanks.

cwm6.0.5.3oldMTDmounts_p500.zip
I do not know what it is? Sorry for the little understood...

Any PlayStore said:
cwm6.0.5.3oldMTDmounts_p500.zip
I do not know what it is? Sorry for the little understood...
Click to expand...
Click to collapse
clockwork mod v 6.0.5.3 for pre-tls roms (before androidarmv6 swapped the system and data Mount points in the kernel) used for kitkat roms around July 2014 or earlier or other 4.4 roms without the MTD partition swap

CWM Recovery for z4u HBOOT 1.0.3 ONLY

This is CWM FOR THE SINGLE SIM on HBOOT 1.0.3 ONLY z4u
installation instructions:
Download recovery
reboot into hboot (bootloader)
fastboot flash recovery recovery.img
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Forked from dummie999's device tree and then modified.
XDA:DevDB Information
ClockWorkMod , Tool/Utility for the HTC Desire 500
Contributors
Lloir, Lloir, dummie999
Source Code: https://github.com/Lloir/android_device_htc_z4u
Version Information
Status: No Longer Updated
Beta Release Date: 2017-04-12
Created 2017-04-12
Last Updated 2017-04-24

Reserved
DOWNLOAD

Reserved
CHANGELOG
14/04/17
Added in the graphics glitch fix thanks to @dummie999 for pointing out the location for the patch.
Fixed up the partitions, which were labeled incorrectly.
Added SELinux support (not really needed at the moment)

what rom? tell us more!

SkopiX said:
what rom? tell us more!
Click to expand...
Click to collapse
CM-10.1 is in the works, once that's done and stable, it'll be released.
Easier to start from the bottom and work up IMO

Lloir said:
CM-10.1 is in the works, once that's done and stable, it'll be released.
Easier to start from the bottom and work up IMO
Click to expand...
Click to collapse
OMG thanks man never thought id see cm on this phone

well, it seems good i hope u will not give it up

Updated the build, I accidentally broke the mount points, those are fixed. I'll sort the graphics glitch out eventually.
Sent from my iPhone Se using Tapatalk

Lloir said:
Updated the build, I accidentally broke the mount points, those are fixed. I'll sort the graphics glitch out eventually.
Sent from my iPhone Se using Tapatalk
Click to expand...
Click to collapse
Is that the dancing back and forth? https://github.com/dummie999/android_kernel_htc_z4u/commit/a122e872928f579530257b51f0dfff2b30ebd6ac

dummie999 said:
Is that the dancing back and forth? https://github.com/dummie999/android_kernel_htc_z4u/commit/a122e872928f579530257b51f0dfff2b30ebd6ac
Click to expand...
Click to collapse
Yeah got it, looks like part of the patch was reverted.
Thanks.

Build updated
Change log in post #3
no more builds of this to be done, unless some huge bug appears.
Besides TWRP is available this was built for nostalgia purposes.

Lloir said:
CHANGELOG
14/04/17
Fixed up the partitions, which were labeled incorrectly.
...
Click to expand...
Click to collapse
The partitions were labelled for hboot version 1.02 and 1.01. Mine is still on 1.02 but I guess yours is on 1.03 (for some reason they changed the partition layout in an update, I still don't know why)
I build cm10.1 this morning, will test tonight.
If anyone needs the 1.02/1.01 cwm just send me a pm

CWM Recovery for z4u
dummie999 said:
The partitions were labelled for hboot version 1.02 and 1.01. mine is still on 1.02 but I guess yours is on 1.03 (for some reason they changed the partition layout in an update, I still don't know why)
I build cm10.1 this morning, will test tonight.
If anyone needs the 1.02/1.01 cwm just send me a pm
Click to expand...
Click to collapse
They layout We have now is perfectly fine, it works on mine and should work on you're one. I need to get another 1.03 dump, mine didn't dump correctly, my derp.
WAIT I NEED A 1.03 DUMP I KNOW WHATS WRONG
#HTCSUCK
Sent from my iPhone Se using Tapatalk

Lloir said:
They layout We have now is perfectly fine, it works on mine and should work on you're one. I need to get another 1.03 dump, mine didn't dump correctly, my derp.
WAIT I NEED A 1.03 DUMP I KNOW WHATS WRONG
#HTCSUCK
Sent from my iPhone Se using Tapatalk
Click to expand...
Click to collapse
The version that is on GitHub right now does not work for me.

dummie999 said:
The version that is on GitHub right now does not work for me.
Click to expand...
Click to collapse
[emoji58]upload your builds for me, I'll add them to the post. I also have to do a hboot script in this case, to stop people from flashing 1.03 builds on 1.02 hboots
Sent from my iPhone Se using Tapatalk

Lloir said:
[emoji58]upload your builds for me, I'll add them to the post. I also have to do a hboot script in this case, to stop people from flashing 1.03 builds on 1.02 hboots
Sent from my iPhone Se using Tapatalk
Click to expand...
Click to collapse
Will do once I get home. A script is a good idea :good:
Also, the recovery has worked fine for dual SIM in the past, can smb test that?

dummie999 said:
Will do once I get home. A script is a good idea :good:
Also, the recovery has worked fine for dual SIM in the past, can smb test that?
Click to expand...
Click to collapse
I have a script I can implement, I'll add it to the device tree later.
Sent from my iPhone Se using Tapatalk

https://github.com/dummie999/android_kernel_htc_z4u/commit/f6ead5ede7d7c9530574491ff266ae6379111eb2
I remember why I turned it off again. Sometimes when I launched the os from multirom (never got it working entirely), the screen jumping would be enabled by the fix. So I disabled it by default, and added a flag to init.rc of the recovery to turn it on. But that doesn't matter now, so it can be on by default.

I changed recovery.fstab with this:
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p32
/cache ext4 /dev/block/mmcblk0p37
/data ext4 /dev/block/mmcblk0p39
/misc emmc /dev/block/mmcblk0p17
/recovery emmc /dev/block/mmcblk0p33
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p38
/devlog ext4 /dev/block/mmcblk0p35

dummie999 said:
I changed recovery.fstab with this:
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p32
/cache ext4 /dev/block/mmcblk0p37
/data ext4 /dev/block/mmcblk0p39
/misc emmc /dev/block/mmcblk0p17
/recovery emmc /dev/block/mmcblk0p33
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/system ext4 /dev/block/mmcblk0p38
/devlog ext4 /dev/block/mmcblk0p35
Click to expand...
Click to collapse
can you upgrade to 1.0.3?
The change was pushed for the releasetools.py
https://github.com/Desire500/android_device_htc_z4u/commit/199a1cebdda28081bab9820e59f937cb49efe818
IF hboot version 1.0.2 works, could you edit the releastools for me please, and use this as the template on what needs to be done https://github.com/CyanogenMod/android_device_htc_endeavoru/blob/cm-10.2/releasetools.py