I bought a used MDA I recently and was quite happy with it for a while. First bought a 512MB SD for it and installed TTN5. Then noticed that I needed more space when I was in Belgium and wanted the Maps for France and got me a 1 GB SD.
I must tell a story first which also occured with the 512 MB SD (but I belileve it isn't SD related anyway): During fiddling with the TTN5 installation, Active Sync and all that (removing programs out of memory or deinstalling them) , it occured several times that the MDA got so slow in response that I had to do a soft reset. The effect when it was slow, was that clicking a menu item took about 5 seconds until the respective action occured. Not only menu items, also action in this bubble game - name escaped me for the moment - was in the same range of slowness.
Doing a soft reset cured the problem.
Now it happened that when I was in Belgium I had connected the cradle to my notebook and was dumping the France maps over USB into the unit. This took an hour or so and I left the setup unattended.
When I came back the notebook had powered down (idle mode). I took out the MDA from the cradle and wanted to switch it on but it didn't react on the on-switch.
Putting it back into the cradle suddelny lit the display and the T-Mobile screen appeared.
From then on the havoc started. I did a soft reset to no avail. A hard reset - nothing.
Accidently (or should I say intuitively) - without knowing that this combination existed - I
pressed the on switch and the soft reset at the same time and got into some strange
Wallaby bootloader which didn't do anything, I think. It timed out or something.
Anyway, I put back the MDA into the cradle, switched it on and left it there with the T-Mobile screen on.
After minutes, may be 10 minutes or so a WM 2003 initial screen had appeared which invited
me to do an initialization.
I went through the interactice dialog and suddenly had a working WM 2003 but is was again
very slow in the menu action.
Also shutting off (switch off) the unit worked but then I couldn't switch it on again.
So in a nutshell, my unit is messed up somehow and I want to get it back into a working state
looking for help in this forum.
How should I proceed now?
flash it with the latest ROM first. If that doesn't work send it off for repair.
saldous said:
flash it with the latest ROM first. If that doesn't work send it off for repair.
Click to expand...
Click to collapse
Thanks. Since I'm new to the matter: I remember that the version number of the T-Mobile screen
had - at the times it was working - some extra letters above the 4.01.19 (a G and some more
letters). These are gone as if some backup ROM is activated after the (hard) reset (?).
The person who sold me the MDA has unbranded it as she said. How do I get the ROM unbranded? When I download it from T-Mobile it is branded for T-Mobile, isn't it?
I got told of a site "lumpisteffan" which I visited already. Do they
carry the ROM I need? And do they have the instructions to do that or can that be found on this site here? Excuse my ignorance at the moment.
You could use nearly any rom of the kitchen to flash your device.
Because you have the 4.01.19 ROM installed on your device, you have to flash your device using a SD-Card.
Instructions how to do this could be found here in the forum, or in the wiki.
http://wiki.xda-developers.com/index.php?pagename=Wallaby
When you restart your device, what is shown on the Bootscreen, where also the 4.01.19 appears. The 2 Other lines, what do they contain?
Slowing down your device on using it for some time could be a memory outage.
If you "close" your running applications by pressing the (X) on the top of the screen, they are not closed, but put in the background. So they do use memory..... Just as little hint for you...
Stefan
LumpiStefan said:
You could use nearly any rom of the kitchen to flash your device.
Because you have the 4.01.19 ROM installed on your device, you have to flash your device using a SD-Card.
Instructions how to do this could be found here in the forum, or in the wiki.
http://wiki.xda-developers.com/index.php?pagename=Wallaby
When you restart your device, what is shown on the Bootscreen, where also the 4.01.19 appears. The 2 Other lines, what do they contain
Stefan
Click to expand...
Click to collapse
Thanks, Stefan. That's of great help. Probably gotta get me a card reader for my desktop first
or could I use my camera also? Probably I can.
> The 2 Other lines, what do they contain
It is puzzling me that I don't see any other letters or lines obove or beyond the line
4.01.19 in the bottom right corner.
But will have to look again at the device later when I have it with me after lunchtime.
LumpiStefan said:
You could use nearly any rom of the kitchen to flash your device.
Because you have the 4.01.19 ROM installed on your device, you have to flash your device using a SD-Card.
Instructions how to do this could be found here in the forum, or in the wiki.
http://wiki.xda-developers.com/index.php?pagename=Wallaby
When you restart your device, what is shown on the Bootscreen, where also the 4.01.19 appears. The 2 Other lines, what do they contain?
Slowing down your device on using it for some time could be a memory outage.
If you "close" your running applications by pressing the (X) on the top of the screen, they are not closed, but put in the background. So they do use memory..... Just as little hint for you...
Stefan
Click to expand...
Click to collapse
Regarding the lines above 4.01.19. They are indeed there (must have had hallucinations).
Comment (reedited):
I noticed that after a soft reset the T-Mobile screen appears with only
4.01.19 in the bottom right. Then after a few minutes the G and R are there.
It reads:
G
R
4.01.19
in magenta letters/digits.
Thanks for the explanation about possible causes for the slowness, but
it is already slow as soon as I have gone through the WM2003 initialization and want to chosse the first dropdown menu item. So no programs in memory at that point in time.
Another effect I forgot to mention:
The first time I put the XDA into the cradle the "charging" LED is red.
After some minutes, when the T-Mobile screen is there it is off.
Normally it is immediately orange when the devie is in the cradle.
I read in another thread that this might be an indication for a blown fuse.
Or blown fuses.
Since that happened in Belgium at the coast in a vacation area it could well be that power spikes have lead to this illbehaviour.
LumpiStefan said:
You could use nearly any rom of the kitchen to flash your device.
Because you have the 4.01.19 ROM installed on your device, you have to flash your device using a SD-Card.
Instructions how to do this could be found here in the forum, or in the wiki.
http://wiki.xda-developers.com/index.php?pagename=Wallaby
When you restart your device, what is shown on the Bootscreen, where also the 4.01.19 appears. The 2 Other lines, what do they contain?
Slowing down your device on using it for some time could be a memory outage.
If you "close" your running applications by pressing the (X) on the top of the screen, they are not closed, but put in the background. So they do use memory..... Just as little hint for you...
Stefan
Click to expand...
Click to collapse
Hi Stefan,
I downloaded the file 4.01.19_GER.exe from the site I was pointed to when visiting your site - I just wanted to go through the steps with an unmodified ROM.
I verified the MD5 sum ok, copied to 17 MB file to my notebook. I had the MDA in the cradle and connected via USB. MS Active Sync had a connection to the device.
At this point I wonder how that would be done with the XDATools OSImagetool which requires to name the source location of the ROM Image. But what I downloaded from your site is an installer .exe.
Anyway when I run the 4.01.19_GER.exe it tells me "Please plug the power adapter in your pocket PC".
Could this be a sign for the malfunction of my device?
How do I get the ROM Image ?
OK. I found that your kitchen builds ROM images while the link to the original ROM obviously delivers the full installer.
Will report further progress.
Looks like your fuse has been killed, or you have problems with your Radio Stack.
Flashing a new ROM wouldn't help to fix that problem......
You could try to repaor the Radio stack by following these instructions:
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
If you have a exe-file and you want to have a nb1/Nbf File, you have to extract the exe useing winzip.....
Stefan
LumpiStefan said:
Looks like your fuse has been killed, or you have problems with your Radio Stack.
Flashing a new ROM wouldn't help to fix that problem......
You could try to repaor the Radio stack by following these instructions:
http://wiki.xda-developers.com/index.php?pagename=Wallaby_HT_GSMError
If you have a exe-file and you want to have a nb1/Nbf File, you have to extract the exe useing winzip.....
Stefan
Click to expand...
Click to collapse
Since the connection via USB sometimes seems to work I tried the XDATools stuff, got me a .nbf file.
I tried the tools intuitively by clicking on the start.bat file.
It told me it had no .nbf file, so I created on from your site.
Thank it told me it didn't have the file in the English subdirectory.
OK, I put it there. The start.bat seems to invoke a adaptrom program. After that the English folder was named German. But some program still requires a GetConnectionType.dll which ain't there.
Anyway, what is pointing to a blown fuse is that I get with all these USB uploaders I'm getting this error telling me I should connect the power cable to my device.
I opened my device and bridged the one fuse (near the lower navigation button) to no avail. Didn't try the other fuse though since I thought that one would be for the piggy back battery, or is it also responsible for the power coming from the cradle?
Could it be my cradle is broken? Ah no, when I insert my spare MDA (the one with the broken display) the orange led lits immediately after inserting the device.
ok I did the soft spl method and flashed the WizFlo Latest went to 100% and soft reseted then went to the Windows Mobile Wiz Flo Screen and said tap here to setup your device i tapped it went to the align screen page and then locked up. I took out the battery and turned it back on this time it locked up on the tap here to setup your device screen. I did a hard reset and it locked again at the align screen. Now it locks on the tap here to setup your device screen and even hard reset wont work. I also have tried holding down the camera button to get into the boot loader but it does nothing? any ideas?
Update:
ok i finally got it to hard reset again but it still doesnt help anything. also the camera button being held down does nothing for me?
Update 2:
Ok I finally got into the bootloader screen and it shows USB in the bottom left but the RUU is unable to make a connection?
Update 3:
Ok I got it working. Not sure how but I just rebooted the XP machine and disabled the USB in activesynce (Also used a different battery) and Viola it loaded the original Tmobile Rom. Now Im just afraid if i try to do the Wiz Flo again it will do the same thing any thoughts should i install the Wizard Love rom first?
Thanks peeps.
adambennett said:
ok I did the soft spl method and flashed the WizFlo Latest went to 100% and soft reseted then went to the Windows Mobile Wiz Flo Screen and said tap here to setup your device i tapped it went to the align screen page and then locked up. I took out the battery and turned it back on this time it locked up on the tap here to setup your device screen. I did a hard reset and it locked again at the align screen. Now it locks on the tap here to setup your device screen and even hard reset wont work. I also have tried holding down the camera button to get into the boot loader but it does nothing? any ideas?
Update:
ok i finally got it to hard reset again but it still doesnt help anything. also the camera button being held down does nothing for me?
Update 2:
Ok I finally got into the bootloader screen and it shows USB in the bottom left but the RUU is unable to make a connection?
Update 3:
Ok I got it working. Not sure how but I just rebooted the XP machine and disabled the USB in activesynce (Also used a different battery) and Viola it loaded the original Tmobile Rom. Now Im just afraid if i try to do the Wiz Flo again it will do the same thing any thoughts should i install the Wizard Love rom first?
Thanks peeps.
Click to expand...
Click to collapse
It must have been a bad flash,nothing to get worried,sometimes,even SoftSPL doesn't load properely,it'll only work when the screen has gotten completely white and displays patched IPL/SPL.
Well,try to flash again,but if it still fails,you shud get the phone HardSPL instead of SoftSPL and upgrade to any wm6.1 rom.
Yea i tried it a second time and same thing. So i should do a hard spl then?
oh btw: it didnt show me a ipl/spl after loading softspl it simply wetn to a blank white screen and when it was updating the rom there was a progress bar on the computer but not on the phone still just a blank white screen.
adambennett said:
Yea i tried it a second time and same thing. So i should do a hard spl then?
oh btw: it didnt show me a ipl/spl after loading softspl it simply wetn to a blank white screen and when it was updating the rom there was a progress bar on the computer but not on the phone still just a blank white screen.
Click to expand...
Click to collapse
Then, as Zabardast said, you should try HardSPL. It can be reversed, so if you need to flash back, you still can, so don't worry.
WizFlo is very nice. Using it right now...
ok ill give it a try thanks
Please help me, I played around with BBs yesterday and lost radio, so installed a stock FW with FlashTool, and got radio back again, but on some 4x BB.. Wanted the new 58 BB, and found out that a .. ..0.16 FW would give me that, so installed the polish one (found no other), and after that no response when touching the screen!
xRecovery is of course gone after "stocking" (also rooting?), but I have tried a number of FWs for FlashTool, and even FW directly from S-E using Update Service, but still my phone is next to bricked.. I am n00b and could very well have done something wrong unknowingly, and/or overlooked something, but what might that be, and what are my options?
Sounds like corrupted FW. Not a big deal cause without a cracked Bootloader, you realy can't screw the phone up.
Turn phone completely off.
Pop Battery - SIM card - Micro-SD card out.
Let it sit for a few minutes.
While your letting it sit, take your Micro SD card and Format it using your PC.
"not saying this is your issue but I have had the phone lock up and appear to be unresponsive due to a corrupt file on the SD Card and it fails to mount and gets stuck." If you have any files you want to save, copy them to your PC Hard Drive.
Reinsert your SD Card - Sim Card.
Plug your USB cord into your phone " LEAVE THE BATTERY OUT "
Start up SEUS " Sony Erricson Update Service ".
While holding the back button, reinsert the battery.
Follow the instructions and restore the phone to factory settings.
I hope this works for you as this should elliminate any problems that could have or would be occuring prior. If it doesn't, shoot me a mail and I will get with you on messenger for trouble shooting.
_-_- Press Thanks if its useful-_-_
Nope, didn't do it, touched the thanks-bottom anyway, because on my PC I can...
PM'ed xKrisx, but everybody are welcome with suggestions as I'm completely lost without my phone!
Edit while waiting, hoping:
Followed instructions above several times now, except
xKrisx said:
.. .. .. and restore the phone to factory settings.
Click to expand...
Click to collapse
no such option, wouldn't that be S-E-Android 1.6 ? In fact I see no other options in SEUS than accepting (or not) uneditable choices towards an update -and done-, so I suppose that's what was meant(?)!
Have tried a number of slight variations including SEUS update without sim and SD at all (was actually allowed that), but most noticeable difference was that first boot pre-choose English instead of Danish (my language), and still no response from touch screen, so can't select anything at all!
My phone shows evidence of "moderate physical pressure" (bought second hand with one corner missing), so I can't totally reject the possibility of a sudden HW digitizer breakdown though I think that would more likely have occurred while phone in use than while sitting on my mouse-pad.. No matter what, I would really like to exclude any SW related errors before moving to torx-driver surgery! Plz help guys!
Hi seek4
Did you ever find a solution for your touchscreen?
Hi, think I know a bit of what I'm doing, read all I could, etc.
W7 laptop, SD SD with HP format, RHOD100.
(Can get serial # from Nexus 7 with ADB install, can reflash WM from SD, etc)
USB cable to computer.
I can 'flash' (update image) new Android RHODIMG.NBH to phone, I get filled progress bar, and then Update Complete, UPDATE SUCCESS and phone will not cut off (stuck in bootloader?) I do manual reset button.
Then I can 3 finger reset (SEND, END, + ON) to get tri-color, and then VolUp option. (So far, this is just like WM reflash) I push VolUp.
Screen goes to "Restore... Waiting for completed" and unfilled progress bar - and that's it. At this point, other resets can get me tricolor with USB, white HTC with NO radio, version, etc, and this waiting screen.
(I can use same process and get right back to WM.)
Where is my error?
THANKS!!
You can't flash Android with USB. SD is the only way to flash the NBH for Android.
Do you see the blue boot loader screen?
(I've also got the image for android on SD, just not getting there...)
I never get a completely blue screen (get tri-color), I go exactly as far as I mentioned - 2nd progress bar with no progress.
Using these instructions and downloaded files... http://forum.xda-developers.com/showthread.php?t=1566955 stuck at step 10 or 11 or so.
THX
tshephard said:
(I've also got the image for android on SD, just not getting there...)
I never get a completely blue screen (get tri-color), I go exactly as far as I mentioned - 2nd progress bar with no progress.
Using these instructions and downloaded files... http://forum.xda-developers.com/showthread.php?t=1566955 stuck at step 10 or 11 or so.
THX
Click to expand...
Click to collapse
Did you unlock your phone?
Unlocked long ago, olinex or something similar. Been trying various roms for years with no problems, played with SD android for awhile, wanted to try NAND.
I have good SDK, etc, put image on SD, phone finds it, first loading bar looks great, reboot, second loading bar never starts.
Do you guys never see 2nd progress bar ("Restore... Waiting for completed") - is my fault before that? Is there a better set of instructions that what I'm using?
tshephard said:
Unlocked long ago, olinex or something similar. Been trying various roms for years with no problems, played with SD android for awhile, wanted to try NAND.
I have good SDK, etc, put image on SD, phone finds it, first loading bar looks great, reboot, second loading bar never starts.
Do you guys never see 2nd progress bar ("Restore... Waiting for completed") - is my fault before that? Is there a better set of instructions that what I'm using?
Click to expand...
Click to collapse
So you flash the NBH... and it's never flashed successfully? Not sure what you mean by "second progress bar"... there's only one when you flash the NBH via SD.
OK - now we're talking!
I definitely see a second progress bar that never starts under "restore, waiting for completed" on a whitish screen as above.
Is the RHODIMG.NBH from that instruction set the correct one?
I will try downloading again and moving to SD again in case of file fault.
THX for helping...
tshephard said:
OK - now we're talking!
I definitely see a second progress bar that never starts under "restore, waiting for completed" on a whitish screen as above.
Is the RHODIMG.NBH from that instruction set the correct one?
I will try downloading again and moving to SD again in case of file fault.
THX for helping...
Click to expand...
Click to collapse
I guess I'm still not following.
Have you ever flashed via SD? The process is really quite simple. Just place the RHODIMG.nbh file at the root of the SD, and put the phone in bootloader mode. It should pickup the file and offer to start the flash.
Yes, and since I tried this I have also successfully flashed back to WM by SD, numerous times now.
I am not successful at flashing and then loading the small .nbh for Android
Am trying new download now...
tshephard said:
Yes, and since I tried this I have also successfully flashed back to WM by SD, numerous times now.
I am not successful at flashing and then loading the small .nbh for Android
Am trying new download now...
Click to expand...
Click to collapse
So to get things straight, you downloaded this file and put it on the SD. Now when you load it, you won't be able to get it to load using the recovery. Recovery is for Windows original files only as far as I get that.
Instead you just press and hold the volume down button while powering on the device. After you see the tri-coloured screen you can let go. You will get prompted with a white screen. On this you'll see:
Now the rhodimg.nbh is detected and by pressing the power button you can flash it. (or press volume down to cancel and return to the tri-coloured screen) After it said OK/Succesfull you remove the battery or press the reset button, after this there's no further steps, you just let it power on and you get a BLUE screen with some white texts called the LK bootloader / minipooploader by [ACL]
Here's a short instruction video to explain what I typed.
Al - THX for joining in!
That's the file (only one I can find), I do exactly as described, but at "battery or press reset" I get a white HTC (like would have 4 files listed on WM) that cuts off after 4 seconds, a three button push gets me a reload with no progress.
I made films...
files on SD - http://www.youtube.com/watch?v=ZbK8aWh9378&feature=youtu.be
process - http://www.youtube.com/watch?v=01Uq1dqtydE&feature=youtu.be
that show reset and 3 button reset (USB in here, same USB out) (Also, fresh solo Task 29 from RUU advanced...)
Any clues anyone?
(Could RHODIMG.NHB be bad on server?)
Not sure why you are doing a hard reset after you load the android NBH. Skip that.
Just let it load.
The instructions and post 11 above indicate reset.
I'm trying just leaving it at the Update Complete UPDATE SUCCESS progress bar now....
Nope - that just sits there after RHODIMG.nbh - OK, OS - , and UC/US,...
tshephard said:
The instructions and post 11 above indicate reset.
I'm trying just leaving it at the Update Complete UPDATE SUCCESS progress bar now....
Nope - that just sits there after RHODIMG.nbh - OK, OS - , and UC/US,...
Click to expand...
Click to collapse
Just a regular reset, not a hard reset is what I think they are meaning. I have lost count of the number of times I have loaded android onto my device, and I have never ever done a hard reset after the initial nbh load.
When I load android on my rhod400 it always hangs at the update success screen from the initial nbh load. Try just popping out the battery (and putting it back in) and letting it boot normally after you see the update success screen from the android nbh. You should get to a blue boot loader screen.
That (simple on or reset button) after android.nbh success gets me:
a white screen with HTC (that would normally [WM] fill in with b,r,s,something - 4 ?file versions) for 4-6 seconds, and then off and blank. Battery yellow will cycle 80% on. Subsequent on times out (HTC white) and off as above.
Have you loaded recently with the current file?
tshephard said:
That (simple on or reset button) after android.nbh success gets me:
a white screen with HTC (that would normally [WM] fill in with b,r,s,something - 4 ?file versions) for 4-6 seconds, and then off and blank. Battery yellow will cycle 80% on. Subsequent on times out (HTC white) and off as above.
Have you loaded recently with the current file?
Click to expand...
Click to collapse
Unless you're using some old file, yes I have flashed recently. Just flashed a TP2 the other day...
https://code.google.com/p/rhodium-nand/downloads/list
That's where you're getting all your NAND downloads from yes? Please ensure you have the newest stuff. This part is really the "easy" part. Just need to be SPL unlocked, then flash .nbh via SD. Seriously, that's the easy part... the hard part is getting your computer to recognize the phone in fastboot mode, and flash the recovery image - that's the step I always seem to have issues with.
This is an video from a Rhod 210, but it gives you a good idea what to expect. Useful info starts around 7:00.
http://www.youtube.com/watch?v=_qNCHqGPofI
Redid it all - exactly per video... fresh downloads. etc...
Where video shows carrier splash, then 4 circular buttons, and then blue with text, I get white HTC for 5-6 seconds and then off.
Just to be sure, since original thread evolved...
Mine is a RHOD100, SEA Roms work fine, SPL 0.85 olinex (AT&T freqs, they think it's a Tilt 2)
Seems it was only some phones early...
tshephard said:
Redid it all - exactly per video... fresh downloads. etc...
Where video shows carrier splash, then 4 circular buttons, and then blue with text, I get white HTC for 5-6 seconds and then off.
Just to be sure, since original thread evolved...
Mine is a RHOD100, SEA Roms work fine, SPL 0.85 olinex (AT&T freqs, they think it's a Tilt 2)
Seems it was only some phones early...
Click to expand...
Click to collapse
I did not intend for you to follow the video to the letter. It was just to give you an idea what to expect.