Database Users

BA Disconnects as Update Starts

Hi,
Apologies in advance if I'm covering old ground.
I'm trying to re-flash a WM6 rom after my previous attempt just left me with the 4 colour screen permanently and as the links to mtty1.42.rar seem to be broken at the moment I decided to re-flash with a different rom.
the problem is that even though I can get the unit into boot-loader mode and the update software appears to see the BA when it checks versions etc. as soon as I hit the upgrade button the BA screen blanks and I get Error 112: CE ROM UPDATE ERROR.
I've tried different roms, different usb ports and different versions of activesync all with the same result.
Any help on this would be great and hopefully I haven't 'bricked' the unit.
Cheers
Duncan

Do you have PH20A2 or PH20B device?
mtty utility can be found using search button

It's a PH20B.
I've now found mtty after a fair bit of searching on other forums..now to see if I can make some sense of it's commands.
A further update: it seems that I've managed to corrupt just the OS part of the ROM. I managed a radio update successfully which means all the USB connection is fine for updating. It just can't access the OS part of the ROM.
Is there anyway to manually format that area of ROM so I can in effect install over clean unit? Infortunately I can't make sense of the mtty commands and don't know what memory address and for how log I should perform the format.
Cheers Duncan

try reflashing

You should know how to use search - however here is the link
http://forum.xda-developers.com/showthread.php?t=348030&highlight=mtty
(Is that hard to put "mtty" in the search field and set BA section only? )

Further update:
Now I don't even get the 4 colour screen. After soft and hard reset I get a dead device. I can put the device into bootloader mode (serial/usb) but as soon as the update software attempts to copy the rom across the screen blanks and I get the ROM Update Error.
Now my thought is to try and flash with the original rom for the device as I have another unit available but using the link from the BA wiki for dumping the ROM doesn't work. I have also tried searching for 'ROM Dump' within the BA section of the forum but there don't seem to be any definitive instructions for this, everyone just keeps asking why not use the wiki or search funtion....
I have used the wiki and the search funstion and I seem to be the first with this situation.
Soft Reset - Nothing
Hard Reset - Nothing
Bootloader - Able to flash the radio rom but as sson as i try to flash the OS rom the screen blanks and I get Error 112: CE ROM Update Error. When I take the device out of the cradle the screen comes back on with the Serial 2.xx screen and I'm back to square one.
I've tried to use the wiki to dump an exisiting working rom but the link on the wiki is broken. I have also searched the BA forum for these intructions but they're not covered as they're already in the wiki..... or not as the case is.
I appreciate you regular users get fed up with noobs coming on and expexting you to do all the work for them but so far I've spent 3 days searching both this site and others to try and resurect my device. I'm not dumb or lazy and would love to be able to do all this myself but without instructions I'm flying somewhat blind.
Any help would be great..... please??

[off topic]
no need for apologies...
we started once like you... some are far worse...
knowing one part and boasting with air on their heads...
since you managed to explain yourself on your first post.
knowing what to search (E.G. MTTY 1.42.rar)
you definitely searched the forum before you posted AND
you stated that the links are not working... that proves it.
we are the one who is sorry because some others think
that they are high and mighty, it sometimes blurs the opinion making.
i dont like opinionated people because i admit that am one too... sometimes...
but that doesnt mean i hate them...
[on-topic]
you never told us what happened when you tried the mtty procedure.
is your last post the result of your mtty experience?
please elaborate how did you end up with that... what did you do before you soft-reset and hard-reset?

