• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root change partition layout without rooting?

I did a compile mid week but not had chance to play until just now (cat poorly).

I removed everything I thought from the compile with and without SU but it still will not boot. I assume there is something in the boot.img compiled that relies on the binary for SU to boot.

Unfortunately I don't know where to go from here. It may be worth manually playing with some roms yourself, see what the iron thingy detects or not.

Sorry dude.
 
SUroot said:
I did a compile mid week but not had chance to play until just now (cat poorly).

I removed everything I thought from the compile with and without SU but it still will not boot. I assume there is something in the boot.img compiled that relies on the binary for SU to boot.

Unfortunately I don't know where to go from here. It may be worth manually playing with some roms yourself, see what the iron thingy detects or not.

Sorry dude.
Click to expand...

well just a thought, i would imagine that it would have to have it there as its part of the linux build.
it doesnt mean that superuser needs to be enabled.
as an example if you download the su zip from revolutionary and only compiled with those files removed then that may work (although you may have already done that)
 
Rastaman-FB said:
well just a thought, i would imagine that it would have to have it there as its part of the linux build.
it doesnt mean that superuser needs to be enabled.
as an example if you download the su zip from revolutionary and only compiled with those files removed then that may work (although you may have already done that)
Click to expand...

I hadn't actually. I was over complicating things

Its just 2 files. /system/app/superuser.apk and /system/bin/su

Edit, if I manually remove them from dGB rom.zip, it also doesnt boot. Maybe another rom would fare better.
 
If I install the normal dGB ROM (with root) and then boot into recovery, mount "/system", can I delete/rename /system/app/superuser.apk and /system/bin/su to something else via adb shell, or do you think that will also stop the phone from booting?

actually, perhaps I should do as here.
http://forum.xda-developers.com/showpost.php?p=17413805&postcount=3
Any thoughts, on whether this would work, on a non standard ROM, rather than a rooted standard ROM, which is what I think it was done on?

Daniel
 
Well both methods do essentially what I have done in the repository.

I'll try it on my version right now and see what happens....

EDIT> deleted with root explorer. Superuser.apk and /bin/su (exactly what I took out of the build. rebooted and it works :confused:

Ah well, yes do that
 
SUroot said:
Well both methods do essentially what I have done in the repository.

I'll try it on my version right now and see what happens....

EDIT> deleted with root explorer. Superuser.apk and /bin/su (exactly what I took out of the build. rebooted and it works :confused:

Ah well, yes do that
Click to expand...
lol odd :/
 
Actually I compiled yesterday then removed SU and superuser and ity didnt boot. Just flashed now and it did. Mustnt have left it long enough.
 
SUroot said:
Actually I compiled yesterday then removed SU and superuser and ity didnt boot. Just flashed now and it did. Mustnt have left it long enough.
Click to expand...

hmm this is good news
the 1st unrooted rom that gives the space a desire needs while being secure enough to use in a corp environment

good shit
 
This is excellent news. Sounds like I should try this out now.

It seems easier to download the normal ROM and then delete the two files manually, don't you think?

The only thing is the issue with the cache partition size you mentioned.

Its worth noting that unrooted OS will not be able to symlink /cache/downloads to /data/local/downloads.
Click to expand...


Perhaps increasing cache to 10 or 15 MB would be a good idea to make sure that most downloads are still possible from the market.
Can you point me towards some reading material for learning how to create custom hboots.

thanks a lot especially to you SUroot, we seem to have come a long way since your rather pesimistic first post. :D

Daniel
 
AlphaRev have a selection of hboots of varying sizes, but if you want a specific cache size and are comfortable doing this you could try custom MTD process (files etc in the toolbox on here).
Or give thalamus' custom hboot tool a go find it here
 
I will be trying this Friday I think.
I will use the MTD process.
I think the instructions are clear enough.

Just wanted some advice regarding partition sizes, in particular to guarantee that there are no problems with larger Market downloads.
This is of course because without root, cache cannot symlink to data

I was thinking
/system 65
/cache 15
/data 3??

So the mtdpartmap.txt would contain "mtd 65 15"
What do people with experience using this technique think of that?

thanks

daniel
 
Yep, agree. Its fine.

I'm only using the hboot because I made them and had to test before release. I just dont see the point going back buit certainly nothing wrong with MTD's.

Safer technically too.
 
flashed ROM with MTD. worked well.
Deleted system/app/Superuser.apk and system/bin/su

but
superuser is still there in installed apps.
I am nt sure if it will work, or if this is just a graphic frontend for the su binary, but regardless I think it should go.
If Mobileiron is searching for things starting with Su or Superuser, then it will find this, and that would be silly, especially if it was a nonfunctional frontend.

Any tips on how to get rid of it.

thanks

Daniel
 
joregelt said:
flashed ROM with MTD. worked well.
Deleted system/app/Superuser.apk and system/bin/su

but
superuser is still there in installed apps.
I am nt sure if it will work, or if this is just a graphic frontend for the su binary, but regardless I think it should go.
If Mobileiron is searching for things starting with Su or Superuser, then it will find this, and that would be silly, especially if it was a nonfunctional frontend.

Any tips on how to get rid of it.

thanks

Daniel
Click to expand...

where are you seeing this? go launcher? or you do see it in manage applications
 
it is in the main app drawer
It is NOT in manage applications

what is "go launcher"
also, what app do you/does SURoot use to display memory statistics as shown in the first post of the dGB ROM

daniel
 
actually, I did nor remove the apk and binary, I just renamed them to something completely different. eg. aaafdsd.apk
I assumed that this would be good enough.
is that not the case?

Daniel
 
probably not, i would take a nandroid backup then remove them
chances are you cannot now due to not having root
you will need to use adb shell via recovery
remember to mount system from recovery first
then
cd /system/app/
rm Superuser.apk (i think thats what its called)
cd ..
cd /system/bin/
rm su
reboot
 
You must log in or register to reply here.
Back
Top Bottom