Database Users

Can't flash radio

Hello, I have a 32A with 1.76.2007 SPL, and 6.35.08.29 Radio, and I simply can't flash the radio. I can flash the SPL just fine, I've flashed it to 1.33.2010 and then to 1.76.2007 with no problems, however, when I try to flash the radio it just keeps saying in the command line "Writing". I've followed this tutorial to the letter: http://forum.xda-developers.com/showthread.php?t=605239
By the way I tried to flash it to two different radios now, an old 3.22, and the newest 6.35
Thanks in advance, and I hope I'm not making a stupid mistake, since I'm new at this.

Still got the problem?
Can you provide more info or why you are trying to flash a diff radio...
Also, download my fastboot commander from my signature and copy-paste all the device info.

Thanks for answering, and I'm sorry I didn't post why I'm trying to flash a different radio. The thing is most ROMs out there are 3.22 and so I can't install them unless I do that. I used your program and here is what it said:
SPL/hboot version: 1.76.2007.
Radio version: 6.35.08.29.
Main software version: 3.05.401.3.
cid: htc__506.
cpld: 12.
product: sapphire.
mid: sapp10000.
security: off.
build-mode: eng.

If you download the magic 32A version, you will get a special tab.
I will flash a compatible set of spl, radio and recovery.
Try it out and if you get an error, post here what you see in the "actual output".

Thanks a lot! It finally worked! But I still don't understand why it didn't work the other way around. I noticed that when I tried to flash it in the command line, as soon as it said it was "Writing" my phone's screen would turn black, and it didn't when I used your awesome program.
Anyways I highly recommend this program to anyone who wants to flash SPL/Radio.
By the way could you check my other thread? It's also about a problem that's been annoying me very much.

I'm glad it worked out for you :0)
About the other problem, i have no idea :0)

Oh, ok, well thanks a lot anyway

Update hboot

Hello,
I want only to update my hboot from 0.80.0007 to 1.01.0001
Nothing else, only hboot so i can s-off
Im currently rooted with cwm and cm7
Does anyone know if it is posibel to only update my hboot?
Sent from my HTC Wildfire using Tapatalk

I thought about this as well as I have the same hboot but I s-offed with xtc clip. But you would need to run a ruu man. And then run revolutionary and then restore your nandroid back up of your cyanogenmod. I didn't as the update hboot did nothing for me but I'm pretty sure that's how you would do it. No guarantees though :-/
Sent from my HTC Wildfire using XDA App

Is there not a way to extract the hboot from the ruu and then update it?
Sent from my HTC Wildfire using Tapatalk

i dont think so. the ruu only signs the hboot for use when its running so if its not in the ruu the phone wont accept it. :/ i dont know of any other method than using a ruu, but would love to see if anyone else knew a way to do it

Can you delete the rest other then de hboot from the ruu then?
Sent from my HTC Wildfire using Tapatalk

I suppose you could try but I don't know how the ruu would react to it, or even if it does that first. lf you were to delete the rest of it and say the ruu wiped your phone before doing the hboot you could end up stuck with s-on with no rom on your phone....
sent from my steroid powered, cyanogenmod filled wrecking machine! using xda app.

ok I have now extracted the rom.zip out of the ruu.exe
and unpacked the zip,
the folowing files are interesting in it:
hboot_7225_1.01.0001_101117.nb0
splash1.nb0
, what should i do now,
how do i flash it??

Delete what you don't want and rename the zip to PC49IMG.zip drop it on your SD card and reboot into hboot, volume down and power wait for it to load up press volume up wait again and press power to reboot and it should be done.
Sent from my HTC Wildfire using xda premium

Ok thanks, was a little thinking about that already. My brain was thinking aaa because of the extention of the hboot file,
Going to try that Tomorrow or at the end of the week
Sent from my HTC Wildfire using Tapatalk