SilverSamurai,
Thanks for the quick response.
After my last 'apparently' successful re-flash with Helmi's latest WM6 rom when I hard reset the device I had nothing but a blank black screen, no power LED or anything. Soft-reset was the same. I can reset into bootloader and the PC detects the device when I place it in the cradle. The first part of the update seems to work although it never detects the current OS installed, it always says upgrade from ' ' to 'ver 6.0.0' which is wierd because it always used to say the previous OS version. When I then hit next the progress bar shows on the PC but the BA screen immediately blanks and eventually the PC gives the ROM update error.
I have managed to re-flash the radio rom in this state which proved that I still have access tho the device from the PC.
Using mtty I can run through all the commands to recover from the 4 colour lines screen (even though I'm beyond that point).
USB>set 14 0
HTCST ÚÈÒHTCEUSB>task 28
DOC_format_HW+
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
USB>task 0
USB>
It's almost as if the last flash didn't complete and has left the area for the OS 'dirty' with what ever it did manage to flash. What I was hoping to try was to re-format the entire OS section of memory and then try to re-flash again. Using mtty it says you can format sections of memory by stating a start address and the length you want to format but I don't have clue what these should be.
I've tried flashing with WM6, WM5 and a compatible version of 2003 with the same result every time. I would like to dump a rom from another BA I have and try with that but as mentioned earlier the link for that is down at the moment.
I think that's about it. If you need any more info let me know.
Many thanks
Duncan.

let's relist the things you did.
USB>set 14 0
Click to expand...
Click to collapse
1. start OS after a reset
result:
HTCST ÚÈÒHTCE
USB>task 28
Click to expand...
Click to collapse
2. format doc (Disc-On-Chip)
result:
DOC_format_HW+
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
USB>task 0
Click to expand...
Click to collapse
3. do hardware clear boot.
Click to expand...
Click to collapse
since i dont want to experiment with my sole BA...
i tried to search for solution...
and with some of my computer instincts i came up with this suggestion...
try this command before "task 28"
"task 7 0" <-- this is the "Do flash ROM lock/unlock" command
"task 2a" <-- fix bad blocks on MFG bootloader and Storage
then try to reflash your BA.
my sources one | two
although it's not BA but i think mtty commands are generic.
it's worth a try.

SS,
Still no joy, it's exactly as it was before.
Just reading through some more posts for bootloader ant it seems at least one other person has the same problem - http://forum.xda-developers.com/showthread.php?t=345181&highlight=bootloader and no resolution posted for that either.
I think I may have got it beyond the point of return.
I've just tried to flash from the blank screen I end up with from the initial attempt and it still detects the device but fails in exactly the same way.

awww... im sorry to hear that.
but dont lose hope.
i'll try to read some more and search for solutions.
and i hope someone with the same problem as
yours that had their BA fixed comes to the foreground.
[off topic]
hmm... come to think of it... we're both Marvel SuperVillains

SilverSamurai said:
awww... im sorry to hear that.
but dont lose hope.
i'll try to read some more and search for solutions.
and i hope someone with the same problem as
yours that had their BA fixed comes to the foreground.
[off topic]
hmm... come to think of it... we're both Marvel SuperVillains
Click to expand...
Click to collapse
These steps are from my notes. Follow these steps. It worked for me last time i tried (3 months back)
2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete)
kill two processes rapimgr.exe and wcescomm.exe
3. put your device into Bootloader Mode by pressing Power + Record Button and Soft Reset.
4. Run mtty (from downloaded) Choose WCEUSBSH001
5. type "set 14 0" without the quotes to tell bootloader to boot the OS after reset.
6. type "task 28" to get your device formatted
7. type "task 0" to ask your device reboot
8. take the device out of the cradle, and manually reset it if it does not do that already.

i think he did all of those already,
that's why i posted this in response to his mtty experience.
wouldnt hurt to try it again though.

A bit more info:
I tried the mtty solution again but still the same result.
I finally managed to find the instructions for dumping and exisiting rom to SD card and pulled one from a working unit. I put the card into the faulty BA and booted into bootloader. Pressed 'Power Button' to flash from card and it appeared it was going to work........ until it got to 12% then it failed with the message 'Download Fail'. So still no better off.
What I'm going to try now as it seems anything is worth a try is use the address ranges used to dump the rom to try and format all 3 sections. See if that will give me a clean base to try and re-flash from the sd card. My only worry is if it will format the section of ROM used to store the bootloader info.
I'll post my results shortly.

