Database Info

ERROR 262 - Bricked phone with Radio Rom Upgrade - SOLVED -

Hi to all,
I have an AT&T TILT HTC 8925,
ROM: 1.57.502.2
RADIO: 1.27.12.11
VE: 22.45.88.07H
Installed the kaiser-HardSPLv1 with no problems.
After this I Flashed (via USB) Q-Mobile_v1.2 ROM, that went perfect. Made a soft reset and then a Hard Reset after this I configured the phone.
After everything was working I made a Radio flash with KAIS Radio Only 1.27.12.17 CustomRUU, all seemed normal until it got to 95%, it suddenly interrupted the update (error 262), and took me to recovery dialog 1-4 steps which I did.
From that moment until know I get the tricolor screen with the following text:
RUUNBH​KAIS 1*0
SPL-1.56.0000
CPLD-8
USB​
Click to expand...
Click to collapse
And when I try to flash ANY ROM, It gets past the tricolor screen, to a white screen with a percentage bar that gets to 0%, after a minute or so the customRUU screen goes to error 262 and I get to the recovery screen, etc...
I run on WinXP SP2, and have already tried several roms with the same result, with the exception of original ATT RUU_Kaiser_CINGULAR_WWE_.exe, it then gets to 1% and displays error code 294 Invalid Vendor ID.
When I tried the MicroSD method with the rom it gets to the tricolor then the "Loading..." screen, and keeps there (I waited for about 30 min)...
There was no SIM or MicroSD card on the phone at the moment of flashing, and I did dump the original ROM to the 4 raw parts as per instructions.
I live waaay out of the countries with AT&T or HTC servicing routes, so I am stuck with it until I fix it, which I know I can do, and to be honest with myself, can't afford to waste the money spent on this thing.
Until now the best similar thing I found about this was with the hermes unbrick phone thread, and I am not sure this works on the KAISER, but to be honest, I get cold sweats to use any more procedures (without reconfirmation) on this as I have a phone that at least still shows "some" signs of life.
After reading days of threads (my eyes are burning) I know the knowledge is within this site, but I need guidance since I am new to this thing (smartphone flashing) although familiar with computers.
Any kind of help will be very appreciated and valued.
Best Regards.
----------------------
As an update, I solved this thing. Thanks for your help.
After seeing that there was some sort of problem with the boot mode screen not showing the kaiser-HardSPL data, I went in that direction. After some suggestions and much trying I decided to download all / any original roms I found in here for my phone (ATT Tilt) then I worked my way from top to bottom based on the versions of the radio.
The one that solved my problem was 1.5.502.3 Radio 1.27.12.11 although strangely it shows on my phone after the successful flashing. 1.5.502.1
Just out of curiosity I went and installed again kaiser-HardSPLv1 and it gets to this text on tricolor screen:
Kais1*0
SPL-.JumpSPL
CPLD-8
Doing a hard reboot (camera button + soft reset) gives me a different screen:
Kais1*0
SPL - 1.56.0000
CPLD-8
Really don't know if this is normal, and after flashing a cooked rom I had to reinstall it (kaiser-HardSPL).
I have now reflashed QMobile rom and have no problems. Although I didn't flashed again new radios
For flashing the Original rom I did make sure of the following steps in addition to normal ones (Just in case)
1) Disconnected fisically from LAN (Unplugged LAN Cable)
2) Disabled all firewall protections
3) Disabled all antivirus and spyware protections
4) Run RUU original files
5) Pray
Thanks again people

I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/

I just tried it again (See I am not so scared anymore), and received the same results (Radio upgrade fails on 95%).
I have burned the original ROM back and all is well again!

I also can't get past the same screen and try as I might Activesync won't recognise the phone. When going through the recovery process on Kaiser Custom RUU it says its recovered but then when trying to go through the update it sticks on 0% and then says there are communication problems etc.
On the tricloloured screen it says
KAIS130
SPL-1.81.0000
CPLD-8
Will a hard reset do anything?
Any help much appreciated.

