Sample Header Ad - 728x90

How can I unlock the boot loader on a HTC Magic?

5 votes
1 answer
2221 views
After a lot of unsuccessful days trying to root my Android phone, I'll now post my problem here with every approach I already did. Maybe someone can help me. I am trying to unlock the boot loader on a HTC Magic 32B (S-ON, HBoot-1.33.0007 (SAP10000), CPLD-10, Radio-2.22.19.26i) so that I can flash it with a custom ROM (like cyanogen 5 or 6).. ## How is it done? If I'm not misunderstanding the process, it's like this: - Rooting the device (i.e. using UniversalRoot.apk, SuperOneClick.exe) - Unlocking the boot loader for CustomRecovery (i.e. Clockworkmod, AmonRA Recovery) - Flashing the custom ROM (cyanogen) in recovery mode (Vol Down+Power while booting) - That's it... (afaik) ## What's the problem? Unlocking my boot loader doesn't seem to work. =( I rooted the device a couple of times using the 1.5 Exploit, SuperoneClick.exe or at least UniversalRoot.apk. So on the OS side it really seems to be rooted. I often heard about "ROM Manager.apk", but it don't find any version working on 1.6 and prior. If I use fastboot flash recovery then I get an FAILED (remote: not allow) which leads to the point where I have to unlock to boot loader. ## What I already tried to unlock the boot loader **HTCDev.com, unlocking officially via HTC** The command fastboot oem get_identifier_token doesn't seem to recognize the "get_identifier_token" parameter, it ends in a [ERR] Command error. I'm in fastboot usb mode (cable to pc, device and fastboot devices confirms that). Everything is installed properly (HTC Sync, Android SDK, ADB, Fastboot). I tried it on Mac and on Windows. **Unlocking via ADB shell** - Connecting to the device using ADBshell - My recovery.img files are on /sdcard and have chmod 0755 (or for testing 777) - su works so I do have a # at the beginning of the command - I do have a flash_image on the root of sdcard, executing it via ./flash_image gives me permission denied, even if I'm root with chmod set I have read that updating HBoot could solve this, but didn't find a working file and tutorial for that (every post is really old and often leads to a 404). Any help is appreciated!
Asked by Thomas Marbella (161 rep)
Aug 3, 2013, 01:21 PM
Last activity: May 29, 2017, 03:21 PM