yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] Bhargav97:
:FAQs:​

Q: Wanna know about Aroma File manager?

Visit the aroma file manager main thread for more info---> Aroma file manager main thread

Aroma file manager is a touch file manager which can be used while in recovery. It has options for copy, paste, delete,

change permissions and many others. Also, it has a Terminal inside. So, if you forgot to give correct permissions to any

file you can do that directly from recovery. This file manager has got many themes, font, icons, etc. options and it's UI

is fully customizable.

Q: How to start this File manager in Recovery?

Rename the downloaded file to 'aromafm.zip'.

Create a folder 'aromafm' inside 'Clockworkmod' folder on your sdcard.

Now, move that 'aromafm.zip' file to the 'aromafm' folder.

We're ready now, when you want to use it in recovery just double tap anywhere OR go to "philz Settings" and select

"Aroma File Manager" and it will start up.

If you also want to browse /data, /system and /sd-ext then mount them in the "mounts & storage" option in recovery.

Q: Problems with Aroma file manager startup?

After doble-tapping OR selecting 'Aroma file Manager' option under 'philz settings' if recovery gives error: 'aromafm.zip

not found at /clockworkmod/aromafm' then, wait for 4-5 seconds and again select 'Aroma file Manager', because it maybe

busy mounting sdcard.

If still doesn't work, you've made mistakes in steps mentioned in first post, please do again carefully.

Q: Does your phone every time reboots to recovery?

This happens very rare when you flash the recovery using any bad app or via any wrong (not proper) method. What you can do

is:

-If you've made a backup of your current ROM then just restore only it's "boot" and then select 'reboot to system'.

OR

-You don't have a backup? Then just flash the ROM which you are using currently again and wipe 'dalvik-cache'. Then reboot

to system. Booting process will take time.
[Samsung Galaxy Mini] Bhargav97:
NEW: Now you can enjoy the full version of the recovery! Thanks to [MENTION=4666971]Phil3759[/MENTION] for uploading necessary commits for armv6. And, everything is expected to be bug-free. Please report the bug here if you find any.

GALAXY MINI GOES OFFICIAL NOW!!!!!!

You'll now find Galaxy Mini in the officially supported devices list at the Main thread.

SCREENSHOTS:

Main menu and PhilZ Settings

GUI Preferences: all is applied live (no reboot). Up to 14 menu height settings, scroll sensitivity, touch accuracy...

27 color settings + 5 alpha transparency levels for every GUI element

Change background image with a custom png (of your device resolution), a solid color (27 presets) or revert to original

cwm image

User configurable touch gestures (feel free to request for new actions)

Setup your time-zone + 30mn offset, super wipe option to install a new ROM

Backup and Restore any partition in a complete freedom, include modem (.img + .bin) and efs (.img + .tar)

Custom backups can also be restored by original CWM Advanced Restore Menu

TWRP Backup and Restore Support + md5 + single/multivolume format

Support multi-cpu compression, md5 check toggle and custom .android_secure path

Choose ors backup volume target

Flash multiple zip files in a raw

Aroma File Manager + Terminal Emulator: launch with a gesture action (double tap is default)

Full Wipe to Install a new ROM (sdcard is preserved)

Free Browse Mode to install zip files: select a default folder to start with and browse up to the root
[Samsung Galaxy Mini] alexanderq:
Hello and thank you for your work but it reboot to recovery again and it says that cant find aroma.zip in path.
[Samsung Galaxy Mini] Faiyaz5yaz:
u hav to rename it to aromafm.zip

and yeah The Rom doesn't boot after installing this recovery
[Samsung Galaxy Mini] Bhargav97:
You mean, you are always rebooting to recovery and not to your rom?

If so, it is a problem of your device configuration by your device developer because this happens also in Jenkins recovery. This is not a fault of my recovery.

