Quote:
Originally Posted by natemcnutty
Yeah, so the root is weird. What I mean by a real root is that on first boot, I log into Market, install Titanium Backup, and it tells me I don't have root. I then install Busybox and Titanium is happy, but other programs like ES File Explorer won't let me run as root. Terminal says unknown uid when I type busybox whoami, but it does let me su, then issue commands which works properly.
Haret users don't have to do anything like this, so that's why I'm wondering what we need to do to clean up the ROM. Also, I'm thinking we should toss spare parts into the ROM like Haret used to unless we want to change the value for the End key. Having no Home button is extremely annoying.
As for the install-seq.sh, that is almost the same code as what I had when I was trying to fix up FRX06. I used @ symbols, but I like yours better. For the 210 to 240, I think we should add a little more to that so we don't mess up build values or anything like that.
|
I tried ES explorer for root but its asking for a specific rom (cyano or some other crap). lol
The request for 'root' is a real hack in android. It doesnt work like you think. Most devs try to write to a section they arent allowed to to cause the superuser apk request to pop up and allow it. Thats it..lol. They dont have the power to go to the shell and execute, its all done internally. they dont select the user to run as. Haret runs wide open. They dont have ro set for any partitions. If you want to run the same way, just mount rw for everything in your initrd. Also reorder your path so where ever you have busybox installed is first.
installed angrybirds with no issues.. so i'll leave it up to you gents to figure it out. If i cant replicate, i cant fix
. I'll try a fresh install instead of my restored data to test further. Also for spare parts and all that stuff, make an update.tgz and lets put it up. Simple enough to do so. I dont want to included it in the rom itself since.
I was thinking more about this direct conversion from the img and realized that the fixperms script will never run since its not there. Not sure if this is gonna work out well in the long run. God knows what they will change forcing us to update the script.. At this stage its easy enough to update the recovery we do have a work around.