[Android Software/Hacking General [Developers Only]] MrCabana:
[MENTION=3868181]x1123[/MENTION]

Thank you very much.

I confess I am not any good with linux command lines, sintaxes and all that. I never tried ln -P.

I can understand why manufacturers try to protect their products against problems. Turning a phone into an unbreakable air-plane like black box is a dream for them. On the other end, I'm with the customers, who pay for these same products and I think they have the right to use and have access to the devices their purchased in their completion.

Great, this is the goal I'm trying to achieve now with my phone. Making ro.secure=0 didn't change a thing though in my case. Perhaps I screwed it up with the so many methods I have tried. We will see.

Thanks for the very useful information about TWRP, CWM and CWR. My head is much less confused now.

Yes, indeed. I had never came across such a thing before. I found this one plugin for AK, called UPDATE V2, that is intended to automate the editing of default.prop file. I had a problem with that plugin script, because I wanted to add more things to the final boot.img file (ie. my own edited script to be run at boot time). I ended up editing this plugin script to wait for me to hit a key before it started repacking all the folders. Just a little trick and I may share it if anyone is interested. Though, I guess I would have to ask the owner of the script first.

As for the ROM building part, I am not interested for now in building my own ROM. I am satisfied with the stock one. All I will be trying to do after rooting is done is replace stock launcher with GO Launcher which I think is much better. I don't want to keep both because I think that would cost more battery.

Absolutely no doubt. I am willing to share my discoveries and make a propper script to make it work on other users with H2000+/H5000 as soon as I figure out what's causing the permanent read-only. I have been thinking of writing my own guide, with your help, of course, in both english and portuguese in a very near future.

Well, if so, if indeed you can't really tell what kernel I have, it doesn't really make a big difference huh? It's like a painting that might be worth millions or zero, depending if it's original or not, when in fact there's only one person in the whole planet who can tell which. If it's 2.3 pretended to be 4.0.4, but nobody can really tell, meaning performance is the same, funciontalities are the same, etc. Then I wouldn't mind having 2.3.

Thank you very much for that information. I was really concerned about that. I though it had to do with permissions to execute root tasks and all.

Sorry, I have no idea what IMEI number is for. Thank God I didn's screw it up on my phone with so many tries.

Besides removing all that chinese apps that runs in the back ground and eats up some memory. They're impossible to be removed if you aren't rooted.

First things first. This asssumption of mine proved to be correct when I mounted mmcblk0p3 using debugfs. It gave me rw so I could put files into /system/bin and /system/xbin and /system/app that survived reboots.

I wasn't saying several mountings of my own. I said that perhaps the phone is configured to have several sources to be mounted on top of /system folder. I don't know if that is possible or if that is happening. It was just a thought. If so, what I see mounted on /system can come from several different sources and the phone could get confused at where to save the files I put there manually.

Anyway, when I accomplited mounting using debugfs this part proved to be wrong. Once mounted, the phone saved files correctly.

I didn't try the add remount -rw just yet. But I've made some noob discoveries about the mount command I am willing to discuss below.

Thank you very much.

Now, I ask permission once again to share my noob thoughts:

1) I realized there's a symlink at /system/bin that says mount -> toolbox. Apparently, when you call mount from either adb or Terminal apk's, that's the bit of code to come up. The one in toolbox.

Ok, I don't remember if either I installed toolbox myself or if it came from stock ROM. Thing is, I tried to delete that link and direct it to busybox instead. Unfortunately, things didn't change. Apparently it's the same if I run mount from toolbox or from busybox.

But something curious came to my mind though. When I was editing boot.img, I made some changes to /init.rc and I saw a lot of mount calls in that file. These calls were made even before the /system folder is created. I wonder, where does the phone get that mount command from which is executed during the run of init.rc ? Does anyone have an answer for this?

Now, the default for mount is to be a symlink to a pack of functions called toolbox that resides in /system/bin. Changing mount from toolbox to busybox doesn't change anything. What if it's a permission problem for toolbox? It differs from busybox as bellow:

I know Superuser.apk wants su to have permissions like "-rwsr-sr-x root root". Could that be the issue? Can I safely change permissions for busybox?

2) As I probably described in my previous posts, I can acctually get rw permissions for a fraction of a second everytime the phone reboots. I can remount /system rw, I can put files in there, these files can be seen by running applictions and everything looks fine until next time I reboot the phone. After that reboot, these files will either be set to 0 bytes (emptied) or deleted. That's a very odd behavior. Let me try to be more clear and say the same thing in another format:

Thanks again for your attention.

---------- Post added at 05:14 AM ---------- Previous post was at 05:05 AM ----------

And that's what I did in my phone. I put su and busybox in /system/bin and a symlink to them in /system/xbin.

The reason I did that is that Superuser.apk expects su to be in /system/bin and with the chmod 06755. Otherwise it will list the su binary as red.

Also, both have to be root.root. Not root.shell as I thought previously.