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

Root S-off

Ok I extracted that to the root of C:\ and ran the cmd again. It worked fine it recognized my device HTxxxxxxxxxx bunch of numbers and alphabets. So I tried running Android Flasher again(Phone on fastboot screen) but it froze on pushing and flashing recovery just like last time!!? Im getitng very frustrated with this now!

EDIT: some threaders on xda have reported issues with the utility so Im going to try an older version and see if that makes any difference.
 
Something is wrong with the utility. I tried v1.6.0 it wouldnt load anything and I cant find v1.5.5 anywhere on the net. Has anybody got a working utility??
 
dont know i'm afraid, out of my depth. The flasher utility worked fine for me. I'm sure a more senior member here can help out.
 
Just out of curiosity how long did it takes for utility to download img?? Mine froze the moment I uploaded the img:confused:
 
About a minute or 2.

You have renamed the file recovery.img havent you? If you already have named it that then just fastboot it manually.

Put it in the tools folder, after the fastboot devices command, the next command you use is fastboot reovery.img
 
it HAS to be called "recovery.img"

I'm sorry, I did imply this earlier but I didn't explicitly say to rename it. I just said "Flash recovery.img"

That'll be why it was freezing then
 
This is what I get:

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\GingaB>cd\

C:\>cd\android-sdk-windows\tools

C:\android-sdk-windows\tools>fastboot devices
HTxxxxxxxxx fastboot

C:\android-sdk-windows\tools>fastboot recovery.img
usage: fastboot [ <option> ] <command>

commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader

options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048

C:\android-sdk-windows\tools>


Not sure what cmd is asking for!!?
 
I tried using AlphaRev for the same reason, tired of using adb, but when I made the boot disc and booted into it, it didn't recognise the phone... It's a HTC Desire GSM Bravo PVT4, exactly what the site says it supports, but no dice.

It doesn't display any information at all. Weird? Amon-ra and everything worked a treat with no issues.
 
You must log in or register to reply here.
Back
Top Bottom