Now, you can restore boot of a backup (if you made any) or you can install your current rom again and wipe dalvik cache and you'll be back normal.
[Samsung Galaxy Mini] alexanderq:
But i have renamed the zip and it does not work.And i tried another ROM but it all ways reboots to recovery.
[Samsung Galaxy Mini] Bhargav97:
Can someone else confirm that it always reboot to recovery even after re-installing a rom?
[Samsung Galaxy Mini] Venkatesh:
Good work bro.:thumbup:
[Samsung Galaxy Mini] Faiyaz5yaz:
no

I didn't restore back up..

I reflashed my previous cwm..

it booted normally
[Samsung Galaxy Mini] ast00:
I confirm it. I even flashed another ROM and it still reboots to recovery instead of system.

Aroma FM works, but there is something I noticed: If you tap internal sd or external sd, they are empty, you have to go to storage/sdcard00 to get to your sd card. Can you somehow link the external sd to the sd card?
[Samsung Galaxy Mini] Bhargav97:
Thanks everyone for reporting....

I'll try to fix this when I get time...

ast00,

Internal sd and External sd will be empty because they are kept there for devices having two different memories. There should be an option: sdcard directly on the root directory. Please see carefully.
[Samsung Galaxy Mini] Bhargav97:
Good news:

My friend [MENTION=4141775]chraso[/MENTION] gave me hint about the problem. There was a very small problem with tags, I'll be fixing and making updated recovery today/tomorrow. Will also update recovery sources.
[Samsung Galaxy Mini] Bhargav97:
First post updated with newer version, v6.22.1 (18.03.2014) and also made changes so that you can boot into ROM after installing it. Hope it's fixed.

Also added some FAQs.

Please post back the Results after using it.

Please give feedback on swipe-touch. Is right/left swipe working? And please post your opinion on the poll above, whether you like swipe touch or it just makes things complex or you just don't like it.
[Samsung Galaxy Mini] Faiyaz5yaz:
flashed the latest zip

still not booting into the same rom..

didn't test new rom
[Samsung Galaxy Mini] Bhargav97:
Which ROM are you installing?

Is the install successful?

What procedure you follow? This is important, please tell me. Do you use 'wipe to install a new rom'?
[Samsung Galaxy Mini] alexanderq:
Does not work for me either, it reboots to recovery and i noticed that to make aroma work i must first install the zip from recovery and then it works OK .
[Samsung Galaxy Mini] Faiyaz5yaz:
not that

I mean I just changed the recovery didn't touch any roms.. after changing recovery , it keeps bootin to the recovery
[Samsung Galaxy Mini] Bhargav97:
Bro,

please read FAQs, this is a problem of your device sources. For solution, see FAQs.

After that, please give me broader report.
[Samsung Galaxy Mini] alexanderq:
You di not ask the right question:

Does this work for someone , anyone please confirm.
[Samsung Galaxy Mini] tiennhu89:
Confirm: not work for me.reboot to recovery always, not to system.
[Samsung Galaxy Mini] Bhargav97:
Seems like it's wasting my time to develop recovery for your device. Because, everyone is providing very short (1-2 lines of) feedback and it's very incomplete. All these is frustrating me.

You'll always reboot to recovery, it's a problem of androidarmv6 sources of your device.

Please read this FAQ:

If you still always reboot to recovery after doing both these things I told in this FAQ, then it's done other fault.

Please reply in detail after doing these steps.
[Samsung Galaxy Mini] alexanderq:
Well here is a more detailed report.

1) Wiped everything reinstalled rom (cm9) wiped dalvik same thing again.

2) Wiped everything reinstalled another rom (cm7) wiped dalvik but again rebooted to recovery.
[Samsung Galaxy Mini] Bhargav97:
Is this issue present in your Jenkins recoveries, please try the latest Jenkins and confirm if this issue persists.
[Samsung Galaxy Mini] masara59:
last omni and CM11 don't work.

recovery bootloop to recovery.

FAQ can't help me to reboot to system.

sorry for bad eng.
[Samsung Galaxy Mini] Bhargav97:
Please make sure you don't don't do 'Wipe to install new rom' after installing ROM.

