Jump to content


Photo

CWM 5.x.x.x with ext4 support question?

* * * * * 2 votes

  • Please log in to reply
133 replies to this topic

Poll: CWM with ext4 support?!... (144 member(s) have cast votes)

Would you like a newer CWM compiled for the Blade?

  1. Yes (124 votes [86.11%] - View)

    Percentage of vote: 86.11%

  2. No (2 votes [1.39%] - View)

    Percentage of vote: 1.39%

  3. Not Bothered (18 votes [12.50%] - View)

    Percentage of vote: 12.50%

Vote Guests cannot vote

#41
KonstaT

KonstaT

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,325 posts
  • Gender:Male
  • Location:Finland
  • Devices:Moto G, ZTE Blade III

Just flash via "old" CWM?

Yep.

I wonder what about touch recovery? can it be done too? my volume keys are gone and the PhoTom 4.0.1.5 is all I got. can we update it?

Source code hasn't been released for the official cwm touch recovery (5.8.x.x), so that isn't possible at the moment.

There is also another touch recovery project, team win recovery project, that would be interesting to have ported for Blade.

  • 1

#42
shmizan

shmizan

    Addict

  • Members
  • PipPipPipPipPip
  • 574 posts
  • Devices:ZTE Blade
not an official clockworkmod touch recovery then. 4.0.1.5 wasn't touch either. and since the code for that is in the hands of our beloved developer t0mm13b, and we do have the code for the latest non touch recovery, couldn't it be easily implanted? sorry I know jack about Linux coding ;)

  • 0

Orange San Francisco, Upgraded to Gen 2 with TPT Helper (custom partition layout: 150-sys, 302-data, 4-cache)
CyanogenMod 10


#43
trueno2k

trueno2k

    Diehard

  • Members
  • PipPipPipPip
  • 495 posts
  • Gender:Male
  • Location:UK
  • Devices:SGS3 I9300 + OMC/ZTE Skate

Here is a fresh build of ClockWorkMod 5.5.0.4. It should be now fully working. :) Cold boot works normally with VOLUME DOWN key pressed. Thanks goes to Koush and Tom G.

recovery-clockwork-5.5.0.4-blade.zip
md5:245337f2ea21c275da8d3e7bbfed9935

recovery.img
md5:d0cec293f1d78ea8bd4e211aead0b9cc

Hey thanks for the update, working brilliantly!... :D ... However, was wondering why it was decided to get rid of the shutdown function?... it frequently saves me from pulling out the battery every time I wanna turn my device off...

  • 0
main-logo.pngSamba_hi_res_normal.jpg02_96x31.png14.gifreferral-ad-120x60.pnglogo-colors1-vflhO4gIp.png
Current devices [ ROM ]: Samsung Galaxy SIII [ CM11 Nightly ], Motorola Moto G [ Stock JB ], & Google/Asus Nexus 7 2013 [ Stock KK ]
Previous devices: Sony Ericsson Xperia ARC ( Anzu ), Orange Monte Carlo ( ZTE Skate ), Orange San Francisco ( ZTE Blade ), & HTC Wildfire ( Buzz )

#44
trueno2k

trueno2k

    Diehard

  • Members
  • PipPipPipPip
  • 495 posts
  • Gender:Male
  • Location:UK
  • Devices:SGS3 I9300 + OMC/ZTE Skate

Okay, I see what you were trying to get at... I just tried the HOME + VOLUME UP + POWER key combination on my OMC and CWM 5.5.0.4 booted up with hard keys fully working, I completely forgot about the above thread Posted Image ... Seeing as I don't care about reverting back Eclair or even Froyo, can I use the same program used for unlocking the OMC / Skate to windows TPT flash my OSF / Blade to Gen2 permanently (using the Blade Gen2 stock TPT)?... I also remember by doing this I am unable to use the Gen1 to Gen2 TPT method once TPT flashing through the windows program, is that right or wrong?... Would that mean I'll have to use the windows program everytime I want to change the partition format on my OSF / Blade?...

I found out I can Gen1 to Gen2 TPT the OSF / Blade using only the partition layout files and all necessary .img files as listed below, but I was also wondering whether this method can be used on the windows TPT flashing tool using only the files listed below as well?...

appsboot.mbn
appsboothd.mbn
partition.mbn
partition_zte.mbn
boot.img
recovery.img
system.img
userdata.img
cache.img


