Related
Just got my Trinity today, and have successfully unlocked it using pof's unlocker. I unlocked the SIM lock and the CID lock, so it's now SuperCID.
I want to put WM6 on it, the LVSW version. I've downloaded the three files in the sticky post. Before I do it, I want to check that I'm understanding it right, because I'm a bit confused with version numbers.
So...
1) First, I need to HardSPL by running the "ROMUpdateUtility.exe" file from the Hard-SPL.zip file, yeah? I ran this (but didn't flash it) and was confused because the new "Image Version" was 1.20 whereas the Image Version shown in the "current image" bit was 1.24.xxx. Usually, going backwards is bad but I may be misunderstanding.
2) I then need to flash the Radio ROM to 1.41 - why do I need to do this? I guess I run the "ROMUpdateUtility.exe" from the GSM_xxx_xx file, right?
3) Finally, I need to flash WM6 - by running the "ROMUpdateUtility.exe" file from the WM6 zip.
Is that right?
Just tried to flash both the HardSPL and the Radio ROM, and the ROM Update Utility always craps out after I select "Yes" to the security prompt on the Trinity.
"ERROR 246 DEVICE NOT RESPONDING" is displayed in the update utility. Any ideas?
Also, if I go to the bootloader manually (holding down the buttons) the version numbers are:
TRIN100
IPL-0.50
TRIN100
SPL-1.07.0000
But when I let the ROM Update program enter the bootloader, these are shown instead:
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
What does it all mean? Very confusing! It won't let it update anyway, when I select "Yes" to the security prompt, the screen goes black, the ROM updater throws up the error 246 and then the Trinity shows the bootloader.
GazChap said:
Just tried to flash both the HardSPL and the Radio ROM, and the ROM Update Utility always craps out after I select "Yes" to the security prompt on the Trinity.
"ERROR 246 DEVICE NOT RESPONDING" is displayed in the update utility. Any ideas?
Also, if I go to the bootloader manually (holding down the buttons) the version numbers are:
TRIN100
IPL-0.50
TRIN100
SPL-1.07.0000
But when I let the ROM Update program enter the bootloader, these are shown instead:
TRIN100
IPL-SSPL by Des
TRIN100
SPL-1.07.ds
What does it all mean? Very confusing! It won't let it update anyway, when I select "Yes" to the security prompt, the screen goes black, the ROM updater throws up the error 246 and then the Trinity shows the bootloader.
Click to expand...
Click to collapse
SPL by Des is a one time only SPL called SSPL-TRIN.exe, it's somewhere on this board. Sometimes it's baked into a ROM too ... it fakes the SPL.
HARD SPL stays on your phone .... doesn't need SPL by Des anymore.
Windows needs some time to switch from Windows CE to the bootlader driver. This can cause an error ...... just start the exe file again on the PC.
Another common flash error is with Vista, then you need to overwrite the default driver when you're in the bootloader. The driver is in "VistaRUU.zip"
Relaunch the Hard-SPL, then the radio ROM and after that LVSW or mUn's ROM.
There is a file you extract called EnterBootLoader.exe
I copy this to the Memory card.
Then before I run the update I run this on the memory card.
The phone goes to the boot loader and then once windows has re-detected it I run the update.
This seems to have eliminated all problems I've ever had flash updating.
akirainblack said:
There is a file you extract called EnterBootLoader.exe
I copy this to the Memory card.
Then before I run the update I run this on the memory card.
The phone goes to the boot loader and then once windows has re-detected it I run the update.
This seems to have eliminated all problems I've ever had flash updating.
Click to expand...
Click to collapse
I just tried this, but Windows doesn't seem to want to detect the presence of the device when I do. ActiveSync reports that nothing's connected.
Well I've got the Hard-SPL and Radio ROM to flash - instead of leaving ActiveSync connected I just went into the bootloader manually and did it that way.
But now I'm trying to flash WM6 and it gets up to 8% and then craps out with Error 286 - communication errors.
The device now won't boot past the bootloader
What do I do now?
Bloody hell. It's amazing, it really is.
I had it plugged into my USB hub.
Took it out and plugged it directly into the PC, just on the off-chance that the hub was screwed up.
It's all working fine now, I think!
Typical. Thanks for the assistance anyway guys.
Nps. Glad you got it sorted
Is the USB Hub powered? If not that will cause a ton of problems!
It's supposed to be powered, but I'm starting to think that the power supply might be faulty!
hi guys,
2 questions if i can;
1)What is HardSPL?
2) Why are there 3 steps to getting WM6? why can I not use the "ROMUpdateUtility.exe" file from the WM6 zip straight away?
Thanks a lot!!
Same Problem as GazChap
Hey All,
I was having the exact same problem as GazChap with the same configuration to start out with.
This is what I did:
1)plug in my p3600 to the USB
2)let synchronize, and hopefully finish, otherwise stop it
3)run HARD-SPL; this usually freezes after the first go and stalls in the bootloader
4)run HARD-SPL again; this time it will finish. You will have to turn on your machine again after this.
5)run AX3L ROM 2.0.8.2; this ALSO usually freezes after the first go and stalls in the bootloader
6)run the ROM again; This time its gonna work...
Now it works..
brick time
I loaded the hard spl succesfully. I could not get the radio upgrade to load no matter what I did. My instructions said it was optional, so I went directly to the WM6 rom exe load and it has a perpetual communications error after about 8% even though the WM6 loader says each time that recovery is successful. I have a tricolor screen (bootloader?) on my 3600 which won't respond to anything I have thought of yet. Anything I can do other than pitch it? Help! And thanks in advance.
ok, just want to make it short: (P3600 user)
1. I have WM6.1 ROM (FleNover 3.3 Black edition) installed.
2. When I want to downgrade to WM6 official, after 20% it goes error.
3. Now, it only shows 3 colors.
4. Here is my PDA information in 3 colors:
TRIN100
IPL-1.00
TRIN100 MFG
SPL-1.30.Olipro
5. When I want to upgrade with WM6 official, after my PDA shows the progress bar, it restarted and the update screen shows Error 286.
6. How do I fix it?
thank you very much
Hello everyone,
I would really appreciate some help as i have got my x1 stuck in the bootloader...
this happened because i tried to hardspl my phone with the microsd method, and it is now stuck in a continuous loop of updating through the bootloader ...
i know this was a retarded thing to do but i recently built a custom pc which i spent over my budget on, so could not afford a legitimate copy of a windows OS, so i am temporarily using a pirate copy....
because i am using the pirate windows OS i cannot download Windows Mobile Device Centre and therefore cannot activesync my x1, and cannot hardspl or flash my x1 by usb cable...
so i thought modifying the "flash with microsd card" method to "hardspl with microsd card" could work, so i extracted the ruu_signed.nbh from the hardspl file, and changed the file name to Kovsimg.nbh, then copied it to the root of the x1's sd card, entered the bootloader, and accepted to update the image with the kovsimg.nbh file, the update progress bar reaches 100% then the phone reboots back to the bootloader and the image updates, tehn rerboots, this happens continuously...
thanks for any help in advance
btw i have tried hardreseting and softreseting, removing the battery, removing the sd card
HardSPL is the only thing we can't flash with microSD method!
Try to flash stock rom with microSD method and maybe your X1 will work again
If it works, do not try anymore to flash your SPL with microSD method
flext said:
btw i have tried hardreseting and softreseting, removing the battery, removing the sd card
Click to expand...
Click to collapse
try mitty..seach the hardspl thread
thanks for your advice, but i have succesful flashed a custom rom, by changing the .nbh file (hardspl) to the .nbh file (custom rom) then flashed through the bootloader
Hello everyone,
This is the last time I try to do something to bring back vitality to my G1.
I have a T-Mobile G1 (DREA100 PVT, Radio: 1.22.12.29) I can boot into bootloader mode and recovery mode. I have no root.
I tried to downgrade the device with the RC29 and RC30, but always without success. When the downgrade end, instead of OK signal to each component, returns the heading "Installation Fail."
Before creating the GoldCard which with DREADIAG.nbh helped me to start it in recovery mode, the phone started only in bootloader mode.
Now I can do a full analysis of the phone with the DREADIAG, but not found anything abnormal.
If I turn on the phone without pressing extra keys, is on the word "T-Mobile G1".
Please if you have any alternative idea to "try a downgrade RC29" do your thing, I'm using it damn phone.
Thank you everyone.
P.S.: Sorry for my Eng.
I had a hard time understanding exactly what you're trying to say, but i'll give it my best shot.
If you're able to access the bootloader, then you're not bricked. If you have the default, original, stock bootloader (spl) you shouldn't have a problem downgrading using the dreaimg.nbh rc29 file. (if you do, then i have no idea...) If you have any other spl, hard/danger-death, then you should be able to get into fastboot and flash a rooted recovery image (cyan 1.4, amon_ra 1.5.2) - there are guides within the forums describing how to do this.
Once you have a modified recovery image and an spl that will enable you to flash custom rom's , just flash as normal
I have original SPL and have a problem to downgrade using DREAIMG.nbh (RC29) file. Every time (with many many different downloaded files) INSTALLATION FAIL.
I can't use fastboot because my phone isn't recognized by adb.
Help...
_tony_ said:
I can't use fastboot because my phone isn't recognized by adb.
Click to expand...
Click to collapse
Last time I checked, adb won't work unless the phone's OS is on. However, fastboot will work when in bootloader mode without adb. Just turn the phone off, hold camera and turn it on. Plug your USB cable in then hit the back key, it should read "FASTBOOT USB". You're in.
Try re-downloading the DREAIMG.NBH, maybe yours got corrupted.
jayshah said:
Last time I checked, adb won't work unless the phone's OS is on. However, fastboot will work when in bootloader mode without adb. Just turn the phone off, hold camera and turn it on. Plug your USB cable in then hit the back key, it should read "FASTBOOT USB". You're in.
Click to expand...
Click to collapse
No man, when I'm in Bootloader mode and plug-in the USB cable, the phone say me "Serial 0".
_tony_ said:
No man, when I'm in Bootloader mode and plug-in the USB cable, the phone say me "Serial 0".
Click to expand...
Click to collapse
If it says Serial 0, it's telling you that something is wrong with your SDCARD.
Format the card again and choose the FAT32 file system.
I have a sd card that would not work properly...found it out the hard way with similar issues to yours! It worked fine in the phone for storage, but not for loading roms or updates. Went to another card after thinking my phone was screwed up and it worked fine.
But I tried to flash the ROM with 3 different SDCard, the last is now a GoldCard (without which I could not use the dreadiag.nbh) and also one of those 3 has already root dream of a friend ...
P.s.: On my Dream has never been turned on "debug usb"
Are you sure the SDCARD is formatted to FAT32? Also, when you used the other Cards, did it also say Serial 0?
Bavilo said:
Are you sure the SDCARD is formatted to FAT32? Also, when you used the other Cards, did it also say Serial 0?
Click to expand...
Click to collapse
Yes, I'm sure! I've tried many times the procedure
- FORMAT in FAT32
- DOWNLOAD RC29
- EXTRACT DREAIMG.nbh in / (of sdcard)
- INSTALL
but everytime this fail.
Yes, with any sdcard the phone say me "Serial 0"
Re-format your card. Format it for FAT32. Change the allocation unit size to 4096 bytes. That should help. Let us know.
_tony_ said:
Yes, I'm sure! I've tried many times the procedure
- FORMAT in FAT32
- DOWNLOAD RC29
- EXTRACT DREAIMG.nbh in / (of sdcard)
- INSTALL
but everytime this fail.
Yes, with any sdcard the phone say me "Serial 0"
Click to expand...
Click to collapse
Yes, I'm sure! I've tried many times the procedure
Right way of writing it:
Yes i'm sure! I've tried the procedure many times.
but everytime this fail.
right way of writing it:
but it fails everytime.
...sorry OCD -.-
Ty Macrophage001 for your lesson...but this is a English or Phone/PDA forum???
I'm Italian and my English is not good, it's a problem for you? Others have understood what I meant...so if you don't understand is not a problem, but ridicule me is really stupid. -_-'
Thank you again...
Hi all!
first of all sorry for my Egnlish
I tried to perform task29 on my HD and get an error "Invalid vender ID", in some guides i read that in this case I should use a stock .nbh files... I tried the .hbn file from HSPL thread from one of restore_stock_spl* zip files. task29 was performed normally. When I turn on device I can see the clear smart mobility screen only with "smart mobility" words in center. bootloader now showing me 1.54 Olinex version. Before task29 this version was 1.56.
And from this moment I can't do anything with device: I can't flash any rom or radio. When using RUU after three-colour screen device shows me a progres indicator which suspends on 0% and RUU progress is also 0%. after waiting some time RUU shows an "262 Update erorr". When I'm trying to flash ROM or radio from SD card I see the three-colour screen then grey screen "loading... No image file!!!" and then again the three-colour screen. It shows so fast that it looks like a screen blinking and almost impossible to read what is written on grey screen.
I have spend 3 days while looking for different files and flash packages, have read a guides and I'm at a loss.
Please helpme to make my HD work again!
sergey.ss said:
Hi all!
first of all sorry for my Egnlish
I tried to perform task29 on my HD and get an error "Invalid vender ID", in some guides i read that in this case I should use a stock .nbh files... I tried the .hbn file from HSPL thread from one of restore_stock_spl* zip files. task29 was performed normally. When I turn on device I can see the clear smart mobility screen only with "smart mobility" words in center. bootloader now showing me 1.54 Olinex version. Before task29 this version was 1.56.
And from this moment I can't do anything with device: I can't flash any rom or radio. When using RUU after three-colour screen device shows me a progres indicator which suspends on 0% and RUU progress is also 0%. after waiting some time RUU shows an "262 Update erorr". When I'm trying to flash ROM or radio from SD card I see the three-colour screen then grey screen "loading... No image file!!!" and then again the three-colour screen. It shows so fast that it looks like a screen blinking and almost impossible to read what is written on grey screen.
I have spend 3 days while looking for different files and flash packages, have read a guides and I'm at a loss.
Please helpme to make my HD work again!
Click to expand...
Click to collapse
Have you tried flashing stock rom which came with your device?
I have tried .nbh file from "HTC Stock ROM_BLACKSTONE_1.14.401.3 (22273) WWE.zip"
if it possible tell me what exactly should I download and how to use it, I'll try. I'll try everything you advise, because I didn't find solution myself and don't know what esle should I try. first of all where should I start? do I need to perform task29 correctly or do I need to restore HSPL to 1.56 version, or flash a stock rom?
* Dont connect your phone to your computer.
* Hold down the Volume down button and hit the power button.
* Your entering the tricolor boot screen and at the bottom the word "Serial".
* Now connect you phone to your computer with te USB cable the word serial disappear and now it says USB.
* Now you can normally flash/update your phone and please use hspl.
I had before a HTC Diamond. On that device I used to run "task29" until that command killed my device. Almost same as you, I could flash the device but I couldn't boot normally. My ROM memory probably got damaged for good so I had to replace the device with a new one. My suggestion to you: on a new device never use that command again and you will be fine.
iamjohno said:
* Dont connect your phone to your computer.
* Hold down the Volume down button and hit the power button.
* Your entering the tricolor boot screen and at the bottom the word "Serial".
* Now connect you phone to your computer with te USB cable the word serial disappear and now it says USB.
* Now you can normally flash/update your phone and please use hspl.
Click to expand...
Click to collapse
I tried this way. Progress is suspends on 0% and then I get an error "262 Update Error" in RUU What should I do first: change HSPL version or flash ROM/radio?
xdmcdmc said:
I had before a HTC Diamond. On that device I used to run "task29" until that command killed my device. Almost same as you, I could flash the device but I couldn't boot normally. My ROM memory probably got damaged for good so I had to replace the device with a new one. My suggestion to you: on a new device never use that command again and you will be fine.
Click to expand...
Click to collapse
it's terrible, hope my devise still alive...
There is one detail I didn't mentioned... If download task29 package and just simply execute task29.exe (using .nbh from this package) progress on device goes forward to 4% and then "Invalid vender ID" error occurs... So I think I should use another .nbh file but which one?. Hope this checking of vender ID is not that 4% of progress and some actions with device memory really starts...
sergey.ss said:
I tried this way. Progress is suspends on 0% and then I get an error "262 Update Error" in RUU What should I do first: change HSPL version or flash ROM/radio?
it's terrible, hope my devise still alive...
There is one detail I didn't mentioned... If download task29 package and just simply execute task29.exe (using .nbh from this package) progress on device goes forward to 4% and then "Invalid vender ID" error occurs... So I think I should use another .nbh file but which one?. Hope this checking of vender ID is not that 4% of progress and some actions with device memory really starts...
Click to expand...
Click to collapse
Try using a radio nbh for blackstone.
The original package, contains nbh for the LEO
thanks all of you for replay but I still need a help very much.
there are ways that I have tried
1. flashing rom/radio from SD card
2. flashing rom/radio using RUU
3. task29 using different .nbh files
4. install/restore HSPL
In the first way always hapens same thig: I turn off the device, turn it on, press volume down button, see tricolor bootloader screen, then for a very short time (less than second) i see a grey screen and there is written: "loading... No image file!!!", then i see tricolor bootloader again.
I tried different rom/radio files (it was "HTC Stock ROM_BLACKSTONE_1.14.401.3 (22273) WWE" and other roms I flashed before and different versions of radio files from thread int this forum).
for the RUU using ways I always get two situations: I turn off the device, turn it on, press volume down button, see tricolor bootloader screen, connect the devise to PC, execute RUU/taks29/HSPL/Restore_SPL, then press next a few times, then i see the progress in RUU and on device screen and there is two endings:
1. progress goes up to 4% and devise making a soft reset, load the black smart mobility screen with no orange version characters on screen bottom, RUU shows "Invalid vender ID";
2. progress suspends on 0% and after some timeout RUU shows "Error [262] Update error" and now changes on device screen.
last what I have tried: execute task29 with last hd radio 1.17.25.09 file and got invalid vendor id error, then execute task29 with radio 1.09.25.14 file and got update error.
my be this holds some information: in my bootloader is written following
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
what should I do?
sergey.ss said:
thanks all of you for replay but I still need a help very much.
there are ways that I have tried
1. flashing rom/radio from SD card
2. flashing rom/radio using RUU
3. task29 using different .nbh files
4. install/restore HSPL
In the first way always hapens same thig: I turn off the device, turn it on, press volume down button, see tricolor bootloader screen, then for a very short time (less than second) i see a grey screen and there is written: "loading... No image file!!!", then i see tricolor bootloader again.
I tried different rom/radio files (it was "HTC Stock ROM_BLACKSTONE_1.14.401.3 (22273) WWE" and other roms I flashed before and different versions of radio files from thread int this forum).
for the RUU using ways I always get two situations: I turn off the device, turn it on, press volume down button, see tricolor bootloader screen, connect the devise to PC, execute RUU/taks29/HSPL/Restore_SPL, then press next a few times, then i see the progress in RUU and on device screen and there is two endings:
1. progress goes up to 4% and devise making a soft reset, load the black smart mobility screen with no orange version characters on screen bottom, RUU shows "Invalid vender ID";
2. progress suspends on 0% and after some timeout RUU shows "Error [262] Update error" and now changes on device screen.
last what I have tried: execute task29 with last hd radio 1.17.25.09 file and got invalid vendor id error, then execute task29 with radio 1.09.25.14 file and got update error.
my be this holds some information: in my bootloader is written following
BLAC100 32M
SPL-1.54.0000
MicroP-BlackStone (LED) v6
what should I do?
Click to expand...
Click to collapse
Hmmm... I want to know, what .nbh file did you include in the task29 folder you have? Remember, you must to copy a radio ROM to your task29 folder and name it as RUU_signed.nbh, don't copy an OS ROM to task29 as this will give problem.
From the information above, seems you had restore to original SPL? Try flash HSPL or USPL. If you have any problem flashing, you can ask in this thread http://forum.xda-developers.com/showthread.php?t=505377
Good luck, my friend. Cheers.
Agree with philrom: you are an the stock SPL. So, flash HSPL, then you should be fine.
Has this been resolved?
Fallen Spartan said:
Has this been resolved?
Click to expand...
Click to collapse
Yes. Sorry I forgot to post the ending of this story...
I didn't understood about flashing HSPL in formated device... I was really tired of using different ways and flashing different roms... I just took my device to a not official service center (there is no Touch HD for my country). There guys said me that I need to flash a stock rom of my HD birthplace country. They found out that it was shipped from Arab Emirates, than they found a required ROM and flash it. It cost me 50$. Now I'm using my HD as usual.
Thank for the replays!!!
Glad you got it resolved
Thread closed
I am having Xperia X1 Black with factory installed Win Mo 6.1....so, now i wanted to try the Windows Mobile 6.5.3-Build- 29007. Can anyone help me with detailed procedure of installing new ROM on my X1.
I tried according to the procedure available in various post's. According to the procedure i need to first Hard SPL my phone. So, when i try doing that my progrees bar on the phone screen gets stuck at 0% and then i get a error that check the connection of the pc and phone.
In bootloader mode the configuration shown is as follows
KOVS110
SPL-0.78.0000
Micro P1-787
Micro P2-707
I even tried the direct SD card method in which i renamed the ROM file i.e RUU_signed.nbh to kovsimg.nbh...in this when i go to the bootloader mode, the tricolour screen shows with above mentioned specifications then after about few seconds another screen is displayed saying" LOADING..." and then gets stuck.
So, anybody can please help me with installing new ROM
Regards
Bhavik
guitarguru31 said:
I am having Xperia X1 Black with factory installed Win Mo 6.1....so, now i wanted to try the Windows Mobile 6.5.3-Build- 29007. Can anyone help me with detailed procedure of installing new ROM on my X1.
I tried according to the procedure available in various post's. According to the procedure i need to first Hard SPL my phone. So, when i try doing that my progrees bar on the phone screen gets stuck at 0% and then i get a error that check the connection of the pc and phone.
In bootloader mode the configuration shown is as follows
KOVS110
SPL-0.78.0000
Micro P1-787
Micro P2-707
I even tried the direct SD card method in which i renamed the ROM file i.e RUU_signed.nbh to kovsimg.nbh...in this when i go to the bootloader mode, the tricolour screen shows with above mentioned specifications then after about few seconds another screen is displayed saying" LOADING..." and then gets stuck.
So, anybody can please help me with installing new ROM
Regards
Bhavik
Click to expand...
Click to collapse
You bootloader should show
Kovs110
SPL-0.78.OliNex
MicroP1-787
MicroP2-707
don't know if .0000 and OliNex is different
http://forum.xda-developers.com/showthread.php?t=431218
look here for download the good Hard SPL and then replace the 0.78 in it, HARD SPL with cable / computer (I never use SD CARD because it never works for me)
then you TASK29 (find it in the forum), then you can flash it =)