Device 'hangs' on O2 screen, but want to upgrade need advice - MDA, XDA, 1010 General

Hello all,
My XDA 1 has a fault I don't understand. When I hit the Power on button it comes on and stops at the O2 splash screen. It will not go beyond this point no matter what I try. The desktop does not recognise the device when I connect via USB. I have tried:
1. Soft reset
2. Hard reset
3. booting up in bootloader and running all device tests (failed USB rx & Infrared rx)
4. In bootloader copying boot to SD and booting with that. (Unfortunately I do not currently have an SD card large enough to copy CE or GSM boot)
What I really need to know is if I can try to upgrade the device (to WM2003) anyway and if the upgrade will solve the problem I have now.
DEVICE DETAILS:
Device: O2 xda 1
Bootloader: 5.14
ROM: 4.01
Radio: 3.02
Any and all advice/help/replies most welcome. Sorry if this has been answered previously but I searched and couldn't find the info I needed.
Thanks,
Aide

It's a lost cause...
Device can't connect to activesync via serial or USB so I can't upgrade and see if that solves it. Don't have card reader to try SD method. The problem is as described in my first post above.
I don't know how this happened (I hadn't tried upgrading or any sort of flashing apart from unlocking the device a looooong time ago).
Any ideas as to a solution would be greatly appreciated.
Aide

Your ROM version is not known (at least for me ) ... are you sure it's not 4.01.00 ??
Anyway, regardless of the reason, the good news is that you still have the boot loader working, the bad new is that you MUST use the SD method since the ActiveSync doesn't recognize the device.