Bump
Now managed to boot via MTTY but power off etc returns me to bootloader screen

Looks to me like you guys have had problems flashing hardspl. Your tri-colour screen should have:
KAIS130 MFG (or Kais 120 etc)
SPL-1.0OliPof
CPLD-8
I don't know about the CPLD number but you MUST have the OliPof SPL. Check this after running hardSPL to make sure that it's there before flashing another ROM.
If you have this but still get trouble flashing, try going to the tri-colour screen and then run the kaiser_RUU.exe to upgrade.

http://forum.xda-developers.com/sho...ked. (One without a radio)
- Flash a radio...

i had the same thing with my MDA Vario 3,but with no success finding the original ROM, since I`m from a small country. I`ve tried to reboot to normal screen via MTTY but it gives me the error: Command error . So - now I`m left with two options: to dump and reconstruct an original ROM from the same type of phone or to find what`s wrong with MTTY.
Anyone had a similar problem, I mean with MTTY and command error???
yes, i`ve searched trough the posts regarding this problem but I didn`t find any saying that MTTY gave this error.
any idea?
THX in advance!

Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061

Martinhdk said:
Focus on HARD-SPL - get that on the phone and make sure its there.
If you cant get it on try this method:
http://forum.xda-developers.com/showthread.php?t=354061
Click to expand...
Click to collapse
if you`re reffering to my problem-how can I copy the JumpSPL1.56-KAIS.exe file and execute it from the phone if I can`t boot it normaly,it always stays in tri-color boot screen?
actually, I`ve bricked my phone with that HardSPL procedure.It was the first step for unlocking. I`ve copied the JumpSPL1.56-KAIS.exe file, executed it and then rebooted and tried to flash with the modified ROM from the jockyw2001`s unlocker. it stopped at 95% and now it seems that it is still CID locked and bricked in boot mode. i`ve already said what MTTY gives as an error.
any idea what may be the problem?

like always:the problem is in RTFM
while i was working on my Kaiser i was doing lots of other things on other computers so i`ve skipped the step with flashing the HardSPL,that`s why all went wrong now,as i`m at home i have more time to read the posts and i`ll try with the jockyw2001`s procedure from the MTTY, with the task8 command.
hope it will help,unless the only solution is to dump the same ROM....
i`ll higly apreciate if anyone has a different solution....
will post results

The problem is that I can't flash the phone with anything be that HardSPL or the original Orange ROM or whatever you care to mention because the PC can't communicate with the device via the USB cable after Activesync ceases to operate. As such everything works up until the % progress bars come on both screens and then they stay at 0% before the communication error message appears.
Funny thing is that the phone is communicating with the PC as USB/Serial alternate depending on whether the cable is plugged in or not and the PC recognises the USB device when its plugged in and when Activesync isn't controlling the situation.

I've been stuck like this with a Hermes but not the Kaiser (yet). As far as I'm aware, you don't need activesync running to run a rom upgrade. If you are in bootloader mode (tricolour screen) you can run the upgrade directly with activesync not connected. If hardspl isn't installed then you should flash the original rom, and if you're unlocked then any rom should do.
Also it might be worth trying the SD card method for flashing. But either way I'd use the original rom and then when you get the phone working again keep trying with HardSPL until it's successful - don't flash any other roms without it.

Laubscherc said:
I had the same issue (I mean exactly the same). After failing the radio upgrade (Luckily I had my trusty Universal, so I started playing around (MTTY, Radio Roms etc.). The only thing that saved my TytnII was the original ROM!!
ftp://ftp.xda-developers.com/Uploads/Kaiser/Roms/
Click to expand...
Click to collapse
Thanks for your help.
I did try other "original" rom I got in here http://wiki.xda-developers.com/index.php?pagename=Kaiser_ROMs
The version corresponding my rom is (1.57.502.2 (radio 1.27.12.11)), however I got the error code 294 Invalid Vendor ID after 1%.
I did try the ftp address you mentioned, but I can't login neither anonymously nor with user & psw for xda-developers.
I would like to try the rom you are referring to, please give me another link to download the file.
Best Regards.

Martinhdk said:
http://forum.xda-developers.com/sho...ardware devices list.
Thanks for your help.:)
Click to expand...
Click to collapse

