Root Your Magic/Sapphire

Seems like Haykuro has done it again, folks. Thanks to a tip off from one of our Senior Members over at Android Forums, noonehereyet, it looks like you are now able to root your Magic and continue laughing at us G1 users. When you’re feeling feisty, head on over to Android-Dls for a walk through and links to the roms needed for the rooting process.

For those of you brave enough to play the Guinea pig role for the fellow Phandroid readers, what are your comments or concerns? Did you run into any snags? How did you resolve them?

Happy Rooting!

[Thanks noonehereyet!]

Continue reading:




  • Geir Sjurseth

    I just did this and it worked. There were two distinct differences for me in the instructions.

    1) My phone had to be actually be on when I ran the adb commands (even the first ones) but since this only really important for pushing the files over i don’t think it much matters.

    2) since I’m on a mac I had to use fastboot-mac instead. Otherwise it went smoothly.

    When I run adb shell now I get a root prompt. I’ve installed busybox and and all is well.

    Now, if only I could understand why I still cannot use wifi-tether :(

  • Mike

    rooting my magic?

    Can someone give me a quick summary of why you would want to do that, what is to be gained.

    Also, why should you not do it, what are the chances of bricking it? Can it be de-bricked?

  • WardCo

    Just did this on my Developer’s Conference sapphire with a Mac OS X host. Two things:

    1. If you don’t have “.” in your path, you have to say
    fastboot boot ./recovery-new.img

    2. I got into an infinite reboot loop as zygote was coming up:

    06-10 15:27:00.474 I/SystemServer( 311): Starting Hardware Service.
    06-10 15:27:00.484 W/HAL ( 311): load: module=/system/lib/hw/lights.sapphire.so error=Cannot find library
    06-10 15:27:00.484 W/HAL ( 311): load: module=/system/lib/hw/lights.sapphire.so error=Cannot find library
    06-10 15:27:00.494 E/ActivityThread( 311): Failed to find provider info for settings
    06-10 15:27:00.504 W/dalvikvm( 311): threadid=31: thread exiting with uncaught exception (group=0x4000fe70)
    06-10 15:27:00.504 E/AndroidRuntime( 311): Uncaught handler: thread PowerManagerService exiting due to uncaught exception
    06-10 15:27:00.504 E/AndroidRuntime( 311): *** EXCEPTION IN SYSTEM PROCESS. System will crash.
    06-10 15:27:00.504 E/AndroidRuntime( 311): java.lang.NullPointerException
    06-10 15:27:00.504 E/AndroidRuntime( 311): at android.content.ContentQueryMap.(ContentQueryMap.java:65)
    06-10 15:27:00.504 E/AndroidRuntime( 311): at com.android.server.PowerManagerService.initInThread(PowerManagerService.java:414)
    06-10 15:27:00.504 E/AndroidRuntime( 311): at com.android.server.PowerManagerService$1.onLooperPrepared(PowerManagerService.java:374)
    06-10 15:27:00.504 E/AndroidRuntime( 311): at android.os.HandlerThread.run(HandlerThread.java:59)

    ….solution was to use the recovery program to erase my DATA mtd partition too.

  • http://www.novoda.com Kevin McDonagh

    @WardCo Thanks for the tip, I got caught out.

  • http://www.novoda.com Kevin McDonagh

    I should explicitly say that I also had to restart the phone in fastboot mode and remove the data partition.

  • http://automation.liveautomatic.com Insteon

    Like the first poster, I had to leave my phone on for it to work for me, but otherwise it worked great.