Well, I had unlocked my son's HTC Incredible 2 with the HTC Dev Tool. All was good until I went to install a ROM and it choked at the white HTC screen. I got it up thanks to the forums but then decided to go for full blown S-OFF via the comprehensive directions.
It was going well but something must have went wrong somewhere and I'm slightly fearful that I may be screwed.
Here's my fastboot info as of now:
VIVO_W XB SHIP S-ON RL
HBOOT-0.97.0000
RADIO-1.09.01.0622
eMMC-boot
It's bootlooping now. If I reset it in fastboot, it will come up and stay up until I reboot it myself. I have no recovery and when I try to unlock the phone with the steps via the dev tool, it fails (signature verify fail).
Anyone have any ideas? I've got a log of my comprehensive adventure if it helps.
Meh, here is the log anyway. Things look weird when I lock it and at the end...
Code:
D:\htc>md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.062
2_NV_VZW1.92_release_199487_si.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[D:\htc\]
RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2... 100% cea499f51b40055ffd118960e1e73255
D:\htc>md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[D:\htc\]
1.09.01.0312_vivow_Radio_PG32IMG.zip ea6b98be48210d7797e62362f49ff751
D:\htc>md5sums misc_version
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[D:\htc\]
misc_version 050f55d34ddbcc860efa5982491437de
D:\htc>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT144MA07332 device
D:\htc>adb push CWM-SuperSU-v0.94.zip /mnt/sdcard
1447 KB/s (674673 bytes in 0.455s)
D:\htc>adb reboot bootloader
D:\htc>fastboot devices
HT144MA07332 fastboot
D:\htc>fastboot flash recovery recovery.img
sending 'recovery' (5330 KB)... OKAY [ 1.692s]
writing 'recovery'... OKAY [ 0.946s]
finished. total time: 2.638s
D:\htc>adb push misc_version /data/local/tmp/misc_version
error: device not found
D:\htc>adb push misc_version /data/local/tmp/misc_version
1792 KB/s (367096 bytes in 0.200s)
D:\htc>adb shell chmod 777 /data/local/tmp/misc_version
D:\htc>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
D:\htc>adb reboot bootloader
D:\htc>fastboot devices
HT144MA07332 fastboot
D:\htc>fastboot getvar mainver
mainver: 2.18.605.3
finished. total time: 0.001s
D:\htc>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.543s
D:\htc>fastboot erase cache
erasing 'cache'... OKAY [ 0.182s]
finished. total time: 0.182s
D:\htc>fastboot oem rebootRUU
... OKAY [ 0.162s]
finished. total time: 0.162s
D:\htc>fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_
1.09.01.0622_NV_VZW1.92_release_199487_si.zip
sending 'zip' (292817 KB)... OKAY [ 47.862s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,31
INFO[RUU]UZ,boot,73
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,99
INFO[RUU]WP,boot,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,22
INFO[RUU]UZ,recovery,43
INFO[RUU]UZ,recovery,63
INFO[RUU]UZ,recovery,84
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,99
INFO[RUU]WP,recovery,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,5
INFO[RUU]UZ,system,8
INFO[RUU]UZ,system,13
INFO[RUU]UZ,system,16
INFO[RUU]UZ,system,22
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,31
INFO[RUU]UZ,system,37
INFO[RUU]UZ,system,42
INFO[RUU]UZ,system,48
INFO[RUU]UZ,system,53
INFO[RUU]UZ,system,56
INFO[RUU]UZ,system,61
INFO[RUU]UZ,system,65
INFO[RUU]WP,system,0
INFO[RUU]WP,system,5
INFO[RUU]WP,system,8
INFO[RUU]WP,system,13
INFO[RUU]WP,system,16
INFO[RUU]WP,system,22
INFO[RUU]WP,system,25
INFO[RUU]WP,system,30
INFO[RUU]WP,system,33
INFO[RUU]WP,system,39
INFO[RUU]WP,system,42
INFO[RUU]WP,system,47
INFO[RUU]WP,system,50
INFO[RUU]WP,system,55
INFO[RUU]WP,system,59
INFO[RUU]WP,system,65
INFO[RUU]UZ,system,65
INFO[RUU]UZ,system,67
INFO[RUU]UZ,system,71
INFO[RUU]UZ,system,73
INFO[RUU]UZ,system,77
INFO[RUU]UZ,system,79
INFO[RUU]UZ,system,82
INFO[RUU]UZ,system,85
INFO[RUU]UZ,system,87
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,95
INFO[RUU]UZ,system,98
INFO[RUU]WP,system,65
INFO[RUU]WP,system,67
INFO[RUU]WP,system,70
INFO[RUU]WP,system,73
INFO[RUU]WP,system,76
INFO[RUU]WP,system,79
INFO[RUU]WP,system,82
INFO[RUU]WP,system,85
INFO[RUU]WP,system,88
INFO[RUU]WP,system,91
INFO[RUU]WP,system,94
INFO[RUU]WP,system,97
INFO[RUU]WP,system,100
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
INFOstart image[dzdata] unzipping & flushing...
INFO[RUU]UZ,dzdata,0
INFO[RUU]UZ,dzdata,100
INFO[RUU]WP,dzdata,0
INFO[RUU]WP,dzdata,100
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFO[RUU]WP,tp,0
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,7
INFO[RUU]UZ,radio,13
INFO[RUU]UZ,radio,21
INFO[RUU]UZ,radio,27
INFO[RUU]UZ,radio,34
INFO[RUU]UZ,radio,42
INFO[RUU]UZ,radio,48
INFO[RUU]UZ,radio,55
INFO[RUU]UZ,radio,62
INFO[RUU]UZ,radio,69
INFO[RUU]UZ,radio,76
INFO[RUU]UZ,radio,83
INFO[RUU]UZ,radio,90
INFO[RUU]UZ,radio,97
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,5
INFO[RUU]WP,radio,12
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,26
INFO[RUU]WP,radio,33
INFO[RUU]WP,radio,42
INFO[RUU]WP,radio,100
OKAY [208.359s]
finished. total time: 256.221s
D:\htc>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.245s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.096s
finished. total time: 6.087s
D:\htc>fastboot reboot
rebooting...
finished. total time: 0.155s
run revolutionary THEN flash the radio
JehC said:
run revolutionary THEN flash the radio
Click to expand...
Click to collapse
Lol I remember telling you that
Did you re-lock the bootloader before trying to s-off? That needs to be done
Sent from my HTC Incredible 2 using xda app-developers app
You guys rock! I didn't even think about running Revolutionary. I just assumed something was jacked and it wouldn't work. I'm not sure if I did something wrong to get it in that state but it would have been nice to see this mentioned in the comprehensive instructions.
At any rate. I'm back in business. Thanks for the help.
Sure did, and I've spread the word a few times myself
sent from my paranoid android
clambert11 said:
You guys rock! I didn't even think about running Revolutionary. I just assumed something was jacked and it wouldn't work. I'm not sure if I did something wrong to get it in that state but it would have been nice to see this mentioned in the comprehensive instructions.
At any rate. I'm back in business. Thanks for the help.
Click to expand...
Click to collapse
What do you want mentioned in my guide? That you need to flash the radio after Revolutionary? I had it that way originally but people weren't able to boot before flashing the new radio. I haven't actually run it myself so I don't know for sure what works all the time.
Sent from my SCH-I535 using Tapatalk 2
prototype7 said:
What do you want mentioned in my guide? That you need to flash the radio after Revolutionary? I had it that way originally but people weren't able to boot before flashing the new radio. I haven't actually run it myself so I don't know for sure what works all the time.
Click to expand...
Click to collapse
When I was done following the steps, the phone was bootlooping. Maybe that's not normal. The only way I could get it to stop was to do a factory reset from Fastboot. If the phone was rebooted or powered off after that, the bootloops would happen all over again.
I just thought if the booplooping was normal it might be worth mentioning in the tutorial, that's all. But I could have been the exception, in which case it wouldn't make sense to mention it.
if i remember right, after i downgraded i was able to boot once without bootlooping, then ran revolutionary, then flashed the radio
pppp
this problem i have too. any ideas?
gioodo said:
this problem i have too. any ideas?
Click to expand...
Click to collapse
run revolutionary first and when its done flash radio
here use these instructions
download and run Revolutionary
you can have revolutionary install a recovery,or install one manually after s-off is achieved. included in miniadb_inc2.zip (the one you downloaded for s-off) download is the 0312 radio, which you will need to flash if you start experiencing bootloops.
if you need to flash the 0312 radio:
put the phone in fastboot mode(select fastboot from hboot menu),open a cmd window,change to miniadb_inc2 directory then enter:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip (when you checked it above with the md5sums command,it matched right?)
fastboot reboot-bootloader (make sure your baseband changed)
fastboot reboot
i have error on flashing process C:\inc2>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.362s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.715s
gioodo said:
i have error on flashing process C:\inc2>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.362s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.715s
Click to expand...
Click to collapse
You need to run revolutionary first before flashing radio radio can't be flashed with s-on
Sent from my ADR6350 using xda app-developers app
ArslanQureshi said:
You need to run revolutionary first before flashing radio radio can't be flashed with s-on
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
please see this my post http://forum.xda-developers.com/showthread.php?p=47003009#post47003009
i have unlock token Can't see locked or not
Welcome.
I have the following problem with my HTC. When you turn on the phone immediately turns on fastboot and can not control buttons Vol + / - on the menu. Can I come in hboot, but there did not respond to my commands.
It is a chance to solve the problem?
*** UNLOCKED ***
BUZZ PVT SHIP S-ON
HBOOT-1002.0000
MICROP-0622
TOUCH PANEL-ATMELC03_16ac
RADIO-3.35.20.10
Click to expand...
Click to collapse
BukeR00 said:
Welcome.
I have the following problem with my HTC. When you turn on the phone immediately turns on fastboot and can not control buttons Vol + / - on the menu. Can I come in hboot, but there did not respond to my commands.
It is a chance to solve the problem?
Click to expand...
Click to collapse
Does it boot Into hboot or fastboot specifically? Also do you have an sdcard in the phone? And lastly when you plug in the usb cable to issue commands does the phone change to hbootUSB or fastbootUSB at all and does Windows detect and Install drivers?
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
When I push the power button, phone starts in FASTBOOT. I can run it in hboot by pressing Vol-+ PWR.
In both modes, the buttons are not working. When I connect the USB cable changes as FASTBOOT USB / HBOOT USB or something like that. I have a card in your phone, I try without the card.
BukeR00 said:
When I push the power button, phone starts in FASTBOOT. I can run it in hboot by pressing Vol-+ PWR.
In both modes, the buttons are not working. When I connect the USB cable changes as FASTBOOT USB / HBOOT USB or something like that. I have a card in your phone, I try without the card.
Click to expand...
Click to collapse
OK please try without the card in also when you are in fastboot USB can you issue the command fastboot getvar all please and see if it works.
Sent from my Nexus 7 using Tapatalk 4
Code:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: ###########
INFOimei: ###########
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 3955mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.053s
Without the card the same problems. Keys are not working. When I'm try to upload RUU crashes. 155 ERROR. I tried to many versions, as last RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed
Thanks for your reply
BukeR00 said:
Code:
C:\adb>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.02.0000
INFOversion-baseband: 3.35.20.10
INFOversion-cpld: None
INFOversion-microp: 0622
INFOversion-main: 2.46.0.0
INFOserialno: ##########
INFOimei: ###############
INFOproduct: buzz
INFOplatform: HBOOT-7225
INFOmodelid: PC4910000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 3955mV
INFOpartition-layout: HTC
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 42e5cc47
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.053s
Without the card the same problems. Keys are not working. When I'm try to upload RUU crashes. 155 ERROR. I tried to many versions, as last RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed
Thanks for your reply
Click to expand...
Click to collapse
I should have said, block out your imei and HTC serial number like I have. You never know whos watching...
Anyway, your bootloader is still unlocked so ruus wont flash. You can use the command fastboot oem lock to relock the bootloader. But, it's unlikely that it will work as you have an upgraded hboot. If I was you I would I would extract the Rom.zip from the ruu. Then extract that Rom.zip and you should end up with several images and some .nbh files. place the boot.img, system.img, data.img Into your fastboot folder. Then you going to want to format the phone with fastboot and then flash the phone with fastboot. http://androidforums.com/one-s-all-things-root/714676-list-fastboot-command.html here is a command list but I will tell you what I think it should be, and if you hit a snag refer to the link. So the commands should be in this order assuming you are CD'd to your fastboot folder
fastboot format boot
fastboot format system
fastboot format data
fastboot format cache
Then assuming it all goes well then issue these commands
fastboot flash system.img
fastboot flash data.img
fastboot flash boot.img
fastboot flash boot.img
fastboot reboot
Yes that flash the boot.img twice is not a typo all going well after this you should able to boot up. if you hit any big problems just hit the thread pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Code:
C:\adb>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.015s
In FASTBOOT shows now - *** RELOCKED ***
Code:
fastboot format boot
fastboot format system
fastboot format data
fastboot format cache
It does not work. There is no these commands
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
Code:
C:\adb>fastboot flash system.img
unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
C:\adb>\fastboot flash data.img
'\fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\adb>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
C:\adb>fastboot flash system system.img
sending 'system' (212163 KB)... OKAY [ 44.854s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 98.833s
C:\adb>fastboot flash boot boot.img
sending 'boot' (2476 KB)... OKAY [ 1.050s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.689s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.012s
In my rom.zip there is no data.img
After the command fastboot reboot the phone hangs on the white HTC boot screen.
BukeR00 said:
Code:
C:\adb>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.015s
In FASTBOOT shows now - *** RELOCKED ***
Code:
fastboot format boot
fastboot format system
fastboot format data
fastboot format cache
It does not work. There is no these commands
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
Code:
C:\adb>fastboot flash system.img
unknown partition 'system.img'
error: cannot determine image filename for 'system.img'
C:\adb>\fastboot flash data.img
'\fastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\adb>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
C:\adb>fastboot flash system system.img
sending 'system' (212163 KB)... OKAY [ 44.854s]
writing 'system'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 98.833s
C:\adb>fastboot flash boot boot.img
sending 'boot' (2476 KB)... OKAY [ 1.050s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.689s
C:\adb>fastboot reboot
rebooting...
finished. total time: 0.012s
In my rom.zip there is no data.img
After the command fastboot reboot the phone hangs on the white HTC boot screen.
Click to expand...
Click to collapse
Ah. This could be problematic. I should have been clearer, I didn't mean for you to lock your bootloader again, I was simply informing you it would need to be locked for an ruu to run. None of those commands will work while the bootloader is locked. If you were the one to unlock the device the you can unlock it again assuming you have the unlock_token.bin, using the same fastboot command again. If you didn't you will have to go to www.htcdev.com and make an account, then go to bootloader unlock, select wildfire buzz and ignore the bootloader update, as you already have it. (Skip should be near the bottom.) Then follow the instructions and get the bootloader unlocked again. Then issue the commands excluding the lock bootloader one and the flash data data.img as you don't have it. Its not a problem though, I was just covering all bases, incase it did have a data.img in there make sure you still do the data format though!
Sorry for the confusion
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
What version of RUU I must use? I tested 3 versions and none of them has data.img
I have uploaded the files system.img, recovery.img, userdata.img and the phone still does not work. How can I delete the data. Fastboot format command does not work, there is no such command.
And after the command fastboot erase still:
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
BukeR00 said:
What version of RUU I must use? I tested 3 versions and none of them has data.img
I have uploaded the files system.img, recovery.img, userdata.img and the phone still does not work. How can I delete the data. Fastboot format command does not work, there is no such command.
And after the command fastboot erase still:
Code:
C:\adb>fastboot erase boot
erasing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb> fastboot erase data
erasing 'data'... FAILED (remote: not allowed)
finished. total time: 0.002s
C:\adb>fastboot erase system
erasing 'system'... FAILED (remote: not allowed)
finished. total time: 0.002s
Click to expand...
Click to collapse
did you get the bootloader unlocked again? fastboot commands will only work on unlocked bootloaders.
Dont worry about the data.img, you do not need it. i simply added it incase the ruu had it and you got confused. again, it is not required.
Yes, I have unlocked bootloader, but comands still don't work.
//edit:
C:\sdk\sdk\platform-tools>fastboot format boot
formatting 'boot' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.006s
C:\sdk\sdk\platform-tools>fastboot format system\
formatting 'system\' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.006s
C:\sdk\sdk\platform-tools>fastboot format userdata
formatting 'userdata' partition...
FAILED (remote: unknown command)
FAILED (remote: unknown command)
finished. total time: 0.006s
Click to expand...
Click to collapse
BukeR00 said:
Yes, I have unlocked bootloader, but comands still don't work.
//edit:
Click to expand...
Click to collapse
hmmm. well if we cannot format the partitions then we are not going to have much luck :/
ok lets try a different tactic. download this and rename it to just recovery.img . then place it into your adb folder and then issue the following command via fastboot.
Code:
fastboot boot recovery.img
hopefully this will allow you to boot into clockworkmod recovery. when you enter clockworkmod recovery use the volume buttons to move and the trackball to select, power is back. format everything. then try to mount your sdcard using advanced/mount storage or sdcard, something to that effect. then place this file onto it. all going well you should be able to then flash this rom. dismount the usb storage, then go back to the main menu (power button) then go to flash/install, select choose zip and then the zip file we placed there. hopefully the recovery will install without issue. then, open the copy of the rom you downloaded on your pc and extract the boot.img. reboot the phone into fastboot and then use the command fastboot flash boot boot.img
all going well this rom will boot and you will have a working phone again.
Unfortunately, it does not change anything. I can not enter into Clockworkmod recovery. The keys are not working
BukeR00 said:
Unfortunately, it does not change anything. I can not enter into Clockworkmod recovery. The keys are not working
Click to expand...
Click to collapse
it should boot into cwm automatically, no button intervention required.
Unfortunately does not turn ClockworkMod. Phone lay two days without batteries, has launched today as normal. Everything worked. I wanted to do S-OFF by unrevoked, entered into hboot, the phone resets and hung on the HTC screen. After removing the battery turns on hboot again. In Unrevoked I saw that wrote "ClockworMode Recovery"
BukeR00 said:
Unfortunately does not turn ClockworkMod. Phone lay two days without batteries, has launched today as normal. Everything worked. I wanted to do S-OFF by unrevoked, entered into hboot, the phone resets and hung on the HTC screen. After removing the battery turns on hboot again. In Unrevoked I saw that wrote "ClockworMode Recovery"
Click to expand...
Click to collapse
Unrevoked doesnt s-off it only roots and flashes a recovery.
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Hi,
Short story:
My One X won't boot to Android anymore. I can only enter boot / fastboot modes.
And when trying to apply modifications (fastboot flash or fastboot unlock), it shows various errors, not always the same.
Long story:
I bought this phone second hand quite a while ago, soon after its market launch. It was already unlocked and rooted, but I don't know what method had been used.
RUU says it runs release 1.28.
Boot says:
- S-On
- HBoot-0.94.0000
- Radio 1.1204.103.14
- Apr 11 2012,02:27:11
Given that it was unlocked / rooted it never received an OTA.
I recently decided to perform a full wipe, and by the way a full upgrade.
So:
- I did a CWM Recovery backup
- I flashed a «semi-stock» image, the stock de-odexed 4.18.401.3 from android-revolution (URL forbidden here, I'm a newbie!) .
- I performed a full wipe / factory reset / cache cleaning / Dalvik cache cleaning.
It didn't boot, and I learnt about the ICS / JB hboot incompatibility.
I tried to flash the boot from the android-revolution page, with no improvements.
So, I decided to revert to my Nandroid backup, from the recovery.
Didn't boot either.
Then I found a Windows computer, relocked the bootloader, and tried RUUs (3.14 and 1.26) with no success.
CID is HTC__203, so I used .401 RUU or OTA files.
RUU application stops each time at a different moment, either for usb connexion error, wrong RUU for my phone, not enough battery, or unknown error.
I read about a battery charge issue, and tried this method to charge it:
Code:
while : ; do fastboot getvar battery-voltage; fastboot reboot-bootloader; sleep 6; done
(as you may see, my main workstation is running Linux)
After a 9 hours long night:
Code:
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
It seems that it couldn't go farther than 3.6V.
But if I tried to unlock my phone after that:
Code:
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]#
You can see error message is not always the same.
Same for my firmware.zip flash attempts:
Code:
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (remote: unknown command)
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (command write failed (Cannot send after transport endpoint shutdown))
finished. total time: 5.928s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
OKAY [ 1.419s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 1.629s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]#
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
hervenicol said:
Hi,
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
Click to expand...
Click to collapse
Give me result from command fastboot getvar version-main
Download this fastboot.zip and extract it to a folder fastboot rename the file fastboot-linux to fastboot. The file fastboot only is for windows and if you want to keep it rename fastboot to fastboot-windows
Thant said:
Give me result from command fastboot getvar version-main
Click to expand...
Click to collapse
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
hervenicol said:
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
Click to expand...
Click to collapse
1. Charge your phone
2. Download this RUU 1.28.401.9
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Thant said:
1. Charge your phone
2. Download RUU 1.28.401.9 (link removed from quote)
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Click to expand...
Click to collapse
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
hervenicol said:
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
Click to expand...
Click to collapse
Good to hear that:good:
All upgrades applied, works like a charm
I set the title for this answer with [SOLVED], I hope it applies to the thread as well.
Now let's look for a way to root this rom!