Stuck in Tri color screen
I have been fighting the same issue for several days. Radio gets to 95% and errors. Then hung up in tri color screen. I used MTTY - "set 14 0" command then "boot" command inMTTY to get the phone to boot. I have had to do this a number of times, sometimes more than once per incident. Hope it works for you too. P.S. once you have a successful flash the phone returns to normal operation until then it will go back to tri color screen on reset. I just flashed a startup splash screen to get mine back to normal.

pennco can you expand in further detail on what you actually did with MTTY cause I have the EXACT same problem....

PANIC - plz help

I finally got the nerves to put the new radio and rom version on my HTC Touch pro.
It went wrong at 1%, and the recovery option was in a loop.
So I did exit the process after recovering/restarting like 12 times.
It did exit on a 262 error at 0% or 1%...
Ok let’s try one other rom; now I did first run the HardSPL Unsigned 190.1.3 again as advised before every rom update, and it was successful...
But when booting the phone it is stuck at the black TOUCHpro screen with the following red text at the right bottom.
R 1.02.25.19
G 52.33.25.17U
D 1.90.00.00
Now whatever I try, whatever rom version I use, it always tells me the phone is not connected by USB.
Seems like the USB driver or something is not loaded at this stage. Maybe when by some key combination I get the phone in the ROM/Boot loading menu I can try other rom version. But I could be completely on the wrong track here.
I was so happy with my WM6 phone, please help me so I can enjoy my phone again, hopefully not with the old rom and radio ofc, when possible.

Don't panic!
Put a the NBH file of the rom you want to flash on your storage card and rename it to RAPHIMG.NBH. Start the bootloader (reset and keep pressing the volume down button) and follow the directions on the screen. When it sais it flashed succesful reset again.
Of course this only work if you did install the hardspl...
Good luck,
Cheers,
Cacti

Ok found that when I go in bootloader mode manually by pressing the Volume-down and reset button at the same time it can connect to my PC.
But no matter what rom version I try, original, Stock or custom it stops at 0% or 1% .. Giving me any of these errors :
readme.doc said:
ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
Click to expand...
Click to collapse
Plz help me, I am using the original USB cable and did try a general one, no-USB hub, did remove my firewall/virus scanner software and all.

Put the NBH file on you storage card and rename it. Don't use rhe RUU...

Thanks le_cactus, the above message crossed yours..
I will try getting the new rom trough my MicroSD card, good thing I have no regular Diamond..

Diamond?
This is the HTC Touch Pro forum

Yhea I know, I have the TouchPro... aka as the Professional version of the HTC Diamond in the Netherlands.
Raphael is rarely used here, only by people who are into rom's and TF3D hacks and stuff...
Damn my CF/MD adapter does not seem to work, or my card reader, printer with card reader and my iPaq don't support 8GB cards..
Guess I have to go to the shop tomorrow for a smaller card with a new adapter or a card reader that accepts MicroSD to get my phone back to order.
Thanks for your advice and cooling down my panic moment.. "Bedankt !!!"

Thanks man for 14 euro's I did buy me a card-reader that is able to handle my 8GB microSD card and my problem is solved. Running on 405.3 with latest .28 radio drivers now.

A little help please, guys

I'm new in the world of flashing cooked ROMs
and i need to do it but i can't
Everytime i try to Flash HARDSPL 3.xx, it stops at the percentage screen and gives me an error on my pc.
And i tried to flash the ROM directly, and same problem.
I'm getting nervous of this stupid mobile, please i need Help.
I read all posts on how to install everything but nothing completed to the end.

bebo833 said:
I'm new in the world of flashing cooked ROMs
and i need to do it but i can't
Everytime i try to Flash HARDSPL 3.xx, it stops at the percentage screen and gives me an error on my pc.
And i tried to flash the ROM directly, and same problem.
I'm getting nervous of this stupid mobile, please i need Help.
I read all posts on how to install everything but nothing completed to the end.
Click to expand...
Click to collapse
you should go here ...

