yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] John_Blaze:
No i havent checked that.. dont even know how and wouldnt even know what i was looking at if i seen it.. hahahaha How you doing Max? Havent heard from you for a few days.. this thread has really been slow the last couple days
[Desire Android Development] madmaxx82:
Thanks fine, just working on the app all the time. Hope to be able to release it in few days. Then I can start working on the recovery again.

And you?Soon returning home I guess ;)

About that md5 thing: If something doesn't install and aborts immediately, then the first thing to do would be check if the file on the sdcard is ok.

You can do that by generating the md5sum of your file and comparing that to the original file. Usually when you download a rom they also post the md5sum.

If they don't match, then your file is not ok and you should redownload it.

You can check the md5sum of your file by using the option in recovery, but you can also use 4EXT Updater Beta2 to do that :)
[Desire Android Development] John_Blaze:
Thanks bud.. youre to kind! :) Yea i leave in about a week and a half.. not looking forward to that long bus ride but it sure will be glad to get home. :)
[Desire Android Development] ptr_hamilton:
What?! Are we really able to check md5 checksums with the app? Amazing :) that's one of the features I always dreamed of Max.. Gonna try that right now, thank you so much!

One more feature I would like to ask you about is if you could stop that annoying haptic feedback in your recovery or just bring it to a minimum of vibration? I would really appreciate. Don't know what other users think but I don't need vibration on recovery ;)

Thanks for your work!

Sent from InsertCoin powered Sensation
[Desire Android Development] bmonster:
Just updated to rc3 thru app with no problems :)

4ext Next Generation Postponed :(
[Desire Android Development] madmaxx82:
I hate long bus rides too!

What are you doing at this nice place at the moment?
[Desire Android Development] madmaxx82:
Hehe yes, I first need to support more devices because they already wait really long now and I also should reduce startup time on the desire.. and finish the app ;)

But it will come.
[Desire Android Development] madmaxx82:
Hehe thank you very much :)
[Desire Android Development] eddyther:
Hi, here i am. ext4 partition working well

desde mi bq Davinci
[Desire Android Development] madmaxx82:
Welcome :) And glad to hear.

BTW:

When you tried ext3.. did you always boot your rom afterwards?

It could be that your rom is running a script which removes journaling from ext3 for the last bit of a speed increase sacrificing data safety.

ext3 without journaling = ext2.
[Desire Android Development] eddyther:
I always reboot. My rom is Reflex S 2.1.9

desde mi bq Davinci
[Desire Android Development] madmaxx82:
Ok, just if you are interested in finding out what caused that earlier with ext3, you could retry that.. convert from ext4 to ext3, but reboot straight into recovery again (using the power menu inside recovery). If it then shows ext3, we know what happened earlier ;)
[Desire Android Development] eddyther:
Ok, converting. In the meantime, is there any option in the recovery to change ext size partition?..i didn't find it!

desde mi bq Davinci
[Desire Android Development] beanbean50:
have a look in the advanced menu :)
[Desire Android Development] madmaxx82:
If you have enough space after your fat32 partition you can use the partitioning menu and select the option to "save my fat32 partition".

But be aware that it cannot shrink your fat32 partition!

If you don't select "start from scratch" it only works for recreating sd-ext partitions!

This makes only sense if you:

Have 2 sd-ext partitions, and now you only need one bigger one instead (removing the 2 sd-ext partitions and creating one large one)

Or removing a swap partition and recreate a bigger sd-ext partition instead.

Or removing a large sd-ext partition and creating 2 smaller ones (+swap if needed)

If you select start from scratch it will remove all your partitions and you can do what ever you want. But using that you lose your data on fat32.

If let's say your fat32 partition is 7GB and you only have 1 sdext partition which is 1GB and your sdcard has only 8GB, you cannot make your sd-ext partition bigger. You would need to select start from scratch effectively losing your fat32 partition, or if you don't want to lose data on fat32, shrink the fat32 partition first with any other tool first (gparted is recommended)!
[Desire Android Development] eddyther:
Ok thks. Rebooted and ext3 is there finally!

desde mi bq Davinci
[Desire Android Development] madmaxx82:
Ok, so your rom seems to be removing journaling from ext3.

That's why you always saw ext2 inside recovery after you booted your rom.
[Desire Android Development] eddyther:
You are right. After reboot]ting the rom and then going back to the recovery, it reverteed to ext2.

Ext4 will remain?