I've made one for callisto and everything is working with the first build itselft. o_O
[Samsung Galaxy Mini] tiennhu89:
1st just help restore recovery and even when restore recovery i cant boot to system too.i dont know how to help u.just notice. :o
[Samsung Galaxy Mini] Bhargav97:
If it is so, its 100% problem in your device configuration at androidarmv6. Please ask your device developers to fix them first.
[Samsung Galaxy Mini] tiennhu89:
ok.thanks for your hard work guy!:o
[Samsung Galaxy Mini] Bhargav97:
There are no Jenkins recoveries for your device right now (I'm talking about new ones, not 2 months older). Once any android-experimental/android build is made for your device, just test that recovery.img and if everything works, just tell me here and I'll make a working philz recovery for you.
[Samsung Galaxy Mini] Bhargav97:
Can anyone confirm that it is right:

Location of Boot and Recovery partitions:

Boot: /dev/block/bml8

Recovery: /dev/block/bml9

Is it okay or wrong?
[Samsung Galaxy Mini] Venkatesh:
Bro check here for that

https://github.com/dany547
[Samsung Galaxy Mini] Bhargav97:
Is your device officially supported in TWRP? Then, what should I check? Where are the device-specific informations?
[Samsung Galaxy Mini] Venkatesh:
You'll find device specific info there....that guy has worked on twrp and cwm6 for our device...
[Samsung Galaxy Mini] Bhargav97:
But, that page redirects me to official Teamwin's Github page! And, there's no device-specific info there.

FYI: In fstab, I won't get what I want.
[Samsung Galaxy Mini] Venkatesh:
Sorry bro, i have no idea...vl look for that.
[Samsung Galaxy Mini] Bhargav97:
I confirmed from sources and the boot and recovery partitions are correct.

Now, there's only one way left:

-Install my recovery, and reboot to recovery.

-Install any ROM (no need for data-wipe) and then without rebooting anywhere, connect your phone to PC.

-Start ADB.

-Give this command:

adb pull /tmp/recovery.log

-Now, you'll get a file: "recovery.log" in your pc where adb is located.

Paste the contents inside this file at pastebin.com or just attach here after renaming to "recovery.log.txt"(because .log format is not supported in attachments, I think).
[Samsung Galaxy Mini] ast00:
There you go!

http://pastebin.com/9yeqXiA1

Just an info: Before flashing an actual ROM, I tried to flash a corrupted one.
[Samsung Galaxy Mini] Bhargav97:
Thanks...

I found no errors nor any doubtful things in the log. o_O

Will try to fix it if I found what's wrong.
[Samsung Galaxy Mini] ast00:
That's weird. By the way all the Jenkins recoverys do the same except for 1. I assume giving only the recovery.img doesn't help, but tell me if I should upload it. It's CWM 6.0.4.7 from Jenkins and sadly it's the only one so far that can reboot to system.
[Samsung Galaxy Mini] Bhargav97:
It just makes no sense bro. It's all same, the Terminal method or Installing from recovery via zip.

Giving that recovery.img won't help me. Though you can tell me date when it was made, it's actually not gonna help though.

So, as expected, this is problem of Jenkins recoveries (i.e.androidarmv6 sources), you can just wait until your developer fixes it.
[Samsung Galaxy Mini] ast00:
Sadly they are focusing on the OTA now. Even when we report a bug with logcat, they don't always respond, because they don't often check the thread. And sadly I don't know the date, because Jenkins already deleted the build.

So can you send them an email or something to get their attention?

Tapatalk-kal küldve az én GT-S5570-el
[Samsung Galaxy Mini] Bhargav97:
I'm not gonna do that. Just let them do what they are doing. Recovery is an afterthought for them. They'll first focus on making the ROM fully stable and then at last they'll be playing with recovery.

The recovery which you are using (Jenkins' working one) was made after 14-15th March or before that?
[Samsung Galaxy Mini] ast00:
It was somewhere around February 15th. Maybe even earlier.

Tapatalk-kal küldve az én GT-S5570-el
[Samsung Galaxy Mini] Harakhti:
Look into this.

http://review.androidarmv6.org/#/c/6205/
[Samsung Galaxy Mini] Bhargav97:
That's not yet merged because of some conflicts. What do you actually want me to do by seeing this? o_O

EDIT:

Thanks!! ;)

Sorry, I didn't saw that it was updated 5 days ago also by androidmeda. I synced my sources 7-8 days ago, so it was not updated. I updated it by myself and will compile today and give you guys to test. Hope that this time, it's successful.
[Samsung Galaxy Mini] Bhargav97:
Hello everybody,

I've updated philz sources to v6.22.5 (22.03.2014) and have fixed the tass defconfig file (thanks to [MENTION=4815693]Harakhti[/MENTION] to remind me about this commit) and have kept the recovery for compile.

If I don't get any major errors, I'll be back here by next 1.5 to 2 hours and post the recovery.img file. I need testers asap.

EDIT:

Due to my other ongoing project, It looks like I messed something up in my repo. I'll be making recovery tomorrow. Sorry.
[Samsung Galaxy Mini] Bhargav97:
Here comes a test:

Changes:

-Updated philZ sources to 6.23.8 (26.03.2014).

-Updated androidarmv6 sources so that cm-ota can be flashed without any signature verification errors.

-Changed tass-defconfig so that you can boot into system.

recovery.img:

http://www.upload.ee/files/3966387/recovery.img.html

Need feedback on what works and what not.
[Samsung Galaxy Mini] alexanderq:
I suppose it is safe for you to develop and play with others devices and then say that it is our devices or roms fault.Any way your new version does not boot at all it just stays to samsung logo.Thanks for nothing because mini is my only phone.
[Samsung Galaxy Mini] Bhargav97:
Recoveries won't brick your device. You can just flash any older recovery through Odin and you're back normal. This is still in test phase as said before. If you want to contribute testing, you can but you can't say I'm playing with your devices. You can brick your device if you don't know what you've to do in Recovery.

I don't see any reason that it stays at Samsung logo. How did you flash the recovery? Using TE or by making a zip? Make sure your download was completed and if you flashed using TE then make sure you typed- "recoveryonly" and not "recovery".

You should check out change #6205 at Gerrit, that's what prevents your device from booting to system and it's not my PhilZ recovery.
[Samsung Galaxy Mini] alexanderq:
Of course i'm trying to help testing but there you go and say that again:

I don't see any reason that it stays at Samsung logo. How did you flash the recovery? Using TE or by making a zip? Make sure your download was completed and if you flashed using TE then make sure you typed- "recoveryonly" and not "recovery".

I flashed the recovery through terminal i double checked the download and the commands and as you see in your thread its not my first flash and report about the recovery
[Samsung Galaxy Mini] arpitkh96:
Reboot to system is perfectly working for me
[Samsung Galaxy Mini] Bhargav97:
So, that implies everything else is also working and most importantly recovery is booting unlike alexanderq said.

So, you finally got a perfectly working philz recovery. :)

