yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] Don Pedro!:
Sorry, but I have to confirm what xEmre66 posted, S6500 doesn't boot with the latest "cm-11-20170203-UNOFFICIAL-jena" and "TWRP-v2.8.5.0-jena only"! I did *exactly* what you wrote above (except I did not install GApps cause I intent to go without them but this should be optional anyway), it installs everything and claims it was sucessful. but in the end when I try to boot the system it boots till the animation logo with "cyanogenmod" and the rotating arrow appears. This animation goes on forever, I did a try, plugged the phone to AC and kept it running the whole night - nothing! I also repeated the complete install procedure a second time, with the very same result. :(

Interesting things to note:

When hung in the animation the phone still can be seen when connected form a PC, a "adb reboot recovery" will be executed.

In TWRP prior to rebooting it gives a hint the phone wasn't rooted yet and offers to do so. If I choose to root it for the glimpse of a second I can see a red message flashing up before the phone switches off (instead of rebooting). If I reenter TWRP and select reboot it again claims the phone wasn't rooted, so obviously rooting doesn't work here. In fact before trying this CM11 I tried to root the phone with two dozens different instructions of how to do it for the S6500 - and *none* off them worked, dunno why.

My phone doesn't allow me to enter the recovery via the vulcan nerve pinch Volup, Home and Power, no matter what I do. The only way to enter recovery is via "adb reboot recovery". This is true for the original firmware, for the TWRP here and I also had this problem with an earlier CWM version.

In TWRP I have the problem that every now and then the phone suddenly and unexpectedly switches off. It can happen even during flashing a FW! I do not have this problem with the stock FW and also the boot animation runs endlessly, so I don't suppose my phone has a HW problem.

Maybe this could help analysing what's wrong here. So this is all rather strange and I have no idea why things are obviously different with other people's S6500, maybe they differ in hardware revision? Whatever is the case, as this CM11 is currently unbootable I simply cannot test it and I will test bleached CW10.1 now. I would've preferred CM11 of course but CW10.1 is still better that Gingerbread stock FW and if Shadow of Leaf will be able to fix the boot issue I will happily give it a second try...

[Edit]

Bleached CW10.1:

Did a test and kept TWRP (instead of using the CWM version that ist linked with Bleached) but flashed cm10.1. And this in fact works and it boots into a usable Android. So the problem seems to be with Shadow Of Leaf's cm11, not with TWRP.

[/Edit]

THX

Don
[Samsung Galaxy Mini] lorn10:
Okay, I don't know if this is relevant but my phone was rooted AND unlocked. So my steps were as follow:

00) unlock the phone under (a compliant) stock Rom 2.3.6 like build XXLK2

--> https://xdaforums.com/showthread.php?t=1958859&page=11

01) root the phone by flashing CWM v6.0.3.3-b2.tar.md5 with ODIN

02) disable verification check in CWM v6.0.3.3-b2 and install (upgrade to) CWM-6.0.5.1-v3-jena.zip (as zip file from SD card)

Note, unfortunately the CWM-6.0.5.1-v3-jena.tar.md5 cannot be flashed directly. ODIN reports a MD5 error, someone must first rebuild the package correctly with new name CWM-6.0.5.1-v3-jena.tar.md5. You can try it to flash directly but I think this issue is still present.

1) install TWRP (from CWM or stock recovery) and reboot into it

2) go to Wipe, Advanced Wipe and then wipe both two Cache & System

3) in Advanced Wipe choose Data and select Repair or Change File System

4) go to Change File System and choose EXT4, format it

5) install the Rom --> Note, when finished the phone will automatically restart, be prepared to catch the right moment!

6) boot back into TWRP recovery and install GApps

[MENTION=5965480]Shadow Of Leaf[/MENTION], your work is great enough! :o:good: I do not need NFC, so this isn't so important. It was just an input of me because there are some unclear information regarding the NFC controller in our mini 2. It's really possible that our NXP 44501 has such a old firmware that this will prevent any correct functionality under a more recent Android Kernel. Maybe someone other finds a way to upgrade to a compatible NXP 44501 controller firmware. ;)

