[Samsung Galaxy Mini] Don Pedro!:
Rooting - a user report

Well, if you know how to do it a lot of things get easy!

OK, I tried to root just a couple on minutes ago. I have Odin3 v3.12.5 on my PC, I know this works. I flashed CWM-6.0.5.1-v3-jena.tar.md5, this went well but I still can get into recovery only via "adb reboot recovery" or the menu entry from the developer settings in CM10.1 (not even if I quickly release all buttons as soon as the Samsung screen appears as was suggested here).

Then the rooting itself. The way I understood it I somehow must place at least a su binary on the phone plus an apk to make it usable from the GUI. If I query xda for "root gt6500" I will sooner or later find a couple of different tools or zip packages that claim to root the gt6500. Among them:

Poot (I know, this is a bloody apk that can't flashed but must be installed. It doesn't work on my phone though, forget it)

CWM-RootMe-Odin3-USB_Driver.rar

Root Galmin2.zip

root-g2x-su-2.3.6.3.zip

Superuser-3.2-RC3-arm-signed.zip

UPDATE-SuperSU-v2.37.zip

and if you search further probably a couple of stuff more. So which one to choose? :confused: Jugde on age, something posted 2013 is more trustworthy than something from 2010? How do I make sure none of them contains any malware? And of course I want to use the latest sources for su, instead of some ancient version from 2003. So which one is the most up to date?

Of course I looked in all of them to see what's inside. In CWM-RootMe-Odin3-USB_Driver.rar there's a zip "RootMe.zip". If I look inside this I can see besides su also busybox and the usual zergRush. So, busybox on the phone does sound good, let's give this one a try. I followed the instruction from the download location: Unpack Zip to folder, start the recovery on the phone and then run "runme.bat" on the PC. The bat does nothing more than trying to adb push three files on the phone and to adb shell some commands to set permissions, set a link, etc. Guess the outcome if I run it?

--- pushing busybox
failed to copy 'files\busybox' to '/data/local/tmp/.': Is a directory
--- correcting permissions
chmod: /data/local/tmp/busybox: No such file or directory
--- remounting /system
/sbin/sh: /data/local/tmp/busybox: not found
--- copying busybox to /system/xbin/
dd: can't open '/data/local/tmp/busybox': No such file or directory
--- correcting ownership
chown: /system/xbin/busybox: No such file or directory
--- correcting permissions
chmod: /system/xbin/busybox: No such file or directory
--- installing busybox
/sbin/sh: /system/xbin/busybox: not found
rm: can't remove '/data/local/tmp/busybox': No such file or directory
--- pushing SU binary
2428 KB/s (22228 bytes in 0.008s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
rm: can't remove '/system/xbin/su': No such file or directory
ln: /system/xbin/su: No such file or directory
--- pushing Superuser app
failed to copy 'files\Superuser.apk' to '/system/app/.': Is a directory
ALL DONE!!!
Drücken Sie eine beliebige Taste . . .

Oh, but then I see that there is an option "Mounts and storage" in CWM and here I realize system and data are not yet mounted, no wonder I got errors from the bat. So mount them and retry:

--- pushing busybox
4375 KB/s (1075144 bytes in 0.239s)
--- correcting permissions
--- remounting /system
--- copying busybox to /system/xbin/
2099+1 records in
2099+1 records out
1075144 bytes (1.0MB) copied, 0.127602 seconds, 8.0MB/s
--- correcting ownership
--- correcting permissions
--- installing busybox
--- pushing SU binary
1778 KB/s (22228 bytes in 0.012s)
--- correcting ownership
--- correcting permissions
--- correcting symlinks
--- pushing Superuser app
4442 KB/s (785801 bytes in 0.172s)
ALL DONE!!!
Drücken Sie eine beliebige Taste . . .

OK, that's different! Am I root now? I must reboot to check!

Yes, there's at least a superuser app, start it. Wow, Version 3.0.5 from end of 2011, 5+ years old... :rolleyes:

Probably will try to download a more recent version of some su apk, but for the time being this may suffice.

Now let's try to get back to twrp and update to cw11.0. I did exactly the following as posted:

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

I did all this in exactly the given order. Now waiting the 10 minutes boot time for cyanogen mod, hopefully with another result than in my previous tests...

Unfortunately this is *not* the case, my phone still doesn't boot CM11.0 during a grace period of 15 minutes, thus again switching back to CM10.1... :mad:

Any idea anyone? Does not installing Gapps influence the boot process of CM11.0? Gapps should be optional and I intend not to use them. Or does an inserted sdcard influence bootability? I currently have a 32G card plugged.