[MENTION=5225000]alexanderq[/MENTION],

Seems like it's your first recovery flash and report. ;)

Because [MENTION=4500270]arpitkh96[/MENTION] got it working.
[Samsung Galaxy Mini] alexanderq:
Hello arpitkh96

That is weird because i'm using your rom which is great by the way.
[Samsung Galaxy Mini] Bhargav97:
A recovery and a ROM has no relation. o_O
[Samsung Galaxy Mini] arpitkh96:
Can you compile twrp also?

There was also a guide for compiling ldpi twrp by dany547
[Samsung Galaxy Mini] alexanderq:
I'm sorry but i did not understand well your thoughts on this maybe my English are non good but what do you mean here

Q: Are you stuck at recovery? Phone every time reboots to recovery?

Ans: This is some problem with the androidarmv6 sources of your device.
[Samsung Galaxy Mini] Bhargav97:
I may compile it but after 10-15 days. Because, I'm very busy right now with my personal life.

And no need for a guide for ldpi compilation, I know what has to be done and I've already helped my friend [MENTION=4141775]chraso[/MENTION] (who compiled TWRP for Galaxy 5 before few days) in this matter. In short, TWRP is already there for Galaxy 5 and so, It would be easier to compile it for your device. So, I'll be doing that in few days as told above.
[Samsung Galaxy Mini] Bhargav97:
I think I've written clear enough.