Now I need to know how to get the bootloader password to enable me to use the 'erase' command through mtty.
The hunt coninues....

Yet more developments.
As the update from SD failed I thought I'd see if it was possible to dump the current contents of the rom to SD using the following
“d2s 80000000 02000000“
“d2s 60000000 00300000 sd a“
“d2s 70000000 01080000 sd a“
The first 2 commands completed fine and checksum was OK. On the 3r command 'd2s 70000000 01080000 sd a' it errored with the following result
USB>d2s 70000000 01080000 sd a
SD:Waiting for card insert.........
CMD3 for SD, it's OK, ready to get RCA from response.
SDetected one card
SD:ready for transfer OK
pc->drive.total_lba=1E8000
pc->drive.num_heads=0
pc->drive.sec_p_track=0
pc->drive.num_cylinders=0
pc->drive.block_size=200
pc->drive.features=0
pc->drive.RCA=B368
pc->drive.drv_type=40000000
pc->drive.securedAreaSize=0
pc->drive.securityDrv=0
pc->drive.busWidth=1
pc->drive.erasedSize=0
Total card size=3D000000
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
DOC_ReadBinary is fail: dwStartAddress=0,dwReadSize=40000.
DOC_ReadBinary is fail: dwStartAddress=0,dwTempReadLength=40000.
*DOC_ReadBinary is fail: dwStartAddress=40000,dwTempReadLength=40000.
*****************************************************************dwCheckSum of Storage=95609D16
cSectionNum=2
psImageSectionInfo[cSectionNum].dwCheckSum=0
psImageSectionInfo[cSectionNum].dwLength=1080000
Stored image of SD/MMC card checksum error!
Now my guess is the Doc_Read_Fail bits are the corrupt part of the rom. If I can find a way to repair these I could then try re-flashing the rom.

what was "task 2a"'s result?
i think that's the chkdsk option of mtty.
we're dissecting the innards of the bootloader.
little by little as we go along the way...
im learning something, i hope you can find the fix for your problem.

SilverSamurai,
Thanks for the help you gave but the unit has finally had enough and totally locked. No power or anything no matter how I try to reset it. I've tried charging for hours, discharging for hours, left the battery out for hours but to no avail. It seemed to take exception to me dumping the rom contents to the SD card. Maybe there was a hardware problem ?? Not sure.
I'll have to see if I can wangle another unit from the company I work for as we're currently selling a bunch that were purchased for a failed IT project on ebay.

it was sad to hear/read that.
anyways. at least we tried to revive it. but dont throw it away.
maybe someday there will be ways how to ressurect your BA.
Happy Computing! err... Mobile Computing!

Polaris ROM Dump in bootloader mode [HELP]

