yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] Shadow Of Leaf:
For the recovery i will try my best to fix it

For cm11 i will build cm with updated display blobs to fix the white screen and other problem

I will try to analyse the nfc problem and try to fix it

So wait for the new build
[Samsung Galaxy Mini] Don Pedro!:
The white screen issue exists since a long time in several CM releases. It seems there are subtle hardware differences in the Galaxy Mini 2 that trigger this. Some devices have the white screen problem, others don't. For the developers of a custom rom this is always difficult to tackle, as most of us have only one mini at hand to test with. So it's difficult to test stuff for all hardware revisions. Luckily according to his post, Shadow of Leaf seems to be able to include all blobs that are required for different revisions. I'd suggest you patiently wait for his next build that will hopefully fix those issues.

Aside from that IMHO we all should be very glad he resumed work on the mini and try to free his time as much as possible for the development towards CAF (instead of asking for support on current roms that will be outdated after he succeeds with CAF).

HTH

Don
[Samsung Galaxy Mini] amag3308:
got problems with my main phone, so came back to this little boy. installed your rom it's awesome how it performs well even after years.

could you please tell me which theme did you use here? it is a touchwiz one and I really like it, but can't find that one
[Samsung Galaxy Mini] Shadow Of Leaf:
look at here https://xdaforums.com/crossdevice-d...s/cm11-theme-samsung-touchwiz-ashish-t3070122
[Samsung Galaxy Mini] Shadow Of Leaf:
Hello

well finally after a long time of intelligence :D i build TWRP 3.0.2 With CAF blobs for Mini 2

i will work on cm11 with caf too if i have time :crying:
[Samsung Galaxy Mini] simika:
so cool to this this project is not end :)
[Samsung Galaxy Mini] Don Pedro!:
Is TWRP already usable on its own, means can I install it as a recovery on a current ROM and does it make sense to do so?

THX

Don
[Samsung Galaxy Mini] Shadow Of Leaf:
TWRP 3.0.2.0 experimental and just for testing cm11 with caf support

by the way random reboot is fixed

if someone want to test it PM me
[Samsung Galaxy Mini] Don Pedro!:
Yes, but be aware that there's only one single developer who is capable of developing and committed himself to the mini. So this is very thin, development is of course rather slow and if SoL decides to abandon his efforts newer CM for the mini will probably always stay a dream. I would be lucky if I could help him, but I'm definitely lacking the time as well as the Android experience to be able to reasonably support him with coding/porting (though I have 20++ years of programming expierience). I also have the impression that developing a custom rom for Android comes with a rather steep learning curve, finding out all the required details is a very lengthy process, especially if you're new to those stuff.

Cheerz

Don
[Samsung Galaxy Mini] Shadow Of Leaf:
thanks for the motivation

about cm11 caf

yesterday i build it on caf support but in booting screen is black , maybe i did something wrong:confused::confused:
[Samsung Galaxy Mini] Don Pedro!:
Is only the boot screen black or doesn't it boot at all? If it was just the boot screen but the system is comming up anyway I could live with that... ;)

Cheerz

Don
[Samsung Galaxy Mini] Shadow Of Leaf:
It bootup but screen is black

I did adb logcat and take some informations

1-there is some news about nfc

I see that the kernel error is fixed and in logcat it seen that nfc is enabled in first boot

2-blackscreen is the display when i build i didnt include the kernel stuff

3-i change the device tree to fully support emulated storage and it work (in logcat)

I will work more further on jenq until it boot
[Samsung Galaxy Mini] Shadow Of Leaf:
GOOD NEWS

TWRP 3.0.2-0 for jena is ready to test

link of download : http://www.mediafire.com/file/2jp8yqat2cqeznb/TWRP-v3.0.2.0-jena.zip

as a far as i test

-fix suddent shutdown

-fix storage and mtp

-fix recovery loop

to enter the recovery mode in shutdown :

-go to mode download

-press volume down

-before the phone reboot hold home and volume up until samsung appear

-you are in recovery
[Samsung Galaxy Mini] Don Pedro!:
Good to hear, will give it a test as soon as I manage to find the time for it. Can I flash the new recovery directly with the old TWRP 2.8.5.0 or will I mess things up?

As someone gave me a second phone (a HTC Desire 626G Dual SIM) my mini became free as a test device I can play around with. So if I find the time I would be happy to test new software, be it a recovery or a more recent android. This is for two reasons:

a) On my mini I'm still not able to use your CM11.0 (it shows an endless boot animation during the first initial boot and never finishes booting), whereas the older CM10.1 works without problems (aside the well known fact that something's draining the battery). So the hope would be to overcome this boot issue with a more current CM.