Much appreciate the response Posted Image Posted Image

UPDATE: I've just flashed Burstlam's ICS AOKP on to my OSF and so far the rom is working perfectly as it should from a fresh build flash, so, besides the upside down issue CWM 5.8.1.0 (supposedly touch version) is working... but this version still doesn't support ext4!... Is this due to the kernel or something, I don't understand why my Wildfire CWM has the option to partition my sdcards with ext 2, 3 & 4 partitions and it is only version 5.0.2.7?...

BUMP for the above post... Apologise for the nagging ( if anyone see it that way! Posted Image )...

Edited by trueno2k, 27 April 2012 - 09:15 PM.

  • 0
main-logo.pngSamba_hi_res_normal.jpg02_96x31.png14.gifreferral-ad-120x60.pnglogo-colors1-vflhO4gIp.png
Current devices [ ROM ]: Samsung Galaxy SIII [ CM11 Nightly ], Motorola Moto G [ Stock JB ], & Google/Asus Nexus 7 2013 [ Stock KK ]
Previous devices: Sony Ericsson Xperia ARC ( Anzu ), Orange Monte Carlo ( ZTE Skate ), Orange San Francisco ( ZTE Blade ), & HTC Wildfire ( Buzz )

#45
trueno2k

trueno2k

    Diehard

  • Members
  • PipPipPipPip
  • 495 posts
  • Gender:Male
  • Location:UK
  • Devices:SGS3 I9300 + OMC/ZTE Skate
UPDATE: Just been playing around with version 5.5.0.4 of CWM recovery and found I can not mount my sdcard, gives me "E:Unable to open v*s lunfile (No such file or directory)"... Anyone else getting this problem???

  • 1
main-logo.pngSamba_hi_res_normal.jpg02_96x31.png14.gifreferral-ad-120x60.pnglogo-colors1-vflhO4gIp.png
Current devices [ ROM ]: Samsung Galaxy SIII [ CM11 Nightly ], Motorola Moto G [ Stock JB ], & Google/Asus Nexus 7 2013 [ Stock KK ]
Previous devices: Sony Ericsson Xperia ARC ( Anzu ), Orange Monte Carlo ( ZTE Skate ), Orange San Francisco ( ZTE Blade ), & HTC Wildfire ( Buzz )

#46
agpoli

agpoli

    Enthusiast

  • Members
  • PipPipPip
  • 186 posts
  • Gender:Male
  • Location:Hungary
  • Devices:ZTE Blade

UPDATE: Just been playing around with version 5.5.0.4 of CWM recovery and found I can not mount my sdcard, gives me "E:Unable to open v*s lunfile (No such file or directory)"... Anyone else getting this problem???


Same here.

  • 0

#47
shanky887614

shanky887614

    Regular

  • Members
  • PipPip
  • 79 posts
  • Devices:orange san franciso
stick to official clockwork recovery and you wont have any problems


the only thing on zte blade im very careful with is reguards to recovery

if you dont have fastboot mode and you mess up clockwork and rom you are screwed

  • 0

#48
targetbsp

targetbsp

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 3,991 posts
  • Gender:Male
  • Devices:Blade V, I9000, Blade
You can flash clockwork from rom manager. The only way you're really screwed is if you also happen to take out your rom at the same time. It takes a lot to really screw a blade. :)

  • 0
My Blade site - includes vanilla KANGS's of CM7. Also available: modified GB Gapps with various market versions, mini ICS Gapps for 160mb system partitions and Flash for ARMv6
CM7 Blade changelog

#49
Sulthekk

Sulthekk

    Addict

  • Members
  • PipPipPipPipPip
  • 619 posts
  • Devices:ZTE Blade
Until the red led is there and light, the device isn't screwed. The blade is a kinda hard-to-kill something.

  • 0

#50
trueno2k

trueno2k

    Diehard

  • Members
  • PipPipPipPip
  • 495 posts
  • Gender:Male
  • Location:UK
  • Devices:SGS3 I9300 + OMC/ZTE Skate

...Seeing as I don't care about reverting back Eclair or even Froyo, can I use the same program used for unlocking the OMC / Skate to windows TPT flash my OSF / Blade to Gen2 permanently (using the Blade Gen2 stock TPT)?... I also remember by doing this I am unable to use the Gen1 to Gen2 TPT method once TPT flashing through the windows program, is that right or wrong?... Would that mean I'll have to use the windows program everytime I want to change the partition format on my OSF / Blade?...

