bricked bootloader wallaby (qtek 1010) (O2 XDA) - Upgrading, Modifying and Unlocking

during a ROM flash (rom build with romkitchen), the flash procedure hangs with the "5 minutes..." notification. After a softreset i still get the "5 minutes" screen.
After this disaster, I'am not able to boot in to the bootloader screen anymore. Before this hangup, there was no problem to boot to the bootloader screen.
I reboot my XDA (wallaby) with "press the powerbutton en the resetswitch". The xda reboots, does not show the bootloader screen, but shows right away the "5 minute..." screen.
I have already tried the tool "pnewbootloader" without any result.
Activesync does regonize my anymore, says: not connected.
Is there a way the restore/rebuild/re-flash the bootloader on my XDA (qtek 1010) wallaby?
Thanks in advange.
Greetings
Patrick

Today i have tried to connect to my XDA (wallaby) with "mtty".
when i place my xda in the cradle, mtty is able to connect, but there is no "USB>" prompt.
When i take the xda out the cradle, mtty is unable to essablish an USB-connection. So i am sure that mtty is able to connect to the XDA, but only with out a promt. Due to that i am not able to send commands to the xda.
I also found the JTAG solution, but i'am not an electric expert (i am no good in solder). So the JTAG is no option for me.
I anyone has a solution i would be very thankfull.
greetings,
Patrick

Related

xda in bootloader mode

Hi.
Think I have a real problem. My xda2 is in bootloader mode ready to be re-rommed, but my activesync (3.7) will not register that xda2 is connected. Tried loads of times re-installing activesync (different versions) with no joy at all. xda2 just sat there with dark screen waiting for rom. Please help.

Not even stuck at Bootloader :(

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....................

XDA Stealth Bootloader Mode

Dear All,
I'm stuck with this XDA Stealth, and guess I need help from you people.
How can I enter Bootloader Mode on XDA Stealth? ( I can enter engineering mode, but can't see any option to enter Bootloader i.e. tri-color screen).
I'm unable to upgrade ROM on this device because of the following reasons.
1. I upgraded WM6.1, and found that Active Sync won't work unless patched.
2. The display's touch screen is defective so after up ROM Upgrade, I'm stuck at align screen, further, the phone is not getting detected in windows as there is this patch required for the ROM.
3. I don't have miniSD reader and also I don't think the car works properly.
So, is there any way to enter the bootloader mode and get the device detected under windows so that I can upgrade again?
wbr
Sonny
For active synch problem, try this
go to setting..connections...usb to pc and uncheck this one
and connect again ....hope this will help
I'm stuck on Align Screen due to bad display. I cannot connect to Active Sync due to bad/cooked ROM.
This is Catch 22
Is there any way to unbrick this phone.

My Dash stuck on the red,green,blue screen (please help)

Yesterday, I tried to upgrade my T-mobile Dash ROM to WM6.1 ROM by kavana. I downloaded and ran both the SDA application unlock and the Excalibur USPL - Cid Bypass. After I completed all the steps, I run the upgrade ROM but it failed at 4% with error 270. After that, I turned the phone off and turned it back on; however, it now stuck on the red(ONBL1.10.0000), green(SPL1.10.0000), and blue(IU) screen every time I turned the phone on.
After I searched using the search function in this forum, I found several solutions, but none of them work for me. I tried to do hard reset (pressing soft buttons) with no success. I also tried to flash the original T-mobile WM5 ROM with no success(error 260) even though the phone is already connected to the PC. My computer cannot read the phone, but the USB indicator on the bottom right corner can detect there is a mobile device connected to the pc.
Is there anyway that I can do to repair my phone?
Same problem here.
On normal boot I get the HTC logo and nothing else.
Hard reset doesn't work.
I can enter the bootloader (Camera+power) but have attempted to flash several roms all failing.
Any suggestions please?
Thanks to all

Help neede - Bricked XDA Orbit

Hi Eveyone
Help needed please.
I came by an XDA Orbit that refuses to work. The symptoms are as follows:
1. When power button is pressed to turn it on the 02 Splash screen comes on for about 3 seconds then some red writing flashes up on the top left of the screen. The phone then turns off. No matter what I do it always does this. Once I have been through this sequence once it won't turn on at all. The only way I can get it to work is to take the battery out for about 30 seconds and re-insert but it never gets passed the splash screen.
2. I can get it to go in to the boot loader mode (multi coloured screen) and if connected to my PC will show USB in the bottom right hand corner of the screen. However Activesync will not recognise it and I therefore can't upgrade the ROM to try and fix it.
3. I have tried to flash the rom from SDHC card but nothing happens
Anybody got any ideas or is it screwed?
Thanks for your help
just read the last line here
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
Bricked XDA Orbit
So if you can't flash from a SDHC card how are you supposed to do it?
Is there any other way I can flash the XDA orbit or get it tom connect to my computer so I can flash it
Any help would be much appreciated
Thanks
you can flash it with sd
sdhc means sd high capacity and they are about 8,16gb
there are MILLIONS of threads about bricked devices,and at least a third of them is answered...please read before posting

Categories

Resources