---------- Post added at 12:35 PM ---------- Previous post was at 12:08 PM ----------

You have to release the buttons very fast when the Samsung Logo appears! So don't push them too long! ;)
[Samsung Galaxy Mini] xEmre66:
It still doesn't boot. And the new TWRP doesn't detect internal storage. I hope somebody can help me. I'm on stock ROM back again and I want CM11 because it's very fast.

Regards,

xEmre66
[Samsung Galaxy Mini] Shadow Of Leaf:
twrp cant detect your internal storage because you didn't change the data partition to ext4 and format it
[Samsung Galaxy Mini] lorn10:
Well, I tried it again and it worked. I can only repeat my install method again, - sorry. My Test phone has Baseband-Version S6500XXMD1.

0) root (& unlock) the phone (if someone can rebuild the package CWM-6.0.5.1-v3-jena.tar.md5 then this will helps a lot;))

1) install TWRP (from CWM) and reboot into it

2) go to Wipe, Advanced Wipe and then wipe both two Cache & System

3) in Advanced Wipe choose Data and select Repair or Change File System

4) go to Change File System and choose EXT4, format it

5) install the Rom --> Note, when finished the phone will automatically restart, be prepared to catch the right moment!

6) boot back into TWRP recovery and install GApps
[Samsung Galaxy Mini] xEmre66:
The old TWRP did detect both internal and external. I already formatted it to EXT4 (data partition) and if I want to flash it, it resprings to "teamwin" splashscreen. Shadow Of Leaf, can you help pls? (@lorn10 I have the same MD1 baseband, but it doesn't install CM11)
[Samsung Galaxy Mini] Don Pedro!:
OK, I will give this a try. I managed to download this ancient XXLK2 stock from the net. However I'm pretty sure my phone is not locked, I bought it at Amazon and without any mobile contract, I can use any SIM I want. But I may have to use use this old stock in order to be able to root, thanks to unfixed security holes?!?

And I guess I should be able to flash CWM-6.0.5.1 directly by renaming the file extension from tar.md5 to just tar. AFAIK this makes Odin skip any checksum validation. Will try that.

OK, I will test that as well. I would be happy to switch to CM11. I will report if this was successful, but pls. give me a couple of days, as usual I'm quite busy...

THX

Don
[Samsung Galaxy Mini] mihael zzzzz:
Good work Shadow Of Leaf this cm very fast and stable,excellent flying on art.
[Samsung Galaxy Mini] lorn10:
If you phone is not locked then you DON'T have to do this! ;):)

My S6500XXMH1 regular phone was locked so I want to unlock it. My S6500XXMD1 test phone was not locked so I just rooted it, - and the latest CM11 build works even so perfectly! :o

The phone will be rooted when you flash the CWM-6.0.3.3-b2.tar.md5 or CWM-6.0.5.1-v3-jena.tar.md5 with ODIN.
[Samsung Galaxy Mini] mihael zzzzz:
:DShadow Of Leaf you managed to kill two problems at once you update the driver fix white screen. Half day walk and push the power button or not never caught a white screen.
[Samsung Galaxy Mini] xEmre66:
Can somebody help me pls to get CM11 on my S6500? Does anyone have a TWRP which doesn't detect internal and resprings to splashscreen if you want to flash a ROM?
[Samsung Galaxy Mini] lorn10:
[MENTION=7429196]xEmre66[/MENTION], this may sounds crazy but I suggest you to go back to old stock rom and stock recovery. When you are on original condition / environment, then you can try to go through all my steps and see if this will work. Otherwise I have no idea...
[Samsung Galaxy Mini] xEmre66:
Guys I was on stock and flashed CWM 6.0.5.1 and then TWRP but now this is only what it shows on the screen:
[Samsung Galaxy Mini] lorn10:
I am really irritated, consternated and affected. :( I have meanwhile installed several times the latest CM11 build (I am experimenting with the NFC enabler) and had until now ZERO issue! Your problem is totally strange, especially in the regard that we have the same baseband type of the phone. :(
[Samsung Galaxy Mini] xEmre66:
You don't have to worry about that. I was very angry and I have smashed the phone a little bit but it still does work. Haha. After smashing it, it now booted up into recovery and I flashed it and all works fine now. But the prob is: Why does it say 23201 in Network name instead of "Three" (my network provider name)? The ROM is very very nice and I thank [MENTION=5965480]Shadow Of Leaf[/MENTION] a lot and you (@lorn10) as well. Thanks for all guys. And I have some good news regarding CM12 for our phone: I started porting our kernel to support CAF display HAL so (maybe) it will boot up to CM12 but don't expect the first build will be bugless. But I will work a lot to fix all the bugs etc. :)
[Samsung Galaxy Mini] lorn10:
[MENTION=7429196]xEmre66[/MENTION], great to hear that you have figure it out!

Yes, I can confirm that this most recent CM 11 build is definite a great one! :good: We have now for the mini 2 a new preferred rom with really good performance. :D In this regard it outperforms the CM 10.1 Improved 07/07 build from bleached. ;) And as mentioned, - I think that with "16-bit transparency" enabled it runs even somewhat smoother. I read about that hint on the mini 1 xda thread. It seems that this option is for low end devices recommended. Only the installation process of the rom could be somewhat easier, - at least for some of us... ;):p

