Database Info

TILT with Dutty's WM6.1 and no signal

Hello there you xda geniuses! I need a little help... I have an ATT Tilt running Dutty's WM6.1 WWE radio 1.65.14.06 protocol 25.81.40.02w. I bought this phone with this ROM, so I don't know what all was done to it, but the problem I am having is that from time to time, the phone and data switch off to 'no service' and i cannot get a phone signal to register, unless i soft reset it. I have read of this on several lists but cant seem to find the definitive answer - do i need to flash the ROM again, or with something other than the version it uses in order to get this resolved? I am missing calls and messages when it is down. Please save me!!

Hard reset the device first.. ..this is what I do with all my new purchases
Reflash the radio if you do not wish to hard reset. This will keep your data unlike a hard reset.
If this does not work reflash the device with a new ROM.
There are plenty around here. Check the WiKi if you want to know more about those ROM's.

When you say reflash the radio, can you elaborate? I dont know what file i'm looking for. You have already been a big help, thank you!

Why don't you post this in the appropriate thread and maybe you will get more answers????

If I knew what thread that was, I would have posted it there. Perhaps you could tell me where it should go before I drive over this phone with my car tire.

When you flash your radio it means that you only flash that part of your device that's responsible for the radio\data\gps etc.
If you check the HTC Kaiser in the WiKi you will find multiple links to radios that are available.

seriously urgent help needed with gsm htc touch pro!!!!!

hi everyone,
iv got a htc touch pro,to be precise it is my first ever smartphone and i have tried to flash and add a new rom to my handset.i read all forums and threads on various sites about how to perform a successful flash and rom.installation of the rom were successful,but my phone does not load up to main screen at all!does that mean my touch pro is bricked????however,i can go to the bootloader and try a hard reset,but that doesnt work either.i have found out that my handset was already unlocked using Olinex.
Please can anyone help me out???im really really stressed out.
many thanks.

Ok, best thing to try is to download the official factory rom.
Start the phone and get it to the boot-loader screen.
Plug it in to your PC and wait for the word USB to show up at the bottom of the phone's screen.
Next run the factory rom installation on the PC and go through the steps. It should hopefully flash fine back to the original OS.

thanks alot,that really helped!!!!you havent a clue how stressed out i was when that happened.anyways,i could do with some more help.since i bought this phone,my net has NOT been working.it was officially branded on vodafone but it was unlocked by previous owner.i have ordered official settings from Htc and o2 themselves and still no result.anyone have any solution(s) for this problem?????
like alot of people have said to me,without net on these smartphones,the TP is nothing!so if anyone has a solution,please DO tell me about it
Many thanks.

I would disagree that without internet smartphones are nothing.... but that's not the point. Do you know which ROM you're using?
Are you using a stock rom? if so, from which company.
Alot of people here have their signature to show what rom/radio/phone (type) they have. it makes it easier for those who want to help to provide answers or suggestions faster and you wont have to get nagged asking the same question everytime

Firstly - slow down!
Not quite sure if you have a problem now or not, and if you do, if its the same as you started with.
From what you have written:
You have read some stuff
You have flashed some stuff
it hasnt worked as you expected
you asked for help on here
you may have flashed some more stuff
you may or may not have a problem still.
No offence, but its pretty tricky to offer much in the way of useful assistance when we dont know what state the phone is in.
Dont panic - enter the bootloader. Note what it says (SPL)
Reset, note the rom & radio versions.
See what works & what doesnt.
Read the forum rules - especially about starting new posts and how to name them (seriously urgent help needed isnt very descriptive). Use the search function to see if your problem has been answered (lots of connectivity issues will have been). If you still are having problems, reply to this post, or make a new one if more appropriate, saying clearly what you have (including rom & radio as appropriate) and what you are stuck with.
Oh, welcome to the forums.

Bricked cdma htc hero after ruu 1.56 Semi Solution

