Not even stuck at Bootloader :( - JASJAR, XDA Exec, MDA Pro Software Upgrading

Please help!
I just upgraded my ROM to Ivan's latest AKU3.5 from bootloader
This completed successfully (100% successful, disconnect and restart etc)
I disconnected and reset, except it was stuck in bootloader mode
I tried the Mtty method (for the first time ever) and followed the step by step instructions...
...after a few seconds a few command lines appeared with "USB>" on the last line
I took this to mean the process had finished (?), disconnected the device from USB and tried a soft reset
the device just stayed stuck in bootloader
next, i downloaded uni_exitbootloader and ran it (as this has worked for me many times in the past). it didn't work the first few times, but i disconnected and reconnected and this time it worked. It said "data sent, you can now reset your device"
This maybe where i went wrong?
I foolishly reset the device before disconnecting it from the USB. The PC immediately said "USB device not recognised" and the screen of my Universal went blank
Now, if i soft reset, it does nothing, i cannot even put it back into bootloader using the camera, on, reset button combination.
HOWEVER, if i press the two soft keys (as if i was going to do a hard reset) i get the white screen with the black text saying "Press 0 to restore etc"
If i press 0, it says "clearing" but the screen just goes blank
If i press x, the screen just goes blank
Now i am completely unable to try and use either mtty or exitbootloader as my PC just says "USB device not recognised" and neither applications run as they should
QUESTION: Have i totally bricked my Universal?!
If not, what can i possibly do...???
As usual, i will be extremely greatful for any advice or assistance to resurrect my favourite Pocket PC!
Thanks in advance for your help.

Aaagh! I think i just realised what i did...
1. I didn't read the posting "For all those stuck in the bootscreen, try the Mamaich method" carefully enough. I didn't realise that the Mamaich method totally erased the ROM!!!
2. By not flashing a new ROM to the device immediately and instead using exitbootloader to exit the bootloader screen i now have a device that has no ROM and probably has no way of knowing how to get into bootloader mode.
Can someone confirm this?
For one, i feel like an idiot for not reading the posting carefully, but having admitted to being stupid,...
... is there anything at all i can do???
Please help...

cancel that, you already said what i was going to ask above

have you try to flash it again with original ROM? sometimes it helps!

Once in bootloader mode, try plugging it into a different USB port, one directly on the PC.
I have had this where one port says not recognised, even after having been plugged in and used for ages, then I go to flash it and it won't work.
Another port has worked for me.

Since you ereased the DOC, all you've got to do now is to reflash the default ROM.

Thanks everyone...
Only problem is, i cannot get it into bootloader mode. And every port i plug it into (so far) says "device not recognised"...
Nevertheless, i did try to reflash the device, but it just gave me the "Error 150" message. It just doesn't know the device is connected i guess?
I think if i hadn't done the Exitbootloader step then i would have been able to reflash it. However, now that i have... i'm a bit stuck... any ideas of other ways to get the device into Bootloader mode?

try
you already know there is a file called EXITBOOTLOADER but did you know that here is a file called ENTERBL ?
try it .....

Thanks dhob187!
Where might i find this file though? Did you mean to attach it?
Just one other question...
How does ENTERBL work if the PC doesn't recognise my device i.e. "USB device not recognised"? Will the application override this and push commands to my pocket pc anyway?
Or is there a way i can get my PC to stop rejecting the device when i plug the USB in?
Thanks in advance,

I believe this is the file u needed
i don't know how this utility works, but just yesterday i stuck in the bootloader after upgrading my uni to AKU 3,5 and solved with ExitBootloader.exe. CMIIW it works the same way, just plug the USB cable then execute the utility (just simple as that).....
but have u tried my earlier suggestion? my friend got the exact problem like you (blank LCD not even bootloader), he was downloaded the original EXEC ROM and try to flash with it (with original upgrade utility also). and the thing start to blink, enter the bootloader and flashing!.....after he manage to wake the device up, then he tried to flash it again with the newest ROM and succeded........
sorry for my english.....

Please don't apologise for your English, thank you for your suggestions!
I didn't quite understand your initial post... but i do now.
Does it have to be the first ROM that it was shipped with or just an original i-mate JasJar ROM?
I can't try it now, but i'm excited to go home and give it a go later tonight... what's more i'm excited at the prospect that there may be some hope for my currently rather expensive paperweight!!!
If the aforementioned doesn't work, i'll try using your attachment.
Cheers again!

it doesn't have to be the first rom that shipped with your imate, just an original one. try your luck then! never give up, keep the faith!!!

sorry, forgot one thing, just ignore the USB error (not recognized) and go for the upgrade (execute the original upgradeUt.exe)

Hi Rudy173.
Thanks for your help, but unfortunately nothing has worked
I have tried running two official JasJar Roms without success... i always get the connection error message (this is surely because the PC always says "device not recognised" when i plug it in).
Also, when i run ENTERBL.exe i just get a failure saying that ...ENTERBL.exe is not a valid WIN32 application... etc...
So unfortunately, i'm still stuck... any further suggestions anyone?
Can the i-mate service centre help me? Is it likely to be expensive?

Back in business )
Wow, not entirely sure what i did... but my Universal is ALIVE!!!
As per the previous post, nothing seemed to be working so i removed Activesync 4.5 beta and reverted to 4.1. I then tried to reflash to an original ROM and the same "connection error" problem happened.
However, next time i tried to enter bootloader, by pressing light, on/off and reset, it went straight into bootloader and i was able to reflash from there
I didn't even need to reflash with an original i-mate ROM. I went straight for Ivan's latest.
This experience has taught me a few things:
1. I have become seriously attached to my Universal!
2. You should never give up hope of retrieval!!
3. This forum is full of very nice helpful people!!!
Thanks everyone.

wow! glad to hear that!
Happy ending....................

Related

Hello Guys I need Your Help

First of all Hello
I've been trying to update my XDA2i Pocke PC for more than an hour
and every time I start the Update Operation I got an error message and the operation corrupt agian it prompts me to reset it, after the reset, it informs me to disconnect the Pocket and Cardle USB, and reconnect it Again but it gave me a message on its screen told me Serial on the top of the screen, and on the buttom V1.01< What should I do?
Please Help me to get it alive again because it's dead now, and it won't work anymore, I need the method of booting it up, what are the buttons combinations to enter the boot again.
and If you gave the ROM Update for it, I'd be so grateful!! :lol:
PS: the Pocket information are
Pocket PC O2 XDA2i
Are you using a usb hub to connect, if you are then try plugging in direct to usb port. You will not be able to boot until you complete the flashing procedure, the program has probably wiped your previous rom.
It didn't work
Thanks sir,
but how can I do the flashing procedure, the Pocket PC wouldn't give the chance to do it!
and I've already plugged the USB directly to the PC.
Could you give the manner to falsh it again and boot,
because it is dead and silent
I'll be so grateful for your efforts

HELP!!!!

:?
I tried to make an update with the file JASJAR_WWE_11353_137_10301
Suddenly the Display stop et 99% of the extended Rom Update and on my monitor was an infomation like "an error happend"
After this, nothing else happend .
Yes, realy nothing happens anymore. I cant start the device not with power, not with reset or with power+reset
nothing nothing nothing
What can i do
If i start to try a new update, it schows me no information about what rom etc. is installed or what will be installed. if i then start i get the notice, that it is the wrong device.
Help me please. ist there any way to put the mda back to live?????
I guess i dont only need an update but the complete software
HELP!!!
I have the exact same issue after the upgrade. Nothing will happen. I spent several hours trying resets, combination of button pressed, removed battery, resets, just to try to get back the boot loader mode but nothing is happening.
there has to be a way to do this and I hope someone on this board had that issue before and got it resolved.
I had a similair issue with my old XDA II, it turned out my storage card was corrupted. Use a card reader to check your storage card is OK, perhaps format the storage card (having saved any data first of course) and see how you fare
Have had the same problem wirh a radio ROM update on my QTEK9000. The anly thin that still worked was the hard reset. After the hard reset the device still did not respond. But when i connected it to the PC I could start the updateprocess of the original ROM. I took about 20 minutes for the whole procedure and than the Qtek9000 was back in factory default (Pffff and I could breath again).
So perhaps you can try a hard rest and then connect aganin to the PC.
I allready tried this!
But nothing happens.
Even if i put the power device or the usb into the mda, no LED schows anything. just sometimes the LED is red for not more than a minute. if it then goes out, i get the message "Unknown usb device" in my PC
Are you in bootloeader mode? Do you see the words USB or Serial on the screen of the Universal in Portrait mode. Note: Backlight is off so you have too look real hard, but it should be there
no, i see nothing.
I had quite a hard time yesterday while upgrading. The bootloader is very hard to see, use a torch to lite up your display. In portrait view on the top should be the word serial or usb, on the bottom v1.00.
I also did a hard-reset in this stage, but it just returned to the bootloader menue.
If I connect to the PC and the device is recognized I see the word serial in the display change to USB. For me I do not know the reason but my PC did not want to fulfill the upgrade process. Needed to take another PC (Laptop) to solve the problem. After the upgrade of the ROM, You still need to upgrade the Radio (this was my experience) before a cold-reset will put You back to business.
Good luck.
Ruud
Having the exact same problem as gary_b and having performed quite a few upgrades, I can confirm there is absolutlely nothing on the screen. The unit will not go into bootloader mode or even able to do a hard reset. It is not recognized when plugged in the USB.
When connected to power and the hard reset procedure is done, the red charging light will come up for less than 1/2 seconds and disappear.
I tried all different combination to make it boot but nothing. If I could at least get it to bootloader more, I can revive it.
Feel very bad I cannot help here.
I was wondering Yesterday about one thing. IF, during all this upgrading process, the battery runs out, (as it does not seem to charge during upgrade process) will it show bootloader screen ?
Would it be possible to get a loaded battery from somebody to check yours ?
That is a good suggestion to try out, but I have been unable to find anyone that has that device. It might be simply a drained battery.
Mine got corrupted I think at the end of the upgrade right after I did a regular reset instead of teh power and reset procedure.
However, I would think that even with no battery in, the unit should power back up when plugged in no?
Maybe an idea for somebody who is doing upgrading now, and is in bootloader status anyway.
Take out the battery, but connect with USB to PC with ASync. Does the bootloader state show ?
I am sorry to not do it for myself, if You saw my desperate state Yesterday, You will believe that I am not willing to see that bootloader screen for some time, sorry.
Ruud
now i know what to do:
Nothing!!
I went to a service-point with my mda pro and there was nothing to do with it.
If this happens the complete memory is "killed". Like "format c:" and while format is running you switch out the power.
Thanks god: I got a new MDA pro because i did not tell them (in the store)that i tried an update!
But i called the service-line before anf they told me that there is nothing to do!
But thx
Wow, can't say that this is good informatuin for those with this problem, but very glad it worked out for You.
I ve had this problem 5 minutes ago. Finally a took out the battery. Then connect to AC and Red led is on. Then i put the battery, tried hard reset and message to confirm hard reset in the screen (wellcome to life, jasjar).Then i run radio update again and it's upgrading rigth now....buffffff
I almost suffered a heart attack when this happened an hour ago. Have found that the update works fine if the SD card is taken out... phew.

