Database Info

forgot 2 turn fastboot off before loading new rom?

hi......i forgot 2 turn fastboot off from setting\power......while switching from CoreDroid_Sense_3.5_26.1.12_RV to Android_Revolution_HD-4G_6.3.2....... so now my phone not booting & can't write recovery............just load in hboot\fastboot...but after that nothing just the t-mobile screen for hours.......now what to do?

Has nothing to do with fastboot. I bet you are unlocked with HtcDev.com and all you need is to flash boot image separately after flashing the rom. Look for details here in the forum, it was explained many times.
Sent from my HTC Desire S

See this thread http://forum.xda-developers.com/showthread.php?t=1537259
Swyped from my Desire S using XDA Premium

dmatik said:
Has nothing to do with fastboot. I bet you are unlocked with HtcDev.com and all you need is to flash boot image separately after flashing the rom. Look for details here in the forum, it was explained many times.
Sent from my HTC Desire S
Click to expand...
Click to collapse
C:\android>fastboot flash recovery recovery.img
sending 'recovery' (5796 KB)... OKAY [ 0.998s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 1.014s
did all but...........
C:\android>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 0.98.0000
INFOversion-baseband: 38.03.02.11_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.30.110.2
INFOserialno: Hxxxxxxxxxxxxxxxx
INFOimei: xxxxxxxxxxxxxxxxxx
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG88*****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3788mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 361a7ba6
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.016s

If you flash the ENG HBOOT 98.2
That should permit you to flash recovery
Although you missed trying to flash the boot image, as suggested above.
Swyped from my Desire S using XDA Premium

ben_pyett said:
If you flash the ENG HBOOT 98.2
That should permit you to flash recovery
Although you missed trying to flash the boot image, as suggested above.
Swyped from my Desire S using XDA Premium
Click to expand...
Click to collapse
have tried flashing the boot.img from Android_Revolution_HD-4G_6.3.2
or should i try another boot img....................

You should try boot image from the ROM that you aye trying
Swyped from my Desire S using XDA Premium

ben_pyett said:
You should try boot image from the ROM that you aye trying
Swyped from my Desire S using XDA Premium
Click to expand...
Click to collapse
tried the boot but...........same error not able to write

lostfossil said:
tried the boot but...........same error not able to write
Click to expand...
Click to collapse
Maybe dumb question, but are you at the bootloader while executing the fastboot command?
Swyped from my Desire S far away from my PC (maybe)

Tectas said:
Maybe dumb question, but are you at the bootloader while executing the fastboot command?
Swyped from my Desire S far away from my PC (maybe)
Click to expand...
Click to collapse
yes..............is i give the command of reboot-bootloader...it does that
........but after the reboot only again t-mobile screeen
tried hboot but same error

was able to flash recovery....................and boot.img but still stuck.........just moved from t-mobile screen to htc screen......do i have to flash sys.img

[guide] back to stock from facepalm s-off

WARNING!!!
DO NOT turn your secureflag on unless on a stock,signed hboot.
s-on with an eng signed or patched hboot will hard brick your device immediately.(read: permanently bricked,unrecoverable)
in other words,ONLY use the writesecureflag 3 command AFTER running an RUU. never before.
im sure were mostly to excited to want to go back to s on just yet,since we just got s-off but its a matter of time before this comes up,so here ya go:
prerequisites:
-that you know your stock CID and build number(x.xx.xxx.x for example, xxx=531= tmobile, xxx=401= htc europe)
if you have a relocked bootloader,and want to reset the lock status to read locked,reference this thread: http://forum.xda-developers.com/showthread.php?t=2155955
flash "lock_bootloader.zip" in your recovery of choice,then procede to the following steps.
1)donwload and run an RUU for your most current STOCK carrier/reigonal build
2)open a cmd window. plug in phone,charge only mode,usb debugging on.
3)run the following:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writecid xxxxxxxx (where xxxxxxxx is your stock CID. example: HTC__001 or T-MOB010)
fastboot reboot-bootloader
fastboot getvar cid (verify your stock CID)
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>[COLOR="Red"]adb reboot bootloader[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]fastboot devices[/COLOR]
HTxxxxxxxxxx fastboot
c:\miniadb_ville>[COLOR="Red"]fastboot oem writecid HTC__001[/COLOR]
...
(bootloader) Start Verify: 0
OKAY [ 0.014s]
finished. total time: 0.016s
c:\miniadb_ville>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
rebooting into bootloader...
OKAY [ 0.066s]
finished. total time: 0.068s
c:\miniadb_ville>[COLOR="red"]fastboot getvar cid[/COLOR]
cid: HTC__001
finished. total time: 0.004s
c:\mini-adb_vigor>[COLOR="red"]fastboot oem writesecureflag 3[/COLOR]
... OKAY [ 0.051s]
finished. total time: 0.051s
c:\mini-adb_vigor>[COLOR="red"]fastboot reboot-bootloader[/COLOR]
rebooting into bootloader... OKAY [ 0.177s]
finished. total time: 0.177s
c:\mini-adb_vigor>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.168s
c:\mini-adb_vigor>
*verified working if you need it for warranty.
*current RUUs can be found here:
http://androidfiles.org/ruu/?dir=Ville
or here:
http://shipped-roms.com/index.php?category=android&model=Ville
*if you need adb/fastboot you can use this:
http://www.mediafire.com/?hzf1u4bowjewhdq
(extract,move to root of c,change to that directory with cd c:\mini-adb )