desde mi bq Davinci
[Desire Android Development] madmaxx82:
The only thing that differences ext3 from ext2 is journaling!

You can also switch off journaling for ext4, but there is much more to ext4 than journaling, so yes!
[Desire Android Development] eddyther:
Ok, so i will leave ext4 permanently, thanks!

desde mi bq Davinci
[Desire Android Development] madmaxx82:
np :)

Glad this mystery is solved.
[Desire Android Development] eddyther:
Thanks for all the help! :)

desde mi bq Davinci
[Desire Android Development] John_Blaze:
Well last night i went out to the bar.. had a cool band there. This wed prolly gonna go hang out at the beach all day
[Desire Android Development] :
How is it possible that all of a sudden my sdext is ext2? thats what the 4ext app tells me :(
[Desire Android Development] ptr_hamilton:
Well just read a few post above, maybe the same happened to you?

Sent from InsertCoin powered Sensation
[Desire Android Development] :
Weird tho that in recovery it states ext4. So what to believe now?
[Desire Android Development] eddyther:
NeoPhyte disables journaling in his roms in order to use tune2fs for increasing speeds.

No idea yet why some people seem to have ext3 intact with his roms. When i will have the answer i will let you know.

Maybe after the formatting they never check again...

desde mi bq Davinci
[Desire Android Development] kazgor:
anyone used this to convert from EXT3 to EXT4 without loosing the existing data?

just found i've ended up on an EXT3 whilst using a CWM4.x

ta
[Desire Android Development] madmaxx82:
Recovery!

Your 4ext version is too low for the app to be able to read values exported by recovery!

If the app cannot find info from 4ext it uses the values that are reported by the running system which can be false.

Just check with adb shell cat /proc/mount

You will see the same values!

Upgrade 4extrecovery to at least 2.1.3 rc2 (would recommend rc3) and the values will be ok!

If he disables journaling on ext3 then this IS ext2.

Ext3 minus journaling = ext2

But ext4 minus journaling is not ext2.

You won't lose data! Check you have enough free space on your sdcard before doing that!
[Desire Android Development] madmaxx82:
That sounds ****ing great :)

Would love to be there! Instead I'm hanging around in a little flat sitting in front of my computer all day :(

Can't you buy me a flight to your location? :D
[Desire Android Development] kazgor:
Thanks.. converted back to an EXT4 partition from EXT3 and worked fine with no lost of data.

Great when things just work as they should.

out of interest what versionof CWMR is this Recovery base on. how much different is it to say latest 5.0.1.0
[Desire Android Development] madmaxx82:
It's still based on 4.0.0.5 with few custom fixes.

This is completely stable.

Judging from the changelog, 5.x is the first version of CWMR that -like 4ext- also remembers your file system on backup/restore (the lack of this feature in previous versions of CWMR was the reason why I even started making 4ext 3 months back).

But there is also another new very nice feature: tar backups. This has a speed advantage when backing up. The code for that is also in 4.0.0.5, but in that version it needs to be enabled at compile time. Since this is now enabled by default, I'm sure the code for that has changed/improved in 5.x.

From what I've gathered, there are still some issues with cwmr5 though.

I will of course update to the latest once/if the source is available and stable.
[Desire Android Development] madmaxx82:
Beta 4 is up :)
[Desire Android Development] angusc:
MadMaxx,

I just updated to Beta4 and the install zip worked wonderfully, thanx!

However a couple of observations. It would be nice if 4EXT Updater could show me my current RECOVERY version?

I did a back up from within 4EXT Updater and it all worked brilliantly! But it would be good if you kept the same file naming protocol as if i had made the back up the old traditional way by booting in to RECOVERY first then selecting back up option from there.

The backups done from RECOVERY are named like:

2011-09-02.09.18.53_CoolSensationv7

The backup done from 4EXT Updater is named like:

9511300PM_1.35.75.1
[Desire Android Development] angusc:
Madmaxx,

Please I need your help with ADB......hope you dont mind me spamming it here in your 4EXT thread?

I have the ADB files copied to my C:\android-sdk-windows

I open CMD window and CD to the C:\android-sdk-windows\platform-tools folder

I boot my phone in to BOOTLOADER

I plug in my USB cable

I see on the screen FASTBOOTUSB

I type in to CMD window: adb.exe

I see the help menu scroll by and end with the prompt: C:\android-sdk-windows\platform-tools>

