I swear, these ****ing phones are cursed. I just got the replacement phone last night, and I started on rooting it this morning. I followed crypysmoker's instructions (since they worked flawlessly on my first myTouch), but something went wrong somewhere. After flashing the SAPPIMG, the phone won't boot past the splash screen, but loaded fastboot. So I continued from there and flashed the original radio and hboot, then recovery, etc. That's where things got weird; it wouldn't boot into recovery at all. So I decided to start over. Now, for some odd reason, the damn thing doesn't even turn on! And the LED on top doesn't light up to indicate that it's being charged. Nothing. So now I'm stuck with two myTouches that are absolutely useless. Any suggestions?
You could see how far you can throw them away in a trash can like your playing basketball but with a couple bricks instead of basketballs
Or I could skip them like rocks across a pond.
Lol it wasnt the 1.2 but the original mytouch3g.. and yeah if you **** up the
radio's and stuff it will brick. It will go into fastboot and you will be able to use it..
once the battery/phone errors enough it eventually dies out.. and you need to get
it replaced. Idk what ta say.. since that "IS" the replacement phone lol..
Idk how many replaces you get but if you dont get another, you can part that phone
out to a local electronic cell repair store and make like 50-100$ and use that as
a down payment for another phone.. That way your not "completely" ****ed lol
Well you should first check to see if they sent you the same board (32A or 32B) and check the radios and SPL. You cant assume that because it worked on your other phone that the same process will work on this new phone.
Thats what im getting from you, at least thats what I read and deducted what happened.
You can't blame the phone and call it a piece of crap. I have had this phone for a month (MT3G 1.2), and there have been times that I have messed it up. But if you read instructions, search google and use the right process, this phone is impossible to brick. I have got mine stuck at the splash screen. I have gotten mine so the touchscreen doesnt work. I have also got mine where I have no recovery. But I fixed it (by reading and searching) and I got mine back to working order.
I love this phone. I wish this had UMA support
Nope, the phones all had 32A boards, though one had a different SPL. The same process worked on the THIRD phone and I'm running Cyanogen's 5.0.7 test6 ROM now, but I'm NEVER going to attempt flashing a radio nor an SPL without any good reason. I never did manage to fix the other two, even after searching extensively for a possible solution.
And what the hell is UMA?
Its a functionality that TMobile has on their Network.
Unlicensed Mobile Access or UMA, is the commercial name of the 3GPP Generic Access Network, or GAN standard. GAN is a telecommunication system that extends mobile voice, data and IP Multimedia Subsystem/Session Initiation Protocol (IMS/SIP) applications over IP access networks.
Its Wifi calling.
Related
OK, I know that may look like a dumb question (and maybe it is!!!)
I have just unlocked my Vario 2 using the "Pof" method with both Sim and SuperCID.
Problem is, my phone needs to be sent back (long story - but basically I am getting a replacement Vario 3). Now obviously I am concerned they will tell me "sorry youve been playing with your phone sonny - its no longer under warrenty", so need to get it back to factory settings if I can.
I appreciate a hard reset will basically wipe any files I have, contacts and settings etc, but will this remove the unlocks that have been done? ie It really does go back to factory settings - or do these unlocks stay on there?
I have been searching the forum and WIKI, but not found the solution. I did think I would need to install a T-Mobile Rom - but all I could find was a hungarian version - which whilst in English, would probably look worse than as I currently have it!
Any help appreciated.
Thanks
EDIT:
For the record, if it makes any difference:
ROM Version 1.21.110.3
Rom Date 06/19/06
Radio version 1.16.00.00
Herm300 IPL-1.01
SPL 1.40.0lipro
a hard reset simply formats the internal drive on the phone and resets it to the factory settings.
generally t mobile wont bother looking at things like that, i unlocked my vario, dropped it, it smashed, they just replaced it after trying to repair it.
A few people have flashed new roms and bricked it, sent it back, tmobile are none the wiser, they are probably unaware people to this to their handsets!
we are all just stupid customers as far as they are concerned!
personally i wouldnt worry about it!
andaroo said:
a hard reset simply formats the internal drive on the phone and resets it to the factory settings.
generally t mobile wont bother looking at things like that, i unlocked my vario, dropped it, it smashed, they just replaced it after trying to repair it.
A few people have flashed new roms and bricked it, sent it back, tmobile are none the wiser, they are probably unaware people to this to their handsets!
we are all just stupid customers as far as they are concerned!
personally i wouldnt worry about it!
Click to expand...
Click to collapse
OK thanks for that. So I assume a hard reset will not over write anything regarding the bootloader radio change and unlocks? I appreciated that it resets the OS - hence the question.
I agree that they probably wouldnt in most cases look into the phone and check, but they have put a note on my account about "charging if not found faulty".
The problem I have been getting is missing calls - even if I am in a strong signal area. I actually work at Waterloo Railway station - and I would doubt too many places would get a better signal! An incoming call is made, my phone doesnt ring and the caller gets a single ring, then nothing. From what I can now gather, this may be to do with the cell shaking hands but not really being connected. ie the phone/cell are duping each other. This appears to be a 3G issue (so is probably likely to still be there on exchange.) Now the silly thing I have noticed; the phone seemed fine until I got web'n'walk put back on and the problem happens once I have been online. Strangely at the moment, I dont think the problem is persisiting (ie Im not aware of missing calls - though of course thats difficult to quantify unless someone tells me!)
Anyway - I have a feeling they will be looking more into this phone as this replacement will be my 5th! (The previous had similar problems with calls being made or incoming that would just fall over before being answered and the signal being completely lost when it was happening. Slightly different this time - but sound related!)
So will there be a way to put it back to being locked and the correct bootloader etc being shown?
Many thanks
I had the same problem with rejected and dropped calls, tmobile couldnt care less from what i learned or are unaware of the problem! try this
1. lock the phone to gsm only (this solved it pretty much straight away)
2) remove the voicemail from your account
3) If you are using gprs data, you will rarely get a phone call through, and by using it i mean looking at web pages or having programs update in the background.
Downgrading the bootloader is way above my head so i wouldnt like to advise.
As regard to relocking the phone to the network, i dont think thats possible, in any event, why would they check the simlock if the phone is having problems with calls!
If its your fifth handset, you should be looking at changing the model at least because thats ridiculous.
It sounds like a network issue rather than a handset problem!
andaroo said:
I had the same problem with rejected and dropped calls, tmobile couldnt care less from what i learned or are unaware of the problem! try this
1. lock the phone to gsm only (this solved it pretty much straight away)
2) remove the voicemail from your account
3) If you are using gprs data, you will rarely get a phone call through, and by using it i mean looking at web pages or having programs update in the background.
Click to expand...
Click to collapse
Yeh, the problems on this phone didnt start until I began using the net again. They did suggest switching off 3G, but since I bought the phone specifically on the promise of a fast connection and HSPDA speeds, that really is an unacceptable solution! I appreciate that signal varies etc - but if a central location where I work isnt good enough, then T-Mobile really shouldnt be advertising themselves as a 3G network!
As it happens, voicemail was switched off on the account. It got put back on again a week ago - and sods law - things now seem to be working, though internet speeds are still very slow.
As regard to relocking the phone to the network, i dont think thats possible, in any event, why would they check the simlock if the phone is having problems with calls!
Click to expand...
Click to collapse
Dunno really. Its just a concern they will and then use it to wriggle out of an exchange!
If its your fifth handset, you should be looking at changing the model at least because thats ridiculous.
It sounds like a network issue rather than a handset problem!
Click to expand...
Click to collapse
When I phoned, I was just looking to get a repair, but it was them that offered a Vario 3 which I accepted. It was agreed for them to be sending the set to me (last Thursday) but all that arrived was a grey bag to send my old one back. I spoke with them at great length again last night and suggested a straight courier swap so I wasn't without a phone. They went through to their repair department, who have now flatly refused the phone change - despite it being agreed already!
Anyway I spoke to another manager who went through my "book" of notes and quoted the sale of goods act and merchandisable quality thing and he has agreed they really have to address this. He is phoning me back today and he did come across as helpful and reasonable. (The second one in 2 weeks - must be a record!!!)
I do agree though, that this issue is likely to be the network and not the phone. I would really love to use O2 as at work and home I get 100% coverage and never had any problems at all - but I ain't paying their data rates! Maybe 3 will be ok - but again, when I had them a few years back, at home they were dire so never bothered again. But one thing is pretty certain, in 5 months time, T-Mobile will be history unless they make amends in a big way and these problems become non existant.
Thanks for your help..... its appreciated.
Hi all,
Firstly apologies for the long post, and thanks for all the info that is up here... however I have managed to get quite lost. I'll try to take you though the whole story as much as I understand it, but I woke up this morning and decided (after 8 months) to finally root my android.
That was 8am, it is now midnight, and I've had sandwiches while working at it, all day. It has been in various stages of bricked, and I think I might have just sent it back that way - should not be playing with it when tired.
Things I have
1 x UK Vodafone HTC Magic, doing return plus power = 32B, HBOOT-1.33.0009 (another story here).
1x 16GB SD-HC card
1x 1gb Card
1x cheap nokia I can use as a reader for the 1gig card, but it can't handle SD-HC
Anyway I started off with the 1 click root idea, which obviously doesn't work these days, so followed the next link, then the next, finding I need to do the 'goldcard' method.
theunlockr.com/2009/08/14/how-to-root-your-mytouch-3g/comment-page-3/
Anyway I'm not sure where all the time has gone (16 hours now), but I have learnt what an SPL was, flashed mine to an ‘imperfect’ one, managed to flash it to deteethed google, then cyanogen on top, but it would never boot, and just hangs saying HTC Magic, then managed to flash it using 'myhero' which gave me a Hero like phone.
However I now seem to have messed it up again as I'm determined to do the cyanogen mod - I really want to be able to tether, and lots of other bits and pieces.
The state at the moment therefore is I have it all working with fastboot, and can easily get the Amon_RA recovery image going, but the cm_recovery one makes it hang and do nothing. If I try and replace the recovery section using fastboot it tells me it has failed (I forget the exact message).
I can therefore upgrade things using the Amon_RA backup, but as I said things don't seem to entirely work, and at the moment my phone is hanging (I think as I'm tired I've overwritten my backup). I'm also not sure if this goldcard method is working – I asked a question in the thread and it seems that it might not be.
I guess I'm just looking for a few pointers, after 16 hours sat here I'm generally pretty frustrated and totally lost - there is a lot of information, but there are so many permutations of hardware, and a lot of the information is now out of date. Trying to take everything in as well as deal with a specific problem may actually be beyond me Which is something I hate- being the newbie needing help with a potentially simple problem (though I have had a good go at it).
I'm really not sure what stage the phone is at, have I rooted it? After all I can use the myhero rom, but on the other hand I can't do what I want to do, so therefore is there a problem? Exactly which step makes it ‘rooted?’ as every guide is obviously a chain of events to make it in to something else. I'm honestly not sure, but it isn't a fun feeling – I’m stressed and at the momentI have no phone just a brick that I can fastboot to recovery, and a bunch of backups as soon as I get it working again.
I really had no idea it would be this difficult, and am a big angry at Google/HTC for making it so - it is easier to get Hackintosh working than this! I’ve also managed to do hundreds of other similar things without any problem – Xbox Media Center (including soldering), and a few more spring to mind, all to use the hardware I already own! My hardware!
Anyway advice and pointers are appreciated, as although I've learnt a lot today, I'm still blundering about, and it is a matter of time until I cause serious damage in my attempts to make it better, al alternatively just throw in the towel, but then I don’t think I can go back as I have a horrible feeling that the restore I did didn’t work.
Again anything you can offer is appreciated, and if you need more detail, I’ll do what I can!
Anthony
Also just to add I've tried searching, which is partially how I've got myself in to this mess - solve one problem but make another!
Also I do have my APN settings, so when I get it installed, I can get my google account workign with it - I think i've had to do this about 6 times now! So if there is a way to get it in to 'myhero' which I think I can do again, and download an apk, then I should be able to do that.
Ant
There is a lot of information and everyone is recommended to do their research before rooting the phone.
That being said, it sounds like your phone is rooted if you can boot into recovery and load up a sense ROM. It'd been much easier to follow cyanogen's wiki instructions for non T-mobile 32B Magics. I also have a vodafone Magic and I rooted my phone successfully using the method.
Not having used the goldcard method, I don't exactly know where it went wrong. Have you done full wipes before applying a zip file? Stuff like that which might be easily overlooked?
Yeha I've been wiping it all before flashing, so that isn't the problem.
I also did as much reading as I could before starting (and watching the youtube guides before doing anything), but I guess a lot of the problems were unexpected (aren't they always?), for example I only found out half way through that I would need to flash the SPL, and it took me 40 minutes to figure out what SPL was, and what it did, then another 40 to work out how I was going to do it, then 40 to do so.
I have been following guides though - for the cyanogen one I get all the way down to flashing it with the detoothed google build, then cyanogen (obviously wiping before doing these). All the steps appear successful but then it doesn't boot.
The phone is also a rather strange one, a vodafone branded one that says 32B, but I'm sure it has more RAM.
Currently trying 'method 2' from here
android-dls.com/wiki/index.php?title=Magic_Rooting
to see if that works, but I'm not optimistic.
Yup 15 minutes laters same problem - it hangs on HTC magic screen, which is exactly what it does when I go for the Cyanogen one.
I'll goign to try and google for other roms, see if any of them work sucessfully (and might provide a bridghe to what I want to have.
Again however anybody knows good guides, sites or anythign else let me know.
As I said a big problem before is I'm reliant heavily on google, and a lot of the informaion out there is useless, as it is out of date in a big way. Also I don't know anyoen else who has doen this, so recommendations ofmethods/roms are dependent on my reading, not wword of mouth (which is generally better).
Ok I've tried the method 2, defiantely no sucess, went back to the myhero (which performs awfully, so much lag!), and have now tried flaskrec.apk on there.
It does not backup, but then bypassing that step, it gives me the error 'Flash failed'.
Really stuck now, and no idea what to try, any suggestions at all would be helpful. I'm almost at the stage of wishing I'd got an iphone :-(
Hello all,
I have recently upgraded from my g1 to an HD2. HD2 is a great phone but still miss android . Anyways, today I wanted to get my g1 to work without a sim or data plan and was about to start working on it when my g1 screen dimmed to just the blacklight with a black screen. I turned it off and tried turning it back on but it just comes up with the backlight on a black screen. It does not even get to the G1 screen. I cannot get to recovery mode or any other mode for that matter. I have searched around but not found any real solution to this problem (if there is one). I am thinking my phone is bricked but have heard possibilities using ADB. I have never used ADB before and if anyone knows if this is a possible fix to my problem that would be great. It would be nice to know if it actually could fix my problem before looking into it and learning it all while finding out it has no chance of fixing my problem. I have tried using my sim card and a different sd card so those are not causing the problems.
So the background of what I am running on my g1. Right before I got my HD2 I was using Cyanogen version 4.2.14.1 with and ext 3. I had no problems with it until now. I got my HD2 a week ago and my g1 has been on about twice in that time without a sim card just for comparing purposes to the HD2. Then just today (about 2-3 days since I last turned it on) the screen just went black and I had my problems. I cannot return my phone because it has been over a year and I dont have insurance on the phone so these are not possibilities for me unfortunately. I also don't really want to get parts from other g1's and take apart and put my g1 back together. I am just looking for something with ADB or any other possible solution to the problem (if one exists).
Any help would be greatly appreciated!
I had this happen to me before. Apparently, it was a hardware GPU problem that would cause a boot loop because it couldn't draw anything on the screen. This happened on SuperD, AOSP, Cyanogen, and stock Donut.
If your problem is the same, you should be able to get into recovery, regardless of your ability to see what you're doing. Easy way of telling is to hit Camera+End on boot. If it doesn't vibrate, you're able to flash still. You may be able to get the screen back temporarily by either pulling the battery or letting the battery die and recharging.
Anyways, I ended up flashing the DREAIMG.nbh, and trying to upgrade back to 1.6 to remove traces of hacking. (Be careful if you have DangerSPL, you want to restore the default before flashing DREAIMG.nbh) I eventually got the screen working on 1.6, but it died again, so I sent it in to T-Mobile and got a replacement. I'm now using AOSP with no problems.
One small note, however, I did start having my problems using Cyanogen's mod. May want to bring it up with him?
Sorry if this sounds scatterbrained, it's a bit late and I should be asleep right now.
e:Just realized you said the warranty was void. You may be able to get something out of what I did, though? Good luck, in any case.
Thanks very much for the help even though it was really late. I did understand pretty much everything you said and I tried the camera plus power button and it didn't vibrate so it should mean I probably can flash things still. I have drained the battery and am charging it back up to see if that helped.
I have a friend who knows ADB so I am going to have him look at it to see if we can't get it working through there. Also the G1 screen has been popping up but then fading right when its about to change to the boot animation. So we will see how things go and I'll try a couple different things and report back if anything seems to work or open up more possibilities.
Thanks again for your information.
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
coolookoo said:
Ok, so my friend and I were going to flash a rom through fastboot. It was responding and such so we knew we were able to get it in there.
Anyone know what the command to flash a rom in fastboot is and if there are specific instructions to follow?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
sorry i have the same problem, but my g1 is not rooted nor has it been flashed before, my friend messed it up somehow? wen i turn it on all there is is a blank highlighted black screen. What do yall suggest i should do
r3s-rt said:
google it. i did and got about 100 links telling me how to do it. "unroot g1 with fastboot."
Click to expand...
Click to collapse
First of all we are not trying to unroot the phone just flash another rom
Secondly we already tried your "fantastic" method of using google before coming to the forums
Ok I think I just bricked my G1
I was following the steps on theunlockr.com and was following the steps to the T like I always do.
The problem incurred after flashing the spl. I flashed the correct radio then ir rebooted and went back into recovery mode. Then I flashed the spl all seemed well home+back and never rebooted. It stayed on a black screen for over 30 mins. So I took out the battery and waited a few mins and put battery back in and same thing. Just a black screen nothing I can do. I have tried holding home+power and camera+power and back+power nothing. I am stuck have looked it up and this is the best forum I have found to post in.
Any input would be great.
thanks
nate
So I installed this rom > http://forum.xda-developers.com/showthread.php?t=797546 this morning and everything was working fine. Texted, talked, got voicemail, email worked, everything. No problems. Restored my messages/contacts/etc. after I did the flash as well. All this was about 7am.
At 9am, I got a random pop up while trying to read a text and I can't remember exactly what it said, but was something to the effect of "blah blah blah could'nt be opened and will now be closed". But when I clicked ok, it was flicker once really fast and still be there. So I pressed the windows key and went to open task manager and another pop up appeared and said the same about task manager. So I went to restart it (pressing and holding the end key and selecting appropriate action) and it just went black. Went to turn it back on and nothing. I plug it into a charger or computer and nothing, at all. No lights, nothing. Removed battery, nothing. Only hint of fate I got was when i removed the memory card, and sim card, and tried again, it continuously vibrated, but still nothing on the screen or any lights, just vibration. Is this a brick? I can't even get into the bootloader, so can't reflash another rom.... Help?
It's hard to try and guess what the problem that you are encountering is. My 1st question would be if which version of the HD2 do you own? Is it the Tmobile version or the international version. There are roms that are specific to each device and it's crucial to know which one you are installing. Based on your signature, it seems like you may be on a CDMA network whereas Tmobile is GSM. But that doesn't quite explain why you were able to text and call for sometime before the crash. I suggest you retrace your steps following the flash guide found here--->http://forum.xda-developers.com/showthread.php?t=653614 Specially if this is your first flash. Try to provide some more information, (HSPL used, rom you were running before, etc...) So that we can help you better.
Best of luck.
Using tmobile hd2, thats why I posted in the tmo section.
Disregard my siggy, no longer even own that phone. This is probably my 10th+ flash on this phone alone, and I didn't do anything differently when I flashed this time around. I don't even look for roms in the non-tmo forum. Been on tmobile for about 5 months now using this phone and only this phone. All the roms I have used in the passed were perfectly fine. Last rom I was using before the one that messed up my phone was AthineOS. Also ran fine, just didn't like the battery drainage and the mms pics being super small when I recieved them. Plus didn't like the interface too much.
I think what he meant was if your phone was bought from T-Mobile USA or overseas.
It's not the radio, so the term bricked doesn't really apply. It sounds to me like it just kicked the bucket. The good news is if you can't get into bootloader mode tmo/htc will never know you installed hspl. Which means you can call T-Mobile and get it replaced under your insurance. Just make sure you can't get into bootloader to avoid the $100 software change fine.
so my mytouch 4g wont turn on even with a different battery. i plug it it in and it gives me a flash on th screen but thats it. any suggestion without sending it in
Take it to a tmo store, they'll swap it.
I got it off of Craigslist I think it was previously tampered with
Sent from my HTC Desire using XDA App
so i was in the process of doing a custom splash screen last night. i went through all the instructions on how to push the custom splash through terminal. everything went how the instructions said, but once i reboot it my phone turned off and never came back on. it doesnt power on, boot into recovery, nothing! i put the phone to charge and the red light comes on on the top left but when i take it off the charger it stays on.
i been rooted for about a month now and i was running cm7 build 8 when this happened. i just want to see if anybody has any idea on what going on. i tired everything i can think of. taking out the battery and normally powering on and nothing. taking off the battery and volume down and power to boot into recovery and nothing. taking off the battery, sd card, sim, putting back the battery and doing both normal power on and to boot into recovery and nothing.
First of all you just hijacked the guys old dead thread and second it sound like you just bricked your phone. As there is boot animation and there is slash screen. Seems like you flashed wrong thing. If the screen don't even turn on its dead then.
Sent from my HTC Glacier
Don't flame the poor guy! He's got it bad enough as is! And he didn't flash the "wrong thing" there are several threads on flashing splash screens in this phone's forum. Cut the guy some slack. He knows it may be bricked, he's just hoping it's not. And he was hoping for someone to provide some possible help. Not be be given **** for not opening a new thread.
i thread jacked because the thread was old and didnt want to clutter by starting a new one when im having some what the same problem. but no i pushed the splash image. i had already flashed a boot animation a few day back. i had call of android running on my phone as a boot animation. i just want to know is theres other methods of reaching hboot or recovery.
First of all don't put words in my mouth as my post does not contain any flame, second when I said wrong thing I meant he may not have meet the requirement for the splash image if he did correctly then obviously he would have had it up and running. Best thing for him would be going back to the original thread where he downloaded the image and asking the OP and troubleshoot it but at this point its to late all he can do now is warn others.
But if his phone is not old lol he can social engineer and play the victim card and send it back to HTC but first would be trying TMo saying he didn't get the POST OTA as he had PRE OTA and when he try to install the OTA it went blank and act like he has no idea what is going on, as he simply just want the phone to work or he will cancel service and do acting best of his life.
i already know i probably super bricked it. becuase ive bricked it before but not like this. i was able to fix it very quickly before. its like if the phone just doesnt have a battery. im just going to wait to see if anybody else has any more input. if not ill head to the tmo store see what they can do.
BlackSHELF said:
But if his phone is not old lol he can social engineer and play the victim card and send it back to HTC but first would be trying TMo saying he didn't get the POST OTA as he had PRE OTA and when he try to install the OTA it went blank and act like he has no idea what is going on, as he simply just want the phone to work or he will cancel service and do acting best of his life.
Click to expand...
Click to collapse
I do apologize for using the word flame. It was too strong. But I get fired up when people criticize instead of offering insight. If you had posted the above paragraph first, I wouldn't have had any issues. This is good and viable option. Albeit a last resort, but much better than criticizing for thread jacking. And I am the OP of the thread that he's using and am doing EVERYTHING I can to help him figure out a way to get this resolved.
coupetastic-droid said:
i already know i probably super bricked it. becuase ive bricked it before but not like this. i was able to fix it very quickly before. its like if the phone just doesnt have a battery. im just going to wait to see if anybody else has any more input. if not ill head to the tmo store see what they can do.
Click to expand...
Click to collapse
ok, I just got caught up on your issue. I am going to do a little research and see if I can come up with anything to maybe help. Do you have adb set up? What recovery are you running?
Same thing happened to me, flashed a rom rebooted and the phone never turned on again.
thanx every one for trying to help. i tried everything i can think of and i could not get that phone to power on at all. it was completely dead. so i went to the tmo store by my pad and they gave me a brand new one. now i just need to gain s=off on this one which i cant do for some reason. i dont know why since it was fairly easy to gain s=off on my other mt4g. ill figure out though.
coupetastic-droid said:
thanx every one for trying to help. i tried everything i can think of and i could not get that phone to power on at all. it was completely dead. so i went to the tmo store by my pad and they gave me a brand new one. now i just need to gain s=off on this one which i cant do for some reason. i dont know why since it was fairly easy to gain s=off on my other mt4g. ill figure out though.
Click to expand...
Click to collapse
Don't know if you used this guide yet or not but I will post it anyway http://forum.xda-developers.com/showthread.php?t=858996
toby4059 said:
Don't know if you used this guide yet or not but I will post it anyway http://forum.xda-developers.com/showthread.php?t=858996
Click to expand...
Click to collapse
I aready got s=off but thanx anyways.
Sent from my CM7 Glacier using XDA App
Hi.
I had the same problem on my htc glacier (mytouch 4g) which was turn it on, stuck on the htcwelcome screen, keep loading and then turn off automatically. My phone is rooted and cusome flashed to the new htc 3.0 sense when this happened, i did a back up and restore to the oem mytouch sense and now it is working just perfectly. So if your phone is rooted you might give it a shot and hope it will work again
i had same prob kinda
i flashed a rom was useing it for a week and today i went to use camera and while camera was loaded the screen shut off like not beining used it did the crt thing and all then it wouln't come out of it so i pulled battary after like 5 min of a lighted black screen and went to power phone back on and nothing like no batt.....
anyways what i was geting to is that i called tmoble and they said it sounded like a hardware problem if you can plug it in to wall or car charger and nothing.. when i plug it into a usb on pc i get
hsusbs or something so u all might want to look into that.
i have s mytouch 4g it wont boot
i rooted my mytouch 4g ussing gfree and then i installed sense 3.0 rom and it worked then force closed left me in bootloader then from there flasheed cm7 worked good for 15 days then said force closed again then never turned back on aghain now when i plug it back in it tells me cannot install drivver software and it recognizes it as qhsusb_dload any solutions or its a gonner contact me at [email protected]