I found out I can Gen1 to Gen2 TPT the OSF / Blade using only the partition layout files and all necessary .img files as listed below, but I was also wondering whether this method can be used on the windows TPT flashing tool using only the files listed below as well?...

appsboot.mbn
appsboothd.mbn
partition.mbn
partition_zte.mbn
boot.img
recovery.img
system.img
userdata.img
cache.img


Much appreciate the response Posted Image Posted Image

UPDATE: ... besides the upside down issue CWM 5.8.1.0 (supposedly touch version) is working... but this version still doesn't support ext4!... Is this due to the kernel or something, I don't understand why my Wildfire CWM has the option to partition my sdcards with ext 2, 3 & 4 partitions and it is only version 5.0.2.7?...

So, this is a bump for the above quote, yeah sorry for nagging :P just hope to have the questions above answered so I don't brick my Blade if I try doing the above flash methods.... Thanks for the reply...


stick to official clockwork recovery and you wont have any problems

the only thing on zte blade im very careful with is reguards to recovery

if you dont have fastboot mode and you mess up clockwork and rom you are screwed

As long as TPT works for me using the files in the above quote list I shouldn't come across any trouble besides reflashing a rom again from scratch that is :P... Atm, my Blade is only used for experimenting new flashes and custom setups I do extra for partitions and system/data app installations, so nothing important can be lost :D...

Edited by trueno2k, 27 April 2012 - 09:36 PM.

  • 0
main-logo.pngSamba_hi_res_normal.jpg02_96x31.png14.gifreferral-ad-120x60.pnglogo-colors1-vflhO4gIp.png
Current devices [ ROM ]: Samsung Galaxy SIII [ CM11 Nightly ], Motorola Moto G [ Stock JB ], & Google/Asus Nexus 7 2013 [ Stock KK ]
Previous devices: Sony Ericsson Xperia ARC ( Anzu ), Orange Monte Carlo ( ZTE Skate ), Orange San Francisco ( ZTE Blade ), & HTC Wildfire ( Buzz )

#51
Amphoras

Amphoras

    Addict

  • Members
  • PipPipPipPipPip
  • 766 posts

So, this is a bump for the above quote, yeah sorry for nagging :P just hope to have the questions above answered so I don't brick my Blade if I try doing the above flash methods.... Thanks for the reply...



As long as TPT works for me using the files in the above quote list I shouldn't come across any trouble besides reflashing a rom again from scratch that is :P... Atm, my Blade is only used for experimenting new flashes and custom setups I do extra for partitions and system/data app installations, so nothing important can be lost :D...


You'll need to use all the files to convert to stock Gen 2. Some of the files you haven't listed are still Gen 1 on your phone, so to be fully Gen 2 you need to use all the files with the flasher. Even if you didn't, I don't know if the flasher can flash only some files, or if its safe to do so. As far as I know no one has tried only flashing some files with it.

  • 0

TPT Helper lets you easily repartition your ZTE phone, install a new ROM and for the Blade, convert to/from Gen 2. Available for Orange San Francisco/ZTE Blade, Orange Monte Carlo/ZTE Skate and Orange San Francisco II/T-Mobile Vivacity. https://market.andro...horas.tpthelper

TPTs and other apps


#52
trueno2k

trueno2k

    Diehard

  • Members
  • PipPipPipPip
  • 495 posts
  • Gender:Male
  • Location:UK
  • Devices:SGS3 I9300 + OMC/ZTE Skate
Okay thanks for the reply, but any chances for answers in the below quote I originally posted in #37

... Seeing as I don't care about reverting back Eclair or even Froyo, can I use the same program used for unlocking the OMC / Skate to windows TPT flash my OSF / Blade to Gen2 permanently (using the Blade Gen2 stock TPT)?... I also remember by doing this I am unable to use the Gen1 to Gen2 TPT method once TPT flashing through the windows program, is that right or wrong?... Would that mean I'll have to use the windows program everytime I want to change the partition format on my OSF / Blade?...
...
...besides the upside down issue CWM 5.8.1.0 (supposedly touch version) is working... but this version still doesn't support ext4!... Is this due to the kernel or something, I don't understand why my Wildfire CWM has the option to partition my sdcards with ext 2, 3 & 4 partitions and it is only version 5.0.2.7?...