I do not get any symbol prompt like a $ or a #?

If i type "fastboot devices" then it shows: "SH0AMPL06166 fastboot"

if i type: "fastboot oem boot" then the output is as expected and the phone reboots

If i type: "adb shell" then the out put says "error: device not found"

Observations: in fastboot the phone drivers are recognised, but if i swap to HBOOT mode then the "dig-dong" from my PC and up pops the "windows has found new hard ware..." I'm not sure if this is relaveant or not. I did originally install the required Windows drivers when i first installed ADB to my PC.

It seems to me that ADB is half working but not fully? I wanted to learn how to use ADB and be able to push files back and forwards to the device and PC.....

Can you offer me any assistance?
[Desire Android Development] madmaxx82:
Hey, thanks very much for that great feedback Angusc!

Your current recovery version is yellowish/orange where you browse all the versions to download. I know I must improve that, why should anyone know that ?:D However you see the version/color changing as you flash different versions.

Blue = older, Red= newer, Yellow/Orange is yours.

You also see the version when you open partition info.. that screen should be as similar as possible as the one you get when you boot recovery.

Your colours, your background, your version and the info about your partitions :)

Regarding the naming of backups: It is using the time and date format of the timezone you are in. I thought it would be better to use your real time and because you can change the name completely anyway, didn't think of that.

If it's because of sorting.. the app should sort it as much as possible by date and not by its name.

About the second number in your example after the date&time: there should of course be your rom name. It seems it wasn't detected properly. Does recovery detect your current rom?
[Desire Android Development] madmaxx82:
No problem :)

adb only works when an OS is booted or while it is booting (recovery or a rom).

About the missing # or $: that would be a unix shell prompt. You only get it if you open a shell on your device by issuing "adb shell".

Fastboot is different.

In fastboot mode your device is recognized by fastboot, but not adb.

In bootloader mode however, your device isn't recognized by either tool ;)
[Desire Android Development] TheUntouchable:
Any info about timeline for sensation ext4? I hate cwr.. :D
[Desire Android Development] dirkw01:
Hello madmaxx82,

I've just installed your app and it looks at this point already fabulous. :cool:

I can put another example in the case above:

Telephone software info says : 'LeeDroiD_HD_V3.3.3_GB-R5'

4EXT uses : '3.3.3-R5'

Is there maybe a 'long' infostring and a 'short' infostring about the ROM version?

Cheers

Dirk
[Desire Android Development] :
Thx for the advice ;) It is indeed ext4 :)

But am I dumb? I can't find rc3?!
[Desire Android Development] angusc:
OK! well I guess as time passes I will see the autum colours of your novel idea coming!!

Both back up examples that i gave you are of the same ROM so with 4EXT RECOVERY back up it correctly detected the ROM name (CoolSensationv7) but via the 4EXT Updater it did not detect the rom name.

If i ADB :o this cmd: getprop ro.build.description it returns Cool Sensation v7
[Desire Android Development] angusc:
OK! now i learned another thing today! so i tried a few simple commands but none worked can you review and advise where I'm going wrong please?

Phone in RECOVERY mode:

~ # su

su

/sbin/sh: su: not found

~ # shell

shell

/sbin/sh: shell: not found

~ # adb

adb

/sbin/sh: adb: not found

~ # adb shell

adb shell

/sbin/sh: adb: not found

~ # help

help

/sbin/sh: help: not found

~ # adb help

adb help

/sbin/sh: adb: not found

~ # mount -o rw,remount /dev/block/stl9 /system

mount -o rw,remount /dev/block/stl9 /system

mount: mounting /dev/block/stl9 on /system failed: Invalid argument

~ # getprop

getprop

/sbin/sh: getprop: not found

~ # adb shell

adb shell

/sbin/sh: adb: not found

~ # getprop

getprop

/sbin/sh: getprop: not found

~ # getprop ro.build.description

getprop ro.build.description

/sbin/sh: getprop: not found

~ # adb reboot recovery

adb reboot recovery

/sbin/sh: adb: not found

~ #

EDIT: OK so when i booted the phone in to the operating system, now the commands seem to work. however i had thought that the idea of sending system files to the operating system was to do it when the phone was not using them i.e. when in recovery, fastboot etc....... so the system did not get corrupted when changing out critical files?
[Desire Android Development] madmaxx82:
As soon as any CM build is officially available for the sensation :)