mine

Thank you! This will come in handy for many.
Sent from my HTC One S using xda premium

AW: [guide] back to stock from facepalm s-off
My stock cid is O2___102 but i changed it to HTC__102 can i use the HTC cid for S-ON?
Gesendet von meinem HTC One S mit Tapatalk 2

Why did you change your CID?Because your phone is branded to O2 and you want to flash different RUU??
If you want to S-ON it again make sure that your CID is for your region and you will flash the correct RUU for it.
After you flashed....and everything looks good you can use "fastboot oem writesecureflag 3" for S-ON.

hi,
i'm currently on an s-off with supercid and twrp recovery with cyanogen image.
I need to revert back to stock firmware, stock recovery, stock cid, s-on, * LOCKED * bootloader.....
anyone can just highlight correct steps sequence to follow to get that?
Thanks in advance

It's all in the first post.

El_Svanto said:
It's all in the first post.
Click to expand...
Click to collapse
I don't see anything about putting back stock recovery...
Also what about changing cid after installing ruu...I read somewhere else it doesn't work...is it true?

The ruu installs stock recovery as a part of the firmware. If you are s-off you can still change cid after ruu. Use command "fastboot oem writecid HTC__001". Use your cid instead of HTC__001.

[SOLVED] Stuck in bootloader/fastboot, RUU: Error [140]

I'm having a serious issue with my device. I'm trying to roll back to s-on and stock GB for warranty purposes using this thread which I've successfully done before.
I flashed the ENG hboot and then the 0.98.0002 hboot using Android Flasher and the bootloader now shows the following:
Code:
*** Security Warning ***
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3831.17.00.16_M
eMMC-boot
Mar 30 2011, 17:29:31
Now I'm trying to run a RUU (the same RUU which worked before) but I'm getting the following message on all the RUUs that I try - Error [140]: Bootloader version error
The RUUs I've tried are:
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed
My device is stuck in the bootloader now - I can't boot into the rom or recovery. Is my goldcard no longer effective for some reason? Did I flash a corrupt hboot?
'fastboot getvar all' reveals the following:
Code:
INFOversion: 0.5
INFOversion-bootloader: 0.98.0002
INFOversion-baseband: 3831.17.00.16_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.04.401.1
INFOserialno: **
INFOimei: **
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG8810000
INFOcidnum: HTC__016
INFObattery-status: good
INFObattery-voltage: 4023mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 0e35ea5b
INFOhbootpreupdate: 12
INFOgencheckpt: 0
I have the official ICS RUU but haven't tried it because I don't want to upgrade the hboot if it's not necessary. Waiting for some sort of guidance on what to do from here - will be highly appreciated.

Re: [Q] Stuck in bootloader/fastboot, RUU: Error [140]
Misc_version
Sent from my HTC Desire S

Can't misc_version only be changed via adb? I don't have access to adb, only fastboot.

Yes, i think misc_version can be chenge only with adb

