Hello,
The only thing I want is to install NetFramework on a Wallaby but it failed!
System msg like, wrong file for device or something.
I read about this problem and die answer was to install wm2003se.
I downloaded it from here:
http://www.handy-faq.de/forum/htc_h...laya_rom_wm_2003_se_update_download_1086.html
But it wont install.
I get the Update windows like update from 4.xxx to 2.xxx
If i press next the wallaby restarts and nothing more.
After 2 mins the update tool said about connection Problems.
I have connected via the Wallaby USB Cradle.
Please some help...
Thanks
farmer.joe said:
Hello,
The only thing I want is to install NetFramework on a Wallaby but it failed!
System msg like, wrong file for device or something.
I read about this problem and die answer was to install wm2003se.
I downloaded it from here:
http://www.handy-faq.de/forum/htc_h...laya_rom_wm_2003_se_update_download_1086.html
But it wont install.
I get the Update windows like update from 4.xxx to 2.xxx
If i press next the wallaby restarts and nothing more.
After 2 mins the update tool said about connection Problems.
I have connected via the Wallaby USB Cradle.
Please some help...
Thanks
Click to expand...
Click to collapse
Is your Wallaby unlocked? It could be that if it isn't, you may be trying to flash a rom not meant for it (and hence, it errors out).
Related
Hi all,
This is my first post :x
I downloaded the ROM (4.00.10) from the kitchen. At first, I downloaded EXE file but when I start upgrading my Qtek reboot and nothing happen, I tried many times. I read about upgrading via SD. I did upgrading without any problem. BUT when it finish upgrading, my device won't start. It hangs-up at splash screen and showing ROM version and Radio Version only. I tried many many times with no success.
I need some help please
my device info:
ROM version: 3.18.04 ENG
ROM date: 05/22/03
Radio version: 4.21.00
Protocol version: 32s54
--
Model No.: PW10A1
Bootloader 5.22
--
Thank you in advance
Bailamos
Download again with NB0 then upgrade from your SD.
Download again with nb1 then upgrade from your SD.
Thank you, socheat.
But I did download nb1 and I tried upgrading with the sd method and the upgrading was successfully but my device won't startup it shows only the splash screen ( NOT FOR SALE ** Powered By Micro$oft ** ) and nothing happen after this screen
I restored my old rom (3.18.04 ENG) and the device is working now, but I want to upgrade to WM2003 :roll:
Is that cuz I upgrade the Radio ? my old radio version was 3.25 ( not sure ).
Thank you , All
Bailamos
Got same problem with you Bailamos
My Bootloader is 5.17
Now by XDArit + SD flash + Wallaby patch, I brought my XDA back to 3.20.06 original from O2 already.
Wondering should I downgrade Bootloader to 5.15 or not?
In XDArit it has one upper box which we can put Bootloader in.
Should I put something like "loader515.nb0" in that box during loading OS on SD?????
UP :? Please
update
Please , I need help.
I tried to downgrade my device:
Bootloader 5.22 => 5.15
ROM 3.18.04 => 14.04
I thought it may help upgrading but that complicate the problem!!
NOW , I can't do any upgrade. When I insert the SD card and start booting, it show me the boot screen : PRESS ACTION to start downloading. as soon as I press ACTION it show : GSM OK and nothing happened!!!! It looks like I pressed the exit button ( I PRESSED the ACTION )
The EXE method still not working , the same as before as soon as it shows : 5 min screen , my device restart and it lose the connection with the ActiveSynic
ANY one CAN help ? P L E A S E
Pretty Please
Thank you
yes it will loose sync, but just leave it there!
some times it takes 10 minutes
but it will finish updating, trust me! that worked several times for me.
Thank you , ntabikha.
I'll give it a shot right now.
it didn't work
when my device re-start , the Program ( 1.09 ) show this message:
Can not open a COM/USB Port. Please use Device Manager on PC to make sure that COM/USB port is available and working properly
and terminate immediately after pressing " Ok "
I think there is something I don't know !! but there is someone may know !!
Is that happening cuz I upgraded my Radio Stack ?????????? ???? ???
It was something about 3.xx and it is now 4.21 !!!!!
Hi Guys,
I need your help .
I've downloaded the 4.00.16 ROM by mistake, it really didn't tell the ROM number, so now I want to revert to a earlier one and I can't.
I've got the following message: "ERROR: GetDeviceData - An established connection was aborted by the software in your host machine.
error getting devicedata" and then "ERROR 011: EXECUTE REMOTE COMMUNICATION PROGRAM ERROR. Cannot execute the remote communication program. Please make sure that the USB/Serial cable is properly connected."
PLEASE HELP ME, I'M REALLY STUCK NOW AND DON'T KNOW WHAT TO DO...
sumaetee said:
Got same problem with you Bailamos
My Bootloader is 5.17
Now by XDArit + SD flash + Wallaby patch, I brought my XDA back to 3.20.06 original from O2 already.
Wondering should I downgrade Bootloader to 5.15 or not?
In XDArit it has one upper box which we can put Bootloader in.
Should I put something like "loader515.nb0" in that box during loading OS on SD?????
Click to expand...
Click to collapse
Have you tried doing it without the Wallaby patch part? If not give that a try, no on the bootloader downgrade part!
HTH
Hello
I did downgrade my Radio stack. It was 4.21 now it is 3.23.01
But that didn't change anything. I'm still can't upgrade my device to 2003.
The problem is:
Method 1: (Program A / B)
my device re-start and the program showing this error msg:
" Can not open a COM/USB Port. Please use Device Manager on PC to make sure that COM/USB port is available and working properly "
Method 2: (SD)
It shows me the upgrading screen
Press ACTION to start downloading
BUT when I press action it go the bootloader main menu:
GSM OK
!!!!!!
That's it !!!
At the first time, my device was able to upgrade but it freez after finishing the upgrade. Now, it wan't even upgrading !!
ANY HELP !! PLEASE ??
** to the people who saying you can't downgrade your radio stack , that's not right .. YOU CAN .. I DID IT **
Bailamos
I blew my bootloader some how and spent some time modifying the pnewbootloader source code to make it work for WM2003 ROM version 4.01.16
I took original source code by itsme and added version and address information for ROM 4.01.16
Use this in conjunction with a valid 5.15 bootloader image to downgrade your bootloader imaget to 5.15 from 6.22 or 5.22 or 5.17
type pnewbootloader_40116.exe bootloader_v5_15.nb0
to apply the bootloader.
FLASH AT YOUR OWN RISK. This program uses defined ROM addresses and will only work with known ROM versions. There are some basic checks to prevent damage.
Fixbootloader don't work
I have T-Mobile ROM 4.01.16 with bootloader 5.15 probably locket by this T-Mobile ROM (I can't flash any other ROM and original pnewbootloader whrite message "Unable to find flash info offset, cannor disable bootloader writeprotect")
When I trying to start you updated pnewbootloader, my WinXP popup a message
"The application failed to inicialize properly (0xc0000135). Click OK to terminate the apllication"
What should it be?.. :?:
This application needs ActiveSync and also the "itsutils.dll" to be located in the same folder as teh EXE.
Which version of XP are you using. I built it on a XP pro SP1 box.
I have exactly the same: WinXP Pro SP1
I run in cmd "pnewbootloader_40116.exe bl515.nb0"
from the folder, which contain
pnewbootloader_40116.exe
pnewbootloader.exe
itsutils.dll
pput.exe
bl515.nb0
Activesync 3.71 i connected to my XDA.
Cant really say why you are having this problem. But one this might help.
Seems like your .net framework is either old or not working.
Go to windows update to download and install the 1.1 .net framework or visit
http://www.microsoft.com/downloads/...e3-f589-4842-8157-034d1e7cf3a3&DisplayLang=en
Thank you for your help! The problem was realy in .NET version.
I had 1.0 installed on my WinXP.
After updating to .NET 1.1 your program is working fine. And it seems, that it updated my bootloader. Its output was
pnewbootloader.exe bl515.nb0
in FindFlashOffset (or somthing like this)
protection found at 8c0d62c8
result: 00000000 00000000
After that my device is still bootable and boot my 4.01.16
But I still can't update my ROM to 3.17.03 through XDATools..
Can anyone help me? plzzzz!
are you using xdarit to write your image to SD card ?.
You have to use SD card flash method to upgrade/downgrade the ROM.
Download XDarit and use that to write the image (.nb1) to SD card in 1k header format.
Then reset and boot your pda after holding the power button. You will see a menu which will let you flash your PDA with the image on the SD. Search for xdarit on the forum. You will find SD card flash process also.
rchir, when you said I blew my bootloader some how , did you mean you get GSM error?
Thanks
No,
I was unable to get into the bootloader anymore. I trid to build a boot loader upload SD card and it wiped out the boot loader from my PPC.
GSM error might be due to you Radio firmware failure.
Thanks, well, if you could figure out how to solve the Radio firmware failure, please post it, I'm sure many people here would apreciate it :lol:
would this fix my broken bootloader?my unit doesn't display anything on it's screen, I think I've already erased my bootloader pls help me, I'm so desperate about this.... i tried everything which inside this thread but my activesync can't detect my unit...SOS
I also have a broken bootloader ...
I have an xdaII, and I've somehow overwritten the original bootloader v1.06 with a corrupt bootloader image. Now my xdaII is completely dead. No leds flashing, no screen, no button response. All I get is a flashing red led when i rty to charge my xdaII without the battery. It seems I can't access my bootloader anymore. Plz help !! If you know any method to access the boot loader agin it be a great help. Thanks.
sorry guys, it has been a long time since i sold my XDA, but i think pnewbootloader will only work if you are able to connect your pda to PC with activesync.
So you should have a working XDA, with a broken bootloader to get it fixed. Seems like in your case, Both the ROM and Bootloader are corrupt. I am not sure about any process which will fix both at the same time.
can u post the download again? or pls send it to me [email protected].. THANK YOU..
(the download feature does not work, here in my computer, and another another computer appears a error message)
Hai
I have PWA1 work in wce 2003 GR 4.01.12 not work bootloder can't dispay because i wrong flash my bootloader himalaya ver. 1.29. plzz help my to change my bootloader 6-22 0r 5.15. please.
Hello,
I have flashed my MDA Vario with a WM6 rom dutch witch worked fine. After i changed my pagepool to 6 MB and soft rebooted my MDA, it stared, but without phone functionalty. every program i try to start it gives me the message that it has no memmory to start the program.
No activesync connection (or any other connection) can be established. I have found some articles on flashing xda pda's from sd card. But in these articles they talk about .NBH files. The only file i can find in the update util is an .NBF file. Can anyone help me solving this issue?
TNX in advance
Try bootloader mode?
Bijdehandje said:
Hello,
. . .
No activesync connection (or any other connection) can be established. I have found some articles on flashing xda pda's from sd card. But in these articles they talk about .NBH files. The only file i can find in the update util is an .NBF file. Can anyone help me solving this issue?
TNX in advance
Click to expand...
Click to collapse
Can you get into bootloader mode (tricolor RGB bands)? ("Get your phone in bootloader mode by doing this: Phone powered off, press Camera button + Power On, will enter into bootloader mode (RGB screen").
Once in bootloader mode you can reflash even though activesync says not connected - just look for little USB in corner of screen.
Tnx cushcalc for your reply.
I have tryed it just a minute ago. I can enter the boot loader but the flashing fails at starting with the message "This update utility cannot be used for your PDA Phone. Please get newer update utility". I have used the same flash tool as the rom image witch is now on the MDA.
Sounds more like CID locked after flashing the last ROM was flashed....cant u even flash any other wm6 ROM?
You should flash the original T. Mobile ROM from bootloader it should work. After you have the original running you can then re-flash WM6 using shelltool if your phone is CID locked. Try it and lets see how it goes.
You people are the greatest. I have tryed to flash my MDA Vario with the latest rom from t-mobile and now i have a fully functional mda again. BIG TNX for helping!!!
Hi guys! It's again me
I have problem with flashing my X1.
Downloaded R2AA Generic English ROM. Installed 3.5 .NET framework on my Vista 64bit(all updates, including .NET 3.5 SP1), everythings suppa - when phone is ON - active sync detects, sync works.
Problem appears in that 4 color mode, where I want to upgrade ROM.
4 colored stripes and text appears, but when i plug the USB cable in.... on X1 it shows "USB" text but active sync doesnt detect the device. I just can't sync my X1 with PC while in that "ROM 4-colored mode" - and in progression - cant update my ROM.
Pls help
I want to install R2AA original, generic UK ROM by that method:
1:enter boot mode on X1
2:connect cable to PC and activesync the device (WinMobDevCentre)
3:run RUU and instal ROM's .image file
Because of temporary leak of mem.card
Have you tried running the program when connected with USB in boot mode?
Program should detect your phone
Active Sync is passive process.
How can I manually sync it?
Im in boot mode - entering USB and - no sync - so no ROM update
1. Enter boot mode
2. Connect with USB (when first time windows has to install drivers, wait for completion)
3. Run RUU (the program should recognize your phone)
1:entered boot mode
2:connected USB - windows installed device named "Microsoft USB Sync"
3:RUU doesnt recongnize connected device (no activesync connection)- cannot be continued
Hmm, let's try something else
1. Leave phone on
2. Connect to pc and WinMobDevCen
3. Run RUU
RUU gives me message: The update ultility could not open requested file.
Abuk007 said:
RUU gives me message: The update ultility could not open requested file.
Click to expand...
Click to collapse
Rename the image file to ruu_signed.nbh and place it in the same folder as the RUU utility
It runs! Thanks a lot
I hope it won't damage phone
...................
It crashed damn!
stopped at 10%.... i haven't HARD-SPL, thought generic ROMS don't require it...
What now ?
Abuk007 said:
It runs! Thanks a lot
I hope it won't damage phone
Click to expand...
Click to collapse
If you wait for the RUU utility to say the flash has been succesfull it won't be damaged....
Just don't do anything with your phone/pc during flash
Glad to be helpful...
Look my upper post :/
Abuk007 said:
It runs! Thanks a lot
I hope it won't damage phone
...................
It crashed damn!
stopped at 10%.... i haven't HARD-SPL, thought generic ROMS don't require it...
What now ?
Click to expand...
Click to collapse
You're correct, generic roms have radio and spl included.
Did ruu gave an error code?
ps you do need hard-spl if you're phone was originally in another language!
It had error. But I don't remember number.
On phone it writes: upgrade ROM code error
I had Vodafone R1AA UK ROM
Just want Generic R2AA UK.
Trying to fix...
using x1 Hard SPL to install R2AA UK generic.... will post result
Im getting 262 error.. even in Hard SPL...
HELP!
............................................
FIXED!
Don't know how
tried to run Hard SPL RUU - no effect - error 262
then runned normal, Kovsky RUU with same ROM - it worked!
Abuk007 said:
Im getting 262 error.. even in Hard SPL...
HELP!
............................................
FIXED!
Don't know how
tried to run Hard SPL RUU - no effect - error 262
then runned normal, Kovsky RUU with same ROM - it worked!
Click to expand...
Click to collapse
Probably hard-spl is installed even after the error, so you're abl to flash other rom than vodafone UK.
You can check this by going into boot mode and check what it says in the upper color bar.
it writes:
KOVS110
SPL-0.72.0000
MicroP1-787
MicroP2-707
so what SPL is it? hard or soft?
Abuk007 said:
it writes:
KOVS110
SPL-0.72.0000
MicroP1-787
MicroP2-707
so what SPL is it? hard or soft?
Click to expand...
Click to collapse
soft
hard says SPL-0.72.OliNex
THX a lot Lokatho for your great help! If there were any kind of credits on forum - you would get min. 100
Hello,
I Flashed my P3600 starting from WM 5 with Trinity_Rom_NiAl_Build_23504.
It worked but not at all (pine nuts) so I decided to upgrade again.
The second one, the upgrade stopped while he was runnung and I did the recovery procedure as suggested by the upgrade.
Now when I connect in bootloader mode to pc USB connection is activated.
But every rom version i try to flash I got the Message Error[270] Update Error
Ur Image file is corrupted.
The bar % run till 1% and the device swich off immediatly.
In >Bootloader<
TRIN100
IPL-0.50
Trin100
SPL-1.06.0000
Please Help me.
Thank You
msmbrt said:
Hello,
I Flashed my P3600 starting from WM 5 with Trinity_Rom_NiAl_Build_23504.
It worked but not at all (pine nuts) so I decided to upgrade again.
The second one, the upgrade stopped while he was runnung and I did the recovery procedure as suggested by the upgrade.
Now when I connect in bootloader mode to pc USB connection is activated.
But every rom version i try to flash I got the Message Error[270] Update Error
Ur Image file is corrupted.
The bar % run till 1% and the device swich off immediatly.
In >Bootloader<
TRIN100
IPL-0.50
Trin100
SPL-1.06.0000
Please Help me.
Thank You
Click to expand...
Click to collapse
Error may appear due to corrupt image ROM. download the entire RUU and try again.
In General for archive with firmware.
I've already tried with another RUU but it works the same; really it means not to recognize the ROM installed because if I run the utility and click update to read the ROM just installed and the ROM to update, the utility recognizes only the new but not the present ROM.
The first time I ran it, the utility recognized the installed ROM too and it finished well.
msmbrt said:
I've already tried with another RUU but it works the same; really it means not to recognize the ROM installed because if I run the utility and click update to read the ROM just installed and the ROM to update, the utility recognizes only the new but not the present ROM.
The first time I ran it, the utility recognized the installed ROM too and it finished well.
Click to expand...
Click to collapse
Well.
In an active sinc disconnect connection on USB
- Download splxploit_HTC_Trinity
- Unpack and start
- Then stitch...
Should work