i was thinking about 2 things
first, the signing (its still s-on so it should be signed (with the key from htc witch noone knows) does the zip also needs to be signed? or just the files within it?(hboot)
second, does the hboot image also format my other partitions (could be posible if you think about this, there are roms in .nb0 format)

Scratch0805 said:
Delete what you don't want and rename the zip to PC49IMG.zip drop it on your SD card and reboot into hboot, volume down and power wait for it to load up press volume up wait again and press power to reboot and it should be done.
Click to expand...
Click to collapse
uh delete from the orginal rom.zip wont work, it gives me an error (winrar: unrecovereble archive, 7-zip: not implemented)(i guess the rom.zip has to be signed or secured but have unpacked it so i can repack what i need but still those 2 questions
topjor said:
i was thinking about 2 things
first, the signing (its still s-on so it should be signed (with the key from htc witch noone knows) does the zip also needs to be signed? or just the files within it?(hboot)
second, does the hboot image also format my other partitions (could be posible if you think about this, there are roms in .nb0 format)
Click to expand...
Click to collapse
i see there is a file: android_info.txt
Code:
modelid: PC4910000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
mainver: 2.22.405.1
hbootpreupdate:12
DelCache: 1
i think i also need to delete some lines of the cidnum's but there are 10 cidnum's and 9 files in the zip

topjor said:
uh delete from the orginal rom.zip wont work, it gives me an error (winrar: unrecovereble archive, 7-zip: not implemented)(i guess the rom.zip has to be signed or secured but have unpacked it so i can repack what i need but still those 2 questions
i see there is a file: android_info.txt
Code:
modelid: PC4910000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
mainver: 2.22.405.1
hbootpreupdate:12
DelCache: 1
i think i also need to delete some lines of the cidnum's but there are 10 cidnum's and 9 files in the zip
Click to expand...
Click to collapse
Extract, delete what you don't want, leave the txt file completely alone then rezip and call it PC49IMG.zip. it doesn't need signing.
Sent from my HTC Wildfire using xda premium

u can use this to update http://forum.xda-developers.com/showthread.php?t=1160251 u can change to any hboot if you want. but if you have s on and want s off just flash froyo ruu, and then rev.

rolks said:
u can use this to update http://forum.xda-developers.com/showthread.php?t=1160251 u can change to any hboot if you want. but if you have s on and want s off just flash froyo ruu, and then rev.
Click to expand...
Click to collapse
Read the op I ONLY WANT TO UPDATE HBOOT so i can s-off
Sent from my HTC Wildfire using Tapatalk

hello again man. did you have any luck? oh btw htcdev have released a bootloader unlock for the wildfire, im not sure if you`ll need to update the whole rom but it says it just needs a hboot update. might be worth a look.

Scratch0805 said:
Extract, delete what you don't want, leave the txt file completely alone then rezip and call it PC49IMG.zip. it doesn't need signing.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
No signing neded would mean that you could flash every rom with s-on
Sent from my HTC Wildfire using Tapatalk

heavy_metal_man said:
hello again man. did you have any luck? oh btw htcdev have released a bootloader unlock for the wildfire, im not sure if you`ll need to update the whole rom but it says it just needs a hboot update. might be worth a look.
Click to expand...
Click to collapse
That's what I want, only update hboot, but I only have one problem now, wil the hboot.nb0 format the rest of the partitions because that would brick my phone
Edit:
Ps I want revolutionary hboot
And the official unlocker wil notify HTC I beleave
Sent from my HTC Wildfire using Tapatalk

topjor said:
No signing neded would mean that you could flash every rom with s-on
Sent from my HTC Wildfire using Tapatalk
Click to expand...
Click to collapse
No custom roms are different to ruu's, they need signing and flashing through cwm, I've used the PC49IMG method to update hboot plenty of times just delete what you don't want i.e radio, recovery, rom splash etc so you're left with hboot and the txt file then zip it up as I've said above after you reboot go back to hboot and you will have the upgraded one.
Sent from my HTC Wildfire using xda premium

Scratch0805 said:
No custom roms are different to ruu's, they need signing and flashing through cwm, I've used the PC49IMG method to update hboot plenty of times just delete what you don't want i.e radio, recovery, rom splash etc so you're left with hboot and the txt file then zip it up as I've said above after you reboot go back to hboot and you will have the upgraded one.
Sent from my HTC Wildfire using xda premium
Click to expand...
Click to collapse
Does that work on s-on.
Just to br sure
Sent from my HTC Wildfire using Tapatalk

topjor said:
Does that work on s-on.
Just to br sure
Sent from my HTC Wildfire using Tapatalk
Click to expand...
Click to collapse
Oh.....maybe not as the partitions will be locked it wouldn't have harmed your phone though as the partition is locked, I never thought of that.
In that case you should try simply running the ruu instead of PC49IMG method.
Sent from my HTC Wildfire using xda premium

[SIM-UNLOCK] All One Varients[WIP]

[Thread will be back up]
This Thread is a WIP Thread open for discussion.
Please be patient, it IS being worked whether it's discussed or not in the thread.

Subscribe already

Oh, it's Christmas in June. :highfive:

ooooh this sounds interesting

Looking forward to this
Sent from my HTC One using Tapatalk 2

18th.abn said:
UNDER CONSTRUCTION
Big Thanks to all the devs who brought us all s-off. Its all because of their HARD work.
Beaups
Fuses
Revolutionary.io
anyone else working in the background ot that im unaware of at this time
Thank you to fnoji111 for providing the temporary hboot we are going to be using here.
S-OFF is MANDATORY. if you aint got it, git it!
WARNING - This is a simple procedure but can and will brick a device if the steps are not followed or if you explore deeper than you should during the Unlock. I am not responsible for any damage and HIGHLY suggest following all the steps through until the end.
Click to expand...
Click to collapse
Eagerly waiting to see how you gonna do it for sprint version in which we can't get any prompt to put unlock code.

i will give a shot here using my htc one sprint fill post a new feedback after im done
------
i got this error on flashing
C:\Users\XXXX\Downloads\Compressed\Root_HTC_One_Sprint\Root_HTC_One_Sprint>fastboot flash hboot enghboot.nb0
sending 'hboot' (2080 KB)...
OKAY [ 0.463s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.499s

solnoy said:
i will give a shot here using my htc one sprint fill post a new feedback after im done
Click to expand...
Click to collapse
Do it?
---------- Post added at 07:39 PM ---------- Previous post was at 07:31 PM ----------
sending 'hboot' (2080 KB)...
OKAY [ 0.450s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.484s
???

here is my info on my Htc One (Sprint)
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 1.00.20.0315
version-cpld: None
version-microp: None
version-main: 1.29.651.7
version-misc: PVT SHIP S-OFF
serialno: FA34AS9XXXXX
imei: 9900014656xxxxx
meid: 99000146xxxxx
product: m7_wls
platform: HBOOT-8064
modelid: PN0720000
cidnum: SPCS_001
battery-status: good
battery-voltage: 3901mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT

I will update op. Must be on fuses Moonshine hboot. He has a lot of work in the hboot and flashing restrictions are removed. With his hboot, the red text is also removed from splash screen.
I apologize, moonshine s-off/hboot is mandatory.

@18th.abn
Is that engineering hboot safe to just leave it on the phone permanently? I would love to have a permanent eng hboot than a normal updated hboot.

18th.abn said:
I will update op. Must be on fuses Moonshine hboot. He has a lot of work in the hboot and flashing restrictions are removed. With his hboot, the red text is also removed from splash screen.
I apologize, moonshine s-off/hboot is mandatory.
Click to expand...
Click to collapse
So thats why it didnt take

18th.abn said:
I will update op. Must be on fuses Moonshine hboot. He has a lot of work in the hboot and flashing restrictions are removed. With his hboot, the red text is also removed from splash screen.
I apologize, moonshine s-off/hboot is mandatory.
Click to expand...
Click to collapse
I used revone to S-off would you mind a quick and dirty explanation of how to install the moonshine Hboot Manually if that's possible?

problem right now is i dont have linux to flash that moonshine

Sorry gunny, all I can do is link to their work. Any modification/alteration of their work isn't supported or allowed. Wish I could help more there :-/

18th.abn said:
Sorry gunny, all I can do is link to their work. Any modification/alteration of their work isn't supported or allowed. Wish I could help more there :-/
Click to expand...
Click to collapse
No worries.
Doesn't hurt to ask, so I asked

Oh well. thanks for the work.

Riyal said:
@18th.abn
Is that engineering hboot safe to just leave it on the phone permanently? I would love to have a permanent eng hboot than a normal updated hboot.
Click to expand...
Click to collapse
It's highly unrecomended. Device won't fully boot on some varients. Also, moonshine has all the benefits of eng hboot without the added danger of tinkering to much in the eng hboot

can i run moonshin even though im already unlocked?

18th.abn said:
It's highly unrecomended. Device won't fully boot on some varients. Also, moonshine has all the benefits of eng hboot without the added danger of tinkering to much in the eng hboot
Click to expand...
Click to collapse
Yeah that's what I thought lol! So then I would ask the 2nd question... On what variant did this eng hboot came from?
And another thing... Couldn't you just dd the eng hboot instead of flashing it through fastboot? Did took a quick glance on moonshine distiler binary and seems like they're doing the same.
*Edit removed for safety of newbies *

My findings for Google Keyboard FC and different CIDs

Ok so since I didn't get an answer in the Q&A section (126+ views) I figured I'd try a few things. I noticed the other day when I switched my CID to HTC__001 from CWS__001 when I rebooted I got a Google Keyboard FC. So I went through and tested 3 Hex edit CIDs with 3 different fastboot CIDs and these are the results:
The fastboot CIDs will be listed under the Hex ones that I tried. I'll put Yes if Google Keyboard worked and No if it FC'ed
Hex = CWS__001 (AT&T)
Fastboot CWS__001 - Yes
Fastboot 11111111 - Yes
Fastboot HTC__001 - No
Hex = HTC__001 (WWE)
Fastboot CWS__001 - Yes
Fastboot 11111111 - No
Fastboot HTC__001 - No
Hex = 11111111 (supercid)
Fastboot CWS__001 - Yes
Fastboot 11111111 - Yes
Fastboot HTC__001 - No
There have been quite a few posts that say there is no need to change the CID value (hex edit) in mmcblk0p19 but obviously it has some effect on at least one app. Also if you make your CID supercid through fastboot and your mmcblk0p19 is AT&T then the LTE icons are stock AT&T which is also true if you make mmcblk0p19 supercid and fasboot CID AT&T.
Can someone with more knowledge try to make sense of this? How come Google Keyboard won't work with anything HTC_001? I've done a full wipe and everything.
FWIW I'm using an AT&T HTC One. I flashed the Droid DNA eng-hboot and changed my model ID to PN0710000. After that I flashed back the 1.44 hboot from the One. I then changed my CID in both places to HTC__001 and flashed the 2.17 FW that mike posted.

SkizzMcNizz said:
Ok so since I didn't get an answer in the Q&A section (126+ views) I figured I'd try a few things. I noticed the other day when I switched my CID to HTC__001 from CWS__001 when I rebooted I got a Google Keyboard FC. So I went through and tested 3 Hex edit CIDs with 3 different fastboot CIDs and these are the results:
The fastboot CIDs will be listed under the Hex ones that I tried. I'll put Yes if Google Keyboard worked and No if it FC'ed
Hex = CWS__001 (AT&T)
Fastboot CWS__001 - Yes
Fastboot 11111111 - Yes
Fastboot HTC__001 - No
Hex = HTC__001 (WWE)
Fastboot CWS__001 - Yes
Fastboot 11111111 - No
Fastboot HTC__001 - No
Hex = 11111111 (supercid)
Fastboot CWS__001 - Yes
Fastboot 11111111 - Yes
Fastboot HTC__001 - No
There have been quite a few posts that say there is no need to change the CID value (hex edit) in mmcblk0p19 but obviously it has some effect on at least one app. Also if you make your CID supercid through fastboot and your mmcblk0p19 is AT&T then the LTE icons are stock AT&T which is also true if you make mmcblk0p19 supercid and fasboot CID AT&T.
Can someone with more knowledge try to make sense of this? How come Google Keyboard won't work with anything HTC_001? I've done a full wipe and everything.
FWIW I'm using an AT&T HTC One. I flashed the Droid DNA eng-hboot and changed my model ID to PN0710000. After that I flashed back the 1.44 hboot from the One. I then changed my CID in both places to HTC__001 and flashed the 2.17 FW that mike posted.
Click to expand...
Click to collapse
I've never had a google keyboard FC, and i've tried all of the cids you've mentioned with fastboot oem writecid. Maybe no one else has either, hence the lack of replies? Of course i've never hex edited any cid location so thats probably why. This looks to me like another reason NOT to hex edit, no errors when just doing fastboot cid.

I replied to the last thread!
Sent from my HTC One using xda premium

SkizzMcNizz said:
Ok so since I didn't get an answer in the Q&A section (126+ views) I figured I'd try a few things. I noticed the other day when I switched my CID to HTC__001 from CWS__001 when I rebooted I got a Google Keyboard FC. So I went through and tested 3 Hex edit CIDs with 3 different fastboot CIDs and these are the results:
The fastboot CIDs will be listed under the Hex ones that I tried. I'll put Yes if Google Keyboard worked and No if it FC'ed
Hex = CWS__001 (AT&T)
Fastboot CWS__001 - Yes
Fastboot 11111111 - Yes
Fastboot HTC__001 - No
Hex = HTC__001 (WWE)
Fastboot CWS__001 - Yes
Fastboot 11111111 - No
Fastboot HTC__001 - No
Hex = 11111111 (supercid)
Fastboot CWS__001 - Yes
Fastboot 11111111 - Yes
Fastboot HTC__001 - No
There have been quite a few posts that say there is no need to change the CID value (hex edit) in mmcblk0p19 but obviously it has some effect on at least one app. Also if you make your CID supercid through fastboot and your mmcblk0p19 is AT&T then the LTE icons are stock AT&T which is also true if you make mmcblk0p19 supercid and fasboot CID AT&T.
Can someone with more knowledge try to make sense of this? How come Google Keyboard won't work with anything HTC_001? I've done a full wipe and everything.
FWIW I'm using an AT&T HTC One. I flashed the Droid DNA eng-hboot and changed my model ID to PN0710000. After that I flashed back the 1.44 hboot from the One. I then changed my CID in both places to HTC__001 and flashed the 2.17 FW that mike posted.
Click to expand...
Click to collapse
I have an ATT One with SuperCID from fastboot oem and the hex edit in mm, and have never had a google keyboard FC.

I Have HTC_001 and I get FC's too. Ive tried 2 different roms, wiped and started fresh each time, including installig the keyboard first, but no dice. Constantly fc's. Only on 4.2.2 though, it worked fine before I upgraded...

To those getting FC's :
have you cleared cache & data for the Keyboard every time you changed CID/ROM's?
If not try it & post results. May be just some basic cache/ app data problem.

Tried that numerous times, still no luck...
x017in said:
To those getting FC's :
have you cleared cache & data for the Keyboard every time you changed CID/ROM's?
If not try it & post results. May be just some basic cache/ app data problem.
Click to expand...
Click to collapse

Posted in the other thread as well. Had issues with the HTC__001 cid as well. Changed it to the US Dev edition and now it works fine. I have done no hex editing. U

nugzo said:
I've never had a google keyboard FC, and i've tried all of the cids you've mentioned with fastboot oem writecid. Maybe no one else has either, hence the lack of replies? Of course i've never hex edited any cid location so thats probably why. This looks to me like another reason NOT to hex edit, no errors when just doing fastboot cid.
Click to expand...
Click to collapse
Download the official Google Keyboard and then change your CID to HTC__001 and reboot to see if it FC'S.
I never would have changed my CID through hex edit but I saw a post saying that we needed to and it wasn't until after I did it that other people started posting saying that person was wrong. =/
It shouldn't matter though because I changed it back to what it was. And like I said the hex edit also affects the LTE icons whether you have supercid or not. I wish there was a way to go completely back to stock. Something that wrote the mmcblk0p19 to what it was originally become any edits.
P.S. I've only tried this on ARHD 10.2. Had anyone who had this happen been on a different rom?
Sent from my HTC One using xda app-developers app

spitfire2425 said:
I replied to the last thread!
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Not before I posted this lol.
Sent from my HTC One using xda app-developers app

x017in said:
To those getting FC's :
have you cleared cache & data for the Keyboard every time you changed CID/ROM's?
If not try it & post results. May be just some basic cache/ app data problem.
Click to expand...
Click to collapse
Yes tried everything, full wipe, etc.
Sent from my HTC One using xda app-developers app

i dont get how changing the CID affects the apps, is it something to do with detecting regions?

I guess maybe i'm confused about the official google keyboard. i thought the keyboard you spoke of was what comes with the rom, i'll check the download version.

just go ahead and change the MID as well. with ENG-hboot. super cid is just doing half the job. no fc's ever converted AT&T to HTC__001 and changed MID to PN0710000. full wipe and RUU install

ATT htc one with supercid from fstbvoot and bs_us001 hexeditied and no google keyboard issues. I am on android revoluition hd 10.3.

tjsooley said:
ATT htc one with supercid from fstbvoot and bs_us001 hexeditied and no google keyboard issues. I am on android revoluition hd 10.3.
Click to expand...
Click to collapse
Its only HTC__001.
Sent from my Nexus 7 using XDA Premium HD app

daddioj said:
just go ahead and change the MID as well. with ENG-hboot. super cid is just doing half the job. no fc's ever converted AT&T to HTC__001 and changed MID to PN0710000. full wipe and RUU install
Click to expand...
Click to collapse
I did it says that in the OP.
Sent from my Nexus 7 using XDA Premium HD app

Off topic: I have HTC_001 and haven't changed my CID but I have noticed if I use any other theme apart from the stock AOSP theme the keyboard becomes transparent. Am using rootbox

I don't know I don't have any of these issues. when I did have ENG hboot. I wiped the phone completely from the radio to the recovery then flashed RUU

daddioj said:
I don't know I don't have any of these issues. when I did have ENG hboot. I wiped the phone completely from the radio to the recovery then flashed RUU
Click to expand...
Click to collapse
Have you switched your CID to HTC__001, downloaded the Official Google Keyboard, and tried to open it?
If you haven't done exactly that then please don't post saying it's not happening to you.
Sent from my HTC One using xda app-developers app

CWM / TWRP and Rom

if you search CWM or TWRP or Backup from Rom look on this Page
HTC-Desire-626G-Development
There is also a description for SuperSU

How much R these phones?; could u use it any phone company??
How much R these phones?; could u use it any phone company?? ?:silly:

Joolie ah Gross said:
How much R these phones?; could u use it any phone company?? :silly:
Click to expand...
Click to collapse
You can get them for around 80$usd. It is unlockable out if the box but you may have to take it to a metro/T-Mobile store to help you with that. But it should work with any gsm carriers for the most part (at&t/T-Mobile/cricket/metro/etc.)

Htc 626 a32_ul boot.img
i soft bricked my phone and downloaded many boot and recovery images and roms and ruu trying to fix my htc626 a32_ul qualcomm 410 type phone , been nightmare that looked impossible to fix and waiting here trying find a root or fix have learnt a lot about andriod these last few weeks
anyway did realise that after learning what i should be looking for i knew it should be in file named
0PKXIMG_A32[email protected]50720.2C_17.00_018_F_release_446349_combined_signed.zip
source found at IR-file.com
my htc 626 phone gehtc version all gives output of :-
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.02.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CC592YM02455
(bootloader) imei: ***************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a32_ul
(bootloader) platform: hTCBmsm8916
(bootloader) modelid: 0PKX20000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: b7436e99
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 1001
bootloader is unlocked
a32_ul pvt ship s-on
i installed your rom onto sd-micro card, then when booting into bootloader i get the rom installing
but get this inforamtion onscreen showing image update fail saying no image or wrong image
sd checking...
no gift file...
loading...(0PKXDIAG.zip)
No image!
loading...(0PKXDIAG.nbh)
no image or wrong image !
loading...(0PKXIMG.zip)
....
....
....
Device halted due to large Image update fail
Press <POWER> to reboot.
!! Image Update FAIL !!
then when I unzipped file and took out boot_signed.img
used htc_fastboot flash boot boot_signed.img then rebooted phone
its alive im back in stock :laugh::laugh::laugh:
boot.img used here [
htc fastboot files used
is such a relief to have my phone back up and working still not rooted but working in stock firmware hope this post may help any other lost souls in the soft bricked nightmare lol
oh dea
o prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
i have link to files but unable to post till 10 posts
regards from Frankgambit

i have boot img for anyone who wants it darn this s-on htc thing what pain in neck for ppl i still want root but now phone up and running again i can wait for definite solution to be found and now free to experiemnt now as i have fail safe repair any eorrors that may cause soft brick now.
---------- Post added at 10:03 PM ---------- Previous post was at 09:41 PM ----------
frankgambit said:
i have boot img for anyone who wants it darn this s-on htc thing what pain in neck for ppl i still want root but now phone up and running again i can wait for definite solution to be found and now free to experiemnt now as i have fail safe repair any eorrors that may cause soft brick now.
Click to expand...
Click to collapse
also another thing is if i brought a 8 gb htc 626 then i assume the free space left on phone would be say 3gb on main internal memory left to use.
so i pay for 16 gb and what do i get not a lot more than before and still only 6 or 7 gb free space on phone after bloat-ware , unable to remove or move such bloat-ware and other apps to external sd card until find method for root
this seems like a recurring makers inbuilt problem caused by manufacturers same like when ibm chose the memory size of first pc so to maximise profit selling 16 kb chips, then cpu need for access to ever larger memory space made there original model impracticable. i think this is deliberate so that they can sell there top end phones with loads internal memory at more higher price. what i would like in phone is phone with 2 sd slots one slot for etreme sd card double port for application to run from or store , and then another sd card for media files for audio or films and pictures to be stored on and of as largest size possible but maybe not so fast if price of speed or data transfer over size consideration.
i see *exception in specs htc626 could use 2 TB of storage space but is limited to 128 gb by operating system of android 5.1 , and yet see maybe android 6.0 maybe allows up-to 512 gb.
root is only way cure this bloatware problem for now and yet even so i have paid for my hardware i am not allowed to make full use of the hardware by restrictions placed on my phone by the manufacturer desire to force me to buy the more expensive models. that have more free internal memory.

i was going to wait till monday before attempting too root phone, but now i feel safer in that i can recover phone from soft brick possibility , i have decided to go through all the one click apps again that i tried using blindly before ,, but now with eyes wide open to the possible pitiful and knowledge i can recover to stock boot again . lets go again as the gains from having rooted device far out weighs the drawbacks of having useless unrooted device as far as i am concerned.

frankgambit said:
i was going to wait till monday before attempting too root phone, but now i feel safer in that i can recover phone from soft brick possibility , i have decided to go through all the one click apps again that i tried using blindly before ,, but now with eyes wide open to the possible pitiful and knowledge i can recover to stock boot again . lets go again as the gains from having rooted device far out weighs the drawbacks of having useless unrooted device as far as i am concerned.
Click to expand...
Click to collapse
you have to relock your device on fastboot to be enable to restore with RUU, belive me, i did the same with a M&, ne max and one 626s, i was like crazy why got error until i found that relocking bootloader then I was able to restore with RUU in some minutes.!