Related
first of all thank you for everyone on this forum for their remarkable work.
ok first i might be a noob but i have read every single thread and still i cannot get it straight. i'm not a electonic user freindly
i need to get rid of the freeze that happens every 3-5 seconds and i read that i have to flasg spl, but which one? (attaching the files needed would be great as i don't know their name and they are similar so just tell me the name of the file)
ok, first of all i have no idea which sl i have as i did the SPL the first time using a file.exe which i cannot even remeber the name , so u tell me pls
when i go to boot loader mode i see this:
KAIS130 MFG
SPL1.0.olipof
CPLD-8
now i have death v3 and radio 1.65.20.29
just need a step by step and which file to use first and what to do in it , i have no idea what OEM means if you are gonna say install OEM
thank you so much, and i know it has been asked a lot but am a bit disabled so don't mind my idiocey
any help would be much apreciated.
P.S. i already read the fix freeze thread and i got lost
ahassouna said:
first of all thank you for everyone on this forum for their remarkable work.
ok first i might be a noob but i have read every single thread and still i cannot get it straight. i'm not a electonic user freindly ...
Click to expand...
Click to collapse
If you have read this thread completely and still don't understand what to do, then you probably shouldn't mess with it.
Honestly...this is the nicest response you are going to get
bengalih said:
If you have read this thread completely and still don't understand what to do, then you probably shouldn't mess with it.
Honestly...this is the nicest response you are going to get
Click to expand...
Click to collapse
hence why i started with a thank you cause i know someone will eventually say something really bad lol
See SPL.zip in the attachment, which is the SPL from the latest RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship, unzip it then you get RUU_signed.nbh and CustomRUU.exe.
Copy the SSPL-KAIS.exe to your phone (if you had to use the White Screen fix you'll need jwocky2001's JumpSPL1.56-KAIS.exe).
Run SSPL-KAIS.exe from your phone (or JumpSPL1.56-KAIS.exe, depending on your situation).
The Bootloader tri-color screen should appear.
Check SPL version number: if it ends in ".JumpSPL" then everything is fine.
Unplug the USB cable and re-plug it.
Run CustomRUU.exe to flash SPL.
After it's finished verify your SPL by holding down power and camera buttons while doing a soft reset. It should be SPL-3.28.0000.
This is all at your own risk, good luck!
Use at your own Risk!
bengalih said:
So how do I change my SPL?
I would like to make a few amendments/comments to his instructions based on my experiences. The first is that I have found that you don't need to remove you SIM card, but you do need to remove your SD card. The second is that JumpSPL1.56-KAIS.exe will probably not work, so just use JumpSPL1.93-KAIS.exe instead.
Also, step 4 and 5 are very important. Once you have launched JumpSPL you will see, after a few seconds, "USB" appear on the bottom white of the bootloader screen. If it doesn't show then either your device is not plugged into your USB port OR your SD card is still in the device. Remember that once is displays "USB" you want to unplug your USB connection and then reconnect it a few seconds later. No message will display when you plug your USB back in, and ActiveSync will not start (if it does start you should worry!) so assume that everything is ok and continue on.
Using the above procedures you should be able to flash between different SPLs with ease. To summarize I will go through the procedure I use to quickly flash between SPLs. Remember to read the above links first so you understand the tools and basic procedures:
Get the SPL file (in .NBH format) that i want to flash along with the KaiserCustomRUU.exe and put it in a folder on my PC. (just unzip ATT_19213_SPL_3.29.0000.zip)
Plug my device into my PC
Copy JumpSPL1.93-KAIS.exe to your device.
Take out my SD card
Run JumpSPL1.93-KAIS.exe on your device (click on the exe)
Wait for the bootloader screen (tri color screen) to appear and "USB" to show.
Unplug my device from the USB port, wait 5 seconds, plug it back in.
Run KaiserCustomRUU.exe (on your PC) and flash the SPL (in the directory where you unzipped ATT_19213_SPL_3.29.0000.zip)
Your done
Click to expand...
Click to collapse
THese files if using the V3.5 death rom
Use ATT_19213_SPL_3.29.0000.zip for step 1 and 8
Use JumpSPL1.93-Kais.zip for step 3
All of this information can be found in the very informative thread by bengalih found here http://forum.xda-developers.com/showthread.php?t=396235
IT actually appears that you have your SPL already HardSPL'd if you have:
KAIS130 MFG
SPL1.0.olipof
CPLD-8
Therefore you only need to pick the SPL you want and flash it. Now if you want to either change the radio, rom, or spl in the future, you would need to re-do the HardSPL.
Want to make $20 thru paypal? help me get my Tilt out of the bootloader screen!
first off, im not new here; i lurked, learned, and flashed a few roms before i really posted much of anything.
my Tilts' screen was cracked a few days back, im headed to Greece in 2 days, so i went and bought a new Tilt to replace it until the replacement screen part gets here from Hong Kong.
The new Tilt came with WM6.1 installed, first thing i did is CID unlock it with HardSPL. i kept getting the white screen, but managed to bypass it, and flashed the RynCppr V4 on it with only the aforementioned white screen issue. I also have Ruu_Signed_Duttys_WM6.1_Official_5.2.19209_1_58_16_27 [FIX] ROM, but that would not install, i kept getting comm errors (ie the installation would never get past 0%).
I would like to run Ruu_Signed_Duttys_WM6.1_5.2.19700_Hybrid V2_1_65.14.06[CubeV2] as i've played around with it on a buddy's Tilt, but it too wont install past 0%; i NEVER had these problems at ALL on my old Tilt (WM6.0), it seems to be linked to the SPL, and hardSPL does not seem to be allowing me to flash anything but the RynCppr V4 ROM; im getting extremely torqued about this, please, any assistance would be appreciated.
Take a look at this post (it's in the Stickies). If you have the white screen then you need to use JumpSPL. Use 1.93.
http://forum.xda-developers.com/showthread.php?t=354061
Good luck.
ecltech said:
Take a look at this post (it's in the Stickies). If you have the white screen then you need to use JumpSPL. Use 1.93.
http://forum.xda-developers.com/showthread.php?t=354061
Good luck.
Click to expand...
Click to collapse
thanks, thats precisely how i bypassed the first white screen errors; the problem here is i can get into the bootloader, but it wont transfer and install the new ROM. i have to jump the SPL every time i want to attempt to flash a ROM. im down to about 4 hrs left of trying before i have to give up and get going lol.
You can't install a ROM using JumpSPL. Just HardSPL the device once you have run JumpSPL as per the instructions in the post and once it's HardSPLed you can install any ROM.
RynCppr worked because it's an AT&T base ROM.
use jumpspl to flash hardspl, then you can flash roms the normal way.
do not use jumpspl to flash a rom.
XtreMe_G said:
use jumpspl to flash hardspl, then you can flash roms the normal way.
do not use jumpspl to flash a rom.
Click to expand...
Click to collapse
it wont let me install HardSPL even with JumpSPL. now its stuck in the bootloader. im trying to get the OEM or the Cppr ROMS...
slade8525,
make sure you follow these steps exactly:
1a. download the 5 attached files
1b. pull out the battery and reinsert it (this step *is* important)
1c. connect your PC to phone with a USB cable
2. REMOVE SIM and SD CARDS !!
3. copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe
4. after a few seconds "USB" appears on the phone display
5. unplug and replug the usb cable
6. deselect "Allow USB connections" in Activesync connection settings
7. now flash hardSPL (run KaiserCustomRUU.exe from flash-hardSPL.zip on your PC)
Are you trying 1.93 or 1.56? I never had luck with 1.56 so try 1.93 if you're not.
Very important you do the steps as listed above. Any shortcuts and no go. When I was doing this on a Tilt I replaced, I kept forgetting to disable the USB connection from Active Sync and also unplug/replug the USB cable.
if anyone can walk me through getting it the HELL out of the bootloader or direct me to the correct ROM that WILL flash correctly, i'd be willing to paypal $20 ASAP.
ecltech said:
slade8525,
make sure you follow these steps exactly:
1a. download the 5 attached files
1b. pull out the battery and reinsert it (this step *is* important)
1c. connect your PC to phone with a USB cable
2. REMOVE SIM and SD CARDS !!
3. copy JumpSPL1.56-KAIS.exe to your device and run it (make sure the USB cable is still connected). If you still get a white screen then reset your device and now try JumpSPL1.93-KAIS.exe
4. after a few seconds "USB" appears on the phone display
5. unplug and replug the usb cable
6. deselect "Allow USB connections" in Activesync connection settings
7. now flash hardSPL (run KaiserCustomRUU.exe from flash-hardSPL.zip on your PC)
Are you trying 1.93 or 1.56? I never had luck with 1.56 so try 1.93 if you're not.
Very important you do the steps as listed above. Any shortcuts and no go. When I was doing this on a Tilt I replaced, I kept forgetting to disable the USB connection from Active Sync and also unplug/replug the USB cable.
Click to expand...
Click to collapse
well, i tried that method several times now, unfortunately im now stuck in the bootloader. here is precisely what the red/green/blue/white bootloader interface says...
top left RUUNBH
top right
KAIS1*0
SPL-1.93.0000
CPLD-8
bottom (in the white band) USB (if connected to PC) Serial (if not connected to PC)
i REALLY need this damn thing operational. flashing my 'older' launch Tilt was a piece of cake. if i try to flash HardSPL (through the PC ) it gets me to the command prompt where you hit Enter, i hit it, and nothing happens. i try to flash ANY ROM and it wont get past 0% and encounters a connection error.
Flash the WM6 factory ATT Rom (do all this crap while in wm6.0)
Go to bootloader mode & confirm HardSPL....if not there, HardSPL
Once done....do the security unlock (may as well do it with wm6.0)
Go to bootloader mode and confirm Security Unlock...if confirmed ***flash back the original Radio***
You should now be HardSPL'd and Security unlocked
Flash a wm6.1 Rom w/Radio (this will skip a flash)
You now have to flash one of the JumpSPL's....since you have a new device, flash the latest
Flash the HardSPL of your choice
Go to bootloader mode to confirm
DONE
Note: Have all you info available and files ready
When flashing SPL's, make sure your SD card is removed
Just went thru this just to get Security Unlocked because security unlock c/n be done with a 3.28 or 3.26 SPL and early on...HardSPL had to be done in wm6.0 and I had issues upgrading the SPL to 3.29 in wm6.0...that's why I say flash to 6.1 (say that twice)
you have bricked your device, for someone who claims to not be new, you should know better and flash hardspl before anything else.
if you want you can try this or just contact gsleon3
XtreMe_G said:
you have bricked your device, for someone who claims to not be new, you should know better and flash hardspl before anything else.
if you want you can try this or just contact gsleon3
Click to expand...
Click to collapse
actually ECLtech is walking me through it right now.
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?
So I got a little bit overzealous and accidentally flashed a gsm rom to my cdma phone (we all make mistakes) and now it just hangs at the Touch Pro2 splash screen. I can still enter the recovery mode but it does nothing when I run the recovery. Is there anything I can do? Any help is appreciated, thanks in advance.
-SeptimusX25
hold power and volume down and hit the reset button, keep holding power and vol down until you see the tricolor bootloader screen, from there you can connect to your computer and flash a new rom
I think we need to make a sticky pointing our what people have done wrong to make them think they have bricked their phone and then how to fix it, because there are a lot of posts saying potential bricking phones and it is the same fix everytime.
Well you may be about people knowing the definition of brick but the suggestion for installing a new rom does not work because even in the colored boot screen my computer does not detect that it is connected and hence I cannot reinstall a new rom. Is there a driver I need to install to get my phone to be detected sans operating system or some software i need to install? I have a feeling once my computer detects my phone it will be smooth sailing from there. Thanks again for your prompt replies.
when i plug mine in it automatically installs a driver (ive done this on multiple computers using multiple OSes) and the white bar at the bottom changes from saying Serial to saying USB, then i can flash a rom as normal
another way im not as familiar with but im sure with a little searching you can find help, would be flashing directly from the SD card, i did it once for a radio rom but dont recall the exact procedure, sorry
I tried flashing the phone from the sd card using this method:
"Step 1: find the rom/radio you wish to flash and download it
Step 2: extract the .nbh file out of said rom package (will usually be named RUU_SIGNED.nbh if the rom is packed in an exe use pocket rar to extract from your phone or 7zip/winrar from your pc)
Step 3: rename the .nbh file to RHODIMG.nbh
step 4: place rom on the root of your SD card (meaning not in any folders)
step 5: power down the device completely
step 6: hold volume down and power (sleep/wake button on the Verizon variant) till the screen boots into bootloader mode (red green blue screen)
step 7: when prompted press power to flash
step 8: wait for it to finish, sometimes it will restart on its own, sometime you need to restart it yourself but make sure you wait for the flash successful screen.
".
It gave me the same result as before. Also, Is it typical for the bootloader screen to only flash for a second and then get a grey screen that prompts you for action? Thats what my phone does, it shows a grey screen immediately after the bootscreen with 3 options which are: 1. "restore factory settings" 2. "Use custom configuration" and 3. "take no action and restart the phone" I tried both options 1and 2 with the sdcard method and got nothing. I also plugged my phone into my laptop and it installed microsoft usb sync driver but the mightyrom RUU, or any RUU for that matter, does not detect the phone, I get an error[264]: connection. Thanks for all the help, I really appreciate it.
If I can't fix it tonight, I'm taking it to the store tommorrow see if I can get it replaced
no, that shouldnt happen, it should stay at the red/green/blue screen, ive never seen the screen you describe
one thing you want to try is formatting your micro sd card to a fat32 then install the continue with the rest of the steps you described. i know this because i did the exact same thing you did. but now I'm typing from the same phone actually it happened a few times works everytime. i just know to triple check your rom to make sure its for your device. meaning gsm or cdma oh and dont forget to remove the sd card after the install and its best if the nbh is the only item on your card when you perform the flash.
@septimusx25 Thank you for posting this! I'm a noob and had the same problem with mine and thought it was a gonner. I was sweatin bullets! LoL
@sapperpipo Thanks for the SOLUTION! It worked perfectly and now I can use my baby again.
Ok. I've had problems up and down and tried and tried to do this and finally got it. So now I'm going to share it with all of you.
1. Download and Unzip the Files in the thread for the Ozone Verizon (HardSPL) posted by JockyW.
http://forum.xda-developers.com/showthread.php?t=551458
2. Connect your phone via ActiveSync, let it sync, and then start the auto.bat.
3. First, the JumpSPL will copy over. Press enter on the computer. Then the SSPL will copy over. Press Enter on the computer. Then it will prompt to start the JumpSPL. Press Enter. JumpSPL should pop up on your phone. Press the silver center button to start JumpSPL. The screen goes black. Then the DOS window will ask you if you have USB Connectivity. DO NOT PRESS ENTER YET!!!!
4. THIS IS VERY IMPORTANT!!! Wait for your phone to disconnect from ActiveSync. Once it does, unplug your phone from the USB. Go into ActiveSync's Connection Settings, and uncheck the box that says ALLOW USB CONNECTIONS. Reconnect your phone to the USB, and it should install the HTC USB Sync driver. NOW PRESS ENTER IN THE DOS WINDOW.
5. The RomUpdateUtility will start up, run it. And it should do the HardSPL on your phone. Your phone will restart when it's finished. If you want to check, before you do any of the above steps, copy the EnterBootloader.exe over to your phone. When you're done with the RomUpdateUtility and the phone has restarted, run the Bootloader and see what the tricolor screen says. It should be 0.39 Hard. Pull the battery, put it back in, restart the phone, and you should be good to go for flashing custom roms!
WOOHOO!
Thanks guys! I'll be donating soon. I'm about to flash the custom 3VO ROM right now! I'll let you know how it goes!
::EDIT:: The 3VO ROM is beautiful and runs like a charm! You guys put so much work into this.
Let it be known that this method for flashing the HardSPL can also be used for flashing the 3VO ROM.
NOTE: I WILL NOT TAKE RESPONSIBILITY FOR BRICKING YOUR PHONE.... seeing as I was scared I almost bricked mine once, and was VERY LUCKY that I did not. Please, follow all directions carefully. Phones are expensive.
ActiveSyn Doesn't disconnect
I got to the step where JumpSPL runs and my screen goes black. However, my phone never disconnects from ActiveSync. I tried unplugging it and disabling USB in activesync, but then my phone comes up as Not Recognized. If I try to run JumpSPL at this point I get, "Error (260): Connection." Any ideas?
How long are you waiting for ActiveSync to disconnect? It takes awhile. I know for me, it took about 5-10 minutes for it to disconnect.
Try waiting a little bit longer, and let us know what happens.
I waited long enough for activesync to stop. I unplugged my phone, disabled USB in activesync, and reconnected my phone. Every time I get a error saying "USB Device Not Recognized." If I try to run the update utility I get a connection error.
In all fairness I bricked my phone initially and had to recover it using a "stock" ROM someone posted for the CEDAR. My phone might just be hosed.
wm 6.5
quick question, the only way i was able to unbrick my phone was by upgrading it to the wm6.5 rom by Verzion, will the HardSPL work with this one?
I flashed the HardSPL on the Verizon 6.5 Update. So I guess the answer would be Yes.
I'm really lovin' this 3VO ROM. It's fast and the battery last a lot longer.
i tried your method and i'm still coming up with SPL-0.39.0000
i've tried other peoples guides as well and cant get it to hardspl, any ideas?
I followed all of these steps a few different times and my Bootloader still says .44. I tried varying the steps a little based on what users said on the thread about putting the HardSPL on the .39 and it still didn't help. I'm going to keep trying various configurations, but if anyone else is able to get their Official 6.5 ROM over to the 3VO, I'd love to hear how.
Thanks
what i need to know is what is hardspl i have an ozone that is unlocked but the data area is still locked to verizson and thats why i need to flash so i need to know what is hardspl and if its needed for an unlocked ozone
recoshaa said:
what i need to know is what is hardspl i have an ozone that is unlocked but the data area is still locked to verizson and thats why i need to flash so i need to know what is hardspl and if its needed for an unlocked ozone
Click to expand...
Click to collapse
You can find the hardspl definition here http://forum.xda-developers.com/wiki/index.php?title=Glossary
If you want to install a custom rom you will need to hardspl your device.
I hope that helps
I ran auto.bat, when the updater failed I disconnected USB from phone, reconnected, then ran updater manually and it all worked. Had to do this on both the HSPL and the ROM.
Also, make sure you don't uncompress both to same folder as it creates a .nbh file and if you have both on same folder you might be trying to install the ROM instead of the HSPL or vice-versa.
Another note. If you are HSPL already you can turn off device, turn it back on pressing DOWN VOLUME and POWER, leave both pressed until you get to rainbow screen, you can then run the updater and it won't bug you with battery being less than 1/2
I had problem that after screen goes blank, the phone will not connect. Some time "HTC USb Sync" will show, some time not. ROM Update will always complain that phone was not connected.
This is what I did to solve.
1. Power Off.
2. Hold vol dn and send with one hand. Then power with other hand.
3. Choose restore default configuration.
4. Let it boot
5. connect to ActiveSync.
6. Now run auto.bat
7. It runs fine and HArd SPL is loaded.
Enjoy.
schoenkn2 said:
quick question, the only way i was able to unbrick my phone was by upgrading it to the wm6.5 rom by Verzion, will the HardSPL work with this one?
Click to expand...
Click to collapse
Hi there, not sure if this belongs here. If you're planning on putting a custom ROM on the Verizon Ozone, do not use the HTC/Verizon wm6.5 update! "!! DO NOT !!" With the original stock wm6.1, you have a .39 Bootloader. After flashing the HTC/Verizon wm6.5 Stock Rom, you have a .44 Bootloader. And you can forget about putting a Custom/3rd Party ROMS. If somebody knows how to fix this, please tell me.
Thanks, and enjoy your HTC!
JD