I'll do a search on XDA for the work needed on converting my Blade to full Gen2 Blade... However, to get me started can someone show me where I can get started for my research please?!... :P

Edited by trueno2k, 28 April 2012 - 11:18 AM.

  • 0
main-logo.pngSamba_hi_res_normal.jpg02_96x31.png14.gifreferral-ad-120x60.pnglogo-colors1-vflhO4gIp.png
Current devices [ ROM ]: Samsung Galaxy SIII [ CM11 Nightly ], Motorola Moto G [ Stock JB ], & Google/Asus Nexus 7 2013 [ Stock KK ]
Previous devices: Sony Ericsson Xperia ARC ( Anzu ), Orange Monte Carlo ( ZTE Skate ), Orange San Francisco ( ZTE Blade ), & HTC Wildfire ( Buzz )

#53
Amphoras

Amphoras

    Addict

  • Members
  • PipPipPipPipPip
  • 766 posts

Okay thanks for the reply, but any chances for answers in the below quote I originally posted in #37

I'll do a search on XDA for the work needed on converting my Blade to full Gen2 Blade... However, to get me started can someone show me where I can get started for my research please?!... :P


You just need to use http://android.modac...ra-via-windows/ and flash one of the packages that says it is compatible with Gen 2 TPTs (image.bin ones). You won't be able to use the Gen 1 to Gen 2 type TPTs any more, but you can use image.bin TPTs.

There isn't really any advantage to doing this though unless you want to go to Gen 3. Fully Gen 2/3 Blades have 15mb less space than Gen 1/hybrid Gen 2 ones, and the TPTs are more annoying to make. Fastboot doesn't work by default, so you'd need to use a TPT to enable that as well. Also if you ever need to go back to stock for the warranty, then its easier if you only have to use a TPT rather than the Windows Flasher as well.

  • 0

TPT Helper lets you easily repartition your ZTE phone, install a new ROM and for the Blade, convert to/from Gen 2. Available for Orange San Francisco/ZTE Blade, Orange Monte Carlo/ZTE Skate and Orange San Francisco II/T-Mobile Vivacity. https://market.andro...horas.tpthelper

TPTs and other apps


#54
trueno2k

trueno2k

    Diehard

  • Members
  • PipPipPipPip
  • 495 posts
  • Gender:Male
  • Location:UK
  • Devices:SGS3 I9300 + OMC/ZTE Skate

You just need to use http://android.modac...ra-via-windows/ and flash one of the packages that says it is compatible with Gen 2 TPTs (image.bin ones). You won't be able to use the Gen 1 to Gen 2 type TPTs any more, but you can use image.bin TPTs.

There isn't really any advantage to doing this though unless you want to go to Gen 3. Fully Gen 2/3 Blades have 15mb less space than Gen 1/hybrid Gen 2 ones, and the TPTs are more annoying to make. Fastboot doesn't work by default, so you'd need to use a TPT to enable that as well. Also if you ever need to go back to stock for the warranty, then its easier if you only have to use a TPT rather than the Windows Flasher as well.

Hi Amphoras, I should have asked you these questions in the beginning as I know you helped me & others out with the partitioning of the OMC / Skate :P ... So from all that explanation above, I should stick to the Gen1 to Gen2 method of TPT as it doesn't loose you stoarge space like Native Gen2 handset does, easier TPT just by placing the actual files instead of messing around with creating the image.bin file, and keeps it simple when I need stock rom for warranty purposes... SO, thats one less thing to think about now :P ... Thanks Amphoras

UPDATE: Just been playing around with version 5.5.0.4 of CWM recovery and found I can not mount my sdcard, gives me "E:Unable to open v*s lunfile (No such file or directory)"... Anyone else getting this problem???

Okay, back to my original topic!... Would love to get sdcard ext4 support and creation on any version of CWM like what we have on the HTC Wildfire!... SO, is there no interest in getting this to work?... Currently the only method I can find is by using a combination of terminal commands ( is that right? ) via a command prompt under Windiows on my PC using a guide I found on the net, which is sometimes a pain when I wanna either increase or decrease the size of ext4 on any of my sdcards I use on my devices... I hope there are interests in this area, as what I am writing here now, is just babble and a waste of post :P if I can not get any help soon... Or better yet, I'll go find the dev that released the 5.0.2.7 CWM version for the Wildfire and ask whether he could help out... Okay, thats enough from me :)
Laters Aligators! :P

