hi guys,
have done the Hard SpL 1.3, added radio 1.5 and tried flashing the WWE JADECore + Manila2D 1.2 PTG version successfully but however the device does not go pass the HTC screen.
i then tried to flash Mary V3.7 lite but it does not load. Requires me to do recovery. However upon recovery , it shows by hello nasty - smart mobility. Stuck right there
i flash JADECore + Manila2D 1.2 PTG again... its loading and successful, however it still reboots to hello nasty - smart mobility and stop again.
Did i miss something out? i dont understand as i assume after the Hard SPL and radio , the rest of the rom can be flashed.
i Have tried several times with this rom and mary's rom
and have soft resetted several times.
Hope for some help.
any help at all?
try official ROM first
hmm okies..
could it be that i didn't unlock the phone yet?
now its in bootloader mode.
how do i flash the unlocker or official rom in?
i still have the original wm5 disc
tried flashing the RUU_Trinity_DOPODASIA_WWE_3.00.707.18_6275_1.46.30.11_108_Ship original wm6.1 rom but it stops at 28% everytime i try.
the custom roms flash nicely and everything boots up until the first or 2nd page then it stops.
i'm on SPL 1.3olio and i guess the radio doesnt matter but its a 1.5
anyone could help? i'm offering a small token via paypal for anyone who can walk my trinity back to the light..
Although Olipro's Hard-SPL 1.30 is the newest version, many people have reported not being able to upgrade their device with this version running. For now it is recommended to use 1.20 or Des' crash-proof SPL for successful upgrades
Click to expand...
Click to collapse
Found at http://trinityguides.info
have used SPLxploit and it changed to SPL 3.03000
what do i do next? install HardSPL? Install CID unlocker?
boot from SD?
someone ? anyone?
Related
Hi, i tried all HardSPL Versions i could find, but that happens every time:
- The ROM Upgrade Utility starts,
- i check all the answer boxes, until the diamond asks if the bootloader program is ok and i push the button.
- the Bootloader starts (3-colored screen), and the progress bar at the top of the screen comes up, but shows 100% after a few seconds.
- The ROM Upgrade Utility says Upgrade is finished and the Diamond resets, but shows still original spl Version.
I Installed net 3.5 compact, does not help.
Yes i read the instructions and i propably did ROM Upgrades a dozen times in the past years, but i am still clueless. Plz help.
The Modifier said:
Hi, i tried all HardSPL Versions i could find, but that happens every time:
- The ROM Upgrade Utility starts,
- i check all the answer boxes, until the diamond asks if the bootloader program is ok and i push the button.
- the Bootloader starts (3-colored screen), and the progress bar at the top of the screen comes up, but shows 100% after a few seconds.
- The ROM Upgrade Utility says Upgrade is finished and the Diamond resets, but shows still original spl Version.
I Installed net 3.5 compact, does not help.
Yes i read the instructions and i propably did ROM Upgrades a dozen times in the past years, but i am still clueless. Plz help.
Click to expand...
Click to collapse
Is it a U.S. version Diamond?
http://forum.xda-developers.com/showthread.php?p=2963492#post2963492
Stupid me
Hi, now i tried the ROM Upgrade (not the HardSPL) and it works. Seems that the HardSPL Upgrade worked from the very beginning, but i got fooled by the T-Mobile start screen still showing 1.93 (at the bottom of the screen), and the ROM Upgrade Utility also told me that the current ROM version is 1.93.something.
... ok Upgrade finished, says 2.03.something now so something changed after all.
... Yep thats the new ROM, i made it.
But after the soft reset theres is still the T-Mobile start screen withe the magenta dots i dont get it: new ROM, but still T-Mobile Logo???
ROM Version is now 2.03.401.2 WWE , does that mean v6.4FullHDTFl.nbh is installed?
I have a major issue here. Please bear with me.
I flash my phone to the official 6.1 rom a few months back. Now I recently decided to try a custom rom by NFSFAN. So first thing was to flash the bootloader by IMCokeMan version 0.41. After doing that I flashed the custom rom. Once it booted up my phone kept reboot itself every few seconds or so. It turns out now that it was a battery issue, but I was sure the battery was fine and thought it was simply an incompatibility issue with the rom.
So I then tried to flash the official 6.1 rom back on, but it froze at 44% and then threw a 262 error after a minute or so. I then learned that I needed to flash the IMCokeMan 0.40 unlocker/relocker to get the official rom back on. So I did. Then tried the official rom again, and lone behold, froze at 44% and then gives the 262 error.
Then I thought I'd try the NFSFAN's rom again. So I flashed that. Once it successfully finished and started to load it freezes at the Telus splash screen and "No Radio" appears in red on the screen.
So this is where I'm at. I've tried to flash nearly every bootloader I could find and no matter what I do the bootloader always shows "SPL-0.41.coke". I can't flash any official rom including Telus, Bell or Sprint as they each freeze at different spots but consistently at the same spot individually (Telus at 44%, Bell at 30-some%, Sprint at 29%). I can flash custom roms as well as the beta wm6.5 rom but those don't fully load and give the "No Radio" error.
The ONLY rom I can successfully flash is an old 6.0 rom that someone dumped from a telus vogue. But in this rom under "Device Information" the rom is 1.11.661.1 and the radio version field is blank! And I cannot make data connections, as in I cannot connect to the internet, etc.
So my question to anyone that may know is: why am I having these issues with the radio version? How can I get rid of the SPL-0.41.coke bootloader?
And what can I do at this point? Any help from anyone is a thousand times over appreciated!
There's another copy of this thread at PPCGeeks.com:
http://forum.ppcgeeks.com/showthread.php?p=792095#post792095
-Chris
*********** bump-a-doo? *************
eeps! similar issue! did I brick it???
My symptoms are different, but the way I got there is pretty much the same:
I wanted to try NFSFAN's 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
cbstryker said:
I then learned that I needed to flash the IMCokeMan 0.40 unlocker/relocker to get the official rom back on. So I did. Then tried the official rom again, and lone behold, froze at 44% and then gives the 262 error.
Click to expand...
Click to collapse
I've been reading through the ImCoKeMaN's unlocker sticky (http://forum.ppcgeeks.com/showthread.php?t=20370), and I noticed there is a "VERY IMPORTANT / Warning" referring to the 0.40 rom you used. Here's what it says:
If your carrier did not release a rom and you flash an exe of another carrier with the 0.40 unlocker you won't be able to flash ANY rom until unlocking again (this requires booting into WM)
Click to expand...
Click to collapse
then it points to this: ftp://up.ppcgeeks.com/Vogue/Users/ImCoKeMaN/Vogue_unlocker.exe
Hopefully that helps you out.
esskay said:
My symptoms are different, but the way I got there is pretty much the same:
I wanted to try NFSFAN's 1.28 Bell rom, so I unlocked with IMCokeMan's 2.31 unlocker (2.31 instead of 0.41 because I had previously upgraded to UTStarcom's Bell WM6.1 rom with the 3.42.50 radio when it came out). The unlock process went smoothly, and I had no problem flashing NFSFAN's 1.28 rom after that either.
NSFAN's RUU said I was successful, and my Vogue automatically restarted but got hung up on the "Bell" splash screen, I tried to let it work itself out for over 15 minutes before I tried a reset, but it still had the same problem. Tried a hard reset: same problem. I let it sit connected to the charger for a half week now and it still is hung at the "Bell" splash screen.
I'd try to flash the stock rom again, but I can't get the RUU to work without an activesync connection (right?).
Did I brick it? Any advice would be appreciated.
Here's everything my version-screen says if it helps at all:
M 03
B 01
P DCAAXOM-4350H
R 3.42.50
D 3NFS (is that NFSFAN's rom or an error?)
Click to expand...
Click to collapse
hey, I answered this question of yours already over here http://forum.xda-developers.com/showthread.php?p=3526872#post3526872
Detroit Doug
Thats the problem im having theres no way I know to get passed that screen that says no radio. So you can't even get into WM. So since it cant load into WM you can't run the unlocker. Most custom roms flash fine but its the radio thats missing it wont go past that.
Viper Matrix Wireless said:
Thats the problem im having theres no way I know to get passed that screen that says no radio. So you can't even get into WM. So since it cant load into WM you can't run the unlocker. Most custom roms flash fine but its the radio thats missing it wont go past that.
Click to expand...
Click to collapse
You do NOT need to be in WM to unlock, WM has nothing to do with it
Start phone in bootloader mode (power+camera+stylus in reset hole and hold this until the 3 color screen comes up) it will say serial at the bottom
Plug in the USB cable to your PC and it will change to say USB
Start the 2.31 Unlocker RUU.EXE (RomUpdateUtility.exe) file, follow the steps
then run your custom ROM when after it restarts do does it thing and reboots again by going back into bootloader mode and doubleclicking the RUU.exe file in the custom ROM folder you want to use
Once it runs through the setup after flashing and then the autorun and restarts - hard reset the phone (red+green+stylus in hole) until a gray screen comes up
Follow directions and then setup and autorun and reboot
Make sure you have a carrier cab and/or mms fix either on your PC to copy over to your phone or on your SD Card ahead of time and you should be set to go
Detroit Doug
Detroit_Doug said:
You do NOT need to be in WM to unlock, WM has nothing to do with it
Start phone in bootloader mode (power+camera+stylus in reset hole and hold this until the 3 color screen comes up) it will say serial at the bottom
Plug in the USB cable to your PC and it will change to say USB
Start the 2.31 Unlocker RUU.EXE (RomUpdateUtility.exe) file, follow the steps
then run your custom ROM when after it restarts do does it thing and reboots again by going back into bootloader mode and doubleclicking the RUU.exe file in the custom ROM folder you want to use
Once it runs through the setup after flashing and then the autorun and restarts - hard reset the phone (red+green+stylus in hole) until a gray screen comes up
Follow directions and then setup and autorun and reboot
Make sure you have a carrier cab and/or mms fix either on your PC to copy over to your phone or on your SD Card ahead of time and you should be set to go
Detroit Doug
Click to expand...
Click to collapse
I answered his question on his thread. You forgot one thing though Doug. He doesn't have a radio. He'll need to flash back to stock before he flashes a custom. Doesn't this get frustrating???
hi all, my situation in this:
i ve an htc s300+ with hardspl 1.30 installed that in boot loader write "WLAN error" , when boot it is blocked to 2nd screen (HTC logo). i ve try with any solution on this forum.. with mtty not solution, with "splxploit" no solution.. i understand that the problem is when i try to flash a Rom radio it don't wont load over 7% and reboot in boot loader, or a original italian complete rom WM5 it don't wont load over 13% but not reboot.
if i flash only the ROM WM6 coocked it load full but the problem is the same.. (after reboot blocket to 2nd screen)..i ve try to flash also directly with mini SD but the loading stopped after start (about 13%)..
the situation is the same if i load with "splxploit" the hardspl 1.20, or sspl 1.05 or 1.06...
i try all solution in my mind... but no resolve this problem..
can anyone with more experience that me to help?
thanks
sorry but i am italian and my english is not good..
I think you have not complete reading all instruction before you start.
HARDSPL Olipro 1.30 is not able to flash Radio Rom as feedback by many.
You should use Olipro 1.20 or Des's SPL.
Sorry, I have the same problem,
How I can downgrade the H-SPL from 1.3 to 1.2 if the P3600 don't boot on, it is stop at startup logo HTC
Thx
Just put your device manualy in bootloader and flash again...It should work
IT don't work.
The process it is ok at 100%, but if I put the pda in bootloader I have again 1.30
Where I wrong?
Have you tried to flash from SD Card? Maybe this would work differently.
Try flashing HTC official rom
As stupid as it sound, it worked for me. it seems the official WM5 rom has some recovery features. It takes forever to flash (and obviously it does some different stuff than cooked roms) but it took my bricked trinity from its brick mode at least twice the past 3 years. If you can't get hold on one, although I am sure it is on this forum, PM me and I will upload it for you. Just too tiered to do so if you have another source to take it from.
Look for RUU_Trinity_DOPODASIA_WWE_3.00.707.18_6275_1.46.30.11_108_Ship. Be aware after it you may need to update the radio as well, but this is easy.
BigE
Please upload the file!!!!!!!!
Thx
for lazy ppl who do not search
http://rapidshare.com/files/47349234/latest_dopod_wm6_anznospl.rar.html
BigE
try this one
http://cid-8231c261cbdd4326.skydriv....751.5|_6275|_1.56.70.11|_108|_Ship.part1.rar
Hi All.
I Need your help.
I have a Diamond Runnig HardSPL 1.40 Olinex, Gen Y ROM, 1.11 Radio.
Everything was fine until my diamond enter on the three color flash screen, i instaled 3 diferent ROM and it's not booting any more. I tried everything and nothing heappened, a shut down install a new ROM and it don't boot, backing to the flash screen.
USB is working fine.
Some one can help me? URGENT!!!!!
you means you always enter to 3 color screen when you boot?
you can try to flash to official rom which sometime it can help.
or another silly suggestion, you sure your VolDown button was not stuck??
Hi
I had my S620 aside, haven't used for 3 years.
Now I'm trying to give it to a friend and i need to put a Portuguese rom on it.
I know I've change the stock rom to the 3VO.2.80.092509 and now I want to flash the official portuguese rom.
I've downloaded it (RUU_Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_02.98.90_Ship Extract) from official rom's page but when I try to flash it, it gives me the Error [244]: Invalid model ID, at 3%.
Well, the rom is for Excalibur, i flashed a rom before long time ago, do i need to update the HSPL ?
What am i doing wrong?
Thks for your help.
Regards
My Excalibur especifications:
On Bootloader
Excalibur
ONBL 1.30.0000
SPL 1.30.0000
Windows Mobile 6.5
OS: CE OS 5.2.23004 (build 23005.5.3.0)
ROM: 3VO.2.80.092509
Radio version: 4.1.13.47_02.98.90
read carefully
i overclock mine and i solve it. go to windows mobile center and disable usb connection. press and hold sym while pluging in usb( this will take you to bootloader mode) and run uspl from the cid bypass after that run the original rom. if it does work go back to stock rom and run cid bypass and ru the rom you metion.
http://forum.xda-developers.com/showthread.php?t=329605
http://forum.xda-developers.com/showthread.php?t=328690&highlight=cid
XicoBombas said:
Hi
I had my S620 aside, haven't used for 3 years.
Now I'm trying to give it to a friend and i need to put a Portuguese rom on it.
I know I've change the stock rom to the 3VO.2.80.092509 and now I want to flash the official portuguese rom.
I've downloaded it (RUU_Excalibur_BRIGHTSTAR_PTB_1.30.514.2_4.1.13.47_02.98.90_Ship Extract) from official rom's page but when I try to flash it, it gives me the Error [244]: Invalid model ID, at 3%.
Well, the rom is for Excalibur, i flashed a rom before long time ago, do i need to update the HSPL ?
What am i doing wrong?
Thks for your help.
Regards
My Excalibur especifications:
On Bootloader
Excalibur
ONBL 1.30.0000
SPL 1.30.0000
Windows Mobile 6.5
OS: CE OS 5.2.23004 (build 23005.5.3.0)
ROM: 3VO.2.80.092509
Radio version: 4.1.13.47_02.98.90
Click to expand...
Click to collapse
so weird
Ratchewer said:
i overclock mine and i solve it. go to windows mobile center and disable usb connection. press and hold sym while pluging in usb( this will take you to bootloader mode) and run uspl from the cid bypass after that run the original rom. if it does work go back to stock rom and run cid bypass and ru the rom you metion.
http://forum.xda-developers.com/showthread.php?t=329605
http://forum.xda-developers.com/showthread.php?t=328690&highlight=cid
Click to expand...
Click to collapse
Hi
I did what you've told, ran uspl from cid paypass, all good till the screen stayed almost white.
When i tried to install PTB stock rom the flasing frooze at 0%.
Had to unplug the usb cable, and now each time i turn on the pda it goes to bootloader mode everytime.
Tried to flash through sd card all the stock roms i found without success. All the attempts through usb cable didnt passed 0%.
It starts to check the sd contents but then goes straight away to 3 colour bootloader mode without doing anything.
Then i remembered i had to install the original stock rom, which was the BT brand, that i found yesterday.
Now comes the weird part.
First time i try to flash the BT brand rom, it installed the rom (i didnt quite saw the whole process), and when it restarted it self, went again to bootloader mode.
Tried hardreset, tried to flash again, it goes straight to bootloader.
What the hell is going on???????
In my whole flashing history, i had 100% success over 50 flashes, and now its freaking weird.
Can you lead me again?
Thanks for everything.
Greetings
Try this here
ok go back to the original phone stock rom from the service provider and start over. use the usb bootloader mode after run the xda applicationunlocker file and do the cid bypas. then run the utilityupdate from the other rom ( not the one in the cid bypas file in the link) meaning do not click yes to the windows security prompt skip and run the romm u want to use
XicoBombas said:
Hi
I did what you've told, ran uspl from cid paypass, all good till the screen stayed almost white.
When i tried to install PTB stock rom the flasing frooze at 0%.
Had to unplug the usb cable, and now each time i turn on the pda it goes to bootloader mode everytime.
Tried to flash through sd card all the stock roms i found without success. All the attempts through usb cable didnt passed 0%.
It starts to check the sd contents but then goes straight away to 3 colour bootloader mode without doing anything.
Then i remembered i had to install the original stock rom, which was the BT brand, that i found yesterday.
Now comes the weird part.
First time i try to flash the BT brand rom, it installed the rom (i didnt quite saw the whole process), and when it restarted it self, went again to bootloader mode.
Tried hardreset, tried to flash again, it goes straight to bootloader.
What the hell is going on???????
In my whole flashing history, i had 100% success over 50 flashes, and now its freaking weird.
Can you lead me again?
Thanks for everything.
Greetings
Click to expand...
Click to collapse