Without I would need to do a lot of work on my own. You surely remember how long it took to get cwmr on the sensation..

I will start supporting more devices *very* soon. And I'm sure that it won't take long for an official CM build to appear ;)

BTW: Don't you already have a nice custom recovery for the sensation? From TWPR? How do you like it? From what I've gathered it's more like Amon Ra type.

Thank you for reporting.

Yes and no.. the problem is that rom builders put their rom names into different locations.. there are basically 4 different ones. Sometimes location1 is used for the name, sometimes for the version number, sometimes not at all..

I need to find the location most likely containing a rom name.

4EXT- Recovery already detects most names properly and of course the app should be at least on par with that.

I will improve that for the next beta!

In the app you should see 2.1.3 rc3..

Thanks for reporting too :) Will improve the detection in the next beta!
[Desire Android Development] madmaxx82:
ok. First thing is: you use adb only top open up a shell on your device and to connect to it.

There is no adb command inside the shell then when it is opened.

Regarding your mount command.. I guess this is no Desire?

I don't know about what partition you want to remount there..

Is /dev/block/stl9 already mounted on /system? You can check that with just typing "mount"

Regarding other commands, they most often depend on your installed busybox if they are available or not.

Sometimes it's also possible that the link to busybox for a give command doesn't exist.. you can then work around that putting "busybox" in front of your command.. just like "busybox mount -o rw,remount /system"
[Desire Android Development] dirkw01:
I think you should aim for the string, which is used in [german] "Einstellungen | Telefoninfo | Software-Informationen | Software-Nummer" [/german] ;)

Cheers

Dirk
[Desire Android Development] angusc:
Madmaxx....... you teached me I give you this: getprop ro.build.description

it gives the ROM name for me, it returns "Cool Sensation v7"
[Desire Android Development] madmaxx82:
Yes ;)

That's one of the locations I check. For another rom it's again different.

It's just my checking algorithms have a bug.

It will be the same as in 4ext after correcting that ;)
[Desire Android Development] madmaxx82:
Hehe it's not that easy ;)
[Desire Android Development] tids2k:
maxy @ any chances you can upload the sources or port it to samsung gs II
[Desire Android Development] madmaxx82:
Will make one for the gsII :)
[Desire Android Development] madmaxx82:
Okay, think I fixed it.. did a very stupid mistake.. forgot an "else" :D

Please try if beta5 fixes your romname detection.. you don't need to start a backup for that.. just use view partition data ;)

Recovery Control Beta5 (got renamed.. so please uninstall Recovery Updater)
[Desire Android Development] ptr_hamilton:
Thank you Max!

My backup names were always correct and still are ;) Is it just me or is the beta5 more responsivley? Really great features included :eek:

Thanks

Peter
[Desire Android Development] ptr_hamilton:
**10chr***
[Desire Android Development] n0j0e:
Cant flash recovery from Recovery_Updater or new Recovery_Control.

No installed recovery anymore after flashing. :(

Tip when lost recovery installation (Desire Bravo!):

Extract the recovery.img where fastboot.exe sit (4EXTRecovery_v2.1.3RC4_bravo.zip or any other recovery system)

Go into fastboot (Vol. down + Power)

Connect usb cable

run cmd > fastboot.exe flash recovery recovery.img

Go in to Bootloader > Recovery

Voila.
[Desire Android Development] madmaxx82:
Everyone using the app to do backups and use its functionality to select the partitions you want to include/exclude in the backup, please upgrade to 4EXT-Recovery v2.1.3 RC4!

This version also fixes a very very rare bug I stumbled upon by accident :p
[Desire Android Development] Jagdish84:
You're just aces mate, Cheers!
[Desire Android Development] EViollet:
When I select "view partition data", all I get is a black screen. Is this normal? Have I done something wrong?

Regards
[Desire Android Development] mattman83:
I have to say, with the updater app, this is the first time I've ever bothered keeping a recovery up to date. Previously it's always been too much hassle but this make things super easy :)

M.
[Desire Android Development] Jagdish84:
Max, are you planning on adding an option to flash an img file? or is this option available and im just being dumb atm...

The lack of this option kindda renders the 4ext updater moot, as we still have to use the computer to flash the img itself...

Thx in advance.
[Desire Android Development] madmaxx82:
Why do you have to connect to a computer?

The App flashes recovery without the need to do that.

