I've been reading the forums for a while now and thought I was ready to give an upgrade a try. So I d/l'd the hard-spl-mfg and made sure I followed the instructions to a "t" (at least I thought). Here's where I started:
http://forum.xda-developers.com/showthread.php?t=472805
The bootloader process seemed to work fine. So I stopped there thinking I'll make sure the phone is fully functional before proceeding. But after trying *228 I still could not connect to the network. I read I may need to call Verizon to receive a new Akey. But along with this the phone would not come out of sleep. WinMobile seemed fully functional upon reset, but once sleep was initiated the phone was a brick until reset again.
So at this point I decided to update the ROM and completed step #2 at the above link. I went with the "Titan Radio ROM 3.42.50.rar" listed and now the phone won't get past the Verizon splash screen.
Any assistance appreciated.
Thanks -
Update: After continuing to read the wiki I attempted again with a dcd ROM and was able to recover. Problem solved.
Related
Ok here goes. Be nice, I'm new...
I have a Stellar in front of me (or Kaiser, TyTynII etc) which has managed to get itself into Boot Loader. I'm usually pretty good at getting these out of it but this one has me stumped, and I'm hoping someone may be able to give me some suggestions, or confirm my suspicions that it is kaput.
It's in Serial mode at the moment, showing
KAIS130
SPL-1.82.0000
CPLD-8
on the top of the screen.
So I plugged it into the computer and it nicely popped into USB mode which then let me flash it, using the file: RUU_Kaiser_O2_UK_1.82.206.1_radio_sign_22.45.88.07_1.27.12.32_Ship
This appeared to take, started the process, splash screen loaded, windows mobile loaded OK and for all intents and purposes was back at the factory reset (which is what I wanted). HOWEVER.....when I performed a soft reset it went back into Boot Loader and I'm now back at square one.
Any ideas? I can't install any homebrew ROMs on this, it HAS to be the standard ROM for reasons I'm not at liberty to post here (don't worry nothing illegal is going on, suffice to say, I shouldn't really be here!)
I have at least 2 others that are doing similar as well and would like to get these fixed also. All help/comments gratefully received and I apologise again if this is covered somewhere else.
It seems you have not done any SPL hard flashing yet.
Did you really read the Flashing for Noob sticky ? It's there .. first you need to do hard SPL, SIM/CID Unlock, then only you can change your ROM to anything.
Please go back and re-read.
Sorry. Will this do anything bad to the device, only I've never done anything like that before, I've just run the ROM flash file. I've never had to do anything like you suggested before. It needs to be put back to factory as it is going to get allocated to someone - which means I then have to install a clone over the top of this.....sorry if I'm being thick. I did read the document you suggested but that resulted in me getting more confused.
If this is not the right place for me to be, please feel free to close this thread and I'll keep looking elsewhere. Cheers.
Hi,
First of all: what do you want to do? Read this to clarify your intention
Take your time, read through the WIKI first.
After that, if you still want to flash, go to the Noob sticky.
If you don't have the passion, I'd suggest just use the phone as from factory. Reading the Wiki still will give you insight and many good tips/tricks without flashing.
Edit to addI apologize.
After re-reading again, it seems that what you're trying to do is reviving the dead Kaiser. From the SPL version, it's not yet 6.1. You can check out here to see any other official ROM matches, which what you currently use seemed to be correct.
Mod, please merge this with Kaiser stuck at Bootloader thread ..
Good luck.
Edit 2
It seems that when you did a soft reset (by pushing at the small hole using stylus?), the other two buttons (camera + power) are still pressed (or due to hardware, kept being pressed), thus resulting in boot loader displayed again?
Well that's why I couldn't work out why I couldn't get the ROM to stay.....this has never happened before! So yes, I am trying to revive a seemingly busted Kaiser. The customer handed it to me in Boot Loader mode. Usually running the RUU fixes this and we can then go about rebuilding it. However in this case it really doesn't want the factory ROM but I need it to! I can quite easily get it into USB mode and flash it by running the .exe file on my desktop - but then that's about all I can do. I can't give it back to the customer as the next time he performs a soft reset or switches it off, it'll be back in Boot Loader...ARGH!
Oh, and apology accepted!
And another thing, I just tried running the exe file again and got as far as the screen alignment and the poxy thing just locked....cue soft reset and back to Boot Loader. Me not happy.
Edit: A quick check of the Hardware and all the buttons appear to be OK - nothing looks like it's stuck down
If you want to take the looooong road, perhaps you can do flashing Hard SPL, unlock SIM/CID and then flashing any other ROM/Radio. Once you get a stable working device, you can flash back the OEM using this method
I'm not sure if this custom RUU can help: http://forum.xda-developers.com/showthread.php?t=334890
I haven't tried that, so it's just an idea for now.
Thread closed.
If you are still having problems with the bootloader check out my sticky.
If you need help with the flashing process check out mskip's sticky.
Only create a new thread for new issues that have not been discussed before.
Good luck
Thanks
Dave
OK, I too skim read (I read a lotta threads ).
PDA-Princess
I've sent you a PM.
Dave
It seems I'm just another one of the masses who rushed in to flashing their ROM/Radio/etc and now my Tilt is stuck at the bootloader. I've run through the "recover" process and every time I re-power the phone back on, I'm stuck in the red/green/blue/white screen with KAIS1*0, SPL-3.56.0000, CPLD-8 in the red section.
I would greatly appreciate any help in getting my phone back into working order.
You can get me on AIM at ygafip or msn at [email protected].
Thanks in advance.
Sorry - posted in ROM development. Can you move to the appropriate forum?
And you can disregard this ... I was able to successfully flash back to a stock ROM that I downloaded from HTC's website - I then followed the noob guide step-by-step and it seems to be working. I guess what I did wrong was I didn't install the HardSPL thing ... that seems to be the only thing I did differently. I have successfully installed the HardSPL, successfully unlocked my SIM thing, I'm currently installing the new ROM and then should be able to successfully install the new radio ... I guess that's the 4 steps I need to do.
Glad it's sorted.
Dave
Ok here is a step by step of what happend.
I bought a unlocked HTC Hero originally T-mobile branded.
I followed the instructions on Unlockr to Root the phone.
I then downloaded the 2.3 Modaco rom and flashed it to the phone exactly as described by Unlocker. HOWEVER as suggested (strongly) on the Modaco post in these forums I did not do a nandroid backup of the original HTC(t-mobile) rom on the phone.
When i restarted the phone it simply goes from the power up screen, to the HTC screen, then to the Tmobile branded screen then to a black screen the restarts. During this cycle no buttons work. If i take the battery out and turn the phone on I can get to recovery etc.
How can I either install the rom correctly or bring it back to how it was or in any way make the phone usable again.
I hope you can help. I'm overseas with no money so I can't afford to have wasted this, im about to cry(figuratively not literally haha).
sorry wrong forum my bad. please delete!!! Sorry guys!!
I'm totally new to flashing phones, but having trouble with my touchpro.
When I load it up, it gets to a screen with the HTC logo and will not load my today screen. It's sluggish, won't autosync, and frustrating the hell out of me to be quite honest lol. The messaging and phone still works. Haven't tried the internet yet but everything takes ages to load. Also my unlock code to get into EPST (000000) will not take. Weird.
Anyways, I've decided I've had enough (this happened before) and just want to flash a new ROM to the phone. I've read the flashing for noobs article and it told me to autosync it up and use Hard-SPL. But I can't autosync - how should I go about doing this?
I'm not worried about backing anything up. I can get all my numbers back there eventually...
I mentioned that this problem has occurred with my phone before...usually I waited a day or two and the Today screen just showed up...but it's been a few days and it's not coming back....I think I am using Hofos or Holos or something like that as my current ROM for Cricket service if that helps....
Put your phone into bootloader mode (soft reset while holding down the power and volume down hard keys). You'll come to a tri-color screen that should read "serial" at the bottom. Connect phone to your computer and wait till it "serial" changes to "USB". Now run the Update Utility to flash the hard-spl and repeat for a new rom after unlocking it.
you can also do an SD card flash. check out the sticky for details.
I've never flashed HardSPL to the phone (at least not that I am aware of - I got this phone from someone else)...Will the bootloader still come up at first? And can I flash the phone without having hardspl on it?
bondra76 said:
I've never flashed HardSPL to the phone (at least not that I am aware of - I got this phone from someone else)...Will the bootloader still come up at first? And can I flash the phone without having hardspl on it?
Click to expand...
Click to collapse
Put the phone in bootloader. On the tri-colored screen, you should see SPL - 1.90 OLIPRO. If not, then the phone isnt unlocked. The phone has to be unlocked in order to flash a custom rom. Check the ROM development thread for more information. I should add that you need to make sure you have a CDMA phone or GSM phone. They use different unlockers. The OLIPRO one I mentioned above is GSM. The CDMA reads SPL - 0.37 CMONEX.
Cricket is cdma, isn't it? You better do some reading before flashing, because the single most critical thing you will do is flash hard spl. If you flash the wrong one, there is no going back and your phone will be toast. Go to PPC Geeks or the cdma forum here, and make sure you stay well away from the 1.90 Olinex hard spl.
Farmer Ted said:
Cricket is cdma, isn't it? You better do some reading before flashing, because the single most critical thing you will do is flash hard spl. If you flash the wrong one, there is no going back and your phone will be toast. Go to PPC Geeks or the cdma forum here, and make sure you stay well away from the 1.90 Olinex hard spl.
Click to expand...
Click to collapse
Thanks you're right it is CDMA. Thanks for the help tho guys I will head over to the CDMA forum
I am trying to attempt messing with this type of thing for the first time so noob handling will be required. My reason is simply my phone is a nice wallpaper display three days after the ota from tmobile 1.63.531.2 710rd.
I began by trying to follow:
http://forum.xda-developers.com/showthread.php?t=1505999
To no avail. Of course I noticed afterwards that for some reason it says to turn s-on in the header... exactly the opposite what what I need to flash the phone back to (PG59IMG_Doubleshot_TMOUS_1.28.531.9_Radio_10.48.9007.00U_10.12.9007.07_M2_release_201815_signed.zip) I have had problems with the phone ever since its first ota a year or so ago. With this latest ota the phone is more or less bricked as of the phone using power saver when I went to sleep last night... Wont call or check into the network...no dial tone. Took me 3-4 restarts for it to even show the antenna symbol and the 4g icon in the taskbar.
My phone is set as S-on for now. The only instructions I have found through the search tool relay how to do it to the sensation... I believe that is the mytouch 4g not slide. However I have the slide which is doubleshot. So my question is, is this instruction on http://forum.xda-developers.com/showthread.php?t=1192300 safe to use with the doubleshot since the (T-Mobile branded HTC myTouch 4g Slide ( doubleshot ) Developers Reference) page links to it indirectly. Using the link at the top of the how to S-on after s-off... again the opposite of what I need so I tried following the link at the top of that page " Guide to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on " which takes you to the s-off instruction page for the sensation (Link: http://forum.xda-developers.com/showthread.php?t=1192300 )...I am guessing that it will work and sensation refers to HTC sense, but I don't care to make the mistake of doing it wrong and bricking my phone due to being derp.
I know there is a bit of overdone explanation and redundancy in the addresses I have left here. I am just trying to cover all my bases thanks for the help in advance.
The short and sweet is I need a link by link list with instructions on how to step my phone back for multiple reasons. First the recent OTA more or less broke my phone and I don't want a refurb phone with inferior parts from Assurion...(They were in class action lawsuits for this in the past.) nor do I want to pay 130$ for said replacement. Next from what I just read the 1.63 update has some serious security compromises that are awaiting response from HTC for an update. Basically it gives full accesses to all your data to include your sim and SD card contents to all apps. Regardless of user specified/agreed permissions.
Following ANY routine or procedure for another phone is just too dangerous & will never work anyway. The bad part being you may very well create a brick in the process. If you have the MT4G SLIDE, this is where you will get all that you need so don't even consider other threads.
Since you've done the OTA & are sitting at Hboot 1.63.XXX now you will HAVE to get S-Off before you can go back to your previous Hboot. To DO that you will have to follow the instructions HERE.
If all you are wanting to do is start flashing ROMs, then the instructions you need are HERE.
Keep us informed & we'll try to help if you need it. Good Luck!
WeekendsR2Short said:
Following ANY routine or procedure for another phone is just too dangerous & will never work anyway. The bad part being you may very well create a brick in the process. If you have the MT4G SLIDE, this is where you will get all that you need so don't even consider other threads.
Since you've done the OTA & are sitting at Hboot 1.63.XXX now you will HAVE to get S-Off before you can go back to your previous Hboot. To DO that you will have to follow the instructions HERE.
If all you are wanting to do is start flashing ROMs, then the instructions you need are HERE.
Keep us informed & we'll try to help if you need it. Good Luck!
Click to expand...
Click to collapse
Thanks for the hasty post reply any other suggestions...I have win7ult 64bit. Or will will juopunutbutter work even though they have the below disclaimer?
"Supported Operating Systems:
We only support Windows 7 32bit or Ubuntu 12.04 (and newer) 32bit, you may use a LiveCD if you have the wrong OS installed natively. Win XP 32bit might work for you but we do not support it as we did not test on it."
Also, this, "Be on the Stock RUU and be rooted (have superuser flashed). No other ROMs are supported, Fresh ROM will not work regardless of what you have read elsewhere."
-I am not rooted. Which is something else I want to accomplish so I can set up firewalls that block certain things.
Oh btw provided I can get this phone working again I am also going to attempt to reflash my older mytouch 3g... back to original as well that thing worked better than any of the current phones for my purposes before it got the update prior to the 2.2.1... the original update didn't work with adobe which is fine with me, people need to move on from adobe's garbage anyway. Specifically with the old mytough 3g though that really did add functionality at the sacrifice of sanity since it slowed the phone down so much. On that note though I may just put on a custom if I can get comfortable with this stuff. The last time I looked at a pc this hard was back in win98se when you had to know how to do tricks to make it faster like modifying available rame to twice as much above and below physical ram and a few other tweeks I have long forgotten.
That brings me to another question. If I go custom rom and unlocked this looming threat of brick is weighing in on me. If a phone is bricked is it possible to recover using some of the same tools that bricked it in the first place... flash install original rom as a fix? Just trying to see how much margin of error I have to work with.
Thanks again.
PS who do we talk to about backing off all the java on the site since it is so compromised right now? This sight has more java permissions than most sights of ill reput... though I have been reading these forums off and on for a while so I trust it more than most with this much tracking. I doubt patch 11 actually fixed the issue...since the day before they said it would take two years or more to actually resolve the java zero day exploit.
You should be fine with your pc, I used a 64bit win7 too. If you're worried dual boot linux.
Your my touch 3g is rooted diferentley, go to that forum for details, its not true radio soff but its close enough.
If you brick it its dead, depending how it was bricked jtag could bring it back to life or this phone is part of the unbricking project which will fix some other bricks. Problem is people use brick as a term that means a whole lot of things so its hard to answer. Usually a brick is forever dead, most people don't actually brick their phone though and usually have to be neglecting things to do it.
As for java... just read up on a bunch of trustworthy places for more info and understanding
Sent from my HTC Vision using xda premium
I'm afraid I just don't know about Win 7 64bit and how it will react but I'm sure there has to be a person or two around with experience concerning that OS. It may very well work fine. I CAN tell you that the "wire trick" (junoptobear?) will work fine on MikTouch because that's what I used. It's a stripped down GB stock ROM which is all you're really looking for. Why....I don't know.
As far as bricking goes, there's not a GREAT deal to worry about as long as you follow all instructions to a tee. You REALLY don't have to even have S-Off to flash ROMs as you read in that link. You just need to flash the kernel after you flash the ROM. It WILL limit a few things you can do but not ROM flashing.
When it comes to rescueing a bricked device though, there are only a very few instances that can be done as far as I know. But I'm no developer either. But if you can make it to your bootloader and/or recovery you not bricked. It may be a hardware of software issue but most of the time you can come back from those.
As far as the Java issue you spoke of goes, you may be able to get an answer to that one by PM'ing one of our moderators or admins.
I want to step it back to previous versions because they worked better...primarily the first version... Also, I am not seeing a guide that refers to doing it to the 1.63 patch. keyboard hasn't swyped right since the first ota update. Also my intent is to root an older version so I can remove crapware like dt sync, friend stream, kidzone, tmobile mall, tmobile tv, tmobile setup, telenav gps, and zinio reader.
X-Lander said:
I want to step it back to previous versions because they worked better...primarily the first version... Also, I am not seeing a guide that refers to doing it to the 1.63 patch. keyboard hasn't swyped right since the first ota update. Also my intent is to root an older version so I can remove crapware like dt sync, friend stream, kidzone, tmobile mall, tmobile tv, tmobile setup, telenav gps, and zinio reader.
Click to expand...
Click to collapse
It's a simple flashing process but you HAVE to achieve S-Off first with the "Wire Trick". You can flash it forward without S-Off but not backwards. Does it work at all or is it just frozen to some point in the boot process? Can you access your SDcard? Can you boot to Hboot & recovery? These are a couple of things you will have to be able to do to go forward if I understand you correctly.