Edited by trueno2k, 29 April 2012 - 12:31 AM.

  • 0
main-logo.pngSamba_hi_res_normal.jpg02_96x31.png14.gifreferral-ad-120x60.pnglogo-colors1-vflhO4gIp.png
Current devices [ ROM ]: Samsung Galaxy SIII [ CM11 Nightly ], Motorola Moto G [ Stock JB ], & Google/Asus Nexus 7 2013 [ Stock KK ]
Previous devices: Sony Ericsson Xperia ARC ( Anzu ), Orange Monte Carlo ( ZTE Skate ), Orange San Francisco ( ZTE Blade ), & HTC Wildfire ( Buzz )

#55
KonstaT

KonstaT

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,325 posts
  • Gender:Male
  • Location:Finland
  • Devices:Moto G, ZTE Blade III

UPDATE: Just been playing around with version 5.5.0.4 of CWM recovery and found I can not mount my sdcard, gives me "E:Unable to open v*s lunfile (No such file or directory)"... Anyone else getting this problem???

Yeah, same here. Strangely it worked on the previous build because I remember testing it then. I used some ancient ColdfusionX device tree to compile the previous versions. Bad news is that I just formatted my HD and installed another distro this week. Now I have no idea what's different compared to current CM9 device tree. There was at least some custom usb controller at that time (if it makes any difference). The ums lunfile path should be right I guess...

  • 0

#56
KonstaT

KonstaT

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,325 posts
  • Gender:Male
  • Location:Finland
  • Devices:Moto G, ZTE Blade III
Fresh (and hopefully final ;)) build of ClockWorkMod 5.5.0.4. Sdcard can be mounted as USB storage via 'mounts and storage' menu so this should be now fully working version.

Clockworkmod needs to have BOARD_UMS_LUNFILE defined so the diff to regular CM9 blade BoardConfig.mk is:
TARGET_USE_CUSTOM_LUN_FILE_PATH := /sys/devices/platform/msm_hsusb/gadget/lun0/file
+BOARD_UMS_LUNFILE := "/sys/devices/platform/msm_hsusb/gadget/lun0/file"

recovery-clockwork-5.5.0.4-blade.zip
md5:2c3ed2e4be8d00ed93d6a255bcc81604

recovery.img
md5:e93a357ec41f9e45101e643446e95f97

Attached Files


  • 2

#57
DrPaua

DrPaua

    Newbie

  • Members
  • Pip
  • 37 posts
  • Devices:Orange San Francisco

[...]Clockworkmod needs to have BOARD_UMS_LUNFILE defined so the diff to regular CM9 blade BoardConfig.mk is:

TARGET_USE_CUSTOM_LUN_FILE_PATH := /sys/devices/platform/msm_hsusb/gadget/lun0/file
+BOARD_UMS_LUNFILE := "/sys/devices/platform/msm_hsusb/gadget/lun0/file"
[...]


can you please explain that? :)

  • 0

#58
shanky887614

shanky887614

    Regular

  • Members
  • PipPip
  • 79 posts
  • Devices:orange san franciso
has anyone got a changelog between this and 4.0

  • 0

#59
KonstaT

KonstaT

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,325 posts
  • Gender:Male
  • Location:Finland
  • Devices:Moto G, ZTE Blade III

can you please explain that? :)

If you look at the ClockWorkMod source you can see that it uses the BOARD_UMS_LUNFILE path. It isn't currently defined in blade's CM9 BoardConfig.mk so I needed to add that one line (BOARD_UMS_LUNFILE := "/sys/devices/platform/msm_hsusb/gadget/lun0/file") to make the USB mass storage work in recovery.

Nothing major and it really doesn't concern anyone if you're not compiling it from source yourself. :)

  • 0

#60
andr0idbeliev3r

andr0idbeliev3r

    Enthusiast

  • Members
  • PipPipPip
  • 240 posts
  • Gender:Male
  • Devices:Sapo a5 (Portugal's ZTE Blade)
KonstaT cant you make Clockworkmod touch?

  • 0
Thanks to all developers for developing such beautifull and stable ROMS and thanks to Google for developing android aaaaand thanks to the original creators of android.

My devices:

ZTE Blade- MegaDrive 4.0.4




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users