PDA

View Full Version : I 80% lobotomized my Tmo Phone ed-boots, but no new rom..


squib308
25-02-2006, 12:53 PM
I'm not sure if I was a little too cocky after trying most of the WM2003 versions, and SE, all via OSImageTool (except SE) and the SD card flashing method; or I just screwed up, but I did it in a way I haven't read about here (and I've been reading here for a loong time :).

I was trying to cook up ROM version 4.02.04 in my own kitchen (more like hotplate), and it appeared to go well. I had (have) wallaby bootloader 5.15 come up, and I go ahead and update from SD card as usual, sos I don't get myself locked out with a PITA version of bootloader, and it looked good and normal. Rebooted, no backlight, which has happened temporarily (1st reboot) before. Backlight doesn't come on. Ever.
Missing splash screen. Instead, I have a black screen, one flash from the backlight or so, with red
g324e4
r6.25.02
4.02.04
in the lower right corner. Ok. Regular welcome screen (which, I've been through so many times, I could kill the person who decided that it needs to come up after every (or any!) cold boot). Then today screen looks normal, with no operator branding, still no backlight. Or sound.
Also have no cell signal icon at the top; instead it's like a network disconnected icon.
Start button brings up programs & settings, somewhat like normal. However settings doesn't have any power, backllight, or device information icons. (maybe missing something else I'm not thinking of, also). The Phone applet in control panel makes it look like it just rebooted, backlight flashes, get the red version info in the right, and I'm back to the today screen.
About half the apps work, but most disturbingly, activesync is not one of them - it complains its missing repllog (or one of it's components), so I can't get any files to my phone that way. None of the custom apps I had tried to put in there (if I tried that, I don't recall now) are in there, so no regedit or better file explorer... If I tried to put anything in there. By now I can't remember. I'm not sure I did, this may have been going to be a dry run sort of thing, then I'd add my BS if it all worked. I think.
Word crashes w/ no message, excel works fine. ?
There is no repllog in \windows as far as I can see, but I don't recall if you can see it with regular file explorer anyway. PIE works, contacts doesn't, calendar doesn't, notes does, mplayer does, but says it has no codec, and the little sound player doesn't go.
I can setup network connections in the control panel, but they never appear as an option on the top disconnected icon to connect to.
Beam says it works, but it doesn't really. looking at the XDA with a webcam that's been tweaked w/ no IR filter, it would appear the IR led is a very very dim 'on'. But it never talks to anything else, which is no surprise, because it's _really_ dim. TV remote blinds the camera in comparison.

I still have wallaby bootloader 5.15, and it ACTS like I can flash the ROM to the unit, it takes 5 minutes or so, does the counting thing, makes me cold boot, but then returns to the single flash, black with red version 'splash' screen, and time to go through welcome again.

I've tried OSImageTool with wm2002, 2003, various versions, both nbf and nb1, and no change. Tried XDArit (old) various versions, and even when it wrote the image to the SD card without crashing, it acted the same. Tried XDArit (old) with wallaby-patch.nb2, and wallaby-patch-tool.nb2, then all the above again - no change.

Tried bootloader -> SD card & back again of the same rom, which looks like it does something, but leaves me in the same place. I've screwed with all the files in the \windows directrory, hoping that an initial-setup type app just didn't fire, but that didn't help. Only about half the apps ran anyway. And it's missing a bunch of the stuff that's usually in there. (like the file for activesync) . the startup folder has poutlook, and that's it.

Uhm.. Oh, no green "I'm a gsm phone" led blinging every 3 seconds; going into the phone via start menu ( hardbutton for bringing phone up !work), brings up the dialpad, but anything I try to dial immedialy comes back with Call Ended, in a second or less. But on the happy side, the bootloader reports GSM (and everything else) is happy.

So I'm stumped. FWIW, I dumprom'ed the bad rom file, and it has repllog, and more than a few other files in the rom that don't appear to be in \windows. setup4.sh tells me
no operator rom found
xip regions not found: 81b00000=XDA_DEVELOPERS2, 81400000=EXAPPS, 817c0000=MISC
please extract parts manually.

and never sticks the rom.nb1 in cfg, so I think somehow.. I dunno know, but it's not good. I can run the dumprom on the err, deadly.nb1 (named after the fact) & that's where I see the repllog & all the \windows stuff.


So any help would be REALLY appriciated..!!! I don't understand why it's not using my new (proven good) ROM images via SD card flash; I can't beam any files to it or get online to get any tools t help poke around... I'm at a loss.
But at least i have my bootloader. ;0 and the welcome screen, and excel.
It's just very dark, and no one calls me.
I'm thinking if they did call me, they might ask if
I didn't get customrom tools mixed with demokitchen tools or something, or maybe old versions of files and newer versions mixed together, because that's the only thing i can think of why
I'm where i am right now. That and not trying to split the rom up after i made it before flashing to make sure that all worked well. Hindsight 20-20 and all that.

TIA, Brooks

squib308
25-02-2006, 02:17 PM
I forgot, even though wallaby bootloader gives me the a-ok on te SD card, and it writes to it & reads from it (i assume, I haven't broken out the hex editor to look at the SD card), WM2003 that's half on my ppc phone doesn't recognize that there is any media in the slot when it's there. I read something about people doing a trick to help fix their radio stack by making a hidden directory on the sd card, like 5547, with the radio upgrade files in it. My device doesn't realize anything is there, so I don't believe that would work in my case. (I was thinkging maybe stick a bunch of missing files, and./or reg entries in there, and it would get past my devices current reluctance to not be retarded, but it's too retarded for that trick. Nor can I email, SMS, or MMS any files from someplace else to myself.. ):

Oh well, the vibra ring wasn't working, so that gives me an excuse to take it apart while it's not working anyway. :) Is the motor easily accessable if you take the back off? I wasn't going to molest it that much until I could get a new bettery, but hey, if the patien't already in the hospital, might as well do a little surgery of convenience while it can't complain..

squib308
27-02-2006, 11:27 AM
Stuipd card reader more or less bit the dust at some point in the whole process. It's been kinda flaky, but it seemed to work when it worked. It just didn't REALLY let OSImageTool or XDArit write the correct image to the card.

I don't know when I got the clue, but I finally came to the conclusion that the wallaby was working fine, it was some other problem. So basically, I ended up getting my corrupted ROM onto the SD card (testing it out in bootloader, to see if the bootloader acted like it was doing the right thing.. it acted like it, too..), then "re-writing" the image on the card with a new one from my desktop to flash back to the wallaby. Except my desktop wasn't writing the correct thing, maybe not even anything. So I flashed the corrupt image over itself each time I was trying a "different" ROM/whatever. No wonder the .nb2 files didn't seem to make any difference. duh

Anyway, new SD card reader, everything is swell. It even lets me use the panasonic SD card format utility to bring my otherwise unformatable/useless SD card back to a state that windows agrees is a good 'disk'.

Yeah, so all those SD cards that become non-functional after you use them to flash/backup your ROM simply have got some crap written to track 0, that makes it so it no longer has the FAT filesystem windows expects. Then if you try to format it in windows, for whatever reason, windows can't write to that area (reserverd for SD card specification information, whatever that is), and says the disk is bad. Or can't be formatted. Get the panasonic utility, and it writes good SD info there, and its as good as new. Google SDFormatter, you'll find it. Windows only.