Database Info

Stuck in bootloader, please help!

Hello all,
Yesterday I tried to update my MDA Compact to qtek 1.06 and I saw to executables in the package:
getdevice.exe and enterbl.exe
I runned getdevice.exe for getting the device data for in the change.bat. That went oke, but out of curiosity I had to run the enterbl.exe, which made me go to the boot loader immediately. And now I'm stuck at the boot loader!
Whatever I do it won't boot to WME anymore! Soft reset, pressing the camera+power+reset, everytime it goes to the "Serial V1.00"screen.
When I remove and put back the backcover of the device (where the battery and sim are) it will go off and after a press on the power button it will boot to WME. But when I manually reset the device or when it automaticaaly reset itself after installing the ExROM tools, it goes back to the boot loader (Serial - V1.00) screen!
I even dumped the ROM with mmty to the SD card and flashed the device with that ROM again, but after it says Checksum is OK and I press reset it just goes straight to bootloader again.
I'm really out of clues of what to do. Can someone please help?
EDIT: When removing and putting back the backcover I can reset the device and it will boot back to WME so I can use it. But still when I softreset (with button or through software) it goes to boot loader. :-(
So using the backcover as a reset button is possible and does work, but it isn't very handy/usefull off course.
TIA
Regards,
Aurora13

Check the forum, the answer is there
Yes, you are still in bootloader mode and it's actually getting ready for you to flash.
Donno which part of it goes wrong, mine also have the same issue. What you need to do now is to restart your desktop pc / laptop (from the info I gathered from the forum). Then run that update thing again. This time, the same screen will appear saying it's trying to get the device data. Difference is, this time you no longer see the current version of ROM (as the Magician is in bootloader mode now). And you will see it show you the ROM that you going to upgrade to. Just follow the instruction, everything is straight forward. Hope this help.
cheers..

Thanks man!
You're the man cyberjaya!
It is working now, here is what I did (as told by cyberjaya):
- Rebooted my laptop
- Connected the MDA to the laptop
- Started the upgrade program of the qtek 1.06 ROM
- It didn't found my version, but it would let me update it to 1.06
- Flashing....(15 minutes is a LOOOONG time if you have to wait )
I did reset it a few times and it just boots normally!
Thank you ver much cyberjaya!
Regards,
Aurora13

No problemo
Am using laptop to flash also. Likely it's the USB hub thing (which listed in the "hardware devices" list). Read it somewhere, it's not recommended to flash using USB hub. Enjoy your new ROM!! .
cheers

I had a thought:
Isn't this the way to do a ROM upgrade without editing the ROM files?
Because it can't detect a different ROM and it will do the upgrade...
Or am I missing something?

Help with a "Bricked" Tilt!

Any Help Appreciated. Anyone ever seen this type of "Brick"?
After flashing a new ROM (Tilt XDA-Live v1.0 - fully flashed to 100% and said finished), the device won't boot. It just gets stuck in an endless loop. It trys to boot, shows the AT&T screen, then reboots/resets back to the beginning before getting to the Windows mobile screen.
The only way to get it to stop the loop is to pull out the battery. Put the battery back in and power on and you get the loop again.
I have loaded HARD SPL (1.0.OliPof).
I can get into Bootloader mode by pressing power/camera then reset.
In this mode, I can get it to reflash the ROM (and even other ROMS) but it still ends up in the same loop.
I have tried flashing the Official ATT WWE ROM from this thread but it still loops at boot.
I did the "original/problematic" flash using Vista. Could that be the issue? I have done subsequent "recovery" flashing using XP to no avail.
I have flashed several ROMs to my Tilt in the past (Mostly Dutty ROMs).
I had a Hermes before and flashed that a million times no issue so I'm not a complete noob.
Any ideas? I'm stuck with a brick!
Thanks in advance.

I'm in the same boat. I've flashed over and over (with different ROMs) and am still stuck. But I did every flash from MicroSD card. Did you get any help?

No input yet.
What ROM did you flash that started the problem for you?

dutty's touchflo rom beta for the tilt. i was on dutty's hybrid rom version 3. after flashing the OEM at&t ROM, i'm out of ideas. stay in touch if you find a fix. i'll keep searching.
- J

Bump...
Anyone else seen the issue with a Tilt stuck in a "boot loop" after flashing (see first post)?
Paypal reward for anyone who helps me recover - otherwise I'm going to have to go buy another Tilt (which I could live with but worse yet, I may be stuck with the stock ROM because I'm too gunshy to go back to my flashing ways)