Upgrade ROM code error

I have flashed many Custome ROM's before. I have HardSPL installed on my phone.
I tried flashing to a ROM (I forget which one now, I think Cloudfa or something) and it stopped at about 15%. The Update utility stopped as well.
I cannot connect to bootloader at all. I tried holding down on Volume down/Reset to enter bootloader, but the thing is that it's already in bootloader with the message "Upgrade ROM code error, Please try again"
ActiveSync doesn't see my phone either. In fact all it does is just sit on the bootloader screen with that error...
Please Help... Thanks You...
A normal soft reset still brings you back to Bootloader?
What happens when you plug in your device? Does it not change from serial to USB at the bottom?
band27 said:
A normal soft reset still brings you back to Bootloader?
What happens when you plug in your device? Does it not change from serial to USB at the bottom?
Click to expand...
Click to collapse
Sorry. Yes it does show USB when plugged in, but won't respond to anything that I have tried software wise. It does not switch from this bootloader/error screen at any point. Even after I pull my battery and turn it back on...
I have yet to come across a thread which has this exact problem...
jzalapski said:
Sorry. Yes it does show USB when plugged in, but won't respond to anything that I have tried software wise. It does not switch from this bootloader/error screen at any point. Even after I pull my battery and turn it back on...
I have yet to come across a thread which has this exact problem...
Click to expand...
Click to collapse
Have you tried flashing a different ROM while in bootloader?
^^ Yes. It give me an error on my computer...
I would like to try the internal flashing method but I don't seem to have a way of getting at my Storage Card.
I found this thread with a similar problem
http://forum.xda-developers.com/showthread.php?t=480022
I WAS just able to get off of that screen I was talking about, but the best I get is to the Touch Diamond Screen that lists my ROM and such. So no real progress.
I have a feeling that I would resolve my problem if I could Flash from the Interanl Storage...
Have you tried hard resetting the device?
Pull out stylus and Holding....1) Vol. Down 2) Center Round button 3) then press red button aka soft reset with stylus
Nothing...
im stuck
hi all i am very new to this im not sure what i have done or how to fix the problem i download these this morning and they worked
rom version 1.57.831.1(47324)wwe
radio version 1.14.25.24
protocol version 52.64.25.34u
when i bootload in tri colours screen it shows
BLAC100 32M
SPL-1.56.OliNex
MicroP-Blackstone (led)v6
if it shows that i must of done something right i think of what ill read
and i have windows 7 ulitmate and i have Miri_WM65_21815_V19.0_Premium
when i double click on the BLACKSTONE RUU WRAPPER it crashes then i rename a new folder and done it from there and it works but it comes up wit error 208 file open? then i got told to rename to ruu_signed.nbh file to blacimg.nbh and to store it in the root of my sd card done that then somehow i got it to come up to the screen by Turn off the phone, press and keep pressed volume down button and while keeping it pressed turn on the phone then i see a message "Press power to flash your device" and i press power to flash got to 0% and it crashed and come up with Upgrade ROM code error plz try again and stuck in bootloader mode but now it wont even turn on its dead it wont turn on no matter what i do can someone plz help
all i want to do is get windows mobile 6.5 working i cant understand that it can be so hard to do
thanxs blueboys25!