According to your CM 12 plans I whish you all the best. Well, according to some statements from the LG L5 & L7 xda section this will be a hard task. They write that the Adreno 200 GPU drivers where already broken / no longer supported in KitKat and had first be patched to work. This may be the reason why I get worser results in AnTuTu v5.7.3 under CM 11 then with CM 10.1. (However, that could be also related to the less amount of RAM which is avaiable under KitKat.)

4013 / 4036 / 4549 comparing to 5538 / 5784 / 5826

These results are totally contrary to the overall working performance which is absolutely better, smoother, less laggy then with CM 10.1.

Yes, I can confirm no white screen occurs during normal operation. The "empty screen" is unfortunately present when a powered-off phone will be connected to the charger (and will load over night). The phone has then mostly an "empty screen" . In such a situation I perform then a "blind restart", - after restart it works again normally.
[Samsung Galaxy Mini] Don Pedro!:
Hopefully I will find the time to retest this next weekend. I'm BTW curious to find out if I could download somewhere on the net the rooting tool mentioned in this security advice. Unfortunately I cannot post links yet, so I must include this somewhat hidden, I needed to strip off the "http:" to be able to post it:

//source.android.com/security/advisory/2016-03-18.html

With this exploit I would expect the tool to be able to root almost all android phones...
[Samsung Galaxy Mini] lorn10:
Rooting the mini 2 is really NOT complicated! You just have to get the Odin tool and the right CWM. Here you can find several Odin builds: http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/

It is noted there that version Odin 3.10.x is recommended for KitKat. I think I have used Odin 3.10.6, - but most other will also work. ;)
[Samsung Galaxy Mini] wverkist2:
Internal Storage - S6500D

[MENTION=5965480]Shadow Of Leaf[/MENTION], greetings!

I installed this on a S6500D. I must have done something wrong, because internal storage is not recognized. My “total space” reads 0.90GB

Going over your instructions, I realize that I did not do “format system”.

I suppose that is “format /system” under “mounts and storage” in CWM? Could that be the cause for my issue?

Funny: the phone being old, I thought that this thread was old, too. Good for me it is alive :)

Regards! Have a nice weekend!
[Samsung Galaxy Mini] lorn10:
[MENTION=5415544]wverkist2[/MENTION], it is very important that you follow EXACTLY all the steps described by Shadow Of Leaf.

I repeat it again somewhat more detailed:

Install method for S6500D:

0) root your phone with CWM-6.0.5.1-v3 (if locked, it's recommended to unlock the phone first with a compliant stock rom)

1) boot into CWM and wipe both data & cache

2) go into menu mounts and storage and select format /system

3) go back to main menu and select install zip, install (from the SD card) the jenad rom, GApps, and the Boot Fix

If you have any problems then repeat steps 1, 2, and 3.

Because most of the people here have the normal (non-D) version of the mini 2 it's not possible to test this in all detail. Well, it is confirmed to work also at the S6500D version. :)
[Samsung Galaxy Mini] wverkist2:
Internal Storage - S6500D / my workaround

[MENTION=7045712]lorn10[/MENTION]
[MENTION=5965480]Shadow Of Leaf[/MENTION]

Short: I installed the Rom for the S6500 on my S6500D, now my total space is 1.81 GB.

Long: I followed lorn10’s instructions for the S6500D meticulously, but no joy.

Repeated once, same. Camera crashed.

I then installed TWRP and followed the OP’s instructions for the S6500, up until “choose EXT4” and then installed CWM 6.0.5.1 again, and then the S6500D rom, gapps and the fix.

Still same issue and TWRP rebooted once in a while. Just telling this in case it matters, I myself have no idea.

What finally worked for my S6500D was this:

- install CWM 6.0.5.1

- boot into CWM and

-- wipe data & cache

-- format /system

-- install zip (cm-11-20170203-UNOFFICIAL-jena.zip, which is the S6500 version)

-- install gapps (I used today’s Pico version for CM11, to be found at opengapps.org)

As said, I have 1.81 GB of storage now. I tested Camera, Bluetooth, WiFi, tethering, Phone, installed Whatsapp and Automate via Play. No issues. No NFC, of course ;)

So I am now following Shadow of Leaf’s last instruction: - enjoy

THX

Kind regards!
[Samsung Galaxy Mini] lorn10:
Thanks [MENTION=5415544]wverkist2[/MENTION] for feedback. :)

So you have installed it according to Shadow Of Leaf's recommendation. You just replaced the jenad rom with the jena one and it worked, - amazing! :eek: It seems that there must exist a bug in the jenad build. If that's true then this should be mentioned at the main thread page...

Well, - if the S6500 rom is working stable and good at the S6500D then NO separate jenad rom is needed. The only thing which is somewhat misleading are the (inactive) NFC settings in the system settings. Well, this is only a trivial issue and can be absolutely ignored. It doesn't affect the operation.
[Samsung Galaxy Mini] lorn10:
[MENTION=8083052]Don Pedro![/MENTION], it seems that you make it yourself somewhat complicated. ;)

Look here at this XDA thread, - it is everything described: https://xdaforums.com/showthread.php?t=1953420

So you really just need a more recent CWM like version CWM-6.0.5.1-v3-jena.tar.md5 and a compliant Odin build. NOTHING ELSE!