Tried all day to find a fix. Think I made things worse. Read up on some threads using the mtty tool and ran a command (task 2a) that cleared the flash. But now it doesn't even boot to a splash screen, and I can't get back to bootloader mode.

This might sound a bit stupid, but I have taken note that my device upon flashing the new at&t rom actually held some of the information, you would think that a hard reset is performed after a rom flash, but that just wasn't how it worked out for me, anyway I had a radio that wouldn't come up, but would after a hard reset, this was directly after flashing my tilt...
?Glitch

Glitch,
Yeah, I have heard in several places that you need to hard reset after a flash to clear out all the settings from the old ROM. Seems odd since you just overwrote ROM - I think of it as a format (HDD mindset) but I guess it's not a clean format.
Jerich007,
Sorry to hear you went backwards. I stopped flashing my Tilt for the same reason - worried about getting farther in the hole without some expert advice. My next step was to try the MTTY tool just as you noted. Guess I'll go that route as a last resort. If it's any consolation, I seem to remember reading about plenty of people recovering from a "brick" that won’t go into bootloader mode.
Hopefully someone trolling the waters will see this thread and take up the offer for a Cash Reward (Paypal) for help recovering this Brick!

ill put up some paypal $$ for a fix as well. i'm at the end of my rope on this one. i'm subscribed to some other threads so hopefully we'll get some feedback.

