ok so I previously had NBD 7.6 on my phone and it was running fine. then I decided it was time to upgrade to 8.3 I went through the flash process using the shell tool straight from 7.6 to 8.3. however the hard reset did not work right away and my phone did what I think was a soft reset. where it gets stuck in the splash screen with the IPL SPL GSM and OS numbers. my phone is a G4 and I have heard that you can't use the RUU to flash new roms you have to use the shelltool. however I am trying to flash back to the original love rom and am having no luck because my computer does not recognize my phone and nothing comes up in my computer however it is connected because it makes the noise when I plug it in. so how can I flash back to the t-mobile love rom without putting Cert_SPCS.cab and EnableRapi.cab files on my phone?
Wizardlove should work. Perhaps you could elaborate on why wizardlove doesnt work.
Another suggestion is that you could flash back to the rom that your device was shipped with.
ok so my thoughts on why it doesn't work is because the Cert_SPCS.cab and EnableRapi.cab are unable to be placed on my mda before I flash. also it doesn't seem to be flashing anything at all because when I flash it and do a hard reset it comes up with my os being 6.6.6.666 which is scary and wasn't there when I used to have the original shipped rom. I have tried flashing wizard love twice both for 30 minutes and the shelltool never says it is done so I unplug and do a hard reset. any ideas?
squishymax said:
ok so my thoughts on why it doesn't work is because the Cert_SPCS.cab and EnableRapi.cab are unable to be placed on my mda before I flash. also it doesn't seem to be flashing anything at all because when I flash it and do a hard reset it comes up with my os being 6.6.6.666 which is scary and wasn't there when I used to have the original shipped rom. I have tried flashing wizard love twice both for 30 minutes and the shelltool never says it is done so I unplug and do a hard reset. any ideas?
Click to expand...
Click to collapse
You havent mentioned bootloader mode so i suspect your flashing wizard love with shelltool? correct me if im wrong. Put the phone in bootloader mode and flash wizard love using the RUU.
The original rom that was supplied with your device can in most cases be downloaded from their website. For example my device is branded I-mate so I obtained the latest rom from I-mate's website.
yeah my device is CID Locked and whenever I try to flash using the RUU the program loads up and I click next for like 2 screens and then when the mini screen that says verifying the information on your pda phone pops up vista kills it and says it has stopped working. so I have never been able to use the RUU when flashing to a new rom. and I have the lastest RUU as well. and yes my phone is in bootloader screen when I try to flash it.
I figured it out. It was easy. Vista can lick my balls! I went to a comp with XP and everything went smooth. after 5 hours of sweating and searching. @$%#%!
Related
I flashed my g4, using shell tool, to core 2.0n. After the hard reset it just sits at the boot screen listing ipl 2.25, spl 2.25, gsm 02.25.11, os 10.2.0.8.
When booting it to the boot loader I try to flash with the htc 8125 rom, but this fails with error 274 or 260.
Any help would be appreciated.
Splooshie said:
I flashed my g4, using shell tool, to core 2.0n. After the hard reset it just sits at the boot screen listing ipl 2.25, spl 2.25, gsm 02.25.11, os 10.2.0.8.
When booting it to the boot loader I try to flash with the htc 8125 rom, but this fails with error 274 or 260.
Any help would be appreciated.
Click to expand...
Click to collapse
Some G4's can't be flashed with the ROM on the HTC site, but can be flashed with the Wizard Love ROM. I'd try that. It's saved me several times.
Or try a hard reset before flashing another rom. See if it fixes the problem
If your phone makes it to the boot screen it isn't bricked.
It isn't bricked. It shouldn't be. If he flashed the Core 2.0n it's impossible that a OS only ROM would brick it because it doesn't touch the bootloader or the extended rom. Plus, from what i understand the ShellTool flashes OS only and that means even if the ROM he was trying to flash contained an IPL/SPL , then only OS would be flashed.
The fact that it even gets to the bootloader screen is proof enough it isnt bricked.... reinstall the carrier update and try something else.
Oh Sorry, he tried to reinstall the carrier ROM .. disregard.
I tried the love rom, but it errors out with error 300, invalid argument ( I think it looks like italian) =/
I've rebooted my pc, did a couple hard resets on the phone and verified the phone is being detected. The USB sync driver is loading. Seems every flash utility cant see the phone even when in the boot loader.
BTW it fails at the point where it tries to verifiy the information on my phone. if that helps.
Is your PC XP or Vista? If its Vista, it can't talk to a phone in bootloader mode. If you are XP then you should be fine but then I'm not sure why you can't flash the Wizard Love rom...
I'm using xp.
When you put it into boot loader mode, is USB in the lower left corner?
Splooshie said:
I'm using xp.
Click to expand...
Click to collapse
Have you tryed a hard reset ?
yes twice the second time when it rebooted I forced it to boot the boot loader before it tried to boot the OS.
And you have tryed taking out your SD card, and flashing the Wizard Love rom directly from the RUU (not with ShellTool) ?
You have enough battery ?
I have been using the flash utility, I don't know how to use shell tool without the scripts, and I can't install any of the cabs since it wont boot into the OS. I just tried on another xp machine and both the cingular rom utility and the love rom failed to communicate with the phone.
any other ideas?
edit: oh and I should have near if not 100% battery ( been plugged into a pc since the problem started and it was 100% when I started this mess. =) SD card has always been removed.
FYI, even though it has been plugged into the computer, it may not have enough battery. From my experiences, it drains the battery even if it is plugged in. Luckily, I have a second wizard so when my first battery drained (and wouldnt recharge even when plugged into the wall) I just popped the second battery in and i could flash it again. See if you can find a charger or something for the battery, and then once it is charged, let me know and I will give you a ROM i have that saved my other wizard (which is a G4 and no it isnt wizard love)
-Nstefanelli-
it seems to be charging, the orange light is on and the phone is off.
ok in a few i'll PM u a link to the ROM.. i havent used it in a while so i might have to gather it up..
-Nstefanelli-
well I tried the rom and it said error 300 this version cannot be used with your phone try a newer version (best I can figure from the italian?)
Splooshie said:
well I tried the rom and it said error 300 this version cannot be used with your phone try a newer version (best I can figure from the italian?)
Click to expand...
Click to collapse
Are you sure you don't have a G3 ? Hmm, I think you have a G3 and that's why it doesn't work. Try and flash the Tmobile 2.26
If your ipl 2.25, spl 2.25, then you defenively have a G3 CID UNLOCKED
Go back to Button's 1.05 ROM, CID UNLOCK it and then flash the Tmobile 2.26 and then flash Core 2.0n
Don't use ShellTool !
I was using Crossbow 1.7 Final and I had the problem with the phone dialpad not always showing up. So I finally decided to goto Crossbow 1.7.1. I loaded Cert_SPCS.cab and EnableRapi.cab and restarted afterwards. Gave it a few minutes and the used shell tool to load the OS. I however did not disable my Phone (In comm manager) before flashing I don't know if thats what messed it up or not. Anyway It flashed in 7 minutes and said end. I performed a hard reset now all I can do is see the iMate splash and IPL 2.16.0001 Etc it will not go passed it what do I do? I tried getting the Love rom but it's on RS and I dont have an account and my IE screwed up at 99% and now I have to wait another hour and a half. What can I do? Did I perform a step wrong and anyway what do I do now!?
I can enter bootloader mode but I don't believe shell tool works in bootloader mode does it? I tried loading with ROMUpdateUtility.exe but it gives me error 264 says there no connection. I'm stumped...please help.
Love rom gives me the same error 264.
try flashing the OFFICIAL cingular ROM ..
Cingular said it was the right manufacturer or something finally got the love rom to work so wohooo! Time to try to goto Crossbow 1.7.1 final again
Hi
I get this problem too often and I dont know why and what I did do when I dont get it. This is the case.
Now I have flashed the g3 wizard with one of the wm6-manilla roms. I have succeded with this once so I have followed the guides with the unlocking and downgrading etc. Now I have downloaded a new cook and try to install it by starting the rom update utility wizard.
Problem is that the installation ALWAYS fails now. It starts, the device disconnects from activesynk, waits another 30 seconds then fails to restart the device so I get the dreadful Error 260 update error and the phone is dead. I remove the battery, restart the device and try again and my hair turns grey.
I figure I need to downgrade first so I try all the differens RUU's that are pointed out in the guides (CUSTOM__RUU_Wizard_1050412_WWE_101_11210_WWE.exe, ruu_prodigy_226102_22610105_022511_tmous_wwe_ship.exe, Xda_MiniS_LaunchROM_v154102.exe) but always the same problem.
What am I missing?
WinXP
AS4.5
IPL 2.26
SPL 2.26
Once downgraded and CID unlocked,a G3 device will remain CID unlocked forever,there's no need to downgrade everytime you flash a new rom.Just simply flash a new rom whenever you desire.So don't reflash Button's Rom 1.05 before every flash,its just required to flash once to get IPL/SPL 1.xx for CID unlocking,after which there's no need to reflash it again.
Error 260 is due to open port,so reboot your pc and Soft Reset the phone,hope it'll work fine.If you have reflashed Button's Rom 1.05 and downgraded,it wud be better if you perform the CID unlocking procedure again through lokiwiz02b or WST_4.2.2,after that upgrade to IPL/SPL 2.xx by either flashing T_mobile 2.26 or any official aku 2 rom,then upgrade to any wm6.1 rom.
You can even take out the battery and leave it for 30 minutes,after that put it back and try to flash.
Hmm.. now I have rebooted the pc and disconnected the battery for 30 mins. No luck. Still the same error.
There must be something I have missed. I have flashed with several roms before w/o any trouble.
I am connected to activesync as a guest on usb-cable.
Oh i didnt downgrade because it failed that too. So right now im on a wm6 manilla pretty good rom but the wifi's gone
Try flashing from bootloader:
* Hold down the camera button and then softrest without letting go of the camera button.
You should se a pretty tri color screen with IPL/SPL Information.
* Connect Wizard to PC using usb and wait for windows to detect the drivers if they are not already installed.
* Start your RUU and follow the steps.
Normally this error occurs when trying to flash under vista, if this is the case visit a friend who has XP and take some coffee
It gets worse im afraid.. and I am under XP.
Now the phone wont pass the t-mobile bootscreen. It gets stuck when showing the IPL/SPL information.
I fail to enter the bootloader. Hopefully im doing something wrong.
I have tried this:
1) Holding down cam-button and pressing soft-reset. The phone boots as normal but stucks at same place.
2) soft-reset and when sceen goes black, hold cambutton. Doing this makes the boot halt totaly and the screen remains black. Looks like it turns off cause the softreset wont work and I have to press the powerbutton to get life signs again.
How (exactly) do I get it into bootloader?
Evolution... i managed to do a hard-reset and got the phone to boot up again. So back to square one with not being able to use the ubs+ruu
hmm very strange.. in a desperate attemt to get into bootmode i held down the voice-button instead of the cam-button and then power-on. Not it worked! Mystic....
***
update! problem solved
In case anyone else reads this. I rebooted the pc for the 10th time, rebooted the phone at the same time and (a dramatic paus here) i pulled the usb-cable and placed it in another slot in the pc. And there it goes...
I dont work with computers... i work against them!
i've already did a research.
Manage to Go bootloader.
But i cant seem to reflash my rom.
Stuck at 0% and theres an eror that came out.
It's strange.
For the first attempt it was a sucess and i managed to stock the Original SPL
So after doing that i tried the Hard-SPL.
Stuck at 0% eversince.
What phone do you have?
GSM or CDMA?
For almost if not all ROMs here you MUST HAVE hardSPL!!!
Oh i did have rom previously.
And i wanted to try lunacieROM
so i did flash it.
and it's stuck on the Black Screen after sucessfully reflashing.
So i went to the bootloader.
Reflash the Stock SPL
and wanted to reflash the Hard SPL
but it failed.
Its GSM.
Don't know why you flashed back to a stock SPL but I assume after flashing to a stock SPL you should FIRST flash your (or a) stock ROM and start from scratch (stockSPL --> hardSPL --> new ROM).
the problem is
after goin back to stock spl.
i dont think i can flash other roms.
including hard spl
or any other roms.
any idea?
And it get stuck at 0%
everytime i try to hard spl.
thats the thing thats been bothering me.
rullly said:
And it get stuck at 0%
everytime i try to hard spl.
thats the thing thats been bothering me.
Click to expand...
Click to collapse
What PC do you have (OS)?
You get a reliable active sync connection?
Did you try to put the phone into bootloader mode (tri-color screen) while DISCONNECTED from USB - will read "serial" at the bottom of the screen- and connect USB while in tri-color screen - should change to USB?
That are some basics to check and to test.
You COULD try to connect the phone in storage mode that it forces your PC to install Qualcom USB/NDIS drivers.
Ok. I've had problems up and down and tried and tried to do this and finally got it. So now I'm going to share it with all of you.
1. Download and Unzip the Files in the thread for the Ozone Verizon (HardSPL) posted by JockyW.
http://forum.xda-developers.com/showthread.php?t=551458
2. Connect your phone via ActiveSync, let it sync, and then start the auto.bat.
3. First, the JumpSPL will copy over. Press enter on the computer. Then the SSPL will copy over. Press Enter on the computer. Then it will prompt to start the JumpSPL. Press Enter. JumpSPL should pop up on your phone. Press the silver center button to start JumpSPL. The screen goes black. Then the DOS window will ask you if you have USB Connectivity. DO NOT PRESS ENTER YET!!!!
4. THIS IS VERY IMPORTANT!!! Wait for your phone to disconnect from ActiveSync. Once it does, unplug your phone from the USB. Go into ActiveSync's Connection Settings, and uncheck the box that says ALLOW USB CONNECTIONS. Reconnect your phone to the USB, and it should install the HTC USB Sync driver. NOW PRESS ENTER IN THE DOS WINDOW.
5. The RomUpdateUtility will start up, run it. And it should do the HardSPL on your phone. Your phone will restart when it's finished. If you want to check, before you do any of the above steps, copy the EnterBootloader.exe over to your phone. When you're done with the RomUpdateUtility and the phone has restarted, run the Bootloader and see what the tricolor screen says. It should be 0.39 Hard. Pull the battery, put it back in, restart the phone, and you should be good to go for flashing custom roms!
WOOHOO!
Thanks guys! I'll be donating soon. I'm about to flash the custom 3VO ROM right now! I'll let you know how it goes!
::EDIT:: The 3VO ROM is beautiful and runs like a charm! You guys put so much work into this.
Let it be known that this method for flashing the HardSPL can also be used for flashing the 3VO ROM.
NOTE: I WILL NOT TAKE RESPONSIBILITY FOR BRICKING YOUR PHONE.... seeing as I was scared I almost bricked mine once, and was VERY LUCKY that I did not. Please, follow all directions carefully. Phones are expensive.
ActiveSyn Doesn't disconnect
I got to the step where JumpSPL runs and my screen goes black. However, my phone never disconnects from ActiveSync. I tried unplugging it and disabling USB in activesync, but then my phone comes up as Not Recognized. If I try to run JumpSPL at this point I get, "Error (260): Connection." Any ideas?
How long are you waiting for ActiveSync to disconnect? It takes awhile. I know for me, it took about 5-10 minutes for it to disconnect.
Try waiting a little bit longer, and let us know what happens.
I waited long enough for activesync to stop. I unplugged my phone, disabled USB in activesync, and reconnected my phone. Every time I get a error saying "USB Device Not Recognized." If I try to run the update utility I get a connection error.
In all fairness I bricked my phone initially and had to recover it using a "stock" ROM someone posted for the CEDAR. My phone might just be hosed.
wm 6.5
quick question, the only way i was able to unbrick my phone was by upgrading it to the wm6.5 rom by Verzion, will the HardSPL work with this one?
I flashed the HardSPL on the Verizon 6.5 Update. So I guess the answer would be Yes.
I'm really lovin' this 3VO ROM. It's fast and the battery last a lot longer.
i tried your method and i'm still coming up with SPL-0.39.0000
i've tried other peoples guides as well and cant get it to hardspl, any ideas?
I followed all of these steps a few different times and my Bootloader still says .44. I tried varying the steps a little based on what users said on the thread about putting the HardSPL on the .39 and it still didn't help. I'm going to keep trying various configurations, but if anyone else is able to get their Official 6.5 ROM over to the 3VO, I'd love to hear how.
Thanks
what i need to know is what is hardspl i have an ozone that is unlocked but the data area is still locked to verizson and thats why i need to flash so i need to know what is hardspl and if its needed for an unlocked ozone
recoshaa said:
what i need to know is what is hardspl i have an ozone that is unlocked but the data area is still locked to verizson and thats why i need to flash so i need to know what is hardspl and if its needed for an unlocked ozone
Click to expand...
Click to collapse
You can find the hardspl definition here http://forum.xda-developers.com/wiki/index.php?title=Glossary
If you want to install a custom rom you will need to hardspl your device.
I hope that helps
I ran auto.bat, when the updater failed I disconnected USB from phone, reconnected, then ran updater manually and it all worked. Had to do this on both the HSPL and the ROM.
Also, make sure you don't uncompress both to same folder as it creates a .nbh file and if you have both on same folder you might be trying to install the ROM instead of the HSPL or vice-versa.
Another note. If you are HSPL already you can turn off device, turn it back on pressing DOWN VOLUME and POWER, leave both pressed until you get to rainbow screen, you can then run the updater and it won't bug you with battery being less than 1/2
I had problem that after screen goes blank, the phone will not connect. Some time "HTC USb Sync" will show, some time not. ROM Update will always complain that phone was not connected.
This is what I did to solve.
1. Power Off.
2. Hold vol dn and send with one hand. Then power with other hand.
3. Choose restore default configuration.
4. Let it boot
5. connect to ActiveSync.
6. Now run auto.bat
7. It runs fine and HArd SPL is loaded.
Enjoy.
schoenkn2 said:
quick question, the only way i was able to unbrick my phone was by upgrading it to the wm6.5 rom by Verzion, will the HardSPL work with this one?
Click to expand...
Click to collapse
Hi there, not sure if this belongs here. If you're planning on putting a custom ROM on the Verizon Ozone, do not use the HTC/Verizon wm6.5 update! "!! DO NOT !!" With the original stock wm6.1, you have a .39 Bootloader. After flashing the HTC/Verizon wm6.5 Stock Rom, you have a .44 Bootloader. And you can forget about putting a Custom/3rd Party ROMS. If somebody knows how to fix this, please tell me.
Thanks, and enjoy your HTC!
JD