Related
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:
RUUNBHKAIS 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....
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?
Please help.
I have the Verizon TP World Phone w/SIM card.
I downloaded the HARDSPL described as such: this package is for Rhodium CDMA-GSM worldphone version only (CDMA Touch Pro 2, not the original Touch Pro) devices. only RHOD400, RHOD500 modelids are accepted. this Hard-SPL supports WM6.5.
This process went successfully and I made it to the tri-color bootloader screen.
Next I ran this flashed this ROM NRGZ 21864, which appeared to complete successfully via PC, but when phone rebooted it just shows black w/Touch Pro 2 in middle of the screen.
Tried resetting, batter pull everything can't get anything to happen.
**Update: I was able to now get it into tri-color boot loader so what should I do with it now? It says SPL-1.00.Olinex, so its still unlocked. Should I just retry the rom again?
What did I do wrong? Is this phone dead? How do I get to bootloader? What should be my next step if phone is not dead.
Thank you!!!
Get a different rom that one didnt load or you could try reflashing doesnt seem as it took properly but no fears your phone is not bricked
Make sure you get a rom built for CDMA phones. this isnt the proper section for that goto RHODUIM CDMA
To Flash from the SD card, the .nbh file needs to be named "RHODIMG.nbh"
copy the .nbh file to a micro sd card, prefarably a 2gb or lower formatted as a FAT32
plug it in
get into the boot loader
i would recommend getting the stock ROM for your carrier and flashing that before moving to a custom ROM
hope that helps
ME TO
How do you get it to load in the bootloader menu ? Any luck with fixing it?
LECKEY73 said:
How do you get it to load in the bootloader menu ? Any luck with fixing it?
Click to expand...
Click to collapse
To enter the bootloader hold volume down and power (the red end key, not the sleep key on top) and press the stylus into the reset button. Once you see the tri-color screen you can release volume and power.
Same thing happened to me on my flash to that exact ROM. I guess sometimes it just doesn't flash correctly for some reason. No worries, enter bootloader mode and try flashing to MightyROM. After that, I was able to flash to whatever ROM I wanted. (But then I flashed back...MightyRom rules!!)
the spl 1.00 is fine. just go here it's for cdma phones only.
thanks everyone, got it back into bootloader via the challenging (hold both buttons and hit reset) Years of cosole gaming clearly paid off for those acrobatics.
Reflashed to original rom/radio, will put MightyRom back on..think I just needed to bump my head a bit, start over after some lessons and get this running better.
I had a StockSpl on my Htc touch pro and I wanted to flash an unsigned Hard-SPL from my MicroSD because I wasn't home and I didn't have the USB cable. After the screen loaded 100% the device restarted I took off the MicroSD and now it keep showing this tri-color screen:
RUUNBH
RAPH100
SPL-1.90.000
MicroP-Raph (LED) v13
MicroP-Raph (KEY) v5
PSOC-Raph STAGE_CVT v0x36
Upgrade ROM code error
Please try again
Serial.
(I've also attached a picture)
If i try to flash again from MicroSD the same HSPL it loads until 100% then restart and start to load again until i get the MicroSD card off. Or if i try to flash other StackSPL or any other ROM it stays on Loading on a grey screen.
After I went home I tried to flash the HSPL again from my computer using the USB cable, it start to load 0% then it does nothing. I've tried to flash StockSpl and other ROMs from the computer too but it does the same.
I think i've tried anything but nothing seems to work ... if someone can help me pls ... i've searched the entire forum and there's someone that had almost the same problem here: http://forum.xda-developers.com/showthread.php?t=566796
but noone had any solutions.
You can't flash hard spl off your sd card; it's got to be done through a usb cable.
Just read through the hard spl thread; it's long, but your situation has probably been addressed. I did it almost 3 years ago, so I don't remember the tricks. That's the case with most posters, I'm afraid. Just read the thread.
can u pls tell me which thread?
this one?: http://forum.xda-developers.com/showthread.php?t=410150
or this one?: http://forum.xda-developers.com/showthread.php?t=448008
Either, but read the first one. You can also look in the unlocker thread. Hell, you may just want to buy the unlocker and run that. It will flash hard spl, and the directions may be better.
I just hope they aren't trying to HSPL(hard SPL) a CDMA device :S I've made the mistake to assume the person that was posting in this forum had a GSM device and they really screwed up after a third attempt at flashing HSPL!
Usually if I have a difficult time flashing my Fuze or TP(both GSM), I remove everything to include the battery, connect the USB to an available USB port on the computer then hold the volume down key while connecting the device to the USB cable. Probably not the most friendly way but it certainly will tell you if there is a problem with your USB port/cable or even device!
My htc raphael is GSM
I've tried to hold the volume down button but it's always the same
There's no problem with the cable just that I can't flash anything because I'm stuck with a stock-spl and I can't flash a hard-spl either. When I try to flash something from the computer it starts to flashing with 0% then nothing happends until the RUU gives me the 262 Error. And when i try to flash from my mSD it just stuck with a Loading screen.
Xadow said:
I had a StockSpl on my Htc touch pro and I wanted to flash an unsigned Hard-SPL from my MicroSD because I wasn't home and I didn't have the USB cable. After the screen loaded 100% the device restarted I took off the MicroSD and now it keep showing this tri-color screen:
RUUNBH
RAPH100
SPL-1.90.000
MicroP-Raph (LED) v13
MicroP-Raph (KEY) v5
PSOC-Raph STAGE_CVT v0x36
Upgrade ROM code error
Please try again
Serial.
(I've also attached a picture)
If i try to flash again from MicroSD the same HSPL it loads until 100% then restart and start to load again until i get the MicroSD card off. Or if i try to flash other StackSPL or any other ROM it stays on Loading on a grey screen.
After I went home I tried to flash the HSPL again from my computer using the USB cable, it start to load 0% then it does nothing. I've tried to flash StockSpl and other ROMs from the computer too but it does the same.
I think i've tried anything but nothing seems to work ... if someone can help me pls ... i've searched the entire forum and there's someone that had almost the same problem here: http://forum.xda-developers.com/showthread.php?t=566796
but noone had any solutions.
Click to expand...
Click to collapse
Naughty Naughty..
I guess you realise now that you should ALWAYS read read read before modifying your phone in any way.
What EXACT file did you originally flash to your phone via microsd card and where did you get it from?
If you go into the bootloader screen and then connect the usb cable does it show "usb" at the bottom of the screen?
PLEASE STOP TRYING TO FLASH HARDSPL FROM MICROSD AS YOU CANT DO IT. If you could then it would be in my guide..
Mark.
mskip said:
Naughty Naughty..
I guess you realise now that you should ALWAYS read read read before modifying your phone in any way.
What EXACT file did you originally flash to your phone via microsd card and where did you get it from?
If you go into the bootloader screen and then connect the usb cable does it show "usb" at the bottom of the screen?
PLEASE STOP TRYING TO FLASH HARDSPL FROM MICROSD AS YOU CANT DO IT. If you could then it would be in my guide..
Mark.
Click to expand...
Click to collapse
Thanks for replying
Yes ... I did read the part with the SD flashing but i thought it's not a bit deal to flash from mSD since the flashing via activesync is so easy.
Well ... i extracted the RUU_Signed.nbh from the Hard-SPL found HERE and i copied it to the mSD (MicroSD) and renamed it RAPHIMG.nbh.
I restarted my phone holding the volume down button and it started to load until 100% then it restarted and showed the bootloader screen and after a couple of seconds start to flash the HSPL again so after it completed 2 or 3 times of flashing and restarted i took the battery and the mSD off (I DIDN'T TOOK THE BATTERY WHILE IT WAS IN THE PROCESS OF FLASHING). And when i started the phone again without mSD it showed the bootloader screen like it was waiting to get a .nbh file on mSD to start flashing again.
No matter what i do my phone start in bootloader and down it shows "Serial". If i connect the usb it shows "USB".
I tryed to do a hard reset and it seem to work but after it finish and the phone restarts is stuck with the same tri-colour screen.
Sry for trouble and thx again
I guess I missed the part in the OP where you said it was stuck in bootloader. That's not good. I would try flashing the stock raphael rom (assuming you have it). Have you tried that? I dunno, you may be stuck for good.
Xadow said:
Thanks for replying
Yes ... I did read the part with the SD flashing but i thought it's not a bit deal to flash from mSD since the flashing via activesync is so easy.
Well ... i extracted the RUU_Signed.nbh from the Hard-SPL found HERE and i copied it to the mSD (MicroSD) and renamed it RAPHIMG.nbh.
I restarted my phone holding the volume down button and it started to load until 100% then it restarted and showed the bootloader screen and after a couple of seconds start to flash the HSPL again so after it completed 2 or 3 times of flashing and restarted i took the battery and the mSD off (I DIDN'T TOOK THE BATTERY WHILE IT WAS IN THE PROCESS OF FLASHING). And when i started the phone again without mSD it showed the bootloader screen like it was waiting to get a .nbh file on mSD to start flashing again.
No matter what i do my phone start in bootloader and down it shows "Serial". If i connect the usb it shows "USB".
I tryed to do a hard reset and it seem to work but after it finish and the phone restarts is stuck with the same tri-colour screen.
Sry for trouble and thx again
Click to expand...
Click to collapse
As Farmer Ted said your best bet now is to download your ORIGINAL Rom (from your provider) and flash it from your pc with the usb cable attached. The phone had to be in SSPL mode before running the RUU which is why everything was packed in a single exe. You may have corrupted your SPL in which case you have bricked your phone but if you can manage to flash a Stock Rom then the Stock SPL should be reflashed and you can start again with the HardSPL by following the CORRECT instructions and not making up your own lol.
Good luck.
Mark.
When i bought my phone, the first thing i did was to dump the rom. So now i rebuild it from raw and tried to flash but it didn't work so i went to Orange site and i downloaded the official ROM then started to flash and ... IT WORKS
I think that the ROM was corrupted not the SPL, and since the SPL was stock it didn't allow me to flash other ROMs other then the official
Thanks for all guys I couldn't done this without your help
P.S: why did it allowed me to flash the official rom but the hspl not?
It didn't flash the hard spl because you did it all wrong; those rebuilt roms aren't exactly the same as the stock roms, so it's not surprising that wouldn't flash. Good job finding the original shipped one, though.
Now, just read mskip's instructions and you should be good to go. I think the trick is just to enter bootloader, then connect to your pc through the usb cable.