b) The HTC is an old phone, it also uses Kitkat, and of course I would be eager to flash a newer ROM. However there are many different versions of the 626 out there, I couldn't find a custom ROM that exactly suits this phone and I don't want to brick it by flashing some ROM that sounds similar (but is not). So my hope is I could somehow learn how to create a custom ROM myself, though I have no idea what the requirements are and where to start. So far I was able to flash a CWM and I could root the HTC, which sounds like a good starting point. Do you know any instructions on the net explaining how to develop one's own ROM?

If I understood you correctly then you suppose NFC might become operable on the mini with the CM you're currently working on? I never used NFC so far but latest c't magazine has a nice article on securely unlocking a password manager like kee pass on a mobile via an NFC badge. This is a real nice application and gives NFC a real value. Getting that up'n'runnin on the mini would be brilliant.

Cheerz

Don
[Samsung Galaxy Mini] Shadow Of Leaf:
it will work normally

for bootloop you didn't format data partition with ext4 type partition

go wipe , advanced wipe , choose data , repair or change file system , change file system , EXT4, confirm ,done

cm11 will work
[Samsung Galaxy Mini] Don Pedro!:
Hm, not sure (it's been a while since I tried it). But if I remember correctly I strictly followed the instructions you posted and I did format the data partition. Will give it a second try when I install/test the latest TWRP and report.

Cheerz

Don
[Samsung Galaxy Mini] ezrawk:
Can you compile for jenad? :(
[Samsung Galaxy Mini] Shadow Of Leaf:
this is just a test recovery

since it will be my last update for the mini 2:crying::crying:

i will build for s6500 and s6500d (cm11 and latest twrp recovery)
[Samsung Galaxy Mini] ezrawk:
Thanks mate, much appreciated. Thank you for all of your work for jena & jenad. :good:
[Samsung Galaxy Mini] Shadow Of Leaf:
nfc

new interesting news for nfc

i test some theories and i get some results

you can see it in logcat

I/NfcService( 674): Enabling NFC

D/NFCJNI ( 674): Start Initialization

E/NFCJNI ( 674): Could not load EEPROM settings

D/NFCJNI ( 674): Terminating client thread...

W/NfcService( 674): Error enabling NFC

this means that it pass the downloading firmware
[Samsung Galaxy Mini] Adiker:
Newest CM11 doesn't work even with data formatted to ext4. Stuck on infinite bootloop, occasionally the animation locks up. However 20160114 version works just fine without any modifications to data partition. The only issue is with camera, it simply doesn't work :P
[Samsung Galaxy Mini] Don Pedro!:
I have this problem too, also with data partition to ext4. But on the other hand we have a lot of folks here that confirm they could boot that cm11 ROM. So there must be some difference, maybe in small hardware differences? What do you mean by "20160114 version"? Ist that the old cm10.1 version from bleached or is it an older cm11 version from Shadow od Leaf?

Regards

Don
[Samsung Galaxy Mini] Adiker:
I downloaded older version from MediaFire. It is CyanogenMod 11. I have no idea who made it, but it worked. I couldn't transfer files from my PC and it lagged a lot though. I can't find it now but tomorrow I will search in history and provide the link.

I finally gave up with this phone because it lags a lot and for me using it is almost painful [emoji14] Regarding the version in this thread, I installed it via CWM because TWRP version in instruction doesn't see internal storage or SD card. Newest version of TWRP on 1st installation attempt gave me error 7. On 2nd attempt it eventually installs ROM successfully but I can't pass "Samsung Galaxy Mini 2 S6500 - cyanogenmod" screen. Whoever is still using this phone, it's really time to change because there is no modification that makes this phone fast and fully usable. Maybe this ROM is the way to go, but yeah, I've been trying many times and it never worked.
[Samsung Galaxy Mini] Don Pedro!:
Well, you have to respect the fact that this is a phone with very limited hardware ressources, it's just a tiny single core processor with a very low clock and the machine has a very small amount of RAM and a low-res LCD - what do you expect? So whatever CM version you put on it, naturally there can be no big performance boost. But this is not what it's about. The aim would be to have an OS running on it that is acceptably young enough, that is capable of accessing the complete hardware and is not draining the battery unneccessarily fast.

Don
[Samsung Galaxy Mini] Shadow Of Leaf:
the latest version of cyanogenmod 11 is ready , just need uploading and there where be also a video on how to install it

after i will build the latest omnirom version for mini so stay tune
[Samsung Galaxy Mini] Don Pedro!:
Nice to hear that this tiny thing is still being worked on. Just email the link if you did the uploading and we'll give it a try.

Hm, what means "latest" omnirom? Does it mean if this works the mini will get a very current Android?

Cheerz

Don
[Samsung Galaxy Mini] Shadow Of Leaf:
this means that omnirom is my last work on mini 2 , i will also upload source code on github to anyone who to build android for this little thing

when i get a stable omnirom (omnirom is android like cyanogenmod but less heavier ) i will discontinued this work

i know some users will be upset but look

there is new phones with a limitless specs (8gb ram and 256gb rom) the mini 2 seems to be their grandfather :silly::silly:
[Samsung Galaxy Mini] Shadow Of Leaf:
Thread Updated With Latest Cm11 And Latest TWRP

Enjoy

Omnirom is Uploading when it Finished I Will Create a New Thread for it

For Who Have Problem With Installing Cm11 on S6500 I create A Help Video On how to flash it Correctly
[Samsung Galaxy Mini] Don Pedro!:
THX for sharing. Downloaded it (huh, GAPPS took incredibly long, it gave up and I needed to restart two dozend times until it finished downloading but finally managed), willl give it a try ASAP and report.

BR

Don
[Samsung Galaxy Mini] Shadow Of Leaf:
It worked ???

If you find any issues please report it

For omniron each time i upload , it failed

When it upload , i will create a thread
[Samsung Galaxy Mini] Don Pedro!:
Could do some testing now:

The new TWRP doesn't work on my phone, trying to boot into it just yields a white screen and that's it (tried twice to flash and boot into it). Had to step back to the previous TWRP with the reboot issue.

Was able to flash the latest CM11 after three tries with this broken TWRP.

But it seems I have the same problem with this latest CM11 version as with your previous one, boot animation is running endlessly and the phone never completely finishes the boot process (gave up waiting after around 20 minutes).

Will make a second attempt in the next couple of days: Factory reset the phone and step back to default FW before updating to CM11. However I must admit I'm meanwhile pessimistic about that attempt, I never got CM11 running on my phone. Seems there are subtle hardware differences with this phone that prevent it...

Will report what I can find out ASAP...

BR

Don
[Samsung Galaxy Mini] Shadow Of Leaf:
Weird , it work on my phone

Did you see the installation video cause i explain a lot of steps to work on it

And do not try the old twrp with new cm11 cause

They dont have the same emmc config
[Samsung Galaxy Mini] Don Pedro!:
Yep, I saw the video. I think the content is clear, you showed the steps the have been previously described in written form. The first step is to flash TWRP via ODIN on the phone, I did so (it's not really difficult and the flashing passed flawlessly in ODIN) but couldn't get TWRP running. My question is: Can I flash the new TWRP over the old one? Or do I need to flash back to stock FW first before flashing the new TWRP?

So if I don't get the new TWRP running I don't need to proceed any further with the new CM11. I couldn't get TWRP running - well sort of. When I flashed it the first time with Odin and booted into recovery I had an all white screen, but it seemed to have been alive somehow, I could tap on the touch screen and it gave me that usual clicking sound. So maybe TWRP was running under the hood but I was suffering from some modification of that white screen problem others had with this phone before?

Whatever is the case, if you say old TWRP and new CM11 don't cooperate then I don't need to test that any further and I'm stuck here until we can find out the reason for the white screen and fix it.

BR

Don
[Samsung Galaxy Mini] Shadow Of Leaf:
The old twrp Will not work with the new cm11

So test this

Go to the twrp 3.0.2.0 thread and download the flashable tWrp (zip) and flash it over the old one

Then reboot and format data partition to ext4

Then install cm11 and gapps

And answering to your question

Flashing the new twrp doesnt require returning back to stock rom
[Samsung Galaxy Mini] Don Pedro!:
Did so and it worked now, I could install TWRP 3.0.2.0 and I could install CM11 and it booted! I think I have an idea why it did'nt work the first time, I had the old CM10.2 on this machine and after flashing TWRP the phone will reboot and if you're not fast enough the old ROM starts booting. I think it does something weird and damages TWRP and it cannot be booted afterwards.

OK, I could successfully update the phone to TWRP 3.0.2.0 and CM11 now. THX for your support!

BR

Don
[Samsung Galaxy Mini] Shadow Of Leaf:
You Welcome im glad to help you

You could test omnirom also
[Samsung Galaxy Mini] Don Pedro!:
What advantages has this compared to CM11? From your screenshot I can see both are based on android 4.4.4. How much memory will omnirom save?
[Samsung Galaxy Mini] Shadow Of Leaf:
Not much

But test it and compare
[Samsung Galaxy Mini] elmejorj:
recommendation

Excellent work :fingers-crossed: but I do not recommend installing gapps-pico (playstore), better download the apks separately and install it. for example the whasaap download from your website and install the apk, enabling unknown sources. :good:
[Samsung Galaxy Mini] peluki82:
Hi. I'm new to the forum, and first of all, I want to thank all the development work you do.

My Galaxy mini 2 is new, in the original box and never used. I had it saved as a spare. Now I'm thinking of using it as a GPS navigator (like a Garmin) for my outings, on foot and by bike, to the mountain using the app "oruxmaps" and connecting a heart rate band to smart bluetooth (v4.0). The band doesn't work on Bluetooth v3.0.

Before installing the rom, I have a question. If I install this rom, it is based on kit kat 4.4:

1. Will the GPS work properly?

2. Will Bluetooth work in version 4.0 to connect the band?

3. Can the external memory card be used?

Thank you very much in advance.
[Samsung Galaxy Mini] buaser:
No chance, you can't update hardware via software.
[Samsung Galaxy Mini] peluki82:
Ok, thanks. Being a version superior to Android 4.3 I thought that this could admit it as it did my previous Galaxy S3.

I would need bluetooth 4.0 or Ant+ to connect the sensors. The galaxy mini 2 supports OTG with this rom?? If yes, could I use an OTG adapter with a bluetooth 4.0 USB or an Ant+ USB??

Thank you.
[Samsung Galaxy Mini] Don Pedro!:
How long did it lie around there? Did the battery survive it? :confused:

Well,

GPS should work. I tested OSMAND and it basically works. However note that this phone is rather slow, so don't expect an ambitious waypoint rate. Depending on what you want to do this may or may not be a severe limitation or even a show stopper.

Bluetooth will not work here, this phone has no 4.0 transceiver. The phone is so old, BT 4.0 wasn't even specified at that time.

SD Card does work, yes. It even works better than with a stock ROM as the custom ROM is rooted. Stock, unrooted Kitkat has some severe limitation regarding access permission on the SD card (which is a real nag).

HTH
[Samsung Galaxy Mini] peluki82:
It has been around for 5 years. Today I turned it on for the first time, and the battery was over 50%, I think it's fine but I have to try it more.

You could tell me if in the SGM2, with this rom, the micro USB works like OTG ??
[Samsung Galaxy Mini] Don Pedro!:
Dunno, never tried it and I don't have a suitable cable at hand! But Shadow of Leave should know if he integrated that in the custom ROM he made. Otherwise just try it. You don't want to run a ginger bread phone these days, do you? So simply change to the custom ROM and see if it works, OTG cables are available on Amazon & Co. for little money and a stick or keyboard you'll probably find in your desk.
[Samsung Galaxy Mini] peluki82:
Thanks for the reply. Let's see if [MENTION=5965480]Shadow Of Leaf[/MENTION] can confirm if with your ROM installed the SGM2 supports OTG and an external Bluetooth 4.0 USB mini could be used.
[Samsung Galaxy Mini] Shadow Of Leaf:
I Think it work cuz i implement it on cm11 and omnirom

but it need testing
[Samsung Galaxy Mini] peluki82:
Thank you very much for the reply. In that case I will buy the OTG and Bluetooth USB adapter, install the rom and try if it works.

Which rom is more recommendable, Cm11 or Omnirom?? I see that the links for s6500d are not yet available in omnirom.

Regards.
[Samsung Galaxy Mini] Shadow Of Leaf:
Soon cuz i dont have a s6500d

so i need a tester

but it will be soon available
[Samsung Galaxy Mini] Don Pedro!:
A said, OTG is one thing, Bluetooth 4.0 is the other. Both have nothing in common.

Which ROM is "the better one" alsways depends on what you're expecting. Didn't test omnirom yet, it is also based on Android Kitkat 4.4.4, same as CM11, so there's probably little difference regarding functionality and I saw little motivation to switch form CM11 to Omnirom. Omnirom currently also seems to have a bug, see here: https://xdaforums.com/galaxy-mini/mini-2-dev/rom-omnirom-4-4-4-stable-mini-2-t3831882. Shadow of Leave promissed to fix it soon but posted no fix yet. It would be interesting to have a more recent Android version than 4.4.4 on the mini but this seems to be a more difficult task to do then you would naively assume. As the mini2 is such an old, weak-CPU phone I also think custom ROM development for that thingy mostly came to a halt. At least you shouldn't expect anything more recent than Kitkat 4.4.4.
[Samsung Galaxy Mini] S3rgi0:
When i try to install it says to me "This package is for device: jenad, GT-S6500D. this device is jena" but my device is GT-S6500D!! :S

And when try to install the 6500 version it says : "mount: failed to mount /dev/block/mmcblk023 at /data: Device..." but finish installation done, and when I restart the splash screen remains eternally...
[Samsung Galaxy Mini] KevMetal:
It's an updater script error ...just delete the assert lines ..

_using 7zip browse ( NOT EXTRACT ) rom zip ...

_browse to META-INF>com>google>

_open updater script with notepad

_delete all the lines from the top until BUT NOT INCLUDING "mount"

_save

_exit

_install

assert prop lines is to protect your device so you don't flash the wrong zip ..if you know the zip will work they are not necessary

*DO THIS AT YOUR OWN RISK*

*IF THE ZIP IS FOR ANOTHER PHONE WILL BOOTLO OP & BRICK
[Samsung Galaxy Mini] S3rgi0:
A lot of thanks!

But now only says : "mount: failed to mount /dev/block/mmcblk023 at /data: Device..." but finish installation done, and when I restart ...the system works!!

But...when i try to download a file with browser it says that I do not have SD card :(
[Samsung Galaxy Mini] KevMetal:
Jajaja you tell me ..:D...if system is running normally it's fine ..twrp can't mount data partition ...i think ..could be solved by formatting data ..i think ...but if the phone works fine ....it works fine ....
[Samsung Galaxy Mini] S3rgi0:
Thanks!

I tried to format /data and /sdcard0 but "failed to mount" again :eek:
[Samsung Galaxy Mini] KevMetal:
Then it's a prolem with your recovery..look for the one that was fixed by opp to mount internal and external data ..
[Samsung Galaxy Mini] S3rgi0:
I use CWM6.0.5.1 but in the first post appears to download twrp... twrp solve that issues?
[Samsung Galaxy Mini] KevMetal:
https://xdaforums.com/galaxy-mini/mini-2-dev/recovery-twrp-3-0-2-0-galaxy-mini-2-t3830997

Bro install that recovery ...in cwm choose install .img file and install ..

Man are you sure you have 6500d & not just 6500 ?

Anyway go to that post and use that recovery and format data in format section to ext4
[Samsung Galaxy Mini] S3rgi0:
yes, is 6500D...i tried the trwp, format data, repair file system, change to fat and then to ext4...and same results...problems with the data partition of my phone persist...finally i'm back to cwm and restore to CM 10.1 for 6500D backup and all work ok again :)
[Samsung Galaxy Mini] KevMetal:
Okay I'm not sure what the error is related to then but if rom was installing and working fine there is no need to remove it ...first try it at least a few days ..but anyway ..glad all is back to CM10.1 without problems.

Wait i understand your problem ...you installed a recovery for s6500 not s6500d

*now your phone thinks it's s6500 & everytime you try to install s6500d rom it is confused ..

Try to find a recovery that is only for s6500d .. install that ..then find an old rom only for s6500d and install that ..after try to install the s6500d version from OP following the exact instructions for s6500d version and see what happens

And try to change data to ext4 with your old recovery ..then flash new recovery then fix files & format data again ..then install ROM

You flashed the rom first i think then you tried to change the recovery and data and all of that and either way your first problem is the recovery of your phone thinks your phone is s6500 so your recovery is starting the problem ...

Hope you understand what i am trying to say .
[Samsung Galaxy Mini] S3rgi0:
I think my phone has a problem with partitions structure or similar, another problem with trwp(for 6500D) is that not detect my external micro sd card...i had to copy the new rom to internal memory of the phone (mounting from recovery) for install...

In any way thanks you for your help, you have tried ;) :good:
[Samsung Galaxy Mini] KevMetal:
Yes , could be. You could try to repartition but be careful. Good luck .
[Samsung Galaxy Mini] S3rgi0:
Today I tried to install stock Rom via Odin and start again from 0 with twrp for 6500D, but same error with f***ing data partition...and twrp remains without recognizing my sdcard...

In future days maybe try a repartition...

thanks!
[Samsung Galaxy Mini] KevMetal:
Yep definitely partition problems. I installed an Omnirom waay back on my Jena and had to repartition to get it on ...then after I forgot and had a similar problem until I remembered and had to backtrack to repartition back to original layout..
[Samsung Galaxy Mini] S3rgi0:
do you know a good tutorial for make the repartition? I never tried that and I want to stay safe before...
[Samsung Galaxy Mini] aficionadodesu:
Maybe you need to format it with ext4. It was necessary for me when going from cm10 to cm11. i think cm10 uses that partiution as internal sd formatted with vfat,and cm11 uses it as data partition formatted as ext4... :confused: