Develop Bugs

[Q] Can't flash splash please help...

I tried to flash a new splash using android flasher 1.6.1 and it didn't worked out.
I tried to do it using ADB and it's write to me :
sending 'splash1' (750KB)...
OKAY [0.118s]
writing 'splash1'...
FAILED (remote:not allowed)
finished.total time 0.119s
I am using Cyanogen7 ROM and I have S-OFF :
BRAVO PV4 SHIP S-OFF
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.09.05.30_2
Can please someone help me ?

fastboot flash?

ghalalb said:
fastboot flash?
Click to expand...
Click to collapse
yes
Im trying to change the splash picture.

sorry, I should have explained myself, have you flashed from fastboot or adb only? I'm sure you have to do it from fastboot not adb, there is a tut on here somewhere, but i can't find the link for it
could try this method though i've not
http://forum.xda-developers.com/showthread.php?t=794638
AmonRa 2.0.1 | PVT4 40000 S-Off Alpharev 1.8| HBoot 0.93.1000 | Radio 5.17.05.08 | LeeDroid 3.0.2 (A2SD) | HTC Desire A8181 | UOT Kitchen Mods

found the method I used
http://forum.xda-developers.com/showthread.php?t=795132&highlight=fastboot+flash+splash1
AmonRa 2.0.1 | PVT4 40000 S-Off Alpharev 1.8| HBoot 0.93.1000 | Radio 5.17.05.08 | LeeDroid 3.0.2 (A2SD) | HTC Desire A8181 | UOT Kitchen Mods

That method worked for me too, nice

I tried to do it with fastboot ,still don't work for me.
it says it's all done but nothing happends.
I also tried to do the S-OFF again and it give me the next error:
waiting for your device... FOUND!
Identifying your phone:
Device model: PB992
CID: 11111111
MID: PB992
HBOOT version: 0.93.0001
Screen type:
Your phone was not recognized or is unsupported at this time.
If you are 100% sure your phone type should be supported in this version,please note the Model ID displayed.
Powering off in 60 seconds.
I dont understand what's wrong ?

I use android flasher. Its damn easy for noobs. I'm not a noob, but I'm lazy enough to use it.

I have also tried with Android Flasher but still doesn't work...

kleinyair said:
I tried to do it with fastboot ,still don't work for me.
it says it's all done but nothing happends.
I also tried to do the S-OFF again and it give me the next error:
waiting for your device... FOUND!
Identifying your phone:
Device model: PB992
CID: 11111111
MID: PB992
HBOOT version: 0.93.0001
Screen type:
Your phone was not recognized or is unsupported at this time.
If you are 100% sure your phone type should be supported in this version,please note the Model ID displayed.
Powering off in 60 seconds.
I dont understand what's wrong ?
Click to expand...
Click to collapse
I think, you should write this problem on irc.freenode.net, channel #alpharev
Don't know what's the problem, but think the guys from alpharev-team could help here...
Sent from my HTC Desire using XDA App

anderl78 said:
I think, you should write this problem on irc.freenode.net, channel #alpharev
Don't know what's the problem, but think the guys from alpharev-team could help here...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
How do I use the IRC ?
I tried to write it in my exlorer,didn't go nowhere.
I'm sorry I'm quite new here.

And your fastboot/hboot does say something like aplpharev on the top? If that is the case it will also work if you do it right when booted into fastboot. I might be able to guide you through it.
If that is not the case, something is wrong, and you will need to run alpharev again.
I also dont get how your cid can be 11111111, as that definitely does not look right. Try booting to fastboot and run "fastboot oem boot" and write the cid it throws out it should be something like HTC_Y13

mortenmhp said:
And your fastboot/hboot does say something like aplpharev on the top? If that is the case it will also work if you do it right when booted into fastboot. I might be able to guide you through it.
If that is not the case, something is wrong, and you will need to run alpharev again.
I also dont get how your cid can be 11111111, as that definitely does not look right. Try booting to fastboot and run "fastboot oem boot" and write the cid it throws out it should be something like HTC_Y13
Click to expand...
Click to collapse
My hboot doesn't say nothing about alpharev i got it allready s-off from the store,thats what it write on my hboot:
BRAVO PV4 SHIP S-OFF
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.11.05.14
I run fastboot oem boot and this is the reasult:
I will very appreciate if you could please help me.

Try the alpha rev s-off method (bootcd) then try again with the gui tool

