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 Help me pls,
I've tried to flash my rom via ActiveSync. Every thing went well until i get the progress bar then it got stuck at 0% for ages so i disconnect the whole thing and tried to restart the process.
NOW I CAN'T ACTIVESYNC ANYMORE !!!! but the connection as "memory card reader" still working.
I went through all the post and tried to flash the ROM via bootloader with the "RAPHIMG.nbh" in my SD card ( already formated FAT32 ) but every time the PDA got stuck at the first stage "loading".
HELP ME PLEASE
I have similar problem, can't connect to PC anymore, but flashing with SD card works for me
have you tried different ROM images?
TQY said:
Hi Help me pls,
I've tried to flash my rom via ActiveSync. Every thing went well until i get the progress bar then it got stuck at 0% for ages so i disconnect the whole thing and tried to restart the process.
NOW I CAN'T ACTIVESYNC ANYMORE !!!! but the connection as "memory card reader" still working.
I went through all the post and tried to flash the ROM via bootloader with the "RAPHIMG.nbh" in my SD card ( already formated FAT32 ) but every time the PDA got stuck at the first stage "loading".
HELP ME PLEASE
Click to expand...
Click to collapse
It sounds like you did not carefully read this.
That is also where this should have been posted. A new thread should not be started for this type of issue. I understand you are panicing. However, in almost all situations the phone can be recovered.
That said, Hold volume down and hit the reset button. It will put you in the tricolor screen. In the white it says serial. Connect it to your usb cord. It should now say usb. Now flash the STOCK rom.
be sure that battery over 50% then follow arupphental's
I have a friend with a kaiser and the same problem. can this be applied to it? i dont want to search through the forum forever...
I would start by going to the kaiser forums and checking the stickies. Search within the kaiser forum also works.
I have This problem on Vista OS, i connect my touch pro after reboot system, and if i disconnect device and try again connect, my system not see device!
On device manager in OS, my touch pro stay present after disconnect device. This problem retry if after connect i try flash rom on device, black screen on and flashing stop with error connect to device.
Please Help!!!!!
P.S. Sorry my Bad English
X2D said:
I would start by going to the kaiser forums and checking the stickies. Search within the kaiser forum also works.
Click to expand...
Click to collapse
ok i thought someone would say that. was just wondering off hand. thanks x2d
A.creature said:
I have This problem on Vista OS, i connect my touch pro after reboot system, and if i disconnect device and try again connect, my system not see device!
On device manager in OS, my touch pro stay present after disconnect device. This problem retry if after connect i try flash rom on device, black screen on and flashing stop with error connect to device.
Please Help!!!!!
P.S. Sorry my Bad English
Click to expand...
Click to collapse
go to bootloader (tricolor on screen)& flash a rom, your PPC 'll be fine. when you flash ROM, PC transfer data through USB to PPC therefor not need connect by activesync.
I had the same problem after a faulty ROM from Vodafone NL, what I had to do is before I wanted to flash my ROM do a hard reset on my device (please back-up your personal data before doing this). After the hard reset, I could get a stable connection with activesync and flash my ROM
While the circumstances are different, my advice is still the same: http://forum.xda-developers.com/showthread.php?t=481527
longnguyen30 said:
go to bootloader (tricolor on screen)& flash a rom, your PPC 'll be fine. when you flash ROM, PC transfer data through USB to PPC therefor not need connect by activesync.
Click to expand...
Click to collapse
Stumbled upon this.. and yes the advise is good, when you run the flashing utility (i.e. CustomRUU.exe), it says you need an Active Sync connection, but you really dont, you can flash it anyway, it seems to find the device via USB regardless.
ufff!!!! to me yes found right, thank you thank you to first post. (flashing from SD)
Undetected
Well i had the problem where my phone wasnt getting detected at all.... i put the stock rom and radio but couldnt put stock spl on the phone with sdcard.... after trying different computers/usb wires/settings i returned it for a new one and this one works fine.
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
Well, I've updated few htcs before and everything went fine. But there's always the first time...
I upgraded my htc hd2 spl 1.42.0000 to hspl2, wanted to upgrade rom/radio too, but couldn't find any rom I do like, and then I got no more leisure to play with it. So there was only hspl2 replaced on the device and that's it. Everything was fine for a month or two, then suddenly the phone function stopped to work (couldn't register into network anymore). Wanted to send back to factory for repair, but to avoid warranty loss I wanted to downgrade the hspl to stock spl. Downloaded stock image at htc site (was 1.48.something), did everything exactly in a way described in the video tutor, and - got stuck on light gray "Loading..." screen after the colourful one, and nothing more. Tried to update ROM via activesync for test, got stuck at 0% and that's it (although the connection is fine), googled a lot, browsed a lot of xda-dev... still nothing useful found.
Technical info + what shows in the colourful screen:
Eastern Europe HTC HD2
PB81100 HX-BC
SPL-2.08.0000 8G XE
I would really appreciate if someone could tell me, what it is, and how to fix it!
Thank you in advance.
I believe when you did the original HSPL, you selected the wrong version. The SPLs that end with '.0000' are the stock ones. Assuming the HSPL was done correctly it should read "2.08.hspl". Try flashing HSPL again, this time select .hspl, then flash your ROM. Should be good to go.
Edit: When people say you need a stock SPL to send it in for warranty, Im not sure if you need the exact same one it came with or not. Because you basically just reflashed a stock one anyway, you might be able to just send it in for repairs as is, but Im not 100% on that.
donkeypunch85 said:
Try flashing HSPL again
Click to expand...
Click to collapse
Thanks for the tip and trick. Unfortunately, like I said this doesn't help, cause flashing doesn't work. Tried hspl2 and hspl3 as well. The screen turns 3-color, then gray "Loading..." like it was when flashing from sdcard, and stucking on it...
When installing hspl3, the software on the computer says (while having that "Loading..." screen on the phone):
CRITICAL ERROR
Flow: 00000001
Error code: 00000002
Description: USB Connect failed!
(although ActiveSync shows connected and sync/exploring runs fine)
I'm becoming really unhappy with this one.
What OS is on your PC? Are you making sure Anti-Virus is disabled before flashing? If Win7 right click on the HSPL and choose 'run as admin'. Your using a USB slot on the rear (main motherboard) of your PC and not one of the front ones right?
It suddenly started to work today. I have no idea, what happened, did the same steps as before. The GSM function is still broken, but now, as the flashing worked finally, I'm able to send it back for repair without a risk to lose warranty. Mystical.
Thanks anyway for your time and willing to help.
...had the same these days on an HD2 which I successfully up-/downgraded at least half a dozen times before.
Did the MTTY 29 thing (again, surely the 6th time, never had any problem before) and afterwards had the issue you describe.
What helped me was re-flashing the HardSPL. Afterwards all worked 'as usual'.
Hope that helps others, Franky
Ok
and if my usb plug is broken?
I can't flash from sd, because it stops on the 'loading...' screen. I even tried the gold card method and still stuck on 'loading...'.
Wat's even worse my current system is rather unstable and WM sees only 208mb of ram...
Any suggestions?
T-mobile HD2! Problem Flashing rom
Hi Guys,
I'm a new guy in this great site, because I bought a T-mobile HD2 recently, via china, and it's not a fake!!!
But I want to update its rom to put the android2.2 's system.
I have tried several methods find in this site. But during the rom's flash, my phone shutdown and the connexion between Pc and phone switch off.
The phone is only in sleep mode and not off.
Can you help me to resolve this problem?
My system :
Phone :
Not SPL on the bootloader (only tri color) and this message :
" Error :
Copying file from SD card failed.
The system will shut down"
OS : Windows mobile 6.5 Professionnel
Software version : DUMA.10X.W10.20.P29
Protocol Stack (software) version :
MAUI.09B.W10.16.MP.V5, 2010/06/07
Dual Sim, and no take off SD card storage
Rom version : v01.00
Rom Date : Sep 10 2010
Boot version 2010 08 01
PCB version v01
Model ID T8585 (Leo)
Manufacturer HTC
CPU QUALCOMM 8250B (1024 MHz)
Ram Size 576 Mb
Nand Size 1024 Mb
Data bus 32 bit
Memory CPU 194 Mo
Memory storage 385 Mo
Memory inside SD card storage 7362 Mo
PC :
OS Windows XP SP2
ActivSyn4.5 Ok, but not synchronization with outlook, but connexion between PC and phone is OK.
Use update Rom Flash : Rom T-mobile v3.14 (run OK, no problem until progress bar (phone in sleep mode).
I tried SD card's method, unless sucess.
I used qmax to find SD card's number. But the memory's value is 3,5 Gb and not 7,3G.
Well, I think, I have forgot anything!
Thanks for your help!
Best regard
If you can get to the bootloader (four color stripes) then do so and then connect the phone to the PC. Wait until word 'serial' changes to 'USB'. Then start update on the PC (normally click the _RUU_(...).exe and follow the steps).
If fails please write at what point.
htc hd2
tomus said:
If you can get to the bootloader (four color stripes) then do so and then connect the phone to the PC. Wait until word 'serial' changes to 'USB'. Then start update on the PC (normally click the _RUU_(...).exe and follow the steps).
If fails please write at what point.
Click to expand...
Click to collapse
it fails at 8%.
So Im trying to reflash my fuze and Im having some big problems. I cant flash over the old ROM.... every time I try I get a connection error. Anyone ever run into this kind of problem? if so how do I avoid it and get around it..
I hook it up via usb cord and it connects to the computer. when I try to use the raphwrapper to update the rom it works..... goes to the rainbow screen and says something about no image. and the PC shows a connection error.
52 views and no help or input?
I think the issue is the neon rom uses some kind of GSM rom? my comp is looking for a GSM driver?
hey have you tried to hard spl your device?
try flashing with memory card
try to card flash
fomart your TF card to FAT32.
rename your rom as RAPHIMG.NBH
hold your voldown button ,reset you phone.
then follow the instruction on the screen