Keep in mind that the CWM files and Odin has changed in name and in the functionality. For example, the former PDA tab in Odin was renamed in later releases to AP tab. Regarding our mini 2 I recommend you to use no higher version then Odin 3.10.7. And regarding the phone drivers, you have to install Samsung Kies or the USB Samsung drivers (http://developer.samsung.com/search/searchList.do?searchTop=usb+driver). Then everything is fine.

As mentioned the CWM-6.0.5.1-v3-jena.tar.md5 package has a MD5 issue because it's name was changed. Yo you can flash it in Odin as tar file CWM-6.0.5.1-v3-jena.tar. Or you can flash CWM-6.0.3.3-b2.tar.md5, disable verification check inside the CWM and upgrade to CWM 6.0.5.1 v3. For any later Cyanogenmod 11 build, CWM-6.0.5.1 v3 is necessary.

Finally, there exist the chance that you have misconfigured something fundamentally at your phone. :( I hope not....
[Samsung Galaxy Mini] wverkist2:
[MENTION=8083052]Don Pedro![/MENTION]

Maybe the only useful advice I can give you:

I too had problems booting into recovery. Then I found this tip:

Press and hold "Home"+"Volume Up"+“Volume Down”+"Power" buttons until you see the Samsung logo, and then immediately release the power button while holding the other buttons.

Less sure about the following, maybe you should investigate a little yourself: I think that after installing TWRP, you should not let it do a normal reboot (some suggest even unplugging the battery), but you should boot once more into recovery.

And I read also a suggestion to not let TWRP root your phone and instead flash SuperSU yourself.

Which leads me to my last remark: why would you want to root at that point, as CM11 comes pre-rooted?

Greetings!
[Samsung Galaxy Mini] lorn10:
[MENTION=5415544]wverkist2[/MENTION]

[MENTION=8083052]Don Pedro![/MENTION]

I think the best is when we let it be as simple as possible. ;) I can only repeat again that for rooting only two things are needed, the corresponding CWM and Odin. This is the way which I conducted MANY times 100% successfully. There may exist other root & install methods, - however because these are unknown to me I cannot help. Maybe someone other can. ;)
[Samsung Galaxy Mini] Don Pedro!:
Basically that's more or less what I did, flash CWM 6.0.5.1-v3 via Odin, boot into recovery and use the runme.bat to root. But please note that beside CWM you need a tool to root! Sometimes somebody has packed them all into one zip, but not necessarily. And there are in fact a lot of tools out there that claim they could root. I'm a big friend of clean systems, be it my PC, be it my phone. No unused, unneccessary software, no stuff of unknown origin. So I simply want to know what software runs on it and where it comes from.

Yes, I already know that.

I used Odin V3.12.5 and this worked without a problem. It instantly found the phone, flashed CWM correctly, no prob. USB drivers are installed, phone is also accessible via ADB.

Yes, I also do know that. I used CWM-6.0.5.1-v3-jena.tar.md5, unpacked it and packed recovery.img again into a tar. This went well.

Hm, the phone came from plain stock FW, no modifications. And as mentioned, I indeed could root it the way you described. The problem is that CM11.0 won't boot. I will do a new test and try to install Gapps together with CM11.0, maybe this changes something, I will report.

THX for your effort to help!

Don

---------- Post added at 09:49 PM ---------- Previous post was at 09:37 PM ----------

I will give this another try (though I also experimented with pressing all buttons in the past). There seem to be a lot of other people that report problems entering recovery, so I'm not alone.

As mentioned earlier, TWRP doesn't manage to root my phone. I had to do it via installing another SU.

Very good point! I already wondered about that myself. Basically I did it because it was recommended here. I had the faint hope it would change something to make CM11 boot on my phone! This did not prove to be true, but I wasn't astonished about that. As the install instructions for CM11 include reformating /data (where su is being dumped by its installer) it just gets wiped again, so rooting should make no difference here. It was just to make sure I didn't miss anything.

BR

Don
[Samsung Galaxy Mini] Don Pedro!:
So here's the (negative) result of my attempts:

I tried to install CM11.0 including Gapps, this did not change anything, phone gets stuck in the boot process with endless CM animation logo turning.

I also tried to boot the phone with the sdcard removed plus gapps installed. Still the same as above, phone gets stuck in the animation, too.

So now I've finally ran out of ideas what else to try! Anyone some other, more elaborate suggestion? Is there a way to switch off the animation and instead get a TTY output to see the kernel log messages during boot?? This might give a hint of what's happening and where the boot process hangs, won't it? As the phone may be accessed via ADB in this state I guess it didn't completely crash but gets stuck in an endless loop waiting for something to happen (that actually never does).

I will - again - flash back the phone to bleached CM10.1, it's 100 times better than bloody stock FW anyway. If someone comes up with another idea to try, Shadow of Leaf does an update to CM11 one day or the ambitious guy that claimed he started porting to CM12 succeeds, I may happily retry if this works. But until then...

THX

