-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Flashing and rooting overview
- Thread starter Cougar
- Start date
-
- Tags
- samsung i7500
Rastaman-FB
Extreme Android User
Why are you using donut sdk when galaxy is on cupcake?
Cougar
Android Enthusiast
pegasus21 said:
Yeah, that's how I got the ADB info. I couldn't see it for fastboot though, all it came back with was "Android 1.0". Maybe just a timing issue?
Rastaman-FB said:
I wasn't using the SDK, just installing it to extract the driver from it. I figured, latest SDK = latest driver set. The SDK version is irrelevant (and if you're really concerned, it contains dev tools for both 1.5 and 1.6 anyway).
Are you asking me or Pegasus? I'm just using what Pegasus provided in his zips. I think he decided to use them as they were more up to date and he was able to hack the drivers to work with it so why not?
I'm going to give adb from 1.5 r3 ago now.
Rastaman-FB
Extreme Android User
i was speaking to you sorry i should have been more specific zombi3
i dont think Pegasus is using x64 vista/window7. i could not get any of the drivers to work in 1.6 sdk. but you can just use the test drivers for x64/x86 in r3
the sdk is relevent as 1.6 does not have any android test drivers and the device does not get recognised by ADB i spent the best part of an 1hr messing around with all the drivers to work this out
i had this exact problem, you have about 10-15 seconds to link the android 1 device to the \android-sdk-windows-1.5_r3\usb_driver\amd64 or
\android-sdk-windows-1.5_r3\usb_driver\x86 and choose adb test
if you are running windows 7 you will need to choose browse for driver, all devices, have disk and then point it to it.
once i did this fastboot worked properly. it was doing my head in as there is no way to slow or pause the boot timer in fast boot
i dont think Pegasus is using x64 vista/window7. i could not get any of the drivers to work in 1.6 sdk. but you can just use the test drivers for x64/x86 in r3
the sdk is relevent as 1.6 does not have any android test drivers and the device does not get recognised by ADB i spent the best part of an 1hr messing around with all the drivers to work this out
i had this exact problem, you have about 10-15 seconds to link the android 1 device to the \android-sdk-windows-1.5_r3\usb_driver\amd64 or
\android-sdk-windows-1.5_r3\usb_driver\x86 and choose adb test
if you are running windows 7 you will need to choose browse for driver, all devices, have disk and then point it to it.
once i did this fastboot worked properly. it was doing my head in as there is no way to slow or pause the boot timer in fast boot
Cougar
Android Enthusiast
I had the same problem. Getting it to pick up the debug connection was straight-forward, getting the fastboot to work was a sod. Once I'd got the correct IDs (courtesy of Pegasus), getting fastboot to work was a matter of removing the working adb bridge driver and reconnecting. If you've got the wrong settings in the .inf for fastboot and the bridge installs, it never retries the same driver. Once you've got the correct code in the .inf, if you then delete the bridge and reconnect the phone it works straight away.
I don't know about any 'test' drivers, I'm mostly making this up as I go along (-:
Rastaman-FB
Extreme Android User
adb with odin?
if its adb? just use the test ones i mentioned before within the usb drivers for 1.5 r3
so go into device manager and uninstall the android device/interface driver, unplug and reconnect the device
point the device driver wizard to the location of the android_usb.inf depending on your os type and pick the adv test interface.
adb will now be able to talk to the device when device is turned on
i noticed that if i am in recovery mode i have to unplug and replug the usb in order for adb to take the status from offline to ready
I got fed up of trying to install the fastboot driver in the 15 secs countdown (my pc must be getting old...) so I tried with the recovery flasher apk. Worked like a charm! Thank you so much for the procedure.
My only concern now is that as soon as I update to II5, where this way of rooting is no longer allowed, I don't know if I would be able to root. Could it possible to have the original firmware pre-rooted before flashing it with Odin?
My only concern now is that as soon as I update to II5, where this way of rooting is no longer allowed, I don't know if I would be able to root. Could it possible to have the original firmware pre-rooted before flashing it with Odin?
Ok so I uninstalled the drivers replugged in the device,went to manaually select the drivers , have disk and all that, but it says "the specified location does not contain information about your hardware".
I think I'm close but this is starting to annoy me now!
edit:
Just pointing it to the driver directory installs the regular composite adb drivers and these don't work when using adb from the command line.
edit: ok scratch that adb is working now! brb
edit: and I'm done, adb all installed
. Thats for the help Raster.It is possible. Just find a way to rebuild the tar archive used in the odin flashing process and swap out recovery. While you're at it, you could also learn how to pre-root your kernel image. Not a straightforward process but you'll be able to do it for any new image that is released.
Rastaman-FB
Extreme Android User
this thread should actually be stickied
justjimjpc
Premium Member
I have added Search Tags to the thread that will make it easy to find using the TAG Search feature on this site ....
Taking out the original recovery.img from the tar file and putting in the recovery.img from hdblog would be a very easy procedure. Too easy in fact, that's why I was wondering that maybe there's some kind of integrated data checksum or integrity checks during the flashing procedure that would prevent the flashing from being successful if I swap the recovery's. Anybody knows?
About the kernel pre-rooting thing... my linux knowledge is near zero, although I have a quite technical profile , so I would love to learn about it, any sources I can get informed from?
As far as I can tell, there isn't any checksum in recovery, kernel and system. There's one in the csc (cache). Both the recovery and kernel contains some code at the beginning of the image. The latter part is gz and cpio-ed. System is a yaffs2 image. Just unyaffs and mkbootimg to get it back.
N
nightcrow
Guest
Somehow I can't get adb remount (step 8) to run. I assume it has to be in recovery mode and the directory has to be the one that has all the downloaded files in them. However the command seems to do nothing. Any idea what I might be missing here?
In recovery mode I can see the list of options, enabled root su and made a backup with nandroid. So I believe all the earlier steps have been succesful.
Rastaman-FB
Extreme Android User
i noticed that when i did these steps it does not give confirmation of command being accepted
only reason i knew it was actually doing what i told it to is because when i got to 9. Once successful, upload busybox "adb push busybox /system/bin/busybox" it gave the amount of bites pushedi did this while in recovery mode and verified the files had been pushed to the device
it has however worked as im able to copy and paste files from protected locations to other locations on the device with no complaint from the system
N
nightcrow
Guest
I used the drivers you posted with the manual as a download. Should I be using another one for these last steps?
When I restart the command prompt and try the command at step number 9 I don't get a reaction either. The cursor just jumps to the next line and keeps blinking there. Weirdest thing is that after using adb I can't shut off my Vista (32bit) PC the normal way by using the start menu. I have to reboot by pressing the on/off button. What could be the cause of this?