I think i bricked my phone...please help!

Ok, so I have flashed a ton of ROMs, very successfully I might add. This last ROM I flashed worked just fine. After a day or so it started having some issues, so I tried to restart it. It started booting back up, and never left the HTC Innovation screen with the red text in the lower right hand corner.
I have hard reset it several times, and still I get the same thing. I can get to the boot loader screen and get it to change from serial to usb when plugging it into the computer, but this is as far as I get. Can someone please help me, thanks in advance!
Mark
PS I have also searched the forums, but unfortunately don't know quite what to search for. Thanks again!
Enter in the Bootloader mode (VolDown when reseting), plug the USB cable and install an older ROM via CustomRUU you know is working..
enter bootloader , use MTTY - http://forum.xda-developers.com/showthread.php?t=540290 to format rom memory .
Then flash it with a stock rom from www.HTC.com
Thanks
Thank you both for the help, trying now...IT WORKED!! Thank you guys so much!
Enter bootloader successfully means your phone is not bricked yet.
1) Use MTTY do delete old ROM
the command is "task 29"
Search the forum "MTTY" to learn how to use and where to download
2) Flash new ROM. Done
satus said:
Enter bootloader successfully means your phone is not bricked yet........
Click to expand...
Click to collapse
May not always be true !?
Here's output of 'TASK 29' (end section)
Flash NAND DM internal transfer failed: dmov_transfer()bad=0x7FF
R:NO bad block reversed for block ID 0x7FF
Read sector fail!!!
Can someone enlighten and lead ....
task 28!!! NOT 29!!
more precisley "task 28 55aa"
Dont typo the MTTY commands as it can completly screw up your phone...
please help after flashing a couple of roms i started having some problems
like everytime i reset it does a hard reset and now it doesn't seem to leave the boot image with TOUCH DIAMOND
i cant understand what steps i must follow for MTTY on xp
MTTY didn't work for me
I bricked my phone a few weeks ago and tried everything i could find on MTTY and nothing worked, error after error, i got really lucky and entered bootloader and plugged my USB in immediately after windows 7 boot up and got away with it through CustomRUU. 6 hours to fix and 25 minutes sleep before work. But hey, fixed the diamond and thats all that mattered.
MTTY + Latest HardSPL should solve any problems if you still have access to the bootloader

[Q] Bootloader nightmare

