I need it to never have been soff. Then I need that person to dump everything on the phone and upload it. That would help my development.
And yes every thing should work.
That's in there. As for everything else, I've dedicated my time to ics. I want to be the first ics booting wildfire s cdma
Sent from my HTC_A510c using Tapatalk
I am posting this on behalf of Simon because it fixes issues in both hboot and recovery and it give you HTC developer support. It is important to follow these steps exactly and in order to avoid any headaches or complications. THIS IS ONLY FOR VIRGIN MOBILE USA WILDFIRE S USERS, IF ANY ONE ELSE TRIES THIS NEITHER ME NOR SIMON ARE RESPONSIBLE FOR ANY DAMAGE DONE TO YOUR PHONE!!!!!here it goes.
1. Download both of these files and put them in the same location as the adb file.
misc.img
flash_image
2 Open the terminal on your computer and enter the following
a. adb push flash_image /data/local/
b. adb shell
c. su
d. chmod 755 /data/local/flash_image
e. /data/local/flash_image /sdcard/misc.img
After this you should get a message that looks like this if you followed these directions correctly
(usage: /data/local/flash_image partition.img )
That is it your phone should not reset or anything and you will notice any obvious changes up front but it is recommended by Simon that you do this for it gives your phone HTC developer support. BUT ONLY IF YOU HAVE A VIRGIN MOBILE USA WILDFIRE S.
6 minutes
10:11 PM
me: dd if=/dev/block/mtd0 of=/sdcard/misc-stock.img bs=4096
you need busybox installed
10:12 PM
simonsimons34: from android or recovery
me: either or
10:13 PM
simonsimons34: ok ill do it from android
/dev/block/mtd0: cannot open for read: No such file or directory
10:14 PM
me: um hold on
try dd if=/proc/mtd0 of=/sdcard/misc-stock.img bs=4096
I can't remember wtf it is on nand
10:16 PM
simonsimons34: no go
same error
10:19 PM
me: cat /dev/mtd/mtd0 > /sdcard/misc.img
try that
10:20 PM
simonsimons34: something happened
10:21 PM
got it
10:22 PM
E: Missing bitmap icon_installing
in recovery
me: what is that for
10:23 PM
simonsimons34: Mkm had that error i got her into recovery but she got that error and it rebooted
me: are you talking to her on gtalk?
10:24 PM
simonsimons34: yep
6 minutes
10:30 PM
simonsimons34: got the img how do i decompile
10:31 PM
me: upload it and give it to me
tell her i never got a invite from her
simonsimons34: Lol ok.
18 minutes
10:50 PM
me: as in I didn't get the talk invite
simonsimons34: i know i told her bout it
invite her
jjpolkri@gmail.com
10:51 PM
me: did you upload that dump ?
simonsimons34: still uploading lol
me: how big is it
10:52 PM
simonsimons34: 1mb lol. uploading at 35 bites per second
10:54 PM
me: also i think she has a bad download or something with that recovery
simonsimons34: weve tried multiple
10:57 PM
http://www.mediafire.com/?ljnfv9esxs7tge3
11:01 PM
thats it
5 minutes
11:06 PM
me: uh there is no cid in this
11:07 PM
simonsimons34: Well, what can i do about it lol
me: fastboot oem boot
go to h-boot
got to fastboot mode and try that above
11:08 PM
simonsimons34: hang on i need the fastboot file
11:11 PM
u know where i can get it other than sdk
11:16 PM
me: try this
http://forum.xda-developers.com/attachment.php?attachmentid=588859&d=1304719623
simonsimons34: thanks
11:18 PM
wont detect my device
11:19 PM
me: you have to be in fastboot mode
simonsimons34: Thats a given
me: You guys aren't s-off fully and I believe you are partially bricked
simonsimons34: huh? me or her
11:20 PM
me: all of you
There should always be a cidnum in the misc-image as ruu's check the misc partition
yours is screwed up and corrupted
unless you uploaded a corrupt one
11:21 PM
simonsimons34: Lol great. Hang on I'm going to loose internet.
11:25 PM
ok i got it. got the output too
OH and mkms recovery worked for gsm only not cdma?
11:27 PM
super cid....
11:28 PM
me: paste the output
simonsimons34: simon@Aspire-5251:~$ adb reboot bootloader
simon@Aspire-5251:~$ fastboot oem boot
...
(bootloader) setup_tag addr=0x60000100 cmdline add=0x9D07DEE0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x2D101
(bootloader) TAG:hero panel = 0x3
(bootloader) TAG:engineerid = 0x0
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is super CID
(bootloader) CID is super CID
(bootloader) Backup CID is empty
(bootloader) setting->cid::11111111
(bootloader) serial number: HT199X001642
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =536
(bootloader) active commandline: board_marvelc.disable_uart3=0 board_marv
(bootloader) elc.usb_h2w_sw=0 board_marvelc.disable_sdcard=0 diag.enabled
(bootloader) =0 board_marvelc.debug_uart=0 smisize=0 userdata_sel=0 andro
(bootloader) idboot.emmc=false androidboot.pagesize=4096 androidboot.bas
(bootloader) eband=0.94.00.0824 androidboot.cid=11111111 androidboot.batt
(bootloader) _poweron=good_battery androidboot.carrier=ALL androidboot.mi
(bootloader) d=PG76*** androidboot.keycaps=qwerty androidboot.mode=norm
(bootloader) al androidboot.serialno=HT199X001642 androidboot.bootloader=
(bootloader) 1.06.0000 zygote_oneshot=off kmemleak=off no_console_suspend
(bootloader) =1 console=null
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) partition number=7
(bootloader) Valid partition num=7
FAILED (status read failed (Protocol error))
finished. total time: 6.060s
11:29 PM
me: ok wtf is going on here then..............
11:30 PM
you are supercid as it says and is what 11111111 means
how ever that misc image i got is corrupted