Related
i have a O2 XDA II . it came loaded with 1.66WWE. i wanted to put 1.60. i downloaded it from sourceo2.com
then double clicked the installable. it started the downgrade . it said it will take 30mins & started deleted the rom image.. i then went for lunch & came back in 15mins.. the phones now totally dead.
If i dock it , the screen says USB V1.06
if i remove it the screen says Serial V1.06. I cant hard rest it nor can i soft reset it. i huess cause there no rom image in it.
What do i do.. please help with as many links software as one can..
Please...
ive got 1.72, but when i try that. it says country error.??
can that be resolved.. i dont mind loading 1.72.
the good news is that it seems you still have the boot loader working ... use ER2003 tool to modify the country code of the 1.72 ROM file ... or you can use the xda2nbftool.exe if you like the command line mode
thakns, but i have the 1.72 as an exe file. can i use er2003 to edit the file ??
hyper said:
thakns, but i have the 1.72 as an exe file. can i use er2003 to edit the file ??
Click to expand...
Click to collapse
Unpack the .exe file with winrar/winzip. And you're good to go.
Edit this file: ms_.nbf
managed to unpack it... now when i try to load 1.60 it says model id error & if i try to load 1.72 it says country id error.
what do i change in the ms_.nbf file ????
do i only change this file fields or all three??
i even removed the battery & checked the model ID. on my phone it says PH10B
i changed all the three files to PH10B ..
Now i get Connection Error.....
Now what???
now the error is ERROR 101... connection error.
(i'm loading 1.60)
also is it possible for me to do it via my emory card (i have a MMC32MB & 128MB)
if so, what file do i need to copy & then whats the procedure??
i got 1.03.00 rom on mine. my xda 2 is 2 days old now dunno wht rom to load it up with now. whts the best & safe rom now. i have no apps or nething to back up so its oki. the phone was bought from u.k. and was locked on O2 network. now its unlocked and being used in India. plz advise wht ROM to d/n and use. if possible the d/n link as well. thx
Question?
Why do you want to downgrade your phone? :shock:
For upgrade to 1.72:
1. Download i-mate 1.72 update and xda2nbftool
2. unpack that update to any directory on your harddrive
3. download script from this post to created directory (unpack it too)
4. copy xda2nbftool.exe to that directory
5. run provided script
6. insert XDA2 to cradle and then HimaUpgradeUt.exe
You will i-mate splash screen from i-mate though, but working device.
thanks for all the help. but im yet getting country ID error even after running the process .
this process basically converts the id to O2, in a batch dos mode... right??
then y is the problem yet there.
i wonder... most O2 XDA II come with 1.6 rom version. mine came with 1.66. could that mean its not O2 even though its written O2 on my phone? could it mean its T-Mobile or something??
can someone post a link or software that i need to put onto my MMC card & then use that to install the rom from the card inserted in the phone??
hyper said:
thanks for all the help. but im yet getting country ID error even after running the process .
this process basically converts the id to O2, in a batch dos mode... right??
then y is the problem yet there.
Click to expand...
Click to collapse
So, what's that problem? Can you run it?
Try to run it in command prompt... And if it writes any error, post it here...
Can you access the file system of your XDA2 from ActiveSync -> Explore?
now i managed to get the problem of Country error out of the way , but now im getting the ERROR 101 - Connection Error.
no i cannot browse any files & my active sync does not show connected.
what files do i need to copy paste onto my MMC card so that i can flash it by executing the files with the camera button & the MMC Card inserted??
im dowloading the NTRW & 1.72 NK.nb1 file. do i just copy & paste it on the mmc card & then instert the card into the phone & then press the camera button.. should this do the trick??
this is all that i have tried so far... yet no luck.
my phones originally from malaysia , its an O2 XDA II
i have the following rom with me. my bootloader is V1.06
1. RUU172800WWE_CDL_SKU1
2. XDA_IIupgrade_v16050
3. RUU172104wwe-t-mobile-uk
1. i removed the battery , dcoked the phone, connected the charger to the docking bay at the back...the red light on the phone lights up.... the bootloader screen shows up ina slightly distorted manner.
i then ran all the three roms as it is..without editing anthing. The error i get in all the three times is ERROR 101. CONNECTION ERROR. it tells me to check is usb is connected, charger is connected usb port is conencted & the phone is on. .......... everythings connected but obviously phone can only be in bootloader mode.
2. i put the battery back in dock the phone, the charger is yet connected to the back of the docking bay. .. i try all three installations withour extracting or editing as they are exe files..... now, all the three times i get COUNTRY ID ERROR OR MODEL ID ERROR.
3. when i edit the ones that give me model id error then i get CONNECTION ERROR AGAIN. (this is again with the battery in & charger plugged in)
i downloaded the NTRW & 1.72 NK.nb1 file. but the one that is available on this forum is corrupted. so i cannot extract it.
NTRW ive downloaded seperately. i need the nb1 file now. can someone post a working, no-corrupted image rom image file?
once i get the correct Rom.nb1 file... all i have to do it copy & paste the correct rom.nb1 & ntrw.exe file onto my MMC card & keep the battery in the phone & insert the MMC card & press the Camera button .... is that correct? i'm guessing that this will run the ntrw exe file & load (dump) the Rom.nb1 file onto the phone. is that correct?
please do let me know what else i can try & dowload a newer RUU or something. i think the best way is to SD flash the phone.
i dont even mind flashing it to a PPC2002 version & then upgrading it from there. if thats possible.
As far as the connection between the USB Docking Bay is concerned,...everytim i connect or disconnect the phone, i hear the familiar XP "TING" which shows that some USB thing is connected, but my active sync does not show that the phones connected, i guess that cause it got no rom in it.
Also when i edit the ms_ / NK / Rom files er2003 i get an error everytime i start the software, but i just press IGNORE & continue. i always get ROM successfully written & then the error pops up again but i keep pressing ignore. this works... but whats up with the CONNECTION ERROR. IF ITS NOT CONNECTING TO THE PHONE, HOW DOES IT KNOW THAT THE MODEL ID OR COUNTRY ID WRONG ???
Ok.
If any ROM update can detect your device (as we can see error messages COUNTRY ID ERROR or MODEL ID ERROR), there is hope, you can update your device.
If it's 1.72 ROM (that writes COUNTRY ID ERROR or MODEL ID ERROR), use the solution I send you few posts ago (unpacking, running batch script etc.)
When you updating, keep battery in your device and charger of device connected to cradle! Don't remove anything.
BTW: Don't use RUU172800WWE_CDL_SKU1 update, it just update only part of your device (ExtROM)!
BTW2: Read this: http://wiki.xda-developers.com/wiki/HimalayaRomFlashing
thanks againa beecher. the problem is that once i use the patch & then run it. it does not show me the country id or model id error (for which i thank you) but then it says error connecting.
i have a USB to serial connector. should i try serial connection?? or maybe try it on another computer.
can anyone please tell me how do to a SD flash step by step with the Rom.nb1 file attachment of link.
Hi guys,
I have to compliment Stefan for personally e-mailing me back about a problem I was having and pointing me here. Hopefully I can become a little less clueless through the forums.
When using kitchen, I get the ROM.EXE update. I understand I run this on my PC. My phone is a Wallaby, with WM2003 first edition. I've written down my t-mobile settings and I'm ready to flash it. However, when attempting to run the ROM.EXE program, I getting the following error:
Code:
ERROR 011: EXECUTE REMOTE COMMUNICATION PROGRAM ERROR
Cannot execute the remote communication progra,
Please make sure that the USB/Serial cable is properly connected.
The phone is connected to the PC directly over USB through it's cradle and I have ActivSync 3.7.1 running. Any ideas what my problem could be?[/code]
http://forum.xda-developers.com/vie...+remote+communication+program+programme+error
http://forum.xda-developers.com/vie...+remote+communication+program+programme+error
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
Stefan
Alrighty, after reading those, I figured I had to write the WM2k3SE ROM to a SD card. After extracing the NK.NBF from the ROM.EXE I have to a directory, I fire up the XDA OS IMAGE TOOL and select it in the SOURCE. I choose "SD CARD" for my destination and produce the following error:
Code:
NK.NBF: Incorrect Filesize(33554464), file size should be exactally 32505888 bytes. Error opening input file.
A quick search of the forums didn't show anything that might apply. According to these wiki instructions this looks like the correct thing to do. Is it possible that I have a bad kitchen rom?
Because of an different Memory Usage of the WM2003SE ROM, thes ROMs could only be flashed via EXE. OSImagetool used for writing this file to SD-Card reports an incorrect Filesize. If you have installed a T-Mobile ROM that prohibits upgrading via EXE-File (you get an error in the DOS-Box) you have to downgrade your phone to 3.17.03 via SD-Card and then use the WM2003SE ROM....
OK, but is the procedure I'm following correct? Download a WM2003FE ROM.EXE at version 3.17.03 and then extract the NK.NKF from the executable and flash with that? This will allow me to use the ROM.EXE of my WM2003SE kitchen image instead of using the OSI tool? (If this works, I'm going to go add to the wiki).
I am trying to capture the unlock of my M3100 to help the forum.
I followed the directions below...
fun_key said:
What you need befor you start:
USBMON (I used the trial): http://www.hhdsoftware.com/usbmon.html
A win 2k/XP computer with admin rights
How to fool the IMEI-CRACK tool:
-Login with the administrator and setup USBMON
-Create with the administrator a user (named wathever you like) with only "user" or "powered user" rights
-Log in with the user you just created (you may have to resetup Active sync with this user; I don't know why but it seems that active sync doesnt setup for all user)
-Right click on the USBMON icon and select "run as"; input the administrator credential and configure the software ready for the capture
-Launch the crack and follow the instruction
And voila ! The dump should be achieved by now
Click to expand...
Click to collapse
I had to create another admin account as the unlock UTIL requires that you use the Admin account. I have been able to RUN USBMON while starting the unlock and it put the M3100 in the white unlock screen but then get an error and the util has shut down.
Any Ideas? I don't mind waiting to unlock so I help th community out...
OK...I think I captured it....The unlocked changes to a different driver type in the middle of the unlock. So I started a new session with the "NEW" device I think I captured it all but what do I do with this file now?
slimsaturn said:
OK...I think I captured it....The unlocked changes to a different driver type in the middle of the unlock. So I started a new session with the "NEW" device I think I captured it all but what do I do with this file now?
Click to expand...
Click to collapse
attach it here
Alright...POF They are too big to attach....Anywhere else I can throw them? If someone tells me how to upload them to the FTP I will do ASAP...Hopefully this is able to help someone. If I did miss the crucial info i am sorry for failing
no problem, i'm sure it will be juicy
Put them here:
ftp://xdaupload:[email protected]/Hermes/
USERNAME: xdaupload
PASSWORD: xda
let me know when the files are uploaded.
OK so I am getting a 530 Permission Denied error. Can i just email them or someone let me know what I am doing wrong
Email them to me.
sexy [email protected] vijay555.com
V
Finally the files are here:
ftp://xda:[email protected]/Hermes/Technical/unlocker-capture.zip
Going to have a look at them right now! will post something later
pof said:
Finally the files are here:
ftp://xda:[email protected]/Hermes/Technical/unlocker-capture.zip
Going to have a look at them right now! will post something later
Click to expand...
Click to collapse
Good Deal...hopefully this helps us
Slimsaturn!! You got it right
This is more or less what the unlocker does, will explain it in another post:
Code:
retuoR
USB> shmsg 8 2 "unlocking..."
USB> rtask a
[COLOR="Red"]Enter Radio Bootloader[/COLOR]
USB> rpass
HTCS-[url=http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoaderPassword]dyamic password[/url]-HTCE
...
USB> rversion
[COLOR="Red"]0106[/COLOR]
rrbmc x 6D0000 8000
rwdata 4D0000 800
[HTCS]- code, to big to paste here -[HTCE]
retuoR
USB> rtask b
[COLOR="Red"]Enter radio Image
AT-Command interpeter ready[/COLOR]
[email protected]=0,1,22051978
[email protected]=0,2,22051978
[email protected]=0,4,22051978
[email protected]=0,8,22051978
[email protected]=0,16,22051978
[email protected]=0,32,22051978
AT
retuoR
USB> shmsg 8 2 " done"
USB> task 8
Is that from what I sent you
slimsaturn, yes this has been taken from the files you posted (Thanks!).
Here is the process explained, if you don't understand anything check the wiki bootloader page for a better explanation.
Code:
retuoR
Returns from radio bootloader to normal bootloader, probably here because the capture was not started at the very begining of the unlocker process
Code:
USB> shmsg 8 2 "unlocking..."
USB> rtask a
[COLOR="Red"]Enter Radio Bootloader[/COLOR]
Shows "unlocking..." on hermes screen, enters radio bootloader
Code:
USB> rpass
HTCS-[url=http://wiki.xda-developers.com/index.php?pagename=Hermes_BootLoaderPassword]dyamic password[/url]-HTCE
Sends "rpass \r" (mind the space between rpass and \r), then sends "HTCS" + the password + the CRC of the password as bytes + "HTCE".
This authenticates to the radio bootloader (to be able to use the rrbmc command later), the password is dynamic (but the method to generate it is known) and sent encapsulated on a HTCS+password+CRC+HTCE block.
It should either return "T " for succes, or "F " for failure (encapsulated in the HTCSHTCE block), in the capture it returns "T".
Code:
USB> rversion
[COLOR="Red"]0106[/COLOR]
returns radio version encapsulated in HTCS HTCE block.
Code:
rrbmc x 6D0000 8000
Read back 32768 bytes (0x8000) of memory content from address 6D0000 and save the data to a file named "x".
@slimsaturn: do you have a file named "x" on your computer? can you send it too? if not, can you try to "undelete" it with some tool...?
Code:
rwdata 4D0000 800
[HTCS]+(2048 bytes of code, to big to paste here)+(4 bytes crc)+[HTCE]
This writes 2048 bytes (0x800) of data to address 4D0000, the data is sent encapsulated on HTCSHTCE block as well. I guess this does the CID unlocking.
These 2048 bytes are on the attachment, if anyone wants to look at (hint: compare it with extracted radios using an hex editor).
Code:
retuoR
USB> rtask b
[COLOR="Red"]Enter radio Image
AT-Command interpeter ready[/COLOR]
Returns from radio bootloader to normal bootloader, then enters the AT command interpreter to talk to GSM AT cmd interface.
Code:
[email protected]=0,1,22051978
[email protected]=0,2,22051978
[email protected]=0,4,22051978
[email protected]=0,8,22051978
[email protected]=0,16,22051978
[email protected]=0,32,22051978
This enters the same sim unlock code to all locking facilities (2,4,8,16,32). The code here is 22051978, I guess this code is calculated from what has been previously read by rrbmc command. Will be a different code on every device. Weird that it doesn't get the locked facility first, it just tries all them.
Code:
retuoR
USB> shmsg 8 2 " done"
USB> task 8
This exits from the AT command interpreter, shows "done" on the Hermes screen and reboots the device.
Now I'm going to try the 'rrbmc' command on my hermes and see what is read from there... I've also found that the content written to device by rwdata has some strings in common on GSM.nb (radio) extracted from NBH update, so it's part of the radio.
pof said:
@slimsaturn: do you have a file named "x" on your computer? can you send it too? if not, can you try to "undelete" it with some tool...?
Click to expand...
Click to collapse
Sure...I will check my recycling BIN tonight. If I can't find it there do you have utility that I can use to search my PC to try to locate it?
It will not be in the recycle bin, it will be either on the folder you run the unlocker from, or on the c:\temp c:\windows\temp
The exact size of the file is 32768 bytes, it is named "x" (without extension).
If the unlocker has removed the file (most probably) then it will be removed (but not in the recycle bin!) so you will need to use some software to undelete removed files, I don't know any but google may help.
Pof, I just tried running the unlocker with file i/o monitoring, and didn't see it produce a file called X (or anything else that looked like a likely candidate)
Maybe we can do a before and after dump of the radio patch - it'll probably be using a similar idea to the Universal unlocker if it's overwriting the radio.
V
pof said:
It will not be in the recycle bin, it will be either on the folder you run the unlocker from, or on the c:\temp c:\windows\temp
The exact size of the file is 32768 bytes, it is named "x" (without extension).
If the unlocker has removed the file (most probably) then it will be removed (but not in the recycle bin!) so you will need to use some software to undelete removed files, I don't know any but google may help.
Click to expand...
Click to collapse
Alright I will check tonight. I am guessing this is the missing link to fully understand what happens.
help needed
I need the help from someone who hasn't unlocked their phone yet and is willing to pay imei-check the 20GBP: I need to compare two regions of the radio before and after running the unlocker.
These are the steps to follow:
1) Disable activesync on your computer by right click on activesync icon -> connection settings -> uncheck "allow USB connections".
2) Put your device in BootLoader mode
3) Connect device to computer using USB cable.
4) Download TryBootloader.exe and run it.
5) TryBootloader fails most times you run it with one of these errors:
"Could not enter bootloader mode" or "SetCommState failed Could not open device " you need to reset your device and put it in bootloader mode again, and keep trying until you get this (usually no more than 5 or 6 tries):
Code:
USB>info 3
password ~:0T4~~000~X~000
Entered advanced bootloader
rtask a
rtask a
Enter Radio Bootloader
rinfo
rpass
Retval:
T
Entered radio bootloader
6) Once TryBootloader successfully authenticates you, open mtty.exe and select "USB" port and click "OK", this time you will not get the usual "USB>" prompt because you will already be in radio bootloader, but this should give you an authenticated command line in radio bootloader where you have all commands enabled.
7) Start HHD USBMonitor.
8) File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
9) In the upper part there are two tabs: basic and complete. Click on "Complete".
10) Type these commands in mtty window (do not copy paste, type them!) please note that you will not get any output (echo) on the screen when typing because you are on radio bootloader:
Code:
[b]rrbmc a 6D0000 8000[/b]
You will see a lot of garbage in the mtty screen, don't worry... when it finishes, type the next command:
[b]rrbmc b 4D0000 800[/b]
You will see a lot of garbage in the mtty screen again, don't worry... when it finisheds, close mtty.
11) you should see all the USB traffic output on USB monitor window.
12) click on Edit -> Export and Save as type "ANSI Text files".
13) Save the file and zip it. Name it "dump-before-unlock.zip"
14) Enable USB connections on ActiveSync again, softreset your Hermes and make sure activesync icon is "green" again.
15) Run the imei check unlocker as normal, following their instructions.
16) Once your phone is unlocked, repeat steps 1 to 13 but this time name the file "dump-after-unlock.zip"
17) Post a comment here and attach the two files, if they are too big upload them to xda-developers ftp.
After that we'll have everything to start working on a free unlocker
PS: I am traveling from Spain to Germany tomorrow and will be 1 week "away" without internet connection, I hope someone will have uploaded the files when I come back!!!
Awesome on the Stick
slimsaturn said:
I am trying to capture the unlock of my M3100 to help the forum.
I followed the directions below...
I had to create another admin account as the unlock UTIL requires that you use the Admin account. I have been able to RUN USBMON while starting the unlock and it put the M3100 in the white unlock screen but then get an error and the util has shut down.
Any Ideas? I don't mind waiting to unlock so I help th community out...
Click to expand...
Click to collapse
Humm, interesting, when I tried it didn't required the admin rights so far. I tried this a quite long time ago, I may have forgot something or they may have updated there util.
@pof: You were talking about CID unlocking. I don't think that the IMEI tool is still able to make the tytn Super CID. I have used it about 2 months ago and my device is far from being super CID . Slimsaturn, could you please give us the CID of your device in order to check what really happen down there?
EDIT: I found the exe program when I tested the dump. There is now an updated version of the .exe on there website. I guess that it could be interesting to test differents version of the tool, in order to better understand what it realy does and how it does it.
I upload here the older version, it can maybe interest someone. I ll give more tries with the newest version, if it is able to handle my radio version.
nice work
my £20 donation is sitting here waiting for you guys!!!!!!!!!!
anything i can do to help?
After I posted ROM-cooking method to create new SoftBank flat-rate data connection, another Japanese X01HT user has found more easier way today.
I would like to introduce new method with respect for his great work...
Now you DON'T need ROM cooking!
Step 1. Unzip the attached file, and run either ConnSBM.CAB or ConnSBM_noproxy.CAB for your purpose.
ConnSBM.CAB: make a connection, overwrite WirelessMgr_Service.dll and enable hidden proxy (webopen.softbank.ne.jp:8080), it is fully compatible as X01HT's standard connection.
ConnSBM_noproxy.CAB: just make a connection (no WirelessMgr_Service.dll and hidden proxy installation).
The connection will be created, however password entry is still empty at this moment.
Step 2. Run ORE2cert.cab (self-signature certificate for WIFIwake.exe).
Step 3. Copy Out.xml and WIFIwake.exe into \Windows folder.
Step 4. Just RUN WIFIwake.exe from \Windows.
The password will be created into the connection made by ConnSBM.CAB.
To confirm whether success or not, check the connection "Internet > SoftBank", and click "Edit -> Next -> Next". If "****************" is shown at the Password field, the password has been successfully created.
Enjoy!
EDIT: Updated WIFIwake.exe as self-signed version. I've prepared Hermes and Universal version separately (the difference is internal string for each model name). For Universal, at least I could have successfully made the connection on the DarkForce WM6 for Universal.
Download ConnSBM_ORE2h.zip (for Hermes X01HT) or ConnSBM_ORE2u.zip (for Universal JASJAR) and try it again if the password is still blank.
IMPORTANT INFORMATION: It seems to depend on CID...
To make this operation correct on non-SuperCID device, it requires to edit internal device name and CID. The attached file for Hermes seems workable for X01HT(Model: HERM200/CID: VODAK801) or SuperCIDed HERM200 device only, and for Universal, also only for JASJAR (PU10/CDL__001) or SuperCIDed device.
If you cannot create PW, you need to edit CID (01C798h-01C7A7h) using Unicode or UTF-16 mode of binary editor (for non-HERM200 or PU10 device, Model [01C760h-01C76Fh] also), and sign yourself... However, if you burn them into your cooked ROM, it may works correctly without edit binary (I've successed on my JASJAR, using original WIFIwake.exe from X01HT).
You can determine your CID using info 2 command of mtty.exe.
Too bad I alreday cooked mine...
great!!
it's perfect work on my x01ht with wm6lvsw edition!!
thank you
WOW! Amazing! Beautiful!
Thank you so much! I love it!
Will you understand the password?
Because it is necessary when using it from the personal computer as a
modem.
Doesn't work with Treo 750v
It seems this CAB utilize WiFi manager or something?
When I extracted the files from ZIP and executed the CAB, copy the Out.xml and WIFIwake.exe to \Windows folder and executed WIFIwake.exe, nothing happens. The connection Internet was created but the password is still blank.
Password Not Made in My hTc Universal
Hi Itamae!
Very Very Good Job!!
But Dont Create Password in my Universal.Of course installing According to the procedure.
Please Help.
My Universal is 02 Xda Exec
ROM:2.10.04JPN
Radio:1.08
Nice, I was messing around and the wifiwake will not put the password without the out.xml file but I was able to edit the text in the out.xml (which was about 300 letter As) and add some more random letters in there and it created it. Anyone think they can decompile the exe and look for the actual password?
Succeeded New SoftBank AP!!
VeryVery Thanks Itamae!!
Exec ROM Changed SuperCID,I Succeess Created New AP.
Not only Hermes JPN cross bow has came!
But also Soft bank connection in defualt!
go! go go!
http://forum.xda-developers.com/showpost.php?p=1181259&postcount=48
wifi connection problems
i got problems connecting to my station after doing this sb round up....it says connected, but my internet explorer wont...the internet connects with the SB connection, but not with my wifi
please help
Same here.
But you can pass this by unchecking the "Internet proxy" under Setting->Connection->Softbank
You have to do this everytime you use Wifi.
pharoah said:
i got problems connecting to my station after doing this sb round up....it says connected, but my internet explorer wont...the internet connects with the SB connection, but not with my wifi
please help
Click to expand...
Click to collapse
Is this guide for fresh devices only, or can I use it on the phone with all my current programs and files intact? I mean, do I need to hard reset the phone to get this to work, or will it work regardless of whether I hard reset or not?
WIFIwake for Athena
Hello itamae,
thank you very nice program!!
I wish ,,,,I have request to you,
Please make WAFIwake for Athena(HERM200,PU10)ATHE100,
sorry bad english,
nevermind... I got it working.. got the username to opensoftbank and lots of * for the password.. thanks..
April's here... is the new softbank AP fix working for everyone of you?
Wifi Problems
s2k7 said:
Same here.
But you can pass this by unchecking the "Internet proxy" under Setting->Connection->Softbank
You have to do this everytime you use Wifi.
Click to expand...
Click to collapse
thanks dude....
i had the wifi problem when i flashed the black rom....now im using lsvw...works okay...
i dont have to change any internet settings. connects ryt away.
anyway, im just happy that itamae's work around went well since yesterday...
everybody had a connection right?....i hope so.
im just quite worried though, what if, sofbank releases another hurdle for flashed x01ht's? i hope they wont.
auyongtc said:
April's here... is the new softbank AP fix working for everyone of you?
Click to expand...
Click to collapse
It is, and I am very grateful for the instructions in the OP. Without them I would be lost.
auyongtc said:
April's here... is the new softbank AP fix working for everyone of you?
Click to expand...
Click to collapse
not working with dark force 2.0
It is bad news!
I just think to upgrade to Black v2.0.
Any reason for this?
Waiting for your work-around!
I am using MicorX WM6 which includes this batch in the rom.
It surely works well after April.
Ryuerik said:
not working with dark force 2.0
Click to expand...
Click to collapse
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