Hi,
I open this thread in the hope that this might help other people in the future (I found it quite time-consuming to find out the relevant information).
Motivation: My Polaris (actually from O2) had lately a servere graphics error which disappeared after a soft reset, but the day after it refused booting:
after pressing the power button, the provider-logo is shown (appearing with some minor graphics errors) and after 30 seconds the device reboots again. Before doing a hard reset or sending it to HTC, I wanted to backup the NAND-Memory, from which I can - hopefully - restore some data, especially Notes, Short Messages and some contacts.
I spent a lot of time finding out the possible ways of ROM dumping. To summarize what is not possible:
Dumping to MicroSD-card is not possible, since "r2sd" (or "d2s") is not available on the Polaris
Dumping via "itsutils" and "pdocread" is not possible, because it requires a properly running Windows Mobile on the Polaris
Please correct me, if I am wrong.
The only available method seems to be:
Start the Polaris in bootloader mode and connect it to the PC via USB
With HTCFlasher (great tool btw! Alternatively mtty/ttermpro) issue the commands
password BsaD5SeoA
set 1e 1
rbmc
I know that rbmc can be told a start-address and length, but I do not know these addresses. In the first moment this seems to work, even though it is quite slow (~8 KB/s, at the moment the dump is at 71 MB). However, after a first peek into the dump, I noticed that the dump might be partially corrupted, due to some seemingly randomly inserted bytes (mostly with value 0x00). For example: at offset 0x39110 there seems to be a Delivery Confirmation of a Short Message: Instead of "Systemadministrator" it reads "Sys.temadmin.i.rator" (the dots are 0x00, 0x82, 0x81). Or again at offset 0x3D1C0 it reads "Sy.stemadmi.ni.rator" (dots are 0x00, 0x04, 0x81).
I use the latest version of HTCFlasher on linux-2.4.32 with the usb-serial-source of linux-2.4.28.
My questions:
Is there something to keep in mind when using rbmc on the polaris?
...probably regarding usb host buffer sizes? In in this thread pof suggests to use two rbmc's to dump the splashscreen.
Is there another way to perform the dump?

Yeah me too
Yeah I wanted to do something similar with my Kaiser. I wanted to dump the various winCE partitions from bootloader.
I started two threads
http://forum.xda-developers.com/showthread.php?t=481964
and
http://forum.xda-developers.com/showthread.php?t=480410
As you will see the only advice I got was "try using QMAT".
Unfortunately, QMAT is an extremely complicated piece of software and only runs for ten minutes at a time unless you are willing to pay for it.
IMO there should be a simple answer to this but nobody cares enough to read our threads...

[Q]I need help please

Hi all, new here, I'll get straight to the point because it'ds quite urgent. I flashed my htc elfin with the onyx 6.5 rom and after flashing if kept crashing on the Orange splash screen but I done an even more of a stupid move because I tried flashing the phone with a shipped rom and at the time I did it I didn't know it was incorrect so now all my phne can do is display pretty red green and blue gradiants with the following written on the red gradiant.
IPL 2.27.0002
SPL 2.28.0000
I can't remember anything like CID or anything like that but I do have the following...
SN :HT837Gxxxxxx
IMEI :35678601xxxxxxx
Part Number :99HEH137-00
Part Description :SKU,ORANGE,English-WWE,GBR,white,GSM 900/1800/1900,HTC_P3452,ELFIN-A2,w/ SIM Lock
Customer Name :Orange P.C.S Limited
Customer Model :
HTC Model :ELFIN-A2
Error Message :
Please help me as I can't do anything with it.
By the way I got two other devices, one being my gizmondo and the other being my old IPAQ h1910.
I've also got this info...
Cmd>password BsaD5SeoA
Pass.
+ SD Controller init
- SD Controller init
+StorageInit
SDInit+++
SDInit - SD ver2.00
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd1 Command response time-out. MMC_STAT = 80
SDCmd55 Card status error in response. MMC_STAT = 4000
SD Ver2.00: Low Capacity
SD clock to 24MHz
***** user area size = 0x3AF000 Secters
SDInit---
SDInit OK
g_cKeyCardSecurityLevel = FF
HTCEType (0x1)(Operation mode flag): cOpModeFlag=(0x0).
Type (0x2)(Back color flag): cBackColorShowFlag=(0x1).
Type (0x5)(Background color value): g_wBColor=(0xC618) (0xC0C0C0).
HTCST
Thanks Leighton

Leightonw87 said:
g_cKeyCardSecurityLevel = FF
Click to expand...
Click to collapse
that little line is telling u that the phone is CID-Locked, and as it doesnt go beyond the bootloader, is bricked too.
so, the most easy thing to do is trying to flash the unbricker rom from sd, if that doesnt work go with the goldcard method that will work for sure if done properly.