Sometimes, flashing recovery by any other method/app, you may get your recovery installed successfully but when you boot in recovery and then select 'reboot system now', even then phone will reboot to recovery. So, for such situation...do as I stated there.
[Samsung Galaxy Mini] GoofyBaars:
flashed the zip stuck on recovery!

flashed the recovery.img: YES!! It's working.

Good job!! :D
[Samsung Galaxy Mini] laloyko:
Very Good!!! :highfive:

Every thing is working..

Nice work [MENTION=5165022]Bhargav97[/MENTION] :D
[Samsung Galaxy Mini] alexanderq:
Finally it worked for me too all i did was replacing recovery.img from zip and flashed from recovery then i did some tests and backup restore is working OK installed a new rom and everithing was OK.

Thank you for work and efforts.

P.S. Can you do something with aroma icons as thy are very small and blurry although i tried to change fonts.
[Samsung Galaxy Mini] Bhargav97:
Yes, Aroma File Manager is not resized for ldpi at all. Sadly, we'll have to stay on this version only until any artist ports it to LDPI. I'm not gonna do that.

Also, the original Aroma file Manger colors are Green and White. But we never get those. Even not in the one that's specially compiled for Mini. I'll have some discussion with Phil3759 and try to fix those colors and some other things if possible.
[Samsung Galaxy Mini] magmini:
i see u are talking about a fully working version. but i can't download it.

[MENTION=5165022]Bhargav97[/MENTION] may u uploud on mediafire or d-h.st ?

thanks for ur hard work dude
[Samsung Galaxy Mini] Bhargav97:
I'll do it for sure but after 10-15 days, My internet is highly misbehaving these days. It sometimes don't allow me transfer of 1 Byte even. Lol :p

You can still download from upload.ee, link is in first post. It gives instant downloads, so I choose it but it limits speed after uploading a certain number of files. You'll be getting equivalent to 20 KB/s of speed.
[Samsung Galaxy Mini] magmini:
:o ;)

edit:

ur link in first post need edit:

http://www.upload.ee/files/3966387/%20recovery.img.html

whole of text is not linked

thanks anyway
[Samsung Galaxy Mini] magmini:
[MENTION=5165022]Bhargav97[/MENTION]

i patched recovery.img and aromafm.zip in one file.

file manager will copy to sd automatically. can i share it here?
[Samsung Galaxy Mini] ast00:
Can I upload it and send you the link?
[Samsung Galaxy Mini] Bhargav97:
magmini,

My link is not broken. Seems like you copied it manually and pasted in adress bar which produced a space there and your browser added percent 20 for space.

It's ideally not good to push aromafm and recovery in one zip because there are people who need only recovery and not Aroma file manager. It would be a bandwidth waste for them.

But, it would still be helpful to some people who don't wanna download aromafm seperately. You can post a link here and I'll add it in my first post. Make sure that you use latest update-binary (from cm-11.0).

Ast00,

You can post the link here and I'll keep it in the first post. Make sure you use latest update-binary from cm-11.0.
[Samsung Galaxy Mini] ast00:
My plan was to upload the recovery.img only, but whatever.

Is it a new update binary if CWM 6.0.4.7 can flash it? Because that recovery can't falsh any ROM that isn't kitkat.
[Samsung Galaxy Mini] Bhargav97:
Yes, this is the update-binary you'll find in cm11 builds or omni 4.4 builds. As you said, your cwm 6.0.4.6 recovery (is actually old, now it can flash everything just like my philz recovery) can only flash cm11 roms that's because of the new update-binary. So, to make any zip flashable with this recovery, you'll have to add an update-binary from cm11/omni4.4. It won't affect older recoveries.
[Samsung Galaxy Mini] ast00:
I managed to flash this zip with CWM 6.0.4.7 and with this recovery itself, so I guess it works, it installed the recovery, I can reboot to system, it all works, so I guess it's fine, just let me know if I messed up anything, because I'm a derp at this.