Any suggestions as to what I could do from here?

Re: [Q] Stuck in bootloader/fastboot, RUU: Error [140]
None, you really need to push the misc . version through adb, can't you get to a computer?
“Some cause happiness wherever they go; others whenever they go” - Oscar Wilde

I do have access to a computer but adb doesn't pick up my device.
As per lowveld's response from the help thread, when I try to flash CWM from this thread via fastboot, I get the following error:
Code:
C:\Users\Admin>fastboot flash recovery recovery-clockwork-touch-5.8.1.5-saga.img
sending 'recovery' (3518 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)

Re: [Q] Stuck in bootloader/fastboot, RUU: Error [140]
oddoneout said:
I do have access to a computer but adb doesn't pick up my device.
As per lowveld's response from the help thread, when I try to flash CWM from this thread via fastboot, I get the following error:
Code:
C:\Users\Admin>fastboot flash recovery recovery-clockwork-touch-5.8.1.5-saga.img
sending 'recovery' (3518 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
Click to expand...
Click to collapse
Did you unlock your bootloader before trying to push the recovery
“Some cause happiness wherever they go; others whenever they go” - Oscar Wilde

Re: [Q] Stuck in bootloader/fastboot, RUU: Error [140]
jugg1es said:
Did you unlock your bootloader before trying to push the recovery
“Some cause happiness wherever they go; others whenever they go” - Oscar Wilde
Click to expand...
Click to collapse
Beat me by 52 seconds...
Sent from my Nexus 4 using Tapatalk 2

I have not - I'm a tad worried about that pesky *** RELOCKED *** warning that I might not be able to remove. Is unlocking my bootloader the only option I have right now?

Re: [Q] Stuck in bootloader/fastboot, RUU: Error [140]
oddoneout said:
I have not - I'm a tad worried about that pesky *** RELOCKED *** warning that I might not be able to remove. Is unlocking my bootloader the only option I have right now?
Click to expand...
Click to collapse
Fraid so, it's the only way you can push anything. There is a way to remove the relocked, ill have to search for it though
Edit, can't find it. Amidabuddha might know how though.
“Some cause happiness wherever they go; others whenever they go” - Oscar Wilde

Right - guess I have to use HTCDev after all. Will report back with the results.

Re: [Q] Stuck in bootloader/fastboot, RUU: Error [140]
oddoneout said:
Right - guess I have to use HTCDev after all. Will report back with the results.
Click to expand...
Click to collapse
Didn't you keep the code from the first time, you can use it again
“Some cause happiness wherever they go; others whenever they go” - Oscar Wilde

I recieved my device with 0.98.0002 so I could s-off without using HTCDev.
Edit: looks like I have to download HTC Sync (160mb) and Android SDK (400mb) which might take some time. Will check in again after some coffee and a cigarette.

Looks like I may be in trouble...
Code:
C:\Users\Admin>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.020s]
finished. total time: 0.030s
PS: my device is listed when using the 'fastboot devices' command.

It's almost 3 in the morning but I've finally managed to sort this out.
In short I installed the official ICS RUU, unlocked bootloader, rooted, lowered misc_version and then installed the original RUU which previously worked (HBoot 0.98.0002). Now everything is factory fresh, without any warnings in the bootloader.
Just to clarify, it was the misc_version that prevented me from installing the RUU which previously worked? If that's the case, how was it changed? Do certain roms higher the misc_version?

Bump

[Q] CM11 and Hboot 2.13

Will I be able to flash CM11 or any other KK ROM with Hboot 2.13? I have searched around without much luck, when I updated my Hboot, I got stuck with this strange version of it.
Thanks

gooner98 said:
Will I be able to flash CM11 or any other KK ROM with Hboot 2.13? I have searched around without much luck, when I updated my Hboot, I got stuck with this strange version of it.
Thanks
Click to expand...
Click to collapse
Try upgrade your hboot to 2.15:
1. Download here
2. Move the file to the location of fastboot on your computer
3. Windows: Open fastboot folder and hold shift and right click, then select Open Command Window Here.
Mac: Open a terminal window and your fastboot folder alongside each other. drag fastboot from folder to terminal window
4. Get into fastboot mode and type the following commands
fastboot oem rebootRUU
fastboot flash zip orig_hboot_2.15.0000.zip
fastboot reboot-bootloader
5. You should see Hboot 2.15.0000. If you had s-off with hboot 2.13 you will have it with 2.15
6. You should be able to flash cm11 nightlies now

