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.

[RECOVERY] BMM - Boot Menu Manager 0.3.5 PreAlpha (Locked Bootloader)

The only way to make nandroid backup then restore it when you have Locked bootloader. Original thread:
http://forum.xda-developers.com/showthread.php?t=2005187
This is whirleyes famous Boot Menu Manager. I've been using it when I had Motorola RAZR.
I only tested nandroid backup and restore and zip install. Both working OK. Most BMM features probably not working and I personally don't want to test it as i don't like install ROM from scratch,
USE it only if you're LOCKED, for UNLOCKED bootloaders use Dexter's CWM or TWRP
What working:
1. Nandroid backup and restore
2. Zip install from External SDCARD
Not working:
1. Touch screen
2. Radio/Kernel flashing
3. Running second system
Install:
Unpack zip, run install.bat
When BMM appear on screen use Vol+/Vol- to enter BMM then Power to accept.
Credits:
All credits goes to whirleyes
Proceed at your own risk. Don't try this if you're not comfortable fixing your phone/troubleshooting/flashing

I want to flash te zaiben rom? Is that possible?
Sent from my LG-P880 using xda app-developers app

yeah as it doesnt change kernel/recovery i think
Sent from my LG-P880 using xda app-developers app

Where do I have to put the .zip files? My phone does not show me the archives i placed on my internal storage

how do I boot into the recovery ??
It goes to a bootscreen of the recovery but then it reboots normal
Sent from my LG-P880 using xda app-developers app

Nice... In recovery my device uses Motorola ADB driver and Motocast starts... (Drivers are installed for my old Moto Defy...)
mrlollog said:
Where do I have to put the .zip files? My phone does not show me the archives i placed on my internal storage
Click to expand...
Click to collapse
Mountpoints are fail... External SD works fine

This is recovery.fstab file from BMM, I only modified 4 mount points. If someone can look into it BMM is located:
/system/etc/bmm
Code:
###################
# Motorola spyder #
###################
# BMM NOTICE:
# - Keep mount point in boot order. This file will be used to generate init.fs.rc
#
# mount point fstype device second device or options
#
/system auto /dev/block/platform/sdhci-tegra.3/by-name/APP
/pds auto /dev/block/pds
/preinstall auto /dev/block/preinstall
/data auto /dev/block/platform/sdhci-tegra.3/by-name/UDA
/cache auto /dev/block/platform/sdhci-tegra.3/by-name/CAC
/ext vfat /dev/block/mmcblk1p1
/int vfat /dev/block/mmcblk1p1

lukas77 said:
This is recovery.fstab file from BMM, I only modified 4 mount points. If someone can look into it BMM is located:
/system/etc/bmm
Code:
###################
# Motorola spyder #
###################
# BMM NOTICE:
# - Keep mount point in boot order. This file will be used to generate init.fs.rc
#
# mount point fstype device second device or options
#
/system auto /dev/block/platform/sdhci-tegra.3/by-name/APP
/pds auto /dev/block/pds
/preinstall auto /dev/block/preinstall
/data auto /dev/block/platform/sdhci-tegra.3/by-name/UDA
/cache auto /dev/block/platform/sdhci-tegra.3/by-name/CAC
/ext vfat /dev/block/mmcblk1p1
/int vfat /dev/block/mmcblk1p1
Click to expand...
Click to collapse
Int and Ext are the same (/dev/block/mmcblk1p1)

Nice! Now we just need ability to load 2nd kernel like in defy roms. Good work!
Sent from my rooted P880

Will there be a new version which allows users to flash new kernels?

I'm not skilled enough to make modification, hopefully Whirleyes can do it in his free time or we can ask Dexter to look into scripts and maybe he can make it working.

lukas77 said:
I'm not skilled enough to make modification, hopefully Whirleyes can do it in his free time or we can ask Dexter to look into scripts and maybe he can make it working.
Click to expand...
Click to collapse
Thanks! Maybe look at the code for defy and other phones that already have 2nd kernel for ideas :thumbup:
Sent from my rooted P880

does this able to flash Zaiben ROM?

vinnong said:
does this able to flash Zaiben ROM?
Click to expand...
Click to collapse
I can't flash the zaiban rom, maby you Have more luck
Sent from my LG-P880 using xda app-developers app

Delete

Unlock and install real recovery: http://forum.xda-developers.com/showthread.php?t=2245836
OP I respect your work but this is no longer needed, mods should close this as no ROMs use locked BL
Sent from my rooted P880

FD1999 said:
Maybe some people don't want to unlock the BL yet?
Gesendet von meinem LG-P880 mit Tapatalk 2
Click to expand...
Click to collapse
Now that it is unlocked for all there will never be ROMs for locked bootloader, you could make backups yes, but if you're not flashing anything there isn't much point imo
Sent from my rooted P880

