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
Related
Hi all,
Have purchased a German MDA_C and flashed it to the latest dutch WWE rom (1.13). I use the NOID updater and get an error message at 99% of the update.
After this my MDA hangs at the splash screen (but showing updated rom and radio versions).
Doing a lot of soft and hard resets I managed to get by the splash screen 1 time...
Tried a lot of different rom versions but each time I get the same problem
I've read that the SPLASH screen problem is more or less common but I wasn't able to find a solution on the forum.
Now I made one stupid mistake... I did not backup the original rom...
Any suggestions how to get up and running?
Thanks in advance...
BuDDaH
The very first boot takes a long time, 15 mins for some! If you're not waiting for around 15 mins ....
Thanks for this valuable information kta.
This time I waited 1 hour after upgrading just to be sure.
same result. flashing stops at 99% of the CE Rom.
Hard reset shows splash screen with version numbers (radio 1.13 rom 1.13 wwe) and then just hangs.
From bad to worse
So I had a MDA_C that did not boot further than the splash screen.
Updated using the MaUpgradeUt_noID.exe. Thought I'd give the SD way a try since I already tried about 6 different roms all with the same result.
First I made a backup to SD card of what was in my MDA using romupdate.exe
extracted the file to my HD.
After extracting (and securing the device ID) I tried rebooting my MDA.
Now things got worse!!! instead of the splashscreen I now have the BLACK SCREEN......
Have tried resetting and hard resetting dozens of times (more like a thousand times) and only occasionaly the splash screen comes up. :roll:
But over the last couple of days I only managed to get the bootloader 1 time (and at that time there was no SD card inside) :shock:
this is behaviour I haven't read about on the forum.
Guess I will have to get it serviced.
Is there anyone on the board that has an address in the Netherlands that can flash or repair my mda? Not sure T-Mobile NL services German devices...
Thanks!
Not dead yet?
Here's some more info.
My 'almost dead' Magician is showing signs of life.
I had the BLACK SCREEN.... (first couple of lines of pixels were not black)
After thousands of hard and soft resets (soft resets seemed to have the best results) I managed to get into the bootloader!! Flashed with an older rom and at least I'm getting the splash screen again. (but still getting an error at 99% of update of the CE rom).
I'm updating using the exe in bootloader mode btw....
Since there's always an error at 99% when I use the exe method and the device is not booting I thought about giving the SD method a shot.
My device didn's show the SD option but fortunately tadzio explained about the MBR (didn't even know a SD card had one!!! :lol:
http://forum.xda-developers.com/viewtopic.php?t=32849
When I decode a nbf file using nbfdec.exe and flashing afterwards I get a message that my ROM is to small.
Size is same as nbf file.
How do I correctly decode a nbf file?
Thanks for the help.
BuDDaH
Don't use a nbf, get a dumped or bs rom from the ftp & follow instructions with copying bytes etc.
M
Ok OLTP I'll skip the nbf decoding route.
Think one of the problems is the way the newer roms are encoded.....
Saw you're using a 1.13 bigstorage rom?
That one is not on the ftp is it?
Modified your own rom image?
Hi BuDDaH,
I downloaded at the Dutch TMO site the shipped-rom, unzipped the exe file & decoded the nk.nbf nbfdec. In this nk.nb1 I altered the usual BS bit patterns and re-encoded the nk.nb1, again with nbfdec, to the nk.nbf. After that it was just running, the extracted, upgrade program & it worked like the usual shipped-rom upgrade. you might have to use the maupgrade_noid version, sometimes twice.
This method is better described in the thread about upgrading to radio 1.13 which you can add along the road as well.
So yes I made it myself, not so fond of using other people's rom unless I have to. Please don't let anyone be offended by this, cause a replaced bit can cause serious harm, like I encountered myself, with my own corrupted rom-dump.
Good luck, M
Just wanted to update you all on the latest status.
I managed to flash a german rom (as I've got a German device) although I always get an error message at 99%.....
Fist it just stuck on the splash screen but this somehow deteriorated. Now I get a black screen covering about 5/6th of the screen. the first 1/6th shows a part of the splash screen. No backlight and it hangs.
No more bootloader so I need to have it serviced (anybody knows what the techies do with such a device?)....
Now the question remains where.
T-Mobile NL refuses to service it since the IMEI is unknown to their system
T-mobile Germany doesn't have a service center but only takes repairs through a T-Punkt shop..
Any ideas?
Thanks,
BuDDaH
Latest update...
I sent it in for repair and it turns out that the ROM is damaged and the phone needs a mainboard replacement..... which costs about the same as a new unit...
Anyone got a spare one laying around for me?
So much for my Magician!
Cheers,
BuDDaH....
Sorry to hear...did you try another SD card?
Yep I did; but unfotunately the situation deteriorated and I'm completely unable to get into bootloader mode.....
Well.. :idea: maybe I must see this as a great opportunity to get wild with a set of scewdrivers
Hey BuddaH,
There enough people interested in the parts here at the forum, so there's a tiny brightside on your adventure :-(, man i do feel sorry for you.
Regards, M
Yup, i need some parts also
BuDDaH said:
Yep I did; but unfotunately the situation deteriorated and I'm completely unable to get into bootloader mode.....
Well.. :idea: maybe I must see this as a great opportunity to get wild with a set of scewdrivers
Click to expand...
Click to collapse
You probably ran the battery down. I don't think it charges unless the ROM is working. That is why it is highly recommended that you start with a full charge before commencing a ROM update.
Hi Stevedebbi,
Even in my situation the it still seemed possible to charge the battery (at least the red light went out and the battery got hot).
Sent my device to apexlaptops.co.uk cause they claimed they reflash...
Got the reply back that they couldn't get it too bootloader mode and were unable to repair. (guess they could not do some JTAG debugging).
I may be able to buy a working device that's damaged on the outside....
Hi there,
My currently installed Rom was RUU-Prophet-G4-AKU2.2-2.20-2.47.21-Jester-r1.exe. (thank you jester for you good job)
Nevertheless, this ROM is in English and I wanted to downgrade to a French One before the selling of my device.
I have tried to install the downgrade kit detailed in this topic : http://forum.xda-developers.com/showthread.php?t=267344
The first step went OK but while trying to make the secnd step, my qtek is blocked at the boot splash screen showing the Jesterz picture and red information about the SPL and so on on the upper left corner... without starting... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Don't worry, its nowhere close to being dead. If you have superCid, then use the SD card image to restore in bootloader mode. However, if the Cid is locked, then you would need a utility that can unlock Cid without Activesync mode (coz in your case, you would not be able to get an Activesync connection). imei-check.co.uk has a utility ($38 i guess) that unlocks Cid in bootloader.--- else show it to a professional. (in my country, I would have to shell out around $20 to get such a problem fixed at a mobile repair shop)
illanz said:
... The USB connexion is not detected so I can't do anything... While trying to install any ROM, the USB connection is not detected ang I get an error message...
Did I kill my phone ?
Please help ! Tell me that it's not dead....
Click to expand...
Click to collapse
Just take out the battery for about 10 minutes and re-insert. If it does not re-start, do a soft resert with the stylus and hopefully you should be fine
Hy,please help!
after downgrade, it doesnt work anymore.... i mean... i cant start the mobile!
after the downgrade i disable the USB data cable and now the mobile is dead... it doesnt starts from the ON/OFF Button and even if i connect the USB cable it makes nothing! No Led on... nothing! absolutly DEAD!!!
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Try this in order to reach the bootloader:
Hold down the camera button and reset the device. (Boot Loader Mode is: Press Camara + Soft Reset, then release soft reset and KEEP PRESSING camara button till appear the Boot Loader.)
it doesnt work
I seem to have a simular problem. this is my post in another topic. It seems to fit better here.
This is what I tired so far:....
I used the RUU_Prophet_2151327_21513121_021921_DOP_ASIA_WWE_S hip-NoVendorID and it often hangs and was slow with Push Email over GPRS.
I tried to find a way to downgrade but hadn't had time sofar. When I logged on XDA Developers Site I saw there was a new Image.
So I thought Great I dont need to find how to downgrade.
I don't know what G4 and G3 is so as everybody let's try the higest best one.
I uploaded the RUU-Prophet-G4-AKU3.3-Jester-b1
Wrong...
Now as previously stated I get to the multicolor screen with IPL 2.09 and the SPL 2.20..0001 on the screen and that's it.
I can get to the bootloader and load the same image again and get the same result.
I can load another image on and it loads to 80 Percent and says error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file.
If I try an older Version it tells me upgrad only
And when I try to upload the G3 version it tells me error[300] invalid upgrade tool. This upgrade utility canot be used for your PDA Phone. Please get newer Upgrade utility.
Trying to use the nf.nbf or the G3 with the ROMUpdateUtility_NoID of the G4 doesn't work either.
If I would like to do the downgrade tool I need a Active Sync connection which I don't have.
I have no more thoughts. Please Help.
If you would have just read the forums better you would have known if your device is a G3 or a G4. (read this!).
Now it appears you have tried both for an update. Which may possibly have bricked your phone.
But... first things first. Can you get into the bootloader? (read wiki HERE on how to do that).
If you can still get into the bootloader then there is still a possibility for updating.
Try upgrading with the latest Qtek rom (note: this is an official rom, this one works for both G3 and G4! And since it's the latest you should be able to upgrade to this one).
Instructions quoted from another post of me:
You could try the 2.20 qtek rom which seems to be working well for quite some people (found here).
Although you have to make sure you read that thread good and use the ROMUpdateUtility_NoID.exe (found here ) to upgrade.
Update instructions:
1: With the qtek 2.20 rom you need to extract the zip and the exe file in the zip with WinRAR.
2: Then there is one folder called 'OutputFile' and a folder called 'RUU_TOOLS'.
Inside the RUU_TOOLS there is prophet and in that one WWE, when you go through them and in the WWE folder you see a bunch of files (readme.doc, enterbootloader.exe etc etc).
You need to copy ROMUpdateUtility_NoID.exe to the WWE folder with all the files. And you also need to copy the 'nk.nbf' file to the WWE folder (from the 'OutputFile' folder).
3: And then you need to put your phone in bootloader mode and run ROMUpdateUtility_NoID.exe to upgrade, which should work nicely then.
Click to expand...
Click to collapse
This should give you a good enough idea of what to do. This should work (new rom combined with no NoID updater).
However, if it's impossible to get yourself into the bootloader your options of upgrading your device are getting smaller.
Downgrading of a complete rom is only possible on a CID unlocked G3 (when it's CID unlocked you would know! because you would have done that yourself) and not on a G4 device.
Flasing a G3 device with a G4 rom or G4 device with a G3 rom might possibly turn your phone into a brick. This can easily be avoided by reading the forums properly and know what you are doing.
If anything (even if it's a small thing) is not completely clear to you about upgrading/downgrading your device I'd recommend not doing so.
edit: oh yeah... if you have a G4 device (which you should know by now) you cannot downgrade from this rom (well, only via a payed online service). And when you have a G3 device you could try and CID unlock it (read wiki + forums) before you want to downgrade, or don't downgrade at all.
But whatever you do, don't try to downgrade it without doing any of those things because you'll get into trouble. (to put it down bluntly)
illanz said:
I have tried to put off the battery all night long with no result.. but I have achieved to reach the bootloader mode by pressing the camera button while soft reseting and keeping the camera button pushed...
OMG, I have been so scared ! ! !
Click to expand...
Click to collapse
If you have reached the bootloader screen, just run my installer (or any official ROM) to get your phone working again.
My Prophet Died
I need help, to restore my Prophet, i upgrade wrong rom, i need will try the SD Backup, where can i see this process ?
Sorry my Inglish is too bad.
I've merged a couple of threads under this one, as they are all about the same problem (mostly)
Opening a new thread for the same problem isnt very useful
Hi RaptorRVL
Thank you very much for your patience in resuming all this for me.
I do try to read the forum but it isn't like a manual where you find the procedure stepby step. Like the G3 and G4 version I have newer come across until now. Sorry.
I tried the image you metioned and I have the result that at 80% it tells me error [326] Invalid Command This NBF cannot be used with your PDA Phone. Please check your NBF file
Any more thoughts?
As you seem to be an expert Can you let me know more about goldcard solution.
Cheers
Mick
From a readme I once found inside an update:
* ERROR [320~328] : INVALID COMMAND
These errors seldom occur. However, if one of these errors occur, it could not be recovered and the device had to be sent back to the customer service center. In this case, you have to flash a new ROM code.
Click to expand...
Click to collapse
Doesn't sound too good really. Maybe someone else here on the forums know what to do with this error :/
You did use the ROMUpdateUtility_NoID.exe and not the normal updater right? Can remember someone getting a similar error when using the wrong updater, but I'm not sure about that though...
edit: try doing a search on the prophet forums for "INVALID COMMAND" maybe there is a helpful post in there somewhere...
THANKS!! I was worried b/c i had the same problem today. I've been looking for so many threads abt this problem. Thanks for ur help guys!
same problem
so i have the same problem. I want to downgrade and it break at 95% invalid file. But now XDA is still alive. I can`t go into the bootloader but i tried this file: RUU_Prophet_220734_2207114_024721_NVID.exe
and now my Prophet is still running again. Hope i can help you. Good luck.
peter paul
P.S. sorry for my english, but its good to learn it again
I have an unusual problem with my oem att tilt running SPL-1.56.0000 (according to the bootloader screen).
The ROM is somehow corrupted in that it will not boot past the giant ATT logo and coordinates (?) screen. I have been having some trouble with the device, but this is a new occurrence not related to anything I did. I have never reflashed the ROM, and because it is in a current hosed state I cannot run hardspl on the device.
I have tried reloading many of the "ATT OEM" ROMs I can find, but they all return "Invalid ID" error the ROM uploader I believe because the versions don't match.
Is there any way to reflash the ROM and bootloader on the device without having first run hardspl? Am I SOL?
Thanks
RK
Did you try going to tri-color first then flashing a stock tilt rom?
Dude, I have the same problem...
I bought the tilt 2 weeks when I was in a business travel in the US and came back to Argentina... I'm kind of screwed about the warranty 'cause I don't think I'll go again so soon to the US...
Is there anybody who can help us with this?
The very diference is that (At the ATT start up Logo screen) the bottom line says D 1.57.00.00 instead of D 1.56.00.00.
Tried everything... soft reset, hard reset... and so on...
The thing is that at some point I think I can get to the phone in some way since if I turn on the phone keeping pressed the camera button and enter in the rom loader screen I can get comm to the phone using mtty (As pof explained to do for "Un-brick" the phone (In the case you got a bad flashing) in this thread...
So, please If anybody have any idea it would be great!
I still have a little hope, because it's like there is some kind of communication between the phone and the computer...
Thanks in advance to any help.
A.
both of you...
Check my sticky thread for reverting back to the stock tilt ROM and SPL...
all you really need from there is the Stock ATT ROM... download it!
Put your phone in Bootloader (shouldn't be too difficult by the sounds of it)
Install the stock ATT ROM.
If this doesn't work try extracting the downloaded ROM (using WinRAR or similar) then just run the ROMUpdateUtility.exe
Then you might want to consider installing HardSPL... the default download should work for the 1.56 guy. The 1.57 guy will need to download jwocky2001's whitescreen fix (check the stickies).
Good Luck!
I am at the tricolor screen and I have tried the instructions on your thread (thanks very much for making it so easy). However, it says invalid vendor ID after loading 1%; the device automatically reboots and reverts back to the ATT screen until I place it back into the tricolor bootloader again. I thought this was because the version I'm running is 1.56 and I could only find two original OEM ATT ROMs, neither was 1.56 and both failed.
BTW I couldn't do the part about hardspl and running the kaiser program on the device for obvious reasons, but I could get the kaiserruu program to recognize the device, another ROM and attempt to upload it.
Any other thoughts? Do I really need the exact same ATT OEM ROM as what is on the device or is something else wrong?
Thanks again
RK
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
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...