It is not so serious as you think! Try the following way:
1- Download the original rom from AT&T (the 1st rom was installed on your device)
2- Turn your bricked Tilt to bootloader ( http://wiki.xda-developers.com/index.php?pagename=Kaiser_Resets )
3- Start flashing your Tilt with the above AT&T rom.
Evething should be OK after that! (but your device need to be installed Hard-SSPL before!!!)

try...
try this link
http://forum.xda-developers.com/showthread.php?t=286755
and maybe these
http://wiki.xda-developers.com/index.php?pagename=Hermes_Unbrick
http://forum.xda-developers.com/showthread.php?t=334693&highlight=how+to+unbrick
http://forum.xda-developers.com/showthread.php?t=344402&highlight=how+to+unbrick
don't forget that some of this info isn't for the tilt...
good luck, and be careful

This ROM solved my issues
try this thread
http://forum.xda-developers.com/showthread.php?t=327482
and DEFINETLY download the ROM, flash it. Once it's flashed,then ya can reflash any ROM ya want. Get the newest stock ROM from the sticky and reflash it (if ya want the ATT ROM)
That will fix it.
(I reflashed Tilt XDA-Live v 1.0, and it's working GREAT.)
I did the same thing to my Tilt.
That ROM saved me.
Alemaker

Problem is I can't get to a bootloader screen now. I press Camera+Power+reset, but all that happens is the green LED goes off then on, and then the screen is blank. Anyone know any other tricks? I think I may have erased my bootloader using mtty command 'task 2a'.

...
Hate to say it, but if after hours of searching on the forum you can't find an answer, i'd pm a pro like pof. I don't know if that will work, but their advice is the only thing i'd listen to.
Don't forget to give a lot of detail and maybe mention what you've tried.

Thanks. I've already PM'd pof and olipro. Hopefully they can come up with something.

jerich007 said:
Problem is I can't get to a bootloader screen now. I press Camera+Power+reset, but all that happens is the green LED goes off then on, and then the screen is blank. Anyone know any other tricks? I think I may have erased my bootloader using mtty command 'task 2a'.
Click to expand...
Click to collapse
****, I should have replied after someone posted all those links to Hermes unbrick procedures, to never do a task 2a from hardSPL. It reformats entire flash including SPL and the problem with hardSPL is that you can't flash another SPL, even if you would have tried before rebooting
Anyhow, your only chances to unbrick your device are to try to enter radio bootloader (there is a radio bootloader running on the mARM (ARM9)) and then to flash it. However, only service centres have such flashx utilities I'm afraid. Furthermore I'm not sure if radio bootloader can be entered directly, usually you can enter it via the normal CE SPL. You can try to first connect USB and then press reset with the stylus while holding the Voicecmd key. If you are in XP, then three new devices should be found (composite USB, a modem and a diagnostics port). Download the Motorola "Q" usb drivers, these will work just fine. In this mode you will have to authenticate to the radio bootloader before you can start entering commands. We'll get to that if you manage to connect. Your other chance to unbrick is via JTAG. I know the kaiser has JTAG points scattered on PCB.

Ok, thanks, I'll search for those drivers and let you know. By Voicecmd key do you mean the push-to-talk key along the side or the talk key with the green phoneset icon?

The top button at the left hand side

Ok here's what happens:
1. downloaded Motorola USB drivers (32-bit) from their site, installed and rebooted.
2. plugged in Tilt via usb cable, 'found new Hardware wizard' starts.
3. clicked next to auto-search for drivers, but the wizard fails with 'cannot install this hardware' message. I have 3 yellow question marks in Device Manager for 'Data Interface' devices.
4. held down Push-to-talk button and hit soft reset. No change, no leds are lit, screen is off.
Did I grab the right drivers?

Not bad at all. Apparently your phone is in Qualcomm DIAG mode, probably as a consequence of task 2a Now you can forget about rebooting with Voicecmd pressed.
Either you've got the wrong drivers or you don't install them in the correct way. Go in device manager, right click one of the 3 and update driver, then 'install from a list or specific location (Advanced)', then check 'Include this location in search' and enter the driver path. I'll take a quick look if I can find the drivers for you, I vaguely remember they were on mobile-files dot com.
EDIT: found the drivers, attached. The VID and PID of the found usb devices should be VID_05C6&PID_6000. Take a look in the device's advanced tab in device manager.
PS: Although diagnostics mode sounds great, I haven't yet found a way to flash the device. Perhaps it works with that Hermes radio flasher MaUpgrade_NoID.exe
Guys with a working SPL can enter radio bootloader DIAG mode via "rtask b", exit MTTY and install drivers. It would be great to know if someone has a htc/qualcomm radio flash utility (perhaps MaUpgrade_NoID.exe is what you need)

Absolutely death?

I tried some new ROMs (by Tomal, luca16thebig, VNInt...) and after upgraging to Cotulla latest version Uni crashed!
Now it only can boot in to hard reset mode (LEFT softkey + RIGHT softkey + RESET), no another activity. PC can't recognize device.
I tried to disable USB connection in ActiveSync and used Multi TTY/ExitBT. These tools couldn't connect to device (mtty says "\\.\WCEUSBSH001 port can not open").
(Uni in that moment was in hard reset mode)
How can i repair device?

MaximKorobov said:
I tried some new ROMs (by Tomal, luca16thebig, VNInt...) and after upgraging to Cotulla latest version Uni crashed!
Now it only can boot in to hard reset mode (LEFT softkey + RIGHT softkey + RESET), no another activity. PC can't recognize device.
I tried to disable USB connection in ActiveSync and used Multi TTY/ExitBT. These tools couldn't connect to device (mtty says "\\.\WCEUSBSH001 port can not open").
(Uni in that moment was in hard reset mode)
How can i repair device?
Click to expand...
Click to collapse
Go into bootloader mode (on/off button, light button, and reset hole all at once) make sure your sd card is out, and try to flash again with cotulla rom! dont forget to read his instructions to go back to normal roms and allow time for rom to set up, dont hard reset after you flash!!!!
regards
Jay

Yep.
I move out SD (SDHC) and SIM cards.
Tried flash again - when PC program usually show previous version and new version right now it show empty fields. When it start to flash it show "Error 112: CE ROM UPDATE ERROR" message.

When my Uni is bricked I boot into the bootloader with the "Serial"-string. Then I put my SDHC out of the device and then it says "USB".
Every flash worked very well.

I can't force it to show "Serial"-string

Try this
Cotulla ROM is different.Memory allocation is different.
1.Remove SD card and always remove the SIM card.Very important.
2.First uncheck the 'allow USB connection' in active sync or WMDC[if VISTA].
Close active sync/WMDC in task manager.
3.Put Uni in BOOTLOADER.[Power+Backlight+Soft reset].
4.Run mtty.Click on USB.
5.Type 14 0 [ there is a single space between 14 and 0],press enter.
Wait ....
6.Type task 32 [there is a single space between task and 32],press enter
Wait....
7.Type task 28 55aa [ there is a single space between 28 and 55,and no space between 55 and aa],press enter
Wait...
8.When the desktop finishes the work..usually takes 5-10 seconds..close mtty.
9.Disconnect Uni...which is still in BOOTLOADER...
10.Go to active sync/WMDC and check 'allow USB connection'.
11.Flash with a WM5 ROM..I had KDSkamal's Ultimate ROM.
12.You should have got Uni back.
13.Then upgrade it to any ROM you want..6.0,6.1etc...if you want to.
Honestly speaking I don't know what the heck these procedures are,but if you do this STEP by STEP it works like a charm.
Cheers...waiting for your reply.

OK.
Now i know what to send Uni via mtty.
We have a solution to connect tools to device properly (mtty says "\\.\WCEUSBSH001 port can not open") after such crush?

MaximKorobov said:
Yep.
I move out SD (SDHC) and SIM cards.
Tried flash again - when PC program usually show previous version and new version right now it show empty fields. When it start to flash it show "Error 112: CE ROM UPDATE ERROR" message.
Click to expand...
Click to collapse
Will it go into boot loder mode??

Please give info
Okay.
So you mean your device is stuck in---
white screen
Splash image
Bootloader
Or what?
I just like to help out,I just read wiki.

responderman said:
Will it go into boot loder mode??
Click to expand...
Click to collapse
In to hard reset mode (LEFT softkey + RIGHT softkey + RESET) - yes.
In mode, when it show "Serial/USB" connection - not.
kalya said:
Okay.
So you mean your device is stuck in---
white screen
Splash image
Bootloader
Or what?
I just like to help out,I just read wiki.
Click to expand...
Click to collapse
Look (It can be shown only with USB connection):
http://picasaweb.google.ru/Maxim.Korobov/RepairOfHTCUniversal?feat=directlink
And nothing else

Well,at this stage,what happens when you press 0[zero]?
And can you please tell whether you can PUT the UNI in the BOOTLOADER by pressing POWER+BACKLIGHT+SOFT RESET simultaneously?
Because I have read almost all the threads regarding STUCK uni and I never came across one with a screen like yours.
On the second thought...press Backlight+Soft reset simultaneously...what do you see?

The image you are showing us is "Hard reset" what you want is bootloader. you get boot loader as we described above, once you have it in boot loader it is easy to get your uni back. In bootloader it will say serial or USB if it is plugged in at the top and V1.01 or V2.01 or something like those numbers at the bottom on a grey unlit screen.

kalya said:
Well,at this stage,what happens when you press 0[zero]?
And can you please tell whether you can PUT the UNI in the BOOTLOADER by pressing POWER+BACKLIGHT+SOFT RESET simultaneously?
Because I have read almost all the threads regarding STUCK uni and I never came across one with a screen like yours.
On the second thought...press Backlight+Soft reset simultaneously...what do you see?
Click to expand...
Click to collapse
1. If i press zero, Uni show "Cleaning now" message and after about 3 seconds turn off;
2. When i press POWER+BACKLIGHT+SOFT RESET there is no any results. What this keystrokes mean? I didn't know it before;
responderman i can't send command via mtty cause it don't wanna to open USB port.

Man,I am no techie,but really want to help you.
MaximKorobov said:
1. If i press zero, Uni show "Cleaning now" message and after about 3 seconds turn off;
Now,Forget mtty.
First PLEASE charge the battery 100%,use another unit if neccessary to charge.
You said When i press POWER+BACKLIGHT+SOFT RESET there is no any results. What this keystrokes mean? I didn't know it before
What do you mean by that.
1.You cannot enter the bootloader
or
2.You don't know what the bootloader is?
And did you uncheck usb connection in AS,remove SD and SIM during MTTY....just to be sure
And finally PLEASE read this thread...It is really helpful..though old.
http://forum.xda-developers.com/showthread.php?t=259003&highlight=universal+dead+stuck
Click to expand...
Click to collapse

"1.You cannot enter the bootloader"
But now... it's funny miracle.
I try POWER+BACKLIGHT+SOFT RESET again and it's go into bootloader (previously - no, just empty screen).
5 minutes and new rom installed successfull.
Thanks you guys!
It was very bad half week with a brick.

Well i'm glad we got there in the end. Can I recomend reading up in the WIKI to get to know things a bit better. Welcome to the forum

Glad to help!
Good to hear that.
And yes please search,read wiki,and please please name your threads in such a manner so people can understand what it's really about.
And I am glad this thread can be closed 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?

stuck during boot, do not know what to do

hi all...
...I hope that you can help. Some years ago, I have flashed my polaris from o2. i then got myself an iphone and some new computers (using vista now instead of xp), so that I do not have any of the old files that I used back then to flash the phone. my father was using the xda for quite a while now. however, suddenly the device is not working any more: if you turn it on, the boot screen will appear, but then it is stuck and nothing is happening (even no rom info in the lower right corner). also a hard reset doesn't help to overcome this problem.
what I am trying now is to flash it, because I guess (and hope) that this might help. But, to be honest, I completely forgot how this works. I downloaded an original rom from this website today, but I cannot flash it to the device (stuck at 0%, getting an communication problem error). If I turn on the phone with camera button pressed down, the tricolor-screen appears reading POLA200, SPL-3.13.0000, CPLD-2. what am I doing wrong? your help is greatly appreciated.

Try flashing the rom from the tricolour-screen just make sure at the bottom of the tricolour-screen it say's usb not serial.
You will only be able to flash official roms as you don't have a stock spl not hard-spl.

thanks. I tried this one from this forum: RUU_Polaris_o2_GER_1.24.207.2_withSplash_noRadio_schaggo_[fixed]
but it did not work.
however, I now downloaded the rom from the original o2-site and it is at the moment in the process of flashing it - let's cross fingers.
damn, it did not work. I mean, the flashing succeeded, but the problem still persists: if I start the device, the start-screen appears, but that's it - nothing happens afterwards, and after some seconds, the device turns itself off again.
what could that be?

Could be the battery if the device turns itself off,try booting with the charger or usb still in.Or flash hard spl and try a different rom.

hi all friends if you are stuck on 0% and u cant install spl then do this ,,,
You can try this:
1. Stop ActiveSync
2. Open Task Manager (press Ctrl + Alt + Delete) on your PC and
stop these two processes rapimgr.exe and wcescomm.exe
3. Plug in your device via USB. Your computer should be asking install a driver. Install and continue.
4. Now Run mtty and choose USB in 'PORT'
4. type "set 16 0" without the quotes to tell bootloader to boot the OS after reset.
5. type "task 8" to get your device formatted.
6. Now unplug your device and manually reset it.
i hope you will be happy after .. thanks