I had a problem when I first did mine. at the tri-color screen my phone never said USB on it and my computer showed an unknown usb device. Here's what worked for me but remember you only need to do this the first time, Once you have HardSPL flashed your phone will work like normal.
after your phone gives you a warning that a program is going to reboot it. You get a tri-color screen. As soon as you see this screen hold the camera and power button and press the reset button, don't disconnect the usb cable.
In other words the program that causes your phone to reboot doesn't allow the usb to work properly but a manual reboot into the SPL using the camera/power button does. I have not tried the "Forced USB" version of HardSPL because this problem goes away once you get HardSPL installed.

This would be better posted in the HardSPL thread.
Flash an official stock ROM, then follow ALL the instructions in the link deepthroat gave you to the T.

Please help, I think I just broke my phone.

So I was flashing my first rom (NATF) and as far as I know I did everything right. HardSPL first, no programs running, etc.
As I was flashing my rom, the installer goes "ERROR" and it says I need to perform these steps. So it says to unplug it, so I do. So it says to take out the battery, so I do. So it says to put it back in and see if I get the colour bars screen - and I do.
So it says to plug the cable back in... but it doesn't recognize it. It says Serial on the bottom instead of USB. What do I do?!
The USB port on my phone isn't broken, as when I plug my phone into my charger it will turn on. Automatically. But the computer won't recognize it at all.

try flashing via Micro SD. Instructions are over at the GSM Flashing for noobs post.

I put an image file on the SD card, I turn on my phone, it goes to the regular tricolor error screen, then it goes white and says loading or something, then it says "Error no image file" and then goes back to the tricolor screen.
I don't know what to do now.

PwnCakes tried a lot of things with me, but none of them have worked so far. Anyone else??

had that problem on my tilt. It was solved by the higher powers at xda by using a jump spl and then flashing to a hard spl. Do some research and find out who made the jump spl and PM him, he is the only one that can help.

From what I've found out about JumpSPL, it is for HardSPL problems. But HardSPL installed fine.
Plus, one of the directions was to connect my phone to my PC - and my phone won't connect to my PC.

you might have corrupted your bootloader and you must install a soft spl then jockyw2001 provide me with a force usb version of the hard spl to load and then all was well. Trust me PM these two guys and they can help.

Thanks man. I'll PM them now.

[TUT] Flashing and Unbricking your Maple

