As I couldn't find a MiniSD (less than 2Gbytes, impossible where I live) I worked on re-flashing my Comet back to the German ROM using USB.
1. Downloaded the Comet ROM + Extended Rom files that Scorpio had placed in rapidshare
2. Executed the DSUU for Atom Life (WWE 20070914) and cut the 12 header bytes from both "FLASH.dio" and "ExRom.img" and pasted those 12 bytes in the German Comet AL1.dio and ExRom.img, and renamed AL1.dio to FLASH.dio
3. Placed the patched German files in the DSUU temp directory, replacing the original WWE files (c:\windows\temp)
4. Instructed DSUU to proceed as normal
5. The deviced cold-booted after finishing and worked.
So, flashing vía USB can be achieved by means of re-using the 12 bytes of both headers (it might be needed depending on the original ROM, to either edit Pass.32 or to hold down the "arrow key" of the PC at the initial stages of DSUU to skip the CID check).
Of course, this has not cured my "Radio ROM" problem, as my XDA Comet still has the WWE Atom Life Radio Rom, which does not work on Comet devices.
I will now work in finding a way (shall it exist) to dump the Radio Rom (I have already got itsutils and executed pdocread a couple of times).
Best regards
Hi
Maybe you can dump the radiorom with haret.
Unfortunetly I have not the knowledge to help you in these job.
You flashed the complete update with replaced files ?
Or did you flash OS and ExtROM only ?
I flashed the complete upgrade.
I did so because I had already flashed the complete WWE Atom Life upgrade, so in my case it made no difference, to put all these extra files back into the device, as they were already there!!!
But if we manage to find out which files affect the GSM/Radio part (and we also find out how to dump radio roms), it might be that we end up with a clear process to update Comet/Life with different ROMs using USB.
P.D.
I did my best into getting a 512 Mbytes MiniSD, but MediaMarkt, Saturn and smaller shops did not have anything so small. They were basically focusing on SD or MicroSD. I think MiniSD may end up as a dead technology.
pepelu456 said:
P.D.
I did my best into getting a 512 Mbytes MiniSD, but MediaMarkt, Saturn and smaller shops did not have anything so small. They were basically focusing on SD or MicroSD. I think MiniSD may end up as a dead technology.
Click to expand...
Click to collapse
You can try a bigger card. If it will be recognized, you can flash with this one.
I don't think, that the device will be damaged.
But I haven't test it.
PS:
I played with pdocread and the following command dumps a part, contained the bootloader.
As I said I don't know how to use pdocread to dump a specified part, but maybe this is a small hint, how you can use this tool.
pdocread.exe -n 0 0x00000000 0xFFFFFFFF -b 0x100000 File_out.bin
Click to expand...
Click to collapse
I belive, if you can dump the bootloader, you can also dump the radiorom.
I hope you have success to lokate the Radiorom.
If I can help to dump the radio, PM me.
I'm not sure, but if you choose in BL:
(5) Burn MOT/BL via UART
and insert a MiniSD, it appered the messages "couldn't find parti.mbn , amsshd.mbn and amss.mbn.
amss.mbn must be the RadioROM.
Your pdocread command works in my mixed WWE-GER device too and dumps te bootloader.
Trying to access binary partition 1 delivers the following error:
"Invalid controler"
Trying to access binary partition 2 delivers the following:
-- Once again the same dump of the bootloader.
--------------------
I also think that it should be possible to dump the Radio ROM, as DSUU is able to report the "date" of the Radio ROM file, whereas WM6 is unable to communicate with the Radio Stack.
Of course, the obvious (not necessarily true) reasoning is that WM6 is trying to use standard API calls that are failing whereas DSUU is accesing the ROM files before going into bootloader mode (when the user decides to execute the upgrade)
HARET fails to dump anything over 4Kbytes with a "short write to disk detected" (it will sometimes not write a single byte down)
Both behaviours may be caused by lack of adaptation to this specific hardware platform.
Regards
P.D.
I really find it unbelievable that the Atom Life has had so little hacking, taking into account that it has been sold by O2 Asia for quite a while, but even looking at Chinese forums (no, I can't speak chinese), they don't seem to be any more advanced than we are.
pepelu456 said:
As I couldn't find a MiniSD (less than 2Gbytes, impossible where I live) I worked on re-flashing my Comet back to the German ROM using USB.
1. Downloaded the Comet ROM + Extended Rom files that Scorpio had placed in rapidshare
Click to expand...
Click to collapse
Pls help, where you can have that comet ROM and Extended Rom.
Thank you.
Dear pepelu456,
I got your same situation. Now, so sad cannot repair.
pepelu456 said:
As I couldn't find a MiniSD (less than 2Gbytes, impossible where I live) I worked on re-flashing my Comet back to the German ROM using USB.
1. Downloaded the Comet ROM + Extended Rom files that Scorpio had placed in rapidshare
2. Executed the DSUU for Atom Life (WWE 20070914) and cut the 12 header bytes from both "FLASH.dio" and "ExRom.img" and pasted those 12 bytes in the German Comet AL1.dio and ExRom.img, and renamed AL1.dio to FLASH.dio
3. Placed the patched German files in the DSUU temp directory, replacing the original WWE files (c:\windows\temp)
4. Instructed DSUU to proceed as normal
5. The deviced cold-booted after finishing and worked.
So, flashing vía USB can be achieved by means of re-using the 12 bytes of both headers (it might be needed depending on the original ROM, to either edit Pass.32 or to hold down the "arrow key" of the PC at the initial stages of DSUU to skip the CID check).
Of course, this has not cured my "Radio ROM" problem, as my XDA Comet still has the WWE Atom Life Radio Rom, which does not work on Comet devices.
I will now work in finding a way (shall it exist) to dump the Radio Rom (I have already got itsutils and executed pdocread a couple of times).
Best regards
Click to expand...
Click to collapse
hi,
u said that we can flash via usb i have atom life purchased from middle east it have wm5 pre-installed , i entered www.seeo2.com and saw that there is an upgrade to wm6 so i downloaded the file an started the update process when detecting device it says ID ERROR, is threr a solution for this problem , and something else i flashed the wm6 rom via SD i took from temp folder in windows and removed the 12 headers , it flashed nice , but i want from the usb so that i can flash the radio files , ext rom , boot loader ...etc.
thnx
Yoou can find sth here for yr upgrade http://forum.xda-developers.com/showthread.php?t=378616
it didnt work for me changed the pass.32 no use i think i cant upgrade via usb
Try this http://www.myxda.com/xda-atom-life_wm6_oct2007ara.aspx
hi i need hel.. plese
i have a o2 comet and mi radio is gone after rom update mwg... plese scorpio could u help me with the original o2 comet files to restore gsm module, i'll be forever in your dept... i sherched everywhere even on ur blog, rapidshare, google, tryed everi original atom life rom, bu evrithig works with other rosms exept radio gsm, plese help me with the files ... i try upgrading rom becouse batery life was lousy. plese help...
the same problem
ion_plugged said:
i have a o2 comet and mi radio is gone after rom update mwg...
Click to expand...
Click to collapse
I have exactly the same problem. Even already try to receive update from service centre... answer was: "we need you device to test and... for repair app cost 100eur and more"
If some one can help us... please help!!!
count me in this list i have the same issue lost radio and imei and i don't have O2 in my country
Related
I have the T-Mobile ROM 1.60 currently installed on my I-Mate. Now I am trying to install the latest I-Mate update, I keep getting Country ID Error 120. Anyone know a solution? It seems we need some kind of AdaptROM...
The same for me yesterday ERROR 120, I try anyway but no results
I think that new ROM only for I- mate Device with special IMEI Number :evil:
Any ideas? :?:
I upgrade to i-mate update and I try to upgrade to T-Mobile I get the same error!!
anyone can help?
try to hard way...
unzip the ruu15283wwe_cdl.exe file,
you'll find there the *.nbf files.
Use the files to flash with SD card.
I'm not sure if this also works with the XDA II, but try XDATools:
http://www.xda-developers.com/XDAtools/
tomerbn said:
try to hard way...
unzip the ruu15283wwe_cdl.exe file,
you'll find there the *.nbf files.
Use the files to flash with SD card.
I'm not sure if this also works with the XDA II, but try XDATools:
http://www.xda-developers.com/XDAtools/
Click to expand...
Click to collapse
It seems not possible by writing just writing the nbf to SD card and flash to the XDA 2 anymore.
Because the bootloader will check the first 412 bytes (i believe it is the code on the last line of the 412 bytes, somthing like HTCSA00400000XXXXXXXX.............) of the rom on the SD card match with your machine or not. Therefore without any modification, only the ROM dump from the Machine itself can be flashed.
Moreover, nbf is encoded, you can't just edit it by HEX editor, you have to get the rom in nb1 format.
I think XDA developers have to develop new tools to
1. Get the first 412 byte of the rom from your machine in an easier way. Now we have to use Multiport / USB TTY get into bootloader console, dump the rom to SD card , and use ntrw read the SD Raw data to the computer to get this 412 byte. You need a HEX Editor to do so. (Please correct me if I said something wrong).
We can
a) develop an APP to get the 412bytes from SD to harddisk without using a HEX editor
b) directly read this 412 bytes from the XDA2 if possible.
2. A Rom tools that can add your machine's own first 412bytes (or the code) , combine it with a .nb1 or .nbf and write it to a SD card.
By the way , I think a new adoptrom support XDA2 will be the best solution 8)
note added by itsme: this will very likely break your devie!! - better look at sdtool
same problem
i'm having the same problem, installed imate update, now i cant install the t-mobile update.
nobody seems to know how to fix this
HEEEEEEEEEEEEELLLLLLLLPPPPPP
try this
Hi,
another idea... :idea:
try to unzip (using winrar i.e.) the file ruu15283wwe_cdl.exe,
and run the HimaUpgradeUt.exe
It might work!
I got error, the device is not connected, or something like that, while trying to use the original file, but with the HimaUpgradeUt it works!
Tomer
Check this out http://forum.xda-developers.com/viewtopic.php?t=4785
First it was a Phone, then it became a computer phone, now it is camera computer phone... what will be the next?
Click to expand...
Click to collapse
A camera computer phone with a stable, reliable OS? Oh well, we can dream....
Hi Folks,
o2 Germany has now published an upgrade to ROM version 1.60.52 GER.
http://hilfe.o2online.de/srvs/DATA/...download/xda_software/neu/xda_16052ger_o2.exe
THIS VERSION IS GERMAN ONLY (ALTHOUGH INSTALLER IS IN ENGLISH), SO ONLY UPGRADE WHEN YOU HAVE A GOOD COMMAND OF THE GERMAN LANGUAGE OR INTEND TO STUDY ANOTHER FOREIGN LANGUAGE!
o2 kept us waiting for a long time, but it looks like it was worth waiting and some old problems (like HZ-Indicator; Bluetooth etc.) have been fixed (at least they tried to!).
Have fun, any comments on the new version are highly appreciated!
bobpopo
Hi!
when i extract extended ROM image file, it can't be accesed by ROM editor from Wiki.. what's wrong?
now that we have thsi update, the question is: do we get a wm2k3se update and if so, when?
Um... is the language in german, or in english, or can it be switched to english?
First Upgrade leads to "Country Error" - Downgrade
After reading some postings in a German forum I already knew about the problem for those using XDAII with T-Mobile ROM 1.60.00 GER:
The update program won't start, displaying "Country error" (or sth. like that). This problem is solved by downgrading to T-Mobile 1.03.00 (which can be downloaded on the same page as the upgrade). After that upgrade works fine, leading to:
ROM-Version: 1.60.00GER
ROM-Date: 12/03/03
Radio-Stack: 1.10.00
Protokoll-Vers: 1337.18
ExtROM-Vers: 1.60.52 (attached)
Compared to the German T-Mobile 1.60 ROM, the radio stack seems to be improved (from 1.06.01 to 1.10.00) and the o2 ExtROm was updated (from 1.03.27 to 1.60.52). Also some good news for the o2 subscribers in Germany using the XDAII: The Homezone control seems to be fixed -until now I did not spot any problems.
Enjoy (and report bugs)...
HI Is this safe to use on the UK XDA II?
Should I wait until the uk release?
The only thing that I am waiting for mainly is a Bluetooth handsfree profile.
@oliven_99
How's your german... 'cause this is a true german update ;-)
links für downgrade pls
"The update program won't start, displaying "Country error" (or sth. like that). This problem is solved by downgrading to T-Mobile 1.03.00 (which can be downloaded on the same page as the upgrade). After that upgrade works fine "
Where can we download T-Mobile 1.03.00
Pls post the link for the german T-Mobile 1.03.00 downgrade because I also got the Country Error!
http://www.t-mobile.de/downloads/company/t-mobile/mda_2_ver_10305.zip
But remember: Downgrade and Upgrade is in German!
It works
Many Thanks!
Does anyone knoews why the ext. ROM Version 1.60.52 GER can not be opened, edited with Windows Mobile 2003 ROM Editor from Wiki?
Homezone Indicator
Cool!!!
The homezone indicator seems now to work stable!
Well done, O2 Germany
CAUTION!!!
Today I got shocked when I tried to modify the ExtROM and almost ruined it. After the common way with ER2003edit did not work out, I tried to downgrade the ExtROM to 1.03.05 (T-Mobile) with the old HimaUpgradeUt that came with that version.
After doing that, the XDA did not work anymore, just showing "serial USB 1.1". After that I tried to flash my cooked ExtROM (merger out of the latest ExtROM and some other cabs), what left my XDA still without function. Then slowly panic arose and I flashed the latest, complete upgrade (1.60.52) again, what led to a standard & working XDAII.
Now I am happy that I did not ruin the device, but still looking for a way to modify the ExtROM. Maybe it is time for those who really know what they are doing to give a little hint to the masses, how this can be solved...
INSTRUCTIONS: Homecooked (locked) ExtROM with o2 GER 1.60.52
Okay, finally I figured out, how to flash the new version with my own ExtROM:
If you are upgrading your XDAII from the MDAII 1.60 ROM, please prepare your XDAII for flashing by downgrading to MDAII 1.03 ROM as explained above. Otherwise you will get a country error.
1. download xda_16052ger_o2.exe from o2 Germany
http://hilfe.o2online.de/srvs/DATA/...download/xda_software/neu/xda_16052ger_o2.exe
2. download ER2003Edit
http://wiki.xda-developers.com/wiki/ER2003Edit
3. download tool Decode extended ROM below (thanks Jos!)
4. use WinRAR to extract the upgrade files from xda_16052ger_o2.exe (you'll get six files: 3 Hima* and 3 *.nbf)
5. unzip files from Decode extended ROM to a separate folder and add ms_.nbf (from step 4) and run decode.bat
6. after decoding, you can open the file ms_.nbf with ER2003Edit, modify the ExtROM-Files and splash images.
7. after modifying, save and run encode.bat, but only perform the encoding step, afterwards copy ms_.nbf back to the files extracted in step 4
8. now start HimaUpgradeUt.exe and flash XDAII as usual, but with your individual ExtROM
(According O2 this step can take up to 1 1/2 hours!)
This upgrade worked out with my German XDAII with (locked) ExtROM. In former versions of the upgrade utility it was possible, to upgrade the ExtROM only, one just had to remove the unwanted *.nbf before upgrading. But now it looks like only a full upgrade will lead to a working XDAII. Otherwise it will be dead but can be recoverd by giving a full upgrade with all three parts.
I will certainly only be held liable for ruining my own XDAII - what you do to your gemstone is on your own risk. There might be easier ways, please drop a note if you find one...
New splash screen...
Just to make it complete:
While installing the new ROM I noticed that there is a second splash image, which is changed to the old one after executing O2DECustomize.sa.CAB. As I liked that new splash screen better, I have changed it within the cab file and removed some other useless example files.
Just replace the old O2DECustomize.sa.CAB in your ExtROM with the one below or copy to and execute on your XDAII to change splash screen (will stay until the next hardreset).
The RSB-Converter is just a tool that I found while waiting for ages to get a trial key for ACDSee. Take this tool if you want to convert your individual splash screeen to the required RSB format. Find further information on creating individual splash screen here:
http://forum.xda-developers.com/viewtopic.php?t=3759&highlight=splash1+nb
After creating your favorite splash image (as *.bmp, 24 bit) cut 13 pixel from the left side of the picture and paste it to the right side (after moving the big part to the left). If you don't do that your splash won't fit the screen properly.
Hi all
For those how what to save close to 2MB space in their ext-rom I have a set of updated files
O2_DE_custimized has additional the settings made in
Broadcast_GER
MIDI_GER_reg
O2_AP_DE_20040118
O2_DE
version_AKU1 which you don't need anymore.
removed is O2 movie, spash images, and O2 ringtone
additonal the regfile makes the ext-rom visible and activates cleartype by default.
CameraRD132_GER removed help file and button graphic
ClearVue233_GER removed ads/demo files
regards, Alex
At the german forum "ppc-welt-community" a user reported, that he tried the update with his xda1 an the upgrate worked.
I doubt about this...what do you mean? Should it be possible to upgrade the xda1?
:?
Hey, I found the entry in the forum, there is no way written that somebody actually manged it or was so stupid to try it.
I think it won't even start, as the bootloader are not the same and the UpgradeUtility will (hopefully) not start at all.
There is an upgrade to WindwosMobile2003 for XDAI this is what he writes about, this is not the upgrade which is here talked about.
Alex
Re: New splash screen...
bobopopo said:
The RSB-Converter is just a tool that I found while waiting for ages to get a trial key for ACDSee. Take this tool if you want to convert your individual splash screeen to the required RSB format.
Click to expand...
Click to collapse
Tried to convert a *.rsb File and got:
"RSB Version not supported"
is there anything i do wrong or cant the program convert all files?
any ideas.....
Re: New splash screen...
Know that I had the same problem, doesn´t always work. But it is so long ago, that I cannot remember clearly, sorry...
pbelcl said:
bobopopo said:
The RSB-Converter is just a tool that I found while waiting for ages to get a trial key for ACDSee. Take this tool if you want to convert your individual splash screeen to the required RSB format.
Click to expand...
Click to collapse
Tried to convert a *.rsb File and got:
"RSB Version not supported"
is there anything i do wrong or cant the program convert all files?
any ideas.....
Click to expand...
Click to collapse
First I appologize for the delay in the availability of this ROM. I was out of town on some business, and the site was down again for a certain time.
To get down to the details, this ROM is the complete set of all three .nbf files, I chose the 2.06 NK.nbf because the cleartype fonts are way better than the 2.02. The radio stack included is version 1.18, and the extended ROM (ms_.nbf) is a customized 2.06.100a, which is a mixture of the extended ROM that dcs posted, the one that came with the 2.06 ROM from the mystery guy and the official Asian 1.60.44 ROM.
I had to remove a couple of the Asian telco provider settings because there was no more space left in the extended ROM since the new versions of the software had larger file sizes than before, and the AutoConfig for Asian telcos alone takes up a lot of space too.
I still included the Extended ROM Viewer and almost all of the newer versions of the software included in the extended ROMs posted by dcs and the mystery guy.
The following telco providers were removed (due to their file sizes being the largest):
1. 1010
2. One2Free
The Socket SDIO Wi-Fi that were available in the previous ROM I posted were also removed due to the lack of space, the SPB GPRS Monitor that was provided as part of one of the extended ROMs posted was also removed. The thumbpad driver is in the extended ROM but does not auto-install, since some times it causes problems, you may install it separately by just clicking on the cab file.
The files removed are included in the .ZIP file so that they may be installed separately if desired.
I would like to thank dcs,mamaich, the mystery man and all other developers who contributed to this endeavor.
RE
Hi ZeroXtreme!
Thank you very much!
Could you post the breakdown of the content here?
Thank you again
Nice work ZeroXtreme
ZeroExtreme is my hero !
Customized ROM Content
NK.nbf = 2.06 (Mystery Man)
Radio_.nbf = 1.18 (dcs)
ms_.nbf = 2.06.100a (Mixed with dcs ms_.nbf, Mystery Man ROM and official Asian 1.60.44)
Extended ROM Contents:
CameraRC141_WWE.sa.CAB
MIDI561.sa.CAB
CprogHook.WM2003_2577.CAB
LoadDialogInit_MS_10150402.sa.CAB
MMS_v2.0.0.13_BA_WWE_0831.CAB
Caller_ID_WWE_RC10.CAB
EmailWiz_v1.01.0003_NL_1027.CAB
IntelliDialer_T-Mobile_WWE_RC10.CAB
IntelliPad_TMO_WWE_B12.CAB
Version_OU.sa.CAB
ClearVue3.4.381WWE_0616_Ozonup.sa.CAB
Extended_ROM_viewer.CAB
sales_service.CAB
hk_html.CAB
BTPSKeyUpdate_003.exe
Autoconfig.txt
Autoconfig.exe
Autoconfig.exe
TPDisable.exe
TPEnable.exe
Also all of the Asian telco settings except the ones listed in the first post that were removed.
it'a Chinese version or English version?
cool thak a lots
Version
vbexpert said:
it'a Chinese version or English version?
Click to expand...
Click to collapse
Its an english version all the way.
Problem...
Hi Zero,
Would like to check with you.. I got this problem. After flashing everything, some how..after booting up.. there is this error.. "Connection Flash Manager" stating "Saved data is corrupted, System will erase all data to fix this error!" But even after i click yes.. the problem will still arise no matter when i softreset. Any idea what is going on?
Thanks
Ranma
Re: Problem...
RaNmA_ said:
Hi Zero,
Would like to check with you.. I got this problem. After flashing everything, some how..after booting up.. there is this error.. "Connection Flash Manager" stating "Saved data is corrupted, System will erase all data to fix this error!" But even after i click yes.. the problem will still arise no matter when i softreset. Any idea what is going on?
Thanks
Ranma
Click to expand...
Click to collapse
I am not too clear about the problem, you flashed your device with the ROM I posted?
This did not happen to me during the multiple times I flashed my device and my dad's device.
I am a bit puzzled here, can anyone help in this matter? ANy similar experiences?
It's so difficult to download! :? I must have tried at least 6 to 7 times. Each time it just stop there.
hi people, i m new to this forum and new to xda2. Just wondering, how do u guys download and load up all the upgrades? hope u pros can give me some pointers.... thanks in advance
Finally managed to download the file. Do I need to do anything before installing the new ROM?
I had once tried to upgrade my unit (blame it on initial enthusiasm, I'd seen all these talks about upgrading to newer ROM versions everywhere on the net that I downloaded an upgrade 2 weeks before I actually bought my device) with a ROM version I had downloaded from O2's UK (The unit was bought from singapore/Honkgkong...Asia ROM presumably)site which naturally and the consequenses were very depressing , I was left with a dead machine on my hands and nobody I knew could be of any help. Anyway that had been taken care of a couple of days back when it reflashed at an authorised service centre.
Well that being that , now that its working fine and now that I see all this talk about windows mobile 2003 SE here I have this irresistable urge to try upgrading mu unit to run SE.
A couple of things before I try to get adventurous
1)How do I do a backup of of EVERYTHING ON MY MACHINE ( Original BASIC/Just out of the box/First time run software included ) So that I don't have to take a week off work just to get the unit reflashed.
2) How do I do a restore all of the backed up data on my device if the 2003SE upgrade doesnt work? From what I have learnt , it isnt anything like a regular computer where just about anyone can format boot and reload windows if it crashes.
I figure a dead PPC is like a regular computer with a dead bios.
I can understand that this post is about 5 times the length of a usual post here but I just had to get all my backup plans in place before I jump off a cliff.
you can use either the x-backup in the xda itself and making a complete back up to your sd or mmc card or make a backup via active sync on the tools menu
where is the download link??
Anonymous said:
where is the download link??
Click to expand...
Click to collapse
You have to log in to see the download link :wink:
I have an xda II australian model, i want windows media player 10, can i use the chinese rom??
This is gonna be my first time to update the ROM of my device so some questions:
Did you include upgrade instructions on the zip?
How do I disable some of the .cab files on the extended rom? I dont like some of them.
Had any probs with this rom on Globe?
~ishtangli
What's the BT software on the new rom? Widcomm or MS?
It is possible - I've just done it. I'm away from home and I've been using my Hermes (with WM5 AKU 3.3) to get my iBook online all week. Finally WM6 has appeared but I'm stuck with no Windows PC to perform the upgrade...but XDA-Developers gave me all I needed to do it. Here's the outline of how to do it (you'll need to figure out some finer details yourself, but I will help where possible if you get stuck).
1) You need just the .nbh file from the WM6 package of your choice. Unfortunately they are built into Windows installers. I downloaded XDA-Live and extracted the .nbh file using Virtual PC.
2)
i) Backup your storage card.
ii) Format your storage card. (I used a program called "Storage Tools" for this).
ii) Rename the WM6 .nbh file to HERMIMG.nbh and copy it to the root of the empty storage card.
3) Get Des' SSPL program from this link:
http://forum.xda-developers.com/attachment.php?attachmentid=34184&d=1171162518
4) Put the SSPL executable on your phone and run it. Cross your fingers. The phone should enter the bootloader and offer to upgrade the OS using the image it finds on the storage card.
And that's it. Once I'd figured this out, the method is straighforward. The part that has taken me all day is getting the image file extracted from a Windows world and onto a blank storage card using only a Mac and the phone itself (and no other internet connection)!
Hope this is useful to someone else.
Edit: typo.
Great! This method is much safe than other methods that depends on USB because you don't have to worry about someone unplug the USB cable, or if the PC will hang during the flashing process.
Maybe the only thing to check is to ensure that the device to have enough battery for flashing
BTW, how long will it takes for this SD upgrade method?
Brilliant!
Very ingenious solution! I'm not ready to flash yet, I want to see some bugs worked out of the WM6, but when I'm ready will probably try it your way just to see how it works!
Ben
Awesome, I'm using Vista, and I don't want to install XP just to flash Thank you.
Will this work with the Universal? I'm getting Vista soon and I want to be able to reflash if I need to.
Thanks in advance.
ahlok_hk said:
BTW, how long will it takes for this SD upgrade method?
Click to expand...
Click to collapse
I didn't time it but I'd guess it only took about 5 minutes.
You CAN flash on Vista using regular ROM updaters (the .EXEs). That's how I upgraded to AKU 3.3 recently (I don't have an XP machine either).
You do it by connecting in bootloader mode so that "HTC USB Sync" appears in Vista's Device Manager. Then you replace that driver with the one from 2004 (I got mine off the CD that came with the phone). Then the ROM updater works
Now is there a way to exec the sspl.exe on boot? So that some of the bricked users can jump start into bootloader and flash any rom.
unfortunately not... sspl is a wince EXE.
Radio ROMS's
Does anyone know if the Radio only ROM's can be flashed by this method also. If you can do you name the .nbh file the same or use a different name.
You can flash any NBH file, radio os or whatever. But not extracted radio roms in NBF, only in NBH. The file must be named HERMIMG.nbh.
pof said:
You can flash any NBH file, radio os or whatever. But not extracted radio roms in NBF, only in NBH. The file must be named HERMIMG.nbh.
Click to expand...
Click to collapse
interesting... does that include unsigned updates??
walshieau said:
interesting... does that include unsigned updates??
Click to expand...
Click to collapse
Yes, but only with SSPL.... not with the real SPL on device.
pof said:
Yes, but only with SSPL.... not with the real SPL on device.
Click to expand...
Click to collapse
ok now back to the drawing board then... do you know whether the SPL can be forced into Service mode via the RomUpgradeUT.exe file... have been doing some digging around in the DLL's and EXE and found some info about a 'Service' mode....
walshieau said:
do you know whether the SPL can be forced into Service mode via the RomUpgradeUT.exe file... have been doing some digging around in the DLL's and EXE and found some info about a 'Service' mode....
Click to expand...
Click to collapse
Not sure if I understand your question.... the so called "service mode" is what we call "booltoader mode" or "tri-color screen".... just the same.
On normal RUU, the bootloader mode is invoked by EnterBootloader.exe, on custom RUU EnterBootloader.exe file has been replaced with SSPL-HERM.exe.
pof said:
Not sure if I understand your question.... the so called "service mode" is what we call "booltoader mode" or "tri-color screen".... just the same.
On normal RUU, the bootloader mode is invoked by EnterBootloader.exe, on custom RUU EnterBootloader.exe file has been replaced with SSPL-HERM.exe.
Click to expand...
Click to collapse
yes i know that BootLoader is a type of Service mode... i was talking about a different procedure... it looks like a command from the RomUpgradeUT file to signal the bootloader to just to flash the ROM and not check the RUU sig's, model type etc....
walshieau said:
i was talking about a different procedure... it looks like a command from the RomUpgradeUT file to signal the bootloader to just to flash the ROM and not check the RUU sig's, model type etc....
Click to expand...
Click to collapse
That's not possible with the normal IPL+SPL on device, load them on IDA Pro and you'll see what it exactly does, its small enough to follow all the disassembled code with the samsung manual in hand.
so......if i want to flash both radio and wm6,
all i have to do .. is to extract the nbh file from .exe using winrar or something and rename it, put it into a formated sd card.. and run the sspl thing and do the same for wm6 ?
yes hellokittyr, that's right.
Hi pof,
have you tried to digg into the radio ROM as well? Probably with the right manual in hand one could seperate the RBL from the rest and create a 1.35.00.11 radio ROM with RBL 0107.
References:
http://forum.xda-developers.com/showthread.php?p=1840788
http://forum.xda-developers.com/showthread.php?p=1684559&highlight=EBOOT.NB0#post1684559
chartreux said:
No, don't use the EBOOT from the ATOM EXEC(MN2). you must use MN1(from ATOM STD). I had attached it to you.
here is the step.
1. copy eboot.nb0 to your SD-CARD (in the root) and insert your card to your ATOM EXEC
2. preset camera+reset
3. you will see the progress status (wait until your device off)
4. TAKE out your SD-card
5. preset camera+reset again (you will see MN1 bootloader)
6. hook up your USB
7. run software update utility (you may use WM5 or WM6 EXEC ROM)
8. wait until 6% stack on extended ROM (you will see failed status on your bootloader screen during update ext ROM)
9. press on/off + reset perform hard reset
10. your windows will be up and able to sync with activesync. (your bootloader now MN2 again!!)
11. now you may perform the DSUU and this time your EXT rom will be update successfully.
12. delete EBOOT.bin from your SD card
13. done and enjoy.
please beware, you are playing the most dangerous part now.
Click to expand...
Click to collapse
Follow by the instruction.
I use the 2GB Mini SD card to flash the MN2 bootloader to MN1.
Before I copy the EBOOT.nb0, I format the MiniSD and I had confirmed the card can be read in AtomExec.
The screen display "transfer completed" after I inserted the MiniSD and press camera+reset.
After the message was shown, no response come out in next 3 - 5 minutes.
So I press camera+reset again.
The Atom Exec will load in MN2 bootloader again.
I got a trouble in step3.
I had tried the Atom EBOOT.nb0 & Atom Exec Offical WM5 EBOOT.nb0.
Both of them are same, after the message come out and nothing to do.
Any solution I can go back to WM5 ?
I'm can not stad for the AtomExec unable to use the Bluetooth headset while in phone call.
Try to use 256MB memorycard.
Is there can not use in 2 GB ??
it is because I have not 256 MB MINI SD......
admin88hk said:
Is there can not use in 2 GB ??
it is because I have not 256 MB MINI SD......
Click to expand...
Click to collapse
It's been proofed in WIKI and it's work. Try it.
Maybe the problem is you have to borrow 256MB or 512 MB
admin88hk said:
Is there can not use in 2 GB ??
it is because I have not 256 MB MINI SD......
Click to expand...
Click to collapse
For some brand, 2gb mini sd can't used for sdflashing. I have 2gb V-Gen and i can flashing with it.
do you know that can I use Kingston to do the flashing ??
to hiro77, thx for your reply, I am lookig for my friends which have 256MB Mini SD
SDflashing tested by me:
- 256MB: V-Gen/MCPro=OKE
- 512MB: V-Gen=OKE
- 1GB: V-Gen/MCPro=FORGET IT
- 2GB: V-Gen=OKE
Thank you very much for chartreux, hiro77, abusalza, katon808, tjlabais and homer.
I am using a 64 MB MiniSD Card succuessfully roll back to WM5 today.
All step are smoothly.
admin88hk said:
Thank you very much for chartreux, hiro77, abusalza, katon808, tjlabais and homer.
I am using a 64 MB MiniSD Card succuessfully roll back to WM5 today.
All step are smoothly.
Click to expand...
Click to collapse
Hi,
can you help me where I can download the Atom Exec WM5 EBOOT.nb0 file.
thanks
Same me
when i cannot find eBoot.nb0 form Office ROM.
I use eBoot.nb0 from Atom/Atom Pure WM 6.0 Kumara Touch New
Extract to folder.
-I copy it to 1 Gb Kingston MiniSD.
-Hard Reset I found my Atom Exec get MN1 Loader file.
-My Atom Exec Show Load eBoot and Ignore other. Cuase MiniSD Have 1 file only.
-when finish and show soft reset.
I remove my MiniSD and Camera+Softreset to MN1 boot loader mode.
-Connect to USB. Pc have sound 1 time.
-I use WM5 Office ROM upgrade it.
You will found error 6% in stage 3 Extended Rom.
Don't warry it's bug normally of WM5 Office ROM.
You must Hard Reset and Default Factory by CallKey+EndCallKey.
No Aligment, No Setting Time, when PC found new hardware.
You will try upgrade by WM5 Office ROM again for get Extended ROM and
other.
OK, Hard Reset for finish or Upgrade to WM 6.1 as Me.
today, I finding solution for upgrade my Atom Exec all time.
Cause I Noob for It. And my old PocketPC is Atom Black.
It's has upgrade flow differrence my old PocketPC.
But, This time i understand Atom Exec upgrade and Error 6% Now.
Hope, Your found the way for clear your problem.
The Power still with you.
mikomarco said:
Hi,
can you help me where I can download the Atom Exec WM5 EBOOT.nb0 file.
thanks
Click to expand...
Click to collapse
If you can read chinese you can find EBOOT.nb0 at here
otherwise you can find at here