Wallaby Bootloader unaccessable - MDA, XDA, 1010 General

Is seems like I can no longer launch the Wallaby Bootloader program on my SX56 using the power button/softreset combination. How can I access this program now? My main problem is to flash the GSM ROM since my unit crashed during a ROM upgrade therefore forcing me to take it out its cradle without the GSM ROM installed. Now, I can't boot the unit up to re-flash the ROM using MS Activesync. How should I proceed? Thanks in advance!

have the same problem. I can't reach bootload menu. And something wrong happened with battery. It doesn't charge after a failed radio stack upgrade.

Failed ROM upgrade on SX56
It appears that our units are screwed... may have to either get it serviced or buy a new model.... is there any way to upload a new ROM image onto unit? I tried to install a new software upgrade but I kept on getting a message that I don't have the adapter plugged in, but in fact, I do. There is no green (or an light) indicating that the unit is either recharging or is fully charged. Does anybody out there know how to remedy this SX56 unit?

Related

Stuck in bootloader v1.06

I have only had my XdaII for a month, but last week it locked up and upon a soft reset it took 5 minutes to get past the O2 screen, then there was no responce to any screen taps, i decided to do a full reset, once rebooted still no response to screen taps, so i couldnt calibrate the screen or go any further, i connected the xda to activesync this still worked fine and was responding normally. I then decided to reload the rom from myxda.com, biggest mistake as it crashed halfway through now it just says Serial v1.06 or USB v1.06 if its in the cradle, now before i get bashed for just asking this question the same as a lot of other people have, i have spent the last 4 days go over this site trying anything that relates to getting any image back onto my xda, nothing has worked i have tried any nbf or nb1 image i can find on here with orginal or modified himaupgradeut.exe same response every time error 100: incorrect device type, i have tried any image i get can get onto an SD card, they either dont boot or wont allow upload, so my question is i have seen several people on here ask about bring v1.06 back from the dead but so far noone has had any instructions on how to this when a normal boot isnt possible.
I don't know if this is any help,but I had something similar.
I concluded that the rom on xda2 was newer than one being upgraded? with,so it says it won't work.I sent mine back to o2,but think that rom 172 or something, might be accepted.People say that you leave it 30 mins before it starts to upgrade.
There is a problem with bootloader v1.06 in that it will not allow 'downgrades'. It seems to have appeared on devices around the same time that ROM versions 1.72 appeared. I have read that it will allow installation of version 1.66 but nothing less than that (and that may apply only to T-Mobile). However, you should be able to install a version 1.72 ROM without to much problem.
My help
You can make the unit work again by downloading the rom version:
1. Ensure that the main battery has enough charge to make the unit in bootloading mode.
2. Execute the bootloading mode and connect the unit to the docking station(cradle), you will see the "Serial" in the upper portion of the screen will switch to "USB" this is an indication that there's a connection established between the pocket pc and your pc.
3. Then download the latest Rom version(1.72 is a better choice).
Thanks dcs and Juni
The 1.72 rom did get it going again .... but i still have no response on the screen so im guessing ill have to return it.
Does anyone know where i can get the 1.66WWE rom from as im assuming returning it with 1.72 rom on it may be frowned upon, and a voided warrany.
Thanks agian guys for your help
Does anyone know where i can get the 1.66WWE rom from as im assuming returning it with 1.72 rom on it may be frowned upon, and a voided warrany.[/quote]
talk to this person in here: :lol:
http://forum.xda-developers.com/viewtopic.php?t=12044

Dead xda2 stuck in seril v 1.06

Hi ,
I had 1.72.00wwe on my phone but i was tryin 2 upgrade it further but it got stuck while upgrading and its showing seril while not on cradle and while on cradle its showing usb 1.06
plz hlp me iam newbee and not good in programmin .I also have asecond Xda2 with 1.66.00wwe plz tell if it can b of any help
Reset your device, place it in the cradle and re-run the upgrade.
thanx i tried it already from 2 computers in one its showing error 103 no rom image found and in another its showing error 101 country code problem
Which ROM are you attempting to upgrade to? Which one exactly had you previously upgrade to? What operator do you use?
I'm asking all this to try and get a better picture. Normally, people in your situation can recover by applying the same upgrade again, or, at worst, re-applying the one they are upgrading from.
Make sure you are in bootloader mode (by pressing Jog button and Power button at the same time as pressing reset) before retrying any upgrade. Also make sure the USB cradle is plugged directly into a USB port on your PC and not through a hub and that the power supply is connected to the cradle. It may help to make sure that Activesync isn't running also.
active sync
in the active sync tray it shows that not connected
Well i had 1.72.00wwe rom image 1.14 earlier and iwas tryiong to upgrade to 1.72. something can't remember exactly but it was with rom image 1.17 it was downloaded from t mobile and my current phone is from o2
Click to expand...
Click to collapse
Activesync is not needed for upgrades. The upgrade process looks after its own connection. I suggest you follow the procedures in my post here to overcome the Country ID error problem. You will need to know what the device's operator and language IDs are currently set to, which is why I asked you above. I suspect you won't have Devicedata.txt, so it becomes necessary to know what operator and language the previous upgrade was.
to revive your XDA2 again
The main point is what is ROM 1.66 come from (e.g. i-mate ot T-mobile)
If you doesn't upgrade 1.66 ROM by yourself or it came from factory ,you must tell us which operator did you buy from.
If you try upgrade across operator ,it will hang on boot loader screen.
And again, which 1.72 ROM did you try to upgrade from?

