Related
I have flashed dutty's v4 rom and i want to change it
the problem is that when i try to do so i run
KaiserCustomRUU
my device goes into the 4 stripes screen it says usb
but then the program in the pc says error 260 and doesn't load the new rom
my phone still works as dutty's rom is still in but what can i do to change it?
Thank you and i have searched a lot but could not find a solution
thimiost said:
I have flashed dutty's v4 rom and i want to change it
the problem is that when i try to do so i run
KaiserCustomRUU
my device goes into the 4 stripes screen it says usb
but then the program in the pc says error 260 and doesn't load the new rom
my phone still works as dutty's rom is still in but what can i do to change it?
Thank you and i have searched a lot but could not find a solution
Click to expand...
Click to collapse
OK lets start at the basics...... In bootloader mode (tricolour screen) what text does it say at top of the screen?
Have you DEFINITELY Sim Unlocked and CID unlocked?
it says these things
kais130 mfg
spl-10.0.Olipof
cpld-8
Ok that confirms you have the capability to flash. I have seen in the past some people have managed to flash one time only using jumpspl but then their device reverts back to original bootloader...I was one of those people
Next question then...Can you boot the phone normally and gain an activsync connection to it?
yes
i can use my phone normally
only i cannot put a new image in
Are you using Xp or vista? If using vista it may be worth trying a reboot... sometimes it goes doolally with its usb ports. If you cannot see the phone through WMDC or activsync after a reboot it is worth going to SYSTEM (on your PC) viewing non present devices through device manager,( Drop to Command prompt and type... Devmgmt.msc set DEVMGR_SHOW_NONPRESENT_DEVICES=1 ) removing the relevant phone connection and then re attaching it so that windows re detects it.
If you can get a connection via actvisync (win XP) or WMDC (vista) to your phone then all should be ok. Uncheck the activesync/ WMDC "allow USB connections" and try again.
If this still doesn't work then search around here for MTTY. That will allow you to specify the usb connection to the device...amongst other things.
thank you for your time
i have win xp and activesync works nice
the problem is when bootloader starts
When you attempt flashing, do you do it from the device already booted into windows mobile or direct from bootloader?
Which ever way you have tried it, try ther other way.
Not teaching you to suck eggs but just in case you dont know.... To get direct to bootloader hold camera button and soft reset with stylus whilst holding camera button down and the tri colour screen should appear.
With device at the bootloader screen, Can you confirm that you hear the windows "noise" when you unplug and re plug the USB cable just as you would when plugging and unplugging the device normally. This will determine if the device has connection at the bootlaoder stage.
why not just flash using the microsd card. its much easier that way
yes it has connection
the thing is that i have already flashed as i told before with dutty's v4
now i can't
Usually Error 260's are related to the USB port functionality ( Port can't be opened etc).
The SD card method or MTTY should sort you out.
thx again
hope it works
at least the sd trick worked!!!!
now running on winmob 6.1
Glad to hear you sorted it.
almost
i cannot use my sd card cause i have to have it formated in order to put a new rom in
thimiost said:
i cannot use my sd card cause i have to have it formated in order to put a new rom in
Click to expand...
Click to collapse
disable USB connections in ActiveSync and flash.
This Link gives a list of eror codes for Hermes, and probably the same for Kaiser.
It's likely that you have a USB port error - maybe try changing the USB port you use or a different sync cable - or just stick to SD card flashing in the future - I keep an old 1gig card for this.
this IS the problem...i cannot flash...
it stays in the bootloader with the message i wrote
thimiost said:
it stays in the bootloader with the message i wrote
Click to expand...
Click to collapse
It happen to me before hardspl again fix it, not sure why
you mean use the sd method to do hardspl again?
OHHH lord dutty we need your new rom
Hi. There is something wrong with my phone. When i tried make phone call. It stopped responding. After reset it goes to four color screen with serial word on the bottom. I never flashed this mobile. Now when I try connect to vista it shows massage Usb device Not recognized, same on xp, but serial changes to usb. Please Help
first of all, i'm not an expert
but there are some threads in this forum about it. the only thing i can explain is:
that you're stuck in the bootloader,
the usb vs serial thingie, is that vista makes any usb device like a serial one..
try checking the spl threads and 'stuck' keywords
sorry can't be of more assitance...
anduh, keep calm and relax.. there's a lot of knowledge here.
so keep breathing and don't go paranoid..
gl
you might want to provide us with some more info,
rom version?, if it sais anything more in the RGB screen
and 1 more thing.. tried removing the battery for at least 1 minute.. / removing sd / simcard
on boot screen i have:
KAIS130
SPL-1.81.0000
CPLD-8
r
emoved sim and memory card
removed battery for 30 minutes.
no change.
podhal said:
on boot screen i have:
KAIS130
SPL-1.81.0000
CPLD-8
r
emoved sim and memory card
removed battery for 30 minutes.
no change.
Click to expand...
Click to collapse
hi podhal,
1) go to settings of activesync and uncheck 'allow USB connections'
2) or just to make sure, go to task manager and kill the process 'rapimgr.exe' and 'wcescomm.exe'
3) download mtty from here: http://forum.xda-developers.com/attachment.php?attachmentid=71806&d=1203597568
4) connect your cable to your kaiser-- it should say 'USB' and not 'Serial' at the bottom
5) choose 'USB' in the drop down list of ports and click 'OK'
6) on the mtty screen press enter key and you should get a cmd>
7) type in 'boot' (without the quotes) and press enter. If it doesn't boot up, paste the output here. DO NOT EXPERIMENT WITH MTTY AND TYPE ANY OTHER THING AS THIS CAN MAKE YOUR PROBLEMS WORSE.
EDIT: do this on you xp machine and not on vista!
HA! Problem solved! something had to be stuck in Usb connector. I just cleaned it with a bit of alcohol. Its a bit odd it went to boot loader just because of usb problem. But thanks for help.
podhal said:
HA! Problem solved! something had to be stuck in Usb connector. I just cleaned it with a bit of alcohol. Its a bit odd it went to boot loader just because of usb problem. But thanks for help.
Click to expand...
Click to collapse
good for you now read and go inside the wonderful world of flashing ROMs, heheh
What you are saying is really interesting. I´m one of the various kaiser users expriencing such problem.
I already did everything you can think of, nothing solved the problem so far. The only thing I didn´t try yet was to completely wipe the kaiser and use frankenkaiser.
Are you sure the problem is solved for you ?!?
StealthNet said:
What you are saying is really interesting. I´m one of the various kaiser users expriencing such problem.
I already did everything you can think of, nothing solved the problem so far. The only thing I didn´t try yet was to completely wipe the kaiser and use frankenkaiser.
Are you sure the problem is solved for you ?!?
Click to expand...
Click to collapse
Try the frankenkaiser then It's pretty *safe* if you know what you're doing-- did it 3-4 times because I was trying to wipe out bad blocks. Make sure you have the right radio though and an old hardspl before you use it jocky patched the new spls to ignore task 2a command.
pfcsabre,
Did you mean that by wiping the kaiser out with the pre-frankenkaiser commands (task 2a or rtask a) the phone is formatted and the bad blocks are mapped out ?
I really think that my problem is exactly that: a bad block within bootloader area...
StealthNet said:
pfcsabre,
Did you mean that by wiping the kaiser out with the pre-frankenkaiser commands (task 2a or rtask a) the phone is formatted and the bad blocks are mapped out ?
I really think that my problem is exactly that: a bad block within bootloader area...
Click to expand...
Click to collapse
well I had 3 bad blocks before, but the problem that I had is my ROM area is writing to that blocks and what's unlucky is the critical parts of the ROM is written there (bad blocks are common, but of all the places.. sheesh) that makes my kaiser just reboot indefinitely. So-- what I did was task 2a and it removed only one, but it was enough to get me flashing flawlessly to any ROM
Nice to know!
Well, since I haven´t frankenkaised my kaiser before, I have a last question:
According to the documented procedure in this thread, there is no task 2a command, instead, in step 2, it is said to issue an rtask a.
Am I right to assume that, if I task 2a my kaiser, I´ll have to pick up from step 3 and on ?
tia!
StealthNet said:
Nice to know!
Well, since I haven´t frankenkaised my kaiser before, I have a last question:
According to the documented procedure in this thread, there is no task 2a command, instead, in step 2, it is said to issue an rtask a.
Am I right to assume that, if I task 2a my kaiser, I´ll have to pick up from step 3 and on ?
tia!
Click to expand...
Click to collapse
there is in step 3 task 2a which completely *bricks* the phone. But as it said, you would go through oemsbl which is the radio bootloader and not the spl (os bootloader) anymore since it's wiped out already. Read the whole thread before doing it, it's not for the faint-hearted
StealthNet said:
Nice to know!
Am I right to assume that, if I task 2a my kaiser, I´ll have to pick up from step 3 and on ?
tia!
Click to expand...
Click to collapse
spot on but you need to make sure the drivers are there. After task 2a it would detect your kaiser as new hardware etc., so you need to still install the qualcomm drivers from that thread.
Thanks for the help! I have a XP machine set up just to do that
Ok, let´s do it.
pfcsabre, maybe you can help me.
I'm stuck at step 6. I successfully ran frankenkaiser. It asks me to replug the USB cable, and that's when things go wrong. In fact, when I remove the USB cable, the drivers are gone and phone is not recognized anymore when I plug it back (windows says the device is not recognized).
What am I doing wrong ??
StealthNet said:
pfcsabre, maybe you can help me.
I'm stuck at step 6. I successfully ran frankenkaiser. It asks me to replug the USB cable, and that's when things go wrong. In fact, when I remove the USB cable, the drivers are gone and phone is not recognized anymore when I plug it back (windows says the device is not recognized).
What am I doing wrong ??
Click to expand...
Click to collapse
sorry mate, just saw your reply.
Maybe you're replugging it too fast, I had that problem also. It kinda takes time before you get it but you're right on track if you ran step 6 with the output
EDIT: I think I know what you did wrong.. I remember that problem before. Are you running the frankenkaiser unbricker radio from hell? if you don't have the radio 1.65.17.10 that won't work. You should ask jocky for the right frankenkaiser unbricker for your radio.
check you later StealthNet, it's 2am and I got to go work in 6 hours. Ta!
StealthNet said:
pfcsabre, maybe you can help me.
I'm stuck at step 6. I successfully ran frankenkaiser. It asks me to replug the USB cable, and that's when things go wrong. In fact, when I remove the USB cable, the drivers are gone and phone is not recognized anymore when I plug it back (windows says the device is not recognized).
What am I doing wrong ??
Click to expand...
Click to collapse
if it's not recognized, try installing active sync again "to load usb drivers", and try again
You incorrectly installed the drivers most likely.
But before you use Franken, you need to be sure you are using one compatible with your OEMSBL & Vboot version.
What was your last radio & rom version?
GSLEON,
I PMed Jocky and, unfortunately, I did it wrong. When I read the procedure to use Frankenkaiser, I mistakenly assumed that, since task 2a wipes out the phone, the radio version wouldn't matter.
In fact, Jocky explained to me that it really does, and that Frankenkaiser is tailored to be used with radio from hell only.
My last ROM and Radio version were the ones based on the latest Dutty's (radio 1.65.16.25).
My attempt to "task 2a" my phone was my last attempt trying to solve my colored brick (booting into bootloader everytime I turn on the phone). I think this is being caused by bad blocks into bootloader or radio area.
Hopefully, I'll be able to get out of the hard brick (task 2a) and it will solve my colored brick problem
In fact, if it does work, I think it will be usefull for lots of kaiser users (last time I accounted at least 4 ppl with the same problem).
Thanks for the help!
Hello XDA Nice Team !
By mistaken i wrote some file to my bootloader in my I-Mate Jam ..
That was after using the bad ROM : 2.03
it's the worst cooked version i saw !
Now my bootloader mode is working .. but no way to connect to PC with USB port ..
My computer does not recognize my Magican when plugged in bootloader mode anymore!
Bootloader Ver: 1.0
is there any way to fix or upgrade or restore original bootloader
Now i cant upgrade or downgrade my magican by any method
Noway to use successful connection with any roomupdate utility
Please help me to fix or restore my bootloader!
Thanks to any one read or replay or try to help or help me to resolve my problem
XDA lover
i'm sorry that happened mate...
i've had success with flash-from-bootloader attempts before, both on my Magician, when i accidentally flashed off of Vista and it'd enter the bootloader every week or on a reset using the reset hole, and also on my Wizard when i ignored warnings from WM5torage and it'd only enter the bootloader
what precisely happens when you connect to the PC, allow USB connections in AS/MDC, and let the phone enter bootloader however it does? i can just flash a rom from there, but i won't (iirc) get any reports of as recognising the device...
My experience:
1- when i plug my sd card into my jam .. usb not recognized in bootloader mood !!
2- when i use puty or roomupdate it reaches to USB> then when i type any command it does not respond !
3- i could do something .. i let my phone bootup and this i-mate logon screen stays 4ever .. i connected my ppc to pc and i could explre my imate by activesync ...
i could reach something .. when i explore my phone and remove everything from startup folder .. my phone boots .. and i can see start botton .. no touch alignment comes .. and everything works .. but.. screen is virtually reversed .. i can see the OK botton but i must click on the facing area and it be clicked ..
i think i executed some wrong hard SPL to my phone ant that happened >
is there any way to resolve this problem?
is there any way to erase flash on my I-Mate Jam????
is there any way flash my phone?
i also have prepaid JAFWM with pkey and USB cable .. no BOX ..
Help please!
that's messed up... howsabout flashing it at the point when the phone boots up? if there's an AS connection there, then it may work... i'd flash to an official rom though
Same problem , PLS Help !!!
Thx for help
You should check USB connection I think...
Try plug your battery out of device and wait a moment (e.g.10 minutes) and try again,sometimes it will be fine when you did this.
If your magician isn't detected at ALL by your PC when plugging the USB cable into it (i mean, no new hardware; no unrecognized hardware; nothing is detected in your PC when you plug the USB cable), and unless you had previously made a SD backup of your entire Flash with this procedure ( http://wiki.xda-developers.com/index.php?pagename=MagicianSDflash ), then your only option will be to build a JTAG diag cable:
Here are some general directions / ideias:
Magician JTAG pinout: http://wiki.xda-developers.com/index.php?pagename=MagicianJTAG
How to build/run the JTAG: http://wiki.xda-developers.com/index.php?pagename=DeadBoot
Photos : http://www.cf-box.com/htm_data/55/0912/1679.html
Some interesting stuff for debugging problems: http://pda2u.ru/ptopic205.html
For sure cotulla has one built so to test his ROMs + bootloader - maybe he will be willing to give you some directions if you run into problems, and above all, give you a prepared .nb0 (with the bootloader file) for your magician, which i do not know if there's one out there, extracted from an original ROM.
Anyway, you can always try and do it for yourself using itsme utilities. Follow this link: http://forum.xda-developers.com/showthread.php?t=218643
Regards
Keeper,you're awesome! I'm searching for JTAG,too
xiaojin1985 said:
You should check USB connection I think...
Try plug your battery out of device and wait a moment (e.g.10 minutes) and try again,sometimes it will be fine when you did this.
Click to expand...
Click to collapse
Dear xiaojin1985 ,
Thx for your help, But unfortunately i tried your solution but it dosnt work !
Dear Keeper,
Thanks too for your help,
and i think the solution for my problem is one of the solutions you says ( How to build/run the JTAG: ) ,
but the pictures is not available anymore , so pls can you get the pictures ?
All the pictures are in here:
http://s218.photobucket.com/albums/cc23/alex_beda/ and in attachment there's a .mth file with all the pics built-in.
Don't take it wrong what i'm about to say, but in all honesty if you can't figure this out yourself (digging up the internet for the missing pics), i would suggest that you shouldn't try this, since this ain't easy at ALL...
Just to give you some ideias, it will require you to adapt your magician test point signals (TDO;TDI; nRESET; etc,)seen on the magician pinout pic to what is said; solder very thin wires (best done with a small hot air tip); fixate the small dip switch (micro switch) to be always on; keep the USB connected...idk... plus alot of other small details which ain't easy to accomplish.
Personally i haven't tried this yet but for sure it would work
If you decide to go ahead, please post some results!
Connection error solution
this is my problem
hi all. A friend of mine gave me an S100, and after i played for a few days with it, i decided to update it's rom. A "country error" problem appeared,cause i have the greek version, so i ran MaUpgradeUt_noID.exe which completed (as showed 100% process). My (new) problem is that i cannot update anymore. Every time i enter boot menu, i ran the upgrade
(HTCMAG_ROM_WWE_O2.rar) following all the steps normally. When the device resets (so the upgrade is going to start), it's re-reseting again and showing ERROR 101 connection error. Any ideas?
Qtek Greek version
R 1.12.00
G 1337.42
D 1.12.00 WWE
P.S. apart the problem everything is function properly
and the solution
hard reset
plug usb (uncheck allow usb connection in activesynch )
run MaUpgradeUt.exe radio_1.11_greek but idont reset the qtek in first screen
and upgrate downgrate start all ok
reset
welcome screen
hard reset
plug usb (uncheck allow usb connection in activesynch )
run MaUpgradeUt.exe MagicianRadio_1.12.10. uk but idont reset the qteki n first screen
upgrate from radio 1.11 to 1.12.10
reset
welcome screen
hard reset
plug usb (uncheck allow usb connection in activesynch )
run HTCMAG_ROM_WWE_O5_251209
everything is ok my magisian run the new Rom
here..........................
My Dear Samaritans,
IMPORTANT:
- My SD/Memory card is removed
- My Sim card is removed
I was upgrading to Tomal v8.9 on a vista 64 system via a virtual machine XP SP2. Update failed and I got stuck in bootloader.
Tried reflashing but got an error and the flash failed... also the program crashed during recovery.
Tried using v8.71 still crashed without any luck.
Moved to a pure XP SP3 desktop...
When I connect the device to the computer(s) "Serial" changes to "USB" but XP sees it as an unrecognized device.
Tried flashing again but same error as on the virtual machine.
Tried mtty (1.16 & 1.42) but neither give me the option of USB, only COM1 and COM2. And had already de-activated the USB connection in Activesync.
Have read through the forum but have had no luck. Everyone's issue is resolved as soon as they remove their SD or SIM, but I have neither and am also using XP with activesync's USB disabled.
Tried UNI_ExitBootloader but that does not find/recognise the device either.
If it helps -- My device is/was an O2 XDA Exec (Stock) which I had previously flashed with Tomal's v8.5
I am ready to try anything, please help!
P.S: The error is Error 112
Did you install ActiveSync on xp pc?
If not, do it now and try again.
I had similar problem. Had corrupted DOC sector
and MTTY was the only solution, but although the Serial changed to USB, I got 'unrecognised' message and Mtty didn't give USB as an option. At some point it occured to me that it was my computer's USB port, for some reason the device was recognised by 1 in 4 ports only, So I just tried my USB cable in different ports until the 'device unrecognised' messaged stopped appearing. Finally, after I was ready to cry in frustration, it just worked. Don't give up.
I heard it mentioned somewhere that the device that went through Mtty will be recognised only by the port used in Mtty procedure.
That... or your device's USB is no longer properly attached to the mainboard.
tomal said:
Did you install ActiveSync on xp pc?
If not, do it now and try again.
Click to expand...
Click to collapse
Already have activesync 4.5 installed with USB connection disabled...
Thank you so much for the prompt response and helpful thought!
enigma1nz said:
and MTTY was the only solution, but although the Serial changed to USB, I got 'unrecognised' message and Mtty didn't give USB as an option. At some point it occured to me that it was my computer's USB port, for some reason the device was recognised by 1 in 4 ports only, So I just tried my USB cable in different ports until the 'device unrecognised' messaged stopped appearing. Finally, after I was ready to cry in frustration, it just worked. Don't give up.
I heard it mentioned somewhere that the device that went through Mtty will be recognised only by the port used in Mtty procedure.
That... or your device's USB is no longer properly attached to the mainboard.
Click to expand...
Click to collapse
Thank you for the ray of hope! Will keep trying every hourly reboot in every USB port (4 in all).
Weird thing is I never had to go through mtty before so this is my first need for it.
Got the physical connection checked and it is supposedly OK...
Thank you for the prompt help...
Don't worry
I had exactly the same problem. First I tried this and it worked but still no connection via mtty. On that evening I disconnected and connected a lot and I removed the battery for a long time (one night). Later I could connect but I don't know why. Maybe these two things were the solution. Mtty showed "usb>" and I've done a DOC format...
If nothing works I would create a rom-image (on sunday or monday) for your sd-card like it's written in the service manual.
blingin said:
Thank you for the ray of hope! Will keep trying every hourly reboot in every USB port (4 in all).
Weird thing is I never had to go through mtty before so this is my first need for it.
Got the physical connection checked and it is supposedly OK...
Thank you for the prompt help...
Click to expand...
Click to collapse
No need for hourly reboots, just get into Bootloader, connect USB to your device and try different ports on computer with a few seconds in between to ensure no 'unrecognised device' message popping up. Once you'll get a connection - go for Mtty facility, the USB is the last on the list of ports.
330e said:
I had exactly the same problem. First I tried this and it worked but still no connection via mtty. On that evening I disconnected and connected a lot and I removed the battery for a long time (one night). Later I could connect but I don't know why. Maybe these two things were the solution. Mtty showed "usb>" and I've done a DOC format...
If nothing works I would create a rom-image (on sunday or monday) for your sd-card like it's written in the service manual.
Click to expand...
Click to collapse
There was no SD card when I began the initial flash but it still got stuck. Been trying without the SD and SIM but to no avail...
Thank you for the manual, downloading it now, will keep everyone posted in case anyone else is suffering from the same thing...
enigma1nz said:
No need for hourly reboots, just get into Bootloader, connect USB to your device and try different ports on computer with a few seconds in between to ensure no 'unrecognised device' message popping up. Once you'll get a connection - go for Mtty facility, the USB is the last on the list of ports.
Click to expand...
Click to collapse
Still trying, will keep you posted and thank you for the responses!
I think you understood me wrong. When your device is still unusable, I would create the files you need to do the steps in point 8.3 (Use Pre-loaded SD card to Re-flash Unit) in the service manual.
Sorry for my bad english
330e said:
I think you understood me wrong. When your device is still unusable, I would create the files you need to do the steps in point 8.3 (Use Pre-loaded SD card to Re-flash Unit) in the service manual.
Sorry for my bad english
Click to expand...
Click to collapse
It's the thought that counts not the language, thank you so much for your help!
I created succesfully a pre-loaded sd card, flashing via this sd works. But I can't copy the files. When I want to open the drive it says, that I have to format the sd card. Is there a special tool to copy the files? Or you find someone near you with a universal.
your need to format your SD after flashing.
330e said:
I created succesfully a pre-loaded sd card, flashing via this sd works. But I can't copy the files. When I want to open the drive it says, that I have to format the sd card. Is there a special tool to copy the files? Or you find someone near you with a universal.
Click to expand...
Click to collapse
tomal said:
your need to format your SD after flashing.
Click to expand...
Click to collapse
Tried the SD image method with a 128MB SD but didn't work. Maybe because I have a G4 and the method is for G3
managed to get a connection finally and ran MTTY, after "task28 55a" it just hung for a long time so I disconnected.
Tried running UNI_ExitBootloader.exe and now can get in and out of Bootloader but still cannot flash or connect...
Any suggestions welcome...
Try this....
This might sound silly but it's worked for me in the past.
1. Go into bootloader (without mem card or sim)
2. Plug-in the USB cable
3. Hold the buttons to go into bootloader again whilst plugged in.
4. DOC Format
5. Flash ROM
My Universal had loads of problems but that is how i fixed it, tried everything else like you, when i first plugged it in on the bootloader nothing happened until i pressed and held the buttons whilst it was plugged in, then windows made the usb connected sound so i quickly mtty'd! lol
Hope this helps, Good luck!!!
martinbrettphilo said:
This might sound silly but it's worked for me in the past.
1. Go into bootloader (without mem card or sim)
2. Plug-in the USB cable
3. Hold the buttons to go into bootloader again whilst plugged in.
4. DOC Format
5. Flash ROM
My Universal had loads of problems but that is how i fixed it, tried everything else like you, when i first plugged it in on the bootloader nothing happened until i pressed and held the buttons whilst it was plugged in, then windows made the usb connected sound so i quickly mtty'd! lol
Hope this helps, Good luck!!!
Click to expand...
Click to collapse
Thank you...
Xda2 stuck in bootloader screen after failed flash in vista
blingin said:
My Dear Samaritans,
Tried reflashing but got an error and the flash failed... also the program crashed during recovery.
When I connect the device to the computer(s) "Serial" changes to "USB" stuck within the bootloader screen
Tried mtty (1.16 & 1.42) but neither give me the option of USB, only COM1 and COM2. And had already de-activated the USB connection in Activesync.
Have read through the forum but have had no luck.
I am ready to try anything, please help!
P.S: The error is Error 112
Click to expand...
Click to collapse
Hi i have had similar problems also i have an XDA 2 pda originaly had wm2003 on it (tried to flash it to wm2003se ) can someone help me also im realy at a loss =C many thanks in advance (i will give more detail if someone actualy) replys to me
Wrong forum
Welcome to the forum
Universal does not means all devices, actually is a model
Please enter into the right section of the forum
Goos luck,
Can you Help?
I have an XDA II was on O2 uk network. I used to flash it all the time and knew my way around. however recently i flashed it in vista without thinking.. and as i upgraded the rom from wm2003 to wm2003se about 25% of the way through vista disconnected the device then it was unrecognised usb.. then vista started installing new drivers that recognised the device... however this then crashed flashing the rom onto the pda..
It wont soft or hard reset, i took the battery out for 24 hours and tried again and nothing.. the only thing on screen is that it says serial on the top of the screen (which changes to usb when connected but get error 101 when trying to reflash/ no activesync connection and am confused my mtty as when it does connect i cant type into the text area only paste)
on the bottom of the screen is v1.06 (which before the flash crash was V1.0 something lower than v1.06)
basicaly is the device recoverable as long as i have this serial / usb recognition by the device????? (using mtty i cant connect through ports or usb but thats because i dont seem to understand how to use it)
the other question is is there any other way to get a rom back onto the device without mtty or activesynch..
I pray that ysomeone will respond .. i miss my pda dearly
a thousand thanks in advance
Hi there, I tired to issue my problem in some other threads, but without any response so far - probably my problem is more specific.
I was using AHEN 6.5-R6i Rom for few weeks when some time after charging my Raphael was not powering up at all. I presume no relation between Ahen rom and the problem (as described further).
I bought new battery and it occurred that probably power charging circuit was damaged, because it newer completed charging, the device was always very hot and discharged in few minutes even when turned off (until completely drained out). What is more the USB connector works only for charging (maybe damaged data connection circuit?).
As a result, before returning the device for guarantee servicing I wanted to downgrade all the roms to the original ones. As advised I started with Radio and OS stocks, but after bootloader update (from SD card, cause my USB doesn't work) I got only "upgrading ROM code error" and the device tries to load some ROM, but putting any on SD card doesn't work anymore.
Any suggestions how to cope with this situation?
If you need help please provide us with important information. So fill your signature first. Mainly if you have hard-spl or if you bought olipro cid unlock and what exactly you have done until now. Also wether your device is CDMA or GSM? If it is GSM than you have to first restore Stock Radio first, after that if you cid-unlocked the phone you have to relock it again. Than remove hard-spl and install stock ROM. But if your USB is broken, i think there is no chance to remove Hard-SPL neither to restore to stock. Remember that when you are in a bootloader and you do not see that the device is connected to activesync or Windows Mobile Device Center it does not mean that it is not connected. Just check you hear the sound indicating that something is connected to usb in vista or windows xp.
If you need help please provide us with important information. So fill your signature first.
=> done
Mainly if you have hard-spl or if you bought olipro cid unlock and what exactly you have done until now.
=> chnged SPL to OliNex, OS to AHEN 6.5-R6i, Radio to version required by AHEN rom
Also wether your device is CDMA or GSM? If it is GSM than you have to first restore Stock Radio first, after that if you cid-unlocked the phone you have to relock it again. Than remove hard-spl and install stock ROM.
=> I retracked the changes as indicated changing both radio and OS to original ones, but had just problem at last step = flashing oryginal SPL (because I made it from SD).
But if your USB is broken, i think there is no chance to remove Hard-SPL neither to restore to stock.
=> Hmm, anyway right now I am stack because bootloader is "loading ..." every time I reboot the device.
Remember that when you are in a bootloader and you do not see that the device is connected to activesync or Windows Mobile Device Center it does not mean that it is not connected. Just check you hear the sound indicating that something is connected to usb in vista or windows xp.
=> I tried to use some terminals to see if I can execute commands directly or see any output, but I haven't even succeeded to open the port. Maybe I am doing something wrong - I give it a try once more tonight.
So what version of SPL is bootloader showing? If it's showing something like 1.90.0000, you are in bootloader and USB circuit is not damaged you should be able to normaly flash ROM from your provider from bootloader. So download the ROM from your T-Mobile it should be some exe. When you see bootloader tricolor screen coonect usb cable from Touch Pro to computer and run the exe soubor with your desired ROM. It should work if everything is OK!
If your device is showing 1.90.OliNex, than i cant help you because i do not know how to remove Hard-SPL from bootloader, maybe it is possible, but for more experienced tech guy, who i am not
PS: Hope you did not bricked your device because Hard-SPL and removing Hard-SPL is all done with cable, you cant do it from SD, and you cant flash original SPL before removing Hard-SPL!
hmm, it seems that I have managed to flash, at least partly, the original SPL from SD card, cause it shows version 1.90.0000. Partly, because it states that the previalus rom update was not successful :-(
In this state (in boot loader mode) I can't even charge battery so I have to do it externaly. Connecting to PC doesn't work (PC USB and cable are fine). The only thing that change after connecting to USB charger is that device gets hot ...
i am sorry to say, that you probably bricked your device... Maybe someone could help with more advanced hardware, software support, but i am not the right person...You can try to put your device to service and hope they will not recognize what have you done, but it depends on your stock SPL version. I got czech T-Mobile and stock SPL was 1.69.0000, so maybe yours was the same...
Next time please read more carefully, search or ask someone if you are not still sure, things about flashing SPLs are very dangerous if they are not done carefully...
Can anyone help this guy? He tried to flash original SPL over Hard-SPL, and therefore it is not looking very well for him to unbrick his Touch Pro...
So ... I got it from the service and they changed the motherboard and the battery, no charges
It was brickes, because of cherging circuit issue.
Unfortunatley I send it back to service, because the loudspeaker is not working ...
Actually I am the same exact boat as the OP. My phone stopped charging and its because the USB port is broken. I need to change the phone back to stock but if its not charging its probably not going to get a connection to the computer either. I read that on at least the Hermes it was possible to flash from the SD card. This is not possible for the TP? Thanks
riotburn said:
Actually I am the same exact boat as the OP. My phone stopped charging and its because the USB port is broken. I need to change the phone back to stock but if its not charging its probably not going to get a connection to the computer either. I read that on at least the Hermes it was possible to flash from the SD card. This is not possible for the TP? Thanks
Click to expand...
Click to collapse
You can flash the ROM, radio, splash screens etc etc from SD card - you will then have to send the phone back with hard spl still installed as you need a usb connection to remove it.
Dont assume you cant get a usb data conenction though - try it and see!
I did try the connection, didn't work. How do you flash from the sdcard? I just dont want to brick it.
Please read this thread on how to flash (including how to flash from SD card).
Again, (assuming you have the correct hard SPL currently flashed) you can flash a ROM, radio & splash screens etc to your phone from the SD card (one at a time) but as previously said you need a USB connection to flash hard spl (dont attempt it from the sd card).
So, my Raphael arrived from service after the second repair (loudspeaker not working) - it seems all works this time
By the way, that is correct that a USB connection is necessary to flash hard spl, but .. I was desperate because the USB was broken, so I tried it from SD. The effect was good enough for the service - the Hard-SPL seemed to be reverted to oryginal one, however the booting was stacked at loading the ROM