Thanks Bis,
Yes ROM is 4.01.00 (sorry if I confused anyone ). Problem is at a new level.
I got an XDA with a cracked screen (so it's almost impossible to use though everything works) and used that with XDAtools (thanks Jeff) to upgrade to xda-dev Special Rom 1.2.
I copied the ROM to the 32MB SD card (got and error message at the end) but still risked using it to try bootloader method on the 'hanging xda. It worked: kinda :?
It now boots and hangs at the xda-dev splash screen and no other changes to original problem. Was that error message I saw responsible or could something hardware related have happened?
Still waiting for relief...Help me please. Someone, anyone...
Aide

aicon said:
I copied the ROM to the 32MB SD card (got and error message at the end) but still risked using it to try bootloader method on the 'hanging xda. It worked: kinda :?
Click to expand...
Click to collapse
That's your problem - redo everything above - but using a 64MB SD Card or higher. The ROM files are just over 32MB. Even if your card said it was all there chances are it could have been corrupt.
-JB

Thanks JB,
Getting 128MB card in the morning, will let all know how it went.
Aide
PS: Noticed someone posted same initial problem under topic 'XDA 1 locked on O2 screen' in General forum with no solution posted. So if anyone is interested - watch this space!

Ahhhh... God is in his heaven and all is right with the world
Used 128MB card and it worked like a charm. One thing I noted though: After I used XDAtools to copy ROM to the SD card and put it in the device it would not boot from the card automatically. I assume the ROM update tool on the device checks to see if the current ROM and the one on the SD card are the same and ignores the SD card if they are. (By the way, could someone please confirm if this is so? Idle curiosity :wink: )
I had to use the tool on the device to write the ROM to SD from one device and then the other device (that had the hanging problem) finally read that copy.
Thanks all,
Aide

some boot loder versions doesn't recognize ROM file on SD cards ... ex: 5.22

Related

My MDA II died after ROM 1.60 upgrade

:evil:
Hi guys,
I need some serious help here. Today I tried to upgrade my MDA II with the latest 1.60 ROM. Somehow during the upgrade something went wrong and my computer frooze and needed a reset. This was in the beginning 10 minutes of the ROM upgrade and my the screen of my PPC went off. After the reboot of my workstation I could not get my MDA II to connect to my workstation. The MDA is completely useless now. The only thing I have on the screen is:
Serial (or USB) on top of the screen (with no backlight) and at the bottem of the screen Version 1.01.
I can't soft reset of hard reset. I took the battery out and waited for almost 30 minutes but I still can't turn the thing on nor can I soft or hard reset. I can't thing of anything else that I can do and I just sold my Loox yesterday so now I'm lost!
Anybody with a good suggestion??
Please help.
Regards,
Wouter
The Netherlands
I think it's a way to use a SD-card with a Rom on it.
Looks like Your bootloader is still working and can reflash a rom to Your device.
Now You have to find somone with an 64MB SD-card to put a rom on it and reflash Your device.
With best regards
Jens
Hi Jens,
I think my bootloader is not working anymore. I tried to do a hard reset a dozen times but the bootloader menu doesn't come up. But thanks for suggesting though.
Wouter
Hi wouterk,
I don't know if this would be of any help, but you've got nothing to lose now.
I've got a similar error that the RUU program asked me to remove my XDA II from the cradle and right after that, the XDA II screen freeze at "Seria 1.01", same as yours.
So I put my XDA II back to the cradle and from my PC, I clicked Control Panel > System > Device Manager > and here my XDA II was recognized as an unknown device, so I updated the MS USB Sync driver.
After the driver update, I rerun the RUU and the ROM upgrade went fine. Now I have my XDA II back alive and kickin' with the new MDA ROM. At least this works for mine and hope it would also work for yours as well.
HTH.
Hi Joparp,
Of course I gave your suggestion a try. But too bad it didn't work for me like that :? . I remebered that when my workstation crashed, after the reboot it found a new USB device (my cradle?) but I couldn't get your sollution to work for me. But I still have hopes. Tomorrow evening I'll meet a guy who can fix my problem (keep my fingers crossed....). So I feel reasonable relaxed now.
It is nice to see that so many people responded to my problem. I posted my problem on three different sites and many people responded. That was a nice feeling! I keep this thread posted about the result of tomorrow.
B.t.w did you install the 1.60 ROM eventually?
Wouter
Hello wouterk
well, i'm sorry about this and i guess the safest way to do ROM update thru SD Card.
i do agree with jenson suggestion and i can't see any other way to resolve this problem which i hope will work here are the steps as follows :-
ask any one who has MDA II device, 64MB SD Card and SD Card reader to backup his/her ROM and Post it for you somewhere where you can download it and write it to SD Card.
ofcourse he/she if using Windows will need serial cable and hyper terminal software which normally can be fount under start/programs/Accessories/Communication otherwise download from http://www.hilgraeve.com/htpe/index.html
get the device into Bootloader Mode ( power button+any direction+reset )
Connected via Serial cable and use these setting 115200 baud, 8n1, direct to com1 port or maybe com2 it depends on which port they use
type d2s command to backup ROM to SD Card which i recommend 64MB SD card formatted and when done you will see something look like this
D:Waiting for card insert.........
SDetected one card
SD:ready for transfer OK
Total card size=3D40000ze=0
SDCARDD2S+,cStoragePlatformType=FF
********************************************************************************
***********************************************
Store image to SD/MMC card successful.
SER>
then reset the device and get SD card reader and insert this card into the reader and use ntrw image reading and writing tool
if you don't have it you can download it from here http://www.tamiminet.com/othman/ntrw.exe
from the command line run ntrw read MDAII.nb1 E:
This assumes your SD card reader has drive letter E:
now you will have new file which is MDAII.nb1 it's about the size of the SD card zip it and post it somewhere so he/she can Download it and unzip it then write it back to SD Card using this command b]ntrw write MDAII.nb1 E:[/b]
again this assumes your SD card reader has drive letter E:
when done go into bootloader mode ( power button+reset ) with SD card inserted, hit camera button and flash your device with rom which is on SD Card
if you don't have serial cable you still can do it using Linux with cardle and thanks for bio and few other cool guys who mentioned this hints on other thread
put your device in bootloader mode
connect via cradle
use any terminal (minicom) to connect to the used port (/dev/ttyUSB0)
- you should see something like 'USB>' or 'SER>'
put an SD Card into device
type d2s on command prompt
wait untill you see Store image to SD/MMC card successful
i don't think this will include the Applications on the Extended ROM but no problem this can be done later.
i hope this could help to get back you device to life.
best regards and good luck.
Othman
Riyadh, Saudi Arabia
It is working again!
:lol:
Hi guys,
Thanks to Akira my MDA II is working again. Everything is working again exept for the bluetooth communication with my Emtac bluetooth GPS. That problem still remains in my case. I even did another hard reset but still the same problem. I then put the Towa fix again on it and now I can use my GPS again.
So thank you all guys!
Wouter

Receiving Error 011: in trying to unlock XDA1

I've been trying for several weeks now to unlock my XDA1 Wallaby without success. Some members have tried to help but no joy. In trying to load the Special Edition ROM I get the Error 011 message per the attached screen grab. Can anyone tell me why this is occurring and what the solution is? My current device ROM is version 4.01.16ENG, Radio Version 6.25.02, Protocol version 32e4.
Any help with this frustrating issue would be much appreciated. Willing to make a phone call if you can help. Thanks.
It´s a very easy solution.
Your installed ROM prohibits flashing via Exe....
Extract the special Edition ROM with winzip or anything else. You got an folder called English. In this folder is a file NK.nbf with about 32 MB. This File you will need for flashing via SD-Card.
Instructions how to flash via SD could be found here:
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
Here
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_Unlock2
are complete instructions what you have to to to unlock your device.
Step 6 is not a must. If you get an error Message you should be able to process without downgrading the bootloader....
Stefan
Stefan,
Thanks for your response. I followed the instructions you pointed me to but they are a little unclear. I first copied the ROM image to my SD Card while in my device (I later assumed the instructions meant to write the ROM image to the SD Card via a card reader, which I don't have).
After downloading to the SD Card in my device I held the power button and soft reset which displayed on screen the message:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
However, nothing happens in touching ACTION on the screen to download. What do I do?
Thanks, David
Don´t know, what you are meaning with "touching ACTION" put you have to press the center of the navigation button on your device to start installation.....
Using the XDA-SD-Slot is also ok. You just have problems if anythhing went wrong, and you don´t have access to this slot any more....
Stefan
Stefan,
Thanks for your reply. I've sent a response to your personal email address.
David

error getting connectintype

hi ppl,
today I ve made rom with the romkitchen, it was 2003 final and everything went ok, phone was functional until I used to try to install some newer versin of the programs I previously included in the rom. That didnt work (of course) so I decide to put another rom without those programs so I can install newer versions but when I run the romkithen exe computer report
in the dos window
error getconnectiontipe - unspecified error
error getting connectiontype
and the program for the patching report that he is trying to get the data from the device and after that he reports that
"cannot execute the remote communication program, please make sure that the usb/serial cable is properly connectes"
of course cable is connected, device syncing with the active sync and the icon is green, used to try to soft reset pc and pocketpc, to hardware reset pocket pc, to connect it to other pc and patch there, to install active sync 3.7.1, to reinstall active sync 4.2, to reinstall usb drivers on the pc, to put sim card and sd card out and to patch then... nothing helped...
what can I do ? is that due to the windows 2003 instalation on the pocket pc (had same version on other wallaby without the problems) ? can I solve that some way ?
I ve read before that patching can be performed from the SD card so I found the xda tools and osi image tool but couldnt found rom nd1 file anywhere (was stupid and didnt make copy of my previous rom)... which rom can I use just to enable USB connection and after that I ll patch it with the "normal" rom from the rom kitchen...
Ive checked those roms http://wiki.xda-developers.com/index.php?pagename=ROMVersions but didnt find any nd1 file in the files I ve checked, can I use those roms with osi image tool eventually ?
which one ?
Lots of questions ... Sorry people ...
I can use it in this condition too but I d rather have an opportunity to flash it to some other version maybe.
Best regards to the community !
I think it´s just the problem that the ROM prohibits flashing via EXE-file. You have to flash via SD-Card.....
You find the ROm to write on the SD-Card in the EXE-FIle. Just extract the exe using winzip, and then you will find it in a subdirectory (normally english, or dependent on the ROM-Language...)
Stefan
Thanks a lot Stefan, so I can use some ROM from the page http://wiki.xda-developers.com/index.php?pagename=ROMVersions ?
Any advice which one should I take please (Im not using any of the operators noted there, just looking for some rom that will function ok) ?
Thanks m8 !
Yes, you can take any rom of it. Mostly the T-Mobile prohibits flashing via EXE-File, but Flashing via SD-Card is more secure in my opinion. So i´ve done 99,9% of my flashes via SD-Card, and you can believe me, i´ve done it a lot of times.....
By the way, which software has to been updated in my romkitchen?
If you give me the hints, i could try to update them....
Stefan
thanks a lot for your time and advices Stefan !
Its not a huge problem but probably we share same opinion - most of the tech guys like to see that everything work fine, if something doesnt work then we re not satisfied.
Basically problem is that I included spb pocket plus in the rom and therefore I cant install spb weather which demands pocket plus v 2.5+ and version in the rom is 2.0. I cant upgrade it coz its in the ROM, used to try to remove it from the registry but no luck, used to install latest spb diary coz the spb weather also work with the diary but looks like that the first thing weather perform is checking of the pocket plus version and if the version is not 2.5+ it stops the installation...
Probably for the most of the people spb weather is not a reason for loosing couple of hours in trying to change rom in wallaby but as I ve mentioned I like the things that work 100%, if some electronic/computer stuff work at 99% that usually bother me. Stupid - I know but thats the way it is.
Im going to patch it thru the SD, thanks again for the all your efforts now and before.
GL & HF !
Sorry...
Still need help, using the OSI tool I copyed NK.nbf file from 4.02.04_eng rom to "XDA SD Card Slot -unknown size" - coz I dont have card reader/writer at the present moment so I tought that I can put the file via the cradle connection while the card is in the wallaby...
Checked the card from the wallaby file explorer but nothing is on the card, since I had expirience with direct writing to c64 and amiga disks writing I assumed that file could be written directly to the card without OS instructions but after the reset of the wallaby it report that card shoud be formatted to become writable... Is that normal, or I should wait for the card writer reader to put the file properly to the sd card ?
If possible please help me with the link for the OSI tool patching, I cant find it anymore, checked thru the site but no luck, dont know what I have to press so the wallaby read the rom from the sd card.
Thanks Stefan & all others
success !
No help needed, I ve made it...
So dont have any fears as Stefan told unpack the rom from the self extracting archive and run osi tool, in the source field set nbf as a file type and then select extraced rom.
As a target you can set card reader/writer and also you can put the SD card in the wallaby as I did. Set the XDA SD card as a target in that case.
Its normal that after the writing (no message that writing is successfull, when it is finished OSI tool will stop) SD card become unreadable to wallaby.
Then perform actions as noted in SD card patching info
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_FlashSD
Hold the power button and soft reset. You'll be taken to the below screen:
SD DOWNLOAD
Card Type:
CE OS & BOOT
Press action to Download
Or
Press REC to Exit
Press action to download and it will start the download/restore from the SD card.
Follow the on screen instructions once its "Completed" which will consist of a " Hard Reset"
Action button mentioned above is middle button - "D PAD"
Works like a charm, now I have o2 win 2002 and later I ll patch it to 2003 SE again but without pocket plus.
Thanks Stefan and community !

Help!Help!SD Rom requested

hi brothers, i upgraded my O2 XDA Atom last night--result fail. i didn't backup ROM on SD card, so i can't restore by using SD card and i can not find someone to fix it for me in my city. does anyone can upload the full SD Backup ROM for me? it would be great! thank you very much.
You're stuck in the bootloader after an ExtROM Flash Fail, right? Do you have the DSUU windows upgrade executable?
If you don't, download the latest Atom ROM upgrade from the O2 site, connect your device to the PC's USB (you'll see the message on the Atom's screen change to Connected), and run the upgrade (it will think you're trying to flash to an empty device with ROM version 0 - let it). IIRC you do NOT need to use an SD card ROM for this process.
To ensure success, be sure you have removed the SIM card from your device first - and it usually takes one or two tries before the extrom format command goes through successfully (*glares at Quanta*). As long as what failed is only your ExtRom you should be able to salvage your device.
Thanks brother, i will try it.

[Q] Hero problem with sd

SERIOUS trouble: After i flashed android 2.1 rooted on my phone it doesnt see sd cards anymore, even from recovery. But bootloader SEE it!!! so i placed rom.zip on sd and installed 1.5 official firmware from bootlader ... with no result, now official FW doesnt see any sd cards DAMN!
Any suggestions gentlemen?
maybe this is an android bug or something?
ziphead said:
SERIOUS trouble: After i flashed android 2.1 rooted on my phone it doesnt see sd cards anymore, even from recovery. But bootloader SEE it!!! so i placed rom.zip on sd and installed 1.5 official firmware from bootlader ... with no result, now official FW doesnt see any sd cards DAMN!
Any suggestions gentlemen?
maybe this is an android bug or something?
Click to expand...
Click to collapse
When you say it doesnt see it where you looking on your phone?
Moved to Q&A today as not development
Haizum74 said:
When you say it doesnt see it where you looking on your phone?
Click to expand...
Click to collapse
First when i boot system it says: "Sd card removed, insert sd card" in tray (something like this) , i looked everywhere, even if i try to make photos it says "insert sd card"
Have you tried plugging your sd card into a card reader or another device to see whether the sd is broken?
btdag said:
Have you tried plugging your sd card into a card reader or another device to see whether the sd is broken?
Click to expand...
Click to collapse
Sure , sd card is working in card reader, also i've tried to plugging other sd's... it simply, doesnt see any sd ....
is it possible to mount sd manualy, somewhere like android configs (text files like in linux) ??
Send it back to HTC. Sounds like the reader in the phone has packed up.
btdag said:
Send it back to HTC. Sounds like the reader in the phone has packed up.
Click to expand...
Click to collapse
The problem is - that i bought my hero in Shanghai (it was allready rooted, and oriented to sell in france Now i'm in Moscow, i called HTC Service Center and they told me that i have to wait for couple a weeks, because they dont have card reader modules to test it. I have no much time to wait, cause i'm going back to china soon in Sept. In china there are no HTC official service centers , only in Taiwan. In China HTC models are selling under the "DOPOD" trademark and i think they provide their own firmware with it (maybe i dont know). For me its a little bit complicated to describe all my problem in chiniese =) So i'm trying to find other ways to understand origins of this problem by myself...
I understand that it looks like hardware problem, but i need to be sure (because bootloader can read sd cards), so i have two questions here:
1)When bootloader starts to check roms or updates on sd card it is looking for: HIRODIAG.ZIP,HIRODIA3.NBH,HERODIA2.NBH,HIRODIAG.NBH,HIROIMG.ZIP . HIROIMG is a firmware, but what about the others? Maybe i could launch a diagnostic tool here to check my system ?
2) Are u sure there are no android configs that i can access through command promt using sdk tool usb drivers?
Thanks everyone who is trying to help me, i'm really appreciated!
Ah i missed the bit about it working in bootloader. Interesting. This would suggest it is less likely to be hardware as it doesn't perform that check when a sd-card is not inserted.
But you get nothing in recovery? Have you tried re-flashing/updating your recovery? Assuming you can put the file on the sd card.
Alternatively try flashing the official HTC WWE rru for v1.5 and see whether doing via rru is any better.
This could be a windows driver issue. Have you tried a different computer?
btdag said:
But you get nothing in recovery? Have you tried re-flashing/updating your recovery? Assuming you can put the file on the sd card.
Alternatively try flashing the official HTC WWE rru for v1.5 and see whether doing via rru is any better.
This could be a windows driver issue. Have you tried a different computer?
Click to expand...
Click to collapse
Recovery? u mean before i flashed official FW? NO i couldnt mount/unmount sdcard from there also.
I've tested other computers. When i connect computer and phone with usb cable windows gives me a popup window that it coudnt recognize the device. HTCSYNC, RRU tool, sdk with usb drivers nothing could see it. There is only one way to flash fw - via BOOTLOADER installation WAY
I was working with linux distributives long time ago , and i remember simillar problems there, like mount/unmount hemorrhoid . And Android is based on linux , and looks like bootloader is booting before linux thats why it works there. It seems that android fw is just a top of the iceberg, and when you flash fw probably this does't affect linux CORE....
I might be mistaken , imnot good at linux and all this stuff , thats why iam asking for help here on xda-developers, maybe someone knows ... linuxoids? ))
Or maybe i should post it somewhere else just tell me ...

Categories

Resources