Thanks to WMExperts who announced the 'official' Verizon rom.
Anyone sitting with a bricked Ozone patiently waiting for an official, signed, rom....here's how your long-bricked Ozone comes back to life:
- Get a hold of the 'Official' WinMO 6.5 Shipped Ozone ROM.
- Remove the SD card and SIM card if one is inserted in the phone.
- Unplug & remove the battery from your phone for a few seconds; Ookba found this step to be essential to reset the device. Put the battery back in.
- While holding volume down button, press the power button. NOTE: The D-PAD is not Volume Control. Utilization of the D-Pad in this operation will result is user failure.
- The phone will enter "bootloader" mode and you will see a tricolor bootscreen.
- While in this mode, plug in your USB cable and wait until you hear the "ba-bing" USB sounds as the device connects.
- Extract 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.
Thanks Ookba for the instructions!
0 ram free?
So i flashed my phone to the signed 6.5 rom, and now the phone boots but i have 0mb free on my phone. I have tried to delete some files, to no avail, as well as doing a hard reset. I tried to flash it again and no change. I am not sure what went wrong, any ideas?
schoenkn6 said:
So i flashed my phone to the signed 6.5 rom, and now the phone boots but i have 0mb free on my phone. I have tried to delete some files, to no avail, as well as doing a hard reset. I tried to flash it again and no change. I am not sure what went wrong, any ideas?
Click to expand...
Click to collapse
Maybe try a soft reset? I just did it and I have 18mb in storage and 64mb free in available memeory.
nope, no change
one more peice of info, it thinks it only has a 10mb drive
schoenkn6 said:
So i flashed my phone to the signed 6.5 rom, and now the phone boots but i have 0mb free on my phone. I have tried to delete some files, to no avail, as well as doing a hard reset. I tried to flash it again and no change. I am not sure what went wrong, any ideas?
Click to expand...
Click to collapse
same problem here ...
cheers
I'm noticing the same thing now. Hmmm. I'll have more of a look tonight. I'd really like to jailbreak it and put anonther ROM on it regardless.
I'll let you know my progress.
Glad I haven't flashed it yet, then...thanks for the heads up. Think I'll stay with the new 3VO ROM until further notice...
I noticed that problem with the 3V0 ROM on one phone but not on another... Seems there is something different in the versions that are out there. My guess is that if you did the 3V0 and didn't see a memory problem you wont with this one. Maybe that is why Verizon is holding back...
I know the problem must lie with the nbh file being 125 MB in size... If you looked at the 3vo roms they all are around 80-90 mb per NBH file, which leaves you with at least 30 megs of free storage. Perhaps they just need to shrink the rom or remove the 0 bytes or something.
I am stuck in the same boat 0Megs free so I can't do anything with the phone. If I try to reload custom 6.5 from bootloader it sticks at 0%. What can we do to get our phones back?
Verizon officially released the 6.5 rom today. From everything I can tell it is the same rom as the unofficially released rom last week.
I'm going to see if it has the same memory leak as the other one.
No change, I installed the new rom and still no memory.
Count me in also, have the memory problem and cant flash withanything but the original 6.5 signed rom...
Has anyone contacted either VZW or HTC regarding this issue? My Ozone is on PagePlus right now, but i am going to see if I can go into VZW and get it replaced if this is not fixed in a few days lol.
I wish I could reproduce this problem on my Ozone so I can help you guys troubleshoot it.
It might have to do with the Bootloader and new SPL version. I will try to cook the OS portion into an NBH and see if the problem persists. You will need to HardSPL to flash it though. Anyone willing to try it and see if it fixes the memory issue?
I'd be willing to try, how do I know if I have a hardSPL though. I'm not a newbie to flashing but I have always followed directions and never had a problem.
Edit: When I start the phone using the power and volume button I have
CEDA100
SPL-0.44.0000
MicroP-Cedar#W (LED) v58B
After doing some research I don't see how to get a hardSPL if I am not able to get it run anything unless its already installed
Burn242 said:
After doing some research I don't see how to get a hardSPL if I am not able to get it run anything unless its already installed
Click to expand...
Click to collapse
Yeah I can't HardSPL due to there not being any free memory on the phone. Is there a way to cook the stock rom and remove some of the un necessary files and still be able to flash it without hardspl? That would be our savior as we would not need that much room to run hardspl after we get the stock rom running.
Same exact response here, Burn...
JC
PS Have one working Ozone up on "official" 6.5, but have been having signal issues, i.e. dropped calls, no calls received, etc...
Related
I ran it according to farias instructions I thought. It flashed but now I cant install anything and I cannot write to the storage card or the phone, any cab i try to install is unsuccessful and I cannot save any files to the storage card or the phones memory.
And it appears that I cannot flash the rom again. Am I screwed?
What is you IPL / SPL? IS your phone a G3 or G4? Can you get to the bootloader? (turn off your phone (pull the battery if you have to) then hold the camera key down while you turn it on). You can flash directly to the bootloader (even though activesync won't connect.
BTW: If this stuff makes you nervous, you probably shouldn't be cooking... Your phone will do all sorts of weird stuff when you screw up a build. And you should really know how to recover from most things that can happen...
I have done this before, this is the first time I have ever had a problem. my IPL/SPL is 2.26. And the phone is unlocked.
beowolf said:
I have done this before, this is the first time I have ever had a problem. my IPL/SPL is 2.26. And the phone is unlocked.
Click to expand...
Click to collapse
ok, cool... wasn't sure... So can you get to the bootloader?
yes I can get to it
I am flashing back to the t-mobile 2.26 rom. Working so far, I will leave the cooking alone. Can you recommend a good wm6 rom that doesnt have any problems?
"doesn't have problems" is the catch
I'm partial to my own Crossbow Reloaded ones, but they aren't perfect. If you don't hit the keypad issue with 1.7 though, its pretty close
Core 2.0n is very good and nice and clean.
Also NBD and Wizard Mobile 6 are both supposed to work well.
The new "official" rom we are playing with is beta, but I have to say its really fast and we aren't seeing much wrong with it (but its only been 12 hours since its been released). There are a couple of issues that are fixed with cabs (CommManager for one).
As for cooking, you probably eith had something wrong in a .rgu or somesuch. Just takes a number of builds and flashes to get it right to where it boots (then you debug what you forgot in packages and start over )
Well I guess I bricked mine ulness someone knows something I don't. I was doing a flash, running nothing else and XP did a memory dump and blue screen of death while 8125 was 54% done. Guess I have a paperweight now.
I am sure I'll get flamed for my post but thank God the Cingular ROM doesn't need an actual Active Sync connection. As long as you are in RBG bootloader screen and the USB comes on when you plug into the PPC, the factory ROM can repair the unit.
Possible Reviving Techniques For (appeared to be) bricked Wizard
See the following link and read, read, read.
http://wiki.xda-developers.com/index.php?pagename=HTC_Wizard
Very good I do remember reading that post from when I first joined here, guess I just panicked. I must mention however that none of the WM6 ROMS i have would flash only the stock one would.
When you have a bad flash you ALWAYS should go back to an official rom. This will guarentee that you get back to a complete IPL/SPL and Extended ROM. If a flash goes bad, any (and all of them) could be corrupted and flashing a custom rom won't help (since most all of the custom roms don't include any of those pieces).
n3rxs said:
Well I guess I bricked mine ulness someone knows something I don't. I was doing a flash, running nothing else and XP did a memory dump and blue screen of death while 8125 was 54% done. Guess I have a paperweight now.
Click to expand...
Click to collapse
Reboot your pc....
Your device should be in bootloader mode still
Connect and flash the same ROM....it should pick up right where it left off
If this doesn't work, flash your factory rom
As long as your device powers up....it's not bricked
The same thing happened to me once on my wife's laptop
Yeah this was on my company laptop. I was flashing Faria's RealThing for the 1 hundredth time.
I have been searching all over for this but it's probaly right in front of my face. I read that you need to get rid of SPL.nbh from official ROMS before flashing back with HardSPL. The problem is, the official T-Mobile Wing ROM that I downloaded is an .exe file. How do I go about removing the SPL.nbh file since it doesn't display folder contents or anything, just runs the RUU?
Sorry for the double post, I realized I was in the wrong forum
flipside123 said:
I have been searching all over for this but it's probaly right in front of my face. I read that you need to get rid of SPL.nbh from official ROMS before flashing back with HardSPL. The problem is, the official T-Mobile Wing ROM that I downloaded is an .exe file. How do I go about removing the SPL.nbh file since it doesn't display folder contents or anything, just runs the RUU?
Sorry for the double post, I realized I was in the wrong forum
Click to expand...
Click to collapse
I'm uploading a zip file which will have the entire thing already to go.
Just flash your device as you would with any other rom.
Hang tight the link will be available within 10 mins.
Thank you sir. Greatly appreciated
flipside123 said:
Thank you sir. Greatly appreciated
Click to expand...
Click to collapse
Done:
Remove HARD-SPL On The Wing
This is the same tool used to flash your device when it was not HARD-SPL.
I replaced the RUU_Signed file and SPL.nh file already.
It will bring your wing back to the stanard rom as when you first got it.
One more question. I'm looking to keep HardSPL but I have to revert to original to upgrade ROMS don't I? I want to upgrade to your OT 6.5 ROM
flipside123 said:
One more question. I'm looking to keep HardSPL but I have to revert to original to upgrade ROMS don't I? I want to upgrade to your OT 6.5 ROM
Click to expand...
Click to collapse
Okay,
I thought you wanted to go back to the original T-Mobile rom.
If your trying to HARD-SPL your device to install one of my roms or another cooks roms then thats another story.
Please read my FAQ or one of the stickies.
Ok, I think I got it now. So I don't need to revert to the original ROM to flash it since I have HardSPL? Thanks for the help
wen i did this i think i bricked my fone now its at the tmobile screen and it jus staying there
I tried the file that you uploaded here...And it went thru the whole process of flashing the ROM, but after it updated my wing just stays on the T-Mobiel screen and never boots past that.
It had that open touch software on it and I don't want open touch. I want plan old WM 6.0 on there.
I called T-Mobile and got an offical 6.0 update from them, but when I try that one it gets to 1% then says it has a disconneted and I get a connection error.
ttran001 said:
Done:
Remove HARD-SPL On The Wing
This is the same tool used to flash your device when it was not HARD-SPL.
I replaced the RUU_Signed file and SPL.nh file already.
It will bring your wing back to the stanard rom as when you first got it.
Click to expand...
Click to collapse
So does this work? The two people who did this had problems. I need the phone to be all stock so I can have t-mobile send a free replacement because the screen is going on this wing.
***EDIT:*** Oka so this is the same as http://forum.xda-developers.com/showthread.php?t=364543&page=2 the first time I tried it it froze at 15% on step 2 so I installed the RAPI CAB like it says. Step two completed, phone rebooted and had white screen then I got error 260 I think. I have the stock t-mobile rom on it and had it on before I did this but it still has the yang from when I did a hard spl. Is there another way to get it to stock or am I doing something wrong? Plug in phone, let it sync, run herald-uspl.exe hit enter and so forth.
***EDIT*** Ok so this time it completed but is now stuck at the T-Mobile screen and I am now unable to even flash because I can't get past it And that damn yang still shows up in bootloader. Well went into bootloader and flashed from there so phone works but the damn yang is still there. And on a side note: Has anyone ever had a problem with their screen going very dark after flashing a rom from here? Phone was fine then I flashed OTP v7.4 TouchFlo 2D Lite.nbh yesterday and at night screen started going dark, would light up when opened in keyboard mode, then switched and then both were very dark and hard to see. I then flashed to OTP v7.3.1 TouchFlo 2D Final.nbh and still dark. Then I flashed to stock rom and have been able to see the screen since.
This is stupid easy to do... im shocked there isnt a post going into detail.
5 steps to going back.
http://forum.xda-developers.com/showpost.php?p=2998657&postcount=4
smokeingit said:
This is stupid easy to do... im shocked there isnt a post going into detail.
5 steps to going back.
http://forum.xda-developers.com/showpost.php?p=2998657&postcount=4
Click to expand...
Click to collapse
Did not work. Do I need to install the cab files again? I know I deleted a file out of the stock rom so it would not overwrite or verify or something but I put that file back, should I not have? This has been a few weeks and still can't get the yang off. Screen on my girls phone is almost dead, she can't even slide it any more so I need to fix the spl so I can send back to t-mobile....anyone ?
this is what i do to get back to the tmobile orginal. download the software from tmobile. I downloaded the newest update from tmobile site. REMOVE YOUR SD CARD. Connected my phone via usb. Launched the update. It has never failed me yet. It is just like updating your phone. tmobile has to take it, it is their update. They sent me a new phone noproblem, matter of fact i have to do it again, the back on the phone keeps getting loose on me. so they are sending me another phone again. hope this helps.
Alternatively you can use the combination of uspl and stock rom ruu to return your device to stock tmobile rom...
1. Enter in to uspl like you were falshing one of ttran001 roms... You can get this HERALD-USPL-beta3 from http://rapidshare.com/files/79249048/Flash_Center.rar
2. ONLY use steps 1 and 2 from the black screen (getting the white screen on your device)...
3. For step 3 in the flasher exit out of the black screen (windows cmd screen) by pressing ctrl+C...
4. Fire up the official ruu from tmobile found here http://forum.xda-developers.com/showthread.php?t=358030 or alternatively if you have a tmobile account still active you can get the most up to date rom from http://www.t-mobile.com/wmupgrade/
5. Fallow on screen instructions...
6. Back to stock rom...
Brick dopod C858
ttran001 said:
Done:
Remove HARD-SPL On The Wing
This is the same tool used to flash your device when it was not HARD-SPL.
I replaced the RUU_Signed file and SPL.nh file already.
It will bring your wing back to the stanard rom as when you first got it.
Click to expand...
Click to collapse
Hello freind,
I have been downloaded the above "Remove_HARD-SPL_On_The_Wing.rar" files and flash it to my Dopod C858 which has the Chiness language, I suppose to change the language from chinesse to Englis, After flashing the above files, now the phone is only in bootloader mode.
If you start the phone it will stuck on white screen and turn off.
Please help me how to revive my phone back.
Thanks and best regards
Jhemzz
Hey I'm having the same problem as most of these guys who tried the file. The phone just idles on the white Tmobile screen... does anyone know what to do or how to help?
Please and thank you!
angest90 said:
wen i did this i think i bricked my fone now its at the tmobile screen and it jus staying there
Click to expand...
Click to collapse
im having the same problem can anyone help me please?
hotsammysliz said:
im having the same problem can anyone help me please?
Click to expand...
Click to collapse
Being stuck at the Tmobile screen isn't a true brick. Just reflash your ROM. (If you're not HardSPL'd, reflash your RUU.)
Remove Hard SPL from bootloader
Hi,
Anyone out there knows if we can remove hardspl from bootloader of Wing. Problem is my mobile displays splash screen, then switch offs by itself. Its been quite some time that I have hardspled it and have been using it. But recently I am facing this issue, so I am trying to move to original RUU and try if it works.
So for that anyone knows if we can remove hardspl from bootloader, because I am only able to enter bootloader. Moreover I tried several original roms from Flash Center as well as through SD card as well, but still be SPL version is 4.70.yang. Anyone knows any other alternative.
Also, if anyone has faced similar problem then kindly advice how you resolved.
Thanks in advance!
Regards,
Pankaj
Hey GUys,
I'm not new to flashing and roms and all that jazz. Had the random stuck in bootloader that wouldn't resolve itself today (using 3.29) Loaded kaisdiagsd.nbh and flashed stock att rom. (probably should have gone right for the spl patch but I was frustrated and needed my phone) Boot loader is now v3.65
Flashed rine, reboot, same issue. Phone will now only load the stock 6.1 att rom from the micro sd. kaisdiagsd.nbh is stuck on loading as for all other roms. I can occassionally get the os to load using mtty. From there tried jumpspl and it would not connect via usb at all.
When in the stock 6.1 os I get the old unrecognized usb device in both xp and vista.
Is there anything else I can do to reflash spl? All i can think of is trying the task 2a, wiping everything and trying to flash from diag but I don't even want to try that route without something solid in place.
The phone is 2 years old, upgrading when the touch pro 2 hits att in aug sept or whenever, but I need my phone.
I have gone through many many many posts. I'm stuck. Any help would be appreciated.
Is there anything else I can do to flash a n
Have you tried to flash the SPL from the SD card? Worth a shot if not.
thanks for getting back, i have tried..multiple. It will just sit on loading as for everything except that damn att rom. i've been going at this for hours and hours. just to make sure, the spl flash will still be named KAISIMG.nbh correct? or has my frustration gotten to me
Yes but make sure you dont put the .nbh. Just kaisimg or it will be kaisimg.nbh.nbh and wont work
haha, yeap. i'm an i.t guy so i have file extensions showing by default so thats golden
I have the stock att rom up and running so the phone is functional, but that said, its the ****y att rom and I'd really like to change that asap., I'm just tired and fed up at this point really
Also for flashing SPL from SD card you need kaisdiag.nbh. Place it on the SD too. I should have told you that first. Its in my 4shared if you dont have it.
just tried it. it is stuck on the loading screen....
Try reading from here: http://forum.xda-developers.com/showthread.php?t=433835
Ta
Dave
First of all please be gentle! I am a complete novice and this is my first post. I have a Touch Pro on a Vodafone contract. I downloaded the recent ROM software upgrade from the Vodafone web site and began the transfer to my phone having followed all the advice. However, the download got stuck at 12% and no matter how many times I start over again it will not go past that point. Worst still the phone is now locked on a red/green/blue/white screen with the message "Upgrade ROM code error Please try again". the error message on the Vodafone software download is No 302. I have tried Vodafone technical help but as I was due for a new phone anyway they have sent me a Touch Pro 2 but don't seem to want to help me resolving the problem with my "old" phone. It is only 5 months old (replacement insurance phone) and in good condition but useless if it can't be made to work.
Can anyone help with simple instructions on how to download a ROM that will work. If not does anyone want to make me an offer for the phone? Currently locked on Vodafone but I am sure you guys out there have the skill to resolve that one.
Many thanks,
Hollybeau
So, they aren't asking you to send it back, I take it? If that's the case, then the first thing I would try would be to flash with the stock rom, if you can find it (not the upgrade that quit on you). If that doesn't work, then just try to flash hard spl. If hard spl goes through ok, you're golden and can flash any raphael rom you want. If it doesn't, the phone is probably toast. You got a new one, so just use the old one as artwork.
Thanks Farmer Ted,
Unfortunately I do not know the orginal stock ROM. It is not on the Vodafone web site and the HTC site keeps telling me that all the likely candidates are "not suitable" ( I assume this is beacuse it is some sort of Vodafone variant). I am afraid that "flash hardspl" means nothing to me - I told you I was a novice! Can you direct me to what and where please.
What bugs me is that here is a phone worth £200? but for a problem caused by Vodafone's buggy software upgrade.
Hollybeau
Start Here.
Best way to find everything you want to know about flashing ROMs.
Lol.
Hard SPL is a bootloader that allows you to flash any rom you want (not just vodaphone). It also has over-write protection, so if you get into the situation you're currently in, the phone won't be bricked. If you can flash it (make sure you flash the gsm version in the raph rom forum), you are fine and dandy.
If you can't find the stock rom online, you may be able to flash the upgraded rom off of your sd card (I believe this will work with a stock rom and stock spl, but am not 100% sure). Re-name the .nbh image file to RAPHIMG.nbh. Format your sd card (1-2 gb works best) to FAT32, and put the image on the root of the card. Go into bootloader (well, you're already there, you may not need to) by holding volume down and soft resetting. Hold vol. down until the tri-color screen appears. At the prompt, press the power button, and let the flash run its course. Soft reset when it says that the update was a success. Let the phone boot up until it gets to the the alignment screen, the hard reset and boot it up.
If you don't have an .nbh file, and instead have a .exe file from vodaphone/htc, then you should be able to extract the contents with either winrar or 7-zip (google) to get at the .nbh image file. I've done this before, and it works fine.
Many thanks to all who have replied. I have fixed the problem. It turns out that it was the download to my PC that was at fault. I downloaded the Vodafone software to my lap top and ran it from there and it has recovered the phone. I now have a spare, and working, Touch Pro. I may try the HardSPL and other ROMS just to use the phone as a test bed. Alternatively, anyone out there want to make me an offer?
Hollybeau
Hollybeau said:
Alternatively, anyone out there want to make me an offer?
Click to expand...
Click to collapse
Ask in market place and you will probably get some takers