Don
[Samsung Galaxy Mini] xEmre66:
Hahah so funny :D If you have the S6500D, you have to flash the Boot fix in the Download Section. Otherwise it'll not boot. Or if you have the S6500 you must change /data partition filesystem to ext4 (with TWRP).

And yes, I'm working on CM12 and once I get it booting I will update my thread.

Regards,

xEmre66
[Samsung Galaxy Mini] Don Pedro!:
I'm well able to read and normally do so, too! I have the Non-D Version with NFC, so no bootfix required. And I have reformatted the data partition with ext4 as explained by Shadow of Leaf and some others. My model is GT-S6500. So I don't know what's so funny about it, I spent a lot of time in trying to get CW11 up'n'runin' but didn't succeed for unclear reasons. :eek:

OK, let's see how it will proceed. If you can offer something promissing some day in the future I will kindly test it.

BR

Don
[Samsung Galaxy Mini] lorn10:
Sorry, that's definitely NOT the case. At least for the mini 2, the phone will be rooted when you flash CWM. Absolutely no additionally tooling like that "runme.bat" is necessary. I read longer time ago, that the mini 2 is in this regard already somewhat "more open" then previous Samsung phone models. However, this may be true only for the Central European mini 2 variants. This could be different in other regions (of the world)...

The fact that you have big problems to enter CWM (after installing it with Odin) is highly strange. Out of my view there must be something wrong. I repeat again my recommendation, got back to ORIGINAL stock rom and stock recovery and try it again with Odin 3.10.7, CWM-6.0.3.3-b2.tar.md5 and CWM-6.0.5.1-v3-jena.tar.md5. May be this will help. ;)
[Android Apps and Games] mrad4tech:
[IMG="Icon"]https://lh3.googleusercontent.com/oCMBohxlgv03IXdXiTyjdDqqNzVjsOAMQZAOsGQa2Z-SW5esM-XJ7-MP_bNwUnXLRDQs=w300-rw[/IMG]

Download HERE

★★ROOT Required★★

Make it easier with Build.prop editor extended with a Material Design for better look and interface !

★<b>Features</b>★

<i>

★View and Edit any Property !

★Add new Property !

★Search for Properties !

★Ability to Backup and Restore Original Build.Prop !

★Change between 2 Themes : Dark Theme and Fresh Theme

★Material,Fresh and Realible Design !

★Simple and Easy ,can be used by anyone !

★Colorful !

</i>

Build.prop properties can control how your system runs. You can change your LCD density, decrease your call ring delay, save battery by increasing your wifi scan interval,rotate lock screen and more.

★Please Remember to keep a backup of your current build.prop. Changing build properties can potentially harm or soft brick your device.

★The developer is not responsible for any problem caused by editing the build.prop file★

★Root and busybox are required for this app to work correctly

[IMG="a"]https://lh3.googleusercontent.com/yspnJRj_-lA5Uwe9bBfWc9b8wUimbI5c7trL7Sz-qOsWjCB9TEpvp6HL6rkAWfE_yA=h310-rw[/IMG[IMG="q"]https://lh3.googleusercontent.com/vAVs0eHxf7cj1dbDDzhVJ4pNz09fRXhYUhCBYPWtfKgY_zXvQPB5bmYUmjSKszfE2oo=h310-rw[/IMG]
[Android Apps and Games] Magnum_Enforcer:
Care to post a link?
[Android Apps and Games] mrad4tech:
Link here

https://play.google.com/store/apps/details?id=com.mrad4tech.build
[Teclast X98 Air 3G] Stony2:
Coming from sikke1 ROM changed to mirek190 ROM I noticed that facebook app @ M5C5 Air III will not start. App can be installed but closes by itself after start. Same with FB Messenger. I installed the v7 ROm for Air II. Tested with the original Air II kernel as well as the modified kernal. Sombody here with the same error?

Regards Stony2.
[Teclast X98 Air 3G] Miketudor:
I've the same issue. Seems to be after the latest fb update. Instagram is also not working.