I have a nordic HTC Touch Pro 2
This unit started acting up after I installed the Energy ROM from the 20th of December. It used to fail in booting occationally(fixed by attaching USB-power), but now it is thouroughly stuck in the bootloader.
This is what I see when I reboot:
RHOD100 32M SS-BC
SPL-0.85.OliNex
MicroP(LED) 0x0A
MicroLED(KEY) 0x04
TURBO HW/TURBO SW
TP MFG DATA
509,521 792,844
795,200 221,198
226,843 Calibrated
Serial (changes to USB when connected)
There is a quick flash of 2 previous screens, one tri-color and one saying something about no image to load.
I belive, but would be thrilled to be proven wrong, that I have tried all tricks.
Running Windows 7 I first disabled device driver signing and loaded the HTC USB driver. Downloaded mtty 1.42, connected to the phone via USB and ran "boot" command.
The only problem listed was one bad block in CE.
Tried reboot again with same error.
"info 8" revealed that the bad block is 370.
Ran "task 29" but it gave an error trying to delete block 370.
Rebooted and tried to flash latest 29007 Energy ROM. No errors reported during the flash, still when it rebooted after reaching 100% it stopped in bootloader again.
I have also tried this procedure and replaced the Energy ROM with the latest original nordic ROM. When I use "boot" command from mtty I get the HTC screen (white background with htc in green letters) but the phone apparantly is stuck there. A soft restart brings me bach to the bootloader again.
Is my phone bricked? I'm not sure what to do or try next and as I have seen others report my battery is draining and will not charge(no light) when plugged in to computer or charger.
Thanks in advance, I love what you all do for this community and wouldn't have still used tha TP2 if it wasn't for all the great ROMs presented here!
NVM, re-read and see you already tried my suggestion.
Additional info
I ahould add that I also can't do a hard reset. Pressing and holding send and end and then power button only result in getting the bootloader menu. I borrowed a freshly charged battery and tried loading a new ROM, but no change, it still only restarts to the bootloader after completion.
If you can get into bootloader and the usb shows when plugged in, you should be able to flash back to stock via RUU.
Try this;
Open your downloaded ROM with unzipper. You should see two files, the RUU and the RHODIMG.nbh. Copy the .nbh onto the root of your SD card. Powerup the device holding the volume down. It should boot to bootloader and immediatly look for and find the .nhb and install it.
Hope that helps.
Hi!
Thanks for your answers! Sorry about the late reply!
I tested with RHODIMG.nbh file(29007 Energy) on the SD-card. The installation started and ran as expected. When done the screen showed the following info:
"RHODIMG.nbh - OK
OS - OK
Update Complete
UPDATE SUCCESS"
There were no button to press on the screen, and pressing the power-button didn't do anything. I eventually removed the battery, reinstalled the battery and pressed the power button. Unfortunately for me I was once again presented with the bootloader screen.
Any ideas to a new approach? I really don't want to write off the phone as bricked, it should have about a year left in it before I consider replacing it.
Try this:
When powered off, attach headset to the phone. Then press power button.
My Touch Pro2 ran into the same situation recently, showing nothing but a 3-color screen with the same information as you listed. I haven't tried mtty but I found if I plug in the headset, it boots normally. No idea why...
It sounds like an error in the instruction set for the bootloader. Maybe cmonex can help you with a bootloader-friendly version of Hard SPL to re-flash.
cajunflavoredbob said:
It sounds like an error in the instruction set for the bootloader. Maybe cmonex can help you with a bootloader-friendly version of Hard SPL to re-flash.
Click to expand...
Click to collapse
he already has Hard-SPL so he could just reflash it with the Hard-SPL exe in manual mode, but as the version number is the same, the device may skip the updating of the SPL. if the OP wants to try this, I can make one with a different version number. though I seriously doubt that the issue would be fixed that way...
Headset trick
Hi,
Again, thanks to all that try to help me!
I tried the headset trick just now and look and behold, it actually worked! My limited brain can't come up with any plausible explenation but I'm happy anyway
I do remember reading about this trick at some point, but I couldn't locate a headset until today. Thanks lilei105!
Now I will reboot the unit several times to ensure this wasn't just a coincident.
Edit: Booted 4 times, still no problem. Have booted both with and without USB-cable connected to PC.
Yeah my advice would be re-flash it or install/download a different ROM.
i may be way off here, but could it be a problem with the volume down button on the unit? maybe the headset bypasses the standard volume button?

Categories

Resources