TyTn update serious problem

Hi guys, I have some experience with rom flashing, and I did it today as usual - flashed HTC 1.35 ... Update stopped at 1%. I tried everything I could to finish the update (It wasn't my first time ). Now, after restart TyTn is flashing with LCD (black & white) & camera led. I can't do anything, even turn it off. Seems like a problem with bootloader. What should I try before i send it for repairing? Do you have any experience with T-Mobile UK? I'm the legal owner of PDA, but I don't have any receipt. Should I contact seller (ebayer) or post it to T-Mob straight away?
Thanks in advance, Jack.
Anyone please?
Check out the wiki for Tytn upgrade problems
I also had this problem, upgrade stopped at 1%....Left it for an hour and no progress. Had to stop update, which then left me at the boot loader screen (tri-color) screen. Tried Hard reset as mentioned above, no luck, still stuck in boot loader, tried to reload rom..got error 262 upgrade error
I had just run the unlocker and set device to super CID, and thought maybe that was my problem, but it wasn't
Luckily the wiki had the answer
Problem 4: Device is stuck in bootloader mode (tri-color screen)
>Disable ActiveSync: connections -- settings -- uncheck "Allow USB Connections"
Remove the battery, put it back in, connect the USB cable, power on the unit (this should allow the USB port to be opened again)
Wait a minute or two, if you get a message that device cannot be recognized just close and ignore it
Open
mtty.exe and select "USB" from the dialog box, then hit Ok.
You should see a white screen, hit enter and you should see a prompt like this: "USB>"
Type set 14 0 (do not copy and paste!!!) and hit enter
Soft reset with stylus
OS ROM and radio version should be back and OS functional, the unit isn't a BRICK anymore!
I had to reload the rom. step 8 did nothing, but return me to bootloader. This time the rom upgrade took about 45 minutes to complete. Weird, but it worked...This is first time in at least 4 rom upgrades with this device and at least 50 other rom upgrades that I ever encountered any issues.
POF...Thanks for the great wiki
http://wiki.xda-developers.com/index...ame=HTC_Hermes
Unfortunately, when it hanged on 1% connection was totally lost. Everytime I tried to run rom upgrade/unlocker/spl downgrader is said no connection. Now I don't have bootloader screen, only flashing LCD & camera diode. Any suggestions?
If you can't get the bootloader running then a service center will be the only solution I think.
Has anybody found the solution to this problem, my phone is doing the same thing. Can't get it into bootloader and screen & camera flash just blinks? I tried everything but to no avail.
Hi mate, have you done anything special or it goes bricked "without help"? I I still haven't put it to RMA because there's no T-Mobile in Republic of Ireland and I'm 2 lazy to go to Belfast
jackass_ass said:
Hi mate, have you done anything special or it goes bricked "without help"? I I still haven't put it to RMA because there's no T-Mobile in Republic of Ireland and I'm 2 lazy to go to Belfast
Click to expand...
Click to collapse
It's bricked trying to update it!!! If i could just get it to the bootloader, i can probably revive it but can't do anything. Can't access USB or nothing, I'll guess I'll send it off to a repair center.
Are there any good repair centers in the US???

Have I bricked my device? Help!!!!

I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up.
Now, the phone is dead completely. I can''t even enter bootloader mode.
Is there a possible way that I can still save it??
Help!!!!
Have I bricked my device? Help plz
I managed to upgrade my phone to aku 3.3 using pof's method(bootloader 1.01 MFG) . Then, out of no where, I tried to use MTTY to upgrade my radio rom
It started as usual with the status bar moving. Suddenly some error messages came up. Can't remember exactly, but like some address can't find error.
Now, the phone is dead completely. I can''t even enter bootloader mode. Only when I take out the battery and plug in the charger cable the red light comes on. I looked the upgrade problem page, my symptom doesn't match any.
Is there a possible way that I can still save it??
Help!!!!
I had something similiar happen a little while back. What I did was pull the battery out and leave it out for a while, maybe a few minutes. I then put the battery back in and held the two side buttons and hit the reset button to put me into bootloader mode. I then cabled it to my computer and flashed a new OS via mutty. That got my phone back and operational.
@float. Nuh, it didn't work on my brick. Prob i will have to take it back to Tmobile if they kind enough to repair the no warranty phone i bought on ebay.
Sorry to have opened a new thread, I was so desperate.
Plz delelte it.
how exactly did you try to update the radio using mtty?
I download the 1.27 shipped radio rom. P.S. It seemed to be a german version, not sure whether that caused the disaster.
Using NBHextract to get the single GSM.NB file, then in MTTY, typed
USB> task 32
USB> lnb GSM.NB
Before flashing, just had it upgraded to the HTC AKU3.3 OS rom only. The old version radio rom version before flashing was 1.18.
Maybe the order i flash is wrong. I flashed OS first then the radio rom.
just guessing
ok, you loaded the radio rom code where os.nb should go. That may have caused mega bad blocks in flash. Can you even get bootloader mode if you reset using Wiki directions to obtain Tri-color bootloader?
Yes. I have tried many ways wiki suggests. Such as removing the battery leaving it more than half an hour and plugging it to the usb cable without battery. still can't get to the tri-color bootloader mode. Basically, I just can't turn on the phone.
If you connect it to the computer, can it communicate w/the PC? If you hear the windows tones try opening up mtty and see if you can communicate.
i'm stuck in the same place
for me it happened during extrom flash
Try removing the battery for a bit (a few minutes, maybe half an hour). Then, put the battery back in but don't plug the usb cable in. After that, hold the two side buttons as if you're trying to get it to go into the bootloader. Hit the reset button a few times with your stylus and see if that gets you to the bootloader. That's what worked for me.
tried that
tried removing battery and connecting usb
nothing helps
is there a place that fixes tytn in belgium ?
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
diffda said:
is there a way to flash a new rom via mutty ?
cause i still have the boot loader, but the phone still in the splash screen
when i type info 2 in the mutty command prompt i get this answer
Cmd>info 2
HTCSQTEK_203”µ·êHTCE
i think it's not realy normal
Click to expand...
Click to collapse
well your not supercid... your still locked to qtek
Look here and unlock your phone before doing any flashing!
http://forum.xda-developers.com/showthread.php?t=295751
to late i ve done that tow day's ago , now the only way to make my phone back to life, PB + KITL method i think
god bless KITL

SPL flash failing

I'm following Mr Vanx's guide for upgrading my Jasjam from WM5 to WM6, but am having trouble with flashing the new bootloader onto the device. It's a second-hand telstra imate. I just bought it off ebay a couple of weeks ago and need to upgrade it to get it to read sdhc memory cards. I can't get it to connect to optus' (my mobile contract provider) mobile internet either, which I did via GPRS on my old phone. I'm hoping by upgrading the OS I can remove all of Telstra's code so It's not trying to connect to telstra's 3g network when I start the web browser.
When I get to the last step of the Hard-SPL installation, where the "updater will flash the new SPL and then restart your device (this will take generally less than a minute)" , the phone restarts almost immediately after clicking yes when prompted on the phone. The screen quickly goes to the bootloader screen, which says
"herm 100
IPL-SSPL by Des
Herm 100
SPL-1.09.ds"
The PC says that it can't connect to the phone and I should check the cable, which is still connected
The phone stays on the bootloader screen until I hit the soft reset, and WM5 boots like normal.
Has anyone else had this happen?
Yup,
Same problem over here. I had the problem before. But i fixed it! The only question is how did i do that? short term memory.
I'm trying to solve the problem. If its solved i will let you know.
Till then hang on
I've been trying again today. Still getting the same result, though I figured out if I just leave it when it gets to the bootloader screen, the pc I'm installing from eventually comes up with Error 260.
I'm thinking now that the XP firewall may be the issue, but I'm having trouble disabling it because it's managed by "group policies" (it's a work computer). I'm going to try either finding out which port to unblock, or starting the pc in safe mode so I can disable the firewall altogether.
I fixed the problem with the following softwaretool Hypercore. Just intergrate the Hard spl from olipro. After this the error dissapears.

Categories

Resources