http://www.mediafire.com/download/tvmxeev44u7a6cs/philz+6.23.8-cwm6.0.4.7-tass.zip
[Samsung Galaxy Mini] Bhargav97:
ast00,

Just rename that file to:

philz_cwm_advanced_6.23.8_tass.zip

I'll keep it in my first post.

Thanks.
[Samsung Galaxy Mini] ast00:
Done, new link:http://www.mediafire.com/download/fn54dm578k850tl/philz_cwm_advanced_6.23.8_tass.zip
[Samsung Galaxy Mini] magmini:
and what about name of recovery+aromafm?

philz_cwm_advanced_6.23.8_tass_aromafm.zip ???
[Samsung Galaxy Mini] Bhargav97:
There are no standards for it.

But still you can keep it: philz_cwm_advanced_6.23.8_tass+aromafm.zip
[Samsung Galaxy Mini] magmini:
ok, here is the link:

https://www.mediafire.com/?ix4kk4syn8xdw7m
[Samsung Galaxy Mini] sushil888:
support ???

dows this rec.. supports galaxy mini gts -5570?? & is it possible to flash stock, cm7 roms with this rex... ?

thanks in advance.
[Samsung Galaxy Mini] Bhargav97:
Stock ROM uses RFS file systems, so they can't be backed up/installed using this recovery.

CM7 can be flashed. But, you'll have to correct few errors in updater script file. Like: 5 args for format command.

I'm working right now on: TWRP. TWRP can also deal with stock ROMs but some work is needed.
[Samsung Galaxy Mini] arpitkh96:
Can u add root permissions to aroma file manager.otherwise it is useless
[Samsung Galaxy Mini] Bhargav97:
Please read first post. It already has root permissions.

As written in first post, to see and modify /system folders, /data folders, etc. Mount them respectively in Recovery.
[Samsung Galaxy Mini] tomi456:
Sorry for my n00by question, but how to correct these errors?
[Samsung Galaxy Mini] Bhargav97:
You can do this only after examining recovery logs (after installing cm7). Flash cm7. Use adb and give command:

adb pull /tmp/recovery.log

Then, you'll get recovery.log file at the location where your adb files are setup-ed.

See where the error comes and due to what it comes.

Generally, there are two errors (see below in example). FYI: You have to edit this file inside cm7 zip:

META-INF/com/google/android/updater-script.

Here's an example of what I had to do in cm7's updater-script file for galaxy5.

Two errors were as listed below.

-First one: Format requires five args instead of three or four or lesser.

This is the line in original updater-script:-

format("ext4", "EMMC", "/dev/block/stl12");

But, it has to be like this according to new pattern of cwm 6.0.4.5 (or newer):-

format("ext4", "EMMC", "/dev/block/stl12", "0", "/system");

So, I corrected it.

-Second one & the last one is that not giving permissions to the file that doesn't exist.

Line in original file:-

set_perm(0, 0, 0544, "/system/etc/install-recovery.sh");

But, the file 'install-recovery.sh' doesn't exist. So, I removed this line.
[Samsung Galaxy Mini] Bhargav97:
MAJOR UPDATE:

PhilZ Recovery updated to 6.27.9.

PhilZ Recovery FULL VERSION now enabled (Touch, GUI options and everything!).

CWM updated to 6.0.4.8.

Ready for official support!

I seriously want feedback on this version. If it is working, we can now get our phone in "officially supported devices" list.

Download link:

https://drive.google.com/file/d/0B5c3gpyMBJusWUh0T1Q5SUp0QnM/edit?usp=sharing

Also, try this new aromafm:

https://drive.google.com/file/d/0B5c3gpyMBJusLTk5ZENsNWpudms/edit?usp=sharing
[Samsung Galaxy Mini] alexanderq:
For me it reboots to recovery and not to system.