hi,
sorry if this is been posted before. i couldn't find one that worked.
my htc trophy is sort of bricked (i accidently took the USB out when updating) it wont get past htc logo, but i can go into USB host mode but PC dosent pick it up, i can go to reset page but it resets but still wont go past htc logo.
i tried downloading a ROM i saw on a thread but it said it didnt pick up the htc trophy.
If your region is one of those listed in the thread, and you can get to the SPL (tri-colour) screen by holding Vol-down when powering on, then try flashing one of the stock ROMs from this thread in the Trophy forum.
http://forum.xda-developers.com/showthread.php?t=924333
I "accidentally" ended up with a 4.6 SPL, no WinPhone 7, and this got me out of trouble!
You'll then be able to re-connect to Zune, and apply all the updates that are available to you.
Alternatively, before updating to Mango, once you've got that far, and since that will put you on a 1.x SPL, you could install RSPL/HSPL then flash any Trophy ROM out there (including the DFT or XBMod Trophy ROMs)...
-PJC
pjc007 said:
If your region is one of those listed in the thread, and you can get to the SPL (tri-colour) screen by holding Vol-down when powering on, then try flashing one of the stock ROMs from this thread in the Trophy forum.
http://forum.xda-developers.com/showthread.php?t=924333
I "accidentally" ended up with a 4.6 SPL, no WinPhone 7, and this got me out of trouble!
You'll then be able to re-connect to Zune, and apply all the updates that are available to you.
Alternatively, before updating to Mango, once you've got that far, and since that will put you on a 1.x SPL, you could install RSPL/HSPL then flash any Trophy ROM out there (including the DFT or XBMod Trophy ROMs)...
-PJC
Click to expand...
Click to collapse
after I download it. how do I install it? the pc dosent reconginse the phone
does any one know how to install a Rom to my phone? but it dosen't connect to pc propably.
can I install a rom or whatever without connecting to zune? because it won't connect to zune
pjc007 said:
If your region is one of those listed in the thread, and you can get to the SPL (tri-colour) screen by holding Vol-down when powering on, then try flashing one of the stock ROMs from this thread in the Trophy forum.
http://forum.xda-developers.com/showthread.php?t=924333
I "accidentally" ended up with a 4.6 SPL, no WinPhone 7, and this got me out of trouble!
You'll then be able to re-connect to Zune, and apply all the updates that are available to you.
Alternatively, before updating to Mango, once you've got that far, and since that will put you on a 1.x SPL, you could install RSPL/HSPL then flash any Trophy ROM out there (including the DFT or XBMod Trophy ROMs)...
-PJC
Click to expand...
Click to collapse
i did the vol down and power and then connected it the pc and the pc installed a driver and a program but the program says not connnect to phone???
galbul said:
i did the vol down and power and then connected it the pc and the pc installed a driver and a program but the program says not connnect to phone???
Click to expand...
Click to collapse
When you power on with vol down, you should get the 'tricolour' screen - at the bottom it should initially say 'Serial'.
When you connect it to the PC, it should say 'USB' and the PC should recognise it and install a driver (which seems to have happened).
Running the RUU as extracted from the Zip file from the Trophy thread should then connect to the phone and allow you to install the stock ROM.
While there's probably not much that can be done if that isn't the case, out of curiosity, what SPL version are you seeing on the tricolour screen?
-PJC
Related
As I have read through the threads in this forum, I am not the only one with this problem, but for some reason none of the solutions make sense to me.
Earlier today, I was trying to use the "Prophet AKU2.3 pdamobiz customized rom released [G3 Only]" to downgrade and didn't notice that my XDA NEO is 4G (the tool is for 3G only). Now after each boot the screen is stuck with the Boot Page showing:
IPL 2.15.0001
SPL 2.15.0001
GSM 02.19.21
OS 1.0.13.21
I am so pissed at myself and so frustrated.
I have tried hard-resetting and the problem still persists. I am able to get into the Bootloader by holding the camera button and pushing soft-reset. I am just not sure where to go from here. I connected the phone per usb to the computer. The phone indicates that it's connected to USB. Every ROM upgrade file I have tried gives me an update error, since they are all expecting the phone to be connected to the computer through ActiveSync.
I bought this phone in Germany and currently live in the US, so it will be tough to send it back for repairs. Plus, I don't even know if I have the original receipt anymore.
Any help would be greatly appreciated.
pengo said:
As I have read through the threads in this forum, I am not the only one with this problem, but for some reason none of the solutions make sense to me.
Earlier today, I was trying to use the "Prophet AKU2.3 pdamobiz customized rom released [G3 Only]" to downgrade and didn't notice that my XDA NEO is 4G (the tool is for 3G only). Now after each boot the screen is stuck with the Boot Page showing:
IPL 2.15.0001
SPL 2.15.0001
GSM 02.19.21
OS 1.0.13.21
I am so pissed at myself and so frustrated.
I have tried hard-resetting and the problem still persists. I am able to get into the Bootloader by holding the camera button and pushing soft-reset. I am just not sure where to go from here. I connected the phone per usb to the computer. The phone indicates that it's connected to USB. Every ROM upgrade file I have tried gives me an update error, since they are all expecting the phone to be connected to the computer through ActiveSync.
I bought this phone in Germany and currently live in the US, so it will be tough to send it back for repairs. Plus, I don't even know if I have the original receipt anymore.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Extract the rom file you are using to flash your phone, to a folder on your pc, than Extract the file i attached ("ROMUpdateUtility-NoVendorID.zip") into this folder. than connect your phone to pc and double click on "ROMUpdateUtility-NoVendorID.exe".
cross your fingers.
reboot the computer first
I guess the trick was to reboot the computer first. After the reboot, I was able to use the provided No_Vendor_ID Updater to reflash again. Now it's all set. Thank you very much for the advice.
pengo said:
I guess the trick was to reboot the computer first. After the reboot, I was able to use the provided No_Vendor_ID Updater to reflash again. Now it's all set. Thank you very much for the advice.
Click to expand...
Click to collapse
cool, any time.
1st off I DID use the search button.... 2nd HELPPP ME!!!
Waaah :'( I have a most intriguing problem I was running pdaviet 4.0.0.6 Touch for almost 2 weeks now without a single glitch.. the phone fell on my carpet and went to bootloader screen and eversince then it has never recovered I tried a hard reset it didn't work when I was pressing the send button it did nothing I did some forum searches and tried putting back the nvid RUU and it said that the update was succesfull and the progress bar on the phone moved accordingly but it went back to the bootloader screen ... then I tried pdaviet temp rom that was in the package still no go I can tell it works somehow because the USB lights up in the bottom left when I plug the usb cable and the progress bar that moves, but I'm getting desperate IPL and SPL info is in my sig...
same same... but i dropped mine before flashing the new PDAVIET touch rom.. still went fine..
now, it still flashes... RUU says its successful.. but PDA just reboots back to bootloader..
i can charge my phone fine in bootloader.. i can see the USB come on when i connect it to my computer.. other than that, can't do anything...
i've tried everything the past 2 days.. looks like i'll have to send it back to dopod.. will let u guys know what happens... probably something got damaged..
struck at bootloader
I tried WM6 (4.0.0.6 touch) from WM5 AKU 2.2 but it failed in between with some write message,which was bit strange as I didn't touch any key on laptop during that time and no program was being run at that time. (I am using VISTA Home premium). I got my phone into bootloader but it does not connect to my laptop...so cant upgrade back to AKU 2.2. In Windows Mobile Device Center, I cant see my device connected. So is it particular to Vista or my phone got bricked?
I am yet to try on Windows XP, which I have to arrange.
Please advise.
i had the sam problem.i installed this : try to install the 2.20 nvid rom
just go into bootloader mode-you dont need active sync connection and start the upgrade-search for 2.20 nvid rom download it and recover your device
charliess said:
i had the sam problem.i installed this : try to install the 2.20 nvid rom
just go into bootloader mode-you dont need active sync connection and start the upgrade-search for 2.20 nvid rom download it and recover your device
Click to expand...
Click to collapse
I tried the same but when I run ROMUpdateUtility_No_VenderID, I get a message 'Update Error, 260' which tells further that PDA is not connected to laptop., although it is very much connected. However LED on PDA does not blink as well.
When I plug in this phone to Wall adaptor, LED does show up.
'USB' appears at Bottom Left corner of PDA when connected to laptop and certainly its getting recognised by Vista as it starts installing Driver as soon as this is connected to laptop.
Please suggest.
I am stuck in the same situation, although I have a G3, running 2.20 on IPL & SPL
Working now
I tried on XP (I was trying on vista before)..I had to install Active Sync as it was not installed on that PC, then run RUU update for AKU 2.2 and update was successfull. Now will try Touch 4.0.0.6 again but this time on XP.
Hope this time I wont have any problems.
I have an ex-Vodafone, sim unlocked HTC touch diamond and it won't turn on. All I can do is bring it into the tri-colour screen/bootloader. When plugged into my computer the phone screen goes from serial to usb, but thats as far as it gets. Communication with activesync is no longer possible. I have no idea what to try now, I've gone as far as my non-technical mind will go ! help
I'm in the UK. Phone info;
Duttys V2.7 RC2 WWE - 27/10/08
Radio 1.08.25.08
P3700
Bootloader screen reads;
DIAM 100 MFG 64M
SPL 1.40 Olinex
MicroP- Diam (LED) v11
PSOC - Diam STAGE_PVT v0x30
Welcome to forums
Please have a deep read here:
http://wiki.xda-developers.com/index.php?pagename=HTC_Diamond
You´ll find all needed to do a succesfull reflash.
Good luck,
no comms with activesync
thanks for the link. have read the info on flashing my device but my phone no longer communicates with activesync. Is it bricked ? Phone won't go beyond initial 'vodafone' startup screen. i don't know what to do now.
which os in computer do you use ??? if in tri-color boot loader, pc only recognized the HTC driver device, but Activesync won't show the connect. You understand what i mean? Go Flash yourself your device with successfully, I will pretty sure that your device doesn't brick.
yes correct you can run the RUU wrapper while the phone is in the boot loader and itll still flash the rom
i use windows xp home sp2, i don't understand the flash process and can't get further than the tri-colour screen. I think i need a very simple step by step walkthrough if I'm to get any further !
ok
down load the rom of your choice and exract it
in the folder there should be a file called ruu_signed.nbh and a exe file called RUU wrapper or something like that if it doesnt come with the RUU wrapper it should be able to be downloaded from a stickied thread at the top of the diamond rom forum
then u need to connect ur phone to the pc while its in the boot screen the click on the ruu wrapper in the file on the pc and it should install on ur phone
hi, i downloaded the ruu, then connect my phone in boot screen, start the install, it asks me to make an activesync connection. activesync no longer finds my phone so no connection is made. i got this close, what now ? thanks for the help !
Done it finally
after many dime bar moments and weeks of annoyance the touch diamond finally came back to life. expecting this phone to actually work as advertised turned out to be a bridge too far. cheers for the help.
Attached you find all you need to flash cooked ROMs on your Dash3G (Maple).
The sspl/hardspl are confirmed to work fine on the HTC Maple platform (Dash3G, SNAP S520, SNAP S521). Any phone that says MAPL1XX under the battery should work just fine with the sspl and hardspl. This has been tested by oOkBa yesterday night. His cooked roms flash extremely fast and he noticed no problems except for the splash screens. Apparently HTC changed the format slightly. Should be easy to tackle and has nothing to do with the sspl/hardspl.
Now for the bad news ... It will not work on the HTC Cedar platform (GSM/CDMA, HTC Ozone XV6175, Verizon). Running the sspl on an Ozone will definitely brick it. Also the HTC Willow platform (SNAP S511, Sprint) is not supported. Please see this post for more info and how you can help.
There are 2 packages both contain a SSPL, HardSPL, patched ROM updater and the original Maple SPL. The first package is based on SPL 1.17 (tested by oOkBa) and the second is based on SPL 1.19 (tested by Gawain1986)
Instructions:
1. remove SD and SIM cards (don't forget otherwise the sspl is likely not to work!!)
2. connect your device to your pc with a USB cable and wait until it is synced
3. extract the file "Dash3G HardSPL by JockyW.zip" and execute "auto.bat"
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "1.17.hard")
5. if you have difficulties to install 1.17 then try 1.19
6. to test the sspl and the hardspl you can flash the attached splash.nbh
Once the HardSPL is installed on your device you can flash any Maple cooked or original ROM.
Have fun,
JockyW
Excellent work!! JockyW is the man! Please donate to a great cause! This now opens the door to amazing possibilities! Thank you thank you!!
ookba said:
Excellent work!! JockyW is the man! Please donate to a great cause! This now opens the door to amazing possibilities! Thank you thank you!!
Click to expand...
Click to collapse
couldnt of said it better myself..
oo..
my Snap 526 is MAPL110..
should i gib it a shot?
but i need a plan b in case something goes wrong.. any idea how to hard reset the snap with the scrollball?
I have the same mapple, ithink it's ok.
before running this file, do we have to dump the rom? and do we have to use the spl backup kit berfore?
(sorry for all these questions)
First of all, there's really no need to run this yet until there are custom ROMS to flash. If you want to simply test or prep, go for it. I can confirm it works in a MAPL100 so I don't see why any other device with MAPL1XX should be an issue. I will build some factory ROMS as well as some custom cooks in the next days for you guys to play with and test.
see i dont think alot of the new people understand the process.
the spl does nothing more than ENABLE ur device for a rom, thats it!
nothing fantastic, its not a completely diff o.s. on ur device..just preps it for whats to come.
what happend with my device today was a fluke!
i was testing and working at the same time..i could have missed a step, one of my work programs on my laptop could have set something off..i dunno.
Bricking usually isnt a part of getting a SPL for a device..just ALOT of testing. SO now is the another part of the process..the waiting process. Waiting for a rom cooker to successfully establish something, test it, and release it.
in this game..u need patience.
So I;ve been trying this and it seems something is going wrong...
Ik run auto.bat, JumpSPL gets copied and started, the device screen goes black, and when I reconnect the USB cable to get the "Smartphone Sync" driver working, my Windows 7 install tells me that there is something wrong with the USB device.
It will then refuse to use any driver I try to add to the device.
Any thoughts?
PS. It's a SNAP S521 (MAPL110)
EDIT: Windows XP x64 has the same problem.
Gawain1986 said:
Ik run auto.bat, JumpSPL gets copied and started, the device screen goes black, and when I reconnect the USB cable to get the "Smartphone Sync" driver working, my Windows 7 install tells me that there is something wrong with the USB device.
Click to expand...
Click to collapse
First, this has not yet been tested on Win7. Second, it should not be necessary to unplug and replug the cable. Try again and just wait a minute or so to allow Win7 to install the driver. Other thing you can do to make sure the driver is already installed is to put the phone in bootloader mode and connect it by usb cable.
ps: it is normal the display turns dark after running the sspl
ok, i understand there are 3 steps. but I would like to know how to do the first one:
dumping my rom.
First I entered the bootload by holding the volume down button and turning the device on...
It said:
Code:
MAPL110
SPL-1.19.0000
MicroP-Maple (LED) v6
ENGID 0x2
PCBID 0x80
PanelInfo 15-0x2
I connected it to the computer and it recognised the Qualcomm phone immediately and settled on the HTC USB Sync driver.
Then I restarted the phone and connected it again, ran auto.bat... it ran SSPL again and I waited.
So after I tried waiting for 5 minutes, WIndows 7 did not see a new device, it stayed with it's normal RNDIS driver.
So I took the plunge and ran the RUU, which told me it could not connect to the phone.
I unplugged the phone and replugged it and it said there was an error regarding the USB device.
Can it be that because my SPL version is higher than the HardSPL or SSPL, that it's getting into conflict with itself?
Hi,
First thanx for your hard working.
I got some trouble when trying to install the Hard SPL.
My SNAP from france, S521 Mapl100 under the Battery; Just HTC no operator
I launched the auto.bat
The device display turned dark and tri-color bootloader screen said "1.19.hard
The flashing process start and stuck at 0%
Unplugged the USB and the phone restart well.
Is this Hard SPL
Enter bootloader. If you see "1.17.Hard" the HardSPL is succesfully installed and you can flash any cooked and official roms in the near future.
Fabtwone said:
Hi,
First thanx for your hard working.
I got some trouble when trying to install the Hard SPL.
My SNAP from france, S521 Mapl100 under the Battery; Just HTC no operator
I launched the auto.bat
The device display turned dark and tri-color bootloader screen said "1.19.hard
The flashing process start and stuck at 0%
Unplugged the USB and the phone restart well.
Is this Hard SPL
Click to expand...
Click to collapse
Gawain1986 said:
Can it be that because my SPL version is higher than the HardSPL or SSPL, that it's getting into conflict with itself?
Click to expand...
Click to collapse
Please first try it on WinXP before we draw wrong conclusions.
Good work jocky - nice to see you about again
Thread Stuck.
Dave
jockyw2001 said:
Please first try it on WinXP before we draw wrong conclusions.
Click to expand...
Click to collapse
Did that immediately after I posted... it just keeps telling me the USB device is "malfunctioning" somehow...
Gawain1986 said:
Did that immediately after I posted... it just keeps telling me the USB device is "malfunctioning" somehow...
Click to expand...
Click to collapse
Ok, if there are similar problems i can try to build a sspl based on 1.19
Please dump it and attach (see first post for the link to the dump kit)
To anyone who has problems, please look up your current SPL version.
(press volume down and power on).
Is there anyone who succesfully flashed the HardSPL where the old SPL version was 1.18.00 or higher?
jockyw2001 said:
Ok, if there are similar problems i can try to build a sspl based on 1.19
Please dump it and attach (see first post for the link to the dump kit)
Click to expand...
Click to collapse
Here you go...
http://www.mediafire.com/?sharekey=cb564520d236e90090a82c7bb0fad7ade04e75f6e8ebb871
Gawain1986 said:
Here you go...
http://www.mediafire.com/?sharekey=cb564520d236e90090a82c7bb0fad7ade04e75f6e8ebb871
Click to expand...
Click to collapse
Try the attached sspl which is based on your v1.19 SPL.
Run sspl.bat (preferrably in XP)
I'm sorry, but the new 1.19 SSPL is not working either. The phone stays in the black screen and both Windows XP x64 and Windows 7 x86 keep telling me the USB device is malfunctioning.
I have had some experience with unlocking my previous Tornado, VOX, Kaiser and X1 and I'm pretty sure I need to see a tri-color scren when invoking JumpSPL.
So maybe that's the problem?
I would like to change my rom to another, but i have a problem.
I cant connect anymore the blackstone to the pc with the windows mobile device center ( i have windows 7). In device manager is not show the mobile device connected. i dont know what can i do to fix it.
So, i tried to upgrade the rom with the microsd, i copied blacimg.nbh and restarted the device by hold volume and power button, but it not flash.
I think becouse i have SPL
how can i change the spl without connect the blackstone to the pc?
thanx
claudioz said:
I would like to change my rom to another, but i have a problem.
I cant connect anymore the blackstone to the pc with the windows mobile device center ( i have windows 7). In device manager is not show the mobile device connected. i dont know what can i do to fix it.
So, i tried to upgrade the rom with the microsd, i copied blacimg.nbh and restarted the device by hold volume and power button, but it not flash.
I think becouse i have SPL
how can i change the spl without connect the blackstone to the pc?
thanx
Click to expand...
Click to collapse
You need to downgrade your usb drivers. Follow this guide on step-by-step procedure on how to flash a rom including how to downgrade drivers
http://forum.xda-developers.com/showthread.php?t=505377
Also, any further queries, please post in that thread