I have an HTC Arrive and I am hoping someone can help. I have an interesting brick I havn't read anywhere else about. Hoping someone can help me unbrick my phone.
First, how my phone became a brick.
I had DFT's 8107 Rom flashed and used RSPL to flash the DFT Tango rom but WIFI hotspot wasn't working so I decided to flash Ansars tango rom.
I used RSPL to try to flash it but it got to 85% and then gave a connection error. I beleive it was error 262. I followed the on screen directions that had me unplug my phone remove the battery and put the battery back in and reflash. When my phone restarted it went into boot loader mode but it showed SPL and the RUU gave an error again. I figured it was because it was no longer in RSPL. I put it intop RSPL and then into HSPL that time to prevent the error from happening again. I then reflashed the rom this time with no errors. But, after that when my phone restarted it showed the HTC screen and then the Windows Phone screen and then it freezes. It eventually resets itself and does the same thing again. I have tried flashhing multiple roms to try to fix this problem but nothing has worked. I even tried using zune to restore an old backup.
Does anybody have any ideas what could be wrong and what I could do to unbrick my phone. Please help.
did it show the correct spl when you entered boot loader mode? (is. 1.xx instead of 4.xx or 5.xx? You may need to run the spl downgrade again.
In bootloader mode I was able to put hspl on and it shows version 1.25. I ended buying another arrive on ebay. My bricked one had a cracked screen and hinge anyway. I'm still open to suggestions to resurrect it though because if I do then since I will have an extra I can keep one hacked and one stock.
like the one above said - the bootloader can be fault, like only displays the SPL/RSPL/HSPL but not function like it should. i would suggest you to do a gold card downgrade and flash a stock ROM for you HTC Arrive (or is it maybe a 7 pro gsm version?) and then again RSPL/HSPL, and then a custom ROM if you want.
Have you tried to just flash the OSPL 1.29 from the HSPL post, and then try the RSPL/HSPL again? No need to goldcard this phone if you are able to at least flash things.
Related
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 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
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
Ok, so I am stuck at the white HTC spash screen, in the bottom left corner it says:
B 04
R 2.35.00WV
P DSDCANPZM-6125
D 4.01.93615
I had EnergyROM GTX, and I was flashing to this stock MR2 release and it flashed, and on first boot it is now stuck on the screen.
EDIT: Fixed! Check my 6th post, it was the steps I took to fix it.
You need to re-lock your phone to flash that update:
http: //forum. xda-developers. com/showpost. php?p=6838067&postcount=3
You'll see in the HSPL notes that there's a protection built in to prevent re-locking:
NOTE 2: this is unsigned Hard-SPL. no limitations on flashing ROMs (except of course some Radio roms). also, this has overwrite protection against HTC RUU's overwriting HSPL with a stock one, so if someone needs to revert to stock SPL for warranty reasons, a stock SPL downgrade package is posted here below. use this relocker *only* if you need to return the phone for warranty, and only use it as last step - after reflashing stock OS and radio. see steps at the end of this post about how to reflash stock SPL.
Click to expand...
Click to collapse
Since I can't post links outside of the forums, take out the spaces here to get the link to relock your device - scroll down to the bottom to where it says "how to reflash Stock":
http :// rhodiumw. htc-unlocks. com/hard-spl. php
well, i cant get it synced with active sync so how do i get it to talk with the computer?
Bootloader
Ok, i got into bootloader.
then what, run the bootloader relocker on post 2 of this thread: http://forum.xda-developers.com/showthread.php?t=578660
im confused the order in what to do things...anyone have a little more in depth info?
still get the white HTC screen after running the relocker...am i now supposed to flash the MR2 ROM update??
Ok I got it!
If stuck on the white HTC screen, get into bootloader on power (volume down + power button). I had to be holding them as I put the battery back in to get it to restart into it.
Once in bootloader, run this relocker
After that, get into bootloader again because you will still have the white HTC screen. Once in bootloader, run the MR2 update
It takes some time, I thought at first it was stuck again at the same screen, but be patient. It will load...
hope this helps!
You dont need to relock. Just put in boot loader and flash...
ai6908 said:
You dont need to relock. Just put in boot loader and flash...
Click to expand...
Click to collapse
to flash to this particular official update you MUST relock as stated on the posts above if you have been using a custom ROM.
without it you will always get a stuck htc screen.
Attempting to relock
I know this is an old thread, but I have been having trouble with a device for several weeks. I decided to give this relock and reflash stock ROM suggestion a try, but the relock sits at 0% and doesn't move. Any ideas what the problem may be?
Thank you!
HTC Touch pro 2 verizon GSM
Hi, i have a problem , I have a htc touch pro 2 verizon , i think its GSM because i can put a sim card in it , which am currently using with it now. the info below is the information for it. for some reason i can only load the mightyrom on it , when i try to load anything else it just gets struck at the bootscreen logo and thats it. i dont like the mightyrom , i wan to load something else on it , what rom is recommended and what process to go through without bricking the phone
B 04
R 2.35.00WV
P. DSDCANPZM-6125
D. 2.04.82488
RHOD500 32 SS-BC
SPL-1.00.01iNex
raven2k7 said:
Hi, i have a problem , I have a htc touch pro 2 verizon , i think its GSM because i can put a sim card in it , which am currently using with it now. the info below is the information for it. for some reason i can only load the mightyrom on it , when i try to load anything else it just gets struck at the bootscreen logo and thats it. i dont like the mightyrom , i wan to load something else on it , what rom is recommended and what process to go through without bricking the phone
B 04
R 2.35.00WV
P. DSDCANPZM-6125
D. 2.04.82488
RHOD500 32 SS-BC
SPL-1.00.01iNex
Click to expand...
Click to collapse
Did you try reflashing the verizon shipped rom?
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!