I tried the unbricker rom through the ruu utility but it says invalid vendor and when I do it through SD it says Checking SD and then nothing. I'm currently trying the goldcard method but it doesn't seem to want to work on my 2gb MicroSD. The SD SN starts with 00 so I not sure whats wrong.
I now regret doing the flash in the first place. Also some of the utilities are reconising it as around 900>mb, not 2gb so thats making me think that I should get a 512mb or 1gb memory card...

try making a smaller partition in sd card and the unbricker rom again.
read this:
http://wiki.xda-developers.com/index.php?pagename=Elf_SD_Card_Flashing
the problem is not flashing roms, the problem is with all the ppl that tries to flash original roms/backups and end with a dead phone.

That is probably what did lol.
Edit, How do I resize the SD card, I've done it in past for my IPAQ but that was a good while ago and it was for putting opie on it.

Start > control panel > administrative tools > computer management, then on the left select disk management under storage. delete all partitions from ur sd card and make a new one with 800mb for example and make sure to format it.

I've got windows 2000 and under disk management, Delete Partition is greyied out on the sd card.
EDIT:
I just tried disk management on my windows xp laptop and I cannot Delete Partition, same as the above which makes me think it maybe my card reader because this is with a 1gb microsd, not my 2gb one.

I know I shouldn't do this but I'll say sorry in advance.
I can't get the gold card method to work nor will it flash from sd, should I be using a wm device with a MicroSD slot or should I be able to use the adaptors in a standard sd slot device as I only got the latter. I'm in desperation and I really can afford to send it off, please help me.

AFAIK, the sd adaptor is just a mechanical device, so it should work ok.
however is strange that u cant flash from SD, make sure that the filename is correct and that u wait long enough.

i will suggest simple way switch off ur device . (take the battery out) reinsert the battery and flash ur carrier provided rom from our forum..see sticky rom thread. and try flashing original one .it will work flawlessly ..and then use 3.10cmon uspl and ur cid unlocked and free to flash any
rom..
Hapy flashing

I've tried looking for the Orange uk shipped rom and they are all dumped roms on the wiki and there isn't any orange uk shipped roms on the stickie.
I wish they made this sort of thing alot easier, My sony ericsson didn't even give me this much hassle.

Leightonw87 said:
I've tried looking for the Orange uk shipped rom and they are all dumped roms on the wiki and there isn't any orange uk shipped roms on the stickie.
I wish they made this sort of thing alot easier, My sony ericsson didn't even give me this much hassle.
Click to expand...
Click to collapse
Your Sony Ericsson probably didn't allow you to flash cooked ROMs either.
You don't need an Orange shipped ROM, you just need a shipped ROM with same device ID (eg. ELF010150 or whatever your device is). Gold card should work if done right.

I think I'll have to see if I can get a Virgin Lobster phone because out local pawn shop gets them quite often and very cheap, to try the goldcard then, until I find one I'll wait abit because my gizmondo refuses to do anything with QMAT even though it says written to sd card.
By any chance is it possible to change Cardid by hex editing?

Leightonw87 said:
I think I'll have to see if I can get a Virgin Lobster phone because out local pawn shop gets them quite often and very cheap, to try the goldcard then, until I find one I'll wait abit because my gizmondo refuses to do anything with QMAT even though it says written to sd card.
By any chance is it possible to change Cardid by hex editing?
Click to expand...
Click to collapse
I don't know because all the knowledge I have about the Gold Card is shared in the Wiki. As I already stated there, I don't know of any other way to get the Card ID. I'm no hacker.

ok no probs, thanks for all the help you've given to me, once I find another WM device I'll try again because I spend too much time on trying to do goldcard and my partner is getting annoyed. lol

Leightonw87 said:
I tried the unbricker rom through the ruu utility but it says invalid vendor and when I do it through SD it says Checking SD and then nothing. I'm currently trying the goldcard method but it doesn't seem to want to work on my 2gb MicroSD. The SD SN starts with 00 so I not sure whats wrong.
.
Click to expand...
Click to collapse
What do you mean by it "doesn't seem to want to work"? What error are you getting. And why do you want to hex edit the card id?