Ok, just like all of you I have rooted, experimented to the limits and pushed them well little did i Know is that you cant reflash the 1.56 ruu so needless to say I ended up with a brick but luckily for us it will still connect in fastboot
so this is a solution to at least get it up and running
Pros-
Reactivate your phone since it will be formated
All functions will work
can still root, install .apk's use wifi etc
camera etc
so the pros are it will operate just like nothing ever happened now to the con's
YOU WILL HAVE TO DO THIS EVERYTIME YOU TURN OFF YOUR DEVICE
Ok here is how to fix it
Connect your phone to your PC
open command and navigate to your android tools folder
type in
fastboot devices
make sure it detects your device
should show the HTC logo on your phone
now simply type
fastboot oem boot
wait a couple minutes while your phone reboots
viola you phone is back to running again...just dont turn it off LOL

can you launch the RUU again and (hopfully) have it restore your phone correctly?

You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet

rayborn said:
You can launch but it will still fail like before, I havent been successful in finding a full solution as of yet
Click to expand...
Click to collapse
hmmmm interesting man. honestly you should be able to rebuild all the / partitions. such as /misc and /radio. we need some linux junkies in this thread to tell us how to rebuild failed / partitions

This is amazing. Sure did work for me. I just wish there was a way to get it flash the original radio. I have only had this thing two weeks and would love to take it back and exchange it, but I am just paranoid since it shows radio 2.41.04.02.03.

wait, what exactly did you do to get your near-bricked phone?
you used the 1.56 RUU on your phone that had a 2.xxxxxx radio?

have you tried both of the RUU's? the original and 1.56?

My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution

did you try the 1.29 RUU?

yeah i tried every sprint hero ruu i promise you i left no stone unturned trying to fix this

BRILLIANT!
I can't tell you how impressed I am that somebody has found what i now consider to be the first step towards getting the RUU 110 error solved.
I still feel that the issue comes down to the lack of ADB that seems to happen once you get 110... maybe a driver issue on the phone vs. driver issue on the computer? after all the RUU starts failing on all the ADB commands when you check out the RUU logs...
sorry i can't help take it from there, i returned my phone to sprint inside of the 30-day window and just told them something i installed form the market "bricked" my phone...
I eagerly await your results though for a final step towards solution, as I am dreading the day i have to RUU my phone for whatever reason that may be, although I've been running a personally customized Pancake ROM for almost a week and totally happy with it so won't be doing anything until 2.1 is official...
R

rayborn said:
My phone was the Sprint Hero *with Google model, so I had rooted it and loaded a custom rom on it etc and was playing around with it but I wanted to go back to stock so i flashed this ruu
RUU_Hero_C_Sprint_1.56.651.2_signed_release
And BAM at the end error 110
wouldnt boot anylonger
spent all day on figuring out this solution
Click to expand...
Click to collapse
Same exact thing for myself. Multiple people said the way to go back to the stock radio was to use the RUU. I tried both RUU's and same results. Now I am just trying to decide what is better.
Live with this and hope for a better option to come or take back a "bricked" hero that shows Radio 2.41.04.02.03 and hope I don't end up getting charged later.

IMHO I think the best thing for you guys to do is wait for our 2.1 update, which will more than likely have a smiliar radio update. Then you can just say the update bricked the phone.
If we get the same radio version, then just take it back, if we get a different version then maybe we can find a file to edit the number to make it say what ever version you want it to say, something like editing Build.prop. Then Sprint has nothing to ask questions about. Should be out in a few weeks if the rumors are right. Maybe you can deal with this soultion until then.
As far as the don't turn your phone off issue, mines been up for 13 days. I hate turning it off, partially because of the missed emails and partially because I worry that it won't come back up.

Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?

SamXp said:
Subscribing. When Sprint releases the official 2.1 in a few weeks, I was planning on using the 1.56 RUU and then doing the 2.1 update. Apparently this isn't going to be possible since I did the Radio update. What is going to be the proper way to get the 2.1 update through Spring for phones with the Radio update to keep from bricking a phone?
Click to expand...
Click to collapse
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?

mginther said:
I was of the same mind, but reading this thread has me wondering the same thing. Are we just screwed now?
Click to expand...
Click to collapse
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen

tatonka_hero said:
There's been plenty of people who have flashed back and forth between the radio versions, using the RUU programs...there's only been a few that have bricked from what I've read.
It's still a bit iffy on whether or not it's actually safe to go between the two, but it shouldn't matter since the new radio versions apparently work just fine with all ROM's that I've seen
Click to expand...
Click to collapse
True, and if we elect to continue to use either a Fresh or Damageless version of an official 2.1 Sprint ROM, then we should be ok. But if we wanted to go to the Sprint ROM, there are going to be a lot of bricked phones if there isn't a way to understand what is going on when a 1.56 RUU is used over a phone with the 2.x Radio update.

Just wanted to pass along some more information in case anyone else is having this problem. I had reactivated an old phone temporarily since this one was bricked. This morning I reactivated my hero due to this semi fix and immediately I could call and textimg was fine, but i kept getting vision error 67 for data. Sprint reset my data about three times and it never worked. I tried updating my profile multiple times and it never worked. Finally I Ran the RUU again and sure enough after a reboot or an "oem boot" I had error 67again. I went ahead and updated my profile and this time it worked and data started working. Still hoping someing else comes along though.

well I think the issue here might be that it does not have the recovery backup on it after you do an RUU. I could be wrong but who knows? I would say install flashrec-1.1.3-20091107-2.apk on your phone once you are able to get it up and running then flash the recovery backup and restart. That could possibly fix the issue? I have the files if anyone needs them, I'm not sure how to upload them on here...
~Danny

I'm not sure if it's possible boot into recovery console using this method, but if you can, has anyone tried manually flashing the old radio in the same manner they flashed the new one to revert back and then RUU. Perhaps that may do the trick.
My phone isn't bricked so I can't try it out, but seems like it might be worth a shot in theory.

How to get my TP flashing again

Hi everyone,
So I updated the stock SPL back to my phone while having a CDMA rom on my device. Looks not like a problem at all, but appearantly it is when your phone is not a CDMA rom After that the phone won't boot anymore.
Since then I am not able to update my device to ANY rom, not even the stock rom. The updater keeps giving me the famous 262 error and hangs at 0% of the update. XDA-user orfeo_b has messaged me a while ago that he had a task29 program for windows 7 to format my phone. But he didn't respond to my message. So my question is: is there anybody who has this program for my phone? and if not, is there any other possibility to empty/format my phone?

Why did you create two threads in the same forum? (THREAD LINK)
You not want to post HERE, did you even bother to do any searching in HERE
You do know the FUZE is GSM, correct?

R^7Z said:
Why did you create two threads in the same forum? (THREAD LINK)
You not want to post HERE, did you even bother to do any searching in HERE
You do know the FUZE is GSM, correct?
Click to expand...
Click to collapse
sorry, a second after saving I realised that my topic was a question so I posted the topic again accidentally.. I searched the whole forum for weeks but didn't find any solution. As I said, I accidentally flashed a CDMA rom to my GSM phone.

User benjamminzIS started the thread HERE
Perhaps give that a once or twice over and see if it works for you. Be sure to leave some feed back if it does!
Additionally, I must confess that I skimmed your post because you posted twice and didn't think anything of it after the fact. So I apologize if I came off slightly rude. Was not my intent!

There's a pretty good chance your phone is dead now. Flashing the stock spl after bricking your phone with a cdma rom is probably the worst thing you could have done. What were you thinking? With the stock spl, you can't flash task 29, or anything, for that matter. I guess you can try flashing hard spl, but you have to keep in mind that this 'stock spl' is not in fact the real stock spl (it's a patched stock spl that is capable of over-writing the hard spl). I'm not sure if it can be over-written with hard spl; I guess you'll find out. If you had read any of the posts on reverting to stock for warranty purposes, you would have seen that the absolute last step is flashing the 'stock spl', because once you do that, the device is locked.
Now, if you also flashed a cdma 'stock spl', then you can definitely throw the phone away.

[Q] Need to flash my phone back prior to the recent ota (1.63... doubleshot)

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.