isit-LoVe said:
Try the alpha rev s-off method (bootcd) then try again with the gui tool
Click to expand...
Click to collapse
I have allready tried with alpharev bootcd and it gave me:
waiting for your device... FOUND!
Identifying your phone:
Device model: PB992
CID: 11111111
MID: PB992
HBOOT version: 0.93.0001
Screen type:
Your phone was not recognized or is unsupported at this time.
If you are 100% sure your phone type should be supported in this version,please note the Model ID displayed.
Powering off in 60 seconds.
what do you mean gui tool ?

seems like your phone uses an alternative s-off method or its just faking S-OFF (only displaying it on screen)
i googled for about 15 mins and found this: http://4pda.ru/forum/index.php?showtopic=180832&st=12640#entry6668455
use google language translator for other language
When you try to get the S-OFF:
identifying your phone:
Device model: PB992
CID: 11111111
MID: PB992
HBOOT VERSION: 0.93.0001
SCREEN TYPE:
Your phone was not recognized or is unsuported at this time.
Have:
BRAVO PVT4 SHIP S-OFF
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.14.05.17
Aug 10, 2010 17:52:18
Telephone gray, root mean.
Beat 3 months, finally found the solution:
when alpharev gives Your phone was not recognized or is unsuported at this time.
disable the phone from the wire
Hit Ctrl + C
see $
write vi alpharev.sh Hit Enter
cursor down to 117 lines, where it is written PB9920000 remove zeros that would get PB992
Hit Shift colon and write wq
see $
write. / alpharev.sh
process will start again on the instructions of obtaining s-off
ps. sewed with flash
Click to expand...
Click to collapse
gui tool i mean android flasher but after you successfully flashed with alpha rev :/

I tried the process,I changed the PB9920000 to PB992 but I dont understand what is that mean :"Hit Shift colon and write wq"
what is shift colon ?
Edit :O.K I figured it out !!!!
after I changed the num to PB992 I pushed Shift+Z
and I wrote :" ./ alpharev.sh "and Enter
It start all over from the begining and its all working good now.
Thank you very much...

His phone is s-off alright, but it has somehow been delivered that way, so you have got a phone, which were meant for development or a store demo device(have seen the same issue on store demo devices).
The problem is, that this is real s-off, which means it's set by a flag on a low level of the nand, so he still has the original bootloader, which doesn't support fastboot commands. And because it's a development device it's got cid 11111111, which is wrong and makes alpharev recognize it as a different/non existing device. You should be able to flash it in another way because as you are s-off, you can make the recovery ask the bootloader to flash low level stuff like splash, and the bootloader is s-off, so it shouldn't check for anything. You might need some specialist aka the ones from alpharev though if they are interested in helping you.
edit: As it is s-off it might very well be able to flash one of the pb99img.zip files containing the alpharev hboot found on the alpharev site because it will accept them as if they were from HTC, so just put them on the sd-card with the right name and reboot to the bootloader. This way you might be able to activate fastboot commands, and start flashing the same way we do. This requires that those images will work normally on your phone, so i would still ask the alpharev guys so you don't risk a brick.

i agree with mortenmhp asking alpharev is probably the best idea
shift colon is probably :
in the editor vi you use ":wq" to tell the programm to save stuff and exit the editor

How can I make contact with alpharev ?
I didn't understant how to use the IRC...

unrevoked failed half way through

A couple of weeks ago I tried to apply the 'one touch' unrevoked tool, and whilst the phone rebooted a couple of times and all seemed to be working well, it eventually froze.
I left it for over an hour with no progress:
Code:
[email protected]:~/Downloads$ ./reflash
unrEVOked recovery reflash tool
git version: 8b5c9e4
ERROR: n = -1, errno = 19 (No such device)
ERROR: n = -1, errno = 19 (No such device)
Now, since I can see the phone with fastboot:
Code:
[email protected]:~/Downloads$ sudo ./fastboot devices
HT09JPL00xxx fastboot
(last 3 digits of serial xxx'd out)
I tried to install an RUU in Windows whose operator+radio match ( RUU_Bravo_Froyo_TMO_UK_2.12.110.4_R_Radio_32.49.00.32U_5.11.05.27_release_157560_signed.exe ) but it fails at the 'RADIO_V2' flash stage.
Code:
Parsing...[downloaded ZIP]
[1] USERDATA - OK
[2] RADIO_CUST - OK
[3] RECOVERY - OK
[4] BOOTLOADER - OK
[5] SPLASH1 - OK
[6] BOOT - OK
[7] RADIO_V2 - Fail-PU
[8] SYSTEM - OK
[9] SPLASH2 - OK
Partition update fail!
Update fail!
When I boot the phone i get the 'htc' logo with exclamation marks in each corner.
I can get into hboot OK with Power + Volume down which shows this:
Code:
BRAVO PVT3 SHIP S-ON
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010.17:52:18
The installed Android OS is corrupted, so if I run "fastboot oem boot" I see a pink circle with an arrow (same shade as the T-Mobile pink...) and then the phone vibrates briefly 7 times.
Code:
[email protected]:~/Downloads$ sudo ./fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E07F9F0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x0
INFOTAG:skuid 0x26A0D
INFOTAG:hero panel = 0x3
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is T-MOB005
INFOsetting->cid::T-MOB005
INFOserial number: HT09JPL00xxx
INFOcommandline from head: no_console_suspend=1
INFOcommand line length =418
INFOactive commandline: board_bravo.disable_uart3=0 board_bravo.
INFOusb_h2w_sw=0 board_bravo.disable_sdcard=0 diag.enabled=0 boa
INFOrd_bravo.debug_uart=0 smisize=0 userdata_sel=0 androidboot.e
INFOmmc=false androidboot.baseband=5.11.05.27 androidboot.cid=T
INFO-MOB005 androidboot.carrier=TMUK androidboot.mid=PB9920000 a
INFOndroidboot.keycaps=qwerty androidboot.mode=normal androidboo
INFOt.serialno=HT09JPL00905 androidboot.bootloader=0.93.0001 no_
INFOconsole_suspend=1
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFOmpu_nand_acpu_rw A1E 1000
INFOjump_to_kernel: machine_id(2457), tags_addr(0x20000100), ker
INFOnel_addr(0x20008000)
INFO-------------------hboot boot time:279875 msec
How can I get some kind of working system back again? Am not bothered if it's rooted or not - I'd just like a working phone

try another RUU, try my guide for some other help

Try Bortak's guide - very nice and useful. And BTW this question is answered a couple (dozen) times.
Sent from my customized HTC Desire using TTP

Thanks for the tips,
I had no doubt this problem had come up before; the terminology is just a little overwhelming - I'll work through bortak's guide.
Is it possible to make a goldcard even when there's no usable Android on the phone? (i.e. can't select USB Debugging for 'adb shell')

yup http://jo0ls-dotnet-stuff.blogspot.com/2008/12/read-secure-digital-sd-card-serial.html use this to get the CID of the sd-card (copy down without commas, spaces) then follow this tut http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/ after they get the CID of the sd-card through the phone (the step you're skipping)

Heh, I've been having fun with this to no end result.
All the Micro-SD's I have are SanDisk which came with previous phones (I am using a 1GB for the gold card)
Tried the full manual process for creating the gold card, reversing the bytes manually, pasting the goldcard.img using hex editor, etc. but when I pop that card in the phone and launch the latest WWE RUU
http://www.mirrorcreator.com/files/0FVU0Y7T/RUU_Bravo_Froyo_HTC_WWE_2_29_405_5_Radio_32_49_00_32U_5_11_05_27_release_159811_signed.exe_links
I still get a CID error. The only RUU I've been able to get to start properly is http://www.shipped-roms.com/download.php?category=android&model=Bravo&file=RUU_Bravo_Froyo_TMO_UK_2.12.110.4_R_Radio_32.49.00.32U_5.11.05.27_release_157560_signed.zip
and that one gives the 'Fail-PU' at the RADIO_V2 stage.
So I then found this: http://www.addictivetips.com/mobile/how-to-easily-create-gold-card-for-htc-desire-without-hex-editing/ and I've included screenshots showing the CID + webpage where I downloaded the goldcard.img
I put the 1GB card into my main phone, a Desire S in order that the Gold Card Tool could run 'adb shell' commands
Even after all that, the WWE RUU still failed with a CID error
What am I doing wrong?

don't use the goldcard tool, use the tut I showed you.. it worked for me..

Hullo again - I've returned and have a little more success - the Goldcard creation worked this time - must've messed something up first time round.
Now I'm able to launch the WWE RUU without CID errors.
I am using: RUU_Bravo_Froyo_HTC_WWE_2_29_405_5_Radio_32_49_00_32U_5_11_05_27_release_159811_signed.exe
Unfortunately, the core problem still exists... when the RUU gets to RADIO_V2 step, it still shouts "Fail-PU" in red letters.
I'm beginning to wonder if there's a hardware fault on this handset even tho it worked before I started messing with ROMs; is there anything else I can try?

gdhgdh said:
Hullo again - I've returned and have a little more success - the Goldcard creation worked this time - must've messed something up first time round.
Now I'm able to launch the WWE RUU without CID errors.
I am using: RUU_Bravo_Froyo_HTC_WWE_2_29_405_5_Radio_32_49_00_32U_5_11_05_27_release_159811_signed.exe
Unfortunately, the core problem still exists... when the RUU gets to RADIO_V2 step, it still shouts "Fail-PU" in red letters.
I'm beginning to wonder if there's a hardware fault on this handset even tho it worked before I started messing with ROMs; is there anything else I can try?
Click to expand...
Click to collapse
Yeah your phones bircked, radio fail is unfixable.
Before you send off for warranty use the 2.3.3 RUU.

Oh poo
No chance with warranty - this phone is well over a year old.. ah well I'll drop it in the 'box of fail' at work

gdhgdh said:
Oh poo
No chance with warranty - this phone is well over a year old.. ah well I'll drop it in the 'box of fail' at work
Click to expand...
Click to collapse
hah, sorry dude... hmm try the 2.3.3 RUU a couple of times and hope for a miracle

Hm, I tried this one last time and the WWE ROM successfully installed - all 9 partitions were 'OK' - maybe it's a heat problem since I powered on, used the PB99IMG.zip method on the SD card, and it flashed first time!
So, now HBOOT + FASTBOOT are both working again, but the device is stuck on white screen with green 'htc' logo. Sometimes it will vibrate 7 times.
I've read the 'ADVANCED BOOT PROBLEMS' in section 2 of your guide for S-ON devices.. and it looks like the only hope is to keep flashing the WWE ROM and hope that the phone just magically starts to boot - is that right?

Ha! Continuing in the spirit of 'one last time', I powered it on again, went to get a drink and heard the 'chimes'.. and sure enough the phone was booting OK - I got through the choose Country / wifi setup wizard, saw a moment of the HTC Sense home screen and the phone rebooted again to the htc static logo
I conclude this phone has a bad hardware problem and I won't be wasting any more time on it.
Many thanks for your time + advice

[Q] Unrooting Desire Z

I'm trying to unroot my dad's Desire Z, but I'm stuck at some problem.
I first tried to use the guide for removing permaroot, but I ended up with a G2 ROM, what I obviously don't want.
So I rooted it again, flashed a new Sense ROM and tried to run a RUU, but it just after I pressed update, it pops up "Image error [158]".
Could someone please tell me what I'm doing wrong?
Thanks in advance

When you unrooted it the ruu applied was for a g2. After rerooting did you get soff? Custom recovery? Is the new ruu your trying to flash for the dz?
Sent from my HTC Vision using xda premium

I indeed flashed a PC10IMG.zip which was meant for a G2.
Now I have regained S-off, Root access (and a custom recovery) and I'm trying to flash a HTC_WWE RUU from shippedroms.com but none of them I tried seem to work. Do I have to pack one matching some system version number?
EDIT: I'm trying to flash an appropriate PC10IMG.zip, found here. But if I extract the .zip and look in the android-info.txt file, the only allowed CID's are all starting with HTC__***, and mine is obviously 11111111 aka super CID. Could this be the problem?
I tried changing my CID using gfree, but it returns this code:
Code:
# ./gfree -c HTC__E10
./gfree -c HTC__E10
--cid set. CID will be changed to: HTC__E10
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.35.14-cyanogenmod-g9e5cdf1
New .modinfo section size: 216
Attempting to power cycle eMMC... Failed.
Module returned an unknown code (No such file or directory).
#
Some info:
Radio: 26.02.01.15_M2
HBOOT: 0.84.2000 (PC1011000)
Currently running CM7.1.0

You should check the md5sum of the download if you can, sounds like it might be corrupt.
Because with supercid and s-off, the allowed cid values of the rom.zip don't matter
Also, you may want to check out my unrooting guide: http://forum.xda-developers.com/showthread.php?t=1442988
-Nipqer