select a version, view its changelog and click on download and it will download and flash automatically..
[Desire Android Development] madmaxx82:
Hmm.. do you have 4extrecovery installed?

If it's your first time, please boot it once and return to view partition data.

This should not be needed, but it would help me track down a possible bug with that function.

Thank you very much! :)
[Desire Android Development] madmaxx82:
First report of such an issue.. That's really strange...

Did it say flash successful?
[Desire Android Development] Jagdish84:
Right, that was my bad, had to install the updater version from the first post again, was sure i did so already, anyways, working perfectly sorry for my ignorance :P
[Desire Android Development] steveathome:
Hi Max, the app says this alpha version expired is there a newer one. Won't allow me to update. :)
[Desire Android Development] madmaxx82:
When it says it is done?

What exactly does it say?

First is the download, then it checks the md5sum of the downloaded file, then it unpacks the zip and checks the md5sum of the image file inside. After that it asks for superuser ans says flashing.. and ok/not ok.

Where does it stop for you?

Does it happen when trying to flash a previous version too?

Hey :)

Please download the beta from here: Beta 6
[Desire Android Development] madmaxx82:
Reading your post again.. this is not the purpose of the app.

You shouldn't need to do this manually..

Usually the app deletes the zip file after flashing and if it was unsuccessful. Might be that this didn't work in the alpha or previous beta versions..

Please guys help me identify the problem some of you seem to have as it works for all other devices and most users on the desire.
[Desire Android Development] madmaxx82:
Ahh thanks for telling me :)

All's good then :)
[Desire Android Development] steveathome:
Thanks Max you are a legend! :)
[Desire Android Development] :
Can you rename the apk in the settings > applications and so on? Would be easier to find if it says 4ext Recovery Updater instead of just Recovery Updater
[Desire Android Development] madmaxx82:
Hahaha thank you :) I hope it works for you and you don't slap me with something big when you find a bug :D
[Desire Android Development] madmaxx82:
Of course!

I will change the name before it's going to the market.
[Desire Android Development] Jemus42:
I just tried out Recovery Control beta5, but the detection might still be off.

I'm on MIUI XJ 1.9.2 GB 2.3.5 (what I expect the ROM name to be)

and the app as well as the actual recovery (2.1.3 rc2) tell me the ROM name is libra_bravo_userdebug 2.3.5, which at least gives me the GB version, so… yeah.

Also, the partition info shows me I'm on ext2 as well, but I formatted the whole sd card with 4ext a few weeks ago and the recovery tells me I'm on ext4 as expected.

TL;DR:

MIUI XJ 1.9.2, 4ext Recovery 2.1.3 rc2, Recovery Control beta5:

ROM name detection off, data fs detection off.

(HTC Desire)

Otherwise: Great idea for the app, looking forward to a stable version :)

Oh and by the way, the app (beta5) tells me there's a new version of the app, but it's the old version with the different name.

EDIT:

Dammit, when I first tried to post this like 1-2 hours ago the site gave me an error, so I copy/pasted the post text and F5'ed every once in a while to see if it works again, now I made this post and missed there's a new beta :) Trying that out now.
[Desire Android Development] madmaxx82:
The new Beta has a new name!

You need to uninstall Beta5.

I'm sure you already installed the new one, but started the old.

Regarding detection of file systems from inside the App:

I already said that: The app can only reliably tell you which file systems you have when you have at least version 2.1.3 RC2 of 4extrecovery!

If you have a lower version number, then the app is using the info as reported by your running system which might be wrong!

Edit: I will add that info to the changelogs!

Take a look with adb shell mount and you'll see ext2 there (in your case).

Regarding detecting romnames.. that's not so easy and MIUI is a bit *different*.

I'm glad the app is detecting romnames now as good as 4extrecovery itself.

I might be able to improve that a bit in 4ext and in the app..
[Desire Android Development] :
I flashed the 2.1.3 rc4 through the newest app version beta6, is it I guess?

But when I want to go into recovery I end up everytime in bootloader :(
[Desire Android Development] madmaxx82:
Did you use the app to reboot into recovery or something else?

Reflash please.. sounds like a bad flash.
[Desire Android Development] :
Yeah I tried all 3 possibilities... through app, power menu and bootloader. nothing works. but i will try again ;)

Edit: I am in recovery now after reflashing. Booting into took a while but it's working ;)

Edit2: solved! Took about 5minutes ;)

Are you planning to include the themes in the app? Make it possible to download them through the app I mean :P