Thanks for that, I'll give it a go.

OK, I got a fail
C:\fastboot>fastboot oem rebootRUU
... INFOStart Verify: 0
OKAY [ 0.280s]
finished. total time: 0.280s
C:\fastboot>fastboot flash zip orig_hboot_2.15.0000.zip
sending 'zip' (400 KB)... OKAY [ 0.238s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 1.928s
C:\fastboot>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.383s]
finished. total time: 0.383s

Do the command again, when you flash your firmware.zip with fastboot, this first try fail but the second is good. I don't know it may be some kind of security
Envoyé de mon One S en utilisant Tapatalk

Hi Guys
Any confirmation with this one? Did it work?
I do also have similat HBoot 2.13.
Have a phone from "3" / Three UK network with this HBOOT.
I was able to do the S-OFF.
Previous CID: CID: H3G__001 (H3G_01)
Current state:
CID: 11111111
Bootloader (HBOOT) 2.13 version
Baseband is 1.11.50.05.28
TWRM 2.6.0.0
Model: PJ4010000
I have checked the zip file from this thread and found txt file with details:
modelid: PJ4010000
cidnum: HTC__001
mainver: 3.16.401.8
btype:1
aareport:1
hbootpreupdate:1
...
Should I change CID before proceeding with HBOOT upgrade?
I am really afraid cause flashing HBOOT causes most of the bricks?

You guys are either not reading much or dont know how to search. The assert check in updater-script for any ROM allows flashing for the following hboots: 2.13.0000, 2.15.4444 and 2.15.0000
It is like this from the beginning and it was stated several times. So you don't need to update any hboot if you're on 2.13.
Sent from nowhere over the air...

Thanks Rapier. and I am sorry for taking your time. can I just clarify? you're saying that I can flash my phone with even kitkat (4.4) when I am on HBOOT 2.13? even when all threads are mentioning HBOOT in version 2.15/2.16?
really confusing for me. like I have missed something really basic over the last 3-4 weeks of reading this forum ?

MOD hboot 1.55 X920D Remove Red Text

You must be S-Off to do this
Just do in bootloader
1) fastboot oem rebootRUU
2) fastboot erase cache
3) fastboot flash zip firmware1.55MOD.zip -- in this point please wait a moment
4) fastboot reboot-bootloader
optional reboot in recovery for test
Important: The flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before
reboot to make sure it is safe to reboot!
note: if needed for another hboot just tell me
Update: 1.57 https://mega.co.nz/#!1Q9yCSrD!fNdHv3ISgIbbKGDl0ovRWCT25z9DuEksx_offKvdxzw

Great Work! Thanks man!

not working for me
cidnum: HTC__044
version-bootloader: 1.55.0000
version-main: 3.15.707.4
hbootpreupdate: 11

Rename the downloaded file to PL99IMG.zip which is place in ext-card and reboot to boot loader. It will install and work fine without any problems.

it says wrong cid, update fails

indrawib said:
it says wrong cid, update fails
Click to expand...
Click to collapse
You must be S-Off to do this

I've already S-OFF but it said like that.

Good working fine...Thanks..
Sent from my HTC One using XDA Premium 4 mobile app

victor0888 said:
You must be S-Off to do this
Just do in bootloader
1) fastboot oem rebootRUU
2) fastboot erase cache
3) fastboot flash zip firmware1.55MOD.zip -- in this point please wait a moment
4) fastboot reboot-bootloader
optional reboot in recovery for test
Important: The flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution!
The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before
reboot to make sure it is safe to reboot!
note: if needed for another hboot just tell me
Update: 1.57 https://mega.co.nz/#!1Q9yCSrD!fNdHv3ISgIbbKGDl0ovRWCT25z9DuEksx_offKvdxzw
Click to expand...
Click to collapse
Dear,
I Fallow these step but following error.
target reported max download size of 1514139648 bytes
sending 'zip' (642 KB)...
OKAY [ 0.205s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 1.723s