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!
Credit goes to the creator of the HardSPL files V3.28/3.29; JockyW
Simple Step-By-Step Installation of 3.28 Hard SPL:
I have decided to expand on what has already been posted for those noobeees that are having hard time understanding the HardSPL procedures and are hesitant to flash new cooked ROMs fearing the process was not really explained in details.
You only need two files; SSPL-KAIS.zip and Kaiser-HardSPL-3.28.zip. Save both files on your PC in their own folder for easy access later. Follow these steps to the tee, Do this only if you have your device CID unlocked already ( OliPoff method ):
1. Save then unzip SSPL-KAIS.zip inside a folder on your PC, then copy the unzipped “SSPL-KAIS.exe” onto your device. To do this, connect your device to ActiveSync, After Syncing, Click on Tools from the ActiveSync window, and then click on Explore Pocket PC. “Mobile Device” window appears, Copy SSPL-KAIS.exe by dragging it inside the “Mobile Device” window.
2. Unzip “Kaiser-HardSPL-3.28.zip” in its own folder on your desk top. It will unzip into two files; KaiserCustomRUU.exe and Kaiser-HardSPL-3.28.nbh.
3. Remove your SIM card and your SD card from device. Your device will power off when your SIM card is removed. Power up your device. You are still connected to your PC via USB at this point. Your phone will sync again since it is still connected.
4. On your device, go to “File Explorer” and locate SSPL-KAIS.exe that you copied earlier on your device main memory and click it.
5. Wait for the Bootloader Tri-Color screen to appear and "USB" to show.
6. On your PC bottom tray, Right-click the ActiveSync icon, go into “Connection Settings” and ensure “Allow USB Connections” is unchecked
7. Unplug your device from the USB port, wait 5 seconds, plug it back in.
8. Go to the folder on your PC that has “KaiserCustomRUU.exe” and click it. This will flash the HardSPL on your device.
9. When done flashing, do a soft reset, and you should be good to go.
10. You can use the above steps to flash Kaiser-HardSPL-3.29 if you so desire.
Good luck
Tilt will not receive ROM
I tried flashing the below upgraded Kaiser Rom on my ATT Tilt but now I have the tri-color screen:
KAISI*0
SPL-1.93.000
CPLD-8
The first time it stopped loading at 15%, recovered and now I am getting vendor ID error (294 invalid vendor ID).
I tried others ROMs (including this one) but it just does nothing 0%, errors out, recovery and repeat (update error 262).
After removing battery the tri-color screen says "serial", once I plug in the USB it says USB, but no firmware can be loaded on it.
Does someone have basic firmware that will load when an ATT Tilt gets in this state?
Any help is really appreciated. I just got this thing too. Below was the update I tried that kill my Tilt.
'RUU_Kaiser_HTC_WWE_3.28.405.0_radio_sign_25.83.40.02_1.65.16.25_Ship.exe' that you can find
did u hardspl?
Yes, I had to use the JumpSPL1.56-KAIS (HardSPL fix).
TiltedHTC said:
Yes, I had to use the JumpSPL1.56-KAIS (HardSPL fix).
Click to expand...
Click to collapse
Sounds like your phone is still CID LOCKED. Unlock it using the software posted somewhere else on XDA but NOT in this thread, and try to upgrade the SPL after unlocking.
One way to find out if your device locked or unlocked is that you can try to revert back to the AT&T OEM ROM and flash it. You would then be certain that the CID is locked if your device accepts the OEM ROM.
I wish you posted your troubles in the ROM post where you downloaded the ROM where it belongs; My instructions have nothing to do with your device ROM issues.
I believe you are exactly right! Do you know where there is copy of the AT&T OEM ROM? I would love to have my phone working again.
Sorry for my ignorance. Where is the ROM section for my AT&T Tilt. I got the ROM link from modxxxx .com
Thank you for the assistance.
TiltedHTC said:
I believe you are exactly right! Do you know where there is copy of the AT&T OEM ROM? I would love to have my phone working again.
Sorry for my ignorance. Where is the ROM section for my AT&T Tilt. I got the ROM link from modxxxx .com
Thank you for the assistance.
Click to expand...
Click to collapse
The following link is to Pof's full and clear post on unlocking your device CID. Use it carefully.
http://forum.xda-developers.com/showthread.php?t=334679
Search the forum for RUU_Kaiser_AT_T_CINGULAR_WWE_1.62 Rom, download and then flash. you will be set.
Cingular/AT&T OEM ROM
Download the AT&T OEM ROM from the following link:
http://rapidshare.com/files/55298724...GULAR_WWE_.exe
This is just because I feel good today... Otherwise I would ask you to take the time and do the search yourself. Noobee Spoon-feeding Time...
I found this link to put OEM ROM back:
http://forum.xda-developers.com/showthread.php?t=335568
but the RUU ROM for the AT&T link would not load on my tilt (step 2 of idiots guide). I also did a search for the RUU_Kaiser_AT_T_CINGULAR_WWE_1.62 Rom but no hits.
At least I know what went wrong, now I need to recover the original Rom.
update:
This newbee still won't eat. I got the file (your link is to the same file) but I am getting the same 294 invalid vendor error (after 1%).
I rebooted computer and tried it again with same 294 error.
did you just use jumpspl and used that to load a rom?? why oh why.......
Tilted newbie, did not read enough. Any solutions?
A question.
On your PC bottom tray, Right-click the ActiveSync icon, go into “Connection Settings” and ensure “Allow USB Connections” is unchecked
Do you have to do this ?
I never did that.In my settings USB connections is enabled and it seems to work
/Linus
thaaaanx
i must admit this is the best and clearest step by step guide i have come acrooss thanks a lot mate
just a quick thought..... maybe you should give some credit to jocky
Also,
It wouldn't hurt to mention the "white screen" issues people get when running SSPL.
In such a case they need to use Jump SPL 1.56 or 1.93.
Link Here
Ta
Dave
Thnks man for tutorial. I think it usefull and simple for newbies.
So now, when my Kaiser has Hard-SPL v1 and custom ROM, I can do above steps to upgrade SPL? And then upgrade to custom ROMS without touching SPL?
Thanks
kpcz said:
So now, when my Kaiser has Hard-SPL v1 and custom ROM, I can do above steps to upgrade SPL? And then upgrade to custom ROMS without touching SPL?
Thanks
Click to expand...
Click to collapse
Correct.
Hard SPL's allow you to flash custom ROM's no matter what version.
Ta
Dave
ok, thanks - will give it a try!
It appears there is no way to recover.
Any great excuse that should be used when I take it back for repairs?
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.
I've flashed my palm pre with ease. I've also done the same to my Samsung Transform. There have always been guides on how to do so. I'm having trouble finding any guide on how to flash a custom rom to my Arrive. Can anyone point me in the right direction?
first: you are going to need to install HSPL. when you reboot with holding down the "volume - " button, what shows up as the SPL? 1.x? good, install the HSPL, anything higher? you'll have to downgrade.
Once you install the HSPL, it is as simple are running the RUU updater from ansar or the DFT rom
here is the HSPL
http://forum.xda-developers.com/showthread.php?t=1195647
and here is the SPL downgrader
http://forum.xda-developers.com/showpost.php?p=22574586&postcount=970
Thanks, for the help..
Those roms are horrible to download. Terribly slow and often lose the connection. I finally got both of them after several hours of retrying. Trying the anasr rom first
cdowers said:
Thanks, for the help..
Those roms are horrible to download. Terribly slow and often lose the connection. I finally got both of them after several hours of retrying. Trying the anasr rom first
Click to expand...
Click to collapse
in my opinion the DFT rom is a bit better. Ansar's would not allow updating the PRL, and would also throw an error on reboot. DFT is running smoothly on mine for the past week.
jeffc313 said:
in my opinion the DFT rom is a bit better. Ansar's would not allow updating the PRL, and would also throw an error on reboot. DFT is running smoothly on mine for the past week.
Click to expand...
Click to collapse
what version is yours?
4?
blanket said:
what version is yours?
4?
Click to expand...
Click to collapse
I'm running the "DFT Freedom Gold_C V1 for Sprint"
if I am reading things right I need to run the rom upgrade utility to downgrade my spl to version 1.xx from the current 4.xx but I can't get the ruu to work, I keep getting error 260 connection. Any idea what I am doing wrong? The readme file says to reset the device and or the computer, which I've tried but still get the error.
Also, if I restore my phone to nodo will that accomplish the same thing (downgrade to spl 1.xx)?
turdsamich said:
if I am reading things right I need to run the rom upgrade utility to downgrade my spl to version 1.xx from the current 4.xx but I can't get the ruu to work, I keep getting error 260 connection. Any idea what I am doing wrong? The readme file says to reset the device and or the computer, which I've tried but still get the error.
Also, if I restore my phone to nodo will that accomplish the same thing (downgrade to spl 1.xx)?
Click to expand...
Click to collapse
you should only have to run the utility to downgrade the SPL. When you boot up the phone into the bootloader by holding down "Volume -" on boot, do you get the "Serial" at the bottom?
When you plug into your PC, does it change to "Usb" for that same line?
It does say serial at the bottom but it doesnt change when I connect it to the pc, if it is already connected to my pc when I boot into bootloader mode it does say usb though.
edit: I figured it out, apparently the driver didnt install
so, I've successfully flashed my arrive to the dft freedom rom and I love it (especially enabled internet sharing) but now I have a noobish question. Is the rom updateable? (through Zune or otherwise) or will I have to flash again and reload all my apps and contacts in order to apply an update?
This is why I've been holding off flashing. I haven't NEEDED the ICS yet and I was worried whether or not it would take updates. So I was going to wait until an update started pushing and see what everyone else experienced.......
turdsamich said:
so, I've successfully flashed my arrive to the dft freedom rom and I love it (especially enabled internet sharing) but now I have a noobish question. Is the rom updateable? (through Zune or otherwise) or will I have to flash again and reload all my apps and contacts in order to apply an update?
Click to expand...
Click to collapse
Honestly, I'm not sure. But the chances of sprint pushing out any more updates is pretty low. 7720 is a very old build, you'd think that they would have done an update since then.
I currently have the stock Rom on the HTC Arrive on Sprint. For those of you that have done it, is it worth putting in a custom ROM?
I just finished flashing dft gold_c v1 rom on my arrive that I got today. I'm liking it a lot so far and it seems faster than stock rom. I like the additional apps and being fully unlocked for loading whatever I want. I'm brand new to the arrive but the flash went smoothly.
houdini13 said:
I just finished flashing dft gold_c v1 rom on my arrive that I got today. I'm liking it a lot so far and it seems faster than stock rom. I like the additional apps and being fully unlocked for loading whatever I want. I'm brand new to the arrive but the flash went smoothly.
Click to expand...
Click to collapse
Awesome! I want to be able to backup all of my SMS messages before I do it though. Is that possible without the custom ROM?
Was unable to save my SMS without a custom ROM so I did it anyway. so far everything is working great. I'm using DFT Freedom Gold_C V1.
Anyone know the differences between the DFT Freedom Gold and Ansar's ROM ?
I haven't tried Ansar's rom yet since there were issues with the prl and network update functions. Now that he has a new tango version out that fixes it, I may try it soon. It will be hard to leave the dft rom because it works perfectly for me and I have it all set up the way I want it. The few added features of tango may make me switch though...like video mms.
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.