Related
Which is latest version of bootloader in JAM??. Is there any version higher than 1.0??. Please submit...
i have 1.02
Due to some issues happened during big storage mod I have restore my phone from other old JAM backup. I think before that my boot loader is also 1.02 But now it is 1.0 . I did the d2s with 80000 0400000 full backup. Will it overwrite bootloader??. Can I upgrade my bootloader in anyway? Please help....
Do we have any advantages with latest version boot loader?? What difference we will have with the each versions??
SD Flashing can change your bootloader .. if you really want to change back your bootloader .. just use your old SD backup (the first/original SD backup that you made) then flash it to your device.. if you dont have it already you can change your bootloader using
itsme's PNEWBOOTLOADER.exe , the tool can upgrade bootloader of WALLABY, HIMALAYA and MAGICIAN .. tnx itsme for creating this tool ..
the only difference i see with different bootloader is during flashing .. some bootloader have some problem in flashing .. like in HIMALAYA .. 0.23 cant flash radio ROM using SD backup , 0.26b cant flash Extended_ROM in nbf, all version below 1.03 .. have this problem that sometimes it cant flash using a nbf(himaupgradeut.exe) and need to make a sd flashing..
Anyway my point is if u didnt find any problem using your current bootloader, i suggest to stay with that but if you do then thats the time that i can only suggest to change your bootloader .. anyway changing your bootloader can fry your device ..
-toe
To use pnewbootloader tool where can I get the rom file of the new bootloader version??
heres bootloader 1.02
15:03:32 Jan 24 2005
1.02 version: 1.38
3d1b0f86b5f1774c32982611b813abbb <- m not sure with md5 (pls itsme correct me if m wrong .. )
i dont have a magician so i didnt try it and i cannot guarantee that this is a correct bootloader
PS. This bootloader is for Magician and not for anyother device, i will not take responsibility for any thing that will cause for a brick device due for using of this bootloader .. please be very careful .. i already once killed my device due to bootloader ..
-toe
SD Flashing
Hi toenailed,
What's SD Flashing?
thanks
Toenailed:
could u be so kind to tell me what i'm doing wrong, i'm trying to upgrade / or maybe should i say fix my bootloader, when I do a pmemdump 80000000 00040000 I get little stuff, mostly it's blank.. (*uh oh*) I'm sure this is not the way it should be. I tried using it'sme pnewbootloader, and got an error
"Unable to find flash info offset, cannot disable bootloader writeprotect"
this is what i typed:
Code:
C:\exp\1\build>pnewbootloader.exe -f -o 80000000 -l 00040000 c:\flashboot.bin\BL1.02-1.38.nb0
Unable to find flash info offset, cannot disable bootloader writeprotect
also tried the simple
Code:
pnewbootloader.exe BL1.02-1.3.28.nb0
I'll post my setup in a bit, i'm trying to re-flash my devices SHIPPED roms, hopefully that will restore things.. (crosses his fingers) anyways what I think I did is erased the GSM bootloader, thus I cannot use my phone at all, the close i get to using my phone is getting to WinMobile.. anyways this is really not a problem thus I called my carrier and they are going to ship me a new one.. I just wanted to known for sake of knowledge and if someone else has the same problem.. also just incase i do it again with my new phone, doubt my carrier will fall for the "I pulled out my battery, and now my device is dead" lol heck i even think I erased my ESN and PRL out of my device, since I get N/A when i'm in Mobile..
[/b]
it means that i did not add code for your specific rom version to pnewbootloader.
what is the OS version you are using?
willem
Oh sorry about that: it'sme, (btw thanks for ur great tools, and website, full of resources). currently I just upgraded to the PDA2k_WWE one, that was just posted recently here is the info...
ROM VERSION: 1.40.00 WWE
ROM Date: 03/10/05
Radio Version: [blank]
Protocol Version: [blank]
ExtROM version: 1.40.176 WWE
but the ORIGINAL one that came with this device is:
I'm not sure if the info below is correct so I also provided the actual full filename of my update..
HA_VZW_13500_115_01140_WOC.exe
MODEL ID: PH20A3
ROM VERSION: 1.35.00
ROM DATE: not sure, since i don't have it installed atm
Radio Version: DM FAIL
Protocol Version: DM FAIL
ExtROM Version: 1.15
also do u happen to know how to bypass the NOT ALLOW UPDATE when using a SD card? I tried to do a radio dump first. but i get Radio stack fail (tm). also i think i messed aroud with some of the rroute rrouter settings, could u possibly tell me what the default/correct settings might be?
thanks lots..
oh yea, and also using xdatools, when I try to use them, It either says that my image is to big, or it says it's to small, or it says cannot connect to USB using Programme a
thanks again..
itsme said:
it means that i did not add code for your specific rom version to pnewbootloader.
what is the OS version you are using?
willem
Click to expand...
Click to collapse
Hello "itsme"... I have a little question to you...
It's posible to use 'pnewbootloader.exe' to flash any OS ROM offset using the '-o' and '-l' parameters?
Thanks :wink:
Hello toenailed / itsme..
Before I'm trying to change my bootloader to the 1.02 (and it can be a disaster some times) what are my advantages with a newer bootloader like 1.02 from 1.00. Now I'm sure before the SD flash restore from another JAM mine was 1.02. Do I have (with 1.02) a higher performance or bugfree or more support to hardware device? I have also notice one thing after this change to 1.00. Some time after soft-reset I will a "Unidentified USB device error" and it will prompt for correct USB driver and bluetooth will not work for sometime. But after 5 mins it will start working. This problem will not occur if I'm removing the main battery for a soft-reset.
Is this issue could be with bootloader version? Other than the OS booting and loading what else bootloader doooo??
zxvf: i don't think you are talking about a magician rom.
the 'not allow update' means that you restore a backup made with a different bootloader version. .... or that the sdcard contains an invalid signature.
MKS: in theory, yes, but for several locations in the ROM, the protection needs to be removed.
the protection is a list of values which specify where the non-flashable area of rom starts and ends.
pnewbootloader temporarily changes these non-flashable area's to something not in the ROM.
nishadks: there is no real need to upgrade your bootloader, it is more useful, to downgrade, since older bootloaders, usually have less protections built in.
Thanks a lot itsme for your help....
Itsme:
You are correct, I didn't pay attention to it being a bootloader for the magician, (eventhough it's bolded lol) anyways, I tried it ones again, with a rom that I KNOW is the same that I had, because before messing around with it, I made a backup with two different tools osupdate.exe and bootblaster.exe (the one from handhelds.org for unix flashing). So i have this files both as .bin files, but can't seem to use the l command AT ALL eventhough I have both of the passwords, (actually don't really know how to use mtty.exe) I can't get the concept on how u send the files.. because it timesout and says something like "the second computer timed out.." or something like that, it seems that I need to start some type of send transfer something similar like (tx, and rx) in unix.. but not really sure how to do this with mtty.exe, or do i actually need to have a serial cable, is it not possible with the cradle that came with the device? I was actually thinking on creating a cable since, I got a USB to Serial converter... so maybe that will work.. but havn't had much time to mess around with that...
I also tried every possible version that u said is supported in ur .cpp file and none will actually work with my device, they all just make my device screan white and it starts fading out to black, (or sometimes it starts with a diff color.)
so what should I do/try to get pnewbootloader.exe to work? or is there any software that I can use in Win mobile (on the pda) to just run it locally?
Cheers, and thanks again...
how to use pnewbootloader
hi mate would u plz like to to tell me how can i install b0otloader 1.02 on my magician. i hav tried to use pnewbootloader but cant find any help abt it how to use it. i hav 2 magicians 1 hav bootloader 1.02 and other 1.0.
the problem is i cant read my high speed sd card on magician with bootloader 1.0. but it works on magician with bootloader 1.02 both hav same versions of roms. i hav extracted my bootloader from newer one but dont know how to copy it on old 1.
if possible than email me on
[email protected]
thanks
bl*.nb
Please someone where I can download any version of the bootloader. I can not download on the link in post number 7
thanks, and sorry for my google translate.
same for me, page goes blank, and download never starts
hi there,
now i have a radio ver. 02.67.90 on my Artemis. Also there is
some radio ver . 02.69.90 extracted from other ROM.
Can anybody explain how to update radio only. (Tool and steps.)
Thanks
I like to know this too. Is there anybody in here who knows how to flash the GSM portion of the Artemis?
Can someone please throw light on this topic? thanks!
Insane Devil said:
Can someone please throw light on this topic? thanks!
Click to expand...
Click to collapse
Working on it! I can read the radio and other data now, almost there to write things back, hopefully tomorrow I will have the answer!
rvbcrs said:
Working on it! I can read the radio and other data now, almost there to write things back, hopefully tomorrow I will have the answer!
Click to expand...
Click to collapse
This im looking forward too,always wanted to upgrade radio to the latest,please do let us know about your results.
rvbcrs said:
Working on it! I can read the radio and other data now, almost there to write things back, hopefully tomorrow I will have the answer!
Click to expand...
Click to collapse
Any luck yet?
cid-lock
and please bring clarity about using it with a cid locked device
thanks in advance!
Hello rvbcrs,
when you are able to read the radio files can you also change the frequence from XXX.X mhz to XXX.XX or XXX.XXX mhz? In this case please change it ist verry interesting for me.
have a nice day
This is what I've got so far, it is to read the different sections of the Artemis, so you can make a backup of the Artemis:
pdocread -n 0 -b 0x20000 0 0x100000 bdk0-spl.nb
pdocread -n 1 -b 0x10000 0 0x40000 bdk1-0-cidarea.nb
pdocread -n 1 -b 0x4000 0x10000 0x4000 bdk1-4-gsmdata.nb
pdocread -n 1 -b 0x40000 0x140000 0x280000 bdk1-5-gsmcode.nb
pdocread -n 1 -G 0x30000 -b 0x10000 0xF0000 0x30000 bdk1-f-splash.nb
write OS:
pdocwrite.exe osrom.nb 0 0x3900000
The problem comes with the writing, I don't know how to use the above adresses to flash the sections back with pdocwrite.exe, I keep trying but maybe someone inhere can tell the exact syntax to flash back for example the GSM part or the splash screen.
I got the addresses from pof so all credits to him!
Hope he can help with the last part too!
RvBCrS
Thanks a lot for the post! But sorry I´m a german paramedic no programer. How can I find the pdowrite.exe? How can I change the frequence? from XX.X mhz to XX.XXXmhz?
Can you change it and send a link with the new file???
Thank a lot and have a nice weekend!
rescue01 said:
Thanks a lot for the post! But sorry I´m a german paramedic no programer. How can I find the pdowrite.exe? How can I change the frequence? from XX.X mhz to XX.XXXmhz?
Can you change it and send a link with the new file???
Thank a lot and have a nice weekend!
Click to expand...
Click to collapse
I think I don't understand what you want to do, is it the frequency of the radio band (NOT GSM)? or do you want to change the frequency of the GSM part?
If you are doing a radio rom only upgrade your device does not need to be cid unlocked. If you don't believe this, read rom guru's - summiter, kyphur and faria's posts in the wizard upgrading forum.
Your device needs to be fully charged and attach to pc via activesync or through bootloader mode and flash radio via the roms upgrade utility. (that is if you have the radio nbh and rom upgrade utility)
All this info is available on the forum please read.
meschle said:
If you are doing a radio rom only upgrade your device does not need to be cid unlocked. If you don't believe this, read rom guru's - summiter, kyphur and faria's posts in the wizard upgrading forum.
Your device needs to be fully charged and attach to pc via activesync or through bootloader mode and flash radio via the roms executable.
All this info is available on the forum please read.
Click to expand...
Click to collapse
Ok and can you tell us how it's done? because you can read all you want but for the Artemis you will not find it anywhere. (or I'm a lousy searcher)
rvbcrs said:
Ok and can you tell us how it's done? because you can read all you want but for the Artemis you will not find it anywhere. (or I'm a lousy searcher)
Click to expand...
Click to collapse
Most of the wm5 devices on the forum flash in the same way - most of the info needed is in the wizard and hermes upgrading forums. I did say how to do this - it is really that easy.(that is if you have the radio nbh and rom upgrade utility) Which part have I missed out?
You like most on this forum are lousy searchers - but don't hang yourself over it
meschle said:
Most of the wm5 devices on the forum flash in the same way - most of the info needed is in the wizard and hermes upgrading forums. I did say how to do this - it is really that easy. Which part have I missed out?
You like most on this forum are lousy searchers - but don't hang yourself over it
Click to expand...
Click to collapse
Are you sure, because as far as I know most parts of the data in WM5 phones is different, ok you have the ones like the Wizard and the Prophet that are almost equal, and there are more, but I thought the Artemis is different than most other phones, the addresses to flash the data in is different, ok the OS part is the same as all the others at offset 0x390000 but the rest, how about the rest? if I read the dat from the Artemis like this
pdocread -n 0 -b 0x20000 0 0x100000 bdk0-spl.nb
pdocread -n 1 -b 0x10000 0 0x40000 bdk1-0-cidarea.nb
pdocread -n 1 -b 0x4000 0x10000 0x4000 bdk1-4-gsmdata.nb
pdocread -n 1 -b 0x40000 0x140000 0x280000 bdk1-5-gsmcode.nb
pdocread -n 1 -G 0x30000 -b 0x10000 0xF0000 0x30000 bdk1-f-splash.nb
can you tell me how to write ik back than?
rvbcrs said:
Are you sure, because as far as I know most parts of the data in WM5 phones is different, ok you have the ones like the Wizard and the Prophet that are almost equal, and there are more, but I thought the Artemis is different than most other phones, the addresses to flash the data in is different, ok the OS part is the same as all the others at offset 0x390000 but the rest, how about the rest? if I read the dat from the Artemis like this
pdocread -n 0 -b 0x20000 0 0x100000 bdk0-spl.nb
pdocread -n 1 -b 0x10000 0 0x40000 bdk1-0-cidarea.nb
pdocread -n 1 -b 0x4000 0x10000 0x4000 bdk1-4-gsmdata.nb
pdocread -n 1 -b 0x40000 0x140000 0x280000 bdk1-5-gsmcode.nb
pdocread -n 1 -G 0x30000 -b 0x10000 0xF0000 0x30000 bdk1-f-splash.nb
can you tell me how to write ik back than?
Click to expand...
Click to collapse
The radio.nb for the artemis is diff from other devices - i would guess the start address is diff from the other devices for the radio.nb. But i was assuming you had the radio nbh for the artemis and was going to flash with the rom RUUpgrade utility - if not it would be better to obtain the radio nbh rather than make your own.
If you want to make your own radio nbh file - I suggest you use the NBHTool v1.1
i would follow instructions here http://forum.xda-developers.com/showthread.php?t=296311
Using dutty's good NBHTool v1.1 (updated) - it should be possible to do what you want i.e. create a nbh file with just the radio.nb and then flash with RUUpgrade utility
meschle said:
The radio.nb for the artemis is diff from other devices - i would guess the start address is diff from the other devices for the radio.nb. But i was assuming you had the radio nbh for the artemis and was going to flash with the rom RUUpgrade utility - if not it would be better to obtain the radio nbh rather than make your own.
If you want to make your own radio nbh file - I suggest you use the NBHTool v1.1
i would follow instructions here http://forum.xda-developers.com/showthread.php?t=296311
Using dutty's good NBHTool v1.1 (updated) - it should be possible to do what you want i.e. create a nbh file with just the radio.nb and then flash with RUUpgrade utility
Click to expand...
Click to collapse
Thanks! I did try dutty's tool, but the updater tool kept saying the update file was corrupt or something, no mather what I did... I guess it has something todo with the 1024 header signature or something.. so that's why I wanted to do it with the pdocwrite.exe tool.. I only need the right addresses and syntax to write it back..
rvbcrs said:
Thanks! I did try dutty's tool, but the updater tool kept saying the update file was corrupt or something, no mather what I did... I guess it has something todo with the 1024 header signature or something.. so that's why I wanted to do it with the pdocwrite.exe tool.. I only need the right addresses and syntax to write it back..
Click to expand...
Click to collapse
Did you try it with the latest version? It appears the latest version works with artemis. If you want to go down the pdocwrite route, pof's your man - i am not familiar with that tool.
meschle said:
Did you try it with the latest version? It appears the latest version works with artemis. If you want to go down the pdocwrite route, pof's your man - i am not familiar with that tool.
Click to expand...
Click to collapse
I just downloaded the newest version, and tried several things, the new version now also includes a feature to change the signature size, but still no luck I tried signatures 128, 256, 512 keep getting the message that the updater file is corrupt. When I try 1024 as signature size the updater starts, I can see the 0% and a progressbar and then the display slowly starts to fade to black and the RUU updater says: ERROR[276]: UPDATER ERROR
the ROM update utility has encountered communication errors bla bla...
I only get this error when I use a signature size of 1024..
strange stuff! DUTTY, POF HELP!! hehe
rvbcrs said:
I just downloaded the newest version, and tried several things, the new version now also includes a feature to change the signature size, but still no luck I tried signatures 128, 256, 512 keep getting the message that the updater file is corrupt. When I try 1024 as signature size the updater starts, I can see the 0% and a progressbar and then the display slowly starts to fade to black and the RUU updater says: ERROR[276]: UPDATER ERROR
the ROM update utility has encountered communication errors bla bla...
I only get this error when I use a signature size of 1024..
strange stuff! DUTTY, POF HELP!! hehe
Click to expand...
Click to collapse
Well it looks like your having a great time with this
Speak to dutty - you cant be far off. Which RUU updater are you using? - it maybe this that is causing the error.
Hello
How do I unblock the CID in a smt5600????
And how do I program another rom???
neb2567 said:
Hello
How do I unblock the CID in a smt5600????
And how do I program another rom???
Click to expand...
Click to collapse
Read Karhoe's first post and follow it entirely. It is the first topic labled 'STICKY" on the Typhoon page. Read everything first, download everything you need. Read everything again, then follow it exactly.
raskell said:
Read Karhoe's first post and follow it entirely. It is the first topic labled 'STICKY" on the Typhoon page. Read everything first, download everything you need. Read everything again, then follow it exactly.
Click to expand...
Click to collapse
Thanks....
But in the Step 9 show me this:
------------------------------------------------------------------
*Image Download Finish
OEMFlashWrite(82040000h,8C080000h,01B00000h)
Update BINFS offset 0x00000000 length 0x01B00000 ...
Write BinFS Offset add=0x0 Length=0x1B00000 Checksum=0x95EA3E42
Write to BINFS partition from sector 4, length 28311552, 55296 sectors...
Can't write to DiskOnChip, status=27
Flash BINFS failed.
Download Fails !!!
OEMFlashWrite error(12)
Error : DownloadImage return error (code = 0xFFFFFFFF)
------------------------------------------------------------------
Help becouse the smartphone isn't turn on
neb2567 said:
Thanks....
But in the Step 9 show me this:
------------------------------------------------------------------
*Image Download Finish
OEMFlashWrite(82040000h,8C080000h,01B00000h)
Update BINFS offset 0x00000000 length 0x01B00000 ...
Write BinFS Offset add=0x0 Length=0x1B00000 Checksum=0x95EA3E42
Write to BINFS partition from sector 4, length 28311552, 55296 sectors...
Can't write to DiskOnChip, status=27
Flash BINFS failed.
Download Fails !!!
OEMFlashWrite error(12)
Error : DownloadImage return error (code = 0xFFFFFFFF)
------------------------------------------------------------------
Help becouse the smartphone isn't turn on
Click to expand...
Click to collapse
U fried ur phone.......
have U checked again by pressing camera button and then inserting cable.....
no sign of life???
IF YES then ur phone is not more than a paper weight.....
I followed all steps as prescribed in kar hoe's blog, and did seuccessfull upgrade......but revived back to WM2003SE coz of RAM s**king and battery draining......
dark_prince said:
U fried ur phone.......
have U checked again by pressing camera button and then inserting cable.....
no sign of life???
IF YES then ur phone is not more than a paper weight.....
I followed all steps as prescribed in kar hoe's blog, and did seuccessfull upgrade......but revived back to WM2003SE coz of RAM s**king and battery draining......
Click to expand...
Click to collapse
Neb's phone is back online. It was not bricked. Karhoe's instructions (which I think are excellent) does not say to copy the os.bin to the root directory of c:, it infers by its command line structure that you need to put it there.
raskell said:
Neb's phone is back online. It was not bricked. Karhoe's instructions (which I think are excellent) does not say to copy the os.bin to the root directory of c:, it infers by its command line structure that you need to put it there.
Click to expand...
Click to collapse
Yes, very thanks Raskell
The problem was the file bin....
Only write a version of windows mobile 5.0...
The others have the problem....
Thanks
neb2567 said:
Yes, very thanks Raskell
The problem was the file bin....
Only write a version of windows mobile 5.0...
The others have the problem....
Thanks
Click to expand...
Click to collapse
If you have problems to flash WM6 then try again to unlock your phone. Sounds like the CID or application unlock procedure did not take correctly. The reason you can flash WM5 is most likely because it is the OEM ROM version.
http://selberg.org/2005/07/22/unlock-an-audiovox-5600-for-free/
This link is the one I used to unlock my Cingluar Audiovox SMT5600. It may help you as well
Hello, I believe that the problem that I have is to try to put it in supercid, because when I want to change it at cid=11111 he doesn't make it
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!
Hello
I tried to install a rom 3.14 on a htc hd 2 sfr (French operator) from the SD card! I find myself with an spl 3.3 that refuses to install another rom! sfr never gives an offcial rom! Now when I start my htc I end up with the boot loader screen!
impoissble to make a gold card because no way to get the CID from ans sd card!
i need your help plz
please i dont want to throw from the window!
Have you tried flashing the 3.14 rom through usb instead of the sd card
yes got an invalid vendor id! the probleme is that sfr is a **** operator! not even the original rom released ti the public
my hope is to get an hsp4 but nobody is working on it
Did you have hspl on the rom before flashing if so you need to remove the hspl and then flash the 3.14 rom if you look in the threads there is a how to i use the artemis rom which is 3.14 based and can be flashed with sspl
projektk said:
impoissble to make a gold card because no way to get the CID from ans sd card!
Click to expand...
Click to collapse
use a friends phone to get the cid, or a laptop, or any other winmo device. Doesnt have to be YOUR phone.
samsamuel said:
use a friends phone to get the cid, or a laptop, or any other winmo device. Doesnt have to be YOUR phone.
Click to expand...
Click to collapse
i have a laptop with an sd card readrer! do you knwo how to get the CID with it?
ps: i cant use sspl iam stuck in bootloader screen
i managed to get this infos using a c# program
C:\Users\acer\Desktop>ReadCID.exe
\\.\PhysicalDrive1 F:\
--------------------
Raw CID Bytes: 96-00-B5-3C-88-A0-38-47-32-30-44-53-4D-54-02-00
--------------------
Manufacturer ID: 2
OEM ID: TM
Product Name: SD02G
Product Revision: 3.8
Product Serial Number: a0883cb5
Manufacture Date: 6/2009
--------------------
Raw CSD Bytes: 00-80-16-80-FF-FF-FF-A9-83-5A-5B-5A-00-2E-00-00
--------------------
CSD Version 2 bit value: CSD Version 1.0
Data Read Access Time 1 (TAAC): 2ms
Data Read Access Time 2 (NSAC): 0
Max Data Transfer Rate: 50Mbit/s
Card Command Classes: 010110110101
Max Read Data Block Length: 10
Partial Blocks For Read Allowed: True
Write Block Misalignment: False
Read Block Misalignment: False
DSR Implemented: False
Device Size: 3751
Max Read Current @ VDD Min: 100mA
Max Read Current @ VDD Max: 200mA
Max Write Current @ VDD Min: 100mA
Max Write Current @ VDD Max: 200mA
Device Size Multiplier: 15
Erase Single Block Enable: True
Erase Sector Size: 128
Write Protect Group Size: 1
Write Protect Group Enable: False
Write Speed Factor: 32
Max Write Data Block Length: 2^10
Partial Blocks For Write Allowed: False
File Format Group: False
Copy Flag (OTP): False
Permanent Write Protection: False
Temporary Write Protection: False
File Format: 0
can some one please make me a gold card?
please i need your help! iam desperate
not sure if the format for the cid is correct (i remember reading it should be reversed when not using psas) so i did both.
9600B53C88A03847323044534D540200
0002544d534430324738a0883cb50096
thanks ! you make happy! havent triy it yet! but what you done is enough
send you a little something for your help
how to write the img file to sd card without the phone! ujsing a laptop sd readrer?
projektk said:
how to write the img file to sd card without the phone! ujsing a laptop sd readrer?
Click to expand...
Click to collapse
well, therein lies the problem. If you managed to get the correct CID, then you should be OK. If it turns out you have a USB type card reader it wont work.
gotta go, sick child, ill write a fuller response in an hour or so
OK, as mentioned in your PMs, you have a PCI reader, so you should be good to go.
have a look at THIS for how to write the img to sd card, but switch reference to phone in hard disk for your card in card reader. the process is the same.
Start at the line 'Get HxD Hex Editor, '
samsamuel said:
well, therein lies the problem. If you managed to get the correct CID, then you should be OK. If it turns out you have a USB type card reader it wont work.
gotta go, sick child, ill write a fuller response in an hour or so
Click to expand...
Click to collapse
hope nothing serious for the kid!
i was trying to write it using winhex but some windows 7 compatibilie issues! i will try HxD Hex Editor and post the result
thanks alot
Rom is updating right now! gold card creation succesful! i will create a post with a tutorial for other people with the same probleme !
thanks sam for your help!
a few tips to solve the probleme
http://forum.xda-developers.com/showthread.php?t=874304
use hspl2 .
flash hspl 2.08
flash a coustom rom, other that 3.14 made.
i got the same problem ... solved like this
hspl2 dont work with spl 3.03