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

Root Flashing and rooting overview

scollie said:
Thanks for the reply but before posting yesterday I had just re-installed NPS for the 3rd time. There are no changes in the devices before and after installing. Also after plugging in the phone, the only difference is ADB Interface appears!

When you say change one of the 'storage devices' do you mean USB Mass Storage Device? Before and after installing NPS there is only 1 USB Mass Storage Device in the USB Serial Controllers list.

When installing NPS it all goes ok until a message pops up

'Installing device drivers. This may take several minutes.'

Then after a short while I get another pop up

'USB driver install error
Unable to launch the 1 Driver Setup file! Code:1'
and so on for each of the drivers.

Is this the error message you would expect on Win 7 for failure to install the USB drivers because as mentioned above nothing gets set up in device manager whereas under XP something was set up (cannot remember exactly what) which then needed to be pointed to the NPS USB drivers (If my memory serves me well)? I would have expected something similar under Win 7.

How have other Win 7 x64 users managed to set up USB drivers and ADB?

Anything else anyone could think of that I could try?
Click to expand...
i installed it via havedisk in "update driver" device manager and pointing it to x64 android_usb.inf in the 1.5r3 SDK then choosing test interface
im using windows7 x64 professional
 
Rastaman-FB said:
i installed it via havedisk in "update driver" device manager and pointing it to x64 android_usb.inf in the 1.5r3 SDK then choosing test interface
im using windows7 x64 professional
Click to expand...

I too updated the ADB Interface exactly as you mention above but it still doesn't work!

When you installed NPS, did you get usb driver install errors like this
'USB driver install error
Unable to launch the 1 Driver Setup file! Code:1'

After installing NPS, apart from ADB Interface what other instances of SAMSUNG do you see in device manager?

For example under XP there were entries under Modem, Ports and USB drivers but under Win 7 I have nothing but the ADB entry relating to SAMSUNG and I'm not sure if this is what is causing my problem.
 
scollie said:
I too updated the ADB Interface exactly as you mention above but it still doesn't work!

When you installed NPS, did you get usb driver install errors like this
'USB driver install error
Unable to launch the 1 Driver Setup file! Code:1'

After installing NPS, apart from ADB Interface what other instances of SAMSUNG do you see in device manager?

For example under XP there were entries under Modem, Ports and USB drivers but under Win 7 I have nothing but the ADB entry relating to SAMSUNG and I'm not sure if this is what is causing my problem.
Click to expand...
i installed NPS in vista compatability and nps sees the device
i got driver errors but i clicked ok to them
i also made sure my account was setup to have higher security permissions
(logged in as administrator and modified my user account to have the same permissions as Administrator"
 
Rastaman-FB said:
i installed NPS in vista compatability and nps sees the device
i got driver errors but i clicked ok to them
i also made sure my account was setup to have higher security permissions
(logged in as administrator and modified my user account to have the same permissions as Administrator"
Click to expand...

My account is an administrator account but that doesn't help. I have also tried right clicking the file and 'Run as administrator' - no difference.

I have now created an administrator account and looked to see whether I could give my account any further permissions but there didn't seem to be a way to do so. I then re-installed NPS from the administrator account - same result!

In device manager do you have any other entries for Samsung apart from ADB Interface which is the only one I have?
 
Hey guys,
After some work and a great search on google, I managed to solve the non-interactive adb driver issue that i, and others, suffered from. The blog that assisted me directed me to a software called USBDeview, where on it you delete any existing samsung drivers and the next time you plug in the phone your OS will recognize it properly as the adb interface and it'll work.

My problem now, after enabling root, is that i can't remount... I get: "remount failed: Operation not permitted"... what can i do about it??
Right after enabling root, while still in the recovery menu i tried typing adb remount and got: "error: device offline". so i rebooted, powered on and then got the failing message.
I appreciate your help guys, it's been quite a challenge to get around the adb issue, now for the busybox.

p.s.
the link for the blog with the USBDeview, credits forward
 
trin said:
Hey guys,
After some work and a great search on google, I managed to solve the non-interactive adb driver issue that i, and others, suffered from. The blog that assisted me directed me to a software called USBDeview, where on it you delete any existing samsung drivers and the next time you plug in the phone your OS will recognize it properly as the adb interface and it'll work.

My problem now, after enabling root, is that i can't remount... I get: "remount failed: Operation not permitted"... what can i do about it??
Right after enabling root, while still in the recovery menu i tried typing adb remount and got: "error: device offline". so i rebooted, powered on and then got the failing message.
I appreciate your help guys, it's been quite a challenge to get around the adb issue, now for the busybox.

p.s.
the link for the blog with the USBDeview, credits forward
Click to expand...

actually its like that
however when it said device offline in recovery, just disconnect the device and reconnect it.
you cannot adb remount when live in the android os unless you have a modified kernal.

so if you need to use adb remount, boot into recover before connecting the device then connect the device and it should function correctly
 
thanks a million!
the remount was successful. However, at the next stage I seem to be getting this error:
"failed to copy 'busybox' to '/system/bin/busybox': No space left on device"
even though it seems like I have a ton of space left...

How can I tackle this?

I really appreciate your support!
 
trin said:
thanks a million!
the remount was successful. However, at the next stage I seem to be getting this error:
"failed to copy 'busybox' to '/system/bin/busybox': No space left on device"
even though it seems like I have a ton of space left...

How can I tackle this?

I really appreciate your support!
Click to expand...
how many apps have you got installed?
even though you have 8 gig of space to play with there is a maximum of 1gig for system and apps i believe
if that is not the case then im not too sure.
you might want to speak with kam or pegasus as they are a bit more clued up about that stuff than me
 
Wierd.. there should be enough space on system. But in any case why dont u put it in /data instead?

"adb push busybox /data/busybox"

Set busybox to executable with "adb shell chmod 4755 /data/busybox"

Next remove the cp command "adb shell rm /system/bin/cp"

Relink cp to busybox "adb shell ln -s /data/busybox /system/bin/cp"

adb shell /data/busybox --install -s /system/bin"
 
I ran all the commands ok, and the last one (install) i got "not a directory" for each of the rows that were printed on screen.
Is that normal?
 
kam187 said:
Wierd.. there should be enough space on system. But in any case why dont u put it in /data instead?

"adb push busybox /data/busybox"

Set busybox to executable with "adb shell chmod 4755 /data/busybox"

Next remove the cp command "adb shell rm /system/bin/cp"

Relink cp to busybox "adb shell ln -s /data/busybox /system/bin/cp"

adb shell /data/busybox --install -s /system/bin"
Click to expand...

So i've added the '/' at the end of the last row, and I'm still getting the 'Not a directory' on every row...

I'm beginning to think busybox doesn't like me ;)
 
You did remount first right?

do:
adb shell

Then in the shell type
chmod 4755 /data/busybox

Just to make sure your file is actually there

Then do:

mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system

and then:

/system/bin/busybox --install -s /system/bin/
 
Kam187, thanks for the efforts. However it still isn't installing. Remember i'm not able to copy busybox to system and you told me to do it through data instead.
I followed your instructions above and at the last one received:
"/sbin/sh: /system/bin/busybox: not found"

I attempted to change your last line to "/data/busybox --install -s /system/bin/"
and again got the 'Not a directory' error....
 
You must log in or register to reply here.
Back
Top Bottom