No matter how many times I try I just doesn't want make the goldcard. on xp and 2000 but like I mentioned before it must be something to do with my gizmondo. My pda is pre ppc 2003 so no luck there. doesn't find the serial number at all.

Leightonw87 said:
No matter how many times I try I just doesn't want make the goldcard. on xp and 2000 but like I mentioned before it must be something to do with my gizmondo. My pda is pre ppc 2003 so no luck there. doesn't find the serial number at all.
Click to expand...
Click to collapse
Just buy a WM device from the electronics shop and then use the Gold Card method on it.. then return the device when you are successful

hahaha, Thats a great idea but these days they are pretty fussy when it comes to returns.

Hi, I just thought I'd add this as I don't know what the CID number is.
Cmd>getdevinfo
HTCSELF010051¡o³fHTCE
As far as I can work out its ELF010051 but looks like something went wrong with the CID number
I know it's orange uk as shown in the first post. I was also wondering could I create a goldcard by just using my pc/laptop or could someone create a goldcard for me???
SD SN:E06E030000000000F0FFFFFF30000306

[Q] Possible Hboot Hack ????

Whilst spending more endless hours attempting to root my wildfire, I have noticed that if I push mtd0 to sdcard as mtd0.img, and then use HxD to edit it as though to use flash_version ( I was thinking I wonder if it's possible to spoof supercid 111111) so after backing up the original I filled the entire file full of 1's (I tried 0's first, the error message tells me if i could force 0's this may be a good thing???) and flashed misc.
On entering hboot when it checks sdcard a load of 1's came up before anything else, so i repeated the experiment with stars *, and *'s is what hboot seen.
I'm thinking possiblity of some kind of alternate boot or mabye a command (fastboot oem unlock, or fastboot erase hboot) or something along those lines. Tried modifying the first line, but still came up *'s so somewhere else in the file possibly where version goes, but version doesnt usually show up on sdcheck does it.
Experiments continue

Keep up the experiments!
Thanks!

keep up doing it, you are great

thousands of people hope this work in the future...
i think unrevoked is not doing anything now
we r 4 months from 2.2....

Any more luck? How is this getting on?

dannyjmcguinness said:
Whilst spending more endless hours attempting to root my wildfire, I have noticed that if I push mtd0 to sdcard as mtd0.img, and then use HxD to edit it as though to use flash_version ( I was thinking I wonder if it's possible to spoof supercid 111111) so after backing up the original I filled the entire file full of 1's (I tried 0's first, the error message tells me if i could force 0's this may be a good thing???) and flashed misc.
On entering hboot when it checks sdcard a load of 1's came up before anything else, so i repeated the experiment with stars *, and *'s is what hboot seen.
I'm thinking possiblity of some kind of alternate boot or mabye a command (fastboot oem unlock, or fastboot erase hboot) or something along those lines. Tried modifying the first line, but still came up *'s so somewhere else in the file possibly where version goes, but version doesnt usually show up on sdcheck does it.
Experiments continue
Click to expand...
Click to collapse
I tried this a week ago and it does not seems to work :S
cid version is on "ro.cid" prop. Change cid on mtd0, flash it and then try a "getprop ro.cid"
Of course, you'll get the original CID, not the supercid. You cannot change these properties (ro.secure is another one. The ONE that prevent us from writing on system, etc)
I think these properties are Read-Only and are loaded into the system from the hboot at boot time.
I managed to change the default.prop on "/" from ro.secure=1 to ro.secure=0 but every time you reboot your phone this file goes back to ro.secure=1, so I think hboot re-load every file and prop needed for their security lock at boot.
I repeat, even with root access you won't change a single property with "ro." before.
Not a single one.
Sorry guys, we'll have to wait more...
For more information abot the proccess read my post: http://forum.xda-developers.com/showthread.php?t=1042077
As you can see, no one has answered yet so I think this is useless...

Looks promising!
Sent from my HTC Wildfire using XDA App

Think I've discovered a bit more, I'm absolutly posotive that this is the way forward. Problem is not enough people seem interested in this post.
It would appear that this can be used to issue a boot message, so please share your knowledge on what you know of boot messages, coz I'm pretty sure a boot message could be used to override certain parameters.
Please people, if you read this, HELP ME OUT

I know what are you talking about,and I think that might help you
http://runtimeworld.com/2011/04/a-complete-list-of-hboot-commands/
I could work with you on this, PM me if you are interested
edit: this command has 8 letters (like cidnum):
writemid // write model ID

The best thing u've found.. I'm feeling like we'll oly root wildfire before unrevoked.,
It'll be good if we do it our self as unrevoked has tried hard but not succeeded due to heavy lock of hboot.. If there is a luck and ability to do it, we can do it..
I dont hav knowledge in linux and android much elz i would hav joined to root wildfire with u all..
Best of luck for rooting and make sure not to brick the phone..

God, I must follow this post.
Thanks for your hard work.
Sent from my HTC Wildfire using XDA App

Maybe you'll find something interesting there
tjworld.net/wiki/Android/HTC/Vision/HbootAnalysis
sry, can't add urls i'm new

ejnreon said:
Maybe you'll find something interesting there
tjworld.net/wiki/Android/HTC/Vision/HbootAnalysis
sry, can't add urls i'm new
Click to expand...
Click to collapse
cant be THAT new if you joined in 2009 :L

[Q] error 80180008 help how to cab

Hello all. I am very sorry to bother you all but I have been trying to upgrade my phone for the last 4 months and have almost given up. I saw the film about noods and really left it to the last resort! have an OMNIA 7 on:
7.10.7740.16 trying to go to 8107 for now but would like to go to windows 7.8 if possible
Fimware: 2424.11.112
Boot loader 6.4.09
I tired Zune: got error 80180008
Asked Microsoft: no help
Read forums and tried cab sender to send 8107 (+ languages) by Heathcliff: got same error but now know a bit more helphowto.cab.pkr ERROR CODE: 0x80180008 invalid signature ) (. (thanks Heathcliff!)
Tried sending firmaware: worked!
Tried sending just language packs (got 6 on my phone) only partial loaded to 7.10.8099
I Read more on forum: tried sending certificates to phone by e-mail. Tried installing various certificates on computer. Tried sending a previous help how to cab (from previous O.S. cab via e-mail to phone (thought it might be missing). Tried partial unlock but, as expected, did nothing.
After reading more on this site, I have seen that the certificates have expired on the CAB files (downloaded from "force ugrade") and so guess it has nothing to do with phone or windows (tried windows xp, vista and 7 ultimate). Asking for a new cert. seems like playing tomb raider to me.
.details about error:
ERROR: 0x80180008 : Updatevalidator in ULDR reported this error. Update cannot continue.
ERROR: E_INVALID_SIGNATURE: Signature validation failed for following Delete Package.
Package: \OSRoot\Application Data\Microsoft\DeviceUpdate\Packages\FB6757FA-7853-4C50-9239-A2C975F81FC4.1.pks\helphowto.cab.pkr FROM Version: 0.0.0.0 TO Version: 0.0.0.0 GUID = {6A540B21-B5C0-4D24-8903-B5B5EB97DF58}
1980-03-21T19:45:43Z:: VerifySignatures failed for graph with base name of HelpHowTo. Trying to find another path.
1980-03-21T19:45:43Z:: BuildReturnValues: Returning HRESULT 0x80180008
=====================================================================
1980-03-21T19:45:43Z:: GOOD PACKAGES AND BAD PACKAGES LIST
=====================================================================
1980-03-21T19:45:43Z:: BAD PACKAGE 1
1980-03-21T19:45:43Z:: : helphowto.cab.pkr ERROR CODE: 0x80180008
1980-03-21T19:45:43Z:: Total number of Bad Packages: 1
1980-03-21T19:45:43Z:: Process Failed with code 0x80180008
Phone works OK except for key board drop so it is not the end of the world I guess. As a last chance I would be to try seven eighter. I have seen that some people even stuck on 7720 have been able to upgrade. However, In one thread you said we can’t roll back. Another one you said it SHOULD be possible to burn a back up back to the phone.
I have seen other questions on ths and other forums about error 8018008 but I have not found an answer that helps.
I Know it is my problem but if someone could find the time to help to answer these questions:
1. to burn a back up back to the phone, will cab sender work ? I have read that zune does not.is there another tool? The tool heathcliff mentioned, does not work with the latest version zune.
2. I have seen other people on 7720 been able to go to 7.8 with seven eighter but I have seen they have had someproblems (I think mainly due to wrong language pack selection issues)-. Do you think it would work for me even if I get this error? If there was not a problem of rolling back I wold gve it a go.
3. Is there something else I can do (except buy a new phone)
Thanks and sorry if this is in the wrong place or I have broken any rules un- intentionally !
Martinxp

Hi,
If you want 7.8, switch to custom rom => look at my signature.

hBk0dY said:
Hi,
If you want 7.8, switch to custom rom => look at my signature.
Click to expand...
Click to collapse
Thanks I will read carefully and let you know. However, If I understand correctly though, the Magldr software unlocks my phone so I can load the immage ROM?
The only other doubt I have is about the memory on my phone. the Samsung site says nothing but an test report I found in WINDOSTECA says it should have 576mb RAM and 512MB ROM. Any one know if it is valid and if it is enough?......also where is the thanks button?
thanks again Misterxp

Yes Magldr unlocks your phone. Samsung omnia 7 as 512Mo of RAM and 8Go of memory, that's enough to install a custom rom.
512MB ROM is the size of the Rom (thus the system). This size can vary depending on the rom.
Thanks Button => http://i70.servimg.com/u/f70/17/66/30/68/captur14.png

problem solved
yippeeeeee
I solved the problem!
I decided that if flashing a custom ROM would solve it then so would flashing the official ROM. Hence I read all I could about official Samsung ROMS, chose the one which was not so old "I8700XXKC1_Many_PROVIDERS_NODO (7.10.7390), Chose the CSC for Italy because I live in Italy and then woke up one morning and went for it.
I followed all the instructions to the letter but had read them 100 times before! I formated the phone holding the Power + Volume DOWN + Camera buttons, followed the instructions in this thread: http://forum.xda-developers.com/showthread.php?t=973420 by Heathcliff and then, after all was done (went very smoothly, I connected to Zune and went all the way to 7.8. I had to cancel the update a couple of times because zune blocked but all went well in the end.
In between updates, I changed the names of the back up folder, so that zune created another in case I had to go back. I made this a habit in the past and meant I was sure I Always had a back up. (sometimes zune will cancel a backup if the process does not go correctly and, if you don't save back ups you end up with no back up!). When I finally got to 7.8 I used CAB SENDER to send an old CAB which I knew could not be installed and in that way I got a back up of my final version with all my apps installed. I did this because, once there are no more updates, zune does not install anything and so does not make a back up either. It is the easest way I have found but there may be another, I tried the various back up programmes but could never get them to work. I don't think my way does any harm to the phone but some one else more expert than me might know. The main thing I learnt is how important it is to have a back up and save the back up. It saved me a few times. Once, when trying other ways to fix the phone, I tried to restore with zune, but it kept giving an error. However, I managed with CAB SENDER. Once, another time, I got as far as 18% and even Cab sender kept giving an error. I took out the battery and waited a few minutes (before shooting my self!) and it worked! Anyway, thanks to you all at Xda and I will send a donation as soon as I get the chance to load Paypal. bye from Mister Xp