I tried your guide, checked the md5, which was correct, but I keep getting this error when I flash the zip via adb and fastboot-windows.exe:
Code:
C:\Root 2>fastboot-windows flash zip DZ_PC1
Sending 'zip' (288060 KB)... OKAY
Writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 22 loading zip info fail)
EDIT: I realized there is no SIM card inserted, does this matter? Just to be sure

No the sim card shouldn't affect it.
It's probably the flashing a dz rom over a g2 hboot thats the issue.
Maybe you should try this http://www.virtuousrom.com/2011/06/t-mobile-g2-users-migrating-to-desirez.html first to give you the dz hboot, then you should be able to flash the dz rom
-Nipqer

Didn't work, still getting the same error...
Tried and RUU which pops up error no. 159 "Image Error", try finding the right RUU.

You can find all the roms/ruu's here http://www.shipped-roms.com/index.php?category=android&model=Vision
-Nipqer

[?] Can't flash the HTC EU ROM because of CID

I've searched the forum and Google high and low to solve this and have come up with the following:
1. Running the RUU. Result: "Wrong customer" error.
2. Grabbing rom.zip from RUU temp files, renaming PK76IMG.zip, flashing from bootloader. Result: No dice.
3. Repeat step 2 on a Goldcard. Tried MMC0 and MMC2 (GoldCard generator got errors with MMC1). Result: "CID incorrect! Update Fail!"
4. Flashing zip from command line as follows:
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip rom.zip
Result: "CID error"
5. Relocking bootloader and repeating #4. Result: same.
6. Change CID as follows: fastboot oem writecid HTC__001. Result: COMMAND ERROR!
7. Downloaded various other fastboot.exe and re-run step 6. Result: COMMAND ERROR!
8. Flashing with fastboot: fastboot flash system system.img. Result: "FAILED (remote: data length is too large)." This one boggles me because the extracted system.img for the HTC UE ROM (what I'm trying to flash) is identical to the HTC Asia ROM (what I have).
9. What's your idea???????
BTW, can I replace the android-info.txt in the HTC EU ROM with the one from the HTC Asia ROM without negative ramifications?

Bump.

So using Goldcard and flash RUU also not working ?
I used to use Goldcard to flash RUU which is not meant for my Desire before.

Thread moved to Q&A.
Sent from my Galaxy Note (i717), using XDA Permium.
•••••••••••••••••••••••••••••••••••••••••••••••••
XDA Rules:
http://forum.xda-developers.com/announcement.php?a=81
Ten post rule:
http://www.xda-developers.com/android/10-post-rule-explained/
Marketplace Rules (updated):
http://forum.xda-developers.com/announcement.php?f=476

ckpv5 said:
So using Goldcard and flash RUU also not working ?
I used to use Goldcard to flash RUU which is not meant for my Desire before.
Click to expand...
Click to collapse
Yes. The same works for Wildfire S. But to change my Wildfire S from Asian to European I ultimately had to flash from fastboot.
I only tried MMC0 so I'm going to try MMC1 and MMC2 next.

I tried MMC1 and MMC2 tonight.
MMC1 didn't work. SimpleGoldCard.exe reported errors and couldn't produce the GoldCard.
MMC2 produced a different CID and successfully generated a GoldCard, but the install failed again: "CID incorrect! Update Fail!"
Any ideas? It can't be impossible to do this!

When we connect our phone as usb drive, with sdcard inserted, there are two removable storage, so patch the sdcard alone with the goldcard won't work as the other is not patched. Anyway this is my guess only.

Delete.

My next approach to changing to CID to the Super CID comes from the AT&T One X forum:
[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev
Thoughts???

CafeKampuchia said:
My next approach to changing to CID to the Super CID comes from the AT&T One X forum:
[UNLOCK] AT&T Bootloader Unlock Through HTC-Dev
Thoughts???
Click to expand...
Click to collapse
Any idea what is mmcblk0p4 referring to ? As we know for one v, our dev/block is numbered differently.

Actually, I don't. I don't think retrieving this block is going to work on the One V, but the method he used will. He found the block containing the CID by searching a dump. I don't (yet) know how to do that.

CafeKampuchia said:
Actually, I don't. I don't think retrieving this block is going to work on the One V, but the method he used will. He found the block containing the CID by searching a dump. I don't (yet) know how to do that.
Click to expand...
Click to collapse
Hi,
I'm trying to figure out how to do the same thing. I can't revert to stock because I have a One V on Three, and the radio is a later version than the RUU online. I found a similar guide to changing the CID on a One S that you did:
http://forum.xda-developers.com/showthread.php?t=1674202
This thread shows how to look at the contents of those blocks:
http://forum.xda-developers.com/showthread.php?t=1694700
And this one gives the purpose of each partition, at least for the primoc, probably same for primou:
http://forum.xda-developers.com/showthread.php?t=2156415
I wrote a BASH script to search through the blocks for a given bit of text, which you can use if you're on Linux by making sure it has execute permission, and running it with the search string (change .txt to .sh if you like). For my CID (H3G__001), I used ./findinblock H3G__001. It is case sensitive. I found my CID in partitions 7, 18, 23, 25 & 26.
Maybe 7 is the one to change. I'm not sure I'm quite ready to just blindly experiment, even if it may be possible to revert. I wonder if someone more experienced can weigh in?

I tried overwriting the CID in mmcblk0p7 but it didn't "take":
Code:
C:\adt-bundle-windows-x86\sdk\platform-tools>adb shell
[email protected]:/ # strings -n 8 /sdcard/mmcblk0p7MOD
strings -n 8 /sdcard/mmcblk0p7MOD
HTC__001
<snip>
[email protected]:/ # strings -n 8 /dev/block/mmcblk0p7
strings -n 8 /dev/block/mmcblk0p7
H3G__001
<snip>
[email protected]:/ # dd if=/sdcard/mmcblk0p7MOD of=/dev/block/mmcblk0p7
dd if=/sdcard/mmcblk0p7MOD of=/dev/block/mmcblk0p7
4096+0 records in
4096+0 records out
2097152 bytes transferred in 0.393 secs (5336264 bytes/sec)
[email protected]:/ # strings -n 8 /dev/block/mmcblk0p7
strings -n 8 /dev/block/mmcblk0p7
H3G__001
<snip>
Perhaps using a goldcard would help. I've only ever done this putting the goldcard directly in the phone. In this case we'd need to use a Y cable to allow a working sdcard in the phone (unless you can store the modded CID partition somewhere else) and I don't have the hardware to hand.
Can anyone else help?

Ok, I tried this with a gold card, sorting this modified block in internal storage instead of SD card. Still no joy.
Sent from my Nexus 7 using XDA Premium HD app

>_<''
Hey everyone
I got the same Problem.
I've found my CID, which is O2___102, on partition 7, 18, 23, 29 and 32.
I made some screenshots of it.
Maybe anyone can help.
P.S.:
Does anyone now the filesize of the mmcblk0p4 partition of the AT&T One X??
Maybe this information can be helpful
- greetings, animeryumyu
EDIT:
I just find out, that the needed partition for modding is the bootloader itself.
At least I read it in the "how to SuperCID" for the HTC One SV (K2_U / K2_UL)
For the One SV it is the same partition as for the AT&T One X.
And before the CID and IMEI of both, the X and the SV is a little text that reads "HTC-BOARD-INFO!".
Maybe this is important to.
Does anyone now any other indicators to find out, which partition is the bootloader??
Maybe, when we get SuperCID, we are one step closer to S-OFF our device

[Q] Badly Need youre help T_T

HTC WILDFIRE S A3333
BUZZ PVT SHIP S-ON
HBOOT-1.01.0002
MICROP-0622
TOUCHPANEL-ATMELA224_16ab
RADIO-3.35.20.10
i tried all the method to down grade to 1.01.0001 i also tried buzzdowngrade but still no good result
it work perfectly i follow every steps but still did not down grade my hboot i really nid some help thank you in advance
btw my gold card generator is this hxxp://huygens.hoxnet.cm/goldcard.html :crying:

OLOKS402 said:
HTC WILDFIRE S A3333
BUZZ PVT SHIP S-ON
HBOOT-1.01.0002
MICROP-0622
TOUCHPANEL-ATMELA224_16ab
RADIO-3.35.20.10
i tried all the method to down grade to 1.01.0001 i also tried buzzdowngrade but still no good result
it work perfectly i follow every steps but still did not down grade my hboot i really nid some help thank you in advance
btw my gold card generator is this hxxp://huygens.hoxnet.cm/goldcard.html :crying:
Click to expand...
Click to collapse
Did you try running the bat files as a admin (ie right click and run as administrator) also do you get any errors
when running the files ? (please post errors) Also post your cid number and i will make a new goldcard just in case thats the problem

huhu
matter1 said:
Did you try running the bat files as a admin (ie right click and run as administrator) also do you get any errors
when running the files ? (please post errors) Also post your cid number and i will make a new goldcard just in case thats the problem
Click to expand...
Click to collapse
CID: 00B1004C58AC021030303030304D531B
if i run as admin the there are errors.:
'adb' is not recognized as an internal or external command,
operable program or batch file.
i search about that it says dont run as admin
step 1 results :
Press enter to start.
511 KB/s (655360 bytes in 1.250s)
690 KB/s (419822 bytes in 0.593s)
572 KB/s (357080 bytes in 0.609s)
*** Getting temproot ***
property service neutered.
killing adbd. (should restart in a second or two)
*** Downgrading MISC ***
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
*** Step 1 is done, continue with Step 2. ***
*** Create a goldcard with the GoldCardTool first!
CID: 00B1004C58AC021030303030304D531B
Executing adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
Reading adb output
------------------------
adb server is out of date. killing...
* daemon started successfully *
1b534d30303030301002ac584c00b10e
------------------------
CID: 1B534D30303030301002AC584C00B10E
Reversing CID
CID: 00B1004C58AC021030303030304D531B
after i create gold card i patched it and the results are
------------------------
CID: 1B534D30303030301002AC584C00B10E
Reversing CID
CID: 00B1004C58AC021030303030304D531B
Loaded D:\Documents\Downloads\goldcard(1).img
Reading sector 0 of DriveG:
Converting to GoldCard Sector
Writing sector 0 of DriveG:
Validating sector 0 of DriveG:
Writing sector 0 of DriveG: Success
and after the reboot stil the same notjing has change on my hboot still
HTC WILDFIRE S A3333
BUZZ PVT SHIP S-ON
HBOOT-1.01.0002
MICROP-0622
TOUCHPANEL-ATMELA224_16ab
RADIO-3.35.20.10
:crying::crying::crying:

OLOKS402 said:
CID: 00B1004C58AC021030303030304D531B
if i run as admin the there are errors.:
'adb' is not recognized as an internal or external command,
operable program or batch file.
i search about that it says dont run as admin
step 1 results :
Press enter to start.
511 KB/s (655360 bytes in 1.250s)
690 KB/s (419822 bytes in 0.593s)
572 KB/s (357080 bytes in 0.609s)
*** Getting temproot ***
property service neutered.
killing adbd. (should restart in a second or two)
*** Downgrading MISC ***
adb server is out of date. killing...
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
*** Step 1 is done, continue with Step 2. ***
*** Create a goldcard with the GoldCardTool first!
CID: 00B1004C58AC021030303030304D531B
Executing adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
Reading adb output
------------------------
adb server is out of date. killing...
* daemon started successfully *
1b534d30303030301002ac584c00b10e
------------------------
CID: 1B534D30303030301002AC584C00B10E
Reversing CID
CID: 00B1004C58AC021030303030304D531B
after i create gold card i patched it and the results are
------------------------
CID: 1B534D30303030301002AC584C00B10E
Reversing CID
CID: 00B1004C58AC021030303030304D531B
Loaded D:\Documents\Downloads\goldcard(1).img
Reading sector 0 of DriveG:
Converting to GoldCard Sector
Writing sector 0 of DriveG:
Validating sector 0 of DriveG:
Writing sector 0 of DriveG: Success
and after the reboot stil the same notjing has change on my hboot still
HTC WILDFIRE S A3333
BUZZ PVT SHIP S-ON
HBOOT-1.01.0002
MICROP-0622
TOUCHPANEL-ATMELA224_16ab
RADIO-3.35.20.10
:crying::crying::crying:
Click to expand...
Click to collapse
Sorry your right about running the bats as a admin !
It looks to be MISC your having trouble with try what i have said below
I meant to say run CMD as a admin then cd to to the folder that has the bat files
and run them from there this is where i had trouble !
also here is a gold card for you
If you still have trouble we will go through it step by step till we get it right...

SAME
matter1 said:
sorry your right about running the bats as a admin !
It looks to be misc your having trouble with try what i have said below
i meant to say run cmd as a admin then cd to to the folder that has the bat files
and run them from there this is where i had trouble !
Also here is a gold card for you
if you still have trouble we will go through it step by step till we get it right...
Click to expand...
Click to collapse
still the same t-t