Works, but stuck at the next step
OK noob questions coming up, can't find the answer!
This method works for me to root my N1 (2.3.6), although I have to do the rm ... /boomsh if I run it more than once, and it loses root on reboot.
I am doing it manually using zergRush exploit rather than the other link, as I am on a mac and would like the experience anyway. Maybe this is where I'm going wrong!
When I finish the root my SD card seems to unmount itself; my computer can't see the drive, but I can still adb; I can reattach the card, is that just me?
I am aiming to get to cyanogenmod in the long run, so I believe the next step (as posted on their site) is to install a custom recovery file (going for clockworkmod).
However, it sounds like I need su, which would come along with any root method that involves a bootload unlock but which I don't have? So not sure if I need to push that to the SD card/where to. I got for these problems trying to do so (I put all the files in the one folder platform tools btw)
Code:
doms-laptop:platform-tools user$ ./adb push su /system/bin
failed to copy 'su' to '/system/bin/su': Read-only file system
and
Code:
doms-laptop:platform-tools user$ ./adb install Superuser.apk
1111 KB/s (785801 bytes in 0.690s)
pkg: /data/local/tmp/Superuser.apk
Failure [INSTALL_FAILED_ALREADY_EXISTS]
I installed the Rom manager app in case they could install superuser rights or clockworkmod from my current rooted stage but no joy, using RomManager to flash clockworkmod recovery fails "while running privileged commands." [That'll be no su then]
EDIT:
So now i booted windows, installed adb drivers, and rooted with the kit, simples... Rom Manager working fine
Thanks chaps