• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

How To root your San Diego

238 posts in this topic

Posted

I'f I remember busybox was in /sbin so can't you use that

0

Share this post


Link to post
Share on other sites

Posted (edited)

OK done, replaced superuser & busybox in root folder with x86 superuser apk and your busybox.

Rooted and rebooted....that flashing screen worries me :lol:

second reboot, my screen is still flashing :unsure:

Not good the flashing screen is permanent now.

Factory reset again I think :lol:

Edited by jikobutsu
0

Share this post


Link to post
Share on other sites

Posted

can you get adb

0

Share this post


Link to post
Share on other sites

Posted

Flashing screen?? :blink:

0

Share this post


Link to post
Share on other sites

Posted

it's because there is a busybox already on the phone lol it's in /sbin

1

Share this post


Link to post
Share on other sites

Posted (edited)

Flashing screen??

Yeah it is what happened when we first rooted, after a reboot it stops, but putting x86 superuser & your busybox in rooting folder, replacing originals, makes the flashing persist.

It ok now, factory reset, good as new.

Edited by jikobutsu
0

Share this post


Link to post
Share on other sites

Posted

Ah right I see. Not liking the sound of this flashing screen though

0

Share this post


Link to post
Share on other sites

Posted (edited)

Can we use Odin to flash roms now we have root

Edited by Mtman1
0

Share this post


Link to post
Share on other sites

Posted

Yeah something not right, but as I said, after a reboot it is gone, what the cause is who knows?

0

Share this post


Link to post
Share on other sites

Posted

Cant we use Odin to flash roms now we have root?

Don't even attempt to do this unless you want a brick

0

Share this post


Link to post
Share on other sites

Posted (edited)

Ok I am a noob, I forgot to replace the su binary for x86 :lol: lets try that again.

Nope same problem, only a factory reset fixes it, but root is still retained.

Edited by jikobutsu
0

Share this post


Link to post
Share on other sites

Posted

If it messes up again then I believe this to be the busybox binary. As said already by rickywyatt, there is busybox in /sbin already set up on the system. The original exploit had the ARM version so this wasn't installed (it would be pushed but cannot run and install itself) which retains the original busybox.

When you use the x86 busybox I found, it gets pushed to the phone and installed - taking over from the /sbin busybox. It seems that the system doesn't like this for whatever reason and panics. I assume it's running some sort of integrity check?

0

Share this post


Link to post
Share on other sites

Posted

Oh Paul said it needs a busybox building with the only additional modules and links (to add the stuff the original busybox is missing)

0

Share this post


Link to post
Share on other sites

Posted

So what is the original busybox missing?

0

Share this post


Link to post
Share on other sites

Posted

Ok I am a noob, I forgot to replace the su binary for x86 vz58yY1liRYCAAFZfy6F4BF5syZM7uzPMVdEiioktM1FywyZ9asmR1lyd4KQEHV7KZJYJFZM2dMrC+O9wIJyvrU9qnDQV6UmzRQUMS2vAEhmBZqJggU5NXLqEIIRvrr8IAcL26dWQrkTp8OJKIDTcVYQd7kUHZMzYWoCw90UGSHBYhhcFxSYmxEiK8BLEBAQadp7hIU4GyiAQ86cCDzS6mpSfHDAxkLAAC0X1cVifZAbAAAAABJRU5ErkJggg== lets try that again.

Nope same problem, only a factory reset fixes it, but root is still retained.

Remove the new busybox and replace with the original ARM binary if you still have it? That should stop the issue and install the right superuser. With luck you'll retain root.

0

Share this post


Link to post
Share on other sites

Posted (edited)

But surely if there was some check going on, when I overwrite busybox with xplore app with your busybox, I would have same problem right ? only it takes it fine and there is root still.

Sorry getting confused now lol. So I should put back the original busybox pushed to my device by the rooting exploit ?

edit: Ok I have replaced the busybox and I still have root.

Edited by jikobutsu
0

Share this post


Link to post
Share on other sites

Posted

There is /sbin busybox - the phones default busybox. Required by the system

Pushing busybox puts it in /system/xbin/ and attempts to run busybox -install to set up the symlinks. This will then overwrite the original /sbin busybox symlinks with symlinks for the new busybox. The phone doesn't like this and refuses to boot.

Pushing the original arm busybox doesn't matter because it doesn't execute on the phone so it doesn't take over - thus retaining the original /sbin busybox and it's symlinks.

Assuming the busybox x86 I found isn't bad then the problem can be resolved by not installing any other busybox, or pushing an ADDITIONAL busybox to /system/xbin to add any missing symlinks

If the busybox x86 I found IS bad (as in it won't run properly on the phone) then we need another busybox.

Sorry if this is unclear.. I'm making sense of it all and it's not an easy thing to write.

0

Share this post


Link to post
Share on other sites

Posted (edited)

Yeah I understand, just been a bit to much excitement tonight :lol:

So what if I was to delete busybox in xbin ? or am I going down wrong road here.

Edited by jikobutsu
0

Share this post


Link to post
Share on other sites

Posted

But surely if there was some check going on, when I overwrite busybox with xplore app with your busybox, I would have same problem right ? only it takes it fine and there is root still.

Sorry getting confused now lol. So I should put back the original busybox pushed to my device by the rooting exploit ?

edit: Ok I have replaced the busybox and I still have root.

Yep that's right. Adding the original busybox back, which was ARM, means it won't be installed.

Can you open Superuser and use the option to check it's set up correctly (I forget what the option is called)

Yeah I understand, just been a bit to much excitement tonight

So what if I was to delete busybox in xbin ? or am I going down wrong road here.

That shouldn't cause a problem leaving it there.

0

Share this post


Link to post
Share on other sites

Posted (edited)

I cannot see any option for that in superuser ?

There is some info on su binary if that is what you mean.

post-796032-0-35525000-1349652456_thumb.

Edited by jikobutsu
0

Share this post


Link to post
Share on other sites

Posted

could you not copy the busybox from /sbin and put it in /system/xbin ?

0

Share this post


Link to post
Share on other sites

Posted

'tap to check for updates' and it'll do a quick update test and check if the bin is installed correctly. Also try requesting root on an app that requires root.

0

Share this post


Link to post
Share on other sites

Posted

I cannot see any option for that in superuser ?

There is some info on su binary if that is what you mean.

tap to check for updates and ask it to download the binary and reinstall su
0

Share this post


Link to post
Share on other sites

Posted

Lol sorry been a while since I had root, yep.binary was out of date now updated.

0

Share this post


Link to post
Share on other sites

Posted

aha. The built-in busybox may be OK then. Superuser just needed to be the right version lol

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.