Welcome! Almost everyone has done it. Bad flash and suddenly your $400 device is a paper weight! Woaaaaaah! Even I have to admit I have done it, many times. But there is hope! Read on.
It is not easy to brick a device if you actually read and follow all of the steps and guidelines before a flash. In fact, not many things can go wrong unless a USB cables disconnects during a flash, your PC crashes in the middle of a flash, or you flash a corrupt image file to your device. Statistically, most of the time people only think their device is "bricked" when actually it's not.
There are currently three methods you can use depending of the severity of the "bricking". The first method will unbrick 50% of all Maples that have simply "locked up" and won't reboot properly. The second method will unbrick 95% of all Maples that encountered flashing problems or flash failures.
** Please perform these steps and methods at your own risk. I am not responsible for any damage you cause your device using this guide.
If you're new to the Maple or SmartPhones in general, please take the time to read the the forums for valuable info before you post or try any of these steps.
But, before I even get into unbricking, if your phone is in fact working right now, I highly recommend you flash HardSPL by JockyW to avoid even having to follow these steps anytime in the future. The steps and info for HardSPL and JumpSPL can be found in this thread by jockyw2001.
HardSPL basically flashes your phone with an "unlocked" security partition so all security checks are bypassed when you try to flash a cooked ROM or a ROM designed for another variation of the Maple such as HTC (SNAP), TMO Dash3G, etc. Makes life much easier when trying different ROMS or cooking and testing your own! Thanks to jockyw2001!!
Ok, so onto the fun stuff...
Flashing:
First a bit of background and info on the different types of ROM images. There are a few different types of ROMS. Carrier released "signed" ROMS, carrier "signed" TEST ROMS, and custom "unsigned" cooked ROMS. The first two are usually released by the carrier (HTC, TMO, AT&T, VOD, etc.). These carrier "signed" ROMS can be flashed anytime without any modifications to the bootloader, SPL, or the device itself. The device already has security checks and certificates in place to check the ROM you are trying to flash to make sure it is official. They do this to avoid users from sending back their "bricked" devices after a failed flash or just user error. This applies to TEST ROMS as well however, TEST ROMS are for just that, TESTING. They usually have an expiration date or "timebomb" applied when the testing period has expired. Cooked ROMS, on the other hand, require unlocking the security checks of the bootloader (SPL) in order to flash successfully. This clarify, this method has several names and is also called CID unlocking, JumpSPL/SSPL (temporarily bypass security checks), HardSPL (permanently bypass security checks), and CID bypassing. Here are the steps to a happy user and a successful flash:
Remove your SD Card
If your device is already hardSPL, proceed to step 10
If using JumpSPL, boot your device up to your homescreen
Download and unzip the ROM package file
If flashing a custom cooked ROM, run auto.bat, or auto_1.17.bat, or auto_1.19.bat (depending on your SPL version)
Follow the prompts in the DOS window
Hit "continue" (trackball button) on your phone, screen will turn black
Run RomUpdateUtility.exe (if it doesn't run via the script)
The flash will take about 5 minutes
If your device is already HardSPL, simply run RomUpdateUtility.exe and follow the prompts
Upon first boot, it will seem frozen for a few minutes, maybe even go black. This is NORMAL!
Enjoy!
Unbricking:
Your phone won't boot... Either it's locked up and simply stopped booting or you flashed your phone and it won't boot. What do you do??
Method 1: Assuming you didn't get "bricked" from a flash problem, the first and easiest method for "unbricking" your device is (this will erase ALL data on your device):
(This method works for 50% of supposedly "bricked" devices)
Remove your SIM and SD card
Remove and reinsert your battery
While holding the volume UP key, press the power button
Continue holding the volume UP key until a black screen appears saying "This operation will delete all your..."
Press "'send"' to restore to hard reset your phone
Let the phone cold boot and restore
That didn't work!! . This next method will reflash your phone to the factory ROM.
Method 2: Second way to the path of unbricking is:
(This method will unbrick 95% of all Maples)
Get a hold of your Shipped ROM. You can find these ROMS either on HTC's site (with a valid serial #), TMO's site (http://www.t-mobile.com/wmupgrade/ with a valid IMEI), or right here at XDA Developers (search for it).
Download one of the factory ROMS and unpack it. **Remember, if your phone is a TMO Dash3G, you MUST use a TMO Dash3G ROM. If your phone is HTC Branded, you MUST use an HTC ROM, etc., etc., etc...
Remove the SD card if one is inserted in the phone
Remove the battery from your phone for a few seconds. I found this step to be essential to reset the device. Put the battery back in.
While holding volume DOWN button, press the power button. The phone will enter "bootloader" mode and you will see a tricolor bootscreen.
While in this mode, plug in your USB cable and you will hear the "ba-bing" USB sounds as the device connects
Unpack the ROM package you just downloaded and run RomUpdateUtility.exe. Follow the steps, check the appropriate boxes, and start the flash
Assuming all goes well, your phone will flash to the factory ROM and you can then troubleshoot what went wrong the first time that bricked your phone.
Method 3: The "goldcard" final method is a bit more intensive so follow closely:
(This method will unbrick 99% of all Maples regardless of branding)
Get a cup of coffee or tea
You will need a working Donor HTC device with a microSD slot and a microSD card that is smaller than 1GB (will be formatted) to create "goldcard" image using QMAT tools as described below
You will need QMAT. Get it from http://revskills.de/index.html.
Go to the Download Link and download the latest version and unpack QMAT
Have some coffee
Use a SD card reader in your PC to access the SD card through Windows. Format the SD card with FAT32.
* Insert the SD card into the donor HTC device and connect the USB cable. If you unchecked "Allow USB Connections" in Activesync in an earlier step, make sure you recheck it so that you can establish a full USB sync connection to the HTC device.
Open QMAT and go to the "Hardware Forecsics" (version 5.04 and below) or "Calculators/Generators" (version 5.05 and up) menu and select "Generate HTC Goldcard"
In "Select device key:" select the Maple
You will need the serial number from the SD card so click the "Get SD Card Serial from WINCE Device" button
Once the Serial number appears in the box, click the "Save Goldcard Image to WINCE SD" button below
If no errors pop up and all goes well, proceed to these next steps
If you get an error or a popup saying "Goldcard for newer devices isn't implemented in newer devices", you must buy and register the software. Believe me, it's worth the small amount of $ you will spend to bring your expensive device back to life!
Now remove the SD card with the newly written Goldcard image from the Donor HTC device
Insert the SD card back into your PC using the microSD card reader adapter. Browse to the drive letter assigned to it. You will see no files on the SD card, this is normal.
(If, for some reason your PC sees the SD card as unformatted, something went wrong. Remove it and reinsert it into the Donor HTC device. The device should see the card as unformatted and ask you to format it, say yes. Now go back to the "* Insert the SD card into the donor HTC device" step above and repeat the steps)
Unpack your HTC, T-Mobile, or other factory ROM and copy RUU_Signed.nbh to the SD card. Once it had finished copying, rename the file to MAPLIMG.nbh. Remove the SD card from the PC.
Make sure the Maple is off and insert the SD card
Enter bootloader mode as mentioned earlier (hold the volume down button while pressing the power button)
You will see a gray screen that says "loading". It will then find the MAPLIMG.nbh file and ask if you would like to start the update process. Follow the instructions and let the phone flash.
You can also do the update using the Rom Update Utility with the USB cable if you like
It will take 10 mins but your phone should boot fine and be back in action!
QMAT is a VERY powerful tool written by viperbjk that allows for full low level manipulation of HTC and WINCE tasks. Read all about it here http://revskills.de/index.html.
Many thanks to jockyw2001 for his amazing HTC device knowledge! Also thanks to all who contributed to this post.
Hope this tutorial helps!

great tuto!!! thanks thanks
it's all clear now.

Is there a factory rom for the HTC Ozone on VZW? I cannot locate it on this site nor HTC's nor VZW's.
Thanks

WOW
This helped me a lot
Method 2: Second way to the path of unbricking is:
Thanks you very much

87vert said:
Is there a factory rom for the HTC Ozone on VZW? I cannot locate it on this site nor HTC's nor VZW's.
Thanks
Click to expand...
Click to collapse
No factory ROM updates available yet.

I seem to lose internet access when i do this..
I seem to lose internet access when i do this..

http://www.htc.com/us/SupportDownload.aspx?p_id=257&cat=0&dl_id=684
Saw this in the main thread. Is it possible to get the signed stock rom for an S511 from this?
New to the winmo modding thing, so excuse me if I'm an idiot.

No signed ROM available at this time.

Kind of figured as much. So, I guess the next question is, once you have HardSPL applied, if the rom flash fails, can you recover with any rom?
I want to load 6.5, I'm a bit apprehensive though, because the 6.1 update for the Ace locked up mid-flash, and bricked the phone. My company's IT department is...sluggish when it comes to replacing dead phones.

No, you can only recover with a signed ROM intended for the device. Not a cooked ROM.

amirthanto said:
This helped me a lot
Method 2: Second way to the path of unbricking is:
Thanks you very much
Click to expand...
Click to collapse
hi, can you tell me how you managed to get the shipped signed rom? i am scratching my head and pulling my hairs over this. thanks alot!

my bro helped me to flash the hspl by jock the other day, however, he failed to notice it was only for willow snap s511 and not for maple. (confusion btwn the htc SNAPS) now what i have is a only phone that keeps rebooting at 'smart mobility' and then resets itself back to the same screen after showing some red codes at the bottom right.
I have tried your unbricking method 1,2 but I cant find a donor so no go for 3. I have done a hard reset but to no avail and am able to bootload. below are the details. is there a way to rescue it? really appreciate any help rendered. i did not managed to find a shipped rom but i heard from gawain that you can flash a rom from sdcard? my set is htc snap s526 from singapore though. =(
MAP110
SPL-1.19.0000
MicroP-Maple(LED)v6
ENGID 0x2
PCBID 0X90
PanelInfo 15-0x2

UGGGHH
I can't believe how complicated this has turned out to be.
I've read and re-read the posts, and other posts to be sure. I've even flashed a MotoQ before.
I don't know if it's Verizon or what, but my Ozone will only boot up to the HTC loading image and thats it.
I can get into bootloader and it looks like the HARDSDL is installed, and I even can start the ROM Utility, but it just shows 0% forever and then errors out about communication problem.
I'm so frustrated.

Delacombo said:
I can't believe how complicated this has turned out to be.
I've read and re-read the posts, and other posts to be sure. I've even flashed a MotoQ before.
I don't know if it's Verizon or what, but my Ozone will only boot up to the HTC loading image and thats it.
I can get into bootloader and it looks like the HARDSDL is installed, and I even can start the ROM Utility, but it just shows 0% forever and then errors out about communication problem.
I'm so frustrated.
Click to expand...
Click to collapse
try the sd method with an original shipped rom....
http://forum.xda-developers.com/showpost.php?p=4872255&postcount=78

Same problem here. Even tried tried what ibanyard said. It loaded up and went 100 percent but then said Error (294) Invalid Vendor ID. I also noticed that my windows moblie/active sync is disconecting.

Unbricking HTC snap (Sprint)
Hi can you give step by step instructions on how to unbrick a HTC Snap, I never flashed anything on it. but recently it started acting weird and so i turned it off and turned it back on, but when i powered it on it came up to the screen where it just says "htc Snap" and its stuck there
help!
*UPDATE* I found out that this issue is addressed by HTC with a hotfix I will try that and if it doesnt work come back here

I think I've bricked my Snap as well after a failed ROM update (flashing stopped at around 98%). The phone stays on the HTC logo screen and doesn't continue with the boot. I'm able to put it on bootloader mode but when running the ROM update it always stays at 0%. The Sprint "hotfix" doesn't take care of this either. When I run the ROM update utility there is no Image Version being reported by the phone at all. I've also tried to update using the miniSD card but all I get is "No image file found".
Anyone had any experience/luck taking a phone in this state into the Sprint (or whichever) store and ask them to fix/reflash it?

technosavviest said:
my bro helped me to flash the hspl by jock the other day, however, he failed to notice it was only for willow snap s511 and not for maple. (confusion btwn the htc SNAPS) now what i have is a only phone that keeps rebooting at 'smart mobility' and then resets itself back to the same screen after showing some red codes at the bottom right.
I have tried your unbricking method 1,2 but I cant find a donor so no go for 3. I have done a hard reset but to no avail and am able to bootload. below are the details. is there a way to rescue it? really appreciate any help rendered. i did not managed to find a shipped rom but i heard from gawain that you can flash a rom from sdcard? my set is htc snap s526 from singapore though. =(
MAP110
SPL-1.19.0000
MicroP-Maple(LED)v6
ENGID 0x2
PCBID 0X90
PanelInfo 15-0x2
Click to expand...
Click to collapse
I have the exact same problem! Still didn't find the answer.

i have a bricked telus snap s510, when attempting to flash the hardSPL i accidently flashed the 3V0 rom instead and bricked it. anyone know how i can unbrick it? i tried methods 1, 2 & 3 and none of them work. the gold card method just sits at loading... after entering bootloader.

tried hard reset, and when phone is turned on normally it just sits at the smart mobility screen. any suggestions on what to do?