Related
Hello I have done all the Faria tutorial and got it unlocked and IPL AND SPL 3.08, but when I tried flashing a WM6 rom the process stuck at 6% and the update program gave me a "conection failure" error and then started a step by step recovery process... I have done it and now i´m with the 3 colors screen (red green blue) but I´m trying to flash a rom to it without success. why is that? can someone help me?
you need to read this thread
http://forum.xda-developers.com/showthread.php?t=314646
I hope you weren't flashing with vista. I think it requires the shell tool.
no, no vista.
I have followed EVERY instruction in the VIPPIE: http://forum.xda-developers.com/showthread.php?t=298613 and FARIA tutorials, the problem was that when flashing it gave me a connection problem at 6% and then is not stuck in the bootloader screen. I hope my phone is not damaged since i´m in brazil. But I´ve tried several roms without success... they say problems with version OR with connection. Why can that be?
it stays a long time in "verifying the information on your PDA phone..." and then it returns those errors I´ve mentioned.
flash the stock Cingular ROM from HTC's website it will flash for you from the RBG screen
http://www.america.htc.com/support/8125/software-downloads.html
n3rxs said:
flash the stock Cingular ROM from HTC's website it will flash for you from the RBG screen
http://www.america.htc.com/support/8125/software-downloads.html
Click to expand...
Click to collapse
thank you man!!! I will try that right away!!!
n3rxs said:
flash the stock Cingular ROM from HTC's website it will flash for you from the RBG screen
http://www.america.htc.com/support/8125/software-downloads.html
Click to expand...
Click to collapse
man, you are a life savier!!! worked flawlessly... now does I have to unlock the cid again or can I flash a Wm6 rom right away??
fscussel said:
man, you are a life savier!!! worked flawlessly... now does I have to unlock the cid again or can I flash a Wm6 rom right away??
Click to expand...
Click to collapse
Once unlock...always unlocked unless you reversed the procedure.
If your flash of a custom rom fails again, your device is probably not CID unlock and you need to go thru the unlocking process again.
ok after fixing the problem with the n3rxs help I´ve flashed the Wizard Love rom to prepare to flash a WM6 rom. The Wizard love rom i´ve used has a Italian instalation program, is that right? after I installed it the cell phone keeps reestarting I can´t do anything in it, it only loops restarting... what´s that?
found the solution, had to keep the camera button pressed and then reset the device so it enters in BootLoad mode then I flashed a original cingular bios and after that upgraded to WM6 without a glitch!!
Hi everyone,
I think I may have bricked my Kaiser. I've been following some similar threads but nothing seems to be working to fix the problem.
I was going through the process to flash a new Rom, starting with installing HardSPL following this thread I was. I was having problems, I think because I have the 1.82 ROM version.
Finally, I thought I had HardSPL installed, so I continued to run KaiserCustomRUU.exe. This completed (jumped from 0% to 100%) very quickly. However, I reset my phone and it is now stuck in the tri-color bootloader screen
The screen has the says:
KAIS130
SPL-1.82.0000
CPLD-8
and has the letters RUUNBH in the top right corner.
I've tried removing the battery and resetting, but the phone always goes back to this screen. I've also tried running mtty, but without success. The command 'readconfig' returned a result 'Command error !!!'.
does anyone know of anything else I can try?
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
If your at the tri-color screen, just reflash a new rom
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
If that goes through ok, then do the same to flash another ROM.
Again no expert at unbricking but its definately worth a try
japher said:
Small bit of good news: if I issue the command 'boot' using mtty, my phone boots into my original ROM successfully, with the mtty output:
InitDisplay: Display_Chip=1
No card inserted
OSSIReadBack ++
Read SI data from flash success
tail signature match
Checksum match
UserStorageSIPreload ++
It takes a long time to boot (like a couple of minutes), but it does eventually boots up fine. When I reset, I'm back at the tri-color screen though
Click to expand...
Click to collapse
Try this.
1.) Open ActiveSync and navigate to File > Connection Settings - Uncheck Allow USB connections.
2.) Download this ROM http://rapidshare.com/files/5781641...dio_sign_22.45.88.07_1.27.12.11_Ship.rar.html and flash it to your device.
That should work for you.
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
japher said:
hi alltheway. thanks for the advice!
I don't want to sound ungrateful, but are you sure the above is safe? I just don't want to make a wrong step now and totally screw up the device (now that I can successfully do a manual boot using mtty).
I know you can't guarantee it but is this what others who are stuck in the bootloader have done?
Click to expand...
Click to collapse
I had this problem about 2 weeks ago.
I was flashing one of Dutty's Great ROMs and I lost power at the house and shut down my computer when I was 46% done.
I had the same RUUNBH in the top right hand corner. All I did to fix this was flash a factory shipped ROM like the one I provided to you and it worked great. No issue thus far.
Honestly I can't gurantee 100% if this will totally fix your problem but I am 95% sure.
Unless some other users have an answer for you I think this will be your best solution. Regardless of what you do you will have to flash to a new ROM anyways.
Also, I'm a bit dubious on whether i will be able to flash to that ROM. I don't think I have the right HardSPL installed to flash roms (see what my boot-loader screen says in the first post).
I'm no expert though.... obviously
Thanks for all the info alltheway. I'm too tired now (will probably f*ck the thing up even further! ), so I'll try flashing this tomorrow.
Here's some more info I've collected using mtty (my phone is an O2 XDA Stellar):
Code:
Cmd>info 2
HTCSO2___001¯JG±HTCE
Cmd>getdevinfo
GetDevInfo: Get CID OK
HTCSKAIS1300O__0HTCE
New Thread
Read this:
http://forum.xda-developers.com/showthread.php?t=355910
Hi tqm. I've been following that post but as far as I can tell there is no solution there yet.
From what I can tell from that thread (and others), the only way stop the phone booting to the tri-color screen (in RUUNBH mode) is to flash with a ROM that matches the vendor. I think because I haven't been able to install HardSPL properly, my phone's version of SSPL will only load O2 ROMs (could be wrong here, but that's the picture I'm building ). Unfortunately no-one seems to have extracted the ROM from an XDA Stellar :\
I believe alltheway's solution above worked for him because he had HardSPL installed properly. He could load the stock ROM to fix the phone, because his SSPL version allowed different ROMs to be loaded. I'm not certain of this, and I'll probably try his suggested solution when I get home today... but I'm not too confident.
If only there was an mtty command to just get the phone out of 'RUUNBH' mode. I've seen the command 'task 8' mentioned on here, but it doesn't work when I try it. Does anyone know of a list of mtty commands for the Kaiser anywhere?
Definitely flash the original ROM, it will get your device to the default HTC shipped state.
Then sync phone with ActiveSync, install HardSPL again and then flash custom ROM.
I remember i had the same issue but the original rom is a lifesaver
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
japher said:
You mean the original HTC ROM? or the original O2 ROM? (what my phone originally came with)
If I don't have one of the HardSPL versions posted on the forums (I believe they never installed properly, which is what caused all my problems I think), will I still be able to flash the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
Basically my questions is: is this stock HTC ROM flash-able to ALL kaisers? (even without downloading/installing HardSPL from the forums)
If not (i.e. I can't flash even the stock HTC ROM), is it expected that if I can't successfully install HardSPL, my Kaiser will only accept O2 ROMS?
Click to expand...
Click to collapse
IMHO the HTC stock ROM should work even without HardSPL, at least for me it worked fine... but just for sure have your O2 stock ROM by hand.
jaso2005 said:
Im not an expert but when its at the tri colour screen, try to flash Hard SPL again, it should pick it up and flash i believe.
Click to expand...
Click to collapse
I don't thinks there's a way to flash HardSPL on tri-color scrren so far, coz activesync cannot connected to computer
the best way is trying to find the phone's offcial ship rom to flash
No luck trying to flash with the stock HTC ROM:
RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship.exe
After getting to 1%, it reports an error:
Error [294] : Invalid Vender Id
As suspected, looks like this will only accept an O2 ROM Will have to wait until one is available.
Did you try installing HardSPL and then reflashing?
the stock HTC rom will not load onto your kaiser simply because it is still CID locked to O2's CID code. You HAVE to find the O2 rom that your device came with or any O2 ROM and reflash that and you will be good to go. You may also try and flash HardSPL but I dont think its going to work. But remember have a friend or someone on the forum dump and rebuild the O2 rom for you and just reflash the OS.nb or ROM only no radio!
It is very simple to dump and rebuild a rom so if you have a friend that has a kaiser have him over for an hour and dump his
thats your only shot at this point.
URPREY said:
Did you try installing HardSPL and then reflashing?
Click to expand...
Click to collapse
My current ROM version is 1.82. I don't think installing HardSPL has been solved for this ROM version, which I think is where all my problems started. I have tried, but no version of HardSPL (that I've found) will install correctly.
austinsnyc said:
You HAVE to find the O2 rom that your device came with or any O2 ROM... just reflash the OS.nb or ROM only no radio!
Click to expand...
Click to collapse
Thanks for the reply austinsnyc, this is what I'm hoping to do now, I'm watching this thread 'Has anyone dumped the o2 Stellar rom yet ?' closely Maybe I should reconstruct the ROM myself, I'm just a bit worried about arsing that up as well I'd rather someone experienced reconstructed and verified the ROM (on a phone that isn't already messed up).
Out of interest, would you be able to give me a succinct explanation of what is actually wrong with my phone at present? As far as I can tell, the only problem is that the boot-loader is stuck in RUUNBH mode. Has part of the ROM on the phone actually been destroyed?
I'm assuming right now that the point of flashing the O2 ROM is just to make the phone 'finish' a flash and get out of RUUNBH mode. Or is it actually to re-instate something that has been lost?
If it is to reinstate something that's at present lost, is this data definitely part of the os.nb?
If it's just to get the boot-loader out of RUUNBH mode, I'm REALLY gutted that there isn't just a mtty command to do this
Oh yeah, and perceptivepixel.com Ace!
i have read several thread but none i could understand
first, i use hermes unlock v3: it said "success". i also have fat32 my sd card and place cheeimg.nbh all by itself and place it in my treo750. can someone guide me thru the rest of the steps please. much thx
Akachay,
If you have done this:
http://wiki.xda-developers.com/index.php?pagename=HTC_Cheetah_Upgrade
and it is not working, then you need to install the hard-spl. Instructions for this are here:
http://forum.xda-developers.com/showthread.php?t=334100
Does this help you?
John
thanks john. instruction is very clear.
now i'm stuck in bootloader; it never prompt me to proceed. can u share the 6.1 cheeimg that u used plz
akachay said:
thanks john. instruction is very clear.
now i'm stuck in bootloader; it never prompt me to proceed. can u share the 6.1 cheeimg that u used plz
Click to expand...
Click to collapse
if you are in bootloader, have you already hardspl-ed ? do you see olipro.... or what text in bootloader you see...
now you can simply flash with ruuwrapper your cheeimg....
like here:
http://forum.xda-developers.com/showthread.php?t=382612&highlight=discovery
cheeimg from this thread works me ok:
http://forum.xda-developers.com/showthread.php?t=374381&highlight=fine
yeah i decided to try hard_spl method: step 1 was successful, step2 "unlock radio" everything went fine til the very end; it said error. can't seem to get past that step to get to step3. some guidance plz.
ps, my phone display windows 6.1 now so is it neccessary to run the last 2 steps?
akachay,
I got the same problem. You have to reflash with the orginal ROM so you have a proper working radio. then you can update to 6.1.
use the original desktop updater for WM6, edit the payloads.xml file, then flash the treo. then update to WM6.1 using the KaiserCustomRRU or the SD method.
akachay said:
yeah i decided to try hard_spl method: step 1 was successful, step2 "unlock radio" everything went fine til the very end; it said error. can't seem to get past that step to get to step3. some guidance plz.
ps, my phone display windows 6.1 now so is it neccessary to run the last 2 steps?
Click to expand...
Click to collapse
Yea, once you come to that error, thats when you just quit, then go on to flashing the actual rom (KaiserRUU + Rom)
then after the rom was flashed to 6.1, them just use the update radio only patch .. although I have NOT YET updated my radio, after flashing, it works fine, no dropped calls or whatever .. internet speed is great .. but i'll update this post if it does stop werking..
Attached you find all you need to flash cooked ROMs on your Ozone (Cedar).
The sspl/hardspl are confirmed to work fine on the HTC Cedar platform (Ozone).
It will not work on the HTC Maple platform (Dash3G). Running this sspl on a Dash3G will definitely brick it. Also the HTC Willow platform (SNAP S511, Sprint) is not supported. For the Dash3G I have already developed a sspl/hardspl. Users of the S511 have to wait until I feel motivated ..
The packages contains a SSPL, HardSPL, patched ROM updater and the original Ozone SPL. The package is based on SPL v0.39
Instructions:
1. remove SD and SIM cards (don't forget otherwise the sspl is likely not to work!!)
2. connect your device to your pc with a USB cable and wait until it is synced
3. extract the file "Ozone HardSPL by JockyW.zip" and execute "auto.bat"
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "0.39.Hard")
5. to test the sspl and the hardspl you can flash the attached splash.nbh
Once the HardSPL is installed on your device you can flash any Ozone cooked or original ROM.
Have fun,
JockyW
PS: Moderators please make this a sticky. Thanks.
Awesome work JockyW.
Awesome, thanks for your hard work.
Now all we need are some 6.5 roms!
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "0.39.Hard")
Click to expand...
Click to collapse
Um... so most of this worked fine, and the screen is dark, and a generic htc driver got auto installed... and the Rom Utility popped up on my screen... But how do I get it to connect to activesync like this?
After my phone rebooted completely (following the ROM utility completing), I just re-enabled Allow USB connections and it seems to work fine.
No, so the rom update tool doesnt complete because ActiveSync doesnt work after the screen turns black...
Edit: and Im using XP (noticed ur not from the thumbnail...) idk if that matters or anything
I'm having some difficulties of my own. I'm running Windows 7 RC x64 with WMDC 6.1.6965.
I started by running the sspl.bat (with USB enabled in WMDC); the SPL app came up on my device's screen, I tapped ok, and the device screen went black w/ solid black pixels. The only way of rebooting it is yanking the battery. The OS loads fine after that.
Later I thought it had run sucessfully so I ran auto.bat. The JumpSPL steps ran fine (with USB enabled still) but it failed at step 4 when the ROM tried to flash (obv. because USB was still enabled).
Strange thing is, when USB is disabled and I run auto.bat, the device is unable to connect in steps 1-3. I canceled all those steps and then the ROM flasher starts, makes a connection, and starts the flash but won't go past 0%. The screen is still black because after step 3 the SPL flashes (or attempts to.)
I later put the device in bootloader manually (with the colorful bars) and ran the ROM flasher by itself. It runs but again, gets stuck at 0% on both the device and the PC. After a while a 262: update error pops up. This must be because the SPL is still locked? The OS boots fine after a battery pull.
Strange. Any advice would be welcome.
forgot to remove my SIM card! Gonna try again, give me a few minutes
no, same problems. :sigh:
The bootloader is still locked in 0.39.0000, confirmed.
EDIT: I'm pretty sure all my problems are coming from x64 drivers. I'm going to try this again in Windows XP Mode. Congrads everyone who's succesfully flashed! Good work guys!
businesschild said:
forgot to remove my SIM card! Gonna try again, give me a few minutes
Click to expand...
Click to collapse
businesschild said:
I'm having some difficulties of my own. I'm running Windows 7 RC x64 with WMDC 6.1.6965.
I started by running the sspl.bat (with USB enabled in WMDC); the SPL app came up on my device's screen, I tapped ok, and the device screen went black w/ solid black pixels. The only way of rebooting it is yanking the battery. The OS loads fine after that.
Later I thought it had run sucessfully so I ran auto.bat. The JumpSPL steps ran fine (with USB enabled still) but it failed at step 4 when the ROM tried to flash (obv. because USB was still enabled).
Strange thing is, when USB is disabled and I run auto.bat, the device is unable to connect in steps 1-3. I canceled all those steps and then the ROM flasher starts, makes a connection, and starts the flash but won't go past 0%. The screen is still black because after step 3 the SPL flashes (or attempts to.)
I later put the device in bootloader manually (with the colorful bars) and ran the ROM flasher by itself. It runs but again, gets stuck at 0% on both the device and the PC. After a while a 262: update error pops up. This must be because the SPL is still locked? The OS boots fine after a battery pull.
Strange. Any advice would be welcome.
Click to expand...
Click to collapse
businesschild said:
no, same problems. :sigh:
Click to expand...
Click to collapse
businesschild said:
The bootloader is still locked in 0.39.0000, confirmed.
Click to expand...
Click to collapse
Instead of replying to yourself, please use the edit button next time.
Anyways, if you run auto.bat, disable USB Connections after the screen turns black via ActiveSync. In your device manager (with the screen still black) look at your USB Devices. You should see a entry called HTC USB Sync. If you see that continue to flash. Seeing HTC USB Sync is a key step in this whole process.
Please read the testing/development thread for some good solid help. A bunch of us ran into the same issue you did. If you read all 4 pages you should be able to troubleshoot your problem: http://forum.xda-developers.com/showthread.php?t=550628
computerpro3 said:
Awesome, thanks for your hard work.
Now all we need are some 6.5 roms!
Click to expand...
Click to collapse
Working on it! Lots of work! Gonna grab my Ozone later today and cook you guys up some treats to taste test! Haha. Ready??
ookba said:
Working on it! Lots of work! Gonna grab my Ozone later today and cook you guys up some treats to taste test! Haha. Ready??
Click to expand...
Click to collapse
I'm a new member here and I can't believe how much hard work you guys put in for free. I am pretty broke right now but at some point in the next week or so I'm going send a small donation to both you and jockyw....won't be much as I really can't afford it but should buy you some decent beer at least...
computerpro3 said:
I'm a new member here and I can't believe how much hard work you guys put in for free. I am pretty broke right now but at some point in the next week or so I'm going send a small donation to both you and jockyw....won't be much as I really can't afford it but should buy you some decent beer at least...
Click to expand...
Click to collapse
HERE HERE!
The stock ozone rom is crap, I would love to cook my own ROM!
BTW hardspl successfully flashed first try on my device. Totally painless. Excellent job.
Anyone with a Telus SNAP try this?
ariesq said:
Anyone with a Telus SNAP try this?
Click to expand...
Click to collapse
I think the Telus SNAP is a CEDAR as well. Uses the same CDMA network as Verizon. Dump your SPL and post it for JockyW to examine and give the tumbs up.
Also, dump your RAW files, upload and post in this thread if you can.
http://forum.xda-developers.com/showthread.php?t=540586
Also guys, we gotta hook up JockyW with some donations. He worked his ASS off to build this and we have to show some gratitude. If you want him to continue to support us, we have to show him some love.
ookba said:
Also guys, we gotta hook up JockyW with some donations. He worked his ASS off to build this and we have to show some gratitude. If you want him to continue to support us, we have to show him some love.
Click to expand...
Click to collapse
I agree. Just sent him a small donation. You're next ookba, but will have to wait until next paycheck.
Update: Small donation sent to you as well ookba. I'll just have to skip lunch tomorrow
P
How sure are you that Ozone is Cedar?
RUU_Chief_W_WM65_VERIZON_WWE_2.10.605.1T_Radio_612522_1.71.00WV_NV_MFG_VZW
looks like a chief to me, but I could be wrong, I would like to release a 6.5 kernal, but dont want to have wrong device.
Good day.
I have an HTC Arrive on Sprint (CDMA, of course) that I'm trying to update to WP7.8. Specifically, I'm trying to use the HTC Arrive 7.8 Sianto Edition AL ROM.
I used this guide to downgrade the SPL to v.1.25... and the MID number is correct.. I then open up the downloaded ROM folder, and click on ROMUpdateUtility. It skips most of the steps that the user guide for the DFT, but I suppose I could attribute that to it being in the ROM folder itself and selection of the ROM being unnecessary.
Whenever I execute the ROMUpdateUtility file, after I have set the phone into bootloader mode (volume down + power button), it skips right to the flashing process. However, it then sits at 0% for a few minutes and exits with error code 262, which, according to documentation:
ERROR [262, 276, 284, 302] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
Click to expand...
Click to collapse
The phone itself still works; it's not a brick. What exactly is going on here? How do I flash it correctly? If this is in the wrong section, just let me know.
Hello. I just recently flashed my Arrive to Wp7.8 with no problems. I chose the LEAD rom though. May I ask why you want the Sianto Edition? I have seen in the thread for that rom that a few people are having issues installing it. I flashed the LEAD rom with no issues and it is great.
You said that you did downgrade your SPL, did you also install both RSPL and HSPL? I don't know if it makes any difference, but as soon as the HSPL installed and the phone rebooted into the boot loader, I began the installation of the new rom. When you attempt to flash it are you seeing "Cotulla" on you phones boot loader? Also be sure that the bottom portion says USB and not Serial. If it says Serial, unplug the phone and plug it back in, it should then turn to USB and you can proceed to flashing.
Hope this helps
Edit - also, are you running the RUU as Admin? You must Run As Administrator when flashing. Right click the EXE and Run As Administrator
x_orange90_x said:
Hello. I just recently flashed my Arrive to Wp7.8 with no problems. I chose the LEAD rom though. May I ask why you want the Sianto Edition? I have seen in the thread for that rom that a few people are having issues installing it. I flashed the LEAD rom with no issues and it is great.
You said that you did downgrade your SPL, did you also install both RSPL and HSPL? I don't know if it makes any difference, but as soon as the HSPL installed and the phone rebooted into the boot loader, I began the installation of the new rom. When you attempt to flash it are you seeing "Cotulla" on you phones boot loader? Also be sure that the bottom portion says USB and not Serial. If it says Serial, unplug the phone and plug it back in, it should then turn to USB and you can proceed to flashing.
Hope this helps
Edit - also, are you running the RUU as Admin? You must Run As Administrator when flashing. Right click the EXE and Run As Administrator
Click to expand...
Click to collapse
Yeah, some idiot (who shall remain nameless because my ego is fragile) didn't do HSPL after RSPL. Installed fine after that.
Sorry to bother you guys :silly:
Glad to here you got it installed!