Radio 1.13.0 SD Card upgrade failure
Error :
SD Download
=========
Section =1
Not Allow
Update!
Right now when the PPC soft reset the right of botton corner display NO GSM
Please Help me Thanks a lot.
didnt you save your origional radio?
or just try again??
it worked for me first try. what did you do??
You should have overwritten the first 444bytes of your 1.13 ROM with 444bytes a SD card backup of an older Radio ROM!
thanks your adivse let try again
416 bytes would be ok, I have done and works fine.
What software do you use to replace the bytes?
Hex Editor, you could find it at the ftp server of xda-developers.
/Magician/Tools/Backup_tools1/
rjtd said:
What software do you use to replace the bytes?
Click to expand...
Click to collapse
I am usng the Hex editor
gradius44 said:
416 bytes would be ok, I have done and works fine.
Click to expand...
Click to collapse
Be very carefull with that. This is NOT a full ROM backup, so the layout is different. I would strongly suggest copying all the bytes, or you could end up with that dreaded paperweight.
what if you don't do the 444 bytes things ?
can you just copy the radio as is ?
thanks
I have no clue, and I would never try to do it. Far too big a risk to take, just to save 1-2 minutes...
i say this because I don't understand this part (overwriting the 440 Bytes from 1.13 Radio with the 440 bytes of my older radio 1.12 )
is that this way or vice versa ?
When you open an hex editor ? What do you see ? how can you see this is the first 440 bytes ?
thanks man if you can help me
Those first few bytes, in this case 444 of them, contain an unique device ID. That ID is needed to 'authenticate' the ROM-image when being flashed to the device. I've tryed to flash my Magician without patching my new ROM with a number of bytes from the older (backup) ROM. The device gives my some freaky error, but nothing else happens, since the bootloader detects a 'bad' ROM.
Related
I need to restore my original T-Mobile ROM to send the hardware in for repair. I have tried ROMS supplied from 2 different sources to no avail. They are all exactly the same size... 33292288. Everytime I try to use the OSImage Tool to copy it to my 256MB SD card, I get this error immediately...
C:\....\tmo.nb1: incorrect filesize(33292288), file should be exactly 32243712 bytes error opening input file.
I am stumped. Anyone know how to get by this?
mmm, the top 1M of your nb1 does belong in the os image part of the rom,
it contains the save contacts etc.
you can either delete it yourself using a hexeditor or other binary file editor.
Your file has to end at offset 0x01ec0000
or wait until I make osimagetool less strict. ( which might not be soon )
Just for the hell of it I'd give XDArit and try, you never know
it might work!
HTH
XDA developer Itsme said:
mmm, the top 1M of your nb1 does belong in the os image part of the rom,
it contains the save contacts etc.
you can either delete it yourself using a hexeditor or other binary file editor.
Your file has to end at offset 0x01ec0000
or wait until I make osimagetool less strict. ( which might not be soon )
Click to expand...
Click to collapse
Would you mind editing it for me if I sent the file to you? I could let you ftp the file and then replace it. I need to get this device in for repair because my contract is almost up... in less than a month. Thanks.
ok, better do some programming than fileeditting.
update is at http://www.xs4all.nl/~itsme/download/oit_105.zip
you have to start it with a commandline option '-f' to disable filesize checking.
Still no good. Now I get ... Error writing 00008000 bytes to 00b18400: Data error (cyclic redundancy check). I've tried two different T-Mobile images from two totally different people and the files are the same size, and they both get the exact same error. Any ideas?
when does this error occur? in osimagetool?
this would point to a faulty sd card I think.
It happens mid way through the load in OSImage Tool... loading to the SD Card. I've been using this card for a year... just about full of stuff... and never had a problem before. Even used XDArit to grab an image from my XDA, and to load the XDA Developers ROM onto it. I'll see if I can get another card. Thanks for trying help me figure this out. I may try the card in a store on a display unit and see if I can grab an image with the bootloader.
Hi folks
I have the same problem that Mike had - the one with the wrong filesize.
Unfortunately the posted link to the updated version of OSImagetool is down. Is there any chance someone could fix that?
Thank you very much in advance.
Chris
hippokrates said:
Hi folks
I have the same problem that Mike had - the one with the wrong filesize.
Unfortunately the posted link to the updated version of OSImagetool is down. Is there any chance someone could fix that?
Thank you very much in advance.
Chris
Click to expand...
Click to collapse
You can get it at:
http://xda-developers.com/~itsme/download/oit_105.zip
HTH
Stefan
Vielen Dank / Thank you very much it worked just perfect.
By the way, this could also be interesting for you Stefan: the reason I was searching for the OSImage Tool was because of the german ROM 4.00.33 Mathias was so kind to share. It is the first german version I could get my hands on and i now have the good old qwertz-keyboard back.
Mabye Jeff or someone else could put it into the kitchen for all german/swiss/austrian XDA users ??? I would think a lot of people would appreciate this.
Chris
Hello,
i do something wrong,
i start the HimaClearJumpCode.exe on my XDAII, and now
the XDA always in the USB/Serial V1.01 mode and any
reset or remove battery don't restart.
could someone have a idea how to reset it?
Regards
Markus
Why do you start this file ????
AFAIK this file is used during the update-process by the
HimalayUpgrade and should never be used manually.
And AFAIK it definitly thrashes your as it jumps into the bootloader.
Try to describe what you want to do !!!
Alex
you can restore your device by running the HimeUpgradeUt.exe with the xda2 cradled. it will take a minute orso before it starts.
by running the HimaClearJumpCode.exe you have erased the first 256k of your rom.
normally this is done by the upgrade tool, which first makes a backup of this part of the rom ( 80040000-80080000 ) to the top 256k ( 81fc0000-82000000 )
then runs HimaClearJumpCode.exe, then resets the device, to enter the bootloader.
and after it is done flashing other parts, it copies back the saved rom part.
itsme said:
you can restore your device by running the HimeUpgradeUt.exe with the xda2 cradled. it will take a minute orso before it starts.
by running the HimaClearJumpCode.exe you have erased the first 256k of your rom.
normally this is done by the upgrade tool, which first makes a backup of this part of the rom ( 80040000-80080000 ) to the top 256k ( 81fc0000-82000000 )
then runs HimaClearJumpCode.exe, then resets the device, to enter the bootloader.
and after it is done flashing other parts, it copies back the saved rom part.
Click to expand...
Click to collapse
hi, I am one of those stupids who did this **** again. In the restoring method, u mentioned that one has to run the HimeUpgradeUt.exe with xda2 cradled. U didn't mention if i need to have the Extended ROM in the same folder where HimeUpgradeUt.exe resides. Do I need to do place the Extended ROM image(.nbf) to that folder. If so, please suggest me a appropriate English Extended ROM name. I have searched at the ftp but unfortunately I could hardly understand by the naming of the ROM on the ftp. I want my XDAII back. please help.
upol said:
hi, I am one of those stupids who did this **** again. In the restoring method, u mentioned that one has to run the HimeUpgradeUt.exe with xda2 cradled. U didn't mention if i need to have the Extended ROM in the same folder where HimeUpgradeUt.exe resides. Do I need to do place the Extended ROM image(.nbf) to that folder. If so, please suggest me a appropriate English Extended ROM name. I have searched at the ftp but unfortunately I could hardly understand by the naming of the ROM on the ftp. I want my XDAII back. please help.
Click to expand...
Click to collapse
extROM is different part. You can update without extROM
If you want to patch any ROM like the one of Alex Anansky...
...download my aplicatión and do it now!!
It's so easy... read the instructions in the file "HowTo.txt".
Bye ;-)
Something tells me that something's fishy here.
Some guy from nowhere with only 4 posts comes up with a "breakthrough" utility and doesn't give any explanation but "download my aplicatión[sic]... Bye!"
The attachment's removed now (not by me).
OK... you lose it...
If somebody want's it... Follow this...
http://www.todophonedition.com/modules.php?name=Forums&file=viewtopic&p=4808#4808
It's a spanish site about PhoneEdition PDA's... I moderate the programing forum.
Bye
MKS,
could you explain more on how it works!
I apologize if I sounded harsh, but this site has gone through a lot of problems from individuals repeatedly deleting things off the FTP, spamming or advertising for porn in the threads, and more.
This site needs to be moderated or protected a little better if it's going to thrive. It needs good people with good understanding, patience, and the willingness to share so we can get things that our manufacturers are not providing properly.
So, thank you for the attachment and link as I will test it out shortly.
Now come on, tell us something about you and how you did it. Or did you only find it yourself? If so: where?
So with this i can add and remove any Ext rom i want?
If that so, then its great!! now i can add IIWPO and Ext rom?
Can i?
the strange thing is if i rename any file to rom.nb1 and run the program, it will create a file with the size of 63MB rom file... is that normal MKS?
Just remember that the NB1 file will have to be 64MB since your Magician/JAM's ROM size is 64MB and it will SD-flash everything, from the CE portion to the Radio to the Extended ROM and Storage area.
Oh! it is necessary to obtain a Microsoft Certificate to upLoad some aplicatións here? :lol:
OK... I do not send many mensages in this forum... but I have been reading it for a long time... watch my date of registry. :wink:
Well, first... The size of the file is correct. Magician ROM does not occupy exactly 64Mb.
When you download the ROM to one 64Mb SD card, a few bytes at the end are single to fill the SD size. But these bytes are not necessary.
The ROM really finishes in the string "HTCE" before arriving at the 64 Mb.
I have trimmed the resulting file to do it easier to handle.
OK...This is everything at the moment. This weekend I have much work... In the next week I tell more to you.
It is possible that I even sends the source code to you too :wink:
Bye.
thanx alot for the HOWTO-method on "bigStorage" 8)
you have compared between original nb1 and the hacked one then you figured out the Anansky's code
NightmarE said:
you have compared between original nb1 and the hacked one then you figured out the Anansky's code
Click to expand...
Click to collapse
Yes, something similar to that... But it's not so simple. I need some info from the xdaDevelopers WIKI's too. And a lot of tests over my Magician with diferent ROM versions & languages.
Probably in the next week I will upload the source code.
Bye :wink: .
Great job dude :wink:
I'm downloading the file now... and I can't wait to create my own BIG-Storage ROM
cheers
MKS said:
Yes, something similar to that... But it's not so simple.
Click to expand...
Click to collapse
i have some tips to get the code in 5 seconds :wink:, but the hard part is to get the idea... 8)
Hi MKS,
I tried yr program on my Imate w/ Traditional Chinese "Dopod818_1110_153_11100_Ship" Rom and it doesn't work.
Steps that I did
1. Back up the Dopod TC rom to my 256mb SD using romupdate.exe w/ d2s command
2. use ntrw to write the rom on my hd
3. using yr program to modify the rom
4. write the modified rom back to the SD
5. The Jam report Section = 1 error and doesn't start the flash
6. Therefore, I copy the first 416 byte from the original Dodpod TC to the modified rom
7. The Jam start flashing. But after it reach 100%, it report download error and checksum error.
Now, I need to roll back to my original rom.......
Rgds,
Jack
Has anyone successfully used this to make a bigstorage ROM?
im having trouble backing up my original rom. after the the check sum ok part i took the sd card out of the phone and into a card reader. i run the ntrw read backup.nb1 f: and it gave me an error. it says "cyclic redundancy check" i see that on drive see it has created a file called backup.nb1 but it is 0 bytes. does anyone know what im doing wrong?
dacmo said:
Has anyone successfully used this to make a bigstorage ROM?
Click to expand...
Click to collapse
Just to let you know that I have successfully used this to make a bigstorage for the new O2 ROM I downloaded from seeo2.com last night. Nice splash screen MKS Many thanks.
test123456 said:
dacmo said:
Has anyone successfully used this to make a bigstorage ROM?
Click to expand...
Click to collapse
Just to let you know that I have successfully used this to make a bigstorage for the new O2 ROM I downloaded from seeo2.com last night. Nice splash screen MKS Many thanks.
Click to expand...
Click to collapse
Also just to let you know that I forgot to patch 416 bytes from O2 ROM into MKS ROM but it worked OK (cuz this is the first time I flashed ROM for my O2 mini ). Now I will do it again after patching 416 bytes from O2 ROM. Will let you know how I go...
Please check it out from xda-dev's ftp server.
what is the procedure to backup the radio alone?? please let me know
What is the instructions to "load" this radio rom to magician?
ya thats what I meant to
why is this radio smaller than all of the others? is it safe
To backup radio rom:
enter bootloader mode and in mtty issue command:
d2s 60000000 300000
this will dump radio rom to SD card then use ntrw or winhex to save backup in PC. End of backup file is HTCE in ASCI (48 54 43 45 hex).
To write 1.13 radio, you have to replace 444 first bytes (1BC hex) in file using bytes from your backup. Write file to SD card using ntrw or winhex. Put SD card to PPC and enter bootloader mode, it will ask you to press power button to procede flashing. I think it will work this way but I'm not 100% shure! Be extremely carefull you can destroy your device!
shamus is right. People in China have flashed the radio ROM to 1.13 using this method. If you can read Chinese, you can find details in the link:
http://www.hi-pda.com/forum/viewthread.php?tid=263959&fpage=1&sid=pIA2Ts
I have already upgraded mine to radio 1.13. The sound volume seems to be much louder and so far, there has been no GPRS error, etc.
I can confirm my speculations 1.13 radio ROM works on my MDA Compact now :twisted:
thanks for the instructions it worked perfect. once again I am at the forefront of convergance technology, for a few minuets :lol:
I'm not sure about this procedure hard-resetting my device after a (succesfull) flash. Will the Radio-ROM-only update cause a hard-reset, or will all my data be intact afterwards?
@Jainoxi: Once you entered bootloader mode all your data is gone - no matter whether any flashing has taken place.
@shamus: Your successful message tempts me to try it myself. And it was also new to me, that Radio ROM could be backed up (as well as being flashed the low level way).
@Chatty: I thought that entering the bootloader would preserve the data. Just flashing would hard-reset... Oh well, have to make a full backup then
shamus said:
To backup radio rom:
... End of backup file is HTCE in ASCI (48 54 43 45 hex)....
Click to expand...
Click to collapse
Should I cut all data before this point, and discard the rest, or leave it like it is, and only change the first few bytes?
EDIT: Shamus, nevermind, figured it out. Just copy the first 444bytes from your saved Radio ROM to the new 1.13.00 ROM, and do nothing else to it
This sounds cool! Would be a dream come true to get rid of the GPRS problems! I rather wait for someone to make a cab and upload it though..
Forget about a .cab file. It's not gonna happen. But no doubt a normal ROM update with this new 1.13 Radio will soon be available, making life a lot easier
I took the 30 minutes out of my life, though, to do this update now. No problems whatsoever and it appears to be running just fine. But don't expect this to cure the GPRS problems. They seem to be related to the later versions of Caller ID and not the Radio, according to another thread on this site.
where is the new radio files?
they dont seem to be in the /Magician/Radio directory?
cheers....
awharton said:
where is the new radio files?
they dont seem to be in the /Magician/Radio directory?
cheers....
Click to expand...
Click to collapse
On the XDA-Dev FTP: /Uploads/Magician/radio1.13.0.sd.rar
I've completed this update succesfully as well. Running like a charm in the past hour
Could anyone post this radio on http://rapidshare.de/ or other similar (http) site ?
Because I have difficulties to access ftp.
Please, share It
Thanx in advance.
running:
d2s 60000000 00300000
doesnt seem to do anything. when u rin just d2s it dumps the whole ROM. What am I doing wrong?
cheers...
You must write the command in the window, not just cut and paste...
awharton try to type d2s 60000000 300000
Hi everybody,
I would like to extract the original SPL from my Kaiser.
After reading some posts, I suppose I have to use pmemdump, but you need to specify an offset and a lenght in bytes.
Can someone tell me the right parameters for the kaiser, please?
Info from the bootloader:
KAIS130
SPL-1.94.0000
CPLD-8
Thanks in advance
Any special reason beside brick your device ?
Pisca said:
Any special reason beside brick your device ?
Click to expand...
Click to collapse
Hi,
maybe I misunderstand the posts I've read, but I don't see any warning on the risk of bricking the device.
For example I saw this in reply to how to dump the SPL from the HTC Touch:
"use pmemdump from itsme's utils.
Code:
pmemdump 0x88000000 0x80000 spl.nb
The address might not be 0x88000000, if not, try 0x9c000000 instead. I'll try and remeber to check the offset tonight .
Dave"
Is the risk real instead?
I think the size should be only 0x40000, because Kaiser has only 256kB SPL IIRC. Not sure about the address though...
OndraSter said:
I think the size should be only 0x40000, because Kaiser has only 256kB SPL IIRC. Not sure about the address though...
Click to expand...
Click to collapse
Thanks for the info.
I'll do some more investigation to find the correct address.
Can you confirm me that I risk to brick the device, as posted above ?
I'm not sure there is any way to brick your device, it is just dumping memory, not writing to NAND
When I mention bkicking your device that's because SPl it's a very delicate place to mess around, and I never see anything about dumping SPL for any reason, but I might be wrong
You can dump SPL by either JTAG or from memory. Because when phone boots and SPL starts, it gets copied to RAM as first thing and gets executed from there. And pmemdump dumps from there, you can dump whole RAM via pmemdump I bet. It just reads memory from some base address for some length and saves to file . It shouldn't touch NAND at all.