Greetings there....does this recovery works if i want to flash zip files? Like customization or anything other than flashing roms
Sent from my LG O4X

Simple answer: No

Afro said:
Simple answer: No
Click to expand...
Click to collapse
???
You can use BMM for installing zipped customizations. And Aroma Installer uses full display...

Device Essential Material *** Firmware, Source Code, Root etc.***

This thread will list and link to all core device essential stuff.
PM me if there is new stuff or something doesn't work please​
STOCK ASUS FIRMWARE
WW_epaduser_11_4_1_17_UpdateLauncher.zip: HERE
US_epaduser_11_4_1_17_UpdateLauncher.zip: HERE
WW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
CN_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_18_UpdateLauncher.zip: HERE
US_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
TW_epaduser_10_26_1_7_UpdateLauncher.zip: HERE
CN_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
JP_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
US_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
WW_epaduser_10_14_1_47_UpdateLauncher.zip: HERE
CN_epaduse_10_14_1_45_UpdateLauncher.zip: HERE
How to flash:
Step 1: Download and unzip the zipfile of your choice.
Step 2: Copy the new Zipfile and paste it in root directory of your internal SdCard, then reboot the device and the update will automatically start.
ASUS SOURCE CODE
kernel_10_14_1_42.rar: HERE
kernel_10_14_1_45.rar: HERE
kernel_10_14_1_47.rar: HERE
kernel_10_26_1_7.rar: HERE
kernel_10_26_1_18.rar: HERE
kernel_11_4_1_17.rar: HERE
UNLOCK YOUR DEVICE
0820-0954_SIGNED_UnLock_for_TF701_repart.apk: HERE
How to unlock:
- Download the Asus unlock app
- Install and run the app. This will require a valid google account (if you use one time passwords, you'll need to generate one for this purpose) and internet access.
- When booting with [vol-] + [power] pressed, the transformer will show the message "The device is unlocked"
ROOT TOOLS
Read here: http://forum.xda-developers.com/showthread.php?t=2516215
CUSTOM RECOVERY
CWM Recovery V6.0.4.8. for 4.3*: HERE
ATTENTION: you must have an unlocked bootloader
How to flash this:
- reboot device into fastboot mode:
- adb reboot bootloader
- now flash the recovery using : fastboot flash recovery recovery.img [where recovery.img is the name of the file image you downloaded]
CUSTOM ROM'S
By Sbdags based on stock with quite some enhancements: HERE
CyanogenMod 11 Preview Proxy thread: HERE
THEMES
Non available yet
BOOTANIMATIONS
Non available yet
OTHER MOD'S
None available yet
PARTITION INFORMATION**
Code:
name device mountpoint fs description
/dev/block/platform/sdhci-tegra.3/ADF /dev/block/mmcblk0p7 /ADF ext4 ?
/dev/block/platform/sdhci-tegra.3/APD /dev/block/mmcblk0p6 /APD ext4 ASUS Product Demo
/dev/block/platform/sdhci-tegra.3/APP /dev/block/mmcblk0p4 /system ext4 Android OS
/dev/block/platform/sdhci-tegra.3/CAC /dev/block/mmcblk0p5 /cache ext4 recovery logs
/dev/block/platform/sdhci-tegra.3/CRA /dev/block/mmcblk0p11 ?
/dev/block/platform/sdhci-tegra.3/DTB /dev/block/mmcblk0p2 ?
/dev/block/platform/sdhci-tegra.3/EKS /dev/block/mmcblk0p13 NVEKSP
/dev/block/platform/sdhci-tegra.3/LNX /dev/block/mmcblk0p3 Linux kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/MDA /dev/block/mmcblk0p12 ?
/dev/block/platform/sdhci-tegra.3/MSC /dev/block/mmcblk0p8 empty (misc, bootloader etc.)
/dev/block/platform/sdhci-tegra.3/PER /dev/block/mmcblk0p10 /persist ext4 config/calibration data
/dev/block/platform/sdhci-tegra.3/SOS /dev/block/mmcblk0p1 Recovery kernel (8388608 b)
/dev/block/platform/sdhci-tegra.3/UDA /dev/block/mmcblk0p14 /data ext4 Android user data
/dev/block/platform/sdhci-tegra.3/USP /dev/block/mmcblk0p9 Staging (blob)
RECOVERY.FSTAB**
Code:
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/sdhci-tegra.2/mmc_host/mmc1 /storage/sdcard1 vfat default voldmanaged=sdcard:auto
/devices/platform/tegra-ehci.0 /mnt/usbdrive vfat default voldmanaged=usbdrive:auto
BLOB**
Code:
name size description status
10.14.1.47: [ATTACH]2435244[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (original) [ATTACH]2435246[/ATTACH]
blob.BC1 8,192 Bytes ? (original) [ATTACH]2435245[/ATTACH]
blob.EBT 1,396,736 Bytes Bootloader (original) [ATTACH]2435247[/ATTACH]
blob.PT 2,202 Bytes Partition Table (original) [ATTACH]2435248[/ATTACH]
10.26.1.7: [ATTACH]2435238[/ATTACH]
blob.BCT 8,192 Bytes Boot Config Table (unchanged) [ATTACH]2435241[/ATTACH]
blob.BC1 8,192 Bytes ? (changed) [ATTACH]2435240[/ATTACH]
blob.EBT 1,421,312 Bytes Bootloader (changed) [ATTACH]2435242[/ATTACH]
**= Thanks to Ipdunwell for sharing this info
HOW TO UNBRICK YOUR DEVICE
Read here: http://forum.xda-developers.com/showpost.php?p=47933481&postcount=1
ATTENTION​
YOUR WARRANTY COULD BE VOID DUE TO ROOTING AND UNLOCKING YOUR DEVICE (depending of which country you reside)
I am NOT responsible for bricked devices, dead SD cards or dead docks.
Please do some research if you have any concerns about the files here BEFORE flashing anything!
When you have no clue what we are talking about here you better leave your hands off it!!
YOU are choosing yourself freely to use these file(s) all by yourself!!!​

Updated Recovery for 4.3 with working "external" SD card, found here
http://forum.xda-developers.com/show....php?t=2621051
Custom Rom's
Cromi-x
http://forum.xda-developers.com/show....php?t=2608129
CM11 -Preview (Unofficial)
http://forum.xda-developers.com/show....php?t=2621028

Delete

Root and firmware.
Hello all. I'm new to the site, and very sorry if this is a dumb question, but Id rather sound dumb than brick my transformer.. I'm planning to root my TF701 following lpdunwells guide. One of the prerequisites is to have 10.14.1.47 as the firmware version. My question is this.. When I unlock my bootloader and it wipes my tablet, will it reset me back to the original firmware version? Or will this matter?
My current firmware version is 10.26.1.18
Thank you very much in advance for your help, also, I will greatly appreciate any and all help and info regarding this matter.

tf701mega said:
Hello all. I'm new to the site, and very sorry if this is a dumb question, but Id rather sound dumb than brick my transformer.. I'm planning to root my TF701 following lpdunwells guide. One of the prerequisites is to have 10.14.1.47 as the firmware version. My question is this.. When I unlock my bootloader and it wipes my tablet, will it reset me back to the original firmware version? Or will this matter?
My current firmware version is 10.26.1.18
Thank you very much in advance for your help, also, I will greatly appreciate any and all help and info regarding this matter.
Click to expand...
Click to collapse
If you want to root then use my guide as it is for 10.26.1.18. Downgrading to .47 and back up again is really painful.

download problem
Hi OP,
Download links are down...
please fix theme?

henengel said:
Hi OP,
Download links are down...
please fix theme?
Click to expand...
Click to collapse
anyone know where I can get the files? links are broken

kuthedude said:
anyone know where I can get the files? links are broken
Click to expand...
Click to collapse
Which files are you looking for?
Most of the files are available from ASUS's website and the ROM and recovery links are old and newer ones are available in the Development section of this form.

Sorry for the inconvenience.
Asked in the OP to PM me if there is new stuff or if somethings doesn't work but received nothing.
Files will be back end of the day with latest firmware and kernel source.

Hi, I am getting my tablet soon, and I am assuming the tablet will be on 4.3 or earlier by the time I get it.
What firmware/kernal/boot loader is the best setup to get me onto the latest 4.3 OS. I only am wanting this because I want to avoid the 4.4.2 battery drain issues (since I am most likely going to flash an AOSP ROM after I get this tablet).
Also, how would I be able to properly update the tablet with the firmware/kernal/boot loader? Thanks for the help!
Sent from my SCH-I545 using Tapatalk 2

Hi, I tried pushing my firmware file to root, but it wouldn't work. I would use root explorer and it would just freeze and restart. anyone know why this would happen? Im trying to update to 4.3 without getting into 4.4.2. please help if you can

You have to unpack the file, inside this is another zip file. Put it then in sd root this should work as far as i know
Gesendet von meinem LG-D855 mit Tapatalk

Hi
There is a new firmware version 11.4.1.27.
Is it posible to add this version to the post?

[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

[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